Nat (inside,outside) source static LOCAL-NETWORKS LOCAL-NETWORKS destination static 10.0.0.0/24 10.0.0.0/24 route-lookup The firmware version of this device is 9.x, so we use object based nat to do our NO-NAT statements. The next command that resolved the issue for me had to do with my nat statement.

For me this did not work, still could not access the device from the remote subnet. For example, if you enter the ASA from the outside interface, this feature lets you connect to the inside interface using ASDM, SSH, Telnet, or SNMP or you can ping the inside interface when entering from the outside interface”.Īwesome, so that allows us to actually use the inside for management when connecting through a different interface (VPN). “If your VPN tunnel terminates on one interface, but you want to manage the ASA by accessing a different interface, you can identify that interface as a management-access interface. All is working with the VPN, its up and functioning everything is great accept access to the ASA itself from the remote subnet. So the above images shows a simple layout of what I have going on.

In this entry I will point out those commands and explain why the commands actually fix the issue. There are a few simple command that fix this. After the tunnel creation, all traffic worked great except traffic (SSH,SNMP,PING) directed to the device’s inside interface. Recently I created a tunnel for a client between two Cisco ASAs, and they monitor VIA PRTG and make automated backups via Solarwinds.

Allow pings through asa asdm