I have not configured IP SLA object tracking on nexus OS before and its looks a bit confusing. Can someone help me interpret the following configuration?

This example shows that object tracking is configured for PBR:

! Configure and schedule IP SLA operations
ip sla 1
ip sla schedule 1 life forever start-time now
ip sla 2
ip sla schedule 2 life forever start-time now
ip sla 3
ip sla schedule 3 life forever start-time now
ip sla 4
ip sla schedule 4 life forever start-time now
ip sla 5
ip sla schedule 5 life forever start-time now
! Configure Object Tracking to track the operations 
track 1 ip sla 1 reachability
track 2 ip sla 2 reachability
track 3 ip sla 3 reachability
track 4 ip sla 4 reachability
track 5 ip sla 5 reachability
! Configure ACL
ip access-list standard ACL
    permit ip
! Configure PBR policing on the router
route-map PBR
    match ip address ACL
    set ip next-hop verify-availability track 1
    set ip next-hop verify-availability track 2
    set ip next-hop verify-availability track 3
! Apply PBR policy on the incoming interface of the router.
interface ethernet 0/0
 ip address
    ip policy route-map PBR

Lets focus on object tracking 1 -- Does it mean as long as TRACK 1 is valid, verify and use as the next hop for the ACL for the routing (ignoring whatever is in the current route table)?

  • Yes, that is correct, if you remove the word "verify" from your question. The track object (Track1) does the actual "verification"
    – Ron Trunk
    Jan 24, 2020 at 18:15
  • Thx Ron, I would mark your answer as the "answer" however, it is in the comments section. Can I also use this without PBR in Nexus OS and use the track commands along with the default static route? Jan 24, 2020 at 18:32


Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Browse other questions tagged or ask your own question.