As global digitalisation increases, more and more enterprises worldwide are turning to emerging tech... Read the full story
2019-03-13 07:45 PM
I have spent an unsucessful hour ont he phone attempting to garner support for packet loss issues.
This needs to be traced and debugged by a network engineer.
I am attempting to transfer data between two sites (geographically close, but on optus and iinet connections).
I experience about 5% packet loss - at worst 11%.
I have trace routed between the end points, and found where my problems start; (end points have been removed)
2 10.77.128.1 (10.77.128.1) 10.372 ms 17.663 ms 17.596 ms
3 * * *
4 * * *
5 * * *
(Good) 6 126.96.36.199 (188.8.131.52) 18.084 ms 184.108.40.206 (220.127.116.11) 22.310 ms 18.104.22.168 (22.214.171.124) 22.358 ms
(bad) 7 126.96.36.199 (188.8.131.52) 36.251 ms 26.466 ms 24.580 ms
8 * * *
(bad) 9 nme-apt-bur-crt2-te-gi-0-7-0-13.tpgi.com.au (184.108.40.206) 25.707 ms 25.292 ms 25.315 ms
(bad) 10 203-219-155-2.tpgi.com.au (220.127.116.11) 27.607 ms 203-219-155-65.tpgi.com.au (18.104.22.168) 26.863 ms 203-219-155-66.tpgi.com.au (22.214.171.124) 27.070 ms
11 nme-apt-bur-crt2-be-30.tpgi.com.au (126.96.36.199) 29.073 ms nme-apt-bur-crt1-be-30.tpgi.com.au (188.8.131.52) 26.373 ms 28.699 ms
12 nme-apt-bur-bras32-po10.tpgi.com.au (184.108.40.206) 25.437 ms 28.520 ms 30.011 ms
At the same time of running ping tests, I'm pinging google's dns server (220.127.116.11) and not having any packet loss issues (0 packets dropped after 1 hour)
The IP addresses at hops 6 nd 7 are owned by Singtel/Optus.
Can someone please help me?
2019-03-14 01:09 PM
Your post doesn’t show anything wrong?
36ms is a decent response time and 18.104.22.168 is the hop router over to the TPG network (as iiNet uses TPG backhaul).
i don’t see any packet loss in your post?
2019-03-14 02:56 PM
Thanks for your interest in this post. No, no one has got back to me.
I'm glad you are able to interpret a traceroute, however traceroute contains no information pertaining to packet loss.
To garner this information - I rang ping tests for hours to get results, as I stated in my post.
No - I didn't post the ping command output results - I didn't think that was necessary. A percentage and an expalnation should have been sufficient for any network engineer with suffcient privileges to hunt down this problem, and start remedial actions.
My target audience for the post was Optus network engineers, who I was unable to reach via telephone or chat channels.
The good news is - a quick (5 minute ping test) seems to show that the packet loss issue has been fixed (no packet loss). I have seen this issue disappear and come back, and took an opportune time of when it was bad to start this thread.