Fabric OS 5.2.x administrator guide 297
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 or 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.
To determine if the negotiation was successfully completed
1.
Enter the
portCfgShow
command to display the port speed settings of all the ports.
2.
Enter the
switchShow
command to determine if the port has module light.
3.
Determine whether or not the port at 1Gig/sec completes by entering the
portCfgSpeed
command.
Then change the port speed to 2 Gig/sec. This should correct the negotiation by setting to one speed.
4.
Enter the
portLogShow
or
portLogDump
command.
5.
Check the events area of the output. The first example is 1 Gbit/sec and the second example is
2 Gbit/sec:
•
sn
indicates a speed negotiation.
•
NC
indicates negotiation complete.
•
01
or
02
indicate the speed that has been negotiated.
• If these fields do not appear, proceed to the
step 6
.
6.
Correct the negotiation by entering the
portCfgSpeed
[
slotnumber
/]
portnumber
,
speed_level
command if the fields in
step 5
do not appear.
To check for a loop initialization failure
1.
Verify the port is an L_Port.
a.
Enter the
switchShow
command.
b.
Check the comment field of the output to verify that the switch port indicates an L_Port. If a loop
device is connected to the switch, the switch port must be initialized as an L_Port.
c.
Check to ensure that the port state is online; otherwise, check for link failures.
2.
Verify the loop initialization
if
the port is not an L_port.
a.
Enter the
portLogShow
or
portLogDump
command.
b.
Check argument number four for the
LISA frame
(0x11050100).
The
LISA frame
indicates that the loop initialization is complete.
14:38:51.976 SPEE sn <Port#> NC 00000001,00000000,00000001
14:39:39.227 SPEE sn <Port#> NC 00000002,00000000,00000001
switch:admin>
portlogdumpport 4
time task event port cmd args
-------------------------------------------------
11:40:02.078 PORT Rx3 23 20 22000000,00000000,ffffffff,11050100
Received LISA frame
Summary of Contents for AE370A - Brocade 4Gb SAN Switch 4/12
Page 18: ...18 ...
Page 82: ...82 Managing user accounts ...
Page 102: ...102 Configuring standard security features ...
Page 126: ...126 Maintaining configurations ...
Page 198: ...198 Routing traffic ...
Page 238: ...238 Using the FC FC routing service ...
Page 260: ...260 Administering FICON fabrics ...
Page 280: ...280 Working with diagnostic features ...
Page 332: ...332 Administering Extended Fabrics ...
Page 414: ...398 Configuring the PID format ...
Page 420: ...404 Configuring interoperability mode ...
Page 426: ...410 Understanding legacy password behaviour ...
Page 442: ...426 ...
Page 444: ......
Page 447: ......