S

Visitor

 • 

3 Messages

Thursday, February 17th, 2022 5:12 PM

Closed

DOCSIS 3.1 Downstream Dropping, Event Type Codes 20 and 22

For a few months now, my modem (Arris Surfboard SB8200) has been dropping DOCSIS 3.1 downstream connection and reverting back to 3.0.  I've been trying to troubleshoot but can't seem to find anything else I can do in my setup to fix it.  When I first started looking into it, I was seeing an increasing number of uncorrectables on channel 159.  I remade all the connections between my modem and the outside drop and that seems to have cleared the uncorrectables.  However, my 3.1 connection is falling back to 3.0 after about 24 hours of uptime.  On my last reboot, I saw the status light change and checked my logs and at 24 hours to the minute I had an event code 20 followed by a 22 show up.  Those error pairs have happened a few times since that first error, I've been letting the modem run to see if things would either correct or uncorrectable errors would appear.

I've copied my levels below.  From what I've found searching, my downstream power is a little low and upstream is a little high.  I have two splitters between the outside drop and my modem (one 3-way outside off the main drop to different ports inside and one 2-way to my modem and a MoCA adapter).  I checked that my modem is on the 3dB leg of the 3-way.  I don't see a way to remove either of them so I'm not sure what next steps would be.

Appreciate any help that can be given!

Startup Procedure
Procedure Status Comment
Acquire Downstream Channel 501000000 Hz Locked
Connectivity State OK Operational
Boot State OK Operational
Configuration File OK
Security Enabled BPI+
DOCSIS Network Access Enabled Allowed

Downstream
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
1 Locked QAM256 501000000 Hz -9.9 dBmV 39.5 dB 11 0
2 Locked QAM256 507000000 Hz -9.5 dBmV 40.4 dB 0 0
3 Locked QAM256 513000000 Hz -9.5 dBmV 40.1 dB 40 0
4 Locked QAM256 519000000 Hz -9.2 dBmV 40.7 dB 45 0
5 Locked QAM256 525000000 Hz -9.4 dBmV 40.0 dB 1 0
6 Locked QAM256 531000000 Hz -10.2 dBmV 40.0 dB 16 0
7 Locked QAM256 537000000 Hz -10.8 dBmV 39.7 dB 0 0
8 Locked QAM256 543000000 Hz -10.9 dBmV 39.2 dB 1 0
9 Locked QAM256 555000000 Hz -9.5 dBmV 40.3 dB 0 0
10 Locked QAM256 561000000 Hz -9.2 dBmV 40.2 dB 0 0
11 Locked QAM256 567000000 Hz -10.4 dBmV 39.8 dB 0 0
12 Locked QAM256 573000000 Hz -11.0 dBmV 39.3 dB 0 0
13 Locked QAM256 579000000 Hz -10.7 dBmV 39.9 dB 0 0
14 Locked QAM256 585000000 Hz -10.1 dBmV 40.1 dB 1 0
15 Locked QAM256 591000000 Hz -10.4 dBmV 39.9 dB 1 0
16 Locked QAM256 597000000 Hz -11.0 dBmV 39.6 dB 0 0
17 Locked QAM256 603000000 Hz -11.1 dBmV 39.6 dB 0 0
18 Locked QAM256 609000000 Hz -11.7 dBmV 39.0 dB 0 0
19 Locked QAM256 615000000 Hz -9.8 dBmV 40.2 dB 0 0
20 Locked QAM256 621000000 Hz -11.1 dBmV 39.6 dB 0 0
21 Locked QAM256 627000000 Hz -11.2 dBmV 39.7 dB 1 0
22 Locked QAM256 633000000 Hz -10.7 dBmV 39.8 dB 0 0
23 Locked QAM256 639000000 Hz -10.1 dBmV 40.1 dB 1 0
24 Locked QAM256 645000000 Hz -10.0 dBmV 39.9 dB 0 0
25 Locked QAM256 651000000 Hz -9.9 dBmV 40.0 dB 5 0
26 Locked QAM256 657000000 Hz -10.4 dBmV 39.7 dB 0 0
27 Locked QAM256 663000000 Hz -10.5 dBmV 40.0 dB 0 0
28 Locked QAM256 669000000 Hz -10.2 dBmV 39.3 dB 0 0
29 Locked QAM256 675000000 Hz -9.4 dBmV 39.9 dB 0 0
30 Locked QAM256 681000000 Hz -9.5 dBmV 40.3 dB 0 0
31 Locked QAM256 687000000 Hz -9.7 dBmV 39.9 dB 0 0
32 Locked QAM256 693000000 Hz -10.7 dBmV 39.4 dB 0 0
159 Locked Other 805000000 Hz -10.3 dBmV 38.0 dB 2428700353 0

