Changes to configuration data
Table 95
lists various combinations of before-and-after PID formats, and indicates whether the
configuration is affected.
NOTE:
After changing the fabric PID format, if the change invalidates the configuration data (see
Table 95
to determine this), do not download old (pre-PID format change) configuration files to any switch
on the fabric.
Table 95
Effects of PID format changes on configurations
PID format before
change
Native
Extended Edge
Native
Core
Extended Edge
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 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.
NOTE:
Switches that are queried using outside calls should be configured using PID 1 (core PID) to ensure
that the correct port numbering is used in other management applications.
PID format after
Configuration effect?
change
Extended Edge
No impact
Native
No impact
Core
You must:
Reenable zoning, if there is an active zone set and it
Native
uses port zones.
Core
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.
Fabric OS 6.1.x administrator guide 453