<?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 Reboots on Nodes connetected to MSA1000 in HPE EVA Storage</title>
    <link>https://community.hpe.com/t5/hpe-eva-storage/reboots-on-nodes-connetected-to-msa1000/m-p/3067200#M3622</link>
    <description>Greetings! &lt;BR /&gt;Has anyone seen DL580's with Win2000 reboot &lt;BR /&gt;when expanding the volume on MSA1000? &lt;BR /&gt;We have 2 MSA 1000 in a fabric(all reduandant) with 6 servers (2 Adv server 2000 and 4 Win2000 server )configured with SSP. 2 Adv servers only access MSA1000 -1 using SSP and other 4 Win 2000 servers access the other MSA1000 - 2 &lt;BR /&gt;All the servers are with Smartstart 6.1 , secure path ver 3.5.0.60, Virtual Replicator ver 3.0 build 176, HBA driver ver 5-4.82a9. &lt;BR /&gt;When we expand a drive using ACU xe on MSA1000-1 , any one of the 2 adv server Blue screens and comes back up with ASR bugcheck &lt;BR /&gt;Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x39B6F120, 0x00000002, 0x00000001, 0xDD4485B6)). This is random .It happend to the other adv server a while ago when we expanded the drive. the Bug check code was same 0x0000000A . It also happend on the server that has access to MSA1000-2. &lt;BR /&gt;Also we noticed that when the rebuild on the hardware level is complete any one of the server reboots with ASR. &lt;BR /&gt;All in common here is that When the rebuild is going on on completion occurs the servers get a Status change notifiacation from the server agents and that is the time when one of the server reboots. like this-&amp;gt; (Compaq External Array Logical Drive Status Change. Logical drive number 1 on array "MSA1000-1" has a new status of 12. &lt;BR /&gt;(Logical Drive status values: 1=other, 2=ok, 3=failed, 4=unconfigured, 5=recovering, 6=readyForRebuild, 7=rebuilding, 8=wrongDrive, 9=badConnect, 10=overheating, 11=shutdown, 12=expanding, 13=notAvailable, 14=queuedForExpansion) &lt;BR /&gt;[SNMP TRAP: 16022 in CPQFCA.MIB] &lt;BR /&gt;&lt;BR /&gt;So we disabled the Compaq agnets on the servers while the rebuild was going on assuming the Status change notification was triggering the reboots., When completed we dint see any reboots.. &lt;BR /&gt;&lt;BR /&gt;Any one seen this kind of a bug? we have had randomly ateast 5-6 reboots so far... &lt;BR /&gt;&lt;BR /&gt;We logged a call earlier at Hp and at that time they instructed us to get all the servers/compaq versions up todate which was latest at that time and we did it. But it didn't help. &lt;BR /&gt;Can Someone help us out here. &lt;BR /&gt;&lt;BR /&gt;Appreciate your responce ! &lt;BR /&gt;&lt;BR /&gt;thanks &lt;BR /&gt;</description>
    <pubDate>Tue, 09 Sep 2003 19:41:53 GMT</pubDate>
    <dc:creator>Poweruser</dc:creator>
    <dc:date>2003-09-09T19:41:53Z</dc:date>
    <item>
      <title>Reboots on Nodes connetected to MSA1000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/reboots-on-nodes-connetected-to-msa1000/m-p/3067200#M3622</link>
      <description>Greetings! &lt;BR /&gt;Has anyone seen DL580's with Win2000 reboot &lt;BR /&gt;when expanding the volume on MSA1000? &lt;BR /&gt;We have 2 MSA 1000 in a fabric(all reduandant) with 6 servers (2 Adv server 2000 and 4 Win2000 server )configured with SSP. 2 Adv servers only access MSA1000 -1 using SSP and other 4 Win 2000 servers access the other MSA1000 - 2 &lt;BR /&gt;All the servers are with Smartstart 6.1 , secure path ver 3.5.0.60, Virtual Replicator ver 3.0 build 176, HBA driver ver 5-4.82a9. &lt;BR /&gt;When we expand a drive using ACU xe on MSA1000-1 , any one of the 2 adv server Blue screens and comes back up with ASR bugcheck &lt;BR /&gt;Blue Screen Trap (BugCheck, STOP: 0x0000000A (0x39B6F120, 0x00000002, 0x00000001, 0xDD4485B6)). This is random .It happend to the other adv server a while ago when we expanded the drive. the Bug check code was same 0x0000000A . It also happend on the server that has access to MSA1000-2. &lt;BR /&gt;Also we noticed that when the rebuild on the hardware level is complete any one of the server reboots with ASR. &lt;BR /&gt;All in common here is that When the rebuild is going on on completion occurs the servers get a Status change notifiacation from the server agents and that is the time when one of the server reboots. like this-&amp;gt; (Compaq External Array Logical Drive Status Change. Logical drive number 1 on array "MSA1000-1" has a new status of 12. &lt;BR /&gt;(Logical Drive status values: 1=other, 2=ok, 3=failed, 4=unconfigured, 5=recovering, 6=readyForRebuild, 7=rebuilding, 8=wrongDrive, 9=badConnect, 10=overheating, 11=shutdown, 12=expanding, 13=notAvailable, 14=queuedForExpansion) &lt;BR /&gt;[SNMP TRAP: 16022 in CPQFCA.MIB] &lt;BR /&gt;&lt;BR /&gt;So we disabled the Compaq agnets on the servers while the rebuild was going on assuming the Status change notification was triggering the reboots., When completed we dint see any reboots.. &lt;BR /&gt;&lt;BR /&gt;Any one seen this kind of a bug? we have had randomly ateast 5-6 reboots so far... &lt;BR /&gt;&lt;BR /&gt;We logged a call earlier at Hp and at that time they instructed us to get all the servers/compaq versions up todate which was latest at that time and we did it. But it didn't help. &lt;BR /&gt;Can Someone help us out here. &lt;BR /&gt;&lt;BR /&gt;Appreciate your responce ! &lt;BR /&gt;&lt;BR /&gt;thanks &lt;BR /&gt;</description>
      <pubDate>Tue, 09 Sep 2003 19:41:53 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/reboots-on-nodes-connetected-to-msa1000/m-p/3067200#M3622</guid>
      <dc:creator>Poweruser</dc:creator>
      <dc:date>2003-09-09T19:41:53Z</dc:date>
    </item>
    <item>
      <title>Re: Reboots on Nodes connetected to MSA1000</title>
      <link>https://community.hpe.com/t5/hpe-eva-storage/reboots-on-nodes-connetected-to-msa1000/m-p/3067201#M3623</link>
      <description>If you implement zoning on the switches, and thereby seperate each server from one another, allowing each server to see only the MSA1000, then the occurences should only be limited to a particular server and not all the connected hosts.&lt;BR /&gt;&lt;BR /&gt;regards&lt;BR /&gt;christian</description>
      <pubDate>Wed, 10 Sep 2003 12:53:10 GMT</pubDate>
      <guid>https://community.hpe.com/t5/hpe-eva-storage/reboots-on-nodes-connetected-to-msa1000/m-p/3067201#M3623</guid>
      <dc:creator>Christian Schwartz-Søre</dc:creator>
      <dc:date>2003-09-10T12:53:10Z</dc:date>
    </item>
  </channel>
</rss>

