idnits 2.17.1 draft-ietf-disman-snmp-alarm-mib-00.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 273 has weird spacing: '... field octet...' == Line 1338 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 (February 21, 2001) is 8462 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 62, but not defined == Missing Reference: 'RFC1212' is mentioned on line 62, but not defined == Missing Reference: 'RFC1215' is mentioned on line 63, but not defined == Missing Reference: 'RFC1157' is mentioned on line 78, but not defined == Missing Reference: 'RFC1901' is mentioned on line 72, but not defined == Missing Reference: 'RFC1906' is mentioned on line 74, but not defined ** Obsolete undefined reference: RFC 1906 (Obsoleted by RFC 3417) == Missing Reference: 'RFC2572' is mentioned on line 74, but not defined ** Obsolete undefined reference: RFC 2572 (Obsoleted by RFC 3412) == Missing Reference: 'RFC2574' is mentioned on line 1279, but not defined ** Obsolete undefined reference: RFC 2574 (Obsoleted by RFC 3414) == Missing Reference: 'RFC1905' is mentioned on line 80, but not defined ** Obsolete undefined reference: RFC 1905 (Obsoleted by RFC 3416) == Missing Reference: 'RFC2573' is mentioned on line 83, but not defined ** Obsolete undefined reference: RFC 2573 (Obsoleted by RFC 3413) == Missing Reference: 'RFC2575' is mentioned on line 1280, but not defined ** Obsolete undefined reference: RFC 2575 (Obsoleted by RFC 3415) == Missing Reference: 'RFC2570' is mentioned on line 87, but not defined ** Obsolete undefined reference: RFC 2570 (Obsoleted by RFC 3410) -- Looks like a reference, but probably isn't: '1' on line 118 ** 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 February 21, 2001 5 SNMP Alarms and MIB Module 6 draft-ietf-disman-snmp-alarm-mib-00.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 1.1.Terminology....................................................4 42 4. MIB Module Overview ............................................4 44 5. Definitions ....................................................5 45 6. Examples ......................................................26 46 7. Security Considerations .......................................26 47 SNMP Alarm MIB Feburary 2001 49 8. Author's Address ..............................................26 50 9. Acknowledgements ..............................................27 51 10. References ..................................................27 52 11. Full Copyright Statement ....................................27 53 SNMP Alarm MIB Feburary 2001 55 1. The SNMP Management Framework 57 o An overall architecture, described in RFC 2571 [RFC2571]. 59 o Mechanisms for describing and naming objects and events for the 60 purpose of management. The first version of this Structure of 61 Management Information (SMI) is called SMIv1 and described in 62 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 63 1215 [RFC1215]. The second version, called SMIv2, is described 64 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 65 STD 58, RFC 2580 [RFC2580]. 67 o Message protocols for transferring management information. The 68 first version of the SNMP message protocol is called SNMPv1 and 69 described in STD 15, RFC 1157 [RFC1157]. A second version of 70 the SNMP message protocol, which is not an Internet standards 71 track protocol, is called SNMPv2c and described in RFC 1901 72 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 73 message protocol is called SNMPv3 and described in RFC 1906 74 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 76 o Protocol operations for accessing management information. The 77 first set of protocol operations and associated PDU formats is 78 described in STD 15, RFC 1157 [RFC1157]. A second set of 79 protocol operations and associated PDU formats is described in 80 RFC 1905 [RFC1905]. 82 o A set of fundamental applications described in RFC 2573 83 [RFC2573] and the view-based access control mechanism described 84 in RFC 2575 [RFC2575]. 86 A more detailed introduction to the current SNMP Management 87 Framework can be found in RFC 2570 [RFC2570]. 89 Managed objects are accessed via a virtual information store, termed 90 the Management Information Base or MIB. Objects in the MIB are 91 defined using the mechanisms defined in the SMI. 93 This memo specifies a MIB module that is compliant to the SMIv2. A 94 MIB conforming to the SMIv1 can be produced through the appropriate 95 translations. The resulting translated MIB must be semantically 96 equivalent, except where objects or events are omitted because no 97 translation is possible (use of Counter64). Some machine readable 98 information in SMIv2 will be converted into textual descriptions in 99 SMIv1 during the translation process. However, this loss of machine 100 readable information is not considered to change the semantics of 101 the MIB. 103 SNMP Alarm MIB Feburary 2001 105 2. Introduction 107 There are two main approaches to management. One is based on polling 108 by a management application to determine node status, and the other 109 is based on a node sending notifications to manager when status 110 changes to and from fault conditions. The SNMP approach to date has 111 been the first. Little has been done to support the second in the 112 SNMP framework. This document provides the mechanisms for 113 management to be based on exception reporting. 115 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 116 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in 117 this document are to be interpreted as described in RFC-2119 [1]. 119 3. Exception Reporting Framework 121 1.1. Terminology 123 Error 124 A deviation of a system from intended operation. 126 Fault 127 A lasting error or warning condition. 129 Alarm 130 Persistent indication of a fault. An alarm is said to be 'set' 131 when a fault is first detected and administratively enabled. An 132 alarm is said to be 'cleared' when a fault is first noticed to 133 have ceased or administratively disabled. 135 Event 136 Something that happened. Examples include a change in status, 137 crossing a threshold, an external input to the system. 138 Additionally, setting or clearing an alarm is also an event. 140 Notification 141 An unsolicited transmission of management information due to an 142 event or condition. 144 150 4. MIB Module Overview 151 SNMP Alarm MIB Feburary 2001 153 155 158 5. Definitions 160 SNMP-ALARM-MIB DEFINITIONS ::= BEGIN 162 IMPORTS 163 MODULE-IDENTITY, 164 OBJECT-TYPE, 165 NOTIFICATION-TYPE, 166 snmpModules, 167 Gauge32, 168 Unsigned32 169 FROM SNMPv2-SMI 171 TEXTUAL-CONVENTION, 172 TruthValue, 173 AutonomousType, 174 VariablePointer, 175 TimeStamp 176 FROM SNMPv2-TC 178 SnmpAdminString 179 FROM SNMP-FRAMEWORK-MIB 181 MODULE-COMPLIANCE, 182 OBJECT-GROUP, 183 NOTIFICATION-GROUP 184 FROM SNMPv2-CONF; 186 snmpAlarmMIB MODULE-IDENTITY 187 LAST-UPDATED "200102220000Z" -- feb 22, 2001 188 ORGANIZATION "IETF Distributed Management Working Group" 189 CONTACT-INFO 190 "WG-email: disman@dorothy.bmc.com 191 Subscribe: disman-request@dorothy.bmc.com 192 In message body: 193 subscribe disman your_email_address 194 Archive: ftp://amethyst.bmc.com/pub/disman/archives 196 Chair: Randy Presuhn 197 BMC Software 198 EMail: rpresuhn@bmc.com 199 Phone: +1-301-854-6889 201 Author: David T. Perkins 202 SNMP Alarm MIB Feburary 2001 204 SNMPinfo 205 Postal: 3763 Benton Street 206 Santa Clara, CA 95051 207 EMail: dperkins@dsperkins.com 208 Phone: +1 408 394 8702" 209 DESCRIPTION 210 "This MIB module defines MIB objects and notifications that 211 provide mechanisms to monitor alarms currently active and 212 the history of alarms being set and cleared on a managed 213 system. 215 Terminology used in this MIB module: 217 Error - A deviation from intended operation. 219 Fault - A lasting error or warning condition. 221 Alarm - A persistent indication of a fault. An alarm is 222 said to be 'set' when a fault is first detected and 223 administratively enabled. An alarm is said to be 224 'cleared' when a fault is first noticed to have 225 ceased or administratively disabled. 227 Event - Something that happened. Examples include a change 228 in status, crossing a threshold, an external input 229 to the system. Additionally, setting or clearing 230 an alarm is also an event." 231 REVISION "200102220000Z" -- feb 22, 2001 232 DESCRIPTION "The initial revision" 233 ::= { snmpModules xx } -- replace "xx" with next appropriate 234 -- value 236 snmpAlarmObjects OBJECT IDENTIFIER ::= { snmpAlarmMIB 1 } 237 snmpAlarmNotifications OBJECT IDENTIFIER ::= { snmpAlarmMIB 2 } 238 snmpAlarmConformance OBJECT IDENTIFIER ::= { snmpAlarmMIB 3 } 239 snmpAlarmCompliances 240 OBJECT IDENTIFIER ::= { snmpAlarmConformance 1 } 241 snmpAlarmGroups 242 OBJECT IDENTIFIER ::= { snmpAlarmConformance 2 } 244 SnmpAlarmCond ::= TEXTUAL-CONVENTION 245 STATUS current 246 DESCRIPTION "The alarm condition. The values are: 247 set(1)....the alarm condition detected 248 clear(2)..the alarm condition ceased" 249 SYNTAX INTEGER { 250 set(1), 251 clear(2) 252 } 254 SnmpAlarmType ::= TEXTUAL-CONVENTION 255 SNMP Alarm MIB Feburary 2001 257 STATUS current 258 DESCRIPTION "The identity of the type of an SNMP alarm. The SNMP 259 SMI does not have a construct to define SNMP alarms. 260 Thus, the OBJECT-IDENTITY construct must be 261 used with the text of the DESCRIPTION clause 262 describing the conditions that cause the alarm 263 to be set and to be clear, and a description of 264 each varBind to be associated with the alarm." 265 SYNTAX OBJECT IDENTIFIER -- really AutonomousType 267 OptDateAndTime ::= TEXTUAL-CONVENTION 268 DISPLAY-HINT "2d-1d-1d,1d:1d:1d.1d,1a1d:1d" 269 STATUS current 270 DESCRIPTION 271 "An date-time specification, or a zero length string. 273 field octets contents range 274 ----- ------ -------- ----- 275 1 1-2 year 0..65536 276 2 3 month 1..12 277 3 4 day 1..31 278 4 5 hour 0..23 279 5 6 minutes 0..59 280 6 7 seconds 0..60 281 (use 60 for leap-second) 282 7 8 deci-seconds 0..9 283 8 9 direction from UTC '+' / '-' 284 9 10 hours from UTC 0..11 285 10 11 minutes from UTC 0..59 287 For example, Tuesday May 26, 1992 at 1:30:15 PM EDT would be 288 displayed as: 290 1992-5-26,13:30:15.0,-4:0 292 Note that if only local time is known, then time zone 293 information (fields 8-10) is not present." 294 SYNTAX OCTET STRING (SIZE (0 | 8 | 11)) -- DateAndTime 296 SnmpValUnion ::= TEXTUAL-CONVENTION 297 STATUS current 298 DESCRIPTION "A descriminated union, which is the 299 following ASN.1 sequence BER encoded 300 and wrapped as the value of an OCTET 301 STRING. 302
303 " 304 SYNTAX OCTET STRING 306 snmpAlarmGlobals OBJECT IDENTIFIER ::= { snmpAlarmObjects 1 } 307 SNMP Alarm MIB Feburary 2001 309 snmpAlarmCurrEntries OBJECT-TYPE 310 SYNTAX Gauge32 311 MAX-ACCESS read-only 312 STATUS current 313 DESCRIPTION "The number of entries in the current alarm table." 314 ::= { snmpAlarmGlobals 1 } 316 snmpAlarmLastChange OBJECT-TYPE 317 SYNTAX TimeStamp 318 MAX-ACCESS read-only 319 STATUS current 320 DESCRIPTION "The value of object sysUpTime when an entry was 321 added or removed from the current alarm table and 322 added to the alarm log table." 323 ::= { snmpAlarmGlobals 2 } 325 snmpAlarmLogFirstIndex OBJECT-TYPE 326 SYNTAX Unsigned32 327 MAX-ACCESS read-only 328 STATUS current 329 DESCRIPTION "The index of the oldest entry in the alarm log 330 table, or zero. The value of zero is used to 331 indicate that no entry exists in the alarm log." 332 ::= { snmpAlarmGlobals 3 } 334 snmpAlarmLogLastIndex OBJECT-TYPE 335 SYNTAX Unsigned32 336 MAX-ACCESS read-only 337 STATUS current 338 DESCRIPTION "The index of the youngest entry in the alarm log 339 table, or zero. The value of zero is used to 340 indicate that no entry exists in the alarm log." 341 ::= { snmpAlarmGlobals 4 } 343 snmpAlarmGenNotify OBJECT-TYPE 344 SYNTAX TruthValue 345 MAX-ACCESS read-write 346 STATUS current 347 DESCRIPTION "The controls whether or not notification 348 snmpAlarmStatusChange may be generated. The 349 values are: 350 true(1)...notifications may be generated 351 false(2)..notifications may not be generated" 352 ::= { snmpAlarmGlobals 5 } 354 -- ITU extension 355 snmpItuAlarmGenNotify OBJECT-TYPE 356 SYNTAX TruthValue 357 MAX-ACCESS read-write 358 STATUS current 359 SNMP Alarm MIB Feburary 2001 361 DESCRIPTION "The controls whether or not notification 362 snmpItuAlarmStatusChange may be generated. 363 The values are: 364 true(1)...notifications may be generated 365 false(2)..notifications may not be generated 367 Note: if this is enabled, then most likely 368 generation of notification snmpAlarmStatusChange 369 should be disabled." 370 ::= { snmpAlarmGlobals 6 } 372 snmpAlarmCurrTable OBJECT-TYPE 373 SYNTAX SEQUENCE OF SnmpAlarmCurrEntry 374 MAX-ACCESS not-accessible 375 STATUS current 376 DESCRIPTION "A table listing all the current 'alarms'. An 377 alarm indicates a persistent fault condition 378 in a software or hardware component or sub-system 379 that is intended to be operating. An alarm is 380 cleared by 'fixing' the fault condition or 381 administratively disabling the alarm." 382 ::= { snmpAlarmObjects 2 } 384 snmpAlarmCurrEntry OBJECT-TYPE 385 SYNTAX SnmpAlarmCurrEntry 386 MAX-ACCESS not-accessible 387 STATUS current 388 DESCRIPTION "A row in the table of current alarms. Rows cannot 389 be created or deleted via SNMP operations." 390 INDEX { snmpAlarmCurrIndex } 391 ::= { snmpAlarmCurrTable 1 } 393 SnmpAlarmCurrEntry ::= SEQUENCE { 394 snmpAlarmCurrIndex Unsigned32, 395 snmpAlarmCurrOccurDateAndTime OptDateAndTime, 396 snmpAlarmCurrOccurUpTime TimeStamp, 397 snmpAlarmCurrType SnmpAlarmType, 398 snmpAlarmCurrId Unsigned32, 399 snmpAlarmCurrContextName SnmpAdminString, 400 snmpAlarmCurrVarBinds Gauge32 401 } 403 snmpAlarmCurrIndex OBJECT-TYPE 404 SYNTAX Unsigned32(1..4294967295) 405 MAX-ACCESS not-accessible 406 STATUS current 407 DESCRIPTION "An arbitrary index of the alarm in the current 408 alarm table. The index for an existing entry is 409 not affected when a entry is added or removed from 410 the table. Index values may be cycled to the max 411 SNMP Alarm MIB Feburary 2001 413 before reuse or follow any implementation specific 414 reuse strategy." 415 ::= { snmpAlarmCurrEntry 1 } 417 snmpAlarmCurrOccurDateAndTime OBJECT-TYPE 418 SYNTAX OptDateAndTime 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION "The local date and time when the alarm was set, 422 or a zero length string. The value is a zero 423 length string when the local time cannot be 424 determined." 425 ::= { snmpAlarmCurrEntry 2 } 427 snmpAlarmCurrOccurUpTime OBJECT-TYPE 428 SYNTAX TimeStamp 429 MAX-ACCESS read-only 430 STATUS current 431 DESCRIPTION "The value of sysUpTime when the alarm was set 432 or zero. The value is zero when the alarm occurred 433 before the most recent reset of the management 434 system." 435 ::= { snmpAlarmCurrEntry 3 } 437 snmpAlarmCurrType OBJECT-TYPE 438 SYNTAX SnmpAlarmType 439 MAX-ACCESS read-only 440 STATUS current 441 DESCRIPTION "The type of the alarm." 442 ::= { snmpAlarmCurrEntry 4 } 444 snmpAlarmCurrId OBJECT-TYPE 445 SYNTAX Unsigned32 446 MAX-ACCESS read-only 447 STATUS current 448 DESCRIPTION "The ID of the alarm. No two active alarms 449 may have the same value. This value is used 450 in matching the set and clear entries in 451 the alarm log." 452 ::= { snmpAlarmCurrEntry 5 } 454 snmpAlarmCurrContextName OBJECT-TYPE 455 SYNTAX SnmpAdminString (SIZE(0..32)) 456 MAX-ACCESS read-only 457 STATUS current 458 DESCRIPTION "The context in which the alarm occurred." 459 ::= { snmpAlarmCurrEntry 6 } 461 snmpAlarmCurrVarBinds OBJECT-TYPE 462 SYNTAX Gauge32 463 MAX-ACCESS read-only 464 SNMP Alarm MIB Feburary 2001 466 STATUS current 467 DESCRIPTION "The number of varBinds associated with the 468 alarm. The count is usually at least one, 469 with at least one varBind identifying 470 the source of the alarm." 471 ::= { snmpAlarmCurrEntry 7 } 473 snmpAlarmCurrVarBindTable OBJECT-TYPE 474 SYNTAX SEQUENCE OF SnmpAlarmCurrVarBindEntry 475 MAX-ACCESS not-accessible 476 STATUS current 477 DESCRIPTION "A table of varBinds (pairs of variable and value) 478 that sparse extends the rows in table 479 snmpAlarmCurrTable. That is, for each row in table 480 snmpAlarmCurrTable, there is zero, one, or more 481 associated rows in this table. The value of object 482 snmpAlarmCurrVarBinds specifies the number of rows 483 in this table." 484 ::= { snmpAlarmObjects 3 } 486 snmpAlarmCurrVarBindEntry OBJECT-TYPE 487 SYNTAX SnmpAlarmCurrVarBindEntry 488 MAX-ACCESS not-accessible 489 STATUS current 490 DESCRIPTION "A row in the table of varBinds for current 491 alarms. Rows cannot be created or deleted via 492 SNMP operations." 493 INDEX { snmpAlarmCurrIndex, 494 snmpAlarmCurrVarBindIndex } 495 ::= { snmpAlarmCurrVarBindTable 1 } 497 SnmpAlarmCurrVarBindEntry ::= SEQUENCE { 498 snmpAlarmCurrVarBindIndex Unsigned32, 499 snmpAlarmCurrVarBindId VariablePointer, 500 snmpAlarmCurrVarBindVal SnmpValUnion 501 } 503 snmpAlarmCurrVarBindIndex OBJECT-TYPE 504 SYNTAX Unsigned32 (1..4294967295) 505 MAX-ACCESS not-accessible 506 STATUS current 507 DESCRIPTION "The index of the varBind. The value is between 508 one and the value of the associated object 509 snmpAlarmCurrVarBinds." 510 ::= { snmpAlarmCurrVarBindEntry 1 } 512 snmpAlarmCurrVarBindId OBJECT-TYPE 513 SYNTAX VariablePointer 514 MAX-ACCESS read-only 515 STATUS current 516 SNMP Alarm MIB Feburary 2001 518 DESCRIPTION "The ID of the object instance." 519 ::= { snmpAlarmCurrVarBindEntry 2 } 521 snmpAlarmCurrVarBindVal OBJECT-TYPE 522 SYNTAX SnmpValUnion 523 MAX-ACCESS read-only 524 STATUS current 525 DESCRIPTION "The value of the object instance." 526 ::= { snmpAlarmCurrVarBindEntry 3 } 528 snmpAlarmLogTable OBJECT-TYPE 529 SYNTAX SEQUENCE OF SnmpAlarmLogEntry 530 MAX-ACCESS not-accessible 531 STATUS current 532 DESCRIPTION "A table containing a log of when each 'alarm' 533 has been 'set' or 'cleared'. An alarm indicates 534 a persistent fault condition in a software or 535 hardware component or sub-system that is intended 536 to be operating. An alarm is cleared by 'fixing' 537 the fault condition or administratively disabling 538 the alarm. 540 The alarm log operates like a circular buffer. 541 The index of the oldest entry is specified by 542 object snmpAlarmLogFirstIndex and the index 543 of the youngest entry is specified by object 544 tbtSystemAlarmLogLastIndex. 546 The alarm log may be preserved in part or in 547 total across restarts of a management system. 548 The last few entries SHOULD be saved to assist 549 in determining the cause of an unplanned 550 restart." 551 ::= { snmpAlarmObjects 4 } 553 snmpAlarmLogEntry OBJECT-TYPE 554 SYNTAX SnmpAlarmLogEntry 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION "A row in the alarm log table. Rows cannot 558 be created or deleted via SNMP operations." 559 INDEX { snmpAlarmLogIndex } 560 ::= { snmpAlarmLogTable 1 } 562 SnmpAlarmLogEntry ::= SEQUENCE { 563 snmpAlarmLogIndex Unsigned32, 564 snmpAlarmLogCond SnmpAlarmCond, 565 snmpAlarmLogOccurDateAndTime OptDateAndTime, 566 snmpAlarmLogOccurUpTime TimeStamp, 567 snmpAlarmLogType SnmpAlarmType, 568 SNMP Alarm MIB Feburary 2001 570 snmpAlarmLogId Unsigned32, 571 snmpAlarmLogContextName SnmpAdminString, 572 snmpAlarmLogVarBinds Gauge32 573 } 575 snmpAlarmLogIndex OBJECT-TYPE 576 SYNTAX Unsigned32(1..4294967295) 577 MAX-ACCESS not-accessible 578 STATUS current 579 DESCRIPTION "An index of the alarm in the alarm log table. The 580 index is increased by one for each new entry in the 581 table until the maximum value is reach and then the 582 index restarts at 1. The index of the oldest entry 583 is specified by object snmpAlarmLogFirstIndex and 584 index of the youngest entry is specified by object 585 snmpAlarmLogLastIndex." 586 ::= { snmpAlarmLogEntry 1 } 588 snmpAlarmLogCond OBJECT-TYPE 589 SYNTAX SnmpAlarmCond 590 MAX-ACCESS read-only 591 STATUS current 592 DESCRIPTION "Indicates if the log entry is due to the alarm 593 Being set (raised) or being cleared." 594 ::= { snmpAlarmLogEntry 2 } 596 snmpAlarmLogOccurDateAndTime OBJECT-TYPE 597 SYNTAX OptDateAndTime 598 MAX-ACCESS read-only 599 STATUS current 600 DESCRIPTION "The local date and time when the alarm was set 601 or clear, or a zero length string. The value is a 602 zero length string when the local time cannot be 603 determined." 604 ::= { snmpAlarmLogEntry 3 } 606 snmpAlarmLogOccurUpTime OBJECT-TYPE 607 SYNTAX TimeStamp 608 MAX-ACCESS read-only 609 STATUS current 610 DESCRIPTION "The value of sysUpTime when the alarm was set or 611 cleared, or zero. The value is zero when the alarm 612 was set or cleared before the most recent reset of 613 the management system." 614 ::= { snmpAlarmLogEntry 4 } 616 snmpAlarmLogType OBJECT-TYPE 617 SYNTAX SnmpAlarmType 618 MAX-ACCESS read-only 619 STATUS current 620 DESCRIPTION "The type of the alarm." 621 SNMP Alarm MIB Feburary 2001 623 ::= { snmpAlarmLogEntry 5 } 625 snmpAlarmLogId OBJECT-TYPE 626 SYNTAX Unsigned32 627 MAX-ACCESS read-only 628 STATUS current 629 DESCRIPTION "The ID of the alarm. Each alarm that is set 630 is assigned a unique ID among active alarms. 631 That is, no two active alarms may have the 632 same value. This value is used in matching 633 the set and clear entries in this log. 634 Note: alarms may be cleared and not recorded 635 across restarts of the management system. 636 Thus, additional checks must be performed 637 to match set and clear entries in the 638 log that occur on opposite sides of a 639 restart." 640 ::= { snmpAlarmLogEntry 6 } 642 snmpAlarmLogContextName OBJECT-TYPE 643 SYNTAX SnmpAdminString (SIZE(0..32)) 644 MAX-ACCESS read-only 645 STATUS current 646 DESCRIPTION "The context in which the alarm occurred." 647 ::= { snmpAlarmLogEntry 7 } 649 snmpAlarmLogVarBinds OBJECT-TYPE 650 SYNTAX Gauge32 651 MAX-ACCESS read-only 652 STATUS current 653 DESCRIPTION "The number of varBinds associated with the 654 alarm. The count is usually at least one, 655 with at least one varBind identifying 656 the source of the alarm." 657 ::= { snmpAlarmLogEntry 8 } 659 snmpAlarmLogVarBindTable OBJECT-TYPE 660 SYNTAX SEQUENCE OF SnmpAlarmLogVarBindEntry 661 MAX-ACCESS not-accessible 662 STATUS current 663 DESCRIPTION "A table of varBinds (pairs of variable and value) 664 that sparse extends the rows in table 665 snmpAlarmLogTable. That is, for each row in table 666 snmpAlarmLogTable, there is zero, one, or more 667 associated rows in this table. The value of object 668 snmpAlarmLogVarBinds specifies the number of rows 669 in this table." 670 ::= { snmpAlarmObjects 5 } 672 snmpAlarmLogVarBindEntry OBJECT-TYPE 673 SNMP Alarm MIB Feburary 2001 675 SYNTAX SnmpAlarmLogVarBindEntry 676 MAX-ACCESS not-accessible 677 STATUS current 678 DESCRIPTION "A row in the table of varBinds for the alarm 679 log. Rows cannot be created or deleted via 680 SNMP operations." 681 INDEX { snmpAlarmLogIndex, 682 snmpAlarmLogVarBindIndex } 683 ::= { snmpAlarmLogVarBindTable 1 } 685 SnmpAlarmLogVarBindEntry ::= SEQUENCE { 686 snmpAlarmLogVarBindIndex Unsigned32, 687 snmpAlarmLogVarBindId VariablePointer, 688 snmpAlarmLogVarBindVal SnmpValUnion 689 } 691 snmpAlarmLogVarBindIndex OBJECT-TYPE 692 SYNTAX Unsigned32 (1..4294967295) 693 MAX-ACCESS not-accessible 694 STATUS current 695 DESCRIPTION "The index of the varBind. The value is between 696 one and the value of the associated object 697 snmpAlarmLogVarBinds." 698 ::= { snmpAlarmLogVarBindEntry 1 } 700 snmpAlarmLogVarBindId OBJECT-TYPE 701 SYNTAX VariablePointer 702 MAX-ACCESS read-only 703 STATUS current 704 DESCRIPTION "The ID of the object instance." 705 ::= { snmpAlarmLogVarBindEntry 2 } 707 snmpAlarmLogVarBindVal OBJECT-TYPE 708 SYNTAX SnmpValUnion 709 MAX-ACCESS read-only 710 STATUS current 711 DESCRIPTION "The value of the object instance." 712 ::= { snmpAlarmLogVarBindEntry 3 } 714 -- ITU-T extensions 715 SnmpItuAlarmClass ::= TEXTUAL-CONVENTION 716 STATUS current 717 DESCRIPTION "The class of alarm as specified in 718 [X.733] and [X.736]. 719 " 720 SYNTAX INTEGER { 721 other (1), 722 communicationsAlarm (2), 723 qualityOfServiceAlarm (3), 724 processingErrorAlarm (4), 725 SNMP Alarm MIB Feburary 2001 727 equipmentAlarm (5), 728 environmentalAlarm (6), 729 integrityViolation (7), 730 operationalViolation (8), 731 physicalViolation (9), 732 securityServiceOrMechanismViolation (10), 733 timeDomainViolation (11) 734 } 736 SnmpItuAlarmProbCause ::= TEXTUAL-CONVENTION 737 STATUS current 738 DESCRIPTION "The probable cause of the alarm as 739 specified in [X.733] and [X.736]. 740 " 741 SYNTAX INTEGER { 742 other (1), 743 adapterError (2), 744 applicationSubsystemFailure (3), 745 bandwidthReduced (4), 746 callEstablishmentError (5), 747 communicationsProtocolError (6), 748 communicationsSubsystemFailure (7), 749 configurationOrCustomizationError (8), 750 congestion (9), 751 corruptData (10), 752 cpuCyclesLimitExceeded (11), 753 dataSetOrModemError (12), 754 degradedSignal (13), 755 dteDceInterfaceError (14), 756 enclosureDoorOpen (15), 757 equipmentMalfunction (16), 758 excessiveVibration (17), 759 fileError (18), 760 fireDetected (19), 761 floodDetected (20), 762 framingError (21), 763 heatingVentCoolingSystemProblem (22), 764 humidityUnacceptable (23), 765 inputOutputDeviceError (24), 766 inputDeviceError (25), 767 lanError (26), 768 leakDetected (27), 769 localNodeTransmissionError (28), 770 lossOfFrame (29), 771 lossOfSignal (30), 772 materialSupplyExhausted (31), 773 multiplexerProblem (32), 774 outOfMemory (33), 775 ouputDeviceError (34), 776 performanceDegraded (35), 777 powerProblem (36), 778 SNMP Alarm MIB Feburary 2001 780 pressureUnacceptable (37), 781 processorProblem (38), 782 pumpFailure (39), 783 queueSizeExceeded (40), 784 receiveFailure (41), 785 receiverFailure (42), 786 remoteNodeTransmissionError (43), 787 resourceAtOrNearingCapacity (44), 788 responseTimeExecessive (45), 789 retransmissionRateExcessive (46), 790 softwareError (47), 791 softwareProgramAbnormallyTerminated (48), 792 softwareProgramError (49), 793 storageCapacityProblem (50), 794 temperatureUnacceptable (51), 795 thresholdCrossed (52), 796 timingProblem (53), 797 toxicLeakDetected (54), 798 transmitFailure (55), 799 transmitterFailure (56), 800 underlyingResourceUnavailable (57), 801 versionMismatch (58), 802 authenticationFailure (59), 803 breachOfConfidentiality (60), 804 cableTamper (61), 805 delayedInformation (62), 806 denialOfService (63), 807 duplicateInformation (64), 808 informationMissing (65), 809 informationModificationDetected (66), 810 informationOutOfSequence (67), 811 intrusionDetection (68), 812 keyExpired (69), 813 nonRepudiationFailure (70), 814 outOfHoursActivity (71), 815 outOfService (72), 816 proceduralError (73), 817 unauthorizedAccessAttempt (74), 818 unexpectedInformation (75) 819 } 821 SnmpItuAlarmPercSeverity ::= TEXTUAL-CONVENTION 822 STATUS current 823 DESCRIPTION "The perceived severity of the alarm as 824 specified in [X.733] and [X.736]. 825 " 826 SYNTAX INTEGER { 827 indeterminate (2), 828 critical (3), 829 major (4), 830 minor (5), 831 SNMP Alarm MIB Feburary 2001 833 warning (6) 834 } 836 SnmpItuAlarmTrendInd ::= TEXTUAL-CONVENTION 837 STATUS current 838 DESCRIPTION "The trend indication of the alarm as 839 specified in [X.733]. 840 " 841 SYNTAX INTEGER { 842 moreSevere (1), 843 noChange (2), 844 lessSevere (3) 845 } 847 snmpItuAlarmCurrTable OBJECT-TYPE 848 SYNTAX SEQUENCE OF SnmpItuAlarmCurrEntry 849 MAX-ACCESS not-accessible 850 STATUS current 851 DESCRIPTION "A table augmenting the current alarm table 852 (snmpAlarmCurrTable) with additional information 853 from the ITU-T alarm model." 854 ::= { snmpAlarmObjects 6 } 856 snmpItuAlarmCurrEntry OBJECT-TYPE 857 SYNTAX SnmpItuAlarmCurrEntry 858 MAX-ACCESS not-accessible 859 STATUS current 860 DESCRIPTION "A row in the table of ITU-T current alarms. Rows 861 cannot be created or deleted via SNMP operations." 862 AUGMENTS { snmpAlarmCurrEntry } 863 ::= { snmpItuAlarmCurrTable 1 } 865 SnmpItuAlarmCurrEntry ::= SEQUENCE { 866 snmpItuAlarmCurrClass SnmpItuAlarmClass, 867 snmpItuAlarmCurrProbCause SnmpItuAlarmProbCause, 868 snmpItuAlarmCurrPercSeverity SnmpItuAlarmPercSeverity, 869 snmpItuAlarmCurrAdditText SnmpAdminString, 870 snmpItuAlarmCurrTrendInd SnmpItuAlarmTrendInd, 871 snmpItuAlarmCurrDetector AutonomousType, 872 snmpItuAlarmCurrServiceProvider AutonomousType, 873 snmpItuAlarmCurrServiceUser AutonomousType 874 } 876 snmpItuAlarmCurrClass OBJECT-TYPE 877 SYNTAX SnmpItuAlarmClass 878 MAX-ACCESS read-only 879 STATUS current 880 DESCRIPTION "The class of the alarm as specified in 881 [X.733] and [X.736]. 882 " 883 SNMP Alarm MIB Feburary 2001 885 ::= { snmpItuAlarmCurrEntry 1 } 887 snmpItuAlarmCurrProbCause OBJECT-TYPE 888 SYNTAX SnmpItuAlarmProbCause 889 MAX-ACCESS read-only 890 STATUS current 891 DESCRIPTION "The probable cause of the alarm as 892 specified in [X.733] and [X.736]. 893 " 894 ::= { snmpItuAlarmCurrEntry 2 } 896 snmpItuAlarmCurrPercSeverity OBJECT-TYPE 897 SYNTAX SnmpItuAlarmPercSeverity 898 MAX-ACCESS read-only 899 STATUS current 900 DESCRIPTION "The perceived severity of the alarm as 901 specified in [X.733] and [X.736]. 902 " 903 ::= { snmpItuAlarmCurrEntry 3 } 905 snmpItuAlarmCurrAdditText OBJECT-TYPE 906 SYNTAX SnmpAdminString 907 MAX-ACCESS read-only 908 STATUS current 909 DESCRIPTION "The additional text field of the alarm as 910 specified in [X.733]. 911 " 912 ::= { snmpItuAlarmCurrEntry 4 } 914 snmpItuAlarmCurrTrendInd OBJECT-TYPE 915 SYNTAX SnmpItuAlarmTrendInd 916 MAX-ACCESS read-only 917 STATUS current 918 DESCRIPTION "The trend indication of the alarm as 919 specified in [X.733]. 920 " 921 ::= { snmpItuAlarmCurrEntry 5 } 923 -- more investigation is needed for the following objects 924 snmpItuAlarmCurrDetector OBJECT-TYPE 925 SYNTAX AutonomousType 926 MAX-ACCESS read-only 927 STATUS current 928 DESCRIPTION "The SecurityAlarmDetector object from [X.736]. 929 " 930 ::= { snmpItuAlarmCurrEntry 6 } 932 snmpItuAlarmCurrServiceProvider OBJECT-TYPE 933 SYNTAX AutonomousType 934 MAX-ACCESS read-only 935 STATUS current 936 SNMP Alarm MIB Feburary 2001 938 DESCRIPTION "The ServiceProvider object from [X.736]. 939 " 940 ::= { snmpItuAlarmCurrEntry 7 } 942 snmpItuAlarmCurrServiceUser OBJECT-TYPE 943 SYNTAX AutonomousType 944 MAX-ACCESS read-only 945 STATUS current 946 DESCRIPTION "The SericeUser object from [X.736]. 947 " 948 ::= { snmpItuAlarmCurrEntry 8 } 950 snmpItuAlarmLogTable OBJECT-TYPE 951 SYNTAX SEQUENCE OF SnmpItuAlarmLogEntry 952 MAX-ACCESS not-accessible 953 STATUS current 954 DESCRIPTION "A table augmenting the alarm log table 955 (snmpAlarmLogTable) with additional information 956 from the ITU-T alarm model." 957 ::= { snmpAlarmObjects 7 } 959 snmpItuAlarmLogEntry OBJECT-TYPE 960 SYNTAX SnmpItuAlarmLogEntry 961 MAX-ACCESS not-accessible 962 STATUS current 963 DESCRIPTION "A row in the ITU-T alarm log table. Rows cannot 964 be created or deleted via SNMP operations." 965 AUGMENTS { snmpAlarmLogEntry } 966 ::= { snmpItuAlarmLogTable 1 } 968 SnmpItuAlarmLogEntry ::= SEQUENCE { 969 snmpItuAlarmLogClass SnmpItuAlarmClass, 970 snmpItuAlarmLogProbCause SnmpItuAlarmProbCause, 971 snmpItuAlarmLogPercSeverity SnmpItuAlarmPercSeverity, 972 snmpItuAlarmLogAdditText SnmpAdminString, 973 snmpItuAlarmLogTrendInd SnmpItuAlarmTrendInd, 974 snmpItuAlarmLogDetector AutonomousType, 975 snmpItuAlarmLogServiceProvider AutonomousType, 976 snmpItuAlarmLogServiceUser AutonomousType 977 } 979 snmpItuAlarmLogClass OBJECT-TYPE 980 SYNTAX SnmpItuAlarmClass 981 MAX-ACCESS read-only 982 STATUS current 983 DESCRIPTION "The class of the alarm as specified in 984 [X.733] and [X.736]. 985 " 986 ::= { snmpItuAlarmLogEntry 1 } 988 snmpItuAlarmLogProbCause OBJECT-TYPE 989 SNMP Alarm MIB Feburary 2001 991 SYNTAX SnmpItuAlarmProbCause 992 MAX-ACCESS read-only 993 STATUS current 994 DESCRIPTION "The probable cause of the alarm as 995 specified in [X.733] and [X.736]. 996 " 997 ::= { snmpItuAlarmLogEntry 2 } 999 snmpItuAlarmLogPercSeverity OBJECT-TYPE 1000 SYNTAX SnmpItuAlarmPercSeverity 1001 MAX-ACCESS read-only 1002 STATUS current 1003 DESCRIPTION "The perceived severity of the alarm as 1004 specified in [X.733] and [X.736]. 1005 " 1006 ::= { snmpItuAlarmLogEntry 3 } 1008 snmpItuAlarmLogAdditText OBJECT-TYPE 1009 SYNTAX SnmpAdminString 1010 MAX-ACCESS read-only 1011 STATUS current 1012 DESCRIPTION "The additional text field of the alarm as 1013 specified in [X.733]. 1014 " 1015 ::= { snmpItuAlarmLogEntry 4 } 1017 snmpItuAlarmLogTrendInd OBJECT-TYPE 1018 SYNTAX SnmpItuAlarmTrendInd 1019 MAX-ACCESS read-only 1020 STATUS current 1021 DESCRIPTION "The trend indication of the alarm as 1022 specified in [X.733]. 1023 " 1024 ::= { snmpItuAlarmLogEntry 5 } 1026 -- more investigation is needed for the following objects 1027 snmpItuAlarmLogDetector OBJECT-TYPE 1028 SYNTAX AutonomousType 1029 MAX-ACCESS read-only 1030 STATUS current 1031 DESCRIPTION "The SecurityAlarmDetector object from [X.736]. 1032 " 1033 ::= { snmpItuAlarmLogEntry 6 } 1035 snmpItuAlarmLogServiceProvider OBJECT-TYPE 1036 SYNTAX AutonomousType 1037 MAX-ACCESS read-only 1038 STATUS current 1039 DESCRIPTION "The ServiceProvider object from [X.736]. 1040 " 1041 ::= { snmpItuAlarmLogEntry 7 } 1042 SNMP Alarm MIB Feburary 2001 1044 snmpItuAlarmLogServiceUser OBJECT-TYPE 1045 SYNTAX AutonomousType 1046 MAX-ACCESS read-only 1047 STATUS current 1048 DESCRIPTION "The SericeUser object from [X.736]. 1049 " 1050 ::= { snmpItuAlarmLogEntry 8 } 1052 -- notifications 1054 snmpAlarmStatusChange NOTIFICATION-TYPE 1055 OBJECTS { snmpAlarmLogCond, 1056 snmpAlarmLogOccurDateAndTime, 1057 snmpAlarmLogOccurUpTime, 1058 snmpAlarmLogId, 1059 snmpAlarmLogVarBinds } 1060 STATUS current 1061 DESCRIPTION "An entry has been added to the alarm log 1062 table. That is, an alarm has been set or cleared. 1063 The objects all have the same instance, which is 1064 the row in the alarm log, and the objects are: 1065 snmpAlarmLogCond....alarm condition, either 1066 set or clear 1067 snmpAlarmLogOccurDateAndTime...date/time the 1068 alarm log entry created 1069 snmpAlarmLogOccurUpTime...timestamp the alarm 1070 log entry created 1071 snmpAlarmLogId....the ID of the alarm 1072 snmpAlarmLogVarBinds....the number of varBinds 1073 associated with the alarm 1075 Note 1: after these varBinds, the associated 1076 varBinds, if any, from table 1077 snmpAlarmLogVarBindTable must be specified in the 1078 varBind list for the notification. 1080 Note 2: object snmpAlarmGenNotify controls 1081 if or if not this notification may be generated." 1082 ::= { snmpAlarmNotifications 0 1 } 1084 snmpItuAlarmStatusChange NOTIFICATION-TYPE 1085 OBJECTS { snmpAlarmLogCond, 1086 snmpAlarmLogOccurDateAndTime, 1087 snmpAlarmLogOccurUpTime, 1088 snmpAlarmLogId, 1089 snmpAlarmLogVarBinds, 1090 snmpItuAlarmLogClass, 1091 snmpItuAlarmLogProbCause, 1092 snmpItuAlarmLogPercSeverity, 1093 SNMP Alarm MIB Feburary 2001 1095 snmpItuAlarmLogAdditText, 1096 snmpItuAlarmLogTrendInd, 1097 snmpItuAlarmLogDetector, 1098 snmpItuAlarmLogServiceProvider, 1099 snmpItuAlarmLogServiceUser } 1100 STATUS current 1101 DESCRIPTION "An entry has been added to the alarm log 1102 table and the ITU extensions are supported. 1103 That is, an alarm has been set or cleared. 1104 The objects all have the same instance, which is 1105 the row in the alarm log, and the objects are: 1106 snmpAlarmLogCond....alarm condition, either 1107 set or clear 1108 snmpAlarmLogOccurDateAndTime...date/time the 1109 alarm log entry created 1110 snmpAlarmLogOccurUpTime...timestamp the alarm 1111 log entry created 1112 snmpAlarmLogId....the ID of the alarm 1113 snmpAlarmLogVarBinds....the number of varBinds 1114 associated with the alarm 1115 1116 snmpItuAlarmLogClass... 1117 snmpItuAlarmLogProbCause... 1118 snmpItuAlarmLogPercSeverity... 1119 snmpItuAlarmLogAdditText... 1120 snmpItuAlarmLogTrendInd... 1121 snmpItuAlarmLogDetector... 1122 snmpItuAlarmLogServiceProvider... 1123 snmpItuAlarmLogServiceUser... 1125 Note 1: after these varBinds, the associated 1126 varBinds, if any, from table 1127 snmpAlarmLogVarBindTable must be specified in the 1128 varBind list for the notification. 1130 Note 2: object snmpItuAlarmGenNotify controls 1131 if or if not this notification may be generated." 1132 ::= { snmpAlarmNotifications 0 2 } 1134 -- Conformance 1136 snmpAlarmCompliance MODULE-COMPLIANCE 1137 STATUS current 1138 DESCRIPTION 1139 "The compliance statement for systems supporting 1140 the SNMP alarms." 1141 MODULE -- this module 1142 MANDATORY-GROUPS { snmpAlarmGblGroup, 1143 snmpAlarmCurrGroup, 1144 snmpAlarmLogGroup, 1146 SNMP Alarm MIB Feburary 2001 1148 snmpAlarmNotifyGroup } 1149 ::= { snmpAlarmCompliances 1 } 1151 snmpItuAlarmCompliance MODULE-COMPLIANCE 1152 STATUS current 1153 DESCRIPTION 1154 "The compliance statement for systems supporting 1155 the ITU-T extension to SNMP alarms." 1156 MODULE -- this module 1157 MANDATORY-GROUPS { snmpAlarmGblGroup, 1158 snmpAlarmCurrGroup, 1159 snmpAlarmLogGroup, 1160 snmpAlarmNotifyGroup, 1161 snmpItuAlarmGblGroup, 1162 snmpItuAlarmCurrGroup, 1163 snmpItuAlarmLogGroup, 1164 snmpItuAlarmNotifyGroup } 1165 ::= { snmpAlarmCompliances 2 } 1167 snmpAlarmGblGroup OBJECT-GROUP 1168 OBJECTS { snmpAlarmCurrEntries, 1169 snmpAlarmLastChange, 1170 snmpAlarmLogFirstIndex, 1171 snmpAlarmLogLastIndex, 1172 snmpAlarmGenNotify } 1173 STATUS current 1174 DESCRIPTION "Global objects for managing SNMP alarms." 1175 ::= { snmpAlarmGroups 1 } 1177 snmpAlarmCurrGroup OBJECT-GROUP 1178 OBJECTS { snmpAlarmCurrOccurDateAndTime, 1179 snmpAlarmCurrOccurUpTime, 1180 snmpAlarmCurrType, 1181 snmpAlarmCurrId, 1182 snmpAlarmCurrContextName, 1183 snmpAlarmCurrVarBinds, 1184 snmpAlarmCurrVarBindId, 1185 snmpAlarmCurrVarBindVal } 1186 STATUS current 1187 DESCRIPTION "Objects in the SNMP current alarm and 1188 current varBind tables." 1189 ::= { snmpAlarmGroups 2 } 1191 snmpAlarmLogGroup OBJECT-GROUP 1192 OBJECTS { snmpAlarmLogCond, 1193 snmpAlarmLogOccurDateAndTime, 1194 snmpAlarmLogOccurUpTime, 1195 snmpAlarmLogType, 1196 snmpAlarmLogId, 1197 SNMP Alarm MIB Feburary 2001 1199 snmpAlarmLogContextName, 1200 snmpAlarmLogVarBinds, 1201 snmpAlarmLogVarBindId, 1202 snmpAlarmLogVarBindVal } 1203 STATUS current 1204 DESCRIPTION "Objects in the SNMP alarm log and 1205 log varBind tables." 1206 ::= { snmpAlarmGroups 3 } 1208 snmpAlarmNotifyGroup NOTIFICATION-GROUP 1209 NOTIFICATIONS { snmpAlarmStatusChange } 1210 STATUS current 1211 DESCRIPTION "Notifications for SNMP alarms." 1212 ::= { snmpAlarmGroups 4 } 1214 snmpItuAlarmGblGroup OBJECT-GROUP 1215 OBJECTS { snmpItuAlarmGenNotify } 1216 STATUS current 1217 DESCRIPTION "Global objects for managing ITU-T 1218 extensions to SNMP alarms." 1219 ::= { snmpAlarmGroups 5 } 1221 snmpItuAlarmCurrGroup OBJECT-GROUP 1222 OBJECTS { snmpItuAlarmCurrClass, 1223 snmpItuAlarmCurrProbCause, 1224 snmpItuAlarmCurrPercSeverity, 1225 snmpItuAlarmCurrAdditText, 1226 snmpItuAlarmCurrTrendInd, 1227 snmpItuAlarmCurrDetector, 1228 snmpItuAlarmCurrServiceProvider, 1229 snmpItuAlarmCurrServiceUser } 1230 STATUS current 1231 DESCRIPTION "Objects in the ITU-T extension to the 1232 SNMP current alarm and current varBind 1233 tables." 1234 ::= { snmpAlarmGroups 6 } 1236 snmpItuAlarmLogGroup OBJECT-GROUP 1237 OBJECTS { snmpItuAlarmLogClass, 1238 snmpItuAlarmLogProbCause, 1239 snmpItuAlarmLogPercSeverity, 1240 snmpItuAlarmLogAdditText, 1241 snmpItuAlarmLogTrendInd, 1242 snmpItuAlarmLogDetector, 1243 snmpItuAlarmLogServiceProvider, 1244 snmpItuAlarmLogServiceUser } 1245 STATUS current 1246 DESCRIPTION "Objects in the ITU-T extension to the 1247 SNMP alarm log and log varBind tables." 1248 ::= { snmpAlarmGroups 7 } 1249 SNMP Alarm MIB Feburary 2001 1251 snmpItuAlarmNotifyGroup NOTIFICATION-GROUP 1252 NOTIFICATIONS { snmpItuAlarmStatusChange } 1253 STATUS current 1254 DESCRIPTION "Notifications for ITU-T extension to SNMP alarms." 1255 ::= { snmpAlarmGroups 8 } 1257 END 1259 6. Examples 1261 1263 7. Security Considerations 1265 There are a number of management objects defined in this MIB that 1266 have a MAX-ACCESS clause of read-write and/or read-create. Such 1267 objects may be considered sensitive or vulnerable in some network 1268 environments. The support for SET operations in a non-secure 1269 environment without proper protection can have a negative effect on 1270 network operations. 1272 SNMPv1 by itself is not a secure environment. Even if the network 1273 itself is secure (for example by using IPSec), even then, there is 1274 no control as to who on the secure network is allowed to access and 1275 GET/SET (read/change/create/delete) the objects in this MIB. 1277 It is recommended that the implementers consider the security 1278 features as provided by the SNMPv3 framework. Specifically, the use 1279 of the User-based Security Model RFC 2574 [RFC2574] and the 1280 View-based Access Control Model RFC 2575 [RFC2575] is recommended. 1282 It is then a customer/user responsibility to ensure that the SNMP 1283 entity giving access to an instance of this MIB, is properly 1284 configured to give access to the objects only to those principals 1285 (users) that have legitimate rights to indeed GET or SET 1286 (change/create/delete) them. 1288 8. Author's Address 1290 David T. Perkins 1291 SNMPinfo 1292 3663 Benton Street 1293 Santa Clara, CA 95051 1294 Phone: +1 408 394-8702 1295 Email: dperkins@dsperkins.com 1296 SNMP Alarm MIB Feburary 2001 1298 9. Acknowledgements 1300 This document is a product of the DISMAN Working Group. 1301 ... 1303 10. References 1305 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 1306 Architecture for Describing SNMP Management Frameworks", 1307 RFC 2571, April 41999. 1309 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., 1310 Rose, M., and S. Waldbusser, "Structure of Management 1311 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 1312 1999. 1314 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., 1315 Rose, M., and S. Waldbusser, "Textual Conventions for 1316 SMIv2", STD 58, RFC 2579, April 1999. 1318 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case,J., 1319 Rose, M., and S. Waldbusser, "Conformance Statements for 1320 SMIv2", STD 58, RFC 2580, April 1999. 1322 [X.733] 1324 [X.736] ] 1326 11. Full Copyright Statement 1328 Copyright (C) The Internet Society (2001). All Rights Reserved. 1330 This document and translations of it may be copied and furnished to 1331 others, and derivative works that comment on or otherwise explain it 1332 or assist in its implementation may be prepared, copied, published 1333 and distributed, in whole or in part, without restriction of any 1334 kind, provided that the above copyright notice and this paragraph 1335 are included on all such copies and derivative works. However, this 1336 document itself may not be modified in any way, such as by removing 1337 the copyright notice or references to the Internet Society or other 1338 Internet organizations, except as needed for the purpose of 1339 developing Internet standards in which case the procedures for 1340 copyrights defined in the Internet Standards process must be 1341 followed, or as required to translate it into languages other than 1342 English. 1344 SNMP Alarm MIB Feburary 2001 1346 The limited permissions granted above are perpetual and will not be 1347 revoked by the Internet Society or its successors or assigns. 1349 This document and the information contained herein is provided on an 1350 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 1351 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING 1352 BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION 1353 HEREIN WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 1354 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. 1356 1 RFC 2119 Bradner, S., "Key words for use in RFCs to Indicate 1357 Requirement Levels", BCP 14, RFC 2119, March 1997