Very good morning Andrew ,
Perfect, then we continue on this forum discussing the configuration of my HP SIM .
As I say , I understand you have to install SNMP agents and SMH machines I want to monitor . I have the following packages installed on a machine to be monitored:
hp- snmp- agents- 9.40 - 2506.37.rhel6.x86_64
hp- smh -templates - 9.4.0 - 1327.37.noarch
hp -health- 9.40 - 1602.44.rhel6.x86_64
hpsmh - 7.2.2 - 8.x86_64
Installing these packages and configure the snmpd.conf file, if I access the server within HP SIM gives me the information that is shown in the first screenshot, both as informacion informacion SNMP Firmware / Software Revision .
Another thing is that I can not configure what you see in the second screenshot ny third . I get problems when authentication to enable an upgrade to HP SIM .
Let's go step by step and go solving small problems that I have . Below I attached the log from one of the machines I've tried to identify :
===================================================================================
Significant issues and overall ********* target discovery / identification
status :
Normal: The system hardware has valid data ( model , serial number, and
unique identifier) and has-been properly Identified for SIM to
manage .
Normal : System ( s ) Have Been successfully identified.
Additional results ********* ( listed for information only) :
* Starting identification process ...
* Checking Known for running web servers ...
* Checking for SNMP protocol support on system ...
Normal: The system did not respond to SNMP. Verify security settings and
community strings in Options- > Security- > Credentials -> System
Credentials
* Checking for SNMPv3 protocol support on system ...
Normal: The system did not respond to SNMPv3. Verify security settings and
v3 credentials in Options- > Security- > Credentials -> System
Credentials
* Running HP ProLiant management agent identification ...
Normal: The system does not support SNMP.
* Running SNMP -based cluster identification using common cluster
MIB ...
Normal: SNMP is not supported or disabled globally , skipping SNMP cluster
identification .
* Checking for WBEM protocol support on system ...
Minor : This system does not have any SMI- S CIMOMs installed. No storage
systems will be found on this system .
Minor : The Central Management System ( CMS) can not not communicate with the
CIMOM locally installed on the managed system using the WBEM
protocol , will try to identify identity Identification systems using Windows
the WMI Mapper as proxy , for Linux and HP- UX systems, check
credentials by going to Options- > Security- > Credentials -> System
Credentials. For Linux systems also check the provider if the HP WBEM
is installed.
* Running WBEM rules based identification ...
Minor : Identification computer system hardware can not get data from the
WBEM / WMI providers.
* Running Virtual Machine (VM ) Host (non HP Integrity VM Host)
Identification ...
Normal: The system is not a VM Host (non HP Integrity VM Host) , or WBEM
May not be specified credentials so skipping VM Identification.
* Running Storage identification ...
* Did not detect the WBEM protocol support on this system . SMI
storage identification will be skipped .
* Storage identification completed .
* Running HP NetServer identification ...
Normal: The system does not support SNMP.
* Running HP -UX SNMP identification ...
Normal: The system does not support SNMP.
* Running OA Identifier Which Will discover systems in an enclosure
enclosure if the automatic discovery option is enabled for OA ...
Normal: The system is not an Onboard Administrator , skipping automatic
discovery of systems in the enclosure .
* Running XMLReply Identifier Which Will discover systems in a
rack / enclosure if the automatic discovery option for the container
node is enabled ...
* Running iLO Identifier Which will discover the server if the
automatic server discovery option is enabled for iLO ...
Minor : The system Responds to the HTTP request but can not get the XML
output. It is usual for servers not to get the XML data.
Minor : If the http communication from CMS to target is working, but if it
is found to be slow then try increase increasing the Default connection
timeout parameter in the global settings for http protocol .
* Running p -Class Identifier ...
Normal: The system is not a p -Class so skipping p -Class identification .
* Running IPMI protocol identification ...
Normal: IPMI protocol not detected so skipping IPMI Identification.
* Running SSH Protocol identification ...
Normal: This system has SSH protocol support.
* Running SSH Identification ...
Normal: The system can be logged in using SSH protocol , you have a valid SSH
credential .
Normal: OS Name is Identified by the SSH Identification.
Normal: This Linux system is Identified by the SSH identification .
* Running Man WS- identification ...
Normal: A non -embedded operating system is detected so skipping the WS -MAN
identification .
* Running Monarch OA Identification ...
Normal: The system is not a monarch monarch OA OA so skipping
identification .
* Checking for System Management Homepage HP agents and other web ...
Normal: The System Management Homepage is not installed on this system . It
May not be supported.
* Running HP Serviceguard Identification ...
Normal: The system is not part of HP Serviceguard cluster.
* Running System Type SNMP manager ...
Normal: The system does not support SNMP.
* Running SNMP subtypes identification ...
* Resolving DNS names ...
Normal: The fully qualified domain name was successfully resolved for the
system .
* Checking if the Node is a Virtual Center ...
Normal: Node is not a Virtual Center Node
* Running Virtual Machine Management ( VMM ) Plug -in Identification ...
* Building relationships system ...
Minor : The Secure Shell key- based access authentication is not configured
on the system ( s ) .
Minor : System Management Homepage ( SMH ) is not installed or is not
responding on the system ( s ) .
* Manage Communication system Running diagnostics ...
* System finished on system identification .
===================================================================================
Greetings andverygood morning
Edu