User Manual

196 Troubleshooting
Correcting link failures
A link failure occurs when a server or storage is connected to a switch, but the link between the
server/storage and the switch does not come up. This prevents the server/storage from communicating
through the switch.
If the switchshow command and/or the LEDs indicate that the link has not come up properly, use one or
more of the following procedures.
To determine if the negotiation was successfully completed:
The port negotiates the link speed with the opposite side. The negotiation usually completes in 1-2
seconds; however, sometimes the speed negotiation fails.
NOTE: Skip this procedure if the port speed is set to a static speed through the portCfgSpeed
command.
1. Issue the switchshow command to determine the speed of the device.
2. Issue the portLogShow or portLogDump command.
3. Check the events area of the output. The first example is 1 Gbps and the second example is 2 Gbps:
•The sn field indicates a speed negotiation.
•The NC field indicates Negotiation Complete.
•The 01 or 02 fields indicate the speed that has been negotiated.
If these fields do not appear, proceed to the step 4.
4. Correct the negotiation by entering the portCfgSpeed [slotnumber/]portnumber,
speed_level command if the fields in Table 3 do not appear.
turboramtest Verifies that the on chip SRAM located in the 2 Gbps ASIC is using the
Turbo-Ram BIST circuitry. These same SRAMs are tested by
portregtest and sramretentiontest using PCI operations, but
for this test the BIST controller is able to perform the SRAM write and
read operations at a much faster rate.
statstest Verifies that the ASIC statistics counter logic.
Related Switch Test Command:
itemlist Restricts the items to be tested to a smaller set of parameter values that
you pass to the switch.
Table 33 Switch component tests (continued)
Test Function
14:38:51.976 SPEE sn <Port#> NC 00000001,00000000,00000001
14:39:39.227 SPEE sn <Port#> NC 00000002,00000000,00000001