SD-WAN Sibling Session for IPv4 IPv6 Control Plane Scaling
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Existing SD-WAN management solutions require additional devices in each domain for control plane functions, leading to increased hardware and complexity, especially when dealing with mixed IPv4 and IPv6 environments, which poses configuration and security challenges, including route leakage issues.
Innovation Solution
The method involves establishing a sibling session between IPv4 and IPv6 connections at the control plane, using a network orchestrator to associate these connections as a single logical connection, preventing route leakage and allowing centralized management across different domains and geographical regions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If additional devices are deployed in each domain for control plane functions, then network control capability is improved, but device complexity and hardware requirements increase
Solution Approach 1:
The patent merges control plane functions across multiple domains by establishing sibling sessions that link connections from different domains (IPv4 and IPv6) to a centralized network orchestrator. This allows a single network controller to manage control plane functions for multiple domains without requiring separate devices in each domain, thereby reducing device complexity while maintaining network control capability.
Solution Approach 2:
The patent introduces a network orchestrator as an intermediary component that mediates between network controllers in different domains. The orchestrator receives control plane communications from multiple domains through sibling sessions and coordinates them centrally, enabling simplified device deployment while preserving comprehensive network control across all domains.
2Stability of the object's composition
If separate IPv4 and IPv6 connections are managed independently, then connection stability is improved, but route leakage and security risks increase
Solution Approach 1:
The patent merges the management of separate IPv4 and IPv6 connections by establishing sibling sessions that link both connection types to the same network orchestrator. This unified management approach maintains the stability of individual IPv4 and IPv6 connections while preventing route leakage through centralized control, as the orchestrator can coordinate routing information across both protocol families without exposing routes to unauthorized domains.
3Device complexity
If centralized control is implemented across different domains, then management complexity is reduced, but network coverage and adaptability requirements increase
Solution Approach 1:
The patent implements a universal network orchestrator that can handle multiple connection types (IPv4 and IPv6) and serve multiple domains through sibling sessions. This multi-functional approach reduces management complexity by providing centralized control while simultaneously increasing network coverage and adaptability, as the orchestrator can manage diverse network configurations across different geographical regions and protocol families through a single platform.
Data Source
AI summary
Disclosed are systems, apparatuses, methods, and computer-readable media for managing networks. According to at least one example, a method is provided for connecting to a network controller across different regions. The method includes identifying a first connection with a network orchestrator during establishment of a second connection with the network orchestrator from a network controller; establishing a sibling session that links the second connection and the first connection at a control plane; inserting a sibling data message that identifies the sibling session into control messages sent; receiving a message from the network orchestrator over the second connection, the message including an address of the network controller associated with the second connection; and transmitting the second address of the network controller over the first connection to the network orchestrator.