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

Upgrade and Downgrade Instructions for JUNOS Software Release 9.5 for M-series, MX-series, and T-series Routing Platforms

This section discusses the following topics:

Basic Procedure for Upgrading to Release 9.5

When upgrading or downgrading the JUNOS software, always use the jinstall package. Use other packages (such as the jbundle package) only when so instructed by a Juniper Networks support representative. For information about the contents of the jinstall package and details of the installation process, see the JUNOS Software Installation and Upgrade Guide.

Note: With JUNOS Release 9.0 and later, the compact flash disk memory requirement for JUNOS software is 1 GB. For M7i and M10i routing platforms with only 256 MB memory, see the Customer Support Center JTAC Technical Bulletin PSN-2007-10-001 at https://www.juniper.net/alerts/viewalert.jsp?txtAlertNumber=PSN-2007-10-001&actionBtn=Search.

Note: Before upgrading, back up the file system and the currently active JUNOS configuration so that you can recover to a known, stable environment in case the upgrade is unsuccessful. Issue the following command:

user@host> request system snapshot

The installation process rebuilds the file system and completely reinstalls the JUNOS software. Configuration information from the previous software installation is retained, but the contents of log files might be erased. Stored files on the routing platform, such as configuration templates and shell scripts (the only exceptions are the juniper.conf and ssh files) may be removed. To preserve the stored files, copy them to another system before upgrading or downgrading the routing platform. For more information, see the JUNOS System Basics Configuration Guide.

The download and installation process for JUNOS Release 9.5 is the same as for previous JUNOS releases.

If you are not familiar with the download and installation process, follow these steps:

  1. Using a Web browser, follow the links to the download URL on the Juniper Networks Web page. Choose either Canada and U.S. Version or Worldwide Version:
  2. Log in to the Juniper Networks authentication system using the username (generally your e-mail address) and password supplied by Juniper Networks representatives.
  3. Download the software to a local host.
  4. Copy the software to the routing platform or to your internal software distribution site.
  5. Install the new jinstall package on the routing platform.

    Note: We recommend that you upgrade all software packages out-of-band using the console because in-band connections are lost during the upgrade process.

    Customers in the United States and Canada use the following command:


    user@host> request system software add validate reboot source/jinstall-9.5B1.7-domestic-signed.tgz

    All other customers use the following command:


    user@host> request system software add validate reboot source/jinstall-9.5B1.7-export-signed.tgz

    Replace source with one of the following values:

    The validate option validates the software package against the current configuration as a prerequisite to adding the software package to ensure that the router reboots successfully. This is the default behavior when the software package being added is a different release.

    Adding the reboot command reboots the router after the upgrade is validated and installed. When the reboot is complete, the router displays the login prompt. The loading process can take 5 to 10 minutes.

    Rebooting occurs only if the upgrade is successful.

Note: After you install a JUNOS 9.5 jinstall package, you cannot issue the request system software rollback command to return to the previously installed software. Instead you must issue the request system software add validate command and specify the jinstall package that corresponds to the previously installed software.

Note: Before you upgrade a router that you are using for voice traffic, you should monitor call traffic on each virtual BGF. Confirm that no emergency calls are active. When you have determined that no emergency calls are active, you can wait for non-emergency call traffic to drain as a result of graceful shutdown, or you can force a shutdown. For detailed information on how to monitor call traffic before upgrading, see the Multiplay Solutions Guide.

Upgrading a Router with Redundant Routing Engines

If the router has two Routing Engines, perform a JUNOS software installation on each Routing Engine separately to avoid disrupting network operation as follows:

  1. Disable graceful Routing Engine switchover (GRES) on the master Routing Engine and save the configuration change to both Routing Engines.
  2. Install the new JUNOS software release on the backup Routing Engine while keeping the currently running software version on the master Routing Engine.
  3. After making sure that the new software version is running correctly on the backup Routing Engine, switch over to the backup Routing Engine to activate the new software.
  4. Install the new software on the original master Routing Engine that is now active as the backup Routing Engine.

For the detailed procedure, see the JUNOS Software Installation and Upgrade Guide.

Upgrading to Release 9.5 in a Routing Matrix

By default, when you upgrade software on the TX Matrix platform, the new image is loaded onto the TX Matrix platform and distributed to all routing nodes in the routing matrix. To upgrade software for the entire routing matrix, issue the request system software add command. Customers in the United States and Canada use the following command:


user@host> request system software add source/jinstall-9.5B1.5-domestic-signed.tgz

