HP StorageWorks Fabric OS 6.x administrator guide (5697-7344, March 2008)

Fabric OS 6.x administrator guide 479
AIX procedure
This procedure is not intended to be comprehensive. It provides a starting point from which a SAN
administrator can 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. If you are not using multipathing software, stop all I/O going to all volumes connected through the
switch or fabric to be updated.
3. If you are not using multipathing software, vary the volume groups offline. The command usage is
varyoffvg <volume_group_name>. For example:
varyoffvg datavg
4. If you are not using multipathing software, unmount the volumes from their mount points using umount.
The command usage is umount <mount_point>. For example:
umount /mnt/jbod
5. If you are using multipathing software, use that software to remove one fabric’s devices from its
configuration.
6. Remove the device entries for the fabric you are migrating. For example, if the HBA for that fabric is
fcs0, execute the command:
rmdev -Rdl fcs0
7. Connect to each switch in the fabric.
8. Issue the switchDisable command.
9. Issue the configure command and change the Core Switch PID Format to 1.
10. Issue the configEnable [effective_zone_configuration] command. For example:
configenable my_config
11. Issue the switchEnable command. Enable the core switches first, then the edges.
12. Rebuild the device entries for the affected fabric using the cfgMgr command. For example:
cfgmgr –v
This command might take several minutes to complete.
13. If you are not using multipathing software, vary the disk volume groups online. The proper usage would
be varyonvg <volume_group_name>. For example:
varyonvg datavg
14. If you are not using multipathing software, mount all devices again and restart I/O. For example:
mount /mnt/jbod
15. If you are using multipathing software, reenable the affected path.
16. Repeat all steps for all fabrics.