Documentation forNetwork Performance Monitor

Understanding Access Point (AP) Status in the SolarWinds Platform

SolarWinds Platform standardizes access point (AP) statuses across a wide range of vendors and technologies, so you can monitor your wireless infrastructure consistently—even when vendors report statuses differently.

How AP status is determined

SolarWinds Platform calculates AP status in two steps:

  1. Generalized AP status: Derived from vendor-specific SNMP or API pollers.

  2. SolarWinds Platform AP status: A standardized status mapped from the generalized status for consistent display and alerting.

AP status may also be affected by the parent node status.

Status mapping

Generalized AP Status SolarWinds Platform AP Status Description
Up (1) Up (1) The AP is online and functioning.
Down (2) Down (2) The AP is unreachable or offline.
Disassociated (3) Warning (3) The AP is in warning state.
Disappeared (4) Unknown (0) The AP is no longer reporting.
Any other value Up (1) Treated as operational by default.

How parent node status affects AP status

The AP’s SolarWinds Platform status may also depend on the status of its parent device:

  • Thin APs (managed by a Wireless LAN Controller): SolarWinds Platform considers the controller’s status when calculating the AP’s status.

  • Autonomous APs (standalone): SolarWinds Platform uses the AP’s own node status.

Parent Node Status SolarWinds Platform AP Status Description
Down (2) Down (2) The parent device is unreachable.
Unmanaged (9) Unmanaged (9) The parent device is excluded from monitoring.
Any other status Based on AP status SolarWinds Platform uses the AP’s own status.

How generalized AP status is calculated

SNMP native pollers

SolarWinds Platform uses vendor-specific SNMP OIDs to determine AP status.

Vendor / Controller OID Used OID Values → Generalized AP Status
Cisco Wireless Controller

bsnAPOperationStatus – .1.3.6.1.4.1.14179.2.2.1.1.6

+

bsnAPAdminStatus – .1.3.6.1.4.1.14179.2.2.1.1.37
  • enable (1) + associated (1) → Up (1)
  • enable (1) + disassociated (2) → Disassociated (3)
  • enable (1) + downloading (3) → Down (2)
  • disable (2) + disassociated → Disassociated (3)
  • disable (2) + any except disassociated → Down (2)
Aruba Wireless Controller wlanAPStatus – .1.3.6.1.4.1.14823.2.2.1.5.2.1.4.1.19
  • up (1) → Up (1)
  • down (2) → Down (2)
HP760 Wireless Controller coDevDisState – .1.3.6.1.4.1.8744.5.23.1.2.1.1.5
  • running (7) → Up (1)
  • Other values → Down (2)
Meru Wireless Controller

mwApOperationalState – .1.3.6.1.4.1.15983.1.1.4.2.1.1.26

+

mwApAvailabilityStatus – .1.3.6.1.4.1.15983.1.1.4.2.1.1.27
  • enabled (1) + online (3) → Up (1)
  • All other combinations → Down (2)
Motorola Wireless Controller wingStatsDevOnline – .1.3.6.1.4.1.388.50.1.4.2.1.1.7
  • 1 → Up (1)
  • Other values → Down (2)
Ruckus Wireless Controller ruckusZDWLANAPStatus – .1.3.6.1.4.1.25053.1.2.2.1.1.2.1.1.3
  • connected (1) → Up (1)
  • Other values → Down (2)
HP420 Autonomous AP RadioEnabled – .1.3.6.1.4.1.11.2.14.11.6.4.1.1.9.1.1.2
  • At least one interface enabled (1) → Up (1)
  • All interfaces disabled (2) → Down (2)
HP Autonomous AP OperStatus – .1.3.6.1.4.1.8744.5.4.3.3.1.2
  • At least one interface up (1) → Up (1)

  • All interfaces down (2) → Down (2)

If the controller no longer reports the AP, its status becomes Disappeared (4).

SNMP Device Studio pollers

SolarWinds Platform supports SNMP-based Device Studio pollers for a variety of wireless LAN controllers (WLCs). These pollers use vendor-specific OIDs to determine the generalized AP status, which is then mapped to SolarWinds Platform status.

Vendor / Controller OID Used OID Values → Generalized AP Status
Huawei Wireless Controller hwWlanApRunState – 1.3.6.1.4.1.2011.6.139.13.3.3.1.6
  • normal (8) → Up (1)
  • other values → Down (2)
HP WX Wireless Controller h3cDot11APOperationStatus – 1.3.6.1.4.1.2011.10.2.75.2.1.1.1.4
  • pure value
Fortinet Wireless Controller fgWcWtpSessionConnectionState – 1.3.6.1.4.1.12356.101.14.4.4.1.7
  • online (2) → Up (1)
  • other values → Down (2)
Samsung Wireless Controller

sweApinfoOpState – 1.3.6.1.4.1.236.4.3.220.3.3.7536930.1.1.4
  • pure value
Netgear WC7520 wcAccessPointRowStatus – 1.3.6.1.4.1.4526.100.8.2.3.1.1.18
  • pure value
Meraki Wireless Controller devStatus – 1.3.6.1.4.1.29671.1.1.4.1.3
  • 1 → Up (1)
  • other values → Down (2)
Juniper / Trapeze Wireless Controller trpzApStatApStatusApState – 1.3.6.1.4.1.14525.4.5.1.1.2.1.5
  • pure value
Aruba Instant Virtual Controller aiAPStatus – 1.3.6.1.4.1.14823.2.3.3.1.2.1.1.11
  • pure value

If the controller no longer reports the AP, its status becomes Disappeared (4).

Autonomous APs

For autonomous APs using Device Studio pollers, the generalized AP status is always set to Up (1).

API pollers

For cloud-managed APs, SolarWinds Platform uses REST API endpoints to determine status. Examples include:

Vendor API Endpoint used to retrieve data API Property API Response → Generalized AP Status
Meraki /organizations/{organizationId}/devices/availabilities status
  • online → Up (1)
  • offline → Down (2)
  • alerting → Disassociated (3)
  • dormant → Disappeared (4)
Aruba Central /monitoring/v2/aps status
  • online → Up (1)
  • other values → Down (2)
AristaWM /manageddevices/aps?fields=boxId&fields=name&fields=active&fields=ipAddress&fields=radios active
  • true → Up (1)
  • false → Down (2)
Juniper Mist /manageddevices/aps?fields=boxId&fields=name&fields=active&fields=ipAddress&fields=radios status
  • connected → Up (1)
  • other values → Down (2)
Ruckus One /venues/aps state
  • operational → Up (1)
  • temporarily degraded → Disassociated (3)
  • other values → Down (2)
Ruckus SZ /${ApiVersion}/query/ap status
  • online → Up (1)
  • other values → Down (2)
FortiEdge Cloud /api/v1/networks/${NetworkID}/fap/access_points/ status
  • connected → Up (1)
  • other values → Down (2)
ExtremeCloudIQ /api/v1/networks/${NetworkID}/fap/access_points/ connected
  • true → Up (1)
  • false → Down (2)

If the API no longer returns the AP, SolarWinds Platform sets the status to Disappeared (4).