Community Forum

Constant disconnects - Event log and Power/SNR logs

New Poster

Constant disconnects - Event log and Power/SNR logs

Hi

Two weeks ago I upgraded to a TP Link Router and a Netgear CM 1000 DOCSIS 3.1 modem.  Since the upgrade the speed has been significantly better, but now I am getting frequent disconnects.  The internet just drops several times per day.  Restarting the modem solves the issue after a few minutes, but this is never something that happened with the Netgear CM 700 modem. 

I looked at the cable modem event log and SNR/Power log.  I don't know really what I am looking at, but there are a lot of Critical errors and the db range for is beyond the +/- 7 db that looks like it is the spec for a Netgear CM1000. 

  Description
2019-02-15, 16:51:15 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 16:51:13 Warning (5) Dynamic Range Window violation
2019-02-15, 16:51:13 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:32:33 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:32:06 Notice (6) Honoring MDD; IP provisioning mode = IPv6
2019-02-15, 11:31:51 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=18;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:49 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=1;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:48 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:43 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1:68;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:34 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=14;CMTS-MAC=00;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:33 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:31 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=1;CMTS-MAC=006;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:31:30 Critical (3) Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=14;CMTS-MAC=00:6;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:53 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:43 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1:68;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:43 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=14;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:33 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:30 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=1:1a:68;CMTS-MAC=00:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:23 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=14a:68;CMTS-MAC=00:08:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:14 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:1a:68;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:13 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=14:;CMTS-MAC=0076;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:27:04 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=168;CMTS-MAC=00:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:43 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=14;CMTS-MAC8:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:33 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=14:;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:32 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=148;CMTS-MAC=00:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:24 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=148;CMTS-MAC=6;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:23 Warning (5) Dynamic Range Window violation
2019-02-15, 11:26:23 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=14:8;CMTS-MAC=6;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:23 Warning (5) Dynamic Range Window violation
2019-02-15, 11:26:23 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=148;CMTS-MAC=08:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:23 Warning (5) Dynamic Range Window violation
2019-02-15, 11:26:23 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=14:;CMTS-MAC=06;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:23 Warning (5) Dynamic Range Window violation
2019-02-15, 11:26:23 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=148;CMTS-MAC=:76;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:22 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=14:8;CMTS-MAC=076;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:26:22 Warning (5) Dynamic Range Window violation
2019-02-15, 11:26:22 Warning (5) RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=18;CMTS-MAC=:;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:25:12 Critical (3) No Maintenance Broadcasts for Ranging opportunities received - T2 time-out;CM-MAC=1;CMTS-MAC=0;CM-QOS=1.1;CM-VER=3.1;
2019-02-15, 11:25:09 Warning (5) Dynamic Range Window violation
<tabindex=-1>
Channel Lock Status Modulation Channel ID Frequency Power SNR / MER Unerrored Codewords Correctable Codewords Uncorrectable Codewords
1 Locked QAM256 38 621000000 Hz -0.4 dBmV 44.3 dB 722534560 0 0
2 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
3 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0
4 Locked QAM256 19 507000000 Hz -21.2 dBmV 29.5 dB 720343688 11685 31
5 Locked QAM256 20 513000000 Hz -12.4 dBmV 38.4 dB 720359960 22 12
6 Locked QAM256 21 519000000 Hz -6.6 dBmV 42.9 dB 720364613 0 0
7 Locked QAM256 22 525000000 Hz -3.7 dBmV 44.2 dB 720368836 22 0
8 Locked QAM256 23 531000000 Hz -2.2 dBmV 44.6 dB 720373560 30 0
9 Locked QAM256 24 537000000 Hz -1.5 dBmV 44.9 dB 637737630 28 4
10 Locked QAM256 25 543000000 Hz -1.2 dBmV 44.7 dB 637745195 0 0
11 Locked QAM256 26 549000000 Hz -0.9 dBmV 45.0 dB 637752794 0 0
12 Locked QAM256 27 555000000 Hz -0.6 dBmV 44.9 dB 637759664 0 0
13 Locked QAM256 28 561000000 Hz -0.2 dBmV 45.2 dB 637767127 0 0
14 Locked QAM256 29 567000000 Hz -0.2 dBmV 45.0 dB 637774298 0 0
15 Locked QAM256 30 573000000 Hz -0.3 dBmV 45.1 dB 637781942 0 0
16 Locked QAM256 31 579000000 Hz -0.1 dBmV 44.8 dB 637788996 0 0
17 Locked QAM256 32 585000000 Hz -0.2 dBmV 44.9 dB 637798656 0 0
18 Locked QAM256 33 591000000 Hz -0.3 dBmV 44.7 dB 637806120 0 0
19 Locked QAM256 34 597000000 Hz -0.2 dBmV 44.4 dB 637813476 0 0
20 Locked QAM256 35 603000000 Hz 0.0 dBmV 44.6 dB 637820542 0 0
21 Locked QAM256 36 609000000 Hz -0.3 dBmV 44.6 dB 637827959 0 0
22 Locked QAM256 37 615000000 Hz -0.5 dBmV 44.5 dB 637835552 0 0
23 Locked QAM256 39 627000000 Hz -0.4 dBmV 44.4 dB 637843489 0 0
24 Locked QAM256 40 633000000 Hz -0.5 dBmV 44.1 dB 637850108 0 0
25 Locked QAM256 41 639000000 Hz -0.6 dBmV 44.3 dB 637857548 0 0
26 Locked QAM256 42 645000000 Hz -0.4 dBmV 44.5 dB 637864591 0 0
27 Locked QAM256 43 651000000 Hz -0.6 dBmV 44.1 dB 637872362 0 0
28 Locked QAM256 44 657000000 Hz -0.8 dBmV 44.4 dB 637879925 0 0
29 Locked QAM256 45 663000000 Hz -1.1 dBmV 44.2 dB 637887590 0 0
30 Locked QAM256 46 669000000 Hz -0.9 dBmV 44.3 dB 637887803 0 0
31 Locked QAM256 47 675000000 Hz -1.2 dBmV 43.6 dB 637889678 0 0
32 Not Locked Unknown 0 0 Hz 0.0 dBmV 0.0 dB 0 0 0

