OPERATIONAL DEFECT DATABASE
...
...
When recovering a node or resetting the system, the HPE Hyper Converged 380 (HC380) System node must be rebooted after the recovery installation. This additional reboot step is currently missing from the recovery and reset procedures in theHPE Hyper Converged 380 User Guide.Failing to reboot the node prevents the ESXi High Availability (HA) from forming properly when joined into the ESXi cluster.
Any HPE Hyper Converged 380 (HC380) System with either of the following VMware ESXI Operating Systems:VMware ESXi 5.5VMware ESXi 6.0
When following the HPE Hyper Converged 380 User Guide procedure for “Recovering a single node” or “Resetting the system,” add a step to reboot the node as shown below.For the “Recovering a single node” procedure, reboot the node as Step 10 under the sub-section “Recovering the node.”Figure 1. Recovering the node -Look for a file named "SUCCESS"and reboot the node:For the “Resetting the system” procedure, reboot the node as Step 10 under the sub-section “Install VMware vSphere ESXi from a USB drive.”Figure 2. Resetting the system, reboot the node: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 theNavigation Tips document.SEARCH TIP: For hints on locating similar documents on HPE.com, refer to theSearch Tips document.
Operating Systems Affected:Not Applicable
No external links available for this bug
Click on a version to see all relevant bugs
Hewlett Packard Enterprise Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
