12,270
edits
Slow FTTP: Difference between revisions
m
→Single thread Vs multi thread performance problems
| (7 intermediate revisions by the same user not shown) | |||
|
Here is some steps to take if you have problems with your FTTP service.
== I may have packetloss ==▼
Packetloss can be seen in a number of ways, check the following to see if the location can be narrowed down to something specific:▼
#Ping your router's LAN IP - this will be the 'default gateway' your computers use - eg, could be something like 192.168.1.1 - if you have loss pinging your local router, check with a wired connection direct in to the router...▼
#Check the CQM Graphs on the A&A Control pages▼
#Ping the A&A endpoint IP: <SyntaxHighlight inline> ping 81.187.81.187</SyntaxHighlight>▼
#ping somewhere on the internet, eg <SyntaxHighlight inline> ping 8.8.8.8</SyntaxHighlight> and <SyntaxHighlight inline> ping bbc.co.uk</SyntaxHighlight>▼
Get in touch with us about what you find.▼
[[File:FTTP-loss.png|frame|none|Packet loss]]▼
== I have a slow FTTP connection ==
# Try a different computer/device
# Try a '''power cycle''' of the Openreach/CityFibre ONT
#Check for '''packet loss''' - see below.
# ...'''get in touch'''.
*# Our Control Page will allow you to run an 'End to End' test, this may if Openreach's systems detect a fault, in which case, do get in touch. eg: <tt>GTC_FTTP_SERVICE_1005 Possible fault in the Openreach network.</tt>
== Single thread Vs multi thread performance problems ==
Sometimes a speed problem occurs for single-thread transfers, whist multi-thread transfers are OK. Broadly speaking, single thread Vs multi-thread speeds should be very similar, and near the top end of the speed of your circuit.
These can be tricky to diagnose and fix, as sometimes the problem is down to congestion in the back-haul network.
As well as testing the usual things (Different computer/router/directly-wired etc) to help diagnose, we suggest using iperf3 rather than http based speed tests as iperf3 is usually more reliable.
Support staff can give access to our own iperf server, and then you can run tests such as:
Single thread transfer from us to you (testing your download)
iperf3 -R -c <speedtest server>
10-thread transfer from us to you (testing your download)
iperf3 -R -P 10 -c <speedtest server>
Single thread transfer from you to us (testing your upload)
iperf3 -c <speedtest server>
10-thread transfer from you to us (testing your upload)
iperf3 -P 10 -c <speedtest server>
Running these at different times of day will give a picture as to whether single-thread is a problem, and if it's a problem due to the time of the day.
▲Packetloss can be seen in a number of ways, check the following to see if the location can be narrowed down to something specific:
▲#Ping your router's LAN IP - this will be the 'default gateway' your computers use - eg, could be something like 192.168.1.1 - if you have loss pinging your local router, check with a wired connection direct in to the router...
▲#Check the CQM Graphs on the A&A Control pages
▲#Ping the A&A endpoint IP: <SyntaxHighlight inline> ping 81.187.81.187</SyntaxHighlight>
▲#ping somewhere on the internet, eg <SyntaxHighlight inline> ping 8.8.8.8</SyntaxHighlight> and <SyntaxHighlight inline> ping bbc.co.uk</SyntaxHighlight>
▲Get in touch with us about what you find.
'''Wrongly configured OLT'''
Packet loss with an odd pattern like this was seen after a CityFibre OLT was upgraded in March 2023 and apparently have some wrong configuration and caused around 5% loss:
[[File:FTTP-misconfig-olt.png|frame|none|Loss caused by a missconfigured CityFibre OLT after being having a firmware upgrade]]
==Slow CityFibre since migrating==
| |||