IP Library Granted Patent US 7,944,816
Granted Patent B2
US 7,944,816 · App. 12/466,363 · Granted May 17, 2011

System and method for detecting and isolating a remote loop

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,944,816
App. No.
12/466,363
Granted
May 17, 2011
Kind
B2
Abstract

A system and method are provided for enabling a first network to detect a loop in a second network connected thereto. The first network runs a first instance of a Spanning Tree Protocol and the second network runs either a different instance or no instance. The method includes sending a Remote Loop Detection Packet (“RLDP”) from the ports in bridges of the first network which are connected to the second network. The RLDP includes identifiers such as the source bridge, port and VLAN. The system and method further includes checking for receipt of the RLDP on the same bridge which sent the RLDP. If such a receipt occurs, a loop is detected and one of the ports of the receiving/sending bridge is blocked.

Claims (40)

1. A computer implemented method comprising:

at a network device comprising a memory and configured to perform packet switching, storing in the memory a first loop packet for sending from a first port of the network device, the network device configured to interface with a first network running a loop avoidance protocol instance, the first loop packet including a first identifier with a first reference to the first port;

responsive to the sending, examining a second loop packet, the second loop packet including a second identifier with a second reference to a second port; and

if the first reference and the second reference match, indicating detection of a loop in a second network communicably coupled to the first network and not running the loop avoidance protocol instance.

2. The method of claim 1 , further comprising blocking at least one of the ports in the network device when the first and second references match.

3. The method of claim 2 , wherein the blocking includes blocking the port which sent the first loop packet.

4. The method of claim 2 , wherein the blocking includes blocking a port which received the second loop packet.

5. The method of claim 2 , further comprising, when the second reference does not match the first reference, for a defined period of time, opening the at least one of the ports in the network device which was blocked.

6. The method of claim 1 , further comprising when the second identifier does not correspond to any of the ports in the network device, forwarding the second loop packet to another network device.

7. The method of claim 1 , wherein the first identifier further includes a third reference to the network device, the second identifier further includes a fourth reference to another network device, and the method further comprises:

comparing the third and fourth references; and

when the third reference matches the fourth reference and the first reference does not match the second reference, dropping the second loop packet.

8. The method of claim 1 , wherein the first network is running a first instance of a spanning tree protocol and the second network is not running the first instance of the spanning tree protocol.

9. The method of claim 1 , wherein the first identifier includes a third reference to a VLAN where the first port resides.

10. The method of claim 2 , wherein the blocking includes blocking one of the port which sent the first loop packet and a port which received the second loop packet based on the respective port IDs.

11. A network device comprising:

a memory; and

one or more modules configured to:

store in the memory a first loop packet for sending from a first port of the network device, the network device configured to perform packet switching and to interface with a first network running a loop avoidance protocol instance, the first loop packet including a first identifier with a first reference to the first port;

responsive to the sending, examine a second loop packet, the second loop packet including a second identifier with a second reference to a second port; and

if the first reference and the second reference match, indicate detection of a loop in a second network communicably coupled to the first network and not running the loop avoidance protocol instance.

12. The network device of claim 11 wherein the one or more modules are further configured to block at least one of the ports in the network device when the first and second references match.

13. The network device of claim 12 wherein the blocking includes blocking the port which sent the first loop packet.

14. The network device of claim 12 wherein the blocking includes blocking a port which received the second loop packet.

15. The network device of claim 12 wherein the one or more modules are further configured to, when the second reference does not match the first reference, for a defined period of time, open the at least one of the ports in the network device which was blocked.

16. The network device of claim 11 wherein the one or more modules are further configured to, when the second identifier does not correspond to any of the ports in the network device, forward the second loop packet to another network device.

17. The network device of claim 11 , wherein the first identifier further includes a third reference to the network device, the second identifier further includes a fourth reference to another network device, and the one or more modules are further configured to:

compare the third and fourth references; and

when the third reference matches the fourth reference and the first reference does not match the second reference, drop the second loop packet.

18. The network device of claim 11 , wherein the first network is running a first instance of a spanning tree protocol and the second network is not running the first instance of the spanning tree protocol.

19. The network device of claim 11 , wherein the first identifier includes a third reference to a VLAN where the first port resides.

20. The network device of claim 12 , wherein the one or more modules are further configured to block one of the port which sent the first loop packet and a port which received the second loop packet based on the respective port IDs.

21. A program storage device readable by a machine, embodying a program of instructions executable by the machine to perform a method, method comprising:

at a network device comprising a memory and configured to perform packet switching, storing in the memory a first loop packet for sending from a first port of the network device, the network device configured to interface with a first network running a loop avoidance protocol instance, the first loop packet including a first identifier with a first reference to the first port;

responsive to the sending, examining a second loop packet, the second loop packet including a second identifier with a second reference to a second port; and

if the first reference and the second reference match, indicating detection of a loop in a second network communicably coupled to the first network and not running the loop avoidance protocol instance.

22. An apparatus comprising:

means for, at a network device comprising a memory and configured to perform packet switching, storing in the memory a first loop packet for sending from a first port of the network device, the network device configured to interface with a first network running a loop avoidance protocol instance, the first loop packet including a first identifier with a first reference to the first port;

means for, responsive to the sending, examining a second loop packet, the second loop packet including a second identifier with a second reference to a second port; and

means for, if the first reference and the second reference match, indicating detection of a loop in a second network communicably coupled to the first network and not running the loop avoidance protocol instance.

Assignments (8)
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 18, 2018
From: BROCADE COMMUNICATIONS SYSTEMS LLC
To: AVAGO TECHNOLOGIES INTERNATIONAL SALES PTE. LIMITED
Reel/Frame 047270/0247 →
RELEASE OF SECURITY INTEREST Recorded Jan 22, 2015
From: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC
Reel/Frame 034804/0793 →
RELEASE OF SECURITY INTEREST Recorded Jan 21, 2015
From: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
To: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC
Reel/Frame 034784/0609 →
SUPPLEMENTAL PATENT SECURITY AGREEMENT Recorded Sep 26, 2011
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION; MCDATA SERVICES CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 026971/0042 →
SUPPLEMENTAL PATENT SECURITY AGREEMENT Recorded Sep 20, 2011
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; MCDATA CORPORATION
To: BANK OF AMERICA, N.A., AS ADMINISTRATIVE AGENT
Reel/Frame 026938/0922 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Dec 20, 2010
From: MONCADA-ELIAS, JORDI; RAMANATHAN, RAJIV
To: FOUNDRY NETWORKS, INC.
Reel/Frame 025527/0478 →
CHANGE OF NAME Recorded Jul 21, 2010
From: FOUNDRY NETWORKS, INC.
To: FOUNDRY NETWORKS, LLC
Reel/Frame 024733/0739 →
SECURITY AGREEMENT Recorded Jan 20, 2010
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, LLC; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION; MCDATA SERVICES CORPORATION
To: WELLS FARGO BANK, NATIONAL ASSOCIATION, AS COLLATERAL AGENT
Reel/Frame 023814/0587 →