cpqacuxe

Synopsis

Capture: CPQACUXE -C FILENAME [-internal | -external] -E FILENAME
Input: CPQACUXE -I FILENAME [-internal | -external] [reset] -E FILENAME
Input with reset: CPQACUXE -i-with-reset FILENAME [-internal | -external] [reset] -E FILENAME

Description

The cpqacuxe utility operates on the configuration of storage array controllers. The cpqacuxe utility enables the array configuration on one server to be replicated on other servers with similar array storage resources. The cpqacuxe utility is located in the utilities directory in the toolkit as a tar file. The main toolkit launch script expands the tar file before executing it.

The cpqacuxe utility has three modes of operation:

In capture mode, it reads the configuration of all internal and external array controllers that are connected to a server and saves this data to a file. You can then use this file to replicate the array configuration on other servers that have similar storage resources.
In input mode, it applies the array configuration that is specified in a file to a target server. You can create this file using the capture mode and leave it unmodified, edit the capture file, or even create the file from scratch.
In input mode with reset, it applies the array configuration that is specified in a file to a target server, clearing any existing controller configuration with total data loss. You can use this mode to overwrite the current controller array and logical drive settings.

cpqacuxe Capture Utility

The cpqacuxe utility captures the configuration of all array controllers on the server to a capture file. This capture file can then be used in input mode to replicate the configuration to other array controllers. Also, the capture file can be edited and then reused in input mode. You can then use this file to replicate the array configuration on other servers that have similar storage resources.

Use of the -internal or -external command line switches effectively filter the controllers captured. For example, if the -external switch is used, any controllers internal to the host computer are not captured in the output file.

A typical array configuration capture file is similar to the following:

Action = Configure  

Method = Custom  

; Controller Options  
; Controller Compaq Smart Array 5300  

Controller = Slot 5  
ReadCache = 50  
WriteCache = 50  
RebuildPriority = Low  
ExpandPriority = Low   

; Array Options  
Array = A  
OnlineSpare = No  
Drive = 2:0,2:1   

; Logical Drive Options  
LogicalDrive = 1  
RAID = 1  Size = 17359  
Sectors = 32  
StripeSize = 256  
ArrayAccelerator = Enabled   

; HBA SSP Specifications  
HBA_WW_ID= 10000000C9272B34  
ConnectionName= TestConn  
HostMode= Linux

Table 6-5 Options

Option	Description
`-C FILENAME`	Specifies the capture file. The capture filename is optional. If no capture file is specified, the default capture file is `acucapt.ini` in the ACU working directory.
`-E FILENAME`	Specifies the error file. The error filename is optional. If no error file is specified, the default error file is `error.ini` in the ACU working directory.
`–internal`	Limits the capture to internal controllers.
`–external`	Limits the capture to external controllers.
`-h`	Displays help information.

The cpqacuxe Utility

The cpqacuxe utility uses a text file that contains options and parameters required to configure array controllers. Lines of the script file can be blank or in the form option = value. The cpqacuxe utility parses the file in a case-insensitive manner. Semicolons are used for comments within script files. If the first character in the line is a semicolon, the line is a comment and the cpqacuxe utility ignores everything up to the next line. The valid options in script files generated and read by the ACU utility are divided into the following categories:

Control options— Define the overall behavior of the cpqacuxe utility when it processes the scripts and stamps configurations. Control options can occur only once in the script file and must be the first options in the file.
Controller options— Define a controller or set of controllers used in the configuration. This set of options must start with the Controller option. All other options up to the next Controller option are assumed to belong to the controller that is being defined. These options can be specified in any order, but an option from another category of options cannot occur between any two options in this category.
Array options— Specify and describe a particular array in the configuration. These options are invalid if there is not a preceding controller option section. This set of options must start with the Array option, and all the following options up to the next Array or Controller option are assumed to belong to the array being defined. These options can be specified in any order, but an option from another category of options cannot occur between any two options in this category.
Logical drive options— Specify and describe a particular logical drive in the configuration. These options are invalid if there is no preceding array option. This set of options must start with the LogicalDrive option, and all the following options up to the next LogicalDrive, Array, or Controller option are assumed to belong to the logical drive being defined. These options can be specified in any order, but an option from another category of options cannot occur between any two options from this category. In general, Logical Drives must be listed in the input file in increasing order, unless existing drives are being reconfigured without data loss.
HBA options— Specify and describe a Host Bus Adapter (HBA) SSP configuration. These options are invalid if there are no preceding logical drive options. This set of options must start with the HBA_WW_ID option, and all the following options up to the next LogicalDrive, Array, Controller, or HBA_WW_ID option are assumed to belong to the HBA being defined. These options can be specified in any order, but an option from another category of options cannot occur between any two options from this category.

