I just wondered whether there has been any progress on eliminating these 'random reboots' as we are severely suffering from it on our network at the moment. We have about 70 Netonix switches and they are all rebooting seemingly at random, causing their connected radios to be power cycled. Sometimes we can go 3-4 days with no problems, and other days we can see many tens of switches rebooting. It's turning into a disaster zone. On our remote syslog server I am seeing 'Detected cold (watchdog) boot'. Nothing is syslogged before the reboot occurs.
Last month we were running 1.4.9 on all switches apart from 2-3 units where we were trialling 1.5.0. After the first major 'reboot storm' (described in
this thread) I upgraded all switches to 1.5.0 to try to prevent recurrence but the reboots seem to have got more frequent if anything, although that might be a co-incidence. We have around 7 Mikrotik switches which occasionally log packet loops ("etherX: bridge port received packet with own address as source address, probably loop") but I'm not sure whether this is an 'erroneous error' or if there is a genuine intermittent loop / storm and whether it's possibly causing the Netonix reboots.
Should I try enabling Loop Protection on all our Netonix Switches? What about the other Storm Control settings i.e. Broadcast / Multicast / Unicast / Pause Frame? Is there any downside or risk to enabling these settings?
Thanks
Glenn
