Browse Prior Art Database

OS/400 System Network Management Protocol Framework

IP.com Disclosure Number: IPCOM000118205D
Original Publication Date: 1996-Nov-01
Included in the Prior Art Database: 2005-Apr-01
Document File: 4 page(s) / 86K

Publishing Venue

IBM

Related People

Boden, EB: AUTHOR [+4]

Abstract

Disclosed is an invention which consists of a set of Application Programming Interfaces (APIs) for the Simple Network Management Protocol (SNMP). There are APIs for both the manager and agent portion of SNMP.

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

OS/400 System Network Management Protocol Framework

      Disclosed is an invention which consists of a set of
Application Programming Interfaces (APIs) for the Simple Network
Management Protocol (SNMP).  There are APIs for both the manager and
agent portion of SNMP.

      The manager APIs allow application programmers to develop SNMP
management applications.

      The agent APIs allow application programmers to develop SNMP
sub-agents which can surface management information to SNMP
management applications.

There are three manager APIs:
  1.  snmpGet
  2.  snmpGetnext
  3.  snmpSet

      These APIs correspond to the GET, GETNEXT and SET operations
described by SNMP.  That is, GET and GETNEXT are requests issued by a
management application to retrieve information from an SNMP agent,
and SET is a request that modifies information in an SNMP agent.

      These three APIs require parameters that include the SNMP
objects acted upon, the host machine in which these objects reside, a
time-out value should the remote host not respond, and a community
name and length which is required by SNMP for authentication
purposes.

      An application would call these APIs with the required
parameters, and within the API, the parameters are parsed and checked
for validity.  The appropriate SNMP protocol data unit is constructed
and sent via User Datagram Protocol (UDP) (a TCP/IP construct) to the
host machine denoted in the parameter list.

      The host machine then sends back the reply, which the API
decodes and parses, and returns to the application program along with
a code that signifies if everything went ok.

      There are 18 sub-agent APIs that implement the Distributed
Protocol Interface (DPI) which is described in RFC 1592.  They are:
   1.  connectSNMP
   2.  debugDPI
   3.  disconnectSNMP
   4.  DPI_PACKET_LEN
   5.  fDPIparse
   6.  fDPIset
   7.  mkDPIAreYouThere
   8.  mkDPIclose
   9.  mkDPIopen
  10.  mkDPIregister
  11.  mkDPIresponse
  12.  mkDPIset
  13.  mkDPItrap
  14.  mkDPIunregister
  15.  pDPIpacket
  16.  receiveDPIpacket
  17.  sendDPIpacket
  18.  waitDPIpacket

In general, DPI sub-agents go through a sequence of steps:
  o  Connect to the agent
  o  Register with the agent
  o ...