draft-ietf-disman-event-mib-03.txt   draft-ietf-disman-event-mib-04.txt 
Event MIB Event MIB
13 March 1998 5 August 1998
draft-ietf-disman-event-mib-03.txt draft-ietf-disman-event-mib-04.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. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
documents as Internet-Drafts. 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.''
To learn the current status of any Internet-Draft, please check the To view the entire list of current Internet-Drafts, please check the
``1id-abstracts.txt'' listing contained in the Internet- Drafts Shadow "1id-abstracts.txt" listing contained in the Internet-Drafts Shadow
Directories on ds.internic.net (US East Coast), nic.nordu.net (Europe), Directories on ftp.is.co.za (Africa), ftp.nordu.net (Northern Europe),
ftp.isi.edu (US West Coast), or munnari.oz.au (Pacific Rim). ftp.nis.garr.it (Southern Europe), munnari.oz.au (Pacific Rim),
ftp.ietf.org (US East Coast), or ftp.isi.edu (US West Coast).
Distribution of this document is unlimited. Please send comments to the
Distributed Management Working Group, <disman@nexen.com>.
Copyright Notice
Copyright (C) The Internet Society (1998). 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
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing monitoring of MIB objects and taking action through events. managing monitoring of MIB objects and taking action through events.
2. The SNMP Network Management Framework 2. The SNMP Management Framework
{The following boilerplate is out of date. It will be replaced when
SNMPv3 boilerplate is available.}
The SNMP Network Management Framework presently consists of three major The SNMP Management Framework presently consists of five major
components. They are: components:
the SMI, described in RFC 1902 [1] - the mechanisms used for o An overall architecture, described in RFC 2271 [1].
describing and naming objects for the purpose of management.
the MIB-II, STD 17, RFC 1213 [2] - the core set of managed objects for o Mechanisms for describing and naming objects and events for the
the Internet suite of protocols. purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in
RFC 1155 [2], RFC 1212 [3] and RFC 1215 [4]. The second version,
called SMIv2, is described in RFC 1902 [5], RFC 1903 [6] and RFC
1904 [7].
the protocol, RFC 1157 [3] and/or RFC 1905 [4], - the protocol for o Message protocols for transferring management information. The
accessing managed objects. first version of the SNMP message protocol is called SNMPv1 and
described in RFC 1157 [8]. A second version of the SNMP message
protocol, which is not an Internet standards track protocol, is
called SNMPv2c and described in RFC 1901 [9] and RFC 1906 [10].
The third version of the message protocol is called SNMPv3 and
described in RFC 1906 [10], RFC 2272 [11] and RFC 2274 [12].
The Framework permits new objects to be defined for the purpose of o Protocol operations for accessing management information. The
experimentation and evaluation. first set of protocol operations and associated PDU formats is
described in RFC 1157 [8]. A second set of protocol operations
and associated PDU formats is described in RFC 1905 [13].
2.1. Object Definitions o A set of fundamental applications described in RFC 2273 [14] and
the view-based access control mechanism described in RFC 2275
[15].
Managed objects are accessed via a virtual information store, termed the Managed objects are accessed via a virtual information store, termed the
Management Information Base or MIB. Objects in the MIB are defined Management Information Base or MIB. Objects in the MIB are defined
using the subset of Abstract Syntax Notation One (ASN.1) defined in the using the mechanisms defined in the SMI.
SMI. In particular, each object type is named by an OBJECT IDENTIFIER,
an administratively assigned name. The object type together with an
object instance serves to uniquely identify a specific instantiation of
the object. For human convenience, we often use a textual string,
termed the descriptor, to refer to the object type.
3. Overview This memo specifies a MIB module that is compliant to the SMIv2. A MIB
conforming to the SMIv1 can be produced through the appropriate
This MIB is based heavily on the RMON and Manager-to-Manager MIBs. It translations. The resulting translated MIB must be semantically
depends on the services of the SNMPv3 Management Target and Notification equivalent, except where objects or events are omitted because no
MIBs and is nicely complemented by the Distributed Management Expression translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the
MIB. MIB.
3. Overview
With network sizes well beyond the ability of people to management their
networks directly automated, distributed management is vital. An
important aspect of such management is the ability of a system to
monitor itself or for some other system to monitor it.
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.
All of these components must suit either a relatively powerful manager All of these components must suit either a relatively powerful manager
or mid-level manager, as well as a somewhat more limited self-managing or mid-level manager, as well as a somewhat more limited self-managing
system. system.
4. Known Problems 4. Relationship to Other MIBs
The compliance section is missing. The Event MIB is based on extensive experience with the RMON MIB [16]
and its alarm and event groups and is intended as a replacement for
those groups. The Event MIB calls "triggers" what the RMON MIB called
"alarms," but the concepts are the same. Event MIB triggers maintain
the RMON handling of thresholds and add the concept of booleans. Event
MIB events maintain the RMON concept of sending an SNMP notification in
response to a trigger and add the concept of setting a MIB object.
5. Definitions The Event MIB is the successor and update to SNMPv2's Manager-to-Manager
MIB [17] which was declared Historic pending this work.
The Event MIB depends on the services of the SNMPv3 Management Target
and Notification MIBs [14].
The Event MIB is nicely complemented by the Distributed Management
Expression MIB [18], which is the expected source of boolean objects to
monitor.
5. MIB Sections
The MIB has three sections, triggers, events, and notifications.
Triggers define the conditions that lead to events. Events may cause
notifications.
The trigger table lists what objects are to be monitored and how and
relates each trigger to an event. In the same section the trigger
object table lists trigger-related objects that can be added to
notifications either for a trigger or for an event.
The event table defines what happens when an event is triggered, sending
a notificaiton, setting a MIB object or both.
The notification section defines a set of generic notifications to go
with the events and for Event MIB error handlling, and it defines a set
of objects to put in those notifications.
6. Operation
The Event MIB is instrumentation for a distributed management
application that monitors MIB objects. In its simplest form this
application monitors individual, local MIB objects, just as an RMON
probe fulfills the functions implied by RMON's alarm and event
operation. Additionally the application can monitor remote objects and
wildcarded groups of objects.
Remote monitoring uses the tag service of the Management Target MIB to
select and access remote systems as an ordinary SNMP-based management
application. Local monitoring may be be a more intimate, local
interface which may, for example, bypass SNMP formatting but otherwise
is functionally identical to remote SNMP operation. A self-management
only system may not implemenet remote monitoring.
Wildcards indicate that the application should use a GetNext-type
operation to find the zero or more instances implied by a truncated
object identifier, just like an ordinary SNMP-based management
application.
Error handling is by notification, which at first thought violates the
principle that notifications may be lost or become a crippling burden,
but the intent is that such error notifications be enabled only for the
diagnosis of problems indicated by error counters and if the
notifications are being lost they be directed to the log as described in
the Notification Log MIB [19].
7. Security
Security of Event MIB entries depends on SNMPv3 access control for the
entire MIB or for subsets based on substrings of trigger and event
names.
Security of monitored objects for remote access depends on the
Management Target MIB. Security for local access can depend on the
Management Target MIB or on recording appropriate security credentials
of the creator of an entry and using those to access the local objects.
8. Definitions
EVENT-MIB DEFINITIONS ::= BEGIN EVENT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
experimental, Integer32, Unsigned32 experimental, Integer32, Unsigned32
NOTIFICATION-TYPE FROM SNMPv2-SMI NOTIFICATION-TYPE FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TimeStamp, DisplayString FROM SNMPv2-TC TimeStamp, DisplayString FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
SnmpTagValue FROM SNMP-TARGET-MIB SnmpTagValue FROM SNMP-TARGET-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
eventMIB MODULE-IDENTITY eventMIB MODULE-IDENTITY
LAST-UPDATED "9803131700Z" LAST-UPDATED "9808051700Z"
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 5, line 45 skipping to change at page 7, line 45
mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 }
mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
FailureReason ::= TEXTUAL-CONVENTION FailureReason ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reasons for failures in an attempt to send a "Reasons for failures in an attempt to send a management message.
management message."
SYNTAX INTEGER { localResourceLack(1), badDestination(2), The first group of errors, numbered less than 100, are copied
tooBig(3), badAccessControl(4), directly from SNMP protocol operations and are intended to carry
noAck(5) } exactly the meanings defined for the protocol as returned in
an SNMP response. Those numbered 100 or greater are related
to problems in sending the request."
SYNTAX INTEGER { tooBig(1),
noSuchName(2),
badValue(3),
readOnly(4),
genErr(5),
noAccess(6),
wrongType(7),
wrongLength(8),
wrongEncoding(9),
wrongValue(10),
noCreation(11),
inconsistentValue(12),
resourceUnavailable(13),
commitFailed(14),
undoFailed(15),
authorizationError(16),
notWritable(17),
inconsistentName(18),
localResourceLack(101),
badDestination(102),
noAck(103) }
-- --
-- Trigger Section -- Trigger Section
-- --
-- Counters
mteTriggerFailures OBJECT-TYPE mteTriggerFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times an attempt to check for a trigger "The number of times an attempt to check for a trigger
condition has failed. This counts individually for each condition has failed. This counts individually for each
attempt in a group of targets or each attempt for a attempt in a group of targets or each attempt for a
wildcarded object." wildcarded object."
::= { mteTrigger 1 } ::= { mteTrigger 1 }
mteTriggerLastFailedTrigger OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The trigger that last failed an attempt to check for a
trigger condition."
::= { mteTrigger 2 }
mteTriggerLastFailedReason OBJECT-TYPE
SYNTAX FailureReason
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The reason for the last failure of an attempt to check
for a trigger condition."
::= { mteTrigger 3 }
mteTriggerLastFailedTargetTag OBJECT-TYPE
SYNTAX SnmpTagValue
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The mteTriggerTargetTag of the last failed attempt to check a
trigger condition. The length 0 means this does not apply."
::= { mteTrigger 4 }
mteTriggerLastFailedTargetName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The target name of the last failed attempt to check a
trigger condition. The length 0 means this does not apply"
::= { mteTrigger 5 }
mteTriggerLastValueID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only
STATUS current
DESCRIPTION
"The object identifier from mteTriggerValueID from the last
attempt to check a trigger condition. This must
be as full-qualified as possible, including filling in
wild-card information determined in processing."
::= { mteTrigger 6 }
mteTriggerLastValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS notification-only
STATUS current
DESCRIPTION
"The value of the object at mteTriggerValueID when a
trigger fires."
::= { mteTrigger 7 }
mteTriggerTargetName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS notification-only
STATUS current
DESCRIPTION
"The target name for which the trigger fired or for which a
check was attempted."
::= { mteTrigger 8 }
-- --
-- Trigger Table -- Trigger Table
-- --
mteTriggerTable OBJECT-TYPE mteTriggerTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteTriggerEntry SYNTAX SEQUENCE OF MteTriggerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of management event trigger information." "A table of management event trigger information."
::= { mteTrigger 9 } ::= { mteTrigger 2 }
mteTriggerEntry OBJECT-TYPE mteTriggerEntry OBJECT-TYPE
SYNTAX MteTriggerEntry SYNTAX MteTriggerEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
"Information about a single trigger, created using mteTriggerStatus." "Information about a single trigger. Applications create and
delete entries using mteTriggerStatus."
INDEX { IMPLIED mteTriggerName } INDEX { IMPLIED mteTriggerName }
::= { mteTriggerteble 1 } ::= { mteTriggerteble 1 }
MteTriggerEntry ::= SEQUENCE { MteTriggerEntry ::= SEQUENCE {
mteTriggerName SnmpAdminString, mteTriggerName SnmpAdminString,
mteTriggerComment DisplayString, mteTriggerComment DisplayString,
mteTriggerTest INTEGER, mteTriggerTest INTEGER,
mteTriggerValueID Integer32, mteTriggerValueID Integer32,
mteTriggerValueIDWildcard TruthValue, mteTriggerValueIDWildcard TruthValue,
mteTriggerFrequency Integer32,
mteTriggerTargetTag SnmpTagValue, mteTriggerTargetTag SnmpTagValue,
mteTriggerContextName SnmpAdminString,
mteTriggerContextNameWildcard TruthValue,
mteTriggerFrequency Integer32,
mteTriggerBooleanStartup INTEGER,
mteTriggerThresholdStartup INTEGER,
mteTriggerRisingThreshold Integer32, mteTriggerRisingThreshold Integer32,
mteTriggerFallingThreshold Integer32, mteTriggerFallingThreshold Integer32,
mteTriggerEvent SnmpAdminString, mteTriggerEvent SnmpAdminString,
mteTriggerRisingEvent SnmpAdminString, mteTriggerRisingEvent SnmpAdminString,
mteTriggerFallingEvent SnmpAdminString, mteTriggerFallingEvent SnmpAdminString,
mteTriggerObjects SnmpAdminString,
mteTriggerStatus RowStatus mteTriggerStatus RowStatus
} }
mteTriggerName OBJECT-TYPE mteTriggerName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..64)) SYNTAX SnmpAdminString (SIZE (1..64))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for the trigger." "A locally-unique, administratively assigned name for the trigger."
::= { mteTriggerEntry 1 } ::= { mteTriggerEntry 1 }
skipping to change at page 9, line 44 skipping to change at page 11, line 13
mteTriggerIDWildcard must be 'true' and if not it must mteTriggerIDWildcard must be 'true' and if not it must
be 'false'." be 'false'."
DEFVAL { 0 0 } DEFVAL { 0 0 }
::= { mteTriggerEntry 4 } ::= { mteTriggerEntry 4 }
mteTriggerValueIDWildcard OBJECT-TYPE mteTriggerValueIDWildcard OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Control over which mteTriggerValueID is to be treated as "Control for whether mteTriggerValueID is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard. fully-specified or wildcarded, with 'true' indicating wildcard.
DEFVAL { false } DEFVAL { false }
::= { mteTriggerEntry 5 } ::= { mteTriggerEntry 5 }
mteTriggerTargetTag OBJECT-TYPE
SYNTAX SnmpTagValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The tag for the target(s) from which to obtain the condition
for a trigger check.
Systems limited to self management may not accept a non-zero
length for the value of this object.
A length of 0 indicates the local system. In this case,
access to the objects indicated by mteTriggerValueID is under
the security credentials of the requester that set
mteTriggerStatus to 'active'."
DEFVAL { ''H }
::= { mteTriggerEntry 6 }
mteTriggerContextName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The management context from which to obtain mteTriggerValueID.
This may be wildcarded by leaving characters off the end. To
indicate such wildcarding mteTriggerContextNameWildcard must
be 'true'."
DEFVAL { ''H }
::= { mteTriggerEntry 7 }
mteTriggerContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteTriggerContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard.
DEFVAL { false }
::= { mteTriggerEntry 8 }
mteTriggerFrequency OBJECT-TYPE mteTriggerFrequency OBJECT-TYPE
SYNTAX Integer32 (0..65535) SYNTAX Integer32 (0..65535)
UNITS "seconds" UNITS "seconds"
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of seconds to wait between trigger condition "The number of seconds to wait between trigger condition
checks. To encourage consistency in sampling, the checks. To encourage consistency in sampling, the
interval is measured from the beginning of one check to interval is measured from the beginning of one check to
the beginning of the next and the timer is restarted immediately the beginning of the next and the timer is restarted immediately
skipping to change at page 10, line 26 skipping to change at page 12, line 36
If the next check begins before the previous one completed the If the next check begins before the previous one completed the
system may either attempt to make the check or treat this as an system may either attempt to make the check or treat this as an
error condition. error condition.
A frequency of 0 indicates instantaneous recognition of the A frequency of 0 indicates instantaneous recognition of the
condition. This is not possible in many cases, but such may condition. This is not possible in many cases, but such may
be supported in cases where it makes sense and the system is be supported in cases where it makes sense and the system is
able to do so." able to do so."
DEFVAL { 600 } DEFVAL { 600 }
::= { mteTriggerEntry 6 } ::= { mteTriggerEntry 9 }
mteTriggerTargetTag OBJECT-TYPE
SYNTAX SnmpTagValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The tag for the target(s) from which to obtain the condition
for a trigger check.
A length of 0 indicates the local system."
DEFVAL { ''H }
::= { mteTriggerEntry 7 }
mteTriggerBooleanStartup OBJECT-TYPE mteTriggerBooleanStartup OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Control for whether an event may be triggered when this entry "Control for whether an event may be triggered when this entry
is first set to 'active'. If the value mteTriggerBooleanStartup is first set to 'active'. If the value mteTriggerBooleanStartup
is 'true' and the first sample after this entry becomes active is is 'true' and the first sample after this entry becomes active is
true then one mteTriggerEvent is triggered. true then one mteTriggerEvent is triggered.
If mteTriggerType is not 'boolean', this object is not If mteTriggerType is not 'boolean', this object is not
instantiated." instantiated."
DEFVAL { true } DEFVAL { true }
::= { mteTriggerEntry 6 } ::= { mteTriggerEntry 10 }
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-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The event that may be triggered when this entry is first "The event that may be triggered when this entry is first
set to 'active'. If the first sample after this entry set to 'active'. If the first sample after this entry
becomes active is greater than or equal to becomes active is greater than or equal to
mteTriggerRisingThreshold and mteTriggerThresholdStartup is mteTriggerRisingThreshold and mteTriggerThresholdStartup is
equal to 'rising' or 'risingOrFalling', then one equal to 'rising' or 'risingOrFalling', then one
mteTriggerRisingEvent is triggered. If the first mteTriggerRisingEvent is triggered. If the first
sample after this entry becomes active is less than sample after this entry becomes active is less than
or equal to mteTriggerFallingThreshold and or equal to mteTriggerFallingThreshold and
mteTriggerThresholdStartup is equal to 'falling' or mteTriggerThresholdStartup is equal to 'falling' or
'risingOrFalling', then one mteTriggerRisingEvent is triggered. 'risingOrFalling', then one mteTriggerRisingEvent is triggered.
If mteTriggerType is not 'threshold', this object is not If mteTriggerType is not 'threshold', this object is not
instantiated." instantiated."
DEFVAL { risingOrFalling } DEFVAL { risingOrFalling }
::= { mteTriggerEntry 6 } ::= { mteTriggerEntry 11 }
mteTriggerRisingThreshold OBJECT-TYPE mteTriggerRisingThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
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 greater than or equal to When the current sampled value is greater than or equal to
skipping to change at page 12, line 8 skipping to change at page 14, line 6
threshold and mteTriggerThresholdStartup is equal to 'rising' threshold and mteTriggerThresholdStartup is equal to 'rising'
or 'risingOrFalling'. or 'risingOrFalling'.
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 sampled value falls below this threshold and triggered until the sampled value falls below this threshold and
reaches mteTriggerFallingThreshold. reaches mteTriggerFallingThreshold.
If mteTriggerType is not 'threshold', this object is not If mteTriggerType is not 'threshold', this object is not
instantiated." instantiated."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerEntry 8 } ::= { mteTriggerEntry 12 }
mteTriggerFallingThreshold OBJECT-TYPE mteTriggerFallingThreshold OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
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 When the current sampled value is less than or equal to
skipping to change at page 12, line 33 skipping to change at page 14, line 31
threshold and mteTriggerThresholdStartup is equal to 'falling' threshold and mteTriggerThresholdStartup is equal to 'falling'
or 'risingOrFalling'. or '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 and triggered until the sampled value rises above this threshold and
reaches mteTriggerRisingThreshold. reaches mteTriggerRisingThreshold.
If mteTriggerType is not 'threshold', this object is not If mteTriggerType is not 'threshold', this object is not
instantiated." instantiated."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerEntry 9 } ::= { mteTriggerEntry 13 }
mteTriggerEvent OBJECT-TYPE mteTriggerEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..64)) SYNTAX SnmpAdminString (SIZE (0..64))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The event to invoke when mteTriggerType is 'boolean' and "The event to invoke when mteTriggerType is 'boolean' and
this trigger fires. A length of 0 indicates no event. this trigger fires. A length of 0 indicates no event.
If mteTriggerType is not 'boolean', this object is not If mteTriggerType is not 'boolean', this object is not
instantiated." instantiated."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerEntry 10 } ::= { mteTriggerEntry 14 }
mteTriggerRisingEvent OBJECT-TYPE mteTriggerRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..64)) SYNTAX SnmpAdminString (SIZE (0..64))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The event to invoke when mteTriggerType is 'threshold' and "The event to invoke when mteTriggerType is 'threshold' and
this trigger fires based on mteTriggerRisingThreshold. A this trigger fires based on mteTriggerRisingThreshold. A
value of 0 indicates no event. value of 0 indicates no event.
If mteTriggerType is not 'threshold', this object is not If mteTriggerType is not 'threshold', this object is not
instantiated." instantiated."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerEntry 11 } ::= { mteTriggerEntry 15 }
mteTriggerFallingEvent OBJECT-TYPE mteTriggerFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..64)) SYNTAX SnmpAdminString (SIZE (0..64))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The event to invoke when mteTriggerType is 'threshold' and "The event to invoke when mteTriggerType is 'threshold' and
this trigger fires based on mteTriggerFallingThreshold. A this trigger fires based on mteTriggerFallingThreshold. A
value of 0 indicates no event. value of 0 indicates no event.
If mteTriggerType is not 'threshold', this object is not If mteTriggerType is not 'threshold', this object is not
instantiated." instantiated."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerEntry 12 } ::= { mteTriggerEntry 16 }
mteTriggerObjects OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..64))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The mteTriggerObjectNName of a group of objects from
mteTriggerObjectTable. These objects are to be added to any
Notification resulting from the firing of this trigger.
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteTriggerEntry 17 }
mteTriggerStatus OBJECT-TYPE mteTriggerStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The control that allows creation and deletion of entries. "The control that allows creation and deletion of entries.
Once made active an entry may not be modified except to Once made active an entry may not be modified except to
delete it." delete it."
::= { mteTriggerEntry 13 } DEFVAL { createAndWait }
::= { mteTriggerEntry 18 }
-- --
-- Trigger Object Table
-- --
mteEventFailures OBJECT-TYPE mteTriggerObjectTable OBJECT-TYPE
SYNTAX Counter32 SYNTAX SEQUENCE OF mteTriggerObjectEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of times an attempt to invoke an event "A table of objects related to a trigger and to be added to
has failed. This counts individually for each Notifications resulting from that trigger."
attempt in a group of targets or each attempt for a ::= { mteTrigger 3 }
wildcarded trigger object."
::= { mteEvent 1 }
mteEventLastFailedEvent OBJECT-TYPE mteTriggerObjectEntry OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX mteTriggerObjectEntry
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current
"Objects for a single trigger. Applications create and
delete entries using mteTriggerObjectStatus."
INDEX { mteTriggerObjectName, mteTriggerObjectIndex }
::= { mteTriggerObjectteble 1 }
mteTriggerObjectEntry ::= SEQUENCE {
mteTriggerObjectName SnmpAdminString,
mteTriggerObjectIndex Unsigned32,
mteTriggerObjectID Integer32,
mteTriggerObjectIDWildcard TruthValue,
mteTriggerObjectStatus RowStatus
}
mteTriggerObjectName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..64))
MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The event that last failed an attempted invocation." "A locally-unique, administratively assigned name for a group
::= { mteEvent 2 } of objects to associate with a trigger."
::= { mteTriggerObjectEntry 1 }
mteEventLastFailedReason OBJECT-TYPE mteTriggerObjectIndex OBJECT-TYPE
SYNTAX FailureReason SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS read-only MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The reason for the last failure of an attempted event "An arbitrary small integer for the purpose of identifying
invocation." individual objects with a mteTriggerObjectName group."
::= { mteEvent 3 } ::= { mteTriggerObjectEntry 2 }
mteEventLastFailedTargetTag OBJECT-TYPE mteTriggerObjectID OBJECT-TYPE
SYNTAX SnmpTagValue SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-only MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The target tag of the last failed attempt to invoke an "The object identifier of a MIB object to add to a Notification
event. The length 0 means this does not apply." that results from the firing of a trigger.
::= { mteEvent 4 }
mteEventLastFailedTargetName OBJECT-TYPE This may be wildcarded by truncating all or part of the
SYNTAX SnmpAdminString instance portion, in which case the instance portion of the
OID for obtaining this object will be the same as that used
in obtaining the mteTriggerObjectValueID that fired.
If such wildcarding is applied, mteTriggerObjectIDWildcard
must be 'true' and if not it must be 'false'."
DEFVAL { 0 0 }
::= { mteTriggerObjectEntry 3 }
mteTriggerObjectValueIDWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteTriggerObjectValueID is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard.
DEFVAL { false }
::= { mteTriggerObjectEntry 4 }
mteTriggerObjectStatus OBJECT-TYPE
SYNTAX RowStatus
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The control that allows creation and deletion of entries.
Once made active an entry may not be modified except to
delete it."
DEFVAL { createAndWait }
::= { mteTriggerObjectEntry 5 }
--
-- Event Section
--
-- Counters
mteEventFailures OBJECT-TYPE
SYNTAX Counter32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The target name of the last failed attempt to invoke an "The number of times an attempt to invoke an event
event. The length 0 means this does not apply" has failed. This counts individually for each
::= { mteEvent 5 } attempt in a group of targets or each attempt for a
wildcarded trigger object."
::= { mteEvent 1 }
-- --
-- Event Table -- Event Table
-- --
mteEventTable OBJECT-TYPE mteEventTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventEntry SYNTAX SEQUENCE OF MteEventEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of management event action information." "A table of management event action information."
::= { mteEvent 6 } ::= { mteEvent 2 }
mteEventEntry OBJECT-TYPE mteEventEntry OBJECT-TYPE
SYNTAX MteEventEntry SYNTAX MteEventEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single event. "Information about a single event. Applications create and
delete entries using mteEventStatus."
To create an entry create the named entry in this
table use mteEventStatus."
INDEX { IMPLIED mteEventName } INDEX { IMPLIED mteEventName }
::= { mteEventTable 1 } ::= { mteEventTable 1 }
MteEventEntry ::= SEQUENCE { MteEventEntry ::= SEQUENCE {
mteEventName SnmpAdminString, mteEventName SnmpAdminString,
mteEventComment DisplayString, mteEventComment DisplayString,
mteEventActions BITS, mteEventActions BITS,
mteEventNotification OBJECT IDENTIFIER, mteEventNotification OBJECT IDENTIFIER,
mteEventObjects SnmpAdminString,
mteEventSetObject OBJECT IDENTIFIER, mteEventSetObject OBJECT IDENTIFIER,
mteEventSetObjectWildcard TruthValue,
mteEventSetValue Integer32, mteEventSetValue Integer32,
mteEventSetTargetTag SnmpTagValue, mteEventSetTargetTag SnmpTagValue,
mteEventCreationStatus RowStatus mteEventSetContextName SnmpAdminString,
mteEventSetContextNameWildcard TruthValue,
mteEventStatus RowStatus
} }
mteEventName OBJECT-TYPE mteEventName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..64)) SYNTAX SnmpAdminString (SIZE (1..64))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for the event." "A locally-unique, administratively assigned name for the event."
::= { mteEventCreationEntry 1 } ::= { mteEventCreationEntry 1 }
skipping to change at page 16, line 15 skipping to change at page 19, line 39
::= { mteEventEntry 2 } ::= { mteEventEntry 2 }
mteEventActions OBJECT-TYPE mteEventActions OBJECT-TYPE
SYNTAX BITS { notification, set } SYNTAX BITS { notification, set }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actions to peform when this event occurs. "The actions to peform 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 { 0 }
::= { mteEventEntry 3 } ::= { mteEventEntry 3 }
mteEventNotification OBJECT-TYPE mteEventNotification OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object identifier from the NOTIFICATION-TYPE for the "The object identifier from the NOTIFICATION-TYPE for the
notification to use if metEventActions has 'notification' set. notification to use if metEventActions has 'notification' set.
If 'notification' is not set, this object is not instantiated." If 'notification' is not set, this object is not instantiated."
DEFVAL { 0 0 } DEFVAL { 0 0 }
::= { mteEventEntry 4 } ::= { mteEventEntry 4 }
mteEventObjects OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..64))
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The mteTriggerObjectName of a group of objects from
mteTriggerObjectTable if mteEventActions has 'notification' set.
These objects are to be added to any Notification generated by
this event.
If 'notification' is not set, this object is not instantiated.
A length of 0 indicates no additional objects."
DEFVAL { ''H }
::= { mteEventEntry 5 }
mteEventSetObject OBJECT-TYPE mteEventSetObject OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object identifier from the MIB object to set if "The object identifier from the MIB object to set if
metEventActions has 'set' set. mteEventActions has 'set' set.
This object identifier may be wildcarded by leaving sub-identifiers
off the end, in which case nteEventSetObjectWildCard must be
'true'.
If mteEventSetObject is wildcarded the instance used to set it
is the same as the instance for the value of mteTriggerValueID
that triggered the event."
If 'set' is not set, this object is not instantiated." If 'set' is not set, this object is not instantiated."
DEFVAL { 0 0 } DEFVAL { 0 0 }
::= { mteEventEntry 5 } ::= { mteEventEntry 6 }
mteEventSetObjectWildcard OBJECT-TYPE mteEventSetObjectWildcard OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Control over whether mteEventSetObject is to be treated as "Control over whether mteEventSetObject 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 mteEventSetObject is wildcarded the instance used to set it If 'set' is not set, this object is not instantiated."
is the same as the instance for the value of mteTriggerValueID
that triggered the event."
DEFVAL { false } DEFVAL { false }
::= { mteEventEntry 6 } ::= { mteEventEntry 7 }
mteEventSetValue OBJECT-TYPE mteEventSetValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value to which to set the object at mteEventSetObject." "The value to which to set the object at mteEventSetObject
if mteEventActions has 'set' set.
If 'set' is not set, this object is not instantiated."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteEventEntry 7 } ::= { mteEventEntry 8 }
mteEventSetTargetTag OBJECT-TYPE mteEventSetTargetTag OBJECT-TYPE
SYNTAX SnmpTagValue SYNTAX SnmpTagValue
MAX-ACCESS read-create MAX-ACCESS read-create
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. A length of 0 mteEventSetObject to mteEventSetValue if mteEventActions
indicates the local system." has 'set' set.
If 'set' is not set, this object is not instantiated."
Systems limited to self management may not accept a non-zero
length for the value of this object.
A length of 0 indicates the local system. In this case,
access to the objects indicated by mteEventObjectID is under
the security credentials of the requester that set
mteEventStatus to 'active'."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteEventEntry 8 } ::= { mteEventEntry 9 }
mteEventSetContextName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"The management context in which to set mteEventObjectID.
if mteEventActions has 'set' set.
If 'set' is not set, this object is not instantiated."
This may be wildcarded by leaving characters off the end. To
indicate such wildcarding mteEventSetContextNameWildcard must
be 'true'.
If this context name is wildcarded the value used to complete
the wildcarding of mteTriggerContextName will be appended."
DEFVAL { ''H }
::= { mteEventEntry 10 }
mteEventSetContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue
MAX-ACCESS read-create
STATUS current
DESCRIPTION
"Control for whether mteEventSetContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard
if mteEventActions has 'set' set.
If 'set' is not set, this object is not instantiated."
DEFVAL { false }
::= { mteTriggerEntry 10 }
mteEventStatus OBJECT-TYPE mteEventStatus OBJECT-TYPE
SYNTAX RowStatus SYNTAX RowStatus
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The control that allows creation and deletion of entries. "The control that allows creation and deletion of entries.
Once made active an entry may not be modified except to Once made active an entry may not be modified except to
delete it." delete it."
::= { mteEventEntry 9 } DEFVAL { createAndWait }
::= { mteEventEntry 12 }
-- --
-- Notifications -- Notifications
-- --
eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 }
eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 } eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 }
eventMIBNotificationObjectss OBJECT IDENTIFIER
::= { eventMIBNotificationPrefix 1 }
--
-- Notification Objects
--
mteHotTrigger OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The name of the trigger causing the notification.
::= { mteTrigger 1 }
mteHotTargetName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The SNMP Target MIB's snmpTargetAddrName related to the
notification.
::= { mteTrigger 2 }
mteHotContextName OBJECT-TYPE
SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The context name related to the notification. This must be as
fully-qualified as possible, inluding filling in wildcard
informaation determined in processing."
::= { mteTrigger 3 }
mteHotOID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The object identifier of the destination object related to the
notification. This must be as fully-qualified as possible,
inluding filling in wildcard informaation determined in processing.
For a trigger-related notification this is from mteTriggerValueID.
For a set failure this is from mteEventSetObject."
::= { mteTrigger 3 }
mterHotValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The value of the object at mteTriggerValueID when a
trigger fired."
::= { mteTrigger 5 }
mteFailedReason OBJECT-TYPE
SYNTAX FailureReason
MAX-ACCESS accessible-for-notify
STATUS current
DESCRIPTION
"The reason for the failure of an attempt to check for a
trigger condition or set an object in response to an event.
::= { mteTrigger 6 }
--
-- Notifications
--
mteTriggerSenseAlarm NOTIFICATION-TYPE mteTriggerSenseAlarm NOTIFICATION-TYPE
OBJECTS { mteTriggerTargetName, OBJECTS { mteHotTrigger,
mteTriggerLastValueID, mteHotTargetName,
mteTriggerLastValue } mteHotContextName,
mteHotOID,
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'."
::= { eventMIBNotifications 1 } ::= { eventMIBNotifications 1 }
mteTriggerRisingAlarm NOTIFICATION-TYPE mteTriggerRisingAlarm NOTIFICATION-TYPE
OBJECTS { mteTriggerTargetName, OBJECTS { mteHotTrigger,
mteTriggerLastValueID, mteHotTargetName,
mteTriggerLastValue } mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification that the rising threshold was met for triggers "Notification that the rising threshold was met for triggers
with mteTriggerType 'threshold'." with mteTriggerType 'threshold'."
::= { eventMIBNotifications 2 } ::= { eventMIBNotifications 2 }
mteTriggerFallingAlarm NOTIFICATION-TYPE mteTriggerFallingAlarm NOTIFICATION-TYPE
OBJECTS { mteTriggerTargetName, OBJECTS { mteHotTrigger,
mteTriggerLastValueID, mteHotTargetName,
mteTriggerLastValue } mteHotContextName,
mteHotOID,
mteHotValue }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification that the falling threshold was met for triggers "Notification that the falling threshold was met for triggers
with mteTriggerType 'threshold'." with mteTriggerType 'threshold'."
::= { eventMIBNotifications 3 } ::= { eventMIBNotifications 3 }
mteTriggerFailureAlarm NOTIFICATION-TYPE mteTriggerFailureAlarm NOTIFICATION-TYPE
OBJECTS { mteTriggerLastFailedReason, OBJECTS { mteHotTrigger,
mteTriggerLastFailedTargetTag, mteHotTargetName,
mteTriggerLastFailedTargetName, mteHotContextName,
mteTriggerLastFailedValueID } mteHotOID,
mteFailedReason }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification that an attempt to check a trigger has failed. "Notification that an attempt to check a trigger has failed.
The network manager must enable this notification only with The network manager must enable this notification only with
a certain fear and trembling, as it can easily crowd out more a certain fear and trembling, as it can easily crowd out more
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."
::= { eventMIBNotifications 4 } ::= { eventMIBNotifications 4 }
mteEventFailureAlarm NOTIFICATION-TYPE mteEventSetFailureAlarm NOTIFICATION-TYPE
OBJECTS { mteTriggerTargetName, OBJECTS { mteHotTrigger,
mteTriggerLastValueID, mteHotTargetName,
mteTriggerLastValue, mteHotContextName,
mteEventLastFailedReason, mteHotOID,
mteEventLastFailedTargetTag, mteFailedReason }
mteEventLastFailedTargetName }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notification that an attempt to check a trigger has failed. "Notification that an attempt to do a set in response to an
event has failed.
The network manager must enable this notification only with The network manager must enable this notification only with
a certain fear and trembling, as it can easily crowd out more a certain fear and trembling, as it can easily crowd out more
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."
::= { eventMIBNotifications 5 } ::= { eventMIBNotifications 5 }
--
-- Conformance
--
eventMIBConformance OBJECT IDENTIFIER ::= { eventMIB 3 }
eventMIBCompliances OBJECT IDENTIFIER ::= { eventMIBConformance 1 }
eventMIBGroups OBJECT IDENTIFIER ::= { eventMIBConformance 2 }
-- Compliance
eventMIBCompliance MODULE-COMPLIANCE
STATUS current
DESCRIPTION
"The compliance statement for entities which implement
the Event MIB."
MODULE -- this module
MANDATORY-GROUPS {
eventTriggerGroup,
eventEventGroup,
eventNotificationObjectGroup,
eventNotificationGroup
}
OBJECT mteTriggerTargetTag
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, thus limiting
monitoring to the local system or preconfigured
remote systems.""
OBJECT mteEventSetTargetTag
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, thus limiting
setting to the local system or preconfigured
remote systems.""
OBJECT mteTriggerValueIDWildcard
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, thus allowing
the system not to implement wildcarding."
OBJECT mteTriggerContextNameWildcard
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, thus allowing
the system not to implement wildcarding."
OBJECT mteTriggerObjectValueIDWildcard
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, thus allowing
the system not to implement wildcarding."
OBJECT mteEventSetContextNameWildcard
MIN-ACCESS read-only
DESCRIPTION
"Write access is not required, thus allowing
the system not to implement wildcarding."
::= { eventMIBCompliances 1 }
-- Units of Conformance
eventTriggerGroup OBJECT-GROUP
OBJECTS {
mteTriggerFailures,
mteTriggerComment,
mteTriggerTest,
mteTriggerValueID,
mteTriggerValueIDWildcard,
mteTriggerTargetTag,
mteTriggerContextName,
mteTriggerContextNameWildcard,
mteTriggerFrequency,
mteTriggerBooleanStartup,
mteTriggerThresholdStartup,
mteTriggerRisingThreshold,
mteTriggerFallingThreshold,
mteTriggerEvent,
mteTriggerRisingEvent,
mteTriggerFallingEvent,
mteTriggerObjects,
mteTriggerStatus,
mteTriggerObjectID,
mteTriggerObjectIDWildcard,
mteTriggerObjectStatus
}
STATUS current
DESCRIPTION
"Event triggers and supplemental objects."
::= { eventMIBGroups 1 }
eventEventGroup OBJECT-GROUP
OBJECTS {
mteEventComment,
mteEventActions,
mteEventNotification,
mteEventObjects,
mteEventSetObject,
mteEventSetObjectWildcard,
mteEventSetValue,
mteEventSetTargetTag,
mteEventSetContextName,
mteEventSetContextNameWildcard,
mteEventStatus
}
STATUS current
DESCRIPTION
"Events."
::= { eventMIBGroups 2 }
eventNotificationObjectGroup OBJECT-GROUP
OBJECTS {
mteHotTrigger,
mteHotTargetName,
mteHotContextName,
mteHotOID,
mterHotValue,
mteFailedReason
}
STATUS current
DESCRIPTION
"Notification objects."
::= { eventMIBGroups 3 }
eventNotificationGroup OBJECT-GROUP
OBJECTS {
mteTriggerSenseAlarm,
mteTriggerRisingAlarm,
mteTriggerFallingAlarm,
mteTriggerFailureAlarm,
mteEventSetFailureAlarm
}
STATUS current
DESCRIPTION
"Notifications."
::= { eventMIBGroups 4 }
END END
6. 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), and colleagues at Cisco. Stewart, and Steve Waldbusser), and colleagues at Cisco.
7. References 10. References
[1] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for
S. Waldbusser, "Structure of Management Information for version 2 Describing SNMP Management Frameworks", RFC 2271, Cabletron
of the Simple Network Management Protocol (SNMPv2)", RFC 1902, Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998
[2] Rose, M., and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
Performance Systems International, Hughes LAN Systems, March 1991
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure
of Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[2] McCloghrie, K., and M. Rose, Editors, "Management Information Base [7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance
for Network Management of TCP/IP-based internets: MIB-II", STD 17, Statements for Version 2 of the Simple Network Management Protocol
RFC 1213, March 1991. (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[3] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network
Management Protocol", RFC 1157, May 1990. Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990.
[4] SNMPv2 Working Group, Case, J., McCloghrie, K., Rose, M., and [9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser,
S. Waldbusser, "Protocol Operations for version 2 of the Simple "Introduction to Community-based SNMPv2", RFC 1901, SNMP Research,
Network Management Protocol (SNMPv2)", RFC 1905, January 1996. Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc.,
International Network Services, January 1996.
8. Security Considerations [10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
Security issues are not discussed in this memo. [11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
9. Author's Address [12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services,
January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998
[16] Waldbusser, S., "Remote Network Monitoring Management Information
Base", RFC 1757, International Network Services, February 1995
[17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to-
Manager Management Information Base", RFC 1451, SNMP Research,
Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc.,
International Network Services, April 1993
[18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc.,
?Month? 1998
[19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc.,
?Month? 1998
11. Security Considerations
Security issues are discussed in the Overview section and in the
DESCRIPTION clauses of relevant objects.
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
Phone: 408-526-4527 Phone: 408-526-4527
Email: bstewart@cisco.com Email: bstewart@cisco.com
Table of Contents Table of Contents
1 Abstract ........................................................ 2 1 Abstract ........................................................ 2
2 The SNMP Network Management Framework ........................... 3 2 The SNMP Management Framework ................................... 2
2.1 Object Definitions ............................................ 3
3 Overview ........................................................ 4 3 Overview ........................................................ 4
4 Known Problems .................................................. 4 4 Relationship to Other MIBs ...................................... 4
5 Definitions ..................................................... 5 5 MIB Sections .................................................... 4
6 Acknowledgements ................................................ 20 6 Operation ....................................................... 5
7 References ...................................................... 21 7 Security ........................................................ 5
8 Security Considerations ......................................... 22 8 Definitions ..................................................... 7
9 Author's Address ................................................ 22 9 Acknowledgements ................................................ 30
10 References ..................................................... 31
11 Security Considerations ........................................ 33
12 Author's Address ............................................... 33
 End of changes. 

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