<?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 Cluster configuration issues in Sim in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/cluster-configuration-issues-in-sim/m-p/4327614#M35683</link>
    <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a Sim V5.2 SP2 system.  &lt;BR /&gt; &lt;BR /&gt;Sim is monitoring a Windows 2003 Cluster with MS SQL installed.  We discovered the cluster nodes and they added to SIM.  The cluster virtual name was discovered by SIM and shows all the physical nodes.  After an overnight discovery runs SIM adds the SQL virtual name and group IP for the SQL clustered groups.  The IP address is added to the node and changes both the server name and network name.  If we check don’t let the discovery change the server name it holds the server name but the network name still changes to the SQL virtual name.  This prevents the smh from launching properly.  Does anyone have a way around this?&lt;BR /&gt;&lt;BR /&gt;Thanks,  Dave&lt;BR /&gt;</description>
    <pubDate>Mon, 22 Dec 2008 20:18:10 GMT</pubDate>
    <dc:creator>David Brichacek</dc:creator>
    <dc:date>2008-12-22T20:18:10Z</dc:date>
    <item>
      <title>Cluster configuration issues in Sim</title>
      <link>https://community.hpe.com/t5/server-management-systems/cluster-configuration-issues-in-sim/m-p/4327614#M35683</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;We have a Sim V5.2 SP2 system.  &lt;BR /&gt; &lt;BR /&gt;Sim is monitoring a Windows 2003 Cluster with MS SQL installed.  We discovered the cluster nodes and they added to SIM.  The cluster virtual name was discovered by SIM and shows all the physical nodes.  After an overnight discovery runs SIM adds the SQL virtual name and group IP for the SQL clustered groups.  The IP address is added to the node and changes both the server name and network name.  If we check don’t let the discovery change the server name it holds the server name but the network name still changes to the SQL virtual name.  This prevents the smh from launching properly.  Does anyone have a way around this?&lt;BR /&gt;&lt;BR /&gt;Thanks,  Dave&lt;BR /&gt;</description>
      <pubDate>Mon, 22 Dec 2008 20:18:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/cluster-configuration-issues-in-sim/m-p/4327614#M35683</guid>
      <dc:creator>David Brichacek</dc:creator>
      <dc:date>2008-12-22T20:18:10Z</dc:date>
    </item>
    <item>
      <title>Re: Cluster configuration issues in Sim</title>
      <link>https://community.hpe.com/t5/server-management-systems/cluster-configuration-issues-in-sim/m-p/4327615#M35684</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt; as a short term fix try excluding it from discovery. &lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Tue, 23 Dec 2008 21:14:45 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/cluster-configuration-issues-in-sim/m-p/4327615#M35684</guid>
      <dc:creator>marsh_1</dc:creator>
      <dc:date>2008-12-23T21:14:45Z</dc:date>
    </item>
  </channel>
</rss>

