[41057] in North American Network Operators' Group
Re: multi-homing fixed
daemon@ATHENA.MIT.EDU (Valdis.Kletnieks@vt.edu)
Wed Aug 29 01:17:08 2001
Message-Id: <200108290515.f7T5FuZ03711@foo-bar-baz.cc.vt.edu>
To: jlewis@lewis.org
Cc: nanog@merit.edu
In-reply-to: Your message of "Wed, 29 Aug 2001 00:05:58 EDT."
<Pine.LNX.4.30.0108282357480.1854-100000@redhat1.mmaero.com>
From: Valdis.Kletnieks@vt.edu
Date: Wed, 29 Aug 2001 01:15:56 -0400
Errors-To: owner-nanog-outgoing@merit.edu
On Wed, 29 Aug 2001 00:05:58 EDT, jlewis@lewis.org said:
> Redundancy is only one reason to multihome. More paths (hopefully at
> least one per destination that doesn't suck) is another big one, and
We had some truly sucking paths to some destinations yesterday (15000ms
over our OC-3) until our chief NOC monkey said enough was enough and
nuked the BGP session with the other end.
Happen to have any pointers to "this path sucks no matter what BGP says"
tools? Especially for the case of the *real* problem being 2 or 3 AS's
down the chain?
Or does everybody's noc monkeys wait for the "foobar.com sucks" phone calls?
Valdis Kletnieks
Operating Systems Analyst
Virginia Tech
