Menu
Reply
richardW67
  • 8
  • 0
  • 0
Joining in
767 Views
Message 1 of 17
Flag for a moderator

No Ranging Response received - T3 time-out

Checking through the log, this message appears many times. I have loads of trouble with getting devices to stay connected. The wifi is dropping off all the time and we have to reconnect. I used to have no issues at all and had a really stable connection but the last 4 months have been awful. VM have been next to useless and suggested that we need boosters. I have an M600 line and this drop off happens when you are literally sitting on the router.

I have seen responses on various threads that VM can make adjustments in the cabinets. I have checked all the cables and rebooted 1000 times. The only option is to cancel my contract if this cannot be resolved

 

10/06/2021 11:02:45criticalNo Ranging Response received - T3 time-out;CM-M
10/06/2021 01:56:37criticalNo Ranging Response received - T3 time-out;CM-
09/06/2021 20:44:27criticalNo Ranging Response received - T3 time-out;CM-
08/06/2021 23:17:50criticalNo Ranging Response received - T3 time-out;CM-
06/06/2021 15:48:8criticalNo Ranging Response received - T3 time-out;CM-
06/06/2021 15:40:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-
03/06/2021 22:24:23criticalNo Ranging Response received - T3 time-out;CM-
03/06/2021 03:40:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-VER=3.0;
31/05/2021 07:14:44criticalNo Ranging Response received - T3 time-out;CM-
30/05/2021 15:40:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-
28/05/2021 10:00:41criticalNo Ranging Response received - T3 time-out;CM-
0 Kudos
Reply
Pars
  • 140
  • 20
  • 29
Superfast
751 Views
Message 2 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

I'm not sure it's critical in itself.
I get the T3 timeout appearing regularly too and that's on a 100% fibre installation.
There has never been a dropout or speed issue.
M350 over FTTP
0 Kudos
Reply
richardW67
  • 8
  • 0
  • 0
Joining in
744 Views
Message 3 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thanks for the reply. All ii know is the connections keep dropping and i'd like an engineer to survey and test. Something has changed in the last 4 months whereas we i had a permanent connection and no dropouts

0 Kudos
Reply
Andrew-G
  • 9.5K
  • 1.53K
  • 4.53K
Very Insightful Person
Very Insightful Person
736 Views
Message 4 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

T3 timeouts often appear as momentary disconnections, although depending what you're doing and when they occur they may not be noticed.

I'd suggest you go back to where you got the network log, find the other tabs titled Downstream and Upstream, and copy and paste all the data for each of those two.  That'll enable us to look for noise or power level faults.

I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more

Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks

0 Kudos
Reply
chaoshusky
  • 68
  • 5
  • 8
Dialled in
695 Views
Message 5 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

As Andrew has said, please get the information logs from your Router, usually via 192.168.0.1 in your browser, post the contents of all the tabs here so we can take a look. Could you possibly do that for us?

Kind regards,

Lee

0 Kudos
Reply
richardW67
  • 8
  • 0
  • 0
Joining in
663 Views
Message 6 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Not sure if this is what you need but these are all the log files I can find

Thanks for you assistance

Richard

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

11787500003.439256 qam6
21387500002.238256 qam1
31467500002.540256 qam2
41547500002.740256 qam3
51627500002.940256 qam4
6170750000340256 qam5
71867500003.538256 qam7
81947500003.438256 qam8
92027500003.440256 qam9
102107500003.440256 qam10
112187500003.540256 qam11
122267500003.540256 qam12
132347500003.240256 qam13
142427500002.940256 qam14
152507500002.540256 qam15
162587500002.740256 qam16
172667500002.240256 qam17
182747500002.240256 qam18
192827500001.938256 qam19
202907500001.740256 qam20
21298750000240256 qam21
223067500001.540256 qam22
233147500002.440256 qam23
243227500002.740256 qam24



Downstream bonded channels

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

1Locked39.33860
2Locked38.92239354
3Locked40.3580227040
4Locked40.31278101
5Locked40.34750
6Locked40.31670
7Locked38.92960
8Locked38.94120
9Locked40.33960
10Locked40.33430
11Locked40.33650
12Locked40.33600
13Locked40.33980
14Locked40.35530
15Locked40.33570
16Locked40.32500
17Locked40.33140
18Locked40.32830
19Locked38.94530
20Locked40.34130
21Locked40.33780
22Locked40.338613
23Locked40.34050
24Locked40.34810

 

Upstream bonded channels

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

16030000038.5512064 qam1
23940000038512064 qam4
34620000038.5512064 qam3
45370000038.5512064 qam2


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA00130
2ATDMA0080
3ATDMA00130
4ATDMA00100

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
fg87dsfd;kfoA,.iyewrkldJKDHSU



Primary Downstream Service Flow

SFID30314
Max Traffic Rate690000278
Max Traffic Burst42600
Min Traffic Rate0

 

0 Kudos
Reply
richardW67
  • 8
  • 0
  • 0
Joining in
662 Views
Message 7 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Primary Upstream Service Flow

SFID30313
Max Traffic Rate44000278
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort
Network LogTime Priority Description
11/06/2021 10:01:36noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2021 17:13:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2021 11:29:28noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2021 11:02:45criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2021 03:40:42noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2021 03:40:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/06/2021 01:56:37criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2021 21:32:57noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2021 20:44:27criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2021 20:03:27noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 23:17:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/06/2021 20:33:34noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/06/2021 15:48:8criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/06/2021 15:40:42noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/06/2021 15:40:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 22:24:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 03:40:42noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
03/06/2021 03:40:42ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
31/05/2021 07:14:44criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/05/2021 15:40:42noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt078+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

0 Kudos
Reply
lotharmat
  • 3.85K
  • 259
  • 724
Community elder
651 Views
Message 8 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

That looks like a lot of T3s

Can we start from a blank slate?

Power off your hub
Unplug it
Leave it off for about 5 minutes
Plug it back in and switch on
Wait about 5-10 mins to stabilise

repost the stats - Let's see what starts happening!



------------------------------------------------------------------
Hub 3 - Modem Mode - TP-Link Archer C7

0 Kudos
Reply
richardW67
  • 8
  • 0
  • 0
Joining in
643 Views
Message 9 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Will do. Although i do this regularly in the vain hope that it will revert back to what it was 4 months

Will have to wait until family are not using otherwise i get router rage 🙂

0 Kudos
Reply
richardW67
  • 8
  • 0
  • 0
Joining in
641 Views
Message 10 of 17
Flag for a moderator

Re: No Ranging Response received - T3 time-out

does this help?

https://www.thinkbroadband.com/broadband/monitoring/quality/share/0a72b77513c2f8c93cee9e46fa24e816f254f87b-11-06-2021
0 Kudos
Reply