<?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 Unable to Discover a Switch through HP SIM in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812787#M60520</link>
    <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to discover a switch in HP SIM server but it always results in the status "Completed with major errors" and the report is&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;********* Significant issues and overall target discovery/identification&lt;BR /&gt;status:&lt;BR /&gt;Minor: The name of the system could not be resolved to a fully qualified&lt;BR /&gt;domain name. For a Windows CMS, make sure that the domain name of&lt;BR /&gt;the managed system is included in the DNS suffixes in the Windows&lt;BR /&gt;Advanced TCP/IP Settings page.&lt;BR /&gt;Minor: The reverse DNS lookup using the IP address: 10.38.151.140 failed.&lt;BR /&gt;It might be that the nslookup timed out or DNS server cannot find&lt;BR /&gt;this address, or that the domain does not exist.&lt;BR /&gt;Minor: Verify that your name resolution service or the host file&lt;BR /&gt;configuration is configured properly so that your system's hostname&lt;BR /&gt;can be resolved to the fully qualified domain name.&lt;BR /&gt;Normal: The system has valid hardware data (model, serial number, and&lt;BR /&gt;unique identifier) and has been identified properly for SIM to&lt;BR /&gt;manage.&lt;BR /&gt;Major: HP SIM cannot communicate with the SNMP service on the system(s).&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;* Running WBEM rules based identification...&lt;BR /&gt;Normal: The system is not a server so skipping WBEM identification.&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;Minor: Running an ipmiutil command failed and the IPMI protocol is not&lt;BR /&gt;supported.&lt;BR /&gt;* Running SSH Protocol identification...&lt;BR /&gt;Normal: The device is a switch. Skipping check for SSH protocol.&lt;BR /&gt;* Running SSH Identification...&lt;BR /&gt;Normal: The system can be logged in using SSH protocol; has a valid SSH&lt;BR /&gt;credential.&lt;BR /&gt;Normal: OS Name is identified by the SSH Identification.&lt;BR /&gt;* Running WS-Man identification...&lt;BR /&gt;Normal: A non-embedded operating system is detected so skipping the WS-MAN&lt;BR /&gt;identification.&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;Normal: The system is not part of HP Serviceguard cluster.&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;* Checking if the Node is a Virtual Center...&lt;BR /&gt;Normal: Node is not a Virtual Center Node&lt;BR /&gt;* Checking if this system is supported by Insight Control power&lt;BR /&gt;management...&lt;BR /&gt;* Insight Control power management is not supported.&lt;BR /&gt;* Running Virtual Machine Management (VMM) Plug-in Identification...&lt;BR /&gt;* Building system relationships...&lt;BR /&gt;Minor: The Secure Shell key-based access authentication is not configured&lt;BR /&gt;on the system(s).&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;/BLOCKQUOTE&gt;&lt;P&gt;Can you please help me on getting this resolved?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
    <pubDate>Fri, 20 Nov 2015 09:09:25 GMT</pubDate>
    <dc:creator>KomalPrakash</dc:creator>
    <dc:date>2015-11-20T09:09:25Z</dc:date>
    <item>
      <title>Unable to Discover a Switch through HP SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812787#M60520</link>
      <description>&lt;P&gt;Hi,&lt;/P&gt;&lt;P&gt;I'm trying to discover a switch in HP SIM server but it always results in the status "Completed with major errors" and the report is&lt;/P&gt;&lt;BLOCKQUOTE&gt;&lt;P&gt;********* Significant issues and overall target discovery/identification&lt;BR /&gt;status:&lt;BR /&gt;Minor: The name of the system could not be resolved to a fully qualified&lt;BR /&gt;domain name. For a Windows CMS, make sure that the domain name of&lt;BR /&gt;the managed system is included in the DNS suffixes in the Windows&lt;BR /&gt;Advanced TCP/IP Settings page.&lt;BR /&gt;Minor: The reverse DNS lookup using the IP address: 10.38.151.140 failed.&lt;BR /&gt;It might be that the nslookup timed out or DNS server cannot find&lt;BR /&gt;this address, or that the domain does not exist.&lt;BR /&gt;Minor: Verify that your name resolution service or the host file&lt;BR /&gt;configuration is configured properly so that your system's hostname&lt;BR /&gt;can be resolved to the fully qualified domain name.&lt;BR /&gt;Normal: The system has valid hardware data (model, serial number, and&lt;BR /&gt;unique identifier) and has been identified properly for SIM to&lt;BR /&gt;manage.&lt;BR /&gt;Major: HP SIM cannot communicate with the SNMP service on the system(s).&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;* Running WBEM rules based identification...&lt;BR /&gt;Normal: The system is not a server so skipping WBEM identification.&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;Minor: Running an ipmiutil command failed and the IPMI protocol is not&lt;BR /&gt;supported.&lt;BR /&gt;* Running SSH Protocol identification...&lt;BR /&gt;Normal: The device is a switch. Skipping check for SSH protocol.&lt;BR /&gt;* Running SSH Identification...&lt;BR /&gt;Normal: The system can be logged in using SSH protocol; has a valid SSH&lt;BR /&gt;credential.&lt;BR /&gt;Normal: OS Name is identified by the SSH Identification.&lt;BR /&gt;* Running WS-Man identification...&lt;BR /&gt;Normal: A non-embedded operating system is detected so skipping the WS-MAN&lt;BR /&gt;identification.&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;Normal: The system is not part of HP Serviceguard cluster.&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;* Checking if the Node is a Virtual Center...&lt;BR /&gt;Normal: Node is not a Virtual Center Node&lt;BR /&gt;* Checking if this system is supported by Insight Control power&lt;BR /&gt;management...&lt;BR /&gt;* Insight Control power management is not supported.&lt;BR /&gt;* Running Virtual Machine Management (VMM) Plug-in Identification...&lt;BR /&gt;* Building system relationships...&lt;BR /&gt;Minor: The Secure Shell key-based access authentication is not configured&lt;BR /&gt;on the system(s).&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;/BLOCKQUOTE&gt;&lt;P&gt;Can you please help me on getting this resolved?&lt;/P&gt;&lt;P&gt;Thanks.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2015 09:09:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812787#M60520</guid>
      <dc:creator>KomalPrakash</dc:creator>
      <dc:date>2015-11-20T09:09:25Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Discover a Switch through HP SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812852#M60521</link>
      <description>&lt;P&gt;i'm sure there are better people to help, but i would start by setting up SNMP on that switch, and make sure SIM is configured to read that straing i.e. public, then try a rediscovery on that.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2015 14:22:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812852#M60521</guid>
      <dc:creator>cesarpegado</dc:creator>
      <dc:date>2015-11-20T14:22:59Z</dc:date>
    </item>
    <item>
      <title>Re: Unable to Discover a Switch through HP SIM</title>
      <link>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812973#M60527</link>
      <description>&lt;P&gt;I agree and see if the switch is supported? If it a HP switch? If it's not see if there is a mib file you can download and import in SIM if needed.&lt;/P&gt;</description>
      <pubDate>Fri, 20 Nov 2015 20:58:03 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/unable-to-discover-a-switch-through-hp-sim/m-p/6812973#M60527</guid>
      <dc:creator>Andrew_Haak</dc:creator>
      <dc:date>2015-11-20T20:58:03Z</dc:date>
    </item>
  </channel>
</rss>

