Switches, Hubs, and Modems
cancel
Showing results for 
Search instead for 
Did you mean: 

Procurve 2524 boots to Monitor ROM Console

dB LEE
Advisor

Procurve 2524 boots to Monitor ROM Console

I have a switch here that is apparently
stuck in ROM Console mode. Every time power is
cycled I have to enter:
=> quit
from the ROM console so the switch will procede to boot.

I've tried the erase command:
Procurve# erase startup-config
and even a successful TFTP Firmware update with no success.

The switch was delivered to me in this state
and I have no idea how it got this way.
Does anyone know how to clear out this mode?

Here is some ROM Console info:
=>
=>boot
ROM information:
Build directory: F:/switch/arm/rom
Build date: Aug 11 2001
Build time: 18:14:53
Build version: F.02.01
Build number: 03

OS identifier found at @ 0x17070000
Verifying Image validity ...
CRC on OS image header Passed
CRC on complete OS image file Passed
Valid OS image @ 0x17070000

HP ProCurve Switch 2524 (J4813A)
ROM Build Directory: F:/switch/arm/rom
ROM Version: F.02.01
ROM Build Date: 18:14:53 Aug 11 2001
ROM Build Number: 03

=>

Thanks ,
-dB


3 REPLIES
Matt Hobbs
Honored Contributor

Re: Procurve 2524 boots to Monitor ROM Console

From the BootROM you can also download the firmware via Xmodem. Before doing this you'd want to set the baud rate higher (115200) followed by matching the settings in your terminal program.

e.g.
baud 115200 (reconfigure your terminal app)
download

If that doesn't recover it sounds faulty.
dB LEE
Advisor

Re: Procurve 2524 boots to Monitor ROM Console

Matt,
Is there a legitimate way to force this switch to stop at the ROM console after power-up rather than proceding to boot?
Matt Hobbs
Honored Contributor

Re: Procurve 2524 boots to Monitor ROM Console

On the newer switches you can use the 'jp 1' or 'jp 2' to boot to the different boot images. Since the 2524 only has one you may be able to use 'jp 1' - but it looks as though you've used 'boot' which is the same thing.

It definitely should not be doing this and if an xmodem re-flash does not help, it's faulty.