Menu
Reply
  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
194 Views
Message 1 of 14
Flag for a moderator

increased upload contention(?) recently

Hello:

I almost love my Vivid 200 Gamer service which can provide in excess of 200 Mbps down / 20 Mbps up connection.

Since switching to the Gamer package I was able to consistently upload at a full 20 Mbps (single stream) to a London server with no issues. Then starting about a week ago (so in the first week of Feb 2017) I noticed I could not do that anymore, and my average upload speed to that same server, single stream, was about 15 Mbps and if you watch a graph of the speed it is constantly wavering from aprox 10Mbps to 16Mpbs. This happens at any time of day and weekdays similar to weekends. Maybe that's an argument against contention which would be worse sometimes than others.

If I run two or three streams I can get back up to the full 20 Mbps, so it's not that my modem is syncing slower or I've been capped or anything, it seems to be increased contention or a bad route.

I'm in Area 20 (Brighton). I also just received a letter from VM that they are starting (or have started) the Virgin Wifi system that uses people's SuperHub 3 devices to provide wifi for VM Wifi customers who happen to be near one's Superhub. Could this be putting increased load on the Virgin backhaul in my area?

It could also just be a malfunctioning router along the way, but frustratingly Virgin blocks some traceroute and MTR paths -- sometimes I can only traceroute or MTR 3 or 4 hops from home before it stops completely, and from the server back to me is really more like 15 hops. Even if I can get a full traceroute (like just now) hops 4 - 9 and 14 don't reply to pings.

Anyone else notice a change lately? Or if Virgin would like to respond as to congestion of their network in my area having increased in the past few weeks?

Thank you.

0 Kudos
Reply
  • 5.65K
  • 290
  • 1.25K
Superuser
Superuser
182 Views
Message 2 of 14
Flag for a moderator

Re: increased upload contention(?) recently

If the stream is only on 1 channel then it doesn't take much from other customers to overload the channel. AFAIK they can do ~50Mbs each channel. So 3 customers uploading on same channel can start the contention. This is why you should be provisioned with 4 on the gamer package (although depends on the CMTS still) so your upload is spread out over the channels and not impacting all on 1.
~~~~~~~~~~~~~~~~~~~~~~~~~
All posts made are personal opinions as I do not work for VirginMedia.
Kudo's a post if you find it useful and want to say thanks
Mark a post as a helpful answer if it answers your question

0 Kudos
Reply
  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
171 Views
Message 3 of 14
Flag for a moderator

Re: increased upload contention(?) recently

Hello:

I didn't say anything about upstream channels, my SH3 is connecting normally I expect (stats below), I just meant that a single large file upload can't saturate the connection anymore, but if I upload two or three files in parallel (or use a speed tester that cranks up many streams) I can still saturate it.

 

Acquired Downstream Channel(Hz)
298750000
Locked
Ranged Upstream Channel(Hz)
35800000
Locked
Provisioning State
Online

 

1298750000-238.9256 qam17
2322750000-1.540.3256 qam20
3314750000-1.740.3256 qam19
4306750000-1.740.3256 qam18
5290750000-2.240.3256 qam16
6282750000-2.440.3256 qam15
7274750000-2.440.3256 qam14
8266750000-2.240.3256 qam13
9258750000-2.240.3256 qam12
10250750000-2.240.3256 qam11
11242750000-240.3256 qam10
12234750000-240.3256 qam9
13226750000-1.940.3256 qam8
14218750000-1.740.3256 qam7
15210750000-1.740.3256 qam6
16202750000-1.740.3256 qam5
17194750000-1.540.9256 qam4
18186750000-1.440.3256 qam3
19178750000-1.240.9256 qam2
20170750000-1.240.3256 qam1

 

5035800000ATDMA44.864 qam64000005120
5253700000ATDMA44.864 qam64000005120

 

General Configuration Value

Network access
Enabled
Maximum Number of CPEs
1
Baseline Privacy
Enabled
Docsis Mode
Docsis30
Config file
V42997a858765887c.cm
Primary Downstream Service Flow
SFID416482
Max Traffic Rate230100000
Primary Upstream Service Flow
SFID416481
Max Traffic Rate22000000

 

