Re: [foxboro] I/A v 8 with Solaris 10

Russ & Andreas,

I should have been more specific in my answer.

NCNIs are not version 8.x equipment.  They only work between version 6.x nodebus
segments and version 7.x workstations and switches, or as FONBE replacements
between two nodebus segments.  So, while you can leave NCNIs in place, that may
mean having three network layers - Nodebus, switched, and mesh.  

Currently, we have two of our V7.1 systems linked together with a V8.1 system
via one nodebus segment on each system.  We had to reboot all the control
stations on one of the two V7.1 systems.  Our current structure (6.5.1 nodebus,
7.1 switched network, 8.1 mesh network) is overly complex and has the potential
to route significant traffic through the layer that can support it the least
(Nodebus), so we will continue migrating segments off the V7.1 on to the V8.x
network via ATS and/or upgrading the CPs and gateways to 270s+FDSI so we can
move control only segments to the mesh by upgrading the nodebus equipment to
mesh connectable.  Unfortunately, each nodebus segment we migrate off the V7.1
network on to the V8.x network with ATS will require re-addressing it's NSAP
addresses, and therefore rebooting the control stations. 

If you already have CLANs it should be easy to replace them with ATS and no
reboots required.  If you have large V7.x systems without CLANS (we have a 7
node, a 5 node and a 4 node system at 6.5.1/7.1) then reboots are inevitible. 
We had previously migrated from CLANs to NCNIs (rebooting everything) so now we
have to go back to CLAN style NSAP addresses.



Quoting "Boulay, Russ" <russ.boulay@xxxxxxxxxxxxxxxx>:

> Andreas.....
> 
> ATS's are not replacements for NCNI's..in most cases...NCNI's stay in
> place.
> ATS's tie Mesh to either an existing single node system...or multimode
> systems. In multimode systems they take the place of Lan modules. There
> are several users now that have migrated 14+ node systems to ATS
> without
> the reboot of their control stations.
> 
> In Kevin's example, he chose a multi "segment" single node of NCNI's.
> The migration to Mesh in his example....now replaced the NCNI's with
> ATS's which now made it a multi "node" system, and those segments had
> to
> be isolated from each other. This would lead to control station reboot
> because it was decided to make multi nodes out of a single node
> system.=20
>  If Kevin had chosen to just simply leave the NCNI's in place and add
> an
> ATS to his current single node, no reboot would be required.
> The only reason to change that topology would be if 64 station limit
> per
> would be exceeded by adding the ATS.
> 
> With the ATS you will NOT have to reboot your existing control stations
> if the existing topology stays in place.
> 
> There have been many users now with that have migrated major multi node
> systems without reboot of any control stations.
> 
> 
> -----Original Message-----
> From: foxboro-bounce@xxxxxxxxxxxxx
> [mailto:foxboro-bounce@xxxxxxxxxxxxx]
> On Behalf Of Kevin FitzGerrell
> Sent: Wednesday, July 26, 2006 5:21 AM
> To: foxboro@xxxxxxxxxxxxx
> Subject: Re: [foxboro] I/A v 8 with Solaris 10
> 
> Andreas,
> 
> I/A version 8.x is I/A on the mesh.
> 
> You will be able to use your AW51Gs by upgrading (paid upgrade) to=20
> Solaris 10 and 8.x, but they are for use on the mesh network. You
> may=20
> be able to use switches from a 7.x network for version 8. NCNIs will=20
> need to upgrade to ATS.
> 
> We currently have two major plant areas with V6.5.1 on the nodebus,
> V7.1
> 
> switched network linking nodebus segments together, and V8.1
> connecting=20
> the two plant areas.
> 
> One big downside in moving from NCNIs to ATS is that all control=20
> stations in all but one network segment need to reboot to be=20
> re-addressed, going back to CLAN style NSAP addresses.
> 
> Regards,
> 
> Kevin
> 
> Weiss, Andreas wrote:
> >>No, Solaris on the mesh will not support Display Manager or Legacy
> >>Historian.
> >=20
> >=20
> > Hi Kevin,
> >=20
> > Mesh???
> >=20
> > We have an installed base of AW51G (P81) with I/A v. 7.1.x and I
> thought
> > that we would get an update to I/A version 8 with Solaris 10 for our
> > existing installation with nodebus and CP60.
> >=20
> > Is that a wrong idea?
> >=20
> > Regards,
> > Andreas
> > =20
> > =20
> >
> ________________________________________________________________
> _______
> > This mailing list is neither sponsored nor endorsed by Invensys
> Process
> > Systems (formerly The Foxboro Company). Use the info you obtain here
> at
> > your own risks. Read
> http://www.thecassandraproject.org/disclaimer.html
> > =20
> > foxboro mailing list:
> http://www.freelists.org/list/foxboro
> > to subscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> > to unsubscribe:
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> > =20
> >=20
> >=20
> =20
> =20
> _____________________________________________
> __________________________
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
> =20
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Djoin
> to unsubscribe: =
> mailto:foxboro-request@xxxxxxxxxxxxx?subject=3Dleave
> =20
> 
>  
>  
> ______________________________________________________________________
> _
> This mailing list is neither sponsored nor endorsed by Invensys Process
> Systems (formerly The Foxboro Company). Use the info you obtain here at
> your own risks. Read http://www.thecassandraproject.org/disclaimer.html
>  
> foxboro mailing list: http://www.freelists.org/list/foxboro
> to subscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
> to unsubscribe: mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave
>  
>  

 
 
_______________________________________________________________________
This mailing list is neither sponsored nor endorsed by Invensys Process
Systems (formerly The Foxboro Company). Use the info you obtain here at
your own risks. Read http://www.thecassandraproject.org/disclaimer.html
 
foxboro mailing list:             http://www.freelists.org/list/foxboro
to subscribe:         mailto:foxboro-request@xxxxxxxxxxxxx?subject=join
to unsubscribe:      mailto:foxboro-request@xxxxxxxxxxxxx?subject=leave

Other related posts: