From: John Bays (baysjohn@xxxxxxx)
Date: Sat Feb 03 2001 - 22:32:52 GMT-3
No to mention it's EGP-multihop... kinda begs for an EBGP problem, not this
IBGP stated problem.
ebgp-multihop is not relevant to this question.
no sync needs to be on in your BGP process, and you need next-hop-self in
strategic positions (Find out where!)
John
At 05:18 PM 2/3/2001 -0800, Kevin Baumgartner wrote:
> So I thought this was a question about Route reflectors?
>Why would you do a neighbor egp-multihop on each of the BGP client
>routers? Sort of defeats the purpose of using Route reflectors.
>
> Kevin
>
> >
> > Add the "neighbor <ip-address> ebgp-multihop option, since you are using
> > update-source you need to increase the hop count.
> >
> > Jeff Kesemeyer
> >
> > -----Original Message-----
> > From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
> > Moran, Ed
> > Sent: Saturday, February 03, 2001 7:44 PM
> > To: 'ccielab@groupstudy.com'
> > Subject: BGP Route Reflection
> >
> >
> > I am having problams with BGP Route Reflection. R3, my RR, is not
> reflecting
> > routes to clients or between clients. All neighbors are Established.
> Here is
> > the config for R3's BGP.
> >
> > router bgp 1
> > bgp router-id 138.1.3.3
> > network 138.1.0.0
> > neighbor 138.1.1.1 remote-as 1
> > neighbor 138.1.1.1 update-source Loopback0
> > neighbor 138.1.1.1 route-reflector-client
> > neighbor 138.1.4.4 remote-as 1
> > neighbor 138.1.4.4 update-source Loopback0
> > neighbor 138.1.4.4 route-reflector-client
> > neighbor 138.1.5.5 remote-as 1
> > neighbor 138.1.5.5 update-source Loopback0
> > neighbor 138.1.5.5 route-reflector-client
> > neighbor 150.10.9.2 remote-as 6
> >
> > 138.1.1.1 - R1
> > 138.1.4.4 - R4
> > 138.1.5.5 - R5
> > 150.10.9.2 - R6
> >
> > R3 has all routes as shown.
> >
> > R3#sh ip bgp
> > BGP table version is 3, local router ID is 138.1.3.3
> > 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
> > *> 138.1.0.0 0.0.0.0 0 32768 i
> > * i 138.1.5.5 0 100 0 i
> > * i 138.1.4.4 0 100 0 i
> > * i 138.1.1.1 0 100 0 i
> > * i140.10.0.0 138.1.1.1 0 100 0 i
> > *> 150.10.0.0 150.10.9.2 0 0 6 i
> > * i160.10.0.0 160.10.9.6 0 100 0 2 i
> >
> > 140.10.0.0 is being advertised by R1, 150.10.0.0 is being advertised by R6,
> > and 160.10.0.0 is being received by R5. R5 originally receivd the routed
> > from R2 vie EBGP.
> >
> > R1 has IP BGP = 138.1.0.0, 140.10.0.0, and 150.10.0.0
> > R4 has IP BGP = 138.1.0.0, and 150.10.0.0
> > R5 has IP BGP = 138.1.0.0, 150.10.0.0, and 160.10.0.0
> > R6 has IP BGP = 138.1.0.0, and 150.10.0.0
> > R2 has IP BGP = 138.1.0.0, and 160.10.0.0
> >
> > Can anyone help me discover why the routes won't "sychronize"? I am not
> > using any route-maps or special commands. This is only a basic config. R5,
> > R1, R3, and R4 are all part of AS 1 and use OSPF as the IGP. All routes in
> > the OSPF domain are sychronized. Please help...
> >
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:28:35 GMT-3