Browse Prior Art Database

Simple Network Management Protocol (SNMP) (RFC1098)

IP.com Disclosure Number: IPCOM000001907D
Original Publication Date: 1989-Apr-01
Included in the Prior Art Database: 2019-Feb-15
Document File: 34 page(s) / 38K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

J.D. Case: AUTHOR [+3]

Related Documents

10.17487/RFC1098: DOI

Abstract

This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or altered by logically remote users. In particular, together with its companion memos which describe the structure of management information along with the initial management information base, these documents provide a simple, workable architecture and system for managing TCP/IP-based internets and in particular the Internet.

This text was extracted from a PDF file.
This is the abbreviated version, containing approximately 7% of the total text.

Network Working Group J. Case Request for Comments: 1098 University of Tennessee at Knoxville Obsoletes: RFC 1067 M. Fedor NYSERNet, Inc. M. Schoffstall Rensselaer Polytechnic Institute C. Davin MIT Laboratory for Computer Science April 1989

A Simple Network Management Protocol (SNMP)

Table of Contents

1. Status of this Memo ................................... 2 2. Introduction .......................................... 2 3. The SNMP Architecture ................................. 4 3.1 Goals of the Architecture ............................ 4 3.2 Elements of the Architecture ......................... 4 3.2.1 Scope of Management Information .................... 5 3.2.2 Representation of Management Information ........... 5 3.2.3 Operations Supported on Management Information ..... 6 3.2.4 Form and Meaning of Protocol Exchanges ............. 7 3.2.5 Definition of Administrative Relationships ......... 7 3.2.6 Form and Meaning of References to Managed Objects .. 11 3.2.6.1 Resolution of Ambiguous MIB References ........... 11 3.2.6.2 Resolution of References across MIB Versions...... 11 3.2.6.3 Identification of Object Instances ............... 11 3.2.6.3.1 ifTable Object Type Names ...................... 12 3.2.6.3.2 atTable Object Type Names ...................... 12 3.2.6.3.3 ipAddrTable Object Type Names .................. 13 3.2.6.3.4 ipRoutingTable Object Type Names ............... 13 3.2.6.3.5 tcpConnTable Object Type Names ................. 13 3.2.6.3.6 egpNeighTable Object Type Names ................ 14 4. Protocol Specification ................................ 15 4.1 Elements of Procedure ................................ 16 4.1.1 Common Constructs .................................. 18 4.1.2 The GetRequest-PDU ................................. 19 4.1.3 The GetNextRequest-PDU ............................. 20 4.1.3.1 Example of Table Traversal ....................... 22 4.1.4 The GetResponse-PDU ................................ 23 4.1.5 The SetRequest-PDU ................................. 24 4.1.6 The Trap-PDU ....................................... 26 4.1.6.1 The coldStart Trap ............................... 27 4.1.6.2 The warmStart Trap ............................... 27 4.1.6.3 The linkDown Trap ................................ 27 4.1.6.4 The linkUp Trap .................................. 27

Case, Fedor, Schoffstall, & Davin [Page 1]

RFC 1098 SNMP April 1989

4.1.6.5 The authenticationFailure Trap ................... 27 4.1.6.6 The egpNeighborLoss Trap ......................... 27 4.1.6.7 The enterpriseSpecific Trap ...................... 28 5. Definitions ........................................... 29 6. Acknowledgements ...................................... 32 7. References ............................................ 33

1. Status of this Memo

This RFC is a re-release of RFC 1067, with a changed "Status of this Memo" section. This memo defines a simple protocol by which management information for a network element may be inspected or...

Processing...
Loading...