Knowledge Search


×
 

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

  [KB21133] Show Article Properties


Summary:

This article steps you thru how to reactivate an 'Inactive' Virtual Chassis (VC) Member.

This article is part of the EX Resolution Guide: KB21064 - Verifying health of Virtual Chassis and troubleshoot if the members are not all present.

Note: If the device is a Master or Backup RE, and remains in linecard mode or unable to join the VC, refer to KB33879 - Routing Engine stuck in 'Linecard' role.

Symptoms:

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-24f   128        Linecard    1  vcp-0      
1 (FPC 1)  Prsnt      BR0209456997   ex4200-24f   128        Master*     3  vcp-0      
                                                              	       	 0  vcp-1      
2 (FPC 2)  Prsnt      BR0208233803   ex4200-24f   128        Backup      3  vcp-1      

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

How do you make the Inactive member active (where the status = Prsnt)?
 

Cause:

Typically when a member is Inactive, all the members of the switch are not running the same Junos OS version. The 'show version' command will display the Junos version for all the members which are physically connected (including Present & Inactive members).

This is confirmed in the following 'show version' output.  In this example, FPC 0 is Inactive because of a Junos version mismatch:

{master:1}[edit]
root@EX4200-VC# run show version
fpc0:
--------------------------------------------------------------------------
Hostname: EX4200-VC
Model: ex4200-48t
JUNOS Base OS boot [11.1R1.10]
JUNOS Base OS Software Suite [11.1R1.10]
JUNOS Kernel Software Suite [11.1R1.10]
JUNOS Crypto Software Suite [11.1R1.10]
JUNOS Online Documentation [11.1R1.10]
JUNOS Enterprise Software Suite [11.1R1.10]
JUNOS Packet Forwarding Engine Enterprise Software Suite [11.1R1.10]
JUNOS Routing Software Suite [11.1R1.10]
JUNOS Web Management [11.1R1.10]

fpc1:
--------------------------------------------------------------------------
Hostname: EX4200-VC
Model: ex4200-24f
JUNOS Base OS boot [10.2R3.10]
JUNOS Base OS Software Suite [10.2R3.10]
JUNOS Kernel Software Suite [10.2R3.10]
JUNOS Crypto Software Suite [10.2R3.10]
JUNOS Online Documentation [10.2R3.10]
JUNOS Enterprise Software Suite [10.2R3.10]
JUNOS Packet Forwarding Engine Enterprise Software Suite [10.2R3.10]
JUNOS Routing Software Suite [10.2R3.10]
JUNOS Web Management [10.2R3.10]

fpc2:
--------------------------------------------------------------------------
Hostname: EX4200-VC
Model: ex4200-24f
JUNOS Base OS boot [10.2R3.10]
JUNOS Base OS Software Suite [10.2R3.10]
JUNOS Kernel Software Suite [10.2R3.10]
JUNOS Crypto Software Suite [10.2R3.10]
JUNOS Online Documentation [10.2R3.10]
JUNOS Enterprise Software Suite [10.2R3.10]
JUNOS Packet Forwarding Engine Enterprise Software Suite [10.2R3.10]
JUNOS Routing Software Suite [10.2R3.10]
JUNOS Web Management [10.2R3.10]

 

 

Solution:

To make the 'Inactive' member active, reinstall Junos version to match the existing Virtual Chassis Master.
There are two ways to achieve this. Both methods are explained in detail below: 

Option 1. Re-install the same Junos OS version running on the active VC members to the inactive member.
Option 2. If this does not form the VC, isolate the inactive member from the VC and upgrade it individually, and then bring it back into the VC. 

Option-1 - Upgrade the affected member without removing it from the VC 

For example, on a four member EX4300VC running 14.1X53-D30, all the VC members become inactive because one of the members has a Junos OS version mismatch.
To recover the state, load the Junos image on the affected member to be the same as entire VC, and perform a reboot. The VC comes up fine once done. 

{master:1}[edit]
root# run show virtual-chassis

Preprovisioned Virtual Chassis
Virtual Chassis ID: e987.b14d.bcbe
Virtual Chassis Mode: Enabled
                                 Mstr Mixed Route Neighbor List
Member ID Status Serial No Model prio Role Mode Mode ID Interface
0 (FPC 0) Inactive PE3715170046 ex4300-48t 129 Linecard N VC 2 vcp-255/1/0
                                                             1 vcp-255/1/1
