Error In Esx Configuration File Esx.conf Upgrade
Contents |
Christian Mohn Posted on August 28, 2015August 28, 2015 VMware During an upgrade from vSphere 5.1 to 5.5, I ran into a rather strange issue when trying to utilize VMware Update Manager to perform the ESXi upgrade. During scanning, VUM reported the ESXi host as "Incompatible", without offering any other explanation. I spent ages looking through VUM logs, trying to find the culprit, suspecting it was an incompatible VIB. Without finding anything that gave me any indication on what the problem might be, I moved on to looking at the ESXi image I had https://kb.vmware.com/kb/2011588 imported into VUM. As this was on a Dell PowerEdge R710, I was utilizing the Dell Customized Image of VMware ESXi 5.5 Update 2, which got an updated A02 version last night (27th of August) - I downloaded my image, VMware-VMvisor-Installer-5.5.0.update02-2068190.x86_64-Dell_Customized-A00.iso on the 27th, but before the VMware-VMvisor-Installer-5.5.0.update02-2068190.x86_64-Dell_Customized-A02.iso image was available. Thinking this would resolve the issue, I imported http://vninja.net/vmware-2/vmware-update-manager-unsupported-configuration/ the new image into VUM, and created a new Upgrade Baseline. Sadly, I was still greeted by the non-gracious "Incompatible" warning after performing a new scan. After some more digging, I found the following entry in the Events pane, for the given host, in vCenter: 123456Error in ESX configuration file (esx.conf). error 28.08.2015 11:51:25 Scan entity [hostname] [username] Naturally I go digging into the /etc/vmware/esx.conf file, and found the following entries: 1234/nas/[oldserver]/readOnly = "false" /nas/[oldserver]/enabled = "true" /nas/[oldserver]/host = "[oldserver.fqdn]" /nas/[oldserver]/share = "/VeeamBackup_[oldserver]/" These references to [oldserver] pointed to an old Veeam Backup & Replication server that was decommissioned ages ago. Veeam B&R adds these to a host if vPowerNFS has been used to mount a backup share, and the entries had not been removed when removing the old Veeam B&R server. DNS resolution for the old server failed, as it has been completely removed from the infrastructure, thus causing the VUM update to fail. Manually removing these lines from /etc/vmware/esx.conf fixed the problem, and VUM was able to scan and remediate without issues. Update: After writing this,
2014 Virtualization I've recently been working on getting my environment upgraded from vSphere 5.1 to 5.5. Last http://www.koolaid.info/unsupported-configuration-using-vum-major-upgrade/ week I replaced one vCenter server with a clean install and https://darrylmiles.wordpress.com/category/vmware/ upgraded another, in process implementing home brewed certificates thanks in no small part to Derek Seaman's excellent SSL toolkit and tutorials. With that done and nice and clean this week I turned towards getting the ESX hosts updated. Like all right thinking folks, I typically error in like to use vSphere Update Manager for this task in a vCenter supported environment. The first host went very well and was up and patched without issue. After that the wheels fell off for the other two. I was continuously getting "Unsupported configuration" when I would try to scan the host, if I tried to push error in esx through and Remediate it would fail with "Software or system configuration of host
Hypervisor with IBM Customization (or customized ESXi… well, I say customised). The readme details a number of Broadcom, Brocade, Emulex, LSI and Qlogic drivers as well as additional management support. I still don't know what concretejob does yet. Anyhow, here is the Readme in PDF format and the link to where you can download it. If you have any queries on this release, please post them to the System x forum on developerWorks Leave a comment Upgrading to IBM's customized ESXi 5.0 with VMware UpdateManager Posted by Darryl Miles in IBM, VMware on December 16, 2011 IBM has released it's customised ESXi 5.0 available here (customized if US spelling!). IBM's customised ESXi 5.0 includes a number of additional management components (for Systems Director and IBM's Upward Integration Module plugin for vCenter) and preloaded drivers for Emulex, Qlogic and LSI. This packaged ESXi has been fully tested by VMware and by IBM on a large range of (newer) IBM Systems x servers. Before you get started, ensure you make the following change on your BladeCenter IMM/AMM as outlined in KB 2006133. I found if I didn't make this change, VMware Update Manager would begin to perform the upgrade and then halt with the following error "Error in ESX configuration file (esx.conf)" Note: You'll also need to ensure you can access the server via your AMM/IMM, or have physical access to the server, you'll find out below why this is important. OK, begin by going to VMware Update Manager (VUM), selecting ESXi Images and importing the IBM customised image ISO: Once that's done, create a new baseline group: I also selected Critical Host Patches (so I could check/install these in the future): Attach this baseline to a host or cluster. I was a little concerned that the status was Incompatible, however after doing some research it looked like others had similar results from VUM. Once the baseline is attached, select it in VUM and click Remediate… I've listed the various screen's you'll see during the Remediate wizard below. One item of note here, is that you might need to select "Disable High Availability admission control if this is enabled for any of the selected clusters" in your environment. Once the remediation starts, you'll see it progressing in the Tasks window. Further along, you get some further info under Details Further along the upgrade process, you start to see some things happening on the ESXi host too: At the end of the upgrade I had the following message on the ESXi host. So you have to p