I'm sorry, what version of code is this? This should not be possible in the latest versions of EEM 2.4 and later. I committed the fix to prevent this via CSCso98512 - Running EEM scripts should be terminated when removed from the config. After this change, when the policy is unregistered it should be forcibly killed similar to how the maxrun timer kills a policy.
The code was changed again to allow policies to continue to run because of the common use case of unregistering the policy from itself then doing some other cleanup. So in very new versions of code, this behavior is expected. Though it should be killable with the scheduler clear command.
You should see the policy terminate on unregistering it in this release. However, I have seen cases where this did not work if the policy enters a blocking state. One way that can happen is reading from a socket. In these cases, the only way to remove the policy was to reload. Even a maxrun expiration wouldn't work since the policy is blocked. If it were to try and execute another instruction, it would terminate, but since it won't, then it never terminates.
[toc:faq]The ProblemOn traditional switches whenever we have a trunk
interface we use the VLAN tag to demultiplex the VLANs. The switch needs
to determine which MAC Address table to look in for a forwarding
decision. To do this we require the switch to do...
[toc:faq]Introduction:Netdr is a tool available on a RSP720, Sup720 or
Sup32 that allows one to capture packets on the RP or SP inband. The
netdr command can be used to capture both Tx and Rx packets in the
software switching path. This is not a substitut...
IntroductionOSPF, being a link-state protocol, allows for every router
in the network to know of every link and OSPF speaker in the entire
network. From this picture each router independently runs the Shortest
Path First (SPF) algorithm to determine the b...