HP StorageWorks Fabric OS 6.2 administrator guide (5697-0016, May 2009)

Fabric OS 6.2 administrator guide 525
which is capable of addressing higher port counts. Changing from Native PID format to Core PID format
changes the PID, which requires hosts that use port binding to be rebooted.
Static PID mapping errors
If you can avoid using drivers that employ static PID binding, you should do so.
With the WWN or dynamic PID binding most typically used with drivers, changing the device’s PID does
not affect the PID mapping. However, before updating the PID format, it is necessary to determine whether
any devices in the SAN use static PID binding.
For those few drivers that do use static PID binding, changing the PID format breaks the mapping, which
must be fixed either by rebooting the host or by using a manual update procedure on the host.
To correct mapping errors caused by static PID binding, see the following sections:
• See ”Evaluating the fabric” on page 526 for details on finding devices that use static PID binding. Then
see Figure on page 528 or ”Changing the PID format offline” on page 528 for recommendations.
• See ”Port number to area ID conversion” on page 530 for instructions.
Changes to configuration data
Table 100 lists various combinations of before-and-after PID formats, and indicates whether the
configuration is affected
IMPORTANT: After changing the fabric PID format, if the change invalidates the configuration data (see
Table 100 to determine this), do not download old (pre-PID format change) configuration files to any switch
on the fabric.
After changing the fabric PID format and verifying correct fabric operation, resave configuration data by
running the configUpload command.
Before downgrading firmware, change the PID back to supported PIDs such as Core PID. If the database is
automatically converted, save the converted database, and then download the older OS.
PID format selection
All switches in a fabric must use the same PID format, so if you add a switch that uses a different PID format
to a fabric, the switch will segment from the fabric. The format you select for your fabric depends on the mix
of switches in the fabric, and to an extent on the specific releases of Fabric OS in use (for example,
Extended Edge PID format is available only in Fabric OS 3.1.2 and later and Fabric OS 4.2.0 through
5.3.0).
If you are building a new fabric with switches running various Fabric OS versions, use Core PID format to
simplify port-to-area_ID mapping.
Table 100 Effects of PID format changes on configurations
PID format
before change
PID format after
change
Configuration effect?
Native Extended Edge No impact
Extended Edge Native No impact
Native Core You must:
Reenable zoning, if there is an active zone set and it uses
port zones.
You do not need to reconfigure Destination ID (DID) if
using:
• Performance monitoring
• The configure command to change the PID format
• The performance monitor database
• The zoning database
The DID will be converted by Fabric OS automatically.
Core Native
Extended Edge Core