J

Visitor

 • 

7 Messages

Thursday, August 18th, 2022 2:18 PM

Closed

Frequent drops and high 'Uncorrected' count on OFDM PLC

Hello,

I am facing frequent internet blips/ drops on my Internet and I've narrowed in down to Xfinity issue (rather than equipment - as I've ATT as well and that works seamlessly with same equipment, except for dsl/modem which is also not an issue per below). Can someone explain how to interpret the channel metrics from my modem?

Background - I had a Netgear CM1100 originally (brand new) and I was experiencing a lot of drops and the netgear admin console leaves a lot to be desired, so I bought a new Motorola 8611 to rule out modem issues. After installing 8611, when checking the channel metrics I see a huge number of uncorrected errors. Is that normal? I have verified the cable run from junction box to my house and then inside - everything is intact and like-new. No rips, no kinked cables, not many splitters, etc.

Is there anything I could do to fix this issue or ask xfinity to fix? Thanks a lot in advance!

 Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 42 399.0 1.7 44.3 0 0
   2 Locked QAM256 1 477.0 0.9 43.8 0 0
   3 Locked QAM256 2 483.0 0.8 43.6 0 0
   4 Locked QAM256 3 489.0 0.7 43.6 0 0
   5 Locked QAM256 4 495.0 0.6 43.5 0 0
   6 Locked QAM256 5 501.0 0.7 43.5 0 0
   7 Locked QAM256 6 507.0 0.7 43.4 0 0
   8 Locked QAM256 7 513.0 0.7 43.4 0 0
   9 Locked QAM256 8 519.0 0.6 43.2 0 0
   10 Locked QAM256 9 525.0 0.8 43.3 0 0
   11 Locked QAM256 10 531.0 1.1 43.4 0 0
   12 Locked QAM256 11 537.0 1.6 43.4 0 0
   13 Locked QAM256 12 543.0 1.7 43.3 0 0
   14 Locked QAM256 13 555.0 2.2 43.5 0 0
   15 Locked QAM256 14 561.0 2.0 43.6 0 0
   16 Locked QAM256 15 567.0 1.7 43.3 0 0
   17 Locked QAM256 16 573.0 1.9 43.3 0 0
   18 Locked QAM256 17 579.0 1.8 43.3 0 0
   19 Locked QAM256 18 585.0 1.7 43.4 0 0
   20 Locked QAM256 19 591.0 1.7 42.5 0 0
   21 Locked OFDM PLC 31 690.0 -1.0 37.6 942513200 16004567
   22 Locked QAM256 34 453.0 0.9 43.7 0 0
   23 Locked QAM256 35 459.0 1.1 43.8 0 0
   24 Locked QAM256 36 465.0 0.7 43.6 0 0
   25 Locked QAM256 37 471.0 0.7 43.6 0 0
   26 Locked QAM256 38 423.0 1.3 44.1 0 0
   27 Locked QAM256 39 429.0 1.2 44.2 0 0
   28 Locked QAM256 40 435.0 1.1 43.9 0 0
   29 Locked QAM256 41 441.0 1.1 43.7 0 0
   30 Locked QAM256 43 405.0 1.4 44.1 0 0
   31 Locked QAM256 44 411.0 1.5 44.1 0 0
   32 Locked QAM256 45 417.0 1.6 44.2 0 0

Visitor

 • 

7 Messages

3 years ago

Additional info - the above counts are during the 15 hours timespan on the new MB8611. 

Problem Solver

 • 

528 Messages

Hello! Please send me a private message. I can most definitely take a further look at this issue. To send a private message, please click the chat icon next to the bell in the upper right corner. Click the “notepad and pen” button. Send the full message to our shared support handle “Xfinity Support”.

I no longer work for Comcast.

Visitor

 • 

7 Messages

Hello, I've sent a DM too but haven't received a reply.

Expert

 • 

110.3K Messages

3 years ago

@XfinityCrystal 

Why does this have to go private right away ? That kind of defeats the purpose of a public help forum such as this is, no ?... Why not ask some general self-troubleshooting things first which is in keeping with the intent of what these public help forums were designed for so that all readers here may benefit. 

Expert

 • 

110.3K Messages

3 years ago

@jgxfinity 

Please copy all of the text in its entirety of the *Downstream Power Levels*, the *SNR's* (Signal to Noise Ratios), and the *Upstream Power Level* numbers and paste them into your next post.

