cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
400
Views
1
Helpful
15
Replies

PBR configuration, "policy routing match 0 packets 0 bytes" Error

Working on PBR on cisco ISR 4331 router, but couldn't able to route as needed to the interface.

michaelgebreegziabher21778_0-1724921176713.pngmichaelgebreegziabher21778_1-1724921288939.png

 

15 Replies 15

You use next hop tracking?

Check track first 

Also did you apply Pbr under correct interface

MHM

Yes, I have configured sla with the track and mapped to the route-map. Also, I have applied on the correct interface where the source IP is originated. But the traffic is not passing to the expected outgoing interface. 

Show track breif <<- share this 

Can I see ip sla and route-map config 

Run

Debug ip policy 

MHM

michaelgebreegziabher21778_0-1724932820371.png

track 10 ip sla 10 reachability
ip sla 10
icmp-echo 10.47.3.X source-interface Port-channelXX
frequency 10
ip sla schedule 10 life forever start-time now

 

 

route-map ISP-INT, permit, sequence 10
Match clauses:
ip address (access-lists): ACL
track-object 10
Set clauses:
ip next-hop verify-availability 10.47.3.X 10 track 10 
Nexthop tracking current: 0.0.0.0
10.47.3.X, fib_nh:0,oce:0,status:0

Policy routing matches: 0 packets, 0 bytes

****** Conf for route-map ************

route-map ISP-INT permit 10
match ip address ACL
match track 10
set ip next-hop verify-availability 10.47.3.X 10 track 10

Hello @michaelgebreegziabher21778 ,

there is a platform dependent part in this kind of route-maps

try to add:

route-map ISP-INT permit 10

set ip next-hop 10.47.3.X

and see what happens

Hope to help

Giuseppe

 

You mean with no match?

Hello @michaelgebreegziabher21778 ,

I mean to add the statement

set ip next-hop 10.47.3..X in the existing configuration without deleting anything

 

Also what kind of interface you are applying the route-map inbound ?

I hope it is a physical routed interface and not a port-channel.

 

Hope to help

Giuseppe

 

debug ip policy <<-

Nothing is shown in the debug ip policy.

Then friend either you not config policy under correct interface 

Or your ACL is wrong <<- show ip access-list (check hit)

Or you config PBR before ACL

So you need to delete PBR abd config it again 

Note:- no need match track 10' track 10 use for verify next-hop only 

MHM

Okay, Let me check it brief and reconfigure it again

Hello
From that route-map output I see no tracking being applied ?

route-map xx
match ip address xx
match track x  < --missing

also can you confirm the next-hop is directly connected or recursive?


Please rate and mark as an accepted solution if you have found any of the information provided useful.
This then could assist others on these forums to find a valuable answer and broadens the community’s global network.

Kind Regards
Paul

Added match track on the route-map, still the same.

The next-hop is a directly connected.

Review Cisco Networking for a $25 gift card