Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

request system software validate

 

List of Syntax

Syntax

Syntax (TX Matrix Router)

Syntax (TX Matrix Plus Router)

Syntax (MX Series Router)

Syntax (Junos OS Evolved)

Syntax

Syntax (TX Matrix Router)

Syntax (TX Matrix Plus Router)

Syntax (MX Series Router)

Syntax (Junos OS Evolved)

Release Information

Command introduced before Junos OS Release 7.4.

sfc option introduced for the TX Matrix Plus router in Junos OS Release 9.6.

Command introduced in Junos OS Release 11.1 for the QFX Series.

set [package-name package-name] option added in Junos OS Release 12.2 for M Series, MX Series, T Series routers.

upgrade-with-config and upgrade-with-config-format format options added in Junos OS Release 12.3 for M Series routers, MX Series routers, and T Series routers.

Command introduced in Junos OS Release 14.1X53-D20 for the OCX Series.

on (host host <username username> | routing-engine routing-engine) option introduced in Junos OS Release 13.3, Junos OS Release 14.1, and Junos OS Release 15.1.

Command introduced in Junos OS Release 17.4 for EX Series switches.

set [package-name package-name] option deprecated in Junos OS Evolved 18.3R1.

restart option added in Junos OS Evolved Release 18.3R1.

Description

Validate candidate software against the current configuration of the router, the switch,or a remote host.

Options

lcc number(TX Matrix routers and TX Matrix Plus routers only) (Optional) On a TX Matrix router, validate the software bundle or package on a specific T640 router (or line-card chassis) that is connected to the TX Matrix router. On a TX Matrix Plus router, validate the software bundle or package for a specific router that is connected to the TX Matrix Plus router.

Replace number with the following values depending on the LCC configuration:

  • 0 through 3, when T640 routers are connected to a TX Matrix router in a routing matrix.

  • 0 through 3, when T1600 routers are connected to a TX Matrix Plus router in a routing matrix.

  • 0 through 7, when T1600 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.

  • 0, 2, 4, or 6, when T4000 routers are connected to a TX Matrix Plus router with 3D SIBs in a routing matrix.

on (host host <username username> | routing-engine routing-engine)(Optional) Validate the software bundle or package by comparing it to the running configuration on a remote host or Routing Engine. Specify either a host, replacing host with the remote hostname, or a Routing Engine, replacing routing-engine with the Routing Engine name. If you specify a remote host, you can optionally provide the username to be used to log in to the remote host.
member member-id(MX Series routers only) (Optional) Validate the software bundle or package on the specified member of the Virtual Chassis configuration. For an MX Series Virtual Chassis, replace member-id with a value of 0 or 1.
package-nameName of the software bundle or package to test.
restart(For Junos OS Evolved only) (Optional). Verify the new software configuration compatibility. This option verifies the ISSU services impact with new software. It emits the list of services which may get restarted when user issues this command.
scc(TX Matrix routers only) (Optional) Validate the software bundle or package for the TX Matrix router (or switch-card chassis).
set [package-name package-name](M Series, MX Series, T Series routers) (Optional) Install multiple software packages or software add-on packages at the same time.
sfc number(TX Matrix Plus routers only) (Optional) Validate the software bundle or package for the TX Matrix Plus router.
upgrade-with-config(Optional) Install one or more configuration files.
upgrade-with-config-format format(Optional) Specify the configuration file fomat, text or xml. The default format is text.
Note

The upgrade-with-config and upgrade-with-config-format options are only available locally on the router or switch. In a routing matrix, the configuration is applied only to the local router and is not propagated to other routers.

The options are validated during the validation process and applied to the router or switch during the upgrade process. If the upgrade process is successful, the options are removed from the configuration. If the upgrade process fails, the configuration file is renamed with the .failed suffix.

Additional Information

By default, when you issue the request system software validate command on a TX Matrix master Routing Engine, all the T640 master Routing Engines that are connected to it are validated. If you issue the same command on the TX Matrix backup Routing Engine, all the T640 backup Routing Engines that are connected to it are upgraded to the same version of software.

Likewise, if you issue the request system software validate command on a TX Matrix Plus master Routing Engine, all the T1600 or T4000 master Routing Engines that are connected to it are validated. If you issue the same command on a TX Matrix Plus backup Routing Engine, all the T1600 or T4000 backup Routing Engines that are connected to it are upgraded to the same version of software.

Required Privilege Level

maintenance

List of Sample Output

request system software validate (Successful Case)

request system software validate (Failure Case)

Output Fields

When you enter this command, you are provided feedback on the status of your request.

Sample Output

request system software validate (Successful Case)

user@host> request system software validate /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz

request system software validate (Failure Case)

user@host> request system software validate 6.3/
user@host> request system software validate test