v1.4.4 Bug Reports and Comments

[jclendenan]

Any chance someone has the MD5 or sha1 sum for this? I Just want to make sure I know I have a good copy of it.

Thanks,
James

[jakematic]

sums

This is what I show, installed and working flawless on my switches

[dcox]

false alarm on the GUI issues, chrome worked fine, and a reboot and cache flush fixed IE.

[mnitech]

Upgraded my test WS-12-250-AC switch from 1.3.9 to 1.4.4,

I now get intermittent beige bars telling me

"Attempting to reestablish communications"

Ping shows

172.19.19.241 timeout
172.19.19.241 timeout
172.19.19.241 timeout
172.19.19.241 timeout
172.19.19.241 56 64 0ms
172.19.19.241 56 64 0ms
172.19.19.241 56 64 0ms
172.19.19.241 56 64 0ms
172.19.19.241 56 64 0ms
172.19.19.241 timeout
172.19.19.241 timeout
172.19.19.241 timeout
172.19.19.241 timeout
sent=33 received=14 packet-loss=57% min-rtt=0ms avg-rtt=0ms max-rtt=1ms

[sirhc]

Upgraded my test WS-12-250-AC switch from 1.3.9 to 1.4.4,

I now get intermittent beige bars telling me

"Attempting to reestablish communications"

Your going to have to give us something to work with here as to why?
I have v1.4.4 active in all but 2 of my WISP towers and do not have this issue and I will upgrade the last 2 over the weekend?

[mnitech]

Its definitely related to software level. Works OK on 1.3.9 and fails with 1.4.2 and 1.4.4. I jumped this Netonix from 1.3.9 to 1.4.4 and noticed the failure. I downgraded to 1.3.9 and the problem disappeared. I loaded 1.4.2 and the problem came back

The Netonix is plugged into a Mikrotik router. There are three direct cables between them. Each cable connects a VLAN on the Netonix to a subnet on the router.

Logs on both devices are clean however the RXDrop counter for the interfaces are incrementing

Port 1 - Port 1 - 172
Receive Total
Rx Packets 3827
Rx Octets 453508
Rx Unicast 1664
Rx Multicast 234
Rx Broadcast 1929
Rx Pause 0
Transmit Total
Tx Packets 2027
Tx Octets 1367112
Tx Unicast 2002
Tx Multicast 24
Tx Broadcast 1
Tx Pause 0
Receive Size Counters
Rx 64 Bytes 2913
Rx 65-127 Bytes 318
Rx 128-255 Bytes 124
Rx 255-511 Bytes 199
Rx 512-1023 Bytes 273
Rx 1024-1526 Bytes 0
Rx 1527- Bytes 0
Transmit Size Counters
Tx 64 Bytes 578
Tx 65-127 Bytes 380
Tx 128-255 Bytes 147
Tx 255-511 Bytes 0
Tx 512-1023 Bytes 83
Tx 1024-1526 Bytes 839
Tx 1527- Bytes 0
Receive Queue Counters
Rx Q0 3827
Rx Q1 0
Rx Q2 0
Rx Q3 0
Rx Q4 0
Rx Q5 0
Rx Q6 0
Rx Q7 0
Transmit Queue Counters
Tx Q0 2027
Tx Q1 0
Tx Q2 0
Tx Q3 0
Tx Q4 0
Tx Q5 0
Tx Q6 0
Tx Q7 0
Receive Error Counters
Rx Drops 1250
Rx CRC 0
Rx Undersize 0
Rx Oversize 0
Rx Fragments 0
Rx Jabber 0
Rx Filtered 119
Transmit Error Counters

[sirhc]

Your going to have to give us something to work with here as to why?

Your issues is so far a unique issue no one else is reporting so please post up all your Config Tabs.

Maybe your config is corrupted so if this is a test switch try factory defaulting it after you upgrade it.

[mnitech]

So recap:

Upgraded from 1.3.9 to 1.4.4 and started dropping packets to the management interface
Regressed to 1.3.9 and problem disappeared
Upgraded to 1.4.2 and problem reoccurred
Left it that way and came back later. Now can't access the web page but ping was working
Pings stopped working but could get a response to ARP
Had to wait until someone stopped by the site and powercycled the switch. (I am 600 miles away)
Problem gone.
Upgraded to 1.4.4 and no problem.

Duh.

[sirhc]

So recap:

Upgraded from 1.3.9 to 1.4.4 and started dropping packets to the management interface
Regressed to 1.3.9 and problem disappeared
Upgraded to 1.4.2 and problem reoccurred
Left it that way and came back later. Now can't access the web page but ping was working
Pings stopped working but could get a response to ARP
Had to wait until someone stopped by the site and powercycled the switch. (I am 600 miles away)
Problem gone.
Upgraded to 1.4.4 and no problem.

Duh.

I would not use v1.4.0 through v1.4.3 as the bugs are significant.

When you upgraded to 1.4.4 maybe you just needed to reboot the switch again as v1.3.9 is 6+ months old and the reboot after upgrade is handled by the previous version?

Also there were many changed between v1.3.9 and 1.4.4 including how SFP modules are configured by default for 1 which is important. You may need to change SFP modules Speed Duplex from Auto to 1G or versa.

Also some SFP modules if used do not always address properly on every reboot.
But now you are on v1.4.4 and all is fine then?

[designweb]

We have had this problem for the past few versions everything beyond 1.4.2 we have had packet loss across the network, on the first switch as we come off of the fibre backhaul BT Vodafone TalkTalk in our case causes monetworkst problems of packet loss. reverting to 1.3.9 gets a stable network. We have tried a few of our networks on 1.4.4 on all of the switches and the network dies, revert the first switch after the fibre to 1.3.9 everything works well