ALCATEL-IND1-TIMETRA-OAM-TEST-MIB :: tmnxOamPingCtlRuns

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsALCATEL-IND1-TIMETRA-OAM-TEST-MIBtmnxOamPingCtlRuns

tmnxOamPingCtlRuns

Module: ALCATEL-IND1-TIMETRA-OAM-TEST-MIB

OID (symbolic): ALCATEL-IND1-TIMETRA-OAM-TEST-MIB::tmnxOamPingCtlRuns

OID (numeric): 1.3.6.1.4.1.6527.3.1.2.11.1.3.1.29

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: The value of tmnxOamPingCtlRuns indicates the number of times this OAM ping test has been executed.

What is tmnxOamPingCtlRuns?

Reports the total number of times this OAM ping test has been executed since it was created. This read-only counter helps track test activity and frequency.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.11.1.3.1.29
snmpwalk -v2c -c public <target> ALCATEL-IND1-TIMETRA-OAM-TEST-MIB::tmnxOamPingCtlRuns

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.6527.3.1.2.11.1.3.1.29.1
snmpget -v2c -c public <target> ALCATEL-IND1-TIMETRA-OAM-TEST-MIB::tmnxOamPingCtlRuns.1

Start monitoring Nokia (Alcatel-Lucent) 7750 SR-series service routers with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ALCATEL-IND1-TIMETRA-OAM-TEST-MIB::tmnxOamPingCtlRuns OID value, configure state conditions and alerts, and monitor any Nokia (Alcatel-Lucent) 7750 SR-series service routers from a single console.

How to Use in IPNetwork Monitor

Select a Nokia (Alcatel-Lucent) 7750 SR-series service router 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 tmnxOamPingCtlRuns 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 value of tmnxOamPingCtlRuns indicates the number of times this OAM ping test has been executed. 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 (10 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.6527timetraALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3timetraProductsALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1tmnxSRMIBALCATEL-IND1-TIMETRA-GLOBAL-MIB
1.3.6.1.4.1.6527.3.1.2tmnxSRObjsALCATEL-IND1-TIMETRA-GLOBAL-MIB
Numeric OIDNameModule
1.3.6.1.4.1.6527.3.1.2.11tmnxOamTestObjsALCATEL-IND1-TIMETRA-OAM-TEST-MIB
1.3.6.1.4.1.6527.3.1.2.11.1tmnxOamPingObjsALCATEL-IND1-TIMETRA-OAM-TEST-MIB
1.3.6.1.4.1.6527.3.1.2.11.1.3tmnxOamPingCtlTableALCATEL-IND1-TIMETRA-OAM-TEST-MIB
1.3.6.1.4.1.6527.3.1.2.11.1.3.1tmnxOamPingCtlEntryALCATEL-IND1-TIMETRA-OAM-TEST-MIB
1.3.6.1.4.1.6527.3.1.2.11.1.3.1.29tmnxOamPingCtlRunsALCATEL-IND1-TIMETRA-OAM-TEST-MIB