<?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: Looking for Command Line Script documentation for the ACU in ProLiant Deployment and Provisioning</title>
    <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154090#M362</link>
    <description>I don't know if this of any help with error messages. There is a batch command called acr.bat that is part of the Rapid Deployment Kit.&lt;BR /&gt;This contains the following:&lt;BR /&gt;&lt;BR /&gt;:: ==============================================================&lt;BR /&gt;:: Error Codes&lt;BR /&gt;:: ==============================================================&lt;BR /&gt;:: 001 = Multiple errors where encountered&lt;BR /&gt;:: 001 = An argument error occured&lt;BR /&gt;:: 002 = An internal error occured&lt;BR /&gt;:: 002 = The input file could not be opened&lt;BR /&gt;:: 003 = The error file could not be opened&lt;BR /&gt;:: 004 = A memory allocation failure occured&lt;BR /&gt;:: 005 = The drive was not found or the drive is already assigned&lt;BR /&gt;:: 006 = The spare was not found or the spare is already assigned&lt;BR /&gt;:: 007 = The capture file could not be opened&lt;BR /&gt;:: 009 = No controllers were found&lt;BR /&gt;:: 010 = The was an error negotiating with the controller&lt;BR /&gt;:: 011 = The array profile does not contain any drive specification&lt;BR /&gt;:: 013 = A configuration error occured&lt;BR /&gt;:: 022 = An error occured while parsing the input file&lt;BR /&gt;:: 113 = An invalid Logical Drive Number was specified&lt;BR /&gt;:: 201 = The logical drive stripe size cannot be supported&lt;BR /&gt;:: 202 = The requested logical drive size cannot be supported&lt;BR /&gt;:: 203 = The RAID level cannot be supported&lt;BR /&gt;:: 206 = The logical drive size specified is too small&lt;BR /&gt;:: ==============================================================</description>
    <pubDate>Thu, 08 Jan 2004 08:38:52 GMT</pubDate>
    <dc:creator>David Alderman</dc:creator>
    <dc:date>2004-01-08T08:38:52Z</dc:date>
    <item>
      <title>Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154085#M357</link>
      <description>10 points to the person who can point me to the Array Configuration Utility "Command Line" undocumented documentation that HP is not so generously deploying. /giggle&lt;BR /&gt;&lt;BR /&gt;I have a copy of the ACU Users Guide "November 2002" (Fourth Eddition) and I am hoping there is a newer version and therefore more info on the command line interface.&lt;BR /&gt;&lt;BR /&gt;The new version is 7.0.1.0 and as far as I can tell, they did not update the documentation with this release. I figure there are new goodies as well as a few old ones burried in the application that are "undocumented". We are attempting to script a process to build using the command line interface that should have like features that are in the web interface.&lt;BR /&gt;&lt;BR /&gt;I guess to clerify... is there a 239449-005 (i.e., a newer document than the November 2002) burried in HP/Compaq web or ftp somewhere or a spcific document that shows the deep commands, codes and switches of the ACU command line interface other than what is shown in the 239449-004 document.&lt;BR /&gt;&lt;BR /&gt;Thanks! -John</description>
      <pubDate>Tue, 30 Dec 2003 13:34:38 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154085#M357</guid>
      <dc:creator>JohnWRuffo</dc:creator>
      <dc:date>2003-12-30T13:34:38Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154086#M358</link>
      <description>I think your looking for ACR found in the toolkit.&lt;BR /&gt;&lt;BR /&gt;&lt;A href="http://h18004.www1.hp.com/products/servers/management/toolkit/index.html" target="_blank"&gt;http://h18004.www1.hp.com/products/servers/management/toolkit/index.html&lt;/A&gt;&lt;BR /&gt;&lt;BR /&gt;</description>
      <pubDate>Wed, 31 Dec 2003 08:45:57 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154086#M358</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2003-12-31T08:45:57Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154087#M359</link>
      <description>Yeah... we are looking at this package to see if what we are trying to accomplish has any reference in there.  We get some interesting ACR error messages when we probe the commands.   I really am thinking that a newer version of the ACU document has not been published yet.  I was really hoping that an HP enginner would troll the board and post something...&lt;BR /&gt;&lt;BR /&gt;Thank you for replying!</description>
      <pubDate>Wed, 31 Dec 2003 09:07:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154087#M359</guid>
      <dc:creator>JohnWRuffo</dc:creator>
      <dc:date>2003-12-31T09:07:51Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154088#M360</link>
      <description>Please explain what you're trying to do.</description>
      <pubDate>Thu, 01 Jan 2004 20:51:56 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154088#M360</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2004-01-01T20:51:56Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154089#M361</link>
      <description>I struggled with this utility myself. &lt;BR /&gt;&lt;BR /&gt;I agree that the documentation in the scripting toolkit is a little bit thin, I had the october 2002 documentation printed out.&lt;BR /&gt;&lt;BR /&gt;I cheated a bit by manually configuring the array on a baseline server and then using the ACR to capture that configutation and write it to a file. You will need to boot the server with a DOS disk or PXE service or somthing similar.&lt;BR /&gt;&lt;BR /&gt;ACR /C [Drive:][path]filename&lt;BR /&gt;&lt;BR /&gt;Having done that with a couple of different array configurations you get more of an idea on how to structure the configuration script file and can make tweaks and changes yourself.&lt;BR /&gt;&lt;BR /&gt;When you have got some configuration files to use you can issue this command from DOS again:&lt;BR /&gt;&lt;BR /&gt;ACR /I {Drive:][path]filename&lt;BR /&gt;&lt;BR /&gt;If you have already got an array configured you might need to use the /O paramater also which confirms that you don't mind nuking the existing config.&lt;BR /&gt;&lt;BR /&gt;Hope this is of use.</description>
      <pubDate>Thu, 08 Jan 2004 08:28:16 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154089#M361</guid>
      <dc:creator>David Alderman</dc:creator>
      <dc:date>2004-01-08T08:28:16Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154090#M362</link>
      <description>I don't know if this of any help with error messages. There is a batch command called acr.bat that is part of the Rapid Deployment Kit.&lt;BR /&gt;This contains the following:&lt;BR /&gt;&lt;BR /&gt;:: ==============================================================&lt;BR /&gt;:: Error Codes&lt;BR /&gt;:: ==============================================================&lt;BR /&gt;:: 001 = Multiple errors where encountered&lt;BR /&gt;:: 001 = An argument error occured&lt;BR /&gt;:: 002 = An internal error occured&lt;BR /&gt;:: 002 = The input file could not be opened&lt;BR /&gt;:: 003 = The error file could not be opened&lt;BR /&gt;:: 004 = A memory allocation failure occured&lt;BR /&gt;:: 005 = The drive was not found or the drive is already assigned&lt;BR /&gt;:: 006 = The spare was not found or the spare is already assigned&lt;BR /&gt;:: 007 = The capture file could not be opened&lt;BR /&gt;:: 009 = No controllers were found&lt;BR /&gt;:: 010 = The was an error negotiating with the controller&lt;BR /&gt;:: 011 = The array profile does not contain any drive specification&lt;BR /&gt;:: 013 = A configuration error occured&lt;BR /&gt;:: 022 = An error occured while parsing the input file&lt;BR /&gt;:: 113 = An invalid Logical Drive Number was specified&lt;BR /&gt;:: 201 = The logical drive stripe size cannot be supported&lt;BR /&gt;:: 202 = The requested logical drive size cannot be supported&lt;BR /&gt;:: 203 = The RAID level cannot be supported&lt;BR /&gt;:: 206 = The logical drive size specified is too small&lt;BR /&gt;:: ==============================================================</description>
      <pubDate>Thu, 08 Jan 2004 08:38:52 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154090#M362</guid>
      <dc:creator>David Alderman</dc:creator>
      <dc:date>2004-01-08T08:38:52Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154091#M363</link>
      <description>Thank you David:&lt;BR /&gt;&lt;BR /&gt;Your post is a confirmation that we are on the right track... we were attempting to do generally the same thing. (have to put out fires first develop later)  I am glad to know you are having sucess with this and we are going down a road that has an ending.&lt;BR /&gt;&lt;BR /&gt;Shy of a formal document from HP on this your post is excelent info!  I sure wish someone from HP would troll this message and give us an insiders hint...&lt;BR /&gt;&lt;BR /&gt;Thanks!</description>
      <pubDate>Thu, 08 Jan 2004 08:50:18 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154091#M363</guid>
      <dc:creator>JohnWRuffo</dc:creator>
      <dc:date>2004-01-08T08:50:18Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154092#M364</link>
      <description>acr /?  - will provide the listing of error messages.</description>
      <pubDate>Thu, 08 Jan 2004 11:36:51 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154092#M364</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2004-01-08T11:36:51Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154093#M365</link>
      <description>Just did some checking and the codes are incorrect. The corrected codes are noted.  Will be corrected in next version of ACR.&lt;BR /&gt;&lt;BR /&gt;ERR001:Multiple Errors Encountered&lt;BR /&gt;ERR002:An internal error occured&lt;BR /&gt;ERR003:Error File could not be opened&lt;BR /&gt;ERR004:Memory Allocation Failure&lt;BR /&gt;ERR005:Drive not found or Drive already assigned&lt;BR /&gt;ERR006:Spare not found or Spare already assigned&lt;BR /&gt;ERR007:Capture File could not be opened&lt;BR /&gt;ERR008:Argument Error&lt;BR /&gt;ERR009:No Controllers found&lt;BR /&gt;ERR010:Error Negotiating with controller&lt;BR /&gt;ERR021:Input File could not be opened&lt;BR /&gt;ERR022:An error occured while parsing input file&lt;BR /&gt;ERR013:A configuration error occured&lt;BR /&gt;ERR113:Invalid Logical Drive Number specified&lt;BR /&gt;ERR202:The requested logical drive size cannot be supported&lt;BR /&gt;ERR203:The RAID Level cannot be supported&lt;BR /&gt;ERR011:Array Profile does not contain any drive specification&lt;BR /&gt;ERR206:The logical drive size specified is too small&lt;BR /&gt;ERR201:The logical drive stripe size cannot be supported&lt;BR /&gt;</description>
      <pubDate>Fri, 23 Jan 2004 17:12:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154093#M365</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2004-01-23T17:12:58Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154094#M366</link>
      <description>Thanks Gordon:&lt;BR /&gt;&lt;BR /&gt;There is an internal HP training course that, if taken (i.e., you pay for it) you get a set of documentation that shows the internal goodies of the ACU/ACR.  We are attempting to get the doc's from this course.</description>
      <pubDate>Sat, 24 Jan 2004 08:00:25 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154094#M366</guid>
      <dc:creator>JohnWRuffo</dc:creator>
      <dc:date>2004-01-24T08:00:25Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154095#M367</link>
      <description>Whst is the course number?</description>
      <pubDate>Mon, 26 Jan 2004 09:32:58 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154095#M367</guid>
      <dc:creator>Gordon Leonard</dc:creator>
      <dc:date>2004-01-26T09:32:58Z</dc:date>
    </item>
    <item>
      <title>Re: Looking for Command Line Script documentation for the ACU</title>
      <link>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154096#M368</link>
      <description>We had looked at the MSA1000 course 9711.  It gave us no real info on the underlying commands used in the GUI.&lt;BR /&gt;&lt;BR /&gt;Essentially what we need is to be able to duplicate the interraction which takes place between the GUI interface (web) with the linux Binary (ACU-EXE).  At present, the CLI (command interface) has limited command reference.  Essentially you can "only" input/output a file or "delimited" from the command line itself.  All the goodies are hidden behind the GUI.&lt;BR /&gt;&lt;BR /&gt;What we were looking for was all the undocumented interactions that appear to exist in the web interface and then duplicate these in a command line script against the binary.&lt;BR /&gt;&lt;BR /&gt;If they put out the tool and claim that the same functionality exists in the CLI as it does in the GUI, then they should have, at least, documented how to do this.  As far as &lt;BR /&gt;we have found, this is NOT the case.&lt;BR /&gt;&lt;BR /&gt;We are using the linux version of the ACU, thus we are looking at this from the Linux perspective (you know command line commando) and we find ourselves at the mercy of a tool with limited "command line" functions and a fully functional "Window" GUI.&lt;BR /&gt;&lt;BR /&gt;Any HP Engineer want to comment about this?</description>
      <pubDate>Mon, 26 Jan 2004 11:54:27 GMT</pubDate>
      <guid>https://community.hpe.com/t5/proliant-deployment-and/looking-for-command-line-script-documentation-for-the-acu/m-p/3154096#M368</guid>
      <dc:creator>JohnWRuffo</dc:creator>
      <dc:date>2004-01-26T11:54:27Z</dc:date>
    </item>
  </channel>
</rss>

