draft-ietf-disman-event-mib-07.txt   draft-ietf-disman-event-mib-08.txt 
Event MIB Event MIB
25 June 1999 22 October 1999
draft-ietf-disman-event-mib-07.txt draft-ietf-disman-event-mib-08.txt
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
bstewart@cisco.com
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance with all This document is an Internet-Draft and is in full conformance with all
provisions of Section 10 of RFC2026. provisions of Section 10 of RFC2026.
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. http://www.ietf.org/shadow.html.Distribution of this document is unlimited.
Distribution of this document is unlimited. Please send comments to the Please send comments to the
Distributed Management Working Group, <disman@nexen.com>. Distributed Management Working Group, <disman@nexen.com>.
Copyright Notice Copyright Notice
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Information This memo defines a portion of the Management Information Base (MIB) for
Base (MIB) for use with network management protocols in the Internet use with network management protocols in the Internet community. In
community. In particular, it describes managed objects used for particular, it describes managed objects used for managing monitoring of
managing monitoring of MIB objects and taking action through events. MIB objects and taking action through events.
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 4, line 16 skipping to change at page 4, line 16
With network sizes well beyond the ability of people to management them With network sizes well beyond the ability of people to management 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 The MIB is intended to suit either a relatively powerful manager or mid-
mid-level manager, as well as a somewhat more limited self-managing level manager, as well as a somewhat more limited self-managing system.
system.
4. Relationship to Other MIBs 4. Relationship to Other MIBs
The Event MIB is based on extensive experience with the RMON MIB 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 its alarm and event groups and is intended as a
replacement for those groups. The Event MIB calls "triggers" what the replacement for those groups. The Event MIB calls "triggers" what the
RMON MIB called "alarms," but the concepts are the same. Event MIB RMON MIB called "alarms," but the concepts are the same. Event MIB
triggers maintain the RMON handling of thresholds and add the concept of triggers maintain the RMON handling of thresholds and add the concept of
booleans. Event MIB events maintain the RMON concept of sending an SNMP 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 notification in response to a trigger and add the concept of setting a
skipping to change at page 8, line 11 skipping to change at page 8, line 11
vacmViewTreeFamilySubtree including the owner index portion, and vacmViewTreeFamilySubtree including the owner index portion, and
vacmViewTreeFamilyMask "wildcarding" the column subidentifier. More vacmViewTreeFamilyMask "wildcarding" the column subidentifier. 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,
experimental, Integer32, Unsigned32, Integer32, Unsigned32,
NOTIFICATION-TYPE, Counter32, NOTIFICATION-TYPE, Counter32,
Gauge32 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 "9906241700Z" LAST-UPDATED "9910220000Z"
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Bob Stewart 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: bstewart@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."
::= { experimental xx } -- Revision History
REVISION "9910220000Z" -- 22 October 1999
DESCRIPTION "This is the initial version of this MIB.
Published as RFC xxxxx"
::= { mib-2 xx } -- final assignment by IANA at publication time
dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 } dismanEventMIBObjects OBJECT IDENTIFIER ::= { dismanEventMIB 1 }
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 }
zeroDotZero OBJECT IDENTIFIER ::= { 0 0 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
FailureReason ::= TEXTUAL-CONVENTION FailureReason ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reasons for failures in an attempt to perform a management "Reasons for failures in an attempt to perform a management
request. request.
skipping to change at page 21, line 36 skipping to change at page 21, line 36
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Information about a single existence trigger. Entries "Information about a single existence trigger. Entries
automatically exist in this this table for each mteTriggerEntry automatically exist in this this table for each mteTriggerEntry
that has 'existence' set in mteTriggerTest." that has 'existence' set in mteTriggerTest."
INDEX { mteOwner, IMPLIED mteTriggerName } INDEX { mteOwner, IMPLIED mteTriggerName }
::= { mteTriggerExistenceTable 1 } ::= { mteTriggerExistenceTable 1 }
MteTriggerExistenceEntry ::= SEQUENCE { MteTriggerExistenceEntry ::= SEQUENCE {
mteTriggerExistenceTest INTEGER, mteTriggerExistenceTest BITS,
mteTriggerExistenceStartup TruthValue, mteTriggerExistenceStartup BITS,
mteTriggerExistenceObjectsOwner SnmpAdminString, mteTriggerExistenceObjectsOwner SnmpAdminString,
mteTriggerExistenceObjects SnmpAdminString, mteTriggerExistenceObjects SnmpAdminString,
mteTriggerExistenceEventOwner SnmpAdminString, mteTriggerExistenceEventOwner SnmpAdminString,
mteTriggerExistenceEvent SnmpAdminString mteTriggerExistenceEvent SnmpAdminString
} }
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
skipping to change at page 34, line 31 skipping to change at page 34, line 31
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The actions to perform when this event occurs. "The actions to perform when this event occurs.
For 'notification', Traps and/or Informs are sent according For 'notification', Traps and/or Informs are sent according
to the configuration in the SNMP Notification MIB. to the configuration in the SNMP Notification MIB.
For 'set', an SNMP Set operation is performed according to For 'set', an SNMP Set operation is performed according to
control values in this entry." control values in this entry."
DEFVAL { { } } -- No bits set. DEFVAL { '0'H } -- No bits set.
::= { mteEventEntry 3 } ::= { mteEventEntry 3 }
mteEventEnabled OBJECT-TYPE mteEventEnabled OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A control to allow an event to be configured but not used. "A control to allow an event to be configured but not used.
When the value is 'false' the event does not execute even if When the value is 'false' the event does not execute even if
triggered." triggered."
skipping to change at page 49, line 5 skipping to change at page 48, line 21
might not be available; neither does it represent that it has made any might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards- procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of related documentation can be found in BCP-11. Copies of claims of
rights made available for publication and any assurances of licenses to rights made available for publication and any assurances of licenses to
be made available, or the result of an attempt made to obtain a general be made available, or the result of an attempt made to obtain a general
license or permission for the use of such proprietary rights by license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the implementors or users of this specification can be obtained from the
IETF Secretariat. IETF Secretariat.
The IETF invites any interested party to bring to its attention any
copyrights, patents or patent applications, or other proprietary rights
which may cover technology that may be required to practice this
standard. Please address the information to the IETF Executive
Director.
10. Acknowledgements 10. Acknowledgements
This MIB contains considerable contributions from the RMON MIB, the This MIB contains considerable contributions from the RMON MIB, the
Distributed Management Design Team (Andy Bierman, Maria Greene, Bob Distributed Management Design Team (Andy Bierman, Maria Greene, Bob
Stewart, and Steve Waldbusser), the Distributed Management Working Stewart, and Steve Waldbusser), the Distributed Management Working
Group, and colleagues at Cisco. Group, and colleagues at Cisco.
11. References 11. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture
skipping to change at page 52, line 18 skipping to change at page 52, line 18
DESCRIPTION clauses of relevant objects. DESCRIPTION clauses of relevant objects.
13. Author's Address 13. Author's Address
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive 170 West Tasman Drive
San Jose, CA 95134-1706 San Jose, CA 95134-1706
U.S.A. U.S.A.
Phone: +1 408 526 4527 14. Editor's Address
Email: bstewart@cisco.com
14. Full Copyright Statement Ramanathan Kavasseri
Cisco Systems, Inc.
170 West Tasman Drive
San Jose, CA 95134-1706
U.S.A.
Phone: +1 408 527 2446
Email: ramk@cisco.com
15. Full Copyright Statement
Copyright (C) The Internet Society (1999). All Rights Reserved. Copyright (C) The Internet Society (1999). All Rights Reserved.
This document and translations of it may be copied and furnished to This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind, distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included provided that the above copyright notice and this paragraph are included
on all such copies and derivative works. However, this document itself on all such copies and derivative works. However, this document itself
may not be modified in any way, such as by removing the copyright notice may not be modified in any way, such as by removing the copyright notice
skipping to change at page 54, line 20 skipping to change at page 54, line 20
4 Relationship to Other MIBs ...................................... 4 4 Relationship to Other MIBs ...................................... 4
5 MIB Sections .................................................... 4 5 MIB Sections .................................................... 4
6 Operation ....................................................... 5 6 Operation ....................................................... 5
7 Security ........................................................ 6 7 Security ........................................................ 6
8 Definitions ..................................................... 8 8 Definitions ..................................................... 8
9 Intellectual Property ........................................... 48 9 Intellectual Property ........................................... 48
10 Acknowledgements ............................................... 49 10 Acknowledgements ............................................... 49
11 References ..................................................... 50 11 References ..................................................... 50
12 Security Considerations ........................................ 52 12 Security Considerations ........................................ 52
13 Author's Address ............................................... 52 13 Author's Address ............................................... 52
14 Full Copyright Statement ....................................... 53 14 Editor's Address ............................................... 52
15 Full Copyright Statement ....................................... 53
 End of changes. 

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