Reply to Message

View discussion in a popup

Replying to:
dks00k
Enthusiast
Enthusiast

Thanks for that

I can confirm that appending the port number to the loghost entry resolves the issue. However it raises several other questions....

1.  The new loghost is added to rather than replacing the existing entry requiring . Is this to be the expected behaviour? I'd prefer to see an option to remove all existing and replace with the new.

vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -t 10.80.9.116 -h esxudhsp1.domain.com.au

Configuring hosts connected to vmvchomapp03.domain.com.au to send logs to 10.80.9.116

Host: esxudhsp1.domain.com.au, VMware ESXi 5.1.0, 1065491

Old Syslog.global.logHost: "udp://10.80.8.127:514"

New Syslog.global.logHost: "udp://10.80.8.127:514,10.80.9.116"

Changes successful.

2.  Is the configure-esxi script essential or can we continue to utilise Host Profiles?

3.  When adding all hosts connected to a vCenter, i'd like to see the script continue when it encounters a problem host rather than halting.

Cheers

Reply
0 Kudos