Rate and give feedback:  Feedback Received. Thank You!

Rate and give feedback: 

X

This document helped resolve my issue

Yes No

Additional Comments

800 characters remaining

May we contact you if necessary?

Name:  

E-mail: 

Enter a valid Email ID

Need product assistance? Contact Juniper Support

Submit

This site is protected by hCaptcha and its Privacy Policy and Terms of Service apply.

English  

English

Example: Replacing a Routing Engine in a Virtual Chassis Configuration for MX Series 3D Universal Edge Routers

If you remove a Routing Engine from a member router in an MX Series Virtual Chassis for upgrade or repair, you must replace it with a new Routing Engine in the empty Routing Engine slot, and install the same Junos OS release on the new Routing Engine that is running on the other Routing Engines in the Virtual Chassis. The Virtual Chassis remains operational during the replacement procedure.

All four Routing Engines (both Routing Engines in the master router and both Routing Engines in the backup router) in the Virtual Chassis must run the same Junos OS release.

Best Practice: We recommend that you replace a Routing Engine in an MX Series Virtual Chassis configuration during a maintenance window to minimize the possibility of disruption to subscribers.

This example describes how to replace a Routing Engine in an MX Series Virtual Chassis configuration consisting of two MX Series routers, each of which has dual Routing Engines installed:

Requirements

• Junos OS Release 11.4
• 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

1. Remove the Routing Engine that needs repair or upgrade.
2. Return the Routing Engine to Juniper Networks, Inc.
3. Install the new Routing Engine in the empty Routing Engine slot.
4. install the same Junos OS release on the new Routing Engine that is running on the other Routing Engines in the Virtual Chassis.
5. Reboot the new Routing Engine to run the Junos OS software release.

Figure 1 shows the topology of the MX Series Virtual Chassis configuration used in this example. This example replaces the backup RE-S-2000 Routing Engine in slot 1 of the Virtual Chassis backup router, which is an MX480 router named trefoil that is assigned member ID 1. The backup Routing Engine in slot 1 of trefoil is represented in the example as member1-re1.

For redundancy, each of the two member routers is configured with two Virtual Chassis ports.

Figure 1: 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.

Configuration

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

• Removing the Routing Engine
• Returning the Routing Engine to Juniper Networks, Inc.
• Installing the New Routing Engine
• Installing the Junos OS Release on the New Routing Engine

Removing the Routing Engine

Step-by-Step Procedure

• Remove the Routing Engine according to the procedure for your MX Series router.

  • For an MX240 router, see Removing an MX240 Routing Engine in the MX240 3D Universal Edge Router Hardware Guide .
  • For an MX480 router, see Removing an MX480 Routing Engine in the MX480 3D Universal Edge Router Hardware Guide .
  • For an MX960 router, see Removing an MX960 Routing Engine in the MX960 3D Universal Edge Router Hardware Guide .

Returning the Routing Engine to Juniper Networks, Inc.

Step-by-Step Procedure

• Obtain a Return Materials Authorization (RMA) from the Juniper Networks Technical Assistance Center (JTAC) and return the Routing Engine to Juniper Networks, Inc.

  For instructions, see Returning a Hardware Component to Juniper Networks, Inc. in the Hardware Guide for your MX Series router.

Installing the New Routing Engine

Step-by-Step Procedure

• Install the Routing Engine in the empty Routing Engine slot of the member router according to the procedure for your MX Series router.
  • For an MX240 router, see Installing an MX240 Routing Engine in the MX240 3D Universal Edge Router Hardware Guide .
  • For an MX480 router, see Installing an MX480 Routing Engine in the MX480 3D Universal Edge Router Hardware Guide .
  • For an MX960 router, see Installing an MX960 Routing Engine in the MX960 3D Universal Edge Router Hardware Guide .

Installing the Junos OS Release on the New Routing Engine

Step-by-Step Procedure

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

   See Downloading Software in the Installation and Upgrade Guide.

   Note: Make sure you download and install the same Junos OS release that is running on all Routing Engines in the Virtual Chassis.

2. Log in to the console of the new Routing Engine as the user root with no password.
3. From the console, configure a plain-text password for the root (superuser) login.
   {local:member1-re1}[edit system]root# set root-authentication plain-text-passwordNew password: type password hereRetype new password: retype password here
4. From the console, commit the configuration.
   {local:member1-re1}[edit]root# commit synchronize and-quit...member1-re0:configuration check succeedsmember0-re0:commit completemember1-re0:commit completemember1-re1:commit completeExiting configuration mode
5. Use Telnet or SSH to log in to the member router containing the new Routing Engine (trefoil).

   {local:member1-re1}

   user@trefoil>

   Notice that the router name (trefoil) now appears in the command prompt.

6. Install the Junos OS release on the new Routing Engine (member1-re1) from the Virtual Chassis master router (member0-re0).

   {master:member0-re0}

   user@trefoil> request system software add member member-id re1 no-validate reboot package-name force

   For example:

   {master:member0-re0}

   user@trefoil> request system software add member 1 re1 no-validate reboot /var/tmp/jinstall-11.4R1-8-domestic-signed.tgz force

   Pushing bundle to re1...

   This command reboots member1-re1 after the software is added.

