Skip to main content

  • Home

  • Getting Started

    • Offers

user_36883e's profile
user_36883e
1st Topic
1st Reply
1st Like

Visitor

 • 

8 Messages

Tuesday, January 31st, 2023 7:14 PM

Closed

MB8611: SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing

Motorola MB8611 randomly dropping internet. In checking the event log there are three issues that remain constant.

1) Critical: SYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;

2) Critical: No Ranging Response received - T3 time-out

3) Warning: MDD message timeout


Xfinity providing 500mbs cable internet connection

The home has cable outside cable running in from original 1994 construction. 
Currently running Xfinity cable directly into house line for MB8611

No splitters on my end- only the Grounding Block connection

MB 8611 feeds into EERO 6+ router

VPN is disabled

For in-house trouble shooting, I have replace the Cat 5 cabling and rebooted the MB8611 Modem several times. Event logs and connectivity reports available on request.

Question

 • 

Updated 

2 years ago

539

6

0

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

Was this helpful?

BruceW

Gold Problem Solver

 • 

26.1K Messages

2 years ago

... MB8611 randomly dropping internet ...

Please post following information from your modem:

  • downstream: power levels, SNR, error counts, and uptime
  • upstream: power levels
  • event log (Be sure to remove or blot out any MAC addresses. Forum security processing considers them "personal information" and may prevent the event log from posting if these are present.)
Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

0

user_36883e

Visitor

 • 

8 Messages

2 years ago

Hi Bruce, 

Here is the current connection data….

Event log to follow

Connection
   Startup Sequence    
   Startup Step Status Comment

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

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 05h:06m:45s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 20 513.0 3.5 41.8 0 0
   2 Locked QAM256 4 417.0 3.8 42.0 0 0
   3 Locked QAM256 5 423.0 3.7 42.0 0 0
   4 Locked QAM256 6 429.0 3.7 41.9 0 0
   5 Locked QAM256 7 435.0 3.6 41.9 0 0
   6 Locked QAM256 8 441.0 3.6 41.9 0 0
   7 Locked QAM256 9 447.0 3.5 41.9 0 0
   8 Locked QAM256 10 453.0 3.5 41.8 0 0
   9 Locked QAM256 11 459.0 3.5 41.7 0 0
   10 Locked QAM256 12 465.0 3.5 41.8 0 0
   11 Locked QAM256 13 471.0 3.6 41.9 0 0
   12 Locked QAM256 14 477.0 3.4 41.8 0 0
   13 Locked QAM256 15 483.0 3.3 41.8 0 0
   14 Locked QAM256 16 489.0 3.1 41.6 0 0
   15 Locked QAM256 17 495.0 3.2 41.7 0 0
   16 Locked QAM256 18 501.0 3.3 41.7 0 0
   17 Locked QAM256 19 507.0 3.4 41.7 0 0
   18 Locked QAM256 21 519.0 3.6 41.7 0 0
   19 Locked QAM256 22 525.0 3.6 41.7 0 0
   20 Locked QAM256 23 531.0 3.6 41.7 0 0
   21 Locked QAM256 24 537.0 3.7 41.6 0 0
   22 Locked QAM256 25 543.0 3.9 41.6 0 0
   23 Locked QAM256 26 549.0 4.0 41.6 0 0
   24 Locked QAM256 27 555.0 4.2 41.7 0 0
   25 Locked QAM256 28 561.0 4.2 41.7 0 0
   26 Locked QAM256 29 567.0 4.4 41.6 0 0
   27 Locked QAM256 30 573.0 4.5 41.5 0 0
   28 Locked QAM256 31 579.0 4.6 41.6 0 0
   29 Locked QAM256 32 585.0 4.7 41.6 0 0
   30 Locked QAM256 33 591.0 4.7 41.4 0 0
   31 Locked QAM256 34 597.0 4.8 41.5 0 0
   32 Locked OFDM PLC 48 722.0 6.6 39.5 313266583 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 16.4 36.3
   2 Locked SC-QAM 2 5120 22.8 37.0
   3 Locked SC-QAM 3 5120 29.2 37.5
   4 Locked SC-QAM 4 5120 35.6 37.5

0

0

user_36883e

Visitor

 • 

8 Messages

2 years ago

And the infamous event log….

Event Log
   Event Log  
  
    Time    Priority    Description 
    11:39:52
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM-CMTS-CM-QOS=1.1;CM-VER=3.1;
    11:39:57
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;
    11:40:17
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-
    11:42:25
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM-
    11:42:26
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA 
    11:42:40
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    12:44:49
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 2; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    12:44:50
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM-
    12:44:54
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A;
    12:45:21
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    12:56:54
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 2; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    12:56:57
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM
    12:56:58
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    12:57:13
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:01:07
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 2; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:01:10
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM
    13:01:13
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:01:15
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    13:01:50
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 2; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:01:50
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM
    13:01:51
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:02:20
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:07:43
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 2; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:07:44
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM
    13:07:47
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:07:53
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:10:11
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM
    13:10:12
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:10:29
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:11:48
Tue Jan 31 2023		   Warning (5)   MDD message timeout;CM
    13:11:53
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
    13:12:02
