Can you check my power levels?

[name123]

Thank you

[name123]

More packet loss yet again.

http://i.imgur.com/vCIMc.png

[Benjamin_T]

Hi name123,

There is currently an open fault ticket for this issue. There is a low SNR(noise on the line) issue which is affecting your cable.

The fault reference for this issue is F002110975 and has an estimated fix date of 13-08-2012.

The majority of the work appears to have been completed but further tests will also be completed.

[name123]

Thanks for the response.

Whatever work has been completed thus far does not appear to have fixed the issue, and may even have made it worse because todays packet loss was very bad

http://i.imgur.com/rYYqw.png

[name123]

Some more packet loss today, relatively minor compared to the other incidents but posting for reference.

http://i.imgur.com/hattg.png

Is the "ubr utilisation" a lot, could that be causing it?

[name123]

More packet loss

http://i.imgur.com/oBhR8.png

[name123]

Problem perhaps identified, "glfd-bb-1b-as1-0.network.virginmedia.net" seems to be failing horribly;

Pinging glfd-bb-1b-as1-0.network.virginmedia.net [212.43.163.105] with 32 bytes of data:
Reply from 81.96.224.138: Destination host unreachable.
Reply from 81.96.224.138: Destination host unreachable.
Reply from 81.96.224.138: Destination host unreachable.
Request timed out.

Ping statistics for 212.43.163.105:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),

In addition, one only has to do a google search for "glfd-bb-1b-as1-0.network.virginmedia.net" to see multiple similar problems being reported all over the forum in regards to ping, jitter, packet loss, latency, and all from around the same time frame as I have started experiencing problems.

http://i.imgur.com/WM4zt.png

Now, how do I go about reporting this?

[name123]

I've just completed a ping result of every hop within Virgin Medias network along the route to bbc.co.uk and they all return good results except for "glfd-bb-1b-as1-0.network.virginmedia.net"

Pinging croy-core-1a-ge137.network.virginmedia.net [81.96.224.86] with 32 bytes of data:
Reply from 81.96.224.86: bytes=32 time=41ms TTL=254
Reply from 81.96.224.86: bytes=32 time=4ms TTL=254
Reply from 81.96.224.86: bytes=32 time=8ms TTL=254
Reply from 81.96.224.86: bytes=32 time=7ms TTL=254

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


Pinging croy-core-2a-ae2-0.network.virginmedia.net [195.182.178.82] with 32 bytes of data:
Reply from 195.182.178.82: bytes=32 time=6ms TTL=62
Reply from 195.182.178.82: bytes=32 time=40ms TTL=62
Reply from 195.182.178.82: bytes=32 time=8ms TTL=62
Reply from 195.182.178.82: bytes=32 time=5ms TTL=62

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


Pinging brnt-bb-1a-ae9-0.network.virginmedia.net [81.96.226.1] with 32 bytes of data:
Reply from 81.96.226.1: bytes=32 time=17ms TTL=61
Reply from 81.96.226.1: bytes=32 time=41ms TTL=61
Reply from 81.96.226.1: bytes=32 time=9ms TTL=61
Reply from 81.96.226.1: bytes=32 time=11ms TTL=61

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


Pinging glfd-bb-1b-as1-0.network.virginmedia.net [212.43.163.105] with 32 bytes of data:
Reply from 81.96.224.138: Destination host unreachable.
Reply from 81.96.224.138: Destination host unreachable.
Request timed out.
Reply from 81.96.224.138: Destination host unreachable.

Ping statistics for 212.43.163.105:
    Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),


Pinging glfd-tmr-1-ae5-0.network.virginmedia.net [213.105.159.46] with 32 bytes of data:
Reply from 213.105.159.46: bytes=32 time=7ms TTL=59
Reply from 213.105.159.46: bytes=32 time=9ms TTL=59
Reply from 213.105.159.46: bytes=32 time=60ms TTL=59
Reply from 213.105.159.46: bytes=32 time=9ms TTL=59

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


Pinging tcl5-ic-1-as0-0.network.virginmedia.net [62.253.185.78] with 32 bytes of data:
Reply from 62.253.185.78: bytes=32 time=11ms TTL=58
Reply from 62.253.185.78: bytes=32 time=8ms TTL=58
Reply from 62.253.185.78: bytes=32 time=12ms TTL=58
Reply from 62.253.185.78: bytes=32 time=9ms TTL=58

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

[name123]

Spoken to a fantastically helpful person who has confirmed that "glfd-bb-1b-as1-0.network.virginmedia.net" is the culprit. It apparently has a "cardie score" of 32%, with spikes up to 70%

I imagine all the issues in that google search image I posted above are due to this as well, but it has now been raised with the network team so hopefully these issues will be fixed soon.

I'll continue to post updates

[name123]

Hi, I was told that the issue would show up on the fault status page with a reference number by midday today, however the page is still saying "good service". Can any staff confirm if this fault has actually been logged and is being worked on, and give me the fault reference number?

Also, these SNR disruptions shown in my graphs and confirmed by the network team, where exactly are they happening on the network? Is it happening at "glfd-bb-1b-as1-0.network.virginmedia.net" or somewhere else, because the more I look into this the more I feel that "glfd-bb-1b-as1-0.network.virginmedia.net" is a different unrelated issue to my packet loss SNR faults. There was talk of the issue being located in the street cabinet, but after I brought up "glfd-bb-1b-as1-0.network.virginmedia.net" they canceled the scheduled engineer visit which I am starting to think might have been a mistake.