Menu
Reply
TheLimpNinja
  • 6
  • 0
  • 0
Joining in
128 Views
Message 1 of 7
Flag for a moderator

No Ranging Response received - T3 time-out

Over the past few weeks my router has been rebooting itself, seemingly randomly, and causing my WiFi to drop out as a result. Looking through my network log I keep seeing the following errors repeated for each instance, any advice on how to address this:

 

Time Priority Description

22/01/2021 14:33:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/01/2021 14:33:50criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/01/2021 14:30:21Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

0 Kudos
Reply
gary_dexter
  • 29.1K
  • 1.78K
  • 3.81K
Alessandro Volta
124 Views
Message 2 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Post the Network, Upstream and Downstream logs from the hubs admin pages back here as text please 


*****
If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!!
I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences.
Office 365, Dynamics CRM and Cloud Computing Jedi
0 Kudos
Reply
Tudor
  • 7.95K
  • 637
  • 1.38K
Alessandro Volta
111 Views
Message 3 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

It is highly unlikely the hub is rebooting, it’s just losing connection to the VM CMTS. You can tell if the hub reboots by dates in the network log of 01/01/1970.

Supply the data as requested. 


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2
0 Kudos
Reply
TheLimpNinja
  • 6
  • 0
  • 0
Joining in
46 Views
Message 4 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thanks all for the reply, logs copied below. will post whole network log separately due to character limits:

Upstream bonded channels

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

16029997652512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000

Downstream 

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

1483000000-11.537256 qam30
2187000000-738256 qam7
3195000000-7.438256 qam8
4203000000-7.538256 qam9
5211000000-7.738256 qam10
6219000000-7.738256 qam11
7227000000-838256 qam12
8235000000-8.538256 qam13
9243000000-8.538256 qam14
10251000000-8.538256 qam15
11259000000-8.738256 qam16
12267000000-8.938256 qam17
13275000000-8.738256 qam18
14283000000-8.238256 qam19
15291000000-8.238256 qam20
16299000000-8.438256 qam21
17307000000-8.738256 qam22
18315000000-838256 qam23
19323000000-838256 qam24
20443000000-1137256 qam25
21451000000-11.237256 qam26
22459000000-11.537256 qam27
23467000000-11.537256 qam28
24475000000-11.536256 qam29



Downstream bonded channels

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

1Locked37.32065
2Locked38.611092836
3Locked38.96367
4Locked38.94566
5Locked38.63189
6Locked38.92678
7Locked38.62291
8Locked38.93598
9Locked38.92585
10Locked38.622108
11Locked38.63284
12Locked38.612108
13Locked38.613118
14Locked38.91379
15Locked38.62877
16Locked38.630129
17Locked38.621105
18Locked38.921131
19Locked38.92769
20Locked37.32257
21Locked37.31752
22Locked37.31470
23Locked37.31797
24Locked36.81946
0 Kudos
Reply
TheLimpNinja
  • 6
  • 0
  • 0
Joining in
45 Views
Message 5 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Network Log

Time Priority Description

25/01/2021 12:55:0Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 22:16:43criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 20:12:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 09:22:21criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 08:15:9criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:38:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:25:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:24:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:18:3criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:16:1Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:15:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:15:35Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:14:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:14:39Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:14:28criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:14:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 07:14:26criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 01:01:9Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 00:57:59criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 00:57:59criticalUnicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
TheLimpNinja
  • 6
  • 0
  • 0
Joining in
28 Views
Message 6 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thank you, data has been posted to this thread. Let me know if it is not visible. 

thanks. 

0 Kudos
Reply
gary_dexter
  • 29.1K
  • 1.78K
  • 3.81K
Alessandro Volta
26 Views
Message 7 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Downstream levels are too low and upstream is too high and only locked to one channel instead of four.

Unless there is an area issue you'll need an engineer.

*****
If you think my answer has helped - please provide me with a Kudos rating and mark as Helpful Answer!!
I do not work for Virgin Media - all opinions expressed are of my own and all answers are provided from my own and past experiences.
Office 365, Dynamics CRM and Cloud Computing Jedi
0 Kudos
Reply