WS-3 lockup

[wtm]

Twice now, we have had a WS-3 unit just lockup. It still provides POE to all devices connected, but it will then seem to intermittantly go up and down (or internally reboot itself) During this time period, the unit can not be accessed via the normal gui or cli routes. Only thing that corrects the issue is a complete power out re-boot.

This happened to the unit about 2 months ago, and it has been working fine up until this week. Then it went into complete lockout again. We tried to get into it remotely but no access. Had to make a physical trip and pull the power on it. It came back up and worked as normal, but we replaced the unit out of caution anyway.

Using 2.0.7 firmware on it.

We can't seem to find anything that may have caused this lockup. Power looks good, it is on a full D.C. run 48 volt power buss with battery backup to it. Site has good grounding. All devices connected to the switch still run, and none seem to have any problems before, during, or after the switch event.

Only other thought is a possible hack to the CPU via Ethernet connection? It does resemble what a Ubiquiti AP will do when it gets hacked (8.5.12 firmware), AP starts re-booting due to a memory stack overload, and it then has to be manually re-booted to correct the problem. But at least you can get access to the AP to do it. (not the case with the switch)

Open to any thoughts on this, as we can't find anything that may have caused it, unless it is a physical problem with this particular unit (hoping so, as we have others out there that so far are working well)?

[wtm]

Well, here we are again, having the same problem!

Except, the original unit was replaced by a new unit. Now this one is doing the same thing. No Gui access, No Ping to the unit, POE's seem to stay working, but data in and out of the unit keeps going up and down.

[Dave]

a developer is looking into ws3 issues...

[wtm]

Dave, this one has stayed locked up, can't even ping into it. I am going to ship it to you, see what you can find on it. We have had to put in some WS-26 units to replace it, and they seem to work fine there, but we really need the 10 gig switch buss.

[Dave]

developer believes he found the ws3 lock up issue..he is still looking at some other ws3 minor bugs before releasing code

[wtm]

Well, just RMA'd our unit, so you will have one that he can use to test on, or possibly use to find any other problem.

[wtm]

Well, went to turn off then on a 48vh port on a WS-3 switch yesterday. As we turned it back on again, the switch went entirely blank. Waited a few minutes still nothing, pulled the fuse, waited 30 seconds put it back in. power light came on, then about 2 minutes later, SFP+ arrows came on (Assuming SFP connection), waited 5 more minutes, and NO POE or switch lights came on. Pulled fuse again, and went through the same scenerio. NOTHING !

Luckily had another WS-3 sitting on the shelf there as a spare. Programmed it up, and replaced the original one. It is currently working?


We will be pulling out ALL our WS-3 switches until this is solved. We put in some WS-26-500-DC units in their place, but we are having problems with the "Bonding" issues that i posted on this forum last year. Seems that Mikrotik and Netonix do not see eye to eye on bonding ports.

Hope you can get these WS-3 units fixed quickly ?

[wtm]

Hey Dave, anything new on getting the WS-3 units fixed?

[michaeln416]

We continue to have this problem with our WS3. It just happened again today spontaneously in the middle of the day. This seems to be happening on its own once every 3 months, give or take. When we are making changes to its configuration it locks up more often, usually while we are logged into it and still applying the changes. It is so temperamental that we have a 2nd WS3 on the rack beside it with the previous config settings so that we can quickly back out if needed.

This is becoming very tiring. Please resolve this and the other issues that have been reported with the WS3.