03-12-2022 08:16 AM
Peoples,
We had a problem with a HX node and I needed to re-install ESXi on and and now I am trying add the node to the HX cluster (two nodes are in place today and am trying to re-add the third).
I keep running into this error.
03-14-2022 08:33 AM
Are you using the same HX Installer version as the HX cluster?
Unfortunately the HX Installer logs are scattered in several files.
Nodes which were previously in the cluster can NOT be re-added using the HX expansion.
This is a workflow which Cisco TAC can walk through with you.
03-14-2022 09:26 AM
Steven,
Thanks for the response. We are using the same installer version as the HX cluster. This node was a part of the cluster, and I did see the call out of nodes that were part of the cluster can not be re-added. However, I am not sure how HX would know if its a fresh ESXi install with all new IPs everywhere. Personally, I would rather be self sufficient vs having to go to TAC since this doesn't look like a bug.
Mind telling me what specifically is going on within HX that is preventing the re-adding of a node?
03-14-2022 10:17 AM
Hyperflex Installer "Cluster expansion" is for never before seen, net-new, servers.
Since the cluster has "seen" these disks and motherboard before this is NOT a "Cluster expansion", but a "node replacement".
The "node replacement" workflow wasn't something HX Engineering put into the HX Installer so Cisco TAC support is required.
The server motherboard UUID and the disk UUIDs are already in the HX cluster database under-the-hood.
I agree that the order-of-events you've done is something which should be doable by the end-customers without Cisco TAC support.
I hear rumors of "node replacement" being added to Intersight so the end customer can self service this very common scenario.
Find answers to your questions by entering keywords or phrases in the Search bar above. New here? Use these resources to familiarize yourself with the community: