Cisco – Event manager applet not getting recognized for Cisco ASA ver8.0

ciscocisco-asacisco-eemfirewall

I need help as Event manager applet not getting recognized for Cisco ASA ver8.0. But for cisco ASA ver 9.6 it is working properly. Please advise

BnglASA/pri/act(config)#Event manager applet backupconfig
BnglASA/pri/act(config-applet) # description "Monthly backup of ASA" 
BnglASA/pri/act(config-applet) # event timer watchdog time 108000
BnglASA/pri/act (config-applet #action 1 cli command "copy /noconfirm running-config ftp://utiftp:v7V5fasffas@10.X.X.X/"
BnglASA/pri/act(config-applet) #output none

Best Answer

The feature was introduced in version 9.2.1:

Release Notes for the Cisco ASA Series, 9.2(x)

We introduced or modified the following commands: event manager applet, description, event syslog id, event none, event timer, event crashinfo, action cli command, output, show running-config event manager, event manager run, show event manager, show counters protocol eem, clear configure event manager, debug event manager, debug menu eem.

-and-

ASA Embedded Event Manager Configuration Example

This document describes Embedded Event Manager (EEM), which is a troubleshooting tool that was added in Adaptive Security Appliance (ASA) Version 9.2(1). The functionality is similar to Cisco IOS? based EEM. It is a powerful way to run CLI commands based on ASA events (syslogs) and save the output. This document covers an introduction to the feature as well as some example EEM applets.

Related Solutions

Cisco ASA-5505 – Inside Interface Not Recognized

After reading this documentation and executing the following commands:

ciscoasa# conf t
ciscoasa(config)# interface vlan X
ciscoasa(config-if)# nameif inside
INFO: Security level for "inside" set to 100 by default.
ciscoasa(config-if)# security-level Y
ciscoasa(config-if)# ip address Z 255.255.255.0
ciscoasa(config-if)# no shutdown
ciscoasa(config-if)# end

interfaces were available:

ciscoasa# conf t
ciscoasa(config)# nat (?

configure mode commands/options:
Current available interface(s):

  inside  Name of interface VlanX

and the commands specified in the question could be executed.

Cisco ASA 5505 – VPN not able to access certain network

I had to make a similar change recently. I needed to add two additional subnets. Though I used CLI rather than ASDM. With version 9.1, I created some new objects for the subnets and then it was just a matter of adding the additional subnets to the split-tunnel ACL (if used) as well as adding additional NAT rules.

For example:

object network {REMOTE_VPN_USER_SUBNET}
 subnet 10.0.1.0 255.255.255.0
object network {EXISTING_VPN_ACCESSIBLE_SUBNET_1}
 subnet 10.0.2.0 255.255.255.0
object network {NEW_VPN_ACCESSIBLE_SUBNET_2}
 subnet 10.0.3.0 255.255.254.0
object network {NEW_VPN_ACCESSIBLE_SUBNET_3}
 subnet 10.0.4.0 255.255.255.0

split-tunnel-network-list value {YOUR_SPLIT-TUNNEL_LIST}
access-list {YOUR_SPLIT-TUNNEL_LIST} standard permit 10.0.1.0 255.255.255.0 
access-list {YOUR_SPLIT-TUNNEL_LIST} standard permit 10.0.2.0 255.255.255.0 
access-list {YOUR_SPLIT-TUNNEL_LIST} standard permit 10.0.3.0 255.255.255.0 

nat (RELEVANT_INTERFACE_OR_VLAN_NAME,outside) source static {EXISTING_VPN_ACCESSIBLE_SUBNET_1} {EXISTING_VPN_ACCESSIBLE_SUBNET_1} destination static {REMOTE_VPN_USER_SUBNET} {REMOTE_VPN_USER_SUBNET} no-proxy-arp route-lookup
nat (RELEVANT_INTERFACE_OR_VLAN_NAME,outside) source static {NEW_VPN_ACCESSIBLE_SUBNET_2} {NEW_VPN_ACCESSIBLE_SUBNET_2} destination static {REMOTE_VPN_USER_SUBNET} {REMOTE_VPN_USER_SUBNET} no-proxy-arp route-lookup
nat (RELEVANT_INTERFACE_OR_VLAN_NAME,outside) source static {NEW_VPN_ACCESSIBLE_SUBNET_3} {NEW_VPN_ACCESSIBLE_SUBNET_3} destination static {REMOTE_VPN_USER_SUBNET} {REMOTE_VPN_USER_SUBNET} no-proxy-arp route-lookup

Best Answer

Related Solutions

Cisco ASA-5505 – Inside Interface Not Recognized

Cisco ASA 5505 – VPN not able to access certain network

Related Topic