Loading

×Sorry to interrupt
Uncaught ReferenceError: addCTracking is not defined
throws at https://kb.vmware.com/resource/KM_TealiumTrackingJS?v=0.5:100:1

Refresh

Cookie Preference Center

General Information on cookies

When you visit our website, we use cookies to ensure that we give you the best experience. This information does not usually directly identify you, but it can give you a more personalized web experience. Because we respect your right to privacy, you can choose not to allow some types of cookies by clicking on the different category headings to find out more and change your settings. However, blocking some types of cookies may impact your experience on the site and the services we are able to offer. Further information can be found in our

Cookie Policy.

Strictly Necessary

Strictly Necessary

Always Active

Strictly Necessary

Strictly necessary cookies are always enabled since they are essential for our website to function. They enable core functionality such as security, network management, and website accessibility. You can set your browser to block or alert you about these cookies, but this may affect how the website functions. For more information please visit www.aboutcookies.org or www.allaboutcookies.org.

Cookie Details‎

Performance

Performance

Performance

Performance cookies are used to analyze the user experience to improve our website by collecting and reporting information on how you use it. They allow us to know which pages are the most and least popular, see how visitors move around the site, optimize our website and make it easier to navigate.

Cookie Details‎

Please confirm your settings by refreshing the page.

Functional

Functional

Functional

Functional cookies help us keep track of your past browsing choices so we can improve usability and customize your experience. These cookies enable the website to remember your preferred settings, language preferences, location and other customizable elements such as font or text size. If you do not allow these cookies, then some or all of these services may not function properly.

Cookie Details‎

Advertising

Advertising

Advertising

Advertising cookies are used to send you relevant advertising and promotional information. They may be set through our site by third parties to build a profile of your interests and show you relevant advertisements on other sites. These cookies do not directly store personal information, but their function is based on uniquely identifying your browser and internet device.

Cookie Details‎

Advertising Cookies

Consent Leg.Interest

Select All Vendors

Select All Vendors

Select All Hosts

Select All

Clear Filters

Information storage and access

Apply

Confirm My Choices Reject All Allow All

My Subscriptions

Loading

Knowledge Base

Recovered VMs fail to power on while performing a test failover to a cloud site in vCloud Availability (76105)

Last Updated: 11/19/2019Categories: TroubleshootingTotal Views: 3492Language:
English

Subscribe to get an email
newsletter with new updates

Please provide article feedback:

Symptoms

When performing a test failover to a cloud site using vCloud Availability, the recovered VM fails to power on.

When you try to manually power on the VM from the vCloud Director Tenant Portal, you see the error:

[aadf196e-f699-4335-9e46-76e3cd51f842] Unable to perform this action. Contact your cloud administrator.

In /opt/vmware/h4/cloud/log/cloud.log on the vApp Replication Manager, you see the following entry:

2019-11-07 03:00:58.495 DEBUG - [UI__626a9995-fa5b-4cb5-9770-50df8dbb39c8_Xw] [task-poller-5] com.vmware.h4.cloud.job.VmFailoverJob    : Failed to power on vapp.DebugInfo = com.vmware.ssdc.library.exceptions.GenericVimFaultException: Underlying system error:
Failed to start the virtual machine.
Module 'DevicePowerOn' power on failed.
Could not set up 'macAddress' for 'ethernet0'.
Invalid MAC address specified.
Impermissible static Ethernet address: '00:50:56:c2:d8:d7'. It conflicts with VMware reserved MACs.
vCenter Server task (moref: task-1665) failed in vCenter Server 'vc' (911c3c42-acaf-4921-8648-9eaf46bb06a2)., details = [ eb08a365-f27b-43ca-9b5f-402f852e31b0 ] Underlying system error: , taskId = urn:vcloud:task:bf07e07a-0f82-4d52-b250-41ba2e026948

Note: The preceding log excerpts are only examples. Date, time, and environmental variables may vary depending on your environment.

Cause

This issue occurs because the recovered VM is assigned a MAC address that is within the address range allocated for host VMkernel adapters on the underlying vCenter Server system.

Resolution

To resolve this issue, change the MAC address of the VM on failover:

Log into the vCloud Availability Portal for the target site.

In the left pane, under Incoming Replications, click from Cloud or from On-Prem depending on the source of the replication.

Select the protected VM and click the Networks button.

In the Migrate/Failover view of the Network Settings window, select Reset MAC.

Click on the Test Failover button.

In the Test Failover view, selet Reset MAC.

Click Apply.

Perform the test failover again and verify the recovered VM can be powered on.

Detectable by VMware SkylineTM

Actions

Copy

link to clipboard
copied!

Print

Language:
English

Attachments

Additional Resources

KB
•
VMware vSAN 仮想環境での IBM Spectrum Protect (76071)

KB
•
使用 vRealize Automation REST API 在重新配置实施后操作期间配置磁盘 (76069)

Results 1-2 of 2

Ask The Community

Get answers quickly from VMware experts in the community

Post Subject

CONTINUE IN COMMUNITIES

Related Products:

VMware vCloud Availability

Related Versions:

VMware vCloud Availability 3.0.x

Take Our Survey

Support Assistant