idnits 2.17.1 draft-ietf-disman-alarm-mib-16.txt: 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 the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- == There are 1 instance of lines with non-RFC6890-compliant IPv4 addresses in the document. If these are example addresses, they should be changed. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 2791 has weird spacing: '...ication mor...' == Line 3464 has weird spacing: '...for the purpo...' == The document seems to use 'NOT RECOMMENDED' as an RFC 2119 keyword, but does not include the phrase in its RFC 2119 key words list. -- 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.) -- The document date (November 2003) is 7461 days in the past. Is this intentional? Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2026' is defined on line 3365, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 3384, but no explicit reference was found in the text == Unused Reference: 'RFC2737' is defined on line 3426, but no explicit reference was found in the text == Unused Reference: 'RFC2788' is defined on line 3429, but no explicit reference was found in the text ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Obsolete normative reference: RFC 3291 (Obsoleted by RFC 4001) -- Obsolete informational reference (is this intentional?): RFC 1657 (Obsoleted by RFC 4273) -- Obsolete informational reference (is this intentional?): RFC 1759 (Obsoleted by RFC 3805) -- Obsolete informational reference (is this intentional?): RFC 2737 (Obsoleted by RFC 4133) Summary: 5 errors (**), 0 flaws (~~), 9 warnings (==), 5 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Disman Working Group S. Chisholm 2 Internet Draft Nortel Networks 3 Document: draft-ietf-disman-alarm-mib-16.txt D. Romascanu 4 Category: Standards Track Avaya 5 Expiration Date: May 2004 November 2003 7 Alarm MIB 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance 12 with all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as 17 Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as 23 "work in progress." 25 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Copyright Notice 34 Copyright (C) The Internet Society (2003). All Rights Reserved. 36 Abstract 38 This memo defines a portion of the Management Information Base (MIB) 39 for use with network management protocols in the Internet community. 40 In particular, it describes management objects used for modelling 41 and storing alarms. 43 Table of Contents 45 1. The Internet-Standard Management Framework 46 2. Introduction 47 3. Alarm Management Framework 48 3.1. Terminology 49 3.2. Alarm Management Architecture 50 3.3. Features of this Architecture 51 3.4. Security 52 3.5. Relationship between Alarm and Notifications 53 3.6. Notification Varbind Storage and Reference 54 3.7. Relation to Notification Log MIB 55 3.8. Relation to Event MIB 56 4. Generic Alarm MIB 57 4.1. Overview 58 4.2. Definitions 59 5. ITU Alarm 60 5.1. Overview 61 5.2. IANA Considerations 62 5.3. Textual Conventions 63 5.4. Definitions 64 6. Examples 65 6.1. Alarms Based on linkUp/linkDown Notifications 66 6.2. Temperature Alarm using generic Notifications 67 6.3. Temperature Alarm without Notifications 68 6.4. Printer MIB Alarm Example 69 6.5. Rmon Alarm Example 70 6.6. The Lifetime of an Alarm 71 7. Security Considerations 72 8. Authors' Addresses 73 9. Acknowledgements 74 10. Intellectual Property 75 11. References 76 12. Full Copyright Statement 77 1. The Internet-Standard Management Framework 79 For a detailed overview of the documents that describe the current 80 Internet-Standard Management Framework, please refer to section 7 of 81 RFC 3410 [RFC3410]. 83 Managed objects are accessed via a virtual information store, termed 84 the Management Information Base or MIB. MIB objects are generally 85 accessed through the Simple Network Management Protocol (SNMP). 86 Objects in the MIB are defined using the mechanisms defined in the 87 Structure of Management Information (SMI). This memo specifies a MIB 88 module that is compliant to the SMIv2, which is described in STD 58, 89 RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and STD 58, RFC 2580 90 [RFC2580]. 92 2. Introduction 94 In traditional SNMP management, problems are detected on an entity 95 either through polling interesting MIB variables, waiting for the 96 entity to send a Notification for a problem, or some combination of 97 the two. This method is somewhat successful, but experience has 98 shown some problems with this approach. Managers monitoring large 99 numbers of entities cannot afford to be polling large numbers of 100 objects on each device. Managers trying to ensure high reliability 101 are unable to accurately determine whether any problems had occurred 102 when they were not monitoring an entity. Finally, it can be time 103 consuming for managers to try to understand the relationships 104 between the various objects they poll, the Notifications they 105 receive and the problems occurring on the entity. Even after 106 detailed analysis they may still be left with an incomplete picture 107 of what problems are occurring. But, it is important for an operator 108 to be able to determine current problems on a system, so they can be 109 fixed. 111 This memo describes a method of using alarm management in SNMP to 112 address these problems. It also provides the necessary MIB objects 113 to support this method. 115 Alarms and other terms related to alarm management are defined in 116 the following sections. 118 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 119 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 120 document are to be interpreted as described in RFC 2119 [RFC2119]. 122 3. Alarm Management Framework 123 3.1 Terminology 125 Error 126 A deviation of a system from normal operation. 128 Fault 129 Lasting error or warning condition. 131 Event 132 Something that happens which may be of interest. 133 A fault, a change in status, crossing a threshold, or an 134 external input to the system, for example. 136 Notification 137 Unsolicited transmission of management information. 139 Alarm 140 Persistent indication of a fault. 142 Alarm State 143 A condition or stage in the existence of an alarm. As a minimum, 144 alarms states are raise and clear. They could also 145 include severity information such as defined by perceived severity 146 in the International Telecommunications Union (ITU) model [M.3100] 147 - cleared, indeterminate, critical, major, minor and warning. 149 Alarm Raise 150 The initial detection of the fault indicated by an alarm or any 151 number of alarm states later entered, except clear. 153 Alarm Clear 154 The detection that the fault indicated by an alarm no longer 155 exists. A Notification SHOULD be sent on alarm clear. 157 Active Alarm 158 An alarm which has an alarm state that has been raised, but not 159 cleared. 161 Alarm Detection Point 162 The entity that detected the alarm. 164 Perceived Severity 165 The severity of the alarm as determined by the alarm detection 166 point using the information it has available. 168 3.2 Alarm Management Architecture 169 +------------------------------------------------+ 170 | | 171 | +------------------------------------+ | 172 | | Notification Management | | 173 | +--------------+---------------------+ | 174 | | | 175 +------------------+-----------------------------+ 176 | 177 V 178 | 179 |<----------------------------------------------+ 180 | | 181 +------------------V-------------+ | 182 | +---------------V-----------+ | | 183 | | RFC 3413 | | | 184 | | SNMP-NOTIFICATION-MIB | | | 185 | +--------+--------------+-+-+ | | 186 | | | | | | 187 | | | +------------------+ | 188 | | | | | | 189 | | | | +----------V--------------+ | 190 | | | | | +--------V---------+ | | 191 | +---------V------------+ | | | | Alarm Modelling | | | 192 | | RFC 3014 | | | | | (descriptions) | | | 193 | | NOTIFICATION-LOG-MIB | | | | +--------+---------+ | | 194 | +----------------------+ | | | | | | 195 | | | | +--------V------------+ | | 196 | +------------------------V-+ | | | Generic: Model- | | | 197 | | RFC 3413 | | | | Active : Specific | | | 198 | | SNMP-TARGET-MIB | | | | Alarms : Extensions | | | 199 | +----------+---------------+ | | +--------+------------+ | | 200 | | | | | | | 201 +------------|-------------------+ +----------|--------------+ | 202 | | | 203 | +------------------+ 204 V 205 Informs & Traps 207 3.3 Features of this Architecture 209 3.3.1 Modular Alarm Architecture 211 The subject of alarm management can potentially cover a large number 212 of topics including real-time alarms, historical alarms, alarm 213 correlation, and alarm suppression, to name a few. Within each of 214 these topics, there are a number of established models that could be 215 supported. This memo focuses on a subset of this problem space, but 216 describes a modular SNMP alarm management framework. 218 The framework defines a generic Alarm MIB that can be supported on 219 its own, or with additional alarm modelling information such as the 220 provided ITU Alarm MIB. In addition, the active alarm tables could 221 also be extended to support additional information about active 222 alarm instances. This framework can also be expanded in the future 223 to support such features as alarm correlation and alarm suppression. 224 This modular architecture means that the cost of supporting alarm 225 management features is proportional to the number of features an 226 implementation supports. 228 3.3.2 Flexible Alarm Modelling 230 Alarm models document an understanding between a manager and an 231 agent as to what problems will be reported on a system, how these 232 problems will be reported, and what might possibly happen over the 233 lifetime of this problem. 235 The alarm modelling method provided in this memo provides 236 flexibility to support implementations with different modelling 237 requirements. All alarms are modelled as a series of states that are 238 related together using an alarm ID. Alarm states can be modelled 239 using traditional Notifications, generic alarm Notifications, or 240 without the use of Notifications. 242 Alarm states modelled using traditional Notifications would specify 243 a Notification Object Identifier, and optionally an (offset, value) 244 pair of one of the Notification varbinds to identify the state. 245 This alarm state would be entered when the entity generated a 246 Notification that matched this information and the alarm would be 247 added to the active alarm table. This Notification would also get 248 sent on the wire to any destinations, as indicated in the 249 SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB [RFC3413]. 251 Alarm states modelled using generic Notifications use the 252 alarmActiveState or alarmClearState Notifications defined in this 253 memo. These alarm states would be entered after being triggered by a 254 stimulus outside the scope of this memo, the alarm would be added to 255 the active alarm table and these generic Notifications would then be 256 sent on the wire to any destinations, as indicated in the 257 SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB [RFC3413]. 259 Alarm states modelled without any Notifications would be triggered 260 by some stimulus outside the scope of this memo, the alarm would be 261 added to the active alarm table, but no Notifications would be sent 262 to interested managers. 264 3.3.3 Problem Indication 266 The Alarm MIB provides a means to determine whether a given 267 notification is of interest to managers for purposes of alarm 268 management by permitting inspection of the alarm models. If no 269 entries in the alarmModelTable could match a particular 270 notification, then that notification is not relevant to the alarm 271 models defined. In addition, information in the alarm model, such 272 as the Notification ID and the description tell exactly what error 273 or warning condition this alarm is indicating. If the ITU-ALARM-MIB 274 is also supported, additional information is provided via the 275 probable cause. 277 3.3.5 Identifying Resource under Alarm 279 An important goal of alarm management is to ensure that any detected 280 problems get fixed, so it is necessary to know exactly where this 281 problem is occurring. In addition, it is necessary to be able to 282 tell when alarm instances are raised against the same component, as 283 well as to be able to tell what instance of an alarm is cleared by 284 an instance of an alarm clear. 286 The Alarm MIB provides a generic method for identifying the resource 287 by extracting and building a resource ID from the Notification 288 varbinds. It records the relevant information needed to locate the 289 source of the alarm. 291 3.3.6 Means of obtaining ITU alarm information 293 Alarm Information, as defined in ITU alarm models [M.3100], is 294 optionally available to implementations through the optional support 295 of the ITU-ALARM-MIB. 297 3.3.7 Configuration of Alarm Models 299 An alarm model can be added and removed during runtime. It can be 300 modified assuming it is not being referenced by any active alarm 301 instance. 303 3.3.8 Active Alarm Management 305 A list of currently active alarms and supporting statistics on the 306 SNMP entity can be obtained. 308 This allows the network management station to find out about any 309 problems that may have occurred before it started managing a 310 particular network element, or while it was out of contact with it. 312 3.3.9 Distributed Alarm Management 314 All aspects of the Alarm MIB can be supported both on the device 315 experiencing the alarms and on any mid-level managers that might be 316 monitoring such devices. 318 3.3.10 Historical Alarm Management 320 Some systems may have a requirement that information on alarms that 321 are no longer active is available. This memo provides a clear table 322 to support this requirement. 324 This can also be achieved through the support of the Notification 325 Log MIB [RFC3014] to store alarm state transitions. 327 3.4 Security 329 Security for alarms is awkward since access control for the objects 330 in the underlying Notifications can be checked only where the 331 Notification is created. Thus such checking is possible only for 332 locally generated Notifications, and even then only when security 333 credentials are available. 335 For the purpose of this discussion, "security credentials" means the 336 input values for the abstract service interface function 337 isAccessAllowed [RFC3411] and using those credentials means 338 conceptually using that function to see that those credentials allow 339 access to the MIB objects in question, operating as for a 340 Notification Originator in [RFC3413]. 342 The Alarm MIB has the notion of a named alarm list. By using alarm 343 list names and view-based access control [RFC3415] a network 344 administrator can provide different access for different users. When 345 an application creates an alarm model (indexed in part by the alarm 346 list name) the security credentials of the creator remain associated 347 with that alarm model and constrain what information is allowed to 348 be placed in the active alarm table, the active alarm variable 349 table, the cleared alarm table, and the ITU alarm table. 351 When processing locally-generated Notifications, the managed system 352 MUST use the security credentials associated with each alarm model 353 respectively, and MUST apply the same access control rules as 354 described for a Notification Originator in [RFC3413]. 356 The managed system SHOULD NOT apply access control when processing 357 remotely-generated Notifications using the alarm models. In those 358 cases the security of the information in the alarm tables SHOULD be 359 left to the normal, overall access control for those tables. 361 3.5 Relationship between Alarm and Notifications 363 It is important to understand the relationship between alarms and 364 Notifications, as both are traditional fault management methods. 365 This relationship is modelled using the alarmModelTable to define 366 the alarmModelNotificationId for each alarm state. 368 Not all Notifications signal an alarm state transition. Some 369 Notifications are simply informational in nature, such as those that 370 indicate that a configuration operation has been performed on an 371 entity. These sorts of Notifications would not be represented in 372 the Alarm MIB. 374 The Alarm MIB allows the use of the Notification space as defined in 376 [RFC2578] in order to identify the Notifications that are related 377 with the specific alarm state transitions. However there is no 378 assumption that the respective Notifications MUST be sent for all or 379 any of the alarm state transitions. It is also possible to model 380 alarms using no Notifications at all. This architecture allows for 381 both the efficient exploitation of the body of defined Notification 382 and for the use of non-Notification based systems. 384 3.6 Notification Varbind Storage and Reference 386 In SNMPv1 [RFC1157], the varbinds in the Trap-PDU sent over the wire 387 map one to one into those varbinds listed in the SMI of the trap in 388 the MIB in which it was defined[RFC1215]. In the case of linkDown 389 trap, the first varbind can unambiguously be identified as ifIndex. 390 With the introduction of the InformRequest-PDU and SNMPv2-Trap-PDU 391 types, which send sysUptime and snmpTrapOID as the first two 392 varbinds, while the SMI in the MIB where the Notification is defined 393 only lists additional varbinds, the meaning of "first varbind" 394 becomes less clear. In the case of the linkDown Notification, 395 referring to the first varbind could potentially be interpreted as 396 either the sysUptime or ifIndex. 398 The varbind storage approach taken in the Alarm MIB is that 399 sysUptime and snmpTrapOID SHALL always be stored in the active alarm 400 variable table as entry 1 and 2 respectively, regardless of whether 401 the transport was the Trap-PDU, the InformRequest-PDU or the 402 SNMPv2-Trap-PDU. If the incoming Notification is an SNMPv1 Trap-PDU 403 then an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be 404 determined by using the rules in section 3.1 of [RFC3584]. 406 The varbind reference approach taken in the Alarm MIB is that, for 407 variables such as the alarmModelVarbindIndex, the first two 408 obligatory varbinds of the InformRequest-PDU and SNMPv2-Trap-PDU 409 need to be considered so the index values of the Trap-PDU and the 410 SMI need be adjusted by two. In the case of linkDown, the third 411 varbind would always be ifIndex. 413 3.7 Relation to Notification Log MIB 415 The Alarm MIB is intended to complement the Notification Log 416 MIB[RFC3014], but can be used independently. The alarmActiveTable 417 is defined in manner similar to that of the nlmLogTable. This 418 format allows for the storage of any Trap or Notification type that 419 can be defined using the SMI, or can be carried by SNMP. Using the 420 same format as the Notification Log MIB also simplifies operations 421 for systems choosing to implement both MIBs. 423 The object alarmActiveLogPointer points, for each entry in the 424 alarmActiveLogTable, to the log index in the Notification Log MIB, 425 if used. 427 If the Notification Log MIB is supported, it can be monitored by a 428 management system as a hedge against lost alarms. The Notification 429 Log can also be used to support historical alarm management. 431 3.8 Relationship with the Event MIB 433 During the work and discussions in the Working Group, the issue of 434 the relationship between the MIB modules and the Event MIB [RFC2981] 435 was raised. There is no direct relation or dependency between the 436 Alarm MIB and the Event MIB. Some common terms (like 'event') are 437 being used in both MIB modules, and the user is directed to the 438 sections that define terminology in the two documents for 439 clarification. 441 4. Generic Alarm MIB 443 4.1 Overview 445 The ALARM-MIB consists of alarm models and lists of active and 446 cleared alarms. 448 The alarmModelTable contains information that is applicable to all 449 instances of an alarm. It can be populated at start-up with all 450 alarms that could happen on a system or later configured by a 451 management application. It contains all the alarms for a given 452 system. If a Notification is not represented in the 453 alarmModelTable, it is not an alarm state transition. The 454 alarmModelTable provides a means of defining the raise/clear and 455 other state transition relationships between alarm states. The 456 alarmModelIndex acts as a unique identifier for an alarm. An alarm 457 model consists of definitions of the possible states an alarm can 458 assume as well as the Object Identifier (OID) of the Notification 459 associated with this alarm state. The object alarmModelState defines 460 the states of an alarm. 462 The alarmActiveTable contains a list of alarms that are currently 463 occurring on a system. It is intended that this table be queried 464 upon device discovery and rediscovery to determine which alarms are 465 currently active on the device. 467 The alarmActiveVariableTable contains the Notification variable 468 bindings associated with the alarms in the alarmActiveTable. 470 The alarmActiveStatsTable contains current and total raised alarm 471 counts as well as the time of the last alarm raise and alarm clears 472 per named alarm list. 474 The alarmClearTable contains recently cleared alarms. It contains up 475 to alarmClearMaximum cleared alarms. 477 The MIB also defines generic alarm Notifications that can be used 478 when there is not an existing applicable Notification to signal the 479 alarm state transition - alarmActiveState and alarmClearState. 481 4.1.1 Extensibility 483 The relationship between the Alarm MIB and the other alarm model MIB 484 modules is expressed by the following: The alarmModelTable has a 485 corresponding table in the specific MIB. For each row in the 486 specific MIB alarm model table there is one row in the 487 alarmModelTable. The alarmActiveTable has a corresponding table in 488 the specific MIBs. For each row in the specific MIB active alarm 489 table, there is one row in the alarmActiveTable. The 490 alarmModelSpecificPointer object in the alarmModelTable points to 491 the specific model entry in an extended alarm model table 492 corresponding to this particular alarm. The 493 alarmActiveSpecificPointer object in the alarmActiveTable points to 494 the specific active alarm entry in an extended active alarm table 495 corresponding to this particular alarm instance. 497 Additional extensions can be defined by defining an AUGEMENTATION of 498 either the Alarm or ITU Alarm tables. As the alarm model table only 499 provides a mechanism to point at one specific alarm model, 500 additional specific models SHOULD define another mechanism to map 501 from the generic alarm model to the additional model. 503 4.1.2 Problem Indication 505 The problem that each alarm indicates is identified through the 506 Object Identifier of the NotificationId of the state transition, 507 and, optionally, the ITU parameters. alarmModelDescription provides 508 a description of the alarm state suitable for displaying to an 509 operator. 511 4.1.3 Alarm State Transition Notification 513 The SNMP-TARGET-MIB [RFC3413] provides the ability to specify which 514 managers, if any, receive Notifications of problems. Solutions can 515 therefore use the features of this MIB to change the Notification 516 behaviour of their implementations. Specifying target hosts in this 517 MIB along with specifying notifications in the 518 alarmModelNotificationId would allow Notifications to be logged and 519 sent out to management stations in an architecture as described in 520 section 3.2. Specifying no target hosts in this MIB along with 521 specifying notifications in the alarmModelNotificationId would allow 522 Notifications to be logged but not sent out to management stations 523 in an architecture as described in section 3.2. Regardless of what 524 is defined in the SNMP-TARGET-MIB, specifying { 0 0 } in the 525 alarmModelNotificationId would result in no notifications being 526 logged or sent to management stations as a consequence of this 527 particular alarm state transition. 529 Alarms are modelled by defining all possible states in the 530 alarmModelTable, as well as defining alarmModelNotificationId, 531 alarmModelVarbindIndex, and alarmModelVarbindValue for each of the 532 possible alarm states. Optionally, ituAlarmPerceivedSeverity models 533 the states in terms of ITU perceived severity. 535 4.1.4 Active Alarm Resource Identifier 537 Resources under alarm can be identified using the 538 alarmActiveResourceId. This OBJECT IDENTIFIER points to an 539 appropriate object to identify the given resource, depending on the 540 type of the resource. 542 The consumer of the alarmActiveResourceId does not necessarily need 543 to know the type of the resource in the resource ID, but if they 544 want to know this, examining the content of the resource ID can 545 derive it - 1.3.6.1.2.1.2.2.1.1.something is an interface, for 546 example. It is therefore good practice to use resource IDs that can 547 be consistently used across technologies, such as ifIndex, 548 entPhysicalIndex or sysApplRunIndex, to minimize the number of 549 resource prefixes a manager interested in a resource type needs to 550 learn. 552 Resource ID can be calculated using the alarmModelResourcePrefix, 553 alarmModelVarbindSubtree and the Notification varbinds. This allows 554 for both the managed element to be able to compute and populate the 555 alarmActiveResourceId object and for the manager to be able to 556 determine when two separate alarm instances are referring to the 557 same resource. 559 If alarmModelResourcePrefix has a value of 0.0, then 560 alarmActiveResourceId is simply the variable identifier of the first 561 Notification varbind that matches the prefix defined in 562 alarmModelVarbindSubtree. Otherwise, alarmActiveResourceId is 563 calculated by appending the instance information from the first 564 Notification varbind that matches alarmModelVarbindSubtree to the 565 prefix defined in alarmModelResourcePrefix. The instance information 566 is the portion of the variable identifier following the part that 567 matched alarmModelVarbindSubtree. If no match is found, then 568 alarmActiveResourceId is simply the value of 569 alarmModelResourcePrefix. 571 In addition to this, the variable bindings from the Notifications 572 that signal the alarm state transitions are stored in the active 573 alarm variable table. This allows for implementations familiar with 574 the particular Notifications to implement other forms of resource 575 identification. 577 For Example: 579 A) Consider an alarm modelled using the authenticationFailure 580 [RFC3418] Notification. 582 authenticationFailure NOTIFICATION-TYPE 583 STATUS current 584 DESCRIPTION 585 "An authenticationFailure trap signifies that the SNMPv2 586 entity, acting in an agent role, has received a protocol 587 message that is not properly authenticated. While all 588 implementations of the SNMPv2 must be capable of generating 589 this trap, the snmpEnableAuthenTraps object indicates 590 whether this trap will be generated." 591 ::= { snmpTraps 5 } 593 To set the resource ID to be usmStats, 1.3.6.1.6.3.15.1.1, 594 configure as follows: 595 alarmModelVarbindSubtree = 0.0 596 alarmModelResourcePrefix = usmStats (1.3.6.1.6.3.15.1.1) 598 B) Consider an alarm modelled using linkDown [RFC2863] 600 linkDown NOTIFICATION-TYPE 601 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 602 STATUS current 603 DESCRIPTION 604 "" 605 ::= { snmpTraps 3 } 607 To set the resource Id to be the ifIndex, configure as follows: 608 alarmModelVarbindSubtree = ifIndex (1.3.6.1.2.1.2.2.1.1) 609 alarmModelResourcePrefix = 0.0 611 Alternatively, since ifIndex is the first varbind, the following 612 would also work, but might be less meaningful to a human reader 613 of the MIB table: 614 alarmModelVarbindSubtree = 0.0 615 alarmModelResourcePrefix = 0.0 617 C) Consider an alarm modelled using the bgpBackwardTransition 618 [RFC1657] Notification. 620 bgpBackwardTransition NOTIFICATION-TYPE 621 OBJECTS { bgpPeerLastError, 622 bgpPeerState } 623 STATUS current 624 DESCRIPTION 625 "The BGPBackwardTransition Event is generated 626 when the BGP FSM moves from a higher numbered 627 state to a lower numbered state." 628 ::= { bgpTraps 2 } 630 To set the resource Id to be the bgpPeerRemoteAddr, the index to 631 the bgpTable, where bgpPeerState resides, configure as follows: 632 alarmModelVarbindSubtree = bgpPeerState 633 (1.3.6.1.2.1.15.3.1.2) 634 alarmModelResourcePrefix = bgpPeerRemoteAddr 635 (1.3.6.1.2.1.15.3.1.7) 637 4.1.5 Configurable Alarm Models 639 The alarm model table SHOULD be initially populated by the system. 640 The objects in alarmModelTable and ituAlarmTable have a MAX-ACCESS 641 of read-create, which allows managers to modify the alarm models to 642 suit their requirements. 644 4.1.6 Active Alarm Management 646 Lists of alarms currently active on an SNMP entity are stored in the 647 alarmActiveTable and, optionally, a model specific alarmTable, e.g. 648 the ituAlarmActiveTable. 650 4.1.7 Distributed Alarm Management 652 Distributed alarm management can be achieved by support of the Alarm 653 MIB on both the alarm detection point and on the mid-level manager. 654 This is facilitated by the ability to be able to store different 655 named alarm lists. A mid-level manager could create an alarmListName 656 for each of the devices it manages and therefore store separate 657 lists for each device. In addition, the context and IP addresses of 658 the alarm detection point are stored in the alarmActiveTable. 660 4.2 Definitions 662 ALARM-MIB DEFINITIONS ::= BEGIN 664 IMPORTS 665 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 666 Integer32, Unsigned32, Gauge32, 667 TimeTicks, Counter32, Counter64, 668 IpAddress, Opaque, mib-2 FROM SNMPv2-SMI 669 DateAndTime, 670 RowStatus, RowPointer, 671 TEXTUAL-CONVENTION FROM SNMPv2-TC 672 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 673 InetAddressType, InetAddress FROM INET-ADDRESS-MIB 674 MODULE-COMPLIANCE, OBJECT-GROUP, 675 NOTIFICATION-GROUP FROM SNMPv2-CONF 676 ZeroBasedCounter32 FROM RMON2-MIB; 678 alarmMIB MODULE-IDENTITY 679 LAST-UPDATED "200311170000Z" 680 ORGANIZATION "IETF Distributed Management Working Group" 681 CONTACT-INFO 682 "WG EMail: disman@ietf.org 683 Subscribe: disman-request@ietf.org 684 http://www.ietf.org/html.charters/disman-charter.html 686 Chair: Randy Presuhn 687 randy_presuhn@mindspring.com 689 Editors: Sharon Chisholm 690 Nortel Networks 691 PO Box 3511 Station C 692 Ottawa, Ont. K1Y 4H7 693 Canada 694 schishol@nortelnetworks.com 696 Dan Romascanu 697 Avaya 698 Atidim Technology Park, Bldg. #3 699 Tel Aviv, 61131 700 Israel 701 Tel: +972-3-645-8414 702 Email: dromasca@avaya.com" 703 DESCRIPTION 704 "The MIB module describes a generic solution 705 to model alarms and to store the current list 706 of active alarms. 708 Copyright (C) The Internet Society (2003). The 709 initial version of this MIB module was published 710 in RFC YYYY. For full legal notices see the RFC 711 itself. Supplementary information may be available on: 712 http://www.ietf.org/copyrights/ianamib.html" 713 -- RFC Ed.: replace yyyy with actual RFC number & remove 714 -- this note 715 REVISION "200311170000Z" 716 DESCRIPTION 717 "Initial version, published as RFC yyyy." 718 -- RFC-Editor assigns yyyy 719 ::= { mib-2 XX } -- to be assigned by IANA 721 alarmObjects OBJECT IDENTIFIER ::= { alarmMIB 1 } 723 alarmNotifications OBJECT IDENTIFIER ::= { alarmMIB 0 } 725 alarmModel OBJECT IDENTIFIER ::= { alarmObjects 1 } 727 alarmActive OBJECT IDENTIFIER ::= { alarmObjects 2 } 729 alarmClear OBJECT IDENTIFIER ::= { alarmObjects 3 } 731 -- Textual Conventions 733 -- ResourceId is intended to be a general textual convention 734 -- that can be used outside of the set of MIBs related to 735 -- Alarm Management. 737 ResourceId ::= TEXTUAL-CONVENTION 738 STATUS current 739 DESCRIPTION 740 "A unique identifier for this resource. 742 The type of the resource can be determined by looking 743 at the OID that describes the resource. 745 Resources must be identified in a consistent manner. 746 For example, if this resource is an interface, this 747 object MUST point to an ifIndex and if this resource 748 is a physical entity, then this MUST point to an 749 entPhysicalDescr, given that entPhysicalIndex is not 750 accessible. In general, the value is the 751 name of the instance of the first accessible columnar 752 object in the conceptual row of a table that is 753 meaningful for this resource type, which SHOULD 754 be defined in an IETF standard MIB." 755 SYNTAX OBJECT IDENTIFIER 757 -- LocalSnmpEngineOrZeroLenStr is intended to be a general 758 -- textual convention that can be used outside of the set of 759 -- MIBs related to Alarm Management. 761 LocalSnmpEngineOrZeroLenStr ::= TEXTUAL-CONVENTION 762 STATUS current 763 DESCRIPTION 764 "An SNMP Engine ID or a zero-length string. The 765 instantiation of this textual convention will provide 766 guidance on when this will be an SNMP Engine ID and 767 when it will be a zero lengths string" 768 SYNTAX OCTET STRING (SIZE(0 | 5..32)) 770 -- Alarm Model 772 alarmModelLastChanged OBJECT-TYPE 773 SYNTAX TimeTicks 774 MAX-ACCESS read-only 775 STATUS current 776 DESCRIPTION 777 "The value of sysUpTime at the time of the last 778 creation, deletion or modification of an entry in 779 the alarmModelTable. 781 If the number and content of entries has been unchanged 782 since the last re-initialization of the local network 783 management subsystem, then the value of this object 784 MUST be zero." 785 ::= { alarmModel 1 } 787 alarmModelTable OBJECT-TYPE 788 SYNTAX SEQUENCE OF AlarmModelEntry 789 MAX-ACCESS not-accessible 790 STATUS current 791 DESCRIPTION 792 "A table of information about possible alarms on the system, 793 and how they have been modelled." 794 ::= { alarmModel 2 } 796 alarmModelEntry OBJECT-TYPE 797 SYNTAX AlarmModelEntry 798 MAX-ACCESS not-accessible 799 STATUS current 800 DESCRIPTION 801 "Entries appear in this table for each possible alarm state. 802 This table MUST be persistent across system reboots." 803 INDEX { alarmListName, alarmModelIndex, alarmModelState } 804 ::= { alarmModelTable 1 } 806 AlarmModelEntry ::= SEQUENCE { 807 alarmModelIndex Unsigned32, 808 alarmModelState Unsigned32, 809 alarmModelNotificationId OBJECT IDENTIFIER, 810 alarmModelVarbindIndex Unsigned32, 811 alarmModelVarbindValue Integer32, 812 alarmModelDescription SnmpAdminString, 813 alarmModelSpecificPointer RowPointer, 814 alarmModelVarbindSubtree OBJECT IDENTIFIER, 815 alarmModelResourcePrefix OBJECT IDENTIFIER, 816 alarmModelRowStatus RowStatus 817 } 819 alarmModelIndex OBJECT-TYPE 820 SYNTAX Unsigned32 (1..4294967295) 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "An integer that acts as an alarm Id 825 to uniquely identify each alarm 826 within the named alarm list. " 827 ::= { alarmModelEntry 1 } 829 alarmModelState OBJECT-TYPE 830 SYNTAX Unsigned32 (1..4294967295) 831 MAX-ACCESS not-accessible 832 STATUS current 833 DESCRIPTION 834 "A value of 1 MUST indicate a clear alarm state. 835 The value of this object MUST be less than the 836 alarmModelState of more severe alarm states for 837 this alarm. The value of this object MUST be more 838 than the alarmModelState of less severe alarm states 839 for this alarm." 840 ::= { alarmModelEntry 2 } 842 alarmModelNotificationId OBJECT-TYPE 843 SYNTAX OBJECT IDENTIFIER 844 MAX-ACCESS read-create 845 STATUS current 846 DESCRIPTION 847 "The NOTIFICATION-TYPE object identifier of this alarm 848 state transition. If there is no notification associated 849 with this alarm state, the value of this object MUST be 850 '0.0'" 851 DEFVAL { { 0 0 } } 852 ::= { alarmModelEntry 3 } 854 alarmModelVarbindIndex OBJECT-TYPE 855 SYNTAX Unsigned32 856 MAX-ACCESS read-create 857 STATUS current 858 DESCRIPTION 859 "The index into the varbind listing of the notification 860 indicated by alarmModelNotificationId which helps 861 signal that the given alarm has changed state. 862 If there is no applicable varbind, the value of this 863 object MUST be zero. 865 Note that the value of alarmModelVarbindIndex acknowledges 866 the existence of the first two obligatory varbinds in 867 the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0 868 and snmpTrapOID.0). That is, a value of 2 refers to 869 the snmpTrapOID.0. 871 If the incoming notification is instead an SNMPv1 Trap-PDU, 872 then an appropriate value for sysUpTime.0 or snmpTrapOID.0 873 shall be determined by using the rules in section 3.1 of 874 [RFC3584]" 875 DEFVAL { 0 } 876 ::= { alarmModelEntry 4 } 878 alarmModelVarbindValue OBJECT-TYPE 879 SYNTAX Integer32 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "The value that the varbind indicated by 884 alarmModelVarbindIndex takes to indicate 885 that the alarm has entered this state. 887 If alarmModelVarbindIndex has a value of 0, so 888 MUST alarmModelVarbindIndex. 889 " 890 DEFVAL { 0 } 891 ::= { alarmModelEntry 5 } 893 alarmModelDescription OBJECT-TYPE 894 SYNTAX SnmpAdminString 895 MAX-ACCESS read-create 896 STATUS current 897 DESCRIPTION 898 "A brief description of this alarm and state suitable to 899 display to operators." 900 DEFVAL { "" } 901 ::= { alarmModelEntry 6 } 903 alarmModelSpecificPointer OBJECT-TYPE 904 SYNTAX RowPointer 905 MAX-ACCESS read-create 906 STATUS current 907 DESCRIPTION 908 "If no additional, model-specific Alarm MIB is supported by the 909 system the value of this object is `0.0'and attempts 910 to set it to any other value MUST be rejected appropriately. 912 When a model-specific Alarm MIB is supported, this object MUST 913 refer to the first accessible object in a corresponding 914 row of the model definition in one of these model-specific MIBs 915 and attempts to set this object to { 0 0 } or any other 916 value MUST be rejected appropriately." 917 DEFVAL { { 0 0 } } 918 ::= { alarmModelEntry 7 } 920 alarmModelVarbindSubtree OBJECT-TYPE 921 SYNTAX OBJECT IDENTIFIER 922 MAX-ACCESS read-create 923 STATUS current 924 DESCRIPTION 925 "The name portion of each VarBind in the notification, 926 in order, is compared to the value of this object. 927 If the name is equal to or a subtree of the value 928 of this object, for purposes of computing the value 929 of AlarmActiveResourceID the 'prefix' will be the 930 matching portion, and the 'indexes' will be any 931 remainder. The examination of varbinds ends with 932 the first match. If the value of this object is 0.0, 933 then the first varbind, or in the case of v2, the 934 first varbind after the timestamp and the trap 935 OID, will always be matched. 936 " 937 DEFVAL { { 0 0 } } 938 ::= { alarmModelEntry 8 } 940 alarmModelResourcePrefix OBJECT-TYPE 941 SYNTAX OBJECT IDENTIFIER 942 MAX-ACCESS read-create 943 STATUS current 944 DESCRIPTION 945 "The value of AlarmActiveResourceID is computed 946 by appending any indexes extracted in accordance 947 with the description of alarmModelVarbindSubtree 948 onto the value of this object. If this object's 949 value is 0.0, then the 'prefix' extracted is used 950 instead. 951 " 952 DEFVAL { { 0 0 } } 953 ::= { alarmModelEntry 9 } 955 alarmModelRowStatus OBJECT-TYPE 956 SYNTAX RowStatus 957 MAX-ACCESS read-create 958 STATUS current 959 DESCRIPTION 960 "Control for creating and deleting entries. Entries may be 961 modified while active. Alarms whose alarmModelRowStatus is 962 not active will not appear in either the alarmActiveTable 963 or the alarmClearTable. Setting this object to notInService 964 cannot be used as an alarm suppression mechanism. Entries 965 that are notInService will disappear as described in RFC2579. 967 This row can not be modified while it is being 968 referenced by a value of alarmActiveModelPointer. In these 969 cases, an error of `inconsistentValue' will be returned to 970 the manager. 972 This entry may be deleted while it is being 973 referenced by a value of alarmActiveModelPointer. This results 974 in the deletion of this entry and entries in the active alarms 975 referencing this entry via an alarmActiveModelPointer. 977 As all read-create objects in this table have a DEFVAL clause, 978 there is no requirement that any object be explicitly set 979 before this row can become active. Note that a row consisting 980 only of default values is not very meaningful." 981 ::= { alarmModelEntry 10 } 983 -- Active Alarm Table -- 985 alarmActiveLastChanged OBJECT-TYPE 986 SYNTAX TimeTicks 987 MAX-ACCESS read-only 988 STATUS current 989 DESCRIPTION 990 "The value of sysUpTime at the time of the last 991 creation or deletion of an entry in the alarmActiveTable. 992 If the number of entries has been unchanged since the 993 last re-initialization of the local network management 994 subsystem, then this object contains a zero value." 995 ::= { alarmActive 1 } 997 alarmActiveOverflow OBJECT-TYPE 998 SYNTAX Counter32 999 UNITS "active alarms" 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION 1003 "The number of active alarms that have not been put into 1004 the alarmActiveTable since system restart as a result 1005 of extreme resource constraints." 1006 ::= { alarmActive 5 } 1008 alarmActiveTable OBJECT-TYPE 1009 SYNTAX SEQUENCE OF AlarmActiveEntry 1010 MAX-ACCESS not-accessible 1011 STATUS current 1012 DESCRIPTION 1013 "A table of Active Alarms entries." 1014 ::= { alarmActive 2 } 1016 alarmActiveEntry OBJECT-TYPE 1017 SYNTAX AlarmActiveEntry 1018 MAX-ACCESS not-accessible 1019 STATUS current 1020 DESCRIPTION 1021 "Entries appear in this table when alarms are raised. They 1022 are removed when the alarm is cleared. 1024 If under extreme resource constraint the system is unable to 1025 add any more entries into this table, then the 1026 alarmActiveOverflow statistic will be increased by one." 1027 INDEX { alarmListName, alarmActiveDateAndTime, 1028 alarmActiveIndex } 1029 ::= { alarmActiveTable 1 } 1031 AlarmActiveEntry ::= SEQUENCE { 1032 alarmListName SnmpAdminString, 1033 alarmActiveDateAndTime DateAndTime, 1034 alarmActiveIndex Unsigned32, 1035 alarmActiveEngineID LocalSnmpEngineOrZeroLenStr, 1036 alarmActiveEngineAddressType InetAddressType, 1037 alarmActiveEngineAddress InetAddress, 1038 alarmActiveContextName SnmpAdminString, 1039 alarmActiveVariables Unsigned32, 1040 alarmActiveNotificationID OBJECT IDENTIFIER, 1041 alarmActiveResourceId ResourceId, 1042 alarmActiveDescription SnmpAdminString, 1043 alarmActiveLogPointer RowPointer, 1044 alarmActiveModelPointer RowPointer, 1045 alarmActiveSpecificPointer RowPointer } 1047 alarmListName OBJECT-TYPE 1048 SYNTAX SnmpAdminString (SIZE(0..32)) 1049 MAX-ACCESS not-accessible 1050 STATUS current 1051 DESCRIPTION 1052 "The name of the list of alarms. This SHOULD be the same as 1053 nlmLogName if the Notification Log MIB [RFC3014] is supported. 1054 This SHOULD be the same as, or contain as a prefix, the 1055 applicable snmpNotifyFilterProfileName if the 1056 SNMP-NOTIFICATION-MIB DEFINITIONS [RFC3413] is supported. 1058 An implementation may allow multiple named alarm lists, up to 1059 some implementation-specific limit (which may be none). A 1060 zero-length list name is reserved for creation and deletion 1061 by the managed system, and MUST be used as the default log 1062 name by systems that do not support named alarm lists." 1063 ::= { alarmActiveEntry 1 } 1065 alarmActiveDateAndTime OBJECT-TYPE 1066 SYNTAX DateAndTime 1067 MAX-ACCESS not-accessible 1068 STATUS current 1069 DESCRIPTION 1070 "The local date and time when the error occurred. 1072 This object facilitates retrieving all instances of 1073 alarms that have been raised or have changed state 1074 since a given point in time. 1076 Implementations MUST include the offset from UTC, 1077 if available. Implementation in environments in which 1078 the UTC offset is not available is NOT RECOMMENDED." 1079 ::= { alarmActiveEntry 2 } 1081 alarmActiveIndex OBJECT-TYPE 1082 SYNTAX Unsigned32 (1..4294967295) 1083 MAX-ACCESS not-accessible 1084 STATUS current 1085 DESCRIPTION 1086 "A strictly monotonically increasing integer which 1087 acts as the index of entries within the named alarm 1088 list. It wraps back to 1 after it reaches its 1089 maximum value." 1090 ::= { alarmActiveEntry 3 } 1092 alarmActiveEngineID OBJECT-TYPE 1093 SYNTAX LocalSnmpEngineOrZeroLenStr 1094 MAX-ACCESS read-only 1095 STATUS current 1096 DESCRIPTION 1097 "The identification of the SNMP engine at which the alarm 1098 originated. If the alarm is from an SNMPv1 system this 1099 object is a zero length string." 1100 ::= { alarmActiveEntry 4 } 1102 alarmActiveEngineAddressType OBJECT-TYPE 1103 SYNTAX InetAddressType 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "This object indicates what type of address is stored in 1108 the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc." 1109 ::= { alarmActiveEntry 5 } 1111 alarmActiveEngineAddress OBJECT-TYPE 1112 SYNTAX InetAddress 1113 MAX-ACCESS read-only 1114 STATUS current 1115 DESCRIPTION 1116 "The address of the SNMP engine on which the alarm is 1117 occurring. 1119 This object MUST always be instantiated, even if the list 1120 can contain alarms from only one engine." 1121 ::= { alarmActiveEntry 6 } 1123 alarmActiveContextName OBJECT-TYPE 1124 SYNTAX SnmpAdminString (SIZE(0..32)) 1125 MAX-ACCESS read-only 1126 STATUS current 1127 DESCRIPTION 1128 "The name of the SNMP MIB context from which the alarm came. 1129 For SNMPv1 alarms this is the community string from the Trap. 1130 Note that care MUST be taken when selecting community 1131 strings to ensure that these can be represented as a 1132 well-formed SnmpAdminString. Community or Context names 1133 that are not well-formed SnmpAdminStrings will be mapped 1134 to zero length strings. 1136 If the alarm's source SNMP engine is known not to support 1137 multiple contexts, this object is a zero length string." 1138 ::= { alarmActiveEntry 7 } 1140 alarmActiveVariables OBJECT-TYPE 1141 SYNTAX Unsigned32 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "The number of variables in alarmActiveVariableTable for this 1146 alarm." 1147 ::= { alarmActiveEntry 8 } 1149 alarmActiveNotificationID OBJECT-TYPE 1150 SYNTAX OBJECT IDENTIFIER 1151 MAX-ACCESS read-only 1152 STATUS current 1153 DESCRIPTION 1154 "The NOTIFICATION-TYPE object identifier of the alarm 1155 state transition that is occurring." 1156 ::= { alarmActiveEntry 9 } 1158 alarmActiveResourceId OBJECT-TYPE 1159 SYNTAX ResourceId 1160 MAX-ACCESS read-only 1161 STATUS current 1162 DESCRIPTION 1163 "This object identifies the resource under alarm. 1165 If there is no corresponding resource, then 1166 the value of this object MUST be 0.0." 1167 ::= { alarmActiveEntry 10 } 1169 alarmActiveDescription OBJECT-TYPE 1170 SYNTAX SnmpAdminString 1171 MAX-ACCESS read-only 1172 STATUS current 1173 DESCRIPTION 1174 "This object provides a textual description of the 1175 active alarm. This text is generated dynamically by the 1176 notification generator to provide useful information 1177 to the human operator. This information SHOULD 1178 provide information allowing the operator to locate 1179 the resource for which this alarm is being generated. 1180 This information is not intended for consumption by 1181 automated tools." 1182 ::= { alarmActiveEntry 11 } 1184 alarmActiveLogPointer OBJECT-TYPE 1185 SYNTAX RowPointer 1186 MAX-ACCESS read-only 1187 STATUS current 1188 DESCRIPTION 1189 "A pointer to the corresponding row in a 1190 notification logging MIB where the state change 1191 notification for this active alarm is logged. 1192 If no log entry applies to this active alarm, 1193 then this object MUST have the value of 0.0" 1194 ::= { alarmActiveEntry 12 } 1196 alarmActiveModelPointer OBJECT-TYPE 1197 SYNTAX RowPointer 1198 MAX-ACCESS read-only 1199 STATUS current 1200 DESCRIPTION 1201 "A pointer to the corresponding row in the 1202 alarmModelTable for this active alarm. This 1203 points not only to the alarm model being 1204 instantiated, but also to the specific alarm 1205 state that is active." 1206 ::= { alarmActiveEntry 13 } 1208 alarmActiveSpecificPointer OBJECT-TYPE 1209 SYNTAX RowPointer 1210 MAX-ACCESS read-only 1211 STATUS current 1212 DESCRIPTION 1213 "If no additional, model-specific, Alarm MIB is supported by the 1214 system this object is `0.0'. When a model-specific Alarm MIB is 1215 supported, this object is the instance pointer to the specific 1216 model-specific active alarm list." 1217 ::= { alarmActiveEntry 14 } 1219 -- Active Alarm Variable Table -- 1221 alarmActiveVariableTable OBJECT-TYPE 1222 SYNTAX SEQUENCE OF AlarmActiveVariableEntry 1223 MAX-ACCESS not-accessible 1224 STATUS current 1225 DESCRIPTION 1226 "A table of variables to go with active alarm entries." 1227 ::= { alarmActive 3 } 1229 alarmActiveVariableEntry OBJECT-TYPE 1230 SYNTAX AlarmActiveVariableEntry 1231 MAX-ACCESS not-accessible 1232 STATUS current 1233 DESCRIPTION 1234 "Entries appear in this table when there are variables in 1235 the varbind list of a corresponding alarm in 1236 alarmActiveTable. 1238 Entries appear in this table as though 1239 the trap/notification had been transported using a 1240 SNMPv2-Trap-PDU, as defined in [RFC3416] - i.e, the 1241 alarmActiveVariableIndex 1 will always be sysUpTime 1242 and alarmActiveVariableIndex 2 will always be 1243 snmpTrapOID. 1245 If the incoming notification is instead an SNMPv1 Trap-PDU and 1246 the value of alarmModelVarbindIndex is 1 or 2, an appropriate 1247 value for sysUpTime.0 or snmpTrapOID.0 shall be determined 1248 by using the rules in section 3.1 of [RFC3584]." 1249 INDEX { alarmListName, alarmActiveIndex, 1250 alarmActiveVariableIndex } 1251 ::= { alarmActiveVariableTable 1 } 1253 AlarmActiveVariableEntry ::= SEQUENCE { 1254 alarmActiveVariableIndex Unsigned32, 1255 alarmActiveVariableID OBJECT IDENTIFIER, 1256 alarmActiveVariableValueType INTEGER, 1257 alarmActiveVariableCounter32Val Counter32, 1258 alarmActiveVariableUnsigned32Val Unsigned32, 1259 alarmActiveVariableTimeTicksVal TimeTicks, 1260 alarmActiveVariableInteger32Val Integer32, 1261 alarmActiveVariableOctetStringVal OCTET STRING, 1262 alarmActiveVariableIpAddressVal IpAddress, 1263 alarmActiveVariableOidVal OBJECT IDENTIFIER, 1264 alarmActiveVariableCounter64Val Counter64, 1265 alarmActiveVariableOpaqueVal Opaque } 1267 alarmActiveVariableIndex OBJECT-TYPE 1268 SYNTAX Unsigned32 (1..4294967295) 1269 MAX-ACCESS not-accessible 1270 STATUS current 1271 DESCRIPTION 1272 "A strictly monotonically increasing integer, starting at 1273 1 for a given alarmActiveIndex, for indexing variables 1274 within the active alarm variable list. " 1275 ::= { alarmActiveVariableEntry 1 } 1277 alarmActiveVariableID OBJECT-TYPE 1278 SYNTAX OBJECT IDENTIFIER 1279 MAX-ACCESS read-only 1280 STATUS current 1281 DESCRIPTION 1282 "The alarm variable's object identifier." 1283 ::= { alarmActiveVariableEntry 2 } 1285 alarmActiveVariableValueType OBJECT-TYPE 1286 SYNTAX INTEGER { 1287 counter32(1), 1288 unsigned32(2), 1289 timeTicks(3), 1290 integer32(4), 1291 ipAddress(5), 1292 octetString(6), 1293 objectId(7), 1294 counter64(8), 1295 opaque(9) 1296 } 1297 MAX-ACCESS read-only 1298 STATUS current 1299 DESCRIPTION 1300 "The type of the value. One and only one of the value 1301 objects that follow is used for a given row in this table, 1302 based on this type." 1303 ::= { alarmActiveVariableEntry 3 } 1305 alarmActiveVariableCounter32Val OBJECT-TYPE 1306 SYNTAX Counter32 1307 MAX-ACCESS read-only 1308 STATUS current 1309 DESCRIPTION 1310 "The value when alarmActiveVariableType is 'counter32'." 1311 ::= { alarmActiveVariableEntry 4 } 1313 alarmActiveVariableUnsigned32Val OBJECT-TYPE 1314 SYNTAX Unsigned32 1315 MAX-ACCESS read-only 1316 STATUS current 1317 DESCRIPTION 1318 "The value when alarmActiveVariableType is 'unsigned32'." 1319 ::= { alarmActiveVariableEntry 5 } 1321 alarmActiveVariableTimeTicksVal OBJECT-TYPE 1322 SYNTAX TimeTicks 1323 MAX-ACCESS read-only 1324 STATUS current 1325 DESCRIPTION 1326 "The value when alarmActiveVariableType is 'timeTicks'." 1327 ::= { alarmActiveVariableEntry 6 } 1329 alarmActiveVariableInteger32Val OBJECT-TYPE 1330 SYNTAX Integer32 1331 MAX-ACCESS read-only 1332 STATUS current 1333 DESCRIPTION 1334 "The value when alarmActiveVariableType is 'integer32'." 1335 ::= { alarmActiveVariableEntry 7 } 1337 alarmActiveVariableOctetStringVal OBJECT-TYPE 1338 SYNTAX OCTET STRING (SIZE(0..65535)) 1339 MAX-ACCESS read-only 1340 STATUS current 1341 DESCRIPTION 1342 "The value when alarmActiveVariableType is 'octetString'." 1343 ::= { alarmActiveVariableEntry 8 } 1345 alarmActiveVariableIpAddressVal OBJECT-TYPE 1346 SYNTAX IpAddress 1347 MAX-ACCESS read-only 1348 STATUS current 1349 DESCRIPTION 1350 "The value when alarmActiveVariableType is 'ipAddress'." 1351 ::= { alarmActiveVariableEntry 9 } 1353 alarmActiveVariableOidVal OBJECT-TYPE 1354 SYNTAX OBJECT IDENTIFIER 1355 MAX-ACCESS read-only 1356 STATUS current 1357 DESCRIPTION 1358 "The value when alarmActiveVariableType is 'objectId'." 1359 ::= { alarmActiveVariableEntry 10 } 1361 alarmActiveVariableCounter64Val OBJECT-TYPE 1362 SYNTAX Counter64 1363 MAX-ACCESS read-only 1364 STATUS current 1365 DESCRIPTION 1366 "The value when alarmActiveVariableType is 'counter64'." 1367 ::= { alarmActiveVariableEntry 11 } 1369 alarmActiveVariableOpaqueVal OBJECT-TYPE 1370 SYNTAX Opaque (SIZE(0..65535)) 1371 MAX-ACCESS read-only 1372 STATUS current 1373 DESCRIPTION 1374 "The value when alarmActiveVariableType is 'opaque'. 1376 Note that although RFC2578 [RFC2578] forbids the use 1377 of Opaque in 'standard' MIB modules, this particular 1378 usage is driven by the need to be able to accurately 1379 represent any well-formed notification, and justified 1380 by the need for backward compatibility." 1381 ::= { alarmActiveVariableEntry 12 } 1383 -- Statistics -- 1385 alarmActiveStatsTable OBJECT-TYPE 1386 SYNTAX SEQUENCE OF AlarmActiveStatsEntry 1387 MAX-ACCESS not-accessible 1388 STATUS current 1389 DESCRIPTION 1390 "This table represents the alarm statistics 1391 information." 1392 ::= { alarmActive 4 } 1394 alarmActiveStatsEntry OBJECT-TYPE 1395 SYNTAX AlarmActiveStatsEntry 1396 MAX-ACCESS not-accessible 1397 STATUS current 1398 DESCRIPTION 1399 "Statistics on the current active alarms." 1400 INDEX { alarmListName } 1402 ::= { alarmActiveStatsTable 1 } 1404 AlarmActiveStatsEntry ::= 1405 SEQUENCE { 1406 alarmActiveStatsActiveCurrent Gauge32, 1407 alarmActiveStatsActives ZeroBasedCounter32, 1408 alarmActiveStatsLastRaise TimeTicks, 1409 alarmActiveStatsLastClear TimeTicks 1410 } 1412 alarmActiveStatsActiveCurrent OBJECT-TYPE 1413 SYNTAX Gauge32 1414 MAX-ACCESS read-only 1415 STATUS current 1416 DESCRIPTION 1417 "The total number of currently active alarms on the system." 1419 ::= { alarmActiveStatsEntry 1 } 1421 alarmActiveStatsActives OBJECT-TYPE 1422 SYNTAX ZeroBasedCounter32 1423 MAX-ACCESS read-only 1424 STATUS current 1425 DESCRIPTION 1426 "The total number of active alarms since system restarted." 1428 ::= { alarmActiveStatsEntry 2 } 1430 alarmActiveStatsLastRaise OBJECT-TYPE 1431 SYNTAX TimeTicks 1432 MAX-ACCESS read-only 1433 STATUS current 1434 DESCRIPTION 1435 "The value of sysUpTime at the time of the last 1436 alarm raise for this alarm list. 1437 If no alarm raises have occurred since the 1438 last re-initialization of the local network management 1439 subsystem, then this object contains a zero value." 1440 ::= { alarmActiveStatsEntry 3 } 1442 alarmActiveStatsLastClear OBJECT-TYPE 1443 SYNTAX TimeTicks 1444 MAX-ACCESS read-only 1445 STATUS current 1446 DESCRIPTION 1447 "The value of sysUpTime at the time of the last 1448 alarm clear for this alarm list. 1449 If no alarm clears have occurred since the 1450 last re-initialization of the local network management 1451 subsystem, then this object contains a zero value." 1452 ::= { alarmActiveStatsEntry 4 } 1454 -- Alarm Clear 1456 alarmClearMaximum OBJECT-TYPE 1457 SYNTAX Unsigned32 1458 MAX-ACCESS read-write 1459 STATUS current 1460 DESCRIPTION 1461 "This object specifies the maximum number of cleared 1462 alarms to store in the alarmClearTable. When this 1463 number is reached, the cleared alarms with the 1464 earliest clear time will be removed from the table." 1465 ::= { alarmClear 1 } 1467 alarmClearTable OBJECT-TYPE 1468 SYNTAX SEQUENCE OF AlarmClearEntry 1469 MAX-ACCESS not-accessible 1470 STATUS current 1471 DESCRIPTION 1472 "This table contains information on 1473 cleared alarms." 1474 ::= { alarmClear 2 } 1476 alarmClearEntry OBJECT-TYPE 1477 SYNTAX AlarmClearEntry 1478 MAX-ACCESS not-accessible 1479 STATUS current 1480 DESCRIPTION 1481 "Information on a cleared alarm." 1482 INDEX { alarmListName, alarmClearDateAndTime, 1483 alarmClearIndex } 1485 ::= { alarmClearTable 1 } 1487 AlarmClearEntry ::= 1488 SEQUENCE { 1489 alarmClearIndex Unsigned32, 1490 alarmClearDateAndTime DateAndTime, 1491 alarmClearEngineID LocalSnmpEngineOrZeroLenStr, 1492 alarmClearEngineAddressType InetAddressType, 1493 alarmClearEngineAddress InetAddress, 1494 alarmClearContextName SnmpAdminString, 1495 alarmClearNotificationID OBJECT IDENTIFIER, 1496 alarmClearResourceId ResourceId, 1497 alarmClearLogIndex Unsigned32, 1498 alarmClearModelPointer RowPointer 1499 } 1501 alarmClearIndex OBJECT-TYPE 1502 SYNTAX Unsigned32 (1..4294967295) 1503 MAX-ACCESS not-accessible 1504 STATUS current 1505 DESCRIPTION 1506 "An integer which acts as the index of entries within 1507 the named alarm list. It wraps back to 1 after it 1508 reaches its maximum value. 1510 This object has the same value as the alarmActiveIndex that 1511 this alarm instance had when it was active." 1512 ::= { alarmClearEntry 1 } 1514 alarmClearDateAndTime OBJECT-TYPE 1515 SYNTAX DateAndTime 1516 MAX-ACCESS not-accessible 1517 STATUS current 1518 DESCRIPTION 1519 "The local date and time when the alarm cleared. 1521 This object facilitates retrieving all instances of 1522 alarms that have been cleared since a given point in time. 1524 Implementations MUST include the offset from UTC, 1525 if available. Implementation in environments in which 1526 the UTC offset is not available is NOT RECOMMENDED." 1527 ::= { alarmClearEntry 2 } 1529 alarmClearEngineID OBJECT-TYPE 1530 SYNTAX LocalSnmpEngineOrZeroLenStr 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "The identification of the SNMP engine at which the alarm 1535 originated. If the alarm is from an SNMPv1 system this 1536 object is a zero length string." 1537 ::= { alarmClearEntry 3 } 1539 alarmClearEngineAddressType OBJECT-TYPE 1540 SYNTAX InetAddressType 1541 MAX-ACCESS read-only 1542 STATUS current 1543 DESCRIPTION 1544 "This object indicates what type of address is stored in 1545 the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc." 1546 ::= { alarmClearEntry 4 } 1548 alarmClearEngineAddress OBJECT-TYPE 1549 SYNTAX InetAddress 1550 MAX-ACCESS read-only 1551 STATUS current 1552 DESCRIPTION 1553 "The Address of the SNMP engine on which the alarm was 1554 occurring. This is used to identify the source of an SNMPv1 1555 trap, since an alarmActiveEngineId cannot be extracted from the 1556 SNMPv1 trap PDU. 1558 This object MUST always be instantiated, even if the list 1559 can contain alarms from only one engine." 1560 ::= { alarmClearEntry 5 } 1562 alarmClearContextName OBJECT-TYPE 1563 SYNTAX SnmpAdminString (SIZE(0..32)) 1564 MAX-ACCESS read-only 1565 STATUS current 1566 DESCRIPTION 1567 "The name of the SNMP MIB context from which the alarm came. 1568 For SNMPv1 traps this is the community string from the Trap. 1569 Note that care needs to be taken when selecting community 1570 strings to ensure that these can be represented as a 1571 well-formed SnmpAdminString. Community or Context names 1572 that are not well-formed SnmpAdminStrings will be mapped 1573 to zero length strings. 1575 If the alarm's source SNMP engine is known not to support 1576 multiple contexts, this object is a zero length string." 1577 ::= { alarmClearEntry 6 } 1579 alarmClearNotificationID OBJECT-TYPE 1580 SYNTAX OBJECT IDENTIFIER 1581 MAX-ACCESS read-only 1582 STATUS current 1583 DESCRIPTION 1584 "The NOTIFICATION-TYPE object identifier of the alarm 1585 clear." 1586 ::= { alarmClearEntry 7 } 1588 alarmClearResourceId OBJECT-TYPE 1589 SYNTAX ResourceId 1590 MAX-ACCESS read-only 1591 STATUS current 1592 DESCRIPTION 1593 "This object identifies the resource that was under alarm. 1595 If there is no corresponding resource, then 1596 the value of this object MUST be 0.0." 1597 ::= { alarmClearEntry 8 } 1599 alarmClearLogIndex OBJECT-TYPE 1600 SYNTAX Unsigned32 (0..4294967295) 1601 MAX-ACCESS read-only 1602 STATUS current 1603 DESCRIPTION 1604 "This number MUST be the same as the log index of the 1605 applicable row in the notification log MIB, if it exists. 1606 If no log index applies to the trap, then this object 1607 MUST have the value of 0." 1608 ::= { alarmClearEntry 9 } 1610 alarmClearModelPointer OBJECT-TYPE 1611 SYNTAX RowPointer 1612 MAX-ACCESS read-only 1613 STATUS current 1614 DESCRIPTION 1615 "A pointer to the corresponding row in the 1616 alarmModelTable for this cleared alarm." 1617 ::= { alarmClearEntry 10 } 1619 -- Notifications 1621 alarmActiveState NOTIFICATION-TYPE 1622 OBJECTS { alarmActiveModelPointer, 1623 alarmActiveResourceId } 1624 STATUS current 1625 DESCRIPTION 1626 "An instance of the alarm indicated by 1627 alarmActiveModelPointer has been raised 1628 against the entity indicated by 1629 alarmActiveResourceId. 1631 The agent must throttle the generation of 1632 consecutive alarmActiveState traps so that there is at 1633 least a two-second gap between traps of this 1634 type against the same alarmActiveModelPointer and 1635 alarmActiveResourceId. When traps are throttled, 1636 they are dropped, not queued for sending at a future time. 1638 A management application should periodically check 1639 the value of alarmActiveLastChanged to detect any 1640 missed alarmActiveState notification-events, e.g., 1641 due to throttling or transmission loss." 1642 ::= { alarmNotifications 2 } 1644 alarmClearState NOTIFICATION-TYPE 1645 OBJECTS { alarmActiveModelPointer, 1646 alarmActiveResourceId } 1647 STATUS current 1648 DESCRIPTION 1649 "An instance of the alarm indicated by 1650 alarmActiveModelPointer has been cleared against 1651 the entity indicated by alarmActiveResourceId. 1653 The agent must throttle the generation of 1654 consecutive alarmActiveClear traps so that there is at 1655 least a two-second gap between traps of this 1656 type against the same alarmActiveModelPointer and 1657 alarmActiveResourceId. When traps are throttled, 1658 they are dropped, not queued for sending at a future time. 1660 A management application should periodically check 1661 the value of alarmActiveLastChanged to detect any 1662 missed alarmClearState notification-events, e.g., 1663 due to throttling or transmission loss." 1664 ::= { alarmNotifications 3 } 1666 -- Conformance 1668 alarmConformance OBJECT IDENTIFIER ::= { alarmMIB 2 } 1670 alarmCompliances OBJECT IDENTIFIER ::= { alarmConformance 1 } 1672 alarmCompliance MODULE-COMPLIANCE 1673 STATUS current 1674 DESCRIPTION 1675 "The compliance statement for systems supporting 1676 the Alarm MIB." 1677 MODULE -- this module 1678 MANDATORY-GROUPS { 1679 alarmActiveGroup, 1680 alarmModelGroup 1681 } 1682 GROUP alarmActiveStatsGroup 1683 DESCRIPTION 1684 "This group is optional." 1685 GROUP alarmClearGroup 1686 DESCRIPTION 1687 "This group is optional." 1688 GROUP alarmNotificationsGroup 1689 DESCRIPTION 1690 "This group is optional." 1691 ::= { alarmCompliances 1 } 1693 alarmGroups OBJECT IDENTIFIER ::= { alarmConformance 2 } 1695 alarmModelGroup OBJECT-GROUP 1696 OBJECTS { 1697 alarmModelLastChanged, 1698 alarmModelNotificationId, 1699 alarmModelVarbindIndex, 1700 alarmModelVarbindValue, 1701 alarmModelDescription, 1702 alarmModelSpecificPointer, 1703 alarmModelVarbindSubtree, 1704 alarmModelResourcePrefix, 1705 alarmModelRowStatus 1706 } 1707 STATUS current 1708 DESCRIPTION 1709 "Alarm model group." 1711 ::= { alarmGroups 1} 1713 alarmActiveGroup OBJECT-GROUP 1714 OBJECTS { 1715 alarmActiveLastChanged, 1716 alarmActiveOverflow, 1717 alarmActiveEngineID, 1718 alarmActiveEngineAddressType, 1719 alarmActiveEngineAddress, 1720 alarmActiveContextName, 1721 alarmActiveVariables, 1722 alarmActiveNotificationID, 1723 alarmActiveResourceId, 1724 alarmActiveDescription, 1725 alarmActiveLogPointer, 1726 alarmActiveModelPointer, 1727 alarmActiveSpecificPointer, 1728 alarmActiveVariableID, 1729 alarmActiveVariableValueType, 1730 alarmActiveVariableCounter32Val, 1731 alarmActiveVariableUnsigned32Val, 1732 alarmActiveVariableTimeTicksVal, 1733 alarmActiveVariableInteger32Val, 1734 alarmActiveVariableOctetStringVal, 1735 alarmActiveVariableIpAddressVal, 1736 alarmActiveVariableOidVal, 1737 alarmActiveVariableCounter64Val, 1738 alarmActiveVariableOpaqueVal 1739 } 1740 STATUS current 1741 DESCRIPTION 1742 "Active Alarm list group." 1743 ::= { alarmGroups 2} 1745 alarmActiveStatsGroup OBJECT-GROUP 1746 OBJECTS { 1747 alarmActiveStatsActives, 1748 alarmActiveStatsActiveCurrent, 1749 alarmActiveStatsLastRaise, 1750 alarmActiveStatsLastClear 1751 } 1752 STATUS current 1753 DESCRIPTION 1754 "Active alarm summary group." 1755 ::= { alarmGroups 3} 1757 alarmClearGroup OBJECT-GROUP 1758 OBJECTS { 1759 alarmClearMaximum, 1760 alarmClearEngineID, 1761 alarmClearEngineAddressType, 1762 alarmClearEngineAddress, 1763 alarmClearContextName, 1764 alarmClearNotificationID, 1765 alarmClearResourceId, 1766 alarmClearLogIndex, 1767 alarmClearModelPointer 1768 } 1769 STATUS current 1770 DESCRIPTION 1771 "Cleared alarm group." 1772 ::= { alarmGroups 4} 1774 alarmNotificationsGroup NOTIFICATION-GROUP 1775 NOTIFICATIONS { alarmActiveState, alarmClearState } 1776 STATUS current 1777 DESCRIPTION 1778 "The collection of notifications that can be used to 1779 model alarms for faults lacking pre-existing 1780 notification definitions." 1781 ::= { alarmGroups 6 } 1783 END 1785 5. ITU Alarm 1787 5.1 Overview 1789 This MIB module defines alarm information specific to the alarm 1790 model defined in ITU M.3100 [M.3100], X.733[X.733] and X.736[X.736]. 1791 This MIB module follows the modular architecture defined by the 1792 Alarm MIB, in which the generic Alarm MIB can be augmented by other 1793 alarm information defined according to more specific models that 1794 define additional behaviour and characteristics. 1796 The ituAlarmTable contains information from the ITU Alarm Model 1797 about possible alarms in the system. 1799 The ituAlarmActiveTable contains information from the ITU Alarm 1800 Model about alarms modeled using the ituAlarmTable that are 1801 currently occurring on the system. 1803 The ituAlarmActiveStatsTable provides statistics on current and 1804 total alarms. 1806 5.2 IANA Considerations 1808 Over time, there will be a need to add new IANAItuProbableCause 1809 enumerated values for new probable causes. The Internet Assigned 1810 Number Authority (IANA) is responsible for the assignment of all 1811 Internet numbers, including various SNMP-related numbers, and 1812 specifically, new IANAItuProbableCause and IANAItuEventType values. 1813 Values of IANAItuProbableCause less than 1024 are reserved for 1814 causes that correspond to ITU probable cause. IANAItuProbableCause 1815 of 0 is reserved for special purposes and therefore cannot be 1816 assigned. Values of IANAProbableCause greater than 1024 may be 1817 assigned on a first come first served basis for causes not covered 1818 by existing probable causes.. 1820 The following shall be used as the initial values, but the latest 1821 values for these textual conventions should be obtained from IANA: 1823 IANA-ITU-ALARM-TC DEFINITIONS ::= BEGIN 1825 IMPORTS 1826 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 1827 TEXTUAL-CONVENTION FROM SNMPv2-TC; 1829 ianaItuAlarmNumbers MODULE-IDENTITY 1830 LAST-UPDATED "200311170000Z" 1831 ORGANIZATION "IANA" 1832 CONTACT-INFO 1833 "Postal: Internet Assigned Numbers Authority 1834 Internet Corporation for Assigned Names 1835 and Numbers 1836 4676 Admiralty Way, Suite 330 1837 Marina del Rey, CA 90292-6601 1838 USA 1840 Tel: +1 310-823-9358 1841 E-Mail: iana@iana.org" 1842 DESCRIPTION 1843 "The MIB module defines the ITU Alarm 1844 textual convention for objects expected to require 1845 regular extension. 1847 Copyright (C) The Internet Society (2003). The 1848 initial version of this MIB module was published 1849 in RFC xxxx. For full legal notices see the RFC 1850 itself. Supplementary information may be available on: 1851 http://www.ietf.org/copyrights/ianamib.html" 1852 REVISION "200311170000Z" 1853 DESCRIPTION 1854 "Initial version, published as RFC yyyy." 1855 -- RFC-Editor assigns yyyy 1856 ::= { mib-2 XX } -- to be assigned by IANA 1858 IANAItuProbableCause ::= TEXTUAL-CONVENTION 1859 STATUS current 1860 DESCRIPTION 1861 "ITU probable cause values. Duplicate values defined in X.733 1862 are appended with X733 to ensure uniqueness. Probable cause 1863 value 0 is reserved for special purposes. 1865 The Internet Assigned Number Authority (IANA) is responsible 1866 for the assignment of all Internet numbers, including 1867 various SNMP-related numbers, and specifically, new 1868 IANAItuProbableCause values. Values of 1869 IANAItuProbableCause less than 1024 are reserved for causes 1870 that correspond to ITU probable cause. IANAItuProbableCause 1871 of 0 is reserved for special purposes and therefore cannot 1872 be assigned. See http://www.iana.org" 1873 REFERENCE 1874 "ITU Recommendation M.3100, 'Generic Network Information 1875 Model', 1995 1876 ITU Recommendation X.733, 'Information Technology - Open 1877 Systems Interconnection - System Management: Alarm 1878 Reporting Function', 1992 1879 ITU Recommendation X.736, 'Information Technology - Open 1880 Systems Interconnection - System Management: Security 1881 Alarm Reporting Function', 1992" 1882 SYNTAX INTEGER 1883 { 1884 -- The following probable causes were defined in M.3100 1885 aIS (1), 1886 callSetUpFailure (2), 1887 degradedSignal (3), 1888 farEndReceiverFailure (4), 1889 framingError (5), 1890 lossOfFrame (6), 1891 lossOfPointer (7), 1892 lossOfSignal (8), 1893 payloadTypeMismatch (9), 1894 transmissionError (10), 1895 remoteAlarmInterface (11), 1896 excessiveBER (12), 1897 pathTraceMismatch (13), 1898 unavailable (14), 1899 signalLabelMismatch (15), 1900 lossOfMultiFrame (16), 1901 receiveFailure (17), 1902 transmitFailure (18), 1903 modulationFailure (19), 1904 demodulationFailure (20), 1905 broadcastChannelFailure (21), 1906 connectionEstablishmentError (22), 1907 invalidMessageReceived (23), 1908 localNodeTransmissionError (24), 1909 remoteNodeTransmissionError (25), 1910 routingFailure (26), 1912 --Values 27-50 are reserved for communications alarm related 1913 --probable causes 1914 -- The following are used with equipment alarm. 1916 backplaneFailure (51), 1917 dataSetProblem (52), 1918 equipmentIdentifierDuplication (53), 1919 externalIFDeviceProblem (54), 1920 lineCardProblem (55), 1921 multiplexerProblem (56), 1922 nEIdentifierDuplication (57), 1923 powerProblem (58), 1924 processorProblem (59), 1925 protectionPathFailure (60), 1926 receiverFailure (61), 1927 replaceableUnitMissing (62), 1928 replaceableUnitTypeMismatch (63), 1929 synchronizationSourceMismatch (64), 1930 terminalProblem (65), 1931 timingProblem (66), 1932 transmitterFailure (67), 1933 trunkCardProblem (68), 1934 replaceableUnitProblem (69), 1935 realTimeClockFailure (70), 1936 --An equipment alarm to be issued if the system detects that the 1937 --real time clock has failed 1938 antennaFailure (71), 1939 batteryChargingFailure (72), 1940 diskFailure (73), 1941 frequencyHoppingFailure (74), 1942 iODeviceError (75), 1943 lossOfSynchronisation (76), 1944 lossOfRedundancy (77), 1945 powerSupplyFailure (78), 1946 signalQualityEvaluationFailure (79), 1947 tranceiverFailure (80), 1948 protectionMechanismFailure (81), 1949 protectingResourceFailure (82), 1950 -- Values 83-100 are reserved for equipment alarm related probable 1951 -- causes 1952 -- The following are used with environmental alarm. 1953 airCompressorFailure (101), 1954 airConditioningFailure (102), 1955 airDryerFailure (103), 1956 batteryDischarging (104), 1957 batteryFailure (105), 1958 commercialPowerFailure (106), 1959 coolingFanFailure (107), 1960 engineFailure (108), 1961 fireDetectorFailure (109), 1962 fuseFailure (110), 1963 generatorFailure (111), 1964 lowBatteryThreshold (112), 1965 pumpFailure (113), 1966 rectifierFailure (114), 1967 rectifierHighVoltage (115), 1968 rectifierLowFVoltage (116), 1969 ventilationsSystemFailure (117), 1970 enclosureDoorOpen (118), 1971 explosiveGas (119), 1972 fire (120), 1973 flood (121), 1974 highHumidity (122), 1975 highTemperature (123), 1976 highWind (124), 1977 iceBuildUp (125), 1978 intrusionDetection (126), 1979 lowFuel (127), 1980 lowHumidity (128), 1981 lowCablePressure (129), 1982 lowTemperatue (130), 1983 lowWater (131), 1984 smoke (132), 1985 toxicGas (133), 1986 coolingSystemFailure (134), 1987 externalEquipmentFailure (135), 1988 externalPointFailure (136), 1989 -- Values 137-150 are reserved for environmental alarm related 1990 -- probable causes 1991 -- The following are used with Processing error alarm. 1992 storageCapacityProblem (151), 1993 memoryMismatch (152), 1994 corruptData (153), 1995 outOfCPUCycles (154), 1996 sfwrEnvironmentProblem (155), 1997 sfwrDownloadFailure (156), 1998 lossOfRealTimel (157), 1999 --A processing error alarm to be issued after the system has 2000 --reinitialised. This will indicate 2001 --to the management systems that the view they have of the managed 2002 --system may no longer 2003 --be valid. Usage example: The managed 2004 --system issues this alarm after a reinitialization with severity 2005 --warning to inform the 2006 --management system about the event. No clearing notification will 2007 --be sent. 2008 applicationSubsystemFailure (158), 2009 configurationOrCustomisationError (159), 2010 databaseInconsistency (160), 2011 fileError (161), 2012 outOfMemory (162), 2013 softwareError (163), 2014 timeoutExpired (164), 2015 underlayingResourceUnavailable (165), 2016 versionMismatch (166), 2017 --Values 168-200 are reserved for processing error alarm related 2018 -- probable causes. 2020 bandwidthReduced (201), 2021 congestion (202), 2022 excessiveErrorRate (203), 2023 excessiveResponseTime (204), 2024 excessiveRetransmissionRate (205), 2025 reducedLoggingCapability (206), 2026 systemResourcesOverload (207 ), 2027 -- The following were defined X.733 2028 adapterError (500), 2029 applicationSubsystemFailture (501), 2030 bandwidthReducedX733 (502), 2031 callEstablishmentError (503), 2032 communicationsProtocolError (504), 2033 communicationsSubsystemFailure (505), 2034 configurationOrCustomizationError (506), 2035 congestionX733 (507), 2036 coruptData (508), 2037 cpuCyclesLimitExceeded (509), 2038 dataSetOrModemError (510), 2039 degradedSignalX733 (511), 2040 dteDceInterfaceError (512), 2041 enclosureDoorOpenX733 (513), 2042 equipmentMalfunction (514), 2043 excessiveVibration (515), 2044 fileErrorX733 (516), 2045 fireDetected (517), 2046 framingErrorX733 (518), 2047 heatingVentCoolingSystemProblem (519), 2048 humidityUnacceptable (520), 2049 inputOutputDeviceError (521), 2050 inputDeviceError (522), 2051 lanError (523), 2052 leakDetected (524), 2053 localNodeTransmissionErrorX733 (525), 2054 lossOfFrameX733 (526), 2055 lossOfSignalX733 (527), 2056 materialSupplyExhausted (528), 2057 multiplexerProblemX733 (529), 2058 outOfMemoryX733 (530), 2059 ouputDeviceError (531), 2060 performanceDegraded (532), 2061 powerProblems (533), 2062 pressureUnacceptable (534), 2063 processorProblems (535), 2064 pumpFailureX733 (536), 2065 queueSizeExceeded (537), 2066 receiveFailureX733 (538), 2067 receiverFailureX733 (539), 2068 remoteNodeTransmissionErrorX733 (540), 2069 resourceAtOrNearingCapacity (541), 2070 responseTimeExecessive (542), 2071 retransmissionRateExcessive (543), 2072 softwareErrorX733 (544), 2073 softwareProgramAbnormallyTerminated (545), 2074 softwareProgramError (546), 2075 storageCapacityProblemX733 (547), 2076 temperatureUnacceptable (548), 2077 thresholdCrossed (549), 2078 timingProblemX733 (550), 2079 toxicLeakDetected (551), 2080 transmitFailureX733 (552), 2081 transmiterFailure (553), 2082 underlyingResourceUnavailable (554), 2083 versionMismatchX733 (555), 2084 -- The following are defined in X.736 2085 authenticationFailure (600), 2086 breachOfConfidentiality (601), 2087 cableTamper (602), 2088 delayedInformation (603), 2089 denialOfService (604), 2090 duplicateInformation (605), 2091 informationMissing (606), 2092 informationModificationDetected (607), 2093 informationOutOfSequence (608), 2094 keyExpired (609), 2095 nonRepudiationFailure (610), 2096 outOfHoursActivity (611), 2097 outOfService (612), 2098 proceduralError (613), 2099 unauthorizedAccessAttempt (614), 2100 unexpectedInformation (615), 2102 other (1024) 2103 } 2105 IANAItuEventType ::= TEXTUAL-CONVENTION 2106 STATUS current 2107 DESCRIPTION 2108 "The ITU event Type values. 2110 The Internet Assigned Number Authority (IANA) is 2111 responsible for the assignment of all Internet numbers, 2112 including various SNMP-related numbers, and specifically, 2113 new IANAEventType values. See http://www.iana.org " 2114 REFERENCE 2115 "ITU Recommendation X.736, 'Information Technology - Open 2116 Systems Interconnection - System Management: Security 2117 Alarm Reporting Function', 1992" 2118 SYNTAX INTEGER 2119 { 2120 other (1), 2121 communicationsAlarm (2), 2122 qualityOfServiceAlarm (3), 2123 processingErrorAlarm (4), 2124 equipmentAlarm (5), 2125 environmentalAlarm (6), 2126 integrityViolation (7), 2127 operationalViolation (8), 2128 physicalViolation (9), 2129 securityServiceOrMechanismViolation (10), 2130 timeDomainViolation (11) 2131 } 2133 END 2135 5.3 Textual Conventions 2137 ITU-ALARM-TC DEFINITIONS ::= BEGIN 2139 IMPORTS 2140 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 2141 TEXTUAL-CONVENTION FROM SNMPv2-TC; 2143 ituAlarmTc MODULE-IDENTITY 2144 LAST-UPDATED "200311170000Z" 2145 ORGANIZATION "IETF Distributed Management Working Group" 2146 CONTACT-INFO 2147 " WG EMail: disman@ietf.org 2148 Subscribe: disman-request@ietf.org 2149 http://www.ietf.org/html.charters/disman-charter.html 2151 Chair: Randy Presuhn 2152 randy_presuhn@mindspring.com 2154 Editors: Sharon Chisholm 2155 Nortel Networks 2156 PO Box 3511 Station C 2157 Ottawa, Ont. K1Y 4H7 2158 Canada 2159 schishol@nortelnetworks.com 2161 Dan Romascanu 2162 Avaya 2163 Atidim Technology Park, Bldg. #3 2164 Tel Aviv, 61131 2165 Israel 2166 Tel: +972-3-645-8414 2167 Email: dromasca@avaya.com" 2168 DESCRIPTION 2169 "This MIB module defines the ITU Alarm 2170 textual convention for objects not expected to require 2171 regular extension. 2173 Copyright (C) The Internet Society (2003). The 2174 initial version of this MIB module was published 2175 in RFC YYYY. For full legal notices see the RFC 2176 itself. Supplementary information may be available on: 2177 http://www.ietf.org/copyrights/ianamib.html" 2178 -- RFC Ed.: replace yyyy with actual RFC number & remove 2179 -- this note 2180 REVISION "200311170000Z" 2181 DESCRIPTION 2182 "Initial version, published as RFC yyyy." 2183 -- RFC-Editor assigns yyyy 2184 ::= { mib-2 XX } -- to be assigned by IANA 2186 ItuPerceivedSeverity ::= TEXTUAL-CONVENTION 2187 STATUS current 2188 DESCRIPTION 2189 "ITU perceived severity values" 2190 REFERENCE 2191 "ITU Recommendation M.3100, 'Generic Network Information 2192 Model', 1995 2193 ITU Recommendation X.733, 'Information Technology - Open 2194 Systems Interconnection - System Management: Alarm 2195 Reporting Function', 1992" 2196 SYNTAX INTEGER 2197 { 2198 cleared (1), 2199 indeterminate (2), 2200 critical (3), 2201 major (4), 2202 minor (5), 2203 warning (6) 2204 } 2206 ItuTrendIndication ::= TEXTUAL-CONVENTION 2207 STATUS current 2208 DESCRIPTION 2209 "ITU trend indication values for alarms." 2210 REFERENCE 2211 "ITU Recommendation M.3100, 'Generic Network Information 2212 Model', 1995 2213 ITU Recommendation X.733, 'Information Technology - Open 2214 Systems Interconnection - System Management: Alarm 2215 Reporting Function', 1992" 2216 SYNTAX INTEGER 2217 { 2218 moreSevere (1), 2219 noChange (2), 2220 lessSevere (3) 2221 } 2223 END 2225 5.4 Definitions 2227 ITU-ALARM-MIB DEFINITIONS ::= BEGIN 2229 IMPORTS 2230 MODULE-IDENTITY, OBJECT-TYPE, 2231 Counter32, Gauge32, mib-2 FROM SNMPv2-SMI 2232 AutonomousType, RowPointer FROM SNMPv2-TC 2233 SnmpAdminString FROM 2234 SNMP-FRAMEWORK-MIB 2235 alarmListName, alarmModelIndex, 2236 alarmActiveDateAndTime, alarmActiveIndex 2237 FROM ALARM-MIB 2238 ItuPerceivedSeverity, 2239 ItuTrendIndication FROM ITU-ALARM-TC 2240 IANAItuProbableCause, 2241 IANAItuEventType FROM IANA-ITU-ALARM-TC 2242 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 2243 ZeroBasedCounter32 FROM RMON2-MIB; 2245 ituAlarmMIB MODULE-IDENTITY 2246 LAST-UPDATED "200311170000Z" 2247 ORGANIZATION "IETF Distributed Management Working Group" 2248 CONTACT-INFO 2249 "WG EMail: disman@ietf.org 2250 Subscribe: disman-request@ietf.org 2251 http://www.ietf.org/html.charters/disman-charter.html 2253 Chair: Randy Presuhn 2254 randy_presuhn@mindspring.com 2256 Editors: Sharon Chisholm 2257 Nortel Networks 2258 PO Box 3511 Station C 2259 Ottawa, Ont. K1Y 4H7 2260 Canada 2261 schishol@nortelnetworks.com 2263 Dan Romascanu 2264 Avaya 2265 Atidim Technology Park, Bldg. #3 2266 Tel Aviv, 61131 2267 Israel 2268 Tel: +972-3-645-8414 2269 Email: dromasca@avaya.com" 2270 DESCRIPTION 2271 "The MIB module describes ITU Alarm information 2272 as defined in ITU Recommendation M.3100 [M.3100], 2273 X.733 [X.733] and X.736 [X.736]. 2275 Copyright (C) The Internet Society (2003). The 2276 initial version of this MIB module was published 2277 in RFC YYYY. For full legal notices see the RFC 2278 itself. Supplementary information may be available on: 2279 http://www.ietf.org/copyrights/ianamib.html" 2280 -- RFC Ed.: replace yyyy with actual RFC number & remove 2281 -- this note 2282 REVISION "200311170000Z" 2283 DESCRIPTION 2284 "Initial version, published as RFC yyyy." 2285 -- RFC-Editor assigns yyyy 2286 ::= { mib-2 XX } -- to be assigned by IANA 2288 ituAlarmObjects OBJECT IDENTIFIER ::= { ituAlarmMIB 1 } 2290 ituAlarmModel OBJECT IDENTIFIER ::= { ituAlarmObjects 1 } 2292 ituAlarmActive OBJECT IDENTIFIER ::= { ituAlarmObjects 2 } 2294 ituAlarmTable OBJECT-TYPE 2295 SYNTAX SEQUENCE OF ItuAlarmEntry 2296 MAX-ACCESS not-accessible 2297 STATUS current 2298 DESCRIPTION 2299 "A table of ITU Alarm information for possible alarms 2300 on the system." 2301 ::= { ituAlarmModel 1 } 2303 ituAlarmEntry OBJECT-TYPE 2304 SYNTAX ItuAlarmEntry 2305 MAX-ACCESS not-accessible 2306 STATUS current 2307 DESCRIPTION 2308 "Entries appear in this table whenever an entry is created 2309 in the alarmModelTable with a value of alarmModelState in 2310 the range from 1 to 6. Entries disappear from this table 2311 whenever the corresponding entries are deleted from the 2312 alarmModelTable, including in cases where those entries 2313 have been deleted due to local system action. The value of 2314 alarmModelSpecificPointer has no effect on the creation 2315 or deletion of entries in this table. Values of 2316 alarmModelState map to values of ituAlarmPerceivedSeverity 2317 as follows: 2319 alarmModelState -> ituAlarmPerceivedSeverity 2320 1 -> clear (1) 2321 2 -> indeterminate (2) 2322 3 -> warning (6) 2323 4 -> minor (5) 2324 5 -> major (4) 2325 6 -> critical (3) 2327 All other values of alarmModelState MUST NOT appear 2328 in this table. 2330 This table MUST be persistent across system reboots." 2331 INDEX { alarmListName, alarmModelIndex, 2332 ituAlarmPerceivedSeverity } 2333 ::= { ituAlarmTable 1 } 2335 ItuAlarmEntry ::= SEQUENCE { 2336 ituAlarmPerceivedSeverity ItuPerceivedSeverity, 2337 ituAlarmEventType IANAItuEventType, 2338 ituAlarmProbableCause IANAItuProbableCause, 2339 ituAlarmAdditionalText SnmpAdminString, 2340 ituAlarmGenericModel RowPointer } 2342 ituAlarmPerceivedSeverity OBJECT-TYPE 2343 SYNTAX ItuPerceivedSeverity 2344 MAX-ACCESS not-accessible 2345 STATUS current 2346 DESCRIPTION 2347 "ITU perceived severity values." 2348 REFERENCE 2349 "ITU Recommendation M.3100, 'Generic Network Information 2350 Model', 1995 2351 ITU Recommendation X.733, 'Information Technology - Open 2352 Systems Interconnection - System Management: Alarm 2353 Reporting Function', 1992" 2354 ::= { ituAlarmEntry 1 } 2356 ituAlarmEventType OBJECT-TYPE 2357 SYNTAX IANAItuEventType 2358 MAX-ACCESS read-write 2359 STATUS current 2360 DESCRIPTION 2361 "Represents the event type values for the alarms" 2362 REFERENCE 2363 "ITU Recommendation M.3100, 'Generic Network Information 2364 Model', 1995 2365 ITU Recommendation X.733, 'Information Technology - Open 2366 Systems Interconnection - System Management: Alarm 2367 Reporting Function', 1992 2368 ITU Recommendation X.736, 'Information Technology - Open 2369 Systems Interconnection - System Management: Security 2370 Alarm Reporting Function', 1992" 2371 ::= { ituAlarmEntry 2 } 2373 ituAlarmProbableCause OBJECT-TYPE 2374 SYNTAX IANAItuProbableCause 2375 MAX-ACCESS read-write 2376 STATUS current 2378 DESCRIPTION 2379 "ITU probable cause values." 2381 REFERENCE 2382 "ITU Recommendation M.3100, 'Generic Network Information 2383 Model', 1995 2384 ITU Recommendation X.733, 'Information Technology - Open 2385 Systems Interconnection - System Management: Alarm 2386 Reporting Function', 1992 2387 ITU Recommendation X.736, 'Information Technology - Open 2388 Systems Interconnection - System Management: Security 2389 Alarm Reporting Function', 1992" 2390 ::= { ituAlarmEntry 3 } 2392 ituAlarmAdditionalText OBJECT-TYPE 2393 SYNTAX SnmpAdminString 2394 MAX-ACCESS read-write 2395 STATUS current 2396 DESCRIPTION 2397 "Represents the additional text field for the alarm." 2398 REFERENCE 2399 "ITU Recommendation M.3100, 'Generic Network Information 2400 Model', 1995 2401 ITU Recommendation X.733, 'Information Technology - Open 2402 Systems Interconnection - System Management: Alarm 2403 Reporting Function', 1992" 2404 ::= { ituAlarmEntry 4} 2406 ituAlarmGenericModel OBJECT-TYPE 2407 SYNTAX RowPointer 2408 MAX-ACCESS read-write 2409 STATUS current 2410 DESCRIPTION 2411 "This object points to the corresponding 2412 row in the alarmModelTable for this alarm severity. 2414 This corresponding entry to alarmModelTable could also 2415 be derived by performing the reverse of the mapping 2416 from alarmModelState to ituAlarmPerceivedSeverity defined 2417 in the description of ituAlarmEntry to determine the 2418 appropriate { alarmListName, alarmModelIndex, alarmModelState } 2419 for this { alarmListName, alarmModelIndex, 2420 ituAlarmPerceivedSeverity }." 2421 ::= { ituAlarmEntry 5 } 2423 -- ITU Active Alarm Table -- 2425 ituAlarmActiveTable OBJECT-TYPE 2426 SYNTAX SEQUENCE OF ItuAlarmActiveEntry 2427 MAX-ACCESS not-accessible 2428 STATUS current 2429 DESCRIPTION 2430 "A table of ITU information for active alarms entries." 2431 ::= { ituAlarmActive 1 } 2433 ituAlarmActiveEntry OBJECT-TYPE 2434 SYNTAX ItuAlarmActiveEntry 2435 MAX-ACCESS not-accessible 2436 STATUS current 2437 DESCRIPTION 2438 "Entries appear in this table when alarms are active. They 2439 are removed when the alarm is no longer occurring." 2440 INDEX { alarmListName, alarmActiveDateAndTime, 2441 alarmActiveIndex } 2442 ::= { ituAlarmActiveTable 1 } 2444 ItuAlarmActiveEntry ::= SEQUENCE { 2445 ituAlarmActiveTrendIndication ItuTrendIndication, 2446 ituAlarmActiveDetector AutonomousType, 2447 ituAlarmActiveServiceProvider AutonomousType, 2448 ituAlarmActiveServiceUser AutonomousType 2449 } 2451 ituAlarmActiveTrendIndication OBJECT-TYPE 2452 SYNTAX ItuTrendIndication 2453 MAX-ACCESS read-only 2454 STATUS current 2455 DESCRIPTION 2456 "Represents the trend indication values for the alarms." 2457 REFERENCE 2458 "ITU Recommendation M.3100, 'Generic Network Information 2459 Model', 1995 2460 ITU Recommendation X.733, 'Information Technology - Open 2461 Systems Interconnection - System Management: Alarm 2462 Reporting Function', 1992" 2463 ::= { ituAlarmActiveEntry 1 } 2465 ituAlarmActiveDetector OBJECT-TYPE 2466 SYNTAX AutonomousType 2467 MAX-ACCESS read-only 2468 STATUS current 2469 DESCRIPTION 2470 "Represents the SecurityAlarmDetector object." 2471 REFERENCE 2472 "ITU Recommendation X.736, 'Information Technology - Open 2473 Systems Interconnection - System Management: Security 2474 Alarm Reporting Function', 1992" 2475 ::= { ituAlarmActiveEntry 2 } 2477 ituAlarmActiveServiceProvider OBJECT-TYPE 2478 SYNTAX AutonomousType 2479 MAX-ACCESS read-only 2480 STATUS current 2481 DESCRIPTION 2482 "Represents the ServiceProvider object." 2483 REFERENCE 2484 "ITU Recommendation X.736, 'Information Technology - Open 2485 Systems Interconnection - System Management: Security 2486 Alarm Reporting Function', 1992" 2487 ::= { ituAlarmActiveEntry 3 } 2489 ituAlarmActiveServiceUser OBJECT-TYPE 2490 SYNTAX AutonomousType 2491 MAX-ACCESS read-only 2492 STATUS current 2493 DESCRIPTION 2494 "Represents the ServiceUser object." 2495 REFERENCE 2496 "ITU Recommendation X.736, 'Information Technology - Open 2497 Systems Interconnection - System Management: Security 2498 Alarm Reporting Function', 1992" 2499 ::= { ituAlarmActiveEntry 4 } 2501 -- Statistics and Counters 2503 ituAlarmActiveStatsTable OBJECT-TYPE 2504 SYNTAX SEQUENCE OF ItuAlarmActiveStatsEntry 2505 MAX-ACCESS not-accessible 2506 STATUS current 2507 DESCRIPTION 2508 "This table represents the ITU alarm statistics 2509 information." 2510 ::= { ituAlarmActive 2 } 2512 ituAlarmActiveStatsEntry OBJECT-TYPE 2513 SYNTAX ItuAlarmActiveStatsEntry 2514 MAX-ACCESS not-accessible 2515 STATUS current 2516 DESCRIPTION 2517 "Statistics on the current active ITU alarms." 2518 INDEX { alarmListName } 2520 ::= { ituAlarmActiveStatsTable 1 } 2522 ItuAlarmActiveStatsEntry ::= 2523 SEQUENCE { 2524 ituAlarmActiveStatsIndeterminateCurrent Gauge32, 2525 ituAlarmActiveStatsCriticalCurrent Gauge32, 2526 ituAlarmActiveStatsMajorCurrent Gauge32, 2527 ituAlarmActiveStatsMinorCurrent Gauge32, 2528 ituAlarmActiveStatsWarningCurrent Gauge32, 2529 ituAlarmActiveStatsIndeterminates ZeroBasedCounter32, 2530 ituAlarmActiveStatsCriticals ZeroBasedCounter32, 2531 ituAlarmActiveStatsMajors ZeroBasedCounter32, 2532 ituAlarmActiveStatsMinors ZeroBasedCounter32, 2533 ituAlarmActiveStatsWarnings ZeroBasedCounter32 2534 } 2536 ituAlarmActiveStatsIndeterminateCurrent OBJECT-TYPE 2537 SYNTAX Gauge32 2538 MAX-ACCESS read-only 2539 STATUS current 2540 DESCRIPTION 2541 "A count of the current number of active alarms with a 2542 ituAlarmPerceivedSeverity of indeterminate." 2543 ::= { ituAlarmActiveStatsEntry 1 } 2545 ituAlarmActiveStatsCriticalCurrent OBJECT-TYPE 2546 SYNTAX Gauge32 2547 MAX-ACCESS read-only 2548 STATUS current 2549 DESCRIPTION 2550 "A count of the current number of active alarms with a 2551 ituAlarmPerceivedSeverity of critical." 2552 ::= { ituAlarmActiveStatsEntry 2 } 2554 ituAlarmActiveStatsMajorCurrent OBJECT-TYPE 2555 SYNTAX Gauge32 2556 MAX-ACCESS read-only 2557 STATUS current 2558 DESCRIPTION 2559 "A count of the current number of active alarms with a 2560 ituAlarmPerceivedSeverity of major." 2561 ::= { ituAlarmActiveStatsEntry 3 } 2563 ituAlarmActiveStatsMinorCurrent OBJECT-TYPE 2564 SYNTAX Gauge32 2565 MAX-ACCESS read-only 2566 STATUS current 2567 DESCRIPTION 2568 "A count of the current number of active alarms with a 2569 ituAlarmPerceivedSeverity of minor." 2570 ::= { ituAlarmActiveStatsEntry 4 } 2572 ituAlarmActiveStatsWarningCurrent OBJECT-TYPE 2573 SYNTAX Gauge32 2574 MAX-ACCESS read-only 2575 STATUS current 2576 DESCRIPTION 2577 "A count of the current number of active alarms with a 2578 ituAlarmPerceivedSeverity of warning." 2579 ::= { ituAlarmActiveStatsEntry 5 } 2581 ituAlarmActiveStatsIndeterminates OBJECT-TYPE 2582 SYNTAX ZeroBasedCounter32 2583 MAX-ACCESS read-only 2584 STATUS current 2585 DESCRIPTION 2586 "A count of the total number of active alarms with a 2587 ituAlarmPerceivedSeverity of indeterminate since system 2588 restart." 2589 ::= { ituAlarmActiveStatsEntry 6 } 2591 ituAlarmActiveStatsCriticals OBJECT-TYPE 2592 SYNTAX ZeroBasedCounter32 2593 MAX-ACCESS read-only 2594 STATUS current 2595 DESCRIPTION 2596 "A count of the total number of active alarms with a 2597 ituAlarmPerceivedSeverity of critical since system restart." 2598 ::= { ituAlarmActiveStatsEntry 7 } 2600 ituAlarmActiveStatsMajors OBJECT-TYPE 2601 SYNTAX ZeroBasedCounter32 2602 MAX-ACCESS read-only 2603 STATUS current 2604 DESCRIPTION 2605 "A count of the total number of active alarms with a 2606 ituAlarmPerceivedSeverity of major since system restart." 2607 ::= { ituAlarmActiveStatsEntry 8 } 2609 ituAlarmActiveStatsMinors OBJECT-TYPE 2610 SYNTAX ZeroBasedCounter32 2611 MAX-ACCESS read-only 2612 STATUS current 2613 DESCRIPTION 2614 "A count of the total number of active alarms with a 2615 ituAlarmPerceivedSeverity of minor since system restart." 2616 ::= { ituAlarmActiveStatsEntry 9 } 2618 ituAlarmActiveStatsWarnings OBJECT-TYPE 2619 SYNTAX ZeroBasedCounter32 2620 MAX-ACCESS read-only 2621 STATUS current 2622 DESCRIPTION 2623 "A count of the total number of active alarms with a 2624 ituAlarmPerceivedSeverity of warning since system restart." 2625 ::= { ituAlarmActiveStatsEntry 10 } 2627 -- Conformance 2629 ituAlarmConformance OBJECT IDENTIFIER ::= { ituAlarmMIB 2 } 2630 ituAlarmCompliances OBJECT IDENTIFIER ::= { ituAlarmConformance 1 } 2632 ituAlarmCompliance MODULE-COMPLIANCE 2633 STATUS current 2634 DESCRIPTION 2635 "The compliance statement for systems supporting 2636 the ITU Alarm MIB." 2637 MODULE -- this module 2638 MANDATORY-GROUPS { 2639 ituAlarmGroup 2640 } 2641 GROUP ituAlarmServiceUserGroup 2642 DESCRIPTION 2643 "This group is optional." 2644 GROUP ituAlarmSecurityGroup 2645 DESCRIPTION 2646 "This group is optional." 2647 GROUP ituAlarmStatisticsGroup 2648 DESCRIPTION 2649 "This group is optional." 2650 ::= { ituAlarmCompliances 1 } 2652 ituAlarmGroups OBJECT IDENTIFIER ::= { ituAlarmConformance 2 } 2654 ituAlarmGroup OBJECT-GROUP 2655 OBJECTS { 2656 ituAlarmEventType, 2657 ituAlarmProbableCause, 2658 ituAlarmGenericModel 2659 } 2660 STATUS current 2661 DESCRIPTION 2662 "ITU alarm details list group." 2663 ::= { ituAlarmGroups 1} 2665 ituAlarmServiceUserGroup OBJECT-GROUP 2666 OBJECTS { 2667 ituAlarmAdditionalText, 2668 ituAlarmActiveTrendIndication 2669 } 2670 STATUS current 2671 DESCRIPTION 2672 "The use of these parameters is a service-user option." 2673 ::= { ituAlarmGroups 2 } 2675 ituAlarmSecurityGroup OBJECT-GROUP 2676 OBJECTS { 2677 ituAlarmActiveDetector, 2678 ituAlarmActiveServiceProvider, 2679 ituAlarmActiveServiceUser 2680 } 2681 STATUS current 2682 DESCRIPTION 2683 "Security Alarm Reporting Function" 2684 REFERENCE 2685 "ITU Recommendation X.736, 'Information Technology - Open 2686 Systems Interconnection - System Management: Security 2687 Alarm Reporting Function', 1992" 2689 ::= { ituAlarmGroups 3 } 2691 ituAlarmStatisticsGroup OBJECT-GROUP 2692 OBJECTS { 2693 ituAlarmActiveStatsIndeterminateCurrent, 2694 ituAlarmActiveStatsCriticalCurrent, 2695 ituAlarmActiveStatsMajorCurrent, 2696 ituAlarmActiveStatsMinorCurrent, 2697 ituAlarmActiveStatsWarningCurrent, 2698 ituAlarmActiveStatsIndeterminates, 2699 ituAlarmActiveStatsCriticals, 2700 ituAlarmActiveStatsMajors, 2701 ituAlarmActiveStatsMinors, 2702 ituAlarmActiveStatsWarnings 2703 } 2704 STATUS current 2705 DESCRIPTION 2706 "ITU Active Alarm Statistics." 2707 ::= { ituAlarmGroups 4 } 2709 END 2711 6. Examples 2713 6.1 Alarms Based on linkUp/linkDown Notifications 2715 This example demonstrates an interface-based alarm that goes into a 2716 state of "warning" when a linkDown Notification [RFC2863] occurs but 2717 the ifAdminStatus indicates the interface was taken down 2718 administratively. If IfAdminStatus is "up" when the linkDown 2719 Notification occurs, then there is a problem, so the state of the 2720 alarm is critical. A linkUp alarm clears the alarm. 2722 linkDown NOTIFICATION-TYPE 2723 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 2724 STATUS current 2725 DESCRIPTION 2726 "" 2727 ::= { snmpTraps 3 } 2729 linkUp NOTIFICATION-TYPE 2730 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 2731 STATUS current 2732 DESCRIPTION 2733 "" 2734 ::= { snmpTraps 4 } 2736 alarmModelIndex 3 2737 alarmModelState 1 2738 alarmModelNotificationId linkUp 2739 alarmModelVarbindIndex 0 2740 alarmModelVarbindValue 0 2741 alarmModelDescription "linkUp" 2742 alarmModelSpecificPointer ituAlarmEntry.3.1 2743 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2744 alarmModelResourcePrefix 0.0 2745 alarmModelRowStatus active (1) 2746 ituAlarmEventType communicationsAlarm (2) 2747 ituAlarmPerceivedSeverity cleared (1) 2748 ituAlarmGenericModel alarmModelEntry.3.1 2750 alarmModelIndex 3 2751 alarmModelState 2 2752 alarmModelNotificationId linkDown 2753 alarmModelVarbindIndex 2 2754 alarmModelVarbindValue down (2) 2755 alarmModelDescription "linkDown administratively" 2756 alarmModelSpecificPointer ituAlarmEntry.3.6 2757 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2758 alarmModelResourcePrefix 0.0 2759 alarmModelRowStatus active (1) 2760 ituAlarmEventType communicationsAlarm (2) 2761 ituAlarmPerceivedSeverity warning (6) 2762 ituAlarmGenericModel alarmModelEntry.3.2 2764 alarmModelIndex 3 2765 alarmModelState 3 2766 alarmModelNotificationId linkDown 2767 alarmModelVarbindIndex 2 2768 alarmModelVarbindValue up (1) 2769 alarmModelDescription "linkDown - confirmed problem" 2770 alarmModelSpecificPointer ituAlarmEntry.3.3 2771 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2772 alarmModelResourcePrefix 0.0 2773 alarmModelRowStatus active (1) 2774 ituAlarmEventType communicationsAlarm (2) 2775 ituAlarmPerceivedSeverity critical (3) 2776 ituAlarmGenericModel alarmModelEntry.3.3 2778 alarmActiveIndex 1 2779 alarmActiveTime 2342464573 2780 alarmActiveDateAndTime DateAndTime, 2781 alarmActiveEngineID SnmpEngineID, 2782 alarmActiveEngineAddressType ipV4 2783 alarmActiveEngineAddress 10.10.10.10 2784 alarmActiveContextName SnmpAdminString, 2785 alarmActiveVariables 3 2786 alarmActiveNotificationID 1.3.6.1.6.3.1.1.5.3 2787 alarmActiveResourceId 1.3.6.1.2.1.2.2.1.1.346 2788 alarmActiveLogPointer 0.0 2789 alarmActiveModelPointer alarmModelEntry.3.3 2790 alarmActiveSpecificPointer ituAlarmActiveEntry.1.3 2791 ituAlarmActiveTrendIndication moreSevere (1) 2792 ituAlarmDetector 0.0 2793 ituAlarmServiceProvider 0.0 2794 ituAlarmServiceUser 0.0 2796 alarmActiveVariableIndex 1 2797 alarmActiveVariableID sysUpTime.0 2798 alarmActiveVariableValueType timeTicks(3) 2799 alarmActiveVariableCounter32Val 0 2800 alarmActiveVariableUnsigned32Val 0 2801 alarmActiveVariableTimeTicksVal 46754 2802 alarmActiveVariableInteger32Val 0 2803 alarmActiveVariableOctetStringVal "" 2804 alarmActiveVariableIpAddressVal 0 2805 alarmActiveVariableOidVal 0.0 2806 alarmActiveVariableCounter64Val 0 2807 alarmActiveVariableIndex 2 2808 alarmActiveVariableID snmpTrapOID.0 2809 alarmActiveVariableValueType objectId(7) 2810 alarmActiveVariableCounter32Val 0 2811 alarmActiveVariableUnsigned32Val 0 2812 alarmActiveVariableTimeTicksVal 0 2813 alarmActiveVariableInteger32Val 0 2814 alarmActiveVariableOctetStringVal "" 2815 alarmActiveVariableIpAddressVal 0 2816 alarmActiveVariableOidVal 1.3.6.1.6.3.1.1.5.3 2817 alarmActiveVariableCounter64Val 0 2818 alarmActiveVariableIndex 3 2819 alarmActiveVariableID ifIndex 2820 alarmActiveVariableValueType integer32(4) 2821 alarmActiveVariableCounter32Val 0 2822 alarmActiveVariableUnsigned32Val 0 2823 alarmActiveVariableTimeTicksVal 0 2824 alarmActiveVariableInteger32Val 346 2825 alarmActiveVariableOctetStringVal "" 2826 alarmActiveVariableIpAddressVal 0 2827 alarmActiveVariableOidVal 0.0 2828 alarmActiveVariableCounter64Val 0 2829 alarmActiveVariableIndex 4 2830 alarmActiveVariableID ifAdminStatus 2831 alarmActiveVariableValueType integer32(4) 2832 alarmActiveVariableCounter32Val 0 2833 alarmActiveVariableUnsigned32Val 0 2834 alarmActiveVariableTimeTicksVal 0 2835 alarmActiveVariableInteger32Val up (1) 2836 alarmActiveVariableOctetStringVal "" 2837 alarmActiveVariableIpAddressVal 0 2838 alarmActiveVariableOidVal 0.0 2839 alarmActiveVariableCounter64Val 0 2840 alarmActiveVariableIndex 5 2841 alarmActiveVariableID ifOperStatus 2842 alarmActiveVariableValueType integer32(4) 2843 alarmActiveVariableCounter32Val 0 2844 alarmActiveVariableUnsigned32Val 0 2845 alarmActiveVariableTimeTicksVal 0 2846 alarmActiveVariableInteger32Val down(2) 2847 alarmActiveVariableOctetStringVal "" 2848 alarmActiveVariableIpAddressVal 0 2849 alarmActiveVariableOidVal 0.0 2850 alarmActiveVariableCounter64Val 0 2851 alarmActiveVariableOpaqueVal 2853 6.2 Temperature Alarms Using Generic Notifications 2855 Consider a system able to detect four different temperature 2856 states for a widget - normal, minor, major, critical. The 2857 system does not have any Notification definitions for these 2858 alarm states. A temperature alarm can be modelled using the 2859 generic alarm Notifications of alarmClearState and alarmActive. 2861 alarmModelIndex 5 2862 alarmModelState 1 2863 alarmModelNotificationId alarmClearState 2864 alarmModelVarbindIndex 2 2865 alarmModelVarbindValue cleared (1) 2866 alarmModelDescription "Acme Widget Temperature Normal" 2867 alarmModelSpecificPointer ituAlarmEntry.5.1 2868 alarmModelVarbindSubtree alarmActiveResourceId 2869 alarmModelResourcePrefix 0.0 2870 alarmModelRowStatus active (1) 2871 ituAlarmEventType environmentalAlarm (6) 2872 ituPerceivedSeverity cleared (1) 2873 ituAlarmGenericModel alarmModelEntry.5.1 2875 alarmModelIndex 5 2876 alarmModelState 2 2877 alarmModelNotificationId alarmActiveState 2878 alarmModelVarbindIndex 2 2879 alarmModelVarbindValue minor (5) 2880 alarmModelDescription "Acme Widget Temperature Minor" 2881 alarmModelSpecificPointer ituAlarmEntry.5.5 2882 alarmModelVarbindSubtree alarmActiveResourceId 2883 alarmModelResourcePrefix 0.0 2884 alarmModelRowStatus active (1) 2885 ituAlarmEventState environmentalAlarm (6) 2886 ituPerceivedSeverity minor (5) 2887 ituAlarmGenericModel alarmModelEntry.5.2 2889 alarmModelIndex 5 2890 alarmModelState 3 2891 alarmModelNotificationId alarmActiveState 2892 alarmModelVarbindIndex 2 2893 alarmModelVarbindValue major (4) 2894 alarmModelDescription "Acme Widget Temperature Major" 2895 alarmModelSpecificPointer ituAlarmEntry.5.4 2896 alarmModelVarbindSubtree alarmActiveResourceId 2897 alarmModelResourcePrefix 0.0 2898 alarmModelRowStatus active (1) 2899 ituAlarmEventType environmentalAlarm (6) 2900 ituPerceivedSeverity major (4) 2901 ituAlarmGenericModel alarmModelEntry.5.3 2903 alarmModelIndex 5 2904 alarmModelState 4 2905 alarmModelNotificationId alarmActiveState 2906 alarmModelVarbindIndex 2 2907 alarmModelVarbindValue critical (3) 2908 alarmModelDescription "Acme Widget Temperature Critical" 2909 alarmModelSpecificPointer ituAlarmEntry.5.3 2910 alarmModelVarbindSubtree alarmActiveResourceId 2911 alarmModelResourcePrefix 0.0 2912 alarmModelRowStatus active (1) 2913 ituAlarmEventType environmentalAlarm (6) 2914 ituPerceivedSeverity critical (3) 2915 ituAlarmGenericModel alarmModelEntry.5.4 2917 6.3 Temperature Alarms Without Notifications 2919 Consider a system able to detect four different temperature 2920 states for a widget - normal, minor, major, critical. The 2921 system does not have any Notification definitions for these 2922 alarm states. A temperature alarm can be modelled without 2923 specifying any Notifications in the alarm model. When a 2924 temperature state other than normal is detected, an instance 2925 of this alarm would be added to the active alarm table, but 2926 no Notifications would be sent out. 2928 This could alternatively be accomplished using the models from 2929 example 6.2 and by not specifying any target managers in the 2930 SNMP-TARGET-MIB, which would allow the alarm state 2931 Notifications to be logged in the Notification Log while 2932 still preventing Notifications from being transmitted 2933 on the wire. 2935 alarmModelIndex 6 2936 alarmModelState 1 2937 alarmModelNotificationId 0.0 2938 alarmModelVarbindIndex 0 2939 alarmModelVarbindValue 0 2940 alarmModelDescription "Widget Temperature" 2941 alarmModelSpecificPointer ituAlarmEntry.6.1 2942 alarmModelVarbindSubtree 0.0 2943 alarmModelResourcePrefix 0.0 2944 alarmModelRowStatus active (1) 2945 ituAlarmEventType environmentalAlarm (6) 2946 ituPerceivedSeverity cleared (1) 2947 ituAlarmGenericModel alarmModelEntry.6.1 2949 alarmModelIndex 6 2950 alarmModelState 2 2951 alarmModelNotificationId 0.0 2952 alarmModelVarbindIndex 0 2953 alarmModelVarbindValue 0 2954 alarmModelDescription "Widget Temperature" 2955 alarmModelSpecificPointer ituAlarmEntry.6.5 2956 alarmModelVarbindSubtree 0.0 2957 alarmModelResourcePrefix 0.0 2958 alarmModelRowStatus active (1) 2959 ituAlarmEventState environmentalAlarm (6) 2960 ituAlarmPerceivedSeverity minor (5) 2961 ituAlarmGenericModel alarmModelEntry.6.2 2963 alarmModelIndex 6 2964 alarmModelState 3 2965 alarmModelNotificationId 0.0 2966 alarmModelVarbindIndex 0 2967 alarmModelVarbindValue 0 2968 alarmModelDescription "Widget Temperature" 2969 alarmModelSpecificPointer ituAlarmEntry.6.4 2970 alarmModelVarbindSubtree 0.0 2971 alarmModelResourcePrefix 0.0 2972 alarmModelRowStatus active (1) 2973 ituAlarmEventType environmentalAlarm (6) 2974 ituPerceivedSeverity major (4) 2975 ituAlarmGenericModel alarmModelEntry.6.3 2977 alarmModelIndex 6 2978 alarmModelState 4 2979 alarmModelNotificationId 0.0 2980 alarmModelVarbindIndex 0 2981 alarmModelVarbindValue 0 2982 alarmModelDescription "Widget Temperature Severe" 2983 alarmModelSpecificPointer ituAlarmEntry.6.3 2984 alarmModelVarbindSubtree 0.0 2985 alarmModelResourcePrefix 0.0 2986 alarmModelRowStatus active (1) 2987 ituAlarmEventType environmentalAlarm (6) 2988 ituPerceivedSeverity critical (3) 2989 ituAlarmGenericModel alarmModelEntry.6.4 2991 6.4 Printer MIB Alarm Example 2993 Consider the following Notifications defined in the 2994 printer MIB [RFC1759]: 2996 prtAlertSeverityLevel OBJECT-TYPE 2997 -- This value is a type 1 enumeration 2998 SYNTAX INTEGER { 2999 other(1), 3000 critical(3), 3001 warning(4) 3002 } 3003 MAX-ACCESS read-only 3004 STATUS current 3005 DESCRIPTION 3006 "The level of severity of this alert table entry. The printer 3007 determines the severity level assigned to each entry into the 3008 table." 3009 ::= { prtAlertEntry 2 } 3011 printerV2Alert NOTIFICATION-TYPE 3012 OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, 3013 prtAlertGroupIndex, prtAlertLocation, prtAlertCode } 3014 STATUS current 3015 DESCRIPTION 3016 "This trap is sent whenever a critical event is added to the 3017 prtAlertTable." 3018 ::= { printerV2AlertPrefix 1 } 3020 These Notifications can be used to model a printer alarm as 3021 follows: 3023 alarmModelIndex 9 3024 alarmModelState 1 3025 alarmModelNotificationId alarmClearState 3026 alarmModelVarbindIndex 0 3027 alarmModelVarbindValue 0 3028 alarmModelDescription "Printer Alarm" 3029 alarmModelSpecificPointer 0.0 3030 alarmModelVarbindSubtree prtAlertGroup 3031 alarmModelResourcePrefix 0.0 3032 alarmModelRowStatus active (1) 3034 alarmModelIndex 9 3035 alarmModelState 2 3036 alarmModelNotificationId printerV2Alert 3037 alarmModelVarbindIndex 2 3038 alarmModelVarbindValue warning (4) 3039 alarmModelDescription "Printer Alarm" 3040 alarmModelSpecificPointer 0.0 3041 alarmModelVarbindSubtree prtAlertGroup 3042 alarmModelResourcePrefix 0.0 3043 alarmModelRowStatus active (1) 3045 alarmModelIndex 9 3046 alarmModelState 3 3047 alarmModelNotificationId printerV2Alert 3048 alarmModelVarbindIndex 2 3049 alarmModelVarbindValue other (1) 3050 alarmModelDescription "Printer Alarm - unknown severity" 3051 alarmModelSpecificPointer 0.0 3052 alarmModelVarbindSubtree prtAlertGroup 3053 alarmModelResourcePrefix 0.0 3054 alarmModelRowStatus active (1) 3056 alarmModelIndex 9 3057 alarmModelState 4 3058 alarmModelNotificationId printerV2Alert 3059 alarmModelVarbindIndex 2 3060 alarmModelVarbindValue critical (3) 3061 alarmModelDescription "Printer Alarm" 3062 alarmModelSpecificPointer 0.0 3063 alarmModelVarbindSubtree prtAlertGroup 3064 alarmModelResourcePrefix 0.0 3065 alarmModelRowStatus active (1) 3067 6.5 RMON Alarm Example 3069 The RMON MIB [RFC2819] defines a mechanism for generating 3070 threshold alarms. When the thresholds are crossed, 3071 RisingAlarm and FallingAlarm Notifications are 3072 generated as appropriate. These Notifications can 3073 be used to model an upper threshold alarm as follows: 3075 alarmModelIndex 6 3076 alarmModelState 1 3077 alarmModelNotificationId FallingAlarm 3078 alarmModelVarbindIndex 0 3079 alarmModelVarbindValue 0 3080 alarmModelDescription "RMON Rising Clear Alarm" 3081 alarmModelSpecificPointer 0.0 3082 alarmModelVarbindSubtree alarmIndex 3083 alarmModelResourcePrefix 0.0 3084 alarmModelRowStatus active (1) 3086 alarmModelIndex 6 3087 alarmModelState 2 3088 alarmModelNotificationId RisingAlarm 3089 alarmModelVarbindIndex 0 3090 alarmModelVarbindValue 0 3091 alarmModelDescription "RMON Rising Alarm" 3092 alarmModelSpecificPointer 0.0 3093 alarmModelVarbindSubtree alarmIndex 3094 alarmModelResourcePrefix 0.0 3095 alarmModelRowStatus active (1) 3097 6.6 The Lifetime of an Alarm 3099 The following example demonstrates the relationship between 3100 the active alarm table, the clear alarm table and the 3101 Notification Log MIB. 3103 Consider a system with alarms modelled as in example 1 and which 3104 also supports the informational Notification dsx3LineStatusChange. 3106 dsx3LineStatusChange NOTIFICATION-TYPE 3107 OBJECTS { dsx3LineStatus, 3108 dsx3LineStatusLastChange } 3109 STATUS current 3110 DESCRIPTION 3111 "A dsx3LineStatusChange trap is sent when the 3112 value of an instance of dsx3LineStatus changes. It 3113 can be utilized by an NMS to trigger polls. When 3114 the line status change results in a lower level 3115 line status change (i.e. ds1), then no traps for 3116 the lower level are sent." 3117 ::= { ds3Traps 0 1 } 3119 0. At system start, the active alarm table, alarm clear table and 3120 the Notification Log are all empty. 3121 ___________________________ _______________________ 3122 | alarmActiveTable | | nlmLogTable | 3123 |---------------------------| |-----------------------| 3124 | alarmActiveIndex | alarm | | nlmLogPointer | notif.| 3125 |---------------------------| |-----------------------| 3126 |___________________________| |_______________________| 3128 __________________________________________________ 3129 | alarmClearTable | 3130 |--------------------------------------------------| 3131 | alarmClear Index | alarm | 3132 |--------------------------------------------------| 3133 | | | 3134 |__________________________________________________| 3136 1. Some time later, a link goes down generating a linkDown 3137 Notification, which is sent out and logged in the 3138 Notification Log. As this Notification is modelled as 3139 an alarm state, an entry is added to the active alarm 3140 table. 3141 __________________________________________________ 3142 | alarmActiveTable | 3143 |--------------------------------------------------| 3144 | alarmActiveIndex | alarm | 3145 |--------------------------------------------------| 3146 | 1 | link down - problem confirmed | 3147 |__________________________________________________| 3149 _______________________________________________ 3150 | nlmLogTable | 3151 |-----------------------------------------------| 3152 | nlmLogPointer | Notification | 3153 |-----------------------------------------------| 3154 | 1 | linkdown | 3155 |_______________________________________________| 3157 __________________________________________________ 3158 | alarmClearTable | 3159 |--------------------------------------------------| 3160 | alarmClear Index | alarm | 3161 |--------------------------------------------------| 3162 | | | 3163 |__________________________________________________| 3165 2. Some time later, the value of an instance of dsx3LineStatus 3166 changes. This Notification is sent out and logged. As this 3167 is not modelled into an alarm state, the active alarm table 3168 remains unchanged. 3169 __________________________________________________ 3170 | alarmActiveTable | 3171 |--------------------------------------------------| 3172 | alarmActiveIndex | alarm | 3173 |--------------------------------------------------| 3174 | 1 | linkDown - problem confirmed | 3175 |__________________________________________________| 3177 _____________________________________________ 3178 | nlmLogTable | 3179 |---------------------------------------------| 3180 | nlmLogPointer | Notification | 3181 |---------------------------------------------| 3182 | 1 | linkDown | 3183 | 2 | dsx3LineStatusChange | 3184 |_____________________________________________| 3186 __________________________________________________ 3187 | alarmClearTable | 3188 |--------------------------------------------------| 3189 | alarmClear Index | alarm | 3190 |--------------------------------------------------| 3191 | | | 3192 |__________________________________________________| 3194 3. Some time later, the link goes back up. A linkUp Notification 3195 is sent out and logged. As this Notification models 3196 the clear alarm for this alarm, the alarm entry is remove 3197 from the active alarm table. An entry is added to the 3198 clear alarm table. 3199 __________________________________________________ 3200 | alarmActiveTable | 3201 |--------------------------------------------------| 3202 | alarmActiveIndex | alarm | 3203 |--------------------------------------------------| 3204 |__________________________________________________| 3206 _____________________________________________ 3207 | nlmLogTable | 3208 |---------------------------------------------| 3209 | nlmLogPointer | Notification | 3210 |---------------------------------------------| 3211 | 1 | linkDown | 3212 | 2 | dsx3LineStatusChange | 3213 | 3 | linkUp | 3214 |_____________________________________________| 3216 __________________________________________________ 3217 | alarmClearTable | 3218 |--------------------------------------------------| 3219 | alarmClear Index | alarm | 3220 |--------------------------------------------------| 3221 | 1 | linkDown - confirmed problem | 3222 |__________________________________________________| 3224 7. Security Considerations 3226 There are a number of management objects defined in this MIB module 3227 with a MAX-ACCESS clause of read-write and/or read-create. Such 3228 objects may be considered sensitive or vulnerable in some network 3229 environments. The support for SET operations in a non-secure 3230 environment without proper protection can have a negative effect on 3231 network operations. 3233 The following objects are defined with a MAX-ACCESS clause of 3234 read-write or read-create: alarmModelNotificationId, 3235 alarmModelVarbindIndex, alarmModelVarbindValue, 3236 alarmModelDescription, alarmModelSpecificPointer, 3237 alarmModelVarbindSubtree, alarmModelResourcePrefix, 3238 alarmModelRowStatus, alarmClearMaximum, ituAlarmEventType, 3239 ituAlarmProbableCause, ituAlarmAdditionalText, and 3240 ituAlarmGenericModel. 3242 Note that setting the value of alarmClearMaximum too low may result 3243 in security related alarms history being prematurely lost. 3245 Changing values of alarmModelRowStatus as part of creating and 3246 deleting rows in the alarmModelTable result in adding new alarm 3247 models to the system or taking them out respectively. These 3248 operations need to be carefully planned. Adding a new model should 3249 be made in a consistent manner to avoid the system overflow with 3250 alarms. Taking out a model should result in the deletion of all this 3251 model's related alarms in the system. 3253 SNMP versions prior to SNMPv3 did not include adequate security. 3254 Even if the network itself is secure (for example by using IPSec), 3255 even then, there is no control as to who on the secure network is 3256 allowed to access and GET/SET (read/change/create/delete) the 3257 objects in this MIB module. 3259 It is RECOMMENDED that implementers consider the security features 3260 as provided by the SNMPv3 framework (see [RFC3410], section 8), 3261 including full support for the SNMPv3 cryptographic mechanisms (for 3262 authentication and privacy). 3264 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3265 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3266 enable cryptographic security. It is then a customer/operator 3267 responsibility to ensure that the SNMP entity giving access to an 3268 instance of this MIB module is properly configured to give access to 3269 the objects only to those principals (users) that have legitimate 3270 rights to indeed GET or SET (change/create/delete) them. 3272 Note that the alarm throttling mechanism associated with the 3273 alarmActiveState and alarmActiveClear notifications only applies to 3274 a given alarm. Defining multiple alarms from the same internal 3275 stimulus may then still result in a flood of alarms into the network. 3277 Although the use of community strings in SNMPv1 is not considered an 3278 effective means of providing security, security administrators 3279 SHOULD consider whether the fact that alarmActiveContextName can 3280 reveal community string values would make this object sensitive in 3281 their environment. 3283 This MIB module can provide access to information that may also be 3284 accessed through manipulation of the SNMP-NOTIFICATION-MIB and the 3285 NOTIFICATION-LOG-MIB. This is expressed in part through the common 3286 indexing structure of nlmLogName [RFC3014], 3287 snmpNotifyFilterProfileName [RFC3413], and alarmListName. 3288 Consequently, it is RECOMMENDED that security administrators take 3289 care to configure a coherent VACM security policy. The objects 3290 alarmActiveLogPointer, alarmActiveModelPointer, 3291 alarmActiveSpecificPointer, and alarmClearModelPointer are object 3292 identifiers that reference information to which a particular user 3293 might not be given direct access. The structure of these object 3294 identifiers does not permit the extraction of any sensitive 3295 information. Two other objects, alarmClearResourceId, and 3296 alarmActiveResourceId, are also syntactically object identifiers, 3297 but their structure could provide a user with potentially useful 3298 information to which he or she might not otherwise be granted 3299 access, such as the existence of a particular resource. 3301 For further discussion of security, see section 3.4. 3303 8. Authors' Addresses 3305 Sharon Chisholm 3306 Nortel Networks 3307 PO Box 3511, Station C 3308 Ottawa, Ontario, K1Y 4H7 3309 Canada 3310 Email: schishol@nortelnetworks.com 3312 Dan Romascanu 3313 Avaya 3314 Atidim Technology Park, Bldg. #3 3315 Tel Aviv, 61131 3316 Israel 3317 Tel: +972-3-645-8414 3318 Email: dromasca@avaya.com 3320 9. Acknowledgements 3322 This document is a product of the DISMAN Working Group. 3324 10. Intellectual Property 3326 The IETF takes no position regarding the validity or scope of any 3327 intellectual property or other rights that might be claimed to pertain 3328 to the implementation or use of the technology described in this 3329 document or the extent to which any license under such rights might or 3330 might not be available; neither does it represent that it has made any 3331 effort to identify any such rights. Information on the IETF's 3332 procedures with respect to rights in standards-track and 3333 standards-related documentation can be found in RFC 2028. Copies of 3334 claims of rights made available for publication and any assurances of 3335 licenses to be made available, or the result of an attempt made to 3336 obtain a general license or permission for the use of such proprietary 3337 rights by implementors or users of this specification can be obtained 3338 from the IETF Secretariat. 3340 The IETF invites any interested party to bring to its attention any 3341 copyrights, patents or patent applications, or other proprietary rights 3342 which may cover technology that may be required to practice this 3343 standard. Please address the information to the IETF Executive 3344 Director. 3346 The IETF has been notified of intellectual property rights claimed in 3347 regard to some or all of the specification contained in this document. 3349 For more information consult the online list of claimed rights. 3351 11. References 3353 11.1 Normative References 3355 [M.3100] ITU Recommendation M.3100, "Generic Network Information 3356 Model", 1995 3358 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 3359 "Simple Network Management Protocol", STD 15, RFC 1157, 3360 May 1990. 3362 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 3363 SNMP", RFC 1215, March 1991. 3365 [RFC2026] Bradner, S., "The Internet Standards Process -- 3366 Revision 3", RFC 2026, 1996 3368 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3369 Requirement Levels", BCP 14, RFC 2119, March 1997. 3371 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3372 Rose, M., and S. Waldbusser, "Structure of Management 3373 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3374 1999. 3376 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3377 Rose, M., and S. Waldbusser, "Textual Conventions for 3378 SMIv2", STD 58, RFC 2579, April 1999. 3380 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3381 Rose, M., and S. Waldbusser, "Conformance Statements for 3382 SMIv2", STD 58, RFC 2580, April 1999 3384 [RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, 3385 J., "Textual Conventions for Internet Network Addresses", 3386 May 2002. 3388 [RFC3411] Harrington, D., Presuhn, R., Wijnen, B., "An Architecture 3389 for Describing Simple Network Management Protocol (SNMP) 3390 Management Frameworks", RFC3411, December 2002. 3392 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3393 Applications", RFC 3414, December 2002. 3395 [RFC3415] Wijnen, B., Presuhn, R., McCloghrie K., "View-based Access 3396 Control Model (VACM) for the Simple Network Management 3397 Protocol (SNMP)", RFC3415, December 2002 3399 [RFC3416] Presuhn, R., Ed.., "Version 2 of the Protocol Operations 3400 for the Simple Network Management Protocol (SNMP).", 3401 RFC 3416, December 2002. 3403 [RFC3584] Frye, R., Levi, D., Routhier, S., Wijnen, B., 3404 "Coexistence between Version 1, Version 2, and Version 3 3405 of the Internet-standard Network Management Framework.", 3406 RFC3584, August 2003 3408 [X.733] ITU Recommendation X.733, "Information Technology - Open 3409 Systems Interconnection - System Management: Alarm 3410 Reporting Function", 1992 3412 [X.736] ITU Recommendation X.736, "Information Technology - Open 3413 Systems Interconnection - System Management: Security 3414 Alarm Reporting Function", 1992 3416 11.2 Informative References 3418 [RFC1657] Willis, S., Burruss, J., Chu, J., "Definitions of 3419 Managed Objects for the Fourth Version of the 3420 Border Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 3421 1994 3423 [RFC1759] Smith, R., Wright, F., Hastings, T., Zilles, S., 3424 Gullenskop, J., "Printer MIB", RFC 1759, March 1995 3426 [RFC2737] McCloghrie, K., Brierman, A., "Entity MIB using SMIv2", 3427 RFC2737, December 1999 3429 [RFC2788] Freed, N., Kille, S., "Network Services Monitoring MIB", 3430 RFC2788, March 2000 3432 [RFC2819] Waldbusser, S. "Remote Network Monitoring Management 3433 Information Base", RFC 2819, May 2000 3435 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group 3436 MIB using SMIv2", RFC2863, June 2000 3438 [RFC2981] Kavasseri, R., Stewart, B., "Event MIB", RFC2981, 3439 October 2000 3441 [RFC3014] Stewart, B., Kavasseri, R., "Notification Log MIB, 3442 RFC 3014, November 2000 3444 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3445 "Introduction and Applicability Statements for Internet- 3446 Standard Management Framework", RFC 3410, December 2002 3448 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3449 Simple Network Management Protocol (SNMP)". RFC 3418, 3450 2002 3452 12. Full Copyright Statement 3454 Copyright (C) The Internet Society (2003). All Rights Reserved. 3456 This document and translations of it may be copied and furnished to 3457 others, and derivative works that comment on or otherwise explain it 3458 or assist in its implementation may be prepared, copied, published 3459 and distributed, in whole or in part, without restriction of any kind, 3460 provided that the above copyright notice and this paragraph are 3461 included on all such copies and derivative works. However, this 3462 document itself may not be modified in any way, such as by removing 3463 the copyright notice or references to the Internet Society or other 3464 Internet organizations, except as needed for the purpose of 3465 developing Internet standards in which case the procedures for 3466 copyrights defined in the Internet Standards process must be followed, 3467 or as required to translate it into languages other than English. 3469 The limited permissions granted above are perpetual and will not be 3470 revoked by the Internet Society or its successors or assigns. 3472 This document and the information contained herein is provided on an 3473 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3474 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3475 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 3476 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3477 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.