CISCO-OUTAGE-MONITOR-MIB

        This MIB module describes, stores, and reports outage 
related information generated by individual hardware 
and software components comprising a router. They includes 
physical interfaces, logical interfaces, physical 
entities such as chassis, slots, modules, ports, 
power supplies, and fan, software processes 
running on each card, and logical entity, which can be 
defined by outage monitoring program,
which are IOS software for each LC and RP,
router device, and CPU utilization. 
        
The outage related information comprises entity or 
interface up and down, process start and abnormal 
or normal termination, unusually high CPU utilization
caused, for example, by Denial of Service (DoS) attack,
etc.
        
The outage related event can be collected by means of 
Cisco's fault manager, Cisco's event manager, and 
syslog messages, etc.
        
An outage manager maintains the following outage data
for each component.
        
    1) Accumulated Outage Time (AOT): total outage 
       time of a component from the beginning of 
       the measurement. 
        
    2) Number of Accumulated Failure (NAF): total 
       number of failure instance from the 
       beginning of the measurement.
        
    3) Recording Start Time (RST): the date-time 
       that the measurement process began against the object. 
             
Using aforementioned outage data, users can calculate 
and correlate to derive availability information as 
follows: 
        
    1) Component Availability: the probability 
       that a component will operate when needed. 
        
       = (1 - (Outage Time / Duration))
        
    2) DPM (Defects per Million): measure(s) of the 
       defects of the system that have an immediate 
       impact on the end-user. 
        
       = ([AOTi / (Measurement Interval)] x 10**6)
        
    3) MTTR(Mean Time To Recovery): expected average 
       time to restore a failed component. 
        
       = (AOTi / NAFi)
        
    4) MTBF (Mean Time Between Failure): expected 
       average time between failures of a component.
        
       = (T2 - RSTi) / NAFi 
        
    5) MTTF (Mean Time To Failure): the mean time to 
       failure once the device starts working.
        
       = (MTBFi - MTTRi = (T2 - RSTi - AOTi) / NAFi)
        
        
                         measurement 1
                     |<----------------->|
                     |                   |
    System Up @------|-------------------|----> Time
                    RSTi                 T2
        
    At the beginning RSTi:
        
	       tmp_AOT = AOTi (from the MIB polling);
        
    At the end T2:
        
       Duration = Current Time(T2) - RSTi;
       Outage Time = AOTj - tmp_AOT;
    
Source file
CISCO-OUTAGE-MONITOR-MIB
Last revised
Identity
ciscoOutageMIB
Base OID
1.3.6.1.4.1.9.9.280
Imported Objects
CISCO-SMI ciscoMgmt
INET-ADDRESS-MIB InetAddress InetAddressType
SNMP-FRAMEWORK-MIB SnmpAdminString
SNMPv2-CONF MODULE-COMPLIANCE (no object page) NOTIFICATION-GROUP (no object page) OBJECT-GROUP (no object page)
SNMPv2-SMI Counter32 MODULE-IDENTITY (no object page) NOTIFICATION-TYPE (no object page) OBJECT-TYPE (no object page) Unsigned32
SNMPv2-TC DateAndTime TEXTUAL-CONVENTION (no object page) TruthValue
Net-SNMP examples using the cisco MIB directory Show commands

These commands use the standard Observium installation path and load the selected MIB variant before the RFC and Net-SNMP directories.

