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

470 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.
Evaluating the fabric
If there is a possibility that your fabric contains host devices with static PID bindings, you should evaluate
the fabric for the following items:
• Find any devices that bind to PIDs.
• Determine how each device driver will respond to the PID format change.
• Determine how any multipathing software will respond to a fabric service interruption.
If current details about the SAN are already available, it might be possible to skip the Data Collection step.
If not, it is necessary to collect information about each device in the SAN. Any type of device might be
able to bind by PID; each device should be evaluated before attempting an online update. This information
has broad applicability, because PID-bound devices are not able to seamlessly perform in many routine
maintenance or failure scenarios.
Table 102 PID format recommendations for adding new switches
Existing Fabric OS versions;
PID format
Switch to be added Recommendations (in order of preference)
2.6.2 and later/3.1.2 and
later; Native PID
2.6.2 and later/3.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.
4.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.
2.6.2 and later/3.1.2 and
later/4.2.0 and later; Core PID
2.6.2 and later/3.1.2
and later/4.2.0 and
later
Use Core PID for new switch.
Host reboot is not required.
2.6.2 and later/3.1.2 and
later/4.2.0 and later;
Extended Edge PID
2.6.2 and later/3.1.2
and later/6.0
Change fabric to Core PID. Extended Edge is not
supported in Fabric OS 6.0.
Host reboot is required.