<?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 MSCS instability in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/mscs-instability/m-p/4236259#M33991</link>
    <description>Hi all,&lt;BR /&gt; I'm still fighting HPSIM ( 5.2 now ) in regard of MSCS .&lt;BR /&gt; We have several mscs clusters ( windows 2003 ) between HP blades , either p-class and c-class .&lt;BR /&gt;&lt;BR /&gt; The problem I'm facing , which I know is an old issue , is the instability of the correct identification.&lt;BR /&gt;&lt;BR /&gt; All the server are configured the same .&lt;BR /&gt;&lt;BR /&gt; I've created some "discovery job" called against each cluster. Each job contains three IP . Two of the physical nodes and the cluster IP .&lt;BR /&gt;&lt;BR /&gt; The problem is that many times the identification process misunderstand one node as the cluster , or viceversa .&lt;BR /&gt;&lt;BR /&gt; I'm desperately looking for a "correct way" to manage MSCS cluster as I'm really upset with this issue .&lt;BR /&gt;&lt;BR /&gt; Has anyone any real good advice on it ?&lt;BR /&gt;&lt;BR /&gt; Thanks in advance &lt;BR /&gt;Stefano</description>
    <pubDate>Fri, 18 Jul 2008 08:20:03 GMT</pubDate>
    <dc:creator>stefano colombo_1</dc:creator>
    <dc:date>2008-07-18T08:20:03Z</dc:date>
    <item>
      <title>MSCS instability</title>
      <link>https://community.hpe.com/t5/server-management-systems/mscs-instability/m-p/4236259#M33991</link>
      <description>Hi all,&lt;BR /&gt; I'm still fighting HPSIM ( 5.2 now ) in regard of MSCS .&lt;BR /&gt; We have several mscs clusters ( windows 2003 ) between HP blades , either p-class and c-class .&lt;BR /&gt;&lt;BR /&gt; The problem I'm facing , which I know is an old issue , is the instability of the correct identification.&lt;BR /&gt;&lt;BR /&gt; All the server are configured the same .&lt;BR /&gt;&lt;BR /&gt; I've created some "discovery job" called against each cluster. Each job contains three IP . Two of the physical nodes and the cluster IP .&lt;BR /&gt;&lt;BR /&gt; The problem is that many times the identification process misunderstand one node as the cluster , or viceversa .&lt;BR /&gt;&lt;BR /&gt; I'm desperately looking for a "correct way" to manage MSCS cluster as I'm really upset with this issue .&lt;BR /&gt;&lt;BR /&gt; Has anyone any real good advice on it ?&lt;BR /&gt;&lt;BR /&gt; Thanks in advance &lt;BR /&gt;Stefano</description>
      <pubDate>Fri, 18 Jul 2008 08:20:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/mscs-instability/m-p/4236259#M33991</guid>
      <dc:creator>stefano colombo_1</dc:creator>
      <dc:date>2008-07-18T08:20:03Z</dc:date>
    </item>
  </channel>
</rss>

