cancel
Showing results for 
Search instead for 
Did you mean: 

BQM

ukmartian
Up to speed

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]
34 REPLIES 34

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 

Screenshot_20220228-170020_Firefox.jpg

Screenshot_20220228-170135_Firefox.jpg

Screenshot_20220228-170154_Firefox.jpg

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.

newapollo
Very Insightful Person
Very Insightful Person

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

 

Dave
I don't work for Virgin Media.
I'm a Very Insightful Person, I'm here to share knowledge.
Problem solved? Click to mark as a Helpful Answer, or use Kudos to say thanks
The do's and don'ts.
Keep the community welcoming for all. Please read the FAQ's
The Service you do for others is the rent you pay for your room here on Earth - Muhammad Ali

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

Tom_W

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.

newapollo
Very Insightful Person
Very Insightful Person

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.

Dave
I don't work for Virgin Media.
I'm a Very Insightful Person, I'm here to share knowledge.
Problem solved? Click to mark as a Helpful Answer, or use Kudos to say thanks
The do's and don'ts.
Keep the community welcoming for all. Please read the FAQ's
The Service you do for others is the rent you pay for your room here on Earth - Muhammad Ali

newapollo
Very Insightful Person
Very Insightful Person

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. 

Dave
I don't work for Virgin Media.
I'm a Very Insightful Person, I'm here to share knowledge.
Problem solved? Click to mark as a Helpful Answer, or use Kudos to say thanks
The do's and don'ts.
Keep the community welcoming for all. Please read the FAQ's
The Service you do for others is the rent you pay for your room here on Earth - Muhammad Ali

Hi I have managed to access my modem on 192.168.100.1. This is the first time I have been able to access over my network for a long time as it would not connect and time out . This access also coincides with my BQM restarting as going totally red . yesterday from about mid afternoon i was plagued by drop out anything from a blip to a few minutes to 15 minutes + the worst was late in the evening between 10 -10.30pm ..the highest speed I recorded was at 353mbps at 17.50 and the slowest was 0.50 mbps at 21.59.I restarted ( unplugged left for 30 seconds then plunged back in ) the hub at approx 22.30 and the speeds recovered from 8.21 mbps before restart  to between 70 and 90 mbps. These speed reading were through Speedtest via my 3 party  WI-Fi equipment  TP-link Deco M4 ....I also got comparable readings from my routers built in speed monitor which measures the incoming speed from the hub modem which is wired via a new cat 7 braided shielded Ethernet cable with gold plugs. I hope this info is acceptable as my knowledge of wi-fi etc is limited should you require anymore info please request , should you wish to speak PM me and I will reply with my mobile no . This issue has been ongoing for poss a year or more starting with the hub in router mode , I then bought a seperate router and switched it to modem only, that didnt work , I then bought a cheap mesh which didn't work, so my speeds were upgraded but I had to also upgrade my mesh as the ethernet interface was only rated at 100 mbps plus i upgraded my ethernet cable.I feel that I have done everything i can to eliminate any faults within my own network ( one of you engineers also said it was ok) and i would like this issue resolved .

Regards

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13630000001.540256 qam29
2251000000-0.238256 qam15
3259000000-0.238256 qam16
42670000000.238256 qam17
52750000000.738256 qam18
62830000000.538256 qam19
72910000000.538256 qam20
82990000000.538256 qam21
93070000000.740256 qam22
103150000001.240256 qam23
113230000001.740256 qam24
123310000001.538256 qam25
133390000001.740256 qam26
143470000001.740256 qam27
153550000001.540256 qam28
163710000001.440256 qam30
17379000000138256 qam31
183870000000.540256 qam32
193950000000.538256 qam33
204030000000.538256 qam34
214110000000.738256 qam35
224190000000.738256 qam36
235230000002.238256 qam37
245310000002.440256 qam38

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked40.312310
2Locked38.92290
3Locked38.93370
4Locked38.93420
5Locked38.92600
6Locked38.92970
7Locked38.93020
8Locked38.94150
9Locked40.33130
10Locked40.33750
11Locked40.35480
12Locked38.97070
13Locked40.38760
14Locked40.310850
15Locked40.39650
16Locked40.313370
17Locked38.914720
18Locked40.917210
19Locked38.918820
20Locked38.918490
21Locked38.922820
22Locked38.924360
23Locked38.932020
24Locked40.320890
 
 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
12579999844512064 qam4
23260000244512064 qam3
33940000744512064 qam2
44619999644512064 qam1


Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1ATDMA0010
2ATDMA0000
3ATDMA0000
4ATDMA0000
 

Network Log

Time Priority Description
28/02/2022 22:10:24criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
28/02/2022 08:44:30noticeDHCP 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:30ErrorDHCP 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:39criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
24/02/2022 20:44:30noticeDHCP 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:30ErrorDHCP 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:29noticeDHCP 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:29ErrorDHCP 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:49criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/02/2022 08:14:29noticeDHCP 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:29ErrorDHCP 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:54criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/02/2022 20:14:29noticeDHCP 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:29ErrorDHCP 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:50criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/02/2022 08:14:29noticeDHCP 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:29ErrorDHCP 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:29criticalNo Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/02/2022 20:14:29noticeDHCP 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:29ErrorDHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;