Managed Device Attribute Verification via SNMP MIB Queries

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network management systems face challenges in verifying the correctness of attribute information, such as community strings and passwords, stored on managed devices, which can lead to failed operations and communication issues due to incorrect or customized values.

Innovation Solution

A method and apparatus for verifying attribute information on managed devices by sending requests containing proposed values for SNMP MIB objects and receiving notification messages indicating matching correct values, allowing management stations to validate credentials and prompt patterns across multiple protocols using a single protocol.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If a management station stores attribute information for managed devices, then management operations can be performed, but the attribute information may become incorrect due to user changes, leading to operation failures

Engineering Contradiction:
Improvemanagement operation reliabilityVSAvoidattribute information accuracy
Core Design Contradiction:
ReliabilityVSLoss of information

Solution Approach 1:

The patent implements a feedback mechanism where the management station periodically verifies attribute information by attempting management operations (e.g., SNMP queries, telnet connections) and detects when attributes become incorrect. When failures occur, the system automatically updates the attribute information by establishing new sessions and re-obtaining correct values, creating a closed-loop feedback system that maintains information accuracy.

Inventive Principle:
Principle #23Feedback

Solution Approach 2:

The patent performs preliminary verification of attribute information before executing management operations. The management station checks whether stored attributes (such as community strings, passwords, prompt patterns) are still valid by attempting test connections or queries, and updates them proactively before they cause operation failures.

Inventive Principle:
Principle #10Preliminary action

2Measurement precision

If a management station uses telnet sessions to verify passwords, then password correctness can be confirmed, but customized prompt patterns may cause verification failures

Engineering Contradiction:
Improvepassword verification accuracyVSAvoidprompt pattern compatibility
Core Design Contradiction:
Measurement precisionVSAdaptability or versatility

Solution Approach 1:

The patent performs preliminary detection of prompt patterns by establishing test telnet sessions and capturing the actual prompt strings returned by the managed device. The management station stores these prompt patterns and uses them to correctly interpret subsequent telnet session outputs, allowing accurate password verification even when devices have customized prompts.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

The patent dynamically adjusts verification parameters based on the detected prompt patterns. Instead of using fixed prompt expectations, the system adapts its verification process to match the actual device-specific prompt formats, enabling compatibility with various device customizations while maintaining verification accuracy.

Inventive Principle:
Principle #35Parameter changes

3Measurement precision

If a management station attempts to verify read/write community strings by setting values, then correctness can be confirmed, but security concerns prevent users from allowing value changes

Engineering Contradiction:
Improvecommunity string verification accuracyVSAvoidsecurity risk
Core Design Contradiction:
Measurement precisionVSObject-affected harmful factors

Solution Approach 1:

The patent performs preliminary verification of read/write community strings by attempting read-only SNMP queries first. The management station tests whether the community string has correct read permissions by querying MIB objects, verifying correctness without executing any write operations that would pose security risks.

Inventive Principle:
Principle #10Preliminary action

Solution Approach 2:

Instead of verifying write permissions by attempting to set values (the conventional approach), the patent inverts the verification method by checking read permissions through get operations. This alternative verification approach confirms community string correctness without requiring write access, eliminating security concerns.

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

4Adaptability or versatility

If a management station maintains attribute information for multiple managed devices, then comprehensive management is enabled, but verification of all attributes becomes time-consuming

Engineering Contradiction:
Improvemulti-device management capabilityVSAvoidattribute verification time
Core Design Contradiction:
Adaptability or versatilityVSLoss of time

Solution Approach 1:

The patent segments the verification process by prioritizing critical attributes (such as authentication credentials and prompt patterns) over less critical ones. The management station performs verification in stages, first checking essential attributes that enable basic connectivity, then optionally verifying additional attributes, allowing selective verification that reduces time consumption while maintaining multi-device management capability.

Inventive Principle:
Principle #1Segmentation

Data Source

PatentUS7779420B1Verifying information stored on a managed network device
Publication Date: 2010.08.17 CISCO TECHNOLOGY INC
  • US7779420B1 patent drawing
  • US7779420B1 patent drawing
  • US7779420B1 patent drawing

AI summary

A method and mechanism for verifying information on a managed device is provided. A request is received at a managed device that contains one or more values that comprise proposals for a correct value of a managed object of the managed device. The managed object may be a SNMP MIB object. The managed object may store information for any attribute for the managed device. Next, a determination is made as to whether any of the one or more values in the request match the correct value of the managed object. Thereafter, a notification message is transmitted from the managed device to a management station that indicates whether any of the one or more values in the request match the correct value of the managed object. The notification message may identify which one of the one or more values in the request matches the correct value of the managed object.