-
Notifications
You must be signed in to change notification settings - Fork 112
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
vcd_nsxt_ipsec_vpn_tunnel tunnel1 is ok tunnel2 is failing #1324
Comments
Hello @andrzej-dobrzynski-pushgaming ,
In particular the In this case the errors comes directly from VCD API and it looks you have coinciding subnets. Could you try to create just the second tunnel without the first? |
Hello @Didainius i destroyed tunnel1 and i created tunnel2 is ok now but aws site to site vpn needs both tunnel1 and tunnel2 be ok for redundancy https://docs.aws.amazon.com/vpn/latest/s2svpn/VPNTunnels.html thus i assume tunnel1 and tunnel2 should have overlapping subnets but different priorities whereby traffic goes via tunnel1 in normal running or via tunnel2 failing tunnel1 ? |
I am afraid I can't comment much on infrastructure requirements and configuration. Are you able to achieve such configuration using VCD UI? |
no since VCD UI does not expose NSXT tags but NSXT UI does therefore the ask if tags can be added to terraform resource |
Ah, so the point is that if VCD UI doesn't have tags - the API won't have it either. And this provider only uses VCD APIs (not NSX-T) |
Hello @adambarreiro et al
vcd_nsxt_ipsec_vpn_tunnel tunnel1 is ok tunnel2 is failing
Terraform Version
Affected Resource(s)
Terraform Configuration Files
Expected Behavior
Actual Behavior
Steps to Reproduce
References
https://knowledge.broadcom.com/external/article/325098/overlapping-subnets-in-ipsec-vpn-policy.html
following up link above can tags be added to terraform resource ?
The text was updated successfully, but these errors were encountered: