SRM (5.5)Test failover fail to power on Multiple machines

Issue:
SRM (5.5)Test fail-over fail to power on Multiple machines withSRM Test failover fail to power on Multiple machines with Error - Timed out waiting for VMware Tools after 300 seconds Operation timed out: 900 seconds Timed out waiting for VMware Tools after 300 seconds Operation timed out: 1200 seconds Operation timed out: 1200 seconds ,
Note:Virtual machines have updated VMware tools, ESXi host (Protected and Recovery site) are running on same build version.

Solution:
Here since the vmware tools wait for the heartbeat from VM (guest OS needs to load and send heartbeat) so avoid this over all you can also uncheck below option , so the vmwaretools wouldn't wait for this and loads successfully .


  Right-click virtual machine in the recovery plan and select Configure.
                        
                                  Go to Startup Action > Power On > Wait for VMware tools.

 Or As a recommendation the only option to come out of this is to increase the time out value, however it has been confirmed that this behaviour is only during test fail over , and actual fail over works fine even if doesn't meet any specific parameter .

Steps to Change the time out value :
 
  Right-click virtual machine in the recovery plan and select Configure.
                        
                                  Go to Startup Action > Power On > Wait for VMware tools.
                        
                                  Change from the default value of 5 minutes to 15 minutes.

Comments

Post a Comment

Popular posts from this blog

Avamar falied to take backup of all virtual machine

Recently I encountered an issue where Avamar failed to take backup. Logs stating  insufficient Permission in the host OS 2018-02-19 06:59:56 avvcbimage Error <0000>: [IMG0008] Failed to connect to virtual disk [VMAXDS] VM/VM-000002.vmdk (3014) (3014) Insufficient permissions in the host operating system (Log #2)  We verified the permission on the vCenter but no luck,However on demand backup from local Account is with same level of access is successful. While investigation further we found that there are errors related to DNS, and even some DNS server are getting backed up via avamar. We asked to remove DNS from Avamar back considering VM stun operation during the backup but it did not help to resolve the issue. Later on we found that DNS server which is hardcoded in Avamar was decommission due which Domain ID's were unable to run backup on vCenter
Read more

How to Configure IPsec VPN within VMware NSX Edge

Image
This article shows you how to create an IPsec VPN between a NSX Edge Gateway with a vCloud Director/NSX Manager and a remote Client site. First you need basic details from client so that you can configure IPSec VPN from your end.Like you need Phase 1 and Phase 2 Details. (This document related to NSX Edge 6.3.2) Image Credit VMware Note: NSX Edge supports Main Mode for Phase 1 and Quick Mode for Phase 2. Phase 1 Parameters Phase 1 sets up mutual authentication of the peers, negotiates cryptographic parameters, and creates session keys. The Phase 1 parameters used by NSX Edge are: Main mode TripleDES / AES [Configurable] SHA-1 MODP group 2 (1024 bits) pre-shared secret [Configurable] SA lifetime of 28800 seconds (eight hours) with no kbytes rekeying ISAKMP aggressive mode disabled In 6.3.2 you Can see basic details or you can say this is mixed mode like Phase 1 and Phase 2 they don’t have different tabs or options. Here are details which you have to ...
Read more

Deploy a 2-node vSAN cluster

Image
A 2-node hyperconverged cluster is useful in branch office where you need high availability or for small infrastructure. With 2-node hyperconverged solution, you don’t need to leverage a NAS or a SAN for the shared storage. So, the hardware footprint is reduced and the manageability is improved because hyperconverged solution are easier to use than standard infrastructure with SAN. VMware provides a Software-Defined Storage solution called vSAN. vSAN can be deployed from 2 nodes to 16 nodes. 2-node cluster should be used for ROBO (Remote Office and Branch Office). A 2-node cluster requires a Witness Appliance provided by VMware freely while the appliance is virtual. The Witness Appliance is based on ESXi. This is the first time that VMware supports a scenario in production with a nested ESXi. This topic describes how to deploy a 2-node vSAN cluster and its witness appliance. Why you need a witness appliance vSAN is something like a RAID over the network. vSAN curre...
Read more