[156786] in North American Network Operators' Group

home help back first fref pref prev next nref lref last post

Re: Anyone from Verizon/TATA on here? Possible Packet Loss

daemon@ATHENA.MIT.EDU (Jo Rhett)
Wed Sep 26 15:02:44 2012

From: Jo Rhett <jrhett@netconsonance.com>
In-Reply-To: <CF7F3A48-A3FD-44E5-8C04-4B181BB8D6A7@derekivey.com>
Date: Wed, 26 Sep 2012 12:02:04 -0700
To: Derek Ivey <derek@derekivey.com>
Cc: NANOG mailing list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

Many (most?) routers deprioritize ICMP meesages. Direct pings against =
the router are not informative re transit failures.

On Sep 26, 2012, at 11:37 AM, Derek Ivey wrote:
> After some further troubleshooting, I believe I have narrowed down the =
issue to one of Verizon's routers (130.81.28.255).
>=20
> ping 130.81.28.255 repeat 100
> Type escape sequence to abort.
> Sending 100, 100-byte ICMP Echos to 130.81.28.255, timeout is 2 =
seconds:
> ?!!!!!!!!?!!!!!!!?!!!!!!!!?!!!!!!!!!!!!!!!?!!!!!!!!!!!!!!?!!!!!!!!!!!?
> !!!!!!!!!!!!!!!!!!!!!!?!!!?!!!
> Success rate is 91 percent (91/100), round-trip min/avg/max =3D =
20/26/30 ms
>=20
> I had my client send me the output of the ping command (100 pings) and =
a trace route.=20
>=20
> Their 5th hop is 130.81.28.254 and one of the response times in their =
trace route was 175ms so the issue seems to be around there.
>=20
> I asked them to open a ticket with Verizon to take a look.
>=20
> Thanks,
> Derek
>=20
> On Sep 26, 2012, at 1:54 PM, Derek Ivey <derek@derekivey.com> wrote:
>=20
>> Thanks guys. That was an informative read. I will do some more =
troubleshooting.
>>=20
>> Derek
>>=20
>> On Sep 26, 2012, at 1:16 PM, Darius Jahandarie =
<djahandarie@gmail.com> wrote:
>>=20
>>> On Wed, Sep 26, 2012 at 1:10 PM, Blake Dunlap <ikiris@gmail.com> =
wrote:
>>>> This is not the proper way to interpret traceroute information. =
Also, 3
>>>> pings is not sufficient to determine levels of packet loss =
statistically.
>>>>=20
>>>> I suggest searching the archives regarding traceroute, or googling =
how to
>>>> interpret them in regards to packet loss, as what you posted does =
not
>>>> indicate what you think it does.
>>>=20
>>> Agreed. Derek should read "A Practical Guide to (Correctly)
>>> Troubleshooting with Traceroute":
>>> =
http://www.nanog.org/meetings/nanog45/presentations/Sunday/RAS_traceroute_=
N45.pdf
>>>=20
>>> --=20
>>> Darius Jahandarie
>>=20
>=20
>=20

--=20
Jo Rhett
Net Consonance : net philanthropy to improve open source and internet =
projects.




home help back first fref pref prev next nref lref last post