Jump to content

This is the support site for Andrews & Arnold Ltd, a UK Internet provider. Information on these pages is generally for our customers but may be useful to others, enjoy!

Packet Loss: Difference between revisions

684 bytes removed ,  6 January 2015
m
→‎What is Packet Loss?: clean up, typos fixed: FaceBook → Facebook
m (→‎What is Packet Loss?: clean up, typos fixed: FaceBook → Facebook)
 
(12 intermediate revisions by one other user not shown)
=What is Packet Loss?=
 
FromDerived from the [http://revk.www.me.uk/2014/02/what-is-packet-loss.html Director's Blog]
 
The Internet uses a system of packets to send information. This means that whatever you are doing, whether accessing [[Facebook|FaceBook]], making a Skype call, playing an on-line game, downloading a file or reading an email, the information is broken down in to packets. These are not always the same size, and are typically up to around 1500 bytes (or characters) of data at a time.
 
Each of these packets carries some addressing information, and some data. The fact that packets are used means it is possible to have lots of things happening at once, with bits of one thing in one packet followed by bits of something else in another packet and so on, mixing up multiple things on one Internet connection. This is how it is possible for lots of people to use an Internet connection at once. The addressing data in the packet makes sure the right things go to the right place and are put back together at the far end.
 
==How Does AAISP Monitor Packet Loss==
[[File:Cqm-screen-shot-notes.png|thumb|CQM Graph Information]]
Through our [CQM Graphs].
 
Through our [[CQM Graphs]].
 
AAISP monitor all lines every second and measure loss, latency, usage. More details on the [[CQM Graphs]] page.
 
We can also set up a separate ICMP ping graph to the WAN address, and then therefor compare the results for more information.
 
 
==So packet loss is normal. It is what happens when a link is full.==
 
However, there is another scenario where you can get packet loss, and this is where there is a fault. In the case of a fault you will find some packets are dropped at random. What usually happens is some of the data in the packet is corrupted (changed) by random noise or errors from the fault, and this means that the packet no longer checks out when it gets to the other end. Packets have built in checks to confirm nothing was changed, and if that check fails the packet is dropped.
 
 
==The effect of fault based packet loss depends on the protocol.==
 
This means that even low levels of random packet loss can massively slow down a data transfers.
 
 
 
==Packet loss when a link is otherwise idle is a fault.==
The best measure of loss as a simple percentage is the loss when sending full size packets (1500 bytes) which is what the data transfer protocols (like TCP) use. Even a 1% or 2% of loss of such packets can cause TCP to slow down massively. It does not work like taking away a couple of percent of speed - the data transfers keep slowing down as they keep thinking the line must be full.
 
[[File:CQM-heavyloss.png|Heavy packetloss.]]
[[File:Cqm-loss.png|Packet loss on an idle line is always bad news, even if only 1% (one red dot at the top is 1%).]]
 
Packet loss on an idle line is always bad news...
 
[[File:CQM-lowloss.png|border|An FTTC line with 1-3% loss, considered a fault.]]
 
...even if only 1% (one red dot at the top is 1%)
 
==2% loss is not like 98% working speed!==
 
A simpler, and less intrusive measure of loss, is a simple short LCP echo. LCP echoes are a normal part of most Internet links, and A&A do them every second and record the loss for every line. This is only a few bytes, and so packet loss that is a fraction of a percentage could mean several percent at full packet sizes. This is why it is so important to take even very low levels of LCP echo loss seriously.
 
This is why packet loss needs to be a clear metric of quality and faults and why companies like BT need documented packet loss measures that are considered a fault. For some inexplicable reason such a simple metric is not part of any service level guarantee, and not considered a "fault" by BT!
 
Oddly, buying transit, which means sending and receiving packets from thousands of places all around the world (not just exchanges in the UK) and even laying cables under the ocean, one can get a service level guarantee of ZERO packet loss ever. This shows how seriously transit providers take such things. They even guarantee latency (the time taken to transfer packets). Even more oddly, such services are typically around a 50th of the cost of BTs connectivity to exchanges around the UK where no service level guarantee exists for packet loss. It is a strange world we live in some times isn't it?
 
 
editor
698

edits