AC-Aware VLAN Bundle Service Interface for EVPN Subnet Isolation
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
EVPN-based multi-homing deployments face scalability and management challenges due to the need for separate bridge domains and IRB interfaces for each subnet, and conventional service interfaces cannot support multiple subnets within a single bridge domain, leading to complexity and cost issues.
Innovation Solution
The introduction of an attachment circuit (AC)-aware VLAN bundle service interface allows multiple subnets to be supported within a single bridge domain by using a new extended community (AC ID extended community) to pass VLAN information, enabling PE devices to synchronize MAC/IP addresses and forward packets correctly across subnets.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If separate bridge domains and IRB interfaces are used for each subnet, then subnet isolation and routing are ensured, but device complexity and management difficulty increase
Solution Approach 1:
The patent merges multiple subnets into a single bridge domain using a bundle service interface that can handle multiple VLANs simultaneously. Instead of creating separate bridge domains for each subnet, the invention combines them under one bridge domain with AC-aware VLAN bundle service, reducing the number of bridge domains and IRB interfaces needed while maintaining subnet isolation through VLAN tagging and AC identification.
Solution Approach 2:
The bundle service interface is designed to perform multiple functions: it can handle multiple subnets, maintain VLAN separation, provide routing services, and support EVPN multi-homing all within a single interface structure. This multi-functional approach replaces the need for multiple specialized interfaces, simplifying the overall network architecture.
2Ease of operation
If multiple subnets are supported within a single bridge domain, then management and scalability are improved, but packet forwarding accuracy may be compromised
Solution Approach 1:
The patent introduces attachment circuit (AC) information as an intermediary identifier that mediates between the single bridge domain and multiple subnets. The AC ID extended community carries VLAN identification information through the MPLS network, enabling PE devices to correctly identify which subnet a packet belongs to and forward it accurately, thus maintaining forwarding precision while using a unified bridge domain.
Solution Approach 2:
The invention changes the parameter representation by introducing AC ID as a new identifying parameter in the extended community attribute. This allows the system to distinguish between multiple subnets within a single bridge domain by encoding VLAN information in the AC ID field, enabling accurate packet routing based on this additional parameter without requiring separate bridge domains.
3Ease of manufacture
If conventional service interfaces are used, then implementation is straightforward, but support for multiple subnets within a single bridge domain is not available
Solution Approach 1:
The patent implements a dynamic bundle service interface that can adaptively handle multiple VLANs and subnets within a single bridge domain. The interface dynamically processes AC information from incoming packets, determines the appropriate subnet and VLAN, and forwards packets accordingly. This dynamic behavior provides multi-subnet support while maintaining a unified interface structure, offering both versatility and implementation feasibility.
Data Source
AI summary
Techniques for routing traffic across different virtual local area networks (VLANs) within a single bridge domain are described. One technique includes receiving at a first network device a packet from a second network device on a first interface of multiple interfaces within a bridge domain at the first network device. Attachment circuit information associated with the packet is determined. An information element that includes an indication of the attachment circuit information is generated. The information element is transmitted to the third network device.