What you have posted shows how you will initiate IP SLA and it looks reasonable. But you have not shown us how you will use IP SLA or where and how it is assigned. Without that we can not see how it would work.
how to configure IP SLA in a routing protocol scenario - that was my question
I understand with static routes it would look like
track 1 rtr 1 reachability
ip route 0.0.0.0 0.0.0.0 x.x.x.x track 1
ip route 0.0.0.0 0.0.0.0 Y.Y.Y.Y 140
Point 2 - Our NMS checks for interfaces up/down but in MPLS cloud scenario it can be interface issue or issue at SP side no reachability. Our idea was to see if IP SLA can support to track interface up/down and reachability
IP SLA route tracking feature is an alternate solution for Routing protocols. When you cannot use a dynamic routing protocol, that where you'd use IP SLA for tracking a static route so that when the remote ip stops pinging, the primay route would automatically failover to the backup.
But in your case, I don't understand why do you want to use IP SLA for a routing protocol? You have OSPF on your primay link and running BGP on the secondary, so if your primary link goes down (even if the interface stays up but the connectivity to other remote router is not there) routing protocol will automatically detect this failure as it would not be able to send or receive Hello packets and bring the OSPF neighborship down and BGP backup route would be installed to start sending the traffic over MPLS.
Really as per me you don't need IP SLA tracking and fyi there is no way to track an IP SLA object anything in a routing protocol config
even for this 2nd point of tracking the interface through NMS, your end goal should be to make sure that Branch office is reachable from HQ at all times.
So even if your NMS software at HQ is not able to reach the MPLS facing interface on the Branch router, regardless of the fact whether it is an interface related issue or SP infra issue, you would get to know that reachability through MPLS is down and you have to take action. You can start by checking the interface on the router, then MPLS cable and then contact SP so that they can check at their end
But if you WANT that instead of NMS alerts, you want that router should generate an alert, only then you would use IP SLA with EEM feature.
Question We run asr9001 with XR 6.1.3, and we have a very long delay to
login w/ SSH 1 or 2 to the device compare to IOS device. After
investigation, the there is 1s delay between the client KEXDH_INIT and
the server (XR) KEXDH_REPLY. After debug ssh serv...
Introduction The purpose of this document is to demonstrate the Open
Shortest Path First (OSPF) behavior when the V-bit (Virtual-link bit) is
present in a non-backbone area. The V-bit is signaled in Type-1 LSA only
if the router is the endpoint of one or ...
Hi, I am seeing quite a few issues with patch install and wanted to
share my experience and workaround to this. Login to admin via CLI, then
access root with the “shell” command Issue “df –h” and you’ll probably
see the following directory full or nearly ...