Why I regret joining virgin media

[Sephiroth]

That's the point. You may have more than one problem viz. the V+ box. The two modem logs mean a common mode event occurred, I presume at your UBR or at a concentrating MUX in the street if your friend is nearby.

[speedfreak]

Originally Posted by Sephiroth

That's the point. You may have more than one problem viz. the V+ box. The two modem logs mean a common mode event occurred, I presume at your UBR or at a concentrating MUX in the street if your friend is nearby.

hes not my "friend" though he seems a nice chap, who knows our relationship might blossom lol , its just someone i stumbled across when i was looking at the newsgroups. hes pr2 i think, im pr7, we arent nearby but are on the same ubr and thats at least 3 t4 timeouts we have shared . I think i might have 2 issues like you say as my v+ issues only started after they wrongfully disconnected me.

The guy at VM didnt ring as promised though he may have tried ringing the mob number on my account and not the one cf provided him with so I'll chase him tomorrow, he said hes working on saturday. 2nd line are still chasing networks, one of the techs said the trouble with networks is they finish at 5pm and if they dont see a fault inday they just close the ticket. very reassuring lol networks were apparently last seen riding shergar across lord lucans back garden been over a week and no response from them

[simplepsy]

Hi Speedfreak, remember me?
For those who have not been following the post on the VM forum, I'm the "other guy".

I do believe Seph is spot on about having multiple issues. On one hand we are sharing the same dropouts on several occasions indicating an area event.
We share to some extent the same severity of codeword issues - again, potentially attributable to the UBR issue - and possibly related to the above mentioned dropouts.

On the other hand you are experiencing far more severe speed issues, V box issues (although mine isnt a v+ since I cannot yet justify the price), and several additional timeouts which I did not experience.

Looks like this needs to be flanked from both sides!

[Sephiroth]

Originally Posted by speedfreak

hes not my "friend" though he seems a nice chap, who knows our relationship might blossom lol........

.....were apparently last seen riding shergar across lord lucans back garden....hem

Hmmm.

[synner]

Originally Posted by simplepsy

Hi Speedfreak, remember me?
For those who have not been following the post on the VM forum, I'm the "other guy".

I do believe Seph is spot on about having multiple issues. On one hand we are sharing the same dropouts on several occasions indicating an area event.
We share to some extent the same severity of codeword issues - again, potentially attributable to the UBR issue - and possibly related to the above mentioned dropouts.

On the other hand you are experiencing far more severe speed issues, V box issues (although mine isnt a v+ since I cannot yet justify the price), and several additional timeouts which I did not experience.

Looks like this needs to be flanked from both sides!

Hello!

Fellow 50Mb-er here in Preston (PR2 area), UBR 14 (cpc1-pres14-2-0-cust***.pres.cable.virginmedia.com)

Here's my T3's and log since Thursday (last time I cleared it down):

T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 27 0 0 0
T4 Timeouts 1 0 0 0

Power Level
(dBmV) -1.68 -2.01 -2.26 -2.38
RxMER
(dB) 36.17 35.97 36.17 36.61
Correctable
Codewords 1199914841 2000987877 1990644762 1475875394
Uncorrectable
Codewords 276 264 283 275

Thu Feb 25 16:34:13 2010 Thu Feb 25 16:35:05 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 25 16:35:05 2010 Thu Feb 25 16:35:05 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 25 16:43:30 2010 Thu Feb 25 16:43:30 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 25 16:45:32 2010 Thu Feb 25 16:45:32 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 25 16:49:37 2010 Thu Feb 25 16:52:32 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 25 21:42:10 2010 Thu Feb 25 22:35:28 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Thu Feb 25 22:45:27 2010 Thu Feb 25 22:45:27 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 00:59:12 2010 Fri Feb 26 01:36:32 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:26:16 2010 Fri Feb 26 13:27:12 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:27:20 2010 Fri Feb 26 13:27:20 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:27:24 2010 Fri Feb 26 13:27:45 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:28:56 2010 Fri Feb 26 13:28:56 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:29:18 2010 Fri Feb 26 13:29:18 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:30:21 2010 Fri Feb 26 13:30:21 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 13:30:31 2010 Fri Feb 26 15:00:25 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 15:05:57 2010 Fri Feb 26 15:05:57 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 15:07:31 2010 Fri Feb 26 15:07:31 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Fri Feb 26 15:07:31 2010 Sat Feb 27 08:58:36 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 08:58:38 2010 Sat Feb 27 08:59:30 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:00:14 2010 Sat Feb 27 09:00:19 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:00:21 2010 Sat Feb 27 09:00:21 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:00:25 2010 Sat Feb 27 09:00:36 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:00:41 2010 Sat Feb 27 09:02:37 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:03:43 2010 Sat Feb 27 09:03:45 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:04:04 2010 Sat Feb 27 09:09:11 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:09:22 2010 Sat Feb 27 09:09:22 2010 Critical (3) No Ranging Response received - T3 time-out;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;
Sat Feb 27 09:09:26 2010 Sat Feb 27 09:09:26 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=**;CMTS-MAC=**;CM-QOS=1.1;CM-VER=3.0;

