ferttrends.blogg.se - Ubiquiti device discovery tool does not work

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT WORK HOW TO

UBIQUITI DEVICE DISCOVERY TOOL DOES NOT WORK HOW TO

See also the Paessler website: How to set up notifications via the PRTG web interface.

This way you are notified as soon as the number of connected access points is lower than expected. For example, define a lower error limit for the number of connected access points. Once the sensor is deployed, you're advised to set up limits in the channel's settings. The sensor will not produce any alerts by default, unless it is unable to authenticate or contact the UniFi controller. For further information refer to the Knowledge Base articles Guide for PowerShell based custom sensors and PowerShell 32-bit and 64 bit and execution policy.

Configure your PRTG probe to enable the execution of unsigned scripts/code.

Note: We cannot guarantee that it works with other UniFi controller versions.

The script was tested with the UniFi controller versions 5.3.8 ~ 6.0.43.

The PRTG probe on which you want to deploy the sensor must run PowerShell version 3 or later.

The PRTG probe on which you want to deploy the sensor must be able to reach the UniFi controller on the "API" port (default is 8443).

Number of Upgreadeable Access Points (UAPs in Connected status with upgradable flag set).

Number of Connected Access Points (UAPs in Connected status).

Number of Connected Clients (Total (Clients+Guests)).

Response time from the controller's API.

The sensor shows you the following per-site statistics: We've put together an EXE/Script Advanced sensor that you can use to monitor general statistics and information of your Ubiquiti UniFi deployment, regarding especially the access points. This article applies to PRTG Network Monitor 16.4.27 or later Monitoring Ubiqiti UniFi Devices with PRTG