<?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: The system has rebooted from a ASR event. in HPE ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633732#M102647</link>
    <description>And the IML is where it's logged.&lt;BR /&gt;You can read the IML through the ILo.&lt;BR /&gt;&lt;BR /&gt;if the System management driver is inresponsive, ei due to a BSOD, the server will AR and log the stop code (First line only).&lt;BR /&gt;&lt;BR /&gt;BR&lt;BR /&gt;/jag</description>
    <pubDate>Sun, 16 May 2010 10:32:38 GMT</pubDate>
    <dc:creator>gregersenj</dc:creator>
    <dc:date>2010-05-16T10:32:38Z</dc:date>
    <item>
      <title>The system has rebooted from a ASR event.</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633729#M102644</link>
      <description>HP ProLiant BL460c Server, HP BladeSystem c7000 Enclosure, Windows Server 2003 R2&lt;BR /&gt;&lt;BR /&gt;Servers are restarting with ASR Reason.&lt;BR /&gt;&lt;BR /&gt;Event log:&lt;BR /&gt;&lt;BR /&gt;The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;User Action: Determine the nature of the Automatic Server Recovery (ASR) event, and take corrective action.&lt;BR /&gt;&lt;BR /&gt;But how can I determine it?&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;hp2&lt;BR /&gt;&lt;BR /&gt;08.05.2010&lt;BR /&gt;&lt;BR /&gt;2:54:24 NetFN 0x6, command 0x25 timed out , Source: hpqilo2&lt;BR /&gt;3:05:12 The previous system shutdown at 3:02:43 Ð½Ð° 08.05.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;3:07:51 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt; &lt;BR /&gt;10.05.2010&lt;BR /&gt;&lt;BR /&gt;6:24:16 NetFN 0x4, command 0x2D timed out  , Source: hpqilo2&lt;BR /&gt;6:24:16 Failed GET SENSOR READING, sensor 14, Source: hpqilo2&lt;BR /&gt;6:35:41 The previous system shutdown at 6:33:26 Ð½Ð° 10.05.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;6:38:12 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;&lt;BR /&gt;hp3&lt;BR /&gt;&lt;BR /&gt;07.04.2010 &lt;BR /&gt;&lt;BR /&gt;10:03:24 The previous system shutdown at 9:50:53 Ð½Ð° 07.04.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;10:05:21 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt; &lt;BR /&gt;12.04.2010&lt;BR /&gt;&lt;BR /&gt;18:09:49 NetFN 0x6, command 0x22 timed out, Source: hpqilo2&lt;BR /&gt;18:21:27 The previous system shutdown at 18:18:00 Ð½Ð° 12.04.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;18:23:57 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;&lt;BR /&gt;14.04.2010&lt;BR /&gt;&lt;BR /&gt;10:32:28 NetFN 0x6, command 0x25 timed out , Source: hpqilo2&lt;BR /&gt;10:44:06 The previous system shutdown at 10:41:21 Ð½Ð° 14.04.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;10:46:07 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;&lt;BR /&gt;11.05.2010&lt;BR /&gt;&lt;BR /&gt;22:22:40 NetFN 0x6, command 0x22 timed out , Source: hpqilo2&lt;BR /&gt;22:34:17 The previous system shutdown at 22:31:28 Ð½Ð° 11.05.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;22:36:32 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;&lt;BR /&gt;hp4&lt;BR /&gt;&lt;BR /&gt;22.04.2010&lt;BR /&gt;&lt;BR /&gt;15:52:40 NetFN 0x6, command 0x22 timed out, Source: hpqilo2&lt;BR /&gt;16:02:57 The previous system shutdown at 16:01:32 Ð½Ð° 22.04.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;16:05:10 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;&lt;BR /&gt;24.04.2010&lt;BR /&gt;&lt;BR /&gt;19:02:49 NetFN 0x6, command 0x22 timed out, Source: hpqilo2&lt;BR /&gt;19:13:03 The previous system shutdown at 19:10:49 Ð½Ð° 24.04.2010 was unexpected.&lt;BR /&gt;...events&lt;BR /&gt;19:15:06 The system has rebooted from a Automatic Server Recovery (ASR) event.&lt;BR /&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Fri, 14 May 2010 09:53:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633729#M102644</guid>
      <dc:creator>Aleksey Krivenya</dc:creator>
      <dc:date>2010-05-14T09:53:49Z</dc:date>
    </item>
    <item>
      <title>Re: The system has rebooted from a ASR event.</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633730#M102645</link>
      <description>Hello,&lt;BR /&gt;this could by known issue with ilo2 firmware and drivers.&lt;BR /&gt;Please update:&lt;BR /&gt;ILO2 firmware to latest v1.82:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=1842750&amp;amp;prodNameId=3288156&amp;amp;swEnvOID=1005&amp;amp;swLang=8&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=MTX-fc5256d2bb88479890a2cb1cd3" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=1842750&amp;amp;prodNameId=3288156&amp;amp;swEnvOID=1005&amp;amp;swLang=8&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=MTX-fc5256d2bb88479890a2cb1cd3&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;ILO2 driver to latest v1.15:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=1842750&amp;amp;prodNameId=3288156&amp;amp;swEnvOID=1005&amp;amp;swLang=8&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=MTX-3673c656eb7b47888630e39ec3" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=1842750&amp;amp;prodNameId=3288156&amp;amp;swEnvOID=1005&amp;amp;swLang=8&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=MTX-3673c656eb7b47888630e39ec3&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;and ILO2 management controler driver to latest v1.13:&lt;BR /&gt;&lt;A href="http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=1842750&amp;amp;prodNameId=3288156&amp;amp;swEnvOID=1005&amp;amp;swLang=8&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=MTX-72257800030e47b1b21e4f6289" target="_blank"&gt;http://h20000.www2.hp.com/bizsupport/TechSupport/SoftwareDescription.jsp?lang=en&amp;amp;cc=us&amp;amp;prodTypeId=3709945&amp;amp;prodSeriesId=1842750&amp;amp;prodNameId=3288156&amp;amp;swEnvOID=1005&amp;amp;swLang=8&amp;amp;mode=2&amp;amp;taskId=135&amp;amp;swItem=MTX-72257800030e47b1b21e4f6289&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;This should help, if yes please assign points :).&lt;BR /&gt;&lt;BR /&gt;Jan</description>
      <pubDate>Sat, 15 May 2010 06:15:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633730#M102645</guid>
      <dc:creator>Jan Soska</dc:creator>
      <dc:date>2010-05-15T06:15:53Z</dc:date>
    </item>
    <item>
      <title>Re: The system has rebooted from a ASR event.</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633731#M102646</link>
      <description>Check the IML.&lt;BR /&gt;&lt;BR /&gt;ASR occour when the system managemnt driver is inresponcive, or when there's a HW failure, that require a reboot, to disable or recover.&lt;BR /&gt;&lt;BR /&gt;BR&lt;BR /&gt;/jag</description>
      <pubDate>Sun, 16 May 2010 10:16:13 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633731#M102646</guid>
      <dc:creator>gregersenj</dc:creator>
      <dc:date>2010-05-16T10:16:13Z</dc:date>
    </item>
    <item>
      <title>Re: The system has rebooted from a ASR event.</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633732#M102647</link>
      <description>And the IML is where it's logged.&lt;BR /&gt;You can read the IML through the ILo.&lt;BR /&gt;&lt;BR /&gt;if the System management driver is inresponsive, ei due to a BSOD, the server will AR and log the stop code (First line only).&lt;BR /&gt;&lt;BR /&gt;BR&lt;BR /&gt;/jag</description>
      <pubDate>Sun, 16 May 2010 10:32:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633732#M102647</guid>
      <dc:creator>gregersenj</dc:creator>
      <dc:date>2010-05-16T10:32:38Z</dc:date>
    </item>
    <item>
      <title>Re: The system has rebooted from a ASR event.</title>
      <link>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633733#M102648</link>
      <description>The event ID 57's with a source of HPQILO2 is a known problem and is resolved by applying what Jan recommended. The only thing I would recommend is to reboot immediately after applying these.</description>
      <pubDate>Mon, 17 May 2010 00:42:04 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-proliant-servers-ml-dl-sl/the-system-has-rebooted-from-a-asr-event/m-p/4633733#M102648</guid>
      <dc:creator>Terry Hutchings</dc:creator>
      <dc:date>2010-05-17T00:42:04Z</dc:date>
    </item>
  </channel>
</rss>