Automatic Script File Format

The automatic script is used to apply automatic configuration rules to unconfigured or configured controllers. If the -i-with-reset or –reset command line switch is used, the existing controller configuration is cleared with data loss before the new configuration is applied, effectively making it an unconfigured controller. The cpqacuxe utility automatic scripting uses the same configuration suggested that is used in the Express path of the cpqacuxe utility GUI. Therefore, the automatic configuration rules are the same as the cpqacuxe utility GUI Express path.

The following is an automatic script file syntax:

Action = Configure|Reconfigure
Method = Auto
; Controller Options
; There can be multiple controller specifications in the file
Controller = All | First | Slot [N][:N] |
SerialNumber [N]| WWN [N] |
IOCabinet [N],IOBay [N],IOChassis [N],
Slot [N],Cabinet [N],Cell [N]
ClearConfigurationWithDataLoss = Yes|No
LicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
DeleteLicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
RaidArrayId = “XXXXXXXXXXXXXXXXXXXX”
ReadCache = 0|10|20|25|30|40|50|60|70|75|80|90|100
WriteCache = 0|10|20|25|30|40|50|60|70|75|80|90|100
RebuildPriority = Low|Medium|High
ExpandPriority = Low|Medium|High
SurfaceScanDelay= N
OnlineSpare = Yes|No
RAID = 0|1|4|5|6|ADG

Table 6-6 Automatic Script File Options

Option	Value
`Action`	Defines if you are changing existing arrays and logical drives or adding new ones. This option is required. `Configure`: Existing arrays are not modified. If unassigned physical drives exist, new arrays and logical drives are automatically created. `Reconfigure`: Existing arrays might be modified in a non-data-destructive manner. If unassigned physical drives exist, existing arrays might automatically be expanded and new arrays automatically created. New logical drives are created on the expanded and newly created arrays. If the -i-with-reset or -reset command line switch is used, the existing controller configuration is cleared with data loss as the first step in the configurations process, regardless of the setting of the Action mode.
`Method`	Defines whether you are in Automatic or Custom mode. `Auto` is the default value.
`Controller`	Identifies to which controllers to apply the configuration. This option is required. `Slot [N][:N]`: The internal controller with slot number `N` is used. External controllers can be identified by appending the Port Number. For example, an Modular Smart Array (MSA) 1500 connected to a SA6402 might be found at “Slot 4:2,” where 4 is the internal Slot number and 2 is the SCSI port. `WWN [N]`: The external controller with World-Wide Name (WWN) `N` is used. `SerialNumber [N]`: The shared storage controller with serial number `N` is used. `All`: All detected internal and external controllers in the system are used. `First`: The first controller found, based on the controller with the lowest PCI slot number. `IOCabinet [N], IOBay [N], IOChassis [N],Slot [N], Cabinet [N], Cell [N]`: The controller identified by the IPF Slot path information is used. Use of the -internal” and -external command line switches influences what is regarded as the first controller. For example, if the -external switch is used, the first controller is the first external controller discovered, regardless of the number of internal controllers in the host system.
`ClearConfigurationWithDataLoss`	Specifies if the configuration should be cleared. This option causes data loss since it deletes all logical drives on the controller. Other scripting commands can exist after this option to recreate a new configuration. This option is optional. `Yes`: The configuration is cleared. All arrays and logical drives on the controller are deleted. `No`: The configuration is not cleared. This is the default option if the command is not specified in the script file
`RAIDArrayID`	Specifies the RaidArrayID for controllers that support RaidArrayID. This is a user-defined string to identify controllers. Currently, RaidArrayIDs are only supported by Fibre and shared-storage controllers. `"XXXXXXXXXXXXXXXXXXXX"` Varying length string that can consist of any of the following characters: a-z A-Z 0-9 ! @ # * ( ) , - _ + : . / [space] This string has a maximum length that varies depending on the type of controller. For, RA4x00 controllers, the max length is 24 characters. For, other controllers, the max length is 20 characters. The quotes surrounding the string are optional. Using quotes allows leading space characters to be used in the RaidArrayID. This string cannot end in a space character.
`LicenseKey`	Specifies a license key to install a controller feature. `XXXXX-XXXXX-XXXXX-XXXXX-XXXXX` This is a 25-character key separated by hyphens. The hyphens are optional.
`DeleteLicenseKey`	Specifies a license key to uninstall a controller feature. If the license key is installed, it is uninstalled. `XXXXX-XXXXX-XXXXX-XXXXX-XXXXX` This is a 25-character key separated by hyphens. The hyphens are optional.
`ReadCache`	Specifies the Read Cache percentage. This option is not required. If this option is not specified, the Read/Write cache ratio remains unchanged. This value is a numeric value from 0 to 100. It must form a valid read/write cache ratio that is supported on the controller with the WriteCache option.
`WriteCache`	Specifies the Write Cache percentage. This option is not required. If this option is not specified, the Read/Write cache ratio remains unchanged. This value is a numeric value from 0 to 100. It must form a valid read/write cache ratio that is supported on the controller with the ReadCache option.
`RebuildPriority`	Specifies the Rebuild Priority. This option is not required. If this option is not specified, the Rebuild Priority remains unchanged. Low Medium High
`ExpandPriority`	Specifies the Expand Priority. This option is not required. If this option is not specified, the Expand Priority remains unchanged. Low Medium High
`SurfaceScanDelay`	Specifies the Surface Scan Delay in seconds. This option is not required. If this option is not specified, the Surface Scan Delay remains unchanged. `N`: This value is a numeric value between 1 and 30 seconds.
`OnlineSpare`	Specifies if Automatic Configuration should attempt to add spares. This option is not required. This option is ignored in Reconfigure mode if there is an existing configuration on the controller. In this case, the configuration suggestskes spare decisions based on the existing configuration. `Yes`: Automatic Configuration attempts to add spares to each array. This is the default value for the OnlineSpare option if it is not specified. `No`: Automatic Configuration does not add spares to each array.
`RAID`	Specifies the RAID level that Automatic Configuraiton uses. It is not required. If the RAID option is not specified or the specified RAID option is not possible, the default RAID is the highest RAID level that is supported with the current state of the controller. This option is ignored in Reconfigure mode if there is an existing configuration on the controller. In this case, the configuration suggester makes RAID decisions based on the existing configuration. `ADG`: RAID ADG is equivalent to RAID 6 `6`: RAID 6 `5`: RAID 5 `4`: RAID 4 `1`: RAID 1 `0`: RAID 0

