Here is something we received from HP when upgrading our 7450. I actually did the upgrade to our 7200 and found the MGT port went offline, so when changing the port to be 1000FD it came back. Also I updated to P07 which then put the cages in a degraded state about FW level (needed to be at 321a). For some reason it didn't automatically upgrade the cages, hmmm? When I called support they said I just needed to execute "upgradecage -a". Then it upgraded them. Nice documenting this in the release notes HP.
Please review the following points and confirm accordingly: 1. Ensure the Host and Array recommendations that was shared earlier & also attached with this email are implemented. Failure to follow the recommendations (e.g. MS MPIO patch) may cause host disconnect/upgrade issues. 2. Let us know the details of the Contact person who would be available to approve controller node reboots and validate host status during the upgrade. 3. The preferred mode of communication, email or phone? 4. Please confirm if you have any Cisco Catalyst/NX series or HP Procurve switch in the environment. If yes, the below workaround needs to be followed before the upgrade For Cisco Catalyst/NX series switches: The Switch ports connected to management ports of 3PAR arrays may disable during InformOS 3.2.1 MU2 upgrade if connected to Cisco Catalyst/NX series switches with link-flap detection enabled. To prevent this, you may suggest the customers to disable the link flap detection feature on ports attached to 3PAR management ports by executing the interface configuration command “no errdisable detect cause link-flap” before firmware upgrade. This command needs to be executed on the Cisco Catalyst/NX series Switches For HP Procurve Switches: If the Network Switch connected to the Admin ports on 3PAR is a HP Procurve, kindly set the interface speed on Procurve Switch to 1000 MBPS. This should be done to avoid the loss of communication between 3PAR Nodes and SP during the upgrade to 3.2.1.MU2.Not setting the speed to 1000 MBPS will result in SP-InServ communication issues during the OS upgrade
So going through the upgrade the first time resulted in loss of network connectivity between the SP and the Inserv. I had opened up a case with HP, but then remembered something about the network and this particular upgrade. I changed the network port that the Inserv connects to to 1000FD and network connectivity came back. After the upgrade completed successfully I applied P07. After the upgrade completed successfully again, the array stated the drive cages were not at the correct FW level. Finally HP calls me this morning and says to run “upgradecage –a”, viola, the drive cages started to upgrade to the correct FW of 321a, just like the 7450.
Shouldn’t all this be in the release notes?????
|