on 29-06-2024 19:10
Hi All,
This is a last ditch effort to get to any conclusion on what is currently happening with my broadband,
It all started around the 7th/8th of this month, i would just randomly have hundreds of disconnects throughout the day, i contacted virgin media customer services and eventually an engineer was booked for the 12th June, When the engineer arrived he could clearly see that there was an issue, he went to make a phone call and came back and said leave it with us.
I then waited over a week and the issue didnt seem to be fixed and nothing was different, no contact from virgin media, at this point i raised an complain with virgin media and rang them up on Friday 21st, I got another engeineer to come out and he said the problem was still there, which i believe the first engineer just up and left and did nothing, he cleaned the outside cables and all seemed to be fine for a day or two, on Thursday the 27th the issue came back and it was doing the exact same thing, i rang virgin media on Friday 28th and got another engineer to come out this morning (29th), He checked the cables and they were all fine so this time he replaced the router, however now the problem is worse and seems to be happening more often than before, i feel like i am at a dead end and minght have to cancel my contract and go somewhere else as my issue seems impossible to resolve.
Below is the logs i keep getting which are a bunch of error codes, these appear when the issue happens every time.
29-06-2024 18:58:44 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:58:14 | notice | GUI Login Status - Login Success from LAN interface |
29-06-2024 18:58:14 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 26 33 35 43 46 47; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:44 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:44 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 26 33 35 43 46 47; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:24 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:24 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 26 33 35 43 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:14 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 26 33 35 43 46 47; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:14 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:12 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:57:11 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:55 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:54 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 26 33 35 43 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:49 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:49 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:49 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 26 35 43 46 47; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:44 | critical | Started Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:24 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 26 35 43 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:19 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 26 35 43 46 47; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:56:17 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:54:07 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 35 43 46 47; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:54:04 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 35 43 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:54:00 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 35 43 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:53:55 | warning | MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:53:35 | notice | CM-STATUS message sent. Event Type Code: 16; Chan ID: 159; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:52:48 | notice | CM-STATUS message sent. Event Type Code: 4; Chan ID: 35 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:52:48 | notice | CM-STATUS message sent. Event Type Code: 5; Chan ID: 35 46; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:52:26 | notice | REGISTRATION COMPLETE - Waiting for Operational status |
29-06-2024 18:52:20 | 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; |
29-06-2024 18:52:20 | warning | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:52:14 | 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; |
29-06-2024 18:52:06 | warning | DHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
29-06-2024 18:52:04 | notice | Honoring MDD; IP provisioning mode = IPv4 |
29-06-2024 18:50:48 | notice | GUI Login Status - Login Success from LAN interface |
29-06-2024 18:40:13 | notice | GUI Login Status - Login Success from LAN interface |
29-06-2024 18:39:25 | notice | GUI Login Status - Login Success from LAN interface |
on 30-06-2024 11:16
The log tab of the VM Hub's often contains lots of entries. It would help to also see the info from the Upstream and Downstream tabs of the VM Hub to see if there are any obvious signal level or error issues
on 30-06-2024 16:54
3.0 Downstream channels
1 | 459000000 | 3.4 | 38 | QAM 256 | 41 |
2 | 267000000 | 3.3 | 39 | QAM 256 | 17 |
3 | 275000000 | 3.3 | 39 | QAM 256 | 18 |
4 | 283000000 | 3.3 | 39 | QAM 256 | 19 |
5 | 291000000 | 3.3 | 39 | QAM 256 | 20 |
6 | 299000000 | 3.1 | 38 | QAM 256 | 21 |
7 | 307000000 | 2.1 | 38 | QAM 256 | 22 |
8 | 315000000 | 2.2 | 38 | QAM 256 | 23 |
9 | 323000000 | 3.2 | 38 | QAM 256 | 24 |
10 | 331000000 | 3.2 | 39 | QAM 256 | 25 |
11 | 339000000 | 3 | 37 | QAM 256 | 26 |
12 | 347000000 | 3.4 | 39 | QAM 256 | 27 |
13 | 355000000 | 3.5 | 39 | QAM 256 | 28 |
14 | 363000000 | 3.5 | 39 | QAM 256 | 29 |
15 | 371000000 | 3.6 | 39 | QAM 256 | 30 |
16 | 379000000 | 3.4 | 37 | QAM 256 | 31 |
17 | 387000000 | 3.3 | 39 | QAM 256 | 32 |
18 | 395000000 | 3.3 | 37 | QAM 256 | 33 |
19 | 403000000 | 3.4 | 39 | QAM 256 | 34 |
20 | 411000000 | 3.7 | 38 | QAM 256 | 35 |
21 | 419000000 | 3.9 | 39 | QAM 256 | 36 |
22 | 427000000 | 3.9 | 39 | QAM 256 | 37 |
23 | 435000000 | 3.8 | 39 | QAM 256 | 38 |
24 | 443000000 | 3.5 | 39 | QAM 256 | 39 |
25 | 451000000 | 3.4 | 40 | QAM 256 | 40 |
26 | 467000000 | 3.3 | 39 | QAM 256 | 42 |
27 | 475000000 | 3.2 | 37 | QAM 256 | 43 |
28 | 483000000 | 3.1 | 38 | QAM 256 | 44 |
29 | 491000000 | 3.1 | 39 | QAM 256 | 45 |
30 | 499000000 | 2.9 | 38 | QAM 256 | 46 |
31 | 507000000 | 2.7 | 39 | QAM 256 | 47 |
32 | 515000000 | 2.6 | 38 | QAM 256 | 48 |
3.0 Downstream channels
1 | Locked | 38 | 5017 | 30664 |
2 | Locked | 39 | 6962 | 48603 |
3 | Locked | 39 | 6281 | 41243 |
4 | Locked | 39 | 6940 | 47508 |
5 | Locked | 39 | 7060 | 46773 |
6 | Locked | 38 | 7066 | 45783 |
7 | Locked | 38 | 6929 | 43381 |
8 | Locked | 38 | 6678 | 45222 |
9 | Locked | 38 | 5223 | 33549 |
10 | Locked | 39 | 7039 | 46512 |
11 | Locked | 37 | 6561 | 42949 |
12 | Locked | 39 | 5235 | 32520 |
13 | Locked | 39 | 5919 | 37771 |
14 | Locked | 39 | 5810 | 37725 |
15 | Locked | 39 | 5832 | 36263 |
16 | Locked | 37 | 5039 | 32478 |
17 | Locked | 39 | 5875 | 38398 |
18 | Locked | 37 | 6105 | 39948 |
19 | Locked | 39 | 5495 | 33561 |
20 | Locked | 38 | 4484 | 28655 |
21 | Locked | 39 | 5906 | 35301 |
22 | Locked | 39 | 6564 | 39844 |
23 | Locked | 39 | 4747 | 30149 |
24 | Locked | 39 | 4786 | 28627 |
25 | Locked | 40 | 5357 | 31889 |
26 | Locked | 39 | 4302 | 26391 |
27 | Locked | 37 | 4483 | 28552 |
28 | Locked | 38 | 4780 | 27958 |
29 | Locked | 39 | 4582 | 26284 |
30 | Locked | 38 | 5154 | 33300 |
31 | Locked | 39 | 4296 | 25831 |
32 | Locked | 38 | 4652 | 27362 |
3.1 Downstream channels
159 | 94 | 4K | 1840 | QAM 4096 | 1108 |
3.1 Downstream channels
159 | Locked | 41 | 5.1 | 729940367 | 120382 |
on 30-06-2024 16:54
3.0 Upstream channels
0 | 60300000 | 32.3 | 5120 | QAM 64 | 1 |
1 | 53700000 | 33.3 | 5120 | QAM 64 | 2 |
2 | 46200000 | 33.3 | 5120 | QAM 64 | 3 |
3 | 39400000 | 33.3 | 5120 | QAM 64 | 4 |
4 | 32600000 | 33.8 | 5120 | QAM 64 | 5 |
5 | 23600000 | 33.8 | 5120 | QAM 64 | 6 |
3.0 Upstream channels
0 | ATDMA | 0 | 3 | 14 | 0 |
1 | ATDMA | 0 | 3 | 0 | 0 |
2 | ATDMA | 0 | 3 | 15 | 0 |
3 | ATDMA | 0 | 3 | 16 | 0 |
4 | ATDMA | 0 | 3 | 17 | 0 |
5 | ATDMA | 0 | 3 | 3 | 0 |
on 30-06-2024 19:15
These signal issues if persisting are of concern...
3.0 Downstream channels
1 | Locked | 38 | 5017 | 30664 |
2 | Locked | 39 | 6962 | 48603 |
3 | Locked | 39 | 6281 | 41243 |
4 | Locked | 39 | 6940 | 47508 |
5 | Locked | 39 | 7060 | 46773 |
6 | Locked | 38 | 7066 | 45783 |
7 | Locked | 38 | 6929 | 43381 |
8 | Locked | 38 | 6678 | 45222 |
9 | Locked | 38 | 5223 | 33549 |
10 | Locked | 39 | 7039 | 46512 |
Errors are seen across all 32 channels.
3.1 Downstream channels
159 | Locked | 41 | 5.1 | 729940367 | 120382 |
3.0 Upstream channels
0 | ATDMA | 0 | 3 | 14 | 0 |
1 | ATDMA | 0 | 3 | 0 | 0 |
2 | ATDMA | 0 | 3 | 15 | 0 |
3 | ATDMA | 0 | 3 | 16 | 0 |
4 | ATDMA | 0 | 3 | 17 | 0 |
5 | ATDMA | 0 | 3 | 3 | 0 |
on 30-06-2024 20:24
What would you recommend I do next?
on 03-07-2024 11:54
Hello Mc_Jordan2000.
Thanks for your first post and welcome to our community.
First of all we're sorry to hear you're still having the same issue after 2 engineers visits.
We're able to run basic checks on your signal from here and can see the upstream levels are not right at all.
It was also possible to see another appointment has been raised for an engineers visit. As this falls within 30 days of the last visit we automatically assign the work out to a senior engineer, who will have a thorough look at everything.
When you got installed was this a self install? If so, it come come down to what we call a repull being needed, The cable from the green cabinet to your property might need replacing.
Can you please let us know how the visit goes.
Gareth_L