Load balancer stops working when "Persistence profile" is enabled.

Products

• VMware NSX

Issue/Introduction

• Enabling the Persistence Profile causes the URL to become unresponsive.
  
• Use the command below to verify the active sessions on the active Edge node.
  # get loadbalancers #####50-###4-###c-###r-########6b49 session-tables |find 192.168.1.10.
• The logs below, collected from the support bundle, show the active connections.
  less edge/lb_#####50-###4-###c-###r-########6b49/session |grep -i 192.168.1.10

                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "daddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",
                "caddr": "192.168.1.10",

Environment

VMware NSX

Cause

When the persistence profile is enabled, if the number of sessions exceeds the configured “max concurrent connections” per pool member, the URL will fail to connect.

Resolution

Increase the "Max concurrent connections" on the pool members.

Add Layer 4 Virtual Servers

Add Layer 7 HTTP Virtual Servers