<?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: PMP in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/pmp/m-p/4290890#M34925</link>
    <description>I have the similar issue with BL 30p.&lt;BR /&gt;&lt;BR /&gt;I have found in intranet (not remember where) next hints:&lt;BR /&gt;&lt;BR /&gt;For licensing &amp;amp; monitoring, PMP is sensitive to server details, such as&lt;BR /&gt;OS name, OS version, Management Agent version &amp;amp; so on, so you might want&lt;BR /&gt;to verify these values against the PMP support matrix. Some of the&lt;BR /&gt;probable causes of getting "unsupported ..." are:&lt;BR /&gt;&lt;BR /&gt;- For a given server, discovery using WBEM might give version no.&lt;BR /&gt;as 5.2.*, whereas the same field is populated as just "5.2", when&lt;BR /&gt;discovered using SNMP. In that case, you can edit this field to make it&lt;BR /&gt;"5.2", as required by PMP.&lt;BR /&gt;&lt;BR /&gt;- Similarly WBEM discovery populated OS name with extra (R), which&lt;BR /&gt;is not required by PMP. So, after referring support matrix, you may want&lt;BR /&gt;to edit that field as per the supported OS name.&lt;BR /&gt;&lt;BR /&gt;You can edit these fields &amp;amp; same will be reflected in SIM database, but&lt;BR /&gt;PMP database may store the older values, so you can either restart PMP&lt;BR /&gt;service (HP Perfromance Management Pack) to refresh its database OR use&lt;BR /&gt;a 'Update Server List' button, available on 'Monitoring Administration'&lt;BR /&gt;page.&lt;BR /&gt;&lt;BR /&gt;The easy way to do this exercise, is to disable WBEM during initial&lt;BR /&gt;discovery of all monitored servers, license them in PMP &amp;amp; set them for&lt;BR /&gt;monitoring AND if required, enable WBEM &amp;amp; do the rediscovery.&lt;BR /&gt;&lt;BR /&gt;Good luck</description>
    <pubDate>Thu, 30 Oct 2008 14:26:09 GMT</pubDate>
    <dc:creator>Roman Belsky</dc:creator>
    <dc:date>2008-10-30T14:26:09Z</dc:date>
    <item>
      <title>PMP</title>
      <link>https://community.hpe.com/t5/server-management-systems/pmp/m-p/4290889#M34924</link>
      <description>&lt;BR /&gt; Oct 16, 2008 14:54:40 GMT        &lt;BR /&gt;&lt;BR /&gt;--------------------------------------------------------------------------------&lt;BR /&gt;I have just installed HP SIM 5.2 and PMP 4.7. when i try and run the PMP it is saying that the servers are ready for licensing. i have run the license manager and assign the licenses but it is saying non used. Anyone any ideas. The servers are a DL385g2 and a DL320 g5 running windows server 2003 am i doing something stupid  &lt;BR /&gt; they also come up with unsupported config but as far as i can see they are on the ok list</description>
      <pubDate>Tue, 21 Oct 2008 07:48:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/pmp/m-p/4290889#M34924</guid>
      <dc:creator>Alex Whittaker</dc:creator>
      <dc:date>2008-10-21T07:48:46Z</dc:date>
    </item>
    <item>
      <title>Re: PMP</title>
      <link>https://community.hpe.com/t5/server-management-systems/pmp/m-p/4290890#M34925</link>
      <description>I have the similar issue with BL 30p.&lt;BR /&gt;&lt;BR /&gt;I have found in intranet (not remember where) next hints:&lt;BR /&gt;&lt;BR /&gt;For licensing &amp;amp; monitoring, PMP is sensitive to server details, such as&lt;BR /&gt;OS name, OS version, Management Agent version &amp;amp; so on, so you might want&lt;BR /&gt;to verify these values against the PMP support matrix. Some of the&lt;BR /&gt;probable causes of getting "unsupported ..." are:&lt;BR /&gt;&lt;BR /&gt;- For a given server, discovery using WBEM might give version no.&lt;BR /&gt;as 5.2.*, whereas the same field is populated as just "5.2", when&lt;BR /&gt;discovered using SNMP. In that case, you can edit this field to make it&lt;BR /&gt;"5.2", as required by PMP.&lt;BR /&gt;&lt;BR /&gt;- Similarly WBEM discovery populated OS name with extra (R), which&lt;BR /&gt;is not required by PMP. So, after referring support matrix, you may want&lt;BR /&gt;to edit that field as per the supported OS name.&lt;BR /&gt;&lt;BR /&gt;You can edit these fields &amp;amp; same will be reflected in SIM database, but&lt;BR /&gt;PMP database may store the older values, so you can either restart PMP&lt;BR /&gt;service (HP Perfromance Management Pack) to refresh its database OR use&lt;BR /&gt;a 'Update Server List' button, available on 'Monitoring Administration'&lt;BR /&gt;page.&lt;BR /&gt;&lt;BR /&gt;The easy way to do this exercise, is to disable WBEM during initial&lt;BR /&gt;discovery of all monitored servers, license them in PMP &amp;amp; set them for&lt;BR /&gt;monitoring AND if required, enable WBEM &amp;amp; do the rediscovery.&lt;BR /&gt;&lt;BR /&gt;Good luck</description>
      <pubDate>Thu, 30 Oct 2008 14:26:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/pmp/m-p/4290890#M34925</guid>
      <dc:creator>Roman Belsky</dc:creator>
      <dc:date>2008-10-30T14:26:09Z</dc:date>
    </item>
  </channel>
</rss>