Results

After the reboot, the new Routing Engine becomes part of the Virtual Chassis, updates its command prompt to display member1-re1, and copies the appropriate configuration from the Virtual Chassis.

Verification

To verify that the MX Series Virtual Chassis is operating properly with the new Routing Engine, perform these tasks:

• Verifying the Junos OS Installation on the New Routing Engine
• Verifying the Junos OS License Installation on the New Routing Engine
• Switching the Local Mastership in the Member Router to the New Routing Engine

Verifying the Junos OS Installation on the New Routing Engine

Purpose

Verify that you have installed the correct Junos OS release on the new Routing Engine (member1-re1).

Action

Display the hostname, model name, and version information of the Junos OS release running on the new Routing Engine.

{local:member1-re1}

Hostname: trefoil
Model: mx480
. . .
JUNOS Base OS boot [11.4R1-8]
JUNOS Base OS Software Suite [11.4R1-8]
. . .

Meaning

The relevant portion of the show version local command output confirms that Junos OS Release 11.4R1-8 was installed as intended.

Verifying the Junos OS License Installation on the New Routing Engine

Purpose

Verify that the MX Virtual Chassis Redundancy Feature Pack and the required Junos OS feature licenses are properly installed on the member router containing the new Routing Engine.

• Installing Junos OS Licenses on Virtual Chassis Member Routers
• Software Features That Require Licenses on MX Series Routers Only

Action

Display the Junos OS licenses installed on the new Routing Engine.

{local:member1-re1}

License usage: 
                                 Licenses     Licenses    Licenses    Expiry
  Feature name                       used    installed      needed 
  subscriber-accounting                 0            1           0    permanent
  subscriber-authentication             0            1           0    permanent
  subscriber-address-assignment         0            1           0    permanent
  subscriber-vlan                       0            1           0    permanent
  subscriber-ip                         0            1           0    permanent
  scale-subscriber                      0       256000           0    permanent
  scale-l2tp                            0         1000           0    permanent
  scale-mobile-ip                       0         1000           0    permanent
  virtual-chassis                       0            1           0    permanent

Meaning

The show system license command output confirms that the MX Virtual Chassis Redundancy Feature Pack has been installed on this member router. In addition, the necessary Junos OS feature licenses have been installed to enable use of a particular software feature or scaling level.

Switching the Local Mastership in the Member Router to the New Routing Engine

Purpose

Verify that the MX Series Virtual Chassis is operating properly with the new Routing Engine by confirming that the new Routing Engine can take over local mastership from the existing Routing Engine in the Virtual Chassis backup router, trefoil (member 1).

Action

{backup:member1-re0}

{backup:member1-re1}

Preprovisioned Virtual Chassis
Virtual Chassis ID: a5b6.be0c.9525

                                               Mastership           Neighbor List
Member ID       Status   Serial No    Model    priority    Role      ID  Interface

0 (FPC   0- 11) Prsnt    JN10C7135AFC mx240           129  Master     1  vcp-2/2/0
                                                                      1  vcp-2/3/0

1 (FPC  12- 23) Prsnt    JN115D117AFB mx480           129  Backup*    0  vcp-2/0/0
                                                                      0  vcp-5/2/0

Meaning

Issuing the request chassis routing-engine master switch command to initiate the local switchover of the Routing Engines in the Virtual Chassis backup router (trefoil) affects only the roles of the Routing Engines in that member router (member1-re0 and member1-re1), but does not change the global mastership of the Virtual Chassis. The output of the show virtual-chassis status command confirms that after the local switchover, member 0 (gladius) is still the Virtual Chassis master router, and member 1 (trefoil) is still the Virtual Chassis backup router.

Before the local switchover, member1-re0 was the master Routing Engine in the Virtual Chassis backup router (VC-Bm), and member1-re1 (the new Routing Engine) was the standby Routing Engine in the Virtual Chassis backup router (VC-Bs).

After the local switchover, member1-re0 and member1-re1 switch roles. The new Routing Engine, member1-re1, becomes the master Routing Engine in the Virtual Chassis backup router (VC-Bm), and member1-re0 becomes the standby Routing Engine in the Virtual Chassis backup router (VC-Bs).

Table 2 lists the role transitions that occur for each member router and Routing Engine before and after the local switchover of the Routing Engines in trefoil.

Note: The role transitions described in Table 2 apply only when you initiate the local switchover from the Virtual Chassis backup router (VC-B). For information about the role transitions that occur when you initiate the local switchover from the Virtual Chassis master router (VC-M), see Switchover Behavior in a Virtual Chassis.

Best Practice: After you switch the local mastership of the Routing Engines, full synchronization of the Routing Engines takes approximately 30 minutes to complete. To prevent possible loss of subscriber state information due to incomplete synchronization, we recommend that you wait at least 30 minutes before performing another local switchover, global switchover, or graceful Routing Engine switchover in an MX Series Virtual Chassis configuration.