cancel
Showing results for 
Search instead for 
Did you mean: 
cancel
1783
Views
0
Helpful
1
Replies

Different behaviour of EEM, same chassis, same IOS

lmcruzmir
Level 1
Level 1

Scenario: 2x7201, both running... c7200p-advipservicesk9-mz.151-4.M6.bin

Code applied to both...

event manager applet foo

event none

action 1.0 cli command "enable"

action 1.1 cli command "terminal exec prompt timestamp"

action 1.2 cli command "sh ip nat statistics | redirect tftp://10.255.255.1/NAT-HITS.$_event_pub_sec"

Result:

Router1...

rt1#sh run | b foo

event manager applet foo

event none

action 1.0 cli command "enable"

action 1.1 cli command "terminal exec prompt timestamp"

action 1.2 cli command "sh ip nat statistics | redirect tftp://10.255.255.1/NAT-HITS.$_event_pub_sec"

!

end

Router2...

rt2#sh run | b foo         

event manager applet foo

event none

action 1.0 cli command "enable"

action 1.1 cli command "terminal exec prompt timestamp"

action 1.2 cli command "sh ip nat statistics | redirect tftp://10.255.255.1/NAT-HITS."

!

end

The var "$_event_pub_sec" is not recognized but router2 due  the command "shell processing full".

So, is there any way to make IOS shell compatible with that kind of vars?

1 Accepted Solution

Accepted Solutions

Joe Clarke
Cisco Employee
Cisco Employee

You can configure this successfully if you disable shell processing full, configure the applet, then re-enable shell processing full.  The variable should stick then.

View solution in original post

1 Reply 1

Joe Clarke
Cisco Employee
Cisco Employee

You can configure this successfully if you disable shell processing full, configure the applet, then re-enable shell processing full.  The variable should stick then.

Getting Started

Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: