NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.

Forum Discussion

Lexxfyre's avatar
Lexxfyre
Aspirant
Oct 10, 2022

Cm2050v disconnects from isp

My modem seems to be dropping the isp overnight. Has been happening every other night for about a week. I didn’t see any firmware updates. And all the cables attached are brand new. The router I have ...
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Oct 10, 2022

Please post a copy and paste of the modems connection status and event log page.
https://kb.netgear.com/30007/How-do-I-obtain-the-cable-connection-information-from-a-NETGEAR-cable-modem-modem-router
https://kb.netgear.com/30008/How-do-I-view-or-clear-the-event-logs-on-my-NETGEAR-cable-modem-or-modem-router

 

Be sure your using a good quality LAN cable between the modem and router. CAT6 or CAT6A STP is recommended. 

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
https://www.duckware.com/tech/solving-intermittent-cable-modem-issues.html

Lexxfyre's avatar
Lexxfyre
Aspirant
Oct 20, 2022

Event Log

Thu Oct 20 16:05:26 2022(Notice (6))CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 16:05:12 2022(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 16:05:08 2022(Notice (6))TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;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=08:36:c9:3b:76:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 15:57:08 2022(Notice (6))CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 15:56:52 2022(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 15:56:48 2022(Notice (6))TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;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=08:36:c9:3b:76:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 13:00:55 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 13:00:45 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:51:27 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:50:59 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:50:45 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:43:06 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:40:31 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:40:19 2022(Notice (6))CM-STATUS message sent. Event Type Code: 5; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:40:03 2022(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:39:58 2022(Notice (6))TLV-11 - unrecognized OID;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Time Not Established(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Time Not Established(Critical (3))No Ranging Response received - T3 time-out;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;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=08:36:c9:3b:76:40;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:38:25 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:38:10 2022(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:51 2022(Notice (6))CM-STATUS message sent. Event Type Code: 22; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:34 2022(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:28 2022(Notice (6))CM-STATUS message sent. Event Type Code: 23; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:16 2022(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:15 2022(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:12 2022(Warning (5))MDD message timeout;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:37:12 2022(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:35:05 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:34:39 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:34:25 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:33:43 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:31:14 2022(Notice (6))CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
Thu Oct 20 12:30:13 2022(Notice (6))CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=08:36:c9:3b:76:40;CMTS-MAC=00:01:5c:82:be:4e;CM-QOS=1.1;CM-VER=3.1;
  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Oct 20, 2022

    Power looks ok but some channels are not the same as the others. 
    You have lots of criticals that the ISP needs to review and resolve. 

     

    • Lexxfyre's avatar
      Lexxfyre
      Aspirant
      Oct 20, 2022

      So action is needed from the ISP to resolve? Is there anything I should mention to them specifically to get help with this issue?

      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User
        Oct 20, 2022

        Other than what I first posted about, they'll need to take a look and figure out the criticals.