HP Proliant Gen8 Agentless Management floods ESXi and vCenter Logs

Hewlett-Packard introduced a new component called HP Agentless Management within their Gen8 Series. This feature is extensible though an agent running inside the operating system, in that case the ESXi Host. The package (hp-ams) is included in all customized VMware images provided by HP and the HP ESXi Offline Bundles. Unfortunately this package create some issues caused by excessive local logins. This might pointlessly blow up the database and logfiles. You can check that problem by opening the Event-Log provided by the ESXi Host which is flooded with the following messages:

In this post i am going to show how to workaround this issue and remove the hp-ams from you ESXi Host, and how to build a new image without that package.

What is this Service good for?Prior to remove that service you should know what the hp-ams package is good for and why you would need a contradictory thing like a "Agentless Managent Agent". Without this agent, there a missing some minor features: OS and driver information passed to the iLO and a feature to log iLO events to Guest OS logs. I do not really need that features, so disabling the service is not a problem. To get more information about that service check this document.

Manually disable hp-ams ServiceYou can easily stop the hp-ams Service to test the impact. This change is active immediately and does not persist a reboot. You do not have to enable Maintenance Mode:

root@esx01.virten.local:~ $ /etc/init.d/hp-ams.sh stop

Remove hp-ams Package
To make this change persistent across reboots you have to remove the hp-ams package. This change requires a reboot:

I have 6 hosts in this cluster and only one is throwing this nuisance event now...and I did find hp-ams.sh in /etc/init.d for this host, so I have stopped it. Still scratching my head wondering why it is not on the other hosts. I built them but perhaps one of my colleagues is already on top of this issue :roll:

when we have to remove a vib from more than 100+ esxi host .. We have to connect all server servers to remove the module? it too loaded. Is there any way that we can connect to vCenter using powercli and then read the esxcli of the host. and remove the vib ﻿

same commands i am able to do if i am connected individual esxi host using root id Connect-VIServer ... But when i connected with vcenter using administrator (Connect-VIServer it not working getting above error message .. .