HP Bundles are not updated using Update Manager

You probably know that you can add HP VIB Repositorys to VMware vSphere Update Manager. I normally add these links to Update Manager:

So you can define an own baseline for HP VIB packages or add them to you already existing baselines. I would recommend the first option. Continue reading “HP Bundles are not updated using Update Manager”

HP Bundles are not updated using Update Manager

Configure HP iLO in ESXi console

To configure a HP iLO board you can use a web browser of course. But how to access iLO when you did not set a correct IP address or Administrator password in BIOS using F8 key? Of course you can reboot and enter F8 at boot. But to restart a ESXi host just to enter a iLO IP address is not very elegant. Here I will explain how to configure iLO in ESXi shell.

Continue reading “Configure HP iLO in ESXi console”

Configure HP iLO in ESXi console

Update host without Update Manager by using esxcli

This blog post describes how to update respectively install VIBs on hosts without using VMware Update Manager (VUM). Instead of VUM we will use esxcli. esxcli software is a really powerful framework which you can use to keep your hosts up-to-date, install and remove bundles. The commands below are using real repositories and vSphere Installation Bundles (VIBs). These examples should work fine for ESXi 5.x. Do not forget to set maintenance mode before updating a host.

Some words for HP VIBs
These days there are strange behavours when updating HP VIBs. So I could not update the VIB for HP-AMS using the command to update all HP VIBs on the host:

esxcli software vib update -d http://vibsdepot.hp.com/index.xml

I got an [VibDownloadError]-error. Coping the vib locally and running the command to install VIBs, previous copied to local disk

esxcli software vib update --viburl /tmp/hp-vib/hp-ams-550.10.0.1-07.1198610.vib

works fine. After this, esxcli software vib update -d http://vibsdepot.hp.com/index.xml works without any problems.

Update host without Update Manager by using esxcli

[HP] bugs you should know about

[September 2015]


Because of a misbehavior in iLO (firmware before 2.20) the internal SD card can suddenly stops working on HP ProLiant Gen9 servers. On ESXi Hosts the following error may occur if it is installed to this device:

Lost connectivity to the device mpx.vmhba32:C0:T0:L0 backing the boot filesystem /vmfs/devices/disk/mpx.vmhba32:C0:T0:L0. As a result, host configuration changes will not be saved to persistent storage.


Upgrade iLO Firmware to at least 2.20.

[November 2014]


Again there is a problem with hp-ams packages! This time the process hangs when doing a restart of ESXi management agents on ProLiant G5, G6 and G7. ESXi versions 5.x and hp-ams versions 9.5, 9.6 and 10.0 are affected.


To be honest, this not really a bug, because hp-ams is at the moment just supportet on Gen8 servers. So the solution is to uninstall the software:

  • enable maintenance mode
  • Stop it by executing /etc/init.d/hp-amd.sh stop
  • remote it by running esxcli software vib remove -n hp-ams
  • reboot and exit maintenance mode

Problem (1)

It seems to be a VMware problem that is fixed with vSphere 5.5 U2. It may cause a PSoD on an ESXi host on certain conditions. The errors logged in vmkernel.log look like:

  • DMAR Fault IOMMU
  • IOMMU context entry dump for ...

I had the problem on an ProLiant server during the upgrade process to 5.5 U2. After installing the updates the host ran into a PSoD during reboot. Thank to the failback-feature during updates, the host booted the last working software-profile.


The Server in my case does not fit exactly to the description in the KB-article but the error were near the same. I resolved the issue by updating the firmware of the server to SPP 2014.09.0. Link to the current SPP you can find here.

[September 2014]


