<?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: SIM 7.4 - problem with alerts on Physical Drive Status Change in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/sim-7-4-problem-with-alerts-on-physical-drive-status-change/m-p/6692023#M59478</link>
    <description>&lt;P&gt;smamm,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please see this thread, it may help:&amp;nbsp; &lt;A href="https://community.hpe.com/t5/ITRC-HP-Systems-Insight-Manager/change-the-severity-of-an-event-in-HP-SIM-7-4/td-p/6680762#.VK6c63tlyYs" target="_self"&gt;http://h30499.www3.hp.com/t5/ITRC-HP-Systems-Insight-Manager/change-the-severity-of-an-event-in-HP-SIM-7-4/td-p/6680762#.VK6c63tlyYs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a workaround for storage/"status change" events, you may want to set up a specific condition or collection to send you all non-informational events for these.&amp;nbsp; Basically, without reading the thread I linked, these are special events where you cannot change the underlying severity.&amp;nbsp; For example, a predictive failure may always be a warning, however it is the same event ID # used for a failure condition, which would be critical (event 3046).&amp;nbsp; There are a few of these types.. another would be the status for RAID cache batteries.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A further example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HDD failure = failure code 7, event ID 3046 - Status change for a physical drive (critical)&lt;/P&gt;&lt;P&gt;HDD PFA = failure code 9, event ID 3046 - Status change for a physical drive (warning)&lt;/P&gt;&lt;P&gt;HDD online = failure code 0, event ID 3046 - Status change for a physical drive (informational)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These are not the correct failure codes, but you get the idea here..&amp;nbsp; it's all the same event number.&amp;nbsp; I am not an SNMP/MIB expert so I can't fully explain this behavior, I just know you cannot change the code behavior in SIM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
    <pubDate>Thu, 08 Jan 2015 15:13:20 GMT</pubDate>
    <dc:creator>LGentile</dc:creator>
    <dc:date>2015-01-08T15:13:20Z</dc:date>
    <item>
      <title>SIM 7.4 - problem with alerts on Physical Drive Status Change</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-7-4-problem-with-alerts-on-physical-drive-status-change/m-p/6691581#M59477</link>
      <description>&lt;P&gt;Strange problem. &amp;nbsp; I just got a new installation of SIM 7.4 up and running and I noticed that a bad disk didn't generate an email alert (like all of our other events).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I checked SNMP Trap Settings, and confirmed that the below event type was already enabled and set to Critical:&lt;/P&gt;&lt;P&gt;Mib Name: &amp;nbsp; cpqida.mib&lt;/P&gt;&lt;P&gt;Trap Name: cpqDa7PhyDrvStatusChange&amp;nbsp;&lt;/P&gt;&lt;P&gt;Event Type: &amp;nbsp; (SNMP) Physical Drive Status Change (3046)&lt;/P&gt;&lt;P&gt;Enable Trap Handling: &amp;nbsp;Yes&lt;/P&gt;&lt;P&gt;Category: &amp;nbsp;Proliant Storage Events&lt;/P&gt;&lt;P&gt;Severity: &amp;nbsp;Critical&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;We have automatic event handling activated for the "Important Events" default collection, which includes the "Proliant Storage Events" category.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;But yet, I never got an email alert on this event:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;(SNMP) Physical Drive Status Change (3046)&lt;/SPAN&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;SPAN&gt;The system has been fully discovered, and other email alerts have generated on it successfully in recent weeks. &amp;nbsp;HOWEVER, the above alert was categorized as a "Warning", which contradicts the severity assigned to it above. &amp;nbsp; I've got to be missing something here. &amp;nbsp; Anyone have an idea as to what may be wrong?&lt;/SPAN&gt;&lt;/P&gt;</description>
      <pubDate>Wed, 07 Jan 2015 16:16:06 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-7-4-problem-with-alerts-on-physical-drive-status-change/m-p/6691581#M59477</guid>
      <dc:creator>smamm</dc:creator>
      <dc:date>2015-01-07T16:16:06Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 7.4 - problem with alerts on Physical Drive Status Change</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-7-4-problem-with-alerts-on-physical-drive-status-change/m-p/6692023#M59478</link>
      <description>&lt;P&gt;smamm,&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Please see this thread, it may help:&amp;nbsp; &lt;A href="https://community.hpe.com/t5/ITRC-HP-Systems-Insight-Manager/change-the-severity-of-an-event-in-HP-SIM-7-4/td-p/6680762#.VK6c63tlyYs" target="_self"&gt;http://h30499.www3.hp.com/t5/ITRC-HP-Systems-Insight-Manager/change-the-severity-of-an-event-in-HP-SIM-7-4/td-p/6680762#.VK6c63tlyYs&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As a workaround for storage/"status change" events, you may want to set up a specific condition or collection to send you all non-informational events for these.&amp;nbsp; Basically, without reading the thread I linked, these are special events where you cannot change the underlying severity.&amp;nbsp; For example, a predictive failure may always be a warning, however it is the same event ID # used for a failure condition, which would be critical (event 3046).&amp;nbsp; There are a few of these types.. another would be the status for RAID cache batteries.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;A further example:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;HDD failure = failure code 7, event ID 3046 - Status change for a physical drive (critical)&lt;/P&gt;&lt;P&gt;HDD PFA = failure code 9, event ID 3046 - Status change for a physical drive (warning)&lt;/P&gt;&lt;P&gt;HDD online = failure code 0, event ID 3046 - Status change for a physical drive (informational)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;These are not the correct failure codes, but you get the idea here..&amp;nbsp; it's all the same event number.&amp;nbsp; I am not an SNMP/MIB expert so I can't fully explain this behavior, I just know you cannot change the code behavior in SIM.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Hope this helps!&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Thu, 08 Jan 2015 15:13:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-7-4-problem-with-alerts-on-physical-drive-status-change/m-p/6692023#M59478</guid>
      <dc:creator>LGentile</dc:creator>
      <dc:date>2015-01-08T15:13:20Z</dc:date>
    </item>
  </channel>
</rss>

