WS-3 lockup
Posted: Tue May 31, 2022 11:46 am
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)?
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)?