H

Visitor

 • 

4 Messages

Monday, June 7th, 2021 4:10 AM

Closed

Numerous Event Type Code 16 & 24 CM-STATUS Messages DOCSIS 3.1 OFDM PLC

I need a line technician to fix. The issue have been going well over a year now.  I have requested / open tickets Xfinity.

 Motorola Cable Modem MB8600

Connection
   Startup Sequence    
   Startup Step Status Comment

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

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 06h:16m:55s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 17 579.0 -5.0 39.2 0 0
   2 Locked QAM256 2 483.0 -4.7 39.5 15 33
   3 Locked QAM256 3 489.0 -4.7 39.4 9 33
   4 Locked QAM256 4 495.0 -4.8 39.5 10 31
   5 Locked QAM256 5 501.0 -5.0 39.5 0 0
   6 Locked QAM256 6 507.0 -4.9 39.5 0 0
   7 Locked QAM256 7 513.0 -4.8 39.5 0 0
   8 Locked QAM256 8 519.0 -4.8 39.6 1 0
   9 Locked QAM256 9 525.0 -4.7 39.4 0 0
   10 Locked QAM256 10 531.0 -4.8 39.5 0 0
   11 Locked QAM256 11 537.0 -5.1 39.3 0 0
   12 Locked QAM256 12 543.0 -5.2 39.2 1 0
   13 Locked QAM256 13 555.0 -5.4 39.2 0 0
   14 Locked QAM256 14 561.0 -5.5 39.3 0 0
   15 Locked QAM256 15 567.0 -5.5 39.2 0 0
   16 Locked QAM256 16 573.0 -5.1 39.3 0 0
   17 Locked QAM256 18 585.0 -5.0 39.3 0 0
   18 Locked QAM256 19 591.0 -5.1 39.2 0 0
   19 Locked QAM256 20 597.0 -5.2 39.3 0 0
   20 Locked QAM256 21 603.0 -5.4 39.3 0 0
   21 Locked QAM256 22 609.0 -5.3 39.4 0 0
   22 Locked QAM256 23 615.0 -5.5 39.4 0 0
   23 Locked QAM256 24 621.0 -5.4 39.4 0 0
   24 Locked QAM256 25 627.0 -5.5 39.3 0 0
   25 Locked QAM256 26 633.0 -5.2 39.6 0 0
   26 Locked QAM256 27 639.0 -5.2 39.6 0 0
   27 Locked QAM256 28 645.0 -5.0 39.9 0 0
   28 Locked OFDM PLC 29 690.0 -5.4 39.3 537173743 841
   29 Locked QAM256 34 651.0 -5.4 39.7 0 0
   30 Locked QAM256 35 657.0 -5.6 39.7 0 0
   31 Locked QAM256 36 663.0 -5.9 39.6 0 0
   32 Locked QAM256 37 669.0 -5.9 39.5 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 45.3
   2 Locked SC-QAM 2 5120 29.2 44.8
   3 Locked SC-QAM 3 5120 22.8 44.3
   4 Locked SC-QAM 4 5120 16.4 43.0
   5 Locked SC-QAM 9 1280 39.6 46.0


   Downstream Frequency Setting    
   Downstream Frequency Select   
  


   LAG Enable/Disable    
   LAG(Link Aggregation Group, or Ethernet Port Bonding)
  •   Disable
  •   Enable
  •    
  

  

This conversation is no longer open for comments or replies and is no longer visible to community members.

Visitor

 • 

4 Messages

3 years ago

Yesterday I contacted Xfinity to reset the modem due to errors.

Event Log
   Event Log  
  
    Time    Priority    Description 
    10:52:09
Sat May 15 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:54:26
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    11:06:11
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:06:17
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:08:38
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:08:39
Sat May 15 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:08:40
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"]CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:08:40
Sat May 15 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:08:47
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:08:48
Sat May 15 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:09:10
Sat May 15 2021
  Critical (3)   SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    11:09:10
Sat May 15 2021
  Critical (3)   Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    00:01:01
Mon May 17 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    23:07:27
Fri May 28 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    09:02:16
Tue Jun 1 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:50:42
Thu Jun 3 2021
  Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];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=[Edited: "Personal Information"];CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Critical (3)   No Ranging Response received - T3 time-out;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    Time Not Established   Notice (6)   Honoring MDD; IP provisioning mode = IPv6
    16:42:53
Sun Jun 6 2021
  Notice (6)   DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    18:17:36
Sun Jun 6 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    18:18:06
Sun Jun 6 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    19:18:22
Sun Jun 6 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    19:18:53
Sun Jun 6 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    21:17:42
Sun Jun 6 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    21:18:15
Sun Jun 6 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A;

(edited)

Gold Problem Solver

 • 

7.8K Messages

3 years ago

Are you having any problems? I see similar sometimes on my SB8200, but don't notice anything. Your SNR for the OFDM channel is actually very good.

Visitor

 • 

4 Messages

3 years ago

Hello,

Yes, My Motorola Cable Modem MB8600 have to be reset approx. every 5 to 12 days due to the number of corrected and (negative number) uncorrected errors on DOCSIS 3.1 OFDM PLC channel ID 29. Their may be a problem with one or more of the DOCSIS 3.1 profiles.   My cable modem modem will go off the network and I’m unable to login to the web interface GUI (no broadcasting).

I normally contact Xfinity customer service to reset the modem. I’m sure some where the calls to reset the cable Internet service is tracked.

I have had this issue every since DOCSIS 3.1 was installed, switch/equipment.

I did not have this issue with DOCSIS 3.0. Possible faulty equipment switch or noise or split at the central station/hub.

A line technician with access to the switch/node/hub will be able to see, hopefully fix the issue. See notes listed below for a reference.

28 Locked OFDM PLC 29 690.0 -5.6 39.0 1513308887 841
    10:57:06
Mon Jun 7 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;
    10:57:40
Mon Jun 7 2021
  Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 29; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC=[Edited: "Personal Information"];CMTS-MAC=[Edited: "Personal Information"];CM-QOS=1.1;CM-VER=3.1;

(edited)

New Problem Solver

 • 

617 Messages

Hi @hhalljr

Thank you so much for taking the time to reach out! I hate to hear you have been experiencing so many issues with your network connection! As someone who works from home, I know it’s crucial to have a steady connection. Please feel free to send me a Peer to Peer message so that I can gather some account details. I will leave the instructions below. 

 

• Click "Sign In" if necessary

• Click the "Peer to peer chat" icon (upper right corner of this page)

• Click the "New message" (pencil and paper) icon

• Type "Xfinity Support" in the to line and select "Xfinity Support" from the drop-down list

• Type your message in the text area near the bottom of the window

• Press Enter to send your message

I no longer work for Comcast.

Regular Visitor

 • 

4 Messages

@hhalljr were you able to resolve this issue? I'm seeing the same with my newly installed Arris S33.

Expert

 • 

103.5K Messages

@baymax 

Please create a new topic of your own here on this board detailing your issue. Thanks.  The original poster hasn't returned. 5-month-old dead thread now being closed.

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
forum icon

New to the Community?

Start Here