Changing vmotion IP address on running system

[tyrrvk]

Hi -

What steps are needed to migrate our VMkernel IP addresses to a new network? This is for a running cluster.

Switches are not vSwitches (distributed). I have 3 ESXi 5.5 hosts.

Primarily I am concerned about impact on running services etc.

Thanks.

Tim

[admin]

Hello,

Assuming that you are not going to Change any Management or iSCSI VMkernel IP and your goal is only VMotion IP .

You will not have any impact on running VM's if your Just going to change the vmotion VMkernel IP.

All you have to do is.

Step 1. Disable HA and DRS on the Cluster, so that it does not initiate any new Migrations

Step 2 :  Go to Network settings and change the vMotion VMkernel IP to New IP.

Step 3 : is its a dvs then Just on the dvs else , Do the step 2  on each host vswitch

Step 4 : Enable HA and DRS.

Thanks,
Avinash

[tyrrvk]

Awesome thank you.

Elaborating further on my question. My management and vmkernel ports are on the same vswitch, which is connected to a single physical nic (vmnic0).

So, If I am moving my vmkernel port to a new network, I'd need to setup a new vswitch connected to a vmnic on that new network correct?  Vmnics can only see one "vlan" and can't be on multiple networks?

If I decide to move my vmkernal AND management ports to this new separate network - what steps would be necessary? Is it possible without downtime?

Thank you.

Tim

[admin]

Actually If your going to leave the Management VMkernel Port and Just change the VMotion VMkernel port then you need not create a New vSwitch you could Just create another VMkernel port group on the same

vSwitct, And to Add you do not give a vlan to an vmnic ( ie the uplink), you give the vlan at the port group level.

if you decide to move it onto a different vswitch, you can move the vMotion VMkernel without a downtime. But the Management VMkernel does require a downtime.

let me know if your still not clarified.Please post a screenshot of your current network settings and your question.will provide you with steps

Thanks,

Avinash

[poliver21820]

Hi,

Here is a screenshot of the situation.

Node ESX04 is no longer connected to the cluster because of my change on the vMotion IP. At the same time, I changed the default gateway because I believed that it was necessary for vMotion too.

I can't modify this at the time because the property link is not active.

As a result, the VM on the left which are hosted on the esx04 node seem to be deconnected because the vCenter lost control on it.

The first thing for me would be to re-establish the link between esx04 and the vCenter. This means that I have to change the defautt gateway of the management network. Actually, I can't do that.

Regards.

[sjesse]

You need to connect to the host directly, being 5.0 you need to either go to the server or use a kvm. You can logon using the root esxi account and update the management network there, I have a feeling your vmotion vkernel adapter also had a management selected and vcenter was using that.