Lima, OH Spectrum/Charter Severe Node/Hop Latency Issues
ross at tajvar.io
Wed Feb 8 00:11:57 UTC 2023
For those who haven't seen it (i.e. Austin), here is "the guide" on how to
troubleshoot correctly with traceroute:
ICMP is deprioritized by any normal router. Non-cascading loss does not
indicate a problem of any kind. The NOC doesn't care because nothing is
wrong, and the OSP team definitely doesn't care because ICMP is several
layers above OSP and is therefore not their problem.
On Tue, Feb 7, 2023 at 5:11 PM Kevin Shymkiw <kshymkiw at gmail.com> wrote:
> ICMP response time from a router/device is not a great way to judge if
> there is an issue or not. The devices generally have control plane
> policing and responding to ICMP is not prioritized at all.
> I would suggest your engineer setup something on their end of the
> connection that you can ping, and start there.
> Leverage something like smoke ping to something on their LAN, or even the
> public IP on their RG/Modem.
> On Tue, Feb 7, 2023 at 15:01 Austin Ayers via NANOG <nanog at nanog.org>
>> Hello all,
>> One of my NetOps engineers resides in Lima, Ohio and they are receiving
>> terrible bufferbloat, packet loss, and random disconnects.
>> I have been pinging 184.108.40.206 (Lima, OH Spectrum/Chart Node) and it's
>> rejecting a ton of packets. This has been going on for weeks.
>> Node having problems: lag-1.limaohid01h.netops.charter.com
>> NOC seems like they don't care, same with OSP in the field.
>> There is no reason why this hop (#13) should have up to 613ms ping times.
>> Thank you,
-------------- next part --------------
An HTML attachment was scrubbed...
More information about the NANOG