This post is more than 5 years old
1 Rookie
•
93 Posts
0
3573
July 21st, 2015 18:00
Configure phase was failed at ScaleIO 1.32 install
Hi,
We are building a ScvaleIO 1.32 system for the first time.
We uploaded " ScaleIO_Complete_Config.csv" file with [New Installation] using [Installation Manager] window, and executed [Start Installation].
Then, we encountered the following error at " install - configure phase".
*************
add protection domain command - domain1
Started: Fri Jul 17 14:59:33 UTC+0900 2015
Operating system: N/A
Command failed: Could not connect to 10.68.76.195,10.68.79.131.
Ensure that the relevant service is running and that the Installation Manager can communicate with the node
*************
Could you let us know the cause and solution of this error?
The error message says that: " Ensure that the relevant service is running and that the Installation Manager can communicate with the node".
However, we do not understand what is "relevant service".
What kind of services could be considered?
IP addresses "10.68.76.195" and "10.68.79.131" are set to "Primary" and "Secondary" respectively on MDM.
And, SDS and SDC are also installed on the same server.
We confirmed that "WMI service" had been started on the Installation Manager and respective nodes.
In addition, we checked that "Ping" command could be succeeded between the Installation Manager and respective nodes.
[Environment]
- Installation Manager
OS:Windows 2008 R2 x64
Conpornent:ScaleIO Gateway
- MDM primary
OS:Windows 2008 R2 x64
Compornent:SDS,SDC,MDM,Python
- MDM secondary
OS:Windows 2008 R2 x64
Compornent:SDS,SDC,MDM,Python
- TB
OS:Windows 2008 R2 x64
Compornent:SDS,SDC,TB
Thanks,
tomer__engineer
155 Posts
0
August 2nd, 2015 23:00
Good to hear. I think this issue can be closed.
SanjeevMalhotra
138 Posts
1
July 22nd, 2015 07:00
You had mentioned IP addresses "10.68.76.195" and "10.68.79.131" are set to "Primary" and "Secondary" respectively on MDM. However 10.68.76.195,10.68.79.131 are two IP addresses on different subnets. can you keep primary and Secondary MDM on the same subnet and check?
RafaelNovo
92 Posts
1
July 22nd, 2015 07:00
Please confirm that the MDM service is up and running and also that the respective ports are open at Windows Firewall
tomer__engineer
155 Posts
1
July 23rd, 2015 02:00
What this error means is:
1. You need to verify that WMI service is running on the Windows host (we use WMI for Windows and SSH for Linux).
2. That there's no firewall enabled that prevents the IM form communicating (and connecting) to that host
As for the IPs -> See attached example of correct CSV
1 Attachment
Multiple_IPs_mix_OS.csv.xls
yyoshida1
1 Rookie
•
93 Posts
0
July 23rd, 2015 17:00
Thank you for your comments.
As for the MDM up and running, we have already confirmed.
When the "Configure" phase is running, the status of MDM service on the server specified for the "Primary" is to be changed from "start" to "stop".
We are suspecting this cause the error at "Configure" phase.
The status of MDM service on the Secondary is remained in "start".
On the other hand, the MDM service on the Primary is to be stopped immediately even if it is started manually.
For the reason, we stopped the MDM service on the Secondary for the first, and then started the MDM service on the Primary. In this case, the status of MDM service "Start" on the Primary could be maintained.
After the above procedure, we retried the "Configure" phase, then confirmed the status became " All commands completed successfully".
Could you let us know why the MDM service stopped on the Primary?
yyoshida1
1 Rookie
•
93 Posts
0
July 23rd, 2015 17:00
Thank you for your comments.
When the "Configure" phase is running, the status of MDM service on the server specified for the "Primary" is to be changed from "start" to "stop".
We are suspecting this cause the error at "Configure" phase.
For the reason, we stopped the MDM service on the Secondary for the first, and then started the MDM service on the Primary. In this case, the status of MDM service "Start" on the Primary could be maintained.
After the above procedure, we retried the "Configure" phase, then confirmed the status became " All commands completed successfully".
[Question]
(1) Could you let us know why the MDM service stopped on the Primary?
(2) Could you explain us how this issue was relating to your comment below:
" However 10.68.76.195,10.68.79.131 are two IP addresses on different subnets."
yyoshida1
1 Rookie
•
93 Posts
0
July 23rd, 2015 18:00
In addition to my previous comments,
As for the respective ports are open at Windows Firewall,we have already confirmed.
yyoshida1
1 Rookie
•
93 Posts
0
July 23rd, 2015 19:00
Thank you for your comments.
We do not see any problem on the setting of firewall as noted below:
1. We verified that the "WMI service" were running on the Windows host.
2. We confirmed that there's no firewall enabled for respective ports could be opened on Windows.
On the CSV attached to your last email, there were some information relating to MDM's Primary and Secondary and TB.
The IP addresses were written in the CSV file in order of small ID number.
We are wondering why these IP addresses are necessary to be written in the CSV file in order of small ID number.
Could you make sure this point for us?
tomer__engineer
155 Posts
0
July 28th, 2015 00:00
I'm not sure I understand what you mean by "small ID number", do you mean lower case drive letters for Windows OS?
Also, in the example csv I sent I forgot to include mgmt network IP for the last 3 hosts, attached a corrected csv file
1 Attachment
Multiple_IPs_mix_OS.csv.xls
yyoshida1
1 Rookie
•
93 Posts
0
August 2nd, 2015 20:00
Thank you for your response.
Since the patch "KB3033929" required for Windows server where SDC was installed, was not applied, we performed the installation again after applying the patch.
All the phases were succeeded to complete.
It seems that this problem was caused by that the patch "KB3033929" was not applied.
This problem has been solved.
Thank you for your help.