topic Health Check for ZoneDirector Controller in Access Points - Indoor and Outdoor

Health Check for ZoneDirector Controller

mahfoud_boulemt — Thu, 30 Jul 2015 07:01:00 GMT

What are the recommended ZoneDirector health Values: CPU Util, Memory Util,... and what are threshold values to get alarms?

Re: Health Check for ZoneDirector Controller

max_o_driscoll — Thu, 30 Jul 2015 10:16:31 GMT

Are you referring to the monitoring tab with various widgets you can display?
In ZD gui go to:
monitor
real time monitoring
choose start/stop and a time value (screenshot below)

I haven't heard of any particular values to be considered good because it will depend on how many access points and how many clients (for instance) you are supporting.
Bad would be 100% and time to consider an upgrade or find out why you ZD is stressed.

If your ZD responds sluggishly or feels "slow" then you know it's working hard and the monitoring tab will only give you pretty pictures to confirm this!
Rather like task manager in windows you get a feel for the numbers and what's normal rather than going by hard and fast rules.

NOTE: I seem to remember (from a comment by tech staff) that actually using the monitoring tool was quite cpu/memory intensive so do not leave it running in background unless you have a good reason.

Re: Health Check for ZoneDirector Controller

alexandra_frinc — Thu, 30 Jul 2015 13:57:10 GMT

We monitor CPU and memory utilization with cacti (a related topic for cacti monitoring https://forums.ruckuswireless.com/ruckuswireless/topics/anyone_using_cacti )

In the past with a ZD3k we’ve set an alarm threshold for the CPU utilization of 60%, relative to the load we had.

It depends on how many APs you use and the load (in terms of number of clients). In our case (multiple SSIDs, 2 802.1X SSIDs, DVLAN) the CPU of ZD3k spiked at 90%-100% several times with 6k simultaneous clients, 450APs, resulting in ZD unresponsive. These numbers were less than the theoretical limits of 1k APs and 10k clients for ZD3k. Since we changed to a ZD5k, the CPU did not went above 15%.

We also did a http health check for the ZD web interface (script which sends an alarm if the ZD url is unresponsive).