U

Sunday, August 6th, 2023 4:32 PM

Closed

CM1200 Random disconnects, plenty of uncorrectables as well

Hello, been seeing lots of uncorrectables on my home network. I was previously using the xfinity modem/router combo, but I couldn’t analyze the logs, so I got a brand new modem and router. I have already had a tech to replace lines in the house as well, worried it’s the lines going to the house. This is a huge issue because I drop off or meetings for work as well. Logs and stats below.

Cable Connection
Frequency start Value
Starting Frequency
Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 627000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Security Enabled BPI+
IP Provisioning Mode Honor MDD honorMdd(4)
 
Downstream Bonded Channels
Channel Lock Status Modulation Channel ID Frequency Power SNR Correctables Uncorrectables
1 Locked QAM256 37 627000000 Hz -0.5 dBmV 42 dB 46430 9693
2 Locked QAM256 13 477000000 Hz 0.5 dBmV 43.2 dB 173479 29477
3 Locked QAM256 14 483000000 Hz 0.4 dBmV 43.2 dB 171183 28546
4 Locked QAM256 15 489000000 Hz 0.6 dBmV 43.1 dB 161224 26866
5 Locked QAM256 16 495000000 Hz 0.5 dBmV 43.1 dB 241639 40117
6 Locked QAM256 17 507000000 Hz 0.2 dBmV 43 dB 138825 22077
7 Locked QAM256 18 513000000 Hz 0.5 dBmV 43 dB 137115 21470
8 Locked QAM256 19 519000000 Hz 0.4 dBmV 42.9 dB 129590 20242
9 Locked QAM256 20 525000000 Hz 0.3 dBmV 42.9 dB 124472 19262
10 Locked QAM256 21 531000000 Hz 0.3 dBmV 42.8 dB 125162 18768
11 Locked QAM256 22 537000000 Hz 0.4 dBmV 42.8 dB 115660 17674
12 Locked QAM256 23 543000000 Hz 0.3 dBmV 42.8 dB 113290 16885
13 Locked QAM256 24 549000000 Hz 0.4 dBmV 42.7 dB 103827 16213
14 Locked QAM256 25 555000000 Hz 0.6 dBmV 42.8 dB 98921 15620
15 Locked QAM256 26 561000000 Hz 0.7 dBmV 42.7 dB 95857 15250
16 Locked QAM256 27 567000000 Hz 0.4 dBmV 42.5 dB 90601 14750
17 Locked QAM256 28 573000000 Hz 0.5 dBmV 42.6 dB 84273 13522
18 Locked QAM256 29 579000000 Hz 0.6 dBmV 42.6 dB 73756 12569
19 Locked QAM256 30 585000000 Hz 0.5 dBmV 42.6 dB 67541 11900
20 Locked QAM256 31 591000000 Hz 0.2 dBmV 42.5 dB 62306 11704
21 Locked QAM256 32 597000000 Hz 0.3 dBmV 42.5 dB 59025 11051
22 Locked QAM256 33 603000000 Hz 0.4 dBmV 42.6 dB 54333 10876
23 Locked QAM256 34 609000000 Hz -0.1 dBmV 42.3 dB 56336 10633
24 Locked QAM256 35 615000000 Hz -0.8 dBmV 42.1 dB 55236 10541
25 Locked QAM256 36 621000000 Hz -0.8 dBmV 42 dB 51952 10674
26 Locked QAM256 38 633000000 Hz -0.9 dBmV 41.9 dB 44463 9380
27 Locked QAM256 39 639000000 Hz -1 dBmV 41.5 dB 43668 9528
28 Locked QAM256 40 645000000 Hz -0.9 dBmV 41.7 dB 41396 8940
29 Locked QAM256 41 651000000 Hz -1.1 dBmV 41.7 dB 38518 9008
30 Locked QAM256 42 657000000 Hz -1.6 dBmV 41.7 dB 38788 8961
31 Locked QAM256 43 663000000 Hz -1.6 dBmV 41.7 dB 35094 8559
32 Locked QAM256 44 669000000 Hz -1.4 dBmV 41.8 dB 31483 8033
 
Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35600000 Hz 50 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 50 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 49.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16400000 Hz 48.8 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 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 159 690000000 Hz -0.5 dBmV 42.2 dB 1126 ~ 2969 10901811499 2132547411 1423
2 Not Locked 0 0 0 Hz 0 dBmV 0.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

Event Logs:

 
Time Priority Description
Sun Aug 06 10:03:52 2023 Warning (5) Dynamic Range Window violation
Sun Aug 06 10:03:52 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 08:57:18 2023 Warning (5) Dynamic Range Window violation
Sun Aug 06 08:57:18 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTD;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 08:53:38 2023 Warning (5) Dynamic Range Window violation
Sun Aug 06 08:53:38 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 08:52:48 2023 Critical (3) Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 05:22:39 2023 Warning (5) Dynamic Range Window violation
Sun Aug 06 05:22:39 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 05:22:39 2023 Warning (5) Dynamic Range Window violation
Sun Aug 06 05:22:39 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 01:36:42 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 01:36:09 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 01:34:36 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sun Aug 06 01:34:07 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 19:21:22 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 19:20:55 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 19:12:44 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 19:12:11 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 19:10:17 2023 Notice (6) CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 19:09:05 2023 Notice (6) CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 18:35:40 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 18:35:40 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 18:35:40 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 18:35:40 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 17:07:49 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 17:07:49 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 17:07:49 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 17:07:49 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 16:57:30 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 16:57:30 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 15:46:37 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 15:46:37 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 15:16:00 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 15:16:00 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 13:36:29 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 13:36:29 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 13:36:29 2023 Warning (5) Dynamic Range Window violation
Sat Aug 05 13:36:29 2023 Warning (5) RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTEDCMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;
Sat Aug 05 13:23:10 2023 Warning (5) Dynamic Range Window violation

