Menu
Reply
Highlighted
  • 5
  • 1
  • 0
Tuning in
421 Views
Message 1 of 8
Flag for a moderator

No Ranging Response received - T3 time-out

I'm seeing regular drop-outs on my router status page, along with ping spikes and dropped packets on a regular basis when using PingPlotter. I work for the NHS and dial into Skype and Teams calls throughout the day, but this is causing difficulty in supporting clinical and operational colleagues.

I know how busy you guys must be at the moment, but I'd appreciate it if you could advise how we could get this resolved?

Just to note that my account here on the community page is not registered with the same email address that our VM account is, happy to provide further detail via PM if that helps.

0 Kudos
Reply
Highlighted
  • 564
  • 190
  • 163
Forum Team (Retired)
Forum Team (Retired)
407 Views
Message 2 of 8
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi,

Please PM me with your account number and area ref and I can take a look at this for you.

Thanks Chris





To PM just hover over my profile picture and click Send Message when the option comes up. Please don't post any of the info I've asked for in this thread as it's public

Here to help! I'm a technician helping out whilst working from home. Find out more


0 Kudos
Reply
Highlighted
  • 5
  • 1
  • 0
Tuning in
333 Views
Message 3 of 8
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Cable Modem Status

Item 
Status 
Comments
Acquired Downstream Channel (Hz)
483000000
Locked
Ranged Upstream Channel (Hz)
32600075
Locked
Provisioning State
Online
 

 

Downstream bonded channels

Channel Frequency (Hz)Power (dBmV)SNR (dB)Modulation Channel ID
1483000000-0.540256 qam30
21870000002.540256 qam7
31950000002.240256 qam8
42030000001.940256 qam9
52110000001.540256 qam10
62190000001.440256 qam11
72270000001.240256 qam12
82350000001.240256 qam13
92430000000.740256 qam14
102510000000.740256 qam15
112590000000.740256 qam16
12267000000140256 qam17
132750000001.240256 qam18
142830000001.240256 qam19
152910000001.240256 qam20
162990000001.740256 qam21
173070000001.740256 qam22
183150000001.940256 qam23
193230000001.740256 qam24
204430000000.240256 qam25
21451000000040256 qam26
22459000000040256 qam27
23467000000-0.240256 qam28
24475000000-0.240256 qam29



Downstream bonded channels

Channel Locked Status RxMER (dB)Pre RS ErrorsPost RS Errors
1Locked40.397259019
2Locked40.910488170
3Locked40.98848186
4Locked40.310738206
5Locked40.314608448
6Locked40.315238143
7Locked40.315818114
8Locked40.314798106
9Locked40.916567885
10Locked40.319367827
11Locked40.919457713
12Locked40.919027968
13Locked40.918647821
14Locked40.320057897
15Locked40.923118166
16Locked40.923608332
17Locked40.921988284
18Locked40.925048557
19Locked40.926407843
20Locked40.948728522
21Locked40.362668427
22Locked40.366368411
23Locked40.973938725
24Locked40.993619025

 

Upstream bonded channels

Channel Frequency (Hz)Power (dBmV)Symbol Rate (ksps)Modulation Channel ID
1326000755.025512064 qam3
2462000525.05512064 qam1
3257998944.975512064 qam4
4394000875.025512064 qam2



Upstream bonded channels

Channel Channel TypeT1 TimeoutsT2 TimeoutsT3 TimeoutsT4 Timeouts
1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000

 

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsl10016u+voc-b.cm



Primary Downstream Service Flow

  
SFID33446
Max Traffic Rate117000047
Max Traffic Burst42600
Min Traffic Rate0


Primary Upstream Service Flow

SFID33445
Max Traffic Rate10500047
Max Traffic Burst16320
Min Traffic Rate0
Max Concatenated Burst16320
Scheduling TypeBestEffort

 

0 Kudos
Reply
Highlighted
  • 5
  • 1
  • 0
Tuning in
332 Views
Message 4 of 8
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Network Log

Time Priority Description
21/04/2020 16:40:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/04/2020 15:53:4ErrorDHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/04/2020 00:08:1ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2020 12:39:41noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2020 09:40:34criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/04/2020 08:23:2ErrorDHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
19/04/2020 08:17:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/04/2020 22:58:55noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/04/2020 05:29:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:17:2criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:14:24Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:14:20Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:14:20criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:14:20Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:14:20criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:14:19Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:13:32Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:13:28criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:13:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
16/04/2020 13:13:27criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Highlighted
  • 1.56K
  • 78
  • 158
Forum Team
Forum Team
324 Views
Message 5 of 8
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi holdawas.  Sorry you're having issues.

I would recommend taking C_Butcher86 advice.  He is a Virgin Media technician and would be able to advise you.

Regards

 

Lee_R

0 Kudos
Reply
Highlighted
  • 5
  • 1
  • 0
Tuning in
291 Views
Message 6 of 8
Flag for a moderator

Re: No Ranging Response received - T3 time-out

I have popped a couple messages across last week and this but not yet heard back. I'm conscious how busy you guys must be (and sympathise, just finished a 90 minute COVID teleconference!) so I was looking to be proactive and supply data that could help clarify the issue.

I'm looking at picking up a mesh WiFi system as well, but am concerned that given that the issues are being flagged on the router network log, this may not resolve the issue.

0 Kudos
Reply
Highlighted
  • 5
  • 1
  • 0
Tuning in
229 Views
Message 7 of 8
Flag for a moderator
Helpful Answer

Re: No Ranging Response received - T3 time-out

Installing a separate mesh network seems to have resolved the issue.
0 Kudos
Reply
Highlighted
  • 1.53K
  • 69
  • 135
Forum Team
Forum Team
225 Views
Message 8 of 8
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thanks for he update holdawas, glad to hear this is now resolved. If you need us again in the future please don't hesitate to get in touch.

 

Stay safe

 

Thanks

 

Rob

0 Kudos
Reply