NMS-IPSLA-MIB :: nmsIpslaJobSuccesses

MIB Reference — IPNetwork Monitor · Updated October 06, 2026

All MIBs › NMS-IPSLA-MIB › nmsIpslaJobSuccesses

nmsIpslaJobSuccesses

Module: NMS-IPSLA-MIB

OID (symbolic): NMS-IPSLA-MIB::nmsIpslaJobSuccesses

OID (numeric): 1.3.6.1.4.1.11606.10.9.102.1.1.1.2

Node type: OBJECT-TYPE

Type: INTEGER

Access: read-only

Description: The Ipsla job entry's success times.

What is nmsIpslaJobSuccesses?

This read-only counter reports how many times this IP SLA jitter job has completed successfully. An admin monitors it alongside nmsIpslaJobFailures to gauge the overall reliability of the measured path. For example, a high success count relative to failures confirms the tested path is generally stable, with only occasional jitter test failures.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.11606.10.9.102.1.1.1.2
snmpwalk -v2c -c public <target> NMS-IPSLA-MIB::nmsIpslaJobSuccesses

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.11606.10.9.102.1.1.1.2.1
snmpget -v2c -c public <target> NMS-IPSLA-MIB::nmsIpslaJobSuccesses.1

Start monitoring NMS Communications voice/network gateway (IP SLA echo/jitter probes) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the NMS-IPSLA-MIB::nmsIpslaJobSuccesses OID value, configure state conditions and alerts, and monitor any NMS Communications voice/network gateway (IP SLA echo/jitter probes) from a single console.

How to Use in IPNetwork Monitor

Select an NMS Communications voice/network gateway (IP SLA echo/jitter probes) 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 nmsIpslaJobSuccesses 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 Ipsla job entry's success times. 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 an INTEGER-type OID, Value bounds is the most useful condition here — trigger an alert if the value drifts significantly from its normal baseline, since an unexpected change often points to a real underlying issue. Click Finish to create the monitor; you can adjust any parameter later.

OID Breakdown

Upper-level ancestors (9 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.11606pbnPBN-ROOT
1.3.6.1.4.1.11606.10nmsNMS-SMI
1.3.6.1.4.1.11606.10.9nmsMgmtNMS-SMI
Numeric OIDNameModule
1.3.6.1.4.1.11606.10.9.102nmsIpslaMIBNMS-IPSLA-MIB
1.3.6.1.4.1.11606.10.9.102.1nmsIpslaJitterObjectsNMS-IPSLA-MIB
1.3.6.1.4.1.11606.10.9.102.1.1ipslaJitterTableNMS-IPSLA-MIB
1.3.6.1.4.1.11606.10.9.102.1.1.1nmsIpslaJitterEntryNMS-IPSLA-MIB
1.3.6.1.4.1.11606.10.9.102.1.1.1.2nmsIpslaJobSuccessesNMS-IPSLA-MIB