Reply

Re: GS510TLP Port flapping

Dave40
Aspirant

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 (which was the reason the GS108T port flapped.  Once the reset was done on that the issue went away).  Anyway, port flats, any port.

 

Message 1 of 18

Accepted Solutions
Dave40
Aspirant

Re: GS510TLP Port flapping

Since the bad cable was found I have not seen anymore port flapping.  Strange that it affected several ports

View solution in original post

Message 16 of 18

All Replies
Dave40
Aspirant

Re: GS510TLP Port flapping

<13> Jun 24 11:51:10 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 826 %% Link Down: g5
<15> Jun 24 11:51:10 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 825 %% HAPI LS callback, u 0. p 6
<15> Jun 24 11:43:36 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 824 %% SNTP: system clock synchronized on Sun Jun 24 11:43:36 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (185.186.77.153).
<15> Jun 24 11:42:31 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 823 %% SNTP: system clock synchronized on Sun Jun 24 11:42:31 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (185.186.77.153).
<15> Jun 24 11:41:25 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 822 %% SNTP: system clock synchronized on Sun Jun 24 11:41:25 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (129.250.35.251).
<15> Jun 24 11:40:19 192.168.50.233-1 SNTP[SNTP]: sntp_client.c(1913) 821 %% SNTP: system clock synchronized on Sun Jun 24 11:40:19 2018 UTC. Indicates that SNTP has successfully synchronized the time of the box with the server (95.215.175.2).
<13> Jun 24 11:21:44 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 820 %% Link Up: g5
<15> Jun 24 11:21:44 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 819 %% HAPI LS callback, u 0. p 6
<13> Jun 24 11:21:40 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 818 %% Link Down: g5
<15> Jun 24 11:21:40 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 817 %% HAPI LS callback, u 0. p 6
<13> Jun 24 11:21:00 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 816 %% Link Up: g5
<15> Jun 24 11:21:00 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 815 %% HAPI LS callback, u 0. p 6
<13> Jun 24 11:20:56 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 814 %% Link Down: g5
<15> Jun 24 11:20:56 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 813 %% HAPI LS callback, u 0. p 6
<13> Jun 24 11:20:35 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 812 %% Link Up: g5
<15> Jun 24 11:20:35 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 811 %% HAPI LS callback, u 0. p 6
<13> Jun 24 11:19:40 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 810 %% Link Up: g4
<15> Jun 24 11:19:40 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 809 %% HAPI LS callback, u 0. p 5
<13> Jun 24 11:19:37 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 808 %% Link Down: g5
<15> Jun 24 11:19:37 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 807 %% HAPI LS callback, u 0. p 6
<13> Jun 24 11:19:35 192.168.50.233-1 TRAPMGR[trapTask]: traputil.c(721) 806 %% Link Up: g5
<15> Jun 24 11:19:35 192.168.50.233-1 DRIVER[bcmLINK.0]: broad_link.c(83) 805 %% HAPI LS callback, u 0. p 6
Message 2 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

Please tell me what those broadcom drivers errors mean - bad firmware?

Why is SNTP going baserk?

Message 3 of 18
DaneA
NETGEAR Moderator

Re: GS510TLP Port flapping

Hi @Dave40,

 

Kindly answer the questions below:

 

a. Was the GS510TLP switch working fine before?

b. Does all the ports flap even before you updated the firmware and factory reset the GS510TLP switch? 

c. How is everything connected?  It would be best if you post an image or screenshot of your detailed network setup.

 

 

Regards,

 

DaneA
NETGEAR Community Team

Message 4 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

a) So the switch is new and I had no issues prior to the switch install.  Was using a GS108T

 

b) never tried the default factory firmware. It is still available on image2 and is 6.6.2.6.  On installation I updated the firmware and configured the settings.  I ran it for about a month and observed this port flapping and TCP connection failure issues across all devices - I've been too busy to fix. I will attempt to try the factory firmware after a few more days of testing.

 

c) Internet Sky Q => GS108T (now swapped for an old FS105 dumb switch 100MB) => GS510TLP => Computer, WiFi, TV etc

I've had everything disconnected apart from the FS105, Sky Q and the GS510TLP and WiFi and the problem is still there with this new switch - it was not there before I bought it.

 

