Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 

Upgrading the Junos OS on a Routing Matrix with a TX Matrix Plus Router

 

When you upgrade the Junos OS on a routing matrix with a TX Matrix Plus router, the new image is loaded onto the TX Matrix Plus router (sfc 0) and distributed to all of the connected routers based on the line-card chassis (LCC) configuration.

Note

Throughout this task description, the term switch-fabric chassis (SFC) refers to the TX Matrix Plus router in the routing matrix, and the term line-card chassis (LCC) refers to a T1600 or T4000 router connected to the SFC in the routing matrix.

Before you begin upgrading the Junos OS on a routing matrix, be sure that the following requirements are met:

  • Sufficient free disk space on each Routing Engine in the routing matrix. To determine the amount of disk space currently available on all Routing Engines in the routing matrix, issue the show system storage operational command.

  • Sufficient DRAM on each Routing Engine in the routing matrix. To determine the amount of DRAM currently available on all the Routing Engines in the routing matrix, issue the show chassis routing-engine operational command.

  • Both Routing Engines on the SFC must have the same model number. Each LCC must contain two Routing Engines. The Routing Engines on all LCCs must have the same model number.

    For more information about which Routing Engines are supported for the TX Matrix Plus router, T1600 router, and T4000 router, see Supported Routing Engines by Chassis.

  • For the TXP-T1600 configuration, you must upgrade the router to Junos OS Release 9.6R2 or later. TX Matrix Plus routers in the TXP-T1600 configuration support 32-bit and 64-bit Junos OS. However, the SFC and LCC must run either 32-bit Junos or 64-bit Junos.

  • Starting with Junos OS Release 13.1, the TX Matrix Plus routers with 3D SIBs (for the TXP-T1600-3D, TXP-T4000-3D, and TXP-Mixed-LCC-3D configurations) support 64-bit Junos OS.

  • The same version of Junos OS must be running on all Routing Engines in the routing matrix.

    Note

    The routing matrix does not operate properly unless all master Routing Engines are running the same version of Junos OS.

    Different versions of the Junos OS can use different message formats that might be incompatible, particularly when graceful Routing Engine switchover (GRES) is enabled. For more information about GRES, see “Understanding Graceful Routing Engine Switchover” and “Configuring Graceful Routing Engine Switchover” in the Junos OS High Availability Library for Routing Devices.

    Because the procedure for upgrading the Junos OS includes switching of the Routing Engine mastership, we recommend that the same version of Junos OS be running on all Routing Engines in the routing matrix. To determine the versions of Junos OS running on the Routing Engines in a routing matrix, issue the show version invoke-on operational command.

Best Practice

By default, the Routing Engine in slot 0 (re0) is the master and the one in slot 1 (re1) is the backup. You can modify the default Routing Engine mastership by including the routing-engine slot-number (master | backup | disabled) statement at the [edit chassis redundancy] hierarchy level. However, 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). Throughout this task description, the master Routing Engine is re0 and the backup Routing Engine is re1 in all routers in the routing matrix.

This topic includes the following tasks:

  1. Logging In to the Master Routing Engine on the TX Matrix Plus Router

  2. Disabling Routing Engine Redundancy and GRES on the Routing Matrix

  3. Installing Junos OS on the Backup Routing Engines

  4. Loading Software on the Backup Routing Engines

  5. Switching Routing Engine Mastership to the Backup Routing Engines

  6. Installing Software on the New Default Master Routing Engines

  7. Loading Software on the New Default Master Routing Engines

  8. Optional: Switching Routing Engine Mastership Back to the Default Master Routing Engines

  9. Restoring the Original Configuration

  10. Backing Up the Routing Engines

Logging In to the Master Routing Engine on the TX Matrix Plus Router

Log in to the master Routing Engine on the SFC.

Note

