NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

jaydubzok's avatar
jaydubzok
Aspirant
Mar 17, 2023

CM1000V2 terrible upload/download latencies, HUGE SPIKES HUGE HEADACHES.

PLEASE HELP, BEEN DEALING WITH THESE ISSUES FOR AWHILE, TOTAL HEADACHE. Been having horrid spikes under load esp with upload when it's spiking well over 100ms and online gaming is **bleep**ing terri...
jaydubzok's avatar
jaydubzok
Aspirant
Aug 19, 2023

Thanks for your quick reply, here's the logs below. Is it the correctables on the downstream that should be 0? Been back and forth with my ISP with no resolution for awhile, new rg6 cables, etc. 

 

Using CAT 8, using a Netduma R2 for a router, I can test here in a bit doing a direct connection. 

 

 

 

 
 
 
 
Time Priority Description
2023-08-18, 21:41:07 Warning (5) DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:41:07 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:56 Warning (5) REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:56 Notice (6) US profile assignment change. US Chan ID: 8; Previous Profile: 13; New Profile: 11 13.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:52 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Notice (6) TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Error (4) Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Error (4) Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 21:27:48 Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;CM-MAC=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 19:07:56 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 19:07:45 Critical (3) REG RSP not received;CM-MAC=;CMTS-MAC=;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=;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-08-18, 09:33:11 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:57 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:57 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:47 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:45 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:45 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:39 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:37 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:37 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:31 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:31 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:31 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:23 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:22 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:22 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:15 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:13 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:13 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:05 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:03 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:30:03 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:53 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:53 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:53 Critical (3) Ranging Request Retries exhausted;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:43 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2023-08-17, 19:29:41 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 8;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Aug 20, 2023

Yes.

 

Any Criticals, Errors or Warnings seen in the event logs needs to be reviewed and resolved by the ISP. Indicates a signal issue on the ISP line up to the modem.

Have the ISP check the signal and line quality UP to the modem. Be sure the ISP provisions the modem correctly.
Be sure there are no coax cable line splitters in the between the modem and ISP service box. 
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, loose connections, bad/old/cheap connectors, or corroded connections. Replace them if you do.
Be sure to power OFF the modem for 1 minute then back ON.
https://community.netgear.com/t5/Cable-Modems-Routers/General-info-and-Troubleshooting-for-Cable-Modems/m-p/1530376#M12853
https://kb.netgear.com/24311/Power-level-guidelines-for-a-NETGEAR-cable-modem-router
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/