ArubaOS and Controllers

Aruba Employee

3.3.1.x to upgrade - config corruption

Has anyone else experienced a configuration corruption issue when upgrading from 3.3.1.x to 3.3.2.x? I've seen it four times now, once in the lab, and three in production (my two masters and a local). Basically, all I did was loaded into the controllers and rebooted, nothing else. The controllers wouldn't come on line and after putting a console on, I noticed my login banner was appended with random bits of config lines.
I could not login to the device with my admin credentials, so I used the password/forgetme! method to get in. I had no time to open a case as I was under a change control and had to get the devices back up. I had to wr erase the configs on all three devices and start over.
Search Airheads
Showing results for 
Search instead for 
Did you mean: