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

Azure Fortigate Virtual Server Active Passive HA failover #270

Open
agyss opened this issue Oct 1, 2024 · 2 comments
Open

Azure Fortigate Virtual Server Active Passive HA failover #270

agyss opened this issue Oct 1, 2024 · 2 comments

Comments

@agyss
Copy link

agyss commented Oct 1, 2024

I could not find any information on how to adapt the virtual server ip in case of a failover from active to passive in terraform.

My scenario is that I have an active-passive HA setup in Azure, with a management interface, ha ports and public/private ports.
When setting up the virtual server, the private IP it receives on the active fortigate must be assigned to it. However, in case of a failover as in the templates here, the public IP is reassigned to a predefined ip-config, so another private IP - resulting in the virtual server becoming unreachable.

For the virtual server to keep working, I would need to specify the public IP there (which didn't work for me) or adjust its private IP in case of a failover, which I could not find means to do it.

Did I miss something, or is this not supported?

@agyss
Copy link
Author

agyss commented Oct 1, 2024

Another way could be to configure one virtual server which only works on the (default) primary and the (default) failover instance. Unfortunately, from the list of ha-synced objects (https://community.fortinet.com/t5/FortiGate/Technical-Tip-HA-FortiGate-configurations-that-will-sync-and/ta-p/216710) this would create both virtual servers on both VMs, making it not very nice.

@mobilesuitzero
Copy link
Collaborator

As during failvoer, public-ip is moved from primary to the secondary, but not the private ip address assigned to the instance in azure.
Hence, in this case, need to put vip setting in the vdom-exception, and user would need to configure those settings separately in each unit due to the private ip addresses(extip) are different for each instance.

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

2 participants