From: Peter van Oene (pvo@xxxxxxxxxxxx)
Date: Fri Jul 12 2002 - 11:07:31 GMT-3
Cisco only rewrites next_hop for EBGP learned routes. You shouldn't have
any issues here.
At 06:16 PM 7/12/2002 +1000, Hunt Lee wrote:
>Hello Gyori,
>
>Thanks so much for the explanation. But in this case, I'm actually using
>next-hop-self between 2 Route Reflectors (RTA & RTD)?? Is this bad too??
>
>
>1.0.0.0/9 --- RTB-| |-RTE --- 3.3.0.0/17
> |--RTA--RTD--|
>2.0.0.0/10 ---RTC-| |-RTF --- 4.4.4.0/28
>
>
>So RTB & RTC are route reflector clients of RTA &
>RTE & RTF are route reflector clients of RTD
>
>All routers are in the same AS.
>
>
>Thanks!!!
>
>Best Regards,
>Hunt
>
>
>-----Original Message-----
>From: Gyori Gabor [mailto:Gabor.Gyori@lnx.hu]
>Sent: Saturday, 6 July 2002 11:05 PM
>To: Hunt Lee; ccielab@groupstudy.com
>Subject: RE: IOS bug??
>
>
>The route reflector server never changes any BGP attribute on route that is
>heard from a route reflector client and forwarded to an other client.
>In includes localpref and next-hop, communities, etc.
>It is in order to avoid routing loop.
>So it is a (useful) feature, not a bug.
>
>Gabor
>
> > -----Original Message-----
> > From: Hunt Lee [mailto:ciscoforme3@yahoo.com.au]
> > Sent: Saturday, July 06, 2002 2:18 PM
> > To: ccielab@groupstudy.com
> > Subject: IOS bug??
> >
> >
> > Does anyone know if there is a bug on IOS Version 12.0(10)?? I have
> > tried a few other 12.0 images, but there seems to be something wrong
> > with the "neighbor x.x.x.x next-hop self" command.
> >
> > RTD is directly connected to RTA
> >
> > RTA is 172.16.1.3
> > RTD is 172.17.1.3
> >
> > From RTD:
> >
> > router bgp 1
> > no synchronization
> > neighbor 172.16.1.3 remote-as 1
> > neighbor 172.16.1.3 update-source Loopback0
> > neighbor 172.16.1.3 next-hop-self
> > neighbor 172.17.1.1 remote-as 1
> > neighbor 172.17.1.1 update-source Loopback0
> > neighbor 172.17.1.1 route-reflector-client
> > neighbor 172.17.1.2 remote-as 1
> > neighbor 172.17.1.2 update-source Loopback0
> > neighbor 172.17.1.2 route-reflector-client
> >
> > On RTA
> >
> > router bgp 1
> > no synchronization
> > bgp log-neighbor-changes
> > neighbor 172.16.1.1 remote-as 1
> > neighbor 172.16.1.1 update-source Loopback0
> > neighbor 172.16.1.1 route-reflector-client
> > neighbor 172.16.1.2 remote-as 1
> > neighbor 172.16.1.2 update-source Loopback0
> > neighbor 172.16.1.2 route-reflector-client
> > neighbor 172.17.1.3 remote-as 1
> > neighbor 172.17.1.3 next-hop-self
> > no auto-summary
> >
> >
> > But only the routes via RTA has been successfully changed it's
> > Next-Hop, but not the ones via RTD.
> >
> > RouterA#sh ip bgp
> > BGP table version is 3, local router ID is 172.16.1.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
> > *>i1.0.0.0/9 172.16.1.1 0 100 0 i
> > *>i2.0.0.0/10 172.16.1.2 0 100 0 i
> > * i3.3.0.0/17 172.17.1.1 0 100 0 i
> > * i4.4.4.0/28 172.17.1.2 0 100 0 i
> > RouterA#
> >
> >
> > RouterD#sh ip bgp
> > BGP table version is 5, local router ID is 172.17.1.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
> > *>i1.0.0.0/9 172.16.1.3 0 100 0 i
> > *>i2.0.0.0/10 172.16.1.3 0 100 0 i
> > *>i3.3.0.0/17 172.17.1.1 0 100 0 i
> > *>i4.4.4.0/28 172.17.1.2 0 100 0 i
> > RouterD#
> >
> >
> > Please help....
> >
> > H.
> >
>http://www.sold.com.au - SOLD.com.au
>- Find yourself a bargain!
This archive was generated by hypermail 2.1.4 : Sat Sep 07 2002 - 19:36:27 GMT-3