Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Fortinet white logo
Fortinet docs logo DOCUMENT LIBRARY
Products Best Practices Hardware Guides Products A-Z
Summary
By Solution
By 4D Pillars
By Cloud
Secure Networking
Unified SASE
Security Operations
Secure SD-WAN
Secure Access Service Edge (SASE)
ZTNA
LAN Edge
Identity and Access Management
Next Generation Firewall
Public Cloud
Private Cloud
FortiCloud
Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
    • More >>
    Unified SASE
  • Single Vendor SASE
  • Cloud Network Security
  • Secure Endpoint Connectivity
  • Web Application / API Protection
    • More >>
    Security Operations
  • Security Operations Automation
  • Identity
  • Early Detection & Prevention
    • More >>
    Secure Networking
  • Hybrid Mesh Firewall
  • NOC Management
  • LAN
  • WAN
  • Communication & Surveillance
    • Unified SASE
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Cloud Network Security
  • Cloud-Native Security
  • Web Application / API Protection
    • Security Operations
  • Security Operations Automation
  • Endpoint
  • Data Protection
  • Identity
  • Email
  • Early Detection & Prevention
  • Expert Services
  • Edge Firewall
  • Orchestration & management
  • SD Branch
  • Application Delivery
  • Single Vendor SASE
  • Secure Endpoint Connectivity
  • Secure Private Access
  • Thin Edge
  • Identity
  • Application Gateway
  • Enterprise Asset Management
  • Endpoint Agent
  • Agentless Security Posture
  • Identity
  • Wireless
  • Switching
  • Identity
  • Privilege Acccess Management
  • Next Generation Firewall
  • Orchestration & management
  • Expert Services
  • All
  • All
  • Account Management
  • SAAS Management
  • SAAS Application Security
  • Managed Services
  • Platform as a service (PAAS)
  • Other SAAS Services
    • 4D Resources
    Solution Hubs
  • 4D Pillars
  • Cloud
  • Popular Solutions

    • Handbook

    Home FortiADC 6.2.2 Handbook
    6.2.2
    7.4.5
    7.4.4
    7.4.3
    7.4.2
    7.4.1
    7.4.0
    7.2.7
    7.2.6
    7.2.5
    7.2.4
    7.2.3
    7.2.2
    7.2.1
    7.2.0
    7.1.4
    7.1.3
    7.1.2
    7.1.1
    7.1.0
    7.0.5
    7.0.4
    7.0.3
    7.0.2
    7.0.1
    7.0.0
    6.2.6
    6.2.5
    6.2.4
    6.2.3
    6.2.2
    6.2.1
    6.2.0
    6.1.6
    6.1.5
    6.1.4
    6.1.3
    6.1.2
    6.1.1
    6.1.0
    6.0.1
    6.0.0
    5.4.3
    5.4.2
    5.4.1
    5.4.0
    5.3.6
    5.3.5
    5.3.4
    5.3.3
    5.3.2
    5.3.1
    5.3.0
    5.2.7

    Configuring virtual server pools

    Configuring virtual server pools

    The virtual server pool configuration defines the set of virtual servers that can be matched in DNS resource records, so it should include, for example, all the virtual servers that can be answers for DNS requests to resolve www.example.com.

    You also specify the key parameters of the global load balancing algorithm, including proximity options, status checking options, load balancing method, and weight.

    The DNS response is an ordered list of answers. Virtual servers that are unavailable are excluded. Available virtual servers are ordered based on the following priorities:

    1. Geographic proximity
    2. Dynamic proximity
    3. Weighted round robin

    A client that receives DNS response with a list of answers tries the first and only proceeds to the next answers if the first answer is unreachable.

    Before you begin:

    • You must have created GLB Servers configuration objects.
    • You must have Read-Write permission for Global Load Balance settings.

    After you have created a virtual server pool configuration object, you can specify it in the global load balancing host configuration.

    To configure a virtual server pool:
    1. Go to Global Load Balance > FQDN Settings.
    2. Click the Virtual Server Pool tab.
    3. Click Create New to display the configuration editor.
    4. Complete the configuration as described in Virtual server pool configuration.
    5. Save the configuration.

    Virtual server pool configuration
    Settings Guidelines

    Name

    Specify a unique name for the virtual server pool configuration. Valid characters are A-Z, a-z, 0-9, _, and -. No spaces. You reference this name in the host configuration.

    Note: After you initially save the configuration, you cannot edit the name.

    Preferred
    • None—No preference.
    • Geo—If selected, virtual servers with the same GEO information as the local DNS address will respond.
    • Geo-ISP—If selected, virtual servers with the same ISP information as the local DNS address will respond first, and virtual servers with the same GEO information as the local DNS address will respond second.
    • RTT—Virtual servers with the shortest latency link or closest to the data center will respond.
    • Least-Connnections—Virtual servers with the least connections will respond.
    • Connection-Limit—Virtual servers will be responded by their connection limit determined by virtual servers' weight: the greater the weight of a virtual server, the more responses it will get.
    • Bytes-Per-Second—Virtual servers with the lowest traffic will respond.
    • Server-Performance—Virtual servers with better server-performancec in the CPU or Memory (whichever one you give more weight to) will respond.

    Alternate

    Same as above.

    Load Balance Method

    Weighted Round Robin

    Check Server Status

    Enable/disable polling of the local FortiADC SLB. If the server is unresponsive, its virtual servers are not selected for DNS answers.

    Check Virtual Server Existence

    Enable/disable checks on whether the status of the virtual servers in the virtual server list is known. Virtual servers with unknown status are not selected for DNS answers.

    Member

    Server

    Select a GLB Servers configuration object.

    Server Member

    Select the name of the virtual server that is in the servers virtual server list configuration.

    Weight

    Assigns relative preference among members—higher values are more preferred and are assigned connections more frequently.

    The default is 1. The valid range is 1-255.

    Backup

    Enable to designate the member as a backup. Backup members are inactive until all main members are down.
    Previous
    Next

    Configuring virtual server pools

    Configuring virtual server pools

    The virtual server pool configuration defines the set of virtual servers that can be matched in DNS resource records, so it should include, for example, all the virtual servers that can be answers for DNS requests to resolve www.example.com.

    You also specify the key parameters of the global load balancing algorithm, including proximity options, status checking options, load balancing method, and weight.

    The DNS response is an ordered list of answers. Virtual servers that are unavailable are excluded. Available virtual servers are ordered based on the following priorities:

    1. Geographic proximity
    2. Dynamic proximity
    3. Weighted round robin

    A client that receives DNS response with a list of answers tries the first and only proceeds to the next answers if the first answer is unreachable.

    Before you begin:

    • You must have created GLB Servers configuration objects.
    • You must have Read-Write permission for Global Load Balance settings.

    After you have created a virtual server pool configuration object, you can specify it in the global load balancing host configuration.

    To configure a virtual server pool:
    1. Go to Global Load Balance > FQDN Settings.
    2. Click the Virtual Server Pool tab.
    3. Click Create New to display the configuration editor.
    4. Complete the configuration as described in Virtual server pool configuration.
    5. Save the configuration.

    Virtual server pool configuration
    Settings Guidelines

    Name

    Specify a unique name for the virtual server pool configuration. Valid characters are A-Z, a-z, 0-9, _, and -. No spaces. You reference this name in the host configuration.

    Note: After you initially save the configuration, you cannot edit the name.

    Preferred
    • None—No preference.
    • Geo—If selected, virtual servers with the same GEO information as the local DNS address will respond.
    • Geo-ISP—If selected, virtual servers with the same ISP information as the local DNS address will respond first, and virtual servers with the same GEO information as the local DNS address will respond second.
    • RTT—Virtual servers with the shortest latency link or closest to the data center will respond.
    • Least-Connnections—Virtual servers with the least connections will respond.
    • Connection-Limit—Virtual servers will be responded by their connection limit determined by virtual servers' weight: the greater the weight of a virtual server, the more responses it will get.
    • Bytes-Per-Second—Virtual servers with the lowest traffic will respond.
    • Server-Performance—Virtual servers with better server-performancec in the CPU or Memory (whichever one you give more weight to) will respond.

    Alternate

    Same as above.

    Load Balance Method

    Weighted Round Robin

    Check Server Status

    Enable/disable polling of the local FortiADC SLB. If the server is unresponsive, its virtual servers are not selected for DNS answers.

    Check Virtual Server Existence

    Enable/disable checks on whether the status of the virtual servers in the virtual server list is known. Virtual servers with unknown status are not selected for DNS answers.

    Member

    Server

    Select a GLB Servers configuration object.

    Server Member

    Select the name of the virtual server that is in the servers virtual server list configuration.

    Weight

    Assigns relative preference among members—higher values are more preferred and are assigned connections more frequently.

    The default is 1. The valid range is 1-255.

    Backup

    Enable to designate the member as a backup. Backup members are inactive until all main members are down.
    Previous
    Next