Page tree

Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.

More complete device profile data can now be exchanged between Cisco Meraki Management Station and Lumeta Enterprise 3.3.4 and beyond through API calls.

How It Works




  1. The user generating the Meraki Management Station API access key must have organizational-level read access.

The Process

  1. Configure the Meraki integration in Lumeta.

  2. The Lumeta system calls the Meraki API and processes its responses.

  3. Lumeta synthesizes the responses and then either creates or updates a device on Lumeta.

    IF the device . . .THEN . . .AND . . .
    Does not exist on LumetaLumeta records the response with scan type "external" and adds the device to the Lumeta database. A device created by Meraki APIs follows same algorithm for target generation as any other scan type

    Adds the attribute "externalSource" with the value "Meraki Management Station"

    Device becomes a discovery target and follows the same algorithm as though it were any device discovered in Lumeta.

    Already exists on LumetaLumeta retains the device. The response entry on Lumeta includes the Lumeta scan type (e.g., Host Discovery) and "external" for the Meraki scan type. Lumeta Device Details shows both Host and External as the discovery scan type.


  • Network - Including additional L3 switch data
  • Devices - Additional information from Meraki has been added re MX* model security appliances 
  • Interface - Including port information from Meraki
  • Meraki source identifier called out in Lumeta Device Details.
  • Meraki-inflected device fingerprints, identification, and confidence-rankings.

  • Meraki-sourced devices and CIDRs can be added to Lumeta Target List and Lumeta Eligible List.


  • Image Added

Configure the Meraki Integration in Lumeta


  1. Log in to Lumeta as an admin or user with superuser privileges.

  2. On the main menu, browse to Settings > Integrations  > Other Solutions > Cisco Meraki.

  3. Complete the configuration form with a polling interval, API access key. Power on the integration only when you are ready to enable the connection.
    The checkboxes enable you to configure the integration to be zone-specific or to select all zones. However, FireMon strongly recommends that you select only one or two zones to avoid forcing the Lumeta system to create or update a found device in multiple zones.

  4. Click Submit to save the configuration. 

Meraki APIs



Meraki CLI

These commands will enable you to configure the Meraki integration via the Command-Line Interface.