Menu
Reply
marccharris
  • 3
  • 0
  • 0
Joining in
134 Views
Message 1 of 6
Flag for a moderator

No Ranging Response received - T3 time-out

Ever since being persuaded to stay by having money taken off our bill (and then having a message saying its going up again by £3.50 🙄) our internet has been absolutely dreadful. Unreliable on wifi and ethernet, which isnt great when you are shielding and work for NHS IT trying to help coordinate the vaccination programme Via MS Teams and it keeps losing signal, but anyway.

Log below, im guessing the No Ranging Response received - T3 time-out are whats killing it each time.

Cant get through on the phone, so hoping someone can read this from VM and send an engineer out to sort it out.

23/01/2021 16:10:45noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 16:01:38criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
23/01/2021 08:12:31ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/01/2021 09:56:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/01/2021 06:02:28ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/01/2021 19:53:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/01/2021 21:22:34ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2021 05:14:17criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/01/2021 02:05:45ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
01/01/1970 00:01:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/01/2021 00:28:58noticeSW download Successful - Via NMS
11/01/2021 00:25:55noticeSW Download INIT - Via NMS
10/01/2021 19:49:8Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:49:8criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:49:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:49:7criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:37:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:37:5criticalSYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:37:5Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/01/2021 19:37:5critical

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTSMAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

0 Kudos
Reply
Tudor
  • 7.94K
  • 636
  • 1.38K
Alessandro Volta
123 Views
Message 2 of 6
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Please post your up/downstream stats.


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
carl_pearce
  • 4.74K
  • 403
  • 708
Superstar
119 Views
Message 3 of 6
Flag for a moderator

Re: No Ranging Response received - T3 time-out

And create a BQM and post the live link.

0 Kudos
Reply
marccharris
  • 3
  • 0
  • 0
Joining in
116 Views
Message 4 of 6
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thankyou. Data attached.

 

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
11390000006.538256 qam1
21470000006.538256 qam2
31550000006.640256 qam3
41630000006.340256 qam4
51710000006.440256 qam5
6179000000638256 qam6
71870000006.340256 qam7
81950000005.838256 qam8
92030000005.540256 qam9
102110000005.438256 qam10
11219000000540256 qam11
122270000004.538256 qam12
132350000004.338256 qam13
142430000003.238256 qam14
152510000002.538256 qam15
162590000002.738256 qam16
172670000004.138256 qam17
182750000004.838256 qam18
19283000000538256 qam19
202910000005.538256 qam20
212990000005.938256 qam21
223070000005.940256 qam22
233150000006.440256 qam23
243230000006.540256 qam24


Downstream bonded channelsChannel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.91430
2Locked38.917813
3Locked40.3348313
4Locked40.35206310
5Locked40.3970
6Locked38.91510
7Locked40.3800
8Locked38.9760
9Locked40.31190
10Locked38.61390
11Locked40.3870
12Locked38.91180
13Locked38.61290
14Locked38.62961
15Locked38.64860
16Locked38.64670
17Locked38.61700
18Locked38.91100
19Locked38.6870
20Locked38.91160
21Locked38.912312
22Locked40.31160
23Locked40.3850
24Locked40.31350

 

Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
15369977744512064 qam2
26029978644.8512064 qam1
34620001943.5512064 qam3
43940000043.3512064 qam4


Upstream bonded channelsChannel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0020
2ATDMA0020
3ATDMA0010
4ATDMA0020
0 Kudos
Reply
marccharris
  • 3
  • 0
  • 0
Joining in
87 Views
Message 5 of 6
Flag for a moderator

Re: No Ranging Response received - T3 time-out

BQM link here.

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1afb2210cadf5420d62832a86b04ff976ec72d9c

That blanketpacket loss between 7am and 11am doesn't seem ideal... 

0 Kudos
Reply
jpeg1
  • 4.23K
  • 236
  • 675
Community elder
83 Views
Message 6 of 6
Flag for a moderator

Re: No Ranging Response received - T3 time-out

That patch looks like a one-off, could be a few different reasons.  Apart from that the BQM is OK and your signal levels are fine too.  Check the BQM on a weekday and see how it looks. 

The log entries are spread over many days so unlikely to have caused a continuous problem. 

0 Kudos
Reply