HP 3PAR Upgrade Pre-Planning Guide

4. If the LUN paths display online, I/O is not affected and paths remain accessible as long as
the server is not restarted during the online upgrade process.
NOTE: HP-UX OS version 11i v2 (11.23) and earlier do not provide the health check utility,
however it has been verified that even though the devices are in the NO_HW state, the online
upgrade will resume without I/O interruption.
If an HP-UX host is restarted during the online upgrade operation, the following steps must be
performed to re-discover 3PAR devices:
1. Ensure all InServ nodes have successfully completed the online upgrade and showing the
correct HP 3PAR OS version as follows:
# cli upgradesys -status
System is not currently undergoing an online upgrade.
First node to be rebooted is node 3
Which will be followed by node 0
Which will be followed by node 2
Which will be followed by node 1
# showversion —b
Release version 3.1.2.322 (MU1)
Patches: P05, P13
Component Name Version
CLI Server 3.1.2.322 (MU1)
CLI Client 3.1.2.322 (MU1)
System Manager 3.1.2.428 (P05)
Kernel 3.1.2.322 (MU1)
TPD Kernel Code 3.1.2.322 (MU1)
TPD Kernel Patch 3.1.2.466 (MU1)
2. Scan the HP-UX system hardware for usable I/O system devices:
#ioscan -fn
3. If you are using LVM/PVLinks, scan the physical volumes for LVM volume groups and activate
them:
#vgscan -v -a
Run the following command for each volume group using 3PAR LUNs:
#vgchange -a y <VG Name>
4. If you are using VxVM, rebuild the volume device nodes and start the volumes:
#vxdctl enable
#vxvol –g <Disk Group> start <Volume Name>
Verify that the volumes are online:
#vxprint –ht –g <Disk Group>
32 HP-UX Guidelines