Inter-Compatible Edge Forwarding Modes for Network Fabric Overlays
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing virtual network overlays face challenges in configuring edge nodes heterogeneously, leading to disrupted data plane traffic and limited utility due to the inability of mismatched edge nodes to establish tunnels, necessitating time-consuming reconfiguration to maintain traffic levels.
Innovation Solution
Implementing inter-compatible forwarding modes by configuring edge nodes to respond to address resolution requests by proxy, allowing TF-configured nodes to operate in EF-compatible modes, and enabling concurrent intra-subnet forwarding between mismatched and matched pairs, while maintaining heterogeneous configurations.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Adaptability or versatility
If edge nodes are configured with heterogeneous forwarding modes (TF and EF), then configurability and flexibility are improved, but data plane traffic is disrupted and tunnel establishment fails between mismatched nodes
Solution Approach 1:
The patent introduces a control plane as an intermediary that manages heterogeneous edge nodes. The control plane receives forwarding requests, determines the forwarding mode capabilities of edge nodes, and orchestrates tunnel establishment accordingly. This mediator enables mismatched TF and EF nodes to communicate by translating and coordinating their different forwarding behaviors, resolving the reliability issue while preserving configurability flexibility.
Solution Approach 2:
The system dynamically adapts tunnel establishment procedures based on the forwarding mode capabilities of edge nodes. When mismatched TF and EF nodes need to communicate, the system dynamically selects appropriate tunnel protocols and encapsulation methods. This dynamic behavior allows the network to maintain traffic continuity despite heterogeneous configurations, as the forwarding path is automatically adjusted to match the capabilities of participating nodes.
2Reliability
If edge nodes are reconfigured to homogeneous forwarding modes, then tunnel establishment and traffic flow are restored, but reconfiguration time and operational disruption increase
Solution Approach 1:
Instead of changing the fundamental forwarding mode parameter of edge nodes, the system changes operational parameters such as tunnel encapsulation type, protocol selection, and forwarding path parameters. This allows mismatched TF and EF nodes to communicate by adjusting these secondary parameters rather than reconfiguring the core forwarding mode, thereby maintaining reliability without incurring reconfiguration time penalties.
Solution Approach 2:
The control plane performs preliminary assessment of edge node capabilities before tunnel establishment. By pre-determining the forwarding mode configurations and selecting appropriate tunnel protocols in advance, the system avoids last-minute reconfiguration attempts. This preliminary action prevents operational disruption and eliminates reconfiguration time, as the correct forwarding parameters are established from the outset.
3Ease of operation
If traditional forwarding mode is used, then simplicity and ease of operation are maintained, but compatibility with enhanced forwarding mode nodes is lost
Solution Approach 1:
The control plane is designed with universal functionality to manage both TF and EF edge nodes through a unified interface. It automatically detects the capabilities of connected nodes and adapts its management procedures accordingly. This multi-functionality allows simple TF nodes to operate without complex configuration while still being compatible with more advanced EF nodes, as the control plane handles the complexity of interoperability transparently.
Solution Approach 2:
Instead of requiring TF nodes to be upgraded to EF mode to achieve compatibility, the system inverts the approach by enabling EF nodes to communicate with TF nodes through backward-compatible tunnel protocols. The control plane configures EF nodes to use simplified forwarding procedures when communicating with TF nodes, thereby maintaining the simplicity of TF operation while achieving compatibility with enhanced forwarding mode nodes.
Data Source
AI summary
Methods and devices configure edge nodes of a virtual network overlay to continuously forward data plane traffic flows between client devices of a common subnet over the course of at least some of the edge nodes being EF-configured. TF-configured edge nodes and EF-configured edge nodes both play roles in unilaterally inducing address discovery by sending to client devices address discovery responses that were not prompted by address discovery requests. TF-configured edge nodes then handle ensuing address discovery requests by proxy, and subsequently handle certain traffic flows according to an EF-compatible forwarding mode, while EF-configured edge nodes continue to forward traffic flows by IP routing normally. This averts throughput of data plane traffic over the network overlay being reduced as a side effect of the heterogeneously configured edge nodes, and averts the possibility of client devices broadcasting address discovery protocol requests as a result of remote client devices being unreachable.