Frequent Visitor
•
7 Messages
Modem resetting throughout day with "Resetting the cable modem due to docsDevResetNow" in event log
There was an issue on the network this morning that caused our internet connection to drop out. This affected other folks in the neighborhood also. In support chat I was told that static or some glitch may have caused it. Seriously? While internet has come back for other affected parties, my modem (Netgear CM2000) continues to experience resets with the following message occurring "(Critical (3)) Resetting the cable modem due to docsDevResetNow" What's going on now? I'll post the event log and connection status below. Could someone that's not going to tell me "static or a glitch caused your issue" please assist? Thanks
## event log 20210611
Acquire Downstream Channel 489000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 17 489000000 Hz 9.0 dBmV 40.0 dB 4 0
2 Locked QAM256 14 471000000 Hz 9.9 dBmV 40.7 dB 1 0
3 Locked QAM256 15 477000000 Hz 9.2 dBmV 39.9 dB 5 0
4 Locked QAM256 16 483000000 Hz 9.6 dBmV 40.7 dB 2 0
5 Locked QAM256 18 495000000 Hz 9.1 dBmV 40.2 dB 5 0
6 Locked QAM256 19 507000000 Hz 8.3 dBmV 39.8 dB 5 0
7 Locked QAM256 20 513000000 Hz 8.5 dBmV 40.1 dB 2 0
8 Locked QAM256 21 519000000 Hz 7.4 dBmV 39.2 dB 7 0
9 Locked QAM256 22 525000000 Hz 8.5 dBmV 39.9 dB 4 0
10 Locked QAM256 23 531000000 Hz 7.8 dBmV 39.2 dB 8 0
11 Locked QAM256 24 537000000 Hz 8.0 dBmV 39.4 dB 9 0
12 Locked QAM256 25 543000000 Hz 7.8 dBmV 39.3 dB 4 0
13 Locked QAM256 26 549000000 Hz 7.5 dBmV 38.9 dB 22 0
14 Locked QAM256 27 555000000 Hz 7.8 dBmV 39.3 dB 6 0
15 Locked QAM256 28 561000000 Hz 7.1 dBmV 38.5 dB 36 0
16 Locked QAM256 30 567000000 Hz 7.7 dBmV 39.0 dB 8 0
17 Locked QAM256 31 573000000 Hz 7.3 dBmV 38.6 dB 16 0
18 Locked QAM256 32 579000000 Hz 6.9 dBmV 38.3 dB 16 0
19 Locked QAM256 33 585000000 Hz 7.3 dBmV 38.7 dB 11 0
20 Locked QAM256 34 591000000 Hz 6.3 dBmV 38.0 dB 38 0
21 Locked QAM256 35 597000000 Hz 7.1 dBmV 38.6 dB 11 0
22 Locked QAM256 36 603000000 Hz 6.2 dBmV 37.8 dB 39 0
23 Locked QAM256 37 609000000 Hz 6.5 dBmV 38.3 dB 14 0
24 Locked QAM256 38 615000000 Hz 5.9 dBmV 37.8 dB 19 0
25 Locked QAM256 39 621000000 Hz 5.9 dBmV 37.6 dB 35 0
26 Locked QAM256 40 627000000 Hz 6.0 dBmV 37.9 dB 22 0
27 Locked QAM256 41 633000000 Hz 5.6 dBmV 37.4 dB 54 0
28 Locked QAM256 42 639000000 Hz 6.4 dBmV 38.0 dB 19 0
29 Locked QAM256 43 645000000 Hz 5.9 dBmV 37.4 dB 67 0
30 Locked QAM256 44 651000000 Hz 6.0 dBmV 37.5 dB 51 0
31 Locked QAM256 45 657000000 Hz 5.8 dBmV 37.3 dB 50 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 85 5120 36500000 Hz 39.8 dBmV
2 Locked ATDMA 86 5120 30100000 Hz 40.0 dBmV
3 Locked ATDMA 87 5120 23700000 Hz 40.0 dBmV
4 Locked ATDMA 88 5120 17300000 Hz 40.0 dBmV
5 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 0 Hz 0.0 dBmV
Downstream OFDM Channels
Channel Lock
Status Modulation /
Profile ID Channel
ID Frequency Power SNR / MER Active Subcarrier Number Range Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked 0 ,1 ,2 ,3 29 690000000 Hz 4.9 dBmV 35.9 dB 1108 ~ 2987 788335 787009 0
##################
Time Priority Description
Fri Jun 11 13:14:26 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 13:14:22 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-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; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 13:13:16 2021 (Critical (3)) Resetting the cable modem due to docsDevResetNow
Fri Jun 11 12:08:18 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 12:08:13 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-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; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 12:07:08 2021 (Critical (3)) Resetting the cable modem due to docsDevResetNow
Fri Jun 11 11:03:15 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 11:03:11 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:59:46 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:59:41 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-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; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:58:35 2021 (Critical (3)) Resetting the cable modem due to docsDevResetNow
Fri Jun 11 10:50:31 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:50:26 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-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; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:49:19 2021 (Critical (3)) Resetting the cable modem due to docsDevResetNow
Fri Jun 11 10:42:04 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:41:59 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-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; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:40:52 2021 (Critical (3)) Resetting the cable modem due to docsDevResetNow
Fri Jun 11 10:19:36 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:19:32 2021 (Notice (6)) TLV-11 - unrecognized OID; xCM-QOS=1.1;CM-VER=3.1;
Time Not Established (Notice (6)) Honoring MDD; IP provisioning mode = IPv6
Time Not Established (Critical (3)) SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;; xCM-QOS=1.1;CM-VER=3.1;
Fri Jun 11 10:18:27 2021 (Critical (3)) Resetting the cable modem due to docsDevResetNow
Fri Jun 11 10:16:03 2021 (Notice (6)) DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.; xCM-QOS=1.1;CM-VER=3.1;




user_JosephC
Problem Solver
•
369 Messages
5 years ago
Hello and Happy Sunday, XimXfin! I hope you’re having a great weekend so far! I also appreciate you taking a moment out of your day to reach out to us on our Community Forums! You’ve reached the best place and perfect person to help with virtually all of your account needs!
Going forward, I sincerely appreciate the time you've taken to provide all these details for us and I do apologize greatly for the connection issues you're having with your services! I definitely want to take a closer look from the backend and utilize my tools to see what could be the main cause. I really appreciate all your continued patience!
To get the ball rolling on this process, please send us a private chat message by following the process that our very own Communities Expert, BruceW so graciously outlined here:
Once you have started a chat message, please provide your name and service address as it appears on your monthly billing statements. Thanks again for both your time and patience!
0
0
EG
Expert
•
118.4K Messages
5 years ago
@XimXfin @ComcastJoey
Please post any possible solutions for the issue here in the open forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.
0