On a  VMware ESXi you can observe:

  • cannot perform vMotion
  • cannot start services such as SSH
  • when trying to restart management agents you see an error that a process can’t fork
  • on the console of the host, pressing ALT+F1, you can see can’t fork all over the screen
  • in vmkernel.log you can see warning like
    WARNING: Heap: 2677: Heap globalCartel-1 already at its maximum size. Cannot expand.
    WARNING: Heap: 3058: Heap_Align(globalCartel-1, 136/136 bytes, 8 align) failed.
  • Veeam backup jobs fail with errors like:
    Error: Client error: File does not exist or locked. VMFS path: [[datastore] path_to_vmx_file.vmx
    Please, try to download specified file using connection to the ESX server where the VM registered.
    Failed to create NFC download stream. NFC path: [nfc://conn:vC-server,nfchost:host-nn,stg:datastore-n@path_to_vmx_file.vmx]


This behavior can be caused by HP Agentless Management Services (AMS). These version are affected:

  • hp-ams 500.9.6.0-12.434156
  • hp-ams-550.9.6.0-12.1198610.

To resolve the issue you can:

  • Stop the service by executing /etc/init.d/hp-ams.sh stop (the next reboot will start the service again)
  • Uninstall the service by running esxcli software vib remove -n hp-ams
  • Upgrade to minimum version hp-ams 500.10.x respectively hp-ams 550.10.x using Update Manager or esxcli

More information on VMware KB you can finde here.

[August 2014]


There is a memory leak in HP NIC Management Agent. Now and then there are problems with HP Management Agents. Years ago SCSI Agent causes a lot of failed backups. According to HP Advisory NIC Agent version 9.4, 9.5 and 9.6 may allocate 5MB memory per hour on Windows 2012 and 2012 R2 Servers. Yes, this can just be the case when Windows is installed directly on HP ProLiant Servers. Because of virtualization most often Windows runs as a VM, but think about Hyper-V or in my case DataCore SANsymphony: the NIC Agent process consumed more then 2 GB of memory and causes a real performance impact. A mirror link could use a bandwidth of app. 2Gbit of a 10Gbit link in one direction, the other direction on the same link could use a bandwidth of app. 9Gbit. After disabling the NIC Agent in Windows system settings, 9Gbit could be used in both directions.


You can:

  • Disable NIC Agent in Windows system settings
  • Upgrade to an version that is not affected
[HP] bugs you should know about

VMworld2014|14.10.|[VAPP2635-SPO] Best practices for managing your VMware environment with HP integrations

I thought the session would be focused on HP tools and practices to integrate HP servers and storage into vSphere environments for managing, monitoring and installation. But this session was mainly focused on OneView integration into vCenter.

HP OneView for VMware vCenter

  • Plug-in to Web Client is available for OneView integration
  • Networking
    • graphical display of network cabling – which is very nice!
    • you can see graphs of throughput and performance, if plug-ins are installed
    • includes checks to look for VLANs configured on host-level also configured at hardware
    • it also recommends actions that you can apply easily. e.g.: networks are not configured on host-level, the plug-in can run the necessary commands on the hosts (doing maintenance mode of course)
  • Storage
    • graphical display of storage connections – which is also very nice!
      here you can see e.g. replicated 3PAR volumes easily
    • you can create, expand, delete datastores directly from this plug-in
    • includes FW update. Works with OneView.
  • Licensing (more information about licensing and download you can finde here)
    • the module for storage management can be used for free. The license is enabled by downloading the software.
    • the server module is licensed with OneView and HP Insight Control
    • HP 3PAR StoreServ Recovery Manager for VMware functionality is licensed separately

HP OneView for other vSphere components

  • Integration in vCOPs
    • Dashboard, including HP server, storage, networking, …
  • Integration in Log Insight
    • provides search strings to allocate HP specific errors
    • provides script to provide data from HP sources (iLO, OA, …)
VMworld2014|14.10.|[VAPP2635-SPO] Best practices for managing your VMware environment with HP integrations

configure Smart Array Controller by use of esxcli

The following commands show how to configure an HP Smart Array Controller by use of command line utility esxcli. Some time ago, ACU is replaced by Smart Storage Administrator (SSA). So if the command hpacucli doesn´t work for you any more, replace it by hpssacli.

To be able to do this, HP offline bundle must be installed on the host.

Continue reading “configure Smart Array Controller by use of esxcli”

configure Smart Array Controller by use of esxcli