8. Click
vSphere DRS
, and click
Fully automated
.
9. Move the threshold slider to the right and apply priority 1 and 2 recommendations, and click
OK
.
Next steps
Important:
After vCenter is back to normal operation, remove any snapshots that you took to preserve data.
Snapshots can adversely affect VM performance if left in place.
You must then configure HA/DRS.
Related links
Troubleshooting software issues
on page 34
Timeout error configuring High Availability in vCenter
Condition
A timeout might occur during the configuration of High Availability in VMware vCenter. An error
similar to the following appears in the
/var/log/fdm.log
file.
[ClusterManagerImpl::ConnectToMaster] Couldn't connect to master
N7Vmacore16TimeoutExceptionE(Operation timed out)
[ClusterManagerImpl::AddBadIP] IP 10.x.x.x marked bad for reason Unreachable IP
[ClusterElection::ChangeState] SlaveConnecting => Startup : SlaveConnectingStateFunc
[ClusterManagerImpl::IsBadIP] 10.x.x.x is bad ip
The following situations are observed as a result of the timeout:
• High Availability configuration fails.
• High Availability cannot be configured on a cluster.
• High Availability configuration completes on the master but fails on all slaves.
Cause
This issue occurs if Jumbo Frames are enabled on the host Management Network (the VMkernel
port used for host management) and the network configuration is not configured for jumbo frames.
This issue is resolved by ensuring that the vSwitch and Management Network MTU values are
configured to 1500.
Solution
1. Right-click the cluster host in vSphere Client.
2. Click the
Configuration
tab.
3. Click
Networking
.
4. Click
Properties
for the Management Network on vSwitch0 on Release 3.0 Pods and
vSwitch1 on pre-Release 3.0 Pods.
Timeout error configuring High Availability in vCenter
October 2017
Troubleshooting the Avaya Pod Fx
™
39