Support Support Downloads Knowledge Base Case Manager My Juniper Community

Knowledge Base

Search our Knowledge Base sites to find answers to your questions.

Ask All Knowledge Base Sites All Knowledge Base Sites JunosE Defect (KA)Knowledge BaseSecurity AdvisoriesTechnical BulletinsTechnotes Sign in to display secure content and recently viewed articles

[EX/QFX] Fixing a Virtual Chassis Member with an 'Inactive' status

0

0

Article ID: KB21133 KB Last Updated: 03 Jun 2020Version: 5.0
Summary:

There are two common scenarios on which members of a Virtual Chassis show as inactive. This article explains the cause of this behavior and how to fix it. (This KB is part of the EX Resolution Guide: KB21064)

Solution:

FIRST SCENARIO:

 The most frequent reason of the Inactive status is due to a Junos OS mismatch between the members of the stack.

 In this example, the Master and Back-up members have a status of Present,  however, one of the members (FPC 0) reports the status as 'Inactive':

Virtual Chassis ID: 6eb0.0094.e64b
                        Mastership    Neighbor List  
Member ID  Status     Serial No      Model        priority   Role       ID  Interface
0 (FPC 0)  Inactive   BR0208233776   ex4200-48t   128        Linecard    1  vcp-0      
1 (FPC 1)  Prsnt      BR0209456997   ex4200-48t   128        Master*     3  vcp-0      
                                                              	       	 0  vcp-1      
2 (FPC 2)  Prsnt      BR0208233803   ex4200-48t   128        Backup      3  vcp-1      

Member ID for next new member: 3 (FPC 3)


The 'show version' command displays the Junos version for all the members which are physically connected (including Present & Inactive members):

{master:1}[edit]

root@EX4200-VC# run show version 
fpc0:
--------------------------------------------------------------------------
Hostname: EX4200-VC
Model: ex4200-48t
JUNOS Base OS boot [12.3R1.1] <--FPC0 is running a different version 
JUNOS Base OS Software Suite [12.3R1.1]
JUNOS Kernel Software Suite [12.3R1.1]
(...)

fpc1:
--------------------------------------------------------------------------
Hostname: EX4200-VC
Model: ex4200-48t
JUNOS Base OS boot [12.3R4.6]
JUNOS Base OS Software Suite [12.3R4.6]
JUNOS Kernel Software Suite [12.3R4.6]
(...)

fpc2:
--------------------------------------------------------------------------
Hostname: EX4200-VC
Model: ex4200-48t
JUNOS Base OS boot [12.3R4.6]
JUNOS Base OS Software Suite [12.3R4.6]
JUNOS Kernel Software Suite [12.3R4.6]
(...)



There are two methods to fix this scenario:

Example:    request system software add /var/tmp/jinstall-ex-4200-12.3R4.6​-domestic-signed.tgz member 0 reboot​
 

  • Option 2. If problem persists, isolate the inactive members from the VC and upgrade them individually by following the below steps:

1.  Isolate the affected switch (the Inactive member) by unplugging the VCP cables.

2.  Re-active the Virtual Chassis to make that switch a stand-alone switch by running "request virtual-chassis reactivate":
 

root@EX4200-VC> show virtual-chassis

Virtual Chassis ID: 6eb0.0094.e64b
                        Mastership    Neighbor List  
Member ID  Status     Serial No      Model        priority   Role       ID  Interface
0 (FPC 0)  Inactive   BR0208233776   ex4200-48t   128        Linecard  
Member ID for next new member: 1 (FPC 1)

{Linecard:0}
root@EX4200-VC> request virtual-chassis reactivate

{master:0}
root@EX4200-VC> show virtual-chassis

Virtual Chassis ID: 684e.e679.9f51
Virtual Chassis Mode: Enabled
                                          Mastership            Neighbor List 
Member ID  Status   Serial No    Model    priority    Role      ID  Interface
0 (FPC 0)  Prsnt    BR0208233776 ex4200-48t      128  Master* 
Member ID for next new member: 1 (FPC 1)

 

3.  Once the affected device been isolated as a stand-alone switch, proceed with the standard upgrade.   

4.  After a successful upgrade, re-connect the VCP cables.  It should then make FPC 0 an Active member.

 
  • Final result

root@EX4200-VC> show virtual-chassis
 
Virtual Chassis ID: 684e.e679.9f51
Virtual Chassis Mode: Enabled
                        Mastership    Neighbor List  
Member ID  Status     Serial No      Model        priority   Role       ID  Interface
0 (FPC 0)  Prsnt      BR0208233776   ex4200-48t   128        Linecard    1  vcp-0      
1 (FPC 1)  Prsnt      BR0209456997   ex4200-48t   128        Master*     3  vcp-0      
                                                                         0  vcp-1      
2 (FPC 2)  Prsnt      BR0208233803   ex4200-48t   128        Backup      3  vcp-1 

 

SECOND SCENARIO:

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 using either setup, you must change the default mode on new members before they can join the existing stack. You can check if there is a mode mismatch by running "show virtual-chassis mode":

Example:

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     TA3711110189 qfx5100-48s-6q 129   Master*      Y  VC   1  vcp-255/0/48
                                                                            3  vcp-255/0/49
 
1 (FPC 1)  Prsnt     TA3711110132 qfx5100-48s-6q 129   Backup       Y  VC   0  vcp-255/0/48
                                                                            2  vcp-255/0/49
 
2 (FPC 2)  Inactive  PE3711111978 ex4300-48t       0   Linecard     Y  VC   1  vcp-255/1/0
                                                                            3  vcp-255/1/1
3 (FPC 3)  Inactive  PE3111111249 ex4300-48t       0   Linecard     Y  VC   2  vcp-255/1/0
                                                                            0  vcp-255/1/1

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 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 could add option "member" to execute command on a specific switch only. A reboot is required after running these commands.

 

  • Final result:

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     TA3711110189 qfx5100-48s-6q 129   Master*      Y  VC   1  vcp-255/0/48
                                                                            3  vcp-255/0/49

1 (FPC 1)  Prsnt     TA3711110132 qfx5100-48s-6q 129   Backup       Y  VC   0  vcp-255/0/48
                                                                            2  vcp-255/0/49

2 (FPC 2)  Prsnt     PE3711111978 ex4300-48t       0   Linecard     Y  VC   1  vcp-255/1/0
                                                                            3  vcp-255/1/1
3 (FPC 3)  Prsnt     PE3111111249 ex4300-48t       0   Linecard     Y  VC   2  vcp-255/1/0
                                                                            0  vcp-255/1/1

Modification History:
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.

Related Links

Comment on this article > Affected Products Browse the Knowledge Base for more articles related to these product categories. Select a category to begin.

Getting Up and Running with Junos

Getting Up and Running with Junos Security Alerts and Vulnerabilities Product Alerts and Software Release Notices Problem Report (PR) Search Tool EOL Notices and Bulletins JTAC User Guide Customer Care User Guide Pathfinder SRX High Availability Configurator SRX VPN Configurator Training Courses and Videos End User Licence Agreement Global Search