draft-ietf-disman-event-mib-08.txt   draft-ietf-disman-event-mib-09.txt 
Event MIB Event MIB
22 October 1999 6 January 2000
draft-ietf-disman-event-mib-08.txt draft-ietf-disman-event-mib-09.txt
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
Ramanathan R. Kavasseri
Cisco Systems, Inc.
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.
Internet-Drafts are working documents of the Internet Engineering Task Internet-Drafts are working documents of the Internet Engineering Task
Force (IETF), its areas, and its working groups. Note that other groups Force (IETF), its areas, and its working groups. Note that other groups
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 The list of Internet-Draft Shadow Directories can be accessed at
http://www.ietf.org/shadow.html.Distribution of this document is unlimited. http://www.ietf.org/shadow.html.
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@dorothy.BMC.com>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (2000). All Rights Reserved.
1. Abstract 1. Abstract
This memo defines a portion of the Management Information Base (MIB) for This memo defines an experimental portion of the Management Information
use with network management protocols in the Internet community. In Base (MIB) for use with network management protocols in the Internet
particular, it describes managed objects used for managing monitoring of community. In particular, it describes managed objects that can be used
MIB objects and taking action through events. to manage and monitor MIB objects and take action through events.
The Event MIB provides the ability to monitor MIB objects on the local
system or on a remote system and take simple action when a trigger
condition is met.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 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:
skipping to change at page 3, line 20 skipping to change at page 3, line 25
defined using the mechanisms defined in the SMI. defined using the mechanisms defined in the SMI.
This memo specifies a MIB module that is compliant to the SMIv2. A This memo specifies a MIB module that is compliant to the SMIv2. A
MIB conforming to the SMIv1 can be produced through the appropriate MIB conforming to the SMIv1 can be produced through the appropriate
translations. The resulting translated MIB must be semantically translations. The resulting translated MIB must be semantically
equivalent, except where objects or events are omitted because no equivalent, except where objects or events are omitted because no
translation is possible (use of Counter64). Some machine readable translation is possible (use of Counter64). Some machine readable
information in SMIv2 will be converted into textual descriptions in information in SMIv2 will be converted into textual descriptions in
SMIv1 during the translation process. However, this loss of machine SMIv1 during the translation process. However, this loss of machine
readable information is not considered to change the semantics of the readable information is not considered to change the semantics of the
MIB. MIB. It may not be possible to meaningfully monitor Counter64 objects
using an SMIv1 version of the MIB.
3. Overview 3. Overview
With network sizes well beyond the ability of people to management them With network sizes well beyond the ability of people to manage them
directly, automated, distributed management is vital. An important directly, automated, distributed management is vital. An important
aspect of such management is the ability of a system to monitor itself aspect of such management is the ability of a system to monitor itself
or for some other system to monitor it. or for some other system to monitor it.
The Event MIB provides the ability to monitor MIB objects on the local The Event MIB provides the ability to monitor MIB objects on the 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 mid- The MIB is intended to suit either a relatively powerful manager or mid-
level manager, as well as a somewhat more limited self-managing system. level manager, as well as a somewhat more limited self-managing system.
4. Relationship to Other MIBs 4. Relationship to Other MIBs
The Event MIB is based on extensive experience with the RMON MIB The Event MIB is based on extensive experience with the RMON MIB
[RFC1757] and its alarm and event groups and is intended as a [RFC1757] and provides a superset of the capabilities of the RMON alarm
replacement for those groups. The Event MIB calls "triggers" what the and event groups. Conceptually, the key extension is the ability to
RMON MIB called "alarms," but the concepts are the same. Event MIB allow alarms to be generated for MIB objects that are on another network
triggers maintain the RMON handling of thresholds and add the concept of element. The Event MIB calls "triggers" what the RMON MIB called
booleans. Event MIB events maintain the RMON concept of sending an SNMP "alarms," but the concepts are the same. Event MIB triggers maintain
notification in response to a trigger and add the concept of setting a the RMON handling of thresholds and add the concept of booleans. Event
MIB object. 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.
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 [RFC1451] 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 [RFC2573]. and Notification MIBs [RFC2573].
The Event MIB is nicely complemented by the Distributed Management The Event MIB is nicely complemented by the Distributed Management
Expression MIB [RFCExpressionMIB], which is the expected source of Expression MIB [RFCExpressionMIB], which is the expected source of
boolean objects to monitor. Note that there is considerable overlap boolean objects to monitor. Note that there is considerable overlap
skipping to change at page 5, line 14 skipping to change at page 5, line 16
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.
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.
The following diagram describes the relationships between the tables
in the Event MIB.
+--------------------------------+
| mteTriggerEntry | subclassed by:
| { mteOwner, |---+
| IMPLIED mteTriggerName } | +-- mteTriggerDeltaEntry
| | |
| | +-- mteTriggerExistenceEntry
| | |
| | +-- mteTriggerBooleanEntry
| | |
| | +-- mteTriggerThresholdEntry
| |
| |
| |
| |
| mteTrigger*Event ----------------------------->+
| | |
| mteTriggerObjects --------------->+ |
| | | |
+--------------------------------+ | |
| |
V |
+<--------------------------------------------+ |
| |
V |
+--------------------------------+ |
| | |
| mteObjectsEntry | |
| { mteOwner, | |
| mteObjectsName, | |
| mteObjectsIndex } | |
| | |
+--------------------------------+ |
|
V
+<---------------------------------------------------------+
|
V
+---------------------------------+
| |
| mteEventEntry |
| { mteOwner, |
| IMPLIED mteEventName } |
| |
| mteEventAction - - - - - - > + (condition)
| | |
+---------------------------------+ |
|
+ < - - - + < - - - - - - - - - - - - - - +
| |
| |
| |
| V
| +---------------------------------+
| | |
| | mteEventNotificationEntry |
| | { mteOwner, |
| | IMPLIED mteEventName } |
| | |
| +---------------------------------+
|
|
|
V
+---------------------------------+
| |
| mteEventSetEntry |
| { mteOwner, |
| IMPLIED mteEventName } |
| |
+---------------------------------+
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
wildcarded groups of objects. wildcarded groups of objects.
Remote monitoring uses the tag service of the Management Target MIB to Remote monitoring uses the tag service of the Management Target MIB
select and access remote systems as an ordinary SNMP-based management [RFC2573] to select and access remote systems as an ordinary SNMP-based
application. Local monitoring may be via a more intimate, local management application. Local monitoring may be via a more intimate,
interface which may, for example, bypass SNMP encoding but otherwise is local interface which may, for example, bypass SNMP encoding but
functionally identical to remote SNMP operation, including the
application of access control. A self-management only system may not
implement remote monitoring.
Wildcards indicate that the application should use a GetNext-type otherwise is functionally identical to remote SNMP operation, including
the application of access control. A self-management only system MAY
not implement remote monitoring.
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
The instance that satisfied the trigger function is used to perform the object. The instance that satisfied the trigger function is used to
set function. All of this takes place independently of any additional perform the set function. All of this takes place independently of any
instances that may fill the wildcard. additional instances that may fill the wildcard.
Error handling is by notification, which at first thought violates the Error handling is by notification. These error notifications SHOULD be
principle that notifications may be lost or become a crippling burden, enabled only for the diagnosis of problems indicated by error counters.
but the intent is that such error notifications be enabled only for the If minimizing the probability of notification loss is a concern they
diagnosis of problems indicated by error counters and if the SHOULD be transmitted as Inform PDUs as described in the [SNMP-TARGET-
notifications are being lost they be directed to the log as described in MIB] or directed to a log as described in the Notification Log MIB
the Notification Log MIB [rfcNotificationLogMIB]. Note that this does [rfcNotificationLogMIB]. Note that this does not mean the Notification
not mean the Notification Log MIB is required, since in fact Log MIB is REQUIRED, since in fact notifications usually are not lost,
notifications usually are not lost, but that the Notification Log MIB but that the Notification Log MIB can be helpful with this as well as
can be helpful with this as well as other MIBs that include other MIBs that include notifications.
notifications.
Although like most MIBs this one has no explicit controls for the Although like most MIBs this one has no explicit controls for the
persistance of the values set in configuring events, a robust, polite persistence of the values set in configuring events, a robust, polite
implementation would certainly not force its managing applications to implementation would certainly not force its managing applications to
reconfigure it whenever it resets. reconfigure it whenever it resets.
Again, as with most MIBs, it is implementation specific how a system Again, as with most MIBs, it is implementation-specific how a system
provides and manages such persistance. To speculate, one could imagine, provides and manages such persistence. To speculate, one could imagine,
for example, that persistance depended on the context in which the for example, that persistence depended on the context in which the
expression was configured, or perhaps system-specific characteristics of expression was configured, or perhaps system-specific characteristics of
the expression's owner. Or perhaps everything in a MIB such as this the expression's owner. Or perhaps everything in a MIB such as this
one, which is clearly aimed at persistant configuration, is one, which is clearly aimed at persistent configuration, is
automatically part of a system's other persistant configuration. automatically part of a system's other persistent 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 entry owner names. entire MIB or for subsets based on entry owner names.
Security of monitored objects for remote access depends on the Security of monitored objects for remote access depends on the
Management Target MIB. Security for local access can depend on the
Management Target MIB or on recording appropriate security credentials Management Target MIB [RFC2573]. Security for local access can depend
of the creator of an entry and using those to access the local objects. on the Management Target MIB or on recording appropriate security
These security credentials are the parameters necessary as inputs to credentials of the creator of an entry and using those to access the
isAccessAllowed from the Architecture for Describing SNMP Management local objects. These security credentials are the parameters necessary
Frameworks. When accessing local objects without using a local target as inputs to isAccessAllowed from the Architecture for Describing SNMP
tag, the system must (conceptually) use isAccessAllowed to ensure that Management Frameworks. When accessing local objects without using a
it does not violate security. local target tag, the system MUST (conceptually) use isAccessAllowed to
ensure that it does not violate security.
To facilitate the provisioning of access control by a security To facilitate the provisioning of access control by a security
administrator for this MIB itself using the View-Based Access Control administrator for this MIB itself using the View-Based Access Control
Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple Model (VACM) defined in RFC 2275 [RFC2575] for tables in which multiple
users may need to independently create or modify entries, the initial 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 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 sub-identifiers (except for the "column" sub-
subidentifier) up to the end of the encoded owner index. To configure identifier) up to the end of the encoded owner index. To configure VACM
VACM to permit access to this portion of the table, one would create to permit access to this portion of the table, one would create
vacmViewTreeFamilyTable entries with the value of vacmViewTreeFamilyTable entries with the value of
vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilySubtree including the owner index portion, and
vacmViewTreeFamilyMask "wildcarding" the column subidentifier. More vacmViewTreeFamilyMask "wildcarding" the column sub-identifier. More
elaborate configurations are possible. elaborate configurations are possible.
8. Definitions 8. Definitions
DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN DISMAN-EVENT-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
Integer32, Unsigned32, Integer32, Unsigned32,
NOTIFICATION-TYPE, Counter32, NOTIFICATION-TYPE, Counter32,
Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI Gauge32, mib-2, zeroDotZero FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TruthValue FROM SNMPv2-TC TruthValue FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP, MODULE-COMPLIANCE, OBJECT-GROUP,
NOTIFICATION-GROUP FROM SNMPv2-CONF NOTIFICATION-GROUP FROM SNMPv2-CONF
sysUpTime FROM SNMPv2-MIB sysUpTime FROM SNMPv2-MIB
SnmpTagValue FROM SNMP-TARGET-MIB SnmpTagValue FROM SNMP-TARGET-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
dismanEventMIB MODULE-IDENTITY dismanEventMIB MODULE-IDENTITY
LAST-UPDATED "9910220000Z" LAST-UPDATED "200001060000Z" -- 6 January 2000
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Ramanathan Kavasseri CONTACT-INFO "Ramanathan Kavasseri
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose CA 95134-1706. San Jose CA 95134-1706.
Phone: +1 408 526 4527 Phone: +1 408 526 4527
Email: ramk@cisco.com" Email: ramk@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for defining event triggers and actions "The MIB module for defining event triggers and actions
for network management purposes." for network management purposes."
-- Revision History -- Revision History
REVISION "9910220000Z" -- 22 October 1999 REVISION "200001060000Z" -- 6 January 2000
DESCRIPTION "This is the initial version of this MIB. DESCRIPTION "This is the initial version of this MIB.
Published as RFC xxxxx" Published as RFC xxxxx"
::= { mib-2 xx } -- final assignment by IANA at publication time ::= { mib-2 xx } - final assignment by IANA at publication time
dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
-- Management Triggered Event (MTE) objects
mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 } mteResource OBJECT IDENTIFIER ::= { dismanEventMIBObjects 1 }
mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 } mteTrigger OBJECT IDENTIFIER ::= { dismanEventMIBObjects 2 }
mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 } mteObjects OBJECT IDENTIFIER ::= { dismanEventMIBObjects 3 }
mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 } mteEvent OBJECT IDENTIFIER ::= { dismanEventMIBObjects 4 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
FailureReason ::= TEXTUAL-CONVENTION FailureReason ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reasons for failures in an attempt to perform a management "Reasons for failures in an attempt to perform a management
request. request.
The first group of errors, numbered less than 0, are related The first group of errors, numbered less than 0, are related
to problems in sending the request. The existence of a to problems in sending the request. The existence of a
skipping to change at page 9, line 20 skipping to change at page 11, line 22
"Reasons for failures in an attempt to perform a management "Reasons for failures in an attempt to perform a management
request. request.
The first group of errors, numbered less than 0, are related The first group of errors, numbered less than 0, are related
to problems in sending the request. The existence of a to problems in sending the request. The existence of a
particular error code here does not imply that all particular error code here does not imply that all
implementations are capable of sensing that error and implementations are capable of sensing that error and
returning that code. returning that code.
The second group, numbered greater than 0, are copied The second group, numbered greater than 0, are copied
directly from SNMP protocol operations and are intended to carry directly from SNMP protocol operations and are intended to
exactly the meanings defined for the protocol as returned in carry exactly the meanings defined for the protocol as returned
an SNMP response. in an SNMP response.
localResourceLack some local resource such as memory lacking localResourceLack some local resource such as memory lacking
or mteResourceSampleInstanceMaximum or mteResourceSampleInstanceMaximum
exceeded exceeded
badDestination unrecognized domain name or otherwise badDestination unrecognized domain name or otherwise
invalid destination address invalid destination address
destinationUnreachable can't get to destination address destinationUnreachable can't get to destination address
noResponse no response to SNMP request noResponse no response to SNMP request
badType the data syntax of a retrieved object badType the data syntax of a retrieved object
as not as expected as not as expected
skipping to change at page 10, line 22 skipping to change at page 12, line 24
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..600) SYNTAX Integer32 (1..2147483647)
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 system may use the larger values of this minimum to accept. A system may use the larger values of this minimum to
lessen the impact of constant sampling. For larger lessen the impact of constant sampling. For larger
sampling intervals the system samples less often and sampling intervals the system samples less often and
suffers less overhead. This object provides a way to enforce suffers less overhead. This object provides a way to enforce
such lower overhead for all triggers created after it is such lower overhead for all triggers created after it is
set. set.
Unless explicitly resource limited, a system's value for Unless explicitly resource limited, a system's value for
this object should be 1, allowing as small as a 1 second this object SHOULD be 1, allowing as small as a 1 second
interval for ongoing trigger sampling. 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
skipping to change at page 11, line 16 skipping to change at page 13, line 18
These are the entries that maintain state, one for each These are the entries that maintain state, one for each
instance of each sampled object as selected by instance of each sampled object as selected by
mteTriggerValueID. Note that wildcarded objects result mteTriggerValueID. Note that wildcarded objects result
in multiple instances of this state. in multiple instances of this state.
A value of 0 indicates no preset limit, that is, the limit A value of 0 indicates no preset limit, that is, the limit
is dynamic based on system operation and resources. is dynamic based on system operation and resources.
Unless explicitly resource limited, a system's value for Unless explicitly resource limited, a system's value for
this object should be 0. this object SHOULD be 0.
Changing this value will not eliminate or inhibit existing sample Changing this value will not eliminate or inhibit existing
state but could prevent allocation of additional state sample state but could prevent allocation of additional state
information." information."
::= { mteResource 2 } ::= { mteResource 2 }
mteResourceSampleInstances OBJECT-TYPE mteResourceSampleInstances OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
UNITS "instances" UNITS "instances"
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The number of currently active instance entries as "The number of currently active instance entries as
skipping to change at page 12, line 17 skipping to change at page 14, line 19
::= { mteResource 5 } ::= { mteResource 5 }
-- --
-- Trigger Section -- Trigger Section
-- --
-- Counters -- Counters
mteTriggerFailures OBJECT-TYPE mteTriggerFailures OBJECT-TYPE
SYNTAX Counter32 SYNTAX Counter32
UNITS "failures"
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 }
-- --
skipping to change at page 14, line 11 skipping to change at page 16, line 15
"A description of the trigger's function and use." "A description of the trigger's function and use."
DEFVAL { ''H } DEFVAL { ''H }
::= { 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 (that is, in BER, not ASN.1) 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, vanishes
the trigger fires. The trigger will not fire again until the or changes value, the trigger fires. If the object's
object has changed states. appearance caused the trigger firing, the object MUST
vanish before the trigger can be fired again for it, and
vice versa. If the trigger fired due to a change in the
object's value, it will be fired again on every successive
value change for that object.
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.
For 'threshold' the test works as described below for For 'threshold' the test works as described below for
mteTriggerThresholdStartup, mteTriggerThresholdRising, and mteTriggerThresholdStartup, mteTriggerThresholdRising, and
mteTriggerThresholdFalling. mteTriggerThresholdFalling.
skipping to change at page 15, line 6 skipping to change at page 17, line 16
meaningful, and is exactly the value of the object at meaningful, and is exactly the value of the object at
mteTriggerValueID at the sample time. mteTriggerValueID at the sample time.
A 'deltaValue' requires two samples to be meaningful and is A 'deltaValue' requires two samples to be meaningful and is
thus not available for testing until the second and subsequent thus not available for testing until the second and subsequent
samples after the object at mteTriggerValueID is first found samples after the object at mteTriggerValueID is first found
to exist. It is the difference between the two samples. For to exist. It is the difference between the two samples. For
unsigned values it is always positive, based on unsigned unsigned values it is always positive, based on unsigned
arithmetic. For signed values it can be positive or negative. arithmetic. For signed values it can be positive or negative.
For SNMP counters to be meaningful they must be sampled as a For SNMP counters to be meaningful they MUST be sampled as a
'deltaValue'. 'deltaValue'.
For 'deltaValue' mteTriggerDeltaTable contains further For 'deltaValue' mteTriggerDeltaTable contains further
parameters. parameters.
If only 'existence' is set in mteTriggerTest this object has If only 'existence' is set in mteTriggerTest this object has
no meaning." no meaning."
DEFVAL { absoluteValue } DEFVAL { absoluteValue }
::= { mteTriggerEntry 5 } ::= { mteTriggerEntry 5 }
skipping to change at page 17, line 14 skipping to change at page 19, line 24
as if there were a separate table entry for each instance as if there were a separate table entry for each instance
that fills the wildcard without having to actually predict that fills the wildcard without having to actually predict
all possible instances ahead of time. all possible instances ahead of time.
Operation of this feature assumes that the local system has a Operation of this feature assumes that the local system has a
list of available contexts against which to apply the list of available contexts against which to apply the
wildcard. If the objects are being read from the local wildcard. If the objects are being read from the local
system, this is clearly the system's own list of contexts. system, this is clearly the system's own list of contexts.
For a remote system a local version of such a list is not For a remote system a local version of such a list is not
defined by any current standard and may not be available, so defined by any current standard and may not be available, so
this function may not be supported." this function MAY not be supported."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerEntry 9 } ::= { mteTriggerEntry 9 }
mteTriggerContextNameWildcard OBJECT-TYPE mteTriggerContextNameWildcard OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Control for whether mteTriggerContextName is to be treated as "Control for whether mteTriggerContextName is to be treated as
fully-specified or wildcarded, with 'true' indicating wildcard." fully-specified or wildcarded, with 'true' indicating wildcard."
skipping to change at page 18, line 8 skipping to change at page 20, line 18
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 may condition. This is not possible in many cases, but 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. This feature allows the MIB to be used in able to do so. This feature allows the MIB to be used in
implementations where such interrupt-driven behavior is implementations where such interrupt-driven behavior is
possible and is not likely to be supported for all MIB objects possible and is not likely to be supported for all MIB objects
even then since such sampling generally has to be tightly even then since such sampling generally has to be tightly
integrated into low-level code. integrated into low-level code.
Systems that can support this should document those cases Systems that can support this SHOULD document those cases
where it can be used. In cases where it can not, setting this where it can be used. In cases where it can not, setting this
object to 0 simply returns a bad value error." object to 0 should be disallowed."
DEFVAL { 600 } DEFVAL { 600 }
::= { mteTriggerEntry 11 } ::= { mteTriggerEntry 11 }
mteTriggerObjectsOwner OBJECT-TYPE mteTriggerObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerObjects, the mteOwner of a group of "To go with mteTriggerObjects, the mteOwner of a group of
objects from mteObjectsTable." objects from mteObjectsTable."
skipping to change at page 20, line 17 skipping to change at page 22, line 27
DESCRIPTION DESCRIPTION
"The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or "The OBJECT IDENTIFIER (OID) of a TimeTicks, TimeStamp, or
DateAndTime object that indicates a discontinuity in the value DateAndTime object that indicates a discontinuity in the value
at 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
is in error, with the error code as from an SNMP request. is in error, with the error code as from an SNMP request.
Bad object identifiers or a mismatch between truncating the Bad object identifiers or a mismatch between truncating the
identifier and the value of mteDeltaDiscontinuityIDWildcard identifier and the value of mteDeltaDiscontinuityIDWildcard
result in operation as one would expect when providing the result in operation as one would expect when providing the
wrong identifier to a Get operation. The Get will fail or get wrong identifier to a Get operation. The Get will fail or get
the wrong object. If the value syntax of those objects is not the wrong object. If the value syntax of those objects is not
skipping to change at page 20, line 40 skipping to change at page 23, line 5
DEFVAL { sysUpTimeInstance } DEFVAL { sysUpTimeInstance }
::= { mteTriggerDeltaEntry 1 } ::= { mteTriggerDeltaEntry 1 }
mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE mteTriggerDeltaDiscontinuityIDWildcard OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Control for whether mteTriggerDeltaDiscontinuityID is to be "Control for whether mteTriggerDeltaDiscontinuityID is to be
treated as fully-specified or wildcarded, with 'true' treated as fully-specified or wildcarded, with 'true'
indicating wildcard." indicating wildcard. Note that the value of this object will
be the same as that of the corresponding instance of
mteTriggerValueIDWildcard when the corresponding
mteTriggerSampleType is 'deltaValue'."
DEFVAL { false } DEFVAL { false }
::= { mteTriggerDeltaEntry 2 } ::= { mteTriggerDeltaEntry 2 }
mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE mteTriggerDeltaDiscontinuityIDType OBJECT-TYPE
SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) } SYNTAX INTEGER { timeTicks(1), timeStamp(2), dateAndTime(3) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value 'timeTicks' indicates the "The value 'timeTicks' indicates the
mteTriggerDeltaDiscontinuityID of this row is of syntax mteTriggerDeltaDiscontinuityID of this row is of syntax
skipping to change at page 22, line 8 skipping to change at page 24, line 22
} }
mteTriggerExistenceTest OBJECT-TYPE mteTriggerExistenceTest OBJECT-TYPE
SYNTAX BITS { present(0), absent(1), changed(2) } SYNTAX BITS { present(0), absent(1), changed(2) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The type of existence test to perform. The trigger fires "The type of existence test to perform. The trigger fires
when the object at mteTriggerValueID is seen to go from when the object at mteTriggerValueID is seen to go from
present to absent, from absent to present, or to have it's present to absent, from absent to present, or to have it's
value changed, depending on which tests are selected. value changed, depending on which tests are selected:
present(0) - when this test is selected, the trigger fires
when the mteTriggerValueID object goes from absent to present.
absent(1) - when this test is selected, the trigger fires
when the mteTriggerValueID object goes from present to absent.
changed(2) - when this test is selected, the trigger fires
the mteTriggerValueID object value changes.
Once the trigger has fired for either presence or absence it Once the trigger has fired for either presence or absence it
will not fire again for that state until the object has been will not fire again for that state until the object has been
to the other state." to the other state."
DEFVAL { { present, absent } } DEFVAL { { present, absent } }
::= { mteTriggerExistenceEntry 1 } ::= { mteTriggerExistenceEntry 1 }
mteTriggerExistenceStartup OBJECT-TYPE mteTriggerExistenceStartup OBJECT-TYPE
SYNTAX BITS { present(0), absent(1), changed(2) } SYNTAX BITS { present(0), absent(1) }
MAX-ACCESS read-write MAX-ACCESS read-write
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' and the test specified by is first set to 'active' and the test specified by
mteTriggerExistenceTest is true. Setting an option causes mteTriggerExistenceTest is true. Setting an option causes
that trigger to fire when its test is true." that trigger to fire when its test is true."
DEFVAL { { present, absent } } DEFVAL { { present, absent } }
::= { mteTriggerExistenceEntry 2 } ::= { mteTriggerExistenceEntry 2 }
skipping to change at page 23, line 15 skipping to change at page 25, line 37
A length of 0 indicates no additional objects." A length of 0 indicates no additional objects."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerExistenceEntry 4 } ::= { mteTriggerExistenceEntry 4 }
mteTriggerExistenceEventOwner OBJECT-TYPE mteTriggerExistenceEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerExistenceEvent, the mteOwner of a group "To go with mteTriggerExistenceEvent, the mteOwner of an event
of objects from mteObjectsTable." entry from the mteEventTable."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerExistenceEntry 5 } ::= { mteTriggerExistenceEntry 5 }
mteTriggerExistenceEvent OBJECT-TYPE mteTriggerExistenceEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is "The mteEventName of the event to invoke when mteTriggerType is
'existence' and this trigger fires. A length of 0 indicates no 'existence' and this trigger fires. A length of 0 indicates no
skipping to change at page 26, line 44 skipping to change at page 29, line 21
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single threshold trigger. Entries "Information about a single threshold trigger. Entries
automatically exist in this table for each mteTriggerEntry automatically exist in this table for each mteTriggerEntry
that has 'threshold' set in mteTriggerTest." that has 'threshold' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName } INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerThresholdTable 1 } ::= { mteTriggerThresholdTable 1 }
MteTriggerThresholdEntry ::= SEQUENCE { MteTriggerThresholdEntry ::= SEQUENCE {
mteTriggerThresholdValue Integer32,
mteTriggerThresholdStartup INTEGER, mteTriggerThresholdStartup INTEGER,
mteTriggerThresholdRising Integer32, mteTriggerThresholdRising Integer32,
mteTriggerThresholdFalling Integer32, mteTriggerThresholdFalling Integer32,
mteTriggerThresholdDeltaRising Integer32,
mteTriggerThresholdDeltaFalling Integer32,
mteTriggerThresholdObjectsOwner SnmpAdminString, mteTriggerThresholdObjectsOwner SnmpAdminString,
mteTriggerThresholdObjects SnmpAdminString, mteTriggerThresholdObjects SnmpAdminString,
mteTriggerThresholdRisingEventOwner SnmpAdminString, mteTriggerThresholdRisingEventOwner SnmpAdminString,
mteTriggerThresholdRisingEvent SnmpAdminString, mteTriggerThresholdRisingEvent SnmpAdminString,
mteTriggerThresholdFallingEventOwner SnmpAdminString, mteTriggerThresholdFallingEventOwner SnmpAdminString,
mteTriggerThresholdFallingEvent SnmpAdminString mteTriggerThresholdFallingEvent SnmpAdminString
mteTriggerThresholdDeltaRisingEventOwner SnmpAdminString,
mteTriggerThresholdDeltaRisingEvent SnmpAdminString,
mteTriggerThresholdDeltaFallingEventOwner SnmpAdminString,
mteTriggerThresholdDeltaFallingEvent SnmpAdminString
} }
mteTriggerThresholdValue OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The value to use for the threshold test."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 1 }
mteTriggerThresholdStartup OBJECT-TYPE mteTriggerThresholdStartup OBJECT-TYPE
SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
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' and a new instance of the object at set to 'active' and a new instance of the object at
mteTriggerValueID is found. If the first sample after this mteTriggerValueID is found. If the first sample after this
instance becomes active is greater than or equal to instance becomes active is greater than or equal to
mteTriggerThresholdRising and mteTriggerThresholdStartup is mteTriggerThresholdRising and mteTriggerThresholdStartup is
equal to 'rising' or 'risingOrFalling', then one equal to 'rising' or 'risingOrFalling', then one
mteTriggerThresholdRisingEvent is triggered for that instance. mteTriggerThresholdRisingEvent is triggered for that instance.
If the first sample after this entry becomes active is less than If the first sample after this entry becomes active is less
or equal to mteTriggerThresholdFalling and than or equal to mteTriggerThresholdFalling and
mteTriggerThresholdStartup is equal to 'falling' or mteTriggerThresholdStartup is equal to 'falling' or
'risingOrFalling', then one mteTriggerThresholdRisingEvent is 'risingOrFalling', then one mteTriggerThresholdRisingEvent is
triggered for that instance." triggered for that instance."
DEFVAL { risingOrFalling } DEFVAL { risingOrFalling }
::= { mteTriggerThresholdEntry 2 } ::= { mteTriggerThresholdEntry 1 }
mteTriggerThresholdRising OBJECT-TYPE mteTriggerThresholdRising OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A threshold value to check against if mteTriggerType is "A threshold value to check against if mteTriggerType is
'threshold'. 'threshold'.
When the current sampled value is greater than or equal to When the current sampled value is greater than or equal to
this threshold, and the value at the last sampling interval this threshold, and the value at the last sampling interval
was less than this threshold, one was less than this threshold, one
mteTriggerThresholdRisingEvent is triggered. That event is mteTriggerThresholdRisingEvent is triggered. That event is
also triggered if the first sample afer this entry bcomes also triggered if the first sample after this entry becomes
active is greater than or equal to this threshold and active is greater than or equal to this threshold and
mteTriggerThresholdStartup is equal to 'rising' or mteTriggerThresholdStartup is equal to 'rising' or
'risingOrFalling'. '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
reaches mteTriggerThresholdFalling." and reaches mteTriggerThresholdFalling."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerThresholdEntry 3 } ::= { mteTriggerThresholdEntry 2 }
mteTriggerThresholdFalling OBJECT-TYPE mteTriggerThresholdFalling OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A threshold value to check against if mteTriggerType is "A threshold value to check against if mteTriggerType is
'threshold'. 'threshold'.
When the current sampled value is less than or equal to this When the current sampled value is less than or equal to this
threshold, and the value at the last sampling interval was threshold, and the value at the last sampling interval was
greater than this threshold, one greater than this threshold, one
mteTriggerThresholdFallingEvent is triggered. That event is mteTriggerThresholdFallingEvent is triggered. That event is
also triggered if the first sample afer this entry bcomes also triggered if the first sample afer this entry bcomes
active is less than or equal to this threshold and active is less than or equal to this threshold and
mteTriggerThresholdStartup is equal to 'falling' or mteTriggerThresholdStartup is equal to 'falling' or
'risingOrFalling'. 'risingOrFalling'.
After a falling event is generated, another such event is not After a falling event is generated, another such event is not
triggered until the sampled value rises above this threshold and triggered until the sampled value rises above this threshold
reaches mteTriggerThresholdRising." and reaches mteTriggerThresholdRising."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 3 }
mteTriggerThresholdDeltaRising OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A threshold value to check against if mteTriggerType is
'threshold'.
When the delta value (difference) between the current sampled
value (value(n)) and the previous sampled value (value(n-1))
is greater than or equal to this threshold,
and the delta value calculated at the last sampling interval
(i.e. value(n-1) - value(n-2)) was less than this threshold,
one mteTriggerThresholdDeltaRisingEvent is triggered. That event is
also triggered if the first delta value calculated after this
entry becomes active, i.e. value(2) - value(1), where value(1)
is the first sample taken of that instance, is greater than or
equal to this threshold.
After a rising event is generated, another such event is not
triggered until the delta value falls below this threshold and
reaches mteTriggerThresholdDeltaFalling."
DEFVAL { 0 } DEFVAL { 0 }
::= { mteTriggerThresholdEntry 4 } ::= { mteTriggerThresholdEntry 4 }
mteTriggerThresholdDeltaFalling OBJECT-TYPE
SYNTAX Integer32
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"A threshold value to check against if mteTriggerType is
'threshold'.
When the delta value (difference) between the current sampled
value (value(n)) and the previous sampled value (value(n-1))
is less than or equal to this threshold,
and the delta value calculated at the last sampling interval
(i.e. value(n-1) - value(n-2)) was greater than this threshold,
one mteTriggerThresholdDeltaFallingEvent is triggered. That event is
also triggered if the first delta value calculated after this
entry becomes active, i.e. value(2) - value(1), where value(1)
is the first sample taken of that instance, is less than or
equal to this threshold.
After a falling event is generated, another such event is not
triggered until the delta value falls below this threshold and
reaches mteTriggerThresholdDeltaRising."
DEFVAL { 0 }
::= { mteTriggerThresholdEntry 5 }
mteTriggerThresholdObjectsOwner OBJECT-TYPE mteTriggerThresholdObjectsOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerThresholdObjects, the mteOwner of a group "To go with mteTriggerThresholdObjects, the mteOwner of a group
of objects from mteObjectsTable." of objects from mteObjectsTable."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 5 } ::= { mteTriggerThresholdEntry 6 }
mteTriggerThresholdObjects OBJECT-TYPE mteTriggerThresholdObjects OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mteObjectsName of a group of objects from "The mteObjectsName of a group of objects from
mteObjectsTable. These objects are to be added to any mteObjectsTable. These objects are to be added to any
Notification resulting from the firing of this trigger for Notification resulting from the firing of this trigger for
this test. this test.
A list of objects may also be added based on the overall A list of objects may also be added based on the overall
trigger, the event or other settings in mteTriggerTest. trigger, the event or other settings in mteTriggerTest.
A length of 0 indicates no additional objects." A length of 0 indicates no additional objects."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 6 } ::= { mteTriggerThresholdEntry 7 }
mteTriggerThresholdRisingEventOwner OBJECT-TYPE mteTriggerThresholdRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerThresholdRisingEvent, the mteOwner of an "To go with mteTriggerThresholdRisingEvent, the mteOwner of an
event entry from mteEventTable." event entry from mteEventTable."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 7 } ::= { mteTriggerThresholdEntry 8 }
mteTriggerThresholdRisingEvent OBJECT-TYPE mteTriggerThresholdRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is "The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on 'threshold' and this trigger fires based on
mteTriggerThresholdRising. A length of 0 indicates no event." mteTriggerThresholdRising. A length of 0 indicates no event."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 8 } ::= { mteTriggerThresholdEntry 9 }
mteTriggerThresholdFallingEventOwner OBJECT-TYPE mteTriggerThresholdFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"To go with mteTriggerThresholdFallingEvent, the mteOwner of an "To go with mteTriggerThresholdFallingEvent, the mteOwner of an
event entry from mteEventTable." event entry from mteEventTable."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 9 } ::= { mteTriggerThresholdEntry 10 }
mteTriggerThresholdFallingEvent OBJECT-TYPE mteTriggerThresholdFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32)) SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is "The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on 'threshold' and this trigger fires based on
mteTriggerThresholdFalling. A length of 0 indicates no event." mteTriggerThresholdFalling. A length of 0 indicates no event."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerThresholdEntry 10 } ::= { mteTriggerThresholdEntry 11 }
mteTriggerThresholdDeltaRisingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdDeltaRisingEvent, the mteOwner of an
event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 12 }
mteTriggerThresholdDeltaRisingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdDeltaRising. A length of 0 indicates no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 13 }
mteTriggerThresholdDeltaFallingEventOwner OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"To go with mteTriggerThresholdDeltaFallingEvent, the mteOwner of an
event entry from mteEventTable."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 14 }
mteTriggerThresholdDeltaFallingEvent OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (0..32))
MAX-ACCESS read-write
STATUS current
DESCRIPTION
"The mteEventName of the event to invoke when mteTriggerType is
'threshold' and this trigger fires based on
mteTriggerThresholdDeltaFalling. A length of 0 indicates no event."
DEFVAL { ''H }
::= { mteTriggerThresholdEntry 15 }
-- --
-- Objects Table -- Objects Table
-- --
mteObjectsTable OBJECT-TYPE mteObjectsTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteObjectsEntry SYNTAX SEQUENCE OF MteObjectsEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
skipping to change at page 31, line 18 skipping to change at page 35, line 37
mteObjectsID OBJECT IDENTIFIER, mteObjectsID OBJECT IDENTIFIER,
mteObjectsIDWildcard TruthValue, mteObjectsIDWildcard TruthValue,
mteObjectsEntryStatus RowStatus mteObjectsEntryStatus RowStatus
} }
mteObjectsName OBJECT-TYPE mteObjectsName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..32)) SYNTAX SnmpAdminString (SIZE (1..32))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for a group of "A locally-unique, administratively assigned name for a group
objects." of objects."
::= { mteObjectsEntry 1 } ::= { mteObjectsEntry 1 }
mteObjectsIndex OBJECT-TYPE mteObjectsIndex OBJECT-TYPE
SYNTAX Unsigned32 (1..4294967295) SYNTAX Unsigned32 (1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"An arbitrary small integer for the purpose of identifying "An arbitrary small integer for the purpose of identifying
individual objects within a mteObjectsName group. individual objects within a mteObjectsName group.
skipping to change at page 32, line 39 skipping to change at page 37, line 14
fully-specified or wildcarded, with 'true' indicating wildcard." fully-specified or wildcarded, with 'true' indicating wildcard."
DEFVAL { false } DEFVAL { false }
::= { mteObjectsEntry 4 } ::= { mteObjectsEntry 4 }
mteObjectsEntryStatus OBJECT-TYPE mteObjectsEntryStatus 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."
::= { mteObjectsEntry 5 } ::= { mteObjectsEntry 5 }
-- --
-- Event Section -- Event Section
-- --
-- Counters -- Counters
mteEventFailures OBJECT-TYPE mteEventFailures OBJECT-TYPE
skipping to change at page 35, line 6 skipping to change at page 39, line 27
triggered." triggered."
DEFVAL { false } DEFVAL { false }
::= { mteEventEntry 4 } ::= { mteEventEntry 4 }
mteEventEntryStatus OBJECT-TYPE mteEventEntryStatus 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 5 } ::= { mteEventEntry 5 }
-- --
-- Event Notification Table -- Event Notification Table
-- --
mteEventNotificationTable OBJECT-TYPE mteEventNotificationTable OBJECT-TYPE
SYNTAX SEQUENCE OF MteEventNotificationEntry SYNTAX SEQUENCE OF MteEventNotificationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A table of management event action notification information." "A table of information about notifications to be sent as a
consequence of management events."
::= { mteEvent 3 } ::= { mteEvent 3 }
mteEventNotificationEntry OBJECT-TYPE mteEventNotificationEntry OBJECT-TYPE
SYNTAX MteEventNotificationEntry SYNTAX MteEventNotificationEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single event's notification. Entries "Information about a single event's notification. Entries
automatically exist in this this table for each mteTriggerEntry automatically exist in this this table for each mteEventEntry
that has 'notification' set in mteEventAction." that has 'notification' set in mteEventActions."
INDEX { mteOwner, IMPLIED mteTriggerName } INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventNotificationTable 1 } ::= { mteEventNotificationTable 1 }
MteEventNotificationEntry ::= SEQUENCE { MteEventNotificationEntry ::= SEQUENCE {
mteEventNotification OBJECT IDENTIFIER, mteEventNotification OBJECT IDENTIFIER,
mteEventNotificationObjectsOwner SnmpAdminString, mteEventNotificationObjectsOwner SnmpAdminString,
mteEventNotificationObjects SnmpAdminString mteEventNotificationObjects SnmpAdminString
} }
mteEventNotification OBJECT-TYPE mteEventNotification OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
skipping to change at page 37, line 5 skipping to change at page 41, line 27
DESCRIPTION DESCRIPTION
"A table of management event action information." "A table of management event action information."
::= { mteEvent 4 } ::= { mteEvent 4 }
mteEventSetEntry OBJECT-TYPE mteEventSetEntry OBJECT-TYPE
SYNTAX MteEventSetEntry SYNTAX MteEventSetEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single event's set option. Entries "Information about a single event's set option. Entries
automatically exist in this this table for each mteTriggerEntry automatically exist in this this table for each mteEventEntry
that has 'set' set in mteEventAction." that has 'set' set in mteEventActions."
INDEX { mteOwner, IMPLIED mteTriggerName } INDEX { mteOwner, IMPLIED mteEventName }
::= { mteEventSetTable 1 } ::= { mteEventSetTable 1 }
MteEventSetEntry ::= SEQUENCE { MteEventSetEntry ::= SEQUENCE {
mteEventSetObject OBJECT IDENTIFIER, mteEventSetObject OBJECT IDENTIFIER,
mteEventSetObjectWildcard TruthValue, mteEventSetObjectWildcard TruthValue,
mteEventSetValue Integer32, mteEventSetValue Integer32,
mteEventSetTargetTag SnmpTagValue, mteEventSetTargetTag SnmpTagValue,
mteEventSetContextName SnmpAdminString, mteEventSetContextName SnmpAdminString,
mteEventSetContextNameWildcard TruthValue mteEventSetContextNameWildcard TruthValue
} }
skipping to change at page 38, line 36 skipping to change at page 43, line 14
mteEventSetTargetTag OBJECT-TYPE mteEventSetTargetTag OBJECT-TYPE
SYNTAX SnmpTagValue SYNTAX SnmpTagValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The tag for the target(s) at which to set the object at "The tag for the target(s) at which to set the object at
mteEventSetObject to mteEventSetValue if mteEventActions mteEventSetObject to mteEventSetValue if mteEventActions
has 'set' set. has 'set' set.
Systems limited to self management may not accept a non-zero Systems limited to self management MAY not accept a non-zero
length for the value of this object. length for the value of this object.
A length of 0 indicates the local system. In this case, A length of 0 indicates the local system. In this case,
access to the objects indicated by mteEventSetObject is under access to the objects indicated by mteEventSetObject is under
the security credentials of the requester that set the security credentials of the requester that set
mteTriggerEntryStatus to 'active'. Those credentials are the mteTriggerEntryStatus to 'active'. Those credentials are the
input parameters for isAccessAllowed from the Architecture for input parameters for isAccessAllowed from the Architecture for
Describing SNMP Management Frameworks. Describing SNMP Management Frameworks.
Otherwise access rights are checked according to the security Otherwise access rights are checked according to the security
skipping to change at page 40, line 27 skipping to change at page 44, line 47
DESCRIPTION DESCRIPTION
"The SNMP Target MIB's snmpTargetAddrName related to the "The SNMP Target MIB's snmpTargetAddrName related to the
notification." notification."
::= { dismanEventMIBNotificationObjects 2 } ::= { dismanEventMIBNotificationObjects 2 }
mteHotContextName OBJECT-TYPE mteHotContextName OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The context name related to the notification. This must be as "The context name related to the notification. This MUST be as
fully-qualified as possible, including filling in wildcard fully-qualified as possible, including filling in wildcard
information determined in processing." information determined in processing."
::= { dismanEventMIBNotificationObjects 3 } ::= { dismanEventMIBNotificationObjects 3 }
mteHotOID OBJECT-TYPE mteHotOID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object identifier of the destination object related to the "The object identifier of the destination object related to the
notification. This must be as fully-qualified as possible, notification. This MUST be as fully-qualified as possible,
inluding filling in wildcard informaation determined in inluding filling in wildcard information determined in
processing. processing.
For a trigger-related notification this is from For a trigger-related notification this is from
mteTriggerValueID. mteTriggerValueID.
For a set failure this is from mteEventSetObject." For a set failure this is from mteEventSetObject."
::= { dismanEventMIBNotificationObjects 4 } ::= { dismanEventMIBNotificationObjects 4 }
mteHotValue OBJECT-TYPE mteHotValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
skipping to change at page 43, line 11 skipping to change at page 47, line 33
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 dismanEventMIBCompliances OBJECT IDENTIFIER ::= { dismanEventMIBConformance 1 }
1 } dismanEventMIBGroups OBJECT IDENTIFIER ::= { dismanEventMIBConformance 2 }
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 43, line 37 skipping to change at page 48, line 13
dismanEventObjectsGroup, dismanEventObjectsGroup,
dismanEventEventGroup, dismanEventEventGroup,
dismanEventNotificationObjectGroup, dismanEventNotificationObjectGroup,
dismanEventNotificationGroup dismanEventNotificationGroup
} }
OBJECT mteTriggerTargetTag OBJECT mteTriggerTargetTag
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, thus limiting "Write access is not required, thus limiting
monitoring to the local system or preconfigured monitoring to the local system or pre-configured
remote systems." remote systems."
OBJECT mteEventSetTargetTag OBJECT mteEventSetTargetTag
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, thus limiting "Write access is not required, thus limiting
setting to the local system or preconfigured setting to the local system or pre-configured
remote systems." remote systems."
OBJECT mteTriggerValueIDWildcard OBJECT mteTriggerValueIDWildcard
MIN-ACCESS read-only MIN-ACCESS read-only
DESCRIPTION DESCRIPTION
"Write access is not required, thus allowing "Write access is not required, thus allowing
the system not to implement wildcarding." the system not to implement wildcarding."
OBJECT mteTriggerContextNameWildcard OBJECT mteTriggerContextNameWildcard
MIN-ACCESS read-only MIN-ACCESS read-only
skipping to change at page 45, line 28 skipping to change at page 50, line 4
mteTriggerDeltaDiscontinuityID, mteTriggerDeltaDiscontinuityID,
mteTriggerDeltaDiscontinuityIDWildcard, mteTriggerDeltaDiscontinuityIDWildcard,
mteTriggerDeltaDiscontinuityIDType, mteTriggerDeltaDiscontinuityIDType,
mteTriggerExistenceTest, mteTriggerExistenceTest,
mteTriggerExistenceStartup, mteTriggerExistenceStartup,
mteTriggerExistenceObjectsOwner, mteTriggerExistenceObjectsOwner,
mteTriggerExistenceObjects, mteTriggerExistenceObjects,
mteTriggerExistenceEventOwner, mteTriggerExistenceEventOwner,
mteTriggerExistenceEvent, mteTriggerExistenceEvent,
mteTriggerBooleanComparison, mteTriggerBooleanComparison,
mteTriggerBooleanValue, mteTriggerBooleanValue,
mteTriggerBooleanStartup, mteTriggerBooleanStartup,
mteTriggerBooleanObjectsOwner, mteTriggerBooleanObjectsOwner,
mteTriggerBooleanObjects, mteTriggerBooleanObjects,
mteTriggerBooleanEventOwner, mteTriggerBooleanEventOwner,
mteTriggerBooleanEvent, mteTriggerBooleanEvent,
mteTriggerThresholdValue,
mteTriggerThresholdStartup, mteTriggerThresholdStartup,
mteTriggerThresholdObjectsOwner, mteTriggerThresholdObjectsOwner,
mteTriggerThresholdObjects, mteTriggerThresholdObjects,
mteTriggerThresholdRising, mteTriggerThresholdRising,
mteTriggerThresholdFalling, mteTriggerThresholdFalling,
mteTriggerThresholdDeltaRising,
mteTriggerThresholdDeltaFalling,
mteTriggerThresholdRisingEventOwner, mteTriggerThresholdRisingEventOwner,
mteTriggerThresholdRisingEvent, mteTriggerThresholdRisingEvent,
mteTriggerThresholdFallingEventOwner, mteTriggerThresholdFallingEventOwner,
mteTriggerThresholdFallingEvent mteTriggerThresholdFallingEvent
mteTriggerThresholdDeltaRisingEventOwner,
mteTriggerThresholdDeltaRisingEvent,
mteTriggerThresholdDeltaFallingEventOwner,
mteTriggerThresholdDeltaFallingEvent
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Event triggers." "Event triggers."
::= { dismanEventMIBGroups 2 } ::= { dismanEventMIBGroups 2 }
dismanEventObjectsGroup OBJECT-GROUP dismanEventObjectsGroup OBJECT-GROUP
OBJECTS { OBJECTS {
mteObjectsID, mteObjectsID,
mteObjectsIDWildcard, mteObjectsIDWildcard,
skipping to change at page 54, line 12 skipping to change at page 59, line 12
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
FITNESS FOR A PARTICULAR PURPOSE. FITNESS FOR A PARTICULAR PURPOSE.
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 ....................................................... 7
7 Security ........................................................ 6 7 Security ........................................................ 8
8 Definitions ..................................................... 8 8 Definitions ..................................................... 10
9 Intellectual Property ........................................... 48 9 Intellectual Property ........................................... 53
10 Acknowledgements ............................................... 49 10 Acknowledgements ............................................... 54
11 References ..................................................... 50 11 References ..................................................... 55
12 Security Considerations ........................................ 52 12 Security Considerations ........................................ 57
13 Author's Address ............................................... 52 13 Author's Address ............................................... 57
14 Editor's Address ............................................... 52 14 Editor's Address ............................................... 57
15 Full Copyright Statement ....................................... 53 15 Full Copyright Statement ....................................... 58
 End of changes. 

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