on 01-07-2021 20:51
Recently my hub has started regularly losing its internet connection for 5-10 minutes - the downtime is always accompanied by one of these 'No Ranging Response received - T3' critical logs. How do I fix this?
PS: Some of these log times don't look right... 01/01/1970 is when the Unix epoch first started
Time Priority Description
01/01/1970 00:01:38 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/07/2021 13:22:1 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:37 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/07/2021 11:26:17 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/07/2021 00:49:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/06/2021 00:02:7 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/06/2021 20:18:25 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/06/2021 17:04:36 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/06/2021 11:58:19 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/06/2021 19:02:2 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/06/2021 19:01:22 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
18/06/2021 15:09:28 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/06/2021 02:13:54 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 14:24:45 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 01:02:29 | critical | SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 01:02:11 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 01:02:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 01:02:0 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 01:01:57 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/06/2021 01:01:42 | Warning! | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 02-07-2021 07:47
on 02-07-2021 09:59
1 | 203000000 | 9.5 | 38 | 256 qam | 9 |
2 | 139000000 | 10.1 | 37 | 256 qam | 1 |
3 | 147000000 | 10.1 | 38 | 256 qam | 2 |
4 | 155000000 | 10 | 38 | 256 qam | 3 |
5 | 163000000 | 10.1 | 38 | 256 qam | 4 |
6 | 171000000 | 10.1 | 38 | 256 qam | 5 |
7 | 179000000 | 10.1 | 38 | 256 qam | 6 |
8 | 187000000 | 10.1 | 38 | 256 qam | 7 |
9 | 195000000 | 9.8 | 38 | 256 qam | 8 |
10 | 211000000 | 9.5 | 38 | 256 qam | 10 |
11 | 219000000 | 9.5 | 38 | 256 qam | 11 |
12 | 227000000 | 9.5 | 38 | 256 qam | 12 |
13 | 235000000 | 9.4 | 38 | 256 qam | 13 |
14 | 243000000 | 9.1 | 38 | 256 qam | 14 |
15 | 251000000 | 9.1 | 38 | 256 qam | 15 |
16 | 259000000 | 9.5 | 38 | 256 qam | 16 |
17 | 267000000 | 9.8 | 38 | 256 qam | 17 |
18 | 275000000 | 9.6 | 38 | 256 qam | 18 |
19 | 283000000 | 9.6 | 38 | 256 qam | 19 |
20 | 291000000 | 9.8 | 38 | 256 qam | 20 |
21 | 299000000 | 10.5 | 38 | 256 qam | 21 |
22 | 307000000 | 10.6 | 38 | 256 qam | 22 |
23 | 315000000 | 10.5 | 38 | 256 qam | 23 |
24 | 323000000 | 10.5 | 38 | 256 qam | 24 |
1 | Locked | 38.9 | 7 | 0 |
2 | Locked | 37.6 | 2 | 0 |
3 | Locked | 38.6 | 6 | 0 |
4 | Locked | 38.6 | 6 | 0 |
5 | Locked | 38.6 | 22 | 0 |
6 | Locked | 38.6 | 22 | 0 |
7 | Locked | 38.6 | 16 | 0 |
8 | Locked | 38.6 | 19 | 0 |
9 | Locked | 38.6 | 8 | 0 |
10 | Locked | 38.6 | 8 | 0 |
11 | Locked | 38.9 | 7 | 0 |
12 | Locked | 38.6 | 9 | 0 |
13 | Locked | 38.6 | 1 | 0 |
14 | Locked | 38.6 | 8 | 0 |
15 | Locked | 38.9 | 2 | 0 |
16 | Locked | 38.9 | 7 | 0 |
17 | Locked | 38.9 | 6 | 0 |
18 | Locked | 38.9 | 6 | 0 |
19 | Locked | 38.6 | 5 | 0 |
20 | Locked | 38.9 | 5 | 0 |
21 | Locked | 38.6 | 7 | 0 |
22 | Locked | 38.9 | 21 | 0 |
23 | Locked | 38.9 | 19 | 0 |
24 | Locked | 38.6 | 19 | 0 |
Upstream bonded channelsChannel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 39400000 | 41.8 | 5120 | 64 qam | 9 |
2 | 46200000 | 41.8 | 5120 | 64 qam | 8 |
3 | 25800000 | 41.3 | 5120 | 64 qam | 12 |
4 | 32600000 | 41.8 | 5120 | 64 qam | 10 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 02-07-2021 10:01
on 04-07-2021 12:49
Hi @chuck205
How is the service today? Can you perform one quick reboot so I can review the level change after this?
Regards
on 04-07-2021 13:23
It's been fine today so far.
Sure, let me know when you want it rebooted.
on 04-07-2021 13:29
Perfect, just do that now for me and let me know once done.
Regards
on 04-07-2021 13:36
on 04-07-2021 14:57
Perfect, thank you. I'm going to private message you now to collect a few more details if that's okay?
Regards
on 04-07-2021 16:00
Best to post another set of stats. If the downstream levels are still too high, but your service is currently ok, you may still be storing up trouble for the future.