NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1200 slows down after 24-48 hours of uptime when using link aggregation
If I hook up my CM1200 to my router (an Asus RT-AX88U) in Link Aggregation mode, it seems to be consistenly slow down to only around 66-ish% of the full connection speed after somewhere between 24 an...
Did you read my post????? It is not the modem, it is Comcast. Read my post and do AS I did and it will fix your issues
I've been having these issues with RCN, as well, so it is clearly not something entirely specific to Comcast.
- I dont have an issue. So believe me or not.
CGASTON: It's not that we don't believe you; it's just that without any metrics to go over with the ISP to indicate the problem is on their side, it's hard to justify calling and asking them to do something about it. Since the issue seems to be across multiple ISPs and the fact that disabling link aggregation resolves the issue, it would make more sense to be related to the CM1200 rather than the upstream provider.
Having said that, since you're no longer having the issue, can you provide screenshots showing that link aggregation is indeed still enabled, the firmware version, and showing the system up time is over 48 hours?
And since I hit the issue again this morning, I wanted to add the increased latency metrics that I see when the issue occurs. As you can see, the issue is local to the cable modem.
$ ping 192.168.100.1
PING 192.168.100.1 (192.168.100.1): 56 data bytes
64 bytes from 192.168.100.1: icmp_seq=0 ttl=63 time=255.084 ms
64 bytes from 192.168.100.1: icmp_seq=1 ttl=63 time=281.300 ms
64 bytes from 192.168.100.1: icmp_seq=2 ttl=63 time=295.809 ms
64 bytes from 192.168.100.1: icmp_seq=3 ttl=63 time=308.160 ms
64 bytes from 192.168.100.1: icmp_seq=4 ttl=63 time=282.951 ms
64 bytes from 192.168.100.1: icmp_seq=5 ttl=63 time=296.976 ms
64 bytes from 192.168.100.1: icmp_seq=6 ttl=63 time=314.000 ms
64 bytes from 192.168.100.1: icmp_seq=7 ttl=63 time=308.621 ms
64 bytes from 192.168.100.1: icmp_seq=8 ttl=63 time=211.340 ms
64 bytes from 192.168.100.1: icmp_seq=9 ttl=63 time=229.270 ms
64 bytes from 192.168.100.1: icmp_seq=10 ttl=63 time=315.650 ms
64 bytes from 192.168.100.1: icmp_seq=11 ttl=63 time=357.060 ms
64 bytes from 192.168.100.1: icmp_seq=12 ttl=63 time=265.974 ms
64 bytes from 192.168.100.1: icmp_seq=13 ttl=63 time=326.605 ms
64 bytes from 192.168.100.1: icmp_seq=14 ttl=63 time=268.339 ms
64 bytes from 192.168.100.1: icmp_seq=15 ttl=63 time=290.238 ms
64 bytes from 192.168.100.1: icmp_seq=16 ttl=63 time=336.371 ms
64 bytes from 192.168.100.1: icmp_seq=17 ttl=63 time=347.420 ms
64 bytes from 192.168.100.1: icmp_seq=18 ttl=63 time=369.044 ms
64 bytes from 192.168.100.1: icmp_seq=19 ttl=63 time=262.031 ms
64 bytes from 192.168.100.1: icmp_seq=20 ttl=63 time=278.381 ms
64 bytes from 192.168.100.1: icmp_seq=21 ttl=63 time=284.568 ms
^C--- 192.168.100.1 ping statistics ---
22 packets transmitted, 22 packets received, 0% packet loss
round-trip min/avg/max/stddev = 211.340/294.781/369.044/38.279 ms$ traceroute 192.168.100.1
traceroute to 192.168.100.1 (192.168.100.1), 64 hops max
1 10.0.0.1 0.141ms 0.165ms 0.122ms
2 192.168.100.1 276.441ms 245.408ms 259.397msNormally this is sub-1ms. Attaching screenshots showing the statistics to the CMTS are unchanged, my uptime is over two days, link aggregation is enabled and active, and I'm running the latest available firmware.
I have opened a NETGEAR support ticket for this issue.
Thanks,
Kenny