# US 12,764,063 B2 · Adaptive filtering of bum traffic in ethernet virtual private network

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

- Number: US 12,764,063 B2
- Document ID: US12764063B2
- Status: Granted
- Kind: B2
- Application number: 18/490,127
- Filed: 2023-10-19
- Published: 2024-10-24
- Granted: 2026-10-13
- Earliest claimed: 2023-04-19
- Assignees: Cisco Technology, Inc.
- Applicants: Cisco Technology, Inc.
- Inventors: Ali Sajassi; Ramchander R Nadipally; Neeraj Malhotra
- Web page: https://patentgrep.com/patent/US12764063B2

## CPC

- H04L 45/32: {Flooding (denial of service attacks H04L63/1458)}
- H04L 45/02: Topology update or discovery
- H04L 45/76: Routing in software-defined topologies, e.g. routing between virtual machines
- H04L: TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION (arrangements common to telegraphic and telephonic communication H04M)

## Abstract

In one aspect, a method includes receiving, at a first PE in a network of EVPNs, one or more of information on status of one or more nodes connected to the first PE, the one or more nodes being one of a leaf node or a root node; and a respective advertisement message from one or more second PEs. The method further includes performing one or more of generating, based on the information, a route advertisement message indicative of the status of the one or more nodes connected to the first PE, wherein the route advertisement message is shared with one or more second PEs; and based on the respective advertisement message received from each of the one or more second PEs, dynamically adjust configurations at the first PE, to perform ingress filtering or egress filtering of Broadcast, Unknown Unicast, and Multicast (BUM) traffic received at the first PE.

## Claims

### Claim 1

A method comprising:
receiving, at a first Provider Edge (PE) of a first Ethernet Virtual Private Network (EVPN) in an inter-connected network of EVPNs:
information on status of one or more nodes connected to the first PE, the one or more nodes being one of a leaf node or a root node, the status indicating whether each of the one or more nodes is one of a leaf node or a root node and whether the node is active or inactive; and
a respective advertisement message from one or more second PEs of one or more second EVPNs in the inter-connected network of EVPNs; and
performing, at the first PE:
generating, based on the information, a route advertisement message indicative of the status of the one or more nodes connected to the first PE, wherein the route advertisement message is shared with one or more second PEs; and
based on the respective advertisement message received from each of the one or more second PEs and the status of the one or more nodes connected to the first PE, dynamically adjusting configurations at the first PE, to switch between ingress filtering and egress filtering of Broadcast, Unknown Unicast, and Multicast (BUM) traffic received at the first PE.

### Claim 2 (depends on 1)

The method of claim 1, further comprising:
generating a first flood list, the first flood list encompassing all PEs in the inter-connected network of EVPNs; and
generating a second flood list, the second flood list excluding any of the one or more second PEs with only a leaf indication included in the respective advertisement message received therefrom.

### Claim 3 (depends on 2)

The method of claim 2, further comprising:
receiving the BUM traffic, at the first PE, from the leaf node attached to the first PE; and performing ingress filtering of the BUM traffic received at first PE from the leaf node to prevent the BUM traffic from being sent to the any of the one or more second PEs with only the leaf indication.

### Claim 4 (depends on 3)

The method of claim 3, wherein the ingress filtering includes sending the BUM traffic to all PEs included in the second flood list.

### Claim 5 (depends on 4)

The method of claim 4, wherein the BUM traffic is sent to all PEs in the second flood list with a leaf VxLAN Network Identifier (VNI) identifying the BUM traffic as being from a leaf node, the leaf VNI enabling a receiving PE from among the one or more second PEs to perform egress filtering prior to sending the BUM traffic to a leaf node associated with the receiving PE.

### Claim 6 (depends on 2)

The method of claim 2, further comprising:
receiving the BUM traffic, at the first PE, from one of the one or more second PEs; and determining whether to perform egress filtering of the BUM traffic based on a VxLAN Network Identifier (VNI) associated with the BUM traffic.

### Claim 7 (depends on 6)

The method of claim 6, wherein the first PE performs egress filtering of the BUM traffic if the VNI associated with the BUM traffic identifies the BUM traffic as originating from a leaf node attached to the one of the one or more second PEs from which the BUM traffic is received, and one of the one or more nodes is the leaf node.

### Claim 8

An inter-connected network of Ethernet Virtual Private Networks (EVPNs), comprising:
a plurality of Provider Edges (PEs) including a first PE and one or more second PEs, wherein the first PE is configured to:
receive information on status of one or more nodes connected to the first PE, the one or more nodes being one of a leaf node or a root node, the status indicating whether each of the one or more nodes is one of a leaf node or a root node and whether the node is active or inactive;
receive a respective advertisement message from the one or more second PEs;
generate, based on the information, a route advertisement message indicative of the status of the one or more nodes connected to the first PE, wherein the route advertisement message is shared with one or more second PEs; and
based on the respective advertisement message received from each of the one or more second PEs and the status of the one or more nodes connected to the first PE, dynamically adjust configurations at the first PE, to switch between ingress filtering and egress filtering of Broadcast, Unknown Unicast, and Multicast (BUM) traffic received at the first PE.

