This appendix illustrates the following examples of how to configure storage on unencrypted MD2412 PowerVault (12 * 16 TB Self Encrypting Drives (SEDs)) external storage devices attached to S7 physical hosts.
Note:
The Enable Encryption on Series 6E or Series 7 Hosts topic describes the process to turn on encryption on NW servers and configured storage devices (MD2412).
If the user chooses to enable or turn on encryption before configuring storage (MD2412), the security on the controllers (internal and external) must be enabled and controller security key must be set. To enable the security on the controllers (internal and external) and set the controller security key, refer to Chapter 8 ->Security Key and RAID Management ->Create a security key in the Dell PowerEdge RAID Controller 12 User's Guide.
Once the security key is set, to enable encryption on the external storage, use preferSecure=1 when executing raidNew command to create RAID.
Alternatively, configure the external storage with preferSecure=0 when creating RAID and then follow the steps in Enable Encryption on Series 6E or Series 7 Hosts to turn on encryption.
Configure Storage for Archiver using MD2412
The following scenario configures storage on one, unencrypted, 12-Drive MD2412 PowerVault for an Archiver physical host.
- Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
- Execute the raidNew command with the following parameters using the controller number and the enclosure number you just recorded.
controller=1 enclosure=386 scheme=archiver preferSecure=0 commit=1
The following example illustrates what you should see after you create a RAID array.
-
Execute the raidList command to verify the new RAID array.
In Use: TRUE
Devices: <device>(for example, sdc)
-
Execute the devlist command to find the exact memory distribution for the newly created raids.
-
Execute the lsblk command at backend to list the newly created raids.
-
Execute the partNew command with the following parameters to create partitions and mount points as required.
name=sdc service=archiver volume=archiver commit=1
-
Execute devlist command to verify partitions created.
-
Execute the srvAlloc command with the following parameters to allocate the space to archiver service.
This adds storage to the archiver service configuration and restarts the service every time it is executed.
service=archiver volume=archiver0 commit=1
-
Execute the srvList command to verify the services allocated on the appliance.
-
Execute lsblk command to list all the raids and partitions in the service.
Configure Storage for Decoder using MD2412
The following scenario configures storage on one, unencrypted, 12-Drive MD2412 PowerVault for a Network Decoder physical host..
- Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
- Execute the raidNew command with the following parameters using the controller number and the enclosure number you just recorded.
controller=1 enclosure=302 scheme=decoder preferSecure=0 commit=1
-
Execute the raidList command to verify the new RAID array.
You should now see the following information.
In Use: TRUE
Devices: <devices>(for example, sdc, sdd)
-
Execute the devlist command to find the exact memory distribution for the newly created raids..
- Execute lsblk command at the backend to verify block devices created on the host.
-
Execute the partNew command to create the decodersmall partition first (decoder dir, index, metadb, sessiondb) on the smaller block device (sdc) with the following parameters.
name=sdc service=decoder volume=decodersmall commit=1
-
Execute the partNew command to create the decoder volume (packetdb) on the bigger block device of the two created (sdd) with the following parameters.
name=sdd service=decoder volume=decoder commit=1
-
Execute devlist command to verify partitions created.
-
Execute the srvAlloc command with the following parameters to add the storage information into the Service Configuration settings. Service is restarted each time the command is executed.
service=decoder volume=decodersmall commit=1
service=decoder volume=decoder commit=1
-
Execute the srvList command to verify the services allocated on the appliance.
-
Execute lsblk command to list all the raids and partitions in the service.
Configure Storage for Concentrator using MD2412
The following scenarios configure storage on one or more unencrypted, 12-Drive MD2412 PowerVault for a Concentrator physical host.
Note: All 12 drives on PowerVault MD2412 are HDDs. This is also used as storage for concentrator service whereas older PowerVault MD1400 for concentrator storage has mixed drive configuration with HDDs and SSDs. Since MD2412 has no support for SSDs and the concentrator service requires atleast 2 SSDs for index database, SSDs are to be installed on the concentrator physical host in slots 4 through 9 with a minimum of 3 drives.
Supported SSD configurations on the S7 concentrator host -
- 3 drives - slots 4,5 and 6 - RAID 5
- 6 drives - slots 4,5,6,7,8 and 9 - RAID 6
- 3 Drives + 3 Drives - RAID 5, initially 3 drives are installed followed by extension with another 3 drives.
The SSD drive packs are available in two sizes - 3 * 3.2 TB or 3 * 7.68 TB. In the following examples, the drive pack of 3 * 3.2 TB is used. When a larger drive pack (3 * 7.68 TB) is used, the virtual drives are larger in size.
Scenario 1:
3 SSD drives are added to the Concentrator physical host. Host is connected to one unencrypted 12-Drive MD2412 PowerVault.
- Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
SSD configuration on this host is as seen below. 3 SSDs are added to slots 4,5 and 6 on the concentrator host for configuring index.
To view details about the SSDs installed on controller 0, run the following command on the concentrator:
/opt/MegaRAID/perccli2/perccli2 /c0/eall/sall show
Partial output of the above command is as shown below.
- Execute the raidNew command with scheme=concentrator for controller (1) with HDDs and scheme=concentrator-metakit for controller (0) with SSDs.
To configure RAID for concentrator scheme, execute raidNew with the following parameters using the controller number and the enclosure number you just recorded from raidList.
controller=1 enclosure=386 scheme=concentrator preferSecure=0 commit=1
-
Execute the raidList command to verify the concentrator RAID created.
- Execute the raidNew command with the following parameters using the controller number and the enclosure number associated with SSDs added to the concentrator host. This creates the RAID for index.
controller=0 enclosure=286 scheme=concentrator-metakit preferSecure=0 commit=1
-
Execute the raidList command to verify the index RAID created.
-
Execute devlist to verify block devices created.
The same can be verified using lsblk.
-
Execute the partNew command to create the concentrator partition first with the following parameters. You must create the concentrator volume before index volume or it will fail. sdc is assoviated with HDDs on PowerVault 2412 and is to be used for concentrator volume.
name=sdc service=concentrator volume=concentrator commit=1
-
Execute the partNew command with the following parameters to create an index on SSDs. sdd is associated with the SSDs added and is to be used for index volume.
name=sdd service=concentrator volume=index commit=1
-
Run devlist to verify block devices have been configured.
-
Execute the srvAlloc command with the following parameters.
service=concentrator volume=concentrator commit=1
service=concentrator volume=index commit=1
-
Execute srvList to verify storage has been assigned as required.
-
Verify partitions and mounts on lsblk.
Scenario 2:
3 SSD Drives + 3 SSD Drives are installed on the Concentrator physical host. This means that initially 3 SSD drives are installed, followed by extension with another 3 drives.
Host is connected to two unencrypted 12-Drive MD2412 PowerVaults.
The following scenario configures storage as per the scenario described above.
- Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
SSD configuration on this host is as seen below. 3 SSDs from the first drive pack are added to slots 4,5 and 6 on the concentrator host for configuring index.
To view details about the SSDs installed on controller 0, run the following command on the concentrator:
/opt/MegaRAID/perccli2/perccli2 /c0/eall/sall show
Partial output of the above command is as shown below.
-
Execute the raidNew command with scheme=concentrator for controller (1) with HDDs and scheme=concentrator-metakit for controller (0) with SSDs.
To configure RAID for concentrator scheme, execute raidNew with the following parameters using the controller number and the enclosure number you just recorded from raidList.
controller=1 enclosure=386 scheme=concentrator preferSecure=0 commit=1
This creates concentrator RAID using the HDDs in PowerVault MD2412.
-
Execute the raidList command to verify the concentrator RAID created.
-
To configure RAID for index scheme, execute raidNew with the following parameters using the controller number and the enclosure number associated with SSDs added to the concentrator host. This creates the RAID for index.
controller=0 enclosure=286 scheme=concentrator-metakit preferSecure=0 commit=1
-
Execute raidList command to verify the index RAID created.
-
Add the second drive pack with another 3 SSDs.
SSD configuration on this host is as seen below. 3 SSDs from the second drive pack are added to slots 7,8 and 9 on the concentrator host for configuring index.
To view details about the SSDs installed on controller 0, run the following command on the concentrator:
/opt/MegaRAID/perccli2/perccli2 /c0/eall/sall show
Partial output of the above command is as shown below.
-
Configure RAID on the second PowerVault. Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
-
Execute the raidNew command with scheme=concentrator for controller (1) with HDDs and scheme=concentrator-metakit for controller (0) with SSDs.
To configure RAID for concentrator scheme, execute raidNew with the following parameters using the controller number and the enclosure number you just recorded from raidList.
This creates concentrator RAID using the HDDs in PowerVault MD2412.
controller=1 enclosure=400 scheme=concentrator preferSecure=0 commit=1
-
Execute the raidList command to verify the concentrator RAID created.
-
Execute the raidNew command with the following parameters using the controller number and the enclosure number associated with SSDs added to the concentrator host. This creates the RAID for index.
controller=0 enclosure=286 scheme=concentrator-metakit preferSecure=0 commit=1
-
Execute the raidList command to verify the index RAID created.
-
Execute devlist to verify block devices created.
-
The same can be verified using lsblk.
-
Execute the partNew command to create the concentrator partition first with the following parameters. You must create the concentrator volume before index volume or it will fail.
sdc is associated with HDDs on PowerVault MD2412 and is to be used for concentrator volume.
name=sdc service=concentrator volume=concentrator commit=1
-
Execute the partNew command with the following parameters to create an index on SSDs. sdd is associated with the SSDs added and is to be used for index volume.
name=sdd service=concentrator volume=index commit=1
-
Run devlist to verify block devices have been configured.
-
Verify partitions and mounts on lsblk.
-
Execute the partNew command to create the concentrator partition on the second PowerVault with the following parameters. You must create the concentrator volume before index volume or it will fail.
sde is associated with HDDs on PowerVault MD2412 and is to be used for concentrator volume.
name=sde service=concentrator volume=concentrator commit=1
-
Execute the partNew command to create the index partition on SSDs associated with the second SSD drive-pack. sdf is associated with these SSDs and is to be used for index volume.
name=sdf service=concentrator volume=index commit=1
-
Run devlist to verify block devices have been configured.
-
Verify partitions and mounts on lsblk.
-
Execute the srvAlloc commands with the following parameters.
service=concentrator volume=concentrator commit=1
service=concentrator volume=index commit=1
service=concentrator volume=concentrator0 commit=1
service=concentrator volume=index0 commit=1
-
Execute srvList to verify storage has been assigned as required.
-
Verify partitions and mounts on lsblk.
Configure Storage for Log Hybrid using MD2412
The following scenario configures storage on one unencrypted, 12-Drive MD2412 PowerVault for a Log Hybrid physical host.
-
Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
- Execute the raidNew command with the following parameters using the controller number and the enclosure number you just recorded.
controller=1 enclosure=288 scheme=log-hybrid commit=1
The following example illustrates what you should see after you create a RAID array.
Execute the raidList command to verify the RAID created.
Execute the devlist command to find the exact memory distribution between the newly created RAIDS. In Log Hybrid, the distribution is exactly equal so any service can be installed in any of the RAIDs.
Execute lsblk to verify the block devices created.
- Execute the partNew commandwith the following parameters to create partitions and mount points in the /etc/fstab file.
name=sdg service=logdecoder volume=logdecoder commit=1
name=sdh service=concentrator volume=concentrator commit=1
Execute devlist to verify partitions created.
- Execute the srvAlloc command with the following parameters to allocate the space to logdecoder and concentrator services.
- This adds storage to the logdecoder service configuration and restarts the service every time it is executed.
service=logdecoder volume=logdecoder0 commit=1
- This adds storage to concentrator service configuration and restarts the service every time it is executed.
service=concentrator volume=concentrator0 commit=1
-
Execute the srvList command to verify the services allocated on the appliance.
-
Execute the lsblk command in backend to see all the raids and partitions inside the service.
Configure Storage for Network Hybrid using MD2412
The following scenario configures storage on an unencrypted, 12-Drive MD2412 PowerVault for a Network Hybrid physical host.
-
Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
-
Execute the raidNew command with the following parameters using the controller number and the enclosure number you just recorded.
controller=1 enclosure=288 scheme=network-hybrid preferSecure=0 commit=1
The following example illustrates what you should see after you create a RAID array.
Following is the response from raidList after creating RAID array.
Execute devlist command to find the exact memory distribution between the newly created RAIDs. In Network Hybrid, the memory for ‘sdh’ block device is more than ‘sdf’ block device, therefore packetdb will be installed in the device with higher memory allocated which is ‘sdh’ .
-
Execute the partNew command with the following parameters to create partitions and mount points in the /etc/fstab file.
name=sdf service=concentrator volume=concentrator commit=1
name=sdh service=decoder volume=decoder commit=1
-
Execute the srvAlloc command with the following parameters to allocate the space to decoder and concentrator services.
This adds storage to the decoder service configuration and restarts the service every time it is executed.
service=decoder volume=decoder0 commit=1
This adds storage to the concentrator service configuration and restarts the service every time it is executed.
service=concentrator volume=concentrator0 commit=1
Execute the srvList command to verify the services allocated on the appliance.
-
Execute lsblk command to list all the raids and partitions in the service.
Configure Storage for Endpoint Log Hybrid using MD2412
The following scenario configures storage on one unencrypted, 12-Drive MD2412 PowerVault for an Endpoint Log Hybrid physical host.
-
Execute the raidList command.
- Record the Controller Number, Enclosure Number, In Use, Drives, and Devices.
You should see the following information.
In Use: FALSE
Devices: <empty>
- Verify the Drive Count, Size, and Vendor.
The following example illustrates what you should see before you create a RAID array.
-
Execute the raidNew command with the following parameters using the controller number and the enclosure number you just recorded.
In this case, the security key has been set on the controller PERCH965e. Hence, preferSecure=1 parameter is used to enable encryption. If the security key is not set on the controller, parameter preferSecure=0 can be used to complete configuring RAID on the controller.
controller=1 enclosure=302 scheme=log-hybrid preferSecure=1 commit=1
The following example illustrates what you should see after you create a RAID array.
Following is the response from raidList after creating RAID array.
Execute the devlist command to find the exact memory distribution for the newly created raids. In Endpoint Log Hybrid, both are exactly equal. Hence, any service can be installed in any of the raid.
Execute the lsblk command at backend to list the newly created raids on the Endpoint Log Hybrid appliance.
-
Execute the partNew command with the following parameters to create partitions and mount points as required.
name=sdf service=logdecoder volume=logdecoder commit=1
name=sdg service=concentrator volume= concentrator commit=1
Execute the devlist command to verify partitions created.
-
Execute the srvAlloc command with the following parameters to allocate the space to logdecoder and concentrator services.
This adds storage to the logdecoder service configuration and restarts the service every time it is executed.
service=logdecoder volume=logdecoder0 commit=1
This adds storage to the concentrator service configuration and restarts the service every time it is executed.
service=concentrator volume=concentrator0 commit=1
Execute the srvList command to verify the services allocated on the appliance.
-
Execute lsblk command to list all the raids and partitions in the service.