Translate the module identity
/usr/bin/snmptranslate -Pud -Ir -On -m 'CISCO-OUTAGE-MONITOR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'CISCO-OUTAGE-MONITOR-MIB::ciscoOutageMIB'
Walk the MIB subtree
/usr/bin/snmpbulkwalk -v2c -c '<community>' -Pud -Ir -OQUs -m 'CISCO-OUTAGE-MONITOR-MIB' -M '/opt/observium/mibs/cisco:/opt/observium/mibs/rfc:/opt/observium/mibs/net-snmp' 'udp:<hostname>:161' 'CISCO-OUTAGE-MONITOR-MIB::ciscoOutageMIB'
How SNMP, Net-SNMP, MIB paths, and variants work
Objects (57)
.1.3.6.1.4.1.9.9.280
.1.3.6.1.4.1.9.9.280.1
.1.3.6.1.4.1.9.9.280.1.1
.1.3.6.1.4.1.9.9.280.1.1.1
notificationsSNMPv2-SMICounter32
.1.3.6.1.4.1.9.9.280.1.1.2
.1.3.6.1.4.1.9.9.280.1.1.3
.1.3.6.1.4.1.9.9.280.1.1.4
.1.3.6.1.4.1.9.9.280.1.1.5
.1.3.6.1.4.1.9.9.280.1.2
.1.3.6.1.4.1.9.9.280.1.2.1
.1.3.6.1.4.1.9.9.280.1.2.2
.1.3.6.1.4.1.9.9.280.1.2.3
.1.3.6.1.4.1.9.9.280.1.2.3.1
.1.3.6.1.4.1.9.9.280.1.2.3.1.1
.1.3.6.1.4.1.9.9.280.1.2.3.1.2
.1.3.6.1.4.1.9.9.280.1.2.3.1.3
.1.3.6.1.4.1.9.9.280.1.2.3.1.4
.1.3.6.1.4.1.9.9.280.1.2.3.1.5
.1.3.6.1.4.1.9.9.280.1.2.3.1.6
.1.3.6.1.4.1.9.9.280.1.3
.1.3.6.1.4.1.9.9.280.1.3.1
.1.3.6.1.4.1.9.9.280.1.3.1.1
.1.3.6.1.4.1.9.9.280.1.3.1.1.1
OctetString
.1.3.6.1.4.1.9.9.280.1.3.1.1.2
.1.3.6.1.4.1.9.9.280.1.3.1.1.3
.1.3.6.1.4.1.9.9.280.1.4
.1.3.6.1.4.1.9.9.280.1.4.1
.1.3.6.1.4.1.9.9.280.1.4.1.1
.1.3.6.1.4.1.9.9.280.1.4.1.1.1
.1.3.6.1.4.1.9.9.280.1.4.1.1.2
Enumeration
.1.3.6.1.4.1.9.9.280.1.4.1.1.3
.1.3.6.1.4.1.9.9.280.1.4.1.1.4
.1.3.6.1.4.1.9.9.280.1.4.1.1.5
.1.3.6.1.4.1.9.9.280.1.4.1.1.6
.1.3.6.1.4.1.9.9.280.1.5
.1.3.6.1.4.1.9.9.280.1.5.1
.1.3.6.1.4.1.9.9.280.1.5.1.1
.1.3.6.1.4.1.9.9.280.1.5.1.1.1
.1.3.6.1.4.1.9.9.280.1.5.1.1.2
.1.3.6.1.4.1.9.9.280.1.5.1.1.3
.1.3.6.1.4.1.9.9.280.1.6
.1.3.6.1.4.1.9.9.280.1.6.1
.1.3.6.1.4.1.9.9.280.1.6.1.1
.1.3.6.1.4.1.9.9.280.1.6.1.1.1
.1.3.6.1.4.1.9.9.280.1.6.1.1.2
.1.3.6.1.4.1.9.9.280.1.6.1.1.3
.1.3.6.1.4.1.9.9.280.1.6.1.1.4
.1.3.6.1.4.1.9.9.280.1.7
.1.3.6.1.4.1.9.9.280.1.7.1
.1.3.6.1.4.1.9.9.280.1.7.1.1
.1.3.6.1.4.1.9.9.280.1.7.1.1.1
.1.3.6.1.4.1.9.9.280.1.7.1.1.2
.1.3.6.1.4.1.9.9.280.2
.1.3.6.1.4.1.9.9.280.2.0
.1.3.6.1.4.1.9.9.280.3
.1.3.6.1.4.1.9.9.280.3.1
.1.3.6.1.4.1.9.9.280.3.2
Dependencies (6) 6 direct Show tree and compile order Hide dependency details

Each imported module is resolved in the importing module's source directory first, then through the normal default-variant rules.

Dependency tree
Dependency-first compile order
  1. SNMPv2-SMIrfc
  2. CISCO-SMIcisco
  3. SNMPv2-TCrfc
  4. INET-ADDRESS-MIBrfc
  5. SNMPv2-CONFrfc
  6. SNMP-FRAMEWORK-MIBrfc
  7. CISCO-OUTAGE-MONITOR-MIBciscoselected
Type Definitions (1)
Enumeration
interface(1)
physicalEntity(2)
swProcess(3)
remoteObject(4)
logicalEntity(5)
Conformance Groups (9)
A collection of managed objects providing basic
outage notification and configuration information
including notification status and event filtering
status.
.1.3.6.1.4.1.9.9.280.3.2.1
A collection of managed objects providing detected
outage related event history information.
.1.3.6.1.4.1.9.9.280.3.2.2
A collection of managed objects defining the
description of outage related events.
.1.3.6.1.4.1.9.9.280.3.2.3
A collection of managed objects providing
accumulated outage data.
This group is deprecated in favour of
ciscoObjectOutageGroupRev.
.1.3.6.1.4.1.9.9.280.3.2.4
A collection of managed objects defining the
mapping of two cpm indexes.
.1.3.6.1.4.1.9.9.280.3.2.5
A collection of managed objects defining the
description of remote objects.
.1.3.6.1.4.1.9.9.280.3.2.6
A collection of notifications.
.1.3.6.1.4.1.9.9.280.3.2.7
A collection of managed objects providing
accumulated outage data information.
.1.3.6.1.4.1.9.9.280.3.2.8
A managed object defining the
description of logical entity objects.
.1.3.6.1.4.1.9.9.280.3.2.9
Compliance Statements (2)

OID .1.3.6.1.4.1.9.9.280.3.1.1
The compliance statement for Cisco agents which
implement the Cisco Outage MIB. This is
deprecated and new compliance
ciscoOutageMIBComplianceRev1 is added.
Required groups

OID .1.3.6.1.4.1.9.9.280.3.1.2
The compliance statement for Cisco agents which
implement the Cisco Outage MIB.
Required groups
Notifications / Traps (1)
NameOIDDescription
.1.3.6.1.4.1.9.9.280.2.0.1
The agent generates this notification when
an outage related event on a monitored object is
detected. The sending of this notification can be
enabled/disabled via the
cOutageNotificationsEnabled object.