<?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: WBEM and Data Collection in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083613#M49703</link>
    <description>Current management agents for your ProLiant servers are exclusively SNMP.  You are gaining nothing by enabling WBEM.</description>
    <pubDate>Tue, 11 Dec 2007 00:44:17 GMT</pubDate>
    <dc:creator>David Claypool</dc:creator>
    <dc:date>2007-12-11T00:44:17Z</dc:date>
    <item>
      <title>WBEM and Data Collection</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083612#M49702</link>
      <description>We are currently using HPSIM 5.1 w/ SP1.  Until recently, we've only used it to monitor our physical Proliant DL servers.  I read that it is possible to monitor virtual servers by enabling WBEM, and so we did.  Everything looked good until I found that every server is failing the BiWeekly Data Collection scheduled task.  If I disable WBEM in the Global Protocol Settings, the Data Collection works as normal.  Does anyone have any suggestions as to why this is?</description>
      <pubDate>Mon, 10 Dec 2007 21:59:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083612#M49702</guid>
      <dc:creator>SethD</dc:creator>
      <dc:date>2007-12-10T21:59:51Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM and Data Collection</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083613#M49703</link>
      <description>Current management agents for your ProLiant servers are exclusively SNMP.  You are gaining nothing by enabling WBEM.</description>
      <pubDate>Tue, 11 Dec 2007 00:44:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083613#M49703</guid>
      <dc:creator>David Claypool</dc:creator>
      <dc:date>2007-12-11T00:44:17Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM and Data Collection</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083614#M49704</link>
      <description>I enable wbem globally but leave the global credentials blank. I then manually add wbem credentials for the virtual guest servers.&lt;BR /&gt;&lt;BR /&gt;Using this I can get wbem to collect data.</description>
      <pubDate>Tue, 11 Dec 2007 07:24:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083614#M49704</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2007-12-11T07:24:16Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM and Data Collection</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083615#M49705</link>
      <description>Thanks Rob, I will give this a try today.</description>
      <pubDate>Tue, 11 Dec 2007 14:16:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083615#M49705</guid>
      <dc:creator>SethD</dc:creator>
      <dc:date>2007-12-11T14:16:09Z</dc:date>
    </item>
    <item>
      <title>Re: WBEM and Data Collection</title>
      <link>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083616#M49706</link>
      <description>Rob's work around will do the trick.  Thanks for your help!</description>
      <pubDate>Tue, 11 Dec 2007 17:37:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/wbem-and-data-collection/m-p/5083616#M49706</guid>
      <dc:creator>SethD</dc:creator>
      <dc:date>2007-12-11T17:37:58Z</dc:date>
    </item>
  </channel>
</rss>

