<?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 Re: Problem running tools on HPUX client. in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550884#M55929</link>
    <description>Do the necessary subscribtion entries exist on the HP-UX system? (evweb subscribe -b external -L)&lt;BR /&gt;Regards, Werner</description>
    <pubDate>Thu, 17 Dec 2009 05:32:32 GMT</pubDate>
    <dc:creator>ITRC Test-CH</dc:creator>
    <dc:date>2009-12-17T05:32:32Z</dc:date>
    <item>
      <title>Problem running tools on HPUX client.</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550883#M55928</link>
      <description>&lt;P&gt;Hi,&lt;BR /&gt;&lt;BR /&gt;I am having trouble configuring hp-ux clients on the SIM CMS. I have installed SSH, OpenSSL and WBEMServices on the clients. I then go into “Configure-&amp;gt;Configure or Repair Agents” on the SIM and configure WBEM, SNMP, SSH and Set Trust by Certificate. This all appears to work, however when I go into “Manage Communications” it shows that I have successfully identified the client, the HP SIM can receive events, but I cannot run tools. Despite the fact it says we can receive events, I send a test event but we don’t receive it. I have also run “Identify System” and it outputs the following:&lt;BR /&gt;&lt;BR /&gt;Starting identification process...&lt;BR /&gt;Checking for known running web servers.&lt;BR /&gt;Checking for System Management Home Page and other HP web agents.&lt;BR /&gt;Received a response from the system management homepage, this system supports SM&lt;BR /&gt;H.&lt;BR /&gt;Checking for WBEM support on system.&lt;BR /&gt;This system has WBEM protocol support&lt;BR /&gt;This system has at least one SMI-S CIMOM installed&lt;BR /&gt;This system has a server CIMOM installed&lt;BR /&gt;Running WBEM rules based identification.&lt;BR /&gt;Got ComputerSystem WBEM/WMI data from the system&lt;BR /&gt;Running VM Identification.&lt;BR /&gt;The system is not a VM Host, or WBEM credentials may not be specified, skipping &lt;BR /&gt;VM Identification&lt;BR /&gt;Running WS-Man identification.&lt;BR /&gt;The system did not respond to WS-Management, verify credentials.&lt;BR /&gt;Checking for SNMP support on system.&lt;BR /&gt;The system responded to a SNMP request, it supports SNMP.&lt;BR /&gt;Running SNMP base Cluster identification using common cluster MIB.&lt;BR /&gt;This was not a system with the common cluster MIBs supported.&lt;BR /&gt;Running HP ProLiant management agent identification&lt;BR /&gt;System does not have the SNMP ProLiant Server (foundation) agents installed.&lt;BR /&gt;Running HP NetServer identification.&lt;BR /&gt;System supports the NetServer SNMP agent, adding system type&lt;BR /&gt;Running HP-UX SNMP identification.&lt;BR /&gt;System has the HPUX SNMP agents installed, adding system type.&lt;BR /&gt;Running SNMP System Type Manager identification.&lt;BR /&gt;No matching SNMP System Type Manager rule was found.&lt;BR /&gt;Checking for DMI protocol support.&lt;BR /&gt;DMI is globally disabled, skipping DMI identification.&lt;BR /&gt;Running DMI System Type Manager identification.&lt;BR /&gt;DMI is globally disabled, skipping DMI identification.&lt;BR /&gt;Running HP-UX DMI identification.&lt;BR /&gt;DMI is globally disabled, skipping DMI identification.&lt;BR /&gt;Running HP/Compaq Desktop identification.&lt;BR /&gt;DMI is globally disabled, skipping DMI identification.&lt;BR /&gt;Running HP DMI Desktop identification.&lt;BR /&gt;DMI is globally disabled, skipping DMI identification.&lt;BR /&gt;Running Generic DMI identification.&lt;BR /&gt;DMI is globally disabled, skipping DMI identification.&lt;BR /&gt;Running SSH Protocol identification.&lt;BR /&gt;The system supports SSH protocol&lt;BR /&gt;Running SSH Identification.&lt;BR /&gt;This system passed the ssh authentication; it has a valid ssh credential&lt;BR /&gt;OS Name is identified by other identifier; continue to run other commands&lt;BR /&gt;Running Storage identification.&lt;BR /&gt;Running HP Service Guard Identification.&lt;BR /&gt;The system is not part of HP Service Guard cluster&lt;BR /&gt;Running SNMP Subtypes identification&lt;BR /&gt;No additional subtypes found from SNMP&lt;BR /&gt;Create bare-metal device nodes if OA is discovered with "Automatic Device discov&lt;BR /&gt;ery" option enabled.&lt;BR /&gt;Create bare-metal server node if ILO is discovered with "Automatic Server discov&lt;BR /&gt;ery" option enabled.&lt;BR /&gt;Running VM identification.&lt;BR /&gt;VMM Integration is not enabled, skipping VM Identification&lt;BR /&gt;Building system relationships.&lt;BR /&gt;Running limited data collection for common attribute.&lt;BR /&gt;The SSH is not configured on this system&lt;BR /&gt;SMH trust status is false.&lt;BR /&gt;Running node communication diagnosis&lt;BR /&gt;System identification done with this system.&lt;BR /&gt;&lt;BR /&gt;The odd thing is it states in the above that it has passed the SSH authentication, but then 4 lines from the bottom it states that SSH is not configured, this is despite the fact the SSH appears to be working on the remote client. Is there anything else I need to do on the CMS to get this working?&lt;BR /&gt;&lt;BR /&gt;The client is an RX2660 running 11.31 and the CMS is running under Windows.&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;&amp;nbsp;&lt;/P&gt;
