Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

Upgrading the Software for a Routing Matrix with a TX Matrix Router

 

Before you begin upgrading the software on a TX Matrix Router and to avoid unnecessary network disruption during the upgrade, ensure the following conditions are met.

Note

By default, when you upgrade software on the TX Matrix router (scc), the new image is loaded onto the TX Matrix router (scc) and distributed to all T640 routers (lcc) in the routing matrix.

Throughout this document, we use the term TX Matrix router to refer to the switch-card chassis (SCC) and T640 router to refer to the line-card chassis (LCC).

  • A minimum of free disk space and DRAM on each Routing Engine. The software upgrade will fail on any Routing Engine without the required amount of free disk space and DRAM. To determine the amount of disk space currently available on all Routing Engines of the routing matrix, use the CLI show system storage command. To determine the amount of DRAM currently available on all the Routing Engines in the routing matrix, use the CLI show chassis routing-engine command.

  • The master Routing Engines of the TX Matrix router (scc) and T640 routers (lcc) are all on re0 or are all on re1.

  • The backup Routing Engines of the TX Matrix router (scc) and T640 routers (lcc) are all on re1 or are all on re0.

  • All master Routing Engines in all routers run the same version of software. This is necessary for the routing matrix to operate.

  • All master and backup Routing Engines run the same version of software before beginning the upgrade procedure. Different versions of the Junos OS can have incompatible message formats especially if you turn on GRES. Because the steps in the process include changing mastership, running the same version of software is recommended.

  • The same Routing Engine model is used within a TX Matrix router (scc) and within a T640 router (lcc) of a routing matrix. For example, a routing matrix with an scc using two RE-A-2000s and an lcc using two RE-1600s is supported. However, an scc or an lcc with two different Routing Engine models is not supported. We suggest that all Routing Engines are the same model throughout all routers in the routing matrix. To determine the Routing Engine type, use the CLI show chassis hardware | match routing command.

Note

It is considered best practice to make sure that all master Routing Engines are re0 and all backup Routing Engines are re1 (or vice versa). For the purposes of this document, the master Routing Engine is re0 and the backup Routing Engine is re1.

On the TX Matrix router, perform a Junos OS upgrade on each Routing Engine separately to avoid unnecessary disruption to network operation. Install the new Junos OS Release on the backup Routing Engine (re1) while keeping the currently running software version on the master Routing Engine (re0).

After making sure that the new software version is running correctly on the backup Routing Engine (re1), switch mastership over to re1, install the new software on the new backup Routing Engine (re0) and then revert mastership from re1 back to re0. These changes are propagated to all of the T640 routers in the routing matrix.

To upgrade the Junos OS for a routing matrix, perform the following tasks:

Disabling GRES on the Routing Matrix with a TX Matrix Router

Before upgrading the software on the routing matrix with a TX Matrix router, you must disable graceful Routing Engine switchover (GRES) on all the routers in the routing matrix. To disable GRES, perform the following steps on the TX Matrix router:

  1. Log in to the master Routing Engine’s (scc-re0) console.

  2. Enter the Junos OS CLI configuration mode:

    1. Start the CLI from the shell prompt using the cli command:

    2. Launche configuration mode:

  3. Disable Routing Engine redundancy and verify that the configuration is removed:

  4. Save the configuration change on all Routing Engines in the routing matrix and exit the CLI configuration mode:

Installing Software on All Backup Routing Engines of a Routing Matrix with a TX Matrix Router

Install the new Junos OS Release on all backup Routing Engines (re1) of the TX Matrix router while keeping the currently running software version on the master Routing Engines (re0). This enables the master Routing Engines (re0) to continue operations, minimizing the disruption to the routing matrix with a TX Matrix router and your network.

To install the software on all of the backup Routing Engines (re1), perform the following steps:

  1. Log in to the backup TX Matrix router (re1) Routing Engine's console.

    For more information on logging in to the Routing Engine through the console port, see the administration manual for your particular router.

  2. To upgrade software for all the backup Routing Engines (re1) in the routing matrix, issue the request system software add command. Below is an example of the request system software add command and the output as the software is being added.

    For more information on the request system software add command, see the Junos System Basics and Services Command Reference.

