50M Unpredictable Connection :(

Trooper · 09-01-2012, 17:06

Posted this on virgins own support forum and not heard anything back yet(even though its only been a couple of days).
Heres a link to the problem that i posted so u can get to grips with it: http://community.virginmedia.com/t5/...uts/m-p/950031

Just been totally unpredictable when it drops i know my power levels are ok using the guide on the site.
Ive tried connecting directly to the modem to no avail.
Looked at all connections even outside aswell and there all fine and not loose.
Puzzled at what it could be.

Also looked today on the log and got this
Mon Jan 9 06:24:56 2012 Mon Jan 9 06:24:56 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 06:25:02 2012 Mon Jan 9 06:25:02 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f0:ed:66;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 9 06:30:57 2012 Mon Jan 9 06:31:26 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 06:31:28 2012 Mon Jan 9 06:31:28 2012 Critical (3) Ranging Request Retries exhausted
Mon Jan 9 06:31:28 2012 Mon Jan 9 06:31:28 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Mon Jan 9 06:31:42 2012 Mon Jan 9 06:32:32 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 06:32:40 2012 Mon Jan 9 06:32:40 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f0:ed:66;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 9 06:32:41 2012 Mon Jan 9 06:57:02 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 06:57:04 2012 Mon Jan 9 06:57:04 2012 Critical (3) Ranging Request Retries exhausted
Mon Jan 9 06:57:04 2012 Mon Jan 9 06:57:04 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Mon Jan 9 06:57:20 2012 Mon Jan 9 06:57:20 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 06:57:30 2012 Mon Jan 9 06:57:30 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f0:ed:66;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 9 07:04:04 2012 Mon Jan 9 08:30:10 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 08:30:12 2012 Mon Jan 9 08:30:12 2012 Critical (3) Ranging Request Retries exhausted
Mon Jan 9 08:30:12 2012 Mon Jan 9 08:30:12 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Mon Jan 9 08:30:25 2012 Mon Jan 9 08:31:01 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 08:31:14 2012 Mon Jan 9 08:31:14 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f0:ed:66;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 9 08:31:15 2012 Mon Jan 9 09:05:53 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 09:05:55 2012 Mon Jan 9 09:05:55 2012 Critical (3) Ranging Request Retries exhausted
Mon Jan 9 09:05:55 2012 Mon Jan 9 09:05:55 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Mon Jan 9 09:06:10 2012 Mon Jan 9 09:07:12 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 09:07:18 2012 Mon Jan 9 09:07:18 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f0:ed:66;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 9 09:07:19 2012 Mon Jan 9 14:27:35 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:27:37 2012 Mon Jan 9 14:27:37 2012 Critical (3) Ranging Request Retries exhausted
Mon Jan 9 14:27:37 2012 Mon Jan 9 14:27:37 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Mon Jan 9 14:27:51 2012 Mon Jan 9 14:29:02 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:29:05 2012 Mon Jan 9 14:29:05 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded
Mon Jan 9 14:29:06 2012 Mon Jan 9 14:30:29 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:30:35 2012 Mon Jan 9 14:30:35 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded
Mon Jan 9 14:30:35 2012 Mon Jan 9 14:31:43 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:31:49 2012 Mon Jan 9 14:31:49 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded
Mon Jan 9 14:31:50 2012 Mon Jan 9 14:33:01 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:33:07 2012 Mon Jan 9 14:33:07 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded
Mon Jan 9 14:33:16 2012 Mon Jan 9 14:34:58 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:34:59 2012 Mon Jan 9 14:34:59 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded
Mon Jan 9 14:35:01 2012 Mon Jan 9 14:36:32 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:36:39 2012 Mon Jan 9 14:36:39 2012 Warning (5) B-INIT-RNG Failure - Retries exceeded
Mon Jan 9 14:36:40 2012 Mon Jan 9 14:37:55 2012 Critical (3) No Ranging Response received - T3 time-out
Mon Jan 9 14:38:05 2012 Mon Jan 9 14:38:05 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=00:22:68:f0:ed:66;CMTS-MAC=xx:xx:xx:xx:xx:xx;CM-QOS=1.1;CM-VER=3.0;
Mon Jan 9 14:42:44 2012 Mon Jan 9 14:42:46 2012 Critical (3) No Ranging Response received - T3 time-out

Any help would be appreciated
Cheers

Admin Edit (Stuart): Not usually a good idea to leave MAC addressess in the public areas of the forum. I have removed them.

thenry · 09-01-2012, 17:13

you've posted your up stats, could you post your down stats too please.

also...

https://my.virginmedia.com/faults/service-status

have you called support 150/151 ?

Trooper · 09-01-2012, 17:22

Heres my downstream stats ATM:
Cable Modem Downstream

DS-1 DS-2 DS-3 DS-4
Frequency 299000000 307000000 315000000 323000000
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y Y/Y/Y
Channel Id 113 114 115 116
Modulation 256QAM 256QAM 256QAM 256QAM
Symbol Rate
(Msym/sec) 6.952 6.952 6.952 6.952
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17
Power Level
(dBmV) 3.10 2.83 2.93 2.71
RxMER
(dB) 35.97 35.25 35.42 34.93
Correctable
Codewords 102 662 589 2086
Uncorrectable
Codewords 307 289 283 273
I have rung support but kept getting an automated message saying there was a problem.(Was a week ago)
Website is reporting a problem but says fix date was Xmas Day (25/12/2011)
F001838845 << Ticket No.

Will try support again today or tommorow.

Peter_ · 09-01-2012, 17:44

Ring in on 0800 052 0431 which is the 50Mb support line.

Trooper · 13-01-2012, 23:06

Thanks masque and ye i tried both numbers and they said today (Friday) and it was all good until 1030pm tonight when it came back again.
They said "we have a noise issue and is affecting around 600 users" thats what they said to me.
But starting to get a bit peed off really with the whole thing.
Just wondered if i need a new modem even though ive heard terrible things about the so called Superhub.
Currently have a VMG300 which has been rock solid for a year until i started getting t3 timeouts.

Heres the logs to see if anythings up but i dont personally think my end is at the wrong here looking at the guides on the site.

Heres the logs:
Cable Modem Upstream
US-1 US-2 US-3 US-4
Channel Type 2.0 N/A N/A N/A
Channel ID 4 N/A N/A N/A
Frequency
(Hz) 35800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation 16QAM N/A N/A N/A
Symbol Rate
(KSym/sec) 5120 N/A N/A N/A
Mini-Slot Size 4 N/A N/A N/A
Power Level
(dBmV) 45.00 N/A N/A N/A
T1 Timeouts 0 0 0 0
T2 Timeouts 0 0 0 0
T3 Timeouts 380 0 0 0
T4 Timeouts 1 0 0 0

able Modem Event Log
First Time Last Time Priority Description
Thu Jan 12 19:42:17 2012 Thu Jan 12 19:42:17 2012 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 2
Thu Jan 12 19:42:19 2012 Thu Jan 12 19:42:56 2012 Critical (3) No Ranging Response received - T3 time-out
Thu Jan 12 19:43:01 2012 Thu Jan 12 19:43:01 2012 Critical (3) Ranging Request Retries exhausted
Thu Jan 12 19:43:01 2012 Thu Jan 12 19:43:01 2012 Critical (3) 16 consecutive T3 timeouts while trying to range on upstream channel 1
Thu Jan 12 19:43:11 2012 Thu Jan 12 19:43:11 2012 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 19:43:11 2012 Thu Jan 12 19:43:11 2012 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 19:43:25 2012 Thu Jan 12 19:43:31 2012 Critical (3) No Ranging Response received - T3 time-out
Thu Jan 12 19:45:38 2012 Thu Jan 12 19:45:38 2012 Critical (3) DHCP FAILED - Discover sent, no offer received;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 19:45:52 2012 Thu Jan 12 19:45:52 2012 Warning (5) Lost MDD Timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 19:45:52 2012 Thu Jan 12 19:45:52 2012 Warning (5) MDD message timeout;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 19:46:05 2012 Thu Jan 12 19:46:05 2012 Critical (3) No Ranging Response received - T3 time-out
Thu Jan 12 19:46:10 2012 Thu Jan 12 19:46:28 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 21:31:46 2012 Thu Jan 12 21:41:22 2012 Critical (3) No Ranging Response received - T3 time-out
Thu Jan 12 21:41:24 2012 Thu Jan 12 21:41:24 2012 Critical (3) Ranging Request Retries exhausted
Thu Jan 12 21:41:24 2012 Thu Jan 12 21:41:24 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Thu Jan 12 21:41:43 2012 Thu Jan 12 21:41:43 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 22:16:16 2012 Thu Jan 12 22:16:44 2012 Critical (3) No Ranging Response received - T3 time-out
Thu Jan 12 22:16:46 2012 Thu Jan 12 22:16:46 2012 Critical (3) Ranging Request Retries exhausted
Thu Jan 12 22:16:46 2012 Thu Jan 12 22:16:46 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Thu Jan 12 22:17:30 2012 Thu Jan 12 22:17:52 2012 Critical (3) No Ranging Response received - T3 time-out
Thu Jan 12 22:17:57 2012 Thu Jan 12 22:17:57 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Thu Jan 12 22:42:19 2012 Fri Jan 13 05:37:52 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Jan 13 05:37:54 2012 Fri Jan 13 05:37:54 2012 Critical (3) Ranging Request Retries exhausted
Fri Jan 13 05:37:54 2012 Fri Jan 13 05:37:54 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Fri Jan 13 05:38:09 2012 Fri Jan 13 05:39:24 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Jan 13 05:39:34 2012 Fri Jan 13 05:39:34 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 13 05:39:35 2012 Fri Jan 13 22:06:12 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Jan 13 22:06:14 2012 Fri Jan 13 22:06:14 2012 Critical (3) Ranging Request Retries exhausted
Fri Jan 13 22:06:14 2012 Fri Jan 13 22:06:14 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Fri Jan 13 22:06:30 2012 Fri Jan 13 22:06:30 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 13 22:13:46 2012 Fri Jan 13 22:14:15 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Jan 13 22:14:17 2012 Fri Jan 13 22:14:17 2012 Critical (3) Ranging Request Retries exhausted
Fri Jan 13 22:14:17 2012 Fri Jan 13 22:14:17 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Fri Jan 13 22:14:36 2012 Fri Jan 13 22:14:36 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 13 22:35:20 2012 Fri Jan 13 22:35:48 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Jan 13 22:35:50 2012 Fri Jan 13 22:35:50 2012 Critical (3) Ranging Request Retries exhausted
Fri Jan 13 22:35:50 2012 Fri Jan 13 22:35:50 2012 Critical (3) Unicast Maintenance Ranging attempted - No response - Retries exhausted
Fri Jan 13 22:36:05 2012 Fri Jan 13 22:36:18 2012 Critical (3) No Ranging Response received - T3 time-out
Fri Jan 13 22:36:24 2012 Fri Jan 13 22:36:24 2012 Warning (5) MIMO Event MIMO: Stored MIMO=0 post cfg file MIMO=-1;CM-MAC=**:**:**:**:**:**;CMTS-MAC=**:**:**:**:**:**;CM-QOS=1.1;CM-VER=3.0;
Fri Jan 13 22:36:25 2012 Fri Jan 13 22:36:25 2012 Critical (3) No Ranging Response received - T3 time-out

Heres the download stats:

Cable Modem Downstream

DS-1 DS-2 DS-3 DS-4
Frequency 299000000 307000000 315000000 323000000
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y Y/Y/Y
Channel Id 129 130 131 132
Modulation 256QAM 256QAM 256QAM 256QAM
Symbol Rate
(Msym/sec) 6.952 6.952 6.952 6.952
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 I=12
J=17
Power Level
(dBmV) 4.84 4.38 4.41 4.24
RxMER
(dB) 35.97 35.42 35.42 34.93
Correctable
Codewords 1 27 23 79
Uncorrectable
Codewords 269 295 274 297

Any help would be appreciated thanks

Nedkelly · 13-01-2012, 23:12

Noise is a pain on the network to find as sometimes its there and other times its not .It can be a bit of VM kit in the street playing up or someone putting noise on the network with a faulty psu or some DIY connection they have done .Lets hope they can find it