<?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 ML530 ASR's in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991268#M18967</link>
    <description>I inherited an ML530 G2 running Win2K SP3 with SQL2K. It has experienced multiple random ASR's over the last month. Only one produced a Bug Stop trap (0xD1). Event logs show nothing other than an unexpected restart (duh!).&lt;BR /&gt;&lt;BR /&gt;Ideas?</description>
    <pubDate>Fri, 06 Jun 2003 17:04:21 GMT</pubDate>
    <dc:creator>Doug Williams_3</dc:creator>
    <dc:date>2003-06-06T17:04:21Z</dc:date>
    <item>
      <title>ML530 ASR's</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991268#M18967</link>
      <description>I inherited an ML530 G2 running Win2K SP3 with SQL2K. It has experienced multiple random ASR's over the last month. Only one produced a Bug Stop trap (0xD1). Event logs show nothing other than an unexpected restart (duh!).&lt;BR /&gt;&lt;BR /&gt;Ideas?</description>
      <pubDate>Fri, 06 Jun 2003 17:04:21 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991268#M18967</guid>
      <dc:creator>Doug Williams_3</dc:creator>
      <dc:date>2003-06-06T17:04:21Z</dc:date>
    </item>
    <item>
      <title>Re: ML530 ASR's</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991269#M18968</link>
      <description>You could try disabling the ASR or changing the ASR timeout.</description>
      <pubDate>Fri, 06 Jun 2003 18:20:49 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991269#M18968</guid>
      <dc:creator>Marc Eastburn</dc:creator>
      <dc:date>2003-06-06T18:20:49Z</dc:date>
    </item>
    <item>
      <title>Re: ML530 ASR's</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991270#M18969</link>
      <description>You could try disabling the ASR or changing the ASR timeout.</description>
      <pubDate>Fri, 06 Jun 2003 18:21:07 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991270#M18969</guid>
      <dc:creator>Marc Eastburn</dc:creator>
      <dc:date>2003-06-06T18:21:07Z</dc:date>
    </item>
    <item>
      <title>Re: ML530 ASR's</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991271#M18970</link>
      <description>No solution I'm afraid, but I am getting the same problem and it only occurs on one of two identical builds. IML is now also reporting 'Unknown event (Class 15, Code 0 and Code 255)on every boot - I have been unable to find any information on these. Whether related or not, Insight Manager Environment shows sensor 5 (one of the CPUs) often running 6-8 degrees hotter than the other (the other server always indicates a 1 degree difference).&lt;BR /&gt;&lt;BR /&gt;Tech support suggest a hardware issue, so I have reseated all hardware and also now swapped over both processors and voltage regulator modules (expecting to see the temp issue move to sensor 4..........it didn't!!)&lt;BR /&gt;I have also run the hardware test on the SmartStart CD for over 4000 cycles now, with no problem identified.</description>
      <pubDate>Mon, 09 Jun 2003 10:27:20 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991271#M18970</guid>
      <dc:creator>Mark Lenton</dc:creator>
      <dc:date>2003-06-09T10:27:20Z</dc:date>
    </item>
    <item>
      <title>Re: ML530 ASR's</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991272#M18971</link>
      <description>Update:&lt;BR /&gt;2 more ASR's this week. I was able to check one memory dump to find the exception address and then run pstat.exe to identify the driver. The offender was ntoskrnl.exe with a 0x0d1 STOP code.&lt;BR /&gt;&lt;BR /&gt;Microsoft's KB article: 302400 would be a great help if we were teaming NIC's on this server. The ML530 is running with only one NIC and is therefore not teamed.&lt;BR /&gt;&lt;BR /&gt;Since the server predates my employment, I am not certain what drivers or SP have been applied.&lt;BR /&gt;&lt;BR /&gt;BTW: Company policy/procedure won't allow me to shut off the ASR's.&lt;BR /&gt;&lt;BR /&gt;Thanks in advance.</description>
      <pubDate>Thu, 12 Jun 2003 20:58:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991272#M18971</guid>
      <dc:creator>Doug Williams_3</dc:creator>
      <dc:date>2003-06-12T20:58:10Z</dc:date>
    </item>
    <item>
      <title>Re: ML530 ASR's</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991273#M18972</link>
      <description>The following forum seems to have provided the information I was looking for to solve my problem. The issue in this forum isn't exactly what I was experiencing, but the disabling of System Information seems to have done the trick.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc731b941255cd71190080090279cd0f9,00.html" target="_blank"&gt;http://forums.itrc.hp.com/cm/QuestionAnswer/1,,0xc731b941255cd71190080090279cd0f9,00.html&lt;/A&gt;</description>
      <pubDate>Thu, 03 Jul 2003 21:36:44 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/ml530-asr-s/m-p/2991273#M18972</guid>
      <dc:creator>Doug Williams_3</dc:creator>
      <dc:date>2003-07-03T21:36:44Z</dc:date>
    </item>
  </channel>
</rss>

