Recover from Stack Link Flaps
Stack link integrity monitoring enables units to monitor their own stack ports and disable any stack port that flaps five times within 10
seconds.
Dell Networking OS displays console messages for 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.
Example of Console Messages About Flapping Link
---------------------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 a Stack
If a unit added to a stack has a different Dell Networking OS version, the unit does not come online and Dell Networking OS cites a card
problem error.
To recover, disconnect the new unit from the stack, change the Dell Networking OS version to match the stack, and then reconnect it to
the stack.
Example of Card Problem Error on a Stack - Different Dell Networking OS Versions
stack-1#show system brief
Stack MAC : 00:01:e8:8a:fd:6e
Reload Type : normal-reload [Next boot : normal-reload]
-- Stack Info --
Unit UnitType Status ReqTyp CurTyp Version Ports
-----------------------------------------------------------
0 Standby card problem S4810 unknown 64
1 Management online S4810 S4810 8-3-10-223 64
2 Member not present
3 Member not present
4 Member not present
5 Member not present
6 Member not present
7 Member not present
8 Member not present
9 Member not present
10 Member not present
11 Member not present
820
Stacking
Summary of Contents for S3048-ON
Page 1: ...Dell Configuration Guide for the S3048 ON System 9 11 2 5 ...
Page 137: ...0 Gi 1 1 Gi 1 2 rx Flow N A N A 0 0 No N A N A yes Access Control Lists ACLs 137 ...
Page 142: ...Figure 10 BFD Three Way Handshake State Changes 142 Bidirectional Forwarding Detection BFD ...
Page 241: ...Dell Control Plane Policing CoPP 241 ...
Page 287: ... RPM Synchronization GARP VLAN Registration Protocol GVRP 287 ...
Page 428: ...Figure 53 Inspecting the LAG Configuration 428 Link Aggregation Control Protocol LACP ...
Page 477: ...Figure 73 Configuring Interfaces for MSDP Multicast Source Discovery Protocol MSDP 477 ...
Page 478: ...Figure 74 Configuring OSPF and BGP for MSDP 478 Multicast Source Discovery Protocol MSDP ...
Page 483: ...Figure 77 MSDP Default Peer Scenario 2 Multicast Source Discovery Protocol MSDP 483 ...
Page 484: ...Figure 78 MSDP Default Peer Scenario 3 484 Multicast Source Discovery Protocol MSDP ...
Page 745: ...Figure 104 Single and Double Tag TPID Match Service Provider Bridging 745 ...
Page 746: ...Figure 105 Single and Double Tag First byte TPID Match 746 Service Provider Bridging ...