Fabric OS 5.2.x administrator guide 383
CAUTION:
After changing the fabric PID format, if the change invalidates the configuration data (see
Table 91
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.
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.
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.
Table 91
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:
•
re-enable 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 Fabric OS automatically.
Core
Native
Extended Edge
Core
Core
Extended Edge
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......