&lt;P&gt;P.S. this thread has been moved&amp;nbsp;from Insight Remote Support &amp;gt; general to ITRC HP Systems Insight Manager Forum - HP Forums moderator&lt;/P&gt;</description>
      <pubDate>Mon, 14 Jan 2013 04:04:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550883#M55928</guid>
      <dc:creator>Neville Lawrence</dc:creator>
      <dc:date>2013-01-14T04:04:35Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running tools on HPUX client.</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550884#M55929</link>
      <description>Do the necessary subscribtion entries exist on the HP-UX system? (evweb subscribe -b external -L)&lt;BR /&gt;Regards, Werner</description>
      <pubDate>Thu, 17 Dec 2009 05:32:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550884#M55929</guid>
      <dc:creator>ITRC Test-CH</dc:creator>
      <dc:date>2009-12-17T05:32:32Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running tools on HPUX client.</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550885#M55930</link>
      <description>Neville,&lt;BR /&gt;&lt;BR /&gt;In addition to checking for the external Alert Indication subscriptions (actually you should do this before checking) open SEA and check if WEBES lacks information about the HP-UX endpoint. If information is missing WEBES highlights the HP-UX host name in orange. Also any missing data on the managed entity page will likewise be highlighted in orange. Fix any missing data by entering it to the HP-UX endpoint's HP SIM system properties page.&lt;BR /&gt;&lt;BR /&gt;If the subscription required for Remote Device Monitoring (RDM) does not show up re-start the DESTA service on the CMS. If that fails restart the CIM-server on HP-UX endpoint with the following:&lt;BR /&gt;&lt;BR /&gt;ps -ef | grep -i cimserver (to see if it is running)&lt;BR /&gt;cimserver -s (to stop)&lt;BR /&gt;cimserver (to start)&lt;BR /&gt;&lt;BR /&gt;All of the above steps generally fix the failure to receive test events problem. Just perform them in order and check after each step to see if the subscription appears.&lt;BR /&gt;&lt;BR /&gt;Take care,&lt;BR /&gt;frank&lt;BR /&gt;</description>
      <pubDate>Thu, 17 Dec 2009 13:10:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550885#M55930</guid>
      <dc:creator>Frank Alden Smith</dc:creator>
      <dc:date>2009-12-17T13:10:57Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running tools on HPUX client.</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550886#M55931</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;Forgive my ignorance, but what is SEA?&lt;BR /&gt;&lt;BR /&gt;Thanks</description>
      <pubDate>Fri, 18 Dec 2009 11:11:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550886#M55931</guid>
      <dc:creator>Neville Lawrence</dc:creator>
      <dc:date>2009-12-18T11:11:56Z</dc:date>
    </item>
    <item>
      <title>Re: Problem running tools on HPUX client.</title>
      <link>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550887#M55932</link>
      <description>Neville,&lt;BR /&gt;&lt;BR /&gt;Neville,&lt;BR /&gt;&lt;BR /&gt;Sorry for using an undefined acronym! SEA is the System Event Analyzer in essence it is the WEBES browser interface, which is installed on the Central Management Server (CMS) when you install Insight Remote Support Advanced (RSA). You access it by following this path: Start &amp;gt; All Programs &amp;gt; Hewlett-Packard Service Tools &amp;gt; System Event Analyzer &amp;gt; System Event Analyzer. You can use the CMS Administrator credentials to log in to SEA.&lt;BR /&gt;&lt;BR /&gt;Take care,&lt;BR /&gt;Frank&lt;BR /&gt;</description>
      <pubDate>Fri, 18 Dec 2009 11:48:35 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/problem-running-tools-on-hpux-client/m-p/4550887#M55932</guid>
      <dc:creator>Frank Alden Smith</dc:creator>
      <dc:date>2009-12-18T11:48:35Z</dc:date>
    </item>
  </channel>
</rss>

