I'm attempting to deploy ScaleIO 2.0.0.2 on vSphere 6.0u2 and keep getting this error when attempting to deploy. I have reviewed this post for network validation. Deploy Scale IO error Configure SDC driver on ESX
I'm able to ping the SVM data IP from the ESXi data vmk. Same with the management vmk to the management IP of the SVM. Re-registered the plugin and rebooted hosts a number of times. Can somebody help me understand the exact traffic flow involved with this error?
Failed: Configure SDC driver on ESX (The SDC cannot communicate with the MDM cluster. Verify vmkernel and/or portgroup settings. )
Are there options for getting a bit more logging detail? I looked at doing this step with scli and found that the scini parameters are already configured with the primary & secondary MDM IP addresses which are correct. Any other suggestions for resolving this issue?
Unfortunately the logs in the virtual center wizzard are lacking. Ideally it would give out some details of service port and IPs involved in the communication. Here are some additional logs but they seem to just list more errors related to the initial one I posted.
node 1
Completed: Deploy VM ScaleIO-10.0.0.42
Completed: Deploy VM ScaleIO-10.0.0.41-GW
Completed: Perform initial configuration for VM: 10.0.0.42
Completed: Perform initial configuration for VM: 10.0.0.41
I am wondering if you are not experiencing the problem described under SCI-12873 in the ScaleIO Release Notes... it isn't a 5 node cluster from what I see, but I guess it's still worth a shot - can you simply please try to click on Continue Deployment and see if that helps?
Clicking continue just results in the exact same errors. Really just looking for some insight into exactly what the script is doing at the point of the error?
I have reviewed these logs. Seeing an sso issue on vcenter and just more generic failures from the SDC configuration tasks. Will look at some solutions from VMware on sso issue but I suspect that is separate from the failures at this point.
trodemaster
5 Posts
2387
1
Posted October 26th, 2016 14:00
OK I have resolved this issue. As it turns out the virtual center SSO bug was preventing the needed communication. The error itslef is discussed in this vmware thread. Exception thrown by SsoUtil: SSO admin service ... | VMware Communities
This issue can show up in vCenter 6.0u1 and u1. The fix will come out in the next patch for vCenter server.
As an immediate workaround you can reboot the psc or vcenter and immediately re-run the failed tasks.