High Downstream power?

[Welshchris]

Ive noticed that my downstream power level is getting gradually higher and higher... from Friday last week its risen again from 4.4dBmv to 5.1dBmv.

Thu Nov 12 03:36:51 2009 Thu Nov 12 03:36:51 2009 Information (7)
Downstream sync ok
Thu Nov 12 03:36:51 2009 Thu Nov 12 03:36:51 2009 Information (7)
locked and synced to rescue CMTS...all is well!
Thu Nov 12 03:36:51 2009 Thu Nov 12 03:36:51 2009 Information (7)
Downstream sync ok
Thu Nov 12 03:36:50 2009 Thu Nov 12 03:36:50 2009 Critical (3) SYNC
Timing Synchronization failure - Loss of Sync
Thu Nov 12 03:36:50 2009 Thu Nov 12 03:36:50 2009 Information (7)
Downstream sync failed
Thu Nov 12 03:34:59 2009 Thu Nov 12 03:34:59 2009 Information (7)
The s/w filename specified in the config file is the same as ...
Thu Nov 12 03:34:59 2009 Thu Nov 12 03:34:59 2009 Information (7) A
software upgrade filename was specified in the config file.
Thu Nov 12 03:34:59 2009 Thu Nov 12 03:34:59 2009 Information (7)
Authorized
Thu Nov 12 03:34:58 2009 Thu Nov 12 03:34:58 2009 Information (7)
Registration complete!
Thu Nov 12 03:34:58 2009 Thu Nov 12 03:34:58 2009 Information (7) We
registered with a DOCSIS 1.1 config file!
Thu Nov 12 03:34:58 2009 Thu Nov 12 03:34:58 2009 Information (7)
Received a REG-RSP message from the CMTS...
Thu Nov 12 03:34:58 2009 Thu Nov 12 03:34:58 2009 Information (7)
Sending a REG-REQ to the CMTS...
Thu Nov 12 03:34:58 2009 Thu Nov 12 03:34:58 2009 Information (7)
CableModem SNMP configure complete
Time Not Established Time Not Established Information (7) IP init
completed ok
Time Not Established Time Not Established Information (7) CableModem
TFTP init ok
Time Not Established Time Not Established Error (4) ToD request sent-
No Response received
Time Not Established Time Not Established Information (7) CableModem
DHCP client init ok
Time Not Established Time Not Established Critical (3) DHCP WARNING -
Non-critical field invalid in response.
Time Not Established Time Not Established Information (7) MAP
w/initial maintenance region received
Time Not Established Time Not Established Information (7) Downstream
sync ok
Time Not Established Time Not Established Information (7) MAP
w/initial maintenance region received
Time Not Established Time Not Established Information (7) Beginning
initial ranging...
Time Not Established Time Not Established Information (7) downstream
time sync acquired...
Time Not Established Time Not Established Information (7) Downstream
sync ok
Time Not Established Time Not Established Information (7) starting ds
time sync acquisition...
Time Not Established Time Not Established Information (7) Locked on
the downstream. Waiting for UCDs...
Time Not Established Time Not Established Information (7) Downstream
lock ok
Time Not Established Time Not Established Information (7) Sync Start
Thu Nov 12 03:20:24 2009 Thu Nov 12 03:20:24 2009 Critical (3) No
Ranging Response received - T3 time-out
Thu Nov 12 03:20:24 2009 Thu Nov 12 03:20:24 2009 Critical (3) No
Ranging Response received - T3 time-out
Thu Nov 12 03:20:18 2009 Thu Nov 12 03:20:18 2009 Critical (3) SYNC
Timing Synchronization failure - Failed to acquire QAM/Q...
Thu Nov 12 03:19:22 2009 Thu Nov 12 03:19:22 2009 Critical (3) DHCP
WARNING - Non-critical field invalid in response.


Here is current power levels...
Downstream Lock : Locked
Downstream Channel Id : 106
Downstream Frequency : 315000000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 5.1 dBmV
Downstream SNR : 39.4 dB

Upstream Lock : Locked
Upstream Channel ID : 1
Upstream Frequency : 47400000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 50.0 dBmV
Upstream Mini-Slot Size : 2

[broadbandking]

Are you experiencing a slowdown or any other issues?

[Welshchris]

ive noticed downloads arnt as brilliant as they once were.

[broadbandking]

As I am aware its still with in the thresold try downloading 4 files from gamefiles.blueyonder.co.uk and let us know how the speed is, as you might need a tech but as they are in the thresold they might not send a tech.

[Welshchris]

i posted on the newsgroups and the idiots added it to an outstanding ticket thats been open since august lol...

they didnt even say wheather a tech was needed or not!

[broadbandking]

Have you dowloaded the files so we can see the speed degrading?

[Welshchris]

what happens is they tend to star around 2mb/s and dwindle to around 800k even on gamefiles.

[broadbandking]

In that case you need to ring in and ask whats happening.

[Welshchris]

i have and i get "the power levels are all within exceptable levels" and "if u have any more problems dont hesitate to ring back at a later date".
Put it this way ive seen my downstream power level rise from 0.7dBmv to over 5 dBmv in a few hrs.

[sollp]

i have and i get "the power levels are all within exceptable levels" and "if u have any more problems dont hesitate to ring back at a later date".
Put it this way ive seen my downstream power level rise from 0.7dBmv to over 5 dBmv in a few hrs.

Well +5dB is a little high but if as you say they are fluctuating between the levels you have said then there is an issues somewhere, either within your home or the local network, or the modem it's self?

[Welshchris]

we know theres a BSR issue but thats nothing to do with power levels.

I think an Engineer needs to come out but getting them to come out is something else.

[Welshchris]

Still having downstream issues and its getting worse now...

Whats happening is that when downloading the modem lights start to flicker in a weird way...

The Send light will carry on flickering fast but the downstream light goes off and then flickers say once every 2 seconds, the download then gets gradually slower and slower until it stops or times out and also websites are really sluggish.

Logs show...
Thu Nov 19 23:22:51 2009 Thu Nov 19 23:22:51 2009 Information (7) Downstream sync ok
Thu Nov 19 23:22:51 2009 Thu Nov 19 23:22:51 2009 Information (7) locked and synced to rescue CMTS...all is well!
Thu Nov 19 23:22:51 2009 Thu Nov 19 23:22:51 2009 Information (7) Downstream sync ok
Thu Nov 19 23:22:50 2009 Thu Nov 19 23:22:50 2009 Information (7) Locked on the rescue CMTS ds. try to re-acquire ds sync...
Thu Nov 19 23:22:50 2009 Thu Nov 19 23:22:50 2009 Information (7) Downstream lock ok
Thu Nov 19 23:22:50 2009 Thu Nov 19 23:22:50 2009 Information (7) Downstream lock failed
Thu Nov 19 23:22:50 2009 Thu Nov 19 23:22:50 2009 Critical (3) SYNC Timing Synchronization failure - Failed to acquire QAM/Q...
Thu Nov 19 23:22:38 2009 Thu Nov 19 23:22:38 2009 Information (7) Downstream lock failed
Thu Nov 19 23:22:20 2009 Thu Nov 19 23:22:20 2009 Information (7) Downstream sync ok
Thu Nov 19 23:22:20 2009 Thu Nov 19 23:22:20 2009 Information (7) locked and synced to rescue CMTS...all is well!
Thu Nov 19 23:22:20 2009 Thu Nov 19 23:22:20 2009 Information (7) Downstream sync ok
Thu Nov 19 23:22:20 2009 Thu Nov 19 23:22:20 2009 Information (7) Locked on the rescue CMTS ds. try to re-acquire ds sync...
Thu Nov 19 23:22:20 2009 Thu Nov 19 23:22:20 2009 Information (7) Downstream lock ok
Thu Nov 19 23:22:19 2009 Thu Nov 19 23:22:19 2009 Information (7) Downstream lock failed
Thu Nov 19 23:11:00 2009 Thu Nov 19 23:11:00 2009 Critical (3) Started Unicast Maintenance Ranging - No Response received - ...
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Information (7) Downstream sync ok
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Information (7) locked and synced to rescue CMTS...all is well!
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Information (7) Downstream sync ok
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Information (7) Downstream sync failed
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Information (7) Downstream sync ok
Thu Nov 19 21:56:04 2009 Thu Nov 19 21:56:04 2009 Information (7) locked and synced to rescue CMTS...all is well!
Thu Nov 19 21:56:03 2009 Thu Nov 19 21:56:03 2009 Information (7) Downstream sync ok
Thu Nov 19 21:56:03 2009 Thu Nov 19 21:56:03 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Thu Nov 19 21:56:03 2009 Thu Nov 19 21:56:03 2009 Information (7) Downstream sync failed
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Information (7) Downstream sync ok
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Information (7) locked and synced to rescue CMTS...all is well!
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Information (7) Downstream sync ok
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Critical (3) SYNC Timing Synchronization failure - Loss of Sync
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Information (7) Downstream sync failed
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Information (7) Downstream sync ok
Thu Nov 19 21:17:42 2009 Thu Nov 19 21:17:42 2009 Information (7) locked and synced to rescue CMTS...all is well!


