![vmware esxi 6.7 does not detect network adapter vmware esxi 6.7 does not detect network adapter](http://mvsourcecode.com/wp-content/uploads/2018/03/POWERCLI.png)
When logging in, the new network card was up and connected to the network. After editing, the file was saved and the virtual machine was rebooted. I removed all but the one that was current with the new MAC address, which is usually the one at the end of the file. On my virtual machine there were three lines with an eth0 configuration. This is another configuration file for the network interfaces in CentOS.
![vmware esxi 6.7 does not detect network adapter vmware esxi 6.7 does not detect network adapter](http://mvsourcecode.com/wp-content/uploads/2018/11/img_5bf57205cf13b.png)
The next step is to edit the 70-persistent-rules file. Vi /etc/sysconfig/network-scripts/ifcfg-eth0Įdit the HWADDR to reflect the new MAC address, save the file and exit. Now you'll need to edit the ifcfg-eth0 configuration file with either vi or nano. To do this, right click on the virtual machine and go to "Edit Settings" in the "Network Adapter 1" you will find the new MAC address, make note of the last two octets and open the console of the virtual machine.
Vmware esxi 6.7 does not detect network adapter update#
This KB from VMware was helpful in detailing what was needed to get the recently deployed template connected to the network.īecause a templates MAC address changes and the CentOS does not update it automatically we need to get the new address. There are a few gotchas to getting the network card to function after deploying from a template. This equates to 256 disks using PVSCSI adapters. At the VM level, the number of vDisks has increased from 16 to 64 disks. Having a CentOS template in a VMware ESXi environment is not like having a Windows Server template when it comes to networking. vSphere 6.7 VMware vSphere 6.7 supports up to 1024 LUNs and 4096 paths per host.