<?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: I cannot apply the Insight Dynamics License to a ESX Server 3.5 in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213735#M51644</link>
    <description>Done.</description>
    <pubDate>Wed, 16 Dec 2009 07:33:51 GMT</pubDate>
    <dc:creator>davesec</dc:creator>
    <dc:date>2009-12-16T07:33:51Z</dc:date>
    <item>
      <title>I cannot apply the Insight Dynamics License to a ESX Server 3.5</title>
      <link>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213732#M51641</link>
      <description>I'd like to integrate my ESX Server (BL460) into VSE. Do do so I tried to apply the Insight Dynamics License to that blade. But this can not be acconplished because of the error:&lt;BR /&gt;&lt;BR /&gt;==============================================&lt;BR /&gt;This tool cannot run on tstesx1 as it does not pass the conditions required for running it.&lt;BR /&gt;&lt;BR /&gt;Device Type must equal Server and Device Sub-type must contain ProLiant&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;The properties that tstesx1 has for the failing conditions :&lt;BR /&gt;Device Sub-type: [Blade, c-Class, VMHost, VMWARE_ESX_VMHost]&lt;BR /&gt;Device Type: Server.&lt;BR /&gt;=============================================&lt;BR /&gt;&lt;BR /&gt;What i'm doing wrong??</description>
      <pubDate>Thu, 10 Dec 2009 16:02:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213732#M51641</guid>
      <dc:creator>davesec</dc:creator>
      <dc:date>2009-12-10T16:02:21Z</dc:date>
    </item>
    <item>
      <title>Re: I cannot apply the Insight Dynamics License to a ESX Server 3.5</title>
      <link>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213733#M51642</link>
      <description>Hi&lt;BR /&gt;&lt;BR /&gt;Surely nothing ;-) it must be the computer !&lt;BR /&gt;&lt;BR /&gt;One can reasonnably think about an identification issue here since properties are  not correct.&lt;BR /&gt;The two most important protocols responsible for bad identifications are SNMP and WBEM.&lt;BR /&gt;SNMP: check the snmpd.conf on the esx server located in /etc/snmp/ be sure that trap destinations are correct, snmp community strings should be checked as well.&lt;BR /&gt;&lt;BR /&gt;WBEM:&lt;BR /&gt;be sure that a user had been set up in the system protocol settings for the machine.&lt;BR /&gt;be sure that the pegasus service (wbem layer)is runnning properly on the esx server (retsarting it sometimes fixes identification issues : service pegasus restart followed by a hp sim identification)&lt;BR /&gt;be sure that the vmm agent service is runniong on the esx : restart using service hpvmmsvccnt restart or use the hp sim web ui to restqrt the vmm agent&lt;BR /&gt;&lt;BR /&gt;You can also use the CRA configure and repair agents to fix these communications issues.&lt;BR /&gt;&lt;BR /&gt;Try these different options, I would start with the wbem part personnally ;-)&lt;BR /&gt;&lt;BR /&gt;Once the server is properly identified , the licensing will go fine.&lt;BR /&gt;&lt;BR /&gt;hope it helps&lt;BR /&gt;&lt;BR /&gt;fred</description>
      <pubDate>Thu, 10 Dec 2009 16:48:23 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213733#M51642</guid>
      <dc:creator>fred Passeron</dc:creator>
      <dc:date>2009-12-10T16:48:23Z</dc:date>
    </item>
    <item>
      <title>Re: I cannot apply the Insight Dynamics License to a ESX Server 3.5</title>
      <link>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213734#M51643</link>
      <description>That was the right rirection. I had to remove all hpagent rpms on the ESX server with &lt;BR /&gt;&lt;BR /&gt; # rpm -e package&lt;BR /&gt;&lt;BR /&gt;And reinstall it over Configure or Repaire Agent.&lt;BR /&gt;&lt;BR /&gt;Case Closed.</description>
      <pubDate>Wed, 16 Dec 2009 07:32:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213734#M51643</guid>
      <dc:creator>davesec</dc:creator>
      <dc:date>2009-12-16T07:32:40Z</dc:date>
    </item>
    <item>
      <title>Re: I cannot apply the Insight Dynamics License to a ESX Server 3.5</title>
      <link>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213735#M51644</link>
      <description>Done.</description>
      <pubDate>Wed, 16 Dec 2009 07:33:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/i-cannot-apply-the-insight-dynamics-license-to-a-esx-server-3-5/m-p/5213735#M51644</guid>
      <dc:creator>davesec</dc:creator>
      <dc:date>2009-12-16T07:33:51Z</dc:date>
    </item>
  </channel>
</rss>

