FireMon Asset Manager
Page tree

Versions Compared

Old Version 27

changes.mady.by.user user-05670

Saved on

compared with

New Version Current

changes.mady.by.user Dong Pak

Saved on

Key

  • 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 Asset Manager 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 LumetaAsset Manager.

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

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

    IF the device . . .THEN . . .AND . . .
    Does not exist on LumetaAsset ManagerLumeta Asset Manager records the response with scan type "external" and adds the device to the Lumeta Asset Manager database.

    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 LumetaAsset Manager.

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


The Results

The responses from Meraki are used to enhance the interface information displayed in Lumeta Asset Manager 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 Asset Manager Device Details.

  • Meraki-inflected device fingerprints, identification, and confidence-rankings.

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

...

  • Image Added

...

Configure the Meraki Integration in

...

Asset Manager

Meraki integration is be configured as follows:

  1. Log in to Lumeta Asset Manager 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 Asset Manager system to create or update a found device in multiple zones.

  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

...