WWP-PING-MIB :: wwpPingFailCause

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › WWP-PING-MIB › wwpPingFailCause

wwpPingFailCause

Module: WWP-PING-MIB

OID (symbolic): WWP-PING-MIB::wwpPingFailCause

OID (numeric): 1.3.6.1.4.1.6141.2.21.1.13

Node type: OBJECT-TYPE

Type: PingFailCause

Access: read-only

Description: The result of the ping.

What is wwpPingFailCause?

This read-only value reports the specific reason the ping test failed, when it did not succeed. An admin checks this to distinguish, for example, an unreachable destination from a request timeout, without having to infer the cause solely from the sent/received packet counts. For example, this object reporting a destination-unreachable style cause would point the admin toward a routing problem rather than simple latency.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6141.2.21.1.13
snmpwalk -v2c -c public <target> WWP-PING-MIB::wwpPingFailCause

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6141.2.21.1.13.1
snmpget -v2c -c public <target> WWP-PING-MIB::wwpPingFailCause.1

Start monitoring World Wide Packets Metro Ethernet switch/router (on-demand ping RTT/loss-result status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the WWP-PING-MIB::wwpPingFailCause OID value, configure state conditions and alerts, and monitor any World Wide Packets Metro Ethernet switch/router (on-demand ping RTT/loss-result status) from a single console.

OID Breakdown

Upper-level ancestors (8 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
1.3.6.1.4.1.6141wwpWWP-SMI
1.3.6.1.4.1.6141.2wwpModulesWWP-SMI
Numeric OIDNameModule
1.3.6.1.4.1.6141.2.21wwpPingMIBWWP-PING-MIB
1.3.6.1.4.1.6141.2.21.1wwpPingMIBObjectsWWP-PING-MIB
1.3.6.1.4.1.6141.2.21.1.13wwpPingFailCauseWWP-PING-MIB