Tue Jan 31 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM
 
 
   
 

0

0

BruceW

Gold Problem Solver

 • 

26.1K Messages

2 years ago

Power levels and SNR values look good, but there are other values that modems do not report, and the event log suggests there is a problem communicating with Comcast's network. A lot problems with the 8611 have been reported in the Forums over the past few weeks (see https://forums.xfinity.com/conversations/search?sortKey=RECENT&q=MB8611). Neither Motorola nor Comcast seem to be doing much about it.

Just to be thorough, if you want to troubleshoot this yourself, please see Internet Troubleshooting Tips. If you can't find the problem or you'd rather have Comcast take care of it, call them at the phone number on your bill or 1-800-Comcast, or use one of the options on https://www.xfinity.com/support/contact-us/. It's not likely they can fix the problem remotely. If not, insist they send a tech out to identify the cause and correct it.

If the tech finds bad coax, splitters, amplifiers, or connections in your home (even if Comcast originally supplied them) you'll probably have to pay for the visit ($70-$100) unless you have their Service Protection Plan ( https://www.xfinity.com/support/articles/service-protection-plan, closed to customers that don't already have it). If the trouble is due to a faulty Comcast rental device or anything outside your home you shouldn't be charged.

Wish I had better news for you . . .

Please be aware that there are 2 kinds of responses in this Forum: Replies and Comments. When you Comment on a post by scrolling down to "Comment on this post here...", I am notified of your response. But if you select Reply, I am NOT notified and may not be aware of your response.

(edited)

0

0

user_36883e

Visitor

 • 

8 Messages

2 years ago

Thank you Bruce, appreciate your time and insights. 
We will follow your suggestions and see where this leads.

1

user_36883e

Visitor

 • 

8 Messages

2 years ago

In following Bruce's suggestions, I have contacted Motorola Customer Support. 

The Rep at Motorola acknowledged that there appears to be some software glitch between Comcast and Motorola involving the 9.21.3 software patch.

As a result:

1) Motorola is working through a software fix that should be sent down through Comcast some time in February 2023

2) Motorola will replace my existing MB8611 Cable Modem with a new unit- though the firmware and components appear to be the same as my original unit.

As this time, request this Community Note remain open as the original issue still remains and the replacement modem has not been received or installed. I will post the final Connection and Event logs showing the updated system status at that time.

Onwards- JB

5

0

user_db1346

Contributor

 • 

34 Messages

@user_36883e​ Good to hear other people are getting different answers. What I got from Motorola is this

"The update is not just firmware, I have mentioned the update several times but at no point did I state it was just a firmware change. The update is several things including changes on their networks back end. I cannot say anymore in regards to the changes they are making sir as it is outside of our ability to speak on. 

The firmware itself is going to be 8611-19.2.18, however there is a chance that you have been put on that firmware and they just havent made whatever changes they need to make on the back end. I cannot say for certain as Comcast does not provide that level of information to outside sources. We as a company have done everything on our side that Comcast needed including providing data and working with them to get to a resolution."

2 years ago

0

user_db1346

Contributor

 • 

34 Messages

@user_36883e​ Also don't let them try to make you pay for the return. They will begrudgingly give you a shipping label if you just stand your ground.

2 years ago

0

user_36883e

Visitor

 • 

8 Messages

Rats! missed your suggestion to request the Motorola RMA Return shipping label. 

However, will post updated modem logs shortly...

2 years ago

0

user_36883e

Visitor

 • 

8 Messages

Received and installed the new Motorola MB8611 Modem yesterday (14 Feb 2023). So far internet connection is steady with the new system running 19.2.18 software. However, the new MB8611 is showing a high number of Corrected/Uncorrected data sends. This may be related to the repeated Critical and Warning entries in the Event Log further below. Suspect the Xfinity internet connection is sub-par, perhaps a coaxial of local area junction issue. 

Updated MB8611 Basic Status and Settings
   Internet Connection    
   Online Connected
  
   Number of Channels Connected



  
         Downstream 32
         Upstream 4


  New MB8611 Cable Modem Version    
   MAC Address
  
   Software Version 8611-19.2.18

