AV-AES-SERVER-NOTIFICATION-MIB :: avAesMissedHeartbeats

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

All MIBs › AV-AES-SERVER-NOTIFICATION-MIB › avAesMissedHeartbeats

avAesMissedHeartbeats

Module: AV-AES-SERVER-NOTIFICATION-MIB

OID (symbolic): AV-AES-SERVER-NOTIFICATION-MIB::avAesMissedHeartbeats

OID (numeric): 1.3.6.1.4.1.6889.2.27.2.2.1.32

Node type: OBJECT-TYPE

Type: Integer32

Access: read-only

Description: Number of missed heartbeats

What is avAesMissedHeartbeats?

Reports the count of heartbeat signals that were expected but not received by the AES server from a monitored component or peer. A rising count indicates a connectivity or availability problem with the corresponding service.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6889.2.27.2.2.1.32
snmpwalk -v2c -c public <target> AV-AES-SERVER-NOTIFICATION-MIB::avAesMissedHeartbeats

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6889.2.27.2.2.1.32.1
snmpget -v2c -c public <target> AV-AES-SERVER-NOTIFICATION-MIB::avAesMissedHeartbeats.1

Start monitoring Avaya Application Enablement Services (AES) servers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the AV-AES-SERVER-NOTIFICATION-MIB::avAesMissedHeartbeats OID value, configure state conditions and alerts, and monitor any Avaya Application Enablement Services (AES) servers from a single console.

How to Use in IPNetwork Monitor

Select an Avaya Application Enablement Services (AES) server 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 avAesMissedHeartbeats into the Find box to locate it in the OID tree, then select it and click OK. It reports the number of missed heartbeats. 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 an Integer32-type OID, Value bounds is the most useful condition here — trigger an alert if the count changes from its expected baseline, since that would indicate the underlying set of items changed unexpectedly. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (11 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.6889avayaAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2mibsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.27avAESMibsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.27.2avAesMIBAV-APPLICATION-ENABLEMENT-SERVICES-MIB
1.3.6.1.4.1.6889.2.27.2.2avAesNotificationsAV-APPLICATION-ENABLEMENT-SERVICES-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6889.2.27.2.2.1avAesServerTrapMibObjectsAV-AES-SERVER-NOTIFICATION-MIB
1.3.6.1.4.1.6889.2.27.2.2.1.32avAesMissedHeartbeatsAV-AES-SERVER-NOTIFICATION-MIB