Stacking | 997
Troubleshoot an S-Series Stack
• Recover from Stack Link Flaps
• Recover from a Card Problem State on an S-Series Stack
• Recover from a Card Mismatch State on an S-Series Stack
Recover from Stack Link Flaps
S-Series Stack Link Integrity Monitoring enables units to monitor their own stack ports and disable any
stack port that flaps five times within 10 seconds. FTOS displays console messages the local and remote
members of a flapping link, and on the primary (master) and standby management units as KERN-2-INT
messages if the flapping port belongs to either of these units.
In the following example, a stack-port on the master flaps. The remote member, Member 2, displays a
console message, and the master and standby display KERN-2-INT messages.
To re-enable the downed stack-port, power cycle the offending unit.
--------------------------------------MANAGMENT UNIT-----------------------------------------
Error: Stack Port 50 has flapped 5 times within 10 seconds.Shutting down this st
ack port now.
Error: Please check the stack cable/module and power-cycle the stack.
10:55:20: %STKUNIT1-M:CP %KERN-2-INT: Error: Stack Port 50 has flapped 5 times w
ithin 10 seconds.Shutting down this stack port now.
10:55:20: %STKUNIT1-M:CP %KERN-2-INT: Error: Please check the stack cable/module
and power-cycle the stack.
---------------------------------------STANDBY UNIT------------------------------------------
10:55:18: %STKUNIT1-M:CP %KERN-2-INT: Error: Stack Port 50 has flapped 5 times within 10
seonds.Shutting down this stack port now.
10:55:18: %STKUNIT1-M:CP %KERN-2-INT: Error: Please check the stack cable/module
and power-cycle the stack.
----------------------------------------MEMBER 2---------------------------------------------
Error: Stack Port 51 has flapped 5 times within 10 seconds.Shutting down this stack port now.
Error: Please check the stack cable/module and power-cycle the stack.
Recover from a Card Problem State on an S-Series Stack
If a unit added to a stack has a different FTOS version, the unit does not come online and FTOS cites a card
problem error, as shown in Figure 47-12. To recover, disconnect the new unit from the stack, change the
FTOS version to match the stack, and then reconnect it to the stack, as shown in Figure 47-13.
Figure 47-12. Card Problem Error on an S-Series Stack - Different FTOS Versions
stack-1#show system brief
Stack MAC : 00:01:e8:8a:fd:6e
After the units are reloaded, the system reboots. The units come up as standalone units after the reboot completes.
Task Command Syntax Command Mode
To Next Page
Loading...
