Menu
Reply
Cutters1982
  • 24
  • 0
  • 0
Tuning in
1,224 Views
Message 1 of 29
Flag for a moderator

Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Hiya

I'm based in Hertford, SG13 postcode, and all of a sudden over the course of the last few days I've been getting limited speeds on the M350 package (it's not just on my PC, it's across all devices).

I'm achieving, at most, 85mb/sec, I know certain parts of the UK wish they could get that speed, but at the end of the day, I am paying to get a certain speed, and for the past few days I've been getting a quarter of the normal speed, and occasionally only a fifth of what it is normally.

I have tried restarting the SuperHub, rebooting my PC, changing to default settings, all the usual stuff. I've also checked all local devices for viruses so as to rule out of the equation.

Hope someone can assist asap, this hasn't been a problem for a long period of time so it's not like a capacity issue on the local server in Ware, this has only occurred in the last few days.

Thanks in advance

(PS. It's saying I am exceeding the 20,000 character limit, so I will post the Downstream/Upstream Logs & Network Log in a 2nd post.

Speed Test
https://www.speedtest.net/result/8322461107

0 Kudos
Reply
Cutters1982
  • 24
  • 0
  • 0
Tuning in
1,223 Views
Message 2 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1323000000-0.240256 qam24
2139000000540256 qam1
31470000003.940256 qam2
41550000003.940256 qam3
5163000000440256 qam4
6171000000440256 qam5
71790000003.440256 qam6
81870000003.540256 qam7
9195000000440256 qam8
102030000003.540256 qam9
112110000002.740256 qam10
122190000002.240256 qam11
132270000002.240256 qam12
142350000002.240256 qam13
152430000001.240256 qam14
16251000000140256 qam15
172590000000.740256 qam16
182670000001.240256 qam17
192750000001.440256 qam18
202830000000.740256 qam19
21291000000140256 qam20
222990000001.240256 qam21
233070000000.440256 qam22
24315000000-0.240256 qam23



Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.3300
2Locked40.9800
3Locked40.91890
4Locked40.33011677528207
5Locked40.98993633805491
6Locked40.9879303062169
7Locked40.911874783813888
8Locked40.936791221157741
9Locked40.31520
10Locked40.930
11Locked40.9200
12Locked40.9180
13Locked40.9320
14Locked40.9260
15Locked40.3130
16Locked40.390
17Locked40.970
18Locked40.918770
19Locked40.92135430
20Locked40.97841622656
21Locked40.961085514
22Locked40.9382270
23Locked40.3700
24Locked40.9350

 

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1603000004.95512064 qam91
2537000004.8512064 qam92



Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000

 

Network Log

Time Priority Description

09/06/2019 06:37:47Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:37:48Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:37:49Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:37:49Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:47:56Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:47:56Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:1Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:3Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:4Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:51:50Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:51:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:29Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:31Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:05:5Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:05:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:15:43Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:15:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply
Adduxi
  • 2.92K
  • 221
  • 624
Trouble shooter
1,200 Views
Message 3 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

You will need an engineer to visit.  There is noise on the line (Post RS Errors) and you are missing 2 US channels. You have only 2 and there should be 4.

You can make sure the connections are all finger tight as a first fix, but if they are okay, then phone VM to arrange an engineer.

0 Kudos
Reply
Cutters1982
  • 24
  • 0
  • 0
Tuning in
1,192 Views
Message 4 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Hi

Is it definitely only me affected? Are Engineer visits chargeable? With regards to the upstream channels thing, is that something to do with the config, are VM Support able to do something remotely to try and sort that out? The fact only 2 channels are available out of 4 sounds like something the Engineer can't fix themselves.

If there is noise it suggests its on the equipment at the exchange, right? Because this is cable it doesn't use a normal phone line so I can't plug in a phone and check for noise at my end 😞

0 Kudos
Reply
jem101
  • 1.62K
  • 229
  • 758
Very Insightful Person
Very Insightful Person
1,186 Views
Message 5 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

By noise we mean interference, there's no exchange (well there sort of is but not really the same as a conventional telephone exchange). There is some interference coming into your hub from somewhere which is causing it to fail to lock onto two of the available upstream channels. The power levels on the two remaining upstream channels are at the upper end of what is acceptable and the excessing error rate on almost half of your downstream channels just confirms that you have a bad cable joint somewhere.

You need an engineer visit, which isn't chargeable as VM are responsible for everything up to and including the Hub itself. You can try calling into the line but this can sometimes be a bit of a mission, to convince the offshore help desk that you need a visit rather than messing about with wifi channels etc. Alternatively if you can hang on, one of the forum team should spot this thread within a couple of days and get in touch directly to arrange things.

0 Kudos
Reply
griffin
  • 11.8K
  • 1.08K
  • 2.57K
Alessandro Volta
1,162 Views
Message 6 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Your CMTS could be configured for 2 upstream channels as your local circuit has not been upgraded to use 4 upstream channels. (mine hasn't)

The Upstream power levels are nowhere near max transmit for two channels on 64QAM.
There is no evidence in the logs that the upstream is in distress.

However as pointed out, it looks like you have some noise ingress on the downstream looking at the RS errors and the network logs support this.

Are you experiencing the poor speeds on a wired or wireless connection to the Hub?

Whilst you may have an intermittent local circuit problem, you may have wireless problems as well, so it is best to confirm this by testing with a wired connection direct to the Hub.

0 Kudos
Reply
Cutters1982
  • 24
  • 0
  • 0
Tuning in
1,154 Views
Message 7 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Hi all

Thanks for the replies.

Before having to ring the helpline (no offence, but it's like going to the dentist!), out of desperation, I left the cable unplugged for around 40 minutes, connected back up and ran a test and I'm getting normal speeds again, and no more post RS errors, so that seemed to do the trick, does that suggest that there is something wrong at the local UBR, maybe I was on a port that has noise on it and its now moved me to a different port, perhaps?

Seems strange that it fixed itself, suggests that its equipment at the UBR and not at my end, but I may be wrong?

Anyway, gladly the problem has gone away now, hopefully not temporarily.

Cheers

0 Kudos
Reply
jem101
  • 1.62K
  • 229
  • 758
Very Insightful Person
Very Insightful Person
1,149 Views
Message 8 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Then quickly do me a big favour, run a speed test and confirm that both the down and upstream are what you expect them to be, then get the stats from the modem as before and take a look. If the performance is fine then we can see how many channels you are supposed to get and the power values for them.  Remember that the Pre and Post RS error count gets reset when the Hub is rebooted so we do expect them to be low to start off with, what we don't want is for the figures to start rising rapidly again. 

Cutters1982
  • 24
  • 0
  • 0
Tuning in
1,157 Views
Message 9 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Yeah, no problem! 🙂 Speeds are as I expect them to be again now

Speedtesthttps://www.speedtest.net/result/8323341503

Downstream bonded channels

Channel Frequency (Hz) Power (dBmV) SNR (dB) Modulation Channel ID

1323000000-0.540256 qam24
21390000005.140256 qam1
31470000004.440256 qam2
41550000004.440256 qam3
5163000000440256 qam4
61710000003.940256 qam5
71790000003.540256 qam6
8187000000440256 qam7
91950000004.340256 qam8
10203000000340256 qam9
11211000000340256 qam10
12219000000240256 qam11
13227000000240256 qam12
142350000001.740256 qam13
152430000001.240256 qam14
16251000000140256 qam15
172590000000.440256 qam16
182670000000.540256 qam17
192750000000.440256 qam18
20283000000040256 qam19
212910000000.740256 qam20
222990000000.940256 qam21
233070000000.240256 qam22
24315000000-0.440256 qam23

Downstream bonded channels

Channel Locked Status RxMER (dB) Pre RS Errors Post RS Errors

1Locked40.3120
2Locked40.3760
3Locked40.9670
4Locked40.9630
5Locked40.93700
6Locked40.9491120
7Locked40.911550
8Locked40.3260
9Locked40.9120
10Locked40.900
11Locked40.990
12Locked40.340
13Locked40.990
14Locked40.350
15Locked40.990
16Locked40.3100
17Locked40.990
18Locked40.370
19Locked40.990
20Locked40.990
21Locked40.9120
22Locked40.3100
23Locked40.940
24Locked40.3210

 

0 Kudos
Reply
Cutters1982
  • 24
  • 0
  • 0
Tuning in
1,156 Views
Message 10 of 29
Flag for a moderator

Re: Suddenly only getting 80mb/sec max on the M350 package (SuperHub 3, Ethernet connection)

Upstream bonded channels

Channel Frequency (Hz) Power (dBmV) Symbol Rate (ksps) Modulation Channel ID

1603002734.825512064 qam91
2537002584.725512064 qam92

Upstream bonded channels

Channel Channel Type T1 Timeouts T2 Timeouts T3 Timeouts T4 Timeouts

1ATDMA0000
2ATDMA0000

Network Log

Time Priority Description

09/06/2019 06:48:1Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:3Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:3Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:48:4Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:51:50Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 06:51:50Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:29Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:30Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:31Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:02:32Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:05:5Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:05:7Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:15:43Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:15:45Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:49:2Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 07:49:10Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 08:19:33Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 08:28:4Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 08:28:15Warning!Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
09/06/2019 08:28:17Warning!RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
0 Kudos
Reply