simon13

updated

10 years ago

S

simon13

7 Posts

0

4699

July 19th, 2016 14:00

Communication error adding Slave MDM

Fresh install with EMC ScaleIO v2.0-6035.0 using the vcenter plugin on VMware ESXi, 6.0.0, 3380124

During the deployment process, I get this error adding the slave MDM

FAILED (Error code: COMMUNICATION_ERROR) : Add Slave MDM


I already moved to a different set of esx servers (different hardware vendor) and got the exact same error.


I can ping between the hosts using the data IPs below.


Any ideas?


-------

Jul 19, 2016 8:17:00 PM Host: esx-a1-3.ilab.plexxi.com - SUCCEEDED: Install ScaleIO Module [IP: 172.25.200.3, module: TB]

Jul 19, 2016 8:17:00 PM Host: esx-a1-2.ilab.plexxi.com - SUCCEEDED: Install ScaleIO Module [IP: 172.25.200.2, module: SLAVE_MDM]

Jul 19, 2016 8:17:00 PM Host: esx-a1-1.ilab.plexxi.com - SUCCEEDED: Install ScaleIO Module [IP: 172.25.200.1, module: MASTER_MDM]

Jul 19, 2016 8:17:00 PM Host: esx-a1-1.ilab.plexxi.com - STARTED: Add Master MDM [Mgmt IPs: [172.25.200.1], data IPs: [10.1.100.1, 10.1.101.1]]

Jul 19, 2016 8:17:08 PM Host: esx-a1-1.ilab.plexxi.com - SUCCEEDED: Add Master MDM [Mgmt IPs: [172.25.200.1], data IPs: [10.1.100.1, 10.1.101.1]]

Jul 19, 2016 8:17:08 PM Host: esx-a1-2.ilab.plexxi.com - STARTED: Add Slave MDM [Mgmt IP: 172.25.200.2, data IP 1: 10.1.100.2, data IP 2: 10.1.101.2]

Jul 19, 2016 8:17:11 PM Host: esx-a1-2.ilab.plexxi.com - FAILED (Error code: COMMUNICATION_ERROR) : Add Slave MDM [Mgmt IP: 172.25.200.2, data IP 1: 10.1.100.2, data IP 2: 10.1.101.2]

Jul 19, 2016 8:23:48 PM Host: esx-a1-2.ilab.plexxi.com - STARTED: Add Slave MDM [Mgmt IP: 172.25.200.2, data IP 1: 10.1.100.2, data IP 2: 10.1.101.2]

Jul 19, 2016 8:23:52 PM Host: esx-a1-2.ilab.plexxi.com - FAILED (Error code: COMMUNICATION_ERROR) : Add Slave MDM [Mgmt IP: 172.25.200.2, data IP 1: 10.1.100.2, data IP 2: 10.1.101.2]

Jul 19, 2016 8:37:48 PM Host: esx-a1-2.ilab.plexxi.com - STARTED: Add Slave MDM [Mgmt IP: 172.25.200.2, data IP 1: 10.1.100.2, data IP 2: 10.1.101.2]

