USR-PING-MIB

All MIBs › USR-PING-MIB

Organization: CommWorks

Last Updated: 2001-02-16

Category: CommWorks/3Com Access Equipment

Description: Manages ICMP ping diagnostic operations and round-trip statistics on CommWorks equipment.

Start monitoring vendor-neutral, standards-based MIB, any SNMPv3-capable network device (SNMP engine identity/boot/clock status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

What Is USR-PING-MIB?

USR-PING-MIB is a CommWorks (US Robotics/3Com) enterprise MIB that provides an SNMP-driven interface to trigger and read results from an ICMP ping diagnostic service running on their access equipment. It exposes objects to initiate ping tests toward a target host and to retrieve round-trip time and packet loss statistics from the results. Its monitoring purpose is diagnostic/software-driven network reachability testing rather than continuous device telemetry: an operator uses it to actively test connectivity from the managed device to a remote host and read back latency and loss figures, helping isolate whether a reported connectivity problem lies on the near side, far side, or in between. It conceptually parallels the IETF PING-MIB / DISMAN-PING-MIB structure, though implemented as a CommWorks-specific enterprise extension for their Ping-for-Services process. It is deployed on CommWorks/3Com carrier access equipment where remote diagnostic ping testing is needed without direct CLI access to the device. Network engineers evaluating or troubleshooting this functionality can download the USR-PING-MIB file directly to load it into their MIB browser.

IPNetwork Monitor allows you to monitor SNMP objects defined in USR-PING-MIB. Use the built-in SNMP Monitoring Browser to explore available variables, view their current values and descriptions, and select the objects you want to monitor. You can then create SNMP monitors, configure thresholds, and receive alerts when monitored values change.

Supported Devices

CommWorks/3Com carrier access equipment

Monitoring Examples

No sample object names were provided for this module in the source data; based on its stated purpose, one would expect objects to configure a target address and initiate a ping test, plus result objects for round-trip time and packet loss. An administrator would set a target IP, trigger the test, then poll the result objects to see whether round-trip time is elevated or packets are being lost, helping confirm whether a subscriber connectivity complaint stems from the WAN path beyond the access device.

Imported Objects

From SNMPv2-SMI

Counter32
Integer32
IpAddress
MODULE-IDENTITY
OBJECT-TYPE

From SNMPv2-TC

DisplayString
TruthValue

From USR-DEFINITIONS-MIB

UsrConfigStatus
common	OBJECT-IDENTITY

How to Use in IPNetwork Monitor

Example using usrPingServerNumberPingsSent OID:

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.

OIDs

OID symbolic	OID numeric	Type	Access	Description
usrPing	1.3.6.1.4.1.429.4.36			This MIB Module defines the Commworks enterprise specific interface to the Ping for Services process.
STR usrPingVersion	1.3.6.1.4.1.429.4.36.1	DisplayString	read-only	The current software version of the Ping Process.
STR usrPingConfigFileName	1.3.6.1.4.1.429.4.36.2	DisplayString	read-only	The name of a ConfigFile to read/write permanent database records. If the value of this object is an empty string, then the Ping process uses the default name `@file://PingProcess.cfg'.
USR usrPingCFMStatusFlag	1.3.6.1.4.1.429.4.36.3	UsrConfigStatus	read-write	Setting the value of this object to `save' causes the values of the Ping Group to be written out to the current config file, which is stored in the cfgPingFile object. While the new ConfigFile is being written, the Ping process will set the value of this flag set to `saving''. Any attempts to set the value while it is not `normal' (i.e. the file is currently being written to the ConfigFile) while result in a badValue error being returned. Setting the value to `normal' will result in no action.
T/F usrPingBusyOutEnabled	1.3.6.1.4.1.429.4.36.4	TruthValue	read-write	The variable defines whether the Ping process will continuously ping a list of systems and busy out the modems if those systems do not respond in the specified period of time.
usrPingBusyOutTable	1.3.6.1.4.1.429.4.36.5		not-accessible	A list of systems to ping for connectivity.
usrPingBusyOutEntry	1.3.6.1.4.1.429.4.36.5.1		not-accessible	An entry containing the server info.
STR usrPingSystem	1.3.6.1.4.1.429.4.36.5.1.1	DisplayString	not-accessible	The name or IP address of the system to ping...
INT usrPingServerStatus	1.3.6.1.4.1.429.4.36.5.1.2	INTEGER	read-write	Is this particular server pinged or not?
I32 usrPingFrequency	1.3.6.1.4.1.429.4.36.5.1.3	Integer32	read-write	How many seconds between each ping request.
I32 usrPingMissesAllowed	1.3.6.1.4.1.429.4.36.5.1.4	Integer32	read-write	The number of allowable misses before this system is declared unreachable.
I32 usrPingTimeOut	1.3.6.1.4.1.429.4.36.5.1.5	Integer32	read-write	The number of seconds a ping request can be outstanding before it is declared a miss (failure).
INT usrPingServerReachable	1.3.6.1.4.1.429.4.36.5.1.6	INTEGER	read-only	Do we consider this server connected?
I32 usrPingServerTimeSinceContacted	1.3.6.1.4.1.429.4.36.5.1.7	Integer32	read-only	The number of seconds since this server was contacted.
C32 usrPingServerNumberPingsSentEx	1.3.6.1.4.1.429.4.36.5.1.8	Counter32	read-only	The number of ping requests sent to this server.
C32 usrPingServerPingsReceived	1.3.6.1.4.1.429.4.36.5.1.9	Counter32	read-only	The number of ping responses received from this server.
C32 usrPingServerNumberTimeouts	1.3.6.1.4.1.429.4.36.5.1.10	Counter32	read-only	The number of ping requests sent but not responded to in the specified time.
C32 usrPingServerNumberUnreachable	1.3.6.1.4.1.429.4.36.5.1.11	Counter32	read-only	The number of ICMP responses received that indicate the system was unreachable.
I32 usrPingServerAverageResponseTime	1.3.6.1.4.1.429.4.36.5.1.12	Integer32	read-only	The average response time, in seconds, between ping request and response for this server.
IP usrPingServerAddress	1.3.6.1.4.1.429.4.36.5.1.13	IpAddress	read-only	The translated IP address of this entry
I32 usrPingServerAverageResponseTimeMS	1.3.6.1.4.1.429.4.36.5.1.14	Integer32	read-only	The average response time, in milliseconds, between ping request and response for this server.

RFC description

Ping service process management for network connectivity monitoring on CommWorks equipment.

Start monitoring CommWorks/3Com carrier access equipment (on-demand ping RTT/packet-loss result status) with a free 30-day trial of IPNetwork Monitor. Import MIBs, browse SNMP OIDs, create custom SNMP monitors, configure alerts, and monitor any SNMP-enabled network device from a single console.

Download USR-PING-MIB

What Is USR-PING-MIB?

Supported Devices

Monitoring Examples

This MIB depends on

Related MIBs

How to Use in IPNetwork Monitor

RFC description