Procurve 2626's lost config after power outage

[Bruce Campbell_3]

After a power flicker here, three 2626's
running H.10.83 gave

CONFIGURATION INITIALIZATION FAILED:
Invalid Product Number in Config File

and needed to be factory reset with the buttons, and reconfigured from scratch.

We have had problems losing parts of Procurve configs on power loss before,

but never the whole config before.

Any suggestions on how to avoid this ?

[Helper]

Hi,

Since how many times these switchs was running ?

How many 2626/2650 switchs do you have ? Is 3 failing switches is a high number ?

Do you have corresponding log events ?

After a full recovery of these switch are you able to reproduce this behaviour ?

This should be a hardware issue.

Bye.

[Bruce Campbell_3]

 The 3 switches in question have been in service since January 2009.

We have 53 Procurve 2626's at our site,  486 Procurve 2650's, and 549 other Procurve models.

Early December 13, there was a power outage/flicker, and 159 switches

rebooted clean, and three 2626's lost their configs.

I don't recall a past incident with these specific symptoms.  We have had 2650's lose their

SFP port config after power flickers, but not the whole config (if I recall correctly)

There is nothing noteworthy in the logs.

We have not tried to reproduce the issue.

[Helper]

Hi,

the best way is to try to reproduce this issue on these three devices, then you will be aware of the situation redundant hardware failure or one-time issue.

Bye.

[Bruce Campbell_3]

It happened again yesterday on two 2650's
running H.10.83. There was a power outage,
about 25 switches lost power for an hour,
when the power came back, the two 2650's
in question lost parts of their configs.

This time the devices came up, but they had

lost some fragments of their configuration.

They could be detected via LLDP from their

neighbour,  but had lost vlans on their uplinks,

and other parts of the config.

Something similar on a 2610 in Dec/09

https://strobe.uwaterloo.ca/~twiki/bin/view/ISTNS/ISTReportToCNAGDec2009

[jefflj]

Hi Bruce,

Have you contacted  HP Networking support?  I'd bet this is not intended behavior and they would want to help out.

In another direction, Do you keep config files backed up on a tftp server?  Although this approach will not solve your problem, and is not intended to minimize the issue you're seeing, it will allow you to recover configs relatively quickly when the situation happens again.