Menu
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
334 Views
Message 1 of 18
Flag for a moderator

No Ranging Response received - T3 time-out

I have recently been getting alot of dropped connections, timeouts and slowdowns on my connection.

Many thanks,

Ben

As others have also seen, its usually showing:

No Ranging Response received - T3 time-out, but there are other errors as well.

28/05/2020 16:40:32 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:30 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

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

1325999124.875512064 qam5
2394000004.875512064 qam4
3462000004.85512064 qam3
4536999464.725512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

Downstream bonded channels

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

12350000004.538256 qam13
22430000004.638256 qam14
32510000004.438256 qam15
42590000003.538256 qam16
52670000001.538256 qam17
62750000000.538256 qam18
7283000000038256 qam19
82910000001.738256 qam20
92990000002.538256 qam21
103070000004.138256 qam22
113150000005.540256 qam23
123230000005.438256 qam24
133470000002.438256 qam25
143550000000.938256 qam26
15363000000-0.538256 qam27
163710000000.538256 qam28
173790000001.538256 qam29
18387000000238256 qam30
193950000002.738256 qam31
204030000003.238256 qam32
214110000002.538256 qam33
224190000001.938256 qam34
234270000001.238256 qam35
24435000000038256 qam36



Downstream bonded channels

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

1Locked38.92120641620549
2Locked38.91466501505878
3Locked38.9522857453152
4Locked38.9734919427965
5Locked38.61435781447149
6Locked38.91664051415944
7Locked38.91518083412202
8Locked38.61387550409197
9Locked38.61535355447676
10Locked38.6638482430946
11Locked40.3512371378855
12Locked38.9512056407076
13Locked38.91185013542729
14Locked38.91848219571013
15Locked38.62634271593103
16Locked38.61773550521028
17Locked38.91837152475389
18Locked38.92069746429145
19Locked38.92565145865117
20Locked38.92617751323699
21Locked38.93022765407966
22Locked38.93773984435461
23Locked38.64502552452504
24Locked38.9139706791014014

 

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
235000000
Locked
Ranged Upstream Channel (Hz)
32599912
Locked
Provisioning State
Online
0 Kudos
Reply
Highlighted
  • 7.54K
  • 593
  • 1.28K
Legend
318 Views
Message 2 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Stats are ok, the Pre & Post RS error look really bad, but as they are accumulative since the last power cycle they could have built up,over a long period of time. So please power cycle your hub and post a new set of stats after a few hours. 


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
Highlighted
  • 3.57K
  • 196
  • 546
Community elder
312 Views
Message 3 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

That wide variation in signal levels across the frequency spectrum suggests there is a mismatch on the cable feed. And that would also explain the pickup of noise. 

I would check that the coax is not damaged and the connections are all tight. The fault could be outside. 

Highlighted
  • 7
  • 0
  • 0
Tuning in
263 Views
Message 4 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi both,

Thanks for the info.  I rebooted the hub yesterday morning and it has still played up with slowdowns and disconnects.

The log seems to have not updated and only shows my password keyboard mashing error and then my login.  Not any of the events for 24hrs or my login this morning.

I have checked the internal cable and all is ok, its a new cable that came with the hub a few months ago and is around 7ft from the wall socket. All pushed in securely - not screwed in anymore.

Many thanks,

Ben

