HP StorageWorks 1606 Brocade Fabric OS Troubleshooting and Diagnostics Guide v - Page 75

ISL Trunking Issues, In this Link issues

Page 75 highlights

ISL Trunking Issues Chapter 8 In this chapter •Link issues 61 •Buffer credit issues 62 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: where: port1 port2 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. 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 a 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. Fabric OS Troubleshoot and Diagnostics Guide 61 53-1001340-01

  • 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
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118

Fabric OS Troubleshoot and Diagnostics Guide
61
53-1001340-01
Chapter
8
ISL Trunking Issues
In this chapter
Link issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
61
Buffer credit issues . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . .
62
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:
where:
Example of a 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.
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.