Remote Logging Not Configured alarm generated in NSX when node profile is used to configure syslog server

Products

• VMware NSX
• VMware NSX-T Data Center

Issue/Introduction

• A node profile has been created in the NSX installation
• The node profile has a syslog server specified by fully qualified domain name (FQDN)
• An alarm for one or more NSX nodes is generated that states, "Remote Logging Not Configured"
• If an attempt is made to manually set the syslog server on the affected NSX node via the "set logging-server" NSX CLI command, an error similar to the following is returned:
  
  The specified logging-server is invalid: <SYSLOG_FQDN>
  
  
• When logged in as root on the affected NSX node, attempts to resolve the name of the syslog server (or any other system) consistently fail, resulting in similar error messages:
  nslookup <SYSLOG_FQDN> 
;; communications  error to ###.###.###.####53: timed out
;; communications  error to ###.###.###.####53: connection refused 
;; no servers could be reached 

Environment

VMware NSX
VMware NSX-T Data Center

Cause

This issue can occur if the IP address specified for the DNS server during node deployment is incorrect, resulting in name resolution failures.

Resolution

Set the DNS server IP address appropriately. 

The set name-servers <IP> and del name-server <IP> commands can be used to set the appropriate DNS server IP address and remove the inappropriate DNS server IP address, respectively.