Today I wanted to run through the process used to patch HP drivers on an ESXi host; specifically through Update Manager. In a vSphere 6.5 troubleshooting post, we discussed a PSOD issue stemming from a specific HP iLO driver. That being the case, it seemed fitting to go through the patch process for the affected iLO driver in this post. Despite this being a very specific patch, the general patch procedure can be applied to other driver updates as well.
Issue Background – HPE Advisory regarding Proliant servers deployed using the hpe-ilo driver version 188.8.131.52-24. VMware ESXi 6.5 host fails with a Purple Screen Diagnostic, indicating that CPU XX / World XXXXXX tried to re-acquire a lock. Resolved by upgrading the hpe-ilo driver to version 6184.108.40.206 or later.
In our instance, we will check the ESXi host(s) for the affected HP driver.
Administering your VMware environment often requires remote access to your ESXi hosts. Access to the ESXi shell via SSH offers administrators the ability to maintain, troubleshoot, and remediate issues by using a Secure Shell client such as PuTTY. For security purposes, SSH is disabled by default. However, you can enable it for remote command execution in multiple ways. In this post, we will go through the different processes of enabling SSH on VMware ESXi 6.5 hosts.
- Direct Console User Interface (DCUI)
- vSphere Web Client – Host
- vSphere Web Client – vCenter
Enable SSH | DCUI
Remote console to the DCUI screen of the ESXi host.
Attention Veeam and Microsoft Exchange 2016 users; if you are running Veeam B&R against your Microsoft Exchange 2016 environment, you may want to wait to upgrade to Exchange Cumulative Update 5.
As noted in Veeam Digest, customers who upgraded to CU5 are experiencing restore failures while utilizing Veeam Explorer for Exchange.
The specific restore failures pertain to mailbox item-level recoveries, which are failing due to a significant change in the mailbox database structure. Typically, users receive an error stating Invalid property BLOB.
Veeam is in the process of updating Veeam Explorer for Exchange to be able to parse the new blob format correctly. They plan to include the fix in Veeam Backup & Replication 9.5 Update 2.
An update in the vCenter 6.5b patch that I have been anticipating is the ability to change the mail sender address vCenter utilizes for email alerts. Releases prior to 6.5b sent e-mail alerts from root@VCSA_FQDN by default. Even if the Mail Sender was changed within the appliance, e-mails would still have that same root return-path. This proved to be problematic in environments who leveraged SMTP relay servers to pass e-mail authentication or encryption (ie. Office 365 relays). Relay servers in those environments typically are configured to reject e-mails that do not come from a specified e-mail address or FQDN. To remedy this, the 6.5b patch now allows admins to specify an e-mail address to Send As.
Configure Mail Server and Mail Sender
Log into vCenter and Edit the General settings on your vCenter instance. This is done from the Configure tab.
In the last few weeks, I have seen several reports of people having issues logging into the ESXi 6.5 Host Client with Chrome or Chromium. When logging in, they receive an unhandled exception stating: Unfortunately, we hit an error that we weren’t expecting. The client may continue working, but at this point, we recommend refreshing your browser and submitting a bug report.
The details of that exception state the cause is Error: [$rootScope:inprog] http://errors.angularjs.org/1.3.2/$rootScope/inprog?p0=%24digest
Unfortunately, I haven’t discovered a permanent fix for the exception. However, you can work around the issue with a simple process.