L2 Mapping Conflict Resolution via Centralized Timestamping
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In virtualized computing environments, resolving Layer-2 (L2) mapping conflicts between hosts is challenging due to the impracticality of synchronizing clocks across thousands of distributed hosts, which is expensive and inefficient, especially when hosts experience networking issues or power outages, leading to stale mappings and conflicts.
Innovation Solution
A method where a network management server records L2 mappings in a database and generates timestamps, using either logical or physical timestamps, to resolve conflicts without requiring clock synchronization across all hosts, relying on connection statuses to determine the correctness of mappings.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Measurement precision
If clock synchronization is implemented across all hosts to resolve L2 mapping conflicts, then mapping conflict resolution accuracy is improved, but system cost and complexity increase significantly
Solution Approach 1:
A centralized controller is introduced as an intermediary to manage L2 mapping information and generate timestamps. Instead of requiring all hosts to synchronize their clocks, the controller acts as a single point of reference that receives mapping reports from hosts, maintains authoritative mapping records, and provides timestamp information for conflict resolution. This eliminates the need for complex distributed clock synchronization while maintaining accurate conflict resolution capability.
2Reliability
If clock synchronization hardware/software is deployed on thousands of hosts, then L2 mapping conflict resolution is improved, but deployment cost increases
Solution Approach 1:
The timestamp generation and mapping management functions are merged into a single centralized controller rather than being distributed across all hosts. This consolidation reduces the number of components from thousands of hosts to a single controller, dramatically reducing deployment cost while maintaining the reliability of L2 mapping conflict resolution through centralized authoritative management.
3Adaptability or versatility
If hosts independently generate and share timestamps for mapping conflicts, then conflict resolution capability is improved, but network synchronization requirements increase
Solution Approach 1:
The centralized controller serves as an intermediary that centralizes timestamp generation authority. Instead of each host independently generating timestamps (which would require network-wide synchronization), the controller generates and distributes timestamps to relevant hosts. This approach provides conflict resolution capability while eliminating the need for complex network synchronization infrastructure.
Data Source
AI summary
A method of recording layer-2 (L2) mappings created for workloads executing on a plurality of hosts in a first database managed by a network management server: upon receipt of a first mapping reported by a first host, determining that the first mapping is not recorded in the first database; and in response to the determining that the received first mapping is not recorded in the first database, generating a first timestamp and persisting a first record in the first database that includes the first mapping and the first timestamp.