I have been performing an upgrade for a customer, using Solaris Live Upgrade to go from Solaris 10 update 2 to Solaris 10 update 10 and at the same time upgrade EMC powerpath from [an old version] to version 5.5I am by no means a powerpath expert, but I am well aware of the issues with upgrading only the one without the other.  The process I followed is:Live-upgrade SolarisRemove (pkgrm) powerpath from the ABEComment out the powerpath dependent file systems in the ABELUactivate and rebootInstall PowerPath 5.5 P 01 B 2The install finds the left-over power-path config and asks whether I want to upgrade it.  On some of the 5 servers, the old version is PowerPath version 5.2, on others it was still running 4.5, but the result is the same for all of them.At the end of the pkgadd it tells me the driver was successfully installed (it was) and tells me that no reboot is needed.  However when I run powercf or powermt display I get an error stating Device(s) not foundRebooting did not help.  cfgadm looks as expected (Sorry I did not save the output), devfsadm -Cv did not create or remove any device links.  The HBAs were linking (confirmed by luxadm -e probe as well as fcinfo hba-port)format showed only the Solaris native links to the LUNs, with half of them in error state as expected due to them seen via both the avtive and passive path. mpathadm is not active.After googling around I found a suggestion to look at the output of powermt display options to confirm that clariion management is enabled, and found that is says unmanaged...  All other storage classes showed as managedI then ran powermt manage class=clariion which returned an error stating incompatible initiator information received from the arrayDespite this error I then got the emcpower devices and could see everything looking normal in powermt display dev=all.  For good measure I followed this by powercf -q; powermt config; powermt saveI then un-commented the entries in /etc/vfstab and rebooted to make sure all was ok.  I then ended up with a system in single-suer mode with filesystems/local in maintenance.  I discovered with a lot of testing that I had to redo the powermt manage class=clarion procedure after every reboot.For now I have reverted to the old pre-upgrade ABE.  Everything is still working perfectly when I moved back to the old versions of Solaris and PowerPath.
Storage becomes unmanaged after Solaris and PowerPath upgrade
solaris;upgrade
I did the following and it worked:Although the Solaris OS can distinguish between FC and iSCSI devices, PowerPath 5.5 does not make this distinction for manage and unmanage. The mpxio-disable value must be set to yes in both the fp.conf and iscsi.conf files for PowerPath to manage the following storage arrays:EMC VNXEMC CLARiiONHitachi USP and HP StorageWorks EVA 3000/5000/8000Arrays listed in scsi_vhci.confSee page 35 of the Installation and Administration guide for EMC PowerPath for Solaris for more details. The Determine if arrays are managed by PowerPath or MPxIO chapter provides the details. When mpxio-disable=yes statement is missing from iscsi.conf file, VNX class is implicitly managed by MPxIO. Since there is no explicit statement to manage the class (the VNX class did not exist in the previous release), the new VNX becomes unmanaged. 