Hi experts,
i m using esx 3.5 update 4 environment with 5 ESX server (IBm 3650 with Broadcom nic). problem is that when i migrate ome machine from one server to other server they stop responding . means migration is complete but they are not pingable from network. this is very critical.
Make sure that the both server's networks are configured the same way - in other words that the virtual switch the vm connects to on the other host an get to the same network segment it was connected to on the originating host
If you find this or any other answer useful please consider awarding points by marking the answer correct or helpful
Be also sure that the network label is the same on both ESX.
Check in VM / Properties after you have moved the VM to see if you loose the label.
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
Thanks for reply.
Everything is same on all server as far as network setting /labels are concerned
asuming you are talking about the service console IP address you need to use
esxcfg-vswif
check
vi/etc/sysconfig/network
GATEWAY=<new gateway ip>
then run this
service network restart
that should be it!
Principle System Engineer
NetSol Technologies
Lahore Cantt Pakistan
54792
Do you have other VM on destination ESX that are working on the same network? Their network connectivity is fine?
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
Yes Andre ,
Virtual machine network part wors fine until i do vmotion.
proces is that last day we do some maintenance with one of the server ragarding ram upgradtion. for that i put that server under Maintenance mode ..all machine randomely moves to another server but when hey moved they vstart unresponding .
Ravinder
Virtual machine network part wors fine until i do vmotion.
But works fine on both ESX?
Could be a problem at physical switch level (maybe STP). Do you have a single core switch?
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
I have One core switch attached to all esx server.
Have you enabled RSPT or Fast SPT?
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
Is that stp or spt
spanning tree protocol
spanning tree protocol
Yes, STP.
Enable the Rapid or the Fast version.
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
Is there any Relation between thease two (Migration ,vmotion and STP)
because before 1 month everything with same conf running fine.
Ravinder
Is there any Relation between thease two (Migration ,vmotion and STP)
Yes.
because before 1 month everything with same conf running fine.
What is changed in the last month?
You say memory, but if VM works fine memory is not the problem.
If you do a cold migration the VM will work?
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
We hav'nt tried with cold migration .but why it is commming
and wha are the possible cause so we can try some trouble shooting.
If you are sure that virtual networking is working on all ESX, and is configured in the same way an all ESX, and NIC are working fine...
...then a possible cause is that physical switch can understand the network change during VMotion (arp table must change inside switch).
Andre
**if you found this or any other answer useful please consider allocating points for helpful or correct answers
Hi
Which type of switch do you have? If you have a Cisco switch, check Port-Security on the Ports. We had the same problem. We deactivated Port-Security and bingo, problem was resolved.
Greez
Patrick