1-- ********************************************************************* 2-- CISCO-OUTAGE-MONITOR-MIB.my: Cisco outage Monitor MIB file 3-- 4-- Dec. 2003 Sejun Song 5-- 6-- Copyright (c) 2002 - 2005 by Cisco Systems, Inc. 7-- All right reserved. 8-- 9-- ********************************************************************* 10 11CISCO-OUTAGE-MONITOR-MIB DEFINITIONS ::= BEGIN 12 13IMPORTS 14 MODULE-IDENTITY, 15 NOTIFICATION-TYPE, 16 OBJECT-TYPE, 17 Unsigned32, 18 Counter32 FROM SNMPv2-SMI 19 InetAddressType, 20 InetAddress FROM INET-ADDRESS-MIB 21 TEXTUAL-CONVENTION, 22 DateAndTime, 23 TruthValue FROM SNMPv2-TC 24 MODULE-COMPLIANCE, 25 OBJECT-GROUP, 26 NOTIFICATION-GROUP FROM SNMPv2-CONF 27 SnmpAdminString FROM SNMP-FRAMEWORK-MIB 28 ciscoMgmt FROM CISCO-SMI; 29 30 31ciscoOutageMIB MODULE-IDENTITY 32 LAST-UPDATED "200508220000Z" 33 ORGANIZATION "Cisco Systems, Inc." 34 CONTACT-INFO "Cisco Systems 35 Customer Service 36 37 Postal: 170 W Tasman Drive 38 San Jose, CA 95134 39 USA 40 41 Tel: +1 800 553-NETS 42 43 E-mail: cs-snmp@cisco.com" 44 DESCRIPTION 45 "This MIB module describes, stores, and reports outage 46 related information generated by individual hardware 47 and software components comprising a router. They includes 48 physical interfaces, logical interfaces, physical 49 entities such as chassis, slots, modules, ports, 50 power supplies, and fan, software processes 51 running on each card, and logical entity, which can be 52 defined by outage monitoring program, 53 which are IOS software for each LC and RP, 54 router device, and CPU utilization. 55 56 The outage related information comprises entity or 57 interface up and down, process start and abnormal 58 or normal termination, unusually high CPU utilization 59 caused, for example, by Denial of Service (DoS) attack, 60 etc. 61 62 The outage related event can be collected by means of 63 Cisco's fault manager, Cisco's event manager, and 64 syslog messages, etc. 65 66 An outage manager maintains the following outage data 67 for each component. 68 69 1) Accumulated Outage Time (AOT): total outage 70 time of a component from the beginning of 71 the measurement. 72 73 2) Number of Accumulated Failure (NAF): total 74 number of failure instance from the 75 beginning of the measurement. 76 77 3) Recording Start Time (RST): the date-time 78 that the measurement process began against the object. 79 80 Using aforementioned outage data, users can calculate 81 and correlate to derive availability information as 82 follows: 83 84 1) Component Availability: the probability 85 that a component will operate when needed. 86 87 = (1 - (Outage Time / Duration)) 88 89 2) DPM (Defects per Million): measure(s) of the 90 defects of the system that have an immediate 91 impact on the end-user. 92 93 = ([AOTi / (Measurement Interval)] x 10**6) 94 95 3) MTTR(Mean Time To Recovery): expected average 96 time to restore a failed component. 97 98 = (AOTi / NAFi) 99 100 4) MTBF (Mean Time Between Failure): expected 101 average time between failures of a component. 102 103 = (T2 - RSTi) / NAFi 104 105 5) MTTF (Mean Time To Failure): the mean time to 106 failure once the device starts working. 107 108 = (MTBFi - MTTRi = (T2 - RSTi - AOTi) / NAFi) 109 110 111 measurement 1 112 |<----------------->| 113 | | 114 System Up @------|-------------------|----> Time 115 RSTi T2 116 117 At the beginning RSTi: 118 119 tmp_AOT = AOTi (from the MIB polling); 120 121 At the end T2: 122 123 Duration = Current Time(T2) - RSTi; 124 Outage Time = AOTj - tmp_AOT; 125 " 126 REVISION "200508220000Z" 127 DESCRIPTION 128 "Added object cOutageRecordingStartTime to cOutageObjectTable. 129 Added logicalEntity(5) to OutageMonObjectType. 130 Added cOutageLntMapping subgroup object." 131 132 REVISION "200209090000Z" 133 DESCRIPTION 134 "Initial version of this MIB." 135 ::= { ciscoMgmt 280 } 136 137 138ciscoOutageMIBObjects OBJECT IDENTIFIER ::= { ciscoOutageMIB 1 } 139 140-- Subgroups 141 142cOutageBasicInfo OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 1 } 143cOutageHistory OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 2 } 144cOutageDescription OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 3 } 145cOutageMonObject OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 4 } 146cOutageCpmMapping OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 5 } 147cOutageRmtMapping OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 6 } 148cOutageLntMapping OBJECT IDENTIFIER ::= { ciscoOutageMIBObjects 7 } 149 150-- Textual Conventions 151 152OutageMonObjectType ::= TEXTUAL-CONVENTION 153 STATUS current 154 DESCRIPTION 155 "Represents different monitored object types: 156 157 interface - this object supports monitoring of both physical 158 and logical interfaces, which is defined in IF-MIB. 159 160 physicalEntity - this object supports monitoring of physical 161 entities contained by the system, including chassis, slots, 162 modules, ports, power supplies, and fan, which is defined 163 in ENTITY-MIB. 164 165 swProcess - this object supports monitoring of software 166 processes, which is defined in CISCO-PROCESS-MIB. 167 168 remoteObject - this object supports monitoring of remote 169 objects including remote customer devices or interfaces. 170 The object is defined by users via CLI configuration. 171 172 logicalEntity - this object supports monitoring of any logical 173 entities contained by the system, including router device, 174 IOS software on each LC or RP, and CPU utilization object, 175 which can be defined by outage monitoring program." 176 177 SYNTAX INTEGER { 178 interface(1), 179 physicalEntity(2), 180 swProcess(3), 181 remoteObject(4), 182 logicalEntity(5) 183 } 184 185 186-- Basic outage information objects 187 188 189cOutageApplVersion OBJECT-TYPE 190 SYNTAX SnmpAdminString 191 MAX-ACCESS read-only 192 STATUS current 193 DESCRIPTION 194 "outage monitoring application version 195 string. 196 197 The format will be: 198 199 'Version.Release.Patch-Level: Textual-Description' 200 201 For example: '1.0.0: Initial Outage Monitor 202 Application'" 203 ::= { cOutageBasicInfo 1 } 204 205 206cOutageNotificationsSent OBJECT-TYPE 207 SYNTAX Counter32 208 UNITS "notifications" 209 MAX-ACCESS read-only 210 STATUS current 211 DESCRIPTION 212 "The number of outage notifications that have been 213 sent. This number may include notifications 214 that were prevented from being transmitted due to 215 reasons such as resource limitations and/or 216 non-connectivity. If one is receiving notifications, 217 one can periodically poll this object to determine if 218 any notifications were missed. If missed, a poll of 219 the cOutageHistoryTable might be necessary." 220 ::= { cOutageBasicInfo 2 } 221 222 223cOutageNotificationsEnabled OBJECT-TYPE 224 SYNTAX TruthValue 225 MAX-ACCESS read-write 226 STATUS current 227 DESCRIPTION 228 "This object indicates whether outage notifications 229 will or will not be sent when an outage related event 230 is generated by the device. Disabling notifications 231 does not prevent outage event from being added 232 to the cOutageHistoryTable." 233 DEFVAL { false } 234 ::= { cOutageBasicInfo 3 } 235 236 237cOutageNotificationFilterEnabled OBJECT-TYPE 238 SYNTAX TruthValue 239 MAX-ACCESS read-write 240 STATUS current 241 DESCRIPTION 242 "This object indicates whether certain outage related 243 event notifications will or will not be sent when the 244 cOutageNotificationsEnabled is TRUE. 245 246 In the event structure, it is possible to have 247 certain hierarchies such that an event causes several 248 related events. The original event is called a root 249 event and other related events are called sub-events. 250 251 If it is enabled, only a root event notification will 252 be sent out and all other related sub-events will be 253 filtered out. The cOutageHistoryTable maintains only 254 the root event. However, it does not prevent the object 255 entries from being updated in the cOutageObjectTable. 256 257 The filtering policy, which correlates a root event and 258 the following sub-events, may vary and can be controlled 259 by the configuration." 260 DEFVAL { false } 261 ::= { cOutageBasicInfo 4 } 262 263 264cOutageFilteredEvents OBJECT-TYPE 265 SYNTAX Counter32 266 MAX-ACCESS read-only 267 STATUS current 268 DESCRIPTION 269 "The number of events which were filtered out. 270 This object can be utilized to determine how 271 many following events got filtered out related 272 to the notified event." 273 ::= { cOutageBasicInfo 5 } 274 275 276-- Outage event history table 277 278 279cOutageHistTableSize OBJECT-TYPE 280 SYNTAX Unsigned32 281 UNITS "entries" 282 MAX-ACCESS read-write 283 STATUS current 284 DESCRIPTION 285 "The upper limit on the number of entries that the 286 cOutageHistoryTable may contain." 287 DEFVAL { 100 } 288 ::= { cOutageHistory 1 } 289 290 291cOutageHistMsgsFlushed OBJECT-TYPE 292 SYNTAX Counter32 293 UNITS "messages" 294 MAX-ACCESS read-only 295 STATUS current 296 DESCRIPTION 297 "The number of entries that have been removed from 298 the cOutageHistoryTable in order to make room for new 299 entries. The value of this object starts at '0' and 300 monotonically increases for each flushed message. 301 If the value of this object is '4294967295', the value 302 will become '0'. This object can be utilized to 303 determine whether your polling frequency on the 304 history table is fast enough and/or the size of your 305 history table is large enough such that you are not 306 missing events." 307 ::= { cOutageHistory 2 } 308 309 310cOutageHistoryTable OBJECT-TYPE 311 SYNTAX SEQUENCE OF COutageHistoryEntry 312 MAX-ACCESS not-accessible 313 STATUS current 314 DESCRIPTION 315 "A table of outage related events generated by this router. 316 Conceptual row entries are dynamically added into this 317 table when outage related events occur. 318 319 Entries are stored in FIFO order. When the maximum number 320 of entries has been reached in the table, the oldest entry 321 in the table is removed immediately. 322 323 When a table is reduced to a smaller size N, the oldest 324 entries are immediately removed from the table leaving 325 a maximum of N entries." 326 ::= { cOutageHistory 3 } 327 328 329cOutageHistoryEntry OBJECT-TYPE 330 SYNTAX COutageHistoryEntry 331 MAX-ACCESS not-accessible 332 STATUS current 333 DESCRIPTION 334 "This entry contains information about an outage related 335 event which has been generated by this router." 336 INDEX {cOutageEventIndex} 337 ::= {cOutageHistoryTable 1} 338 339 340COutageHistoryEntry ::= SEQUENCE { 341 cOutageEventIndex Unsigned32, 342 cOutageEventObjectType OutageMonObjectType, 343 cOutageEventMonObjectIndex Unsigned32, 344 cOutageEventTypeIndex Unsigned32, 345 cOutageEventTime DateAndTime, 346 cOutageEventInterval Unsigned32 347} 348 349cOutageEventIndex OBJECT-TYPE 350 SYNTAX Unsigned32 351 MAX-ACCESS not-accessible 352 STATUS current 353 DESCRIPTION 354 "An arbitrary non-zero integer value that uniquely 355 identifies a COutageHistoryEntry in the table. 356 The value of this table starts at '1' and monotonically 357 increases for each object failure and recovery event 358 received by the agent. If the value of this object is 359 '4294967295', the agent will reset it to '1' upon 360 receiving the next event." 361 ::= { cOutageHistoryEntry 1 } 362 363 364cOutageEventObjectType OBJECT-TYPE 365 SYNTAX OutageMonObjectType 366 MAX-ACCESS read-only 367 STATUS current 368 DESCRIPTION 369 "This object specifies the monitored object's type. 370 It comprises interface(1), physicalEntity(2), 371 swProcess(3), remoteObject(4), and logicalEntity(5). 372 373 The detailed description has been presented above 374 in the OutageMonObjectType definition." 375 ::= { cOutageHistoryEntry 2 } 376 377 378cOutageEventMonObjectIndex OBJECT-TYPE 379 SYNTAX Unsigned32 380 MAX-ACCESS read-only 381 STATUS current 382 DESCRIPTION 383 "This object identifies a specific index of the 384 monitored object based upon the cOutageEventObjectType. 385 If it is interface(1), it correlates the object 386 with ifIndex in ifTable in the IF-MIB. 387 If it is physicalEntity(2), it correlates the object 388 with entPhysicalIndex in entPhysicalTable in the 389 ENTITY-MIB. 390 If it is swProcess(3), the value corresponds to an entry 391 in the cOutageCpmMapTable, which correlates the object 392 with cpmCPUTotalIndex and cpmProcessPID in 393 cpmProcessTable in the CISCO-PROCESS-MIB. 394 If it is remoteObject(4), the value corresponds to an 395 entry in the cOutageRemoteObjMapTable, which correlates the 396 object with its ID and description. 397 If it is logicalEntity(5), the value corresponds to an 398 entry in the cOutageLogicalObjMapTable, which correlates the 399 object with the description. 400 401 It also correlates the event entry with a specific 402 entry in cOutageObjectTable." 403 ::= { cOutageHistoryEntry 3 } 404 405 406cOutageEventTypeIndex OBJECT-TYPE 407 SYNTAX Unsigned32 408 MAX-ACCESS read-only 409 STATUS current 410 DESCRIPTION 411 "The type of outage related event. The value 412 corresponds to an entry in the cOutageEventTypeMapTable." 413 ::= { cOutageHistoryEntry 4 } 414 415 416cOutageEventTime OBJECT-TYPE 417 SYNTAX DateAndTime 418 MAX-ACCESS read-only 419 STATUS current 420 DESCRIPTION 421 "This object specifies the date and time of the 422 event was generated. 423 424 The value of sysUpTime, which is reinitialized during 425 the router boot-up, is not sufficient, since it 426 shall be able to measure the outage time of the 427 router failure over the measurement period." 428 ::= { cOutageHistoryEntry 5 } 429 430 431cOutageEventInterval OBJECT-TYPE 432 SYNTAX Unsigned32 433 MAX-ACCESS read-only 434 STATUS current 435 DESCRIPTION 436 "Object that identifies the time duration between 437 transitions in available state of a component. 438 According to the cOutageEventTypeIndex, If the event type 439 is up, the interval time from the last down time is 440 TTR (Time To Recovery). 441 Otherwise, the interval time from the last up is TTF 442 (Time To Failure)." 443 ::= { cOutageHistoryEntry 6 } 444 445 446-- Event Map Table 447 448 449cOutageEventTypeMapTable OBJECT-TYPE 450 SYNTAX SEQUENCE OF COutageEventTypeMapEntry 451 MAX-ACCESS not-accessible 452 STATUS current 453 DESCRIPTION 454 "A table containing information about 455 cOutageEventTypeMapIndex value mapping. 456 Each conceptual row specifies a unique mapping 457 between a cOutageEventTypeMapIndex value, and an 458 outage related event type." 459 ::= { cOutageDescription 1 } 460 461 462cOutageEventTypeMapEntry OBJECT-TYPE 463 SYNTAX COutageEventTypeMapEntry 464 MAX-ACCESS not-accessible 465 STATUS current 466 DESCRIPTION 467 "A mapping between an event type and an event description." 468 INDEX { cOutageEventTypeMapIndex } 469 ::= { cOutageEventTypeMapTable 1 } 470 471 472COutageEventTypeMapEntry ::= SEQUENCE { 473 cOutageEventTypeMapIndex Unsigned32, 474 cOutageEventTypeName SnmpAdminString, 475 cOutageEventTypeDescrText SnmpAdminString 476} 477 478 479cOutageEventTypeMapIndex OBJECT-TYPE 480 SYNTAX Unsigned32 481 MAX-ACCESS not-accessible 482 STATUS current 483 DESCRIPTION 484 "This object uniquely identifies an event description." 485 ::= { cOutageEventTypeMapEntry 1 } 486 487 488cOutageEventTypeName OBJECT-TYPE 489 SYNTAX SnmpAdminString (SIZE (0..128)) 490 MAX-ACCESS read-only 491 STATUS current 492 DESCRIPTION 493 "The name of the outage related event." 494 ::= { cOutageEventTypeMapEntry 2 } 495 496 497cOutageEventTypeDescrText OBJECT-TYPE 498 SYNTAX SnmpAdminString 499 MAX-ACCESS read-only 500 STATUS current 501 DESCRIPTION 502 "This object specifies a human-readable 503 message describing information about the 504 outage related event." 505 ::= { cOutageEventTypeMapEntry 3 } 506 507 508-- Object Outage 509 510 511cOutageObjectTable OBJECT-TYPE 512 SYNTAX SEQUENCE OF COutageObjectEntry 513 MAX-ACCESS not-accessible 514 STATUS current 515 DESCRIPTION 516 "A table of monitored object entries generated 517 by this router, which include interface, physical 518 entry, and software process. 519 520 The conceptual row entries are initially established 521 during the monitoring start-up procedure based upon 522 configuration set-up. The entries are also dynamically 523 added into this table when a new object is detected. 524 525 The entry information will be updated, when the outage 526 related event occurs. 527 528 The entry will be removed only by configuration reset." 529 ::= { cOutageMonObject 1 } 530 531 532cOutageObjectEntry OBJECT-TYPE 533 SYNTAX COutageObjectEntry 534 MAX-ACCESS not-accessible 535 STATUS current 536 DESCRIPTION 537 "An entry containing outage related information 538 applicable to a particular measurement object." 539 INDEX {cOutageObjectType, cOutageMonitoredObjectIndex} 540 ::= {cOutageObjectTable 1} 541 542 543COutageObjectEntry ::= SEQUENCE { 544 cOutageObjectType OutageMonObjectType, 545 cOutageMonitoredObjectIndex Unsigned32, 546 cOutageCurrentStatus INTEGER, 547 cOutageAOTSinceMeasureStarted Unsigned32, 548 cOutageNAFSinceMeasureStarted Unsigned32, 549 cOutageRecordingStartTime DateAndTime 550} 551 552 553cOutageObjectType OBJECT-TYPE 554 SYNTAX OutageMonObjectType 555 MAX-ACCESS not-accessible 556 STATUS current 557 DESCRIPTION 558 "This object specifies the monitored object's type. 559 It comprises interface(1), physicalEntity(2), 560 swProcess(3), remoteObject(4), and logicalEntity(5). 561 562 The detailed description has been presented above 563 in the OutageMonObjectType definition." 564 ::= { cOutageObjectEntry 1 } 565 566 567cOutageMonitoredObjectIndex OBJECT-TYPE 568 SYNTAX Unsigned32 569 MAX-ACCESS not-accessible 570 STATUS current 571 DESCRIPTION 572 "This object identifies a specific index of the 573 monitored object based upon the cOutageObjectType. 574 If it is interface(1), it correlates the object 575 with ifIndex in ifTable in the IF-MIB. 576 If it is PhysicalEntity(2), it correlates the object 577 with entPhysicalIndex in entPhysicalTable in the 578 ENTITY-MIB. 579 If it is SWProcess(3), the value corresponds to an entry 580 in the cOutageCpmMapTable, which correlates the object 581 with cpmCPUTotalIndex and cpmProcessPID in 582 cpmProcessTable in the CISCO-PROCESS-MIB. 583 If it is remoteObject(4), the value corresponds to an 584 entry in the cOutageRemoteObjMapTable, which correlates the 585 object with its ID and description. 586 If it is logicalEntity(5), the value corresponds to an 587 entry in the cOutageLogicalObjMapTable, which correlates the 588 object with the description." 589 ::= { cOutageObjectEntry 2 } 590 591 592cOutageCurrentStatus OBJECT-TYPE 593 SYNTAX INTEGER { 594 up(1), 595 down(2) 596 } 597 MAX-ACCESS read-only 598 STATUS current 599 DESCRIPTION 600 "The current operational state of the monitored object. 601 The Up(1) state indicates that the monitored object is 602 actively or passively running in the normal condition. 603 The Down(2) state indicates that the monitored object 604 is experiencing some degree of outage." 605 ::= { cOutageObjectEntry 3 } 606 607 608cOutageAOTSinceMeasureStarted OBJECT-TYPE 609 SYNTAX Unsigned32 610 MAX-ACCESS read-only 611 STATUS current 612 DESCRIPTION 613 "The total outage time in second of a component from the 614 beginning of the measurement. The table stores the outage 615 time up to the last recovery event. However, a request 616 comes in during the down status of a component, the report 617 adds the outage time between the last failure to the 618 current." 619 ::= { cOutageObjectEntry 4 } 620 621 622cOutageNAFSinceMeasureStarted OBJECT-TYPE 623 SYNTAX Unsigned32 624 MAX-ACCESS read-only 625 STATUS current 626 DESCRIPTION 627 "The total number of failure instances from the beginning 628 of the measurement. Every failure event of a component 629 adds 1 to this object." 630 ::= { cOutageObjectEntry 5 } 631 632cOutageRecordingStartTime OBJECT-TYPE 633 SYNTAX DateAndTime 634 MAX-ACCESS read-only 635 STATUS current 636 DESCRIPTION 637 "This object specifies the date and time of the 638 object to start outage recording. 639 640 The instance value of this cOutageRecordingStartTime 641 value is initialized to the time when the monitored 642 object is added into this cOutageObjectTable." 643 ::= { cOutageObjectEntry 6 } 644 645 646-- Process Index Map Table 647 648 649cOutageCpmMapTable OBJECT-TYPE 650 SYNTAX SEQUENCE OF COutageCpmMapEntry 651 MAX-ACCESS not-accessible 652 STATUS current 653 DESCRIPTION 654 "A table containing information about 655 cOutageMonitoredObjectIndex value mapping, 656 when the cOutageObjectType is swProcess. 657 Each conceptual row specifies a unique mapping 658 between a cOutageMonitoredObjectIndex value, and 659 cpmCPUTotalIndex and cpmProcessPID in 660 cpmProcessTable in the CISCO-PROCESS-MIB." 661 ::= { cOutageCpmMapping 1 } 662 663 664cOutageCpmMapEntry OBJECT-TYPE 665 SYNTAX COutageCpmMapEntry 666 MAX-ACCESS not-accessible 667 STATUS current 668 DESCRIPTION 669 "A mapping between an object index and a pair of cpm indexes." 670 INDEX { cOutageCpmMapIndex } 671 ::= { cOutageCpmMapTable 1 } 672 673 674COutageCpmMapEntry ::= SEQUENCE { 675 cOutageCpmMapIndex Unsigned32, 676 cOutageCpmCPUTotalIndex Unsigned32, 677 cOutageCpmProcessPID Unsigned32 678} 679 680 681cOutageCpmMapIndex OBJECT-TYPE 682 SYNTAX Unsigned32 683 MAX-ACCESS not-accessible 684 STATUS current 685 DESCRIPTION 686 "This object uniquely identifies cpmCPUTotalIndex and 687 cpmProcessPID in CISCO-PROCESS-MIB. The cpmCPUTotalIndex 688 is used for the cpmCPUTotalTable reference. A pair of 689 { cpmCPUTotalIndex, cpmProcessPID } is used for the 690 cpmProcessTable reference." 691 ::= { cOutageCpmMapEntry 1 } 692 693 694cOutageCpmCPUTotalIndex OBJECT-TYPE 695 SYNTAX Unsigned32 696 MAX-ACCESS read-only 697 STATUS current 698 DESCRIPTION 699 "An index that uniquely represents a CPU in cpmCPUTotalTable 700 in CISCO-PROCESS-MIB." 701 ::= { cOutageCpmMapEntry 2 } 702 703 704cOutageCpmProcessPID OBJECT-TYPE 705 SYNTAX Unsigned32 706 MAX-ACCESS read-only 707 STATUS current 708 DESCRIPTION 709 "This object contains the process ID. It identifies an 710 entry combined with cpmCPUTotalIndex in cpmProcessTable 711 in CISCO-PROCESS-MIB." 712 ::= { cOutageCpmMapEntry 3 } 713 714 715-- Remote Object Map Table 716 717 718cOutageRemoteObjMapTable OBJECT-TYPE 719 SYNTAX SEQUENCE OF COutageRemoteObjMapEntry 720 MAX-ACCESS not-accessible 721 STATUS current 722 DESCRIPTION 723 "A table containing information about 724 cOutageMonitoredObjectIndex value mapping, 725 when the cOutageObjectType is remoteObject. 726 Each conceptual row specifies a unique mapping 727 between a cOutageMonitoredObjectIndex value, and 728 a remote object related information such as the 729 object ID and the object description. 730 Using IP ICMP protocol to monitor the remote object, 731 the object ID can be Network Layer Address, which 732 has been configured by users via configuration file 733 or CLI." 734 ::= { cOutageRmtMapping 1 } 735 736 737cOutageRemoteObjMapEntry OBJECT-TYPE 738 SYNTAX COutageRemoteObjMapEntry 739 MAX-ACCESS not-accessible 740 STATUS current 741 DESCRIPTION 742 "A mapping between a remote object and a remote object 743 description." 744 INDEX { cOutageRemoteObjMapIndex } 745 ::= { cOutageRemoteObjMapTable 1 } 746 747 748COutageRemoteObjMapEntry ::= SEQUENCE { 749 cOutageRemoteObjMapIndex Unsigned32, 750 cOutageRemoteObjIDType InetAddressType, 751 cOutageRemoteObjID InetAddress, 752 cOutageRemoteObjDescrText SnmpAdminString 753} 754 755 756cOutageRemoteObjMapIndex OBJECT-TYPE 757 SYNTAX Unsigned32 758 MAX-ACCESS not-accessible 759 STATUS current 760 DESCRIPTION 761 "This object uniquely identifies a remote object 762 description." 763 ::= { cOutageRemoteObjMapEntry 1 } 764 765 766cOutageRemoteObjIDType OBJECT-TYPE 767 SYNTAX InetAddressType 768 MAX-ACCESS read-only 769 STATUS current 770 DESCRIPTION 771 "Represents the type of address stored in 772 cOutageRemoteObjID." 773 ::= { cOutageRemoteObjMapEntry 2 } 774 775 776cOutageRemoteObjID OBJECT-TYPE 777 SYNTAX InetAddress 778 MAX-ACCESS read-only 779 STATUS current 780 DESCRIPTION 781 "This object represents the Network Layer Address 782 of the remote object, which is configured by 783 users via configuration file or CLI. 784 It could be an IP address or DNS 785 depends on users input." 786 ::= { cOutageRemoteObjMapEntry 3 } 787 788 789cOutageRemoteObjDescrText OBJECT-TYPE 790 SYNTAX SnmpAdminString 791 MAX-ACCESS read-only 792 STATUS current 793 DESCRIPTION 794 "This object specifies a human-readable 795 message describing information about the 796 monitored remote components such as router name 797 or interface name, etc." 798 ::= { cOutageRemoteObjMapEntry 4 } 799 800 801-- Logical Entity Object Map Table 802 803 804cOutageLogicalObjMapTable OBJECT-TYPE 805 SYNTAX SEQUENCE OF COutageLogicalObjMapEntry 806 MAX-ACCESS not-accessible 807 STATUS current 808 DESCRIPTION 809 "A table containing information about 810 cOutageMonitoredObjectIndex value mapping, 811 when the cOutageObjectType is logicalEntity. 812 Each conceptual row specifies a unique mapping 813 between a cOutageMonitoredObjectIndex value, and 814 a logical entity object related information such 815 as the object description." 816 ::= { cOutageLntMapping 1 } 817 818 819cOutageLogicalObjMapEntry OBJECT-TYPE 820 SYNTAX COutageLogicalObjMapEntry 821 MAX-ACCESS not-accessible 822 STATUS current 823 DESCRIPTION 824 "A mapping between a logical entity object and 825 a logical entity object description." 826 INDEX { cOutageLogicalObjMapIndex } 827 ::= { cOutageLogicalObjMapTable 1 } 828 829 830COutageLogicalObjMapEntry ::= SEQUENCE { 831 cOutageLogicalObjMapIndex Unsigned32, 832 cOutageLogicalObjDescrText SnmpAdminString 833} 834 835 836cOutageLogicalObjMapIndex OBJECT-TYPE 837 SYNTAX Unsigned32 838 MAX-ACCESS not-accessible 839 STATUS current 840 DESCRIPTION 841 "This object uniquely identifies a logical entity 842 object description." 843 ::= { cOutageLogicalObjMapEntry 1 } 844 845 846cOutageLogicalObjDescrText OBJECT-TYPE 847 SYNTAX SnmpAdminString 848 MAX-ACCESS read-only 849 STATUS current 850 DESCRIPTION 851 "This object specifies a human-readable 852 message describing a detailed information 853 about the monitored logical entity." 854 ::= { cOutageLogicalObjMapEntry 2 } 855 856 857-- MIB Notification Definitions 858 859 860ciscoOutageMIBNotificationPrefix OBJECT IDENTIFIER ::= 861 { ciscoOutageMIB 2 } 862ciscoOutageMIBNotifications OBJECT IDENTIFIER ::= 863 { ciscoOutageMIBNotificationPrefix 0 } 864 865ciscoOutageEvent NOTIFICATION-TYPE 866 OBJECTS { 867 cOutageEventObjectType, 868 cOutageEventMonObjectIndex, 869 cOutageEventTypeIndex, 870 cOutageEventTime, 871 cOutageEventInterval 872 } 873 STATUS current 874 DESCRIPTION 875 "The agent generates this notification when 876 an outage related event on a monitored object is 877 detected. The sending of this notification can be 878 enabled/disabled via the 879 cOutageNotificationsEnabled object." 880 ::= { ciscoOutageMIBNotifications 1 } 881 882 883-- Conformance Information 884 885 886ciscoOutageMIBConformance OBJECT IDENTIFIER ::= { ciscoOutageMIB 3 } 887ciscoOutageMIBCompliances OBJECT IDENTIFIER ::= 888 { ciscoOutageMIBConformance 1 } 889ciscoOutageMIBGroups OBJECT IDENTIFIER ::= 890 { ciscoOutageMIBConformance 2 } 891 892 893-- Compliance Statements 894 895 896ciscoOutageMIBCompliance MODULE-COMPLIANCE 897 STATUS deprecated 898 DESCRIPTION 899 "The compliance statement for Cisco agents which 900 implement the Cisco Outage MIB. This is 901 deprecated and new compliance 902 ciscoOutageMIBComplianceRev1 is added." 903 MODULE 904 MANDATORY-GROUPS { 905 ciscoOutageBasicGroup, 906 ciscoEventHistoryGroup, 907 ciscoEventDescrGroup, 908 ciscoObjectOutageGroup, 909 ciscoCpmMappingGroup, 910 ciscoRmtMappingGroup, 911 ciscoOutageNotificationsGroup 912 } 913 ::= { ciscoOutageMIBCompliances 1 } 914 915ciscoOutageMIBComplianceRev1 MODULE-COMPLIANCE 916 STATUS current 917 DESCRIPTION 918 "The compliance statement for Cisco agents which 919 implement the Cisco Outage MIB." 920 MODULE 921 MANDATORY-GROUPS { 922 ciscoOutageBasicGroup, 923 ciscoEventHistoryGroup, 924 ciscoEventDescrGroup, 925 ciscoObjectOutageGroupRev, 926 ciscoCpmMappingGroup, 927 ciscoRmtMappingGroup, 928 ciscoLntMappingGroup, 929 ciscoOutageNotificationsGroup 930 } 931 ::= { ciscoOutageMIBCompliances 2 } 932 933 934-- Units of Conformance 935 936 937ciscoOutageBasicGroup OBJECT-GROUP 938 OBJECTS { 939 cOutageApplVersion, 940 cOutageNotificationsSent, 941 cOutageNotificationsEnabled, 942 cOutageNotificationFilterEnabled, 943 cOutageFilteredEvents 944 } 945 STATUS current 946 DESCRIPTION 947 "A collection of managed objects providing basic 948 outage notification and configuration information 949 including notification status and event filtering 950 status." 951 ::= { ciscoOutageMIBGroups 1 } 952 953 954ciscoEventHistoryGroup OBJECT-GROUP 955 OBJECTS { 956 cOutageHistTableSize, 957 cOutageHistMsgsFlushed, 958 cOutageEventObjectType, 959 cOutageEventMonObjectIndex, 960 cOutageEventTypeIndex, 961 cOutageEventTime, 962 cOutageEventInterval 963 } 964 STATUS current 965 DESCRIPTION 966 "A collection of managed objects providing detected 967 outage related event history information." 968 ::= { ciscoOutageMIBGroups 2 } 969 970 971ciscoEventDescrGroup OBJECT-GROUP 972 OBJECTS { 973 cOutageEventTypeName, 974 cOutageEventTypeDescrText 975 } 976 STATUS current 977 DESCRIPTION 978 "A collection of managed objects defining the 979 description of outage related events." 980 ::= { ciscoOutageMIBGroups 3 } 981 982 983ciscoObjectOutageGroup OBJECT-GROUP 984 OBJECTS { 985 cOutageCurrentStatus, 986 cOutageAOTSinceMeasureStarted, 987 cOutageNAFSinceMeasureStarted 988 } 989 STATUS deprecated 990 DESCRIPTION 991 "A collection of managed objects providing 992 accumulated outage data. 993 This group is deprecated in favour of 994 ciscoObjectOutageGroupRev." 995 ::= { ciscoOutageMIBGroups 4 } 996 997 998ciscoCpmMappingGroup OBJECT-GROUP 999 OBJECTS { 1000 cOutageCpmCPUTotalIndex, 1001 cOutageCpmProcessPID 1002 } 1003 STATUS current 1004 DESCRIPTION 1005 "A collection of managed objects defining the 1006 mapping of two cpm indexes." 1007 ::= { ciscoOutageMIBGroups 5 } 1008 1009 1010ciscoRmtMappingGroup OBJECT-GROUP 1011 OBJECTS { 1012 cOutageRemoteObjIDType, 1013 cOutageRemoteObjID, 1014 cOutageRemoteObjDescrText 1015 } 1016 STATUS current 1017 DESCRIPTION 1018 "A collection of managed objects defining the 1019 description of remote objects." 1020 ::= { ciscoOutageMIBGroups 6 } 1021 1022 1023ciscoOutageNotificationsGroup NOTIFICATION-GROUP 1024 NOTIFICATIONS { 1025 ciscoOutageEvent 1026 } 1027 STATUS current 1028 DESCRIPTION 1029 "A collection of notifications." 1030 ::= { ciscoOutageMIBGroups 7 } 1031 1032ciscoObjectOutageGroupRev OBJECT-GROUP 1033 OBJECTS { 1034 cOutageCurrentStatus, 1035 cOutageRecordingStartTime, 1036 cOutageAOTSinceMeasureStarted, 1037 cOutageNAFSinceMeasureStarted 1038 } 1039 STATUS current 1040 DESCRIPTION 1041 "A collection of managed objects providing 1042 accumulated outage data information." 1043 ::= { ciscoOutageMIBGroups 8 } 1044 1045ciscoLntMappingGroup OBJECT-GROUP 1046 OBJECTS { 1047 cOutageLogicalObjDescrText 1048 } 1049 STATUS current 1050 DESCRIPTION 1051 "A managed object defining the 1052 description of logical entity objects." 1053 ::= { ciscoOutageMIBGroups 9 } 1054END 1055