<?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>Server Management - Systems Insight ManagerのトピックReporting Issue in SIM 5.1 sp1</title>
    <link>https://community.hpe.com/t5/server-management-systems/reporting-issue-in-sim-5-1-sp1/m-p/4023133#M28011</link>
    <description>&lt;!--!*#--&gt;I have rolled out a disk space thresh hold for all servers in my domain. There is one server that is proving to be an enigma. &lt;BR /&gt;&lt;BR /&gt;It is a ProLiant BL20p G2. It connected to our SAN with 4 logical drives that are spanned. Why is it spanned? I have no idea, this configuration predates everyone on my team. &lt;BR /&gt;&lt;BR /&gt;Well when I do a data collection report in insightm - the total disk space for the SAN is correct, and the available space is correct. But the Percentage Used is off by a LOT. It shows that only 12 percent of the disk space is used when actually, it is about 40%. &lt;BR /&gt;&lt;BR /&gt;Windows reflects the correct amounts, even in the "system management homepage" is reporting everything properly. &lt;BR /&gt;&lt;BR /&gt;The issue is that we got down to 8% free space on the SAN last week and the disk threshold never prompted us. Why - because SIM - data collection report still showed about 30% available and yes, the disk space thresh hold is installed on this server.&lt;BR /&gt;&lt;BR /&gt;This is the only server that is spanned. All other servers that are connected to the SAN are just fine in Insightm.&lt;BR /&gt;&lt;BR /&gt;Is there a known issue for this? How does the data collection report calculate the info when genereating the report? Has anyone else seen this issue?</description>
    <pubDate>Tue, 19 Jun 2007 15:09:42 GMT</pubDate>
    <dc:creator>jlbetsch</dc:creator>
    <dc:date>2007-06-19T15:09:42Z</dc:date>
    <item>
      <title>Reporting Issue in SIM 5.1 sp1</title>
      <link>https://community.hpe.com/t5/server-management-systems/reporting-issue-in-sim-5-1-sp1/m-p/4023133#M28011</link>
      <description>&lt;!--!*#--&gt;I have rolled out a disk space thresh hold for all servers in my domain. There is one server that is proving to be an enigma. &lt;BR /&gt;&lt;BR /&gt;It is a ProLiant BL20p G2. It connected to our SAN with 4 logical drives that are spanned. Why is it spanned? I have no idea, this configuration predates everyone on my team. &lt;BR /&gt;&lt;BR /&gt;Well when I do a data collection report in insightm - the total disk space for the SAN is correct, and the available space is correct. But the Percentage Used is off by a LOT. It shows that only 12 percent of the disk space is used when actually, it is about 40%. &lt;BR /&gt;&lt;BR /&gt;Windows reflects the correct amounts, even in the "system management homepage" is reporting everything properly. &lt;BR /&gt;&lt;BR /&gt;The issue is that we got down to 8% free space on the SAN last week and the disk threshold never prompted us. Why - because SIM - data collection report still showed about 30% available and yes, the disk space thresh hold is installed on this server.&lt;BR /&gt;&lt;BR /&gt;This is the only server that is spanned. All other servers that are connected to the SAN are just fine in Insightm.&lt;BR /&gt;&lt;BR /&gt;Is there a known issue for this? How does the data collection report calculate the info when genereating the report? Has anyone else seen this issue?</description>
      <pubDate>Tue, 19 Jun 2007 15:09:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/reporting-issue-in-sim-5-1-sp1/m-p/4023133#M28011</guid>
      <dc:creator>jlbetsch</dc:creator>
      <dc:date>2007-06-19T15:09:42Z</dc:date>
    </item>
    <item>
      <title>Re: Reporting Issue in SIM 5.1 sp1</title>
      <link>https://community.hpe.com/t5/server-management-systems/reporting-issue-in-sim-5-1-sp1/m-p/4023134#M28012</link>
      <description>I'm confused.&lt;BR /&gt;You use the term "free space on the SAN" but you're also talking about space on a particular disk presented to a server which would be a LUN.&lt;BR /&gt;Space on the SAN itself is only monitored if you have the appropriate software set up and that depends on what kind of SAN you have. Growth on a SAN would be caused by snapshots, logfiles or whatever, again depending on what kind of SAN you have.&lt;BR /&gt;&lt;BR /&gt;As regards the data presented to the reports, the Report tables, by default, are updated every two weeks. There's a task that does this: Bi Weekly Data Collection.&lt;BR /&gt;You can increase the frequency of this.&lt;BR /&gt;&lt;BR /&gt;You can also create a Daily Historical Data collection task and then write your own reports to pull data directly from the database tables. The data tables (CIM_Logical_Disk from memory but check) will contain more up to date data.&lt;BR /&gt;&lt;BR /&gt;Lastly there is an issue with agents prior to 7.80 where the usage figures for larger storage arrays are not correctly reported.&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 20 Jun 2007 15:55:47 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/reporting-issue-in-sim-5-1-sp1/m-p/4023134#M28012</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2007-06-20T15:55:47Z</dc:date>
    </item>
  </channel>
</rss>

