Resolution
Configuration of the syslog service on ESXi 5.0 can be performed using Host Profiles, the vCLI, or the Advanced Configuration options in the vSphere Client. Select the method most appropriate for your environment. Configuration cannot be performed using the
vicfg-syslog command.
There are 5 configurable options. This table outlines the options:
| Option | Description |
Syslog.global.logDir | A location on a local or remote datastore and path where logs are saved to. Has the format [DatastoreName] DirectoryName/Filename, which maps to/vmfs/volumes/DatastoreName/DirectoryName/Filename. The[DatastoreName] is case sensitive and if the specified DirectoryNamedoes not exist, it will be created. If the datastore path field is blank, the logs are only placed in their default location. If /scratch is defined, the default is[]/scratch/log. For more information on scratch, see Creating a persistent scratch location for ESXi (1033696). For all other cases, the default is blank. |
Syslog.global.logHost | A remote server where logs are sent using the syslog protocol. If the logHostfield is blank, no logs are forwarded. Include the protocol and port, similar totcp://hostname:514. |
Syslog.global.logDirUnique | A boolean option which controls whether a host-specific directory is created within the configured logDir. The directory name is the hostname of the ESXi host. A unique directory is useful if the same shared directory is used by multiple ESXi hosts. Defaults to false. |
Syslog.global.defaultRotate | The maximum number of log files to keep locally on the ESXi host in the configured logDir. Does not affect remote syslog server retention. Defaults to 8. |
Syslog.global.defaultSize | The maximum size, in kilobytes, of each local log file before it is rotated. Does not affect remote syslog server retention. Defaults to 1024 KB. For more information on sizing, see Providing Sufficient Space for System Logging. |
Niciun comentariu:
Trimiteți un comentariu