4 Messages
Internet Dropping randomly, getting worse everyday
Unsure what is going on. Only fix is to reset my Netgear Nighthawk CM2000 cable modem. Logged into it, found a lot of error codes. I currently have the fastest Xfinity residential plan available (1.2 Mbps down, 40 up).
Error logs for just today below (MAC Addresses Removed)
Time | Priority | Description |
Mon May 13 19:19:00 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:18:58 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:17:00 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 42 43 44; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:58 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=94:a6:7e:fb:36:24;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:58 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 42 43 44 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=1;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:56 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=:d1;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:52 2024 | (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; |
Mon May 13 19:16:52 2024 | (Warning (5)) | RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:46 2024 | (Critical (3)) | SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:44 2024 | (Warning (5)) | MDD message timeout;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:43 2024 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:43 2024 | (Critical (3)) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:43 2024 | (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; |
Mon May 13 19:16:41 2024 | (Warning (5)) | RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:38 2024 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:29 2024 | (Warning (5)) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:22 2024 | (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; |
Mon May 13 19:16:21 2024 | (Warning (5)) | RCS Partial Service;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:16:00 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 24 25 36; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:14:01 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 36; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=9;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:13:57 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 2; Chan ID: 36; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:13:57 2024 | (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; |
Mon May 13 19:13:54 2024 | (Warning (5)) | RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:12:39 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 37 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:12:32 2024 | (Warning (5)) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:12:24 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:12:20 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:12:18 2024 | (Warning (5)) | MDD message timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:11:52 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 37 38 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:11:20 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 5; Chan ID: 39; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:10:57 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:10:54 2024 | (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; |
Mon May 13 19:10:54 2024 | (Warning (5)) | RCS Partial Service;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:10:49 2024 | (Critical (3)) | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=9;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:10:49 2024 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 19:09:35 2024 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=CMTS-MAC=CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 18:58:44 2024 | (Warning (5)) | Dynamic Range Window violation |
Mon May 13 18:58:44 2024 | (Warning (5)) | RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Mon May 13 18:58:43 2024 | (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; |
Mon May 13 18:58:30 2024 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1; |
Menelaus
4 Messages
26 days ago
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.
Number Range
Codewords
Codewords
Codewords
0
0
EG
Expert
•
103.9K Messages
25 days ago
This may or may not be the root cause of the problem (YMMV) but it should be addressed regardless.
The downstream power is on the low / weak side and it may be intermittently fluctuating even lower to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.
In an effort to try to obtain better connectivity / more wiggle room, check to see if there are any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1002 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.
Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.
If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.
(edited)
1
EG
Expert
•
103.9K Messages
25 days ago
Ok so if the problem returns / continues you'll need to get a tech out to investigate as stated. Good luck with it and please post back with how things turn out.
0