So this will teach me to get involved with a linux installation
I am deploying the SMI-S components that are used for configuring VASA on a linux VM - CentOS v6.2 - 64 bit
CIM ObjectManager Name: EMC:127.0.0.1
CIMOM Version: EMC CIM Server Version 2.6.7.0.0.22
SMI-S spec version: 1.6.0
SMI-S Provider version: V4.3.2.0
SMI-S Provider Location: Proxy
SMI-S Provider Server: Linux VASACENTOS 2.6.32-220.el6.x86_64 #1 SMP Tue Dec 6 19:48:22 GMT 2011 x86_64 VM Guest OS (64bit Libraries)
Solutions Enabler version: V7.3-1404 2.0
When trying to add a VNX to the system through the TestSmiProvider tool I get the following error indicated that there is a problem communicating with the base daemon (which I am assuming in this instance is Storapid)
++++ EMCAddSystem ++++
Error: A general error occurred that is not covered by a more specific error code. (com.emc.cmp.osls.se.osl.DiscoveryServices.StorInstanceDiscover():142 F:ERROR_FAMILY_FAILED R:1000133 L:2 1000133 : "Problem encountered while communicating with the base daemon" : "SymDiscover Failed" : 2 : 4649 : "Problem encountered while communicating with the base daemon")
I get the same error if I simply run a standard symcfg discover command, the following content is from the symapi.log and shows both types of operation
01/29/2012 18:01:31.889 4026 1 EMC:SMI Provider emcSymDiscover A network failure occurred while communicating with the base daemon
01/29/2012 18:01:58.918 4026 3 EMC:SMI Provider emcSymDiscover A network failure occurred while communicating with the base daemon
01/29/2012 18:08:00.748 5107 2 EMC:SYMCFG emcSymDiscover A network failure occurred while communicating with the base daemon
I've had a look around and checked the log for the storapid and it appears to be running ok
Craig, I don't know if you have sorted this out yet. If not, I'd suggest you take a look at Primus emc256119
The cause could be :
There are networking issues stopping the host from being able to communicate with the base daemon. The host attempts to open a socket to communicate with the base daemon, and when that fails the 'problem encountered while communicating with the base daemon' error message is returned.
And it gives a temp workaround:
Support: Setting storapid:client_use=never in daemon_options file and restarting storapid daemon works as a temporary workaround.
This primus is for Symcli on windows server host, but I think you can try it on you Centos environment. Good luck.
Now it stucks at the same place as in you initial question:
++++ EMCAddSystem ++++
Error: A general error occurred that is not covered by a more specific error code. (com.emc.cmp.osls.se.osl.DiscoveryServices.StorInstanceDiscover():142 F:ERROR_FAMILY_FAILED R:1000186 L:2 1000186 : "Unable to communicate with the base daemon. The base daemon is shutting down" : "SymDiscover Failed" : 2 : 28016 : "Unable to communicate with the base daemon. The base daemon is shutting down")
The bad is that there isn´t a use_client option in: /usr/emc/API/symapi/config/daemon_options
I tried a number of things before taking to the forums, including changing the port used by ECOM in case it was clashing with something else on the CentOS box.
I couldn't find the issue and haven't had time to revisit. Hopefully someone else out there does, if I get the chance I will take a look at this again as been meaning to get the completed blog post out there.
Have you tried to open a ticket with OSAPI team (now it's called SSG). From the support perspective, OSAPI should handle the issues occurred with symcli. You can use the powerlink support URL to open the ticket and don't even need to put symm s/n or site id.
Update: After some help from SSG I installed it on RHEL and found a list of libraries I had to install before. Now it runs as expected. The only thing I don´t understand that there is no profile for NFS on VNX... the compatibility matrix also points to the FC/FCoE and iSCSI protocols... Any idea when this will be available for NFS on VNX?
Cheers to you! That's what I was missing. If only support had been able to figure this out in the week and a half we've been looking at this. Thanks again.
Jingyi1
2 Intern
•
199 Posts
1228
0
Posted February 13th, 2012 23:00
Craig, I don't know if you have sorted this out yet. If not, I'd suggest you take a look at Primus emc256119
The cause could be :
There are networking issues stopping the host from being able to communicate with the base daemon. The host attempts to open a socket to communicate with the base daemon, and when that fails the 'problem encountered while communicating with the base daemon' error message is returned.
And it gives a temp workaround:
Support: Setting storapid:client_use=never in daemon_options file and restarting storapid daemon works as a temporary workaround.
This primus is for Symcli on windows server host, but I think you can try it on you Centos environment. Good luck.