Network Management
Troubleshooting Adding a Meraki Node on an Additional Polling Engine (APE)
You are unable to add a Meraki node on an Additional Polling Engine (APE) in SolarWinds, or the node is added as an ICMP node instead of SNMP.
First published date
Last published date
Overview
Meraki devices require specific configuration to be properly monitored using SNMP on an Additional Polling Engine (APE) within the SolarWinds Platform. By default, if SNMP is not enabled or configured correctly, nodes may be added as ICMP-only, limiting monitoring capabilities. Additionally, network connectivity and firewall rules between the APE and Meraki devices must allow SNMP traffic.
Product section
Cause
The Meraki device is not configured for SNMP polling, or network/firewall settings prevent SNMP communication between the Additional Polling Engine and the Meraki device. Incorrect polling method selection in SolarWinds can also cause the node to be added as ICMP instead of SNMP.
Resolution
-
Enable SNMP on the Meraki Dashboard
- Navigate to Organization > Configure > Settings > SNMP and enable SNMP.
- Configure a community string under Network Wide > Configure > General.
- Reference: Meraki SNMP Overview and Configuration
-
Allow SolarWinds Main Polling Engine IP in Meraki Firewall
- Add the IP address of the SolarWinds Main Polling Engine to the allow list in Meraki’s firewall settings under Security & SD-WAN > Configure > Firewall > WAN appliance services.
Reference: How to add a Meraki device as SNMP since it is added as a ICMP node
- Add the IP address of the SolarWinds Main Polling Engine to the allow list in Meraki’s firewall settings under Security & SD-WAN > Configure > Firewall > WAN appliance services.
-
Add the Node in SolarWinds Using SNMP
- When adding the node, select SNMP as the polling method and enter the correct SNMP credentials (community string or SNMPv3 details).
- If the node is already added as ICMP, change the polling method to SNMP via Settings > Manage Nodes > Edit Properties.
- For detailed steps, see: Add Node Wizard and Change Polling Method
-
Verify Network Connectivity from APE to Meraki Device and Cloud
- Ensure the APE has proper network connectivity to the Meraki device.
- If using API polling, confirm the APE can reach Meraki cloud services.
- Check firewall rules, routing, and DNS resolution as needed.
-
Check Proxy and API Endpoint Configuration
- If your organization uses a regional Meraki API endpoint, verify the MerakiCloudHostname is correctly configured in SolarWinds.
- Review proxy settings to ensure the APE can communicate with the Meraki API endpoints without obstruction.
Meraki API Integration Fails with “Failed to Get List of Organizations” After Upgrading to SolarWinds Platform 2025.2
Additional Recommendations
- Review Logs and Network Traffic
If issues persist after completing the above steps, review SolarWinds logs on the APE and network connectivity logs between the APE and Meraki devices to identify potential causes. - Consider API-Only Polling Option
For Meraki devices, SolarWinds supports API-only polling (appliance, switch, wireless categories) which may be used if SNMP polling is not feasible, though it provides less detailed information.
SNMP or API-based monitoring for Meraki devices