ACMIB :: pingStatusReasonCode

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsACMIBpingStatusReasonCode

pingStatusReasonCode

Module: ACMIB

OID (symbolic): ACMIB::pingStatusReasonCode

OID (numeric): 1.3.6.1.4.1.1751.2.18.15.42

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The response value - Alive destination can be reached Not Alive destination can't be reached

What is pingStatusReasonCode?

This OID reports the result of the most recent ping operation, indicating whether the target host is Alive (reachable) or Not Alive (unreachable). Network engineers use this to quickly verify end-to-end network connectivity and identify routing or link problems. For example, a status of 'Alive' confirms the target host responded to the ping and the network path is operational.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.15.42
snmpwalk -v2c -c public <target> ACMIB::pingStatusReasonCode

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.1751.2.18.15.42.1
snmpget -v2c -c public <target> ACMIB::pingStatusReasonCode.1

Start monitoring Lucent/Nortel Access Concentrator (legacy) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ACMIB::pingStatusReasonCode 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.42pingStatusReasonCodeACMIB