Archived - Cisco Meraki support

What information does Entuity collect from Meraki devices?

To manage Meraki switches, routers, WAPS and appliances

To manage Meraki WiFi deployments

To add a Meraki CMP

To receive traps from the Meraki Cloud Management Platform

Polling Meraki port information

Entuity offers complete support for the Cisco Meraki cloud-hosted management platform (CMP) and all Cisco Meraki network devices.

What information does Entuity collect from Meraki devices?

Please see the section on the Meraki dashboards in Entuity for further information.

Wireless access points

• name assigned to the access point (AP).
• IP address of the AP.
• MAC address of the AP.
• user-specified location of the AP.
• Meraki AP Mesh Status (e.g. gateway, repeater).
• model number.
• serial number.
• operational status.
• attached host count.
• list of AP interfaces.
• ICMP latency.
• SNMP latency.
• device reachability.

WAP interfaces

• interface name.
• interface speed (manually defined).
• inbound packet rate.
• outbound packet rate.
• inbound traffic.
• outbound traffic.
• inbound utilization % (available if interface speed is defined).
• outbound utilization % (available if interface speed is defined).
• interface status.

CMP

• router, firewall, IDS, IPS, SD-WAN (MX series).
• switches (MS series).
• access points (MR series).
• cameras (MV series).
• phones (MC series).
• endpoint management.
• license information.
  • current status.
  • expiry date.

Devices

• name.
• management MAC
• serial number.
• network ID.
• model.
• 'claimed' date.
• public IP
• status of device to cloud management platfrom connection.
• LAN IPs.
• WAN IPs.
• cellular failover status.
• location (latitude and longitude).
• tags.
• geographic (post address).

Organizations

• name, ID.
• list of VPN peers.
• list of networks.
• breakdown of each Meraki device type.

Networks

• ID.
• name.
• timezone.
• type.
• tags.
• list of VLANs defined for this network.
• list of devices belonging to this network.

VLANs

• name.
• appliance IP.
• subnet.
• fixed IP assignments.
• reserved IP ranges.
• DNS servers.

VPN peers

• name.
• public IP.
• private subnets 

To manage Meraki switches, routers, WAPS and appliances:

In order to manage Meraki switches, routers, WAPs and appliances, you need to do the following:

• Manage the Meraki CMP via its RESTful API.
• Manage the Meraki device (switch, router, WAP or appliance) via SNMP, like any other SNMP-managed device).

Management information comes from a combination of these two data sources, and both are necessary.

You can distribute direct SNMP polling of Meraki devices across multiple Entuity servers. The CMP should only be managed once, via its RESTful API, on any one of your Entuity servers.

It is recommended that you do not duplicate CMP API polling across multiple Entuity servers for the same API key. This is because the API returns information for all organizations, networks and devices for a given API key, and Cisco significantly throttles the throughput of the CMP API.

To add a Meraki CMP:

1. Follow steps 1-3 set out in the section To add a single device to management.
2. In the Device Type field, select Cloud Controller.
3. Enter the Meraki API connection key in the Connection API Key field.
4. In the Connection URL field, you will need to enter the URL that is documented in the Cisco Meraki Dashboard API guide. Typically, this URL will be https://api.meraki.com/api/v0/.
5. Click Add, otherwise click Cancel. Once the cloud management platform is added to the Entuity inventory, data will be retrieved from the platform and stored in a new Cloud Controller database.

To receive traps from the Meraki Cloud Management Platform:

1. For trap receipt to work, you will need to download the MERAKI-CLOUD-CONTROLLER.mib from the Meraki dashboard and add to Entuity, as described in this article.
2. Because the CMP does not send SNMP traps on the usual SNMP UDP port number, you will need to configure the Entuity trap receiver (prologV2) to listen for traps arriving on this additional port. To do this, you will need to enter the following into the root section of the entuity.cfg file:
   
   trapportnum=[]
   
   where its value is a comma-separated list of ports, e.g. trapportnum=162,16200. This list will capture packets from devices that send traps to port 162 and devices that send traps to port 16200 (for Meraki).
3. For traps to be correctly received by Entuity, the Cloud Management Platform must be managed as a Cloud Management Platform, i.e. traps cannot be sent to Entuity from a Meraki Cloud Management Platform which is not under full management.

Polling Meraki port information

From ENA v17.0 P09 and v18.0 P01 upwards, Meraki port information will not be polled by default so as to improves system performance. Instead, you can control logging of RESTful API requests through two config values in the [ccm] section of entuity.cfg:

• ccm.retrievePorts - this is a boolean value that enables or disables port information information gathering.
• ccm.restApiLogInterval - this is an integer value of seconds that represents the interval of time between logging of successful and unsuccessful RESTful API calls during Meraki polling.