CREATE POOLS ON LOAD BALANCING

Log in to the HI GIO PORTAL as an Organization Administrator and Navigate to  

Networking > Edge Gateway > Load Balancer > Pool.

Press ADD to Create a Load Balancer Pool and configure the Pool.

1. Create a pool for non-encrypted application

*General Settings Tab:

  • Name: type Pool name (example IIS-Web-Pool)

  • Default Server Port: The destination server port used by the traffic sent to the member (example 80)

  • Load Balancer Algorithm: (example Round Robin)

NSX ALB supports various Load-balancing methods:

Consistent Hash

Core Affinity

Fastest Response

Fewest Servers

Least Connections

Least Load

Round Robin

 

  • Persistence: The persistence profile will ensure that the same user sticks to the same server for a desired duration of time (e.g. Client IP)

NSX ALB supports various Persistence types:

System-Persistence-App-Cookie

System-Persistence-Client-IP

System-Persistence-Custom-HTTP-Header

System-Persistence-HTTP-Cookie

System-Persistence-TLS

  • Active Health Monitor: (example HTTP - This will send periodic HTTP HEAD requests to each server in the Pool to check the availability)

In the Members tab, add two/or more entries and enter the IP Addresses and Port from the Virtual Machines running the application Servers.

 

Press SAVE to create a non-encrypted pool.

2. Create a pool for encrypted application

*General Settings Tab:

  • Name: type Pool name (example IIS-Web-Pool)

  • Default Server Port: The destination server port used by the traffic sent to the member (example 443)

  • Load Balancer Algorithm: (example Round Robin)

NSX ALB supports various Load-balancing methods:

Consistent Hash

Core Affinity

Fastest Response

Fewest Servers

Least Connections

Least Load

Round Robin

  • Persistence: The persistence profile will ensure that the same user sticks to the same server for a desired duration of time (e.g. Client IP)

NSX ALB supports various Persistence types:

System-Persistence-App-Cookie

System-Persistence-Client-IP

System-Persistence-Custom-HTTP-Header

System-Persistence-HTTP-Cookie

System-Persistence-TLS

  • Active Health Monitor: (example HTTPS - This will send periodic HTTPS HEAD requests to each server in the Pool to check the availability)

 

 

 

In the Members Tab, add two/or more entries and enter the IP Addresses and Port from the Virtual Machines running the application Servers.

 

In the SSL Settings Tab:

  • SSL Enable: Enable

  • Hide Service Certificates: disable

  • Select one or more certificates to be used by the Load Balancer Pool: Select your Certificate

Press SAVE to create an encrypted pool.

** Default Active Health Monitor:

  • HTTP/HTTPS:

    • Send Interval: 10s

    • Receive Timeout: 4s

    • Successful Checks: 3

    • Failed Checks: 3

    • Health Monitor Port: use the Default Server Port of the pool.

    • HTTP request: HEAD / HTTP/1.0

    • Response Code: 2xx, 3xx

  • TCP:

    • Send Interval: 10s

    • Receive Timeout: 4s

    • Successful Checks: 2

    • Failed Checks: 2

    • Health Monitor Port: use the Default Server Port of the pool.

  • UDP:

    • Send Interval: 4s

    • Receive Timeout: 2s

    • Successful Checks: 2

    • Failed Checks: 2

    • Health Monitor Port: use the Default Server Port of the pool.

  • PING:

    • Send Interval: 10s

    • Receive Timeout: 4s

    • Successful Checks: 2

    • Failed Checks: 2