draft-ietf-disman-event-mib-06.txt   draft-ietf-disman-event-mib-07.txt 
Event MIB Event MIB
22 February 1999 25 June 1999
draft-ietf-disman-event-mib-06.txt draft-ietf-disman-event-mib-07.txt
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
bstewart@cisco.com bstewart@cisco.com
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
skipping to change at page 1, line 29 skipping to change at page 1, line 29
may also distribute working documents as Internet-Drafts. may also distribute working documents as Internet-Drafts.
Internet-Drafts are draft documents valid for a maximum of six months Internet-Drafts are draft documents valid for a maximum of six months
and may be updated, replaced, or obsoleted by other documents at any and may be updated, replaced, or obsoleted by other documents at any
time. It is inappropriate to use Internet- Drafts as reference material time. It is inappropriate to use Internet- Drafts as reference material
or to cite them other than as ``work in progress.'' or to cite them other than as ``work in progress.''
The list of current Internet-Drafts can be accessed at The list of current Internet-Drafts can be accessed at
http://www.ietf.org/ietf/1id-abstracts.txt http://www.ietf.org/ietf/1id-abstracts.txt
The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.
Distribution of this document is unlimited. Please send comments to the Distribution of this document is unlimited. Please send comments to the
Distributed Management Working Group, <disman@nexen.com>. Distributed Management Working Group, <disman@nexen.com>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
skipping to change at page 2, line 21 skipping to change at page 2, line 21
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119. document are to be interpreted as described in RFC 2119.
2. The SNMP Management Framework 2. 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 2271 [1]. 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
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version, STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC 1215 [RFC1215]. The second version, called SMIv2, is described
1904 [7]. in STD 58, RFC 2578 [RFC2578], RFC 2579 [RFC2579] and 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 RFC 1157 [8]. A second version of the SNMP message described in STD 15, RFC 1157 [RFC1157]. A second version of the
protocol, which is not an Internet standards track protocol, is SNMP message protocol, which is not an Internet standards track
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10]. protocol, is called SNMPv2c and described in RFC 1901 [RFC1901]
The third version of the message protocol is called SNMPv3 and and RFC 1906 [RFC1906]. The third version of the message
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12]. protocol is called SNMPv3 and described in RFC 1906 [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 RFC 1157 [8]. A second set of protocol operations described in STD 15, RFC 1157 [RFC1157]. A second set of
and associated PDU formats is described in RFC 1905 [13]. protocol operations and associated PDU formats is described in
RFC 1905 [RFC1905].
o A set of fundamental applications described in RFC 2273 [14] and o A set of fundamental applications described in RFC 2573
the view-based access control mechanism described in RFC 2275 [RFC2573] and the view-based access control mechanism described
[15]. in RFC 2575 [RFC2575].
Managed objects are accessed via a virtual information store, termed the A more detailed introduction to the current SNMP Management Framework
Management Information Base or MIB. Objects in the MIB are defined can be found in RFC 2570 [RFC2570].
using the mechanisms defined in the SMI. Managed objects are accessed via a virtual information store, termed
the Management Information Base or MIB. Objects in the MIB are
defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A MIB This memo specifies a MIB module that is compliant to the SMIv2. A
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. MIB.
3. Overview 3. Overview
skipping to change at page 4, line 22 skipping to change at page 4, line 22
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 local
system or on a remote system and take simple action when a trigger system or on a remote system and take simple action when a trigger
condition is met. condition is met.
The MIB is intended to suit either a relatively powerful manager or The MIB is intended to suit either a relatively powerful manager or
mid-level manager, as well as a somewhat more limited self-managing mid-level manager, as well as a somewhat more limited self-managing
system. system.
4. Relationship to Other MIBs 4. Relationship to Other MIBs
The Event MIB is based on extensive experience with the RMON MIB [16] The Event MIB is based on extensive experience with the RMON MIB
and its alarm and event groups and is intended as a replacement for [RFC1757] and its alarm and event groups and is intended as a
those groups. The Event MIB calls "triggers" what the RMON MIB called replacement for those groups. 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 of
MIB events maintain the RMON concept of sending an SNMP notification in booleans. Event MIB events maintain the RMON concept of sending an SNMP
response to a trigger and add the concept of setting a MIB object. 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-Manager
MIB [17] which was declared Historic pending this work. 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 [14]. 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 [18], which is the expected source of boolean objects to Expression MIB [RFCExpressionMIB], which is the expected source of
monitor. Note that there is considerable overlap between the wildcard boolean objects to monitor. Note that there is considerable overlap
and delta sample capabilities of the Event and Expression MIBs. A between the wildcard and delta sample capabilities of the Event and
carefully-planned implementation might well use common code to provide Expression MIBs. A carefully-planned implementation might well use
the overlapping functions. common code to provide the overlapping functions.
5. MIB Sections 5. MIB Sections
The MIB has four sections: triggers, objects, events, and notifications. The MIB has four sections: triggers, objects, events, and notifications.
Triggers define the conditions that lead to events. Events may cause Triggers define the conditions that lead to events. Events may cause
notifications. 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 for
the trigger. 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 based
on the trigger, the trigger test type, or the event that resulted in the on the trigger, the trigger test type, or the event that resulted in the
notification. notification.
skipping to change at page 5, line 17 skipping to change at page 5, line 19
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 for
the trigger. 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 based
on the trigger, the trigger test type, or the event that resulted in the on the trigger, the trigger test type, or the event that resulted in the
notification. notification.
The event table defines what happens when an event is triggered, sending The event table defines what happens when an event is triggered, sending
a notification, setting a MIB object or both. It has supplementary, a notification, setting a MIB object or both. It has supplementary,
companion tables for additional objects that depend on the action taken. companion tables for additional objects that depend on the action taken.
82 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 set
of objects to put in those notifications. of objects to put in those notifications.
6. Operation 6. 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 and
skipping to change at page 5, line 48 skipping to change at page 6, line 4
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 object. trigger an event and result in the setting of another wildcarded object.
The instance that satisfied the trigger function is used to perform the The instance that satisfied the trigger function is used to perform the
set function. All of this takes place independently of any additional set function. All of this takes place independently of any additional
instances that may fill the wildcard. instances that may fill the wildcard.
Error handling is by notification, which at first thought violates the Error handling is by notification, which at first thought violates the
principle that notifications may be lost or become a crippling burden, principle that notifications may be lost or become a crippling burden,
but the intent is that such error notifications be enabled only for the but the intent is that such error notifications be enabled only for the
diagnosis of problems indicated by error counters and if the diagnosis of problems indicated by error counters and if the
notifications are being lost they be directed to the log as described in notifications are being lost they be directed to the log as described in
the Notification Log MIB [19]. Note that this does not mean the the Notification Log MIB [rfcNotificationLogMIB]. Note that this does
Notification Log MIB is required, since in fact notifications usually not mean the Notification Log MIB is required, since in fact
are not lost, but that the Notification Log MIB can be helpful with this notifications usually are not lost, but that the Notification Log MIB
as well as 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
persistance of the values set in configuring events, a robust, polite
implementation would certainly not force its managing applications to
reconfigure it whenever it resets.
Again, as with most MIBs, it is implementation specific how a system
provides and manages such persistance. To speculate, one could imagine,
for example, that persistance depended on the context in which the
expression was configured, or perhaps system-specific characteristics of
the expression's owner. Or perhaps everything in a MIB such as this
one, which is clearly aimed at persistant configuration, is
automatically part of a system's other persistant configuration.
7. Security 7. Security
Security of Event MIB entries depends on SNMPv3 access control for the Security of Event MIB entries depends on SNMPv3 access control for the
entire MIB or for subsets based on substrings of trigger and event entire MIB or for subsets based on entry owner names.
names.
Security of monitored objects for remote access depends on the Security of monitored objects for remote access depends on the
Management Target MIB. Security for local access can depend on the Management Target MIB. Security for local access can depend on the
Management Target MIB or on recording appropriate security credentials Management Target MIB or on recording appropriate security credentials
of the creator of an entry and using those to access the local objects. of the creator of an entry and using those to access the local objects.
These security credentials are the parameters necessary as inputs to These security credentials are the parameters necessary as inputs to
isAccessAllowed from the Architecture for Describing SNMP Management isAccessAllowed from the Architecture for Describing SNMP Management
Frameworks. When accessing local objects without using a local target Frameworks. When accessing local objects without using a local target
tag, the system must (conceptually) use isAccessAllowed to ensure that tag, the system must (conceptually) use isAccessAllowed to ensure that
it does not violate security. 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 [15] for tables in which multiple users Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple
may need to independently create or modify entries, the initial index is
used as an "owner index". Such an initial index has a syntax of users may need to independently create or modify entries, the initial
index is used as an "owner index". Such an initial index has a syntax of
SnmpAdminString, and can thus be trivially mapped to a securityName or SnmpAdminString, and can thus be trivially mapped to a securityName or
groupName as defined in VACM, in accordance with a security policy. groupName as defined in VACM, in accordance with a security policy.
All entries in related tables belonging to a particular user will have All entries in related tables belonging to a particular user will have
the same value for this initial index. For a given user's entries in a the same value for this initial index. For a given user's entries in a
particular table, the object identifiers for the information in these particular table, the object identifiers for the information in these
entries will have the same subidentifiers (except for the "column" entries will have the same subidentifiers (except for the "column"
subidentifier) up to the end of the encoded owner index. To configure subidentifier) up to the end of the encoded owner index. To configure
VACM to permit access to this portion of the table, one would create VACM to permit access to this portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilyTable entries with the value of
skipping to change at page 7, line 23 skipping to change at page 8, line 23
Gauge32 FROM SNMPv2-SMI Gauge32 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 "9902221700Z" LAST-UPDATED "9906241700Z"
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Bob Stewart CONTACT-INFO "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.
Phone: +1 408 526 4527 Phone: +1 408 526 4527
Email: bstewart@cisco.com" Email: bstewart@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."
skipping to change at page 9, line 22 skipping to change at page 10, line 22
commitFailed(14), commitFailed(14),
undoFailed(15), undoFailed(15),
authorizationError(16), authorizationError(16),
notWritable(17), notWritable(17),
inconsistentName(18) } inconsistentName(18) }
-- --
-- Resource Control Section -- Resource Control Section
-- --
mteResourceSampleMinimum OBJECT-TYPE mteResourceSampleMinimum OBJECT-TYPE
SYNTAX Integer32 (-1 | 1..600) SYNTAX Integer32 (1..600)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The minimum mteTriggerFrequency this system will
"The minimum mteTriggerFrequency this system will accept. A accept. A system may use the larger values of this minimum to
system may use the larger values of this minimum to lessen the lessen the impact of constant sampling. For larger
impact of sampling. sampling intervals the system samples less often and
suffers less overhead. This object provides a way to enforce
such lower overhead for all triggers created after it is
set.
Unless explicitly resource limited, a system's value for Unless explicitly resource limited, a system's value for
this object should be 1. this object should be 1, allowing as small as a 1 second
interval for ongoing trigger sampling.
Changing this value will not invalidate an existing setting Changing this value will not invalidate an existing setting
of mteTriggerFrequency." of mteTriggerFrequency."
::= { mteResource 1 } ::= { mteResource 1 }
mteResourceSampleInstanceMaximum OBJECT-TYPE mteResourceSampleInstanceMaximum OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
UNITS "instances" UNITS "instances"
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
skipping to change at page 13, line 8 skipping to change at page 14, line 13
::= { mteTriggerEntry 3 } ::= { mteTriggerEntry 3 }
mteTriggerTest OBJECT-TYPE mteTriggerTest OBJECT-TYPE
SYNTAX BITS { existence(0), boolean(1), threshold(2) } SYNTAX BITS { existence(0), boolean(1), threshold(2) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of trigger test to perform. For 'boolean' and "The type of trigger test to perform. For 'boolean' and
'threshold' tests, the object at mteTriggerValueID must 'threshold' tests, the object at mteTriggerValueID must
evaluate to an integer, that is, anything that ends up encoded evaluate to an integer, that is, anything that ends up encoded
for transmission as an integer. for transmission (that is, in BER, not ASN.1) as an integer.
For 'existence', the specific test is as selected by For 'existence', the specific test is as selected by
mteTriggerExistenceTest. When an object appears or vanishes mteTriggerExistenceTest. When an object appears or vanishes
the trigger fires. The trigger will not fire again until the the trigger fires. The trigger will not fire again until the
object has changed states. object has changed states.
For 'boolean', the specific test is as selected by For 'boolean', the specific test is as selected by
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.
skipping to change at page 19, line 5 skipping to change at page 20, line 8
mteTriggerDeltaDiscontinuityIDType INTEGER mteTriggerDeltaDiscontinuityIDType INTEGER
} }
sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 } sysUpTimeInstance OBJECT IDENTIFIER ::= { sysUpTime 0 }
mteTriggerDeltaDiscontinuityID OBJECT-TYPE mteTriggerDeltaDiscontinuityID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The OBJECT IDENTIFIER (OID) of a TimeTicks or TimeStamp object "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or
that indicates a discontinuity in the value at DateAndTime object that indicates a discontinuity in the value
mteTriggerValueID. at mteTriggerValueID.
The OID may be for a leaf object (e.g. sysUpTime.0) or may The OID may be for a leaf object (e.g. sysUpTime.0) or may
be wildcarded to match mteTriggerValueID. be wildcarded to match mteTriggerValueID.
This object supports normal checking for a discontinuity in a This object supports normal checking for a discontinuity in a
counter. Note that if this object does not point to sysUpTime counter. Note that if this object does not point to sysUpTime
discontinuity checking must still check sysUpTime for an overall discontinuity checking must still check sysUpTime for an overall
discontinuity. discontinuity.
If the object identified is not accessible the sample attempt If the object identified is not accessible the sample attempt
skipping to change at page 29, line 37 skipping to change at page 30, line 41
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 }
mteObjectsEntry OBJECT-TYPE mteObjectsEntry OBJECT-TYPE
SYNTAX MteObjectsEntry SYNTAX MteObjectsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A group of objects. Applications create and delete entries "A group of objects. Applications create and delete entries
using mteObjectsEntryStatus." using mteObjectsEntryStatus.
INDEX { mteOwner, mteObjectsName, mteObjecsIndex }
When adding objects to a notification they are added in the
lexical order of their index in this table. Those associated
with a trigger come first, then trigger test, then event."
INDEX { mteOwner, mteObjectsName, mteObjectsIndex }
::= { mteObjectsTable 1 } ::= { mteObjectsTable 1 }
MteObjectsEntry ::= SEQUENCE { MteObjectsEntry ::= SEQUENCE {
mteObjectsName SnmpAdminString, mteObjectsName SnmpAdminString,
mteObjectsIndex Unsigned32, mteObjectsIndex Unsigned32,
mteObjectsID OBJECT IDENTIFIER, mteObjectsID OBJECT IDENTIFIER,
mteObjectsIDWildcard TruthValue, mteObjectsIDWildcard TruthValue,
mteObjectsEntryStatus RowStatus mteObjectsEntryStatus RowStatus
} }
skipping to change at page 33, line 24 skipping to change at page 34, line 31
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 } } 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 40, line 28 skipping to change at page 41, line 34
mteTriggerFired NOTIFICATION-TYPE mteTriggerFired NOTIFICATION-TYPE
OBJECTS { mteHotTrigger, OBJECTS { mteHotTrigger,
mteHotTargetName, mteHotTargetName,
mteHotContextName, mteHotContextName,
mteHotOID, mteHotOID,
mteHotValue } mteHotValue }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification that the trigger indicated by the object "Notification that the trigger indicated by the object
instances has fired, for triggers with mteTriggerType instances has fired, for triggers with mteTriggerType
'boolean'." 'boolean' or 'existence'."
::= { dismanEventMIBNotifications 1 } ::= { dismanEventMIBNotifications 1 }
mteTriggerRising NOTIFICATION-TYPE mteTriggerRising NOTIFICATION-TYPE
OBJECTS { mteHotTrigger, OBJECTS { mteHotTrigger,
mteHotTargetName, mteHotTargetName,
mteHotContextName, mteHotContextName,
mteHotOID, mteHotOID,
mteHotValue } mteHotValue }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 42, line 6 skipping to change at page 43, line 11
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 ::= { dismanEventMIBConformance
dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 2 } 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 46, line 7 skipping to change at page 47, line 14
mteHotOID, mteHotOID,
mteHotValue, mteHotValue,
mteFailedReason mteFailedReason
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification objects." "Notification objects."
::= { dismanEventMIBGroups 5 } ::= { dismanEventMIBGroups 5 }
dismanEventNotificationGroup NOTIFICATION-GROUP dismanEventNotificationGroup NOTIFICATION-GROUP
OBJECTS { NOTIFICATIONS {
mteTriggerFired, mteTriggerFired,
mteTriggerRising, mteTriggerRising,
mteTriggerFalling, mteTriggerFalling,
mteTriggerFailure, mteTriggerFailure,
mteEventSetFailure mteEventSetFailure
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications." "Notifications."
::= { dismanEventMIBGroups 6 } ::= { dismanEventMIBGroups 6 }
skipping to change at page 49, line 7 skipping to change at page 50, line 7
10. Acknowledgements 10. 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 11. References
[1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
Describing SNMP Management Frameworks", RFC 2271, Cabletron for Describing SNMP Management Frameworks", RFC 2571, April
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, 1999
January 1998.
[2] Rose, M. and K. McCloghrie, "Structure and Identification of [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification
Management Information for TCP/IP-based Internets", RFC 1155, of Management Information for TCP/IP-based Internets", STD
Performance Systems International, Hughes LAN Systems, May 1990. 16, RFC 1155, May 1990
[3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", STD
Performance Systems International, Hughes LAN Systems, March 1991. 16, RFC 1212, March 1991
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [RFC1215] M. Rose, "A Convention for Defining Traps for use with the
RFC 1215, Performance Systems International, March 1991. SNMP", RFC 1215, March 1991
[5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Management Information for Version 2 of the Simple Network Rose, M., and S. Waldbusser, "Structure of Management
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1999
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Conventions for Version 2 of the Simple Network Management Protocol Rose, M., and S. Waldbusser, "Textual Conventions for
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., SMIv2", STD 58, RFC 2579, April 1999
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J.,
Statements for Version 2 of the Simple Network Management Protocol Rose, M., and S. Waldbusser, "Conformance Statements for
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., SMIv2", STD 58, RFC 2580, April 1999
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple
Management Protocol", RFC 1157, SNMP Research, Performance Systems Network Management Protocol", STD 15, RFC 1157, May 1990.
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco "Introduction to Community-based SNMPv2", RFC 1901, January
Systems, Inc., Dover Beach Consulting, Inc., International Network 1996.
Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Mappings for Version 2 of the Simple Network Management Protocol "Transport Mappings for Version 2 of the Simple Network
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1906, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, Protocol (SNMP)", RFC 2572, April 1999
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC (USM) for version 3 of the Simple Network Management
2274, IBM T. J. Watson Research, January 1998. Protocol (SNMPv3)", RFC 2574, April 1999
[13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
Operations for Version 2 of the Simple Network Management Protocol "Protocol Operations for Version 2 of the Simple Network
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., Management Protocol (SNMPv2)", RFC 1905, January 1996.
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications",
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco RFC 2573, April 1999
Systems, January 1998.
[15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based
Control Model (VACM) for the Simple Network Management Protocol Access Control Model (VACM) for the Simple Network
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., Management Protocol (SNMP)", RFC 2575, April 1999
Cisco Systems, Inc., January 1998.
[16] Waldbusser, S., "Remote Network Monitoring Management Information [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart,
Base", RFC 1757, International Network Services, February 1995. "Introduction to Version 3 of the Internet-standard Network
Management Framework", RFC 2570, April 1999
[17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- [RFC1903] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser,
Manager Management Information Base", RFC 1451, SNMP Research, "Coexistence between Version 1 and version 2 of the
Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc., Internet-standard Network Management Framework", RFC 1903,
International Network Services, April 1993. January 1996.
[18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc., [RFCEventMIB]
?Month? 1998. Stewart, B., "Event MIB", RFC ????, ?Month? 1999.
[19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc., [RFC1757]
?Month? 1998. Waldbusser, S., "Remote Network Monitoring Management Information
Base", RFC 1757, February 1995.
[RFC1451]
Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to-
Manager Management Information Base", RFC 1451, April 1993.
[RFCExpressionMIB]
Stewart, B., "Expression MIB", RFC ????, ?Month? 1999.
[RFCNotificationLogMIB]
Stewart, B., "Notification Log MIB", RFC ????, ?Month? 1999.
12. Security Considerations 12. Security Considerations
Security issues are discussed in the Overview 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 13. 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.
skipping to change at page 53, line 14 skipping to change at page 54, line 14
Table of Contents Table of Contents
1 Abstract ........................................................ 2 1 Abstract ........................................................ 2
2 The SNMP Management Framework ................................... 2 2 The SNMP Management Framework ................................... 2
3 Overview ........................................................ 4 3 Overview ........................................................ 4
4 Relationship to Other MIBs ...................................... 4 4 Relationship to Other MIBs ...................................... 4
5 MIB Sections .................................................... 4 5 MIB Sections .................................................... 4
6 Operation ....................................................... 5 6 Operation ....................................................... 5
7 Security ........................................................ 6 7 Security ........................................................ 6
8 Definitions ..................................................... 7 8 Definitions ..................................................... 8
9 Intellectual Property ........................................... 47 9 Intellectual Property ........................................... 48
10 Acknowledgements ............................................... 48 10 Acknowledgements ............................................... 49
11 References ..................................................... 49 11 References ..................................................... 50
12 Security Considerations ........................................ 51 12 Security Considerations ........................................ 52
13 Author's Address ............................................... 51 13 Author's Address ............................................... 52
14 Full Copyright Statement ....................................... 52 14 Full Copyright Statement ....................................... 53
 End of changes. 

This html diff was produced by rfcdiff 1.23, available from http://www.levkowetz.com/ietf/tools/rfcdiff/