IP Library Granted Patent US 8,462,668
Granted Patent B2
US 8,462,668 · App. 10/261,946 · Granted Jun 11, 2013

System and method for implementation of layer 2 redundancy protocols across multiple networks

Inventors: Andrew Tai-Chin Kuo (Newark, CA); Gurudeep Kamat (Mountain View, CA); Jordi Moncada-Elias (Milpitas, CA); Ivy Pei-Shan Hsu (Pleasanton, CA); Rajkumar Jalan (Saratoga, CA)
Assignee: Foundry Networks, LLC
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,462,668
App. No.
10/261,946
Granted
Jun 11, 2013
Kind
B2
Abstract

The system, method, and article of manufacture of the present invention allows multiple customers connected to a common external network to each implement a layer 2 redundancy protocol, such as the spanning tree protocol, in order to prevent layer 2 loops. Accordingly, a method is presented for providing an independent loop free layer 2 topology between a external network and a customer network comprising tagging control packets originating on the customer network with a unique identifier and tunneling the control packets received from the customer network between a plurality of boundary interface devices at the external network such that the control packets are routed back to the customer network based on the presence of the unique identifier in the control packet. The layer 2 redundancy protocol on the customer network converges based at least in part on the presence of control packets appearing on more than one port on the customer network.

Claims (24)

1. A method performed by a network device for use in a first network, the method comprising:

modifying, by the network device, a MAC address of a Bridge Protocol Data Unit (BPDU) to include a unique identifier that identifies a second network as a source network for the BPDU,

wherein the first network is configured to implement a first instance of Spanning Tree Protocol (STP),

wherein the second network is configured to implement a second instance of STP that is separate from the first instance, and

wherein the modifying causes the BPDU to be flooded through the first network in a tunnel and routed back to the second network from the first network based on the presence of the unique identifier in the BPDU, the BPDU being configured to facilitate convergence of the second instance of STP upon being routed back to the second network.

2. The method of claim 1 further comprising forwarding the BPDU to one or more network devices at the first network.

3. The method of claim 2 wherein forwarding the BPDU comprises flooding the BPDU.

4. The method of claim 1 further comprising modifying, by the network device, a second BPDU to include a second unique identifier that identifies a third network as a source network for the second BPDU, wherein the third network is configured to implement a third instance of STP separate from the first and second instances, and

wherein the modifying of the second BPDU causes the second BPDU to be routed back to the third network from the first network based on the presence of the second unique identifier in the second BPDU.

5. The method of claim 1 further comprising:

entering a preforwarding state; and

while in the preforwarding state, preventing the forwarding of general data packet traffic.

6. The method of claim 1 wherein modifying the MAC address of the BPDU to include the unique identifier comprises modifying fourth and fifth bytes of the MAC address.

7. A network device for use in a first network, the network device comprising:

a processor; and

a non-transitory data store having stored thereon program code which, when executed by the processor, causes the processor to:

modify a MAC address of a BPDU to include a unique identifier that identifies a second network as a source network for the BPDU, wherein the first network is configured to implement a first instance of STP, wherein the second network is configured to implement a second instance of STP separate from the first instance, and wherein the unique identifier allows the BPDU to be flooded through the first network in a tunnel and routed back to the second network from the first network based on the presence of the unique identifier in the BPDU, the BPDU being configured to facilitate convergence of the second instance of STP upon being routed back to the second network.

8. The network device of claim 7 wherein the program code further causes the processor to:

modify a second BPDU to include a second unique identifier that identifies a third network as a source network for the second BPDU, wherein the third network is configured to implement a third instance of STP separate from the first and second instances, and wherein the second unique identifier allows the second BPDU to be routed back to the third network from the first network based on the presence of the second unique identifier in the second BPDU.

9. The network device of claim 7 , wherein the modifying is performed by the processor while the network device is in a pre-forwarding state, and wherein the network device is unable to forward any packets other than BPDUs from the second network while the network device is in the pre-forwarding state.

10. The network device of claim 7 wherein the program code further causes the processor to forward the BPDU to one or more network devices at the first network.

11. The network device of claim 10 wherein forwarding the BPDU comprises flooding the BPDU.

12. The network device of claim 7 wherein the program code further causes the processor to enter a preforwarding state in which the processor prevents the forwarding of general data packet traffic.

13. The network device of claim 7 wherein modifying the MAC address comprises modifying fourth and fifth bytes of the MAC address.

Assignments (7)
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.; INRANGE TECHNOLOGIES CORPORATION; FOUNDRY NETWORKS, LLC
Reel/Frame 034792/0540 →
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 →
SECURITY AGREEMENT Recorded Dec 22, 2008
From: BROCADE COMMUNICATIONS SYSTEMS, INC.; FOUNDRY NETWORKS, INC.; INRANGE TECHNOLOGIES CORPORATION; MCDATA CORPORATION
To: BANK OF AMERICA, N.A. AS ADMINISTRATIVE AGENT
Reel/Frame 022012/0204 →
ASSIGNMENT OF ASSIGNOR'S INTEREST Recorded Oct 1, 2002
From: TAI-CHIN KUO, ANDREW; KAMAT, GURUDEEP; MONCADA-ELIAS, JORDI; PEI-SHAN HSU, IVY; JALAN, RAJKUMAR
To: FOUNDRY NETWORKS, INC.
Reel/Frame 013359/0864 →
Continuity (1)
Related Publication 20090274153A1 · Nov 5, 2009