<?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: enable Drive Array Accelerator in ProLiant Servers (ML,DL,SL)</title>
    <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464676#M38550</link>
    <description>The error is generated only on a restart. I would assume that this is a normal occurance if the Array Accelerator is not configured.&lt;BR /&gt;There is very little utilization of this server so I'm not too concerned about load.&lt;BR /&gt;I suppose if the option is available in the Windows interface of the ACU that HP meant for it to be changed there, I'm just not certain if that will adversly effect the array.&lt;BR /&gt;&lt;BR /&gt;Have you experienced enabling this on the fly ?&lt;BR /&gt;&lt;BR /&gt;Thanks, Wayne</description>
    <pubDate>Mon, 17 Jan 2005 14:52:31 GMT</pubDate>
    <dc:creator>Wayne Glabais</dc:creator>
    <dc:date>2005-01-17T14:52:31Z</dc:date>
    <item>
      <title>enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464672#M38546</link>
      <description>Receiving Drive Array Accelerator status = not configured.&lt;BR /&gt;&lt;BR /&gt;Can I configure this "on the fly" using ACU without negatively impacting my server environment ?&lt;BR /&gt;&lt;BR /&gt;OS=Windows 2003/Active Directory</description>
      <pubDate>Mon, 17 Jan 2005 12:33:40 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464672#M38546</guid>
      <dc:creator>Wayne Glabais</dc:creator>
      <dc:date>2005-01-17T12:33:40Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464673#M38547</link>
      <description>In general it designed to do from O/S when System Up and Running or from Smart Start CD. As fare as un-configured seems it asking to set Read write Options &amp;amp; Expand and Rebuild Priority. Normally it should not ask you unless battery was low or any other changes. Verify your Settings and check Firmware for array controller. &lt;A href="http://h18000.www1.hp.com/support/files/storage/us/index.html" target="_blank"&gt;http://h18000.www1.hp.com/support/files/storage/us/index.html&lt;/A&gt;</description>
      <pubDate>Mon, 17 Jan 2005 13:06:17 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464673#M38547</guid>
      <dc:creator>Oleg Koroz</dc:creator>
      <dc:date>2005-01-17T13:06:17Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464674#M38548</link>
      <description>I looked into the configuration of the array with the ACU utility. This may have been an oversite, as the checkbox beside "enable array accelerator" has not been checked.&lt;BR /&gt;&lt;BR /&gt;Can I simply enable the accelerator or will this have a negative impact on the array ?&lt;BR /&gt;&lt;BR /&gt;Regards, Wayne&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Jan 2005 13:10:43 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464674#M38548</guid>
      <dc:creator>Wayne Glabais</dc:creator>
      <dc:date>2005-01-17T13:10:43Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464675#M38549</link>
      <description>You should able change when System up and running it planned to do from O/S, however under heavy load it possibly to cause system to hung or crush. Once again we don't know actual reason why it gave error? So if your box 100% healthy there should be no problem.</description>
      <pubDate>Mon, 17 Jan 2005 14:15:01 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464675#M38549</guid>
      <dc:creator>Oleg Koroz</dc:creator>
      <dc:date>2005-01-17T14:15:01Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464676#M38550</link>
      <description>The error is generated only on a restart. I would assume that this is a normal occurance if the Array Accelerator is not configured.&lt;BR /&gt;There is very little utilization of this server so I'm not too concerned about load.&lt;BR /&gt;I suppose if the option is available in the Windows interface of the ACU that HP meant for it to be changed there, I'm just not certain if that will adversly effect the array.&lt;BR /&gt;&lt;BR /&gt;Have you experienced enabling this on the fly ?&lt;BR /&gt;&lt;BR /&gt;Thanks, Wayne</description>
      <pubDate>Mon, 17 Jan 2005 14:52:31 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464676#M38550</guid>
      <dc:creator>Wayne Glabais</dc:creator>
      <dc:date>2005-01-17T14:52:31Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464677#M38551</link>
      <description>For your practice you can set to 100% read 0% Write for First Time, where those setting by defaults even if not selected, after you can change if BBWC used. &lt;BR /&gt;&lt;BR /&gt;Here is something from actual white Papers: &lt;BR /&gt;....... The read/write ratio is adjustable from 100% read or write to any mix in between. The ratio is usually set during configuration, but can be set at any time using the Array Configuration Utility.....&lt;BR /&gt;</description>
      <pubDate>Mon, 17 Jan 2005 15:40:00 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464677#M38551</guid>
      <dc:creator>Oleg Koroz</dc:creator>
      <dc:date>2005-01-17T15:40:00Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464678#M38552</link>
      <description>*PROVIDED* the battery for the array controller is installed and in good condition, you can enable the array accelerator at any time.&lt;BR /&gt;&lt;BR /&gt;You can also turn it off for specific logical volumes within an array -depending on the model of array controller.&lt;BR /&gt;&lt;BR /&gt;You can split the proportion of memory on the array controller allocated to read vs write.  I recommend 75/25 read/write, but tune it based on the performance figures that Insight Manager gives.</description>
      <pubDate>Mon, 17 Jan 2005 19:53:42 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464678#M38552</guid>
      <dc:creator>John Marinov</dc:creator>
      <dc:date>2005-01-17T19:53:42Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464679#M38553</link>
      <description>You have not said what Array Controller you are using.  It must have a battery backed cache to enable write caching.  Once the battery is fully charged you will be able to change the ratio.  The actual ratio that you employ will depend on the use of the server (are the applications read or write intensive?).  This may be changed at any time "on the fly".</description>
      <pubDate>Tue, 18 Jan 2005 11:31:46 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464679#M38553</guid>
      <dc:creator>Colin_29</dc:creator>
      <dc:date>2005-01-18T11:31:46Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464680#M38554</link>
      <description>The controller is a Smart Array 5i</description>
      <pubDate>Tue, 18 Jan 2005 12:52:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464680#M38554</guid>
      <dc:creator>Wayne Glabais</dc:creator>
      <dc:date>2005-01-18T12:52:58Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464681#M38555</link>
      <description>The DL 360 G2 server is the only server which has a battery connector for the optional upgrade, the BBWC Enabler, for the Smart Array 5i controller.  If you do not have this model or you have not installed the optional upgrade then you will no have Battery Backed Write Cache and will therefore only be able to utilise read cache.&lt;BR /&gt;&lt;BR /&gt;The "5i plus" is different but you still require the optional upgrade to use write cache.</description>
      <pubDate>Tue, 18 Jan 2005 13:36:11 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464681#M38555</guid>
      <dc:creator>Colin_29</dc:creator>
      <dc:date>2005-01-18T13:36:11Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464682#M38556</link>
      <description>The server is a DL360 G3 series so it would be an Integrated Smart Array 5i Plus, Firmware Version Rev B, v2.36.&lt;BR /&gt;We have 5 of these configured identically, except for this one. For some reason the accelerator is not in the enabled state in the ACU Logical Drive Array Accelerator Settings. I suspect this was changed somehow during the initial array configuration, however I cannot confirm this other than the event log shows the event:1204 from day 1 of the install.&lt;BR /&gt;"Drive Array Accelerator Status Change.  The array accelerator board attached to the array controller in Slot 0 has a new status of 2.(Accelerator status values: 1=other, 2=notConfigured, 3=enabled, 4=tmpDisabled, 5=permDisabled)&lt;BR /&gt; [SNMP TRAP: 3038 in CPQIDA.MIB]"&lt;BR /&gt;&lt;BR /&gt;My guess is that the installer unchecked this during the config of the array.&lt;BR /&gt;&lt;BR /&gt;Q. Is it exceptable practice to change this to the enabled state via the ACU ? All other servers of same function have this enabled.&lt;BR /&gt;&lt;BR /&gt;Thanks to everyone for helping on this,&lt;BR /&gt;Regards, Wayne&lt;BR /&gt;</description>
      <pubDate>Tue, 18 Jan 2005 14:05:19 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464682#M38556</guid>
      <dc:creator>Wayne Glabais</dc:creator>
      <dc:date>2005-01-18T14:05:19Z</dc:date>
    </item>
    <item>
      <title>Re: enable Drive Array Accelerator</title>
      <link>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464683#M38557</link>
      <description>Wayne,&lt;BR /&gt;&lt;BR /&gt;I think we can hit this on the head now otherwise you will never get round to assigning points!!&lt;BR /&gt;&lt;BR /&gt;The simple answer is "Yes"&lt;BR /&gt;&lt;BR /&gt;Colin</description>
      <pubDate>Tue, 18 Jan 2005 14:37:32 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-servers-ml-dl-sl/enable-drive-array-accelerator/m-p/3464683#M38557</guid>
      <dc:creator>Colin_29</dc:creator>
      <dc:date>2005-01-18T14:37:32Z</dc:date>
    </item>
  </channel>
</rss>

