flchristoph
Enthusiast
Enthusiast

Unknown interface on VMK created by cluster preparation

Jump to solution

Hi,

I am trying to set this up in our test environment. I get the following error when trying to do a 'test connectivity' for VXLAN traffic between two clusters:

vcns55_1.jpg

On the ESXi CLI:

vcns55_2.jpg

So, somehow the VMK created through the vShield preparation is faulty.

I am using the following builds:

- ESXi 5.5: 1331820

- VC Appliance 5.5: 1312298

- vCNS 5.5: 1317534

Am I missing something?

Thanks,

Chris

Tags (1)
1 Solution

Accepted Solutions
sachinthakkar
Enthusiast
Enthusiast

Yes, there is a known bug on the connectivity checker in vCNS 5.5 when executing the test against 5.5 ESX hosts.

From the CLI, you have to specify the netstack to get the proper output. On 5.5 vSphere hosts, VXLAN has a dedicated netstack for the VTEP interface(s).

See the example below from my lab:

Without netstack specified, you see the error:

~ # vmkping 10.24.115.13 -I vmk1

Unknown interface 'vmk1': Invalid argument

With netstack specified, it works as expected:

~ # vmkping ++netstack=vxlan 10.24.115.13 -I vmk1

PING 10.24.115.13 (10.24.115.13): 56 data bytes

64 bytes from 10.24.115.13: icmp_seq=0 ttl=56 time=9.796 ms

64 bytes from 10.24.115.13: icmp_seq=1 ttl=56 time=1.465 ms

--- 10.24.115.13 ping statistics ---

2 packets transmitted, 2 packets received, 0% packet loss

round-trip min/avg/max = 1.465/5.630/9.796 ms

In your case:

vmkping ++netstack=vxlan 172.20.10.10 -I vmk3

Hope this helps!

View solution in original post

5 Replies
sachinthakkar
Enthusiast
Enthusiast

Yes, there is a known bug on the connectivity checker in vCNS 5.5 when executing the test against 5.5 ESX hosts.

From the CLI, you have to specify the netstack to get the proper output. On 5.5 vSphere hosts, VXLAN has a dedicated netstack for the VTEP interface(s).

See the example below from my lab:

Without netstack specified, you see the error:

~ # vmkping 10.24.115.13 -I vmk1

Unknown interface 'vmk1': Invalid argument

With netstack specified, it works as expected:

~ # vmkping ++netstack=vxlan 10.24.115.13 -I vmk1

PING 10.24.115.13 (10.24.115.13): 56 data bytes

64 bytes from 10.24.115.13: icmp_seq=0 ttl=56 time=9.796 ms

64 bytes from 10.24.115.13: icmp_seq=1 ttl=56 time=1.465 ms

--- 10.24.115.13 ping statistics ---

2 packets transmitted, 2 packets received, 0% packet loss

round-trip min/avg/max = 1.465/5.630/9.796 ms

In your case:

vmkping ++netstack=vxlan 172.20.10.10 -I vmk3

Hope this helps!

charliejllewell
Enthusiast
Enthusiast

Sorry for hijacking this thread but I receive the same issue. The fix for vmkping works however I also receive an issue when adding static routes for the vxlan vmkernel port. Do you know if there is a similar fix for this?

0 Kudos
charliejllewell
Enthusiast
Enthusiast

Sorry, found the answer:

esxcli network ip route ipv4 add --gateway x.x.x.x --network x.x.x.x/xx --netstack=vxlan

0 Kudos
jfnoriega
Contributor
Contributor

Thank you very much for the tip on using the network stack !

This worked great on ESXi 6 !

0 Kudos
RanjnaAggarwal
VMware Employee
VMware Employee

is this works on esxi 5.5 as i am getting the error

Regards, Ranjna Aggarwal
0 Kudos