Autoconfigure storage array

The autoConfigure storageArray command automatically configures a storage array.

Supported Arrays

This command applies to any individual storage array, including the E2700, E5600, E2800, E5700, EF600 and EF300 arrays, as long as all SMcli packages are installed.

Roles

To execute this command on an E2800, E5700, EF600, or EF300 storage array, you must have the Storage Admin role.

Context

Before you enter the autoConfigure storageArray command, run the show storageArray autoConfiguration command. The show storageArray autoConfiguration command returns configuration information in the form of a list of valid drive types, RAID levels, volume information, and hot spare information. (This list corresponds to the parameters for the autoConfigure storageArray command.) The controllers audit the storage array and then determine the highest RAID level that the storage array can support and the most efficient volume definition for the RAID level. If the configuration that is described by the returned list is acceptable, you can enter the autoConfigure storageArray command without any parameters. If you want to modify the configuration, you can change the parameters to meet your configuration requirements. You can change a single parameter or all of the parameters. After you enter the autoConfigure storageArray command, the controllers set up the storage array by using either the default parameters or those you selected.

Syntax

autoConfigure storageArray 
[driveType=(SAS | NVMe4K)] 
[driveMediaType=(hdd | ssd | allMedia | unknown)] 
[raidLevel=(0 | 1 | 3 | 5 | 6)] 
[volumeGroupWidth=numberOfDrives] 
[volumeGroupCount=numberOfVolumeGroups] 
[volumesPerGroupCount=numberOfVolumesPerGroup] 
[hotSpareCount=numberOfHotSpares] 
[segmentSize=segmentSizeValue] 
[cacheReadPrefetch=(TRUE | FALSE)] 
[readAheadMultiplier=multiplierValue] 
[securityType=(none | capable | enabled)] 
[secureDrives=(fips | fde)]
[dataAssurance=(none | enabled)]

Parameters

Parameter Description
driveType

The type of drives that you want to use for the storage array.

You must use this parameter when you have more than one type of drive in your storage array.

These drive types are valid:

  • SAS
  • NVMe4K
driveMediaType

The type of drive media that you want to use for the storage array.

You must use this parameter when you have more than one type of drive media in your storage array.

These drive media types are valid:

  • hdd – Use this option when you have hard drives.
  • ssd – Use this option when you have solid state disks.
  • unknown – Use if you are not sure what types of drive media are in the drive tray.
raidLevel The RAID level of the volume group that contains the drives in the storage array. Valid RAID levels are 0, 1, 3, 5, or 6.
volumeGroupWidth The number of drives in a volume group in the storage array.
volumeGroupCount The number of volume groups in the storage array. Use integer values.
volumesPerGroupCount The number of equal-capacity volumes per volume group. Use integer values.
hotSpareCount The number of hot spares that you want in the storage array. Use integer values.
segmentSize The amount of data (in KB) that the controller writes on a single drive in a volume before writing data on the next drive. Valid values are 4 (SSD only)8, 16, 32, 64, 128, 256, or 512.
cacheReadPrefetch The setting to turn on or turn off cache read prefetch. To turn off cache read prefetch, set this parameter to FALSE. To turn on cache read prefetch, set this parameter to TRUE.
readAheadMultiplier

This parameter defines how many additional data blocks are read into cache. Valid values range from 0 to 65535.

Note: This parameter is deprecated and will be removed in a future release of storage management software. For best operation use the cacheReadPrefetch parameter.
securityType

The setting to specify the security level when creating the volume groups and all associated volumes. These settings are valid:

  • none – The volume group and volumes are not secure.
  • capable – The volume group and volumes are capable of having security set, but security has not been enabled.
  • enabled – The volume group and volumes have security enabled.
secureDrives

The type of secure drives to use in the volume group. These settings are valid:

  • fips – To use FIPS compliant drives only.
  • fde – To use FDE compliant drives.
Important: Use this parameter along with the securityType parameter. If you specify none for the securityType parameter, the value of the secureDrives parameter is ignored, because non-secure volume groups do not need to have secure drive types specified.

Drives and volume groups

A volume group is a set of drives that are logically grouped together by the controllers in the storage array. The number of drives in a volume group is a limitation of the RAID level and the controller firmware. When you create a volume group, follow these guidelines:

Level Criteria for Tray Loss Protection Minimum number of trays required
Disk Pool The disk pool contains no more than two drives in a single tray. 6
RAID 6 The volume group contains no more than two drives in a single tray. 3
RAID 3 or RAID 5 Each drive in the volume group is located in a separate tray. 3
RAID 1 Each drive in a RAID 1 pair must be located in a separate tray. 2
RAID 0 Cannot achieve Tray Loss Protection. Not applicable
Level Criteria for drawer loss protection Minimum number of drawers required
Disk Pool The pool includes drives from all five drawers and there are an equal number of drives in each drawer. A 60-drive tray can achieve Drawer Loss Protection when the disk pool contains 15, 20, 25, 30, 35, 40, 45, 50, 55, or 60 drives. 5
RAID 6 The volume group contains no more than two drives in a single drawer. 3
RAID 3 or RAID 5 Each drive in the volume group is located in a separate drawer. 3
RAID 1 Each drive in a mirrored pair must be located in a separate drawer. 2
RAID 0 Cannot achieve Drawer Loss Protection. Not applicable

