<?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 bugcheck events in Server Management - Systems Insight Manager</title>
    <link>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430058#M7721</link>
    <description>Hi there, Im trying to figure out how to get our SIM v4 to create a critical event upon detection of a bugcheck condition.  I would have thought it would do this by default but it appears not to. &lt;BR /&gt;&lt;BR /&gt;Instead, all we get are the events relating to the link up/link down status for the particular server that fell over.  Because the server comes back up so quickly it's not picked up within the polling interval.  Rather than shorten this interval I was hoping there would be an easy way for SIM to alarm upon a BSOD condition noted in it's integrated log...&lt;BR /&gt;&lt;BR /&gt;Any ideas guys?</description>
    <pubDate>Wed, 24 Nov 2004 17:05:59 GMT</pubDate>
    <dc:creator>Anthony Ashwin</dc:creator>
    <dc:date>2004-11-24T17:05:59Z</dc:date>
    <item>
      <title>bugcheck events</title>
      <link>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430058#M7721</link>
      <description>Hi there, Im trying to figure out how to get our SIM v4 to create a critical event upon detection of a bugcheck condition.  I would have thought it would do this by default but it appears not to. &lt;BR /&gt;&lt;BR /&gt;Instead, all we get are the events relating to the link up/link down status for the particular server that fell over.  Because the server comes back up so quickly it's not picked up within the polling interval.  Rather than shorten this interval I was hoping there would be an easy way for SIM to alarm upon a BSOD condition noted in it's integrated log...&lt;BR /&gt;&lt;BR /&gt;Any ideas guys?</description>
      <pubDate>Wed, 24 Nov 2004 17:05:59 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430058#M7721</guid>
      <dc:creator>Anthony Ashwin</dc:creator>
      <dc:date>2004-11-24T17:05:59Z</dc:date>
    </item>
    <item>
      <title>Re: bugcheck events</title>
      <link>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430059#M7722</link>
      <description>In the HP Agents GUI, try checking the Application Exception Trap box. You'll need to restart the agents.&lt;BR /&gt;This might generate a trap when the application terminates</description>
      <pubDate>Mon, 29 Nov 2004 14:51:30 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430059#M7722</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-11-29T14:51:30Z</dc:date>
    </item>
    <item>
      <title>Re: bugcheck events</title>
      <link>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430060#M7723</link>
      <description>tried setting the application exception tick box. Restarted the agents however it still didn't notify me upon a server bugcheck.  I did have an issue restarting the NIC agent but apart from that all agents restarted.&lt;BR /&gt;&lt;BR /&gt;Im probably making an assumption here but I would have thought that out of the box insight manager would have a predefined bugcheck event -and that it would be classed as critical?</description>
      <pubDate>Thu, 02 Dec 2004 16:27:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430060#M7723</guid>
      <dc:creator>Anthony Ashwin</dc:creator>
      <dc:date>2004-12-02T16:27:00Z</dc:date>
    </item>
    <item>
      <title>Re: bugcheck events</title>
      <link>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430061#M7724</link>
      <description>Is the Bugcheck taking the Server out?&lt;BR /&gt;If so then I'd say that the OS is not getting a chance to do anything.&lt;BR /&gt;I've shortened my Polling intervals to 1 minute to be able to pick up quick reboots.&lt;BR /&gt;I actuall set up a Ping Only Hardware Polling Task to run every minute and removed Ping from the regular check.</description>
      <pubDate>Thu, 02 Dec 2004 16:45:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/server-management-systems/bugcheck-events/m-p/3430061#M7724</guid>
      <dc:creator>Rob Buxton</dc:creator>
      <dc:date>2004-12-02T16:45:43Z</dc:date>
    </item>
  </channel>
</rss>

