Menu
Reply
azcom
  • 8
  • 0
  • 2
Tuning in
482 Views
Message 1 of 6
Flag for a moderator

M350 only getting around 80 Megabits down lately

First a little history:

When I first got this broadband connection back in January I had some immediate issues with it. Long story short the engineer that came to fix it found that the problem was due to a faulty RF network tap in the street cabinet. He swapped me over to another tap and everything was immediately as expected and I was getting download speeds around the 320 Mbps mark. This was the case for some time.

Jump forward to today:

I am now receiving only around a quarter of that speed, roughly 70-80 Mbps on average. The speed is obviously much lower than I was getting before and far below the Minimum guaranteed download speed of 181 Mbps stated in my contract.

I cannot be sure exactly how long this has been going on for but I first noticed it probably a couple of months ago now. I had hoped it may have corrected itself but it hasn't so now I want it sorted.

Router stats included in following post:

0 Kudos
Reply
azcom
  • 8
  • 0
  • 2
Tuning in
478 Views
Message 2 of 6
Flag for a moderator

Re: M350 only getting around 80 Megabits down lately

Cable Modem StatusItem Status Comments
Acquired Downstream Channel (Hz)
474250000
Locked
Ranged Upstream Channel (Hz)
32599959
Locked
Provisioning State

 


Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID
1 474250000 2.9 38 256 qam 9
2 410250000 4.5 38 256 qam 1
3 418250000 4.4 38 256 qam 2
4 426250000 4.5 38 256 qam 3
5 434250000 4.3 38 256 qam 4
6 442250000 4 38 256 qam 5
7 450250000 3.5 38 256 qam 6
8 458250000 3.4 38 256 qam 7
9 466250000 3.4 38 256 qam 8
10 482250000 2.7 38 256 qam 10
11 490250000 3 38 256 qam 11
12 498250000 3.5 38 256 qam 12
13 506250000 3 38 256 qam 13
14 514250000 2.7 38 256 qam 14
15 522250000 3 38 256 qam 15
16 530250000 3 38 256 qam 16
17 538250000 2.2 38 256 qam 17
18 546250000 2 38 256 qam 18
19 554250000 2 38 256 qam 19
20 562250000 1.7 38 256 qam 20
21 570250000 0.9 38 256 qam 21
22 578250000 0.7 38 256 qam 22
23 586250000 1 38 256 qam 23
24 594250000 0.2 38 256 qam 24


Downstream bonded channels
Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors
1 Locked 38.6 2823 38
2 Locked 38.6 2766 104
3 Locked 38.9 1643 82
4 Locked 38.9 2049 6
5 Locked 38.9 1430 0
6 Locked 38.9 2152 14
7 Locked 38.9 2554 47
8 Locked 38.9 3006 100
9 Locked 38.9 2969 57
10 Locked 38.9 2410 49
11 Locked 38.6 1506 24
12 Locked 38.9 1592 7
13 Locked 38.9 2281 18
14 Locked 38.9 2432 19
15 Locked 38.6 2441 36
16 Locked 38.9 2411 24
17 Locked 38.9 2453 14
18 Locked 38.6 2679 24
19 Locked 38.6 2522 41
20 Locked 38.6 3166 72
21 Locked 38.6 4049 80
22 Locked 38.6 4329 96
23 Locked 38.9 3487 76
24 Locked 38.6 4462 47

Refresh data
Upstream bonded channels
Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID
1 32599959 4.025 5120 64 qam 3
2 25799926 4.05 5120 64 qam 4
3 46200023 4.025 5120 64 qam 1
4 39399927 4 5120 64 qam 2


Upstream bonded channels
Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts
1 ATDMA 0 0 0 0
2 ATDMA 0 0 0 0
3 ATDMA 0 0 0 0
4 ATDMA 0 0 0 0

Refresh data
General Configuration
Network access
Allowed
Maximum Number of CPEs
1
Baseline Privacy
Enabled
DOCSIS Mode
Docsis30
Config file
cmreg-vmdg505-rtsxxl35016u+voc-b.cm


Primary Downstream Service Flow
SFID 182140
Max Traffic Rate 402500089
Max Traffic Burst 42600
Min Traffic Rate 0


Primary Upstream Service Flow
SFID 182139
Max Traffic Rate 38500089
Max Traffic Burst 42600
Min Traffic Rate 0
Max Concatenated Burst 42600
Scheduling Type BestEffort

Network Log
Time Priority Description
27/08/2020 18:53:5 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
26/08/2020 22:53:20 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 22:50:53 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 21:50:14 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 09:57:41 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
22/08/2020 08:59:15 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
21/08/2020 22:05:11 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2020 07:00:15 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2020 03:38:46 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
18/08/2020 02:33:55 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2020 17:34:29 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2020 04:27:59 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
17/08/2020 04:08:46 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
14/08/2020 02:58:24 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
13/08/2020 01:40:12 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 14:00:58 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 06:55:39 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
12/08/2020 02:21:48 Error DHCP RENEW sent - No response for IPv4;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
10/08/2020 04:38:52 critical No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
08/08/2020 12:54:32 Error DHCP REBIND WARNING - Field invalid in response;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply
MikeRobbo
  • 15.27K
  • 1.17K
  • 1.94K
Alessandro Volta
473 Views
Message 3 of 6
Flag for a moderator

Re: M350 only getting around 80 Megabits down lately

70 to 80Mbs is indicative of two things

A low spec / iffy ethernet cable try a different cable.

A Network Interface Card (NIC) set at 10/100 or has out of date drivers - check the NIC status / update the drivers.


*********************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************************
BT Smart Hub 2 with 70Mbs Download,18Mbs Upload, 9.17ms Latency & 0.35ms Jitter.
azcom
  • 8
  • 0
  • 2
Tuning in
418 Views
Message 4 of 6
Flag for a moderator

Re: M350 only getting around 80 Megabits down lately

After some troubleshooting led by following your advice it appears that a short patch cable between my gigabit switch & patch panel was to blame. Unfortunately this was for the feed from the router so nothing would have been operating at gigabit speeds across the network. Replacing this has restored me to full speed as can be seen below:

9989892161.png

Thank you so much for your advice. Such a stupid & simple thing, kinda makes me feel like a complete noob again!

Lee_R
  • 2.57K
  • 136
  • 239
Forum Team
Forum Team
376 Views
Message 5 of 6
Flag for a moderator

Re: M350 only getting around 80 Megabits down lately

Hi azcom

Just for clarification, are you satisfied that Virgin Media's equipment was not at fault for the slow speeds?

Regards

 

Lee_R 

0 Kudos
Reply
azcom
  • 8
  • 0
  • 2
Tuning in
347 Views
Message 6 of 6
Flag for a moderator

Re: M350 only getting around 80 Megabits down lately

Yes, that is indeed correct. In this instance Virgin Media and their equipment were not the cause of the reduction in speed.

0 Kudos
Reply