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
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 So I'm now using FW v6.6.2.9 - reset - reset to defaults - set IP to 192.168.50.233 and debug logging.
I'll monitor the switch for a few days and report back.
These:
<11> Jan 1 00:19:36 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2293 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jan 1 00:19:36 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2292 %% dot1sBpduReceive(): Invalid Forward Delay <11> Jan 1 00:19:35 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(269) 2291 %% dot1sBpduReceive(): Discarding the BPDU, since it is an invalid BPDU type <13> Jan 1 00:19:35 192.168.50.233-1 DOT1S[dtlTask]: dot1s_txrx.c(1246) 2290 %% dot1sBpduReceive(): Invalid Forward Delay
Those are from the Sky Q router.
Test method:
I disconnected everything. All that was plugged in was GS510 and my PC and cleared log and no new message.
I connected Sky Q to port 1 and the BPDU messages flood in. So Edimax wifi wasn't the source - even though it is putting out STP frames?
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
