Switch Failover Using VMAC Address Group Port Reassignment
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Current failover mechanisms in computing and communication networks are complex and costly to deploy, often requiring dedicated wires and multiple protocols, which can lead to single points of failure and security vulnerabilities, especially when devices with identical VMAC addresses need to be configured as masters and slaves.
Innovation Solution
A method that assigns devices with identical VMAC addresses to specific VLANs, allowing a switch to automatically reassign ports and roles between master and slave devices based on received messages, eliminating the need for dedicated wires and reducing configuration complexity by using existing network infrastructure.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If dedicated wires are used to connect master and slave devices, then failover reliability is improved, but device complexity and deployment cost increase
Solution Approach 1:
The patent merges the master-slave communication into the existing network infrastructure by using virtual network interfaces and VLANs. Instead of dedicated physical wires, the system uses virtual network connections through a shared network switch, combining multiple communication functions (data traffic, failover signaling, heartbeats) into existing network pathways.
Solution Approach 2:
The network switch acts as an intermediary device that facilitates communication between master and slave devices. The switch receives messages from devices with identical VMAC addresses and automatically routes them to the appropriate device, eliminating the need for direct dedicated wire connections between master and slave.
2Reliability
If failover packages and protocols are installed on each device, then failover functionality is achieved, but deployment cost and configuration complexity increase
Solution Approach 1:
The system implements self-service failover by automatically detecting device status and performing role transitions without administrator intervention. The network switch monitors messages from devices with identical VMAC addresses and automatically reassigns virtual network interfaces when failover is needed, eliminating the need for manual configuration and reducing deployment complexity.
Solution Approach 2:
The invention makes the network switch universal by giving it multiple functions: it acts as a regular network switch for data traffic, a failover controller for monitoring device status, and an automatic role assignment system. This consolidates failover management functionality into the existing network infrastructure rather than requiring separate dedicated systems.
3Reliability
If devices are configured to support failover packages, then failover capability is provided, but security is negatively affected
Solution Approach 1:
The patent uses VLAN segmentation to isolate failover control traffic from regular data traffic. By placing master and slave devices in a dedicated virtual network, the system creates a secure boundary that limits exposure to potential security threats while maintaining failover functionality. The virtual network interface acts as a segmented communication channel.
4Reliability
If ARP caches are stored by master and slave devices, then failover protocol functionality is achieved, but failover speed is reduced
Solution Approach 1:
The system performs preliminary actions by pre-configuring virtual network interfaces and maintaining readiness states for both master and slave devices. The network switch is pre-programmed with the VMAC address mappings and can immediately reassign virtual interfaces when failover is triggered, eliminating the need for time-consuming ARP cache updates during the failover process.
Data Source
AI summary
A system is configured to: transmit requests to a first device and a second device; receive a first reply from the first device in response to one of the requests; determine an address of the first device based on the first reply; assign a first port to a first network when the first device is a first one of one or more devices that replied to the requests and have a same address as the first device; receive a second reply from the second device in response to another one of the requests; assign a second port to a second network when the address of the second device is the same as the address of the first device; and reassign the second port, from the second network, to the first network when a failure of the first device occurs.