ToR Switch Provisioning via Packet Mobility Domain Identifiers
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current network orchestration techniques face challenges in efficiently provisioning top-of-rack (ToR) switches for tenant networks, especially when virtual machines migrate across different VLANs and mobility domains, as they require specialized control protocols like VDP, which may not be compatible with all virtual switches and hypervisors, leading to inefficiencies and limitations in resource allocation.
Innovation Solution
The proposed solution involves using data packet identifiers and mobility domain identifiers to form a unique identifier, allowing the ToR switch to obtain provisioning information from a network database without relying on VDP, enabling automated resource provisioning based on standard network traffic and being agnostic to hypervisors and orchestrator solutions.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If specialized control protocols like VDP are used for network orchestration, then provisioning accuracy for tenant networks is improved, but device complexity and compatibility requirements increase
Solution Approach 1:
The patent introduces a database as an intermediary layer between the control plane and data plane. The database stores provisioning information that translates complex protocol requirements into simple database lookups based on mobility domain identifiers. This intermediary eliminates the need for specialized control protocols like VDP while maintaining provisioning accuracy, as the ToR switch only needs to perform database queries using identifiers extracted from standard network packets.
Solution Approach 2:
The patent replaces the mechanical control protocol exchange (VDP) with a data-driven approach using standard network traffic. Instead of requiring specialized control plane communications, the system uses data packet identifiers and mobility domain identifiers to trigger automated provisioning through database lookups. This substitution eliminates protocol complexity while maintaining provisioning functionality.
2Reliability
If specialized control protocols are required for VM migration, then network provisioning reliability is improved, but adaptability to different hypervisors and orchestrators decreases
Solution Approach 1:
The patent creates a universal provisioning mechanism that works across different hypervisors and orchestrator solutions. By using mobility domain identifiers that can be extracted from standard network packets regardless of the underlying virtualization platform, the system achieves both reliability and universality. The database-stored provisioning information serves as a common interface that abstracts away hypervisor-specific details.
Solution Approach 2:
The patent changes the parameter used for provisioning from protocol-specific control messages to standard network packet identifiers. By using mobility domain identifiers that are independent of hypervisor implementation details, the system maintains provisioning reliability while achieving broad adaptability across different virtualization platforms and orchestrator solutions.
3Ease of operation
If automated provisioning is implemented without specialized protocols, then ease of operation is improved, but measurement precision of network state decreases
Solution Approach 1:
The patent implements feedback through the use of mobility domain identifiers extracted from actual network traffic. The system continuously monitors standard network packets, extracts identifiers, and uses them to trigger appropriate provisioning actions from the database. This feedback mechanism ensures precise network state detection while maintaining ease of operation through automated database-driven provisioning.
Data Source
AI summary
Presented herein are techniques to handle data packets received at a top-of-rack (ToR) switch in an underlay network hosting one or more tenant networks. The underlay network may comprise a plurality of ToR switches each connected to each of a plurality of spine switches. The data packet may be received from a virtual machine in a tenant network, and have a header with a data packet identifier. A mobility domain identifier may be determined that corresponds to the network portion within which the virtual machine can be migrated. The mobility domain may be configured on the ToR switch on a per-port basis based on the virtual machine connected to the ToR switch port. A unique identifier may be formed based on the data packet identifier and mobility domain identifier. Using this unique identifier, provisioning information may be obtained for the tenant network on the ToR switch.