394 Configuring the PID format
Example
10.
After all switches are updated to use the new PID format and re-enabled, verify that the fabric has fully
reconverged (each switch “sees” the other switches).
11.
Enter
cfgEnable [active_zoning_config]
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, but merely 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.
Backup all data. Verify backups.
2.
If you are not using multipathing software, stop all I/O going to all volumes connected through the
switch/fabric to be updated.
3.
If you are not using multipathing software, unmount the volumes from their mount points using umount.
The proper usage would be
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 would be
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.
11.
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 by using the command vgscan.
switch:admin> switchdisable
switch:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no] yes
Domain: (1..239) [1]
R_A_TOV: (4000..120000) [10000]
E_D_TOV: (1000..5000) [2000]
Data field size: (256..2112) [2112]
Sequence Level Switching: (0..1) [0]
Disable Device Probing: (0..1) [0]
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]
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......