- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎08-30-2015 01:57 PM
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
Solved! Go to Solution.
- Labels:
-
Discovery
-
Service Mapping
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 07:48 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎07-20-2021 12:09 PM
Its being used in identification phase .I am seeing any affinity created .Any other way we can check that.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-23-2015 07:48 AM
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.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎03-10-2016 06:14 AM
Hi,
I am getting below errors:
'Script error in sensor: Data field `tcp_port` is undefined on Ci ' on the CIM probe. /
Script error in sensor: Data field `tcp_port` is undefined on Ci {cim_object_path:'(undefined)',sys_id:'fadfasdfasdcvc34534sdfcxcz4345',table:'cmdb_ci_wbem_service'} |
and
CIMOM information not provided. Skipped CI. on the CIM WBEM.
any ideas on this?
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-05-2016 10:42 AM
Hi Amit,
We are also planning to do the storage discovery from NETAPP,now my storage guys are asking me what level of CIM Credential required for this,
like read-only/admin CIM Credentials,is there any other credentials are required
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎11-05-2016 12:21 PM
You are going to want an Admin user configured in the SLP provider (agent) and that same user on the host in which its installed!