dell ome devices unknown

Hi William,

Thanks for the query.

Dell Command | Monitor is certainly the way to go with managing Dell business clients in OME. Hope you are using the latest version of OME (i.e. 2.0.1) which enables optimal Dell business client support till date.

Note: WMI is the recommended protocol to discover Dell business clients in OME.

White paper for reference: en.community.dell.com/.../20218168

Hope this helps, keep us posted!

Is it possible to use ome to deploy the dell command monitor client onto every computer on the network so that I don't have to manually install it onto each computer?

This functionality is not available as of today in OME. Feedback taken and something to think about for future releases.

I have enabled both WMI and SNMP during discovery and the devices still show up as unknown. I'm scratching my head at the moment. Are there any other reasons as to why this is happening? I can't seem to find a solution anywhere on the web either.

I suspect that this has something to do with both wmi protocols during the discover and inventory process. I have snmp authentication traps enabled and every time I discover using wmi, I get authentication failure. I don't know what I'm doing wrong. When I try connecting to the machine using wmi in trouble shooting tool, it just tells me "failed to connect to name space". This is probably the reason why my devices show up as unknown. I understand that Dell OpenMonitor installs the ns onto the client so that it can be discovered properly. But it doesn't seem to fix this issue.

The SNMP Authenticatoin failure is because of this setting that needs to be disabled on the client.

If the troubleshoot tool give an error connecting to the WMI namepace that is the cause of the issue.

• Check if all the necessary ports on every relevant firewall is opened.
• Make sure the user you are using has sufficient rights (Local Admin).

Are you sure that the clients are supported in OME? Check the Dell OpenManage Essentials Version 2.0.1 Support Matrix 

Yes, but the authentication trap is a good way to test whether or not the wmi credentials that I'm inputting are valid or not. I have enabled the ports necessary for snmp protocol to work. Aside from the Dell monitor client, is there another wmi client that I'm supposed to install? 

That authentication error you get from SNMP has nothing to do with the password you enter for WMI, see SNMP Security Tab 

Send authentication trap: Specifies whether to send an SNMP trap message to all trap destinations if this SNMP host receives an SNMP request from an SNMP host or community that is not listed on the Security tab. Authentication is the process of verifying that a host name or address is valid. When the SNMP agent receives a request that does not contain a known community name or that is not sent from a member of the acceptable hosts list, the SNMP agent sends an authentication trap message to one or more trap destinations, indicating the failure of authentication. This check box is selected by default.

Please make sure WMI on the client is working as it should see this Microsoft article to troubleshoot WMI http://blogs.technet.com/b/askperf/archive/2014/08/11/wmi-missing-or-failing-wmi-providers-or-invalid-wmi-class.aspx 

Thanks for clarifying that. Yes, so apparently it's only this one computer on the network that's having this issue. It seems as if there is something wrong with the name space. I've found nothing helpful for me on that site unfortunately. 

I actually one more question that I want to ask. :

For all of the computers that I've successfully discovered and inventoried, when I click on the alerts tab, there is nothing. In this video, the alerts page generates an extensive summary of the current state of the client. I can't seem to get my devices to generate the same type of summaries.

Alerts are just SNMP traps.

So configure your Windows servers, Windows clients and IDRAC's to send SNMP traps to the OME server and you will get the alerts.

It still doesn't show anything in the alerts trap. Does this summary only appear for servers? I am only trying to set up alerts for computers. I set up my snmp traps properly. I put the static IP address under destination and the same community string as what I have inside snmp service properties. When I send test trap and email alerts, they go through. I even enabled port 162 for both TCP and UDP in the firewall settings. Any other suggestions as to what I can do?

Do you see the test traps in the OME server?

Alerts are only send once when they occur, so there is no historical data.

Yes, I do see the test traps sent by ome. What I meant by alerts was the alerts that you see in the video above. When you click on the alerts tab, there should be a detailed description of the current status of the client.

My question is, if one of my computers hard drives die, will this generate an email saying that there's an hard drive failure? is this accomplished by setting up snmp traps? So far, I am able to get email alerts when the computer is down. Do I have to configure the community string and destination IP address as the monitoring ome server's in order to receive these trap notifications via email?

Also, are we able to configure alerts so that they generate real time notifications? After I pulled out the power, it generated an email like a minute later.

SNMP alerts are realtime and their capabilities depend on the sending device, but they can do what you are describing.

For instance on a Dell server with iDRAC you need to configure the iDRAC to send SNMP alerts to OME and also enable the events to being able to send for certain alerts.
See Integrated Dell Remote Access Controller 8(iDRAC8) and iDRAC7 Version 2.10.10.10 RACADM Command Line Interface Reference Guide on page 30.

Are you still testing on Dell clients or servers?

I am testing on computers only. So in terms of computers, how can I get the computers to generate an snmp alert to ome and then issue  the alert to our help desk's email? iDRAC is only for severs, correct?

I tried testing a computer with a failed hard drive, and all it said was system down. System up/down seems to be the only two statuses that I get.

bump