Power Levels are..

Upstream Lock : Locked
Upstream Channel ID : 1
Upstream Frequency : 47400000 Hz
Upstream Modulation : QAM16
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 50.8 dBmV
Upstream Mini-Slot Size : 2


Downstream Lock : Locked
Downstream Channel Id : 138
Downstream Frequency : 315000000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 6952 Ksym/sec
Downstream Interleave Depth : taps12Increment17
Downstream Receive Power Level : 3.9 dBmV
Downstream SNR : 39.3 dB

My downstream fluctuates so rapidly, ive seen it go from 0.7 dBmv to 5.1dBmv in the matter of hrs.

---------- Post added at 23:41 ---------- Previous post was at 23:30 ----------

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Jim>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=17ms TTL=119
Reply from 212.58.224.138: bytes=32 time=19ms TTL=119
Reply from 212.58.224.138: bytes=32 time=18ms TTL=119
Reply from 212.58.224.138: bytes=32 time=17ms TTL=119

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 17ms, Maximum = 19ms, Average = 17ms

C:\Users\Jim>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 190 ms 9 ms 9 ms cwma-cmts-07-lback-20.network.virginmedia.net [8
6.5.128.1]
2 8 ms 12 ms 10 ms swan-core-1a-ge-300-1859.network.virginmedia.net
[213.105.225.37]
3 13 ms 15 ms 603 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.4
3.162.105]
4 17 ms 19 ms 19 ms nth-bb-b-ae2-0.network.virginmedia.net [62.253.1
85.85]
5 21 ms 20 ms 22 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
6 23 ms 20 ms 22 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
7 22 ms 26 ms 23 ms 212.58.238.153
8 17 ms 22 ms 17 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

is it me or does no 3 on the tracert look odd?

[chris26engwales]

Chris dads went off around about 7:10 this evening for about 10 mins with the ready light blinking problem and its been sluggish ever since.

[Sephiroth]

3 13 ms 15 ms 603 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.43.162.105]

This is how I interpret #3.

There are three pings sent to that IP address. Two of them are fine, the third took a lot longer.

Note that the pings further down the line went OK so that whatever ther was happening in Birmingham had passed.

If you did a tracert which showed all three attempts at high ping time, and if this was consistent when tracert was repeated, then you'd have identified a problem.

Anyone disagree?

My flaky memory did twitch when I read "My downstream fluctuates so rapidly, ive seen it go from 0.7 dBmv to 5.1dBmv in the matter of hrs."

I've been following your story and prolly you've had your modem changed by VM. But the twitch was that one person who said the same thing about downstream voltages was diagnosed on this or the other forum as having a line problem. The engineer came, changed the modem and the problem went away.

