Log messages to logging server vmwNsxTDataCenterHostnameOrIPAddressWithPort (vmwNsxTDataCenterEntityId) cannot be delivered possibly due to an unresolvable FQDN, an invalid TLS certificate or missing NSX appliance iptables rule. Action required: 1. Ensure that vmwNsxTDataCenterHostnameOrIPAddressWithPort is the correct hostname or IP address and port. 2. If the logging server is specified using a FQDN, ensure the FQDN is resolvable from the NSX appliance using the NSX CLI command `nslookup <fqdn>`. If not resolvable, verify the correct FQDN is specified and the network DNS server has the required entry for the FQDN. 3. If the logging server is configured to use TLS, verify the specified certificate is valid. For example, ensure the logging server is actually using the certificate or verify the certificate has not expired using the openssl command `openssl x509 -in <cert-file-path> -noout -dates`. 4. NSX appliances use iptables rules to explicitly allow outgoing traffic. Verify the iptables rule for the logging server is configured properly by invoking the NSX CLI command `verify logging-servers` which re-configures logging server iptables rules as needed. 5. If for any reason the logging server is misconfigured, it should be deleted using the NSX CLI `del logging-server <hostname-or-ip-address[:port]> proto <proto> level <level>` command and re-added with the correct configuration.