|
» |
|
|
|
What's New? |
|
|
- Configuration files have been modified to make ACUXE compatible with HP
System Management Homepage V2.0
|
Supported OpenVMS Versions |
|
|
- OpenVMS Alpha V7.3-2, V8.2, and V8.3
- OpenVMS Integrity servers V8.2, V8.2-1, V8.3, and V8.3-1H1
|
|
|
|
- SA5300A and SA6400A on OpenVMS Alpha
- SA6402 and SA6404 on OpenVMS Integrity
servers
|
Hardware Requirements |
|
|
|
Software Requirements |
|
|
or
|
Supported Versions of ACUXE |
|
|
HP provides support only for ACUXE V6.4 or later.
|
Starting ACUXE |
|
|
To start ACUXE, follow these steps:
Note: HP Insight Management Agents and HP System Management Homepage cannot
be started at the same time.
Insight Management Agents:
- On an OpenVMS system, log on using the SYSTEM account.
- Start Management Agents using an SYSTEM account. To start Management Agents, enter the following command:
$@SYS$SPECIFIC:[WBEM]WBEM$STARTUP.COM - Wait until the WBEM$SERVER_RUNNING logical is defined as TRUE.
- Grant the WBEM$ADMIN identifier to SYSTEM user with administrator privileges. To grant this identifier, enter the following commands:
$ SET DEFAULT SYS$SYSTEM
$ MCR AUTHORIZE
UAF> GRANT/IDENTIFIER WBEM$ADMIN SYSTEM
UAF> EXIT
- To start ACUXE, enter the following command:
$ @SYS$SPECIFIC:[WBEM.ACUXE]CPQ$ACUXE -R
- Ensure if the CPQ$ACUXE process is running by entering the following command:
$ SHOW SYSTEM/PROC= CPQ$ACUXE
System Management Homepage:
- On an OpenVMS system, log on using the SYSTEM account.
- Start System Management Homepage using an SYSTEM account. To start System Management
Homepage, enter the following command:
$@SYS$STARTUP:SMH$STARTUP.COM
- Wait for few seconds until the APACHE$SMH process is started.
- Grant the SMH$ADMIN identifier to SYSTEM user with administrator privileges. To grant this identifier, enter the following commands:
$ SET DEFAULT SYS$SYSTEM
$ MCR AUTHORIZE
UAF> GRANT/IDENTIFIER SMH$ADMIN SYSTEM
UAF> EXIT
- To start ACUXE, enter the following command:
$ @SYS$SPECIFIC:[WBEM.ACUXE]CPQ$ACUXE -R
- Ensure if the CPQ$ACUXE process is running by entering the following command:
$ SHOW SYSTEM/PROC= CPQ$ACUXE
|
Supported Features on OpenVMS |
|
|
ACUXE on OpenVMS can be operated in both GUI and Scripting mode. Following are the list of tasks supported on OpenVMS.
Note: A "+" in the appropriate column indicates that the feature or procedure is supported and "-" indicates that the feature or procedure is not supported.
Tasks |
Web Interface |
Scripting Support |
Basic configuration or reconfiguration of drives and arrays (create or modify logical drives, change controller settings, set cache ratio) |
+ |
+ |
Configure several systems identically |
+* |
+* |
Configure SSP |
- |
- |
Configure switches |
- |
- |
Copy the configuration of one system to several other systems |
- |
+ |
Disable a redundant controller |
- |
- |
Enable or disable Logical drive with write/read cache |
+ |
+ |
Identify devices by causing the LEDs to blink |
+ |
- |
Re-enable a failed logical drive |
+ |
+ |
Set the surface scan delay |
+ |
+ |
Split a RAID 1 array, or recombine a split Array |
- |
- |
Max Boot |
- |
- |
MSA and Smart Array cluster storage controllers |
- |
- |
Set the preferred controller for a logical drive(in systems that support redundant controllers) |
- |
- |
* Scripting is more efficient for these tasks.
Following is the list of supported configuration or
reconfiguration of Drives and Arrays that are supported on OpenVMS:
Name |
Description |
Controller |
Controller Settings, Logical Drive Array Accelerator Settings, Create Array, Clear Configuration, More information |
Array |
Assign Spare, Create Logical Drive, Delete, Expand, Remove Spare, More Information |
Logical drive |
Migrate RAID/Stripe Size, Delete, More Information, Array Acceleration |
Unused space |
Create Logical Drive, More information |
|
Opening ACU in a Browser |
|
|
To open ACU in a browser, follow these steps:
Insight Management Agents:
- Log on to Insight Management Agent. Refer to Insight Management Agents User's Guide for log on instructions.
- The Array Configuration Utility icon appears on the Insight Management Agents Home page. Click the Array Configuration Utility icon to open the ACUXE page.
Note: To access ACUXE, WBEM$ADMIN identifier should be granted to the user.
System Management Homepage:
- Log on to System Management Homepage. Refer to
System Management
Homepage Installation Guide for log on instructions.
- The Array Configuration Utility link appears on the System Management
Homepage under 'Other Agents'. Click the Array Configuration Utility link to open the ACUXE page.
Note: To access ACUXE, SMH$ADMIN identifier should be granted to the user.
|
ACUXE Scripting Support |
|
|
Starting with V6.40 the ACUXE on OpenVMS provides support for scripting. Using ACUXE scripting the user can capture a SmartArray configuration or create a new configuration using a script file
instead of the ACUXE web interface. This is mainly to replicate the Array configuration onto other RAID Arrays.
The command line syntax for ACUXE scripting is:
(Before you start this you have to stop the WBEM$ACUXE process)
$ @SYS$SYSROOT:[WBEM.ACUXE]CPQ$ACUXE [option] [filename]
Options: (use one option only) -c <File Name> Captures configuration to a script file.
(Default file is ACUCAPT.INI.)
-i <Input File> Input configuration from a script file.
(Default file is ACUINPUT.INI)
Any errors encountered during a script command will be logged in a file called ERROR.INI that the ACUXE will create in the current working directory. After executing a script command be sure to check
if an ERROR.INI file has been created and review the file to determine if any errors have occurred.
For details on ACUXE script file syntax refer to the HP Array Configuration User's Guide.
In addition to the c and i scripting options, the following -cli show option is available:
$ @SYS$SYSROOT:[WBEM.ACUXE]CPQ$ACUXE [options]
options: -cli show Shows the storage systems current configuration.
The following list describes features and restrictions of OpenVMS ACUXE scripting:
- The show command is the only command supported by CLI option.
- To identify a controller in a script, use the following syntax:
"Controller= Rad X, Hose Y,Slot Z, Device Name PKXX"
In this syntax, the values X, Y, Z identify the Rad, Hose, and Slot numbers of the
controller and PKXX identifies the device name. The Rad, Hose, Slot, and Device
Name values for a specific controller can be found with Management Agents.
You can also use "Controller=All" for a script command that will be applied
to all controllers.
The following table describes the supported script file options:
Category |
Options |
Decsription |
Control |
|
These options define the overall behavior of ACU when it processes the scripts and creates configurations. Control options can occur only once in a script file and must be the first option
listed.
|
Controller |
- Controller
- ClearConfigurationWithDataLoss
- ReadCache
- WriteCache
- RebuildPriority
- ExpandPriority
- SurfaceScanDelay
|
Options in this category define the controller that has to be configured (or the controller that has had its configuration captured). The Controller option must be at the beginning of this
section of the script, but you can script other options in this category in any order. You can use one script to configure several controllers if all controllers are to be configured identically
or if you define each controller configuration separately. When you define each controller separately, specify all category options for a particular controller before starting a new controller
listing.
|
Array |
|
These options define an array that is to be configured on the controller that is identified previously in the script. (If no controller is previously identified, ACU sends an error message.) The
Array option must be at the beginning of this section of the script, but you can script the other options in this category in any order.
|
LogicalDrive |
- LogicalDrive
- RAID
- Size
- Sectors
- StripeSize
- ArrayAccelerator
|
These options define a logical drive that is to be configured on an array that is defined previously in the script. (If no array is previously defined, ACU sends an error message.) The
LogicalDrive option must be at the beginning of this section of the script, but you can script the other options in this category in any order.
|
|
Limitations |
|
|
This section describes the
limitations in ACUXE Version 6.40-11P09A:
- Crash occurs when ACUXE is used extensively resulting in PGFLQUOTA to exceed its limit. To overcome this limitation, restart ACUXE.
- Logical Drive Capacity Extension is not supported.
- "Command Line Interpreter" operating mode is not supported.
- The SHOW command is the only command supported by CLI (CPQ$ACUXE.COM -cli show).
- After starting ACUXE, the Array
Configuration Utility link appears after five minutes on the System Management
Homepage.
|
» return to the Array Configuration Utility home page
|