Skip to content
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

IP-Pool name synced in HA-Cluster and breaking recommended setup in Azure #64

Open
agyss opened this issue May 21, 2024 · 1 comment
Open

Comments

@agyss
Copy link

agyss commented May 21, 2024

I followed the implementation of: https://github.com/fortinet/azure-templates/blob/main/FortiGate/Active-Passive-ELB-ILB/doc/config-outbound-nat-considerations.md

However, as soon as the IP-Pool is configured on the primary fortigate, it's synced to the failover system. As a consequence, it is not possible to create an IP-Pool with the same name but a different ip on the failover system. The failover is therefore effectively not working.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant