Seamless spanning tree upgrade of a linecard

• US 7,801,061 B2
• Filed: 01/10/2006
• Issued: 09/21/2010
• Est. Priority Date: 01/10/2006
• Status: Active Grant

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Patel, Amitkumar, Khan, Tameen, Desai, Ronak, Mahajan, Umesh, Mellacheruvu, Ramana
• Primary Examiner(s): Ton; Dang T
• Assistant Examiner(s): Zhao; Wei
• Application Number:
  US11/329,863
• Publication Number:
  US 20070159988A1
• Time in Patent Office: 1,715 Days
• Field of Search: 370/256, 370/250, 370/254, 370/219, 455/427
• US Class Current: 370/256
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 45/18 Loop-free operations
• CPC Class Codes: H04L 45/563 Software download or update

Abstract

Disclosed are methods and apparatus for restarting a first network device having a plurality of ports for receiving and transmitting layer 2 data. The first network device belongs to a network of network devices. When a restart of at least a portion of the first network device is imminent whereby the restarting network device portion can no longer alter a spanning tree protocol (STP) state of one or more of the ports and such ports that remain in a fixed state during the restart are referred to as restarting ports, a current state (such as forwarding) of each restarting port is maintained during the restart under predefined conditions. During the restart, each of the restarting ports of the restarting network device portion cooperate with its peer port of a second non-restarting network device that is a neighbor of the first network device so as to prevent layer 2 loops in the network.

Claims

1. A method of restarting a first network device having a plurality of ports for receiving and transmitting layer 2 data, wherein the first network device belongs to a network of network devices, the method comprising:

when a restart of a process that includes altering a spanning state protocol (STP) state of one or more ports of at least a restarting network portion of the first network device is imminent whereby the restarting process can no longer alter the STP state of one or more restarting ports of the first network device'"'"'s ports during the restart, maintaining an STP forwarding state of each restarting port that is in such STP forwarding state so as not to change such STP forwarding state to a blocking state before or during the restart under predefined conditions; and

during the restart, each of the restarting ports of the restarting network portion cooperating with its peer port of a second non-restarting network device that is a neighbor of the first network device so as to prevent layer 2 loops in the network.

2. The method as recited in claim 1, wherein the restarting network portion is a linecard in the first network device, wherein the linecard can no longer alter the spanning tree protocol (STP) state of one or more of the restarting ports.

3. The method as recited in claim 2, wherein each restarting port that is a Portfast port is maintained in the STP forwarding state during the restart.

4. The method as recited in claim 3, further comprising blocking each restarting port that is shared by two or more other network devices during the restart.

5. The method as recited in claim 4, wherein each restarting port that is not shared and not a Portfast port is maintained in the STP forwarding state during the restart if it is determined that its peer can cooperate to prevent loops, the method further comprising informing the peers of the restarting ports, which can cooperate to prevent loops during the restart, about the restart.

6. The method as recited in claim 5, wherein each peer is informed that a restart is imminent, about the kind of restart, and of the completion of the restart when the restart is completed.

7. The method as recited in claim 6, wherein each restarting port that is not shared and not a Portfast port is blocked during the restart if it is determined that its peer cannot cooperate to prevent loops during the restart.

8. The method as recited in claim 7, further comprising completing any pending port STP state changes prior to the restart and blocking STP configuration until the restart completes.

9. The method as recited in claim 8, further comprising excluding restarting ports that are blocked during the restart from STP root computations during the restart.

10. The method as recited in claim 8, further comprising deferring a restarting port'"'"'s STP state change from blocking to forwarding until after completion of the restart.

11. The method as recited in claim 10, further comprising performing the following operations when a role change in the network results in an STP state change for a particular restarting port from forwarding to blocking:

the particular restarting port sending a first Bridge Protocol Data Unit (BPDU) advertising its current STP state and identifying its new port role to the particular restarting port'"'"'s peer, wherein the first BPDU is sent to cause the particular restarting port'"'"'s peer to change its STP state to blocking and mark itself as Restart-Inconsistent; and

the particular restarting port receiving a second BPDU from the particular restarting port'"'"'s peer conveying the peer'"'"'s new STP blocking state.

12. The method as recited in claim 11, further comprising performing the following operations when a SYNC operation in the network results in an STP state change for a particular restarting port from forwarding to blocking:

when the first network device receives a proposal for a new link to open from a peer port that proposes to go to the STP forwarding state, the first network device forwarding the proposal to its one or more neighbor network devices so that the one or more neighbor network devices can each cut itself off from the rest of the network; and

when, in response to the proposal that was forwarded to the one or more neighbor network devices, an agreement is received into the first network device, forwarding the agreement to its peer port of the new link.

13. The method as recited in claim 12, further comprising setting a short aging timer for a MAC Address Learning table for the restarting network device, prior to restart, so as to invoke a fast flush of stale L2 entries in the MAC Address Learning table.

14. A first network device operable to restart, wherein the first network device has a plurality of ports for receiving and transmitting layer 2 data, wherein the first network device belongs to a network of network devices, the first network device comprising:

one or more processors;

one or more memory, wherein at least one of the processors and memory are configured for;

when a restart of a process that includes altering a spanning state protocol (STP) state of one or more ports of at least a restarting network portion of the first network device is imminent whereby the restarting process can no longer alter the STP state of one or more restarting ports of the first network device'"'"'s ports during the restart, maintaining an STP forwarding state of each restarting port that is in such STP forwarding state so as not to change such STP forwarding state to a blocking state before or during the restart under predefined conditions; and

during the restart, each of the restarting ports of the restarting network portion cooperating with its peer port of a second non-restarting network device that is a neighbor of the first network device so as to prevent layer 2 loops in the network.

15. The first network device as recited in claim 14, wherein the restarting network portion is a linecard in the first network device, wherein the linecard can no longer alter the spanning tree protocol (STP) state of one or more of the restarting ports.

16. The first network device as recited in claim 15, wherein each restarting port that is a Portfast port is maintained in the STP forwarding state during the restart.

17. The first network device as recited in claim 16, wherein at least one of the processors and memory are configured for blocking each restarting port that is shared by two or more other network devices during the restart.

18. The first network device as recited in claim 17, wherein each restarting port that is not shared and not a Portfast port is maintained in the STP forwarding state during the restart if it is determined that its peer can cooperate to prevent loops, wherein the at least one of the processors and memory are further configured for informing the peers of the restarting ports, which can cooperate to prevent loops during the restart, about the restart.

19. The first network device as recited in claim 18, wherein each peer is informed that a restart is imminent, about the kind of restart, and of the completion of the restart when the restart is completed.

20. The first network device as recited in claim 19, wherein each restarting port that is not shared and not a Portfast port is blocked during the restart if it is determined that its peer cannot cooperate to prevent loops during the restart.

21. The first network device as recited in claim 20, wherein at least one of the processors and memory are further configured for completing any pending port STP state changes prior to the restart and blocking STP configuration until the restart completes.

22. The first network device as recited in claim 21, wherein at least one of the processors and memory are further configured for excluding restarting ports that are blocked during the restart from STP root computations during the restart.

23. The first network device as recited in claim 21, wherein at least one of the processors and memory are further configured for deferring a restarting port'"'"'s STP state change from blocking to forwarding until after completion of the restart.

24. The first network device as recited in claim 23, wherein at least one of the processors and memory are further configured for performing the following operations when a role change in the network results in an STP state change for a particular restarting port from forwarding to blocking:

the particular restarting port sending a first Bridge Protocol Data Unit (BPDU) advertising its current STP state and identifying its new port role to the particular restarting port'"'"'s peer, wherein the first BPDU is sent to cause the particular restarting port'"'"'s peer to change its STP state to blocking and mark itself as Restart-Inconsistent; and

the particular restarting port receiving a second BPDU from the particular restarting port'"'"'s peer conveying the peer'"'"'s new STP blocking state.

25. The first network device as recited in claim 24, wherein at least one of the processors and memory are further configured for performing the following operations when a SYNC operation in the network results in an STP state change for a particular restarting port from forwarding to blocking:

when the first network device receives a proposal for a new link to open from a peer port that proposes to go to the STP forwarding state, the first network device forwarding the proposal to its one or more neighbor network devices so that the one or more neighbor network devices can each cut itself off from the rest of the network; and

when, in response to the proposal that was forwarded to the one or more neighbor network devices, an agreement is received into the first network device, forwarding the agreement to its peer port of the new link.

26. The first network device as recited in claim 25, wherein at least one of the processors and memory are further configured for setting a short aging timer for a MAC Address Learning table for the restarting network device, prior to restart, so as to invoke a fast flush of stale L2 entries in the MAC Address Learning table.

27. An apparatus for restarting a first network device having a plurality of ports for receiving and transmitting layer 2 data, wherein the first network device belongs to a network of network devices, the apparatus being in the form of the first network device and comprising:

means for when a restart of a process that includes altering a spanning state protocol (STP) state of one or more ports of at least a restarting network portion of the first network device is imminent whereby the restarting process can no longer alter the STP of one or more restarting ports of the first network device'"'"'s ports during the restart, maintaining an STP forwarding state of each restarting port that is in such STP forwarding state so as not to change such STP forwarding state to a blocking state before or during the restart under predefined conditions; and

means for during the restart, each of the restarting ports of the restarting network portion cooperating with its peer port of a second non-restarting network device that is a neighbor of the first network device so as to prevent layer 2 loops in the network.

28. A network system for restarting a first switch having a plurality of ports for receiving and transmitting layer 2 data, comprising:

a plurality of switches including the first switch and at least one neighbor switch coupled to the first switch,

the first switch being operable to;

when a restart of a process that includes altering a spanning state protocol (STP) state of one or more ports of at least a restarting portion of the first switch is imminent whereby the restarting portion can no longer alter the STP state of one or more restarting ports of the first switch'"'"'s ports during the restart, maintaining such STP forwarding state of each restarting port so as not to change such STP forwarding state to a blocking state before or during the restart under predefined conditions; and

during the restart, at least one of the restarting ports of the restarting portion cooperating with a peer port of the neighbor switch so as to prevent layer 2 loops in the network.