Network Management

Meraki AP IP address changes do not automatically update for Autonomous AP nodes in the SolarWinds Platform

When a Meraki AP is monitored as a separate SNMP or SNMP+API node, SolarWinds does not automatically update the node IP address after the AP IP changes. This is by design for Autonomous AP nodes. APs monitored in scope of the Meraki Wireless Controller are treated as Thin APs, and their IP addresses are updated automatically from controller data.

First published date

7/7/2026 4:57 PM

Last published date

7/7/2026 4:57 PM

Overview

Meraki APs can be monitored in two different ways:

  • Thin AP: monitored in scope of the Meraki Wireless Controller. The controller supplies the current AP IP address, so the IP is updated automatically.

  • Autonomous AP: added as a separate SNMP-based node. The node uses the configured node address and does not automatically update when the AP IP changes.

If the same AP is monitored both ways, two records can appear for that device: one Thin AP record and one Autonomous AP record.

Product section

Network Performance Monitor

Resolution

Choose the resolution based on the monitoring method to keep.

If you want to keep separate SNMP node monitoring

  • Update the node IP address manually when the AP IP changes.

  • If DNS is available, add or manage the AP by hostname and enable the Dynamic IP Address option.

  • With Dynamic IP Address enabled for a resolvable node, the updated IP can flow to NodesData and later to Wireless_AccessPoints.

If you want automatic IP maintenance

  • Discover the APs as API-only nodes linked to the monitored Meraki controller.

  • API-only nodes are treated as Thin APs, so their IP addresses are maintained automatically from the Meraki controller data.