Network Management System State Tracking via Event-Driven Streaming

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Traditional datacenter networks face challenges such as software crashes, unplanned outages, lengthy feature deployment processes, and configuration errors due to manual configuration and lack of comprehensive state information, making debugging and analysis difficult, and existing polling mechanisms are inefficient and prone to deadlocks.

Innovation Solution

A distributed network management system that continuously streams configuration state and operational status changes from network elements to a collector node, storing data in a distributed database for real-time analysis and prediction of network failures, allowing for proactive remediation and historical state reconstruction.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If synchronous or asynchronous polling is used to query software state, then the internal state of network elements can be retrieved, but wasted cycles and possible deadlocks and race conditions occur during concurrent events

Engineering Contradiction:
Improvestate retrieval reliabilityVSAvoidpolling efficiency
Core Design Contradiction:
ReliabilityVSProductivity

Solution Approach 1:

Instead of the network element responding to polling requests (traditional approach), the invention inverts the approach by having the network element proactively push state change notifications to the management system. This is implemented through an event-driven architecture where state changes trigger asynchronous notifications, eliminating the need for continuous polling and its associated waste of cycles and potential deadlocks.

Inventive Principle:
Principle #13The other way round (Inversion)

2Adaptability or versatility

If manual configuration is used within datacenter networks, then flexibility in network setup is achieved, but configuration errors occur which compromise network uptime or availability

Engineering Contradiction:
Improveconfiguration flexibilityVSAvoidnetwork availability
Core Design Contradiction:
Adaptability or versatilityVSReliability

Solution Approach 1:

The invention implements comprehensive state monitoring and tracking of network element configurations. By continuously capturing and storing configuration state and operational status data, the system provides feedback mechanisms that can detect configuration errors early. This enables validation of manual configurations against desired states and allows for automated remediation or alerting, thus maintaining network availability while preserving configuration flexibility.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The system captures and stores configuration state data before failures occur, creating a historical record of the network state. This preliminary action enables post-failure analysis and debugging by preserving the state information that existed prior to the error, allowing operators to understand what configuration led to the failure and to restore the network to a known good state.

Inventive Principle:
Principle #10Preliminary action

3Device complexity

If comprehensive state information is not tracked, then system complexity is reduced, but debugging and analysis of failures become more difficult

Engineering Contradiction:
Improvestate tracking complexityVSAvoidfailure analysis difficulty
Core Design Contradiction:
Device complexityVSDifficulty of detecting and measuring

Solution Approach 1:

The invention creates copies of the network element's internal state by capturing and storing configuration state and operational status data in an external management system. This copying approach allows comprehensive state information to be maintained without adding complexity to the network elements themselves, as the state tracking functionality is implemented in the management plane rather than the data plane.

Inventive Principle:
Principle #26Copying

Solution Approach 2:

The invention introduces an intermediary management system that sits between the network elements and the operators. This intermediary captures, stores, and manages comprehensive state information from multiple network elements, providing a centralized view that simplifies debugging and analysis. The intermediary handles the complexity of state tracking, shielding operators from the underlying complexity while providing easy access to failure analysis capabilities.

Inventive Principle:
Principle #24Intermediary (Mediator)

4Adaptability or versatility

If multiple different software releases are deployed across switch platforms, then feature variety is increased, but deploying new features and services becomes lengthy and time-consuming

Engineering Contradiction:
Improvefeature varietyVSAvoiddeployment time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The invention implements a universal state management architecture that can handle multiple software releases and platform types through a common interface. By standardizing how state information is captured, stored, and accessed across different network elements regardless of their specific software version or platform, the system enables efficient deployment of new features and services. The universal approach allows operators to manage diverse infrastructure through consistent procedures, reducing deployment time while maintaining feature variety.

Inventive Principle:
Principle #6Universality (Multi-functionality)

Data Source

PatentUS11729056B2Data analytics on internal state
Publication Date: 2023.08.15 ARISTA NETWORKS INC
  • US11729056B2 patent drawing
  • US11729056B2 patent drawing
  • US11729056B2 patent drawing

AI summary

Various embodiments are described herein to track and/or update the state of components within a network element. One embodiment provides for a network management system comprising a collector node including an ingest gateway to receive configuration and status data of a set of network elements coupled to the collector node via the network, the collector node further to store the configuration and status data from the set of network elements in a distributed database; a search engine to locate and retrieve the configuration and status data of a specified subset of the network elements at a specified time period; and an interface server to receive a request for the configuration and status data from an external requester, the interface server to facilitate provision of the configuration and status data in response to the request.