Level3 issues from Denver to San Jose?

Mailman List Mirror (Read Only)
1

I'm seeing packetloss starting at
ae-1-100.ebr1.Denver1.Level3.net(4.69.132.37) destined down to San
Jose (4.69.132.57).

10. ae-1-100.ebr1.Denver1.Level3.net 1.5%

11. ae-3-3.ebr2.SanJose1.Level3.net 3.6%

12. ae-92-92.csw4.SanJose1.Level3.net 3.9%

13. ae-4-99.edge2.SanJose1.Level3.net 3.9%

Is anyone else seeing the same thing? I know its not much, but at times it
spikes up, this was just part of a small snapshot taken.

~Jared

2

I'm seeing some packet loss out of one of my routers in San Diego, we peer
with L3.

ping 4.69.132.57 so gi3/8 repeat 1000 size 5000

Type escape sequence to abort.
Sending 1000, 5000-byte ICMP Echos to 4.69.132.57, timeout is 2 seconds:
Packet sent with a source address of x.y.d.z
!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!
!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!
!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!
!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!
!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!!!!!!.!!!!!!!!!!!
!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!
!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!!!!
!!!!!!!!.!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!!.!!!!!!!!!!!!!.!!!
!!!!!!!!!!!.!
Success rate is 93 percent (534/573), round-trip min/avg/max = 20/27/204 ms

3

That's most probably ICMP rate-limiting by Level3 - notice the regular
pattern. Judging from the reverse DNS of your ping target, this is a
Juniper router interface that you are pinging.

Best regards,
Daniel