Remote Logging Not Configured alarm
search cancel

Remote Logging Not Configured alarm

book

Article ID: 345834

calendar_today

Updated On:

Products

VMware NSX

Issue/Introduction

Title: Alarm for Remote Logging Not Configured
Event ID: logging.remote_logging_not_configured

Alarm Description

  • Purpose: Indicates if remote logging server is not configured for NSX appliances or the ESX hosts.
  • Impact: There is limited disk space on nodes to store log messages. Log rotation is used to limit the amount of space each log file consumes. If a remote logging server is not configured, then the rotated log messages are lost which makes it difficult to triage issues.

Environment

VMware NSX 

Cause

The alarm is raised to highlight that the appliance(s) or the ESXi hosts do not have a remote logging server configured.

Disk space on the appliances is limited; therefore, logs must be rolled over to prevent disk space exhaustion. If an issue occurred in the past and the logs have already rolled over, there may be insufficient data to help identify the root cause.

If you do not wish to configure a remote logging server, this may be considered the desired state. In that case, the alarm should be acknowledged and resolved manually.

Resolution

Steps to resolve
For version 4.1.2 and above

Recommended Action:

  1. Invoke API GET /api/v1/configs/central-config/logging-servers to see the nodes on which remote logging is not configured.
  2. It is recommended to use Node Profile to configure the remote logging server. Go to System -> Fabric -> Profiles -> Node Profiles -> All NSX Nodes and configure the remote logging server in the Syslog Servers section. The configuration will be applied on all NSX Manager and Edge nodes.
  3. Alternatively For NSX Manager, Global Manager and Edge nodes, use NSX CLI set logging-server <hostname-or-ip-address[:port]> proto <proto> level <level> to configure a remote logging server and use NSX CLI get logging-servers to confirm if a remote logging server has been configured.

    Note: Choose the logging level based on the user requirements to avoid full the remote logging server's disk space. Valid logging level operation includes: emerg, alert, crit, err, warning, notice, info, debug.

  4. For ESXi nodes, use ESXi CLI esxcli system syslog config set --loghost=<str> and then esxcli system syslog reload to configure a remote logging server. Use ESXi CLI esxcli system syslog config get to confirm the configuration. See Configuring Syslog on ESXi.


Maintenance required for remediation? No

Additional Information

Powered by Wolken Software