Menu
Reply
DaveSm
  • 9
  • 0
  • 0
Tuning in
437 Views
Message 1 of 12
Flag for a moderator

No Ranging Response received - T3 time-out

Hello all

I've been having an on/off issue with no ranging response received errors and packet loss since the end of July - about once a week would have to restart the hub3 a few times over the space of an hour or so before back to the usual fast service for another week or so.

Today since about midday its been particularly bad prompting me posting this now. Decided not to restart the hub aside from a couple of times to see if anything extra in the logs.

Posting the usual router status info and a BQM below. I'm on the 350 service with a Hub3 as mentioned, hub restarted loads of times over the weeks, all connections are tight. Any other info needed happy to provide it of course.

Thanks - Dave

 

0 Kudos
Reply
DaveSm
  • 9
  • 0
  • 0
Tuning in
436 Views
Message 2 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 267000000 2.7 40 256 qam 17
2 275000000 2.7 40 256 qam 18
3 283000000 3 40 256 qam 19
4 291000000 2.7 40 256 qam 20
5 299000000 3.2 40 256 qam 21
6 307000000 3.5 40 256 qam 22
7 315000000 3.7 40 256 qam 23
8 323000000 3.7 40 256 qam 24
9 331000000 3.5 40 256 qam 25
10 371000000 3.9 40 256 qam 26
11 379000000 3.7 40 256 qam 27
12 387000000 4 40 256 qam 28
13 395000000 4.4 40 256 qam 29
14 403000000 4.6 40 256 qam 30
15 411000000 4.8 40 256 qam 31
16 419000000 4.5 40 256 qam 32
17 427000000 4.5 40 256 qam 33
18 435000000 4.4 40 256 qam 34
19 443000000 4 40 256 qam 35
20 451000000 3.5 40 256 qam 36
21 459000000 3 38 256 qam 37
22 467000000 2.5 38 256 qam 38
23 475000000 2.5 40 256 qam 39
24 483000000 2.9 38 256 qam 40


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.3 5 0
2 Locked 40.3 5 0
3 Locked 40.3 5 0
4 Locked 40.3 5 0
5 Locked 40.3 12 0
6 Locked 40.9 4 0
7 Locked 40.3 6 0
8 Locked 40.3 4 0
9 Locked 40.3 1 0
10 Locked 40.3 0 0
11 Locked 40.3 5 0
12 Locked 40.3 7 0
13 Locked 40.3 5 0
14 Locked 40.3 4 0
15 Locked 40.9 5 0
16 Locked 40.3 6 0
17 Locked 40.3 5 0
18 Locked 40.3 6 0
19 Locked 40.3 5 0
20 Locked 40.3 5 0
21 Locked 38.6 4 0
22 Locked 38.9 6 0
23 Locked 40.3 7 0
24 Locked 38.9 8 0
0 Kudos
Reply
DaveSm
  • 9
  • 0
  • 0
Tuning in
435 Views
Message 3 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 39400843 5.2 5120 16 qam 6
2 25799854 5.2 5120 16 qam 8
3 46201667 5.2 5120 16 qam 5
4 32600087 5.2 5120 16 qam 7


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
0 Kudos
Reply
DaveSm
  • 9
  • 0
  • 0
Tuning in
434 Views
Message 4 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

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 1133602
Max Traffic Rate 402500089
Max Traffic Burst 42600
Min Traffic Rate 0


Primary Upstream Service Flow
SFID 1133601
Max Traffic Rate 38500089
Max Traffic Burst 42600
Min Traffic Rate 0
Max Concatenated Burst 42600
Scheduling Type BestEffort
0 Kudos
Reply
DaveSm
  • 9
  • 0
  • 0
Tuning in
431 Views
Message 5 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Network Log
Time Priority Description
13/09/2020 21:49:41 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 21:24:18 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 21:19:45 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 21:09:0 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 21:03:38 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 21:01:5 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 20:50:39 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 15:12:6 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 15:11:52 notice Received REG-RSP while in REG-HOLD1 state;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 15:11:42 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 15:11:31 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 15:05:34 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 15:05:12 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 14:59:18 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 14:58:47 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 14:22:17 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 14:16:48 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 13:59:35 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 13:58:32 notice LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/09/2020 13:57:33 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
DaveSm
  • 9
  • 0
  • 0
Tuning in
430 Views
Message 6 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

bqm.png

0 Kudos
Reply
Tudor
  • 8.12K
  • 649
  • 1.42K
Alessandro Volta
423 Views
Message 7 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

All four upstreams are too high, out of spec, and on 16 QAM when they should be 64QAM, you need a technician to correct, call customer services or wait for a VM staff member to get to your post.


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
DaveSm
  • 9
  • 0
  • 0
Tuning in
419 Views
Message 8 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thanks Tudor. I'll give them a call in the morning then.

Interestingly however, I did a check service status and received the message stating there was network interference in my area affecting multiple customers. I guess I have two problems, unless the service check message is generic but not seen that particular one before.

 

0 Kudos
Reply
Tudor
  • 8.12K
  • 649
  • 1.42K
Alessandro Volta
376 Views
Message 9 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

If there is a service problem with interference in your area it’s no use reporting your problem. All visits are cancelled until that problem is fixed. You need to keep checking on the status, if the problem is resolved, but your one persists then is the time to report your 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
Emily_G
  • 4.78K
  • 207
  • 285
Forum Team
Forum Team
316 Views
Message 10 of 12
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thanks for the post Davesm.

 

Can we please confirm how your services are today? 

 

Did you get in touch with the team to investigate further?

 

Let us know, Emily.

0 Kudos
Reply