2017-02-01 00:08:36.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-01 16:41:22.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-01 17:37:21.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-01 23:27:01.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-02 08:03:41.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-06 01:55:35.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-06 12:26:20.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-06 15:21:18.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-06 18:15:33.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-06 22:04:10.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-06 23:44:25.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-07 01:25:36.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-07 04:47:05.0068010400DHCP REBIND WARNING - Field invalid in response;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-07 20:58:56.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-15 12:49:16.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-15 16:39:22.0082000200No Ranging Response received - T3 time-out;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;
2017-02-16 04:24:31.0068010100DHCP RENEW sent - No response for IPv4;CM-MAC=xxx;CMTS-MAC=xxx;CM-QOS=1.1;CM-VER=3.0;

 

I xxx'ed out the MAC addresses. Thanks.

0 Kudos
Reply
  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
147 Views
Message 4 of 14
Flag for a moderator

Re: increased upload contention(?) recently

I realise my line stats didn't post in a very readable manner, but would anyone be able to have a look and see if they are within spec? Thank you.

0 Kudos
Reply
  • 5.65K
  • 290
  • 1.25K
Superuser
Superuser
141 Views
Message 5 of 14
Flag for a moderator

Re: increased upload contention(?) recently

They are in spec, and don't worry we are used to reading like that. sorry thought I had posted that, guess I must not of hit send.
~~~~~~~~~~~~~~~~~~~~~~~~~
All posts made are personal opinions as I do not work for VirginMedia.
Kudo's a post if you find it useful and want to say thanks
Mark a post as a helpful answer if it answers your question

  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
136 Views
Message 6 of 14
Flag for a moderator

Re: increased upload contention(?) recently

thanks
0 Kudos
Reply
  • 6.62K
  • 174
  • 438
Forum Team
Forum Team
110 Views
Message 7 of 14
Flag for a moderator

Re: increased upload contention(?) recently

Hi NoResyncsPlease,

 

Sorry about the connection fault experienced.

 

I've already responded to you post in a separate thread regarding this.

 

Looking at everything from this end, I've not been able to find any obvious cause for the issue.

 

I've noticed though that you're utilising modem mode at the moment and as mentioned in my other post, I'd definitely recommend disconnecting any third party equipment that may be connected to ours such as a third party router, etc.

 

Nat_J


Who's who? Find out more about our community members. Good folk to know


0 Kudos
Reply
  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
94 Views
Message 8 of 14
Flag for a moderator

Re: increased upload contention(?) recently

Is it correct that on Vivid 200 Gamer (200/20) package my modem should be connected with only two upstream channels?

5035800000ATDMA44.864 qam64000005120
5253700000ATDMA44.864 qam64000005120
0 Kudos
Reply
  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
81 Views
Message 9 of 14
Flag for a moderator

Re: increased upload contention(?) recently

Ch ID  Freq	   Mode    Power Mod	BW(Hz)	SRate (ksps)
50	35800000   ATDMA   44.8	64 qam	6400000	5120
52	53700000   ATDMA   44.8	64 qam	6400000	5120

 

0 Kudos
Reply
  • 56
  • 0
  • 5
NoResyncsPlease
On our wavelength
62 Views
Message 10 of 14
Flag for a moderator

Re: increased upload contention(?) recently

now one of my upstream channels has switched to QAM 32:

 

Upstream bonded channels
Channel ID	Frequency(Hz)	Mode	Power
(dBmV)	Modulation	Channel Bandwidth(Hz)	Symbol Rate (ksps)
50	35800000	ATDMA	45	32 qam	6400000	5120
52	53700000	ATDMA	45	64 qam	6400000	5120

and recent logs:

2017-02-21 13:24:58.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-02-21 13:24:58.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-02-21 13:24:58.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-02-21 13:24:58.00 84000500 SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-02-21 13:24:59.00 84000700 RCS Partial Service;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
2017-02-22 05:42:19.00 82000200 No Ranging Response received - T3 time-out;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;

0 Kudos
Reply