Just had 50mb installed...

maz2390 · 08-02-2010, 17:44

Hi all,

I've just had 50mb installed this morning but my speeds are all over the place. I've done 12 speed tests and it's ranging from 6.88Mb/s to 51.22Mb/s

Is this normal for it to happen on the first few days and then it will eventually settle or is something wrong?

Any help you can provide would be great

broadbandking · 08-02-2010, 18:06

No it should have to settle, you need to ring and find out what the problem is.

Can you post your modem config first please 192.168.100.1, we need the downstream and upstream power levels

maz2390 · 08-02-2010, 18:16

Downstream:

Quote:

Frequency 299000000 307000000 315000000 N/A
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y N/N/N
Channel Id 27 28 29 N/A
Modulation 64QAM 64QAM 64QAM N/A
Symbol Rate
(Msym/sec) 6.952 6.952 6.952 N/A
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 N/A
Power Level
(dBmV) -2.87 -2.96 -3.39 N/A
RxMER
(dB) 30.96 30.71 30.77 N/A
Correctable
Codewords 1 1 560 N/A
Uncorrectable
Codewords 236 236 1140 N/A

Upstream:

Quote:

Channel Type 1.0 N/A N/A N/A
Channel ID 3 N/A N/A N/A
Frequency
(Hz) 45800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation QPSK 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) 39.00 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 1 0 0 0
T4 Timeouts 0 0 0 0

broadbandking · 08-02-2010, 18:19

Your power levels seem fine, have you tested the speed with the modem just connected.

pip08456 · 08-02-2010, 18:20

I'm no expert (far from it) but I'd be wondering about the number of uncorrectable codewords

maz2390 · 08-02-2010, 18:25

I've also got my event log here if it helps? (I've change the MAC)

Sorry that it's a bit messy, I have no idea how to get it to line up correctly :-/

It's also the same when connected directly.

Quote:

First Time

Last Time

Priority

Description

Tue Nov 24 03:22:33 2009

Tue Nov 24 03:22:33 2009

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:22:33 2009

Tue Nov 24 03:22:33 2009

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:23:04 2009

Tue Nov 24 03:23:04 2009

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:23:04 2009

Tue Nov 24 03:23:04 2009

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:53:09 2009

Tue Nov 24 03:53:09 2009

Critical (3)

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Tue Nov 24 03:53:39 2009

Tue Nov 24 03:53:39 2009

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

Tue Nov 24 03:53:54 2009

Tue Nov 24 03:53:54 2009

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:53:54 2009

Tue Nov 24 03:53:54 2009

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:54:07 2009

Tue Nov 24 03:54:07 2009

Critical (3)

No Ranging Response received - T3 time-out

Tue Nov 24 03:56:29 2009

Tue Nov 24 03:56:29 2009

Critical (3)

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Tue Nov 24 03:56:51 2009

Tue Nov 24 03:56:51 2009

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

Tue Nov 24 03:57:06 2009

Tue Nov 24 03:57:06 2009

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:57:06 2009

Tue Nov 24 03:57:06 2009

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:57:20 2009

Tue Nov 24 03:57:20 2009

Critical (3)

No Ranging Response received - T3 time-out

Tue Nov 24 03:57:38 2009

Tue Nov 24 03:57:38 2009

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:57:38 2009

Tue Nov 24 03:57:38 2009

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:58:49 2009

Tue Nov 24 03:58:49 2009

Critical (3)

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Tue Nov 24 03:59:05 2009

Tue Nov 24 03:59:05 2009

Critical (3)

Received Response to Broadcast Maintenance Request, But no Unicast Maintenance opportunities received - T4 time out

Tue Nov 24 03:59:21 2009

Tue Nov 24 03:59:21 2009

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 03:59:21 2009

Tue Nov 24 03:59:21 2009

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Tue Nov 24 04:09:10 2009

Tue Nov 24 04:09:10 2009

Critical (3)

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Time Not Established

Warning (5)

Lost MDD Timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Time Not Established

Time Not Established

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Time Not Established

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out

Time Not Established

Time Not Established

Critical (3)

Ranging Request Retries exhausted

Time Not Established

Time Not Established

Critical (3)

16 consecutive T3 timeouts while trying to range on upstream channel

Time Not Established

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out

Tue Nov 24 12:47:03 2009