You should be so lucky.

[chris26engwales]

3 13 ms 15 ms 603 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.43.162.105]

This is how I interpret #3.

There are three pings sent to that IP address. Two of them are fine, the third took a lot longer.

Note that the pings further down the line went OK so that whatever ther was happening in Birmingham had passed.

If you did a tracert which showed all three attempts at high ping time, and if this was consistent when tracert was repeated, then you'd have identified a problem.

Anyone disagree?

My flaky memory did twitch when I read "My downstream fluctuates so rapidly, ive seen it go from 0.7 dBmv to 5.1dBmv in the matter of hrs."

I've been following your story and prolly you've had your modem changed by VM. But the twitch was that one person who said the same thing about downstream voltages was diagnosed on this or the other forum as having a line problem. The engineer came, changed the modem and the problem went away.

You should be so lucky.

Modem has been changed twice since August in an attempt to fix another issue which is still ongoing with the BSR, ive been following it also with chris as dad has the same issue

[Welshchris]

thats correct chris im on my 3rd modem since Second week now in August and they even sent me out a 4th saying that my modem was over a year old after they botched my records up lol

Did these also...

C:\Users\Jim>ping yahoo.co.uk

Pinging yahoo.co.uk [217.146.186.221] with 32 bytes of data:
Reply from 217.146.186.221: bytes=32 time=30ms TTL=55
Reply from 217.146.186.221: bytes=32 time=27ms TTL=55
Reply from 217.146.186.221: bytes=32 time=31ms TTL=55
Reply from 217.146.186.221: bytes=32 time=30ms TTL=55

Ping statistics for 217.146.186.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 31ms, Average = 29ms

C:\Users\Jim>tracert yahoo.co.uk

Tracing route to yahoo.co.uk [217.146.186.221]
over a maximum of 30 hops:

1 52 ms 8 ms 7 ms cwma-cmts-07-lback-20.network.virginmedia.net [8
6.5.128.1]
2 8 ms 11 ms 12 ms swan-core-1a-ge-300-1860.network.virginmedia.net
[213.105.225.41]
3 15 ms 10 ms 13 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.4
3.162.105]
4 20 ms 19 ms 18 ms nth-bb-b-ae2-0.network.virginmedia.net [62.253.1
85.85]
5 22 ms 21 ms 19 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
6 18 ms 20 ms 23 ms 70-14-250-212.static.virginmedia.com [212.250.14
.70]
7 31 ms 31 ms 30 ms so-0-1-0.msr1.ird.yahoo.com [66.196.65.33]
8 31 ms 30 ms 33 ms gi-1-3.bas-a2.ird.yahoo.com [217.146.191.139]
9 28 ms 45 ms 30 ms rc1.vip.ird.yahoo.com [217.146.186.221]

Trace complete.


C:\Users\Jim>ping yahoo.co.uk

Pinging yahoo.co.uk [217.146.186.221] with 32 bytes of data:
Reply from 217.146.186.221: bytes=32 time=31ms TTL=55
Reply from 217.146.186.221: bytes=32 time=28ms TTL=55
Reply from 217.146.186.221: bytes=32 time=31ms TTL=55
Reply from 217.146.186.221: bytes=32 time=30ms TTL=55

Ping statistics for 217.146.186.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 28ms, Maximum = 31ms, Average = 30ms

C:\Users\Jim>tracert yahoo.co.uk

Tracing route to yahoo.co.uk [217.146.186.221]
over a maximum of 30 hops:

