Phil Freund wrote:
Update:  I was off base with my assumption about the upgrade problem not being 
related to MPXIO (Traffic Manager). That is exactly where the problem lies.

I finally had a chance to try doing an upgrade on a server with a SAN-based 
zone root without MPXIO and the upgrade worked with no problems. So disregard 
my comments about the fundamental design flaw - they are wrong. My suggested 
changes are unneeded.

I still have the problem with upgrading. Live Upgrade still does not look like 
it will ever be a possibility for the reasons listed in the original post. It 
now looks like I will first have to convert my servers off of MPXIO prior to 
doing the upgrade, run the upgrade, and then re-enable MPXIO. (As well as 
unencapsulating and re-encapsulating the boot drives for Veritas Volume 
Manager.) It's going to be real ugly, particularly because I don't currently 
know of a way to identify the mapping between the MPXIO devices and the same 
non-MPXIO devices.

Seems to depend on your setup, but try:

# stmsboot -L
non-STMS device name                    STMS device name
/dev/rdsk/c2t5006048AD52CFF88d0 /dev/rdsk/c4t60060480000190100478533030453435d0 /dev/rdsk/c3t5006048AD52CFF97d0 /dev/rdsk/c4t60060480000190100478533030453435d0

I still think that using MPXIO is the correct design decision for high 
availablity of the zones but the side-effects of that decision are a lot worse 
than I had anticipated. Perhaps a future update will allow for the use of MPXIO 
as an option for sites that are in my position.

This message posted from
zones-discuss mailing list

zones-discuss mailing list

Reply via email to