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 thought I’d check here to see if this is my local problem or if this is repeatable on somebody else’s hardware.  I’m currently running Cable Firmware Version V9.01.01 on Hardware Version 1.01.  Any suggestions would be appreciated.

Thanks,

Carl

41 Replies

Replies have been turned off for this discussion
  • FURRYe38's avatar
    FURRYe38
    Guru - Experienced User

    How about the Cable Connections and standard Event logs pages? Can you access these and then also post the data here in this thread so we can take a look? 

    • carlvanwormer's avatar
      carlvanwormer
      Apprentice

      Thanks for your quick response. 

      All the other pages seem to load up without problems.  I tried the eMTA Event Log about 3 hours ago (generating the reset).  Here are the requested results of Cable Connections and standard Event log:

      Cable Connection
      Cancel Apply
      Cable Diagnostic
      Status:   Good
      Action:  
      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.
      CM Status: 
      Downstream Status: 
      Upstream Status: 
       Refresh Save Cable Diagnostic Info
       
      Advanced Information
      Frequency Start Value
      This field below allows you to modify the frequency the cable modem start with its scan during initialization and registration. Enter the new start frequency and restart the cable modem for it to take effect.
      Starting Frequency
       
      Startup Procedure
      ProcedureStatusComment
      Acquire Downstream Channel435000000 HzLocked
      Connectivity StateOKOperational
      Boot StateOKOperational
      SecurityEnabledBPI+
      IP Provisioning ModeHonor MDDIPv6 only
       
      Downstream Bonded Channels
      ChannelLock StatusModulationChannel IDFrequencyPowerSNRCorrectablesUncorrectables
      1LockedQAM2564435000000 Hz0.7 dBmV44.2 dB00
      2LockedQAM2561417000000 Hz0.5 dBmV44.2 dB00
      3LockedQAM2562423000000 Hz0.5 dBmV44.2 dB00
      4LockedQAM2563429000000 Hz0.6 dBmV44.2 dB00
      5LockedQAM2565441000000 Hz0.6 dBmV44.3 dB00
      6LockedQAM2566447000000 Hz1.0 dBmV44.3 dB00
      7LockedQAM2567453000000 Hz1.1 dBmV44.4 dB00
      8LockedQAM2568459000000 Hz1.1 dBmV44.4 dB00
      9LockedQAM2569465000000 Hz1.2 dBmV44.4 dB00
      10LockedQAM25610471000000 Hz1.3 dBmV44.4 dB00
      11LockedQAM25611477000000 Hz1.3 dBmV44.4 dB00
      12LockedQAM25612483000000 Hz1.3 dBmV44.4 dB00
      13LockedQAM25613489000000 Hz1.3 dBmV44.4 dB00
      14LockedQAM25614495000000 Hz1.3 dBmV44.4 dB00
      15LockedQAM25615501000000 Hz1.1 dBmV44.4 dB00
      16LockedQAM25616507000000 Hz1.1 dBmV44.4 dB00
      17LockedQAM25617513000000 Hz1.1 dBmV44.5 dB00
      18LockedQAM25618519000000 Hz0.9 dBmV44.4 dB00
      19LockedQAM25619525000000 Hz1.0 dBmV44.4 dB00
      20LockedQAM25620531000000 Hz0.9 dBmV44.4 dB00
      21LockedQAM25621537000000 Hz0.8 dBmV44.3 dB00
      22LockedQAM25622543000000 Hz0.6 dBmV44.2 dB00
      23LockedQAM25623549000000 Hz0.5 dBmV44.1 dB00
      24LockedQAM25624555000000 Hz0.6 dBmV44.1 dB00
      25LockedQAM25625561000000 Hz0.5 dBmV44.1 dB00
      26LockedQAM25626567000000 Hz0.6 dBmV44.1 dB00
      27LockedQAM25627573000000 Hz0.7 dBmV44.2 dB00
      28LockedQAM25628579000000 Hz0.6 dBmV44.1 dB00
      29LockedQAM25629585000000 Hz0.6 dBmV44.1 dB00
      30LockedQAM25630591000000 Hz0.6 dBmV44.0 dB00
      31LockedQAM25631597000000 Hz0.6 dBmV44.0 dB00
      32LockedQAM25632603000000 Hz0.6 dBmV44.0 dB00
       
      Upstream Bonded Channels
      ChannelLock StatusUS Channel TypeChannel IDSymbol RateFrequencyPower
      1LockedATDMA205120 Ksym/sec35600000 Hz47.8 dBmV
      2LockedATDMA185120 Ksym/sec22800000 Hz46.3 dBmV
      3LockedATDMA195120 Ksym/sec29200000 Hz47.0 dBmV
      4LockedATDMA175120 Ksym/sec16400000 Hz45.3 dBmV
      5Not LockedUnknown0000.0 dBmV
      6Not LockedUnknown0000.0 dBmV
      7Not LockedUnknown0000.0 dBmV
      8Not LockedUnknown0000.0 dBmV
       
      Downstream OFDM Channels
      ChannelLock StatusProfile IDChannel IDFrequencyPowerSNR / MERActive Subcarrier
      Number Range
      Unerrored
      Codewords
      Correctable
      Codewords
      Uncorrectable
      Codewords
      1Locked0 ,1 ,2 ,3193957000000 Hz-2.62 dBmV42.0 dB148 ~ 3947186996469461084070
      2Not Locked000 Hz0 dBmV0 dB0 ~ 4095000
       
      Upstream OFDMA Channels
      ChannelLock StatusModulation / Profile IDChannel IDFrequencyPower
      1Not Locked000 Hz0 dBmV
      2Not Locked000 Hz0 dBmV
       
      Current System Time:Wed Mar 20 12:29:38 2024
      System Up Time:03:33:43

       

       

      Event Log
       
      Clear Log Refresh Export
       
      TimePriorityDescription
      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;
      Wed Mar 20 12:12:20 2024(Critical (3))Started Unicast Maintenance Ranging - No Response received - T3 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 12:12:20 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 08:57:06 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 08:56:59 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 08:56:53 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 08:56:44 2024(Notice (6))Honoring MDD; IP provisioning mode = IPv6
      • FURRYe38's avatar
        FURRYe38
        Guru - Experienced User

        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? 

  • I am on Hardware Version 1.01 Cable Firmware Version V2.01.03.  And trying to open the eMTA event log causes the modem to reboot every time.  This has persisted after modem reinitialization.  Glad it is not just me...

    • carlvanwormer's avatar
      carlvanwormer
      Apprentice

      This is great to hear!  I will try to contact Netgear again to see if I can get access to more information about this condition.  I'm past the 90 days of free tech support, but I'll see if I can weasel my way into support without paying the $60 they asked for last time.

      Thanks,
      Carl

       

      • carlvanwormer's avatar
        carlvanwormer
        Apprentice

        I called Netgear again and was able to gather more "free" information from the tech (who really wanted me to buy the additional tech support subscription).  He wanted to prompt me through a reset and I told him I had already used the web interface reset, the power-cycle reset, and the hold-reset-button-down-for-7-seconds reset (from the online documents.  He said I needed to do a 90-second shock reset, consisting of holding down the reset button with power-on for 30 seconds,  continue holding down the reset button with power-off for 30 seconds, continue holding down the reset button for 30 more seconds while reapplying power.  After this process, I should use the local user interface to set up the modem (no details given) and then contact my ISP to have the current software downloaded to me again.  I'm not home right now, so I'll try this process when I get home tonight.

  • I can confirm that this happens on my modem as well. Viewing the event log sometimes causes the modem to reboot.

    • Miked2's avatar
      Miked2
      Apprentice

      Me as well!

       

      Is there some way to report issues to netgear, without paying for support?

    • carlvanwormer's avatar
      carlvanwormer
      Apprentice

      When my system "always" reset when clicking on the eMTA Event Log button, I tried a direct connect to the modem from my laptop.  That connection gave me the eMTA Event Log and after that, connection of my main computer through the router was able to load the eMTA Event Log without resets.  After performing a "shock reset", the software had changed back to the V2.01.01 version and my eMTA Event Log requests started doing the resets again.  My questions to you are "do you like to play" and "are you feeling lucky?"

       

      Later,
      Carl

       

      • Miked2's avatar
        Miked2
        Apprentice

        I have never felt lucky with NetGear products.  I have had many and they always seem fluky.  I bought this because for voice and high speed comcast data, this was the only choice, then it fell off the compatibility list 😞