Global Realization Number for Logical Network Status
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
In distributed virtual networks, it is difficult to determine whether logical entities have been realized in the network infrastructure at a particular point in time, and there is no method to identify the source of issues when a logical entity is not properly realized.
Innovation Solution
A method and tool that query the control plane to determine the realization status of logical entities, using a global realization number (GRN) to track the realization of desired states and identify physical nodes where logical entities are not realized, allowing users to query the realization status of multiple entities at different times.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the control plane processes and pushes configuration data to multiple managed forwarding elements, then the logical entities are realized across the network infrastructure, but it becomes difficult to determine whether all logical entities have been properly realized at a particular point in time
Solution Approach 1:
The patent implements a feedback mechanism where the control plane receives runtime data from managed forwarding elements and compares it against desired state data to determine realization status. The system continuously monitors whether logical entities have been properly configured on MFEs by receiving runtime configuration data and comparing it with the desired state, providing feedback about the realization status of logical entities across the distributed network infrastructure.
Solution Approach 2:
The patent introduces an intermediary mechanism in the form of a realization determination tool that acts as a mediator between the control plane and the management plane. This tool receives queries about logical entity realization status, coordinates with the control plane to obtain runtime data, and returns determination results. The intermediary simplifies the complexity by providing a centralized interface for tracking realization status across multiple distributed MFEs without requiring each component to independently track all entities.
2Adaptability or versatility
If the system distributes logical entities across multiple physical nodes, then the network infrastructure can implement complex logical networks, but it becomes impossible to identify the source of problems when a logical entity is not properly realized
Solution Approach 1:
The patent applies segmentation by dividing the realization determination process into distinct components: desired state data stored in the control plane, runtime data collected from individual managed forwarding elements, and a realization determination tool that processes this segmented information. Each MFE reports its own runtime configuration data separately, allowing the system to identify which specific physical node or MFE fails to properly realize a logical entity by comparing segmented runtime data against the desired state.
Solution Approach 2:
The system uses feedback from each managed forwarding element's runtime data to identify problem sources. When a logical entity is not properly realized, the feedback mechanism allows the control plane to determine which specific MFE or physical node is responsible by comparing the desired state data with the actual runtime data reported from each node, thereby identifying the source of the realization failure.
3Reliability
If the control plane continuously monitors the realization status of logical entities, then the system can ensure proper configuration, but the complexity of tracking and verifying each entity increases
Solution Approach 1:
The patent implements self-service by having each managed forwarding element autonomously report its own runtime configuration data to the control plane. Each MFE independently monitors its own configuration state and provides this information when queried, eliminating the need for a complex centralized monitoring system that would actively probe each node. The MFEs serve themselves by maintaining and reporting their own state information.
Solution Approach 2:
The system uses copying by creating a runtime copy of the configuration data at each managed forwarding element and another copy at the control plane. The realization determination tool compares these copies to verify realization status. Instead of continuously monitoring through complex active probing, the system relies on comparing configuration data copies that already exist at different locations in the distributed system.
Data Source
AI summary
Some embodiments provide a method for determining a realization status of one or more logical entities of a logical network. The method, each time a particular event occurs, increments the value of a realization number and publishes the incremented value to a set of controllers of the logical network. Upon receiving data that specifies the state of a logical entity of the logical network, the method publishes the logical entity state's data to the set of controllers. In some embodiments, the method queries the set of controllers for a realization status of the state data for a set of logical entities that is published to the set of controllers up to a particular point of time. The submitted query, in some embodiments, includes a particular value of the realization number associated with the particular point of time.