Multicast source discovery mechanism to avoid multicast-traffic sync between active multi-homing peers or any cast gateway L2 stretch

Patent metadata

Field	Value
Publication number	US-10862697-B2
Application number	US-201916293447-A
Country	US
Kind code	B2
Filing date	Mar 5, 2019
Priority date	Mar 5, 2019
Publication date	Dec 8, 2020
Grant date	Dec 8, 2020

Abstract

Systems, methods, and computer-readable media for controlling multicast traffic flows through provider edge routers. In some examples, a multicast traffic of one or more multicast traffic flows is received from a multicast source at a first provider edge router of a plurality of provider edge routers. A multicast routing message including a loopback address of the first provider edge router can be originated at the first provider edge router. The multicast routing message can be flooded into a multicast core network for controlling traffic in the one or more multicast flows through the multicast core network to the first provider edge router. Subsequently, multicast joins can be received at the first provider edge router for establishing the one or more multicast flows through the multicast core network based on the multicast routing message including the loopback address of the first provider edge router.

First claim

What is claimed is:

1. A method comprising:
receiving, at a first provider edge router of a plurality of provider edge routers, multicast traffic of one or more multicast flows from a multicast source;
refraining from transmitting the multicast traffic from the first provider edge router to at least one other edge router of the plurality of provider edge routers in response to receiving the multicast traffic from the multicast source;
originating, at the first provider edge router in response to receiving the multicast traffic from the multicast source, a multicast routing message including a multicast source indicator of the multicast source, a multicast group identifier of the multicast traffic, and a loopback address of the first provider edge router;
flooding the multicast routing message into a multicast core network, from the first provider edge router, for controlling traffic in the one or more multicast flows extending through at least a portion of the multicast core network to the first provider edge router; and
receiving one or more multicast joins at the first provider edge router from the multicast core network for establishing the one or more multicast flows through the multicast core network to the first provider edge router based on the multicast routing message including the loopback address of the first provider edge router.

2. The method of claim 1 , wherein the multicast routing message is a PIM flooding mechanism and source discovery (PFM-SD) message and the multicast routing message is flooded into the multicast core network.

3. The method of claim 1 , wherein the loopback address of the first provider edge router is included in the multicast routing message as a type-length value (TLV).

4. The method of claim 1 , wherein the first provider edge router and the at least one other edge router of the plurality of provider edge routers are connected to the multicast source through all active multihoming.

5. The method of claim 4 , wherein the multicast routing message including the loopback address of the first provider edge router is flooded to the multicast core network while refraining from replicating the multicast traffic across the at least one of the plurality of provider edge routers.

6. The method of claim 1 , wherein the first provider edge router periodically floods the multicast routing message into the multicast core network as the first provider edge router receives the multicast traffic from the multicast source.

7. The method of claim 1 , further comprising:
receiving, at a second provider edge router of the plurality of provider edge routers, additional multicast traffic of the one or more multicast flows from the multicast source;
originating, at the second provider edge router, another multicast routing message including the multicast source indicator of the multicast source, the multicast group identifier of the additional multicast traffic, and a loopback address of the second provider edge router, wherein the loopback address of the second provider edge router is different than the loopback address of the first provider edge router;
flooding the another multicast routing message into the multicast core network for controlling the traffic in the one or more multicast flows through the multicast core network to the second provider edge router; and
receiving one or more additional multicast joins at the second provider edge router from the multicast core network for re-establishing the one or more multicast flows through the multicast core network to the second provider edge router based on the another multicast routing message including the loopback address of the second provider edge router.

8. The method of claim 1 , wherein the multicast source is concurrently connected in multicast flows to both the first provider edge router and a second provider edge router of the plurality of provider edge routers for providing multicast traffic in different multicast groups including a first multicast group of the multicast traffic sent to the first provider edge router and a second multicast group of additional multicast traffic sent to the second provider edge router.

9. The method of claim 1 , wherein at least one of the plurality of provider edge routers is connected to the multicast source through a layer 2 stretch connection.

10. The method of claim 9 , wherein the at least one of the plurality of provider edge routers has the same integrated routing and bridging (IRB) IP address as the first provider edge router.

11. The method of claim 9 , wherein the multicast routing message including the loopback address of the first provider edge router is flooded to the multicast core network while refraining from replicating the multicast traffic across the at least one of the plurality of provider edge routers through the layer 2 stretch connection.

12. The method of claim 1 , further comprising:
identifying, by the first provider edge router, that the first provider edge router is no longer receiving the multicast traffic from the multicast source;
generating, by the first provider edge router, a clear flag multicast routing message to clear an association of the loopback address of the first provider edge router with the multicast source indicator of the multicast source and the multicast group identifier of the multicast traffic; and
flooding the clear flag multicast routing message into the multicast core network for controlling traffic in the one or more multicast flows through the multicast core network.

13. The method of claim 1 , further comprising:
receiving, by two or more provider edge routers of the plurality of provider edge routers including the first provider edge router, the multicast traffic from the multicast source;
determining, by the two or more provider edge routers, whether to flood the multicast core network with multicast routing messages for the multicast traffic based on loopback addresses of the two or more provider edge routers; and
flooding the multicast routing message into the multicast core network from the first provider edge router, if it is determined to flood the multicast routing message for the multicast traffic into the multicast core network based on the loopback addresses of the two or more provider edge routers.

14. The method of claim 13 , wherein the multicast traffic is received at the two or more provider edge routers from the multicast source based on different user datagram protocol ports.

15. A system comprising:
one or more processors; and
at least one computer-readable storage medium having stored therein instructions which, when executed by the one or more processors, cause the one or more processors to perform operations comprising:
receiving, at a first provider edge router of a plurality of provider edge routers, multicast traffic of one or more multicast flows from a multicast source;
refraining from transmitting the multicast traffic from the first provider edge router to at least one other edge router of the plurality of provider edge routers in response to receiving the multicast traffic from the multicast source;
originating, at the first provider edge router in response to receiving the multicast traffic from the multicast source, a multicast routing message including a multicast source indicator of the multicast source, a multicast group identifier of the multicast traffic, and a loopback address of the first provider edge router as a type-length value (TLV) included as part of the multicast routing message;
flooding the multicast routing message into a multicast core network, from the first provider edge router, fo

Assignees

• Cisco Tech Inc

Inventors

• Mishra Mankamana Prasad
• Sajassi Ali
• Thoria Samir
• Wijnands Ijsbrand
• Ginsberg Lester C

Classifications

• H04L12/1886 Primary

  with traffic restrictions for efficiency improvement, e.g. involving subnets or subdomains · CPC title

• H04L12/4675 Primary

  Dynamic sharing of VLAN information amongst network nodes (configuration of the network or of network elements H04L41/08) · CPC title

• H04L45/50

  using label swapping, e.g. multi-protocol label switch [MPLS] · CPC title

• H04L45/16

  Multipoint routing · CPC title

• H04L45/02

  Topology update or discovery · CPC title