Dell PowerVault MD3260i CLI Guide - Page 39

Example of the Auto Configuration Command, command. See Modifying Your Configuration.

Page 39 highlights

values that MD Storage Manager uses to create a storage array. Change any of the parameter values by entering new values for the parameters when you run the autoConfigure storageArray command. If you are satisfied with the parameter values that the show storageArray autoConfiguration command returns, run the autoConfigure storageArray command without new parameter values. The following syntax is the general form of autoConfigure storageArray command: autoConfigure storageArray [physicalDiskType= (SAS) raidLevel=(0 | 1 | 5 | 6) | diskGroupWidth= numberOfPhysicalDisks | diskGroupCount= numberOfDiskGroups | virtualDisksPerGroupCount= numberOfVirtualDisksPerGroup | hotSpareCount= numberOfHotspares | segmentSize=segmentSizeValue] NOTE: All parameters are optional. You can use one or all of the parameters as needed to define your configuration. When you use the autoConfigure storageArray command without specifying the number of disk groups, the firmware determines how many virtual disks and disk groups to create. The firmware creates one disk group and one virtual disk up to the maximum number that the storage array can support. When you specify the number of disk groups, the firmware creates only that number of disk groups. When you create more than one disk group, all of the disk groups have the same number of physical disks and the same number of virtual disks. • The diskGroupWidth parameter defines the number of unassigned physical disks wanted for each new disk group. • The diskGroupCount parameter defines the number of new disk groups wanted in the storage array. • The virtualDisksPerGroupCount parameter defines the number of virtual disks wanted in each disk group. • The hotSpareCount parameter defines the number of hot spares wanted in each disk group. • The segmentSize parameter defines the amount of data in kilobytes that the RAID controller module writes on a single physical disk in a virtual disk before writing data on the next physical disk. The smallest units of storage are data blocks. Each data block stores 512 bytes of data. The size of a segment determines how many data blocks that it contains. An 8-KB segment holds 16 data blocks. A 64-KB segment holds 128 data blocks. Valid values for the segment size are 8, 16, 32, 64, 128, 256, and 512. When you enter a value for the segment size, the value is checked against the supported values provided by the RAID controller module at run time. If the value you enter is not valid, the RAID controller module returns a list of valid values. If the virtual disk is for a single user with large I/O requests (such as multimedia), performance is maximized when a single I/O request can be serviced with a single data stripe. A data stripe is the segment size multiplied by the number of physical disks in the disk group that are used for data storage. In this environment, multiple physical disks are used for the same request, but each physical disk is accessed only once. For optimal performance in a multi-user database or file system storage environment, set the segment size to minimize the number of physical disks needed to satisfy an I/O request. Using a single physical disk for a single request leaves other physical disks available to simultaneously service other requests. After you have finished creating the disk groups and virtual disks by using the autoConfigure storageArray command, you can further define the properties of the virtual disks in a configuration using the set virtualDisk command. (See Modifying Your Configuration.) Example of the Auto Configuration Command client>smcli 123.45.67.89 -c "autoConfigure storageArray physicalDiskType=SAS raidLevel=5 diskGroupWidth=8 diskGroupCount=3 virtualDisksPerGroupCount=4 hotSpareCount=2 segmentSize=8;" 39

  • 1
  • 2
  • 3
  • 4
  • 5
  • 6
  • 7
  • 8
  • 9
  • 10
  • 11
  • 12
  • 13
  • 14
  • 15
  • 16
  • 17
  • 18
  • 19
  • 20
  • 21
  • 22
  • 23
  • 24
  • 25
  • 26
  • 27
  • 28
  • 29
  • 30
  • 31
  • 32
  • 33
  • 34
  • 35
  • 36
  • 37
  • 38
  • 39
  • 40
  • 41
  • 42
  • 43
  • 44
  • 45
  • 46
  • 47
  • 48
  • 49
  • 50
  • 51
  • 52
  • 53
  • 54
  • 55
  • 56
  • 57
  • 58
  • 59
  • 60
  • 61
  • 62
  • 63
  • 64
  • 65
  • 66
  • 67
  • 68
  • 69
  • 70
  • 71
  • 72
  • 73
  • 74
  • 75
  • 76
  • 77
  • 78
  • 79
  • 80
  • 81
  • 82
  • 83
  • 84
  • 85
  • 86
  • 87
  • 88
  • 89
  • 90
  • 91
  • 92
  • 93
  • 94
  • 95
  • 96
  • 97
  • 98
  • 99
  • 100
  • 101
  • 102
  • 103
  • 104
  • 105
  • 106
  • 107
  • 108
  • 109
  • 110
  • 111
  • 112
  • 113
  • 114
  • 115
  • 116
  • 117
  • 118
  • 119
  • 120
  • 121
  • 122
  • 123
  • 124
  • 125
  • 126
  • 127
  • 128
  • 129
  • 130
  • 131
  • 132
  • 133
  • 134
  • 135
  • 136
  • 137
  • 138
  • 139
  • 140
  • 141
  • 142
  • 143
  • 144
  • 145
  • 146
  • 147
  • 148
  • 149
  • 150
  • 151
  • 152
  • 153
  • 154
  • 155
  • 156
  • 157
  • 158
  • 159
  • 160
  • 161
  • 162
  • 163
  • 164
  • 165
  • 166
  • 167
  • 168
  • 169
  • 170
  • 171
  • 172
  • 173
  • 174
  • 175
  • 176
  • 177
  • 178
  • 179
  • 180
  • 181
  • 182
  • 183
  • 184
  • 185
  • 186
  • 187
  • 188
  • 189
  • 190
  • 191
  • 192
  • 193
  • 194
  • 195
  • 196
  • 197
  • 198
  • 199
  • 200
  • 201
  • 202
  • 203
  • 204
  • 205
  • 206
  • 207
  • 208
  • 209
  • 210
  • 211
  • 212
  • 213
  • 214
  • 215
  • 216
  • 217
  • 218
  • 219
  • 220
  • 221
  • 222
  • 223
  • 224
  • 225
  • 226

