HP Brocade 8/12c Fabric OS Troubleshooting and Diagnostics Guide v6.4.0 (53-10 - Page 51

Segmented fabrics

Get HP Brocade 8/12c PDF manuals and user guides View all HP Brocade 8/12c manuals
Add to My Manuals
Save this manual to your list of manuals

Page 51 highlights

Segmented fabrics 3 TABLE 7 Test Switch component tests Function portBeacon Sets port beaconing mode. portLoopbackTest Performs a functional test of port N to N path. Verifies the functional components of the switch. turboRamTest Verifies that the on chip SRAM located in the 4 and 8 Gbps ASIC is using the Turbo-Ram BIST circuitry. This allows the BIST controller to perform the SRAM write and read operations at a much faster rate. Segmented fabrics Fabric segmentation is generally caused by one of the following conditions: • Incompatible fabric parameters (see "Reconciling fabric parameters individually" on page 38). • Incompatible zoning configuration (see Chapter 9, "Zone Issues"). • Domain ID conflict (see "Reconciling fabric parameters individually" on page 38). • 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 Condor, GoldenEye, Condor2, or GoldenEye2 fabrics. For more information regarding these ASIC types, refer to Appendix A, "Switch Type and Blade ID".) • BB credit • PID format Fabric OS Troubleshooting and Diagnostics Guide 37 53-1001769-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
Fabric OS Troubleshooting and Diagnostics Guide
37
53-1001769-01
Segmented fabrics
3
Segmented fabrics
Fabric segmentation is generally caused by one of the following conditions:
•
Incompatible fabric parameters (see
“Reconciling fabric parameters individually”
on page 38).
•
Incompatible zoning configuration (see
Chapter 9, “Zone Issues”
).
•
Domain ID conflict (see
“Reconciling fabric parameters individually”
on page 38).
•
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 Condor, GoldenEye, Condor2, or GoldenEye2 fabrics.
For more information regarding these ASIC types, refer to
Appendix A, “Switch Type and Blade
ID”
.)
•
BB credit
•
PID format
TABLE 7
Switch component tests
Test
Function
portBeacon
Sets port beaconing mode.
portLoopbackTest
Performs a functional test of port N to N path. Verifies the functional components of the
switch.
turboRamTest
Verifies that the on chip SRAM located in the 4 and 8 Gbps ASIC is using the Turbo-Ram BIST
circuitry. This allows the BIST controller to perform the SRAM write and read operations at a
much faster rate.