1 58 ms 8 ms 8 ms cwma-cmts-07-lback-20.network.virginmedia.net [8
6.5.128.1]
2 8 ms 10 ms 12 ms swan-core-1a-ge-300-1860.network.virginmedia.net
[213.105.225.41]
3 15 ms 10 ms 12 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.4
3.162.105]
4 20 ms 16 ms 20 ms nth-bb-b-ae2-0.network.virginmedia.net [62.253.1
85.85]
5 22 ms 23 ms 19 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
6 18 ms 21 ms 23 ms 70-14-250-212.static.virginmedia.com [212.250.14
.70]
7 31 ms 34 ms 32 ms so-0-1-0.msr1.ird.yahoo.com [66.196.65.33]
8 36 ms 32 ms 33 ms gi-1-3.bas-a2.ird.yahoo.com [217.146.191.139]
9 29 ms 47 ms 30 ms rc1.vip.ird.yahoo.com [217.146.186.221]

Trace complete.

C:\Users\Jim>ping yahoo.co.uk

Pinging yahoo.co.uk [217.146.186.221] with 32 bytes of data:
Reply from 217.146.186.221: bytes=32 time=30ms TTL=55
Reply from 217.146.186.221: bytes=32 time=27ms TTL=55
Reply from 217.146.186.221: bytes=32 time=33ms TTL=55
Reply from 217.146.186.221: bytes=32 time=30ms TTL=55

Ping statistics for 217.146.186.221:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 27ms, Maximum = 33ms, Average = 30ms

C:\Users\Jim>tracert yahoo.co.uk

Tracing route to yahoo.co.uk [217.146.186.221]
over a maximum of 30 hops:

1 55 ms 8 ms 10 ms cwma-cmts-07-lback-20.network.virginmedia.net [8
6.5.128.1]
2 8 ms 11 ms 15 ms swan-core-1a-ge-300-1860.network.virginmedia.net
[213.105.225.41]
3 15 ms 15 ms 13 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.4
3.162.105]
4 22 ms 18 ms 18 ms nth-bb-b-ae2-0.network.virginmedia.net [62.253.1
85.85]
5 26 ms 21 ms 18 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
6 19 ms 30 ms 22 ms 70-14-250-212.static.virginmedia.com [212.250.14
.70]
7 31 ms 31 ms 30 ms so-0-1-0.msr1.ird.yahoo.com [66.196.65.33]
8 31 ms 32 ms 33 ms gi-1-3.bas-a2.ird.yahoo.com [217.146.191.139]
9 31 ms 45 ms 28 ms rc1.vip.ird.yahoo.com [217.146.186.221]

Trace complete.

[Ignitionnet]

3 13 ms 15 ms 603 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.43.162.105]

This is how I interpret #3.

There are three pings sent to that IP address. Two of them are fine, the third took a lot longer.

Note that the pings further down the line went OK so that whatever ther was happening in Birmingham had passed.

If you did a tracert which showed all three attempts at high ping time, and if this was consistent when tracert was repeated, then you'd have identified a problem.

Anyone disagree?

My flaky memory did twitch when I read "My downstream fluctuates so rapidly, ive seen it go from 0.7 dBmv to 5.1dBmv in the matter of hrs."

I've been following your story and prolly you've had your modem changed by VM. But the twitch was that one person who said the same thing about downstream voltages was diagnosed on this or the other forum as having a line problem. The engineer came, changed the modem and the problem went away.

You should be so lucky.

The high ping response on 3rd ping is fine. bir-bb-a is a router, it routes and both gives responding to pings a low priority for its' CPU time and has a rate limit on how many responses per second it will provide. It may have just been refreshing some routing tables for 600ms before it got to responding to the ping.

Variations in voltages are absolutely fine and expected, even variations of a few dBmV over the course of a few hours. If it were a variation like that in a matter of moments sure there are issues but over a few hours is far from impossible. Cable networks are outside, weather changes can cause not insignificant changes to line conditions, this is why DOCSIS networks have such a wide operating range precisely to accomodate things like amplifiers working slightly better at a lower temperature, automatic gain control kicking in, connectors expanding and contracting, etc, etc.

In the UK it's also very noticeable when dealing with blocks of apartments / flats. The temperatures within junction boxes can vary quite considerably depending on whether the heating has clicked on or not, the ambient temperature outside, etc, more than ambient temperatures even.

