EEM Policy that removes itself then does a 'write mem'
I have the following EEM Policy that I thought would remove itself then perform a 'write mem' but the policy seems to terminate at the point it removes itself from running config without the final 'write mem', I am running the below EEM version which I have read will no longer run to completion after the policy removes itself to prevent runaway policies, is there a way to achieve the final 'write mem' after policy removal, if it doesn't save to startup it will run every time the router reboots.
Embedded Event Manager Version 3.20 Component Versions: eem: (320_rel2)2.0.3
This is actually a pretty cool feature, i didn't even know it existed until I was looking for a solution to advertise a subnet (prefix in BGP talk), only if a certain condition existed. This is exactly what conditional advertisements does
j ai une question j ai achete un routeur cisco 887VA-k9 , je le configuré avec la configuration ci- dessous
si je le lier avec mon pc portable sur l un de ses ports directement ça marche toute est bien ( la connexion internet + m...
Attached policy provides CLI access to the Cisco 4G router over text messaging. Two files are in the attached .tar file:
2. PDF with instructions on how to load and use the .tcl file.