We have a dual MPLS network. I have multiple alerts configured through tracking objects and event manager applets. We receive routes from MPLS1 on router 1, and routes from MPLS2 go to router 2. There is also a link between the two routers so that if we lose a route on router 1, weighted static routes will send the traffic over to router 2 instead.
I have tracking objects configured to monitor reachability to each destination subnet on the MPLS, but the tracking object never goes down when the weighted static route is installed in the routing table.
track 1 ip route 10.150.10.0 255.255.255.0 reachability
ip route 10.150.10.0 255.255.255.0 10.250.250.2 250
event manager applet PRIMARY-REACHABILITY-DOWN event track 1 state down
(another config line that sends an email to our mail relay)
event manager applet PRIMARY-REACHABILITY-UP event track 1 state up (another config line that sends an email to our mail relay)
The "show track" information is listed below. When the BGP route goes away, the reachability state stays up, but it changes from "(BGP)" to "(static)"
R1#show track 1 Track 1 IP route 10.150.10.0 255.255.255.0 reachability Reachability is Up (BGP) 25 changes, last change 20w6d First-hop interface is GigabitEthernet0/0/1 Tracked by: Static IP Routing 0 EEM 2495244088 EEM 2495245448
R1#show track 1 IP route 10.150.10.0 255.255.255.0 reachability Reachability is Up (static) 25 changes, last change 20w6d First-hop interface is GigabitEthernet0/0/2 Tracked by: Static IP Routing 0 EEM 2495244088 EEM 2495245448
Is there any way to configure tracking to pay attention to the change from BGP to static and vice versa?
... View more
Another solution to this is to use traceroutes. That way the router's CPU will have to process the packet in order to decrement the TTL value, and the traffic will show up in the debug. traceroute <destination ip> You can also modify the probe value to send more than 3 packets to each router in the path. traceroute <destination ip> probe 10
... View more