Odd VM 50meg Issue (Works fine then goes slow like its capped)

Thesnipergecko · 16 Jul 2009 at 15:34

HEADRAT said:
Mine is now behaving most of the time.

Was yours behaving the same way as mine? (shown in screencast)

x Darkchild · 16 Jul 2009 at 15:47

http://www.techdigest.tv/2008/03/virgin_media_sp.html

I used to have virgin 2meg but changed as soon as i heard about them throttling speeds, i dont know if they throttle speeds when your on 50meg internet.
Anyway if you have anybody in the house with an O2 contract go with o2 14meg with the discount (works out cheap and the service is top notch)

Phemo · 16 Jul 2009 at 16:46

50mbit has no throttling, there is something else on the network screwing it up for some users.

As for my issue, Virgin actually said themselves they had no other suggestions apart from to try a modem swap. They have now swapped out my modem and it's unsurprisingly still exactly the same. I guess if they have no ideas that should qualify for cancellation.

Nogimmix · 17 Jul 2009 at 12:16

Are you using Windows Vista?

Reason I ask is I had this problem the other day - for some strange reason my 50meg connection went from 5.5mbps to 1.1mbps. I checked everything, done speed tests etc and it was still stuck at 1.1mbps.

I decided to install Windows 7 and low and behold my connection was back to 5.5mbps. If you are running Vista it might be a problem with that.

Wyrdo · 17 Jul 2009 at 15:06

Thesnipergecko said:
I recently upgraded from 20meg to 50meg. In the last few weeks I was seeing phenominal speeds from 20meg, I was getting upwards of 2.5MBp/s with it.

Anywho, after upgrading to 50meg and getting the new modem, after downloading a few gig's worth of data via newsgroups the connection seems to struggle and speeds go from 5.5MBp/s to less than 1MBp/s.

Not only when do my newsgroups go slow the whole HTTP goes slow too. The problem seems to get rectified after turning the modem off for 20 seconds then turning it back on.

I have tried all different combinations of hardware to make sure than the problem is with the modem.

Any idea's? Could I have gotten a duff modem?

Myself and lots of other people have had exactly the same problem - mine seems to have been fine lately but I haven't been downloading as much so may just not have noticed it. It usually lasts for 5 minutes then you're back to full speed again.

Terrier_Jimlad · 17 Jul 2009 at 15:25

i thought on 50mb after you download 4GB between the hours of 16:00 and 12:00, then your connection is dropped to something daft like 3mb/sec ... part of their fair usage policy traffic shaping ...

HEADRAT · 17 Jul 2009 at 15:35

There is no STM on 50Mbps

Thesnipergecko · 28 Jul 2009 at 10:31

Right!

Had the engineer's out again today. They are now saying the issue is with Software Version : 3.11.1010 of the modems firmware. They are working on fixing this and version 3.11.1011 should be rolling out "soon".

Wheres that Massive roll eyes emote when you need it.

HEADRAT · 28 Jul 2009 at 10:41

I'm running 3.11.1011

HEADRAT

Thesnipergecko · 28 Jul 2009 at 10:44

I'm still on 3.11.1010. Has it resolved your issues HEADRAT?

Jabbs · 28 Jul 2009 at 10:59

I'm on same version as Headrat and i get a issue where i have to unplug the modem can be from 3-9 times a day as my internet just stops working, soon as i plug it back in its fine.

HEADRAT · 28 Jul 2009 at 10:59

I still get the occasional slowdown, doesn't seem to be as bad as it was before.

Thesnipergecko · 28 Jul 2009 at 11:01

Jabbs said:
I'm on same version as Headrat and i get a issue where i have to unplug the modem can be from 3-9 times a day as my internet just stops working, soon as i plug it back in its fine.

The firmware programmers said version 1011 should fix that issue. Doesn't look good. They have no idea when it will be rolling out in my area. I just have to wait and see and put up with it.

Jabbs · 28 Jul 2009 at 11:04

I never really noticed when it was that firmware ill keep you posted if it goes off, for all i know they could have done it yesterday.

Thesnipergecko · 28 Jul 2009 at 20:52

Had a call earlier, they forced the update to my modem via mac address. I'm now on 3.11.1011 and my problem has gotten worse. I cannot get over 10meg now!

