WS-26-400-IDC & WS-12-250-DC Random Reboots

DOWNLOAD THE LATEST FIRMWARE HERE
dmccaslin
Member
 
Posts: 1
Joined: Thu Apr 30, 2026 3:53 pm
Has thanked: 0 time
Been thanked: 0 time

WS-26-400-IDC & WS-12-250-DC Random Reboots

Fri May 01, 2026 5:55 pm

Hello all,

I would like to preface this by saying I am very new to the Netonix Platform. I love it so far. I had some questions regarding them though as we have had some recent outages due to them rebooting seemingly for no reason.

We have a very important microwave PTP that not only keeps our WISP clients connected but also supports the Public Safety works for the county it resides in. In the last few weeks we have had outages due to the switches rebooting. 1 time on each side. Checking the logs after the reboot doesn't seem to point to anything specific regarding the reboot except an entry that states switch [877]: Detected cold (watchdog) boot. I have checked and from what I can tell we don't even have watchdog setup on any of them. For clarification there are 2 switches on each end. The 2 - 400s on one end of the link and the 2 - 250's on the other. I have read many posts on here trying to figure out if anyone has had similar issues and while I can see there are some regarding reboots, this isn't a continuous cycle. I eventually landed on what I believe the issue to be is, STP. The setup we have is 2 carriers that are bonded together giving us a 4+0 link. We have dedicated management cables going to each radio. between the radio there are 2 fiber cables. One of them is for link bonding/mgmt. The other is for the actual traffic. We have since disabled it but in band management was also an option. The reason I fall on STP being the cause is that the logs are absolutely filled to the brim of STP logs where the ports are constantly going from forwarding to discarding and back to forwarding which to me sounds like STP is working. I have seen in a few posts that if the switches sense a loop they can reboot. We need both carriers on each side to have dedicated management for access. I can take inband management out of the equation as we have other means of access to both sides. Is there a way to negate this issue (if it even is the issue)? Appreciate any info and apologies if I'm just ignorant in understanding this :lol:

Return to Hardware and software issues

Who is online

Users browsing this forum: Google [Bot] and 40 guests