Browse Prior Art Database

Event MIB (RFC2981)

IP.com Disclosure Number: IPCOM000005174D
Original Publication Date: 2000-Oct-01
Included in the Prior Art Database: 2001-Aug-16
Document File: 51 page(s) / 99K

Publishing Venue

Internet Society Requests For Comment (RFCs)

Related People

R. Kavasseri (Editor of this version): AUTHOR

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects that can be used to manage and monitor MIB objects and take action through events.

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

Network Working Group R. Kavasseri Request for Comments: 2981 (Editor of this version) Category: Standards Track B. Stewart (Author of previous version) Cisco Systems, Inc.

October 2000

Event MIB

Status of this Memo

This document specifies an Internet standards track protocol for the Internet community, and requests discussion and suggestions for improvements. Please refer to the current edition of the "Internet Official Protocol Standards" (STD 1) for the standardization state and status of this protocol. Distribution of this memo is unlimited.

Copyright Notice

Copyright (C) The Internet Society (2000). All Rights Reserved.

Abstract

This memo defines a portion of the Management Information Base (MIB) for use with network management protocols in the Internet community. In particular, it describes managed objects that can be used to manage and monitor MIB objects and take action through events.

The Event MIB provides the ability to monitor MIB objects on the local system or on a remote system and take simple action when a trigger condition is met.

The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this document are to be interpreted as described in RFC 2119.

Table of Contents

1 The SNMP Management Framework ............................... 2 2 Overview .................................................... 3 3 Relationship to Other MIBs .................................. 3 4 MIB Sections ................................................ 4 5 Operation ................................................... 5 6 Security .................................................... 7 7 Definitions ................................................. 7 8 Intellectual Property ....................................... 47 9 Acknowledgements ............................................ 47

Kavasseri Stewart Standards Track [Page 1]

RFC 2981 Event MIB October 2000

10 References ................................................. 47 11 Security Considerations .................................... 49 12 Author's Address ........................................... 49 13 Editor's Address ........................................... 49 14 Full Copyright Statement ................................... 50

1. The SNMP Management Framework

The SNMP Management Framework presently consists of five major components:

o An overall architecture, described in RFC 2571 [RFC2571].

o Mechanisms for describing and naming objects and events for the purpose of management. The first version of this Structure of Management Information (SMI) is called SMIv1 and described in STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 [RFC2580].

o Message protocols for transferring management information. The first version of the SNMP message protocol is called SNMPv1 and described in STD 15, RFC 1157 [RFC11...