draft-ietf-disman-event-mib-04.txt   draft-ietf-disman-event-mib-05.txt 
Event MIB Event MIB
5 August 1998 7 October 1998
draft-ietf-disman-event-mib-04.txt draft-ietf-disman-event-mib-05.txt
Bob Stewart Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
bstewart@cisco.com bstewart@cisco.com
Status of this Memo Status of this Memo
This document is an Internet-Draft. Internet-Drafts are working This document is an Internet-Draft. Internet-Drafts are working
documents of the Internet Engineering Task Force (IETF), its areas, and documents of the Internet Engineering Task Force (IETF), its areas, and
its working groups. Note that other groups may also distribute working its working groups. Note that other groups may also distribute working
skipping to change at page 2, line 12 skipping to change at page 2, line 12
Copyright (C) The Internet Society (1998). All Rights Reserved. Copyright (C) The Internet Society (1998). All Rights Reserved.
1. Abstract 1. Abstract
This memo defines an experimental portion of the Management Information This memo defines an experimental portion of the Management Information
Base (MIB) for use with network management protocols in the Internet Base (MIB) for use with network management protocols in the Internet
community. In particular, it describes managed objects used for community. In particular, it describes managed objects used for
managing monitoring of MIB objects and taking action through events. managing monitoring of MIB objects and taking action through events.
The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT",
"SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this
document are to be interpreted as described in RFC 2119.
2. The SNMP Management Framework 2. The SNMP Management Framework
The SNMP Management Framework presently consists of five major The SNMP Management Framework presently consists of five major
components: components:
o An overall architecture, described in RFC 2271 [1]. o An overall architecture, described in RFC 2271 [1].
o Mechanisms for describing and naming objects and events for the o Mechanisms for describing and naming objects and events for the
purpose of management. The first version of this Structure of purpose of management. The first version of this Structure of
Management Information (SMI) is called SMIv1 and described in Management Information (SMI) is called SMIv1 and described in
skipping to change at page 7, line 20 skipping to change at page 7, line 20
MODULE-IDENTITY, OBJECT-TYPE, MODULE-IDENTITY, OBJECT-TYPE,
experimental, Integer32, Unsigned32 experimental, Integer32, Unsigned32
NOTIFICATION-TYPE FROM SNMPv2-SMI NOTIFICATION-TYPE FROM SNMPv2-SMI
TEXTUAL-CONVENTION, RowStatus, TEXTUAL-CONVENTION, RowStatus,
TimeStamp, DisplayString FROM SNMPv2-TC TimeStamp, DisplayString FROM SNMPv2-TC
MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF
SnmpTagValue FROM SNMP-TARGET-MIB SnmpTagValue FROM SNMP-TARGET-MIB
SnmpAdminString FROM SNMP-FRAMEWORK-MIB; SnmpAdminString FROM SNMP-FRAMEWORK-MIB;
eventMIB MODULE-IDENTITY eventMIB MODULE-IDENTITY
LAST-UPDATED "9808051700Z" LAST-UPDATED "9810071700Z"
ORGANIZATION "IETF Distributed Management Working Group" ORGANIZATION "IETF Distributed Management Working Group"
CONTACT-INFO "Bob Stewart CONTACT-INFO "Bob Stewart
Cisco Systems, Inc. Cisco Systems, Inc.
170 West Tasman Drive, 170 West Tasman Drive,
San Jose CA 95134-1706. San Jose CA 95134-1706.
Phone: +1 408 526 4527 Phone: +1 408 526 4527
Email: bstewart@cisco.com" Email: bstewart@cisco.com"
DESCRIPTION DESCRIPTION
"The MIB module for defining event triggers and actions "The MIB module for defining event triggers and actions
for network management purposes." for network management purposes."
skipping to change at page 7, line 45 skipping to change at page 7, line 45
mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 } mteTrigger OBJECT IDENTIFIER ::= { eventMIBObjects 1 }
mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 } mteEvent OBJECT IDENTIFIER ::= { eventMIBObjects 2 }
-- --
-- Textual Conventions -- Textual Conventions
-- --
FailureReason ::= TEXTUAL-CONVENTION FailureReason ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Reasons for failures in an attempt to send a management message. "Reasons for failures in an attempt to send a management
message.
The first group of errors, numbered less than 100, are copied The first group of errors, numbered less than 100, are copied
directly from SNMP protocol operations and are intended to carry directly from SNMP protocol operations and are intended to carry
exactly the meanings defined for the protocol as returned in exactly the meanings defined for the protocol as returned in
an SNMP response. Those numbered 100 or greater are related an SNMP response. Those numbered 100 or greater are related
to problems in sending the request." to problems in sending the request."
SYNTAX INTEGER { tooBig(1), SYNTAX INTEGER { tooBig(1),
noSuchName(2), noSuchName(2),
badValue(3), badValue(3),
readOnly(4), readOnly(4),
skipping to change at page 10, line 5 skipping to change at page 10, line 6
mteTriggerFallingEvent SnmpAdminString, mteTriggerFallingEvent SnmpAdminString,
mteTriggerObjects SnmpAdminString, mteTriggerObjects SnmpAdminString,
mteTriggerStatus RowStatus mteTriggerStatus RowStatus
} }
mteTriggerName OBJECT-TYPE mteTriggerName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..64)) SYNTAX SnmpAdminString (SIZE (1..64))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for the trigger." "A locally-unique, administratively assigned name for the
trigger."
::= { mteTriggerEntry 1 } ::= { mteTriggerEntry 1 }
mteTriggerComment OBJECT-TYPE mteTriggerComment OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A description of the trigger's function and use." "A description of the trigger's function and use."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteTriggerEntry 2 } ::= { mteTriggerEntry 2 }
mteTriggerTest OBJECT-TYPE mteTriggerTest OBJECT-TYPE
SYNTAX INTEGER { boolean(1), threshold(2) } SYNTAX INTEGER { 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 all tests, "The type of trigger test to perform. For all tests,
mteTriggerValue must evaluate to an integer. mteTriggerValue must evaluate to an integer.
For 'boolean', a value of 0 is false. A non-zero value For 'boolean', a value of 0 is false. A non-zero value is true
is true and fires the trigger. The trigger will not fire and fires the trigger. The trigger will not fire again until
again until the value has become false and come back to the value has become false and come back to true.
true.
For 'threshold' it works as described below for For 'threshold' it works as described below for
mteTriggerThresholdStartup, mteTriggerRisingThreshold, and mteTriggerThresholdStartup, mteTriggerRisingThreshold, and
mteTriggerFallingThreshold." mteTriggerFallingThreshold."
DEFVAL { boolean } DEFVAL { boolean }
::= { mteTriggerEntry 3 } ::= { mteTriggerEntry 3 }
mteTriggerValueID OBJECT-TYPE mteTriggerValueID OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
skipping to change at page 12, line 45 skipping to change at page 12, line 45
DEFVAL { 600 } DEFVAL { 600 }
::= { mteTriggerEntry 9 } ::= { mteTriggerEntry 9 }
mteTriggerBooleanStartup OBJECT-TYPE mteTriggerBooleanStartup OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Control for whether an event may be triggered when this entry "Control for whether an event may be triggered when this entry
is first set to 'active'. If the value mteTriggerBooleanStartup is first set to 'active'. If the value mteTriggerBooleanStartup
is 'true' and the first sample after this entry becomes active is is 'true' and the first sample after this entry becomes active
true then one mteTriggerEvent is triggered. is true then one mteTriggerEvent is triggered.
If mteTriggerType is not 'boolean', this object is not If mteTriggerType is not 'boolean', this object is not
instantiated." instantiated."
DEFVAL { true } DEFVAL { true }
::= { mteTriggerEntry 10 } ::= { mteTriggerEntry 10 }
mteTriggerThresholdStartup OBJECT-TYPE mteTriggerThresholdStartup OBJECT-TYPE
SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) } SYNTAX INTEGER { rising(1), falling(2), risingOrFalling(3) }
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
skipping to change at page 16, line 43 skipping to change at page 16, line 43
mteTriggerObjectID Integer32, mteTriggerObjectID Integer32,
mteTriggerObjectIDWildcard TruthValue, mteTriggerObjectIDWildcard TruthValue,
mteTriggerObjectStatus RowStatus mteTriggerObjectStatus RowStatus
} }
mteTriggerObjectName OBJECT-TYPE mteTriggerObjectName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..64)) SYNTAX SnmpAdminString (SIZE (1..64))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for a group "A locally-unique, administratively assigned name for a group of
of objects to associate with a trigger." objects to associate with a trigger."
::= { mteTriggerObjectEntry 1 } ::= { mteTriggerObjectEntry 1 }
mteTriggerObjectIndex OBJECT-TYPE mteTriggerObjectIndex 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 with a mteTriggerObjectName group." individual objects with a mteTriggerObjectName group."
::= { mteTriggerObjectEntry 2 } ::= { mteTriggerObjectEntry 2 }
skipping to change at page 19, line 19 skipping to change at page 19, line 19
mteEventSetContextName SnmpAdminString, mteEventSetContextName SnmpAdminString,
mteEventSetContextNameWildcard TruthValue, mteEventSetContextNameWildcard TruthValue,
mteEventStatus RowStatus mteEventStatus RowStatus
} }
mteEventName OBJECT-TYPE mteEventName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE (1..64)) SYNTAX SnmpAdminString (SIZE (1..64))
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A locally-unique, administratively assigned name for the event." "A locally-unique, administratively assigned name for the
event."
::= { mteEventCreationEntry 1 } ::= { mteEventCreationEntry 1 }
mteEventComment OBJECT-TYPE mteEventComment OBJECT-TYPE
SYNTAX DisplayString SYNTAX DisplayString
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"A description of the event's function and use." "A description of the event's function and use."
DEFVAL { ''H } DEFVAL { ''H }
::= { mteEventEntry 2 } ::= { mteEventEntry 2 }
skipping to change at page 20, line 37 skipping to change at page 20, line 38
::= { mteEventEntry 5 } ::= { mteEventEntry 5 }
mteEventSetObject OBJECT-TYPE mteEventSetObject OBJECT-TYPE
SYNTAX OBJECT IDENTIFIER SYNTAX OBJECT IDENTIFIER
MAX-ACCESS read-create MAX-ACCESS read-create
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The object identifier from the MIB object to set if "The object identifier from the MIB object to set if
mteEventActions has 'set' set. mteEventActions has 'set' set.
This object identifier may be wildcarded by leaving sub-identifiers This object identifier may be wildcarded by leaving
off the end, in which case nteEventSetObjectWildCard must be sub-identifiers off the end, in which case
'true'. nteEventSetObjectWildCard must be 'true'.
If mteEventSetObject is wildcarded the instance used to set it If mteEventSetObject is wildcarded the instance used to set it
is the same as the instance for the value of mteTriggerValueID is the same as the instance for the value of mteTriggerValueID
that triggered the event." that triggered the event."
If 'set' is not set, this object is not instantiated." If 'set' is not set, this object is not instantiated."
DEFVAL { 0 0 } DEFVAL { 0 0 }
::= { mteEventEntry 6 } ::= { mteEventEntry 6 }
mteEventSetObjectWildcard OBJECT-TYPE mteEventSetObjectWildcard OBJECT-TYPE
skipping to change at page 23, line 9 skipping to change at page 23, line 9
delete it." delete it."
DEFVAL { createAndWait } DEFVAL { createAndWait }
::= { mteEventEntry 12 } ::= { mteEventEntry 12 }
-- --
-- Notifications -- Notifications
-- --
eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 } eventMIBNotificationPrefix OBJECT IDENTIFIER ::= { eventMIB 2 }
eventMIBNotifications OBJECT IDENTIFIER ::= { eventMIBNotificationPrefix 0 } eventMIBNotifications OBJECT IDENTIFIER ::=
{ eventMIBNotificationPrefix 0 }
eventMIBNotificationObjectss OBJECT IDENTIFIER eventMIBNotificationObjectss OBJECT IDENTIFIER
::= { eventMIBNotificationPrefix 1 } ::= { eventMIBNotificationPrefix 1 }
-- --
-- Notification Objects -- Notification Objects
-- --
mteHotTrigger OBJECT-TYPE mteHotTrigger OBJECT-TYPE
SYNTAX SnmpAdminString SYNTAX SnmpAdminString
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
skipping to change at page 23, line 40 skipping to change at page 23, line 41
"The SNMP Target MIB's snmpTargetAddrName related to the "The SNMP Target MIB's snmpTargetAddrName related to the
notification. notification.
::= { mteTrigger 2 } ::= { mteTrigger 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, inluding filling in wildcard fully-qualified as possible, including filling in wildcard
informaation determined in processing." informaation determined in processing."
::= { mteTrigger 3 } ::= { mteTrigger 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 processing. inluding filling in wildcard informaation determined in
processing.
For a trigger-related notification this is from mteTriggerValueID. For a trigger-related notification this is from
mteTriggerValueID.
For a set failure this is from mteEventSetObject." For a set failure this is from mteEventSetObject."
::= { mteTrigger 3 } ::= { mteTrigger 3 }
mterHotValue OBJECT-TYPE mterHotValue OBJECT-TYPE
SYNTAX Integer32 SYNTAX Integer32
MAX-ACCESS accessible-for-notify MAX-ACCESS accessible-for-notify
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The value of the object at mteTriggerValueID when a "The value of the object at mteTriggerValueID when a
skipping to change at page 30, line 5 skipping to change at page 30, line 5
mteTriggerFailureAlarm, mteTriggerFailureAlarm,
mteEventSetFailureAlarm mteEventSetFailureAlarm
} }
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"Notifications." "Notifications."
::= { eventMIBGroups 4 } ::= { eventMIBGroups 4 }
END END
9. Acknowledgements 9. Intellectual Property
The IETF takes no position regarding the validity or scope of any
intellectual property or other rights that might be claimed to pertain
to the implementation or use of the technology described in this
document or the extent to which any license under such rights might or
might not be available; neither does it represent that it has made any
effort to identify any such rights. Information on the IETF's
procedures with respect to rights in standards-track and standards-
related documentation can be found in BCP-11. Copies of claims of
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
license or permission for the use of such proprietary rights by
implementors or users of this specification can be obtained from the
IETF Secretariat.
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), and colleagues at Cisco. Stewart, and Steve Waldbusser), and colleagues at Cisco.
10. References 11. References
[1] Harrington, D., Presuhn, R., and B. Wijnen, "An Architecture for [1] Harrington, D., Presuhn, R. and B. Wijnen, "An Architecture for
Describing SNMP Management Frameworks", RFC 2271, Cabletron Describing SNMP Management Frameworks", RFC 2271, Cabletron
Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research, Systems, Inc., BMC Software, Inc., IBM T. J. Watson Research,
January 1998 January 1998.
[2] Rose, M., and K. McCloghrie, "Structure and Identification of [2] Rose, M. and K. McCloghrie, "Structure and Identification of
Management Information for TCP/IP-based Internets", RFC 1155, Management Information for TCP/IP-based Internets", RFC 1155,
Performance Systems International, Hughes LAN Systems, May 1990 Performance Systems International, Hughes LAN Systems, May 1990.
[3] Rose, M., and K. McCloghrie, "Concise MIB Definitions", RFC 1212, [3] Rose, M. and K. McCloghrie, "Concise MIB Definitions", RFC 1212,
Performance Systems International, Hughes LAN Systems, March 1991 Performance Systems International, Hughes LAN Systems, March 1991.
[4] M. Rose, "A Convention for Defining Traps for use with the SNMP", [4] M. Rose, "A Convention for Defining Traps for use with the SNMP",
RFC 1215, Performance Systems International, March 1991 RFC 1215, Performance Systems International, March 1991.
[5] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Structure [5] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Structure of
of Management Information for Version 2 of the Simple Network Management Information for Version 2 of the Simple Network
Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco Management Protocol (SNMPv2)", RFC 1902, SNMP Research,Inc., Cisco
Systems, Inc., Dover Beach Consulting, Inc., International Network Systems, Inc., Dover Beach Consulting, Inc., International Network
Services, January 1996. Services, January 1996.
[6] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Textual [6] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Textual
Conventions for Version 2 of the Simple Network Management Protocol Conventions for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1903, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services, Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[7] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Conformance [7] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Conformance
Statements for Version 2 of the Simple Network Management Protocol Statements for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1904, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services, Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[8] Case, J., Fedor, M., Schoffstall, M., and J. Davin, "Simple Network [8] Case, J., Fedor, M., Schoffstall, M. and J. Davin, "Simple Network
Management Protocol", RFC 1157, SNMP Research, Performance Systems Management Protocol", RFC 1157, SNMP Research, Performance Systems
International, Performance Systems International, MIT Laboratory International, Performance Systems International, MIT Laboratory
for Computer Science, May 1990. for Computer Science, May 1990.
[9] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, [9] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Introduction
"Introduction to Community-based SNMPv2", RFC 1901, SNMP Research, to Community-based SNMPv2", RFC 1901, SNMP Research, Inc., Cisco
Inc., Cisco Systems, Inc., Dover Beach Consulting, Inc., Systems, Inc., Dover Beach Consulting, Inc., International Network
International Network Services, January 1996. Services, January 1996.
[10] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Transport [10] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Transport
Mappings for Version 2 of the Simple Network Management Protocol Mappings for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1906, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services, Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[11] Case, J., Harrington D., Presuhn R., and B. Wijnen, "Message [11] Case, J., Harrington D., Presuhn R. and B. Wijnen, "Message
Processing and Dispatching for the Simple Network Management Processing and Dispatching for the Simple Network Management
Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems, Protocol (SNMP)", RFC 2272, SNMP Research, Inc., Cabletron Systems,
Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998. Inc., BMC Software, Inc., IBM T. J. Watson Research, January 1998.
[12] Blumenthal, U., and B. Wijnen, "User-based Security Model (USM) for [12] Blumenthal, U. and B. Wijnen, "User-based Security Model (USM) for
version 3 of the Simple Network Management Protocol (SNMPv3)", RFC version 3 of the Simple Network Management Protocol (SNMPv3)", RFC
2274, IBM T. J. Watson Research, January 1998. 2274, IBM T. J. Watson Research, January 1998.
[13] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, "Protocol [13] Case, J., McCloghrie, K., Rose, M. and S. Waldbusser, "Protocol
Operations for Version 2 of the Simple Network Management Protocol Operations for Version 2 of the Simple Network Management Protocol
(SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc., (SNMPv2)", RFC 1905, SNMP Research, Inc., Cisco Systems, Inc.,
Dover Beach Consulting, Inc., International Network Services, Dover Beach Consulting, Inc., International Network Services,
January 1996. January 1996.
[14] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 Applications", RFC [14] Levi, D., Meyer, P. and B. Stewart, "SNMPv3 Applications", RFC
2273, SNMP Research, Inc., Secure Computing Corporation, Cisco 2273, SNMP Research, Inc., Secure Computing Corporation, Cisco
Systems, January 1998 Systems, January 1998.
[15] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based Access [15] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based Access
Control Model (VACM) for the Simple Network Management Protocol Control Model (VACM) for the Simple Network Management Protocol
(SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc., (SNMP)", RFC 2275, IBM T. J. Watson Research, BMC Software, Inc.,
Cisco Systems, Inc., January 1998 Cisco Systems, Inc., January 1998.
[16] Waldbusser, S., "Remote Network Monitoring Management Information [16] Waldbusser, S., "Remote Network Monitoring Management Information
Base", RFC 1757, International Network Services, February 1995 Base", RFC 1757, International Network Services, February 1995.
[17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to- [17] Case, J., McCloghrie, K., Rose, M., Waldbusser, S., "Manager-to-
Manager Management Information Base", RFC 1451, SNMP Research, Manager Management Information Base", RFC 1451, SNMP Research,
Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc., Inc., Cisco SYSTEMS< Inc., Dover Beach Consulting, Inc.,
International Network Services, April 1993 International Network Services, April 1993.
[18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc., [18] Stewart, B., "Expression MIB", RFC ????, Cisco Systems, Inc.,
?Month? 1998 ?Month? 1998.
[19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc., [19] Stewart, B., "Notification Log MIB", RFC ????, Cisco Systems, Inc.,
?Month? 1998 ?Month? 1998.
11. Security Considerations 12. Security Considerations
Security issues are discussed in the Overview section and in the Security issues are discussed in the Overview section and in the
DESCRIPTION clauses of relevant objects. DESCRIPTION clauses of relevant objects.
12. 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.
Phone: 408-526-4527 Phone: +1 408 526 4527
Email: bstewart@cisco.com Email: bstewart@cisco.com
14. Full Copyright Statement
Copyright (C) The Internet Society (1998). All Rights Reserved.
This document and translations of it may be copied and furnished to
others, and derivative works that comment on or otherwise explain it or
assist in its implementation may be prepared, copied, published and
distributed, in whole or in part, without restriction of any kind,
provided that the above copyright notice and this paragraph are included
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
or references to the Internet Society or other Internet organizations,
except as needed for the purpose of developing Internet standards in
which case the procedures for copyrights defined in the Internet
Standards process must be followed, or as required to translate it into
languages other than English.
The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an "AS
IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK
FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT
LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT
INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR
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 ....................................................... 5
7 Security ........................................................ 5 7 Security ........................................................ 5
8 Definitions ..................................................... 7 8 Definitions ..................................................... 7
9 Acknowledgements ................................................ 30 9 Intellectual Property ........................................... 30
10 References ..................................................... 31 10 Acknowledgements ............................................... 31
11 Security Considerations ........................................ 33 11 References ..................................................... 32
12 Author's Address ............................................... 33 12 Security Considerations ........................................ 34
13 Author's Address ............................................... 34
14 Full Copyright Statement ....................................... 35
 End of changes. 

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