08-23-2018 08:01 AM - edited 02-21-2020 08:08 AM
Hi all,
I am having some problems with a spoke-hub-spoke setup and I'm really stumped. Hopefully some knowledgeable person can help me out...
I have three sites: a hub and spokes A and B. Site-to-site VPNs are configured between spoke A and the hub, and spoke B and the hub. The hub can communicate with each spoke, but they can't communicate with each other.
Things I have already done:
Spoke A ASA: added the spoke B subnets to the interesting traffic and no-NAT
Spoke B ASA: added the spoke A subnets to the interesting traffic and no-NAT
Hub ASA: configured same-security-traffic inter-interface; configured no-NAT from the spoke A subnets to the spoke B subnets on the outside interface
The only routing in place on the hub ASA is 0.0.0.0 to the outside interface.
Using the command show crypto sa peer <peer ip> on the hub ASA, I can see that traffic for spoke B is arriving from spoke A and being de-encapsulated, but not being encapsulated and sent to spoke B. Same for traffic from spoke B to spoke A.
I will post santised configs if required, but is there anything I could have missed?
Many thanks
Alex
09-14-2018 08:33 AM
Strange indeed. No reason I can see that the ASA should not encrypt. You have the right outside,outside NAT rule to match between SiteA and SiteB.
nat (outside,outside) source static Site_A_Networks Site_A_Networks destination static Site_B_Networks Site_B_Networks no-proxy-arp route-lookup
Can you get the "show nat detail" to see if the show the order of the NAT statements on the ASA.
Also, do you have other VPN tunnels that you have not pasted in the config? I see sequence number 2 and 6 on your config. Are there other crypto map sequences that you have not shown here, which could conflict with the tunnels shown here?
Last point to make is the version on the hub. The 9.2(2)4 version is very old. There have been many bugs in the earlier 9.x versions regarding Stale VPN contexts, which caused failure in encapsulation. A reboot usually fixes this. Is this something you can try in a window?
09-17-2018 07:01 AM
09-17-2018 04:06 PM
Nat Rule#1 seems to show translates and untranslates - which is good:
1 (outside) to (outside) source static Site_A_Networks Site_A_Networks destination static Site_B_Networks Site_B_Networks no-proxy-arp route-lookup
translate_hits = 1113612, untranslate_hits = 1113618
Source - Origin: 10.25.0.0/16 Translated: 10.25.0.0/16
Destination - Origin: 10.12.0.0/16 Translated: 10.12.0.0/16
I see that you have removed the following from Site B networks:
network-object object 10.10.0.0
network-object object 10.13.13.0
network-object object 10.80.0.0
The reason I asked for the other tunnels is to check if there could be a possible conflicts in the crypto ACL. The crypto map is matched in sequence, so if there is an entry that is higher up that matches the traffic, it will try to send it to through that tunnel instead.
Reload will definitely help if this is a bug. If this is still not resolved after a reload, there is most likely a conflicting entry somewhere.
09-18-2018 06:43 AM
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide