This topic has been marked solved and closed to new posts due to inactivity. We hope you'll join the conversation by posting to an open topic or starting a new one.
Hello, Ive been having issues with gaming while gaming on my Netgear CM600. My latency variation is high and it causes a bit of rubber banding in online first person shooters. I have tried using the CM600 without a router and with a router that contains anti buffer bloat software. After doing a lot of research and purchasing new routers and talking with my ISP (Spectrum) to no avail, I have come to the conclusion that it must be my modem. I logged into my modem recently and found that I was getting a lot of sync timing synchronization failures and read that this could be causing my issues with latency. How would I fix this? Below are all my readings for my modem. Note: there is a splitter in my wall panel where the coax comes from outside and I have tried removing it and latency issue remains.
Time Priority Description 2022-08-21, 22:35:07 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.1;CM-VER=3.0; 2022-08-21, 22:35:07 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.1;CM-VER=3.0; 2022-08-04, 21:36:14 Critical (3) Resetting the cable modem due to docsDevResetNow 2022-08-04, 21:07:27 Critical (3) Resetting the cable modem due to docsDevResetNow 2022-08-03, 23:54:41 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; 2022-08-03, 23:52:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) Ranging Request Retries exhausted;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) Ranging Request Retries exhausted;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) Ranging Request Retries exhausted;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) Ranging Request Retries exhausted;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:17:10:88:a4:9a;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire FEC framing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=38:94:ed:d6:e6:d0;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0; Time Not Established Notice (6) Overriding MDD IP initialization parameters; IP provisioning mode = IPv6
Startup Procedure Procedure Status Comment Acquire Downstream Channel 357000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enable BPI+ IP Provisioning Mode Override MDD IPv6 only
Hello, the issue was due to something on the ISP side. After scheduling a tech visit, the next day I received a text that my service had been restored before the tech had even come. So after doing some testing there were no more latency issues. I’m not sure what they did but it seemed to work. Thank you all! Happy Gaming!
Start with removing any amplifiers, signal attenuators, or splitters from the coax. From there check the line for kinks, damage, moisture in the line. Check the connectors for improperly made ends, foil touching the copper coax line, bad/old/cheap connectors, or corroded connections. Replace them if you do. If you can, simply connect the modem right where the coax comes into the home. This prevents wiring in the home from being the issue. And some ISP’s charge if the wiring issue is in the home. So this helps prevent this.
Seems like theres issues with the line to the point the cmts is sending reboot signals
Will do! I will assemble and plug in modem where it comes it at my home. I’m sorry I forgot to mention in the original post that it was me that initiated those documented resets in the event log. I will return within 48 hours with an update and documented results. Thanks for your assistance in advance!
Hello, the issue was due to something on the ISP side. After scheduling a tech visit, the next day I received a text that my service had been restored before the tech had even come. So after doing some testing there were no more latency issues. I’m not sure what they did but it seemed to work. Thank you all! Happy Gaming!
