From: Richard Geiger (geiger_rich@xxxxxxxxxxx)
Date: Mon Jan 07 2002 - 02:34:37 GMT-3
Yes! You got it!
I have tried tagging the route as with the table feature. The tag works but
when I try to manipulate it with the local-policy route-map
all packets are matched.
I can get it to work with the next hop statement,
set ip next-hop 2.2.2.2 1.1.1.1
but if R2 goes down it does not use the next hop, I have tried evry
combination on this with CDP turned on and the validation feature in the new
OS and it doesn't work.
I am guessing that you could place a unique admin distance on the route and
then work from there.............
>From: "Joe Hsieh" <joe.hsieh@networkplus.com>
>To: "Richard Geiger" <geiger_rich@hotmail.com>, <ccielab@groupstudy.com>
>Subject: RE: BGP Help 2 days untill Lab
>Date: Mon, 7 Jan 2002 00:26:59 -0500
>
>Richard,
>
>I do not think this will work. Reason:
>
>R3 will never pass iBGP routes it learn from R1 to R2. ---(ibgp rules)
>
>So, there is no way you can let R2 to route through R3 using BGP route
>info.
>
>If I am right, "sh ip bgp" on R2, you should get routes from R1 only.
>
>Joe Hsieh
>
>-----Original Message-----
>From: nobody@groupstudy.com [mailto:nobody@groupstudy.com]On Behalf Of
>Richard Geiger
>Sent: Sunday, January 06, 2002 11:42 PM
>To: ccielab@groupstudy.com
>Subject: BGP Help 2 days untill Lab
>
>
>The senerio is that you have 1 BGP external router AS100 connected to an
>internal router AS999. You are using the next hop command because you are
>not using IGP for the outside route.
>
> AS100 lo0 10.10.10.1/24
> |
> AS999 -R1
> / \
> AS999-R2 --- As999 -R3
>
>All three of the internals are peered to each other.
>R2 and R3 both show the next hop to 10.10.10.0 to be the Loopback
>on R1
>
>As there is only one path local-pref,weight, as-path won't help here.
>How do you tell R3 to use a path through R2 to Reach 10.10.10.1
>
>
>
This archive was generated by hypermail 2.1.4 : Thu Jun 13 2002 - 10:56:18 GMT-3