IP address of the AP (this is not available when the switch is operating in the Layer 2 mode).

MAC address of the AP.

user-specified location of the AP.

Meraki AP Mesh Status (e.g. gateway, repeater).

AP model number.

AP serial number.

AP Group to which the AP has been associated.

AP operational status.

attached host count.

list of AP interfaces.

AP interfaces

AP interface name.

AP interface full name.

AP 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).

When syslog is enabled on a Meraki Network, syslog can be enabled for several different use cases (e.g. URLs, wireless event log, security events, appliance event logs, flow etc). In order to reduce syslog message volume, Entuity recommends that you only turn on security events and appliance event logs, and turn off syslog flow record messages.

To add a Meraki Wireless Controller:

The Wireless Controller does not listen on the usual SNMP TCP port number (16100 by default, rather than 161). This means you will need to set this TCP port number accordingly when adding the device. The port number can be set on the Wireless Controller settings page.

Because the Wireless Controller does not send SNMP traps on the usual SNMP TCP 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).

IP address of the AP (this is not available when the switch is operating in the Layer 2 mode).

MAC address of the AP.

user-specified location of the AP.

Meraki AP Mesh Status (e.g. gateway, repeater).

AP model number.

AP serial number.

AP Group to which the AP has been associated.

AP operational status.

attached host count.

list of AP interfaces.

AP interfaces

AP interface name.

AP interface full name.

AP 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).

CMP

router, firewall, IDS, IPS, SDWAN (MX series).

switches (MS series).

access points (MR series).

cameras (MV series).

phones (MC series).

endpoint management.

license information.

current status.

expiry date.

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

When syslog is enabled on a Meraki Network, syslog can be enabled for several different use cases (e.g. URLs, wireless event log, security events, appliance event logs, flow etc). In order to reduce syslog message volume, Entuity recommends that you only turn on security events and appliance event logs, and turn off syslog flow record messages.

To manage Meraki switches, routers and firewalls:

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

Manage the Meraki CMP via its RESTful API.

Manage the Meraki device (switch, router or firewall) via SNMP, like any other SNMP-managed device).

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

To manage Meraki WiFi deployments:

In order to manage Meraki WiFi deployments, you need to do the following:

Manage the Meraki CMP as an SNMP-managed device, configured as the "Wireless Controller" device type.

In this case, there is no need to manage the individual wireless access points, because information about these will be polled and displayed in relation to the wireless controller device (just like any other wireless controller device).

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 via RESTful API:

Click Add, otherwise click Cancel. Once the cloud management platform is added to the ENA inventory, data will be retrieved from the platform and stored in a new Cloud Controller database.

To add a Meraki CMP via SNMP as a Wireless Controller device type:

The CMP does not listen on the usual SNMP UDP port number (16100 by default, rather than 161). This means you will need to set this port number accordingly when adding the device. The port number can be set on the Wireless Controller settings page.

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