How to handle missing remote logging server alarm
Article ID: 345834
Updated On:
Products
VMware NSX Networking
Issue/Introduction
Title: Alarm for logging.missing_remote_logging_server
Event ID: logging.missing_remote_logging_server
Added in release: 4.1.2
Alarm Description
1. Invoke API GET /api/v1/configs/central-config/logging-servers to see the nodes on which remote logging is not configured.
2. 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. Please 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.
3. 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 and use ESXi CLI esxcli system syslog config get and check Remote Host in response to confirm if the remote logging server has been configured.
4. If your setup only contains NSX Manager and Edge nodes, we recommend you 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.
Event ID: logging.missing_remote_logging_server
Added in release: 4.1.2
Alarm Description
- Purpose: Indicates whether a remote logging server is configured.
- 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.
1. Invoke API GET /api/v1/configs/central-config/logging-servers to see the nodes on which remote logging is not configured.
2. 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. Please 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.
3. 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 and use ESXi CLI esxcli system syslog config get and check Remote Host in response to confirm if the remote logging server has been configured.
4. If your setup only contains NSX Manager and Edge nodes, we recommend you 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.
Environment
VMware NSX-T Data Center
Additional Information
Admin Guide: https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-B4AE1432-690E-480E-91C4-903C1E549C23.html
https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-8085C57D-681A-4435-83A3-CB21C98F4A93.html
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-esxi-installation/GUID-58D496FD-BB6E-4E2D-A68B-E6533B9193DE.html
https://docs.vmware.com/en/VMware-NSX/4.1/administration/GUID-8085C57D-681A-4435-83A3-CB21C98F4A93.html
https://docs.vmware.com/en/VMware-vSphere/8.0/vsphere-esxi-installation/GUID-58D496FD-BB6E-4E2D-A68B-E6533B9193DE.html
Feedback
Yes
No
Powered by
