idnits 2.17.1 draft-ietf-disman-alarm-mib-18.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 1824 has weird spacing: '... should come ...' == Line 1895 has weird spacing: '... should come ...' == Line 2151 has weird spacing: '... should come ...' == Line 2830 has weird spacing: '...ication mor...' == Line 3503 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 (February 2004) is 7369 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 3404, but no explicit reference was found in the text == Unused Reference: 'RFC3291' is defined on line 3423, but no explicit reference was found in the text == Unused Reference: 'RFC2737' is defined on line 3465, but no explicit reference was found in the text == Unused Reference: 'RFC2788' is defined on line 3468, 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 (~~), 12 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-18.txt D. Romascanu 4 Category: Standards Track Avaya 5 Expiration Date: July 2004 February 2004 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 (2004). 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. 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 | 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. Alarms SHOULD 217 be modelled so Notifications are sent on alarm Clear. 219 The framework defines a generic Alarm MIB that can be supported on 220 its own, or with additional alarm modelling information such as the 221 provided ITU Alarm MIB. In addition, the active alarm tables could 222 also be extended to support additional information about active 223 alarm instances. This framework can also be expanded in the future 224 to support such features as alarm correlation and alarm suppression. 225 This modular architecture means that the cost of supporting alarm 226 management features is proportional to the number of features an 227 implementation supports. 229 3.3.2 Flexible Alarm Modelling 231 Alarm models document an understanding between a manager and an 232 agent as to what problems will be reported on a system, how these 233 problems will be reported, and what might possibly happen over the 234 lifetime of this problem. 236 The alarm modelling method provided in this memo provides 237 flexibility to support implementations with different modelling 238 requirements. All alarms are modelled as a series of states that are 239 related together using an alarm ID. Alarm states can be modelled 240 using traditional Notifications, generic alarm Notifications, or 241 without the use of Notifications. 243 Alarm states modelled using traditional Notifications would specify 244 a Notification Object Identifier, and optionally an (offset, value) 245 pair of one of the Notification varbinds to identify the state. 246 This alarm state would be entered when the entity generated a 247 Notification that matched this information and the alarm would be 248 added to the active alarm table. This Notification would also get 249 sent on the wire to any destinations, as indicated in the 250 SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB [RFC3413]. 252 Alarm states modelled using generic Notifications use the 253 alarmActiveState or alarmClearState Notifications defined in this 254 memo. These alarm states would be entered after being triggered by a 255 stimulus outside the scope of this memo, the alarm would be added to 256 the active alarm table and these generic Notifications would then be 257 sent on the wire to any destinations, as indicated in the 258 SNMP-TARGET-MIB and SNMP-NOTIFICATION-MIB [RFC3413]. 260 Alarm states modelled without any Notifications would be triggered 261 by some stimulus outside the scope of this memo, the alarm would be 262 added to the active alarm table, but no Notifications would be sent 263 to interested managers. 265 3.3.3 Problem Indication 267 The Alarm MIB provides a means to determine whether a given 268 notification is of interest to managers for purposes of alarm 269 management by permitting inspection of the alarm models. If no 270 entries in the alarmModelTable could match a particular 271 notification, then that notification is not relevant to the alarm 272 models defined. In addition, information in the alarm model, such 273 as the Notification ID and the description tell exactly what error 274 or warning condition this alarm is indicating. If the ITU-ALARM-MIB 275 is also supported, additional information is provided via the 276 probable cause. 278 3.3.5 Identifying Resource under Alarm 280 An important goal of alarm management is to ensure that any detected 281 problems get fixed, so it is necessary to know exactly where this 282 problem is occurring. In addition, it is necessary to be able to 283 tell when alarm instances are raised against the same component, as 284 well as to be able to tell what instance of an alarm is cleared by 285 an instance of an alarm clear. 287 The Alarm MIB provides a generic method for identifying the resource 288 by extracting and building a resource ID from the Notification 289 varbinds. It records the relevant information needed to locate the 290 source of the alarm. 292 3.3.6 Means of obtaining ITU alarm information 294 Alarm Information, as defined in ITU alarm models [M.3100], is 295 optionally available to implementations through the optional support 296 of the ITU-ALARM-MIB. 298 3.3.7 Configuration of Alarm Models 300 An alarm model can be added and removed during runtime. It can be 301 modified assuming it is not being referenced by any active alarm 302 instance. 304 3.3.8 Active Alarm Management 306 A list of currently active alarms and supporting statistics on the 307 SNMP entity can be obtained. 309 This allows the network management station to find out about any 310 problems that may have occurred before it started managing a 311 particular network element, or while it was out of contact with it. 313 3.3.9 Distributed Alarm Management 315 All aspects of the Alarm MIB can be supported both on the device 316 experiencing the alarms and on any mid-level managers that might be 317 monitoring such devices. 319 3.3.10 Historical Alarm Management 321 Some systems may have a requirement that information on alarms that 322 are no longer active is available. This memo provides a clear table 323 to support this requirement. 325 This can also be achieved through the support of the Notification 326 Log MIB [RFC3014] to store alarm state transitions. 328 3.4 Security 330 Given the nature of VACM, security for alarms is awkward since 331 access control for the objects in the underlying Notifications can 332 be checked only where the Notification is created. Thus such 333 checking is possible only for locally generated Notifications, and 334 even then only when security credentials are available. 336 For the purpose of this discussion, "security credentials" means the 337 input values for the abstract service interface function 338 isAccessAllowed [RFC3411] and using those credentials means 339 conceptually using that function to see that those credentials allow 340 access to the MIB objects in question, operating as for a 341 Notification Originator in [RFC3413]. 343 The Alarm MIB has the notion of a named alarm list. By using alarm 344 list names and view-based access control [RFC3415] a network 345 administrator can provide different access for different users. When 346 an application creates an alarm model (indexed in part by the alarm 347 list name) the security credentials of the creator remain associated 348 with that alarm model and constrain what information is allowed to 349 be placed in the active alarm table, the active alarm variable 350 table, the cleared alarm table, and the ITU alarm table. 352 When processing locally-generated Notifications, the managed system 353 MUST use the security credentials associated with each alarm model 354 respectively, and MUST apply the same access control rules as 355 described for a Notification Originator in [RFC3413]. 357 The managed system SHOULD NOT apply access control when processing 358 remotely-generated Notifications using the alarm models. In those 359 cases the security of the information in the alarm tables SHOULD be 360 left to the normal, overall access control for those tables. 362 3.5 Relationship between Alarm and Notifications 364 It is important to understand the relationship between alarms and 365 Notifications, as both are traditional fault management methods. 366 This relationship is modelled using the alarmModelTable to define 367 the alarmModelNotificationId for each alarm state. 369 Not all Notifications signal an alarm state transition. Some 370 Notifications are simply informational in nature, such as those that 371 indicate that a configuration operation has been performed on an 372 entity. These sorts of Notifications would not be represented in 373 the Alarm MIB. 375 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) 635 alarmModelResourcePrefix = bgpPeerRemoteAddr 636 (1.3.6.1.2.1.15.3.1.7) 638 4.1.5 Configurable Alarm Models 640 The alarm model table SHOULD be initially populated by the system. 641 The objects in alarmModelTable and ituAlarmTable have a MAX-ACCESS 642 of read-create, which allows managers to modify the alarm models to 643 suit their requirements. 645 4.1.6 Active Alarm Management 647 Lists of alarms currently active on an SNMP entity are stored in the 648 alarmActiveTable and, optionally, a model specific alarmTable, e.g. 649 the ituAlarmActiveTable. 651 4.1.7 Distributed Alarm Management 653 Distributed alarm management can be achieved by support of the Alarm 654 MIB on both the alarm detection point and on the mid-level manager. 655 This is facilitated by the ability to be able to store different 656 named alarm lists. A mid-level manager could create an alarmListName 657 for each of the devices it manages and therefore store separate 658 lists for each device. In addition, the context and IP addresses of 659 the alarm detection point are stored in the alarmActiveTable. 661 4.2 Definitions 663 ALARM-MIB DEFINITIONS ::= BEGIN 665 IMPORTS 666 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 667 Integer32, Unsigned32, Gauge32, 668 TimeTicks, Counter32, Counter64, 669 IpAddress, Opaque, mib-2, 670 zeroDotZero FROM SNMPv2-SMI 671 DateAndTime, 672 RowStatus, RowPointer, 673 TEXTUAL-CONVENTION FROM SNMPv2-TC 674 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 675 InetAddressType, InetAddress FROM INET-ADDRESS-MIB 676 MODULE-COMPLIANCE, OBJECT-GROUP, 677 NOTIFICATION-GROUP FROM SNMPv2-CONF 678 ZeroBasedCounter32 FROM RMON2-MIB; 680 alarmMIB MODULE-IDENTITY 681 LAST-UPDATED "200402090000Z" 682 ORGANIZATION "IETF Distributed Management Working Group" 683 CONTACT-INFO 684 "WG EMail: disman@ietf.org 685 Subscribe: disman-request@ietf.org 686 http://www.ietf.org/html.charters/disman-charter.html 687 Chair: Randy Presuhn 688 randy_presuhn@mindspring.com 690 Editors: Sharon Chisholm 691 Nortel Networks 692 PO Box 3511 Station C 693 Ottawa, Ont. K1Y 4H7 694 Canada 695 schishol@nortelnetworks.com 697 Dan Romascanu 698 Avaya 699 Atidim Technology Park, Bldg. #3 700 Tel Aviv, 61131 701 Israel 702 Tel: +972-3-645-8414 703 Email: dromasca@avaya.com" 704 DESCRIPTION 705 "The MIB module describes a generic solution 706 to model alarms and to store the current list 707 of active alarms. 709 Copyright (C) The Internet Society (2004). The 710 initial version of this MIB module was published 711 in RFC YYYY. For full legal notices see the RFC 712 itself. Supplementary information may be available on: 713 http://www.ietf.org/copyrights/ianamib.html" 714 -- RFC Ed.: replace yyyy with actual RFC number & remove 715 -- this note 716 REVISION "200402090000Z" 717 DESCRIPTION 718 "Initial version, published as RFC yyyy." 719 -- RFC-Editor assigns yyyy 720 ::= { mib-2 XX } -- to be assigned by IANA 722 alarmObjects OBJECT IDENTIFIER ::= { alarmMIB 1 } 724 alarmNotifications OBJECT IDENTIFIER ::= { alarmMIB 0 } 726 alarmModel OBJECT IDENTIFIER ::= { alarmObjects 1 } 728 alarmActive OBJECT IDENTIFIER ::= { alarmObjects 2 } 730 alarmClear OBJECT IDENTIFIER ::= { alarmObjects 3 } 732 -- Textual Conventions 734 -- ResourceId is intended to be a general textual convention 735 -- that can be used outside of the set of MIBs related to 736 -- Alarm Management. 738 ResourceId ::= TEXTUAL-CONVENTION 739 STATUS current 740 DESCRIPTION 741 "A unique identifier for this resource. 743 The type of the resource can be determined by looking 744 at the OID that describes the resource. 746 Resources must be identified in a consistent manner. 747 For example, if this resource is an interface, this 748 object MUST point to an ifIndex and if this resource 749 is a physical entity, then this MUST point to an 750 entPhysicalDescr, given that entPhysicalIndex is not 751 accessible. In general, the value is the 752 name of the instance of the first accessible columnar 753 object in the conceptual row of a table that is 754 meaningful for this resource type, which SHOULD 755 be defined in an IETF standard MIB." 756 SYNTAX OBJECT IDENTIFIER 758 -- LocalSnmpEngineOrZeroLenStr is intended to be a general 759 -- textual convention that can be used outside of the set of 760 -- MIBs related to Alarm Management. 762 LocalSnmpEngineOrZeroLenStr ::= TEXTUAL-CONVENTION 763 STATUS current 764 DESCRIPTION 765 "An SNMP Engine ID or a zero-length string. The 766 instantiation of this textual convention will provide 767 guidance on when this will be an SNMP Engine ID and 768 when it will be a zero lengths string" 769 SYNTAX OCTET STRING (SIZE(0 | 5..32)) 771 -- Alarm Model 773 alarmModelLastChanged OBJECT-TYPE 774 SYNTAX TimeTicks 775 MAX-ACCESS read-only 776 STATUS current 777 DESCRIPTION 778 "The value of sysUpTime at the time of the last 779 creation, deletion or modification of an entry in 780 the alarmModelTable. 782 If the number and content of entries has been unchanged 783 since the last re-initialization of the local network 784 management subsystem, then the value of this object 785 MUST be zero." 786 ::= { alarmModel 1 } 788 alarmModelTable OBJECT-TYPE 789 SYNTAX SEQUENCE OF AlarmModelEntry 790 MAX-ACCESS not-accessible 791 STATUS current 792 DESCRIPTION 793 "A table of information about possible alarms on the system, 794 and how they have been modelled." 795 ::= { alarmModel 2 } 797 alarmModelEntry OBJECT-TYPE 798 SYNTAX AlarmModelEntry 799 MAX-ACCESS not-accessible 800 STATUS current 801 DESCRIPTION 802 "Entries appear in this table for each possible alarm state. 803 This table MUST be persistent across system reboots." 804 INDEX { alarmListName, alarmModelIndex, alarmModelState } 805 ::= { alarmModelTable 1 } 807 AlarmModelEntry ::= SEQUENCE { 808 alarmModelIndex Unsigned32, 809 alarmModelState Unsigned32, 810 alarmModelNotificationId OBJECT IDENTIFIER, 811 alarmModelVarbindIndex Unsigned32, 812 alarmModelVarbindValue Integer32, 813 alarmModelDescription SnmpAdminString, 814 alarmModelSpecificPointer RowPointer, 815 alarmModelVarbindSubtree OBJECT IDENTIFIER, 816 alarmModelResourcePrefix OBJECT IDENTIFIER, 817 alarmModelRowStatus RowStatus 818 } 820 alarmModelIndex OBJECT-TYPE 821 SYNTAX Unsigned32 (1..4294967295) 822 MAX-ACCESS not-accessible 823 STATUS current 824 DESCRIPTION 825 "An integer that acts as an alarm Id 826 to uniquely identify each alarm 827 within the named alarm list. " 828 ::= { alarmModelEntry 1 } 830 alarmModelState OBJECT-TYPE 831 SYNTAX Unsigned32 (1..4294967295) 832 MAX-ACCESS not-accessible 833 STATUS current 834 DESCRIPTION 835 "A value of 1 MUST indicate a clear alarm state. 836 The value of this object MUST be less than the 837 alarmModelState of more severe alarm states for 838 this alarm. The value of this object MUST be more 839 than the alarmModelState of less severe alarm states 840 for this alarm." 841 ::= { alarmModelEntry 2 } 843 alarmModelNotificationId OBJECT-TYPE 844 SYNTAX OBJECT IDENTIFIER 845 MAX-ACCESS read-create 846 STATUS current 847 DESCRIPTION 848 "The NOTIFICATION-TYPE object identifier of this alarm 849 state transition. If there is no notification associated 850 with this alarm state, the value of this object MUST be 851 '0.0'" 852 DEFVAL { zeroDotZero } 853 ::= { alarmModelEntry 3 } 855 alarmModelVarbindIndex OBJECT-TYPE 856 SYNTAX Unsigned32 857 MAX-ACCESS read-create 858 STATUS current 859 DESCRIPTION 860 "The index into the varbind listing of the notification 861 indicated by alarmModelNotificationId which helps 862 signal that the given alarm has changed state. 863 If there is no applicable varbind, the value of this 864 object MUST be zero. 866 Note that the value of alarmModelVarbindIndex acknowledges 867 the existence of the first two obligatory varbinds in 868 the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0 869 and snmpTrapOID.0). That is, a value of 2 refers to 870 the snmpTrapOID.0. 872 If the incoming notification is instead an SNMPv1 Trap-PDU, 873 then an appropriate value for sysUpTime.0 or snmpTrapOID.0 874 shall be determined by using the rules in section 3.1 of 875 [RFC3584]" 876 DEFVAL { 0 } 877 ::= { alarmModelEntry 4 } 879 alarmModelVarbindValue OBJECT-TYPE 880 SYNTAX Integer32 881 MAX-ACCESS read-create 882 STATUS current 883 DESCRIPTION 884 "The value that the varbind indicated by 885 alarmModelVarbindIndex takes to indicate 886 that the alarm has entered this state. 888 If alarmModelVarbindIndex has a value of 0, so 889 MUST alarmModelVarbindIndex. 890 " 891 DEFVAL { 0 } 893 ::= { alarmModelEntry 5 } 895 alarmModelDescription OBJECT-TYPE 896 SYNTAX SnmpAdminString 897 MAX-ACCESS read-create 898 STATUS current 899 DESCRIPTION 900 "A brief description of this alarm and state suitable 901 to display to operators." 902 DEFVAL { "" } 903 ::= { alarmModelEntry 6 } 905 alarmModelSpecificPointer OBJECT-TYPE 906 SYNTAX RowPointer 907 MAX-ACCESS read-create 908 STATUS current 909 DESCRIPTION 910 "If no additional, model-specific Alarm MIB is supported by 911 the system the value of this object is `0.0'and attempts 912 to set it to any other value MUST be rejected appropriately. 914 When a model-specific Alarm MIB is supported, this object 915 MUST refer to the first accessible object in a corresponding 916 row of the model definition in one of these model-specific 917 MIB and attempts to set this object to { 0 0 } or any other 918 value MUST be rejected appropriately." 919 DEFVAL { zeroDotZero } 920 ::= { alarmModelEntry 7 } 922 alarmModelVarbindSubtree OBJECT-TYPE 923 SYNTAX OBJECT IDENTIFIER 924 MAX-ACCESS read-create 925 STATUS current 926 DESCRIPTION 927 "The name portion of each VarBind in the notification, 928 in order, is compared to the value of this object. 929 If the name is equal to or a subtree of the value 930 of this object, for purposes of computing the value 931 of AlarmActiveResourceID the 'prefix' will be the 932 matching portion, and the 'indexes' will be any 933 remainder. The examination of varbinds ends with 934 the first match. If the value of this object is 0.0, 935 then the first varbind, or in the case of v2, the 936 first varbind after the timestamp and the trap 937 OID, will always be matched. 938 " 939 DEFVAL { zeroDotZero } 940 ::= { alarmModelEntry 8 } 942 alarmModelResourcePrefix OBJECT-TYPE 943 SYNTAX OBJECT IDENTIFIER 944 MAX-ACCESS read-create 945 STATUS current 946 DESCRIPTION 947 "The value of AlarmActiveResourceID is computed 948 by appending any indexes extracted in accordance 949 with the description of alarmModelVarbindSubtree 950 onto the value of this object. If this object's 951 value is 0.0, then the 'prefix' extracted is used 952 instead. 953 " 954 DEFVAL { zeroDotZero } 955 ::= { alarmModelEntry 9 } 957 alarmModelRowStatus OBJECT-TYPE 958 SYNTAX RowStatus 959 MAX-ACCESS read-create 960 STATUS current 961 DESCRIPTION 962 "Control for creating and deleting entries. Entries may be 963 modified while active. Alarms whose alarmModelRowStatus is 964 not active will not appear in either the alarmActiveTable 965 or the alarmClearTable. Setting this object to notInService 966 cannot be used as an alarm suppression mechanism. Entries 967 that are notInService will disappear as described in RFC2579. 969 This row can not be modified while it is being 970 referenced by a value of alarmActiveModelPointer. In these 971 cases, an error of `inconsistentValue' will be returned to 972 the manager. 974 This entry may be deleted while it is being 975 referenced by a value of alarmActiveModelPointer. This results 976 in the deletion of this entry and entries in the active alarms 977 referencing this entry via an alarmActiveModelPointer. 979 As all read-create objects in this table have a DEFVAL clause, 980 there is no requirement that any object be explicitly set 981 before this row can become active. Note that a row consisting 982 only of default values is not very meaningful." 983 ::= { alarmModelEntry 10 } 985 -- Active Alarm Table -- 987 alarmActiveLastChanged OBJECT-TYPE 988 SYNTAX TimeTicks 989 MAX-ACCESS read-only 990 STATUS current 991 DESCRIPTION 992 "The value of sysUpTime at the time of the last 993 creation or deletion of an entry in the alarmActiveTable. 995 If the number of entries has been unchanged since the 996 last re-initialization of the local network management 997 subsystem, then this object contains a zero value." 998 ::= { alarmActive 1 } 1000 alarmActiveOverflow OBJECT-TYPE 1001 SYNTAX Counter32 1002 UNITS "active alarms" 1003 MAX-ACCESS read-only 1004 STATUS current 1005 DESCRIPTION 1006 "The number of active alarms that have not been put into 1007 the alarmActiveTable since system restart as a result 1008 of extreme resource constraints." 1009 ::= { alarmActive 5 } 1011 alarmActiveTable OBJECT-TYPE 1012 SYNTAX SEQUENCE OF AlarmActiveEntry 1013 MAX-ACCESS not-accessible 1014 STATUS current 1015 DESCRIPTION 1016 "A table of Active Alarms entries." 1017 ::= { alarmActive 2 } 1019 alarmActiveEntry OBJECT-TYPE 1020 SYNTAX AlarmActiveEntry 1021 MAX-ACCESS not-accessible 1022 STATUS current 1023 DESCRIPTION 1024 "Entries appear in this table when alarms are raised. They 1025 are removed when the alarm is cleared. 1027 If under extreme resource constraint the system is unable to 1028 add any more entries into this table, then the 1029 alarmActiveOverflow statistic will be increased by one." 1030 INDEX { alarmListName, alarmActiveDateAndTime, 1031 alarmActiveIndex } 1032 ::= { alarmActiveTable 1 } 1034 AlarmActiveEntry ::= SEQUENCE { 1035 alarmListName SnmpAdminString, 1036 alarmActiveDateAndTime DateAndTime, 1037 alarmActiveIndex Unsigned32, 1038 alarmActiveEngineID LocalSnmpEngineOrZeroLenStr, 1039 alarmActiveEngineAddressType InetAddressType, 1040 alarmActiveEngineAddress InetAddress, 1041 alarmActiveContextName SnmpAdminString, 1042 alarmActiveVariables Unsigned32, 1043 alarmActiveNotificationID OBJECT IDENTIFIER, 1044 alarmActiveResourceId ResourceId, 1045 alarmActiveDescription SnmpAdminString, 1046 alarmActiveLogPointer RowPointer, 1047 alarmActiveModelPointer RowPointer, 1048 alarmActiveSpecificPointer RowPointer } 1050 alarmListName OBJECT-TYPE 1051 SYNTAX SnmpAdminString (SIZE(0..32)) 1052 MAX-ACCESS not-accessible 1053 STATUS current 1054 DESCRIPTION 1055 "The name of the list of alarms. This SHOULD be the same as 1056 nlmLogName if the Notification Log MIB [RFC3014] is supported. 1057 This SHOULD be the same as, or contain as a prefix, the 1058 applicable snmpNotifyFilterProfileName if the 1059 SNMP-NOTIFICATION-MIB DEFINITIONS [RFC3413] is supported. 1061 An implementation may allow multiple named alarm lists, up to 1062 some implementation-specific limit (which may be none). A 1063 zero-length list name is reserved for creation and deletion 1064 by the managed system, and MUST be used as the default log 1065 name by systems that do not support named alarm lists." 1066 ::= { alarmActiveEntry 1 } 1068 alarmActiveDateAndTime OBJECT-TYPE 1069 SYNTAX DateAndTime 1070 MAX-ACCESS not-accessible 1071 STATUS current 1072 DESCRIPTION 1073 "The local date and time when the error occurred. 1075 This object facilitates retrieving all instances of 1076 alarms that have been raised or have changed state 1077 since a given point in time. 1079 Implementations MUST include the offset from UTC, 1080 if available. Implementation in environments in which 1081 the UTC offset is not available is NOT RECOMMENDED." 1082 ::= { alarmActiveEntry 2 } 1084 alarmActiveIndex OBJECT-TYPE 1085 SYNTAX Unsigned32 (1..4294967295) 1086 MAX-ACCESS not-accessible 1087 STATUS current 1088 DESCRIPTION 1089 "A strictly monotonically increasing integer which 1090 acts as the index of entries within the named alarm 1091 list. It wraps back to 1 after it reaches its 1092 maximum value." 1093 ::= { alarmActiveEntry 3 } 1095 alarmActiveEngineID OBJECT-TYPE 1096 SYNTAX LocalSnmpEngineOrZeroLenStr 1097 MAX-ACCESS read-only 1098 STATUS current 1099 DESCRIPTION 1100 "The identification of the SNMP engine at which the alarm 1101 originated. If the alarm is from an SNMPv1 system this 1102 object is a zero length string." 1103 ::= { alarmActiveEntry 4 } 1105 alarmActiveEngineAddressType OBJECT-TYPE 1106 SYNTAX InetAddressType 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION 1110 "This object indicates what type of address is stored in 1111 the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc." 1112 ::= { alarmActiveEntry 5 } 1114 alarmActiveEngineAddress OBJECT-TYPE 1115 SYNTAX InetAddress 1116 MAX-ACCESS read-only 1117 STATUS current 1118 DESCRIPTION 1119 "The address of the SNMP engine on which the alarm is 1120 occurring. 1122 This object MUST always be instantiated, even if the list 1123 can contain alarms from only one engine." 1124 ::= { alarmActiveEntry 6 } 1126 alarmActiveContextName OBJECT-TYPE 1127 SYNTAX SnmpAdminString (SIZE(0..32)) 1128 MAX-ACCESS read-only 1129 STATUS current 1130 DESCRIPTION 1131 "The name of the SNMP MIB context from which the alarm came. 1132 For SNMPv1 alarms this is the community string from the Trap. 1133 Note that care MUST be taken when selecting community 1134 strings to ensure that these can be represented as a 1135 well-formed SnmpAdminString. Community or Context names 1136 that are not well-formed SnmpAdminStrings will be mapped 1137 to zero length strings. 1139 If the alarm's source SNMP engine is known not to support 1140 multiple contexts, this object is a zero length string." 1141 ::= { alarmActiveEntry 7 } 1143 alarmActiveVariables OBJECT-TYPE 1144 SYNTAX Unsigned32 1145 MAX-ACCESS read-only 1146 STATUS current 1147 DESCRIPTION 1148 "The number of variables in alarmActiveVariableTable for this 1149 alarm." 1151 ::= { alarmActiveEntry 8 } 1153 alarmActiveNotificationID OBJECT-TYPE 1154 SYNTAX OBJECT IDENTIFIER 1155 MAX-ACCESS read-only 1156 STATUS current 1157 DESCRIPTION 1158 "The NOTIFICATION-TYPE object identifier of the alarm 1159 state transition that is occurring." 1160 ::= { alarmActiveEntry 9 } 1162 alarmActiveResourceId OBJECT-TYPE 1163 SYNTAX ResourceId 1164 MAX-ACCESS read-only 1165 STATUS current 1166 DESCRIPTION 1167 "This object identifies the resource under alarm. 1169 If there is no corresponding resource, then 1170 the value of this object MUST be 0.0." 1171 ::= { alarmActiveEntry 10 } 1173 alarmActiveDescription OBJECT-TYPE 1174 SYNTAX SnmpAdminString 1175 MAX-ACCESS read-only 1176 STATUS current 1177 DESCRIPTION 1178 "This object provides a textual description of the 1179 active alarm. This text is generated dynamically by the 1180 notification generator to provide useful information 1181 to the human operator. This information SHOULD 1182 provide information allowing the operator to locate 1183 the resource for which this alarm is being generated. 1184 This information is not intended for consumption by 1185 automated tools." 1186 ::= { alarmActiveEntry 11 } 1188 alarmActiveLogPointer OBJECT-TYPE 1189 SYNTAX RowPointer 1190 MAX-ACCESS read-only 1191 STATUS current 1192 DESCRIPTION 1193 "A pointer to the corresponding row in a 1194 notification logging MIB where the state change 1195 notification for this active alarm is logged. 1196 If no log entry applies to this active alarm, 1197 then this object MUST have the value of 0.0" 1198 ::= { alarmActiveEntry 12 } 1200 alarmActiveModelPointer OBJECT-TYPE 1201 SYNTAX RowPointer 1202 MAX-ACCESS read-only 1203 STATUS current 1204 DESCRIPTION 1205 "A pointer to the corresponding row in the 1206 alarmModelTable for this active alarm. This 1207 points not only to the alarm model being 1208 instantiated, but also to the specific alarm 1209 state that is active." 1210 ::= { alarmActiveEntry 13 } 1212 alarmActiveSpecificPointer OBJECT-TYPE 1213 SYNTAX RowPointer 1214 MAX-ACCESS read-only 1215 STATUS current 1216 DESCRIPTION 1217 "If no additional, model-specific, Alarm MIB is supported by 1218 the system this object is `0.0'. When a model-specific Alarm 1219 MIB is supported, this object is the instance pointer to the 1220 specific model-specific active alarm list." 1221 ::= { alarmActiveEntry 14 } 1223 -- Active Alarm Variable Table -- 1225 alarmActiveVariableTable OBJECT-TYPE 1226 SYNTAX SEQUENCE OF AlarmActiveVariableEntry 1227 MAX-ACCESS not-accessible 1228 STATUS current 1229 DESCRIPTION 1230 "A table of variables to go with active alarm entries." 1231 ::= { alarmActive 3 } 1233 alarmActiveVariableEntry OBJECT-TYPE 1234 SYNTAX AlarmActiveVariableEntry 1235 MAX-ACCESS not-accessible 1236 STATUS current 1237 DESCRIPTION 1238 "Entries appear in this table when there are variables in 1239 the varbind list of a corresponding alarm in 1240 alarmActiveTable. 1242 Entries appear in this table as though 1243 the trap/notification had been transported using a 1244 SNMPv2-Trap-PDU, as defined in [RFC3416] - i.e, the 1245 alarmActiveVariableIndex 1 will always be sysUpTime 1246 and alarmActiveVariableIndex 2 will always be 1247 snmpTrapOID. 1249 If the incoming notification is instead an SNMPv1 Trap-PDU and 1250 the value of alarmModelVarbindIndex is 1 or 2, an appropriate 1251 value for sysUpTime.0 or snmpTrapOID.0 shall be determined 1252 by using the rules in section 3.1 of [RFC3584]." 1253 INDEX { alarmListName, alarmActiveIndex, 1254 alarmActiveVariableIndex } 1255 ::= { alarmActiveVariableTable 1 } 1257 AlarmActiveVariableEntry ::= SEQUENCE { 1258 alarmActiveVariableIndex Unsigned32, 1259 alarmActiveVariableID OBJECT IDENTIFIER, 1260 alarmActiveVariableValueType INTEGER, 1261 alarmActiveVariableCounter32Val Counter32, 1262 alarmActiveVariableUnsigned32Val Unsigned32, 1263 alarmActiveVariableTimeTicksVal TimeTicks, 1264 alarmActiveVariableInteger32Val Integer32, 1265 alarmActiveVariableOctetStringVal OCTET STRING, 1266 alarmActiveVariableIpAddressVal IpAddress, 1267 alarmActiveVariableOidVal OBJECT IDENTIFIER, 1268 alarmActiveVariableCounter64Val Counter64, 1269 alarmActiveVariableOpaqueVal Opaque } 1271 alarmActiveVariableIndex OBJECT-TYPE 1272 SYNTAX Unsigned32 (1..4294967295) 1273 MAX-ACCESS not-accessible 1274 STATUS current 1275 DESCRIPTION 1276 "A strictly monotonically increasing integer, starting at 1277 1 for a given alarmActiveIndex, for indexing variables 1278 within the active alarm variable list. " 1279 ::= { alarmActiveVariableEntry 1 } 1281 alarmActiveVariableID OBJECT-TYPE 1282 SYNTAX OBJECT IDENTIFIER 1283 MAX-ACCESS read-only 1284 STATUS current 1285 DESCRIPTION 1286 "The alarm variable's object identifier." 1287 ::= { alarmActiveVariableEntry 2 } 1289 alarmActiveVariableValueType OBJECT-TYPE 1290 SYNTAX INTEGER { 1291 counter32(1), 1292 unsigned32(2), 1293 timeTicks(3), 1294 integer32(4), 1295 ipAddress(5), 1296 octetString(6), 1297 objectId(7), 1298 counter64(8), 1299 opaque(9) 1300 } 1301 MAX-ACCESS read-only 1302 STATUS current 1303 DESCRIPTION 1304 "The type of the value. One and only one of the value 1305 objects that follow is used for a given row in this table, 1306 based on this type." 1307 ::= { alarmActiveVariableEntry 3 } 1309 alarmActiveVariableCounter32Val OBJECT-TYPE 1310 SYNTAX Counter32 1311 MAX-ACCESS read-only 1312 STATUS current 1313 DESCRIPTION 1314 "The value when alarmActiveVariableType is 'counter32'." 1315 ::= { alarmActiveVariableEntry 4 } 1317 alarmActiveVariableUnsigned32Val OBJECT-TYPE 1318 SYNTAX Unsigned32 1319 MAX-ACCESS read-only 1320 STATUS current 1321 DESCRIPTION 1322 "The value when alarmActiveVariableType is 'unsigned32'." 1323 ::= { alarmActiveVariableEntry 5 } 1325 alarmActiveVariableTimeTicksVal OBJECT-TYPE 1326 SYNTAX TimeTicks 1327 MAX-ACCESS read-only 1328 STATUS current 1329 DESCRIPTION 1330 "The value when alarmActiveVariableType is 'timeTicks'." 1331 ::= { alarmActiveVariableEntry 6 } 1333 alarmActiveVariableInteger32Val OBJECT-TYPE 1334 SYNTAX Integer32 1335 MAX-ACCESS read-only 1336 STATUS current 1337 DESCRIPTION 1338 "The value when alarmActiveVariableType is 'integer32'." 1339 ::= { alarmActiveVariableEntry 7 } 1341 alarmActiveVariableOctetStringVal OBJECT-TYPE 1342 SYNTAX OCTET STRING (SIZE(0..65535)) 1343 MAX-ACCESS read-only 1344 STATUS current 1345 DESCRIPTION 1346 "The value when alarmActiveVariableType is 'octetString'." 1347 ::= { alarmActiveVariableEntry 8 } 1349 alarmActiveVariableIpAddressVal OBJECT-TYPE 1350 SYNTAX IpAddress 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The value when alarmActiveVariableType is 'ipAddress'." 1355 ::= { alarmActiveVariableEntry 9 } 1357 alarmActiveVariableOidVal OBJECT-TYPE 1358 SYNTAX OBJECT IDENTIFIER 1359 MAX-ACCESS read-only 1360 STATUS current 1361 DESCRIPTION 1362 "The value when alarmActiveVariableType is 'objectId'." 1363 ::= { alarmActiveVariableEntry 10 } 1365 alarmActiveVariableCounter64Val OBJECT-TYPE 1366 SYNTAX Counter64 1367 MAX-ACCESS read-only 1368 STATUS current 1369 DESCRIPTION 1370 "The value when alarmActiveVariableType is 'counter64'." 1371 ::= { alarmActiveVariableEntry 11 } 1373 alarmActiveVariableOpaqueVal OBJECT-TYPE 1374 SYNTAX Opaque (SIZE(0..65535)) 1375 MAX-ACCESS read-only 1376 STATUS current 1377 DESCRIPTION 1378 "The value when alarmActiveVariableType is 'opaque'. 1380 Note that although RFC2578 [RFC2578] forbids the use 1381 of Opaque in 'standard' MIB modules, this particular 1382 usage is driven by the need to be able to accurately 1383 represent any well-formed notification, and justified 1384 by the need for backward compatibility." 1385 ::= { alarmActiveVariableEntry 12 } 1387 -- Statistics -- 1389 alarmActiveStatsTable OBJECT-TYPE 1390 SYNTAX SEQUENCE OF AlarmActiveStatsEntry 1391 MAX-ACCESS not-accessible 1392 STATUS current 1393 DESCRIPTION 1394 "This table represents the alarm statistics 1395 information." 1396 ::= { alarmActive 4 } 1398 alarmActiveStatsEntry OBJECT-TYPE 1399 SYNTAX AlarmActiveStatsEntry 1400 MAX-ACCESS not-accessible 1401 STATUS current 1402 DESCRIPTION 1403 "Statistics on the current active alarms." 1404 INDEX { alarmListName } 1406 ::= { alarmActiveStatsTable 1 } 1408 AlarmActiveStatsEntry ::= 1409 SEQUENCE { 1410 alarmActiveStatsActiveCurrent Gauge32, 1411 alarmActiveStatsActives ZeroBasedCounter32, 1412 alarmActiveStatsLastRaise TimeTicks, 1413 alarmActiveStatsLastClear TimeTicks 1414 } 1416 alarmActiveStatsActiveCurrent OBJECT-TYPE 1417 SYNTAX Gauge32 1418 MAX-ACCESS read-only 1419 STATUS current 1420 DESCRIPTION 1421 "The total number of currently active alarms on the system." 1423 ::= { alarmActiveStatsEntry 1 } 1425 alarmActiveStatsActives OBJECT-TYPE 1426 SYNTAX ZeroBasedCounter32 1427 MAX-ACCESS read-only 1428 STATUS current 1429 DESCRIPTION 1430 "The total number of active alarms since system restarted." 1432 ::= { alarmActiveStatsEntry 2 } 1434 alarmActiveStatsLastRaise OBJECT-TYPE 1435 SYNTAX TimeTicks 1436 MAX-ACCESS read-only 1437 STATUS current 1438 DESCRIPTION 1439 "The value of sysUpTime at the time of the last 1440 alarm raise for this alarm list. 1441 If no alarm raises have occurred since the 1442 last re-initialization of the local network management 1443 subsystem, then this object contains a zero value." 1444 ::= { alarmActiveStatsEntry 3 } 1446 alarmActiveStatsLastClear OBJECT-TYPE 1447 SYNTAX TimeTicks 1448 MAX-ACCESS read-only 1449 STATUS current 1450 DESCRIPTION 1451 "The value of sysUpTime at the time of the last 1452 alarm clear for this alarm list. 1453 If no alarm clears have occurred since the 1454 last re-initialization of the local network management 1455 subsystem, then this object contains a zero value." 1457 ::= { alarmActiveStatsEntry 4 } 1459 -- Alarm Clear 1461 alarmClearMaximum OBJECT-TYPE 1462 SYNTAX Unsigned32 1463 MAX-ACCESS read-write 1464 STATUS current 1465 DESCRIPTION 1466 "This object specifies the maximum number of cleared 1467 alarms to store in the alarmClearTable. When this 1468 number is reached, the cleared alarms with the 1469 earliest clear time will be removed from the table." 1470 ::= { alarmClear 1 } 1472 alarmClearTable OBJECT-TYPE 1473 SYNTAX SEQUENCE OF AlarmClearEntry 1474 MAX-ACCESS not-accessible 1475 STATUS current 1476 DESCRIPTION 1477 "This table contains information on 1478 cleared alarms." 1479 ::= { alarmClear 2 } 1481 alarmClearEntry OBJECT-TYPE 1482 SYNTAX AlarmClearEntry 1483 MAX-ACCESS not-accessible 1484 STATUS current 1485 DESCRIPTION 1486 "Information on a cleared alarm." 1487 INDEX { alarmListName, alarmClearDateAndTime, 1488 alarmClearIndex } 1490 ::= { alarmClearTable 1 } 1492 AlarmClearEntry ::= 1493 SEQUENCE { 1494 alarmClearIndex Unsigned32, 1495 alarmClearDateAndTime DateAndTime, 1496 alarmClearEngineID LocalSnmpEngineOrZeroLenStr, 1497 alarmClearEngineAddressType InetAddressType, 1498 alarmClearEngineAddress InetAddress, 1499 alarmClearContextName SnmpAdminString, 1500 alarmClearNotificationID OBJECT IDENTIFIER, 1501 alarmClearResourceId ResourceId, 1502 alarmClearLogIndex Unsigned32, 1503 alarmClearModelPointer RowPointer 1504 } 1506 alarmClearIndex OBJECT-TYPE 1507 SYNTAX Unsigned32 (1..4294967295) 1508 MAX-ACCESS not-accessible 1509 STATUS current 1510 DESCRIPTION 1511 "An integer which acts as the index of entries within 1512 the named alarm list. It wraps back to 1 after it 1513 reaches its maximum value. 1515 This object has the same value as the alarmActiveIndex that 1516 this alarm instance had when it was active." 1517 ::= { alarmClearEntry 1 } 1519 alarmClearDateAndTime OBJECT-TYPE 1520 SYNTAX DateAndTime 1521 MAX-ACCESS not-accessible 1522 STATUS current 1523 DESCRIPTION 1524 "The local date and time when the alarm cleared. 1526 This object facilitates retrieving all instances of 1527 alarms that have been cleared since a given point in time. 1529 Implementations MUST include the offset from UTC, 1530 if available. Implementation in environments in which 1531 the UTC offset is not available is NOT RECOMMENDED." 1532 ::= { alarmClearEntry 2 } 1534 alarmClearEngineID OBJECT-TYPE 1535 SYNTAX LocalSnmpEngineOrZeroLenStr 1536 MAX-ACCESS read-only 1537 STATUS current 1538 DESCRIPTION 1539 "The identification of the SNMP engine at which the alarm 1540 originated. If the alarm is from an SNMPv1 system this 1541 object is a zero length string." 1542 ::= { alarmClearEntry 3 } 1544 alarmClearEngineAddressType OBJECT-TYPE 1545 SYNTAX InetAddressType 1546 MAX-ACCESS read-only 1547 STATUS current 1548 DESCRIPTION 1549 "This object indicates what type of address is stored in 1550 the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc." 1551 ::= { alarmClearEntry 4 } 1553 alarmClearEngineAddress OBJECT-TYPE 1554 SYNTAX InetAddress 1555 MAX-ACCESS read-only 1556 STATUS current 1557 DESCRIPTION 1558 "The Address of the SNMP engine on which the alarm was 1559 occurring. This is used to identify the source of an SNMPv1 1560 trap, since an alarmActiveEngineId cannot be extracted from the 1561 SNMPv1 trap PDU. 1563 This object MUST always be instantiated, even if the list 1564 can contain alarms from only one engine." 1565 ::= { alarmClearEntry 5 } 1567 alarmClearContextName OBJECT-TYPE 1568 SYNTAX SnmpAdminString (SIZE(0..32)) 1569 MAX-ACCESS read-only 1570 STATUS current 1571 DESCRIPTION 1572 "The name of the SNMP MIB context from which the alarm came. 1573 For SNMPv1 traps this is the community string from the Trap. 1574 Note that care needs to be taken when selecting community 1575 strings to ensure that these can be represented as a 1576 well-formed SnmpAdminString. Community or Context names 1577 that are not well-formed SnmpAdminStrings will be mapped 1578 to zero length strings. 1580 If the alarm's source SNMP engine is known not to support 1581 multiple contexts, this object is a zero length string." 1582 ::= { alarmClearEntry 6 } 1584 alarmClearNotificationID OBJECT-TYPE 1585 SYNTAX OBJECT IDENTIFIER 1586 MAX-ACCESS read-only 1587 STATUS current 1588 DESCRIPTION 1589 "The NOTIFICATION-TYPE object identifier of the alarm 1590 clear." 1591 ::= { alarmClearEntry 7 } 1593 alarmClearResourceId OBJECT-TYPE 1594 SYNTAX ResourceId 1595 MAX-ACCESS read-only 1596 STATUS current 1597 DESCRIPTION 1598 "This object identifies the resource that was under alarm. 1600 If there is no corresponding resource, then 1601 the value of this object MUST be 0.0." 1602 ::= { alarmClearEntry 8 } 1604 alarmClearLogIndex OBJECT-TYPE 1605 SYNTAX Unsigned32 (0..4294967295) 1606 MAX-ACCESS read-only 1607 STATUS current 1608 DESCRIPTION 1609 "This number MUST be the same as the log index of the 1610 applicable row in the notification log MIB, if it exists. 1611 If no log index applies to the trap, then this object 1612 MUST have the value of 0." 1613 ::= { alarmClearEntry 9 } 1615 alarmClearModelPointer OBJECT-TYPE 1616 SYNTAX RowPointer 1617 MAX-ACCESS read-only 1618 STATUS current 1619 DESCRIPTION 1620 "A pointer to the corresponding row in the 1621 alarmModelTable for this cleared alarm." 1622 ::= { alarmClearEntry 10 } 1624 -- Notifications 1626 alarmActiveState NOTIFICATION-TYPE 1627 OBJECTS { alarmActiveModelPointer, 1628 alarmActiveResourceId } 1629 STATUS current 1630 DESCRIPTION 1631 "An instance of the alarm indicated by 1632 alarmActiveModelPointer has been raised 1633 against the entity indicated by 1634 alarmActiveResourceId. 1636 The agent must throttle the generation of 1637 consecutive alarmActiveState traps so that there is at 1638 least a two-second gap between traps of this 1639 type against the same alarmActiveModelPointer and 1640 alarmActiveResourceId. When traps are throttled, 1641 they are dropped, not queued for sending at a future time. 1643 A management application should periodically check 1644 the value of alarmActiveLastChanged to detect any 1645 missed alarmActiveState notification-events, e.g., 1646 due to throttling or transmission loss." 1647 ::= { alarmNotifications 2 } 1649 alarmClearState NOTIFICATION-TYPE 1650 OBJECTS { alarmActiveModelPointer, 1651 alarmActiveResourceId } 1652 STATUS current 1653 DESCRIPTION 1654 "An instance of the alarm indicated by 1655 alarmActiveModelPointer has been cleared against 1656 the entity indicated by alarmActiveResourceId. 1658 The agent must throttle the generation of 1659 consecutive alarmActiveClear traps so that there is at 1660 least a two-second gap between traps of this 1661 type against the same alarmActiveModelPointer and 1662 alarmActiveResourceId. When traps are throttled, 1663 they are dropped, not queued for sending at a future time. 1665 A management application should periodically check 1666 the value of alarmActiveLastChanged to detect any 1667 missed alarmClearState notification-events, e.g., 1668 due to throttling or transmission loss." 1669 ::= { alarmNotifications 3 } 1671 -- Conformance 1673 alarmConformance OBJECT IDENTIFIER ::= { alarmMIB 2 } 1675 alarmCompliances OBJECT IDENTIFIER ::= { alarmConformance 1 } 1677 alarmCompliance MODULE-COMPLIANCE 1678 STATUS current 1679 DESCRIPTION 1680 "The compliance statement for systems supporting 1681 the Alarm MIB." 1682 MODULE -- this module 1683 MANDATORY-GROUPS { 1684 alarmActiveGroup, 1685 alarmModelGroup 1686 } 1687 GROUP alarmActiveStatsGroup 1688 DESCRIPTION 1689 "This group is optional." 1690 GROUP alarmClearGroup 1691 DESCRIPTION 1692 "This group is optional." 1693 GROUP alarmNotificationsGroup 1694 DESCRIPTION 1695 "This group is optional." 1696 ::= { alarmCompliances 1 } 1698 alarmGroups OBJECT IDENTIFIER ::= { alarmConformance 2 } 1700 alarmModelGroup OBJECT-GROUP 1701 OBJECTS { 1702 alarmModelLastChanged, 1703 alarmModelNotificationId, 1704 alarmModelVarbindIndex, 1705 alarmModelVarbindValue, 1706 alarmModelDescription, 1707 alarmModelSpecificPointer, 1708 alarmModelVarbindSubtree, 1709 alarmModelResourcePrefix, 1710 alarmModelRowStatus 1711 } 1712 STATUS current 1713 DESCRIPTION 1714 "Alarm model group." 1715 ::= { alarmGroups 1} 1717 alarmActiveGroup OBJECT-GROUP 1718 OBJECTS { 1719 alarmActiveLastChanged, 1720 alarmActiveOverflow, 1721 alarmActiveEngineID, 1722 alarmActiveEngineAddressType, 1723 alarmActiveEngineAddress, 1724 alarmActiveContextName, 1725 alarmActiveVariables, 1726 alarmActiveNotificationID, 1727 alarmActiveResourceId, 1728 alarmActiveDescription, 1729 alarmActiveLogPointer, 1730 alarmActiveModelPointer, 1731 alarmActiveSpecificPointer, 1732 alarmActiveVariableID, 1733 alarmActiveVariableValueType, 1734 alarmActiveVariableCounter32Val, 1735 alarmActiveVariableUnsigned32Val, 1736 alarmActiveVariableTimeTicksVal, 1737 alarmActiveVariableInteger32Val, 1738 alarmActiveVariableOctetStringVal, 1739 alarmActiveVariableIpAddressVal, 1740 alarmActiveVariableOidVal, 1741 alarmActiveVariableCounter64Val, 1742 alarmActiveVariableOpaqueVal 1743 } 1744 STATUS current 1745 DESCRIPTION 1746 "Active Alarm list group." 1747 ::= { alarmGroups 2} 1749 alarmActiveStatsGroup OBJECT-GROUP 1750 OBJECTS { 1751 alarmActiveStatsActives, 1752 alarmActiveStatsActiveCurrent, 1753 alarmActiveStatsLastRaise, 1754 alarmActiveStatsLastClear 1755 } 1756 STATUS current 1757 DESCRIPTION 1758 "Active alarm summary group." 1759 ::= { alarmGroups 3} 1761 alarmClearGroup OBJECT-GROUP 1762 OBJECTS { 1764 alarmClearMaximum, 1765 alarmClearEngineID, 1766 alarmClearEngineAddressType, 1767 alarmClearEngineAddress, 1768 alarmClearContextName, 1769 alarmClearNotificationID, 1770 alarmClearResourceId, 1771 alarmClearLogIndex, 1772 alarmClearModelPointer 1773 } 1774 STATUS current 1775 DESCRIPTION 1776 "Cleared alarm group." 1777 ::= { alarmGroups 4} 1779 alarmNotificationsGroup NOTIFICATION-GROUP 1780 NOTIFICATIONS { alarmActiveState, alarmClearState } 1781 STATUS current 1782 DESCRIPTION 1783 "The collection of notifications that can be used to 1784 model alarms for faults lacking pre-existing 1785 notification definitions." 1786 ::= { alarmGroups 6 } 1788 END 1790 5. ITU Alarm 1792 5.1 Overview 1794 This MIB module defines alarm information specific to the alarm 1795 model defined in ITU M.3100 [M.3100], X.733[X.733] and X.736[X.736]. 1796 This MIB module follows the modular architecture defined by the 1797 Alarm MIB, in which the generic Alarm MIB can be augmented by other 1798 alarm information defined according to more specific models that 1799 define additional behaviour and characteristics. 1801 The ituAlarmTable contains information from the ITU Alarm Model 1802 about possible alarms in the system. 1804 The ituAlarmActiveTable contains information from the ITU Alarm 1805 Model about alarms modeled using the ituAlarmTable that are 1806 currently occurring on the system. 1808 The ituAlarmActiveStatsTable provides statistics on current and 1809 total alarms. 1811 5.2 IANA Considerations 1813 Over time, there will be a need to add new IANAITUEventType and 1814 IANAItuProbableCause enumerated values. The Internet Assigned Number 1815 Authority (IANA) is responsible for the assignment of the 1816 enumerations in these TCs. 1818 IANAItuProbableCause value of 0 is reserved for special purposes and 1819 MUST NOT be assigned. Values of IANAItuProbableCause in the range 1 1820 to 1023 are reserved for causes that correspond to ITU-T probable 1821 cause. All other requests for new causes will be handled on a 1822 first-come, with 1025. 1824 Request should come in the form of well-formed SMI [RFC2578] for 1825 enumeration names that are unique and sufficiently descriptive. 1827 While some effort will be taken to ensure that new enumerations do 1828 not conceptually duplicate existing enumerations it is acknowledged 1829 that the existence of conceptual duplicates in the starting probable 1830 cause list is an known industry reality. 1832 To aid IANA in the administration of probable cause names and 1833 values, the OPS Area Director will appoint one or more experts to 1834 help review requests. 1836 See http://www.iana.org 1838 The following shall be used as the initial values, but the latest 1839 values for these textual conventions should be obtained from IANA: 1841 IANA-ITU-ALARM-TC DEFINITIONS ::= BEGIN 1843 IMPORTS 1844 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 1845 TEXTUAL-CONVENTION FROM SNMPv2-TC; 1847 ianaItuAlarmNumbers MODULE-IDENTITY 1848 LAST-UPDATED "200402090000Z" 1849 ORGANIZATION "IANA" 1850 CONTACT-INFO 1851 "Postal: Internet Assigned Numbers Authority 1852 Internet Corporation for Assigned Names 1853 and Numbers 1854 4676 Admiralty Way, Suite 330 1855 Marina del Rey, CA 90292-6601 1856 USA 1858 Tel: +1 310-823-9358 1859 E-Mail: iana@iana.org" 1860 DESCRIPTION 1861 "The MIB module defines the ITU Alarm 1862 textual convention for objects expected to require 1863 regular extension. 1865 Copyright (C) The Internet Society (2004). The 1866 initial version of this MIB module was published 1867 in RFC xxxx. For full legal notices see the RFC 1868 itself. Supplementary information may be available on: 1869 http://www.ietf.org/copyrights/ianamib.html" 1870 REVISION "200402090000Z" 1871 DESCRIPTION 1872 "Initial version, published as RFC yyyy." 1873 -- RFC-Editor assigns yyyy 1874 ::= { mib-2 XX } -- to be assigned by IANA 1876 IANAItuProbableCause ::= TEXTUAL-CONVENTION 1877 STATUS current 1878 DESCRIPTION 1879 "ITU-T probable cause values. Duplicate values defined in 1880 X.733 are appended with X733 to ensure syntactic uniqueness. 1881 Probable cause value 0 is reserved for special purposes. 1883 The Internet Assigned Number Authority (IANA) is responsible 1884 for the assignment of the enumerations in this TC. 1885 IANAItuProbableCause value of 0 is reserved for special 1886 purposes and MUST NOT be assigned. 1888 Values of IANAItuProbableCause in the range 1 to 1023 are 1889 reserved for causes that correspond to ITU-T probable cause. 1891 All other requests for new causes will be handled on a 1892 first-come, first served basis and will be assigned 1893 enumeration values starting with 1025. 1895 Request should come in the form of well-formed 1896 SMI [RFC2578] for enumeration names that are unique and 1897 sufficiently descriptive. 1899 While some effort will be taken to ensure that new probable 1900 causes do not conceptually duplicate existing probable 1901 causes it is acknowledged that the existence of conceptual 1902 duplicates in the starting probable cause list is an known 1903 industry reality. 1905 To aid IANA in the administration of probable cause names 1906 and values, the OPS Area Director will appoint one or more 1907 experts to help review requests. 1909 See http://www.iana.org" 1910 REFERENCE 1911 "ITU Recommendation M.3100, 'Generic Network Information 1912 Model', 1995 1913 ITU Recommendation X.733, 'Information Technology - Open 1914 Systems Interconnection - System Management: Alarm 1915 Reporting Function', 1992 1916 ITU Recommendation X.736, 'Information Technology - Open 1917 Systems Interconnection - System Management: Security 1918 Alarm Reporting Function', 1992" 1920 SYNTAX INTEGER 1921 { 1922 -- The following probable causes were defined in M.3100 1923 aIS (1), 1924 callSetUpFailure (2), 1925 degradedSignal (3), 1926 farEndReceiverFailure (4), 1927 framingError (5), 1928 lossOfFrame (6), 1929 lossOfPointer (7), 1930 lossOfSignal (8), 1931 payloadTypeMismatch (9), 1932 transmissionError (10), 1933 remoteAlarmInterface (11), 1934 excessiveBER (12), 1935 pathTraceMismatch (13), 1936 unavailable (14), 1937 signalLabelMismatch (15), 1938 lossOfMultiFrame (16), 1939 receiveFailure (17), 1940 transmitFailure (18), 1941 modulationFailure (19), 1942 demodulationFailure (20), 1943 broadcastChannelFailure (21), 1944 connectionEstablishmentError (22), 1945 invalidMessageReceived (23), 1946 localNodeTransmissionError (24), 1947 remoteNodeTransmissionError (25), 1948 routingFailure (26), 1950 --Values 27-50 are reserved for communications alarm related 1951 --probable causes 1952 -- The following are used with equipment alarm. 1954 backplaneFailure (51), 1955 dataSetProblem (52), 1956 equipmentIdentifierDuplication (53), 1957 externalIFDeviceProblem (54), 1958 lineCardProblem (55), 1959 multiplexerProblem (56), 1960 nEIdentifierDuplication (57), 1961 powerProblem (58), 1962 processorProblem (59), 1963 protectionPathFailure (60), 1964 receiverFailure (61), 1965 replaceableUnitMissing (62), 1966 replaceableUnitTypeMismatch (63), 1967 synchronizationSourceMismatch (64), 1968 terminalProblem (65), 1969 timingProblem (66), 1970 transmitterFailure (67), 1971 trunkCardProblem (68), 1972 replaceableUnitProblem (69), 1973 realTimeClockFailure (70), 1974 --An equipment alarm to be issued if the system detects that the 1975 --real time clock has failed 1976 antennaFailure (71), 1977 batteryChargingFailure (72), 1978 diskFailure (73), 1979 frequencyHoppingFailure (74), 1980 iODeviceError (75), 1981 lossOfSynchronisation (76), 1982 lossOfRedundancy (77), 1983 powerSupplyFailure (78), 1984 signalQualityEvaluationFailure (79), 1985 tranceiverFailure (80), 1986 protectionMechanismFailure (81), 1987 protectingResourceFailure (82), 1988 -- Values 83-100 are reserved for equipment alarm related probable 1989 -- causes 1990 -- The following are used with environmental alarm. 1991 airCompressorFailure (101), 1992 airConditioningFailure (102), 1993 airDryerFailure (103), 1994 batteryDischarging (104), 1995 batteryFailure (105), 1996 commercialPowerFailure (106), 1997 coolingFanFailure (107), 1998 engineFailure (108), 1999 fireDetectorFailure (109), 2000 fuseFailure (110), 2001 generatorFailure (111), 2002 lowBatteryThreshold (112), 2003 pumpFailure (113), 2004 rectifierFailure (114), 2005 rectifierHighVoltage (115), 2006 rectifierLowFVoltage (116), 2007 ventilationsSystemFailure (117), 2008 enclosureDoorOpen (118), 2009 explosiveGas (119), 2010 fire (120), 2011 flood (121), 2012 highHumidity (122), 2013 highTemperature (123), 2014 highWind (124), 2015 iceBuildUp (125), 2016 intrusionDetection (126), 2017 lowFuel (127), 2018 lowHumidity (128), 2019 lowCablePressure (129), 2020 lowTemperatue (130), 2021 lowWater (131), 2022 smoke (132), 2023 toxicGas (133), 2024 coolingSystemFailure (134), 2025 externalEquipmentFailure (135), 2026 externalPointFailure (136), 2027 -- Values 137-150 are reserved for environmental alarm related 2028 -- probable causes 2029 -- The following are used with Processing error alarm. 2030 storageCapacityProblem (151), 2031 memoryMismatch (152), 2032 corruptData (153), 2033 outOfCPUCycles (154), 2034 sfwrEnvironmentProblem (155), 2035 sfwrDownloadFailure (156), 2036 lossOfRealTimel (157), 2037 --A processing error alarm to be issued after the system has 2038 --reinitialised. This will indicate 2039 --to the management systems that the view they have of the managed 2040 --system may no longer 2041 --be valid. Usage example: The managed 2042 --system issues this alarm after a reinitialization with severity 2043 --warning to inform the 2044 --management system about the event. No clearing notification will 2045 --be sent. 2046 applicationSubsystemFailure (158), 2047 configurationOrCustomisationError (159), 2048 databaseInconsistency (160), 2049 fileError (161), 2050 outOfMemory (162), 2051 softwareError (163), 2052 timeoutExpired (164), 2053 underlayingResourceUnavailable (165), 2054 versionMismatch (166), 2055 --Values 168-200 are reserved for processing error alarm related 2056 -- probable causes. 2057 bandwidthReduced (201), 2058 congestion (202), 2059 excessiveErrorRate (203), 2060 excessiveResponseTime (204), 2061 excessiveRetransmissionRate (205), 2062 reducedLoggingCapability (206), 2063 systemResourcesOverload (207 ), 2064 -- The following were defined X.733 2065 adapterError (500), 2066 applicationSubsystemFailture (501), 2067 bandwidthReducedX733 (502), 2068 callEstablishmentError (503), 2069 communicationsProtocolError (504), 2070 communicationsSubsystemFailure (505), 2071 configurationOrCustomizationError (506), 2072 congestionX733 (507), 2073 coruptData (508), 2074 cpuCyclesLimitExceeded (509), 2075 dataSetOrModemError (510), 2076 degradedSignalX733 (511), 2077 dteDceInterfaceError (512), 2078 enclosureDoorOpenX733 (513), 2079 equipmentMalfunction (514), 2080 excessiveVibration (515), 2081 fileErrorX733 (516), 2082 fireDetected (517), 2083 framingErrorX733 (518), 2084 heatingVentCoolingSystemProblem (519), 2085 humidityUnacceptable (520), 2086 inputOutputDeviceError (521), 2087 inputDeviceError (522), 2088 lanError (523), 2089 leakDetected (524), 2090 localNodeTransmissionErrorX733 (525), 2091 lossOfFrameX733 (526), 2092 lossOfSignalX733 (527), 2093 materialSupplyExhausted (528), 2094 multiplexerProblemX733 (529), 2095 outOfMemoryX733 (530), 2096 ouputDeviceError (531), 2097 performanceDegraded (532), 2098 powerProblems (533), 2099 pressureUnacceptable (534), 2100 processorProblems (535), 2101 pumpFailureX733 (536), 2102 queueSizeExceeded (537), 2103 receiveFailureX733 (538), 2104 receiverFailureX733 (539), 2105 remoteNodeTransmissionErrorX733 (540), 2106 resourceAtOrNearingCapacity (541), 2107 responseTimeExecessive (542), 2108 retransmissionRateExcessive (543), 2109 softwareErrorX733 (544), 2110 softwareProgramAbnormallyTerminated (545), 2111 softwareProgramError (546), 2112 storageCapacityProblemX733 (547), 2113 temperatureUnacceptable (548), 2114 thresholdCrossed (549), 2115 timingProblemX733 (550), 2116 toxicLeakDetected (551), 2117 transmitFailureX733 (552), 2118 transmiterFailure (553), 2119 underlyingResourceUnavailable (554), 2120 versionMismatchX733 (555), 2121 -- The following are defined in X.736 2122 authenticationFailure (600), 2123 breachOfConfidentiality (601), 2124 cableTamper (602), 2125 delayedInformation (603), 2126 denialOfService (604), 2127 duplicateInformation (605), 2128 informationMissing (606), 2129 informationModificationDetected (607), 2130 informationOutOfSequence (608), 2131 keyExpired (609), 2132 nonRepudiationFailure (610), 2133 outOfHoursActivity (611), 2134 outOfService (612), 2135 proceduralError (613), 2136 unauthorizedAccessAttempt (614), 2137 unexpectedInformation (615), 2139 other (1024) 2140 } 2142 IANAItuEventType ::= TEXTUAL-CONVENTION 2143 STATUS current 2144 DESCRIPTION 2145 "The ITU event Type values. 2147 The Internet Assigned Number Authority (IANA) is 2148 responsible for the assignment of the enumerations 2149 in this TC. 2151 Request should come in the form of well-formed 2152 SMI [RFC2578] for enumeration names that are unique 2153 and sufficiently descriptive. 2155 See http://www.iana.org " 2156 REFERENCE 2157 "ITU Recommendation X.736, 'Information Technology - Open 2158 Systems Interconnection - System Management: Security 2159 Alarm Reporting Function', 1992" 2160 SYNTAX INTEGER 2161 { 2162 other (1), 2163 communicationsAlarm (2), 2164 qualityOfServiceAlarm (3), 2165 processingErrorAlarm (4), 2166 equipmentAlarm (5), 2167 environmentalAlarm (6), 2168 integrityViolation (7), 2169 operationalViolation (8), 2170 physicalViolation (9), 2171 securityServiceOrMechanismViolation (10), 2172 timeDomainViolation (11) 2173 } 2175 END 2177 5.3 Textual Conventions 2179 ITU-ALARM-TC DEFINITIONS ::= BEGIN 2181 IMPORTS 2182 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 2183 TEXTUAL-CONVENTION FROM SNMPv2-TC; 2185 ituAlarmTc MODULE-IDENTITY 2186 LAST-UPDATED "200402090000Z" 2187 ORGANIZATION "IETF Distributed Management Working Group" 2188 CONTACT-INFO 2189 " WG EMail: disman@ietf.org 2190 Subscribe: disman-request@ietf.org 2191 http://www.ietf.org/html.charters/disman-charter.html 2193 Chair: Randy Presuhn 2194 randy_presuhn@mindspring.com 2196 Editors: Sharon Chisholm 2197 Nortel Networks 2198 PO Box 3511 Station C 2199 Ottawa, Ont. K1Y 4H7 2200 Canada 2201 schishol@nortelnetworks.com 2203 Dan Romascanu 2204 Avaya 2205 Atidim Technology Park, Bldg. #3 2206 Tel Aviv, 61131 2207 Israel 2208 Tel: +972-3-645-8414 2209 Email: dromasca@avaya.com" 2210 DESCRIPTION 2211 "This MIB module defines the ITU Alarm 2212 textual convention for objects not expected to require 2213 regular extension. 2215 Copyright (C) The Internet Society (2004). The 2216 initial version of this MIB module was published 2217 in RFC YYYY. For full legal notices see the RFC 2218 itself. Supplementary information may be available on: 2219 http://www.ietf.org/copyrights/ianamib.html" 2220 -- RFC Ed.: replace yyyy with actual RFC number & remove 2221 -- this note 2222 REVISION "200402090000Z" 2223 DESCRIPTION 2224 "Initial version, published as RFC yyyy." 2225 -- RFC-Editor assigns yyyy 2226 ::= { mib-2 XX } -- to be assigned by IANA 2228 ItuPerceivedSeverity ::= TEXTUAL-CONVENTION 2229 STATUS current 2230 DESCRIPTION 2231 "ITU perceived severity values" 2232 REFERENCE 2233 "ITU Recommendation M.3100, 'Generic Network Information 2234 Model', 1995 2235 ITU Recommendation X.733, 'Information Technology - Open 2236 Systems Interconnection - System Management: Alarm 2237 Reporting Function', 1992" 2238 SYNTAX INTEGER 2239 { 2240 cleared (1), 2241 indeterminate (2), 2242 critical (3), 2243 major (4), 2244 minor (5), 2245 warning (6) 2246 } 2248 ItuTrendIndication ::= TEXTUAL-CONVENTION 2249 STATUS current 2250 DESCRIPTION 2251 "ITU trend indication values for alarms." 2252 REFERENCE 2253 "ITU Recommendation M.3100, 'Generic Network Information 2254 Model', 1995 2255 ITU Recommendation X.733, 'Information Technology - Open 2256 Systems Interconnection - System Management: Alarm 2257 Reporting Function', 1992" 2258 SYNTAX INTEGER 2259 { 2260 moreSevere (1), 2261 noChange (2), 2262 lessSevere (3) 2263 } 2265 END 2267 5.4 Definitions 2269 ITU-ALARM-MIB DEFINITIONS ::= BEGIN 2271 IMPORTS 2272 MODULE-IDENTITY, OBJECT-TYPE, 2273 Gauge32, mib-2 FROM SNMPv2-SMI 2274 AutonomousType, RowPointer FROM SNMPv2-TC 2275 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 2276 alarmListName, alarmModelIndex, 2277 alarmActiveDateAndTime, alarmActiveIndex 2278 FROM ALARM-MIB 2280 ItuPerceivedSeverity, 2281 ItuTrendIndication FROM ITU-ALARM-TC 2282 IANAItuProbableCause, 2283 IANAItuEventType FROM IANA-ITU-ALARM-TC 2284 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF 2285 ZeroBasedCounter32 FROM RMON2-MIB; 2287 ituAlarmMIB MODULE-IDENTITY 2288 LAST-UPDATED "200402090000Z" 2289 ORGANIZATION "IETF Distributed Management Working Group" 2290 CONTACT-INFO 2291 "WG EMail: disman@ietf.org 2292 Subscribe: disman-request@ietf.org 2293 http://www.ietf.org/html.charters/disman-charter.html 2295 Chair: Randy Presuhn 2296 randy_presuhn@mindspring.com 2298 Editors: Sharon Chisholm 2299 Nortel Networks 2300 PO Box 3511 Station C 2301 Ottawa, Ont. K1Y 4H7 2302 Canada 2303 schishol@nortelnetworks.com 2305 Dan Romascanu 2306 Avaya 2307 Atidim Technology Park, Bldg. #3 2308 Tel Aviv, 61131 2309 Israel 2310 Tel: +972-3-645-8414 2311 Email: dromasca@avaya.com" 2312 DESCRIPTION 2313 "The MIB module describes ITU Alarm information 2314 as defined in ITU Recommendation M.3100 [M.3100], 2315 X.733 [X.733] and X.736 [X.736]. 2317 Copyright (C) The Internet Society (2004). The 2318 initial version of this MIB module was published 2319 in RFC YYYY. For full legal notices see the RFC 2320 itself. Supplementary information may be available on: 2321 http://www.ietf.org/copyrights/ianamib.html" 2322 -- RFC Ed.: replace yyyy with actual RFC number & remove 2323 -- this note 2324 REVISION "200402090000Z" 2325 DESCRIPTION 2326 "Initial version, published as RFC yyyy." 2327 -- RFC-Editor assigns yyyy 2328 ::= { mib-2 XX } -- to be assigned by IANA 2330 ituAlarmObjects OBJECT IDENTIFIER ::= { ituAlarmMIB 1 } 2331 ituAlarmModel OBJECT IDENTIFIER ::= { ituAlarmObjects 1 } 2333 ituAlarmActive OBJECT IDENTIFIER ::= { ituAlarmObjects 2 } 2335 ituAlarmTable OBJECT-TYPE 2336 SYNTAX SEQUENCE OF ItuAlarmEntry 2337 MAX-ACCESS not-accessible 2338 STATUS current 2339 DESCRIPTION 2340 "A table of ITU Alarm information for possible alarms 2341 on the system." 2342 ::= { ituAlarmModel 1 } 2344 ituAlarmEntry OBJECT-TYPE 2345 SYNTAX ItuAlarmEntry 2346 MAX-ACCESS not-accessible 2347 STATUS current 2348 DESCRIPTION 2349 "Entries appear in this table whenever an entry is created 2350 in the alarmModelTable with a value of alarmModelState in 2351 the range from 1 to 6. Entries disappear from this table 2352 whenever the corresponding entries are deleted from the 2353 alarmModelTable, including in cases where those entries 2354 have been deleted due to local system action. The value of 2355 alarmModelSpecificPointer has no effect on the creation 2356 or deletion of entries in this table. Values of 2357 alarmModelState map to values of ituAlarmPerceivedSeverity 2358 as follows: 2360 alarmModelState -> ituAlarmPerceivedSeverity 2361 1 -> clear (1) 2362 2 -> indeterminate (2) 2363 3 -> warning (6) 2364 4 -> minor (5) 2365 5 -> major (4) 2366 6 -> critical (3) 2368 All other values of alarmModelState MUST NOT appear 2369 in this table. 2371 This table MUST be persistent across system reboots." 2372 INDEX { alarmListName, alarmModelIndex, 2373 ituAlarmPerceivedSeverity } 2374 ::= { ituAlarmTable 1 } 2376 ItuAlarmEntry ::= SEQUENCE { 2377 ituAlarmPerceivedSeverity ItuPerceivedSeverity, 2378 ituAlarmEventType IANAItuEventType, 2379 ituAlarmProbableCause IANAItuProbableCause, 2380 ituAlarmAdditionalText SnmpAdminString, 2381 ituAlarmGenericModel RowPointer } 2383 ituAlarmPerceivedSeverity OBJECT-TYPE 2384 SYNTAX ItuPerceivedSeverity 2385 MAX-ACCESS not-accessible 2386 STATUS current 2387 DESCRIPTION 2388 "ITU perceived severity values." 2389 REFERENCE 2390 "ITU Recommendation M.3100, 'Generic Network Information 2391 Model', 1995 2392 ITU Recommendation X.733, 'Information Technology - Open 2393 Systems Interconnection - System Management: Alarm 2394 Reporting Function', 1992" 2395 ::= { ituAlarmEntry 1 } 2397 ituAlarmEventType OBJECT-TYPE 2398 SYNTAX IANAItuEventType 2399 MAX-ACCESS read-write 2400 STATUS current 2401 DESCRIPTION 2402 "Represents the event type values for the alarms" 2403 REFERENCE 2404 "ITU Recommendation M.3100, 'Generic Network Information 2405 Model', 1995 2406 ITU Recommendation X.733, 'Information Technology - Open 2407 Systems Interconnection - System Management: Alarm 2408 Reporting Function', 1992 2409 ITU Recommendation X.736, 'Information Technology - Open 2410 Systems Interconnection - System Management: Security 2411 Alarm Reporting Function', 1992" 2412 ::= { ituAlarmEntry 2 } 2414 ituAlarmProbableCause OBJECT-TYPE 2415 SYNTAX IANAItuProbableCause 2416 MAX-ACCESS read-write 2417 STATUS current 2419 DESCRIPTION 2420 "ITU probable cause values." 2421 REFERENCE 2422 "ITU Recommendation M.3100, 'Generic Network Information 2423 Model', 1995 2424 ITU Recommendation X.733, 'Information Technology - Open 2425 Systems Interconnection - System Management: Alarm 2426 Reporting Function', 1992 2427 ITU Recommendation X.736, 'Information Technology - Open 2428 Systems Interconnection - System Management: Security 2429 Alarm Reporting Function', 1992" 2430 ::= { ituAlarmEntry 3 } 2432 ituAlarmAdditionalText OBJECT-TYPE 2433 SYNTAX SnmpAdminString 2434 MAX-ACCESS read-write 2435 STATUS current 2436 DESCRIPTION 2437 "Represents the additional text field for the alarm." 2438 REFERENCE 2439 "ITU Recommendation M.3100, 'Generic Network Information 2440 Model', 1995 2441 ITU Recommendation X.733, 'Information Technology - Open 2442 Systems Interconnection - System Management: Alarm 2443 Reporting Function', 1992" 2444 ::= { ituAlarmEntry 4} 2446 ituAlarmGenericModel OBJECT-TYPE 2447 SYNTAX RowPointer 2448 MAX-ACCESS read-write 2449 STATUS current 2450 DESCRIPTION 2451 "This object points to the corresponding 2452 row in the alarmModelTable for this alarm severity. 2454 This corresponding entry to alarmModelTable could also 2455 be derived by performing the reverse of the mapping 2456 from alarmModelState to ituAlarmPerceivedSeverity defined 2457 in the description of ituAlarmEntry to determine the 2458 appropriate { alarmListName, alarmModelIndex, alarmModelState } 2459 for this { alarmListName, alarmModelIndex, 2460 ituAlarmPerceivedSeverity }." 2461 ::= { ituAlarmEntry 5 } 2463 -- ITU Active Alarm Table -- 2465 ituAlarmActiveTable OBJECT-TYPE 2466 SYNTAX SEQUENCE OF ItuAlarmActiveEntry 2467 MAX-ACCESS not-accessible 2468 STATUS current 2469 DESCRIPTION 2470 "A table of ITU information for active alarms entries." 2471 ::= { ituAlarmActive 1 } 2473 ituAlarmActiveEntry OBJECT-TYPE 2474 SYNTAX ItuAlarmActiveEntry 2475 MAX-ACCESS not-accessible 2476 STATUS current 2477 DESCRIPTION 2478 "Entries appear in this table when alarms are active. They 2479 are removed when the alarm is no longer occurring." 2480 INDEX { alarmListName, alarmActiveDateAndTime, 2481 alarmActiveIndex } 2482 ::= { ituAlarmActiveTable 1 } 2484 ItuAlarmActiveEntry ::= SEQUENCE { 2485 ituAlarmActiveTrendIndication ItuTrendIndication, 2486 ituAlarmActiveDetector AutonomousType, 2487 ituAlarmActiveServiceProvider AutonomousType, 2488 ituAlarmActiveServiceUser AutonomousType 2489 } 2491 ituAlarmActiveTrendIndication OBJECT-TYPE 2492 SYNTAX ItuTrendIndication 2493 MAX-ACCESS read-only 2494 STATUS current 2495 DESCRIPTION 2496 "Represents the trend indication values for the alarms." 2497 REFERENCE 2498 "ITU Recommendation M.3100, 'Generic Network Information 2499 Model', 1995 2500 ITU Recommendation X.733, 'Information Technology - Open 2501 Systems Interconnection - System Management: Alarm 2502 Reporting Function', 1992" 2503 ::= { ituAlarmActiveEntry 1 } 2505 ituAlarmActiveDetector OBJECT-TYPE 2506 SYNTAX AutonomousType 2507 MAX-ACCESS read-only 2508 STATUS current 2509 DESCRIPTION 2510 "Represents the SecurityAlarmDetector object." 2511 REFERENCE 2512 "ITU Recommendation X.736, 'Information Technology - Open 2513 Systems Interconnection - System Management: Security 2514 Alarm Reporting Function', 1992" 2515 ::= { ituAlarmActiveEntry 2 } 2517 ituAlarmActiveServiceProvider OBJECT-TYPE 2518 SYNTAX AutonomousType 2519 MAX-ACCESS read-only 2520 STATUS current 2521 DESCRIPTION 2522 "Represents the ServiceProvider object." 2523 REFERENCE 2524 "ITU Recommendation X.736, 'Information Technology - Open 2525 Systems Interconnection - System Management: Security 2526 Alarm Reporting Function', 1992" 2527 ::= { ituAlarmActiveEntry 3 } 2529 ituAlarmActiveServiceUser OBJECT-TYPE 2530 SYNTAX AutonomousType 2531 MAX-ACCESS read-only 2532 STATUS current 2533 DESCRIPTION 2534 "Represents the ServiceUser object." 2535 REFERENCE 2536 "ITU Recommendation X.736, 'Information Technology - Open 2537 Systems Interconnection - System Management: Security 2538 Alarm Reporting Function', 1992" 2539 ::= { ituAlarmActiveEntry 4 } 2541 -- Statistics and Counters 2543 ituAlarmActiveStatsTable OBJECT-TYPE 2544 SYNTAX SEQUENCE OF ItuAlarmActiveStatsEntry 2545 MAX-ACCESS not-accessible 2546 STATUS current 2547 DESCRIPTION 2548 "This table represents the ITU alarm statistics 2549 information." 2550 ::= { ituAlarmActive 2 } 2552 ituAlarmActiveStatsEntry OBJECT-TYPE 2553 SYNTAX ItuAlarmActiveStatsEntry 2554 MAX-ACCESS not-accessible 2555 STATUS current 2556 DESCRIPTION 2557 "Statistics on the current active ITU alarms." 2558 INDEX { alarmListName } 2560 ::= { ituAlarmActiveStatsTable 1 } 2562 ItuAlarmActiveStatsEntry ::= 2563 SEQUENCE { 2564 ituAlarmActiveStatsIndeterminateCurrent Gauge32, 2565 ituAlarmActiveStatsCriticalCurrent Gauge32, 2566 ituAlarmActiveStatsMajorCurrent Gauge32, 2567 ituAlarmActiveStatsMinorCurrent Gauge32, 2568 ituAlarmActiveStatsWarningCurrent Gauge32, 2569 ituAlarmActiveStatsIndeterminates ZeroBasedCounter32, 2570 ituAlarmActiveStatsCriticals ZeroBasedCounter32, 2571 ituAlarmActiveStatsMajors ZeroBasedCounter32, 2572 ituAlarmActiveStatsMinors ZeroBasedCounter32, 2573 ituAlarmActiveStatsWarnings ZeroBasedCounter32 2574 } 2576 ituAlarmActiveStatsIndeterminateCurrent OBJECT-TYPE 2577 SYNTAX Gauge32 2578 MAX-ACCESS read-only 2579 STATUS current 2580 DESCRIPTION 2581 "A count of the current number of active alarms with a 2582 ituAlarmPerceivedSeverity of indeterminate." 2583 ::= { ituAlarmActiveStatsEntry 1 } 2585 ituAlarmActiveStatsCriticalCurrent OBJECT-TYPE 2586 SYNTAX Gauge32 2587 MAX-ACCESS read-only 2588 STATUS current 2589 DESCRIPTION 2590 "A count of the current number of active alarms with a 2591 ituAlarmPerceivedSeverity of critical." 2592 ::= { ituAlarmActiveStatsEntry 2 } 2594 ituAlarmActiveStatsMajorCurrent OBJECT-TYPE 2595 SYNTAX Gauge32 2596 MAX-ACCESS read-only 2597 STATUS current 2598 DESCRIPTION 2599 "A count of the current number of active alarms with a 2600 ituAlarmPerceivedSeverity of major." 2601 ::= { ituAlarmActiveStatsEntry 3 } 2603 ituAlarmActiveStatsMinorCurrent OBJECT-TYPE 2604 SYNTAX Gauge32 2605 MAX-ACCESS read-only 2606 STATUS current 2607 DESCRIPTION 2608 "A count of the current number of active alarms with a 2609 ituAlarmPerceivedSeverity of minor." 2610 ::= { ituAlarmActiveStatsEntry 4 } 2612 ituAlarmActiveStatsWarningCurrent OBJECT-TYPE 2613 SYNTAX Gauge32 2614 MAX-ACCESS read-only 2615 STATUS current 2616 DESCRIPTION 2617 "A count of the current number of active alarms with a 2618 ituAlarmPerceivedSeverity of warning." 2619 ::= { ituAlarmActiveStatsEntry 5 } 2621 ituAlarmActiveStatsIndeterminates OBJECT-TYPE 2622 SYNTAX ZeroBasedCounter32 2623 MAX-ACCESS read-only 2624 STATUS current 2625 DESCRIPTION 2626 "A count of the total number of active alarms with a 2627 ituAlarmPerceivedSeverity of indeterminate since system 2628 restart." 2629 ::= { ituAlarmActiveStatsEntry 6 } 2631 ituAlarmActiveStatsCriticals OBJECT-TYPE 2632 SYNTAX ZeroBasedCounter32 2633 MAX-ACCESS read-only 2634 STATUS current 2635 DESCRIPTION 2636 "A count of the total number of active alarms with a 2637 ituAlarmPerceivedSeverity of critical since system restart." 2638 ::= { ituAlarmActiveStatsEntry 7 } 2640 ituAlarmActiveStatsMajors OBJECT-TYPE 2641 SYNTAX ZeroBasedCounter32 2642 MAX-ACCESS read-only 2643 STATUS current 2644 DESCRIPTION 2645 "A count of the total number of active alarms with a 2646 ituAlarmPerceivedSeverity of major since system restart." 2647 ::= { ituAlarmActiveStatsEntry 8 } 2649 ituAlarmActiveStatsMinors OBJECT-TYPE 2650 SYNTAX ZeroBasedCounter32 2651 MAX-ACCESS read-only 2652 STATUS current 2653 DESCRIPTION 2654 "A count of the total number of active alarms with a 2655 ituAlarmPerceivedSeverity of minor since system restart." 2656 ::= { ituAlarmActiveStatsEntry 9 } 2658 ituAlarmActiveStatsWarnings OBJECT-TYPE 2659 SYNTAX ZeroBasedCounter32 2660 MAX-ACCESS read-only 2661 STATUS current 2662 DESCRIPTION 2663 "A count of the total number of active alarms with a 2664 ituAlarmPerceivedSeverity of warning since system restart." 2665 ::= { ituAlarmActiveStatsEntry 10 } 2667 -- Conformance 2669 ituAlarmConformance OBJECT IDENTIFIER ::= { ituAlarmMIB 2 } 2670 ituAlarmCompliances OBJECT IDENTIFIER ::= { ituAlarmConformance 1 } 2672 ituAlarmCompliance MODULE-COMPLIANCE 2673 STATUS current 2674 DESCRIPTION 2675 "The compliance statement for systems supporting 2676 the ITU Alarm MIB." 2677 MODULE -- this module 2678 MANDATORY-GROUPS { 2679 ituAlarmGroup 2680 } 2681 GROUP ituAlarmServiceUserGroup 2682 DESCRIPTION 2683 "This group is optional." 2684 GROUP ituAlarmSecurityGroup 2685 DESCRIPTION 2686 "This group is optional." 2687 GROUP ituAlarmStatisticsGroup 2688 DESCRIPTION 2689 "This group is optional." 2690 ::= { ituAlarmCompliances 1 } 2692 ituAlarmGroups OBJECT IDENTIFIER ::= { ituAlarmConformance 2 } 2694 ituAlarmGroup OBJECT-GROUP 2695 OBJECTS { 2696 ituAlarmEventType, 2697 ituAlarmProbableCause, 2698 ituAlarmGenericModel 2699 } 2700 STATUS current 2701 DESCRIPTION 2702 "ITU alarm details list group." 2703 ::= { ituAlarmGroups 1} 2705 ituAlarmServiceUserGroup OBJECT-GROUP 2706 OBJECTS { 2707 ituAlarmAdditionalText, 2708 ituAlarmActiveTrendIndication 2709 } 2710 STATUS current 2711 DESCRIPTION 2712 "The use of these parameters is a service-user option." 2713 ::= { ituAlarmGroups 2 } 2715 ituAlarmSecurityGroup OBJECT-GROUP 2716 OBJECTS { 2717 ituAlarmActiveDetector, 2718 ituAlarmActiveServiceProvider, 2719 ituAlarmActiveServiceUser 2720 } 2721 STATUS current 2722 DESCRIPTION 2723 "Security Alarm Reporting Function" 2724 REFERENCE 2725 "ITU Recommendation X.736, 'Information Technology - Open 2726 Systems Interconnection - System Management: Security 2727 Alarm Reporting Function', 1992" 2728 ::= { ituAlarmGroups 3 } 2730 ituAlarmStatisticsGroup OBJECT-GROUP 2731 OBJECTS { 2732 ituAlarmActiveStatsIndeterminateCurrent, 2733 ituAlarmActiveStatsCriticalCurrent, 2734 ituAlarmActiveStatsMajorCurrent, 2735 ituAlarmActiveStatsMinorCurrent, 2736 ituAlarmActiveStatsWarningCurrent, 2737 ituAlarmActiveStatsIndeterminates, 2738 ituAlarmActiveStatsCriticals, 2739 ituAlarmActiveStatsMajors, 2740 ituAlarmActiveStatsMinors, 2741 ituAlarmActiveStatsWarnings 2742 } 2743 STATUS current 2744 DESCRIPTION 2745 "ITU Active Alarm Statistics." 2746 ::= { ituAlarmGroups 4 } 2748 END 2750 6. Examples 2752 6.1 Alarms Based on linkUp/linkDown Notifications 2754 This example demonstrates an interface-based alarm that goes into a 2755 state of "warning" when a linkDown Notification [RFC2863] occurs but 2756 the ifAdminStatus indicates the interface was taken down 2757 administratively. If IfAdminStatus is "up" when the linkDown 2758 Notification occurs, then there is a problem, so the state of the 2759 alarm is critical. A linkUp alarm clears the alarm. 2761 linkDown NOTIFICATION-TYPE 2762 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 2763 STATUS current 2764 DESCRIPTION 2765 "" 2766 ::= { snmpTraps 3 } 2768 linkUp NOTIFICATION-TYPE 2769 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 2770 STATUS current 2771 DESCRIPTION 2772 "" 2773 ::= { snmpTraps 4 } 2775 alarmModelIndex 3 2776 alarmModelState 1 2777 alarmModelNotificationId linkUp 2778 alarmModelVarbindIndex 0 2779 alarmModelVarbindValue 0 2780 alarmModelDescription "linkUp" 2781 alarmModelSpecificPointer ituAlarmEntry.3.1 2782 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2783 alarmModelResourcePrefix 0.0 2784 alarmModelRowStatus active (1) 2785 ituAlarmEventType communicationsAlarm (2) 2786 ituAlarmPerceivedSeverity cleared (1) 2787 ituAlarmGenericModel alarmModelEntry.3.1 2789 alarmModelIndex 3 2790 alarmModelState 2 2791 alarmModelNotificationId linkDown 2792 alarmModelVarbindIndex 2 2793 alarmModelVarbindValue down (2) 2794 alarmModelDescription "linkDown administratively" 2795 alarmModelSpecificPointer ituAlarmEntry.3.6 2796 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2797 alarmModelResourcePrefix 0.0 2798 alarmModelRowStatus active (1) 2799 ituAlarmEventType communicationsAlarm (2) 2800 ituAlarmPerceivedSeverity warning (6) 2801 ituAlarmGenericModel alarmModelEntry.3.2 2803 alarmModelIndex 3 2804 alarmModelState 3 2805 alarmModelNotificationId linkDown 2806 alarmModelVarbindIndex 2 2807 alarmModelVarbindValue up (1) 2808 alarmModelDescription "linkDown - confirmed problem" 2809 alarmModelSpecificPointer ituAlarmEntry.3.3 2810 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2811 alarmModelResourcePrefix 0.0 2812 alarmModelRowStatus active (1) 2813 ituAlarmEventType communicationsAlarm (2) 2814 ituAlarmPerceivedSeverity critical (3) 2815 ituAlarmGenericModel alarmModelEntry.3.3 2817 alarmActiveIndex 1 2818 alarmActiveTime 2342464573 2819 alarmActiveDateAndTime DateAndTime, 2820 alarmActiveEngineID SnmpEngineID, 2821 alarmActiveEngineAddressType ipV4 2822 alarmActiveEngineAddress 10.10.10.10 2823 alarmActiveContextName SnmpAdminString, 2824 alarmActiveVariables 3 2825 alarmActiveNotificationID 1.3.6.1.6.3.1.1.5.3 2826 alarmActiveResourceId 1.3.6.1.2.1.2.2.1.1.346 2827 alarmActiveLogPointer 0.0 2828 alarmActiveModelPointer alarmModelEntry.3.3 2829 alarmActiveSpecificPointer ituAlarmActiveEntry.1.3 2830 ituAlarmActiveTrendIndication moreSevere (1) 2831 ituAlarmDetector 0.0 2832 ituAlarmServiceProvider 0.0 2833 ituAlarmServiceUser 0.0 2835 alarmActiveVariableIndex 1 2836 alarmActiveVariableID sysUpTime.0 2837 alarmActiveVariableValueType timeTicks(3) 2838 alarmActiveVariableCounter32Val 0 2839 alarmActiveVariableUnsigned32Val 0 2840 alarmActiveVariableTimeTicksVal 46754 2841 alarmActiveVariableInteger32Val 0 2842 alarmActiveVariableOctetStringVal "" 2843 alarmActiveVariableIpAddressVal 0 2844 alarmActiveVariableOidVal 0.0 2845 alarmActiveVariableCounter64Val 0 2846 alarmActiveVariableIndex 2 2847 alarmActiveVariableID snmpTrapOID.0 2848 alarmActiveVariableValueType objectId(7) 2849 alarmActiveVariableCounter32Val 0 2850 alarmActiveVariableUnsigned32Val 0 2851 alarmActiveVariableTimeTicksVal 0 2852 alarmActiveVariableInteger32Val 0 2853 alarmActiveVariableOctetStringVal "" 2854 alarmActiveVariableIpAddressVal 0 2855 alarmActiveVariableOidVal 1.3.6.1.6.3.1.1.5.3 2856 alarmActiveVariableCounter64Val 0 2857 alarmActiveVariableIndex 3 2858 alarmActiveVariableID ifIndex 2859 alarmActiveVariableValueType integer32(4) 2860 alarmActiveVariableCounter32Val 0 2861 alarmActiveVariableUnsigned32Val 0 2862 alarmActiveVariableTimeTicksVal 0 2863 alarmActiveVariableInteger32Val 346 2864 alarmActiveVariableOctetStringVal "" 2865 alarmActiveVariableIpAddressVal 0 2866 alarmActiveVariableOidVal 0.0 2867 alarmActiveVariableCounter64Val 0 2868 alarmActiveVariableIndex 4 2869 alarmActiveVariableID ifAdminStatus 2870 alarmActiveVariableValueType integer32(4) 2871 alarmActiveVariableCounter32Val 0 2872 alarmActiveVariableUnsigned32Val 0 2873 alarmActiveVariableTimeTicksVal 0 2874 alarmActiveVariableInteger32Val up (1) 2875 alarmActiveVariableOctetStringVal "" 2876 alarmActiveVariableIpAddressVal 0 2877 alarmActiveVariableOidVal 0.0 2878 alarmActiveVariableCounter64Val 0 2879 alarmActiveVariableIndex 5 2880 alarmActiveVariableID ifOperStatus 2881 alarmActiveVariableValueType integer32(4) 2882 alarmActiveVariableCounter32Val 0 2883 alarmActiveVariableUnsigned32Val 0 2884 alarmActiveVariableTimeTicksVal 0 2885 alarmActiveVariableInteger32Val down(2) 2886 alarmActiveVariableOctetStringVal "" 2887 alarmActiveVariableIpAddressVal 0 2888 alarmActiveVariableOidVal 0.0 2889 alarmActiveVariableCounter64Val 0 2890 alarmActiveVariableOpaqueVal 2892 6.2 Temperature Alarms Using Generic Notifications 2894 Consider a system able to detect four different temperature 2895 states for a widget - normal, minor, major, critical. The 2896 system does not have any Notification definitions for these 2897 alarm states. A temperature alarm can be modelled using the 2898 generic alarm Notifications of alarmClearState and alarmActive. 2900 alarmModelIndex 5 2901 alarmModelState 1 2902 alarmModelNotificationId alarmClearState 2903 alarmModelVarbindIndex 2 2904 alarmModelVarbindValue cleared (1) 2905 alarmModelDescription "Acme Widget Temperature Normal" 2906 alarmModelSpecificPointer ituAlarmEntry.5.1 2907 alarmModelVarbindSubtree alarmActiveResourceId 2908 alarmModelResourcePrefix 0.0 2909 alarmModelRowStatus active (1) 2910 ituAlarmEventType environmentalAlarm (6) 2911 ituPerceivedSeverity cleared (1) 2912 ituAlarmGenericModel alarmModelEntry.5.1 2914 alarmModelIndex 5 2915 alarmModelState 2 2916 alarmModelNotificationId alarmActiveState 2917 alarmModelVarbindIndex 2 2918 alarmModelVarbindValue minor (5) 2919 alarmModelDescription "Acme Widget Temperature Minor" 2920 alarmModelSpecificPointer ituAlarmEntry.5.5 2921 alarmModelVarbindSubtree alarmActiveResourceId 2922 alarmModelResourcePrefix 0.0 2923 alarmModelRowStatus active (1) 2924 ituAlarmEventState environmentalAlarm (6) 2925 ituPerceivedSeverity minor (5) 2926 ituAlarmGenericModel alarmModelEntry.5.2 2928 alarmModelIndex 5 2929 alarmModelState 3 2930 alarmModelNotificationId alarmActiveState 2931 alarmModelVarbindIndex 2 2932 alarmModelVarbindValue major (4) 2933 alarmModelDescription "Acme Widget Temperature Major" 2934 alarmModelSpecificPointer ituAlarmEntry.5.4 2935 alarmModelVarbindSubtree alarmActiveResourceId 2936 alarmModelResourcePrefix 0.0 2937 alarmModelRowStatus active (1) 2938 ituAlarmEventType environmentalAlarm (6) 2939 ituPerceivedSeverity major (4) 2940 ituAlarmGenericModel alarmModelEntry.5.3 2941 alarmModelIndex 5 2942 alarmModelState 4 2943 alarmModelNotificationId alarmActiveState 2944 alarmModelVarbindIndex 2 2945 alarmModelVarbindValue critical (3) 2946 alarmModelDescription "Acme Widget Temperature Critical" 2947 alarmModelSpecificPointer ituAlarmEntry.5.3 2948 alarmModelVarbindSubtree alarmActiveResourceId 2949 alarmModelResourcePrefix 0.0 2950 alarmModelRowStatus active (1) 2951 ituAlarmEventType environmentalAlarm (6) 2952 ituPerceivedSeverity critical (3) 2953 ituAlarmGenericModel alarmModelEntry.5.4 2955 6.3 Temperature Alarms Without Notifications 2957 Consider a system able to detect four different temperature 2958 states for a widget - normal, minor, major, critical. The 2959 system does not have any Notification definitions for these 2960 alarm states. A temperature alarm can be modelled without 2961 specifying any Notifications in the alarm model. When a 2962 temperature state other than normal is detected, an instance 2963 of this alarm would be added to the active alarm table, but 2964 no Notifications would be sent out. 2966 This could alternatively be accomplished using the models from 2967 example 6.2 and by not specifying any target managers in the 2968 SNMP-TARGET-MIB, which would allow the alarm state 2969 Notifications to be logged in the Notification Log while 2970 still preventing Notifications from being transmitted 2971 on the wire. 2973 alarmModelIndex 6 2974 alarmModelState 1 2975 alarmModelNotificationId 0.0 2976 alarmModelVarbindIndex 0 2977 alarmModelVarbindValue 0 2978 alarmModelDescription "Widget Temperature" 2979 alarmModelSpecificPointer ituAlarmEntry.6.1 2980 alarmModelVarbindSubtree 0.0 2981 alarmModelResourcePrefix 0.0 2982 alarmModelRowStatus active (1) 2983 ituAlarmEventType environmentalAlarm (6) 2984 ituPerceivedSeverity cleared (1) 2985 ituAlarmGenericModel alarmModelEntry.6.1 2987 alarmModelIndex 6 2988 alarmModelState 2 2989 alarmModelNotificationId 0.0 2990 alarmModelVarbindIndex 0 2991 alarmModelVarbindValue 0 2992 alarmModelDescription "Widget Temperature" 2993 alarmModelSpecificPointer ituAlarmEntry.6.5 2994 alarmModelVarbindSubtree 0.0 2995 alarmModelResourcePrefix 0.0 2996 alarmModelRowStatus active (1) 2997 ituAlarmEventState environmentalAlarm (6) 2998 ituAlarmPerceivedSeverity minor (5) 2999 ituAlarmGenericModel alarmModelEntry.6.2 3001 alarmModelIndex 6 3002 alarmModelState 3 3003 alarmModelNotificationId 0.0 3004 alarmModelVarbindIndex 0 3005 alarmModelVarbindValue 0 3006 alarmModelDescription "Widget Temperature" 3007 alarmModelSpecificPointer ituAlarmEntry.6.4 3008 alarmModelVarbindSubtree 0.0 3009 alarmModelResourcePrefix 0.0 3010 alarmModelRowStatus active (1) 3011 ituAlarmEventType environmentalAlarm (6) 3012 ituPerceivedSeverity major (4) 3013 ituAlarmGenericModel alarmModelEntry.6.3 3015 alarmModelIndex 6 3016 alarmModelState 4 3017 alarmModelNotificationId 0.0 3018 alarmModelVarbindIndex 0 3019 alarmModelVarbindValue 0 3020 alarmModelDescription "Widget Temperature Severe" 3021 alarmModelSpecificPointer ituAlarmEntry.6.3 3022 alarmModelVarbindSubtree 0.0 3023 alarmModelResourcePrefix 0.0 3024 alarmModelRowStatus active (1) 3025 ituAlarmEventType environmentalAlarm (6) 3026 ituPerceivedSeverity critical (3) 3027 ituAlarmGenericModel alarmModelEntry.6.4 3029 6.4 Printer MIB Alarm Example 3031 Consider the following Notifications defined in the 3032 printer MIB [RFC1759]: 3034 prtAlertSeverityLevel OBJECT-TYPE 3035 -- This value is a type 1 enumeration 3036 SYNTAX INTEGER { 3037 other(1), 3038 critical(3), 3039 warning(4) 3041 } 3042 MAX-ACCESS read-only 3043 STATUS current 3044 DESCRIPTION 3045 "The level of severity of this alert table entry. The printer 3046 determines the severity level assigned to each entry into the 3047 table." 3048 ::= { prtAlertEntry 2 } 3050 printerV2Alert NOTIFICATION-TYPE 3051 OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, 3052 prtAlertGroupIndex, prtAlertLocation, prtAlertCode } 3053 STATUS current 3054 DESCRIPTION 3055 "This trap is sent whenever a critical event is added to the 3056 prtAlertTable." 3057 ::= { printerV2AlertPrefix 1 } 3059 These Notifications can be used to model a printer alarm as 3060 follows: 3062 alarmModelIndex 9 3063 alarmModelState 1 3064 alarmModelNotificationId alarmClearState 3065 alarmModelVarbindIndex 0 3066 alarmModelVarbindValue 0 3067 alarmModelDescription "Printer Alarm" 3068 alarmModelSpecificPointer 0.0 3069 alarmModelVarbindSubtree prtAlertGroup 3070 alarmModelResourcePrefix 0.0 3071 alarmModelRowStatus active (1) 3073 alarmModelIndex 9 3074 alarmModelState 2 3075 alarmModelNotificationId printerV2Alert 3076 alarmModelVarbindIndex 2 3077 alarmModelVarbindValue warning (4) 3078 alarmModelDescription "Printer Alarm" 3079 alarmModelSpecificPointer 0.0 3080 alarmModelVarbindSubtree prtAlertGroup 3081 alarmModelResourcePrefix 0.0 3082 alarmModelRowStatus active (1) 3084 alarmModelIndex 9 3085 alarmModelState 3 3086 alarmModelNotificationId printerV2Alert 3087 alarmModelVarbindIndex 2 3088 alarmModelVarbindValue other (1) 3089 alarmModelDescription "Printer Alarm - unknown severity" 3090 alarmModelSpecificPointer 0.0 3091 alarmModelVarbindSubtree prtAlertGroup 3092 alarmModelResourcePrefix 0.0 3093 alarmModelRowStatus active (1) 3095 alarmModelIndex 9 3096 alarmModelState 4 3097 alarmModelNotificationId printerV2Alert 3098 alarmModelVarbindIndex 2 3099 alarmModelVarbindValue critical (3) 3100 alarmModelDescription "Printer Alarm" 3101 alarmModelSpecificPointer 0.0 3102 alarmModelVarbindSubtree prtAlertGroup 3103 alarmModelResourcePrefix 0.0 3104 alarmModelRowStatus active (1) 3106 6.5 RMON Alarm Example 3108 The RMON MIB [RFC2819] defines a mechanism for generating 3109 threshold alarms. When the thresholds are crossed, 3110 RisingAlarm and FallingAlarm Notifications are 3111 generated as appropriate. These Notifications can 3112 be used to model an upper threshold alarm as follows: 3114 alarmModelIndex 6 3115 alarmModelState 1 3116 alarmModelNotificationId FallingAlarm 3117 alarmModelVarbindIndex 0 3118 alarmModelVarbindValue 0 3119 alarmModelDescription "RMON Rising Clear Alarm" 3120 alarmModelSpecificPointer 0.0 3121 alarmModelVarbindSubtree alarmIndex 3122 alarmModelResourcePrefix 0.0 3123 alarmModelRowStatus active (1) 3125 alarmModelIndex 6 3126 alarmModelState 2 3127 alarmModelNotificationId RisingAlarm 3128 alarmModelVarbindIndex 0 3129 alarmModelVarbindValue 0 3130 alarmModelDescription "RMON Rising Alarm" 3131 alarmModelSpecificPointer 0.0 3132 alarmModelVarbindSubtree alarmIndex 3133 alarmModelResourcePrefix 0.0 3134 alarmModelRowStatus active (1) 3136 6.6 The Lifetime of an Alarm 3138 The following example demonstrates the relationship between 3139 the active alarm table, the clear alarm table and the 3140 Notification Log MIB. 3142 Consider a system with alarms modelled as in example 1 and which 3143 also supports the informational Notification dsx3LineStatusChange. 3145 dsx3LineStatusChange NOTIFICATION-TYPE 3146 OBJECTS { dsx3LineStatus, 3147 dsx3LineStatusLastChange } 3148 STATUS current 3149 DESCRIPTION 3150 "A dsx3LineStatusChange trap is sent when the 3151 value of an instance of dsx3LineStatus changes. It 3152 can be utilized by an NMS to trigger polls. When 3153 the line status change results in a lower level 3154 line status change (i.e. ds1), then no traps for 3155 the lower level are sent." 3156 ::= { ds3Traps 0 1 } 3158 0. At system start, the active alarm table, alarm clear table and 3159 the Notification Log are all empty. 3160 ___________________________ _______________________ 3161 | alarmActiveTable | | nlmLogTable | 3162 |---------------------------| |-----------------------| 3163 | alarmActiveIndex | alarm | | nlmLogPointer | notif.| 3164 |---------------------------| |-----------------------| 3165 |___________________________| |_______________________| 3167 __________________________________________________ 3168 | alarmClearTable | 3169 |--------------------------------------------------| 3170 | alarmClear Index | alarm | 3171 |--------------------------------------------------| 3172 | | | 3173 |__________________________________________________| 3175 1. Some time later, a link goes down generating a linkDown 3176 Notification, which is sent out and logged in the 3177 Notification Log. As this Notification is modelled as 3178 an alarm state, an entry is added to the active alarm 3179 table. 3180 __________________________________________________ 3181 | alarmActiveTable | 3182 |--------------------------------------------------| 3183 | alarmActiveIndex | alarm | 3184 |--------------------------------------------------| 3185 | 1 | link down - problem confirmed | 3186 |__________________________________________________| 3188 _______________________________________________ 3189 | nlmLogTable | 3190 |-----------------------------------------------| 3191 | nlmLogPointer | Notification | 3192 |-----------------------------------------------| 3193 | 1 | linkdown | 3194 |_______________________________________________| 3196 __________________________________________________ 3197 | alarmClearTable | 3198 |--------------------------------------------------| 3199 | alarmClear Index | alarm | 3200 |--------------------------------------------------| 3201 | | | 3202 |__________________________________________________| 3204 2. Some time later, the value of an instance of dsx3LineStatus 3205 changes. This Notification is sent out and logged. As this 3206 is not modelled into an alarm state, the active alarm table 3207 remains unchanged. 3208 __________________________________________________ 3209 | alarmActiveTable | 3210 |--------------------------------------------------| 3211 | alarmActiveIndex | alarm | 3212 |--------------------------------------------------| 3213 | 1 | linkDown - problem confirmed | 3214 |__________________________________________________| 3216 _____________________________________________ 3217 | nlmLogTable | 3218 |---------------------------------------------| 3219 | nlmLogPointer | Notification | 3220 |---------------------------------------------| 3221 | 1 | linkDown | 3222 | 2 | dsx3LineStatusChange | 3223 |_____________________________________________| 3225 __________________________________________________ 3226 | alarmClearTable | 3227 |--------------------------------------------------| 3228 | alarmClear Index | alarm | 3229 |--------------------------------------------------| 3230 | | | 3231 |__________________________________________________| 3233 3. Some time later, the link goes back up. A linkUp Notification 3234 is sent out and logged. As this Notification models 3235 the clear alarm for this alarm, the alarm entry is remove 3236 from the active alarm table. An entry is added to the 3237 clear alarm table. 3238 __________________________________________________ 3239 | alarmActiveTable | 3240 |--------------------------------------------------| 3241 | alarmActiveIndex | alarm | 3242 |--------------------------------------------------| 3243 |__________________________________________________| 3245 _____________________________________________ 3246 | nlmLogTable | 3247 |---------------------------------------------| 3248 | nlmLogPointer | Notification | 3249 |---------------------------------------------| 3250 | 1 | linkDown | 3251 | 2 | dsx3LineStatusChange | 3252 | 3 | linkUp | 3253 |_____________________________________________| 3255 __________________________________________________ 3256 | alarmClearTable | 3257 |--------------------------------------------------| 3258 | alarmClear Index | alarm | 3259 |--------------------------------------------------| 3260 | 1 | linkDown - confirmed problem | 3261 |__________________________________________________| 3263 7. Security Considerations 3265 There are a number of management objects defined in this MIB module 3266 with a MAX-ACCESS clause of read-write and/or read-create. Such 3267 objects may be considered sensitive or vulnerable in some network 3268 environments. The support for SET operations in a non-secure 3269 environment without proper protection can have a negative effect on 3270 network operations. 3272 The following objects are defined with a MAX-ACCESS clause of 3273 read-write or read-create: alarmModelNotificationId, 3274 alarmModelVarbindIndex, alarmModelVarbindValue, 3275 alarmModelDescription, alarmModelSpecificPointer, 3276 alarmModelVarbindSubtree, alarmModelResourcePrefix, 3277 alarmModelRowStatus, alarmClearMaximum, ituAlarmEventType, 3278 ituAlarmProbableCause, ituAlarmAdditionalText, and 3279 ituAlarmGenericModel. 3281 Note that setting the value of alarmClearMaximum too low may result 3282 in security related alarms history being prematurely lost. 3284 Changing values of alarmModelRowStatus as part of creating and 3285 deleting rows in the alarmModelTable result in adding new alarm 3286 models to the system or taking them out respectively. These 3287 operations need to be carefully planned. Adding a new model should 3288 be made in a consistent manner to avoid the system overflow with 3289 alarms. Taking out a model should result in the deletion of all this 3290 model's related alarms in the system. 3292 SNMP versions prior to SNMPv3 did not include adequate security. 3293 Even if the network itself is secure (for example by using IPSec), 3294 even then, there is no control as to who on the secure network is 3295 allowed to access and GET/SET (read/change/create/delete) the 3296 objects in this MIB module. 3298 It is RECOMMENDED that implementers consider the security features 3299 as provided by the SNMPv3 framework (see [RFC3410], section 8), 3300 including full support for the SNMPv3 cryptographic mechanisms (for 3301 authentication and privacy). 3303 Further, deployment of SNMP versions prior to SNMPv3 is NOT 3304 RECOMMENDED. Instead, it is RECOMMENDED to deploy SNMPv3 and to 3305 enable cryptographic security. It is then a customer/operator 3306 responsibility to ensure that the SNMP entity giving access to an 3307 instance of this MIB module is properly configured to give access to 3308 the objects only to those principals (users) that have legitimate 3309 rights to indeed GET or SET (change/create/delete) them. 3311 Note that the alarm throttling mechanism associated with the 3312 alarmActiveState and alarmActiveClear notifications only applies to 3313 a given alarm. Defining multiple alarms from the same internal 3314 stimulus may then still result in a flood of alarms into the network. 3316 Although the use of community strings in SNMPv1 is not considered an 3317 effective means of providing security, security administrators 3318 SHOULD consider whether the fact that alarmActiveContextName can 3319 reveal community string values would make this object sensitive in 3320 their environment. 3322 This MIB module can provide access to information that may also be 3323 accessed through manipulation of the SNMP-NOTIFICATION-MIB and the 3324 NOTIFICATION-LOG-MIB. This is expressed in part through the common 3325 indexing structure of nlmLogName [RFC3014], 3326 snmpNotifyFilterProfileName [RFC3413], and alarmListName. 3327 Consequently, it is RECOMMENDED that security administrators take 3328 care to configure a coherent VACM security policy. The objects 3329 alarmActiveLogPointer, alarmActiveModelPointer, 3330 alarmActiveSpecificPointer, and alarmClearModelPointer are object 3331 identifiers that reference information to which a particular user 3332 might not be given direct access. The structure of these object 3333 identifiers does not permit the extraction of any sensitive 3334 information. Two other objects, alarmClearResourceId, and 3335 alarmActiveResourceId, are also syntactically object identifiers, 3336 but their structure could provide a user with potentially useful 3337 information to which he or she might not otherwise be granted 3338 access, such as the existence of a particular resource. 3340 For further discussion of security, see section 3.4. 3342 8. Authors' Addresses 3344 Sharon Chisholm 3345 Nortel Networks 3346 PO Box 3511, Station C 3347 Ottawa, Ontario, K1Y 4H7 3348 Canada 3349 Email: schishol@nortelnetworks.com 3351 Dan Romascanu 3352 Avaya 3353 Atidim Technology Park, Bldg. #3 3354 Tel Aviv, 61131 3355 Israel 3356 Tel: +972-3-645-8414 3357 Email: dromasca@avaya.com 3359 9. Acknowledgements 3361 This document is a product of the DISMAN Working Group. 3363 10. Intellectual Property 3365 The IETF takes no position regarding the validity or scope of any 3366 intellectual property or other rights that might be claimed to pertain 3367 to the implementation or use of the technology described in this 3368 document or the extent to which any license under such rights might or 3369 might not be available; neither does it represent that it has made any 3370 effort to identify any such rights. Information on the IETF's 3371 procedures with respect to rights in standards-track and 3372 standards-related documentation can be found in RFC 2028. Copies of 3373 claims of rights made available for publication and any assurances of 3374 licenses to be made available, or the result of an attempt made to 3375 obtain a general license or permission for the use of such proprietary 3376 rights by implementors or users of this specification can be obtained 3377 from the IETF Secretariat. 3379 The IETF invites any interested party to bring to its attention any 3380 copyrights, patents or patent applications, or other proprietary rights 3381 which may cover technology that may be required to practice this 3382 standard. Please address the information to the IETF Executive 3383 Director. 3385 The IETF has been notified of intellectual property rights claimed in 3386 regard to some or all of the specification contained in this document. 3388 For more information consult the online list of claimed rights. 3390 11. References 3392 11.1 Normative References 3394 [M.3100] ITU Recommendation M.3100, "Generic Network Information 3395 Model", 1995 3397 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 3398 "Simple Network Management Protocol", STD 15, RFC 1157, 3399 May 1990. 3401 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 3402 SNMP", RFC 1215, March 1991. 3404 [RFC2026] Bradner, S., "The Internet Standards Process -- 3405 Revision 3", RFC 2026, 1996 3407 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3408 Requirement Levels", BCP 14, RFC 2119, March 1997. 3410 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3411 Rose, M., and S. Waldbusser, "Structure of Management 3412 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3413 1999. 3415 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3416 Rose, M., and S. Waldbusser, "Textual Conventions for 3417 SMIv2", STD 58, RFC 2579, April 1999. 3419 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3420 Rose, M., and S. Waldbusser, "Conformance Statements for 3421 SMIv2", STD 58, RFC 2580, April 1999 3423 [RFC3291] Daniele, M., Haberman, B., Routhier, S., Schoenwaelder, 3424 J., "Textual Conventions for Internet Network Addresses", 3425 May 2002. 3427 [RFC3411] Harrington, D., Presuhn, R., Wijnen, B., "An Architecture 3428 for Describing Simple Network Management Protocol (SNMP) 3429 Management Frameworks", RFC3411, December 2002. 3431 [RFC3413] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3432 Applications", RFC 3414, December 2002. 3434 [RFC3415] Wijnen, B., Presuhn, R., McCloghrie K., "View-based Access 3435 Control Model (VACM) for the Simple Network Management 3436 Protocol (SNMP)", RFC3415, December 2002 3438 [RFC3416] Presuhn, R., Ed.., "Version 2 of the Protocol Operations 3439 for the Simple Network Management Protocol (SNMP).", 3440 RFC 3416, December 2002. 3442 [RFC3584] Frye, R., Levi, D., Routhier, S., Wijnen, B., 3443 "Coexistence between Version 1, Version 2, and Version 3 3444 of the Internet-standard Network Management Framework.", 3445 RFC3584, August 2003 3447 [X.733] ITU Recommendation X.733, "Information Technology - Open 3448 Systems Interconnection - System Management: Alarm 3449 Reporting Function", 1992 3451 [X.736] ITU Recommendation X.736, "Information Technology - Open 3452 Systems Interconnection - System Management: Security 3453 Alarm Reporting Function", 1992 3455 11.2 Informative References 3457 [RFC1657] Willis, S., Burruss, J., Chu, J., "Definitions of 3458 Managed Objects for the Fourth Version of the 3459 Border Gateway Protocol (BGP-4) using SMIv2", RFC 1657, 3460 1994 3462 [RFC1759] Smith, R., Wright, F., Hastings, T., Zilles, S., 3463 Gullenskop, J., "Printer MIB", RFC 1759, March 1995 3465 [RFC2737] McCloghrie, K., Brierman, A., "Entity MIB using SMIv2", 3466 RFC2737, December 1999 3468 [RFC2788] Freed, N., Kille, S., "Network Services Monitoring MIB", 3469 RFC2788, March 2000 3471 [RFC2819] Waldbusser, S. "Remote Network Monitoring Management 3472 Information Base", RFC 2819, May 2000 3474 [RFC2863] McCloghrie, K., Kastenholz, F., "The Interfaces Group 3475 MIB using SMIv2", RFC2863, June 2000 3477 [RFC2981] Kavasseri, R., Stewart, B., "Event MIB", RFC2981, 3478 October 2000 3480 [RFC3014] Stewart, B., Kavasseri, R., "Notification Log MIB, 3481 RFC 3014, November 2000 3483 [RFC3410] Case, J., Mundy, R., Partain, D. and B. Stewart, 3484 "Introduction and Applicability Statements for Internet- 3485 Standard Management Framework", RFC 3410, December 2002 3487 [RFC3418] Presuhn, R., "Management Information Base (MIB) for the 3488 Simple Network Management Protocol (SNMP)". RFC 3418, 3489 2002 3491 12. Full Copyright Statement 3493 Copyright (C) The Internet Society (2004). All Rights Reserved. 3495 This document and translations of it may be copied and furnished to 3496 others, and derivative works that comment on or otherwise explain it 3497 or assist in its implementation may be prepared, copied, published 3498 and distributed, in whole or in part, without restriction of any kind, 3499 provided that the above copyright notice and this paragraph are 3500 included on all such copies and derivative works. However, this 3501 document itself may not be modified in any way, such as by removing 3502 the copyright notice or references to the Internet Society or other 3503 Internet organizations, except as needed for the purpose of 3504 developing Internet standards in which case the procedures for 3505 copyrights defined in the Internet Standards process must be followed, 3506 or as required to translate it into languages other than English. 3508 The limited permissions granted above are perpetual and will not be 3509 revoked by the Internet Society or its successors or assigns. 3511 This document and the information contained herein is provided on an 3512 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3513 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3514 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 3515 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3516 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.