VSAN network

[ChevUribe]

I would like setup a distributed switch with 2 DV portgroups.

one is for VSAN traffic and one is for the production network with VLAN 40.

They will be both using nic0 and nic1 ports.

Do I need the ports in my physical switch connected to my VSAN servers in trunk mode or only in VLAN 40 for these setup?

[zdickinson]

Good morning, I want to make sure I understand correctly.  You have 2 NICs in your servers, NIC0 and NIC1.  You want to run VM traffic and vSAN traffic on these NICs, but on 2 different DV switches.  If that's correct, here's what I would do.

vSAN traffic.

Create DV switch with NIC0 as active and NIC1 as standby

Create a new vLAN for vSAN traffic

Make the ports on the switch trunks

Tag the traffic with the newly created vLAN

VM production traffic

Create DV switch with NIC1 active and NIC0 as standby

Ports on switch would be trunk to support vLAN 40 and new vSAN vLAN.

Tag the traffic with vLAN 40.

Hope that helps.  Thank you, Zach.

[ChevUribe]

no, nic1 and nic 1 are uplink ports for 1 distributed switch.

in these distributed switch, 1 port group is for the production network which is vlan 40.

and another network for vsan traffic (no vlan)

both will be using the same distributed switch.

Can I have a vmkernel with both vmotion and vsan traffic?

[zdickinson]

Good morning, the answer is yes you can have vMotion and vSAN on the same vmKernel.  We do and it works well in our case.  However, it won't work well in all cases.  Yes you can is not equal to you should in every case.  Thank you, Zach.

[ChevUribe]

but since production network (vlan 40) and vsan/vmotion traffic is using the same nics, I need to make the physical port switch to trunk? right?

[zdickinson · Accepted solution]

If they are on separate vLANs, then yes it would need to be a trunk port on the switch and then tag the traffic.  Thank you, Zach.