We have recently (a day ago) upgraded our servers from ESX 4.0 to ESX 4.1 but couldnt enable vMotion.
I have searched and found out how to enable it, but we dont seem to have any spare NICs.
Can I enable vMotion on existing VMKernal Ports that are for ISCSI?
maybe the screenshot will help you understand more..
so the below screenshot shows the ISCSI we have for storage..
This comes when i try to add new one.. none is available..
So editing ISCSI shows I can enable, but not too sure so i need advice from you guys..
We have 1 cluster, 2 hosts and a SAN. there are 4 Phycisal NICs on each hosts which are going to the two physical switch connecting to SAN.
I am a beginner in VMWare so let me know if you guys need any more info..
Welcome to the Community - You could but best practice is to create seperate vmkernel ports for vmotion and place them on their own sepeprate network which can be a seperate vlan -
Do I need to have a physical NIC or its pure vlan?
If you can, a link to creating vlan will be much appreciated.
I tried creating new vmkernal port but it was showing me there are no adapters.
actually I have noticed when I select vSwitch and click next, it does show the added vmkernal..
I have attached the screenshot..
am I doing it right?
So if I add a new VMKernal port on an existing vSwitch, will it work?
I guess I have to give a different subnet address for vmotion port which is different to Internal Network and ISCSI?
Thanks in advance and sorry for asking simple silly questions.
You have done it correctly - and if you notice under the settings of the vmkernel port you can assign a vlan id - you will also need to configure your physical switch to accept the vlan -
thanks again david.
Let me try that.
thanks for your help
Thank You very much David for your help.
I have managed to enable the vMotion.
I will try to migrate vmachine now..