Hp/Ux Procedure - HP A7533A - Brocade 4Gb SAN Switch Base Administrator's Manual

Hp storageworks fabric os 6.1.x administrator guide (5697-0234, november 2009)
Hide thumbs Also See for A7533A - Brocade 4Gb SAN Switch Base:
Table of Contents

Advertisement

Suppress Class F Traffic: (0..1) [0]
SYNC IO mode: (0..1) [0]
Core Switch PID Format: (0..2) [0] 1
Per-frame Route Priority: (0..1) [0]
Long Distance Fabric: (0..1) [0]
BB credit: (1..27) [16]
10.
After all switches are updated to use the new PID format and re-enabled, verify the fabric has fully
reconverged. Each switch can communicate with other switches in the fabric and no segmentation has
occurred.
1 1.
Enter the cfgEnable active_config_name command on one of the switches in the fabric to update
zoning to use the new PID form.
This does not change the definition of zones in the fabric; it causes the lowest level tables in the
zoning database to be updated with the new PID format setting. It is only necessary to do this once
per fabric; the zoning update automatically propagates to all switches.
At this point, all switches in the fabric are operating in the new addressing mode.

HP/UX procedure

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.
If you are not using multipathing software, stop all I/O going to all volumes connected through the
switch and fabric to be updated.
3.
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
4.
If you are using multipathing software, use that software to remove one fabric's devices from its
configuration.
5.
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
6.
Make a backup copy of the volume group directory using tar from within /dev. For example:
tar –cf /tmp/jbod.tar jbod
7.
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
8.
Connect to each switch in the fabric
9.
Issue the switchDisable command.
10.
Issue the configure command and change the Core Switch PID Format to 1.
1 1.
Issue the command cfgEnable [effective_zone_configuration]. For example:
cfgEnable my_zones
12.
Issue the switchEnable command. Enable the core switches first, then the edges.
13.
Clean the lvmtab file with the command vgscan.
14.
Change to /dev and untar the file that was tared in step 4. For example:
tar –xf /tmp/jbod.tar
15.
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
16.
Activate the volume groups using vgchange. The proper usage would be vgchange –a y
<path_to_volume_group>. For example:
454 Configuring the PID format

Hide quick links:

Advertisement

Table of Contents
loading

Table of Contents