SNMP Data Collection Channel Locking and Queuing
Find Innovative SolutionsGenerate Solutions
Solution Overview
Problem
The existing network management systems face inefficiencies and data loss due to duplicate SNMP data collection requests, which lead to increased latency and throttling in the network, as they often require additional data collection queries to calculate values from the collected data.
Innovation Solution
Implementing a data collection channel management system with a queue for duplicate requests, where channels already submitting requests are locked, and additional requests are queued until the initial request's value is returned, allowing the channel to be unlocked and the queued requests to receive the value, thereby eliminating duplicate queries.
Engineering Contradictions & Design Principles
Engineering Contradiction Analysis
1Reliability
If additional data collection queries are executed to calculate values from collected data, then data collection completeness is improved, but network latency increases and data loss occurs due to throttling
Solution Approach 1:
The patent performs preliminary data collection by executing SNMP queries to gather raw data from network devices before any calculations are performed. This preliminary action ensures that all necessary data is available in advance, eliminating the need for additional latency-causing queries during the calculation phase.
Solution Approach 2:
The patent introduces an intermediary processing layer that receives raw SNMP data, performs the necessary calculations to derive additional values, and then provides both the original and calculated data to the user. This intermediary prevents direct additional queries that would cause network throttling and latency.
2Productivity
If multiple duplicate data collection requests are processed simultaneously, then request fulfillment speed is improved, but network throughput decreases due to throttling and redundant queries
Solution Approach 1:
The patent merges multiple duplicate data collection requests into a single consolidated SNMP query. When multiple users or processes request the same data, the system combines these requests and executes one unified query to the network device, thereby maintaining request fulfillment while preserving network throughput.
Solution Approach 2:
The patent creates a universal data collection mechanism that serves multiple functions: it handles individual requests, consolidates duplicate requests, caches results for future use, and provides both raw and calculated data. This multi-functional approach improves productivity without proportionally increasing network load.
3Loss of substance
If data collection channels are locked to prevent duplicate requests, then redundant queries are eliminated, but request processing time increases due to queuing
Solution Approach 1:
The patent uses copying by implementing a cache that stores previously collected raw SNMP data. When a new request arrives, the system checks the cache first and provides a copy of the existing data if available, avoiding the need to re-execute queries entirely and thus eliminating redundant network traffic while maintaining fast response times.
Solution Approach 2:
The patent implements dynamic channel locking where the locked state is temporary and automatically released after data is collected and cached. This dynamic approach allows the system to prevent duplicates during active collection while quickly transitioning to a state where cached data can be rapidly served to subsequent requests, minimizing overall processing time.
Data Source
AI summary
Expressions to calculate values from data collection can often involve additional data collection queries causing duplicate requests for SNMP data collection. The duplicate requests can lead to increased latency or even data loss as SNMP data collection requests are throttled in a network. To eliminate duplicate requests, data collection channels for variable SNMP data collection can be managed with a queue for duplicate requests. Channels for which a data collection request has already been submitted can be locked while the request is pending. Additional requests for the locked channel are considered duplicate requests and are queued until a value is returned for the initial request. The returned value is then supplied to each of the queued requests, and the channel is unlocked.