NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
Solved
GS110T/GS110TP Multicast overload bug
Hi, I have the following switches on a network, and they all suffer from this issue:
2x GS110T (v5.4.0.6 - latest?)
2x GS110TP (v5.4.2.30 - latest?)
1x GS110TP (v5.0.5.4)
1x GS110TP (v5.4...
Hi DaneA,
Sorry for the delay, I had been trying to make sure that everything was stable with the updated firmwares before updating.
As you say they were able to provide an updated firmware, that appears to be working fine for the GS110TP models.
for the GS110T switches I was given a work around from Engineering, which I will post below for anyone else who has this problem:
"The root cause is, the reserved range multicast packets comes to switch CPU and the IGMP application fowards them to other ports in same VLAN. Since, the packets are coming at high rate, CPU is becoming slow and failing to open GUI connection.
On GS110T, you can try installing an ACL and drop the multicast packets in the range 224.0.0.1 to 224.0.0.255. If you need these packets, then configure ACL with redirect action (redirect the matched packets to desired port)."Cheers
James
Hi DaneA,
As per my first post, I already have several of the switches running on the most recent firmware(s), and the problem is still there. I have tried factory resets as well and that makes no difference.
In this situation, the Web GUI IS affected, my use of the pings were to purely demonstrate when things stop working. The GUI stops functioning at exactly the same time.
From the trace provided, it should be possible to see that we are not dealing with a high volume of traffic at all, and that there is some processing that the switch is trying to perform and failing at.
Has anyone actually tried sending the data in the trace across a switch on a test bench yet? That response from higher tier reads as suspiciously like a stock answer to me.
Cheers
James
As per my first post, I already have several of the switches running on the most recent firmware(s), and the problem is still there. I have tried factory resets as well and that makes no difference.
In this situation, the Web GUI IS affected, my use of the pings were to purely demonstrate when things stop working. The GUI stops functioning at exactly the same time.
From the trace provided, it should be possible to see that we are not dealing with a high volume of traffic at all, and that there is some processing that the switch is trying to perform and failing at.
Has anyone actually tried sending the data in the trace across a switch on a test bench yet? That response from higher tier reads as suspiciously like a stock answer to me.
Cheers
James
The suggestion about having all switches be on the latest firmware version is a way to isolate more of the problem in order to see what would be the result if ever the same problem will occur if all of the switches in the star topology are on the latest firmware version.
The Wireshark packet trace you have provided was checked by the higher tier of NETGEAR Support that is why they came up with the suggestion mentioned.
Regards,
DaneA
NETGEAR Community Team
NETGEAR Academy
Boost your skills with the Netgear Academy - Get trained, certified and stay ahead with the latest Netgear technology!
Join Us!