Network Log
Time Priority Description
30/05/2020 09:52:17 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/05/2020 09:52:8 Warning! LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 18:53:12 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 18:53:7 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 18:53:6 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 18:53:6 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 18:53:6 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 16:33:35 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 16:33:30 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 16:33:30 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 16:33:30 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 16:33:30 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
29/05/2020 12:20:27 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:32 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:30 Warning! Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 critical SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 16:40:25 Warning! RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/05/2020 14:45:53 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32599979 4.825 5120 64 qam 5
2 39400000 4.825 5120 64 qam 4
3 46200000 4.8 5120 64 qam 3
4 53699990 4.65 5120 64 qam 2


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0


Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 235000000 5.4 38 256 qam 13
2 243000000 5.5 38 256 qam 14
3 251000000 5 38 256 qam 15
4 259000000 4.3 38 256 qam 16
5 267000000 2.5 38 256 qam 17
6 275000000 1.4 38 256 qam 18
7 283000000 0.9 38 256 qam 19
8 291000000 2.5 38 256 qam 20
9 299000000 3.2 38 256 qam 21
10 307000000 4.8 38 256 qam 22
11 315000000 6.3 40 256 qam 23
12 323000000 6.1 38 256 qam 24
13 347000000 3.2 38 256 qam 25
14 355000000 1.7 38 256 qam 26
15 363000000 0.2 38 256 qam 27
16 371000000 1.4 38 256 qam 28
17 379000000 2.5 38 256 qam 29
18 387000000 3 38 256 qam 30
19 395000000 3.7 38 256 qam 31
20 403000000 4.1 38 256 qam 32
21 411000000 3.5 38 256 qam 33
22 419000000 2.7 38 256 qam 34
23 427000000 2.2 38 256 qam 35
24 435000000 0.7 38 256 qam 36


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.9 339 0
2 Locked 38.9 239 3
3 Locked 38.9 170 0
4 Locked 38.6 382 26
5 Locked 38.6 486 27
6 Locked 38.9 791 30
7 Locked 38.6 624 2
8 Locked 38.9 478 3
9 Locked 38.9 554 1
10 Locked 38.6 259 0
11 Locked 40.3 133 0
12 Locked 38.9 121 0
13 Locked 38.6 308 0
14 Locked 38.9 512 0
15 Locked 38.6 855 3
16 Locked 38.6 337 0
17 Locked 38.6 168 0
18 Locked 38.9 118 0
19 Locked 38.6 93 0
20 Locked 38.6 46 0
21 Locked 38.6 59 0
22 Locked 38.9 84 0
23 Locked 38.9 109 0
24 Locked 38.9 239 0

 

Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz)
235000000
Locked
Ranged Upstream Channel (Hz)
32599979
Locked
Provisioning State
Online

 


General Configuration
Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsxxl35016u-b.cm


Primary Downstream Service Flow
SFID 260712
Max Traffic Rate 402500089
Max Traffic Burst 42600
Min Traffic Rate 0


Primary Upstream Service Flow
SFID 260711
Max Traffic Rate 38500089
Max Traffic Burst 42600
Min Traffic Rate 0
Max Concatenated Burst 42600
Scheduling Type BestEffort

0 Kudos
Reply
Highlighted
  • 6.08K
  • 310
  • 539
Forum Team
Forum Team
248 Views
Message 5 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi edax, 

 

Thanks for posting. I am sorry for the broadband issues. I've ran a check here and no issues are showing, faults in area etc. 

 

However, on the WiFi, it is giving me several suggestions. It is saying there are some devices such as an Amazon device too close to the router and a few other devices on the wrong band of WiFi. Could these devices either be connected via Ethernet and/or moved away from the hub? This would then improve the bandwidth.

 

If you do have a smartphone, please download the Virgin Media Connect app which when downloaded, you can do a wireless scan in the property. You can find out more here

 

Kind regards,

John_GS
Forum Team

Need a helpful hand to show you how to make a payment? Check out our guide - "How to pay my Virgin Media bill"

0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
243 Views
Message 6 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi John_GS,

I do have several devices on the network here and I can add the echo pro to the switch or move it.  I have not seen wifi connected devices cause router issues before though.  

I have used the connect app to check the wifi and other than prompting for a plug-in extender for use in the next room, it showed no problems.  I have uninstalled it as it often causes problems with the virgin wifi on my phone when I am out.  

I will see what a difference this can make and post later today. 

Many thanks,

Ben

0 Kudos
Reply
Highlighted
  • 7.54K
  • 593
  • 1.28K
Legend
223 Views
Message 7 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

@John_GS

With Pre RS errors numbers like that in a short time there is definitely a hub or more probably a circuit problem.


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
Highlighted
  • 6.08K
  • 310
  • 539
Forum Team
Forum Team
215 Views
Message 8 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Cheers Ben, keep me posted 🙂

 

