07-01-2016 07:55 AM
I just upgraded from 184.108.40.206 to 220.127.116.11 and after everything was back up and running, it looks like I lost part of my config. During the upgrade, I had "yes" selected to save the configuration before the reboot. Does this option mean it saves my running to startup? Or does it copy my running config somewhere else?
If the second one, is there a procedure to restore it? The cron to backup this controller was apparently not working, so I don't have the most current backup handy.
This is on a 7005 controller.
Solved! Go to Solution.
07-01-2016 07:59 AM
07-01-2016 08:08 AM
I do see them in there. Is there a safe way to attempt a restore? Is there any way to validate what that config looks like ahead of time, or to do a diff, etc? Or can I load it into the running config and if it's no good, copy start to run?
07-01-2016 08:19 AM
You can copy the file from flash to your computer using TFTP and take a look. You can also change the boot options to boot from the file you desire.
Aruba Customer Engineering
Looking for an Answer? Search the Community Knowledge Base Here: Community Knowledge Base
07-01-2016 09:02 AM - edited 07-01-2016 09:03 AM
Alright, I SCP'd the flash to my backup server, unzipped it, and grep'd all of the files for 'essid' to see if the missing SSID was in any of them. It's not there - even in the "default.cfg_writemem_..." file created just before the upgrade reboot. So then I looked at the reboot logs and apparently there was a power outage a few hours before the upgrade that caused an unplanned power cycle.
I always forget to "save configuration" since a manual apply/save is already required to apply config to memory. I'll add a write mem to the start of my nightly backup script to avoid this in the future.
Thanks for your help!