This should have been done prior to installing the MDM/SDS backend. The plugin shouldn't let you continue until the SDC is installed.
Either way, go to your ScaleIO plugin on the vsphere web client. There will be a link for installing the SDC on the landing page there.
If you can't install it that way, you can do it manually. You downloaded it with the other ScaleIO software. Find the vib that is appropriate for your platform (5.5 or 6), copy it to your host and install it like any other vib on an ESXi host. Reboot the host after the initial install.
Can you please try to SSH into the deployed SVMs and try to ping all 3 IPs (management+data) in each direction? Please don't run ping from the ESXi, rather from the SVMs and paste the outputs here.
In a case like this,being able to ping is a good start. However, the key here is that it succeeds when creating the Master MDM, as it is still using SSH (port 22) to do the work. When the Master MDM is then up and running, the two ports that the MDM uses, 9011 and 6611, will be taking over for adding all other components (Slave MDMs and SDSes) and SSH is no longer the main communication component here.
Verify that the two ports listed above are open in the firewall as that is most likely the cause of failure here. Also verify that the MTU size on all components is set to the same size, both on the SVM side and the VMware vswitch side. Less likely but still need to check... SSH to the Slave MDM SVM and make sure that the MDM process is up and running.
As per the above i have open both the port but i can't able to ping primary data link ip to secondery datalink ip and try to check MDM server with service mdm status command but no service is running like this am deploying VMware scaleio deployment
According to your own update, you are not able to ping between primary and secondary MDMs. I assume that is what you meant by "i can't able to ping primary data link ip to secondery datalink ip".
Can you ping the following:
10.20.30.14 <--> 10.20.30.15
10.20.70.13<--> 10.20.70.14
To check if the mdm service is running, just type in "ps -ef |grep mdm". If it isn't running, type in "/opt/emc/scaleio/mdm/bin/create_service.sh", and check again.
You can also look at the /opt/emc/scaleio/mdm/logs/trc.0 to see if there are any clues for why you are unable to communicate. The problem here is definitely because of communication. So either the IP and network is not setup properly to talk, or the service is not up and running.
RHasleton1
73 Posts
3194
0
Posted April 19th, 2017 11:00
This should have been done prior to installing the MDM/SDS backend. The plugin shouldn't let you continue until the SDC is installed.
Either way, go to your ScaleIO plugin on the vsphere web client. There will be a link for installing the SDC on the landing page there.
If you can't install it that way, you can do it manually. You downloaded it with the other ScaleIO software. Find the vib that is appropriate for your platform (5.5 or 6), copy it to your host and install it like any other vib on an ESXi host. Reboot the host after the initial install.