Dell PowerVault MD3260i CLI Guide - Page 183

Set Storage Array Enclosure Positions, Cache Block Size, Cache Flush Start and Cache Flush Stop

Page 183 highlights

• Automatic collection of the configuration and state information occurs every 72 hours. The configuration and state information is saved to the storage array zip archive file. The archive file has a time stamp that is used to manage the archive files. • Two storage array zip archive files are maintained for each storage array. The zip archive files are kept on a physical disk. After the 72-hour time period is exceeded, the oldest archive file is always overwritten during the new cycle. • After you enable automatic collection of the configuration and state information using this command, an initial collection of information starts. Collecting information after the you issue the command makes sure that one archive file is available and starts the time stamp cycle. You can run the set storageArray autoSupportConfig command on more than one storage array. Cache Block Size When you define cache block sizes, use the 4-KB cache block size for storage arrays that require I/O streams that are typically small and random. Use the 8- KB cache block size when the majority of your I/O streams are larger than 4 KB but smaller than 8 KB. Use the 16-KB cache block size or the 32-KB cache block size for storage arrays that require large data transfer, sequential, or high-bandwidth applications. The cacheBlockSize parameter defines the supported cache block size for all of the virtual disks in the storage array. Not all RAID controller module types support all cache block sizes. For redundant configurations, this parameter includes all of the virtual disks that are owned by both RAID controller modules within the storage array. Cache Flush Start and Cache Flush Stop When you define values to start a cache flush, a value that is too low increases the chance that data needed for a host read is not in the cache. A low value also increases the number of physical disk writes that are necessary to maintain the cache level, which increases system overhead and decreases performance. When setting storage array cache settings, the value of the cacheFlushStart parameter must always be greater than or equal to the value of the cacheFlushStop parameter. For example, if the value of the cacheFlushStart parameter is set to 80, you may set the value of the cacheFlushStop parameter within the range of 0 to 80. When you define values to stop a cache flush, the lower the value, the higher the chance that the data for a host read requires a physical disk read rather than reading from the cache. Default Host Type When you define host types, if Storage Partitioning is enabled, the default host type affects only those virtual disks that are mapped in the default group. If Storage Partitioning is not enabled, all of the hosts that are attached to the storage array must run the same operating system and be compatible with the default host type. Media Scan Rate Media scan runs on all of the virtual disks in the storage array that have optimal status, do not have modification operations in progress, and have the mediaScanRate parameter enabled. Use the set virtualDisk command to enable or disable the mediaScanRate parameter. NOTE: If you are using self-encrypting disk physical disks in your storage array, you must use these criteria for your storage array password. NOTE: You must set a password for your storage array before you can create a security key for encrypted selfencrypting disk physical disks. Set Storage Array Enclosure Positions This command defines the position of the enclosures in a storage array. You must include all of the enclosures in the storage array when you enter this command. Syntax set storageArray enclosurePositions=(controller | enclosureID... enclosureIDn) 183

  • 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

Automatic collection of the configuration and state information occurs every 72 hours. The configuration and
state information is saved to the storage array zip archive file. The archive file has a time stamp that is used to
manage the archive files.
Two storage array zip archive files are maintained for each storage array. The zip archive files are kept on a
physical disk. After the 72-hour time period is exceeded, the oldest archive file is always overwritten during the
new cycle.
After you enable automatic collection of the configuration and state information using this command, an initial
collection of information starts. Collecting information after the you issue the command makes sure that one
archive file is available and starts the time stamp cycle.
You can run the
set storageArray autoSupportConfig
command on more than one storage array.
Cache Block Size
When you define cache block sizes, use the 4-KB cache block size for storage arrays that require I/O streams that are
typically small and random. Use the 8- KB cache block size when the majority of your I/O streams are larger than 4 KB
but smaller than 8 KB. Use the 16-KB cache block size or the 32-KB cache block size for storage arrays that require large
data transfer, sequential, or high-bandwidth applications.
The
cacheBlockSize
parameter defines the supported cache block size for all of the virtual disks in the storage
array. Not all RAID controller module types support all cache block sizes. For redundant configurations, this parameter
includes all of the virtual disks that are owned by both RAID controller modules within the storage array.
Cache Flush Start and Cache Flush Stop
When you define values to start a cache flush, a value that is too low increases the chance that data needed for a host
read is not in the cache. A low value also increases the number of physical disk writes that are necessary to maintain
the cache level, which increases system overhead and decreases performance.
When setting storage array cache settings, the value of the
cacheFlushStart
parameter must always be greater
than or equal to the value of the
cacheFlushStop
parameter. For example, if the value of the
cacheFlushStart
parameter is set to
80
, you may set the value of the
cacheFlushStop
parameter within the range of
0
to
80
.
When you define values to stop a cache flush, the lower the value, the higher the chance that the data for a host read
requires a physical disk read rather than reading from the cache.
Default Host Type
When you define host types, if Storage Partitioning is enabled, the default host type affects only those virtual disks that
are mapped in the default group. If Storage Partitioning is not enabled, all of the hosts that are attached to the storage
array must run the same operating system and be compatible with the default host type.
Media Scan Rate
Media scan runs on all of the virtual disks in the storage array that have optimal status, do not have modification
operations in progress, and have the
mediaScanRate
parameter enabled. Use the
set virtualDisk
command
to enable or disable the
mediaScanRate
parameter.
NOTE:
If you are using self-encrypting disk physical disks in your storage array, you must use these criteria for
your storage array password.
NOTE:
You must set a password for your storage array before you can create a security key for encrypted self-
encrypting disk physical disks.
Set Storage Array Enclosure Positions
This command defines the position of the enclosures in a storage array. You must include all of the enclosures in the
storage array when you enter this command.
Syntax
set storageArray enclosurePositions=(controller |
enclosureID... enclosureIDn
)
183