This issue is due to the presence of Cisco bug IDCSCsg05519.
When Internet Protocol Security (IPsec) over Transmission Control Protocol (TCP) is configured, the PIX/ASA rejects TCP/443 as an option because that port is already in use by WebVPN. This even occurs on the ASA when WebVPN is not enabled and on the PIX platforms that do not support WebVPN.
The use of this command returns the error message:
ERROR: Port 443 is already configured for WebVPN and will not be added. Please Choose a different port for ipsec-over-tcp.
The security appliance can support both WebVPN and an Adaptive Security Device Manager (ASDM) administrative session simultaneously on the same interface, but by default, both WebVPN and ASDM listen on port 443.
In order to resolve this, assign different port numbers to one of these functions.
Enable ASDM to listen on a different port with this command:
Hello, i have a problem with our ISE 2.7 distributed deployment and the COA after a Guest with a IPhone succuesfully registers. We use a Self-registration with approval process and Single SSID. After the Client succesfully registers he get...
FPR-1010 with ASA 9.14(1)30.Clientless VPN is not showing any bookmarks (there's simply section showing up, multiple browsers), even though they have been configured in the DAP & GP and debugs are showing that they have been applied after the user log...
Hi, a customer has a ESA Cluster of two C100V.the CPU usage es overall very high ( 85% sometimes 100% ) but the Appliance does not seam busy.Why ist the CPU average so high? SystemRAM Utilization 4%Overall CPU load average 86%CPU UtilizationMGA ...
Hello guys,I have 2x ASA 5545c in cluster mode in ACTIVE/ACTIVE mode. Problem is when one unit goes down ASA stop advertising route via OSPF to ASR 1001X router.As you can see in output i can see ASAs MAC addresse from ASR but after failover arp isnt upda...