ACMIB :: timingReasonCode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsACMIBtimingReasonCode

timingReasonCode

Module: ACMIB

OID (symbolic): ACMIB::timingReasonCode

OID (numeric): 1.3.6.1.4.1.1751.2.18.15.14

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: Indicator of type of relationship violated.

What is timingReasonCode?

This read-only integer identifies which type of timing synchronization relationship was violated, such as clock source mismatch or timing loop detection. Engineers monitoring systems with stringent timing requirements (like telecom or financial networks) use this to detect synchronization issues before they cause data corruption. A code might indicate 'primary clock source lost' so you know to failover to the secondary timing reference.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.15.14
snmpwalk -v2c -c public <target> ACMIB::timingReasonCode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.15.14.1
snmpget -v2c -c public <target> ACMIB::timingReasonCode.1

Start monitoring Lucent/Nortel Access Concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ACMIB::timingReasonCode OID value, configure state conditions and alerts, and monitor any Lucent/Nortel Access Concentrator (legacy) from a single console.

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.1751lucentACMIB
1.3.6.1.4.1.1751.2mibsACMIB
1.3.6.1.4.1.1751.2.18acMIBACMIB
1.3.6.1.4.1.1751.2.18.15returnCodeACMIB
1.3.6.1.4.1.1751.2.18.15.14timingReasonCodeACMIB