Thought might be related to our newly upgrade 5.5, however seems a lot of people ran into same problem.
ERROR:
Migration to host <10.33.29.51> failed with error Already disconnected (195887150).
vMotion migration [169942327:1389120124781890] failed writing stream completion: Already disconnected
vMotion migration [169942327:1389120124781890] failed to flush stream buffer: Already disconnected
vMotion migration [169942327:1389120124781890] socket connected returned: Already disconnected
VMware KB found on problem:
http://kb.vmware.com/selfservice/microsites/search.do?language=en_US&cmd=displayKC&externalId=1030267
I tried all the regular fixes:
- vmkping to and from the vmkernel port used for vmotion
- verify DNS
- restart the management agent on host given error.
- /etc/init.d/hostd restart
- /etc/init.d/vpxa restart
- Verified time on the both hosts
- Turned off Enable Migration in the Advanced Settings of the host and re-enabled it.
- vSphere web client -> Manage tab -> Settings tab -> Advanced System Settings
- Search for "migration"
- Find Migrate.Enabled and set to 0(disabled)
- Unchecked vmotion on the vmkernel port and re-enabled it.
Still this did not resolve my problem.
RESOLUTION:
Change the IP address of the MVkernel adapter for vMotion traffic. This seems to fix the problem. I then also changed the IP back to original and problem was still resolved.
The vMotion VMkernel adpater IP address was previously used but not on this server since new server.
Fixed it for me- nothing decent in the logs, this was perfect!
ReplyDeleteFixed it for me- nothing decent in the logs, this was perfect!
ReplyDelete