Netonix Forums

I have specified Netonix products to be used for our company projects.

I just had an incident where a WS-8-150-AC ceased operation during service,
and would not function until I brought it back to the shop bench and performed the procedure holding the reset button for 45 seconds.

During the outage the following was observed:
- No ethernet connectivity
- No ethernet link lights
- No PoE indication
- No response on Serial port
- PWR light does light
- Fan runs, then idles out about 2 minutes 30 seconds after power up.

Again, the reset button for 45 seconds cleared the issue.

The unit is running on 1.5.1.rc11

The disruption to service was major and has put our customer relationship at risk.

I have 2 other units currently in service and am very concerned...

Has anyone else experienced this?

How old is the unit?

What all are you powering with the unit?

Is the unit accessible from the web (valid IP).

Is the unit plugged into a UPS, because if you have a power blip meaning the switch loses power for a second then power is restored the unit can come up in a weird state as it never had time to power down properly. This can happen to any embedded device.

Also I would use v1.5.1rc12 as there was a recent fix for a bug introduced accidentally in v1.5.1rc2 regarding STP/RSTP/MSTP which would affect LACP LAGs as well, see release notes.

Explain how the unit is being used, what is it plugged into, and what is it powering.

Considering there are almost 10,000 of these units in service around the world and is one of our most popular units I would think they are pretty reliable. However with that said there are bad units just like with any other manufacturer.

Well over a year ago we had a batch of WS-6-MINI and WS-8-150-AC units with "possible" bad 3V CAPs which could result in problems which is documented in the BENCH test post:

viewtopic.php?f=6&t=2780#p19221

We just received the unit, last week, from a distributor called WAV.

The unit was running on a UPS.

It was powering a Cambium ePMP2000 and a small Samsung WEA-412h WiFi AP.

The last change I made to it (minutes before the failure), was to enable Flow Control on the PoE port the Cambium ePMP2000 was on.

kb8doa wrote:We just received the unit, last week, from a distributor called WAV.

The unit was running on a UPS.

It was powering a Cambium ePMP2000 and a small Samsung WEA-412h WiFi AP.

The last change I made to it (minutes before the failure), was to enable Flow Control on the PoE port the Cambium ePMP2000 was on.

Flow control is a tricky thing to use with wireless gear and has been a long and lengthy debate here on this forum, the UBNT forum, and on other platforms like Facebook groups. If implement right on small routed Layer 2 segments if can be a benefit but on larger flat Layer 2 segments I would not enable it unless you fully understand what can happen and why.

Flow control can cause a packet lock where the switch has received so many pause frames that it fills up its buffers and stops accepting packets. Again you can do a search on this forum and read some very lengthy detailed posts and discussions if you like.

I would leave Flow Control OFF for awhile and if you have no problems then enable it and if this then happens again you have a starting point as to the cause.

What we experienced was much more than just a "packet lock".

The switch ceased operation, and power cycling it (several times) did not resolve it.

During this time, no LED indications - no ethernet functionality - nothing...

Taking it back to the bench, and holding the reset button in - to default it
was the only way to get it operational again.

I would have consoled into it before I factory defaulted it and looked around.

Maybe set laptop IP to something that could ping it then try and access it.

No power on the ethernet ports, even for non-PoE.
The ports would NOT light up to indicate an ethernet connection.
How would I have been able to establish any sort of IP connection?

kb8doa wrote:No power on the ethernet ports, even for non-PoE.
The ports would NOT light up to indicate an ethernet connection.
How would I have been able to establish any sort of IP connection?

How about a console connection?

It is possible the unit has defective 3V CAP issue if it is over a year old which could cause the unit to LOCK UP.

You can learn how to bench test it here: viewtopic.php?f=6&t=2780#p19221

Or it could have been a fluke or possible a corrupted config/flash which the default cleared.

If it is accessible to the web and you are running old firmware it could have been hacked, also if accessible to the web or even your network I would upgrade to v1.5.1 or later and implement the access control list