draft-ietf-disman-event-mib-09.txt   rfc2981.txt 
Internet Draft Distributed Management Event MIB 6 January 2000
Event MIB
6 January 2000
draft-ietf-disman-event-mib-09.txt
Bob Stewart
Cisco Systems, Inc.
Ramanathan R. Kavasseri
Cisco Systems, Inc.
Status of this Memo Network Working Group R. Kavasseri
Request for Comments: 2981 (Editor of this version)
This document is an Internet-Draft and is in full conformance with all Category: Standards Track B. Stewart
provisions of Section 10 of RFC2026. (Author of previous version)
Cisco Systems, Inc.
October 2000
Internet-Drafts are working documents of the Internet Engineering Task Event MIB
Force (IETF), its areas, and its working groups. Note that other groups
may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Status of this Memo
and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at This document specifies an Internet standards track protocol for the
http://www.ietf.org/ietf/1id-abstracts.txt 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.
The list of Internet-Draft Shadow Directories can be accessed at Copyright Notice
http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to the Copyright (C) The Internet Society (2000). All Rights Reserved.
Distributed Management Working Group, <disman@dorothy.BMC.com>.
Copyright Notice Abstract
Copyright (C) The Internet Society (2000). All Rights Reserved. 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.
1. Abstract 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.
This memo defines an experimental portion of the Management Information The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
Base (MIB) for use with network management protocols in the Internet "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
community. In particular, it describes managed objects that can be used document are to be interpreted as described in RFC 2119.
to manage and monitor MIB objects and take action through events.
The Event MIB provides the ability to monitor MIB objects on the local Table of Contents
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", 1 The SNMP Management Framework ............................... 2
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 2 Overview .................................................... 3
document are to be interpreted as described in RFC 2119. 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
10 References ................................................. 47
11 Security Considerations .................................... 49
12 Author's Address ........................................... 49
13 Editor's Address ........................................... 49
14 Full Copyright Statement ................................... 50
2. The SNMP Management Framework 1. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described 1215 [RFC1215]. The second version, called SMIv2, is described
in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and RFC 2580 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and
[RFC2580]. STD 58, RFC 2580 [RFC2580].
o Message protocols for transferring management information. The o Message protocols for transferring management information. The
first version of the SNMP message protocol is called SNMPv1 and first version of the SNMP message protocol is called SNMPv1 and
described in STD 15, RFC 1157 [RFC1157]. A second version of the described in STD 15, RFC 1157 [RFC1157]. A second version of
SNMP message protocol, which is not an Internet standards track the SNMP message protocol, which is not an Internet standards
protocol, is called SNMPv2c and described in RFC 1901 [RFC1901] track protocol, is called SNMPv2c and described in RFC 1901
and RFC 1906 [RFC1906]. The third version of the message [RFC1901] and RFC 1906 [RFC1906]. The third version of the
protocol is called SNMPv3 and described in RFC 1906 [RFC1906], message protocol is called SNMPv3 and described in RFC 1906
RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574].
o Protocol operations for accessing management information. The o Protocol operations for accessing management information. The
first set of protocol operations and associated PDU formats is first set of protocol operations and associated PDU formats is
described in STD 15, RFC 1157 [RFC1157]. A second set of described in STD 15, RFC 1157 [RFC1157]. A second set of
protocol operations and associated PDU formats is described in protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905]. RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2573 o A set of fundamental applications described in RFC 2573
[RFC2573] and the view-based access control mechanism described [RFC2573] and the view-based access control mechanism described
in RFC 2575 [RFC2575]. in RFC 2575 [RFC2575].
A more detailed introduction to the current SNMP Management Framework A more detailed introduction to the current SNMP Management Framework
can be found in RFC 2570 [RFC2570]. can be found in RFC 2570 [RFC2570].
Managed objects are accessed via a virtual information store, termed Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. It may not be possible to meaningfully monitor Counter64 objects MIB. It may not be possible to meaningfully monitor Counter64
using an SMIv1 version of the MIB. objects using an SMIv1 version of the MIB.
3. Overview 2. Overview
With network sizes well beyond the ability of people to manage them With network sizes well beyond the ability of people to manage them
directly, automated, distributed management is vital. An important directly, automated, distributed management is vital. An important
aspect of such management is the ability of a system to monitor itself aspect of such management is the ability of a system to monitor
or for some other system to monitor it. itself or for some other system to monitor it.
The Event MIB provides the ability to monitor MIB objects on the local The Event MIB provides the ability to monitor MIB objects on the
system or on a remote system and take simple action when a trigger local system or on a remote system and take simple action when a
condition is met. trigger condition is met.
The MIB is intended to suit either a relatively powerful manager or mid- The MIB is intended to suit either a relatively powerful manager or
level manager, as well as a somewhat more limited self-managing system. mid- level manager, as well as a somewhat more limited self-managing
system.
4. Relationship to Other MIBs 3. Relationship to Other MIBs
The Event MIB is based on extensive experience with the RMON MIB The Event MIB is based on extensive experience with the RMON MIB
[RFC1757] and provides a superset of the capabilities of the RMON alarm [RFC1757] and provides a superset of the capabilities of the RMON
and event groups. Conceptually, the key extension is the ability to alarm and event groups. Conceptually, the key extension is the
allow alarms to be generated for MIB objects that are on another network ability to allow alarms to be generated for MIB objects that are on
element. The Event MIB calls "triggers" what the RMON MIB called another network element. The Event MIB calls "triggers" what the
"alarms," but the concepts are the same. Event MIB triggers maintain RMON MIB called "alarms," but the concepts are the same. Event MIB
the RMON handling of thresholds and add the concept of booleans. Event triggers maintain the RMON handling of thresholds and add the concept
MIB events maintain the RMON concept of sending an SNMP notification in of booleans. Event MIB events maintain the RMON concept of sending
response to a trigger and add the concept of setting a MIB object. an SNMP notification in response to a trigger and add the concept of
setting a MIB object.
The Event MIB is the successor and update to SNMPv2's Manager-to-Manager The Event MIB is the successor and update to SNMPv2's Manager-to-
MIB [RFC1451] which was declared Historic pending this work. Manager MIB [RFC1451] which was declared Historic pending this work.
The Event MIB depends on the services of the SNMPv3 Management Target The Event MIB depends on the services of the SNMPv3 Management Target
and Notification MIBs [RFC2573]. and Notification MIBs [RFC2573].
The Event MIB is nicely complemented by the Distributed Management The Event MIB is nicely complemented by the Distributed Management
Expression MIB [RFCExpressionMIB], which is the expected source of Expression MIB [RFC2982], which is the expected source of boolean
boolean objects to monitor. Note that there is considerable overlap objects to monitor. Note that there is considerable overlap between
between the wildcard and delta sample capabilities of the Event and the wildcard and delta sample capabilities of the Event and
Expression MIBs. A carefully-planned implementation might well use Expression MIBs. A carefully-planned implementation might well use
common code to provide the overlapping functions. common code to provide the overlapping functions.
5. MIB Sections 4. MIB Sections
The MIB has four sections: triggers, objects, events, and notifications. The MIB has four sections: triggers, objects, events, and
Triggers define the conditions that lead to events. Events may cause notifications. Triggers define the conditions that lead to events.
notifications. Events may cause notifications.
The trigger table lists what objects are to be monitored and how and The trigger table lists what objects are to be monitored and how and
relates each trigger to an event. It has supplementary, companion relates each trigger to an event. It has supplementary, companion
tables for additional objects that depend on the type of test done for tables for additional objects that depend on the type of test done
the trigger. for the trigger.
The objects table lists objects that can be added to notifications based The objects table lists objects that can be added to notifications
on the trigger, the trigger test type, or the event that resulted in the based on the trigger, the trigger test type, or the event that
notification. resulted in the notification.
The event table defines what happens when an event is triggered: sending The event table defines what happens when an event is triggered:
a notification, setting a MIB object or both. It has supplementary, sending a notification, setting a MIB object or both. It has
companion tables for additional objects that depend on the action taken. supplementary, companion tables for additional objects that depend on
the action taken.
The notification section defines a set of generic notifications to go The notification section defines a set of generic notifications to go
with the events and for Event MIB error handling, and it defines a set with the events and for Event MIB error handling, and it defines a
of objects to put in those notifications. set of objects to put in those notifications.
The following diagram describes the relationships between the tables The following diagram describes the relationships between the tables
in the Event MIB. in the Event MIB.
+--------------------------------+ +-----------------------------+
| mteTriggerEntry | subclassed by: | mteTriggerEntry | subclassed by:
| { mteOwner, |---+ | { mteOwner, |---+
| IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry | IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry
| | | | | |
| | +-- mteTriggerExistenceEntry | | +-- mteTriggerExistenceEntry
| | | | | |
| | +-- mteTriggerBooleanEntry | | +-- mteTriggerBooleanEntry
| | | | | |
| | +-- mteTriggerThresholdEntry | | +-- mteTriggerThresholdEntry
| | | |
| | | mteTrigger*Event -------------------------------->+
| | | | |
| | | mteTriggerObjects ------------------>+ |
| mteTrigger*Event ----------------------------->+ +-----------------------------+ | |
| | |
| mteTriggerObjects --------------->+ |
| | | |
+--------------------------------+ | |
| | | |
V | +-----------------------------+ V |
+<--------------------------------------------+ | | mteObjectsEntry | | |
| | | { mteOwner, |<-------------+ |
V | | mteObjectsName, | |
+--------------------------------+ | | mteObjectsIndex } | |
| | | +-----------------------------+ |
| mteObjectsEntry | |
| { mteOwner, | |
| mteObjectsName, | |
| mteObjectsIndex } | |
| | |
+--------------------------------+ |
|
V V
+<---------------------------------------------------------+ +---------------------------+ |
| | mteEventEntry |<----------------------------+
V | { mteOwner, |
+---------------------------------+ | IMPLIED mteEventName } |
| | | |
| mteEventEntry | | mteEventAction---> + (condition)
| { mteOwner, | +---------------------------+ |
| IMPLIED mteEventName } | V
| | +---------------------------+ | +---------------------------+
| mteEventAction - - - - - - > + (condition) | mteEventNotificationEntry | | | mteEventSetEntry |
| | | | { mteOwner, |<--+-->| { mteOwner, |
+---------------------------------+ | | IMPLIED mteEventName } | | IMPLIED mteEventName } |
| +---------------------------+ +---------------------------+
+ < - - - + < - - - - - - - - - - - - - - +
| |
| |
| |
| V
| +---------------------------------+
| | |
| | mteEventNotificationEntry |
| | { mteOwner, |
| | IMPLIED mteEventName } |
| | |
| +---------------------------------+
|
|
|
V
+---------------------------------+
| |
| mteEventSetEntry |
| { mteOwner, |
| IMPLIED mteEventName } |
| |
+---------------------------------+
6. Operation 5. Operation
The Event MIB is instrumentation for a distributed management The Event MIB is instrumentation for a distributed management
application that monitors MIB objects. In its simplest form this application that monitors MIB objects. In its simplest form this
application monitors individual, local MIB objects, just as an RMON application monitors individual, local MIB objects, just as an RMON
probe fulfills the functions implied by RMON's alarm and event probe fulfills the functions implied by RMON's alarm and event
operation. Additionally the application can monitor remote objects and operation. Additionally the application can monitor remote objects
wildcarded groups of objects. and wildcarded groups of objects.
Remote monitoring uses the tag service of the Management Target MIB Remote monitoring uses the tag service of the Management Target MIB
[RFC2573] to select and access remote systems as an ordinary SNMP-based [RFC2573] to select and access remote systems as an ordinary SNMP-
management application. Local monitoring may be via a more intimate, based management application. Local monitoring may be via a more
local interface which may, for example, bypass SNMP encoding but intimate, local interface which may, for example, bypass SNMP
otherwise is functionally identical to remote SNMP operation, including encoding but otherwise is functionally identical to remote SNMP
the application of access control. A self-management only system MAY operation, including the application of access control. A self-
not implement remote monitoring. management only system MAY not implement remote monitoring.
Wildcards indicate that the application SHOULD use a GetNext-type Wildcards indicate that the application SHOULD use a GetNext-type
operation to find the zero or more instances implied by a truncated operation to find the zero or more instances implied by a truncated
object identifier, just like an ordinary SNMP-based management object identifier, just like an ordinary SNMP-based management
application. Each instance of a wildcard is treated as if it were a application. Each instance of a wildcard is treated as if it were a
separate entry, that is the instances of a wildcarded object are separate entry, that is the instances of a wildcarded object are
independent of one another. For example, a wild-carded object may independent of one another. For example, a wild-carded object may
trigger an event, and result in the setting of another wildcarded trigger an event, and result in the setting of another wildcarded
object. The instance that satisfied the trigger function is used to object. The instance that satisfied the trigger function is used to
perform the set function. All of this takes place independently of any perform the set function. All of this takes place independently of
additional instances that may fill the wildcard. any additional instances that may fill the wildcard.
Error handling is by notification. These error notifications SHOULD be Error handling is by notification. These error notifications SHOULD
enabled only for the diagnosis of problems indicated by error counters. be enabled only for the diagnosis of problems indicated by error
If minimizing the probability of notification loss is a concern they counters. If minimizing the probability of notification loss is a
SHOULD be transmitted as Inform PDUs as described in the [SNMP-TARGET- concern they SHOULD be transmitted as Inform PDUs as described in the
MIB] or directed to a log as described in the Notification Log MIB [SNMP-TARGET-MIB] or directed to a log as described in the
[rfcNotificationLogMIB]. Note that this does not mean the Notification Notification Log MIB [rfcNotificationLogMIB]. Note that this does
Log MIB is REQUIRED, since in fact notifications usually are not lost, not mean the Notification Log MIB is REQUIRED, since in fact
but that the Notification Log MIB can be helpful with this as well as notifications usually are not lost, but that the Notification Log MIB
other MIBs that include notifications. can be helpful with this as well as other MIBs that include
notifications.
Although like most MIBs this one has no explicit controls for the Although like most MIBs this one has no explicit controls for the
persistence of the values set in configuring events, a robust, polite persistence of the values set in configuring events, a robust, polite
implementation would certainly not force its managing applications to implementation would certainly not force its managing applications to
reconfigure it whenever it resets. reconfigure it whenever it resets.
Again, as with most MIBs, it is implementation-specific how a system Again, as with most MIBs, it is implementation-specific how a system
provides and manages such persistence. To speculate, one could imagine, provides and manages such persistence. To speculate, one could
for example, that persistence depended on the context in which the imagine, for example, that persistence depended on the context in
expression was configured, or perhaps system-specific characteristics of which the expression was configured, or perhaps system-specific
the expression's owner. Or perhaps everything in a MIB such as this characteristics of the expression's owner. Or perhaps everything in
one, which is clearly aimed at persistent configuration, is a MIB such as this one, which is clearly aimed at persistent
automatically part of a system's other persistent configuration. configuration, is automatically part of a system's other persistent
configuration.
7. Security 6. Security
Security of Event MIB entries depends on SNMPv3 access control for the Security of Event MIB entries depends on SNMPv3 access control for
entire MIB or for subsets based on entry owner names. the entire MIB or for subsets based on entry owner names.
Security of monitored objects for remote access depends on the Security of monitored objects for remote access depends on the
Management Target MIB [RFC2573]. Security for local access can depend Management Target MIB [RFC2573]. Security for local access can
on the Management Target MIB or on recording appropriate security depend on the Management Target MIB or on recording appropriate
credentials of the creator of an entry and using those to access the security credentials of the creator of an entry and using those to
local objects. These security credentials are the parameters necessary access the local objects. These security credentials are the
as inputs to isAccessAllowed from the Architecture for Describing SNMP parameters necessary as inputs to isAccessAllowed from the
Management Frameworks. When accessing local objects without using a Architecture for Describing SNMP Management Frameworks. When
local target tag, the system MUST (conceptually) use isAccessAllowed to accessing local objects without using a local target tag, the system
ensure that it does not violate security. MUST (conceptually) use isAccessAllowed to ensure that it does not
violate security.
To facilitate the provisioning of access control by a security To facilitate the provisioning of access control by a security
administrator for this MIB itself using the View-Based Access Control administrator for this MIB itself using the View-Based Access Control
Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple Model (VACM) defined in RFC 2275 [RFC2575] for tables in which
users may need to independently create or modify entries, the initial multiple users may need to independently create or modify entries,
index is used as an "owner index". Such an initial index has a syntax of the initial index is used as an "owner index". Such an initial index
SnmpAdminString, and can thus be trivially mapped to a securityName or has a syntax of SnmpAdminString, and can thus be trivially mapped to
groupName as defined in VACM, in accordance with a security policy. a securityName or groupName as defined in VACM, in accordance with a
security policy.
All entries in related tables belonging to a particular user will have If a security administrator were to employ such an approach, all
the same value for this initial index. For a given user's entries in a entries in related tables belonging to a particular user will have
particular table, the object identifiers for the information in these the same value for this initial index. For a given user's entries in
entries will have the same sub-identifiers (except for the "column" sub- a particular table, the object identifiers for the information in
identifier) up to the end of the encoded owner index. To configure VACM these entries will have the same sub-identifiers (except for the
to permit access to this portion of the table, one would create "column" sub-identifier) up to the end of the encoded owner index.
vacmViewTreeFamilyTable entries with the value of To configure VACM to permit access to this portion of the table, one
vacmViewTreeFamilySubtree including the owner index portion, and would create vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilyMask "wildcarding" the column sub-identifier. More vacmViewTreeFamilySubtree including the owner index portion, and
elaborate configurations are possible. vacmViewTreeFamilyMask "wildcarding" the column sub-identifier. More
elaborate configurations are possible.
8. Definitions 7. Definitions
DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Unsigned32, Integer32, Unsigned32,
NOTIFICATION-TYPE, Counter32, NOTIFICATION-TYPE, Counter32,
Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TruthValue FROM SNMPv2-TC TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
sysUpTime FROM SNMPv2-MIB sysUpTime FROM SNMPv2-MIB
SnmpTagValue FROM SNMP-TARGET-MIB SnmpTagValue FROM SNMP-TARGET-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
dismanEventMIB MODULE-IDENTITY dismanEventMIB MODULE-IDENTITY
LAST-UPDATED "200001060000Z" -- 6 January 2000 LAST-UPDATED "200010160000Z" -- 16 October 2000
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Ramanathan Kavasseri CONTACT-INFO "Ramanathan Kavasseri
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose CA 95134-1706. San Jose CA 95134-1706.
Phone: +1 408 526 4527 Phone: +1 408 526 4527
Email: ramk@cisco.com" Email: ramk@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for defining event triggers and actions "The MIB module for defining event triggers and actions
for network management purposes." for network management purposes."
-- Revision History -- Revision History
REVISION "200001060000Z" -- 6 January 2000 REVISION "200010160000Z" -- 16 October 2000
DESCRIPTION "This is the initial version of this MIB. DESCRIPTION "This is the initial version of this MIB.
Published as RFC xxxxx" Published as RFC 2981"
::= { mib-2 xx } - final assignment by IANA at publication time ::= { mib-2 88 }
dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
-- Management Triggered Event (MTE) objects -- Management Triggered Event (MTE) objects
mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
FailureReason ::= TEXTUAL-CONVENTION FailureReason ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reasons for failures in an attempt to perform a management "Reasons for failures in an attempt to perform a management
request. request.
skipping to change at page 11, line 25 skipping to change at page 9, line 11
to problems in sending the request. The existence of a to problems in sending the request. The existence of a
particular error code here does not imply that all particular error code here does not imply that all
implementations are capable of sensing that error and implementations are capable of sensing that error and
returning that code. returning that code.
The second group, numbered greater than 0, are copied The second group, numbered greater than 0, are copied
directly from SNMP protocol operations and are intended to directly from SNMP protocol operations and are intended to
carry exactly the meanings defined for the protocol as returned carry exactly the meanings defined for the protocol as returned
in an SNMP response. in an SNMP response.
localResourceLack some local resource such as memory lacking localResourceLack some local resource such as memory
or mteResourceSampleInstanceMaximum lacking or
mteResourceSampleInstanceMaximum
exceeded exceeded
badDestination unrecognized domain name or otherwise badDestination unrecognized domain name or otherwise
invalid destination address invalid destination address
destinationUnreachable can't get to destination address destinationUnreachable can't get to destination address
noResponse no response to SNMP request noResponse no response to SNMP request
badType the data syntax of a retrieved object badType the data syntax of a retrieved object
as not as expected as not as expected
sampleOverrun another sample attempt occurred before sampleOverrun another sample attempt occurred before
the previous one completed" the previous one completed"
skipping to change at page 16, line 39 skipping to change at page 14, line 9
mteTriggerBooleanTest. If the test result is true the trigger mteTriggerBooleanTest. If the test result is true the trigger
fires. The trigger will not fire again until the value has fires. The trigger will not fire again until the value has
become false and come back to true. become false and come back to true.
For 'threshold' the test works as described below for For 'threshold' the test works as described below for
mteTriggerThresholdStartup, mteTriggerThresholdRising, and mteTriggerThresholdStartup, mteTriggerThresholdRising, and
mteTriggerThresholdFalling. mteTriggerThresholdFalling.
Note that combining 'boolean' and 'threshold' tests on the Note that combining 'boolean' and 'threshold' tests on the
same object may be somewhat redundant." same object may be somewhat redundant."
DEFVAL { boolean } DEFVAL { { boolean } }
::= { mteTriggerEntry 4 } ::= { mteTriggerEntry 4 }
mteTriggerSampleType OBJECT-TYPE mteTriggerSampleType OBJECT-TYPE
SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } SYNTAX INTEGER { absoluteValue(1), deltaValue(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of sampling to perform. "The type of sampling to perform.
An 'absoluteValue' sample requires only a single sample to be An 'absoluteValue' sample requires only a single sample to be
meaningful, and is exactly the value of the object at meaningful, and is exactly the value of the object at
mteTriggerValueID at the sample time. mteTriggerValueID at the sample time.
A 'deltaValue' requires two samples to be meaningful and is A 'deltaValue' requires two samples to be meaningful and is
thus not available for testing until the second and subsequent thus not available for testing until the second and subsequent
samples after the object at mteTriggerValueID is first found samples after the object at mteTriggerValueID is first found
to exist. It is the difference between the two samples. For to exist. It is the difference between the two samples. For
unsigned values it is always positive, based on unsigned unsigned values it is always positive, based on unsigned
arithmetic. For signed values it can be positive or negative. arithmetic. For signed values it can be positive or negative.
For SNMP counters to be meaningful they MUST be sampled as a For SNMP counters to be meaningful they should be sampled as a
'deltaValue'. 'deltaValue'.
For 'deltaValue' mteTriggerDeltaTable contains further For 'deltaValue' mteTriggerDeltaTable contains further
parameters. parameters.
If only 'existence' is set in mteTriggerTest this object has If only 'existence' is set in mteTriggerTest this object has
no meaning." no meaning."
DEFVAL { absoluteValue } DEFVAL { absoluteValue }
::= { mteTriggerEntry 5 } ::= { mteTriggerEntry 5 }
skipping to change at page 29, line 31 skipping to change at page 26, line 4
mteTriggerThresholdStartup INTEGER, mteTriggerThresholdStartup INTEGER,
mteTriggerThresholdRising Integer32, mteTriggerThresholdRising Integer32,
mteTriggerThresholdFalling Integer32, mteTriggerThresholdFalling Integer32,
mteTriggerThresholdDeltaRising Integer32, mteTriggerThresholdDeltaRising Integer32,
mteTriggerThresholdDeltaFalling Integer32, mteTriggerThresholdDeltaFalling Integer32,
mteTriggerThresholdObjectsOwner SnmpAdminString, mteTriggerThresholdObjectsOwner SnmpAdminString,
mteTriggerThresholdObjects SnmpAdminString, mteTriggerThresholdObjects SnmpAdminString,
mteTriggerThresholdRisingEventOwner SnmpAdminString, mteTriggerThresholdRisingEventOwner SnmpAdminString,
mteTriggerThresholdRisingEvent SnmpAdminString, mteTriggerThresholdRisingEvent SnmpAdminString,
mteTriggerThresholdFallingEventOwner SnmpAdminString, mteTriggerThresholdFallingEventOwner SnmpAdminString,
mteTriggerThresholdFallingEvent SnmpAdminString mteTriggerThresholdFallingEvent SnmpAdminString,
mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString, mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString,
mteTriggerThresholdDeltaRisingEvent SnmpAdminString, mteTriggerThresholdDeltaRisingEvent SnmpAdminString,
mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString, mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString,
mteTriggerThresholdDeltaFallingEvent SnmpAdminString mteTriggerThresholdDeltaFallingEvent SnmpAdminString
} }
mteTriggerThresholdStartup OBJECT-TYPE mteTriggerThresholdStartup OBJECT-TYPE
SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 30, line 48 skipping to change at page 27, line 18
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A threshold value to check against if mteTriggerType is "A threshold value to check against if mteTriggerType is
'threshold'. 'threshold'.
When the current sampled value is less than or equal to this When the current sampled value is less than or equal to this
threshold, and the value at the last sampling interval was threshold, and the value at the last sampling interval was
greater than this threshold, one greater than this threshold, one
mteTriggerThresholdFallingEvent is triggered. That event is mteTriggerThresholdFallingEvent is triggered. That event is
also triggered if the first sample afer this entry bcomes also triggered if the first sample after this entry becomes
active is less than or equal to this threshold and active is less than or equal to this threshold and
mteTriggerThresholdStartup is equal to 'falling' or mteTriggerThresholdStartup is equal to 'falling' or
'risingOrFalling'. 'risingOrFalling'.
After a falling event is generated, another such event is not After a falling event is generated, another such event is not
triggered until the sampled value rises above this threshold triggered until the sampled value rises above this threshold
and reaches mteTriggerThresholdRising." and reaches mteTriggerThresholdRising."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerThresholdEntry 3 } ::= { mteTriggerThresholdEntry 3 }
skipping to change at page 31, line 27 skipping to change at page 27, line 42
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A threshold value to check against if mteTriggerType is "A threshold value to check against if mteTriggerType is
'threshold'. 'threshold'.
When the delta value (difference) between the current sampled When the delta value (difference) between the current sampled
value (value(n)) and the previous sampled value (value(n-1)) value (value(n)) and the previous sampled value (value(n-1))
is greater than or equal to this threshold, is greater than or equal to this threshold,
and the delta value calculated at the last sampling interval and the delta value calculated at the last sampling interval
(i.e. value(n-1) - value(n-2)) was less than this threshold, (i.e. value(n-1) - value(n-2)) was less than this threshold,
one mteTriggerThresholdDeltaRisingEvent is triggered. That event is one mteTriggerThresholdDeltaRisingEvent is triggered. That event
also triggered if the first delta value calculated after this is also triggered if the first delta value calculated after this
entry becomes active, i.e. value(2) - value(1), where value(1) entry becomes active, i.e. value(2) - value(1), where value(1)
is the first sample taken of that instance, is greater than or is the first sample taken of that instance, is greater than or
equal to this threshold. equal to this threshold.
After a rising event is generated, another such event is not After a rising event is generated, another such event is not
triggered until the delta value falls below this threshold and triggered until the delta value falls below this threshold and
reaches mteTriggerThresholdDeltaFalling." reaches mteTriggerThresholdDeltaFalling."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerThresholdEntry 4 } ::= { mteTriggerThresholdEntry 4 }
skipping to change at page 32, line 7 skipping to change at page 28, line 19
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A threshold value to check against if mteTriggerType is "A threshold value to check against if mteTriggerType is
'threshold'. 'threshold'.
When the delta value (difference) between the current sampled When the delta value (difference) between the current sampled
value (value(n)) and the previous sampled value (value(n-1)) value (value(n)) and the previous sampled value (value(n-1))
is less than or equal to this threshold, is less than or equal to this threshold,
and the delta value calculated at the last sampling interval and the delta value calculated at the last sampling interval
(i.e. value(n-1) - value(n-2)) was greater than this threshold, (i.e. value(n-1) - value(n-2)) was greater than this threshold,
one mteTriggerThresholdDeltaFallingEvent is triggered. That event is one mteTriggerThresholdDeltaFallingEvent is triggered. That event
also triggered if the first delta value calculated after this is also triggered if the first delta value calculated after this
entry becomes active, i.e. value(2) - value(1), where value(1) entry becomes active, i.e. value(2) - value(1), where value(1)
is the first sample taken of that instance, is less than or is the first sample taken of that instance, is less than or
equal to this threshold. equal to this threshold.
After a falling event is generated, another such event is not After a falling event is generated, another such event is not
triggered until the delta value falls below this threshold and triggered until the delta value falls below this threshold and
reaches mteTriggerThresholdDeltaRising." reaches mteTriggerThresholdDeltaRising."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerThresholdEntry 5 } ::= { mteTriggerThresholdEntry 5 }
skipping to change at page 33, line 48 skipping to change at page 30, line 10
'threshold' and this trigger fires based on 'threshold' and this trigger fires based on
mteTriggerThresholdFalling. A length of 0 indicates no event." mteTriggerThresholdFalling. A length of 0 indicates no event."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 11 } ::= { mteTriggerThresholdEntry 11 }
mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner of an "To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner
event entry from mteEventTable." of an event entry from mteEventTable."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 12 } ::= { mteTriggerThresholdEntry 12 }
mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is "The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on 'threshold' and this trigger fires based on
mteTriggerThresholdDeltaRising. A length of 0 indicates no event." mteTriggerThresholdDeltaRising. A length of 0 indicates
no event."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 13 } ::= { mteTriggerThresholdEntry 13 }
mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner of an "To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner
event entry from mteEventTable." of an event entry from mteEventTable."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 14 } ::= { mteTriggerThresholdEntry 14 }
mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is "The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on 'threshold' and this trigger fires based on
mteTriggerThresholdDeltaFalling. A length of 0 indicates no event." mteTriggerThresholdDeltaFalling. A length of 0 indicates
no event."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 15 } ::= { mteTriggerThresholdEntry 15 }
-- --
-- Objects Table -- Objects Table
-- --
mteObjectsTable OBJECT-TYPE mteObjectsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteObjectsEntry SYNTAX SEQUENCE OF MteObjectsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of objects that can be added to notifications based "A table of objects that can be added to notifications based
on the trigger, trigger test, or event, as pointed to by on the trigger, trigger test, or event, as pointed to by
entries in those tables." entries in those tables."
::= { mteObjects 1 } ::= { mteObjects 1 }
skipping to change at page 35, line 46 skipping to change at page 31, line 50
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for a group "A locally-unique, administratively assigned name for a group
of objects." of objects."
::= { mteObjectsEntry 1 } ::= { mteObjectsEntry 1 }
mteObjectsIndex OBJECT-TYPE mteObjectsIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary small integer for the purpose of identifying "An arbitrary integer for the purpose of identifying
individual objects within a mteObjectsName group. individual objects within a mteObjectsName group.
Objects within a group are placed in the notification in the Objects within a group are placed in the notification in the
numerical order of this index. numerical order of this index.
Groups are placed in the notification in the order of the Groups are placed in the notification in the order of the
selections for overall trigger, trigger test, and event. selections for overall trigger, trigger test, and event.
Within trigger test they are in the same order as the Within trigger test they are in the same order as the
numerical values of the bits defined for mteTriggerTest. numerical values of the bits defined for mteTriggerTest.
skipping to change at page 39, line 7 skipping to change at page 34, line 43
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actions to perform when this event occurs. "The actions to perform when this event occurs.
For 'notification', Traps and/or Informs are sent according For 'notification', Traps and/or Informs are sent according
to the configuration in the SNMP Notification MIB. to the configuration in the SNMP Notification MIB.
For 'set', an SNMP Set operation is performed according to For 'set', an SNMP Set operation is performed according to
control values in this entry." control values in this entry."
DEFVAL { '0'H } -- No bits set. DEFVAL { {} } -- No bits set.
::= { mteEventEntry 3 } ::= { mteEventEntry 3 }
mteEventEnabled OBJECT-TYPE mteEventEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A control to allow an event to be configured but not used. "A control to allow an event to be configured but not used.
When the value is 'false' the event does not execute even if When the value is 'false' the event does not execute even if
triggered." triggered."
skipping to change at page 43, line 14 skipping to change at page 38, line 35
mteEventSetTargetTag OBJECT-TYPE mteEventSetTargetTag OBJECT-TYPE
SYNTAX SnmpTagValue SYNTAX SnmpTagValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tag for the target(s) at which to set the object at "The tag for the target(s) at which to set the object at
mteEventSetObject to mteEventSetValue if mteEventActions mteEventSetObject to mteEventSetValue if mteEventActions
has 'set' set. has 'set' set.
Systems limited to self management MAY not accept a non-zero Systems limited to self management MAY reject a non-zero
length for the value of this object. length for the value of this object.
A length of 0 indicates the local system. In this case, A length of 0 indicates the local system. In this case,
access to the objects indicated by mteEventSetObject is under access to the objects indicated by mteEventSetObject is under
the security credentials of the requester that set the security credentials of the requester that set
mteTriggerEntryStatus to 'active'. Those credentials are the mteTriggerEntryStatus to 'active'. Those credentials are the
input parameters for isAccessAllowed from the Architecture for input parameters for isAccessAllowed from the Architecture for
Describing SNMP Management Frameworks. Describing SNMP Management Frameworks.
Otherwise access rights are checked according to the security Otherwise access rights are checked according to the security
skipping to change at page 44, line 15 skipping to change at page 39, line 33
"Control for whether mteEventSetContextName is to be treated as "Control for whether mteEventSetContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard fully-specified or wildcarded, with 'true' indicating wildcard
if mteEventActions has 'set' set." if mteEventActions has 'set' set."
DEFVAL { false } DEFVAL { false }
::= { mteEventSetEntry 6 } ::= { mteEventSetEntry 6 }
-- --
-- Notifications -- Notifications
-- --
dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::= { dismanEventMIB 2 } dismanEventMIBNotificationPrefix OBJECT IDENTIFIER ::=
{ dismanEventMIB 2 }
dismanEventMIBNotifications OBJECT IDENTIFIER ::= dismanEventMIBNotifications OBJECT IDENTIFIER ::=
{ dismanEventMIBNotificationPrefix 0 } { dismanEventMIBNotificationPrefix 0 }
dismanEventMIBNotificationObjects OBJECT IDENTIFIER dismanEventMIBNotificationObjects OBJECT IDENTIFIER
::= { dismanEventMIBNotificationPrefix 1 } ::= { dismanEventMIBNotificationPrefix 1 }
-- --
-- Notification Objects -- Notification Objects
-- --
mteHotTrigger OBJECT-TYPE mteHotTrigger OBJECT-TYPE
skipping to change at page 45, line 15 skipping to change at page 40, line 31
information determined in processing." information determined in processing."
::= { dismanEventMIBNotificationObjects 3 } ::= { dismanEventMIBNotificationObjects 3 }
mteHotOID OBJECT-TYPE mteHotOID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object identifier of the destination object related to the "The object identifier of the destination object related to the
notification. This MUST be as fully-qualified as possible, notification. This MUST be as fully-qualified as possible,
inluding filling in wildcard information determined in including filling in wildcard information determined in
processing. processing.
For a trigger-related notification this is from For a trigger-related notification this is from
mteTriggerValueID. mteTriggerValueID.
For a set failure this is from mteEventSetObject." For a set failure this is from mteEventSetObject."
::= { dismanEventMIBNotificationObjects 4 } ::= { dismanEventMIBNotificationObjects 4 }
mteHotValue OBJECT-TYPE mteHotValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
skipping to change at page 47, line 33 skipping to change at page 42, line 42
important information. It should be used only to help diagnose important information. It should be used only to help diagnose
a problem that has appeared in the error counters and can not a problem that has appeared in the error counters and can not
be found otherwise." be found otherwise."
::= { dismanEventMIBNotifications 5 } ::= { dismanEventMIBNotifications 5 }
-- --
-- Conformance -- Conformance
-- --
dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 } dismanEventMIBConformance OBJECT IDENTIFIER ::= { dismanEventMIB 3 }
dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1 } dismanEventMIBCompliances OBJECT IDENTIFIER ::=
dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 2 } { dismanEventMIBConformance 1 }
dismanEventMIBGroups OBJECT IDENTIFIER ::=
{ dismanEventMIBConformance 2 }
-- Compliance -- Compliance
dismanEventMIBCompliance MODULE-COMPLIANCE dismanEventMIBCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for entities which implement "The compliance statement for entities which implement
the Event MIB." the Event MIB."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { MANDATORY-GROUPS {
skipping to change at page 50, line 22 skipping to change at page 45, line 22
mteTriggerThresholdStartup, mteTriggerThresholdStartup,
mteTriggerThresholdObjectsOwner, mteTriggerThresholdObjectsOwner,
mteTriggerThresholdObjects, mteTriggerThresholdObjects,
mteTriggerThresholdRising, mteTriggerThresholdRising,
mteTriggerThresholdFalling, mteTriggerThresholdFalling,
mteTriggerThresholdDeltaRising, mteTriggerThresholdDeltaRising,
mteTriggerThresholdDeltaFalling, mteTriggerThresholdDeltaFalling,
mteTriggerThresholdRisingEventOwner, mteTriggerThresholdRisingEventOwner,
mteTriggerThresholdRisingEvent, mteTriggerThresholdRisingEvent,
mteTriggerThresholdFallingEventOwner, mteTriggerThresholdFallingEventOwner,
mteTriggerThresholdFallingEvent mteTriggerThresholdFallingEvent,
mteTriggerThresholdDeltaRisingEventOwner, mteTriggerThresholdDeltaRisingEventOwner,
mteTriggerThresholdDeltaRisingEvent, mteTriggerThresholdDeltaRisingEvent,
mteTriggerThresholdDeltaFallingEventOwner, mteTriggerThresholdDeltaFallingEventOwner,
mteTriggerThresholdDeltaFallingEvent mteTriggerThresholdDeltaFallingEvent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Event triggers." "Event triggers."
::= { dismanEventMIBGroups 2 } ::= { dismanEventMIBGroups 2 }
skipping to change at page 52, line 4 skipping to change at page 46, line 45
NOTIFICATIONS { NOTIFICATIONS {
mteTriggerFired, mteTriggerFired,
mteTriggerRising, mteTriggerRising,
mteTriggerFalling, mteTriggerFalling,
mteTriggerFailure, mteTriggerFailure,
mteEventSetFailure mteEventSetFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications." "Notifications."
::= { dismanEventMIBGroups 6 } ::= { dismanEventMIBGroups 6 }
END END
9. Intellectual Property 8. Intellectual Property
The IETF takes no position regarding the validity or scope of any The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain intellectual property or other rights that might be claimed to
to the implementation or use of the technology described in this pertain to the implementation or use of the technology described in
document or the extent to which any license under such rights might or this document or the extent to which any license under such rights
might not be available; neither does it represent that it has made any might or might not be available; neither does it represent that it
effort to identify any such rights. Information on the IETF's has made any effort to identify any such rights. Information on the
procedures with respect to rights in standards-track and standards- IETF's procedures with respect to rights in standards-track and
related documentation can be found in BCP-11. Copies of claims of standards- related documentation can be found in BCP-11. Copies of
rights made available for publication and any assurances of licenses to claims of rights made available for publication and any assurances of
be made available, or the result of an attempt made to obtain a general licenses to be made available, or the result of an attempt made to
license or permission for the use of such proprietary rights by obtain a general license or permission for the use of such
implementors or users of this specification can be obtained from the proprietary rights by implementors or users of this specification can
IETF Secretariat. be obtained from the IETF Secretariat.
The IETF invites any interested party to bring to its attention any The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights copyrights, patents or patent applications, or other proprietary
which may cover technology that may be required to practice this rights which may cover technology that may be required to practice
standard. Please address the information to the IETF Executive this standard. Please address the information to the IETF Executive
Director. Director.
10. Acknowledgements 9. Acknowledgements
This MIB contains considerable contributions from the RMON MIB, the This MIB contains considerable contributions from the RMON MIB, the
Distributed Management Design Team (Andy Bierman, Maria Greene, Bob Distributed Management Design Team (Andy Bierman, Maria Greene, Bob
Stewart, and Steve Waldbusser), the Distributed Management Working Stewart, and Steve Waldbusser), the Distributed Management Working
Group, and colleagues at Cisco. Group, and colleagues at Cisco.
11. References 10. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R. and B. Wijnen, "An
for Describing SNMP Management Frameworks", RFC 2571, April Architecture for Describing SNMP Management Frameworks",
1999 RFC 2571, April 1999.
[RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification [RFC1155] Rose, M. and K. McCloghrie, "Structure and Identification
of Management Information for TCP/IP-based Internets", STD of Management Information for TCP/IP-based Internets",
16, RFC 1155, May 1990 STD 16, RFC 1155, May 1990.
[RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD [RFC1212] Rose, M. and K. McCloghrie, "Concise MIB Definitions",
16, RFC 1212, March 1991 STD 16, RFC 1212, March 1991.
[RFC1215] M. Rose, "A Convention for Defining Traps for use with the [RFC1215] Rose, M., "A Convention for Defining Traps for use with
SNMP", RFC 1215, March 1991 the SNMP", RFC 1215, March 1991.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Structure of Management Rose, M. and S. Waldbusser, "Structure of Management
Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999 Information Version 2 (SMIv2)", STD 58, RFC 2578, April
1999.
[RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Textual Conventions for Rose, M. and S. Waldbusser, "Textual Conventions for
SMIv2", STD 58, RFC 2579, April 1999 SMIv2", STD 58, RFC 2579, April 1999.
[RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Rose, M., and S. Waldbusser, "Conformance Statements for Rose, M. and S. Waldbusser, "Conformance Statements for
SMIv2", STD 58, RFC 2580, April 1999 SMIv2", STD 58, RFC 2580, April 1999.
[RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple [RFC1157] Case, J., Fedor, M., Schoffstall, M. and J. Davin,
Network Management Protocol", STD 15, RFC 1157, May 1990. "Simple Network Management Protocol", STD 15, RFC 1157,
May 1990.
[RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1901] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Introduction to Community-based SNMPv2", RFC 1901, January "Introduction to Community-based SNMPv2", RFC 1901,
1996. January 1996.
[RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1906] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Transport Mappings for Version 2 of the Simple Network "Transport Mappings for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1906, January 1996. Management Protocol (SNMPv2)", RFC 1906, January 1996.
[RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [RFC2572] Case, J., Harrington D., Presuhn R. and B. Wijnen,
Processing and Dispatching for the Simple Network Management "Message Processing and Dispatching for the Simple
Protocol (SNMP)", RFC 2572, April 1999 Network Management Protocol (SNMP)", RFC 2572, April
1999.
[RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model [RFC2574] Blumenthal, U. and B. Wijnen, "User-based Security Model
(USM) for version 3 of the Simple Network Management (USM) for version 3 of the Simple Network Management
Protocol (SNMPv3)", RFC 2574, April 1999 Protocol (SNMPv3)", RFC 2574, April 1999.
[RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [RFC1905] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Protocol Operations for Version 2 of the Simple Network "Protocol Operations for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1905, January 1996. Management Protocol (SNMPv2)", RFC 1905, January 1996.
[RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", [RFC2573] Levi, D., Meyer, P. and B. Stewart, "SNMPv3
RFC 2573, April 1999 Applications", RFC 2573, April 1999.
[RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based [RFC2575] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based
Access Control Model (VACM) for the Simple Network Access Control Model (VACM) for the Simple Network
Management Protocol (SNMP)", RFC 2575, April 1999 Management Protocol (SNMP)", RFC 2575, April 1999.
[RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, [RFC2570] Case, J., Mundy, R., Partain, D. and B. Stewart,
"Introduction to Version 3 of the Internet-standard Network "Introduction to Version 3 of the Internet-standard
Management Framework", RFC 2570, April 1999 Network Management Framework", RFC 2570, April 1999.
[RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, [RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
"Coexistence between Version 1 and version 2 of the "Coexistence between Version 1 and version 2 of the
Internet-standard Network Management Framework", RFC 1903, Internet-standard Network Management Framework", RFC
January 1996. 1903, January 1996.
[RFCEventMIB] [RFC2981] Stewart, B., "Event MIB", RFC 2981, October 2000.
Stewart, B., "Event MIB", RFC ????, ?Month? 1999.
[RFC1757] [RFC1757] Waldbusser, S., "Remote Network Monitoring Management
Waldbusser, S., "Remote Network Monitoring Management Information Information Base", RFC 1757, February 1995.
Base", RFC 1757, February 1995.
[RFC1451] [RFC1451] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- "Manager-to- Manager Management Information Base", RFC
Manager Management Information Base", RFC 1451, April 1993. 1451, April 1993.
[RFCExpressionMIB] [RFC2982] Stewart, B., "Distributed Management Expression MIB", RFC
Stewart, B., "Expression MIB", RFC ????, ?Month? 1999. 2982, October 2000.
[RFCNotificationLogMIB] [LOG-MIB] Stewart, B., "Notification Log MIB", Work in Progress.
Stewart, B., "Notification Log MIB", RFC ????, ?Month? 1999.
12. Security Considerations 11. Security Considerations
Security issues are discussed in the Security section and in the Security issues are discussed in the Security section and in the
DESCRIPTION clauses of relevant objects. DESCRIPTION clauses of relevant objects.
13. Author's Address 12. Author's Address
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
U.S.A. U.S.A.
14. Editor's Address 13. Editor's Address
Ramanathan Kavasseri Ramanathan Kavasseri
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
U.S.A. U.S.A.
Phone: +1 408 527 2446 Phone: +1 408 527 2446
Email: ramk@cisco.com EMail: ramk@cisco.com
15. Full Copyright Statement 14. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it
assist in its implementation may be prepared, copied, published and or assist in its implementation may be prepared, copied, published
distributed, in whole or in part, without restriction of any kind, and distributed, in whole or in part, without restriction of any
provided that the above copyright notice and this paragraph are included kind, provided that the above copyright notice and this paragraph are
on all such copies and derivative works. However, this document itself included on all such copies and derivative works. However, this
may not be modified in any way, such as by removing the copyright notice document itself may not be modified in any way, such as by removing
or references to the Internet Society or other Internet organizations, the copyright notice or references to the Internet Society or other
except as needed for the purpose of developing Internet standards in Internet organizations, except as needed for the purpose of
which case the procedures for copyrights defined in the Internet developing Internet standards in which case the procedures for
Standards process must be followed, or as required to translate it into copyrights defined in the Internet Standards process must be
languages other than English. followed, or as required to translate it into languages other than
English.
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS This document and the information contained herein is provided on an
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
Table of Contents Acknowledgement
1 Abstract ........................................................ 2 Funding for the RFC Editor function is currently provided by the
2 The SNMP Management Framework ................................... 2 Internet Society.
3 Overview ........................................................ 4
4 Relationship to Other MIBs ...................................... 4
5 MIB Sections .................................................... 4
6 Operation ....................................................... 7
7 Security ........................................................ 8
8 Definitions ..................................................... 10
9 Intellectual Property ........................................... 53
10 Acknowledgements ............................................... 54
11 References ..................................................... 55
12 Security Considerations ........................................ 57
13 Author's Address ............................................... 57
14 Editor's Address ............................................... 57
15 Full Copyright Statement ....................................... 58
 End of changes. 123 change blocks. 
409 lines changed or deleted 387 lines changed or added

This html diff was produced by rfcdiff 1.41. The latest version is available from http://tools.ietf.org/tools/rfcdiff/