WS-12-250-DC switch config loss upon de-powering port/saving

[ch0g]

Hi all

We are a wisp running very many WS-12-250-DC through our network, including multiple at key sites. We have experienced on 3 separate occasions a switch condition (on different switches/different parts of our network) whereby the switch will stop passing traffic on our production network. Following a power cycle of the switch, the switch is no longer contactable and POE is disabled on all ports. A procedure involving the reset hole at boot for 1 minute is required to recover to defaults.

The failure appears to occur after a configuration save, when choosing to POE OFF a particular port.

I will say, Netonix has been great for us, a fantastic product we will continue to support.

Thanks for your input

Cheers

[sirhc]

Can you please post up the a screen grab of the Device/Status TAB of the units that causing you issues.

See my post signature for instructions on uploading screen grabs/attachments.

[ch0g]

Attached

[ch0g]

Here is another switch we took out of production (the initial time it happened).

[sirhc]

So the input voltage is around 13-14 volts.

Please describe how the switch is powered.

How much is the total watts being used.

Unselect all ports and show the main Status TAB which will show what each port is delivering and at the top the total watts being used including the switch plus POE.

[ch0g]

The switch is directly powered by a 130ah 12v AGM battery. Supply charge mode from mains charger.

Complete current draw is 44.2W

[sirhc]

We are hoping to release a firmware fix today for WS-12-250-DC and WS-26-500-DC that should fix some issues that some people have had with these 2 models.

We had made an attempt to fix these issues with v1.5.0rc1 and rc2 but rc2 made things worse and we pulled it and have spent the last week doing fixes and MORE TESTING.

v1.5.0rc1 would reduce CPU overhead but did not fix the issues
v1.5.0rc2 "could" cause a worse issue and could require the unit to be RMA to fix - WARRANTY OF COURSE
we took down v1.5.0rc2 as soon as some people reported issues with it
We have spent the last week debugging and testing and hope to release it tonight or tomorrow.

Please try v1.5.0rc3 once released.