USR-PING-MIB :: usrPingServerNumberPingsSent

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › USR-PING-MIB › usrPingServerNumberPingsSent

usrPingServerNumberPingsSent

Module: USR-PING-MIB

OID (symbolic): USR-PING-MIB::usrPingServerNumberPingsSent

OID (numeric): 1.3.6.1.4.1.429.4.36.5.1.8

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The number of ping requests sent to this server.

What is usrPingServerNumberPingsSent?

This read-only Counter32 tallies the total number of ping requests the device has sent to a specific busy-out target. An admin uses it alongside usrPingServerPingsReceived to calculate that target's ping success rate over time. For example, a target showing 1000 pings sent against 950 received indicates roughly a 5 percent loss rate to that system.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.429.4.36.5.1.8
snmpwalk -v2c -c public <target> USR-PING-MIB::usrPingServerNumberPingsSent

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.429.4.36.5.1.8.1
snmpget -v2c -c public <target> USR-PING-MIB::usrPingServerNumberPingsSent.1

Start monitoring CommWorks/3Com carrier access equipment (on-demand ping RTT/packet-loss result status) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the USR-PING-MIB::usrPingServerNumberPingsSent OID value, configure state conditions and alerts, and monitor any CommWorks/3Com carrier access equipment (on-demand ping RTT/packet-loss result status) from a single console.

How to Use in IPNetwork Monitor

Select a CommWorks/3Com carrier access equipment (on-demand ping RTT/packet-loss result status) 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 usrPingServerNumberPingsSent 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 number of ping requests sent to this server. 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 (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.429usrANIC-MIB
1.3.6.1.4.1.429.4commonHDR2-MIB
Numeric OIDNameModule
1.3.6.1.4.1.429.4.36usrPingUSR-PING-MIB
1.3.6.1.4.1.429.4.36.5usrPingBusyOutTableUSR-PING-MIB
1.3.6.1.4.1.429.4.36.5.1usrPingBusyOutEntryUSR-PING-MIB
1.3.6.1.4.1.429.4.36.5.1.8usrPingServerNumberPingsSentUSR-PING-MIB