EVPN Ingress Replication Across Multi-Tier Leaf-Spine Fabrics
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing ingress replication solutions for Ethernet Virtual Private Networks (EVPN) are limited by spine-leaf structure deployment to one or two layers, require manual configuration, and result in unnecessary information storage due to bridge domain provisioning in spine nodes.
Innovation Solution
Optimize ingress replication by defining depths and zones in a multi-tier leaf-spine network topology, using Inclusive Multicast Ethernet Tag (IMET) routes to carry depth and zone information, and designating upstream and downstream replicators to reduce unnecessary replication and enhance efficiency.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If ingress replication is deployed in traditional spine-leaf structure with 1 or 2 layers, then manual configuration is required and information storage overhead increases, but the patent enables multi-tier deployment with automated depth and zone definition
Solution Approach 1:
The patent segments the spine-leaf network into multiple tiers by defining depth values for different device levels and zones. Each spine device is assigned a specific depth, and replication is performed selectively within zones rather than globally across the entire network. This segmentation reduces the information storage requirement at each spine device while enabling flexible multi-tier deployment architectures.
2Extent of automation
If manual configuration is used for ingress replication, then deployment flexibility is reduced, but the patent implements automated depth and zone definition
Solution Approach 1:
The patent implements self-service automation where the control plane automatically defines depths and zones based on network topology, and automatically generates replication lists without manual configuration. Spine devices autonomously determine their depth values and identify appropriate downstream replicators within their zones, eliminating manual configuration overhead while managing control plane complexity through structured algorithms.
3Reliability
If bridge domain is provisioned in spine nodes, then replication coverage is comprehensive, but unnecessary information storage overhead increases
Solution Approach 1:
The patent applies local quality by defining zones that limit the scope of bridge domain provisioning to specific regions of the network rather than requiring all spine devices to store information about all bridge domains. Each spine device stores replication information only for its designated zone, maintaining reliable replication coverage within that zone while significantly reducing the quantity of information stored at each device.
4Productivity
If PIM-based trees are used for BUM traffic, then traffic efficiency is improved, but dependency on PIM control plane is created
Solution Approach 1:
The patent introduces an intermediary mechanism where the control plane defines depths and zones that mediate between the data plane replication actions and the underlying network topology. This intermediary layer enables automated, topology-aware ingress replication that achieves efficient BUM traffic conveyance similar to PIM-based trees, while eliminating direct dependency on PIM control plane protocols by using a simplified depth-zone-based control mechanism.
Data Source
AI summary
In one aspect, a method includes defining a corresponding depth for each leaf device and each spine device in a leaf-spine network fabric having a hierarchical structure; defining one or more zones in the leaf-spine network fabric; generating a corresponding replication list for each leaf device and one or more spine devices in the leaf-spine network fabric based at least in part of the corresponding depth and the one or more zones defined; and performing ingress replication of network traffic received at a given leaf device using the corresponding replication list of the given leaf device and the corresponding replication list of at least one of the one or more spine devices.