Are there any modem RF error log entries being shown ? If so, please post them as well in their entirety (copy and paste them, don't post a screenshot) but redact the CM MAC and the CMTS MAC addresses for your privacy. They are considered to be personal information. The posting of personally identifying information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically.

Visitor

 • 

7 Messages

3 years ago

Thanks @EG  for your reply. I've posted all the details above (those are all the details I have on logs and status screens.

(edited)

Visitor

 • 

7 Messages

3 years ago

  Startup Step Status Comment

  
   Acquire Downstream Channel 399000000 Hz Locked
  
   Upstream Connection OK Operational
  
   Boot State OK Operational

  
   Configuration File OK
  
   Security Enabled BPI+

Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 42 399.0 1.4 44.4 0 0
   2 Locked QAM256 1 477.0 0.8 43.8 0 0
   3 Locked QAM256 2 483.0 0.7 43.7 0 0
   4 Locked QAM256 3 489.0 0.6 43.7 0 0
   5 Locked QAM256 4 495.0 0.5 43.5 0 0
   6 Locked QAM256 5 501.0 0.6 43.4 0 0
   7 Locked QAM256 6 507.0 0.6 43.5 0 0
   8 Locked QAM256 7 513.0 0.5 43.5 0 0
   9 Locked QAM256 8 519.0 0.5 43.3 0 0
   10 Locked QAM256 9 525.0 0.6 43.3 0 0
   11 Locked QAM256 10 531.0 0.9 43.4 0 0
   12 Locked QAM256 11 537.0 1.3 43.5 0 0
   13 Locked QAM256 12 543.0 1.5 43.3 0 0
   14 Locked QAM256 13 555.0 1.9 43.6 0 0
   15 Locked QAM256 14 561.0 1.7 43.5 0 0
   16 Locked QAM256 15 567.0 1.3 43.1 0 0
   17 Locked QAM256 16 573.0 1.5 43.3 20 0
   18 Locked QAM256 17 579.0 1.4 43.3 35 0
   19 Locked QAM256 18 585.0 1.3 43.3 7 0
   20 Locked QAM256 19 591.0 1.2 42.2 13 0
   21 Locked OFDM PLC 31 690.0 -2.3 0.0 -467878538 98465589
   22 Locked QAM256 34 453.0 0.8 43.8 0 0
   23 Locked QAM256 35 459.0 1.0 43.9 0 0
   24 Locked QAM256 36 465.0 0.7 43.8 0 0
   25 Locked QAM256 37 471.0 0.7 43.6 0 0
   26 Locked QAM256 38 423.0 0.8 44.0 0 0
   27 Locked QAM256 39 429.0 0.6 44.1 0 0
   28 Locked QAM256 40 435.0 0.6 43.9 0 0
   29 Locked QAM256 41 441.0 0.7 43.8 0 0
   30 Locked QAM256 43 405.0 1.1 44.2 0 0
   31 Locked QAM256 44 411.0 1.0 44.1 0 0
   32 Locked QAM256 45 417.0 1.1 44.1 0 0

Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 35.6 51.0
   2 Locked SC-QAM 2 5120 29.2 51.0
   3 Locked SC-QAM 3 5120 22.8 51.3
   4 Locked SC-QAM 4 5120 16.4 51.3
   5 Locked SC-QAM 5 1280 39.6 50.0

 Event Log  
  
    Time    Priority    Description 
    13:26:23
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:27:03
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:27:05
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:27:18
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:27:22
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:27:36
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:27:56
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:27:57
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:27:58
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:28:12
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:28:32
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:28:55
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:28:58
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:29:27
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:29:41
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:29:49
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:29:51
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:29:56
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:30:31
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:30:32
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:31:10
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:31:38
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:31:52
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:31:54
Thu Aug 18 2022
  Warning (5)   MDD message timeout;CM-QOS=1.1;CM-VER=3.1;
    13:32:01
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 23; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:32:01
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 22; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:32:05
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:32:14
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 20; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:32:15
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-QOS=1.1;CM-VER=3.1;
    13:32:20
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    13:32:28
Thu Aug 18 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-QOS=1.1;CM-VER=3.1;
    03:43:14
Fri Aug 19 2022
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 31; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1 2 3.;CM-QOS=1.1;CM-VER=3.1;

Expert

 • 

110.3K Messages

3 years ago

Quite welcome ! O/k so 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.

Here are some self troubleshooting tips that may or may not apply but I'm going to include them anyway;

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 Radio Shack, Home Depot, Target, 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, 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.

If there is nothing more that can be done to improve the connection quality, then you'll need a tech visit as stated. 


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 !

(edited)

Visitor

 • 

7 Messages

3 years ago

Thanks @EG . I saw your post on another thread and I did all the troubleshooting you've mentioned. From the junction box in the yard - the Comcast cable comes to my wall junction box where it goes to a splitter to split into 2 connections to go into the house. Inside the basement that cable is directly connected via a 2-way female to the coax endpoint of the wall cable outlet on the top floor. I guess I'll let Xfinity support reply to my DM and then schedule a tech visit.

Problem Solver

 • 

528 Messages

Hello! Please send me a private message. I can most definitely take a further look at this issue. To send a private message, please click the chat icon next to the bell in the upper right corner. Click the “notepad and pen” button. Send the full message to our shared support handle “Xfinity Support”. We look forward to hearing from you!

I no longer work for Comcast.

Expert

 • 

110.3K Messages

@jgxfinity​ Good luck with it and please post back here with how things turn out. Thank you !

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? Please mark an Accepted Answer!tick

Visitor

 • 

9 Messages

3 years ago

I am seeing similar issues.  I have a SonicWall firewall behind my S33 cable modem.  I see in its logs multiple WAN connectivity failures per day.  In addition I am now seeing one third of my provisioned throughput.  I am provisioned for 300/10.  In the past speedtest.net would indicate approximately 360/11.  Now it indicates approximately 100/11.  Sometimes it is around 80/11.

When this service was initially setup there were signal strength issues (mid to low 30dB range).  It took a few months, but that was corrected.  They replaced the COAX from the pedestal to my home.  That had no impact on the issue.  Later after escalation they found an issue upstream somewhere and I saw all signal levels come up to 42 dB or more.  A week later they want back down, another ticket and they came back up again.  Things were stable for months until I started noticing slowdown issues and the WAN disconnects logged in my firewall.  The WAN disconnects are short, sometimes under a minute, other times only a minute or two.  My signal levels are still between 40 dB and 42 dB with most at 41 dB.

I have rebooted my cable modem (more than once) and I haven't changed anything on my end.  Perhaps network congestion or something else upstream.  I am open to thoughts, but I don't want to go through multiple be at home appointments again before they look upstream if it is possible to avoid that. 

I'm located in Northern Virginia  10 miles outside the Washington, DC beltway.

(edited)

Expert

 • 

110.3K Messages

3 years ago

@user_f8cbd6 

Please create a new topic of your own here on this board detailing your issue. Thanks. For future reference, it is better to submit your own post as it creates a ticket to get help, and posting on someone else's help thread in progress may delay you in getting help.

forum icon

New to the Community?

Start Here