can not test FT

gjedgewater · ‎07-12-2010

Hello,

I am unable to test fault tolerance the options are greyed out. I have esx 4 2u, with vSphere 4 2u as well. Fault tolerance starts and installes no issues, I can migrate VMs between any of the 3 hosts in the cluster. I can not test and if I restart a host with a FT Vm the VM shuts off. In the log for the vm I see this:

6: vcpu-0| Guest: vmx_fb: Driver compiled against: 2.0.

Jul 12 11:27:44.776: vcpu-0| Guest: vmx_fb: DrvGetDirectDrawInfo: Overlay flags set

Jul 12 11:27:45.169: vcpu-0| Migration pre-copy failed 0xbad010b

Jul 12 11:27:45.169: vcpu-0| MigrateSetStateFinished: type=1 new state=5

Jul 12 11:27:45.169: vcpu-0| MigrateStateUpdate: Transitioning from state 2 to 5.

Jul 12 11:27:45.170: vcpu-0| Migrate_SetFailure: switching to new log file.

Jul 12 11:27:45.172: vcpu-0| Migrate_SetFailure: Now in new log file.

Jul 12 11:27:45.177: vcpu-0| Migrate_SetFailure: The migration was cancelled because the amount of changing memory for the VM was greater than the available network bandwidth, meaning the migration was not making forward progress. Please attempt the migration again when the VM is not as busy or more network bandwidth is available.

Jul 12 11:27:45.251: vcpu-0| Migration of primary failed (creating secondary)

Jul 12 11:27:45.251: vcpu-0| Migrate: cleaning up migration state.

Jul 12 11:27:45.252: vcpu-0| MigrateStateUpdate: Transitioning from state 5 to 0.

Jul 12 11:27:45.252: vcpu-0| Msg_Post: Error

Jul 12 11:27:45.252: vcpu-0| http://msg.checkpoint.precopyfailure.noforwardprogress The migration was cancelled because the amount of changing memory for the VM was greater than the available network bandwidth, meaning the migration was not making forward progress. Please attempt the migration again when the VM is not as busy or more network bandwidth is available.

Jul 12 11:27:45.253: vcpu-0| -

Jul 12 11:27:45.257: vcpu-0| Migrate: secondary failure during migration: error Migration failed due to lack of pre-copy forward progress.

Thanks in advance! George

JaySMX · ‎07-12-2010

How is your FT Logging connection configured and what speed is the link?

-Justin, VCP3/4, MCSE

-Justin

gjedgewater · ‎07-12-2010

Hello Justin,

vmkping works to anyof the hosts from any host of the 3 hosts in the cluster....

This is from esx.conf:

/net/vmkernelnic/child[0009]/ipv4address = "10.10.12.30"

/net/vmkernelnic/child[0009]/ipv4broadcast = "10.10.12.255"

/net/vmkernelnic/child[0009]/ipv4netmask = "255.255.255.0"

/net/vmkernelnic/child[0009]/mac = "00:50:56:7d:f6:10"

/net/vmkernelnic/child[0009]/mtu = "9000"

/net/vmkernelnic/child[0009]/name = "vmk1"

/net/vmkernelnic/child[0009]/portgroup = "FaultTolerant"

/net/vmkernelnic/child[0009]/routAdv = "false"

/net/vmkernelnic/child[0009]/tsoMss = "0"

Networking in vSphere:

Both the vswitch and the vkernal are the same:

vlan = 601

load balance = route based on ip hash

network failover = link status only

modify switches = yes

failback = yes

override svswitch failover order (checked)

vmnic2 and vmnic3 active 1000full

The vSwitch vmknic and the ports on the switch are all configured for jumbo frames.

Excerpt from the dell switch:

interface ethernet 1/g17

channel-group 4 mode on

description 'ESX1-NIC2-FT'

spanning-tree disable

mtu 9216

switchport mode general

switchport general pvid 601

switchport general acceptable-frame-type tagged-only

switchport general allowed vlan add 601 tagged

Channel group:

interface port-channel 4

description 'ESX1-FT'