values that MD Storage Manager uses to create a storage array. Change any of the parameter values by entering new
values for the parameters when you run the
autoConfigure storageArray
command. If you are satisfied with
the parameter values that the
show storageArray autoConfiguration
command returns, run the
autoConfigure storageArray
command without new parameter values.
The following syntax is the general form of
autoConfigure storageArray
command:
autoConfigure storageArray [physicalDiskType=
(SAS) raidLevel=(0 | 1 | 5 | 6) | diskGroupWidth=
numberOfPhysicalDisks | diskGroupCount=
numberOfDiskGroups | virtualDisksPerGroupCount=
numberOfVirtualDisksPerGroup | hotSpareCount=
numberOfHotspares | segmentSize=segmentSizeValue]
NOTE:
All parameters are optional. You can use one or all of the parameters as needed to define your
configuration.
When you use the
autoConfigure storageArray
command without specifying the number of disk groups, the
firmware determines how many virtual disks and disk groups to create. The firmware creates one disk group and one
virtual disk up to the maximum number that the storage array can support. When you specify the number of disk groups,
the firmware creates only that number of disk groups. When you create more than one disk group, all of the disk groups
have the same number of physical disks and the same number of virtual disks.
The
diskGroupWidth
parameter defines the number of unassigned physical disks wanted for each new disk
group.
The
diskGroupCount
parameter defines the number of new disk groups wanted in the storage array.
The
virtualDisksPerGroupCount
parameter defines the number of virtual disks wanted in each disk
group.
The
hotSpareCount
parameter defines the number of hot spares wanted in each disk group.
The
segmentSize
parameter defines the amount of data in kilobytes that the RAID controller module writes
on a single physical disk in a virtual disk before writing data on the next physical disk. The smallest units of
storage are data blocks. Each data block stores 512 bytes of data. The size of a segment determines how many
data blocks that it contains. An 8-KB segment holds 16 data blocks. A 64-KB segment holds 128 data blocks.
Valid values for the segment size are
8
,
16
,
32
,
64
,
128
,
256
, and
512
.
When you enter a value for the segment size, the value is checked against the supported values provided by the
RAID controller module at run time. If the value you enter is not valid, the RAID controller module returns a list of
valid values.
If the virtual disk is for a single user with large I/O requests (such as multimedia), performance is maximized when a
single I/O request can be serviced with a single data stripe. A data stripe is the segment size multiplied by the number of
physical disks in the disk group that are used for data storage. In this environment, multiple physical disks are used for
the same request, but each physical disk is accessed only once.
For optimal performance in a multi-user database or file system storage environment, set the segment size to minimize
the number of physical disks needed to satisfy an I/O request. Using a single physical disk for a single request leaves
other physical disks available to simultaneously service other requests.
After you have finished creating the disk groups and virtual disks by using the
autoConfigure storageArray
command, you can further define the properties of the virtual disks in a configuration using the
set virtualDisk
command. (See Modifying Your Configuration.)
Example of the Auto Configuration Command
client>smcli 123.45.67.89 -c "autoConfigure
storageArray physicalDiskType=SAS raidLevel=5
diskGroupWidth=8 diskGroupCount=3
virtualDisksPerGroupCount=4 hotSpareCount=2
segmentSize=8;"
39