Can you please remove your MAC info from these logs as it can be easily cloned and used to get free access via a chipped modem etc?

Your BQM doesn’t look bad to me. There’s no packet loss. The green bar at the bottom is not hugely high. The spikes are aligned with usage of the connection.

Here is a genuinely poor BQM

Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 40.9 11579 3714
2 Locked 40.3 13511 9379
3 Locked 40.3 13127 7836
4 Locked 40.3 12583 6715
5 Locked 40.3 11138 5968
6 Locked 40.3 10340 5707
7 Locked 40.3 11157 5902
8 Locked 40.3 12028 6450
9 Locked 40.3 11667 5972
10 Locked 40.3 11710 6645
11 Locked 40.3 10876 6199
12 Locked 40.3 11849 6584
13 Locked 40.9 10780 5758
14 Locked 40.3 10276 5103
15 Locked 40.9 6209 4136
16 Locked 40.9 10003 3789
17 Locked 40.3 10784 3725
18 Locked 38.9 10603 2830
19 Locked 40.9 11699 2983
20 Locked 40.3 12353 2595
21 Locked 38.9 12555 2623
22 Locked 40.3 12259 2412
23 Locked 40.3 12035 2313
24 Locked 40.3 10677 2126

Can you confirm there are errors showing in the POST RS Errors?

Post RS (Reed-Solomon) errors are errors that are uncorrectable. A non-zero value (or close to zero) usually means there’s a line fault.

RCS Partial Service - means on one or more channels the signal has been lost between the hub and Virginmedia. That is bad. It will generally still work at depreciated performance and may drop temporarily. Typically where logs show this the provider will issue an engineer.

Do you still see this error on the hub 5?

Thanks for your response - I really appreciate iit.

I haven’t checked with the Hub5 (yet - I’ll have a look later on)- but I lknow that there were quite a few PostRS errors on the H3. Certainly have been noticing some dropouts/other connection issues.

Not going to post the full stats and I can't edit the post to remove the MAC address but:

Most of the channels have normal power and SNB levels. However, the DOCSIS 3.1 downstream channel has a modulation of 4096 QAM and shows a ridiculous amount of corrected errors (over 10 million). (sorry i'm not very technical). There's some T3 Timeouts also.
There's still lots of PostRS errors - does this indicate an issue with the cable or could it be a area issue? I'm a little confused.

There's also some weird errors etc in the network logs (posting them, while removing the MAC Addresses) - I know the GUI ones are normal.

I've lost trust in Virgin - I've had 4 engineer visits that have fixed nothing. Is there any way to get this dealt with by a senior/more experienced engineer?

Time Priority Description
17-04-2024 08:10:48 notice GUI Login Status - Login Success from LAN interface
17-04-2024 07:58:51 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 07:58:51 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 07:48:49 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 07:48:49 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 07:35:38 notice GUI Login Status - Login Success from LAN interface
17-04-2024 07:27:04 notice GUI Login Status - Login Success from LAN interface
17-04-2024 07:26:55 notice GUI Login Status - Login Success from LAN interface
17-04-2024 07:26:01 notice GUI Login Status - Login Success from LAN interface
17-04-2024 06:59:13 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 06:28:13 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 06:28:13 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 06:18:07 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 06:18:07 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 04:17:00 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 04:17:00 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 03:56:57 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 03:56:57 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 02:54:58 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;;CM-VER=3.1;
17-04-2024 02:36:16 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 02:36:16 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 02:26:06 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 02:26:06 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:46:05 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:45:51 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:45:51 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:42:05 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:35:43 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:35:43 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:25:40 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:25:40 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:15:48 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:15:30 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;;CM-QOS=1.1;CM-VER=3.1;
17-04-2024 01:15:30 notice US profile assignment change. US Chan ID: 6; Previous Profile: 11 13; New Profile: 12 13.:cf;CM-QOS=1.1;CM-VER=3.1;
16-04-2024 20:56:34 warning RNG-RSP CCAP Commanded Power in Excess of 6 dB Below the Value Corresponding to the Top of the DRW;CM-QOS=1.1;CM-VER=3.1;
16-04-2024 20:53:27 warning DBC-REQ Mismatch Between Calculated Value for P1.6hi Compared to CCAP Provided Value;CM-QOS=1.1;CM-VER=3.1;
16-04-2024 20:53:27 notice US profile assignment change. US Chan ID: 6; Previous Profile: 12 13; New Profile: 11 13.;CM-QOS=1.1;CM-VER=3.1;

Edited by RT123 (Wed 17-Apr-24 09:06:24)

Corrected errors wont do any harm, as long as uncorrected is low, thats fine.