request system software validate (Junos OS)
Syntax
request system software validate package-name <on (host host <username username> | routing-engine routing-engine)> <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> <on (host host <username username> | routing-engine routing-engine)> <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> <on (host host <username username> | routing-engine routing-engine)> <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> <on (host host <username username> | routing-engine routing-engine)> <set [package-name package-name]> <upgrade-with-config> <upgrade-with-config-format format>
Description
Use this command to 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:
|
| 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
|
| 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-namepackage-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, The 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 primary Routing Engine, all the T640 primary 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 primary Routing Engine, all the T1600 or T4000 primary 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
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
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.
set [package-namepackage-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.
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.