Upstream
Channel Channel ID Lock Status US Channel Type Frequency Width Power
1 1 Locked SC-QAM Upstream 16400000 Hz 6400000 Hz 50.0 dBmV
2 2 Locked SC-QAM Upstream 22800000 Hz 6400000 Hz 50.0 dBmV
3 3 Locked SC-QAM Upstream 29200000 Hz 6400000 Hz 50.0 dBmV
4 4 Locked SC-QAM Upstream 35600000 Hz 6400000 Hz 50.0 dBmV
5 5 Locked SC-QAM Upstream 40400000 Hz 3200000 Hz

51.0 dBmV

Date Time Event ID Event Level Description
02/16/2022 14:24 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/16/2022 14:24 74010100 6 "CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/16/2022 11:38 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/16/2022 11:16 74010100 6 "CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/16/2022 11:14 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/16/2022 11:04 74010100 6 "CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/15/2022 9:48 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/15/2022 9:47 74010100 6 "CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/15/2022 9:36 74010100 6 "CM-STATUS message sent. Event Type Code: 22; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/15/2022 9:36 74010100 6 "CM-STATUS message sent. Event Type Code: 20; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/14/2022 9:36 67050300 5 "DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/14/2022 9:36 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/14/2022 9:24 73050400 5 "REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/14/2022 9:24 67061600 6 "DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:00 2436694066 6 "Honoring MDD; IP provisioning mode = IPv6"
01/01/1970 0:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
02/14/2022 9:23 2436694044 3 "Resetting the cable modem due to docsDevResetNow"
02/12/2022 14:02 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
02/10/2022 17:37 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/10/2022 17:34 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/10/2022 17:34 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/10/2022 17:34 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/10/2022 17:34 84000400 3 "SYNC Timing Synchronization failure - Failed to receive MAC SYNC frame within time-out period;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
02/03/2022 23:09 84000500 3 "SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/26/2022 18:10 82000500 3 "Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:02 82000200 3 "No Ranging Response received - T3 time-out;CM-MAC=<<MODEM MAC>>;CMTS-MAC=<<UNKNOWN MAC>>;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:01 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"
01/01/1970 0:00 84000100 3 "SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=<<MODEM MAC>>;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;"

Accepted Solution

Visitor

 • 

3 Messages

3 years ago

Update 2 and final update:

After my last reply, I was in touch with chat support again and they suggested another tech come out because the first one "must have missed something."  I agreed and within a few days another tech was out to take a look.  Immediately he started pointing out all the things that were "absolutely causing my problems" without even checking signal levels, and that the previous tech must not have even tried looking and didn't know what he was talking about.  After the initial criticisms, he did unhook everything and check the lines.  This tech also had no idea what a MoCA network was but was confident that it was incompatible with Xfinity's network, even though the previous tech had confirmed via a phone call that customer MoCA networks were 100% OK as long as there is a filter at the first connection (which I have).  After taking all the levels, the tech came up with three fixes, two of which he implemented at the same time so I couldn't tell what effect each had. 

