No Ranging Response received T3 timeout

[stujwallace]

Hi Community,

I've been having issues recently with "No Ranging Response received - T3 time-out"'.
My internet connection drops almost every day.
I have a VM Hub 3.0 which is operating in 'modem mode'.
When the internet connection drops, modem reboots and internet access is then restored.
No reported faults in my post code.
I've directly paste the network logs as plain text below.

Please let me know whether I should provide anything more from my side.
Thanks

Stuart


Network Log
Time Priority Description
05/08/2023 08:39:37 notice LAN login Success;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
03/08/2023 22:38:26 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
31/07/2023 00:43:25 Error DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
30/07/2023 02:27:19 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:43:28 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:11:24 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:07:38 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:07:38 critical Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:06:54 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 16:53:35 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 13:07:46 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 12:59:14 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 12:41:58 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 12:03:43 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:59:58 critical Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:59:58 critical Ranging Request Retries exhausted;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:59:14 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:48:15 Warning! RCS Partial Service;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:38:2 critical Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:34:2 critical No Ranging Response received - T3 time-out;CM-MAC=xx:xx:xx:xx:xx:xx;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;

[Adduxi]

Try checking with Area faults on 0800 561 0061 or if you have a VM landline 150 as small local faults are not listed on the VM status page.

Post the power levels, Pre and PostRS errors from the Hub. Also setup a BQM to monitor your circuit www.thinkbroadband.com/ping

Once done we can comment.

[stujwallace]

Hi,

I've checked the local area status and there are no reported issues.

Here are the Pre and PostRS numbers

I setup a BQM for monitoring, but that was only started from this morning, so not a great deal to see there at the moment.

[jbrennand]

What make model of router are you using ?

Post more data....

Just copy/paste the normal “Formatted Text” (not images) of 3 FULL sets of data onto here – 2 tables from the Downstream, 2 from the Upstream, & the Network Logs pages. Don't worry too much about the formatting it can be easily read & DON’T include personal data or MAC addresses - blank them out - if you copy/paste the data, the board software will do this for you (you may need to click the "submit" button again). If character limits are “exceeded” - just do two posts

[stujwallace]

Downstream bonded channels

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

1	259000000	6.1	38	256 qam	16
2	251000000	6	38	256 qam	15
3	267000000	6.1	38	256 qam	17
4	275000000	6.1	38	256 qam	18
5	283000000	6.1	40	256 qam	19
6	291000000	6.1	38	256 qam	20
7	299000000	6.4	38	256 qam	21
8	307000000	6.1	40	256 qam	22
9	315000000	6	38	256 qam	23
10	323000000	6	38	256 qam	24
11	331000000	5.9	38	256 qam	25
12	339000000	5.8	38	256 qam	26
13	347000000	5.4	38	256 qam	27
14	355000000	4.9	38	256 qam	28
15	363000000	4.9	38	256 qam	29
16	371000000	5	38	256 qam	30
17	379000000	5	38	256 qam	31
18	387000000	4.8	38	256 qam	32
19	395000000	4.9	38	256 qam	33
20	403000000	4.8	38	256 qam	34
21	411000000	4.9	38	256 qam	35
22	419000000	4.5	38	256 qam	36
23	523000000	3	38	256 qam	37
24	531000000	2.7	38	256 qam	38

Downstream bonded channels

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

1	Locked	38.9	13	0
2	Locked	38.9	11	0
3	Locked	38.9	9	0
4	Locked	38.9	9	0
5	Locked	40.3	12	0
6	Locked	38.9	9	0
7	Locked	38.9	12	0
8	Locked	40.3	10	0
9	Locked	38.9	10	0
10	Locked	38.9	16	0
11	Locked	38.9	12	0
12	Locked	38.9	12	0
13	Locked	38.9	16	0
14	Locked	38.9	29	0
15	Locked	38.6	24	0
16	Locked	38.6	21	0
17	Locked	38.6	15	0
18	Locked	38.6	10	0
19	Locked	38.9	8	0
20	Locked	38.9	8	0
21	Locked	38.6	17	0
22	Locked	38.6	4	0
23	Locked	38.6	12	0
24	Locked	38.6	11	0

