HP P9000 Command View Advanced Edition Suite Software 7.4.0-00 CLI Reference Guide (TB581-96326, December 2012)
Table Of Contents
- CLI Reference Guide
- Table of Contents
- Preface
- 1 Overview
- 2 Environment settings
- 3 Executing commands
- 4 Command reference
- Storage system commands
- AddArrayReservation
- AddExternalArrayGroup
- AddHostStorageDomain
- AddLabel
- AddLogicalUnit
- AddLUSE
- AddPool
- AddStorageArray
- AddTieredPoolOperation
- AddVirtualVolume
- DeleteArrayReservation
- DeleteExternalArrayGroup
- DeleteHostStorageDomain
- DeleteLabel
- DeleteLogicalUnit
- DeleteLUSE
- DeletePool
- DeleteStorageArray
- DeleteVirtualVolume
- FormatLU
- GetArrayReservation
- GetPoolShrinkStatus
- GetStorageArray
- Using the GetStorageArray parameter
- GetStorageArray (subtarget not specified)
- GetStorageArray (subtarget=ArrayGroup)
- GetStorageArray (subtarget=CommParameters)
- GetStorageArray (subtarget=Component)
- GetStorageArray (subtarget=ExternalStorage)
- GetStorageArray (subtarget=Filter)
- GetStorageArray (subtarget=FreeSpace)
- GetStorageArray (subtarget=HostStorageDomain)
- GetStorageArray (subtarget=LDEV)
- GetStorageArray (subtarget=LogicalDKC)
- GetStorageArray (subtarget=LogicalUnit)
- GetStorageArray (subtarget=MFReplicationInfo)
- GetStorageArray (subtarget=Path)
- GetStorageArray (subtarget=PDEV)
- GetStorageArray (subtarget=Pool)
- GetStorageArray (subtarget=Port)
- GetStorageArray (subtarget=PortController)
- GetStorageArray (subtarget=ReplicationInfo)
- GetStorageArray (subtarget=TieringPolicy)
- GetTieredPoolStatus
- GetZeroPageReclaimStatus
- ModifyArrayReservation
- ModifyExternalTierRank
- ModifyLabel
- ModifyLogicalUnit
- ModifyPool
- ModifyPort
- ModifyPortController
- ModifyStorageArray
- ModifyTieringPolicy
- ModifyVirtualVolume
- RefreshPerformanceData
- RefreshStorageArrays
- RunZeroPageReclaim
- ShrinkPool
- Logical group commands
- LUN commands
- Host management commands
- Server management commands
- Replication commands
- Storage system commands
- 5 Output items
- Alert instance
- ArrayGroup instance
- ArrayReservation instance
- CommParameters instance
- Component instance
- ConfigFile instance
- Datastore instance
- ExternalPathInfo instance
- ExternalStorage instance
- FreeLUN instance
- FreeSpace instance
- Host instance
- HostInfo instance
- HostStorageDomain instance
- IPAddress instance
- LDEV instance
- LogicalDKC instance
- LogicalGroup instance
- LogicalUnit instance
- MFReplicationInfo instance
- ObjectLabel instance
- PairedPool instance
- PairedPortController instance
- Path instance
- PDEV instance
- PerformanceStatus instance
- Pool instance
- PoolTier instance
- Port instance
- PortController instance
- RelatedDistributedArrayGroup instance
- ReplicationControllerPair instance
- ReplicationGroup instance
- ReplicationInfo instance
- ServerInfo instance
- StorageArray instance
- TieringPolicy instance
- URLLink instance
- VirtualDisk instance
- VM instance
- VolumeConnection instance
- WWN instance
- 6 Batch functionality
- 7 Import functionality
- 8 Properties file
- Overview of the properties file
- Using the properties file to specify options
- Using the properties file to specify parameters
- Setting up the execution environment
- Specifying the log file
- Specifying a log level
- Message trace output
- Specifying the URL
- Inputting requests from XML documents
- Using the message trace file
- Output format of execution results
- Outputting execution results in CSV format
- Outputting execution results in XML format
- Specifying a DTD
- Using a DTD with the Device Manager CLI
- 9 Troubleshooting
- 10 Support and other resources
- A Connecting to P9000 mainframe agent
- About connecting to P9000 mainframe agent
- Setting up the mainframe host environment
- Setting up the Device Manager environment
- Refreshing information recognized by the mainframe host
- Acquiring P9000 mainframe agent information registered in Device Manager
- Changing P9000 mainframe agent information registered in Device Manager
- Deleting P9000 mainframe agent information registered in Device Manager
- Acquiring mainframe host information
- Changing mainframe host information
- Deleting a mainframe host
- Glossary
- Index

FunctionVariable
Options control the behavior of the CLI application. Options are entered in the typical
UNIX fashion. Options are case sensitive. Each option has a single character
representation and an alternate word representation; for the single character, prefix the
character with a single dash; for the word, prefix the word with two dashes. For example:
-t or --messagetrace. Some options require an argument, which follows the option.
For example, the -u option is followed by a user ID. For details about the options that
can be used with the Device Manager CLI, see Table 3.
When the same option is specified multiple times, the value specified last is used.
options
Parameters that are passed to the server as part of a request. The required and optional
parameters depend on the command requested. Each parameter is represented as a
combination of a parameter name and a parameter value, such as parameter-name
= parameter-value. The parameter name is not case sensitive. If you want to specify
a value that includes spaces, enclose the value in double quotation marks ("), as in
hostmode="Windows Extension, Solaris Extension".
Unless otherwise noted in parameter descriptions, parameter values are case sensitive.
There are required parameters and optional parameters. If you omit a required
parameter, you cannot execute the command.
When the same parameter is specified multiple times, the value specified last is used.
Some parameters cannot be used for some commands. For usable parameters, see
Chapter 4 on page 43.
parameters
Table 3 Device Manager CLI options
DescriptionStatus
Argument for the
option
Option
A valid Device Manager server login user ID
You must have your user ID registered in Device
Manager before using the Device Manager CLI.
Required
user-ID
#1
-u or
--user
The Device Manager server login password or the path
to the password file that contains the login password
#1, #2, #3
A password can either be specified directly, or a file
containing a password can be specified. The
application user needs to have access permissions for
the password file. Do not grant access permissions to
common users for the password file.
When specifying the password file, include an @ sign
at the beginning of the path. The text on the first line of
the specified file is read and used as the password.
HP recommends that you set an encoded character
string rather than plain text for the password file. For
details about how to encode a password, see
“Encoding the password in the properties file or
password file” on page 409.
Required
password or
password-file
-p or
--password
Uses HTTPS to communicate with the Device Manager
server.
OptionalNo argument
-s or
--secure
CLI Reference Guide 27