1. Log in to the vSphere Web Client.
  2. Click Networking & Security > NSX Edges.
  3. Double-click an NSX Edge.
  4. Click Manage > Load Balancer > Global Configuration.
  5. Next to Load Balancer Global Configuration, click Edit.
  6. Specify the global load balancer configuration parameters.
    Option Description
    Load Balancer Allows the NSX Edge load balancer to distribute traffic to internal servers for load balancing.

    When disabled, all virtual IP addresses (VIPs) use the L7 LB engine.

    When enabled, the virtual IP uses the faster L4 LB engine or L7 LB engine (based on the VIP configuration).

    The L4 VIP ("acceleration enabled" in the VIP configuration and no L7 setting such as AppProfile with cookie persistence or SSL-Offload) is processed before the edge firewall, and no edge firewall rule is required to reach the VIP. However, if the VIP is using a pool in non-transparent mode, the edge firewall must be enabled (to allow the auto-created SNAT rule).

    The L7 HTTP/HTTPS VIPs ("acceleration disabled" or L7 setting such as AppProfile with cookie persistence or SSL-Offload) are processed after the edge firewall, and require an edge firewall allow rule to reach the VIP.

    Note: To validate which LB engine is used for each VIP by the NSX Load Balancer, on the NSX Edge CLI (ssh or console), run the following command: "show service loadbalancer virtual" and look for "LB PROTOCOL [L4|L7]"


    The NSX Edge load balancer collects traffic logs.

    You can select the log level from the drop-down menu. The logs are exported to the configured syslog server. You can also use the show log follow command to list the load balancing logs.

    The debug and info options log end-user requests. Warning, error, and critical options do not log end-users requests. If the NSX Edge Control-level log is set as debug or info, the load balancer logs lb, vip, pool, and pool member statistics every minute.

    Note that running in debug or info consumes CPU and edge log partition space, and might have a slight impact on the maximum traffic management capability.

    Enable Service Insertion

    Allows the load balancer to work with third-party vendor services.

    If you have a third party vendor load balancer service deployed in your environment, see Using a Partner Load Balancer.

    Attention: Starting in NSX 6.4.5, support for integrating third-party services is deprecated.
  7. Click OK.