cancel
Showing results for 
Search instead for 
Did you mean: 

T3 timeouts and other fun

Icantcrabhere
Superfast

Hi there,
noticed over the past few weeks that i'm getting random bursts of T3 timeouts,
also yesterday in the morning, I lost a whole upstream channel - rebooting restored this, however it still isn't a good sign.

I've checked both the online fault checker and the phone version:

Yesterday the online fault checker showed no issues in my area. - then I clicked the "test your hub" option.
It showed "intermittent signal in your area" - but today it's back to normal, showing just the standard "We couldn't find an issue, let's try resetting the hub!" style message.
However this is far from the case, clearly.

I'll share my fresh stats from the restart yesterday, these are from after 12PM yesterday afternoon.

I'll have to split the post due to character limits.

Firstly, BQM live graph:(Nothing much to see here, just for future reference)

https://www.thinkbroadband.com/broadband/monitoring/quality/share/1700d27c199ce3ea214d66ce063ff9f395507b3e

 

Downstream bonded channels

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

15390000000.538256 qam17
25470000000.238256 qam18
3555000000038256 qam19
4563000000-0.238256 qam20
5571000000-0.538256 qam21
6579000000-0.438256 qam22
7587000000038256 qam23
85950000000.538256 qam24
96030000000.438256 qam25
106110000000.238256 qam26
11619000000-0.438256 qam27
12627000000-0.538256 qam28
13635000000-0.537256 qam29
14643000000-0.238256 qam30
156510000000.238256 qam31
166590000000.538256 qam32
176670000000.538256 qam33
186750000000.238256 qam34
19683000000-0.238256 qam35
20691000000-0.238256 qam36
21699000000-0.437256 qam37
22707000000037256 qam38
23715000000-0.437256 qam39
24723000000-0.538256 qam40



Downstream bonded channels

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

1Locked38.6300
2Locked38.6380
3Locked38.9440
4Locked38.9430
5Locked38.6680
6Locked38.9470
7Locked38.6370
8Locked38.6220
9Locked38.9180
10Locked38.6610
11Locked38.6900
12Locked38.61250
13Locked37.61210
14Locked38.6780
15Locked38.9580
16Locked38.6610
17Locked38.6480
18Locked38.6780
19Locked38.61260
20Locked38.61360
21Locked37.61100
22Locked37.6780
23Locked37.61080
24Locked38.61240

Upstream bonded channels

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

14960025845512064 qam1
23660000044.3512064 qam3
32360000043.8512064 qam5
43010025844512064 qam4
54310000044.5512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0010
2ATDMA0010
3ATDMA0000
4ATDMA0000
5ATDMA0020

 

41 REPLIES 41

Icantcrabhere
Superfast

Network Log

Time Priority Description

05/04/2024 21:13:30criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:40:27criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:40:3criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:40:3criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:33:38criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:33:14criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:33:14criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:26:50criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:26:26criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:26:26criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:20:1criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:19:37criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:19:37criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:13:13criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:12:48criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:12:48criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:06:24criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:06:0criticalUnicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 10:06:0criticalRanging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
05/04/2024 09:59:35critical

Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

As noted at the top of my post, you can see where the channel dropped out with the "Started Unicast Maintenance Ranging" messages being spammed.
I know a few T3's is completely fine, i'm more worried about the bursts they've been coming in recently.

I'd love this to get looked into/resolved - cheers in advance!



Hi Icantcrabhere,

Thank you for reaching out to us in our community and welcome back, sorry to see you have been suffering with T3 Timeouts, I was able to locate you on our system with the details we have for you and cannot see any current issues, it does look like you may have a 3rd party Router and have ours in Modem mode which means there is things we cannot see, how have things been since Saturday?

Regards

Paul.

Hi there, Paul!
Thanks for the reply.
T3's definitely stacked up a bit since then,
however so far today it's looking stable (for now),

I'll continue to monitor over the next few days.

Upstream bonded channels

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

14960002544.8512064 qam1
23660000044512064 qam3
32360000043.8512064 qam5
43009996143.8512064 qam4
54310000044.3512064 qam2



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0050
2ATDMA0020
3ATDMA0000
4ATDMA0000
5ATDMA00100

Downstream bonded channels

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