### Claim 9 (depends on 8)

The inter-connected network EVPNs of claim 8, wherein the first PE is further configured to:
generate a first flood list, the first flood list encompassing all PEs in the inter-connected network of EVPNs; and
generate a second flood list, the second flood list excluding any of the one or more second PEs with only a leaf indication included in the respective advertisement message received therefrom.

### Claim 10 (depends on 9)

The inter-connected network of EVPNs of claim 9, wherein the first PE is further configured to:
receive the BUM traffic, at the first PE, from the leaf node attached to the first PE; and
perform ingress filtering of the BUM traffic received at first PE from the leaf node to prevent the BUM traffic from being sent to the any of the one or more second PEs with only the leaf indication.

### Claim 11 (depends on 10)

The inter-connected network EVPNs of claim 10, wherein the ingress filtering includes sending the BUM traffic to all PEs included in the second flood list.

### Claim 12 (depends on 11)

The inter-connected network EVPNs of claim 11, wherein the BUM traffic is sent to all PEs in the second flood list with a leaf VxLAN Network Identifier (VNI) identifying the BUM traffic as being from a leaf node, the leaf VNI enabling a receiving PE from among the one or more second PEs to perform egress filtering prior to sending the BUM traffic to a leaf node associated with the receiving PE.

### Claim 13 (depends on 9)

The inter-connected network EVPNs of claim 9, wherein the first PE is further configured to:
receive the BUM traffic, at the first PE, from one of the one or more second PEs; and determine whether to perform egress filtering of the BUM traffic based on a VxLAN Network Identifier (VNI) associated with the BUM traffic.

### Claim 14 (depends on 13)

The inter-connected network EVPNs of claim 13, wherein the first PE performs egress filtering of the BUM traffic if the VNI associated with the BUM traffic identifies the BUM traffic as originating from a leaf node attached to the one of the one or more second PEs from which the BUM traffic is received, and one of the one or more nodes is the leaf node.

### Claim 15

One or more non-transitory computer-readable media comprising computer-readable instructions, which when executed by one or more processors at a first Provider Edge (PE) of an inter-connected network of Ethernet Virtual Private Networks (EVPNs), cause the first PE to:
receive information on status of one or more nodes connected to the first PE, the one or more nodes being one of a leaf node or a root node, the status indicating whether each of the one or more nodes is one of a leaf node or a root node and whether the node is active or inactive;
receive a respective advertisement message from one or more second PEs of one or more second EVPNs in the inter-connected network of EVPNs;
generate, based on the information, a route advertisement message indicative of the status of the one or more nodes connected to the first PE, wherein the route advertisement message is shared with one or more second PEs; and
based on the respective advertisement message received from each of the one or more second PEs and the status of the one or more nodes connected to the first PE, dynamically adjust configurations at the first PE, to switch between ingress filtering and egress filtering of Broadcast, Unknown Unicast, and Multicast (BUM) traffic received at the first PE.

### Claim 16 (depends on 15)

The one or more non-transitory computer-readable media of claim 15, wherein the execution of the computer-readable instructions further cause the first PE to:
generate a first flood list, the first flood list encompassing all PEs in the inter-connected network of EVPNs; and
generate a second flood list, the second flood list excluding any of the one or more second PEs with only a leaf indication included in the respective advertisement message received therefrom.

### Claim 17 (depends on 16)

The one or more non-transitory computer-readable media of claim 16, wherein the execution of the computer-readable instructions further cause the first PE to:
receive the BUM traffic, at the first PE, from the leaf node attached to the first PE; and
perform ingress filtering of the BUM traffic received at first PE from the leaf node to prevent the BUM traffic from being sent to the any of the one or more second PEs with only the leaf indication.

### Claim 18 (depends on 17)

The one or more non-transitory computer-readable media of claim 17, wherein the ingress filtering includes sending the BUM traffic to all PEs included in the second flood list.

### Claim 19 (depends on 18)

The one or more non-transitory computer-readable media of claim 18, wherein the BUM traffic is sent to all PEs in the second flood list with a leaf VxLAN Network Identifier (VNI) identifying the BUM traffic as being from a leaf node, the leaf VNI enabling a receiving PE from among the one or more second PEs to perform egress filtering prior to sending the BUM traffic to a leaf node associated with the receiving PE.

### Claim 20 (depends on 16)

The one or more non-transitory computer-readable media of claim 16, wherein the execution of the computer-readable instructions further cause the first PE to:
receive the BUM traffic, at the first PE, from one of the one or more second PEs; and determine whether to perform egress filtering of the BUM traffic based on a VxLAN Network Identifier (VNI) associated with the BUM traffic.
