- This topic has 1 reply, 2 voices, and was last updated October 25, 2016 by Joshua S.
FailoverTest doesnt work in VM with Standard Port
You must be logged in to create new topics.
Click here to login
Hello all,
I need to know if someone had the same problem like me.
When I try to do a FailoverTest on a VM with standard port group, and the target network in a vDC is Distributed port group, it fails with this [ERROR], and VM is created in poweroff state.
[ERROR]Task: Power Off virtual machine
info
03/06/2016 9:45:38
Power Off virtual machine
Virtual machine on esx211.ti.local is powered on
info
03/06/2016 9:45:25
Power On virtual machine
Resource allocation changed
…
Virtual machine is starting
info
03/06/2016 9:45:24
Power On virtual machine
Task: Power On virtual machine
info
03/06/2016 9:45:24
Power On virtual machine
Reconfigured virtual machine
info
03/06/2016 9:45:23
Reconfigure virtual machine
Task: Reconfigure virtual machine
info
03/06/2016 9:45:21
Changed custom field system.service.vmware.vsla.vCloudGTD to vCloudGTD
info
03/06/2016 9:45:20
Reconfigured virtual machine
info
03/06/2016 9:45:12
Reconfigure virtual machine
Task: Reconfigure virtual machine
info
03/06/2016 9:45:11
Reconfigure virtual machine
Completed the relocation of the virtual machine
info
03/06/2016 9:44:37
Migrate virtual machine
Relocating from esx225.ti.local, CML-Lidic001-Clientes-Vcloud14 to esx211.ti.local, CML-Lidic001-Clientes-Vcloud14
info
03/06/2016 9:44:35
Migrate virtual machine
Migration from esx225.ti.local to esx211.ti.local and resource pool SRVTI_DRaaS_Zerto_VDCo (aa8e8f26-695c-4b0a-83f0-d305326129ed):
Network interface ‘Network adapter 1’ uses network ‘none’, which is not accessible.
warning***
03/06/2016 9:44:35
Migrate virtual machine
Task: Migrate virtual machine
info
03/06/2016 9:44:34
Migrate virtual machine
***(in bold the unique warning alert)
Any idea? anyone could create a test in other vCenter? I have try in 2 vCenter, with the same behavior.
[INFO: vCenter source 6.0 vCenter target with vCloud 5.5]Thanks!
Hey Matias,
I noticed nobody replied to your post. Did you raise a support ticket on this? It looks to be an issue with your environment as there should be no issue with Zerto connecting a VM to standard port group, this is relatively simple. Thanks,
JOshua