Managing a global forwarding table in a distributed switch

• US 8,891,535 B2
• Filed: 01/18/2012
• Issued: 11/18/2014
• Est. Priority Date: 01/18/2012
• Status: Active Grant

• Current Assignee: International Business Machines Corporation
• Original Assignee: International Business Machines Corporation
• Inventors: Angst, Debra L., Basso, Claude, Cors, Josep, Mundhra, Rekha, Vaidhyanathan, Natarajan
• Primary Examiner(s): Weidner, Timothy J
• Application Number:
  US13/352,973
• Publication Number:
  US 20130182707A1
• Time in Patent Office: 1,035 Days
• Field of Search: None
• US Class Current: 370/400
• CPC Class Codes: H04L 12/18 for broadcast or conference , e.g. multicast
• CPC Class Codes: H04L 12/44 Star or tree networks
• CPC Class Codes: H04L 12/4625 Single bridge functionality, e.g. connection of two networks over a single bridge
• CPC Class Codes: H04L 41/12 Discovery or management of network topologies
• CPC Class Codes: H04L 45/02 Topology update or discovery
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/54 Organization of routing tables
• CPC Class Codes: H04L 47/15 in relation to multipoint traffic arrangements for broadcast or multicast in data networks H04L12/18
• CPC Class Codes: H04L 49/201 Multicast operation; Broadcast operation
• CPC Class Codes: H04L 49/65 Re-configuration of fast packet switches
• CPC Class Codes: H04L 69/28 Timers or timing mechanisms used in protocols

Abstract

Apparatuses and methods to manage a global forwarding table in a distributed switch are provided. A particular method may include managing a global forwarding table in a distributed switch. The distributed switch may include a plurality of switch forwarding units. The method may start a timer for an entry in the global forwarding table, and the entry may include a multicast destination address and corresponding multicast membership information. The method may also, in response to expiration of the timer of the entry, check at least one hit status to determine whether at least one switch forwarding unit of the plurality of switch forwarding units has forwarded multicast data to the corresponding multicast membership information of the multicast destination address of the entry. The method may further determine whether the entry is a cast-out candidate based on the hit status.

Claims

1. A method comprising:

adding an entry in a global forwarding table in a distributed switch, wherein the entry includes a multicast destination address and multicast membership information, wherein the distributed switch comprises distributed switch elements, wherein each distributed switch element comprises;

a plurality of switch forwarding units,

a plurality of caches corresponding to the plurality of switch forwarding units, and

a programming table corresponding to information programmed into the plurality of caches;

starting a timer for the entry;

when a miss event is generated by a first switch forwarding unit of the plurality of switch forwarding units that corresponds to a first distributed switch element of the distributed switch elements;

programming the first switch forwarding unit with the multicast destination address and corresponding multicast membership information; and

registering the multicast destination address and corresponding multicast membership information to create a registration, wherein the registering comprises storing the multicast destination address and corresponding multicast membership information in the programming table of the first distributed switch element, and wherein the registration includes a hit status;

in response to expiration of the timer of the entry, checking a hit status of a cache of each of the switch forwarding units of the distributed switch to determine whether any switch forwarding unit of the distributed switch has forwarded multicast data to the corresponding multicast membership information of the multicast destination address of the entry; and

determining whether the entry is a cast-out candidate based on checking the hit status.

2. The method of claim 1, wherein checking the hit status does not indicate forwarding of the multicast data to the corresponding multicast membership information of the multicast destination address of the entry, further comprising indicating that the entry is a cast-out candidate.

3. The method of claim 1, wherein checking the hit status indicates forwarding of the multicast data to the corresponding multicast membership information of the multicast destination address of the entry, further comprising resetting the hit status.

4. The method of claim 1, including determining that the entry is a cast-out candidate, and further comprising indicating that the entry is a cast-out candidate to a snooper of the distributed switch.

5. The method of claim 1, including determining that the entry is a cast-out candidate, and further comprising removing the entry from the global forwarding table.

