13-08-2021 13:43 - edited 13-08-2021 13:44
Connection been a bit dodgy lately.... I know there was some known service issues in my area not so long ago but all seems ok now with that.
Last time I had this engineer fitted some sort of booster but seems to have dropped off recently and speeds sometimes a bit lower than I usually get (I'm on 350) I realise that's dependant on a lot of factors but I test from same kit.
Downstream bonded channels
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 171000000 | -1.2 | 37 | 256 qam | 5 |
2 | 139000000 | -1.7 | 37 | 256 qam | 1 |
3 | 147000000 | -1.2 | 37 | 256 qam | 2 |
4 | 155000000 | -1.2 | 37 | 256 qam | 3 |
5 | 163000000 | -1.2 | 37 | 256 qam | 4 |
6 | 179000000 | -1.2 | 37 | 256 qam | 6 |
7 | 187000000 | -1.2 | 37 | 256 qam | 7 |
8 | 195000000 | -1 | 38 | 256 qam | 8 |
9 | 203000000 | -1 | 38 | 256 qam | 9 |
10 | 211000000 | -1 | 38 | 256 qam | 10 |
11 | 219000000 | -1 | 38 | 256 qam | 11 |
12 | 227000000 | -1.2 | 37 | 256 qam | 12 |
13 | 235000000 | -1.4 | 37 | 256 qam | 13 |
14 | 243000000 | -1.4 | 38 | 256 qam | 14 |
15 | 251000000 | -1 | 38 | 256 qam | 15 |
16 | 259000000 | -1 | 38 | 256 qam | 16 |
17 | 267000000 | -1 | 38 | 256 qam | 17 |
18 | 275000000 | -1 | 37 | 256 qam | 18 |
19 | 283000000 | -1 | 38 | 256 qam | 19 |
20 | 291000000 | -0.7 | 37 | 256 qam | 20 |
21 | 299000000 | -0.2 | 37 | 256 qam | 21 |
22 | 307000000 | 0 | 37 | 256 qam | 22 |
23 | 315000000 | 0.2 | 38 | 256 qam | 23 |
24 | 323000000 | 0.4 | 37 | 256 qam | 24 |
Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 37.6 | 361 | 0 |
2 | Locked | 37.6 | 1068 | 0 |
3 | Locked | 37.6 | 728 | 0 |
4 | Locked | 37.3 | 583 | 0 |
5 | Locked | 37.6 | 477 | 0 |
6 | Locked | 37.6 | 273 | 0 |
7 | Locked | 37.6 | 260 | 0 |
8 | Locked | 38.6 | 183 | 0 |
9 | Locked | 38.9 | 165 | 0 |
10 | Locked | 38.6 | 174 | 0 |
11 | Locked | 38.6 | 191 | 0 |
12 | Locked | 37.6 | 225 | 0 |
13 | Locked | 37.3 | 292 | 0 |
14 | Locked | 38.6 | 328 | 0 |
15 | Locked | 38.6 | 259 | 0 |
16 | Locked | 38.6 | 282 | 0 |
17 | Locked | 38.6 | 360 | 0 |
18 | Locked | 37.6 | 411 | 0 |
19 | Locked | 38.6 | 509 | 0 |
20 | Locked | 37.6 | 489 | 0 |
21 | Locked | 37.3 | 434 | 0 |
22 | Locked | 37.6 | 343 | 0 |
23 | Locked | 38.6 | 302 | 0 |
24 | Locked | 37.6 | 230 | 0 |
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 46200000 | 44.3 | 5120 | 64 qam | 11 |
2 | 39400000 | 43.8 | 5120 | 64 qam | 12 |
3 | 53700000 | 44.3 | 5120 | 64 qam | 10 |
4 | 60300000 | 45.8 | 5120 | 64 qam | 9 |
Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | ATDMA | 0 | 0 | 2 | 0 |
2 | ATDMA | 0 | 0 | 54 | 0 |
3 | ATDMA | 0 | 0 | 17 | 0 |
4 | ATDMA | 0 | 0 | 6 | 0 |
on 13-08-2021 13:44
Network Log
Time Priority Description
13/08/2021 13:31:45 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
13/08/2021 11:02:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/08/2021 10:14:33 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062+voc-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/08/2021 10:14:33 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 10:45:56 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:18:32 | critical | Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:18:32 | critical | Ranging Request Retries exhausted;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:18:9 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:18:9 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:17:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:17:7 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:16:36 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:16:36 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:16:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:16:27 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:15:27 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:15:27 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:15:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:15:20 | critical | Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/08/2021 09:14:30 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 13-08-2021 13:54
on 13-08-2021 15:08
The router was rebooted couple days ago, rebooted a few times recently.
There is "no known issues" in my area currently but at the beginning of the week I think it was there were some issues being shown in the service status.
on 15-08-2021 16:07
Hi CRNeo,
Thanks for your post and apologies to hear you are having an issue with your internet connection.
Checking things at this end, all is looking good within the area. Your Hub stats are also good and not showing any issues.
I have sent a hit down the line to try and resolve this. Can you please reboot the hub and then monitor for the next 24 hours to see if you have any more issues.
Keep us posted.
Thanks,