●
About status of Agentless Management Service(AMS) on iLO Web interface.
When you recived the corrupted SNMP alert about physical drive status changed,confirm the location information of the
same event at “Information” - “Integarated Management log” of iLO5 Web interface.
When status of Agentless Management Service(AMS) is “Unknown” or “Not available”(*) on iLO Web interface,
please reset iLO.
After about 10 minutes, please restart Agentless Management Service(AMS) by following procedures.
* Verifying AMS status
Please confirm the status from iLO Web interface : [System Information] - [Summary] – [Subsystems and Devices] -
"Agentless Management Service".
If the status of Agentless Management Service(AMS) is “Unknown” or “Not available”, iLO can’t collect some part of
information of storage, network and iLO can’t display those information correctly.
< Restarting AMS >
Procedure
・
Windows
Navigate to the Windows Services page and restart AMS.
・
Red Hat Enterprise Linux 7.x and 8.x
Enter the following command:
# systemctl restart smad
# systemctl restart amsd
・
ESXi6.5/6.7
Enter the following command:
# /etc/init.d/amsd.sh restart
or
# /etc/init.d/ams.sh restart
* Command depends on the version of AMS you are using
・
ESXi7.0
Enter the following command:
# /etc/init.d/amsd restart
4) Notice about the OS
●
About EXPRESSBUILDER Manual Installation
Partitions in the target disk are deleted when you install the Windows by EXPRESSBUILDER even if you select the
"Manual" option.
Pay attention to the user data stored in the system drive when re-installing Windows.
●
Notice of Windows Server
When the USB device is used in supported Windows Server OS, the next event log is sometimes registered.
But ignore this message since it does not cause any problem for the operation.
< Event Log >
ID
: 1
Source
: VDS Basic Provider
Level
: Error
Unexpected error occurred. Error code :32@01000004
●
Notice of Agentless Management Service (AMS) on the server running Windows Server OS
The server running a Windows Server 2012 R2, Windows Server 2016, or Windows Server 2019 operating system with
Agentless Management Service (AMS) version 1.40.0.0 installed, the ams.exe process will exhibit an increasing handle
count. Handle leaks can cause performance issues overtime due to over consumption of memory.
