Any newly created Virtual Servers will not change to 'success' status and would remain down. While existing Virtual Servers have no issue.
search cancel

Any newly created Virtual Servers will not change to 'success' status and would remain down. While existing Virtual Servers have no issue.

book

Article ID: 317198

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Symptoms:
- Any newly created Virtual Servers can be seen in the UI, but they never enter the 'Up' state and remain in the 'Down' state indefinitely.

- Any pre-existing Virtual Servers are 'Up' and operational.

- In /var/l/og/syslog on the Edge you may see messages like the following:

2021-09-15T14:21:26.566275+00:00 edge01.corp.local NSX 7906 LOAD-BALANCER [nsx@6876 comp="nsx-edge" subcomp="lb" s2comp="lb" level="FATAL"] [########-####-####-####-############] invalid port 000 [version: 5] in /config/vmware/edge/lb/etc/#######-####-####-####-############/nginx.conf:127

- You find a Virtual Server deployed with an unexpected port such as port '000', which is an 'Unknown' state.

- On a version of NSX-T prior to version 3.2.0.

Environment

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

Cause

- The NSX-T LB makes use of nginx and if there is an issue with the nginx.conf file, then the worker processes will not be reloaded.

- In this case the issue is the invalid port '000', which will cause the nginx.conf file to fail to be reloaded until the invalid config is removed. Please note this will prevent any new Virtual Servers being loaded, even if their configuration is valid, until the Virtual Server with the invalid config is deleted.

Resolution

  • Delete the Virtual Server in the unknown state and with the invalid configuration.
  • This is fixed in NSX-T 3.2.0, which will prevent a user from entering an invalid port config either through the NSX Manager UI or the API.