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
- Enable the SNMP parameter on your Meraki devices to allow responses to Lumeta queries.
By default, the Meraki devices do not speak native SNMP. Using the Meraki Management console, assign a read-only credential and push it to all devices.
- The user generating the API access key must have organizational-level read access.
- Configure the Meraki integration in Lumeta.
The Lumeta system calls the Meraki API and processes its responses.
Lumeta synthesizes the responses and then either creates or updates a device.
IF the device . . . THEN . . . AND . . . Does not exist on Lumeta Lumeta 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 a target as though it were and following the same algorithm any other device discovered in Lumeta.
Already exists on Lumeta Lumeta 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.
The responses from Meraki are used to enhance the interface information displayed in Lumeta Device Details, including:
- 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.
Configuring the Meraki Integration in Lumeta
Meraki integration is be configured as follows:
Log in to Lumeta as an admin or user with superuser privileges.
On the main menu, browse to Settings > Integrations > Other Solutions > Cisco Meraki.
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 select all zones. However, it is strongly recommended that you select only one or two zones to minimize taxing your system by forcing it to to create or update a found device in multiple zones.
Click Submit to save the configuration.
See Meraki APIs.