Egress node protection for broadcast, unknown unicast, or multicast traffic in EVPN topologies

Patent metadata

Field	Value
Publication number	US-10567279-B2
Application number	US-201816100565-A
Country	US
Kind code	B2
Filing date	Aug 10, 2018
Priority date	May 17, 2016
Publication date	Feb 18, 2020
Grant date	Feb 18, 2020

Abstract

A first device may receive network traffic including a first label. The first label may be an inclusive multicast label associated with a second device. The second device may be a designated forwarder for an Ethernet segment. The first device may determine a second label based on receiving the network traffic including the first label. The second label may be used to route the network traffic to a customer edge device, via a third device, rather than the second device. The third device may be a non-designated forwarder for the Ethernet segment. The first device may provide the network traffic, including the second label, to the third device to permit the third device to provide, via the Ethernet segment, the network traffic to the customer edge device based on the second label when a failure occurs in association with the second device.

First claim

What is claimed is:

1. A first device, comprising:
one or more memories; and
one or more processors to:
establish a peering session with a second device;
determine a failure associated with the second device,
the second device being a designated forwarder for an Ethernet segment associated with an Ethernet virtual private network instance;

receive network traffic including a first label,
the first label being a multicast label associated with the second device,
the network traffic being broadcast, unknown unicast, or multicast traffic associated with the Ethernet virtual private network instance;

receive information, from the second device, that identifies a second label,
the second label being used to route the network traffic to a customer edge device, via a third device rather than the second device, in an event of the failure associated with the second device;

store the information that identifies the second label based on receiving the information that identifies the second label;
determine the second label based on receiving the information that identifies the second label; and
provide the network traffic, including the second label, to the third device to permit the third device to provide, via the Ethernet segment, the network traffic to the customer edge device based on the information that identifies the second label.

2. The first device of claim 1 , where the one or more processors, when determining the failure associated with the second device, are to:
determine the failure after establishing the peering session with the second device.

3. The first device of claim 1 , where the one or more processors are further to:
determine a third label associated with the network traffic,
the third label being a transport label associated with the second device; and

where the one or more processors, when determining the second label, are to:
determine the second label based on the third label associated with the network traffic.

4. The first device of claim 1 , where the one or more processors are further to:
store information that identifies the first label and an operation associated with the first label,
the operation being associated with removing the first label from the network traffic and including the second label with the network traffic; and

where the one or more processors, when providing the network traffic to the third device, are to:
provide the network traffic to the third device based on the information that identifies the first label and the operation associated with the first label.

5. The first device of claim 1 , where the one or more processors are further to:
determine a third label associated with the network traffic,
the third label being a transport label that identifies the second device; and

perform a lookup using a data structure based on the third label; and
where the one or more processors, when determining the second label, are to:
determine the second label based on performing the lookup using the data structure.

6. The first device of claim 1 , where the failure associated with the second device is at least one of:
a failure of a first link between the first device and the second device;
a failure of the second device; or
a failure of a second link between the second device and the customer edge device.

7. A non-transitory computer-readable medium storing instructions, the instructions comprising:
one or more instructions that, when executed by one or more processors of a first device, cause the one or more processors to:
establish a peering session with a second device;
receive network traffic including a first label,
the first label being a multicast label associated with the second device,
the second device being a designated forwarder for an Ethernet segment;

determine a second label based on receiving the network traffic including the first label,
the second label being used to route the network traffic to a customer edge device, via a third device, rather than the second device,

the third device being a non-designated forwarder for the Ethernet segment;
store information that identifies the first label and an operation associated with the first label,
the operation being associated with removing the first label from the network traffic and including the second label with the network traffic; and

provide the network traffic, including the second label, to the third device to permit the third device to provide, via the Ethernet segment, the network traffic to the customer edge device based on the information that identifies the first label and the operation associated with the first label.

8. The non-transitory computer-readable medium of claim 7 , where the one or more instructions, that cause the one or more processors to determine the second label, cause the one or more processors to:
determine the second label based on the peering session.

9. The non-transitory computer-readable medium of claim 7 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
determine a third label associated with the network traffic,
the third label being a transport label that identifies the second device; and

perform a lookup using a data structure based on the third label; and
where the one or more instructions, that cause the one or more processors to determine the second label, cause the one or more processors to:
determine the second label based on performing the lookup using the data structure.

10. The non-transitory computer-readable medium of claim 7 , where the one or more instructions, when executed by the one or more processors, further cause the one or more processors to:
store route information associated the second device; and
where the one or more instructions, that cause the one or more processors to determine the second label, cause the one or more processors to:
determine the second label based on the route information.

11. The non-transitory computer-readable medium of claim 7 , where the first device is a penultimate hop associated with an Ethernet virtual private network instance.

12. The non-transitory computer-readable medium of claim 7 , where a failure associated with the second device is at least one of:
a failure of a first link between the first device and the second device;
a failure of the second device; or
a failure of a second link between the second device and the customer edge device.

13. A method, comprising:
establishing, between a first device and a second device, a peering session;
determining, by the first device, a failure associated with the second device,
the second device being a designated forwarder for an Ethernet segment associated with an Ethernet virtual private network instance;

receiving, by the first device, network traffic including a first label,
the first label being a multicast label associated with the second device;

determining, by the first device, a second label based on receiving the network traffic including the first label and based on determining the failure associated with the second device,
where determining the second label comprises:
determining the second label based on a third label associated with the network traffic;

determining, by the first device, the third label associated with the network traffic,
the third label indicating that the network traffic is to be forwarded to the second device; and

providing, by the first device, to a third device, and without providing to the second device, the network traffic including the second label to permit the third device to provide,

Assignees

• Juniper Networks Inc

Inventors

• Arora Kapil
• Singh Nitin
• Malali Sunil Kumar
• Nagarajan Vikram

Classifications

• H04L12/4666

  Operational details on the addition or the stripping of a tag in a frame, e.g. at a provider edge node · CPC title

• H04L12/1886

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

• H04L12/4641 Primary

  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 title

• H04L41/0654

  using network fault recovery (ring fault isolation or reconfiguration in loop networks without recovery actions by a network management system H04L12/437) · CPC title

• H04L45/28

  using route fault recovery · CPC title