Granular Control of Multicast Delivery Services for Layer-2 Interconnect Solutions

• US 20130021942A1
• Filed: 07/18/2011
• Published: 01/24/2013
• Est. Priority Date: 07/18/2011
• Status: Abandoned Application

• Current Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Original Assignee: Cisco Technology, Inc. (Cisco Systems, Inc.)
• Inventors: Grover, Hasmit, Sivaramu, Raghava, Bacthu, Nataraj, Chippa, Ashok
• Application Number:
  US13/185,326
• Publication Number:
  US 20130021942A1
• Time in Patent Office: Days
• US Class Current: 370/254
• CPC Class Codes: H04L 12/1836 with heterogeneous network architecture
• CPC Class Codes: H04L 12/4641 Virtual LANs, VLANs, e.g. virtual private networks [VPN] LAN interconnection over a bridge based backbone H04L12/462; encapsulation techniques H04L12/4633; routing of packets H04L45/00; packet switches H04L49/00; virtual private networks for security H04L63/0272
• CPC Class Codes: H04L 45/04 Interdomain routing, e.g. hierarchical routing
• CPC Class Codes: H04L 45/16 Multipoint routing
• CPC Class Codes: H04L 45/48 Routing tree calculation
• CPC Class Codes: H04L 45/484 using multiple routing trees
• CPC Class Codes: H04L 45/64 using an overlay routing layer

Abstract

In order to achieve optimized delivery of multicast traffic between L2 OTV sites across an L3 multicast service provider core infrastructure, embodiments of the present disclosure describe building different provider multicast data trees rooted at a source site for individual per-vlan (*,G)/(S,G) streams. Building such provider trees may require individual sites to discover multicast sources local to their network and subsequently announce to all receiver sites the multicast data trees (DS, DG) to be used to deliver such multicast traffic. The present disclosure describes the coordination between OTV edge devices for the (S,G) to (DS, DG) mapping originated by the source OTV edge device where the multicast traffic is originated.

Claims

1. A network device comprising:

a processor, wherein the processor is configured to;

detect a multicast traffic stream;

edit mapping information maintained in an L3 core network to reflect the mapping of the multicast traffic stream to the address of an L2 site associated with the network device; and

announce the edited mapping information to one or more L2 remote sites.

2. The network device of claim 1, wherein the network device is an edge device.

3. The network device of claim 1, wherein the processor is further configured to:

store mapping information in a multicast tree.

4. The network device of claim 2, wherein the processor is further configured to:

map the multicast traffic stream through core encapsulation with the L3 core network.

5. The network device of claim 1 where the multicast traffic stream originates with the L2 site associated with the network device.

6. The network device of claim 1, wherein the processor is further configured to:

store a plurality of multicast tress for individual per-vlan (*,G) /(S,G) streams.

7. The network device of claim 6, wherein the processor is further configured to:

forward the encapsulated stream to the L3 core network.

8. The network device of claim 7, wherein the processor is further configured to:

forward only one packet per frame of the encapsulated stream to the L3 core network.

9. A method comprising:

sending multicast traffic addressed to a first group;

editing a multicast tree by mapping the multicast traffic to an address associated with an L2 source site of the multicast traffic;

announcing the mapping to a plurality of L2 local sites;

determining that one or more remote network devices are interested in the first group;

encapsulating the multicast traffic; and

forwarding the multicast traffic to the interested remote network devices.

10. The method of claim 9, further comprising:

forwarding the encapsulated multicast traffic to an L3 core network.

11. The method of claim 9, further comprising:

receiving a multicast join from one of the plurality of interested remote network devices.

12. The method of claim 10, further comprising:

aggregating the multicast traffic with one or more multicast trees located in the L3 core network.

13. The method of claim 12, further comprising:

forwarding only one packet per frame of the encapsulated stream to the L3 core network.

14. The method of claim 13, further comprising:

storing the multicast tree in the L3 core network.

15. A method comprising:

receiving a mapping announcement from a first network device indicating a multicast traffic stream associated with a first group;

determining whether there are receivers interested in traffic associated with the first group;

if it is determined that there are receivers interested in traffic associated with the first group, sending a multicast join message;

receiving the multicast traffic stream; and

forwarding the multicast traffic stream to the interested receivers.

16. The method of claim 15 further comprising:

decapsulating the multicast traffic stream based on information in the mapping announcement.

17. The method of claim 15 wherein the mapping announcement is received from a source edge device.

18. The method of claim 17, wherein the mapping announcement includes the address of the source of the multicast traffic stream.

19. The method of claim 18, wherein the source edge device is located at the source of the multicast traffic stream.

20. The method of claim 15, wherein the multicast traffic stream is received from a core network.