Shared-IP NVD Routing for Seamless Host Network Failover
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In network virtualization environments, the failure of a Network Virtualization Device (NVD) can disrupt communication between compute instances, and quickly detecting and failing over to another NVD is challenging, leading to processing interruptions and resource access issues.
Innovation Solution
Implementing a shared IP address on loopback interfaces of multiple NVDs, prepopulating an ARP table linking the IP address to a compute instance, and advertising unique routes with route characterizers to enable active-active or active-backup traffic load-balancing, ensuring seamless failover.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Device complexity
If a single NVD is assigned to a compute instance, then the network architecture is simple, but the system reliability deteriorates when the NVD fails
Solution Approach 1:
The patent segments the network virtualization function by creating multiple NVDs (first NVD and second NVD) that can independently handle traffic for the same compute instance. This segmentation allows the system to distribute the single-point-failure risk across multiple devices, thereby improving reliability without significantly increasing architectural complexity.
Solution Approach 2:
The patent changes the routing parameter by advertising multiple unique routes (first unique route and second unique route) to the same compute instance via different NVDs. This parameter change enables traffic engineering and failover capabilities, allowing the system to switch between NVDs based on their operational status while maintaining communication availability.
2Reliability
If multiple NVDs are configured for a compute instance, then the system reliability improves, but the device complexity increases
Solution Approach 1:
The patent implements universality by configuring multiple NVDs to perform the same network virtualization functions for a single compute instance. Each NVD can independently advertise routes, handle ARP requests, and process traffic, making them interchangeable for failover purposes. This multi-functionality approach improves reliability while keeping the complexity manageable through standardized configurations.
Solution Approach 2:
The patent applies preliminary action by pre-configuring multiple NVDs with loopback interfaces and advertising unique routes before any failure occurs. The ARP table is prepopulated with the shared IP address mapping, and route characterizers are pre-established. This preliminary configuration ensures that failover can occur rapidly without requiring complex real-time decision-making or reconfiguration during failure events.
3Ease of manufacture
If traditional ARP resolution is used, then the implementation is simple, but the failover detection time increases
Solution Approach 1:
The patent applies preliminary action by prepopulating the ARP table with the shared IP address and its mapping to the compute instance before any failure occurs. This pre-population allows the system to immediately detect NVD failures by monitoring ARP table validity without requiring time-consuming ARP request-retry cycles, thus reducing failover detection time while maintaining implementation simplicity.
Solution Approach 2:
The patent implements feedback by continuously monitoring the validity of ARP table entries and route advertisements from multiple NVDs. When an NVD stops advertising its route or the ARP entry becomes invalid, the system receives feedback about the failure condition and can trigger failover. This feedback mechanism enables rapid failure detection while building upon the familiar ARP protocol foundation.
4Reliability
If rapid failover is implemented, then the communication availability improves, but the system complexity increases
Solution Approach 1:
The patent applies preliminary action by pre-configuring route characterizers and advertising unique routes with different preferences before failure occurs. The system pre-establishes the hierarchy and preferences for route selection, so that when failover is needed, the switching logic is already determined and can execute rapidly without complex real-time calculations or negotiations.
Solution Approach 2:
The patent implements dynamics by making the routing configuration adaptable and changeable based on NVD operational status. The route characterizers allow the system to dynamically adjust which NVD is active for a given compute instance based on real-time conditions. This dynamic capability enables rapid failover while keeping the underlying mechanism relatively simple through standardized routing protocol extensions.
Data Source
AI summary
Systems and methods for highly-available host networking with active-active or active-backup traffic load-balancing are disclosed herein. The method can include selecting a compute instance from an overlay network residing on a substrate network, identifying a plurality of Network Virtualization Devices (“NVD”) for association with the compute instance, creating a loopback interface on each of the NVDs, each of which loopback interfaces can include a shared IP address that can be in the substrate layer, prepopulating a table in each of the NVDs, the table linking the shared IP address to the compute instance, and each of the plurality of NVDs advertising a unique route to the compute instance via the shared IP address.