Hope that helps anyone in identifying any common themes....?

Bri

[simplepsy]

My events for the 27th match yours - begining with:
Sat Feb 27 08:58:34 2010 Sat Feb 27 08:58:34 2010 Warning (5) TEK Invalid - Invalid Key Sequence Number;CM-MAC=x;CMTS-MAC=x;CM-QOS=1.1;CM-VER=3.0;

Current codewords:
Correctable
Codewords 1622203695 2694956187 2687508951 1990312036

Uncorrectable
Codewords 416 434 1173 1145

(these reset a couple of days ago for some reason.. not sure why)

Also on the same UBR as you.

[speedfreak]

Originally Posted by Sephiroth

Hmmm.

Ive been chuckling about the way you quoted me all day

Im still no further, newsgroup guys are still chasing networks (no reply from networks in over a week) and VM contact is trying to find newsgroup guys to find whats happening with networks Are there any VM network guys on here? Ask your managers to read their emails lol

[speedfreak]

Still no answers from VM and now Ive discovered I cant stream iplayer HD, never tried before. It keeps stuttering then I get a message saying insufficient bandwidth, 3.5mbps required. Seriously, if anyone reading this is planning on getting 50meg, I wouldnt bother. Reported all this at the end of January and still no answers

2nd line have been waiting nearly 2 weeks for a reply from networks, Im going grey with it all

One thing i have noticed is that the more i use my connection, the more t3 timeouts I get

[pip08456]

It may be worth getting back on to the CEO's people (via email so you have a record) and cancelling and requesting you be reimbursed for the charges you have paid as they have been given ample opportunity to solve the problem but have been unable to do so.

Excuses like CEO's rep is trying to find out who in 2nd line is dealing with it and networks etc just do not wash.

[speedfreak]

Originally Posted by pip08456

It may be worth getting back on to the CEO's people (via email so you have a record) and cancelling and requesting you be reimbursed for the charges you have paid as they have been given ample opportunity to solve the problem but have been unable to do so.

Excuses like CEO's rep is trying to find out who in 2nd line is dealing with it and networks etc just do not wash.

well i read i have to wait 8 weeks until i contact otelo so i think theres 2 weeks to go, disappointed though, i just dont need all this playing on the ps3 earlier and i heard "oh no laggy ste is the host", my ps3 profile now says "I hate VM 50Mb". I was with TalkTalK LLU before, 16meg+ sync speed but poor peak time throughput due to a congested exchange but it was still better than this, if it wasnt for the fact I despise the clown of a forum manager on TT's forum Id still be with them. For roughly the same price I had the full sky package (sports and movies), 16meg BB and a phoneline with TT

Day off work tomorrow so I shall be chasing it up,

replies on the newsgroup are now just like this..

>> Hi speedfreak,
>>
>> I am waiting to hear back from a network engineer today regarding
>> this issue. I will post again once I have spoken to them.
>>
>>
>> --
>>
>> Kind Regards
>>
>> Virgin Media Technical Support

Then the next day

Hi speedfreak,

We are still awaiting information from our support teams on the issue you
are having. Once received we will let you know.

Once again sorry for the inconvienience.


--
Kind Regards

VirginMedia Technical Support

Then today, nothing. No news whatsoever. Been replies like this everyday for well over a week, I have no idea if they are even looking into it and running tests because Ive had no feedback. Just people chasing other people The contact at VM has been off for a few days and nobody else from VM has contacted me. Add to that my bill is still wrong (again) and I will no doubt get disconnected (again) before that gets sorted (again).

Id kill for a constant and reliable 8Mb at this moment in time. Ive been extremely patient and laidback about it all but enoughs enough

[speedfreak]

Heard from the CEO guy and things are now moving, hes now dealing with networks and a few other people directly to push things forward, happy days He even sorted out my bill for me

[speedfreak]

well just had networks round, he tested everything. Id had several t3 timeouts just before he came,all through the day but he said he hadnt seen anything when testing at the cab. He cant find any fault, told me t3 timeouts are normal and wont affect anything and that t4 timeouts can be expected. Tried a test modem and the correctables still rapidly climb but no one at VM seems bothered about them. Has anyone got any advice?

As soon as the modem is plugged in i have this many codeword errors and they continually rise, rapidly. Surely this must be an indication of a fault

Power Level
(dBmV) 2.42 2.26 2.45 2.64
RxMER
(dB) 36.39 36.17 36.39 36.84
Correctable
Codewords 10016975 16114857 16095260 12784823
Uncorrectable
Codewords 287 935 275 274


Since 5pm when he left

Power Level
(dBmV) 40.25 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 3 0 0 0
T4 Timeouts 0

[Sephiroth]

Originally Posted by speedfreak

well just had networks round, he tested everything. Id had several t3 timeouts just before he came,all through the day but he said he hadnt seen anything when testing at the cab. He cant find any fault, told me t3 timeouts are normal and wont affect anything and that t4 timeouts can be expected. Tried a test modem and the correctables still rapidly climb but no one at VM seems bothered about them. Has anyone got any advice? .....

I suppose you could:

1/
Copy your current event log to a safe place

2/
Clear it & get your modem stats + event log

3/
Do the downloads from the VM site and note the MBYTES/sec aggregate
Please also note the total number of bytes downloaded in the exercise. Very important.

4/
Get your modem stats + event log

This will tell us at a crude level what's going on during downloads. It depends what we see in the event log as to whether or not you have something to take back to the CEO's office in the face of the engineer's remarks.

We'll also calculate the % of data that is correctably corrupted. Anything above 3% corrupted packets is considered unacceptable in the network world. That would be something else to impress on the suit that's dealing with you.

[speedfreak]

Thanks Seph, Im hoping I wont have to go to all that trouble yet. We have had some progress. Networks have found and fixed an issue! They have said that they have found a fault on one of my neighbours drop cables which was causing noise spikes on the upstream which could also affect others on the same BSR. I cant remember the exact details but it was something along the lines of 3.5MHz and they have filtered out the noise. Its still very early days but from yesterday I havent had a single T3 timeout

Had a manager and a tech round yesterday but they had trouble with my laptop so they are coming back with their own laptop to run some speedtests, only thing is my codewords are still climbing like they were before and speedtests on my ps3 are always between 2Mb and 20Mb wired, its always up and down. I will have to see what they say when they run tests from their laptop.

[pabscars]

Originally Posted by speedfreak

Thanks Seph, Im hoping I wont have to go to all that trouble yet. We have had some progress. Networks have found and fixed an issue! They have said that they have found a fault on one of my neighbours drop cables which was causing noise spikes on the upstream which could also affect others on the same BSR. I cant remember the exact details but it was something along the lines of 3.5MHz and they have filtered out the noise. Its still very early days but from yesterday I havent had a single T3 timeout

Had a manager and a tech round yesterday but they had trouble with my laptop so they are coming back with their own laptop to run some speedtests, only thing is my codewords are still climbing like they were before and speedtests on my ps3 are always between 2Mb and 20Mb wired, its always up and down. I will have to see what they say when they run tests from their laptop.

what server are you using on speedtest.net on your PS3, just out of interest.

Ive noticed recently when using the PS3 to check speed from the above site, it no longer finds all the servers and just shows a couple in the UK.

Previously I used london which seemed to give good results, but its no longer visible.

Coupled to this the speed is now displayed in Kbps not Mbps, with some of the wording in German