Simple Network Management Protocol
RFC 1067
Document | Type |
RFC - Unknown
(August 1988; No errata)
Obsoleted by RFC 1098
|
|
---|---|---|---|
Authors | |||
Last updated | 2013-03-02 | ||
Stream | Legacy | ||
Formats | plain text html pdf htmlized bibtex | ||
Stream | Legacy state | (None) | |
Consensus Boilerplate | Unknown | ||
RFC Editor Note | (None) | ||
IESG | IESG state | RFC 1067 (Unknown) | |
Telechat date | |||
Responsible AD | (None) | ||
Send notices to | (None) |
Network Working Group J. Case Request for Comments: 1067 University of Tennessee at Knoxville M. Fedor NYSERNet, Inc. M. Schoffstall Rensselaer Polytechnic Institute J. Davin Proteon, Inc. August 1988 A Simple Network Management Protocol 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 1067 SNMP August 1988 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 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 memo specifies a draft standard for the Internet community. TCP/IP implementations in the Internet which are network manageable are expected to adopt and implement this specification. Distribution of this memo is unlimited. 2. Introduction As reported in RFC 1052, IAB Recommendations for the Development of Internet Network Management Standards [1], the Internet Activities Board has directed the Internet Engineering Task Force (IETF) to create two new working groups in the area of network management. One group is charged with the further specification and definition of elements to be included in the Management Information Base (MIB). The other is charged with defining the modifications to the Simple Network Management Protocol (SNMP) to accommodate the short-term needs of the network vendor and operations communities, and to align with the output of the MIB working group. The MIB working group has produced two memos, one which defines aShow full document text