NSX-T Data Center 2.5.x upgrade to 3.x Load balancer returns "502 bad gateway" when using load balancer rules

Products

• VMware NSX Networking

Issue/Introduction

Symptoms:

• Upgraded from NSX-T Data Center 2.5.x to 3.x recently.
• You use load balancer rules to route traffic based on destination port.
• The load balancer VIP returns a 502 bad gateway error after the upgrade.
• Prior to the upgrade this worked with no 502 bad gateway error.
• If you bypass the load balancer, the connection works.

Environment

VMware NSX-T Data Center
VMware NSX-T Data Center 3.x
VMware NSX-T Data Center 2.5.x

Cause

Prior to NSX-T 3.x, the IP address and port were evaluated.
When this issue occurs in 3.x, this evaluation fails to consider the destination port, therefore it can not make a match on the rule and the connection fails.

Resolution

This issue is resolved in VMware NSX-T Data Center 3.1.2, available at VMware Downloads.

Workaround:
Upgrade to NSX-T 3.1.2 where the correct evaluation of the header occurs for the load balancer rule.