https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922268#M15971 Are you using teaming on the heartbeat?<BR /><BR />Don't! Set your HB up as a simple connection only using just 1 NIC on either side. <BR /><BR />Disable everything on the HB except for TCP/IP (this includes the Microsoft clients). In the Cluster manager, set it up so that the HB connection is highest priority. Configure the client connection (your main NIC team) so that it supports client and cluster communication. That way you get redundancy if the HB NIC combo fails. Make sure you HB IP nets are completely out of any other range used in your network - I had a prob once where the HB had a net IP address which was used elsewhere and the cluster was trying to route traffic up the HB. Mon, 10 Mar 2003 06:56:57 GMT Tony Glynn_1 2003-03-10T06:56:57Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922267#M15970 I have a HP Proliant DL 380 G3 Running Windows 2000 SP 3 with 4 NIC cards installed. I have the 2 integrated NICS (Compaq NC7781)and 2 NC7131. I have them set up with two NIC teams with one NC7781 NIC and one NC7131 NIC in each team. I am experiencing issues with one of these teams. I have a degraded status on the NIC team and when monitoring it shows a heartbeat error on one of the network connections. I swapped network cables and the problem follows, but the network guys have double checked and say nothing is different between any of the network connections.<BR /><BR />Any clues here as to what might be causing my heartbeat error?<BR /> Fri, 07 Mar 2003 16:34:18 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922267#M15970 Jim Odom 2003-03-07T16:34:18Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922268#M15971 Are you using teaming on the heartbeat?<BR /><BR />Don't! Set your HB up as a simple connection only using just 1 NIC on either side. <BR /><BR />Disable everything on the HB except for TCP/IP (this includes the Microsoft clients). In the Cluster manager, set it up so that the HB connection is highest priority. Configure the client connection (your main NIC team) so that it supports client and cluster communication. That way you get redundancy if the HB NIC combo fails. Make sure you HB IP nets are completely out of any other range used in your network - I had a prob once where the HB had a net IP address which was used elsewhere and the cluster was trying to route traffic up the HB. Mon, 10 Mar 2003 06:56:57 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922268#M15971 Tony Glynn_1 2003-03-10T06:56:57Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922269#M15972 No Clustering at. Just using NIC teaming for hardware fault tolerance. Should I uncheck the box for heartbeat during NIC team setup? What is the Heartbeat used for?<BR /><BR />Thanks,<BR /><BR />Jim Mon, 10 Mar 2003 14:07:51 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922269#M15972 Jim Odom 2003-03-10T14:07:51Z https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922270#M15973 Sorry Jim,<BR /><BR />I just assumed that heartbeat meant cluster! I'm assuming that in a FT Team it determines if the other NICS are alive and connected. Which teaming are you using? My preference is always ALB - gives you full transmit bandwidth with fault tolerance Mon, 10 Mar 2003 22:11:53 GMT https://community.hpe.com/t5/proliant-servers-ml-dl-sl/heartbeat-issue-with-compaq-nic-team/m-p/2922270#M15973 Tony Glynn_1 2003-03-10T22:11:53Z