on 08-11-2023 20:33
Just now, my internet started “buffering” on Netflix which it never does (I’m on the 1GB service, using a Hub 5) so thought I would check my logs and noticed lots of T3 errors and critical messages. Can someone pls explain what I need to do as I don’t understand it. I was getting T3 errors before and when I rebooted they all went away but slowly creep back in. I have a broadband monitor set up which I have attached as well as the logs. Please advise accordingly. Logs on messages below. Thanks all.
https://www.thinkbroadband.com/broadband/monitoring/quality/share/88b2215f41ff6a289f376f4055dd348fae...
on 08-11-2023 20:35
3.0 Downstream channels
1 | 147000000 | 6.2 | 40 | QAM 256 | 2 |
2 | 139000000 | 6.1 | 40 | QAM 256 | 1 |
3 | 155000000 | 6.1 | 40 | QAM 256 | 3 |
4 | 163000000 | 6 | 40 | QAM 256 | 4 |
5 | 171000000 | 5.7 | 40 | QAM 256 | 5 |
6 | 179000000 | 5.8 | 40 | QAM 256 | 6 |
7 | 187000000 | 5.8 | 40 | QAM 256 | 7 |
8 | 195000000 | 6.1 | 40 | QAM 256 | 8 |
9 | 203000000 | 5.8 | 40 | QAM 256 | 9 |
10 | 211000000 | 6 | 40 | QAM 256 | 10 |
11 | 219000000 | 5.8 | 40 | QAM 256 | 11 |
12 | 227000000 | 5.7 | 40 | QAM 256 | 12 |
13 | 235000000 | 5.7 | 40 | QAM 256 | 13 |
14 | 243000000 | 5.6 | 40 | QAM 256 | 14 |
15 | 251000000 | 5.5 | 40 | QAM 256 | 15 |
16 | 259000000 | 5.4 | 40 | QAM 256 | 16 |
17 | 267000000 | 5.6 | 40 | QAM 256 | 17 |
18 | 275000000 | 5.5 | 40 | QAM 256 | 18 |
19 | 283000000 | 5.7 | 40 | QAM 256 | 19 |
20 | 291000000 | 5.5 | 40 | QAM 256 | 20 |
21 | 299000000 | 6.2 | 40 | QAM 256 | 21 |
22 | 307000000 | 6.6 | 40 | QAM 256 | 22 |
23 | 315000000 | 7 | 41 | QAM 256 | 23 |
24 | 323000000 | 6.6 | 41 | QAM 256 | 24 |
25 | 363000000 | 6.2 | 41 | QAM 256 | 25 |
26 | 371000000 | 6.1 | 40 | QAM 256 | 26 |
27 | 379000000 | 6 | 40 | QAM 256 | 27 |
28 | 387000000 | 6.3 | 40 | QAM 256 | 28 |
29 | 395000000 | 6.1 | 41 | QAM 256 | 29 |
30 | 403000000 | 6.1 | 41 | QAM 256 | 30 |
31 | 411000000 | 5.5 | 41 | QAM 256 | 31 |
3.0 Downstream channels
1 | Locked | 40 | 1513125 | 452613 |
2 | Locked | 40 | 1210319 | 459351 |
3 | Locked | 40 | 1415268 | 302629 |
4 | Locked | 40 | 1329901 | 133803 |
5 | Locked | 40 | 2404475 | 82057 |
6 | Locked | 40 | 3589749 | 37201 |
7 | Locked | 40 | 788440 | 41116 |
8 | Locked | 40 | 397149 | 38345 |
9 | Locked | 40 | 329238 | 26694 |
10 | Locked | 40 | 287980 | 34659 |
11 | Locked | 40 | 256458 | 25120 |
12 | Locked | 40 | 248912 | 28550 |
13 | Locked | 40 | 277605 | 30296 |
14 | Locked | 40 | 200960 | 22047 |
15 | Locked | 40 | 215943 | 29287 |
16 | Locked | 40 | 149532 | 20117 |
17 | Locked | 40 | 126839 | 20063 |
18 | Locked | 40 | 135147 | 26522 |
19 | Locked | 40 | 94993 | 15124 |
20 | Locked | 40 | 108747 | 25908 |
21 | Locked | 40 | 82406 | 19569 |
22 | Locked | 40 | 61599 | 19055 |
23 | Locked | 41 | 66645 | 23592 |
24 | Locked | 41 | 59352 | 20947 |
25 | Locked | 41 | 47384 | 19837 |
26 | Locked | 40 | 44963 | 21044 |
27 | Locked | 40 | 43532 | 22478 |
28 | Locked | 40 | 42252 | 24790 |
29 | Locked | 41 | 45189 | 27568 |
30 | Locked | 41 | 42170 | 25364 |
31 | Locked | 41 | 33702 | 18968 |
3.1 Downstream channels
159 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
159 | Locked | 41 | 2.2 | 383043216 | 22987 |
on 08-11-2023 20:35
3.0 Upstream channels
0 | 49600000 | 47 | 5120 | QAM 32 | 1 |
1 | 43100000 | 46.8 | 5120 | QAM 32 | 2 |
2 | 36600000 | 47 | 5120 | QAM 32 | 3 |
3 | 30100000 | 47 | 5120 | QAM 32 | 4 |
4 | 23600000 | 46.8 | 5120 | QAM 32 | 5 |
3.0 Upstream channels
0 | ATDMA | 0 | 2 | 72 | 0 |
1 | ATDMA | 0 | 2 | 90 | 0 |
2 | ATDMA | 0 | 2 | 72 | 0 |
3 | ATDMA | 0 | 2 | 72 | 0 |
4 | ATDMA | 0 | 2 | 72 | 0 |
3.1 Upstream channels
6 | 10 | 41.0 | 2K | QAM 256 |
3.1 Upstream channels
6 | OFDMA | 200 | 74000000 | 12 | 0 |
on 08-11-2023 20:36
Network Log
08-11-2023 20:14:53 | notice | CM-STATUS message sent. Event Type Code: 24; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:30 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:24 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:12 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:12 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:12 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:01 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:13:00 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 1.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:12:54 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:12:45 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 20:12:45 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:53:44 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:53:44 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:43:39 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:43:39 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:33:33 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:33:33 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:26:38 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:26:38 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:26:38 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:26:18 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
08-11-2023 19:26:18 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 10-11-2023 20:51
I have checked the area Matt and can confirm that there is an SNR outage and this is due to be resolved on the 15th November 2023 - The fault ref is F011016336 - Chris.
on 19-11-2023 10:27
Thanks for this. I have still been experiencing internet blackouts and buffering. I was watching Netflix last night and all of a sudden it started buffering for ages then an error message came up to say I had been disconnected from the internet. It took a while to reconnect afterwards. Today, the same happened on YouTube. I looked at the Hub5 and it was flashing red. It did reconnect itself after about 10 mins but it becoming a nuisance now. I do think something is not quite right with the Hub. An engineer came out a while ago due to the same issues but didn’t really do much. He said he didn’t know why it kept timing out or losing internet. Can someone please look into this as it’s getting frustrating now. Many thanks.
on 19-11-2023 11:09
I’ve just checked the upload log again and getting consistent T3 errors again??
Network Log
19-11-2023 10:35:43 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 3;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:43 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:43 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:23 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:23 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:23 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 2;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:03 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:03 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:35:03 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:34:43 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:34:43 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 0;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:32:43 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:32:23 | critical | 16 consecutive T3 timeouts while trying to range on upstream channel 4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:32:23 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:31:24 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:16:04 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:16:04 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:15:09 | notice | US profile assignment change. US Chan ID: 6; Previous Profile: 13; New Profile: 11 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:15:09 | warning | DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:15:06 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
19-11-2023 10:14:59 | warning | Dynamic Range Window violation |
19-11-2023 10:14:59 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:59 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:59 | warning | REG-RSP-MP Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:59 | warning | Dynamic Range Window violation |
19-11-2023 10:14:59 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:59 | warning | RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:59 | warning | Dynamic Range Window violation |
19-11-2023 10:14:59 | warning | Dynamic Range Window violation |
19-11-2023 10:14:54 | notice | DS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:47 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
19-11-2023 10:14:45 | notice | Honoring MDD; IP provisioning mode = IPv4 |
on 19-11-2023 11:22
Check on 0800 561 0061 to see if a fault is still reported in your area.
Your problems are due to a lot of noise on the signal. This is due to a fault either outside on the network, or inside your house. Check that all your coax connections are done up tight.
on 19-11-2023 11:27
Just called the number and it says there are no issues with broadband in my area. Could this be due to a faulty Hub? All my wires are in tight. I’ve rebooted many times and it settles down but then creeps back up again. Don’t seem to be getting anywhere. Last engineer that came out didn’t really seem to know what he was doing and told me to unplug my Ethernet cables for a few days and then plug them back in, which didn’t make any difference.
on 21-11-2023 11:45
Hello mattymatt1980,
Thank you very much for joining our Community.
Can I just apologise for continued issues with your broadband connection
We can run a few tests from here and check on your equipment.
Sadly its not showing anything wrong, So I will need to send you a private message to gain account access and run further tests.
If you can check the envelope top right of your screen that would be great.
Regards
Gareth_L