During the upgrade process, in-band management connections to the routing matrix are lost each time you reboot the system (first, to load the new software onto the backup Routing Engines and later, to load the new software onto the master Routing Engines). Therefore, we recommend that you perform the software upgrade procedure out-of-band, over a direct console connection to the TX Matrix Plus router using Secure Shell (SSH) or Telnet. Connect the system console device to the asynchronous serial port (labeled CONSOLE) on the Control Board (CB) associated with the master Routing Engine.

To log in to the master Routing Engine on the SFC and start the Junos OS CLI:

  1. At a management console attached to the master Routing Engine (re0) on the TX Matrix Plus router, log in to the Junos OS CLI using a root administration account:

    Note

    From the factory, the root administration user account is not associated with a password.

    However, you must add a password to the root administration account before you can successfully commit a configuration.

  2. At the shell prompt (%), start the Junos OS CLI:

Disabling Routing Engine Redundancy and GRES on the Routing Matrix

By default, graceful Routing Engine switchover (GRES) is disabled. To enable GRES on a router, you can include the graceful-switchover statement at the [edit chassis redundancy] hierarchy level:

The procedure for upgrading the Junos OS on a routing matrix with a TX Matrix Plus router includes tasks that entail disruption of traffic processing by the affected Routing Engines:

  • Upgrading the software on all the backup Routing Engines.

  • Switching the Routing Engine mastership to the backup Routing Engines.

  • Upgrading the software on all the master Routing Engines.

  • Switching the Routing Engine mastership back to the master Routing Engines.

If GRES is enabled on any routers in the routing matrix, disable this feature.

To disable GRES on all routers in the routing matrix:

  1. Enter configuration mode:

    Note

    In the example shown in this step, the form of CLI prompt (beginning with either {master} or {backup} and displaying either -re0 or -re1 in the hostname portion of the prompt) indicates that GRES is enabled on that router.

  2. Display the Routing Engine redundancy stanza:

  3. Disable Routing Engine redundancy in the candidate configuration. If GRES is enabled, it is removed with the redundancy stanza:

  4. Verify that the graceful-routing statement has been removed (if it was previously enabled) with the redundancy stanza from the [edit chassis] hierarchy level of the candidate configuration:

    Note

    You can also issue the show system switchover all-chassis operational command to display Routing Engine graceful switchover information

  5. Commit the configuration on all Routing Engines in the routing matrix by using the commit synchronize and-quit statement at the [edit] hierarchy. If the configuration contains no errors and the commit succeeds, exit CLI configuration mode:

Installing Junos OS on the Backup Routing Engines

Install the new version of Junos OS on the backup Routing Engines (re1) of all the routers in the routing matrix while leaving the currently running version of Junos OS running on the master Routing Engines (re0). This allows the master Routing Engines to continue operations, minimizing the disruption to the routing matrix and your network.

To install the new version of Junos OS on all backup Routing Engines in the routing matrix:

  1. At a management console attached to the backup Routing Engine (re1) on the SFC, log in to the Junos OS CLI using a root administration account:

  2. At the shell prompt (%), start the Junos OS CLI:

  3. To install the new Junos OS on the backup Routing Engines (re1) in the routing matrix, issue the request system software add operational command at the SFC, and specify the new Junos OS image file.

    The following example shows sample output for the request system software add command:

    The following example shows a sample output for the request system software add command for a routing matrix with a combination of three T1600 routers and two T4000 routers.

    root@sfc0_alt_re> request system software add /var/tmp/jinstall64-13.1R1.0-domestic-signed.tgz

    For more information on the request system software add command, see the CLI Explorer.

Loading Software on the Backup Routing Engines

To start running the newly installed Junos OS on all the backup Routing Engines in the routing matrix, you must reboot those Routing Engines. The Routing Engines reboot from the boot device on which the software was just installed. Each reboot operation can take between 5 and 10 minutes to complete.

Note

This is your last chance to abort the upgrade of the Junos OS on the backup Routing Engines. If you want to abort the software upgrade, do not reboot the backup Routing Engines.

