<?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 SIM 5.1 VMWare ESX Cluster turns Orphan in Operating System - VMware</title>
    <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422557#M575</link>
    <description>I have a six-node ESX cluster that has five of the nodes turn to orphan within a day of discovery.  If I delete all of them and re-discover, they will initially show up correctly but will all change to Orphan-XXX-HostName within a day.  I'm guessing that there is something about the cluster that is confusing SIM since it leaves one node alone and orphans the other 5.  Any ideas?  I have a dozen other ESX hosts that are OK but this is the only cluster I've got.&lt;BR /&gt;&lt;BR /&gt;I do have one other ESX host that loses its name and reverts back to the serial number.  It seems to lose its IP address at the same time.  Some sort of a DNS problem?  This one host is at the other end of a not 100% reliable radio link from the SIM and DNS servers.</description>
    <pubDate>Tue, 19 May 2009 12:28:53 GMT</pubDate>
    <dc:creator>KenMacEachern</dc:creator>
    <dc:date>2009-05-19T12:28:53Z</dc:date>
    <item>
      <title>SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422557#M575</link>
      <description>I have a six-node ESX cluster that has five of the nodes turn to orphan within a day of discovery.  If I delete all of them and re-discover, they will initially show up correctly but will all change to Orphan-XXX-HostName within a day.  I'm guessing that there is something about the cluster that is confusing SIM since it leaves one node alone and orphans the other 5.  Any ideas?  I have a dozen other ESX hosts that are OK but this is the only cluster I've got.&lt;BR /&gt;&lt;BR /&gt;I do have one other ESX host that loses its name and reverts back to the serial number.  It seems to lose its IP address at the same time.  Some sort of a DNS problem?  This one host is at the other end of a not 100% reliable radio link from the SIM and DNS servers.</description>
      <pubDate>Tue, 19 May 2009 12:28:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422557#M575</guid>
      <dc:creator>KenMacEachern</dc:creator>
      <dc:date>2009-05-19T12:28:53Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422558#M576</link>
      <description>Sorry, I had a typo.  SIM version is 5.3</description>
      <pubDate>Tue, 19 May 2009 12:32:22 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422558#M576</guid>
      <dc:creator>KenMacEachern</dc:creator>
      <dc:date>2009-05-19T12:32:22Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422559#M577</link>
      <description>No one has ever seen this?  Any reasons why a node would change to an orphan?&lt;BR /&gt;&lt;BR /&gt;Anyone have a VMWare cluster being monitored?&lt;BR /&gt;</description>
      <pubDate>Mon, 25 May 2009 16:19:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422559#M577</guid>
      <dc:creator>KenMacEachern</dc:creator>
      <dc:date>2009-05-25T16:19:59Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422560#M578</link>
      <description>Have you solved your case?</description>
      <pubDate>Fri, 11 Sep 2009 06:27:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422560#M578</guid>
      <dc:creator>htulumba</dc:creator>
      <dc:date>2009-09-11T06:27:25Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422561#M579</link>
      <description>No, the problem still exists.  My cluster still shows as orphans.</description>
      <pubDate>Fri, 11 Sep 2009 10:09:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422561#M579</guid>
      <dc:creator>KenMacEachern</dc:creator>
      <dc:date>2009-09-11T10:09:21Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422562#M580</link>
      <description>Have you ESX or ESXi hosts? Which os and agent version? Which ProLiant type?</description>
      <pubDate>Mon, 14 Sep 2009 07:13:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422562#M580</guid>
      <dc:creator>htulumba</dc:creator>
      <dc:date>2009-09-14T07:13:16Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422563#M581</link>
      <description>My servers are a mix of BL460c G1, BL465c G5, BL480c G1 and DL365 G1 running ESXi 4 and 3.5.&lt;BR /&gt;&lt;BR /&gt;The cluste is all 465s running ESXi 4 (but they were originally 3.5)&lt;BR /&gt;&lt;BR /&gt;I have a second cluster that did work (480s with ESXi 4) but when I add two nodes to it the new ones remain as orphans.</description>
      <pubDate>Mon, 14 Sep 2009 10:07:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422563#M581</guid>
      <dc:creator>KenMacEachern</dc:creator>
      <dc:date>2009-09-14T10:07:25Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422564#M582</link>
      <description>Have you installed the software HP ESXi 3.5 update 4 CIM Providers version 2.01.11 Update CD? &lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://bizsupport1.austin.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=3682822&amp;amp;swItem=MTX-3b1f5654f0eb47a1a3b96697e9&amp;amp;prodNameId=3682823&amp;amp;swEnvOID=4025&amp;amp;swLang" target="_blank"&gt;http://bizsupport1.austin.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=3682822&amp;amp;swItem=MTX-3b1f5654f0eb47a1a3b96697e9&amp;amp;prodNameId=3682823&amp;amp;swEnvOID=4025&amp;amp;swLang&lt;/A&gt;&lt;BR /&gt;=13&amp;amp;taskId=135&amp;amp;mode=4&amp;amp;idx=2 &lt;BR /&gt;&lt;BR /&gt;HP has fixed an issue in which the UUID returned by HPÃ¢Â Â s Common Information Model (CIM) providers does not match the UUID returned by iLO. This issue causes HP-SIM (System Insight Manager) to be unable to properly associate the server with its corresponding iLO component, which also causes several side affects within HP-SIM. This issue is resolved in release 2.01.11. &lt;BR /&gt;&lt;BR /&gt;This ISO updates the HP Common Information Model (CIM) providers on ESXi 3.5 U4. This ISO updates HP CIM Providers from 2.01.10 to 2.01.11. Note: This CD does not support upgrades on ESX, only ESXi.</description>
      <pubDate>Mon, 14 Sep 2009 10:11:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422564#M582</guid>
      <dc:creator>htulumba</dc:creator>
      <dc:date>2009-09-14T10:11:40Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 5.1 VMWare ESX Cluster turns Orphan</title>
      <link>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422565#M583</link>
      <description>Have you solved your case?&lt;BR /&gt;</description>
      <pubDate>Tue, 19 Jan 2010 16:25:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-vmware/sim-5-1-vmware-esx-cluster-turns-orphan/m-p/4422565#M583</guid>
      <dc:creator>htulumba</dc:creator>
      <dc:date>2010-01-19T16:25:45Z</dc:date>
    </item>
  </channel>
</rss>

