HPE SimpliVity Plug-in cannot complete the task because it cannot contact the HPE OmniStack virtual

[coretizora]

Hi Everyone 

I recently had a vcenter siyying on a vm, i have moved it to a standalone windows machine, we are using simplivity. we installed HPE Simplivity plugin for Omnistack version 3.7.8. It seems to be working fine.. the only issue is that its failing to communicate with Omnistack Virtual Controller

Please Advise.

Khonzani Tizora

[LiamP]

1. What are you seeing/errors in vCenter's virgo logs associated with the HPe SimpliVity Plugin?
2. Is the plugin visible in vCenter
3. Is port 9190 open?

[Kripanidhi]

Basend on your question, my understading is that you moved the nodes to another vCenter, if this is the case.

1. Port 9190 should be reachable from Vcenter to OVC management network.

2. If this is moved ,please reach out to support and they would have to register the nodes to new vCenter server. using commands.

[gustenar]

@coretizora 

You need to update the OmniStack controllers with the new vCenter information. I would suggest running this command on all OVCs, one at a time:

To get root access:

>sudo su

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

Then run:

_{dsv-update-vcenter --server <IP address of new vCenter Server> --user <vsphere administrator with domain> --password <vsphere admin password>}

Have in mind that this command requires rebooting the Omnistack controller. You may need to plan for a maintenance window.

Hope it helps.

[BenH10]

I just had to run this command after restoring vCenter, there is some information missing to this. Special characters are not really supported with this command, place a "\" before every special characeter and make sure the password is surrounded by single quotes. 

Run SVT-VM-SHOW before running this command and verify all VMs are HA compliant. The command is going to reboot the OVC right after running the command. 

If this does not fix the issue, re install the plugin. I recoomend using the vCenter Server Appliance for vCenter. The Windows version of vCenter is no longer being developed. 

[Daniel_ST]

Hi, I have the same problem. I need to update the controllers. I have OmniStack 4.0.0 and when I try to execute the command I get an error:

_{dsv-update-vcenter : command not found}

Thanks in advanced!
Daniel

[B0ris]

@Daniel_ST: Did you execute this commands prior to executing dsv-update-vcenter:

sudo su

source /var/tmp/build/bin/appsetup

[Rajini_Saini]

Please elevated the access to root to try the dsv commands.

sudo su
source source /var/tmp/build/bin/appsetup

and then try the dsv command with its options.

[Daniel_ST]

Ok, thanks you ...

my mistake was to write  #source /var/tmp/build/bin/appsetup

Now all ok.

One more question... Can i execute the command and reinitialice the OmniStack more later, when I can or the command  do a reinitialice at the moment ?

P.D. (sorry by my english)

Thanks!

[Rajini_Saini]

Please run the command when you are ready to reboot the OVC.
The command requires OVC reboot for the update to take place.

[Daniel_ST]

Hi, i have OVC 4.0.0 and do all the steps that you write for add to a new VCSA 6.7 (last in the HP Support web). All the steps show correct result but i have some problems.

1º. When i write "svt-vm-show" or "svt-federation-show" i get "ERROR [47]: Missing session credentials."

2º. Working throught VCSA 6.7, the access that need to show esxi hosts, vms or datacenter is very very very slow. An example, when i need to move one vm to another esxi host, when i must select the new host, it's very very slow to show the two hosts that i have.

Before I execute the "dsv-update-center" i can navigate normally throught the vcsa but without the simplivity plug-in.

Thanks in advanced, i really need help.

[Rajini_Saini]

Hi,

If you have moved the hosts to a new Vcenter, the new vCenter details have to be updated using the 'dsv-update-vcenter' command.  Please note this will reboot the OVC and has to be done one OVC at a time.
If you have rebooted the vCenter and facing a plugin slow issue, then please check the OVC from vCenter GUI,  Select OVC - > Summary Tab-> if the 3 IP addresses are same, then launch web console of OVC, keep it open for 10 seconds and you should see the OVC showing the 3 IP's correct.
Do this on all the OVC in the federation if the OVC 3IP's are the same.

Thanks,
Rajini

[Daniel_ST]

The three IPs are different. I'm going to write the steps that I did when I have a little time ... lot of work now ...

[A525-9410]

just a node for hint my self

1. new vcenter , verify right version build, 

2. install right version plug-in

in vc add SVT host in to cluster

3.  into ovc

verify all ip address is good status

sudo su

source /var/tmp/build/bin/appsetup

dsv-update-vcenter --server 192.168.100.10 --user administrator@vsphere.local --password P@ssw0rd

..............the ovc will need reboot .....

4. if still cant display in VC Federation view      

sudo su

source /var/tmp/build/bin/appsetup

goto  directory 

/var/tmp/build/dsv# ./dsv-update-conf --server  vc_ip_address

than refresh   HPE SimpliVity Federation    every thing  ok