[j-nsp] Feature idea: commit and-reboot

[Pekka Savola]

On Wed, 21 Jan 2004, Ryburn, Justin wrote:
> I think keeping the existing restart/reload methods is probably a good
> idea.  However, having something like 'commit after-reload' might be
> useful.  Then you could just reload as normal and the changes would be
> made when the router boots back up.  Might also be a good idea to have
> some kind of warning when you reload that the current configuration and
> the startup configuration differ.  Just in case someone did a 'commit
> after-reload' and never did their reload.

This idea is a bit problematic.  The syntactic config checker is a bit 
.. lacking.  You wouldn't want to run into a situation where at 
reboot, the router wouldn't come up due to invalid configuration.  So, 
in that light something like 'commit delay-activation' sounds like a 
better idea (activation would be done when rebooting) if necessary -- 
I personally don't see much value in that though.

> -----Original Message-----
> From: juniper-nsp-bounces at puck.nether.net
> [mailto:juniper-nsp-bounces at puck.nether.net] On Behalf Of Richard A
> Steenbergen
> Sent: Tuesday, January 20, 2004 8:56 PM
> To: juniper-nsp at puck.nether.net
> Subject: [j-nsp] Feature idea: commit and-reboot
> 
> 
> While attempting to combine a software upgrade and reboot with a commit
> change that would require a routing bounce (to minimize flaps
> obviously),
> I noticed that there is no way to make a change which will take affect
> after the reboot is complete.
> 
> If you wanted to, say, turn on graceful-restart, change the families you
> negotiate on BGP sessions, or otherwise make a session-resetting (but
> not
> so complex you need the safety net of commit confirmed) change while you
> are upgrading or rebooting (the equiv of changing your startup-config
> without changing your running-config), there doesn't seem to be any way
> to
> do it (other than trying to be really fast :P) which won't result in two
> bounces.
> 
> I know the Juniper philosophy is "always make the configured state the
> current state", but perhaps a "commit and-reboot" type command could be
> used to check the config, apply it in the appropriate databases for
> after
> the reboot, and then begin the reboot without reloading the daemons with
> 
> the new config?
> 
> 

-- 
Pekka Savola                 "You each name yourselves king, yet the
Netcore Oy                    kingdom bleeds."
Systems. Networks. Security. -- George R.R. Martin: A Clash of Kings