02-21-2012 02:18 PM - edited 02-21-2012 02:23 PM
We recently changed our guest captive portal solution over to Amigopod, and since then our Aruba guest controllers (the one that still does the redirect over to Amigopod) is pegging CPU at 100% fairly often. Is there any way to see what is causing the high CPU? show processes only shows system processes, not user, AFAICT.
(XXXXX) #show cpuload
user 91.6%, system 8.4%, idle 0.0%
2400 Controller running 188.8.131.52
02-21-2012 02:45 PM
SSL is used, yes. It's a standard Aruba/Amigopod integration, so I wouldn't expect something like this to kill a controller. Any idea how one can definitively tell what's causing this?
02-21-2012 02:49 PM
Now someone ask about this...
Is there is a way on Aruba controller to know what process is using all the CPU or memory?
At least you can do that on fortigates, you can run a diagnosis command to know what process is taking all the cpu and memory for easy troubleshooting....
Product Manager - Aruba Networks
02-21-2012 03:06 PM
Im not sure about that. I can see The ArubaOS CRG states that the command "Displays a list of all process running on the controller".
How can you tell that its only showing system processes?
02-22-2012 08:09 AM
Yes, show cpuload current is what I was looking for. We have a case open and the tech ran that command. Funny, I was just about to post that.
Turns out it is the httpd daemon that's killing the CPU. Not sure what I'm supposed to do about it, there were no minimum requirements on the Aruba controller in the Amigopod docs.