In a shared environment, care should be taken to ensure the user is restricted to the proper Organizations. This plugin allows auditing of the access provided to the user. Note that only one Organization can be configured on each Dashboard device in Zenoss (zMerakiOrganizationId). Retrieves the list of Organizations that the configured API Key can be used to access and displays on the Dashboard Device Overview page.Creates Device components for the Network Devices returned from the Meraki SNMP Proxy.The following modeler plugins are provided for Dashboard Devices.
(Optional) Password for Basic Authentication (Optional) Username for Basic Authentication If use of an HTTP Proxy is required to communicate with the Meraki Dashboard API, the following zProperties will be used.
If manually adding end Devices (not using the built-in discovery) then each Device will also need to be configured for the organizationId and Device Serial Number. If the ID is unknown, this can be left unset and the '' modeling plugin will pull a list of the Organizations the API user can access and display them on the Dashboard Device Overview Page.
In addition, the Organization ID will need to be set (editable on the Device Overview page). API Key for the monitoring user to use for API queries.Will likely always use the default: ' '.Configure the Devices to send SNMP Traps to Zenoss to create Events.Ĭonfigure the following zProperties to enable the API communication: SNMP Trap translation is provided by the ZenPack. SNMP Polling from the Dashboard provides the following Components and Monitoring on the Dashboard Device.Īdditionally this information is used on the Meraki Devices to model and monitor ZMerakiSnmpHost also specifies the port to use, for example: " :16100" If multiple Organizations are to be monitored, a Dashboard device will need to be added in Zenoss for each.ĭue to the Meraki SNMP Proxy using the same IP for multiple Organizations, each Dashboard will need to be configured for it's unique SNMP settings (available in the Meraki Dashboard under Organization > Settings > SNMP).Ĭonfigure zMerakiSnmpHost and zSnmpCommunity with the settings provided for the Organization in the Meraki Configuration interface. The hostname/IP for the device is not used directly for modeling or polling, so can be set to any unique value.Įach added Dashboard device monitors all Networks and Devices in a single Meraki Organization. Rather than monitoring the manageIp as typical with Zenoss devices, this ZenPack instead monitors the IP address of each of the Uplink components.Ĭonfiguration and Adding Dashboard DevicesĪdd a Meraki Dashboard device in Zenoss under the /Network/Meraki/Dashboard Device Class. The Meraki Network Devices are configured with a customized Ping monitor. The '' modeler is included by default.Ĭonnection information is configured with the typical zProperties on the Devices. It is expected that most use cases will not support this, but we include it as a 'best effort' to try get as much data as possible from the devices. Use of SNMP polling may not be possible or practical depending on the network architecture. This is the traditional SNMP as used elsewhere in Zenoss, where the Device's manageIp is polled directly via SNMP. NOTE: The Network Devices pull their SNMP connection information from the zMerakiSnmpHost and zSnmpCommunity properties on the associated Dashboard Device. This endpoint is polled from both Dashboard (the modeler) and Network Devices (the modeler). The Meraki SNMP proxy is a cloud service that aggregates data from the Network Devices and provides it through a unified SNMP endpoint. The Dashboard REST API is used by both the Dashboard and Network Devices for modeling and monitoring (see details in the modeler plugins and configuration sections below). How these are used may differ between Dashboard and Network Devices. This ZenPack uses several sources of data for modeling and monitoring Meraki Devices. SNMP Polling can be enabled for the Dashboard devices (using the SNMP connection information provided for the Organization) and for the Network Devices, if enabled on individual Devices and network connectivity exists between the collector and Device.ĪPI Polling uses the same global API to monitor all devices, so should be available regardless of the network connectivity between Zenoss and the Network Devices. This ZenPack adds Discovery, Modeling, and Monitoring for Meraki Network devices managed through the Meraki Dashboard API and SNMP Polling. Contact Zenoss to request more information regarding this or any other ZenPacks. All standard packages are renewable every 12 months from the date of purchase. Our Integration Services are offered as subscriptions in order to provide initial setup and ongoing compatibility and maintenance.
This integration is a subscription-based Professional Services engagement.