R

Visitor

 • 

3 Messages

Monday, July 24th, 2023 6:17 PM

Closed

DOCSIS3.0 is slow but consistent while DOCSIS3.1 is faster but fails often

I have Xfinity high speed service in the SF Bay Area and have been frustrated with the following issue. My OLD Netgear CM600 (DOCSIS3.0) works well and is stable, but limits my connection speeds due to the age of the modem. I've tried 2 different DOCSIS3.1 models (Netgear CM1200 and Motorola MB8611) and both have the same problem. They both connect and provide higher speeds BUT disconnect/reconnect randomly (several times a day) resulting in no internet for 5 minutes. I've had an Xfinity technician come out and re-wire the cable coming into the house. We still have the same issue. 

This post from a couple of years ago captures what we have been experiencing since establishing service: https://forums.xfinity.com/conversations/your-home-network/docsis30-works-31-no-longer-functional/605f901fc264e93e85820b74.

Is there a known functional issue for Xfinity and DOCSIS3.1? Is there anyone who is successfully maintaining a stable connection with DOCSIS3.1 modems? I briefly owned an Aris SB8200 but returned it when the technician told me there was a known issue that Aris and Xfinity were working to resolve. Could this be more widespread? For such a critical service, I'd like a clearer explanation of what the problem is and how it can be resolved. Most support focuses on the "did you make sure your modem is plugged in or please manually restart your modem" level, which hasn't been helpful.

Contributor

 • 

204 Messages

2 years ago

DOCSIS 3.1 isn't the problem, at least not directly.  It's probably a line issue.  DOCSIS 3.1 modems are backwards compatible with DOCSIS 3.0, but also support signaling modes that 3.0 doesn't.  Comcast runs a mixed network with some of both.  The 3.0 and 3.1 signaling use different frequencies, so what's probably going on is you have some interference that mostly or only affects the 3.1 frequencies.  If you have a 3.1 modem it will use the 3.1 only frequencies and there's nothing you can do about that.

If everything is working properly DOCSIS 3.1 can be very stable.  My NetGear CM2050V stayed up so long the uptime counter rolled over and started displaying negative numbers.  I'm pretty sure it was more than a year.

Could you post your signal stats?  Bonus if you can do it with a DOCSIS 3.1 modem since a 3.0 modem won't report signal problems at 3.1 only frequencies.  This post gives you some info on how to do it but it's modem specific:  https://forums.xfinity.com/conversations/your-home-network/internet-troubleshooting-tips/602dae4ac5375f08cde52ea0  Be sure to redact any MAC addresses (CM-MAC, etc.) and public IP addresses.  The forum regards them as personal information and will block your post if you don't.  Also it works much better to cut and paste a table rather than taking a screen shot.  The forum does quite well with pasted tables and the result will be more readable.

Visitor

 • 

3 Messages

2 years ago

Hi,

Quick update. I switched back to the DOCSIS 3.1 modem and it was running for nearly a week without any issues. All of a sudden, today it started losing connections again. This time it's multiple times per hour. Here is the latest snapshot of the connection details. In addition, I confirmed that the new coax line that the technician ran goes straight from the junction box on the side of the garage to my cable modem. I'm not sure if there's a way for me to check anything between my house and the junction box on the street. Let me know if additional information would be helpful.

Connection
   Startup Step Status Comment
   Acquire Downstream Channel 507000000 Hz Locked
   Upstream Connection OK Operational
   Boot State OK Operational
   Configuration File OK
  
   Security Enabled BPI+

   Connection Status    
   System Up Time 0 days 00h:09m:13s
   Network Access Allowed

