Switch Cannot Attach To The Fabric; Verifying Fabric Binding Violations Using Fabric Manager - Cisco 9134 - MDS Multilayer Fabric Switch Troubleshooting Manual

Fabric Binding Issues
S e n d d o c u m e n t a t i o n c o m m e n t s t o m d s f e e d b a c k - d o c @ c i s c o . c o m

Switch Cannot Attach to the Fabric

Symptom
Table 19-9 Switch Cannot Attach to the Fabric
Symptom Possible Cause
Switch cannot attach Fabric binding not activated on local
to the fabric. switch. (It is activated on only one side
of the ISL).
sWWN not present in fabric binding
database.
Fabric binding database has sWWN
with a different domain ID configured.
The local active fabric binding database
is different from the other switches.
Switch blocked because of fabric
binding violation.

Verifying Fabric Binding Violations Using Fabric Manager

To verify fabric binding violations using Fabric Manager, follow these steps:
Step 1 Choose Fabricxx > VSANxx > Fabric Binding and select the Violations tab to search for an interface
that is shut down.
Optionally, remove the switch, choose Switches > Interfaces > FC Physical, and select up from the
Step 2
Admin Status drop-down menu to bring the port back online. Click Apply Changes.
Note
Cisco MDS 9000 Family Troubleshooting Guide, Release 3.x
19-16
Switch cannot attach to the fabric.
You may need to set the interface down and then up to bring it back online.
Chapter 19 Troubleshooting FC-SP, Port Security, and Fabric Binding
Solution
Activate fabric binding. Choose Fabricxx > VSANxx >
Fabric Binding and select the Actions tab, select activate
from the Action drop-down menu, and click Apply
Changes to copy the configure database to the active
database and activate fabric binding.
Or use the fabric-binding activate CLI command.
Add sWWN to fabric binding database. See the
Fabric Binding Violations Using Fabric Manager" section
on page 19-16 or the "Verifying Fabric Binding Violations
Using the CLI" section on page 19-17
For non-FICON VSANs, you can remove the domain ID
from the fabric binding database.
Or update the domain ID in the fabric binding database (for
FICON or NON-FICON VSANs).
See the "Verifying Fabric Binding Violations Using Fabric
Manager" section on page 19-16
Binding Violations Using the CLI" section on page 19-17
Update the fabric binding database and reactivate it. See
the "Verifying Fabric Binding Violations Using Fabric
Manager" section on page 19-16
Binding Violations Using the CLI" section on page 19-17
Remove the device causing the fabric binding violation or
add that device to the database. See the
Binding Violations Using Fabric Manager" section on
page 19-16 or the "Verifying Fabric Binding Violations
Using the CLI" section on page
"Verifying
or the "Verifying Fabric
or the "Verifying Fabric
"Verifying Fabric
19-17.
OL-9285-05