HP 3PAR X9000 File Serving Software (IBRIX) Implementation Guide (QL226-96987, June 2013)

When a node is down during an online upgrade or node reboot, from the output of the showport
command, the FailoverState column would show that Persistent Ports is active. In the example
below, node 1 has gone down, Persistent Ports for 1:1:1 has become active on port 0:1:1, and
all filesystem I/O for port 1:1:1 is physically served by port 0:1:1.
Before Persistent Ports is active, the output of the showhost command displays as follows:
# showhost
Id Name Persona ---------------WWN/iSCSI_Name--------------- Port
1 server1 Generic 5001438009AE770E 0:1:1
5001438009AE770C 0:1:1
5001438009AE770E 1:1:1
5001438009AE770C 1:1:1
When Persistent Ports is active, the output of the showhost command, under the Port column,
shows both the physical port and the physical port where Persistent Ports is active. In the example
below, port 0:1:1, logged in from each of the host HBA ports, appears twice, once for the physical
port and once again for the persistent port that is active on the physical port.
# showhost
Id Name Persona ---------------WWN/iSCSI_Name--------------- Port
1 server1 Generic 5001438009AE770E 0:1:1
5001438009AE770C 0:1:1
5001438009AE770E 0:1:1
5001438009AE770C 0:1:1
After the controller node has been successfully rebooted, the FailoverState for the ports changes
back to none, as shown in the following example:
After the node has been successfully rebooted, the node entry of node 0 reappears in the GUI and
I/O is still in progress.
Manually, you can perform failover and failback using the controlport failover <N:S:P>
and controlport failback <N:S:P> command options.
Persistent Ports Limitations
Persistent Ports Technical White Paper
To learn more about Persistent Ports, refer to the following White Paper:
http://h20195.www2.hp.com/V2/GetPDF.aspx/4AA4-4545ENW.pdf
12 Configuring the HP 3PAR StoreServ Storage for Fibre Channel