syslog configuration of NSX Controller Attributes results in "Invalid Parameter(s) - syslogServer" if non TLD FQDN is specified
search cancel

syslog configuration of NSX Controller Attributes results in "Invalid Parameter(s) - syslogServer" if non TLD FQDN is specified

book

Article ID: 332495

calendar_today

Updated On:

Products

VMware NSX Networking

Issue/Introduction

Symptoms:
Attempting to configure syslog as a FQDN in NSX Controller Attributes may result in the following error:
"errorCode":408,"details":"Invalid Parameter(s) - syslogServer.","rootCauseString":null,"moduleName":"core-services"
 
The controller cluster DNS is set correctly:

[root@nsxmgr-01a /home/secureall/secureall]# curl -k -u admin -H 'Content-Type:application/xml' -X GET https://nsxmgr-01a.corp.local/api/2.0/vdn/controller/cluster/dns
Enter host password for user 'admin': VMware1!VMware1!
<?xml version="1.0" encoding="UTF-8"?>
<ControllerClusterDns><dnsServer>192.168.110.10</dnsServer><dnsSuffix>corp.local</dnsSuffix></ControllerClusterDns>[root@nsxmgr-01a /home/secureall/secureall]#

NSX Controller can resolve syslog.corp.local successfully from the OS level:

nsx-controller # ping syslog.corp.local
PING syslog.corp.local (192.168.110.10) 56(84) bytes of data.
64 bytes from controlcenter.corp.local (192.168.110.10): icmp_seq=1 ttl=128 time=0.886 ms
64 bytes from controlcenter.corp.local (192.168.110.10): icmp_seq=2 ttl=128 time=0.903 ms
64 bytes from controlcenter.corp.local (192.168.110.10): icmp_seq=3 ttl=128 time=1.56 ms
64 bytes from controlcenter.corp.local (192.168.110.10): icmp_seq=4 ttl=128 time=1.13 ms
^C
--- syslog.corp.local ping statistics ---
4 packets transmitted, 4 received, 0% packet loss, time 3005ms
rtt min/avg/max/mdev = 0.886/1.120/1.563/0.276 ms

The following works, when specifying syslog as an IP address:

[root@nsxmgr-01a /home/secureall/secureall]# curl -k -u admin -H 'Content-Type:application/xml' -X PUT https://nsxmgr-01a.corp.local/api/2.0/vdn/controller/cluster/syslog -d '<ControllerSyslogServerList><controllerSyslogServer><syslogServer>192.168.110.10</syslogServer><port>999</port><protocol>UDP</protocol><level>ERROR</level></controllerSyslogServer></ControllerSyslogServerList>'
Enter host password for user 'admin':
<?xml version="1.0" encoding="UTF-8"?>
<ControllerSyslogServerList><controllerSyslogServer><syslogServer>192.168.110.10</syslogServer><port>999</port><protocol>UDP</protocol><level>ERROR</level></controllerSyslogServer></ControllerSyslogServerList>[root@nsxmgr-01a /home/secureall/secureall]#

With ControllerClusterDns set up correctly, the following fails, when specifying syslog as a FQDN:


curl -k -u admin -H 'Content-Type:application/xml' -X PUT https://nsxmgr-01a.corp.local/api/2.0/vdn/controller/cluster/syslog -d '<ControllerSyslogServerList><controllerSyslogServer><syslogServer>syslog.corp.local</syslogServer><port>999</port><protocol>UDP</protocol><level>ERROR</level></controllerSyslogServer></ControllerSyslogServerList>'
Enter host password for user 'admin':
{"errorCode":408,"details":"Invalid Parameter(s) - syslogServer.","rootCauseString":null,"moduleName":"core-services","errorData":null}

The following works successfully, when specifying syslog as a TLD FQDN,
syslog.corp.local.com:

[root@nsxmgr-01a /home/secureall/secureall/nikhil]# curl -k -u admin -H 'Content-Type:application/xml' -X PUT https://nsxmgr-01a.corp.local/api/2.0/vdn/controller/cluster/syslog -d '<ControllerSyslogServerList><controllerSyslogServer><syslogServer>syslog.local.corp</syslogServer><port>999</port><protocol>UDP</protocol><level>ERROR</level></controllerSyslogServer></ControllerSyslogServerList>'
Enter host password for user 'admin':
<?xml version="1.0" encoding="UTF-8"?>
<ControllerSyslogServerList><controllerSyslogServer><syslogServer>syslog.corp.local.com</syslogServer><port>999</port><protocol>UDP</protocol><level>ERROR</level></controllerSyslogServer></ControllerSyslogServerList>


Cause

This is a known issue impacting all versions of NSX-V.

Resolution

There is no resolution at this time.  This is to be fixed in upcoming version of 6.4.7

Workaround:
To workaround this issue, configure syslog as an IP Address or as an Top Level Domain (TLD) FQDN., where a TLD FQDN ends in .com, .net, .org, .co.uk, etc.