Loading the New Junos OS Version on the Backup Routing Engines of the Routing Matrix with a TX Matrix Router

After you have added the new software version to the backup Routing Engines (re1), reboot the routing matrix with a TX Matrix router to load the new software and verify the version of the software. To reboot the routing matrix, reboot the TX Matrix router which forces all T640 routers to reboot and loads the new software on all backup Routing Engines (re1) in the routing matrix.

  1. Reboot the TX Matrix router to start the new software using the request system reboot command:

    Note

    You must reboot to load the new installation of the Junos OS onto the backup Routing Engine (re1) of the TX Matrix router and to propagate the new image on all backup Routing Engines (re1) of the T640 routers in the routing matrix.

    To abort the installation, do not reboot your system; instead, finish the installation and then issue the request system software delete jinstall command. This is your last chance to stop the installation.

    All the software is loaded on all the backup Routing Engines when you reboot the system. Installation can take about 10 minutes. The backup Routing Engines (re1) then reboot from the boot device on which the software was just installed. When the reboot is complete, the TX Matrix router backup Routing Engine (re1) displays the login prompt.

    While the software is being upgraded, the Routing Engine (re1) on which you are performing the installation is not routing traffic.

  2. Log in to the TX Matrix router backup Routing Engine (re1) and issue the show version command to verify the version of the software installed:

Installing Software on the Master Routing Engines of a Routing Matrix with a TX Matrix Router

Before you install the new software on the master Routing Engines (re0) of the routing matrix with a TX Matrix router, you need to switch mastership over to the backup Routing Engines (re1) to minimize the disruption to network operation.

To change mastership and install the new software version on the new backup Routing Engine (re0), perform the following steps:

  1. On the TX Matrix router, log in to the original master Routing Engine (re0) console port.

    For more information on logging in to the Routing Engine through the console port, see the administration guide for your particular router.

  2. Transfer mastership to the backup Routing Engine (re1) for all routers in the routing matrix using the request chassis routing-engine master switch all-chassis command:

  3. Verify that the backup Routing Engine (slot 1) is now the master Routing Engine on all routers in the routing matrix using the show chassis routing-engine command:

  4. Install the new software package using the request system software add command:

  5. Reboot the Routing Engine (re0) using the request system reboot command:

    Note

    You must reboot to load the new installation of the Junos OS onto the original master Routing Engine (re0) of the TX Matrix router and to propagate the new image on all original master Routing Engines (re0) of the T640 routers in the routing matrix.

    To abort the installation, do not reboot your system; instead, finish the installation and then issue the request system software delete jinstall command. This is your last chance to stop the installation.

    The software is loaded when you reboot the system. Installation can take about 10 minutes. The routers then reboot from the boot device on which the software was just installed. When the reboot is complete, the TX Matrix Routing Engine (re0) displays the login prompt.

    While the software is being upgraded, the Routing Engine (re0) on which you are performing the installation does not route traffic.

  6. Log in and issue the show version command to verify the version of the software installed:

  7. (Optional to avoid another traffic disruption) Transfer routing control back to the original master Routing Engine (re0) using the request chassis routing-engine master switch all-chassis command:

  8. Verify that the master Routing Engine (slot 0) is indeed the master Routing Engine using the show chassis routing-engine command:

Finalizing the Installation for a Routing Engine with a TX Matrix Router

After the software is installed on all Routing Engines, you return the routing matrix with a TX Matrix router back to its original configuration and back up the new installation.

  1. Restore the configuration that existed before you deleted it at the start of this procedure using the configure and rollback commands:

  2. Save the configuration change on all Routing Engines using the commit synchronize and-quit command:

  3. After you have installed the new software and are satisfied that it is successfully running, issue the following commands to back up the new software on both the master (re0) and the backup (re1) Routing Engines:

    The sample output below shows examples of all the commands above.



    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.