NETGEAR is aware of a growing number of phone and online scams. To learn how to stay safe click here.
Forum Discussion
carlvanwormer
Mar 20, 2024Apprentice
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
- FURRYe38Guru - 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?
- carlvanwormerApprentice
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 ConnectionCancel ApplyCable 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 Procedure Status Comment Acquire Downstream Channel 435000000 Hz Locked Connectivity State OK Operational Boot State OK Operational Security Enabled BPI+ IP Provisioning Mode Honor MDD IPv6 only Downstream Bonded Channels Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables 1 Locked QAM256 4 435000000 Hz 0.7 dBmV 44.2 dB 0 0 2 Locked QAM256 1 417000000 Hz 0.5 dBmV 44.2 dB 0 0 3 Locked QAM256 2 423000000 Hz 0.5 dBmV 44.2 dB 0 0 4 Locked QAM256 3 429000000 Hz 0.6 dBmV 44.2 dB 0 0 5 Locked QAM256 5 441000000 Hz 0.6 dBmV 44.3 dB 0 0 6 Locked QAM256 6 447000000 Hz 1.0 dBmV 44.3 dB 0 0 7 Locked QAM256 7 453000000 Hz 1.1 dBmV 44.4 dB 0 0 8 Locked QAM256 8 459000000 Hz 1.1 dBmV 44.4 dB 0 0 9 Locked QAM256 9 465000000 Hz 1.2 dBmV 44.4 dB 0 0 10 Locked QAM256 10 471000000 Hz 1.3 dBmV 44.4 dB 0 0 11 Locked QAM256 11 477000000 Hz 1.3 dBmV 44.4 dB 0 0 12 Locked QAM256 12 483000000 Hz 1.3 dBmV 44.4 dB 0 0 13 Locked QAM256 13 489000000 Hz 1.3 dBmV 44.4 dB 0 0 14 Locked QAM256 14 495000000 Hz 1.3 dBmV 44.4 dB 0 0 15 Locked QAM256 15 501000000 Hz 1.1 dBmV 44.4 dB 0 0 16 Locked QAM256 16 507000000 Hz 1.1 dBmV 44.4 dB 0 0 17 Locked QAM256 17 513000000 Hz 1.1 dBmV 44.5 dB 0 0 18 Locked QAM256 18 519000000 Hz 0.9 dBmV 44.4 dB 0 0 19 Locked QAM256 19 525000000 Hz 1.0 dBmV 44.4 dB 0 0 20 Locked QAM256 20 531000000 Hz 0.9 dBmV 44.4 dB 0 0 21 Locked QAM256 21 537000000 Hz 0.8 dBmV 44.3 dB 0 0 22 Locked QAM256 22 543000000 Hz 0.6 dBmV 44.2 dB 0 0 23 Locked QAM256 23 549000000 Hz 0.5 dBmV 44.1 dB 0 0 24 Locked QAM256 24 555000000 Hz 0.6 dBmV 44.1 dB 0 0 25 Locked QAM256 25 561000000 Hz 0.5 dBmV 44.1 dB 0 0 26 Locked QAM256 26 567000000 Hz 0.6 dBmV 44.1 dB 0 0 27 Locked QAM256 27 573000000 Hz 0.7 dBmV 44.2 dB 0 0 28 Locked QAM256 28 579000000 Hz 0.6 dBmV 44.1 dB 0 0 29 Locked QAM256 29 585000000 Hz 0.6 dBmV 44.1 dB 0 0 30 Locked QAM256 30 591000000 Hz 0.6 dBmV 44.0 dB 0 0 31 Locked QAM256 31 597000000 Hz 0.6 dBmV 44.0 dB 0 0 32 Locked QAM256 32 603000000 Hz 0.6 dBmV 44.0 dB 0 0 Upstream Bonded Channels Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power 1 Locked ATDMA 20 5120 Ksym/sec 35600000 Hz 47.8 dBmV 2 Locked ATDMA 18 5120 Ksym/sec 22800000 Hz 46.3 dBmV 3 Locked ATDMA 19 5120 Ksym/sec 29200000 Hz 47.0 dBmV 4 Locked ATDMA 17 5120 Ksym/sec 16400000 Hz 45.3 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 ,3 193 957000000 Hz -2.62 dBmV 42.0 dB 148 ~ 3947 186996469 46108407 0 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 Current System Time:Wed Mar 20 12:29:38 2024 System Up Time:03:33:43 Event LogClear Log Refresh Export Time Priority Description 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 - FURRYe38Guru - 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?
- Miked2Apprentice
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...
- carlvanwormerApprentice
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- carlvanwormerApprentice
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.
- patreeekTutor
I can confirm that this happens on my modem as well. Viewing the event log sometimes causes the modem to reboot.
- Miked2Apprentice
Me as well!
Is there some way to report issues to netgear, without paying for support?
- carlvanwormerApprentice
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- Miked2Apprentice
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 😞