[159565] in North American Network Operators' Group
Re: Issues with level3?
daemon@ATHENA.MIT.EDU (Warren Bailey)
Tue Jan 15 12:24:06 2013
From: Warren Bailey <wbailey@satelliteintelligencegroup.com>
To: Richard A Steenbergen <ras@e-gerbil.net>, Network Operations
<NetworkOperations@etsms.com>
Date: Tue, 15 Jan 2013 17:23:50 +0000
In-Reply-To: <20130115171710.GY65604@gerbil.cluepon.net>
Cc: "nanog@nanog.org" <nanog@nanog.org>
Reply-To: Warren Bailey <wbailey@satelliteintelligencegroup.com>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
I still call a /24 a class c too.. :/ lol
From my Android phone on T-Mobile. The first nationwide 4G network.
-------- Original message --------
From: Richard A Steenbergen <ras@e-gerbil.net>
Date: 01/15/2013 9:19 AM (GMT-08:00)
To: Network Operations <NetworkOperations@etsms.com>
Cc: nanog@nanog.org
Subject: Re: Issues with level3?
On Tue, Jan 15, 2013 at 04:12:12PM +0000, Network Operations wrote:
> Anyone seeing any issues with level3? We can connect to every other
> IP in our Class C. When tracerouting to individual IP's,
> (x.x.x.50/51/52/53) we get a drop at
> ge-4-16.car2.Washington1.Level3.net [4.59.146.53] for 50, but 51 is
> fine, drop for 52, 53 is fine.
Sounds like a classic problem with a member of a bundle (like a link-agg
or ECMP) breaking. Level3 tends not to do anything in bundles of 2, so
you might want to look elsewhere, like with your own connections to
them, possibly on the reverse path. Now, please go find a blunt object
and hit yourself in the head as punishment for using the words "Class C"
in 2013 in a non-historic or ironic context. Hard. :)
--
Richard A Steenbergen <ras@e-gerbil.net> http://www.e-gerbil.net/ras
GPG Key ID: 0xF8B12CBC (7535 7F59 8204 ED1F CC1C 53AF 4C41 5ECA F8B1 2CBC)
