Adding third node to existing cluster...ERROR Step 8 of 43 ERR_INVALID_CONFIG

[bballlal]

I'm trying to deploy a 3rd node in an existing cluster. I'm getting the following error in the orchestrator logs: DeployStatus(status:ERROR, detail:ERR_INVALID_CONFIG, message:Step 8 of 43: ERR_INVALID_CONFIG: A configuration parameter is invalid. - target.boot could not be determined at /opt/svtdi/hvitool/Plugin/Esxi.pm line 134.

Our SimpliVity version is 4.1.2 and I've booted the new node from file deploy-installer-11.93.1-psi29+sva-4.1.2.185-usb-tiny.img. I've seen other posts that say this is most likely a RAID problem. This is a Large node and Smart Storage Administrator is saying that I have 1 array and 3 logical drives. Logical Drive 1 is 200 GB, Drive 2 is 1 TB, and Drive 3 is 16.27 TB. 

Our existing ESXi nodes are on version 7.0 Update 3g. The hypervisor file in the software download I'm using is called hypervisorImage-19193900.2-hp.tar which is ESXi 7.0 Update 3c so I'm assuming I'm going to have to patch it to 7.0 Update 3g after running the Deployment Manager. 

I've already downgraded firmware on the new third node to match the firmware in the existing nodes, not sure if that was necessary or not. 

Any suggestions on how to resolve this error? If I need to delete and recreate a logical drive, which one? 

[Mahesh202 · Accepted solution]

Hi bballlal

I would suggest a Plan Of Action that you may want to try.

1. Download the 4.1.3 bundle.
2. Factory reset with 4.1.3 tiny image.
3. In the downloads folder, put ESXi 7u3f zip, and OVA of 4.1.2.

Use the 4.1.3 deployment manager and attempt deployment.

Please refer to the below-mentioned KB article: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000067655en_us

If you need assistance in downloading the image or have any further queries you can get in touch with HPE SimpliVity Tech Support.

Hope this helps.!!

Regards
Mahesh

[gustenar]

@bballlal 

Usually this is fixed by doing the following: 

- Make sure that you factory reset the node before attempting to redeploy it. Factory reset will clear the arrays and make them happy for redeployment. Check this document for the procedure, it is a bit outdated but still valid: 

https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000067656en_us

- Also, once you have factory reset the node appropiately make sure that you keep the tiny image mounted when you are running the Deployment Manager. 

Hope it helps. 

[bballlal]

Thanks everyone and thanks for the article showing what arrays to delete. Everything I read said that the factory reset option was removed in 4.0.1 and I wasn't sure the process on rebuilding the array. I'll give that a try. 

[gustenar]

It is just done a bit different now because we don't offer the full images anymore and only those will show the "factory reset" option. 

[bballlal]

I think the issue is our new Gen10 SimpliVity node has an HPE NS204i-p Gen10+ Boot Controller and it looks like that isn't supported until version 4.1.3 and I'm trying to deploy 4.1.2. I will try the steps in that article to deploy 4.1.2 by booting off the 4.1.3 tiny image and having only the 4.1.2 OVA and .tar file in the Downloads folder. 

[gustenar]

Deploying with 4.1.2 may cause issues if the appropiate drivers for that controller are not available. It might be best to upgrade your federation to 4.1.3 and then deploy the new node. 

[Aditya_A]

Hello bballlal,

Let us know if you were able to resolve the issue.

If you have no further queries and you are satisfied with the answer then kindly mark the topic as Solved so that it is helpful for all community members.

[bballlal]

This was the solution because the NS204i-p card isn't supported until 4.1.3. I had a ticket open with support but I was able to get a resolution here faster. Thanks everyone. 

[Sunitha_Mod]

Hello @bballlal,

Perfect! 

We are glad to know the issue has been resolved.