VMware Cloud Community

what's the difference between disable a network through "vmkchdev" and "esxcli"?

Searching the web, i found this article posted by William Lam http://www.virtuallyghetto.com/2011/06/how-to-disable-vmnic-in-esxi.html

In this article, he introduced a command "vmkchdev" to disable your vmnic

Normally, if we want to bring down a vmnic connection, using "esxcli network nic down -n vmnic0" is your top choice.

But, in Windows platform, disconnect the network means the link is down whereas disable the NIC means the NIC is disabled in device manager and the NIC will gray out.

Is "esxcln network nic down -n vmnic0" ONLY stops your connection, not disable the nic?

And if you want to disable a NIC, you should choice "vmkchdev"?

What's the difference between disable a network through "vmkchdev" and "esxcli"?   Any thought?

Tags (3)
0 Kudos
1 Reply

Maybe this helps to clarify things: Workaround to disable one of the unused NIC or FCOE ports in ESXi 3.x, 4.x and 5.x using vmkchdev

vmkchdev is mainly used to switch between vmkernel handling or passing through the device. So if you use that to disable a NIC it's like you pull out/unplug the actual card.

The esxcli command just cuts off the link, so it's like pulling the network cable.