Adding configurations to an existing syslog server via NSX CLI results in the error "% Only one TLS syslog exporter is supported. Please delete the current TLS syslog exporter before adding a new TLS syslog exporter"

Products

• VMware NSX

Issue/Introduction

• The existing syslog server is configured with the TLS protocol.
  

  manager> get logging-servers
  <Timestamp>
  <IP_Address>:10514 proto tls level info exporter_name <UUID>

• Adding configurations to the existing syslog server via NSX CLI outputs the following error:
  

  manager> set logging-server <IP_Address>:10514 proto tls level info facility local6 messageid SYSTEM,FABRIC structured-data audit="true"
  % A CA certificate file must be specified for TLS logging-servers

• Specifying the certificates used when registering the existing syslog server still outputs the following error:
  

  manager> set logging-server <IP_Address>:10514 proto tls level info facility local6 serverca <serverca> clientca <clientca> certificate <certificate> key <key> structured-data audit="true"
  % Only one TLS syslog exporter is supported. Please delete the current TLS syslog exporter before adding a new TLS syslog exporter

Environment

VMware NSX

Cause

When UDP or TCP is specified as the protocol, additional configurations can be applied to an existing syslog server. However, by design, this is not possible when using TLS.

Resolution

Delete the existing syslog server using the del logging-server command, and then execute the set logging-server command with the additional configurations.