on 12-11-2021 16:42
Acquired Downstream Channel (Hz) | 331000000 | Locked |
Ranged Upstream Channel (Hz) | 53700004 | Locked |
Provisioning State | Online |
on 12-11-2021 16:42
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 2.4 | 38 | 256 qam | 25 |
2 | 203000000 | 3.5 | 38 | 256 qam | 9 |
3 | 211000000 | 3.4 | 38 | 256 qam | 10 |
4 | 219000000 | 3.4 | 38 | 256 qam | 11 |
5 | 227000000 | 3.2 | 38 | 256 qam | 12 |
6 | 235000000 | 3.2 | 38 | 256 qam | 13 |
7 | 243000000 | 3 | 38 | 256 qam | 14 |
8 | 251000000 | 3 | 38 | 256 qam | 15 |
9 | 259000000 | 2.9 | 38 | 256 qam | 16 |
10 | 267000000 | 2.9 | 38 | 256 qam | 17 |
11 | 275000000 | 2.5 | 38 | 256 qam | 18 |
12 | 283000000 | 2.5 | 38 | 256 qam | 19 |
13 | 291000000 | 2.5 | 38 | 256 qam | 20 |
14 | 299000000 | 2.7 | 38 | 256 qam | 21 |
15 | 307000000 | 2.5 | 38 | 256 qam | 22 |
16 | 315000000 | 2.4 | 38 | 256 qam | 23 |
17 | 323000000 | 2.4 | 38 | 256 qam | 24 |
18 | 339000000 | 2.5 | 38 | 256 qam | 26 |
19 | 347000000 | 2.5 | 38 | 256 qam | 27 |
20 | 355000000 | 2.4 | 38 | 256 qam | 28 |
21 | 363000000 | 2.5 | 38 | 256 qam | 29 |
22 | 371000000 | 2.4 | 38 | 256 qam | 30 |
23 | 379000000 | 2.5 | 38 | 256 qam | 31 |
24 | 387000000 | 2.5 | 38 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.6 | 376 | 161 |
2 | Locked | 38.9 | 2345 | 179 |
3 | Locked | 38.6 | 2833 | 175 |
4 | Locked | 38.9 | 123 | 10421 |
5 | Locked | 38.9 | 2176 | 5892 |
6 | Locked | 38.6 | 447 | 201 |
7 | Locked | 38.9 | 1173 | 182 |
8 | Locked | 38.6 | 2037 | 184 |
9 | Locked | 38.9 | 780 | 204 |
10 | Locked | 38.9 | 1181 | 150 |
11 | Locked | 38.9 | 394 | 110 |
12 | Locked | 38.6 | 474 | 104 |
13 | Locked | 38.6 | 761 | 122 |
14 | Locked | 38.9 | 846 | 96 |
15 | Locked | 38.9 | 911 | 98 |
16 | Locked | 38.6 | 2712 | 117 |
17 | Locked | 38.9 | 1262 | 154 |
18 | Locked | 38.6 | 354 | 143 |
19 | Locked | 38.6 | 372 | 103 |
20 | Locked | 38.9 | 399 | 83 |
21 | Locked | 38.9 | 378 | 113 |
22 | Locked | 38.6 | 389 | 64 |
23 | Locked | 38.9 | 345 | 113 |
24 | Locked | 38.6 | 357 | 90 |
on 12-11-2021 16:43
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700004 | 38 | 5120 | 64 qam | 10 |
2 | 39400000 | 38 | 5120 | 64 qam | 12 |
3 | 46199976 | 38 | 5120 | 64 qam | 11 |
4 | 60299991 | 38 | 5120 | 64 qam | 9 |
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 | 1 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
on 12-11-2021 16:44
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | 873254k;fg87dsfd;kfoA,.iy |
SFID | 15392 |
Max Traffic Rate | 575000000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 15391 |
Max Traffic Rate | 38520000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
on 12-11-2021 16:45
Time Priority Description
11/11/2021 00:28:46 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
11/11/2021 00:28:46 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/11/2021 21:16:8 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
05/11/2021 14:54:42 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/11/2021 19:20:10 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/11/2021 14:35:40 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
03/11/2021 14:35:40 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
02/11/2021 05:49:58 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/10/2021 13:01:35 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt053-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
31/10/2021 13:01:35 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS- |
on 12-11-2021 16:45
https://www.thinkbroadband.com/broadband/monitoring/quality/share/4be84993a42db8ea66c54bac4dd5c2f6bbf13538
on 12-11-2021 16:57
BQM is pretty much perfect, however too many PostRS errors. Reboot the Hub to clear the counters and keep an eye on those. If they increase quickly there is a fault and will need VMO2 to fix.
How are you connecting by the way, as a cabled connection is preferred over wifi to reduce latency.
I'm a Very Insightful Person, I'm here to share knowledge, I don't work for Virgin Media. Learn more
Have I helped? Click Mark as Helpful Answer or use Kudos to say thanks
on 12-11-2021 17:28
Thank you for the reply.
Ethernet cable. I’ll reboot and report back later
on 15-11-2021 09:40
Hi @halifax1983,
Welcome back to our community forums and thank you for bringing this lag issue to our attention.
How has service been since the reboot? Is the issue still ongoing?
Thanks,
on 15-11-2021 10:25
The downstream post-RS errors indicate a noise ingress problem across all channels, but particularly around 219 and 227 MHz. I'd hazard a guess that the particular noise is probably due to DAB broadcasts on VHF band III, in particular sub-bands 11B and 12C, although internal signal reflections due to cable damage are a possibility. Others may have better knowledge of the specific sources of noise in VHF Band III rather than my assumption of DAB, but regardless of source, there's a noise issue on those frequencies.
Whether noise ingress or reflections, they both suggest either a damaged coax cable (or an unsuitable self-supplied one, eg to move the hub), a poorly made connector, or an uncapped coax port, any of which could be on the same segment you're connected to. When I say "same segment as you", it means that the source of the noise could be on a neighbour's connection, not necessarily yours, but in that case it's VM's problem to trace and resolve it.
What you can do about this is limited, but includes the following:
1) Check that all VM related coaxial cables are as supplied by the company, have the connectors properly made and tightened. So undo each connector, give it a wipe on a tee shirt, damp rag, kitchen paper, reconnect, and do up any securing nuts finger tight.
2) If you're able and willing, do the same in any brown plastic wall box on the outside of the property. These joints tend to be tighter, and you'd probably need a small spanner or similar to undo and redo them, along with a screwdriver to get into the box. If you're not confident to do this, don't attempt it.
3) If there's any unused VM coax ports (eg from a now unused TV box, or previous hub location) they need any ports to have proper caps fitted. Those are usually F-type male terminator caps that you can get for a few quid in any hardware shop.
4) Check for damage on the coax cable such as crushing, kinking, staples or cable clips that have gone through it.
When you've made those checks, turn the hub off and then on again - that will clear the error counters, so you'll soon see if the post-RS counts start rising (pre-RS can usually be ignored). If after this the problems persist and post-RS counts are rising, then it's VM's problem to resolve, and you can ignore any daft advice about "wifi devices too close to the hub", that has no bearing whatsoever on the problems the hub's status data is indicating.