Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for
- Cisco Community
- :
- About andrewfkay
Stats
Member since
03-14-2006
7
Posts
0
Helpful
0
Solutions
07-16-2012
04:10 AM
Hi Joseph, I have made the change but I'm still having problems. I get the following message: %HA_EM-3-FMPD_UNKNOWN_ENV: fh_parse_var: could not find environment variable: _track_state Also, it creates the applet RE_SHUT_FA0 but I would expect it to be removed after applet has run. It remains in the running config. Please add explanation of any changes as I'm an EEM beginner and I'd like to understand the config. Thanks Andrew
... View more
07-12-2012
07:42 AM
Ok, my config now looks like this and I'm getting the following error message: event manager environment q " event manager applet SHUT_FA0 event timer countdown time 60 action 0.0 cli command "enable" action 1.0 cli command "conf t" action 2.0 cli command "interface fa0" action 3.0 cli command "shut" action 4.0 cli command "end" event manager applet NO_SHUT_FA0 event timer cron cron-entry "37 15 * * 0-6" action 0.0 cli command "enable" action 1.0 cli command "conf t" action 2.0 cli command "interface fa0" action 3.0 cli command "no shut" action 4.0 cli command "event manager applet RE_SHUT_FA0" action 4.1 cli command "event timer countdown time 60" action 4.2 cli command "action 1.0 if $_track_state eq down" action 4.3 cli command "action 1.1 cli command enable" action 4.4 cli command "action 1.2 cli command $q config t$q" action 4.5 cli command "action 1.3 cli command $q interface fa0$q" action 4.6 cli command "action 1.4 cli command shut" action 4.7 cli command "action 1.5 cli command $q no event manager applet RE_SHUT_FA0$q" action 4.8 cli command "action 1.6 end" action 4.9 cli command "end" event manager applet RE_SHUT_FA0 event timer countdown time 60 ! Jul 12 14:37:00.108: %HA_EM-3-FMPD_UNKNOWN_ENV: fh_parse_var: could not find environment variable: _track_state Jul 12 14:37:00.108: %HA_EM-3-FMPD_ERROR: Error executing applet NO_SHUT_FA0 statement 4.2 Jul 12 14:37:00.108: %HA_EM-4-FMPD_NO_ACTION: No action configured for applet RE_SHUT_FA0 Any ideas?
... View more
07-11-2012
06:47 AM
Ok, I've got a bit further with the below config but it seems to end at the 'wait 60' and not go any further. Any ideas? ! event manager applet SHUT_FA0 event track 100 state down action 0.0 cli command "enable" action 1.0 cli command "conf t" action 2.0 cli command "interface fa0" action 3.0 cli command "shut" action 4.0 cli command "end" ! event manager applet NO_SHUT_FA0 event timer cron cron-entry "20 14 * * 0-6" action 0.0 cli command "enable" action 1.0 cli command "conf t" action 2.0 cli command "interface fa0" action 3.0 cli command "no shut" action 4.0 cli command "end" action 4.5 wait 60 action 5.0 track read 100 action 5.5 if $_track_state eq down action 6.0 cli command "enable" action 6.5 cli command "conf t" action 7.0 cli command "interface fa0" action 7.5 cli command "shut" action 8.0 end !
... View more
07-11-2012
02:25 AM
Hi, I have confiugred EEM to track an IP SLA and shut interface Fa0 if it fails. Then, at 23:00 each day (least disruptive to user traffic) open the Fa0 interface again. I've got this part working fine except I want it to shut the interface down again if the interface remains down once it has been reopened. At the moment, I don't think it's working because the track doesn't change state from up to down and therefore stays down. Any ideas how to get this working (I'm new to EEM). Thanks Andrew Config: track 100 rtr 99 reachability delay down 5 up 5 ! ! ip sla 99 icmp-echo 10.51.145.3 source-interface fa0 frequency 10 ip sla schedule 99 life forever start-time now ! ! event manager applet SHUT_FA0 event track 100 state down action 0 cli command "enable" action 1 cli command "conf t" action 2 cli command "interface fa0" action 3 cli command "shut" action 4 cli command "end" ! event manager applet NO_SHUT_FA0 event timer cron cron-entry "00 23 * * 0-6" action 0 cli command "enable" action 1 cli command "conf t" action 2 cli command "interface fa0" action 3 cli command "no shut" action 4 cli command "end" !
... View more
- Tags:
- eem
Labels:
06-21-2012
04:11 AM
Hi, NAT overload would change the source of the packets. I'm trying to get the users (10.0.0.0/24) to target 192.168.1.1 and this be changed to 172.16.1.1 by nat or any other means. This is because the users already have 172.16.1.1 on their network, hence the ip address conflict. Hope this clarifies it a little. Thanks Andrew
... View more
06-21-2012
03:29 AM
Hi, Due to ip address confliction issues I am trying to change the destination address of traffic hitting my router when sourced from a 3rd party router. So, if traffic sourced from 10.0.0.0/24 from 3rd party router targets a loopback on my router, lets say Lo1 - 192.168.1.1/32 can I then modify the destination to 172.16.1.1 and then forward the traffic further into my network where the server on 172.16.1.1 lives. If it's possible to nat the source to 192.168.1.1 also that would be great. I am using 1800 routers and statics for the routing. Is this possible? This is very roughly the setup (missing the /30 networks between the routers) 10.0.0.0/24 <-->Lo1 (192.168.1.1/32) <--> Server 172.16.1.1 Thanks Andrew
... View more
- Tags:
- destination_nat
- nat
Labels:
07-16-2012
Hi Joseph,I have made the change but I'm still having problems. I get
the following message:%HA_EM-3...
07-12-2012
Ok, my config now looks like this and I'm getting the following error
message:event manager environm...
07-11-2012
Ok, I've got a bit further with the below config but it seems to end at
the 'wait 60' and not go any...
07-11-2012
Hi,I have confiugred EEM to track an IP SLA and shut interface Fa0 if it
fails. Then, at 23:00 each ...
06-21-2012
Hi,NAT overload would change the source of the packets. I'm trying to
get the users (10.0.0.0/24) to...
Public Statistics
| Date Registered | 03-14-2006 06:26 AM |
| Date Last Visited | 08-08-2018 12:02 AM |
| Total Messages Posted | 7 |
