zlacker

And then if it worked for those 5 min before the reboot, you'd redeploy the change 'for real', without a reboot?

>>dang+(OP)
Yeah, there are different kinds of memory in firewalls. Like a running-config and a startup-config. If you just change the running-config and don't commit to the startup-config, when the reboot takes place it'll pull the config from the (non-modified) startup-config instead, reverting changes.

>>dang+(OP)
My typical workflow was:

- Schedule the reboot

- do my changes

- Make sure everything was working properly

- Go get lunch

- Notice a bunch of pages and alarms about a firewall going offline

- Rush back to my office

- Login to the firewall

- Schedule the reboot

- Re apply the changes

- Test it again

- CANCEL THE FING REBOOT THIS TIME

- Eat my now cold lunch

>>2snake+t3
copy run start!

>>Nifty3+bm
This used to be my workflow as well. I did make a few improvements though

  - begin change control at 4:55pm on Friday before Christmas
  - schedule reboot
  - paste changes
  - make sure everything is working properly
  - leave security key on desk 
  - go to christmas party
  - firewall goes offline, pages go off
  - remotely log into firewall with phone
  - rush back to office to get security key
  - accidentally type init 1 hanging server
  - discount datacenter remote hands not picking up the  phone
  - rush to datacenter to power cycle server
  - :(