IP Library Granted Patent US 7,672,227
Granted Patent B2
US 7,672,227 · App. 11/452,173 · Granted Mar 2, 2010

Loop prevention system and method in a stackable ethernet switch system

Assignee: Alcatel Lucent
View Patent ↗
Loading inventors, assignments & file history…
Monitor This Case
Get email alerts when status or documents change.
Order Certified Copies
Most orders are placed with the USPTO same day — all within 24 business hours.
Order via The Patent Place →
Pre-filled with this patent's details
Quick Facts
Patent No.
US 7,672,227
App. No.
11/452,173
Granted
Mar 2, 2010
Kind
B2
Abstract

A stackable Ethernet switch system (SESS) includes a number of stack switch elements in which loops are prevented. In one embodiment, logic is provided for monitoring control management traffic on a stacking port of a stack switch element of the SESS. Also included is logic, operable responsive to determining that there is a loss of control management traffic on a stacking port of a particular switch element of the SESS, for disabling user traffic data on that stacking port while keeping the control management traffic path open. The user data traffic on that stacking port of the particular switch element may be enabled upon detecting that the control management traffic on that stacking port has resumed.

Claims (30)

1. A loop prevention method operable in a stackable Ethernet switch system (SESS) having at least two stackable switch elements, wherein each switch element includes at least one stacking port and at least one core switch port such that said at least one core switch port is operable to be connected to a core switch, said loop prevention method comprising:

monitoring control management traffic on said at least one stacking port of each of said stackable switch elements;

upon determining that there is a loss of said control management traffic on a stacking port of a particular switch element of said SESS, disabling user data traffic on said stacking port of said particular switch element while continuing to keep a control/management traffic path open to avert a loop condition involving said user data traffic in said SESS; and

enabling said user data traffic on said stacking port of said particular switch element upon detecting that said control management traffic on said stacking port has resumed.

2. The loop prevention method as recited in claim 1 , wherein said loss of said control management traffic on said stacking port of said particular switch element is determined based on detecting that “Keep Alive” messages from a neighboring switch element connected to said particular switch element are not received after a period of time.

3. The loop prevention method as recited in claim 2 , wherein said period of time is predetermined.

4. The loop prevention method as recited in claim 2 , wherein said period of time is configurably variable.

5. The loop prevention method as recited in claim 1 , wherein said monitoring is performed after initial configuration of said SESS in which at least one of said core switch ports is rendered into a blocking state upon coupling to said core switch.

6. The loop prevention method as recited in claim 1 , wherein said control management traffic is monitored on each of said stackable switch elements by a stacking port traffic logic block associated with each stackable switch element.

7. A loop prevention apparatus operable in a stackable Ethernet switch system (SESS) having at least two stackable switch elements, wherein each switch element includes at least one stacking port and at least one core switch port such that said at least one core switch port is operable to be connected to a core switch, said loop prevention apparatus comprising:

means for monitoring control management traffic on said at least one stacking port of each of said stackable switch elements;

means, operable responsive to determining that there is a loss of said control management traffic on a stacking port of a particular switch element of said SESS, for disabling user data traffic on said stacking port of said particular switch element while continuing to keep a control/management traffic path open to avert a loop condition involving said user data traffic in said SESS; and

means for enabling said user data traffic on said stacking port of said particular switch element upon detecting that said control management traffic on said stacking port has resumed.

8. The loop prevention apparatus as recited in claim 7 , wherein said loss of said control management traffic on said stacking port of said particular switch element is determined based on detecting that “Keep Alive” messages from a neighboring switch element connected to said particular switch element are not received after a period of time.

9. The loop prevention apparatus as recited in claim 8 , wherein said period of time is predetermined.

10. The loop prevention apparatus as recited in claim 8 , wherein said period of time is configurably variable.

11. The loop prevention apparatus as recited in claim 8 , wherein said means for monitoring said control management traffic is operable after initial configuration of said SESS in which at least one of said core switch ports is rendered into a blocking state upon coupling to said core switch.

12. A stackable Ethernet switch system (SESS), comprising:

at least two stackable switch elements, wherein each switch element includes at least one stacking port and at least one core switch port such that said at least one core switch port is operable to be connected to a core switch;

logic implemented with each stackable switch element for monitoring control management traffic on said at least one stacking port of each of said stackable switch elements;

logic implemented with each stackable switch element, operable responsive to determining that there is a loss of said control management traffic on a stacking port of a particular switch element of said SESS, for disabling user data traffic on said stacking port of said particular switch element while continuing to keep a control/management traffic path open to avert a loop condition involving said user data traffic in said SESS; and

logic implemented with each stackable switch element for enabling said user data traffic on said stacking port of said particular switch element upon detecting that said control management traffic on said stacking port has resumed;

wherein the logic comprises at least one of a computer-readable medium, hardware, or firmware of each stackable switch element.

13. The stackable Ethernet switch system as recited in claim 12 , wherein said loss of said control management traffic on said stacking port of said particular switch element is determined based on detecting that “Keep Alive” messages from a neighboring switch element connected to said particular switch element are not received after a period of time.

14. The stackable Ethernet switch system as recited in claim 13 , wherein said period of time is predetermined.

15. The stackable Ethernet switch system as recited in claim 13 , wherein said period of time is configurably variable.

16. The stackable Ethernet switch system as recited in claim 12 , wherein said logic for monitoring said control management traffic is operable after initial configuration of said SESS in which at least one of said core switch ports is rendered into a blocking state upon coupling to said core switch.

17. The stackable Ethernet switch system as recited in claim 12 , wherein said stackable switch elements are arranged in a star configuration.

18. The stackable Ethernet switch system as recited in claim 12 , wherein said stackable switch elements are arranged in a ring configuration.

19. The stackable Ethernet switch system as recited in claim 12 , wherein said stackable switch elements are arranged in a chain configuration.

Assignments (2)
CHANGE OF NAME Recorded Jan 6, 2010
From: ALCATEL
To: ALCATEL LUCENT
Reel/Frame 023738/0246 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jul 3, 2006
From: SANTOSO, IGNATIUS D.; MAGRET, VINCENT
To: ALCATEL
Reel/Frame 017872/0170 →
Continuity (2)
Provisional Application 6069860500 · Jul 12, 2005
Related Publication 20070014234A1 · Jan 18, 2007