Skip to main content
Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

regana

3 Posts

1052

October 19th, 2015 07:00

How does SDC choose VMKernel Adapter to use

I just installed ScaleIO R1_32.2451.4 in my vSphere 6.0 environment. Is there any way to choose which VMKernel Adapter the SDC uses for communication? I currently have 2 VMKernel Adapters created and it looks like the SDC is using the one that I have configured for vMotion. I'd like to switch it over to a different VMKernel Adapter.

pavel.heidrich

9 Posts

November 2nd, 2015 23:00

Hello, in my understanding there is no way to explicitly tie the SDC client to a particular VMkernel port, rather you can define the IP addresses it should talk to and in consequence the traffic will flow through VMkernel ports connected to the appropriate subnets.

Technically it is just a module running in VMware that uses its standard TCP/IP stack including routing table to cummunicate with other devices on network.

~ # esxcli software vib list | grep scaleio
scaleio-sdc-esx5.5             1.32-2449.4                            EMC       PartnerSupported  2015-10-11

~ # esxcli system module parameters list -m scini | grep IoctlMdmIPStr
IoctlMdmIPStr                  string  172.16.1.10,172.16.2.10,172.16.1.20,172.16.2.20  Mdms IPs, IPs for MDM in same cluster should be coma separated. To configure more than one cluster use '+' to separate between IPs.For Example: 10.20.30.40,50.60.70.80+11.22.33.44. Max 1024 characters

~ # esxcli network ip route ipv4 list
Network       Netmask        Gateway       Interface  Source
------------  -------------  ------------  ---------  ------
default       0.0.0.0        192.168.58.1  vmk0       MANUAL
172.16.1.0    255.255.255.0  0.0.0.0       vmk2       MANUAL
172.16.2.0    255.255.255.0  0.0.0.0       vmk1       MANUAL
192.168.58.0  255.255.255.0  0.0.0.0       vmk0       MANUAL

Was this post helpful?

View All

No Events found!

Top