NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
was looking for some help / info on what to do gonna post my logs i bought a Nighthawk CM3000
and even before i got this i was having weird internet drop issues. i will post my logs and would love some feedback / help what to do. i tried swapping the splitter a few times.. i want to get rid of the splitter.. but my mom HAS to have her cable box plugged in. can i call my isp for them to just send 2 separate lines?
| Thu May 29 19:18:36 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 19:12:37 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 19:05:46 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:52:03 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:48:48 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:46:49 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 22; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:44:51 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:44:50 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 23; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:54 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:54 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:54 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:53 2025 | (Warning (5)) | MDD message timeout;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:47 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:41 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:37 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:34 2025 | (Warning (5)) | MDD message timeout;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:43:15 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:52 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:38 2025 | (Notice (6)) | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:37 2025 | (Notice (6)) | TLV-11 - unrecognized OID;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:36 2025 | (Error (4)) | Missing BP Configuration Setting TLV Type: 17.9;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:36 2025 | (Error (4)) | Missing BP Configuration Setting TLV Type: 17.8;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:30 2025 | (Notice (6)) | Overriding MDD IP initialization parameters; IP provisioning mode = IPv6 |
| Thu May 29 18:40:25 2025 | (Critical (3)) | No Ranging Response received - T3 time-out;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:40:16 2025 | (Warning (5)) | ToD request sent - No Response received;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:39:39 2025 | (Critical (3)) | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:39:33 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 21; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:39:33 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:39:33 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 20; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:39:25 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:39:24 2025 | (Warning (5)) | MDD message timeout;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:37:37 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:35:17 2025 | (Error (4)) | ToD request sent - No Response received;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:35:17 2025 | (Notice (6)) | DHCP Renew - lease parameters Time Protocol Servers modified;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:33:36 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:33:32 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:33:30 2025 | (Warning (5)) | MDD message timeout;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:33:25 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 4; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
| Thu May 29 18:33:18 2025 | (Notice (6)) | CM-STATUS message sent. Event Type Code: 1; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=54:07:7d:c4:70:90;CMTS-MAC=00:17:10:91:7a:02;CM-QOS=1.1;CM-VER=3.1; |
6 Replies
Startup Procedure Procedure Status Comment Acquire Downstream Channel 495000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode IPv6 Only IPv6 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 32 495000000 Hz 6.8 dBmV 37.9 dB 261 6 2 Locked QAM256 1 297000000 Hz 1.5 dBmV 38.8 dB 1644 6317 3 Locked QAM256 2 303000000 Hz 1.2 dBmV 38.6 dB 1296 5063 4 Locked QAM256 3 309000000 Hz 1.2 dBmV 38.6 dB 1356 6277 5 Locked QAM256 4 315000000 Hz 1.9 dBmV 38.9 dB 1268 6142 6 Locked QAM256 5 321000000 Hz 1.9 dBmV 38.8 dB 1415 6287 7 Locked QAM256 6 327000000 Hz 1.9 dBmV 38.8 dB 1507 6171 8 Locked QAM256 7 333000000 Hz 2.3 dBmV 38.9 dB 3249 8373 9 Locked QAM256 8 339000000 Hz 2.6 dBmV 38.7 dB 1613 6051 10 Locked QAM256 9 345000000 Hz 3.0 dBmV 38.9 dB 1529 6077 11 Locked QAM256 10 351000000 Hz 3.5 dBmV 39.0 dB 1355 6100 12 Locked QAM256 11 357000000 Hz 3.8 dBmV 38.9 dB 1550 6073 13 Locked QAM256 12 363000000 Hz 3.7 dBmV 38.8 dB 1727 6064 14 Locked QAM256 13 369000000 Hz 4.4 dBmV 39.0 dB 1613 5852 15 Locked QAM256 14 375000000 Hz 4.9 dBmV 38.9 dB 1808 7531 16 Locked QAM256 15 381000000 Hz 4.9 dBmV 38.8 dB 9366 47942 17 Locked QAM256 16 387000000 Hz 5.1 dBmV 38.8 dB 39192 204540 18 Locked QAM256 17 393000000 Hz 5.6 dBmV 38.9 dB 45863 232203 19 Locked QAM256 18 399000000 Hz 5.5 dBmV 38.7 dB 192440 564858 20 Locked QAM256 19 405000000 Hz 5.4 dBmV 38.6 dB 299665 447251 21 Locked QAM256 20 411000000 Hz 5.6 dBmV 38.1 dB 222770 536901 22 Locked QAM256 21 423000000 Hz 5.5 dBmV 38.3 dB 403686 296070 23 Locked QAM256 22 429000000 Hz 6.0 dBmV 38.4 dB 434237 206536 24 Locked QAM256 23 435000000 Hz 6.1 dBmV 38.4 dB 263879 21528 25 Locked QAM256 24 447000000 Hz 6.3 dBmV 38.3 dB 134885 16252 26 Locked QAM256 25 453000000 Hz 6.4 dBmV 38.3 dB 51204 6981 27 Locked QAM256 26 459000000 Hz 6.3 dBmV 38.2 dB 46244 9107 28 Locked QAM256 27 465000000 Hz 6.4 dBmV 38.2 dB 29690 15893 29 Locked QAM256 28 471000000 Hz 6.6 dBmV 38.1 dB 23208 15768 30 Locked QAM256 29 477000000 Hz 6.7 dBmV 38.0 dB 27739 16238 31 Locked QAM256 30 483000000 Hz 6.7 dBmV 37.9 dB 19491 15866 32 Locked QAM256 31 489000000 Hz 6.8 dBmV 37.8 dB 19123 16314 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 1 5120 Ksym/sec 17600000 Hz 45.5 dBmV 2 Locked ATDMA 2 5120 Ksym/sec 24000000 Hz 46.8 dBmV 3 Locked ATDMA 3 5120 Ksym/sec 30400000 Hz 46.8 dBmV 4 Locked ATDMA 4 5120 Ksym/sec 36800000 Hz 46.8 dBmV 5 Not Locked Unknown 0 0 0 0.0 dBmV 6 Not Locked Unknown 0 0 0 0.0 dBmV 7 Not Locked Unknown 0 0 0 0.0 dBmV 8 Not Locked Unknown 0 0 0 0.0 dBmV Downstream OFDM Channels Channel Lock Status Profile ID Channel ID Frequency Power SNR / MER Active Subcarrier
Number RangeUnerrored
CodewordsCorrectable
CodewordsUncorrectable
Codewords1 Locked 0 ,1 ,2 33 617000000 Hz 7.08 dBmV 38.9 dB 1108 ~ 2987 32206216925 24338710001 374632041 2 Not Locked 0 0 0 Hz 0 dBmV 0 dB 0 ~ 4095 0 0 0 Upstream OFDMA Channels Channel Lock Status Modulation / Profile ID Channel ID Frequency Power 1 Not Locked 0 0 0 Hz 0 dBmV 2 Not Locked 0 0 0 Hz 0 dBmV i have spectrum internet btw
What Firmware version is currently loaded?
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.
Lots of correctables and un-correctables that should be mostly zeros.
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.
Be sure your using good quality RG6 coax cable up to the modem.
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/hey thank you for the feedback! yeah i was really confused all these things have been happening within the last few months and i thought they got better 2 days ago seemed everything was nice and smooth but then they came back the next day and made everything worse again... and the thing is i called about it and they said they werent even there or it wasnt logged for them being there the second time.. and ofcourse it made it worse.
and everytime i call them and tell them about my logs and me seeing critical and errors they said they dont go by logs.. and say they cant see anything with my own modem.. i say well how am i supposed to get this information to you if you and resolve this problem if you dont go by logs? its very frustrating.. cause they always say my signal is too high here or something and they need to lower it.. witch makes no sense only thing i could think of is we used to have a business account with them and we also had to buy / pay for them to put internet out here for us and ever since my mom swaped it to residential i think thats when i noticed anything but even then im not sure.. i just am trying just about anything at this point.. i also asked if they could remove the splitter but we also have cable so i dont think i can?
but one thing i did notice was they have a orange coax going from the box also on my property to the closer box on my property but for some reason then put something inbetween that orange one to a black one.. then connected it to the splitter.. can i remove the black one and just connect the orange one to the splitter and fix it?
also i have the newest version of firmware on the modem but spectrum doesnt even use the newest version
ok it seems they connected the orange one to something also with a grounder for some reason not sure if thats needed or whatever would love to just connect the orange one to the splitter but even then would rather just get rid of the splitter but mom has cable
