Powerpath upgrade to 5.2

i would run emcgrab on all the systems, you can get grabs here:

Home > Support > Product and Diagnostic Tools > Grab Utilities

then i would run these out from grubs through HEAT here:

Home > Support > Product and Diagnostic Tools > Environment Analysis Tools > Host Environment Analysis Tool (HEAT)

looks for things that are marked as critical, and lastly i would run your config through E-Lab navigator found here:

Home > Support > Interoperability and Product Lifecycle Information > E-Lab Interoperability Navigator

As dynamox suggested doing a grab is the best approach since you never know exactly what you have. In fact I'm suprised that your CE did not request you to do that since that is the normal course of action for "out-of-family" microcode upgrades.

Since your OS versions are relatively new and it looks like you only have a single HBA type I'm sure you will be fine. Not aware of any major gotchas with PowerPath 5.x for Windows/Linux versions that you referenced.

As for ECC - what version of it are you running? From a host-agent perspective you should not have any issues, but I know ECC 6.0 was required for 5772 code support via the Symmetrix/SDM agents. To take advantage of some of the 5773 features I believe you do need to be at ECC 6.1.

I have see more issues on Windows 2003 upgrading from older versions of PowerPath to version 5.2 than I ever did upgraded older versions to 5.1. New installations seem to work fine, but the upgrades are hit or miss so far for me. Sometimes the safest route for a PowerPath upgrade is to disable storage access (disabling the switch ports is sometimes the easiest way), uninstall old version of PowerPath, reboot, install new version of PowerPath, reboot and enable storage access.

Thank you all for your inputs. We are at ECC 6.0. We will first upgrade to 5772 and then once the powerpath are upgraded to 5.2, then upgrade the code to 5773. Also the servers are cluster'd. so we are planing to start on all passive nodes and then failover and upgrade on active nodes. Just thought of knowing any gotchas.

what OS ?

We are doing the same upgrading the support software to allow for Enginuity code upgrades 71->72->73 etc.

I found PowerPath v5.2-SP2 has a huge memory leak. Basically froze any system where it was installed after a day with page memory failures. I downgraded all my test systems to PP v5.2.0 and everything seems fine with this version.

Windows 2003 SP2 Enterprise on DL385 G1 hardware - SE 6.5.2

cool ..thank you for sharing ..going to be on the lookout next time i am upgrading my win2k3 boxes.