<?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: Clustering in Server Clustering</title>
    <link>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034335#M6</link>
    <description>Hi Muhammand,&lt;BR /&gt;&lt;BR /&gt;From your description, the other guys are right, it is difficult to ascertain what your exact problem is! Have you a sketch of the system you can attach in word format etc.&lt;BR /&gt;&lt;BR /&gt;What version of OS+SP are you using as behaviour of the cluster under network failure is different between NT, 2000 and 2003.&lt;BR /&gt;&lt;BR /&gt;Phil&lt;BR /&gt;</description>
    <pubDate>Wed, 06 Aug 2003 02:49:01 GMT</pubDate>
    <dc:creator>Philip Sharp</dc:creator>
    <dc:date>2003-08-06T02:49:01Z</dc:date>
    <item>
      <title>Clustering</title>
      <link>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034332#M3</link>
      <description>My heartbeat(NIC) is not failing over.two ml350 with RA4100 storage system.</description>
      <pubDate>Sat, 26 Jul 2003 20:54:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034332#M3</guid>
      <dc:creator>Muhammad_4</dc:creator>
      <dc:date>2003-07-26T20:54:31Z</dc:date>
    </item>
    <item>
      <title>Re: Clustering</title>
      <link>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034333#M4</link>
      <description>Sorry but I don't understand what you mean.&lt;BR /&gt;&lt;BR /&gt;You say the heartbeat nic doesn't fail over. On each node a NIC should be configured for heartbeat and during a failover it keeps the IP address that is used for internal cluster communication.&lt;BR /&gt;</description>
      <pubDate>Mon, 28 Jul 2003 07:39:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034333#M4</guid>
      <dc:creator>Martin Breidenbach</dc:creator>
      <dc:date>2003-07-28T07:39:42Z</dc:date>
    </item>
    <item>
      <title>Re: Clustering</title>
      <link>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034334#M5</link>
      <description>Yes, it's difficult to understand the problem. It might be helpful if you could provide more details regarding your network configuration, and also describe what symptoms you are observing.&lt;BR /&gt;&lt;BR /&gt;You should check that you are using static IP addresses for the heartbeat and public networks, as well as for any cluster groups - do not use DHCP for any of these. Also, the 2 NICs used for the heartbeat should ber on the same IP subnet, and this should be different from the NICs used for the public LAN (which also need to be on the same IP subnet.&lt;BR /&gt;&lt;BR /&gt;Thanks,&lt;BR /&gt;Doug</description>
      <pubDate>Mon, 28 Jul 2003 13:15:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034334#M5</guid>
      <dc:creator>Doug de Werd</dc:creator>
      <dc:date>2003-07-28T13:15:27Z</dc:date>
    </item>
    <item>
      <title>Re: Clustering</title>
      <link>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034335#M6</link>
      <description>Hi Muhammand,&lt;BR /&gt;&lt;BR /&gt;From your description, the other guys are right, it is difficult to ascertain what your exact problem is! Have you a sketch of the system you can attach in word format etc.&lt;BR /&gt;&lt;BR /&gt;What version of OS+SP are you using as behaviour of the cluster under network failure is different between NT, 2000 and 2003.&lt;BR /&gt;&lt;BR /&gt;Phil&lt;BR /&gt;</description>
      <pubDate>Wed, 06 Aug 2003 02:49:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-clustering/clustering/m-p/3034335#M6</guid>
      <dc:creator>Philip Sharp</dc:creator>
      <dc:date>2003-08-06T02:49:01Z</dc:date>
    </item>
  </channel>
</rss>

