Resolving the issue where newly created virtual machines appears as unprotected in vCenter

7
© 2014 VMware Inc. All rights reserved. Newly created virtual machines appears as unprotected in vCenter

Transcript of Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Page 1: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

© 2014 VMware Inc. All rights reserved.

Newly created virtual machines appears as unprotected in vCenter

Page 2: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Symptoms vCenter reports "unknown error initializing HA" for the host, but the Fault Default

Manager log shows that the host successfully becomes an HA master or slave node. Enabling HA times out in vCenter, but is successful on host(s).Re-configuring vsphere HA task

fails on "Timed out Exception" in vCenter, but Fault Default Manager log shows that the host successfully becomes an HA master or slave node.

Newly powered on virtual machine shows as unprotected by HA in vCenter,but the Fault Default Manager log shows that the virtual machine is protected.

vCenter and ESXi hosts are not in the same subnet, there is a gateway/ firewall between vCenter and ESXi hosts.

Disabling and re-enabling HA on the cluster will resolve the issue temporarily, but issue will re-occur.

Page 3: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Why it happens?

This issue occurs when there is a

firewall in the environment that is

dropping the HA traffic between the

ESXi hosts and vCenter Server.

Page 4: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Resolution

To resolve this issue:

1. Change "vpxd.das.fdmWaitForUpdatesTimeoutSec" settings to smaller value until the issue never shows. E.g. 30 or 60.Note:This option is available from 5.5 u3.

a) In the vSphere Web Client, navigate to the vCenter Server instance.  b) Select the Manage tab.  c) Select Advanced settings. d) Click Edit. e) In the Key, type a key. f) In the Value field,type the value for the specified key. g) Click Add. h) Click OK.

Page 5: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Resolution 2. Change firewall settings,enlarge relevant "connection timeout" settings, consult device vendor for specific steps.

For example  Timeout:10800

a) TCP Timeout:10800

b) TCP Half Closed360

c) TCP Time Wait 120

Page 6: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Resolution 3. Restart HA on the cluster.   Browse to the cluster in the vSphere Web Client object navigator.

a) Click the Manage tab and click Settings.

b) Under Services, click Edit.

c) Uncheck the Turn ON vSphere HA.

d) Click OK.

e) Click Settings again and select Turn ON vSphere HA.

f) Click OK.

Page 7: Resolving the issue where newly created virtual machines appears as unprotected in vCenter

Resolution 4. Reconfigure HA on host level.

a) In the vSphere Web Client select the ESXi host.  b) Right click the ESXi host. c) Select All vCenter Actions > Reconfigure for vSphere HA.

5. Move vCenter and ESXi hosts to the same subnet.