[c-nsp] route-map behavior with policy routing

[Bruce Pinsky]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Paul Stewart wrote:
> Relating to this same post...
> 
> I have been trying to get PBR running with a multi-homed BGP setup
> here....
> 
> route-map inbound-trio permit 5
>  match as-path 100
>  set ip next-hop 67.29.145.1
> !
> route-map inbound-trio permit 10
>  match as-path 21
>  set local-preference 150
> !
> route-map inbound-trio permit 20
>  set local-preference 100
> 
> AS-PATH 100 is setup to match one particular AS like this:
> 
> ip as-path access-list 100 permit ^23252$
> 
> AS-PATH 21 statement works great to match "close to us" AS's and give
> them a higher local-pref .. But I want to explicitly prefer our path to
> AS23252 using AS-PATH 100 via our BGP peer (67.29.145.1 is far side of
> the point to point to the BGP peer we want to prefer).
> 
> Why does this not work and is there a better way to do this?
> 

I don't believe you can change the next-hop inbound in this manner.

Why not just set the local-pref (or weight) in permit 5 to make those
routes better?

- --
=========
bep

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.4 (MingW32)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org

iD8DBQFE7ftVE1XcgMgrtyYRAuOGAJ4kL0FCMx8de1iGAF71rq0h+6mw/wCfbxBm
nSXwjh9uLq/oBsRKnHrqq/A=
=lSQM
-----END PGP SIGNATURE-----