Meraki monitoring - Error messages and troubleshooting tips

'Meraki API' error messages

1. You are trying to access the Dashboard from an unauthorized IP address. Contact your network administrator for more information.

Issue: The above error will be thrown when tried to access the Meraki console's dashboard using an unauthorized IP address.

Cause: This issue occurs when the OpManager IP address is restricted in the Meraki console's dashboard.

Solution: Login to the Meraki console's dashboard and allow OpManager server's IP address to access the dashboard.

2. Invalid API Key

Issue: The given API key is invalid.

Cause:

1. The API key might be regenerated in the Meraki console.
2. The API access to the Meraki controller is not allowed in the Meraki console.

Solution:

1. Update the new API key in Meraki controller device snapshot page in OpManager's UI.
2. Login to the Meraki console and enable the 'Allow API access' option.

Learn more on how to enable API access in Meraki console dashboard.

3. API rate limit exceeded for organization

Issue: The API rate limit has exceeded its maximum value for this organization.

Cause: This error code (429 - rate limit exceeded) is thrown by the Meraki console's dashboard API when a particular Meraki organization exceeds the pre-defined API rate limit. (The limit is 5 requests per second and is not configurable.)

Solution: Try to add the Meraki Organization after few minutes. Make sure the Meraki API requests from OpManager doesn't exceed 5 requests per second. This can be avoided by adding a certain interval between each API call. If the API request is still not processed, contact our support team at opmanager-support@manageengine.com.

4. Other Meraki communication failure messages.

Issue: Any general failure message (device down or not reachable) corresponding to the Meraki Organization that is being monitored.

Cause: This occurs when the response from a Meraki API is NULL. The reason is mostly due to general network issues or any anomalies with the device itself.

Solution: 1. Make sure there is no network connectivity issues between OpManager and the Meraki console. Also, allow api.meraki.com in your firewall server and DNS Server (if DHCP environment). If the issue persists, contact our support team at opmanager-support@manageengine.com.

5. Organization does not exist

Issue: The Meraki organization tried to discover is not available or does not exist.

Cause:

1. Meraki Organization is not mapped with the API key supplied in OpManager.
2. API key is not available or regenerated for that organization in the Meraki console dashboard and you are trying with old API key in OpManager UI.

Solution:

1. Check if the provided API key is available. Also make sure that the API key provided in OpManager is mapped to the desired Organization in the Meraki console
2. Check if the API key is regenerated for that Organization in the Meraki console. If so, try with the new API key. If the issue persists, contact our support team at opmanager-support@manageengine.com.

Meraki - General error messages in OpManager

1. Meraki Radio SSIDs were not displayed properly

Issue: Meraki Radio SSIDs are not displayed properly upon Meraki controller discovery

Cause: Once the Meraki controller is added, the client details will be fetched only after 30 minutes of discovery, and the data will be listed under the SSID tab of the Meraki Radio device.

Solution: Kindly wait 30 minutes for the client details to be updated under the SSID tab of the Meraki Radio device.

2. Organization already exists in OpManager.

Issue: The Meraki organization trying to discover is already available in OpManager.

Cause: This error message is thrown when a Meraki Organization is already added in OpManager or if the same IP address is mapped to an existing device in OpManager.

Solution: Please check if the desired Meraki Organization is already added in OpManager or if the IP address is mapped to any existing device in OpManager Inventory. If the IP is mapped to an existing device, delete that device (if not monitored) and try adding the Meraki organization again. If the issue persists, contact our support team at opmanager-support@manageengine.com.

3. IP Address does not exist

Issue: The IP address of the Meraki Organization entered is not reachable or does not exist.

Cause: This error message is thrown when OpManager is unable to resolve the IP address from the Meraki controller dashboard.

Solution: Make sure that the IP address of the Meraki console dashboard is reachable and resolved from the OpManager server. OpManager resolves IP address from the Meraki console's dashboard url. If the url is reachable from the OPM Installed server, IP Address will be resolved. Try logging in to the Meraki console's dashboard in OpManager installed server. If the issue persists, contact our support team at opmanager-support@manageengine.com.

4. Cannot add device. This edition of OpManager does not support adding more than {n} devices

Issue: Unable to add the device in OpManager as it does not support addition of any more devices.

Cause: You may have run out of your licensed limit for device that can be monitored. Here, {n} indicates the number of devices that has exceeded the device licensing limit.

Solution: Delete or Unmanage a few idle devices to make room for the new ones or please upgrade your license so that OpManager can accommodate more devices. Learn more.

5. Advance Monitoring of Meraki Device failed

Issue: Unable to perform advanced monitoring of Meraki devices from the Meraki controller dashboard.

Cause:

1. Meraki API might have failed to respond.
2. The IP Address might already be available in OpManager.
3. Addition of Meraki device with IP - 0.0.0.0 is restricted.
4. Meraki device license count might have reached its maximum limit. Meraki Security (MX), Meraki Switch (MS) devices will be considered under the device licensing, and Meraki Radio (MR), Meraki Vision (MV), and Meraki Cellular Gateway (MG) will be considered under the Access Point Licensing

Solution: Kindly wait 30 minutes for the client details to be updated under the SSID tab of the Meraki Radio device.