From: Joseph Brunner (joe@affirmedsystems.com)
Date: Sun Sep 30 2007 - 22:45:40 ART
Scott, I'm seeing the same behavior required in my real-world deployments of
EEM, check this one...
ip sla monitor 20
type echo protocol ipIcmpEcho 172.28.40.129 source-ipaddr 172.28.40.132
timeout 10
tag testping
frequency 3
track 20 rtr 20
ip route 207.126.90.128 255.255.255.128 172.28.40.129 track 20
event manager applet track
event syslog pattern "%TRACKING-5-STATE: 20 rtr 20 state Up->Down"
action 1.0 cli command "enable"
action 1.1 cli command "configure terminal"
action 1.2 cli command "router bgp 65030"
action 1.3 cli command "no network 207.126.90.128 mask 255.255.255.128"
-----Original Message-----
From: nobody@groupstudy.com [mailto:nobody@groupstudy.com] On Behalf Of
Scott M Vermillion
Sent: Sunday, September 30, 2007 6:28 PM
To: 'Cisco certification'
Subject: OT: EEM and Enable Mode
Hi folks,
I'm mocking up a client-deployed configuration that they're having some
trouble with. They have Embedded Event Manger set to clear all NAT
translations when a certain track object goes down or comes back up. In my
lab, I was not seeing any NAT translations being flushed following a track
object state transition, so I did a 'debug event manager all' to see what I
could see. What it looked like buried in the output was this:
R3>clear ip nat trans *
^
As if the command was being executed from a non-enable prompt. So I added
an action into the EEM of simply 'action .5 cli command "enable"' prior to
my 'action 1.0 cli command "clear ip nat trans *"' and viola! Everything
seems to work.
This strikes me as ludicrous. I had a look through the DocCD and found no
reference to needed to force this. Never having implemented this CLI
command line feature, I don't know if this is normal behavior or not.
Anyone care to share their experiences with this?
Thanks much!
Scott
This archive was generated by hypermail 2.1.4 : Sat Oct 06 2007 - 12:01:17 ART