No, I didnt mention about creating default route. It is not interfering with routing table at all. All traffic where the route-map is applied, if it matches the route-map (which is match anything), router will set the next hop of those packets to be x.x.x.x or y.y.y.y depending on circumstances. There's no routes involved here.
If you take out the track commands your PBR will fail (policy based routing). You are doing source based routing with PBR not destination as normal.
The track commands are there so that you can ensure with your PBR that you are not going to black hole your traffic.
If none of your next hop's are available and tracking is in a down state for both, all traffic will be treated as normal.
Its kind of like your ON OFF switch for PBR.
With your PBR all traffic is going to next-hop x.x.x.x first, what happens with x.x.x.x fails? If you didnt have ip sla and tracking, your router would still try and send to x.x.x.x but would never realise that its dead - with tracking and verify-availability it will turn the PBR OFF for that particular rule (set). So without this, your traffic is essentially blackholed. In your case you have a secondary y.y.y.y next hop. If this fails then the backup is to use the routing table.
Your track commands are tracking ip sla 1 and 2 respectively. If you was to remove this configuration, your next hop's would not be tracked or monitored for 'up' or 'down' state.
Hope this explains better
Please rate useful posts & remember to mark any solved questions as answered. Thank you.
Please rate useful posts & remember to mark any solved questions as answered. Thank you.
