Destination MAC Aging in Asymmetric Routing Switches
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In asymmetric routing scenarios, the lack of destination MAC address entries on non-ingress linecards leads to flooding issues when return traffic is not synchronized, causing network problems such as bandwidth oversubscription and broken secure connections.
Innovation Solution
Implementing a destination MAC aging protocol on linecards, where the time value of destination MAC address entries is updated and the DMA bit is set, ensuring that these entries are not prematurely dropped from the address table, thereby preventing flooding.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Quantity of substance
If destination MAC address entries are not maintained on non-ingress linecards in asymmetric routing scenarios, then the address table size is reduced and memory resources are conserved, but flooding occurs when return traffic arrives causing network congestion and broken secure connections
Solution Approach 1:
The patent applies preliminary action by pre-populating destination MAC address entries on non-ingress linecards before return traffic arrives. When forward traffic is received, the system proactively creates destination MAC entries for return traffic on the ingress linecard and synchronizes them to non-ingress linecards ahead of time, preventing flooding when the return traffic arrives later.
2Reliability
If destination MAC address entries are maintained on all linecards to prevent flooding, then network reliability is improved, but the address table size increases and memory resources are consumed
Solution Approach 1:
The patent applies local quality by making destination MAC address table maintenance selective rather than universal. Only non-ingress linecards that are part of asymmetric routing paths maintain destination MAC entries, while other linecards use traditional source MAC address learning. This localized approach prevents flooding only where needed without unnecessarily increasing address table size system-wide.
3Reliability
If destination MAC address entries are synchronized across all linecards, then flooding is prevented in asymmetric routing scenarios, but the system complexity and synchronization overhead increase
Solution Approach 1:
The patent applies segmentation by dividing the address table synchronization process into separate mechanisms: source MAC address learning continues to operate independently on each linecard, while destination MAC address synchronization is implemented as a separate, targeted process that only affects non-ingress linecards in asymmetric routing scenarios. This segmentation isolates the complexity to specific components rather than requiring system-wide changes.
4Reliability
If destination MAC address entries are updated frequently to maintain accuracy, then flooding is prevented, but the processing overhead and CPU utilization increase
Solution Approach 1:
The patent applies periodic action by implementing aging mechanisms and scheduled synchronization intervals for destination MAC address entries. Instead of continuous updates, the system periodically refreshes destination MAC entries on non-ingress linecards at defined intervals, balancing table accuracy with reduced processing overhead compared to real-time continuous updates.
Data Source
AI summary
In one embodiment, entries in an address table of the forwarding engine in a linecard or supervisor are updated to a current time value when the MAC address in the entry matches the destination MAC address of a received packet to prevent flooding if the linecard or supervisor is a non-ingress linecard or supervisor of an asymmetrically routed flow.