06-28-2012 04:47 AM
We are getting ready to deploy a 651 Controller but I noticed that the latest 188.8.131.52 has some major caveats related to the 651 funcionality , and I was wondering what 6.1.x.x AOS code is more stable for the 651 controller.
Lead Mobility Engineer @ Integration Partners
AMFX | ACMX | ACDX | ACCX | CWAP | CWDP | CWNA
Solved! Go to Solution.
06-28-2012 06:17 AM
According to the release notes - "An Aruba 651 controller is susceptible to continuous rebooting if its internal AP (radio) is configured in Air Monitor mode (am-mode).
Reconfigure the internal AP (radio) in Access Point mode (ap-mode). Alternatively, you may disable the radio if not needed."
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
06-28-2012 04:00 PM
I always / always recommend
1) a seperate AP group for the internal AP on the 651 controller from the other APs in the deployment .
Why? That way the configuration of that internal AP is deterministic and you don't have to be careful/mindful of any settings that you meant to apply in the broader deployment.
2) never modify any profile that has the word 'default' in it... instead make 'new' profiles for all APs, and seperate profiles on the internal AP vs. non-internal APs. That way you (again) avoid any 'whoops we just turned on/off something on the internal AP that we only meant for the other APs.
This approach has served me...and many others well...