This article explains the ESXi 5 syslog in simple terms and its configuration.
As all of you know, logs are the critical in troubleshooting any issue and they should be persistent after the system reboot. Syslog exactly does the same with couple of options, either to store logs on persistent scratch partition (local disk/ datastore) or on a remote syslog server.
How to configure syslog on ESXi 5.0 from vSphere Client
2. Then navigate to "Configuration- Advanced Settings"
3. Then select “Syslog” and check Syslog.global.logDirUnique (This option places logs in a unique subdirectory of logdir, based on hostname)
4. And enter your syslog server name in tcp://<Syslog server IP>:514
5. If you are configuring the syslog to dump log files to local or VMFS datastore, enter datasore details at “Syslog.global.logDir” in “[DatastoreName] DirectoryName/Filename” format
To configure Syslog from command prompt
1. Login to ESXi host via Putty/ SSH or tech support mode and enter following commands.
esxcli system syslog config set --loghost=udp://xxx.xxx.xxx.xxx:514
2. To load the new Syslog configuration execute following command
esxcli system syslog reload
Screenshot form VMware with explanation on various syslog settings.
Error: Call "OptionManager.UpdateValues" for object "EsxHostAdvSettings-1030" on vCenter Server "ESXhost1.local" failed
Reason for the above error can be Syslog host, datastore is not reachable or syntax error. First make sure that you are entering the correct details.
- Then check whether you can navigate/ connect to sthe yslog datastore or remote server and try again.
- If you still fail, try executing command from command prompt to get more understanding on what is happening.
- Or execute “esxcli system syslog reload” command and then try configuring the syslog.
- Sometimes you get “Failed to resolve remote host” error when you are configuring Syslog from command prompt. Again it could be because of wrong syntax or there is a firewall between remote syslog server and ESXi host