Dell Brocade G620 Brocade 8.0.1 Fabric OS Troubleshooting and Diagnostics Guid - Page 73

ISL Trunking, Link issues

Page 73 highlights

ISL Trunking ∙ Link issues...73 ∙ Buffer credit issues...74 Link issues This section describes trunking link issues that can come up and recommended actions to take to correct the problems. You can use the islShow command to find the incompatible and segmented ISL links. To know the reason for incompatibility and segmentation, use the switchShow command on both ends of the ISL link. Symptom Probable cause and recommended action A link that is part of an ISL trunk failed. Use the trunkDebug 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 command: In the trunkDebug command, the following operands are used: ∙ 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. 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. ∙ Trunking is not supported in switch interoperability mode. ∙ Port trunking is disabled. ∙ The port is not an E_Port. ∙ The port is not 2 Gbps, 4 Gbps, 8 Gbps, 10Gbps, or 16Gbps. ∙ The port connects to a switch other than the one you want. Brocade Fabric OS Troubleshooting and Diagnostics Guide 53-1004126-01 73

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107

ISL Trunking
Link issues
.............................................................................................................................................................................................................................
73
Buffer credit issues
...........................................................................................................................................................................................................
74
Link issues
This section describes trunking link issues that can come up and recommended actions to take to correct the problems.
You can use the
islShow
command to find the incompatible and segmented ISL links. To know the reason for incompatibility and
segmentation, use the
switchShow
command on both ends of the ISL link.
Symptom
A link that is part of an ISL trunk failed.
Probable cause and recommended action
Use the trunkDebug 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
command:
In the
trunkDebug
command, the following operands are used:
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.
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.
Trunking is not supported in switch interoperability mode.
Port trunking is disabled.
The port is not an E_Port.
The port is not 2 Gbps, 4 Gbps, 8 Gbps, 10Gbps, or 16Gbps.
The port connects to a switch other than the one you want.
Brocade Fabric OS Troubleshooting and Diagnostics Guide
53-1004126-01
73