NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1200 WAN aggregation slows down (requires reboot)
A few days back, I realized WAN aggregation was the only way I could get total bandwidth to use my 1.2gbs xfinity service due to the 1gbs ports on my CM1200. I successfully enabled WAN aggregation ...
I have the RAX120… and I noticed in the router conversation a two year old (long long) thread that this was happening for many people using different routers. Technically you’re correct, either side can loose sync, and even though the 1+1 connection is green… the sync layers from either side could prevent both ports from being used… using only port but now with the overhead of a failed sync layer.
How are you testing speeds?
Using the built in speedtest? If so, I wouldn't always trust that one as it doesn't always pick the best server to test from.
It could be the rebooting choosing a different server.
Just something to try next time it slows down
- Thanks. I am using the Netgear app on the phone. Certainty not pinpoint accurate! Lol… so no measuring for small changes. These are big repeatable changes which are consistent.
Before WAN aggregation… range was always 920-945mbs.
After WAN aggregation.. range was 1410-1440.
Like clockwork… after 22-24 hours… it just drops from the 1400mbs down to 800-840 …
Repeatable and consistent. After rebooting modem, back to 1400 for 22-24 hours.
I’ll keep looking otherwise, I’ll just have to disable, go back to my 940mbs … and wait for a good time to upgrade.Please post CM logs for review when you can.
Time Priority Description
Tue Mar 12 07:17:46 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 07:17:26 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 07:17:18 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 07:17:12 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) UCD invalid or channel unusable;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 07:06:53 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 07:06:46 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Tue Mar 12 07:06:40 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) UCD invalid or channel unusable;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 21:36:57 2024 Notice (6) CM-STATUS message sent. Event Type Code: 1; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 21:36:36 2024 Warning (5) MDD message timeout;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 12:54:12 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 12:54:05 2024 Critical (3) UCD invalid or channel unusable;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 12:53:56 2024 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 08 12:53:51 2024 Notice (6) TLV-11 - unrecognized OID;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) UCD invalid or channel unusable;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 06 12:58:09 2024 Notice (6) CM-STATUS message sent. Event Type Code: 5; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=28:80:88:af:53:60;CMTS-MAC=00:90:f0:64:09:00;CM-QOS=1.1;CM-VER=3.1;
- Could be!!! But since they have a history of crappy support and bad developers…. Might be time to try someone new. I’m tired of printed promises and bad support. Bought top of the line CM1200 and RAX120 … and they can’t give me a full generation…. Might be better off renting xfinity hardware.
