1 of 1 people found this helpful
If you're confident in your new configs and your sites can tolerate minor downtime, you can just copy to each unit's flash, copy to startup-configuration and schedule a reboot for overnight.
Using a text editor, copy the contents of your new config to your computer's clipboard. Logon to an AOS unit, go to the Enable prompt and disable event notification:
Prepare the console so that you can paste the config from your clipboard:
copy console mynewconfig.cfg
Then paste (right-click using Putty). After the paste operation is finished, press Ctrl-D. Now copy the new config to startup-config:
copy mynewconfig.cfg startup-config
Schedule a reload (using hhh:mm format)
reload in 10:00
When prompted, choose NO to saving the configuration, otherwise the current running-configuration will overwrite your changes to startup-configuration. Then choose YES that you're sure to reload.
Note that command syntax may vary, depending on your AOS version. Will this work for your situation?
This is pretty much what Adtran support recommended, although they recommended uploading the config through the web interface and doing a reboot from there without saving first. Why the 10 minute delay on the reload, though?
Just for convenience. The command "reload in" uses hhh:mm format, so the example was for 10 hours. Sometimes it's handy to let the unit reload after-hours so you don't bother users during normal operation.