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

Patent metadata

Field	Value
Publication number	US-10050873-B2
Application number	US-201615157058-A
Country	US
Kind code	B2
Filing date	May 17, 2016
Priority date	May 17, 2016
Publication date	Aug 14, 2018
Grant date	Aug 14, 2018

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:
determine a failure associated with a 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;

determine a second label based on the first label and based on determining the failure associated with the second device;
determine a third label associated with the network traffic,
the third label being determined based on the second label associated with the network traffic, and
the third 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; and

provide the network traffic, including the third 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 third label.

2. The first device of claim 1 , where the one or more processors are further to:
receive information, from the second device, that identifies the second label; and
store the information that identifies the second label based on receiving the information that identifies the second label.

3. The first device of claim 1 , where the third device is a non-designated forwarder for the Ethernet segment.

4. The first device of claim 1 , where the one or more processors are further to:
receive configuration information that identifies that the third device is to provide, to the customer edge device, the network traffic based on the failure associated with the second device; 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 configuration information.

5. The first device of claim 1 , where the one or more processors are further to:
establish a peering session with the second device; and
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.

6. The first device of claim 1 , where the one or more processors are further to:
receive route information from the second device; and
store the route information based on receiving the route information, the route information including the first label; and
where the one or more processors, when determining the second label, are to:
determine the second label based on the route information.

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:
receive network traffic including a first label,
the first label being a multicast label associated with a 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;
determine a third label associated with the network traffic,
the third label being determined based on the second label associated with the network traffic,
the third label being used to route network traffic to a customer edge device, via a third device rather than the second device, in an event of failure associated with the second device; and

provide the network traffic, including the third 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 third label when a failure occurs in association with the second device.

8. 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 that the failure occurred in association with 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 determining that the failure occurred in association with the second device.

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:
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 third label with the network traffic; and

where the one or more instructions, that cause the one or more processors to provide the network traffic to the third device, cause the one or more processors 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.

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:
establish a peering session with 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 peering session.

11. 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:
receive configuration information that identifies that the third device is to provide the network traffic to the customer edge device in an event of a failure associated with the second device; and
where the one or more instructions, that cause the one or more processors to provide the network traffic to the third device, cause the one or more processors to:
provide the network traffic to the third device based on the configuration information.

12. 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:
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.

13. A method, comprising:
determining, by a first device, a failure associated with a 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;
determining, by the first device, a third label associated with the network traffic,
the third label being determined based on the second label associated with the network traffic, and
the third label being used to route the ne

Assignees

• Juniper Networks Inc

Inventors

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

Classifications

• H04L12/4675

  Dynamic sharing of VLAN information amongst network nodes (configuration of the network or of network elements H04L41/08) · 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

• 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

• H04L45/50 Primary

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

• H04L12/18

  for broadcast or conference {, e.g. multicast} · CPC title