Neverfail Continuity Engine Secondary server deployment hangs at: Waiting for Secondary VM to complete auto configuration...

Neverfail Continuity Engine Secondary server deployment hangs at: Waiting for Secondary VM to complete auto configuration...

Summary

This Knowledgebase article provides details and a workaround procedure for the situation where Secondary server deployment hangs at Waiting for Secondary VM to complete auto configuration... step and eventually, the Secondary VM deployment operation times-out.

 

More information

Primary's VM MAC address was configured as Manual (not as recommended, default Automatic). As a consequence, the cloned Secondary had the same manual MAC address. This causes the post-clone Secondary auto-configuration task to fail.

 

Procedure

Symptom

  • Secondary server deployment hangs at Waiting for Secondary VM to complete auto configuration... step and eventually operation times-out.
  • EMS logs contain following events:

[2017-12-20 08:35:09,653] INFO  7706[TaskExecutor](com.neverfail.webservices.install.config.FirstStartWindowsConfigurationSequencer) - FirstStartWindowsConfigurationSequencer> Found inconsistent MAC addresses, aborting reconfiguration.
[2017-12-20 08:35:09,653] INFO  7706[TaskExecutor](com.neverfail.webservices.install.config.FirstStartWindowsConfigurationSequencer) - FirstStartWindowsConfigurationSequencer> isSourceServer() currentIdentity=PRIMARY, targetIdentity=PRIMARY

Cause

Primary VM's network adapters are configured with Manual MAC Addresses prior of cloning the Secondary VM out of it. As a consequence, the cloned Secondary VM's network adapters have the same MAC addresses as those configured on Primary VM. And this causes Secondary VM auto-configuration to fail.

Workaround

  1. Shutdown Secondary server
  2. Reconfigure the Secondary VM Network Adapter(s) with Automatic MAC Address
  3. Restart Secondary Server => VM will be automatically reconfigured with a new MAC address, hence the reconfiguration task will be automatically started and server will be correctly configured as Secondary/Passive

Note: it is recommended to reconfigure the Primary VM also with Automatic MAC address     

 

Applies To

Neverfail Continuity Engine v8.1 or newer installations where the following are true:

  • Primary target is a VMware VM
  • Cloning or Recloning operations are done using the configured vCenter Server

   

KBID-3024

    • Related Articles

    • Neverfail Continuity Engine v8.5 - Release Notes

      Summary This Knowledge base article provides information about the 8.5 release of Neverfail Continuity Engine and all subsequent updates to this release. Neverfail Continuity Engine v8.5 Update 7 The following information applies to ...
    • Neverfail Continuity Engine v8.0 Automated Deployment of Stand-by Servers with Automatic Cloning

      Summary This Knowledgebase article provides the procedure used for Automated Deployment of Stand-by Servers with Automatic Cloning when the Secondary server is physical or virtual.  More Information Procedure  You have the following options: If the ...
    • Continuity Engine Troubleshooting - Synchronization Failures

      Neverfail Continuity Engine provides protection to your applications by replicating data to a passive server. Continuity Engine attempts to synchronize protected data on all servers and continually replicates changes to that data. This article ...
    • Continuity Engine Product Architecture

      Learning objectives At the completion of this session you should be able to: Identify major components of the Neverfail Continuity Engine product architecture. Describe major component configuration. Identify advantages of the Neverfail Continuity ...
    • Neverfail IT Continuity Engine v7.1.2 - Release Notes

      Summary This Knowledgebase article provides information about this specific release of Neverfail IT Continuity Engine v7.1.2 Overview This release of Neverfail IT Continuity Engine is a patch release that applies to Neverfail IT Continuity Engine ...