WISP WS3-14-600-AC Firmware question

[OacysShop]

Hello All,

I had a question and was a little confused regarding which firmware should be loaded on our WS3-14-600-AC. I see in the forums the "latest" firmware is 1.5.6 but at the bottom of our switch's UI (and in some screenshots in some posts) I see firmware 2.0.4. Could I be pointed in the right direction of which should be loaded? We have had an issue when our switch was connected using the 2 10GB ports to our 2 40GB switches and were curious if maybe we just have a wrong firmware on it.

Thank you,

Luis

[Stephen]

The WS3 is a brand new product, as such 2.0.4 is the latest, I am working on a new firmware version now, once it's available it will be on the forum's and I will either post it in the same thread as the WS firmware (1.5.6) or provide a link too it on that same thread.

[Stephen]

OacysShop, btw what is the issue exactly with the 10G ports?

[OacysShop]

Stephen,

After we installed our new Netonix 10Gb switch we found it was taking over MAC of one of our servers after it rebooted. The server was generally able to ping two of our router vlan1 IPs, but pings to outside sources such as Google and our Sophos would have high loss (generally over 50%). We found that pings from our routers to the server would not work, but arping broadcasts would work reliably and found MAC address moving ports (towards Netonix switch). We disabled the secondary port on the switch Netonix that is connected to one of our 40Gb switches and then problem went away. We are using STP and both ports were showing as forwarding, alternate and dropping as expected. We think that somewhere the switch may be rebroadcasting or looping some packets that may be causing this?

-Luis

[Stephen]

On the WS3 are you using any tagged ports in the management VLAN?

[OacysShop]

No, just vlan1 untagged across the board.

[Stephen]

Can you post the logs.

[OacysShop]

Currently in our LOGS, it only shows the following, may have to try and duplicate and see if new logging shows?

Dec 1 22:17:07 syslogd started: BusyBox v1.29.3

Dec 1 22:17:09 Netonix: link state changed to 'down' on port 1

Dec 1 22:17:09 Netonix: link state changed to 'down' on port 2

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 3

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 4

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 5

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 6

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 7

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 8

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 9

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 10

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 11

Dec 1 22:17:10 Netonix: link state changed to 'down' on port 12

Dec 1 22:17:11 Netonix: link state changed to 'down' on port 13

Dec 1 22:17:11 Netonix: link state changed to 'up' (10G) on port 14

Dec 1 22:17:12 netonix: 2.0.4 on

Dec 1 22:17:16 Netonix: link state changed to 'up' (10G) on port 14

Dec 1 22:17:16 l2proto: MSTI0 port 14: new STP state discarding

Dec 1 22:17:18 l2proto: MSTI0 port 14: new STP state discarding

Dec 1 22:17:18 Spanning_Tree: MSTI0: New root on port 14, root path cost is 2000, root bridge id is 4096.F8-BC-12-26-C5-60

Dec 1 22:17:18 l2proto: MSTI0 port 14: new STP state learning

Dec 1 22:17:18 l2proto: MSTI0 port 14: new STP state forwarding

Dec 1 14:17:23 syslogd exiting

Dec 1 14:17:25 syslogd started: BusyBox v1.29.3

Dec 1 22:17:37 Netonix: link state changed to 'down' on port 14

Dec 1 22:17:37 l2proto: MSTI0 port 14: new STP state discarding

Dec 1 22:17:40 Netonix: link state changed to 'up' (10G) on port 14

Dec 1 22:17:40 l2proto: MSTI0 port 14: new STP state discarding

Dec 1 22:17:42 Spanning_Tree: MSTI0: New root on port 14, root path cost is 2000, root bridge id is 4096.F8-BC-12-26-C5-60

Dec 1 22:17:42 l2proto: MSTI0 port 14: new STP state learning

Dec 1 22:17:42 l2proto: MSTI0 port 14: new STP state forwarding

Dec 1 14:17:45 dropbear[190]: Running in background

Dec 1 14:17:47 ntpd[197]: ntpd 4.2.8p13@1.3847-o Thu Jun 11 17:39:06 UTC 2020 (1): Starting

Dec 1 14:17:47 ntpd[197]: Command line: ntpd -g 64.18.240.60

Dec 1 14:17:47 ntpd[200]: proto: precision = 4.732 usec (-18)

Dec 1 14:17:47 ntpd[200]: basedate set to 2020-05-30

Dec 1 14:17:47 ntpd[200]: gps base set to 2020-05-31 (week 2108)

Dec 1 14:17:47 ntpd[200]: Listen and drop on 0 v6wildcard [::]:123

Dec 1 14:17:47 ntpd[200]: Listen and drop on 1 v4wildcard 0.0.0.0:123

Dec 1 14:17:48 ntpd[200]: Listen normally on 2 lo 127.0.0.1:123

Dec 1 14:17:48 ntpd[200]: Listen normally on 3 vtss.vlan.1 10.42.1.207:123

Dec 1 14:17:48 ntpd[200]: Listening on routing socket on fd #20 for interface updates

Dec 1 14:17:48 ntpd[200]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

Dec 1 14:17:48 ntpd[200]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

Dec 1 22:17:50 switch[45]: Detected cold boot

Jan 13 08:53:37 ntpd[200]: kernel reports TIME_ERROR: 0x41: Clock Unsynchronized

[OacysShop]

Hello Stephen,

Upon further troubleshooting we got the following results. When our server does a restart (or even a restart of the network service), during a packet trace on one of our routers, it sends out a couple of the following:

15:22:21.349563 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28

Which everything is ok and we have no issues as long as we have the port to the netonix (from our 40GB switch) shutdown. Once we enable the port on our 40GB switch to send traffic to the netonix, after a reboot of our server (or a network restart as we tested with today), we start seeing the same packets above but looping continuously then showing something a bit slight different:

15:26:57.109505 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.113221 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.115496 IP6 fe80::d419:7bff:fe4e:cd2b > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.115592 IP6 fe80::d419:7bff:fe4e:cd2b > ff02::2: ICMP6, router solicitation, length 16
15:26:57.125169 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.128759 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.132322 IP6 fe80::d419:7bff:fe4e:cd2b > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.141705 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.153778 IP6 :: > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28
15:26:57.157533 IP6 fe80::d419:7bff:fe4e:cd2b > ff02::16: HBH ICMP6, multicast listener report v2, 1 group record(s), length 28

On our switch while both 10GB ports are enabled, port 13 is set to forwarding while port 14 is set to discarding (we have yet see anything labeled as alternate or root as in other switches) so it seems that the switch is receiving the packet and rebroadcasting causing the loop instead of discarding and other devices on the network seer the servers MAC coming from the netonix itself.

[Stephen]

Can you try disabling IPv6 and let me know here what happens? If I'm reading that correctly, that service may be related.