15390000000.738256 qam17
25470000000.438256 qam18
35550000000.238256 qam19
4563000000038256 qam20
5571000000-0.238256 qam21
6579000000-0.238256 qam22
75870000000.238256 qam23
85950000000.738256 qam24
96030000000.738256 qam25
106110000000.438256 qam26
11619000000-0.238256 qam27
12627000000-0.238256 qam28
13635000000-0.438256 qam29
14643000000038256 qam30
156510000000.538256 qam31
166590000000.938256 qam32
176670000000.738256 qam33
186750000000.538256 qam34
19683000000038256 qam35
20691000000038256 qam36
21699000000037256 qam37
227070000000.238256 qam38
23715000000037256 qam39
24723000000-0.238256 qam40



Downstream bonded channels

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

1Locked38.61010
2Locked38.61530
3Locked38.61490
4Locked38.91650
5Locked38.63120
6Locked38.92690
7Locked38.61710
8Locked38.6900
9Locked38.9730
10Locked38.62130
11Locked38.63690
12Locked38.95560
13Locked38.64970
14Locked38.63740
15Locked38.92520
16Locked38.62070
17Locked38.61560
18Locked38.62970
19Locked38.65050
20Locked38.65640
21Locked37.64920
22Locked38.63370
23Locked37.64360
24Locked38.65750

Hey @Icantcrabhere,

Do let us know if stuff like this changes and let us know with regards to this, we will then look into it further for you.

Joe

Hi there!,

The T3's still seem to be climbing at a rate which isn't exactly "great"
Also seems that my "Pre-RS error" count reset itself without any input from myself, which is odd. - i'm not sure why they'd do that.

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
15390000000.538256 qam17
2547000000038256 qam18
3555000000038256 qam19
4563000000-0.238256 qam20
5571000000-0.538256 qam21
6579000000-0.538256 qam22
7587000000038256 qam23
85950000000.438256 qam24
96030000000.438256 qam25
106110000000.238256 qam26
11619000000-0.538256 qam27
12627000000-0.538256 qam28
13635000000-0.538256 qam29
14643000000-0.238256 qam30
156510000000.238256 qam31
166590000000.538256 qam32
176670000000.538256 qam33
186750000000.238256 qam34
19683000000-0.238256 qam35
20691000000-0.238256 qam36
21699000000-0.437256 qam37
22707000000-0.238256 qam38
23715000000-0.437256 qam39
24723000000-0.538256 qam40


Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked38.61370
2Locked38.6490
3Locked38.9490
4Locked38.6620
5Locked38.91050
6Locked38.9910
7Locked38.6570
8Locked38.6340
9Locked38.9340
10Locked38.6690
11Locked38.61200
12Locked38.91950
13Locked38.61700
14Locked38.61540
15Locked38.6680
16Locked38.6900
17Locked38.6620
18Locked38.6870
19Locked38.61450
20Locked38.91620
21Locked37.61610
22Locked38.61350
23Locked37.61420
24Locked38.61650

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
14960000045512064 qam1
23660000044.3512064 qam3
32360000044512064 qam5
43010000044512064 qam4
54310000044.5512064 qam2


Upstream bonded channels

 

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0090
2ATDMA0020
3ATDMA0000
4ATDMA0000
5ATDMA0013

0

IPFreely
Fibre optic

The RS count may have reset because you were disconnected. Looks like you've upstream noise on the channel centered at 43.1 MHz, probably towards the higher end, with noise also above and, to a lesser extent, below there.

This should show in the upstream SNR values. These do not require you to be in router mode to be obtained. This will be impacting everyone in your local area if this is the case.

Hi there, cheers for the reply - i appreciate it! 🙂
the RS coun't shouldn't have reset, i've had no full disconnects - which is why I was confused by this

I assumed it'd be noise of some sort, hadn't seen any upstream channels fall below 64QAM so I was truly unsure.

Interesting. May actually be very localised. Modulation drops when the error rate and SNR across all modems hit a threshold. If only one or a few are having issues modulation might stay high. 

Sephiroth
Alessandro Volta

Just to respond to what the Forum Team observed about modem mode, and to back up what IPFreely said (he really knows his a stuff), if it’s T3 events that are of concern, there’s nothing other than your hub that they need to look at.  The behaviour of your router is totally irrelevant.

The stats are a point-in-time snapshot and the only pointer towards possible modulation changes is the T3 event count.  I note that no T4 events are reported and that there is thus no history recorded of 16x T3 on the trot that would have caused a reset. 

You haven’t said what real-life issues you are experiencing.  T3 events normally occur in the background and shouldn’t affect your experience.

Seph - ( DEFROCKED - My advice is at your risk)