HP StorageWorks Fabric OS 5.X Administrator Guide (AA-RVHWB-TE, September 2005)

Fabric OS 5.x administrator guide 215
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 converted, save the converted database, and then download the earlier OS.
Selecting a PID format
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 segments 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 2.6.2 and later, Fabric OS 3.1.2 and
later, and Fabric OS 4.2.0 and later).
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 46 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 45 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 DID if using:
• Performance monitoring
• The configure command to change the PID
format
• The performance monitor database
• The zoning database
• Security dcc database (if secure mode is
enabled)
The DID is converted by FOS.
Core Native
Extended Edge Core
Core Extended Edge