EVPN Provider Edge Loop Prevention Through Source Address Matching
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In Ethernet virtual private networks (EVPN), traffic loops can form, leading to waste of network resources and performance degradation in provider edge (PE) devices due to the lack of proper address matching and interface fault detection in dual-active scenarios.
Innovation Solution
The solution involves PE devices storing entries with peer addresses and using source address matching to prevent loops, ensuring data packets are not sent back to the same PE device, and implementing fast reroute paths through local and non-local interfaces based on pre-configured segment identifiers (SID) and Ethernet segment identifiers (ESI).
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Productivity
If PE devices forward data packets without source address matching in dual-active scenarios, then traffic forwarding efficiency is improved, but traffic loops are formed causing network resource waste
Solution Approach 1:
The patent applies preliminary action by pre-configuring peer PE device addresses and establishing forwarding entries before traffic loops can occur. When a PE device receives a data packet, it checks the source address against the pre-stored peer address in the forwarding entry. This pre-established mechanism enables immediate loop detection without affecting normal forwarding efficiency, resolving the contradiction between forwarding speed and loop prevention.
2Reliability
If PE devices implement source address matching to prevent loops, then traffic loop prevention is improved, but device complexity increases
Solution Approach 1:
The patent uses copying by creating simplified forwarding entries that contain only the essential peer PE device address information needed for loop detection. Instead of implementing complex routing protocols or maintaining full routing tables, each PE device stores a compact copy of the peer's address in its forwarding entry. This copied information enables reliable loop prevention through simple source address matching while keeping the device complexity low.
3Measurement precision
If PE devices check source addresses for every incoming packet, then loop detection accuracy is improved, but processing time increases
Solution Approach 1:
The patent extracts only the critical source address field from incoming data packets for comparison with the pre-stored peer address in the forwarding entry. Instead of performing comprehensive routing lookups or complex path analysis for every packet, the system extracts and compares just the source address against the essential peer identifier. This extraction approach maintains high loop detection accuracy while minimizing packet processing time.
Data Source
Figure 1
Figure 2
Figure 3~4
AI summary
This application provides a communication method and a provider edge PE device, to prevent a loop from being formed when traffic is forwarded, and avoid waste of network resources. The method includes: receiving, by a first PE device, a message sent by a second PE device, where the message includes a first ESI and an address of the second PE device, and the first ESI is used to identify an Ethernet segment to which a connection between the second PE device and a CE device belongs; determining, by the first PE device, that the first ESI is the same as a second ESI stored in the first PE device, where the second ESI is used to identify an Ethernet segment to which a connection between the first PE device and the CE device belongs; generating, by the first PE device, an entry when determining that the first ESI is the same as the second ESI, where the entry includes the address of the second PE device; receiving, by the first PE device, a data packet; and avoiding, by the first PE device, sending the data packet to the second PE device when the first PE device determines that a source address of the data packet is the same as the address of the second PE device in the entry.