This question was originally posted on DCIM Support by Norberto Castillo on 2016-12-21
We use protocols WMware, SNMP, SSH,WMI in our ITO.
I attached screen of discovery and server visiteds
The messages of result are:
Error to conect
Ensure the service is runing and verify credentials
Unable to determine device operating system
Ensure the service is running and verify credentials SSH
Error – Password authentica
What we should do in every mistake?
In case discovery IBM and HP Chassis of “advanced SNMP agent”, you can send me more information.
Why I don´t can see power and temperature?
This answer was originally posted on DCIM Support by Greg Sterling on 2016-12-22
There are several questions in your posting. Lets see if we can answer some of them here.
Regarding your question/comment regarding missing temperature information. IPMI protocol should be used to return direct avg/peak power and server inlet temperature data. None of the other protocols return temp information. If you have HP's OneView software then using the HP OneView integration will also return temp and power data because OneView uses IPMI.
The power data in the ITO overlay in DCO might be missing if the discovery did not match a genome asset to the server model or if the database is missing power profile data for the server model. Which server make and model is this device?
The "error to connect" messages mean ITO could not connect to the target host using the specified protocol(s). So for example if you see "snmp: unable to connect", then either the SNMPD daemon is not running on the target client, the specified community string is incorrect, or the portion of the SNMP mib is not enabled.
Try using this command to test an SNMP response from a linux client. In general if this command returns successfully then SNMP polling should work
snmpwalk -c public -v 1 <clientip> 188.8.131.52.4.1.2021
You can try this command to test WMI connections to a host from the ITO server.
wmic /node:<client-ip> /user:<username> OS get
Regarding the SSH discoveries and the messages "unable to determine device vendor". When you see that message using a WMI, or SSH discovery that is usually a sign the user account used to complete the discovery on the host lacked permissions to grab the data it needed to determine the device make and model. For SSH discoveries this usually means you used a non-root user account for discovery and "sudo" permissions have not been enabled in ITO. Here's how to enable SUDO with ITO and an example of setting up a /etc/sudoers file.
There's a one-time change required on the IT Optimize server, to enable SSH discovery using "sudo".
itouser ALL=(ALL) NOPASSWD: /usr/local/bin/viriditylisthw
Discuss challenges in energy and automation with 30,000+ experts and peers.
Find answers in 10,000+ support articles to help solve your product and business challenges.
Find peer based solutions to your questions. Provide answers for fellow community members!