If you choose to abort the software upgrade, you can remove the new Junos OS package or bundle from the router by issuing the request system software delete operational command and specifying the jinstall command.

To start running the new Junos OS on the backup Routing Engines:

  1. To reboot all the backup Routing Engines (re1), issue the request system reboot operational command at the backup Routing Engine one the SFC. At the warning message and prompt, type yes to allow the command to proceed:

    root@sfc0_alt_ret> request system reboot
    root@sfc0_alt_ret

    All of the backup Routing Engines (re1) in the routing matrix reboot from the boot devices on which the software was just installed, which loads the new Junos OS. Each reboot operation can take between 5 and 10 minutes to complete.

    When the backup Routing Engine on the SFC (sfc0-re1) finishes rebooting, the management console attached to the backup Routing Engine on the TX Matrix Plus router displays the login prompt.

  2. Log in to the SFC backup Routing Engine (sfc0-re1) and issue the show version command to verify the version of the software installed:

    root@sfc0_alt_re> show version

Switching Routing Engine Mastership to the Backup Routing Engines

The new Junos OS is now running on all the backup Routing Engines (re1) in the routing matrix. Next, you must install and load the same new software on the master Routing Engines (re0) of the routing matrix.

While the Junos OS is being upgraded (installed and then loaded), the Routing Engine on which you are performing the software upgrade does not route traffic. Therefore, to minimize disruption to network operation, you need to temporarily switch Routing Engine mastership over to the backup Routing Engines (re1), which are now running the new version of Junos OS.

To switch Routing Engine mastership over to the backup Routing Engines:

  1. At a management console attached to the master Routing Engine (re0) on the SFC, log in to the Junos OS CLI using a root administration account:

  2. At the shell prompt (%), start the Junos OS CLI:

  3. To transfer Routing Engine mastership to the backup Routing Engine (re1) for all routers in the routing matrix, issue the request chassis routing-engine master command with the switch and all-chassis options.

    Caution

    Switching Routing Engine mastership causes traffic to be disrupted.

    At the warning message and prompt, type yes to allow the command to proceed:

    root@sfc0> request chassis routing-engine master switch all-chassis
  4. To verify that the default backup Routing Engines (installed in slot 1) are now operating the elected master Routing Engines, issue the show chassis routing-engine command at the TX Matrix Plus router:

The default backup Routing Engines (re1), which are now running the new version of Junos OS, are temporarily operating as the elected master Routing Engines. This enables you to avoid disruption to network operation while you install and load the new version of Junos OS on the default master Routing Engines (re0) .

Installing Software on the New Default Master Routing Engines

To install the new version of Junos OS on the new default master Routing Engines (re0) in the routing matrix, issue the request system software add operational command at the default master Routing Engine (re0 in this procedure) of the SFC, and specify the new Junos OS image file.

Note

The default backup Routing Engines (re1), which are now running the new version of Junos OS, are operating as the elected master Routing Engines. This enables you to avoid disruption to network operation while you install and load the new version of Junos OS on the default master Routing Engines (re0).

The following example of the request system software add command is truncated, but the command output is similar to the output displayed when you installed the new software on the default backup Routing Engines:

root@sfc0> request system software add /var/tmp/jinstall64-13.1R1.1-domestic-signed.tgz

Loading Software on the New Default Master Routing Engines

To start running the newly installed Junos OS on all the default master Routing Engines in the routing matrix, you must reboot those Routing Engines. The Routing Engines reboot from the boot device on which the software was just installed. Each reboot operation can take between 5 and 10 minutes to complete.

Note

This is your last chance to abort the upgrade of the Junos OS on the default master Routing Engines. If you want to abort the software upgrade, do not reboot the default master Routing Engines. However, aborting the software upgrade procedure at this point this is not recommend, because the default backup routing Engines are already running the new Junos OS.