Downstream Bonded Channels
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 20 507.0 8.9 42.1 0 0
   2 Locked QAM256 4 405.0 8.4 42.0 0 0
   3 Locked QAM256 5 411.0 8.4 42.0 0 0
   4 Locked QAM256 6 417.0 8.5 41.9 0 0
   5 Locked QAM256 7 423.0 8.5 41.9 0 0
   6 Locked QAM256 8 429.0 8.7 42.1 0 0
   7 Locked QAM256 9 435.0 8.8 41.9 0 0
   8 Locked QAM256 10 441.0 8.7 41.8 0 0
   9 Locked QAM256 11 447.0 8.8 41.9 0 0
   10 Locked QAM256 12 453.0 8.8 42.0 0 0
   11 Locked QAM256 13 459.0 8.7 41.9 0 0
   12 Locked QAM256 14 465.0 8.9 42.1 0 0
   13 Locked QAM256 15 471.0 8.9 41.9 0 0
   14 Locked QAM256 16 477.0 8.8 42.1 0 0
   15 Locked QAM256 17 483.0 8.8 42.0 0 0
   16 Locked QAM256 18 489.0 8.6 41.8 0 0
   17 Locked QAM256 19 495.0 8.6 41.8 0 0
   18 Locked QAM256 21 513.0 8.8 42.1 0 0
   19 Locked QAM256 22 519.0 8.7 42.0 0 0
   20 Locked QAM256 23 525.0 8.6 41.9 0 0
   21 Locked QAM256 24 531.0 8.6 42.0 0 0
   22 Locked QAM256 25 537.0 8.6 41.9 0 0
   23 Locked QAM256 26 543.0 8.7 42.1 0 0
   24 Locked QAM256 27 549.0 8.6 41.9 0 0
   25 Locked QAM256 28 555.0 8.6 41.8 0 0
   26 Locked QAM256 29 561.0 8.5 41.8 0 0
   27 Locked QAM256 30 567.0 8.9 42.0 0 0
   28 Locked QAM256 31 573.0 9.0 42.0 0 0
   29 Locked QAM256 32 579.0 9.2 41.9 0 0
   30 Locked QAM256 33 585.0 9.1 41.9 0 0
   31 Locked QAM256 34 591.0 8.9 41.7 0 0
   32 Locked OFDM PLC 48 688.0 8.6 41.1 8146517 0

Upstream Bonded Channels
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 6 2560 10.4 37.8
   2 Locked SC-QAM 7 5120 16.4 38.0
   3 Locked SC-QAM 8 5120 22.8 38.0
   4 Locked SC-QAM 9 5120 29.2 38.0
   5 Locked SC-QAM 10 5120 35.6 38.3
   6 Locked SC-QAM 12 2560 40.4 38.5

Visitor

 • 

3 Messages

2 years ago

Some additional notes on things I can see with the connection details:

1. The frequencies used by the channels does not seem to approach 1GHZ

2. The downstream channel using OFDM PLC for modulation seems to have a VERY high number of correctable packets. 

3. When I check the event log I see A LOT of T3 time-outs (alternating between SYNC Timing Synchronization failures and No Ranging Response received:

Example:

Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.1;

Problem Solver

 • 

1.5K Messages

@rilkeanheart​ You were running high on downstream power, and only up for 9 minutes at that point. It probably drifts higher during the day.  I know they say -10dB to +10dB for a modem, -7dB to +7dB for a gateway in the troubleshooting doc they have pinned, but I suspect that was from quite a while ago.  Everyone's using the same parts for DOCSIS these days and I'd go with the smaller range if you want it to work reliably.  I'd fix that issue first.

Correctable errors on the OFDM channel are hardware corrected and part of the protocol.  They didn't cost you anything in a delay, and it was done on the fly.  If you want the gory details, some specifications on how it works and the protocols are published for free by cablelabs:

https://www.cablelabs.com/specifications/

Official Employee

 • 

1.6K Messages

Hey there @rilkeanheart Thanks so much for taking the time to reach out regarding these connection issues. We can certainly take a look at your current signal levels to see if we can ID any possible patterns. 

 

Please send a direct message by clicking the chat icon in the upper right corner of the page, click on the pen and paper icon, then enter “Xfinity Support” in the “To” section. Please include your name and address and I'll be happy to help.  

I am an Official Xfinity Employee.
Official Employees are from multiple teams within Xfinity: CARE, Product, Leadership.
We ask that you post publicly so people with similar questions may benefit from the conversation.
Was your question answered? Please, mark a reply as the Accepted Answer.tick

Visitor

 • 

12 Messages

2 years ago

I had to switch back to the Xfinity XB8. I'm in NH and I was getting similar issues with my MB8611. One thing to note is that you have Docsis 3.1 only on your downstream channels, channel 32. OFDM is part of Docsis 3.1. You only have Docsis 3.0 on the upload. It's a huge difference I noticed between my MB8611 and the XB8. The XB8 I have has 4 QAM channels and 1 OFDMA channel on the upload. The 8611 only had the 4 QAM channels.

My issue was slow upload speeds and also a lot of packet loss every single day. Once I switched to the XB8 and put it in bridging mode, the issues went away. I'm very unhappy about having to pay an extra $15/month for a Comcast modem because they can't properly provision customer owned equipment to be stable and with the advertised speeds. 

Also adding that I had opened up a case with Motorola and they sent me a replacement modem. Same issue with original and replacement modem.

forum icon

New to the Community?

Start Here