@zemarcio wrote:
Thank you cjoseph.
I didn't know the AMON.
One more question: is there an option to start a debug log level on all controllers for a client with problems, because when the client is roaming quickly, when I start a debug in one controller it may be on other controller now.
We deployed APs in one floor each one for a different controller. Is this a design problem?
There are some businesses that deploy with APs on one floor for each controller. That is because they cannot afford any downtime, so when upgrade time comes, only half of their infrastructure will be down. This is the exception, because even 24/7 businesses like hospitals schedule a 1 hour outage to upgrade their controller (it takes much less time than that), and they are fine.
The side effect of putting access points on everyother floor to a different controller is that it is MUCH more difficult to decipher a roaming or a client issue, because logs are spread across both controller. If you do not need to have absolutely zero downtime, you would save yourself some administration worries if you put all the access points in the same building on the same controller.
Putting every other floor on a different controller does increase your uptime, somehow, but having all the access points fail over to a backup controller would accomplish the same thing without making troubleshooting more difficult....
That is just my general opinion. Maybe your local Aruba SE or reseller who knows about your specific setup can give you better advice.