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
Registering the mainframe host in Device Manager
To use the AddHost command to register the mainframe host in Device Manager:
1. Execute the AddHost command to register the mainframe host in Device Manager.
When you execute the command, specify the following parameters:
• hostname: In this parameter, specify the host name that you specified when setting up the
mainframe host environment.
• hosttype: In this parameter, specify 2.
2. From the execution result of the AddHost command, make sure that specified information is
correctly output to the name and hosttype parameters.
Notes on executing the AddHost command:
• If the host name specified during mainframe host environment setup and the host name specified
during Device Manager environment setup do not match, information registered in P9000
mainframe agent cannot be acquired.
• Do not specify the wwnlist parameter when registering the mainframe host in Device Man-
ager. If you do, an error occurs.
• Record the objectID value output when the AddHost command is executed. You will need
this value for the subsequent procedures and operations.
• Although the IP address specified in the ipaddress parameter of a command is registered
as an attribute of the mainframe host, the IP address registered using the AddHost command
is not used for communication with P9000 mainframe agent. The information necessary for
communication with P9000 mainframe agent will be specified in “Registering the P9000
mainframe agent running on the mainframe host in Device Manager” on page 437.
Action to be taken if an error occurs during the execution of the AddHost command:
Use the GetHost command to check whether the mainframe host has been registered. If the
mainframe host has not been registered, register it by using the AddHost command. If the
mainframe host has been registered incorrectly, use the ModifyHost command to correct the
registered information. For details about how to correct the registered mainframe host information,
see “Changing mainframe host information” on page 443.
Command format:
hdvmcli AddHost "hostname=mainframe-host-name" "hosttype=2"
Example of executing the command:
hdvmcli AddHost -o "D:\logs\AddHost.log" "hostname=toro2" "hosttype=2"
Example of output from executing the command:
RESPONSE:
An instance of Host
objectID=*****
Connecting to P9000 mainframe agent436