This device template can be used to automate the deployment of these sensors using auto-discovery.
While PRTG doesn't offer any alternative built-in sensor for Meraki's devices our Custom Sensors or this device template allows you to monitor your AP's Status and traffic counters. The built-in SNMP Traffic Sensor should also work but doesn't as Meraki's SNMP agent implementation does not respond to uptime queries. However, after setting up the community string, an MX can be configured to allow polling from a remote IP whitelist, configured under Security appliance > Configure > Firewall & traffic shaping. You will not be able to poll repeaters using SNMP as they do not have an IP address on the Local LANīy default, Meraki devices cannot be polled from outside the network. Using SNMP to directly poll individual devices provides the ability to choose between SNMP v1/v2c or v3. These settings can be found under Network-wide > General > Reporting:
Once enabled note the required SNMP host and Credentials, for example: Host(The device's address within PRTG)Ģ) Enabling direct/local device Polling (For Device's traffic Counters)Ĭonfiguration steps as provided by Meraki: In this scenario the SNMP traffic would stay within the local network and each device would need to be polled from the network management system. It also defines the community string and provides a sample command to extract information via SNMP requests. Once SNMP has been enabled you will be able to send the SNMP requests to the host that is defined directly under the enable setting. Preparation / Meraki Set-up 1) "Cloud" DashBoard (For monitoring AP's status)Ĭonfiguration steps as provided by Meraki: The Dashboard can be configured for SNMP polling from Organization > Settings > SNMP.
Meraki has an excellent SNMP Overview and Configuration article available at their website. The information available using each method is distinct. There are two very distinct ways of querying Meraki devices, they can either be monitored via the cloud(dashboard) or directly (using the individual AP IP addresses). This article applies to PRTG Network Monitor 16.2.25 or later
0 kommentar(er)
