on 30-01-2022 11:02
Hi,
Im seeing some latency and packet loss on my 500mb connection. As you can see from the graph it’s not horrendous but does cause issues on ms teams calls when I’m working from home. I had been setup in modem mode with a commercial router and ap’s so decided to go back into router mode to see if that was any better. So config is now router mode WiFi off and laptop connected directly on gig Ethernet. I would say looking at my graph and doing some tests it’s actually worse. Know people on here have had far worse graphs! Even so it does seem to be causing me issues on work meetings. Any ideas?
https://www.thinkbroadband.com/broadband/monitoring/quality/share/f5074f0691772c4ec3fb3d46b642fbac038a6fa5-30-01-2022
on 30-01-2022 11:06
Post your power levels and network log as well please. Your BQM is not bad really, I've seen a lot worse!
I'm surprised your own router and AP's are not outperforming the Hub? Maybe you should revisit your setup?
But as you have a wired connection, that's a moot point regardless. We'll wait to see the Hub stats first.
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 30-01-2022 11:21
Thanks Adduxi,
My AP's certainly are out performing the VM hub. Had seen something on here that there may be issues with Modem mode firmware so switched back to router mode to see if there was any difference... from a latency pov there is not. I am going to switch back to my own router soon. Just wanted to make sure that there were no issues with my own equipment.
Before going back to router mode yesterday I did a pinhole rest also. The BQM I have posted is an example...but it has been slightly worse...cant post those due to me screwing up my bqm account!
Cable Modem Status Item Status Comments
Acquired Downstream Channel (Hz) | 331000000 | Locked |
Ranged Upstream Channel (Hz) | 60299969 | Locked |
Provisioning State | Online |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 | 331000000 | 2.2 | 38 | 256 qam | 25 |
2 | 203000000 | 0.7 | 38 | 256 qam | 9 |
3 | 211000000 | 0.7 | 38 | 256 qam | 10 |
4 | 219000000 | -0.9 | 38 | 256 qam | 11 |
5 | 227000000 | 0 | 38 | 256 qam | 12 |
6 | 235000000 | -0.2 | 38 | 256 qam | 13 |
7 | 243000000 | -1.2 | 38 | 256 qam | 14 |
8 | 251000000 | -1.2 | 38 | 256 qam | 15 |
9 | 259000000 | -0.7 | 37 | 256 qam | 16 |
10 | 267000000 | 1 | 38 | 256 qam | 17 |
11 | 275000000 | 0.2 | 38 | 256 qam | 18 |
12 | 283000000 | -0.2 | 37 | 256 qam | 19 |
13 | 291000000 | 1.2 | 38 | 256 qam | 20 |
14 | 299000000 | 0.9 | 38 | 256 qam | 21 |
15 | 307000000 | 0.4 | 38 | 256 qam | 22 |
16 | 315000000 | 1.5 | 38 | 256 qam | 23 |
17 | 323000000 | 1.5 | 38 | 256 qam | 24 |
18 | 339000000 | 1.5 | 38 | 256 qam | 26 |
19 | 347000000 | 1.7 | 38 | 256 qam | 27 |
20 | 355000000 | 2.5 | 38 | 256 qam | 28 |
21 | 363000000 | 0.7 | 38 | 256 qam | 29 |
22 | 371000000 | 0.7 | 38 | 256 qam | 30 |
23 | 379000000 | 1.2 | 38 | 256 qam | 31 |
24 | 387000000 | 0.4 | 38 | 256 qam | 32 |
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 | Locked | 38.9 | 37 | 0 |
2 | Locked | 38.6 | 2121 | 93 |
3 | Locked | 38.6 | 2976 | 20 |
4 | Locked | 38.6 | 64601 | 158 |
5 | Locked | 38.6 | 37750 | 65 |
6 | Locked | 38.6 | 6539 | 166 |
7 | Locked | 38.6 | 9949 | 289 |
8 | Locked | 38.6 | 1211 | 96 |
9 | Locked | 37.6 | 255 | 147 |
10 | Locked | 38.6 | 830 | 14 |
11 | Locked | 38.6 | 105 | 0 |
12 | Locked | 37.6 | 74 | 12 |
13 | Locked | 38.6 | 98 | 24 |
14 | Locked | 38.6 | 865 | 0 |
15 | Locked | 38.6 | 312 | 6 |
16 | Locked | 38.9 | 124 | 83 |
17 | Locked | 38.6 | 111 | 50 |
18 | Locked | 38.9 | 43 | 90 |
19 | Locked | 38.6 | 53 | 6 |
20 | Locked | 38.9 | 33 | 0 |
21 | Locked | 38.6 | 51 | 0 |
22 | Locked | 38.6 | 60 | 0 |
23 | Locked | 38.9 | 41 | 86 |
24 | Locked | 38.6 | 29 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 60299969 | 48.3 | 5120 | 64 qam | 1 |
2 | 39400007 | 48 | 5120 | 64 qam | 4 |
3 | 46199969 | 48.5 | 5120 | 64 qam | 3 |
4 | 53700009 | 48.8 | 5120 | 64 qam | 2 |
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 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
Network access | Allowed |
Maximum Number of CPEs | 1 |
Baseline Privacy | Enabled |
DOCSIS Mode | Docsis30 |
Config file | ca69834ncxv9873254k;fg87d |
on 30-01-2022 11:21
SFID | 321 |
Max Traffic Rate | 575000000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 1531 |
Max Traffic Rate | 38520000 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 16320 |
Scheduling Type | BestEffort |
Time Priority Description
30/01/2022 11:11:52 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
30/01/2022 04:08:26 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/01/2022 14:59:17 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
01/01/1970 00:01:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/01/2022 14:47:48 | Warning! | LAN login FAILED : Incorrect Username / Password / ConnectionType;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/01/2022 14:39:43 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/01/2022 14:36:45 | notice | Unit has been restored to factory defaults from a software issued command;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
29/01/2022 14:27:41 | notice | LAN login Success;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/01/2022 17:36:7 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/01/2022 10:53:38 | 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; |
28/01/2022 10:53:38 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/01/2022 12:24:32 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
26/01/2022 01:49:52 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/01/2022 22:53:37 | 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; |
24/01/2022 22:53:37 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/01/2022 13:43:10 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/01/2022 13:24:22 | 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; |
21/01/2022 13:24:22 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/01/2022 12:17:44 | Warning! | RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/01/2022 18:35:20 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
on 30-01-2022 11:25
Stats look okay, apart from the PostRS errors and they may be historical? If you reboot the Hub and keep an eye on these errors, they should be zero. Any errors are usually indicative of noise on the circuit and will need a VM technician to locate the source and fix it.
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 30-01-2022 11:27
Hub uptime after a full factory reset is only 20hrs so those errors are recent...and old log (before reset) was full of them
on 30-01-2022 11:29
So if it does need a tech....what's the best route to get them to check?
on 30-01-2022 11:43
Either phone in or wait here a day or two for a VM Mod to pick this up.
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 31-01-2022 13:04
Hmm, think I’ll be waiting for a mod then, got through to a human once who told me to do a reboot and then lost the call. Have tried to call back and just get the automatic notification that nothing is wrong and I need to reboot my hub… guess what… makes no difference… and sorry not a rant at you Adduxi… know you are just a helpful community member, and you’ve been more than helpful 😀
03-02-2022 10:40 - edited 03-02-2022 10:42
Still nothing from mods guess they are busy!
live bqm… packet loss not so bad but latency… guessing this may be more around over utilisation in my area?
https://www.thinkbroadband.com/broadband/monitoring/quality/share/32a6576b1e8780bd66b65e06f8b3c95c93...