Setup Guide

Testing components to and from the HBA
1. Connect to the switch and log in as admin.
2. Enter the portTest command (refer to the Fabric OS Command Reference for information on the command options).
Refer to Table 7 for a list of additional tests that can be used to determine the switch components that are not functioning
properly. Refer to the Fabric OS Command Reference for additional command information.
The HBA bcu fcDiag --linkbeacon command can be used to beacon a target port on the switch. These commands work only in
Brocade-branded or qLogic BR-series adapters.
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 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 (refer to Reconciling fabric parameters individually on page 48)
∙ Incompatible zoning configuration (refer to Zoning on page 75)
∙ Domain ID conflict (refer to Reconciling fabric parameters individually on page 48)
∙ Fabric ID conflict (refer to Virtual Fabrics on page 67)
∙ 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.
In general, the following fabric parameters must be identical on each switch for fabrics to merge. However, the following table
summarizes the scenarios when the fabrics are not segmented (but merged) even when these fabric parameters are not identical.
TABLE 8
Segmented fabric scenarios
Fabric Parameter LISL XISL ISL (Fabric OS 7.3.0 or
later)
ISL (Fabric OS 7.1.0 or
earlier)
Domain ID Not segmented (merged) Segmented Segmented Segmented
R_A_TOV Segmented Segmented Segmented Segmented
E_D_TOV Segmented Segmented Segmented Segmented
Connectivity
Brocade Fabric OS Troubleshooting and Diagnostics Guide
53-1004126-01 47