Brocade Fabric OS Troubleshooting and Diagnostics Guide (Supporting Fabric OS v7.3.0) - Manual (Page 82)

66 Fabric OS Troubleshooting and Diagnostics Guide
53-1003141-01
Fabric identification issues
7
• Admin Domains are mutually exclusive with Virtual Fabrics. When Virtual Fabrics is enabled, all
access control is based on the Virtual Fabrics context.
• Traffic Isolation zones with no failover option are not supported in logical fabrics. TI zones
defined in the base fabric for logical fabric traffic must allow failover.
NOTE
The configure command has a “Disable FID check” fabric parameter option, which can be used to
disable the FID check for FICON logical switches.
Fabric identification issues
Symptom E_Ports directly connecting two logical switches do not form, or are disabled.
Probable cause and recommended action
The FIDs on each of the logical switches must be the same.
Use the lsCfg
--
show command to view the current FIDs on the chassis and then the lsCfg
--
change FID -newfid FID command to change the FID.
Symptom Invalid FID.
Probable cause and recommended action
FIDs for switches may be from 1 through 128 as long as they are not already in use, except for
EX_Ports, which are only assigned FIDs from 1 through 127.
Use the lsCfg
--
show command to verify whether the FID is in use. If it is, use another FID.
Symptom The FID is currently in use.
Probable cause and recommended action
You may not create two (2) or more logical switches with the same FID.
Use the lsCfg
--
show and fcrFabricShow commands to view FIDs in use.
Logical Fabric issues
Symptom Logical port disabled.
Probable cause and recommended action
This message indicates an LISL was disabled because of some protocol conflict or security or policy
violation. This can result in possible traffic issues. You should resolve the cause of the conflict and
re-enable the LISL by using the lfCfg
--
lislenable command.