Reference Guide

Stacking | 879
Figure 48-18. show hardware stack-unit stack-port Command Example
Failure Scenarios
The following sections describe some of the common fault conditions that can happen in a switch stack and
how they are resolved.
Stack Member Fails
Problem: A unit that is not the stack master fails in an operational stack.
Resolution: If a stack member fails in a daisy chain topology, a split stack occurs. If a member unit fails in
a ring topology, traffic is re-routed over existing stack links.
The following syslog messages are generated when a member unit fails:
Dell#Feb 13 15:26:18: %STKUNIT4-M:CP %IPC-2-STATUS: target stack unit 2 not responding
Feb 13 15:26:19: %STKUNIT4-M:CP %CHMGR-2-STACKUNIT_DOWN: Major alarm: Stack unit 2 down - IPC
timeout
Feb 13 15:26:19: %STKUNIT4-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Te 2/1
Feb 13 15:26:19: %STKUNIT4-M:CP %IFMGR-5-OSTATE_DN: Changed interface state to down: Po 1
Feb 13 15:26:19: %STKUNIT4-M:CP %IFMGR-1-DEL_PORT: Removed port: Te 2/0-11,20-23, Fo 2/
48,52,56,60,
Feb 13 15:26:19: %STKUNIT3-S:CP %IFMGR-1-DEL_PORT: Removed port: Te 2/0-11,20-23, Fo 2/
48,52,56,60,
Dell# show hardware stack-unit 1 stack-port 53
Dell#show hardware stack-unit 4 stack-port 4
Input Statistics:
199 packets, 52878 bytes
0 64-byte pkts, 14 over 64-byte pkts, 150 over 127-byte pkts
13 over 255-byte pkts, 11 over 511-byte pkts, 11 over 1023-byte pkts
0 Multicasts, 0 Broadcasts
0 runts, 0 giants, 0 throttles
0 CRC, 0 overrun, 0 discarded
Output Statistics:
50 packets, 31212 bytes, 0 underruns
0 64-byte pkts, 11 over 64-byte pkts, 9 over 127-byte pkts
0 over 255-byte pkts, 15 over 511-byte pkts, 15 over 1023-byte pkts
0 Multicasts, 0 Broadcasts, 50 Unicasts
0 throttles, 0 discarded, 0 collisions, 0 wredDrops
Rate info (interval 30 seconds):
Input 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate
Output 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate