Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
 

request system software sync

Syntax

Description

Use this command on the primary Routing Engine (RE) of a system to synchronize the software and configurations from the primary RE to the other nodes and reboot the other nodes. The configurations are synchronized even if the images are identical. If specified on the backup RE, the command fails.

Options

current | rollback | all-versions

Specify which software version (current, rollback, or all versions) to sync to the other node:

  • For the current option, the system syncs the current version from the primary RE to the other node and reboots the other node with that version. If the current version on the primary RE of the system matches the version on the other node of the system, the command fails.

  • For the rollback option, the system synchronizes the rollback version to the other node. If the rollback version on the primary RE of the system matches the rollback version on the other node, the command fails.

  • For the all-versions option, the system synchronizes all software versions and configurations from the primary RE to the other node and reboots the other node if there's a mismatch between current versions.

Additional Information

For the all-versions option, the synchronization proceeds as follows:

  1. All versions are deleted on the other node, except for the current version.
  2. The current and rollback images and configurations are copied from the primary RE to the other node. Even if the software versions match, the configuration is copied and the software proceeds to the next image.
  3. Any other versions and configurations are copied from the primary RE to the other node.
  4. If the current version on the other node is not the same as current on the primary RE, then the other node is rebooted after warning the user.

The request system software sync all-versions command is successful if the first two steps of the synchronization are successful. If step 3 fails, a warning message is displayed. To make the versions match, you can delete the extra versions using the request system software delete operational mode command.

To see what the software versions are available on the device, use the show system software list command.

If an RE that has a different software version is inserted into the system, the RE is kept outside the system and a software mismatch alarm is generated, which specifies the RE name and the version of software on that RE, similar to the following: Software Version Mismatch on re1:junos-evo-install-ptx-x86-64-20.4R2.6-EVO. To clear this alarm, use the request system software sync all-versions command to synchronize the software. Once the new RE comes back up, it joins the system.

For the current option, before you switch control to a newly-inserted RE, ensure all images are synchronized to the newly-inserted RE by using the output from the show system software list operational mode command to compare the images installed on both REs and make sure they are the same. You must make sure that the system has finished synchronizing all of the images in the background before you switch control to the newly- inserted RE to ensure that the newly-inserted RE does not remove any images from the existing RE.

Required Privilege Level

view

Sample Output

request system software sync current

request system software sync rollback (Versions Are Already The Same)

request system software sync all-versions

Release Information

Command introduced in Junos OS Evolved Release 18.3R1.