Intermittent Application connectivity issue over Load Balancer

Products

• VMware NSX

Issue/Introduction

Symptoms:

• All the connections to the application get refused with IPv6 addresses over Layer 4 connection.
• Load balancer Pool members are configured with both IPv4 and IPv6 address. Edge is using the L7 LB engine.
• In the Load balancer log file, you see entries similar to:

  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_POOL_#####_8080/###-###-####-01_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 3 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_POOL_#####_8080/###-###-#####-02_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_###_POOL_############_9000/###-###-############-01_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 3 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_###_POOL_############_9000/###-###-############-02_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_POOL_#########_8080/###-###-###-01_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 3 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_POOL_#########_8080/###-###-###-02_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:09+00:00 ###-###-nsxlb-01-1 loadbalancer[16975]: [default]: [local0.alert] Server ###_POOL_####_8080/###-###-####-01_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 3 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:10+00:00 ###-###-nsxlb-01-1 loadbalancer[16976]: [default]: [local0.alert] Server ###_POOL_####_8080/###-###-####-02_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:10+00:00 ###-###-nsxlb-01-1 loadbalancer[16976]: [default]: [local0.alert] Server ###_POOL_######_8080/###-###-#####-01_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 3 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.
  2017-03-30T03:03:10+00:00 ###-###-nsxlb-01-1 loadbalancer[16976]: [default]: [local0.alert] Server ###_POOL_######_8080/###-###-#####-02_<ipv6> is DOWN, reason: Layer4 connection problem, info: "General socket error (Invalid argument)", check duration: 0ms. 2 active and 0 backup servers left. 0 sessions active, 0 requeued, 0 remaining in queue.

   

Environment

VMware NSX for vSphere 6.4.x

VMware NSX for vSphere 6.3.x

VMware NSX for vSphere 6.2.x

Resolution

To resolve this issue:

• Use IP address as pool member instead of VM name.
• Remove IPv6 address in server VMs.