Brocade Network OS Administrator’s Guide v4.1.1 - Manual (Page 712)

Dual-CLI sessions from the same switch: If you start a zone transaction from CLI-Session1 and
then try to perform a zone modification from CLI-Session2, the CLI-Session2 zone transaction is not
allowed, as CLI-Session2 is not the owner of the open transaction. If CLI-Session1 logs out, this ends
the open transaction and aborts any current zone modifications. CLI-Session2 is then able to perform
zone modifications. Therefore, the zone transaction locking mechanism works on a single switch from
the CLI perspective and there is no dangling transaction.
Dual-CLI sessions from different switches: If you start a CLI zone transaction on Switch1 and
started another CLI zone transaction on Switch2, when the zone transaction from Switch1 is
committed, the open zone transaction from Switch2 is aborted by Switch1. The following message is
posted on Switch2 at the time of zone commit from Switch1:
2014/01/09-21:45:26, [ZONE-1027], 3285, FID 128, INFO, switch, Zoning transaction
aborted Zone Config update Received
Zone does not form correctly
Some problems you might encounter when configuring zones include potential Fibre Channel router
issues. For a more detailed discussion of possible Fibre Channel issues, refer to the Fabric OS
Troubleshooting and Diagnostics Guide.
Some of the following problems may contribute to the zone not forming correctly:
• A Brocade VDX switch gets isolated when an RBridge ID matches the front domain ID or translate
domain ID in a mixed network. Refer to Recovering an isolated switch in a mixed FCoE fabric on
page 712.
• A "FID over-subscribed" message occurs during attempts to connect a backbone fabric to an edge
fabric. Refer to Recovering from FID oversubscription on page 713.
• A "FID conflict" message occurs during attempts to connect a backbone fabric to an edge fabric.
Refer to Recovering from Fabric ID conflict on page 713.
• Interfabric link (IFL) traffic does not flow over the intended link. Refer to Rebalancing traffic over
multiple IFLs on page 713.
• Zone merge was expected to be blocked following reboot, but was not blocked. Refer to Blocking
zone merge after reboot on page 714.
• Stale translate domains exist in an edge fabric. Refer to Removing stale translate domains on page
714.
Recovering an isolated switch in a mixed FCoE fabric
In an FCoE fabric that spans Network OS switches and Fabric OS switches, a Network OS switch with
an RBridge ID that matches a front phantom domain ID or translate phantom domain ID of a
connecting Fibre Channel router can become isolated.
FCoE connectivity across the Fibre Channel link between VCS Fabric clusters and Fibre Channel
routers uses domain IDs to identify switches. Within a VCS Fabric cluster, a domain ID is the same as
an RBridge ID. When you connect to a Fibre Channel router, the Fibre Channel router service in the
Fibre Channel fabric emulates virtual phantom Fibre Channel domains in the FCoE fabric. Each Fibre
Channel router-enabled switch emulates a single front phantom domain and each FC fabric is
represented by a translate phantom domain.
To recover an isolated Network OS switch, complete the following steps.
1. Disable all FC routers that connect to the VCS Fabric cluster.
2. Reboot the isolated Network OS switch.
3. Re-enable all disabled FC routers.
4. To prevent switch isolation, follow these steps on each FC router that attaches to a VCS Fabric
cluster.
Zone does not form correctly
712 Network OS Administrator’s Guide
53-1003225-04