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

www.virtualpro.co.uk