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
NOTE:
If you use the Device Manager CLI on the same computer as the Device Manager server, HP
recommends that you specify the same JRE that the Device Manager server uses (the JRE provided
with HP P9000 Command View Advanced Edition Suite). However, when HTTPS is used to communicate
with the Device Manager server, you cannot use the same JRE that the Device Manager server uses.
In this case, prepare another JRE that is supported by the Device Manager CLI and configure a Java
environment.
When the Device Manager CLI uses the same JRE as the Device Manager server, specify the path of
that JRE in the HDVM_CLI_JRE_PATH environment variable. The HP P9000 Command View Advanced
Edition Suite Common Component (abbreviated hereafter as Common Component) installation directory
is included in the JRE path. The JRE path is as follows:
• In Windows:
Common-Component-installation-folder\jdk\jre\bin
• In Solaris and Linux:
Common-Component-installation-directory/jdk/jre/bin
If you do not know the installation directory for Common Component, you can check the directory in
the server.base.home property of the Device Manager server server.properties file. A
forward slash (/) is used as a delimiter for directories in the server.base.home property. Therefore,
when you set the JRE path in the HDVM_CLI_JRE_PATH environment variable in Windows, change
a forward slash (/) to a backslash (\).
When upgrading Device Manager
When upgrading Device Manager, the version of Java that the Device Manager CLI or the Device
Manager server supports might be updated.
If the Java version has been updated, check the JRE version that is currently configured, and then, if
necessary, change the JRE settings. You have to be especially careful when the Device Manager CLI
is used in the following environment:
• The Device Manager CLI is downloaded from the GUI and being used
• The path of the JRE that the Device Manager server uses has been set in the HDVM_CLI_JRE_PATH
environment variable.
If the above conditions are satisfied, the JRE that the Device Manager server uses is updated when
Device Manager is upgraded. At the same time, the JRE version set in the HDVM_CLI_JRE_PATH
environment variable is also updated. However, if the Device Manager CLI (that was downloaded
from the GUI) is being used, the Device Manager CLI will not be upgraded even if Device Manager
is upgraded. Therefore, the Device Manager CLI might not support the new JRE version.
If the updated JRE version is not supported by the Device Manager CLI version that you are using,
take either of the following actions:
• Download the latest Device Manager CLI version from the GUI (recommended)
• Prepare another JRE that is supported by the Device Manager CLI version being used, and then
set that JRE for the HDVM_CLI_JRE_PATH environment variable.
Environment settings22