cancel
Showing results for 
Search instead for 
Did you mean: 

Poor upload speeds - under 1 Mbps on VM Hub 5 Router

ozzy3
Joining in

Hi,

We've been experiencing very poor upload speeds (under 1 Mbps) on the VM Hub 5 Router when I should be getting between 48-52 Mbps for the 1 gig tariff, download speed seems to be good (around 757 Mbps) - these figures are based on SamKnows RealSpeed test - the download speed going to the router is 1 Gbps whilst the upload speed is 0.3 Mbps whilst the download speed from the router to the laptop is 757 Mpbs whilst the upload speed remains low. This has been going on for the past couple of weeks causing issues with regards to working from home.

I have reset the router a couple of times and rebooted it a few times, checked all cables are tight, etc. I called VM and they told me that there's an outage but I don't understand how an outage can cause the upload speed to be extremely low but the download speed to remain fine.

I'll post the router status in the next posts to see if someone can identify what the issues might be.

1 ACCEPTED SOLUTION

Accepted Solutions


The fault on the upstream looks to be as described.

The Upstream channels are impacted, this group of 5 are all at QAM 16 the slowest rate,  QAM 64 for all 5 is the normal mode.

Client62_0-1673637346650.png

Regarding how Downstream is fine but Upstream is not, the two directions use different frequencies,
damage to a cable in the local area can result in a degraded performance
on either or both the Upstream and Downstream.

See where this Helpful Answer was posted

7 REPLIES 7

ozzy3
Joining in

Cable Modem StatusItem Status Comments

Acquired Downstream Channel(Hz)306000000Locked
Ranged Upstream Channel(Hz)49600000Ranged
Provisioning StateOnlineOperational

 

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
13060000006.739QAM 25622
21380000007.939QAM 2561
31460000007.939QAM 2562
41540000007.639QAM 2563
51620000007.339QAM 2564
61700000006.739QAM 2565
71780000006.439QAM 2566
81860000006.239QAM 2567
91940000006.639QAM 2568
102020000006.539QAM 2569
112100000006.839QAM 25610
122180000006.639QAM 25611
132260000006.239QAM 25612
142340000005.939QAM 25613
152420000005.739QAM 25614
162500000005.639QAM 25615
17258000000639QAM 25616
182660000005.739QAM 25617
192740000005.639QAM 25618
202820000005.739QAM 25619
21290000000639QAM 25620
222980000006.339QAM 25621
233140000006.839QAM 25623
243220000006.739QAM 25624
253300000006.639QAM 25625
263380000006.638QAM 25626
273460000006.438QAM 25627
283540000005.738QAM 25628
293620000005.338QAM 25629
30370000000538QAM 25630
313780000004.838QAM 25631

 

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1Locked3900
2Locked3900
3Locked3900
4Locked3900
5Locked3900
6Locked3900
7Locked3900
8Locked3900
9Locked3900
10Locked3900
11Locked3900
12Locked3900
13Locked3900
14Locked3900
15Locked3900
16Locked3900
17Locked3900
18Locked3900
19Locked3900
20Locked3900
21Locked3900
22Locked3900
23Locked3900
24Locked3900
25Locked3900
26Locked3800
27Locked3800
28Locked3800
29Locked3800
30Locked3800
31Locked3800

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000029.55120QAM 161
14310000028.35120QAM 162
23660000026.85120QAM 163
330100000275120QAM 164
42360000027.85120QAM 169

 

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
0ATDMA0000
1ATDMA0090
2ATDMA0020
3ATDMA0000
4ATDMA0000

ozzy3
Joining in

General Configuration

Network access Allowed
Maximum Number of CPEs 1
Baseline Privacy Enabled
DOCSIS Mode 3.1
Config file cmreg-vmdg660-bbt076-b.cm
Primary Downstream Service Flow

SFID 63600
Max Traffic Rate 1230000450 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps

Primary Upstream Service Flow

SFID 63599
Max Traffic Rate 55000270 bps
Max Traffic Burst 42600bytes
Min Traffic Rate 0 bps
Max Concatenated Burst 42600bytes
Scheduling Type Best Effort

 

Network Log

Time Priority Description
13-01-2023 18:37:37criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2023 18:36:23noticeREGISTRATION COMPLETE - Waiting for Operational status
13-01-2023 18:36:19criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2023 18:36:16noticeUS profile assignment change. US Chan ID: 10; Previous Profile: 13; New Profile: 12 13.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2023 18:36:11noticeDS profile assignment change. DS Chan ID: 32; Previous Profile: ; New Profile: 1 2 3.;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2023 18:35:58warningDHCP WARNING - Non-critical field invalid in response ;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2023 18:35:56noticeHonoring MDD; IP provisioning mode = IPv4
13-01-2023 18:35:44criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
13-01-2023 18:35:33criticalCable Modem Reboot due to power button reset
12-01-2023 12:46:21criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-01-2023 12:45:44criticalReceived Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-01-2023 12:44:55criticalStarted Unicast Maintenance Ranging - No Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-01-2023 12:44:49criticalSYNC Timing Synchronization failure - Failed to acquire QAM/QPSK symbol timing;;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.1;
12-01-2023 12:44:37criticalCable Modem do Reboot Factory reset UI


The fault on the upstream looks to be as described.

The Upstream channels are impacted, this group of 5 are all at QAM 16 the slowest rate,  QAM 64 for all 5 is the normal mode.

Client62_0-1673637346650.png

Regarding how Downstream is fine but Upstream is not, the two directions use different frequencies,
damage to a cable in the local area can result in a degraded performance
on either or both the Upstream and Downstream.

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
04960000029.55120QAM 161
14310000028.35120QAM 162
23660000026.85120QAM 163
330100000275120QAM 164
42360000027.85120QAM 169

 


 

Your upstream channels are out of spec on QAM, which should be 64 on all channels. QAM is the equivalent of bandwidth so it explains the slow upload speed.

 

Edit: beat me to it...

Tudor
Very Insightful Person
Very Insightful Person

Check with Area faults on 0800 561 0061 If you have a VM landline 150 this goes down to post code level. You could also try the web page status, but this is not recommended as it only covers issues that affect a very large number of customers.

VM will not dispatch any technicians while an area fault exists.

If no area faults found:

The primary place to report faults or for service requests is Customer Services on 0345 454 1111/150 if you have a VM landline or wait two or three days for a VM staff member to get to your post.


Tudor
There are 10 types of people: those who understand binary and those who don't and F people out of 10 who do not understand hexadecimal c1a2a285948293859940d9a49385a2

Thank you very much for your response Client62, it makes sense.

I was told that there's an area fault which is affecting the upload speeds and should be resolved tomorrow (17th January).

Many thanks to everyone else who has responded to my post.

Hey ozzy3, thank you for reaching out and a warm welcome to the community I am sorry to see you are having some connection issues.

I have taken a look and I can see from our side there is an SNR outage lasting until the 31st January 2023.

I am sorry about any trouble this may cause can you keep an eye on any updates here. Thanks 

Matt - Forum Team


New around here?