Refreshing an Op Script from the Master Source

To refresh a local op script with a copy from the location specified in the source statement, include the refresh statement at the [edit system scripts op file filename] hierarchy level:

When you commit the configuration and the refresh operation is performed, the copy of the XSLT or SLAX file located in the /var/db/scripts/op directory is overwritten by the copy of the file located at the URL you configure in the source statement at the same hierarchy level. If the script is enabled as described in Enabling an Automation Script and Defining a Script Alias, the refreshed copy of the automation script runs immediately during the current commit operation.

To refresh all scripts from their sources, include the refresh statement at the [edit system scripts op] hierarchy level:

If a platform has dual Routing Engines and you want the script to be refreshed on both Routing Engines, you must include the refresh statement in the configuration of both Routing Engines. The commit synchronize command does not cause the refresh statement to take effect on scripts in both Routing Engine directories.

The refresh operation happens as soon as you include the refresh statement in the configuration and issue the commit command. The refresh statement is not permanently recorded in the configuration file. In this way, it behaves like an operational mode command.

Copyright © 2008, Juniper Networks, Inc. All rights reserved. Trademark Notice.