How to safely change IP addresses of vCenter, ESXi hosts, and OVC (HPE SimpliVity)?

[carlostorres]

Estou planejando uma tarefa de manutenção que envolve a alteração de endereços IP em um ambiente executando o HPE SimpliVity 5.x no vSphere e gostaria de confirmar se há uma sequência recomendada ou práticas recomendadas a serem seguidas para garantir uma transição tranquila sem afetar a disponibilidade da VM.

Aqui está o cenário:

Alterar o IP de gerenciamento do vCenter Server (executando como uma VM);

Alterando os IPs de gerenciamento dos hosts ESXi ;

Alterando os IPs de gerenciamento do OVC (OmniStack Virtual Controller) , incluindo possivelmente o gateway.

Minhas perguntas são:

1. Existe uma ordem ideal para executar essas alterações? (vCenter → OVC → ESXi ou uma sequência diferente?)

2. Depois de usar dsv-address-change no OVC, é obrigatório executar dsv-peer-reset de outro OVC?

3. O plugin SimpliVity no vCenter precisará ser reconfigurado após alterar o IP do vCenter?

4. É necessário remover e reassociar o OVC ao vCenter?

5. Mais importante: existe um documento oficial da HPE ou um artigo da KB abordando esse procedimento completo de alteração de IP?
   
   

**Google Translate**

This is a maintenance task that involves altering IP addresses in an environment running HPE SimpliVity 5.x no vSphere and you should confirm whether there is a recommended sequence or recommended practice to be followed to ensure a smooth transition. remove availability from VM.

Here is the dinner:

Change the management IP of vCenter Server (running as a VM);

Altering the IPs of managing ESXi hosts;

Altering the management IPs of the OVC (OmniStack Virtual Controller), possibly including the gateway.

Minhas perguntas são:

1. Is there an ideal order for carrying out these alterations? (vCenter → OVC → ESXi or a different sequence?)
2. After using dsv-address-change on OVC, is it mandatory to perform dsv-peer-reset on another OVC?
3. Will the SimpliVity plugin in vCenter be reconfigured after changing the IP of vCenter?
4. Is it necessary to remove and reassociate the OVC with the vCenter?
5. More importantly: is there an official document from HPE or an article from KB addressing the complete IP alteration process?

[Sanika]

Hi @carlostorres 

1. The recommended sequence for changing IP addresses in your SimpliVity environment is as follows:

• vCenter Server:  Change the management IP of the vCenter Server first.
• ESXi Hosts:  Then, change the IP addresses of the ESXi hosts.
• OmniStack Virtual Controllers (OVCs):  Lastly, change the OVC IP addresses.

This order ensures that dependencies are handled properly, as OVCs rely on the vCenter and ESXi hosts for communication and management.

2. After using dsv-address-change on the OVC, it is mandatory to run dsv-peer-reset from another OVC in the federation. This ensures all OVCs re-establish communication with the updated OVC.

3. SimpliVity Plugin in vCenter:  If the vCenter IP changes, the plugin may fail to connect to OVCs. In this case, HPE SimpliVity plugin may need to be reconfigured or re-registered with the new vCenter IP address. 
Also, ensure the plugin version is compatible with the new vCenter version,

4. OVC Reassociation: If the vCenter IP address changes, it is not always necessary to remove and re-associate the OVCs to vCenter, but you should:

• Verify connectivity between the OVCs and vCenter.
• Check if the OVCs recognize the new vCenter IP automatically (this depends on the configuration). If there are issues, you may need to manually re-associate the OVCs with vCenter.

5. For more information on this, you may refer to the below docs:
HPE SimpliVity's Administrator Guide and Deployment Guide for your version.
VMware vSphere documentation for changing vCenter and ESXi management IPs.

Regards,
Sanika.

If you feel this was helpful, please click the KUDOS thumb below. Also consider marking this as an "Accepted Solution" , if the post has helped to solve your issue.