Elastic IP Address for Hypervisor Virtual Router Management
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Conventional branch deployment infrastructure for virtual networks requires two public IP addresses, one for the hypervisor and one for the virtual router, leading to unreachability and unrecoverability when the virtual router fails, as management traffic cannot pass through the virtual router effectively.
Innovation Solution
Implementing a method where one public IP address is shared seamlessly between the hypervisor and the virtual router, allowing the hypervisor to monitor the virtual router's health and reassign the IP address upon failure, ensuring continuous management and recovery of the virtual branch site.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If two public IP addresses are assigned (one for hypervisor, one for virtual router), then the virtual router can handle traffic routing, but the system becomes unreachable and unrecoverable when the virtual router fails
Solution Approach 1:
The patent implements dynamic IP address assignment where the public IP address is not statically bound to either the hypervisor or virtual router, but is instead dynamically assigned based on operational state. The IP address moves between components depending on which is currently operational and able to handle management traffic, making the system resilient to virtual router failures while maintaining simple IP management.
Solution Approach 2:
The patent introduces an intermediary mechanism (the elastic IP address assignment system) that mediates between the hypervisor and virtual router. This intermediary layer allows management traffic to reach the operational component regardless of which component currently holds the IP address, resolving the reachability issue without requiring complex dual-IP configurations.
2Reliability
If one public IP address is shared between hypervisor and virtual router, then the system remains reachable during virtual router failure, but the IP address assignment becomes complex
Solution Approach 1:
The public IP address is designed to be universal and multi-functional, serving both the hypervisor and virtual router as needed. Rather than being dedicated to a single component, the IP address can be assigned to either component depending on operational requirements, providing management reachability through both components while maintaining a single IP address configuration.
Solution Approach 2:
The patent changes the parameter of IP address assignment from static to dynamic. The IP address assignment state changes based on operational conditions, allowing the system to adapt to failures and maintain reachability. This parameter change simplifies the overall configuration while enabling complex failover behavior.
3Productivity
If the virtual router is configured to take the public IP address for traffic handling, then routing works effectively, but management traffic cannot pass through the virtual router when it is in error state
Solution Approach 1:
The patent makes the IP address assignment dynamic rather than static. The virtual router can hold the IP address for efficient traffic routing when operational, but the IP address can be reassigned to the hypervisor when the virtual router fails, allowing management access. This dynamic behavior resolves the contradiction between routing efficiency and management accessibility.
Solution Approach 2:
The system performs preliminary actions by pre-configuring the hypervisor as a backup management access point. Before failure occurs, the hypervisor is prepared to take over the IP address and handle management traffic, ensuring that management accessibility is maintained without interrupting normal routing operations through the virtual router.
Data Source
AI summary
An elastic Internet Protocol (IP) address for hypervisor and virtual router management in a branch environment may be provided. First, an IP address may be assigned to a hypervisor associated with a virtual branch. Next, it may be determined that a virtual machine (VM) has been instantiated at the virtual branch. In response to determining that the VM has been instantiated at the virtual branch, the IP address may then be released. It may next be determined that the VM is in a failed state and then, in response to determining that the VM is in the failed state, the IP address may be reassigned to the hypervisor.