Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

request system software validate

Syntax

request system software validate package-name <set [package-name package-name]><upgrade-with-config><upgrade-with-config-format format>

Syntax (TX Matrix Router)

request system software validate package-name <lcc number | scc><set [package-name package-name]><upgrade-with-config><upgrade-with-config-format format>

Syntax (TX Matrix Plus Router)

request system software validate package-name <lcc number | sfc number><set [package-name package-name]><upgrade-with-config><upgrade-with-config-format format>

Syntax (MX Series Router)

request system software validate package-name<member member-id><set [package-name package-name]><upgrade-with-config><upgrade-with-config-format format>

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, and Branch SRX Series Services Gateways.

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.

Description

Validate candidate software against the current configuration of the router.

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.
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-name
—

Name of the software bundle or package to test.

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, and Branch SRX Series Services Gateways only) (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

 

Related Documentation

 

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 
Checking compatibility with configuration
Initializing...
Using /packages/jbase-5.3I20020122_1901_sjg
Using /var/sw/pkg/jbundle-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jbase-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jkernel-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jcrypto-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jpfe-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jdocs-5.3I20020124_0520_sjg.tgz
Using /var/chroot/var/tmp/jbundle/jroute-5.3I20020124_0520_sjg.tgz
Validating against /config/juniper.conf.gz
mgd: commit complete

WARNING: cli has been replaced by an updated version:
CLI release 5.3I0 built by sjg on 2002-01-24 05:23:53 UTC
Restart cli using the new version ? [yes,no] (yes)

request system software validate (Failure Case)

user@host> request system software validate 6.3/ 
Pushing bundle to lcc0-re0
error: Failed to transfer package to lcc0-re0
user@host> request system software validate test
Pushing bundle to lcc0-re0
Pushing bundle to lcc2-re0

lcc0-re0:
gzip: stdin: not in gzip format
tar: child returned status 1
ERROR: Not a valid package: /var/tmp/test

Published: 2013-09-25

Previous Page Next Page