Tue Nov 24 12:47:03 2009

Critical (3)

SYNC Timing Synchronization failure - Loss of Sync;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.0;CM-VER=3.0;

Time Not Established

Time Not Established

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:38:35 2010

Mon Feb 8 08:38:35 2010

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:38:47 2010

Mon Feb 8 08:38:49 2010

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:38:56 2010

Mon Feb 8 08:38:56 2010

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:38:59 2010

Mon Feb 8 08:38:59 2010

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:39:08 2010

Mon Feb 8 08:39:08 2010

Notice (6)

SW Download INIT - Via Config file xv9873254k;fg87dsfd

Mon Feb 8 08:39:57 2010

Mon Feb 8 08:39:57 2010

Notice (6)

SW download Successful - Via Config file

Time Not Established

Time Not Established

Warning (5)

MDD message timeout;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:48:51 2010

Mon Feb 8 08:49:27 2010

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 08:49:29 2010

Mon Feb 8 08:49:29 2010

Warning (5)

B-INIT-RNG Failure - Retries exceeded;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 09:30:48 2010

Mon Feb 8 09:30:48 2010

Error (4)

DHCP RENEW sent - No response for IPv;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Mon Feb 8 18:12:45 2010

Mon Feb 8 18:12:45 2010

Critical (3)

No Ranging Response received - T3 time-out;CM-MAC=00:00:00:00:00:00;CMTS-MAC=00:00:00:00:00:00;CM-QOS=1.1;CM-VER=3.0;

Sephiroth · 08-02-2010, 18:29

I know that the power levels are theoretically fine.

I know that the SNR is within margins for 64QAM modulation - BUT ....

1/
I don't like only 30 dB SNR. It's poor although if you're right at the end of a trunk then there may be little that can be done about it - perhaps the nearest amplifier could be looked at.

2/
It is fairly clear that DS3, which has the poorest power level has the highest number of uncorrected codewords. This is not good.

So something is wrong IMO and it needs proper attention. The one caveat to my remarks would be to look at the stats again ajnd see if anything's changed.

Post the stats here again plus your event log (MINUS YOUR CM-MAC ADDRESS).

maz2390 · 08-02-2010, 18:33

I've got the event log above... or did you want that again?

Here's the other stats:

Downstream:

Quote:

Frequency 299000000 307000000 315000000 N/A
Lock Status
(QAM Lock/FEC Sync/MPEG Lock) Y/Y/Y Y/Y/Y Y/Y/Y N/N/N
Channel Id 27 28 29 N/A
Modulation 64QAM 64QAM 64QAM N/A
Symbol Rate
(Msym/sec) 6.952 6.952 6.952 N/A
Interleave Depth I=12
J=17 I=12
J=17 I=12
J=17 N/A
Power Level
(dBmV) -2.56 -2.69 -3.08 N/A
RxMER
(dB) 30.96 30.77 30.89 N/A
Correctable
Codewords 1 1 560 N/A
Uncorrectable
Codewords 236 236 1140 N/A

Upstream

Quote:

Channel Type 1.0 N/A N/A N/A
Channel ID 3 N/A N/A N/A
Frequency
(Hz) 45800000 N/A N/A N/A
Ranging Status Success N/A N/A N/A
Modulation QPSK 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) 39.00 N/A N/A N/A
T1 Timeouts 0
T2 Timeouts 0 0 0 0
T3 Timeouts 1 0 0 0
T4 Timeouts 0 0 0 0

Sephiroth · 08-02-2010, 19:11

The codewords haven't worsened. If there was a serious problem, they'd be shooting upward. So Broadbandking may have had a point about letting it settle.

Toto · 08-02-2010, 19:15

Speedtest.net varies, here's three back to back.

And....

Thought I'd chuck in a Dublin server for good measure....

They don't prove a great deal, as a consistent download over a period of time is more reliable really.

pip08456 · 08-02-2010, 19:33

I seem to remember a post in another thread stating that for 50Mb users the London server for speedtest was the reliable one as not all could handle the speed.

Bman · 08-02-2010, 19:39

Yep. Speedtest reccomends I use Birmingham but it rarely goes higher than 30-35. London shows 50Mb all day every day.

Toto · 08-02-2010, 19:40

I've had 50Mb regularly on the B'ham server, but not tonight.