Expert

 • 

111.3K Messages

2 years ago

@user_79617b 

Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private". 

That said. The upstream power is on the high side and it may be intermittently fluctuating even higher to out of spec levels. That can cause random disconnects, spontaneous re-booting of the modem, speed, packet loss, latency problems, and the un-bonding of channels.

In an effort to try to obtain better connectivity / more wiggle room, check to see if there are there any excess/unneeded coax cable splitters in the line leading to the modem that can be eliminated/re-configured. Any splitters that remain should be high quality and cable rated for 5-1000 MHz, bi-directional, and no gold colored garbage from Home Depot, Target, Wal-Mart, etc. Splitters should be swapped with known to be good / new ones to test.

Also check the coax cable for any damage such as cuts, nicks, abrasions, kinks, sharp bends, etc.

If there aren't any unneeded splitters that can be eliminated and if your coax wiring setup can't be reconfigured so that there is a single two-way splitter connected directly off of the drop from the street / pole with one port feeding the modem and the other port feeding the rest of the house/equipment with additional splits as needed and you've checked all the wiring and fittings for integrity and tightness and refresh them by taking them apart then check for and clean off any corrosion / oxidation on the center wire and put them back together again, then perhaps it's best to book a tech visit to investigate and correct.

4 Messages

@EG​ Apologies, I didn't realize my CM MAC and CMTS MAC were private components. I have replaced the MAC's with REDACTED. Thank you for the heads up and glad to hear there is some automation grabbing those things.

I was thinking the same thing with the higher levels after analyzing against what is normal. I originally was using XFinity's router/modem combo and was having the same disconnections, hence why I now have a modem and router separately just to diagnose this.

I had a tech come out last week to replace all the cables in the house. There is one splitter in the basement, but I don't have the proper setup to remove the splitter. That was freshly put in as well, so it's just one splitter with brand new cables in the house. It is a bi-directional splitter rated directly from Comcast, since that was replaced.

I checked the coax cable and no abrasions as far as I can tell. I have cleaned off all oxidation on the center wires of all connections, and made sure they were connected properly. Still experiencing random drops and issues with calls, which is important for work. Would you suggest I book another tech? I have a feeling it's an issue with the line coming in, or the line going down into the ground from the pole. I could be off base but that's my suspicion since even the line that was ran to the house is rather fresh. This has been on-going pretty much since May.

Appreciate any feedback you may have. Thank you for your time, and let me know if there is anything more I should do.

4 Messages

FYI, I have reconnected all the cables after cleaning:

Upstream Bonded Channels
Channel Lock Status US Channel Type Channel ID Symbol Rate Frequency Power
1 Locked ATDMA 1 5120 Ksym/sec 35600000 Hz 50 dBmV
2 Locked ATDMA 2 5120 Ksym/sec 29200000 Hz 50 dBmV
3 Locked ATDMA 3 5120 Ksym/sec 22800000 Hz 49.5 dBmV
4 Locked ATDMA 4 5120 Ksym/sec 16400000 Hz 49 dBmV
5 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
6 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
7 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV
8 Not Locked Unknown 0 0 Ksym/sec 0 Hz 0.0 dBmV

Still seeing higher upstream power levels.

Expert

 • 

111.3K Messages

2 years ago

@user_79617b 

You're quite welcome ! Yes. More needs to be done. There's no wiggle room to allow for those inevitable intermittent signal power fluctuations. 

So if there is nothing more that can be done by you to improve the connection quality, then you'll need to get the techs re-involved until things get fixed properly. 


Bear in mind that if the premises facing techs can not find or fix a problem at your home, it is they who are responsible for escalating it to their line / network / maintenance dept. techs. The problem may lie beyond your home in the local neighborhood infrastructure somewhere but it is their S.O.P. to start at the home. And if the problem is found to be on their side of the demarcation point, there will not be any charge.


Good luck !

Expert

 • 

111.3K Messages

2 years ago

My pleasure ! Good luck with this ! Please post back here with how things turn out.

Official Employee

 • 

1.4K Messages

2 years ago

Hello, @user_79617b. Thank you for reaching out over Xfinity Forums, you have reached out to the right place for assistance. I appreciate all the detailed information you have provided, and completely understand where you're coming from in regard to needing a solid internet connection as I work from home as well. 

 

I would like to ensure that you're able to get this corrected, and see you were working with someone over the phone. If you're still needing help, please send a DM with the requested information as we don't want that in a public conversation: 

To send a direct message: 

 

Click "Sign In" if necessary

 

• Click the "Direct Message" icon in the upper right - it looks like a chat bubble  

• Click the "New message" (pencil and paper) icon just to the right of Conversations

• Type "Xfinity Support" in the "To:" line - do not use the Employee's name!

• Type your message in the text area near the bottom of the window

• Press Enter to send it

To expedite your request, we ask that you please include your name, the account holder name (if different), and the service address. 

forum icon

New to the Community?

Start Here