on 12-02-2022 17:39
Having read scage 's trial and tribulations, whose patience and resilience I admire, it is with some trepidation that I make an almost identical post.
Since upgrading from M600, which gave me a reliable 660mb download, I upgraded to Giganet and a Hub4 and can now manage only 400+mb on a good day.
At the moment, I'm on my 3rd Hub4 and have had three engineers, all doing their best, but without success.
Samknows Real Speed Test shows the Hub receiving 1100/52. Even with a laptop, connected with a cat8 cable as the only device, I can barely obtain a 500mb download speed.
This does seem to be a bit of a regular theme here, so if any learned folks have any thoughts, I'd love to hear them.
Thanks
John
on 12-02-2022 17:49
Router status
Cable Modem Status
Cable Modem Status | Online | DOCSIS 3.1 |
Primary downstream channel | Locked | SC-QAM |
DOCSIS 3.0 channels | 31 | 4 |
DOCSIS 3.1 channels | 1 | 0 |
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 330750000 | 3.3 | 39 | QAM256 | 25 |
6 | 178750000 | 2.3 | 39 | QAM256 | 6 |
7 | 186750000 | 2.5 | 39 | QAM256 | 7 |
8 | 194750000 | 2.6 | 38.6 | QAM256 | 8 |
9 | 202750000 | 2.8 | 39 | QAM256 | 9 |
10 | 210750000 | 2.6 | 39 | QAM256 | 10 |
11 | 218750000 | 2.7 | 40.4 | QAM256 | 11 |
12 | 226750000 | 2.6 | 39 | QAM256 | 12 |
13 | 234750000 | 2.5 | 39 | QAM256 | 13 |
14 | 242750000 | 2.4 | 39 | QAM256 | 14 |
15 | 250750000 | 2.2 | 38.6 | QAM256 | 15 |
16 | 258750000 | 2.1 | 39 | QAM256 | 16 |
17 | 266750000 | 1.8 | 39 | QAM256 | 17 |
18 | 274750000 | 2 | 39 | QAM256 | 18 |
19 | 282750000 | 2.6 | 39 | QAM256 | 19 |
20 | 290750000 | 3 | 39 | QAM256 | 20 |
21 | 298750000 | 3.6 | 38.6 | QAM256 | 21 |
22 | 306750000 | 3.8 | 39 | QAM256 | 22 |
23 | 314750000 | 3.9 | 39 | QAM256 | 23 |
24 | 322750000 | 3.5 | 39 | QAM256 | 24 |
26 | 338750000 | 3.8 | 39 | QAM256 | 26 |
27 | 346750000 | 3.7 | 39 | QAM256 | 27 |
28 | 354750000 | 3.7 | 39 | QAM256 | 28 |
29 | 362750000 | 3.5 | 39 | QAM256 | 29 |
30 | 370750000 | 3.7 | 38.6 | QAM256 | 30 |
31 | 378750000 | 3.5 | 39 | QAM256 | 31 |
32 | 386750000 | 3.5 | 39 | QAM256 | 32 |
33 | 394750000 | 3.2 | 38.6 | QAM256 | 33 |
34 | 402750000 | 3 | 38.6 | QAM256 | 34 |
35 | 410750000 | 3 | 40.4 | QAM256 | 35 |
36 | 418750000 | 2.9 | 39 | QAM256 | 36 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
6 | Locked | 38.983261 | 0 | 0 |
7 | Locked | 38.983261 | 0 | 0 |
8 | Locked | 38.605377 | 0 | 0 |
9 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 40.366287 | 0 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.983261 | 0 | 0 |
14 | Locked | 38.983261 | 0 | 0 |
15 | Locked | 38.605377 | 0 | 0 |
16 | Locked | 38.983261 | 0 | 0 |
17 | Locked | 38.983261 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 38.983261 | 0 | 0 |
21 | Locked | 38.605377 | 0 | 0 |
22 | Locked | 38.983261 | 0 | 0 |
23 | Locked | 38.983261 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
26 | Locked | 38.983261 | 0 | 0 |
27 | Locked | 38.983261 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 38.605377 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
32 | Locked | 38.983261 | 0 | 0 |
33 | Locked | 38.605377 | 0 | 0 |
34 | Locked | 38.605377 | 0 | 0 |
35 | Locked | 40.366287 | 0 | 0 |
36 | Locked | 38.983261 | 0 | 0 |
on 12-02-2022 17:50
Channel Channel Width (MHz) FFT Type Number of Active Subcarriers Modulation (Active Profile) First Active Subcarrier (Hz)
37 | 94 | 4K | 1840 | QAM4096 | 424 |
Channel ID Lock Status RxMER Data (dB) PLC Power (dBmV) Correcteds (Active Profile) Uncorrectables (Active Profile)
37 | Locked | 41 | 2.8 | 183831441 | 0 |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 44 | 5120 KSym/sec | 64QAM | 1 |
2 | 46200000 | 43.3 | 5120 KSym/sec | 64QAM | 2 |
3 | 32600000 | 44 | 5120 KSym/sec | 64QAM | 4 |
4 | 39400000 | 43.8 | 5120 KSym/sec | 64QAM | 3 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cmreg-vmdg640-bbt076-b.cm |
SFID | 59256 |
Max Traffic Rate | 1230000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 59255 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 44 | 5120 KSym/sec | 64QAM | 1 |
2 | 46200000 | 43.3 | 5120 KSym/sec | 64QAM | 2 |
3 | 32600000 | 44 | 5120 KSym/sec | 64QAM | 4 |
4 | 39400000 | 43.8 | 5120 KSym/sec | 64QAM | 3 |
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
2 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
Network access | true |
Maximum Number of CPEs | 1 |
Baseline Privacy | true |
DOCSIS Mode | 3.1 |
Config file | cmreg-vmdg640-bbt076-b.cm |
SFID | 59256 |
Max Traffic Rate | 1230000450 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 59255 |
Max Traffic Rate | 55000270 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
Sat 12/02/2022 09:17:08 | 6 | SW Download INIT - Via Config file cmreg-vmdg640-bbt076-b.cm |
Sat 12/02/2022 09:18:22 | 6 | SW download Successful - Via Config file |
Sat 12/02/2022 09:20:57 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/02/2022 09:48:43 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Thu 01/01/1970 00:01:20 | 3 | No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/02/2022 10:15:51 | 5 | MIMO Event MIMO: Stored MIMO=-1 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Sat 12/02/2022 11:01:11 | 4 | DHCP RENEW WARNING - Field invalid in response v4 option;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
on 14-02-2022 15:03
on 15-02-2022 10:44
Okay stats are all fine. Can you setup and share a BQM please? www.thinkbroadband.com/ping
Also if you are using a Windows device, can you test with a wired connection using "Safe Mode with Networking support"
As for the Cat 8 cable, that's a bit overkill and sometimes the shielding on these cables can affect the connection in the ethernet ports. Best to stick to a Cat 6a or even a Cat 5e, both are quite capable of Gigabit speeds.
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 15-02-2022 11:33
Thanks for your response, Adduxi
I set up a BQM a few days ago:-
The poor speeds that I've experienced are mainly via a Windows 11 desktop, which was previously getting 660+mb on M600, before I upgraded. So, dropping back to 300mb is disappointing.
I've tried safe mode with networking, as well as wiring up a Windows 10 laptop as the only device attached to the hub, to no avail. Samknows suggests 1100mb to the router but <300mb to the PC.
John
on 16-02-2022 13:14
@Stumbler wrote:<snip> a Windows 10 laptop as the only device attached to the hub, to no avail. Samknows suggests 1100mb to the router but <300mb to the PC. John
There is the issue, VM will acknowledge full speed to the Hub. Not too sure where you will go from here? If you have a good Cat 6a cable and wired directly to the Hub, there is not much else you can test with. Strange .....
BTW, the BQM link is not working, I suspect your WAN IP is incorrect ?
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 16-02-2022 13:38
@Adduxi, thanks for your time on this.
Not sure what happened to the BQM link, but here is a snapshot from Sunday :-
VM's problem management is a disgrace really. They are quick to send an engineer. And, even quicker to close the problem record (if there is one!), whether the issue is resolved or not!
Thanks again.
John
on 12-04-2022 17:02
on 12-04-2022 17:15