# US 2017/0289216 A1 · Hot root standby support for multicast

> Agents: this data is available as JSON from the patentgrep API and MCP server — see https://patentgrep.com/llms.txt

- Number: US 2017/0289216 A1
- Document ID: US20170289216A1
- Status: Published application
- Kind: A1
- Application number: 15/085,843
- Filed: 2016-03-30
- Published: 2017-10-05
- Earliest claimed: 2016-03-30
- Assignees: Juniper Networks, Inc.
- Applicants: Juniper Networks, Inc.
- Inventors: Vinod Kumar N; Sudarsanan Codandam
- Web page: https://patentgrep.com/patent/US20170289216A1

## CPC

- H04L 45/22: {Alternate routing}
- H04L 45/24: Multipath
- H04L 45/243: using M+N parallel active paths
- H04L 45/28: using route fault recovery
- H04L 45/50: using label swapping, e.g. multi-protocol label switch [MPLS]
- H04L 65/611: for multicast or broadcast (systems for broadcast or conference H04L12/18; arrangements for broadcast or distribution combined with broadcast H04H20/00; arrangements for broadcast applications with a direct linkage to broadcast information or to broadcast space-time H04H60/00; selective distribution of broadcast services, e.g. multimedia broadcast multicast service [MBMS], H04W4/06)
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In general, techniques are described for providing Hot-Root Standby in Global Table Multicast (GTM) environments. For example, in such GTM environments, normally a single unicast route to the customer multicast source (“C-Source”) will be available to egress provider edge (PE) routers. As described herein, ingress PE routers may advertise multiple routes to a C-Source, including unicast routes that include Route Import Extended Communities, which are imported by egress PE routers. This enables an egress PE router to have multiple paths to the C-Source, and the egress PE router may generate multiple C-multicast source tree joins for respective ingress PE routers in order to receive respective multicast streams sourced by the C-Source from the ingress PE routers.

## Claims

### Claim 1

A method comprising:
receiving, by an egress provider edge (PE) router of a multi-protocol label switching (MPLS) network, a first unicast route to a source device of a customer site that is attached to a first ingress PE router and a second ingress PE router, the first unicast route originated by the first ingress PE router and having a route distinguisher value of zero;
receiving, by the egress PE router, a second unicast route to the source device, the second unicast route originated by the second ingress PE router and having a route distinguisher value of zero;
storing, by the egress PE router to a global routing table of the egress PE router, a first multicast source tree join route that specifies a customer-multicast flow sourced by the source device, the first multicast source tree join route having a first route distinguisher value; and
storing, by the egress PE router to the global routing table of the egress PE router, a second multicast source tree join route that specifies the customer-multicast flow sourced by the source device, the second multicast source tree join route having a second route distinguisher value different than the first route distinguisher.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
outputting, by the egress PE router, the first multicast source tree join route, the first multicast source tree join route having a first route target that causes the first ingress PE router to import the first multicast source tree join route to a global routing table of the first ingress PE router and send first multicast traffic from the source device to the egress PE router; and
outputting, by the egress PE router, the second multicast source tree join route, the second multicast source tree join route having a second route target that causes the second ingress PE router to import the second multicast source tree join route to a global routing table of the second ingress PE router and send second multicast traffic from the source device to the egress PE router.

### Claim 3 (depends on 2)

The method of claim 2,
wherein the first route target is drawn from a Route Import Extended Community value of the first unicast route, and
wherein the second route target is drawn from a Route Import Extended Community value of the second unicast route.

### Claim 4 (depends on 1)

The method of claim 1,
wherein the first route distinguisher value comprises a value of a Route Import Extended Community of the first unicast route, and
wherein the second route distinguisher value comprises a value of a Route Import Extended Community of the second unicast route.

### Claim 5 (depends on 4)

The method of claim 4,
wherein the first route distinguisher value comprises an IP address of the first ingress PE router included in the Route Import Extended Community of the first unicast route, and
wherein the second route distinguisher value comprises an IP address of the second ingress PE router included in the Route Import Extended Community of the second unicast route.

### Claim 6 (depends on 1)

The method of claim 1, further comprising:
storing, by the egress PE router in response to determining the route distinguisher value is zero for the first and second unicast routes, the first and second unicast routes to a global routing table that is not specific to any virtual private network.

### Claim 7 (depends on 1)

The method of claim 1, wherein the first and second unicast routes are received using BGP Add-Path procedures.

### Claim 8 (depends on 1)

The method of claim 1, wherein the first and second multicast source tree join routes comprise C-Multicast routes, and wherein the first and second multicast source tree join routes specify the customer-multicast flow by specifying the same (C-S, C-G) pair.

### Claim 9 (depends on 1)

The method of claim 1, wherein the egress PE router is operating in Hot-Standby Mode with respect to a first multicast stream and a second multicast stream from the source device.

### Claim 10

A method comprising:
receiving, by an egress provider edge (PE) router of a multi-protocol label switching (MPLS) network, a first unicast route to a source device of a customer site that is attached to a first ingress PE router and a second ingress PE router, the first unicast route originated by the first ingress PE router and having a route distinguisher value of zero;
receiving, by the egress PE router, a second unicast route to the source device, the second unicast route originated by the second ingress PE router and having a route distinguisher value of zero; and
storing, by the egress PE router to a global routing table of the egress PE router, a multicast source tree join route that specifies a customer-multicast flow sourced by the source device, the multicast source tree join route having a route distinguisher value of zero and a plurality of route targets to cause each of the first ingress PE router and the second ingress PE router to import the multicast source tree join route when advertised by the egress PE router.

### Claim 11 (depends on 10)

The method of claim 10, further comprising:
outputting, by the egress PE router, the multicast source tree join route with the plurality of route targets to the first and second ingress PE routers, wherein the plurality of route targets comprises IP addresses of the first and second ingress PE routers.

### Claim 12 (depends on 10)

The method of claim 10, wherein the plurality of route targets are taken from corresponding Route Import Extended Communities of the first and second unicast routes.

### Claim 13 (depends on 10)

The method of claim 10, further comprising:
storing, by the egress PE router in response to determining the route distinguisher value is zero for the first and second unicast routes, the first and second unicast routes to a global routing table that is not specific to any virtual private network.

### Claim 14 (depends on 10)

The method of claim 10, wherein receiving the first and second unicast routes are received based on BGP Add-Path procedures.

### Claim 15 (depends on 10)

The method of claim 10, wherein the first and second multicast source tree join routes are C-Multicast routes, and wherein the first and second multicast source tree join routes specify the customer-multicast flow by specifying the same (C-S, C-G) pair.

### Claim 16 (depends on 10)

The method of claim 10, wherein the egress PE router is operating in Hot-Standby Mode with respect to the first multicast stream and the second multicast stream.

### Claim 17

A provider edge (PE) router comprising:
a forwarding unit coupled to one or more network interface cards;
a routing unit comprising at least one processor operably coupled to a memory, the routing unit configured to:
receive a first unicast route to a source device that is attached to a first ingress PE router and a second ingress PE router, the first unicast route originated by the first ingress PE router and having a route distinguisher value of zero;
receive a second unicast route to the source device, the second unicast route originated by the second ingress PE router and having a route distinguisher value of zero;
store, to a global routing table, a first multicast source tree join route that specifies a customer-multicast flow sourced by the source device, the first multicast source tree join route having a first route distinguisher value; and
store, to the global routing table, a second multicast source tree join route that specifies the customer-multicast flow sourced by the source device, the second multicast source tree join route having a second route distinguisher value different than the first route distinguisher.

### Claim 18 (depends on 17)

The provider edge router of claim 17, wherein the routing unit is further configured to:
output the first multicast source tree join route, the first multicast source tree join route having a route target that causes the first ingress PE router to import the first multicast source tree join route to a global routing table of the first ingress PE router and send first multicast traffic from the source device to the egress PE router; and
output the second multicast source tree join route, the second multicast source tree join route having a route target that causes the second ingress PE router to import the second multicast source tree join route to a global routing table of the second ingress PE router and send second multicast traffic from the source device to the egress PE router.

### Claim 19

A system comprising:
a multicast source device of a first customer site;
a multicast receiver device of a second customer site;
an egress provider edge (PE) router on a multi-protocol label switching (MPLS) network and attached to the second customer site; and
a first ingress PE router and second ingress PE router attached to the first customer site,
wherein the egress PE router is configured to:
receive a first unicast route to the multicast source device, the first unicast route originated by the first ingress PE router and having a route distinguisher value of zero;
receive a second unicast route to the multicast source device, the second unicast route originated by the second ingress PE router and having a route distinguisher value of zero;
store, to a global routing table, a first multicast source tree join route that specifies a customer-multicast flow sourced by the source device, the first multicast source tree join route having a first route distinguisher value; and
store, to the global routing table, a second multicast source tree join route that specifies the customer-multicast flow sourced by the source device, the second multicast source tree join route having a second route distinguisher value different than the first route distinguisher.

### Claim 20 (depends on 19)

The system of claim 19, wherein the egress PE router is further configured to:
output the first multicast source tree join route, the first multicast source tree join route having a first route target that causes the first ingress PE router to import the first multicast source tree join route to a global routing table of the first ingress PE router and send first multicast traffic from the source device to the egress PE router; and
output the second multicast source tree join route, the second multicast source tree join route having a second route target that causes the second ingress PE router to import the second multicast source tree join route to a global routing table of the second ingress PE router and send second multicast traffic from the source device to the egress PE router.
