Help us improve your experience.

Let us know what you think.

Do you have time for a two-minute survey?

header-navigation

Solutions

Featured solutions AI Campus and branch Data center WAN Security Service provider Cloud operator Industries
Campus and Branch

Welcome to the NOW Way to Wi-Fi

Take your networking performance to new heights with a modern, cloud-native, AI-Native architecture. Only Juniper can help you unleash the full potential of Wi-Fi 7 with our AI-Native platform for innovation.
Prepare for liftoff
Business intelligence analyst dashboard on virtual screen. Big data Graphs Charts.

AI Data Center Networking

Juniper’s AI data center solution is a quick way to deploy high performing AI training and inference networks that are the most flexible to design and easiest to manage with limited IT resources.
Find out more
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Zero trust security

Ops4AI Lab

Visit our lab in Sunnyvale, CA and see our AI data center solution for yourself. You can try out your own model’s functionality and performance, too.
Visit the lab
Enterprise AI-Native Networking

Enterprise AI‑Native Routing

Juniper's Ai-Native routing solution delivers robust 400GbE and 800GbE capabilities for unmatched performance, reliability, and sustainability at scale.
Explore enterprise routing
Higher Education

Shaping Student Experiences: The NOW Way to Build Higher Education Networks

Juniper Networks CIO Sharon Mandell and a virtual summit of C-level IT leaders from prestigious institutions discuss ongoing efforts to support digital transformation on campus.
Watch now
Hand on tablet with healthcare overlay of graphics

Security in healthcare

In this IDC Spotlight report, discover how AI networking can automate and strengthen a healthcare ecosystem to defeat criminals and prevent loss. 
Gain insights into ecosystem security
Retail

The Future of In-Store Technologies

Retail experts Kevin McCartan, Senior IT Service Delivery Engineer at Musgrave; Jack Stratten of Insider Trends; and Christian Gilby, Senior Director of Product Marketing at Juniper Networks, discuss customer experiences.
See the future

Products

Wireless access Wired access SD-WAN / SASE Routing and switching Security Mist AI™ Management software Network operating system Blueprint for AI-Native Acceleration Optics
  • Operations
ACX7020 router

Juniper ACX7020 Cloud Metro Access Router

Legacy networks simply cannot meet the demands of today’s rapidly evolving metro landscape. Unlock a new generation of highly scalable architectures and automated operations with the Juniper ACX7020. 
Learn more
EX4000 Ethernet Switch

Next-gen AI-Native EX4000 line of switches

Lack of AI innovation from your current networking vendor slowing you down? Embrace Juniper’s cloud-native, AI-Native access switches that support every level and layer, across nearly every deployment.
Discover how
The Q and AI text with an image of Bob Friday and Kedar Dhuru.

The Q&AI Podcast

Delivering practical solutions and enriching discussions, this podcast series is a vital resource for those seeking an in-depth exploration of AI's transformative potential.
Catch the latest episode

Services

Services
Services AI Care

Juniper AI Care Services Revolutionize Your Service Experience

Our industry-first AI-Native services couple AIOps with our deep expertise across the full network life cycle. You can move from reactive response to proactive insight and action.
Explore AI Care Services
Services AI Data Center

Juniper AI Data Center Deployment Services Optimize Your AI Model Runs

We use our expertise and validated designs to help design, deploy, validate and tune networks, including GPUs and storage, to get the most from your AI infrastructure operation.
Learn about AI Data Center Deployment Services

Partners

Partners

Support and Documentation

Support and Documentation

Learn

About Juniper Training Events The Feed Resources Technology learning topics Thought leadership and insights
Audience raising hands up while businessman is speaking in training at the office.

Juniper certification and training news

See the latest
Ringing of the bell

All global events

See the latest
AI-native-now

AI-Native NOW event series

Register now
Juniper's Christina Hendrix at the head of a conference table. With the text "The NOW Way to Network" overlayed, with "NOW" emphasizing the "O" in green color.

The NOW Way to Network

Watch the video series
AI Native Now

Executive insights

Dive deep with leading experts and thought leaders on all the topics that matter most to your business, from AI to network security to driving rapid, relevant transformation for your business.
Learn more
A keynote speaker giving a presentation at a conference. There are dozens of people sitting around them. The presentation is displayed via projector on all the walls in the room.

Leadership voices

