[outages] level3 LA

[jd]

   2.|-- cr2.la2ca.ip.att.net       0.0%  1000   13.2  16.2   9.6 126.4  
15.6
   3.|-- ggr2.la2ca.ip.att.net      0.0%  1000    9.7  15.7   8.6 144.1  
16.9
   4.|-- 192.205.37.146             0.0%  1000   10.9  15.8  10.6 149.3  
16.8
   5.|-- vl-3508-ve-122.ebr1.tusti  0.0%  1000    9.9  14.3   9.6 120.3  
15.4
   6.|-- ae-6-6.ebr1.losangeles1.l  0.0%  1000   13.6  18.7  13.5 132.4  
16.2
   7.|-- ae-81-81.csw3.losangeles1  0.0%  1000   12.6  17.2  12.3 147.4  
16.5
   8.|-- ae-3-80.edge3.losangeles1  7.3%  1000   12.5  16.7  12.3 140.6  
15.8
   9.|-- b.resolvers.level3.net     8.0%  1000   30.8  33.4  16.4 161.3  
16.6

   2.|-- ae7.cr1.lax112.us.above.n  0.1%  1000    2.9   5.6   2.5 69.4   7.5
   3.|-- ae8.mpr1.lax12.us.above.n 21.7%  1000    2.7   3.2   2.4 63.9   4.7
   4.|-- ae7.edge2.LosAngles.Level  4.9%  1000    2.7   3.4   2.5 85.7   6.3
   5.|-- ae-1-60.edge3.LosAngeles1  6.1%  1000    3.4   2.8   2.5 21.9   1.9
   6.|-- b.resolvers.Level3.net     9.3%  1000   18.3  19.7  10.7 24.9   1.7



problem is now gone..

   2.|-- cr2.la2ca.ip.att.net       0.0%    50   11.8  11.6   9.7 13.6   0.9
   3.|-- ggr2.la2ca.ip.att.net      0.0%    50   10.0  10.8   8.7 12.7   1.0
   4.|-- 192.205.37.146             0.0%    50   10.7  12.1  10.7 72.0   8.6
   5.|-- vl-3508-ve-122.ebr1.tusti  0.0%    50    9.9   9.9   9.7 11.8   0.3
   6.|-- ae-6-6.ebr1.losangeles1.l  0.0%    50   13.6  13.8  13.5 15.7   0.3
   7.|-- ae-81-81.csw3.losangeles1  0.0%    50   14.6  12.8  12.4 20.2   1.1
   8.|-- ae-3-80.edge3.losangeles1  0.0%    50   12.3  12.8  12.3 29.5   2.4
   9.|-- b.resolvers.level3.net     0.0%    50   12.0  18.7  11.7 29.4   5.8

On 3/11/2014 10:28 AM, Tri Tran wrote:
> We couldn't ping one IP in Tustin from the outside (was able to ping 
> from same network) from 6:45am- 8:05am PST.
> Problem went away around 8:15 AM PST.
> Weird that only one IP was affected.
> --
> Tri Tran
> On 3/11/2014 10:15 AM, Jeremy Chadwick wrote:
>> Your 1st traceroute shows loss happening within the Los Angeles region
>> possibly within Level3 (hop #8 from the look of it, and it looks like
>> multipathing is involved).  Because traceroutes going only one direction
>> are provided (due to the destination you chose and the nature of
>> asymmetric routing), only half of the picture is shown, which is why I
>> say "possibly".
>>
>> Your 2nd traceroute shows two things;
>>
>> - Loss showing up starting at hop #3 (possibly within Zayo/Abovenet
>>    space, again "possibly", re: asymmetric routing)
>> - Loss showing up at hop #8 (could be an effect of something happening
>>    earlier in the path)
>>
>> For reference, here are your traceroutes:
>>
>> https://puck.nether.net/pipermail/outages/2014-March/006787.html
>>
>> So when you say "I think it's a problem with Tustin > LA", the 2nd
>> traceroute you provided doesn't seem to support that theory, nor the
>> statement "I am unable to reproduce it to any other network".
>>
>> Do you have any other tools available to you, like mtr?  mtr won't
>> narrow down where the issue is happening, but would make it more clear
>> as to where the issue is happening, especially if you let it run for a
>> while (say 10 minutes or so) from both places (you didn't provide source
>> IPs for either traceroute, so that doesn't help either).
>>
>
>
>
> _______________________________________________
> Outages mailing list
> Outages at outages.org
> https://puck.nether.net/mailman/listinfo/outages

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://puck.nether.net/pipermail/outages/attachments/20140311/b6a5223a/attachment.htm>