Simplivity Action "Shutdown Virtual Controller" error Unexpected server error

[dbartlett]

Has anyone seen this. We deployed 2 new hosts and one of the hosts when trying to shutdown Virtual controller from SimpliVity Action we get an error "Unexpected server error." but we can safely shutdown the OVC through CLI.

I also notice that the icon for Omnicube is different from the rest. Not sure if that means anything.

The omnistack that does not have the 3 dots is the one that gets the Unexpected error.

The other works fine and checking the rest of the omnistacks we have in our vcenter all has those 3 dots in the icon

Weve been working with support and so far no resolution yet.

[gustenar]

Hello @dbartlett, 

The three dots mean that the OmniStack controller VM is being managed by SimpliVity. Not having the dots is most likely the reason of the error as it probably can't communicate properly with vCenter. Since this is a fresh installation, try the command:

"dsv-update-vcenter --username <vCenter admin account> --server <vCenter IP address> --password <vCenter admin password"

Reboot the OVC when prompted to do so. This should help fix the issue. Let me know how it works. 

[dbartlett]

@gustenar  thank you for the steps provided. I followed and ran this command but still was not able to resolve the issue.

Another thing I noticed is that when I click this OVC the Summary page does not say "Managed by: SimpliVity" whereas the other does.

[gustenar]

Yes, that's what I mentioned before. The three dots mean it is being managed by SimpliVity. This is your main issue at the moment. Here's another thing to check. Click on the OmniStack controller and go to the "Configure menu", check the vApp Options (should be enabled). Select "OVF Details" and see that the "OVF environment transport" has the "ISO image" checked. Compare the settings with another OVC that shows managed by SimpliVity. 

[dbartlett]

I did found a couple days ago that vApp options was not enabled so I manually enabled it. Configured it exactly the same as the one that works. 

Rebooted the OVC but still no go.

[gustenar]

Run the command "svt-extension-refresh" on the non working OVC. Log out of vCEnter and re-login to see if the status changes. 

[dbartlett · Accepted solution]

@ gustenar  I wanted to let you know that your first advice of running the dsv-update command worked.

what happened was I had to deploy another cluster and one host joined with IP instead of FQDN, as soon as I made changes and remove from Inventory and readd it had the same issue with OVC controller. I ran the dsv-update command and that worked.

So thern I tried it again on the one I posted about but had to disable the vApp option first then run the command and it worked.

Thank you so much

[gustenar]

That's great! Thanks for sharing the resolution.