Upstream bonded channels

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

1	36599854	36.3	5120	64 qam	3
2	30099986	35.8	5120	64 qam	4
3	43100000	36.3	5120	64 qam	2
4	49600000	36.8	5120	64 qam	1
5	23599903	35.5	5120	64 qam	9

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

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

[stujwallace]

Network Log

Time	Priority	Description
05/08/2023 12:31:12	notice	LAN login Success;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:48	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
05/08/2023 08:39:37	notice	LAN login Success;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
03/08/2023 22:38:26	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
31/07/2023 00:43:25	Error	DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
30/07/2023 02:27:19	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:43:28	Warning!	RCS Partial Service;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:11:24	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:07:38	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:07:38	critical	Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
28/07/2023 07:06:54	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 16:53:35	Warning!	RCS Partial Service;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 13:07:46	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 12:59:14	Warning!	RCS Partial Service;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 12:41:58	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 12:03:43	critical	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:59:58	critical	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:59:58	critical	Ranging Request Retries exhausted;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:59:14	critical	No Ranging Response received - T3 time-out;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;
26/07/2023 11:48:15	Warning!	RCS Partial Service;CM-MAC=XX:XX:XX:XX:XX:XX;CMTS-MAC=XX:XX:XX:XX:XX:XX;CM-QOS=1.1;CM-VER=3.0;

My Virgin Media router is a Hub 3.0.
It's in modem mode connected to a TP-Link AX3000.

[jbrennand]

Nothing amiss in the Hub stats.  Lets see how the BQM develops.

What devices do you have connected to the TP-Link on ethernet cables? And do these have the same issues as wifi connected ones ?

Are these good quality Cat6a spec. cables?

[stujwallace]

Thanks for your feedback.

My TP-Link has x 5 ports.
1 port connected to the VM 3.0 hub
1 connected to a mini PC
1 connected to my work laptop
1 connected to a Siemens Gigaset VOIP box
1 connected to a Synology NAS box

Most outages occur during the week while I was using my broadband for work.
Last week, I was only using the Wifi for work and didn't experience any outages.
I can by all means swap out any patch leads for new ones.
I'll keep the BQM collecting data and see what happens.

[jbrennand · Accepted solution]

If it turns out that there is no issue on the VM connection or Hub - but the BQM is suggesting there are issues then I think you should consider doing the below..

Or customise it by removing your Router and restoring the Hub to router mode first and see if that fixes it

____________

There is one other option, there have been several threads on here recently where similar BQM latency/packet loss problems were eventually pinned down to a dodgy piece of connected kit affecting the connection . Bad connectors on ethernet cables and faulty network switches being high on the list of suspects

What I advised was... if you run the BQM for 24h to get a picture of the issues and then unplug all the ethernet cable connections from the Hub and just let it run - overnight is best - then in the morning look at the BQM and see if it has cleaned up. If it has - plug the devices back in one at a time for an hour or two until the problem reappears and that should indicate where to look for what is causing the issues

Examples of this,.........
See message 21 in the first thread - and 13 in the second.
https://community.virginmedia.com/t5/Networking-and-WiFi/Internet-connection-dropping/td-p/4781287/p...
https://community.virginmedia.com/t5/Networking-and-WiFi/Intermittent-Connection/td-p/5069984/page/2

The ‘Block fragmented IP packets’ box in Firewall settings cured the Hub5 drop outs

See message 10

https://community.virginmedia.com/t5/QuickStart-set-up-and/Hub-5-broadband-dropping-regularly/td-p/5...

_________

[stujwallace]

Thanks John.
I've had issues with my broadband connection dropping before I ever bought the TP-Link box.
Disconnecting the 'connected devices' / systematically re-connecting is probably worth looking at. 
I'll carry out that action plan next week and update this thread with my findings.

I'm not averse to missing out the TP-Link and sticking the VM Hub back in router mode, but I think I'll do that last.
The reason I bought the TP-Link was to improve connections for Wi-Fi devices.
If it's maybe a wired device causing the issues, I've no probelm taking the TP-Link out of the equation.