Kind regards

John_GS
Forum Team

Need a helpful hand to show you how to make a payment? Check out our guide - "How to pay my Virgin Media bill"

0 Kudos
Reply
Highlighted
  • 7
  • 0
  • 0
Tuning in
201 Views
Message 9 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi John,

Thank you.  I have the following logs from the past 24hrs or so.  Its still causing problems especially when I need the bandwidth such as Teams or Zoom meetings and phone calls via softphone.

Many thanks.

Ben

TimePriorityDescription02/06/2020 05:37:4Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:36:59criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:36:59Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:36:58criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:36:58Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:36criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:34Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:28Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:28criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:28Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:28criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;02/06/2020 05:17:28Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 16:24:57Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 16:24:52criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 16:24:52Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 16:24:52criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 16:24:52Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 16:24:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 11:35:35noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;01/06/2020 08:18:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32599974 4.875 5120 64 qam 5
2 39399956 4.875 5120 64 qam 4
3 46200000 4.85 5120 64 qam 3
4 53700034 4.7 5120 64 qam 2


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

 

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 235000000 4.1 38 256 qam 13
2 243000000 4.4 38 256 qam 14
3 251000000 4 38 256 qam 15
4 259000000 3 38 256 qam 16
5 267000000 1.2 38 256 qam 17
6 275000000 0 38 256 qam 18
7 283000000 -0.2 38 256 qam 19
8 291000000 1.2 38 256 qam 20
9 299000000 2.2 38 256 qam 21
10 307000000 3.7 38 256 qam 22
11 315000000 5.1 40 256 qam 23
12 323000000 4.9 38 256 qam 24
13 347000000 2 38 256 qam 25
14 355000000 0.5 38 256 qam 26
15 363000000 -0.7 38 256 qam 27
16 371000000 0.2 38 256 qam 28
17 379000000 1.2 38 256 qam 29
18 387000000 1.7 38 256 qam 30
19 395000000 2.4 38 256 qam 31
20 403000000 2.7 38 256 qam 32
21 411000000 2.2 38 256 qam 33
22 419000000 1.5 38 256 qam 34
23 427000000 0.9 38 256 qam 35
24 435000000 -0.5 38 256 qam 36

 

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 1616 7853
2 Locked 38.9 1423 10990
3 Locked 38.9 1725 9209
4 Locked 38.9 2386 7744
5 Locked 38.6 4890 6178
6 Locked 38.9 5020 6255
7 Locked 38.6 4231 5979
8 Locked 38.6 5861 6496
9 Locked 38.9 2152 11524
10 Locked 38.6 1655 11940
11 Locked 38.9 1451 11456
12 Locked 38.9 1308 10800
13 Locked 38.9 1372 11749
14 Locked 38.6 1493 12521
15 Locked 38.9 2593 12757
16 Locked 38.6 1910 11026
17 Locked 38.9 1249 11283
18 Locked 38.6 1413 11829
19 Locked 38.6 1829 11186
20 Locked 38.9 1636 10427
21 Locked 38.6 1732 10311
22 Locked 38.9 1544 10912
23 Locked 38.9 1823 10402
24 Locked 38.9 2974 10196

 

Cable Modem Status
Item Status Comments
Acquired Downstream Channel (Hz)
235000000
Locked
Ranged Upstream Channel (Hz)
32599974
Locked
Provisioning State
Online

 

General Configuration
Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsxxl35016u-b.cm


Primary Downstream Service Flow
SFID 260712
Max Traffic Rate 402500089
Max Traffic Burst 42600
Min Traffic Rate 0

Primary Upstream Service Flow
SFID 260711
Max Traffic Rate 38500089
Max Traffic Burst 42600
Min Traffic Rate 0
Max Concatenated Burst 42600
Scheduling Type BestEffort

 

0 Kudos
Reply
Highlighted
  • 3.57K
  • 196
  • 546
Community elder
192 Views
Message 10 of 18
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Nearly 6 dB variation across the channels, and a lot of noise pickup. Looks very like a cable fault. 

0 Kudos
Reply