Browse Prior Art Database

Simple Network Management Protocol (SNMP) (RFC1157)

IP.com Disclosure Number: IPCOM000001968D
Original Publication Date: 1990-May-01
Included in the Prior Art Database: 2000-Sep-12
Document File: 27 page(s) / 67K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J.D. Case: AUTHOR [+4]

Abstract

As reported in RFC 1052, IAB Recommendations for the Development of Internet Network Management Standards [1], a two-prong strategy for network management of TCP/IP-based internets was undertaken. In the short-term, the Simple Network Management Protocol (SNMP) was to be used to manage nodes in the Internet community. In the long-term, the use of the OSI network management framework was to be examined. Two documents were produced to define the management information: RFC 1065, which defined the Structure of Management Information (SMI) [2], and RFC 1066, which defined the Management Information Base (MIB) [3]. Both of these documents were designed so as to be

This text was extracted from a ASCII Text document.
This is the abbreviated version, containing approximately 4% of the total text.

Network Working Group J. Case

Request for Comments: 1157 SNMP Research

Obsoletes: RFC 1098 M. Fedor

Performance Systems International

M. Schoffstall

Performance Systems International

J. Davin

MIT Laboratory for Computer Science

May 1990

A Simple Network Management Protocol (SNMP)

Table of Contents

1. Status of this Memo ................................... 2

2. Introduction .......................................... 2

3. The SNMP Architecture ................................. 5

3.1 Goals of the Architecture ............................ 5

3.2 Elements of the Architecture ......................... 5

3.2.1 Scope of Management Information .................... 6

3.2.2 Representation of Management Information ........... 6

3.2.3 Operations Supported on Management Information ..... 7

3.2.4 Form and Meaning of Protocol Exchanges ............. 8

3.2.5 Definition of Administrative Relationships ......... 8

3.2.6 Form and Meaning of References to Managed Objects .. 12

3.2.6.1 Resolution of Ambiguous MIB References ........... 12

3.2.6.2 Resolution of References across MIB Versions...... 12

3.2.6.3 Identification of Object Instances ............... 12

3.2.6.3.1 ifTable Object Type Names ...................... 13

3.2.6.3.2 atTable Object Type Names ...................... 13

3.2.6.3.3 ipAddrTable Object Type Names .................. 14

3.2.6.3.4 ipRoutingTable Object Type Names ............... 14

3.2.6.3.5 tcpConnTable Object Type Names ................. 14

3.2.6.3.6 egpNeighTable Object Type Names ................ 15

4. Protocol Specification ................................ 16

4.1 Elements of Procedure ................................ 17

4.1.1 Common Constructs .................................. 19

4.1.2 The GetRequest-PDU ................................. 20

4.1.3 The GetNextRequest-PDU ............................. 21

4.1.3.1 Example of Table Traversal ....................... 23

4.1.4 The GetResponse-PDU ................................ 24

4.1.5 The SetRequest-PDU ................................. 25

4.1.6 The Trap-PDU ....................................... 27

4.1.6.1 The coldStart Trap ............................... 28

4.1.6.2 The warmStart Trap ............................... 28

4.1.6.3 The linkDown Trap ................................ 28

4.1.6.4 The linkUp Trap .................................. 28

4.1.6.5 The authenticationFailure Trap ................... 28

4.1....