Seems like there was a formatting issue in my initial mail. Therefore sending
again.
BR Per
Hi all,
While playing around with PBR,, it seems like matching an as-path access-list
in the PBR route-map actually works!!?? As far as I knew (as documented), only
IP ACL:s and length were the only matchable criterias. Has anyone got any
experience from this (matching other things than IP ACL and length in PBR)?
This is the topology and config (R6 is doing PBR on f0.50.);
R6 is running Version 12.4(16),
upstream
|
R6--f0.50-------BB3
|
f0.30
|
|
BB2(AS2)
R6#sh ip b 199.172.1.0
BGP routing table entry for 199.172.1.0/24, version 10
Paths: (2 available, best #1, table Default-IP-Routing-Table)
Advertised to update-groups:
2
2
150.3.13.254 from 150.3.13.254 (150.3.13.254)
Origin IGP, metric 0, localpref 300, valid, external, best
1
150.1.13.254 (metric 282112) from 150.1.13.254 (199.172.16.1)
Origin IGP, metric 0, localpref 200, valid, external
R6#sh ip ro 150.3.13.254
Routing entry for 150.3.13.0/24
Known via "connected", distance 0, metric 0 (connected, via interface)
Redistributing via eigrp 13, eigrp 100
Advertised by eigrp 100
Routing Descriptor Blocks:
* directly connected, via FastEthernet0.30
Route metric is 0, traffic share count is 1
R6#sh run int f0.50 | i policy
ip policy route-map pbr
R6#sh route-map pbr
route-map pbr, permit, sequence 10
Match clauses:
as-path (as-path filter): 1
Set clauses:
interface Tunnel0
Policy routing matches: 132 packets, 8448 bytes
R6#sh ip as 1
AS path access list 1
permit ^2$
A trace with PBR enabled on R6;
BB3#tr 199.172.1.0
Type escape sequence to abort.
Tracing the route to 199.172.1.0
1 150.2.13.1 0 msec 4 msec 0 msec
2 13.13.6.2 8 msec 4 msec 4 msec
3 150.1.13.254 8 msec 4 msec 4 msec
4 * *
Hop 3 above is beyond the tunnel endpoint:
A trace without PBR on R6;
BB3#tr 199.172.1.0
Type escape sequence to abort.
Tracing the route to 199.172.1.0
1 150.2.13.1 0 msec 4 msec 4 msec
2 150.3.13.254 0 msec 0 msec 4 msec
3 *
It goes straight down to BB2 accordingly to the RIB.
Another trace to another dest behind BB2 that doesn't match as-path acl 1 when
PBR is enabled on R6;
BB3#tr 200.200.200.0
Type escape sequence to abort.
Tracing the route to 200.200.200.0
1 150.2.13.1 0 msec 4 msec 0 msec
2 150.3.13.254 8 msec 4 msec 0 msec
3 150.3.13.254 !H
Think this proves that PBR and as-path ACL actually works...or ??
_________________________________________________________________
Spara, redigera och organisera dina foton enkelt med Photo Gallery!
http://get.live.com/photogallery/overview
