draft-ietf-disman-snmp-alarm-mib-00.txt   draft-ietf-disman-snmp-alarm-mib-01.txt 
Disman Working Group David T. Perkins Disman Working Group David T. Perkins
Internet Draft SNMPinfo Internet Draft SNMPinfo
Expires: August 2001 February 21, 2001 Expires: August 2001 March 2, 2001
SNMP Alarms and MIB Module SNMP Alarms and MIB Module
draft-ietf-disman-snmp-alarm-mib-00.txt draft-ietf-disman-snmp-alarm-mib-01.txt
Status of this Memo Status of this Memo
This document is an Internet-Draft and is in full conformance This document is an Internet-Draft and is in full conformance
with all provisions of Section 10 of RFC2026. with all provisions of Section 10 of RFC2026.
Internet-Drafts are working documents of the Internet Engineering Internet-Drafts are working documents of the Internet Engineering
Task Force (IETF), its areas, and its working groups. Note that Task Force (IETF), its areas, and its working groups. Note that
other groups may also distribute working documents as other groups may also distribute working documents as
Internet-Drafts. Internet-Drafts.
skipping to change at page 1, line 43 skipping to change at page 1, line 43
This document defines the model for alarms in the SNMP framework and This document defines the model for alarms in the SNMP framework and
defines a Management Information Base (MIB) module that defines a defines a Management Information Base (MIB) module that defines a
list of outstanding alarms and log of alarms that have occurred and list of outstanding alarms and log of alarms that have occurred and
have been cleared. have been cleared.
Table of Contents Table of Contents
1. The SNMP Management Framework ..................................3 1. The SNMP Management Framework ..................................3
2. Introduction ...................................................4 2. Introduction ...................................................4
3. Exception Reporting Framework ..................................4 3. Exception Reporting Framework ..................................4
1.1.Terminology....................................................4 3.1 Terminology ..................................................4
4. MIB Module Overview ............................................4
5. Definitions ....................................................5 3.2 Alarm Definitions ............................................4
6. Examples ......................................................26 4. MIB Module Overview ............................................6
7. Security Considerations .......................................26 5. Definitions ....................................................7
SNMP Alarm MIB Feburary 2001 6. Examples ......................................................28
7. Security Considerations .......................................28
8. Author's Address ..............................................28
9. Acknowledgements ..............................................28
10. References ..................................................29
8. Author's Address ..............................................26 11. Full Copyright Statement ....................................29
9. Acknowledgements ..............................................27
10. References ..................................................27
11. Full Copyright Statement ....................................27
SNMP Alarm MIB Feburary 2001
1. The SNMP Management Framework 1. The SNMP Management Framework
o An overall architecture, described in RFC 2571 [RFC2571]. o An overall architecture, described in RFC 2571 [RFC2571].
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
STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC
1215 [RFC1215]. The second version, called SMIv2, is described 1215 [RFC1215]. The second version, called SMIv2, is described
skipping to change at page 4, line 5 skipping to change at page 4, line 5
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 readable information is not considered to change the semantics of
the MIB. the MIB.
SNMP Alarm MIB Feburary 2001
2. Introduction 2. Introduction
There are two main approaches to management. One is based on polling There are two main approaches to management. One is based on polling
by a management application to determine node status, and the other by a management application to determine node status, and the other
is based on a node sending notifications to manager when status is based on a node sending notifications to manager when status
changes to and from fault conditions. The SNMP approach to date has changes to and from fault conditions. The SNMP approach to date has
been the first. Little has been done to support the second in the been the first. Little has been done to support the second in the
SNMP framework. This document provides the mechanisms for SNMP framework. This document provides the mechanisms for
management to be based on exception reporting. management to be based on exception reporting.
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 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in
this document are to be interpreted as described in RFC-2119 [1]. this document are to be interpreted as described in RFC-2119 [1].
3. Exception Reporting Framework 3. Exception Reporting Framework
1.1. Terminology 3.1 Terminology
Error Error
A deviation of a system from intended operation. A deviation of a system from intended operation.
Fault Fault
A lasting error or warning condition. A lasting error or warning condition.
Alarm Alarm
Persistent indication of a fault. An alarm is said to be 'set' Persistent indication of a fault. An alarm is said to be 'set'
when a fault is first detected and administratively enabled. An (or raised) when a fault is first detected and administratively
alarm is said to be 'cleared' when a fault is first noticed to enabled. An alarm is said to be 'cleared' when a fault is first
have ceased or administratively disabled. noticed to have ceased or administratively disabled.
Event Event
Something that happened. Examples include a change in status, Something that happened. Examples include a change in status,
crossing a threshold, an external input to the system. crossing a threshold, an external input to the system.
Additionally, setting or clearing an alarm is also an event. Additionally, setting or clearing an alarm is also an event.
Notification Notification
An unsolicited transmission of management information due to an An unsolicited transmission of management information due to an
event or condition. event or condition.
<need more here to specify that alarms and notifications need 3.2 Alarm Definitions
different name spaces. And that the SNMP SMI is not extensible, and,
thus there is not a clean way to specify alarm definitions. The Each type of an alarm needs to be well specified. Ideally, a new
OBJECT-IDENTITY must be used, and the parameters of the alarm construct (or template) would be added to the MIB module language,
specified in the text of the DESCRIPTION clause.> which is specified by SNMP's SMI. Unfortunately, this is not
possible. Since alarms are identified with an OID value, the best
choice of construct to use is OBJECT-IDENTITY. This construct allows
a descriptor to be defined, a status and description specified, and
an OID value assigned. The contents of the DESCRIPTION text must be
structured to specify the attributes of an alarm type. The
attributes include:
Raise Conditions
What set of conditions or events cause the alarm to be raised?
Clear Conditions
What must occur to cause the alarm to be cleared?
Source Identification
How are the sources of the alarm identified (a source can be
physical (such as port), or logical, such as a session)?
Perceived Severity
How is the perceived severity of the alarm determined (it may
be statically specified or dynamically determined)?
Service Affecting
How is it determined if the condition is service affecting (it
may be statically specified or dynamically determined)?
Associated Information
What additional information is associated, if any, with the
alarm? For example, if the alarm is due to a threshold being
crossed, the additional information could be the threshold
value and the current value.
Class (Category)
What is the class (category) of the alarm using the ITU-T
terminology?
Probable Cause
How is the probable cause of the alarm determined (it may be
statically specified or dynamically determined)?
Dependencies
What are the dependencies, if any, between this alarm and other
alarms. For example, a loss of signal alarm on a network
interface would probably also result in a network interface
down alarm.
In summary, instead of adding a new construct like the following:
TemperatureAlarm ALARM-TYPE
STATUS current
DESCRIPTION "The current temperature outside of the
acceptable operating range"
RAISED-BY "The measured temperature has been outside of the
acceptable operating range for the last 5 seconds."
ClEARED-BY "The measure temperature has been within the
acceptable range for the last 15 seconds."
. . .
::= { myAlarms 1 }
the existing OBJECT-IDENTITY construct must be used and the
DESCRIPTION field structured like in the following:
TemperatureAlarm OBJECT-IDENTITY
STATUS current
DESCRIPTION "An Alarm
Description:
The current temperature outside of the
acceptable operating range
RAISED-BY:
The measured temperature has been outside of the
acceptable operating range for the last 5
seconds.
ClEARED-BY:
The measure temperature has been within the
acceptable range for the last 15 seconds.
. . . "
::= { myAlarms 1 }
4. MIB Module Overview 4. MIB Module Overview
SNMP Alarm MIB Feburary 2001
<describe the "groups"> The MIB module defines a list of current alarms and a log of alarms
that have been raised and/or cleared. The current alarm list is
specified as two tables. Table snmpAlarmCurrTable contains generic
information about alarms and table snmpItuAlarmCurrTable contains
ITU-T (from X.733 and X.736) information about alarms. The current
varBind table provides additional information about each current
alarm.
<describe how a management application would efficiently manage The alarm log table is specified as two tables. An entry is made in
alarms.> table snmpAlarmLogTable each time an entry is added or removed from
the current alarm table. Likewise an entry is made in table
snmpItuAlarmLogTable each time an entry is added or removed from the
ITU-T augmentation of the current alarm table.
Scalar objects snmpAlarmLastChange, snmpAlarmLogFirstIndex, and
snmpAlarmLogLastIndex provide the information so that a management
application can efficiently track the current alarms and retrieve
entries in the alarm log. Additionally, a manager may choose to use
notifications to assist in tracking the current alarms and/or alarm
log entries. The notification snmpAlarmStatusChange or
snmpItuAlarmStatusChange can be used.
5. Definitions 5. Definitions
SNMP-ALARM-MIB DEFINITIONS ::= BEGIN SNMP-ALARM-MIB DEFINITIONS ::= BEGIN
IMPORTS IMPORTS
MODULE-IDENTITY, MODULE-IDENTITY,
OBJECT-TYPE, OBJECT-TYPE,
NOTIFICATION-TYPE, NOTIFICATION-TYPE,
snmpModules, snmpModules,
skipping to change at page 6, line 4 skipping to change at page 7, line 49
In message body: In message body:
subscribe disman your_email_address subscribe disman your_email_address
Archive: ftp://amethyst.bmc.com/pub/disman/archives Archive: ftp://amethyst.bmc.com/pub/disman/archives
Chair: Randy Presuhn Chair: Randy Presuhn
BMC Software BMC Software
EMail: rpresuhn@bmc.com EMail: rpresuhn@bmc.com
Phone: +1-301-854-6889 Phone: +1-301-854-6889
Author: David T. Perkins Author: David T. Perkins
SNMP Alarm MIB Feburary 2001
SNMPinfo SNMPinfo
Postal: 3763 Benton Street Postal: 3763 Benton Street
Santa Clara, CA 95051 Santa Clara, CA 95051
EMail: dperkins@dsperkins.com EMail: dperkins@dsperkins.com
Phone: +1 408 394 8702" Phone: +1 408 394 8702"
DESCRIPTION DESCRIPTION
"This MIB module defines MIB objects and notifications that "This MIB module defines MIB objects and notifications that
provide mechanisms to monitor alarms currently active and provide mechanisms to monitor alarms currently active and
the history of alarms being set and cleared on a managed the history of alarms being set and cleared on a managed
system. system.
skipping to change at page 7, line 4 skipping to change at page 8, line 51
STATUS current STATUS current
DESCRIPTION "The alarm condition. The values are: DESCRIPTION "The alarm condition. The values are:
set(1)....the alarm condition detected set(1)....the alarm condition detected
clear(2)..the alarm condition ceased" clear(2)..the alarm condition ceased"
SYNTAX INTEGER { SYNTAX INTEGER {
set(1), set(1),
clear(2) clear(2)
} }
SnmpAlarmType ::= TEXTUAL-CONVENTION SnmpAlarmType ::= TEXTUAL-CONVENTION
SNMP Alarm MIB Feburary 2001
STATUS current STATUS current
DESCRIPTION "The identity of the type of an SNMP alarm. The SNMP DESCRIPTION "The identity of the type of an SNMP alarm. The SNMP
SMI does not have a construct to define SNMP alarms. SMI does not have a construct to define SNMP alarms.
Thus, the OBJECT-IDENTITY construct must be Thus, the OBJECT-IDENTITY construct must be
used with the text of the DESCRIPTION clause used with the text of the DESCRIPTION clause
describing the conditions that cause the alarm describing the conditions that cause the alarm
to be set and to be clear, and a description of to be set and to be clear, and a description of
each varBind to be associated with the alarm." each varBind to be associated with the alarm."
SYNTAX OBJECT IDENTIFIER -- really AutonomousType SYNTAX OBJECT IDENTIFIER -- really AutonomousType
skipping to change at page 8, line 4 skipping to change at page 9, line 50
STATUS current STATUS current
DESCRIPTION "A descriminated union, which is the DESCRIPTION "A descriminated union, which is the
following ASN.1 sequence BER encoded following ASN.1 sequence BER encoded
and wrapped as the value of an OCTET and wrapped as the value of an OCTET
STRING. STRING.
<details later> <details later>
" "
SYNTAX OCTET STRING SYNTAX OCTET STRING
snmpAlarmGlobals OBJECT IDENTIFIER ::= { snmpAlarmObjects 1 } snmpAlarmGlobals OBJECT IDENTIFIER ::= { snmpAlarmObjects 1 }
SNMP Alarm MIB Feburary 2001
snmpAlarmCurrEntries OBJECT-TYPE snmpAlarmCurrEntries OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The number of entries in the current alarm table." DESCRIPTION "The number of entries in the current alarm table."
::= { snmpAlarmGlobals 1 } ::= { snmpAlarmGlobals 1 }
snmpAlarmLastChange OBJECT-TYPE snmpAlarmLastChange OBJECT-TYPE
SYNTAX TimeStamp SYNTAX TimeStamp
skipping to change at page 9, line 4 skipping to change at page 10, line 51
values are: values are:
true(1)...notifications may be generated true(1)...notifications may be generated
false(2)..notifications may not be generated" false(2)..notifications may not be generated"
::= { snmpAlarmGlobals 5 } ::= { snmpAlarmGlobals 5 }
-- ITU extension -- ITU extension
snmpItuAlarmGenNotify OBJECT-TYPE snmpItuAlarmGenNotify OBJECT-TYPE
SYNTAX TruthValue SYNTAX TruthValue
MAX-ACCESS read-write MAX-ACCESS read-write
STATUS current STATUS current
SNMP Alarm MIB Feburary 2001
DESCRIPTION "The controls whether or not notification DESCRIPTION "The controls whether or not notification
snmpItuAlarmStatusChange may be generated. snmpItuAlarmStatusChange may be generated.
The values are: The values are:
true(1)...notifications may be generated true(1)...notifications may be generated
false(2)..notifications may not be generated false(2)..notifications may not be generated
Note: if this is enabled, then most likely Note: if this is enabled, then most likely
generation of notification snmpAlarmStatusChange generation of notification snmpAlarmStatusChange
should be disabled." should be disabled."
::= { snmpAlarmGlobals 6 } ::= { snmpAlarmGlobals 6 }
skipping to change at page 10, line 4 skipping to change at page 11, line 50
} }
snmpAlarmCurrIndex OBJECT-TYPE snmpAlarmCurrIndex OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295) SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An arbitrary index of the alarm in the current DESCRIPTION "An arbitrary index of the alarm in the current
alarm table. The index for an existing entry is alarm table. The index for an existing entry is
not affected when a entry is added or removed from not affected when a entry is added or removed from
the table. Index values may be cycled to the max the table. Index values may be cycled to the max
SNMP Alarm MIB Feburary 2001
before reuse or follow any implementation specific before reuse or follow any implementation specific
reuse strategy." reuse strategy."
::= { snmpAlarmCurrEntry 1 } ::= { snmpAlarmCurrEntry 1 }
snmpAlarmCurrOccurDateAndTime OBJECT-TYPE snmpAlarmCurrOccurDateAndTime OBJECT-TYPE
SYNTAX OptDateAndTime SYNTAX OptDateAndTime
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The local date and time when the alarm was set, DESCRIPTION "The local date and time when the alarm was set,
or a zero length string. The value is a zero or a zero length string. The value is a zero
length string when the local time cannot be length string when the local time cannot be
determined." determined."
::= { snmpAlarmCurrEntry 2 } ::= { snmpAlarmCurrEntry 2 }
skipping to change at page 11, line 4 skipping to change at page 12, line 51
snmpAlarmCurrContextName OBJECT-TYPE snmpAlarmCurrContextName OBJECT-TYPE
SYNTAX SnmpAdminString (SIZE(0..32)) SYNTAX SnmpAdminString (SIZE(0..32))
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The context in which the alarm occurred." DESCRIPTION "The context in which the alarm occurred."
::= { snmpAlarmCurrEntry 6 } ::= { snmpAlarmCurrEntry 6 }
snmpAlarmCurrVarBinds OBJECT-TYPE snmpAlarmCurrVarBinds OBJECT-TYPE
SYNTAX Gauge32 SYNTAX Gauge32
MAX-ACCESS read-only MAX-ACCESS read-only
SNMP Alarm MIB Feburary 2001
STATUS current STATUS current
DESCRIPTION "The number of varBinds associated with the DESCRIPTION "The number of varBinds associated with the
alarm. The count is usually at least one, alarm. The count is usually at least one,
with at least one varBind identifying with at least one varBind identifying
the source of the alarm." the source of the alarm."
::= { snmpAlarmCurrEntry 7 } ::= { snmpAlarmCurrEntry 7 }
snmpAlarmCurrVarBindTable OBJECT-TYPE snmpAlarmCurrVarBindTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpAlarmCurrVarBindEntry SYNTAX SEQUENCE OF SnmpAlarmCurrVarBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
skipping to change at page 12, line 4 skipping to change at page 13, line 50
STATUS current STATUS current
DESCRIPTION "The index of the varBind. The value is between DESCRIPTION "The index of the varBind. The value is between
one and the value of the associated object one and the value of the associated object
snmpAlarmCurrVarBinds." snmpAlarmCurrVarBinds."
::= { snmpAlarmCurrVarBindEntry 1 } ::= { snmpAlarmCurrVarBindEntry 1 }
snmpAlarmCurrVarBindId OBJECT-TYPE snmpAlarmCurrVarBindId OBJECT-TYPE
SYNTAX VariablePointer SYNTAX VariablePointer
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
SNMP Alarm MIB Feburary 2001
DESCRIPTION "The ID of the object instance." DESCRIPTION "The ID of the object instance."
::= { snmpAlarmCurrVarBindEntry 2 } ::= { snmpAlarmCurrVarBindEntry 2 }
snmpAlarmCurrVarBindVal OBJECT-TYPE snmpAlarmCurrVarBindVal OBJECT-TYPE
SYNTAX SnmpValUnion SYNTAX SnmpValUnion
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The value of the object instance." DESCRIPTION "The value of the object instance."
::= { snmpAlarmCurrVarBindEntry 3 } ::= { snmpAlarmCurrVarBindEntry 3 }
skipping to change at page 13, line 4 skipping to change at page 14, line 50
be created or deleted via SNMP operations." be created or deleted via SNMP operations."
INDEX { snmpAlarmLogIndex } INDEX { snmpAlarmLogIndex }
::= { snmpAlarmLogTable 1 } ::= { snmpAlarmLogTable 1 }
SnmpAlarmLogEntry ::= SEQUENCE { SnmpAlarmLogEntry ::= SEQUENCE {
snmpAlarmLogIndex Unsigned32, snmpAlarmLogIndex Unsigned32,
snmpAlarmLogCond SnmpAlarmCond, snmpAlarmLogCond SnmpAlarmCond,
snmpAlarmLogOccurDateAndTime OptDateAndTime, snmpAlarmLogOccurDateAndTime OptDateAndTime,
snmpAlarmLogOccurUpTime TimeStamp, snmpAlarmLogOccurUpTime TimeStamp,
snmpAlarmLogType SnmpAlarmType, snmpAlarmLogType SnmpAlarmType,
SNMP Alarm MIB Feburary 2001
snmpAlarmLogId Unsigned32, snmpAlarmLogId Unsigned32,
snmpAlarmLogContextName SnmpAdminString, snmpAlarmLogContextName SnmpAdminString,
snmpAlarmLogVarBinds Gauge32 snmpAlarmLogVarBinds Gauge32
} }
snmpAlarmLogIndex OBJECT-TYPE snmpAlarmLogIndex OBJECT-TYPE
SYNTAX Unsigned32(1..4294967295) SYNTAX Unsigned32(1..4294967295)
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "An index of the alarm in the alarm log table. The DESCRIPTION "An index of the alarm in the alarm log table. The
index is increased by one for each new entry in the index is increased by one for each new entry in the
table until the maximum value is reach and then the table until the maximum value is reach and then the
index restarts at 1. The index of the oldest entry index restarts at 1. The index of the oldest entry
is specified by object snmpAlarmLogFirstIndex and is specified by object snmpAlarmLogFirstIndex and
index of the youngest entry is specified by object index of the youngest entry is specified by object
skipping to change at page 14, line 4 skipping to change at page 15, line 50
cleared, or zero. The value is zero when the alarm cleared, or zero. The value is zero when the alarm
was set or cleared before the most recent reset of was set or cleared before the most recent reset of
the management system." the management system."
::= { snmpAlarmLogEntry 4 } ::= { snmpAlarmLogEntry 4 }
snmpAlarmLogType OBJECT-TYPE snmpAlarmLogType OBJECT-TYPE
SYNTAX SnmpAlarmType SYNTAX SnmpAlarmType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The type of the alarm." DESCRIPTION "The type of the alarm."
SNMP Alarm MIB Feburary 2001
::= { snmpAlarmLogEntry 5 } ::= { snmpAlarmLogEntry 5 }
snmpAlarmLogId OBJECT-TYPE snmpAlarmLogId OBJECT-TYPE
SYNTAX Unsigned32 SYNTAX Unsigned32
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The ID of the alarm. Each alarm that is set DESCRIPTION "The ID of the alarm. Each alarm that is set
is assigned a unique ID among active alarms. is assigned a unique ID among active alarms.
That is, no two active alarms may have the That is, no two active alarms may have the
same value. This value is used in matching same value. This value is used in matching
skipping to change at page 15, line 4 skipping to change at page 16, line 50
DESCRIPTION "A table of varBinds (pairs of variable and value) DESCRIPTION "A table of varBinds (pairs of variable and value)
that sparse extends the rows in table that sparse extends the rows in table
snmpAlarmLogTable. That is, for each row in table snmpAlarmLogTable. That is, for each row in table
snmpAlarmLogTable, there is zero, one, or more snmpAlarmLogTable, there is zero, one, or more
associated rows in this table. The value of object associated rows in this table. The value of object
snmpAlarmLogVarBinds specifies the number of rows snmpAlarmLogVarBinds specifies the number of rows
in this table." in this table."
::= { snmpAlarmObjects 5 } ::= { snmpAlarmObjects 5 }
snmpAlarmLogVarBindEntry OBJECT-TYPE snmpAlarmLogVarBindEntry OBJECT-TYPE
SNMP Alarm MIB Feburary 2001
SYNTAX SnmpAlarmLogVarBindEntry SYNTAX SnmpAlarmLogVarBindEntry
MAX-ACCESS not-accessible MAX-ACCESS not-accessible
STATUS current STATUS current
DESCRIPTION "A row in the table of varBinds for the alarm DESCRIPTION "A row in the table of varBinds for the alarm
log. Rows cannot be created or deleted via log. Rows cannot be created or deleted via
SNMP operations." SNMP operations."
INDEX { snmpAlarmLogIndex, INDEX { snmpAlarmLogIndex,
snmpAlarmLogVarBindIndex } snmpAlarmLogVarBindIndex }
::= { snmpAlarmLogVarBindTable 1 } ::= { snmpAlarmLogVarBindTable 1 }
skipping to change at page 16, line 4 skipping to change at page 17, line 50
SnmpItuAlarmClass ::= TEXTUAL-CONVENTION SnmpItuAlarmClass ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "The class of alarm as specified in DESCRIPTION "The class of alarm as specified in
[X.733] and [X.736]. [X.733] and [X.736].
<expand this>" <expand this>"
SYNTAX INTEGER { SYNTAX INTEGER {
other (1), other (1),
communicationsAlarm (2), communicationsAlarm (2),
qualityOfServiceAlarm (3), qualityOfServiceAlarm (3),
processingErrorAlarm (4), processingErrorAlarm (4),
SNMP Alarm MIB Feburary 2001
equipmentAlarm (5), equipmentAlarm (5),
environmentalAlarm (6), environmentalAlarm (6),
integrityViolation (7), integrityViolation (7),
operationalViolation (8), operationalViolation (8),
physicalViolation (9), physicalViolation (9),
securityServiceOrMechanismViolation (10), securityServiceOrMechanismViolation (10),
timeDomainViolation (11) timeDomainViolation (11)
} }
SnmpItuAlarmProbCause ::= TEXTUAL-CONVENTION SnmpItuAlarmProbCause ::= TEXTUAL-CONVENTION
skipping to change at page 17, line 4 skipping to change at page 18, line 51
leakDetected (27), leakDetected (27),
localNodeTransmissionError (28), localNodeTransmissionError (28),
lossOfFrame (29), lossOfFrame (29),
lossOfSignal (30), lossOfSignal (30),
materialSupplyExhausted (31), materialSupplyExhausted (31),
multiplexerProblem (32), multiplexerProblem (32),
outOfMemory (33), outOfMemory (33),
ouputDeviceError (34), ouputDeviceError (34),
performanceDegraded (35), performanceDegraded (35),
powerProblem (36), powerProblem (36),
SNMP Alarm MIB Feburary 2001
pressureUnacceptable (37), pressureUnacceptable (37),
processorProblem (38), processorProblem (38),
pumpFailure (39), pumpFailure (39),
queueSizeExceeded (40), queueSizeExceeded (40),
receiveFailure (41), receiveFailure (41),
receiverFailure (42), receiverFailure (42),
remoteNodeTransmissionError (43), remoteNodeTransmissionError (43),
resourceAtOrNearingCapacity (44), resourceAtOrNearingCapacity (44),
responseTimeExecessive (45), responseTimeExecessive (45),
retransmissionRateExcessive (46), retransmissionRateExcessive (46),
skipping to change at page 18, line 4 skipping to change at page 19, line 51
SnmpItuAlarmPercSeverity ::= TEXTUAL-CONVENTION SnmpItuAlarmPercSeverity ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "The perceived severity of the alarm as DESCRIPTION "The perceived severity of the alarm as
specified in [X.733] and [X.736]. specified in [X.733] and [X.736].
<expand this>" <expand this>"
SYNTAX INTEGER { SYNTAX INTEGER {
indeterminate (2), indeterminate (2),
critical (3), critical (3),
major (4), major (4),
minor (5), minor (5),
SNMP Alarm MIB Feburary 2001
warning (6) warning (6)
} }
SnmpItuAlarmTrendInd ::= TEXTUAL-CONVENTION SnmpItuAlarmTrendInd ::= TEXTUAL-CONVENTION
STATUS current STATUS current
DESCRIPTION "The trend indication of the alarm as DESCRIPTION "The trend indication of the alarm as
specified in [X.733]. specified in [X.733].
<expand this>" <expand this>"
SYNTAX INTEGER { SYNTAX INTEGER {
moreSevere (1), moreSevere (1),
skipping to change at page 19, line 4 skipping to change at page 20, line 50
snmpItuAlarmCurrServiceUser AutonomousType snmpItuAlarmCurrServiceUser AutonomousType
} }
snmpItuAlarmCurrClass OBJECT-TYPE snmpItuAlarmCurrClass OBJECT-TYPE
SYNTAX SnmpItuAlarmClass SYNTAX SnmpItuAlarmClass
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The class of the alarm as specified in DESCRIPTION "The class of the alarm as specified in
[X.733] and [X.736]. [X.733] and [X.736].
<expand this>" <expand this>"
SNMP Alarm MIB Feburary 2001
::= { snmpItuAlarmCurrEntry 1 } ::= { snmpItuAlarmCurrEntry 1 }
snmpItuAlarmCurrProbCause OBJECT-TYPE snmpItuAlarmCurrProbCause OBJECT-TYPE
SYNTAX SnmpItuAlarmProbCause SYNTAX SnmpItuAlarmProbCause
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The probable cause of the alarm as DESCRIPTION "The probable cause of the alarm as
specified in [X.733] and [X.736]. specified in [X.733] and [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmCurrEntry 2 } ::= { snmpItuAlarmCurrEntry 2 }
skipping to change at page 20, line 4 skipping to change at page 21, line 51
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The SecurityAlarmDetector object from [X.736]. DESCRIPTION "The SecurityAlarmDetector object from [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmCurrEntry 6 } ::= { snmpItuAlarmCurrEntry 6 }
snmpItuAlarmCurrServiceProvider OBJECT-TYPE snmpItuAlarmCurrServiceProvider OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
SNMP Alarm MIB Feburary 2001
DESCRIPTION "The ServiceProvider object from [X.736]. DESCRIPTION "The ServiceProvider object from [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmCurrEntry 7 } ::= { snmpItuAlarmCurrEntry 7 }
snmpItuAlarmCurrServiceUser OBJECT-TYPE snmpItuAlarmCurrServiceUser OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The SericeUser object from [X.736]. DESCRIPTION "The SericeUser object from [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmCurrEntry 8 } ::= { snmpItuAlarmCurrEntry 8 }
snmpItuAlarmLogTable OBJECT-TYPE snmpItuAlarmLogTable OBJECT-TYPE
SYNTAX SEQUENCE OF SnmpItuAlarmLogEntry SYNTAX SEQUENCE OF SnmpItuAlarmLogEntry
skipping to change at page 21, line 4 skipping to change at page 22, line 51
snmpItuAlarmLogClass OBJECT-TYPE snmpItuAlarmLogClass OBJECT-TYPE
SYNTAX SnmpItuAlarmClass SYNTAX SnmpItuAlarmClass
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The class of the alarm as specified in DESCRIPTION "The class of the alarm as specified in
[X.733] and [X.736]. [X.733] and [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmLogEntry 1 } ::= { snmpItuAlarmLogEntry 1 }
snmpItuAlarmLogProbCause OBJECT-TYPE snmpItuAlarmLogProbCause OBJECT-TYPE
SNMP Alarm MIB Feburary 2001
SYNTAX SnmpItuAlarmProbCause SYNTAX SnmpItuAlarmProbCause
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The probable cause of the alarm as DESCRIPTION "The probable cause of the alarm as
specified in [X.733] and [X.736]. specified in [X.733] and [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmLogEntry 2 } ::= { snmpItuAlarmLogEntry 2 }
snmpItuAlarmLogPercSeverity OBJECT-TYPE snmpItuAlarmLogPercSeverity OBJECT-TYPE
SYNTAX SnmpItuAlarmPercSeverity SYNTAX SnmpItuAlarmPercSeverity
skipping to change at page 22, line 4 skipping to change at page 23, line 51
<expand this>" <expand this>"
::= { snmpItuAlarmLogEntry 6 } ::= { snmpItuAlarmLogEntry 6 }
snmpItuAlarmLogServiceProvider OBJECT-TYPE snmpItuAlarmLogServiceProvider OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The ServiceProvider object from [X.736]. DESCRIPTION "The ServiceProvider object from [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmLogEntry 7 } ::= { snmpItuAlarmLogEntry 7 }
SNMP Alarm MIB Feburary 2001
snmpItuAlarmLogServiceUser OBJECT-TYPE snmpItuAlarmLogServiceUser OBJECT-TYPE
SYNTAX AutonomousType SYNTAX AutonomousType
MAX-ACCESS read-only MAX-ACCESS read-only
STATUS current STATUS current
DESCRIPTION "The SericeUser object from [X.736]. DESCRIPTION "The SericeUser object from [X.736].
<expand this>" <expand this>"
::= { snmpItuAlarmLogEntry 8 } ::= { snmpItuAlarmLogEntry 8 }
-- notifications -- notifications
skipping to change at page 23, line 4 skipping to change at page 24, line 50
snmpItuAlarmStatusChange NOTIFICATION-TYPE snmpItuAlarmStatusChange NOTIFICATION-TYPE
OBJECTS { snmpAlarmLogCond, OBJECTS { snmpAlarmLogCond,
snmpAlarmLogOccurDateAndTime, snmpAlarmLogOccurDateAndTime,
snmpAlarmLogOccurUpTime, snmpAlarmLogOccurUpTime,
snmpAlarmLogId, snmpAlarmLogId,
snmpAlarmLogVarBinds, snmpAlarmLogVarBinds,
snmpItuAlarmLogClass, snmpItuAlarmLogClass,
snmpItuAlarmLogProbCause, snmpItuAlarmLogProbCause,
snmpItuAlarmLogPercSeverity, snmpItuAlarmLogPercSeverity,
SNMP Alarm MIB Feburary 2001
snmpItuAlarmLogAdditText, snmpItuAlarmLogAdditText,
snmpItuAlarmLogTrendInd, snmpItuAlarmLogTrendInd,
snmpItuAlarmLogDetector, snmpItuAlarmLogDetector,
snmpItuAlarmLogServiceProvider, snmpItuAlarmLogServiceProvider,
snmpItuAlarmLogServiceUser } snmpItuAlarmLogServiceUser }
STATUS current STATUS current
DESCRIPTION "An entry has been added to the alarm log DESCRIPTION "An entry has been added to the alarm log
table and the ITU extensions are supported. table and the ITU extensions are supported.
That is, an alarm has been set or cleared. That is, an alarm has been set or cleared.
The objects all have the same instance, which is The objects all have the same instance, which is
skipping to change at page 24, line 4 skipping to change at page 25, line 50
snmpAlarmCompliance MODULE-COMPLIANCE snmpAlarmCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for systems supporting "The compliance statement for systems supporting
the SNMP alarms." the SNMP alarms."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { snmpAlarmGblGroup, MANDATORY-GROUPS { snmpAlarmGblGroup,
snmpAlarmCurrGroup, snmpAlarmCurrGroup,
snmpAlarmLogGroup, snmpAlarmLogGroup,
SNMP Alarm MIB Feburary 2001
snmpAlarmNotifyGroup } snmpAlarmNotifyGroup }
::= { snmpAlarmCompliances 1 } ::= { snmpAlarmCompliances 1 }
snmpItuAlarmCompliance MODULE-COMPLIANCE snmpItuAlarmCompliance MODULE-COMPLIANCE
STATUS current STATUS current
DESCRIPTION DESCRIPTION
"The compliance statement for systems supporting "The compliance statement for systems supporting
the ITU-T extension to SNMP alarms." the ITU-T extension to SNMP alarms."
MODULE -- this module MODULE -- this module
MANDATORY-GROUPS { snmpAlarmGblGroup, MANDATORY-GROUPS { snmpAlarmGblGroup,
skipping to change at page 25, line 4 skipping to change at page 26, line 49
DESCRIPTION "Objects in the SNMP current alarm and DESCRIPTION "Objects in the SNMP current alarm and
current varBind tables." current varBind tables."
::= { snmpAlarmGroups 2 } ::= { snmpAlarmGroups 2 }
snmpAlarmLogGroup OBJECT-GROUP snmpAlarmLogGroup OBJECT-GROUP
OBJECTS { snmpAlarmLogCond, OBJECTS { snmpAlarmLogCond,
snmpAlarmLogOccurDateAndTime, snmpAlarmLogOccurDateAndTime,
snmpAlarmLogOccurUpTime, snmpAlarmLogOccurUpTime,
snmpAlarmLogType, snmpAlarmLogType,
snmpAlarmLogId, snmpAlarmLogId,
SNMP Alarm MIB Feburary 2001
snmpAlarmLogContextName, snmpAlarmLogContextName,
snmpAlarmLogVarBinds, snmpAlarmLogVarBinds,
snmpAlarmLogVarBindId, snmpAlarmLogVarBindId,
snmpAlarmLogVarBindVal } snmpAlarmLogVarBindVal }
STATUS current STATUS current
DESCRIPTION "Objects in the SNMP alarm log and DESCRIPTION "Objects in the SNMP alarm log and
log varBind tables." log varBind tables."
::= { snmpAlarmGroups 3 } ::= { snmpAlarmGroups 3 }
snmpAlarmNotifyGroup NOTIFICATION-GROUP snmpAlarmNotifyGroup NOTIFICATION-GROUP
skipping to change at page 26, line 4 skipping to change at page 27, line 50
snmpItuAlarmLogPercSeverity, snmpItuAlarmLogPercSeverity,
snmpItuAlarmLogAdditText, snmpItuAlarmLogAdditText,
snmpItuAlarmLogTrendInd, snmpItuAlarmLogTrendInd,
snmpItuAlarmLogDetector, snmpItuAlarmLogDetector,
snmpItuAlarmLogServiceProvider, snmpItuAlarmLogServiceProvider,
snmpItuAlarmLogServiceUser } snmpItuAlarmLogServiceUser }
STATUS current STATUS current
DESCRIPTION "Objects in the ITU-T extension to the DESCRIPTION "Objects in the ITU-T extension to the
SNMP alarm log and log varBind tables." SNMP alarm log and log varBind tables."
::= { snmpAlarmGroups 7 } ::= { snmpAlarmGroups 7 }
SNMP Alarm MIB Feburary 2001
snmpItuAlarmNotifyGroup NOTIFICATION-GROUP snmpItuAlarmNotifyGroup NOTIFICATION-GROUP
NOTIFICATIONS { snmpItuAlarmStatusChange } NOTIFICATIONS { snmpItuAlarmStatusChange }
STATUS current STATUS current
DESCRIPTION "Notifications for ITU-T extension to SNMP alarms." DESCRIPTION "Notifications for ITU-T extension to SNMP alarms."
::= { snmpAlarmGroups 8 } ::= { snmpAlarmGroups 8 }
END END
6. Examples 6. Examples
skipping to change at page 27, line 4 skipping to change at page 28, line 45
(change/create/delete) them. (change/create/delete) them.
8. Author's Address 8. Author's Address
David T. Perkins David T. Perkins
SNMPinfo SNMPinfo
3663 Benton Street 3663 Benton Street
Santa Clara, CA 95051 Santa Clara, CA 95051
Phone: +1 408 394-8702 Phone: +1 408 394-8702
Email: dperkins@dsperkins.com Email: dperkins@dsperkins.com
SNMP Alarm MIB Feburary 2001
9. Acknowledgements 9. Acknowledgements
This document is a product of the DISMAN Working Group. This document is a product of the DISMAN Working Group.
... ...
10. References 10. References
[RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An
Architecture for Describing SNMP Management Frameworks", Architecture for Describing SNMP Management Frameworks",
RFC 2571, April 41999. RFC 2571, April 41999.
[RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J.,
skipping to change at page 28, line 4 skipping to change at page 29, line 47
and distributed, in whole or in part, without restriction of any and distributed, in whole or in part, without restriction of any
kind, provided that the above copyright notice and this paragraph kind, provided that the above copyright notice and this paragraph
are included on all such copies and derivative works. However, this are included on all such copies and derivative works. However, this
document itself may not be modified in any way, such as by removing document itself may not be modified in any way, such as by removing
the copyright notice or references to the Internet Society or other the copyright notice or references to the Internet Society or other
Internet organizations, except as needed for the purpose of Internet organizations, except as needed for the purpose of
developing Internet standards in which case the procedures for developing Internet standards in which case the procedures for
copyrights defined in the Internet Standards process must be copyrights defined in the Internet Standards process must be
followed, or as required to translate it into languages other than followed, or as required to translate it into languages other than
English. English.
SNMP Alarm MIB Feburary 2001
The limited permissions granted above are perpetual and will not be The limited permissions granted above are perpetual and will not be
revoked by the Internet Society or its successors or assigns. revoked by the Internet Society or its successors or assigns.
This document and the information contained herein is provided on an This document and the information contained herein is provided on an
"AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING
TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING
BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION
HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF
MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.
 End of changes. 

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