28.06.2014 Views

Discussion

Discussion

Discussion

SHOW MORE
SHOW LESS

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

The time is in 24-hour (military) format, so to specify a time after 12 p.m., use the<br />

following command:<br />

[edit]<br />

aviva@router1# commit at 22:45<br />

configuration check succeeds<br />

commit at will be executed at 2005-02-25 22:45:00 PST<br />

Exiting configuration mode<br />

To schedule the activation of a configuration to occur on another day, use the full<br />

date and time:<br />

[edit]<br />

aviva@router1# commit at "2005-02-26 10:45"<br />

configuration check succeeds<br />

commit at will be executed at 2005-02-26 10:45:00 PST<br />

Exiting configuration mode<br />

To cancel a commit operation scheduled with the commit at command, use the following<br />

command:<br />

aviva@router1> clear system commit<br />

Pending commit cleared<br />

<strong>Discussion</strong><br />

Sometimes you want to delay the activation of a configuration, scheduling it to occur<br />

at some later time. For example, if you are a network provider and have a service<br />

window in which network changes are made, you want the new configuration to<br />

take effect during that window. Or, if you are making changes on a number of routers,<br />

you might want the changes to take effect on all the routers at the same time or<br />

within the same time window, especially if you are making changes to routing protocols<br />

that might affect routing and route convergence across the network.<br />

One way to schedule the activation of a configuration is to use the commit at command.<br />

The first two commands in this recipe commit the configuration at a specific<br />

time on the current day, one at 10:45 a.m. and the second at 10:45 p.m. The third<br />

command schedules the commit at 10:45 a.m. on another day.<br />

Verify that the commit command has actually executed by looking at the timestamp<br />

on the currently running configuration file:<br />

aviva@router1> file list detail /config<br />

/config:<br />

total 34<br />

-rw-r----- 1 root wheel<br />

-rw-r----- 1 root wheel<br />

-rw-r----- 1 root wheel<br />

-rw-r----- 1 root wheel<br />

drwxr-xr-x 2 root wheel<br />

2127 Feb 25 03:10 juniper.conf.1.gz<br />

2127 Feb 25 03:00 juniper.conf.2.gz<br />

2127 Feb 24 12:56 juniper.conf.3.gz<br />

2127 Feb 25 10:45 juniper.conf.gz<br />

512 Jan 18 2004 license/<br />

38 | Chapter 1: Router Configuration and File Management<br />

This is the Title of the Book, eMatter Edition<br />

Copyright © 2008 O’Reilly & Associates, Inc. All rights reserved.

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!