<div dir="ltr">Hi Jeremy, thanks for getting back to me.<div><br></div><div style>That is indeed our edge router, I was just giving an example of the path.</div><div style><br></div><div style>We have all return traffic preferenced to leave the network via our Level3 connection right now, and we've got our AS prepended with our nLayer session multiple times. Cox is choosing to use our nLayer route inbound regardless and we're not going to consider taking it down to resolve the problem.</div>
<div style><br></div><div style>The trace path I sent is not unusual for our connection (though the latency is, we've been in contact with Cox about that), I was providing it as an example of the inbound path only.</div>
<div style><br></div><div style>The issue is affecting all Cox users in our area, so it's not isolated to our office or even our city.</div><div style><br></div><div style>The fact that ICMP is unaffected leads me to believe that a malfunctioning device performing some sort of "traffic shaping" may be at fault.</div>
</div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Dec 19, 2012 at 6:34 PM, Jeremy Chadwick <span dir="ltr"><<a href="mailto:jdc@koitsu.org" target="_blank">jdc@koitsu.org</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Brandon,<br>
<br>
Do you have return-path traceroutes from 198.46.80.1 to wherever you did<br>
the below traceroute (and what is that source IP)? Also, is 198.46.80.1<br>
a host/system or a router? If a router, please do not do that -- please<br>
use a host/system as a destination.<br>
<br>
I would say the problem looks like it's happening between hops #6 and #7<br>
in the below traceroute (jump in latency from 5ms to 210ms), but that<br>
may be normal -- do you have traceroutes for what things look like<br>
normally?<br>
<br>
The latency seen may also be caused by issues on the return-path.<br>
<br>
P.S. -- This would be the first I've heard in a long time where ICMP<br>
*was not* affected, but TCP and UDP were. Usually the reports are<br>
"everything is impacted" or "only ICMP is impacted" (result of ICMP<br>
deprio and a reporter not having familiarity with that fact).<br>
<br>
--<br>
| Jeremy Chadwick <a href="mailto:jdc@koitsu.org">jdc@koitsu.org</a> |<br>
| UNIX Systems Administrator <a href="http://jdc.koitsu.org/" target="_blank">http://jdc.koitsu.org/</a> |<br>
| Mountain View, CA, US |<br>
| Making life hard for others since 1977. PGP 4BD6C0CB |<br>
<div><div class="h5"><br>
On Wed, Dec 19, 2012 at 06:24:46PM -0500, Brandon Whaley wrote:<br>
> We've been seeing intermittent TCP/UDP connectivity issues from Cox<br>
> Communications in Virginia to any location that routes over nLayer. UDP<br>
> traceroutes are fine, but DNS lookups time out for minutes at a time, then<br>
> work again for ~5 minutes before repeating the problem. ICMP is never<br>
> affected during the outages.<br>
><br>
> traceroute to 198.46.80.1 (198.46.80.1), 30 hops max, 60 byte packets<br>
> 1 router36f24c.local (192.168.14.1) 0.560 ms 0.531 ms 0.753 ms<br>
> 2 <a href="http://wsip-174-77-92-169.hr.hr.cox.net" target="_blank">wsip-174-77-92-169.hr.hr.cox.net</a> (174.77.92.169) 2.532 ms 2.581 ms<br>
> 3.009 ms<br>
> 3 172.21.224.153 (172.21.224.153) 3.995 ms 4.067 ms 4.111 ms<br>
> 4 172.21.249.101 (172.21.249.101) 4.185 ms 4.396 ms 4.561 ms<br>
> 5 172.21.249.73 (172.21.249.73) 4.916 ms 4.900 ms 5.128 ms<br>
> 6 172.21.249.18 (172.21.249.18) 5.517 ms 5.124 ms 5.043 ms<br>
> 7 <a href="http://ip-216-54-33-22.coxfiber.net" target="_blank">ip-216-54-33-22.coxfiber.net</a> (216.54.33.22) 210.486 ms 210.477 ms<br>
> 210.466 ms<br>
> 8 68.1.4.139 (68.1.4.139) 221.950 ms 222.460 ms 232.268 ms<br>
> 9 * <a href="http://xe-5-0-7.ar1.iad1.us.nlayer.net" target="_blank">xe-5-0-7.ar1.iad1.us.nlayer.net</a> (69.31.10.81) 226.332 ms 226.866 ms<br>
> 10 <a href="http://as54641.xe-9-0-1.ar1.iad1.us.nlayer.net" target="_blank">as54641.xe-9-0-1.ar1.iad1.us.nlayer.net</a> (69.31.31.42) 223.718 ms<br>
> 225.083 ms 225.744 ms<br>
> 11 198.46.80.1 (198.46.80.1) 225.706 ms 226.670 ms 226.698 ms<br>
><br>
> Is anyone with Cox on the list that can investigate/contact me?<br>
><br>
> --<br>
> Best Regards,<br>
> Brandon W.<br>
<br>
</div></div>> _______________________________________________<br>
> Outages mailing list<br>
> <a href="mailto:Outages@outages.org">Outages@outages.org</a><br>
> <a href="https://puck.nether.net/mailman/listinfo/outages" target="_blank">https://puck.nether.net/mailman/listinfo/outages</a><br>
<br>
</blockquote></div><br><br clear="all"><div><br></div>-- <br>Best Regards, <br>Brandon W.<br>Tier 3 System Administrator<br>InMotion Hosting Inc.<br> <br>888-321-4678<br>757-416-6575 (Int'l)<br>NEW: 24x7 EMAIL and PHONE Technical Support<br>
<br>Did you know?<br>We'll Build, Update and Promote Your Site for You! Visit <a href="http://www.inmotionhosting.com/webdesign" target="_blank">www.inmotionhosting.com/webdesign</a><br>Answers to commonly asked questions, as well as other useful tools, can be found at <a href="http://support.inmotionhosting.com" target="_blank">http://support.inmotionhosting.com</a><br>
<br>How am I doing? Please feel free to email my manager at <a href="mailto:manager_feedback@inmotion.net" target="_blank">manager_feedback@inmotion.net</a><br>
</div>