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

Command execution result
RESPONSE:
An instance of ObjectLabel
targetID=*****
label=myLabel
An instance of ObjectLabel
targetID=*****
label=myLabel
*****: The values are encoded by the CLI.
AddLogicalUnit
AddLogicalUnit creates an LDEV and LU. With P9500, XP24000/XP20000, or
XP12000/XP10000/SVS200, you can create multiple logical units at once.
The LDEVs created by this command are formatted when they are created. However, if you are using
P9500, XP24000/XP20000, or XP12000/XP10000/SVS200, you can use the format parameter
to specify whether to format the LDEVs and also the format type.
For P9500 or XP24000/XP20000, depending on whether you specify the fsindex and
creationoption parameters, you can control LUs or create an LU by optimally using the regions
of unused capacity in a parity group (optimization of regions of unused capacity).
NOTE:
• For P9500, XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128, the capacity
of LDEV to be created will be larger than the specified capacity.
• For P9500, XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128, you cannot
create an LDEV that is the same size as the unused capacity of the parity group, because the
control area is created on the storage system side.
• For P9500, XP24000/XP20000, XP12000/XP10000/SVS200, or XP1024/XP128, the SSID
must be set before an LDEV and LU are created. For details about the SSID, see the manual for
each storage system.
• For P9500 or XP24000/XP20000, logical units cannot be created in parity groups with chassis
numbers from 65 to 96, or from 16485 to 16516. Parity groups with chassis numbers from 65
to 96, or from 16485 to 16516 are indicated as V-VOLs.
• For XP12000/XP10000/SVS200, logical units cannot be created in parity groups with chassis
numbers from 65 to 96. Array groups with chassis numbers from 65 to 96 are indicated as V-
VOLs.
Format for P9500, XP24000/XP20000, and XP12000/XP10000/SVS200
When creating a single LU:
hdvmcli [URL] AddLogicalUnit [options]
serialnum=serial-number model=model
{chassis=chassis-number groupnum=parity-group-number
|arraygroupname=parity-group-name}
Command reference62