NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS510TLP Port flapping
So had a similar issue with a GS108T where the ports would flap down then up repeatedly causing internet to break. The GS510TLP has been updated to latest 6.6.2.9 firmware and RESET to DEFAULTS (whi...
Since the bad cable was found I have not seen anymore port flapping. Strange that it affected several ports
I just want to follow-up on this. Were you able to perform a factory reset on the GS510TLP switch? If yes, are the ports still flapping?
Regards,
DaneA
NETGEAR Community Team
I disconnected the GS510TLP and subbed in another spare GS108T I have. At the moment, I haven't noticed any issues with the two GS108T switches.
Before I did that, I activated the GS510 factory firmware with reset to defaults and that appeared to work just fine.
My next step is to go back to the GS510, make sure factory firmware is ok and move on to the latest firmware again and try that.
Although the issue was usually apparent in a short space of time, I did see it more frequently in sporadic patches. At the time, the GS510 reported that one of my devices was pushing out incorrect bpdu messages and that it, the GS510, was rejecting them. Very odd as I was sure all STP and BPDU forwarding and checking was switched off. I don't like to post hearsay so let's forget about that until I get hard facts.
I found a bad cable connector (a fact) that might be PART of the original problem but I'm sure it would account for 50% of the issues at most (again hearsay).
What I found most strange as a software developer myself was that the settings on one firmware were the same for the newer firmware. As in...... 1 settings memory and 2 firmware memories. So a factory reset of the settings would have to be done in the firmware intended for use to ensure all the default values were captured.
Before I did that, I activated the GS510 factory firmware with reset to defaults and that appeared to work just fine.
My next step is to go back to the GS510, make sure factory firmware is ok and move on to the latest firmware again and try that.
Although the issue was usually apparent in a short space of time, I did see it more frequently in sporadic patches. At the time, the GS510 reported that one of my devices was pushing out incorrect bpdu messages and that it, the GS510, was rejecting them. Very odd as I was sure all STP and BPDU forwarding and checking was switched off. I don't like to post hearsay so let's forget about that until I get hard facts.
I found a bad cable connector (a fact) that might be PART of the original problem but I'm sure it would account for 50% of the issues at most (again hearsay).
What I found most strange as a software developer myself was that the settings on one firmware were the same for the newer firmware. As in...... 1 settings memory and 2 firmware memories. So a factory reset of the settings would have to be done in the firmware intended for use to ensure all the default values were captured.
Hi Dave40,
Please only connect GS510TLP with PC, not connect with other device, keep your switch with default configuration(except for enable memory log severity filter as Debug) on v6.6.2.9, to check switch port will flap or not? If still flap, please give the time and frequency, logs.
Regards,
NETGEAR Employee.
Hi Dave40,
Please only connect GS510TLP with PC, not connect with other device, keep your switch with default configuration(except for enable memory log severity filter as Debug) on v6.6.2.9, to check switch port will flap or not? If still flap, please give the time and frequency, logs.
Regards,
NETGEAR Employee.
FW v6.6.2.6 gave this (g3 is edimax WAP1750)
<11> Jul 6 23:09:19 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2209 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:19 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2208 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:18 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2207 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:18 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2206 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:17 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2205 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:17 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2204 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:16 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2203 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:16 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2202 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:15 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2201 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:15 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2200 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:14 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2199 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:14 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2198 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:13 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2197 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:13 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2196 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:12 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2195 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jul 6 23:09:12 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2194 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jul 6 23:09:11 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2193 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type 0 Jan 1 00:01:47 1970 Spanning Tree Topology Change Received: MSTID: 0 g3 1 Jan 1 00:01:45 1970 Spanning Tree Topology Change Received: MSTID: 0 g3 2 Jan 1 00:01:43 1970 Spanning Tree Topology Change Received: MSTID: 0 g3 3 Jan 1 00:01:41 1970 Spanning Tree Topology Change Received: MSTID: 0 g3 4 Jan 1 00:01:39 1970 Spanning Tree Topology Change Received: MSTID: 0 g3 5 Jan 1 00:01:37 1970 Cold Start: Unit: 0
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
