Hi
Atwologsattachedbelowthelogfor thefirstidentificationof anokserverlogand the otherfor a non-serverok.
FIRST LOG
********* Significant issues and overall target discovery/identification status: Normal: The system has valid hardware data (model, serial number, and unique identifier) and has been identified properly for SIM to manage. Normal: System(s) have been successfully identified.
********* Additional results (listed for information only):
* Starting identification process... * Checking for known running web servers... * Checking for SNMP protocol support on system... Normal: The system responded to an SNMP request; it supports SNMP Protocol and has a valid read community string. * 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: Identification can get the system information from the ProLiant SNMP Foundation agents for servers. * Running SNMP base cluster identification using common cluster MIB... Normal: This system does not have the common cluster MIBs support. * 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) cannot communicate with the CIMOM locally installed on the managed system using the WBEM protocol, Identification will try to identify Windows systems using 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 if the HP WBEM provider is installed. * Running WBEM rules based identification... Minor: Identification cannot get computer system hardware 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 credentials may not be specified 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: System supports the NetServer SNMP agent, adding system type. * Running HP-UX SNMP identification... Normal: System does not have the HP-UX SNMP agents installed. * Running OA Identifier which will discover systems in an enclosure if the automatic enclosure discovery option for OA is enabled... Normal: A non-embedded operating system is detected so skipping the OA identification. * Running XMLReply Identifier which will discover systems in a rack/enclosure if the automatic discovery option for the container node is enabled... Normal: A non-embedded operating system is detected so skipping the Management processor identification. * Running iLO Identifier which will discover the server if the automatic server discovery option for iLO is enabled... Normal: A non-embedded operating system is detected so skipping the ILO identification. * Running p-Class Identifier... Normal: The system is not a p-Class so skipping p-Class identification. * Running IPMI protocol identification... Normal: Skipping IPMI discovery in favor of WBEM/SNMP discovery. * Running SSH Protocol identification... Normal: This system has SSH protocol support. * Running SSH Identification... Normal: The system can be logged in using SSH protocol; has a valid SSH credential. Normal: OS Name is identified by the SSH Identification. Normal: This Linux system is identified by the SSH identification. * Running WS-Man 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 OA so skipping monarch OA identification. * Checking for System Management Homepage and other HP web agents... Normal: System Management Homepage (SMH) is installed or is responding on the system(s). * Running HP Serviceguard Identification... Normal: The system is not part of HP Serviceguard cluster. * Running SNMP System Type manager ... Normal: No matching SNMP System Type Manager rule for sysObjID was found. * Running SNMP subtypes identification... * No additional subtype(s) found from SNMP. * 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 system relationships... Normal: SSH is configured on this system. Major: In order to access Secure Sockets Layer (SSL) based tools such as System Management Homepage and Version Control Repository Manager on remote systems without performing an additional sign-in, you need to establish trust between the Central Management Server (CMS) and the managed system(s). * Running system Manage Communication diagnosis... * System identification finished on system.
********************************************************************************
********************************************************************************
SECOND LOG
********* Significant issues and overall target discovery/identification status: Normal: The system has valid hardware data (model, serial number, and unique identifier) and has been identified properly for SIM to manage. Normal: System(s) have been successfully identified.
********* Additional results (listed for information only):
* Starting identification process... * Checking for known 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 base cluster identification using common cluster MIB... Normal: SNMP is not supported or globally disabled, 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) cannot communicate with the CIMOM locally installed on the managed system using the WBEM protocol, Identification will try to identify Windows systems using 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 if the HP WBEM provider is installed. * Running WBEM rules based identification... Minor: Identification cannot get computer system hardware 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 credentials may not be specified 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 if the automatic enclosure discovery option for OA is enabled... 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 for iLO is enabled... Minor: The system responds to the HTTP request but cannot get the XML output. It is normal 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 increasing the Default connection timeout parameter for http in global protocol settings. * 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; has a valid SSH credential. Normal: OS Name is identified by the SSH Identification. Normal: This Linux system is identified by the SSH identification. * Running WS-Man 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 OA so skipping monarch OA identification. * Checking for System Management Homepage and other HP web agents... 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 SNMP System Type 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 system relationships... 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). * Running system Manage Communication diagnosis... * System identification finished on system.
I understandthat I needto installpackageson a serverthat is notok.Canbethese packages!?
hpsmh-7.2.2-8.x86_64
hp-health-9.40-1602.44.rhel6.x86_64
hp-snmp-agents-9.40-2506.37.rhel6.x86_64
hp-smh-templates-9.4.0-1327.37.noarch
In this case, I'll haveto doa display ofinstallation ofthese packages onother serversI wantto monitor,andeachcorrectlyconfiguresmnpd.confsnmpd.conftakingas an example theserverisok.
On the other hand,when you refer to performthe trustmanually on server VCRM, in what part ofHPSIMI cannotconfigure it?I can notsee it.
Thank you so much