CM1000v2 Slow upload speeds

[tomc38]

I was wondering if anyone could help me out with my CM1000v2 modem. I am getting super slow upload speeds (2-5mbps when I pay for 50) and  my ISP is saying its my problem and they dont see any issues. I know very little about networking so I was hoping someone could look at the cable connection and tell me if there is anything wrong here. Thanks!

<tabindex=-1>Startup Procedure</tabindex=-1>

Procedure Status Comment Acquire Downstream Channel 801000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Disabled Disabled IP Provisioning Mode Honor MDD IPv4 only

<tabindex=-1>Downstream Bonded Channels (Partial Service)</tabindex=-1>

Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked QAM256 23 801000000 Hz -8.0 dBmV 39.6 dB 236440456 121 47 2 Locked QAM256 1 669000000 Hz -2.5 dBmV 41.6 dB 235388032 101 43 3 Locked QAM256 2 675000000 Hz -3.9 dBmV 40.9 dB 235391784 106 35 4 Locked QAM256 3 681000000 Hz -6.0 dBmV 40.4 dB 235395244 92 41 5 Locked QAM256 4 687000000 Hz -7.7 dBmV 39.5 dB 235398999 111 39 6 Locked QAM256 5 693000000 Hz -7.9 dBmV 39.4 dB 235402616 128 51 7 Locked QAM256 6 699000000 Hz -7.4 dBmV 39.6 dB 235406294 110 53 8 Locked QAM256 7 705000000 Hz -7.0 dBmV 39.8 dB 235410107 125 42 9 Locked QAM256 8 711000000 Hz -7.2 dBmV 39.8 dB 235413961 119 51 10 Locked QAM256 9 717000000 Hz -7.6 dBmV 39.5 dB 235417554 105 43 11 Locked QAM256 10 723000000 Hz -7.7 dBmV 39.6 dB 235419634 118 39 12 Locked QAM256 11 729000000 Hz -7.3 dBmV 39.7 dB 235423218 125 42 13 Locked QAM256 12 735000000 Hz -6.4 dBmV 40.3 dB 235426649 98 36 14 Locked QAM256 13 741000000 Hz -5.4 dBmV 40.7 dB 235430698 99 43 15 Locked QAM256 14 747000000 Hz -4.8 dBmV 40.9 dB 235434394 96 43 16 Locked QAM256 15 753000000 Hz -4.8 dBmV 41.0 dB 235438502 116 38 17 Locked QAM256 16 759000000 Hz -4.7 dBmV 41.1 dB 235442290 84 37 18 Locked QAM256 17 765000000 Hz -5.4 dBmV 40.7 dB 235445831 85 41 19 Locked QAM256 18 771000000 Hz -6.6 dBmV 40.1 dB 235449521 105 39 20 Locked QAM256 19 777000000 Hz -7.4 dBmV 39.8 dB 235453035 136 40 21 Locked QAM256 20 783000000 Hz -7.1 dBmV 39.9 dB 235460377 104 45 22 Locked QAM256 21 789000000 Hz -7.1 dBmV 40.0 dB 235476647 111 41 23 Locked QAM256 22 795000000 Hz -7.5 dBmV 39.8 dB 235467504 127 43 24 Locked QAM256 24 807000000 Hz -8.1 dBmV 39.6 dB 235472262 119 43 25 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 26 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 27 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 28 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 29 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 30 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 31 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0 32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

<tabindex=-1>Upstream Bonded Channels</tabindex=-1>

Channel Lock Status Modulation Channel ID Frequency Power 1 Locked ATDMA 1 36800000 Hz 45.0 dBmV 2 Locked ATDMA 2 30400000 Hz 45.8 dBmV 3 Locked ATDMA 3 24000000 Hz 44.5 dBmV 4 Locked ATDMA 4 17600000 Hz 45.0 dBmV 5 Not Locked Unknown 0 0 Hz 0.0 dBmV 6 Not Locked Unknown 0 0 Hz 0.0 dBmV 7 Not Locked Unknown 0 0 Hz 0.0 dBmV 8 Not Locked Unknown 0 0 Hz 0.0 dBmV

<tabindex=-1>Downstream OFDM Channels</tabindex=-1>

Channel Lock Status Modulation / Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords 1 Locked 0, 1, 2, 3 159 484000000 Hz 0.3 dBmV 0.0 dB 0 ~ 4095 0 0 0 2 Locked 0, 1, 2, 3 160 831000000 Hz -6.7 dBmV 38.8 dB 3176 ~ 5015 118464467 26115941 33

