NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM3000 Cable Modem Upload Stream Issues
I have had Cox communications to my house several times in the past month and a half. They've replaced all the cable connections both in and out of my house. I have 2 gig download 100+MBPS upload. ...
Firmware version is 6.01.03
Connections Status
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: Fri Sep 12 06:22:17 2025
Startup Procedure
Acquire Downstream Channel: 759000000 Hz Locked
Connectivity State: OK Operational
Boot State: OK Operational
Security: Enabled BPI+
IP Provisioning Mode: Honor MDD IPv4 only
Downstream Bonded Channels
Channel LockedStatus Modulation ChannelID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 5 759000000 Hz -0.5 42.7 0 0
2 Locked QAM256 1 735000000 Hz -0.3 43.1 0 0
3 Locked QAM256 2 741000000 Hz -0.5 42.9 0 0
4 Locked QAM256 3 747000000 Hz -0.4 42.9 0 0
5 Locked QAM256 4 753000000 Hz -0.5 42.8 0 0
6 Locked QAM256 6 765000000 Hz -0.8 42.7 0 0
7 Locked QAM256 7 771000000 Hz -0.9 42.6 0 0
8 Locked QAM256 8 777000000 Hz -0.9 42.6 0 0
9 Locked QAM256 9 783000000 Hz -1 42.5 0 0
10 Locked QAM256 10 789000000 Hz -1.1 42.4 0 0
11 Locked QAM256 11 795000000 Hz -1.3 42.3 0 0
12 Locked QAM256 12 801000000 Hz -1.1 42.1 0 0
13 Locked QAM256 13 807000000 Hz -1.3 42.1 0 0
14 Locked QAM256 14 813000000 Hz -1.3 42 0 0
15 Locked QAM256 15 819000000 Hz -1.2 42 0 0
16 Locked QAM256 16 825000000 Hz -1.2 42.1 0 0
17 Locked QAM256 17 831000000 Hz -1.1 42.1 0 0
18 Locked QAM256 18 837000000 Hz -1.1 42.1 0 0
19 Locked QAM256 19 843000000 Hz -1.1 42.1 0 0
20 Locked QAM256 20 849000000 Hz -0.9 42.2 0 0
21 Locked QAM256 21 855000000 Hz -1.2 42.1 0 0
22 Locked QAM256 22 861000000 Hz -1.2 42.1 0 0
23 Locked QAM256 23 867000000 Hz -1.5 42 0 0
24 Locked QAM256 24 873000000 Hz -1.3 41.9 0 0
25 Locked QAM256 41 213000000 Hz 0.6 44 2 0
26 Locked QAM256 42 219000000 Hz 0.5 44 3 0
27 Locked QAM256 43 225000000 Hz 0.3 44 1 0
28 Locked QAM256 44 231000000 Hz 0.2 43.8 1 0
29 Locked QAM256 45 237000000 Hz 0.2 39.2 1 0
30 Locked QAM256 46 243000000 Hz 0.2 38.2 470710 165
31 Locked QAM256 47 249000000 Hz 0.2 38 38 0
32 Locked QAM256 48 255000000 Hz 0.1 43.6 4 0
Upstream Bonded Channels
Channel LockedStatus ChannelType ChannelID SymbolRate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 16900000 Hz 42.8 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 23500000 Hz 42.8 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 29900000 Hz 42.8 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 36300000 Hz 43.3 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 159 300000000 Hz -0.22 dBmV 43.4 dB 296 ~ 7895 444807898 233749043 0
2 Locked 0 ,1 ,2 ,3 160 918000000 Hz -0.12 dBmV 42.0 dB 2216 ~ 5975 591000640 142733067 1
Upstream OFDMA Channels
Channel LockedStatus ProfileID ChannelID Frequency Power
1 Locked 9 ,13 6 36800000 Hz 39.0 dBmV
2 Not Locked 0 0 0 Hz 0 dBmV
Event Log
Time Priority Description
Thu Sep 11 21:50:21 2025 Notice (6) US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 9 13.;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 21:49:32 2025 Warning (5) Dynamic Range Window violation
Thu Sep 11 21:49:32 2025 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 21:49:26 2025 Notice (6) DS profile assignment change. DS Chan ID: 33; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 21:49:24 2025 Notice (6) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 21:49:19 2025 Notice (6) TLV-11 - unrecognized OID;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Warning (5) DHCP WARNING - Non-critical field invalid in response ;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Notice (6) Honoring MDD; IP provisioning mode = IPv4
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 19:28:09 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 15:24:41 2025 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 12:26:20 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Thu Sep 11 12:26:16 2025 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;CM-QOS=1.1;CM-VER=3.1;
Time Not Established Critical (3) No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:c0:98;CMTS-MAC=6c:13:d5:21:a5:d6;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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00: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=54:07:7d:c4:c0:98;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Event Log
| |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
Help Center
Show/Hide Help Center
Ok, so there is a known issue with FW v6 on these modems. NG is aware of it. You'll need to contact the ISP and have them revert the FW back to prior v5 or what ever they had been using before v6 FW was loaded on it and there the only ones that can load FW on user modems. CC/XF have already been reverting there users back for this model modem. After reverting, modems are working.
After that, check the event logs page again. Currently theres too many criticals and warnings that the ISP needs to resolve. However check again after v5 FW is loaded back on by the ISP. If you still see issues there with criticals, errors and warnings, have the ISP check all up to the modem.
The cable connections log and data looks good. No issues there.
Thanks for the info. I don't believe Cox does firmware updates on modems they didn't sell correct? Can I obtain a version of the firmware to apply?
You'll need to ask them that. Ask for escalated support from the ISP. They should be aware of this issue as NG has been working with the ISPs about this v6 version. There all needing to downgrade until the v6 FW issue is fixed. Zero idea when that will be.
ALL ISPs handle cable modem FW updates. There is not user path for updating cable modem FW. Been like this for years. ISPs control all of that.
According to Cox they don't do firmware downgrades and they're waiting for the fix from Netgear. They offerred one of their modems to use in the meantime.