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

keyboard_arrow_right

Configuring Member IDs for a Virtual Chassis

date_range 06-Dec-23

arrow_backward

arrow_forward

After you commit the preprovisioned configuration on the primary router, you must assign the preprovisioned member IDs to both MX Series routers in the Virtual Chassis by using the request virtual-chassis member-id set command. In an MX Series Virtual Chassis, you can optionally include the slots-per-chassis slot-count option to identify the number of chassis slots in the member router. Assigning the member ID and, optionally, slot-count causes the router to reboot in preparation for forming the Virtual Chassis.

Note:

If you issue the request virtual-chassis member-id set command without first installing an MX Virtual Chassis Redundancy Feature Pack license on both member routers, the software displays a warning message that you are operating without a valid Virtual Chassis software license.

For information about the supported member router combinations in an MX Series Virtual Chassis, see Interchassis Redundancy and Virtual Chassis Overview. Platform support depends on the Junos OS release in your installation.

To configure the member ID and, optionally, slot count for each member router in an MX Series Virtual Chassis:

Set the member ID on the router configured as member 0 in one of the following ways:
- For a Virtual Chassis consisting of a combination of MX240 routers, MX480 routers, and MX960 routers:
  user@hostA> request virtual-chassis member-id set member 0
  This command will enable virtual-chassis mode and reboot the system. Continue? [yes,no] yes
  With this Virtual Chassis configuration, the default slot-count (12) is the same for both member routers, so you do not need to configure it.
- For a Virtual Chassis consisting of an MX2010 router and either an MX960 router or MX2010 router:
  user@hostA> request virtual-chassis member-id set member 0
  This command will enable virtual-chassis mode and reboot the system. Continue? [yes,no] yes
  With this Virtual Chassis configuration, the default slot-count (12) is the same for an MX960 router and an MX2010 router, so you do not need to configure it.
- For a Virtual Chassis consisting of an MX2020 router and either an MX960 router or MX2010 router:
  user@hostA> request virtual-chassis member-id set member 0 slots-per-chassis slot-count
  This command will enable virtual-chassis mode and reboot the system. Continue? [yes,no] yes
  To ensure that this Virtual Chassis configuration forms properly, you must set the slot-count value of the MX960 router or MX2010 router to 20 to match the slot-count of the MX2020 router. For example:
  user@hostA> request virtual-chassis member-id set member 0 slots-per-chassis 20
- For a Virtual Chassis consisting of two MX2020 routers:
  user@hostA> request virtual-chassis member-id set member 0
  This command will enable virtual-chassis mode and reboot the system. Continue? [yes,no] yes
  With this Virtual Chassis configuration, the default slot-count (20) is the same for both MX2020 routers, so you do not need to configure it.
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.

Repeat Step 1 to set the member ID on the router configured as member 1.

content_copy zoom_out_map
user@hostB> request virtual-chassis member-id set member 1

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

content_copy zoom_out_map
user@hostB> request virtual-chassis member-id set member 1 slots-per-chassis slot-count

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

For example:

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

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.

arrow_backward PREVIOUS Enabling Graceful Routing Engine Switchover and Nonstop Active Routing for a Virtual Chassis

NEXT arrow_forward Example: Configuring Interchassis Redundancy for MX Series 5G Universal Routing Platforms Using a Virtual Chassis

Interchassis Redundancy Using Virtual Chassis User Guide for MX Series Routers

Configuring Member IDs for a Virtual Chassis

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

Configuring Member IDs for a Virtual Chassis

Related Documentation

Stay in touch