IP Multicast Snooping and Routing with Multi-Chassis Link Aggregation

• US 20120033668A1
• Filed: 01/20/2011
• Published: 02/09/2012
• Est. Priority Date: 08/04/2010
• Status: Active Grant

• Current Assignee: WSOU Investments, LLC (WSOU Holdings, LLC)
• Original Assignee: Alcatel-Lucent USA, Inc. (Nokia Corporation)
• Inventors: Humphries, Kevin J.
• Granted Patent: US 8,472,447 B2
• Time in Patent Office: Days
• US Class Current: 370/390
• CPC Class Codes: H04L 12/185 with management of multicast group membership
• CPC Class Codes: H04L 45/22 Alternate routing
• CPC Class Codes: H04L 45/245 Link aggregation, e.g. trunking
• CPC Class Codes: H04L 45/28 using route fault recovery
• CPC Class Codes: H04L 45/58 Association of routers
• CPC Class Codes: H04L 49/552 by ensuring the integrity of packets received through redundant connections
• CPC Class Codes: Y02D 30/50 in wire-line communication networks, e.g. low power modes or reduced link rate

Abstract

Aggregation Switches connected via a virtual fabric link (VFL) are each active and able to perform at least limited IP multicast snooping. The resulting IP multicast snooping information is maintained internally within each Aggregation Switch and shared substantially in real-time therebetween via the VFL.

Claims

1. An aggregation switch in a multi-chassis system for performing Internet Protocol (IP) multicast snooping, comprising:

a plurality of virtual fabric link (VFL) ports coupled to a VFL, wherein the VFL is connected to a remote aggregation switch, wherein the remote aggregation switch is active and in a separate physical chassis;

a plurality of external ports coupled to at least one edge node and at least one network node;

a database maintaining IP multicast snooping information; and

a chassis management module for receiving the snooping information via at least the external ports, storing the snooping information within the database and sharing the snooping information substantially in real-time with the remote aggregation switch via the VFL.

2. The aggregation switch of claim 1, wherein the chassis management module shares the snooping information with an additional chassis management module on the remote aggregation switch via a logical inter-process communication (IPC) channel over the VFL.

3. The aggregation switch of claim 1, wherein the snooping information includes at least one of group membership information identifying groups for receiving multicast traffic flows, queries for multicast traffic flows, identifiers of multicast traffic flows and identifiers of neighboring multicast routers.

4. The aggregation switch of claim 1, wherein:

one or more of the external ports are member ports of a multi-chassis link aggregation group (MC-LAG) connected to an edge node; and

the remote aggregation switch includes one or more of the member ports of the MC-LAG.

5. The aggregation switch of claim 4, wherein the chassis management module further receives a portion of the snooping information from the remote aggregation switch via the VFL, the portion of the snooping information having remote hardware device information associated therewith, the remote hardware device information including a remote external port identifier of a remote external port that received the snooping information on the remote aggregation switch.

6. The aggregation switch of claim 5, wherein the chassis management module further:

determines whether the remote hardware device information identifies one of the member ports of the MC-LAG on the remote aggregation switch;

when the remote hardware device information identifies one of the member ports of the MC-LAG on the remote aggregation switch;

determines a local member port of the MC-LAG on the aggregation switch,

creates a membership record for the portion of the snooping information,

stores the membership record and local hardware device information of the local member port of the MC-LAG in the database for the portion of the snooping information, and

uses the local hardware device information to compute a forwarding vector for the portion of the snooping information.

7. The aggregation switch of claim 6, wherein, when the remote hardware device information does not identify one of the member ports of the MC-LAG on the remote aggregation switch, the chassis management module further:

stores the membership record and VFL hardware device information of the VFL in the database for the portion of the snooping information; and

uses the VFL hardware device information to compute a forwarding vector for the portion of the snooping information.

8. The aggregation switch of claim 1, wherein the chassis management module further:

receives a portion of the snooping information from the remote aggregation switch via the VFL, the portion of the snooping information including a source address, group address and flow characteristics of a multicast data source and further including remote hardware device information associated therewith, the remote hardware device information including a remote external port identifier of a remote external port that received the snooping information on the remote aggregation switch;

creates a flow record for the portion of the snooping information;

stores the flow record and VFL hardware device information of the VFL in the database for the portion of the snooping information; and

uses the VFL hardware device information to compute a forwarding vector for the portion of the snooping information.

9. The aggregation switch of claim 1, wherein the aggregation switch is a primary switch and the remote aggregation switch is a secondary switch, and wherein the chassis management module further configures:

a virtual IP interface associated with a virtual IP virtual local area network (VIP VLAN) coupling the primary switch and the secondary switch to a MC-LAG as a stub network to prevent the virtual IP interface from sending and processing received Layer 3 routing control packets on the external ports, the virtual IP interface being further configured as a designated Protocol Independent Multicast (PIM) router for the VIP VLAN; and

a network IP interface associated with a VLAN coupling the primary switch to a network node as a normal IP interface to enable the network interface to send and receive Layer 3 routing control packets for the VIP VLAN on the external ports;

wherein the chassis management module and provides the snooping information to the network IP interface to enable the network IP interface to send and receive the Layer 3 routing control packets on the external ports.

10. The aggregation switch of claim 9, wherein the chassis management module further builds replication vectors for multicast traffic flows based on the Layer 3 routing control packets and provides the replication vectors to the remote aggregation switch.

11. The aggregation switch of claim 1, wherein the aggregation switch is a secondary switch and the remote aggregation switch is a primary switch, and wherein the chassis management module further configures a virtual IP interface associated with a virtual IP virtual local area network (VIP VLAN) coupling the primary switch and the secondary switch to a MC-LAG as a stub network to prevent the virtual IP interface from sending and processing received Layer 3 routing control packets on the external ports.

12. The aggregation switch of claim 1, wherein the chassis management module further builds respective forwarding vectors for multicast traffic flows received from the network nodes via the external ports or the VLF ports based on the snooping information.

13. The aggregation switch of claim 12, wherein the chassis management module further determines a multicast index for a received multicast traffic flow to set-up hardware paths for forwarding the received multicast traffic flow to the external ports in a virtual local area network (VLAN) that requested the received multicast traffic flow via the at least one edge node, the multicast index being used globally between the aggregation switch and the remote aggregation switch.

14. The aggregation switch of claim 13, wherein the chassis management module further builds the forwarding vector for the received multicast traffic flow based on the multicast index.

15. The aggregation switch of claim 13, wherein the aggregation switch is a primary switch and the remote aggregation switch is a secondary switch, and wherein the chassis management module on the primary switch allocates the multicast index for the received multicast traffic flow and shares the multicast index with the secondary switch.

16. The aggregation switch of claim 13, wherein the aggregation switch is a secondary switch and the remote aggregation switch is a primary switch, and wherein the chassis management module on the secondary switch is prevented from allocating the multicast index for the received multicast traffic flow and receives the multicast index from the primary switch.

17. A method for performing Internet Protocol (IP) multicast snooping on an aggregation switch in a multi-chassis system, comprising:

receiving snooping information via at least external ports coupled to at least one edge node and at least one network node;

storing the snooping information within a database; and

sharing the snooping information substantially in real-time with a remote aggregation switch via a virtual fabric link (VFL) therebetween, wherein the remote aggregation switch is active and in a separate physical chassis.

18. The method of claim 17, wherein one or more of the external ports are member ports of a multi-chassis link aggregation group (MC-LAG) connected to an edge node and the remote aggregation switch includes one or more of the member ports of the MC-LAG connected to the edge node and wherein the receiving the snooping information further includes:

receiving a portion of the snooping information from the remote aggregation switch via the VFL, the portion of the snooping information having remote hardware device information associated therewith, the remote hardware device information including a remote external port identifier of a remote external port that received the snooping information on the remote aggregation switch.

19. The method of claim 18, further comprising:

determining whether the remote hardware device information identifies one of the member ports of the MC-LAG on the remote aggregation switch;

when the remote hardware device information identifies one of the member ports of the MC-LAG on the remote aggregation switch, determining a local member port of the MC-LAG on the aggregation switch and storing a membership record and local hardware device information of the local member port of the MC-LAG in the database for the portion of the snooping information; and

when the source hardware device information does not identify one of the member ports of the MC-LAG on the remote aggregation switch, storing the membership record and VFL hardware device information of the VFL in the database for the portion of the snooping information.

20. The method of claim 17, wherein the aggregation switch is a primary switch and the remote aggregation switch is a secondary switch, and further comprising:

configuring a virtual IP interface associated with a virtual IP virtual local area network (VIP VLAN) coupling the primary switch and the secondary switch to a MC-LAG as a stub network to prevent the virtual IP interface from sending and processing received Layer 3 routing control packets on the external ports, the virtual IP interface being further configured as a designated Protocol Independent Multicast (PIM) router for the VIP VLAN;

configuring a network IP interface associated with a VLAN coupling the primary switch to a network node as a normal IP interface to enable the network interface to send and receive Layer 3 routing control packets for the VIP VLAN on the external ports; and

providing the snooping information to the network IP interface to enable the network IP interface to send and receive the Layer 3 routing control packets on the external ports.

21. The method of claim 17, wherein the aggregation switch is a secondary switch and the remote aggregation switch is a primary switch, and further comprising:

configuring a virtual IP interface associated with a virtual IP virtual local area network (VIP VLAN) coupling the primary switch and the secondary switch to a MC-LAG as a stub network to prevent the virtual IP interface from sending and processing received Layer 3 routing control packets on the external ports.