We have following scenario, my side we have Cisco ASA and we have IPsec tunnel to Customer US-Datacenter and i can ping subnet from my ASA (local LAN but now i want to ping EU-Datacenter subnet too which is and confused how do i add that remote subnet in my IPsec tunnel?

enter image description here

We have following ACL for interesting traffic.

access-list ACL-VPN extended permit ip

I have tried add following ACL to see if it work but it didn't work.

access-list ACL-VPN extended permit ip


My ASA Config:

crypto isakmp identity 49.XX.XX.101
crypto ikev1 enable outside
crypto ikev1 policy 100
authentication pre-share
encryption 3des
hash md5
group 1
lifetime 86400
tunnel-group 49.XX.XX.101     type ipsec-l2l
tunnel-group 49.XX.XX.101     ipsec-attributes
ikev1 pre-shared-key  SuperSecret

crypto ipsec ikev1 transform-set TSET esp-3des esp-md5
crypto map VPN 10 match address ACL-VPN
crypto map VPN 10 set peer 49.XX.XX.101
crypto map VPN 10 set ikev1 transform-set TSET
crypto map VPN 10 set security-association lifetime seconds 3600
access-list ACL-VPN extended permit ip
nat (any,outside) source static destination static
  • We need to see the rest of the ASA configuration.
    – Ron Trunk
    Dec 27, 2017 at 23:54
  • I have added snippet for IPsec config in my question, Tunnel is up and i can ping remote LAN but now i want to ping which i don't know how to do that
    – Satish
    Dec 28, 2017 at 0:11
  • Need the rest of the configuration
    – Ron Trunk
    Dec 28, 2017 at 0:59
  • its massive config and we have many many tunnel terminated on ASA i don't know what specific you looking for. I don't know what portion i should put here and omit all security stuff, it would be massive cut paste for me. if you point specific section i can do that, all i want to know how IPsec VPN know or route remote subnet traffic, there is no route command i can use to tell route subnet over VPN tunnel
    – Satish
    Dec 28, 2017 at 1:10

1 Answer 1



What you did is NOT enough. You have to ensure VPN configuration is updated for the additional subnet ( at BOTH ends. To be specific, the following points need to be satisfied:

At your end:

  1. Add Crypto ACL for additional subnet. You already did this.

  2. Add Interface ACL for additional subnet. I do not see rules for in your configuration. Anyway, if you have rules configured for, you have to do the same for

  3. Add NAT Exemption statement for additional subnet such as:

    nat (any,outside) source static destination static
  4. Add a route for additional subnet. I do not see a route for in your configuration, so I assume you have a default route. Otherwise, if you have a route for, you have to configure a similar route for

At your US DC customer end:

On the device where VPN tunnel configured, they also have to update their VPN configuration (mirror points #1 - #3 mentioned above) for additional/second subnet (EU DC).

In US DC network, they do not need the point #4, because they already a route for your network ( However, they would need a route for their EU DC subnet on the device where VPN tunnel configured.

And At your EU DC customer end:

They would need a route for your network ( with next-hop IP address located at US DC, so that the return traffic could be sent back through VPN tunnel.


When everything is properly configured, VPN traffic from your network ( to EU DC subnet ( would hit the device (where VPN tunnel configured) at US DC. This traffic is decrypted, and then is forwarded/routed to US DC backbone network, then forwarded to EU DC via DC-Link. At EU DC, return traffic is sent back to US DC via DC-Link again thanks to newly-configured route I mentioned above.

enter image description here


Regarding the configuration on your ASA, you should avoid using IP addresses/subnets and TCP/UDP ports directly in your ACL and NAT rules as much as possible. It is ugly and would take you lot of efforts and time to maintain the configuration and troubleshoot when issues happen.

Always put them into an object or object-group with meaningful name. If you need to change or update the configuration related to them, you just only need to update that object or object-group.


I hope it is helpful and you can get it worked.

  • Thanks for details, question related step 4. You said specify route what does that means? In IPsec there is no route option you can tell to ASA this is your gateway or out going interface? Can you explain what you trying to say?
    – Satish
    Dec 28, 2017 at 23:51
  • @Satish ASA needs to know where to route/forward traffic for remote subnets ( and If you only have only one outside interface, a default route and there is no other specific routes for remote subnets, then VPN traffic will be sent to outside interface where you enable crypto IKEv1. That is why you do not need to add a route when creating new VPN tunnel for new customers.
    – Hung Tran
    Dec 29, 2017 at 9:27
  • @Satish In some cases, when you have more than one outgoing interface, let us say you have outside and outside_2 interfaces, and you configure VPN tunnels for different customers on different outgoing interface, you have to put a route for additional remote subnet to correct outgoing interface.
    – Hung Tran
    Dec 29, 2017 at 9:33
  • @Satish Have you got this fixed?
    – Hung Tran
    Jan 5, 2018 at 9:13
  • I have add in ACL for IPsec that didn't work but then US Datacenter folks did something which don't know but they said it has been fix our side and now i can ping everywhere. I would agreed with your theory too
    – Satish
    Jan 5, 2018 at 21:42

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge you have read our privacy policy.

Not the answer you're looking for? Browse other questions tagged or ask your own question.