Has any deployed a EEM script that extends the delay times for tracked objects beyond the Cisco 180 sec max? See attachment for details. Not experience at EEM scripting, just trying some things. Any suggestions or link that might help?
You're most of the way there. Using a tracking stub will do what you need.
First, you define your IP SLA and tracking object, which you've already done, but add an additional track:
ip sla 10
ip sla schedule 10 life forever start-time now
track 10 ip sla 10 reachability
track 20 stub-object
Once this is done, you can run two EEM scripts with trigger delays to set the tracking stub's status based on the IP SLA tracking object.
event manager applet DELAY_UP
event track 10 state up
trigger delay 3600
action 1.0 track set 20 state up
event manager applet DELAY_DOWN
event track 10 state down
trigger delay 10
action 1.0 track set 20 state down
This will set the tracking stub based on the delays defined in the EEM applets. Reference the tracking stub instead of the IP SLA tracking object and you should be all set.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...