Nimble DHCI "OneClick Update"

[Bernd_Mueller_MCL]

Hi,

I have a qestion regarding Nimble DHCI "OneClick Update".

Is there anyone who has successfully performed a Nimble DHCI "OneClick Update"?

Three different environments, ZERO successful OneClick Updates!

(Erros were: "Not all Hosts have access to all volumes" (false error, all Hosts have access to all volumes!) "Not enough space in /scratch to unpack ssp", "vMotion not enabled on the MGMT Protgroup (but enabled in a vMotion Portgroup) "Updates show up , but the update button is greyed out..... to name some of the errors.

My coworkers also had ZERO success with the OneClick Updates.

Seems to me, the same developer team in charge for the HPE Oneview vLCM Updates that also never work, when you add any SPP to the image have written these scripts /s

[Mahesh202]

Hi Bernd_Mueller

I'm sorry to hear that you and your coworkers have experienced difficulties with the Nimble DHCI "OneClick Update" process. While I cannot speak to specific instances of failed updates, I can provide some general guidance on the OneClick Update process.

First, it's important to ensure that your environment meets the prerequisites for OneClick Updates, such as having the necessary connectivity, permissions, and resources. For example, if you're receiving an error message about hosts not having access to volumes, it may be worth double-checking your zoning and masking configurations to ensure that all hosts can access the necessary volumes.

Second, it's worth reviewing the release notes and known issues for the specific version of Nimble OS that you're updating to, as there may be specific caveats or requirements for the update process. For example, if you're receiving an error about not having enough space in /scratch to unpack ssp, it may be worth checking the release notes to see if there are any recommendations for increasing scratch space or clearing out temporary files.

Finally, if you continue to experience difficulties with OneClick Updates, it may be worth reaching out to HPE Nimble Tech support for assistance. They can help troubleshoot specific errors and provide guidance on best practices for updating your DHCI environment.

I hope this information is helpful, and I wish you the best of luck with your future update attempts.

Regards
Mahesh

[Sunitha_Mod]

Hello @Bernd_Mueller_MCL,

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

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

[scavendishjr]

Dozens of them and one running right now that is just about finished. It sounds like after the system was deployed someone tweaked your box. You cannot have a dedicated vMotion network. It needs to be on the core mgmt nic like it is when it is deployed. You cannot treat a dHCI solutions like any VMware cluster. This is where most people run into issues. For the disk., do you have a snapshop presented from an old recovery to a single host? Did you put a log datastore on each host? things that we all do in a typicale three tier architecture break HCI solutions. Treat this like you would an appliance and you will be a lot happier. If you want customerization stick to a non-DHCi type environment. Did you add all your hosts through the Inventory Add wizard? if not, drop them to be able to do the upgrade or better yet blank them and redeploy them the supported way. 

A lot of the updates will be greyed out. Check your infosight validated config matrix to see versions that should be available to you. Validated Configuration Matrix | HPE InfoSight

Also have several dozen implementations of the VMware vLCM and can patch firmware with zero issues (NOT IN A dHCI). Try reaching out to a partner who has done this a few times. Once you get it up it is really easy to maintain.