U

Visitor

 • 

13 Messages

Tue, Nov 23, 2021 6:04 PM

Closed

High number of Uncorrected packets. Internet drops. Direct wired connection.

Good afternoon,

Router/Modem MG8702.

Direct wired connection via ethernet cable. From street - into the house - into the router/modem. No splitters involved. No WiFi use. 

Below I post my event log and SNR and Power values. As you can see in just 3 hrs of use I have about 60 uncorrected packets on avg. Uncorrected values are higher than corrected.  If I do not reset the modem/router I get over 2000 uncorrected in 2-3 days. 

This is a brand new router.  I assumed it might have been a router issue because I was using an old one.  The numbers below are from a brand new router that I have had for 1 month.

I believe the issue is with the line coming to my house.  Thank you for your help.

[Image Removed: "Personal Information"]

Accepted Solution

Visitor

 • 

13 Messages

1 m ago

Update: 

2 days of stable connection. 0 uncorrected packets. 0 errors in log. 

I will close this as solved. Solved by a tech visit.

EG

Expert

 • 

91.6K Messages

@user_ef90aa

Now closing your thread. 

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
EG

Expert

 • 

91.6K Messages

2 m ago

The signal stats are ok / in spec. Please post the modem's RF error log entries in their entirety (copy and paste all of the text) but redact the CM and the CMTS MAC addresses for your privacy or else the forum bot will not allow your post to be seen publically.

Visitor

 • 

13 Messages

@EG

   Time    Priority    Description 
    20:55:24
Sun Nov 21 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=CMTS-MAC=QOS=1.1;CM-VER=3.1;
    20:55:27
Sun Nov 21 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    20:55:42
Sun Nov 21 2021
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    20:55:50
Sun Nov 21 2021
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    21:46:14
Sun Nov 21 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    22:03:11
Sun Nov 21 2021
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    22:55:24
Sun Nov 21 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    00:25:16
Mon Nov 22 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    00:35:34
Mon Nov 22 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    11:17:33
Mon Nov 22 2021
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    16:54:26
Mon Nov 22 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    17:49:20
Mon Nov 22 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=;CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    18:34:51
Mon Nov 22 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=CMTS-MAC=-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    09:04:27
Tue Nov 23 2021
  Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    09:04:32
Tue Nov 23 2021
  Warning (5)   REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    09:16:37
Tue Nov 23 2021
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    09:16:39
Tue Nov 23 2021
  Warning (5)   DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=;CMTS-MAC=CM-QOS=1.1;CM-VER=3.1;
    11:04:44
Tue Nov 23 2021
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=CMTS-MAC=;CM-QOS=1.1;CM-VER=3.1;
    11:04:44
Tue Nov 23 2021
  Warning (5)   Dynamic Range Window violation
    11:06:04
