AV-AES-SERVER-NOTIFICATION-MIB

MIB Reference — IPNetwork Monitor · Updated October 05, 2026

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

Organization: Avaya Inc.

Last Updated: 2013-05-29

Category: Telephony and VoIP, Vendor: Avaya

Description: Defines SNMP notifications for Avaya Application Enablement Services (AES) server events and service state changes.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is AV-AES-SERVER-NOTIFICATION-MIB?

AV-AES-SERVER-NOTIFICATION-MIB defines SNMP traps and supporting objects for Avaya Application Enablement Services (AES), a middleware server bridging PBX/switch telephony (CTI) with enterprise applications. The module's data centers on system maintenance and alarm events: alarm type/severity, switch connection identity, service names, and CTI (Computer Telephony Integration) link status. It is explicitly built to support monitoring of software/service health on the AES server — flagging when a CTI link goes down, when a service state changes, or when a client application's session or login fails, effectively serving as a fault/status monitoring feed rather than a performance-counter MIB. It has an implicit dependency on the standard SNMP notification framework (NOTIFICATION-TYPE conventions) and is tied to the Avaya enterprise OID tree. It is typically deployed in enterprise contact-center and unified-communications environments where AES mediates between an Avaya Communication Manager switch and CTI applications, and AV-AES-SERVER-NOTIFICATION-MIB SNMP monitoring gives operators early warning of CTI link and service-state failures.

IPNetwork Monitor allows you to monitor SNMP objects defined in AV-AES-SERVER-NOTIFICATION-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

  • Avaya Application Enablement Services (AES) server

Monitoring Examples

An admin would subscribe to traps carrying avAesAlarmType and avAesEvtSrvReason to be alerted when a CTI link (identified by avAesCtiLinkNum) transitions its avAesCtiLinkStatus to down, indicating a lost connection between the AES server and the switch (avAesSwitchName / avAesSwConnIPAddress). Objects like avAesClientLogin, avAesClientIPAddress, and avAesApiName let an operator see which CTI client application triggered a service event tied to avAesServiceName. This supports troubleshooting scenarios such as a call-center application losing its telephony integration path.

What Can Be Monitored

  • CTI link status
  • alarm type and severity
  • switch connection state
  • client application login/session status
  • service name and state
  • API session identity
Imported Objects

From AV-APPLICATION-ENABLEMENT-SERVICES-MIB

avAESMibsOBJECT-IDENTITY
avAesNotificationCompliancesOBJECT-IDENTITY
avAesNotificationGroupsOBJECT-IDENTITY
avAesNotificationsOBJECT-IDENTITY

From AV-CORE-SERVICES-MIB

csAlarmSeverityOBJECT-TYPE

From ENTITY-MIB

entPhysicalAssetIDOBJECT-TYPE

From INET-ADDRESS-MIB

InetAddress
InetAddressType

From ITU-ALARM-TC-MIB

ItuPerceivedSeverity

From SNMPv2-CONF

MODULE-COMPLIANCE
NOTIFICATION-GROUP
OBJECT-GROUP

From SNMPv2-MIB

sysNameOBJECT-TYPE
sysObjectIDOBJECT-TYPE

From SNMPv2-SMI

Integer32
IpAddress
MODULE-IDENTITY
NOTIFICATION-TYPE
OBJECT-TYPE

From SNMPv2-TC

TEXTUAL-CONVENTION

How to Use in IPNetwork Monitor

Example using avAesMissedHeartbeats OID:

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.
OIDs

RFC description

Provides SNMP traps and alarms for Avaya Application Enablement Services (AES) Server for system maintenance and event notifications.

Start monitoring Avaya Application Enablement Services (AES) servers with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download AV-AES-SERVER-NOTIFICATION-MIB