VSAN traffic

[ChevUribe]

I would like to create two distributed switch, each will have a vmkernel for vsan traffic.

will this configuration work?

[rcporto]

It should work but take in mind the following:

Virtual SAN does not support multiple VMkernel adapters on the same subnet for load balancing. Multiple VMkernel adapters on different networks, such as VLAN or separate physical fabric, are supported.

[ChevUribe]

one vsan kernel i used 192.168.1.x

another vsan kernel i used 192.168.2.x

so it means this will not work?

[rcporto]

If subnet mask is 255.255.255.0 it will be supported, since your VMkernel will be on different subnets.

[ChevUribe]

I think it is misleading,

If it says VSAN traffic can't be on the same subnet, it means 2 vmkernel VSAN traffic in the same 255.255.255.0 will not work regardless if they are on separate distributed sitch and physical adapters. Eventhough they are using different IP range?

What do you mean another physical fabric?

[ChevUribe]

up!

[depping]

Not sure what is unclear about it, we only support VSAN VMKernel Interfaces which are on two different subnets, regardless of the physical  topology. I hope that helps. Personally I wouldn't complicate things. Especially in a 10GbE network in 99 out of 100 cases most customers can suffice with using 1 VMkernel interface and doing "load based teaming" or "active/standby".

[ChevUribe]

I have two distributed switch. each have a vsan traffic kernel.

distributed switch 1:

vsan traffic:

192.168.1.206

255.255.240.0

--gateway--

distributed switch 2:

192.168.2.206

255.255.240.0

--gateway--

when I did this configuration, vsan traffic went down.

Is the subnet for vsan in distributed switch should be in 255.255.255.0?

[rcporto · Accepted solution]

Since you're using the subnet mask 255.255.240.0, your both VMkernel IP address are on the same subnet, that is 192.168.0.0 - 192.168.15.255. Try changing the subnet mask for 255.255.255.0.

[ChevUribe]

thanks!