VM Network Configuration via IP Mapper Rules
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Traditional disaster recovery for virtual machines (VMs) requires labor-intensive and error-prone manual configuration of TCP/IP settings for each VM, which is tedious and affects user experience and manageability.
Innovation Solution
Implementing IP mapping rules associated with virtual networks to dynamically derive new TCP/IP settings at a recovery site based on old settings, eliminating the need for per-VM configuration by using IP mapper objects that define transformations and predicates for network mappings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Manufacturing precision
If manual configuration of TCP/IP settings is performed for each VM, then network configuration accuracy is improved, but labor intensity and time consumption increase
Solution Approach 1:
The patent creates template configurations that can be copied and applied to multiple VMs. Instead of manually configuring each VM individually, administrators define a template once with the desired TCP/IP settings, and this template is then automatically applied to numerous VMs during disaster recovery, dramatically reducing time consumption while maintaining configuration accuracy through the template's predefined parameters.
Solution Approach 2:
The patent enables dynamic parameter changes by allowing administrators to modify TCP/IP configuration parameters (such as IP addresses, subnets, gateways) in a centralized template. When disaster recovery occurs, these parameters are automatically updated and applied across all affected VMs, eliminating the need for manual reconfiguration of each VM while ensuring consistent and accurate network settings throughout the recovery process.
2Manufacturing precision
If manual configuration of TCP/IP settings is performed for each VM, then configuration precision is improved, but complexity of operation increases
Solution Approach 1:
The patent implements a universal template mechanism that can serve multiple VMs across different disaster recovery scenarios. A single template configuration can be applied universally to numerous VMs, eliminating the need for administrators to perform repetitive manual configuration tasks for each individual VM. This universal approach maintains configuration precision through standardized templates while dramatically improving ease of operation through automated application.
Solution Approach 2:
The patent enables the system to perform self-service configuration by automatically applying template-based TCP/IP settings to VMs during disaster recovery. Instead of requiring manual intervention for each VM, the system autonomously retrieves the appropriate template, extracts the configuration parameters, and applies them to the recovered VMs, thereby reducing operational complexity while maintaining configuration accuracy.
3Adaptability or versatility
If individual VM configuration is performed, then adaptability to specific VM requirements is improved, but device complexity increases
Solution Approach 1:
The patent segments the configuration management into two distinct layers: template definitions and VM-specific applications. The template layer contains the adaptable configuration parameters that can be customized for different disaster recovery scenarios, while the application layer automatically applies these templates to individual VMs. This segmentation allows the system to maintain adaptability to specific VM requirements through template customization while reducing management complexity through automated template application across multiple VMs.
Data Source
AI summary
Techniques disclosed herein provide disaster recovery IP customization based on rules associated with virtual networks that virtual machines (VMs) are connected to. In one embodiment, the rules are applied to each recovered VM to dynamically derive new TCP/IP settings at a recovery site based on TCP/IP settings used at a protected site and the virtual networks that the VMs is connected to at the protected and recovery sites. In particular, the rules may be defined in IP mapper objects associated with mappings between protected site networks and recovery site networks. During disaster recovery, the protected-site-to-recovery-site network mapping for a vNIC of a recovered VM is determined and rules that are defined in the IP mapper object associated with such a network mapping are evaluated to generate new TCP/IP settings.