Dell Brocade 6520 Fabric OS Troubleshooting and Diagnostics Guide v7.1.0 - Page 53

Reconciling fabric parameters individually, Zoning, Virtual Fabrics, Appendix

Get Dell Brocade 6520 PDF manuals and user guides View all Dell Brocade 6520 manuals
Add to My Manuals
Save this manual to your list of manuals

Page 53 highlights

Segmented fabrics 3 • Incompatible zoning configuration (see Chapter 9, "Zoning"). • Domain ID conflict (see "Reconciling fabric parameters individually" on page 37). • Fabric ID conflict (see Chapter 7, "Virtual Fabrics"). • 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 • Disable device probing • 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 above list) 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. 8. Enter the configure command to edit the appropriate fabric parameters for the segmented switch. 9. Enable the switch by entering the switchEnable command. Fabric OS Troubleshooting and Diagnostics Guide 37 53-1002751-01

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
Fabric OS Troubleshooting and Diagnostics Guide
37
53-1002751-01
Segmented fabrics
3
•
Incompatible zoning configuration (see
Chapter 9, “Zoning”
).
•
Domain ID conflict (see
“Reconciling fabric parameters individually”
on page 37).
•
Fabric ID conflict (see
Chapter 7, “Virtual Fabrics”
).
•
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
•
Disable device probing
•
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 above list) 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.
8.
Enter the
configure
command to edit the appropriate fabric parameters for the segmented
switch.
9.
Enable the switch by entering the
switchEnable
command.