[38847] in North American Network Operators' Group
Re: Routing Table inconsistencies
daemon@ATHENA.MIT.EDU (Robert E. Seastrom)
Mon Jun 18 20:30:21 2001
To: Tim Winders <twinders@SPC.cc.tx.us>
Cc: David Meyer <dmm@sprint.net>,
Marshall Eubanks <tme@21rst-century.com>,
Nanog mailing list <nanog@merit.edu>,
MbonedD List <mboned@network-services.uoregon.edu>,
tech team <tech@multicasttech.com>
From: rs@seastrom.com (Robert E. Seastrom)
Date: 18 Jun 2001 20:29:40 -0400
In-Reply-To: Tim Winders's message of "Mon, 18 Jun 2001 19:13:37 -0500 (CDT)"
Message-ID: <871yoh5n2j.fsf@valhalla.seastrom.com>
Errors-To: owner-nanog-outgoing@merit.edu
Tim Winders <twinders@SPC.cc.tx.us> writes:
> This is probably a bone-head question, but what are the implications of
> inconsistent-as's?
it means that two different ASes are originating the same prefix/mask.
> I know that I have _tons_ of bgp inconsitent-as paths, but no mbgp
> inconsistent-as paths.
>
> I also have 2 bgp peers, but only 1 mbgp peer. I would think if you only
> have 1 mbgp peer you could _not_ have any inconsistent-as paths as there
> is only one source for the mbgp information, so only 1 path. Right?
They could still be out there, just you would never hear them. :)
---Rob
