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

Configuring Virtual Chassis Ports to Interconnect Member Routers

To interconnect the member routers in an MX Series Virtual Chassis, you must use the request virtual-chassis vc-port set command to configure Virtual Chassis ports on Trio Modular Port Concentrator/Modular Interface Card (MPC/MIC) interfaces. After it is configured, a Virtual Chassis port is dedicated to the task of interconnecting member routers, and is no longer available for configuration as a standard network port.

Note: If you issue the request virtual-chassis vc-port 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.

1. Configure the Virtual Chassis ports on the router configured as member 0.
   1. Configure the first Virtual Chassis port that connects to member 1.

      {local:member0-re0}

      user@hostA> request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-number

      After the Virtual Chassis port is created, it is renamed vcp-slot/pic/port, 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.

      For example, the following command configures Virtual Chassis port vcp-2/2/0 on member 0:

      {local:member0-re0}

      user@hostA> request virtual-chassis vc-port set fpc-slot 2 pic-slot 2 port 0

      vc-port successfully set

   2. When the first Virtual Chassis port is up on member 0, repeat Step 1a to configure the second Virtual Chassis port that connects to member 1.

      {local:member0-re0}

      user@hostA> request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-number
2. Configure the Virtual Chassis ports on the router configured as member 1.
   1. Configure the first Virtual Chassis port that connects to member 0.

      {master:member1-re0}

      user@hostB> request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-number
   2. When the first Virtual Chassis port is up on member 1, repeat Step 2a to configure the second Virtual Chassis port that connects to member 0.

      {master:member1-re0}

      user@hostB> request virtual-chassis vc-port set fpc-slot fpc-slot-number pic-slot pic-slot-number port port-number

   When all of the line cards in all of the member routers are online, and the Virtual Chassis has formed, you can issue Virtual Chassis commands from the terminal window of the master router.

   Note: When the Virtual Chassis forms, the FPC slots are renumbered to reflect the slot numbering and offsets used in the Virtual Chassis instead of the physical slot numbers where the FPC is actually installed. Member 0 in the Virtual Chassis uses FPC slot numbers 0 through 11 with no offset, and member 1 uses FPC slot numbers 12 through 23, with an offset of 12. For example, a 10-Gigabit Ethernet interface that appears as xe-14/2/2 (FPC slot 14, PIC slot 2, port 2) in the show interfaces command output is actually interface xe-2/2/2 (FPC slot 2, PIC slot 2, port 2) on member 1 after deducting the FPC slot numbering offset of 12 for member 1.

3. (Optional) Verify the that the Virtual Chassis is properly configured and that the Virtual Chassis ports are operational.

   {master:member0-re0}

   user@hostA> show virtual-chassis status
   
   
   

   {master:member0-re0}

   user@hostA> show virtual-chassis vc-port all-members
4. Commit the configuration on the master router.
   {master:member0-re0}[edit system]user@hostA# commit synchronize

   This step is required to ensure that the configuration groups and Virtual Chassis configuration are propagated to both members of the Virtual Chassis.