why do I get message - tty is now going through its death sequence ?

[AshG]

I have simple EEM applet policy which runs every 10 mins and executes tcl script.

event manager applet testconnection
 event timer cron cron-entry "*/10 * * * *" maxrun 60
 action 010 cli command "enable"
 action 020 cli command "tclsh flash:TestConnection.tcl"

All works fine but in the end I get message : tty is now going through its death sequence

029213: Jun 17 12:50:30.262: %HA_EM-6-LOG: testconnection : DEBUG(cli_lib) : : OUT :
029214: Jun 17 12:50:30.262: %HA_EM-6-LOG: testconnection : DEBUG(cli_lib) : : OUT : 08-isr-1#
029215: Jun 17 12:50:30.262: %HA_EM-6-LOG: testconnection : DEBUG(cli_lib) : : CTL : cli_close called.
029216: Jun 17 12:50:30.262:
029217: Jun 17 12:50:30.262: tty is now going through its death sequence

It seems like EEM is ending abruptly. Do I need to do something for the EEM to end gracefully after finished?

its ISR 3945e with IOS 15.3.2.T2

[Joe Clarke]

This message is fine.  You only see it because you have debugging enabled.  That said, you should not be using EEM to spawn a tclsh script.  That is inefficient.  It would be better to convert the tclsh script to an EEM Tcl policy, and then register that instead of the applet.  This way you are not involving an unneeded subsystem.

[AshG]

Thanks Jospeh,

Can you please guide me on how to convert tcl script to EEM tcl Policy.

tcl script just checks connection to web servers and update IP host entries based on live servers.

[Joe Clarke]

Without seeing the script, I cannot comment on everything that must be done to convert it to EEM Tcl.  But in general, have a look at http://www.cisco.com/c/en/us/td/docs/ios/netmgmt/configuration/guide/12_2sx/nm_12_2sx_book/nm_eem_policy_tcl.html .