Service intermittent All day Driving me mental

[Dono]

For about the last 2 months the service in my area had been horrible at best and non existent at worst i tried phoning virgin only to be told to reset my modem etc. Im in the manchester M14 area and as we all know there has been ongoing CRAP service there for ages.

Im currently on the 50meg connection and it was actually working fine for the last 2 weeks (unbelievebly so) until last night when the interent went down.

I have taken a look at the modem and the sync light turns off when the internet goes down and also there is only 1 downstream channel open at any time. the problem seems to resolve itself for around 90seconds after I reboot the router then it f**** up again. I have tried connecting the modem directly into my PC but that still makes no difference.

As i was composing this message the internet has one down TWICE!!!

It is driving me insane as I need it for work, im just wondering if anybody can tell me what is going on before I switch to BT I am at my wits end with these people.

---------- Post added at 21:49 ---------- Previous post was at 21:48 ----------

Frequency 298750000 N/A N/A N/A
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y N/N/N N/N/N N/N/N
Channel Id 163 N/A N/A N/A
Modulation 256QAM N/A N/A N/A
Symbol Rate
(Msym/sec) 6.952 N/A N/A N/A
Interleave Depth I=12
J=17 N/A N/A N/A
Power Level
(dBmV) 4.86 N/A N/A N/A
RxMER
(dB) 36.17 N/A N/A N/A
Correctable
Codewords 22 N/A N/A N/A
Uncorrectable
Codewords 275 N/A N/A N/A

[Sephiroth]

Can we see the full modem stats please with the event log? Cable Modem MAC address to be edited out.

If there's nothing in the event log, then you're gonna have to call it in for resolution. You'll end up having to do this anyway.

Thanks.

[Peter_]

Call the 50Mb Support team tomorrow after 0800 for a UK agent

50Mb support line number 0800 052 0431

[Dono]

Tue Feb 2 21:57:03 2010
Tue Feb 2 21:57:03 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 21:57:07 2010
Tue Feb 2 21:57:13 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 21:57:13 2010
Tue Feb 2 21:57:13 2010
Warning (5)
B-INIT-RNG Failure - Retries exceeded;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:01:35 2010
Tue Feb 2 22:02:04 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:02:06 2010
Tue Feb 2 22:02:06 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:02:06 2010
Tue Feb 2 22:02:06 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:06:31 2010
Tue Feb 2 22:07:01 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:07:03 2010
Tue Feb 2 22:07:03 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:07:03 2010
Tue Feb 2 22:07:03 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:07:08 2010
Tue Feb 2 22:07:14 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:07:14 2010
Tue Feb 2 22:07:14 2010
Warning (5)
B-INIT-RNG Failure - Retries exceeded;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:11:36 2010
Tue Feb 2 22:12:05 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:12:07 2010
Tue Feb 2 22:12:07 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:12:07 2010
Tue Feb 2 22:12:07 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:12:11 2010
Tue Feb 2 22:12:17 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:12:18 2010
Tue Feb 2 22:12:18 2010
Warning (5)
B-INIT-RNG Failure - Retries exceeded;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:12:29 2010
Tue Feb 2 22:12:29 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:14:02 2010
Tue Feb 2 22:14:02 2010
Warning (5)
TEK Invalid - Invalid Key Sequence Number;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:16:43 2010
Tue Feb 2 22:17:12 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:17:14 2010
Tue Feb 2 22:17:14 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:17:14 2010
Tue Feb 2 22:17:14 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:17:19 2010
Tue Feb 2 22:17:25 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:17:26 2010
Tue Feb 2 22:17:26 2010
Warning (5)
B-INIT-RNG Failure - Retries exceeded;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:17:36 2010
Tue Feb 2 22:22:10 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:22:12 2010
Tue Feb 2 22:22:12 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:22:12 2010
Tue Feb 2 22:22:12 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:22:17 2010
Tue Feb 2 22:22:23 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:22:23 2010
Tue Feb 2 22:22:23 2010
Warning (5)
B-INIT-RNG Failure - Retries exceeded;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:26:43 2010
Tue Feb 2 22:27:11 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:27:13 2010
Tue Feb 2 22:27:13 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:27:13 2010
Tue Feb 2 22:27:13 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:27:19 2010
Tue Feb 2 22:32:18 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:32:20 2010
Tue Feb 2 22:32:20 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:32:20 2010
Tue Feb 2 22:32:20 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:32:26 2010
Tue Feb 2 22:37:10 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:37:12 2010
Tue Feb 2 22:37:12 2010
Critical (3)
Ranging Request Retries exausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:37:12 2010
Tue Feb 2 22:37:12 2010
Critical (3)
Unicast Maintenance Ranging attempted - No response - Retries exhausted;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:37:16 2010
Tue Feb 2 22:37:22 2010
Critical (3)
No Ranging Response received - T3 time-out;CM-;CM-QOS=1.1;CM-VER=3.0;
Tue Feb 2 22:37:23 2010
Tue Feb 2 22:37:23 2010
Warning (5)
B-INIT-RNG Failure - Retries exceeded;CM-;CM-QOS=1.1;CM-VER=3.0;

[Peter_]

Please post your upstream including any T3 and T4 that are there.

[Dono]

US-1 US-2 US-3 US-4
Channel Type 1.0 N/A N/A N/A
Channel ID 7 N/A N/A N/A
Frequency
(Hz) 42800000 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) 2560 N/A N/A N/A
Mini-Slot Size 2 N/A N/A N/A
Power Level
(dBmV) 37.71 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 339 0 0 0
T4 Timeouts 0 0 0 0

---------- Post added at 23:35 ---------- Previous post was at 23:34 ----------

Req
Init Maint
Per Maint
Short Data
Long Data
(1)

(3)

(4)

(5)

(6)

Modulation Type QPSK QPSK QPSK 16QAM 16QAM
Differential Encoding OFF OFF OFF OFF OFF
Preamble Length 64 128 128 144 160
Preamble Value Offset 140 6 6 216 216
FEC Error Correction (T) 0 5 5 5 10
FEC Codeword Information Bytes (k) 16 34 34 78 235
Maximum Burst Size 2 0 0 8 0
Guard Time Size 8 48 48 8 8
Last Codeword Length FIX FIX FIX SHORT SHORT
Scrambler on/off ON ON ON ON ON



I think thats everything it keeps cutting off so it took me a while

[Peter_]

The T3's indicate issues with the modem, probably power fluctuations internally and will require an engineer who will probably replace the modem and check the cabling to the cabinet.

[Sephiroth]

Can you let us know the outcome of the engineer visit for lessons learned purposes? I've got to give Moldova his props since he's directly in the business. I think he's noticed frequency drift from 299000000.

[Ignitionnet]

Originally Posted by Moldova

The T3's indicate issues with the modem, probably power fluctuations internally and will require an engineer who will probably replace the modem and check the cabling to the cabinet.

They do?

http://www.dslreports.com/faq/13055

Upstream SNR causing high error rate and RNG-REQs to fail mebbe.

---------- Post added at 12:06 ---------- Previous post was at 12:03 ----------

Originally Posted by Sephiroth

Can you let us know the outcome of the engineer visit for lessons learned purposes? I've got to give Moldova his props since he's directly in the business. I think he's noticed frequency drift from 299000000.

He's in Manchester, ex-ntl, IRC channel scheme so 1.25MHz offset from 8MHz harmonics. Frequencies ending in 750000 are correct.

[Dono]

Will do the engineer should be coming tomorrow. hopefully this will sort the problem, though im not sure as im in that same M14 area which was having problems since november.

Ill let you know