HPE Community read-only access December 15, 2018
This is a maintenance upgrade. You will be able to read articles and posts, but not post or reply.
Hours:
Dec 15, 4:00 am to 10:00 am UTC
Dec 14, 10:00 pm CST to Dec 15, 4:00 am CST
Dec 14, 8:00 pm PST to Dec 15, 2:00 am PST
HPE SimpliVity
cancel
Showing results for 
Search instead for 
Did you mean: 

Can we manually add the host into the new vCenter if the previous vCenter was crash ?

 
SOLVED
Go to solution
Highlighted
jacky5001
Occasional Visitor

Can we manually add the host into the new vCenter if the previous vCenter was crash ?

what should we do inside the OVC after adding the host into the new vCenter? any downtime required? how do we verify if everything was working fine after added into new vCenter?

3 REPLIES
jacky5001
Occasional Visitor

Re: Can we manually add the host into the new vCenter if the previous vCenter was crash ?

can anyone provide me the step or guide on how to do the vcenter repointing? require any downtime?

DowS
HPE Pro
Solution

Re: Can we manually add the host into the new vCenter if the previous vCenter was crash ?

Hi Jacky5001,

    • If the Current Simplivity version you are running is above 3.7.3 then you can run these commands yourself if below 3.7.3 then A support case will be required and an engineer will need to run these for you.
    • Pointing the clusters to a new vCenter can be done with a 2 single command's (Steps 3&4) but will require a reboot of the OVC's which is initiated by the first update command.
    • These commands need to be ran from every OVC in the federation.
    • Downtime is not required as IP failover will migrate the running state of the VM's to the other node in the HA pair.

     

    1. Elevate permissions prior to running below commands.
    • sudo su
    • source /var/tmp/build/bin/appsetup

     

    1. Confirm all VM's are in HA sync prior to running commands to ensure IP failover will migrate running state.
    • svt-vm-show (If all VM's are not in HA Sync then open support case for assistance) 

     

    1.  This command will initiate a reboot of OVC
    • dsv-update-vcenter --server <IP of vCenter> --user <HMS User> --password <HMS Password>   

    HMS User = administrator@vsphere.local

    1. This command is non-intrusive and will only restart some of the authentication services.
    • dsv-identitystore-init <HMS User> <Host IP> <Host User>  <HMS Password> <Host Password> 

    HMS User = administrator@vsphere.local 

    Host IP = vmkernel management IP address of ESXi host housing specific OVC

    ​​​​​​​Host User = Root

     

    1. Confirm federation is healthy after re-point.
    • svt-federation-show

     

    I would advise that you open a support case for assistance if you encounter any issues running these commands 


I am an HPE Employee
jacky5001
Occasional Visitor

Re: Can we manually add the host into the new vCenter if the previous vCenter was crash ?

Thank you Sir. it's working fine after i did the repointing. svtfs running and svt-federation-show showing alive and connected