request system software validate

Syntax

Syntax (TX Matrix Router)

Syntax (TX Matrix Plus Router)

Release Information

Command introduced before JUNOS Release 7.4.

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

Description

Validate candidate software against the current configuration of the router.

Options

package-name — Name of the software bundle or package to test.

lcc number — (TX Matrix 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 on a specific T1600 router (or line-card chassis) that is connected to the TX Matrix Plus router. Replace number with a value from 0 through 3.

scc — (TX Matrix routers only) (Optional) Validate the software bundle or package for the TX Matrix router (or switch-card chassis).

sfc number — (TX Matrix Plus routers only) (Optional) Validate the software bundle or package for the TX Matrix Plus router (or switch-fabric chassis).

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 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 backup Routing Engines that are connected to it are upgraded to the same version of software.

Required Privilege Level

maintenance

Related Topics

request system software add
request system software delete
request system software rollback

List of Sample Output

Output Fields

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

Sample Output

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)

Pushing bundle to lcc0-re0
error: Failed to transfer package to lcc0-re0

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