Difference between revisions of "VCP4"

VCP4 (view source)

1,268 bytes added , 14:17, 27 November 2009

m

2,187

edits

@@ Line 436: / Line 436: @@
 == Perform Basic Troubleshooting for VMware FT and Third-Party Clusters ==
+'''Unexpected FT Failovers'''
+* Partial Hardware Failure Related to Storage - Caused by one ESX experiencing problems accessing VM's storage
+* Partial Hardware Failure Related to Network - Caused by FT logging NIC being congested or down
+* Insufficient Bandwidth on the Logging NIC Network - Caused by too many FT VM's on the same ESX
+* VMotion Failures Due to Virtual Machine Activity Level - VM is too active for VMotion to succeed
+* Too Much Activity on VMFS Volume Can Lead to Virtual Machine Failovers - Too many file system locking operations (VM power on/off's etc)
+* Lack of File System Space Prevents Secondary VM Startup
+'''Other FT Errors'''
+* Hardware Virtualization Must Be Enabled - HV (ie VT/AMD-V) must be enabled to allow FT
+* Compatible Secondary Hosts Must Be Available - No spare ESX's with HV, capacity, not in Maintenance mode etc
+* Very Large Virtual Machines Can Prevent Use of Fault Tolerance - If memory is large (>15GB) or changing too much, VMotion will not be able to keep in sync, can increase time-out value (def 8 sec -> 30 secs) <code> ft.maxSwitchoverSeconds = "30" </code> entered in VM's VMX file
+* Secondary VM CPU Usage Appears Excessive - Replaying some events can be more expensive than recording on Primary, normal operation
 == Perform Basic Troubleshooting for Networking ==
 == Perform Basic Troubleshooting for Storage ==