on 15-03-2022 10:23
Morning all,
Keep getting an issue where the ethernet connection to my Hub 3.0 is intermittently dropping and then connecting again. It happens a few times and then nothing for a few weeks/months but I've noticed it happening again the last few days.
From what I can see, the lights on the hub don't change when the dropouts happen and the wifi seems to be unaffected in the sense I haven't noticed it drop at the same time as the ethernet connection...
Restarting the hub didn't seem to do anything either.
My data as follows:
Downstream
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 202750000 | 3.5 | 38 | 256 qam | 9 |
2 | 138750000 | 2 | 38 | 256 qam | 1 |
3 | 146750000 | 2.2 | 38 | 256 qam | 2 |
4 | 154750000 | 2.4 | 38 | 256 qam | 3 |
5 | 162750000 | 2.5 | 40 | 256 qam | 4 |
6 | 170750000 | 2.9 | 38 | 256 qam | 5 |
7 | 178750000 | 3 | 38 | 256 qam | 6 |
8 | 186750000 | 3.4 | 38 | 256 qam | 7 |
9 | 194750000 | 3.5 | 40 | 256 qam | 8 |
10 | 210750000 | 3.4 | 40 | 256 qam | 10 |
11 | 218750000 | 3.2 | 40 | 256 qam | 11 |
12 | 226750000 | 3.4 | 38 | 256 qam | 12 |
13 | 234750000 | 3 | 40 | 256 qam | 13 |
14 | 242750000 | 2.5 | 40 | 256 qam | 14 |
15 | 250750000 | 1.7 | 40 | 256 qam | 15 |
16 | 258750000 | 2.5 | 38 | 256 qam | 16 |
17 | 266750000 | 3 | 40 | 256 qam | 17 |
18 | 274750000 | 2.2 | 38 | 256 qam | 18 |
19 | 282750000 | 4.3 | 38 | 256 qam | 19 |
20 | 290750000 | 5.6 | 40 | 256 qam | 20 |
21 | 298750000 | 5.6 | 40 | 256 qam | 21 |
22 | 306750000 | 5.6 | 40 | 256 qam | 22 |
23 | 314750000 | 5.5 | 40 | 256 qam | 23 |
24 | 322750000 | 5.6 | 40 | 256 qam | 24 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 19 | 0 |
2 | Locked | 38.6 | 13 | 0 |
3 | Locked | 38.9 | 4 | 0 |
4 | Locked | 38.9 | 9 | 0 |
5 | Locked | 40.3 | 6 | 0 |
6 | Locked | 38.6 | 6 | 0 |
7 | Locked | 38.9 | 16 | 0 |
8 | Locked | 38.9 | 5 | 0 |
9 | Locked | 40.3 | 4 | 0 |
10 | Locked | 40.3 | 6 | 0 |
11 | Locked | 40.9 | 5 | 0 |
12 | Locked | 38.9 | 4 | 0 |
13 | Locked | 40.3 | 4 | 0 |
14 | Locked | 40.3 | 13 | 0 |
15 | Locked | 40.3 | 5 | 0 |
16 | Locked | 38.6 | 8 | 0 |
17 | Locked | 40.3 | 14 | 0 |
18 | Locked | 38.9 | 2 | 0 |
19 | Locked | 38.9 | 6 | 0 |
20 | Locked | 40.3 | 1 | 0 |
21 | Locked | 40.3 | 6 | 0 |
22 | Locked | 40.3 | 4 | 0 |
23 | Locked | 40.3 | 19 | 0 |
24 | Locked | 40.3 | 9 | 0 |
Upstream
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 47.5 | 5120 | 64 qam | 4 |
2 | 46200000 | 47.3 | 5120 | 64 qam | 1 |
3 | 39400000 | 46.8 | 5120 | 64 qam | 2 |
4 | 32600000 | 47.3 | 5120 | 64 qam | 3 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
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 15-03-2022 10:24
Network log
Time Priority Description
13/03/2022 12:46:34 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/03/2022 20:18:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/03/2022 19:55:54 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/03/2022 10:29:32 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/03/2022 20:18:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 14:03:35 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/03/2022 08:18:28 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
27/02/2022 13:37:55 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/02/2022 20:18:28 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2022 12:28:3 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/02/2022 15:40:58 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 20:23:33 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 19:25:57 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 19:25:55 | Error | DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
15/02/2022 23:55:57 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/02/2022 11:34:1 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/02/2022 11:55:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/02/2022 07:38:11 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
08/02/2022 23:55:56 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
07/02/2022 03:35:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 15-03-2022 11:17
Live graph for broadband monitor
https://www.thinkbroadband.com/broadband/monitoring/quality/share/16956441c771148dd45c5e3bca22aa939ea26f35
on 17-03-2022 11:35
Hi @chrisw991
Thanks for posting on our community forum!
Sorry to hear about your issue, I am going to drop you a private message now to collect some more details.
Please keep an eye on your inbox!
Regards