Unsolved
This post is more than 5 years old
37 Posts
0
6202
SMI-S Provider on CentOS 6.2
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
[23765 Listener] Jan-29 21:10:18.407 : storapid Starting, Version: V7.3-1404 (2.0) [RT]
[23765 Listener] Jan-29 21:10:18.408 : [acquire_gk_lock()] Gatekeeper lock mode is 'FREE'
[23765 Listener] Jan-29 21:10:18.408 : storapid Daemon : up and running
[23765 Init] Jan-29 21:10:18.408 : [gkmgt_init()] Gatekeeper Management recovery started
[23765 Init] Jan-29 21:10:18.409 : [display_pr_topology()] The PR_TOPOLOGY is NULL
[23765 Init] Jan-29 21:10:18.409 : [gkmgt_init()] Waiting up to 20 seconds for LockMgr thread to start (attempt 1/3)
[23765 Init] Jan-29 21:10:18.409 : [gkmgt_init()] The LockMgr thread has started
[23765 Init] Jan-29 21:10:18.409 : [gkmgt_init()] Waiting up to 20 seconds for GKMgt thread to start (attempt 1/3)
[23765 Init] Jan-29 21:10:18.409 : [gkmgt_init()] The GKMgt thread has started
[23765 Init] Jan-29 21:10:18.409 : [gkmgt_init()] Gatekeeper Management recovery complete
[23765 Init] Jan-29 21:10:19.410 : [init_thread()] Daemon initialization complete
Be grateful if anyone has any ideas about what may be wrong with this deployment and causing this issue?
Regards
Craig Stewart
vSpecialist Technical UK/I
Jingyi1
199 Posts
0
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.
cjohannsen81
11 Posts
0
February 29th, 2012 04:00
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
Craig_Stewart
37 Posts
0
February 29th, 2012 05:00
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
cjohannsen81
11 Posts
0
February 29th, 2012 07:00
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
Craig_Stewart
37 Posts
0
February 29th, 2012 07:00
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.
Jingyi1
199 Posts
0
February 29th, 2012 19:00
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
cjohannsen81
11 Posts
0
April 23rd, 2012 08:00
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?
cjohannsen81
11 Posts
0
April 25th, 2012 13:00
Hi woody,
sure. Please have a look into the attached shots
best regards
Christian
woody_ent
2 Posts
0
April 25th, 2012 13:00
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
woody_ent
2 Posts
0
April 27th, 2012 07:00
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.