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

Forum Discussion

carlvanwormer's avatar
carlvanwormer
Apprentice
Mar 20, 2024

Trying to view eMTA Event Log causes reset on my CM2050V modem

While logged in to the local web interface to my Nighthawk CM2050V modem, selecting the Advanced eMTA Event Log causes a modem reset after about 10 seconds.  I don’t think this is normal, but I thoug...
Firmware
Troubleshooting
FURRYe38's avatar
FURRYe38
Guru - Experienced User
Mar 20, 2024

Power levels are good and no correctables or un-currectables. 

 

I see some Criticals the the ISP should look into. 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.

 

Not sure about the Advanced EMTA events logs. Wondering if maybe that is not supported with is modem and the ISP services. 

 

Something to try, disconnect the modem from the ISP coax line. Then try this advanced EMTA log selection to see if the modem reboots or does something different...Reconnect the ISP coax line after checking this. 

 

Anything connected to the phone ports? 

What is the brand and model# of the wifi router connected to the modem?


Does this happen with a different browser? 

carlvanwormer's avatar
carlvanwormer
Apprentice
Mar 20, 2024

When I disconnected the cable (a couple of times), my connectivity to the modem stopped.  Reconnecting the cable allowed me to log in to the local interface again.  The lights on the modem didn't indicate the reboot sequence (all black, then top to bottom lights coming on over 2 minutes).  I do have 1 phone connected to the POTS jacks.  Here is the log of a pair of cable disconnects (starting at 13:12:53)

I'm hoping somebody with at CM2050V can try to read the eMTA logs to see if it is a system problem or a problem with my unit.  Since I'm past the 90 days tech-support policy (but within the 1 year hardware warranty), I'm hoping I don't need to pay $60 to talk with NG tech support.

Thanks,

Carl

 

 

Event Log
 
Clear Log Refresh Export
 
TimePriorityDescription
Wed Mar 20 13:18:21 2024(Critical (3))UCD invalid or channel unusable;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:18:14 2024(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:18:13 2024(Notice (6))TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:18:05 2024(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Wed Mar 20 13:18:01 2024(Critical (3))UCD invalid or channel unusable;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:55 2024(Warning (5))ToD request sent - No Response received;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:45 2024(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Wed Mar 20 13:17:39 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:19 2024(Warning (5))ToD request sent - No Response received;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:18 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:18 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:18 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:17 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:17 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:16 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:14 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:17:14 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:16:27 2024(Warning (5))MDD message timeout;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:16:26 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:14:54 2024(Critical (3))UCD invalid or channel unusable;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:14:45 2024(Notice (6))DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:14:44 2024(Notice (6))TLV-11 - unrecognized OID;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:14:36 2024(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Wed Mar 20 13:14:32 2024(Critical (3))UCD invalid or channel unusable;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:14:25 2024(Warning (5))ToD request sent - No Response received;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:14:16 2024(Notice (6))Honoring MDD; IP provisioning mode = IPv6
Wed Mar 20 13:14:08 2024(Warning (5))Lost MDD Timeout;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:58 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:49 2024(Warning (5))ToD request sent - No Response received;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:48 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:48 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:44 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:44 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:36 2024(Critical (3))Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:13:36 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:12:59 2024(Warning (5))MDD message timeout;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:12:59 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:12:53 2024(Warning (5))MDD message timeout;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 13:12:53 2024(Critical (3))SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
Wed Mar 20 12:12:28 2024(Notice (6))CM-STATUS message sent. Event Type Code: 4; Chan ID: 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=6c:cd:d6:ce:3d:24;CMTS-MAC=00:90:f0:7e:06:00;CM-QOS=1.1;CM-VER=3.1;
  • carlvanwormer's avatar
    carlvanwormer
    Apprentice
    Mar 20, 2024

    Oops, I forgot you asked about my router.  It is a Ubiquity Edge router, but I can't imagine that it would be causing my reboot problem when I perform the eMTA read request.

    Thanks,
    Carl

     

  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User
    Mar 20, 2024

    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.

    • carlvanwormer's avatar
      carlvanwormer
      Apprentice
      Mar 20, 2024

      OK, I'll contact Xfinity to see if I can get their attention.  I'll set aside some time tonight or tomorrow and find some nice relaxing music to calm my soul as I go through that process.

      Thanks,
      Carl

       

      • Kitsap's avatar
        Kitsap
        Master
        Mar 20, 2024

        In your original post you indicate you are running firmware version V9.01.01.  Several months ago that firmware was pulled by Xfinity and reverted back to version V2.01.03.

         

        I am running V2.01.03 on my CM2050V and have no problems with the eMTA event log.

         

        A reset on your modem might trigger an update on your firmware.

         

        You will get a much better response from Xfinity by posting over on the Reddit Comcast_Xfinity sub forum here:

         

        https://www.reddit.com/r/Comcast_Xfinity/wiki/knowledgebase/next-generation-internet/