Creating Logical Drives With Software-Assigned Disk Drives - IBM System Storage DS3000 Programming Manual

inside the square brackets). You can use one or all of the optional parameters as needed to define your
configuration. If you choose not to use any of the optional parameters, the default values of the
parameters are used for your configuration.
The userLabel parameter is the name that you want to give to the logical drive. The logical drive name
can be any combination of alphanumeric characters, hyphens, and underscores. The maximum length of
the logical drive name is 30 characters. You must enclose the logical drive name with double quotation
marks (" ").
The drives parameter is a list of the disk drives that you want to use for the subsystem. Enter the
enclosure ID and the slot ID of each disk drive that you want to use. Enclose the list in parentheses,
separate the enclosure ID value and the slot ID value of a disk drive with a comma, and separate each
enclosure ID and slot ID pair with a space. This example shows you how to enter enclosure ID values
and slot ID values:
(1,1 1,2 1,3 1,4 1,5)
The capacity parameter defines the size of the logical drive. You do not need to assign the entire capacity
of the disk drives to the logical drive. Later, you can assign any unused space to another logical drive.
The owner parameter defines the controller to which you want to assign the logical drive. If you do not
specify a controller, the controller firmware determines the logical drive owner.
The cacheReadPrefetch parameter and the segmentSize parameter are the same as those described for the
autoConfigure storageSubsystem command.
The enclosureLossProtect parameter defines enclosure loss protection for the subsystem. (For a
description of how enclosure loss protection works, see "Enclosure Loss Protection" on page 4-38.)
The securityType parameter is used to specify the security level when creating subsystems and logical
drives in storage subsystems with Full Disk Encryption (FDE) drives.
Example of Creating Logical Drives with User-Assigned Disk Drives
c:\...\...\client>smcli 123.45.67.89 -c "create logicalDrive drives
=(1,1 1,2 1,3 2,1 2,2 2,3) raidLevel=5 userLabel=\"Engineering_1\"
capacity=20GB owner=a cacheReadPrefetch=TRUE segmentSize=128 securityType=enabled T10PI=none;"
The command in this example automatically creates a new subsystem and a logical drive with the name
Engineering_1. The subsystem has a RAID level of 5 (RAID 5). The command uses six disk drives to
construct the subsystem. The disk drives have a total logical drive capacity of 20 GB. If each disk drive
has a capacity of 18 GB, the total capacity of all the assigned disks is 108 GB.
18 GB x 6 disk drives = 108 GB
Because only 20 GB is assigned to the logical drive, 88 GB remains available (as unconfigured capacity)
for other logical drives that a user can add to this subsystem later.
108 GB - 20 GB subsystem size = 88 GB
Cache read prefetch is turned on, which causes additional data blocks to be written into the cache. The
segment size for each logical drive is 128 KB. Enclosure loss protection is set to TRUE, which prevents any
operations to disk drives in the expansion drawer if the expansion drawer fails. Hot spares are not
created for this new subsystem. You must create hot spares after you run this command.

Creating Logical Drives with Software-Assigned Disk Drives

If you choose to let the Storage Manager software assign the disk drives when you create the logical
drive, you need only to specify the number of disk drives that you want to use. The Storage Manager
software then assigns the disk drives. The controller firmware assigns an subsystem number to the new
subsystem. To manually create subsystems and logical drives, use the create logicalDrive command:
4-36
IBM System Storage DS3000, DS4000, and DS5000: Command Line Interface and Script Commands Programming Guide