IP Library Granted Patent US 8,117,336
Granted Patent B2
US 8,117,336 · App. 11/809,224 · Granted Feb 14, 2012

Methods, systems, and computer program products for providing accidental stack join protection

Assignee: Extreme Networks, Inc.
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 8,117,336
App. No.
11/809,224
Filed
May 31, 2007
Granted
Feb 14, 2012
Kind
B2
Art Unit
2491
USPC
709/238
Abstract

The subject matter described herein includes methods and systems for providing accidental stack join protection. According to one embodiment, a method includes connecting stacking ports of a first switch that is a member of a first stack and a second switch that is a member of a second stack and thereby joining the first and second stacks. The configurations of the first stack and of the second stack are detected and it is determined whether the detected configurations indicate a configuration mismatch between the first and second stacks. In response to determining that the detected configurations relate to a mismatch, the automatic joining of the first and second stacks is inhibited and the first and second stacks are allowed to continue switching traffic with their existing configurations.

Claims (28)

1. A method for providing accidental stack join protection, the method comprising:

connecting stacking ports of a first switch that is a member of a first stack and a second switch that is a member of a second stack and thereby connecting the first and second stacks;

detecting configurations of the first stack and of the second stack;

determining whether the detected configurations indicate a stack configuration mismatch which indicates an accidental connection between the first and second stacks, wherein an accidental connection is an unintentional connection between the first and second stacks made by a user;

wherein determining whether the detected configurations indicate a stack configuration mismatch includes determining whether the first and second stacks are operational, whether a slot identifier is duplicated between the first and second stacks, and whether a stack identifier associated with the first stack is different than a stack identifier associated with the second stack; and

in response to determining that the detected configurations indicate a mismatch which indicates an accidental connection, inhibiting automatic joining of the first and second stacks and allowing the first and second stacks to continue switching traffic with their existing configurations, wherein inhibiting automatic joining of the first and second stacks includes blocking the transmission of data packets and management packets not associated with stacking control and status between the first and second switches and allowing the transmission of packets associated with stacking control and status between the first and second switches, and wherein allowing the first and second stacks to continue switching traffic with their existing configurations includes allowing transmission and reception of network traffic using at least one non-stacking port at one or more of the first and second stacks.

2. The method of claim 1 comprising in response to determining that the detected configurations do not indicate a mismatch, automatically joining the first and second stacks.

3. The method of claim 1 wherein connecting the first and second stacks includes connecting at least one of two single-member stacks, two multi-member stacks, and a single-member stack and a multi-member stack.

4. The method of claim 1 wherein detecting configurations of the first and second stacks includes, for each switch, detecting at least one of a stack identifier, a slot identifier, and an operational status indicator.

5. The method of claim 1 wherein the data packets and management packets not associated with stacking control and status include at least one of open shortest path first (OSPF) packets, border gateway protocol (BGP) packets, spanning tree protocol packets, hardware control commands, software state synchronization packets, and packets associated with configuring the processing of data packets.

6. The method of claim 1 wherein the packets associated with stacking control and status include packets used to change stacking specific configurations, packets used for determining the topology of the stack, and packets used for determining the status of the stack.

7. The method of claim 6 wherein the packets associated with stacking control and status include packets for configuring at least one of a slot identifier, a stack identifier, and an operational status.

8. A system for providing accidental stack join protection, the system comprising:

a first switch that includes a stacking port and is a member of a first stack;

a second switch that includes a stacking port and is a member of a second stack, where the stacking port of the second switch is connected to the stacking port of the first switch; and

a stack joining manager for detecting configurations of the first and second stacks, determining whether the detected configurations indicate a stack configuration mismatch which indicates an accidental connection between the first and second stacks, wherein an accidental connection is an unintentional connection between the first and second stacks made by a user and wherein the stack joining manager is configured to determine whether the first and second stacks are operational as indicated by the operational status indictors and at least one of a slot identifier is duplicated between the first and second stack and the stack identifier of the first stack is different than the stack identifier of the second stack, and

in response to determining that the detected configurations indicate a mismatch which indicates an accidental connection, inhibiting automatic joining of the first and second stacks and allowing the first and second stacks to continue switching traffic with their existing configurations, wherein inhibiting automatic joining of the first and second stacks includes blocking the transmission of data packets and management packets not associated with stacking control and status between the first and second switches and allowing the transmission of packets associated with stacking control and status between the first and second switches, and wherein allowing the first and second stacks to continue switching traffic with their existing configurations includes allowing transmission and reception of network traffic using at least one non-stacking port at one or more of the first and second stacks.

