NetApp Storage Discovery

Amit Sharma4 · ‎08-30-2015

Hi All

I have some NetApp boxes to discover. I have installed SMI-S agent 5.2 on one of my MID servers and did the repository of one of the boxes for testing.

The box was added via root privileges and same credentials were created as CIM credentials in instance.

Once I tried discovery , the result remains same as "Active, could not classified". For client installation I followed the steps mentioned in the document and took help from storage admin but no luck with discovery.

Don't know what I am missing. Please guide.

Thanks

Amit

Amit Sharma4 · ‎09-23-2015

Hi All

Thanks for the replies.
This is what worked for me.

1. Install the SMI-S agent in a server. Might be MID server with good configuration.
2. Create a local user on server and add to local admin group.
3. Login to the server with that user.
4. Run the SMI-S agent with elevated permissions.
5. Check SIM server status with command --> smis cimserver status
5. Add the for CIM access on SIM-S agent console via command --> cimuser -a -u user_name
6. Set below value on the SIM-S agent console --> cimconfig -p -s enableAuthentication=false
7. Restart the service via commands

net stop cimserver
net start cimserver
Or
smis cimserver stop
smis cimserver start

8. Take help from storage admin to add the storage controller via

smis add storage_sys storage_sys_user
Or
smis addsecure storage_sys storage_sys_user

9. Wait for 20 miutes for the repository to complete
10. Try discovery now and discover the IP on which you have installed the host.

View solution in original post

Niranjan Danda · ‎06-13-2017

Hello Steve,

I am running the storage discovery for 3par devices and while running the "CIM - Identity - WBEM Service" probe it is giving me session timed out error. i have tried to increase the socket timeout value which couldn't solve the issue. But when i change the "cim_version" probe parameter value from "modern" to "legacy" it is able to run the query.

Can you please let me know what is the issue which is giving timedout error when running with "cim_version" as "modern". The same type of warning is seen when discovering Brocade switches too while running "SMI - Fibre Channel Switch" probe.

Also for brocade devices when i change "cim_version" from "modern" to "legacy" it is giving me "Brocade_Switch{CreationClassName='Brocade_Switch',Name='10000005339EA86E'}.Name,NameFormat - Name,NameFormat. - Syntax error: Invalid token. warning.

Can you please help me in solving this issue.

Thank you,

Niranjan

stevefrancis · ‎06-16-2017

Answering your second question first: cim_version "modern" supports a more flexible query language than cim_version "legacy". One feature supported by modern that legacy doesn't support is the ability to request multiple individual values in a single query. The query should work in legacy mode if you change "Name,NameFormat" to "*"

For your first question: I don't know why legacy would work where modern fails. When the legacy code builds the query it does include two additional parameters that aren't included in modern, but both parameters are optional, and both were deprecated in 2003. If you file an INT I can check to see if that's the problem and if it is I can fix modern. If you do file an INT, refer to this conversation so customer support knows to direct the INT to me.

Niranjan Danda · ‎06-16-2017

Thanks for your response Steve! I have already created a INT with SN team. i will refer INT to this conversation.

Thank you,

Niranjan.

Ravindra Duggi1 · ‎11-08-2016

Thank you Glenn,

I don't see the smi-s installation/configuration information .

My storage team asking me to install smi-s agent and configure.

Here I have few questions :

If I install smi-s on mid server ,do we need to any configy

On Tuesday, November 8, 2016, glennpinto <community-no-reply@servicenow.com>

glennpinto · ‎11-09-2016

See Steve Francis' response.