Custom Script File Format

The custom script is used to apply custom configurations to unconfigured or configured controllers. You can specify exactly the configuration needed.

The following is a custom script file syntax:

Action = Configure|Reconfigure
Method = Custom
; Controller Options
; There can be multiple controller specifications in the file
Controller = All|Slot [N][:N]|WWN [N]| First |
SerialNumber [N]|
IOCabinet [N],IOBay [N],IOChassis [N],
Slot [N],Cabinet [N],Cell [N]
ClearConfigurationWithDataLoss = Yes|No
LicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
DeleteLicenseKey = XXXXX-XXXXX-XXXXX-XXXXX-XXXXX
RaidArrayId = “XXXXXXXXXXXXXXXXXXXX”
ReadCache = 0|10|20|25|30|40|50|60|70|75|80|90|100
WriteCache = 0|10|20|25|30|40|50|60|70|75|80|90|100
RebuildPriority = Low|Medium|High
ExpandPriority = Low|Medium|High
SurfaceScanDelay= N
SSPState = Enable|Disable
PreferredPathMode= Auto|Manual
; Array Options
; There can be multiple array specifications in the file
Array = A|B|C|D|E|F|…Z|a|b|c|d|e|f
OnlineSpare = Port:ID,… | Box:Bay,… | Port:Box:Bay | None | N
Drive = Port:ID,… | Box:Bay,… | Port:Box:Bay,… | N | *
DriveType= SCSI | SAS | SATA
; Logical Drive Options
; There can be multiple logical drive specifications in the file
LogicalDrive = 1|2|3|…32
RAID = 0|1|4|5|6|ADG|AUTO
Size = [N]|Max
Sectors = 32|63
StripeSize = 8|16|32|64|128|256
ArrayAccelerator= Enable|Disable
ResourceVolumeOwner= N
LogicalDriveSSPState = Enable|Disable
SSPAdaptersWithAccess = [N],[N]…|None
PreferredPath = 1|2
; HBA Options
; There can be multiple HBA specifications in the file
HBA_WW_ID = WWN
ConnectionName = UserDefinedName
HostMode = Default|Windows|Windows(degrade
|OpenVMS|Tru64|Linux|Solaris|Netware|HP|Windows_SP2_and_

Table 6-7 Custom Script File Options

Option	Value
`Action`	Defines if you are changing existing arrays and logical drives or adding new ones. This option is required. `Configure`: Existing arrays are not modified. Only new arrays and new logical drives can be created in this mode. `Reconfigure`: Existing arrays and logical drives might be modified in a non-data-destructive manner. You can create new arrays, expand existing arrays, create new logical drives, migrate existing logical drives, and extend existing logical drives If the -i-with-reset or -reset command line switch is used, the existing controller configuration is cleared with data loss as the first step in the configurations process, regardless of the setting of the Action mode.
`Method`	Defines if you are in Automatic or Custom mode. Specify `Custom` for a custom script.
`Controller`	Identifies to which controllers to apply the configuration. This option is required. `Slot [N][:N]`: The internal controller with slot number N is used. External controllers can be identified by appending the Port Number. For example, an MSA1500 connected to a SA6402 might be found at “Slot 4:2,” where 4 is the internal Slot number and 2 is the SCSI port. `WWN [N]`: The external controller with World-Wide Name(WWN) N is used. `SerialNumber [N]`: The shared storage controller with serial number N is used. `All`: All detected internal and external controllers in the system are used. `First`: The first controller found, based on the controller with the lowest PCI slot number. `IOCabinet [N], IOBay [N], IOChassis [N],Slot [N], Cabinet [N], Cell [N]`: The controller identified by the IPF Slot path information is used. Use of the -internal” and -external command line switches influences what is regarded as the first controller. For example, if the -external switch is used, the first controller is the first external controller discovered, regardless of the number of internal controllers in the host system.
`ClearConfigurationWithDataLoss`	Specifies if the configuration should be cleared. This option causes data loss since it deletes all logical drives on the controller. Other scripting commands can exist after this option to recreate a new configuration. This option is optional. `Yes`: The configuration is cleared. All arrays and logical drives on the controller are deleted. `No`: The configuration is not cleared. This is the default option if the command is not specified in the script file
`RAIDArrayID`	Specifies the RaidArrayID for controllers that support RaidArrayID. This is a user-defined string to identify controllers. Currently, RaidArrayIDs are only supported by Fibre and shared-storage controllers. `"XXXXXXXXXXXXXXXXXXXX"` Varying length string that can consist of any of the following characters: a-z A-Z 0-9 ! @ # * ( ) , - _ + : . / [space] This string has a maximum length that varies depending on the type of controller. For, RA4x00 controllers, the max length is 24 characters. For, other controllers, the max length is 20 characters. The quotes surrounding the string are optional. Using quotes allows leading space characters to be used in the RaidArrayID. This string cannot end in a space character.
`LicenseKey`	Specifies a license key to install a controller feature. `XXXXX-XXXXX-XXXXX-XXXXX-XXXXX` This is a 25-character key separated by hyphens. The hyphens are optional.
`DeleteLicenseKey`	Specifies a license key to uninstall a controller feature. If the license key is installed, it is uninstalled. `XXXXX-XXXXX-XXXXX-XXXXX-XXXXX` This is a 25-character key separated by hyphens. The hyphens are optional.
`ReadCache`	Specifies the Read Cache percentage. This option is not required. If this option is not specified, the Read/Write cache ratio remains unchanged. This value is a numeric value from 0 to 100. It must form a valid read/write cache ratio that is supported on the controller with the WriteCache option.
`WriteCache`	Specifies the Write Cache percentage. This option is not required. If this option is not specified, the Read/Write cache ratio remains unchanged. This value is a numeric value from 0 to 100. It must form a valid read/write cache ratio that is supported on the controller with the ReadCache option.
`RebuildPriority`	Specifies the Rebuild Priority. This option is not required. If this option is not specified, the Rebuild Priority remains unchanged. `Low` `Medium` `High`
`ExpandPriority`	Specifies the Expand Priority. This option is not required. If this option is not specified, the Expand Priority remains unchanged. `Low` `Medium` `High`
`SurfaceScanDelay`	Specifies the Surface Scan Delay in seconds. This option is not required. If this option is not specified, the Surface Scan Delay remains unchanged. `N`: This value is a numeric value between 1 and 30 seconds.
`SSPState`	Specifies the SSP State for controllers that support SSP that is enabled/disabled on a controller basis. This option is not required. If this option is not specified, the SSP State remains unchanged. Currently, only Fibre and shared-storage controllers support SSP. This command is not valid for the RA4x00 controller because RA4x00 controllers support SSP that is enabled/disabled on a logical drive basis. `Enable`: Enables SSP for the controller. `Disable`: Disables SSP for the controller. SSP only remains enabled if the SSPAdaptersWithAccess command specifies an adapter for one or more logical drives. If no adapters with access are specified for any logical drives, the SSP State reverts back to disabled.
`PreferredPathMode`	Specifies the preferred path mode when redundant array controllers are in an active-active configuration. This option is only available for certain redundant array controllers. If the option is not specified, it remains unchanged. This option is ignored in active-standby configurations. This option is optional. `Auto`: This is the default value. The array controller automatically determines which logical drives are assigned to each active array controller for I/O. The array controller dynamically load balances the logical drive paths. `Manual`: Manually specify which logical drives are assigned to each active array controller for I/O. The array controller does not change the paths. The paths are specified using the PreferredPath command in the LogicalDrive section.
`Array`	Specifies the Array ID. `[A-Z,a-f]`: In Configure mode, a new array is created. The array letter specified must be the next available array letter in the existing configuration. In Reconfigure mode, the array letter can identify an existing array, or it can identify the next available array letter in the existing configuration to create a new array.
`Drive`	Specifies the physical drives for the array. A comma separated list specifies the location of physical drives that are to be used in the array. In Configure mode, the physical drives listed are used to create the new array. In Reconfigure mode, all physical drives that are in the array must be listed. Any additional physical drives that are listed are added to the array for an array expansion. `[X]:[Y], …`: The Port:ID for controllers that use Port/ID drive numbering schemes or the Box:Bay for controllers that use Box/Bay numbering schemes. `[X]:[Y]:[Z],…`: The Port:Box:Bay for SAS controllers. `N`: The number of spares that are added to the array. The cpqacuxe utility select the best available unused physical drives for the spares. `*`: All available physical drives are added to the array. Specifying this option consumes all drives and makes adding spare drives impossible.
`DriveType`	Restricts the array and operations on the array to the specified type of physical drive. `SCSI`: Use only SCSI drives. `SAS`: Use only SAS drives. `SATA`: Use only SATA drives.
`OnlineSpare`	Specifies the spare drives for the array. A comma separated list specifies the location of spare drives that are to be used in the array. `[X]:[Y], …`: The Port:ID for controllers that use Port/ID drive numbering schemes or the Box:Bay for controllers that use Box/Bay numbering schemes. `[X]:[Y]:[Z],…`: The Port:Box:Bay for SAS controllers. `None`: No spares are added to the array and any existing spares on the array are removed. In Configure mode if this option is not specified, `None` is the default value. In Reconfigure mode if this option is not specified, the spare state of the array remains unchanged. `N`: The number of spares that are added to the array. The cpqacuxe utility selects the fest available unused physical drives for the spares.
`LogicalDrive`	Specifies the Logical Drive ID. `[1-32]`: In Configure mode, a new logical drive is created. The logical drive number specified must be the next available logical drive number in the existing configuration. In Reconfigure mode, the logical drive number can identify an existing logical drive, or it can identify the next available logical drive in the existing configuration to create a new logical drive. In most cases logical drives must appear in the configuration file in increasing order.
`RAID`	Specifies the RAID level for the current logical drive. In Configure mode, the RAID is the RAID for the new logical drive. In Reconfigure mode, if the logical drive already exists and the RAID is different than the existing RAID on the logical drive. The cpqacuxe utility then attempts to migrate the logical drive to the specified RAID. The RAID option is not required. If the RAID is not specified for a new logical drive, the RAID are the highest RAID level that is supported on the current Array. If the RAID is not specified for an existing logical drive in Reconfigure mode, then the current RAID setting remains unchanged. `AUTO`: The best available RAID level is selected based on the number of disks in the array. This is normally be the highest RAID level supported. `ADG`: RAID ADG is equivalent to RAID 6. `6`: RAID 6 `5`: RAID 5 `4`: RAID 4 `1`: RAID 1 `0`: RAID 0
`Size`	Specifies the size of the logical drive. If the logical drive is new, the size is for the new logical drive. In Reconfigure mode, if the logical drive already exists and the size is different than the existing size of the logical drive, the cpqacuxe utility attempts to extend the logical drive to the new size. This option is not required. If the size is not specified for a new logical drive, the default is `MAX`. If the size is not specified for an existing logical drive, the current logical drive size remains unchanged. `[N]`: The size in MB. `MAX`: Uses the maximum size possible for the logical drive.
`Sectors`	Specifies the Max Boot setting (Sectors Per Track) for the logical drive. The Sectors option is not required. If the logical drive is new, the default is 32. If the logical drive already exists, then the default is the current Sectors setting on the logical drive. `32`: Disable Max Boot (32 sectors per track). 63: Enable Max Boot (63 sectors per track).
`StripeSize`	Specifies the Stripe Size for the logical drive in KB. In Configure mode, the Stripe Size is the Stripe Size for the new logical drive. In Reconfigure mode, if the logical drive already exists and the Stripe Size is different than the existing Stripe Size on the logical drive, the cpqacuxe utility attempts to migrate the logical drive to the specified Stripe Size. The Stripe Size option is not required. If the Stripe Size is not specified for a new logical drive, the Stripe Size is the default Stripe Size for the RAID level of the logical drive. If the Stripe Size is not specified for an existing logical drive in Reconfigure mode and the user is not migrating the RAID, then the current Stripe Size setting remains unchanged. The following Stripe Size values are available: `8`: 8 KB `16`: 16 KB `32`: 32 KB `64`: 64 KB `256`: 256 KB `16`: 16 KB The following Stripe Size values are available for RAIDS): RAID 0: `8, 16, 32, 64, 128, 256` (default is 128) RAID 1: `8, 16, 32, 64, 128, 256` (default is 128) RAID 4: `8, 16, 32, 64` (default is 16) RAID 5: `8, 16, 32, 64` (default is 16) RAID ADG: `8, 16, 32, 64 (default is 16)`
`ArrayAccelerator`	Specifies the Array Accelerator setting for the logical drive. `Enable`: Enables the Array Accelerator for the logical drive. This is the default setting for new logical drives. `Disable`: Disables the Array Accelerator for the logical drive.
`ResourceVolumeOwner`	Specifies that this logical drive should be a snapshot resource volume and specifies the owner logical drive ID. If this command is not specified, the logical drive is a normal data volume. `N`: This value is the logical drive ID of an existing logical drive which owns this snapshot resource volume.
`LogicalDriveSSPState`	Specifies the SSP State for a logical drive. This command is only valid for controllers that support SSP that is enabled/disabled on a logical drive basis. This option is not required. If this option is not specified, the SSP State remains unchanged for existing logical drives and is disabled for new logical drives. Currently, only the RA4x00 controller supports SSP that is enabled/disabled on a logical drive basis. For other controllers that support SSP, see SSPState command. `Enable`: Enables SSP for the logical drive. `Disable`: Disables SSP for the logical drive.
`SSPAdaptersWithAccess`	Specifies the SSP adapters that have access to a logical drive. This command is only valid for controllers that support SSP. This option is processed only if the SSPState or LogicalDriveSSPState is set to Enable. Otherwise, this command is ignored. `[N],[N]…`: A comma separated list of SSP adapter IDs that are granted access to the logical drive. `None`: No SSP adapters are granted access to the logical drive.
`PreferredPath`	Specifies the preferred path for the logical drive when redundant array controllers are in an active-active redundancy mode and the preferred path mode is set to Manual. This option is only available for certain redundant array controllers. If the option is not specified, the preferred path remains unchanged for the logical drive. This option is ignored in active-standby configurations and in active-active configurations when the preferred path mode is Auto. `1`: This is the default value. The controller in chassis-slot 1 is the preferred controller I/O path for the logical drive. `2`: The controller in chassis-slot 2 is the preferred controller I/O path for the logical drive.
`HBA_WW_ID`	Specifies to which HBA to apply the configuration changes. `WWN [N]`: The external controller with World-Wide Name (WWN) N is used.
`ConnectionName`	A user defined string used as the connection name for the specified HBA. `“XXXXXXXXXXXXXXXXXXXX”` Varying length string that can consist of any of the following characters: a-z A-Z 0-9 ! @ # * ( ) , - _ + : . / [space]. This string has a maximum length of 16 characters and can contain embedded spaces but cannot end in a space character.
`HostMode`	Specifies the Host Mode for the selected HBA. Setting the Host Mode optimizes the storage array for the selected OS. The available host modes for an HBA are device specific, and not all modes are available on all devices. Not all HBAs support a Host Mode. The following OS options might be available: `Default` `Windows` `Windows (degrade)` `OpenVMS` `TRU64` `Linux` `Solaris` `Netware` `HP` `Windows_SP2`

