This issue is due to the presence of Cisco bug ID CSCsh13946.
In this issue, the modification of an access-list that has multiple entries and is tied to a NAT statement can cause the central processing unit (CPU) usage to be high for an extended period of time, which results in packet loss, triggers failover, and so forth.
This issue is typically seen when an access-list that references several object-groups exists in the configuration. When this access-list is edited in order to include more elements that reference additional object-groups, the number of access-list elements grows substantially. When this type of access-list is tied to a NAT statement and the ACL edits are made, the CPU can spike for a few minutes.
The workaround for this issue is to modify the access-lists applied to NAT statements so that the number of elements stays as low as possible.
Note: In order to minimizethe impact, make all of these changes during maintenance windows.
This issue is resolved in these PIX/ASA versions:
In order to completely resolve this issue, downgrade or upgrade to any of the suggested PIX/ASA software versions from Cisco Downloads.
I am successfully backing up running-config using Embedded Event Manager: event manager applet Backup-Configevent timer absolute time 1:00:00action 0 cli command "copy /noconfirm running-config tftp://guru/backups/asa-x-vpn-config-latest"output file ...
Hi folks, not really sure if this is the right place or not, seeking for your assistance on this matter, we have a pretty old ISE running 2.0 so we have started getting alerts of an intermediate certificate authority: Inter...
Community,I recently implemented FTD's and had a question. I am not seeing any Intrusion Events or Attackers populating in the Intrustion Events or Geolocation tabs in my dashboard. Is this because I have not yet enabled the "inspection" option in any of ...
Hi Guys, I have FTD/FMC setup for AnyConnect. The ISE is for authentication. In our AD's IT_Group_VPN which currently has almost 300 users for AnyConnect VPN. As setup today, everyone who is in this AD group 'IT_Group_VPN' would have acce...