Segmented fabrics, Reconciling fabric parameters individually – Brocade Fabric OS Troubleshooting and Diagnostics Guide (Supporting Fabric OS v7.3.0) User Manual
Page 53
Fabric OS Troubleshooting and Diagnostics Guide
37
53-1003141-01
Segmented fabrics
3
Segmented fabrics
Fabric segmentation is generally caused by one of the following conditions:
•
Incompatible fabric parameters (refer to
“Reconciling fabric parameters individually”
•
Incompatible zoning configuration (refer to
)
•
Domain ID conflict (refer to
“Reconciling fabric parameters individually”
•
Fabric ID conflict (refer to
)
•
Incompatible security policies
•
Incorrect fabric mode
•
Incorrect policy distribution
•
Incompatible software features
There are a number of settings that control the overall behavior and operation of the fabric. Some
of these values, such as the domain ID, are assigned automatically by the fabric and can differ
from one switch to another in the fabric. Other parameters, such as the BB credit, can be changed
for specific applications or operating environments, but must be the same among all switches to
allow the formation of a fabric.
The following fabric parameters must be identical on each switch for a fabric to merge:
•
R_A_TOV
•
E_D_TOV
•
Data field size
•
Sequence level switching
•
Suppress class F traffic
•
Per-frame route priority
•
Long-distance fabric (not necessary on Brocade DCX, DCX-4S, 6505, 6510, 6520, and the
Brocade DCX 8510 Backbone families; for more information regarding these product types,
refer to
Appendix A, “Switch Type and Blade ID”
Reconciling fabric parameters individually
1. Log in to one of the segmented switches as admin.
2. Enter the configShow -pattern “fabric.ops” command.
3. Log in to another switch in the same fabric as admin.
4. Enter the configShow -pattern “fabric.ops” command.
5. Compare the two switch configurations line by line and look for differences. Do this by
comparing the two Telnet windows or by printing the configShow -pattern “fabric.ops” output.
Also, verify that the fabric parameter settings (refer to the list of fabric parameters in
) are the same for both switches.
6. Connect to the segmented switch after the discrepancy is identified.
7. Disable the switch by entering the switchDisable command.