1 (FPC 1) Prsnt PD3715220083 ex4300-48p 129 Master* N VC 0 vcp-255/1/0
                                                         3 vcp-255/1/1
2 (FPC 2) Inactive PE3715170221 ex4300-48t 0 Linecard N VC 3 vcp-255/1/0
                                                           0 vcp-255/1/1
3 (FPC 3) Inactive PE3715210118 ex4300-48t 0 Linecard N VC 1 vcp-255/1/0
                                                           2 vcp-255/1/1

root# run show version
fpc0:
--------------------------------------------------------------------------
Model: ex4300-48t
JUNOS EX Software Suite [14.1X53-D30.3]
JUNOS FIPS mode utilities [14.1X53-D30.3]
JUNOS Online Documentation [14.1X53-D30.3]
JUNOS EX 4300 Software Suite [14.1X53-D30.3]
JUNOS Web Management Platform Package [14.1X53-D30.3]
JUNOS py-base-powerpc [14.1X53-D30.3]

fpc1:
----------------------------------------------------------- <---------- Affected member
Model: ex4300-48p
JUNOS EX Software Suite [13.2X51-D26.2]
JUNOS FIPS mode utilities [13.2X51-D26.2]
JUNOS Online Documentation [13.2X51-D26.2]
JUNOS EX 4300 Software Suite [13.2X51-D26.2]
JUNOS Web Management [13.2X51-D26.2]
JUNOS py-base-powerpc [13.2X51-D26.2]

fpc2:
--------------------------------------------------------------------------
Model: ex4300-48t
JUNOS EX Software Suite [14.1X53-D30.3]
JUNOS FIPS mode utilities [14.1X53-D30.3]
JUNOS Online Documentation [14.1X53-D30.3]
JUNOS EX 4300 Software Suite [14.1X53-D30.3]
JUNOS Web Management Platform Package [14.1X53-D30.3]
JUNOS py-base-powerpc [14.1X53-D30.3]

fpc3:
--------------------------------------------------------------------------
Model: ex4300-48t
JUNOS EX Software Suite [14.1X53-D30.3]
JUNOS FIPS mode utilities [14.1X53-D30.3]
JUNOS Online Documentation [14.1X53-D30.3]
JUNOS EX 4300 Software Suite [14.1X53-D30.3]
JUNOS Web Management Platform Package [14.1X53-D30.3]
JUNOS py-base-powerpc [14.1X53-D30.3]
After the upgrade and reboot:

{master:1}
root> show virtual-chassis

Preprovisioned Virtual Chassis
Virtual Chassis ID: e987.b14d.bcbe
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 PE3715170046 ex4300-48t 129 Backup N VC 2 vcp-255/1/0
                                                        1 vcp-255/1/1
1 (FPC 1) Prsnt PD3715220083 ex4300-48p 129 Master* N VC 0 vcp-255/1/0
                                                         3 vcp-255/1/1
2 (FPC 2) Prsnt PE3715170221 ex4300-48t 0 Linecard N VC 3 vcp-255/1/0
                                                        0 vcp-255/1/1
3 (FPC 3) Prsnt PE3715210118 ex4300-48t 0 Linecard N VC 1 vcp-255/1/0
                                                        2 vcp-255/1/1



Option-2 - Isolate affected switch, upgrade and put it back into the VC

Here is another way to recover the VC: 

  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 using command:
    root@EX4200-VC> request virtual-chassis reactivate
    
     Example output:
    
    {Linecard: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  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 (Master role with 1 member), proceed with upgrading. Refer to KB20536 - Upgrading EX series Devices.  

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

    root@EX4200-VC# run 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)  Prsnt    BR0208233776    ex4200-24f    128        Linecard    1  vcp-0     
    1 (FPC 1)  Prsnt    BR0209456997    ex4200-24f    128        Master*     3  vcp-0     
                                                                                                                    0  vcp-1     
    2 (FPC 2)  Prsnt    BR0208233803    ex4200-24f    128        Backup      3  vcp-1     
    
    Member ID for next new member: 3 (FPC 3)


Once Active (status=Prsnt), if you prefer to have FPC 0 as a Backup, refer to KB21115 - Converting a Virtual Chassis Member Role from Linecard to Backup.

To verify the health of your Virtual Chassis, refer to KB21064 - Verifying health of Virtual Chassis and troubleshoot if the members are not all present.

Modification History:
2019-09-12: Added reference to KB article that helps resolve 'Linecard' role.
2018-03-26: Updated solution using two options.
Related Links: