Community FAQ
cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

T3 Timeouts + Post RS Errors

D_T
Joining in

on ‎12-11-2021 10:48

Hello Virgin Media,

I don’t notice any issues with the connection, but I have noticed on my connection I keep getting T3 Timeouts on each upstream channel and Post RS Errors on every downstream channel which I believe I shouldn’t be getting. Please can you take a look at my connection and area to see if there are any current or past faults.

These power levels below are within spec aren’t they?

 

Downstream bonded channels

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

13870000003.740256 qam32
22030000004.540256 qam9
32110000004.540256 qam10
42190000004.340256 qam11
52270000004.440256 qam12
62350000004.340256 qam13
7243000000440256 qam14
8251000000440256 qam15
9259000000440256 qam16
10267000000440256 qam17
11275000000440256 qam18
122830000004.140256 qam19
13291000000440256 qam20
142990000004.540256 qam21
153070000004.540256 qam22
163150000004.540256 qam23
173230000004.640256 qam24
183310000004.540256 qam25
193390000004.440256 qam26
203470000004.140256 qam27
21355000000440256 qam28
22363000000440256 qam29
23371000000440256 qam30
243790000003.740256 qam31



Downstream bonded channels

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

1Locked40.36959
2Locked40.912058
3Locked40.311642
4Locked40.386121
5Locked40.37960
6Locked40.97262
7Locked40.310053
8Locked40.910462
9Locked40.310554
10Locked40.39763
11Locked40.911669
12Locked40.99158
13Locked40.98646
14Locked40.39752
15Locked40.312257
16Locked40.97450
17Locked40.98260
18Locked40.98654
19Locked40.38158
20Locked40.910573
21Locked40.37378
22Locked40.36271
23Locked40.38547
24Locked40.311353

 

Upstream bonded channels

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

13939999145512064 qam4
24619998345512064 qam3
35369999645512064 qam2
46029999845512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0070
2ATDMA0040
3ATDMA0040
4ATDMA0030



Thanks,

D_T

0 Kudos
20 REPLIES 20

D_T
Joining in
In response to Adduxi

on ‎12-11-2021 22:17

Hello Adduxi,

Thanks again for viewing and replying to my post.

How do these new set of stats look since I rebooted the hub just after 17:30?

 

Downstream bonded channels

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

13870000003.540256 qam32
22030000004.540256 qam9
32110000004.440256 qam10
42190000004.340256 qam11
52270000004.340256 qam12
62350000004.140256 qam13
7243000000440256 qam14
8251000000440256 qam15
9259000000440256 qam16
10267000000440256 qam17
11275000000440256 qam18
122830000004.140256 qam19
13291000000440256 qam20
142990000004.540256 qam21
153070000004.540256 qam22
163150000004.540256 qam23
173230000004.640256 qam24
183310000004.540256 qam25
193390000004.440256 qam26
203470000004.140256 qam27
21355000000440256 qam28
22363000000440256 qam29
233710000003.940256 qam30
243790000003.740256 qam31



Downstream bonded channels

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

1Locked40.300
2Locked40.950
3Locked40.360
4Locked40.350
5Locked40.350
6Locked40.950
7Locked40.350
8Locked40.350
9Locked40.340
10Locked40.360
11Locked40.360
12Locked40.950
13Locked40.350
14Locked40.350
15Locked40.950
16Locked40.950
17Locked40.940
18Locked40.960
19Locked40.940
20Locked40.370
21Locked40.350
22Locked40.950
23Locked40.360
24Locked40.350

 

Upstream bonded channels

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

13939996445512064 qam4
24620001245512064 qam3
35370001945512064 qam2
46029999845512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0000
4ATDMA0000



Thanks,

D_T

0 Kudos

D_T
Joining in

on ‎14-11-2021 22:17

How do these new set of stats look since I rebooted the hub just over 48 hours ago? I have noticed the Post RS Errors have been 0 on every downstream channel which is good, but unfortunately 2x T3 Timeouts have appeared, one on Saturday evening at 23:00 and another one sometime after that but the second one hasn’t been logged in the network log for some reason. The BQM graphs look ok too.

Downstream bonded channels

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

13870000003.540256 qam32
22030000004.640256 qam9
32110000004.540256 qam10
42190000004.440256 qam11
52270000004.340256 qam12
6235000000440256 qam13
72430000003.940256 qam14
82510000003.740256 qam15
9259000000440256 qam16
102670000004.340256 qam17
112750000004.340256 qam18
122830000004.540256 qam19
132910000004.340256 qam20
142990000004.840256 qam21
153070000004.840256 qam22
163150000004.840256 qam23
17323000000540256 qam24
183310000004.840256 qam25
193390000004.840256 qam26
203470000004.540256 qam27
213550000004.440256 qam28
223630000004.140256 qam29
23371000000440256 qam30
243790000003.740256 qam31



Downstream bonded channels

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

1Locked40.930
2Locked40.390
3Locked40.9150
4Locked40.9100
5Locked40.9120
6Locked40.9120
7Locked40.3110
8Locked40.980
9Locked40.380
10Locked40.3110
11Locked40.390
12Locked40.990
13Locked40.9130
14Locked40.9130
15Locked40.9100
16Locked40.9190
17Locked40.3230
18Locked40.9250
19Locked40.3240
20Locked40.9240
21Locked40.3100
22Locked40.990
23Locked40.390
24Locked40.3120
     



Upstream bonded channels

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

13939996445512064 qam4
24620001245512064 qam3
35370001945512064 qam2
46029999845512064 qam1



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000
3ATDMA0010
4ATDMA0010

 

Thanks,

D_T

0 Kudos

D_T
Joining in

on ‎14-11-2021 22:24

Below is the network log and screenshot of the upstream channels and T3 Timeouts. 

Network Log

Time Priority Description

14/11/2021 15:24:15noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2021 15:24:14ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/11/2021 23:00:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/11/2021 11:03:13noticeREMOTE login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/11/2021 05:20:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 13:10:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 13:10:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/11/2021 21:57:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2021 01:10:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2021 01:10:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/11/2021 17:35:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/11/2021 13:10:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/11/2021 13:10:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/10/2021 06:42:0criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/10/2021 01:10:25noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
30/10/2021 01:10:25ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
27/10/2021 04:10:9criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/10/2021 23:57:32noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/10/2021 23:57:32ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/10/2021 04:20:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

 

3714D118-9DBD-4812-A75E-F1901FBC8B7F.jpeg

Thanks,

D_T

0 Kudos

Zak_M
Forum Team (Retired)
Forum Team (Retired)
In response to D_T

on ‎17-11-2021 09:35

Good morning @D_T 

 

Welcome back to the forums & thank you for taking the time to post. 

 

I have managed to locate the account & have run some diagnostics & there is nothing of notes on the downstream or upstream etc 

 

Please keep monitoring this situation & if anything does deteriorate then please do let us know. 

 

Kind regards,

Zak_M

0 Kudos

D_T
Joining in
In response to Zak_M

on ‎21-11-2021 21:01

Hello Zak_M

Thanks for viewing and replying to my post as well as running some diagnostics.

I am still getting T3 Timeouts, any idea why when my power levels are within spec?

 

Network Log

Time Priority Description

21/11/2021 20:22:41noticeREMOTE login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/11/2021 03:52:11criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2021 20:47:22noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
20/11/2021 20:47:22ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/11/2021 13:17:10criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/11/2021 08:47:22noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/11/2021 08:47:22ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
15/11/2021 02:41:7criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2021 15:24:15noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/11/2021 15:24:14ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/11/2021 23:00:6criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/11/2021 11:03:13noticeREMOTE login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
11/11/2021 05:20:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 13:10:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/11/2021 13:10:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
07/11/2021 21:57:47criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2021 01:10:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
06/11/2021 01:10:26ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/11/2021 17:35:23criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
02/11/2021 13:10:26noticeDHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt060-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

 

Thanks,

D_T

0 Kudos

Sofia_B
Forum Team (Retired)
Forum Team (Retired)
In response to D_T

on ‎24-11-2021 08:51

Thanks for getting back to us @D_T. 

 

I'm very sorry to hear this, I appreciate this is frustrating and we apologise for any inconvenience caused. 

 

I'm going to send you a PM for more details so I can have a look into things for you. 

 

Please look out for a notification in the purple envelope located in the top right hand corner of the screen. 

 

Thanks, 

Sofia
Forum Team



New around here? To find out more about the Community check out our Getting Started guide
0 Kudos

D_T
Joining in
In response to Sofia_B

on ‎25-11-2021 14:08

Hi Sofia,

Thanks for replying back to my post, I’ll reply back to your private message now.

Please see below a screenshot of the T3 Timeouts, have you got any idea why I keep getting them as my power levels are within spec?

 

771B95B2-9C77-4D50-8910-7CFD76682FA8.jpeg

Thanks,

D_T

0 Kudos

Sofia_B
Forum Team (Retired)
Forum Team (Retired)
In response to D_T

on ‎26-11-2021 10:36

Thanks for chatting with me over PM @D_T. 

 

I apologise there are some issues with your power levels currently, I'm glad I was able to get a technician scheduled to rectify this for you. 

 

Please keep us updated on how the service performs are the visit. 

 

Thanks, 

 

 

Sofia
Forum Team



New around here? To find out more about the Community check out our Getting Started guide
0 Kudos

D_T
Joining in
In response to Sofia_B

on ‎26-11-2021 14:21

Hi Sofia,

Thanks again for replying back to my post, I’ll reply back to your private message now.

Thanks,

D_T

0 Kudos
Top