LIGO-ATHDRV-STATS-MIB :: ligoAthWatchdogTimeouts

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › LIGO-ATHDRV-STATS-MIB › ligoAthWatchdogTimeouts

ligoAthWatchdogTimeouts

Module: LIGO-ATHDRV-STATS-MIB

OID (symbolic): LIGO-ATHDRV-STATS-MIB::ligoAthWatchdogTimeouts

OID (numeric): 1.3.6.1.4.1.32750.3.7.1.1.1.1

Node type: OBJECT-TYPE

Type: Counter32

Access: read-only

Description: Watchdog timeouts.

What is ligoAthWatchdogTimeouts?

This Counter32, indexed by ifIndex, counts how many times the driver's watchdog timer fired because the radio hardware stopped responding on this radio interface, and like the other counters in this table it only ever increases until the interface or agent resets. Because it reflects a hardware/driver-level fault rather than ordinary traffic, a sudden increase (as opposed to slow, steady growth) is worth alerting on - it typically points to a wedged radio chip, RF calibration trouble, or a driver bug rather than to normal load.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.32750.3.7.1.1.1.1
snmpwalk -v2c -c public <target> LIGO-ATHDRV-STATS-MIB::ligoAthWatchdogTimeouts

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.32750.3.7.1.1.1.1.1
snmpget -v2c -c public <target> LIGO-ATHDRV-STATS-MIB::ligoAthWatchdogTimeouts.1

Start monitoring LigoWave wireless access point/bridge radio (Atheros driver statistics) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the LIGO-ATHDRV-STATS-MIB::ligoAthWatchdogTimeouts OID value, configure state conditions and alerts, and monitor any LigoWave wireless access point/bridge radio (Atheros driver statistics) from a single console.

How to Use in IPNetwork Monitor

Select a LigoWave wireless access point/bridge radio (Atheros driver statistics) 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 ligoAthWatchdogTimeouts 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 watchdog timeouts. 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.32750ligowaveLIGOWAVE-MIB
1.3.6.1.4.1.32750.3ligoMgmtLIGOWAVE-MIB
Numeric OIDNameModule
1.3.6.1.4.1.32750.3.7ligoAthDrvStatsMIBLIGO-ATHDRV-STATS-MIB
1.3.6.1.4.1.32750.3.7.1ligoAthDrvStatsMIBObjectsLIGO-ATHDRV-STATS-MIB
1.3.6.1.4.1.32750.3.7.1.1ligoAthStatsTableLIGO-ATHDRV-STATS-MIB
1.3.6.1.4.1.32750.3.7.1.1.1ligoAthStatsEntryLIGO-ATHDRV-STATS-MIB
1.3.6.1.4.1.32750.3.7.1.1.1.1ligoAthWatchdogTimeoutsLIGO-ATHDRV-STATS-MIB