Fabric OS Troubleshooting and Diagnostics Guide v6.4.0 (53-1001769-01, June 2010)

Fabric OS Troubleshooting and Diagnostics Guide 37

53-1001769-01

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.