Fortinet Document Library

Version:

Version:


Table of Contents

FortiVoice Cookbook

Download PDF
Copy Link

Configuring service-based failover

There may be cases where the system and heartbeat are established, but the service process may be down. Service-based monitoring can help to appropriately trigger a failover.

HA service monitoring settings are not synchronized and need to be configured on each primary and secondary unit. If service monitor detects a failure, the effective HA operating mode of the primary unit switches to off or failed. A failover occurs and the effective HA operating mode of the secondary unit switches to master.

Service monitoring provides extra protection, in cases where both the primary and secondary heartbeat links fail or become disconnected. Use the following steps to allow the secondary unit to confirm its connection to the primary unit over the network using SIP and HTTP connections.

  1. Go to System > High Availability > Configuration.
  2. Under Service Monitor, select Remote HTTP and click Edit.
  3. Click Enable.
  4. Set Remote IP to the peer unit's IP address.
  5. Set Port to the port number of the SMTP service.
  6. Enter a Timeout period in seconds for one connection test, and enter an Interval frequency in seconds for these timeout tests.
  7. Enter the number of Retries that are allowed before the primary unit is deemed unresponsive and a failover occurs.
  8. Click OK.
  9. Select SIP UDP, click Edit, and configure the options available.
  10. Click OK.
  11. Select Interface monitor, click Edit, and configure its interval and retry options.
  12. Click OK.
  13. Select Local hard drives, click Edit, click Enable, and configure its interval and retry options.
  14. Click OK.

Configuring service-based failover

There may be cases where the system and heartbeat are established, but the service process may be down. Service-based monitoring can help to appropriately trigger a failover.

HA service monitoring settings are not synchronized and need to be configured on each primary and secondary unit. If service monitor detects a failure, the effective HA operating mode of the primary unit switches to off or failed. A failover occurs and the effective HA operating mode of the secondary unit switches to master.

Service monitoring provides extra protection, in cases where both the primary and secondary heartbeat links fail or become disconnected. Use the following steps to allow the secondary unit to confirm its connection to the primary unit over the network using SIP and HTTP connections.

  1. Go to System > High Availability > Configuration.
  2. Under Service Monitor, select Remote HTTP and click Edit.
  3. Click Enable.
  4. Set Remote IP to the peer unit's IP address.
  5. Set Port to the port number of the SMTP service.
  6. Enter a Timeout period in seconds for one connection test, and enter an Interval frequency in seconds for these timeout tests.
  7. Enter the number of Retries that are allowed before the primary unit is deemed unresponsive and a failover occurs.
  8. Click OK.
  9. Select SIP UDP, click Edit, and configure the options available.
  10. Click OK.
  11. Select Interface monitor, click Edit, and configure its interval and retry options.
  12. Click OK.
  13. Select Local hard drives, click Edit, click Enable, and configure its interval and retry options.
  14. Click OK.