There are two common scenarios wherein the members of a Virtual Chassis show as inactive. This article explains the cause of this behavior and how to fix it.
Note: This article is part of the EX Resolution Guide - Troubleshoot Virtual Chassis: KB21064 [juniper.net] .
The most common reason for the Inactive status is a Junos OS mismatch between the members of the stack.
In this example, the Primary and Backup members have a status of Present; however, one of the members (FPC 1) reports the status as Inactive :
Virtual Chassis ID: 21dc.c221.cd99 Virtual Chassis Mode: Enabled Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 0 (FPC 0) Prsnt PF3713480ABC ex4300-24p 129 Master* N VC 1 vcp-255/1/1 1 (FPC 1) Inactive PE3715210DEF ex4300-48t 0 Linecard N VC 0 vcp-255/1/1
The show version command displays the Junos OS version for all the members that are physically connected (including Present and Inactive members):
show version
root@virtual-chassis> show version fpc0: -------------------------------------------------------------------------- Hostname: virtual-chassis Model: ex4300-24p Junos: 18.4R2-S3 JUNOS EX Software Suite [18.4R2-S3] JUNOS FIPS mode utilities [18.4R2-S3] JUNOS Crypto Software Suite [18.4R2-S3] JUNOS Online Documentation [18.4R2-S3] JUNOS Phone-Home Software Suite [18.4R2-S3] JUNOS jsd [powerpc-18.4R2-S3-jet-1] JUNOS SDN Software Suite [18.4R2-S3] JUNOS EX 4300 Software Suite [18.4R2-S3] JUNOS Web Management Platform Package [18.4R2-S3] JUNOS py-base-powerpc [18.4R2-S3] JUNOS py-extensions-powerpc [18.4R2-S3] fpc1: -------------------------------------------------------------------------- Hostname: virtual-chassis Model: ex4300-48t Junos: 17.3R3-S9.3 <----- (FPC 1 is running a different version.) JUNOS EX Software Suite [17.3R3-S9.3] JUNOS FIPS mode utilities [17.3R3-S9.3] JUNOS Crypto Software Suite [17.3R3-S9.3] JUNOS Online Documentation [17.3R3-S9.3] JUNOS jsd [powerpc-17.3R3-S9.3-jet-1] JUNOS SDN Software Suite [17.3R3-S9.3] JUNOS EX 4300 Software Suite [17.3R3-S9.3] JUNOS Web Management Platform Package [17.3R3-S9.3] JUNOS py-base-powerpc [17.3R3-S9.3] JUNOS py-extensions-powerpc [17.3R3-S9.3]
There are two methods to fix this scenario:
Option 1 : Re-install the same Junos OS version that is running on the active VC members on the inactive members as well by executing request system software add package-name member , and then reboot the affected switches.
request system software add
member
Example: request system software add /var/tmp/ jinstall-ex-4300-18.4R2-S3-signed.tgz member 1 reboot
request system software add /var/tmp/
jinstall-ex-4300-18.4R2-S3-signed.tgz
member 1 reboot
Option 2: If the problem persists, isolate the inactive members from the VC and upgrade them individually by performing the following steps:
Isolate the affected switch (the Inactive member) by unplugging the VCP cables.
Re-activate the Virtual Chassis to make that switch a stand-alone switch by running request virtual-chassis reactivate :
request virtual-chassis reactivate
root@virtual-chassis> show virtual-chassis Virtual Chassis ID: 21dc.c221.cd99 Virtual Chassis Mode: Enabled Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 1 (FPC 1) Inactive PE3715210DEF ex4300-48t 128 Linecard N VC {Linecard:1} root@virtual-chassis> request virtual-chassis reactivate {master:1} root@virtual-chassis> show virtual-chassis Virtual Chassis ID: 21dc.c221.cd91 Virtual Chassis Mode: Enabled Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 1 (FPC 1) Prsnt PE3715210DEF ex4300-48t 128 Linecard N VC
Once the affected device been isolated as a stand-alone switch, proceed with the standard upgrade.
After a successful upgrade, re-connect the VCP cables. It should then make FPC 0 an Active member.
Final Result
{master:0} root@virtual-chassis> show virtual-chassis Virtual Chassis ID: 21dc.c221.cd99 Virtual Chassis Mode: Enabled Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 0 (FPC 0) Prsnt PF3713480ABC ex4300-24p 129 Master* N VC 1 vcp-255/1/1 1 (FPC 1) Prsnt PE3715210DEF ex4300-48t 0 Backup N VC 0 vcp-255/1/1
Besides the standard Virtual Chassis feature of building single stacks with the same platform models, Juniper allows other VC modes like "mixed" and "fabric". If you are using either setup, you must change the default mode on new members before they can join the existing stack. They must run the same Junos OS version on all members, regardless of platform. For more information, review KB31540 - Installing software on a Mixed-Mode Virtual Chassis [juniper.net] . You can check if there is a mode mismatch by running show virtual-chassis mode :
show virtual-chassis mode
Example
{master:0} root@virtual-chassis> show virtual-chassis Preprovisioned Virtual Chassis Virtual Chassis ID: 47a5.dd6e.29bb Virtual Chassis Mode: Mixed Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 0 (FPC 0) Prsnt TA3710000ABC qfx5100-48s-6q 129 Master* Y VC 1 vcp-255/0/48 3 vcp-255/0/49 1 (FPC 1) Prsnt TA3710000DEF qfx5100-48s-6q 129 Backup Y VC 0 vcp-255/0/48 2 vcp-255/0/49 2 (FPC 2) Inactive PE3710000GHI ex4300-48t 0 Linecard N VC 1 vcp-255/1/0 3 vcp-255/1/1 3 (FPC 3) Inactive PE3110000JKL ex4300-48t 0 Linecard N VC 2 vcp-255/1/0 0 vcp-255/1/1 {master:0} root@virtual-chassis> show virtual-chassis mode fpc0: ------------------------------------------------------------------------- Current mode : Virtual Chassis with mixed devices <-- FPC0 and FPC1 are running mixed mode Future mode after reboot : Virtual Chassis with mixed devices fpc1: -------------------------------------------------------------------------- Current mode : Virtual Chassis with mixed devices Future mode after reboot : Virtual Chassis with mixed devices fpc2: -------------------------------------------------------------------------- Current mode : Virtual Chassis with similar devices <-- FPC2 and FPC3 are running standard mode Future mode after reboot : Virtual Chassis with similar devices fpc3: -------------------------------------------------------------------------- Current mode : Virtual Chassis with similar devices Future mode after reboot : Virtual Chassis with similar devices
You can fix this problem by running request virtual-chassis mode on the affected members. Different options exist:
request virtual-chassis mode
request virtual-chassis mode fabric (Use this mode when building a VCF.) request virtual-chassis mode mixed (Use this mode to form mixed Virtual Chassis or mixed VCF.) request virtual-chassis mode disable (Disable the Virtual Chassis fabric or mixed mode setting if it was previously enabled.)
Note: You can add the option " member " to execute the command on a specific switch only. A reboot is required after running these commands.
{master:0} root@virtual-chassis> show virtual-chassis Preprovisioned Virtual Chassis Virtual Chassis ID: 47a5.d06e.29bb Virtual Chassis Mode: Mixed Mstr Mixed Route Neighbor List Member ID Status Serial No Model prio Role Mode Mode ID Interface 0 (FPC 0) Prsnt TA3710000ABC qfx5100-48s-6q 129 Master* Y VC 1 vcp-255/0/48 3 vcp-255/0/49 1 (FPC 1) Prsnt TA3710000DEF qfx5100-48s-6q 129 Backup Y VC 0 vcp-255/0/48 2 vcp-255/0/49 2 (FPC 2) Prsnt PE3710000GHI ex4300-48t 0 Linecard Y VC 1 vcp-255/1/0 3 vcp-255/1/1 3 (FPC 3) Prsnt PE3110000JKL ex4300-48t 0 Linecard Y VC 2 vcp-255/1/0 0 vcp-255/1/1
2024-02-05: publishing the article.
2022-02-28: Updated article to reflect latest information
2021-03-25: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives.
2020-06-03: Added QFX
2019-09-12: Added reference to KB article that helps resolve 'Linecard' role.
2018-03-26: Updated solution using two options.