4 Messages
Speeds exact same after substantial upgrade - errors in log
I upgraded my plan from 1100/40 to 2100/300 the other day, and noticed I'm getting the exact same speeds (around 600/30) as before. I noticed in logs that I'm getting a few errors associate with T3 and UCD invalid or channel unusable errors. I am running a Netgear Nighthawk CM2000, have swapped coax cables and tested at modem. Same speeds.
Cable Diagnostic
Status: Good
Action:
Your setup looks fine. If you can't access the internet, make sure you properly activated the modem. If modem has been activated and you still can't access the internet, contact your service provider for troubleshooting help.
If you can access the internet but has other internet issue, the Netgear Cable Knowledge Base can provide additional troubleshooting info.
CM Status: Good
Downstream Status: Good
Downstream Power Level: Good
Downstream SNR Level: Good
Upstream Status: Good
Upstream Power Level: Good
Current Time: Mon Mar 31 17:51:46 2025
Startup Procedure
Acquire Downstream Channel: 519000000 Hz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD IPv6 only
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 20 519000000 Hz 1.6 43.9 0 0
2 Locked QAM256 1 405000000 Hz 0.4 43.9 0 0
3 Locked QAM256 2 411000000 Hz 0.5 43.5 0 0
4 Locked QAM256 3 417000000 Hz -0.3 43.4 0 0
5 Locked QAM256 4 423000000 Hz 0 43.7 0 0
6 Locked QAM256 5 429000000 Hz 0 43.7 0 0
7 Locked QAM256 6 435000000 Hz -0.3 43.6 0 0
8 Locked QAM256 7 441000000 Hz 0.9 44.2 0 0
9 Locked QAM256 8 447000000 Hz 1.2 44.4 0 0
10 Locked QAM256 9 453000000 Hz 1.5 44.6 0 0
11 Locked QAM256 10 459000000 Hz 1.8 44.7 0 0
12 Locked QAM256 11 465000000 Hz 2 44.7 0 0
13 Locked QAM256 12 471000000 Hz 2.4 44.8 0 0
14 Locked QAM256 13 477000000 Hz 2.3 44.8 0 0
15 Locked QAM256 14 483000000 Hz 2.1 44.7 0 0
16 Locked QAM256 15 489000000 Hz 2 44.7 0 0
17 Locked QAM256 16 495000000 Hz 1.8 44.5 0 0
18 Locked QAM256 17 501000000 Hz 1.6 44.6 0 0
19 Locked QAM256 18 507000000 Hz 2.1 44.6 0 0
20 Locked QAM256 19 513000000 Hz 1.9 44.7 0 0
21 Locked QAM256 21 525000000 Hz 1.8 44.5 0 0
22 Locked QAM256 22 531000000 Hz 1.7 44.1 0 0
23 Locked QAM256 23 537000000 Hz 1 43.9 0 0
24 Locked QAM256 24 543000000 Hz 0.5 43.4 0 0
25 Locked QAM256 25 549000000 Hz 0 42.9 0 0
26 Locked QAM256 26 555000000 Hz 0.8 43.7 0 0
27 Locked QAM256 27 561000000 Hz 0.4 43.8 0 0
28 Locked QAM256 28 567000000 Hz 0.8 43.9 0 0
29 Locked QAM256 29 573000000 Hz 1.6 44.3 0 0
30 Locked QAM256 30 579000000 Hz 1.2 44.1 0 0
31 Locked QAM256 31 585000000 Hz 1.2 44 0 0
32 Locked QAM256 32 591000000 Hz 1.1 44 0 0
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 17 5120 Ksym/sec 16400000 Hz 44.5 dBmV
2 Locked ATDMA 18 5120 Ksym/sec 22800000 Hz 43.8 dBmV
3 Locked ATDMA 19 5120 Ksym/sec 29200000 Hz 43.3 dBmV
4 Locked ATDMA 20 5120 Ksym/sec 35600000 Hz 42.8 dBmV
5 Not Locked Unknown 0 0 0 0.0
6 Not Locked Unknown 0 0 0 0.0
7 Not Locked Unknown 0 0 0 0.0
8 Not Locked Unknown 0 0 0 0.0
Downstream OFDM Channels
Channel LockedStatus ProfileID ChannelID Frequency Power SNR/MER ActiveSubcarrier Unerror Correctable Uncorrectable
1 Locked 0 ,1 ,2 ,3 193 722000000 Hz -1.42 dBmV 41.7 dB 628 ~ 3467 517658425 498182595 0
2 Locked 0 ,1 ,2 ,3 194 957000000 Hz -5.62 dBmV 39.0 dB 148 ~ 3947 536516032 500819420 0
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Not Locked 0 0 0 Hz 0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Mon Mar 31 10:29:05 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:28:58 2025 Notice (6) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:28:57 2025 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:28:50 2025 Notice (6) TLV-11 - unrecognized OID;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:28:42 2025 Notice (6) Honoring MDD; IP provisioning mode = IPv6
Mon Mar 31 10:28:38 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:28:32 2025 Warning (5) ToD request sent - No Response received;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv6
Time Not Established Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:20:32 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Mon Mar 31 10:20:01 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:45:58 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:45:32 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:44:04 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:36 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:32 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:31 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:25 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:24 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:19 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:19 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:16 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:16 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:16 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:15 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:03 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:03 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:01 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:01 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:01 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:43:00 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:57 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:56 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:55 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:55 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:54 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:54 2025 Critical (3) UCD invalid or channel unusable;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
Fri Mar 28 08:42:50 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
EG
Expert
•
109.5K Messages
2 days ago
The CM 2000 is not compatible with their new Next Gen / mid-split /enhanced upload speeds. These are the only third-party / retail purchased devices that are currently compatible;
As are their XB6, XB7, and XB8 rented gateway devices.
1
0
EG
Expert
•
109.5K Messages
1 day ago
Quite welcome ! And make sure that you are in a market area that has indeed been upgraded. Please post back here with how things turn out. Good luck !
1
0
user_yjmvxp
4 Messages
1 day ago
Logs coming from new modem:
0
0
EG
Expert
•
109.5K Messages
16 hours ago
Sometimes the cart gets put before the horse.... I'm going to escalate your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards for review. You should get a reply here in your topic. Good luck !
0
XfinityJustinC
Official Employee
•
1.1K Messages
16 hours ago
Hello, @user_yjmvxp thank you for the follow up posting after swapping to the CM3000. Sorry to see you are still experiencing issues and would definitely like to investigate further to ensure the equipment is provisioned correctly, and can further troubleshoot. Since I will need to gather some information to locate your account and we don't want that in our public conversation, when you have time please send a direct message.
To send a direct message:
Click "Sign In" if necessary
• Click the "Direct Message" icon in the upper right - it looks like a chat bubble
• Click the "New message" (pencil and paper) icon just to the right of Conversations
• Type "Xfinity Support" in the "To:" line - do not use the Employee's name!
• Type your message in the text area near the bottom of the window
• Press Enter to send it
To expedite your request, we ask that you please include your name, the account holder name (if different), and the service address
1
EG
Expert
•
109.5K Messages
14 hours ago
@user_yjmvxp @XfinityJustinC
Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
0