9. The system of claim 8 wherein the stack joining manager is configured to, in response to determining that the detected configurations do not indicate a mismatch, automatically join the first and second stacks.

10. The system of claim 8 wherein the first and second stacks include at least one of two single-member stacks, two multi-member stacks, and a single-member stack and a multi-member stack.

11. The system of claim 8 wherein the stack joining manager is configured to detect at least one of a stack identifier, a slot identifier, and an operational status indicator.

12. The system of claim 8 wherein the data packets and management packets not associated with stacking control and status include at least one of open shortest path first (OSPF) packets, border gateway protocol (BGP) packets, spanning tree protocol packets, hardware control commands, software state synchronization packets, and packets associated with configuring the processing of data packets.

13. The system of claim 8 wherein the packets associated with stacking control and status include packets used to change stacking specific configurations, packets used for determining the topology of the stack, and packets used for determining the status of the stack.

14. The system of claim 13 wherein the packets associated with stacking control and status include packets for configuring at least one of a slot identifier, a stack identifier, and an operational status.

15. A computer program product comprising computer-executable instructions embodied in a non-transitory computer-readable medium for performing steps comprising:

connecting stacking ports of a first switch that is a member of a first stack and a second switch that is a member of a second stack and thereby connecting the first and second stacks;

detecting configurations of the first switch and of the second switch;

determining whether the detected configurations indicate a stack configuration mismatch which indicates an accidental connection between the first and second stacks, wherein an accidental connection is an unintentional connection between the first and second stacks made by a user wherein determining whether the detected configurations indicate a stack configuration mismatch includes determining whether the first and second stacks are operational, whether a slot identifier is duplicated between the first and second stacks, and whether a stack identifier associated with the first stack is different than a stack identifier associated with the second stack; and

in response to determining that the detected configurations indicate a mismatch which indicates an accidental connection, inhibiting automatic joining of the first and second stacks and allowing the first and second stacks to continue switching traffic with their existing configurations, wherein inhibiting automatic joining of the first and second stacks includes blocking the transmission of data packets and management packets not associated with stacking control and status between the first and second switches and allowing the transmission of packets associated with stacking control and status between the first and second switches, and wherein allowing the first and second stacks to continue switching traffic with their existing configurations includes allowing transmission and reception of network traffic using at least one non-stacking port at one or more of the first and second stacks.

Assignments (10)
RELEASE OF PATENT AND TRADEMARK SECURITY INTEREST AT REEL/FRAME NO. 46050/0546 Recorded Jul 30, 2026
From: BANK OF MONTREAL, AS AGENT
To: EXTREME NETWORKS, INC.
Reel/Frame 076081/0088 →
SECURITY INTEREST Recorded Jul 29, 2026
From: EXTREME NETWORKS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 076078/0590 →
AMENDED SECURITY AGREEMENT Recorded Aug 18, 2023
From: EXTREME NETWORKS, INC.; AEROHIVE NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 064782/0971 →
SECURITY INTEREST Recorded May 1, 2018
From: EXTREME NETWORKS, INC.
To: BANK OF MONTREAL
Reel/Frame 046050/0546 →
RELEASE OF SECURITY INTEREST Recorded May 1, 2018
From: SILICON VALLEY BANK
To: EXTREME NETWORKS, INC.
Reel/Frame 046051/0775 →
THIRD AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 044639/0300 →
SECOND AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Jul 14, 2017
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 043200/0614 →
AMENDED AND RESTATED PATENT AND TRADEMARK SECURITY AGREEMENT Recorded Oct 31, 2016
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 040521/0762 →
SECURITY AGREEMENT Recorded Jul 27, 2015
From: EXTREME NETWORKS, INC.
To: SILICON VALLEY BANK
Reel/Frame 036189/0284 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jun 25, 2007
From: DERNOSEK, LOUIS A.; GROSSER, DONALD B.; MROZ, MICHAEL D.; RICHARDSON, HOOD L. JR.
To: EXTREME NETWORKS, INC.
Reel/Frame 019475/0544 →
Continuity (1)
Related Publication 20080301319A1 · Dec 4, 2008