Support for Cisco Meraki

Support for Cisco Meraki
casp1041
Virtual Network Assurance and
CA Spectrum
10.3.2 (or higher) support modeling of Cisco Meraki devices (Cloud Controller and Access Points) and proactive monitoring and managing of wireless networks. The monitoring information is provided by VNA, whereas,
DX NetOps Spectrum
relies on the inventory data from VNA to monitor and manage Meraki devices. The Access Points are modeled as certified SNMP devices, if they are SNMP- reachable, if not, then they are modeled as Access Point pingable models. To model the Access Points using SNMP, ensure the SNMP community string of the access points is added under the following:
  • VNM→AutoDiscovery
  • Control→Modeling
  • Protocol Options-→SNMP Community Strings
Discovering connections between controller, switches and access points is based on the SNMP data available on the corresponding models, without which
DX NetOps Spectrum
cannot create any connections, and VNA cannot provide this connectivity information.
Properties of Cloud Controller and Access Points are displayed under the OneClick information tab. The operation status of Cloud Controller and Access Points is monitored based on the VNA inventory updates. Access Point availability is monitored through
DX NetOps Spectrum
and VNA inventory updates. If Access Point is unreachable from
DX NetOps Spectrum
(by Poll/Ping) and from VNA (OperationStatus is down), then a device unreachable alarm is asserted on the AP model.
Meraki Cloud controller dashboard exposes APIs to monitor its elements (Cloud Controller, Access Points, Service Appliances, Switches, Routers, and so on). VNA uses APIs to get monitoring data of
DX NetOps Spectrum
Controller and Access Points.
DX NetOps Spectrum
is integrated with VNA (using a Meraki plugin) that consume inventory information from VNA to model Meraki devices in the SDN/VNA manager hierarchy.
Following are the entities which are newly supported for Meraki under VNA
:
  • POLICY
  • POLICY_GROUP
  • SSID
  • WIFI_CONTROLLER
  • WIRELESS_NETWORK
  • ACCESS_POINT
  • MX_ROUTER
These entities are modeled in
DX NetOps Spectrum
with special model types. Meraki Cloud Controller is auto-modeled as a Wifi_Controller, which is a virtual entity.
The Cloud Controller properties are displayed under OneClick view, which contains:
  • General Information, displaying the serial number, MAC, IP address, uptime, system name, location, condition/contact status, etc.
  • Wireless Information, displaying the Access Points hardware details.
The Access Point properties that are displayed under the OneClick view are:
  • General
  • Asset Information
Hierarchy and Icons
Following is the hierarchy and icons that are supported with this release:
Organizations>Wireless Networks>Access Points, Appliances (MX Routers), and SSIDs
Cisco Meraki icon heirarchy
Organization
A collection of networks that are all part of a single organizational entity.
Organization Meraki.JPG
Access Points
Access points provide deep network insight enabling smarter network management.
Access points meraki.JPG
MX Router
MX Routers provide powerful routing, switching, security, and services features.
MX_Router
SSIDs
Service Set Identifier (SSID) is a unique identifier that is applied to the Access Point (AP) and the wireless client, allowing them to associate.
SSIDs.JPG
Cloud Controller
Cloud Controller is the control framework that allows various Cisco Meraki products to work together seamlessly, including indoor and outdoor wireless access points, switches, security appliances.
Cloud Controller icon Meraki.JPG
Events and Alarm
Events and alarms are raised on Meraki entities using the data that is provided by VNA. Following is the list of Events and Alarms identified:
MX Routers
Event Type
Description
Alarm Severity
events     
VPN connectivity change 
minor VPN_Connectivity=false
events   
VPN connectivity change
Clear VPN_Connectivity=false
events   
uplink connectivity change
critical Cellular Connection Down
events
uplink connectivity change
Major
events
uplink connectivity change
Major
events
uplink connectivity change
Clear Cellular Connection Down
events
client DHCP lease
NA
ids-alerts
ids signature matched
NA
ids-alerts
ids signature matched
NA
security_event ids_alerted
ids signature matched
NA
security_event security_filtering_file_scanned
Malicious file blocked by amp
Minor action="block"
security_event security_filtering_disposition_change
File issued retrospective malicious disposition
Clear Minor action="block"
Meraki Dashboard API
The CA Virtual Network Assurance polls the Meraki Dashboard API. The following REST API returns mappings of above
DX NetOps Spectrum
alarm model fields to incident fields:
URL
GET /networks/{networkId}/devices/   {serial}/uplink
Response
[ { "interface": "WAN 1", "status": "Active", "ip": "1.2.3.4", "gateway": "1.2.3.5", "publicIp": "123.123.123.1", "dns": "8.8.8.8, 8.8.4.4", "usingStaticIp": false } ]
In case the status of the uplink interface is down, the Virtual Network Assurance sends an update to
DX NetOps Spectrum
. Once
DX NetOps Spectrum
receives an update, it raises an alarm.
Meraki Interface Alarm
Access Points
Event Type
Event Description
Alarms
events     
802.11 association
N/A
events   
802.11 disassociation
N/A
events   
WPA authentication
N/A
events   
WPA deauthentication  
N/A
events   
WPA failed authentication attempt
N/A
events   
802.1x failed authentication attempt
N/A
events   
802.1x deauthentication
N/A
events   
802.1x authentication  
N/A
events   
splash authentication 
N/A
events   
wireless packet flood detected  
Minor
events   
wireless packet flood end  
Clear packet flood detected alarm
events   
rogue SSID detected  
Major
There is no overlay topology for Meraki devices. The topology is formed based on the connections that are discovered as part of the regular/legacy SNMP discover connections action in
DX NetOps Spectrum
.
Refer to SNMP Support for Cisco Meraki Solutions for a list of supported Meraki solutions, including wireless appliances and switches.