Developers Guide

Fabric OS Troubleshooting and Diagnostics Guide 71
53-1003141-01
Chapter
8ISL Trunking
In this chapter
Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 71
Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 72
Link issues
This section describes trunking link issues that can come up and recommended actions to take to
correct the problems.
Symptom A link that is part of an ISL trunk failed.
Probable cause and recommended action
Use the trunkDebug port1 port2 command to troubleshoot the problem, as shown in the following
procedure.
1. Connect to the switch and log in as admin.
2. Enter the trunkDebug port1 port2 command:
In the trunkDebug command, the following operands are used::
Example of an unformed E_Port
This example shows that port 3 is not configured as an E_Port:
ecp:admin> trunkdebug 126, 127
port 126 is not E/EX port
port 127 is not E/EX port
Example of a formed E_Port
ecp:admin> trunkdebug 100, 101
port 100 and 101 connect to the switch 10:00:00:05:1e:34:02:45
The trunkDebug command displays the possible reason that two ports cannot be trunked. Possible
reasons are:
The switch does not support trunking.
A trunking license is required.
port1 Specify the area number or index of port 1. Use the switchShow command to
view the area or index numbers for a port. This operand is required.
port2 Specify the area number or index of port 2. Use the switchShow command to
view the area or index numbers for a port. This operand is required.