U

Contributor

 • 

35 Messages

Thursday, March 13th, 2025 1:52 PM

getting repeat errors

I get the same 2 errors several times a day

CM-STATUS message sent. Event Type Code: 16; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

CM-STATUS message sent. Event Type Code: 24; Chan ID: 33; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;

Expert

 • 

109.7K Messages

30 days ago

Are you actually having any drops with the internet connection or just curious about those log entries ?

Contributor

 • 

35 Messages

30 days ago

Long story but I had a SB8200 and it didn't seen to drop the connection. I then bought an MB8611 and it would drop the connection so I got an SBG8300 and it didn't didn't drop. Now I got an S33 and it dropped once so far but I just got it.

So to answer your question yes sometimes with some modems.

Contributor

 • 

35 Messages

30 days ago

A little more info. The channel it is referring to has lots of corrected and uncorrected errors

33 Locked OFDM PLC 690000000 Hz -2 dBmV 41 dB 612336433 4684079

Expert

 • 

109.7K Messages

30 days ago

Please post all of the error log entries in their entirety (copy and paste them, don't post a screenshot) but redact any 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 publicly.

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

Contributor

 • 

35 Messages

30 days ago

I had just rebooted before your message. Thanks for any help.

Date Time Event Level Description
31/12/1969
19:00:15
3 CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz.
31/12/1969
19:00:19
3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:21
3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-9, 42MHz.
31/12/1969
19:00:24
3 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:28
6 Honoring MDD; IP provisioning mode = IPv6
31/12/1969
19:00:37
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
31/12/1969
19:00:37
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
31/12/1969
19:00:37
3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
13/3/2025
12:40:28
6 DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
12:41:15
3 Successful LAN WebGUI login from 71.207.71.20 on 25/03/13 at 12:41 PM.
13/3/2025
12:42:11
3 Successful LAN WebGUI login from 71.207.71.20 on 25/03/13 at 12:42 PM.

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

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
42 Locked QAM256 405000000 Hz 2 dBmV 42 dB 0 0
1 Locked QAM256 429000000 Hz 3 dBmV 42 dB 0 0
2 Locked QAM256 435000000 Hz 3 dBmV 42 dB 0 0
3 Locked QAM256 441000000 Hz 3 dBmV 42 dB 0 0
4 Locked QAM256 447000000 Hz 4 dBmV 42 dB 0 0
5 Locked QAM256 453000000 Hz 4 dBmV 43 dB 0 0
6 Locked QAM256 459000000 Hz 4 dBmV 42 dB 0 0
7 Locked QAM256 465000000 Hz 4 dBmV 42 dB 0 0
8 Locked QAM256 471000000 Hz 4 dBmV 42 dB 0 0
9 Locked QAM256 477000000 Hz 4 dBmV 43 dB 0 0
10 Locked QAM256 483000000 Hz 4 dBmV 42 dB 0 0
11 Locked QAM256 489000000 Hz 4 dBmV 42 dB 0 0
12 Locked QAM256 495000000 Hz 5 dBmV 43 dB 0 0
13 Locked QAM256 507000000 Hz 5 dBmV 43 dB 0 0
14 Locked QAM256 513000000 Hz 5 dBmV 43 dB 0 0
15 Locked QAM256 519000000 Hz 5 dBmV 42 dB 0 0
16 Locked QAM256 525000000 Hz 5 dBmV 43 dB 0 0
17 Locked QAM256 531000000 Hz 5 dBmV 42 dB 0 0
18 Locked QAM256 537000000 Hz 4 dBmV 42 dB 0 0
19 Locked QAM256 543000000 Hz 4 dBmV 42 dB 0 0
20 Locked QAM256 549000000 Hz 4 dBmV 42 dB 0 0
21 Locked QAM256 555000000 Hz 4 dBmV 42 dB 0 0
22 Locked QAM256 561000000 Hz 4 dBmV 42 dB 0 0
23 Locked QAM256 567000000 Hz 4 dBmV 42 dB 0 0
24 Locked QAM256 573000000 Hz 4 dBmV 42 dB 0 0
25 Locked QAM256 579000000 Hz 4 dBmV 42 dB 0 0
26 Locked QAM256 585000000 Hz 4 dBmV 42 dB 0 0
27 Locked QAM256 591000000 Hz 4 dBmV 42 dB 0 0
33 Locked OFDM PLC 690000000 Hz 0 dBmV 41 dB 37475254 0
43 Locked QAM256 411000000 Hz 2 dBmV 42 dB 0 0
44 Locked QAM256 417000000 Hz 3 dBmV 42 dB 0 0
45 Locked QAM256 423000000 Hz 3 dBmV 42 dB 0 0



Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
2 Locked SC-QAM 16300000 Hz 6400000 43.8 dBmV
3 Locked SC-QAM 22800000 Hz 6400000 43.8 dBmV
4 Locked SC-QAM 29200000 Hz 6400000 43.3 dBmV
5 Locked SC-QAM 35600000 Hz 6400000 42.0 dBmV
6 Locked SC-QAM 40400000 Hz 3200000 43.3 dBmV



Expert

 • 

109.7K Messages

30 days ago

The signal status values at that snapshot in time were OK but the error log entries indicate that something is going on. Perhaps there is noise ingress into the line(s) /  an upstream channel / return path impairment somewhere.

There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and those upstream receive signal stats.


You should get a reply here in your topic. Good luck !

Even though the signal status values looked OK at that snapshot in time, the error log entries confirm that something is going on. Perhaps there is noise ingress into the line(s) / an upstream channel / return path impairment somewhere.


There are other signal stat values that can't be read by the modem. They are the "Upstream Rx Power" (Upstream Receive Power Level), the "Upstream SNR Ch." (Upstream Signal To Noise Ratio), and the "Upstream ICFR" (In Channel Frequency Response). These are as equally important in diagnosing connectivity issues as are the modem's stats.


I'm going to escalate your issue to the Comcast corporate employees (The Digital Care Team) who are available to these boards. They will be able to poll the CMTS (Cable Modem Termination System) to check for any real-time degradation and / or error reports, see your node / cable plant, and modem health, and see whether or not everything is in the green zone. They can also see a history plot for the modem and check those upstream receive signal stats.

You should get a reply here in your topic. Good luck !

Contributor

 • 

35 Messages

30 days ago

Thank you for your help

Official Employee

 • 

2.5K Messages

Hi there, user_a9365

 

Thanks for the detailed info! Based on what you're describing, it looks like the issues you're seeing—specifically the corrected/uncorrected errors and the drops on certain modems—could be signal-related. The OFDM channel (ID 33) showing a high number of corrected errors could indicate a noise issue or a problem with how your modem is handling the signal.

 

We would like to look into this further. Can you initiate a direct message and start with your full name and address? To start a direct message, you must be signed in. Please click the "Direct Messaging" icon in the top right of the page next to the bell, and send your message to "Xfinity Support". Talk to you there!

 

 

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

Expert

 • 

109.7K Messages

@XfinityAirelle​ wrote:

The OFDM channel (ID 33) showing a high number of corrected errors could indicate a noise issue or a problem with how your modem is handling the signal.

FWIW. A large amount of corrected errors on an OFDM channel is to be expected. It's the way it works and is normal. . It is a very wide bandwidth channel that packs a lot of data within. Due to that fact, seeing a large number of corrected errors is normal. The FEC (Forward Error Correction) circuitry / system is doing its job. It's the *uncorrectable* bit errors that can be problematic in large amounts.

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

Expert

 • 

109.7K Messages

30 days ago

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

Contributor

 • 

35 Messages

Tech support checked out everything and they said it all looked good. Thanks again

Contributor

 • 

35 Messages

30 days ago

I don't know if it helps but here is a complete log I just did a complete reset.

Date Time Event Level Description
31/12/1969
19:00:15
3 CMSTATUS:US_Diplexer_Mode_Change:Init, 5-42MHz.
31/12/1969
19:00:21
3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:00:31
5 Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:19
3 SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:26
5 Lost MDD Timeout;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:27
3 CMSTATUS:US_Diplexer_Mode_Change_Ignored:TLV-9, 42MHz.
31/12/1969
19:01:31
3 Successful LAN WebGUI login from 192.168.100.10 on 70/01/01 at 12:01 AM.
31/12/1969
19:01:33
3 No Ranging Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
31/12/1969
19:01:42
6 Honoring MDD; IP provisioning mode = IPv6
31/12/1969
19:01:51
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.2, 108MHz.
31/12/1969
19:01:51
3 CMSTATUS:DS_Diplexer_Mode_Change_Ignored:TLV-84.3, 1002MHz.
31/12/1969
19:01:51
3 CMSTATUS:US_Diplexer_Mode_Change:TLV-84.1, 5-42MHz.
13/3/2025
13:35:15
3 Successful LAN WebGUI login from 192.168.100.10 on 25/03/13 at 1:35 PM.
13/3/2025
13:35:16
6 DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
13:35:16
3 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
13:35:22
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
13:35:22
5 Dynamic Range Window violation
13/3/2025
13:35:22
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
13:35:22
5 Dynamic Range Window violation
13/3/2025
13:35:22
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
13:35:22
5 Dynamic Range Window violation
13/3/2025
13:35:22
5 RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
13/3/2025
13:35:23
5 Dynamic Range Window violation
forum icon

New to the Community?

Start Here