If you want to see some scary stuff go check out cable networks in places like Canada where 10dBmV shifts in power levels throughout a day are far from impossible :)

Overanalysing is an easy route to pain.

Just had another thought as well - remember that on the overlay network when connected to a BSR customers are load balanced across 4 different downstreams, a shift from the bottom one to the top one could also induce a 2dBmV variation in power levels depending on sloping.

[Welshchris]

but we are talking about a 4dBmv variation sometimes.

[Sephiroth]

overanalysing is an easy route to pain.

just had another thought as well - remember that on the overlay network when connected to a bsr customers are load balanced across 4 different downstreams, a shift from the bottom one to the top one could also induce a 2dbmv variation in power levels depending on sloping.

rotfl!

[Ignitionnet]

rotfl!

Talking of which check your PMs on t'other site, slacker.

But anyway my power levels swing by a range of 2dB or so throughout the course of a day and that's nothing special. Much better indicators of issues on downstream path are correctable / uncorrectable codewords and SNR. Packet loss also nice.

[Welshchris]

when u say throughout the day mine can swing 4dBmv in 1-2hrs lol

[Sephiroth]

Talking of which check your PMs on t'other site, slacker.

But anyway my power levels swing by a range of 2dB or so throughout the course of a day and that's nothing special. Much better indicators of issues on downstream path are correctable / uncorrectable codewords and SNR. Packet loss also nice.

Packet loss doesn't occur on TCP unless the line/circuit/connexion breaks. Or what?

[Ignitionnet]

Packet loss doesn't occur on TCP unless the line/circuit/connexion breaks. Or what?

It happens but is unlikely, however I was thinking more of measuring the drops with ICMP. A few hundred full size pings to the BBC or LINX usually shows issues quite well ( ping -n 100 -l 1460 bbc.co.uk )

[Sephiroth]

It happens but is unlikely, however I was thinking more of measuring the drops with ICMP. A few hundred full size pings to the BBC or LINX usually shows issues quite well ( ping -n 100 -l 1460 bbc.co.uk )
Sure.

[Ignitionnet]

My own power levels are nice and warm at the moment, though all is running as it should be so all is good :)

Power Level (dBmV) 8.04 8.30 8.41 8.75
RxMER (dB) 38.26 38.61 38.98 39.40

[Kev401]

Hi, new to the forum and cable internet, so sorry to jump in. What do you do if the values are 'really' high then; should I be ringing VM and asking for a replacement?

Figures are;
Cable Modem Downstream
Downstream Lock : Locked
Downstream Channel Id : 5
Downstream Frequency : 339000000 Hz
Downstream Modulation : QAM256
Downstream Symbol Rate : 5360.537 Ksym/sec
Downstream Interleave Depth : taps32Increment4
Downstream Receive Power Level : 10.5 dBmV
Downstream SNR : 39.3 dB

Cable Modem Upstream
Upstream Lock : Locked
Upstream Channel ID : 1
Upstream Frequency : 22200000 Hz
Upstream Modulation : QPSK
Upstream Symbol Rate : 2560 Ksym/sec
Upstream transmit Power Level : 43.0 dBmV
Upstream Mini-Slot Size : 2

Cheers for helping a newbie.

[Welshchris]

https://www.cableforum.co.uk/images/local/2009/11/19.png (http://www.speedtest.net)

If my connection gets any slower it will stop!

[Ignitionnet]

Hi, new to the forum and cable internet, so sorry to jump in. What do you do if the values are 'really' high then; should I be ringing VM and asking for a replacement?

So long as all is working as it should be don't worry :)

[Sephiroth]

https://www.cableforum.co.uk/images/local/2009/11/19.png (http://www.speedtest.net)

If my connection gets any slower it will stop!
Eh? There are peops on 50 Mbps contracts with less than 1 Mpbs. I wish I could get 10 Mbps at 19:00!

[Tech_Boy]

:Dhttps://www.cableforum.co.uk/images/local/2009/11/18.png:D (http://www.speedtest.net)

