Skip to main content

Firmware upgrading is pending on install in progress on HP ESXi 5.5 blade by HP SUM

In my post HP Blade Firmware Upgrading Best Practices for ESXi Host I mentioned HP released firmware and drivers by SPP image.  I have set my ESXi 5.5 baseline to SPP2014.06 as I have tested it in my lab environment. Looks like stable.

SPP2014.06 has ability to upgrade ESXi 5.5 host online, this is pretty convenient for my upgrading strategy. Before this release I have to make vCenter Update Manager baseline for new drivers, and apply it after offline firmware upgrading. I have to reboot host twice at least, but now it's just one reboot!

BTW, I'm not familiar with SPP online firmware upgrading. After observation of vmkernel log I feel it's actually mount a virtual USB drive to do upgrading, that's only information I have regarding upgrading process.

Okay, let's talk about the topic of this post. During the SPP2014.06 online firmware upgrading, my HP SUM keep show status Install in progress. I waited 3 hours in morning but got back nothing! vmkernel.logvpxa.log and hostd.log show nothing, just regular events. Eventually I took the risk to force reboot the host. God bless me! It's back online without any issue. :-)

You have to be brave to do that if you are managing enterprise data center. IT Pro does not like risk! I would say we have way to work around it, at least reduce the risk.

If you go to %temp%HPSUM, you will see some folders are named by IP address. That's the logs folder of HP SUM nodes, the upgrading logs is in deploy.log.

If you see keyword Update completed, but system reboot required, it indicates the upgrading has been completed. You could wait 15 - 20 minutes to see whether HP SUM can return upgrading result. If it keeps on Install in progress a long time, you could just stop HP SUM and reboot the host.

Do let me know if you see a problem by this workaround. Thanks.

在我之前的文章 HP Blade Firmware Upgrading Best Practices for ESXi Host中我提到惠普用SPP光盘来更新固件和驱动程序。我在试验环境下已经测试了SPP2014.06的稳定性,并且把我的ESXi 5.5的惠普刀片服务器固件和驱动基准定为SPP2014.06

SPP2014.06可以实现在线更新ESXi 5.5服务器的固件和驱动,这对我的升级策略非常有意义。在这个版本之前我都不得不用SPP光盘先做离线固件升级,然后再在vCenter Update Manager下把对应的驱动程序做好基准包打到ESXi 5.5服务器上。这整个过程需要重启两次,现在只要一次重启了!

我不是很熟悉SPP的固件升级过程,但是通过观察vmkernel日志,看起来它应该是通过在ESXi 5.5服务器下加载一个虚拟USB实现升级的。这是题外话。

OK,回到主题。我的HP SUM一直显示Install in progress当我
SPP2014.06升级时,花了我一上午3个小时时间一直这样!而vmkernel.logvpxa.loghostd.log 里除了普通的记录外什么都没有。最终我决定冒险强制重启。还好最终这台服务器上线了且没有任何错误的硬件。J

如果你是管理企业级数据中心,并做和我一样的事情,你需要很大的勇气才行,哈哈!IT Pro是不喜欢风险的!其实我想说我们还是有办法解决这个问题的,至少是减少风险。

%temp%HPSUM目录下,有一些以IP地址命名的文件夹,这就是HP SUM里每个目标主机的日志目录,进去找到deploy.log

如果你在这个日志文件里看到关键字Update completed, but system reboot required,则说明升级已经成功了。可以继续等待1520分钟看看HP SUM上会不会返回升级结果。如果它一直处于Install in progress 很久,你可以直接重启了。


Popular posts from this blog

Connect-NsxtServer shows "Unable to connect to the remote server"

When you run Connect-NsxtServer in the PowerCLI, it may show "Unable to connect to the remote server".  Because the error message is a little bit confusing with other login issues. It's not easy to troubleshoot. The actual reason is the NSX-T uses a self-signed certificate, and the PowerCLI cannot accept the certificate automatically. The fix is super easy. You need to set the PowerCLI to ignore the invalid certificate with the following command: Set-PowerCLIConfiguration -Scope User -InvalidCertificateAction:Ignore -Confirm:$false

Setup Terraform and Ansible for Windows provisionon CentOS

Provisioning Windows machines with Terraform is easy. Configuring Windows machines with Ansible is also not complex. However, it's a little bit challenging to combine them. The following steps are some ideas about handling a Windows machine from provisioning to post configuration without modifying the winrm configuration on the guest operating system. Install required repos for yum. yum -y install yum -y install yum -y install yum -y install epel-release yum -y install yum-utils yum-config-manager --add-repo Install  Terraform . sudo yum -y install terraform Install  Ansible . sudo yum -y install ansible Install  Kerberos . yum -y install gcc python-devel krb5-devel krb5-libs krb5-workstation

How to List All Users in Terraform Cloud

Terraform has a rich API. However, the API documentation does not mention how to list all users. We can leverage the organization membership API and the PowerShell command  Invoke-RestMethod  to get a user list. 1. Create an organization token in Terraform Cloud. 2. Create the token variable ( $Token ) in PowerShell. $Token = "abcde" 3. Create the API parameters variable in PowerShell. $params = @{ Uri = "" Authentication = "Bearer" Token = $Token ContentType = "application/vnd.api+json" } Note: You need to replace ZHENGWU with your own organization name. And I used 100 at the end of the URI to retrieve the first 100 users. It can be any number.  4. Retrieve the API return and list the user's email address. $Test = Invoke-RestMethod @params $