topic Query: AMS not available in ILO in ProLiant Servers (ML,DL,SL)

AMS not available in ILO

IW-Peter — Fri, 27 Jan 2023 04:52:46 GMT

Hello,

When we log into a Gen 10 proliant DL380p, ilo displays that AMS is not available. If we go to System information and Network then we get:

iLO did not detect the Agentless Management Service when this page was loaded. To view a full set of data on this page, ensure that AMS is installed and running.

The server is running ESX v7.0.3 and has amsd running, infact the vib versions and amsd versions are the same on the other hosts we have (also gen 10) but none of the other servers have any issue with AMS in the ILO.

ESX is up to date in HP and VMware patches, it was built using the HP customised ESX installer ISO and the server has been running for a week and the message stays in ILO.

Running ./etc/init.d/amsd status results in amsd-smarev, amsd-ahsd, amsd-amsd and amsd-smad all running and they can be stopped and started.

The host is running ILO 5 v2.78, I assume that that ILO connection is at fault here as the ESX services appear to be running however I have no way to test if they are.

ilo error

ESX AMS information

Query: AMS not available in ILO

support_s — Wed, 25 Jan 2023 17:32:53 GMT

System recommended content:

1. HPE iLO 5 2.72 User Guide | Agentless Management and AMS

2. HPE Integrated Lights Out (iLO 4) - AMS and the Insight Management Agents

Please click on "Thumbs Up/Kudo" icon to give a "Kudo".

Thank you for being a HPE valuable community member.

Re: Query: AMS not available in ILO

IW-Peter — Thu, 26 Jan 2023 09:24:04 GMT

Thanks but there is nothing in the ILO mangaement that documents this issue, I believe its an HP issue and not a VMware one as my colleague is updating the ILO to 2.78 and this issue has occured on another Gen10 server.

Re: AMS not available in ILO

shiva_jr — Thu, 27 Mar 2025 10:40:27 GMT

Hello Peter,
As per what you are getting in "System information', the Agentless Management Service may not installed.
1. You can try installing AMS. ~~Here~~ is the guide. [Moderator edit: Removed the broken link. Please refer to https://support.hpe.com/]

2. Still issue persists, try with the latest SPP update.

Regards,
SHIVA_JR
Please mark as 'Accepted solution' if my post worked.

Re: AMS not available in ILO

IW-Peter — Fri, 27 Jan 2023 11:56:57 GMT

I've resolved this, for anyone else who has this issue:

On Gen 9 - make sure that both amsd-helpr services are running under ESX

On Gen 10 make sure all 4 amsd services are running under ESX

Restart ILO

On the Gen 10's we confirmed the services were running and found out that an ILO restart was required, this can be done independent of the host and no loss of service occurs.

The Gen 9 service just needed started, I don't think these use amsd, just the amsd-helpr

Re: AMS not available in ILO

Sunitha_Mod — Mon, 30 Jan 2023 06:06:50 GMT

Hello @IW-Peter,

Awesome!

We are glad to know you were able to find the solution and we appreciate you for keeping us updated.

AMS not available in ILO and errors in Windows event log

Kevi1 — Wed, 15 Feb 2023 04:36:51 GMT

Agreed , this corrected the event error logs which claimed the AMS had crashed but was still trying to run. and could not contact the ILO. On reset of the ILO the errors stopped

AMS log files are a great source of fault finding. Caution - file reads from top to bottom when entries are logging.

Actual event log entry,

The Service Control Manager tried to take a corrective action (Restart the service) after the unexpected termination of the Agentless Management Service service, but this action failed with the following error:

An instance of the service is already running.

Now from the Windows application event log entry

Faulting application name: ams.exe, version: 2.51.2.0, time stamp: 0x62d14154 Faulting module name: ntdll.dll, version: 10.0.17763.3887, time stamp: 0x494079d6 Exception code: 0xc0000005 Fault offset: 0x0000000000074de5 Faulting process id: 0x55bc Faulting application start time: 0x01d940b721b98d27 Faulting application path: C:\Program Files\OEM\AMS\service\ams.exe Faulting module path: C:\Windows\SYSTEM32\ntdll.dll Report Id: 5220fec0-c74a-48fd-aa9c-31c49a805b9c

Faulting package full name:

Faulting package-relative application ID:

Reset of the ILO stopped the errors