HPE Aruba Networking & ProVision-based
1832235 Members
2563 Online
110041 Solutions
New Discussion

HP Procurve 2650 sometimes stucks in bootloop

 
Drudge
Occasional Visitor

HP Procurve 2650 sometimes stucks in bootloop

Hello dear community members,

 

I have bought an used HP Procurve 2650 (J4899A) switch. Unfortunately the switch is not working very well.

The switch is stucked in a kind of bootloop. Here is the console output:

 

initializing...

ROM information:
Build directory: /sw/rom/build/fishrom(mkfs)
Build date: Jul 21 2004
Build time: 10:45:52
Build version: H.08.02
Build number: 137

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

Decompressing...done.

initializing.

 Then it repeats itself. When the switch rebooted three or four times, I can unplug it from the power source and plug it in again. Then the switch is booting at the first time.

 

What can cause this error? The switch only stucks in the bootloop if it was not on power for a couple of minutes. Is there a kind of BIOS-battery inside which may be empty?

 

Additionally I want to know if the firmware ist the most recent one. The firmware is from 2004 and I could imagine there is a new one. But the support-links in the webinterface are outdated and do only redirect me to the hp start page.

I only found a manual by google-ing, but no firmware :(

 

The third think I want to know is whether I can submit a warranty claim if this should be a switch error. As I said, I am not the original customer of the switch but bought the switch as a used one. The HP gurantee checking page said that I have gurantee until 2104.

 

Thanks in advance!

Mark Lukas

 

 

Edit: I upgraded the firmware to the newest version (the ROM version is still the same) and the behaviour still persists.

I found out that the switch does not boot if it is "cold". If the switch is powered a couple of minutes and is warm, it boots without any problems, even when unplugged and plugged in again. But when the switch was shutted down some minutes, the error occures again.

 

Is that probably a hardware error I cannox fix myself? :(