I will be making some changes to the way our ASA 5505 is configured over the next few weeks. It is used mainly for our phone VPN clients to connect to our internal CME. The issue is that I shall be changing the inside network to another vlan and another IP address, although the name will be staying the same. I know that this will remove all the config which uses that interface name, such as NAT translations etc but my main concern is that when I put them back in again with the same name it may confuse the ASA in some way and just not work.
Has anyone had any experience with this as I would really like to know possible issues before I get to them.
the Cisco CPN Client for a long time to connect to a VPN Server. Now I've got a new machine with a Windows 7 64 bit. The Cisco VPN Client isn't avaiable in a 64 bit version. Cisco suggests to use Cisco AnyConnect instead because there'a 64 bit version ava...
May 2016Splunk is a powerful tool for analyzing information in your organization by collecting, storing, alerting, reporting, and analyzing machine data. With Cisco platform Exchange Grid (pxGrid) Splunk is able to proactively act on received network secu...
Happy to announce that we have an updated version of our Enabling AMP on Content Security Products - Best Practices (v3.0). Please feel free to review if you have questions regarding deployment of AMP (File Reputation and File Analysis).
Updated: July 2018
New: Updated format , Netflow configuration examples per platform (End of Table)
Note: Remember the table is scrollable horizontally to view other columns, not only vertically
IOS / IOS XE