Problems with EAM (VMware ESX Agent Manager) and NSX After upgrading ESXi 6.0 there can be problems with the NSX-v installation VIBs. Edit Symptoms In the Installation section, of Network and Security the installation status of the host(s) will show as not ready. When you click the gear icon next to the host and attempt to run the “resolve” operation, it fails repeatedly. In the administration page of the vCSA under vCenter Server Extensions, double click on vSphere ESX Agent Manager and select the agency for the appropriate cluster. If you see the issue that “Agent VIB module is not installed” To confirm, ssh to the vCenter server and check the EAM log: [ msherian@MARS-E550 ~ ] $ ssh root@vc-01 VMware vCenter Server Appliance 6.5.0.11000 Type: vCenter Server with an external Platform Services Controller root@vc-01's password: root@vc-01 [ ~ ] # less /storage/log/vmware/eam/eam.log 2017 - 11 -15T18: 52 :39.932Z | INFO | host- 1886 - 2 | VibJob.java | 288
One of the minor annoyances of using unsupported hardware is that you get unexpected behaviour. The Intel NUC will not report some required hardware states that ESXi needs. These include things such as the make, model, serial, and asset numbers. In order to work around this we need to build a custom BIOS to populate missing values. Thanks to Virten.net for the know how to do this. There is one caveat, the NUC does not appear in the "download and customize selection" any more. download the BIOS file from Intel Open the file Add in the missing details—I've created a BIOS file for each node with proper details for each, but that isn't really required. Save the BIOS file(s) To easily create a bootable USB use Rufus Rufus version: 2.5.799 Windows version: Windows 10 64-bit (Build 10240) Syslinux versions: 4.07/2013-07-25, 6.03/2014-10-06 Grub versions: 0.4.6a, 2.02~beta2 Locale ID: 0x0409 0 devices found Checking for Rufus updates... Checking