RE: should all IBGP neighbours have all EBGP paths?

From: mcaplan.cs@xxxxxxxxxxxxxxx
Date: Mon May 21 2001 - 06:06:49 GMT-3


   
Darren,

I cant tell without diagrams and configs, but I suspect its a case of BGP
only advertises the best path.
Consider the following example

r3----------------r4 AS2
| |
++++++++++++++++++++++
| |
| |
r1-----------------r2 AS1

If R2 has the better local preference to AS2, it will tell R1 about it. R1
will then decide that R2 is the best route to AS2. Any route that R1 had
advertised to R2 as a route to AS2 will be then withdrawn. If you use 'debug
ip bgp updates' you can actually see this WITHDRAWN message being sent.
After that R2 will only have a single route to AS2 in the BGP table. R1
however will probably have 2 routes in its BGP table - the best one via R2
and the other via R3.

Hope this helps

Mark

> ----------
> From: zhutong[SMTP:zhutong@ronghai.com.cn]
> Reply To: zhutong
> Sent: Montag, 21. Mai 2001 08:02
> To: Darren Hosking; ccielab@groupstudy.com
> Subject: Re: should all IBGP neighbours have all EBGP paths?
>
> Give your config pls.
>
> ----- Original Message -----
> From: "Darren Hosking" <dhosking@commander.com.au>
> To: <ccielab@groupstudy.com>
> Sent: Monday, May 21, 2001 11:44 AM
> Subject: should all IBGP neighbours have all EBGP paths?
>
>
> > I have 2 BGP routers connected externally to the same AS and internally
> to
> > each other using IBGP. The local preference is set to prefer one link
> over
> > the other. All paths are visible on the non-preferred router (shows both
> > paths out with the other as preferred), however, the router with the
> > preferred path to the ISP only shows the paths it knows about and not
> the
> > paths via the other link.
> >
> > Is this correct? Don't both need all paths or are they exchanged when
> the
> > preferred path is no longer available (could be a lot of traffic)?
> >
> > I'm using Halabi 1st edition as reference, is the 2nd edition much
> better
> > and in what areas (ie should I buy the newer edition).
> >
> > Thanks, Darren
> >
> > The output of sh ip bgp summ and sh ip bgp for one network is shown
> below.
> >
> > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> > State/PfxRcd
> > 10.0.1.1 4 1221 6221 3628 43815 0 0 2d12h
> 6606
> > 172.24.24.1 4 65000 6626 6313 43815 0 0 13:10:59
> 6606
> >
> > BGP table version is 43789, local router ID is 172.24.97.1
> > Status codes: s suppressed, d damped, h history, * valid, > best, i -
> > internal
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > *>i9.3.4.0/24 172.24.24.1 300 0 1221 ?
> > * 10.0.1.1 250 0 1221 ?
> >
> > Neighbor V AS MsgRcvd MsgSent TblVer InQ OutQ Up/Down
> > State/PfxRcd
> > 10.0.2.1 4 1221 43026 26728 37714 0 0 4d01h
> 6605
> > 172.24.96.1 4 65000 11860 12348 37714 0 0 13:10:26
> 0
> > <---?????
> >
> > BGP table version is 37689, local router ID is 172.24.23.1
> > Status codes: s suppressed, d damped, h history, * valid, > best, i -
> > internal
> > Origin codes: i - IGP, e - EGP, ? - incomplete
> >
> > Network Next Hop Metric LocPrf Weight Path
> > *> 9.3.4.0/24 10.0.2.1 300 0 1221 ?
> > **Please read:http://www.groupstudy.com/list/posting.html
> **Please read:http://www.groupstudy.com/list/posting.html
Visit us at http://www.clearstream.com

IMPORTANT MESSAGE

Internet communications are not secure and therefore Clearstream International
does not
accept legal responsibility for the contents of this message.

The information contained in this e-mail is confidential and may be legally pri
vileged. It is
intended solely for the addressee. If you are not the intended recipient, any d
isclosure,
copying, distribution or any action taken or omitted to be taken in reliance on
 it, is
prohibited and may be unlawful. Any views expressed in this e-mail are those of
 the
individual sender, except where the sender specifically states them to be the v
iews of
Clearstream International or of any of its affiliates or subsidiaries.

END OF DISCLAIMER
**Please read:http://www.groupstudy.com/list/posting.html



This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:30:47 GMT-3