Advanced Traffic Management Guide K/KA/KB.15.15

Example 211 Viewing show tech output
Port Number : 1 State : Available
Last Event : Available Start Req : 1
NE Present : 1 HPID Good : 1
HPID Fails : 0 FE Present : 1
Rem Dev Rdy : 1
ESSI Link : 1 ESSI Good : 1
ESSI Fails : 0 ESSI TX En : 1
ICL Good : 1 ICL Enabled : 1
LP Local RDY: 1 LP Rem RDY : 1
LP DONE : 1 ICL FailCnt : 0 (10 second interval)
ICL FailCnt : 0 (10 minute interval)
NE Presence HW : 1
FE Presence HW : 1
Rem Dev Rdy HW : 1
Local Dev Rdy HW : 1
Asserted NE Presence HW : 1
Asserted FE Presence HW : 1
Asserted Rem Dev Rdy HW : 1
Phy Frame Errors : 0
Invalid Status Errors : 0
Invalid Packet Type Errors : 0
Incomplete Packet Errors : 0
Checksum Errors : 0
ESSI Flow Out This Port (HW) : 0x2
Example 212 Viewing trace information for a port
Trace for Port 1
[ 0] [Info ] Start Request Received (Empty) [0]
[ 1] [Info ] Waiting for Stack Module Good (Empty) [0]
[ 2] [Info ] Stack Module Good Received (Empty) [0]
[ 3] [Info ] Cable Insertion Detected (Empty) [1]
[ 4] [Info ] Re-enable NE Present Int [487]
[ 5] [Info ] Starting Cable HPID Validation (Inserted) [488]
[ 6] [Info ] Skipping Cable HPID Validation (Inserted) [488]
[ 7] [Info ] Far End Insertion Detected (Valid) [988]
[ 8] [Info ] Polling for ESSI phy link up (Valid) [988]
[ 9] [Info ] ESSI Link Up [9988]
[10] [Info ] ESSI Link Good (Valid) [9988]
[11] [Info ] ESSI Linked at 9988 ms [9988]
[12] [Info ] Remote Device Ready Detected (Valid) [10898]
[13] [Info ] ICL Change Request Enable (Cable Ready) [10898]
[14] [Info ] Detected Remote Ready Drop. (Cable Ready) [12651]
[15] [Info ] ICL Good. Behind. Partner ready. (Cable Ready) [12988]
[16] [Info ] ICL GOOD received at 2091 ms [12988]
[17] [Info ] Partner LP ready. (Cable Ready) [13980]
[18] [Info ] Set Device Ready. (Cable Ready) [13987]
[19] [Info ] ESSI Link Verfied [13988]
[20] [Info ] ESSI Able to Transmit (Cable Ready) [13988]
[21] [Info ] ESSI Verified at 3091 ms [13988]
[22] [Info ] Cable Available (Available) [13988]
Troubleshooting when a switch crashes and reboots
Although the switch software is highly reliable, a switch in the stack can experience a software
issue that results in the crash and reboot of that switch. This crash can happen in the software
running on the CPU in the management CPU or on the software running on the CPUs in the
interfaces. In either case, crash information is generated and the switch is rebooted.
The resiliency of the stack is determined by the stacking topology, however, in all cases, the
interfaces/ports on the switch that crashes are brought down and a reboot of that switch occurs.
316 Stack management for the 3800 switches