Dell Brocade G620 Brocade 8.0.1 Fabric OS Administratiors Guide - Page 504
Backbone fabric IDs
View all Dell Brocade G620 manuals
Add to My Manuals
Save this manual to your list of manuals |
Page 504 highlights
Using FC-FC Routing to Connect Fabrics Integrated Routing Ports on Demand license Capacity 128 If you are connecting to a Fabric OS and the Integrated Routing license is not installed, you must install it, as described in the Fabric OS Software Licensing Guide. The Integrated Routing license is not required if you are connecting to a Brocade Network OS fabric. For configuring EX_Ports on an ICL, both the Integrated Routing license and the ICL POD license are required. 4. If all switches in the fabric are running Fabric OS 7.3.0 or later, skip this step. If any switch is running a Fabric OS version earlier than 7.3.0, then enter the fddCfg --showall command to verify that the Fabric-Wide Consistency Policy is not in "strict" mode. When it is in strict mode, an ACL cannot support Fibre Channel routing in the fabric. switch:admin> fddcfg --showall Local Switch Configuration for all Databases:- DATABASE - Accept/Reject SCC - accept DCC - accept PWD - accept FCS - accept AUTH - accept Fabric-Wide Consistency Policy :- "SCC:S;DCC" If the Fabric-Wide Consistency Policy has the letter "S" in it in the edge fabric or the backbone fabric, do not connect the edge fabric to the FC router. The letter "S" (shown in the preceding sample output) indicates the policy is strict. The Fabric-Wide Consistency Policy must be tolerant before you can connect fabrics to the FC router. Refer to Configuring Security Policies on page 215 for information about configuring the Fabric-Wide Consistency Policy. 5. For 8-Gbps platforms, delete fabric mode Top Talker monitors, if they are configured. FC-FC routing and fabric mode Top Talker monitors are not concurrently supported on 8-Gbps platforms. FC-FC routing and fabric mode Top Talker monitors are concurrently supported only on the Brocade 6510 and 6520 switches, and on the Brocade DCX Backbone family with only 16-Gbps capable ports. Backbone fabric IDs If your configuration has only one backbone fabric, then you do not need to assign a backbone fabric ID because the backbone fabric ID in this situation defaults to a value of 128. The default backbone fabric ID is 1 if Virtual Fabrics is disabled. All switches in a backbone fabric must have the same backbone fabric ID. You can configure the backbone fabric ID using the fcrConfigure command. The backbone fabric ID must be unique from the perspective of every attached edge fabric. Fabric ID changes made on a switch are not propagated to other switches in the backbone fabric. The backbone fabric administrator is responsible for making sure that all switches in the backbone have the same fabric ID. Because fabric IDs are used heavily by the routing protocol between the Fibre Channel routers, using the wrong fabric ID can affect both edge-to-edge and backbone-to-edge routing. In addition to ensuring that the backbone fabric IDs are the same within the same backbone, you must make sure that when two different backbones are connected to the same edge fabric, the backbone fabric IDs are different, but the edge fabric ID should be the same. Configuration of two backbones with the same backbone fabric ID that are connected to the same edge is invalid. In this configuration, a RASLog message displays a warning about fabric ID overlap. When two backbone fabrics are not connected to the same edge, they can have the same backbone fabric ID. ATTENTION In a multi-switch backbone fabric, modification of the FID within the backbone fabric will cause disruption to local traffic. 504 Brocade Fabric OS Administration Guide, 8.0.1 53-1004111-02