Fortinet black logo

Geographic redundancy

Copy Link
Copy Doc ID dd09e35b-031d-11e9-b86b-00505692583a:56100
Download PDF

Geographic redundancy

In order to increase resiliency, implement geographic redundancy when clustering FortiManager devices. That is, situate your FortiManager devices in locations that are not affected by the same conditions, such as power outages or floods.

In the event that the original primary FortiManager fails, the new primary FortiManager will attempt to contact all of the managed devices after the admin user has promoted the FortiManager to primary AND has issued the exec fgfm reclaim command. If any of your managed devices are behind a NAT device, the new primary FortiManager may be unable to connect to the managed devices, depending on whether that NAT is 1-to-1. In the event that FortiManager is unable to initiate a connection to managed devices, you must manually repoint the managed devices to the new primary FortiManager since they only have the IP address for the previous primary FortiManager.

Geographic redundancy

In order to increase resiliency, implement geographic redundancy when clustering FortiManager devices. That is, situate your FortiManager devices in locations that are not affected by the same conditions, such as power outages or floods.

In the event that the original primary FortiManager fails, the new primary FortiManager will attempt to contact all of the managed devices after the admin user has promoted the FortiManager to primary AND has issued the exec fgfm reclaim command. If any of your managed devices are behind a NAT device, the new primary FortiManager may be unable to connect to the managed devices, depending on whether that NAT is 1-to-1. In the event that FortiManager is unable to initiate a connection to managed devices, you must manually repoint the managed devices to the new primary FortiManager since they only have the IP address for the previous primary FortiManager.