No Ranging Response received - T3 time-out keep disconnecting

[ahrualove]

i keep having short connections and disconnections daily, I thought to check the logs and found this

04/05/2022 06:56:30	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
04/05/2022 04:22:57	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 21:09:35	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 16:13:26	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 12:56:50	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 12:56:50	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/05/2022 10:58:53	notice	LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 14:48:47	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 00:56:50	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/04/2022 00:56:50	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/04/2022 21:12:23	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/04/2022 04:23:55	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/04/2022 04:23:55	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/04/2022 00:18:31	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
25/04/2022 00:15:27	notice	SW download Successful - Via NMS
25/04/2022 00:12:54	notice	SW Download INIT - Via NMS
23/04/2022 19:17:4	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/04/2022 08:29:40	notice	DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/04/2022 08:29:40	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2022 03:16:29	critical	No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

[Andrew-G]

A few T3 errors are very common, and not an obvious sign of trouble.  Go back to where you found the Network log, and post the Downstream and Upstream data - could be a noise or power problem.

[ahrualove]

is this what you are looking for?

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

1	331000000	3.9	40	256 qam	25
2	267000000	3.5	40	256 qam	17
3	275000000	3.4	40	256 qam	18
4	283000000	3.4	40	256 qam	19
5	291000000	3.7	40	256 qam	20
6	299000000	3.7	40	256 qam	21
7	307000000	3.5	40	256 qam	22
8	315000000	3.9	40	256 qam	23
9	323000000	3.5	40	256 qam	24
10	339000000	3.7	40	256 qam	26
11	347000000	3.2	40	256 qam	27
12	355000000	3.2	40	256 qam	28
13	363000000	3	40	256 qam	29
14	371000000	2.7	40	256 qam	30
15	379000000	3	40	256 qam	31
16	387000000	2.7	40	256 qam	32
17	395000000	2.9	40	256 qam	33
18	403000000	3.2	40	256 qam	34
19	411000000	2.7	40	256 qam	35
20	419000000	3	41	256 qam	36
21	427000000	3.2	40	256 qam	37
22	435000000	2.7	40	256 qam	38
23	443000000	3.2	40	256 qam	39
24	451000000	3	40	256 qam	40

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1	Locked	40.3	124	0
2	Locked	40.3	88	0
3	Locked	40.9	93	0
4	Locked	40.9	80	0
5	Locked	40.9	78	0
6	Locked	40.3	89	0
7	Locked	40.9	96	0
8	Locked	40.3	105	0
9	Locked	40.9	73	0
10	Locked	40.3	133	0
11	Locked	40.3	107	0
12	Locked	40.9	104	0
13	Locked	40.9	85	0
14	Locked	40.3	179	0
15	Locked	40.3	133	0
16	Locked	40.9	93	0
17	Locked	40.9	137	0
18	Locked	40.9	113	0
19	Locked	40.9	130	0
20	Locked	41.6	95	0
21	Locked	40.9	110	0
22	Locked	40.3	168	0
23	Locked	40.9	121	0
24	Locked	40.3	102	0

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1	60300000	46.8	5120	64 qam	9
2	39400000	45.3	5120	64 qam	12
3	46200000	45.3	5120	64 qam	11
4	53700029	46.8	5120	64 qam	10

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	2	0
2	ATDMA	0	0	4	0
3	ATDMA	0	0	4	0
4	ATDMA	0	0	5	0

[Andrew-G]

It is.  When was the hub last rebooted?  Asking because that's when the error count is from, and the upstream timeout count might be high  There's sometimes no obvious link between t3 reports in the log and upstream t3 eror counts.

[ahrualove]

If I'm honest I don't remember if have rebooted it within the last week but I certainly did the week before last. but the main reason I was looking was the fact that I kept having random disconnects on even while ethernet they weren't long but like 10-30 seconds
.

[Martin_N]

Hi ahrualove,

Thank you for your post and welcome to the community. 

I'm very sorry for any issues you're having with your Broadband service. 

I have taken a look on our system and I have been unable to locate anything that could be affecting this. 

Can you confirm if you are still having these issues?

^Martin