Yesterday, I disabled the SNTP (made it local time) and lo and behold the mental time checks (every few seconds and sporadically in bursts) have stopped (obviously, because it's now off) but also the port flapping appears much reduced and possibly cured.  I won't declare it solved yet as 1 days isn't suffient in my eyes.  So I'll monitor.  If I confirm SNTP issue then I'll report back - I'll also try the 6.6.2.6 to see if the problem exists there.

 

Changes from DEFAULT config is that I disable STP, set SNTP to 0.uk.pool.ntp.org

 

Have tried: IGMP OFF (think it was on but also had the problem before I turned that off), ARP renew is now OFF but had the issue before this was changed .

 

I have just noticed that DNS is enabled but no DNS server entered.  I can't remember if I had this set before with SNTP.  I have factory reset a few times since.  Anyway, SNTP with no DNS server (but set to enabled) was the last known config that was causing this issue (with STP off also).

Message 5 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

I must clarify the amount the SNTP I had in the logs = it was sincerily a lot of entries.  I was only able to supply a small snapshot due to the character limits on the forum.  It was sporadic but with entries of 10-20 every few seconds.  Polling was very high despite successfully updating time and resolving the DNS supplied. (probably without the DNS servers specified - really can't remember setting this)

Message 6 of 18
DaneA
NETGEAR Moderator

Re: GS510TLP Port flapping

@Dave40,

 

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

Message 7 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

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.
Message 8 of 18
DaneA
NETGEAR Moderator

Re: GS510TLP Port flapping

@Dave40,

 

Thanks for the feedback.  It would be best if you open a chat or online support ticket with NETGEAR Support here at anytime.  Your concern might get escalated to the engineering team for further investigation as well as for the switch logs to be analyzed.

 

 

Regards,

 

DaneA
NETGEAR Community Team

Message 9 of 18
ElaineP
NETGEAR Expert

Re: GS510TLP Port flapping

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.

510.jpg

 

Regards,

NETGEAR Employee.

Message 10 of 18
ElaineP
NETGEAR Expert

Re: GS510TLP Port flapping

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.

510.jpg

 

Regards,

NETGEAR Employee.

Message 11 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

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
Message 12 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

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
Message 13 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

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.

Message 14 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

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?

 

Message 15 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

Since the bad cable was found I have not seen anymore port flapping.  Strange that it affected several ports

Message 16 of 18
Dave40
Aspirant

Re: GS510TLP Port flapping

Confirmed the port flapping was a bad connector plug.  I've not had any issues since I re-seated the plug.  Plan to fully rewire and remove the plug and socket sometime soon.

Anyway, never had a reply concerning the spanning tree mystery.  I still have that but it doesn't cause any issues.

There are 21x spanning tree topo change received messages with a link down /up on g3.

So whenever g3 goes down up then I get the same pattern.  How do I find out which device is Unit 1?

 

53 Jul 13 20:40:21 2018 Spanning Tree Topology Change Received: MSTID: 0 g3
54 Jul 13 20:40:19 2018 Spanning Tree Topology Change Received: MSTID: 0 g3
55 Jul 13 20:39:49 2018 Spanning Tree Topology Change Initiated: 0, Interface: g3
56 Jul 13 20:39:49 2018 Spanning Tree Topology Change: 0, Unit: 1
57 Jul 13 20:39:48 2018 Link Up: g3
58 Jul 13 20:39:45 2018 Unit 1 elected as the new STP root
59 Jul 13 20:39:45 2018 Link Down: g3

 

Message 17 of 18
DaneA
NETGEAR Moderator

Re: GS510TLP Port flapping

@Dave40,

 

Are you seeing this log on the GS510TLP switch?  If yes, what is the device connected to port 3?   

 

c) Internet Sky Q => GS108T (now swapped for an old FS105 dumb switch 100MB) => GS510TLP => Computer, WiFi, TV etc

I've had everything disconnected apart from the FS105, Sky Q and the GS510TLP and WiFi and the problem is still there with this new switch - it was not there before I bought it.

This is the network setup you mentioned before.  If ever FS105 switch is still the switch connected to the GS510TLP, it seems that STP is not needed because the FS105 does not support STP.  Kindly try to disable STP on the GS510TLP switch and observe.

 

 

Regards,

 

DaneA

NETGEAR Community Team

Message 18 of 18
Top Contributors
Discussion stats
  • 17 replies
  • 8194 views
  • 0 kudos
  • 3 in conversation
Announcements