8.3.17.0 - Force10 Networks
8.3.17.0 - Force10 Networks
8.3.17.0 - Force10 Networks
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
Figure 17-27. show hardware stack-unit stack-port Command Example<br />
FTOS# show hardware stack-unit 1 stack-port 33<br />
Input Statistics:<br />
7934 packets, 1049269 bytes<br />
0 64-byte pkts, 7793 over 64-byte pkts, 100 over 127-byte pkts<br />
0 over 255-byte pkts, 7 over 511-byte pkts, 34 over 1023-byte pkts<br />
70 Multicasts, 0 Broadcasts<br />
0 runts, 0 giants, 0 throttles<br />
0 CRC, 0 overrun, 0 discarded<br />
Output Statistics:<br />
438 packets, 270449 bytes, 0 underruns<br />
0 64-byte pkts, 57 over 64-byte pkts, 181 over 127-byte pkts<br />
54 over 255-byte pkts, 0 over 511-byte pkts, 146 over 1023-byte pkts<br />
72 Multicasts, 0 Broadcasts, 221 Unicasts<br />
0 throttles, 0 discarded, 0 collisions, 0 wredDrops<br />
Rate info (interval 45 seconds):<br />
Input 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate<br />
Output 00.00 Mbits/sec, 0 packets/sec, 0.00% of line-rate<br />
Failure Scenarios<br />
The following sections describe some of the common fault conditions that can happen in a switch stack and<br />
how they are resolved.<br />
Stack Member Fails<br />
Problem: A unit that is not the stack master fails in an operational stack.<br />
Resolution: If a stack member fails in a daisy chain topology, a split stack occurs. If a member unit fails in<br />
a ring topology, traffic is re-routed over existing stack links.<br />
The following syslog messages are generated when a member unit fails:<br />
FTOS#May 31 01:46:17: %STKUNIT3-M:CP %IPC-2-STATUS: target stack unit 4 not responding<br />
May 31 01:46:17: %STKUNIT3-M:CP %CHMGR-2-STACKUNIT_DOWN: Major alarm: Stack unit 4 down - IPC<br />
timeout<br />
FTOS#May 31 01:46:17: %STKUNIT3-M:CP %IFMGR-1-DEL_PORT: Removed port: Te 4/1-32,41-48, Fo 4/<br />
49,53<br />
FTOS#May 31 01:46:18: %STKUNIT5-S:CP %IFMGR-1-DEL_PORT: Removed port: Te 4/1-32,41-48, Fo 4/<br />
49,53<br />
Unplugged Stacking Cable<br />
Problem: A stacking cable is unplugged from a member switch. The stack loses half of its bandwidth from<br />
the disconnected switch.<br />
Resolution: Intra-stack traffic is re-routed on a another link using the redundant stacking port on the<br />
switch. A recalculation of control plane and data plane connections is performed.<br />
Stacking | 215