<?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: Predicitve Failure Notification in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326797#M35656</link>
    <description>You can set the trap for the hard drive predictive failure to critical, and then you will get notifications.  I have done this for a few different things.</description>
    <pubDate>Fri, 19 Dec 2008 19:49:59 GMT</pubDate>
    <dc:creator>Rancher</dc:creator>
    <dc:date>2008-12-19T19:49:59Z</dc:date>
    <item>
      <title>Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326796#M35655</link>
      <description>We are running HP SIM 5.1.  We only have four servers at this location, but it has been worthwhile to set up specifically for the alerting on hardware failures.&lt;BR /&gt;&lt;BR /&gt;I recently found that one of my servers (ML370 G4) has a predictive failure on one of the hard drives.  I discovered this accidentally while in the server room (orange light flashing on the drive - which is behind the door of the server in a tower configuration).  The problem is, SIM does not alert on this condition, as it is considered a "Minor Event".  I have alerting turned on for Major and Critical Events, but I have not included Minor Events because of the level of noise produced.  Does anyone have a creative way to catch these predictive failures, while still keeping the noise level down?  For example, filtering the Minor Event capturing to specific machines, or possibly (but less preferable) filtering it to specific events?  Of course the second option means you have to know what you specifically want to capture, which usually happens after the first crisis you encounter :&amp;gt;)</description>
      <pubDate>Fri, 19 Dec 2008 18:34:29 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326796#M35655</guid>
      <dc:creator>Glen R Martin</dc:creator>
      <dc:date>2008-12-19T18:34:29Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326797#M35656</link>
      <description>You can set the trap for the hard drive predictive failure to critical, and then you will get notifications.  I have done this for a few different things.</description>
      <pubDate>Fri, 19 Dec 2008 19:49:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326797#M35656</guid>
      <dc:creator>Rancher</dc:creator>
      <dc:date>2008-12-19T19:49:59Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326798#M35657</link>
      <description>Thanks for the quick answer!  I was not aware you could do that.  How do you change the status level of a trap?</description>
      <pubDate>Fri, 19 Dec 2008 20:29:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326798#M35657</guid>
      <dc:creator>Glen R Martin</dc:creator>
      <dc:date>2008-12-19T20:29:43Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326799#M35658</link>
      <description>You are very welcome!&lt;BR /&gt;&lt;BR /&gt;We also have ML370 G4s, so hopefully this will be the correct trap for you.  If not, your system logs will tell you which MIB and which trap you want to change and you can use the same procedure. &lt;BR /&gt; &lt;BR /&gt;In SIMS, go to Options, Events, SNMP Trap Settings.&lt;BR /&gt;Click the drop down box by MIB name and select cpqida.mib&lt;BR /&gt;CLick the drop down box by Trap name and select (SNMP) Physical Drive Status Change (3046)  &lt;BR /&gt;In the Severity box, select critical.&lt;BR /&gt;&lt;BR /&gt;This is what I have done to get alerts.</description>
      <pubDate>Fri, 19 Dec 2008 20:40:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326799#M35658</guid>
      <dc:creator>Rancher</dc:creator>
      <dc:date>2008-12-19T20:40:43Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326800#M35659</link>
      <description>Sorry for the rookie questions...you are already far deeper into SIM than I have ever delved :&amp;gt;)  I have a basic understanding of MIB concepts, but no experience working with them at this level.&lt;BR /&gt;&lt;BR /&gt;I have followed your directions, but when I get to the Trap Name drop down, I don't have any entries that start with SNMP.  What I have is numerous cpqDA(x) entries, where (x) is either 2-7, or there is a number of entries with cpqDA with no number after.  So there are a number of "PhyDrvStatusChange" entries, but all of these already appear to be set to "Critical".&lt;BR /&gt;&lt;BR /&gt;What you indicated (Physical Drive Status Change (3046)) shows up in the field below Trap Name titled "Event Type".  The number (3046) is different for each of the cpqDA entries.&lt;BR /&gt;&lt;BR /&gt;I have double checked the basic alerting functionality by sending a test trap, and it does appear to be working.  I have the SNMP configured, and I do occasionally receive other alerts.&lt;BR /&gt;&lt;BR /&gt;Thanks again for the help.</description>
      <pubDate>Fri, 19 Dec 2008 22:49:50 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326800#M35659</guid>
      <dc:creator>Glen R Martin</dc:creator>
      <dc:date>2008-12-19T22:49:50Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326801#M35660</link>
      <description>I still haven't got a solution for this - anyone?</description>
      <pubDate>Mon, 05 Jan 2009 22:22:12 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326801#M35660</guid>
      <dc:creator>Glen R Martin</dc:creator>
      <dc:date>2009-01-05T22:22:12Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326802#M35661</link>
      <description>I am still waiting for a final answer to this.  It's killing me that I am 90% of the way there.  Can anyone provide the answer to my last question to Rancher?&lt;BR /&gt;&lt;BR /&gt;Thanks.</description>
      <pubDate>Thu, 12 Mar 2009 21:54:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326802#M35661</guid>
      <dc:creator>Glen R Martin</dc:creator>
      <dc:date>2009-03-12T21:54:18Z</dc:date>
    </item>
    <item>
      <title>Re: Predicitve Failure Notification</title>
      <link>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326803#M35662</link>
      <description>hi,&lt;BR /&gt;&lt;BR /&gt;  did you check the logs as rancher suggested to identify the mib / trap involved ?&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Mon, 16 Mar 2009 15:51:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/predicitve-failure-notification/m-p/4326803#M35662</guid>
      <dc:creator>marsh_1</dc:creator>
      <dc:date>2009-03-16T15:51:16Z</dc:date>
    </item>
  </channel>
</rss>

