HP Logical Server Management Best Practices

59
<volumeNumber> set to the appropriate value, generally 1.
<storageSize> size of the local disk in MB or GB
<shareble> set to false
The <description> value can be set as appropriate for the customer environment. The other fields should be left
unspecified (e.g., <storageDeviceType>, <storageSpeed>, <disk status>). The
<CliComputePhysical> fields should not be changed (e.g., server name, UUID, and portability group).
Once the file contains the correct information, the lsmutil -import an file filename.xml command
ensures Matrix OE is aware of the new information.
After the import, Matrix OE is aware which compute resources have local disks which can be used as boot volumes.
That information is shared with Matrix infrastructure orchestration along with information about storage pool entries.
Matrix IO can then determine the appropriate resources to support instantiating a given service template.
NOTE: Once a logical server is activated on a target with local disk, it cannot be moved (but can be deactivated
and reactivated onto the same physical server, although no other logical server will be able to use that physical
server).
If the local disk needs to be deleted at a later time, executing the lsmutil -import an file
filename.xml command with the below information in the filename.xml file will delete the local disk. The
<name>, <uuid> and <portabilityGroupId> fields need to be adjusted as appropriate for the environment.
<?xml version="1.0" encoding="UTF-8" ?>
<ComputeActuals xmlns="www.infosim/sn">
<CliComputePhysical>
<name>lsaserver04</name>
<uuid>38313933-3533-5355-4538-30354E333237</uuid>
<portabilityGroupId>2</portabilityGroupId>
<CliLocalDisk></CliLocalDisk>
</CliComputePhysical>
</ComputeActuals>
LSMUTIL Usage
The lsmutil command line utility can be used by administrators to list objects such as logical servers, compute
resources and storage pool entries within the Matrix OE database. The administrator can also list, reserve and
unreserve WWN‟s within the Virtual Connect Enterprise Manager GUID server using lsmutil. Finally the lsmutil
utility allows the administrator to export and import storage pool entries and compute resources (including optional
local disk information); but these export and import operations must be executed when the HP Logical Server
Automation service is available. The following commands are available for use.
lsmutil -list -ls [ -active | -inactive ] [names] [-xml] [-detail] [-file filename] [-help]
Prints a short list in ASCII format to sysout or to the specified file. The list contains All, Active or Inactive logical servers
in the Matrix OE database. The type of logical servers shown are determined by the user‟s input. The user may also
specify the name(s) of the logical servers to display. If no option is selected, all logical servers are displayed. The
short list will show Server Name, Type (ESX, Blade, HyperV), Architecture and State. If applicable, it will also show
the associated Virtual Doman Group and the Storage WWN. If the -xml parameter is specified, the utility will print a
detailed list in XML format to sysout or to the specified file. If the -detail parameter is specified, a detailed list of the
logical servers in a friendlier than XML format will be printed to sysout or to the supplied file. The list contains All,
Active or Inactive logical servers in the Matrix OE database.
lsmutil -list -cr [-vm | -vc | -oowf] [names] [-xml] [-file filename] [-help]