Print | Rate this content

Advisory: HPE ProLiant Gen9 or Gen10 Servers - HPE Agentless Management Service For VMware ESXi Stops and Restarts When a Link Event Occurs on a NIC Port Configured With Multiple IPv6 Addresses

SUPPORT COMMUNICATION - CUSTOMER ADVISORY

Document ID: a00059794en_us

Version: 1

Advisory: HPE ProLiant Gen9 or Gen10 Servers - HPE Agentless Management Service For VMware ESXi Stops and Restarts When a Link Event Occurs on a NIC Port Configured With Multiple IPv6 Addresses
NOTICE: The information in this document, including products and software versions, is current as of the Release Date. This document is subject to change without notice.

Release Date: 2018-11-06

Last Updated: 2018-11-06


DESCRIPTION

On an HPE ProLiant Gen9 or Gen10 server running VMware ESXi 6.0, 6.5 or 6.7 with Agentless Management Service (AMS) version 11.2.0 (or later), when a NIC port is configured with multiple IPv6 addresses and its link status changes, the HPE Agentless Management Service will crash, causing health monitoring and reporting to stop. The service will attempt to restart after a certain time (within 10 minutes or earlier).

Note: When AMS tries to restart, it successfully restarts, but it will fail again if another state change occurs. The current state of the NIC port when AMS restarts would be the initial state, it should not cause AMS to fail quickly as it restarts.

The following message will be seen in the vmkernel.log indicating AMS crashed:

amsd: wantCoreDump:amsd signal:6 exitCode:0 coredump:disabled

OR

ams-main: wantCoreDump:ams-main signal:6 exitCode:0 coredump:disabled

The following messages will be seen in the syslog.log indicating AMS is restarting:

2018-09-19T01:57:58Z root: amsd-wd: Detected one or more AMS process(es) have stopped running. Restarting...
2018-09-19T01:57:58Z root: amsd stop service...
2018-09-19T01:58:00Z root: amsd-wd: AMS start...

SCOPE

Any HPE ProLiant Gen9 or Gen10 server running VMware ESXi 6.0, 6.5 or 6.7 with Agentless Management Service (AMS) version 11.2.0 ((or later).

RESOLUTION

A future release of Agentless Management Service (AMS) will correct this issue.

As a workaround, assign only one IPv6 address to the NIC port(s) to keep the Agentless Management Service health monitoring and reporting functioning.

The advisory will be updated when the solution becomes available.




NOTE:Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.




RECEIVE PROACTIVE UPDATES : Receive support alerts (such as Customer Advisories), as well as updates on drivers, software, firmware, and customer replaceable components, proactively via e-mail through HPE Subscriber's Choice. Sign up for Subscriber's Choice at the following URL: Proactive Updates Subscription Form.

NAVIGATION TIP : For hints on navigating HPE.com to locate the latest drivers, patches, and other support software downloads for ProLiant servers and Options, refer to the Navigation Tips document .

SEARCH TIP : For hints on locating similar documents on HPE.com, refer to the Search Tips Document .


Hardware Platforms Affected: HPE ProLiant ML30 Gen9 Server, HPE ProLiant DL360 Gen10 Server, HPE ProLiant BL460c Gen10 Server Blade, HPE Synergy 660 Gen10 Compute Module, HPE ProLiant DL380 Gen10 Server, HPE ProLiant DL560 Gen10 Server, HPE ProLiant XL230k Gen10 Server, HPE ProLiant XL170r Gen10 Server, HPE ProLiant XL190r Gen10 Server, HPE ProLiant DL580 Gen10 Server, HPE ProLiant ML110 Gen10 Server, HPE ProLiant ML350 Gen10 Server, HPE ProLiant XL450 Gen10 Server, HPE ProLiant DL385 Gen10 Server, HPE ProLiant DL180 Gen9 Server, HPE ProLiant DL360 Gen9 Server, HPE ProLiant BL460c Gen9 Server Blade, HPE ProLiant DL380 Gen9 Server, HPE ProLiant ML350 Gen9 Server, HPE ProLiant XL230a Gen9 Server, HPE ProLiant XL250a Gen9 Server, HPE ProLiant DL120 Gen9 Server, HPE ProLiant ML150 Gen9 Server, HPE ProLiant DL60 Gen9 Server, HPE ProLiant DL80 Gen9 Server, HPE ProLiant ML110 Gen9 Server, HPE ProLiant XL170r Gen9 Server, HPE ProLiant XL190r Gen9 Server, HPE ProLiant DL580 Gen9 Server, HPE ProLiant BL660c Gen9 Server Blade, HPE ProLiant DL560 Gen9 Server, HPE Apollo 4200 Gen9 Server, HPE ProLiant XL450 Gen9 Server
Operating Systems Affected: Not Applicable
Software Affected: Not Applicable
Support Communication Cross Reference ID: SIK3817
©Copyright 2018 Hewlett Packard Enterprise Development LP
Hewlett Packard Enterprise Development shall not be liable for technical or editorial errors or omissions contained herein. The information provided is provided "as is" without warranty of any kind. To the extent permitted by law, neither HPE nor its affiliates, subcontractors or suppliers will be liable for incidental, special or consequential damages including downtime cost; lost profits; damages relating to the procurement of substitute products or services; or damages for loss of data, or software restoration. The information in this document is subject to change without notice. Hewlett Packard Enterprise Development and the names of Hewlett Packard Enterprise Development products referenced herein are trademarks of Hewlett Packard Enterprise Development in the United States and other countries. Other product and company names mentioned herein may be trademarks of their respective owners.

Legal Disclaimer: Products sold prior to the November 1, 2015 separation of Hewlett-Packard Company into Hewlett Packard Enterprise Company and HP Inc. may have older product names and model numbers that differ from current models.

Provide feedback

Please rate the information on this page to help us improve our content. Thank you!
Document title: Advisory: HPE ProLiant Gen9 or Gen10 Servers - HPE Agentless Management Service For VMware ESXi Stops and Restarts When a Link Event Occurs on a NIC Port Configured With Multiple IPv6 Addresses
Document ID: emr_na-a00059794en_us-1
How helpful was this document?
How can we improve this document?
Note: Only English language comments can be accepted at this time.
Please wait while we process your request.