Fortinet Document Library

Version:

Version:

Version:


Table of Contents

Administration Guide

Download PDF
Copy Link

Server communication

Shared IP - same subnet

In a (Undefined variable: User_Guide.ProductAbbrev) Control Server and (Undefined variable: User_Guide.ProductAbbrev) Application Server configuration that uses a shared IP, the (Undefined variable: User_Guide.ProductAbbrev) Application Server appliances are separate standbys from the (Undefined variable: User_Guide.ProductAbbrev) Control Server appliances.

Examples:
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server fails, the secondary (Undefined variable: User_Guide.ProductAbbrev) Control Server communicates with whichever (Undefined variable: User_Guide.ProductAbbrev) Application Server is in control (either the primary or the secondary).
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Application Server fails, the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server communicates whichever (Undefined variable: User_Guide.ProductAbbrev) Application Server is in control.
No shared IP - different subnets

In a (Undefined variable: User_Guide.ProductAbbrev) Control Server and (Undefined variable: User_Guide.ProductAbbrev) Application Server configuration that does not use a shared IP, the (Undefined variable: User_Guide.ProductAbbrev) Application Server and (Undefined variable: User_Guide.ProductAbbrev) Control Server appliances failover in pairs.

Examples:
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server fails the primary (Undefined variable: User_Guide.ProductAbbrev) Application server is also brought down and the Secondary pair of appliances take control.
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Application Server fails, the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server is also brought down and the Secondary pair of appliances take control.

Server communication

Shared IP - same subnet

In a (Undefined variable: User_Guide.ProductAbbrev) Control Server and (Undefined variable: User_Guide.ProductAbbrev) Application Server configuration that uses a shared IP, the (Undefined variable: User_Guide.ProductAbbrev) Application Server appliances are separate standbys from the (Undefined variable: User_Guide.ProductAbbrev) Control Server appliances.

Examples:
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server fails, the secondary (Undefined variable: User_Guide.ProductAbbrev) Control Server communicates with whichever (Undefined variable: User_Guide.ProductAbbrev) Application Server is in control (either the primary or the secondary).
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Application Server fails, the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server communicates whichever (Undefined variable: User_Guide.ProductAbbrev) Application Server is in control.
No shared IP - different subnets

In a (Undefined variable: User_Guide.ProductAbbrev) Control Server and (Undefined variable: User_Guide.ProductAbbrev) Application Server configuration that does not use a shared IP, the (Undefined variable: User_Guide.ProductAbbrev) Application Server and (Undefined variable: User_Guide.ProductAbbrev) Control Server appliances failover in pairs.

Examples:
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server fails the primary (Undefined variable: User_Guide.ProductAbbrev) Application server is also brought down and the Secondary pair of appliances take control.
  • If the primary (Undefined variable: User_Guide.ProductAbbrev) Application Server fails, the primary (Undefined variable: User_Guide.ProductAbbrev) Control Server is also brought down and the Secondary pair of appliances take control.