idnits 2.17.1 draft-chisholm-disman-active-alarm-01.txt: ** The Abstract section seems to be numbered Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** Looks like you're using RFC 2026 boilerplate. This must be updated to follow RFC 3978/3979, as updated by RFC 4748. Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- ** The document seems to lack a 1id_guidelines paragraph about 6 months document validity -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? ** The document is more than 15 pages and seems to lack a Table of Contents. == No 'Intended status' indicated for this document; assuming Proposed Standard == The page length should not exceed 58 lines per page, but there was 20 longer pages, the longest (page 2) being 60 lines == It seems as if not all pages are separated by form feeds - found 0 form feeds but 21 pages Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. ** The document seems to lack a both a reference to RFC 2119 and the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords. RFC 2119 keyword, line 399: '...aged system, and MUST be used as the d...' RFC 2119 keyword, line 423: '... value MUST be set to zero."...' RFC 2119 keyword, line 458: '... This object MUST always be instan...' Miscellaneous warnings: ---------------------------------------------------------------------------- == Line 942 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) -- Looks like a reference, but probably isn't: 'RFC2571' on line 41 -- Looks like a reference, but probably isn't: 'RFC1155' on line 46 -- Looks like a reference, but probably isn't: 'RFC1212' on line 46 -- Looks like a reference, but probably isn't: 'RFC1215' on line 47 -- Looks like a reference, but probably isn't: 'RFC2578' on line 48 -- Looks like a reference, but probably isn't: 'RFC2579' on line 48 -- Looks like a reference, but probably isn't: 'RFC2580' on line 49 -- Looks like a reference, but probably isn't: 'RFC1157' on line 62 -- Looks like a reference, but probably isn't: 'RFC1901' on line 56 -- Looks like a reference, but probably isn't: 'RFC1906' on line 58 -- Looks like a reference, but probably isn't: 'RFC2572' on line 58 -- Looks like a reference, but probably isn't: 'RFC2574' on line 58 -- Looks like a reference, but probably isn't: 'RFC1905' on line 64 -- Looks like a reference, but probably isn't: 'RFC2573' on line 67 -- Looks like a reference, but probably isn't: 'RFC2575' on line 68 -- Looks like a reference, but probably isn't: 'RFC2570' on line 71 == Unused Reference: '1' is defined on line 921, but no explicit reference was found in the text == Unused Reference: '2' is defined on line 923, but no explicit reference was found in the text == Unused Reference: '3' is defined on line 926, but no explicit reference was found in the text -- Possible downref: Non-RFC (?) normative reference: ref. '1' -- Possible downref: Non-RFC (?) normative reference: ref. '2' -- Possible downref: Non-RFC (?) normative reference: ref. '3' Summary: 8 errors (**), 0 flaws (~~), 7 warnings (==), 21 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 INTERNET-DRAFT S. Chisholm 2 Nortel Networks 3 October 22 2000 5 Alarm MIB 6 draft-chisholm-disman-active-alarm-01.txt 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance with all 11 provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering Task 14 Force (IETF), its areas, and its working groups. Note that other groups 15 may also distribute working documents as Internet-Drafts. 17 Internet-Drafts are draft documents valid for a maximum of six months 18 and may be updated, replaced, or obsoleted by other documents at any 19 time. It is inappropriate to use Internet- Drafts as reference material 20 or to cite them other than as "work in progress." 22 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 1. Abstract 31 This memo defines a portion of the Management Information Base (MIB) 32 for use with network management protocols in the Internet community. 33 In particular, it describes management objects used for maintaining 34 a list of alarms currently active on a network element. 36 2. The SNMP Management Framework 38 The SNMP Management Framework presently consists of five major 39 components: 41 o An overall architecture, described in RFC 2571 [RFC2571]. 43 o Mechanisms for describing and naming objects and events for the 44 purpose of management. The first version of this Structure of 45 Management Information (SMI) is called SMIv1 and described in 46 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 47 1215 [RFC1215]. The second version, called SMIv2, is described 48 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 49 STD 58, RFC 2580 [RFC2580]. 51 o Message protocols for transferring management information. The 52 first version of the SNMP message protocol is called SNMPv1 and 53 described in STD 15, RFC 1157 [RFC1157]. A second version of 54 the SNMP message protocol, which is not an Internet standards 55 track protocol, is called SNMPv2c and described in RFC 1901 56 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 57 message protocol is called SNMPv3 and described in RFC 1906 58 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 60 o Protocol operations for accessing management information. The 61 first set of protocol operations and associated PDU formats is 62 described in STD 15, RFC 1157 [RFC1157]. A second set of 63 protocol operations and associated PDU formats is described in 64 RFC 1905 [RFC1905]. 66 o A set of fundamental applications described in RFC 2573 67 [RFC2573] and the view-based access control mechanism described 68 in RFC 2575 [RFC2575]. 70 A more detailed introduction to the current SNMP Management Framework 71 can be found in RFC 2570 [RFC2570]. 73 Managed objects are accessed via a virtual information store, termed 74 the Management Information Base or MIB. Objects in the MIB are 75 defined using the mechanisms defined in the SMI. 77 This memo specifies a MIB module that is compliant to the SMIv2. A 78 MIB conforming to the SMIv1 can be produced through the appropriate 79 translations. The resulting translated MIB must be semantically 80 equivalent, except where objects or events are omitted because no 81 translation is possible (use of Counter64). Some machine readable 82 information in SMIv2 will be converted into textual descriptions in 83 SMIv1 during the translation process. However, this loss of machine 84 readable information is not considered to change the semantics of the 85 MIB. 87 3. Introduction 89 An alarm is an error condition occurring on a system that needs 90 to be fixed, either automatically or through manual intervention. 92 The alarm details table contains information which is applicable 93 to all instances of an alarm. It is populated at start-up with 94 all alarms that could happen on a system. The information in this 95 table should be fairly static during system operation. 97 The active alarm table contains a list of alarms which are currently 98 occurring on a system. It is intended that this table be queried 99 upon device discovery and rediscovery to determine which alarms are 100 currently active on the device. This allows the network management 101 station to find out about any problems that may have occurred before 102 it started managing a particular network element, or while it was out 103 of contact with it. 105 Each alarm should have a corresponding clear which removes it from 106 the active alarm table. Alternatively it could be aged out. The 107 configuring and querying of alarm age-outs is not covered in this 108 document. 110 4. Relation to Notification Log MIB 112 This MIB is intended to compliment the notification log MIB, but 113 can be used independently. The active alarm table is defined in 114 manner similar to that of the notification log table. This format 115 allows for the storage of any NOTIFICATION that can be defined using 116 SMI. Using the same format as the notification log MIB also 117 simplifies operations for systems choosing to implement both MIBs. 119 5. Alarm Raise and Clear 121 The alarm details table provides a means of defining the raise/clear 122 relationship between alarms. The alarmDetailsPerceivedSeverity object 123 indicates whether this is a raise alarm or a clear alarm. The 124 alarmDetailsNotificationId gives the OID of this particular alarm. If 125 this is a raise alarm, the alarmDetailsClearNotificationId object 126 gives the OID of corresponding clear alarm. If this is a clear 127 alarm, the alarmDetailsClearNotificationId object gives the OID of 128 one of the corresponding raise alarms for this clear. 130 6. ITU-T X.733, X.736 Trap Content 132 Selected information from ITU-T X.733, X.736 alarm documents has been 133 included in the alarmDetailsTable and the alarmActiveTable, depending 134 on the variability of this information. Support of these objects is 135 not necessary to support the alarm raise/clear and active alarm 136 components of this MIB. 138 7. Definitions 140 ALARM-MIB DEFINITIONS ::= BEGIN 142 IMPORTS 143 MODULE-IDENTITY, OBJECT-TYPE, 144 experimental, Integer32, Unsigned32, 145 TimeTicks, Counter32, Counter64, 146 IpAddress, Opaque, mib-2 FROM SNMPv2-SMI 147 TimeStamp, DateAndTime, DisplayString, 148 StorageType, RowStatus FROM SNMPv2-TC 149 SnmpAdminString, SnmpEngineID FROM SNMP-FRAMEWORK-MIB 150 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 152 alarm MODULE-IDENTITY 153 LAST-UPDATED "000010220000Z" 154 ORGANIZATION "Alarm MIB" 155 CONTACT-INFO 156 " Sharon Chisholm 157 Nortel Networks 158 PO Box 3511 Station C 159 Ottawa, Ont. K1Y 4H7 160 Canada 162 schishol@nortelnetworks.com" 163 DESCRIPTION 164 "The MIB module describes a generic solution 165 to improve the reliability of SNMP traps by storing alarm 166 details and the current list of active alarms." 167 ::= { mib-2 xx } 169 alarmObjects OBJECT IDENTIFIER ::= { alarm 1 } 171 alarmDetailsTable OBJECT-TYPE 172 SYNTAX SEQUENCE OF AlarmDetailsEntry 173 MAX-ACCESS not-accessible 174 STATUS current 175 DESCRIPTION 176 "A table of information about possible alarms on the system." 177 ::= { alarmObjects 1 } 179 alarmDetailsEntry OBJECT-TYPE 180 SYNTAX AlarmDetailsEntry 181 MAX-ACCESS not-accessible 182 STATUS current 183 DESCRIPTION 184 "Entries appear in this table for each possible alarm." 186 INDEX { alarmListName, alarmDetailsIndex } 187 ::= { alarmDetailsTable 1 } 189 AlarmDetailsEntry ::= SEQUENCE { 190 alarmDetailsIndex Unsigned32, 191 alarmDetailsNotificationId OBJECT IDENTIFIER, 192 alarmDetailsClearNotificationId OBJECT IDENTIFIER, 193 alarmDetailsEventType INTEGER, 194 alarmDetailsProbableCause INTEGER, 195 alarmDetailsPerceivedSeverity INTEGER, 196 alarmDetailsAdditionalText DisplayString } 198 alarmDetailsIndex OBJECT-TYPE 199 SYNTAX Unsigned32 (1..4294967295) 200 MAX-ACCESS read-only 201 STATUS current 202 DESCRIPTION 203 "A integer which acts as the 204 index of entries within the named alarm list. " 205 ::= { alarmDetailsEntry 1 } 207 alarmDetailsNotificationId OBJECT-TYPE 208 SYNTAX OBJECT IDENTIFIER 209 MAX-ACCESS read-only 210 STATUS current 211 DESCRIPTION 212 "The NOTIFICATION-TYPE object identifier of this alarm." 213 ::= { alarmDetailsEntry 2 } 215 alarmDetailsClearNotificationId OBJECT-TYPE 216 SYNTAX OBJECT IDENTIFIER 217 MAX-ACCESS read-only 218 STATUS current 219 DESCRIPTION 220 "The NOTIFICATION-TYPE object identifier of the alarm which 221 clears this alarm. If this entry corresponds to a clear 222 alarm, then this object should be one of the notifications 223 which sets this alarm condition" 224 ::= { alarmDetailsEntry 3 } 226 alarmDetailsEventType OBJECT-TYPE 227 SYNTAX INTEGER 228 { 229 other (1), 230 communityAlarmType (2), 231 qualityOfServerAlarmType (3), 232 processingErrorAlarmType (4), 233 equipmentAlarmType (5), 234 environmentalAlarmType (6) } 235 MAX-ACCESS read-only 236 STATUS current 237 DESCRIPTION 238 " Represents the event type values for the alarms as per 239 (ITU-T X.733)." 240 ::= { alarmDetailsEntry 4 } 242 alarmDetailsProbableCause OBJECT-TYPE 243 SYNTAX INTEGER 244 { 245 other (1), 246 adapterError (2), 247 applicationSubsystemFailure (3), 248 bandwidthReduced (4), 249 callEstablishmentError (5), 250 communicationsProtocolError (6), 251 communicationsSubsystemFailure (7), 252 configurationOrCustomizationError (8), 253 congestion (9), 254 corruptData (10), 255 cpuCyclesLimitExceeded (11), 256 dataSetOrModemError (12), 257 degradedSignal (13), 258 dteDceInterfaceError (14), 259 enclosureDoorOpen (15), 260 equipmentMalfunction (16), 261 excessiveVibration (17), 262 fileError (18), 263 fireDetected (19), 264 floodDetected (20), 265 framingError (21), 266 heatingOrVentilationOrCoolingSystemProblem (22), 267 humidityUnacceptable (23), 268 inputOutputDeviceError (24), 269 inputDeviceError (25), 270 lanError (26), 271 leakDetected (27), 272 localNodeTransmissionError (28), 273 lossOfFrame (29), 274 lossOfSignal (30), 275 materialSupplyExhausted (31), 276 multiplexerProblem (32), 277 outOfMemory (33), 278 ouputDeviceError (34), 279 performanceDegraded (35), 280 powerProblem (36), 281 pressureUnacceptable (37), 282 processorProblem (38), 283 pumpFailure (39), 284 queueSizeExceeded (40), 285 receiveFailure (41), 286 receiverFailure (42), 287 remoteNodeTransmissionError (43), 288 resourceAtOrNearingCapacity (44), 289 responseTimeExecessive (45), 290 retransmissionRateExcessive (46), 291 softwareError (47), 292 softwareProgramAbnormallyTerminated (48), 293 softwareProgramError (49), 294 storageCapacityProblem (50), 295 temperatureUnacceptable (51), 296 thresholdCrossed (52), 297 timingProblem (53), 298 toxicLeakDetected (54), 299 transmitFailure (55), 300 transmitterFailure (56), 301 underlyingResourceUnavailable (57), 302 versionMismatch (58), 303 authenticationFailure (59), 304 breachOfConfidentiality (60), 305 cableTamper (61), 306 delayedInformation (62), 307 denialOfService (63), 308 duplicateInformation (64), 309 informationMissing (65), 310 informationModificationDetected (66), 311 informationOutOfSequence (67), 312 intrusionDetection (68), 313 keyExpired (69), 314 nonRepudiationFailure (70), 315 outOfHoursActivity (71), 316 outOfService (72), 317 proceduralError (73), 318 unauthorizedAccessAttempt (74), 319 unexpectedInformation (75) 320 } 321 MAX-ACCESS read-only 322 STATUS current 324 DESCRIPTION 325 " Represents the probable cause values for the alarms as 326 per (ITU-T X.733, X.736)." 327 ::= { alarmDetailsEntry 5 } 329 alarmDetailsPerceivedSeverity OBJECT-TYPE 330 SYNTAX INTEGER { 331 cleared (1), 332 indeterminate (2), 333 critical (3), 334 major (4), 335 minor (5), 336 warning (6) } 337 MAX-ACCESS read-only 338 STATUS current 339 DESCRIPTION 340 " Represents the perceived severity values for the alarms 341 as per (ITU-T X.733)." 342 ::= { alarmDetailsEntry 6 } 344 alarmDetailsAdditionalText OBJECT-TYPE 345 SYNTAX DisplayString 346 MAX-ACCESS read-only 347 STATUS current 348 DESCRIPTION 349 " Represents the additional text field for the alarm as per 350 (ITU-T X.733)." 351 ::= { alarmDetailsEntry 7} 353 -- -- Active Alarm Table -- 355 alarmActiveTable OBJECT-TYPE 356 SYNTAX SEQUENCE OF AlarmActiveEntry 357 MAX-ACCESS not-accessible 358 STATUS current 359 DESCRIPTION 360 "A table of Active Alarms entries." 361 ::= { alarmObjects 2 } 363 alarmActiveEntry OBJECT-TYPE 364 SYNTAX AlarmActiveEntry 365 MAX-ACCESS not-accessible 366 STATUS current 367 DESCRIPTION 368 "Entries appear in this table when alarms are active. They are 369 removed when the alarm is no longer occurring." 370 INDEX { alarmListName, alarmActiveIndex } 371 ::= { alarmActiveTable 1 } 373 AlarmActiveEntry ::= SEQUENCE { 374 alarmListName SnmpAdminString, 375 alarmActiveIndex Unsigned32, 376 alarmActiveTime TimeStamp, 377 alarmActiveDateAndTime DateAndTime, 378 alarmActiveEngineID SnmpEngineID, 379 alarmActiveEngineAddress IpAddress, 380 alarmActiveContextEngineID SnmpEngineID, 381 alarmActiveContextName SnmpAdminString, 382 alarmActiveVariables Unsigned32, 383 alarmActiveNotificationID OBJECT IDENTIFIER, 384 alarmActiveTrendIndication INTEGER, 385 alarmActiveLogIndex Unsigned32, 386 alarmActiveDetailsIndex Unsigned32 } 388 alarmListName OBJECT-TYPE 389 SYNTAX SnmpAdminString (SIZE(0..32)) 390 MAX-ACCESS not-accessible 391 STATUS current 392 DESCRIPTION 393 "The name of the list of alarms. This is the same as 394 nlmLogName if the Nofication Log MIB is supported. 396 An implementation may allow multiple named alarm lists, up to 397 some implementation-specific limit (which may be none). A 398 zero-length list name is reserved for creation and deletion 399 by the managed system, and MUST be used as the default log 400 name by systems that do not support named alarm lists." 401 ::= { alarmActiveEntry 1 } 403 alarmActiveIndex OBJECT-TYPE 404 SYNTAX Unsigned32 (1..4294967295) 405 MAX-ACCESS read-only 406 STATUS current 407 DESCRIPTION 408 "A monotonically increasing integer which acts as the 409 index of entries within the named alarm list. It wraps 410 back to 1 after it reaches its maximum value." 411 ::= { alarmActiveEntry 2 } 413 alarmActiveTime OBJECT-TYPE 414 SYNTAX TimeStamp 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION 418 "The value of sysUpTime when the alarm occurred. Alarms tend 419 to get cleared and resent if still applicable at reboot, so this 420 value tends to be is a valid sysUptime. In the case where the 421 alarms are not cleared at reboot, and the alarm occurred before 422 the most recent management system initialization, this object 423 value MUST be set to zero." 425 ::= { alarmActiveEntry 3 } 427 alarmActiveDateAndTime OBJECT-TYPE 428 SYNTAX DateAndTime 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION 432 "The local date and time when the alarm occurred, instantiated 433 only by systems that have date and time capability." 434 ::= { alarmActiveEntry 4 } 436 alarmActiveEngineID OBJECT-TYPE 437 SYNTAX SnmpEngineID 438 MAX-ACCESS read-only 439 STATUS current 440 DESCRIPTION 441 "The identification of the SNMP engine at which the alarm 442 originated. 443 If the alarm list can contain Notifications from only one 444 engine or the Trap is from an SNMPv1 system, this object is not 445 instantiated." 446 ::= { alarmActiveEntry 5 } 448 alarmActiveEngineAddress OBJECT-TYPE 449 SYNTAX IpAddress 450 MAX-ACCESS read-only 451 STATUS current 452 DESCRIPTION 453 "The IP Address of the SNMP engine on which the alarm is 454 occurring. This is used to identify the source of an SNMPv1 455 trap, since an alarmActiveEngineId cannot be extracted from the 456 SNMPv1 trap pdu. 458 This object MUST always be instantiated, even if the list 459 can contain alarms from only one engine." 460 ::= { alarmActiveEntry 6 } 462 alarmActiveContextEngineID OBJECT-TYPE 463 SYNTAX SnmpEngineID 464 MAX-ACCESS read-only 465 STATUS current 466 DESCRIPTION 467 "If the alarm is occurring on a device using a protocol which 468 has a contextEngineID element like SNMPv3, this object has that 469 value. Otherwise its value is a zero-length string." 470 ::= { alarmActiveEntry 7 } 472 alarmActiveContextName OBJECT-TYPE 473 SYNTAX SnmpAdminString 474 MAX-ACCESS read-only 475 STATUS current 476 DESCRIPTION 477 "The name of the SNMP MIB context from which the alarm came. 478 For SNMPv1 Traps this is the community string from the Trap. 479 If the alarm's source SNMP engine is known not to support 480 multiple contexts, this object is not instantiated." 481 ::= { alarmActiveEntry 8 } 483 alarmActiveVariables OBJECT-TYPE 484 SYNTAX Unsigned32 485 MAX-ACCESS read-only 486 STATUS current 487 DESCRIPTION 488 "The number of variables in alarmActiveVariableTable for this 489 Notification." 490 ::= { alarmActiveEntry 9 } 492 alarmActiveNotificationID OBJECT-TYPE 493 SYNTAX OBJECT IDENTIFIER 494 MAX-ACCESS read-only 495 STATUS current 496 DESCRIPTION 497 "The NOTIFICATION-TYPE object identifier of the Notification 498 that occurred." 499 ::= { alarmActiveEntry 10 } 501 alarmActiveTrendIndication OBJECT-TYPE 502 SYNTAX INTEGER 503 { 504 moreSevere (1), 505 noChange (2), 506 lessSevere (3) 507 } 508 MAX-ACCESS read-only 509 STATUS current 510 DESCRIPTION 511 " Represents the trend indication values for the alarms 512 as per (ITU-T X.733)." 513 ::= { alarmActiveEntry 11 } 515 alarmActiveLogIndex OBJECT-TYPE 516 SYNTAX Unsigned32 (0..4294967295) 517 MAX-ACCESS read-only 518 STATUS current 519 DESCRIPTION 520 "This number can be considered a sequence number for the trap. 521 It should be the same as the log index in the notification log 522 MIB, if used. If no log index or sequence number applies to the 523 trap, then this object should have the value of 0." 524 ::= { alarmActiveEntry 12 } 526 alarmActiveDetailsIndex OBJECT-TYPE 527 SYNTAX Unsigned32 (0..4294967295) 528 MAX-ACCESS read-only 529 STATUS current 530 DESCRIPTION 531 "The index of the corresponding row in the alarmDetails table. 532 If the alarmDetails table is not supported this object should 533 have a value of 0." 534 ::= { alarmActiveEntry 13 } 536 -- -- Active Alarm Variable Table -- 538 alarmActiveVariableTable OBJECT-TYPE 539 SYNTAX SEQUENCE OF AlarmActiveVariableEntry 540 MAX-ACCESS not-accessible 541 STATUS current 542 DESCRIPTION 543 "A table of variables to go with active alarm entries." 544 ::= { alarmObjects 3 } 546 alarmActiveVariableEntry OBJECT-TYPE 547 SYNTAX AlarmActiveVariableEntry 548 MAX-ACCESS not-accessible 549 STATUS current 550 DESCRIPTION 551 "Entries appear in this table when there are variables in 552 the varbind list of a corresponding alarm in alarmActiveTable." 553 INDEX { alarmListName, alarmActiveIndex, alarmActiveVariableIndex 554 } 555 ::= { alarmActiveVariableTable 1 } 557 AlarmActiveVariableEntry ::= SEQUENCE { 558 alarmActiveVariableIndex Unsigned32, 559 alarmActiveVariableID OBJECT IDENTIFIER, 560 alarmActiveVariableValueType INTEGER, 561 alarmActiveVariableCounter32Val Counter32, 562 alarmActiveVariableUnsigned32Val Unsigned32, 563 alarmActiveVariableTimeTicksVal TimeTicks, 564 alarmActiveVariableInteger32Val Integer32, 565 alarmActiveVariableOctetStringVal OCTET STRING, 566 alarmActiveVariableIpAddressVal IpAddress, 567 alarmActiveVariableOidVal OBJECT IDENTIFIER, 568 alarmActiveVariableCounter64Val Counter64, 569 alarmActiveVariableOpaqueVal Opaque } 571 alarmActiveVariableIndex OBJECT-TYPE 572 SYNTAX Unsigned32 (1..4294967295) 573 MAX-ACCESS not-accessible 574 STATUS current 575 DESCRIPTION 576 "A monotonically increasing integer, starting at 1 for a given 577 alarmActiveIndex, for indexing variables within the active 578 alarm list." 579 ::= { alarmActiveVariableEntry 1 } 581 alarmActiveVariableID OBJECT-TYPE 582 SYNTAX OBJECT IDENTIFIER 583 MAX-ACCESS read-only 584 STATUS current 585 DESCRIPTION 586 "The variable's object identifier." 587 ::= { alarmActiveVariableEntry 2 } 589 alarmActiveVariableValueType OBJECT-TYPE 590 SYNTAX INTEGER { counter32(1), unsigned32(2), timeTicks(3), 591 integer32(4), ipAddress(5), octetString(6), 592 objectId(7), counter64(8), opaque(9) } 593 MAX-ACCESS read-only 594 STATUS current 595 DESCRIPTION 596 "The type of the value. One and only one of the value 597 objects that follow is used, based on this type." 598 ::= { alarmActiveVariableEntry 3 } 600 alarmActiveVariableCounter32Val OBJECT-TYPE 601 SYNTAX Counter32 602 MAX-ACCESS read-only 603 STATUS current 604 DESCRIPTION 605 "The value when alarmActiveVariableType is 'counter32'." 606 ::= { alarmActiveVariableEntry 4 } 608 alarmActiveVariableUnsigned32Val OBJECT-TYPE 609 SYNTAX Unsigned32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The value when alarmActiveVariableType is 'unsigned32'." 615 ::= { alarmActiveVariableEntry 5 } 617 alarmActiveVariableTimeTicksVal OBJECT-TYPE 618 SYNTAX TimeTicks 619 MAX-ACCESS read-only 620 STATUS current 621 DESCRIPTION 622 "The value when alarmActiveVariableType is 'timeTicks'." 623 ::= { alarmActiveVariableEntry 6 } 625 alarmActiveVariableInteger32Val OBJECT-TYPE 626 SYNTAX Integer32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION 630 "The value when alarmActiveVariableType is 'integer32'." 631 ::= { alarmActiveVariableEntry 7 } 633 alarmActiveVariableOctetStringVal OBJECT-TYPE 634 SYNTAX OCTET STRING 635 MAX-ACCESS read-only 636 STATUS current 637 DESCRIPTION 638 "The value when alarmActiveVariableType is 'octetString'." 639 ::= { alarmActiveVariableEntry 8 } 641 alarmActiveVariableIpAddressVal OBJECT-TYPE 642 SYNTAX IpAddress 643 MAX-ACCESS read-only 644 STATUS current 645 DESCRIPTION 646 "The value when alarmActiveVariableType is 'ipAddress'." 647 ::= { alarmActiveVariableEntry 9 } 649 alarmActiveVariableOidVal OBJECT-TYPE 650 SYNTAX OBJECT IDENTIFIER 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION 654 "The value when alarmActiveVariableType is 'objectId'." 655 ::= { alarmActiveVariableEntry 10 } 657 alarmActiveVariableCounter64Val OBJECT-TYPE 658 SYNTAX Counter64 659 MAX-ACCESS read-only 660 STATUS current 661 DESCRIPTION 662 "The value when alarmActiveVariableType is 'counter64'." 664 ::= { alarmActiveVariableEntry 11 } 666 alarmActiveVariableOpaqueVal OBJECT-TYPE 667 SYNTAX Opaque 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION 671 "The value when alarmActiveVariableType is 'opaque'." 672 ::= { alarmActiveVariableEntry 12 } 674 -- -- Statistics -- 676 alarmActiveStatsTable OBJECT-TYPE 677 SYNTAX SEQUENCE OF AlarmActiveStatsEntry 678 MAX-ACCESS not-accessible 679 STATUS current 680 DESCRIPTION 681 "This table represents the alarm statistics type 682 information." 683 ::= { alarmObjects 4 } 685 alarmActiveStatsEntry OBJECT-TYPE 686 SYNTAX AlarmActiveStatsEntry 687 MAX-ACCESS not-accessible 688 STATUS current 689 DESCRIPTION 690 "Statistics on the current active alarms." 692 INDEX { alarmListName } 694 ::= { alarmActiveStatsTable 1 } 696 AlarmActiveStatsEntry ::= 697 SEQUENCE { 698 alarmActiveStatsTotalActive Unsigned32 699 } 701 alarmActiveStatsTotalActive OBJECT-TYPE 702 SYNTAX Unsigned32 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION 706 "The total number of currently active alarms on the system." 708 ::= { alarmActiveStatsEntry 1 } 710 -- Conformance Stuff 712 alarmConformance OBJECT IDENTIFIER ::= { alarm 2 } 714 alarmDetailsGroup OBJECT-GROUP 715 OBJECTS { 716 alarmDetailsIndex, 717 alarmDetailsNotificationId, 718 alarmDetailsClearNotificationId, 719 alarmDetailsEventType, 720 alarmDetailsProbableCause, 721 alarmDetailsPerceivedSeverity, 722 alarmDetailsAdditionalText 723 } 724 STATUS current 725 DESCRIPTION 726 "Alarm details list group." 727 ::= { alarmConformance 2} 729 alarmActiveListGroup OBJECT-GROUP OBJECTS { 730 alarmListName, 731 alarmActiveIndex, 732 alarmActiveTime, 733 alarmActiveDateAndTime, 734 alarmActiveEngineID, 735 alarmActiveEngineAddress, 736 alarmActiveContextEngineID, 737 alarmActiveContextName, 738 alarmActiveVariables, 739 alarmActiveNotificationID, 740 alarmActiveLogIndex, 741 alarmActiveVariableIndex, 742 alarmActiveVariableID, 743 alarmActiveVariableValueType, 744 alarmActiveVariableCounter32Val, 745 alarmActiveVariableUnsigned32Val, 746 alarmActiveVariableTimeTicksVal, 747 alarmActiveVariableInteger32Val, 748 alarmActiveVariableOctetStringVal, 749 alarmActiveVariableIpAddressVal, 750 alarmActiveVariableOidVal, 751 alarmActiveVariableCounter64Val, 752 alarmActiveVariableOpaqueVal 753 } STATUS current 754 DESCRIPTION 755 "Active Alarm list group." 756 ::= { alarmConformance 3} 758 alarmActiveSummaryGroup OBJECT-GROUP 759 OBJECTS { 760 alarmActiveStatsTotalActive 761 } 762 STATUS current 763 DESCRIPTION 764 " Active alarm summary group." 765 ::= { alarmConformance 4} 767 alarmCompliance MODULE-COMPLIANCE 768 STATUS current 769 DESCRIPTION 770 "The compliance statement for systems supporting 771 the Alarm MIB." 772 MODULE -- this module 773 MANDATORY-GROUPS { 774 alarmActiveListGroup 775 } 776 GROUP alarmActiveSummaryGroup 777 DESCRIPTION 778 "The actual active alarms." 780 ::= { alarmConformance 1 } END 782 8. Example 784 Define the following Object: 785 acmeWidgetIndex OBJECT-TYPE 786 SYNTAX Integer32 787 MAX-ACCESS read-only 788 STATUS current 789 DESCRIPTION 790 "A unique number which identifies a particular Widget." 791 ::= { acmeWidgetEntry 1 } 793 Define the following three traps: 794 acmeWidgetTemperatureCritical NOTIFICATION-TYPE 795 OBJECTS { acmeWidgetIndex } 796 STATUS current 797 DESCRIPTION 798 "This trap indicates that the indicated 799 widget has reached a critical temperature." 800 ::= { acmeWidgetTraps 1 } 802 acmeWidgetTemperatureNormal NOTIFICATION-TYPE 803 OBJECTS { acmeWidgetIndex } 804 STATUS current 805 DESCRIPTION 806 "This trap indicates that the indicated widget has 807 reached a normal temperature." 808 ::= { acmeWidgetTraps 2 } 810 bgpBackwardTransition NOTIFICATION-TYPE 811 OBJECTS { bgpPeerLastError, 812 bgpPeerState } 813 STATUS current 814 DESCRIPTION 815 "The BGPBackwardTransition Event is generated 816 when the BGP FSM moves from a higher numbered 817 state to a lower numbered state." 818 ::= { bgpTraps 2 } 820 0. Active alarm table empty and nothing in notification log 821 ___________________________ _____________________ 822 | alarmActiveTable | | nlmLogTable | 823 |---------------------------| |---------------------| 824 | alarmActiveIndex | alarm | | nlmLogIndex | alarm | 825 |---------------------------| |---------------------| 826 |___________________________| |_____________________| 828 1. Temperature of widget 2 goes critical 829 __________________________________________________ 830 | alarmActiveTable | 831 |--------------------------------------------------| 832 | alarmActiveIndex | alarm | 833 |--------------------------------------------------| 834 | 1 | acmeWidgetTemperatureCritical | 835 |__________________________________________________| 837 _____________________________________________ 838 | nlmLogTable | 839 |---------------------------------------------| 840 | nlmLogIndex | alarm | 841 |---------------------------------------------| 842 | 1 | acmeWidgetTemperatureCritical | 843 |_____________________________________________| 845 2. BGP peering session transitions from a state of established 846 to opensent 847 __________________________________________________ 848 | alarmActiveTable | 849 |--------------------------------------------------| 850 | alarmActiveIndex | alarm | 851 |--------------------------------------------------| 852 | 1 | acmeWidgetTemperatureCritical | 853 | 2 | bgpBackwardTransition | 854 |__________________________________________________| 856 _____________________________________________ 857 | nlmLogTable | 858 |---------------------------------------------| 859 | nlmLogIndex | alarm | 860 |---------------------------------------------| 861 | 1 | acmeWidgetTemperatureCritical | 862 | 2 | bgpBackwardTransition | 863 |_____________________________________________| 865 3. Temperature of widget 2 goes back to normal 866 __________________________________________________ 867 | alarmActiveTable | 868 |--------------------------------------------------| 869 | alarmActiveIndex | alarm | 870 |--------------------------------------------------| 871 | 2 | bgpBackwardTransition | 872 |__________________________________________________| 874 _____________________________________________ 875 | nlmLogTable | 876 |---------------------------------------------| 877 | nlmLogIndex | alarm | 878 |---------------------------------------------| 879 | 1 | acmeWidgetTemperatureCritical | 880 | 2 | bgpBackwardTransition | 881 | 3 | acmeWidgetTemperatureNormal | 882 |_____________________________________________| 884 4. Time passes .... BGP alarm ages out. 886 __________________________________________________ 887 | alarmActiveTable | 888 |--------------------------------------------------| 889 | alarmActiveIndex | alarm | 890 |--------------------------------------------------| 891 |__________________________________________________| 892 _____________________________________________ 893 | nlmLogTable | 894 |---------------------------------------------| 895 | nlmLogIndex | alarm | 896 |---------------------------------------------| 897 | 1 | acmeWidgetTemperatureCritical | 898 | 2 | bgpBackwardTransition | 899 | 3 | acmeWidgetTemperatureNormal | 900 |_____________________________________________| 902 9. Security Considerations 904 There are no management objects defined in this MIB that have a MAX- 905 ACCESS clause of read-write and/or read-create. So, if this MIB is 906 implemented correctly, then there is no risk that an intruder can 907 alter or create any management objects of this MIB via direct SNMP 908 SET operations. 910 10. Author's Address 912 Sharon Chisholm 913 Nortel Networks 914 PO Box 3511, Station C 915 Ottawa, Ontario, K1Y 4H7 916 Canada 918 Email: schishol@nortelnetworks.com 920 11. References 921 [1] Stewart, B, Kavasseri, R, "Notification Log MIB, 922 draft 17, October 2000 923 [2] ITU Recommendation X.733, "Information Technology - Open 924 Systems Interconnection - System Management: Alarm Reporting 925 Function", 1992 926 [3] ITU Recommendation X.736, "Information Technology - Open 927 Systems Interconnection - System Management: Security Alarm 928 Reporting Function", 1992 930 12. Full Copyright Statement 932 Copyright (C) The Internet Society (2000). All Rights Reserved. 934 This document and translations of it may be copied and furnished to 935 others, and derivative works that comment on or otherwise explain it or 936 assist in its implementation may be prepared, copied, published and 937 distributed, in whole or in part, without restriction of any kind, 938 provided that the above copyright notice and this paragraph are included 939 on all such copies and derivative works. However, this document itself 940 may not be modified in any way, such as by removing the copyright notice 941 or references to the Internet Society or other Internet organizations, 942 except as needed for the purpose of developing Internet standards in 943 which case the procedures for copyrights defined in the Internet 944 Standards process must be followed, or as required to translate it into 945 languages other than English. 947 The limited permissions granted above are perpetual and will not be 948 revoked by the Internet Society or its successors or assigns. 950 This document and the information contained herein is provided on an "AS 951 IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING TASK 952 FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT 953 LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT 954 INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR 955 FITNESS FOR A PARTICULAR PURPOSE.