Skip to main content
user_g5ept1
1st Topic

2 Messages

Sunday, November 5th, 2023 12:58 AM

Closed

mb8611 frequently dropping connection. RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW

Lately my mb8611 has frequently been dropping connection multiple times throughout the day. Included are event logs and connection logs

Event Log

Top of Form

   Event Log

 


  

   

Time 

 

Priority 

 

Description 

   

15:28:24
Sat Nov 4 2023

 

Notice (6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

15:28:34
Sat Nov 4 2023

 

Critical (3)

 

UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

15:28:48
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

15:28:48
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

15:28:48
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

15:28:48
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

15:28:48
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

15:28:48
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

15:29:51
Sat Nov 4 2023

 

Notice (6)

 

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

   

15:59:11
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

15:59:11
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

16:36:18
Sat Nov 4 2023

 

Notice (6)

 

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

   

16:36:23
Sat Nov 4 2023

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:36:23
Sat Nov 4 2023

 

Notice (6)

 

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

   

16:36:28
Sat Nov 4 2023

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:36:28
Sat Nov 4 2023

 

Notice (6)

 

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

   

16:36:51
Sat Nov 4 2023

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:37:51
Sat Nov 4 2023

 

Critical (3)

 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:38:02
Sat Nov 4 2023

 

Critical (3)

 

No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:38:35
Sat Nov 4 2023

 

Critical (3)

 

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:05
Sat Nov 4 2023

 

Critical (3)

 

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:06
Sat Nov 4 2023

 

Critical (3)

 

No Ranging Response received - T3 time-out;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:15
Sat Nov 4 2023

 

Notice (6)

 

Honoring MDD; IP provisioning mode = IPv6

   

16:39:24
Sat Nov 4 2023

 

Notice (6)

 

DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:35
Sat Nov 4 2023

 

Critical (3)

 

UCD invalid or channel unusable;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:49
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:49
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

16:39:49
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:49
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

16:39:49
Sat Nov 4 2023

 

Warning (5)

 

RNG-RSP CCAP Commanded Power Exceeds Value Corresponding to the Top of the DRW;CM-MAC=REDACTED;CMTS-MAC=REDACTED;CM-QOS=1.1;CM-VER=3.1;

   

16:39:49
Sat Nov 4 2023

 

Warning (5)

 

Dynamic Range Window violation

   

16:43:56
Sat Nov 4 2023

 

Notice (6)

 

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

Connection
   Startup Sequence    
   Startup Step Status Comment

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

  
   Configuration File OK
  
   Security Enabled BPI+
  


   Connection Status    
   System Up Time 2 days 22h:19m:40s  
  
   Network Access Allowed  
  


   Downstream Bonded Channels  
  
   Channel Lock Status Modulation Channel ID Freq. (MHz) Pwr (dBmV) SNR (dB) Corrected Uncorrected
   1 Locked QAM256 4 435.0 0.5 43.8 21207 13852
   2 Locked QAM256 1 417.0 0.6 44.0 35112 20082
   3 Locked QAM256 2 423.0 0.5 44.0 38375 21145
   4 Locked QAM256 3 429.0 0.6 43.8 39470 22479
   5 Locked QAM256 5 441.0 0.3 43.8 40361 21778
   6 Locked QAM256 6 447.0 0.3 43.9 38517 20509
   7 Locked QAM256 7 453.0 0.3 44.0 37019 19440
   8 Locked QAM256 8 459.0 0.2 43.9 32201 17585
   9 Locked QAM256 9 465.0 0.3 43.8 34059 18276
   10 Locked QAM256 10 471.0 0.2 43.8 37176 18504
   11 Locked QAM256 11 477.0 0.4 43.9 39156 19875
   12 Locked QAM256 12 483.0 0.4 44.1 40174 20923
   13 Locked QAM256 13 489.0 0.4 43.9 23935 14298
   14 Locked QAM256 14 495.0 0.5 44.0 24087 13382
   15 Locked QAM256 15 501.0 0.4 43.8 23033 12753
   16 Locked QAM256 16 507.0 0.4 43.8 23524 12663
   17 Locked QAM256 17 513.0 0.4 43.9 23531 12416
   18 Locked QAM256 18 519.0 0.2 43.7 22620 12142
   19 Locked QAM256 19 525.0 0.2 43.7 22005 11919
   20 Locked QAM256 20 531.0 0.2 43.6 19874 10812
   21 Locked QAM256 21 537.0 0.1 43.5 27671 11710
   22 Locked QAM256 22 543.0 0.1 43.5 29524 12643
   23 Locked QAM256 23 549.0 -0.1 43.4 20255 10483
   24 Locked QAM256 24 555.0 -0.2 43.4 20912 10621
   25 Locked QAM256 25 561.0 -0.1 43.5 19377 9281
   26 Locked QAM256 26 567.0 -0.3 43.2 19651 9029
   27 Locked QAM256 27 573.0 -0.1 43.3 19032 8454
   28 Locked QAM256 28 579.0 -0.1 43.3 18687 8656
   29 Locked QAM256 29 585.0 -0.2 43.2 20357 9361
   30 Locked QAM256 30 591.0 -0.2 43.2 19817 9372
   31 Locked QAM256 31 597.0 -0.2 43.2 22754 9419
   32 Locked QAM256 32 603.0 -0.1 43.2 37305 9183
   33 Locked OFDM PLC 193 957.0 -7.2 40.8 953588629 7532


   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 40.0
   2 Locked SC-QAM 2 5120 22.8 40.0
   3 Locked SC-QAM 3 5120 29.2 40.5
   4 Locked SC-QAM 4 5120 35.6 41.0

 

 

Question

 • 

Updated 

2 years ago

104

2

0

Oldest First
Selected Oldest First
EG

Expert

 • 

117.6K Messages

2 years ago

First. Bear in mind that we have been seeing many posts here in the recent past that may indicate a pattern that the 8611 is currently not playing nicely with the Comcast system / firmware. YMMV.

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.


And there are a fair number of uncorrectable bit errors, but that may not be significant depending on the total uptime of the modem since the last reboot.


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 !

(edited)

0

0

XfinityPeterH

Official Employee

 • 

2.7K Messages

2 years ago

Hi @user_g5ept1 and thanks for your post. We are happy to check your connection. Please send us your full name and complete address. 

(Full credit to @BruceW for this excellent explanation!) 


"Search for Xfinity Support" won't work. To send a "Direct Messaging" message to Xfinity Support:


 • Click "Sign In" if necessary


 • Click the "Direct Messaging" icon or https://forums.xfinity.com/direct-messaging


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


 • The "To:" line prompts you to "Type the name of a person". Instead, type "Xfinity Support" there


 •  - As you are typing a drop-down list appears. Select "Xfinity Support" from that list


 •  - An "Xfinity Support" graphic replaces the "To:" line


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


 • Press Enter to send it


See https://forums.xfinity.com/conversations/email/cant-create-a-new-email-address/605e52b726aa974d63032d02?commentId=606107ea738c7f46a02b830e for an example.

1

0

user_g5ept1

2 Messages

DM sent with name and address. Thank you. 

2 years ago

0

forum icon

New to the Community?

Start Here