Netonix Forums

Hello
We have a very odd thing happening with a WS-6-MINI

Its GUI is unstable, and when we monitor it and ping it from the gateway it looses A LOT of pings.

However, if you ping the radios that are behind it, they are just fine. Looks like the Software on the mini 6 is having issues and not actually the network?

The Status page is ok, CPU is low. Running 1.5.5. on E board.

It usually has 60-100Mbps of traffic only

Any ideas?
all comments are welcomed.

That's odd.
Can you post the log?

Sure

Dec 31 18:00:05 sysinit: killall: udhcpc: no process killed

Dec 31 18:00:07 kernel: vtss_core: module license '(c) Vitesse Semiconductor Inc.' taints kernel.

Dec 31 18:00:07 kernel: switch: 'Luton26' board detected

Dec 31 18:00:09 kernel: vtss_port: Loaded port module on board Luton26, type 5

Dec 31 18:00:09 kernel: nf_conntrack version 0.5.0 (2048 buckets, 8192 max)

Dec 31 18:00:10 system: Setting MAC address from flash configuration: EC:13:B2:91:47:9A

Dec 31 18:00:10 kernel: i2c /dev entries driver

Dec 31 18:00:10 kernel: i2c_vcoreiii i2c_vcoreiii: i2c bus driver on IRQ 19

Dec 31 18:00:11 sysinit: Loading defaults

Dec 31 18:00:11 system: starting ntpclient

Dec 31 18:00:12 sysinit: Adding custom chains

Dec 31 18:00:12 sysinit: Loading zones

Dec 31 18:00:12 sysinit: Loading forwarding

Dec 31 18:00:12 sysinit: Loading redirects

Dec 31 18:00:12 sysinit: Loading rules

Dec 31 18:00:12 sysinit: Loading includes

Dec 31 18:00:13 admin: adding lan (eth0) to firewall zone lan

Dec 31 18:00:13 dropbear[636]: Running in background

Dec 31 18:00:14 netonix: 1.5.5 on WS-6-MINI

Dec 31 18:00:17 UI: web config OK

Dec 31 18:00:17 syslogd exiting

Dec 31 18:00:18 syslogd started: BusyBox v1.19.4

Dec 31 18:00:21 Port: link state changed to 'up' (1G) on port 4

Dec 31 18:00:22 Port: link state changed to 'up' (1G) on port 5

Dec 31 18:00:22 Port: link state changed to 'up' (1G) on port 2

Dec 31 18:00:22 sysinit: 1969-12-31 18:00:21: (network.c.272) warning: please use server.use-ipv6 only for hostnames, not without server.bind / empty address; your config will break if the kernel default for IPV6_V6ONLY changes

Dec 31 18:00:22 sysinit: 1969-12-31 18:00:21: (network.c.272) warning: please use server.use-ipv6 only for hostnames, not without server.bind / empty address; your config will break if the kernel default for IPV6_V6ONLY changes

Dec 31 18:00:22 sysinit: 1969-12-31 18:00:21: (log.c.216) server started

Dec 31 18:00:23 Port: link state changed to 'up' (1G) on port 6

Dec 31 18:00:26 switch[770]: temp sensor version 3

Dec 31 18:00:27 Port: link state changed to 'down' on port 6

Dec 31 18:00:27 switch[771]: Detected cold boot

Dec 31 18:00:28 Port: link state changed to 'down' on port 4

Dec 31 18:00:28 Port: link state changed to 'down' on port 5

Dec 31 18:00:28 Port: link state changed to 'down' on port 2

Dec 31 18:00:28 switch[771]: PoE enabled on port 2, PoE Smart is starting cable check

Dec 31 18:00:28 switch[771]: PoE enabled on port 4, PoE Smart is starting cable check

Dec 31 18:00:28 switch[771]: PoE enabled on port 5, PoE Smart is starting cable check

Dec 31 18:00:28 switch[771]: PoE enabled on port 6, PoE Smart is starting cable check

Dec 31 18:00:30 system: starting ntpclient

