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

Andreas,

There is an update path to Solaris 10 for your 51G, and possibly much of 
the rest of your system, but you're right in saying it is more expensive 
to have taken the intermediate 7.x step.

Unfortunately, we had an immediate need to migrate away from our CLANs 
and add new segments to our network, so the 7.x step was helpful.

We bought switches that were going to be supported under V8, and 51F 
workstations that should be able to go to Solaris on the mesh.

I'm anxious to see what the advantage upgrade cost for migrating a V7.x 
license to a V8.x license for a Solaris workstation.  My RCNIs will be a 
write-off, unless they figure into an advantage upgrade somewhere.  I'll 
be purchasing fibre NICs for the boxes, hope I can fit a pair in each of 
my 51Fs - not many slots in those boxes.

On the up side, V8 NFD in the ATS seems to be much more effective and 
robust than the V7 NFD on a 51F behind an RCNI.  I do wish there was a 
good way to get the same level of logging (nfd_log and nfd_debug) as 
when NFD runs on an AW.

As to your other point, I also would love to see a system that installed 
on Solaris 10, building on some of the great features of the OS.  It may 
be that since many of the legacy compatibilities are left behind with 
Solaris on the Mesh, this will actually be possible.

It looks like you will have to have at least one Windows system though 
-- Display Manager is not supported, and neither is FoxDraw.  You'll 
have to do configuration on a windows workstation and convert/copy 
graphics to the Solaris workstations.

Regards,

Kevin FitzGerrell
+64 27 460 9994

Weiss, Andreas wrote:
> Hi Kevin and Russ,
> 
> thanks a lot for that valuable information.
> 
> But I'm still a little bit irritated about the fact that we have thrown
> our AW51C away, using now AW51G (P81) and their is "no" update path to
> Solaris 10.
> 
> Solaris 10 and an I/A System that avoids it to manipulate the underlying
> operating system would allow us to manage the systems in a better way.=20
> Means a central system to do health check about all system using
> standard solaris products and a lot things more ...
> 
> I'm ending with the idea that it would be better to use the old AW51C
> and migrate directly to mesh instead the thing that we have done.
> The way that Kevin and we seems to go is in my eyes to expensive. It
> seems to be cheaper to jump over every second hardware update. That
> requires another strategy regarding spare parts but thats not a problem
> for big installations.
> 
> ...
> 
> Regards,
> Andreas
>  
>  
> _______________________________________________________________________
> 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: