Technical data

A-4 Fabric OS Administrator’s Guide
Publication Number: 53-0000518-09
Selecting a PID format
A
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.
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 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 only available in Fabric OS v2.6.2 and later, Fabric OS
v3.1.2 and later, and Fabric OS v4.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 A-2 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
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
- Security dcc database (if secure mode is
enabled)
The DID will be converted by FOS automatically.
Core Native
Extended Edge Core
Core Extended Edge
Table A-1 Effects of PID Format Changes on Configurations (Continued)
PID Format
Before Change
PID Format After
Change
Configuration Effect?