<%NUMBERING1%>.<%NUMBERING2%>.<%NUMBERING3%> PRTG Manual: Cisco Meraki Network Health Sensor

Enabled organization API access

This sensor requires that you enable the access of an organization to the Cisco Meraki Dashboard API.

If the API access for an organization is disabled, you must enable it manually. For more information, see Cisco Meraki Dashboard API: Enable API Access.

Credentials

This sensor requires credentials for Cisco Meraki.

IPv6

This sensor supports IPv6.

Performance impact

This sensor has a very low performance impact.

Scanning interval

• The minimum scanning interval of this sensor is 10 seconds.
• The recommended scanning interval of this sensor is 5 minutes.

Multi-platform probe

You can add this sensor to a multi-platform probe.

Network

The name of the network that this sensor monitors.

Organization

The name of the organization that the monitored network belongs to.

Primary Channel

Select a channel from the list to define it as the primary channel. In the device tree, PRTG displays the last value of the primary channel below the sensor's name. The available options depend on what channels are available for this sensor.

You can set a different primary channel later by clicking below a channel gauge on the sensor's Overview tab.

Graph Type

Define how this sensor shows different channels:

• Show channels independently (default): Show a graph for each channel.
• Stack channels on top of each other: Stack channels on top of each other to create a multi-channel graph. This generates a graph that visualizes the different components of your total traffic.
  You cannot use this option in combination with manual Vertical Axis Scaling (available in the channel settings).

Stack Unit

This setting is only visible if you select Stack channels on top of each other above.

Select a unit from the list. PRTG stacks all channels with this unit on top of each other. By default, you cannot exclude single channels from stacking if they use the selected unit. However, there is an advanced procedure to do so.

Result Handling

Define what PRTG does with the sensor result:

• Discard result (default): Do not store the sensor result.
• Store result: Store the last sensor result in the \Logs\sensors subfolder of the PRTG data directory on the probe system. The file name is Result of Sensor [ID].log. This setting is for debugging purposes. PRTG overwrites this file with each scanning interval.

This option is not available when the sensor runs on the hosted probe of a PRTG Hosted Monitor instance.

In a cluster, PRTG stores the result in the PRTG data directory of the master node.

Downtime

In the channel table on the Overview tab, this channel never shows any values. PRTG uses this channel in graphs and reports to show the amount of time in which the sensor was in the Down status

IOT "Alerting"

IOT devices in alerting status

IOT "Dormant"

IOT devices in dormant status

IOT "Offline"

IOT devices in offline status

IOT "Online"

IOT devices in online status

MR "Alerting"

Meraki Radios (MR) devices in alerting status

MR "Dormant"

MR devices in dormant status

MR "Offline"

MR devices in offline status

MR "Online"

MR devices in online status

MS "Alerting"

Meraki Switching (MS) devices in alerting status

MS "Dormant"

MS devices in dormant status

MS "Offline"

MS devices in offline status

MS "Online"

MS devices in online status

MX "Alerting"

Meraki Security (MX) devices in alerting status

MX "Dormant"

MX devices in dormant status

MX "Offline"

MX devices in offline status

MX "Online"

MX devices in online status

Uplinks "Active"

Uplinks in active status

This channel is the primary channel by default.

Uplinks "Failed"

Uplinks in failed status

Uplinks "Not Connected"

Uplinks in not connected status

Uplinks "Ready"

Uplinks in ready status