![]() ![]() ![]() ![]() |
|
It's not out of the realm of possibility that the LFC PON port is congesting (or exhibiting behaviours resulting from very high usage) but confirming that requires parsing hundreds of GB of data from Chorus. (I'm not sure if the other LFCs even make the data available)
Cheers- N
Please note all comments are from my own brain and don't necessarily represent the position or opinions of my employer, previous employers, colleagues, friends or pets.
Response from Orcon, aligns with comments above:
We have provided the data to our Tier 2 team to review. There does appear to be a large spike in ping when your issues occur but they have not been able to find an explanation as to why this is the case. There is uncertainty as to why IPv6 appears to be prioritised too. To elaborate, they are not seeing any breaks in session or other noticeable issues in our records which align with the timing of the ping spikes in the data you have provided.
Our Tier 2 team has advised that they will need more data. They have indicated that you should use a minimalistic setup (i.e. connect the PC directly to the modem which in turn is connected directly to the ONT). No other devices should be connected at the time of testing as they wish to rule out all other variables related to your equipment/setup.
With the setup above, the team has requested that you perform and provide the following:
1. A trace route run on your PC.
2. A trace route run on your PC with IPv6 disabled.
3. A trace route run on an alternate PC.
Any views expressed on these forums are my own and don't necessarily reflect those of my employer.
Any views expressed on these forums are my own and don't necessarily reflect those of my employer.
majiktripp: Have just updated LAN DHCP settings on the Orcon modem and disabled IPV6 so will monitor over next while and see if any impact/change.
Any views expressed on these forums are my own and don't necessarily reflect those of my employer.
Just had another outage, and hooked up the laptop to the ONT box via the LAN 1 Port being used by the Orcon router.
Pings from the laptop via the ONT box worked without issue, detailed below:
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [2400:4800:1::6] with 32 bytes of data:
Reply from 2400:4800:1::6: time=2ms
Reply from 2400:4800:1::6: time=1ms
Reply from 2400:4800:1::6: time=1ms
Reply from 2400:4800:1::6: time=1ms
Ping statistics for 2400:4800:1::6:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Ping statistics for 60.234.0.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Ping statistics for 60.234.0.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=3ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Ping statistics for 60.234.0.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 2ms, Maximum = 3ms, Average = 2ms
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Ping statistics for 60.234.0.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 2ms, Average = 1ms
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=3ms TTL=252
Reply from 60.234.0.19: bytes=32 time=3ms TTL=252
Reply from 60.234.0.19: bytes=32 time=2ms TTL=252
Reply from 60.234.0.19: bytes=32 time=1ms TTL=252
Ping statistics for 60.234.0.19:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 1ms, Maximum = 3ms, Average = 2ms
At this point, I reconnected to the Orcon Router and was carrying out pings on the laptop - the times below blow out again:
C:\Users\Caroline>ping www.orcon.net.nz
Ping request could not find host www.orcon.net.nz. Please check the name and try again.
C:\Users\Caroline>ping www.orcon.net.nz
Ping request could not find host www.orcon.net.nz. Please check the name and try again.
C:\Users\Caroline>ping www.orcon.net.nz
Pinging www.orcon.net.nz [60.234.0.19] with 32 bytes of data:
Reply from 60.234.0.19: bytes=32 time=18ms TTL=251
Request timed out.
Reply from 60.234.0.19: bytes=32 time=1457ms TTL=251
Reply from 60.234.0.19: bytes=32 time=2796ms TTL=251
Ping statistics for 60.234.0.19:
Packets: Sent = 4, Received = 3, Lost = 1 (25% loss),
Approximate round trip times in milli-seconds:
Minimum = 18ms, Maximum = 2796ms, Average = 1423ms
Seems it would indicate an issue with the Orcon router? I'll be sending this all through to their ICT on the existing thread but at this point I'm thinking of swapping out the router for one of my own (leaning towards Ubiquiti Edgerouter at moment).
Last update for completeness. I have removed the Orcon router from the equation and been running a TP-Link ER605 router in its place. It has been up and running for the last 9 days without any drop outs or outages and seems to have resolved the problem. I will continue to monitor using the TP-Link Omada SDN software but so far so good. Seems to indicate the router itself was the core of the problem all along.
|
![]() ![]() ![]() ![]() |