Segmented Fabrics - Brocade Communications Systems 8 Troubleshooting And Diagnostics Manual

TABLE 7
Test
portBeacon
portLoopbackTest
turboRamTest

Segmented fabrics

Fabric segmentation is generally caused by one of the following conditions:
•
•
•
•
•
•
•
•
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:
•
•
•
•
•
•
•
•
•
•
Fabric OS Troubleshooting and Diagnostics Guide
53-1001769-01
Switch component tests
Function
Sets port beaconing mode.
Performs a functional test of port N to N path. Verifies the functional components of the
switch.
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.
Incompatible fabric parameters (see
Incompatible zoning configuration (see
Domain ID conflict (see "Reconciling fabric parameters individually"
Fabric ID conflict (see Chapter 7, "Virtual
Incompatible security policies.
Incorrect fabric mode.
Incorrect policy distribution.
Incompatible software features.
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
ID".)
BB credit
PID format
"Reconciling fabric parameters individually"
Chapter 9, "Zone Issues").
Fabrics").
Appendix A, "Switch Type and Blade

Segmented fabrics

on page 38).
on page 38).
3
37