First, he switched the outside connection at the node to a different port because the one I was currently on was bad.  No real explanation here, as he glossed over that real quickly to blame my internal connections and wouldn't answer questions about it when I tried to ask.

Second was changing a few connections inside.  He swapped my coax wallplate to a higher quality one, according to him.  He also changed all my splitters to unbalanced two-ways, and put the path to the modem on the lowest resistance line (-2dB vs the -3.5dB it was on previously).  This lost me an active coax port within my home, however it was unused, so not the biggest deal.  Interestingly, he stated the splitter originally installed by Xfinity and the one internal were "not rated for Xfinity's network" however the ones he installed actually pass a lower range of frequencies (i.e. don't pass typical MoCA frequencies) and both splitters he removed were fairly high quality.

Last, he ordered me a new drop from the node since mine was old.  That was completed a few days later and seems to have no affect (good or bad).

After all was said was done, he managed to bring my levels to around -4dB to -7dB and I have kept a DOCSIS signal since he left so my problem is resolved.  I'm still fairly confused at why raising delivered power levels is not an option, it seems like a home should be able to have more than one splitter before the signal inside the home is lowered out of spec.  If I needed that third coax port, would I just be out of luck?  Seems strange to me, but maybe there's a good reason.

Up to the second tech's visit I had actually been pretty impressed with Xfinity's responsiveness to the issue.  However, the second tech ended up leaving a bit of a bad taste in my mouth.  He kept repeating that I would likely be charged for the visit since it was customer installed equipment causing the problem, even though he changed the outside line and the splitter provided by Xfinity (waiting to see if I'll need to have that battle with Xfinity billing or not).  His confidence that he knew exactly what the issue was from the start even though it took him about 2 hours to basically just change a wallplate and a couple splitters has me very skeptical of his claimed in depth knowledge of coax networks. 

At this point, I'm happy to have a stable connection and am hoping to not have to have any more technician visits in the near future.

Official Employee

 • 

2.5K Messages

3 years ago

Hi there! Our awesome digital care team would be happy to assist you. Can you initiate a chat and start with your full name and address? To start a chat, you must be signed in. Please click the chat icon in the top right of the page next to the bell, and send your message to "Xfinity Support". Talk to you there!

Expert

 • 

110.1K Messages

3 years ago

@spookytoast wrote;

From what I've found searching, my downstream power is a little low and upstream is a little high. 

Yes. 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 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.


Good luck with it !

Visitor

 • 

3 Messages

3 years ago

An update on what's happened so far:

I was able to start a chat with the Xfinity support team and get a tech visit scheduled same day.  The tech came out and checked the levels at my modem as well as coming from the pole.  He was very courteous and listened to everything I was telling him.  After taking the levels and re-terminating a couple of my unused lines, he said there was nothing really wrong internally he could see and that the power level coming from the pole was a little low (however not enough in his opinion to cause serious issues).  He also noticed that there must be some upgrading going on because I gained an upstream channel between my first post and the day he was out.  The tech said he would put in a ticket to the network team to look at the closest node, as there was also some component inside which was able to move but shouldn't be. 

The next day, I got a follow up call from Xfinity support because I had responded to their survey that my issue had not been corrected.  I told them the tech did a great job, but was unable to find anything to fix and that there should be a ticket in with the network team.  The support agent said he would follow up with the network team to make sure it was being worked.

The day after, there was network outage for an hour or two (a friend about 5 miles away was also down).  Since then, I had been seeing slightly better downstream power levels (-7dB instead of -9dB) and my DOCSIS 3.1 light was staying on...until today.  After 4 days of no errors, this afternoon I lost my DOCSIS 3.1 connection and I see two sets of event code 20/22 errors in my log.

So it looks like things are still currently unchanged and, according to the tech, I'm at the mercy of Xfinity raising power levels.  I'm hoping the network team still has to look at the node and that the outage earlier wasn't their attempt to fix things. 

forum icon

New to the Community?

Start Here