clean up, typos fixed: ie, → i.e.,, etc) → etc.), eg → e.g. , 250Kb/s → 250Kbit/s, 250Kbit/s → 250kbit/s
===A note on Tx/Rx download/upload===
As stated in the image above, the dark red is customer uploading, and the darker green is customer downloading. The key on th right does label these as Red=rx Green=tx. As the graph is created at the AAISP side, the Tx/Rx is in relation to AAISP,
ie, Red is Rx, what AAISP has received from the customer.
The colours may vary and we even allow users to configure colours individually (useful for people with colour blindness, etc). It is also possible for us to show graphs with only some of the fields which can make some information clearer.
|Purple on the graph is off line, and this can be short blips if a line loses sync or longer. Notes (pins) are often added to graphs to explain why a line is off line if we know, especially when we are investigating a fault. The notes on this graph told when the BT engineer arrived and left.
|'''Regular drops repeating every day'''
eg Central Heating causing drops. [http://wiki.aa.org.uk/File:Cqm-heating.png View a week of these graphs] Here there is interference as the central heating goes on, the drops are regular - twice a day, at the time the heating goes on. This actually highlighted a fault in the central heating for this customer as the graphs showed no drops for 2 days running!
===I pay for usage - what is this monitoring costing me?===
The usage based tariffs are metered based on IP traffic. They do not include LCP traffic at all, so these LCP echos are not costing you anything. They do use some of your bandwidth. One ATM cell (53 bytes) is sent each second. On an 8M line this is 0.005% of your downlink bandwidth. Even with limited uplink such as
250Kb/s, only a tiny fraction of a percent of the bandwidth is used for the monitoring.
===I have a firewall - will this stop the graphs working?===