If it won't zeroize fully, you have stacking config I bet. Been there, done that.
My process is this:
*remove stack config files so zerioize works completely*
cd /config/vchassis
rm *
rmdir /config/vchassis
zeroize + media option
create usb using balenaEtcher using the junos-install-media-usb-ex-arm-32-22.2R1.9.img.gz file, windows will say it's unformatted after but that is ok
reboot the switch, ctrl-c during the 2 second windows, pick boot options then pick boot from usb (option 4?) - this is in cli via console but not typing commands, more picking from a menu like windows safe mode
boots from usb, loads latest Junos
set partial config, https web management, ip, dns, default route, switch name, etc.
check to see basic JWEB is working
then update JWEB via GUI browse to file
finish config
Let me know if that helps!
------------------------------
Jason Fagan
------------------------------
Original Message:
Sent: 01-13-2023 03:09
From: Erik Slagter
Subject: Linecard shown after zerioze.
That is interesting. I have been doing quite a few zeroizing lately,
using verious JunOS versions and I haven't seen this behaviour. What I
have seen several times is that somehow a vc configuration gets
remembered and the unit still tries to do "logging to master..."
afterwards. This is even with no vc ports enabled at all, which would be
silly anyway.
So sorry no solution. Maybe a second round of zeroizing helps?
Original Message:
Sent: 1/12/2023 4:34:00 AM
From: gedebook2009
Subject: Linecard shown after zerioze.
Hi. I have EX2300-C at Junos 19.1R3-S5.3. I just cleanup everything by using.
> request system zerioze
And it's rebooted. Then I relogin into my switch. But the switch seems saving my old root password, although it should be no password at all. And the output shown like this.
FreeBSD/arm (Amnesiac) (ttyu0)login: rootJan 12 15:44:26 login: login_getclass: unknown class 'junos-login-defaults'Password:Last login: Thu Jan 12 15:36:24 on ttyu0--- JUNOS 19.1R3-S5.3 Kernel 32-bit JNPR-11.0-20210212.420a184_builroot@:LC:0% cliJan 12 15:44:26 login: login_getclass: unknown class 'junos-login-defaults'Jan 12 15:44:38 cli: login_getclass: unknown class 'j-idle-timeout'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.{linecard:0}root>
I cannot make any operation since it is not a master routing-engine. How it could be happened? Any advice how to resolve it?