close

keyboard_arrow_left

Table of Contents Expand all

play_arrow Understanding How Virtual Chassis Provides Interchassis Redundancy
- Interchassis Redundancy and Virtual Chassis Overview
play_arrow Understanding How a Virtual Chassis Works
play_arrow Configuring a Virtual Chassis
play_arrow Configuring Virtual Chassis Ports to Interconnect Member Devices
play_arrow Configuring Locality Bias to Conserve Bandwidth on Virtual Chassis Ports
play_arrow Configuring Class of Service for Virtual Chassis Ports
play_arrow Configuring Redundancy Mechanisms on Aggregated Ethernet Interfaces in a Virtual Chassis
play_arrow Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
- Example: Upgrading Junos OS in a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms by Rebooting the Routing Engines
play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Unified In-Service Software Upgrade (ISSU)
play_arrow Upgrading Junos OS in an MX Series Virtual Chassis by Performing a Sequential Upgrade
- How to Use Sequential Upgrade in an MX Series Virtual Chassis
play_arrow Monitoring an MX Series Virtual Chassis
play_arrow Tracing Virtual Chassis Operations for Troubleshooting Purposes
play_arrow Configuration Statements and Operational Commands
- Junos CLI Reference Overview

list Table of Contents

English

Preparing for the SCBE2 Upgrade
Powering Off the MX Series Router
Removing an MX Series Routing Engine from an SCB or SCBE
Replacing the SCB or SCBE with SCBE2
Installing the MX Series Routing Engine into an SCBE2
Powering On the MX Series Router
Configuring Member IDs for the Virtual Chassis
Configuring Virtual Chassis Ports
Completing the SCBE2 Upgrade

keyboard_arrow_right

Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2

date_range 06-Dec-23

arrow_backward

arrow_forward

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:

Verify that the system is runing Junos OS Release 13.3 or later by issuing the show version command on the primary router.
```
user@host> show version
Junos Base OS Software Suite [13.3-yyyymmdd];
...
```
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.
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.
Apply a system halt before shutting down the system by issuing the request system halt all-members command on the primary router.
```
user@host> request system halt all-members
```

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:

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.
```
user@host> request system halt all-members
```
Wait until a message appears on the console confirming that the operating system has halted.
Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
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.

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.

Replacing the SCB or SCBE with SCBE2

To replace the existing SCB or SCBE with SCBE2:

Attach an electrostatic discharge (ESD) grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
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:

Attach an electrostatic discharge (ESD) grounding strap to your bare wrist, and connect the strap to one of the ESD points on the chassis.
Ensure that the ejector handles are not in the locked position. If necessary, flip the ejector handles outward.
Place one hand underneath the Routing Engine to support it.
Carefully align the sides of the Routing Engine with the guides inside the opening on the SCBE2.
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.
Press both of the ejector handles inward to seat the Routing Engine.
Tighten the captive screws on the top and bottom of the Routing Engine.
Connect the management device cables to the Routing Engine.

Powering On the MX Series Router

To power on the MX Series router:

Verify that the power supplies are fully inserted in the chassis.
Verify that each AC power cord is securely inserted into its appliance inlet.
Verify that an external management device is connected to one of the Routing Engine ports (AUX, CONSOLE, or ETHERNET).
Turn on the power to the external management device.
Switch on the dedicated customer-site circuit breakers. Follow the ESD and safety instructions for your site.
Attach an ESD grounding strap to your bare wrist and connect the strap to one of the ESD points on the chassis.
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.
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.
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.

Set the member ID on the router configured as member 0:

content_copy zoom_out_map
user@hostA> request virtual-chassis member-id set member 0

content_copy zoom_out_map
This command will enable virtual-chassis mode and reboot the system.
 Continue? [yes,no] yes

Repeat Step 1 to set the member ID on the router configured as member 1.
```
user@hostB> request virtual-chassis member-id set member 1
```
```
This command will enable virtual-chassis mode and reboot the system.
 Continue? [yes,no] yes
```
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.

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

For example:

content_copy zoom_out_map
{master:member0-re0}
user@hostA> show virtual-chassis status
Preprovisioned Virtual Chassis
Virtual Chassis ID: 4f2b.1aa0.de08
                                               Mastership           Neighbor List  
Member ID       Status   Serial No    Model    priority    Role      ID  Interface

0 (FPC   0- 11) Prsnt    JN10C7135AFC mx240          129  Master*

(Optional) Verify the member ID configuration for member 1.
For example:
```
Amnesiac (ttyd0)

login: user
Password:

... 
{master:member1-re0}
user> show virtual-chassis status
Virtual Chassis ID: ef98.2c6c.f7f7
                                               Mastership           Neighbor List  
Member ID       Status   Serial No    Model    priority    Role      ID  Interface

1 (FPC  12- 23) Prsnt    JN115D117AFB mx480          128  Master*
```
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.

Log into the console port on member 0 and configure the first Virtual Chassis port that connects to member 1.
```
{master:member0-re0}
user@host> request virtual-chassis vc-port set fpc-slot number pic-slot number port number
vc-port successfully set
```
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.

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

content_copy zoom_out_map
{master:member1-re0}
user@host> request virtual-chassis vc-port set fpc-slot number pic-slot number port number
vc-port successfully set

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.

content_copy zoom_out_map
user@host> show interface xe-0/0/1
Physical interface: xe-0/0/1, Enabled, Physical link is Up
  Interface index: 49195, SNMP ifIndex: 591
  Link-level type: Ethernet, MTU: 1514, Speed: 10Gbps, Duplex: Full-Duplex, BPDU Error: None, MAC-REWRITE Error: None, Loopback: Disabled, Source filtering: Disabled,
  Flow control: Disabled
  Device flags   : Present Running
  Interface flags: SNMP-Traps Internal: 0x0
  Link flags     : None
  CoS queues     : 12 supported, 12 maximum usable queues
  Current address: 00:1d:b5:f7:4e:e1, Hardware address: 00:1d:b5:f7:4e:e1
  Last flapped   : 2011-06-01 00:42:03 PDT (00:02:42 ago)
  Input rate     : 0 bps (0 pps)
  Output rate    : 0 bps (0 pps)
  Active alarms  : None
  Active defects : None

  Logical interface xe-0/0/1.0 (Index 73) (SNMP ifIndex 523)
    Flags: SNMP-Traps 0x0 Encapsulation: ENET2
    Input packets : 0
    Output packets: 0
    Protocol eth-switch, MTU: 0
      Flags: Trunk-Mode

Configure the remaining VCP ports 1 at a time. Wait 30 seconds after setting each VCP port.

content_copy zoom_out_map
user@host> request virtual-chassis vc-port set fpc-slot number pic-slot number port number
vc-port successfully set

Completing the SCBE2 Upgrade

To complete the SCBE2 upgrade procedure:

Verify that the installation is successful and the SCBE2 is online by issuing the show chassis environment cb command:
```
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.

Verify that the fabric planes come online correctly by issuing the show chassis fabric summary command:

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
...

Verify that the backup Routing Engine is back online by issuing the show chassis routing-engine 1 command:
```
user@host> show chassis routing-engine 1
Routing Engine Status:
Slot 1:
Current State		Backup
...
```

Verify the SCBE2s before you finish by issuing the show chassis hardware command:

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
...

You see that the router now has SCBE2s.

arrow_backward PREVIOUS Example: Deleting a Virtual Chassis Configuration for MX Series 5G Universal Routing Platforms

NEXT arrow_forward Guidelines for Configuring Virtual Chassis Ports

Interchassis Redundancy Using Virtual Chassis User Guide for MX Series Routers

ON THIS PAGE

Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2

Preparing for the SCBE2 Upgrade

Powering Off the MX Series Router

Removing an MX Series Routing Engine from an SCB or SCBE

Replacing the SCB or SCBE with SCBE2

Installing the MX Series Routing Engine into an SCBE2

Powering On the MX Series Router

Configuring Member IDs for the Virtual Chassis

Configuring Virtual Chassis Ports

Completing the SCBE2 Upgrade

Stay in touch

Helped me install or use the product
Accelerated my deployment

Discuss the product with a co-worker
Make a purchase inquiry

Interchassis Redundancy Using Virtual Chassis User Guide for MX Series Routers

ON THIS PAGE

Upgrading an MX Virtual Chassis SCB or SCBE to SCBE2

Preparing for the SCBE2 Upgrade

Powering Off the MX Series Router

Removing an MX Series Routing Engine from an SCB or SCBE

Replacing the SCB or SCBE with SCBE2

Installing the MX Series Routing Engine into an SCBE2

Powering On the MX Series Router

Configuring Member IDs for the Virtual Chassis

Configuring Virtual Chassis Ports

Completing the SCBE2 Upgrade

Related Documentation

Stay in touch