No Ranging Response received - T3 time-out

[Lexsed]

Hi,

Got this going on for the last month or so, frequent drops, while short, are extremely annoying and frequent. Tried all the troubleshooting I could find here, as well as from 3rd party sources, but no dice, it comes back and goes away randomly

Here are the logs which I assume can help determine the issue:

Date Time Error Number Error Description

08/05/2017	18:35:04 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:35:02 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:33:43 GMT	66050310	Auth Success - Web login successful.
08/05/2017	18:31:26 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:31:00 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:30:59 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:28:35 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:28:09 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:21:56 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:21:55 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:15:53 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:15:45 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:10:56 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:10:40 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:10:10 GMT	84020200	Lost MDD Timeout
08/05/2017	18:08:41 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:08:06 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:07:51 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:07:50 GMT	82000200	No Ranging Response received - T3 time-out
08/05/2017	18:07:46 GMT	82000200	No Ranging Response received - T3 time-out

Downstream Channels

Lock StatusChannel IDFrequencyModulationRx PowerRxMERPre RS ErrorsPost RS ErrorsLocked1171000000 Hz256 QAM-5.6 dBmV 37.1 dB994843745736Locked2179000000 Hz256 QAM-5.7 dBmV 37.6 dB955494700219Locked3187000000 Hz256 QAM-5.6 dBmV 37.6 dB1090159729393Locked4195000000 Hz256 QAM-5.6 dBmV 37.1 dB1309304915025Locked5203000000 Hz256 QAM-5.7 dBmV 37.4 dB1196401796995Locked6211000000 Hz256 QAM-5.9 dBmV 37.4 dB841841575510Locked7219000000 Hz256 QAM-6.0 dBmV 37.4 dB775186506153Locked8227000000 Hz256 QAM-6.0 dBmV 37.6 dB778429499077

Upstream Channels

Lock StatusChannel IDFrequencyModulationTx PowerModeChannel BandwidthSymbol RateLocked7439400000 HzATDMA48.3 dBmV16QAM6400000 Hz5120 Ksym/secNotLocked00 Hz 0 dBmV  0 Ksym/secNotLocked00 Hz 0 dBmV  0 Ksym/secLocked7625800000 HzATDMA46.8 dBmV16QAM6400000 Hz5120 Ksym/sec

[Dave_cq]

Downstream power levels are right at the lower limit of the acceptable range whilst Signal to Noise Ratio appears to be ok ... BUT ... I also notice that both your Upstream channels are on 16QAM instead of the expected 64QAM which may well indicate a noisy connection.   Arranging an engineer's visit to put you on a higher power tapping point in the street cabinet may be a solution.

[Lexsed]

Alright I see. Would calling be the solution then, or waiting for a response here, to avoid explaining the issue again without the convenience of clearly presented logs?

[DaveM]

Forum staff will get to you but it can take up to week.

Dave.

[Samantha_L · Accepted solution]

Hi Lexsed,

Welcome to the community and thanks for posting.

I'm sorry to read you are experiencing intermittent broadband connection. I can imagine how annoying this must be.

Looking at your connection, the downstream power levels are on the low side as Dave_cq mentioned. There is also a high amount of T3 time-outs reported within a short space of time. As there are no issues on the network I would like to book an engineer to check this over. I've sent you a PM (purple envelope icon, right corner) with some details for you to confirm please.

Hope to hear from you soon

Sam

[hamtrektng]

Recently been getting on mine too.

Note in log:

T3 Timeout errors: 35

DownloadStream Power is above 2.0dbmV
Downstream Channel ID: 9

Upstream Power is above 50.0dbmV (as of 10.14am)
Upstream Channel ID: 79

Any ideas?

[hamtrektng]

As of today, the issue has been resolved. Will monitor for a few more days for further critical errors.

[Heather_J]

Hello hamtrektng, 

Thanks for the update 🙂

Good to hear you've noticed an improvement. 

Let us know if you need help with anything else at the moment. 

Take care.

[Adduxi]

---

@Dave_cqwrote:

Downstream power levels are right at the lower limit of the acceptable range whilst Signal to Noise Ratio appears to be ok ... BUT ... I also notice that both your Upstream channels are on 16QAM instead of the expected 64QAM which may well indicate a noisy connection.   Arranging an engineer's visit to put you on a higher power tapping point in the street cabinet may be a solution.

---

I've been on 16QAM for as long as I can remember without issue. 

Yes, it can indicate a problem if you dropped from 64 to 16, however being on 16 already, it's not always the case.  

[pc2018]

Hi,

I am getting the same problem , connection drops off , then comes back on 5-10 minutes later , logs are below

Date And Time Error Number Event Description

2018-05-20 10:47:34.00	84000700	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 10:47:38.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 10:47:38.00	84000700	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 10:47:49.00	84020200	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:13:33.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:14:52.00	82000300	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:14:52.00	82000600	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:15:16.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:47:25.00	82000300	Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:47:25.00	82000600	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 11:47:49.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 12:10:08.00	84000700	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 12:35:29.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 12:43:45.00	84000700	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 13:40:13.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 19:01:00.00	84020200	Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 20:17:14.00	84000700	RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 21:34:33.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 21:38:51.00	82000400	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2018-05-20 21:39:41.00	82000200	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Channel Frequency(Hz) Power(dBmV) SNR(dB) Modulation Channel ID

1	299000000	2.7	37.6	256 qam	21
2	323000000	1.5	37.3	256 qam	24
3	315000000	2.2	38.6	256 qam	23
4	307000000	2.5	38.6	256 qam	22
5	291000000	2.9	37.6	256 qam	20
6	283000000	3	38.6	256 qam	19
7	275000000	3.2	38.9	256 qam	18
8	267000000	3.2	38.6	256 qam	17
9	259000000	3.7	38.6	256 qam	16
10	251000000	3.5	38.6	256 qam	15
11	243000000	4	38.6	256 qam	14
12	235000000	4	38.6	256 qam	13
13	227000000	4.3	37.6	256 qam	12
14	219000000	4.4	38.6	256 qam	11
15	211000000	4.9	38.6	256 qam	10
16	203000000	4.6	38.9	256 qam	9
17	195000000	5	38.6	256 qam	8
18	187000000	5.5	38.9	256 qam	7
19	179000000	5.3	38.6	256 qam	6
20	171000000	5.6	38.6	256 qam	5
21	163000000	5.6	38.9	256 qam	4
22	155000000	5.6	37.6	256 qam	3
23	147000000	5.8	37.6	256 qam	2
24	139000000	6.1	37.6	256 qam	1

Upstream bonded channelsChannel ID Frequency(Hz) Mode Power(dBmV) Modulation Channel Bandwidth(Hz) Symbol Rate (ksps)

51	24400000	ATDMA	46.5	16 qam	6400000	5120
49	37600000	ATDMA	46.5	16 qam	6400000	5120