NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
CM1000v2 Intermittent issue
I have contacted Mediacom (My ISP) and they claim the problem is with the modem.
I am up-to-date on the firmware.
Anyone know how I can resolve this issue?
| Time | Priority | Description |
| 2022-03-07, 11:23:05 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-07, 11:22:40 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-07, 04:35:44 | Error (4) | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-07, 04:23:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-07, 04:23:14 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-06, 04:12:32 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-06, 04:12:08 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 11:24:28 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 11:24:03 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 07:08:38 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 07:08:14 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:27:42 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:27:17 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:19:09 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:18:45 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:18:19 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:17:55 | Notice (6) | CM-STATUS message sent. Event Type Code: 16; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
| 2022-03-05, 03:16:24 | Notice (6) | CM-STATUS message sent. Event Type Code: 24; Chan ID: 200; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=bc:a5:11:8d:39:5c;CMTS-MAC=00:17:10:91:72:3f;CM-QOS=1.1;CM-VER=3.1; |
9 Replies
Please post a copy and paste of the modems connection status page.
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.
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?article=24311
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html
https://highspeed.tips/docsis-events/You didn't really give us a very good description of what your actual issues. Just that you think its the line and media come thinks its the modem.
1. what actual issue (in detail) are you having?
2. does it impact both wired and wireless devices?
3. what router do you have connected to the modem?
4. do you have a screen snip of the cable connections page?
5. what makes you think its the line and mediacom think its the modem? (what testing has been done)
