Alarm Remote Logging Not Configured Displayed for NSX Nodes or ESXi Hosts

Products

• VMware NSX

Issue/Introduction

The NSX Manager displays an alarm indicating remote logging is not configured: Alarm for Remote Logging Not Configured Event ID: logging.remote_logging_not_configured

Appliance and host log disk space is constrained. Log rotation is utilized to control local disk consumption. Without a centralized syslog server, rotated logs are purged, limiting historical log availability during root cause analysis.

Environment

VMware NSX 

Cause

The alarm fires when NSX Manager, Edge nodes, or ESXi hosts lack an active remote syslog configuration, or when alarm state desynchronization occurs after external configuration deployment.

Resolution

1. Identify unconfigured nodes via the NSX Manager API: GET /api/v1/configs/central-config/logging-servers

2. Configure remote logging:

   • Option A: NSX Nodes (Recommended via Node Profile) Navigate to System > Fabric > Profiles > Node Profiles > All NSX Nodes. Configure the remote logging server details under the Syslog Servers section.

   • Option B: NSX Manager / Edge Nodes (CLI) Execute the following command on the target node CLI: set logging-server <hostname-or-ip-address[:port]> proto <proto> level <level> Validate configuration: get logging-servers

   • Option C: ESXi Hosts (CLI) Execute the following commands on the target ESXi host CLI: esxcli system syslog config set --loghost=<str> esxcli system syslog reload Validate configuration: esxcli system syslog config get

3. If remote logging is validated as active via CLI but the alarm remains active in NSX Manager, toggle the configured logging level in the UI or CLI to trigger a configuration resynchronization and clear the alert.

Additional Information

Configure a Node Profile

Configure Remote Logging (NSX)

The NSX Manager is showing alarms indicating that 'one or more ESXi nodes are not currently configured to forward log messages to a remote logging server.'

Remote Logging Not Configured のアラーム