sflanders
Commander
Commander

1. Yes this is expected behavior. ESXi 5.x support multiple loghost entries and to ensure a user does not accidentally remove old loghost entries configure-esxi requires a separate command to remove a loghost. ESXi 4.x only supports a single loghost and as such configure-esxi comes with the -f flag to override the existing entry. You will notice when using --help that -t will configure a syslog target. This distinction is important as -t can be used for more than just adding a syslog target. For example if you have a loghost 10.10.10.10 configured and then attempt to add tcp://10.10.10.10:1514 then configure-esxi will change 10.10.10.10 to tcp://10.10.10.10:1514 instead of adding a second entry.

2. configure-esxi is provided as a tool for people to use, which is especially helpful for people who do not have existing scripts and do not leverage host profiles. If you have an existing script or host profiles then feel free to use them.

3. I assume you are referring to when configure-esxi detected what it thought was a malformed loghost. Thanks for the feedback, I will ensure it is considered for a future release.

Hope this helps! === If you find this information useful, please award points for "correct" or "helpful". ===

View solution in original post

Reply
0 Kudos