[166426] in North American Network Operators' Group
Re: BGP failure analysis and recommendations
daemon@ATHENA.MIT.EDU (Christopher Morrow)
Wed Oct 23 23:06:22 2013
In-Reply-To: <5.1.0.14.0.20131023214304.0396ead0@authsmtp.jensenresearch.com>
Date: Wed, 23 Oct 2013 23:06:07 -0400
From: Christopher Morrow <morrowc.lists@gmail.com>
To: JRC NOC <nospam-nanog@jensenresearch.com>
Cc: nanog list <nanog@nanog.org>
Errors-To: nanog-bounces+nanog.discuss=bloom-picayune.mit.edu@nanog.org
On Wed, Oct 23, 2013 at 10:40 PM, JRC NOC
<nospam-nanog@jensenresearch.com> wrote:
> Is this just an unavoidable issue with scaling large networks?
nope... sounds like (to me at least) the forwarding plane and control
plane are non-congruent in your provider's network :( so as you said,
if the forwarding-plane is dorked up between you and 'the rest of
their netowrk', but the edge device you are connected to thinks
next-hops for routes are still valid... oops :(
> Is it perhaps a known side effect of MPLS?
nope.
> Have we/they lost something important in the changeover to converged
> mutiprotocol networks?
> Is there a better way for us edge networks to achieve IP resiliency in the
> current environment?
sadly I bet not, aside from active probing and disabling paths that
are non-functional.
