All MIBs › MITEL-APPLICATION-MON-MIB
Organization: MITEL Networks Corporation
Last Updated: 2003--0-3-
Category: Mitel PBX / Telephony, Voice & Telephony
Description: Monitors MITEL Networks application process health and performance metrics.
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 MITEL-APPLICATION-MON-MIB?
MITEL-APPLICATION-MON-MIB is a Mitel Networks proprietary MIB, part of Mitel's enterprise IP telephony/unified communications product line under the shared "mitel" enterprise registration tree, that monitors the health and performance of Mitel application processes such as call server software. Its object tree is organized under mitelProprietary/mitelIdentification, including identification objects for specific Mitel platforms such as call servers and the Ipera1000 product, indicating it tracks per-application identity alongside runtime monitoring data. This MIB is explicitly aimed at software status monitoring — tracking whether Mitel application processes (e.g., call-processing software) are running correctly, their identification/version, and performance metrics that would reveal degraded call-server behavior. As a Mitel proprietary MIB it depends on Mitel's broader enterprise MIB structure (the shared mitel/mitelProprietary registration subtree used across Mitel products) rather than any IETF standard. It is deployed on Mitel IP telephony call servers and related application servers, such as Ipera1000-based systems, in enterprise unified-communications environments, where MITEL-APPLICATION-MON-MIB SNMP monitoring tracks call-processing software health.
IPNetwork Monitor allows you to monitor SNMP objects defined in MITEL-APPLICATION-MON-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
- Mitel IP telephony call servers
- Mitel Ipera1000-based systems
Monitoring Examples
An administrator would poll objects under the mitelIdentification subtree, such as mitelIdCallServers and the specific mitelIdCsIpera1000 entry, to confirm which Mitel call-server application (and version/platform) is running on a given system. Combined with the application monitoring objects implied by the MIB's purpose, this would reveal whether the Ipera1000 call-processing application is correctly identified and active, helping detect a misconfigured or unresponsive call server before it affects call routing.
What Can Be Monitored
- call server application identity/version
- application process health
- call-processing performance metrics
- software status of Mitel application processes
Imported Objects
From SNMPv2-CONF
| NOTIFICATION-GROUP |
From SNMPv2-SMI
| Counter32 | |
| Integer32 | |
| MODULE-IDENTITY | |
| NOTIFICATION-TYPE | |
| OBJECT-TYPE | |
| enterprises |
From SNMPv2-TC
| DisplayString |
How to Use in IPNetwork Monitor
Example using mitelApplicationMonFaultOccur OID:
OIDs
RFC description
SNMP MIB for monitoring Mitel application platform services and systems, providing management objects for application health, status, and performance monitoring on Mitel devices.
Start monitoring Mitel IP telephony call server / Ipera1000-based system (application health) 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.