v1.4.0rc1-16 Bug reports and comments

[designweb]

not sure what happened to this WS-12 250B 1.4.0rc2

(we do not use VLAN 1 anywhere on our network) Just enabled backup link over PTP650 after we lost power at a tower but when we first connected new route to WS-24-400A it had no traffic flow, mac table showed multiple entries but on VLAN 1 only, I untagged management on port and then retagged it and link recovered WS-24 showed no errors


Feb 11 17:44:59 kernel: link state changed to 'up' on port 4
Feb 13 13:28:55 kernel: link state changed to 'down' on port 4
Feb 13 13:28:57 kernel: link state changed to 'up' on port 4
Feb 13 13:29:21 kernel: link state changed to 'down' on port 4
Feb 13 13:29:23 kernel: link state changed to 'up' on port 4
Feb 15 20:20:24 kernel: link state changed to 'down' on port 4
Feb 15 20:20:26 kernel: link state changed to 'up' on port 4
Feb 29 17:39:03 UI: Configuration changed by x.x.x.x
Feb 29 17:39:03 UI: Port 3 Enable: changed from 'Disabled' to 'Enabled'
Feb 29 17:39:07 kernel: link state changed to 'up' on port 3
Feb 29 17:47:29 UI: Configuration changed by x.x.x.x
Feb 29 17:47:29 UI: Port 3 Enable: changed from 'Enabled' to 'Disabled'
Feb 29 17:47:32 kernel: link state changed to 'down' on port 3
Feb 29 17:50:55 UI: Configuration changed by x.x.x.x
Feb 29 17:50:55 UI: Port 3 Enable: changed from 'Disabled' to 'Enabled'
Feb 29 17:50:59 kernel: link state changed to 'up' on port 3
Feb 29 17:53:59 UI: Configuration changed by x.x.x.x
Feb 29 17:53:59 UI: VLAN 1 PortSettings: changed from 'TTTTTTTTTTETTT' to 'TTUTTTTTTTETTT'
Feb 29 17:56:43 UI: Configuration changed by x.x.x.x
Feb 29 17:56:43 UI: VLAN 1 PortSettings: changed from 'TTUTTTTTTTETTT' to 'TTTTTTTTTTETTT'

[sirhc]

not sure what happened to this WS-12 250B 1.4.0rc2

(we do not use VLAN 1 anywhere on our network) Just enabled backup link over PTP650 after we lost power at a tower but when we first connected new route to WS-24-400A it had no traffic flow, mac table showed multiple entries but on VLAN 1 only, I untagged management on port and then retagged it and link recovered WS-24 showed no errors


Feb 11 17:44:59 kernel: link state changed to 'up' on port 4
Feb 13 13:28:55 kernel: link state changed to 'down' on port 4
Feb 13 13:28:57 kernel: link state changed to 'up' on port 4
Feb 13 13:29:21 kernel: link state changed to 'down' on port 4
Feb 13 13:29:23 kernel: link state changed to 'up' on port 4
Feb 15 20:20:24 kernel: link state changed to 'down' on port 4
Feb 15 20:20:26 kernel: link state changed to 'up' on port 4
Feb 29 17:39:03 UI: Configuration changed by x.x.x.x
Feb 29 17:39:03 UI: Port 3 Enable: changed from 'Disabled' to 'Enabled'
Feb 29 17:39:07 kernel: link state changed to 'up' on port 3
Feb 29 17:47:29 UI: Configuration changed by x.x.x.x
Feb 29 17:47:29 UI: Port 3 Enable: changed from 'Enabled' to 'Disabled'
Feb 29 17:47:32 kernel: link state changed to 'down' on port 3
Feb 29 17:50:55 UI: Configuration changed by x.x.x.x
Feb 29 17:50:55 UI: Port 3 Enable: changed from 'Disabled' to 'Enabled'
Feb 29 17:50:59 kernel: link state changed to 'up' on port 3
Feb 29 17:53:59 UI: Configuration changed by x.x.x.x
Feb 29 17:53:59 UI: VLAN 1 PortSettings: changed from 'TTTTTTTTTTETTT' to 'TTUTTTTTTTETTT'
Feb 29 17:56:43 UI: Configuration changed by x.x.x.x
Feb 29 17:56:43 UI: VLAN 1 PortSettings: changed from 'TTUTTTTTTTETTT' to 'TTTTTTTTTTETTT'

