MERU-CONFIG-AP-MIB :: mwApUpTime

MIB Reference — IPNetwork Monitor · Updated October 02, 2026

All MIBs › MERU-CONFIG-AP-MIB › mwApUpTime

mwApUpTime

Module: MERU-CONFIG-AP-MIB

OID (symbolic): MERU-CONFIG-AP-MIB::mwApUpTime

OID (numeric): 1.3.6.1.4.1.15983.1.1.4.2.1.1.17

Node type: OBJECT-TYPE

Type: TimeTicks

Access: read-only

Description: This object describes Uptime

What is mwApUpTime?

Reports how long this AP has been running since its last restart, in TimeTicks (hundredths of a second); a low value flags a recent reboot worth investigating.

Examples

Walk all instances (SNMPv2c):

snmpwalk -v2c -c public <target> 1.3.6.1.4.1.15983.1.1.4.2.1.1.17
snmpwalk -v2c -c public <target> MERU-CONFIG-AP-MIB::mwApUpTime

Get a specific instance (index 1):

snmpget -v2c -c public <target> 1.3.6.1.4.1.15983.1.1.4.2.1.1.17.1
snmpget -v2c -c public <target> MERU-CONFIG-AP-MIB::mwApUpTime.1

Start monitoring Meru Networks WLAN access point (radio/profile configuration) with a free 30-day trial of IPNetwork Monitor. Create custom SNMP monitor using the MERU-CONFIG-AP-MIB::mwApUpTime OID value, configure state conditions and alerts, and monitor any Meru Networks WLAN access point (radio/profile configuration) from a single console.

How to Use in IPNetwork Monitor

Select a Meru Networks WLAN access point (radio/profile configuration) 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 mwApUpTime 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. This object describes Uptime. 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 TimeTicks-type OID, Value bounds is the most useful condition here — trigger an alert if the value is unexpectedly low (e.g. under 10 minutes), since that indicates a recent, possibly unplanned, reboot or restart. 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.15983meruMERU-SMI
1.3.6.1.4.1.15983.1meru_regMERU-SMI
1.3.6.1.4.1.15983.1.1meru_wlanMERU-SMI
1.3.6.1.4.1.15983.1.1.4mwConfigurationMERU-SMI
Numeric OIDNameModule
1.3.6.1.4.1.15983.1.1.4.2mwConfigApMERU-CONFIG-AP-MIB
1.3.6.1.4.1.15983.1.1.4.2.1mwApTableMERU-CONFIG-AP-MIB
1.3.6.1.4.1.15983.1.1.4.2.1.1mwApEntryMERU-CONFIG-AP-MIB
1.3.6.1.4.1.15983.1.1.4.2.1.1.17mwApUpTimeMERU-CONFIG-AP-MIB