<tabindex=-1>Upstream Bonded Channels (Partial Service)
Channel Lock Status Modulation Channel ID Frequency Power
1 Locked ATDMA 33 36500000 Hz 47.3 dBmV
2 Locked ATDMA 34 30100000 Hz 55.3 dBmV
3 Locked ATDMA 35 23700000 Hz 56.8 dBmV
4 Locked ATDMA 36 17300000 Hz 59.0 dBmV
5 Not Locked Unknown 0 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Hz 0.0 dBmV

<tabindex=-1>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, 255 48 722000000 Hz -2.2 dBmV 36.3 dB 1348 ~ 2747 1302072645 1248045287 0
2 Not Locked 0, 255 0 0 Hz -50.6 dBmV 0.0 dB 0 ~ 4095 0 0 0

<tabindex=-1>Upstream OFDMA Channels
Channel Lock Status Modulation / Profile ID Channel ID Frequency Power
1 Not Locked Unknown 0 0 Hz 0 dBmV
2 Not Locked Unknown 0 0 Hz 0 dBm
Diamond Problem Solver

Re: Constant disconnects - Event log and Power/SNR logs

Part of the problem would be your upstream levels. 3 out of 4 channels are way too high and out of spec. Unless you have 2 or 3 splitters that you can remove/reduce, to see if it helps, you’ll need a tech out to troubleshoot further.

I am a Retired Official Comcast Employee
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark a post as the Best Answer!
7B6E7951-54C8-472A-B916-3453932D6721.jpeg
Expert

Re: Constant disconnects - Event log and Power/SNR logs

FWIW, some of the downstream channels are borked as well !!


I am not a Comcast Employee.
I am a Customer Expert volunteering my time to help other customers here in the Forums.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: Constant disconnects - Event log and Power/SNR logs

Hi there, SuperMegaServer. Thanks for posting, welcome to the community. After you check your connections and see if there are any simple modifications you can make and if you continue to see the signal issue being present, please send me a private message and I will get that appointment scheduled for you.

 

To send a private message, please click my name "ComcastMorgan" then select "Send a Message" on the right side.
 

Thanks!

 

 


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!
Official Employee

Re: Constant disconnects - Event log and Power/SNR logs

Hi, SuperMegaServer. I never heard back from you on this. I will be completing this interaction. If you end up needing further support with it, please send me that PM. Thank you.


I am an Official Comcast Employee.
Official Employees are from multiple teams within Comcast: CARE, Product, Leadership. We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Mark the post as Best Answer!