Browse Prior Art Database

Service Interface that Supports Simple Network Management Protocol

IP.com Disclosure Number: IPCOM000109557D
Original Publication Date: 1992-Sep-01
Included in the Prior Art Database: 2005-Mar-24
Document File: 5 page(s) / 245K

Publishing Venue

IBM

Related People

Potok, RJ: AUTHOR

Abstract

Simple Network Management Protocol (SNMP) is a telecommunications protocol which is designed to minimize the number and complexity of management functions required by Manager-Station and Agents in a network. The protocol relies on a Management Information Base (MIB) that defines the Communications Network Management (CNM) Objects (e.g., the counters, thresholds, etc.) for each system in a network. Within a system, the MIB can be distributed across various protocol entities (e.g., Logical Link Control, Medium Access Control Sub-layer, etc.) depending on the protocol layers being managed. This article describes a service interface that enables an SNMP application entity to manage local MIB data in a manner that is consistent with the SNMP. See Fig. 1.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 43% of the total text.

Service Interface that Supports Simple Network Management Protocol

       Simple Network Management Protocol (SNMP) is a
telecommunications protocol which is designed to minimize the number
and complexity of management functions required by Manager-Station
and Agents in a network.  The protocol relies on a Management
Information Base (MIB) that defines the Communications Network
Management (CNM) Objects (e.g., the counters, thresholds, etc.) for
each system in a network.  Within a system, the MIB can be
distributed across various protocol entities (e.g., Logical Link
Control, Medium Access Control Sub-layer, etc.) depending on the
protocol layers being managed.  This article describes a service
interface that enables an SNMP application entity to manage local MIB
data in a manner that is consistent with the SNMP.  See Fig. 1.

      Management of one or more stations in a network may be
performed by a single central station using SNMP.  SNMP defines
protocol data units, which are exchanged between stations, that
identify functions related to management of CNM objects.  These
functions are GET, SET, GETNEXT, and TRAP.

      In order for a station to use SNMP it must contain an SNMP
Application which supports the elements of procedure for the SNMP
protocol, and also have the capability to perform SNMP management
functions on the MIBs within the station.

      The service interface between the SNMP application and the MIB
is defined in terms of primitives which are passed across the
interface.  These primitives which are passed across the service
interface between the SNMP application and the MIB which allow the
SNMP application to perform functions on information within the MIB
(e.g., Get, Set, Getnext) and allows the MIB to notify the
application if an unsolicited event occurs (e.g., similar to the Trap
function).

      The primitives defined in this invention are:
Primitive      Description
GET            This primitive instructs the MIB to retrieve the value
of an object.  This primitive has two forms:
                1. Request - Issued by the SNMP application to the
MIB.
                2. Confirm - Issued by the MIB to the SNMP
application (contains the completion status of the requested GET.)
SET            This primitive instructs the MIB to set the value of
an object. This primitive has two forms:
                1. Request - Issued by the SNMP application to the
MIB.
                2. Confirm - Issued by the MIB to the SNMP
application (contains the completion status of the requested SET.)
TRAP           This primitive is used by the MIB to indicate that an
unsolicited event occurred that required the notification of the SNMP
application.  This primitive has one form:
                1. Indication - Issued by the MIB to the SNMP
Application.
GETNEXT        This primitive instructs th...