I am configuring the swithces for the SAN and VMWARE environment and the Microsoft cluster uses the heartbeat between servers using 2 NIC cards. the second NIC is connected to a separated VLAN for hearbeat signaling. I prepared the VLAN but it is not working. Microsoft does not have a clue. I am using layer2 only. Does any one knows about any problem related to this case or knows if it is really necessary to have a separated VLAN for the heartbeat?
The IP address of the heartbeat NIC needs to be in a completely different subnet to the other NIC in the server. If you are not connecting the heartbeat NIC to a switch (for geographically separated cluster) VLAN setup is not necessary.
Are the servers in the cluster in the same room? A direct crossover cable is the simplest and most effective way to configure the back-end link between the two servers, whether copper Cat5 UTP or fiber optic.
If Gig Ethernet over copper, you can make a crossover cable using the following pinouts:
Remember, Gig Ethernet uses all four pairs, so they all need to be crossed; Fast Ethernet only uses two of the four pairs, so you can get away with crossing just the first two pairs listed (1,2 and 3,6).
If you don't want to or can't use a crossover cable, then if both servers plug into the same switch just create a VLAN that exists only on those two ports. Configure "spanning-tree portfast" on them too, if you want them to go directly to forwarding traffic as soon as they see a link.
If you're going across several switches in order to geographically disperse your servers, you should make sure that the heartbeat VLAN gets priority across any VLAN trunks, so that the heartbeat doesn't get drowned out by high-volume traffic on the trunks.
We are pleased to announce availability of Beta software for 16.6.3. 16.6.3 will be the second rebuild on the 16.6 release train targeted towards Catalyst 9500/9400/9300/3850/3650 switching platforms. We are looking for early feedback from custome...