Cisco Meraki Dashboard


Starting from TKU May 2024 imlicit discovery of devices via Cisco Meraki Dashboard API is supported. More info about the Meraki Dasboard can be found here.

Compatibility

Cisco Meraki Dashboard API discovery feature is only supported starting from BMC Discovery 24.2 (14.0).

Prerequisites

  • Valid Meraki Dashboard API credential with API key allowing to request data from managed Meraki Dashboard organizations. See example below.

meraki_add_cred.png

How it works

Devices managed by the Meraki Dashboard are scanned implicitly, Discovery sends API requests againt the API URL (https://api.meraki.com/api/v1 by default, but can be changed in credential).

The following API calls are made during Cisco Meraki Dashboard API discovery.

API Call

API Endpoint

Description

Offical documentation link

Meraki.getManagedDevices 

Internal call, no API endpoint

Main call to get all the managed devices for all organizations.

Under the hood, combination of two calls:

  • Meraki.getOrganizations
  • Meraki.getOrganizationDevices

-

Meraki.getOrganizations

{api_url}/organizations

List the organizations that the user has privileges on

Meraki.getOrganizationDevices

{api_url}/organizations/{organization_id}/devices

List the devices in an organization

Meraki.getDeviceSwitchPortsStatuses

{api_url}/devices/{serial}/switch/ports/statuses

List status for all the ports of a switch. Used to discover Network Interfaces info for switches.

Meraki.getDeviceLldpCdp

{api_url}/devices/{serial}/lldpCdp

To retrieve LLDP and CDP information for all devices other than switches.

Used to discover Network Interfaces info for all devices other than switches.

Note that this API call returns info only for ports with LLDP/CDP enabled.

To run Meraki Dashboard API scan

  • Select Manage > Discovery
  • Click Add New Run, select API > Meraki Dashboard and valid credential from the drop-down menu.

meraki_new_run.png

  • Click OK. If you have configured a snapshot run, you can see it running immediately in the Currently Processing Runs tab. If you have configured a scheduled run, it is listed in the Scheduled Runs tab.
  • As devices scanned implicitly, for each individual device DiscoveryAccess node is created. See below examples of the DiscoveryRun and list of DiscoveryAccesses.

meraki_DR.png

meraki_DA_list.png

  • Example of the Layer 3 Switch Network Device discovered via Meraki Dashboard API in shown in the example below.

meraki_switch.png


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*