Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

TechLibrary
Navigation

Example: Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 3D Universal Edge Routers

You can upgrade an MX Series Virtual Chassis configuration from Junos OS Release 11.2 to a later release. This upgrade procedure assumes that both member routers in the Virtual Chassis have dual Routing Engines installed.

Note: Make sure all four Routing Engines in the Virtual Chassis (both Routing Engines in the master router and both Routing Engines in the backup router) are running the same Junos OS release.

This example describes how to upgrade Junos OS in a Virtual Chassis consisting of two MX Series routers, each of which has dual Routing Engines:

Requirements

This example uses the following software and hardware and components:

  • Junos OS Release 11.2
  • One MX240 3D Universal Edge Router with dual Routing Engines
  • One MX480 3D Universal Edge Router with dual Routing Engines

See Table 1 for information about the hardware installed in each MX Series router.

Overview and Topology

To upgrade Junos OS in an MX Series Virtual Chassis configuration, you must:

  1. Prepare for the upgrade.
  2. Install the Junos OS software package on each of the four Routing Engines.
  3. Reboot the Routing Engines to run the new Junos OS release.
  4. Re-enable graceful Routing Engine switchover and nonstop active routing.

This example upgrades Junos OS in an MX Series Virtual Chassis configuration that uses the basic topology shown in Figure 1. For redundancy, each member router is configured with two Virtual Chassis ports.

Figure 1: Sample Topology for a Virtual Chassis with Two MX Series Routers

Sample Topology for a Virtual Chassis with Two MX Series Routers

Table 1 shows the hardware and software configuration settings for each MX Series router in the Virtual Chassis.

Table 1: Components of the Sample MX Series Virtual Chassis

Router Name

Hardware

Serial Number

Member ID

Role

Virtual Chassis Ports

Network Port Slot Numbering

gladius

MX240 router with:

  • 60-Gigabit Ethernet Enhanced Queuing MPC
  • 20-port Gigabit Ethernet MIC with SFP
  • 4-port 10-Gigabit Ethernet MIC with XFP
  • Master RE-S-2000 Routing Engine in slot 0 (represented in example as member0-re0)
  • Backup RE-S-2000 Routing Engine in slot 1 (represented in example as member0-re1)

JN10C7135AFC

0

routing-engine (master)

vcp-2/2/0
vcp-2/3/0

FPC 0 – 11

trefoil

MX480 router with:

  • Two 30-Gigabit Ethernet Queuing MPCs
  • Two 20-port Gigabit Ethernet MICs with SFP
  • Two 2-port 10-Gigabit Ethernet MICs with XFP
  • Master RE-S-2000 Routing Engine in slot 0 (represented in example as member1-re0)
  • Backup RE-S-2000 Routing Engine in slot 1 (represented in example as member1-re1)

JN115D117AFB

1

routing-engine (backup)

vcp-2/0/0
vcp-5/2/0

FPC 12 – 23 (offset = 12)

Configuration

To upgrade Junos OS in a Virtual Chassis configuration consisting of two MX Series routers, each with dual Routing Engines, perform these tasks:

Preparing for the Upgrade

Step-by-Step Procedure

To prepare for the upgrade process:

  1. Use FTP or a Web browser to download the Junos OS software package to the master Routing Engine on the Virtual Chassis master router (member0-re0).

    See Downloading Software in the Installation and Upgrade Guide.

  2. Disable nonstop active routing on the master router.
    {master:member0-re0}[edit routing-options]
    user@gladius# delete nonstop-routing
  3. Disable graceful Routing Engine switchover on the master router.
    {master:member0-re0}[edit chassis redundancy]
    user@gladius# delete graceful-switchover
  4. Commit the configuration on the master router.
    {master:member0-re0}[edit system]
    user@gladius# commit synchronize
  5. Exit CLI configuration mode.
    {master:member0-re0}[edit]
    user@gladius# exit

Installing the Junos OS Software Package on Each Routing Engine

Step-by-Step Procedure

Installing the Junos OS software package on each Routing Engine in an MX Series Virtual Chassis prepares the Routing Engines to run the new software release after a reboot. This action is also referred to as arming the Routing Engines.

To install the Junos OS software package on all four Routing Engines from the master router (member0-re0) in the Virtual Chassis:

  1. Install the software package on member0-re0. This command also propagates the software package to member1-re0.
    {master:member0-re0}
    user@gladius> request system software add package-name

    For example:

    {master:member0-re0}
    user@gladius> request system software add jinstall-11.2R1-8-domestic-signed.tgz
  2. Install the software package on member0-re1.
    {master:member0-re0}
    user@gladius> request system software add package-name re1
  3. Install the software package on member1-re1.
    {master:member0-re0}
    user@gladius> request system software add package-name member 1 re1

Results

Display the results of the installation. Verify that the correct software package has been installed on the local master Routing Engine in member 0 (member0-re0) and on the local master Routing Engine in member 1 (member1-re0). 

{master:member0-re0}
user@gladius> show version
member0:
-------------------------------------
Hostname: gladius
Model: mx240
. . .
JUNOS Installation Software [11.2R1-8]


member1:
-------------------------------------
Hostname: trefoil
Model: mx480
. . .
JUNOS Installation Software [11.2R1-8]

Rebooting the Routing Engines to Run the New Junos OS Release

Step-by-Step Procedure

To reboot each of the four Routing Engines in an MX Series Virtual Chassis from the Virtual Chassis master router (member0-re0):

  1. Reboot member1-re1.
    {master:member0-re0}
    user@gladius> request system reboot member 1 other-routing-engine
  2. Reboot member0-re1.
    {master:member0-re0}
    user@gladius> request system reboot other-routing-engine
  3. Reboot both master Routing Engines (member0-re0 and member1-re0).
    {master:member0-re0}
    user@gladius> request system reboot all-members

    This command reboots all line cards in member 0 (gladius) and member 1 (trefoil) to use the new Junos OS release. A traffic disruption occurs until all line cards are back online and the Virtual Chassis re-forms.

Re-enabling Graceful Routing Engine Switchover and Nonstop Active Routing

Step-by-Step Procedure

After upgrading the Junos OS release, you need to re-enable graceful Routing Engine switchover and nonstop active routing for the Virtual Chassis.

To re-enable graceful Routing Engine switchover and nonstop active routing from the Virtual Chassis master router (member0-re0):

  1. In the console window on member 0 (gladius), enable graceful Routing Engine switchover on the master router.
    {master:member0-re0}[edit chassis redundancy]
    user@gladius# set graceful-switchover
  2. Re-enable nonstop active routing on the master router.
    {master:member0-re0}[edit routing-options]
    user@gladius# set nonstop-routing
  3. Commit the configuration on the master router.
    {master:member0-re0}[edit system]
    user@gladius# commit synchronize
 

Related Documentation

 

Published: 2013-02-11

Previous Page Next Page