Supported Platforms
Related Documentation
- T Series
- Overview of a Routing Matrix with a TX Matrix Plus Router
- Roadmap for Configuring the Routing Matrix
- Example Configuration for the Routing Matrix
- Upgrading the Junos OS on the Routing Matrix
- Troubleshooting: Upgrade Failure Due to Insufficient Disk Space
- Troubleshooting: Upgrade Failure Due to Insufficient DRAM
Troubleshooting: Software Upgrade Failure Due to Mixed Software Versions on a Routing Matrix with a TX Matrix Plus Router
Problem
In a routing matrix with a TX Matrix Plus router, a successful upgrade of the Junos OS requires that all Routing Engines of the SFC and connected LCCs are running the same version of software.
If the software versions on the Routing Engines are not aligned, the software upgrade process will return an error.
Cause
Different versions of the Junos OS can have incompatible message formats, particularly if graceful routing engine switchover (GRES) is enabled. Because the steps in the upgrade process include changing Routing Engine mastership, running the same version of software is recommended.
To display the hostname and version information about the software running on all routers in a routing matrix, issue the show version command with the invoke-on all-routing-engines option.
In the following example, a routing matrix consists of a TX Matrix Plus router (sfc0) and two connected T1600 routers (lcc0 and lcc2), with all three routers containing redundant host subsystems. The sample output from the show version command shows that a different version of the Junos OS is installed on the TX Matrix Plus router’s backup Routing Engine (sfc0-re1), while all the other Routing Engines have Junos OS Release 9.6R1.0 installed.
In the following sample output, the backup Routing Engine on the TX Matrix Plus router is running a version of Junos OS that is different from the software on the other Routing Engines:
root@sfc0> show version invoke-on all-routing-engines sfc0-re0: -------------------------------------------------------------------------- Hostname: sfc0 Model: txp JUNOS Base OS boot [9.6-20090713.0] JUNOS Base OS Software Suite [9.6-20090713.0] JUNOS Kernel Software Suite [9.6-20090713.0] JUNOS Crypto Software Suite [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (M/T Common) [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (T-Series) [9.6-20090713.0] JUNOS Online Documentation [9.6-20090713.0] JUNOS Voice Services Container package [9.6-20090713.0] JUNOS Border Gateway Function package [9.6-20090713.0] JUNOS Services AACL Container package [9.6-20090713.0] JUNOS Services LL-PDF Container package [9.6-20090713.0] JUNOS Services Stateful Firewall [9.6-20090713.0] JUNOS AppId Services [9.6-20090713.0] JUNOS IDP Services [9.6-20090713.0] JUNOS Routing Software Suite [9.6-20090713.0] lcc0-re0: -------------------------------------------------------------------------- Hostname: mylcc0 Model: t1600 JUNOS Base OS boot [9.6-20090713.0] JUNOS Base OS Software Suite [9.6-20090713.0] JUNOS Kernel Software Suite [9.6-20090713.0] JUNOS Crypto Software Suite [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (M/T Common) [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (T-Series) [9.6-20090713.0] JUNOS Online Documentation [9.6-20090713.0] JUNOS Voice Services Container package [9.6-20090713.0] JUNOS Border Gateway Function package [9.6-20090713.0] JUNOS Services AACL Container package [9.6-20090713.0] JUNOS Services LL-PDF Container package [9.6-20090713.0] JUNOS Services Stateful Firewall [9.6-20090713.0] JUNOS AppId Services [9.6-20090713.0] JUNOS IDP Services [9.6-20090713.0] JUNOS Routing Software Suite [9.6-20090713.0] lcc2-re0: -------------------------------------------------------------------------- Hostname: mylcc2 Model: t1600 JUNOS Base OS boot [9.6-20090713.0] JUNOS Base OS Software Suite [9.6-20090713.0] JUNOS Kernel Software Suite [9.6-20090713.0] JUNOS Crypto Software Suite [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (M/T Common) [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (T-Series) [9.6-20090713.0] JUNOS Online Documentation [9.6-20090713.0] JUNOS Voice Services Container package [9.6-20090713.0] JUNOS Border Gateway Function package [9.6-20090713.0] JUNOS Services AACL Container package [9.6-20090713.0] JUNOS Services LL-PDF Container package [9.6-20090713.0] JUNOS Services Stateful Firewall [9.6-20090713.0] JUNOS AppId Services [9.6-20090713.0] JUNOS IDP Services [9.6-20090713.0] JUNOS Routing Software Suite [9.6-20090713.0] sfc0-re1: -------------------------------------------------------------------------- Hostname: sfc0_alt_re Model: txp JUNOS Base OS boot [1.1-11111111.1] JUNOS Base OS Software Suite [1.1-11111111.1] JUNOS Kernel Software Suite [1.1-11111111.1] JUNOS Crypto Software Suite [1.1-11111111.1] JUNOS Packet Forwarding Engine Support (M/T Common) [1.1-11111111.1] JUNOS Packet Forwarding Engine Support (T-Series) [1.1-11111111.1] JUNOS Online Documentation [1.1-11111111.1] JUNOS Voice Services Container package [1.1-11111111.1] JUNOS Border Gateway Function package [1.1-11111111.1] JUNOS Services AACL Container package [1.1-11111111.1] JUNOS Services LL-PDF Container package [1.1-11111111.1] JUNOS Services Stateful Firewall [1.1-11111111.1] JUNOS AppId Services [1.1-11111111.1] JUNOS IDP Services [1.1-11111111.1] JUNOS Routing Software Suite [1.1-11111111.1] lcc0-re1: -------------------------------------------------------------------------- Hostname: mylcc0_alt_re Model: t1600 JUNOS Base OS boot [9.6-20090713.0] JUNOS Base OS Software Suite [9.6-20090713.0] JUNOS Kernel Software Suite [9.6-20090713.0] JUNOS Crypto Software Suite [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (M/T Common) [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (T-Series) [9.6-20090713.0] JUNOS Online Documentation [9.6-20090713.0] JUNOS Voice Services Container package [9.6-20090713.0] JUNOS Border Gateway Function package [9.6-20090713.0] JUNOS Services AACL Container package [9.6-20090713.0] JUNOS Services LL-PDF Container package [9.6-20090713.0] JUNOS Services Stateful Firewall [9.6-20090713.0] JUNOS AppId Services [9.6-20090713.0] JUNOS IDP Services [9.6-20090713.0] JUNOS Routing Software Suite [9.6-20090713.0] lcc2-re1: -------------------------------------------------------------------------- Hostname: mylcc2_alt_re Model: t1600 JUNOS Base OS boot [9.6-20090713.0] JUNOS Base OS Software Suite [9.6-20090713.0] JUNOS Kernel Software Suite [9.6-20090713.0] JUNOS Crypto Software Suite [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (M/T Common) [9.6-20090713.0] JUNOS Packet Forwarding Engine Support (T-Series) [9.6-20090713.0] JUNOS Online Documentation [9.6-20090713.0] JUNOS Voice Services Container package [9.6-20090713.0] JUNOS Border Gateway Function package [9.6-20090713.0] JUNOS Services AACL Container package [9.6-20090713.0] JUNOS Services LL-PDF Container package [9.6-20090713.0] JUNOS Services Stateful Firewall [9.6-20090713.0] JUNOS AppId Services [9.6-20090713.0] JUNOS IDP Services [9.6-20090713.0] JUNOS Routing Software Suite [9.6-20090713.0]
Solution
To synchronize the Junos OS versions running on the Routing Engines in a routing matrix, perform the following steps on each Routing Engine that has an incorrect version of Junos OS installed:
- Log in to the Routing Engine that has the incorrect version
of Junos OS installed. To log in to a Routing Engine, issue the request routing-engine login command.
In the example scenario, the backup Routing Engine on the TX Matrix Plus router is running an incorrect version of software. To log in to that Routing Engine, you would enter the following command:
root@sfc0> request routing-engine login other-routing-engine --- JUNOS 1.1-11111111.1 built 1111-11-11 11:11:11 UTC root@sfc0_alt_re>
Note: Throughout the software upgrade procedure instructions, we assume that the master Routing Engines are in slot 0 and the backup Routing Engines are in slot 1, which is the recommended installation. Therefore, we could issue the request routing-engine login command with the re1 option (instead of the other-routing-engine option) and obtain the same results.
- If the appropriate software package or bundle is not already
present on the Routing Engine that has the incorrect version of Junos
OS installed, copy the software onto the Routing Engine.
For more information, see the Junos OS Release Notes and the Installation and Upgrade Guide.
- To install a software package or bundle on the Routing Engine that has the incorrect version of Junos OS installed, use the request system software add command.
- When all the Routing Engines in the routing matrix are running the same version of the Junos OS, try the software upgrade procedure again.
Related Documentation
- T Series
- Overview of a Routing Matrix with a TX Matrix Plus Router
- Roadmap for Configuring the Routing Matrix
- Example Configuration for the Routing Matrix
- Upgrading the Junos OS on the Routing Matrix
- Troubleshooting: Upgrade Failure Due to Insufficient Disk Space
- Troubleshooting: Upgrade Failure Due to Insufficient DRAM
Published: 2013-03-13
Supported Platforms
Related Documentation
- T Series
- Overview of a Routing Matrix with a TX Matrix Plus Router
- Roadmap for Configuring the Routing Matrix
- Example Configuration for the Routing Matrix
- Upgrading the Junos OS on the Routing Matrix
- Troubleshooting: Upgrade Failure Due to Insufficient Disk Space
- Troubleshooting: Upgrade Failure Due to Insufficient DRAM