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
Inputting requests from XML documents
CAUTION:
To use the XML-API CLI feature, you need thorough knowledge of XML-API, and need to take great
care in formulating commands.
Rather than specifying the command and parameters from the command line, the request can originate
from a file. The file must contain a valid XML document in the correct form for a Device Manager
request. The command line option -i or --input specifies the input file. The other options are still
valid. However, any command or parameter specified from the command line or in the properties
file is ignored, because that information is already in the XML document.
The -i <file-name> option allows you to specify an xml message file. You can use this feature to
request multiple operations from the CLI command, which can save considerable time.
For example, usually the AddLun command specifies creation of a single LUN. The AddLun XML-API
allows you to create multiple LUNs with a single request.
Syntax:
hdvmcli [-t] AddLun
serialnum=serial-number model=model
port=port-number domain=domain-ID
scsi=SCSI-ID lun=valid-LUN devnum=device-number
From the command line, specify the -t option and the AddLUN command as follows, and then execute
hdvmcli.
hdvmcli -t AddLun
serialnum=15045 model=XP1024/XP128
port=0 domain=0 scsi=15 lun=100 devnum=1
The XML-API request that follows the AddLUN command executed by using hdvmcli is output to the
message destination file (MessageTrace.log).
<?xml version="1.0" encoding="UTF-8"?>
<HiCommandServerMessage>
<APIInfo version="7.4.0" />
<Request>
<StorageManager>
<Add target="LUN">
<StorageArray objectID="ARRAY.XP1024/XP128.15045">
<Path portID="0" domainID="0" scsiID="15" lun="100" devNum="1" />
</StorageArray>
</Add>
</StorageManager>
</Request>
</HiCommandServerMessage>
Create a file by specifying multiple LUNs as follows:
Properties file412