IP Library Granted Patent US 9,860,133
Granted Patent B2
US 9,860,133 · App. 15/051,601 · Granted Jan 2, 2018

Configuration validation in a mixed node topology

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 9,860,133
App. No.
15/051,601
Granted
Jan 2, 2018
Kind
B2
Abstract

Techniques for validating configuration changes in a mixed node topology are provided. In one embodiment, a device can identify a link to be removed from a topology comprising a plurality of nodes, where the plurality of nodes includes one or more nodes of a first type and one or more nodes of a second type. The device can then determine whether the removal of the link from the topology would require data traffic between two nodes of the first type to pass through a node of the second type.

Claims (40)

1. A method comprising:

receiving, by a device, a user command to remove a link from a topology comprising a plurality of nodes, the plurality of nodes including one or more nodes of a first type and one or more nodes of a second type;

validating, by the device, whether removal of the link from the topology would cause one or more nodes in the plurality of nodes to become unreachable by a master node of the first type, or whether removal of the link would cause data traffic between two nodes of the first type to pass through a node of the second type;

if removal of the link would cause one or more nodes in the plurality of nodes to become unreachable by the master node or cause data traffic between two nodes of the first type to pass through a node of the second type, rejecting, by the device, the user command to remove the link from the topology; and

if removal of the link would not cause one or more nodes in the plurality of nodes to become unreachable by the master node and would not cause data traffic between two nodes of the first type to pass through a node of the second type, accepting, by the device, the user command to remove the link from the topology.

2. The method of claim 1 wherein the topology is a mesh topology.

3. The method of claim 1 wherein the one or more nodes of the first type are more capable than the one or more nodes of the second type.

4. The method of claim 3 wherein the one or more nodes of the first type support greater port bandwidth, a larger number of ports, or a higher level of security clearance than the one or more nodes of the second type.

5. The method of claim 1 wherein the validating comprises:

removing the link from a representation of the topology; and

for each endpoint node located at an endpoint of the link, creating a node set that includes the endpoint node.

6. The method of claim 5 wherein the validating further comprises, for the endpoint node:

adding, to the node set, other nodes in the plurality of nodes that are directly linked to the endpoint node in the representation of the topology; and

subsequently to the adding, checking whether the node set includes the master node.

7. The method of claim 6 wherein if the endpoint node is of the second type, the adding comprises adding directly linked nodes that are of the first type or the second type, and

wherein if the endpoint node is of the first type, the adding comprises adding directly linked nodes that are of the first type, without adding any directly linked nodes that are of the second type.

8. The method of claim 6 wherein the validating further comprises:

if the node set does not include the master node, repeating the adding and the checking for additional nodes in the node set;

else if the node set includes the master node, returning a first result.

9. The method of claim 8 wherein the validating further comprises:

if every node in the node set has been processed and the first result has not been returned, returning a second result.

10. The method of claim 9 wherein the user command is rejected if the second result is returned for any endpoint node of the link.

11. The method of claim 1 wherein the device is the master node.

12. The method of claim 1 wherein the topology represents a stacking system, and wherein each node in the plurality of nodes corresponds to a stackable switch in the stacking system.

13. The method of claim 12 wherein the user command specifies a stacking port or a stacking trunk of a node in the plurality of nodes, and

wherein the link is identified based on the stacking port or the stacking trunk.

14. A non-transitory computer readable medium having stored thereon program code executable by a processor, the program code comprising code that causes the processor to:

receive a user command to remove a link from a topology comprising a plurality of nodes, the plurality of nodes including one or more nodes of a first type and one or more nodes of a second type;

validate whether removal of the link from the topology would cause one or more nodes in the plurality of nodes to become unreachable by a master node of the first type, or whether removal of the link would cause data traffic between two nodes of the first type to pass through a node of the second type;

if removal of the link would cause one or more nodes in the plurality of nodes to become unreachable by the master node or cause data traffic between two nodes of the first type to pass through a node of the second type, reject the user command to remove the link from the topology; and

if removal of the link would not cause one or more nodes in the plurality of nodes to become unreachable by the master node and would not cause data traffic between two nodes of the first type to pass through a node of the second type, accept the user command to remove the link from the topology.

15. The non-transitory computer readable medium of claim 14 wherein the one or more nodes of the first type are more capable than the one or more nodes of the second type.

16. A device comprising:

a processor; and

a non-transitory computer readable medium having stored thereon program code which, when executed by the processor, causes the processor to:

receive a user command to remove a link from a topology comprising a plurality of nodes, the plurality of nodes including one or more nodes of a first type and one or more nodes of a second type;

validate whether removal of the link from the topology would cause one or more nodes in the plurality of nodes to become unreachable by a master node of the first type, or whether removal of the link would cause data traffic between two nodes of the first type to pass through a node of the second type;

if removal of the link would cause one or more nodes in the plurality of nodes to become unreachable by the master node or cause data traffic between two nodes of the first type to pass through a node of the second type, reject the user command to remove the link from the topology; and

if removal of the link would not cause one or more nodes in the plurality of nodes to become unreachable by the master node and would not cause data traffic between two nodes of the first type to pass through a node of the second type, accept the user command to remove the link from the topology.

17. The device of claim 16 wherein the one or more nodes of the first type are more capable than the one or more nodes of the second type.

Assignments (8)
RELEASE OF SECURITY INTEREST AT REEL/FRAME 049905/0504 Recorded Dec 19, 2024
From: JPMORGAN CHASE BANK, N.A., AS COLLATERAL AGENT
To: ARRIS ENTERPRISES LLC (F/K/A ARRIS ENTERPRISES, INC.); ARRIS TECHNOLOGY, INC.; ARRIS SOLUTIONS, INC.; COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC; RUCKUS WIRELESS, LLC (F/K/A RUCKUS WIRELESS, INC.)
Reel/Frame 071477/0255 →
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 →
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 →
ABL SECURITY AGREEMENT Recorded Jul 3, 2019
From: COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC; ARRIS ENTERPRISES LLC; ARRIS TECHNOLOGY, INC.; RUCKUS WIRELESS, INC.; ARRIS SOLUTIONS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 049892/0396 →
PATENT SECURITY AGREEMENT Recorded Jul 3, 2019
From: ARRIS ENTERPRISES LLC
To: WILMINGTON TRUST, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 049820/0495 →
TERM LOAN SECURITY AGREEMENT Recorded Jul 3, 2019
From: COMMSCOPE, INC. OF NORTH CAROLINA; COMMSCOPE TECHNOLOGIES LLC; ARRIS ENTERPRISES LLC; ARRIS TECHNOLOGY, INC.; RUCKUS WIRELESS, INC.; ARRIS SOLUTIONS, INC.
To: JPMORGAN CHASE BANK, N.A.
Reel/Frame 049905/0504 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Apr 16, 2018
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 045600/0755 →
CHANGE OF NAME Recorded Dec 13, 2017
From: BROCADE COMMUNICATIONS SYSTEMS, INC.
To: BROCADE COMMUNICATIONS SYSTEMS LLC
Reel/Frame 044861/0618 →