Heads Up :
The post you are writing will appear in a public forum. Please ensure all content is appropriate for public consumption. Review the employee guidelines for the community here.
Hello,
I am setting up new webvpn bookmarks in preparation for moving away from a Netapp-hosted CIFS file server to a Windows Server 2012 SMB file server. ASA version 9.1(7)12.
The current bookmark works, and looks like this: CSCO_WEBVPN_USERNAME:CS...
Hey all,
My question is about how Cisco handles bug fixes for different ASA code releases. For example, I get daily email notifications from Cisco showing new and fixed bugs and the code releases they apply to, e.g.
Known Affected Releases:
100.16(1...
Hey all,
I am trying to find the 5 second CPU usage of a 5515-X ASA running 9.2(4). I have a 5550 that it works on, running 8.4(4), as well as a 5520 running 9.1(7)4.
The OID is 1.3.6.1.4.1.9.9.109.1.1.1.1.3. cpmCPUTotal5sec. Has Cisco just removed...
Hey all,
I am trying to enable VPN access from the testing interface to the wifi interface. I get an implicit ACL drop in packet-tracer, and Deny IP spoof log messages, even though RPF is not enabled on either interface. VPN is currently working for ...
Hey guys,
I'd like some help with port forwarding on a 5505 running 9.2(4) code.
I'm trying to forward requests on port 80 on my outside, ISP provided IP to port 8000 on an internal server. Everything inside the ASA is PATing on the outside address.
...
I am able to poll .1.3.6.1.4.1.9.9.109.1.1.1.1.8.1 cpmCPUTotal5minRev as well as .1.3.6.1.4.1.9.9.109.1.1.1.1.7.1 cpmCPUTotal1minRev with no problems. I can also poll 1.3.6.1.4.1.9.9.109.1.1.1.1.3. cpmCPUTotal5sec on my other two ASAs, but not on t...
VPN is working on the testing interface now. I just need to mess with DNS now to get it to resolve correctly for hosts inside it. I believe my problem is resolved. Thanks for all the help.
This what I'm trying to accomplish. Wireless users on the wifi interface use VPN to access internal domain resources, using vpn.ourcompany.com, which resolves to the wifi interface address, 172.20.16.2.
My thought was to use that same interface as th...
Wow, you nailed it. That didn't even occur to me. Packet-tracer to 172.20.16.3 works just fine. My issue now is that the VPN address is on the wifi interface, using the interface address.
