idnits 2.17.1 draft-ietf-disman-itualarm-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: ---------------------------------------------------------------------------- ** Missing document type: Expected "INTERNET-DRAFT" in the upper left hand corner of the first page ** The document seems to lack a 1id_guidelines paragraph about the list of current Internet-Drafts -- however, there's a paragraph with a matching beginning. Boilerplate error? == 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. ** There are 28 instances of lines with control characters in the document. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the RFC 3978 Section 5.4 Copyright Line does not match the current year == Line 803 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.) -- Couldn't find a document date in the document -- date freshness check skipped. Checking references for intended status: Proposed Standard ---------------------------------------------------------------------------- (See RFCs 3967 and 4897 for information about using normative references to lower-maturity documents in RFCs) == Unused Reference: 'RFC2274' is defined on line 772, but no explicit reference was found in the text == Unused Reference: 'RFC2275' is defined on line 776, but no explicit reference was found in the text ** Obsolete normative reference: RFC 2571 (Obsoleted by RFC 3411) ** Downref: Normative reference to an Informational RFC: RFC 1215 ** Downref: Normative reference to an Historic RFC: RFC 1157 ** Downref: Normative reference to an Historic RFC: RFC 1901 ** Obsolete normative reference: RFC 1906 (Obsoleted by RFC 3417) ** Obsolete normative reference: RFC 2572 (Obsoleted by RFC 3412) ** Obsolete normative reference: RFC 2574 (Obsoleted by RFC 3414) ** Obsolete normative reference: RFC 1905 (Obsoleted by RFC 3416) ** Obsolete normative reference: RFC 2573 (Obsoleted by RFC 3413) ** Obsolete normative reference: RFC 2575 (Obsoleted by RFC 3415) ** Obsolete normative reference: RFC 2570 (Obsoleted by RFC 3410) ** Obsolete normative reference: RFC 2274 (Obsoleted by RFC 2574) ** Obsolete normative reference: RFC 2275 (Obsoleted by RFC 2575) -- Possible downref: Non-RFC (?) normative reference: ref. 'ALARM-MIB' Summary: 19 errors (**), 0 flaws (~~), 5 warnings (==), 3 comments (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Disman Working Group S. Chisholm 2 Internet Standards Track Nortel Networks 3 Document: draft-ietf-disman-itualarm-mib-01.txt D. Romascanu 4 Expiration Date: Sept 2001 Avaya Inc. 5 March 2 2001 7 ITU Alarm MIB 9 Status of this Memo 11 This document is an Internet-Draft and is in full conformance 12 with all provisions of Section 10 of RFC2026. 14 Internet-Drafts are working documents of the Internet Engineering 15 Task Force (IETF), its areas, and its working groups. Note that 16 other groups may also distribute working documents as 17 Internet-Drafts. 19 Internet-Drafts are draft documents valid for a maximum of six 20 months and may be updated, replaced, or obsoleted by other 21 documents at any time. It is inappropriate to use Internet- 22 Drafts as reference material or to cite them other than as 23 "work in progress." 25 The list of current Internet-Drafts can be accessed at 27 http://www.ietf.org/ietf/1id-abstracts.txt 29 The list of Internet-Draft Shadow Directories can be accessed at 30 http://www.ietf.org/shadow.html. 32 Abstract 34 This memo defines a portion of the Management Information Base (MIB) 35 for use with network management protocols in the Internet community. 36 In particular, it describes management objects used for describing 37 alarms using the ITU Alarm Model, defined in X.733 and X.736. 39 Table of Contents 41 1. The SNMP Management Framework 42 2. Introduction 43 3. ITU Alarm Architecture 44 3.1. Relation to Alarm MIB 45 3.2. Alarm States 46 3.3. ITU-T X.733, X.736 Trap Content 47 4. MIB Overview 48 5. Definitions 49 6. Example 50 7. Security Considerations 51 8. Authors' Address 52 9. Acknowledgements 53 10. References 54 11. Full Copyright Statement 55 1.The SNMP Management Framework 57 The SNMP Management Framework presently consists of five major 58 components: 60 o An overall architecture, described in RFC 2571 [RFC2571]. 62 o Mechanisms for describing and naming objects and events for the 63 purpose of management. The first version of this Structure of 64 Management Information (SMI) is called SMIv1 and described in 65 STD 16, RFC 1155 [RFC1155], STD 16, RFC 1212 [RFC1212] and RFC 66 1215 [RFC1215]. The second version, called SMIv2, is described 67 in STD 58, RFC 2578 [RFC2578], STD 58, RFC 2579 [RFC2579] and 68 STD 58, RFC 2580 [RFC2580]. 70 o Message protocols for transferring management information. The 71 first version of the SNMP message protocol is called SNMPv1 and 72 described in STD 15, RFC 1157 [RFC1157]. A second version of 73 the SNMP message protocol, which is not an Internet standards 74 track protocol, is called SNMPv2c and described in RFC 1901 75 [RFC1901] and RFC 1906 [RFC1906]. The third version of the 76 message protocol is called SNMPv3 and described in RFC 1906 77 [RFC1906], RFC 2572 [RFC2572] and RFC 2574 [RFC2574]. 79 o Protocol operations for accessing management information. The 80 first set of protocol operations and associated PDU formats is 81 described in STD 15, RFC 1157 [RFC1157]. A second set of 82 protocol operations and associated PDU formats is described in 83 RFC 1905 [RFC1905]. 85 o A set of fundamental applications described in RFC 2573 86 [RFC2573] and the view-based access control mechanism described 87 in RFC 2575 [RFC2575]. 89 A more detailed introduction to the current SNMP Management Framework 90 can be found in RFC 2570 [RFC2570]. 92 Managed objects are accessed via a virtual information store, termed 93 the Management Information Base or MIB. Objects in the MIB are 94 defined using the mechanisms defined in the SMI. 96 This memo specifies a MIB module that is compliant to the SMIv2. A 97 MIB conforming to the SMIv1 can be produced through the appropriate 98 translations. The resulting translated MIB must be semantically 99 equivalent, except where objects or events are omitted because no 100 translation is possible (use of Counter64). Some machine readable 101 information in SMIv2 will be converted into textual descriptions in 102 SMIv1 during the translation process. However, this loss of machine 103 readable information is not considered to change the semantics of the 104 MIB. 106 2. Introduction 108 This MIB module defines alarms specific to the model defined in ITU 109 X.733[X.733] and X.736[X.736]. This MIB module follows the modular 110 architecture defined by the Alarm MIB[ALARM-MIB], in which the 111 model-neutral Alarm MIB can be augmented by other alarm information 112 defined according to more specific models that determine their 113 behaviour and characteristics. 115 3. ITU Alarm Architecture 117 3.1 Relation to Alarm MIB 119 This MIB will be used in conjunction with the Alarm MIB [ALARM-MIB]. 121 The relationship between the Alarm MIB and the ITU Alarm MIB is 122 expressed by the following: 124 The alarmDetailsTable has a corresponding table in the ITU Alarms MIB 125 - the ituAlarmTable - with similar indexing. For each row in the 126 ituAlarmTable there is one row in the alarmDetailsTable. 128 The alarmActiveTable has a corresponding table in the ITU Alarms MIBs 129 - the ituAlarmActiveTable - with similar indexing. For each row in the 130 ituAlarmTable there is one row in the alarmActiveTable 132 Also, the alarmDetailsModelPointer object in the alarmDetailsTable 133 points to the ituAlarm module, identifying alarms that comply to the 134 ITU alarm model. The alarmActiveModelPointer object in the 135 alarmActiveTable points to the ituAlarm module identifying active 136 alarms that comply to the ITU alarm model. 138 3.2 Alarm States 140 The raise and clear relationship is defined in the Alarm MIB. The ITU 141 alarm model allows for more alarm states. These states are indicated 142 using ituAlarmPerceivedSeverity object. 144 3.3 ITU-T X.733, X.736 Trap Content 146 Mandatory Alarm information from ITU-T X.733, X.736 alarm documents 147 has been included in the ituAlarmTable and the ituAlarmActiveTable, 148 depending on the variability of this information. 150 4. MIB Overview 152 The ituAlarmTable contains information from the ITU Alarm Model about 153 possible alarms in the system. 155 The ituAlarmActiveTable contains information from the ITU Alarm Model 156 about alarms which are currently occurring on the system. 158 5. Definitions 159 ITU-ALARM-MIB DEFINITIONS ::= BEGIN 161 IMPORTS 162 MODULE-IDENTITY, OBJECT-TYPE, 163 Counter32, Gauge32, mib-2 FROM SNMPv2-SMI 164 DisplayString, AutonomousType FROM SNMPv2-TC 165 alarmListName, alarmDetailsIndex, 166 alarmActiveTimeFilter FROM ALARM-MIB 167 MODULE-COMPLIANCE, OBJECT-GROUP FROM SNMPv2-CONF; 169 ituAlarm MODULE-IDENTITY 170 LAST-UPDATED "200103020000Z" 171 ORGANIZATION "IETF Distributed Management Working Group" 172 CONTACT-INFO 173 " Sharon Chisholm 174 Nortel Networks 175 PO Box 3511 Station C 176 Ottawa, Ont. K1Y 4H7 177 Canada 178 schishol@nortelnetworks.com 180 Dan Romascanu 181 Avaya Inc. 182 Atidim Technology Park, Bldg. #3 183 Tel Aviv, 61131 184 Israel 185 Tel: +972-3-645-8414 186 Email: dromasca@avaya.com" 187 DESCRIPTION 188 "The MIB module describes ITU Alarm information 189 as defined in ITU Recommendation X.733 [X.733] 190 and ITU Recommendation X.736 [X.736]." 192 REVISION "200103020000Z" 193 DESCRIPTION 194 "Initial version, published as RFC XXXX." 195 ::= { mib-2 xx } 197 ituAlarmObjects OBJECT IDENTIFIER ::= { ituAlarm 1 } 199 ituAlarmDetails OBJECT IDENTIFIER ::= { ituAlarmObjects 1 } 201 ituAlarmActive OBJECT IDENTIFIER ::= { ituAlarmObjects 2 } 202 ituAlarmTable OBJECT-TYPE 203 SYNTAX SEQUENCE OF ItuAlarmEntry 204 MAX-ACCESS not-accessible 205 STATUS current 206 DESCRIPTION 207 "A table of ITU Alarm information about possible alarms 208 on the system." 209 ::= { ituAlarmDetails 1 } 211 ituAlarmEntry OBJECT-TYPE 212 SYNTAX ItuAlarmEntry 213 MAX-ACCESS not-accessible 214 STATUS current 215 DESCRIPTION 216 "Entries appear in this table for each possible alarm." 217 INDEX { alarmListName, alarmDetailsIndex } 218 ::= { ituAlarmTable 1 } 220 ItuAlarmEntry ::= SEQUENCE { 221 ituAlarmEventType INTEGER, 222 ituAlarmProbableCause INTEGER, 223 ituAlarmPerceivedSeverity INTEGER, 224 ituAlarmAdditionalText DisplayString, 225 ituAlarmDetector AutonomousType, 226 ituAlarmServiceProvider AutonomousType, 227 ituAlarmServiceUser AutonomousType } 229 ituAlarmEventType OBJECT-TYPE 230 SYNTAX INTEGER 231 { 232 other (1), 233 communicationsAlarm (2), 234 qualityOfServiceAlarm (3), 235 processingErrorAlarm (4), 236 equipmentAlarm (5), 237 environmentalAlarm (6), 238 integrityViolation (7), 239 operationalViolation (8), 240 physicalViolation (9), 241 securityServiceOrMechanismViolation (10), 242 timeDomainViolation (11) 243 } 244 MAX-ACCESS read-only 245 STATUS current 246 DESCRIPTION 247 " Represents the event type values for the alarms as per 248 [X.733] and [X.736]" 249 ::= { ituAlarmEntry 1 } 251 ituAlarmProbableCause OBJECT-TYPE 252 SYNTAX INTEGER 253 { 254 other (1), 255 adapterError (2), 256 applicationSubsystemFailure (3), 257 bandwidthReduced (4), 258 callEstablishmentError (5), 259 communicationsProtocolError (6), 260 communicationsSubsystemFailure (7), 261 configurationOrCustomizationError (8), 262 congestion (9), 263 corruptData (10), 264 cpuCyclesLimitExceeded (11), 265 dataSetOrModemError (12), 266 degradedSignal (13), 267 dteDceInterfaceError (14), 268 enclosureDoorOpen (15), 269 equipmentMalfunction (16), 270 excessiveVibration (17), 271 fileError (18), 272 fireDetected (19), 273 floodDetected (20), 274 framingError (21), 275 heatingVentCoolingSystemProblem (22), 276 humidityUnacceptable (23), 277 inputOutputDeviceError (24), 278 inputDeviceError (25), 279 lanError (26), 280 leakDetected (27), 281 localNodeTransmissionError (28), 282 lossOfFrame (29), 283 lossOfSignal (30), 284 materialSupplyExhausted (31), 285 multiplexerProblem (32), 286 outOfMemory (33), 287 ouputDeviceError (34), 288 performanceDegraded (35), 289 powerProblem (36), 290 pressureUnacceptable (37), 291 processorProblem (38), 292 pumpFailure (39), 293 queueSizeExceeded (40), 294 receiveFailure (41), 295 receiverFailure (42), 296 remoteNodeTransmissionError (43), 297 resourceAtOrNearingCapacity (44), 298 responseTimeExecessive (45), 299 retransmissionRateExcessive (46), 300 softwareError (47), 301 softwareProgramAbnormallyTerminated (48), 302 softwareProgramError (49), 303 storageCapacityProblem (50), 304 temperatureUnacceptable (51), 305 thresholdCrossed (52), 306 timingProblem (53), 307 toxicLeakDetected (54), 308 transmitFailure (55), 309 transmitterFailure (56), 310 underlyingResourceUnavailable (57), 311 versionMismatch (58), 312 authenticationFailure (59), 313 breachOfConfidentiality (60), 314 cableTamper (61), 315 delayedInformation (62), 316 denialOfService (63), 317 duplicateInformation (64), 318 informationMissing (65), 319 informationModificationDetected (66), 320 informationOutOfSequence (67), 321 intrusionDetection (68), 322 keyExpired (69), 323 nonRepudiationFailure (70), 324 outOfHoursActivity (71), 325 outOfService (72), 326 proceduralError (73), 327 unauthorizedAccessAttempt (74), 328 unexpectedInformation (75) 329 } 330 MAX-ACCESS read-only 331 STATUS current 333 DESCRIPTION 334 " Represents the probable cause values for the alarms as 335 per [X.733] and [X.736]." 336 ::= { ituAlarmEntry 2 } 338 ituAlarmPerceivedSeverity OBJECT-TYPE 339 SYNTAX INTEGER { 340 cleared (1), 341 indeterminate (2), 342 critical (3), 343 major (4), 344 minor (5), 345 warning (6) 346 } 347 MAX-ACCESS read-only 348 STATUS current 349 DESCRIPTION 350 " Represents the perceived severity values for the alarms 351 as per [X.733]." 352 ::= { ituAlarmEntry 3 } 354 ituAlarmAdditionalText OBJECT-TYPE 355 SYNTAX DisplayString 356 MAX-ACCESS read-only 357 STATUS current 358 DESCRIPTION 359 " Represents the additional text field for the alarm 360 as per [X.733]." 361 ::= { ituAlarmEntry 4} 363 ituAlarmDetector OBJECT-TYPE 364 SYNTAX AutonomousType 365 MAX-ACCESS read-only 366 STATUS current 367 DESCRIPTION 368 "Represents the SecurityAlarmDetector object from [X.736]." 369 ::= { ituAlarmEntry 5 } 371 ituAlarmServiceProvider OBJECT-TYPE 372 SYNTAX AutonomousType 373 MAX-ACCESS read-only 374 STATUS current 375 DESCRIPTION 376 "Represents the ServiceProvider object from [X.736]." 377 ::= { ituAlarmEntry 6 } 379 ituAlarmServiceUser OBJECT-TYPE 380 SYNTAX AutonomousType 381 MAX-ACCESS read-only 382 STATUS current 383 DESCRIPTION 384 "Represents the SericeUser object from [X.736]." 385 ::= { ituAlarmEntry 7 } 387 -- ITU Active Alarm Table -- 389 ituAlarmActiveTable OBJECT-TYPE 390 SYNTAX SEQUENCE OF ItuAlarmActiveEntry 391 MAX-ACCESS not-accessible 392 STATUS current 393 DESCRIPTION 394 "A table of ITU information for active alarms entries." 395 ::= { ituAlarmActive 1 } 397 ituAlarmActiveEntry OBJECT-TYPE 398 SYNTAX ItuAlarmActiveEntry 399 MAX-ACCESS not-accessible 400 STATUS current 401 DESCRIPTION 402 "Entries appear in this table when alarms are active. They 403 are removed when the alarm is no longer occurring." 404 INDEX { alarmListName, alarmActiveTimeFilter, 405 alarmDetailsIndex } 406 ::= { ituAlarmActiveTable 1 } 408 ItuAlarmActiveEntry ::= SEQUENCE { 409 ituAlarmActiveTrendIndication INTEGER 410 } 412 ituAlarmActiveTrendIndication OBJECT-TYPE 413 SYNTAX INTEGER 414 { 415 moreSevere (1), 416 noChange (2), 417 lessSevere (3) 418 } 419 MAX-ACCESS read-only 420 STATUS current 421 DESCRIPTION 422 " Represents the trend indication values for the alarms 423 as per [X.733]." 424 ::= { ituAlarmActiveEntry 1 } 426 ituAlarmActiveStatsTable OBJECT-TYPE 427 SYNTAX SEQUENCE OF ItuAlarmActiveStatsEntry 428 MAX-ACCESS not-accessible 429 STATUS current 430 DESCRIPTION 431 "This table represents the ITU alarm statistics 432 information." 433 ::= { ituAlarmActive 2 } 435 ituAlarmActiveStatsEntry OBJECT-TYPE 436 SYNTAX ItuAlarmActiveStatsEntry 437 MAX-ACCESS not-accessible 438 STATUS current 439 DESCRIPTION 440 "Statistics on the current active ITU alarms." 441 INDEX { alarmListName } 443 ::= { ituAlarmActiveStatsTable 1 } 445 ItuAlarmActiveStatsEntry ::= 446 SEQUENCE { 447 ituAlarmActiveStatsIndeterminateCurrent Gauge32, 448 ituAlarmActiveStatsCriticalCurrent Gauge32, 449 ituAlarmActiveStatsMajorCurrent Gauge32, 450 ituAlarmActiveStatsMinorCurrent Gauge32, 451 ituAlarmActiveStatsWarningCurrent Gauge32, 452 ituAlarmActiveStatsIndeterminateTotal Counter32, 453 ituAlarmActiveStatsCriticalTotal Counter32, 454 ituAlarmActiveStatsMajorTotal Counter32, 455 ituAlarmActiveStatsMinorTotal Counter32, 456 ituAlarmActiveStatsWarningTotal Counter32 457 } 459 ituAlarmActiveStatsIndeterminateCurrent OBJECT-TYPE 460 SYNTAX Gauge32 461 MAX-ACCESS read-only 462 STATUS current 463 DESCRIPTION 464 "A count of the current number of active alarms with a 465 ituAlarmPerceivedSeverity of indeterminate." 466 ::= { ituAlarmActiveStatsEntry 1 } 468 ituAlarmActiveStatsCriticalCurrent OBJECT-TYPE 469 SYNTAX Gauge32 470 MAX-ACCESS read-only 471 STATUS current 472 DESCRIPTION 473 "A count of the current number of active alarms with a 474 ituAlarmPerceivedSeverity of critical." 475 ::= { ituAlarmActiveStatsEntry 2 } 477 ituAlarmActiveStatsMajorCurrent OBJECT-TYPE 478 SYNTAX Gauge32 479 MAX-ACCESS read-only 480 STATUS current 481 DESCRIPTION 482 "A count of the current number of active alarms with a 483 ituAlarmPerceivedSeverity of major." 484 ::= { ituAlarmActiveStatsEntry 3 } 486 ituAlarmActiveStatsMinorCurrent OBJECT-TYPE 487 SYNTAX Gauge32 488 MAX-ACCESS read-only 489 STATUS current 490 DESCRIPTION 491 "A count of the current number of active alarms with a 492 ituAlarmPerceivedSeverity of minor." 493 ::= { ituAlarmActiveStatsEntry 4 } 495 ituAlarmActiveStatsWarningCurrent OBJECT-TYPE 496 SYNTAX Gauge32 497 MAX-ACCESS read-only 498 STATUS current 499 DESCRIPTION 500 "A count of the current number of active alarms with a 501 ituAlarmPerceivedSeverity of warning." 502 ::= { ituAlarmActiveStatsEntry 5 } 504 ituAlarmActiveStatsIndeterminateTotal OBJECT-TYPE 505 SYNTAX Counter32 506 MAX-ACCESS read-only 507 STATUS current 508 DESCRIPTION 509 "A count of the total number of active alarms with a 510 ituAlarmPerceivedSeverity of indeterminate since system 511 restart." 512 ::= { ituAlarmActiveStatsEntry 6 } 514 ituAlarmActiveStatsCriticalTotal OBJECT-TYPE 515 SYNTAX Counter32 516 MAX-ACCESS read-only 517 STATUS current 518 DESCRIPTION 519 "A count of the total number of active alarms with a 520 ituAlarmPerceivedSeverity of critical since system restart." 521 ::= { ituAlarmActiveStatsEntry 7 } 523 ituAlarmActiveStatsMajorTotal OBJECT-TYPE 524 SYNTAX Counter32 525 MAX-ACCESS read-only 526 STATUS current 527 DESCRIPTION 528 "A count of the total number of active alarms with a 529 ituAlarmPerceivedSeverity of major since system restart." 530 ::= { ituAlarmActiveStatsEntry 8 } 532 ituAlarmActiveStatsMinorTotal OBJECT-TYPE 533 SYNTAX Counter32 534 MAX-ACCESS read-only 535 STATUS current 536 DESCRIPTION 537 "A count of the total number of active alarms with a 538 ituAlarmPerceivedSeverity of minor since system restart." 539 ::= { ituAlarmActiveStatsEntry 9 } 541 ituAlarmActiveStatsWarningTotal OBJECT-TYPE 542 SYNTAX Counter32 543 MAX-ACCESS read-only 544 STATUS current 545 DESCRIPTION 546 "A count of the total number of active alarms with a 547 ituAlarmPerceivedSeverity of warning since system restart." 548 ::= { ituAlarmActiveStatsEntry 10 } 550 -- Conformance 552 ituAlarmConformance OBJECT IDENTIFIER ::= { ituAlarm 2 } 553 ituAlarmCompliances OBJECT IDENTIFIER ::= { ituAlarmConformance 1 } 555 ituAlarmCompliance MODULE-COMPLIANCE 556 STATUS current 557 DESCRIPTION 558 "The compliance statement for systems supporting 559 the ITU Alarm MIB." 560 MODULE -- this module 561 MANDATORY-GROUPS { 562 ituAlarmGroup 563 } 564 ::= { ituAlarmCompliances 1 } 566 ituAlarmGroups OBJECT IDENTIFIER ::= { ituAlarmConformance 2 } 568 ituAlarmGroup OBJECT-GROUP 569 OBJECTS { 570 ituAlarmEventType, 571 ituAlarmProbableCause, 572 ituAlarmPerceivedSeverity 573 } 574 STATUS current 575 DESCRIPTION 576 "ITU alarm details list group." 577 ::= { ituAlarmGroups 1} 579 ituAlarmServiceUserGroup OBJECT-GROUP 580 OBJECTS { 581 ituAlarmAdditionalText, 582 ituAlarmActiveTrendIndication 583 } 584 STATUS current 585 DESCRIPTION 586 "The use of these parameters is a service-user option." 587 ::= { ituAlarmGroups 2 } 589 ituAlarmSecurityGroup OBJECT-GROUP 590 OBJECTS { 591 ituAlarmDetector, 592 ituAlarmServiceProvider, 593 ituAlarmServiceUser 594 } 595 STATUS current 596 DESCRIPTION 597 "Security Alarm Reporting Function as defined in [X.736]" 598 ::= { ituAlarmGroups 3 } 600 ituAlarmStatisticsGroup OBJECT-GROUP 601 OBJECTS { 602 ituAlarmActiveIndetrminateCurrent, 603 ituAlarmActiveCriticalCurrent, 604 ituAlarmActiveMajorCurrent, 605 ituAlarmActiveMinorCurrent, 606 ituAlarmActiveWarningCurrent, 607 ituAlarmActiveIndetrminateTotal, 608 ituAlarmActiveCriticalTotal, 609 ituAlarmActiveMajorTotal, 610 ituAlarmActiveMinorTotal, 611 ituAlarmActiveWarningTotal 612 } 614 STATUS current 615 DESCRIPTION 616 "Itu Active Alarm Statistics." 617 ::= { ituAlarmGroups 4 } 619 END 621 6. Example 623 The following example shows a mapping of linkUp and linkDown traps 624 into the model-neutral MIB [ALARM-MIB] and ITU Alarm MIB. 626 alarmDetailsIndex 3 627 alarmDetailsNotificationId 1.3.6.1.6.3.1.1.5.3 628 alarmDetailsClearNotificationId 1.3.6.1.6.3.1.1.5.4 629 alarmDetailsType raise (3) 630 alarmDetailsModelPointer ituAlarmEntry.3 631 alarmDetailsRowStatus active (1) 632 ituAlarmEventType communicationsAlarm (2) 633 ituAlarmProbableCause cableTamper(61) 634 ituAlarmPerceivedSeverity critical(3) 635 ituAlarmAdditionalText "" 636 ituAlarmDetector 0.0 637 ituAlarmServiceProvider 0.0 638 ituAlarmServiceUser 0.0 640 alarmDetailsIndex 4 641 alarmDetailsNotificationId 1.3.6.1.6.3.1.1.5.4 642 alarmDetailsClearNotificationId 1.3.6.1.6.3.1.1.5.3 643 alarmDetailsType clear (2) 644 alarmDetailsModelPointer ituAlarmEntry.4 645 alarmDetailsRowStatus active (1) 646 ituAlarmEventType communicationsAlarm (2) 647 ituAlarmProbableCause cableTamper(61) 648 ituAlarmPerceivedSeverity cleared(1) 649 ituAlarmAdditionalText "" 650 ituAlarmDetector 0.0 651 ituAlarmServiceProvider 0.0 652 ituAlarmServiceUser 0.0 654 7. Security Considerations 656 There are no management objects defined in this MIB that have a MAX- 657 ACCESS clause of read-write and/or read-create. So, if this MIB is 658 implemented correctly, then there is no risk that an intruder can 659 alter or create any management objects of this MIB via direct SNMP 660 SET operations. 662 The security related managed objects in this MIB are sensitive since 663 they provide information regarding operational condition and quality 664 of server, pertaining to security. 666 It is thus important to control even GET access to these objects and 667 possibly to even encrypt the values of these object when sending them 668 over the network via SNMP. Not all versions of SNMP provide features 669 for such a secure environment 671 SNMPv1 by itself is not a secure environment. Even if the network 672 itself is secure (for example by using IPSec), even then, there is no 673 control as to who on the secure network is allowed to access and 674 GET/SET (read/change/create/delete) the objects in this MIB. 676 It is recommended that the implementers consider the security 677 features as provided by the SNMPv3 framework. Specifically, the use 678 of the User-based Security Model RFC 2574 [RFC2574] and the View- 679 based Access Control Model RFC 2575 [RFC2575] is recommended. 681 It is then a customer/user responsibility to ensure that the SNMP 682 entity giving access to an instance of this MIB, is properly 683 configured to give access to the objects only to those principals 684 (users) that have legitimate rights to indeed GET or SET 685 (change/create/delete) them. 687 8. Authors' Address 689 Sharon Chisholm 690 Nortel Networks 691 PO Box 3511, Station C 692 Ottawa, Ontario, K1Y 4H7 693 Canada 694 Email: schishol@nortelnetworks.com 696 Dan Romascanu 697 Avaya Inc. 698 Atidim Technology Park, Bldg. #3 699 Tel Aviv, 61131 700 Israel 701 Tel: +972-3-645-8414 702 Email: dromasca@avaya.com 704 9. Acknowledgements 706 This document is a product of the DISMAN Working Group. 707 ... 709 10. References 710 [RFC2571] Harrington, D., Presuhn, R., and B. Wijnen, "An 711 Architecture for Describing SNMP Management Frameworks", 712 RFC 2571, April 1999. 714 [RFC1155] Rose, M., and K. McCloghrie, "Structure and Identification 715 of Management Information for TCP/IP-based Internets", STD 716 16, RFC 1155, May 1990. 718 [RFC1212] Rose, M., and K. McCloghrie, "Concise MIB Definitions", 719 STD 16, RFC 1212, March 1991. 721 [RFC1215] M. Rose, "A Convention for Defining Traps for use with the 722 SNMP", RFC 1215, March 1991. 724 [RFC2578] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 725 Rose, M., and S. Waldbusser, "Structure of Management 726 Information Version 2 (SMIv2)", STD 58, RFC 2578, April 727 1999. 729 [RFC2579] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 730 Rose, M., and S. Waldbusser, "Textual Conventions for 731 SMIv2", STD 58, RFC 2579, April 1999. 733 [RFC2580] McCloghrie, K., Perkins, D., Schoenwaelder, J., Case, J., 734 Rose, M., and S. Waldbusser, "Conformance Statements for 735 SMIv2", STD 58, RFC 2580, April 1999. 737 [RFC1157] Case, J., Fedor, M., Schoffstall, M., and J. Davin, 738 "Simple Network Management Protocol", STD 15, RFC 1157, 739 May 1990. 741 [RFC1901] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 742 "Introduction to Community-based SNMPv2", RFC 1901, 743 January 1996. 745 [RFC1906] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 746 "Transport Mappings for Version 2 of the Simple Network 747 Management Protocol (SNMPv2)", RFC 1906, January 1996. 749 [RFC2572] Case, J., Harrington D., Presuhn R., and B. Wijnen, 750 "Message Processing and Dispatching for the Simple Network 751 Management Protocol (SNMP)", RFC 2572, April 1999. 753 [RFC2574] Blumenthal, U., and B. Wijnen, "User-based Security Model 754 (USM) for version 3 of the Simple Network Management 755 Protocol (SNMPv3)", RFC 2574, April 1999. 757 [RFC1905] Case, J., McCloghrie, K., Rose, M., and S. Waldbusser, 758 "Protocol Operations for Version 2 of the Simple Network 759 Management Protocol (SNMPv2)", RFC 1905, January 1996. 761 [RFC2573] Levi, D., Meyer, P., and B. Stewart, "SNMPv3 762 Applications",RFC 2573, April 1999. 764 [RFC2575] Wijnen, B., Presuhn, R., and K. McCloghrie, "View-based 765 Access Control Model (VACM) for the Simple Network 766 Management Protocol (SNMP)", RFC 2575, April 1999. 768 [RFC2570] Case, J., Mundy, R., Partain, D., and B. Stewart, 769 "Introduction to Version 3 of the Internet-standard 770 Network Management Framework", RFC 2570, April 1999. 772 [RFC2274] Blumenthal, U. and B. Wijnen, "User-based Security 773 Model (USM) for version 3 of the Simple Network Management 774 Protocol (SNMPv3)", RFC 2274, January 1998. 776 [RFC2275] Wijnen, B., Presuhn, R. and K. McCloghrie, "View-based 777 Access Control Model (VACM) for the Simple Network 778 Management Protocol (SNMP)", RFC 2275, January 1998. 780 [X.733] ITU Recommendation X.733, "Information Technology - Open 781 Systems Interconnection - System Management: Alarm 782 Reporting Function", 1992 784 [X.736] ITU Recommendation X.736, "Information Technology - Open 785 Systems Interconnection - System Management: Security 786 Alarm Reporting Function", 1992 788 [ALARM-MIB] Chisholm, S., Romascanu, D., "Alarm MIB, 789 Work in Progress 791 11. Full Copyright Statement 793 Copyright (C) The Internet Society (2000). All Rights Reserved. 795 This document and translations of it may be copied and furnished to 796 others, and derivative works that comment on or otherwise explain it 797 or assist in its implementation may be prepared, copied, published and 798 distributed, in whole or in part, without restriction of any kind, 799 provided that the above copyright notice and this paragraph are 800 included on all such copies and derivative works. However, this 801 document itself may not be modified in any way, such as by removing 802 the copyright notice or references to the Internet Society or other 803 Internet organizations, except as needed for the purpose of 804 developing Internet standards in which case the procedures for 805 copyrights defined in the Internet Standards process must be followed, 806 or as required to translate it into languages other than English. 808 The limited permissions granted above are perpetual and will not be 809 revoked by the Internet Society or its successors or assigns. 811 This document and the information contained herein is provided on an 812 "AS IS" basis and THE INTERNET SOCIETY AND THE INTERNET ENGINEERING 813 TASK FORCE DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT 814 NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN 815 WILL NOT INFRINGE ANY RIGHTS OR ANY IMPLIED WARRANTIES OF 816 MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.