<?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 4.0 Notify Errors in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355148#M5112</link>
    <description>What we wound up doing is setting up all of the servers to send traps to the SIM management server as well as having the SIM agents on the server checking status every 30 seconds, and then setting the SIM server to only poll the hardware every 5 minutes. Once the server recieves a trap, it generates an event and then sends an email to the specified accounts. Most fo the events are generated as critical events, but you can edit the severity in the sim console under Options-&amp;gt;Events-&amp;gt;SNMP Trap Settings. This has actually worked out well for us. Hope this helps</description>
    <pubDate>Mon, 03 Jan 2005 10:56:11 GMT</pubDate>
    <dc:creator>Alex Jackson</dc:creator>
    <dc:date>2005-01-03T10:56:11Z</dc:date>
    <item>
      <title>SIM 4.0 Notify Errors</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355146#M5110</link>
      <description>I have SIM 4.0 on a DL380 G3 with W2K3 running MSSQL2000. All patches have been applied. The issue I have, is that whenever there is a hardware status change(such as a failed hard drive), I shows up under hardware status but not under uncleared events. It also is not sending out any emails about the hardware change. I does send emails whenever a device goes into critical or normal status, but never for major or minor status with the exceptions of login failures or task failures. I have uninstalled and reinstalled both HP SIM and SQL to attempt to resolve the issue. And just for info...it worked very nicely for about 2 weeks before it quit notifying.</description>
      <pubDate>Wed, 11 Aug 2004 23:31:54 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355146#M5110</guid>
      <dc:creator>Alex Jackson</dc:creator>
      <dc:date>2004-08-11T23:31:54Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 4.0 Notify Errors</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355147#M5111</link>
      <description>Alex, I have the same problem. I use 4.2 on a DL360 with W2K3 running MSDE. Do you have already an solution. I would really like to implement HP SIM 4.2 Thanks &lt;BR /&gt;&lt;BR /&gt;Sander Biemans&lt;BR /&gt;Holland (The Netherlands)</description>
      <pubDate>Mon, 03 Jan 2005 10:21:09 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355147#M5111</guid>
      <dc:creator>Sander Biemans</dc:creator>
      <dc:date>2005-01-03T10:21:09Z</dc:date>
    </item>
    <item>
      <title>Re: SIM 4.0 Notify Errors</title>
      <link>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355148#M5112</link>
      <description>What we wound up doing is setting up all of the servers to send traps to the SIM management server as well as having the SIM agents on the server checking status every 30 seconds, and then setting the SIM server to only poll the hardware every 5 minutes. Once the server recieves a trap, it generates an event and then sends an email to the specified accounts. Most fo the events are generated as critical events, but you can edit the severity in the sim console under Options-&amp;gt;Events-&amp;gt;SNMP Trap Settings. This has actually worked out well for us. Hope this helps</description>
      <pubDate>Mon, 03 Jan 2005 10:56:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/sim-4-0-notify-errors/m-p/3355148#M5112</guid>
      <dc:creator>Alex Jackson</dc:creator>
      <dc:date>2005-01-03T10:56:11Z</dc:date>
    </item>
  </channel>
</rss>

