How to monitor the performance of a local RADIUS instance

In this topic, you will find suggestions on monitoring the performance of the local RADIUS instance in a virtual machine. Such monitoring will require third-party tools.

The performance of a local RADIUS server depends on the volume of RADIUS authentication and accounting traffic it handles, which cannot be predicted in advance. You should monitor the server’s performance and increase resources if needed to prevent overload. This topic provides suggestions for tools that can help you monitor the local RADIUS server.

You may use any of the third-party tools listed here, but the list is not exhaustive – other server/RADIUS monitoring tools may also be available. For detailed usage instructions, refer to the tool manufacturer’s documentation.

Note: To monitor a local RADIUS server, you must enable SNMP in Portnox Cloud for that local RADIUS server, and may also need to forward the server’s syslog output to your monitoring tool. For instructions on configuring these settings, see: Set up a local RADIUS server using a virtual machine.
Note: The recommendations above apply to monitoring a local RADIUS server running in its own virtual machine. If you run the local RADIUS server in a Docker container instead, you must monitor the performance of the Docker host, which may also be running other containers. The Docker host is completely independent of Portnox Cloud, so no Portnox Cloud configuration is required for SNMP or syslog connectivity. You are responsible for setting up monitoring for the Docker host using your own tools and methods.