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.

Hi Craig,

installed SMI-S on a CentOS today. Any idea how to add the VNX 5500? With the "symcli" or one of the other commands?

Christian

Hi Christian

Once you have deployed it on the CentOS machine Navigate to /opt/emc/ECIM/ECOM/bin and run ./TestSmiProvider

from there add the system as per the instructions in my blog post for using this on a Windows server.

http://www.virtualpro.co.uk/2011/12/20/configuring-vasa-with-emc-arrays-%e2%80%93-clariion-vnx-and-vmax/

Let me know how you get on,  have been working on a VASA and Linux blog post  (before hitting the original issue shown above and becoming a lot busier) 

Regards

Craig Stewart

vSpecialist Technical UK/I

www.virtualpro.co.uk

Thanks Craig!

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

Any idea what to do?

Christian

Nightmare,  was hoping you had cracked it!

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.

Craig and Chris,

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.

http://powerlink.emc.com/km/appmanager/km/secureDesktop?_nfpb=true&_pageLabel=freeformlinks3&internalId=0b01406680198ce4&_irrt=true

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?

Hi woody,

sure. Please have a look into the attached shots

best regards

Christian

Hi cjohannsen81,

I'm running RHEL6.2 x64, and running into the same error. Would you mind sharing which packages it needed to work? Thank you

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.