After reading http://kb.vmware.com/kb/2003322 and doing some experimentation I'm trying to figure out if it is possible to use Host Profiles to configure syslog to use a local VMFS datastore. I have come up with these approaches, none of which do what I want:
1) Create a local VMFS datastore, e.g. "Datastore1", on each host and set "Syslog.global.logDir" to "[Datastore1] /Syslog". The problem with this approach is that I end up with name collision on the Storage view in vCenter.
2) Create a local VMFS datastore, e.g. "<ESXi hostname>--Datastore1", on each host which avoids the name collision problem, but then I can't (apparently) use "Host Profiles".
3) Set "Syslog.global.logDir" to some shared storage and set "Syslog.global.logDirUnique" to True, but then this isn't using a local VMFS datastore.
My concern is that my shared storage is all IP based (both iSCSI and NFS). I was hoping to use a local datastore to add some resiliency to syslog.
Thanks.
Please refer the link https://pubs.vmware.com/vsphere-51/index.jsp?topic=%2Fcom.vmware.vsphere.install.doc%2FGUID-24FDBC4B..., for configuring syslog through host profiles
AishR:
This article seems to apply to the configuration of "Syslog.global.loghost" which is a remote syslog server, i.e. over the wire. I don't see how to specify local storage for syslog files, unless I'm missing something.