dks00k's Posts

I guess then it's not possible to export and import data either Steve?? Cheers
HI As an aside to this, will the Certificate file format remain PEM or will the option of PKCS12 also be available akin to most other things vSphere?
Great Thanks very much for that
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 th... See more...
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
Sure Thanks for taking a look... vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -q Password: Querying remote log settings of hosts on vCenter Server: vmvchomapp03.... See more...
Sure Thanks for taking a look... vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -q Password: Querying remote log settings of hosts on vCenter Server: vmvchomapp03.domain.com.au NOTE: configure-esxi will work methodically but not quickly. Large inventories or slow network connections will further slow down execution. Please be patient. Attempting to connect to vCenter Server vmvchomapp03.domain.com.au Host: esxbohsp1.domain.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxbohsp2.domain.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxhdhsp30.domain.com.au, VMware ESXi 5.1.0, 1065491 No remote syslog target set on host esxhdhsp30.domain.com.au Host: esxhdhsp31.domain.com.au, VMware ESXi 5.1.0, 1065491 No remote syslog target set on host esxhdhsp31.domain.com.au Host: esxudhsp30.domain.com.au, VMware ESXi 5.1.0, 1065491 No remote syslog target set on host esxudhsp30.domain.com.au Host: esxudhsp31.domain.com.au, VMware ESXi 5.1.0, 1065491 No remote syslog target set on host esxudhsp31.domain.com.au Host: esxhdhsp1.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.9.73" Host: esxhdhsp2.countryenergy.com.au, VMware ESXi 5.0.0, 1024429 Syslog.global.logHost: "udp://10.80.9.73" Host: vmhdp1.countryenergy.com.au, VMware ESX 3.5.0, 259926 *** WARNING: Skipping host vmhdp1.countryenergy.com.au *** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi. *** See http://kb.vmware.com/kb/1005030 for manual configuration. Host: vmhdp2.countryenergy.com.au, VMware ESX 3.5.0, 259926 *** WARNING: Skipping host vmhdp2.countryenergy.com.au *** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi. *** See http://kb.vmware.com/kb/1005030 for manual configuration. Host: esxhdhsp5.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.9.73" Host: esxhdhsp6.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.9.73" Host: esxhdhsp7.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.8.127" Host: esxhdhsp9.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.9.73" Host: esxhdhsp12.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.9.73" Host: esxhdhsp14.countryenergy.com.au, VMware ESXi 5.0.0, 914586 Syslog.global.logHost: "udp://10.80.8.127" Host: esxhdhsp13.countryenergy.com.au, VMware ESXi 5.0.0, 768111 Syslog.global.logHost: "udp://10.80.9.73" Host: esxhdhsp8.countryenergy.com.au, VMware ESXi 5.0.0, 1024429 Syslog.global.logHost: "udp://10.80.9.73" Host: esxpdhsp2.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxpdhsp1.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxqohsp1.domain.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxqohsp2.domain.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxudhsp6.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxudhsp4.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxudhsp3.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxudhsp1.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxudhsp2.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "udp://10.80.8.127" Host: esxudhsp5.countryenergy.com.au, VMware ESXi 5.1.0, 1065491 Syslog.global.logHost: "10.80.9.116" Host: esxudhsp7.domain.com.au, VMware ESXi 5.1.0, 1065491 No remote syslog target set on host esxudhsp7.domain.com.au Host: esxudhsp8.domain.com.au, VMware ESXi 5.1.0, 1065491 No remote syslog target set on host esxudhsp8.domain.com.au Host: vmudp8.countryenergy.com.au, VMware ESX 3.5.0, 259926 *** WARNING: Skipping host vmudp8.countryenergy.com.au *** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi. *** See http://kb.vmware.com/kb/1005030 for manual configuration. Host: vmudp7.countryenergy.com.au, VMware ESX 3.5.0, 259926 *** WARNING: Skipping host vmudp7.countryenergy.com.au *** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi. *** See http://kb.vmware.com/kb/1005030 for manual configuration.
Hi I am having a problems with the configure-esxi script. I have two vCenters, both 5.1.0 Build 947673. One vCenter contains 4 hosts, the other 32 hosts. The following command worked fla... See more...
Hi I am having a problems with the configure-esxi script. I have two vCenters, both 5.1.0 Build 947673. One vCenter contains 4 hosts, the other 32 hosts. The following command worked flawlessly and configured the 4 hosts without error. All 4 hosts are visible in the Log Insight GUI.... configure-esxi -u vimanager -s vmvchomapp05.domain.com.au -t 10.80.9.116 vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp05.domain.com.au -q Password: Querying remote log settings of hosts on vCenter Server: vmvchomapp05.domain.com.au NOTE: configure-esxi will work methodically but not quickly. Large inventories or slow network connections will further slow down execution. Please be patient. Attempting to connect to vCenter Server vmvchomapp05.domain.com.au Host: esxhdhsp3.domain.com.au, VMware ESXi 5.1.0, 1021289 Syslog.global.logHost: "10.80.9.116" Host: esxhdhsp4.domain.com.au, VMware ESXi 5.1.0, 1021289 Syslog.global.logHost: "10.80.9.116" Host: esxhdhsp10.domain.com.au, VMware ESXi 5.1.0, 838463 Syslog.global.logHost: "10.80.9.116" Host: esxhdhsp11.domain.com.au, VMware ESXi 5.1.0, 838463 Syslog.global.logHost: "10.80.9.116" However, against the 2nd and larger vCenter, I receive the following....... configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -t 10.80.9.116 Password: Configuring hosts connected to vmvchomapp03.domain.com.au to send logs to 10.80.9.116 NOTE: configure-esxi will work methodically but not quickly. Large inventories or slow network connections will further slow down execution. Please be patient. Attempting to connect to vCenter Server vmvchomapp03.domain.com.au Host: esxbohsp1.domain.com.au, VMware ESXi 5.1.0, 1065491 *** WARNING: VMware ESXi 5.1.0, 1065491 has a known issue where if a remote syslog destination becomes *** unavailable the host will stop sending remote syslog messages until the syslog server is *** restarted. Please note that tcp/ssl also experience this behavior. *** See http://kb.vmware.com/kb/2003127 for more information. ERROR: Unsupported <syslog> format Other things I have noted are: Querying the vCenter or a host for currently configured setting works fine Makes no difference if there is a syslog host configured on the host or not. Error persists either way. The format of <syslog> makes no difference, ipaddress, udp://ipaddress:514, hostname all fail I note that Configuration > Software >Advanced Settings > Syslog > Syslog.global.loghost in the vSphere Client is blank for the successfully configured hosts. I assume this is normal behaviour. /etc/vmsyslog.conf is correclty configured I have perused the log files at /var/log/loginsight and see nothing that is useful for my troubleshooting. Any assistance with this issue would be greatly appreciated. Cheers