<?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: HPSIM communication Issue in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295515#M57766</link>
    <description>Hello there,&lt;BR /&gt;&lt;BR /&gt;The above is correct, you could also check if the firewall is configured to allow snmp and if snmp it self is installed.&lt;BR /&gt;&lt;BR /&gt;Type service snmpd status to check this.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
    <pubDate>Sat, 18 Jan 2014 18:56:18 GMT</pubDate>
    <dc:creator>Andrew_Haak</dc:creator>
    <dc:date>2014-01-18T18:56:18Z</dc:date>
    <item>
      <title>HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295179#M57761</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I am getting issue with HP SIM.&lt;BR /&gt;I am not able to get data from a server.&lt;/P&gt;&lt;P&gt;SMH is working fine on the server&lt;BR /&gt;SIM server name has been added in SNMP settings&lt;BR /&gt;&lt;BR /&gt;Please find the below logs:&lt;BR /&gt;&lt;BR /&gt;&lt;/P&gt;&lt;P&gt;********* Significant issues and overall target discovery/identification&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; status:&lt;BR /&gt;Major:&amp;nbsp;&amp;nbsp;&amp;nbsp; The system cannot be identified properly for HP SIM to manage;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unable to get one or more of the following: model, serial number or&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; unique identifier (UUID). For management processors, verify the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; system is running the latest firmware. For Linux based operating&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; systems, you must have dmidecode installed, enable the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; PermitRootLogin and PasswordAuthentication in sshd, and use root&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; sign-in credential. For HP-UX, verify the sign-in credential. For&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Windows, check if WMIMapper is configured correctly on the CMS and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; verify the sign-in credential.&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; Identification status is only available for servers, workstations,&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; or desktops, where monitoring is enabled.&lt;BR /&gt;&lt;BR /&gt;********* Additional results (listed for information only):&lt;BR /&gt;&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Starting identification process...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Checking for known running web servers...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Checking for SNMP protocol support on system...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system did not respond to SNMP. Verify security settings and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; community strings in Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credentials&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running HP ProLiant management agent identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system does not support SNMP.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running SNMP base cluster identification using common cluster&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; MIB...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; SNMP is not supported or globally disabled, skipping SNMP cluster&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; identification.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Checking for WBEM protocol support on system...&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; This system does not have any SMI-S CIMOMs installed. No storage&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; systems will be found on this system.&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; The Central Management System (CMS) cannot communicate with the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; CIMOM locally installed on the managed system using the WBEM&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; protocol, Identification will try to identify Windows systems using&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; the WMI Mapper as proxy; for Linux and HP-UX systems, check&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; credentials by going to Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credentials. For Linux systems also check if the HP WBEM provider&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; is installed.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running WBEM rules based identification...&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; Identification cannot get computer system hardware data from the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; WBEM / WMI providers.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running Virtual Machine (VM) Host (non HP Integrity VM Host)&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system is not a VM Host (non HP Integrity VM Host), or WBEM&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; credentials may not be specified so skipping VM Identification.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running Storage identification...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Did not detect the WBEM protocol support on this system. SMI&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; storage identification will be skipped.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Storage identification completed.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running HP NetServer identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system does not support SNMP.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running HP-UX SNMP identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system does not support SNMP.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running OA Identifier which will discover systems in an enclosure&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; if the automatic enclosure discovery option for OA is enabled...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system is not an Onboard Administrator, skipping automatic&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; discovery of systems in the enclosure.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running XMLReply Identifier which will discover systems in a&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; rack/enclosure if the automatic discovery option for the container&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; node is enabled...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running iLO Identifier which will discover the server if the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; automatic server discovery option for iLO is enabled...&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; The system responds to the HTTP request but cannot get the XML&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; output. It is normal for servers not to get the XML data.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running p-Class Identifier...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system is not a p-Class so skipping p-Class identification.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running IPMI protocol identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; IPMI protocol not detected so skipping IPMI Identification.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running SSH Protocol identification...&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; The system(s) do not have Secure Shell (SSH) installed or it is not&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; running on the managed system(s).&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running SSH Identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; SSH Protocol is not enabled so skipping SSH Identification.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running WS-Man identification...&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; The system did not respond to WS-Management (WS-Man) request.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running Monarch OA Identification...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system is not a monarch OA so skipping monarch OA&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; identification.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Checking for System Management Homepage and other HP web agents...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system is not a server, storage or desktop. Skipping the check&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; for System Management Homepage.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running HP Serviceguard Identification...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running SNMP System Type manager ...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The system does not support SNMP.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running SNMP subtypes identification...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Resolving DNS names...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; The fully qualified domain name was successfully resolved for the&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; system.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Checking if the Node is a Virtual Center...&lt;BR /&gt;Normal:&amp;nbsp;&amp;nbsp; Skipping MxVirtualCenter Identifier.&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running Virtual Machine Management (VMM) Plug-in Identification...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Building system relationships...&lt;BR /&gt;Minor:&amp;nbsp;&amp;nbsp;&amp;nbsp; System Management Homepage (SMH) is not installed or is not&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; responding on the system(s).&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running system Manage Communication diagnosis...&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * System identification finished on system.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Kindly Help.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2013 12:56:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295179#M57761</guid>
      <dc:creator>Sands15</dc:creator>
      <dc:date>2013-12-05T12:56:32Z</dc:date>
    </item>
    <item>
      <title>Re: HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295485#M57764</link>
      <description>&lt;P&gt;Normal:&amp;nbsp;&amp;nbsp; The system did not respond to SNMP. Verify security settings and&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; community strings in Options-&amp;gt;Security-&amp;gt;Credentials-&amp;gt;System&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; Credentials&lt;BR /&gt;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp;&amp;nbsp; * Running HP ProLiant management agent identification...&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This looks like your community string is not set correct or your SIM Server name can not be resolved from your managed system .&lt;/P&gt;</description>
      <pubDate>Thu, 05 Dec 2013 17:08:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295485#M57764</guid>
      <dc:creator>BPE</dc:creator>
      <dc:date>2013-12-05T17:08:19Z</dc:date>
    </item>
    <item>
      <title>Re: HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295515#M57766</link>
      <description>Hello there,&lt;BR /&gt;&lt;BR /&gt;The above is correct, you could also check if the firewall is configured to allow snmp and if snmp it self is installed.&lt;BR /&gt;&lt;BR /&gt;Type service snmpd status to check this.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Sat, 18 Jan 2014 18:56:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6295515#M57766</guid>
      <dc:creator>Andrew_Haak</dc:creator>
      <dc:date>2014-01-18T18:56:18Z</dc:date>
    </item>
    <item>
      <title>Re: HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6334841#M58016</link>
      <description>&lt;P&gt;Kindly ellborate more about "service snaps statu"&lt;/P&gt;</description>
      <pubDate>Tue, 14 Jan 2014 21:07:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6334841#M58016</guid>
      <dc:creator>Sands15</dc:creator>
      <dc:date>2014-01-14T21:07:42Z</dc:date>
    </item>
    <item>
      <title>Re: HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6340277#M58062</link>
      <description>Hello there,&lt;BR /&gt;&lt;BR /&gt;Sorry for the typo i ment service snmpd status&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Fri, 17 Jan 2014 20:39:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6340277#M58062</guid>
      <dc:creator>Andrew_Haak</dc:creator>
      <dc:date>2014-01-17T20:39:21Z</dc:date>
    </item>
    <item>
      <title>Re: HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6340373#M58066</link>
      <description>&lt;P&gt;&amp;gt;Sorry for the typo i ment service snmpd status&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;You can edit your post with "Post Options &amp;gt; Edit Reply".&lt;/P&gt;</description>
      <pubDate>Fri, 17 Jan 2014 22:41:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6340373#M58066</guid>
      <dc:creator>Dennis Handly</dc:creator>
      <dc:date>2014-01-17T22:41:47Z</dc:date>
    </item>
    <item>
      <title>Re: HPSIM communication Issue</title>
      <link>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6340711#M58069</link>
      <description>Hello Dennis,&lt;BR /&gt;&lt;BR /&gt;I normaly edit my typo's when i see them in time. This time overlooked my error, but thanks for the hint i corrected the original message.&lt;BR /&gt;&lt;BR /&gt;Kind regards,&lt;BR /&gt;&lt;BR /&gt;Andrew</description>
      <pubDate>Sat, 18 Jan 2014 19:00:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/hpsim-communication-issue/m-p/6340711#M58069</guid>
      <dc:creator>Andrew_Haak</dc:creator>
      <dc:date>2014-01-18T19:00:17Z</dc:date>
    </item>
  </channel>
</rss>