------

  • 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.

  • simon13

    7 Posts

    2148

    0

    Posted July 19th, 2016 15:00

    A bit more from the details on the esx host its failing on

    ......

    Completed: Deploy VM ScaleIO-172.25.200.2

    Completed: Perform initial configuration for VM: 172.25.200.2

    Completed: Install ScaleIO LIA module

    Failed: Add SLAVE_MDM to MDM cluster (ScaleIO - Communication error between core components)

    Waiting: Install ScaleIO SDS module

    ......

  • pawelw1

    306 Posts

    2148

    0

    Posted July 21st, 2016 00:00

    Hi Simon,

    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.

    Thanks!

    Pawel

  • pawelw1

    306 Posts

    2148

    0

    Posted December 1st, 2016 04:00

    Hi Jonathan,

    No, I haven't heard from Simon. In most cases the issue lies in the network configuration on the ESXi.

  • Suriya_007

    54 Posts

    2148

    0

    Posted April 9th, 2017 12:00

    Hi

    Am also facing same error i can able to ping both management and data link IP's from my SVM's

    Regards

    Suriya M

  • RHasleton1

    73 Posts

    2148

    0

    Posted April 10th, 2017 07:00

    Hi Suriya_007 (and everyone else),

    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.

    Hope that helps

  • Suriya_007

    54 Posts

    2148

    0

    Posted April 14th, 2017 12:00

    Hi Rickh,

    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

    module: SLAVE_MDM]

    Apr 14, 2017 7:21:28 PM Host: mcdcesxi09.masscloudspace.local - STARTED: Install ScaleIO Module [IP: 10.20.30.14, module: MASTER_MDM]

    Apr 14, 2017 7:21:59 PM Host: mcdcesxi11.masscloudspace.local - SUCCEEDED: Install ScaleIO Module [IP: 10.20.30.16, module: TB]

    Apr 14, 2017 7:21:59 PM Host: mcdcesxi10.masscloudspace.local - SUCCEEDED: Install ScaleIO Module [IP: 10.20.30.15, module: SLAVE_MDM]

    Apr 14, 2017 7:21:59 PM Host: mcdcesxi09.masscloudspace.local - SUCCEEDED: Install ScaleIO Module [IP: 10.20.30.14, module: MASTER_MDM]

    Apr 14, 2017 7:21:59 PM Host: mcdcesxi09.masscloudspace.local - STARTED: Add Master MDM [Mgmt IPs: [10.20.30.14], data IPs: [10.20.70.13]]

    Apr 14, 2017 7:22:05 PM Host: mcdcesxi09.masscloudspace.local - SUCCEEDED: Add Master MDM [Mgmt IPs: [10.20.30.14], data IPs: [10.20.70.13]]

    Apr 14, 2017 7:22:05 PM Host: mcdcesxi10.masscloudspace.local - STARTED: Add Slave MDM [Mgmt IP: 10.20.30.15, data IP 1: 10.20.70.14, data IP 2: null]

    Apr 14, 2017 7:22:10 PM Host: mcdcesxi10.masscloudspace.local - FAILED (Error code: COMMUNICATION_ERROR) : Add Slave MDM [Mgmt IP: 10.20.30.15, data IP 1: 10.20.70.14, data IP 2: null]

    Apr 14, 2017 7:36:09 PM Host: mcdcesxi10.masscloudspace.local - STARTED: Add Slave MDM [Mgmt IP: 10.20.30.15, data IP 1: 10.20.70.14, data IP 2: null]

    Apr 14, 2017 7:36:13 PM Host: mcdcesxi10.masscloudspace.local - FAILED (Error code: COMMUNICATION_ERROR) : Add Slave MDM [Mgmt IP: 10.20.30.15, data IP 1: 10.20.70.14, data IP 2: null]

    Thanks in Advance

    Suriya

  • Suriya_007

    54 Posts

    2152

    0

    Posted April 17th, 2017 01:00

    Can i have update on the above request plz

  • Suriya_007

    54 Posts

    2152

    0

    Posted April 17th, 2017 05:00

    Hi Implementation stopped in getting with below error

    Completed: Deploy VM ScaleIO-10.20.30.15

    Completed: Perform initial configuration for VM: 10.20.30.15

    Completed: Install ScaleIO LIA module

    Failed: Add SLAVE_MDM to MDM cluster (ScaleIO - Communication error between core components)

    Waiting: Install ScaleIO SDS module

    Waiting: Install ScaleIO RFCACHE module

    Waiting: Configure SDC driver on ESX

    Waiting: Create VMDK ScaleIO-VMDK-2074960421 on datastore esxi_10_local_ds_02

    Waiting: Create VMDK ScaleIO-VMDK-2074960422 on datastore esxi_10_local_ds_01

    Waiting: Add SDS device ScaleIO-7bad6225 to Storage Pool MSSI_SP

    Waiting: Add SDS device ScaleIO-7bad6226 to Storage Pool MSSI_SP

    Any suggestion please

    Regards,

    Suriya M

  • RHasleton1

    73 Posts

    1263

    0

    Posted April 17th, 2017 11:00

    Hi Suriya,

    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.