Lost config due to power outage.

[Tony]

All -

I saw 2 case of the switch (standalone or stack) with 55xx series and running the old firmware version of release v5.1.x.x. is it anything to prevent for this problem w/o upgrade the latest of firmware?

it was a pain to recovered....

Cheers..

[TankII]

1)  back up your config after EVERY change.
2)  disable autosave, wr mem, then re-enable autosave.  Seems to fix this issue on older switches.

TankII

[Tony]

Thanks, Tankii

[Johan Witters]

Unfortunately, it is something that just "happens", regardless model / software / autosave.

I've had config losses on all types of switches, old firmware and recent, with and without autosave enabled. In most cases, if you miss a part of the config it has to do with forgetting to manually save the config on devices where autosave has been disabled.

Last time I had the issue was with a ERS3524GTX-PWR, running latest software in a 3 unit stack. After a reboot of the stack, configuration of unit #3 was gone. I put it back in and unplugged or rebooted a few times, but nothing strange happened..

I've read that new firmware should introduce a backup configuration to prevent defaulting if the primary config gets corrupted.

Just make sure you always have a recent copy of the configuration, in case you have to put it back in the box.

[LondonDragon]

Have to agree with Johan,

I also tend to have an issue with the switch #3 in the stack loosing its configuration and defaulting to VLAN 1.

Any of you guys running NSNA?

[TankII]

NSNA?  Don't know that acronym.
We've got several stacks of three switches, with no issues, both units with and without L-3 licenses.

Our trick is to disable autosave, wr mem to force a save, then re-enable autosave.  It appears to work fine, even though reboots in the future.
Sometimes though, you have to 'clear log nv', then 'clear log' to free up space, wr mem, make sure logging is set to overwrite and not latch before you re-enable autosave.

TankII

[LondonDragon]

NSNA?  Don't know that acronym.

Also known as SNAS!

[Johan Witters]

Nope, not in use..

Untill now I've not been able to see a clear line in the issue. I've had it happen on several models in the 2500/3500/4500 series switches, can't remember any issues with 5xxx and 8xxx though.

The issue seems to be random, testing 10 identical switches might result in 1 failure, or none, both in standalone and stacking configurations.