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

Recovering a Routing Engine in a Member Switch in an EX8200 Virtual Chassis

Problem

A single Routing Engine in a member switch within an EX8200 Virtual Chassis might not boot. Some typical reasons for Routing Engine boot failure include uninstalled or corrupted software.

When the boot failure occurs, the member switch remains in the u-boot prompt (=>) or in the loader prompt (loader>).

This procedure can be used to update software on a single Routing Engine of a member switch in an EX8200 Virtual Chassis whenever that Routing Engine is in the loader or u-boot prompt. It is especially useful after a Routing Engine in a member switch within an EX8200 Virtual Chassis is replaced and the software on the new Routing Engine has not been installed.

You can use this recovery installation procedure to install Junos OS to the Routing Engine of the member switch only without disrupting all traffic to the EX8200 Virtual Chassis by updating the software for the other EX8200 Virtual Chassis devices.

Cause

Solution

You can resolve a boot failure on the Routing Engine by downloading a Junos OS image for an EX8200 switch into the /tftpboot directory on a directly-connected XRE200 External Routing Engine. You can then boot the switch using the downloaded Junos OS image.

To upgrade the software on the Routing Engine:

1. Log in to the master XRE200 External Routing Engine.
2. Copy a Junos OS image for an EX8200 switch into the /tftpboot directory on the external Routing Engine. The Junos OS image for the EX8200 switch should have the same release as the software currently running on the Virtual Chassis.

   Note: You can download a Junos OS image for a standalone EX8200 switch that is independent of the Junos OS image for the XRE200 External Routing Engine as long as the image that you download has the same release as the software currently running on the Virtual Chassis.

   user@external-routing-engine> file copy source /tftpboot

   where source represents the name and location of the Junos OS image; for example, tftp://192.17.1.28/junos/jinstall-ex-8200-11.4R1.5-domestic-signed.tgz

3. Log in to the Routing Engine of the member switch in the loader or u-boot prompt.
4. From the loader or u-boot prompt, set the IP address to any address in the 128.0.0.0/24 network, set the gateway IP address to 128.0.0.1 (the external Routing Engine), and set the network mask to 255.255.254.0. Save the configuration.

   From the loader prompt:

   loader> set ipaddr=128.0.0.10loader> set gatewayip=128.0.0.1loader> set netmask=255.255.254.0loader> save

   Note: You can enter the show command in the loader> prompt to confirm these changed settings.

   From the u-boot prompt:

   => setenv ipaddr 128.0.0.10=> setenv gatewayip 128.0.0.1=> setenv netmask 255.255.254.0=> save
5. (u-boot prompt only) Access the loader prompt by booting the switch and pressing the Spacebar during the boot:
   => boot[Space Bar]loader>
6. Install the Junos OS image:
   loader> install tftp://128.0.0.1/image-name

   where image-name represents the name of the Junos OS image copied to the /tftpboot directory in step 2; for example, jinstall-ex-8200-11.4R1.5-domestic-signed.tgz.

7. Configure the switch into Virtual Chassis mode, if necessary:

   Note: This step is only necessary if the switch fails to join the Virtual Chassis. An EX8200 member switch joins the Virtual Chassis if the Virtual Chassis mode has been enabled.

   user@switch> set chassis virtual-chassis

   A reboot of the member switch is required to change the Virtual Chassis mode. You can reboot the switch by answering the prompts after entering the set chassis virtual-chassis command or by entering the request system reboot command.