BladeSystem Management Software

ESXi host cannot initiate vMotion due to HP-AMS 500.9.6.0

 
chuckk281
Trusted Contributor

ESXi host cannot initiate vMotion due to HP-AMS 500.9.6.0

Joe was looking to help a customer regarding the "Agentless Management Service":

 

************

 

Dear Experts,

 

My customer ESXi hosts cannot initiate vMotion due to running version HP-AMS 500.x, they plan on upgrading to AMS version 10.0.1 which will fix the problem, but that upgrade will be pushed out maybe one month down the road as it is part of a full SPP upgrade maintenance.

 

My question is regarding the workaround mentioned in the vmware knowledge base, if the customer removes the HP-AMS service on their  ESXi hosts as a stop gap measure what features will they lose or new risks they may be creating for themselves by performing the vmware workaround mentioned below?

 

http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=2085618

Work Around

To work around this issue, remove the package on all hosts running on one of the preceding AMS versions.

 To remove the package on all hosts running on these AMS versions:

  1. Log in to the host using SSH. For more information, see Using ESXi Shell in ESXi 5.x (2004746).
  2. Run this command to stop the HP service (does not persist on reboot):  /etc/init.d/hp-ams.sh stop 
  3.  Run this command to remove the VIB:  esxcli software vib remove -n hp-ams 
  4. Reboot the host

 

*************

 

Help from John:

Unless something has changed recently, Vsphere HP bits are “dual stack” – meaning that they have a traditional CIM provider agent on there *AND* they have the AMS “service.”

 

If they dump the AMS, they would still have the CIM provider – which means that the vcenter plugin will still work – and if it was in HP SIM, you’d still get an ILO to Hypervisor association built and could subscribe to WBEM alerts and such.

 

 

Joe got additional help:

I got an answer to my original question:

 

“if the customer removes the HP-AMS service on their  ESXi hosts as a stop gap measure what features will they lose or new risks they may be creating for themselves by performing the VMware workaround mentioned below”

 

Below is a grid that shows the alerting features with and without the AMS Agent.

 

I’ve also paste the source AMS whitepaper thank you Joe Guydish for providing me this information.

 

http://h20565.www2.hp.com/portal/site/hpsc/template.BINARYPORTLET/public/kb/docDisplay/resource.process/?spf_p.tpst=kbDocDisplay_ws_BI&spf_p.rid_kbDocDisplay=docDisplayResURL&javax.portlet.begCacheTok=com.vignette.cachetoken&spf_p.rst_kbDocDisplay=wsrp-resourceState%3DdocId%253Demr_na-c03488111-1%257CdocLocale%253D&javax.portlet.endCacheTok=com.vignette.cachetoken

 

webpic342.png

 

 

 

***********

 

Other comments?