Page 1 of 2
WS-12-250-AC rebooting all ports
Posted: Mon Sep 28, 2015 11:11 pm
by zrob_12
Running Firmware Version 1.3.3
No ping watchdog configured
Netonix switch randomly reboots all ports (no consistency, but typically after 15-30 minutes).
Thoughts or suggestions anyone?
Re: WS-12-250-AC rebooting all ports
Posted: Mon Sep 28, 2015 11:13 pm
by zrob_12
New installation BTW
Re: WS-12-250-AC rebooting all ports
Posted: Mon Sep 28, 2015 11:21 pm
by Dave
can you do a screen capture of main status tab page, and also of the status page under the device tab?
Re: WS-12-250-AC rebooting all ports
Posted: Mon Sep 28, 2015 11:42 pm
by sirhc
Are you sure you did not have a ping watch dog configured on each devices and they can not ping that anymore?
I did that once, changed the IP they were pinging for their ping watchdog and you get that.
These are the things to check:
1) If the switch is not rebooting then I really highly doubt it is the switch so check the up time on the switch.
2) Check the log of the switch, see what it says and post it up.
3) How many watts is your total usage (Displayed on Main Status page when you select no ports).
Please post up a grab of your main Status Tab and the Device/Status Tab.
Please gather some more information, but if this was a problem with the firmware or the switch design you would think hundreds of people would be screaming as there are over 5,000 units now out there including my WISP?
Re: WS-12-250-AC rebooting all ports
Posted: Tue Sep 29, 2015 12:20 am
by zrob_12
Wow, thanks for the fast response.
Checked all ping watchdogs on units and all are set to ping Netonix switch. I disabled ping watchdog on a few to determine if that might be cause.
Total use around 80W pretty consistent.
- post.jpg (220.21 KiB) Viewed 6050 times
- post2.jpg (88.77 KiB) Viewed 6049 times
Re: WS-12-250-AC rebooting all ports
Posted: Tue Sep 29, 2015 12:22 am
by sirhc
zrob_12 wrote:Wow, thanks for the fast response.
Checked all ping watchdogs on units and all are set to ping Netonix switch. I disabled ping watchdog on a few to determine if that might be cause.
Total use around 80W pretty consistent.
Yes, see if the units that you disabled their ping watchdog do not reboot and let us know.
Re: WS-12-250-AC rebooting all ports
Posted: Tue Sep 29, 2015 1:28 am
by sirhc
Everything looks fine on your screen grabs.
Let us know if the units you disabled watch dog on stay up.
It has to be something along those lines.
Re: WS-12-250-AC rebooting all ports
Posted: Wed Sep 30, 2015 1:44 am
by zrob_12
Well, things seemed to improve all around for a bit after removing ping watchdog from only a few of the units interestingly enough. However, that was short-lived and the units are still rebooting. When the units reboot, the ports on the Netonix turn to red as they do when first booting up if that tells you anything...
Re: WS-12-250-AC rebooting all ports
Posted: Wed Sep 30, 2015 1:45 am
by zrob_12
Here is a small snapshot of the log:
Sep 28 23:16:13 syslogd started: BusyBox v1.19.4
Sep 29 15:19:14 kernel: link state changed to 'down' on port 8
Sep 29 15:19:14 kernel: link state changed to 'down' on port 11
Sep 29 15:19:14 kernel: link state changed to 'down' on port 1
Sep 29 15:19:14 kernel: link state changed to 'down' on port 2
Sep 29 15:19:14 kernel: link state changed to 'down' on port 3
Sep 29 15:19:14 kernel: link state changed to 'down' on port 4
Sep 29 15:19:16 kernel: link state changed to 'up' on port 11
Sep 29 15:19:17 kernel: link state changed to 'up' on port 3
Sep 29 15:19:17 kernel: link state changed to 'up' on port 4
Sep 29 15:19:17 kernel: link state changed to 'up' on port 2
Sep 29 15:19:17 kernel: link state changed to 'up' on port 1
Sep 29 15:19:17 kernel: link state changed to 'up' on port 8
Sep 29 15:19:17 kernel: link state changed to 'up' on port 6
Sep 29 15:19:21 kernel: link state changed to 'down' on port 4
Sep 29 15:19:23 kernel: link state changed to 'up' on port 4
Sep 29 15:19:37 kernel: link state changed to 'down' on port 11
Sep 29 15:19:38 kernel: link state changed to 'down' on port 1
Sep 29 15:19:38 kernel: link state changed to 'down' on port 6
Sep 29 15:19:38 kernel: link state changed to 'down' on port 8
Sep 29 15:19:38 kernel: link state changed to 'down' on port 3
Sep 29 15:19:39 kernel: link state changed to 'down' on port 4
Sep 29 15:19:39 kernel: link state changed to 'up' on port 11
Sep 29 15:19:39 kernel: link state changed to 'up' on port 1
Sep 29 15:19:39 kernel: link state changed to 'up' on port 8
Sep 29 15:19:40 kernel: link state changed to 'up' on port 6
Sep 29 15:19:40 kernel: link state changed to 'up' on port 3
Sep 29 15:19:41 kernel: link state changed to 'down' on port 2
Sep 29 15:19:41 kernel: link state changed to 'up' on port 4
Sep 29 15:19:42 kernel: link state changed to 'down' on port 6
Sep 29 15:19:42 kernel: link state changed to 'down' on port 8
Sep 29 15:19:42 kernel: link state changed to 'down' on port 3
Sep 29 15:19:42 kernel: link state changed to 'up' on port 2
Sep 29 15:19:43 kernel: link state changed to 'down' on port 1
Sep 29 15:19:44 kernel: link state changed to 'up' on port 6
Sep 29 15:19:44 kernel: link state changed to 'up' on port 8
Sep 29 15:19:44 kernel: link state changed to 'up' on port 3
Sep 29 15:19:44 kernel: link state changed to 'up' on port 1
Sep 29 16:17:58 kernel: link state changed to 'down' on port 3
Sep 29 16:17:58 kernel: link state changed to 'down' on port 5
Sep 29 16:17:58 kernel: link state changed to 'down' on port 6
Sep 29 16:17:58 kernel: link state changed to 'down' on port 7
Sep 29 16:17:58 kernel: link state changed to 'down' on port 8
Sep 29 16:17:58 kernel: link state changed to 'down' on port 11
Sep 29 16:17:58 kernel: link state changed to 'down' on port 1
Sep 29 16:17:58 kernel: link state changed to 'down' on port 2
Sep 29 16:17:58 kernel: link state changed to 'down' on port 10
Sep 29 16:17:58 kernel: link state changed to 'down' on port 4
Sep 29 16:18:00 kernel: link state changed to 'up' on port 11
Sep 29 16:18:01 kernel: link state changed to 'up' on port 3
Sep 29 16:18:01 kernel: link state changed to 'up' on port 4
Sep 29 16:18:01 kernel: link state changed to 'up' on port 10
Sep 29 16:18:01 kernel: link state changed to 'up' on port 1
Sep 29 16:18:01 kernel: link state changed to 'up' on port 7
Sep 29 16:18:01 kernel: link state changed to 'up' on port 2
Sep 29 16:18:01 kernel: link state changed to 'up' on port 6
Sep 29 16:18:01 kernel: link state changed to 'up' on port 8
Sep 29 16:18:01 kernel: link state changed to 'up' on port 5
Sep 29 16:18:05 kernel: link state changed to 'down' on port 4
Sep 29 16:18:05 kernel: link state changed to 'down' on port 10
Sep 29 16:18:07 kernel: link state changed to 'up' on port 4
Sep 29 16:18:07 kernel: link state changed to 'up' on port 10
Sep 29 16:18:21 kernel: link state changed to 'down' on port 11
Sep 29 16:18:22 kernel: link state changed to 'down' on port 1
Sep 29 16:18:22 kernel: link state changed to 'down' on port 6
Sep 29 16:18:22 kernel: link state changed to 'down' on port 7
Sep 29 16:18:22 kernel: link state changed to 'down' on port 8
Sep 29 16:18:22 kernel: link state changed to 'down' on port 3
Sep 29 16:18:22 kernel: link state changed to 'up' on port 11
Sep 29 16:18:22 kernel: link state changed to 'down' on port 4
Sep 29 16:18:23 kernel: link state changed to 'down' on port 10
Sep 29 16:18:23 kernel: link state changed to 'up' on port 6
Sep 29 16:18:23 kernel: link state changed to 'up' on port 1
Sep 29 16:18:23 kernel: link state changed to 'up' on port 7
Sep 29 16:18:23 kernel: link state changed to 'up' on port 3
Sep 29 16:18:23 kernel: link state changed to 'up' on port 8
Sep 29 16:18:25 kernel: link state changed to 'up' on port 4
Sep 29 16:18:25 kernel: link state changed to 'down' on port 2
Sep 29 16:18:25 kernel: link state changed to 'up' on port 10
Sep 29 16:18:25 kernel: link state changed to 'down' on port 5
Sep 29 16:18:26 kernel: link state changed to 'down' on port 6
Sep 29 16:18:26 kernel: link state changed to 'down' on port 7
Sep 29 16:18:26 kernel: link state changed to 'down' on port 8
Sep 29 16:18:26 kernel: link state changed to 'down' on port 3
Sep 29 16:18:26 kernel: link state changed to 'up' on port 2
Sep 29 16:18:26 kernel: link state changed to 'down' on port 1
Sep 29 16:18:26 kernel: link state changed to 'up' on port 5
Sep 29 16:18:27 kernel: link state changed to 'up' on port 6
Sep 29 16:18:27 kernel: link state changed to 'up' on port 8
Sep 29 16:18:27 kernel: link state changed to 'up' on port 7
Sep 29 16:18:27 kernel: link state changed to 'up' on port 3
Sep 29 16:18:28 kernel: link state changed to 'up' on port 1
Sep 29 18:25:17 kernel: link state changed to 'down' on port 6
Sep 29 18:25:17 kernel: link state changed to 'down' on port 7
Sep 29 18:25:17 kernel: link state changed to 'down' on port 8
Sep 29 18:25:17 kernel: link state changed to 'down' on port 11
Sep 29 18:25:17 kernel: link state changed to 'down' on port 1
Sep 29 18:25:17 kernel: link state changed to 'down' on port 2
Sep 29 18:25:17 kernel: link state changed to 'down' on port 3
Sep 29 18:25:17 kernel: link state changed to 'down' on port 4
Sep 29 18:25:19 kernel: link state changed to 'up' on port 11
Sep 29 18:25:20 kernel: link state changed to 'up' on port 4
Sep 29 18:25:20 kernel: link state changed to 'up' on port 2
Sep 29 18:25:20 kernel: link state changed to 'up' on port 3
Sep 29 18:25:20 kernel: link state changed to 'up' on port 6
Sep 29 18:25:20 kernel: link state changed to 'up' on port 1
Sep 29 18:25:20 kernel: link state changed to 'up' on port 8
Sep 29 18:25:20 kernel: link state changed to 'up' on port 7
Sep 29 18:25:24 kernel: link state changed to 'down' on port 4
Sep 29 18:25:26 kernel: link state changed to 'up' on port 4
Sep 29 18:25:40 kernel: link state changed to 'down' on port 11
Sep 29 18:25:40 kernel: link state changed to 'down' on port 1
Sep 29 18:25:40 kernel: link state changed to 'down' on port 6
Sep 29 18:25:40 kernel: link state changed to 'down' on port 7
Sep 29 18:25:40 kernel: link state changed to 'down' on port 8
Sep 29 18:25:41 kernel: link state changed to 'down' on port 3
Sep 29 18:25:41 kernel: link state changed to 'up' on port 11
Sep 29 18:25:41 kernel: link state changed to 'down' on port 4
Sep 29 18:25:42 kernel: link state changed to 'up' on port 1
Sep 29 18:25:42 kernel: link state changed to 'up' on port 7
Sep 29 18:25:42 kernel: link state changed to 'up' on port 8
Sep 29 18:25:42 kernel: link state changed to 'up' on port 6
Sep 29 18:25:42 kernel: link state changed to 'up' on port 3
Sep 29 18:25:43 kernel: link state changed to 'up' on port 4
Sep 29 18:25:43 kernel: link state changed to 'down' on port 2
Sep 29 18:25:45 kernel: link state changed to 'down' on port 6
Sep 29 18:25:45 kernel: link state changed to 'down' on port 7
Sep 29 18:25:45 kernel: link state changed to 'down' on port 8
Sep 29 18:25:45 kernel: link state changed to 'down' on port 3
Sep 29 18:25:45 kernel: link state changed to 'up' on port 2
Sep 29 18:25:45 kernel: link state changed to 'down' on port 1
Sep 29 18:25:46 kernel: link state changed to 'up' on port 6
Sep 29 18:25:46 kernel: link state changed to 'up' on port 7
Sep 29 18:25:46 kernel: link state changed to 'up' on port 8
Sep 29 18:25:46 kernel: link state changed to 'up' on port 3
Sep 29 18:25:47 kernel: link state changed to 'up' on port 1
Sep 29 18:57:27 kernel: link state changed to 'down' on port 5
Sep 29 18:57:27 kernel: link state changed to 'down' on port 7
Sep 29 18:57:27 kernel: link state changed to 'down' on port 8
Sep 29 18:57:27 kernel: link state changed to 'down' on port 11
Sep 29 18:57:27 kernel: link state changed to 'down' on port 1
Sep 29 18:57:27 kernel: link state changed to 'down' on port 3
Sep 29 18:57:27 kernel: link state changed to 'down' on port 4
Sep 29 18:57:29 kernel: link state changed to 'up' on port 11
Sep 29 18:57:30 kernel: link state changed to 'up' on port 4
Sep 29 18:57:30 kernel: link state changed to 'up' on port 3
Sep 29 18:57:30 kernel: link state changed to 'up' on port 5
Sep 29 18:57:30 kernel: link state changed to 'up' on port 1
Sep 29 18:57:30 kernel: link state changed to 'up' on port 8
Sep 29 18:57:30 kernel: link state changed to 'up' on port 7
Sep 29 18:57:34 kernel: link state changed to 'down' on port 4
Sep 29 18:57:36 kernel: link state changed to 'up' on port 4
Sep 29 18:57:50 kernel: link state changed to 'down' on port 11
Sep 29 18:57:51 kernel: link state changed to 'down' on port 1
Sep 29 18:57:51 kernel: link state changed to 'down' on port 7
Sep 29 18:57:51 kernel: link state changed to 'down' on port 8
Sep 29 18:57:51 kernel: link state changed to 'down' on port 3
Sep 29 18:57:52 kernel: link state changed to 'down' on port 4
Re: WS-12-250-AC rebooting all ports
Posted: Wed Sep 30, 2015 8:55 am
by sirhc
They turn red when the units/radios boot because when the radios first start up they connect with a 10 meg link.
You have to have something configured wrong somewhere.
Can I get access to your computer today via Team View so I can look at the switch and the AP's?
Have the browser open to the switch and all the AP's when I connect?