I have a Juniper EX4200 series 8PoE that was donated to me as a lab asset. The problem is tha it has a configuration on it and i have no usernames/passwords. When i go through the password recovery process this is what happens:
/kernel data=0x8e55b8+0x950d0 syms= [0x4+0x7aab0+0x4+0xae2b8]
Hit [Enter] to bbot immediately. or space bar for command prompt.
Type '?' for list of commands, 'help' for more detailed help.
loader> boot -s
Then it continues to boot but then i get the following:
System watchdog timer disabled
Enter root password, or ^D to go multi-user
Once i press the return key it continues the boot process, never takes me to CLI ust finishes booting and ends up at a hostname and login prompt.
Is there any way to break into this device to clear the configuration so i can use it? Please help and thank you for any assistance that you can provide.
It looks like you might have missed the step where you type "recovery" at the prompt (after boot -s to boot into single-user mode)?
I agree but that's the issue it doesn't even give me the option for this step:
Enter full path name of shell or 'recovery' for root password recovery or RETURN for /bin/sh: recovery
It goes straight to the propmt of asking for the root password so i never get to type recovery. Any suggestions? Thanks for the reply.
Why don't you do an installation and format the filesystem in the same time?
I know it's not what you are looking for, but it will save some time.
This in the case that you don't need the configuration present already.
=====If this worked for you please flag my post as an "Accepted Solution" so others can benefit. A kudo would be cool if you think I earned it.
No i don't need the configuration that's currently on there, do you have a link to the process that you are referring to?
Thank you for your assistance.
And what if the need is to keep the configuration?
You can use single user mode from the console port to do a root password recovery following this kb article. This does require you power off the switch and have physical access to the serial console port for the operation.
Note that this doesn't work for a stack. You have to seperate the master from the stack and update the master individually.