idnits 2.17.1 draft-ietf-disman-alarm-mib-09.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? == The page length should not exceed 58 lines per page, but there was 2 longer pages, the longest (page 21) being 59 lines Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** There are 19 instances of lines with control characters in the document. == 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 2541 has weird spacing: '...ication mor...' == Line 3148 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 (September 2002) is 7895 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) == Missing Reference: 'RFC2576' is mentioned on line 1192, but not defined ** Obsolete undefined reference: RFC 2576 (Obsoleted by RFC 3584) == Unused Reference: 'RFC2119' is defined on line 3065, but no explicit reference was found in the text == Unused Reference: 'RFC2037' is defined on line 3121, but no explicit reference was found in the text == Unused Reference: 'RFC2233' is defined on line 3124, but no explicit reference was found in the text == Unused Reference: 'RFC2788' is defined on line 3127, 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 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) -- Obsolete informational reference (is this intentional?): RFC 1759 (Obsoleted by RFC 3805) -- Obsolete informational reference (is this intentional?): RFC 2037 (Obsoleted by RFC 2737) -- Obsolete informational reference (is this intentional?): RFC 2233 (Obsoleted by RFC 2863) Summary: 15 errors (**), 0 flaws (~~), 11 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-09.txt D. Romascanu 4 Category: Standards Track Avaya Inc 5 Expiration Date: March 2003 September 2002 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 The IETF has been notified of potential intellectual property 15 rights in regard to some or all of the specification contained 16 in this document. For more information consult the online list 17 of notices. 19 Internet-Drafts are working documents of the Internet Engineering 20 Task Force (IETF), its areas, and its working groups. Note that 21 other groups may also distribute working documents as 22 Internet-Drafts. 24 Internet-Drafts are draft documents valid for a maximum of six 25 months and may be updated, replaced, or obsoleted by other 26 documents at any time. It is inappropriate to use Internet- 27 Drafts as reference material or to cite them other than as 28 "work in progress." 30 The list of current Internet-Drafts can be accessed at 32 http://www.ietf.org/ietf/1id-abstracts.txt 34 The list of Internet-Draft Shadow Directories can be accessed at 35 http://www.ietf.org/shadow.html. 37 Copyright Notice 39 Copyright (C) The Internet Society (2002). All Rights Reserved. 41 Abstract 43 This memo defines a portion of the Management Information Base (MIB) 44 for use with network management protocols in the Internet community. 45 In particular, it describes management objects used for modelling 46 and storing alarms. 48 Table of Contents 50 1. The SNMP Management Framework 51 2. Introduction 52 3. Alarm Management Framework 53 3.1. Terminology 54 3.2. Alarm Management Architecture 55 3.3. Features of this Architecture 56 3.4. Security 57 3.5. Relationship between Alarm and Notifications 58 3.6. Notification Varbind Storage and Reference 59 3.7. Relation to Notification Log MIB 60 3.8. Relation to Event MIB 61 4. Generic Alarm MIB 62 4.1. Overview 63 4.2. Definitions 64 5. ITU Alarm 65 5.1. Overview 66 5.2. IANA Considerations 67 5.3. Textual Conventions 68 5.4. Definitions 69 6. Examples 70 6.1. Alarms Based on linkUp/linkDown Notifications 71 6.2. Temperature Alarm using generic Notifications 72 6.3. Temperature Alarm without Notifications 73 6.4. Printer MIB Alarm Example 74 6.5. Rmon Alarm Example 75 6.6. The Lifetime of an Alarm 76 7. Security Considerations 77 8. Authors' Addresses 78 9. Acknowledgements 79 10. References 80 11. Full Copyright Statement 81 1. The SNMP Management Framework 83 The SNMP Management Framework presently consists of five major 84 components: 86 o An overall architecture, described in RFC 2571 [RFC2571]. 88 o Mechanisms for describing and naming objects and events for the 89 purpose of management. The first version of this Structure of 90 Management Information (SMI) is called SMIv1 and described in 91 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 92 1215 [RFC1215]. The second version, called SMIv2, is described 93 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 94 STD 58, RFC 2580 [RFC2580]. 96 o Message protocols for transferring management information. The 97 first version of the SNMP message protocol is called SNMPv1 and 98 described in STD 15, RFC 1157 [RFC1157]. A second version of 99 the SNMP message protocol, which is not an Internet standards 100 track protocol, is called SNMPv2c and described in RFC 1901 101 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 102 message protocol is called SNMPv3 and described in RFC 1906 103 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 105 o Protocol operations for accessing management information. The 106 first set of protocol operations and associated PDU formats is 107 described in STD 15, RFC 1157 [RFC1157]. A second set of 108 protocol operations and associated PDU formats is described in 109 RFC 1905 [RFC1905]. 111 o A set of fundamental applications described in RFC 2573 112 [RFC2573] and the view-based access control mechanism described 113 in RFC 2575 [RFC2575]. 115 A more detailed introduction to the current SNMP Management Framework 116 can be found in RFC 2570 [RFC2570]. 118 Managed objects are accessed via a virtual information store, termed 119 the Management Information Base or MIB. Objects in the MIB are 120 defined using the mechanisms defined in the SMI. 122 This memo specifies a MIB module that is compliant to the SMIv2. A 123 MIB conforming to the SMIv1 can be produced through the appropriate 124 translations. The resulting translated MIB must be semantically 125 equivalent, except where objects or events are omitted because no 126 translation is possible (use of Counter64). Some machine readable 127 information in SMIv2 will be converted into textual descriptions in 128 SMIv1 during the translation process. However, this loss of machine 129 readable information is not considered to change the semantics of the 130 MIB. 132 2. Introduction 134 In traditional SNMP management, problems are detected on an entity 135 either through polling interesting MIB variables, waiting for the 136 entity to send a Notification for a problem, or some combination of 137 the two. This method is somewhat successful, but experience has 138 shown some problems with this approach. Managers monitoring large 139 number of entities cannot afford to be polling large numbers of 140 objects on each device. Managers trying to ensure high-reliability 141 are unable to accurately determine problems that may have occurred 142 when they were not monitoring an entity. Finally, it can be time 143 consuming for managers to try to understand the relationships 144 between the various objects they poll, the Notifications they 145 receive and the problems occurring on the entity and even after 146 detailed analysis they may still be left with an incomplete picture 147 of what problems are occurring. But, it is important for an operator 148 to be able to determine current problems on a system, so they can be 149 fixed. 151 This memo describes a method of using alarm management in SNMP to 152 address these problems. It also provides the necessary MIB objects 153 to support these methods. 155 Alarms and other terms related to alarms management are defined in 156 the following sections. 158 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 159 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 160 document are to be interpreted as described in RFC 2119. 162 3. Alarm Management Framework 164 3.1 Terminology 166 Error 167 A deviation of a system from normal operation. 169 Fault 170 Lasting error or warning condition. 172 Event 173 Something that happens which may be of interest to a management 174 station. A fault, a change in status, crossing a threshold, or an 175 external input to the system, for example. 177 Notification 178 Unsolicited transmissions of management information. 180 Alarm 181 Persistent indication of a fault. 183 Alarm State 184 A condition or stage in the existence of an alarm. As a minimum, 185 alarms states are raise and clear. They could also 186 include severity information such as defined by perceived severity 187 in the ITU model - cleared, indeterminate, critical, major, minor 188 and warning. 190 Alarm Raise 191 The initial detection of the fault indicated by an alarm or any 192 number of alarm states later entered, except clear. A Notification 193 SHOULD be sent on alarm raise. 195 Alarm Clear 196 The detection that the fault indicated by an alarm no longer 197 exists. A Notification SHOULD be sent on alarm clear. 199 Active Alarm 200 An alarm which has an alarm state that has been raised, but not 201 cleared. 203 Alarm Detection Point 204 The entity that detected the alarm. 206 Perceived Severity 207 The severity of the alarm as determined by the alarm detection 208 point using the information it has available. 210 3.2 Alarm Management Architecture 211 +------------------------------------------------+ 212 | | 213 | +------------------------------------+ | 214 | | Notification Management | | 215 | +--------------+---------------------+ | 216 | | | 217 +------------------+-----------------------------+ 218 | 219 V 220 | 221 |<----------------------------------------------+ 222 | | 223 +------------------V-------------+ | 224 | +---------------V-----------+ | | 225 | | RFC 2573 | | | 226 | | SNMP-NOTIFICATION-MIB | | | 227 | +--------+--------------+-+-+ | | 228 | | | | | | 229 | | | +------------------+ | 230 | | | | | | 231 | | | | +----------V--------------+ | 232 | | | | | +--------V---------+ | | 233 | +---------V------------+ | | | | Alarm Modelling | | | 234 | | RFC 3014 | | | | | (descriptions) | | | 235 | | NOTIFICATION-LOG-MIB | | | | +--------+---------+ | | 236 | +----------------------+ | | | | | | 237 | | | | +--------V------------+ | | 238 | +------------------------V-+ | | | Generic: Model- | | | 239 | | RFC 2573 | | | | Active : Specific | | | 240 | | SNMP-TARGET-MIB | | | | Alarms : Extensions | | | 241 | +----------+---------------+ | | +--------+------------+ | | 242 | | | | | | | 243 +------------|-------------------+ +----------|--------------+ | 244 | | | 245 | +------------------+ 246 V 247 Informs & Traps 249 3.3 Features of this Architecture 251 3.3.1 Modular Alarm Architecture 253 The subject of alarm management can potentially cover a large number 254 of topics including real-time alarms, historical alarms, alarm 255 correlation, and alarm suppression, to name a few. Within each of 256 these topics, there are a number of established models that could be 257 supported. This memo focuses on a subset of this problem space, but 258 describes a modular SNMP alarm management framework. 260 The framework defines a generic Alarm MIB that can be supported on 261 its own, or with additional alarm modelling information such as the 262 provided ITU Alarm MIB. In addition, the active alarm tables could 263 also be extended to support additional information about active 264 alarm instances. This framework can also be expanded in the future 265 to support such features as alarm correlation and alarm suppression. 266 This modular architecture means that the cost of supporting alarm 267 management features is proportional to the number of features an 268 implementation supports. 270 3.3.2 Flexible Alarm Modeling 272 Alarm models document an understanding between a manager and an 273 agent as to what problems will be reported on a system, how these 274 problems will be reported, and what might possibly happen over the 275 lifetime of this problem. 277 The alarm modelling method provided in this memo provides 278 flexibility to support implementations with different modelling 279 requirements. All alarms are modelled as a series of states that are 280 related together using an alarm ID. Alarm states can be modelled 281 using traditional Notifications, generic alarm Notifications, or 282 without the use of Notifications. 284 Alarm states modelled using traditional Notifications would identify 285 a Notification OID, and optionally an offset, value pair of one of 286 the Notification varbinds to define the state. This alarm state 287 would be entered when the entity generated a Notification that 288 matched this information and the alarm would be added to the active 289 alarm table. This Notification would also get sent on the wire to 290 any destinations, as indicated in the SNMP-TARGET-MIB [RFC2573]. 292 Alarm states modelled using generic Notifications, use the 293 alarmActiveState or alarmClearState Notifications defined in this 294 memo. These alarm states would be entered by some internal stimuli, 295 the alarm would be added to the active alarm table and these generic 296 Notifications would then be sent on the wire to any destinations, as 297 indicated in the SNMP-TARGET-MIB [RFC2573]. 299 Alarm states modelled without any Notifications would be triggered 300 by some internal stimuli, the alarm would be added to the active 301 alarm table, but no Notifications would be sent to interested 302 managers. 304 3.3.3 Problem Indication 306 The Alarm MIB provides a means to tell what Notifications are just 307 informational events or not of interest to the manager for other 308 reasons by not including them in any alarm models. In addition, 309 information in the alarm model, such as the Notification ID and the 310 description tell exactly what error or warning condition this alarm 311 is indicating. If the ITU-ALARM-MIB is also supported, additional 312 information is provided via the probable cause. 314 3.3.5 Identifying Resource under Alarm 316 An important goal of alarm management is to ensure that any detected 317 problems get fixed, so it is necessary to know exactly where this 318 problem is occurring. In addition, it is necessary to be able to 319 tell when alarm instances are raised against the same component, as 320 well as to be able to tell what instance of an alarm is cleared by 321 an instance of an alarm clear. 323 This MIB provides a generic method for identifying the resource by 324 extracting and building a resource ID from the Notification 325 varbinds. Solutions interested in being able to differentiate the 326 source of the alarm by means other than the source IP address and 327 resource ID should create separate alarm lists such that each 328 context/source IP address pair is its own list. 330 3.3.6 Means of obtaining ITU alarm information 332 Alarm Information, as defined in ITU alarm models [M.3100], is 333 optionally available to implementations through the optional support 334 of the ITU-ALARM-MIB. 336 3.3.7 Configuration of Alarm Models 338 An alarm model can be added, updated or removed during runtime, 339 assuming it is not being referenced by any active alarm instance. 341 3.3.8 Active Alarm Management 343 A list of currently active alarms on a system and supporting 344 statistics on the SNMP entity can be obtained. 346 This allows the network management station to find out about any 347 problems that may have occurred before it started managing a 348 particular network element, or while it was out of contact with it. 350 3.3.9 Distributed Alarm Management 352 All aspects of the Alarm MIB can be supported both on the device 353 experiencing the alarms and on any middle managers that might be 354 monitoring such devices. 356 3.3.10 Historical Alarm Management 358 Some systems may have a requirement that information on alarms that 359 are no longer active is available. This memo provides a clear table 360 to support this requirement. 362 This can also be achieved through the support of the Notification 363 log MIB [RFC3014] to store alarm state transitions. 365 3.4 Security 367 Security for alarms is awkward since access control for the objects 368 in the underlying Notifications can be checked only where the 369 Notification is created. Thus such checking is possible only for 370 locally generated Notifications, and even then only when security 371 credentials are available. 373 For the purpose of this discussion, "security credentials" means the 374 input values for the abstract service interface function 375 isAccessAllowed [RFC2571] and using those credentials means 376 conceptually using that function to see that those credentials allow 377 access to the MIB objects in question, operating as for a 378 Notification Originator in [RFC2573]. 380 The Alarm MIB has the notion of a named alarm list. By using alarm 381 list names and view-based access control [RFC2575] a network 382 administrator can provide different access for different users. When 383 an application creates an alarm model (indexed in part by the alarm 384 list name) the security credentials of the creator remain associated 385 with that alarm model and constrain what information is allowed to 386 be placed in the active alarm table, the active alarm variable 387 table, the cleared alarm table, and the ITU alarm table. 389 When processing locally-generated Notifications, the managed system 390 MUST use the security credentials associated with each alarm model 391 respectively, and MUST apply the same access control rules as 392 described for a Notification Originator in [RFC2573]. 394 The managed system SHOULD NOT apply access control when processing 395 remotely-generated Notifications using the alarm models. In those 396 cases the security of the information in the alarm tables SHOULD be 397 left to the normal, overall access control for those tables. 399 3.5 Relationship between Alarm and Notifications 401 It is important to understand the relationship between alarms and 402 Notifications, as both are traditional fault management methods. 403 This relationship is modelled using the alarmModelTable to define 404 the alarmModelNotificationId for each alarm state. 406 Not all Notifications signal an alarm state transition. Some 407 Notifications are simply informational in nature, such as those that 408 indicate that a configuration operation has been performed on an 409 entity. These sorts of Notifications would not be represented in 410 the Alarm MIB. 412 The Alarm MIB allows the use of the Notification space as defined in 413 [RFC2578] in order to identify the Notifications that are related 414 with the specific alarm state transitions. However there is no 415 assumption that the respective Notifications MUST be sent for all or 416 any of the alarm state transitions. It is also possible to model 417 alarms using no Notifications at all. This architecture allows for 418 both the efficient exploitation of the body of defined Notification 419 and for the use of non-Notification based systems. 421 3.6 Notification Varbind Storage and Reference 423 In SNMPv1, the varbinds in the Trap-PDU sent over the wire map one 424 to one into those varbinds listed in the SMI of the trap in the MIB 425 in which it was defined. In the case of linkDown trap, the first 426 varbind can unambiguously be identified as ifIndex. With the 427 introduction of the InformRequest-PDU and SNMPv2-Trap-PDU types, 428 which send sysUptime and snmpTrapOID as the first two varbinds, 429 while the SMI in the MIB where the Notification is defined only 430 lists additional varbinds, the meaning of "first varbind" becomes 431 less clear. In the case of the linkDown Notification, referring to 432 the first varbind could potentially be interpreted as either the 433 sysUptime or ifIndex. 435 The varbind storage approach taken in the Alarm MIB is that 436 sysUptime and snmpTrapOID shall always be stored in the active alarm 437 variable table as entry 1 and 2 respectively, regardless of whether 438 the transport was the Trap-PDU, the InformRequest-PDU or the 439 SNMPv2-Trap-PDU. If the incoming Notification is an SNMPv1 Trap-PDU 440 then an appropriate value for sysUpTime.0 or snmpTrapOID.0 shall be 441 determined by using the rules in section 3.1 of [RFC2576]. 443 The varbind reference approach taken in the Alarm MIB is that, for 444 variables such as the alarmModelVarbindIndex, the first two 445 obligatory varbinds of the InformRequest-PDU and SNMPv2-Trap-PDU are 446 ignored, and the index aligns with the Trap-PDU and the SMI. In the 447 case of linkDown, the first varbind would always be ifIndex. 449 3.7 Relation to Notification Log MIB 451 The Alarm MIB is intended to complement the Notification Log 452 MIB[RFC3014], but can be used independently. The alarmActiveTable 453 is defined in manner similar to that of the nlmLogTable. This 454 format allows for the storage of any Trap or Notification that can 455 be defined using SMIv1 or SMIv2. Using the same format as the 456 Notification log MIB also simplifies operations for systems choosing 457 to implement both MIBs. 459 The object alarmActiveLogPointer points, for each entry in the 460 alarmActiveLogTable, to the log index in the Notification log MIB, 461 if used. 463 If the Notification log MIB is supported, it can be monitored by a 464 management system as a hedge against lost alarms. The Notification 465 log can also be used to support historical alarm management. 467 3.8 Relationship with the Event MIB 469 During the work and discussions in the Working Group, the issue of 470 the relationship between the MIB modules and the Event MIB [RFC2981] 471 was raised. There is no direct relation or dependency between the 472 Alarm MIB and the Event MIB. Some common terms (like 'event') are 473 being used in both MIB modules, and the user is directed to the 474 sections that define terminology in the two documents for 475 clarification. 477 4. Generic Alarm MIB 479 4.1 Overview 481 The ALARM-MIB consists of alarm models and lists of active and 482 cleared alarms. 484 The alarmModelTable contains information that is applicable to all 485 instances of an alarm. It can be populated at start-up with all 486 alarms that could happen on a system or later configured by a 487 management application. It contains all the alarms for a given 488 system. If a Notification is not represented in the 489 alarmModelTable, it is not an alarm state transition. The 490 alarmModelTable provides a means of defining the raise/clear and 491 other state transition relationship between alarm states. 492 alarmModelIndex acts as a unique identifier for an alarm. An alarm 493 model consists of defining the possible states an alarm can assume 494 as well as the OID of the Notification that is sent out when an 495 alarm changes state. The object alarmModelState defines the states 496 of an alarm. 498 The alarmActiveTable contains a list of alarms that are currently 499 occurring on a system. It is intended that this table be queried 500 upon device discovery and rediscovery to determine which alarms are 501 currently active on the device. 503 The alarmActiveVariableTable contains the Notification variable 504 bindings associated with the alarms in the alarmActiveTable. 506 The alarmActiveStatsTable contains current and total raised alarm 507 counts as well as the time of the last alarm raise and alarm clears 508 per named alarm list. 510 The alarmClearTable contains recently cleared alarms. It contains up 511 to alarmClearMaximum cleared alarms. 513 The MIB also defines generic alarm Notifications that can be used 514 when there is not an existing applicable Notification to signal the 515 alarm state transition - alarmActiveState and alarmClearState. 517 4.1.1 Extensibility 519 The relationship between the Alarm MIB and the other alarm model MIB 520 modules is expressed by the following: The alarmModelTable has a 521 corresponding table in the specific MIB. For each row in the 522 specific MIB alarm model table there is one row in the 523 alarmModelTable. The alarmActiveTable has a corresponding table in 524 the specific MIBs. For each row in the specific MIB active alarm 525 table, there is one row in the alarmActiveTable. The 526 alarmModelSpecificPointer object in the alarmModelTable points to 527 the specific model entry in an extended alarm model table 528 corresponding to this particular alarm. The 529 alarmActiveSpecificPointer object in the alarmActiveTable points to 530 the specific active alarm entry in an extended active alarm table 531 corresponding to this particular alarm instance. 533 4.1.2 Problem Indication 535 The problem that each alarm indicates is identified through the OID 536 of the NotificationId of the state transition, and, optionally, the 537 ITU parameters. alarmModelDescription provides a description of the 538 alarm state suitable for displaying to an operator. 540 4.1.3 Alarm State Transition Notification 542 Managers interested in receiving a Notification when an alarm 543 changes state can associate a Notification with an alarm state 544 change. Alarm state transitions can use existing Notifications or 545 can use the generic Notifications and alarmActiveState and 546 alarmClearState. If the implementation chooses not to alert the 547 management station, then a value of 0.0 can be used for 548 alarmModelNotificationId. Alternatively, a Notification can be 549 defined in alarmModelNotificationId and no hosts specified in the 550 SNMP-TARGET-MIB [RFC2573]. 552 Alarms are modelled by defining all possible states in the 553 alarmModelTable, as well as defining alarmModelNotificationId, 554 alarmModelVarbindIndex, and alarmModelVarbindValue for each of the 555 possible alarm states. Optionally, ituAlarmPerceivedSeverity models 556 the states in terms of ITU perceived severity. 558 4.1.4 Active Alarm Resource Identifier 560 Resources under alarm can be identified using the 561 alarmActiveResourceId. This OBJECT IDENTIFIER points to an 562 appropriate object to identify the given resource, depending on the 563 type of the resource. 565 The consumer of the alarmActiveResourceId does not necessarily need 566 to know the type of the resource in the resource ID, but if they 567 want to know this, examining the content of the resource ID can 568 derive it - 1.3.6.1.2.1.2.2.1.1.something is an interface for 569 example. It is therefore good practice to use resource IDs that can 570 be consistently used across technologies such as ifIndex, 571 entPhysicalIndex or sysApplRunIndex to minimize the number of 572 resource prefixes a manager interested in resource type needs to 573 learn. 575 Resource ID can be calculated using the alarmModelResourcePrefix, 576 alarmModelVarbindSubtree and the Notification varbinds. This allows 577 for both the managed element to be able to compute and populate the 578 alarmActiveResourceId object and for the manager to be able to 579 determine when two separate alarm instances are referring to the 580 same resource. 582 If alarmModelResourcePrefix has a value of 0.0, then 583 alarmActiveResourceId is simply the variable identifier of the first 584 Notification varbind that matches the prefix defined in 585 alarmModelVarbindSubtree. Otherwise, alarmActiveResourceId is 586 calculated by appending the instance information from the first 587 Notification varbind that matches alarmModelVarbindSubtree to the 588 prefix defined in alarmModelResourcePrefix. The instance information 589 is the portion of the variable identifier following the part that 590 matched alarmModelVarbindSubtree. If no match is found, then 591 alarmModelResourceId is simply the value of alarmModelResourcePrefix. 593 In addition to this, the variable bindings from the Notifications 594 that signal the alarm state transitions are stored in the active 595 alarm table. This allows for implementations familiar with the 596 particular Notifications to implement other forms of resource 597 identification. 599 For Example: 601 A) Consider an alarm modelled using the authenticationFailure 602 Notification. 604 authenticationFailure NOTIFICATION-TYPE 605 STATUS current 606 DESCRIPTION 607 "An authenticationFailure trap signifies that the SNMPv2 608 entity, acting in an agent role, has received a protocol 609 message that is not properly authenticated. While all 610 implementations of the SNMPv2 must be capable of generating 611 this trap, the snmpEnableAuthenTraps object indicates 612 whether this trap will be generated." 613 ::= { snmpTraps 5 } 615 To set the resource ID to be usmStats, 1.3.6.1.6.3.15.1.1, 616 configure as follows: 617 alarmModelVarbindSubtree = 0.0 618 alarmModelResourcePrefix = usmStats (1.3.6.1.6.3.15.1.1) 620 B) Consider an alarm modelled using linkDown 621 linkDown NOTIFICATION-TYPE 622 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 623 STATUS current 624 DESCRIPTION 625 "" 626 ::= { snmpTraps 3 } 628 To set the resource Id to be the ifIndex, configure as follows: 629 alarmModelVarbindSubtree = ifIndex (1.3.6.1.2.1.2.2.1.1) 630 alarmModelResourcePrefix = 0.0 632 Alternatively, since ifIndex is the first varbind, the following 633 would also work, but might be less meaningful to a human reader 634 of the MIB table: 635 alarmModelVarbindSubtree = 0.0 636 alarmModelResourcePrefix = 0.0 638 B) Consider an alarm modelled using the bgpBackwardTransition 639 Notification. 641 bgpBackwardTransition NOTIFICATION-TYPE 642 OBJECTS { bgpPeerLastError, 643 bgpPeerState } 644 STATUS current 645 DESCRIPTION 646 "The BGPBackwardTransition Event is generated 647 when the BGP FSM moves from a higher numbered 648 state to a lower numbered state." 649 ::= { bgpTraps 2 } 651 To set the resource Id to be the bgpPeerRemoteAddr, the index to 652 the bgpTable, where bgpPeerState resides, configure as follows: 653 alarmModelVarbindSubtree = bgpPeerState 654 (1.3.6.1.2.1.15.3.1.2) 655 alarmModelResourcePrefix = bgpPeerRemoteAddr 656 (1.3.6.1.2.1.15.3.1.7) 658 4.1.5 Configurable Alarm Models 660 The alarm model table can, and probably should, be initially 661 populated by the system. The objects in alarmModelTable and 662 ituAlarmTable have a MAX-ACCESS of read-write, which allows the 663 manager to modify the alarm models to suit their requirements. 665 4.1.6 Active Alarm Management 667 Lists of alarms currently active on an SNMP entity are stored in the 668 alarmActiveTable and, optionally a model specific alarmTable, e.g. 669 the ituAlarmActiveTable. 671 4.1.7 Distributed Alarm Management 673 Distributed alarm management can be achieved by support of the Alarm 674 MIB on both the alarm detection point and on the mid-level manager. 675 This is facilitated by the ability to be able to store different 676 named alarm lists. A middle manager could therefore, create an 677 alarmListName for each of the devices it manages and therefore store 678 separate lists for each device. In additional, the context and IP 679 addresses of the alarm detection point are stored in the 680 alarmActiveTable. 682 4.2 Definitions 684 ALARM-MIB DEFINITIONS ::= BEGIN 686 IMPORTS 687 MODULE-IDENTITY, OBJECT-TYPE, NOTIFICATION-TYPE, 688 Integer32, Unsigned32, Gauge32, 689 TimeTicks, Counter32, Counter64, 690 IpAddress, Opaque, mib-2 FROM SNMPv2-SMI 691 DateAndTime, 692 RowStatus, RowPointer, 693 TEXTUAL-CONVENTION FROM SNMPv2-TC 694 SnmpAdminString, SnmpEngineID FROM SNMP-FRAMEWORK-MIB 695 InetAddressType, InetAddress FROM INET-ADDRESS-MIB 696 MODULE-COMPLIANCE, OBJECT-GROUP, 697 NOTIFICATION-GROUP FROM SNMPv2-CONF; 699 alarmMIB MODULE-IDENTITY 700 LAST-UPDATED "200208280000Z" 701 ORGANIZATION "IETF Distributed Management Working Group" 702 CONTACT-INFO 703 "WG EMail: disman@dorothy.bmc.com 704 Subscribe: disman-request@dorothy.bmc.com 706 Chair: Randy Presuhn 707 BMC Software, Inc. 708 Office 1-3141 709 2141 North First Street 710 San Jose, California 95131 711 USA 712 rpresuhn@bmc.com 713 +1 408 546-1006 715 Editors: Sharon Chisholm 716 Nortel Networks 717 PO Box 3511 Station C 718 Ottawa, Ont. K1Y 4H7 719 Canada 720 schishol@nortelnetworks.com 722 Dan Romascanu 723 Avaya Inc. 724 Atidim Technology Park, Bldg. #3 725 Tel Aviv, 61131 726 Israel 727 Tel: +972-3-645-8414 728 Email: dromasca@avaya.com" 729 DESCRIPTION 730 "The MIB module describes a generic solution 731 to model alarms and to store the current list 732 of active alarms." 733 REVISION "200208280000Z" 734 DESCRIPTION 735 "Initial version, published as RFC XXXX." 737 ::= { mib-2 xx } 739 alarmObjects OBJECT IDENTIFIER ::= { alarmMIB 1 } 741 alarmNotifications OBJECT IDENTIFIER ::= { alarmMIB 0 } 743 alarmModel OBJECT IDENTIFIER ::= { alarmObjects 1 } 745 alarmActive OBJECT IDENTIFIER ::= { alarmObjects 2 } 747 alarmClear OBJECT IDENTIFIER ::= { alarmObjects 3 } 749 -- Textual Conventions 751 ResourceId ::= TEXTUAL-CONVENTION 752 STATUS current 753 DESCRIPTION 754 "A unique identifier for this resource. 756 The type of the resource can be determined by looking 757 at the OID that describes the resource. 759 Resources must be identified in a consistent manner. 760 For example, if this resource is an interface, this 761 object MUST point to an ifIndex." 762 SYNTAX OBJECT IDENTIFIER 764 -- Alarm Model 766 alarmModelLastChanged OBJECT-TYPE 767 SYNTAX TimeTicks 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "The value of sysUpTime at the time of the last 772 creation, deletion or modification of an entry in 773 the alarmModelTable. 775 If the number and content of entries has been unchanged 776 since the last re-initialization of the local network 777 management subsystem, then the value of this object 778 MUST be zero." 779 ::= { alarmModel 1 } 781 alarmModelTable OBJECT-TYPE 782 SYNTAX SEQUENCE OF AlarmModelEntry 783 MAX-ACCESS not-accessible 784 STATUS current 785 DESCRIPTION 786 "A table of information about possible alarms on the system, 787 and how they have been modelled." 788 ::= { alarmModel 2 } 790 alarmModelEntry OBJECT-TYPE 791 SYNTAX AlarmModelEntry 792 MAX-ACCESS not-accessible 793 STATUS current 794 DESCRIPTION 795 "Entries appear in this table for each possible alarm state." 796 INDEX { alarmListName, alarmModelIndex, alarmModelState } 797 ::= { alarmModelTable 1 } 799 AlarmModelEntry ::= SEQUENCE { 800 alarmModelIndex Unsigned32, 801 alarmModelState Unsigned32, 802 alarmModelNotificationId OBJECT IDENTIFIER, 803 alarmModelVarbindIndex Integer32, 804 alarmModelVarbindValue Integer32, 805 alarmModelDescription SnmpAdminString, 806 alarmModelSpecificPointer RowPointer, 807 alarmModelVarbindSubtree OBJECT IDENTIFIER, 808 alarmModelResourcePrefix OBJECT IDENTIFIER, 809 alarmModelRowStatus RowStatus 810 } 812 alarmModelIndex OBJECT-TYPE 813 SYNTAX Unsigned32 (1..4294967295) 814 MAX-ACCESS not-accessible 815 STATUS current 816 DESCRIPTION 817 "An integer that acts as an alarm Id 818 to uniquely identify each alarm 819 within the named alarm list. " 820 ::= { alarmModelEntry 1 } 822 alarmModelState OBJECT-TYPE 823 SYNTAX Unsigned32 (1..4294967295) 824 MAX-ACCESS not-accessible 825 STATUS current 826 DESCRIPTION 827 "A value of 1 MUST indicate a clear alarm state. 828 The value of this object MUST be less than the 829 alarmModelState of more severe alarm states for 830 this alarm. The value of this object MUST be more 831 than the alarmModelState of less severe alarm states 832 for this alarm." 833 ::= { alarmModelEntry 2 } 835 alarmModelNotificationId OBJECT-TYPE 836 SYNTAX OBJECT IDENTIFIER 837 MAX-ACCESS read-create 838 STATUS current 839 DESCRIPTION 840 "The NOTIFICATION-TYPE object identifier of this alarm 841 state transition. If there is no notification associated 842 with this alarm state, the value of this object MUST be 843 '0.0'" 844 ::= { alarmModelEntry 3 } 846 alarmModelVarbindIndex OBJECT-TYPE 847 SYNTAX Integer32 848 MAX-ACCESS read-create 849 STATUS current 850 DESCRIPTION 851 "The index into the varbind listing of the notification 852 indicated by alarmModelNotificationId which helps 853 signal that the given alarm has changed state. 854 If there is no applicable varbind, the value of this 855 object MUST be zero. 857 Note that the value of alarmModelVarbindIndex ignores 858 the existence of the first two obligatory varbinds in 859 the InformRequest-PDU and SNMPv2-Trap-PDU (sysUpTime.0 860 and snmpTrapOID.0). That is, a value of 1 refers to 861 the first varbind after snmpTrapOID.0. 863 If the incoming notification is instead an SNMPv1 Trap-PDU, 864 then a value of 1 refers to the first varbind." 865 ::= { alarmModelEntry 4 } 867 alarmModelVarbindValue OBJECT-TYPE 868 SYNTAX Integer32 869 MAX-ACCESS read-create 870 STATUS current 871 DESCRIPTION 872 "The value that the varbind indicated by 873 alarmModelVarbindIndex takes to indicate 874 that the alarm has entered this state. 875 " 876 ::= { alarmModelEntry 5 } 878 alarmModelDescription OBJECT-TYPE 879 SYNTAX SnmpAdminString 880 MAX-ACCESS read-create 881 STATUS current 882 DESCRIPTION 883 "A brief description of this alarm and state suitable to 884 display to operators." 885 ::= { alarmModelEntry 6 } 887 alarmModelSpecificPointer OBJECT-TYPE 888 SYNTAX RowPointer 889 MAX-ACCESS read-create 890 STATUS current 891 DESCRIPTION 892 "If no additional, model-specific Alarm MIB is supported by the 893 system the value of this object is `0.0'. When a model-specific 894 Alarm MIB is supported, this object is the instance pointer to 895 the model-specific alarm definition." 896 ::= { alarmModelEntry 7 } 898 alarmModelVarbindSubtree OBJECT-TYPE 899 SYNTAX OBJECT IDENTIFIER 900 MAX-ACCESS read-create 901 STATUS current 902 DESCRIPTION 903 "The name portion of each VarBind in the notification, 904 in order, is compared to the value of this object. 905 If the name is equal to or a subtree of the value 906 of this object, for purposes of computing the value 907 of AlarmActiveResourceID the 'prefix' will be the 908 matching portion, and the 'indexes' will be any 909 remainder. The examination of varbinds ends with 910 the first match. If the value of this object is 0.0, 911 then the first varbind, or in the case of v2, the 912 first varbind after the timestamp and the trap 913 OID, will always be matched. 914 " 915 ::= { alarmModelEntry 8 } 917 alarmModelResourcePrefix OBJECT-TYPE 918 SYNTAX OBJECT IDENTIFIER 919 MAX-ACCESS read-create 920 STATUS current 921 DESCRIPTION 922 "The value of AlarmActiveResourceID is computed 923 by appending any indexes extracted in accordance 924 with the description of alarmModelVarbindSubtree 925 onto the value of this object. If this object's 926 value is 0.0, then the 'prefix' extracted is used 927 instead. 928 " 929 ::= { alarmModelEntry 9 } 931 alarmModelRowStatus OBJECT-TYPE 932 SYNTAX RowStatus 933 MAX-ACCESS read-create 934 STATUS current 935 DESCRIPTION 936 "Control for creating and deleting entries. Entries may be 937 modified while active. Alarms whose alarmModelRowStatus is 938 not active will not appear in either the alarmActiveTable 939 or the alarmClearTable. Setting this object to notInService 940 cannot be used as an alarm suppression mechanism. Entries 941 that are notInService will disappear as described in RFC2579 943 This row can not be modified or deleted while it is being 944 referenced by a value of alarmActiveModelPointer. In these 945 cases, an error of `inconsistentValue' will be returned to 946 the manager." 947 ::= { alarmModelEntry 10 } 949 -- Active Alarm Table -- 951 alarmActiveLastChanged OBJECT-TYPE 952 SYNTAX TimeTicks 953 MAX-ACCESS read-only 954 STATUS current 955 DESCRIPTION 956 "The value of sysUpTime at the time of the last 957 creation or deletion of an entry in the alarmActiveTable. 958 If the number of entries has been unchanged since the 959 last re-initialization of the local network management 960 subsystem, then this object contains a zero value." 961 ::= { alarmActive 1 } 963 alarmActiveTable OBJECT-TYPE 964 SYNTAX SEQUENCE OF AlarmActiveEntry 965 MAX-ACCESS not-accessible 966 STATUS current 967 DESCRIPTION 968 "A table of Active Alarms entries." 969 ::= { alarmActive 2 } 971 alarmActiveEntry OBJECT-TYPE 972 SYNTAX AlarmActiveEntry 973 MAX-ACCESS not-accessible 974 STATUS current 975 DESCRIPTION 976 "Entries appear in this table when alarms are raised. They 977 are removed when the alarm is cleared." 978 INDEX { alarmListName, alarmActiveDateAndTime, 979 alarmActiveIndex } 980 ::= { alarmActiveTable 1 } 982 AlarmActiveEntry ::= SEQUENCE { 983 alarmListName SnmpAdminString, 984 alarmActiveDateAndTime DateAndTime, 986 alarmActiveIndex Unsigned32, 987 alarmActiveEngineID SnmpEngineID, 988 alarmActiveEngineAddressType InetAddressType, 989 alarmActiveEngineAddress InetAddress, 990 alarmActiveContextName SnmpAdminString, 991 alarmActiveVariables Unsigned32, 992 alarmActiveNotificationID OBJECT IDENTIFIER, 993 alarmActiveResourceId ResourceId, 994 alarmActiveDescription SnmpAdminString, 995 alarmActiveLogPointer RowPointer, 996 alarmActiveModelPointer RowPointer, 997 alarmActiveSpecificPointer RowPointer } 999 alarmListName OBJECT-TYPE 1000 SYNTAX SnmpAdminString (SIZE(0..32)) 1001 MAX-ACCESS not-accessible 1002 STATUS current 1003 DESCRIPTION 1004 "The name of the list of alarms. This SHOULD be the same as 1005 nlmLogName if the Notification Log MIB [RFC3014] is supported. 1007 An implementation may allow multiple named alarm lists, up to 1008 some implementation-specific limit (which may be none). A 1009 zero-length list name is reserved for creation and deletion 1010 by the managed system, and MUST be used as the default log 1011 name by systems that do not support named alarm lists." 1012 ::= { alarmActiveEntry 1 } 1014 alarmActiveDateAndTime OBJECT-TYPE 1015 SYNTAX DateAndTime 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION 1019 "The local date and time when the error occurred. 1021 Implementations MUST include the offset from UTC, 1022 if available. Implementation in environments in which 1023 the UTC offset is not available is NOT RECOMMENDED." 1024 ::= { alarmActiveEntry 2 } 1026 alarmActiveIndex OBJECT-TYPE 1027 SYNTAX Unsigned32 (1..4294967295) 1028 MAX-ACCESS not-accessible 1029 STATUS current 1030 DESCRIPTION 1031 "A strictly monotonically increasing integer which 1032 acts as the index of entries within the named alarm 1033 list. It wraps back to 1 after it reaches its 1034 maximum value." 1035 ::= { alarmActiveEntry 3 } 1037 alarmActiveEngineID OBJECT-TYPE 1038 SYNTAX SnmpEngineID 1039 MAX-ACCESS read-only 1040 STATUS current 1041 DESCRIPTION 1042 "The identification of the SNMP engine at which the alarm 1043 originated. 1044 If the alarm list can contain alarms from only one 1045 engine or the alarm is from an SNMPv1 system, this object is 1046 a zero length string." 1047 ::= { alarmActiveEntry 4 } 1049 alarmActiveEngineAddressType OBJECT-TYPE 1050 SYNTAX InetAddressType 1051 MAX-ACCESS read-only 1052 STATUS current 1053 DESCRIPTION 1054 "This object indicates what type of address is stored in 1055 the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc." 1056 ::= { alarmActiveEntry 5 } 1058 alarmActiveEngineAddress OBJECT-TYPE 1059 SYNTAX InetAddress 1060 MAX-ACCESS read-only 1061 STATUS current 1062 DESCRIPTION 1063 "The IP Address of the SNMP engine on which the alarm is 1064 occurring. This is used to identify the source of an SNMPv1 1065 trap, since an alarmActiveEngineId cannot be extracted from the 1066 SNMPv1 trap PDU. 1068 This object MUST always be instantiated, even if the list 1069 can contain alarms from only one engine." 1070 ::= { alarmActiveEntry 6 } 1072 alarmActiveContextName OBJECT-TYPE 1073 SYNTAX SnmpAdminString 1074 MAX-ACCESS read-only 1075 STATUS current 1076 DESCRIPTION 1077 "The name of the SNMP MIB context from which the alarm came. 1078 For SNMPv1 alarms this is the community string from the Trap. 1079 If the alarm's source SNMP engine is known not to support 1080 multiple contexts, this object is a zero length string." 1081 ::= { alarmActiveEntry 7 } 1083 alarmActiveVariables OBJECT-TYPE 1084 SYNTAX Unsigned32 1085 MAX-ACCESS read-only 1086 STATUS current 1087 DESCRIPTION 1088 "The number of variables in alarmActiveVariableTable for this 1089 alarm. Also, the number of varbinds for the notification 1090 associated with this alarm state." 1091 ::= { alarmActiveEntry 8 } 1093 alarmActiveNotificationID OBJECT-TYPE 1094 SYNTAX OBJECT IDENTIFIER 1095 MAX-ACCESS read-only 1096 STATUS current 1097 DESCRIPTION 1098 "The NOTIFICATION-TYPE object identifier of the alarm 1099 state transition that is occurring." 1100 ::= { alarmActiveEntry 9 } 1102 alarmActiveResourceId OBJECT-TYPE 1103 SYNTAX ResourceId 1104 MAX-ACCESS read-only 1105 STATUS current 1106 DESCRIPTION 1107 "This object identifies the resource under alarm. 1109 If there is no corresponding resource, then 1110 the value of this object MUST be 0.0." 1111 ::= { alarmActiveEntry 10 } 1113 alarmActiveDescription OBJECT-TYPE 1114 SYNTAX SnmpAdminString 1115 MAX-ACCESS read-only 1116 STATUS current 1117 DESCRIPTION 1118 "This object provides a textual description of the 1119 active alarm. This text is generated dynamically by the 1120 notification generator to provide useful information 1121 to the human operator. This information SHOULD 1122 provide information allowing the operator to locate 1123 the resource for which this alarm is being generated. 1124 This information is not intended for consumption by 1125 automated tools." 1126 ::= { alarmActiveEntry 11 } 1128 alarmActiveLogPointer OBJECT-TYPE 1129 SYNTAX RowPointer 1130 MAX-ACCESS read-only 1131 STATUS current 1132 DESCRIPTION 1133 "A pointer to the corresponding row in a 1134 notification logging MIB where the state change 1135 notification for this active alarm is logged. 1136 If no log entry applies to this active alarm, 1137 then this object MUST have the value of 0.0" 1138 ::= { alarmActiveEntry 12 } 1140 alarmActiveModelPointer OBJECT-TYPE 1141 SYNTAX RowPointer 1142 MAX-ACCESS read-only 1143 STATUS current 1144 DESCRIPTION 1145 "A pointer to the corresponding row in the 1146 alarmModelTable for this active alarm. This 1147 points not only to the alarm model being 1148 instantiated, but also to the specific alarm 1149 state that is active." 1150 ::= { alarmActiveEntry 13 } 1152 alarmActiveSpecificPointer OBJECT-TYPE 1153 SYNTAX RowPointer 1154 MAX-ACCESS read-only 1155 STATUS current 1156 DESCRIPTION 1157 "If no additional, model-specific, Alarm MIB is supported by the 1158 system this object is `0.0'. When a model-specific Alarm MIB is 1159 supported, this object is the instance pointer to the specific 1160 model-specific active alarm list." 1161 ::= { alarmActiveEntry 14 } 1163 -- Active Alarm Variable Table -- 1165 alarmActiveVariableTable OBJECT-TYPE 1166 SYNTAX SEQUENCE OF AlarmActiveVariableEntry 1167 MAX-ACCESS not-accessible 1168 STATUS current 1169 DESCRIPTION 1170 "A table of variables to go with active alarm entries." 1171 ::= { alarmActive 3 } 1173 alarmActiveVariableEntry OBJECT-TYPE 1174 SYNTAX AlarmActiveVariableEntry 1175 MAX-ACCESS not-accessible 1176 STATUS current 1177 DESCRIPTION 1178 "Entries appear in this table when there are variables in 1179 the varbind list of a corresponding alarm in 1180 alarmActiveTable. 1182 Entries appear in this table as though 1183 the trap/notification had been transported using a 1184 SNMPv2-Trap-PDU, as defined in [RFC1905] - i.e, the 1185 alarmActiveVariableIndex 1 will always be sysUpTime 1186 and alarmActiveVariableIndex 2 will always be 1187 snmpTrapOID. 1189 If the incoming notification is instead an SNMPv1 Trap-PDU and 1190 the value of alarmModelVarbindIndex is 1 or 2, an appropriate 1191 value for sysUpTime.0 or snmpTrapOID.0 shall be determined 1192 by using the rules in section 3.1 of [RFC2576]." 1193 INDEX { alarmListName, alarmActiveIndex, 1194 alarmActiveVariableIndex } 1195 ::= { alarmActiveVariableTable 1 } 1197 AlarmActiveVariableEntry ::= SEQUENCE { 1198 alarmActiveVariableIndex Unsigned32, 1199 alarmActiveVariableID OBJECT IDENTIFIER, 1200 alarmActiveVariableValueType INTEGER, 1201 alarmActiveVariableCounter32Val Counter32, 1202 alarmActiveVariableUnsigned32Val Unsigned32, 1203 alarmActiveVariableTimeTicksVal TimeTicks, 1204 alarmActiveVariableInteger32Val Integer32, 1205 alarmActiveVariableOctetStringVal OCTET STRING, 1206 alarmActiveVariableIpAddressVal IpAddress, 1207 alarmActiveVariableOidVal OBJECT IDENTIFIER, 1208 alarmActiveVariableCounter64Val Counter64, 1209 alarmActiveVariableOpaqueVal Opaque } 1211 alarmActiveVariableIndex OBJECT-TYPE 1212 SYNTAX Unsigned32 (1..4294967295) 1213 MAX-ACCESS not-accessible 1214 STATUS current 1215 DESCRIPTION 1216 "A strictly monotonically increasing integer, starting at 1217 1 for a given alarmActiveIndex, for indexing variables 1218 within the active alarm list. " 1219 ::= { alarmActiveVariableEntry 1 } 1221 alarmActiveVariableID OBJECT-TYPE 1222 SYNTAX OBJECT IDENTIFIER 1223 MAX-ACCESS read-only 1224 STATUS current 1225 DESCRIPTION 1226 "The alarm variable's object identifier." 1227 ::= { alarmActiveVariableEntry 2 } 1229 alarmActiveVariableValueType OBJECT-TYPE 1230 SYNTAX INTEGER { 1231 counter32(1), 1232 unsigned32(2), 1233 timeTicks(3), 1234 integer32(4), 1235 ipAddress(5), 1236 octetString(6), 1237 objectId(7), 1238 counter64(8), 1239 opaque(9) 1240 } 1241 MAX-ACCESS read-only 1242 STATUS current 1243 DESCRIPTION 1244 "The type of the value. One and only one of the value 1245 objects that follow is used, based on this type." 1246 ::= { alarmActiveVariableEntry 3 } 1248 alarmActiveVariableCounter32Val OBJECT-TYPE 1249 SYNTAX Counter32 1250 MAX-ACCESS read-only 1251 STATUS current 1252 DESCRIPTION 1253 "The value when alarmActiveVariableType is 'counter32'." 1254 ::= { alarmActiveVariableEntry 4 } 1256 alarmActiveVariableUnsigned32Val OBJECT-TYPE 1257 SYNTAX Unsigned32 1258 MAX-ACCESS read-only 1259 STATUS current 1260 DESCRIPTION 1261 "The value when alarmActiveVariableType is 'unsigned32'." 1262 ::= { alarmActiveVariableEntry 5 } 1264 alarmActiveVariableTimeTicksVal OBJECT-TYPE 1265 SYNTAX TimeTicks 1266 MAX-ACCESS read-only 1267 STATUS current 1268 DESCRIPTION 1269 "The value when alarmActiveVariableType is 'timeTicks'." 1270 ::= { alarmActiveVariableEntry 6 } 1272 alarmActiveVariableInteger32Val OBJECT-TYPE 1273 SYNTAX Integer32 1274 MAX-ACCESS read-only 1275 STATUS current 1276 DESCRIPTION 1277 "The value when alarmActiveVariableType is 'integer32'." 1278 ::= { alarmActiveVariableEntry 7 } 1280 alarmActiveVariableOctetStringVal OBJECT-TYPE 1281 SYNTAX OCTET STRING 1282 MAX-ACCESS read-only 1283 STATUS current 1284 DESCRIPTION 1285 "The value when alarmActiveVariableType is 'octetString'." 1286 ::= { alarmActiveVariableEntry 8 } 1288 alarmActiveVariableIpAddressVal OBJECT-TYPE 1289 SYNTAX IpAddress 1290 MAX-ACCESS read-only 1291 STATUS current 1292 DESCRIPTION 1293 "The value when alarmActiveVariableType is 'ipAddress'." 1294 ::= { alarmActiveVariableEntry 9 } 1296 alarmActiveVariableOidVal OBJECT-TYPE 1297 SYNTAX OBJECT IDENTIFIER 1298 MAX-ACCESS read-only 1299 STATUS current 1300 DESCRIPTION 1301 "The value when alarmActiveVariableType is 'objectId'." 1302 ::= { alarmActiveVariableEntry 10 } 1304 alarmActiveVariableCounter64Val OBJECT-TYPE 1305 SYNTAX Counter64 1306 MAX-ACCESS read-only 1307 STATUS current 1308 DESCRIPTION 1309 "The value when alarmActiveVariableType is 'counter64'." 1310 ::= { alarmActiveVariableEntry 11 } 1312 alarmActiveVariableOpaqueVal OBJECT-TYPE 1313 SYNTAX Opaque 1314 MAX-ACCESS read-only 1315 STATUS current 1316 DESCRIPTION 1317 "The value when alarmActiveVariableType is 'opaque'." 1318 ::= { alarmActiveVariableEntry 12 } 1320 -- Statistics -- 1322 alarmActiveStatsTable OBJECT-TYPE 1323 SYNTAX SEQUENCE OF AlarmActiveStatsEntry 1324 MAX-ACCESS not-accessible 1325 STATUS current 1326 DESCRIPTION 1327 "This table represents the alarm statistics 1328 information." 1329 ::= { alarmActive 4 } 1331 alarmActiveStatsEntry OBJECT-TYPE 1332 SYNTAX AlarmActiveStatsEntry 1333 MAX-ACCESS not-accessible 1334 STATUS current 1335 DESCRIPTION 1336 "Statistics on the current active alarms." 1337 INDEX { alarmListName } 1339 ::= { alarmActiveStatsTable 1 } 1341 AlarmActiveStatsEntry ::= 1342 SEQUENCE { 1343 alarmActiveStatsActiveCurrent Gauge32, 1344 alarmActiveStatsActives Counter32, 1345 alarmActiveStatsLastRaise TimeTicks, 1346 alarmActiveStatsLastClear TimeTicks 1347 } 1349 alarmActiveStatsActiveCurrent OBJECT-TYPE 1350 SYNTAX Gauge32 1351 MAX-ACCESS read-only 1352 STATUS current 1353 DESCRIPTION 1354 "The total number of currently active alarms on the system." 1356 ::= { alarmActiveStatsEntry 1 } 1358 alarmActiveStatsActives OBJECT-TYPE 1359 SYNTAX Counter32 1360 MAX-ACCESS read-only 1361 STATUS current 1362 DESCRIPTION 1363 "The total number of active alarms since system restarted." 1365 ::= { alarmActiveStatsEntry 2 } 1367 alarmActiveStatsLastRaise OBJECT-TYPE 1368 SYNTAX TimeTicks 1369 MAX-ACCESS read-only 1370 STATUS current 1371 DESCRIPTION 1372 "The value of sysUpTime at the time of the last 1373 alarm raise for this alarm list. 1374 If no alarm raises have occurred since the 1375 last re-initialization of the local network management 1376 subsystem, then this object contains a zero value." 1377 ::= { alarmActiveStatsEntry 3 } 1379 alarmActiveStatsLastClear OBJECT-TYPE 1380 SYNTAX TimeTicks 1381 MAX-ACCESS read-only 1382 STATUS current 1383 DESCRIPTION 1384 "The value of sysUpTime at the time of the last 1385 alarm clear for this alarm list. 1386 If no alarm clears have occurred since the 1387 last re-initialization of the local network management 1388 subsystem, then this object contains a zero value." 1389 ::= { alarmActiveStatsEntry 4 } 1391 -- Alarm Clear 1393 alarmClearMaximum OBJECT-TYPE 1394 SYNTAX Integer32 1395 MAX-ACCESS read-write 1396 STATUS current 1397 DESCRIPTION 1398 "This object specifies the maximum number of cleared 1399 alarms to store in the alarmClearTable. When this 1400 number is reached, the cleared alarms with the 1401 earliest clear time will be removed from the table." 1402 ::= { alarmClear 1 } 1404 alarmClearTable OBJECT-TYPE 1405 SYNTAX SEQUENCE OF AlarmClearEntry 1406 MAX-ACCESS not-accessible 1407 STATUS current 1408 DESCRIPTION 1409 "This table contains information on 1410 cleared alarms." 1411 ::= { alarmClear 2 } 1413 alarmClearEntry OBJECT-TYPE 1414 SYNTAX AlarmClearEntry 1415 MAX-ACCESS not-accessible 1416 STATUS current 1417 DESCRIPTION 1418 "Information on a cleared alarm." 1419 INDEX { alarmListName, alarmClearDateAndTime, 1420 alarmClearIndex } 1422 ::= { alarmClearTable 1 } 1424 AlarmClearEntry ::= 1425 SEQUENCE { 1426 alarmClearIndex Unsigned32, 1427 alarmClearDateAndTime DateAndTime, 1428 alarmClearEngineID SnmpEngineID, 1429 alarmClearEngineAddressType InetAddressType, 1430 alarmClearEngineAddress InetAddress, 1431 alarmClearContextName SnmpAdminString, 1432 alarmClearNotificationID OBJECT IDENTIFIER, 1433 alarmClearResourceId ResourceId, 1434 alarmClearLogIndex Unsigned32, 1435 alarmClearModelPointer RowPointer 1436 } 1438 alarmClearIndex OBJECT-TYPE 1439 SYNTAX Unsigned32 (1..4294967295) 1440 MAX-ACCESS not-accessible 1441 STATUS current 1442 DESCRIPTION 1443 "A strictly monotonically increasing integer which acts 1444 as the index of entries within the named alarm list. 1445 It wraps back to 1 after it reaches its maximum value. 1447 This object has the same value as the alarmActiveIndex that 1448 this alarm instance had when it was active." 1449 ::= { alarmClearEntry 1 } 1451 alarmClearDateAndTime OBJECT-TYPE 1452 SYNTAX DateAndTime 1453 MAX-ACCESS not-accessible 1454 STATUS current 1455 DESCRIPTION 1456 "The local date and time when the alarm cleared. 1458 Implementations MUST include the offset from UTC, 1459 if available. Implementation in environments in which 1460 the UTC offset is not available is NOT RECOMMENDED." 1461 ::= { alarmClearEntry 2 } 1463 alarmClearEngineID OBJECT-TYPE 1464 SYNTAX SnmpEngineID 1465 MAX-ACCESS read-only 1466 STATUS current 1467 DESCRIPTION 1468 "The identification of the SNMP engine at which the alarm 1469 originated. 1470 If the alarm list can contain Notifications from only one 1471 engine or the trap is from an SNMPv1 system, this object is 1472 a zero length string." 1473 ::= { alarmClearEntry 3 } 1475 alarmClearEngineAddressType OBJECT-TYPE 1476 SYNTAX InetAddressType 1477 MAX-ACCESS read-only 1478 STATUS current 1479 DESCRIPTION 1480 "This object indicates what type of address is stored in 1481 the alarmActiveEngineAddress object - IPv4, IPv6, DNS, etc." 1482 ::= { alarmClearEntry 4 } 1484 alarmClearEngineAddress OBJECT-TYPE 1485 SYNTAX InetAddress 1486 MAX-ACCESS read-only 1487 STATUS current 1488 DESCRIPTION 1489 "The IP Address of the SNMP engine on which the alarm was 1490 occurring. This is used to identify the source of an SNMPv1 1491 trap, since an alarmActiveEngineId cannot be extracted from the 1492 SNMPv1 trap PDU. 1494 This object MUST always be instantiated, even if the list 1495 can contain alarms from only one engine." 1496 ::= { alarmClearEntry 5 } 1498 alarmClearContextName OBJECT-TYPE 1499 SYNTAX SnmpAdminString 1500 MAX-ACCESS read-only 1501 STATUS current 1502 DESCRIPTION 1503 "The name of the SNMP MIB context from which the alarm came. 1504 For SNMPv1 traps this is the community string from the Trap. 1505 If the alarm's source SNMP engine is known not to support 1506 multiple contexts, this object is a zero length string." 1507 ::= { alarmClearEntry 6 } 1509 alarmClearNotificationID OBJECT-TYPE 1510 SYNTAX OBJECT IDENTIFIER 1511 MAX-ACCESS read-only 1512 STATUS current 1513 DESCRIPTION 1514 "The NOTIFICATION-TYPE object identifier of the alarm 1515 clear." 1516 ::= { alarmClearEntry 7 } 1518 alarmClearResourceId OBJECT-TYPE 1519 SYNTAX ResourceId 1520 MAX-ACCESS read-only 1521 STATUS current 1522 DESCRIPTION 1523 "This object identifies the resource that was under alarm. 1525 If there is no corresponding resource, then 1526 the value of this object MUST be 0.0." 1527 ::= { alarmClearEntry 8 } 1529 alarmClearLogIndex OBJECT-TYPE 1530 SYNTAX Unsigned32 (0..4294967295) 1531 MAX-ACCESS read-only 1532 STATUS current 1533 DESCRIPTION 1534 "This number MUST be the same as the log index of the 1535 applicable row in the notification log MIB, if it exists. 1536 If no log index applies to the trap, then this object 1537 MUST have the value of 0." 1538 ::= { alarmClearEntry 9 } 1540 alarmClearModelPointer OBJECT-TYPE 1541 SYNTAX RowPointer 1542 MAX-ACCESS read-only 1543 STATUS current 1544 DESCRIPTION 1545 "A pointer to the corresponding row in the 1546 alarmModelTable for this cleared alarm." 1547 ::= { alarmClearEntry 10 } 1549 -- Notifications 1551 alarmActiveState NOTIFICATION-TYPE 1552 OBJECTS { alarmActiveModelPointer, 1553 alarmActiveResourceId } 1554 STATUS current 1555 DESCRIPTION 1556 "An instance of the alarm indicated by 1557 alarmActiveModelPointer has been raised 1558 against the entity indicated by 1559 alarmActiveResourceId." 1560 ::= { alarmNotifications 2 } 1562 alarmClearState NOTIFICATION-TYPE 1563 OBJECTS { alarmActiveModelPointer, 1564 alarmActiveResourceId } 1565 STATUS current 1566 DESCRIPTION 1567 "An instance of the alarm indicated by 1568 alarmActiveModelPointer has been cleared against 1569 the entity indicated by alarmACtiveResourceId." 1570 ::= { alarmNotifications 3 } 1572 -- Conformance 1574 alarmConformance OBJECT IDENTIFIER ::= { alarmMIB 2 } 1576 alarmCompliances OBJECT IDENTIFIER ::= { alarmConformance 1 } 1578 alarmCompliance MODULE-COMPLIANCE 1579 STATUS current 1580 DESCRIPTION 1581 "The compliance statement for systems supporting 1582 the Alarm MIB." 1583 MODULE -- this module 1584 MANDATORY-GROUPS { 1585 alarmActiveGroup, 1586 alarmModelGroup 1587 } 1588 ::= { alarmCompliances 1 } 1590 alarmGroups OBJECT IDENTIFIER ::= { alarmConformance 2 } 1591 alarmModelGroup OBJECT-GROUP 1592 OBJECTS { 1593 alarmModelLastChanged, 1594 alarmModelNotificationId, 1595 alarmModelVarbindIndex, 1596 alarmModelVarbindValue, 1597 alarmModelDescription, 1598 alarmModelSpecificPointer, 1599 alarmModelVarbindSubtree, 1600 alarmModelResourcePrefix, 1601 alarmModelRowStatus 1602 } 1603 STATUS current 1604 DESCRIPTION 1605 "Alarm model group." 1606 ::= { alarmGroups 1} 1608 alarmActiveGroup OBJECT-GROUP 1609 OBJECTS { 1610 alarmActiveLastChanged, 1611 alarmActiveEngineID, 1612 alarmActiveEngineAddressType, 1613 alarmActiveEngineAddress, 1614 alarmActiveContextName, 1615 alarmActiveVariables, 1616 alarmActiveNotificationID, 1617 alarmActiveResourceId, 1618 alarmActiveDescription, 1619 alarmActiveLogPointer, 1620 alarmActiveModelPointer, 1621 alarmActiveSpecificPointer, 1622 alarmActiveVariableID, 1623 alarmActiveVariableValueType, 1624 alarmActiveVariableCounter32Val, 1625 alarmActiveVariableUnsigned32Val, 1626 alarmActiveVariableTimeTicksVal, 1627 alarmActiveVariableInteger32Val, 1628 alarmActiveVariableOctetStringVal, 1629 alarmActiveVariableIpAddressVal, 1630 alarmActiveVariableOidVal, 1631 alarmActiveVariableCounter64Val, 1632 alarmActiveVariableOpaqueVal 1633 } 1634 STATUS current 1635 DESCRIPTION 1636 "Active Alarm list group." 1637 ::= { alarmGroups 2} 1639 alarmActiveStatsGroup OBJECT-GROUP 1640 OBJECTS { 1641 alarmActiveStatsActives, 1642 alarmActiveStatsActiveCurrent, 1643 alarmActiveStatsLastRaise, 1644 alarmActiveStatsLastClear 1645 } 1646 STATUS current 1647 DESCRIPTION 1648 " Active alarm summary group." 1649 ::= { alarmGroups 3} 1651 alarmClearGroup OBJECT-GROUP 1652 OBJECTS { 1653 alarmClearMaximum, 1654 alarmClearEngineID, 1655 alarmClearEngineAddressType, 1656 alarmClearEngineAddress, 1657 alarmClearContextName, 1658 alarmClearNotificationID, 1659 alarmClearResourceId, 1660 alarmClearLogIndex, 1661 alarmClearModelPointer 1662 } 1663 STATUS current 1664 DESCRIPTION 1665 " Cleared alarm group." 1666 ::= { alarmGroups 4} 1668 alarmNotificationsGroup NOTIFICATION-GROUP 1669 NOTIFICATIONS { alarmActiveState, alarmClearState } 1670 STATUS current 1671 DESCRIPTION 1672 "The collection of notifications that can be used to 1673 model alarms for faults lacking pre-existing 1674 notification definitions." 1675 ::= { alarmGroups 6 } 1677 END 1679 5. ITU Alarm 1681 5.1 Overview 1683 This MIB module defines alarm information specific to the alarm 1684 model defined in ITU M.3100 [M.3100], X.733[X.733] and X.736[X.736]. 1685 This MIB module follows the modular architecture defined by the 1686 Alarm MIB, in which the generic Alarm MIB can be augmented by other 1687 alarm information defined according to more specific models that 1688 define additional behaviour and characteristics. 1690 The ituAlarmTable contains information from the ITU Alarm Model 1691 about possible alarms in the system. 1693 The ituAlarmActiveTable contains information from the ITU Alarm 1694 Model about alarms that are currently occurring on the system. 1696 The ituAlarmActiveStatsTable provides statistics on current and 1697 total alarms. 1699 5.2 IANA Considerations 1701 Over time, there will be a need to add new IANAItuProbableCause 1702 enumerated values for new probable causes. The Internet Assigned 1703 Number Authority (IANA) is responsible for the assignment of all 1704 Internet numbers, including various SNMP-related numbers, and 1705 specifically, new IANAItuProbableCause and IANAItuEventType values. 1706 Values of IANAItuProbableCause less than 1024 are reserved for 1707 causes that correspond to ITU probable cause. IANAItuProbableCause 1708 of 0 is reserved for special purposes and therefore cannot be 1709 assigned. 1711 The following shall be used as the initial values, but the latest 1712 values for these textual conventions should be obtained from IANA: 1714 IANA-ITU-ALARM-TC DEFINITIONS ::= BEGIN 1716 IMPORTS 1717 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 1718 TEXTUAL-CONVENTION FROM SNMPv2-TC; 1720 ianaItuAlarmNumbers MODULE-IDENTITY 1721 LAST-UPDATED "200208280000Z" 1722 ORGANIZATION "IANA" 1723 CONTACT-INFO 1724 "Postal: Internet Assigned Numbers Authority 1725 Internet Corporation for Assigned Names 1727 and Numbers 1728 4676 Admiralty Way, Suite 330 1729 Marina del Rey, CA 90292-6601 1730 USA 1732 Tel: +1 310-823-9358 1733 E-Mail: iana@iana.org" 1734 DESCRIPTION 1735 "The MIB module defines the ITU Alarm 1736 textual convention for objects expected to require 1737 regular extension." 1738 ::= { mib-2 xx } 1740 IANAItuProbableCause ::= TEXTUAL-CONVENTION 1741 STATUS current 1742 DESCRIPTION 1743 "ITU probable cause values for the alarms as per M.3100, 1744 X.733 and X.736. Duplicate values defined in X.733 1745 are appended with _X733 to ensure uniqueness. Probable 1746 cause 1747 value 0 is reserved for special purposes." 1748 SYNTAX INTEGER 1749 { 1750 -- The following probable causes were defined in M.3100 1751 aIS (1), 1752 callSetUpFailure (2), 1753 degradedSignal (3), 1754 farEndReceiverFailure (4), 1755 framingError (5), 1756 lossOfFrame (6), 1757 lossOfPointer (7), 1758 lossOfSignal (8), 1759 payloadTypeMismatch (9), 1760 transmissionError (10), 1761 remoteAlarmInterface (11), 1762 excessiveBER (12), 1763 pathTraceMismatch (13), 1764 unavailable (14), 1765 signalLabelMismatch (15), 1766 lossOfMultiFrame (16), 1767 receiveFailure (17), 1768 transmitFailure (18), 1769 modulationFailure (19), 1770 demodulationFailure (20), 1771 broadcastChannelFailure (21), 1772 connectionEstablishmentError (22), 1773 invalidMessageReceived (23), 1774 localNodeTransmissionError (24), 1775 remoteNodeTransmissionError (25), 1776 routingFailure (26), 1778 --Values 27-50 are reserved for communications alarm related 1779 --probable causes 1780 -- The following are used with equipment alarm. 1782 backplaneFailure (51), 1783 dataSetProblem (52), 1784 equipmentIdentifierDuplication (53), 1785 externalIFDeviceProblem (54), 1786 lineCardProblem (55), 1787 multiplexerProblem (56), 1788 nEIdentifierDuplication (57), 1789 powerProblem (58), 1790 processorProblem (59), 1791 protectionPathFailure (60), 1792 receiverFailure (61), 1793 replaceableUnitMissing (62), 1794 replaceableUnitTypeMismatch (63), 1795 synchronizationSourceMismatch (64), 1796 terminalProblem (65), 1797 timingProblem (66), 1798 transmitterFailure (67), 1799 trunkCardProblem (68), 1800 replaceableUnitProblem (69), 1801 realTimeClockFailure (70), 1802 --An equipment alarm to be issued if the system detects that the 1803 --real time clock has failed 1804 antennaFailure (71), 1805 batteryChargingFailure (72), 1806 diskFailure (73), 1807 frequencyHoppingFailure (74), 1808 iODeviceError (75), 1809 lossOfSynchronisation (76), 1810 lossOfRedundancy (77), 1811 powerSupplyFailure (78), 1812 signalQualityEvaluationFailure (79), 1813 tranceiverFailure (80), 1814 protectionMechanismFailure (81), 1815 protectingResourceFailure (82), 1816 -- Values 83-100 are reserved for equipment alarm related probable 1817 -- causes 1818 -- The following are used with environmental alarm. 1819 airCompressorFailure (101), 1820 airConditioningFailure (102), 1821 airDryerFailure (103), 1822 batteryDischarging (104), 1823 batteryFailure (105), 1824 commercialPowerFailure (106), 1825 coolingFanFailure (107), 1826 engineFailure (108), 1827 fireDetectorFailure (109), 1828 fuseFailure (110), 1829 generatorFailure (111), 1830 lowBatteryThreshold (112), 1831 pumpFailure (113), 1832 rectifierFailure (114), 1833 rectifierHighVoltage (115), 1834 rectifierLowFVoltage (116), 1835 ventilationsSystemFailure (117), 1836 enclosureDoorOpen (118), 1837 explosiveGas (119), 1838 fire (120), 1839 flood (121), 1840 highHumidity (122), 1841 highTemperature (123), 1842 highWind (124), 1843 iceBuildUp (125), 1844 intrusionDetection (126), 1845 lowFuel (127), 1846 lowHumidity (128), 1847 lowCablePressure (129), 1848 lowTemperatue (130), 1849 lowWater (131), 1850 smoke (132), 1851 toxicGas (133), 1852 coolingSystemFailure (134), 1853 externalEquipmentFailure (135), 1854 externalPointFailure (136), 1855 -- Values 137-150 are reserved for environmental alarm related 1856 -- probable causes 1857 -- The following are used with Processing error alarm. 1858 storageCapacityProblem (151), 1859 memoryMismatch (152), 1860 corruptData (153), 1861 outOfCPUCycles (154), 1862 sfwrEnvironmentProblem (155), 1863 sfwrDownloadFailure (156), 1864 lossOfRealTimel (157), 1865 --A processing error alarm to be issued after the system has 1866 --reinitialised. This will indicate 1867 --to the management systems that the view they have of the managed 1868 --system may no longer 1869 --be valid. Usage example: The managed 1870 --system issues this alarm after a reinitialization with severity 1871 --warning to inform the 1872 --management system about the event. No clearing notification will 1873 --be sent. 1874 applicationSubsystemFailure (158), 1875 configurationOrCustomisationError (159), 1876 databaseInconsistency (160), 1877 fileError (161), 1878 outOfMemory (162), 1879 softwareError (163), 1880 timeoutExpired (164), 1881 underlayingResourceUnavailable (165), 1882 versionMismatch (166), 1883 --Values 168-200 are reserved for processing error alarm related 1884 -- probable causes. 1885 bandwidthReduced (201), 1886 congestion (202), 1887 excessiveErrorRate (203), 1888 excessiveResponseTime (204), 1889 excessiveRetransmissionRate (205), 1890 reducedLoggingCapability (206), 1891 systemResourcesOverload (207 ), 1892 -- The following were defined X.733 1894 adapterError (500), 1895 applicationSubsystemFailture (501), 1896 bandwidthReduced_X733 (502), 1897 callEstablishmentError (503), 1898 communicationsProtocolError (504), 1899 communicationsSubsystemFailure (505), 1900 configurationOrCustomizationError (506), 1901 congestion_X733 (507), 1902 coruptData (508), 1903 cpuCyclesLimitExceeded (509), 1904 dataSetOrModemError (510), 1905 degradedSignal_X733 (511), 1906 dteDceInterfaceError (512), 1907 enclosureDoorOpen_X733 (513), 1908 equipmentMalfunction (514), 1909 excessiveVibration (515), 1910 fileError_X733 (516), 1911 fireDetected (517), 1912 framingError_X733 (518), 1913 heatingVentCoolingSystemProblem (519), 1914 humidityUnacceptable (520), 1915 inputOutputDeviceError (521), 1916 inputDeviceError (522), 1917 lanError (523), 1918 leakDetected (524), 1919 localNodeTransmissionError_X733 (525), 1920 lossOfFrame_X733 (526), 1921 lossOfSignal_X733 (527), 1922 materialSupplyExhausted (528), 1923 multiplexerProblem_X733 (529), 1924 outOfMemory_X733 (530), 1925 ouputDeviceError (531), 1926 performanceDegraded (532), 1927 powerProblems (533), 1928 pressureUnacceptable (534), 1929 processorProblems (535), 1930 pumpFailure_X733 (536), 1931 queueSizeExceeded (537), 1932 receiveFailure_X733 (538), 1933 receiverFailure_X733 (539), 1934 remoteNodeTransmissionError_X733 (540), 1935 resourceAtOrNearingCapacity (541), 1936 responseTimeExecessive (542), 1937 retransmissionRateExcessive (543), 1938 softwareError_X733 (544), 1939 softwareProgramAbnormallyTerminated (545), 1940 softwareProgramError (546), 1941 storageCapacityProblem_X733 (547), 1942 temperatureUnacceptable (548), 1943 thresholdCrossed (549), 1944 timingProblem_X733 (550), 1945 toxicLeakDetected (551), 1946 transmitFailure_X733 (552), 1947 transmiterFailure (553), 1948 underlyingResourceUnavailable (554), 1949 versionMismatch_X733 (555), 1950 -- The following are defined in X.736 1951 authenticationFailure (600), 1952 breachOfConfidentiality (601), 1953 cableTamper (602), 1954 delayedInformation (603), 1955 denialOfService (604), 1956 duplicateInformation (605), 1957 informationMissing (606), 1958 informationModificationDetected (607), 1959 informationOutOfSequence (608), 1960 keyExpired (609), 1961 nonRepudiationFailure (610), 1962 outOfHoursActivity (611), 1963 outOfService (612), 1964 proceduralError (613), 1965 unauthorizedAccessAttempt (614), 1966 unexpectedInformation (615), 1968 other (1024) 1969 } 1971 IANAItuEventType ::= TEXTUAL-CONVENTION 1972 STATUS current 1973 DESCRIPTION 1974 "The ITU event Type values as per M.3100" 1975 SYNTAX INTEGER 1976 { 1977 other (1), 1978 communicationsAlarm (2), 1979 qualityOfServiceAlarm (3), 1980 processingErrorAlarm (4), 1981 equipmentAlarm (5), 1982 environmentalAlarm (6), 1983 integrityViolation (7), 1984 operationalViolation (8), 1985 physicalViolation (9), 1986 securityServiceOrMechanismViolation (10), 1987 timeDomainViolation (11) 1988 } 1990 END 1992 5.3 Textual Conventions 1994 ITU-ALARM-TC DEFINITIONS ::= BEGIN 1996 IMPORTS 1997 MODULE-IDENTITY, mib-2 FROM SNMPv2-SMI 1998 TEXTUAL-CONVENTION FROM SNMPv2-TC; 1999 alarmItuTc MODULE-IDENTITY 2000 LAST-UPDATED "200202040000Z" 2001 ORGANIZATION "IETF Distributed Management Working Group" 2002 CONTACT-INFO 2003 " WG EMail: disman@dorothy.bmc.com 2004 Subscribe: disman-request@dorothy.bmc.com 2006 Chair: Randy Presuhn 2007 BMC Software, Inc. 2008 Office 1-3141 2009 2141 North First Street 2010 San Jose, California 95131 2011 USA 2012 rpresuhn@bmc.com 2013 +1 408 546-1006 2015 Editors: Sharon Chisholm 2016 Nortel Networks 2017 PO Box 3511 Station C 2018 Ottawa, Ont. K1Y 4H7 2019 Canada 2020 schishol@nortelnetworks.com 2022 Dan Romascanu 2023 Avaya Inc. 2024 Atidim Technology Park, Bldg. #3 2025 Tel Aviv, 61131 2026 Israel 2027 Tel: +972-3-645-8414 2028 Email: dromasca@avaya.com" 2029 DESCRIPTION 2030 "The MIB module defines the ITU Alarm 2031 textual convention for objects not expected to require 2032 regular extension." 2033 REVISION "200202040000Z" 2034 DESCRIPTION 2035 "Initial version, published as RFC XXXX." 2036 ::= { mib-2 xx } 2038 ItuPerceivedSeverity ::= TEXTUAL-CONVENTION 2039 STATUS current 2040 DESCRIPTION 2041 "ITU perceived severity values as per M.3100 2042 and X.733" 2043 SYNTAX INTEGER { 2044 cleared (1), 2045 indeterminate (2), 2046 critical (3), 2047 major (4), 2048 minor (5), 2049 warning (6) 2050 } 2052 ItuTrendIndication ::= TEXTUAL-CONVENTION 2053 STATUS current 2054 DESCRIPTION 2055 "ITU trend indication values for alarms 2056 as per [M.3100] and [X.733]." 2057 SYNTAX INTEGER 2058 { 2059 moreSevere (1), 2060 noChange (2), 2061 lessSevere (3) 2062 } 2064 END 2066 5.4 Definitions 2068 ITU-ALARM-MIB DEFINITIONS ::= BEGIN 2070 IMPORTS 2071 MODULE-IDENTITY, OBJECT-TYPE, 2072 Counter32, Gauge32, mib-2 FROM SNMPv2-SMI 2073 AutonomousType, RowPointer FROM SNMPv2-TC 2074 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 2075 alarmListName, alarmModelIndex, 2076 alarmActiveDateAndTime, alarmActiveIndex 2077 FROM ALARM-MIB 2078 ItuPerceivedSeverity, 2079 ItuTrendIndication FROM ITU-ALARM-TC 2080 IANAItuProbableCause, 2081 IANAItuEventType FROM IANA-ITU-ALARM-TC 2082 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 2084 ituAlarmMIB MODULE-IDENTITY 2085 LAST-UPDATED "200209280000Z" 2086 ORGANIZATION "IETF Distributed Management Working Group" 2087 CONTACT-INFO 2088 "WG EMail: disman@dorothy.bmc.com 2089 Subscribe: disman-request@dorothy.bmc.com 2091 Chair: Randy Presuhn 2092 BMC Software, Inc. 2093 Office 1-3141 2094 2141 North First Street 2095 San Jose, California 95131 2096 USA 2097 rpresuhn@bmc.com 2098 +1 408 546-1006 2100 Editors: Sharon Chisholm 2101 Nortel Networks 2102 PO Box 3511 Station C 2103 Ottawa, Ont. K1Y 4H7 2104 Canada 2105 schishol@nortelnetworks.com 2107 Dan Romascanu 2108 Avaya Inc. 2109 Atidim Technology Park, Bldg. #3 2110 Tel Aviv, 61131 2111 Israel 2112 Tel: +972-3-645-8414 2113 Email: dromasca@avaya.com" 2114 DESCRIPTION 2115 "The MIB module describes ITU Alarm information 2116 as defined in ITU Recommendation M.3100 [M.3100], 2117 X.733 [X.733] and X.736 [X.736]." 2119 REVISION "200209280000Z" 2120 DESCRIPTION 2121 "Initial version, published as RFC XXXX." 2122 ::= { mib-2 xx } 2124 ituAlarmObjects OBJECT IDENTIFIER ::= { ituAlarmMIB 1 } 2126 ituAlarmModel OBJECT IDENTIFIER ::= { ituAlarmObjects 1 } 2128 ituAlarmActive OBJECT IDENTIFIER ::= { ituAlarmObjects 2 } 2130 ituAlarmTable OBJECT-TYPE 2131 SYNTAX SEQUENCE OF ItuAlarmEntry 2132 MAX-ACCESS not-accessible 2133 STATUS current 2134 DESCRIPTION 2135 "A table of ITU Alarm information for possible alarms 2136 on the system." 2137 ::= { ituAlarmModel 1 } 2139 ituAlarmEntry OBJECT-TYPE 2140 SYNTAX ItuAlarmEntry 2141 MAX-ACCESS not-accessible 2142 STATUS current 2143 DESCRIPTION 2144 "Entries appear in this table for each possible alarm 2145 severity." 2146 INDEX { alarmListName, alarmModelIndex, 2147 ituAlarmPerceivedSeverity } 2148 ::= { ituAlarmTable 1 } 2150 ItuAlarmEntry ::= SEQUENCE { 2151 ituAlarmPerceivedSeverity ItuPerceivedSeverity, 2152 ituAlarmEventType IANAItuEventType, 2153 ituAlarmProbableCause IANAItuProbableCause, 2154 ituAlarmAdditionalText SnmpAdminString, 2155 ituAlarmGenericModel RowPointer } 2157 ituAlarmPerceivedSeverity OBJECT-TYPE 2158 SYNTAX ItuPerceivedSeverity 2159 MAX-ACCESS not-accessible 2160 STATUS current 2161 DESCRIPTION 2162 " ITU perceived severity values as per [M.3100] and 2163 [X.733]." 2164 ::= { ituAlarmEntry 1 } 2166 ituAlarmEventType OBJECT-TYPE 2167 SYNTAX IANAItuEventType 2168 MAX-ACCESS read-write 2169 STATUS current 2170 DESCRIPTION 2171 " Represents the event type values for the alarms as per 2172 [M.3100], [X.733] and [X.736]" 2173 ::= { ituAlarmEntry 2 } 2175 ituAlarmProbableCause OBJECT-TYPE 2176 SYNTAX IANAItuProbableCause 2177 MAX-ACCESS read-write 2178 STATUS current 2180 DESCRIPTION 2181 " ITU probable cause values as per [M.3100], 2182 [X.733] and [X.736]." 2183 ::= { ituAlarmEntry 3 } 2185 ituAlarmAdditionalText OBJECT-TYPE 2186 SYNTAX SnmpAdminString 2187 MAX-ACCESS read-write 2188 STATUS current 2189 DESCRIPTION 2190 " Represents the additional text field for the alarm 2191 as per [M.3100] and [X.733]." 2192 ::= { ituAlarmEntry 4} 2194 ituAlarmGenericModel OBJECT-TYPE 2195 SYNTAX RowPointer 2196 MAX-ACCESS read-write 2197 STATUS current 2198 DESCRIPTION 2199 "This object points to the corresponding 2200 row in the alarmModelTable for this alarm severity." 2201 ::= { ituAlarmEntry 5 } 2203 -- ITU Active Alarm Table -- 2205 ituAlarmActiveTable OBJECT-TYPE 2206 SYNTAX SEQUENCE OF ItuAlarmActiveEntry 2207 MAX-ACCESS not-accessible 2208 STATUS current 2209 DESCRIPTION 2210 "A table of ITU information for active alarms entries." 2211 ::= { ituAlarmActive 1 } 2213 ituAlarmActiveEntry OBJECT-TYPE 2214 SYNTAX ItuAlarmActiveEntry 2215 MAX-ACCESS not-accessible 2216 STATUS current 2217 DESCRIPTION 2218 "Entries appear in this table when alarms are active. They 2219 are removed when the alarm is no longer occurring." 2220 INDEX { alarmListName, alarmActiveDateAndTime, 2221 alarmActiveIndex } 2222 ::= { ituAlarmActiveTable 1 } 2224 ItuAlarmActiveEntry ::= SEQUENCE { 2225 ituAlarmActiveTrendIndication ItuTrendIndication, 2226 ituAlarmActiveDetector AutonomousType, 2227 ituAlarmActiveServiceProvider AutonomousType, 2228 ituAlarmActiveServiceUser AutonomousType 2229 } 2231 ituAlarmActiveTrendIndication OBJECT-TYPE 2232 SYNTAX ItuTrendIndication 2233 MAX-ACCESS read-only 2234 STATUS current 2235 DESCRIPTION 2236 " Represents the trend indication values for the alarms 2237 as per [M.3100] and [X.733]." 2238 ::= { ituAlarmActiveEntry 1 } 2240 ituAlarmActiveDetector OBJECT-TYPE 2241 SYNTAX AutonomousType 2242 MAX-ACCESS read-only 2243 STATUS current 2244 DESCRIPTION 2245 "Represents the SecurityAlarmDetector object from [X.736]." 2246 ::= { ituAlarmActiveEntry 2 } 2248 ituAlarmActiveServiceProvider OBJECT-TYPE 2249 SYNTAX AutonomousType 2250 MAX-ACCESS read-only 2251 STATUS current 2252 DESCRIPTION 2253 "Represents the ServiceProvider object from [X.736]." 2254 ::= { ituAlarmActiveEntry 3 } 2256 ituAlarmActiveServiceUser OBJECT-TYPE 2257 SYNTAX AutonomousType 2258 MAX-ACCESS read-only 2259 STATUS current 2260 DESCRIPTION 2261 "Represents the SericeUser object from [X.736]." 2262 ::= { ituAlarmActiveEntry 4 } 2264 -- Statistics and Counters 2266 ituAlarmActiveStatsTable OBJECT-TYPE 2267 SYNTAX SEQUENCE OF ItuAlarmActiveStatsEntry 2268 MAX-ACCESS not-accessible 2269 STATUS current 2270 DESCRIPTION 2271 "This table represents the ITU alarm statistics 2272 information." 2273 ::= { ituAlarmActive 2 } 2275 ituAlarmActiveStatsEntry OBJECT-TYPE 2276 SYNTAX ItuAlarmActiveStatsEntry 2277 MAX-ACCESS not-accessible 2278 STATUS current 2279 DESCRIPTION 2280 "Statistics on the current active ITU alarms." 2281 INDEX { alarmListName } 2283 ::= { ituAlarmActiveStatsTable 1 } 2285 ItuAlarmActiveStatsEntry ::= 2286 SEQUENCE { 2287 ituAlarmActiveStatsIndeterminateCurrent Gauge32, 2288 ituAlarmActiveStatsCriticalCurrent Gauge32, 2289 ituAlarmActiveStatsMajorCurrent Gauge32, 2290 ituAlarmActiveStatsMinorCurrent Gauge32, 2291 ituAlarmActiveStatsWarningCurrent Gauge32, 2292 ituAlarmActiveStatsIndeterminates Counter32, 2293 ituAlarmActiveStatsCriticals Counter32, 2294 ituAlarmActiveStatsMajors Counter32, 2295 ituAlarmActiveStatsMinors Counter32, 2296 ituAlarmActiveStatsWarnings Counter32 2297 } 2299 ituAlarmActiveStatsIndeterminateCurrent OBJECT-TYPE 2300 SYNTAX Gauge32 2301 MAX-ACCESS read-only 2302 STATUS current 2303 DESCRIPTION 2304 "A count of the current number of active alarms with a 2305 ituAlarmPerceivedSeverity of indeterminate." 2307 ::= { ituAlarmActiveStatsEntry 1 } 2309 ituAlarmActiveStatsCriticalCurrent OBJECT-TYPE 2310 SYNTAX Gauge32 2311 MAX-ACCESS read-only 2312 STATUS current 2313 DESCRIPTION 2314 "A count of the current number of active alarms with a 2315 ituAlarmPerceivedSeverity of critical." 2316 ::= { ituAlarmActiveStatsEntry 2 } 2318 ituAlarmActiveStatsMajorCurrent OBJECT-TYPE 2319 SYNTAX Gauge32 2320 MAX-ACCESS read-only 2321 STATUS current 2322 DESCRIPTION 2323 "A count of the current number of active alarms with a 2324 ituAlarmPerceivedSeverity of major." 2325 ::= { ituAlarmActiveStatsEntry 3 } 2327 ituAlarmActiveStatsMinorCurrent OBJECT-TYPE 2328 SYNTAX Gauge32 2329 MAX-ACCESS read-only 2330 STATUS current 2331 DESCRIPTION 2332 "A count of the current number of active alarms with a 2333 ituAlarmPerceivedSeverity of minor." 2334 ::= { ituAlarmActiveStatsEntry 4 } 2336 ituAlarmActiveStatsWarningCurrent OBJECT-TYPE 2337 SYNTAX Gauge32 2338 MAX-ACCESS read-only 2339 STATUS current 2340 DESCRIPTION 2341 "A count of the current number of active alarms with a 2342 ituAlarmPerceivedSeverity of warning." 2343 ::= { ituAlarmActiveStatsEntry 5 } 2345 ituAlarmActiveStatsIndeterminates OBJECT-TYPE 2346 SYNTAX Counter32 2347 MAX-ACCESS read-only 2348 STATUS current 2349 DESCRIPTION 2350 "A count of the total number of active alarms with a 2351 ituAlarmPerceivedSeverity of indeterminate since system 2352 restart." 2353 ::= { ituAlarmActiveStatsEntry 6 } 2355 ituAlarmActiveStatsCriticals OBJECT-TYPE 2356 SYNTAX Counter32 2357 MAX-ACCESS read-only 2358 STATUS current 2359 DESCRIPTION 2360 "A count of the total number of active alarms with a 2361 ituAlarmPerceivedSeverity of critical since system restart." 2362 ::= { ituAlarmActiveStatsEntry 7 } 2364 ituAlarmActiveStatsMajors OBJECT-TYPE 2365 SYNTAX Counter32 2366 MAX-ACCESS read-only 2367 STATUS current 2368 DESCRIPTION 2369 "A count of the total number of active alarms with a 2370 ituAlarmPerceivedSeverity of major since system restart." 2371 ::= { ituAlarmActiveStatsEntry 8 } 2373 ituAlarmActiveStatsMinors OBJECT-TYPE 2374 SYNTAX Counter32 2375 MAX-ACCESS read-only 2376 STATUS current 2377 DESCRIPTION 2378 "A count of the total number of active alarms with a 2379 ituAlarmPerceivedSeverity of minor since system restart." 2380 ::= { ituAlarmActiveStatsEntry 9 } 2382 ituAlarmActiveStatsWarnings OBJECT-TYPE 2383 SYNTAX Counter32 2384 MAX-ACCESS read-only 2385 STATUS current 2386 DESCRIPTION 2387 "A count of the total number of active alarms with a 2388 ituAlarmPerceivedSeverity of warning since system restart." 2389 ::= { ituAlarmActiveStatsEntry 10 } 2391 -- Conformance 2393 ituAlarmConformance OBJECT IDENTIFIER ::= { ituAlarmMIB 2 } 2394 ituAlarmCompliances OBJECT IDENTIFIER ::= { ituAlarmConformance 1 } 2396 ituAlarmCompliance MODULE-COMPLIANCE 2397 STATUS current 2398 DESCRIPTION 2399 "The compliance statement for systems supporting 2400 the ITU Alarm MIB." 2401 MODULE -- this module 2402 MANDATORY-GROUPS { 2403 ituAlarmGroup 2404 } 2405 ::= { ituAlarmCompliances 1 } 2407 ituAlarmGroups OBJECT IDENTIFIER ::= { ituAlarmConformance 2 } 2409 ituAlarmGroup OBJECT-GROUP 2410 OBJECTS { 2411 ituAlarmEventType, 2412 ituAlarmProbableCause, 2413 ituAlarmGenericModel 2414 } 2415 STATUS current 2416 DESCRIPTION 2417 "ITU alarm details list group." 2418 ::= { ituAlarmGroups 1} 2420 ituAlarmServiceUserGroup OBJECT-GROUP 2421 OBJECTS { 2422 ituAlarmAdditionalText, 2423 ituAlarmActiveTrendIndication 2424 } 2425 STATUS current 2426 DESCRIPTION 2427 "The use of these parameters is a service-user option." 2428 ::= { ituAlarmGroups 2 } 2430 ituAlarmSecurityGroup OBJECT-GROUP 2431 OBJECTS { 2432 ituAlarmActiveDetector, 2433 ituAlarmActiveServiceProvider, 2434 ituAlarmActiveServiceUser 2435 } 2436 STATUS current 2437 DESCRIPTION 2438 "Security Alarm Reporting Function as defined in [X.736]" 2439 ::= { ituAlarmGroups 3 } 2441 ituAlarmStatisticsGroup OBJECT-GROUP 2442 OBJECTS { 2443 ituAlarmActiveStatsIndeterminateCurrent, 2444 ituAlarmActiveStatsCriticalCurrent, 2445 ituAlarmActiveStatsMajorCurrent, 2446 ituAlarmActiveStatsMinorCurrent, 2447 ituAlarmActiveStatsWarningCurrent, 2448 ituAlarmActiveStatsIndeterminates, 2449 ituAlarmActiveStatsCriticals, 2450 ituAlarmActiveStatsMajors, 2451 ituAlarmActiveStatsMinors, 2452 ituAlarmActiveStatsWarnings 2453 } 2454 STATUS current 2455 DESCRIPTION 2456 "ITU Active Alarm Statistics." 2457 ::= { ituAlarmGroups 4 } 2459 END 2461 6. Examples 2463 6.1 Alarms Based on linkUp/linkDown Notifications 2465 This example demonstrates an interface-based alarm that goes into a 2466 state of "warning" when a linkDown Notification occurs but the 2467 ifAdminStatus indicates the interface was taken down 2468 administratively. If IfAdminStatus is "up" when the linkDown 2469 Notification occurs, then there is a problem, so the state of the 2470 alarm is critical. A linkUp alarm clears the alarm. 2472 linkDown NOTIFICATION-TYPE 2473 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 2474 STATUS current 2475 DESCRIPTION 2476 "" 2477 ::= { snmpTraps 3 } 2479 linkUp NOTIFICATION-TYPE 2480 OBJECTS { ifIndex, ifAdminStatus, ifOperStatus } 2481 STATUS current 2482 DESCRIPTION 2483 "" 2484 ::= { snmpTraps 4 } 2486 alarmModelIndex 3 2487 alarmModelState 1 2488 alarmModelNotificationId linkUp 2489 alarmModelVarbindIndex 0 2490 alarmModelVarbindValue 0 2491 alarmModelDescription "linkUp" 2492 alarmModelSpecificPointer ituAlarmEntry.3.1 2493 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2494 alarmModelResourcePrefix 0.0 2495 alarmModelRowStatus active (1) 2496 ituAlarmEventType communicationsAlarm (2) 2497 ituAlarmPerceivedSeverity cleared (1) 2498 ituAlarmGenericModel alarmModelEntry.3.1 2500 alarmModelIndex 3 2501 alarmModelState 2 2502 alarmModelNotificationId linkDown 2503 alarmModelVarbindIndex 2 2504 alarmModelVarbindValue down (2) 2505 alarmModelDescription "linkDown administratively" 2506 alarmModelSpecificPointer ituAlarmEntry.3.6 2507 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2508 alarmModelResourcePrefix 0.0 2509 alarmModelRowStatus active (1) 2510 ituAlarmEventType communicationsAlarm (2) 2511 ituAlarmPerceivedSeverity warning (6) 2512 ituAlarmGenericModel alarmModelEntry.3.2 2514 alarmModelIndex 3 2515 alarmModelState 3 2516 alarmModelNotificationId linkDown 2517 alarmModelVarbindIndex 2 2518 alarmModelVarbindValue up (1) 2519 alarmModelDescription "linkDown - confirmed problem" 2520 alarmModelSpecificPointer ituAlarmEntry.3.3 2521 alarmModelVarbindSubtree ifIndex (1.3.6.1.2.1.2.2.1.1) 2522 alarmModelResourcePrefix 0.0 2523 alarmModelRowStatus active (1) 2524 ituAlarmEventType communicationsAlarm (2) 2525 ituAlarmPerceivedSeverity critical (3) 2526 ituAlarmGenericModel alarmModelEntry.3.3 2528 alarmActiveIndex 1 2529 alarmActiveTime 2342464573 2530 alarmActiveDateAndTime DateAndTime, 2531 alarmActiveEngineID SnmpEngineID, 2532 alarmActiveEngineAddressType ipV4 2533 alarmActiveEngineAddress 10.10.10.10 2534 alarmActiveContextName SnmpAdminString, 2535 alarmActiveVariables 3 2536 alarmActiveNotificationID 1.3.6.1.6.3.1.1.5.3 2537 alarmActiveResourceId 1.3.6.1.2.1.2.2.1.1.346 2538 alarmActiveLogPointer 0.0 2539 alarmActiveModelPointer alarmModelEntry.3.3 2540 alarmActiveSpecificPointer ituAlarmActiveEntry.1.3 2541 ituAlarmActiveTrendIndication moreSevere (1) 2542 ituAlarmDetector 0.0 2543 ituAlarmServiceProvider 0.0 2544 ituAlarmServiceUser 0.0 2546 alarmActiveVariableIndex 1 2547 alarmActiveVariableID sysUpTime.0 2548 alarmActiveVariableValueType timeTicks(3) 2549 alarmActiveVariableCounter32Val 0 2550 alarmActiveVariableUnsigned32Val 0 2551 alarmActiveVariableTimeTicksVal 46754 2552 alarmActiveVariableInteger32Val 0 2553 alarmActiveVariableOctetStringVal "" 2554 alarmActiveVariableIpAddressVal 0 2555 alarmActiveVariableOidVal 0.0 2556 alarmActiveVariableCounter64Val 0 2557 alarmActiveVariableIndex 2 2558 alarmActiveVariableID snmpTrapOID.0 2559 alarmActiveVariableValueType objectId(7) 2560 alarmActiveVariableCounter32Val 0 2561 alarmActiveVariableUnsigned32Val 0 2562 alarmActiveVariableTimeTicksVal 0 2563 alarmActiveVariableInteger32Val 0 2564 alarmActiveVariableOctetStringVal "" 2565 alarmActiveVariableIpAddressVal 0 2566 alarmActiveVariableOidVal 1.3.6.1.6.3.1.1.5.3 2567 alarmActiveVariableCounter64Val 0 2568 alarmActiveVariableIndex 3 2569 alarmActiveVariableID ifIndex 2570 alarmActiveVariableValueType integer32(4) 2571 alarmActiveVariableCounter32Val 0 2572 alarmActiveVariableUnsigned32Val 0 2573 alarmActiveVariableTimeTicksVal 0 2574 alarmActiveVariableInteger32Val 346 2575 alarmActiveVariableOctetStringVal "" 2576 alarmActiveVariableIpAddressVal 0 2577 alarmActiveVariableOidVal 0.0 2578 alarmActiveVariableCounter64Val 0 2579 alarmActiveVariableIndex 4 2580 alarmActiveVariableID ifAdminStatus 2581 alarmActiveVariableValueType integer32(4) 2582 alarmActiveVariableCounter32Val 0 2583 alarmActiveVariableUnsigned32Val 0 2584 alarmActiveVariableTimeTicksVal 0 2585 alarmActiveVariableInteger32Val up (1) 2586 alarmActiveVariableOctetStringVal "" 2587 alarmActiveVariableIpAddressVal 0 2588 alarmActiveVariableOidVal 0.0 2589 alarmActiveVariableCounter64Val 0 2590 alarmActiveVariableIndex 5 2591 alarmActiveVariableID ifOperStatus 2592 alarmActiveVariableValueType integer32(4) 2593 alarmActiveVariableCounter32Val 0 2594 alarmActiveVariableUnsigned32Val 0 2595 alarmActiveVariableTimeTicksVal 0 2596 alarmActiveVariableInteger32Val down(2) 2597 alarmActiveVariableOctetStringVal "" 2598 alarmActiveVariableIpAddressVal 0 2599 alarmActiveVariableOidVal 0.0 2600 alarmActiveVariableCounter64Val 0 2601 alarmActiveVariableOpaqueVal 2603 6.2 Temperature Alarms Using Generic Notifications 2605 Consider a system able to detect four different temperature 2606 states for a widget - normal, minor, major, critical. The 2607 system does not have any Notification definitions for these 2608 alarm states. A temperature alarm can be modelled using the 2609 generic alarm Notifications of alarmClearState and alarmActive. 2611 alarmModelIndex 5 2612 alarmModelState 1 2613 alarmModelNotificationId alarmClearState 2614 alarmModelVarbindIndex 2 2615 alarmModelVarbindValue cleared (1) 2616 alarmModelDescription "Acme Widget Temperature Normal" 2617 alarmModelSpecificPointer ituAlarmEntry.5.1 2618 alarmModelVarbindSubtree alarmActiveResourceId 2619 alarmModelResourcePrefix 0.0 2620 alarmModelRowStatus active (1) 2621 ituAlarmEventType environmentalAlarm (6) 2622 ituPerceivedSeverity cleared (1) 2623 ituAlarmGenericModel alarmModelEntry.5.1 2625 alarmModelIndex 5 2626 alarmModelState 2 2627 alarmModelNotificationId alarmActiveState 2628 alarmModelVarbindIndex 2 2629 alarmModelVarbindValue minor (5) 2630 alarmModelDescription "Acme Widget Temperature Minor" 2631 alarmModelSpecificPointer ituAlarmEntry.5.5 2632 alarmModelVarbindSubtree alarmActiveResourceId 2633 alarmModelResourcePrefix 0.0 2634 alarmModelRowStatus active (1) 2635 ituAlarmEventState environmentalAlarm (6) 2636 ituPerceivedSeverity minor (5) 2637 ituAlarmGenericModel alarmModelEntry.5.2 2639 alarmModelIndex 5 2640 alarmModelState 3 2641 alarmModelNotificationId alarmActiveState 2642 alarmModelVarbindIndex 2 2643 alarmModelVarbindValue major (4) 2644 alarmModelDescription "Acme Widget Temperature Major" 2645 alarmModelSpecificPointer ituAlarmEntry.5.4 2646 alarmModelVarbindSubtree alarmActiveResourceId 2647 alarmModelResourcePrefix 0.0 2648 alarmModelRowStatus active (1) 2649 ituAlarmEventType environmentalAlarm (6) 2650 ituPerceivedSeverity major (4) 2651 ituAlarmGenericModel alarmModelEntry.5.3 2653 alarmModelIndex 5 2654 alarmModelState 4 2655 alarmModelNotificationId alarmActiveState 2656 alarmModelVarbindIndex 2 2657 alarmModelVarbindValue critical (3) 2658 alarmModelDescription "Acme Widget Temperature Critical" 2659 alarmModelSpecificPointer ituAlarmEntry.5.3 2660 alarmModelVarbindSubtree alarmActiveResourceId 2661 alarmModelResourcePrefix 0.0 2662 alarmModelRowStatus active (1) 2663 ituAlarmEventType environmentalAlarm (6) 2664 ituPerceivedSeverity critical (3) 2665 ituAlarmGenericModel alarmModelEntry.5.4 2667 6.3 Temperature Alarms Without Notifications 2669 Consider a system able to detect four different temperature 2670 states for a widget - normal, minor, major, critical. The 2671 system does not have any Notification definitions for these 2672 alarm states. A temperature alarm can be modelled without 2673 specifying any Notifications in the alarm model. When a 2674 temperature state other than normal is detected, an instance 2675 of this alarm would be added to the active alarm table, but 2676 no Notifications would be sent out. 2678 This could alternatively be accomplished using the models from 2679 example 6.2 and by not specifying any target managers in the 2680 SNMP-TARGET-MIB, which would allow the alarm state 2681 Notifications to be logged in the Notification log while 2682 still preventing Notifications from being transmitted 2683 on the wire. 2685 alarmModelIndex 6 2686 alarmModelState 1 2687 alarmModelNotificationId 0.0 2688 alarmModelVarbindIndex 0 2689 alarmModelVarbindValue 0 2690 alarmModelDescription "Widget Temperature" 2691 alarmModelSpecificPointer ituAlarmEntry.6.1 2692 alarmModelVarbindSubtree 0.0 2693 alarmModelResourcePrefix 0.0 2694 alarmModelRowStatus active (1) 2695 ituAlarmEventType environmentalAlarm (6) 2696 ituPerceivedSeverity cleared (1) 2697 ituAlarmGenericModel alarmModelEntry.6.1 2699 alarmModelIndex 6 2700 alarmModelState 2 2701 alarmModelNotificationId 0.0 2702 alarmModelVarbindIndex 0 2703 alarmModelVarbindValue 0 2704 alarmModelDescription "Widget Temperature" 2705 alarmModelSpecificPointer ituAlarmEntry.6.5 2706 alarmModelVarbindSubtree 0.0 2707 alarmModelResourcePrefix 0.0 2708 alarmModelRowStatus active (1) 2709 ituAlarmEventState environmentalAlarm (6) 2710 ituAlarmPerceivedSeverity minor (5) 2711 ituAlarmGenericModel alarmModelEntry.6.2 2713 alarmModelIndex 6 2714 alarmModelState 3 2715 alarmModelNotificationId 0.0 2716 alarmModelVarbindIndex 0 2717 alarmModelVarbindValue 0 2718 alarmModelDescription "Widget Temperature" 2719 alarmModelSpecificPointer ituAlarmEntry.6.4 2720 alarmModelVarbindSubtree 0.0 2721 alarmModelResourcePrefix 0.0 2722 alarmModelRowStatus active (1) 2723 ituAlarmEventType environmentalAlarm (6) 2724 ituPerceivedSeverity major (4) 2725 ituAlarmGenericModel alarmModelEntry.6.3 2727 alarmModelIndex 6 2728 alarmModelState 4 2729 alarmModelNotificationId 0.0 2730 alarmModelVarbindIndex 0 2731 alarmModelVarbindValue 0 2732 alarmModelDescription "Widget Temperature Severe" 2733 alarmModelSpecificPointer ituAlarmEntry.6.3 2734 alarmModelVarbindSubtree 0.0 2735 alarmModelResourcePrefix 0.0 2736 alarmModelRowStatus active (1) 2737 ituAlarmEventType environmentalAlarm (6) 2738 ituPerceivedSeverity critical (3) 2739 ituAlarmGenericModel alarmModelEntry.6.4 2741 6.4 Printer MIB Alarm Example 2743 Consider the following Notifications defined in the 2744 printer MIB [RFC1759]: 2746 prtAlertSeverityLevel OBJECT-TYPE 2747 -- This value is a type 1 enumeration 2748 SYNTAX INTEGER { 2749 other(1), 2750 critical(3), 2751 warning(4) 2752 } 2753 MAX-ACCESS read-only 2754 STATUS current 2755 DESCRIPTION 2756 "The level of severity of this alert table entry. The printer 2757 determines the severity level assigned to each entry into the 2758 table." 2759 ::= { prtAlertEntry 2 } 2761 printerV2Alert NOTIFICATION-TYPE 2762 OBJECTS { prtAlertIndex, prtAlertSeverityLevel, prtAlertGroup, 2763 prtAlertGroupIndex, prtAlertLocation, prtAlertCode } 2765 STATUS current 2766 DESCRIPTION 2767 "This trap is sent whenever a critical event is added to the 2768 prtAlertTable." 2769 ::= { printerV2AlertPrefix 1 } 2771 These Notifications can be used to model a printer alarm as 2772 follows: 2774 alarmModelIndex 9 2775 alarmModelState 1 2776 alarmModelNotificationId alarmClearState 2777 alarmModelVarbindIndex 0 2778 alarmModelVarbindValue 0 2779 alarmModelDescription "Printer Alarm" 2780 alarmModelSpecificPointer 0.0 2781 alarmModelVarbindSubtree prtAlertGroup 2782 alarmModelResourcePrefix 0.0 2783 alarmModelRowStatus active (1) 2785 alarmModelIndex 9 2786 alarmModelState 2 2787 alarmModelNotificationId printerV2Alert 2788 alarmModelVarbindIndex 2 2789 alarmModelVarbindValue warning (4) 2790 alarmModelDescription "Printer Alarm" 2791 alarmModelSpecificPointer 0.0 2792 alarmModelVarbindSubtree prtAlertGroup 2793 alarmModelResourcePrefix 0.0 2794 alarmModelRowStatus active (1) 2796 alarmModelIndex 9 2797 alarmModelState 3 2798 alarmModelNotificationId printerV2Alert 2799 alarmModelVarbindIndex 2 2800 alarmModelVarbindValue other (1) 2801 alarmModelDescription "Printer Alarm - unknown severity" 2802 alarmModelSpecificPointer 0.0 2803 alarmModelVarbindSubtree prtAlertGroup 2804 alarmModelResourcePrefix 0.0 2805 alarmModelRowStatus active (1) 2807 alarmModelIndex 9 2808 alarmModelState 4 2809 alarmModelNotificationId printerV2Alert 2810 alarmModelVarbindIndex 2 2811 alarmModelVarbindValue critical (3) 2812 alarmModelDescription "Printer Alarm" 2813 alarmModelSpecificPointer 0.0 2814 alarmModelVarbindSubtree prtAlertGroup 2815 alarmModelResourcePrefix 0.0 2816 alarmModelRowStatus active (1) 2818 6.5 RMON Alarm Example 2820 The RMON MIB [RFC2819] defines a mechanism for generating 2821 threshold alarms. When the thresholds are crossed, 2822 RisingAlarm and FallingAlarm Notifications are 2823 generated as appropriate. These Notifications can 2824 be used to model an upper threshold alarm as follows: 2826 alarmModelIndex 6 2827 alarmModelState 1 2828 alarmModelNotificationId FallingAlarm 2829 alarmModelVarbindIndex 0 2830 alarmModelVarbindValue 0 2831 alarmModelDescription "RMON Rising Clear Alarm" 2832 alarmModelSpecificPointer 0.0 2833 alarmModelVarbindSubtree alarmIndex 2834 alarmModelResourcePrefix 0.0 2835 alarmModelRowStatus active (1) 2837 alarmModelIndex 6 2838 alarmModelState 2 2839 alarmModelNotificationId RisingAlarm 2840 alarmModelVarbindIndex 0 2841 alarmModelVarbindValue 0 2842 alarmModelDescription "RMON Rising Alarm" 2843 alarmModelSpecificPointer 0.0 2844 alarmModelRowStatus active (1) 2845 alarmModelVarbindSubtree alarmIndex 2846 alarmModelResourcePrefix 0.0 2847 alarmModelRowStatus active (1) 2849 6.6 The Lifetime of an Alarm 2851 The following example demonstrates the relationship between 2852 the active alarm table, the clear alarm table and the 2853 Notification log MIB. 2855 Consider a system with alarms modelled as in example 1 and which 2856 also supports the informational Notification dsx3LineStatusChange. 2858 dsx3LineStatusChange NOTIFICATION-TYPE 2859 OBJECTS { dsx3LineStatus, 2860 dsx3LineStatusLastChange } 2861 STATUS current 2862 DESCRIPTION 2863 "A dsx3LineStatusChange trap is sent when the 2864 value of an instance of dsx3LineStatus changes. It 2865 can be utilized by an NMS to trigger polls. When 2866 the line status change results in a lower level 2867 line status change (i.e. ds1), then no traps for 2868 the lower level are sent." 2869 ::= { ds3Traps 0 1 } 2871 0. At system start, the active alarm table, alarm clear table and 2872 the Notification log are all empty. 2873 ___________________________ _______________________ 2874 | alarmActiveTable | | nlmLogTable | 2875 |---------------------------| |-----------------------| 2876 | alarmActiveIndex | alarm | | nlmLogPointer | notif.| 2877 |---------------------------| |-----------------------| 2878 |___________________________| |_______________________| 2880 __________________________________________________ 2881 | alarmClearTable | 2882 |--------------------------------------------------| 2883 | alarmClear Index | alarm | 2884 |--------------------------------------------------| 2885 | | | 2886 |__________________________________________________| 2888 1. Some time later, a link goes down generating a linkDown 2889 Notification, which is sent out and logged in the 2890 Notification log. As this Notification is modelled as 2891 an alarm state, an entry is added to the active alarm 2892 table. 2893 __________________________________________________ 2894 | alarmActiveTable | 2895 |--------------------------------------------------| 2896 | alarmActiveIndex | alarm | 2897 |--------------------------------------------------| 2898 | 1 | link down - problem confirmed | 2899 |__________________________________________________| 2901 _______________________________________________ 2902 | nlmLogTable | 2903 |-----------------------------------------------| 2904 | nlmLogPointer | Notification | 2905 |-----------------------------------------------| 2906 | 1 | linkdown | 2907 |_______________________________________________| 2909 __________________________________________________ 2910 | alarmClearTable | 2911 |--------------------------------------------------| 2912 | alarmClear Index | alarm | 2913 |--------------------------------------------------| 2914 | | | 2915 |__________________________________________________| 2917 2. Some time later, the value of an instance of dsx3LineStatus 2918 changes. This Notification is sent out and logged. As this 2919 is not modelled into an alarm state, the active alarm table 2920 remains unchanged. 2921 __________________________________________________ 2922 | alarmActiveTable | 2923 |--------------------------------------------------| 2924 | alarmActiveIndex | alarm | 2925 |--------------------------------------------------| 2926 | 1 | linkDown - problem confirmed | 2927 |__________________________________________________| 2929 _____________________________________________ 2930 | nlmLogTable | 2931 |---------------------------------------------| 2932 | nlmLogPointer | Notification | 2933 |---------------------------------------------| 2934 | 1 | linkDown | 2935 | 2 | dsx3LineStatusChange | 2936 |_____________________________________________| 2938 __________________________________________________ 2939 | alarmClearTable | 2940 |--------------------------------------------------| 2941 | alarmClear Index | alarm | 2942 |--------------------------------------------------| 2943 | | | 2944 |__________________________________________________| 2946 3. Some time later, the link goes back up. A linkUp Notification 2947 is sent out and logged. As this Notification models 2948 the clear alarm for this alarm, the alarm entry is remove 2949 from the active alarm table. An entry is added to the 2950 clear alarm table. 2951 __________________________________________________ 2952 | alarmActiveTable | 2953 |--------------------------------------------------| 2954 | alarmActiveIndex | alarm | 2955 |--------------------------------------------------| 2956 |__________________________________________________| 2958 _____________________________________________ 2959 | nlmLogTable | 2960 |---------------------------------------------| 2961 | nlmLogPointer | Notification | 2962 |---------------------------------------------| 2963 | 1 | linkDown | 2964 | 2 | dsx3LineStatusChange | 2965 | 3 | linkUp | 2966 |_____________________________________________| 2968 __________________________________________________ 2969 | alarmClearTable | 2970 |--------------------------------------------------| 2971 | alarmClear Index | alarm | 2972 |--------------------------------------------------| 2973 | 1 | linkDown - confirmed problem | 2974 |__________________________________________________| 2976 7. Security Considerations 2978 There are a number of management objects defined in this MIB that 2979 have a MAX-ACCESS clause of read-write and/or read-create. Such 2980 objects may be considered sensitive or vulnerable in some network 2981 environments. The support for SET operations in a non-secure 2982 environment without proper protection can have a negative effect on 2983 network operations. 2985 The following objects are defined with a MAX-ACCESS clause of 2986 read-write or read-create: alarmModelNotificationId, 2987 alarmModelVarbindIndex, alarmModelVarbindValue, 2988 alarmModelDescription, alarmModelSpecificPointer, 2989 alarmModelVarbindSubtree, alarmModelResourcePrefix, 2990 alarmModelRowStatus, ituAlarmEventType, ituAlarmProbableCause, 2991 ituAlarmAdditionalText, and ituAlarmGenericModel. 2993 SNMPv1 by itself is not a secure environment. Even if the network 2994 itself is secure (for example by using IPSec), even then, there is 2995 no control as to who on the secure network is allowed to access and 2996 GET/SET (read/change/create/delete) the objects in this MIB. 2998 It is recommended that the implementers consider the security 2999 features as provided by the SNMPv3 framework. Specifically, the use 3000 of the User-based Security Model RFC 2574 [RFC2574] and the 3001 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 3003 It is then a customer/user responsibility to ensure that the SNMP 3004 entity giving access to an instance of this MIB, is properly 3005 configured to give access to the objects only to those principals 3006 (users) that have legitimate rights to indeed GET or SET 3007 (change/create/delete) them. 3009 For further discussion of security, see section 3.4. 3011 8. Authors' Addresses 3013 Sharon Chisholm 3014 Nortel Networks 3015 PO Box 3511, Station C 3016 Ottawa, Ontario, K1Y 4H7 3017 Canada 3018 Email: schishol@nortelnetworks.com 3020 Dan Romascanu 3021 Avaya Inc. 3022 Atidim Technology Park, Bldg. #3 3023 Tel Aviv, 61131 3024 Israel 3025 Tel: +972-3-645-8414 3026 Email: dromasca@avaya.com 3028 9. Acknowledgements 3030 This document is a product of the DISMAN Working Group. 3032 10. References 3034 10.1 Normative References 3036 [M.3100] ITU Recommendation M.3100, "Generic Network Information 3037 Model", 1995 3039 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 3040 of Management Information for TCP/IP-based Internets", STD 3041 16, RFC 1155, May 1990. 3043 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 3044 "Simple Network Management Protocol", STD 15, RFC 1157, 3045 May 1990. 3047 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 3048 STD 16, RFC 1212, March 1991. 3050 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 3051 SNMP", RFC 1215, March 1991. 3053 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3054 "Introduction to Community-based SNMPv2", RFC 1901, 3055 January 1996. 3057 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3058 "Protocol Operations for Version 2 of the Simple Network 3059 Management Protocol (SNMPv2)", RFC 1905, January 1996. 3061 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 3062 "Transport Mappings for Version 2 of the Simple Network 3063 Management Protocol (SNMPv2)", RFC 1906, January 1996. 3065 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 3066 Requirement Levels", BCP 14, RFC 2119, March 1997. 3068 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 3069 "Introduction to Version 3 of the Internet-standard 3070 Network Management Framework", RFC 2570, April 1999. 3072 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 3073 Architecture for Describing SNMP Management Frameworks", 3074 RFC 2571, April 41999. 3076 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 3077 "Message Processing and Dispatching for the Simple 3078 Network Management Protocol (SNMP)", RFC 2572, April 3079 1999. 3081 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 3082 Applications", RFC 2573, April 1999. 3084 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 3085 (USM) for version 3 of the Simple Network Management 3086 Protocol (SNMPv3)", RFC 2574, April 1999. 3088 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 3089 Access Control Model (VACM) for the Simple Network 3090 Management Protocol (SNMP)", RFC 2575, April 1999. 3092 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3093 Rose, M., and S. Waldbusser, "Structure of Management 3094 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 3095 1999. 3097 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3098 Rose, M., and S. Waldbusser, "Textual Conventions for 3099 SMIv2", STD 58, RFC 2579, April 1999. 3101 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 3102 Rose, M., and S. Waldbusser, "Conformance Statements for 3103 SMIv2", STD 58, RFC 2580, April 1999 3105 [X.733] ITU Recommendation X.733, "Information Technology - Open 3106 Systems Interconnection - System Management: Alarm 3107 Reporting Function", 1992 3109 [X.736] ITU Recommendation X.736, "Information Technology - Open 3110 Systems Interconnection - System Management: Security 3111 Alarm Reporting Function", 1992 3113 10.2 Informative References 3115 [RFC1759] Smith, R., Wright, F., Hastings, T., Zilles, S., 3116 Gullenskop, J., "Printer MIB", RFC 1759, March 1995 3118 [RFC2819] Waldbusser, S. "Remote Network Monitoring Management 3119 Information Base", RFC 2819, May 2000 3121 [RFC2037] McCloghrie, K., Brierman, A., "Entity MIB using SMIv2", 3122 RFC2037, October 1996 3124 [RFC2233] McCloghrie, K., Kastenholz, F., "The Interfaces Group 3125 MIB using SMIv2", RFC2233, November 1997 3127 [RFC2788] Freed, N., Kille, S., "Network Services Monitoring MIB", 3128 RFC2788, March 2000 3130 [RFC2981] Kavasseri, R., Stewart, B., "Event MIB", RFC2981, 3131 October 2000 3133 [RFC3014] Stewart, B., Kavasseri, R., "Notification Log MIB, 3134 RFC 3014, November 2000 3136 11. Full Copyright Statement 3138 Copyright (C) The Internet Society (2002). All Rights Reserved. 3140 This document and translations of it may be copied and furnished to 3141 others, and derivative works that comment on or otherwise explain it 3142 or assist in its implementation may be prepared, copied, published 3143 and distributed, in whole or in part, without restriction of any kind, 3144 provided that the above copyright notice and this paragraph are 3145 included on all such copies and derivative works. However, this 3146 document itself may not be modified in any way, such as by removing 3147 the copyright notice or references to the Internet Society or other 3148 Internet organizations, except as needed for the purpose of 3149 developing Internet standards in which case the procedures for 3150 copyrights defined in the Internet Standards process must be followed, 3151 or as required to translate it into languages other than English. 3153 The limited permissions granted above are perpetual and will not be 3154 revoked by the Internet Society or its successors or assigns. 3156 This document and the information contained herein is provided on an 3157 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 3158 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 3159 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 3160 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 3161 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.