<?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 Orphaned virtual servers in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/orphaned-virtual-servers/m-p/3592188#M13326</link>
    <description>I have a few virtual servers on clustered Windows 2003 servers.  They all 'discovered' normally, but after a few days two of them showed up as orphans (top portion of attached image).  If I hovered over the 'Orphan_XX', the true name of the server was displayed. If I clicked the link I was taken to the information page of the server (bottom half of the attached image), which showed all the correct information.&lt;BR /&gt;&lt;BR /&gt;I could ping the 'v001002' server, attach to it, I verified all the DNS info, but the CMS still showed a red "system unreachable" icon.  If I went to "Edit System Properties" under the links tab, I could change the 'preferred system name', but it still came back as unreachable.&lt;BR /&gt;&lt;BR /&gt;I tried to delete and re-discover these two servers (v001002 &amp;amp; v001003), but they almost seem to be mutually exclusive.  If I discover v001002, then v001003 disappears from the All Systems list (and vice-versa).  Which ever 'V' server displays, the hyperlink to the system information does not work (no response to click).&lt;BR /&gt;&lt;BR /&gt;I'm thinking of deleting all the virtual server names and only monitoring the underlying cluster server hosts.  Any other suggestions before I do that?  Is it possible that this has happened because the cluster has changed active servers? (The reason I ask this is when it was working originally, the links on the 'Links' page would show the 'V' server name, but direct me to the active cluster server.)</description>
    <pubDate>Thu, 28 Jul 2005 14:41:06 GMT</pubDate>
    <dc:creator>Pat Wilson_1</dc:creator>
    <dc:date>2005-07-28T14:41:06Z</dc:date>
    <item>
      <title>Orphaned virtual servers</title>
      <link>https://community.hpe.com/t5/server-management-systems/orphaned-virtual-servers/m-p/3592188#M13326</link>
      <description>I have a few virtual servers on clustered Windows 2003 servers.  They all 'discovered' normally, but after a few days two of them showed up as orphans (top portion of attached image).  If I hovered over the 'Orphan_XX', the true name of the server was displayed. If I clicked the link I was taken to the information page of the server (bottom half of the attached image), which showed all the correct information.&lt;BR /&gt;&lt;BR /&gt;I could ping the 'v001002' server, attach to it, I verified all the DNS info, but the CMS still showed a red "system unreachable" icon.  If I went to "Edit System Properties" under the links tab, I could change the 'preferred system name', but it still came back as unreachable.&lt;BR /&gt;&lt;BR /&gt;I tried to delete and re-discover these two servers (v001002 &amp;amp; v001003), but they almost seem to be mutually exclusive.  If I discover v001002, then v001003 disappears from the All Systems list (and vice-versa).  Which ever 'V' server displays, the hyperlink to the system information does not work (no response to click).&lt;BR /&gt;&lt;BR /&gt;I'm thinking of deleting all the virtual server names and only monitoring the underlying cluster server hosts.  Any other suggestions before I do that?  Is it possible that this has happened because the cluster has changed active servers? (The reason I ask this is when it was working originally, the links on the 'Links' page would show the 'V' server name, but direct me to the active cluster server.)</description>
      <pubDate>Thu, 28 Jul 2005 14:41:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/orphaned-virtual-servers/m-p/3592188#M13326</guid>
      <dc:creator>Pat Wilson_1</dc:creator>
      <dc:date>2005-07-28T14:41:06Z</dc:date>
    </item>
  </channel>
</rss>

