<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: configure-esxi problems in VMware Aria Operations for Logs Discussions</title>
    <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171843#M1721</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The issue is that you already have a remote syslog loghost set and it is not in a configure-esxi supported format. Today, the script allows for &amp;lt;IP&amp;gt;, &amp;lt;Hostname&amp;gt;, &amp;lt;FQDN&amp;gt;, or &amp;lt;PROTOCOL&amp;gt;://&amp;lt;IP|Hostname|FQDN&amp;gt;:&amp;lt;PORT&amp;gt;. The issue is the loghost you have set is in the format &amp;lt;PROTOCOL://&amp;lt;IP|Hostname|FQDN&amp;gt; in short, it is missing the :&amp;lt;PORT&amp;gt;. The vSphere documentation does not make it clear that &amp;lt;PROTOCOL://&amp;lt;IP|Hostname|FQDN&amp;gt; is allowed and the configure-esxi script --help states the supported formats. If you try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 11.818181991577148px;"&gt;configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -t udp://10.80.9.116&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 11.818181991577148px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 11.818181991577148px;"&gt;you will see that configure-esxi will not allow it. The problem you are experiencing is that configure-esxi needs to validate the existing loghosts on the ESXi server, but the error message does not tell you what loghost is in the wrong format. I will dig into this a bit more and get this addressed in the configure-esxi script. In the meantime, you will need to change your existing loghosts in the format &amp;lt;PROTOCOL&amp;gt;://&amp;lt;IP|Hostname|FQDN&amp;gt;&amp;nbsp; to one of the supported formats for configure-esxi to work.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Thu, 13 Jun 2013 00:22:05 GMT</pubDate>
    <dc:creator>sflanders</dc:creator>
    <dc:date>2013-06-13T00:22:05Z</dc:date>
    <item>
      <title>configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171840#M1718</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Hi&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I am having a problems with the configure-esxi script.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I have two vCenters, both 5.1.0 Build 947673. One vCenter contains 4 hosts, the other 32 hosts.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;The following command worked flawlessly and configured the 4 hosts without error. All 4 hosts are visible in the Log Insight GUI....&lt;/P&gt;&lt;P&gt;configure-esxi -u vimanager -s vmvchomapp05.domain.com.au -t 10.80.9.116&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp05.domain.com.au -q&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Password:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Querying remote log settings of hosts on vCenter Server: vmvchomapp05.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;NOTE: configure-esxi will work methodically but not quickly. Large inventories&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;or slow network connections will further slow down execution. Please be patient.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Attempting to connect to vCenter Server vmvchomapp05.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp3.domain.com.au, VMware ESXi 5.1.0, 1021289&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "10.80.9.116"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp4.domain.com.au, VMware ESXi 5.1.0, 1021289&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "10.80.9.116"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp10.domain.com.au, VMware ESXi 5.1.0, 838463&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "10.80.9.116"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp11.domain.com.au, VMware ESXi 5.1.0, 838463&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "10.80.9.116"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;However, against the 2nd and larger vCenter, I receive the following....... &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -t 10.80.9.116&lt;/P&gt;&lt;P&gt;Password:&lt;/P&gt;&lt;P&gt;Configuring hosts connected to vmvchomapp03.domain.com.au to send logs to 10.80.9.116&lt;/P&gt;&lt;P&gt;NOTE: configure-esxi will work methodically but not quickly. Large inventories&lt;/P&gt;&lt;P&gt;or slow network connections will further slow down execution. Please be patient.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Attempting to connect to vCenter Server vmvchomapp03.domain.com.au&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Host: esxbohsp1.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/P&gt;&lt;P&gt;*** WARNING: VMware ESXi 5.1.0, 1065491 has a known issue where if a remote syslog destination becomes&lt;/P&gt;&lt;P&gt;*** unavailable the host will stop sending remote syslog messages until the syslog server is&lt;/P&gt;&lt;P&gt;*** restarted. Please note that tcp/ssl also experience this behavior.&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;*** See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://kb.vmware.com/kb/2003127"&gt;http://kb.vmware.com/kb/2003127&lt;/A&gt;&lt;SPAN&gt; for more information.&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;ERROR: Unsupported &amp;lt;syslog&amp;gt; format&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Other things I have noted are:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Querying the vCenter or a host for currently configured setting works fine&lt;/P&gt;&lt;P&gt;Makes no difference if there is a syslog host configured on the host or not. Error persists either way.&lt;/P&gt;&lt;P&gt;The format of &amp;lt;syslog&amp;gt; makes no difference, ipaddress, udp://ipaddress:514, hostname all fail&lt;/P&gt;&lt;P&gt;I note that &lt;STRONG style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt;Configuration&lt;/STRONG&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt; &amp;gt; &lt;/SPAN&gt;&lt;STRONG style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt;Software&lt;/STRONG&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt; &amp;gt;&lt;/SPAN&gt;&lt;STRONG style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt;Advanced Settings&lt;/STRONG&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt; &amp;gt; &lt;/SPAN&gt;&lt;STRONG style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt;Syslog&lt;/STRONG&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt; &amp;gt; &lt;/SPAN&gt;&lt;STRONG style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt;Syslog.global.loghost&lt;/STRONG&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif, 'Bitstream Vera Sans'; font-size: 12px;"&gt; in the vSphere Client&lt;/SPAN&gt; is blank for the successfully configured hosts. I assume this is normal behaviour. /etc/vmsyslog.conf is correclty configured&lt;/P&gt;&lt;P&gt;I have perused the log files at /var/log/loginsight and see nothing that is useful for my troubleshooting.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Any assistance with this issue would be greatly appreciated.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 06:03:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171840#M1718</guid>
      <dc:creator>dks00k</dc:creator>
      <dc:date>2013-06-12T06:03:00Z</dc:date>
    </item>
    <item>
      <title>Re: configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171841#M1719</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Can you post an image of Configuration &amp;gt; Software &amp;gt; Advanced Setting &amp;gt; Syslog for esxbohsp1.domain.com.au? Can you also paste the results of running configure-esxi with the -q flag for the vCenter Server that is not working?&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 12:26:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171841#M1719</guid>
      <dc:creator>sflanders</dc:creator>
      <dc:date>2013-06-12T12:26:40Z</dc:date>
    </item>
    <item>
      <title>Re: configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171842#M1720</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Sure&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks for taking a look...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -q&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Password:&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Querying remote log settings of hosts on vCenter Server: vmvchomapp03.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;NOTE: configure-esxi will work methodically but not quickly. Large inventories&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;or slow network connections will further slow down execution. Please be patient.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Attempting to connect to vCenter Server vmvchomapp03.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxbohsp1.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxbohsp2.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp30.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;No remote syslog target set on host esxhdhsp30.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp31.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;No remote syslog target set on host esxhdhsp31.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp30.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;No remote syslog target set on host esxudhsp30.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp31.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;No remote syslog target set on host esxudhsp31.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp1.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp2.countryenergy.com.au, VMware ESXi 5.0.0, 1024429&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: vmhdp1.countryenergy.com.au, VMware ESX 3.5.0, 259926&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** WARNING: Skipping host vmhdp1.countryenergy.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN&gt;*** See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://kb.vmware.com/kb/1005030"&gt;http://kb.vmware.com/kb/1005030&lt;/A&gt;&lt;SPAN&gt; for manual configuration.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: vmhdp2.countryenergy.com.au, VMware ESX 3.5.0, 259926&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** WARNING: Skipping host vmhdp2.countryenergy.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN&gt;*** See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://kb.vmware.com/kb/1005030"&gt;http://kb.vmware.com/kb/1005030&lt;/A&gt;&lt;SPAN&gt; for manual configuration.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp5.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp6.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp7.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp9.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp12.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp14.countryenergy.com.au, VMware ESXi 5.0.0, 914586&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp13.countryenergy.com.au, VMware ESXi 5.0.0, 768111&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxhdhsp8.countryenergy.com.au, VMware ESXi 5.0.0, 1024429&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.9.73"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxpdhsp2.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxpdhsp1.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxqohsp1.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxqohsp2.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp6.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp4.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp3.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp1.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp2.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "udp://10.80.8.127"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp5.countryenergy.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Syslog.global.logHost: "10.80.9.116"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp7.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;No remote syslog target set on host esxudhsp7.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: esxudhsp8.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;No remote syslog target set on host esxudhsp8.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: vmudp8.countryenergy.com.au, VMware ESX 3.5.0, 259926&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** WARNING: Skipping host vmudp8.countryenergy.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN&gt;*** See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://kb.vmware.com/kb/1005030"&gt;http://kb.vmware.com/kb/1005030&lt;/A&gt;&lt;SPAN&gt; for manual configuration.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Host: vmudp7.countryenergy.com.au, VMware ESX 3.5.0, 259926&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** WARNING: Skipping host vmudp7.countryenergy.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;*** ESX does not support remote configuration of syslog via an API. Consider upgrading to ESXi.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;&lt;SPAN&gt;*** See &lt;/SPAN&gt;&lt;A class="jive-link-external-small" href="http://kb.vmware.com/kb/1005030"&gt;http://kb.vmware.com/kb/1005030&lt;/A&gt;&lt;SPAN&gt; for manual configuration.&lt;/SPAN&gt;&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="one.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/45532i9C25627840BB06D3/image-size/large?v=v2&amp;amp;px=999" role="button" title="one.jpg" alt="one.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="two.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/45533i71BCD7CD952044E9/image-size/large?v=v2&amp;amp;px=999" role="button" title="two.jpg" alt="two.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="three.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/45536iB529B22BACF3000E/image-size/large?v=v2&amp;amp;px=999" role="button" title="three.jpg" alt="three.jpg" /&gt;&lt;/span&gt;&lt;span class="lia-inline-image-display-wrapper" image-alt="four.jpg"&gt;&lt;img src="https://communities.vmware.com/t5/image/serverpage/image-id/45537iCF406B1166404667/image-size/large?v=v2&amp;amp;px=999" role="button" title="four.jpg" alt="four.jpg" /&gt;&lt;/span&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 12 Jun 2013 23:23:00 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171842#M1720</guid>
      <dc:creator>dks00k</dc:creator>
      <dc:date>2013-06-12T23:23:00Z</dc:date>
    </item>
    <item>
      <title>Re: configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171843#M1721</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;The issue is that you already have a remote syslog loghost set and it is not in a configure-esxi supported format. Today, the script allows for &amp;lt;IP&amp;gt;, &amp;lt;Hostname&amp;gt;, &amp;lt;FQDN&amp;gt;, or &amp;lt;PROTOCOL&amp;gt;://&amp;lt;IP|Hostname|FQDN&amp;gt;:&amp;lt;PORT&amp;gt;. The issue is the loghost you have set is in the format &amp;lt;PROTOCOL://&amp;lt;IP|Hostname|FQDN&amp;gt; in short, it is missing the :&amp;lt;PORT&amp;gt;. The vSphere documentation does not make it clear that &amp;lt;PROTOCOL://&amp;lt;IP|Hostname|FQDN&amp;gt; is allowed and the configure-esxi script --help states the supported formats. If you try:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 11.818181991577148px;"&gt;configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -t udp://10.80.9.116&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 11.818181991577148px;"&gt;&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&lt;SPAN style="color: #333333; font-family: Arial, Helvetica, sans-serif; font-size: 11.818181991577148px;"&gt;you will see that configure-esxi will not allow it. The problem you are experiencing is that configure-esxi needs to validate the existing loghosts on the ESXi server, but the error message does not tell you what loghost is in the wrong format. I will dig into this a bit more and get this addressed in the configure-esxi script. In the meantime, you will need to change your existing loghosts in the format &amp;lt;PROTOCOL&amp;gt;://&amp;lt;IP|Hostname|FQDN&amp;gt;&amp;nbsp; to one of the supported formats for configure-esxi to work.&lt;BR /&gt;&lt;/SPAN&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2013 00:22:05 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171843#M1721</guid>
      <dc:creator>sflanders</dc:creator>
      <dc:date>2013-06-13T00:22:05Z</dc:date>
    </item>
    <item>
      <title>Re: configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171844#M1722</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Thanks for that&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;I can confirm that appending the port number to the loghost entry resolves the issue. However it raises several other questions....&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;vmlihdp1:~ # configure-esxi -u vimanager -s vmvchomapp03.domain.com.au -t 10.80.9.116 -h esxudhsp1.domain.com.au&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Configuring hosts connected to vmvchomapp03.domain.com.au to send logs to 10.80.9.116&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-size: 10pt; line-height: 1.5em;"&gt;Host: esxudhsp1.domain.com.au, VMware ESXi 5.1.0, 1065491&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM style="font-size: 10pt; line-height: 1.5em;"&gt;Old Syslog.global.logHost: "udp://10.80.8.127:514"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;New Syslog.global.logHost: "udp://10.80.8.127:514,10.80.9.116"&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;EM&gt;Changes successful.&lt;/EM&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2.&amp;nbsp; Is the configure-esxi script essential or can we continue to utilise Host Profiles?&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;3.&amp;nbsp; 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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Cheers&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2013 01:20:40 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171844#M1722</guid>
      <dc:creator>dks00k</dc:creator>
      <dc:date>2013-06-13T01:20:40Z</dc:date>
    </item>
    <item>
      <title>Re: configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171845#M1723</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;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. &lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2013 02:02:12 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171845#M1723</guid>
      <dc:creator>sflanders</dc:creator>
      <dc:date>2013-06-13T02:02:12Z</dc:date>
    </item>
    <item>
      <title>Re: configure-esxi problems</title>
      <link>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171846#M1724</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Great&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Thanks very much for that&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Thu, 13 Jun 2013 03:32:48 GMT</pubDate>
      <guid>https://communities.vmware.com/t5/VMware-Aria-Operations-for-Logs/configure-esxi-problems/m-p/2171846#M1724</guid>
      <dc:creator>dks00k</dc:creator>
      <dc:date>2013-06-13T03:32:48Z</dc:date>
    </item>
  </channel>
</rss>

