Hello,
Thank you very much for your reply. The command request system zeroize did nothing also, the switch keeps booting in this vc mode.
I have of course kept reading the internet for this issue, and it seems like there are some problems when reverting back into stand-alone mode. I've found people who had success by deleting the /config/vchassis files and folder, however when I do that and reboot, the files just come back and the switch is still in vc mode.
Using delete virtual-chassis also gives me no results. Each time I boot the switch I can write show virtual-chassis and it tells me the switch is in vc mode.
Your suggestion to format install is what I came to find as well while searching. It seems like this is the absolute last possible thing to do, and as far as I can read it does a full deletion of the partition and create a new and format it like a brand new drive, and then installs a fresh JUNOS.
I did find the link you provided also, but I also fell over the official procedure for this, which seems to be extremely easy:
https://supportportal.juniper.net/s/article/EX-Performing-and-resolving-any-common-issues-during-Format-Install-on-legacy-EX-platforms?language=en_USWhile writing this reply the switch just finished doing install with --format on, and the output of show virtual-chassis is here:
root> show virtual-chassis
Virtual Chassis ID: a7ee.e9dc.9446
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 BM0212511494 ex4200-24t 128 Master* N VC
Member ID for next new member: 1 (FPC 1)
It still says virtual chassis mode is enabled?
The error I have is:
root> show chassis alarms
1 alarms currently active
Alarm time Class Description
2020-10-21 16:28:40 UTC Major Management Ethernet Link Down
Which is perfectly fine, I am only running console with no other connections.
Did I succeed? This virtual chassis enabled this is throwing me off, could be a standard thing?
------------------------------
Jesper Lammert
------------------------------
Original Message:
Sent: 07-27-2022 09:56
From: PAUL PETERSON
Subject: Juniper EX4200 remove vc and revert to default
Try 'request system zeroize'. if that doesn't work you can try doing a format install.
See post number 7 on this thread:
EX4200 USB software upgrade | Switching (juniper.net)
------------------------------
PAUL PETERSON
Original Message:
Sent: 07-27-2022 08:20
From: Jesper Lammert
Subject: Juniper EX4200 remove vc and revert to default
Hello all,
First time poster, long time reader.
I got a bunch of Juniper EX4200 that I'd like to repurpose. I am by no means any expert in these switches, I usually work with Cisco and HP.
These switches are part of a big virtual chassis, and I haven't been able to find any solution on how to make them not be part of this virtual chassis. All of them seem to call for some master switch before performing anything, and of course I don't know anything about the switches, but none of them seem to be a master.
I press space when the switch is booting, and using boot -s and type recovery. Normal startup won't let me log in because it keeps calling for the master.
Then I have run:
load factory-default
delete system commit factory-settings
set root-authentication plain-text-password
juniper1 as password
Then commit (it won't commit without a password)
rebooting has no effect here. I get the same problems when trying to login.
When i boot up with boot -s and recovery the switch tells me this:
warning: This chassis is operating in a non-master role as part of a virtual-chassis (VC) system.warning: Use of interactive commands should be limited to debugging and VC Port operations.warning: Full CLI access is provided by the Virtual Chassis Master (VC-M) chassis.warning: The VC-M can be identified through the show virtual-chassis status command executed at this console.warning: Please logout and log into the VC-M to use CLI.
Of course I don't know the master, nor the passwords.
I tried with this:
root# run request virtual-chassis vc-port set interface vcp-0 disable
But output is:
error: the chassis-manager subsystem is not running
So the big question here is, what is the magical command that will revert this chassis into a stand-alone chassis?
------------------------------
Jesper Lammert
------------------------------