Deployment Guide

3. Enter the licenseShow command to verify that the Integrated Routing license is installed.
switch:admin> licenseshow
S9bddb9SQbTAceeC:
Fabric license
bzbzRcbcSc0c0SY:
Remote Fabric license
RyeSzRScycazfT0G:
Integrated Routing license
If you are connecting to a Fabric OS or M-EOS fabric 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 v7.3.0 or higher, skip this step. If any switch is
running a Fabric OS version lower than v7.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 209 for
information about configuring the Fabric-Wide Consistency Policy.
5. For 8-Gbps platforms, delete fabric mode Top Talker monitors, if they are configured. Refer to
Deleting all fabric mode Top Talker monitors on page 507 for instructions.
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. Rather, 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.
Backbone fabric IDs
Fabric OS Administrators Guide 545
53-1003130-01