HP StorageWorks Fabric OS 5.3.x administrator guide (5697-0244, November 2009)

426 Configuring the PID format
Table 102 shows various combinations of existing fabrics, new switches added to those fabrics, and the
recommended PID format for that combination. The criteria for the recommendations are first to eliminate
host reboots, and second to minimize the need for a host reboot in the future.
Table 102 PID format recommendations for adding new switches
Existing Fabric OS
versions; PID format
Switch to be
added
Recommendations (in order of preference)
v2.6.2 and later/v3.1.2 and
later; Native PID
v2.6.2 and
later/v3.1.2
and later
1. Use Native PID format for new switch
Host reboot is not required.
2. Convert existing fabric to Core PID format, upgrading the
version of Fabric OS, if necessary. Set Core PID format for new
switch.
Host reboot is required.
3. If devices are bound statically and it is not possible to reboot,
convert existing fabric to Extended Edge PID format, upgrading
the version of Fabric OS, if necessary. Use Extended Edge PID
format for new switch
Host reboot is not required.
v4.2.0 and
later
1. Convert existing fabric to Core PID format, upgrading the
version of Fabric OS, if necessary. Set Core PID format for new
switch.
Host reboot is required.
2. If devices are bound statically and it is not possible to reboot,
convert existing fabric to Extended Edge PID format, upgrading
the version of Fabric OS, if necessary. Use Extended Edge PID
format for new switch
Host reboot is not required.
v2.6.2 and later/v3.1.2 and
later/v4.2.0 and later; Core
PID
v2.6.2 and
later/v3.1.2
and
later/v4.2.0
and later
Use Core PID for new switch
Host reboot is not required.
v2.6.2 and later/v3.1.2 and
later/v4.2.0 and later;
Extended Edge PID
v2.6.2 and
later/v3.1.2
and
later/v4.2.0
and later
Use Extended Edge PID for new switch
Host reboot is not required.