T3 timeouts and other fun

[Icantcrabhere]

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

1	539000000	0.5	38	256 qam	17
2	547000000	0.2	38	256 qam	18
3	555000000	0	38	256 qam	19
4	563000000	-0.2	38	256 qam	20
5	571000000	-0.5	38	256 qam	21
6	579000000	-0.4	38	256 qam	22
7	587000000	0	38	256 qam	23
8	595000000	0.5	38	256 qam	24
9	603000000	0.4	38	256 qam	25
10	611000000	0.2	38	256 qam	26
11	619000000	-0.4	38	256 qam	27
12	627000000	-0.5	38	256 qam	28
13	635000000	-0.5	37	256 qam	29
14	643000000	-0.2	38	256 qam	30
15	651000000	0.2	38	256 qam	31
16	659000000	0.5	38	256 qam	32
17	667000000	0.5	38	256 qam	33
18	675000000	0.2	38	256 qam	34
19	683000000	-0.2	38	256 qam	35
20	691000000	-0.2	38	256 qam	36
21	699000000	-0.4	37	256 qam	37
22	707000000	0	37	256 qam	38
23	715000000	-0.4	37	256 qam	39
24	723000000	-0.5	38	256 qam	40

Downstream bonded channels

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

1	Locked	38.6	30	0
2	Locked	38.6	38	0
3	Locked	38.9	44	0
4	Locked	38.9	43	0
5	Locked	38.6	68	0
6	Locked	38.9	47	0
7	Locked	38.6	37	0
8	Locked	38.6	22	0
9	Locked	38.9	18	0
10	Locked	38.6	61	0
11	Locked	38.6	90	0
12	Locked	38.6	125	0
13	Locked	37.6	121	0
14	Locked	38.6	78	0
15	Locked	38.9	58	0
16	Locked	38.6	61	0
17	Locked	38.6	48	0
18	Locked	38.6	78	0
19	Locked	38.6	126	0
20	Locked	38.6	136	0
21	Locked	37.6	110	0
22	Locked	37.6	78	0
23	Locked	37.6	108	0
24	Locked	38.6	124	0

Upstream bonded channels

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

1	49600258	45	5120	64 qam	1
2	36600000	44.3	5120	64 qam	3
3	23600000	43.8	5120	64 qam	5
4	30100258	44	5120	64 qam	4
5	43100000	44.5	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	1	0
2	ATDMA	0	0	1	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0
5	ATDMA	0	0	2	0

[Icantcrabhere]

Network Log

Time Priority Description

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

[Paul_DN]

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.

[Icantcrabhere]

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

1	49600025	44.8	5120	64 qam	1
2	36600000	44	5120	64 qam	3
3	23600000	43.8	5120	64 qam	5
4	30099961	43.8	5120	64 qam	4
5	43100000	44.3	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	5	0
2	ATDMA	0	0	2	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0
5	ATDMA	0	0	10	0

Downstream bonded channels

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

1	539000000	0.7	38	256 qam	17
2	547000000	0.4	38	256 qam	18
3	555000000	0.2	38	256 qam	19
4	563000000	0	38	256 qam	20
5	571000000	-0.2	38	256 qam	21
6	579000000	-0.2	38	256 qam	22
7	587000000	0.2	38	256 qam	23
8	595000000	0.7	38	256 qam	24
9	603000000	0.7	38	256 qam	25
10	611000000	0.4	38	256 qam	26
11	619000000	-0.2	38	256 qam	27
12	627000000	-0.2	38	256 qam	28
13	635000000	-0.4	38	256 qam	29
14	643000000	0	38	256 qam	30
15	651000000	0.5	38	256 qam	31
16	659000000	0.9	38	256 qam	32
17	667000000	0.7	38	256 qam	33
18	675000000	0.5	38	256 qam	34
19	683000000	0	38	256 qam	35
20	691000000	0	38	256 qam	36
21	699000000	0	37	256 qam	37
22	707000000	0.2	38	256 qam	38
23	715000000	0	37	256 qam	39
24	723000000	-0.2	38	256 qam	40

Downstream bonded channels

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

1	Locked	38.6	101	0
2	Locked	38.6	153	0
3	Locked	38.6	149	0
4	Locked	38.9	165	0
5	Locked	38.6	312	0
6	Locked	38.9	269	0
7	Locked	38.6	171	0
8	Locked	38.6	90	0
9	Locked	38.9	73	0
10	Locked	38.6	213	0
11	Locked	38.6	369	0
12	Locked	38.9	556	0
13	Locked	38.6	497	0
14	Locked	38.6	374	0
15	Locked	38.9	252	0
16	Locked	38.6	207	0
17	Locked	38.6	156	0
18	Locked	38.6	297	0
19	Locked	38.6	505	0
20	Locked	38.6	564	0
21	Locked	37.6	492	0
22	Locked	38.6	337	0
23	Locked	37.6	436	0
24	Locked	38.6	575	0

[Joseph_B]

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

[Icantcrabhere]

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

1	539000000	0.5	38	256 qam	17
2	547000000	0	38	256 qam	18
3	555000000	0	38	256 qam	19
4	563000000	-0.2	38	256 qam	20
5	571000000	-0.5	38	256 qam	21
6	579000000	-0.5	38	256 qam	22
7	587000000	0	38	256 qam	23
8	595000000	0.4	38	256 qam	24
9	603000000	0.4	38	256 qam	25
10	611000000	0.2	38	256 qam	26
11	619000000	-0.5	38	256 qam	27
12	627000000	-0.5	38	256 qam	28
13	635000000	-0.5	38	256 qam	29
14	643000000	-0.2	38	256 qam	30
15	651000000	0.2	38	256 qam	31
16	659000000	0.5	38	256 qam	32
17	667000000	0.5	38	256 qam	33
18	675000000	0.2	38	256 qam	34
19	683000000	-0.2	38	256 qam	35
20	691000000	-0.2	38	256 qam	36
21	699000000	-0.4	37	256 qam	37
22	707000000	-0.2	38	256 qam	38
23	715000000	-0.4	37	256 qam	39
24	723000000	-0.5	38	256 qam	40

Downstream bonded channels

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

1	Locked	38.6	137	0
2	Locked	38.6	49	0
3	Locked	38.9	49	0
4	Locked	38.6	62	0
5	Locked	38.9	105	0
6	Locked	38.9	91	0
7	Locked	38.6	57	0
8	Locked	38.6	34	0
9	Locked	38.9	34	0
10	Locked	38.6	69	0
11	Locked	38.6	120	0
12	Locked	38.9	195	0
13	Locked	38.6	170	0
14	Locked	38.6	154	0
15	Locked	38.6	68	0
16	Locked	38.6	90	0
17	Locked	38.6	62	0
18	Locked	38.6	87	0
19	Locked	38.6	145	0
20	Locked	38.9	162	0
21	Locked	37.6	161	0
22	Locked	38.6	135	0
23	Locked	37.6	142	0
24	Locked	38.6	165	0

Upstream bonded channels

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

1	49600000	45	5120	64 qam	1
2	36600000	44.3	5120	64 qam	3
3	23600000	44	5120	64 qam	5
4	30100000	44	5120	64 qam	4
5	43100000	44.5	5120	64 qam	2

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1	ATDMA	0	0	9	0
2	ATDMA	0	0	2	0
3	ATDMA	0	0	0	0
4	ATDMA	0	0	0	0
5	ATDMA	0	0	13	0

[IPFreely]

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.

[Icantcrabhere]

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.

[IPFreely]

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]

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.