New MB8611 Connection Log
   Startup Sequence    
   Startup Step Status Comment

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

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 0 days 17h:53m:38s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 4 417.0 5.4 42.0 30007 33583
   2 Locked QAM256 5 423.0 5.1 42.0 31759 36353
   3 Locked QAM256 6 429.0 5.2 41.8 30199 33671
   4 Locked QAM256 7 435.0 5.0 41.7 28217 30292
   5 Locked QAM256 8 441.0 5.0 41.8 28809 30339
   6 Locked QAM256 9 447.0 5.0 41.8 27262 28555
   7 Locked QAM256 10 453.0 4.9 41.6 26451 26669
   8 Locked QAM256 11 459.0 4.9 41.6 26239 25158
   9 Locked QAM256 12 465.0 4.9 41.8 26080 24878
   10 Locked QAM256 13 471.0 5.0 41.8 25623 24319
   11 Locked QAM256 14 477.0 4.8 41.7 25032 24235
   12 Locked QAM256 15 483.0 4.7 41.6 24821 24083
   13 Locked QAM256 16 489.0 4.5 41.5 25020 23211
   14 Locked QAM256 17 495.0 4.5 41.5 24725 23022
   15 Locked QAM256 18 501.0 4.6 41.5 24251 23091
   16 Locked QAM256 19 507.0 4.7 41.6 23934 21081
   17 Locked QAM256 20 513.0 4.7 41.5 23738 20169
   18 Locked QAM256 21 519.0 4.9 41.6 23489 19306
   19 Locked QAM256 22 525.0 4.9 41.6 23074 19082
   20 Locked QAM256 23 531.0 5.0 41.6 23127 18504
   21 Locked QAM256 24 537.0 5.0 41.3 23169 18432
   22 Locked QAM256 25 543.0 5.3 41.7 22435 17857
   23 Locked QAM256 26 549.0 5.4 41.5 22675 18116
   24 Locked QAM256 27 555.0 5.6 41.6 22696 18074
   25 Locked QAM256 28 561.0 5.7 41.4 22081 17883
   26 Locked QAM256 29 567.0 5.9 41.4 21735 16604
   27 Locked QAM256 30 573.0 6.1 41.5 21643 16194
   28 Locked QAM256 31 579.0 6.2 41.5 21589 15723
   29 Locked QAM256 32 585.0 6.3 41.5 21094 15614
   30 Locked QAM256 33 591.0 6.3 41.5 20772 14606
   31 Locked QAM256 34 597.0 6.4 41.5 20127 14137
   32 Locked OFDM PLC 48 722.0 8.5 39.8 1558811771 5962


   Upstream Bonded Channels  
  
   Channel Lock Status Channel Type Channel ID Symb. Rate (Ksym/sec) Freq. (MHz) Pwr (dBmV)
   1 Locked SC-QAM 1 5120 16.4 36.5
   2 Locked SC-QAM 2 5120 22.8 37.0
   3 Locked SC-QAM 3 5120 29.2 37.8
   4 Locked SC-QAM 4 5120 35.6 37.8


   Downstream Frequency Setting    
   Downstream Frequency Select   
  

-----------------------------------------------------------------------------------------------------------------------------------

New MB8611 Event Log
   Event Log  
  
    Time    Priority    Description 
    12:46:32
Wed Feb 15 2023		   Warning (5)   MDD message timeout;
    12:46:37
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    12:46:56
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    12:52:13
Wed Feb 15 2023		   Warning (5)   MDD message timeout;CM-MAC
    12:52:14
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    12:52:21
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 1; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    12:52:24
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 4; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    12:52:24
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 5; Chan ID: 7; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC
    13:08:36
Wed Feb 15 2023		   Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC
    13:08:36
Wed Feb 15 2023		   Warning (5)   Dynamic Range Window violation
    13:08:36
Wed Feb 15 2023		   Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC
    13:08:36
Wed Feb 15 2023		   Warning (5)   Dynamic Range Window violation
    13:08:36
Wed Feb 15 2023		   Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC
    13:08:36
Wed Feb 15 2023		   Warning (5)   Dynamic Range Window violation
    13:08:36
Wed Feb 15 2023		   Warning (5)   RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW
    13:08:36
Wed Feb 15 2023		   Warning (5)   Dynamic Range Window violation
    13:08:48
Wed Feb 15 2023		   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC
    13:09:12
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC
    13:10:21
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC
    13:11:48
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC
    13:11:50
Wed Feb 15 2023		   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC
    13:12:04
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC
    13:12:32
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC
    13:12:54
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 3.;
    13:13:20
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC
    13:13:22
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC
    13:13:30
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC
    13:13:32
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1
    13:13:35
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2 3.;CM-MAC
    13:13:40
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 16; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC
    13:13:59
Wed Feb 15 2023		   Critical (3)   Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC
    13:14:37
Wed Feb 15 2023		   Notice (6)   CM-STATUS message sent. Event Type Code: 24; Chan ID: 48; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1 2 3.;CM-MAC

2 years ago

0

EG

Expert

 • 

107.6K Messages

@user_3cb19e 

Please redact all of the CM MAC and the CMTS MAC addresses from your error log entries for your privacy. They are considered to be personal information. The posting of personally identifiable information is a violation of their forum guidelines. The forum bot will not allow your post to be seen publically. It flagged your post as "Private".

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

2 years ago

0

forum icon

New to the Community?

Start Here