Users Guide

-- Stack-unit Failover Record --
------------------------------------------------
Failover Count: 0
Last failover timestamp: None
Last failover Reason: None
Last failover type: None
-- Last Data Block Sync Record: --
------------------------------------------------
Stack Unit Config: succeeded Feb 13 2013 15:13:52
Start-up Config: succeeded Feb 13 2013 15:13:52
Runtime Event Log: succeeded Feb 13 2013 15:13:52
Running Config: succeeded Feb 13 2013 15:13:52
ACL Mgr: succeeded Feb 13 2013 15:13:52
LACP: no block sync done
STP: no block sync done
SPAN: no block sync done
Example of the show hardware stack-unit stack port Command
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
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.
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
Stacking 1041