6. The method of claim 1, including determining that the entry is a cast-out candidate, and further comprising invalidating the multicast destination address and corresponding multicast membership information of the entry in at least one switch forwarding unit that is programmed with the multicast destination address and corresponding multicast membership information of the entry.

7. The method of claim 1, wherein the global forwarding table is managed by a snooper of the distributed switch.

8. The method of claim 1, wherein the global forwarding table is managed by master multicast firmware of a master distributed switch element of the distributed switch.

9. The method of claim 1, further comprising:

restarting the timer for the entry;

in response to expiration of the restarted timer of the entry, rechecking the hit status of the cache of each of the switch forwarding units of the distributed switch to determine whether any switch forwarding unit of the distributed switch has forwarded multicast data to the corresponding multicast membership information of the multicast destination address of the entry; and

determining whether the entry is a cast-out candidate based on rechecking the hit status.

10. The method of claim 1, further comprising determining whether a master switch forwarding unit or a slave switch forwarding unit is programmed with the multicast destination address and corresponding multicast membership information.

11. An apparatus comprising:

at least one processor; and

program code configured to be executed by the processor to manage a global forwarding table in a distributed switch, wherein the distributed switch comprises distributed switch elements, wherein each distributed switch element comprises;

a plurality of switch forwarding units,

a plurality of caches corresponding to the plurality of switch forwarding units, and

a programming table corresponding to information programmed into the plurality of caches; and

wherein the program code when executed by the processor causes operations including;

starting a timer for an entry in the global forwarding table, wherein the entry includes a multicast destination address and corresponding multicast membership information;

when a miss event is generated by a first switch forwarding unit of the plurality of switch forwarding units that corresponds to a first distributed switch element of the distributed switch elements;

programming the first switch forwarding unit with the multicast destination address and corresponding multicast membership information; and

registering the multicast destination address and corresponding multicast membership information to create a registration, wherein the registering comprises storing the multicast destination address and corresponding multicast membership information in the programming table of the first distributed switch element, and wherein the registration includes a hit status;

in response to expiration of the timer of the entry, checking a hit status of a cache of each of the switch forwarding units of the distributed switch to determine whether any switch forwarding unit of the distributed switch has forwarded multicast data to the corresponding multicast membership information of the multicast destination address of the entry; and

determining whether the entry is a cast-out candidate based on checking the hit status.

12. The apparatus of claim 11, wherein when checking the hit status does not indicate forwarding of the multicast data the program code causes indicating that the entry is a cast-out candidate.

13. The apparatus of claim 11, wherein when checking the hit status indicates forwarding of the multicast data the program code causes resetting the hit status.

14. The apparatus of claim 11, wherein when the entry is determined to be a cast-out candidate the program code causes indicating that the entry is a cast-out candidate to a snooper of the distributed switch.

15. The apparatus of claim 11, wherein the program code is configured to cause determining that the entry is a cast-out candidate, and wherein the program code is further configured to cause removing the entry from the global forwarding table.

16. The apparatus of claim 11, wherein the program code is configured to cause determining that the entry is a cast-out candidate, and wherein the program code is further configured to cause invalidating the multicast destination address and corresponding multicast membership information of the entry in at least one switch forwarding unit that is programmed with the multicast destination address and corresponding multicast membership information of the entry.

17. The apparatus of claim 11, wherein the program code is further causes:

restarting the timer for the entry;

in response to expiration of the restarted timer of the entry, rechecking the hit status of the cache of each of the switch forwarding units of the distributed switch to determine whether any switch forwarding unit of the distributed switch has forwarded multicast data to the corresponding multicast membership information of the multicast destination address of the entry; and

determining whether the entry is a cast-out candidate based on rechecking the hit status.

18. The apparatus of claim 11, wherein the program code causes managing the global forwarding table by a snooper of the distributed switch, master multicast firmware of a master distributed switch element of the distributed switch, or any combination thereof.