[c-nsp] as path filtering in route map policy

[Bruce Pinsky]

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

Alain Cocconi wrote:
| Hello,
|
| I'm trying to do a route selection on a bgp prefix but when I use the
| config below, all the packets are matched by the
| first route-map. Is it possible to use the ip as-path access list in
| this case ?
|

IIRC, Policy based routing does not support using as-path lists as match
criteria.  I believe this excerpt from the cisco docs supports that:

	Although there are many route-map matching options, here you can 		specify
only length and/or ip address.

		?length matches the Level 3 length of the packet.

		?ip address matches the source or destination IP address 			that is
permitted by one or more standard or extended 				access lists.


| tia
|
| interface GigabitEthernet0/3
|  ip address 192.168.100.100 255.255.255.0
|  no ip redirects
|  no ip unreachables
|  no ip proxy-arp
|  ip accounting access-violations
|  ip load-sharing per-packet
|  ip route-cache policy
|  ip route-cache flow
|  no ip mroute-cache
|  ip policy route-map test-out
|  no negotiation auto
|  no cdp enable
| !
| ip as-path access-list 1 permit ^17480$
| !
| access-list 150 permit ip 192.168.68.0 0.0.3.255 any
| !
| route-map test-out permit 10
|  match as-path 1
|  set ip next-hop 192.168.128.213
| !
| route-map test-out permit 20
|  match ip address 150
|  set ip next-hop 192.168.128.209
| !
| route-map test-out deny 30
| !
|
| _______________________________________________
| cisco-nsp mailing list  cisco-nsp at puck.nether.net
| https://puck.nether.net/mailman/listinfo/cisco-nsp
| archive at http://puck.nether.net/pipermail/cisco-nsp/


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

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.2 (MingW32)

iD8DBQFBUM19E1XcgMgrtyYRAp50AKCuZP4sY64+xA/TNFo6k1Qrye1znQCfQlI6
d+zlogDaR4R3pOpgmb5ZPs0=
=jhp8
-----END PGP SIGNATURE-----