<tabindex=-1>Upstream OFDMA Channels</tabindex=-1>

Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked Unknown 0 0 Hz 0 dBmV 2 Not Locked Unknown 0 0 Hz 0 dBmV

Current System Time: Thu Mar 16 14:38:46 2023

System Up Time: 1:27:02

[plemans · Accepted solution]

ISP's fight not to come out. 

Its their main goal in life is to make money off existing infrastructure without having to do maintenence on it. 

You have errors (the codewords) and t3/t4 errors. They indicate a connection issue with the isp. 

So if you're directly connected to the line coming in and you know that end connector is good, it doesn't leave much that could be the problems. It could always be the modem so thats the chance you take but the errors/logs indicate the line. 

[tomc38]

Sorry I just realized I posted this under routers and not modems and I cant figure out how to change it. Here is the log too.

Time	Priority	Description
2023-03-16, 18:12:05	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 18:08:21	Critical (3)	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:18:11	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:58	Notice (6)	CM-STATUS message sent. Event Type Code: 1; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:42	Warning (5)	MDD message timeout;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:37	Notice (6)	CM-STATUS message sent. Event Type Code: 21; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:29	Warning (5)	Dynamic Range Window violation
2023-03-16, 17:12:29	Warning (5)	RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:28	Warning (5)	REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:28	Warning (5)	RCS Partial Service;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:23	Notice (6)	DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:22	Notice (6)	DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-16, 17:12:18	Notice (6)	TLV-11 - unrecognized OID;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Warning (5)	DHCP WARNING - Non-critical field invalid in response ;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP FAILED - Discover sent, no offer received;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Notice (6)	Honoring MDD; IP provisioning mode = IPv4
Time Not Established	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;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=9c:c9:eb:96:8e:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:48:06	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;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=9c:c9:eb:96:8e:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:47:04	Critical (3)	Resetting the cable modem due to docsDevResetNow
2023-03-06, 16:35:59	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;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=9c:c9:eb:96:8e:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:18:07	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:17:58	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:17:37	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:17:28	Critical (3)	REG-RSP - invalid format or not recognized;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-03-06, 16:17:28	Critical (3)	REG RSP not received;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
Time Not Established	Critical (3)	DHCP FAILED - Request sent, No response;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;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=9c:c9:eb:96:8e:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-02-18, 14:30:25	Critical (3)	Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-02-17, 17:01:17	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-02-17, 17:01:15	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-02-17, 17:01:12	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-02-17, 17:01:11	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-02-17, 17:00:35	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-02-17, 17:00:25	Critical (3)	SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;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=9c:c9:eb:96:8e:08;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
2023-01-23, 23:39:41	Critical (3)	No Ranging Response received - T3 time-out;CM-MAC=9c:c9:eb:96:8e:08;CMTS-MAC=24:7e:12:f1:19:d2;CM-QOS=1.1;CM-VER=3.1;
2023-01-23, 23:39:34	Critical (3)	TFTP Request Retries exceeded, CM unable to register

[plemans]

Your logs and cable connections page are indicating line issues. 

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.
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.

[tomc38]

Thanks for the response. Is there anything specific I can point out to my ISP that indicate its a line issue. I am having a difficult time even trying to get someone to come to the house for testing because they say everything looks fine and since I dont rent their modem they just blame the one I own. My current setup is very simple and the modem is connected right where the cable comes into the house. There is a box on the outside of the house where the line from the street goes into a connector and then the cable running out of the connector goes into the wall outlet that the modem is connected to.

I have also been wondering if weather could be the cause. Both days I have had issues have been 2 days after a snow storm when things started melting. Maybe there is moisture getting in somewhere? The box on my house seems to be totally dry. The first time the issue occurred it resolved itself the next day but now a week later its back.

[plemans · Accepted solution]

ISP's fight not to come out. 

Its their main goal in life is to make money off existing infrastructure without having to do maintenence on it. 

You have errors (the codewords) and t3/t4 errors. They indicate a connection issue with the isp. 

So if you're directly connected to the line coming in and you know that end connector is good, it doesn't leave much that could be the problems. It could always be the modem so thats the chance you take but the errors/logs indicate the line. 

[tomc38]

Thanks for your help, I appreciate it!