[Contents] [Prev] [Next] [Index] [Report an Error]

Scheduling a JUNOS Commit Operation

You can schedule when you want your candidate configuration to become active. To save JUNOS software configuration changes and activate the configuration on the router at a future time or upon reboot, use the commit at configuration mode command, specifying reboot or a future time at the [edit] hierarchy level:

[edit]
user@host # commit at string

string is reboot or the future time to activate the configuration changes. You can specify time in two formats:

Enclose the string value in quotation marks (" "). For example, commit at "18:00:00". For date and time, include both values in the same set of quotation marks. For example, commit at "2005-03-10 14:00:00".

A commit check is performed immediately when you issue the commit at configuration mode command. If the result of the check is successful, then the current user is logged out of configuration mode, and the configuration data is left in a read-only state. No other commit can be performed until the scheduled commit is completed.

Note: If the JUNOS software fails before the configuration changes become active, all configuration changes are lost.

You cannot issue the commit at configuration command after you issue the request system reboot command.

You cannot issue the request system reboot command once you schedule a commit operation for a specific time in the future.

You cannot commit a configuration when a scheduled commit is pending. For information about how to cancel a scheduled configuration by means of the clear command, see the JUNOS System Basics and Services Command Reference.


[Contents] [Prev] [Next] [Index] [Report an Error]