cannot vmkping own ip.

[rbac]

we have just upgraded ( actually reinstalled) a bunch of hosts to 6.5 and on one host we cannot vmkping anything on the vmotion interface. ( works on all the others )  Vmotion to and from this host works fine. i can vmkping this host just fine.

[root@pesxserver10:~] esxcli network ip interface ipv4 get
Name  IPv4 Address     IPv4 Netmask     IPv4 Broadcast   Address Type  Gateway         DHCP DNS
----  ---------------  ---------------  ---------------  ------------  --------------  --------
vmk0  192.168.250.19   255.255.255.240  192.168.250.31   STATIC        192.168.250.17     false
vmk1  192.168.255.101  255.255.255.0    192.168.255.255  STATIC        0.0.0.0            false
vmk3  192.168.243.53   255.255.255.0    192.168.243.255  STATIC        0.0.0.0            false
vmk2  192.168.250.34   255.255.255.240  192.168.250.47   STATIC        0.0.0.0            false
[root@pesxserver10:~] vmkping 192.168.250.34
PING 192.168.250.34 (192.168.250.34): 56 data bytes

--- 192.168.250.34 ping statistics ---
3 packets transmitted, 0 packets received, 100% packet loss

On another host

Name  IPv4 Address     IPv4 Netmask     IPv4 Broadcast   Address Type  Gateway         DHCP DNS
----  ---------------  ---------------  ---------------  ------------  --------------  --------
vmk0  192.168.250.18   255.255.255.240  192.168.250.31   STATIC        192.168.250.17     false
vmk1  192.168.255.103  255.255.255.0    192.168.255.255  STATIC        0.0.0.0            false
vmk2  192.168.250.39   255.255.255.240  192.168.250.47   STATIC        0.0.0.0            false
vmk3  192.168.243.62   255.255.255.0    192.168.243.255  STATIC        0.0.0.0            false
[root@pesxserv01:~] vmkping 192.168.250.18
PING 192.168.250.18 (192.168.250.18): 56 data bytes
64 bytes from 192.168.250.18: icmp_seq=0 ttl=64 time=0.099 ms
64 bytes from 192.168.250.18: icmp_seq=1 ttl=64 time=0.116 ms

--- 192.168.250.18 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.099/0.107/0.116 ms
[root@pesxserv01:~] vmkping 192.168.250.34
PING 192.168.250.34 (192.168.250.34): 56 data bytes
64 bytes from 192.168.250.34: icmp_seq=0 ttl=64 time=0.382 ms
64 bytes from 192.168.250.34: icmp_seq=1 ttl=64 time=0.250 ms

--- 192.168.250.34 ping statistics ---
2 packets transmitted, 2 packets received, 0% packet loss
round-trip min/avg/max = 0.250/0.316/0.382 ms

Any ideas why or what I should at?

[SureshKumarMuth]

Try this

  vmkping  -I vmk2 192.168.250.34

[rbac]

gets wierder....

[root@pesxserver10:~] vmkping  -I vmk2 192.168.250.34

Unknown interface 'vmk2': Invalid argument

[SureshKumarMuth]

can you please identify which vmkX is used for vmotion network and use that vmk in the command. Error says vmk2 not exists.

[rbac]

correct,  but it most definitely does exist. and is the vmk used for vmotion

vmk2

   Name: vmk2

   MAC Address: 00:50:56:6d:42:20

   Enabled: true

   Portset: vSwitch1

   Portgroup: vMotion

   Netstack Instance: vmotion

   VDS Name: N/A

   VDS UUID: N/A

   VDS Port: N/A

   VDS Connection: -1

   Opaque Network ID: N/A

   Opaque Network Type: N/A

   External ID: N/A

   MTU: 9000

   TSO MSS: 65535

   Port ID: 50331653

[daphnissov]

Your vmkping is failing because you aren't specifying the TCP/IP stack (use the -S flag) on which the vmkernel interface is found. If you don't specify the stack, it assumes the default one is in use. When that's not the case, the command fails.

[rbac]

the port was connected to the wrong network stack. Thanks to daphnissov​ for the pointer.