IP Library Granted Patent US 10,838,832
Granted Patent B2
US 10,838,832 · App. 16/046,109 · Granted Nov 17, 2020

Cluster failover to avoid network partitioning

Inventors: Sudip Ghosal (Saratoga, CA); Yi-Nan Lee (Milpitas, CA)
Assignee: ARRIS Enterprises LLC
G06F11/2023H04L41/0686H04L41/0856G06F2201/805G06F2201/82
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 10,838,832
App. No.
16/046,109
Granted
Nov 17, 2020
Kind
B2
Abstract

During a synchronization technique, states of a primary cluster in the computer system with multiple primary controllers that provide controllers for access points and a backup cluster in the computer system with multiple backup controllers that independently provide controllers for the access points may be dynamically synchronized. In particular the primary cluster may receive configuration requests with configuration information for the access points on an input node of the primary cluster. In response, the primary cluster may store the configuration requests in a replay queue in the computer system. Then, the primary cluster may playback the configuration requests in the replay queue for the backup cluster to synchronize the states of the primary cluster and the backup cluster. For example, the configuration requests may be played back within a time interval associated with a service level agreement of a service provider of a service for the access points.

Claims (51)

1. A computer system, comprising:

a primary cluster with multiple primary controllers and a replay queue, wherein the primary cluster is configured to communicate with access points and a backup cluster; and

the backup cluster with multiple backup controllers coupled to the primary cluster, wherein the backup cluster is configured to communicate with the access points and the primary cluster, wherein the primary controllers and the backup controllers are independently configured to implement controllers for the access points, and wherein the primary cluster is configured to:

receive configuration requests with configuration information for the access points on an input node of the primary cluster;

store the configuration requests in the replay queue; and

playback the configuration requests in the replay queue for the backup cluster to synchronize states of the primary cluster and the backup cluster, wherein the configuration requests are played back in order for the backup cluster.

2. The computer system of claim 1 , wherein the access points are divided into zones and a given zone is associated with a given primary controller and a given backup controller.

3. The computer system of claim 2 , wherein the zones are based on one or more of: geographic locations of the access points, and software versions of the access points.

4. The computer system of claim 2 , wherein the computer system is configured to provide network addresses of the given primary controller and the given backup controller to an output node of the computer system for a subset of the access points in the given zone.

5. The computer system of claim 2 , wherein, when the given primary controller fails, the primary cluster is configured to:

receive requests associated with a subset of the access points in the given zone on the input node of the primary cluster; and

in response to the requests, provide, using at least another primary controller, failover coverage for the subset of the access points.

6. The computer system of claim 5 , wherein the requests are independently received from the subset of the access points.

7. The computer system of claim 5 , wherein the primary cluster is configured to select the other primary controller based on loading of the primary controllers.

8. The computer system of claim 5 , wherein, when the other primary controller subsequently fails, the backup cluster is configured to:

receive additional requests associated with the subset of the access points on an input node of the backup cluster; and

in response to the additional requests, provide, using at least the given backup controller, failover coverage for the subset of the access points.

9. The computer system of claim 8 , wherein the additional requests are independently received from the subset of the access points.

10. The computer system of claim 1 , wherein the configuration requests are played back within a time interval.

11. The computer system of claim 10 , wherein the time interval is associated with a service level agreement of a service provider of a service for the access points.

12. The computer system of claim 1 , wherein, when a link between the primary cluster and the backup cluster fails, the primary cluster is configured to:

store additional configuration requests that are subsequently received in the replay queue; and

playback the additional configuration requests in the replay queue for the backup cluster when the link is restored; and

wherein the additional configuration requests are played back in order for the backup cluster.

13. A non-transitory computer-readable storage medium for use in conjunction with a computer system that includes a primary cluster with multiple primary controllers and a backup cluster with multiple backup controllers, and the primary controllers and the backup controllers are independently configured to implement controllers for access points, the computer-readable storage medium storing program instructions that, when executed by the computer system, causes the computer system to perform one or more operations comprising:

receiving configuration requests for the primary cluster with configuration information for the access points;

storing the configuration requests in a replay queue; and

playing back the configuration requests in the replay queue for the backup cluster to synchronize states of the primary cluster and the backup cluster, wherein the configuration requests are played back in order for the backup cluster.

14. The computer-readable storage medium of claim 13 , wherein the access points are divided into zones and a given zone is associated with a given primary controller and a given backup controller.

15. The computer-readable storage medium of claim 14 , wherein, when the given primary controller fails, the one or more operations comprise:

receiving requests associated with a subset of the access points in the given zone; and

in response to the requests, providing, using at least another primary controller, failover coverage for the subset of the access points.

16. The computer-readable storage medium of claim 15 , wherein, when the other primary controller subsequently fails, the one or more operations comprise:

receiving additional requests associated with the subset of the access points; and

in response to the additional requests, providing, using at least the given backup controller, failover coverage for the subset of the access points.

17. The computer-readable storage medium of claim 13 , wherein, when a link between the primary cluster and the backup cluster fails, the one or more operations comprise:

storing additional configuration requests that are subsequently received in the replay queue; and

playing back the additional configuration requests in the replay queue for the backup cluster when the link is restored; and

wherein the additional configuration requests are played back in order for the backup cluster.

18. A method for synchronizing states of a primary cluster with multiple primary controllers and a backup cluster with multiple backup controllers, wherein the primary controllers and the backup controllers independently implement controllers for access points, comprising:

by a computer system:

receiving configuration requests for the primary cluster with configuration information for the access points;

storing the configuration requests in a replay queue; and

playing back the configuration requests in the replay queue for the backup cluster to synchronize states of the primary cluster and the backup cluster, wherein the configuration requests are played back in order for the backup cluster.

19. The method of claim 18 , wherein the access points are divided into zones and a given zone is associated with a given primary controller and a given backup controller; and

wherein, when the given primary controller fails, the method comprises:

receiving requests associated with a subset of the access points in the given zone; and

in response to the requests, providing, using at least another primary controller, failover coverage for the subset of the access points.

20. The method of claim 19 , wherein, when the other primary controller subsequently fails, the method comprises:

receiving additional requests associated with the subset of the access points; and

in response to the additional requests, providing, using at least the given backup controller, failover coverage for the subset of the access points.

Assignments (11)
SECURITY INTEREST Recorded Apr 8, 2026
From: ARRIS ENTERPRISES LLC; RUCKUS IP HOLDINGS LLC
To: CITIBANK, N.A., AS COLLATERAL AGENT
Reel/Frame 075476/0814 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 067620/0675 Recorded Jan 12, 2026
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: RUCKUS IP HOLDINGS LLC
Reel/Frame 074593/0001 →
RELEASE OF SECURITY INTEREST AT REEL/FRAME 067620/0717 Recorded Dec 19, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: RUCKUS IP HOLDINGS LLC
Reel/Frame 069743/0220 →
SECURITY INTEREST Recorded Dec 17, 2024
From: ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE INC., OF NORTH CAROLINA; OUTDOOR WIRELESS NETWORKS LLC; RUCKUS IP HOLDINGS LLC
To: APOLLO ADMINISTRATIVE AGENCY LLC
Reel/Frame 069889/0114 →
PATENT SECURITY AGREEMENT (ABL) Recorded Jun 4, 2024
From: RUCKUS IP HOLDINGS LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 067620/0675 →
PATENT SECURITY AGREEMENT (TERM) Recorded Jun 4, 2024
From: RUCKUS IP HOLDINGS LLC
To: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
Reel/Frame 067620/0717 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Jan 12, 2024
From: ARRIS ENTERPRISES LLC
To: RUCKUS IP HOLDINGS LLC
Reel/Frame 066399/0561 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 10, 2022
From: BROCADE COMMUNICATIONS SYSTEMS LLC F/K/A BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS LLC F/K/A FOUNDRY NETWORKS INC.
To: ARRIS ENTERPRISES LLC
Reel/Frame 061362/0801 →
SECURITY INTEREST Recorded Nov 19, 2021
From: ARRIS SOLUTIONS, INC.; ARRIS ENTERPRISES LLC; COMMSCOPE TECHNOLOGIES LLC; COMMSCOPE, INC. OF NORTH CAROLINA; RUCKUS WIRELESS, INC.
To: WILMINGTON TRUST
Reel/Frame 060752/0001 →
CHANGE OF NAME Recorded Apr 20, 2020
From: BROCADE COMMUNICATIONS SYSTEMS, INC
To: BROCADE COMMUNICATIONS SYSTEMS LLC
Reel/Frame 052619/0789 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Sep 4, 2018
From: LEE, YI-NAN; GHOSAL, SUDIP
To: BROCADE COMMUNICATIONS SYSTEMS, INC
Reel/Frame 046777/0769 →
Continuity (2)
Provisional Application 62536988 · Jul 26, 2017
Related Publication 20190036765A1 · Jan 31, 2019