In case the network location of the master source copy defined by the source statement at the [edit system scripts op file filename] hierarchy level becomes unreachable, you can refresh an op script with a copy from a different location. To do this, include the refresh-from statement at the [edit system scripts op file filename] hierarchy level:
- [edit system scripts op file filename]
-
refresh-from url;
Specify the source as an HTTP URL, FTP URL, or scp-style remote file specification.
The refresh operation happens as soon as you include the refresh-from statement in the configuration and issue the commit command. The refresh-from statement is not carried in the configuration file. In this way, it behaves like an operational mode command.
To refresh all scripts from a specified source, include the refresh-from statement at the [edit system scripts op] hierarchy level:
- [edit system scripts op]
-
refresh-from url;
Specify the source as an HTTP URL, FTP URL, or scp-style remote file specification.
If a platform has dual Routing Engines and you want the script to be refreshed on both Routing Engines, you must include the refresh-from statement in the configuration of both Routing Engines. The commit synchronize command does not cause the refresh-from statement to take effect on scripts in both Routing Engine directories.
The refresh and refresh-from statements are mutually exclusive.