on 13-02-2022 23:05
My speeds are up and down I very rarely get 350mbps as per previous posts I am on a mesh system..this problem has been consistent on 3 different set up. as unable to a wired connection I was asked to set up a BQM...tonight I had problems between 10pm and 11pm..i hope I have attached this BQM properly what does it show, if not there ease tell me how..thanks
[url=https://www.thinkbroadband.com/broadband/monitoring/quality/share/f863ef2073eb4705bf1b64524b0c6b0be68c72f6-13-02-2022][img]https://www.thinkbroadband.com/broadband/monitoring/quality/share/thumb/f863ef2073eb4705bf1b64524b0c6b0be68c72f6-13-02-2022.png[/img][/url]
Answered! Go to Answer
on 28-02-2022 18:08
Hi again after multiple drop outs this after noon I checked my BQM , note, I do not understand them or what they mean, I cannot post results...we have been getting signal loss this afternoon and but by the time we do a speed test everything seems ok...when I checked my BQM.this what I found, as I can't post I have posted 3 screen prints from when the graph changed...I have not changed any setting etc this just happened could someone explain if this could be a source off my problems...thanks
on 28-02-2022 18:47
Everyone is very quick to suggest ethernet cable faults, device faults, utilisation faults yet i never see them suggest the actual coax to the property or from the wall to modem is faulty.
I do see "box outside falling off the wall" fairly often, one thing i always remember is that little spanner they supply with self installs, its there for a reason.
Check the connections from the outside wall to the modem as a just in case.
on 28-02-2022 19:17
Hi @ukmartian
I'm afraid your BQM screen shots have been rejected as they contain your IP address.
The latest ones are all showing red which means that the BQM isn't working. This sometimes happens on the rare occassion that the VM IP address has been changed, however you'rs is still the same.
Reboot your hub and the BQM should start working again. Then either post the live BQM graph (it strips out the IP address)* or wait a few hours and take a screenshot ensuring you edit out the IP address
*
On Think Broadband go to your BQM and under the options you will see
Today | Previous Days | Edit | Delete | Share
Click on the Share option and on the screen that opens click on Share
On the next screen click on Share Live Graph
Copy the text in the Direct Link box (beware there may be more text than you can see)
On here click the Link icon (2 links chain to the left of the camera icon)
In the URL box paste the link you copied and then click OK
on 28-02-2022 20:18
on 28-02-2022 20:57
Hi @ukmartian thanks for your post.
I just want to highlight that a colleague has responded to your recent PM to us, and we are awaiting a response - hopefully our advice can help you on this matter.
Unfortunately though, it's hard to give you an exact answer on if your devices connected will be affected or not, due to this being about a third party networking piece of equipment which we don't support through Virgin Media I'm afraid.
Please kindly respond to our PM and we'll be able to support you further through there.
Many thanks
on 28-02-2022 22:05
Sorry about delay it's just that my BB IS NOT WORKING at this moment in time, the BMQ that I set up has turned solid red hundreds of people use the same set up as me they don't get this trouble I will check the modem when I get the opportunity, but I would feel happier trying another one as that has not been changed as yet ...something must be causing these problems ,I have done everything by upgrading my equipment 3 times, this has been going on for months.
on 28-02-2022 23:05
Hi again @ukmartian I've merged your two threads together to make it easier for the Forum team to follow.
Your Live BQM is working, it's no longer all red, but it doesn't look pretty at present.
If it is utilisation then as @SCA1972 suggested the BQM should clear up after midnight.
It is possible that it's also an issue with the VM hub, your mesh system, or the VM cabling, either internal or external to your property.
on 28-02-2022 23:09
I also noticed you haven't yet posted the network logs from the VM hub which will help towards a solution.
In your browser’s URL box type in http://192.168.100.1 if still in modem mode and hit return. It's http://192.168.0.1 when you can test it without your mesh system.
Don't login, instead below there click on Check Router Status
From the Router Status page copy/paste 3 FULL sets of data onto here (Not screen shots but text) – from the Downstream, Upstream, & Network Logs pages.
on 01-03-2022 16:38
Regards
1 | 363000000 | 1.5 | 40 | 256 qam | 29 |
2 | 251000000 | -0.2 | 38 | 256 qam | 15 |
3 | 259000000 | -0.2 | 38 | 256 qam | 16 |
4 | 267000000 | 0.2 | 38 | 256 qam | 17 |
5 | 275000000 | 0.7 | 38 | 256 qam | 18 |
6 | 283000000 | 0.5 | 38 | 256 qam | 19 |
7 | 291000000 | 0.5 | 38 | 256 qam | 20 |
8 | 299000000 | 0.5 | 38 | 256 qam | 21 |
9 | 307000000 | 0.7 | 40 | 256 qam | 22 |
10 | 315000000 | 1.2 | 40 | 256 qam | 23 |
11 | 323000000 | 1.7 | 40 | 256 qam | 24 |
12 | 331000000 | 1.5 | 38 | 256 qam | 25 |
13 | 339000000 | 1.7 | 40 | 256 qam | 26 |
14 | 347000000 | 1.7 | 40 | 256 qam | 27 |
15 | 355000000 | 1.5 | 40 | 256 qam | 28 |
16 | 371000000 | 1.4 | 40 | 256 qam | 30 |
17 | 379000000 | 1 | 38 | 256 qam | 31 |
18 | 387000000 | 0.5 | 40 | 256 qam | 32 |
19 | 395000000 | 0.5 | 38 | 256 qam | 33 |
20 | 403000000 | 0.5 | 38 | 256 qam | 34 |
21 | 411000000 | 0.7 | 38 | 256 qam | 35 |
22 | 419000000 | 0.7 | 38 | 256 qam | 36 |
23 | 523000000 | 2.2 | 38 | 256 qam | 37 |
24 | 531000000 | 2.4 | 40 | 256 qam | 38 |
on 01-03-2022 16:41
1 | Locked | 40.3 | 1231 | 0 |
2 | Locked | 38.9 | 229 | 0 |
3 | Locked | 38.9 | 337 | 0 |
4 | Locked | 38.9 | 342 | 0 |
5 | Locked | 38.9 | 260 | 0 |
6 | Locked | 38.9 | 297 | 0 |
7 | Locked | 38.9 | 302 | 0 |
8 | Locked | 38.9 | 415 | 0 |
9 | Locked | 40.3 | 313 | 0 |
10 | Locked | 40.3 | 375 | 0 |
11 | Locked | 40.3 | 548 | 0 |
12 | Locked | 38.9 | 707 | 0 |
13 | Locked | 40.3 | 876 | 0 |
14 | Locked | 40.3 | 1085 | 0 |
15 | Locked | 40.3 | 965 | 0 |
16 | Locked | 40.3 | 1337 | 0 |
17 | Locked | 38.9 | 1472 | 0 |
18 | Locked | 40.9 | 1721 | 0 |
19 | Locked | 38.9 | 1882 | 0 |
20 | Locked | 38.9 | 1849 | 0 |
21 | Locked | 38.9 | 2282 | 0 |
22 | Locked | 38.9 | 2436 | 0 |
23 | Locked | 38.9 | 3202 | 0 |
24 | Locked | 40.3 | 2089 | 0 |
1 | 25799998 | 44 | 5120 | 64 qam | 4 |
2 | 32600002 | 44 | 5120 | 64 qam | 3 |
3 | 39400007 | 44 | 5120 | 64 qam | 2 |
4 | 46199996 | 44 | 5120 | 64 qam | 1 |
1 | ATDMA | 0 | 0 | 1 | 0 |
2 | ATDMA | 0 | 0 | 0 | 0 |
3 | ATDMA | 0 | 0 | 0 | 0 |
4 | ATDMA | 0 | 0 | 0 | 0 |
28/02/2022 22:10:24 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/02/2022 08:44:30 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
28/02/2022 08:44:30 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
25/02/2022 07:52:39 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2022 20:44:30 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2022 20:44:30 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2022 20:14:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
24/02/2022 20:14:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
23/02/2022 01:51:49 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/02/2022 08:14:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
21/02/2022 08:14:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
20/02/2022 13:54:54 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/02/2022 20:14:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
17/02/2022 20:14:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/02/2022 08:48:50 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/02/2022 08:14:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
14/02/2022 08:14:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
12/02/2022 08:17:29 | critical | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/02/2022 20:14:29 | notice | DHCP Renew - lease parameters tftp file-cmreg-vmdg505-bbt062-b.cm modified;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |
10/02/2022 20:14:29 | Error | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0; |