Need the 4.2 USB

[TDW1]

I am trying to do a factory reset using the tiny image to 4.2 but it is not working.  I get the option to deploy and can set it to waiting to be discovered, I getting the error that no OmniStack version available when running the deployment.  

Where can I find just the full USB, not the tiny image?  I am searching the HPE software site but I only get the option to download the bundle which only contains the tiny image.

[Sanika]

Hi @TDW1 ,

"deploy-installer-10.110.4-psinn-sva-n.n.n.n-usb-tiny.img" is specfically developed to perform factory reset from ILO which comes in the download called
"Q8A57-11090_SimpliVity_Deployment_Package_VMware_vSphere_n.n.n.zip". There are no other deploy installers included in this download. This is about 800MB in size. Since you can use ILO for factory reset, you don't need a USB stick.

The tiny images are the correct set of images and for mounting it you need to use the option of attaching the image as removable media as the file is of .img extension.
The new tiny image will provide the option to go for the direct deploy instead of performing a complete factory reset.

Please ensure you're using the correct tiny image downloaded from the HPE Software Center specifically for OmniStack 4.2.
You may refer to the HPE OmniStack 4.2.0 for vSphere release notes and HPE OmniStack 4.2.0 for vSphere Deployment Guide.
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00131390en_us
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00131389en_us

If you need a full USB image instead of tiny image for factory reset, I suggest contacting HPE Support and opening a support ticket. They should be able to assist you in obtaining the full USB image for the desired OmniStack version.

Hope this helps.

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution", if the post has helped to solve your issue.

[Convergo]

Also ask support to provide you the HPE SimpliVity 380 Factory Reset Guide. This gives you some more details regarding resetting the hardware specific part.

[Mahesh202]

Hi

1. To perform a factory reset of an HPE SimpliVity node on a DL380 Gen10 hardware build, the process may vary slightly depending on the specific configuration and requirements. However, in general, it is recommended to remove all existing logical drives to ensure a clean re-deployment.
2. To deploy an HPE SimpliVity node watch the video using the below link, it demonstrates how to deploy an HPE SimpliVity node

URL: https://support.hpe.com/hpesc/public/videoDisplay?videoId=vtc00030091en_us

Hope this helps.!!

Regards
Mahesh

[TDW1]

I received the full image from support and was able to do a factory reset, but it turns out the issue is not with what image I am using.  The install fails with an OVC compatiblility issue.  

I saw a forum discussion where it was suggested to change a line in the Simplivity.DM.View.exe.config file.  The line was for predeployment validation checks to "True" as below.  I changed that but it still does not resolve the compatability issue. 

<add key="PredeployValidationOverride" value="True"/>

When I run svt-federation-show, it shows the existing node in the cluster is at 4.2.0.97 which is the version I am trying to deploy.  But when I run svt-federation-show -o xml, the existing node shows to still be on 4.1.2.185 which was the previous version.

[gustenar]

The change you are referring to doesn't have to do with your issue, reason why it didn't help. I would suggest avoiding making these type of changes as you could be forcing the Deployment Manager to skip real issues. 

Now, if your federation is 4.1.x and no other server is 4.2.0 then you won't be able to install 4.2.0, even if it's a different cluster. The --xml output won't provide any different output than the command without the switch, so i'm a abit confused. It kinda sounds like your federation is 4.1.x, make sure that you install the same version for this new node. 

[TDW1]

gustenar

It was unknown what the issue was when I submitted the post.  The XML out IS different from the command with no switch as verified by support as well. 

From working with support, It was determined that all the cluster nodes in the federation need to be upgraded and then committed.