Hot spares

With volume groups, a valuable strategy to protect data is to assign available drives in the storage array as hot spare drives. A hot spare is a drive, containing no data, that acts as a standby in the storage array in case a drive fails in a RAID 1, RAID 3, RAID 5, or RAID 6 volume group. The hot spare adds another level of redundancy to the storage array.

Generally, hot spare drives must have capacities that are equal to or greater than the used capacity on the drives that they are protecting. Hot spare drives must be of the same media type, the same interface type, and the same capacity as the drives that they are protecting.

If a drive fails in the storage array, the hot spare is normally substituted automatically for the failed drive without requiring your intervention. If a hot spare is available when a drive fails, the controller uses redundancy data parity to reconstruct the data onto the hot spare. Data evacuation support also allows data to be copied to a hot spare before the software marks the drive "failed."

After the failed drive is physically replaced, you can use either of the following options to restore the data:

When you have replaced the failed drive, the data from the hot spare is copied back to the replacement drive. This action is called copyback.

If you designate the hot spare drive as a permanent member of a volume group, the copyback operation is not needed.

The availability of tray loss protection and drawer loss protection for a volume group depends on the location of the drives that comprise the volume group. Tray loss protection and drawer loss protection might be lost because of a failed drive and the location of the hot spare drive. To make sure that tray loss protection and drawer loss protection are not affected, you must replace a failed drive to initiate the copyback process.

The storage array automatically selects Data Assurance (DA)-capable drives for hot spare coverage of DA-enabled volumes.

Make sure you have DA-capable drives in the storage array for hot spare coverage of DA-enabled volumes. For more information about DA-capable drives, refer to Data Assurance feature.

Secure-capable (FIPS and FDE) drives can be used as a hot spare for both secure-capable and non-secure-capable drives. Non-secure-capable drives can provide coverage for other non-secure-capable drives, and for secure-capable drives if the volume group does not have the security enabled. A FIPS volume group can only use a FIPS drive as a hot spare; however, you can use a FIPS hot spare for non-secure-capable, secure-capable, and secure-enabled volume groups.

If you do not have a hot spare, you can still replace a failed drive while the storage array is operating. If the drive is part of a RAID 1, RAID 3, RAID 5, or RAID 6 volume group, the controller uses redundancy data parity to automatically reconstruct the data onto the replacement drive. This action is called reconstruction.

Segment size

The size of a segment determines how many data blocks that the controller writes on a single drive in a volume before writing data on the next drive. Each data block stores 512 bytes of data. A data block is the smallest unit of storage. The size of a segment determines how many data blocks that it contains. For example, an 8-KB segment holds 16 data blocks. A 64-KB segment holds 128 data blocks.

When you enter a value for the segment size, the value is checked against the supported values that are provided by the controller at run time. If the value that you entered is not valid, the controller returns a list of valid values. Using a single drive for a single request leaves other drives available to simultaneously service other requests. If the volume is in an environment where a single user is transferring large units of data (such as multimedia), performance is maximized when a single data transfer request is serviced with a single data stripe. (A data stripe is the segment size that is multiplied by the number of drives in the volume group that are used for data transfers.) In this case, multiple drives are used for the same request, but each drive is accessed only once.

For optimal performance in a multiuser database or file system storage environment, set your segment size to minimize the number of drives that are required to satisfy a data transfer request.

Cache read prefetch

Cache read prefetch lets the controller copy additional data blocks into cache while the controller reads and copies data blocks that are requested by the host from the drive into cache. This action increases the chance that a future request for data can be fulfilled from cache. Cache read prefetch is important for multimedia applications that use sequential data transfers. Valid values for the cacheReadPrefetch parameter are TRUE or FALSE. The default is TRUE.

Security type

Use the securityType parameter to specify the security settings for the storage array.

Before you can set the securityType parameter to enabled, you must create a storage array security key. Use the create storageArray securityKey command to create a storage array security key. These commands are related to the security key:

Secure drives

Secure-capable drives can be either Full Disk Encryption (FDE) drives or Federal Information Processing Standard (FIPS) drives. Use the secureDrives parameter to specify the type of secure drives to use. The values you can use are fips and fde.

Example command

autoConfigure storageArray securityType=capable secureDrives=fips;

Minimum firmware level

7.10 adds RAID level 6 capability and removes hot spare limits.

7.50 adds the securityType parameter.

7.75 adds the dataAssurance parameter.

8.25 adds the secureDrives parameter.