This problem is due to the presence of Cisco bug ID CSCsb92243.
When the Cisco Adaptive Security Device Manager (ASDM) 5.0(2) is used to configure VPN tunnels on the PIX or Adaptive Security Appliance (ASA), the IPsec rules do not always show up correctly under Configuration > Features > VPN > IPSec > IPSec Rules.
The rules that define the protected tunnel sometimes do not match the access-lists defined in the Command Line Interface (CLI). This is caused by the presence of static policy Network Address Translation (NAT) statements in the configuration. If the IPsec rule is then edited in ASDM, this causes an incorrect rule to be sent to the ASA.
This issue happens when a combination of the ASDM and the CLI is used to configure the rules.
As a workaround, use the CLI in order to manually edit the rules or use only the ASDM. Do not use a combination of both the ASDM and the CLI.
This issue is fixed in ASDM version 5.2, which can be downloaded from Cisco Downloads.
Sometimes I'm using our VPN near the end of the 24-hour limit, and it warns me that it's about to run out. Then it cuts the connection suddenly and interrupts my work. There is no option to continue. It would be much better if there were a button to exten...
Hi, I am implementing Guest wireless nw via Cisco ISE, wherein am utilizing the sponsor page registration for the Guest users.Now my question is for the Portal certificate can i use an ip based certificate instead of Fqdn ? Since i do not want the fq...
I currently have Adaptive Security Appliance Software Version 9.16(2)SSP Operating System Version 2.10(1.162)Device Manager Version 7.16(1)150 want to upgrade to the latest recommended version, sees thsi 9.16(2) IS HAVING LOTS OF ISSUES, checke...
I have only one operational DC from where user Agent are getting userid/ip mapping info. Even though there are 1 other DC added at User agent but other 1 are part of Test Site.
How to confirm which dc actually providing user id and ip mapping to...