Hey y'all
I'm a newbie to the AOS-CX/Aruba Central world after over a decade manually managing switches in the old ProCurve/ArubaOS universe. I just sat down to deploy a new CX 6100 switch, naively thinking that the changes would be incremental from the old ArubaOS platform, but I am instead experiencing some serious future-shock. I'm attempting to translate the configurations from an EoL ProCurve to this new switch, however I've lost the privileges to locally configure the CX switch over HTTPS. I can still log in locally under the
admin account but it displays "Central Managed" at the top of the Web GUI page and appears to be in read-only mode now. Because of this, I'm in the awkward situation of having to configure the CX switch using Aruba Central via an internet connection
provided by the ProCurve it's replacing, and as far as I know "I'm my own grandpa" is only funny if it isn't playing out in a production network environment.
Ideally, I'd like to be able set the CX on my bench, isolated from the production network, and just plop in the initial configs (VLANs, static IPs, routing) manually while I explore Central and the new CLI interfaces at my leisure. Unfortunately Central seems to have hijacked management control from the local administrator over the HTTPS interface and I'm not sure how to find my way back to get this new switch into production.
My question is (perhaps) simple. How can I restore local management of a switch that has been on-boarded with Aruba Central? We're in a pretty vanilla authentication environment with no RADIUS or TACACS.
Looking forward to getting the ball rolling with this new platform and learning what else it is capable of. Thank you for your insights and patience!
------------------------------
Chris Zappe
------------------------------