[Contents] [Prev] [Next] [Index] [Report an Error]

Upgrading Individual Software Packages

Note: When you install individual software packages, the following notes apply:

When upgrading from JUNOS Release 8.2 or earlier to JUNOS Release 8.5, use the system software add < image> no-validate command option.
Only use the jinstall JUNOS software image when upgrading or downgrading to or from JUNOS Release 8.5. Do not use the jbundle image.
Before upgrading to JUNOS Release 8.5, ensure that the routing platform’s CompactFlash card is 256 MB or larger to avoid disk size restrictions. (M7i routers without a CompactFlash card are excluded.)

To upgrade an individual JUNOS software package, follow these steps:

Download the software packages you need from the Juniper Networks Support Web site at http://www.juniper.net/support/. Choose either the Canada and U.S. Version or the Worldwide Version.

To download the software packages, you must have a service contract and an access account. If you need help obtaining an account, complete the registration form at the Juniper Networks Web site: https://www.juniper.net/registration/Register.jsp.

Note: We recommend that you upgrade all individual software packages using an out-of-band connection from the console or fxp0 interface, because in-band connections can be lost during the upgrade process.

Back up the currently running and active file system so that you can recover to a known, stable environment in case something goes wrong with the upgrade:



 user@host> request system snapshot

The root file system is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router’s CompactFlash card, and the /altroot and /altconfig file systems are on the router’s hard disk.

Note: After you issue the request system snapshot command, you cannot return to the previous version of the software, because the running copy and the backup copy of the software are identical.

If you are copying multiple software packages to the router, copy them to the /var/tmp directory on the hard disk:user@host> file copy ftp://username :prompt@ftp.hostname .net/filename/var/tmp/filename
Add the new software package:user@host> request system software add/var/tmp/ package-name-signed.tgz validate
package-name is the full URL to the file.

The system might display the following message:
```
pkg_delete: couldn’t entirely delete package
```
This message indicates that someone manually deleted or changed an item that was in a package. You do not need to take any action; the package is still properly deleted.

If you are upgrading more than one package at the same time, add jbase first. If you are using this procedure to upgrade all packages at once, add them in the following order:
user@host> request system software add /var/tmp/jbase-release-signed.tgzuser@host> request system software add /var/tmp/jkernel-release-signed.tgzuser@host> request system software add /var/tmp/jpfe-release-signed.tgzuser@host> request system software add /var/tmp/jdocs-release- signed.tgzuser@host> request system software add /var/tmp/jweb-release- signed.tgzuser@host> request system software add /var/tmp/jroute-release-signed.tgzuser@host> request system software add /var/tmp/jcrypto-release-signed.tgz
Reboot the router to start the new software: user@host> request system reboot
After you have upgraded or downgraded the software and are satisfied that the new software is successfully running, issue the request system snapshot command to back up the new software:user@host> request system snapshot
The root file system is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on the router’s CompactFlash card, and the /altroot and /altconfig file systems are on the router’s hard disk.

Note: After you issue the request system snapshot command, you cannot return to the previous version of the software, because the running copy and backup copy of the software are identical.

[Contents] [Prev] [Next] [Index] [Report an Error]