WMI discovery

[DCIM_Support]

When I trying to discover Windows server via WMI - get nothing.

Username which using for that is correct (no nonEnglish letters) and have all permissions to execute remote queries (checked in wmic command ). Discover details which available after discovery - empty.

Which right and permissions are needed for successfully discovering Windows machine?

Where can I find detailed logs about discovery process on DCO server ?

(CID:96044533)

[DCIM_Support]

Hello DFJ

You mentioned in your question the discovery details are empty. If you narrow the IP address range in the discovery to attempt to discover the specific server, does the discover state the host is visited or does the visited field for this discover remain 0?

Logs from the IT Optimize server are collected when client and server logs are collected from the DCO client. If you open the collected logs zip file, go to the server folder, then the ito sub-folder, there should be a CustomerSupport.zip file prefixed with the ito server name or IP address.  If you open that zip file look for the file called console.log.0 to investigate the discover problem. You can also share these logs with us and we will look into the problem.

Regards

Greg Sterling

(CID:96044593)

[DCIM_Support]

Hi Greg, if only one ip address is specified for discover - visited field is 1 but discovered/rediscovered is 0. Here you can see tail of log - http://pastebin.com/GWfcftns Discovery was made for only one ip, protocol - ipmi.

(CID:96044605)

[DCIM_Support]

DFJ. Looking at the log information it appears the DCM services are not running: 04/28/2015:07:02:04:INFO:tid=000019: Executed InvalidateResultSetRequest in 0ms successfully. 04/28/2015:07:02:06:INFO:tid=000022: JMSScheduler: Executing saved request - Job: Job-1430229726066 Group: com.viridity.dcos.mgmtglue.discovery.DMDiscoveryRequest 04/28/2015:07:02:06:INFO:tid=000023: JMSScheduler: Job Job-1430229726066 is about to be executed. 04/28/2015:07:02:06:INFO:tid=000015: Executed InvalidateITPSessionRequest in 0ms successfully. 04/28/2015:07:02:09:WARNING:tid=000024: Failed to establish connection to DCM Server @localhost:8688 - com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.UnknownHostException: Struxure_ITOptimize 04/28/2015:07:02:09:WARNING:tid=000024: DCM: Unable to connected to DCM Server localhost:8688 04/28/2015:07:02:11:WARNING:tid=000024: Failed to establish connection to DCM Server @localhost:8688 - com.sun.xml.internal.ws.client.ClientTransportException: HTTP transport error: java.net.UnknownHostException: Struxure_ITOptimize 04/28/2015:07:02:11:INFO:tid=000024: AEFPlatformDiscovery.acceptsCommand: package com.viridity.dcos.discovery.com.viridity.dcos.discovery.AEFShallowDiscoveryCommand 04/28/2015:07:02:11:INFO:tid=000024: Processing command: package com.viridity.dcos.discovery.com.viridity.dcos.discovery.AEFShallowDiscoveryCommand 04/28/2015:07:02:11:INFO:tid=000024: Discovering unknown object: OMUnknown 04/28/2015:07:02:11:INFO:tid=000024: Request: 27464 IP: 10.136.204.253/10.136.204.253 is reachable. 04/28/2015:07:02:11:INFO:tid=000018: *** Analysis time for AEFSimpleAnalysisCommand took 78ms 04/28/2015:07:02:12:INFO:tid=000011: *** Analysis time for AEFSimpleAnalysisCommand took 9ms 04/28/2015:07:02:12:INFO:tid=000014: Executed GetDiscoveryConfigRequest in 4419ms successfully. 04/28/2015:07:02:12:INFO:tid=000018: Executed GetAssetByHandleRequest in 552ms successfully. 04/28/2015:07:02:12:INFO:tid=000025: JMSStateManager: Job: Job-1430229726066 has completed with state: Success Group: com.viridity.dcos.mgmtglue.discovery.DMDiscoveryRequest 04/28/2015:07:02:12:INFO:tid=000011: Executed GetAssetByHandleRequest in 562ms successfully. The log entries are typical when the Intel DCM services are not running. If you review the windows services control panel you should see five Intel services, make sure the Intel Data Center Manager Server and Intel DCM services are both running. Can you send us a full set of logs from this IT Optimize server? To collect only the ITO logs, browser to the ITO server https://:8090/, logon using apc/apc, then click the "system settings" button (top right side), click the support tab, then the "download..." button to download a customersupport.zip file. Regards Greg Sterling

(CID:96044623)

[DCIM_Support]

I have been working on using various protocols for ITO for discoveries and have found that especially for WMI discoveries many times the windows server which you want to discover doesn't respond for following reasons:

a. You need to switch on SNMP polling along with WMI and ensure the key is correct for SNMP polling as most of the time the keys are not public or private on servers.

b. There is a service called as SNMP TRAP service within windows server machines which requires you to enter the ip of ITO to respond to. The moment you put address of ITO server in the to be discovered server you will start getting SNMP/WMI response also at times...

See if you are able to get response using the above tricks...

(CID:96044607)

[DCIM_Support]

This question is closed for comments. You're welcome to start a new topic if you have further comments on this issue.