Heartbeat network

Mikdilly

Trying to setup a vlan for heartbeat network between 2 VM's residing on different hosts, both hosts are connected to the same physical switch, both ports on switch have been added to vlan created on switch. These 2 Vm's will be the only nodes on the the vlan, both VM's have been given static addresses on 10.1.0, can't get the 2 VM's to connect. Separate vswitch has been setup on each host, port group added and given VLAN id of 5. 2nd adapters added to each VM and assigned to vlan 5,. The vmnic has been checked to match the physical nic on the host that is connected to the physical switch. With this kind of setup I assume i'm using VST, the physical switch is a Linksys slm2008, it looks like the breakdown is on the switch, did a port mirror and when 1st vm pings the 2nd vm there is arp broadcast sent out from vmware_8a:21:de looking for the pinged address, looks as though vlans are not setup correctly, is anyone famiiar with vlan setup on these switches?

wedge1988

There could be a number of reasons why this isnt working. break it down more. (You mentioned some of the below but for simplifying it):

1. you say both ports are added to the same VLAN? Add the heartbeat to a separate VLAN.

2. 10.1.0.? /? Correct subnet configured?

3. vmware sometimes needs a reboot for settings to be loaded. check your MTU settings also, they should be 1500 for a heartbeat and 9000 for iSCSi is the switch supports jumbo frames

4. I don't set VLAN's in vmware, i only set them on the switch, this simplifies things for me, but if you want to be **** feel free - I would probably also add the virtual port (The NIC in the virtual machine) to VLAN 5 if you have not already also.

5. Do you have the physical setup connected properly? This is just as important as the virtual setup!

6. If you can't figure it out, put it back to the native vlan, and do each step as you did before to find the step causing you the issue.

Hope this helps?

meadIT

Mikdilly wrote: »

Separate vswitch has been setup on each host, port group added and given VLAN id of 5. 2nd adapters added to each VM and assigned to vlan 5,. The vmnic has been checked to match the physical nic on the host that is connected to the physical switch.

So, you have a separate port group and vmnic just for this vlan, correct? On the physical switch, do you have the port set to vlan 5? If so, that will be your problem. If the switch is set to vlan 5, or even if it is a trunk with vlan 5 untagged, that will cause this issue. You should have either the vswitch or the physical switch set to vlan 5, but not both. The following configs should work:

1) vswitch tagged with vlan 5, physical switch set to trunk with vlan 5 tagged
or
2) vswitch with no vlan assigned, physical switch set to port access vlan 5
or
3) vswitch with no vlan assigned, physical switch set to trunk with vlan 5 untagged

Mikdilly

Thanks for the replies, was going to use setup steps from this page(http://www.jarmanator.net/kb/slm2008vlan.htm) but looks like i need to move all existing connections to another connected switch first. All i want is for the switch to bridge and isolate 2 ports onto their own private network. The switch should be able to route one vlan's traffic that comes in 1 port and send it out another port, right? I don't need a router in order to get the traffic out of the switch, the switch should be able handle this on it's own, this vlan's traffic doesn't need to go any further upstream. All i plan to have connected to this switch is 1 connection from each host but it looks like 1 of the connections needs to be a trunk.

sratakhin

You don't need another switch. Just set up the one you have properly. Untag the two porst on the switch in the hearbeat vlan and then create two vSwitches without specifying the VLAN number in VMware.

Mikdilly

Nothing seems to work, here's current setup on switch with port 2 as trunk using instructions from post on cisco forum:








Port group on 1 host, similar port group added to 2nd host:



Vswitch with port groups with or without vlan id's don't make a difference in getting connected.

From the cisco support forum:

"What you'll want to do first on your SLM200x is go to the VLAN tab and create the VLANs that you would like your switch to use. As you create them, decide which port you want to be your trunked port and check both that port, and the port you want that VLAN to be on.

Example: My uplink port (and the port I want to be the trunk port) is port 1 and I want port 2 to be in VLAN 5. I click the VLAN tab, type in 5 for VLAN ID and click Add. In the next screen I check the box next to port 1 and port 2, then save changes.

Once you've done that, modify VLAN 1 settings and remove all of the ports that you don't want in VLAN 1 (for me this was all of them except port 1). Repeat the process for any other VLANs you wish to create.

Finally what you'll need to do is click the VLAN Port Settings tab and for each port, under PVID, select the VLAN number you want that port to represent."

Little confused as to the need for trunk port, since i have just 2 connections coming from each host into the switch, which one is to be the trunk? Or is it not needed? Seems like i should just be able to assign the ports the hosts are connected to to vlan 5 and let them have at it. It shouldn't be this hard.

sratakhin

Do you really have to use LAGs? Try with a single port and make that port an access port in vlan 5.
If it works, create a LAG and then add another nic to vSwitch. Change your vSwitch settings to "Route based on IP hash".

P.S. Nevermind about the LAG, I misread your post.