All other customers use the following command:


user@host> request system software add source/jinstall-9.5B1.5-export-signed.tgz

Replace source with one of the following values:

When you complete the software installation and reboot the TX Matrix platform, all routing nodes also reboot and all hardware and software components in the routing matrix begin using the new software.

To upgrade the backup Routing Engines, log in to the backup Routing Engine on the TX Matrix platform before you issue the request system software add command. You can also update the software on the TX Matrix platform only or on a specific T640 routing node as needed by including the lcc or scc option.

Note: We recommend you run the same JUNOS software release on the master and backup Routing Engines on all components of a routing matrix. If you elect to run different JUNOS software releases on the Routing Engines, a change in Routing Engine mastership can cause one or all routing nodes to be logically disconnected from the TX Matrix platform. It is also a best practice to make sure that all master Routing Engines are re0 and all backup Routing Engines are re1 (or vice versa).

Note: You must use the same Routing Engine model on all routing platforms in a routing matrix. For example, it is not supported to use model RE-A-2000 on the TX Matrix platform and model RE-1600 on the routing nodes.

Upgrading Using ISSU

Unified in-service software upgrade (ISSU) enables you to upgrade between two different JUNOS software releases with no disruption on the control plane and with minimal disruption of traffic. Unified in-service software upgrade is only supported by dual Routing Engine platforms. In addition, graceful Routing Engine switchover (GRES) and nonstop active routing (NSR) must be enabled. For additional information about using unified in-service software upgrade, see the JUNOS High Availability Configuration Guide.

Note: Upgrading with ISSU from JUNOS 9.4R2 to any other release results in the loss of control traffic due to the loss of keepalives. This causes interfaces to go down and will result in the loss of respective adjacencies for all configured protocols. This problem only exist in JUNOS 9.4R2.

Upgrading from JUNOS Release 9.2 or Earlier on a Router Enabled for Both PIM and NSR

JUNOS Release 9.3 introduced NSR support for PIM for IPv4 traffic. However, the following PIM features are not currently supported with NSR. The commit operation fails if the configuration includes both NSR and one or more of these features:

JUNOS 9.3 introduced a new configuration statement that disables NSR for PIM only, so that you can activate incompatible PIM features and continue to use NSR for the other protocols on the router: the nonstop-routing disable statement at the [edit protocols pim] hierarchy level. (Note that this statement disables NSR for all PIM features, not only incompatible features.)

If neither NSR nor PIM is enabled on the router to be upgraded or if one of the unsupported PIM features is enabled but NSR is not enabled, no additional steps are necessary and you can use the standard upgrade procedure described in other sections of these instructions. If NSR is enabled and no NSR-incompatible PIM features are enabled, use the standard reboot or ISSU procedures described in the other sections of these instructions.

Because the nonstop-routing disable statement was not available in JUNOS Release 9.2 and earlier, if both NSR and an incompatible PIM feature are enabled on a router to be upgraded from JUNOS Release 9.2 or earlier to a later release, you must disable PIM before the upgrade and reenable it after the router is running the upgraded JUNOS software and you have enter4ed the nonstop-routing disable statement. If your router is running JUNOS Software Release 9.3 or later, you can upgrade to a later release without disabling NSR or PIM–simply use the standard reboot or ISSU procedures described in the other sections of these instructions.

To disable and reenable PIM:

  1. On the router running JUNOS Release 9.2 or earlier, enter configuration mode and disable PIM:
    [edit]

    user@host# deactivate protocols pim


    user@host# commit
  2. Upgrade to JUNOS Release 9.3 or later software using the instructions appropriate for the router type. You can either use the standard procedure with reboot or use ISSU.
  3. After the router reboots and is running the upgraded JUNOS software, enter configuration mode, disable PIM NSR with the nonstop-routing disable statement, and then reenable PIM:
    [edit]

    user@host# set protocols pim nonstop-routing disable


    user@host# activate protocols pim


    user@host# commit

Downgrade from Release 9.5

To downgrade from Release 9.5 to another supported release, follow the procedure for upgrading, but replace the 9.5 jinstall package with one that corresponds to the appropriate release.

Note: You cannot downgrade more than three releases. For example, if your routing platform is running JUNOS Release 9.3, you can downgrade the software to Release 9.0 directly, but not to Release 8.5 or earlier; as a workaround, you can first downgrade to Release 9.0 and then downgrade to Release 8.5.

For more information, see the JUNOS Software Installation and Upgrade Guide.

Related Topics

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