Which command can be run to troubleshoot connectivity problems with vmkernal network interfaces?
A.
esxcli network
B.
vmkping
C.
net-status
D.
vicfg-vmknic
Explanation:
https://kb.vmware.com/selfservice/microsites/search.do?
language=en_US&cmd=displayKC&externalId=2003042
B
https://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1003728
1
0
Notes:
If you see intermittent ping success, this might indicate you have incompatible NICs teamed on the VMotion port. Either team compatible NICs or set one of the NICs to standby.
If you do not see a response when pinging by the hostname of the server, initiate a ping to the IP address. Initiating a ping to the IP address allows you to determine if the problem is a result of an issue with hostname resolution. If you are testing connectivity to another VMkernel port on another server remember to use the VMkernel port IP address because the server’s hostname usually resolves to the service console address on the remote server.
In vSphere 5.5 VXLAN has its own vmkernel networking stack therefore ping connectivity testing between two different vmknics on the transport VLAN must be done from the ESXi console with the either of this syntax:
vmkping ++netstack=vxlan -d -s
esxcli network diag ping –netstack=vxlan –host –df –size=
0
0
https://recommender.vmware.com/solution/SOL-951
Seems both A and B can be used.
Unrated (beta) question?
1
0
I pick B
0
0
I’d say B
0
0
What’s more, part of that new 125Q 2V0-622PSE dumps are available here:
https://drive.google.com/open?id=0B-ob6L_QjGLpaXhnQWQ4S2Ffc1k
Best Regards!
0
1
B
vmkping ++netstack=vxlan -d -s
esxcli network diag ping –netstack=vxlan –host –df –size=
0
0
B
0
0