ADTRAN-AOS-NETWORKMONITOR :: adGenAOSnmTestsRun

MIB Reference — IPNetwork Monitor · Updated September 14, 2026

All MIBsADTRAN-AOS-NETWORKMONITORadGenAOSnmTestsRun

adGenAOSnmTestsRun

Module: ADTRAN-AOS-NETWORKMONITOR

OID (symbolic): ADTRAN-AOS-NETWORKMONITOR::adGenAOSnmTestsRun

OID (numeric): 1.3.6.1.4.1.664.5.53.2.2.4.1.3

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Number of test run on the probe.

What is adGenAOSnmTestsRun?

This is a read-only counter of total test executions. Used to validate probe is executing. Example: "3600" means 3600 tests have run since reset.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.664.5.53.2.2.4.1.3
snmpwalk -v2c -c public <target> ADTRAN-AOS-NETWORKMONITOR::adGenAOSnmTestsRun

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.664.5.53.2.2.4.1.3.1
snmpget -v2c -c public <target> ADTRAN-AOS-NETWORKMONITOR::adGenAOSnmTestsRun.1

Start monitoring ADTRAN NetVanta/SDG-series AOS devices with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the ADTRAN-AOS-NETWORKMONITOR::adGenAOSnmTestsRun OID value, configure state conditions and alerts, and monitor any ADTRAN NetVanta/SDG-series AOS devices from a single console.

How to Use in IPNetwork Monitor

Select an ADTRAN NetVanta/SDG-series AOS device 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 adGenAOSnmTestsRun 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. It reports the number of test run on the probe. 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.664adtranADTRAN-ACTDAXL3-MIB
1.3.6.1.4.1.664.5adSharedADTRAN-MIB
1.3.6.1.4.1.664.5.53adGenAOSADTRAN-AOS
1.3.6.1.4.1.664.5.53.2adGenAOSRouterADTRAN-AOS
Numeric OIDNameModule
1.3.6.1.4.1.664.5.53.2.2adGenAOSNetMonADTRAN-AOS-NETWORKMONITOR
1.3.6.1.4.1.664.5.53.2.2.4adGenAOSnmProbeStatusTableADTRAN-AOS-NETWORKMONITOR
1.3.6.1.4.1.664.5.53.2.2.4.1adGenAOSnmProbeStatusEntryADTRAN-AOS-NETWORKMONITOR
1.3.6.1.4.1.664.5.53.2.2.4.1.3adGenAOSnmTestsRunADTRAN-AOS-NETWORKMONITOR