Quantcast
Channel: VMware Communities : All Content - All Communities
Viewing all articles
Browse latest Browse all 179681

configure-esxi problems

$
0
0

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


Viewing all articles
Browse latest Browse all 179681

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>