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?
