HPE SimpliVity
1820645 Members
2048 Online
109626 Solutions
New Discussion юеВ

SimpliVity plug-in connect to one fo the OVC instead of MVA

 
SOLVED
Go to solution
adam900331
Frequent Advisor

SimpliVity plug-in connect to one fo the OVC instead of MVA

Hy!

I have a 2 node SimpliVity environment (HPE DL380) and the SimpliVity federation show under the Management Information pane: "The HPE SimpliVity plug-in is in degraded management state."

The VMware verison is 7.0.3. The SimpliVity plug-in version is 4.1.3.16.

I think the plug-in should be connected to the MVA. How can I config the plug-in to connec to MVA?

This environment is our client. My Simpli┼░Vity environment connected to the MVA.

Thanks!

Adam

4 REPLIES 4
adam900331
Frequent Advisor

Re: SimpliVity plug-in connect to one fo the OVC instead of MVA

Anyone?

Aditya_A
HPE Pro

Re: SimpliVity plug-in connect to one fo the OVC instead of MVA

Hi,

 

Could you confirm if you are facing this issue after upgrading the OVC?

If the MVA is in degraded state, you will have to log a case with support to get it fixed, which may require removal and re-deployment of MVA, which is a non-destructive procedure.

I'm an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo
adam900331
Frequent Advisor

Re: SimpliVity plug-in connect to one fo the OVC instead of MVA

Hello,

Are there any step-by-step to redeploy the MVA?

Thanks.

Aditya_A
HPE Pro
Solution

Re: SimpliVity plug-in connect to one fo the OVC instead of MVA

Hi,
You'll find the step-by-step documentation for deployment of MVA here at page 125: https://support.hpe.com/hpesc/public/docDisplay?docLocale=en_US&docId=a00131388en_us


However, since you need to re-deploy, you will have to use command line to remove the MVA from the cluster first (dsv-mva-delete).
Steps to remove MVA:

sudo su

source /var/tmp/build/bin/appsetup

You can obtain the MVA id using command: dsv-mva-show 

To remove MVA: dsv-mva-delete --id <MVA id> --username <vCenter username>


In case you have upgraded the OVC but not the MVA, then you will have to upload the MVA tar file of the same version as OVC in /mva/deploy folder of each OVC in the cluster where MVA will be deployed.

I'm an HPE employee.
[Any personal opinions expressed are mine, and not official statements on behalf of Hewlett Packard Enterprise]
Accept or Kudo