This post is more than 5 years old
6 Posts
0
4681
Question, should SCINI be running after installing SDC on ESX hosts?
Forgive me for the noob question, still learning this stuff. Using the EMC ScaleIO Deployment Guide, v 2.0.x Rev03. After installing the plugin successfully and successfully uploading the template ova to the DASxx datastores. I ran the Install "SDC on ESX" from the EMC ScaleIO plugin. All seems to go well, and I have rebooted a few times since, but during the required reboot, I see a message that says "scini failed to load". This is ESXi 6.0 U3 dell customized A03 (file name: VMWare-VMvisor-Installer-6.0.0.update03-5224934.x86_64-DellEMC_Customized-A03.iso ( I did confirm the hash was good after downloading it)
So my question is, should SCINI be running after reboot?
Background: I had gone thru this last week (with the A02 version of the iso), and had seen the same message, but basically ignored it. I went thru the complete ScaleIO deployment, and it went a ways, installed the Master MDM, then died installing the slave MDM saying it couldnt connect to the master and timed out. I googled the message and it pointed to scini not running (in addition to checking network configuration issues). The suggestion was to manually copy the vib and install it manually, and I did this, but trying to start the scini module would simply say : Failure.
Nothing I did would make it run, so I wiped the hosts and installed the above A03 iso, but again I see the "failed to start scini". I have yet to try the ScaleIO deployment again.
I should note, I'm in a testing environment and I dont have the management side of the cluster up and running, I am only tasked with the adding of a node to the compute cluster (which I'm trying to configure).
gc_emc
45 Posts
0
September 26th, 2017 00:00
Hi ,
These few tip should help in getting you started:
Check what VIBs are installed on the server
#esxcli software vib list | grep -i scaleio
Check the current SDC configuration - make sure the MDM ip address are visible here:
#esxcli system module parameters list -m scini | head -4
If not configure the MDM ip addresses:
#esxcli system module parameters set -m scini -p "IoctlIniGuidStr=GUID_GOES_HERE IoctlMdmIPStr=x.x.x.x,x.x.x.x,x.x.x.x,x.x.x.x"
( x.x.x.x.x are the MDM ip addresses )
Check the output from the cmd below and confirm it is set to true.
# esxcli system module list |grep scini
scini true true
Make sure all your ESXi servers that you are installing the SDC drivers on can ping the MDMs and SDSs.
Refer to the Dell EMC KB for further information on ESXi SDC configuration and troubleshooting.
https://support.emc.com/kb/466097
Rdgs.
Avinash V
91 Posts
0
September 26th, 2017 02:00
try to run 'esxcli system module load -m scini' and check what error you get.
Most likely if the error refer to Bad Parameters, setting parameters what Gearoid stated above should fix this.
reybeast
6 Posts
0
September 26th, 2017 08:00
Oh, and the other 2 systems involved have .114 and .115 IP addresses like the above post.
so, vmk0 100.68.77.113 can vmkping 100.68.77.114 and .115 (using jumbo frames fails on this range, but I believe 9K is not used on management.) non jumbo vmkping works fine.
vmk1 can vmkping 75.113, 114 and 115 using jumbo
vmk2 can vmkping 103.113, 114 and 115 using jumbo
vmk3 can vmkping 105.113, 114 and 115 using jumbo
reybeast
6 Posts
0
September 26th, 2017 08:00
Really my confusion is that it appears there is not an MDM IP available, but that seems correct since I havnt actually gone thru the ScaleIO deployment where I configure the Initial Master MDM, Manager MDM and TieBraker MDM. I forgot to mention in my original post that I did see https://support.emc.com/kb/466097 and went thru the steps, other than generating a GUID.
NOTE: I use different vlans for my deployment:
esx mgmt 105 >> vlan 77
vMotion 106 >> vlan 75
Sio Data1 152 >> vlan 103
Sio Data2 160 >> vlan 105
Here are results of commands:
[root@Reysys1:~] esxcli software vib list | grep -i scaleio
scaleio-sdc-esx6.0 2.0-13000.166 EMC VMwareAccepted 2017-09-25
[root@Reysys1:~] esxcli system module list |grep scini
scini false true
[root@Reysys1:~] esxcli system module load -m scini
Unable to load module /usr/lib/vmware/vmkmod/scini: Failure
[root@Reysys1:~] esxcfg-vmknic -l
Interface Port Group/DVPort/Opaque Network IP Family IP Address Netmask Broadcast MAC Address MTU TSO MSS Enabled Type NetStack
vmk0 0 IPv4 100.68.77.113 255.255.254.0 100.68.77.255 24:6e:96:18:1d:ca 9000 65535 true STATIC defaultTcpipStack
vmk1 16 IPv4 100.68.75.113 255.255.254.0 100.68.75.255 00:50:56:62:0a:da 9000 65535 true STATIC defaultTcpipStack
vmk2 0 IPv4 192.168.103.113 255.255.255.0 192.168.103.255 00:50:56:6f:e2:e5 9000 65535 true STATIC defaultTcpipStack
vmk3 0 IPv4 192.168.105.113 255.255.255.0 192.168.105.255 00:50:56:69:9a:71 9000 65535 true STATIC defaultTcpipStack
[root@Reysys1:~]
[root@Reysys1:~] esxcli system module parameters list -m scini | head -4
Name Type Value Description
----------------------------------- ------ ----- --------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
IoctlIniGuidStr string Ini Guid, for example: 12345678-90AB-CDEF-1234-567890ABCDEF
IoctlMdmIPStr string 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
[root@R
reybeast
6 Posts
0
September 26th, 2017 11:00
Well, answered my own question, no, it doesnt matter if scini fails to load after installing SDC (before ScaleIO deployment). I went ahead and attempted the ScaleIO deployment, and it went through completely. I can say that I did have to tag the physical switch ports in the vlans for sio data1 and sio data2, which was all I changed.
I made the change before retrying the SDC installation, so the message "scini failed to load" happened even though the network configuration was in a good state.
I will admit, it is critical that the vmkping tests work as described in the article https://support.emc.com/kb/466097
and that one can ping the configured host IPs from its respective vmknic.
Live and learn. Hopefully this will help someone in the future.