IP SLA tracks fail CLI commands - Cisco ISR 4451+ K9 Security

[varunoberoi]

I have 2 ISPs connected with load balancing configuration, I automate the load share using IP SLA tracks which trigger EEM to run CLI the following CLI commands:

event manager applet ISP_1_DOWN
!no event manager applet ISP_1_DOWN
event track 1 state down
action 1.0 cli command "enable"
action 2.0 cli command "config t"
action 3.0 cli command "no ip route 0.0.0.0 0.0.0.0 dialer 1"
action 4.0 cli command "exit"
action 5.0 cli command ""
action 6.0 cli command "end"
action 7.0 syslog msg "ISP 1 is DOWN!"
exit

event manager applet ISP_1_UP
!no event manager applet ISP_1_UP
event track 1 state up
action 1.0 cli command "enable"
action 2.0 cli command "conf t"
action 3.0 cli command "ip route 0.0.0.0 0.0.0.0 dialer 1"
action 4.0 cli command "exit"
action 5.0 cli command ""
action 6.0 cli command "end"
action 7.0 syslog msg "ISP 1 is UP!"
exit

I am getting the following error repeatedly:

Unable to establish CLI session: 'Embedded Event Manager' detected the 'fatal' condition 'no tty lines available, minimum of 2 required by EEM'

What is the problem?

[Jaderson Pessoa]

Hello, 

try it:

event manager applet ISP_1_UP authorization bypass

event manager applet ISP_1_DOWN authorization bypass

[balaji.bandi]

action 5.0 cli command ""

what is this line ? why empty here ?  remove that line and test it (also clear vty lines)

Looks for me script not ending from VTY lines

show line

show line summary

[MHM Cisco World]

follow

[Dan Frey]

EEM runs like any other user and consumes a tty line just like a normal user.   EEM will not use the last tty line and that is what the message means.  There must be at least 2 tty lines available in order for EEM to run.   

[varunoberoi]

@Dan Frey  Hi Daniel, What is a tty line?

I googled and read about it. But unsure how my commands do not have or have tty lines.

[Georg Pauwen]

Hello,

I think creating more VTY lines could help:

ISR4451#conf t

ISR4451(config)#line vty 0 100

[balaji.bandi]

I have provided the command to look for TTY lines :

Looks to me script does not end from VTY lines

show line

show line summary