AIX Hosts Loose Paths to 3Par after OS Upgrade

[dyamamoto]

Hello,

During a routine 3Par OS upgrade from 3.3.1 MU3 to 3.3.1 MU5, we lost all FC path connections from our AIX hosts. I understand that each node needs to reboot during the upgrade process, but its supposed to re-establish connectivity to the configured hosts once each node comes back online. In my case, I have a bunch of AIX hosts that currently do not have any vv's exported to them, and all of their FC paths didnt come back online after the upgrade. Do you know if this is normal behavior if a host does not have any vv's exported to it?

Thx in advance - Darryl

[MammaGutt]

Not expected.

If you have a SAN fabric with NPIV enabled and 3PAR connected per best practice the hosts shouldn't notice the node reboots either. A feature called "persistent port" should virtualize the WWN of a partner port as it goes down.

[JinSXS]

if im not mistaken on the aix server the fcsXX the setting /one of the settings should be enabled which is dyn_tracking, that will allow AIX to track the PortID change when the 3par fail over the ports when doing the controller reboot

does 3par have AIX ODM that needed to be installed ?

[Richard Siemers]

Agree with all the responses so far. The AIX admins did not read the 3PAR Implementation Guide for AIX, in addition to installing the ODM for 3PAR, there are parameters that need to be set on the HBAs, like dyn_tracking. I've been there before, no one reads instructions anymore =)