HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
Showing results for 
Search instead for 
Did you mean: 


Occasional Visitor


My heartbeat(NIC) is not failing over.two ml350 with RA4100 storage system.
Martin Breidenbach
Honored Contributor

Re: Clustering

Sorry but I don't understand what you mean.

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.
Doug de Werd
Honored Contributor

Re: Clustering

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.

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.

Expert in ProLiant Clusters
Philip Sharp
Occasional Visitor

Re: Clustering

Hi Muhammand,

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.

What version of OS+SP are you using as behaviour of the cluster under network failure is different between NT, 2000 and 2003.

A scientist discovers that which exists. An engineer creates that which never was.