Page tree

Versions Compared

Key

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

For Lumeta customers who have expressed interest in sending more More complete device profile data to their can now be exchanged between Cisco Meraki Management Station , Lumeta now provides that capability through an API call. Device information from your Meraki platform to Lumetaand Lumeta Enterprise 3.3.4 and beyond.

How It Works

...

Prerequisites

  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 response. A device is either created or updated in Lumeta based on the information gatheredresponses.

  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"

    Generates

    Device becomes a discovery target and follows the same algorithm as though it were

    and following the same algorithm

    any

    other

    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.

Get Devices from Meraki

To get list of devices managed by Meraki . . .

Enhance Device Data on Lumeta

To enhance/enrich device data on Lumeta from devices returned by Meraki . . .

Enhance Device Details on Lumeta

Record interface information returned by Meraki and display them in Device Details

Retrieve information on :

...


The Results

The responses from Meraki are used to enhance the interface information displayed in Lumeta Device Details, including:

  • 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.

Requirements

  1. Enable the SNMP parameter on your Meraki devices to allow responses to Lumeta queries.
  2. The user generating the API access key must have organizational-level read access.

How To

  1. Log in.
    Image Removed
  • Image Added

Anchor
config
config

...

Configure the Meraki Integration in Lumeta

...

Meraki integration is be configured as follows:

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

  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

    global

    to select all zones. However,

    it is better to create the device in one or only a few zones to  minimize the system overhead necessary

    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.

    Image Modified

  4. Click Submit to save the configuration.  

Meraki CLI

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

  1. system feed list meraki
  2. system feed set meraki enabled [ true | false ] - Enable or Disable the Meraki integration
  3. system feed set meraki pollInterval posInt - Set the polling interval
  4. system feed set meraki key apiKey - Provide the API key to Meraki API
  5. system feed set meraki zone zone [ enable | disable ] - Enable integration for the indicated zone