<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Problem discovering server running WBEM agents on HP SIM 7.5.1 in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/problem-discovering-server-running-wbem-agents-on-hp-sim-7-5-1/m-p/6848361#M60769</link>
    <description>&lt;P&gt;I've upgraded WBEM agents to version 10.40.0.0 and system management homepage to version 7.5.4.3 on a server and i can see on the system management homepage it shows WBEM is working etc, but when i do discovery of the server in HP SIM 7.5.1 I get teh following error.&lt;/P&gt;&lt;P&gt;I've logged in using the account details i've set and it loads HP SMH &amp;nbsp;up fine, that administrator account also allows me to login to the server.&lt;/P&gt;&lt;P&gt;I can telnet the server from HP SIM server on port 5989 and 5988 which is what i believe it uses for WBEM&lt;/P&gt;&lt;P&gt;So any ideas?&lt;/P&gt;&lt;P&gt;Anyone testing these new version of WBEM And SMH with HP SIM 7.5.1 as these agents only came out 1APR2016.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;********* Significant issues and overall target discovery/identification&lt;BR /&gt;status:&lt;BR /&gt;Major: The system cannot be identified properly for HP SIM to manage;&lt;BR /&gt;unable to get one or more of the following: model, serial number or&lt;BR /&gt;unique identifier (UUID). For management processors, verify the&lt;BR /&gt;system is running the latest firmware. For Linux based operating&lt;BR /&gt;systems, you must have dmidecode installed, enable the&lt;BR /&gt;PermitRootLogin and PasswordAuthentication in sshd, and use root&lt;BR /&gt;sign-in credential. For HP-UX, verify the sign-in credential. For&lt;BR /&gt;Windows, check if WMIMapper is configured correctly on the CMS and&lt;BR /&gt;verify the sign-in credential.&lt;BR /&gt;Normal: Identification status is only available for servers, workstations,&lt;BR /&gt;or desktops, where monitoring is enabled.&lt;/P&gt;&lt;P&gt;********* Additional results (listed for information only):&lt;/P&gt;&lt;P&gt;* Starting identification process...&lt;BR /&gt;* Checking for known running web servers...&lt;BR /&gt;* Checking for SNMP protocol support on system...&lt;BR /&gt;Normal: The system did not respond to SNMP. Verify security settings and&lt;BR /&gt;community strings in Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;Credentials&lt;BR /&gt;* Checking for SNMPv3 protocol support on system...&lt;BR /&gt;Normal: The system did not respond to SNMPv3. Verify security settings and&lt;BR /&gt;v3 credentials in Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;Credentials&lt;BR /&gt;* Running HP ProLiant management agent identification...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running SNMP base cluster identification using common cluster&lt;BR /&gt;MIB...&lt;BR /&gt;Normal: SNMP is not supported or globally disabled, skipping SNMP cluster&lt;BR /&gt;identification.&lt;BR /&gt;* Checking for WBEM protocol support on system...&lt;BR /&gt;Minor: This system does not have any SMI-S CIMOMs installed. No storage&lt;BR /&gt;systems will be found on this system.&lt;BR /&gt;Minor: The Central Management System (CMS) cannot communicate with the&lt;BR /&gt;CIMOM locally installed on the managed system using the WBEM&lt;BR /&gt;protocol, Identification will try to identify Windows systems using&lt;BR /&gt;the WMI Mapper as proxy; for Linux and HP-UX systems, check&lt;BR /&gt;credentials by going to Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;Credentials. For Linux systems also check if the HP WBEM provider&lt;BR /&gt;is installed.&lt;BR /&gt;Critical: There are no valid WBEM / WMI credentials for the system(s).&lt;BR /&gt;* Running WBEM rules based identification...&lt;BR /&gt;Minor: Identification cannot get computer system hardware data from the&lt;BR /&gt;WBEM / WMI providers.&lt;BR /&gt;* Running Virtual Machine (VM) Host (non HP Integrity VM Host)&lt;BR /&gt;Identification...&lt;BR /&gt;Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM&lt;BR /&gt;credentials may not be specified so skipping VM Identification.&lt;BR /&gt;* Running Storage identification...&lt;BR /&gt;* Did not detect the WBEM protocol support on this system. SMI&lt;BR /&gt;storage identification will be skipped.&lt;BR /&gt;* Storage identification completed.&lt;BR /&gt;* Running HP NetServer identification...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running HP-UX SNMP identification...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running OA Identifier which will discover systems in an enclosure&lt;BR /&gt;if the automatic enclosure discovery option for OA is enabled...&lt;BR /&gt;Normal: The system is not an Onboard Administrator, skipping automatic&lt;BR /&gt;discovery of systems in the enclosure.&lt;BR /&gt;* Running XMLReply Identifier which will discover systems in a&lt;BR /&gt;rack/enclosure if the automatic discovery option for the container&lt;BR /&gt;node is enabled...&lt;BR /&gt;* Running iLO Identifier which will discover the server if the&lt;BR /&gt;automatic server discovery option for iLO is enabled...&lt;BR /&gt;Minor: The system responds to the HTTP request but cannot get the XML&lt;BR /&gt;output. It is normal for servers not to get the XML data.&lt;BR /&gt;Minor: If the http communication from CMS to target is working, but if it&lt;BR /&gt;is found to be slow then try increasing the Default connection&lt;BR /&gt;timeout parameter for http in global protocol settings.&lt;BR /&gt;* Running p-Class Identifier...&lt;BR /&gt;Normal: The system is not a p-Class so skipping p-Class identification.&lt;BR /&gt;* Running IPMI protocol identification...&lt;BR /&gt;Normal: IPMI protocol not detected so skipping IPMI Identification.&lt;BR /&gt;* Running SSH Protocol identification...&lt;BR /&gt;Minor: The system(s) do not have Secure Shell (SSH) installed or it is not&lt;BR /&gt;running on the managed system(s).&lt;BR /&gt;* Running SSH Identification...&lt;BR /&gt;Normal: SSH Protocol is not enabled so skipping SSH Identification.&lt;BR /&gt;* Running WS-Man identification...&lt;BR /&gt;Minor: The system did not respond to WS-Management (WS-Man) request.&lt;BR /&gt;* Running Monarch OA Identification...&lt;BR /&gt;Normal: The system is not a monarch OA so skipping monarch OA&lt;BR /&gt;identification.&lt;BR /&gt;* Checking for System Management Homepage and other HP web agents...&lt;BR /&gt;Normal: The system is not a server, storage or desktop. Skipping the check&lt;BR /&gt;for System Management Homepage.&lt;BR /&gt;* Running HP Serviceguard Identification...&lt;BR /&gt;* Running SNMP System Type manager ...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running SNMP subtypes identification...&lt;BR /&gt;* Resolving DNS names...&lt;BR /&gt;Normal: The fully qualified domain name was successfully resolved for the&lt;BR /&gt;system.&lt;BR /&gt;* Checking if the Node is a Virtual Center...&lt;BR /&gt;Normal: Skipping Virtual Center Identifier.&lt;BR /&gt;* Running Virtual Machine Management (VMM) Plug-in Identification...&lt;BR /&gt;* Building system relationships...&lt;BR /&gt;Minor: System Management Homepage (SMH) is not installed or is not&lt;BR /&gt;responding on the system(s).&lt;BR /&gt;* Running system Manage Communication diagnosis...&lt;BR /&gt;* System identification finished on system.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Wed, 06 Apr 2016 11:56:21 GMT</pubDate>
    <dc:creator>cesarpegado</dc:creator>
    <dc:date>2016-04-06T11:56:21Z</dc:date>
    <item>
      <title>Problem discovering server running WBEM agents on HP SIM 7.5.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-discovering-server-running-wbem-agents-on-hp-sim-7-5-1/m-p/6848361#M60769</link>
      <description>&lt;P&gt;I've upgraded WBEM agents to version 10.40.0.0 and system management homepage to version 7.5.4.3 on a server and i can see on the system management homepage it shows WBEM is working etc, but when i do discovery of the server in HP SIM 7.5.1 I get teh following error.&lt;/P&gt;&lt;P&gt;I've logged in using the account details i've set and it loads HP SMH &amp;nbsp;up fine, that administrator account also allows me to login to the server.&lt;/P&gt;&lt;P&gt;I can telnet the server from HP SIM server on port 5989 and 5988 which is what i believe it uses for WBEM&lt;/P&gt;&lt;P&gt;So any ideas?&lt;/P&gt;&lt;P&gt;Anyone testing these new version of WBEM And SMH with HP SIM 7.5.1 as these agents only came out 1APR2016.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;********* Significant issues and overall target discovery/identification&lt;BR /&gt;status:&lt;BR /&gt;Major: The system cannot be identified properly for HP SIM to manage;&lt;BR /&gt;unable to get one or more of the following: model, serial number or&lt;BR /&gt;unique identifier (UUID). For management processors, verify the&lt;BR /&gt;system is running the latest firmware. For Linux based operating&lt;BR /&gt;systems, you must have dmidecode installed, enable the&lt;BR /&gt;PermitRootLogin and PasswordAuthentication in sshd, and use root&lt;BR /&gt;sign-in credential. For HP-UX, verify the sign-in credential. For&lt;BR /&gt;Windows, check if WMIMapper is configured correctly on the CMS and&lt;BR /&gt;verify the sign-in credential.&lt;BR /&gt;Normal: Identification status is only available for servers, workstations,&lt;BR /&gt;or desktops, where monitoring is enabled.&lt;/P&gt;&lt;P&gt;********* Additional results (listed for information only):&lt;/P&gt;&lt;P&gt;* Starting identification process...&lt;BR /&gt;* Checking for known running web servers...&lt;BR /&gt;* Checking for SNMP protocol support on system...&lt;BR /&gt;Normal: The system did not respond to SNMP. Verify security settings and&lt;BR /&gt;community strings in Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;Credentials&lt;BR /&gt;* Checking for SNMPv3 protocol support on system...&lt;BR /&gt;Normal: The system did not respond to SNMPv3. Verify security settings and&lt;BR /&gt;v3 credentials in Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;Credentials&lt;BR /&gt;* Running HP ProLiant management agent identification...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running SNMP base cluster identification using common cluster&lt;BR /&gt;MIB...&lt;BR /&gt;Normal: SNMP is not supported or globally disabled, skipping SNMP cluster&lt;BR /&gt;identification.&lt;BR /&gt;* Checking for WBEM protocol support on system...&lt;BR /&gt;Minor: This system does not have any SMI-S CIMOMs installed. No storage&lt;BR /&gt;systems will be found on this system.&lt;BR /&gt;Minor: The Central Management System (CMS) cannot communicate with the&lt;BR /&gt;CIMOM locally installed on the managed system using the WBEM&lt;BR /&gt;protocol, Identification will try to identify Windows systems using&lt;BR /&gt;the WMI Mapper as proxy; for Linux and HP-UX systems, check&lt;BR /&gt;credentials by going to Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;Credentials. For Linux systems also check if the HP WBEM provider&lt;BR /&gt;is installed.&lt;BR /&gt;Critical: There are no valid WBEM / WMI credentials for the system(s).&lt;BR /&gt;* Running WBEM rules based identification...&lt;BR /&gt;Minor: Identification cannot get computer system hardware data from the&lt;BR /&gt;WBEM / WMI providers.&lt;BR /&gt;* Running Virtual Machine (VM) Host (non HP Integrity VM Host)&lt;BR /&gt;Identification...&lt;BR /&gt;Normal: The system is not a VM Host (non HP Integrity VM Host), or WBEM&lt;BR /&gt;credentials may not be specified so skipping VM Identification.&lt;BR /&gt;* Running Storage identification...&lt;BR /&gt;* Did not detect the WBEM protocol support on this system. SMI&lt;BR /&gt;storage identification will be skipped.&lt;BR /&gt;* Storage identification completed.&lt;BR /&gt;* Running HP NetServer identification...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running HP-UX SNMP identification...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running OA Identifier which will discover systems in an enclosure&lt;BR /&gt;if the automatic enclosure discovery option for OA is enabled...&lt;BR /&gt;Normal: The system is not an Onboard Administrator, skipping automatic&lt;BR /&gt;discovery of systems in the enclosure.&lt;BR /&gt;* Running XMLReply Identifier which will discover systems in a&lt;BR /&gt;rack/enclosure if the automatic discovery option for the container&lt;BR /&gt;node is enabled...&lt;BR /&gt;* Running iLO Identifier which will discover the server if the&lt;BR /&gt;automatic server discovery option for iLO is enabled...&lt;BR /&gt;Minor: The system responds to the HTTP request but cannot get the XML&lt;BR /&gt;output. It is normal for servers not to get the XML data.&lt;BR /&gt;Minor: If the http communication from CMS to target is working, but if it&lt;BR /&gt;is found to be slow then try increasing the Default connection&lt;BR /&gt;timeout parameter for http in global protocol settings.&lt;BR /&gt;* Running p-Class Identifier...&lt;BR /&gt;Normal: The system is not a p-Class so skipping p-Class identification.&lt;BR /&gt;* Running IPMI protocol identification...&lt;BR /&gt;Normal: IPMI protocol not detected so skipping IPMI Identification.&lt;BR /&gt;* Running SSH Protocol identification...&lt;BR /&gt;Minor: The system(s) do not have Secure Shell (SSH) installed or it is not&lt;BR /&gt;running on the managed system(s).&lt;BR /&gt;* Running SSH Identification...&lt;BR /&gt;Normal: SSH Protocol is not enabled so skipping SSH Identification.&lt;BR /&gt;* Running WS-Man identification...&lt;BR /&gt;Minor: The system did not respond to WS-Management (WS-Man) request.&lt;BR /&gt;* Running Monarch OA Identification...&lt;BR /&gt;Normal: The system is not a monarch OA so skipping monarch OA&lt;BR /&gt;identification.&lt;BR /&gt;* Checking for System Management Homepage and other HP web agents...&lt;BR /&gt;Normal: The system is not a server, storage or desktop. Skipping the check&lt;BR /&gt;for System Management Homepage.&lt;BR /&gt;* Running HP Serviceguard Identification...&lt;BR /&gt;* Running SNMP System Type manager ...&lt;BR /&gt;Normal: The system does not support SNMP.&lt;BR /&gt;* Running SNMP subtypes identification...&lt;BR /&gt;* Resolving DNS names...&lt;BR /&gt;Normal: The fully qualified domain name was successfully resolved for the&lt;BR /&gt;system.&lt;BR /&gt;* Checking if the Node is a Virtual Center...&lt;BR /&gt;Normal: Skipping Virtual Center Identifier.&lt;BR /&gt;* Running Virtual Machine Management (VMM) Plug-in Identification...&lt;BR /&gt;* Building system relationships...&lt;BR /&gt;Minor: System Management Homepage (SMH) is not installed or is not&lt;BR /&gt;responding on the system(s).&lt;BR /&gt;* Running system Manage Communication diagnosis...&lt;BR /&gt;* System identification finished on system.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 06 Apr 2016 11:56:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-discovering-server-running-wbem-agents-on-hp-sim-7-5-1/m-p/6848361#M60769</guid>
      <dc:creator>cesarpegado</dc:creator>
      <dc:date>2016-04-06T11:56:21Z</dc:date>
    </item>
    <item>
      <title>Re: Problem discovering server running WBEM agents on HP SIM 7.5.1</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-discovering-server-running-wbem-agents-on-hp-sim-7-5-1/m-p/6849502#M60783</link>
      <description>&lt;P&gt;Hello,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You did set the discovery credentials in de discovery job or in the general setting in SIM right ?&lt;/P&gt;&lt;P&gt;THe log shows it has no valid credentials, this should be something like domain\account and the a password in the WBEM part, so not only in the login credentials you see when typing the credentials. Als click the Show advanced protocol credentials and click on the WBEM/WMI tab.&lt;/P&gt;</description>
      <pubDate>Mon, 11 Apr 2016 08:21:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-discovering-server-running-wbem-agents-on-hp-sim-7-5-1/m-p/6849502#M60783</guid>
      <dc:creator>Andrew_Haak</dc:creator>
      <dc:date>2016-04-11T08:21:43Z</dc:date>
    </item>
  </channel>
</rss>

