Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

 
ON THIS PAGE
 

Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2

To upgrade an MX Virtual Chassis SCB or SCBE to SCBE2, perform the following steps:

Note:

SCBE2 does not support smooth upgrade.

Preparing for the SCBE2 Upgrade

To prepare for the SCBE2 upgrade:

  1. Verify that the system is runing Junos OS Release 13.3 or later by issuing the show version command on the primary router.
    Note:

    The SCBE2 is supported only on:

    • Junos OS Release 13.3 or later

    • Network Services Mode: Enhanced-IP

    The latest software ensures a healthy system—that is, a system that comprises Routing Engines, control boards, and FPCs—before the upgrade.

    For information about how to verify and upgrade Junos OS on MX Virtual Chassis configurations, see Example: Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines.

  2. Record the local IP address of each RE in the Virtual Chassis configuration. This information will be necessary to reconfigure the VC member IDs after the upgrade.
  3. Apply a system halt before shutting down the system by issuing the request system halt all-members command on the primary router.

Powering Off the MX Series Router

Note:

After turning off the power supply, wait at least 60 seconds before turning it back on.

To power off the MX Series router:

  1. On the external management device connected to the Routing Engine, issue the request system halt all-members operational mode command. The command shuts down the Routing Engines cleanly, so that their state information is preserved.
  2. Wait until a message appears on the console confirming that the operating system has halted.
  3. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
  4. Move the AC input switch on the chassis above the AC power supply or the DC circuit breaker on each DC power supply faceplate to the off (O) position.

Removing an MX Series Routing Engine from an SCB or SCBE

To remove an MX Series Routing Engine from an SCB or SCBE:

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

Replacing the SCB or SCBE with SCBE2

To replace the existing SCB or SCBE with SCBE2:

  1. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
  2. Remove and replace the offline SCB or SCBE on the router with SCBE2.

Installing the MX Series Routing Engine into an SCBE2

After removing the routing engine from the original SCB or SCBE, you can install it into the new SCBE2. Follow these instructions to install a MX Series Routing Engine into an SCBE2:

  1. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
  2. Ensure that the ejector handles are not in the locked position. If necessary, flip the ejector handles outward.
  3. Place one hand underneath the Routing Engine to support it.
  4. Carefully align the sides of the Routing Engine with the guides inside the opening on the SCBE2.
  5. Slide the Routing Engine into the SCBE2 until you feel resistance and then press the faceplate of the Routing Engine until it engages the connectors.
  6. Press both of the ejector handles inward to seat the Routing Engine.
  7. Tighten the captive screws on the top and bottom of the Routing Engine.
  8. Connect the management device cables to the Routing Engine.

Powering On the MX Series Router

To power on the MX Series router:

  1. Verify that the power supplies are fully inserted in the chassis.
  2. Verify that each AC power cord is securely inserted into its appliance inlet.
  3. Verify that an external management device is connected to one of the Routing Engine ports (AUX, CONSOLE, or ETHERNET).
  4. Turn on the power to the external management device.
  5. Switch on the dedicated customer-site circuit breakers. Follow the ESD and safety instructions for your site.
  6. Attach an ESD grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
  7. Move the AC input switch on the chassis above the AC power supply or the DC circuit breaker on each DC power-supply faceplate to the off (—) position.
  8. Check that the AC or the DC power supply is correctly installed and functioning normally. Verify that the AC OK and DC OK LEDs light steadily, and the PS FAIL LED is not lit.
    Note:

    After a power supply is powered on, it can take up to 60 seconds for status indicators—such as the status LEDs on the power supply and the show chassis command display—to indicate that the power supply is functioning normally. Ignore error indicators that appear during the first 60 seconds.

    If any of the status LEDs indicates that the power supply is not functioning normally, repeat the installation and cabling procedures.

  9. On the external management device connected to the Routing Engine, monitor the startup process to verify that the system has booted properly.
    Note:

    If the system is completely powered off when you power on the power supply, the Routing Engine boots as the power supply completes its startup sequence. Normally, the router boots from the Junos OS on the CompactFlash card.

    After turning on a power supply, wait at least 60 seconds before turning it off.

Configuring Member IDs for the Virtual Chassis

To re-enable the Virtual Chassis, you must configure the member ID on both devices in the Virtual Chassis configuration.

  1. Set the member ID on the router configured as member 0:
  2. Repeat Step 1 to set the member ID on the router configured as member 1.

    The router reboots in preparation for forming the Virtual Chassis. After the reboot, all MPCs remain powered off until the Virtual Chassis port connection is configured.

  3. (Optional) Verify the member ID configuration for member 0.

    For example:

  4. (Optional) Verify the member ID configuration for member 1.

    For example:

    Note:

    At this point in the configuration procedure, all line cards are offline, and the routers are each designated with the Master role because they are not yet interconnected as a fully formed Virtual Chassis. In addition, member 1 remains in Amnesiac state (has no defined configuration) until the Virtual Chassis forms and the configuration is committed.

Configuring Virtual Chassis Ports

Wait until the system is fully booted back up after setting the VC member IDs. VCP ports need to be defined in order for line cards to function properly in the VC configuration.

  1. Log into the console port on member 0 and configure the first Virtual Chassis port that connects to member 1.

    After the Virtual Chassis port is created, it is renamed vcp-slot/pic/port (for example, vcp-2/2/0), and the line card associated with that port comes online. The line cards in the other member router remain offline until the Virtual Chassis forms. Each Virtual Chassis port is dedicated to the task of interconnecting member routers in a Virtual Chassis, and is no longer available for configuration as a standard network port.

  2. Log into the console port on member 1 and configure the first Virtual Chassis port that connects to member 0.
  3. After establishing the VCP link, wait for all line cards and REs to come online. Confirm the availability of ports that will be used as VCP links by issuing the show interface command.
  4. Configure the remaining VCP ports 1 at a time. Wait 30 seconds after setting each VCP port.

Completing the SCBE2 Upgrade

To complete the SCBE2 upgrade procedure:

  1. Verify that the installation is successful and the SCBE2 is online by issuing the show chassis environment cb command:

    Other details, such as, temperature, power, etc are also displayed along with the state.

  2. Verify that the fabric planes come online correctly by issuing the show chassis fabric summary command:
  3. Verify that the backup Routing Engine is back online by issuing the show chassis routing-engine 1 command:
  4. Verify the SCBE2s before you finish by issuing the show chassis hardware command:

    You see that the router now has SCBE2s.

Related Documentation