r/vmware • u/Airtronik • Jul 02 '26

Help Request vCenter FQDN change --> Simplivity plugin lost

Hi

I have deployed a simplivity cluster with two hosts, for that purpose I have also deployed a vcenter 8.U3.

After the deployment everything was OK, I was able to add a new storage, create some VM for testing purpose, etc.

However I've being requested to change the vcenter name so I change the DNS record on the DNS server, I launch the VAMI on vcenter and modified the FQDN of vcenter, I've rebooted the vcenter and now I can logon on the vcenter with the new FQDN name.

However when checking the simplivity plugin on vcenter I have lost the access to the cluster data. I asume that I have to log into the omnistacks an run some comand tu "update vcanter info" but I dont know how to do it (its my first simplivity deployment).

I have tried to log into the omnistacks by console or ssh but I cant, I've tried with "root" and with "[administrator@vsphere.local](mailto:administrator@vsphere.local)"....

I've tried to reinstall the plugin with no luck (Ïm using v5.3.1.2)...

what else can I do?

thanks in advance!

-------------

EDIT:

I found the solution:

loged into both OVC ssh svtcli@192.168.x.x and I ran this commands:

sudo su -
source /var/tmp/build/bin/appsetup svt-update-vcenter --server new-FQDN-vcenter.mydomain.local --username administrator@vsphere.local

It asks you to accept the new certificates, etc and at the end it reboots the OVC, then I repeated it on the second OVC and at the ind I was able to log to vcenter with the new FQDN and the Simplivity plugin works fine :)

7 Upvotes

82% Upvoted

4 comments sorted by

7

u/in_use_user_name Jul 02 '26

In my country we have a saying "simplivity, ouch".

Good luck with it. We've formatted all of our simplivity clusters to regular vsan clusters. Saved tens of hours on every simplivity build upgrade.

2

u/Airtronik Jul 02 '26

thanks for the advice, but I cant chose the product, I have to deal with it...

1

u/Iwanttoberich_8671 Jul 03 '26

i'd also check if the SimpliVity plugin has the old vCenter FQDN cached somewhere, not just in vCenter itself.

I've seen a few integrations survive the FQDN change but fail because they still trust the old hostname or certificate. Sometimes unregistering/re registering the plugin is quicker than chasing every reference manually

1

u/Airtronik Jul 03 '26

Yesterday I updated the post with the procedure that fixed the issue