This was discussed in this post: viewtopic.php?f=17&t=1449&start=40#p11290

VLAN 1 PortSettings: changed from 'TTTUUUUEUU' to 'TTTTTTTEEE'

Oh, what that is saying is "the first VLAN" rather than "the VLAN with ID 1". However, I can see how that can be confusing, so I will change it so that it uses "VLAN <ID>" instead.

Try upgrading to v1.4.0rc4

[designweb]

upgraded to 1.4.0rc4 now I get this fan disappeared and a second twin fan switch now states no fans at all


Jan 1 00:00:33 system: starting ntpclient
Feb 29 20:06:32 dropbear[1407]: Running in background
Feb 29 20:06:41 switch[1479]: Detected warm boot
Feb 29 20:09:06 switch[1424]: Warning: expected 2 fans but found 1
Feb 29 20:09:06 sSMTP[1741]: RCPT TO: (550 Sender verify failed)

[Eric Stern]

upgraded to 1.4.0rc4 now I get this fan disappeared and a second twin fan switch now states no fans at all


Jan 1 00:00:33 system: starting ntpclient
Feb 29 20:06:32 dropbear[1407]: Running in background
Feb 29 20:06:41 switch[1479]: Detected warm boot
Feb 29 20:09:06 switch[1424]: Warning: expected 2 fans but found 1
Feb 29 20:09:06 sSMTP[1741]: RCPT TO: (550 Sender verify failed)

I tested this build on a WS-24-400A and a WS-12-250B and they both worked fine. Try downgrading to 1.3.9 and see if the fans come back.

[designweb]

Hi Eric

uptime now 22 hours for both switches, no further entry in log for WS-12-250B, however both fans now reporting normal operation?? WS-12-250A still reporting no fans operational until downgrade to 1.3.9 then still no fans until after 4.5 minutes of uptime?

[sirhc]

Hi Eric

uptime now 22 hours for both switches, no further entry in log for WS-12-250B, however both fans now reporting normal operation?? WS-12-250A still reporting no fans operational until downgrade to 1.3.9 then still no fans until after 4.5 minutes of uptime?

You do realize that the fans are off until the board temp is above 40C? THe fans do not constantly run if not needed.

[lligetfa]

You do realize that the fans are off until the board temp is above 40C? THe fans do not constantly run if not needed.

None the less, there should not be log entries about fans not found.

[sirhc]

None the less, there should not be log entries about fans not found.

I agree Les but that is not what he is saying., at least how I understand it????

uptime now 22 hours for both switches, no further entry in log for WS-12-250B, however both fans now reporting normal operation??
WS-12-250A still reporting no fans operational until downgrade to 1.3.9 then still no fans until after 4.5 minutes of uptime?

You do realize that the fans are off until the board temp is above 40C? THe fans do not constantly run if not needed.

He is not mentioning anything about log entries at this point, simply that the fans were not running for 4.5 minutes after reboot.

Thus I am saying that the fans will not run until the board exceeds 40C.

Am I missing something?

[designweb]

You are both correct, the board temp is around 40C so the fans will oscillate, however the log stating fans not found is also correct, so the 4 minute delay could just be low operating temp but the fans are definitely in the case and working

[therealboss]

Is there any point on putting v1.4.0rc on a WS-8-250-DC, it has 1.3.9 and is running fine.

I'm very happy with 1.3.9, this is the first one we have used but have several in the workshop to start rolling these switches out across our network.

Think we have 8 of these switches, some 6 port, several 8 ports and a few 12 ports, but before I send them out I just wanted to see if it is recommended to upgrade to v1.4rc or just leave them with 1.3.9.