In some scenarios, a switch that is expected to work in Routing-Engine mode will be stuck as a Linecard even after reboot or even after running the request virtual-chassis reactivate command. This may happen after performing changes on the existing Virtual Chassis (VC) or due to unexpected hardware or power issues.
request virtual-chassis reactivate
This article explains how to restore the switch when the above problem is encountered.
The affected switch remains in the "Linecard" role even after executing the request virtual-chassis reactivate command, and it will not communicate with other members of the stack:
root@switch> 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 BR0123456ABC ex4200-48t 128 Linecard*
In order to restore the switch, it is necessary to remove the old VC files and restart the process by performing the following steps:
(Optional) In some cases, it is necessary to delete the existing VC ports as an initial step:
See request virtual-chassis vc-port delete for syntax and description.
Example EX4200: root@switch> request virtual-chassis vc-port delete pic-slot 0 port 48 local ELS: root@switch> request virtual-chassis vc-port delete pic-slot <PIC number> port <port number> EX4400: root@switch> request virtual-chassis mode network-port <reboot> Note that EX4400 requires a reboot to complete the conversion of a port from virtual-chassis mode to network mode. See Understanding EX Series Virtual Chassis for more information.
Example
EX4200: root@switch> request virtual-chassis vc-port delete pic-slot 0 port 48 local ELS: root@switch> request virtual-chassis vc-port delete pic-slot <PIC number> port <port number> EX4400: root@switch> request virtual-chassis mode network-port <reboot>
Note that EX4400 requires a reboot to complete the conversion of a port from virtual-chassis mode to network mode.
See Understanding EX Series Virtual Chassis for more information.
Clear the Virtual Chassis configuration file:
root@host1>Start shell user root %cd /config/vchassis/ %rm *
Restart the VCCP process:
root% ps –auwx | grep vccp root% kill “process #”
Example root% ps -auwx | grep vccp root 1590 0.0 0.8 52128 15712 ?? S< 6:53AM 0:05.08 /usr/sbin/vccpd -N root 3281 0.0 0.1 2536 1100 u0 R+ 10:52PM 0:00.01 grep vccp root% kill 1590
root% ps -auwx | grep vccp root 1590 0.0 0.8 52128 15712 ?? S< 6:53AM 0:05.08 /usr/sbin/vccpd -N root 3281 0.0 0.1 2536 1100 u0 R+ 10:52PM 0:00.01 grep vccp root% kill 1590
Reactivate the Virtual Chassis from operational mode:
root@switch>request virtual-chassis reactivate
If successful, the switch will change from Linecard to Primary role:
root@host1> 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 BR0123456ABC ex4200-48t 128 Master*
Note: If Role is Master but the cli prompt shows as linecard, try to power cycle the device to recover.
If the problem persists, contact Support for further investigation and troubleshooting.
2025-02-25: Added power cycle option
2022-03-07: Added documentation link to reference reboot for EX4400 port mode conversion
2021-12-02: Minor edit for deleting virtual chassis ports
2021-04-07: Updated the article terminology to align with Juniper's Inclusion & Diversity initiatives
2019-09-07: Minor, non-technical edits