ASYNCOS-MAIL-MIB :: raidEvents

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsASYNCOS-MAIL-MIBraidEvents

raidEvents

Module: ASYNCOS-MAIL-MIB

OID (symbolic): ASYNCOS-MAIL-MIB::raidEvents

OID (numeric): 1.3.6.1.4.1.15497.1.1.1.17

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The total number of RAID events that have occurred since the last appliance power on event.

What is raidEvents?

Counts the total number of RAID-related events that have occurred since the appliance was last powered on. An increasing count may indicate disk problems requiring attention.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.15497.1.1.1.17
snmpwalk -v2c -c public <target> ASYNCOS-MAIL-MIB::raidEvents

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.15497.1.1.1.17.1
snmpget -v2c -c public <target> ASYNCOS-MAIL-MIB::raidEvents.1

Start monitoring Cisco IronPort Email Security Appliance (ESA) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ASYNCOS-MAIL-MIB::raidEvents OID value, configure state conditions and alerts, and monitor any Cisco IronPort Email Security Appliance (ESA) from a single console.

How to Use in IPNetwork Monitor

Select a Cisco IronPort Email Security Appliance (ESA) 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 raidEvents into the Find box to locate it in the OID tree, then select it and click OK. The total number of RAID events that have occurred since the last appliance power on event. 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, 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 (9 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.15497ironPortIRONPORT-SMI
1.3.6.1.4.1.15497.1asyncOSAppliancesIRONPORT-SMI
1.3.6.1.4.1.15497.1.1asyncOSMailIRONPORT-SMI
Numeric OIDNameModule
1.3.6.1.4.1.15497.1.1.1asyncOSMailObjectsASYNCOS-MAIL-MIB
1.3.6.1.4.1.15497.1.1.1.17raidEventsASYNCOS-MAIL-MIB