The larger features within the various ADC types are covered in their own documentation. For the general settings, we have descriptions where appropriate below.

The product is also self-documented, providing all the information you need within the Edit ADC page.

Balancing Methods

Balance methods decide how to share the traffic between backends. If you are not using persistence you may need source hashing.

  • Roundrobin: distribute traffic in a round-robin fashion (only when under load). This is best for short lived connections, like HTTP.
  • Least Connections: send traffic to the server with the least connections, best for long lived connections like RDP or MySQL.
  • Source Hash: predictably hash all traffic to avoid needing sticky sessions or cookie insertion for tracking backends.

Session Persistence

Persistence allows you to stick users to the first server they connect to, useful for authentication.

  • Cookie Insertion: the preferred Nova method, insert a cookie (non-tracking) that tracks which server the user went to, and keeps them on that server.
  • Stick Tables: maintain an in-memory table of IP addresses and backend servers to keep persistence.
  • None: do not attempt to persist sessions, excellent for APIs or servers that have shared memory/stores.

Listen Bindings

You need to specify a list of IP addresses and ports to bind to, by default this should be, meaning any IP on the system on port X.

The different ADCs will have different defaults. Typically, you will only change this if you use custom ports, or if you want to bind to a specific IP because you are running multiple ADCs on a single Node.

Health Checks

How Nova establishes and monitors the health of each backend server or upstream. None will disable checking, Layer 4 will use TCP checks to see if the port is open, and Layer 7 is available on HTTP ADCs to fetch an HTTP page.