HP StorageWorks SAN Virtualization Services Platform Manager Command Line Interface User Guide (5697-0936, May 2011)

Constraints on name strings
Name strings are limited to 31 characters, followed by a zero-terminating character. Name strings
of VSM objects (virtual disks, points-in-time, snapshots, and so on) are case sensitive. Name strings
that contain spaces must be surrounded by quotation marks. They also must use only printable
characters, and not contain the following characters:
" : ; , * % { } [ ] ' ~ / \ ? < > |
Names containing white spaces or special symbols (tildes, quotes, dashes, and so on) must be
enclosed between quotation marks to avoid problems in parsing the command line. Also, the
decimal symbol in some regions is a comma (for example, 1,24), which is normally used as an
argument separator. Consequently, enclose numbers with a decimal symbol between quotation
marks to avoid this problem.
Known limitations
Working with dynamic volumes in Windows 2003/2008
• In Microsoft Windows 2003 or 2008, partition numbers are not applicable to dynamic
volumes. Consequently, the mount/unmount volume APIs and CLI commands cannot distinguish
between multiple dynamic volumes that are defined on same dynamic disks. As a result, the
current limitation is that only one dynamic volume (file system) is allowed per one VSM virtual
disk, and its partition number is always 1.
• When expanding a dynamic volume (file system) with the CLI commands, the command will
always expand the VSM virtual disk associated with the first dynamic disk added to the
dynamic volume (file system).
For example, if the dynamic volume P: was originally created spanning three disks (#7, #8,
and #9), the CLI command will expand the VSM virtual disk associated with disk #7 (which
is presumably the first disk to be added to that partition).
Expanding a partition (file system) on Windows 2003/2008
When using the ExpandPartition and the ExpandPartitionEx commands on Windows
2003/2008, make sure that Windows Disk Manager console is closed. Leaving the Disk Manager
console open while the VSM API tries to expand a file system may cause the operation to fail. In
case of a failure because of Disk Manager, close it and rerun the ExpandPartition command,
expanding the partition by a small amount of storage (by no less than 100 MB).
Redhat Linux v4.7 does not load SG module automatically
Redhat v4.7 does not automatically load the SG module like previous versions, and this module
is necessary to run the VSM CLI. To load the module, perform a modprobe sg.
You can verify the module loaded successfully by running a simple command like:
VSMCLI —SD DomainName UserName Password —C liststoragepools where the
DomainName, UserName, and Password are applicable to your configuration. You should obtain
a list of storage pools within the domain.
If the command ran successfully, then you can rebuild the initrd to include the sg, so it loads
each time a boot is performed.
Virtual disks in DPM groups
Virtual disks that belong to a virtual disk group (VDG) are always presented to a host through a
specific Data Path Module (DPM) group. The VSM GUI has an internal algorithm that assigns a
virtual disk to the DPM group, therefore the VSM CLI cannot be used to assign a virtual disk to a
10 Overview