Cisco Support Community
cancel
Showing results for 
Search instead for 
Did you mean: 
New Member

Applet Script to shutdown interface failing 1/15 times

The following scripts are meant to shutdown the dialer 0 interface if the fa0 interface goes down and vice versa.

track 456 interface FastEthernet0 line-protocol

event manager applet lantrackdown
event track 456 state down
action 1.0 syslog msg "shuts down controller interface in the event that the fa0 interface fails"
action 2.0 cli command "enable"
action 3.0 cli command "config t"
action 4.0 cli command "controller vdsl 0"
action 5.0 cli command "shut"
action 6.0 cli command "end"
action 7.0 syslog msg "controller interface has been shut down"

event manager applet lantrackup
event track 456 state up
action 1.0 syslog msg "re-enables controller interface in the event that the fa0 interface comes back up"
action 2.0 cli command "enable"
action 3.0 cli command "config t"
action 4.0 cli command "controller vdsl 0"
action 5.0 cli command "no shut"
action 6.0 cli command "end"
action 7.0 syslog msg "controller interface has been re-enabled"

 

It currently works on an 887-VA-K9 and an 887-VA-SEC-K9. However roughly once in every 15 times so that we test this, one of the scripts (either lantrackdown or lantrackup) will fail.

 

I am unsure why this is and cannot tell for the debug:

Jul 28 19:52:05 BST: EEM: policy_dir xml builtin: name:_event_type value:211
Jul 28 19:52:05 BST: EEM: policy_dir xml builtin: name:_event_type_string value:track
Jul 28 19:52:05 BST: EEM: policy_dir xml builtin: name:_event_severity value:severity-normal
Jul 28 19:52:05 BST: EEM: policy_dir xml builtin: name:_track_number value:456
Jul 28 19:52:05 BST: EEM: policy_dir xml builtin: name:_track_state value:down
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown: shuts down controller interface in the event that the fa0 interface fails
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : CTL : cli_open called.
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : OUT : You are attempting to connect to a managed device
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : OUT : If you are not an authorised user DISCONNECT IMMEDIATELY
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : OUT :
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : OUT : Router>
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : IN  : Router>enable
Jul 28 19:52:05 BST: %HA_EM-3-FMPD_ERROR: Error executing applet lantrackdown statement 2.0
Jul 28 19:52:05 BST: %HA_EM-6-LOG: lantrackdown : DEBUG(cli_lib) : : CTL : cli_close called.
Jul 28 19:52:05 BST: fh_server: fh_io_ipc_msg: received msg FH_MSG_CALLBACK_DONE from client 19 pclient 1
Jul 28 19:52:05 BST: fh_io_ipc_msg: EEM callback policy lantrackdown has ended with abnormal exit status of 0xFFFFFFFF
Jul 28 19:52:05 BST: EEM: server decrements in use thread: jobid=16 rule id=2 in use thread=0.
Jul 28 19:52:05 BST: fh_schedule_callback: fh_schedule_callback: cc=8984CB68 prev_epc=8A8A051C; epc=0
Jul 28 19:52:05 BST: fh_schedule_policy: prev_epc=0x0; epc=0x0
Jul 28 19:52:05 BST: EEM server schedules scripts
Jul 28 19:52:05 BST: fh_server: fh_io_ipc_msg: received msg FH_MSG_API_CLOSE from client 19 pclient 1
Jul 28 19:52:05 BST: fh_io_ipc_msg: received FH_MSG_API_CLOSE client=19
Jul 28 19:52:05 BST: %LINEPROTO-5-UPDOWN: Line protocol on Interface FastEthernet0, changed state to down

 

An anomalous output of 0xFFFFFFFF does not tell me much and moreover I cannot discern what it is we are doing differently when it fails (we are simply unplugging the fa0 lan cable from the router).

 

Can anyone advise of what might be causing this intermittent problem?

Everyone's tags (3)
1 ACCEPTED SOLUTION

Accepted Solutions
Cisco Employee

This looks like CSCue60804. 

This looks like CSCue60804.  It should be fixed in 15.4(2)T1 for this platform.  The workaround is simply to have the events run again, but that is clearly not ideal.

7 REPLIES
Cisco Employee

What version of code is this

What version of code is this router running?

New Member

router#show event manager

router#show event manager version
Embedded Event Manager Version 4.00
Component Versions:
eem: (rel2)1.0.10
eem-gold: (rel1)1.0.2
eem-call-home: (rel2)1.0.0
Event Detectors:
Name                Version   Node        Type
application         01.00     node0/0     RP
identity            01.00     node0/0     RP
neighbor-discovery  01.00     node0/0     RP
routing             02.00     node0/0     RP
nhrp                01.00     node0/0     RP
track               01.00     node0/0     RP
syslog              01.00     node0/0     RP
resource            01.00     node0/0     RP
cli                 01.00     node0/0     RP
counter             01.00     node0/0     RP
interface           01.00     node0/0     RP
ioswdsysmon         01.00     node0/0     RP
none                01.00     node0/0     RP
oir                 01.00     node0/0     RP
snmp                01.00     node0/0     RP
snmp-object         01.00     node0/0     RP
ipsla               01.00     node0/0     RP
snmp-notification   01.00     node0/0     RP
timer               01.00     node0/0     RP
test                01.00     node0/0     RP
config              01.00     node0/0     RP
env                 01.00     node0/0     RP
nf                  01.00     node0/0     RP
rpc                 01.00     node0/0     RP

router#

 

Cisco Employee

No, what version of IOS is

No, what version of IOS is this?

New Member

Oh sorry. Never hear someone

Oh sorry. Never hear someone refer to the IOS version as the version of code (plus, when I google how to show the version of EEM code the first link is the above command :) )

 

Anyways, version of IOS is as follows:

 

router#sh ver
Cisco IOS Software, C880 Software (C880DATA-UNIVERSALK9-M), Version 15.2(4)M4, RELEASE SOFTWARE (fc2)
Technical Support: http://www.cisco.com/techsupport
Copyright (c) 1986-2013 by Cisco Systems, Inc.
Compiled Thu 20-Jun-13 16:47 by prod_rel_team

ROM: System Bootstrap, Version 12.4(22r)YB5, RELEASE SOFTWARE (fc1)

 

New Member

Wait.... the post I found on

Wait.... the post I found on google is written by you :)

 

Sorry I didn't realise.

Cisco Employee

This looks like CSCue60804. 

This looks like CSCue60804.  It should be fixed in 15.4(2)T1 for this platform.  The workaround is simply to have the events run again, but that is clearly not ideal.

New Member

Hi Joseph,Thank you for your

Hi Joseph,

Thank you for your help. This issue seems to have stabilized. Should it recur I will upgrade the IOS as you suggest.


Regards,
Steve

484
Views
5
Helpful
7
Replies
CreatePlease to create content