EEM config & Track delay

We have two iBGP peers with their own separate eBGP (Internet) peers.
We use them as an HSRP pair (over an L2 trunk) for our redundant Internet.
I've created an EEM script that will have the "secondary" router track the "primary" router's HSRP interface to ensure it's still up.
If the link goes down, the router immediately removes all of its iBGP static routes to avoid a routing black hole.
When the link comes back up, the secondary router re-adds the iBGP static routes.
The script works fine, but the maximum delay on the ip sla track command has a maximum of 180 seconds.
Since we're talking BGP, this short delay could wreak havoc if an Internet link is flapping or something.
Here's the track command:
track 1 ip sla 1 reachability
default-state up
delay down 30 up 180
I'm trying to think of a way to make it wait longer than 180 seconds. (900 seconds would be ideal to ensure the issue has been resolved before re-establishing the static routes.
Can anyone think of a way to increase the delay using the EEM commands? The track command is too limited here.
Thanks!
Ven

Looks like it's calling the add-ibgp, but it stops after the config t.
scp1001-a5t-3#
*Sep 25 15:26:23.680: %TRACKING-5-STATE: 1 ip sla 1 reachability Up->Down
*Sep 25 15:26:23.680: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : CTL : cli_open called.
*Sep 25 15:26:23.681: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3>
*Sep 25 15:26:23.681: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : IN : scp1001-a5t-3>enable
*Sep 25 15:26:23.691: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3#
*Sep 25 15:26:23.691: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : IN : scp1001-a5t-3#conf t
*Sep 25 15:26:23.801: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : Enter configuration commands, one per line. End with CNTL/Z.
*Sep 25 15:26:23.801: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config)#
*Sep 25 15:26:23.801: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config)#router bgp 27336
*Sep 25 15:26:23.911: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-router)#
*Sep 25 15:26:23.911: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-router)#neighbor 152.179.202.81 shutdown
*Sep 25 15:26:24.021: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-router)#
*Sep 25 15:26:24.021: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-router)#no event manager applet add-ibgp
*Sep 25 15:26:24.131: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config)#
*Sep 25 15:26:24.131: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config)#end
*Sep 25 15:26:24.138: %SYS-5-CONFIG_I: Configured from console by EEM on vty0 (EEM:track-bgp-down)
*Sep 25 15:26:24.141: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : OUT : scp1001-a5t-3#
*Sep 25 15:26:24.141: %HA_EM-5-LOG: track-bgp-down: SCP iBGP static routes deleted due to vlan200 failure
*Sep 25 15:26:24.141: %HA_EM-6-LOG: track-bgp-down : DEBUG(cli_lib) : : CTL : cli_close called.
*Sep 25 15:26:24.141: tty is now going through its death sequence
*Sep 25 15:26:31.530: %BGP-5-ADJCHANGE: neighbor 163.230.254.66 Down BGP Notification sent
*Sep 25 15:26:31.530: %BGP-3-NOTIFICATION: sent to neighbor 163.230.254.66 4/0 (hold time expired) 0 bytes
*Sep 25 15:26:31.530: %BGP_SESSION-5-ADJCHANGE: neighbor 163.230.254.66 IPv4 Unicast topology base removed from session BGP Notification sent
*Sep 25 15:26:47.964: %LINK-3-UPDOWN: Interface GigabitEthernet0/0/1, changed state to up
*Sep 25 15:26:48.964: %LINEPROTO-5-UPDOWN: Line protocol on Interface GigabitEthernet0/0/1, changed state to up
*Sep 25 15:26:47.964: %LINK-3-UPDOWN: SIP0/0: Interface GigabitEthernet0/0/1, changed state to up
*Sep 25 15:26:49.909: %BGP-5-ADJCHANGE: neighbor 163.230.254.66 Up
*Sep 25 15:27:23.680: %TRACKING-5-STATE: 1 ip sla 1 reachability Down->Up
*Sep 25 15:27:23.680: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : CTL : cli_open called.
*Sep 25 15:27:23.681: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3>
*Sep 25 15:27:23.681: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3>enable
*Sep 25 15:27:23.691: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3#
*Sep 25 15:27:23.691: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3#conf t
*Sep 25 15:27:23.701: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : Enter configuration commands, one per line. End with CNTL/Z.
*Sep 25 15:27:23.701: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config)#
*Sep 25 15:27:23.701: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config)#event manager applet add-ibgp
*Sep 25 15:27:23.811: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:23.811: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#event timer countdown time 300
*Sep 25 15:27:23.921: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:23.921: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#action 1.0 cli command enable
*Sep 25 15:27:24.031: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:24.031: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#action 2.0 cli command " config t"
*Sep 25 15:27:24.141: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:24.141: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#action 3.0 cli command " router bgp 27336"
*Sep 25 15:27:24.251: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:24.251: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#action 4.0 cli command " no neighbor 152.179.202.81 shutdown"
*Sep 25 15:27:24.361: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:24.361: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#action 8.0 cli command end
*Sep 25 15:27:24.471: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3(config-applet)#
*Sep 25 15:27:24.471: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : IN : scp1001-a5t-3(config-applet)#end
*Sep 25 15:27:24.474: %SYS-5-CONFIG_I: Configured from console by EEM on vty0 (EEM:track-bgp-up)
*Sep 25 15:27:24.481: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : OUT : scp1001-a5t-3#
*Sep 25 15:27:24.481: %HA_EM-5-LOG: track-bgp-up: SCP iBGP static routes re-added - vlan200 UP
*Sep 25 15:27:24.481: %HA_EM-6-LOG: track-bgp-up : DEBUG(cli_lib) : : CTL : cli_close called.
*Sep 25 15:27:24.481: tty is now going through its death sequence
*Sep 25 15:27:42.058: %HSRP-5-STATECHANGE: GigabitEthernet0/0/1 Grp 1 state Speak -> Standby
*Sep 25 15:32:24.474: %HA_EM-6-LOG: add-ibgp : DEBUG(cli_lib) : : CTL : cli_open called.
*Sep 25 15:32:24.475: %HA_EM-6-LOG: add-ibgp : DEBUG(cli_lib) : : OUT : scp1001-a5t-3>
*Sep 25 15:32:24.475: %HA_EM-6-LOG: add-ibgp : DEBUG(cli_lib) : : IN : scp1001-a5t-3>enable
*Sep 25 15:32:24.485: %HA_EM-6-LOG: add-ibgp : DEBUG(cli_lib) : : OUT : scp1001-a5t-3#
*Sep 25 15:32:24.485: %HA_EM-6-LOG: add-ibgp : DEBUG(cli_lib) : : IN : scp1001-a5t-3# config t
*Sep 25 15:32:44.500: %HA_EM-6-LOG: add-ibgp : DEBUG(cli_lib) : : CTL : cli_close called.
*Sep 25 15:32:46.496: tty is now going through its death sequence

Similar Messages

Audio-tracks delayed

With my *Digi 003 rack* and *Logic Studio Pro 8.0.2* I suddenly have recorded audio-tracks delayed when played back. If I play a guitar right on click and play it back, it is totally out of timing. Never had that one before. When I use the *Apogee Duet Soundcard*, all is working fine. Has anyone any idea what that may be?
Cheers!
Michael

Hi Anthro,
I just repeat this test for you rigth now..
it is very fresh test... in order to have a perfect sync when recording an external instrument with "Software Monitoring" turn to "OFF" (for be able to repeat this test on Logic that usually is used with SW turned to "ON" you must restart Logic or Core Audio before starting the test)
I repeat this test refering to specific Logic setting : *Software Monitoring turn to "OFF"*
(when SW is turn to ON, every external incoming Audio input is recorded in perfect sync with the SMPTE and BPM time)
I have use an External Midi Drum machine as sound source!
see the following pictures:
this is the MIDI object quantize at 1/4:
this is the Audio recording of the MIDI object and the relative coreaudio setting preferences
*software monitoring off*
this is the Audio recording of the same Midi object with a correct Recording Delay Compensation setting.
*software monitoring off*
If you have doubt about this test, feel free to replay me... I hope this should be help you to find a good sync....
in any case... this is not the same for all Audio devices, they can have different driver-hardware adding or less DELAY...there are faster device like Motu 828mk3 and there are not so fast device like as Digidesign core audio drivers that have proprietary security and rigths protection)
however, FOR A PERFECT Sync... i suggest to extend the resolution of the Samples Editor...
bacause some device can be set as 1124 instead 1024 (or different value)
(on My MOtu I get a near to perfect sync around 1009 /1012 Delay
(I hope this post can be helpful also for the people that they +*"cannot believe that"*+ )
Good Luck
fermusic

EEM event track is not supported (version 3.2)

Hello,
I'm replacing a router 2911 by IE3010 (with IP service) and trying to transfer configurations across. I have noticed that on the IE3010 EEM , I can't trigger an event based on Object Tracking.
IE3010(config-applet)#event ?
application Application specific event
cli CLI event
config Configuration policy event
counter Counter event
env Environmental event
gold GOLD event
identity Identity event
interface Interface event
ioswdsysmon IOS WDSysMon event
ipsla IPSLA Event
mat MAC address table event
neighbor-discovery Neighbor Discovery event
nf NF Event
none Manually run policy event
oir OIR event
routing Routing event
rpc Remote Procedure Call event
snmp SNMP event
snmp-notification SNMP Notification Event
snmp-object SNMP object event
syslog Syslog event
tag event tag identifier
timer Timer event
I do have a track that monitors (ICMP-echo) of two IP addresses and I want to do some action when the track is down and this has been working quite well on the 2911. I have found in the IE3010 event detector that tracking event is not available while the same is available in the 2911
Any advise how can I solve this problem and how can I do action based on the status of the tracked object in the IE3010 ?
The software version of the IE3010 is as follows
IE3010 Software (IE3010-IPSERVICESK9-M), Version 15.0(2)SE6, RELEASE SOFTWARE (fc2).
Embedded Event Manager Version 3.20
Component Versions:
eem: (320_rel3)1.0.0
eem-gold: (v320_rel1)1.0.0
eem-call-home: (v320_rel1)1.0.2
Event Detectors:
Name Version Node Type
application 01.00 node0/0 RP
identity 01.00 node0/0 RP
neighbor-discovery 01.00 node0/0 RP
mat 01.00 node0/0 RP
syslog 01.00 node0/0 RP
routing 03.00 node0/0 RP
cli 01.00 node0/0 RP
counter 01.00 node0/0 RP
interface 01.00 node0/0 RP
ioswdsysmon 01.00 node0/0 RP
none 01.00 node0/0 RP
oir 01.00 node0/0 RP
snmp 01.00 node0/0 RP
timer 01.00 node0/0 RP
snmp-object 01.00 node0/0 RP
snmp-notification 01.00 node0/0 RP
ipsla 01.00 node0/0 RP
nf 01.00 node0/0 RP
test 01.00 node0/0 RP
config 01.00 node0/0 RP
env 01.00 node0/0 RP
gold 01.00 node0/0 RP
rpc 01.00 node0/0 RP

I need to track if an IP is up with ICMP, Source IP: 192.168.249.1 Dest IP: 192.168.249.2 on port FastEthernet fa0/19
I do not understand how the weights work here with the UP or Down Status can you please explain. I modified your commands a bit and this is what I got, can you let me know if I am on the right path:
track 10 ip sla 10
delay down 10
track 19 list threshold weight
object 10 weight 70
threshold weight down 30 up 70
authentication mac-move permit
ip sla 10
icmp-echo 10.13.249.2 source-ip 10.13.249.1
timeout 300
frequency 5
ip sla schedule 10 life forever start-time now
ip sla enable reaction-alerts
event manager applet Remote_Site_Up
event syslog pattern "TRACKING-5-STATE: 19 list threshold weight Down->Up"
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "interface FastEthernet0/19"
action 4.0 cli command "no shut"
action 5.0 cli command "end"
event manager applet Remote_Site_Down
event syslog pattern "TRACKING-5-STATE: 19 list threshold weight Up->Down"
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "interface FastEthernet0/19"
action 4.0 cli command "shut"
action 5.0 cli command "end"
This is the status with the show track command:
Track 10
IP SLA 10 state
State is Up
    1 change, last change 00:29:35
Delay down 10 secs
Latest operation return code: OK
Latest RTT (millisecs) 1
Track 19
List threshold weight
Threshold Weight is Up (70/70)
    2 changes, last change 00:29:34
    object 10 weight 70 Up (70/70)
Threshold weight down 30 up 70

EEM config to monitor ping failure

Hello All,
Excellent forum...
I'm hoping someone can help me with my configuration...
I'm looking at setting up EEM on my switch to basically bounce a few selected ports once their is an ICMP failure.
Ideally i'll be conected to the device being monitored, and once their is a failure (ICMP failure), I'll like to trigger a reset on a few ports on the switch .
Anyt help would be greatly appreciated.
B.K

You can use IP SLA, object tracking, and EEM for this. For example:
ip sla 1
icmp-echo 10.1.1.1
ip sla schedule 1 life forever start now
track 1 ip sla 1 reachability
event manager applet ping-watch
event track 1 state down
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "int range gi0/1 - 4"
action 4.0 cli command "shut"
action 5.0 cli command "end"

Track delays before playing - Help please

DSP - 3 One of my tracks seems to delay before playing and I end up with a black screen before it begins. I went back to Final Cut and can't find any problem with it there. All my other tracks start fine. Help please.
Thanks.

Where are you seeing this? On a DVD player or in Simulator? What kind of menu are you using?
The delay on a disc is usually (but not always) related to where the menu is physically located (usually near the spindle hole) compared to the track (anywhere else moving outwards towards the edge of the disc), and the routing tables which DVDSP creates on your behalf when the disc is built. Not all menu/track relationships will see the same delay and you can perhaps reduce it by adding the asset for the troublesome track into another track and setting it apart with a story. Your menu can then point to the assets within the story and it should make a difference.
However, the delay you see on your player will almost certainly be different to that seen on another player - without using a spec level authoring package (or trying it in DVDSP4 where you can move menus into specific VTSs) you may well be stuck with it as it is if adding the asset to an existing track doesn't work.

Recorded track delayed on playback

Just starting out with Logic. I'm using an Aurora 16 with firewire and a Macbook Pro. Tried to record some bass yesterday, and it seemed fine as we were recording, but the recorded track is delayed on playback. What's up with that?

What were your Buffer settings during recording? I assume you didn't monitor through Logic (Software monitoring) but directly through your Interface otherwise you would have noticed the latency while playing. So set the Buffer settings in the Audio prefs to the lowest possible (try 32 or 64) and see if that improves the issue.
Did you record with your Plug In delay compensation to "All" or "tracks+Busses" or off? Try "tracks" or "off" next time and also make sure you don't have a latency inducing plug on your Stereo outs like Adaptive Limiter or alike.

EEM Event Track Question

Hi Experts,
I have the below EEM configured.
No. Class Type Event Type Trap Time Registered Name
1 applet user track Off Mon Sep 8 20:33:19 2014 test
track 1 state down
maxrun 10.000
action 1.0 snmp-trap strdata "TRACK 1 DoWN DETECTED"
My question is:
- Do I need to set the applet to: event manager applet test trap? Do I need this so the trap action would work?
- When the tracked object goes down, will the EEM app continue to generate traps during certain intervals until the tracked object is down? Or will it generate only one trap on the first occurrence the object goes down?
Thanks in advance.

1. No. Just make sure "snmp-server enable traps event-manager" is configured.
2. It will only generate the trap when the object first goes down. It will not generate the trap again until the object comes back up and goes down again.

Recording Multiple Audio Tracks - delay problems in 7.2 Pls HELP

Hi, I'm finding very buggy behavior - if I record across several audio tracks (say 5 mono channels) for longer then 10-15 sec. Logic HANGS for a long time when I'm done with a take - 15-25 secs of the spinning ball icon, and then will redraw and start the dialog box that says it's computing the overview. I'm currently on 7.2.2 but I also tried going back to 7.2.1 and it's still doing this. I have the "faster overview calculation" box un-checked, but it didn't seem to make any difference either way. I also tried this on a new file, same problem -
I also already tried recording to different drives, and selecting and unselecting the 'record limit' dialog in the record destination dialog - I usually have this set to a max recording time of about 7 minutes. None of these changes affected the sluggish behavior.
Anybody else know of this and know of a fix/workaround? I have a session to record tonight with multiple players and this session is going to go like molasses unless I figure this out!
thanx

Hmm, I've never had anything like this. I'm wondering whether it indicates an underlying disk problem?
Try running repair permissions and a disk diagnostic tool if you have it. Are you using an internal or external drive? Try recording to a different drive if you can and see whether the problem persists.
You could also try creating a different user and running Logic under that account, to see if it still shows the same behaviour (if not, then it could be a user permissions issue or something funky with your user account).

CRS IOS XR 4.2.3 ABF IP SLA

Dear all,
I got a problem when running Access-List Based Forwarding (ABF / PBR) with IP SLA.
The Cisco document its says Object Tracking IP SLA with ABF is supported on IOS XR 4.2.1, even with the sample.
http://www.cisco.com/en/US/docs/routers/asr9000/software/asr9k_r4.1/addr_serv/configuration/guide/ipaddr_cg41a9k_chapter1.html#concept_4CBDF391A97345A084853EE73C280FCE
If i looked at Feature Navigator, IP SLA is already supported on IOS XR 4.1.1, with MPLS package software.
But when i configured on CRS, IP SLA cannot be attached on ABF.
Log :
RP/0/RP0/CPU0:CG-P-03(admin)#show install activ sum
Mon Feb 18 17:28:28.023 WIB
Default Profile:
Admin Resources
SDRs:
   Owner
Active Packages:
   disk0:hfr-mini-px-4.2.3
   disk0:hfr-doc-px-4.2.3
   disk0:hfr-services-px-4.2.3
   disk0:hfr-mpls-px-4.2.3
   disk0:hfr-mgbl-px-4.2.3
   disk0:hfr-mcast-px-4.2.3
   disk0:hfr-px-4.2.3.CSCuc41902-1.0.0
   disk0:hfr-px-4.2.3.CSCuc11390-1.0.0
   disk0:hfr-fpd-px-4.2.3
   disk0:hfr-diags-px-4.2.3
RP/0/RP0/CPU0:CG-P-03(config)#track track?
WORD
RP/0/RP0/CPU0:CG-P-03(config)#track track1
RP/0/RP0/CPU0:CG-P-03(config-track)#type rtr 1 rea
RP/0/RP0/CPU0:CG-P-03(config-track)#delay up 5
RP/0/RP0/CPU0:CG-P-03(config-track)#delay down 10
RP/0/RP0/CPU0:CG-P-03(config-track)#comm
Mon Feb 18 17:29:21.213 WIB
RP/0/RP0/CPU0:CG-P-03(config-track)#ipv4 access-list testtrack
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit any nexthop1 ?
ipv4 Enter nexthop1 ipv4 address
vrf   Enter specific VRF Name for this nexthop
<cr>
RP/0/RP0/CPU0:CG-P-03(config)#ipsla
RP/0/RP0/CPU0:CG-P-03(config-ipsla)#operation 1
RP/0/RP0/CPU0:CG-P-03(config-ipsla-op)#type icmp echo
RP/0/RP0/CPU0:CG-P-03(config-ipsla-icmp-echo)#destination add 1.1.1.1
RP/0/RP0/CPU0:CG-P-03(config-ipsla-icmp-echo)#frequency 60
RP/0/RP0/CPU0:CG-P-03(config-ipsla-icmp-echo)#exi
RP/0/RP0/CPU0:CG-P-03(config-ipsla-op)#exi
RP/0/RP0/CPU0:CG-P-03(config-ipsla)#schedule operation 1
RP/0/RP0/CPU0:CG-P-03(config-ipsla-sched)#start-time now
RP/0/RP0/CPU0:CG-P-03(config-ipsla-sched)#life forever
RP/0/RP0/CPU0:CG-P-03(config-ipsla-sched)#commit
Mon Feb 18 17:31:42.496 WIB
RP/0/RP0/CPU0:CG-P-03(config)#ipv4 access-list testtrack
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 ?
A.B.C.D Enter nexthop1 IPv4 address
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 1.1.1.1 ?
nexthop2 Enter another nexthop
<cr>
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 1.1.1.1 track track1
                                                                                   ^
Theres no option track on CLI, even if i specified track, CLI said error / invalid input.
Is there anything to make the ABF IP SLA run on CRS ?
Thanks,
Budi L

Hi Parthiv,
i have already test the configuration, but it cannot work:
RP/0/RP0/CPU0:CG-P-03#sh run | in track
Thu Feb 21 15:22:15.039 WIB
Building configuration...
track track1
RP/0/RP0/CPU0:CG-P-03#sh run track
Thu Feb 21 15:22:18.739 WIB
track track1
type rtr 1 reachability
delay up 5
delay down 10
RP/0/RP0/CPU0:CG-P-03#sh run ip sla
                              ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03#sh run sla
                              ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03#sh run ipsla
Thu Feb 21 15:22:32.501 WIB
ipsla
operation 1
type icmp echo
   destination address 1.1.1.1
   frequency 60
schedule operation 1
start-time now
life forever
RP/0/RP0/CPU0:CG-P-03#sh run access-l
                              ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03#sh run ipv4 access-list
Thu Feb 21 15:22:54.753 WIB
ipv4 access-list ospf_traffic
10 permit ospf any any
RP/0/RP0/CPU0:CG-P-03#conf t
Thu Feb 21 15:22:59.523 WIB
RP/0/RP0/CPU0:CG-P-03(config)#ipv4 access-list testtrack
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any ?
default        Use specified default nexthop on match against this entry
dscp           Match packets with given DSCP value
fragments      Check non-initial fragments
log            Log matches against this entry
log-input      Log matches against this entry, including input interface
nexthop1       Forward to specified nexthop on match against this entry
packet-length Check packet length
precedence     Match packets with given precedence
ttl            match against ttl
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ?
ipv4 Enter nexthop1 ipv4 address
vrf   Enter specific VRF Name for this nexthop
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 track track1 ipv4 1.1.1.1
                                                                       ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ?
ipv4 Enter nexthop1 ipv4 address
vrf   Enter specific VRF Name for this nexthop
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ?
ipv4 Enter nexthop1 ipv4 address
vrf   Enter specific VRF Name for this nexthop
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 ?
A.B.C.D Enter nexthop1 IPv4 address
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 track ?
                                                                            ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 1.1.1.1 ?
nexthop2 Enter another nexthop
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 1.1.1.1 track track1
                                                                                    ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 track1 1.1.1.1
                                                                            ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#10 permit ipv4 any any nexthop1 ipv4 track track1 1.1.1.1
                                                                            ^
% Invalid input detected at '^' marker.
RP/0/RP0/CPU0:CG-P-03(config-ipv4-acl)#exit
RP/0/RP0/CPU0:CG-P-03(config)#exi
RP/0/RP0/CPU0:CG-P-03#

Using IP SLA and EEM to provide 3G backup to ADSL connection on CISCO887VAG+7-K9 router

On a Cisco887VAG+7-K9 router, I want to be able to use IP SLA and EEM to track connectivity to an external address via my ADSL line, if connectivity is UP then I want the 3G interface to be admin shutdown. If connectivity is down, then I want the 3G interface to be activated and connectivity to resume via 3G.
I have configured this and it works apart from one problem. If the config on the router is written to startup memory while the 3G interface is admin shutdown, we subsequently have a problem with the ADSL line and the router is then rebooted, then the EEM does not seem to re-activate the 3G interface so all connectivity is lost until the ADSL is returned to service. i.e. it seems to be the case that if the IP SLA starts off as "Down" then the EEM doesn't take any action. The IP SLA has to have gone into the "up" state before it starts working? Does that make sense and, if so, is there any way round it?
For info, here is my IP SLA and EEM config:
ip sla 1
icmp-echo 8.8.8.8 source-interface dialer2
timeout 60000
ip sla schedule 1 life forever start-time now
track 1 ip sla 1 reachability
ip route 0.0.0.0 0.0.0.0 Dialer2 track 1
ip route 0.0.0.0 0.0.0.0 Dialer1 20
event manager applet 3G-ACTIVATE
event track 1 state down
action 10 cli command "enable"
action 20 cli command "configure terminal"
action 30 cli command "interface Cellular0"
action 40 cli command "no shutdown"
action 50 cli command "end"
event manager applet 3G-DEACTIVATE
event track 1 state up
action 10 cli command "enable"
action 20 cli command "configure terminal"
action 30 cli command "interface Cellular0"
action 40 cli command "shutdown"
action 50 cli command "end"
Any assistance/advice on getting this to work effectively would be appreciated!
Thanks.

Yes, basically, when the tracked object is not reachable on initial router boot, the router doesn’t detect a transition of the tracking object from up to down and therefore does not execute the associated EEM script.
So, in my case, if I have an ADSL fault and the 3G interface has taken over, if the router is subsequently rebooted, all connectivity will be lost because the startup config of the router has the 3G interface as admin down and the EEM script to activate it does not kick in.
I've tried using "default-state up" under the track config but this didn't seem to have any effect - the reachability of my IP SLA was still down after a router reboot with no ADSL connection.
I also tried your script but this gave the errors:
%HA_EM-3-FMPD_ACTION_NOTRACK: bump-track: unable to set state for tracking object number 1; object does not exist or is not a stub-object.
Mar 19 10:23:00.005: %HA_EM-3-FMPD_ERROR: Error executing applet bump-track statement 1.0 %HA_EM-3-FMPD_ACTION_NOTRACK: bump-track: unable to set state for tracking object number 1; object does not exist or is not a stub-object.
Mar 19 10:23:00.005: %HA_EM-3-FMPD_ERROR: Error executing applet bump-track statement 1.0
I'm not sure how to resolve that?
Any further advice would be welcome! Thanks.

IP SLA and Tracking for alerting

Hi,
I configured IP SLAs for sites that connect to the Internet via a 2911 router
Config:
ip sla 199
icmp-echo 4.2.2.2 source-interface GigabitEthernet0/2
ip sla schedule 199 life forever start-time now
ip sla logging traps
track 199 ip sla 199
delay down 120 up 120
Works great - sends a syslog message to the Solarwinds box and message sets off an email alert.
We have a couple of smaller sites that connect to the Internet via a 5510. I'm trying to accomplish the same thing but, it doesn't seem to have the options to set a "delay down and delay up"
Below seems to be my only option:
"track 199 rtr 199 reachability"
Will this tracking-config log the ping fail and if so, is there a way to delay the logging for 120 secs - for Up and Down events?
Thanks, Pat

Hello Pat,
Have you tried entering the command "track 199 rtr 199 reachability"
The prompt should look like this after:
Router(config-track)#
Here you should be able to enter the command "delay down 120 up 120" to my recollection.

ASR 1002-X HRSP Object Tracking

Hello
I have the following config in place. I want to make sure my HSRP is tracking to be affective.
Please review and advise.
track 1 ip route (ISP PER ip address) 255.255.255.252 reachability
interface GigabitEthernet0/0/5
description Inside_DMZ_3750
ip address 10.27.254.3 255.255.255.0
standby 1 ip 10.27.254.1
standby 1 priority 150
standby 1 preempt
standby 2 ip 10.27.254.2
standby 2 priority 90
standby 2 preempt
speed 1000
no negotiation auto
I have tried to add standby track 1 statements to HSRP config, however they do not show in display.
   standby 1 track 1 ?
   standby track 1 ?

1 more question
I am using this track command "track 1 ip route 1.1.1.9 255.255.255.252 reachability
is there anything else I should add to this:
ASR1002x(config-track)#?
Tracking instance configuration commands:
default Set a command to its defaults
delay    Tracking delay
exit     Exit from tracking configuration mode
ip       Tracking IP configuration subcommands
no       Negate a command or set its defaults

EEM in an EEM

The requirement is when the tracking object 12 is down, execute/create another event called reset-modem and it recursively run once every 60 seconds, until the tracking object 12 is up.
I’ve managed to come up with this configuration. Somehow Action 6.0 in the first EEM does not seem to be taken. I am think it could be related to the "" quotations. Can someone advise?
event manager applet track-down
event track 12 state down
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "event manager applet reset-modem"
action 4.0 cli command "event timer watchdog time 60"
action 5.0 cli command "action 1.0 cli command enable"
action 6.0 cli command "action 2.0 cli command test cellular 0 modem-power-cycle"
action 7.0 cli command "end"
event manager applet track-up
event track 12 state up
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "no event manager applet reset-modem"
action 4.0 cli command "end"

Here is what I got. I still believe it is because the action inside an action does not know where the actual commands starting from. I tried puting double quotes, it did not take the config.
track-down : DEBUG(cli_lib) : : IN : Router>enable
track-down : DEBUG(cli_lib) : : OUT : Router#
track-down : DEBUG(cli_lib) : : IN : Router#config t
track-down : DEBUG(cli_lib) : : OUT : Enter configuration commands, one per line. End with CNTL/Z.
track-down : DEBUG(cli_lib) : : OUT : Router(config)#
track-down : DEBUG(cli_lib) : : IN : Router(config)#event manager applet reset-modem
track-down : DEBUG(cli_lib) : : OUT : Router(config-applet)#
track-down : DEBUG(cli_lib) : : IN : Router(config-applet)#event timer watchdog time 60
track-down : DEBUG(cli_lib) : : OUT : Router(config-applet)#
track-down : DEBUG(cli_lib) : : IN : Router(config-applet)#action 1.0 cli command enable
track-down : DEBUG(cli_lib) : : OUT : Router(config-applet)#
track-down : DEBUG(cli_lib) : : IN : Router(config-applet)#action 2.0 cli command test cellular 0 modem-power-cycle
track-down : DEBUG(cli_lib) : : OUT : ^
track-down : DEBUG(cli_lib) : : OUT : % Invalid input detected at '^' marker.
track-down : DEBUG(cli_lib) : : OUT :
track-down : DEBUG(cli_lib) : : OUT : Router(config-applet)#
track-down : DEBUG(cli_lib) : : IN : Router(config-applet)#end

SNMP traps for tracking objects

Hi ,
I have the track objects configured as "boolean or" on my router. I want to configure to send SNMP traps when the "track 202" is down.
I know we can configure SNMP traps for IP SLA. Can we configure for the track as well ?. Below is the track CONFIG.
track 200 rtr 200 reachability
delay down 12
track 201 rtr 201 reachability
delay down 12
track 202 list boolean or
object 200
object 201
Thanks

Hi Rolf,
Thanks for the information. It helped me.
I have configured the trigger event to use the track instead insted of the syslog. And it send the traps to the server.
sysUpTime.0 = 1805405563
snmpTrapOID.0 = cEventMgrMIB.0.2
ceemHistoryEventEntry.2.3 = 211
ceemHistoryEventEntry.3.3 = 0
ceemHistoryEventEntry.4.3 = 0
ceemHistoryEventEntry.5.3 = 0
ceemHistoryEventEntry.6.3 =
ceemHistoryEventEntry.7.3 = applet: TRACK_SNMP_TRAP
ceemHistoryEventEntry.9.3 = 0
ceemHistoryEventEntry.10.3 = 0
ceemHistoryEventEntry.11.3 = DOWN
Cheers!
Win

Problem with STEREO track

hi everyone.
this is a really dumn question since i used to do this all the time is Sonar.
i recorded some vocals and it only recorded in one channel. i could always hit the infinity button to make it mono so i can hear it on both speakers. however, isn't there some effect i can add to get sound on both channels and keep it the stereo track? i'm using the tascam us-122 as an interface and for some reason it only allows you to record on either the L or R. not both of them at the same time. any ideas?

Next time record the mic on two seperate tracks and set the track delay to taste on one of the tracks. Or -quick fix, copy the region to another audio track and set the track delay as above. Use pitch changer to drop or raise the pitch one cent or two (keep it subtle or it will ruin the vocal track). Next ime, you could also use two mics, one a condenser for direct (or ribbon or tube) and a dynamic pointed slightly off center (just becareful to watch for phase issues) small dead rooms work best because they minimize reflections and capture the "dry sound" More track delay can always be added to spread the stereo effect. I find that the spreader plug-ins are good for instruments but deadly to vocals. Your lead vocals have to be kept pure unless you are distorting on purpose. Megabucks are spent on mics and vocal processors by the larger studios for just this purpose. Two or three mics are always better than artificial effects. Try using your best mic in the usual place and set two ambient mics panned hard L/R - watch the phase and enjoy

EEM config & Track delay

Similar Messages

Maybe you are looking for