VMware Cloud Community
kapiljha
Contributor
Contributor
Jump to solution

VSAN in nested environment:Network issue

Hi All,

I am building a test VSAN env in nested environment, and I am stuck with one error which seems to be not new with VSAN implementation.

pastedImage_0.png

I checked various blogs and website and solution seems to be

  • Option 1 – Disable IGMP Snooping. Now this will allow all multicast traffic through, but if the only traffic is VSAN, then this should be a negligible amount of traffic and should be safe to use.
  • Option 2 - Configure IGMP snooping querier. If there is other multicast traffic and you are concerned that disabling IGMP snooping might open the network up to a flood of multicast traffic, then this is a preferred option. Cisco detail how to do this here.

But these virtual ESX host in nested environments are connected via vSwitch and there is no physical NIC conntect

Any help is much appreciated.

Thanks

Kapil

Reply
0 Kudos
1 Solution

Accepted Solutions
depping
Leadership
Leadership
Jump to solution

If you are running nested, did you configure promiscuous mode and forged transmits?

http://www.virtuallyghetto.com/2013/11/why-is-promiscuous-mode-forged.html

View solution in original post

Reply
0 Kudos
5 Replies
depping
Leadership
Leadership
Jump to solution

So you created VSAN VMkernel interfaces all in the same subnet? and you can ping these from host to host?

admin
Immortal
Immortal
Jump to solution

Hi,

Have you enabled the Virtual SAN traffic service on the vmk interface?

Screen Shot 2014-05-05 at 00.42.19.png

Reply
0 Kudos
kapiljha
Contributor
Contributor
Jump to solution

Hi, you are right, there is some network issue,

~ # esxcli network ip route ipv4 list

Network      Netmask        Gateway      Interface  Source

-----------  -------------  -----------  ---------  ------

default      0.0.0.0        192.168.0.4  vmk0       MANUAL

192.168.0.0  255.255.255.0  0.0.0.0      vmk1       MANUAL

I just have 1 vswitch ie vSwitch0, and ESXhost have IP

192.168.0.1/2/3   vcenter server has IP 192.168.0.4 and putting it as gateya for both port groups.

I created another port group VSAN with vKernel adapter vmk1 having IPs

192.168.0.151/152/153

they all in same subnet /24, I tried to split the subnet but still it did not work.

so basically 192.168.0.1/2/3 and 192.168.0.151/152/153 are not pingable

Can you please point what is missing here.

Thanks

Kapil

Reply
0 Kudos
depping
Leadership
Leadership
Jump to solution

If you are running nested, did you configure promiscuous mode and forged transmits?

http://www.virtuallyghetto.com/2013/11/why-is-promiscuous-mode-forged.html

Reply
0 Kudos
kapiljha
Contributor
Contributor
Jump to solution

Bingo,

You are awesome man!!

Thanks

Kapil

Reply
0 Kudos