Error Reporting

When using the cpqacuxe utility, any errors that are encountered are logged to the error.ini file or the specified error file. Error codes are also returned to the calling process, allowing scripting clients to key off the return code instead of having to parse the error file.

The error file displays the error code, error message, and if possible, lists the controller, array, or logical drive associated with the error.

The format of the error file is as follows:

Line1:ACU Configuration Replication Error Line2:ERROR: (<error code>) <error description>
Line3:Controller: Slot # | SerialNumber # | WWN #
Line4:Array: #
Line5: Logical Drive: #

Table 6-8 Error Codes

Code	Error	Reason
0	`Success`	Success
1	`General error`	Problem spawning ACU process (user is not authenticated to use ACU or ACU is already running).
2866	`Failure opening capture file '%s'`	Error opening capture file.
2867	`Failure opening input file '%s'`	Error opening input file.
2868	`Failure opening error file '%s'`	Error opening error file.
2869	`‘%s’ command expected`	The specified command is missing or in the incorrect place in the file.
2870	`'%s' is not a supported command`	The specified command is not a valid scripting command.
2871	`'%s' is not a Controller command`	The specified command does not belong in the Controller section of the script file.
2872	`'%s' is not an Array command`	The specified command does not belong in the Array section of the script file.
2873	`'%s' is not a Logical Drive command`	The specified command does not belong in the LogicalDrive section of the script file.
2874	`’%s' is not an HBA command`	A command found in the HBA section is not a valid command for this section.
2875	`More than one '%s' command cannot exist in the same section`	The specified command is used more than once in the same section. It should only be used once per section.
2821	`No controllers detected`	No controllers were detected. This error applies to input mode only.
1102	`Slot information is not available`	Input mode cannot be run on internal controllers without slot information online. For Windows, this means the System Management Driver has to be loaded.
2819	`Controller '%s' is invalid`	The controller specified is not specified correctly.
2820	`Could not detect Controller '%s'`	The controller specified was not detected.
2818	`Invalid Method`	Invalid Method value.
2819	`Invalid Controller`	Invalid Controller value.
2822	`Invalid Read Cache/Write Cache Ratio`	The specified Read Cache/Write Cache Ratio is not supported either by the controller or the current controller configuration.
2823	`Invalid Rebuild Priority`	The specified Rebuild Priority is not supported.
2824	`Invalid Expand Priority`	The specified Expand Priority is not supported. Also, this error occurs if the controller does not allow expansion and therefore does not support Expand Priority.
2857	`Invalid Surface Scan Delay`	Invalid Surface Scan Delay
2849	`Invalid ClearConfigurationWithDataLoss parameter`	The specified ClearConfigurationWithDataLoss parameter is not correct.
2825	`Invalid Array`	The Array ID is invalid.
2826	`Array not specified`	The array command is missing from the script file. Some commands were found that require an array to work on.
2827	`New Array ID does not match the next available Array ID`	The Array ID in the script file does not match the Array ID of the newly created array. For example, if you have Array A already and the script file tries to create Array C (without Array B), the script generates this error.
2828	`New Array ID already exists`	When running in Configure mode, this error happens when the Array ID in the script file already exists in the configuration. Configure mode can only create new arrays.
2829	`Cannot create Array`	The controller does not allow a new array to be created. This could be because there are no unassigned physical drives on the controller, or the maximum number of arrays or logical drives has already been reached.
2830	`Cannot expand Array`	The array could not be expanded. This could be because the controller does not support expansion, or the current configuration does not allow expansion to occur on the array.
2831	`Cannot change Array Spare`	The spare state of the array could not be changed. This can happen when you are trying to add a spare or drop a spare. The current configuration does not allow a spare state change for the array.
2832	`Invalid Physical Drive`	The physical drive listed for the array is not a valid physical drive, or it is a physical drive that is not capable of being placed in the array.
2833	`Invalid Spare`	The spare drive listed for the array is not a valid spare drive, or it is a drive that is not capable of being placed on the array as a spare.
1053	`Cannot remove Physical Drives from existing array`	One or more drives are not listed in an existing array. This is illegal because removing physical drives from a configured array causes data loss.
1052	`Array requires an odd number of drives`	This error message can occur if the user is attempting to add an odd number of drives to an existing array that has RAID 1 logical drives. If the controller has RAID 1 logical drives and supports RAID 1 -> RAID 5/RAID ADG migration, this error does not occur. However, if the controller does not support migration, this error occurs.
2834	`Invalid Logical Drive`	The Logical Drive ID is not valid.
2835	`Logical Drive not specified`	The Logical Drive command is missing from the script file. Some commands were found that require a Logical Drive to work on.
2836	`New Logical Drive ID does not match the next available Logical Drive ID`	The Logical Drive ID in the script file does not match the Logical Drive ID of the newly created logical drive. For example, if you already have Logical Drive 1 and the script file attempts to create Logical Drive 3 (without Logical Drive 2), the script generates this error. This error can occur when using an input file with logical drive numbers that are not sequential. In this case, the logical drive numbers need to be changed so that they are sequential in the input file.
2837	`New Logical Drive ID already exists`	When running in Configure mode, this error occurs when the Logical Drive ID in the script file already exists in the configuration. Configure mode can only create new logical drives.
2838	`Cannot create Logical Drive`	The controller does not allow a new logical drive to be created. This could be because there is no free space on the array, or the maximum number of logical drives has already been reached.
2839	`Cannot migrate Logical Drive Raid`	The controller does not support migration, or the current configuration of the controller does not allow migration to occur.
2840	`Cannot migrate Logical Drive Stripe Size`	The controller does not support migration, or the current configuration of the controller does not allow migration to occur.
2841	`Cannot extend Logical Drive`	The controller does not support extension, or the current configuration of the controller does not allow extension to occur. For example, there might be no free space on an array, so extension is not supported for the logical drive.
2842	`Invalid Raid`	The specified RAID is invalid or is not possible with the current configuration.
2843	`Invalid Size`	The specified size is invalid or is not possible with the current configuration.
2844	`Invalid Stripe Size`	The specified stripe size is invalid, is not supported with the current RAID level, or is not supported with the current configuration.
2846	`Cannot change Logical Drive Sectors`	You cannot change the max boot on a configured logical drive. This leads to data loss.
2845	`Invalid Sectors`	The specified Max Boot setting is invalid, or is not supported with the current configuration.
2848	`Cannot change Logical Drive Array Accelerator Setting`	The current controller configuration does not support changing the logical drive Array Accelerator state.
2847	`Invalid Array Accelerator Setting`	The specified Array Accelerator setting is invalid or is not supported with the current configuration.
290	`Error communicating with Controller`	There was a problem communicating with one or more controllers.
278-282, 2564	`Controller is locked by another machine or user`	One or more controllers is locked by another machine or user.
268	`Error saving Controller`	There was a problem saving one or more controller configurations.
1065-1066	`Too many coinciding expansion, migration, or extension operations`	This error is the “invalid increase/decrease” in logical drive offset error. This can happen when too many unsaved expansions, extensions, or migrations are tried at the same time.
1110	`Controller does not support license keys`	The controller does not support license key entry or deletion.
1093	`Controller requires physical drives to set license keys`	The controller requires physical drives for license keys.
1114	`Controller requires non-failed physical drives to set license keys`	The controller requires non-failed physical drives for license keys.
1111	`Invalid license key`	The entered license key is not a valid license key.
1112	`Controller has maximum number of license keys`	The controller already has the maximum number of license keys installed.
1110	`License key is not a controller feature license key`	The entered license key is not a controller feature license key.
2850	`Controller does not support Raid Array ID`	The controller does not support Raid Array ID.
2851	`Invalid Raid Array ID`	The entered Raid Array ID is invalid. The Raid Array ID can only consist of the following characters: a-z A-Z 0-9 ! @ # * ( ) , - _ + : . / [space]. It cannot end with a space character or exceed the maximum number of characters allowed by the controller.
1091	`Controller does not support SSP`	The controller does not support SSP.
2855	`Controller does not support Logical Drive SSP states. Use 'SSPState' Controller command to set the Controller SSP state`	The Controller does not support Logical Drive SSP states. Use SSPState controller command to set the Controller SSP state.
2856	`Controller does not support Controller SSP state. Use 'LogicalDriveSSPState' Logical Drive command to set SSP states for each Logical Drive`	Controller does not support Controller SSP state. Use LogicalDriveSSPState logical drive command to set SSP states for each Logical Drive.
2853	`Cannot change SSP settings`	The SSP settings cannot be changed for the controller or logical drive.
2854	`Invalid SSP Adapter ID`	The adapter ID is not a valid adapter ID that was detected by the controller.
2852	`Invalid SSP State`	The requested SSP State is not a valid SSP state.
2858	`Controller does not support snapshot resource volume feature`	The controller does not support the snapshot resource volume feature.
2859	`Invalid Resource Volume Owner`	The specified Resource Volume Owner is not valid. The Resource Volume Owner should be a valid existing logical drive ID.
2860	`Cannot change Resource Volume Owner`	The Resource Volume owner cannot be changed if it is a configured logical drive.
2861	`Controller does not support redundancy settings`	The controller is not redundant or does not support redundancy settings.
2864	`Invalid Preferred Path Mode`	The preferred path mode is not a valid preferred path mode or the controller is not available.
2865	`Invalid Preferred Path`	The preferred path specified is not a valid chassis-slot for an available active controller or the controller is not available.
2876	`Invalid Physical Drive Count`	Invalid Physical Drive count. A possible reason is that more disks were requested than available of the current DriveType.
2877	`No Spares Available`	No suitable Spares available.
2878	`Spare Request for RAID0 is Invalid`	Spares are not supported in RAID0-only Arrays.
2879	`Reset and Reconfigure combined Error`	Mode is Reconfigure and a controller reset with data loss was specified.
2880	`Invalid Drive Type Specified`	Invalid Disk Type specified.
516	`Internal Error`	An internal ACU error has occurred. This error should never occur. If it does, there is a problem with ACU, and some error is not being identified properly.