[156785] 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 (Derek Ivey)
Wed Sep 26 14:37:55 2012

From: Derek Ivey <derek@derekivey.com>
In-Reply-To: <42FFDE3C-D460-4759-BEFF-D407563D791C@derekivey.com>
Date: Wed, 26 Sep 2012 14:37:42 -0400
To: Darius Jahandarie <djahandarie@gmail.com>
Cc: NANOG mailing list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org

After some further troubleshooting, I believe I have narrowed down the =
issue to one of Verizon's routers (130.81.28.255).

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

I had my client send me the output of the ping command (100 pings) and a =
trace route.=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.

I asked them to open a ticket with Verizon to take a look.

Thanks,
Derek

On Sep 26, 2012, at 1:54 PM, Derek Ivey <derek@derekivey.com> wrote:

> 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



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