[outages] Savvis LA issues?

[Jeremy Chadwick]

Todd,

http://www.nanog.org/meetings/nanog47/presentations/Sunday/RAS_Traceroute_N47_Sun.pdf

1. Can you provide source and destination IPs?

2. Do you have a return path traceroute?  This is incredibly important.

3. Can you use a utility like mtr instead, from both endspoints?

4. Is there some reason your below traceroute is in some format that
looks almost hand-written and lacks any indication of packet loss (e.g.
no "*" indicators)?  It's not that I don't believe you, it's that the
evidence needs to be presented.

If you need a destination to reach (that hopefully utilises the network
path you're seeing problems with), you can use my box: 206.125.172.42.
I do not filter ICMP.  If you provide an answer to #1 I can provide
return-path results.

But in general, testing against a site where you don't have return-path
access/visibility makes troubleshooting very difficult.  See the PDF I
linked.  :-)

-- 
| Jeremy Chadwick                                   jdc at koitsu.org |
| UNIX Systems Administrator                http://jdc.koitsu.org/ |
| Mountain View, CA, US                                            |
| Making life hard for others since 1977.             PGP 4BD6C0CB |

On Wed, Apr 24, 2013 at 01:57:22PM -0700, Todd Lyons wrote:
> We have a colo in the El Segundo Savvis facility and as of about 30
> minutes ago we started experiencing much reduced inbound traffic
> (email) and outbound traffic (websites) and large packet loss.  Doing
> a traceroute to yahoo, I see:
> 
>  2:  gw.iv.ivenue.com (208.89.136.1)                        0.617ms
>  3:  no reply
>  4:  hr2-v3008.la1.savvis.net (64.70.11.61)                 0.810ms
>  5:  204.70.203.90 (204.70.203.90)                         15.891ms
>  6:  no reply
>  7:  208.178.58.221 (208.178.58.221)                       13.790ms
>  8:  no reply
>  9:  no reply
> 10:  YAHOOPEER.Te2-3.1101.ar5.CHI2.gblx.net (206.57.3.210)  67.495ms asymm 13
> 11:  ae-7.pat1.nez.yahoo.com (216.115.104.124)             80.223ms asymm 15
> 12:  xe-5-0-0.msr1.ne1.yahoo.com (216.115.100.1)           80.218ms asymm 16
> 13:  xe-4-0-0.clr1-a-gdc.ne1.yahoo.com (98.138.144.21)     74.594ms asymm 17
> 
> Hop 5 is Savvis, hop 7 is Level 3.  I do not know the geographical
> location of those routers.  The master case number is 3877881, but I
> can't view any details of that case from their portal (and they
> "closed" mine that I created when they attached it to the master
> case).  I know it's impacting the El Segundo and Orange County
> facilities, not sure about Burbank or any other locations.
> 
> Is there something going on with either of these two (Savvis and/or
> Level 3) at the moment that anybody is aware of in the SoCal area?
> Details, we're looking for details.
> 
> ...Todd
> --
> The total budget at all receivers for solving senders' problems is $0.
>  If you want them to accept your mail and manage it the way you want,
> send it the way the spec says to. --John Levine
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages