SNMP Agent Cluster Entity Awareness via Lexicographic Selection
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
Scalable networking systems face performance degradation when managing large numbers of tabular data and entities, particularly in clustered environments, due to the need to maintain awareness of all entities across the cluster, leading to increased maintainability costs and scalability issues.
Innovation Solution
A distributed system that generates an on-the-fly partial view of the cluster configuration relevant to current requests, using a configuration coordinator SNMP daemon to request and aggregate statistical or configuration information from nodes, selecting the lexicographically minimum entity to respond to SNMP GETNEXT requests, thereby reducing the impact of cluster state changes and maintaining entity awareness without explicit information storage.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If the configuration coordinator SNMP daemon maintains awareness of all entities across the cluster, then it can provide aggregated view and support SNMP operations, but the system performance significantly decreases when scaling to large number of managed objects
Solution Approach 1:
The patent segments the cluster entities into different partitions or groups, allowing the SNMP daemon to handle requests for specific partitions rather than maintaining awareness of all entities. This segmentation reduces the memory and processing requirements while maintaining the ability to provide aggregated views through coordinated access to partition-specific data.
Solution Approach 2:
The patent introduces partition-specific SNMP daemons or intermediary components that manage entity information for specific partitions. The configuration coordinator daemon acts as a mediator that coordinates between these partition-specific daemons and external SNMP managers, reducing the load on any single component while maintaining comprehensive entity awareness across the cluster.
2Stability of the object's composition
If all nodes in the cluster are informed when a new entity is added or removed, then the aggregated view remains consistent, but the maintainability cost and complexity increases
Solution Approach 1:
The patent segments the cluster into partitions with partition-specific SNMP daemons that independently track entities within their partitions. This segmentation reduces the complexity of maintaining configuration consistency, as changes only need to be communicated to relevant partition daemons rather than all nodes, while still maintaining overall cluster-wide consistency through coordinated management.
3Measurement precision
If the configuration coordinator maintains explicit information about all entities, then it can respond to SNMP requests accurately, but the scalability is limited due to increased memory and processing requirements
Solution Approach 1:
The patent extracts entity information management from the configuration coordinator daemon and distributes it to partition-specific daemons or local node components. The coordinator only maintains metadata or routing information about partitions, while detailed entity information is stored and managed locally. This extraction enables the system to scale to large numbers of managed objects without overwhelming the coordinator's memory and processing resources.
Solution Approach 2:
The patent introduces partition-specific SNMP daemons as intermediaries between the configuration coordinator and the actual entity data. These intermediaries handle the detailed entity information locally, allowing the coordinator to maintain accurate entity information for its partition while delegating broader cluster-wide entity management to other intermediaries, thereby enabling scalability.
Data Source
AI summary
The present disclosure is directed towards systems and methods for supporting Simple Network Management Protocol (SNMP) request operations over clustered networking devices. The system includes a cluster that includes a plurality of intermediary devices and an SNMP agent executing on a first intermediary device of the plurality of intermediary devices. The SNMP agent receives an SNMP GETNEXT request for an entity. Responsive to receipt of the SNMP GETNEXT request, the SNMP agent requests a next entity from each intermediary device of the plurality of intermediary devices of the cluster. To respond to the SNMP request, the SNMP agent selects a lexicographically minimum entity. The SNMP agent may select the lexicographically minimum entity from a plurality of next entities received via responses from each intermediary device of the plurality of intermediary devices.