Tips for a Successful Virtual SAN 5.5 Evaluation
It states on page 9 to use vmkping -S 9000 to test connectivity between hosts using jumbo frames.
There is where I hit a wall.... I kept getting the following error message:
~ # vmkping -S 9000 192.168.100.14
*** vmkernel stack not configured ***
I kept racking my brain, checking my configuration, making sure that MTU 9000 was set on the distributed switch and also on the VSAN VMkernel, and that my network switches were set to support jumbo frames on both the physical ports and on my VSAN VLAN (I use VLAN 1001 since VLAN 1000 is my vMotion network). Then I came across the following post:
Even though that is an old post from well before VSAN existed, it is still entirely relevant. Now armed with the correct formatting of the command:
~ # vmkping -I vmk2 -s 8972 -d 192.168.100.14
PING 192.168.100.14 (192.168.100.14): 8972 data bytes
8980 bytes from 192.168.100.14: icmp_seq=0 ttl=64 time=0.176 ms
8980 bytes from 192.168.100.14: icmp_seq=1 ttl=64 time=0.159 ms
8980 bytes from 192.168.100.14: icmp_seq=2 ttl=64 time=0.157 ms
--- 192.168.100.14 ping statistics ---
3 packets transmitted, 3 packets received, 0% packet loss
round-trip min/avg/max = 0.157/0.164/0.176 ms
Eureka! (also vmk2 is my VSAN VMkernel interface and adding "-I vmk2" specifies what interface to force the ping to travel over)
