Internet Draft Remote Network Monitoring Traps August 21, 1991 SNMP Trap Definitions For Remote Network Monitoring August 21, 1991 Steven Waldbusser Carnegie Mellon University 4910 Forbes Ave. Pittsburgh, PA 15213 waldbusser@andrew.cmu.edu 1. Status of this Memo This draft document will be submitted to the RFC editor as an experimental extension to the SNMP MIB. Distribution of this memo is unlimited. Please send comments to the author. 2. Abstract This memo defines an experimental portion of the Management Information Base (MIB) for use with network management protocols in TCP/IP-based internets. In particular, it defines trap objects for use in remote network monitoring devices. This memo does not specify a standard for the Internet community. Steven Waldbusser [Page 1] Internet Draft Remote Network Monitoring Traps August 21, 1991 3. The Network Management Framework The Internet-standard Network Management Framework consists of three components. They are: RFC 1155 which defines the SMI, the mechanisms used for describing and naming objects for the purpose of management. RFC 1212 defines a more concise description mechanism, which is wholly consistent with the SMI. RFC 1156 which defines MIB-I, the core set of managed objects for the Internet suite of protocols. RFC 1213 defines MIB-II, an evolution of MIB-I based on implementation experience and new operational requirements. RFC 1157 which defines the SNMP, the protocol used for network access to managed objects. The Framework permits new objects to be defined for the purpose of experimentation and evaluation. Steven Waldbusser [Page 2] Internet Draft Remote Network Monitoring Traps August 21, 1991 4. Objects Managed objects are accessed via a virtual information store, termed the Management Information Base or MIB. Objects in the MIB are defined using the subset of Abstract Syntax Notation One (ASN.1) [7] defined in the SMI. In particular, each object has a name, a syntax, and an encoding. The name is an object identifier, an administratively assigned name, which specifies an object type. The object type together with an object instance serves to uniquely identify a specific instantiation of the object. For human convenience, we often use a textual string, termed the OBJECT DESCRIPTOR, to also refer to the object type. The syntax of an object type defines the abstract data structure corresponding to that object type. The ASN.1 language is used for this purpose. However, the SMI [3] purposely restricts the ASN.1 constructs which may be used. These restrictions are explicitly made for simplicity. The encoding of an object type is simply how that object type is represented using the object type's syntax. Implicitly tied to the notion of an object type's syntax and encoding is how the object type is represented when being transmitted on the network. The SMI specifies the use of the basic encoding rules of ASN.1 [8], subject to the additional requirements imposed by the SNMP. 4.1. Format of Definitions Section 6 contains contains the specification of all object types contained in this module. The object types are defined using the conventions defined in [10]. Steven Waldbusser [Page 3] Internet Draft Remote Network Monitoring Traps August 21, 1991 5. Definitions RFCxxxx-MIB DEFINITIONS ::= BEGIN IMPORTS experimental FROM RFC1155-SMI TRAP-TYPE FROM RFC-1215 rmon, alarmIndex, alarmVariable, alarmSampleType, alarmValue, alarmRisingThreshold, alarmFallingThreshold, channelIndex, channelMatches, channelDescription FROM RFC-ffff; -- This MIB module uses the TRAP-TYPE macro as defined in [10] -- Remote Network Monitoring Traps risingAlarm TRAP-TYPE ENTERPRISE { rmon } VARIABLES { alarmIndex, alarmVariable, alarmSampleType, alarmValue, alarmRisingThreshold } DESCRIPTION "The SNMP trap that is generated when an alarm entry crosses its rising threshold and generates an event that is configured for sending SNMP traps." ::= 1 fallingAlarm TRAP-TYPE ENTERPRISE { rmon } VARIABLES { alarmIndex, alarmVariable, alarmSampleType, alarmValue, alarmFallingThreshold } DESCRIPTION "The SNMP trap that is generated when an alarm entry crosses its falling threshold and generates an event that is configured for sending SNMP traps." ::= 2 packetMatch TRAP-TYPE ENTERPRISE { rmon } VARIABLES { channelIndex, channelMatches, channelDescription } DESCRIPTION "The SNMP trap that is generated when a packet Steven Waldbusser [Page 4] Internet Draft Remote Network Monitoring Traps August 21, 1991 is captured by a channel that is configured for sending SNMP traps." ::= 3 END Steven Waldbusser [Page 5] Internet Draft Remote Network Monitoring Traps August 21, 1991 6. Acknowledgments This document was produced by the IETF Remote Network Monitoring Working Group. Steven Waldbusser [Page 6] Internet Draft Remote Network Monitoring Traps August 21, 1991 7. References [1] V. Cerf, IAB Recommendations for the Development of Internet Network Management Standards. Internet Working Group Request for Comments 1052. Network Information Center, SRI International, Menlo Park, California, (April, 1988). [2] V. Cerf, Report of the Second Ad Hoc Network Management Review Group, Internet Working Group Request for Comments 1109. Network Information Center, SRI International, Menlo Park, California, (August, 1989). [3] M.T. Rose and K. McCloghrie, Structure and Identification of Management Information for TCP/IP-based internets, Internet Working Group Request for Comments 1155. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [4] K. McCloghrie and M.T. Rose, Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1156. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [5] J.D. Case, M.S. Fedor, M.L. Schoffstall, and J.R. Davin, Simple Network Management Protocol, Internet Working Group Request for Comments 1157. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [6] M.T. Rose (editor), Management Information Base for Network Management of TCP/IP-based internets, Internet Working Group Request for Comments 1158. Network Information Center, SRI International, Menlo Park, California, (May, 1990). [7] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987). [8] Information processing systems - Open Systems Interconnection - Specification of Basic Encoding Rules Steven Waldbusser [Page 7] Internet Draft Remote Network Monitoring Traps August 21, 1991 for Abstract Notation One (ASN.1), International Organization for Standardization. International Standard 8825, (December, 1987). [9] M.T. Rose, K. McCloghrie (editors), Towards Concise MIB Definitions, Internet Draft, Internet Engineering Task Force, (September, 1990). [10] M.T. Rose (editor), A Convention for Defining Traps for use with the SNMP, Internet Draft, Internet Engineering Task Force, (September, 1990). Steven Waldbusser [Page 8] Internet Draft Remote Network Monitoring Traps August 21, 1991 Table of Contents 1 Status of this Memo ................................... 1 2 Abstract .............................................. 1 3 The Network Management Framework ...................... 2 4 Objects ............................................... 3 4.1 Format of Definitions ............................... 3 5 Definitions ........................................... 4 6 Acknowledgments ....................................... 6 7 References ............................................ 7 Steven Waldbusser [Page 9]