"Operation Timed out" error while configuring HA in vCenter Server
•Download as PPTX, PDF•
1 like•2,364 views
This issue occurs when Jumbo Frames is enabled on the host Management Network (VMkernel port used for host management) and a network misconfiguration prevent hosts communicating using jumbo frames. It is supported to use jumbo frames on the Management Network as long as the MTU values and physical network are set correctly. These slides explains how to resolve this issue in few steps.
![Symptoms
Configuring HA fails
Completes on the HA master, but fails on all HA slaves
You see the error:
Operation Timed out
In the /var/log/fdm.log file, you see entries similar to:
[ClusterManagerImpl::ConnectToMaster] Couldn't connect to master
N7Vmacore16TimeoutExceptionE(Operation timed out)
[ClusterManagerImpl::AddBadIP] IP <x.x.x.x> marked bad for reason Unreachable IP
[ClusterElection::ChangeState] SlaveConnecting => Startup :
SlaveConnectingStateFunc
[ClusterManagerImpl::IsBadIP] <x.x.x.x> is bad ip](data:image/gif;base64,R0lGODlhAQABAIAAAAAAAP///yH5BAEAAAAALAAAAAABAAEAAAIBRAA7)
Recommended
More Related Content
What's hot
What's hot (13)
Viewers also liked
Similar to "Operation Timed out" error while configuring HA in vCenter Server
Similar to "Operation Timed out" error while configuring HA in vCenter Server (20)
Recently uploaded
Recently uploaded (20)
"Operation Timed out" error while configuring HA in vCenter Server
- 1. © 2014 VMware Inc. All rights reserved. "Operation Timed out" error while configuring HA in vCenter Server
- 2. Symptoms Configuring HA fails Completes on the HA master, but fails on all HA slaves You see the error: Operation Timed out In the /var/log/fdm.log file, you see entries similar to: [ClusterManagerImpl::ConnectToMaster] Couldn't connect to master N7Vmacore16TimeoutExceptionE(Operation timed out) [ClusterManagerImpl::AddBadIP] IP <x.x.x.x> marked bad for reason Unreachable IP [ClusterElection::ChangeState] SlaveConnecting => Startup : SlaveConnectingStateFunc [ClusterManagerImpl::IsBadIP] <x.x.x.x> is bad ip
- 3. Why it happens? This issue occurs when Jumbo Frames is enabled on the host Management Network (VMkernel port used for host management) and a network misconfiguration prevent hosts communicating using jumbo frames. It is supported to use jumbo frames on the Management Network as long as the MTU values and physical network are set correctly.
- 4. Resolution To resolve this issue, ensure that the network supports jumbo frames end-to-end. This should be verified by the local networking team. To check the current MTU values set on the vSwitch and VMkernel network interface: • In the vSphere Client, right-click the host in the cluster and then click the Configuration tab. • Click Networking. • Click Properties for Management Network on vSwitch0. • Under the Ports tab, click vSwitch and then click Edit. • Ensure that the MTU value is set to 9000 and not 1500 and then click OK. • Repeat this process for the Management Network under the Ports tab, click Management Network and then click Edit. • Ensure that the MTU value is set to 9000 and not 1500 and then click OK. • Click OK. • Repeat this process for all hosts in the cluster. • Right-click the cluster and reconfigure HA.