MITEL-APPLICATION-MON-MIB :: mitelApplicationMonFaultOccur

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › MITEL-APPLICATION-MON-MIB › mitelApplicationMonFaultOccur

mitelApplicationMonFaultOccur

Module: MITEL-APPLICATION-MON-MIB

OID (symbolic): MITEL-APPLICATION-MON-MIB::mitelApplicationMonFaultOccur

OID (numeric): 1.3.6.1.4.1.1027.4.11.1.1.4

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The mitelApplicationMonFaultOccur indicates the occurence of the fault since the last system restart

What is mitelApplicationMonFaultOccur?

This read-only Counter32 tracks how many times this fault has occurred since the last system restart. Admins use this to gauge whether a fault is a one-time event or a recurring, chronic problem with a monitored application. For example, this counter reading 15 since the last restart tells an admin a particular application task has crashed and been restarted 15 times, indicating a persistent stability issue.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1027.4.11.1.1.4
snmpwalk -v2c -c public <target> MITEL-APPLICATION-MON-MIB::mitelApplicationMonFaultOccur

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1027.4.11.1.1.4.1
snmpget -v2c -c public <target> MITEL-APPLICATION-MON-MIB::mitelApplicationMonFaultOccur.1

SNMPv3 example:

snmpget -v3 -l authPriv -u snmpv3-user -a SHA -A "AuthPassword1" -x AES -X "PrivPassword1" <target> mitelApplicationMonFaultOccur.1

Start monitoring Mitel IP telephony call server / Ipera1000-based system (application health) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MITEL-APPLICATION-MON-MIB::mitelApplicationMonFaultOccur OID value, configure state conditions and alerts, and monitor any Mitel IP telephony call server / Ipera1000-based system (application health) from a single console.

How to Use in IPNetwork Monitor

Select a Mitel IP telephony call server / Ipera1000-based system (application health) 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 mitelApplicationMonFaultOccur into the Find box to locate it in the OID tree, selecting the specific row/instance you want to monitor since this is a table column, then select it and click OK. The mitelApplicationMonFaultOccur indicates the occurence of the fault since the last system restart. 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 (6 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
Numeric OIDNameModule
1.3.6.1.4.1.1027mitelMITEL-APPLICATION-MON-MIB
1.3.6.1.4.1.1027.4mitelProprietaryMITEL-APPLICATION-MON-MIB
1.3.6.1.4.1.1027.4.11mitelApplicationMonMITEL-APPLICATION-MON-MIB
1.3.6.1.4.1.1027.4.11.1mitelApplicationMonFaultTableMITEL-APPLICATION-MON-MIB
1.3.6.1.4.1.1027.4.11.1.1mitelApplicationMonFaultEntryMITEL-APPLICATION-MON-MIB
1.3.6.1.4.1.1027.4.11.1.1.4mitelApplicationMonFaultOccurMITEL-APPLICATION-MON-MIB