A traceroute would be more useful than ping in this situation, especially since the TTL is reaching 118 (!!!). Routing loop anyone? -- | Jeremy Chadwick jdc at parodius.com | | Parodius Networking http://www.parodius.com/ | | UNIX Systems Administrator Mountain View, CA, US | | Making life hard for others since 1977. PGP 4BD6C0CB | On Tue, Jul 26, 2011 at 10:34:08AM -0400, J. Oquendo wrote:
Anyone seeing hiccups on while traversing po2-20G.ar2.dca3 or po3-20G-ar1.mia2 I'm getting bucket loads of TTL exceeded errors:
From 67.16.142.209 icmp_seq=1177 Time to live exceeded From 67.16.142.209 icmp_seq=1181 Time to live exceeded From 67.16.142.209 icmp_seq=1184 Time to live exceeded 64 bytes from 8.20.18x.xxx: icmp_seq=1187 ttl=118 time=94.5 ms 64 bytes from 8.20.18x.xxx: icmp_seq=1188 ttl=118 time=91.5 ms 64 bytes from 8.20.18x.xxx: icmp_seq=1189 ttl=118 time=92.0 ms 64 bytes from 8.20.18x.xxx: icmp_seq=1190 ttl=118 time=91.0 ms
...
1259 packets transmitted, 1098 received, +34 errors, 12% packet loss, time 1259563ms rtt min/avg/max/mdev = 8.192/156.007/8703.504/684.907 ms, pipe 10
Whenever I cross a peering between the two (XO + Global) I am seeing nothing but errors.
--
=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+=+ J. Oquendo SGFA, SGFE, C|EH, CNDA, CHFI, OSCP, CPT, RWSP, GREM
"It takes 20 years to build a reputation and five minutes to ruin it. If you think about that, you'll do things differently." - Warren Buffett
42B0 5A53 6505 6638 44BB 3943 2BF7 D83F 210A 95AF http://pgp.mit.edu:11371/pks/lookup?op=get&search=0x2BF7D83F210A95AF
_______________________________________________ Outages mailing list Outages@outages.org https://puck.nether.net/mailman/listinfo/outages