Start a Conversation

This post is more than 5 years old

Solved!

Go to Solution

4321

June 12th, 2012 00:00

Unable to connect to the SMI provider on Celerra

Hi there,

I started the ECOM service on the Celerra machine using the command

/celerra/wbem/bin/start_cim_server /celerra/wbem

This command ends with this message, which I presume that the service is successfully started

[root@PITEMC1 bin]# ./start_cim_server /celerra/wbem                       

program 707000 version 1 ready and waiting

-I- Loading configuration files from /celerra/wbem/conf

-I- Base directory set to /celerra/wbem/

HTTP Output Tracing initialized. Messages will be logged to HTTP_trace.log

HTTP Input Tracing initialized. Messages will be logged to HTTP_trace.log

-W- Could not get config setting ECOMContextManager:PluginName

-I- Could not initialize the platform specific context manager. Setting it to default behaviour of cimom.

-I- Successfully loaded Security plugin: Celerra_SecurityPlugin

With this running I try to connect to the ECOM service using http using wget

root@sg-schneider:~# wget http://10.1.1.120:5988

--2012-06-12 07:07:14--  http://10.1.1.120:5988/

Connecting to 10.1.1.120:5988... connected.

HTTP request sent, awaiting response... 301 Moved Permanently

Location: https://10.1.1.120:5989/ [following]

--2012-06-12 07:07:14--  https://10.1.1.120:5989/

Connecting to 10.1.1.120:5989... connected.

ERROR: cannot verify 10.1.1.120's certificate, issued by `/O=Initial Factory Certificate/CN=1.2.3.4/CN=Temporary Certificate - NOT VALID/CN=Generate New Certificate with /nas/sbin/nas_config -ssl':

  Self-signed certificate encountered.

ERROR: certificate common name `1.2.3.4' doesn't match requested host name `10.1.1.120'.

To connect to 10.1.1.120 insecurely, use `--no-check-certificate'.

root@sg-schneider:~#

My Port_Setting.xml file is as follows

        5988

        false

        true

               

               

                Port1

                true

               

       

        5989

        true

        true

Can anyone please let me know whats wrong here. I got ECOM working on Clariion pretty easily. I also did try runnning /nas/sbin/nas_config -ssl

but in vain.

Any help is appreciated.

Thanks

Roycey

4 Operator

 • 

8.6K Posts

June 13th, 2012 11:00

Try the nasadmin account

Also make sure in UniSphere the account has API access enabled

4 Operator

 • 

8.6K Posts

June 12th, 2012 04:00

Are you trying to use the SMI-S for file provider ?

As far as I remember you need to edit the config file.

See the SMI-S programmers guide on Powerlink

Rainer

19 Posts

June 13th, 2012 04:00

Here is message from the cimomlog.txt

13-Jun-2012 06:14:32.717 -140106640-T- NAVHTTPServerListener: Received connection from monitoring-box[0:0:0:0:0:FFFF:A02:13D]:56837 (on PITEMC1.sdcpa.com[0:0:0:0:0:FFFF:A01:178]:5988)

13-Jun-2012 06:14:32.720 -93293456-T- WebServer: Received HTTP request. Version = HTTP/1.1

13-Jun-2012 06:14:32.721 -93293456-I- ECOM: Authenticating incoming request

13-Jun-2012 06:14:32.723 -93293456-I- ECOM: Authenticating user "admin" (basic authentication)

13-Jun-2012 06:14:35.073 -93293456-I- admin:Celerra_Authenticator::authenticate: ^B

13-Jun-2012 06:14:35.075 -93293456-E- admin:Celerra_Authenticator::authenticate: ^B

13-Jun-2012 06:14:35.077 -93293456-E- RequestHandler::sendForbidden: Forbidden request: HTTP/1.110.1.1.120:5988/cimom

Not sure if I even need to pass some credentials or not.

19 Posts

June 13th, 2012 04:00

Now I am sure the ECOM server is running fine. I am trying to query the server for information about the Celerra system - CIM-ComputerSystem.

In case of Clariion, we connect to the ECOM server using the credentials admin and #1Password. Does the Celerra ECOM server have similary credentials. If yes, are they the same or something else. The SMI programmer guide does not mention any credentials as such. It just mentions how to get the server started.

How do I connect to the ECOM server for running CIM-XML queries?

19 Posts

June 14th, 2012 05:00

Thanks Rainer

nasadmin did work.

19 Posts

June 14th, 2012 05:00

Just for the benefit of others, I did some changes to the /celerra/wbem/conf/Port_Settings.xml file.

Instead of forward the traffic on http to the https port (my initial) question, I just allowed all traffic on the HTTP port with these changes

    5988

    false

    true

       

               

               

                true

       

       

 

    5989

    true

    true

Once this was done, I could send requests to the http://my_ip:5988/ecomconfig and it showed the login page

Thats when I used the nasadmin credentials to login. The same credentials can be used for your CIM-XML queries.

4 Operator

 • 

8.6K Posts

June 14th, 2012 09:00

Thanks for the feedback

May I ask what you are using the API for ?

Is this a custom application for one customer or a commercial product?

Rainer

No Events found!

Top