Skip to main content

  • Home

  • Getting Started

    • Offers

U
user_get27r
1st Topic
1st Like

7 Messages

Friday, October 4th, 2024 4:15 AM

No Ranging Response Received T3 timeout

I noticed that the lights in my new Arris SB8200 were all green, when the manual says they are supposed to be blue if the modem Is set up as DOCSIS 3.1 (as it should, since it is compatible). Not knowing what I would find I logged into the modem, I see a lot of errors under "Corrected" and "Uncorrectables". I have attached images. Then in the Event log page, I see this error "No ranging response T3 timeout" appear roughly every 2 hours.

Can someone please help!!

I have tried to upload images but I get an error to PLEASE TRY AGAIN. My images are all either TIFF or JPEG and less than 1 MB, so I am not sure why this is happening. 

Question

 • 

Updated 

20 days ago

39

3

0

Was this helpful?

EG

Expert

 • 

106.9K Messages

1 month ago

Copy all of the text of them (instead of using an image) and paste it into your next post here, but you'll need to redact all of the CM MAC and CMTS MAC addresses. The 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 as well.

3

0

user_get27r

7 Messages

Downstream Bonded Channels
Channel ID Lock Status Modulation Frequency Power SNR/MER Corrected Uncorrectables
20 Locked 256QAM 543000000 Hz 8 dBmV 40 dB 0 0
4 Locked 256QAM 447000000 Hz 8 dBmV 40 dB 1321 62
12 Locked 256QAM 495000000 Hz 8 dBmV 40 dB 1354 142
28 Locked 256QAM 591000000 Hz 8 dBmV 40 dB 534 1
1 Locked 256QAM 429000000 Hz 8 dBmV 40 dB 1461 78
2 Locked 256QAM 435000000 Hz 8 dBmV 40 dB 1428 55
3 Locked 256QAM 441000000 Hz 8 dBmV 40 dB 1462 80
5 Locked 256QAM 453000000 Hz 8 dBmV 40 dB 1321 52
6 Locked 256QAM 459000000 Hz 8 dBmV 40 dB 1190 52
7 Locked 256QAM 465000000 Hz 8 dBmV 40 dB 1261 75
8 Locked 256QAM 471000000 Hz 8 dBmV 40 dB 1458 138
9 Locked 256QAM 477000000 Hz 8 dBmV 40 dB 1390 74
10 Locked 256QAM 483000000 Hz 8 dBmV 40 dB 1640 1169
11 Locked 256QAM 489000000 Hz 8 dBmV 40 dB 1437 29
13 Locked 256QAM 501000000 Hz 8 dBmV 40 dB 1234 189
14 Locked 256QAM 507000000 Hz 8 dBmV 40 dB 1207 92
15 Locked 256QAM 513000000 Hz 8 dBmV 40 dB 1197 119
16 Locked 256QAM 519000000 Hz 8 dBmV 40 dB 1134 100
17 Locked 256QAM 525000000 Hz 8 dBmV 40 dB 1047 56
18 Locked 256QAM 531000000 Hz 8 dBmV 40 dB 942 13
19 Locked 256QAM 537000000 Hz 8 dBmV 40 dB 814 6
21 Locked 256QAM 549000000 Hz 8 dBmV 40 dB 883 26
22 Locked 256QAM 555000000 Hz 8 dBmV 40 dB 842 10
23 Locked 256QAM 561000000 Hz 8 dBmV 40 dB 839 14
24 Locked 256QAM 567000000 Hz 8 dBmV 40 dB 804 24
25 Locked 256QAM 573000000 Hz 8 dBmV 40 dB 678 8
26 Locked 256QAM 579000000 Hz 8 dBmV 40 dB 657 12
27 Locked 256QAM 585000000 Hz 8 dBmV 40 dB 641 2
29 Locked 256QAM 597000000 Hz 9 dBmV 40 dB 635 0
30 Locked 256QAM 603000000 Hz 8 dBmV 40 dB 548 4
31 Locked 256QAM 609000000 Hz 8 dBmV 40 dB 564 3
32 Locked 256QAM 615000000 Hz 8 dBmV 40 dB 570 10
193 Locked OFDM PLC 957000000 Hz 6 dBmV 41 dB 639296135 25963



Upstream Bonded Channels
Channel ID Lock Status US Channel Type Frequency Width Power
2 Locked SC-QAM 22800000 Hz 6400000 44.0 dBmV
4 Locked SC-QAM 35600000 Hz 6400000 44.0 dBmV
3 Locked SC-QAM 29200000 Hz 6400000 44.0 dBmV
1 Locked SC-QAM 16400000 Hz 6400000 44.0 dBmV



Current System Time:Fri Oct 4 21:07:55 2024

