Solved!
Go to SolutionR
RussFellows
1 Rookie
•
4 Posts
1
3478
May 15th, 2016 19:00
ScaleIO 2.0 Install errors
Following 2.0 Install guide, and running into issues on page 6, "Registering the plug-in"
From a Windows 8.1 host with the latest version of VMware PowerCLI installed (version 6.3), running as Administrator:
———————————————————————
PowerCLI C:\TMP> .\ScaleIOPluginSetup-2.0-5014.0.ps1
cmdlet ScaleIOPluginSetup-2.0-5014.0.ps1 at command pipeline position 1
Supply values for the following parameters:
(Type !? for Help.)
vCenter: win-gu0ugqsk9mv.egi1.vdi.local
Username: Administrator@vsphere.local
Password: *********
Adjusting vCenter ipv6 address : [win-gu0ugqsk9mv.egi1.vdi.local]
Choose mode:
1 - Register ScaleIO plug-in
2 - Unregister ScaleIO plug-in
3 - Create SVM template
4 - Exit the script
: 1
Welcome to ScaleIO Plugin Register Utility
Important notice to users upgrading to ScaleIO release 1.32, or higher:
1. ESXi 5.1 is no longer supported. ESXi 5.5 and above are supported.
2. Running SDC within an SVM is no longer supported. SDC must be installed in the ESXi host.
If your configuration isn't supported, DO NOT UPGRADE.
Contact Support for additional info and further assistance.
Do you wish to continue? Y / N: y
Do you want to run the Standard or Advanced registration? [s|a]: s
Enter your local IP address. The vCenter will attempt to connect to that IP and will fail if it is inaccessible.: 172.16
.1.84
verify protocol url : https://172.16.1.84:65101/resources/plugin
Waiting for internal server to load (attempt 1)...
Attempt 1 failed. The error was 'Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote
server"'.
Waiting for internal server to load (attempt 2)...
Attempt 2 failed. The error was 'Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote
server"'.
Waiting for internal server to load (attempt 3)...
Attempt 3 failed. The error was 'Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote
server"'.
Waiting for internal server to load (attempt 4)...
Attempt 4 failed. The error was 'Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote
server"'.
Waiting for internal server to load (attempt 5)...
Attempt 5 failed. The error was 'Exception calling "GetResponse" with "0" argument(s): "Unable to connect to the remote
server"'.
WARNING: Failed retrieving thumbprint from the server (https://172.16.1.84:65101/resources/plugin)
Enter the https server's thumbprint: xx:xx:xx:xx:xx:-------
Connecting to vCenter [win-gu0ugqsk9mv.egi1.vdi.local]...
Cannot connect to the vCenter. Run the script again. If the problem continue, reopen PowerCLI.
ERROR: The process with PID 14584 could not be terminated.
Reason: There is no running instance of the task.
———————————————————————
Note: I changed the thumbprint above from the actual value.
So yes, it appears that the IP address of the vCenter server is not accessible on port 65101, which is correct. I cannot connect to my vCenter server on that port. No, there is no firewall on that system, so the question is what service is supposed to be running on that port?
There is nothing in the install that I saw that shows anything about running a service on vCenter prior to installation.
Thoughts, help???
Hi,
Can you please clarify whether 172.16.1.84 is the IP address of the vCenter server, or the Windows box you are running the plugin from? Or are you running the plugin from the vCenter server itself?
Sometimes the plugin isn't working great when it's running on the vCenter host - one of the fastest workaround is to manually deploy an SVM, install the IM Gateway manually (rpm -i, the installation packages are under "install" folder in /root directory of the SVM) and use Advanced installation - then point the plugin to the freshly installed Gateway, rather than to the Windows host where you are running the plugin from - in 95% of cases this trick allows you to register the plugin quickly and flawlessly,without need to debug Windows services (which can be painful).
Let me know if that worked for you!
Best,
Pawel
RussFellows
1 Rookie
•
4 Posts
1525
2
Posted May 17th, 2016 08:00
Thanks for the pointers.
The IP address questions were confusing, because I've never had a program ask for the IP of the system I am on. I tried multiple combinations, and the IP in the example was actually that of the vCenter server. Using the IP of the system I was on produced a different set of errors.
I did find a solution. The problem turned out to be that the FQDN does not work in your PowerShell script, even though I can ping the FQDN with no problems. That is "ping xxx.a.b" where xxx is the hostname and a.b is domain works fine from the powershell command line. BUT, it does not work in your script.
So the solution was to use the IP address instead of the FQDN, and then everything worked. Seems like a bug somewhere in the script, or at the very least room for enhancements.
Thanks.