Draft Manager to Manager MIB for SMP Jul 92 Manager to Manager Management Information Base for the Simple Management Protocol (SMP) Framework Sat Jul 4 17:76:07 1992 Jeffrey D. Case SNMP Research, Inc. University of Tennessee, Knoxville case@cs.utk.edu Keith McCloghrie Hughes LAN Systems kzm@hls.com Marshall T. Rose Dover Beach Consulting, Inc. mrose@dbc.mtview.ca.us Steven L. Waldbusser Carnegie Mellon University waldbusser@andrew.cmu.edu 1. Status of this Memo This document is an Internet Draft. Internet Drafts are working documents of the Internet Engineering Task Force (IETF), its Areas, and its Working Groups. Note that other groups may also distribute working documents as Internet Drafts. Internet Drafts are draft documents valid for a maximum of six months. Internet Drafts may be updated, replaced, or obsoleted by other documents at any time. It is not appropriate to use Internet Drafts as reference material or to Expires January 4, 1993 [Page 1] Draft Manager to Manager MIB for SMP Jul 92 cite them other than as a "working draft" or "work in progress". Please check the 1id-abstracts.txt listing contained in the internet-drafts Shadow Directories on nic.ddn.mil, nnsc.nsf.net, nic.nordu.net, ftp.nisc.sri.com, or munnari.oz.au to learn the current status of any Internet Draft. Please send comments to the SNMP discussion group, . Expires January 4, 1993 [Page 2] Draft Manager to Manager MIB for SMP Jul 92 2. Introduction A network management system contains: several (potentially many) entities, each with management instrumentation termed an agent; at least one management station; and, a management protocol, which is used to convey management information between the agents and management stations, as well as between the management stations. Operations of the protocol are carried out under an administrative framework which defines both authentication and authorization policies. Network management stations execute management applications which monitor and control network elements. Network elements are devices such as hosts, routers, terminal servers, etc., which are monitored and controlled through access to their management information. Management information is viewed as a collection of managed objects, residing in a virtual information store, termed the Management Information Base (MIB). Collections of related objects are defined in MIB modules. These modules are written using a subset of OSI's Abstract Syntax Notation One (ASN.1) [1], termed the Structure of Management Information (SMI) [2]. The management protocol, termed the Simple Management Protocol (SMP) [3], provides for the exchange of messages which convey management information between the agents and the management stations, including between management stations. It is the purpose of this document to define managed objects which describe the behavior of an SMP protocol entity acting in both a manager role and an agent role. Expires January 4, 1993 [Page 3] Draft Manager to Manager MIB for SMP Jul 92 3. Overview The purpose of this MIB is to provide the means for coordination between multiple management stations. That is, the means by which the controlling and monitoring functions of network management can be distributed amongst multiple management stations. Such distribution facilitates the scaling of network management solutions based on the SMP to meet the needs of very large networks, or of networks composed of multiple interconnected administrations. Specifically, this MIB provides the means for one management station to request management services from another management station. 3.1. A SMP Entity Acting in a Dual Role A management station providing services to other management station(s), is an SMP entity which acts in the dual role of both manager and agent; the requests for service are received through acting in an agent role (with respect to the managed objects defined in this MIB), and the requested services are performed through acting in a manager role. 3.2. Alarms, Events, and Notifications In this initial version, this MIB defines the concepts of "alarms", "events", and "notifications". Each alarm is a specific condition detected through the periodic (at a configured sampling interval) monitoring of the value of a specific management information variable. An example of an alarm condition is when the monitored variable falls outside a configured range. Each alarm condition triggers an event, and each event can cause (one or more) notifications to be reported to other management stations using the Inform-Request PDU. Specifically, this MIB defines three MIB tables and a number of scalar objects. The three tables are: the Alarm Table, the Event Table, and the Notification Table. Expires January 4, 1993 [Page 4] Draft Manager to Manager MIB for SMP Jul 92 3.3. Access Control The Administrative framework for SMP [4] includes an access control model, which must not be subverted by allowing access to management information variables via the Alarm table. That is, access to a monitored variable via the Alarm table must be controlled according to the identity of the management station accessing the particular entry in the Alarm table. An entry in the Alarm table provides the means to configure the sampling of the value of a MIB variable in a particular MIB view. The particular MIB view is that associated with a party [4], called the sampling destination party, which can be any party accessible from the SMP entity acting in a dual role, either local or remote. The sampling is done by (conceptually or actually) issuing a SMP request to retrieve the variable's value. This request is authenticated according to a source party, called the sampling source party which must be local to the SMP entity acting in a dual role, and directed to the sampling destination party. Thus, to provide the required access control, the initial MIB view assigned, by convention, to parties on SMP entities that implement the smpAlarmTable, must include the component: viewSubtree = { smpAlarm } viewStatus = { excluded } viewMask = { ''h } Then, the MIB view of a party, partyRequestDest, accessible by a requesting management station, can be configured to include specific Alarm table entries -- the ones associated with those sampling destination parties to which the requesting management station has access. In particular, to provide a partyRequestDest with access to the sampling destination party partySampleDest, the following family of view subtrees would be included for partyRequestDest on the SMP entity acting in a dual role: { smpAlarmEntry WILDCARD partySampleDest } Which would be configured in the party MIB [5] as: viewParty = { partyRequestDest } Expires January 4, 1993 [Page 5] Draft Manager to Manager MIB for SMP Jul 92 viewSubtree = { smpAlarmEntry 1 partySampleDest } viewStatus = { included } viewMask = { 'FFBF'h } -- specifies wildcard for column Expires January 4, 1993 [Page 6] Draft Manager to Manager MIB for SMP Jul 92 4. Definitions SMP-M2M-MIB DEFINITIONS ::= BEGIN IMPORTS OBJECT-TYPE, OBJECT-GROUP, MODULE-COMPLIANCE, ObjectName, smpObjects FROM SMP-SMI DisplayString, RowStatus FROM SMP-TC smp-compliance FROM SMP-MIB Party, partyIdentity FROM RFC1353-MIB; -- compliance statement for this MIB smp-m2m-mib-compliance MODULE-COMPLIANCE MODULE -- this module MANDATORY-GROUPS { smpAlarm, smpEvent } ::= { smp-compliance 2 } Expires January 4, 1993 [Page 7] Draft Manager to Manager MIB for SMP Jul 92 -- the alarm group smpAlarm OBJECT-GROUP OBJECTS { smpAlarmNextIndex, smpAlarmIndex, smpAlarmSourcePartyID, smpAlarmVariable, smpAlarmInterval, smpAlarmSampleType, smpAlarmValue, smpAlarmStartupAlarm, smpAlarmRisingThreshold, smpAlarmFallingThreshold, smpAlarmRisingEventIndex, smpAlarmFallingEventIndex, smpAlarmUnavailableEventIndex, smpAlarmStatus } DESCRIPTION "A collection of objects allowing the description and configuration of threshold alarms from an SMP entity acting in a dual role." ::= { smpObjects 7 } -- This Alarm mechanism periodically takes statistical samples -- from variables available via SMP and compares them to -- thresholds that have been configured. The alarm table -- stores configuration entries that each define a variable, -- polling period, and threshold parameters. If a sample is -- found to cross the threshold values, an event is generated. -- Only variables that resolve to an ASN.1 primitive type of -- INTEGER (Integer32, Counter32, Gauge32, TimeTicks, or -- Counter64) may be monitored in this way. -- -- This function has a hysteresis mechanism to limit the -- generation of events. This mechanism generates one event -- as a threshold is crossed in the appropriate direction. No -- more events are generated for that threshold until the -- opposite threshold is crossed. -- -- In the case of sampling a deltaValue, an entity may -- implement this mechanism with more precision if it takes a -- delta sample twice per period, each time comparing the sum -- of the latest two samples to the threshold. This allows -- the detection of threshold crossings that span the sampling -- boundary. Note that this does not require any special -- configuration of the threshold value. It is suggested that -- entities implement this more precise algorithm. -- smpAlarmNextIndex OBJECT-TYPE Expires January 4, 1993 [Page 8] Draft Manager to Manager MIB for SMP Jul 92 SYNTAX INTEGER (1..65535) MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The index number of the next appropriate unassigned entry in the smpAlarmTable. A management station should create new entries in the smpAlarmTable using this algorithm: first, issue a management protocol retrieval operation to determine the value of smpAlarmNextIndex; and, second, issue a management protocol set operation to create an instance of the smpAlarmStatus object setting its value to `underCreation(1)'. If this latter operation succeeds, then the management station may continue modifying the instances corresponding to the newly created conceptual row, without fear of collision with other management stations." ::= { smpAlarm 1 } smpAlarmTable OBJECT-TYPE SYNTAX SEQUENCE OF SmpAlarmEntry MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of smpAlarm entries." ::= { smpAlarm 2 } smpAlarmEntry OBJECT-TYPE SYNTAX SmpAlarmEntry MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of parameters that set up a periodic sampling query to check for alarm conditions. The partyIdentity included in the INDEX clause is the sampling destination party, i.e., the party to which the sampling queries are directed." INDEX { partyIdentity, smpAlarmIndex } ::= { smpAlarmTable 1 } SmpAlarmEntry ::= SEQUENCE { smpAlarmIndex INTEGER, smpAlarmSourcePartyID Party, Expires January 4, 1993 [Page 9] Draft Manager to Manager MIB for SMP Jul 92 smpAlarmVariable ObjectName, smpAlarmInterval Integer32, smpAlarmSampleType INTEGER, smpAlarmValue Integer32, smpAlarmStartupAlarm INTEGER, smpAlarmRisingThreshold Integer32, smpAlarmFallingThreshold Integer32, smpAlarmRisingEventIndex INTEGER, smpAlarmFallingEventIndex INTEGER, smpAlarmUnavailableEventIndex INTEGER, smpAlarmStatus RowStatus } smpAlarmIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "An index that uniquely identifies an entry in the smpAlarm table for a particular sampling destination party. Each such entry defines a diagnostic sample at a particular interval for a variable in the particular party's MIB view." ::= { smpAlarmEntry 1 } smpAlarmSourcePartyID OBJECT-TYPE SYNTAX Party MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The sampling source party, i.e., the source party to be used to query the variable's value. This party must be local to the SMP entity acting in a dual role." ::= { smpAlarmEntry 2 } smpAlarmVariable OBJECT-TYPE SYNTAX ObjectName MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The object identifier of the particular variable to be sampled. Only variables that resolve to an ASN.1 primitive type of INTEGER (Integer32, Counter32, Gauge32, TimeTicks, or Counter64) may Expires January 4, 1993 [Page 10] Draft Manager to Manager MIB for SMP Jul 92 be sampled. If it is detected by an error response of authorizationError, noSuchObject, or noSuchInstance that the variable name of an established smpAlarmEntry is no longer available to the sampling destination party, a single objectUnavailableAlarm event is generated and the status of this smpAlarmEntry is changed to `underDestruction(2)'. Likewise, if the syntax of the variable retrieved by the query is not Integer32, Counter32, Gauge32, TimeTicks, or Counter64, the same actions will be taken. If the SMP entity acting in a dual role detects that the sampled value can not be obtained due to lack of response to management queries, it should set the status of this smpAlarmEntry to `underDestruction(2)' if it is determined that further communication is not possible; or delete the associated smpAlarmValue instance (but not the entire conceptual row) and continue to attempt to sample the variable and recreate the associated smpAlarmValue instance should communication be reestablished. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 3 } smpAlarmInterval OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The interval in seconds over which the data is sampled and compared with the rising and falling thresholds. When setting this object and the sampling type is `deltaValue(2)', care should be taken to ensure that the change during this interval of the variable being sampled will not Expires January 4, 1993 [Page 11] Draft Manager to Manager MIB for SMP Jul 92 exceed the (-2^31...2^31-1) range of the smpAlarmValue. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 4 } smpAlarmSampleType OBJECT-TYPE SYNTAX INTEGER { absoluteValue(1), deltaValue(2) } MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The method of sampling the selected variable and calculating the value to be compared against the thresholds. If the value of this object is `absoluteValue(1)', the value of the selected variable at the end of the sampling interval will be compared directly with both the smpAlarmRisingThreshold and the smpAlarmFallingThreshold values. If the value of this object is `deltaValue(2)', the value of the selected variable at the end of the sampling interval will be subtracted from its value at the end of the previous sampling interval, and the difference compared with both the smpAlarmRisingThreshold and the smpAlarmFallingThreshold values. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." DEFVAL { deltaValue } ::= { smpAlarmEntry 5 } smpAlarmValue OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only Expires January 4, 1993 [Page 12] Draft Manager to Manager MIB for SMP Jul 92 STATUS mandatory DESCRIPTION "The value of the statistic during the last sampling period. The value during the current sampling period is not made available until the period is completed. If the value of the statistic does not fit in the signed 32 bit representation of this object, it should be truncated in an implementation specific manner. Note that if the associated smpAlarmSampleType is set to `deltaValue(2)', the value of this object is the difference in the sampled variable since the last sample. This object will be created by the SMP entity acting in a dual role when this entry is set to `active(4)', and the first sampling period has completed. It may be created and deleted at other times by the SMP entity acting in a dual role when the sampled value can not be obtained, as specified in the smpAlarmVariable object." ::= { smpAlarmEntry 6 } smpAlarmStartupAlarm OBJECT-TYPE SYNTAX INTEGER { risingAlarm(1), fallingAlarm(2), risingOrFallingAlarm(3) } MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The alarm that may be sent when this entry is first set to `active(4)'. If the first sample after this entry becomes active is greater than or equal to the risingThreshold and smpAlarmStartupAlarm is equal to `risingAlarm(1)' or `risingOrFallingAlarm(3)', then a single rising alarm will be generated. If the first sample after this entry becomes active is less than or equal to the fallingThreshold and smpAlarmStartupAlarm is equal to `fallingAlarm(2)' or `risingOrFallingAlarm(3)', then a single falling alarm will be generated. Note that an Expires January 4, 1993 [Page 13] Draft Manager to Manager MIB for SMP Jul 92 objectUnavailableAlarm is sent upon startup whenever it is applicable, independent of the setting of smpAlarmStartupAlarm. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." DEFVAL { risingOrFallingAlarm } ::= { smpAlarmEntry 7 } smpAlarmRisingThreshold OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS mandatory DESCRIPTION "A threshold for the sampled statistic. When the current sampled value is greater than or equal to this threshold, and the value at the last sampling interval was less than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes active is greater than or equal to this threshold and the associated smpAlarmStartupAlarm is equal to `risingAlarm(1)' or `risingOrFallingAlarm(3)'. After a rising event is generated, another such event will not be generated until the sampled value falls below this threshold and reaches the smpAlarmFallingThreshold. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 8 } smpAlarmFallingThreshold OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS mandatory DESCRIPTION Expires January 4, 1993 [Page 14] Draft Manager to Manager MIB for SMP Jul 92 "A threshold for the sampled statistic. When the current sampled value is less than or equal to this threshold, and the value at the last sampling interval was greater than this threshold, a single event will be generated. A single event will also be generated if the first sample after this entry becomes active is less than or equal to this threshold and the associated smpAlarmStartupAlarm is equal to `fallingAlarm(2)' or `risingOrFallingAlarm(3)'. After a falling event is generated, another such event will not be generated until the sampled value rises above this threshold and reaches the smpAlarmRisingThreshold. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 9 } smpAlarmRisingEventIndex OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The index of the smpEventEntry that is used when a rising threshold is crossed. The smpEventEntry identified by a particular value of this index is the same as identified by the same value of the smpEventIndex object. If there is no corresponding entry in the smpEventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid smpEventIndex. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 10 } Expires January 4, 1993 [Page 15] Draft Manager to Manager MIB for SMP Jul 92 smpAlarmFallingEventIndex OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The index of the smpEventEntry that is used when a falling threshold is crossed. The smpEventEntry identified by a particular value of this index is the same as identified by the same value of the smpEventIndex object. If there is no corresponding entry in the smpEventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid smpEventIndex. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 11 } smpAlarmUnavailableEventIndex OBJECT-TYPE SYNTAX INTEGER (0..65535) MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The index of the smpEventEntry that is used when a variable becomes unavailable. The smpEventEntry identified by a particular value of this index is the same as identified by the same value of the smpEventIndex object. If there is no corresponding entry in the smpEventTable, then no association exists. In particular, if this value is zero, no associated event will be generated, as zero is not a valid smpEventIndex. An attempt to modify this object will fail with an `inconsistentValue' error if the associated smpAlarmStatus object would be equal to `active(4)' both before and after the modification attempt." ::= { smpAlarmEntry 12 } smpAlarmStatus OBJECT-TYPE Expires January 4, 1993 [Page 16] Draft Manager to Manager MIB for SMP Jul 92 SYNTAX RowStatus MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The status of this smpAlarm entry. This object may not be set to `active(4)' unless the following columnar objects exist in this row: smpAlarmSourcePartyID, smpAlarmVariable, smpAlarmInterval, smpAlarmSampleType, smpAlarmStartupAlarm, smpAlarmRisingThreshold, smpAlarmFallingThreshold, smpAlarmRisingEventIndex, smpAlarmFallingEventIndex, and smpAlarmUnavailableEventIndex." ::= { smpAlarmEntry 13 } Expires January 4, 1993 [Page 17] Draft Manager to Manager MIB for SMP Jul 92 -- alarm-related traps smpAlarmEvents OBJECT IDENTIFIER ::= { smpAlarm 3 } risingAlarm TRAP-DEFINITION OBJECTS { smpAlarmVariable, smpAlarmSampleType, smpAlarmValue, smpAlarmRisingThreshold } DESCRIPTION "An event that is generated when an alarm entry crosses its rising threshold. The instances of those objects contained within the varbind list are those of the alarm entry which generated this event." ::= { smpAlarmEvents 1 } fallingAlarm TRAP-DEFINITION OBJECTS { smpAlarmVariable, smpAlarmSampleType, smpAlarmValue, smpAlarmFallingThreshold } DESCRIPTION "An event that is generated when an alarm entry crosses its falling threshold. The instances of those objects contained within the varbind list are those of the alarm entry which generated this event." ::= { smpAlarmEvents 2 } objectUnavailableAlarm TRAP-DEFINITION OBJECTS { smpAlarmVariable } DESCRIPTION "An event that is generated when a variable monitored by an alarm entry becomes unavailable. The instance of smpAlarmVariable contained within the varbind list is the one associated with the alarm entry which generated this event." ::= { smpAlarmEvents 3 } Expires January 4, 1993 [Page 18] Draft Manager to Manager MIB for SMP Jul 92 -- the event group smpEvent OBJECT-GROUP OBJECTS { smpEventNextIndex, smpEventIndex, smpEventID, smpEventDescription, smpEventEvents, smpEventLastTimeSent, smpEventStatus, smpEventNotifyMinInterval, smpEventNotifyMaxRetransmissions, smpEventNotifySrcParty, smpEventNotifyIntervalRequested, smpEventNotifyRetransmissionsRequested, smpEventNotifyLifetime, smpEventNotifyStatus } DESCRIPTION "A collection of objects allowing the description and configuration of events from an SMP entity acting in a dual role." ::= { smpObjects 8 } -- The smpEvent table defines the set of events generated on a SMP -- entity acting in a dual role. Each entry in the smpEventTable -- associates an event type with the notification method and -- associated parameters. Some smpEvent entries are fired by an -- associated condition in the smpAlarmTable. Others are -- fired on behalf of conditions defined in the TRAP-DEFINITION -- macro. The smpNotificationTable defines notifications that -- should occur when an associated event is fired. smpEventNextIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The index number of the next appropriate unassigned entry in the smpEventTable. A management station should create new entries in the smpEventTable using this algorithm: first, issue a management protocol retrieval operation to determine the value of smpEventNextIndex; and, second, issue a management protocol set operation to create an instance of the smpEventStatus object setting its value to `underCreation(1)'. If this latter operation succeeds, then the management station may continue modifying the instances corresponding to the newly created conceptual row, without fear of collision with other management Expires January 4, 1993 [Page 19] Draft Manager to Manager MIB for SMP Jul 92 stations." ::= { smpEvent 1 } smpEventTable OBJECT-TYPE SYNTAX SEQUENCE OF SmpEventEntry MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of events." ::= { smpEvent 2 } smpEventEntry OBJECT-TYPE SYNTAX SmpEventEntry MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "A set of parameters that describe an event that is generated when certain conditions are met." INDEX { smpEventIndex } ::= { smpEventTable 1 } SmpEventEntry ::= SEQUENCE { smpEventIndex INTEGER, smpEventID OBJECT IDENTIFIER, smpEventDescription DisplayString, smpEventEvents Counter32, smpEventLastTimeSent TimeStamp, smpEventStatus RowStatus } smpEventIndex OBJECT-TYPE SYNTAX INTEGER (1..65535) MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "An index that uniquely identifies an entry in the smpEvent table. Each such entry defines an event generated when the appropriate conditions occur." ::= { smpEventEntry 1 } smpEventID OBJECT-TYPE SYNTAX OBJECT IDENTIFIER MAX-ACCESS read-create STATUS mandatory DESCRIPTION Expires January 4, 1993 [Page 20] Draft Manager to Manager MIB for SMP Jul 92 "The authoritative identification of the event type generated by this entry. This variable occurs as the first varbind of an InformRequest- PDU. If this OBJECT IDENTIFIER maps to a TRAP- DEFINITION the sender will place the objects listed in the TRAP-DEFINITION in the varbind list." ::= { smpEventEntry 2 } smpEventDescription OBJECT-TYPE SYNTAX DisplayString (SIZE (0..127)) MAX-ACCESS read-create STATUS mandatory DESCRIPTION "A comment describing this smpEvent entry." ::= { smpEventEntry 3 } smpEventEvents OBJECT-TYPE SYNTAX Counter32 MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The number of events caused by event generators associated with this smpEvent entry." ::= { smpEventEntry 4 } smpEventLastTimeSent OBJECT-TYPE SYNTAX TimeStamp MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The value of sysUpTime at the time this smpEvent entry last generated an event. If this entry has not generated any events, this value will be zero." DEFVAL { 0 } ::= { smpEventEntry 5 } smpEventStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The status of this smpEvent entry. This object may not be set to `active(4)' unless the following Expires January 4, 1993 [Page 21] Draft Manager to Manager MIB for SMP Jul 92 columnar objects exist in this row: smpEventID, smpEventDescription, smpEventEvents, and smpEventLastTimeSent. Setting an instance of this object to the value any/all entries in the smpEventTable, and the smpEventNotifyTable which reference the corresponding smpEventEntry." ::= { smpEventEntry 6 } -- The smpEventNotifyTable is used to configure the -- destination and type of notifications sent by an SMP -- entity acting in a manager role when a particular event -- is triggered. smpEventNotifyMinInterval OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The minimum interval that the SMP entity acting in a dual role will wait before retransmitting an InformRequest-PDU. This object specifies the minimal value supported by the SMP entity acting in a dual role, based on resource or implementation constraints. For a particular entry in the smpEventNotifyTable, if the associated smpEventNotifyIntervalRequested variable is greater than this object, the smpEventNotifyIntervalRequested value shall be used as the minimum interval for retransmissions of InformRequest-PDUs sent on behalf of that entry." ::= { smpEvent 3 } smpEventNotifyMaxRetransmissions OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-only STATUS mandatory DESCRIPTION "The maximum number of time that the SMP entity acting in a dual role will retransmit an InformRequest-PDU. This object specifies the Expires January 4, 1993 [Page 22] Draft Manager to Manager MIB for SMP Jul 92 maximal value supported by the SMP entity acting in a dual role, based on resource or implementation constraints. For a particular entry in the smpEventNotifyTable, if the associated smpEventNotifyRetransmissionsRequested variable is less than this object, the smpEventNotifyRetransmissionsRequested value shall be used as the retransmission count for InformRequest-PDUs sent on behalf of that entry." ::= { smpEvent 4 } smpEventNotifyTable OBJECT-TYPE SYNTAX SEQUENCE OF SmpEventNotifyEntry MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "A list of protocol configuration entries for event notifications from this entity." ::= { smpEvent 5 } smpEventNotifyEntry OBJECT-TYPE SYNTAX SmpEventNotifyEntry MAX-ACCESS not-accessible STATUS mandatory DESCRIPTION "A set of parameters that describe the type and destination of InformRequest-PDUs sent for a particular event. The smpEventIndex in this entry's INDEX clause identifies the smpEventEntry which, when triggered, will generate a notification as configured in this entry. The partyIdentity in this entry's INDEX clause identifies the destination party to which a notification will be sent." INDEX { smpEventIndex, partyIdentity } ::= { smpEventNotifyTable 1 } SmpEventNotifyEntry ::= SEQUENCE { smpEventNotifySrcParty Party, smpEventNotifyIntervalRequested Integer32, smpEventNotifyRetransmissionsRequested Integer32, smpEventNotifyLifetime Integer32, smpEventNotifyStatus RowStatus Expires January 4, 1993 [Page 23] Draft Manager to Manager MIB for SMP Jul 92 } smpEventNotifySrcParty OBJECT-TYPE SYNTAX Party MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The source party to be used to send the InformRequest-PDU." ::= { smpEventNotifyEntry 1 } smpEventNotifyIntervalRequested OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The requested interval for retransmission of Inform PDUs generated on the behalf of this entry. This variable will be the actual interval used unless the smpEventNotifyMinInterval is greater than this object, in which case the interval shall be equal to smpEventNotifyMinInterval." DEFVAL { 30 } ::= { smpEventNotifyEntry 2 } smpEventNotifyRetransmissionsRequested OBJECT-TYPE SYNTAX Integer32 MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The requested number of retransmissions of an InformRequest-PDU generated on behalf of this entry. This variable will be the actual number of retransmissions used unless the smpEventNotifyMaxRetransmissions is less than this object, in which case the retransmission count shall be equal to smpEventNotifyMaxRetransmissions." DEFVAL { 5 } ::= { smpEventNotifyEntry 3 } Expires January 4, 1993 [Page 24] Draft Manager to Manager MIB for SMP Jul 92 smpEventNotifyLifetime OBJECT-TYPE SYNTAX Integer32 UNITS "seconds" MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The number of seconds this entry shall live until it is put into the underDestruction state. This value shall count down to zero, at which time the status of this entry will be changed to underDestruction. Any management station that is using this entry must periodically refresh this value to ensure the continued delivery of events." DEFVAL { 86400 } ::= { smpEventNotifyEntry 4 } smpEventNotifyStatus OBJECT-TYPE SYNTAX RowStatus MAX-ACCESS read-create STATUS mandatory DESCRIPTION "The state of this smpEventNotifyEntry. This object may not be set to `active(4)' unless the following columnar objects exist in this row: smpEventNotifySrcParty, smpEventNotifyIntervalRequested, smpEventNotifyRetransmissionsRequested, and smpEventNotifyLifetime." ::= { smpEventNotifyEntry 5 } END Expires January 4, 1993 [Page 25] Draft Manager to Manager MIB for SMP Jul 92 5. References [1] Information processing systems - Open Systems Interconnection - Specification of Abstract Syntax Notation One (ASN.1), International Organization for Standardization. International Standard 8824, (December, 1987). [2] J.D. Case, K. McCloghrie, M.T. Rose, S.L. Waldbusser, Structure of Management Information for the Simple Management Protocol (SMP) Framework, (July, 1992). [3] J.D. Case, K. McCloghrie, M.T. Rose, S.L. Waldbusser, Protocol Operations for the Simple Management Protocol (SMP) Framework, (July, 1992). [4] J.R. Davin, J.M. Galvin, K. McCloghrie, SNMP Administrative Model. Request for Comments 1351, (July, 1992). [5] K. McCloghrie, J.R. Davin, J.M. Galvin, Definitions of Managed Objects for Administration of SNMP Parties. Request for Comments 1353, (July, 1992). Expires January 4, 1993 [Page 26] Draft Manager to Manager MIB for SMP Jul 92 Table of Contents 1 Status of this Memo ................................... 1 2 Introduction .......................................... 3 3 Overview .............................................. 4 3.1 A SMP Entity Acting in a Dual Role .................. 4 3.2 Alarms, Events, and Notifications ................... 4 3.3 Access Control ...................................... 5 4 Definitions ........................................... 7 3.1 The Alarm Group ..................................... 8 3.1.2 Alarm-Related Traps ............................... 18 3.2 The Event Group ..................................... 19 5 References ............................................ 26 Expires January 4, 1993 [Page 27]