v1.3.8 FINAL bug reports and comments

[maxbb]

Here is the log.

Dec 31 19:12:03 STP: set port 2 to learning
Dec 31 19:12:03 STP: set port 2 to forwarding
Dec 31 20:39:13 UI: Configuration changed by 10.0.4.35
Dec 31 20:39:13 UI: IPv4_Address: changed from '10.0.4.7' to '10.0.9.7'
Dec 31 20:39:13 UI: IPv4_Gateway: changed from '10.0.4.1' to '10.0.9.1'
Dec 31 20:39:15 admin: removing lan (eth0) from firewall zone lan
Dec 31 20:39:19 admin: adding lan (eth0) to firewall zone lan
Dec 31 20:39:20 STP: set port 2 to discarding
Dec 31 20:39:23 STP: set port 2 to learning
Dec 31 20:39:23 STP: set port 2 to forwarding
Dec 31 20:40:23 admin: Reverting to last known good configuration
Dec 31 20:40:25 admin: removing lan (eth0) from firewall zone lan
Dec 31 20:40:28 admin: adding lan (eth0) to firewall zone lan
Dec 31 20:40:30 STP: set port 2 to discarding
Dec 31 20:40:33 STP: set port 2 to learning
Dec 31 20:40:33 STP: set port 2 to forwarding

[sirhc]

Here is the log.

Dec 31 19:12:03 STP: set port 2 to learning
Dec 31 19:12:03 STP: set port 2 to forwarding
Dec 31 20:39:13 UI: Configuration changed by 10.0.4.35
Dec 31 20:39:13 UI: IPv4_Address: changed from '10.0.4.7' to '10.0.9.7'
Dec 31 20:39:13 UI: IPv4_Gateway: changed from '10.0.4.1' to '10.0.9.1'
Dec 31 20:39:15 admin: removing lan (eth0) from firewall zone lan
Dec 31 20:39:19 admin: adding lan (eth0) to firewall zone lan
Dec 31 20:39:20 STP: set port 2 to discarding
Dec 31 20:39:23 STP: set port 2 to learning
Dec 31 20:39:23 STP: set port 2 to forwarding
Dec 31 20:40:23 admin: Reverting to last known good configuration
Dec 31 20:40:25 admin: removing lan (eth0) from firewall zone lan
Dec 31 20:40:28 admin: adding lan (eth0) to firewall zone lan
Dec 31 20:40:30 STP: set port 2 to discarding
Dec 31 20:40:33 STP: set port 2 to learning
Dec 31 20:40:33 STP: set port 2 to forwarding

If the browser you are using can not re-establish communications with the switch when you change the IP address within 60 seconds the switch will revert to the last IP address.

You either need to upgrade to v1.3.9rc12 and disable Safe Mode on the device config by setting to "0".

CLICK IMAGE BELOW TO VIEW FULL SIZE

[maxbb]

ok thanks for your help, i changed the time to 120 and added that subnet to my computer and it works now. The problem was by the time i changed the ip on computer it reverted back to original ip.

[davidvw]

ok thanks for your help, i changed the time to 120 and added that subnet to my computer and it works now. The problem was by the time i changed the ip on computer it reverted back to original ip.

I just had a similar issue and fixed it by increasing the revert timer. The problem for me was that I was testing it locally and was manually changing the IP address on my secondary NIC to be on the new subnet. I guess 60 seconds wasn't enough time to do that and log back into the switch before it would kick back to the original IP.

[sirhc]

Maybe on next release we will increase the default to 120 seconds?

[Uintadave]

I've reviewed the code and tested it and I don't see any way it could go wrong. I'm going to have to suggest that its not a bug and the AP is working enough that the ping check is successful, so the ping watchdog is not being triggered.

I'd recommend that the next time it happens before you manually bounce it, log into the switch and ping the AP from the command line. The actual command the ping watchdog uses is "ping -c 3 -W 1 ", which pings 3 times and times out after 1 second. Unless there is 100% packet loss the script considers the ping successful.

I will test it, but I am 100% certain it is 100% packet loss as this is a known issue where XW Titanium rockets have the LAN port randomly "lockup" and stop passing data when running 1G.

Also my switch and APs are in different subnets/vlans so if the tower router cannot ping the AP I do not know how the switch would be able to ping it and get enough replies to not trip the watchdog.

Again I will do as you suggest and report back next time it happens.

Well it happened again today. AP went down around 4am and when I woke up at 7am it was still down and unpingable. I tried the command you gave me from the switch console and it would not run. Instead I ran a normal ping and the switch showed 100% packet loss.

I am certain the switch is not even receiving one ping from the AP during the outage as we ping the AP from our core in our SNMP monitor once a minute and it did not get a single hit. I cannot see how the switch during this ~3 hour outage did not miss 3 pings when the interval is 120 seconds and my SNMP monitor did not also record a hit.

I am having this exact same problem, and it is with ubnt Titanium radios randomly having LAN lockup problems. I don't know why the watchdog works some times but not others. I would say it works about 1 in three times. the other times I have to log into the switch and manually port bounce the port.

and like sbyrd the switch is not on the same subnet. It gets routed in order to check the ping. If the router can't ping the radio the switch won't be able to.

[sirhc]

I am having this exact same problem, and it is with ubnt Titanium radios randomly having LAN lockup problems. I don't know why the watchdog works some times but not others. I would say it works about 1 in three times. the other times I have to log into the switch and manually port bounce the port.

and like sbyrd the switch is not on the same subnet. It gets routed in order to check the ping. If the router can't ping the radio the switch won't be able to.

Please try v1.3.9rc13 as there was a lot of work done to Ring Watchdog

[Uintadave]

will do.

[redpeppers]

I am not sure if it is a fluke but I installed 1.38 stable on two ws-12-250-dc switches and I loose access to the UI after upgrade. It appears that after a hard power cycle it comes back up. I have not power cycled the 2nd yet, but I did loose UI access to the first one and with a power cycle it came back up. I can not power cycle the 2nd one until a good maintenance window due to it being a major backhaul on the ring. All devices and vlans are still working fine after the upgrade. Thanks in advance.

[sirhc]

I would suggest reading the release notes on v1.3.9rc14 which is about to go final, especially when using the DC switches.