Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

request system scripts synchronize

Syntax

request system scripts synchronize (all | commit | event | lib | op)<file filename><newer-than YYYY-MM-DD.HH:MM:SS>

Release Information

Command introduced in Junos OS Release 13.2.

Description

This command is for devices with multiple Routing Engines only. Synchronize scripts from the requesting Routing Engine to the other Routing Engine.

Specify all to synchronize all scripts present on the requesting Routing Engine to the responding Routing Engine. Specify commit, event, lib, or op to synchronize all scripts of the given type to the other Routing Engine. Include the file option or the newer-than option to narrow the scope to only synchronize scripts with the specified filename or date criteria.

If the load-scripts-from-flash statement is configured for the requesting Routing Engine, the device synchronizes the scripts that are in flash memory. Otherwise, the device synchronizes the scripts that are on the hard disk. If the load-scripts-from-flash statement is configured for the responding Routing Engine, the scripts are synchronized to flash memory. Otherwise, the scripts are synchronized to the hard disk. The device synchronizes a script regardless of whether it is enabled in the configuration.

The Junos XML management protocol equivalent for this operational mode command is: 

<request-scripts-synchronize>
   <all/> | <commit/> | <event/> | <lib/> | <op/>
   <file>filename</file>
   <newer-than>YYYY-MM-DD.HH:MM:SS</newer-than>
</request-scripts-synchronize>

Options

(all | commit | event | lib | op)
—

Synchronize all scripts or all scripts of a given type that are present on the requesting Routing Engine to the responding Routing Engine.

file filename
—

(Optional) Synchronize an individual script with the specified filename from the requesting Routing Engine to the responding Routing Engine. This option can only be used with a specific script type.

newer-than YYYY-MM-DD.HH:MM:SS
—

(Optional) Synchronize scripts that are more current than the specified date and time from the requesting Routing Engine to the responding Routing Engine.

Required Privilege Level

maintenance

 

Related Documentation

 

List of Sample Output

request system scripts synchronize all
request system scripts synchronize commit file
request system scripts synchronize event file
request system scripts synchronize op newer-than

Sample Output

request system scripts synchronize all

The following command synchronizes all scripts from the requesting Routing Engine to the responding Routing Engine.

user@host> request system scripts synchronize all
user@host>

request system scripts synchronize commit file

The following command synchronizes the commit script vpn-commit.slax from the requesting Routing Engine to the responding Routing Engine. In this case, the script does not exist on the requesting Routing Engine, and the device issues an error message.

user@host> request system scripts synchronize commit file vpn-commit.slax
error: Invalid directory: No such file or directory
warning: No script will be pushed to other RE

request system scripts synchronize event file

The following command synchronizes the event script ospf-neighbor.slax from the requesting Routing Engine to the responding Routing Engine. In this case, the responding Routing Engine does not have the resources to perform the operation, and the device issues an error message.

user@host> request system scripts synchronize event file ospf-neighbor.slax
error: Unable to copy scripts to re: re1

request system scripts synchronize op newer-than

The following command synchronizes any op scripts that have been modified after the specified date. In this case, no op scripts meet this requirement.

user@host> request system scripts synchronize op newer-than 2012-05-30
warning: No script will be pushed to other RE

Published: 2013-07-26

Previous Page Next Page