Date Time Event Level Description
04/10/2024 21:07:53
notice
GUI Login Status - Login Success from LAN interface; client ip=xx.xx.xx.xx;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
04/10/2024 17:08:37
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
03/10/2024 22:39:02
notice
GUI Login Status - Login Success from LAN interface; client ip=[24.129.73.184];CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
03/10/2024 22:08:13
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
03/10/2024 15:28:20
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
03/10/2024 13:23:16
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
03/10/2024 11:14:13
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
03/10/2024 07:54:02
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 4; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
02/10/2024 19:34:13
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
02/10/2024 17:56:00
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 9; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
02/10/2024 15:01:06
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
02/10/2024 13:12:57
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
02/10/2024 09:33:02
notice
DS profile config update. DS Chan ID: 193.;CM-MAC=xxxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
02/10/2024 08:17:14
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 16; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxx;CMTS-MAC=xxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
01/10/2024 20:41:20
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
01/10/2024 14:18:24
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
30/09/2024 10:25:23
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
29/09/2024 20:45:41
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
29/09/2024 17:54:43
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxx;CMTS-MAC=xxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
29/09/2024 17:26:36
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
29/09/2024 10:11:45
notice
DS profile config update. DS Chan ID: 193.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
29/09/2024 08:35:53
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 2.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
29/09/2024 04:18:02
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
28/09/2024 23:37:36
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 13:25:42
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 12:44:58
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 12:20:37
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 11:53:18
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 10:20:55
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 09:59:44
notice
CM-STATUS message sent. Event Type Code: 24; Chan ID: 193; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 08:43:52
critical
No Ranging Response received - T3 time-out;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 08:23:21
notice
CM-STATUS message sent. Event Type Code: 5; Chan ID: 6; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:32:02
notice
REGISTRATION COMPLETE - Waiting for Operational status;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:58
warning
RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:54
critical
Config File Rejected due to Invalid or Unexpected TLV 11;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:54
notice
TLV-11 - unrecognized OID;CM-MAC=xxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:53
warning
MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:53
notice
CMSTATUS:DS_Diplexer_Mode_Change_Ignored:[TLV-84.3], [1002MHZ];CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:53
notice
CMSTATUS:DS_Diplexer_Mode_Change_Ignored:[TLV-84.2], [108MHZ];CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;
27/09/2024 05:31:53
notice
CMSTATUS:US_Diplexer_Mode_Change:[TLV-84.1], [5-42MHZ];CM-MAC=xxxxxxxxxxx;CMTS-MAC=xxxxxxxxxx;CM-QOS=1.1;CM-VER=3.1;



Like

Reply

1 month ago

0

XfinityOrlandoM

Official Employee

 • 

1.4K Messages

@user_get27r

 

Thanks for reaching out to us as a customer who works from home I understand the need to have a strong steady connection. This link https://www.xfinity.com/support/articles/internet-connectivity-troubleshooting has great information on how you can troubleshoot your services via our awesome Xfinity app

 

the app will go through some remote troubleshooting steps to try and solve the issue remotely. If the issue can't be resolved remotely the app will connect you to an awesome Xfinity chat agent to schedule for a technician to come out to survey the home check all the connections and wiring to find and resolve the issue

 

Are there any troubleshooting steps you have taken by making sure all the connections are finger tight rebooting the modem by unplugging the power cord from the back of the motor for 30 seconds also rebooting your Wi-Fi router?

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

Like

Reply

1 month ago

0

user_get27r

7 Messages

I already did the test using the app and it said everything was OK. However I am still getting these error messages from the modem. Also, they are both brand new (less than 3 months old), as my previous setup was over 7 years old and needed a refresh.  have also rebooted my router and the modem. I have done everything I can on my end .

Like

Reply

25 days ago

0

EG

Expert

 • 

106.9K Messages

1 month ago

Everything was within specs at that snapshot in time, but 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 !

(edited)

3

0

user_get27r

7 Messages

Thank you!

I will wait for someone to reach out to help me.

Like

Reply

25 days ago

0

XfinityThomasD

Official Employee

 • 

942 Messages

 

user_get27r When you have a moment, please send our team a direct message with your full name and address. We can definitely look into the signal health and see a bit more on what's going on and where we need to go to get a resolution.

 

To send a Direct Message:

 

Ensure you are logged in

  • 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.

 

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

Like

Reply

23 days ago

0

user_get27r

7 Messages

@XfinityThomasD​ 

thank you. Did as instructed and I am now waiting for a response. 

Like

Reply

23 days ago

0

EG

Expert

 • 

106.9K Messages

23 days ago

@user_get27r @XfinityThomasD 

Please circle back here and post any possible solutions for the issue here in these open public forums so that all readers here may benefit from the exchange / info. This is in keeping with the spirit for which these public help forums were originally intended. Thank you.

3

0

user_get27r

7 Messages

Will do. I am currently waiting on a response by Xfinity Support to see how they can help me. 

Like

Reply

23 days ago

user_get27r

7 Messages

So, the technician just left. Couple of things that they found:

 First, there were 2 signal filters on my line. One at the tap and another one in my condo. So they removed one of them.

 The second issue was that the tech said the signal was “a little high at the tap”. He also indicated that inside my condo someone had installed a splitter, possibly to try to attenuate the signal a bit. He told me that he would be making a report to have another tech come in and fix the signal issue, and that someone would be contacting me to schedule this new appointment. At that point I will probably also tell them to remove the splitter if it is not needed for any other purpose (I don’t have cable tv so I only need one cable line: the one going into my modem).

i will report back when they come to work on my signal issue.

Like

Reply

20 days ago

0

XfinityBenjaminM

Official Employee

 • 

1.5K Messages

 

user_get27r Thank you for the update! We are glad that the technician was able to identify a few things that required some attention and that they're working on the second issue for you as well. We've sent you a DM, please reply to us there if anything further is required.

 

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

Like

Reply

20 days ago

0

forum icon

New to the Community?

Start Here