HP StorageWorks Fabric OS 6.2 administrator guide (5697-0016, May 2009)

532 Configuring the PID format
At this point, all switches in the fabric are operating in the new addressing mode.
HP-UX procedure for changing the PID format
This procedure is not intended to be comprehensive. It provides a starting point from which a SAN
administrator could develop a site-specific procedure for a device that binds automatically by PID, and
cannot be rebooted due to uptime requirements.
1. Back up all data. Verify backups.
2. Perform the appropriate actions based on whether you using or not using multipathing software:
• If you are not using multipathing software, stop all I/O going to all volumes connected through the
switch and fabric to be updated.
• If you are not using multipathing software, unmount the volumes from their mount points using
umount. The proper usage is umount <mount_point>. For example:
umount /mnt/jbod
3. If you are using multipathing software, use that software to remove one fabric’s devices from its
configuration.
4. Deactivate the appropriate volume groups using vgchange. The proper usage is
vgchange –a n <path_to_volume_group>. For example:
vgchange –a n /dev/jbod
5. Make a backup copy of the volume group directory using tar from within /dev. For example:
tar –cf /tmp/jbod.tar jbod
6. Export the volume group using vgexport. The proper usage would be
vgexport –m <mapfile> <path_to_volume_group>. For example:
vgexport –m /tmp/jbod_map /dev/jbod
7. Connect to each switch in the fabric
8. Enter the switchDisable command.
9. Enter the configure command and change the Core Switch PID Format to 1.
10. Enter the command cfgEnable [effective_zone_configuration]. For example:
cfgEnable my_zones
11. Enter the switchEnable command. Enable the core switches first, and then the edges.
12. Clean the lvmtab file by using the command vgscan.
13. Change to /dev and untar the file that was tared in step 4. For example:
tar –xf /tmp/jbod.tar
14. Import the volume groups using vgimport. The proper usage would be
vgimport –m <mapfile> <path_to_volume_group> <physical_volume_path>. For
example:
vgimport –m /tmp/jbod_map /dev/jbod /dev/dsk/c64t8d0 /dev/dsk/c64t9d0
15. Activate the volume groups using vgchange. The proper usage would be vgchange –a y
<path_to_volume_group>. For example:
vgexport –a y /dev/jbod
16. Perform the appropriate actions based on whether you using or not using multipathing software:
• If you are not using multipathing software, mount all devices again and restart I/O. For example:
mount /mnt/jbod
• If you are using multipathing software, reenable the affected path. The preceding steps do not
“clean up” the results from ioscan. When viewing the output of ioscan, notice the that the original
entry is still there, but now has a status of NO_HW.