If you choose to abort the software upgrade, you can remove the new Junos OS package or bundle from the router by issuing the request system software delete operational command and specifying the jinstall command.

To start running the new Junos OS on the default master Routing Engines:

  1. To reboot all the default master Routing Engines (re0), issue the request system reboot operational command at the TX Matrix Plus router.

    At the warning message and prompt, type yes to allow the command to proceed:

    All of the default master Routing Engines (re0) in the routing matrix reboot from the boot devices on which the software was just installed, which loads the new Junos OS. Each reboot operation can take between 5 and 10 minutes to complete.

    When the default master Routing Engine on the TX Matrix Plus router (sfc0-re0) finishes rebooting, the management console attached to the default master Routing Engine on the TX Matrix Plus router displays the login prompt.

    The new version of Junos OS is loaded and running on the new default master Routing Engines

  2. At a management console attached to the new default master Routing Engine (re1) on the SFC, log in to the Junos OS CLI using a root administration account:

  3. Issue the show version command to verify the version of the software installed:

Optional: Switching Routing Engine Mastership Back to the Default Master Routing Engines

The default backup Routing Engines (re1) are still operating as the elected master Routing Engines while the default master Routing Engines (re0) are operating as the elected backup Routing Engines.

To avoid confusion about which Routing Engine in any router is the master and which is the backup, you should switch the Routing Engine mastership assignment back to the original designations (with the re0 Routing Engines operating as the master Routing Engines and the re1 Routing Engines operating as the backup Routing Engines).

Note

Switching Routing Engine mastership causes traffic to be disrupted.

However, if you need to avoid another disruption to traffic while the Routing Engine mastership is switched on all the routers, you can skip this task.

To switch Routing Engine mastership back to the default master Routing Engine (re0) on all routers in the routing matrix:

  1. Transfer Routing Engine mastership to the backup Routing Engine (re1) for all routers in the routing matrix. To do this, issue the request chassis routing-engine master command and specify the switch and all-chassis options.

    At the warning message and prompt, type yes to allow the command to proceed:

  2. Verify that Routing Engine mastership has indeed switched back to the default master Routing Engines (re0) in the routing matrix. To display Routing Engine mastership information, issue the show chassis routing-engine command at the SFC:

Restoring the Original Configuration

After you have installed the new Junos OS and are satisfied that it is running properly on all Routing Engines, restore the routing matrix to the original configuration (that existed before you deleted it at the beginning of this procedure) and then back up the configuration change.

To restore the previous configuration and then create a configuration backup, perform the following steps at the master Routing Engine of the SFC:

  1. Restore the routing matrix configuration that existed before you deleted it at the start of this procedure:

  2. Commit the configuration changes on all Routing Engines, which activates the original configuration, and then return to operational mode:

Backing Up the Routing Engines

Back up the currently running and active file system partitions on each Routing Engine to standby partitions that are not running. Specifically, the root file system (/) is backed up to /altroot, and /config is backed up to /altconfig. The root and /config file systems are on each Routing Engine's flash drive, and the /altroot and /altconfig file systems are on Routing Engine's hard drive.

Caution

After you run the request system snapshot command, you cannot return to the previous version of the software, because the running and backup copies of the software are identical.

To back up the Routing Engines of the routing matrix:

  1. To back up the master Routing Engines (re0) in the routing matrix, issue the request system snapshot command.

    The following example shows sample output for backing up the master Routing Engines:

  2. To transfer Routing Engine mastership back to the default backup Routing Engines, issue the request chassis routing-engine command with the switch and all-chassis options.

    Caution

    Switching Routing Engine mastership causes traffic to be disrupted.

    At the warning message and prompt, type yes to allow the operation to proceed

  3. To back up the backup Routing Engines (re1), issue the request system snapshot operational command at the backup Routing Engine on the TX Matrix Plus router.

    The following examples shows sample command output for backing up the backup Routing Engines: