Deploy ScaleIO Environment Fails In VMware vCenter

Question

I am trying to setup ScaleIO 1.3.2 in my home lab for testing. I have a vCenter 5.5 virtual appliance and 3 ESXi 5.5 Hosts. I have successful installed the web plugin in vCenter and I have successfully gone through the install SDC on ESX process. I run into errors when I try to deploy ScaleIO enviroment through the vCenter plugin. I get the following error messages in the logs (read below). Also, as a side note these errors occur early in the process after only 3 of 39 tasks. I have also tried this process several times after two full reboots of the ESXi hosts and vCenter Server. Does anyone know what is causing these errors? Thank you for your help. Aug 6, 2015 5:36:20 AM Host: 192.168.125.132 - STARTED: Deploy SVM [Mgmt IP: 192.168.125.73, data IP 1: 20.20.20.23, data IP 2: null, VM id: null, mgmt subnet mask: 255.255.255.0, data subnet mask 1: 255.255.255.0, data subnet mask 2: null, default gateway: 192.168.125.1, datastore: ESX2Store1, memory size: 1704] Aug 6, 2015 5:36:20 AM Host: 192.168.125.126 - STARTED: Deploy SVM [Mgmt IP: 192.168.125.72, data IP 1: 20.20.20.22, data IP 2: null, VM id: null, mgmt subnet mask: 255.255.255.0, data subnet mask 1: 255.255.255.0, data subnet mask 2: null, default gateway: 192.168.125.1, datastore: ESX1Store1, memory size: 1704] Aug 6, 2015 5:36:20 AM Host: 192.168.125.133 - STARTED: Deploy SVM [Mgmt IP: 192.168.125.74, data IP 1: 20.20.20.24, data IP 2: null, VM id: null, mgmt subnet mask: 255.255.255.0, data subnet mask 1: 255.255.255.0, data subnet mask 2: null, default gateway: 192.168.125.1, datastore: ESX3Store1, memory size: 1704] Aug 6, 2015 5:47:42 AM Host: 192.168.125.132 - FAILED (Error code: VMWARE_CANNOT_RETRIEVE_VM_MOR_ID, Error details: Retrieved VM is null) : Deploy SVM [Mgmt IP: 192.168.125.73, data IP 1: 20.20.20.23, data IP 2: null, VM id: null, mgmt subnet mask: 255.255.255.0, data subnet mask 1: 255.255.255.0, data subnet mask 2: null, default gateway: 192.168.125.1, datastore: ESX2Store1, memory size: 1704] Aug 6, 2015 5:47:45 AM Host: 192.168.125.126 - FAILED (Error code: VMWARE_CANNOT_RETRIEVE_VM_MOR_ID, Error details: Retrieved VM is null) : Deploy SVM [Mgmt IP: 192.168.125.72, data IP 1: 20.20.20.22, data IP 2: null, VM id: null, mgmt subnet mask: 255.255.255.0, data subnet mask 1: 255.255.255.0, data subnet mask 2: null, default gateway: 192.168.125.1, datastore: ESX1Store1, memory size: 1704] Aug 6, 2015 5:47:49 AM Host: 192.168.125.133 - FAILED (Error code: VMWARE_CANNOT_RETRIEVE_VM_MOR_ID, Error details: Retrieved VM is null) : Deploy SVM [Mgmt IP: 192.168.125.74, data IP 1: 20.20.20.24, data IP 2: null, VM id: null, mgmt subnet mask: 255.255.255.0, data subnet mask 1: 255.255.255.0, data subnet mask 2: null, default gateway: 192.168.125.1, datastore: ESX3Store1, memory size: 1704]

tomer__engineer · Accepted Answer

VM MOR ID is needed as a unique identifier in VMware for the ScaleIO VMs (SVMs). vSphere client tries to get the VM MOR ID from the VC DB (multiple attempts). If it takes a long time for the VM to come up and for the VC DB to be updated, you may come across this problem.

VC (and ESX) do not know the SVMs IP while they are down. Please check if the SVMs are up and if you can see in vSphere client their configured IPs.

Please send us the full logs.

VC 5.5

Windows:

Virgo logs: C:\ProgramData\VMware\vSphere Web Client\serviceability\logs

Plugin logs and other files: C:\Windows\System32\config\systemprofile\AppData\Roaming\VMware\scaleio

Plugin location C:\ProgramData\VMware\vSphere Web Client\vc-packages\vsphere-client-serenity

Linux:

Virgo logs: /var/log/vmware/vsphere-client/

Plugin logs and other files: /opt/.vmware/scaleio

Plugin location /var/lib/vmware/vsphere-client/vc-packages/vsphere-client-serenity/

VC 6.0

Windows:

Virgo logs: C:\ProgramData\VMWare\vCenterServer\logs\vsphere-client\logs

Plugin logs and other files: C:\Users\vspherewebclientsvc\AppData\Roaming\VMware\scaleio

Plugin location C:\ProgramData\VMware\vCenterServer\cfg\vsphere-client\vc-packages\vsphere client-serenity

Linux:

Virgo logs: /var/log/vmware/vsphere-client/logs

Plugin logs and other files: /etc/vmware/vsphere-client/vc-packages/scaleio

Plugin location: /etc/vmware/vsphere-client/vc-packages/vsphere-client-serenity

Serhad Ali Turhan · Answer

Hello all, I couldn't understand the solution here. What should I do to speed up the deployment process in order not to see VM MOR ID error? Thanks,

daverush · Answer

saturhan,

You may need to assess the speed of the disks the datastore is built on.

The SVM deployment from a template is no different than any other template->VM deployment in terms of speed.

I recommend consulting the VMware Community for expertise on the matter.

PowerFlex

Was this post helpful?