a month ago - last edited a month ago
Having a slight issue today with one of the downstream channels going crazy with errors. I've rebooted and it does the same thing. It's been the last hour now. No issues on any of the other channels and it hasn't gone offline or anything. But checking the test it does throw up the area having intermittent signal issues. But this one channel does keep going up and up in errors every time I check on it.
I'm guessing it's our turn for the oversubscribed area faults.
a month ago
1 | 331000000 | 2.4 | 38 | 256 qam | 25 |
2 | 139000000 | 2.9 | 37 | 256 qam | 1 |
3 | 147000000 | 2.9 | 37 | 256 qam | 2 |
4 | 155000000 | 2.7 | 37 | 256 qam | 3 |
5 | 163000000 | 2.7 | 37 | 256 qam | 4 |
6 | 171000000 | 2.5 | 37 | 256 qam | 5 |
7 | 179000000 | 2.7 | 37 | 256 qam | 6 |
8 | 187000000 | 2.7 | 37 | 256 qam | 7 |
9 | 195000000 | 2.5 | 38 | 256 qam | 8 |
10 | 203000000 | 2.2 | 37 | 256 qam | 9 |
11 | 211000000 | 1.7 | 37 | 256 qam | 10 |
12 | 219000000 | 1.5 | 38 | 256 qam | 11 |
13 | 227000000 | 1.5 | 37 | 256 qam | 12 |
14 | 235000000 | 1 | 37 | 256 qam | 13 |
15 | 243000000 | 0.4 | 37 | 256 qam | 14 |
16 | 251000000 | 0 | 37 | 256 qam | 15 |
17 | 259000000 | 0 | 37 | 256 qam | 16 |
18 | 339000000 | 2.5 | 38 | 256 qam | 26 |
19 | 347000000 | 2.7 | 38 | 256 qam | 27 |
20 | 355000000 | 2.9 | 38 | 256 qam | 28 |
21 | 363000000 | 3.2 | 38 | 256 qam | 29 |
22 | 371000000 | 3 | 38 | 256 qam | 30 |
23 | 379000000 | 1.7 | 38 | 256 qam | 31 |
24 | 387000000 | 0.9 | 38 | 256 qam | 32 |
1 | Locked | 38.9 | 3 | 0 |
2 | Locked | 37.6 | 0 | 0 |
3 | Locked | 37.6 | 4 | 0 |
4 | Locked | 37.3 | 6 | 0 |
5 | Locked | 37.3 | 16 | 0 |
6 | Locked | 37.6 | 16 | 0 |
7 | Locked | 37.6 | 21 | 0 |
8 | Locked | 37.6 | 19 | 0 |
9 | Locked | 38.6 | 6 | 0 |
10 | Locked | 37.6 | 5 | 0 |
11 | Locked | 37.6 | 5 | 0 |
12 | Locked | 38.6 | 5 | 0 |
13 | Locked | 37.6 | 6 | 0 |
14 | Locked | 37.6 | 5 | 0 |
15 | Locked | 37.3 | 6 | 0 |
16 | Locked | 37.6 | 0 | 0 |
17 | Locked | 37.6 | 0 | 0 |
18 | Locked | 38.6 | 1 | 0 |
19 | Locked | 38.6 | 19 | 0 |
20 | Locked | 38.6 | 18 | 0 |
21 | Locked | 38.9 | 5 | 0 |
22 | Locked | 38.6 | 5 | 0 |
23 | Locked | 38.6 | 0 | 0 |
24 | Locked | 38.9 | 1466 | 26771 |
a month ago
1 | 36599981 | 47 | 5120 | 64 qam | 3 |
2 | 23599993 | 47 | 5120 | 64 qam | 5 |
3 | 30099981 | 47 | 5120 | 64 qam | 4 |
4 | 43099998 | 47 | 5120 | 64 qam | 2 |
5 | 49600009 | 47 | 5120 | 64 qam | 1 |
1 | ATDMA | 0 | 0 | 0 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
5 | ATDMA | 0 | 0 | 0 | 0 |
a month ago
09/11/2024 11:18:46 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/11/2024 11:08:26 | Warning! | TCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/11/2024 11:08:26 | Warning! | Initializing Channel Timeout Expires - Time the CM can perform initial ranging on all upstream channels in the TCS has expired;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
09/11/2024 10:16:35 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/11/2024 23:54:47 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
04/11/2024 19:47:39 | 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; |
04/11/2024 19:47:39 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/11/2024 10:55:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/11/2024 20:50:40 | 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; |
01/11/2024 20:50:40 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/10/2024 19:18:5 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/10/2024 14:21:44 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/10/2024 10:21:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/10/2024 05:44:38 | 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; |
28/10/2024 05:44:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/10/2024 13:39:59 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 15:41:31 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 08:12:48 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
22/10/2024 01:26:17 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/10/2024 02:26:32 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
a month ago - last edited a month ago
a month ago
Hi @Mr-Hare
Thanks for posting and welcome back to the community.
Sorry to hear of any Broadband issues. We've done a check today and everything does seem sorted for you.
Please do reach back out if you need further help.
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill