Cisco Meraki

This document provides the steps required to configure the Cisco Meraki Inspector.


Quick Details:

Recommended Agent: On-Demand
Supported Agents: On-Demand, On-Premises, or Self-Hosted
Is Auto-Discovered By: N/A
Can Auto-Discover: Meraki Child Inspectors
Parent/Child Type Inspector: Yes
Inspection via: API
Data Summary: Here


See it in Action

Video isn't playing? Click here.

Inspector Setup Preparation

Step 1: Ensure all Meraki Organizations have been set to enable access to the Dashboard API


Enabling the Meraki Dashboard API

You must enable the Meraki Dashboard API for ALL of your Organizations in Meraki to allow Liongard to query information from those Meraki systems. Liongard will not be able to auto-discover any child account that does not have this checkbox selected.

In Meraki, starting with your own Organization, go to each Organization's Organization > Settings page

  • Navigate to the Dashboard API Access section
  • Ensure that the Enable access to the Cisco Meraki Dashboard API box is checked. If not, check the box and hit Save


Access To Organizations

Please note that the API Key will inherit the permissions of the users who provisioned it. Be sure that the user who provisions the API Key has access to all the organizations you are looking to inspect, otherwise Liongard will not be able to discover the additional organizations.

Step 2: Create a Meraki Dashboard API Key

You will need to create an API Key for the Liongard Inspector. Using the profile hyperlink displayed in the last screenshot from step one will take you to the appropriate page. Be sure to perform this step within your own organization. Documentation to acquire a Key can also be found here: The Cisco Meraki Dashboard API

Liongard Inspector Setup

Step 1: Parent Inspector Setup

Since Meraki is a multi-tenant system where a single portal is used to manage many environments, we will set up a single "Parent" Inspector with the API Key that will then auto-discover "Child" Inspectors for each Environment.

In Liongard, navigate to Admin > Inspectors > Navigate to the Cisco Meraki Inspector > Click Add System.

Fill in the following information:

  • Type of Inspector: Parent
  • Environment: Select your MSP's Environment
  • Friendly Name: Suggested Naming: [MSP Name] Cisco Meraki Parent
  • Agent: Select On-Demand Agent
  • Inspector Version: Latest
  • API Key: Provide the API Key generated from the Meraki User Console
  • Scheduling: The Inspector will default to run once a day at the time the Inspector is set up. Here you can adjust the schedule

Select Save. The Inspector will now be triggered to run within the minute.

Step 2: Child Inspector Setup

After the first run of the Parent Inspector, your client Cisco Meraki organizations will be Auto-Discovered in the Discovered Systems tab on the Inspectors > Cisco Meraki page.

Navigate to the Discovered Systems tab in your Inspectors > Cisco Meraki page

  • Activate or Archive your Discovered Systems by ensuring that they're mapped to the correct Environment > Check the checkbox to the left of Inspector(s) > Select the Actions drop down menu > Activate Launchpoints

Optional: Turn on Flexible Asset/Configuration Auto-Updating

If you would like this Inspector's data to be sent to ConnectWise and/or IT Glue, turn on Flexible Assets/Configurations for this Inspector:

  • ConnectWise: Admin > Integrations > ConnectWise > Configuration Types > Confirm the "Configuration Auto-Updating" toggle is enabled
  • IT Glue: Admin > Integrations > IT Glue > Flexible Assets > Confirm the "Flexible Asset Auto-Updating" toggle is enabled

Inspector FAQs

Did this page help you?