CISCO-OUTAGE-MONITOR-MIB :: cOutageNotificationsSent

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › CISCO-OUTAGE-MONITOR-MIB › cOutageNotificationsSent

cOutageNotificationsSent

Module: CISCO-OUTAGE-MONITOR-MIB

OID (symbolic): CISCO-OUTAGE-MONITOR-MIB::cOutageNotificationsSent

OID (numeric): 1.3.6.1.4.1.9.9.280.1.1.2

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of outage notifications that have been sent. This number may include notifications that were prevented from being transmitted due to reasons such as resource limitations and/or non-connectivity. If one is receiving notifications, one can periodically poll this object to determine if any notifications were missed. If missed, a poll of the cOutageHistoryTable might be necessary.

What is cOutageNotificationsSent?

Read-only counter of outage notifications sent by the device, which may also include attempted notifications that failed to transmit due to resource or connectivity issues; useful for detecting missed notifications by comparing against previously polled values.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.9.9.280.1.1.2
snmpwalk -v2c -c public <target> CISCO-OUTAGE-MONITOR-MIB::cOutageNotificationsSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.9.9.280.1.1.2.1
snmpget -v2c -c public <target> CISCO-OUTAGE-MONITOR-MIB::cOutageNotificationsSent.1

Start monitoring Cisco routing equipment (outage monitoring) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the CISCO-OUTAGE-MONITOR-MIB::cOutageNotificationsSent OID value, configure state conditions and alerts, and monitor any Cisco routing equipment (outage monitoring) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco routing equipment (outage monitoring) as the target host to create a monitor — the SNMP service should be up and running on it. Click New Monitor, then check SNMP Custom on the Favorites tab, click Next, and confirm the host. On the next page, click Select... to open the built-in SNMP MIB Browser and type cOutageNotificationsSent into the Find box to locate it in the OID tree, then select it and click OK. The number of outage notifications that have been sent. On the monitor's Main parameters page you can set the target's SNMP port (default 161), credentials, polling interval, and other settings — see the SNMP Monitor help for details. On the State conditions and Alerting tabs, configure when the monitor should change state and trigger an alert; since this is a Counter32-type OID, Value bounds is the most useful condition here — trigger an alert if the counter increases sharply between polls relative to its normal baseline (in notifications), since an unexpected spike often reflects a real change in traffic or activity. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (8 from the standard OID tree / other modules)
Numeric OIDNameModule
1isoLANART-AGENT
1.3orgAirPair-MIB
1.3.6dodAirPair-MIB
1.3.6.1internetAirPair-MIB
1.3.6.1.4privateAirPair-MIB
1.3.6.1.4.1enterprisesAirPair-MIB
1.3.6.1.4.1.9ciscoCAT2600-MIB
1.3.6.1.4.1.9.9ciscoMgmtCISCO-SMI
Numeric OIDNameModule
1.3.6.1.4.1.9.9.280ciscoOutageMIBCISCO-OUTAGE-MONITOR-MIB
1.3.6.1.4.1.9.9.280.1ciscoOutageMIBObjectsCISCO-OUTAGE-MONITOR-MIB
1.3.6.1.4.1.9.9.280.1.1cOutageBasicInfoCISCO-OUTAGE-MONITOR-MIB
1.3.6.1.4.1.9.9.280.1.1.2cOutageNotificationsSentCISCO-OUTAGE-MONITOR-MIB