"Remote Logging Not Configured" alarm does not identify the affected ESXi Host

Products

• VMware NSX

Issue/Introduction

• The Remote Logging Not Configured alarm is triggered.
• Verification using the API GET /api/v1/configs/central-config/logging-servers confirms that NSX Managers and Edges are correctly configured : List all nodes logging-server configuration status.
• However, the alarm details do not identify which ESXi Host is missing the configuration.

Environment

VMware NSX

Cause

This is a known limitation in the current NSX design.

Resolution

Run the ESXi CLI command esxcli system syslog config get to confirm the configuration. The following is an example output from an ESXi host that is not configured.

[root@esxi:~] esxcli system syslog config get
   Allow Vsan Backing: false
   Check Certificate Revocation List: false
   Dropped Log File Rotation Size: 100
   Dropped Log File Rotations: 10
   Enforce SSLCertificates: true
   Local Log Output: /scratch/log
   Local Log Output Is Configured: false
   Local Log Output Is Persistent: true
   Local Logging Default Rotation Size: 1024
   Local Logging Default Rotations: 8
   Log Level: error
   Log To Unique Subdirectory: false
   Message Queue Drop Mark: 90
   Remote Host: <none>
   Remote Host Connect Retry Delay: 180
   Remote Host Maximum Message Length: 4096
   Strict X509Compliance: false