<?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: Software &amp;amp; Hardware Audit in Operating System - HP-UX</title>
    <link>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029554#M132225</link>
    <description>As Massimo said MeasureWare (it has now been re-branded as part of Open View, but I dont know its name), &amp;amp; Systems Tool Manager (STM) * Event Monitoring System (EMS)&lt;BR /&gt;&lt;BR /&gt;We use both quite successfully.  On the MeasureWare front, you can raise alarms on certain conditions (say a process taking up too much cpu etc) which is nifty.&lt;BR /&gt;&lt;BR /&gt;What we do is try (we were successful) to find a system driver like number of queries or number of inserts.  We found that if you also log this driver as well &amp;amp; plot say CPU Vs Driver, disk% Vs Driver, the whole "performance" of the box was simply representeed by a few straight lines.  The gradient of the each line represented a performance indicator AND you knew when the box would run out of steam.&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;Tim</description>
    <pubDate>Tue, 22 Jul 2003 07:13:29 GMT</pubDate>
    <dc:creator>Tim D Fulford</dc:creator>
    <dc:date>2003-07-22T07:13:29Z</dc:date>
    <item>
      <title>Software &amp; Hardware Audit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029552#M132223</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;I'm interested to find out a tools that use by HP engineer to audit a system performance (OS &amp;amp; Hardware) for preventive maintenance and also a guide line to evaluate the result. Or if someone have other tools (not HP) for the same purpose. Would really appreciate for your input.&lt;BR /&gt;&lt;BR /&gt;Regards,&lt;BR /&gt;Munawwar</description>
      <pubDate>Tue, 22 Jul 2003 06:55:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029552#M132223</guid>
      <dc:creator>Ahmad Munawwar</dc:creator>
      <dc:date>2003-07-22T06:55:58Z</dc:date>
    </item>
    <item>
      <title>Re: Software &amp; Hardware Audit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029553#M132224</link>
      <description>Hi,&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;performance related&lt;BR /&gt;&lt;BR /&gt;best tools are not free, and are mwa (for data gathering), glance (for instant check of parameters, a must have for every serious performance study), perfview (needed to analyze mwa data graphically over time).&lt;BR /&gt;&lt;BR /&gt;free tools include many unix command, like top, ps, sar, vmstat, nfsstat.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hardware monitoring&lt;BR /&gt;&lt;BR /&gt;Diagnostic tools (free), are shipped quarterly with the patches. Best known are EMS (event monitoring system) for continuos hw monitor and stm/xstm/cstm for ad hoc investigation&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;Massimo&lt;BR /&gt;</description>
      <pubDate>Tue, 22 Jul 2003 07:00:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029553#M132224</guid>
      <dc:creator>Massimo Bianchi</dc:creator>
      <dc:date>2003-07-22T07:00:50Z</dc:date>
    </item>
    <item>
      <title>Re: Software &amp; Hardware Audit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029554#M132225</link>
      <description>As Massimo said MeasureWare (it has now been re-branded as part of Open View, but I dont know its name), &amp;amp; Systems Tool Manager (STM) * Event Monitoring System (EMS)&lt;BR /&gt;&lt;BR /&gt;We use both quite successfully.  On the MeasureWare front, you can raise alarms on certain conditions (say a process taking up too much cpu etc) which is nifty.&lt;BR /&gt;&lt;BR /&gt;What we do is try (we were successful) to find a system driver like number of queries or number of inserts.  We found that if you also log this driver as well &amp;amp; plot say CPU Vs Driver, disk% Vs Driver, the whole "performance" of the box was simply representeed by a few straight lines.  The gradient of the each line represented a performance indicator AND you knew when the box would run out of steam.&lt;BR /&gt;&lt;BR /&gt;Good luck&lt;BR /&gt;&lt;BR /&gt;Tim</description>
      <pubDate>Tue, 22 Jul 2003 07:13:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029554#M132225</guid>
      <dc:creator>Tim D Fulford</dc:creator>
      <dc:date>2003-07-22T07:13:29Z</dc:date>
    </item>
    <item>
      <title>Re: Software &amp; Hardware Audit</title>
      <link>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029555#M132226</link>
      <description>This script is to notify SA when the usage of a filesystem exceeds a "upperlimit". Run it using cron jobs daily in the morning.</description>
      <pubDate>Tue, 22 Jul 2003 07:42:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/operating-system-hp-ux/software-amp-hardware-audit/m-p/3029555#M132226</guid>
      <dc:creator>twang</dc:creator>
      <dc:date>2003-07-22T07:42:10Z</dc:date>
    </item>
  </channel>
</rss>

