Fix Missing NIC of Nested ESXi

Sometimes when I create new nested ESXi servers (like now that I just set up a new nested vSphere 6 lab) only 1 NIC shows up inside the Direct Console User Interface (DCUI) despite configuring it with several NICs, and choosing the correct VM type.

There were times when reboot does the trick but that workaround has 50/50 chance of working, which I’m not willing to do anymore.

I scrutinized the .vmx file of the VM, which is the nested ESXi in this case, and found that the other missing NICs were created using the wrong type.

1. So, like any good VI admin, I put the ESXi VM in Maintenance mode first, turned it off, and then removed it from the VMware Workstation library.

2. Edit the .vmx of the VM using notepad and added the appropriate NIC entries in this file:

ethernet0.present = “TRUE”
ethernet0.vnet = “VMnet1”
ethernet0.connectionType = “custom”
ethernet0.virtualDev = “e1000”
ethernet0.wakeOnPcktRcv = “FALSE”
ethernet0.addressType = “generated”
ethernet1.present = “TRUE”
ethernet1.vnet = “VMnet2”
ethernet1.connectionType = “custom”
ethernet1.virtualDev = “e1000”
ethernet1.wakeOnPcktRcv = “FALSE”
ethernet1.addressType = “generated”
ethernet2.present = “TRUE”
ethernet2.connectionType = “nat”
ethernet2.virtualDev = “e1000”
ethernet2.wakeOnPcktRcv = “FALSE”
ethernet2.addressType = “generated”

The highlighted lines could be missing or having a different value than what we want for them to work. Keep adding / correcting them for each network interface of your nested ESXi.

By |2018-10-07T12:56:15+00:00July 9th, 2017|Technology, VMware|0 Comments

About the Author:

Leave A Comment