- Posts: 51
- Liked: never
- Joined: Apr 20, 2010 9:00 am
- Full Name: Irina Simkina
To enable syslog on a ESX host you need to modify the /etc/syslog.conf by adding the record like this:
ftp.crit @[collector IP],
where ftp.crit and kern.*- type of errors.
For ESXi you should use VI client.
please refer our MP Operations guide (http://www.veeam.com/files/guide/nworks ... _guide.pdf)
section "APPENDIX B. SYSLOG AND COS FILE SYSTEM USAGE MONITORING" for information how to enable syslog in nworks.
also refer syslog.conf manual to get list of possible errors.
With best regards,
- VP, Product Management
- Posts: 1245
- Liked: 298 times
- Joined: Jan 01, 2006 1:01 am
If you really want to forward EVERYTHING, then you would use
*.* [collector IP]
and replace [collector IP] with the IP address of your Collector.
However I would be careful when forwarding ALL Syslog messages - Syslog can be very verbose. You could get hundreds or even thousands of events forwarded. Are you sure you want to see absolutely everything that syslog generates?
And can I ask why you want to see Syslog messages at all? The messages we get from our default VMware API connection are generally much more useful and informative.....
Users browsing this forum: No registered users and 2 guests