idnits 2.17.1 draft-ietf-disman-snmp-alarm-mib-01.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: ---------------------------------------------------------------------------- == No 'Intended status' indicated for this document; assuming Proposed Standard Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- ** The document seems to lack an IANA Considerations section. (See Section 2.2 of https://www.ietf.org/id-info/checklist for how to handle the case when there are no actions for IANA.) ** The document seems to lack separate sections for Informative/Normative References. All references will be assumed normative when checking for downward references. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 362 has weird spacing: '... field octet...' == Line 1390 has weird spacing: '...for the purpo...' -- The document seems to lack a disclaimer for pre-RFC5378 work, but may have content which was first submitted before 10 November 2008. If you have contacted all the original authors and they are all willing to grant the BCP78 rights to the IETF Trust, then this is fine, and you can ignore this comment. If not, you may need to add the pre-RFC5378 disclaimer. (See the Legal Provisions document at https://trustee.ietf.org/license-info for more information.) -- The document date (March 2, 2001) is 8448 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: 'RFC1155' is mentioned on line 61, but not defined == Missing Reference: 'RFC1212' is mentioned on line 61, but not defined == Missing Reference: 'RFC1215' is mentioned on line 62, but not defined == Missing Reference: 'RFC1157' is mentioned on line 77, but not defined == Missing Reference: 'RFC1901' is mentioned on line 71, but not defined == Missing Reference: 'RFC1906' is mentioned on line 73, but not defined ** Obsolete undefined reference: RFC 1906 (Obsoleted by RFC 3417) == Missing Reference: 'RFC2572' is mentioned on line 73, but not defined ** Obsolete undefined reference: RFC 2572 (Obsoleted by RFC 3412) == Missing Reference: 'RFC2574' is mentioned on line 1333, but not defined ** Obsolete undefined reference: RFC 2574 (Obsoleted by RFC 3414) == Missing Reference: 'RFC1905' is mentioned on line 79, but not defined ** Obsolete undefined reference: RFC 1905 (Obsoleted by RFC 3416) == Missing Reference: 'RFC2573' is mentioned on line 82, but not defined ** Obsolete undefined reference: RFC 2573 (Obsoleted by RFC 3413) == Missing Reference: 'RFC2575' is mentioned on line 1334, but not defined ** Obsolete undefined reference: RFC 2575 (Obsoleted by RFC 3415) == Missing Reference: 'RFC2570' is mentioned on line 86, but not defined ** Obsolete undefined reference: RFC 2570 (Obsoleted by RFC 3410) -- Looks like a reference, but probably isn't: '1' on line 115 ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) Summary: 11 errors (**), 0 flaws (~~), 16 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Disman Working Group David T. Perkins 2 Internet Draft SNMPinfo 3 Expires: August 2001 March 2, 2001 5 SNMP Alarms and MIB Module 6 draft-ietf-disman-snmp-alarm-mib-01.txt 8 Status of this Memo 10 This document is an Internet-Draft and is in full conformance 11 with all provisions of Section 10 of RFC2026. 13 Internet-Drafts are working documents of the Internet Engineering 14 Task Force (IETF), its areas, and its working groups. Note that 15 other groups may also distribute working documents as 16 Internet-Drafts. 18 Internet-Drafts are draft documents valid for a maximum of six 19 months and may be updated, replaced, or obsoleted by other documents 20 at any time. It is inappropriate to use Internet-Drafts as 21 reference material or to cite them other than as "work in progress." 23 The list of current Internet-Drafts can be accessed at 24 http://www.ietf.org/ietf/1id-abstracts.txt 26 The list of Internet-Draft Shadow Directories can be accessed at 27 http://www.ietf.org/shadow.html. 29 Abstract 31 This document defines the model for alarms in the SNMP framework and 32 defines a Management Information Base (MIB) module that defines a 33 list of outstanding alarms and log of alarms that have occurred and 34 have been cleared. 36 Table of Contents 38 1. The SNMP Management Framework ..................................3 39 2. Introduction ...................................................4 40 3. Exception Reporting Framework ..................................4 41 3.1 Terminology ..................................................4 43 3.2 Alarm Definitions ............................................4 44 4. MIB Module Overview ............................................6 45 5. Definitions ....................................................7 46 6. Examples ......................................................28 47 7. Security Considerations .......................................28 48 8. Author's Address ..............................................28 49 9. Acknowledgements ..............................................28 50 10. References ..................................................29 52 11. Full Copyright Statement ....................................29 54 1. The SNMP Management Framework 56 o An overall architecture, described in RFC 2571 [RFC2571]. 58 o Mechanisms for describing and naming objects and events for the 59 purpose of management. The first version of this Structure of 60 Management Information (SMI) is called SMIv1 and described in 61 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 62 1215 [RFC1215]. The second version, called SMIv2, is described 63 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 64 STD 58, RFC 2580 [RFC2580]. 66 o Message protocols for transferring management information. The 67 first version of the SNMP message protocol is called SNMPv1 and 68 described in STD 15, RFC 1157 [RFC1157]. A second version of 69 the SNMP message protocol, which is not an Internet standards 70 track protocol, is called SNMPv2c and described in RFC 1901 71 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 72 message protocol is called SNMPv3 and described in RFC 1906 73 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 75 o Protocol operations for accessing management information. The 76 first set of protocol operations and associated PDU formats is 77 described in STD 15, RFC 1157 [RFC1157]. A second set of 78 protocol operations and associated PDU formats is described in 79 RFC 1905 [RFC1905]. 81 o A set of fundamental applications described in RFC 2573 82 [RFC2573] and the view-based access control mechanism described 83 in RFC 2575 [RFC2575]. 85 A more detailed introduction to the current SNMP Management 86 Framework can be found in RFC 2570 [RFC2570]. 88 Managed objects are accessed via a virtual information store, termed 89 the Management Information Base or MIB. Objects in the MIB are 90 defined using the mechanisms defined in the SMI. 92 This memo specifies a MIB module that is compliant to the SMIv2. A 93 MIB conforming to the SMIv1 can be produced through the appropriate 94 translations. The resulting translated MIB must be semantically 95 equivalent, except where objects or events are omitted because no 96 translation is possible (use of Counter64). Some machine readable 97 information in SMIv2 will be converted into textual descriptions in 98 SMIv1 during the translation process. However, this loss of machine 99 readable information is not considered to change the semantics of 100 the MIB. 102 2. Introduction 104 There are two main approaches to management. One is based on polling 105 by a management application to determine node status, and the other 106 is based on a node sending notifications to manager when status 107 changes to and from fault conditions. The SNMP approach to date has 108 been the first. Little has been done to support the second in the 109 SNMP framework. This document provides the mechanisms for 110 management to be based on exception reporting. 112 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 113 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 114 this document are to be interpreted as described in RFC-2119 [1]. 116 3. Exception Reporting Framework 118 3.1 Terminology 120 Error 121 A deviation of a system from intended operation. 123 Fault 124 A lasting error or warning condition. 126 Alarm 127 Persistent indication of a fault. An alarm is said to be 'set' 128 (or raised) when a fault is first detected and administratively 129 enabled. An alarm is said to be 'cleared' when a fault is first 130 noticed to have ceased or administratively disabled. 132 Event 133 Something that happened. Examples include a change in status, 134 crossing a threshold, an external input to the system. 135 Additionally, setting or clearing an alarm is also an event. 137 Notification 138 An unsolicited transmission of management information due to an 139 event or condition. 141 3.2 Alarm Definitions 143 Each type of an alarm needs to be well specified. Ideally, a new 144 construct (or template) would be added to the MIB module language, 145 which is specified by SNMP's SMI. Unfortunately, this is not 146 possible. Since alarms are identified with an OID value, the best 147 choice of construct to use is OBJECT-IDENTITY. This construct allows 148 a descriptor to be defined, a status and description specified, and 149 an OID value assigned. The contents of the DESCRIPTION text must be 150 structured to specify the attributes of an alarm type. The 151 attributes include: 153 Raise Conditions 154 What set of conditions or events cause the alarm to be raised? 156 Clear Conditions 157 What must occur to cause the alarm to be cleared? 159 Source Identification 160 How are the sources of the alarm identified (a source can be 161 physical (such as port), or logical, such as a session)? 163 Perceived Severity 164 How is the perceived severity of the alarm determined (it may 165 be statically specified or dynamically determined)? 167 Service Affecting 168 How is it determined if the condition is service affecting (it 169 may be statically specified or dynamically determined)? 171 Associated Information 172 What additional information is associated, if any, with the 173 alarm? For example, if the alarm is due to a threshold being 174 crossed, the additional information could be the threshold 175 value and the current value. 177 Class (Category) 178 What is the class (category) of the alarm using the ITU-T 179 terminology? 181 Probable Cause 182 How is the probable cause of the alarm determined (it may be 183 statically specified or dynamically determined)? 185 Dependencies 186 What are the dependencies, if any, between this alarm and other 187 alarms. For example, a loss of signal alarm on a network 188 interface would probably also result in a network interface 189 down alarm. 191 In summary, instead of adding a new construct like the following: 193 TemperatureAlarm ALARM-TYPE 194 STATUS current 195 DESCRIPTION "The current temperature outside of the 196 acceptable operating range" 197 RAISED-BY "The measured temperature has been outside of the 198 acceptable operating range for the last 5 seconds." 199 ClEARED-BY "The measure temperature has been within the 200 acceptable range for the last 15 seconds." 202 . . . 203 ::= { myAlarms 1 } 205 the existing OBJECT-IDENTITY construct must be used and the 206 DESCRIPTION field structured like in the following: 208 TemperatureAlarm OBJECT-IDENTITY 209 STATUS current 210 DESCRIPTION "An Alarm 212 Description: 213 The current temperature outside of the 214 acceptable operating range 216 RAISED-BY: 217 The measured temperature has been outside of the 218 acceptable operating range for the last 5 219 seconds. 221 ClEARED-BY: 222 The measure temperature has been within the 223 acceptable range for the last 15 seconds. 224 . . . " 225 ::= { myAlarms 1 } 227 4. MIB Module Overview 229 The MIB module defines a list of current alarms and a log of alarms 230 that have been raised and/or cleared. The current alarm list is 231 specified as two tables. Table snmpAlarmCurrTable contains generic 232 information about alarms and table snmpItuAlarmCurrTable contains 233 ITU-T (from X.733 and X.736) information about alarms. The current 234 varBind table provides additional information about each current 235 alarm. 237 The alarm log table is specified as two tables. An entry is made in 238 table snmpAlarmLogTable each time an entry is added or removed from 239 the current alarm table. Likewise an entry is made in table 240 snmpItuAlarmLogTable each time an entry is added or removed from the 241 ITU-T augmentation of the current alarm table. 243 Scalar objects snmpAlarmLastChange, snmpAlarmLogFirstIndex, and 244 snmpAlarmLogLastIndex provide the information so that a management 245 application can efficiently track the current alarms and retrieve 246 entries in the alarm log. Additionally, a manager may choose to use 247 notifications to assist in tracking the current alarms and/or alarm 248 log entries. The notification snmpAlarmStatusChange or 249 snmpItuAlarmStatusChange can be used. 251 5. Definitions 253 SNMP-ALARM-MIB DEFINITIONS ::= BEGIN 255 IMPORTS 256 MODULE-IDENTITY, 257 OBJECT-TYPE, 258 NOTIFICATION-TYPE, 259 snmpModules, 260 Gauge32, 261 Unsigned32 262 FROM SNMPv2-SMI 264 TEXTUAL-CONVENTION, 265 TruthValue, 266 AutonomousType, 267 VariablePointer, 268 TimeStamp 269 FROM SNMPv2-TC 271 SnmpAdminString 272 FROM SNMP-FRAMEWORK-MIB 274 MODULE-COMPLIANCE, 275 OBJECT-GROUP, 276 NOTIFICATION-GROUP 277 FROM SNMPv2-CONF; 279 snmpAlarmMIB MODULE-IDENTITY 280 LAST-UPDATED "200102220000Z" -- feb 22, 2001 281 ORGANIZATION "IETF Distributed Management Working Group" 282 CONTACT-INFO 283 "WG-email: disman@dorothy.bmc.com 284 Subscribe: disman-request@dorothy.bmc.com 285 In message body: 286 subscribe disman your_email_address 287 Archive: ftp://amethyst.bmc.com/pub/disman/archives 289 Chair: Randy Presuhn 290 BMC Software 291 EMail: rpresuhn@bmc.com 292 Phone: +1-301-854-6889 294 Author: David T. Perkins 295 SNMPinfo 296 Postal: 3763 Benton Street 297 Santa Clara, CA 95051 298 EMail: dperkins@dsperkins.com 299 Phone: +1 408 394 8702" 300 DESCRIPTION 301 "This MIB module defines MIB objects and notifications that 302 provide mechanisms to monitor alarms currently active and 303 the history of alarms being set and cleared on a managed 304 system. 306 Terminology used in this MIB module: 308 Error - A deviation from intended operation. 310 Fault - A lasting error or warning condition. 312 Alarm - A persistent indication of a fault. An alarm is 313 said to be 'set' when a fault is first detected and 314 administratively enabled. An alarm is said to be 315 'cleared' when a fault is first noticed to have 316 ceased or administratively disabled. 318 Event - Something that happened. Examples include a change 319 in status, crossing a threshold, an external input 320 to the system. Additionally, setting or clearing 321 an alarm is also an event." 322 REVISION "200102220000Z" -- feb 22, 2001 323 DESCRIPTION "The initial revision" 324 ::= { snmpModules xx } -- replace "xx" with next appropriate 325 -- value 327 snmpAlarmObjects OBJECT IDENTIFIER ::= { snmpAlarmMIB 1 } 328 snmpAlarmNotifications OBJECT IDENTIFIER ::= { snmpAlarmMIB 2 } 329 snmpAlarmConformance OBJECT IDENTIFIER ::= { snmpAlarmMIB 3 } 330 snmpAlarmCompliances 331 OBJECT IDENTIFIER ::= { snmpAlarmConformance 1 } 332 snmpAlarmGroups 333 OBJECT IDENTIFIER ::= { snmpAlarmConformance 2 } 335 SnmpAlarmCond ::= TEXTUAL-CONVENTION 336 STATUS current 337 DESCRIPTION "The alarm condition. The values are: 338 set(1)....the alarm condition detected 339 clear(2)..the alarm condition ceased" 340 SYNTAX INTEGER { 341 set(1), 342 clear(2) 343 } 345 SnmpAlarmType ::= TEXTUAL-CONVENTION 346 STATUS current 347 DESCRIPTION "The identity of the type of an SNMP alarm. The SNMP 348 SMI does not have a construct to define SNMP alarms. 349 Thus, the OBJECT-IDENTITY construct must be 350 used with the text of the DESCRIPTION clause 351 describing the conditions that cause the alarm 352 to be set and to be clear, and a description of 353 each varBind to be associated with the alarm." 354 SYNTAX OBJECT IDENTIFIER -- really AutonomousType 356 OptDateAndTime ::= TEXTUAL-CONVENTION 357 DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d" 358 STATUS current 359 DESCRIPTION 360 "An date-time specification, or a zero length string. 362 field octets contents range 363 ----- ------ -------- ----- 364 1 1-2 year 0..65536 365 2 3 month 1..12 366 3 4 day 1..31 367 4 5 hour 0..23 368 5 6 minutes 0..59 369 6 7 seconds 0..60 370 (use 60 for leap-second) 371 7 8 deci-seconds 0..9 372 8 9 direction from UTC '+' / '-' 373 9 10 hours from UTC 0..11 374 10 11 minutes from UTC 0..59 376 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be 377 displayed as: 379 1992-5-26,13:30:15.0,-4:0 381 Note that if only local time is known, then time zone 382 information (fields 8-10) is not present." 383 SYNTAX OCTET STRING (SIZE (0 | 8 | 11)) -- DateAndTime 385 SnmpValUnion ::= TEXTUAL-CONVENTION 386 STATUS current 387 DESCRIPTION "A descriminated union, which is the 388 following ASN.1 sequence BER encoded 389 and wrapped as the value of an OCTET 390 STRING. 391
392 " 393 SYNTAX OCTET STRING 395 snmpAlarmGlobals OBJECT IDENTIFIER ::= { snmpAlarmObjects 1 } 397 snmpAlarmCurrEntries OBJECT-TYPE 398 SYNTAX Gauge32 399 MAX-ACCESS read-only 400 STATUS current 401 DESCRIPTION "The number of entries in the current alarm table." 402 ::= { snmpAlarmGlobals 1 } 404 snmpAlarmLastChange OBJECT-TYPE 405 SYNTAX TimeStamp 406 MAX-ACCESS read-only 407 STATUS current 408 DESCRIPTION "The value of object sysUpTime when an entry was 409 added or removed from the current alarm table and 410 added to the alarm log table." 411 ::= { snmpAlarmGlobals 2 } 413 snmpAlarmLogFirstIndex OBJECT-TYPE 414 SYNTAX Unsigned32 415 MAX-ACCESS read-only 416 STATUS current 417 DESCRIPTION "The index of the oldest entry in the alarm log 418 table, or zero. The value of zero is used to 419 indicate that no entry exists in the alarm log." 420 ::= { snmpAlarmGlobals 3 } 422 snmpAlarmLogLastIndex OBJECT-TYPE 423 SYNTAX Unsigned32 424 MAX-ACCESS read-only 425 STATUS current 426 DESCRIPTION "The index of the youngest entry in the alarm log 427 table, or zero. The value of zero is used to 428 indicate that no entry exists in the alarm log." 429 ::= { snmpAlarmGlobals 4 } 431 snmpAlarmGenNotify OBJECT-TYPE 432 SYNTAX TruthValue 433 MAX-ACCESS read-write 434 STATUS current 435 DESCRIPTION "The controls whether or not notification 436 snmpAlarmStatusChange may be generated. The 437 values are: 438 true(1)...notifications may be generated 439 false(2)..notifications may not be generated" 440 ::= { snmpAlarmGlobals 5 } 442 -- ITU extension 443 snmpItuAlarmGenNotify OBJECT-TYPE 444 SYNTAX TruthValue 445 MAX-ACCESS read-write 446 STATUS current 447 DESCRIPTION "The controls whether or not notification 448 snmpItuAlarmStatusChange may be generated. 449 The values are: 450 true(1)...notifications may be generated 451 false(2)..notifications may not be generated 453 Note: if this is enabled, then most likely 454 generation of notification snmpAlarmStatusChange 455 should be disabled." 456 ::= { snmpAlarmGlobals 6 } 458 snmpAlarmCurrTable OBJECT-TYPE 459 SYNTAX SEQUENCE OF SnmpAlarmCurrEntry 460 MAX-ACCESS not-accessible 461 STATUS current 462 DESCRIPTION "A table listing all the current 'alarms'. An 463 alarm indicates a persistent fault condition 464 in a software or hardware component or sub-system 465 that is intended to be operating. An alarm is 466 cleared by 'fixing' the fault condition or 467 administratively disabling the alarm." 468 ::= { snmpAlarmObjects 2 } 470 snmpAlarmCurrEntry OBJECT-TYPE 471 SYNTAX SnmpAlarmCurrEntry 472 MAX-ACCESS not-accessible 473 STATUS current 474 DESCRIPTION "A row in the table of current alarms. Rows cannot 475 be created or deleted via SNMP operations." 476 INDEX { snmpAlarmCurrIndex } 477 ::= { snmpAlarmCurrTable 1 } 479 SnmpAlarmCurrEntry ::= SEQUENCE { 480 snmpAlarmCurrIndex Unsigned32, 481 snmpAlarmCurrOccurDateAndTime OptDateAndTime, 482 snmpAlarmCurrOccurUpTime TimeStamp, 483 snmpAlarmCurrType SnmpAlarmType, 484 snmpAlarmCurrId Unsigned32, 485 snmpAlarmCurrContextName SnmpAdminString, 486 snmpAlarmCurrVarBinds Gauge32 487 } 489 snmpAlarmCurrIndex OBJECT-TYPE 490 SYNTAX Unsigned32(1..4294967295) 491 MAX-ACCESS not-accessible 492 STATUS current 493 DESCRIPTION "An arbitrary index of the alarm in the current 494 alarm table. The index for an existing entry is 495 not affected when a entry is added or removed from 496 the table. Index values may be cycled to the max 497 before reuse or follow any implementation specific 498 reuse strategy." 499 ::= { snmpAlarmCurrEntry 1 } 501 snmpAlarmCurrOccurDateAndTime OBJECT-TYPE 502 SYNTAX OptDateAndTime 503 MAX-ACCESS read-only 504 STATUS current 505 DESCRIPTION "The local date and time when the alarm was set, 506 or a zero length string. The value is a zero 507 length string when the local time cannot be 508 determined." 509 ::= { snmpAlarmCurrEntry 2 } 511 snmpAlarmCurrOccurUpTime OBJECT-TYPE 512 SYNTAX TimeStamp 513 MAX-ACCESS read-only 514 STATUS current 515 DESCRIPTION "The value of sysUpTime when the alarm was set 516 or zero. The value is zero when the alarm occurred 517 before the most recent reset of the management 518 system." 519 ::= { snmpAlarmCurrEntry 3 } 521 snmpAlarmCurrType OBJECT-TYPE 522 SYNTAX SnmpAlarmType 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION "The type of the alarm." 526 ::= { snmpAlarmCurrEntry 4 } 528 snmpAlarmCurrId OBJECT-TYPE 529 SYNTAX Unsigned32 530 MAX-ACCESS read-only 531 STATUS current 532 DESCRIPTION "The ID of the alarm. No two active alarms 533 may have the same value. This value is used 534 in matching the set and clear entries in 535 the alarm log." 536 ::= { snmpAlarmCurrEntry 5 } 538 snmpAlarmCurrContextName OBJECT-TYPE 539 SYNTAX SnmpAdminString (SIZE(0..32)) 540 MAX-ACCESS read-only 541 STATUS current 542 DESCRIPTION "The context in which the alarm occurred." 543 ::= { snmpAlarmCurrEntry 6 } 545 snmpAlarmCurrVarBinds OBJECT-TYPE 546 SYNTAX Gauge32 547 MAX-ACCESS read-only 548 STATUS current 549 DESCRIPTION "The number of varBinds associated with the 550 alarm. The count is usually at least one, 551 with at least one varBind identifying 552 the source of the alarm." 553 ::= { snmpAlarmCurrEntry 7 } 555 snmpAlarmCurrVarBindTable OBJECT-TYPE 556 SYNTAX SEQUENCE OF SnmpAlarmCurrVarBindEntry 557 MAX-ACCESS not-accessible 558 STATUS current 559 DESCRIPTION "A table of varBinds (pairs of variable and value) 560 that sparse extends the rows in table 561 snmpAlarmCurrTable. That is, for each row in table 562 snmpAlarmCurrTable, there is zero, one, or more 563 associated rows in this table. The value of object 564 snmpAlarmCurrVarBinds specifies the number of rows 565 in this table." 566 ::= { snmpAlarmObjects 3 } 568 snmpAlarmCurrVarBindEntry OBJECT-TYPE 569 SYNTAX SnmpAlarmCurrVarBindEntry 570 MAX-ACCESS not-accessible 571 STATUS current 572 DESCRIPTION "A row in the table of varBinds for current 573 alarms. Rows cannot be created or deleted via 574 SNMP operations." 575 INDEX { snmpAlarmCurrIndex, 576 snmpAlarmCurrVarBindIndex } 577 ::= { snmpAlarmCurrVarBindTable 1 } 579 SnmpAlarmCurrVarBindEntry ::= SEQUENCE { 580 snmpAlarmCurrVarBindIndex Unsigned32, 581 snmpAlarmCurrVarBindId VariablePointer, 582 snmpAlarmCurrVarBindVal SnmpValUnion 583 } 585 snmpAlarmCurrVarBindIndex OBJECT-TYPE 586 SYNTAX Unsigned32 (1..4294967295) 587 MAX-ACCESS not-accessible 588 STATUS current 589 DESCRIPTION "The index of the varBind. The value is between 590 one and the value of the associated object 591 snmpAlarmCurrVarBinds." 592 ::= { snmpAlarmCurrVarBindEntry 1 } 594 snmpAlarmCurrVarBindId OBJECT-TYPE 595 SYNTAX VariablePointer 596 MAX-ACCESS read-only 597 STATUS current 598 DESCRIPTION "The ID of the object instance." 599 ::= { snmpAlarmCurrVarBindEntry 2 } 601 snmpAlarmCurrVarBindVal OBJECT-TYPE 602 SYNTAX SnmpValUnion 603 MAX-ACCESS read-only 604 STATUS current 605 DESCRIPTION "The value of the object instance." 606 ::= { snmpAlarmCurrVarBindEntry 3 } 608 snmpAlarmLogTable OBJECT-TYPE 609 SYNTAX SEQUENCE OF SnmpAlarmLogEntry 610 MAX-ACCESS not-accessible 611 STATUS current 612 DESCRIPTION "A table containing a log of when each 'alarm' 613 has been 'set' or 'cleared'. An alarm indicates 614 a persistent fault condition in a software or 615 hardware component or sub-system that is intended 616 to be operating. An alarm is cleared by 'fixing' 617 the fault condition or administratively disabling 618 the alarm. 620 The alarm log operates like a circular buffer. 621 The index of the oldest entry is specified by 622 object snmpAlarmLogFirstIndex and the index 623 of the youngest entry is specified by object 624 tbtSystemAlarmLogLastIndex. 626 The alarm log may be preserved in part or in 627 total across restarts of a management system. 628 The last few entries SHOULD be saved to assist 629 in determining the cause of an unplanned 630 restart." 631 ::= { snmpAlarmObjects 4 } 633 snmpAlarmLogEntry OBJECT-TYPE 634 SYNTAX SnmpAlarmLogEntry 635 MAX-ACCESS not-accessible 636 STATUS current 637 DESCRIPTION "A row in the alarm log table. Rows cannot 638 be created or deleted via SNMP operations." 639 INDEX { snmpAlarmLogIndex } 640 ::= { snmpAlarmLogTable 1 } 642 SnmpAlarmLogEntry ::= SEQUENCE { 643 snmpAlarmLogIndex Unsigned32, 644 snmpAlarmLogCond SnmpAlarmCond, 645 snmpAlarmLogOccurDateAndTime OptDateAndTime, 646 snmpAlarmLogOccurUpTime TimeStamp, 647 snmpAlarmLogType SnmpAlarmType, 648 snmpAlarmLogId Unsigned32, 649 snmpAlarmLogContextName SnmpAdminString, 650 snmpAlarmLogVarBinds Gauge32 651 } 653 snmpAlarmLogIndex OBJECT-TYPE 654 SYNTAX Unsigned32(1..4294967295) 655 MAX-ACCESS not-accessible 656 STATUS current 657 DESCRIPTION "An index of the alarm in the alarm log table. The 658 index is increased by one for each new entry in the 659 table until the maximum value is reach and then the 660 index restarts at 1. The index of the oldest entry 661 is specified by object snmpAlarmLogFirstIndex and 662 index of the youngest entry is specified by object 663 snmpAlarmLogLastIndex." 664 ::= { snmpAlarmLogEntry 1 } 666 snmpAlarmLogCond OBJECT-TYPE 667 SYNTAX SnmpAlarmCond 668 MAX-ACCESS read-only 669 STATUS current 670 DESCRIPTION "Indicates if the log entry is due to the alarm 671 Being set (raised) or being cleared." 672 ::= { snmpAlarmLogEntry 2 } 674 snmpAlarmLogOccurDateAndTime OBJECT-TYPE 675 SYNTAX OptDateAndTime 676 MAX-ACCESS read-only 677 STATUS current 678 DESCRIPTION "The local date and time when the alarm was set 679 or clear, or a zero length string. The value is a 680 zero length string when the local time cannot be 681 determined." 682 ::= { snmpAlarmLogEntry 3 } 684 snmpAlarmLogOccurUpTime OBJECT-TYPE 685 SYNTAX TimeStamp 686 MAX-ACCESS read-only 687 STATUS current 688 DESCRIPTION "The value of sysUpTime when the alarm was set or 689 cleared, or zero. The value is zero when the alarm 690 was set or cleared before the most recent reset of 691 the management system." 692 ::= { snmpAlarmLogEntry 4 } 694 snmpAlarmLogType OBJECT-TYPE 695 SYNTAX SnmpAlarmType 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION "The type of the alarm." 699 ::= { snmpAlarmLogEntry 5 } 701 snmpAlarmLogId OBJECT-TYPE 702 SYNTAX Unsigned32 703 MAX-ACCESS read-only 704 STATUS current 705 DESCRIPTION "The ID of the alarm. Each alarm that is set 706 is assigned a unique ID among active alarms. 707 That is, no two active alarms may have the 708 same value. This value is used in matching 709 the set and clear entries in this log. 710 Note: alarms may be cleared and not recorded 711 across restarts of the management system. 712 Thus, additional checks must be performed 713 to match set and clear entries in the 714 log that occur on opposite sides of a 715 restart." 716 ::= { snmpAlarmLogEntry 6 } 718 snmpAlarmLogContextName OBJECT-TYPE 719 SYNTAX SnmpAdminString (SIZE(0..32)) 720 MAX-ACCESS read-only 721 STATUS current 722 DESCRIPTION "The context in which the alarm occurred." 723 ::= { snmpAlarmLogEntry 7 } 725 snmpAlarmLogVarBinds OBJECT-TYPE 726 SYNTAX Gauge32 727 MAX-ACCESS read-only 728 STATUS current 729 DESCRIPTION "The number of varBinds associated with the 730 alarm. The count is usually at least one, 731 with at least one varBind identifying 732 the source of the alarm." 733 ::= { snmpAlarmLogEntry 8 } 735 snmpAlarmLogVarBindTable OBJECT-TYPE 736 SYNTAX SEQUENCE OF SnmpAlarmLogVarBindEntry 737 MAX-ACCESS not-accessible 738 STATUS current 739 DESCRIPTION "A table of varBinds (pairs of variable and value) 740 that sparse extends the rows in table 741 snmpAlarmLogTable. That is, for each row in table 742 snmpAlarmLogTable, there is zero, one, or more 743 associated rows in this table. The value of object 744 snmpAlarmLogVarBinds specifies the number of rows 745 in this table." 746 ::= { snmpAlarmObjects 5 } 748 snmpAlarmLogVarBindEntry OBJECT-TYPE 749 SYNTAX SnmpAlarmLogVarBindEntry 750 MAX-ACCESS not-accessible 751 STATUS current 752 DESCRIPTION "A row in the table of varBinds for the alarm 753 log. Rows cannot be created or deleted via 754 SNMP operations." 755 INDEX { snmpAlarmLogIndex, 756 snmpAlarmLogVarBindIndex } 757 ::= { snmpAlarmLogVarBindTable 1 } 759 SnmpAlarmLogVarBindEntry ::= SEQUENCE { 760 snmpAlarmLogVarBindIndex Unsigned32, 761 snmpAlarmLogVarBindId VariablePointer, 762 snmpAlarmLogVarBindVal SnmpValUnion 763 } 765 snmpAlarmLogVarBindIndex OBJECT-TYPE 766 SYNTAX Unsigned32 (1..4294967295) 767 MAX-ACCESS not-accessible 768 STATUS current 769 DESCRIPTION "The index of the varBind. The value is between 770 one and the value of the associated object 771 snmpAlarmLogVarBinds." 772 ::= { snmpAlarmLogVarBindEntry 1 } 774 snmpAlarmLogVarBindId OBJECT-TYPE 775 SYNTAX VariablePointer 776 MAX-ACCESS read-only 777 STATUS current 778 DESCRIPTION "The ID of the object instance." 779 ::= { snmpAlarmLogVarBindEntry 2 } 781 snmpAlarmLogVarBindVal OBJECT-TYPE 782 SYNTAX SnmpValUnion 783 MAX-ACCESS read-only 784 STATUS current 785 DESCRIPTION "The value of the object instance." 786 ::= { snmpAlarmLogVarBindEntry 3 } 788 -- ITU-T extensions 789 SnmpItuAlarmClass ::= TEXTUAL-CONVENTION 790 STATUS current 791 DESCRIPTION "The class of alarm as specified in 792 [X.733] and [X.736]. 793 " 794 SYNTAX INTEGER { 795 other (1), 796 communicationsAlarm (2), 797 qualityOfServiceAlarm (3), 798 processingErrorAlarm (4), 799 equipmentAlarm (5), 800 environmentalAlarm (6), 801 integrityViolation (7), 802 operationalViolation (8), 803 physicalViolation (9), 804 securityServiceOrMechanismViolation (10), 805 timeDomainViolation (11) 806 } 808 SnmpItuAlarmProbCause ::= TEXTUAL-CONVENTION 809 STATUS current 810 DESCRIPTION "The probable cause of the alarm as 811 specified in [X.733] and [X.736]. 812 " 813 SYNTAX INTEGER { 814 other (1), 815 adapterError (2), 816 applicationSubsystemFailure (3), 817 bandwidthReduced (4), 818 callEstablishmentError (5), 819 communicationsProtocolError (6), 820 communicationsSubsystemFailure (7), 821 configurationOrCustomizationError (8), 822 congestion (9), 823 corruptData (10), 824 cpuCyclesLimitExceeded (11), 825 dataSetOrModemError (12), 826 degradedSignal (13), 827 dteDceInterfaceError (14), 828 enclosureDoorOpen (15), 829 equipmentMalfunction (16), 830 excessiveVibration (17), 831 fileError (18), 832 fireDetected (19), 833 floodDetected (20), 834 framingError (21), 835 heatingVentCoolingSystemProblem (22), 836 humidityUnacceptable (23), 837 inputOutputDeviceError (24), 838 inputDeviceError (25), 839 lanError (26), 840 leakDetected (27), 841 localNodeTransmissionError (28), 842 lossOfFrame (29), 843 lossOfSignal (30), 844 materialSupplyExhausted (31), 845 multiplexerProblem (32), 846 outOfMemory (33), 847 ouputDeviceError (34), 848 performanceDegraded (35), 849 powerProblem (36), 850 pressureUnacceptable (37), 851 processorProblem (38), 852 pumpFailure (39), 853 queueSizeExceeded (40), 854 receiveFailure (41), 855 receiverFailure (42), 856 remoteNodeTransmissionError (43), 857 resourceAtOrNearingCapacity (44), 858 responseTimeExecessive (45), 859 retransmissionRateExcessive (46), 860 softwareError (47), 861 softwareProgramAbnormallyTerminated (48), 862 softwareProgramError (49), 863 storageCapacityProblem (50), 864 temperatureUnacceptable (51), 865 thresholdCrossed (52), 866 timingProblem (53), 867 toxicLeakDetected (54), 868 transmitFailure (55), 869 transmitterFailure (56), 870 underlyingResourceUnavailable (57), 871 versionMismatch (58), 872 authenticationFailure (59), 873 breachOfConfidentiality (60), 874 cableTamper (61), 875 delayedInformation (62), 876 denialOfService (63), 877 duplicateInformation (64), 878 informationMissing (65), 879 informationModificationDetected (66), 880 informationOutOfSequence (67), 881 intrusionDetection (68), 882 keyExpired (69), 883 nonRepudiationFailure (70), 884 outOfHoursActivity (71), 885 outOfService (72), 886 proceduralError (73), 887 unauthorizedAccessAttempt (74), 888 unexpectedInformation (75) 889 } 891 SnmpItuAlarmPercSeverity ::= TEXTUAL-CONVENTION 892 STATUS current 893 DESCRIPTION "The perceived severity of the alarm as 894 specified in [X.733] and [X.736]. 895 " 896 SYNTAX INTEGER { 897 indeterminate (2), 898 critical (3), 899 major (4), 900 minor (5), 901 warning (6) 902 } 904 SnmpItuAlarmTrendInd ::= TEXTUAL-CONVENTION 905 STATUS current 906 DESCRIPTION "The trend indication of the alarm as 907 specified in [X.733]. 908 " 909 SYNTAX INTEGER { 910 moreSevere (1), 911 noChange (2), 912 lessSevere (3) 913 } 915 snmpItuAlarmCurrTable OBJECT-TYPE 916 SYNTAX SEQUENCE OF SnmpItuAlarmCurrEntry 917 MAX-ACCESS not-accessible 918 STATUS current 919 DESCRIPTION "A table augmenting the current alarm table 920 (snmpAlarmCurrTable) with additional information 921 from the ITU-T alarm model." 922 ::= { snmpAlarmObjects 6 } 924 snmpItuAlarmCurrEntry OBJECT-TYPE 925 SYNTAX SnmpItuAlarmCurrEntry 926 MAX-ACCESS not-accessible 927 STATUS current 928 DESCRIPTION "A row in the table of ITU-T current alarms. Rows 929 cannot be created or deleted via SNMP operations." 930 AUGMENTS { snmpAlarmCurrEntry } 931 ::= { snmpItuAlarmCurrTable 1 } 933 SnmpItuAlarmCurrEntry ::= SEQUENCE { 934 snmpItuAlarmCurrClass SnmpItuAlarmClass, 935 snmpItuAlarmCurrProbCause SnmpItuAlarmProbCause, 936 snmpItuAlarmCurrPercSeverity SnmpItuAlarmPercSeverity, 937 snmpItuAlarmCurrAdditText SnmpAdminString, 938 snmpItuAlarmCurrTrendInd SnmpItuAlarmTrendInd, 939 snmpItuAlarmCurrDetector AutonomousType, 940 snmpItuAlarmCurrServiceProvider AutonomousType, 941 snmpItuAlarmCurrServiceUser AutonomousType 942 } 944 snmpItuAlarmCurrClass OBJECT-TYPE 945 SYNTAX SnmpItuAlarmClass 946 MAX-ACCESS read-only 947 STATUS current 948 DESCRIPTION "The class of the alarm as specified in 949 [X.733] and [X.736]. 950 " 951 ::= { snmpItuAlarmCurrEntry 1 } 953 snmpItuAlarmCurrProbCause OBJECT-TYPE 954 SYNTAX SnmpItuAlarmProbCause 955 MAX-ACCESS read-only 956 STATUS current 957 DESCRIPTION "The probable cause of the alarm as 958 specified in [X.733] and [X.736]. 959 " 960 ::= { snmpItuAlarmCurrEntry 2 } 962 snmpItuAlarmCurrPercSeverity OBJECT-TYPE 963 SYNTAX SnmpItuAlarmPercSeverity 964 MAX-ACCESS read-only 965 STATUS current 966 DESCRIPTION "The perceived severity of the alarm as 967 specified in [X.733] and [X.736]. 968 " 969 ::= { snmpItuAlarmCurrEntry 3 } 971 snmpItuAlarmCurrAdditText OBJECT-TYPE 972 SYNTAX SnmpAdminString 973 MAX-ACCESS read-only 974 STATUS current 975 DESCRIPTION "The additional text field of the alarm as 976 specified in [X.733]. 977 " 978 ::= { snmpItuAlarmCurrEntry 4 } 980 snmpItuAlarmCurrTrendInd OBJECT-TYPE 981 SYNTAX SnmpItuAlarmTrendInd 982 MAX-ACCESS read-only 983 STATUS current 984 DESCRIPTION "The trend indication of the alarm as 985 specified in [X.733]. 986 " 987 ::= { snmpItuAlarmCurrEntry 5 } 989 -- more investigation is needed for the following objects 990 snmpItuAlarmCurrDetector OBJECT-TYPE 991 SYNTAX AutonomousType 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION "The SecurityAlarmDetector object from [X.736]. 995 " 996 ::= { snmpItuAlarmCurrEntry 6 } 998 snmpItuAlarmCurrServiceProvider OBJECT-TYPE 999 SYNTAX AutonomousType 1000 MAX-ACCESS read-only 1001 STATUS current 1002 DESCRIPTION "The ServiceProvider object from [X.736]. 1003 " 1004 ::= { snmpItuAlarmCurrEntry 7 } 1006 snmpItuAlarmCurrServiceUser OBJECT-TYPE 1007 SYNTAX AutonomousType 1008 MAX-ACCESS read-only 1009 STATUS current 1010 DESCRIPTION "The SericeUser object from [X.736]. 1011 " 1012 ::= { snmpItuAlarmCurrEntry 8 } 1014 snmpItuAlarmLogTable OBJECT-TYPE 1015 SYNTAX SEQUENCE OF SnmpItuAlarmLogEntry 1016 MAX-ACCESS not-accessible 1017 STATUS current 1018 DESCRIPTION "A table augmenting the alarm log table 1019 (snmpAlarmLogTable) with additional information 1020 from the ITU-T alarm model." 1021 ::= { snmpAlarmObjects 7 } 1023 snmpItuAlarmLogEntry OBJECT-TYPE 1024 SYNTAX SnmpItuAlarmLogEntry 1025 MAX-ACCESS not-accessible 1026 STATUS current 1027 DESCRIPTION "A row in the ITU-T alarm log table. Rows cannot 1028 be created or deleted via SNMP operations." 1029 AUGMENTS { snmpAlarmLogEntry } 1030 ::= { snmpItuAlarmLogTable 1 } 1032 SnmpItuAlarmLogEntry ::= SEQUENCE { 1033 snmpItuAlarmLogClass SnmpItuAlarmClass, 1034 snmpItuAlarmLogProbCause SnmpItuAlarmProbCause, 1035 snmpItuAlarmLogPercSeverity SnmpItuAlarmPercSeverity, 1036 snmpItuAlarmLogAdditText SnmpAdminString, 1037 snmpItuAlarmLogTrendInd SnmpItuAlarmTrendInd, 1038 snmpItuAlarmLogDetector AutonomousType, 1039 snmpItuAlarmLogServiceProvider AutonomousType, 1040 snmpItuAlarmLogServiceUser AutonomousType 1041 } 1043 snmpItuAlarmLogClass OBJECT-TYPE 1044 SYNTAX SnmpItuAlarmClass 1045 MAX-ACCESS read-only 1046 STATUS current 1047 DESCRIPTION "The class of the alarm as specified in 1048 [X.733] and [X.736]. 1049 " 1050 ::= { snmpItuAlarmLogEntry 1 } 1052 snmpItuAlarmLogProbCause OBJECT-TYPE 1053 SYNTAX SnmpItuAlarmProbCause 1054 MAX-ACCESS read-only 1055 STATUS current 1056 DESCRIPTION "The probable cause of the alarm as 1057 specified in [X.733] and [X.736]. 1058 " 1059 ::= { snmpItuAlarmLogEntry 2 } 1061 snmpItuAlarmLogPercSeverity OBJECT-TYPE 1062 SYNTAX SnmpItuAlarmPercSeverity 1063 MAX-ACCESS read-only 1064 STATUS current 1065 DESCRIPTION "The perceived severity of the alarm as 1066 specified in [X.733] and [X.736]. 1067 " 1068 ::= { snmpItuAlarmLogEntry 3 } 1070 snmpItuAlarmLogAdditText OBJECT-TYPE 1071 SYNTAX SnmpAdminString 1072 MAX-ACCESS read-only 1073 STATUS current 1074 DESCRIPTION "The additional text field of the alarm as 1075 specified in [X.733]. 1076 " 1077 ::= { snmpItuAlarmLogEntry 4 } 1079 snmpItuAlarmLogTrendInd OBJECT-TYPE 1080 SYNTAX SnmpItuAlarmTrendInd 1081 MAX-ACCESS read-only 1082 STATUS current 1083 DESCRIPTION "The trend indication of the alarm as 1084 specified in [X.733]. 1085 " 1086 ::= { snmpItuAlarmLogEntry 5 } 1088 -- more investigation is needed for the following objects 1089 snmpItuAlarmLogDetector OBJECT-TYPE 1090 SYNTAX AutonomousType 1091 MAX-ACCESS read-only 1092 STATUS current 1093 DESCRIPTION "The SecurityAlarmDetector object from [X.736]. 1094 " 1095 ::= { snmpItuAlarmLogEntry 6 } 1097 snmpItuAlarmLogServiceProvider OBJECT-TYPE 1098 SYNTAX AutonomousType 1099 MAX-ACCESS read-only 1100 STATUS current 1101 DESCRIPTION "The ServiceProvider object from [X.736]. 1102 " 1103 ::= { snmpItuAlarmLogEntry 7 } 1105 snmpItuAlarmLogServiceUser OBJECT-TYPE 1106 SYNTAX AutonomousType 1107 MAX-ACCESS read-only 1108 STATUS current 1109 DESCRIPTION "The SericeUser object from [X.736]. 1110 " 1111 ::= { snmpItuAlarmLogEntry 8 } 1113 -- notifications 1115 snmpAlarmStatusChange NOTIFICATION-TYPE 1116 OBJECTS { snmpAlarmLogCond, 1117 snmpAlarmLogOccurDateAndTime, 1118 snmpAlarmLogOccurUpTime, 1119 snmpAlarmLogId, 1120 snmpAlarmLogVarBinds } 1121 STATUS current 1122 DESCRIPTION "An entry has been added to the alarm log 1123 table. That is, an alarm has been set or cleared. 1124 The objects all have the same instance, which is 1125 the row in the alarm log, and the objects are: 1126 snmpAlarmLogCond....alarm condition, either 1127 set or clear 1128 snmpAlarmLogOccurDateAndTime...date/time the 1129 alarm log entry created 1130 snmpAlarmLogOccurUpTime...timestamp the alarm 1131 log entry created 1132 snmpAlarmLogId....the ID of the alarm 1133 snmpAlarmLogVarBinds....the number of varBinds 1134 associated with the alarm 1136 Note 1: after these varBinds, the associated 1137 varBinds, if any, from table 1138 snmpAlarmLogVarBindTable must be specified in the 1139 varBind list for the notification. 1141 Note 2: object snmpAlarmGenNotify controls 1142 if or if not this notification may be generated." 1143 ::= { snmpAlarmNotifications 0 1 } 1145 snmpItuAlarmStatusChange NOTIFICATION-TYPE 1146 OBJECTS { snmpAlarmLogCond, 1147 snmpAlarmLogOccurDateAndTime, 1148 snmpAlarmLogOccurUpTime, 1149 snmpAlarmLogId, 1150 snmpAlarmLogVarBinds, 1151 snmpItuAlarmLogClass, 1152 snmpItuAlarmLogProbCause, 1153 snmpItuAlarmLogPercSeverity, 1154 snmpItuAlarmLogAdditText, 1155 snmpItuAlarmLogTrendInd, 1156 snmpItuAlarmLogDetector, 1157 snmpItuAlarmLogServiceProvider, 1158 snmpItuAlarmLogServiceUser } 1159 STATUS current 1160 DESCRIPTION "An entry has been added to the alarm log 1161 table and the ITU extensions are supported. 1162 That is, an alarm has been set or cleared. 1163 The objects all have the same instance, which is 1164 the row in the alarm log, and the objects are: 1165 snmpAlarmLogCond....alarm condition, either 1166 set or clear 1167 snmpAlarmLogOccurDateAndTime...date/time the 1168 alarm log entry created 1169 snmpAlarmLogOccurUpTime...timestamp the alarm 1170 log entry created 1171 snmpAlarmLogId....the ID of the alarm 1172 snmpAlarmLogVarBinds....the number of varBinds 1173 associated with the alarm 1174 1175 snmpItuAlarmLogClass... 1176 snmpItuAlarmLogProbCause... 1177 snmpItuAlarmLogPercSeverity... 1178 snmpItuAlarmLogAdditText... 1179 snmpItuAlarmLogTrendInd... 1180 snmpItuAlarmLogDetector... 1181 snmpItuAlarmLogServiceProvider... 1182 snmpItuAlarmLogServiceUser... 1184 Note 1: after these varBinds, the associated 1185 varBinds, if any, from table 1186 snmpAlarmLogVarBindTable must be specified in the 1187 varBind list for the notification. 1189 Note 2: object snmpItuAlarmGenNotify controls 1190 if or if not this notification may be generated." 1191 ::= { snmpAlarmNotifications 0 2 } 1193 -- Conformance 1195 snmpAlarmCompliance MODULE-COMPLIANCE 1196 STATUS current 1197 DESCRIPTION 1198 "The compliance statement for systems supporting 1199 the SNMP alarms." 1200 MODULE -- this module 1201 MANDATORY-GROUPS { snmpAlarmGblGroup, 1202 snmpAlarmCurrGroup, 1203 snmpAlarmLogGroup, 1204 snmpAlarmNotifyGroup } 1205 ::= { snmpAlarmCompliances 1 } 1207 snmpItuAlarmCompliance MODULE-COMPLIANCE 1208 STATUS current 1209 DESCRIPTION 1210 "The compliance statement for systems supporting 1211 the ITU-T extension to SNMP alarms." 1212 MODULE -- this module 1213 MANDATORY-GROUPS { snmpAlarmGblGroup, 1214 snmpAlarmCurrGroup, 1215 snmpAlarmLogGroup, 1216 snmpAlarmNotifyGroup, 1217 snmpItuAlarmGblGroup, 1218 snmpItuAlarmCurrGroup, 1219 snmpItuAlarmLogGroup, 1220 snmpItuAlarmNotifyGroup } 1221 ::= { snmpAlarmCompliances 2 } 1223 snmpAlarmGblGroup OBJECT-GROUP 1224 OBJECTS { snmpAlarmCurrEntries, 1225 snmpAlarmLastChange, 1226 snmpAlarmLogFirstIndex, 1227 snmpAlarmLogLastIndex, 1228 snmpAlarmGenNotify } 1229 STATUS current 1230 DESCRIPTION "Global objects for managing SNMP alarms." 1231 ::= { snmpAlarmGroups 1 } 1233 snmpAlarmCurrGroup OBJECT-GROUP 1234 OBJECTS { snmpAlarmCurrOccurDateAndTime, 1235 snmpAlarmCurrOccurUpTime, 1236 snmpAlarmCurrType, 1237 snmpAlarmCurrId, 1238 snmpAlarmCurrContextName, 1239 snmpAlarmCurrVarBinds, 1240 snmpAlarmCurrVarBindId, 1241 snmpAlarmCurrVarBindVal } 1242 STATUS current 1243 DESCRIPTION "Objects in the SNMP current alarm and 1244 current varBind tables." 1245 ::= { snmpAlarmGroups 2 } 1247 snmpAlarmLogGroup OBJECT-GROUP 1248 OBJECTS { snmpAlarmLogCond, 1249 snmpAlarmLogOccurDateAndTime, 1250 snmpAlarmLogOccurUpTime, 1251 snmpAlarmLogType, 1252 snmpAlarmLogId, 1253 snmpAlarmLogContextName, 1254 snmpAlarmLogVarBinds, 1255 snmpAlarmLogVarBindId, 1256 snmpAlarmLogVarBindVal } 1258 STATUS current 1259 DESCRIPTION "Objects in the SNMP alarm log and 1260 log varBind tables." 1261 ::= { snmpAlarmGroups 3 } 1263 snmpAlarmNotifyGroup NOTIFICATION-GROUP 1264 NOTIFICATIONS { snmpAlarmStatusChange } 1265 STATUS current 1266 DESCRIPTION "Notifications for SNMP alarms." 1267 ::= { snmpAlarmGroups 4 } 1269 snmpItuAlarmGblGroup OBJECT-GROUP 1270 OBJECTS { snmpItuAlarmGenNotify } 1271 STATUS current 1272 DESCRIPTION "Global objects for managing ITU-T 1273 extensions to SNMP alarms." 1274 ::= { snmpAlarmGroups 5 } 1276 snmpItuAlarmCurrGroup OBJECT-GROUP 1277 OBJECTS { snmpItuAlarmCurrClass, 1278 snmpItuAlarmCurrProbCause, 1279 snmpItuAlarmCurrPercSeverity, 1280 snmpItuAlarmCurrAdditText, 1281 snmpItuAlarmCurrTrendInd, 1282 snmpItuAlarmCurrDetector, 1283 snmpItuAlarmCurrServiceProvider, 1284 snmpItuAlarmCurrServiceUser } 1285 STATUS current 1286 DESCRIPTION "Objects in the ITU-T extension to the 1287 SNMP current alarm and current varBind 1288 tables." 1289 ::= { snmpAlarmGroups 6 } 1291 snmpItuAlarmLogGroup OBJECT-GROUP 1292 OBJECTS { snmpItuAlarmLogClass, 1293 snmpItuAlarmLogProbCause, 1294 snmpItuAlarmLogPercSeverity, 1295 snmpItuAlarmLogAdditText, 1296 snmpItuAlarmLogTrendInd, 1297 snmpItuAlarmLogDetector, 1298 snmpItuAlarmLogServiceProvider, 1299 snmpItuAlarmLogServiceUser } 1300 STATUS current 1301 DESCRIPTION "Objects in the ITU-T extension to the 1302 SNMP alarm log and log varBind tables." 1303 ::= { snmpAlarmGroups 7 } 1305 snmpItuAlarmNotifyGroup NOTIFICATION-GROUP 1306 NOTIFICATIONS { snmpItuAlarmStatusChange } 1307 STATUS current 1308 DESCRIPTION "Notifications for ITU-T extension to SNMP alarms." 1309 ::= { snmpAlarmGroups 8 } 1311 END 1313 6. Examples 1315 1317 7. Security Considerations 1319 There are a number of management objects defined in this MIB that 1320 have a MAX-ACCESS clause of read-write and/or read-create. Such 1321 objects may be considered sensitive or vulnerable in some network 1322 environments. The support for SET operations in a non-secure 1323 environment without proper protection can have a negative effect on 1324 network operations. 1326 SNMPv1 by itself is not a secure environment. Even if the network 1327 itself is secure (for example by using IPSec), even then, there is 1328 no control as to who on the secure network is allowed to access and 1329 GET/SET (read/change/create/delete) the objects in this MIB. 1331 It is recommended that the implementers consider the security 1332 features as provided by the SNMPv3 framework. Specifically, the use 1333 of the User-based Security Model RFC 2574 [RFC2574] and the 1334 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1336 It is then a customer/user responsibility to ensure that the SNMP 1337 entity giving access to an instance of this MIB, is properly 1338 configured to give access to the objects only to those principals 1339 (users) that have legitimate rights to indeed GET or SET 1340 (change/create/delete) them. 1342 8. Author's Address 1344 David T. Perkins 1345 SNMPinfo 1346 3663 Benton Street 1347 Santa Clara, CA 95051 1348 Phone: +1 408 394-8702 1349 Email: dperkins@dsperkins.com 1351 9. Acknowledgements 1352 This document is a product of the DISMAN Working Group. 1353 ... 1355 10. References 1357 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1358 Architecture for Describing SNMP Management Frameworks", 1359 RFC 2571, April 41999. 1361 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., 1362 Rose, M., and S. Waldbusser, "Structure of Management 1363 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1364 1999. 1366 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., 1367 Rose, M., and S. Waldbusser, "Textual Conventions for 1368 SMIv2", STD 58, RFC 2579, April 1999. 1370 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., 1371 Rose, M., and S. Waldbusser, "Conformance Statements for 1372 SMIv2", STD 58, RFC 2580, April 1999. 1374 [X.733] 1376 [X.736] ] 1378 11. Full Copyright Statement 1380 Copyright (C) The Internet Society (2001). All Rights Reserved. 1382 This document and translations of it may be copied and furnished to 1383 others, and derivative works that comment on or otherwise explain it 1384 or assist in its implementation may be prepared, copied, published 1385 and distributed, in whole or in part, without restriction of any 1386 kind, provided that the above copyright notice and this paragraph 1387 are included on all such copies and derivative works. However, this 1388 document itself may not be modified in any way, such as by removing 1389 the copyright notice or references to the Internet Society or other 1390 Internet organizations, except as needed for the purpose of 1391 developing Internet standards in which case the procedures for 1392 copyrights defined in the Internet Standards process must be 1393 followed, or as required to translate it into languages other than 1394 English. 1396 The limited permissions granted above are perpetual and will not be 1397 revoked by the Internet Society or its successors or assigns. 1399 This document and the information contained herein is provided on an 1400 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1401 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1402 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1403 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1404 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1406 1 RFC 2119 Bradner, S., "Key words for use in RFCs to Indicate 1407 Requirement Levels", BCP 14, RFC 2119, March 1997