[Welshchris]

Eh? There are peops on 50 Mbps contracts with less than 1 Mpbs. I wish I could get 10 Mbps at 19:00!

it takes approx 12 seconds from the time i click submit reply to the time it shows on the forum.

im getting a max of around 1mb/s downloads until the download fades and times out.

[Sephiroth]

it takes approx 12 seconds from the time i click submit reply to the time it shows on the forum.

im getting a max of around 1mb/s downloads until the download fades and times out.

yeah - but you just posted 10 Mbps and thought you were at a crawl. I wouldn't have dared post that and complain!

[Welshchris]

when i cant even download something because of whatever the issue is i will complain

[Welshchris]

Connection issues again tonight and downloads dropping out..

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Jim>ping bbc.co.uk

Pinging bbc.co.uk [212.58.224.138] with 32 bytes of data:
Reply from 212.58.224.138: bytes=32 time=24ms TTL=119
Request timed out.
Reply from 212.58.224.138: bytes=32 time=156ms TTL=119
Reply from 212.58.224.138: bytes=32 time=272ms TTL=119

Ping statistics for 212.58.224.138:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 24ms, Maximum = 272ms, Average = 150ms

C:\Users\Jim>tracert bbc.co.uk

Tracing route to bbc.co.uk [212.58.224.138]
over a maximum of 30 hops:

1 86 ms 48 ms 52 ms cpc3-cwma7-2-0-gw.7-3.cable.virginmedia.com [82.
16.168.1]
2 100 ms 100 ms 105 ms swan-core-1a-ge-300-1859.network.virginmedia.net
[213.105.225.37]
3 118 ms 117 ms 126 ms bir-bb-a-ge-130-0.network.virginmedia.net [212.4
3.162.105]
4 166 ms 155 ms 202 ms nth-bb-b-ae2-0.network.virginmedia.net [62.253.1
85.85]
5 226 ms 228 ms 249 ms tele-ic-1-as0-0.network.virginmedia.net [62.253.
184.2]
6 165 ms 252 ms 157 ms pos6-1.rt0.thdo.bbc.co.uk [212.58.239.237]
7 258 ms 175 ms 179 ms 212.58.238.129
8 151 ms 165 ms 148 ms virtual-vip.thdo.bbc.co.uk [212.58.224.138]

Trace complete.

---------- Post added at 21:43 ---------- Previous post was at 21:07 ----------

Microsoft Windows [Version 6.0.6002]
Copyright (c) 2006 Microsoft Corporation. All rights reserved.

C:\Users\Jim>ping gamefiles.virginmedia.com

Pinging gamefiles.virginmedia.com [194.117.143.71] with 32 bytes of data:
Reply from 194.117.143.71: bytes=32 time=72ms TTL=58
Reply from 194.117.143.71: bytes=32 time=537ms TTL=58
Reply from 194.117.143.71: bytes=32 time=57ms TTL=58
Reply from 194.117.143.71: bytes=32 time=879ms TTL=58

Ping statistics for 194.117.143.71:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 57ms, Maximum = 879ms, Average = 386ms

C:\Users\Jim>tracert gamefiles.virginmedia.com

Tracing route to gamefiles.virginmedia.com [194.117.143.71]
over a maximum of 30 hops:

1 * * 18 ms cpc3-cwma7-2-0-gw.7-3.cable.virginmedia.com [82.
16.168.1]
2 * 376 ms 7 ms swan-core-1a-ge-300-1860.network.virginmedia.net
[213.105.225.41]
3 605 ms 13 ms * bir-bb-a-ge-130-0.network.virginmedia.net [212.4
3.162.105]
4 * 131 ms 13 ms man-bb-b-so-510-0.network.virginmedia.net [62.25
3.185.134]
5 741 ms 14 ms 15 ms know-dcore-1b-tenge100.network.virginmedia.net [
212.43.162.54]
6 581 ms 23 ms 22 ms mirror3.mirrors.virginm.net [194.117.143.71]

Trace complete.