Juniper Networks’ leaders operate on the front lines of creating the network of the future. Take a look around to see what’s on their minds.
Watch now
Bob Friday and Jessica Garrison speaking

Bob Friday Talks

Join Bob as he ventures into all the knowns -- and -- unknowns -- of AI.
Catch the latest episode
Documentation
Menu
License Guide
Quick Starts
Validated Designs
Home Documentation MX240 Universal Routing Platform Hardware Guide Maintaining, Installing and Replacing Components

MX240 Universal Routing Platform Hardware Guide

keyboard_arrow_up
close
keyboard_arrow_left
MX240 Universal Routing Platform Hardware Guide
Table of Contents Expand all
list Table of Contents
file_download PDF
{ "lLangCode": "en", "lName": "English", "lCountryCode": "us", "transcode": "en_US" }
English
ON THIS PAGE
keyboard_arrow_right

Maintaining MX240 Switch Control Boards

date_range 19-Mar-25
arrow_backward
arrow_forward

Replacing an MX240 SCB-MX

CAUTION:

Before you replace the Switch Control Board, you must take the host subsystem offline. If there is only one host subsystem, taking the host subsystem offline shuts down the router.

Before replacing an SCB-MX, read the guidelines in Operating and Positioning the MX240 SCB Ejectors.

Removing an MX240 SCB-MX

CAUTION:

Before removing the Switch Control Board, ensure that you know how to operate the ejector handles properly to avoid damage to the equipment.

Note:

You can remove the Switch Control Board and Routing Engine as a unit, or remove the Routing Engine separately.

  1. Take the host subsystem offline.
  2. Place an electrostatic bag or antistatic mat on a flat, stable surface.
  3. Attach an ESD grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
  4. Rotate the ejector handles simultaneously counterclockwise to unseat the Switch Control Board.
  5. Grasp the ejector handles, and slide the Switch Control Board about halfway out of the chassis.
  6. Place one hand underneath the Switch Control Board to support it, and slide it completely out of the chassis.
  7. Place the Switch Control Board on the antistatic mat.
  8. If you are not replacing the Switch Control Board now, install a blank panel over the empty slot.
Figure 1: Removing the Switch Control Board from an MX240 RouterRemoving the Switch Control Board from an MX240 Router

Installing an MX240 Switch Control Board

To install a Switch Control Board (see Figure 2):

  1. Attach an ESD grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
  2. Carefully align the sides of the Switch Control Board with the guides inside the chassis.
  3. Slide the Switch Control Board into the chassis until you feel resistance, carefully ensuring that it is correctly aligned.
  4. Grasp both ejector handles, and rotate them simultaneously clockwise until the Switch Control Board is fully seated.
  5. Place the ejector handles in the proper position, horizontally and toward the center of the board.
    Figure 2: Installing a Switch Control Board in the MX480Installing a Switch Control Board in the MX480
  6. Check the LEDs on the Switch Control Board faceplate to verify that it is functioning normally.

    • The green OK/FAIL LED should light steadily a few minutes after the Switch Control Board is installed.

    • If the OK/FAIL LED is red, remove and install the Switch Control Board again. If the OK/FAIL LED still lights steadily, the Switch Control Board is not functioning properly. Contact your customer support representative.

  7. Check the status of the Switch Control Board using the show chassis environment cb command:
    content_copy zoom_out_map
    user@host> show chassis environment cb
 CB 0 status:
State                      Online Master
  Temperature                25 degrees C / 77 degrees F
  Power 1
    1.2 V                     1198 mV
    1.5 V                     1508 mV
    1.8 V                     1830 mV
    2.5 V                     5059 mV
    3.3 V                     6593 mV
    5.0 V                     5111 mV
    12.0 V                   12181 mV
    1.25 V                    1250 mV
    3.3 V SM3                 6587 mV
    5 V RE                    5078 mV
    12 V RE                  12026 mV
  Power 2
    11.3 V bias PEM          11253 mV
    4.6 V bias MidPlane       4827 mV
    11.3 V bias FPD          11408 mV
    11.3 V bias POE 0        11446 mV
    11.3 V bias POE 1        11408 mV
  Bus Revision               6
  FPGA Revision              0
CB 1 status:
  State                      Online Standby
  Temperature                26 degrees C / 78 degrees F
  Power 1
    1.2 V                     1211 mV
    1.5 V                     1517 mV
    1.8 V                     1817 mV
    2.5 V                     2507 mV
    3.3 V                     3312 mV
    5.0 V                     5136 mV
    12.0 V                   12142 mV
    1.25 V                    1260 mV
    3.3 V SM3                 3306 mV
    5 V RE                    5085 mV
    12 V RE                  11968 mV
  Power 2
    11.3 V bias PEM          11369 mV
    4.6 V bias MidPlane       4814 mV
    11.3 V bias FPD          11427 mV
    11.3 V bias POE 0        11350 mV
    11.3 V bias POE 1        11330 mV
  Bus Revision               39
  FPGA Revision              1

Upgrading an MX240 to Use the SCBE-MX

Prepare for the SCB-MX Upgrade

Note:

Do not make other changes to the CLI during the entire upgrade process. To insure you don’t inadvertently change the CLI, open a telnet session to the primary RE CLI operational mode and issue the configure exclusive command. This command locks the configuration procedure.

Tip:

To prevent traffic loss during the upgrade process, we recommend that you operate the line cards at 50% line rate. This 50% limit must be maintained per PFE on each line card.

To prepare the MX240 router for the Enhanced MX Switch Control Board (SCBE-MX) upgrade:

  1. Verify that the system runs Junos OS Release 11.4 or later by issuing the show version command on the primary router:
    content_copy zoom_out_map
    user@host> show version
Model: mx240 
Junos Base OS Software Suite [11.4-20110530];
    Note:

    The SCBE-MX is supported only in Junos OS Release 11.4 or later.

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

  2. Verify that SCB-MX boards are installed:
    content_copy zoom_out_map
    user@host> show chassis hardware
Item 	Version 	Part Number	Serial Number	Description 
CB0 	REV 07	710-021523	ABBC8281		MX SCB
CB1 	REV 07	710-021523	ABBC8323		MX SCB

    SCB-MX details are displayed as above, along with other hardware components. The MX240 router has only two SCB-MXs, and each SCB-MX has four fabric planes.

  3. Establish console connections to both Routing Engines. You can use a telnet session to connect to the router console by issuing the <router name>-con command. For example, if the router name is juniper, you can connect to RE0 and RE1 consoles by issuing the telnet juniper-con and telnet juniper1-con commands.
  4. Ensure that graceful switchover (GRES), commit synchronize (required for nonstop routing), and nonstop routing (NSR) are enabled or configured by running the set chassis redundancy graceful-switchover, set system commit synchronize, set routing-options nonstop-routing commands.
    Note:

    These commands are mandatory for this upgrade and may be removed, if desired, after the upgrade.

  5. Set the upgrade flag on, and start the SCB-MX upgrade by issuing the set chassis state cb-upgrade on command:
    content_copy zoom_out_map
    user@host# set chassis state cb-upgrade on
user@host# configure
user@host# commit
  6. Determine the order to replace the existing SCB-MXs with upgraded ones. SCB 0 is associated with RE0 and SCB1 is associated with RE1.
    Note:

    Do not add or remove any router hardware during the upgrade procedure.

Upgrade the MX240 SCB-MX in the Backup Routing Engine

Tip:

The MX240 has two slots for an SCB-MX: SCB 0 and SCB 1. These correspond to RE0 and RE1, respectively, where SCB 1 is the first SCB-MX.

To upgrade the SCB-MX in the backup Routing Engine (SCB 1):

  1. Power down the backup Routing Engine from the primary Routing Engine by issuing the request system power-off other-routing-engine command.
  2. Verify that the Routing Engine is powered down by issuing the show chassis routing-engine 1 command. The slot of the Routing Engine may be 0 or 1, and is shown as 1 in this example:
    content_copy zoom_out_map
    user@host> show chassis routing-engine 1
Routing Engine Status:
Slot 1:
Current State 	Present

    Verify that the Current State is Present, which indicates that the Routing Engine is offline.

  3. Take the fabric plane offline by issuing the request chassis fabric plane 4 offline command. SCB1 has four fabric planes numbered, 4, 5, 6, and 7.
  4. Verify that the fabric plane is offline:
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane		State		Uptime
  4		Offline
  5		Online		1 hour, 15 minutes, 35 seconds

    Verify that the 'State’ of Plane 4 is Offline.

  5. Take the remaining fabric planes offline by issuing the request chassis fabric plane 5/6/7 offline command—that is, by changing the fabric plane number each time. Verify that the fabric planes are offline by issuing the command given in Step 2.
  6. Take the SCB-MX in slot 1 offline by issuing the request chassis cb offline slot 1 command.
  7. Verify that the control SCB-MX is offline:
    content_copy zoom_out_map
    user@host> show chassis environment cb 1
CB 1 status:
State		Offline
Power 1		Disabled
Power 2		Disabled
  8. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
  9. Remove and replace SCB 1 on the router with the SCBE-MX. Use the replacement procedure described in Replacing an MX240 SCB-MX.
  10. Verify that the installation is successful and the SCBE-MX is online:
    content_copy zoom_out_map
    user@host> show chassis environment cb 1
CB 1 status
State		Online
Temperature	30 degrees C / 86 degrees F

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

  11. Verify that the fabric planes come online correctly:
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane	 State	Uptime
4	Online	2 minutes, 25 seconds	
5	Online	2 minutes, 15 seconds
6	Online	2 minutes, 3 seconds
7	Online	1 minute, 49 seconds
  12. Verify that the backup Routing Engine is back online:
    content_copy zoom_out_map
    user@host> show chassis routing-engine 1
Routing Engine Status:
Slot 1:
Current State		Backup
  13. Verify the alarms:
    content_copy zoom_out_map
    user@host> show chassis alarms
Alarm Time 		Class	Description
2011-06-01 13:26:56 EDT	Major	CB fabrics are of mixed types

    Because only one SCB-MX has been upgraded, the alarm indicates that the SCB-MXs are of mixed type. This alarm is cleared after all the control boards are upgraded.

Upgrade the MX240 SCB-MX in the Primary Routing Engine

  1. Issue the request chassis routing-engine master switch command so that the backup RE becomes the primary RE. This ensures a Graceful RE Switchover (GRES) to gracefully switch between the primary and backup Routing Engines.
  2. Log in to the new primary Routing Engine after the switchover.
  3. Switch the configuration mode to ensure that you are still in configure exclusive mode by issuing the exit command and then the configure exclusive command, from the old primary Routing Engine.
  4. Log in to the current primary Routing Engine again and issue the configure exclusive command.
  5. Issue the request system power-off other-routing-engine command to power down the backup Routing Engine from the primary Routing Engine.
  6. Issue the show chassis routing-engine 0 command to verify that the Routing Engine is powered down.
    content_copy zoom_out_map
    user@host> show chassis routing-engine 0
Routing Engine Status:
Slot 0:
Current State 	Present

    Verify that the Current State is Present, which indicates that the Routing Engine is offline.

  7. Issue the request chassis fabric plane 0 offline command to take the first fabric plane of the backup Routing Engine offline. SCB 0 has four fabric planes numbered, 0, 1, 2, and 3.
  8. Issue the show chassis fabric summary command to verify that the fabric plane is offline.
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane	State	Uptime
0	Offline
1 	Online 3 minutes, 45 seconds

    Verify that the State of plane 0 is Offline.

  9. Take the remaining fabric planes offline by issuing the request chassis fabric plane 1/2/3 offline command—that is, by changing the fabric plane number each time.
  10. Issue the configure exclusive command to verify that the fabric planes are offline.
  11. Issue the request chassis cb offline slot 0 command to take the SCB-MX in slot 0 offline.
  12. Issue the show chassis environment cb 0 command to verify that the SCB is offline.
    content_copy zoom_out_map
    user@host> show chassis environment cb 0
CB 0 status:
State		Offline
Power 1		Disabled
Power 2		Disabled
  13. Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
  14. Remove and replace the offline SCB-MX on the Routing Engine with the SCBE-MX. Use the replacement procedure described in Replacing an MX240 SCB-MX.
  15. Issue the show chassis environment cb 0 command to verify that the installation is successful and SCB 0 is online:
    content_copy zoom_out_map
    user@host> show chassis environment cb 0
CB 0 status
State		Online
Temperature	30 degrees C / 86 degrees F

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

  16. Issue the show chassis fabric summary command to verify that the fabric planes come online correctly:
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane	State	Uptime
0	Online	2 minutes, 5 seconds	
1	Online	1 minute, 55 seconds
2	Online	1 minute, 43 seconds
3	Online	1 minute, 33 seconds
  17. Issue the show chassis routing-engine 0 command to verify that the backup Routing Engine is back online:
    content_copy zoom_out_map
    user@host> show chassis routing-engine 0
Routing Engine Status:
Slot 0:
Current State		Backup
  18. Issue the show chassis alarms command to verify the alarms:
    content_copy zoom_out_map
    user@host> show chassis alarms
Alarm Time 	Class	Description
2011-06-01 13:26:56 EDT Major CB fabric links require upgrade/training
2011-06-01 12:10:41 EDT Major Require a fan tray upgrade

    The major alarm has changed from CB fabrics are of mixed types to CB fabric links require upgrade/training, as a SCB-MX requires training to change the link speed from 3G to 6G for the SCBE-MX. This alarm is displayed until the 3G to 6G link transition is completed.

Complete the SCB-MX Upgrade

  1. Check to see if there are any MPCs running at 3G instead of 6G:
    content_copy zoom_out_map
    user@host> request chassis fabric upgrade-bandwidth info
Slot	State
0	Upgrade not supported
1	Needs upgrade
2	Empty
3	Empty	
4	Empty
5	Empty

    In this example, the results indicate that slot 0 does not support the upgrade and slot 1 needs to be upgraded.

  2. Issue the request chassis fabric upgrade-bandwidth fpc all command to upgrade the bandwidth of all MPCs. If you want to control the MPC line card upgrade, go to Step 3.
    CAUTION:

    Use this command only if you are not concerned with the slot upgrade order or if only one old MPC is present in the chassis. Running this command may result in a loss of traffic across the MPC. Using this method may increase the traffic loss, because it does not consider any redundancy or graceful switchover strategies that you may have configured on the system.

  3. Issue the request chassis fabric upgrade-bandwidth fpc slot 1 command to upgrade the MPC in slot 1.
  4. Verify that the MPC is upgraded:
    content_copy zoom_out_map
    user@host> request chassis fabric upgrade-bandwidth info
Slot	State
0	Upgrade not supported
1	Upgraded
2	Empty
  5. Verify the state of the fabric planes for all MPCs:
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane	State	Uptime
0	Spare	21 seconds
1	Spare	12 seconds
2	Online   12 minutes
3	Online   12 minutes	
4	Online   30 minutes
5	Online   30 minutes
  6. Verify the state of the MPCs:
    content_copy zoom_out_map
    user@host> show chassis fabric fpcs
FPC 1
PFE #0
	Plane 0: Links ok
	Plane 1: Links ok
	Plane 2: Plane enabled
	Plane 3: Plane enabled
	Plane 4: Plane enabled
	Plane 5: Plane enabled
PFE #1
	Plane 0: Links ok
	Plane 1: Links ok
	Plane 2: Plane enabled
	Plane 3: Plane enabled
	Plane 4: Plane enabled
	Plane 5: Plane enabled
PFE #2
	Plane 0: Links ok
	Plane 1: Links ok
	Plane 2: Plane enabled
	Plane 3: Plane enabled
	Plane 4: Plane enabled
	Plane 5: Plane enabled
PFE #3
	Plane 0: Links ok
	Plane 1: Links ok
	Plane 2: Plane enabled
	Plane 3: Plane enabled
	Plane 4: Plane enabled
	Plane 5: Plane enabled

    Fabric plane details of all MPCs are also displayed.

  7. Verify if the show chassis fabric summary command output shows fabric planes in the 'check' state. This indicates that the fabric plane has an error. You can try to recover the fabric plane to normal operation by issuing the request chassis fabric plane <#> offline command, followed by the request chassis fabric plane <#> online command, where <#> equals the fabric plane in error.
    Note:

    After you issue the request chassis fabric plane <#> offline and request chassis fabric plane <#> online commands, issue the show chassis fabric summary command to verify that the fabric plane errors are rectified and to verify the current state of the fabric planes.

  8. Verify if any major alarms are displayed:
    content_copy zoom_out_map
    user@host> show chassis alarms
Alarm Time 		Class	Description
2011-06-01 13:37:43 EDT	Minor	Require a fan tray upgrade
2011-06-01 13:37:26 EDT	Minor	Backup RE Active

    In this example, the major alarms are no longer displayed, and the upgrade is successfully completed.

  9. Disable the upgrade configuration by issuing the set chassis state cb-upgrade off command and then the commit command.
  10. You can delete that command by issuing the delete chassis state cb-upgrade command and then the commit command.
  11. Verify the SCBE-MXs before you finish by issuing the show chassis hardware command:
    content_copy zoom_out_map
    user@host> show chassis hardware
Item 	Version 	Part Number	Serial Number	Description 
CB0 	REV 02	750-031391	YE8505		Enhanced MX SCB
CB1 	REV 07	710-031391	YL6769		Enhanced MX SCB

See Also

Upgrading an MX240 to Use the SCBE2-MX

Consider the following scenarios when upgrading an MX240 SCB-MX or SCBE-MX to use the SCBE2-MX:

Scenario 1: SCBE2-MX; Routing Engine with Junos OS Release 13.3R1 or later installed.

  • Replace the SCB-MXs. Ensure that you replace the SCB-MXs at the same time.

  • Ensure that Enhanced IP or Enhanced Ethernet Network Services mode is configured before you power on the router.

Scenario 2: SCB-MX or SCBE-MX; existing Routing Engine with a Junos OS Release 13.3R1 or earlier installed.

  • Upgrade the Routing Engine (RE0 and RE1) software to Junos OS Release 13.3 or later.

  • Configure Enhanced IP or Enhanced Ethernet Network Services mode.

  • Replace the SCB-MXs. Ensure that you replace the SCB-MXs at the same time.

Scenario 3: Failed SCB-MX or SCBE-MX; Routing Engine with a Junos OS Release 13.3R1 or earlier installed.

  • Upgrade the software on the Routing Engine hosting the failed SCB-MX or SCBE-MX with Junos OS Release 13.3R1 or later.

  • Replace the SCB-MXs. Ensure that you replace the SCB-MXs at the same time.

  • Upgrade the software on the Routing Engine hosting the SCBE2-MX with Junos OS Release 13.3R1 or later.

  • Configure Enhanced IP or Enhanced Ethernet Network Services mode.

To upgrade the MX240 to use the SCBE2-MX, perform the following steps:

Note:

The SCBE2-MX does not support smooth upgrade.

Prepare the MX240 Router for the SCBE2-MX Upgrade

Verify that the system runs Junos OS Release 13.3 or later by issuing the show version command on the primary router.
content_copy zoom_out_map
user@host> show version
Model: mx240 
Junos Base OS Software Suite [13.3-yyyymmdd];
...
Note:

The SCBE2-MX is supported only on:

  • Junos OS Release 13.3R1 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 the Junos OS, see the Junos OS Installation and Upgrade Guide.

Power Off the MX240 Router

Note:

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

  1. On the external management device connected to the Routing Engine, issue the request system halt both-routing-engines operational mode command. This command shuts down the Routing Engines cleanly, so that their state information is preserved. (If the router contains only one Routing Engine, issue the request system halt command.)
    content_copy zoom_out_map
    user@host> request system halt both-routing-engines
  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.

Remove the MX240 Routing Engine

  1. Remove the cables connected to the Routing Engine.
  2. Place an electrostatic bag or antistatic mat on a flat, stable surface.
  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. Loosen the captive screws on the top and bottom of the Routing Engine.
  5. Flip the ejector handles outward to unseat the Routing Engine.
  6. Grasp the Routing Engine by the ejector handles, and slide it about halfway out of the chassis.
  7. Place one hand underneath the Routing Engine to support it, and slide it completely out of the chassis.
  8. Place the Routing Engine on the antistatic mat.

Install the MX240 Routing Engine into the SCBE2-MX

  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-MX.
  5. Slide the Routing Engine into the SCBE2-MX 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.

Power On the MX240 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.

Complete the SCBE2-MX Upgrade

  1. Verify that the installation is successful and the SCBE2-MX is online:
    content_copy zoom_out_map
    user@host> show chassis environment cb 0
CB 0 status
State		Online
Temperature	30 degrees C / 86 degrees F
...
user@host> show chassis environment cb 1
CB 1 status
State		Online
Temperature	30 degrees C / 86 degrees F
...

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

  2. Verify that the fabric planes come online correctly:
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane   State    Uptime
 0      Online   2 days, 19 hours, 10 minutes, 9 seconds
 1      Online   2 days, 19 hours, 10 minutes, 9 seconds
...
  3. Verify that the backup Routing Engine is back online:
    content_copy zoom_out_map
    user@host> show chassis routing-engine 1
Routing Engine Status:
Slot 1:
Current State		Backup
...
  4. Verify the SCBE2-MXs are installed:
    content_copy zoom_out_map
    user@host> show chassis hardware
Hardware inventory:
Item             Version  Part number  Serial number     Description
CB 0             REV 08   750-048307   CABC9829          Enhanced MX SCB 2
CB 1             REV 08   750-048307   CABC9828          Enhanced MX SCB 2
...

Upgrading an MX240, MX480, or MX960 Router to Use the SCBE3-MX

Upgrade the Routing Engine

Note: Ensure that you power down the router before you begin the upgrade from SCBE2 to SCBE3. See Powering off the MX series router for instructions on powering down the router.

If you are upgrading to the SCBE3-MX from an SCBE2-MX or older SCB, the Routing Engine must be upgraded to the first supported Junos release for the SCBE3-MX (18.4R1) before you install it in the SCBE3-MX. Also, we recommend that you update the recovery snapshot with the 18.4R1 or later image before you begin the upgrade. If the Routing Engine fails to boot from the primary image, it will attempt to boot from the recovery image. Since the older recovery image does not support the SCBE3-MX, the Routing Engine will crash if it attempts to boot from the old recovery image.

CAUTION:

If you plug the Routing Engine into the SCBE3-MX without first upgrading Junos to 18.4R1 or later, Junos might crash and go to a db prompt. Should this occur, you’ll need to recover the router by copying the Junos software image for the 18.4R1 or later release and then booting from the USB drive to install 18.4R1 Junos on the SCBE3-MX. The USB install will wipe out the router configuration and all user files on the Routing Engine.

To upgrade the Routing Engine while it’s plugged into an SCBE2-MX or older SCB:

  1. Download the software related to your MX Series Routing Engine.
  2. If you have not already done so, connect to the console port on the switch from your management device, and log in to the Junos OS CLI.
  3. (Optional) Back up the current software configuration to a second storage option. See the Junos OS Installation and Upgrade Guide for instructions on performing this task.
  4. Install the new software.
  5. Reboot the Routing Engine and wait for it to boot with the new Routing Engine image.

  6. Install the SCBE3-MX into the Router Chassis. See:

    Maintaining MX240 SFP and XFP Transceivers

    Maintaining MX480 Switch Control Boards

    Installing an MX960 Switch Control Board

Install the Routing Engine into the SCBE3-MX

Refer to the Routing Engine installation procedure for your MX model:

Installing an MX240 Routing Engine

Installing an MX480 Routing Engine

Installing an MX960 Routing Engine

Install the SCBE3-MX into the Router Chassis

Refer to the Switch Control Board installation procedure for your MX model:

Installing an MX240 Switch Control Board

Installing an MX480 Switch Control Board

Installing an MX960 Switch Control Board

Complete the SCBE3-MX Upgrade

  1. Verify that the installation is successful and the SCBE3-MX is online:
    content_copy zoom_out_map
    user@host> show chassis environment cb 0
CB 0 status
State		Online
Temperature	30 degrees C / 86 degrees F
...
user@host> show chassis environment cb 1
CB 1 status
State		Online
Temperature	30 degrees C / 86 degrees F
...

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

  2. Verify that the fabric planes come online correctly:
    content_copy zoom_out_map
    user@host> show chassis fabric summary
Plane   State    Uptime
 0      Online   2 days, 19 hours, 10 minutes, 9 seconds
 1      Online   2 days, 19 hours, 10 minutes, 9 seconds
...
  3. Verify that the backup Routing Engine is back online:
    content_copy zoom_out_map
    user@host> show chassis routing-engine 1
Routing Engine Status:
Slot 1:
Current State		Backup
...
  4. Verify the SCBE3-MXs are installed:
    content_copy zoom_out_map
    user@host> show chassis hardware
Hardware inventory:
Item             Version  Part number  Serial number     Description
CB 0             REV 29   750-070866   CAKP0543          Enhanced MX SCB 3
CB 1             REV 29   750-070866   CAKP0541          Enhanced MX SCB 3
...

See Also

arrow_backward PREVIOUS Maintaining MX240 SFP and XFP Transceivers
NEXT arrow_forward Troubleshooting the MX240 Components
footer-navigation

© 1999 - 2025 Juniper Networks, Inc. All rights reserved.

Scroll to top

Back to Top