on 15-02-2022 23:29
Hey folks
We called up and got our speed upgraded from 200 to 350 Sunday 06/02. Got a Hub reboot so clearly something applied.
Current setup is Hub 4 in Modem mode, speed tests being triggered a varying times throughout the day from device connected directly to the Hub is showing no real change in speed before or after the upgrade. This falls shout of the ~180 minimum we were told to expect.
Any help spotting what's wrong or helping us get it sorted would be gratefully received.
Cheers
SFID | 92244 |
Max Traffic Rate | 402500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
SFID | 92243 |
Max Traffic Rate | 38500089 |
Max Traffic Burst | 42600 |
Min Traffic Rate | 0 |
Max Concatenated Burst | 42600 |
Scheduling Type | bestEffort |
Time Priority Description
Mon Feb 7 16:27:09 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:45:59 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:46:02 2022 | 6 | CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:46:43 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:46:47 2022 | 6 | CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:49:11 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:49:14 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:49:55 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:50:01 2022 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:50:41 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:50:48 2022 | 6 | CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:52:13 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:52:23 2022 | 6 | CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:55:23 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:55:50 2022 | 6 | CM-STATUS message sent. Event Type Code: 4; Chan ID: 12; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:55:59 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:56:13 2022 | 6 | CM-STATUS message sent. Event Type Code: 2; Chan ID: 11; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:56:45 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 16:56:53 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 17:06:08 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 17:06:32 2022 | 6 | CM-STATUS message sent. Event Type Code: 5; Chan ID: 10; DSID: N/A; MAC Addr: N/A; OFDM/OFDMA Profile ID: N/A.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Mon Feb 7 17:09:17 2022 | 5 | Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1; |
Answered! Go to Answer
on 21-02-2022 09:09
Thanks for your post on our Community Forums @Teppotastic
How's the connection performed over the weekend?
Do you have a BQM reflecting the hub's performance?
I've looked into the local area and cannot see any issues
What speed do you currently achieve when the router is in modem mode and is connected via a Cat 6 (or above) Ethernet directly to the PC?
Kindest regards,
David_Bn
on 15-02-2022 23:30
on 16-02-2022 00:08
16-02-2022 09:57 - edited 16-02-2022 09:58
@Teppotastic wrote:
Probably should have added we're normally getting around 148 (same as before the upgrade), with occasional dips down to 100.
You need to post the power levels for the Hub. From the network log you have connection problems, Lost MDD etc.
Also setup a BQM and post the shared link. www.thinkbroadband.com/ping
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 22:58
Thanks Adduxi - I've set the BQM running (well for the 2nd time, forgot to unblock ICMP)
Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
25 | 331000000 | 9.4 | 39 | QAM256 | 25 |
10 | 211000000 | 10.8 | 39 | QAM256 | 10 |
11 | 219000000 | 10.6 | 39 | QAM256 | 11 |
12 | 227000000 | 10.5 | 39 | QAM256 | 12 |
13 | 235000000 | 10.5 | 39 | QAM256 | 13 |
14 | 243000000 | 10.4 | 40.4 | QAM256 | 14 |
15 | 251000000 | 10.2 | 39 | QAM256 | 15 |
16 | 259000000 | 10.7 | 40.4 | QAM256 | 16 |
17 | 267000000 | 11.1 | 39 | QAM256 | 17 |
18 | 275000000 | 10.8 | 39 | QAM256 | 18 |
19 | 283000000 | 10.3 | 39 | QAM256 | 19 |
20 | 291000000 | 10 | 40.4 | QAM256 | 20 |
21 | 299000000 | 10.1 | 40.4 | QAM256 | 21 |
22 | 307000000 | 10.2 | 40.9 | QAM256 | 22 |
23 | 315000000 | 10.1 | 40.4 | QAM256 | 23 |
24 | 323000000 | 9.6 | 39 | QAM256 | 24 |
26 | 339000000 | 9.4 | 38.6 | QAM256 | 26 |
27 | 347000000 | 9.5 | 40.4 | QAM256 | 27 |
28 | 355000000 | 9.3 | 39 | QAM256 | 28 |
29 | 363000000 | 9.1 | 39 | QAM256 | 29 |
30 | 371000000 | 8.9 | 39 | QAM256 | 30 |
31 | 379000000 | 8.7 | 39 | QAM256 | 31 |
32 | 387000000 | 8.7 | 38.6 | QAM256 | 32 |
33 | 395000000 | 8.9 | 39 | QAM256 | 33 |
34 | 403000000 | 9 | 40.4 | QAM256 | 34 |
35 | 411000000 | 8.9 | 39 | QAM256 | 35 |
36 | 419000000 | 8.8 | 39 | QAM256 | 36 |
37 | 427000000 | 9 | 39 | QAM256 | 37 |
38 | 435000000 | 9.2 | 38.6 | QAM256 | 38 |
39 | 443000000 | 9.6 | 40.4 | QAM256 | 39 |
40 | 451000000 | 9.5 | 40.4 | QAM256 | 40 |
Channel Lock Status RxMER (dB) Pre RS Errors Post RS Errors
25 | Locked | 38.983261 | 0 | 0 |
10 | Locked | 38.983261 | 0 | 0 |
11 | Locked | 38.983261 | 0 | 0 |
12 | Locked | 38.983261 | 0 | 0 |
13 | Locked | 38.983261 | 0 | 0 |
14 | Locked | 40.366287 | 0 | 0 |
15 | Locked | 38.983261 | 0 | 0 |
16 | Locked | 40.366287 | 0 | 0 |
17 | Locked | 38.983261 | 0 | 0 |
18 | Locked | 38.983261 | 0 | 0 |
19 | Locked | 38.983261 | 0 | 0 |
20 | Locked | 40.366287 | 0 | 0 |
21 | Locked | 40.366287 | 0 | 0 |
22 | Locked | 40.946209 | 0 | 0 |
23 | Locked | 40.366287 | 0 | 0 |
24 | Locked | 38.983261 | 0 | 0 |
26 | Locked | 38.605377 | 0 | 0 |
27 | Locked | 40.366287 | 0 | 0 |
28 | Locked | 38.983261 | 0 | 0 |
29 | Locked | 38.983261 | 0 | 0 |
30 | Locked | 38.983261 | 0 | 0 |
31 | Locked | 38.983261 | 0 | 0 |
32 | Locked | 38.605377 | 0 | 0 |
33 | Locked | 38.983261 | 0 | 0 |
34 | Locked | 40.366287 | 0 | 0 |
35 | Locked | 38.983261 | 0 | 0 |
36 | Locked | 38.983261 | 0 | 0 |
37 | Locked | 38.983261 | 0 | 0 |
38 | Locked | 38.605377 | 0 | 0 |
39 | Locked | 40.366287 | 0 | 0 |
40 | Locked | 40.366287 | 0 | 0 |
41 | 96 | 4K | 1880 | QAM4096 | 759 |
41 | Locked | 42 | 5 | 362850338 | 21 |
on 16-02-2022 22:59
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 | 53700000 | 42 | 5120 KSym/sec | 64QAM | 2 |
2 | 46200000 | 41.3 | 5120 KSym/sec | 64QAM | 3 |
3 | 39400000 | 41.5 | 5120 KSym/sec | 64QAM | 4 |
4 | 60300000 | 42.3 | 5120 KSym/sec | 64QAM | 1 |
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 | 2 | 0 |
3 | US_TYPE_STDMA | 0 | 0 | 1 | 0 |
4 | US_TYPE_STDMA | 0 | 0 | 0 | 0 |
18-02-2022 08:16 - edited 18-02-2022 08:17
Just tried the reboot / off for 2mins. Sadly no change in speedtest results at ~148 Down.
Anyone got any thoughts from the information posted so far? 😕
on 21-02-2022 09:09
Thanks for your post on our Community Forums @Teppotastic
How's the connection performed over the weekend?
Do you have a BQM reflecting the hub's performance?
I've looked into the local area and cannot see any issues
What speed do you currently achieve when the router is in modem mode and is connected via a Cat 6 (or above) Ethernet directly to the PC?
Kindest regards,
David_Bn
on 21-02-2022 13:23
Thank you for responding David_Bn.
My speed tests are already executed from a device connected directly to the router in modem mode via Cat6 cable. The tests fire off at staggered intervals to provide coverage of peak and off-peak over a period of time. With an advertised speed of 350M, I'd be expecting 181+ as the minimum (according to the guidance provided during the contract change). I'm never getting above 150, even in the dead of night when other devices are off.
This is from the past 30d. The vertical blip is when the Hub rebooted following the call to upgrade my package. The previous blip was some form of temporary interruption to service, external to my home. It hasn't recurred. You can see from the rest of the graph both before and after there has been no meaningful change in speed.
BQM is here (doesn't seem to show any particular issue from my untrained eyes):
on 21-02-2022 17:16
*sigh* I'm big enough to admit when it was my fault... this one was on me, folks!
For the benefit of anyone following after me. Specifically anyone running their VM Hub in Modem mode with a 3rd party router (a Ubiquiti Dream Machine aka UDM in my case)... check your QoS and/or Smart Queues. In my case I had not remembered to adjust mine up for the new total WAN speed and had also not realised I'd applied it to the source of my speed tests. D'oh.
I am now getting speed tests results around 360M.
Thank you all - would have taken me a lot longer to get there without your questions and pointers. The cats, sadly, are not has helpful for technical troubleshooting.