HP AE370A - Brocade 4Gb SAN Switch 4/12, Administrator'S Manual

Page: 404 / 447

388 Configuring the PID format
The following maps the PID format names to the names used in the management interfaces.
Before changing the PID format, determine if host reboots will be necessary. The section ” Host reboots ” on
page 382 summarizes the situations that might require a reboot.
Example
Changing to extended edge PID format
In rare cases, you might be affected by the presence in the fabric of drivers that rely on static binding to the
dynamically assigned PID; for example, you might be installing a switch running Fabric OS v4.2.0 into a
fabric consisting solely of Fabric OS v2.6.2 and later/v3.1.2 and later switches. In these cases, if you
absolutely cannot reboot the affected servers when you upgrade your switches, you can choose Extended
Edge PID format. It uses the same PID mapping for the first 16 ports and can support switches and Directors
with higher port counts. However, because Extended Edge format only supports 128 ports per domain, its
use can lead to port addressing issues in Directors.
Use the following procedure only if your fabric contains devices that are bound statically and you cannot
reboot the host.
PID format name Management interface name
native PID switch PID address mode 0
core PID switch PID address mode 1
extended edge PID switch PID address mode 2
switch:admin> switchdisable
switch:admin> configure
Configure...
Fabric parameters (yes, y, no, n): [no] y
Domain: (1..239) [1]
BB credit: (1..27) [16]
R_A_TOV: (4000..120000) [10000]
E_D_TOV: (1000..5000) [2000]
WAN_TOV: (1000..120000) [0]
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]
Switch PID Address Mode: (0..2) [1] < Set mode number here.
Per-frame Route Priority: (0..1) [0]
Long Distance Fabric: (0..1) [0]