Dec 31 18:00:33 switch[771]: Port 2 cable check results: Open, Open, Open, Open

Dec 31 18:00:33 switch[771]: Port 2 passed PoE Smart cable check, turning on power

Dec 31 18:00:33 switch[771]: Port 4 cable check results: Open, Abnormal termination, Open, Open

Dec 31 18:00:33 switch[771]: Port 4 passed PoE Smart cable check, turning on power

Dec 31 18:00:33 switch[771]: Port 5 cable check results: Open, Abnormal termination, Open, Open

Dec 31 18:00:33 switch[771]: Port 5 passed PoE Smart cable check, turning on power

Dec 31 18:00:33 switch[771]: Port 6 cable check results: Open, Open, Open, Open

Dec 31 18:00:33 switch[771]: Port 6 passed PoE Smart cable check, turning on power

Dec 31 18:00:36 Port: link state changed to 'up' (1G) on port 2

Dec 31 18:00:36 Port: link state changed to 'up' (100M-F) on port 5

Dec 31 18:00:36 Port: link state changed to 'up' (100M-F) on port 6

Dec 31 18:00:36 Port: link state changed to 'up' (100M-F) on port 4

Dec 31 18:00:44 system: starting ntpclient

Dec 31 18:00:49 Port: link state changed to 'down' on port 2

Dec 31 18:00:52 Port: link state changed to 'up' (1G) on port 2

Dec 31 18:00:57 system: starting ntpclient

Dec 31 18:00:59 Port: link state changed to 'down' on port 4

Dec 31 18:01:01 Port: link state changed to 'down' on port 6

Dec 31 18:01:01 Port: link state changed to 'down' on port 2

Dec 31 18:01:01 Port: link state changed to 'down' on port 5

Dec 31 18:01:02 Port: link state changed to 'up' (1G) on port 4

Dec 31 18:01:03 Port: link state changed to 'up' (1G) on port 2

Dec 31 18:01:04 Port: link state changed to 'up' (1G) on port 6

Dec 31 18:01:04 Port: link state changed to 'up' (1G) on port 5

Dec 31 18:01:04 Port: link state changed to 'down' on port 4

Dec 31 18:01:06 Port: link state changed to 'down' on port 6

Dec 31 18:01:06 Port: link state changed to 'down' on port 5

Dec 31 18:01:09 Port: link state changed to 'up' (1G) on port 4

Dec 31 18:01:10 Port: link state changed to 'up' (1G) on port 6

Dec 31 18:01:10 system: starting ntpclient

Dec 31 18:01:10 Port: link state changed to 'up' (1G) on port 5

Jan 18 17:01:41 system: time set by NTP server

Jan 20 10:58:57 sSMTP[3438]: Unable to locate mailhub

Jan 20 10:58:57 sSMTP[3438]: Cannot open mailhub:25



I could not see anything odd, we sent a guy to re do a plug , but it just drops pings
thanks

Well, the only thing I see in the log that seems a little noticeable is at the very end SMTP seem's to attempt to send an email via mailhub for some reason but fails.

Can you post the Config Tab for the switch?
Also, just for a sanity check, maybe try disabling SMTP temporarily could potentially help.

Thanks for the quick reply, SMTP is off . Odd.

I recommend defaulting the switch and rebuilding the config. SMTP shouldn't be attempting to do anything it is a strong clue too me that there is a minor config corruption resulting in undefined behavior.

To accomplish this; in the serial console - run the command

Code: Select all

reload defaults


The switch will reboot at IP address 192.168.1.20/24 from there you can re-apply your configurations as needed.

Normally, to save time I would say it would be a good idea to save the config and re-apply it. But in this case I think it would be necessary to do it manually to attempt to avoid any further issue's.

Ummm.... AFAIK the MINI does not have a serial console.

Right, forgot which device I was looking at for a second there.

You can also do it by pressing "Default" from the Utilities dropdown.

We might need to send a tech to the site, it is a town far away. If i reset it, the PoE on the ports will be off after reboot right? I could lose access to it.

I dont have another mini to test.

You are correct.