Tue Nov 23 2021
  Warning (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;
    11:06:04
Tue Nov 23 2021
  Warning (5)   Dynamic Range Window violation
    11:06:04
Tue Nov 23 2021
  Warning (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;
    11:06:04
Tue Nov 23 2021
  Warning (5)   Dynamic Range Window violation
    11:06:04
Tue Nov 23 2021
  Warning (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;
    11:06:04
Tue Nov 23 2021
  Warning (5)   Dynamic Range Window violation
    11:06:04
Tue Nov 23 2021
  Warning (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;
    11:06:04
Tue Nov 23 2021
  Warning (5)   Dynamic Range Window violation

Visitor

 • 

13 Messages

I am noticing that today I've had a several messages of "Power in Excess of 6 dB Below the Value Corresponding" and "Commanded Power Exceeds Value Corresponding" and "Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value"

Is the ISP sending too much power? Should I slap a splitter into the line? 

EG

Expert

 • 

91.6K Messages

2 m ago

O/k even though the signal stats looked o/k at that snapshot in time, the error log entries and the bit errors confirm that something is going on. Perhaps there is noise ingress into the line(s) somewhere.


There are other signal stat figures 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 that are available to these boards.  They can check the CMTS (Cable Modem Termination System) 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 poll for those upstream receive signal stats.

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

Visitor

 • 

13 Messages

@EG Thank you for your quick responses!

EG

Expert

 • 

91.6K Messages

@user_ef90aa

Quite welcome ! 🙂 

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

 • 

13 Messages

@EG 6 days have passed with no reply from the Comcast corporate employees. Please ping them again. Thank you.

Official Employee

 • 

3.1K Messages

Hello @user_ef90aa!

Thanks for taking the time to reach out to us here on the Xfinity Forums. 

I'm so sorry it's taken us some time to follow up with you on this and I really appreciate you working with @EG in the meantime.

I'd love to take a closer look so we can pinpoint the cause and get this connection issue fixed and get you back to a reliable service! Please send us a Direct Message with your first and last name as well as your service address so we can assist.

To send a Direct Message, please click on the chat icon on the top right of this page, next to the bell. Make sure to send the message to our singular handle "Xfinity Support" and we will get back to you ASAP.

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

 • 

13 Messages

@XfinityTambrey message sent to Xfinity Support. Will keep this forum post open until solution is reached. Thank you.

EG

Expert

 • 

91.6K Messages

2 m ago

Hmmm..... Must have slipped through the cracks. I'll re-escalate it.

Visitor

 • 

13 Messages

@EG how long should I wait before bothering you about this again? Don't want to be annoying, but it is strange that we're at 7 days with no reply from Comcast corporate employees.  Internet is as bad as it was. No change.

Visitor

 • 

13 Messages

2 m ago

Updated values after 7 days up time with no reset.

Startup Sequence    
   Startup Step Status Comment

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



  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 7 days 02h:55m:29s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 17 549.0 6.3 39.3 795 2555
   2 Locked QAM256 1 447.0 5.3 39.8 1020 4063
   3 Locked QAM256 2 453.0 5.7 39.8 1354 5479
   4 Locked QAM256 3 459.0 5.5 39.7 1206 4895
   5 Locked QAM256 4 465.0 6.0 39.8 1195 5034
   6 Locked QAM256 5 471.0 6.1 39.6 1408 5423
   7 Locked QAM256 6 477.0 6.4 39.8 1287 4717
   8 Locked QAM256 7 483.0 6.3 39.7 1206 4904
   9 Locked QAM256 8 489.0 5.6 39.5 1201 5229
   10 Locked QAM256 9 495.0 5.7 39.5 1301 5036
   11 Locked QAM256 10 507.0 5.8 39.5 1160 4568
   12 Locked QAM256 11 513.0 6.0 39.5 1126 4506
   13 Locked QAM256 12 519.0 5.6 39.4 1101 4493
   14 Locked QAM256 13 525.0 5.9 39.4 818 2978
   15 Locked QAM256 14 531.0 5.7 39.3 1114 4232
   16 Locked QAM256 15 537.0 6.2 39.4 1068 4239
   17 Locked QAM256 16 543.0 6.6 39.3 1086 4705
   18 Locked QAM256 18 555.0 5.9 39.2 1057 4014
   19 Locked QAM256 19 561.0 6.2 39.1 1000 3925
   20 Locked QAM256 20 567.0 6.1 39.2 1037 4021
   21 Locked QAM256 21 573.0 6.3 39.4 1035 3959
   22 Locked QAM256 22 579.0 5.9 39.1 1027 3790
   23 Locked QAM256 23 585.0 6.6 39.1 1059 3687
   24 Locked QAM256 24 591.0 7.0 39.2 1028 3753
   25 Locked QAM256 25 597.0 7.5 39.3 933 3272
   26 Locked QAM256 26 603.0 7.9 39.3 966 3330
   27 Locked QAM256 27 609.0 7.6 39.2 1090 3722
   28 Locked QAM256 28 615.0 7.8 39.3 970 3395
   29 Locked QAM256 29 621.0 7.6 39.3 989 3379
   30 Locked QAM256 30 627.0 7.6 39.1 1032 3399
   31 Locked QAM256 31 633.0 7.4 38.7 1137 3180
   32 Locked QAM256 32 639.0 7.7 39.0 1503 4238
   33 Locked OFDM PLC 159 768.0 8.0 38.6 288120332 2924


   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 36.3
   2 Locked SC-QAM 2 5120 29.2 35.5
   3 Locked SC-QAM 3 5120 22.8 35.0
   4 Locked SC-QAM 4 5120 16.4 35.0
   5 Locked SC-QAM 5 1280 39.6 35.5

Visitor

 • 

13 Messages

2 m ago

    Time    Priority    Description 
    10:52:41
Tue Nov 30 2021
  Warning (5)   Dynamic Range Window violation
    10:53:03
Tue Nov 30 2021
  Notice (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=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    10:53:03
Tue Nov 30 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 23; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=0[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    10:53:07
Tue Nov 30 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 0 1.;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:05:51
Tue Nov 30 2021
  Warning (5)   DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:06:01
Tue Nov 30 2021
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:06:05
Tue Nov 30 2021
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:06:05
Tue Nov 30 2021
  Warning (5)   Dynamic Range Window violation
    11:06:11
Tue Nov 30 2021
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:06:23
Tue Nov 30 2021
  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=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:27:17
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:27:18
Tue Nov 30 2021
  Warning (5)   MDD message timeout;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:28:19
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:28:19
Tue Nov 30 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:28:39
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:28:39
Tue Nov 30 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:28:59
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:28:59
Tue Nov 30 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:29:19
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:29:19
Tue Nov 30 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:29:39
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:29:39
Tue Nov 30 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:31:31
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:31:43
Tue Nov 30 2021
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:31:53
Tue Nov 30 2021
  Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    11:32:17
Tue Nov 30 2021
  Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1.;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:32:22
Tue Nov 30 2021
  Warning (5)   REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:32:23
Tue Nov 30 2021
  Warning (5)   RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:32:23
Tue Nov 30 2021
  Warning (5)   Dynamic Range Window violation
    11:44:50
Tue Nov 30 2021
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:44:52
Tue Nov 30 2021
  Warning (5)   DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
    11:45:18
Tue Nov 30 2021
  Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[edited]CMTS-MAC=[edited]CM-QOS=1.1;CM-VER=3.1;
EG

Expert

 • 

91.6K Messages

2 m ago

No prob. It's not bothering me ! I'm not an employee so I have no idea what goes on internally with their company. All I can say is that this isn't typical and usually after a second escalation an employee responds here. I have one other method of escalation that I will try for you.

Visitor

 • 

13 Messages

@EG this is becoming funny, but also frustrating at the same time. I see all these threads with XfinityJohn(Stacey, Steven, Lucy etc.) responding. Yet I'm going past 7 days with nothing. Discrimination?

EG

Expert

 • 

91.6K Messages

How do you figure that it's discrimination ? 

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

 • 

13 Messages

Not in the "generally" accepted way (based on race, ethnicity etc.).  Discrimination in a sense of "I choose to help this forum post, and not that". 

Just chatted with them.  Their solution for now, is a tech visit.  So will keep this post open as unresolved. 

Visitor

 • 

13 Messages

2 m ago

Tech came out today. 

Three issues were discovered.  

1) Comcast was not receiving any information as to the frequencies (on the tech's device status was orange, but should be green).  Solution - replacement of the line going from the pedestal to the house.

2) Upstream power was at the lower end of the acceptable values (33-34).  Although, might not have been an issue, the tech decided that a splitter was a good just in case solution.  So we added a splitter and thus increased the upstream power to be more in the middle of the acceptable ranges (37-38).  Downstream power still good.

3) Voltage spike in and around the modem. Solution - additional ground was placed going from the splitter to the ground on the breaker box.

Will monitor the status and the connection for a few days before coming to a conclusion.  

A few errors in the log are already present (30 min of online time).

   Time    Priority    Description 
    12:49:06
Sat Dec 4 2021
  Warning (5)   MDD message timeout;CM-MAC=(edited)CMTS-MAC=(edited)CM-QOS=1.1;CM-VER=3.1;
    12:49:06
Sat Dec 4 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 33 40 41; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=(edited)CMTS-MAC=(edited)CM-QOS=1.1;CM-VER=3.1;
    12:55:21
Sat Dec 4 2021
  Critical (3)   SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=(edited)CMTS-MAC=(edited)CM-QOS=1.1;CM-VER=3.1;
    12:55:23
Sat Dec 4 2021
  Warning (5)   DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=(edited)CMTS-MAC=(edited)CM-QOS=1.1;CM-VER=3.1;

Official Employee

 • 

477 Messages

Thank you for providing those details. Please keep us posted.

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
EG

Expert

 • 

91.6K Messages

@user_ef90aa

Hope things hold up for you ! Good luck ! 

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

New to the Community?

Start Here