26-10-2021 00:33 - edited 26-10-2021 00:45
These graphs sure look like over utilisation to me!! I'd love for a Virgin media representative to tell me otherwise! - not like I was given a fix date over a year ago.
on 26-10-2021 00:40
Can you remove your IP address in the photos and then post them again please?
Also if possible set up a live link to your BQM, doing that will automatically obscure your IP address.
on 26-10-2021 00:46
on 26-10-2021 00:52
That's perfect.Thanks for doing that.
The tech guru's should pick up your post at some point on Tuesday, however it may also be useful to post your router logs for them too.
In your browser’s URL box type in http://192.168.0.1 (or http://192.168.100.1 - if in modem mode) and hit return.
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 (please don't post the pictures as they are difficult to read, plus the pictures would contain your MAC address which would be rejected) – from the Downstream, Upstream, & Network Logs pages.
If you see an error message don't worry, just press post again and it will be accepted. You will probably need two posts to fit all the info in.
on 26-10-2021 01:04
UPSTREAM
Channel Type | 2.0 | 2.0 | 2.0 | 2.0 |
Channel ID | 2 | 4 | 3 | 1 |
Frequency (Hz) | 53700000 | 39400000 | 46200000 | 60300000 |
Ranging Status | Success | Success | Success | Success |
Modulation | 64QAM | 64QAM | 64QAM | 64QAM |
Symbol Rate (Sym/sec) | 5120000 | 5120000 | 5120000 | 5120000 |
Mini-Slot Size | 2 | 2 | 2 | 2 |
Power Level (dBmV) | 46.75 | 45.25 | 46.75 | 46.75 |
T1 Timeouts | 0 | 0 | 0 | 0 |
T2 Timeouts | 0 | 0 | 0 | 0 |
T3 Timeouts | 0 | 0 | 0 | 0 |
T4 Timeouts | 0 | 0 | 0 | 0 |
DOWNSTREAM
Downstream DS-1 DS-2 DS-3 DS-4 DS-5 DS-6 DS-7 DS-8
Frequency (Hz) | 138750000 | 146750000 | 154750000 | 162750000 | 170750000 | 178750000 | 186750000 | 194750000 |
Lock Status(QAM Lock/FEC Sync/MPEG Lock) | Locked | Locked | Locked | Locked | Locked | Locked | Locked | Locked |
Channel ID | 1 | 2 | 3 | 4 | 5 | 6 | 7 | 8 |
Modulation | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM | 256QAM |
Symbol Rate (Msym/sec) | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 | 6.952000 |
Interleave Depth | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 | I=12 J=17 |
Power Level (dBmV) | -0.40 | -0.98 | -1.12 | -1.05 | -1.28 | -1.56 | -1.69 | -1.62 |
RxMER (dB) | 35.08 | 34.93 | 34.77 | 35.08 | 35.42 | 35.42 | 35.60 | 35.78 |
Pre RS Errors | 2994 | 4221 | 3358 | 2341 | 732 | 1144 | 491 | 466 |
Post RS Errors | 299 | 274 | 313 | 271 | 284 | 917 | 290 | 290 |
First Time | Last Time | Priority | Error Number | Description |
25/10/2021 13:07:13 GMT | 25/10/2021 13:07:13 GMT | Error (4) | 68000407 | TOD established |
Time Not Established | Time Not Established | Notice (6) | 84000510 | Downstream Locked Successfully |
25/10/2021 07:00:57 GMT | 25/10/2021 07:00:57 GMT | Notice (6) | 68010600 | DHCP Renew - lease parameters tftp file-******** modified |
25/10/2021 07:00:57 GMT | 25/10/2021 07:00:57 GMT | Error (4) | 68010300 | DHCP RENEW WARNING - Field invalid in response v4 option |
22/10/2021 14:46:06 GMT | 22/10/2021 14:46:06 GMT | Notice (6) | 68010600 | DHCP Renew - lease parameters tftp file-******** modified |
22/10/2021 14:46:06 GMT | 22/10/2021 14:46:06 GMT | Error (4) | 68010300 | DHCP RENEW WARNING - Field invalid in response v4 option |
20/10/2021 19:16:22 GMT | 20/10/2021 19:16:22 GMT | Error (4) | 68000407 | TOD established |
Time Not Established | Time Not Established | Notice (6) | 84000510 | Downstream Locked Successfully |
17/10/2021 10:15:32 GMT | 17/10/2021 10:15:32 GMT | Notice (6) | 68010600 | DHCP Renew - lease parameters tftp file-******** modified |
17/10/2021 10:15:32 GMT | 17/10/2021 10:15:32 GMT | Error (4) | 68010300 | DHCP RENEW WARNING - Field invalid in response v4 option |
14/10/2021 00:19:01 GMT | 14/10/2021 00:19:01 GMT | Notice (6) | 68010600 | DHCP Renew - lease parameters tftp file-******** modified |
14/10/2021 00:19:01 GMT | 14/10/2021 00:19:01 GMT | Error (4) | 68010300 | DHCP RENEW WARNING - Field invalid in response v4 option |
12/10/2021 18:33:53 GMT | 12/10/2021 18:33:53 GMT | Critical (3) | 82000200 | No Ranging Response received - T3 time-out |
12/10/2021 18:33:52 GMT | 12/10/2021 18:33:52 GMT | Critical (3) | 82000700 | Unicast Ranging Received Abort Response - initializing MAC |
12/10/2021 18:32:33 GMT | 12/10/2021 18:32:33 GMT | Critical (3) | 82000200 | No Ranging Response received - T3 time-out |
12/10/2021 18:32:33 GMT | 12/10/2021 18:32:33 GMT | Critical (3) | 82000700 | Unicast Ranging Received Abort Response - initializing MAC |
12/10/2021 18:32:13 GMT | 12/10/2021 18:32:13 GMT | Critical (3) | 82000200 | No Ranging Response received - T3 time-out |
12/10/2021 18:32:13 GMT | 12/10/2021 18:32:13 GMT | Critical (3) | 82000700 | Unicast Ranging Received Abort Response - initializing MAC |
12/10/2021 18:31:13 GMT | 12/10/2021 18:31:13 GMT | Critical (3) | 82000200 | No Ranging Response received - T3 time-out |
12/10/2021 18:31:13 GMT | 12/10/2021 18:31:13 GMT | Critical (3) | 82000700 | Unicast Ranging Received Abort Response - initializing MAC |
on 26-10-2021 06:21
Could be a problem that occurs when the network is busy, rather than a simple case of over-utilisation. Whilst the overnight lull is persuasive for O-U, the daytime traces are less so, because there's no build up across the day, and although the afternoon's not ideal, it's not that bad.
What I do observe is that you are running a Superhub 2 (a decrepit antique using out of date technology), and your SNR is borderline on a couple of channels. Potentially your problems might be fixed by a replacement of the hub, and the line setup tweaking to improve SNR. The best you can hope for here is that the forum staff agree there's a problem and assign a technician, and that the technician replaces the hub and tweaks the line; Sometimes that's straightforward, sometimes you'll get claims that VM can see nothing wrong, and have to be very persistent. Or to be more Machiavellian in how you ensure that the matter is addressed.
If you get the hub replaced and SNR improved, and the BQM still looks like that (check the IP address the BQM monitors is still the one for your connection, they can change), then at that point I'd agree that O-U may be a culprit. The bad news then is that at the level of O-U that would be indicated then you might find that the problem is not, in VM's opinion, sufficient to pass the threshold used to decide that there is a problem. Worry about that when the existing issues have been resolved.
on 26-10-2021 11:22
Thanks for the insight. I currently have the SH2 running in modem mode with a much better third party router. When these problems were raised last year I did try running the SH2 as the router but the problems still persisted. Could the SH2 be negatively affecting the third party router when used as a modem?
on 26-10-2021 12:27
@CleverTortoise wrote:< snip> Could the SH2 be negatively affecting the third party router when used as a modem?
No.
However, the SuperHub 2 can only bond 8 channels and if there is any hint of over utilisation, it will struggle. The newer Hub's 3 and 4 can bond more channels and hence a better chance of getting a reasonable broadband circuit.
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 26-10-2021 12:34
Running in modem mode won't affect the BQM, or the SNR issue that I think I see. The hub stats refer entirely to the cable modem connection back to VM's network. The BQM does involve the ThinkBroadband test servers pinging the active modem - so the hub's router when in router mode, or your router when the hub is in modem mode. But that should not make any difference - your own router is probably faster to respond than the hub's pound shop router, offset by the extra electrical distance of the ethernet cable, but either way we're talking nanoseconds.
So the BQM does "include" your router, not to mention TTB servers, and internet traffic routing, but the 20-200ms trace you see on the BQM is influenced primarily by the performance of the analogue RF circuit from the hub's cable modem back to the broom cupboard that is at the head of the coax network.
Thinking the other way round, can modem mode affect router performance? No, in the way I understand your question. Your router, or my mesh wifi both deal with the decoded internet traffic from the hub's cable modem, but there's no way that the hub can cause the third party router performance to deteriorate. If the cable modem passes a good connection to the router, you get a good connection. If the connection is ropey (as seems) then that will be a ropey connection faithfully passed on by your router, but the bit under your control and the wireless will be as good as it can be in the circumstances.
on 28-10-2021 14:06
Thanks for posting. My apologies for the broadband issues.
I've not been able to locate the account from the forum information. Can you send me a PM with the address, name and postcode so I can run some tests?
Best,
Need a helpful hand to show you how to make a payment? Check out our guide - How to pay my Virgin Media bill