v1.4.4 Bug Reports and Comments

[sirhc]

Eric had a lunch meeting but I just left him a message in Skype to contact you when he gets back.

[jermudgeon]

Updated a 12-port DC switch with 1.4.4 via the web UI.

On reboot, the web UI was inaccessible, and ssh CLI segfaulted. Ctrl-C got me to busybox. SCP and firmware_upgrade (a second time) returned no space left on device to create the upgrade config tar.

On reboot, I did a du comparison to a non-updated switch; /root was full of this:

-rwxrwxrwx 1 admin root 1153672 Aug 13 18:43 10881xb
-rwxrwxrwx 1 admin root 879912 Aug 21 09:16 JRSYN
-rwxrwxrwx 1 admin root 5100983 Aug 6 09:27 Linux2.4
-rwxrwxrwx 1 admin root 172280 Aug 6 18:17 xb132
-rwxrwxrwx 1 admin root 10220 Aug 6 18:18 xb164
-rwxrwxrwx 1 admin root 649480 Aug 6 19:36 xbaspsyn
-rwxrwxrwx 1 admin root 122556 Aug 24 19:11 xiaarm
-rwxrwxrwx 1 admin root 306308 Aug 6 09:26 xiage8uc
-rwxrwxrwx 1 admin root 395812 Aug 22 07:51 xiajis
-rw-r--r-- 1 admin root 110592 Aug 24 19:12 xialinux

Clearing this out, firmware_upgrade worked.

[IntL-Daniel]

We have WS-12-250-AC on 1.4.4. Currently I play with QOS settings and after enable “Trust status” on ports we can see this in the log:

Sep 20 13:44:32 UI: Port 1 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:44:32 UI: Port 2 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 3 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 4 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 5 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 6 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 7 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 8 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 9 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 10 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 11 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 12 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 13 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 14 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:04 Port: link state changed to 'down' on port 10
(!)Sep 20 13:45:04 switch[1354]: Port 10 has link while turning on PoE (this line has exclamation mark, is that correct?)
Sep 20 13:45:04 switch[1354]: PoE enabled on port 10, PoE Smart is starting cable check
Sep 20 13:45:09 switch[1354]: Port 10 cable check results: Ok, Ok, Abnormal termination, Abnormal termination
Sep 20 13:45:09 switch[1354]: Port 10 passed PoE Smart cable check, turning on power
Sep 20 13:45:11 Port: link state changed to 'up' (100M-F) on port 10
Sep 20 13:45:40 Port: link state changed to 'down' on port 10
Sep 20 13:45:41 Port: link state changed to 'up' (100M-F) on port 10
Sep 20 13:45:52 Port: link state changed to 'down' on port 10
Sep 20 13:45:54 Port: link state changed to 'up' (100M-F) on port 10

As you can see, port 10 generated „port bounce“ and then with false detection on POE Smart check. There we have set 48V (not VH) and the device itself really rebooted (due to port bounce).

[Eric Stern]

We have WS-12-250-AC on 1.4.4. Currently I play with QOS settings and after enable “Trust status” on ports we can see this in the log:

Sep 20 13:44:32 UI: Port 1 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:44:32 UI: Port 2 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 3 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 4 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 5 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 6 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 7 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 8 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 9 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 10 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 11 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 12 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 13 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:01 UI: Port 14 QoSTrust: changed from 'Disabled' to 'Enabled'
Sep 20 13:45:04 Port: link state changed to 'down' on port 10
(!)Sep 20 13:45:04 switch[1354]: Port 10 has link while turning on PoE (this line has exclamation mark, is that correct?)
Sep 20 13:45:04 switch[1354]: PoE enabled on port 10, PoE Smart is starting cable check
Sep 20 13:45:09 switch[1354]: Port 10 cable check results: Ok, Ok, Abnormal termination, Abnormal termination
Sep 20 13:45:09 switch[1354]: Port 10 passed PoE Smart cable check, turning on power
Sep 20 13:45:11 Port: link state changed to 'up' (100M-F) on port 10
Sep 20 13:45:40 Port: link state changed to 'down' on port 10
Sep 20 13:45:41 Port: link state changed to 'up' (100M-F) on port 10
Sep 20 13:45:52 Port: link state changed to 'down' on port 10
Sep 20 13:45:54 Port: link state changed to 'up' (100M-F) on port 10

As you can see, port 10 generated „port bounce“ and then with false detection on POE Smart check. There we have set 48V (not VH) and the device itself really rebooted (due to port bounce).

Can I see the entire log file?

[IntL-Daniel]

Oh sorry already cleared :(

[juanvi]

Released 2015?

"
v1.4.4
Click HERE to download firmware v1.4.4 - Released 9/6/2015
Click HERE to go to the thread on v1.4.4 to read other people's comments and questions.

v1.4.5rcX
Click HERE to download firmware v1.4.5rc2 - Released 9/21/2015
Click HERE to go to the thread on v1.4.5rcX to read other people's comments and questions.
"

[IntL-Daniel]

:-D

[juanvi]

Ok. Now we have L3 Qos. But what about L2 QoS (IEEE 802.1p)? Can give some info?
Thanks in advance for a great products and service!

[Eric Stern]

Ok. Now we have L3 Qos. But what about L2 QoS (IEEE 802.1p)? Can give some info?
Thanks in advance for a great products and service!

It does 802.1p.

https://en.wikipedia.org/wiki/IEEE_P802.1p

Just map the PCP value to the desired queue on the QoS tab.

[expohl]

Not sure if these are bugs or if they have already been reported. Just upgraded a 250-dc to 1.4.4 and noticed the following problems, not sure if these persisted in prior firmware though...

1. This switch is at my house, I have redundant ptp links to the switch, my router wan to my house faces port 1, my main ptp link is on port 2, and my secondary link is on port 3, ports 1,2,3 are on a un-tagged group of vlans and port 3 is disabled by unchecking the "enable" box under the ports tab. Traffic flows normally to the router. If port 3 is enabled and port 2 is disabled under the ports tab I can't pass traffic over the second link, however if I enable all 3 under the ports tab and take port 2 out of the vlan I can pass traffic over the backup link. So basically my intended "fail over" was if one link went down, I would disable it under the ports tab and enable the other link (port) which isn't working but if I simply leave them all enabled and add or remove the backup and primary link with vlans it works fine.

2. Previously I left the warn/hibernate/wake up voltages at their factory settings despite being on 24v system powering the switch. Today I looked and the log shows the past 24hrs being at 28v so I decided to set the warning at 27v, hibernate at 23v and the wakeup at 24v. A little later I rebooted the switch and it shut off and went black besides the single green smd led on the power supply inside the switch. I measured the input terminals at 28.0v. I tried to remove power for 10 seconds and power it back up and it still would be dark and not boot. Finally after leaving the power off for 10 minutes and powering it back up it finally booted, this would be devastating if it occurred on a normal site... I suspect the switch was in hibernation mode?