Looking for Command Line Script documentation for the ACU

[JohnWRuffo]

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

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.

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.

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.

Thanks! -John

[Gordon Leonard]

I think your looking for ACR found in the toolkit.

http://h18004.www1.hp.com/products/servers/management/toolkit/index.html

[JohnWRuffo]

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...

Thank you for replying!

[Gordon Leonard]

Please explain what you're trying to do.

[David Alderman · Accepted solution]

I struggled with this utility myself.

I agree that the documentation in the scripting toolkit is a little bit thin, I had the october 2002 documentation printed out.

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.

ACR /C [Drive:][path]filename

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.

When you have got some configuration files to use you can issue this command from DOS again:

ACR /I {Drive:][path]filename

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.

Hope this is of use.

[David Alderman]

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.
This contains the following:

:: ==============================================================
:: Error Codes
:: ==============================================================
:: 001 = Multiple errors where encountered
:: 001 = An argument error occured
:: 002 = An internal error occured
:: 002 = The input file could not be opened
:: 003 = The error file could not be opened
:: 004 = A memory allocation failure occured
:: 005 = The drive was not found or the drive is already assigned
:: 006 = The spare was not found or the spare is already assigned
:: 007 = The capture file could not be opened
:: 009 = No controllers were found
:: 010 = The was an error negotiating with the controller
:: 011 = The array profile does not contain any drive specification
:: 013 = A configuration error occured
:: 022 = An error occured while parsing the input file
:: 113 = An invalid Logical Drive Number was specified
:: 201 = The logical drive stripe size cannot be supported
:: 202 = The requested logical drive size cannot be supported
:: 203 = The RAID level cannot be supported
:: 206 = The logical drive size specified is too small
:: ==============================================================

[JohnWRuffo]

Thank you David:

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.

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...

Thanks!

[Gordon Leonard]

acr /? - will provide the listing of error messages.

[Gordon Leonard]

Just did some checking and the codes are incorrect. The corrected codes are noted. Will be corrected in next version of ACR.

ERR001:Multiple Errors Encountered
ERR002:An internal error occured
ERR003:Error File could not be opened
ERR004:Memory Allocation Failure
ERR005:Drive not found or Drive already assigned
ERR006:Spare not found or Spare already assigned
ERR007:Capture File could not be opened
ERR008:Argument Error
ERR009:No Controllers found
ERR010:Error Negotiating with controller
ERR021:Input File could not be opened
ERR022:An error occured while parsing input file
ERR013:A configuration error occured
ERR113:Invalid Logical Drive Number specified
ERR202:The requested logical drive size cannot be supported
ERR203:The RAID Level cannot be supported
ERR011:Array Profile does not contain any drive specification
ERR206:The logical drive size specified is too small
ERR201:The logical drive stripe size cannot be supported

[JohnWRuffo]

Thanks Gordon:

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.

[Gordon Leonard]

Whst is the course number?

[JohnWRuffo]

We had looked at the MSA1000 course 9711. It gave us no real info on the underlying commands used in the GUI.

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.

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.

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
we have found, this is NOT the case.

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.

Any HP Engineer want to comment about this?