Change certificate in vCenter broke the Simplivty Plugin

[wesmrt]

Hello,

We have two Simplivty DL380 Gen10 nodes with a cluster in VCSA 6.5.

We try to change the certificate from vcenter to a certificate assign by our internal CA. After the change, the Simplivity plugin for vCenter don't work anymore. We receive the "response error 400". We rollback the certificate and everything back to normal.

How can i proceed in this scenario to change the certificate? Do I have to uninstall the plugin and install again after change the certificate?

My Simplivity version is 3.7.9.279.

Thanks!

[JohnHHaines]

No, the problem is not with the plug-in, it is with the authentication of the OVC to vCenter - the plug-in can't get any info because the SimplIVity side of the system can't log in. 

If you change the certificate in vCenter, you break the authentication of the OVC to vCenter.

I would suggest opening a Support call, and walking through the update wiht Support - you would need to update the OVC authentication, but I am not sure how you log in to the OVC once you apply the new certificate.

It IS possible to do this, though.

John

I am an HPE Employee

[wesmrt]

Thank you, John. I will open a support call for this. I thought it was something simpler.

[julioadmtibr]

Hello,

You can solve this?

[B0ris]

First try to do the following:

- login into OVC with username svtcli and password that you provided during deployment

- sudo su

- source /var/tmp/build/bin/appsetup

- dsv-update-vcenter --server "you vcenter server IP" --username "vcenter credentials" --password "vcenter credentials"

[gustenar]

Just have in mind this command will reboot the OVC. 

[TamesM]

This fixed it for us: https://support.hpe.com/hpesc/public/docDisplay?docId=sf000097959en_us&docLocale=en_US

No reboot required and everything started working.

In case the link goes dead in the future, these were the steps:

Login with 'svtcli' user. Then run this:

$ sudo su
# source /var/tmp/build/bin/appsetup
# dsv-reload-vc-cert --username administrator@vsphere.local --password 'password' --server '<vcenter ip>'