Recovering from fid oversubscription, Recovering from fabric id conflict, Rebalancing traffic over multiple ifls – Brocade Network OS Administrator’s Guide v4.1.1 User Manual
Page 713: Fabric. refer to, Refer to, Rebalancing traffic over, Multiple ifls

a)
Enter the portCfgExPort
‐d Fabric OS command to set a unique front phantom domain ID.
b)
Enter the fcrXlateConfig importedFID exportedFID preferredDomainID command to set a
unique translate phantom domain ID.
Refer to the Fabric OS Command Reference for details about the portCfgExPort and
fcrXlateConfig commands.
Recovering from FID oversubscription
A "FID over-subscribed" message occurs when different Fibre Channel backbones attempt to connect
to the same edge fabric using different Fabric IDs (FIDs). When you assign a FID to the edge fabric
(portCfgExPort -f command), you must use the same FID as any other Fibre Channel backbone that
connects to the edge fabric.
To resolve this problem, complete the following steps.
1. On the Fibre Channel router on the backbone with the errant FID configured, disable the EX_Port.
2. Enter the portCfgExPort -f command to configure the EX_Port with the same FID as the EX_Port on
the other Fibre Channel router that connects to the same edge fabric.
3. Re-enable the EX_Port.
Refer to "Configuring an IFL for both edge and backbone connections" in the Fabric OS
Administrator's Guide for details.
Recovering from Fabric ID conflict
The "FID conflict" message occurs when a backbone fabric connects to two or more edge fabrics that
have the same Fabric ID (FID). Every edge fabric that a Fibre Channel router connects to must have a
Fabric ID configured for the EX_Port that is unique on that Fibre Channel backbone. This error is most
likely to occur when an edge fabric temporarily splits, causing it to appear as two edge fabrics with the
same Fabric ID. This symptom might occur during VCS Fabric or Fibre Channel fabric upgrade, or as a
result of a Brocade VDX or Fibre Channel switch reboot or crash.
Problem resolution depends on the cause of the problem. If the error is due to a temporary split, the
problem will go away when the fabrics merge again.
If the problem is not due to a temporary fabric split, the most likely cause is misconfiguration. In this
case, enter the portCfgExPort -f command to reconfigure one of the EX_Ports with a unique fabric ID.
Rebalancing traffic over multiple IFLs
If traffic across multiple interfabric links (IFLs) between a Fibre Channel router and an edge fabric is not
balanced as you intended, it may be because the Fibre Channel router cannot determine an FSFP path
from the Fibre Channel backbone to the target in the edge fabric. It uses all paths.
To direct the traffic the way you intend, on the FC router, use the fcrRouterPortCost command to
configure a cost for each IFL. Traffic will flow across the lowest-cost IFL.
1. Connect to the FC router and log in using an account with admin permissions.
2. Disable the EX_Port.
3. Enter the fcrRouterPortCost command to configure the link cost.
Set the cost to 1000 if you want to the link to carry traffic during normal operation. If you want the link
to not carry traffic under normal operation, set the cost to 10000 (ten thousand) and set the cost of at
least one other link to 1000. The default value is 1000, which you get when you enter a value of 0.
4. Re-enable the port.
For details about the fcrRouterPortCost command, refer to the Fabric OS Command Reference.
Recovering from FID oversubscription
Network OS Administrator’s Guide
713
53-1003225-04