09-24-2014 11:15 AM
I've inherited a 3200 (non XM) controller that is currently running 220.127.116.11 code. Probably a good idea to get it updated. As far as I can tell I can use 6.1.x.x releases as the latest major branch of code on the non-XM 3200s. My network only consists of AP-105s.
Can anyone think of a problem with moving moving to 18.104.22.168 on this controller. Nothing jumped out at me in the release notes PDF. It's a signifact version jump and I'm only about 2 weeks into my Aruba experience. There maybe known issues I don't know about.
Wireless SSIDs deployed:
Currently tunneling all traffic back to controller and sending it to the appropriate VLAN.
WPA-TKIP w/ 802.1x (Server side cert is already trusted on clients)
A guest portal with no encryption
Hoping to turn on control plane security so I can do bridge mode forwarding instead of tunneling traffic.
Deploy WPA2-AES-PSK for some devices.
Deploy WPA2-AES w/ 802.1x with client-side cert check
Anyone know of any issues with the version jump and/or my future plans for wireless network deployments?
Solved! Go to Solution.
09-25-2014 12:34 AM
If you have no issues now, you should be fine. You could ask TAC to review your tech-support to see if there is anything specific that you are doing that would keep you from upgrading successfully.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base