OceanStor Dorado 6.1 Disk Encryption User Guide
OceanStor Dorado 6.1 Disk Encryption User Guide
6.1.x
Issue 03
Date 2022-04-15
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Purpose
This document introduces how to install and configure key management servers
connected to the storage systems that use self-encrypting drives (SEDs).
NOTE
The following table lists the product models that this document is applicable to.
NOTICE
This document is updated periodically with the software version. The operations
described in this document use the latest version as an example. Note that the
supported functions and features vary according to the software version. The
content in this document is for reference only.
Intended Audience
This document is intended for:
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue 03 (2022-04-15)
This issue is the third official release.
Optimized descriptions.
Issue 02 (2022-01-25)
This issue is the second official release.
Issue 01 (2021-09-30)
This issue is the first official release.
Contents
B Glossary................................................................................................................................... 92
C Acronyms and Abbreviations........................................................................................... 107
1 Overview
OceanStor Dorado series storage systems support disk encryption, which provides
secure storage services without impacting storage performance.
NOTE
Only self-encrypting drives (SEDs) are supported for the disk encryption feature.
If you enable Data Encryption when creating a storage pool, disk encryption is
enabled. The storage system activates the AutoLock function on SEDs and uses the
authentication keys (AKs) allocated by the key management server. SED access is
protected by the AutoLock function and only the storage system itself can access
its SEDs. When the storage system accesses an SED, it acquires an AK from the key
management server. If the AK's hash value is consistent with that on the SED, the
SED decrypts the data encryption key (DEK) for data encryption/decryption. If the
AKs' hash values are different, all read and write operations will fail.
If you do not enable Data Encryption when creating a storage pool, disk
encryption is disabled and the AutoLock function of SEDs is deactivated. In this
case, the SEDs use the default AKs and access to the SEDs is not restricted. The
SEDs can be read and written normally. Data written to the SEDs is encrypted
using DEKs, regardless of whether Disk Encryption is enabled.
Key management is critical for disk encryption. OceanStor Dorado series storage
systems support internal and external key management.
NOTE
The key management server has passed FIPS certification and provides key storage and
management functions. The server can be connected to storage systems to provide
interfaces and functions required by the KMIP protocol. The storage systems can invoke
these interfaces to create, update, destroy, and query keys required by the disk encryption
service.
NOTICE
You cannot use internal and external key management at the same time. When
you change from one method to the other, you must delete original services and
re-create self-encrypting storage pools. Otherwise, disk encryption cannot take
effect.
NOTICE
If all keys are damaged or lost, the SEDs in the self-encrypting storage pool
cannot be identified, resulting in data loss.
Prerequisites
SEDs have been configured on the storage system. The AutoLock status of the
SEDs is Disable.
To query the AutoLock status of the SEDs, you can log in to the CLI of the storage
system and run the show disk general command.
admin:/>show disk general
ID Health Status Running Status Type Capacity Role Disk Domain ID Speed(RPM) Health
Mark Bar Code Item AutoLock State Key Expiration Time
------ ------------- -------------- -------- --------- --------- -------------- ---------- -----------
-------------------- -------- -------------- -------------------
DAE000.0 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000131 02350LGX OFF --
DAE000.1 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000124 02350LGX OFF --
DAE000.2 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000238 02350LGX OFF --
DAE000.3 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000228 02350LGX OFF --
DAE000.4 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10FA000227 02350LGX OFF --
DAE000.5 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10FA000187 02350LGX OFF --
DAE100.0 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000159 02350LGX OFF --
DAE100.1 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000161 02350LGX OFF --
DAE100.2 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10G3000505 02350LGX OFF --
DAE100.3 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000182 02350LGX OFF --
DAE100.4 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10G3000511 02350LGX OFF --
Procedure
Step 1 Log in to DeviceManager and create a storage pool.
The Create Storage Pool page is displayed.
NOTE
Use either of the following methods to go to the Create Storage Pool page:
● When you log in to the storage system for the first time, you can create a storage pool
in Custom mode in the initial configuration wizard. For details, see "Initially Configuring
a Storage Device" in the initialization guide specific to your product model.
● On the menu bar, choose System > Storage Pools and then click Create.
NOTE
Alternatively, you can choose Settings > Key Service from the menu bar.
2. In the function pane on the right, click Modify. Then select Enable the
internal key service.
3. (Optional) Configure a key backup policy.
When a key changes, the storage system automatically backs up the key's
information on the backup server. If all keys and backup keys on the storage
system are damaged or lost, you can obtain the latest backup keys from the
backup server and import them to the storage system for restoration.
NOTE
The keys uploaded to the backup server are encrypted and signed to prevent
disclosure and tampering.
Before using the key backup function, ensure that the backup server has been
successfully configured and communicates properly with the storage system.
Table 2-1 lists the SSH key exchange algorithms supported by the storage
system. When deploying the backup server, use SFTP server tools that support
these key exchange algorithms, such as xlight FTP.
KexAlgorithms – ecdh-sha2-nistp256
– ecdh-sha2-nistp384
– ecdh-sha2-nistp521
– diffie-hellman-group-exchange-sha256
– diffie-hellman-group-exchange-sha1
– diffie-hellman-group14-sha1
NOTE
For details about how to use xlight FTP, see 2.6.1 Using the xlight FTP Tool to
Deploy the FTP Backup Server.
NOTE
Alternatively, you can choose Settings > Key Service from the menu bar and
click Modify.
c. Click Test to test the connectivity between the backup server and the
storage system.
4. Click Save to save the configurations of the internal key service.
Step 3 Set other parameters of the storage pool. After the self-encrypting storage pool is
created, the storage system automatically generates encryption keys.
For the parameter description, see section "Creating a Storage Pool" in the Basic
Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the specific product model.
Save the exported key file properly and do not make any change. When the key is
damaged, this file can be used for recovery.
----End
Follow-up Procedure
● After creating the self-encrypting storage pool, you can create LUNs or file
systems to allocate the storage space to application servers. For details, see
Basic Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the corresponding product model.
NOTE
Prerequisites
This operation can be performed only by the super administrator and
administrator.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose System > Storage Pools.
Step 3 Click More on the right of the desired storage pool and choose Rekey.
NOTE
The Success dialog box only indicates that the key update operation is issued successfully. It
takes several minutes for the system to update the keys for all SEDs (depending on the
number of SEDs). After the update is complete, the system reports an event "succeeded in
updating the key of self-encrypting disks". If you want to perform other operations (for
example, deleting the storage pool) after the update operation is issued, ensure that you
perform these operations after the system has reported this event.
----End
Follow-up Procedure
After the self-encrypting storage pool is updated, export keys in time.
2.5 FAQs
This section provides FAQs in the process of using the internal key management
service.
Answer
NOTICE
Step 1 Export the latest encryption key files of disks on the storage system.
1. Log in to DeviceManager.
2. Choose Settings > Key Service. In the function pane, click Export Internal
Keys to export the keys manually on the browser.
Step 2 Obtain the encryption keys on the backup server.
Use the user name and password configured in 2.3 Configuring the Internal Key
Management Service to log in to the backup server and obtain the encryption
key files from the set path.
Step 3 After analysis, select encryption key files that can be used for key recovery.
Step 4 Log in to the CLI and enter the developer mode. Run the import kms key
command to import the encryption key files and recover keys.
developer:/>import kms key ip=10.10.10.1 user=admin password=****** path=InnerKey.dat protocol=FTP
WARNING: You are about to import a key file of the internal key management service, which will overwrite
the original key data. If the operation is inappropriate, it may cause the internal key management service to
lose some key.
Suggestion:
1. Confirm that the key file to be imported is up-to-date, and back up the key of the internal key
management service of the current system before the import.
2. During the key import, creating, updating, and deleting the disk domain of self-encrypting disks are all
forbidden.
Have you read warning message carefully?(y/n)y
NOTICE
When keys are being recovered, do not perform any operation on self-encrypting
storage pools.
----End
Answer
If the disk encryption key is lost, the storage system cannot access the SEDs after
a transient interruption occurs. This will result in a storage pool fault and service
interruption.
You can recover the services as follows:
NOTICE
On the CLI, run show disk general to check the status of each encrypted disk.
admin:/>show disk general
ID Health Status Running Status Type Capacity Role Disk Domain ID Speed(RPM) Health
Mark Bar Code Item AutoLock State Key Expiration Time
------ ------------- -------------- -------- --------- --------- -------------- ---------- -----------
-------------------- -------- -------------- -------------------
DAE000.0 Fault Online SSD SED 561.994GB Member Disk 0 10000 -- 210235G6BB1000000007 0235G6BB
ON 2020-12-31
DAE000.1 Fault Online SSD SED 561.994GB Member Disk 0 10000 -- 210235G6BB1000000007 0235G6BB
ON 2020-12-31
DAE000.2 Fault Online SSD SED 561.994GB Member Disk 0 10000 -- 210235G6BB1000000007 0235G6BB
ON 2020-12-31
NOTE
If the AutoLock State of a disk is ON and Health Status is Fault, this is a faulty disk.
Step 3 Power off and then power on all the faulty disks.
On the CLI, run poweroff disk and poweron disk in developer mode.
engineer:/>poweroff disk disk_id=DAE000.0
DANGER: You are about to power off the disk.
This operation causes the disk to be unreadable and unwritable for services. If the disk domain where the
disk resides is in the reconstruction or degradation state, this operation may cause reconstruction failure,
service interruption, and data loss.
Suggestion: Before performing this operation, check the disk properties and status of the disk domain that
houses the disk to avoid reconstruction failure, service interruption and data loss. Back up data before
powering off.
Have you read danger alert message carefully?(y/n)y
Are you sure you really want to perform the operation?(y/n)y
Command executed successfully.
engineer:/>poweron disk disk_id=DAE000.0
Command executed successfully.
NOTE
If a faulty disk is not a member of the involved storage pool, the disk's object will be
released after it is powered off. As a result, powering on the disk will fail.
Step 4 After all faulty disks have been powered on, check the health status.
On the CLI, run show disk_domain general to check the status.
admin:/>show disk_domain general
ID Name Health Status Running Status Total Capacity Free Capacity Hot Spare Capacity Used Hot Spare
Capacity
-- ---- ------------- -------------- -------------- ------------- ------------------ -----------------------
0 d0 Normal Online 4.055TB 556.242GB 524.312GB 0.000B
----End
2.6.1 Using the xlight FTP Tool to Deploy the FTP Backup
Server
This section describes how to deploy the FTP backup server by using the xlight FTP
tool. For details on how configure other FTP servers, see their respective
configuration documentation.
Prerequisites
● The FTP server software installation package is ready.
● The IP address to be configured can properly communicate with the storage
system.
Procedure
Step 1 Start the Xlight FTP server software.
Select the added virtual server and click to start the server.
NOTE
You can also select the added virtual server, right-click, and choose Start Server to start the
server.
2. Click .
The adding users dialog box is displayed.
3. In the dialog box, enter Username and Password and set Home Directory.
4. Click OK.
The user is added, and user information is displayed on the user page.
----End
This chapter introduces how to install and configure KeySecure (K250) key
management servers of SafeNet.
3.1 About KeySecure Key Management Servers
3.2 Logging In to DeviceManager
3.3 Configuration Process
3.4 Hardware Deployment
3.5 Configuring a Key Management Server
3.6 FAQs
Hardware
Figure 3-1 and Figure 3-2 show the front and rear panels of a KeySecure key
management server, respectively.
Typical Networking
A storage system connects to two KeySecure key management servers that are
configured into a cluster in active/standby mode. Figure 3-3 shows the typical
networking.
NOTE
On a KeySecure key management server, the management network port (used to access
the key management server's management interface) and the service network port (used
to connect to a storage array) share the eth1 port on the front panel.
To ensure that the key management servers can work properly, verify that the
network communication between the following components is normal:
● Storage system's management network port -> key management servers'
eth1
● Maintenance terminal -> key management servers' eth1
● Key management server 1's eth1 -> key management server 2's eth1
● Backup server's network port -> key management servers' eth1
Start
Install key management
servers.
End
Prerequisites
● The installation positions of the two key management servers have been
determined.
● Cables and tools required for hardware installation have been prepared,
including:
– Serial cable (included in the product package)
– Power cable (included in the product package)
– Network cable (not included in the product package)
– Phillips screwdriver (not included in the product package)
– (Optional) USB-to-serial cable (not included in the product package)
NOTE
Prepare the USB-to-serial cable if the maintenance terminal has no serial port.
Procedure
Step 1 Determine the installation positions.
Step 5 Use a network cable to connect the eth1 port of the key management server to
the management network port of the storage system through a switch.
Step 6 Insert one end of the power cable to the electric socket at the server back, and
insert the other end to the external AC power module.
Step 8 Put the baffle plate on the front panel, then insert and turn the key.
Step 9 Repeat Step 3 to Step 8 to install and power on the other key management
server.
Step 10 If the maintenance terminal has no serial port, use the USB-to-serial cable to
connect the USB port of the maintenance terminal to the serial port of the key
management server.
----End
After two key management servers with the same configurations are clustered,
the two servers provide the encryption service together. If one of them becomes
faulty or fails to provide the encryption service, the storage system automatically
connects to the other one.
For details on how to initialize key management servers and create a cluster, refer
to the key management servers' user guide and consult technical support
engineers of the server manufacturer.
Context
The certificate generated on the storage system is not signed. It must be signed on
the key management server.
Procedure
Step 1 Log in to DeviceManager.
Step 3 On the Certificate Management page, choose KMC certificate, and click Export
Request File. On the displayed page, set the Certificate Key Algorithm to RSA
2048 or RSA 4096, and then click OK.
NOTE
You can also click KMC certificate. On the Certificate Details page that is displayed, click
Operation > Export Request File, set the Certificate Key Algorithm to RSA 2048 or RSA
4096, and then click OK.
----End
Precautions
To ensure that the key management server can identify the storage system
successfully, the local user name of the key management server must be set to
Storage, which is the same as the OU value in the signed certificate of the storage
system.
Procedure
Step 1 Log in to DeviceManager.
You can also click KMC certificate. On the Certificate Details page that is displayed,
click Operation > Import Certificate.
2. Import the signed certificate and CA certificate. Table 3-1 describes the
parameters.
3. Click OK.
The Warning dialog box is displayed.
4. Carefully read the content in the dialog box, select I have read and
understand the consequences associated with performing this operation,
and click OK.
The Success dialog box is displayed.
5. Click OK.
----End
Context
A storage system needs two key management servers.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Key Service. In the function pane on the right, click Modify.
Then select Enable the external key service.
Step 3 Specify the key management server parameters listed in Table 3-2.
NOTE
A storage system can connect to a maximum of two key management servers in a cluster.
The following example adds one key management server to the storage system.
Step 4 Import the signed certificate and CA certificate. Table 3-3 describes the
parameters.
----End
Follow-up Procedure
After the storage system has connected to the key management servers, wait for 2
to 3 minutes before performing follow-up procedures.
Prerequisites
SEDs have been configured on the storage system. The AutoLock status of the
SEDs is OFF.
To query the AutoLock status of the SEDs, you can log in to the CLI of the storage
system and run the show disk general command.
Procedure
Step 1 Log in to DeviceManager and create a storage pool.
The Create Storage Pool page is displayed.
NOTE
Use either of the following methods to go to the Create Storage Pool page:
● When you log in to the storage system for the first time, you can create a storage pool
in Custom mode in the initial configuration wizard. For details, see "Initially Configuring
a Storage Device" in the initialization guide specific to your product model.
● On the menu bar, choose System > Storage Pools and then click Create.
Step 2 Create a self-encrypting storage pool and automatically generate encryption keys
on the storage system.
1. Select Advanced and enable Data Encryption. Disk encryption is enabled for
all SEDs in the storage pool.
NOTE
After a storage pool has been created, data encryption cannot be enabled or disabled
for the storage pool.
2. Set other parameters for the storage pool.
For the parameter description, see section "Creating a Storage Pool" in the
Basic Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the specific product model.
3. Click OK.
Confirm your operation as prompted.
----End
Follow-up Procedure
After creating the self-encrypting storage pool, you can create LUNs or file
systems to allocate the storage space to application servers. For details, see Basic
Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the corresponding product model.
NOTE
3.6 FAQs
This section provides the FAQs for the configuration and maintenance of the key
management server.
Answer
Step 1 Log in to the key management server's management interface through the serial
port.
Step 2 Run the config command to enter the config mode.
Step 3 Run the edit ras settings command and enter n to close the client certificate
verification.
SafeNet-01 (config)# edit ras settings
Available IP addresses:
1. All
2. 172.17.7.29
Web Admin Server IP (1-2)[1]:1
Web Admin Server Port [9443]: 9443
Web Admin Client Certificate Authentication (y/n) [n]: n
Available IP addresses:
1. All
2. 172.17.7.29
SSH Admin Server IP (1-2)[1]:1
SSH Admin Server Port [22]: 22
Successfully changed Remote Admin Settings.
SafeNet-01 (config)# Connection to 172.17.7.29 closed by remote host.
Connection to 172.17.7.29 closed.
----End
Answer
Step 1 Log in to the key management server's web interface.
Step 2 Check whether Username Field in Client Certificate of the KMIP server is OU
(Organization Unit).
1. Choose Device > Key Server.
2. In the Cryptographic Key Server area, select the KMIP server and click
Properties.
3. In the Authentication Settings area, check whether Username Field in
Client Certificate is OU (Organization Unit).
– If yes, go to the next step.
– If no, click Edit, set Username Field in Client Certificate to OU
(Organization Unit), and click Save. Then go to the next step.
Step 3 Check whether a local user named Storage is created.
1. Choose Security > Users & Groups > Local Users & Groups.
2. In the Local Users area, check whether a local user whose Username is
Storage exists.
– If yes, re-create the key on the storage system.
– If no, create a local user whose Username is Storage, then re-create the
key on the storage system.
----End
This chapter describes how to install the SecKMS key management server of
Sansec and how to connect it to the storage system.
NOTICE
The version of the SecKMS key management server must be 2.16.0 or later. If your
server is running an earlier version, contact the server manufacturer for the
upgrade files and upgrade method.
Hardware
The SecKMS key management server is a 2 U device. Figure 4-1 and Figure 4-2
show its front and rear panels, respectively.
5 Power button - -
Typical Networking
A storage system connects to two SecKMS key management servers that are
configured into a cluster in active/standby mode. Figure 4-3 shows the typical
networking.
NOTE
On the SecKMS key management server, the management port (for accessing the server's
management console) and the service port (for connecting to a storage system) can either
share a physical network port or use different physical ports. In the following example, the
management and service ports share a physical network port (LAN1).
To ensure that the key management servers can work properly, verify that the
network communication between the following components is normal:
Start
Install key management
servers.
End
Prerequisites
● The installation positions of the two key management servers have been
determined.
● Cables and tools required for hardware installation have been prepared,
including:
– Serial cable (included in the product package)
– Power cable (included in the product package)
– Network cable (not included in the product package)
Prepare the USB-to-serial cable if the maintenance terminal has no serial port.
Procedure
Step 1 Determine the installation positions.
Step 5 Use a network cable to connect the LAN1 port of the key management server to
the management network port of the storage system through a switch.
Step 6 Insert one end of the power cable to the electric socket at the server back, and
insert the other end to the external AC power module.
Step 8 Put the baffle plate on the front panel, then insert and turn the key.
Step 9 Repeat Step 3 to Step 8 to install and power on the other key management
server.
Step 10 If the maintenance terminal has no serial port, use the USB-to-serial cable to
connect the USB port of the maintenance terminal to the serial port of the key
management server.
----End
NOTICE
● Ensure that the key management server has been initialized and a cluster has
been created before connecting it to the storage system.
● The version of the SecKMS key management server must be 2.16.0 or later. If
your server is running an earlier version, contact the server manufacturer for
the upgrade files and upgrade method.
Prerequisites
The key management server has been initialized and added to a cluster.
Procedure
Step 1 On the browser of the maintenance terminal, enter https://XXX.XXX.XXX.XXX:
9443/SecKMS in the address box and press Enter. Log in to the key management
server's web management page using the password or USB key authentication.
Step 2 Choose Device CAs > Local CAs from the navigation tree on the left.
----End
Prerequisites
A local CA has been created on the key management server.
Procedure
Step 1 On the browser of the maintenance terminal, enter https://XXX.XXX.XXX.XXX:
9443/SecKMS in the address box and press Enter. Log in to the key management
server's web management page using the password or USB key authentication.
Step 2 Choose Device CAs > Trusted CAs from the navigation tree on the left.
The Trusted CA Lists page is displayed.
The Choose Local CAs & Known CAs page is displayed, as shown in Figure 4-9.
Step 4 Select the local CA created in 4.5.1 Creating a Local CA and enter the profile
name.
----End
Prerequisites
The key management server has been initialized and added to a cluster.
Procedure
Step 1 On the browser of the maintenance terminal, enter https://XXX.XXX.XXX.XXX:
9443/SecKMS in the address box and press Enter. Log in to the key management
server's web management page using the password or USB key authentication.
Step 2 Choose SSL Certificates > SSL Certificates from the navigation tree on the left.
The SSL Certificate List page is displayed.
----End
Prerequisites
● A local CA has been created on the key management server and added to the
trusted CA list.
● An SSL certificate has been created on the key management server.
Procedure
Step 1 On the browser of the maintenance terminal, enter https://XXX.XXX.XXX.XXX:
9443/SecKMS in the address box and press Enter. Log in to the key management
server's web management page using the password or USB key authentication.
Step 2 Choose SSL Certificates > SSL Certificates from the navigation tree on the left.
The SSL Certificate List page is displayed.
Step 3 Select the SSL certificate created in 4.5.3 Creating an SSL Certificate and click
in the lower part of the page to download the certificate.
Step 4 Choose Device CAs > Local CAs from the navigation tree on the left.
Step 5 Select the CA created in 4.5.1 Creating a Local CA and click in the lower part
of the page to issue a signature request.
Table 4-3 describes the signature request parameters. Set Certificate Purpose to
Server, Certificate Duration (Days) to a value no greater than the validity period
of the local CA, and Certificate Request to the SSL certificate content copied in
Step 3, as shown in Figure 4-14.
Step 6 Click Sign. The system returns to the Local CAs page.
Step 7 Select the CA used in Step 5 and click in the lower part of the page.
The Local Signed Certificate page is displayed.
Step 8 Select the local signed certificate and click in the lower part of the page to
download the certificate.
Open the downloaded certificate and copy its content.
Step 9 Choose SSL Certificates > SSL Certificates from the navigation tree on the left.
The SSL Certificate List page is displayed.
Select the SSL certificate created in 4.5.3 Creating an SSL Certificate and click
in the lower part of the page to install the certificate.
Step 10 Paste the certificate content copied in Step 8 to the blank area.
----End
Prerequisites
● A local CA has been created on the key management server and added to the
trusted CA list.
● An SSL certificate has been created and signed on the key management
server.
Procedure
Step 1 On the browser of the maintenance terminal, enter https://XXX.XXX.XXX.XXX:
9443/SecKMS in the address box and press Enter. Log in to the key management
server's web management page using the password or USB key authentication.
Step 2 Choose Server Management > Server List from the navigation tree on the left.
Step 3 Check whether the status of KMIP_TCP is run. If it is not, click in the lower part
of the page to start the KMIP_TCP service.
Step 4 Choose Key Management > Key Servers from the navigation tree on the left.
----End
Context
The certificate generated on the storage system is not signed. It must be signed on
the key management server.
Procedure
Step 1 Log in to DeviceManager.
Step 3 On the Certificate Management page, choose KMC certificate, and click Export
Request File. On the displayed page, set the Certificate Key Algorithm to RSA
2048 or RSA 4096, and then click OK.
NOTE
You can also click KMC certificate. On the Certificate Details page that is displayed, click
Operation > Export Request File, set the Certificate Key Algorithm to RSA 2048 or RSA
4096, and then click OK.
----End
Procedure
Step 1 On the browser of the maintenance terminal, enter https://XXX.XXX.XXX.XXX:
9443/SecKMS in the address box and press Enter. Log in to the key management
server's web management page using the password or USB key authentication.
Step 2 Choose Device CAs > Local CAs from the navigation tree on the left.
Step 3 Select the CA created in section 4.5.1 Creating a Local CA and click in the
lower part of the page to issue a signature request.
Table 4-4 describes the signature request parameters. Set Certificate Purpose to
Client, Certificate Duration (Days) to a value no greater than the validity period
of the local CA, and Certificate Request to the content of the storage system
certificate obtained in 4.5.6.1 Generating and Exporting a Certificate on the
Storage System, as shown in Figure 4-22.
Step 4 Click Sign. The system returns to the Local CAs page.
Step 5 Select the CA certificate used for the signature and click in the lower part of
the page to download the certificate.
Step 6 Click in the lower part of the page. The Local Signed Certificate page is
displayed.
Step 7 Select the local signed certificate and click in the lower part of the page to
download the certificate.
----End
Procedure
Step 1 Log in to DeviceManager.
NOTE
You can also click KMC certificate. On the Certificate Details page that is displayed,
click Operation > Import Certificate.
2. Import the signed certificate and CA certificate. Table 4-5 describes the
parameters.
3. Click OK.
The Warning dialog box is displayed.
4. Carefully read the content in the dialog box, select I have read and
understand the consequences associated with performing this operation,
and click OK.
The Success dialog box is displayed.
5. Click OK.
----End
Context
A storage system needs two key management servers.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Key Service. In the function pane on the right, click Modify.
Then select Enable the external key service.
Step 3 Specify the key management server parameters listed in Table 4-6.
NOTE
A storage system can connect to a maximum of two key management servers in a cluster.
The following example adds one key management server to the storage system.
Step 4 Import the signed certificate and CA certificate. Table 4-7 describes the
parameters.
Step 6 Repeat Step 3 to add the other key management server in the cluster.
----End
Follow-up Procedure
After the storage system has connected to the key management servers, wait for 2
to 3 minutes before performing follow-up procedures.
Prerequisites
SEDs have been configured on the storage system. The AutoLock status of the
SEDs is OFF.
To query the AutoLock status of the SEDs, you can log in to the CLI of the storage
system and run the show disk general command.
admin:/>show disk general
ID Health Status Running Status Type Capacity Role Disk Domain ID Speed(RPM) Health
Mark Bar Code Item AutoLock State Key Expiration Time
------ ------------- -------------- -------- --------- --------- -------------- ---------- -----------
-------------------- -------- -------------- -------------------
DAE000.0 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000131 02350LGX OFF --
DAE000.1 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000124 02350LGX OFF --
DAE000.2 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000238 02350LGX OFF --
DAE000.3 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000228 02350LGX OFF --
DAE000.4 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10FA000227 02350LGX OFF --
DAE000.5 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10FA000187 02350LGX OFF --
DAE100.0 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000159 02350LGX OFF --
DAE100.1 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000161 02350LGX OFF --
DAE100.2 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10G3000505 02350LGX OFF --
DAE100.3 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000182 02350LGX OFF --
DAE100.4 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10G3000511 02350LGX OFF --
Procedure
Step 1 Log in to DeviceManager and create a storage pool.
The Create Storage Pool page is displayed.
NOTE
Use either of the following methods to go to the Create Storage Pool page:
● When you log in to the storage system for the first time, you can create a storage pool
in Custom mode in the initial configuration wizard. For details, see "Initially Configuring
a Storage Device" in the initialization guide specific to your product model.
● On the menu bar, choose System > Storage Pools and then click Create.
Step 2 Create a self-encrypting storage pool and automatically generate encryption keys
on the storage system.
1. Select Advanced and enable Data Encryption. Disk encryption is enabled for
all SEDs in the storage pool.
NOTE
After a storage pool has been created, data encryption cannot be enabled or disabled
for the storage pool.
2. Set other parameters for the storage pool.
For the parameter description, see section "Creating a Storage Pool" in the
Basic Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the specific product model.
3. Click OK.
Confirm your operation as prompted.
----End
Follow-up Procedure
After creating the self-encrypting storage pool, you can create LUNs or file
systems to allocate the storage space to application servers. For details, see Basic
Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the corresponding product model.
NOTE
This chapter introduces how to install and configure KeySecure (K170v) key
management servers of SafeNet.
NOTE
Typical Networking
A storage system connects to two key management servers that are configured
into a cluster in active/standby mode. Figure 5-1 shows the typical networking.
NOTE
On a key management server, the management network port (used to access the key
management server's management interface) and the service network port (used to
connect to a storage array) share the eth1 port on the front panel.
To ensure that the key management servers can work properly, verify that the
network communication between the following components is normal:
Start
Install key management
servers.
End
Prerequisites
● The installation positions of the two key management servers have been
determined.
● Cables and tools required for hardware installation have been prepared,
including:
Prepare the USB-to-serial cable if the maintenance terminal has no serial port.
Procedure
Step 1 Determine the installation positions.
Step 5 Use a network cable to connect the eth1 port of the key management server to
the management network port of the storage system through a switch.
Step 6 Insert one end of the power cable to the electric socket at the server back, and
insert the other end to the external AC power module.
Step 8 Put the baffle plate on the front panel, then insert and turn the key.
Step 9 Repeat Step 3 to Step 8 to install and power on the other key management
server.
Step 10 If the maintenance terminal has no serial port, use the USB-to-serial cable to
connect the USB port of the maintenance terminal to the serial port of the key
management server.
----End
After two key management servers with the same configurations are clustered,
the two servers provide the encryption service together. If one of them becomes
faulty or fails to provide the encryption service, the storage system automatically
connects to the other one.
For details about how to initialize key management servers and create a cluster,
refer to the user guide and consult technical support engineers of the server
vendor.
NOTICE
When configuring the key management server, select Enable hard delete, as
shown in Figure 5-4.
Procedure: Log in to the web management page of the key management server as
user admin, choose Admin Settings > System > Interfaces, click on the
right of the kmip line, and click Edit.
Context
The certificate generated on the storage system is not signed. It must be signed on
the key management server.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Certificates.
Step 3 On the Certificate Management page, choose KMC certificate, and click Export
Request File. On the displayed page, set the Certificate Key Algorithm to RSA
2048 or RSA 4096, and then click OK.
NOTE
You can also click KMC certificate. On the Certificate Details page that is displayed, click
Operation > Export Request File, set the Certificate Key Algorithm to RSA 2048 or RSA
4096, and then click OK.
----End
NOTICE
Precautions
To ensure that the key management server can identify the storage system
successfully, the local user name of the key management server must be set to
Storage, which is the same as the OU value in the signed certificate of the storage
system.
You can query the OU value as follows:
1. Double-click the certificate.
2. Click the Detail tab, and select User. You can view the OU value in the lower
pane.
Procedure
Step 1 Log in to the web management page of the key management server as user
admin.
Step 2 Choose Keys & Access Management > Users, and click Create New User.
Step 3 Enter Storage in the Username field and set the password.
NOTE
The name of the local user created on the key management server must be the same as
the OU value (Storage) in the certificate file signed on the storage system.
Step 4 Click Create. The new user is displayed on the Users page.
Step 5 Click user Storage to display the user information. Click on the right of a
group.
Figure 5-9 Searching for group Key Admins and Key Users
Step 7 Click Add on the right of groups Key Admins and Key Users.
----End
Precautions
If the key management server is connected to multiple storage devices, a client is
required for each storage device.
Procedure
Step 1 Log in to the web management page of the key management server as user
admin.
Step 4 Create a registration token. For details, see 5.4.2.3.2 Creating a Registration
Token.
----End
Prerequisites
The key management server must have been added to a cluster.
Procedure
Step 1 Log in to the web management page of the key management server as user
admin.
Step 2 Choose KMIP > Client Profiles, and click Add Profile.
Step 3 Enter a Profile Name, select OU for Username Location in Certificate, and click
on the right of Certificate Details. In the CSR field, input the certificate file of
the storage system exported in 5.4.2.1 Generating and Exporting a Certificate
on the Storage System.
Step 4 Click Save. The profile is displayed on the Client Profiles page.
----End
Prerequisites
● The key management server has been added to a cluster.
● A profile has been created.
Procedure
Step 1 Choose KMIP > Registration Token, and click New Registration Token.
Step 2 Click Begin, and create a registration token following the wizard.
1. On the Configure Token page, set the Name Prefix and Token lifetime. You
can click to view the rules. It is recommended that the Name Prefix be
kept the same as the profile name. You can use the default token lifetime or
set a value based on actual requirements. Click Next.
2. On the Select CA page, select the default CA and click Select Profile.
3. On the Select Profile page, select the created profile from the drop-down list,
and click Create Token.
4. On the Create Token page, click Copy to copy the certificate information, and
click Done.
NOTE
You can also copy the certificate information on the Registration Token page in Step
5.
----End
Prerequisites
● The key management server has been added to a cluster.
● A profile has been created.
● A registration token has been created.
Procedure
Step 1 Choose KMIP > Registered Clients, and click Add Client.
Step 2 Set the Name and fill in the Registration Token field with the certificate
information copied in Step 4. You can click to view the rules. It is
recommended that the client name be the same as the profile name. Click Save.
Step 4 Click Close. The new client is displayed on the Registered Clients page.
----End
Procedure
Step 1 Log in to the web management page of the key management server as user
admin.
Step 2 Choose Keys & Access Management > CA, and click on the right of the
subject in the Local Certificate Authorities area. Click Download to obtain the
file Certificate.pem.
Step 3 Choose KMIP > Registered Clients, and click on the right. Click Save
Certificate to obtain the file Cert.pem.
NOTE
If you have saved the file Cert.pem in Step 3, skip this step.
----End
Procedure
Step 1 Log in to DeviceManager.
You can also click KMC certificate. On the Certificate Details page that is displayed,
click Operation > Import Certificate.
2. Import the signed certificate and CA certificate. Table 5-1 describes the
parameters.
3. Click OK.
The Warning dialog box is displayed.
4. Carefully read the content in the dialog box, select I have read and
understand the consequences associated with performing this operation,
and click OK.
----End
Context
A storage system needs two key management servers.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Key Service. In the function pane on the right, click Modify.
Then select Enable the external key service.
Step 3 Specify the key management server parameters listed in Table 5-2.
NOTE
A storage system can connect to a maximum of two key management servers in a cluster.
The following example adds one key management server to the storage system.
Step 4 Import the signed certificate and CA certificate. Table 5-3 describes the
parameters.
----End
Follow-up Procedure
After the storage system has connected to the key management servers, wait for 2
to 3 minutes before performing follow-up procedures.
Prerequisites
SEDs have been configured on the storage system. The AutoLock status of the
SEDs is OFF.
To query the AutoLock status of the SEDs, you can log in to the CLI of the storage
system and run the show disk general command.
admin:/>show disk general
ID Health Status Running Status Type Capacity Role Disk Domain ID Speed(RPM) Health
Procedure
Step 1 Log in to DeviceManager and create a storage pool.
The Create Storage Pool page is displayed.
NOTE
Use either of the following methods to go to the Create Storage Pool page:
● When you log in to the storage system for the first time, you can create a storage pool
in Custom mode in the initial configuration wizard. For details, see "Initially Configuring
a Storage Device" in the initialization guide specific to your product model.
● On the menu bar, choose System > Storage Pools and then click Create.
Step 2 Create a self-encrypting storage pool and automatically generate encryption keys
on the storage system.
1. Select Advanced and enable Data Encryption. Disk encryption is enabled for
all SEDs in the storage pool.
NOTE
After a storage pool has been created, data encryption cannot be enabled or disabled
for the storage pool.
2. Set other parameters for the storage pool.
For the parameter description, see section "Creating a Storage Pool" in the
Basic Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the specific product model.
3. Click OK.
Confirm your operation as prompted.
----End
Follow-up Procedure
After creating the self-encrypting storage pool, you can create LUNs or file
systems to allocate the storage space to application servers. For details, see Basic
Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the corresponding product model.
NOTE
6
Configuring and Managing the Key
Management Server (Utimaco, Applicable to
6.1.2 and Later)
This chapter describes how to install and configure the Utimaco key management
server.
6.1 About Utimaco Key Management Servers
6.2 Configuration Process
6.3 Hardware Deployment
6.4 Configuring the Key Management Server and Cluster
6.5 Connecting the Key Management Server to the Storage System
6.6 Creating a Self-encrypting Storage Pool
Typical Networking
A storage system connects to two Utimaco key management servers that are
clustered in hot backup mode. Figure 6-1 shows the typical networking.
To ensure that the key management servers can work properly, verify that the
network communication between the following components is normal:
● Storage system's management network port -> key management servers'
LAN1
Start
Install key management
servers.
End
Prerequisites
● The installation positions of the two key management servers have been
determined.
● Cables and tools required for hardware installation have been prepared,
including:
– Serial cable (included in the product package)
– Power cable (included in the product package)
– Network cable (not included in the product package)
– Phillips screwdriver (not included in the product package)
Prepare the USB-to-serial cable if the maintenance terminal has no serial port.
Procedure
Step 1 Determine the installation positions.
Step 5 Use a network cable to connect the LAN1 port of the key management server to
the management network port of the storage system through a switch.
Step 6 Insert one end of the power cable to the electric socket at the server back, and
insert the other end to the external AC power module.
Step 8 Put the baffle plate on the front panel, then insert and turn the key.
Step 9 Repeat Step 3 to Step 8 to install and power on the other key management
server.
Step 10 If the maintenance terminal has no serial port, use the USB-to-serial cable to
connect the USB port of the maintenance terminal to the serial port of the key
management server.
----End
Context
The certificate generated on the storage system is not signed. It must be signed on
the key management server.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Certificates.
Step 3 On the Certificate Management page, choose KMC certificate, and click Export
Request File. On the displayed page, set the Certificate Key Algorithm to RSA
2048 or RSA 4096, and then click OK.
NOTE
You can also click KMC certificate. On the Certificate Details page that is displayed, click
Operation > Export Request File, set the Certificate Key Algorithm to RSA 2048 or RSA
4096, and then click OK.
----End
----End
Step 3 Select the default CA certificate, and click Download to export the CA certificate
of the key management server.
----End
Precautions
To ensure that the key management server can identify the storage system
successfully, the local user name of the key management server must be set to
Storage, which is the same as the OU value in the signed certificate of the storage
system.
Context
Create at least one local user.
Procedure
Step 1 Log in as the admin user to the key management server's web interface.
Step 2 Choose Security > Users & Groups > Local Users & Groups > Local Users.
The User & Group Configuration page is displayed, as shown in Figure 6-8.
NOTICE
Enter the signed.crt certificate content downloaded in Step 5 in the KMIP Client
Certificate area.
NOTE
For Map non-existent Object Group to x-Object Group, KMIP User Group, and KMIP
Object Group, use the default values.
----End
Procedure
Step 1 Log in to DeviceManager.
You can also click KMC certificate. On the Certificate Details page that is displayed,
click Operation > Import Certificate.
2. Import the signed certificate and CA certificate. Table 6-2 describes the
parameters.
3. Click OK.
The Warning dialog box is displayed.
4. Carefully read the content in the dialog box, select I have read and
understand the consequences associated with performing this operation,
and click OK.
The Success dialog box is displayed.
5. Click OK.
----End
Context
A storage system needs two key management servers.
Procedure
Step 1 Log in to DeviceManager.
Step 2 Choose Settings > Key Service. In the function pane on the right, click Modify.
Then select Enable the external key service.
Step 3 Specify the key management server parameters listed in Table 6-3.
NOTE
A storage system can connect to a maximum of two key management servers in a cluster.
The following example adds one key management server to the storage system.
Step 4 Import the signed certificate and CA certificate. Table 6-4 describes the
parameters.
Follow-up Procedure
After the storage system has connected to the key management servers, wait for 2
to 3 minutes before performing follow-up procedures.
Prerequisites
SEDs have been configured on the storage system. The AutoLock status of the
SEDs is OFF.
To query the AutoLock status of the SEDs, you can log in to the CLI of the storage
system and run the show disk general command.
admin:/>show disk general
ID Health Status Running Status Type Capacity Role Disk Domain ID Speed(RPM) Health
Mark Bar Code Item AutoLock State Key Expiration Time
------ ------------- -------------- -------- --------- --------- -------------- ---------- -----------
-------------------- -------- -------------- -------------------
DAE000.0 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000131 02350LGX OFF --
DAE000.1 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000124 02350LGX OFF --
DAE000.2 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FB000238 02350LGX OFF --
DAE000.3 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000228 02350LGX OFF --
DAE000.4 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10FA000227 02350LGX OFF --
DAE000.5 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10FA000187 02350LGX OFF --
DAE100.0 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000159 02350LGX OFF --
DAE100.1 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000161 02350LGX OFF --
DAE100.2 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10G3000505 02350LGX OFF --
DAE100.3 Normal Online SSD-SED 366.965GB Free Disk -- -- --
2102350LGX10FA000182 02350LGX OFF --
DAE100.4 Normal Online SSD-SED 371.965GB Free Disk -- -- --
2102350LGX10G3000511 02350LGX OFF --
Procedure
Step 1 Log in to DeviceManager and create a storage pool.
The Create Storage Pool page is displayed.
NOTE
Use either of the following methods to go to the Create Storage Pool page:
● When you log in to the storage system for the first time, you can create a storage pool
in Custom mode in the initial configuration wizard. For details, see "Initially Configuring
a Storage Device" in the initialization guide specific to your product model.
● On the menu bar, choose System > Storage Pools and then click Create.
Step 2 Create a self-encrypting storage pool and automatically generate encryption keys
on the storage system.
1. Select Advanced and enable Data Encryption. Disk encryption is enabled for
all SEDs in the storage pool.
NOTE
After a storage pool has been created, data encryption cannot be enabled or disabled
for the storage pool.
2. Set other parameters for the storage pool.
For the parameter description, see section "Creating a Storage Pool" in the
Basic Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the specific product model.
3. Click OK.
Confirm your operation as prompted.
----End
Follow-up Procedure
After creating the self-encrypting storage pool, you can create LUNs or file
systems to allocate the storage space to application servers. For details, see Basic
Storage Service Configuration Guide for Block or Basic Storage Service
Configuration Guide for File of the corresponding product model.
NOTE
B Glossary
A
AC power module The module that transfers the external AC power
supply into the power supply for internal use.
Application server A service processing node (a computer device) on the
network. Application programs of data services run
on the application server.
Asynchronous remote A kind of remote replication. When the data at the
replication primary site is updated, the data does not need to be
updated synchronously at the mirroring site to finish
the update. In this way, performance is not reduced
due to data mirroring.
Air baffle It optimizes the ventilation channels and improves
the heat dissipation capability of the system.
Audit log guarantee A mode for recording audit logs. This mode
mode preferentially ensures that the audit log function is
normal and no audit log is missing.
Audit log non- A mode for recording audit logs. In this mode,
guarantee mode services are running properly. Audit logs may be
missing.
B
Backup A collection of data stored on (usually removable)
non-volatile storage media for purposes of recovery
in case the original copy of data is lost or becomes
inaccessible; also called a backup copy. To be useful
for recovery, a backup must be made by copying the
source data image when it is in a consistent state.
The act of creating a backup.
C
Cache hit ratio The ratio of the number of cache hits to the number
of all I/Os during a read task, usually expressed as a
percentage.
Captive screw Specially designed to lock into place on a parent
board or motherboard, allowing for easy installation
and removal of attached pieces without release of
the screw.
Challenge Handshake A password-based authentication protocol that uses a
Authentication challenge to verify that a user has access rights to a
Protocol system. A hash of the supplied password with the
challenge is sent for comparison so the cleartext
password is never sent over the connection.
Compliance mode A protection mode of WORM. In compliance mode,
files within their protection period cannot be changed
or deleted by either the file user or by the system
administrator. Files with expired protection periods
can be deleted but not changed by the file user or
the system administrator.
Controller The control logic in a disk or tape that performs
command decoding and execution, host data transfer,
serialization and deserialization of data, error
detection and correction, and overall management of
device operations. The control logic in a storage
subsystem that performs command transformation
and routing, aggregation (RAID, mirroring, striping, or
other), high-level error recovery, and performance
optimization for multiple storage devices.
Controller enclosure An enclosure that accommodates controllers and
provides storage services. It is the core component of
a storage system and generally consists of
components, such as controllers, power supplies, and
fans.
Copying A pair state. The state indicates that the source LUN
data is being synchronized to the target LUN.
Container root Space used to store the metadata for running
directory container images and container instances.
Container image An image is a special file system, which provides the
programs, libraries, resources, and configuration files
required for running containers. It also contains
configuration parameters, for example, for
anonymous disks, environment variables, and users.
The image does not contain dynamic data, and its
content will not be modified after construction.
Containerized An image can start multiple containers, and an
application application can contain one or a group of containers.
D
Data compression The process of encoding data to reduce its size. Lossy
compression (i.e., compression using a technique in
which a portion of the original information is lost) is
acceptable for some forms of data (e.g., digital
images) in some applications, but for most IT
applications, lossless compression (i.e., compression
using a technique that preserves the entire content of
the original data, and from which the original data
can be reconstructed exactly) is required.
Data flow A process that involves processing data extracted
from the source system. These processes include:
filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting
invalid data so that the processed data meets the
requirements of the destination system for the input
data.
Data migration A movement of data or information between
information systems, formats, or media. Migration is
performed for reasons such as possible decay of
storage media, obsolete hardware or software
(including obsolete data formats), changing
performance requirements, the need for cost
efficiencies etc.
Data source A system, database (database user; database
instance), or file that can make BOs persistent.
Deduplication The replacement of multiple copies of data — at
variable levels of granularity — with references to a
shared copy in order to save storage space and/or
bandwidth.
Dirty data Data that is stored temporarily on the cache and has
not been written onto disks.
E
eDevLUN Logical storage array space created by a third-party
storage array.
Expansion module A component used for expansion.
Expansion Connects a storage system to more disk enclosures
through connection cables, expanding the capacity of
the storage system.
F
Field replaceable unit A unit or component of a system that is designed to
be replaced in the field, i.e., without returning the
system to a factory or repair depot. Field replaceable
units may either be customer-replaceable or their
replacement may require trained service personnel.
Firmware Low-level software for booting and operating an
intelligent device. Firmware generally resides in read-
only memory (ROM) on the device.
Flash Translation Layer Flash Translation Layer (FTL) organizes and manages
host data, enables host data to be allocated to NAND
flash chips of SSDs in an orderly manner, maintains
the mapping relationship between logical block
addresses (LBAs) and physical block addresses
(PBAs), and implements garbage collection, wear
leveling, and bad block management.
Front-end port The port that connects the controller enclosure to the
service side and transfers service data. There are
three types of front-end ports: Fibre Channel and
iSCSI.
Front-end interconnect On a storage device, all controllers share the front-
I/O module (FIM) end interface modules.
G
Garbage collection The process of reclaiming resources that are no
longer in use. Garbage collection has uses in many
aspects of computing and storage. For example, in
flash storage, background garbage collection can
improve write performance by reducing the need to
perform whole block erasures prior to a write.
Gateway A device that receives data via one protocol and
transmits it via another.
Global garbage With a view to defragmentation of storage arrays
collection and garbage collection of disks, global garbage
collection reduces garbage of disks by enabling
storage arrays to inform disks of not implementing
invalid data relocation and of controlling space
release so that disks and controllers consume less
space, reducing costs and prolonging the useful life
of storage arrays.
H
Hard disk tray The tray that bears the hard disk.
Heartbeat Heartbeat supports node communication, fault
diagnosis, and event triggering. Heartbeats are
protocols that require no acknowledgement. They are
transmitted between two devices. The device can
judge the validity status of the peer device.
Hit ratio The ratio of directly accessed I/Os from the cache to
all I/Os.
Hot swap The substitution of a replacement unit (RU) in a
system for a defective unit, where the substitution
can be performed while the system is performing its
normal functioning normally. Hot swaps are physical
operations typically performed by humans.
HyperMetro A value-added service of storage systems.
HyperMetro means two datasets (on two storage
systems) can provide storage services as one dataset
to achieve load balancing among applications and
failover without service interruption.
HyperMetro domain A HyperMetro configuration object generally; made
up of two storage arrays and one quorum server.
HyperMetro services can be created on a HyperMetro
domain.
HyperMetro vStore A HyperMetro vStore pair consists of two vStores,
pair that is, two tenants. After a HyperMetro relationship
is set up for a pair of vStores, the datasets in the two
vStores work in redundancy mode and provide
storage services in one dataset view, achieving hitless
service failover.
I
In-band management The management control information of the network
and the carrier service information of the user
network are transferred through the same logical
channel. In-band management enables users to
manage storage arrays through commands.
Management commands are sent through service
channels, such as I/O write and read channels. The
advantages of in-band management include high
speed, stable transfer, and no additional
management network ports required.
Initiator The system component that originates an I/O
command over an I/O interconnect. The endpoint
that originates a SCSI I/O command sequence. I/O
adapters, network interface cards, and intelligent I/O
interconnect control ASICs are typical initiators.
I/O Shorthand for input/output. I/O is the process of
moving data between a computer system's main
memory and an external device or interface such as a
storage device, display, printer, or network connected
to other computer systems. This encompasses
reading, or moving data into a computer system's
memory, and writing, or moving data from a
computer system's memory to another location.
Interface module A replaceable field module that accommodates the
service or management ports.
L
Load balance A method of adjusting the system, application
components, and data to averagely distribute the
applied I/Os or computing requests to physical
resources of the system.
Logical unit The addressable entity within a SCSI target that
executes I/O commands.
Logical unit number The SCSI identifier of a logical unit within a target.
Industry shorthand, when phrased as "LUN", for the
logical unit indicated by the logical unit number.
LUN formatting The process of writing 0 bits in the data area of the
logical drive and generating related parity bits so that
the logical drive can be in the ready state.
LUN mapping A storage system maps LUNs to application servers
so that application servers can access storage
resources.
LUN migration A method for the LUN data to migrate between
different physical storage spaces while ensuring data
integrity and uninterrupted operation of host
services.
LUN snapshot A type of snapshot created for a LUN. This snapshot
is both readable and writable and is mainly used to
provide a snapshot LUN from point-in-time LUN
data.
Lever A lever resides on the structural part of a module. It
is used to insert or remove a module into or from a
chassis, saving efforts.
Local image repository A private repository used to store the container
images and Helm charts imported by users. It is
different from the standard image repository. The
imported images and Helm charts must meet the
compatibility requirements of the system.
M
Maintenance terminal A computer connected through a serial port or
management network port. It maintains the storage
system.
Management interface The module that integrates one or more
module management network ports.
Management network An entity that provides means to transmit and
process network management information.
N
NVM Express A host controller interface with a register interface
and command set designed for PCI Express-based
SSDs.
NVMe SSD A solid state disk (SSD) with a non-volatile memory
express (NVMe) interface. Compared with other
SSDs, such SSDs can deliver higher performance and
shorter latency.
O
Out-of-band A management mode used during out-of-band
management networking. The management and control
information of the network and the bearer service
information of the user network are transmitted
through different logical channels.
P
Power failure When an external power failure occurs, the AC PEM
protection depends on the battery for power supply. This
ensures the integrity of the dirty data in the cache.
Pre-copy When the system monitors a failing member disk in a
RAID group, the system copies the data from the disk
to a hot spare disk in advance.
Palm-sized NVMe SSD A palm-sized NVMe SSD is a type of NVMe SSD of
which the dimensions (H x W x D) are 160 mm x 79.8
mm x 9.5 mm (neither 3.5-inch nor 2.5-inch).
Q
Quorum server A server that can provide arbitration services for
clusters or HyperMetro to prevent the resource access
conflicts of multiple application servers.
R
RAID level The application of different redundancy types to a
logical drive. A RAID level improves the fault
tolerance or performance of the logical drive but
reduces the available capacity of the logical drive.
You must specify a RAID level for each logical drive.
Reconstruction The regeneration and writing onto one or more
replacement disks of all of the user data and check
data from a failed disk in a mirrored or RAID array. In
most arrays, a rebuild can occur while applications
are accessing data on the array's virtual disks.
Redundancy The inclusion of extra components of a given type in
a system (beyond those required by the system to
carry out its function) for the purpose of enabling
continued operation in the event of a component
failure.
Remote replication A core technology for disaster recovery and a
foundation that implements remote data
synchronization and disaster recovery. This
technology remotely maintains a set of data mirrors
through the remote data connection function of the
storage devices that are separated in different places.
Even when a disaster occurs, the data backup on the
remote storage device is not affected. Remote
replication can be divided into synchronous remote
replication and asynchronous remote replication.
Reverse The process of restoring data from the redundancy
synchronization machine (RM) when the services of the production
machine (PM) are recovering.
Route The path that network traffic takes from its source to
its destination. On a TCP/IP network, each IP packet
is routed independently. Routes can change
dynamically.
S
Script A parameterized list of primitive I/O interconnect
operations intended to be executed in sequence.
Often used with respect to ports, most of which are
able to execute scripts of I/O commands
autonomously (without policy processor assistance).
A sequence of instructions intended to be parsed and
carried out by a command line interpreter or other
scripting language. Perl, VBScript, JavaScript and Tcl
are all scripting languages.
Serial port An input/output location (channel) that sends and
receives data (one bit at a time) to and from the CPU
of a computer or a communications device. Serial
ports are used for serial data communication and as
interfaces for some peripheral devices, such as mouse
devices and printers.
Service data The user and/or network information required for the
normal functioning of services.
Service network port The network port that is used to store services.
Simple network An IETF protocol for monitoring and managing
management protocol systems and devices in a network. The data being
monitored and managed is defined by an MIB. The
functions supported by the protocol are the request
and retrieval of data, the setting or writing of data,
and traps that signal the occurrence of events.
Single point of failure One component or path in a system, the failure of
which would make the system inoperable.
Slot A position defined by an upper guide rail and the
corresponding lower guide rail in a frame. A slot
houses a board.
Small computer system A collection of ANSI standards and proposed
interface standards that define I/O interconnects primarily
intended for connecting storage subsystems or
devices to hosts through host bus adapters. Originally
intended primarily for use with small (desktop and
desk-side workstation) computers, SCSI has been
extended to serve most computing needs, and is
arguably the most widely implemented I/O
interconnect in use today.
Snapshot A point in time copy of a defined collection of data.
Clones and snapshots are full copies. Depending on
the system, snapshots may be of files, LUNs, file
systems, or any other type of container supported by
the system.
Snapshot copy A copy of a snapshot LUN.
T
Target The endpoint that receives a SCSI I/O command
sequence.
Target LUN The LUN on which target data resides.
Thin LUN A logic disk that can be accessed by hosts. It
dynamically allocates storage resources from the thin
pool according to the actual capacity requirements of
users.
U
User interface The space where users interact with a machine.
U-shaped bracket It is an optional structural part like letter "U". It is
located between the mounting ear of a chassis and
the mounting bar of a cabinet or bay and is used to
adjust the locations of the chassis and mounting bar
of the cabinet or bay.
W
Wear leveling A set of algorithms utilized by a flash controller to
distribute writes and erases across the cells in a flash
device. Cells in flash devices have a limited ability to
survive write cycles. The purpose of wear leveling is
to delay cell wear out and prolong the useful life of
the overall flash device.
Write amplification Increase in the number of write operations by the
device beyond the number of write operations
requested by hosts.
Write amplification The ratio of the number of write operations on the
factor device to the number of write operations requested
by the host.
Z
Zone A collection of Fibre Channel N_Ports and/or
NL_Ports (i.e., device ports) that are permitted to
communicate with each other via the fabric. Any two
N_Ports and/or NL_Ports that are not members of at
least one common zone are not permitted to
communicate via the fabric. Zone membership may
be specified by: 1) port location on a switch, (i.e.,
Domain_ID and port number); or, 2) the device's
N_Port_Name; or, 3) the device's address identifier;
or, 4) the device's Node_Name. Well-known
addresses are implicitly included in every zone.
C
CPU Central Processing Unit
I
I/O Input/Output
IOPS Input/Output Operations Per Second
L
LUN Logical Unit Number
R
RAID Redundant Array of Independent Disks
RTO Recovery Time Objective
S
SAS Serial Attached SCSI