Menu
Reply
cneeson467
  • 4
  • 0
  • 0
Joining in
330 Views
Message 1 of 7
Flag for a moderator

No Ranging Response received - T3 time-out

Hi all,

I've been having frequent drop outs of my 200mb line for around 2 months now. Had an engineer out who replaced the hub but it didn't help our problem. Inspecting the network logs on the hub show the readouts below.

Very frustrating problem as we use the line for work, hoping someone from the support team can shed some light.

Network Log

Time Priority Description

10/04/2022 08:27:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 08:21:14noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 08:19:48Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 06:40:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 03:03:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 22:34:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 21:56:54Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 17:23:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 09:53:47Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 08:25:58criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 08:03:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 07:57:55criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 07:54:27Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 21:11:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 18:51:16Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 11:21:12criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 11:19:52criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 11:19:52criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 11:16:57criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/04/2022 11:15:38criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13310000003.540256 qam25
2203000000540256 qam9
32110000004.940256 qam10
42190000004.840256 qam11
52270000004.540256 qam12
62350000004.540256 qam13
7243000000440256 qam14
82510000004.140256 qam15
92590000004.340256 qam16
102670000004.140256 qam17
112750000003.940256 qam18
122830000003.940256 qam19
132910000003.940256 qam20
14299000000440256 qam21
153070000003.740256 qam22
163150000003.440256 qam23
173230000003.240256 qam24
183390000003.240256 qam26
19347000000340256 qam27
203550000002.540256 qam28
213630000002.540256 qam29
223710000002.740256 qam30
233790000002.540256 qam31
243870000002.240256 qam32

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14620000044512064 qam3
23260000042512064 qam5
33940000044.5512064 qam4
45370000043512064 qam2

 

Thanks,
Craig

Tags (1)
0 Kudos
Reply
Tudor
  • 12.88K
  • 1K
  • 2.57K
Very Insightful Person
Very Insightful Person
308 Views
Message 2 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Please post the rest of the 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
cneeson467
  • 4
  • 0
  • 0
Joining in
293 Views
Message 3 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Thanks for your reply! Ah sorry I can't edit the original post, here are the full stats from the hub. If there is anything more specific you need please let me know

Cable Modem StatusItem Status Comments

Acquired Downstream Channel (Hz)
331000000
Locked
Ranged Upstream Channel (Hz)
46200000
Locked
Provisioning State
Online

Downstream bonded channels

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

1331000000440256 qam25
22030000005.840256 qam9
32110000005.540256 qam10
42190000005.540256 qam11
52270000005.140256 qam12
6235000000540256 qam13
72430000004.640256 qam14
82510000004.840256 qam15
92590000004.940256 qam16
102670000004.640256 qam17
112750000004.540256 qam18
122830000004.440256 qam19
132910000004.440256 qam20
142990000004.540256 qam21
153070000004.140256 qam22
163150000003.740256 qam23
173230000003.740256 qam24
183390000003.738256 qam26
193470000003.440256 qam27
20355000000340256 qam28
213630000002.938256 qam29
223710000003.240256 qam30
233790000002.938256 qam31
243870000002.540256 qam32

 

Downstream bonded channels

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

1Locked40.33553013721
2Locked40.37512134059
3Locked40.37249532021
4Locked40.36892829664
5Locked40.36614127955
6Locked40.96129626491
7Locked40.35739124842
8Locked40.35374423117
9Locked40.35239121813
10Locked40.35666820227
11Locked40.34865919349
12Locked40.94399818387
13Locked40.94095217237
14Locked40.33932416427
15Locked40.33802916041
16Locked40.33694015367
17Locked40.93698714977
18Locked38.93540913541
19Locked40.33313812912
20Locked40.33297812447
21Locked38.93149512416
22Locked40.92973412044
23Locked38.92878611502
24Locked40.32652411362
 

 

0 Kudos
Reply
cneeson467
  • 4
  • 0
  • 0
Joining in
292 Views
Message 4 of 7
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
14620000042.3512064 qam3
23260000039.8512064 qam5
33940000040512064 qam4
45370000041512064 qam2


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA00420
2ATDMA001380
3ATDMA00120
4ATDMA0040

 

General Configuration

Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
DHSUBsgvca69834ncxv987325



Primary Downstream Service Flow

SFID16719
Max Traffic Rate230000061
Max Traffic Burst42600
Min Traffic Rate0



Primary Upstream Service Flow

SFID16718
Max Traffic Rate22000061
Max Traffic Burst42600
Min Traffic Rate0
Max Concatenated Burst42600
Scheduling TypeBestEffort
0 Kudos
Reply
cneeson467
  • 4
  • 0
  • 0
Joining in
291 Views
Message 5 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

 

Network Log

Time Priority Description
10/04/2022 18:28:45noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 18:10:18criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 16:43:46noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 16:43:46ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 08:27:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 08:21:14noticeLAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 08:19:48Warning!LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 06:40:4criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/04/2022 03:03:37Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 22:34:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 21:56:54Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/04/2022 17:23:22criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
 
0 Kudos
Reply
Tudor
  • 12.88K
  • 1K
  • 2.57K
Very Insightful Person
Very Insightful Person
276 Views
Message 6 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Too many upstream T3s and large number of downstream Pre an Post errors. Unfortunately because these figures are accumulative since the hub was last power cycled we need to find out the current situation. So please turn off your hub for a minute and then turn it on, this will reset the counters. Next after say 2 hours post a new full set of stats, we can then see if the figures are too high.


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
Jodi_S
  • 4.14K
  • 205
  • 440
Forum Team
Forum Team
237 Views
Message 7 of 7
Flag for a moderator

Re: No Ranging Response received - T3 time-out

Hi cneeson467,

A warm welcome and thanks for posting. Sorry to see that you're currently experiencing issues with our internet services again. You advised you've had a hub replacement but this has not resolved the frequent drop out issue. 

We have checked the systems form our end this morning and can see that you are experiencing short term connectivity issues. 

I have raised a fault ticket on your behalf regarding this issue. It has advised this issue should be resolved in the next 24 hours, however, if you're still experiencing issues after this time, please come back to us. 

Kind regards Jodi. 

0 Kudos
Reply