They think the modem may be fubar now. They are going to do some tests over the next few days on the line and get a new modem out to me.

Jabbs · 28 Jul 2009 at 22:14

Well so far today my connection hasn't dropped once, so touch wood it will stop like this.

Thesnipergecko · 29 Jul 2009 at 16:02

Here is what my modem is saying:

Code:

Fri Jul 24 10:46:11 2009 	Fri Jul 24 11:36:07 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Sun Jul 26 18:52:47 2009 	Sun Jul 26 18:52:47 2009 	Notice (6) 	DHCP Renew - lease parameters tftp file- modifie;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Mon Jul 27 20:43:14 2009 	Tue Jul 28 07:17:04 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 09:06:07 2009 	Tue Jul 28 09:22:27 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 09:27:56 2009 	Tue Jul 28 10:04:51 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 15:43:03 2009 	Tue Jul 28 15:43:03 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 15:43:04 2009 	Tue Jul 28 15:43:04 2009 	Notice (6) 	SW Download INIT - Via Config file 834ncxv9873254k;fg8
Tue Jul 28 15:43:58 2009 	Tue Jul 28 15:43:58 2009 	Notice (6) 	SW download Successful - Via Config file
Tue Jul 28 15:45:01 2009 	Tue Jul 28 15:54:25 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 16:01:12 2009 	Tue Jul 28 16:43:06 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 16:58:56 2009 	Tue Jul 28 16:58:56 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Tue Jul 28 17:46:04 2009 	Tue Jul 28 23:30:40 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:26:25 2009 	Wed Jul 29 09:26:25 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:26:40 2009 	Wed Jul 29 09:26:40 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:34:52 2009 	Wed Jul 29 09:34:52 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:35:22 2009 	Wed Jul 29 09:35:22 2009 	Critical (3) 	Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:35:34 2009 	Wed Jul 29 09:35:34 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:35:35 2009 	Wed Jul 29 09:35:35 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:35:43 2009 	Wed Jul 29 09:35:43 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:35:50 2009 	Wed Jul 29 09:35:50 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:41:40 2009 	Wed Jul 29 09:41:55 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:41:56 2009 	Wed Jul 29 09:41:56 2009 	Critical (3) 	Ranging Request Retries exausted;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:41:56 2009 	Wed Jul 29 09:41:56 2009 	Critical (3) 	Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:42:07 2009 	Wed Jul 29 09:42:07 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:52:02 2009 	Wed Jul 29 09:52:02 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 09:52:15 2009 	Wed Jul 29 09:52:15 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:03:58 2009 	Wed Jul 29 10:03:58 2009 	Critical (3) 	No Ranging Response received - T3 time-out;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:05:32 2009 	Wed Jul 29 10:05:32 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:05:43 2009 	Wed Jul 29 10:05:43 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:07:54 2009 	Wed Jul 29 10:07:54 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:08:06 2009 	Wed Jul 29 10:08:06 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:09:12 2009 	Wed Jul 29 10:09:12 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:09:25 2009 	Wed Jul 29 10:09:25 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:11:27 2009 	Wed Jul 29 10:11:27 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:11:38 2009 	Wed Jul 29 10:11:38 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:11:43 2009 	Wed Jul 29 10:11:43 2009 	Critical (3) 	Unicast Ranging Received Abort Response - initializing MAC;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;
Wed Jul 29 10:11:54 2009 	Wed Jul 29 10:11:54 2009 	Notice (6) 	TLV-11 - unrecognized OID;CM-MAC=00:22:68:f0:8a:7d;CMTS-MAC=00:1d:45:70:29:3c;CM-QOS=1.1;CM-VER=3.0;

Code:

T1 Timeouts	0
T2 Timeouts	0	0	0	0
T3 Timeouts	37	0	0	0
T4 Timeouts	1	0	0	0

Code:

Power Level
(dBmV) 	4.81	4.23	3.49	N/A
RxMER
(dB) 	38.26	38.26	38.26	N/A
Correctable
Codewords 	25	22	39	N/A
Uncorrectable
Codewords 	908	395	1009	N/A

It has gotten worse since the new firmware update.

Jabbs · 29 Jul 2009 at 16:33

So far so good for me not sure when they updated my modems firmware but this the second day with out the issue of having to reboot the modem around 5 times a day and speeds have settled down well now.