SNMP Variable Persistence Mechanism for Network Element Reloads

Resolve Bottlenecks,
Find Innovative Solutions
Generate Solutions

Solution Overview

Problem

Current network management systems require extra coding and complexity to persist SNMP MIB variable values across network element reloads, particularly due to the need to re-initialize values like ifIndex, which is inefficient and specific to individual features.

Innovation Solution

Implementing a generic persist operation at the network element that allows specification of SNMP object IDs for persistence, with values stored in non-volatile memory, enabling persistence across reloads for any SNMP object or group of objects using wildcarding, thereby simplifying the process and reducing complexity.

Engineering Contradictions & Design Principles

VSEngineering Contradiction Analysis

1Reliability

If individual persistence commands are implemented for specific features, then persistence of specific SNMP variables is achieved, but device complexity and coding requirements increase

Engineering Contradiction:
Improvepersistence of SNMP variablesVSAvoidcoding complexity
Core Design Contradiction:
ReliabilityVSDevice complexity

Solution Approach 1:

The patent implements a universal persistence mechanism that can handle any SNMP variable or group of variables through a single generic command structure. Instead of creating separate persistence commands for each feature (ifIndex, interface names, routing tables, etc.), the system provides a single `snmp-server persistence` command that works with wildcards to persist any desired SNMP objects, thereby reducing coding complexity while maintaining reliability

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

Solution Approach 2:

The patent segments the persistence functionality into configurable components where users can specify individual SNMP variables, groups of variables, or use wildcards to persist entire MIB branches. This segmentation allows the system to handle specific persistence needs without requiring separate commands for each variable, reducing overall device complexity

Inventive Principle:
Principle #1Segmentation

2Reliability

If individual persistence commands are implemented for specific features, then persistence of specific SNMP variables is achieved, but ease of operation decreases

Engineering Contradiction:
Improvepersistence of SNMP variablesVSAvoidconfiguration simplicity
Core Design Contradiction:
ReliabilityVSEase of operation

Solution Approach 1:

The universal persistence command with wildcard support allows network administrators to persist individual variables, groups of variables, or entire MIB branches using a single command syntax. This eliminates the need to learn and configure multiple different commands for different features, significantly improving ease of operation while ensuring reliable persistence

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

Solution Approach 2:

The wildcard mechanism in the persistence command allows users to copy the persistence behavior across multiple SNMP variables and groups by specifying pattern matches (e.g., persisting all interface-related variables with a single wildcard pattern), thereby simplifying configuration operations

Inventive Principle:
Principle #26Copying

Data Source

PatentUS8051155B2Method and apparatus for persisting SNMP variable values
Publication Date: 2011.11.01 CISCO TECHNOLOGY INC
  • US8051155B2 patent drawing
  • US8051155B2 patent drawing
  • US8051155B2 patent drawing

AI summary

A method of persisting SNMP (Simple Network Management Protocol) variable values associated with SNMP object IDs for an SNMP managed network element across network element reloads comprises implementing a generic persist operation at the network element; and defining, in conjunction with the generic persist operation, at least one object ID for which a value is to be persisted.