HPE SimpliVity Plug-In not working properly in some VMs

[ChongYanYan]

Hi support,

I have recently upgrade my HPE SimpliVity solution to OVC 4.1.2 and running VCSA 7 U3G. After upgrade, I realize while I right click at the VM and choose "All HPE SimpliVity Actions", some are showing backups while some VMs are showing "No actions available". Do I need to lodge a support case for this?

[Deepak_K]

Hi ChongYanYan,

Thank you for reaching HPE.

Thank you for upgrading the OVC to 4.1.2 and vCenter to 7.0U3G. I would like to inform that there is more latest OVC version available got released recently. The present latest version of OVC 4.1.3. We recommend you to upgrade to the latest version.

For the SimpliVity Plug-In Issues - Have you uninstalled the old plug-in version from all the linked mode vCenters ? if no, we request you to uninstall the old plug-in from all the linked mode vCneters and install the latest plug-in on all the linked mode vCenters. Please refer the below documents:

1. How to uninstall SimpliVity Plug-In:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000044489en_us

2. How to install SimpliVity Plug-In: Refer Page No. 14 - 15:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00123772en_us

3. SimpliVity - Understanding and Troubleshooting Web Client Plugin Performance Issues:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000046864en_us

Please find the below documents links for the latest OVC version 4.1.3:

HPE OmniStack 4.1.3 for vSphere Release Notes: 
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00126378en_us

HPE OmniStack 4.1.3 for vSphere Deployment Guide: 
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00126377en_us

HPE OmniStack 4.1.3 for vSphere Upgrade Guide:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00126380en_us

HPE OmniStack 4.1.3 for vSphere Administration Guide:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00126375en_us

HPE OmniStack 4.1.3 Command Reference Guide 
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00126368en_us

Thanks
Deepak
HPE

[ChongYanYan]

Hi Deepak,

Thank you for your response and letting us know there is a latest OVC version 4.1.3.

As for my situation, I was actually performing upgrading exercise for another HPE SimpliVity environment, with only one vCenter Server make available, and I was upgraded from OVC 3.7.5, and vCenter Server 6.5 U2C which was previously running on Windows. So when I upgraded to VCSA 7.0 U3G, I installed VCSA 7.0 U3G from fresh, and later to re-point the SimpliVity hosts to VCSA 7.0 U3G. Therefor in this case my plug-in was freshly installed in VCSA 7.0 U3G.

For the document "SimpliVity - Understanding and Troubleshooting Web Client Plugin Performance Issues:" you have shared, which issue inside the document do you think it will be helpful to my current situation? I have roughly gone through but it seems like not reflecting in my current scenario.

Looking forward to your feedback in this case, thank you.

[Deepak_K]

Hi ChongYanYan,

Thank you for writing to us back.

Please follow the steps mentioned in the below KB article:
https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=sf000082926en_us

If the issue persist even after following the above KB article, please share the Serial Number of the server in a private conversation so that the issue can be investigated further.

Thanks
Deepak
HPE

[ChongYanYan]

Hi Deepak,

Thank you for sharing KB article. Before performing the steps:

#sudo su

#source /var/tmp/build/bin/appsetup 

#dsv-hyperproxy register-extension <vCenter Admin username> <vCenter Admin Password>

Does the above steps to cause the OVC to reboot? If yes, I will arrange for a downtime to perform the steps above. Thank you.

[Deepak_K]

Hi ChongYanYan,

Thank you for writing to us back.

dsv-update-vcenter --server "IP address of new vCenter Server" --user  "vCenterAdministrator user" - The OVC will go for a reboot.

For an example:

Check for the VMs Storage HA sync by running the command svt-vm-show. In the output check for the column which says as "Storage HA". All the VMs "Storage HA" must show as "Yes". You might see other status as "Unknown" for a template and powered off VMs which is fine. Once all the VMs are in Storage HA sync.
Run the above command on OVC-1. Wait for the OVC to reboot completely. Check for the VMs Storage HA sync by running the command svt-vm-show. In the output check for the column which says as "Storage HA". All the VMs "Storage HA" must show as "Yes". You might see other status as "Unknown" for a template and powered off VMs. Once all the VMs are in Storage HA sync. Go for the OVC-2 and so on...

dsv-hyperproxy register-extension "vCenter Admin username" "vCenter Admin Password" - The OVC will not go for a reboot.- The OVC will not go for a reboot.

In a multi-node cluster - If all the VMs are in Storage HA Sync and only, if the OVC is rebooted - no need to migrate the VMs from the host.

Note: If it is a two nodes cluster - ensure the OVCs are connected to the Arbiter.

Thanks
Deepak
HPE