TECS-CloveStorageV07.20.20.07UME One-Click Deployment and Configuration CloveStorage Guide - R1.4

TECS-CloveStorageV07.20.20.07UME Daisyseed3.
0 One-click Deployment and Configurationand ConfigurationGuide Secret▲
TECS-CloveStorageV07.20.20.07UME Daisyseed3.0
One-click Deployment and Configuration
CloveStorage Cluster Guide
<All rights reserved. No spreading without permission of ZTE.> Page1

TECS-CloveStorageV07.20.20.07UME Daisyseed3.0 One-click Deployment and Configurationand ConfigurationGuide Secret▲
Legal Statement
This document is owned by ZTE Corporation. Without the written permission of

the copyright owner, no unit or individual shall extract, copy, or translate the
documents in any way.
All rights reserved.
And are registered trademarks of ZTE Corporation. The name and
logo of a ZTE product are the proprietary logo or registered trademark of ZTE. The
names of other products or companies mentioned in this Manual may be trademarks
or trade names of their respective owners. Without the prior written consent of ZTE or
the owners of third-party trademarks or trade names, this manual does not grant the
reader any permission or right to use any marks listed in this manual.
This product complies with the design requirements for environmental
protection and personal safety. The storage, use, and disposal of this product shall
comply with the requirements of the product manual, relevant contracts or laws and
regulations of relevant countries.
Due to the continuous update and improvement of products and technologies,
the contents of this document may not be completely consistent with the actual
products. To query product updates, contact the local representative office.
For the latest information, please visit the website http://support.zte.com.cn.
Document Information
 Document No.: SJ-20220622131424-001
 Document version: 20220825-R1.3

Contents
1. OVERVIEW..............................................................................................................................................5
2. DEPLOYMENT PREPARATIONS................................................................................................................5
2.1 PREPARE THE VERSION FILE..............................................................................................................5

2.2 ENVIRONMENT NETWORKING PLANNING.....................................................................................................6
2.3 DEPLOYMENT PRECAUTIONS...................................................................................................................8
3. DEPLOYMENT FLOW................................................................................................................................9
4. DEPLOYMENT TABLE CONFIGURATION................................................................................................10
4.1 DAISYSEED TABLE CONFIGURATION......................................................................................................10

4.2 TECS SILENT INSTALLATION TABLE CONFIGURATION............................................................................12
4.3 CLOVESTORAGE SILENT INSTALLATION TABLE CONFIGURATION................................................................12
4.4 CLOVESTORAGE CONFIGURATION TABLE CONFIGURATION..........................................................................13
4.5 FOUR TABLES FOR ONE-CLICK DEPLOYMENT OF ARE ASSOCIATED..........................................................13
5. DAISYSEED ONE-CLICK DEPLOYMENT.................................................................................15
5.1 DAIYSEED SOFTWARE PREPARATION......................................................................................................15

5.2 START ONE-CLICK DEPLOYMENT.........................................................................................................15
5.3 ONE-CLICK DEPLOYMENT COMPLETED....................................................................................................18
5.4 CLOVESTORAGE ERROR CODE...............................................................................................................18
6. UPDATING THE RAID CARD DRIVER..................................................................................................19
6.1 CHECK THE DRIVER VERSION BEFORE UPGRADE.....................................................................................19

6.2 UPGRADE DRIVER VERSION.................................................................................................................19
6.3 CHECK THE VERSION AFTER UPGRADE..................................................................................................19
6.4 RESTART NODE...............................................................................................................................20
APPENDIX 1 5300 G4X RAID CONFIGURATION.........................................................................21
APPENDIX 2 5300 G4X BIOS CONFIGURATION..........................................................................31
APPENDIX 3 CLOVESTORAGE ERROR CODE DESCRIPTIONS............................................33

Version Update Description
Docu
ment
Version No. Issued on Update Description
Versi
on
V07.20.20.07UME R1.0 2022-4 -21 New
Changed some Chinese pictures to English pictures.
V07.20.20.07UME R1.1 2022-5 -23
Adjusted the English format of some titles.
Delete the description of the Raid.conf file in the UME template
Modified the content of Section 2.3: Combined Paragraph 1 and
2, optimized the description of Section 4.
V07.20.20.07UME R1.2 2022-6-22 Modified the content of Section 4.1: Description of Optimized
raid configuration method
Added the content in Chapter 5.3: The default validity period of
the NM password can be changed to 10 years.
Added the content in Chapter 4.2: Enter the operating system
V07.20.20.07UME R1.3 2022-8-26
version in the host template.
V07.20.20.07UME R1.4 2022-9-15 Modifying the OS Version and daisy Version in the 2.1 Table

1. Overview
This document is intended to instruct the user to deploy the CloveStorage storage cluster in
daisyseed3.0 one-click mode.
2. Deployment Preparations
2.1 Prepare the version file.

Table 2.1 Version File Description
Version Version File Name Description
Storage version
TECS TECS-CloveStorageV07.20.20.07UME_VERSION.zip
Used for mirroring packages in hyper-
CloveStorage TECS-CloveStorageV07.20.20.07UME.img
convergence scenarios.
OS Mimosa-x86_64-7.4-030886-FI.iso Storage resource operating system
daisy-2016.3.15-11.4.52135.el7.x86_64.rpm Daisy software package
daisyseed_win_V07.21.20.07_523.7z Daisyseed3.0 package
Mimosa-x86_64-7.4-030865-Manager-provider-
Daisy 19.40.10.28-0-dockerimage-installer-220512113000-
daisy52135-ZXTECS_V03.17.15.110438445.img TECS mirror package and third-party
ZXTECS_3rdparty_V03.17.15.110438445.bin packages
provider-3rdparty-19.40.10.28-0-dockerimage-
installer-220512113000.bin
inspector_v07.20.10.13_220316.bin (python2)
inspector_v07.20.10.13py3_220318.bin (python3) O&M inspector tools and corresponding
Tools cephcheck-2022-05-18.zip security reinforcement packages and
cephrepair-2022-05-18.zip preventive maintenance packages
cephsec-2022-05-18.zip
smartpqi-2.1.8-040.1_1.el7.x86_64.rpm Controller drive update package
update_data_cache_serial.zip This package is a tool for updating

CloveStorage NM disk sequence number

Version Version File Name Description
after the server replaces the raid card.
clear_storage_script.zip Storing the Clearing Script
Client package used by the PaaS container

alpine TECS-CloveStorageV07.20.20.07UME-alpine.tar.gz
platform
UME_Ceph_Install_Template.xlsx
UME_Templ UME_daisyseed.xlsx UME one-click deployment configuration
ate UME_TECS_Install_Template.xlsx file
UME_ZSTOR_ZMS_TEMPLATE.xls
NDS_daisyseed.xlsx
NDS_Templa NDS_Ceph_Install_Template.xlsx One-click NDS deployment configuration
te NDS_TECS_Install_Template.xlsx file
NDS_ZSTOR_ZMS_TEMPLATE.xls
2.2 Environment networking planning
Figure 2.1 Networking Diagram

TECSClient: It is used for interconnection between PaaS and CloveStorage, clock
synchronization and volume management. It is the maintenance network used when HA is created
as CloveStorage in the CloveStorage cluster, through which the CloveStorage NM can be
accessed.
MANAGEMENT: The TECS synchronizes the clock with the CloveStorage through it. The
MANAGEMENT plane between the PaaS and the CloveStorage is disconnected.
STORAGE_DATA: Storage service network. It is responsible for the communication
between the client and the CloveStorage cluster, between MONs, and between MONs and OSDs.
The 10 G network is recommended.
STORAGE_CLUSTER: The cluster internal network is responsible for communication
between OSDs. The 10 G network is recommended.
The host installed with the TECS version can serve as the resource node of the CloveStorage,
and the other two independent servers can serve as the management and resource integration

nodes of the CloveStorage. The host does not provide the computing service. The TECS silent
installation template does not contain the host.
Figure 2.2 Final Delivery Deployment Diagram
When deploying the CloveStorage with the daisyseed one click, the daisyseed needs to
configure the hardware of each node through the BMC network interface, install the OS of the
first node through the PXE network and start the control node VM. The network planes are
planned as follows:

Figure 2.3 Daisyseed One-Click Deployment CloveStorage Network Planning

Note 1: In the above figure, PXE and TECSClient are deployed on different network
interfaces. In actual networking, the same physical network interface can be deployed. In this case,
the vlan of the two planes must be different (this is not a daisyseed requirement, but a basic
networking rule).
Note 2: If PXE and TECSClient are deployed on different network interfaces, they can be
configured with the same vlan id. In this case, it is not necessary to configure layer-3 route, but the
network can be connected.
Network principles:
PC <---> PXE: To use the layer-2 switching interoperability with the same vlan;
PC <---> BMC: If the BMC network vlan id is different from the PC, two vlan
PC <---> TECSClient: Same as BMC network
L3 switching configuration method: Configure an L3 route on the switch. Specify the route
table on the switch to forward the packets of different vlan from the IP layer. In addition, IP route
should be configured on the Windows device.
2.3 Deployment precautions

1. The management plane IP cannot be planned as the 192.168 network segment, because
when the CloveStorage cluster selects the internal clock source, it may select the IP of the virtual
network bridge virbr0, and the HA configuration may fail.
2. As long as the number of hard disks in the storage pool, the number of volumes, iSCSI
gateways, and the number of hosts in the mapping group exist, they cannot be modified through
templates. They need to be modified manually.
3. The configuration file of Raid needs to be generated with the support of hardware tools.
The target objects include not only R5300G4X but also other ZTE servers. The appendix takes
R5300G4X as an example.

3. Deployment Flow
The entire deployment is completed by the unified entrance of daisyseed. The user only needs
to plan the network and prepare the version package for the environment to be deployed before the
deployment, fill in the deployment configuration form as required and then import it into
daisyseed. All the subsequent operations are completed by daisyseed. The overall daisyseed
deployment flow is shown in the following figure:
The daisyseed completes the whole CloveStorage independent deployment process, from the
installation of the first node OS to the configuration of the CloveStorage.

4. Deployment Table Configuration
This chapter describes the precautions for configuring the four Excel tables required for daisyseed
one-click deployment.
4.1 Daisyseed table configuration
For the UME project, please unzip it.In the/UME_Template.zip file, fill in the following
configuration tables according to the UME_daisyseed.xlsx template requirements.
1) PXE Table Configuration
Item Value Comment
PXE Service Listen Address 88.88.1.8 IP address of the PXE server
Subnet Mask 255.255.255.0 PXE Server Subnet Mask
Start IP of the PXE server
Address Pool Start Address 88.88.1.9
address pool
End IP of the PXE Server
Address Pool End Address 88.88.1.20
Address Pool
2) Configure the Hardware table.
A.Enter the server BMC address, server type, and BMC user password (note that SSH user
password is also required for the 5300 G4/DELL-R740xd server).
B. Raid Configuration method of the ZTE Server refer to Appendix 1 5300 G4X RAID
configuration (Note that the name of the generated *.conf file cannot be modified),Other servers
need to be configured with RAID manually. In addition, BIOS configuration method of
R5300G4X server refer to Appendix 2 5300 G4X BIOS configuration.
The following uses the configuration of three RAID methods as an example(The following
*.conf needs to be changed to the actual file name):
The first RAID configuration: Copy UME_daisyseed.xlsx as UME_daisyseed-01.xlsx, fill in
the first RAID mode in the *.conf configuration file, and fill in the *.conf in the RAID File
column of the server that needs to perform the first RAID in the Hardware table. Daisyseed should
run with UME_daisyseed-01.xlsx first.
Second RAID configuration: Copy UME_daisyseed-01.xlsx into UME_daisyseed-02.xlsx,
and fill in the second RAID mode in the *.conf configuration file. Fill in *.conf in the RAID File
column of the server that needs to perform the second RAID in the Hardware table. Then, run
daisyseed again with UME_daisyseed-02.xlsx.
Third RAID configuration: Finally, modify the configuration file *.conf to the third RAID.
Fill in *.conf in the RAID File column of the server where the third RAID needs to be performed

in the Hardware table of UME_daisyseed.xlsx. Then, use UME_daisyseed.xlsx to run the formal
deployment flow.
C. SNMP Community needs to be configured for OS and VM installation, It is usually set to
zte_public (depending on the server configuration, if you are not sure, please log in to the BMC
and check it).
3) Host and VM Configuration table configuration
Deploy Target: OS+vm indicates installing and deploying the Tecs control node, and
installing the operating system and starting the control node VMs. Os indicates installing only the
operating system, while daisyseed only needs to install the first node OS+VM. The operating
systems of other nodes do not need to be installed with daisyseed. They will be installed with
daisy in the future. However, the first three items of information shall be provided to daisy for
discovering the host and modifying the host name.
Installation disk: Enter KVM to check which drive is the installation disk identified by the
system.
VM Name: Name of the control node
VM RAM: Deploy the memory size of the control node
VM vCPU Number: Number of cores used to deploy the control node
Node Type: Add the table. For the control node, fill in controller_node. For other nodes, leave
it blank.
4) Network Configuration table configuration

Deploy the TECS control node (that is, the node with Deploy Target being os+vm in the
above table). Fill in the MANAGEMENT and TECSClient plane information.
Note: IPv4/IPv6 must be correct. The IP address to be deployed is IPV4, and the IPV4 type
needs to be selected. The IP to be deployed is IPV6, and the IPV6 type needs to be selected.
5) Fill in the Deploy File table.

Please fill in the correct path of each version in the following table: .iso file of the operating
system, .img file of the control node VM, and information of the operating system and version file
of CloveStorage. These files should be placed in the same directory (e.g., F:\ceph)). Daisy third-
party file: Provider-3rdparty-xxx.bin and ZXTECS_3rdparty_xxx.bin must be placed under the
same directory as the VM_IMG file.
4.2 TECS silent installation table configuration
Unzip the file.In the/UME_Template.zip file, fill in the following configuration

tables according to the UME_TECS_Install_Template.xlsx template
requirements.
1) Cluster Attribute

TECS: That is, TECS in Table 2.1. Other configurations remain unchanged by default.
2) Cluster Network Planning
Currently, only the management plane (MANAGEMENT), PUBLICAPI plane and
TECSClient plane need to be deployed for the silent installation of the tecs.
3) Host Template
The controller node template is provided for the host instantiation table. You can select the
correct node type, network interface name, mapped network plane name, OS version, and system
disk as required.
Note: The OS version in the above table must be filled in. Otherwise, the CloveStorage OS
version of UME Web will be null.
4) Host Instantiation Table
Fill in only the TECS control node VM (do not fill in the host information). The IP addresses
of the Management and TECSClient planes are consistent with VM IP in the Network
Configuration table of UME_daisyseed.xlsx.
4.3 CloveStorage silent installation table
configuration
Unzip the file.In the/UME_Template.zip file, fill in the following configuration

tables according to the UME_Ceph_Install_Template.xlsx template
requirements.
1) Cluster Attribute
Clove: That is, the file name of the TECS CloveStorage version file bin in Table 2.1;
NTP server: Enter the IP address of the CloveStorage external clock source. If there is no
external clock source, leave this item blank.
2) Network Cluster Planning
The TECSClient network plane is added. The TECSClient plane of the CloveStorage and the
TECSClient plane of the TECS cluster are the same plane. The MANAGEMENT plane of the
CloveStorage and the TECS cluster are also the same plane.
Note: The Clove internal management plane IP and TECS-Client floating IP are unused IP
respectively.
3) Cluster Storage Planning
Fill in according to the project planning. It is recommended that clove be 20G-100G,
clove_lib be 50G-100 G and clove_log 10G-50 G.
4) Host Template

Fill in the host template as planned for the host instantiation table. Fill in the node type,
network interface name, network interface members, network plane, system disk, and
management disk information and size as required.
5) Host Instantiation
The host name of CloveStorage should be consistent with that in the Host and VM
Configuration table of UME_daisyseed.xlsx. When the CloveStorage resource node and the tecs
host are deployed together, the IP addresses of the MANAGEMENT and TECSClient planes in
the CloveStorage cluster should be consistent with those of the Host IP planes in the Network
Configuration table of UME_daisyseed.xlsx.
4.4 CloveStorage configuration table configuration
Unzip the file./UME_Template.zip file fill in the CloveStorage configuration

contents according to the requirements of the
UME_ZSTOR_ZMS_TEMPLATE.xlsx template. Each list in the template has a
detailed configuration description, which can be filled in according to the
instructions.
4.5 Four tables for one-click deployment of are
associated.
After the four tables of one-click deployment are filled in, you can refer to the relationships of the
four tables in the following figure to check whether the table configuration is correct.

5. Daisyseed one-click deployment

After making preparations for deployment, the user starts to deploy the CloveStorage cluster
in daisyseed one-click mode.
5.1 Daiyseed software preparation

After downloading daisyseed, unzip it on the local path of the PC.
5.2 Start one-click deployment.

1) One-click deployment
Place the four configuration files that have been filled in under the F:\ceph\daisyseed_xxx\
config_files directory (the specific path and file name are subject to the actual situation). Double
click "daisyseed.bat" to run the startup program, and the following interface appears:
Select Common Mode, and click Use, see the following figure.

Select Installation Deployment. The Installation Deployment page is displayed, see the
following figure.
Select the CloveStorage independent deployment scenario and configure it as follows:

Scenario: General
Service set: Ceph
Node Scale: Set it as required.
Template: Select a template according to the specific file path (subject to the actual file path
and the corresponding version package name).

Click OK. The one-click installation progress page is displayed, see the following figure.
Note:
1. If any failure occurs in the above steps, click Retry to continue the deployment. If manual
intervention is required, contact the R&D team for online support.
2. When running to ceph_silence_install, if the following error occurs, please click Retry to

continue the deployment:
3、If the deployment cannot continue, click Force Stop to cancel the deployment.
5.3 One-click deployment completed

After the daisyseed one-click deployment of CloveStorage is completed, the interface will display
as follows:
Use the TECSClient floating IP to log in to the CloveStorage Web (https://{IP}: 34100). The
default password is admin/admin. To enter the Web system, you need to modify the default
password first. After modifying the password, log in to the Web again. You can change the
validity period of the Web password to 10 years in the security policy of "admin" -> "System" ->
"Strategy" > "Strategyin" of the Web.
5.4 CloveStorage error code

If a failure occurs during deployment, refer to Attachment 3 for the returned error code.

6. Updating the raid card driver
6.1 Check the driver version before upgrade

Execute the modinfo smartpqi command and the version is 0.9.14-100.
(All versions earlier than 2.1.8-040 need to be upgraded.)
6.2 Upgrade driver version

Execute the rpm -Uvh smartpqi-2.1.8-040.1_1.el7.x86_64.rpm command.
6.3 Check the version after upgrade

Execute the modinfo smartpqi command and the version is 2.1.8-040.

6.4 Restart node
Execute reboot to restart the node where the RAID card is being upgraded.

Appendix 1 5300 G4X RAID configuration
1. Download the tool version: Download the latest version.
https://server.zte.com.cn/index.php?example=tools&method=list&aid=717&id=59
2. After the tool is downloaded, unzip it and install the tool package. The
installation tool has requirements for the browser used. The version of the
Google browser must be above 60.
Click Install, see the following figure.

3. After the installation is successful, click the application program
interface shown in the following figure. The username/password is admin;
Superuser9!.
4. Enter the username and password, see the following figure. Click Next.

5. Enter the home page after the next step.
6. Click < span > Deploy --- PXE </span > to perform batch configuration.

Click Open Tool.

7. Click Open Tool. The following page is displayed.
8. Click RAID, see the following figure.
9. Click Add to add a controller.
View controller information first: On the web:

Add the controller information as follows: 5300G4X, onboard controller. The
controller type is HBA_ 8238 forced restart. Straight-through/JBOD: Enable as
follows:

10. Click OK, see the following figure.

11. Click Add to add a logical disk. The following figure shows the
configuration information.

12. Click OK, see the following figure.

13. Click to save the configuration.

14. Click Export, and select the path to be exported. Click OK, see the
following figure.
15. Manually select a path for storing the exported configuration file: The
generated file is automatically stored in the Config folder. The generated raid
file cannot be modified.
Copy this file to the daisyseed directory: Daisyseed_win_V07.21.20.07_
516 \daisyseed_win_V07.21.20.07_ 516 \config_files


Appendix 2 5300 G4X BIOS configuration
Set the bios of the server. Similar to V9200, this server only supports
UEFI startup, and does not support traditional legacy startup.
There is a boot configuration item in bios. It is necessary to enable the
pxe mode and network pxe mode.
Open PXE Boot capalility: Click this option to select UEFI: IPV4


Appendix 3 CloveStorage Error Code
Descriptions
CloveStorage error code and corresponding error contents are as follows:

Error Code Error Content
1 The operation is not allowed due to insufficient permissions.
2 The operation object does not exist.
4 Interruption or timeout error
5 IO error
13 Access is rejected due to insufficient permissions.
16 The object or resource is being used.
17 The operation object already exists.
22 Invalid parameter
28 The available space of the device is insufficient.
30 The volume has the read-only attribute.
33 The parameter value exceeds the specified range.
38 This function is not supported.
39 The volume has associated snapshots.
61 No data is available.
108 Connection closed
110 Connection timeout
122 The hard disk quota is exceeded.
400 The request has a syntax error or does not support the request.
401 No permission - refer to the authorization plan
403 The server has rejected the request.
404 URL address error

405 The method is unavailable.
500 Server error
501 The server does not support this operation.
502 No response from other servers or agents
503 The server cannot process requests due to heavy load.
1000 Operation failed # Check the health status of the cluster
1002 The object {0}: {1} is not found.
2000 The cluster configuration failed to be obtained.
2001 There is no available data placement rule # Create a data placement rule first
2003 The storage pool name already exists # Please enter again
2004 Data placement rule does not exist # Refresh the page
2005 The number of PGP s cannot be greater than the number of PGs.
2006 The number of modified PGP instances must be greater than the current
number.
2007 The number of modified PGs must be greater than the current number.
2008 The number of PGs cannot exceed the maximum number allowed by the
system.
2009 The minimum number of copies cannot be greater than the current number of
copies.
3001 The cluster name already exists # Enter a new name.
3002 This cluster does not exist.
3003 This cluster already exists # Confirm it before performing the operation.
3004 Failed to obtain the cluster capacity.
3005 The memory space is insufficient.
10000 Request processing error
10001 Incorrect username or password # Please enter again
10003 Request timeout # Please try again later
10005 User permission is insufficient.
10006 Failed to obtain the server information.
10007 Server not managed # Confirm the operation before the operation.
10008 The heartbeat link between the management server and the storage cluster is

abnormal # Check whether the network connection is normal.
10009 The OSD service does not exist.
10010 Communication error # Contact ZTE technical support.
10011 Failed to obtain the hard disk information.
10012 The server is not unique in the cluster # Contact ZTE technical support.
10013 The server already exists.
10014 The cluster does not exist.
10015 The server is already in another cluster.
10016 The server already exists.
10017 This operation is not supported.
10018 Failed to configure the file storage cluster # Make sure that the NIC information
is valid and all IP addresses are in the same network segment
10019 Hard disk: {0} does not exist
10020 Storage pool: The current data backup specification of '{1}' is '{2}', and hard
disk: '{0}' does not allow to disable or isolate data.
10021 Hard disk: {0} has been isolated, so isolation is not allowed.
10022 Hard disk: {0} has not been added to the storage pool. Data migration is not
allowed.
10023 Hard disk: {0} is being isolated, and it is not allowed to perform relevant
operations.
10024 Hard disk: The {0} is being activated, and it is not allowed to perform related
operations.
10025 Hard disk: The {0} is being deleted. The related operations are not allowed to
be performed.
10026 Hard disk: {0} has data, and the deletion operation is not allowed.
10027 Hard disk: The {0} is being used, and the activation operation is not allowed.
10028 Hard disk: {0} is being isolated. Hard disk: {1} is not allowed to perform the
isolation operation.
10029 Hard disk: {0} is activated. Hard disk: {1} is not allowed to perform isolation.
10030 Storage pool: {0} is full. Hard disk: {1} is not allowed to disable or isolate {0}.

For storage pool: {0} is allowed to expand first, and then hard disk: {1} is
allowed to disable or isolate
10031 Storage pool: {0} is in recovery or downgrade status. Hard disk: {1} is not
allowed to perform isolation.
10032 Timeout occurs when the storage pool is in normal status # Check whether the
storage pool is in normal status.
10033 Too many failures, user locked # Please {0} and try again
10034 The username cannot be null.
10035 The password cannot be null.
10036 The account is locked by the system. # Contact the system administrator to
unlock the account.
10037 Hard disk: {0} is being enabled, and related operations are not allowed to be
performed.
10038 Hard disk: {0} is in the process of suspension. It is not allowed to perform
relevant operations.
10039 Host: {0} timed out while deleting from the topology structure. Please check
whether this host exists in the topology structure.
10040 Host: {0} failed to delete from the topology structure. Please check whether
hard disk exists in the host.
10041 '{0}' syntax is incorrect. Please check whether the format is correct.
10042 Failed to inject the configuration parameters. Please try again later.
10043 Hard disk: The number of data backups on the {0} is smaller than the backup
specification. It is not allowed to perform relevant operations.
10044 Other tasks are being executed on the current server. Please try again later.
10045 The current cluster is unavailable # Check the cluster status.
10046 Storage pool: The current data backup specification of '{1}' is '{2}', and the
hard disk: '{0}' does not allow the suspension operation # Migrate the data out
of the hard disk first
10047 The host has the {0} service. The deletion is not allowed # Please stop the
service first

10048 Input parameters are not changed # Modify parameters and try again
10049 Verification code error # Please enter again
10050 File storage cluster configuration failed # The storage service is not deployed
on some servers, or no public network segment IP is configured for the cluster.
10051 There is a deployment task being executed # Please try again later
10052 Error in parsing the Excel file.
10053 Configuring NTP# please try again later
10054 Parameter error
10055 {0}: Must be an integer between {1} and {2} or any value from {3}.
10056 Failed to obtain the operation steps.
10057 Hard disk: {0} is being isolated. Hard disk: {1} is not allowed to disable.
10058 Hard disk: {0} is out of service. Hard disk: {1} is not allowed to execute out of
service.
10059 The isolation task is cancelled because the alarm is cleared.
10200 The DSM task already exists.
10201 The DSM task does not exist.
10202 VIM TOKEN is invalid.
10203 The DSM does not support recollection of {0} data # Currently, only PM and
LOG data are supported.
10204 FM Data Push Failure
10500 Task execution failure
10501 The connection with AGENT {0} is lost.
10502 Task timeout
10503 The task is cancelled.
10504 Task execution error: {0}
10505 Exception when the Agent executes the task: {0}
10506 After the task is finished, the storage pool is not found {0}
10507 Pg creation process interruption (pg_num inconsistent with expected value)
10508 The OSD status is Down, and the Up operation is not allowed.
10509 The task is not delivered.
20002 Failed to query historical alarms # Check whether the management system is

normal.
41000 Mapping group {0} does not exist # Please refresh the page
41001 Mapping group {0} already exists # Please enter again
41003 Client {0} is not in the mapping group # Please refresh the page
41004 Client {0} is already in the mapping group # Please enter again
41007 LUN ID {0} already exists
41008 The gateway {0} is already in the mapping group # Do not add it again
41009 Gateway {0} is not in the mapping group # Please refresh the page
41010 The gateway {0} does not exist
41100 Storage pool {0} does not exist # Please refresh the page
41101 The volume {0} does not exist # Please refresh the page
41102 Volume {0} already exists # Please enter again
41103 The volume capacity must be an integer. # Please enter again.
41104 The volume capacity should be between 64 M-64T # Please enter again
41105 The block size must be an integer. # Please enter again.
41106 The block size should be between 4K-32 M # Please enter again
41107 The feature value must be an integer # Please enter again
41108 Invalid characteristic value
41109 Stripe unit must be an integer # Please enter again.
41110 The stripe size must be an integer # Please enter again.
41111 The volume is in the mapping group # Please move the volume out of the
mapping group first
41112 Rename is not allowed. The volume is in the mapping group # Please move the
volume out of the mapping group first
41113 The volume capacity cannot be reduced.
41114 Snapshot associated with the volume # Delete the snapshot associated with the
volume
41115 Invalid volume operation # Check whether the parameters are correct.
41116 Failed to query the volume information of the storage pool # Please try again
later
41117 Snapshot associated with the volume # Delete the snapshot associated with the

volume
41118 The QoS parameter value must be a positive integer.
41119 The reserved IOPS and IO priority cannot be set to 0# at the same time. Please
re-enter.
41120 The reserved IOPS cannot exceed the upper limit IOPS# please re-enter IOPS#
41121 The acquisition of used volume capacity times out # Please try again later
41122 The volume is associated with a non-independent clone volume # Please
perform clone isolation first
41123 Volume {0} is executing task # Please try again later
41124 The storage pool {0} is in the protection state, no operation is allowed.
41125 The QoS parameter value cannot be smaller than -1 # Please enter again
41150 Failed to obtain snapshot information.
41151 Invalid snapshot operation # Check whether the parameters are correct.
41152 Snapshot {0} does not exist # Please refresh the page
41153 Snapshot {0} already exists # Please enter again
41154 Snapshot {0} has been protected.
41155 Snapshot {0} not protected
41156 Snapshot {0} associated non-independent clone volume exists # Please perform
clone isolation first
41200 Client {0} does not exist # Please refresh the page
41201 Client {0} already exists # Please enter again
41202 The client name cannot be null # Please enter again
41203 The length of WWPN must be 16#. Please re-enter.
41204 Invalid WWPN format: {0}#
41205 WWPN {0} already exists # Please re-enter it
41206 WWPN does not exist # Please refresh the page
41207 Invalid IQN format: Please re-enter {0}#.
41208 IQN {0} already exists # Please enter again
41209 IQN {0} does not exist # Please refresh the page
41300 The server is not in the cluster # Refresh the page
41301 Server {0} service already exists

41302 The server {0} service does not exist # Please refresh the page
41305 The inbound password is null # Please enter again
41306 The outbound password is null # Please enter again
41307 The incoming authentication switch is not turned on, so the outgoing
authentication switch cannot be configured.
41308 Failed to obtain the IP address of the server.
41309 Invalid password format # Please enter again
41310 The outbound password cannot be the same as the inbound password.
41400 The SCSI metadata pool does not exist # Please specify the SCSI metadata pool
41401 The SCSI metadata pool already exists.
41402 Failed to configure the SCSI metadata pool.
41403 The SCSI metadata pool does not exist # Refresh the page
41404 SCSI metadata pool being migrated # Please try again later
41405 The destination storage pool does not exist # Refresh the page
41406 The destination storage pool is a protected storage pool. No operation is
allowed # Select another storage pool
41407 Gateway server is insufficient. To avoid single point of failure, at least {0}
gateway servers are required # Add a gateway server first
41408 Gateway server is insufficient. At least {0} gateway servers are required. Please
add a gateway server first.
41409 The remaining gateway servers are insufficient, and LUNs exist in this mapping
group. To avoid single point of failure, at least {0} gateway servers are required
# Remove LUNs from this mapping group first.
41410 The remaining gateway servers are insufficient. There are LUNs in this
mapping group. At least {0} gateway servers are required # Please remove the
LUNs in this mapping group first.
41411 Volume {0} has joined the mapping group # Please select another volume
41412 Gateway server {0} joined into the mapping group # Please remove these
gateway servers from the mapping group first

41413 The mapping group is executing a task # Please try again later
41414 Task execution of the mapping group fails # Contact ZTE technical support
41415 This iSCSI high availability group is in use. Do not delete this group. # Please
remove this high availability group from the mapping group first.
41416 There is a mapping group. The mapping group cannot be set. # Delete the
mapping group first.
41417 The high-availability group ID already exists.
41418 {0} is not a gateway server.
41419 {0} is not added into the rack.
41420 Existing gateway servers under rack {0} are added into other HA groups.
Please select gateway servers under other racks.
41421 The high-availability group name already exists.
41422 The HA group does not exist.
41423 It is forbidden to add or remove a gateway server at the same time.
41424 At least one gateway server is required for the high-availability group.
41425 Failed to obtain the available ID # Please try again later
41426 The high-availability group is being operated. # Please try again later.
41427 High-availability group {0} is already in the mapping group # Do not add it
again
41428 High-availability group {0} is not in the mapping group # Please refresh the
page
41429 The remaining high availability group is insufficient, and LUNs exist in this
mapping group. To avoid single point of failure, at least {0} high availability
group # Remove LUNs from this mapping group first.
41430 The remaining high availability groups are insufficient. There are LUNs in this
mapping group. At least {0} high availability groups are required. Please
remove the LUNs in this mapping group first.
41431 High availability groups are insufficient. To avoid single point of failure, at
least {0} high availability groups are required. Please add high availability
groups first.

41432 The high-availability group is insufficient, and at least {0} high availability
groups are required. Please add high availability groups first.
41433 The high availability group is enabled. This operation is forbidden.
41434 This operation is forbidden because the high availability group is not enabled.
41435 There is a high-availability group. This operation is forbidden. # Delete the
high-availability group first.
41436 Gateway server {0} added to other high availability groups # Please select
another gateway server
41437 Gateway server {0} has been added to the iSCSI high availability group #
Please remove these gateway servers from the high availability group first
41438 The gateway server is being operated. # Please try again later.
41439 The cluster is being configured # Please try again later
41440 The mapping group is being operated. # Please try again later.
41500 The storage pool mirroring mode is pool mode # Please modify the storage pool
mirroring mode first
41501 The storage pool mirroring mode is disabled # Please modify the storage pool
41502 The volume mirror status is disabled # Modify the volume mirror status first
41503 Volume as the active role # Please degrade the image first
41504 Volume as a secondary role # Please perform image promotion first
41505 The storage pool mirroring mode is disabled # Please modify the storage pool
41506 Enable the mirror service first.
41507 There are volumes with the slave role in the storage pool.
41508 Enable the volume log feature first.
41509 The volume mirror status is enabled # Please disable the volume mirror status
first
41510 Invalid image operation # Check whether the parameters are correct.
41511 Failed to obtain the mirror cluster configuration.
41512 Only enabling and disabling operations are supported.

41513 There is a volume whose mirror status is enabled in the storage pool # Please
disable the mirror status of the volume first
41514 The source volume is a slave volume and cannot be deleted.
51000 Deployment failed # Contact ZTE technical support.
51001 Server network unreachable # Check the IP address of the server
51002 Insufficient user permission # Ensure that the user has the operation permission,
or contact the system administrator to authorize a higher permission.
51003 Failed to start the agent service # Try it again later.
51004 Failed to log in to the server without password # Try to repair the server without
password
51005 Server password-free failure # Check whether the SSH software of the
management server and target server is installed successfully.
51007 Server password free timeout. Please try again later.
51009 Insufficient user permission # Ensure that the user has the operation permission,
or contact the system administrator to authorize a higher permission.
51010 Unsupported operating system # Deploy it on the supported operating system
by referring to the user guide.
51011 Only the RPM package management mode is supported.
51012 Software package download failure # Check whether the software package path
is correct.
51019 Failed to restore the YUM source file # Contact ZTE technical support
51021 Failed to synchronize NTP client configurations.
51022 NTP Server Configuration Synchronization Failure
51024 The management server is not configured with an IP address in the same
network segment as the target server.

51025 Failed to modify the agent configuration file.
51026 Failed to modify the Agent log level.
51035 Cluster configuration files fail to be synchronized.
51036 Failed to synchronize the log configuration file.
51037 No public network IP address is configured for the server.
51038 Failed to check the server.
51039 The MON service already exists.
51068 Failed to generate authentication information
51071 The hard disk has user data. # Are you sure you want to format the hard disk?
51076 Communication error # Check whether the management system is normal.
51078 The service fails to be enabled # Contact ZTE technical support.
51079 Start OSD service is not started #OSD service is started one by one. Please wait
patiently.
51080 Hard disk addition timed out. # Contact ZTE technical support.
51081 Hard Disk Cleaning Is Not Started
51082 The cluster configuration failed to be modified.
51084 Check the cluster status before version upgrade.
51085 There is no available upgrade version # Add a version on the Version
Management page.
51086 The current version is the latest one.
51087 Server not in the cluster # Please upgrade the server in the home cluster.
51088 Online upgrade is not supported.
51089 The version number of the selected upgrade installation package is lower than
the current version # Please select a new version
51090 Some servers are not configured with IP addresses in the management network
segment.
51092 Unknown Python module # Contact ZTE technical support.
51094 The MON service is enabled.
51095 Incorrect username or password # Please enter again

51100 The floating IP address fails to be modified # Contact ZTE technical support.
51101 MON Service Enabling Failure
51103 The server version is different from the cluster version.
51107 The IP address cannot be a floating IP address.
51108 The server is not configured with the IP address of the correct cluster network
segment {0}.
51109 The MDS service already exists.
51113 The uninstallation operation is not performed, and the pre-operation fails.
51114 The service failed to be uninstalled.
51115 Failed to modify the NFS configuration file.
51116 The NFS service failed to be enabled.
51117 Failed to create the NFS directory.
51118 Failed to enable the NFS export directory service.
51119 The NFS service fails to be disabled.
51120 Failed to enable the FUSE service.
51121 The version upgrade is not started yet.
51122 File Backup Failure
51123 Destination host network unreachable # Check whether the IP address is
correct.
51124 The destination path does not exist.
51125 The user has no operation permission over the destination path.
51127 MON service enabled timeout # Check whether the server system time is
synchronized or whether the public network of the cluster is normal.
51128 The acquisition of server {0} version failed
51129 Failed to modify the file storage cluster configuration.
51130 Failed to modify the NFS database.
51131 Timeout
51132 Please check the cluster first.
51133 Services of other clusters may exist.
51134 Failed to read the configuration file template # Contact ZTE to re-obtain the

version
51135 Upgrade not started: The {0} node upgrade fails # Please solve the {0} node
upgrade problem first
51136 The service fails to be stopped.
51137 The startup operation is not started, and the pre-operation fails.
51138 The deactivation operation is not started, and the pre-operation fails.
51139 Failed to start the service.
51140 Failed to upgrade the Agent because the management software is being
upgraded. Please refresh the interface and try again later.
51141 System detection timed out before deployment. Please refresh the page and try
again later.
51142 Please upgrade all MON nodes in the cluster first.
51143 Failed to stop services # Contact ZTE technical support.
51144 The AGENT configuration file does not exist # Retry later
51145 Agent authentication failed # Try it again later.
51146 Failure to turn off the data balance switch: For {0}#, please contact ZTE
technical support.
51147 Failure to turn on the data balance switch: For {0}#, please contact ZTE
technical support.
51148 The server is not configured with a correct cluster network and cannot be
connected with {0}.
51149 Server public network configuration error # Check the network configuration to
ensure that the unique public network address can be located.
51150 Server cluster network configuration error # Check the network configuration
to ensure that the unique cluster network address can be located.
51151 The public network address of the server does not match that of the public
network # Enter the correct network configuration
51152 The server cluster network does not match the cluster network address # Enter
the correct network configuration
51153 Server network configuration error # Enter the correct network configuration

51154 The public network of the cluster does not support mixing IPV4 and IPV6 #
Please select a network segment in the same IP format
51155 The cluster network does not support mixing IPV4 and IPV6 # Please select the
same IP network segment
51156 Server not bound to {0} network # Configure the {0} network for the server on
the server page
51157 The {0} network bound to the server has expired # Reconfigure the {0}
network for the server on the server page
51158 The storage service has been deployed on the server, and the public network
cannot be modified. # Please remove the storage service first
51159 Hard disks are deployed on the server. The cluster network cannot be modified.
# Please delete the hard disk first
52003 Command execution failure: {0}
52004 Service {0} enablement failure
52005 MGR key generation timeout
52006 The NFS export service fails to be disabled.
52007 The software package {0} fails to be installed.
52008 Timeout occurs when the bcache kernel driver is installed.
52009 Cluster ID inconsistency: {0}
52010 Inconsistent Ceph service version on the server: {0}
52011 The current version {0} does not support upgrade
52012 The current version cannot be upgraded to the major version: {0}
52013 Abnormal service exists in the cluster: {0}#. Please restore this service first.
52014 The Ceph service consistency check fails.
52017 Upgrade failure: {0}#. Please contact ZTE technical support.
52018 Service restart failure: {0}
52019 The current version does not support: {0}
52020 Hard disk detection failure: {0}

52021 The hard disk interface type is not supported.
52022 The hard disk exists in the system partition # If it is not used any more, format
it manually.
52023 The hard disk is a multi-path disk. # If it is not used any more, format it
manually.
52024 A logical volume exists on the hard disk. # If it is not used any more, format it
manually.
52025 The hard disk has been used as a cache disk. # If it is not used any more, format
it manually.
52026 The hard disk has been added to the cluster. # If it is not used any more, format
it manually.
52027 User data exists on the hard disk. If the user data is not used any more, format it
manually.
52028 User data exists on the hard disk. If the user data is not used any more, format it
manually.
52029 Failed to format the hard disk.
52030 Failed to allocate cache disk space # The hard disk is occupied.
52031 The cluster configuration failed to be modified.
52032 Failed to add the hard disk.
52033 Hard disk addition timed out.
52034 The NFS export service failed to be enabled.
52035 The NFS export service fails to be disabled.
52036 Path {0} is not an absolute path
52038 The file fails to write data: {0}
52039 Failed to generate authentication information
52040 Failed to query the IPTABLES list.
52041 Failure to create client keyring
52042 Failed to import client keyring
52043 MON Service Enabling Failure

52045 Failed to create MGR bootstrap keyring
52046 Operation {0} service failure
52047 Failed to initialize the hard disk.
52048 Failed to create OSD bootstrap keyring
52049 Failed to create MDS bootstrap keyring
52050 Failed to add the hard disk.
52051 Failed to create MDS keyring
52052 Failed to reset the service {0}.
52053 Failure to disable the service {0}
52054 {0} failure
52055 Failed to delete the authentication information.
52056 Failed to query the MON service status # Check whether the MON service is
normal.
52057 Installation software package {0} failure # Check whether the software package
path is correct.
52058 Failed to query the software package {0} # Check whether the path of the
software package exists.
52059 Query the software package {0} failure # Check whether the software package
has been installed.
52060 YUM clears {0} failure # Check YUM configuration
52061 Failed to configure the system time zone.
52062 Querying the {0} service version of the cluster fails # Please check whether the
cluster status is normal.
52063 Failed to query basic cluster information # Check whether the cluster status is
normal.
52064 Failed to create FUSE keyring
52065 The NFS service failed to be enabled.
52066 The NFS service fails to be disabled.
52067 The hard disk has been used as a DRBD device.
52068 The hard disk {0} does not exist.

52069 Failed to modify the NFS configuration file.
52070 Failed to uninstall the software package {0}.
52071 Failed to modify the configuration of the management system.
52072 Failure to unmount {0}
52073 Failed to mount {0}
52074 The cluster status is abnormal.
52075 Daemon service {0} failure
52076 {0} failure
52077 Existing unknown service: {0}
52078 Invalid command: {0}
52079 Failed to set the maintenance mode.
52080 Failed to cancel maintenance mode.
52081 Failed to delete the ZCACHE kernel module, which is in use.
52082 Failed to load the ZCACHE kernel module.
52083 Failed to delete the ZCACHE kernel module.
52084 The SAN service fails to be updated.
52085 The SAN service fails to be started.
52086 Cluster status detection failed.
52087 Failed to generate the cache device.
52088 Uninstall the abnormal MON service first.
52089 The MON service {0} fails to be uninstalled.
52090 Disabling the Last Normal MON Service
52091 Failed to upgrade hard disk: Stop encrypted device {0} failed
52092 Failed to upgrade hard disk: Failed to activate hard disk {0}
52093 Failed to install software package {0}.
52094 It is forbidden to stop the MON service. You must ensure that more than half of
the MON services in the cluster are normal.
52095 Failed to upgrade ZCACHE, hard disk OSD.{0}Failed to unmount the file to
the abnormal directory.
52096 Failed to upgrade performance components # Contact ZTE technical support.
52097 Insufficient disk space

52098 The cache pool failed to be configured.
52099 Failed to create the cache disk.
52100 Failed to update the disk # Retry
52101 Failed to clear the disk # Try again
52102 Failed to create the RAID5 device # Please try again
52103 Failed to delete the RAID5 device # Please try again
52104 The disk {0} is unavailable.
52105 The cache pool is being synchronized # Please try again later
52108 Cache pool being degraded # Please operate the online cache disk.
52110 Pool: The {0} status is abnormal, and the replacement cache disk is not secure.
52111 Pool: {0} does not have enough copies, so replacing the cache disk is unsafe.
52112 Cache Data Migration Failure
52113 Cache Device Registration Failure
52114 Failed to log out of the cache device.
52115 Failed to reset the cache device.
52116 The disk is not available. Please select another disk.
52117 The cache device fails to be bound.
52118 Failed to clean the cache pool of a RAID device.
52119 Failed to stop the cache disk.
52120 Failed to configure the host RAID.
52121 The cache disk does not exist # Check the cache disk
52122 Failed to configure the cache pool recovery speed.
52123 The cache pool failed to be restored.
52124 Hard disks in the cache pool fail to be restored.
52125 The cache pool is being used.
52126 Cache disk data migration timed out.
52127 The statistics of hard disks in the cache pool failed.
52128 The cache pool is unavailable # Rebuild the cache pool after deleting it.

52129 The server {0} package {1} is not installed # Please install the package
manually
52130 The cache pool is not ready after the server is powered on. # Retry later.
52131 The cache disk ID is the same as that of another cache disk. Do not replace it. #
Contact ZTE technical support.
52132 Failed to obtain the available area number # Please try again later
52133 The device does not exist.
52134 The device is not a piece of device # Contact ZTE technical support
52135 The device status is abnormal # Contact ZTE technical support.
52136 USB disk, forbidden to be used
52137 The Mon clock is not synchronous.
52138 Junk data may exist on this node. Please check and clear it first.
52139 Agent file synchronization failure # Try to fix the Agent.
52140 Hard disk stop timed out # Try it again later
52141 Failed to unmount the mounted hard disk # Please try again later
52142 A timeout occurred when the cache disk was stopped on a device. # Please try
again later.
52143 Failed to stop the hard disk # Try it again later.
52144 Failed to modify hard disk attributes # Retry later
52145 Failed to mount the hard disk # Retry later
52146 Failed to start the hard disk # Try it again later.
52147 Hard disk startup timed out # Please try again later
52148 Lost hard disk startup rule file # Contact ZTE technical support.
52149 Invalid hard disk operation # Contact ZTE technical support.
52150 Invalid cache disk operation # Contact ZTE technical support.
52151 Timeout of registering a cache disk-related device # Please try again later
52152 Asynchronous host clock # Check the host clock
52153 Connection establishment with the clock source timed out.
52154 Clock synchronization with the clock source fails.
52155 Failed to configure and enable the iSCSI high-availability service # Contact

ZTE technical support
52156 The iSCSI high-availability service fails to be stopped # Contact ZTE technical
support
52157 Failed to create the zstor user # Contact ZTE technical support
53000 The NAS command {0} fails to be executed.
53001 The NAS instance {0} already exists.
53002 The NAS instance '{0}' does not exist.
53003 The gateway exists under the NAS instance '{0}' and cannot be deleted.
53004 There is no available gateway under the NAS instance '{0}', so the operation
cannot be performed.
53005 The file system has an NAS instance, which cannot be deleted.
53006 The NAS instance does not access the LDAP domain.
53007 NAS Instance Not Accessing the AD
53008 Timeout occurs in executing the NAS command {0}.
53009 The NAS gateway status is abnormal.
53010 Not all NAS commands are executed successfully.
53011 The NAS instance has a shared directory.
53012 The {0} service of the gateway node is not healthy.
53013 The NAS instance is connected to the LDAP domain.
53014 The NAS instance has accessed the AD.
53015 The load balancing function is enabled for the NAS instance.
53016 The NAS instance does not enable the CIFS service.
53017 The FTP service is not enabled for the NAS instance.
53018 The NFS service is not enabled for the NAS instance.
53019 Batch operations are only applicable to the same NAS instance.
53020 The CIFS shared directory of the NAS instance already exists. It cannot be
added to the LDAP domain.
53021 The NAS instance already exists the CIFS shared directory. It cannot be added
into the AD domain.
53022 The NAS instance already exists an FTP shared directory, and cannot be added

to the LDAP domain.
53023 The NAS instance already exists a CIFS shared directory managed by the
LDAP user and cannot exit the LDAP domain.
53024 The NAS instance already exists a CIFS shared directory managed by the AD
user. It cannot be exited from the AD domain.
53025 An NAS instance already exists an FTP-shared directory managed by an LDAP
user, and the user cannot exit the LDAP domain.
53026 The NAS instance is not added to the LDAP domain, and thus the user cannot
log out.
53027 The NAS instance is not added to this AD, so you cannot exit.
53028 The service of the gateway node '{0}' '{1}' is not healthy.
53029 No gateway is configured for the NAS instance.
53030 The NAS instance has been configured with a shared CIFS directory, so
authentication cannot be modified.
53031 The shared FTP directory of the NAS instance is already configured, and
authentication cannot be modified.
53032 The {0} shared directory has been configured for the NAS instance, so all
services cannot be stopped.
53033 The NAS instance fails to read the {0} configuration file.
53034 The current version only supports the creation of one NAS instance.
53050 The {0} already exists.
53051 The {0} does not exist.
53052 The gateway belongs to the NAS instance '{0}'.
53053 The gateway node has the {0} service.
53054 The gateway node does not have the "{0}" service.
53100 The virtual IP group {0} already exists.
53101 The virtual IP group {0} does not exist.
53102 The virtual IP group is used for gateway nodes.
53103 The virtual IP group is used for the DNS node.
53104 The virtual IP group {0} has been used.

53105 The number of networks in the virtual IP group is smaller than the number of
associated gateway nodes.
53200 Number of DNS nodes: 1 or 2
53201 The DNS domain {0} does not exist.
53202 The DNS node does not exist.
53203 The gateway '{0}' has the DNS service.
53204 DNS domain name '{0}' already exists
53205 The primary DNS node does not exist, and the operation domain is not allowed.
53250 The user group {0} already exists.
53251 User group GID '{0}' already exists
53252 The user group {0} does not exist.
53253 The local user {0} already exists.
53254 The local user UID '{0}' already exists.
53255 The local {0} user does not exist.
53256 A user group is creating a task # Please try again later
53257 A user is creating a task, # Please try again later
53258 The user group "{0}" is in use.
53259 The user {0} is in use.
53260 The node already exists a local user group.
53261 Failed to query local user data.
53262 The user exists in the local user group and cannot be deleted.
53263 Master Group and Subsidiary Group Conflict
53264 The main group cannot be modified.
53300 Only one LDAP domain is supported.
53301 The LDAP domain '{0}' does not exist.
53302 No node joins the LDAP domain.
53303 An existing node is added to the LDAP domain.
53304 Failed to obtain LDAP user group/user information.
53305 All nodes fail to operate the LDAP domain.
53350 Only one AD is supported.
53351 Ad domain '{0}' does not exist

53352 No node joins the LDAP domain.
53353 An existing node is added to the LDAP domain.
53354 Failed to obtain AD user group/user information.
53400 The shared directory {0} does not exist.
53401 The shared directory {0} already exists.
53402 The shared directory has been used.
53403 The default protection period of the shared directory must be later than the
minimum protection period.
53404 The default protection period of the shared directory must be less than or equal
to the maximum protection period.
53405 The permission of the shared directory should be between 000 ~ and 777.
53406 Failed to obtain the details of the shared directory.
53407 A snapshot exists in the shared directory.
53408 The directory snapshot '{0}' does not exist.
53409 The directory snapshot '{0}' already exists.
53410 The directory snapshot policy {0} does not exist.
53411 The directory snapshot policy '{0}' already exists.
53412 Failed to delete the directory snapshot.
53413 Incomplete configuration of shared directory WORM
53450 The NFS export directory {0} does not exist.
53451 The NFS export directory {0} already exists.
53452 The NFS export directory does not restrict the existence of the client {0}.
53453 The NFS export directory does not restrict the existence of the client's {0}.
53454 There is a restricted client under the NFS export directory.
53500 The CIFS export directory {0} does not exist.
53501 The CIFS export directory {0} already exists.
53502 CIFS "{0}" does not exist.
53503 The {0} user permission of the CIFS export directory already exists.
53504 The shared directory of the existing CIFS is authenticated by {0}.
53505 User rights exist in the CIFS export directory.

53506 The CIFS rights are incorrectly selected.
53550 The FTP export directory {0} does not exist.
53551 The FTP export directory {0} already exists.
53552 The user {0} permission of the FTP export directory does not exist.
53553 The {0} user permission already exists.
53554 The shared directory of the existing FTP uses the {0} authentication.
53555 There are user permissions under the FTP export directory.
53600 The user quota does not exist.
53601 The user quota already exists.
53602 Failed to query the user quota.
53650 This operation is not supported in the current status.
53651 Invalid expiration time
53652 Non-WORM file
53653 The expiration time cannot be less than {0}
53654 The expiration time cannot be later than {0}
54001 Failed to obtain the cluster version number.
54002 Only the versions whose version numbers start with 10 are supported.
54003 Cluster Version Consistency Check Failure
54100 Expansion failure # Contact ZTE technical support.
70001 Failed to check the user password # Please enter again
70002 The user password is null # Please enter again
70003 The current user is a system administrator and cannot be configured with
permissions.
70004 The current user is a system administrator and is not allowed to perform cluster
configuration for the user.
70005 A new user fails to be created. # Check whether the parameters are correct.
70006 The user is created successfully, but the permission configuration fails.
70007 User Creation and Permission Configuration Succeeds, and Cluster
Configuration Fails
70008 Failed to modify user permissions.

70009 User Cluster Configuration Failure
70010 Failed to modify the user password # Check whether the parameters are correct
70011 Failed to delete user cluster information.
70012 Failed to delete user information.
70013 The user does not exist # Please refresh the page
70014 Do not set the same password within {0} times of modification.
70015 Your password has expired. Please modify it immediately.
70016 The user name is limited by the system. Please enter another user name.
70017 Your password is the default one. Please modify it immediately.
70018 Your password is about to expire. Please modify it as soon as possible.
70019 The domain account password cannot be modified.
70020 The domain account permissions cannot be modified.
70021 The local username already exists.
74000 Communication error # Contact ZTE technical support.
74001 The size of the license file exceeds the limit (2M) # Apply for a new license.
74002 Failed to check the license file # Apply for a new license.
74003 The license file has been bound and used # Apply for a new license.
74004 This function is not authorized # Import the license file authorized by this
function.
74005 The license file already exists.
74006 File import error
74007 Cluster capacity exceeds the license limit {0}#
74008 File format error # Please import the extension name.LCS or .lcs license file
74009 The license has expired # Apply for a new license.
74010 Failed to check the license file # Apply for a new license.
74011 This function is not authorized # Import the license file authorized by this
function.
75000 SNMP Operation Error
75100 The SNMP public configuration failed to be obtained.
75101 The SNMP public configuration failed to be modified.

75102 The port is used. # Please enter again.
75200 The SNMP user configuration failed to be obtained.
75201 SNMP user creation failure # Check whether the parameters are correct.
75202 The SNMP user fails to be modified. # Check whether the parameters are
correct.
75203 The SNMP user fails to be deleted.
75204 SNMP user does not exist # Refresh the page
75205 The SNMP user already exists # Please enter again
75206 The specified security level is not supported # Please enter again
75207 The specified authentication mode is not supported # Please enter again
75208 The specified encryption mode is not supported # Please enter again
75209 Invalid authentication password # Please enter again
75210 Illegal encrypted password # Please enter again
75300 Failure to obtain the SNMP TRAP configuration information
75301 SNMP TRAP rule creation failure # Please check whether the parameters are
correct.
75302 SNMP TRAP rule modification failed # Please check whether the parameters
are correct.
75303 SNMP TRAP rule deletion failure
75304 The TRAP rule already exists # Please enter again
75305 Trap rule does not exist # Refresh the page
75306 The encrypted password of the SNMP user is invalid.
76001 The host cache pool information fails to be queried # Retry again later.
76002 Cache pool does not exist # Refresh the page
76003 Cache disk does not exist # Refresh the page
76004 The cache pool name already exists # Please enter again
76005 The cache pool name must be unique.
76006 The cache pool fails to be created. # Check whether the hard disk is available.
76007 The cache pool configuration fails to be updated # Try to update the cache pool

again later.
76008 The cache configuration fails to be updated # Try to update the configuration
again later.
76009 Cache pool deletion failed # Try to delete the cache pool again later.
76010 Insufficient cache pool space # Use a large-capacity disk to recreate a cache
pool
76011 Buffer pool in use
76012 Deploy the MON service first.
76013 The cluster is replacing other cache disks. Please try again later.
76014 This type of cache disk replacement is not supported.
76015 Disk {0} space is insufficient # Please select large-capacity disk or use other
cache pool mode
76016 Replace the abnormal cache disk first.
76017 Cannot replace the cache disk in the unavailable cache pool # Replace the cache
pool after deleting it.
76018 One server can have only one cache pool.
76019 The cache disk is offline # Replace the offline cache disk first to restore the
cache pool.
76020 Replacement is not safe. # Contact ZTE technical support.
76021 Insufficient cache ratio # Modify the cache pool configuration and recreate it.
76022 The cache pool cannot be created because there is no HDD hard disk.
76023 Failed to obtain the sector size.
76024 The cache disk being used cannot be replaced.
77001 User permission is insufficient.
77002 Operation error
77003 This operation does not exist # Refresh it and try again.
77004 Operation object {0} executing task # Please try again later
77005 There is a task being executed # Go to <b> <a href
View the
"javascript:

Index.goSyste
mPageMenu(\''l
ogcommon\'');
"> Operation
log </a>
</b> page
77006 A task is being executed.
77101 The last collection task is not finished. Please try again later.
77102 The task failed to be started.
77103 Failed to collect logs. Please try again later.
78000 The current operation is not supported.
78001 The current cluster is not in cluster maintenance mode # Refresh the page
78002 The maintenance mode is not changed.
78003 The current cluster is in cluster maintenance mode # Refresh the page
80000 Checking server password-free
80001 Checking the operating system of the server
80002 Synchronizing the Configuration File
80003 The software package is being installed.
80004 Checking the NTP service.
80005 Synchronizing the NTP Client Configuration File
80006 Synchronizing the NTP Server Configuration File
80007 Checking the Agent Network
80008 Synchronizing the Agent Configuration File
80009 Enabling the NTP service.
80010 Updating time zone configuration
80011 Saving NTP service information
80012 Enabling the AGENT service
80013 The cluster configuration is being synchronized.
80014 Checking server status
80015 The MON service is being detected.
80016 Deleting MON service

80017 Creating MON Service
80018 The MON service is being enabled.
80019 Waiting for the completion of MON service enabling
80020 Waiting for the completion of other MON services
80021 Creating MGR key
80022 Guiding OSD service creation
80023 Enabling OSD service for/dev/{0}
80024 Reading hard disk capacity
80025 The cache disk is being operated.
80026 Querying hard disk information
80027 Deleting hard disk information
80028 Formatting the hard disk
80029 Cluster upgrade conditions are being detected.
80030 Cluster detection is being completed.
80031 Detecting Services
80032 Queuing for upgrade
80033 Checking whether the Ceph service is healthy
80035 Querying Version No.
80036 Synchronizing Client Authentication Information
80037 Saving server information
80038 The server network is being detected.
80039 Obtaining server memory information
80040 The gateway service is being operated.
80041 The server is not encrypted.
80042 Modifying cluster configuration
80043 Configuring QoS Information
80044 Waiting
80045 Enabling service {0}
80046 Stopping service {0}
80047 Checking Whether the Server Exists

80048 The environment is being prepared.
80049 Checking Roles
80050 The MDS service is being detected.
80051 Creating MDS key
80052 Enabling the MDS service
80053 Enabling the MDS service
80054 Stopping a service
80055 Synchronizing NFS Configuration Files
80056 Enabling the NFS service
80057 Creating NFS Export Folder
80058 Enabling the NFS Export Service
80059 Disabling the NFS service
80060 Enabling FUSE
80061 File Backup in Progress
80062 The hard disk is being detected.
80063 Configuring an SCSI metadata pool
80065 Restarting the NFS service
80066 Synchronizing the Configuration File
80067 Synchronizing CTDB configuration
80068 Starting FUSE service
80069 Starting CTDB service
80070 Synchronizing LVS configuration
80071 Waiting for the completion of the upgrade of the peer node of HA
80072 The database version is being updated.
80073 The system service is being restarted.
80074 Updating ZCACHE kernel
80079 Restarting
80090 Please wait.
80092 HA Software Package Upgrading

80094 Wait until all MGR are deployed
80095 Checking cluster status
80096 HA Software Package Upgrading
80101 Restarting the Agent Service
80102 Starting Cluster Configuration Synchronization
80105 Verifying the new disk
80106 Collecting cache disk information
80107 Checking cluster status
80108 The original cache disk is dirty.
80109 The original cache disk is dirty.
80110 A new cache disk is being deployed.
80111 A new cache disk is being deployed.
80112 The hard disk is being restored.
80113 Deleting original cache disk
80114 The cache disk restoration speed is being configured.
80115 Recovering the cache disk
80116 Restoring the cache disk:
80117 The hard disk is being restored.
80118 Stopping the gateway service
80119 Verifying the cache pool name
80120 Verifying that the hard disk is available
80121 Verifying hard disk capacity
80122 Creating a cache disk
80125 Detecting the Cache Pool
80126 Deleting cache pool
80127 The back-end device of the cache pool is being collected.
80128 Verifying Cache Security
80129 Setting the hard disk maintenance mode
80130 Data is being migrated.

80131 Verifying the new hard disk
80132 Creating a partition for the new hard disk
80133 A new cache device is being generated.
80134 Binding Backend Device
80135 Deleting original cache disk
80136 Recovering the cache disk
80137 Waiting for the Backend Device to Restore
80138 Back-end device maintenance mode is being canceled.
80139 Updating firewall rules
80140 Please wait.
80142 Checking whether the client service network is reachable
80143 Software is being uninstalled.
80144 Clearing node data
80145 Stopping services
80146 Waiting for Cluster Restoration
80147 Upgrading other high-priority services and hosts
80148 Upgrading other high-priority services and hosts
80149 The data balance function is being disabled.
80151 Checking Configurations
80152 Check the configuration.
80153 Configure {0} {1}
80154 Configure {0} end {1}
80155 Configure {0} timeout
80156 Clock synchronization is being configured.
80157 Synchronizing the Clock with the Clock Source
80158 The management node is being restarted.
80159 Setting the HA Maintenance Mode
80160 Configuring the Master Node
80161 The standby management node is being configured.
80162 HA maintenance mode is being canceled.
80163 Configuring Other Nodes

80164 Configuring other nodes {0}/{1}
80165 NTP Configuration End
80166 Configuring and Enabling the High-Availability Service
80167 Stopping High-Availability Services
80168 Checking server network
90001 Hard disk parameter error # Contact ZTE technical support.
90002 Failed to check modified parameters # Please enter again
90011 Server '{0}' is not in the rack # Please refresh the page
90012 Server '{0}' is located in another rack '{1}' # Please refresh the page
90013 The rack '{0}' does not exist # Please refresh the page
90014 The rack name already exists # Enter the rack name again
90015 There is a server under the rack # Remove the server first
90027 There are volumes added to the mapping group in the storage pool # Remove
the volumes from the mapping group first
90028 Request parameter error
90029 Server {0} does not exist # Please refresh the page
90030 The storage pool name is already used # Please enter again
90031 Security level parameter of the storage pool is incorrect.
90032 The storage pool data backup policy parameter is incorrect.
90033 Hard disk '{0}' does not exist # Please refresh the page
90034 The selected hard disk '{0}' has been used.
90035 Select a device that bears the data of the corresponding storage pool, or select
an existing shared storage pool group.
90036 The specified storage pool group does not exist # Select an existing storage
pool group
90037 The current status of the specified storage pool group is exclusive # Select a
shared storage pool group to create a storage pool.
90038 The number of multi-copy policy copies should be a positive integer not greater
than 4 # Please enter again
90039 The erasure code policy should be '4+2' or '2+1'#. Please re-enter it.
90040 Storage pool '{0}' does not exist # Please refresh the page

90041 The storage pool '{0}' is created externally. It cannot be configured as a shared
storage pool and cannot be updated with hard disk distribution.
90042 The storage pool '{0}' is already in the shared status.
90043 Storage pool '{0}' created based on other storage pools, hard disk distribution is
not allowed to be updated.
90044 Hard disk '{0}' does not exist # Please refresh the page
90045 The hard disk '{0}' has been used by other storage pools.
90046 The specifications of the erasure code storage pool cannot be modified.
90047 Failed to obtain the security policy for the storage pool.
90048 The storage pool is migrating SCSI metadata # Retry later
90049 Failed to obtain cluster information # Retry later
90050 Select the server that has at least the same number of copies as {0}, or specify a
data backup mode for the corresponding storage pool.
90051 Select a rack that has at least the same quantity as the specified number of
copies {0}, or specify a data backup mode for the corresponding storage pool.
90052 Select a hard disk that has at least the same number of copies as {0}, or specify
a data backup mode for the corresponding storage pool.
90053 Creation failure. Each shared storage pool group contains a maximum of '{0}'
storage pools.
90054 The selected hard disk '{0}' has been used by the storage pool group '{1}'
90055 There are volumes in the storage pool. Please delete the volumes first.
90056 The protected storage pool cannot be renamed.
90057 Storage pool '{0}' is in protection status
90058 Storage pool '{0}' is in unprotected status
90059 Creation failed. A storage pool is being created. The shared storage pool group
already contains '{0}' storage pools # Please try again later
90060 The storage pool '{0}' is in the unhealthy status # Please handle the related
alarms first
90061 Failed to create. The rack name cannot be the same as the host name.

90062 Failed to create. The rack name cannot be the same as the storage pool name.
90063 Failed to create. The rack name cannot be the same as the hard disk name.
90064 Server {0} is a member gateway server of the iSCSI HA group # Please remove
these gateway servers from the iSCSI HA group first
90065 The stripe depth must be an integer multiple of 4K.
91001 The system is operating in active/standby HA mode.
91002 The floating IP address is incorrect # Enter an IP address that is in the same
network segment as the cluster management network
91003 Communication of the management server is abnormal # Try it again later.
91004 The HA cluster is being created. # Do not create it again.
91005 The HA cluster already exists # Refresh the page
91006 Failed to configure the active/standby cluster mode # Please try again later
91007 Incorrect heartbeat link configuration # Check whether the heartbeat link
configuration is correct.
91008 HA cluster does not exist # Refresh the page
91009 There is a task in progress for the HA cluster # Try it again later
91010 The system does not operate in active/standby HA mode # Configure the
active/standby HA mode and then try again.
91011 The standby node of the HA cluster is offline and cannot be switched over.
91012 The standby node of the HA cluster cannot be switched because it is in inactive
status.
91013 The standby node of the HA cluster is abnormal and cannot be switched over.
91014 The HA cluster status is abnormal, and switchover cannot be performed.
91015 The shared device in the HA cluster is in abnormal status and cannot be
switched.
91016 Data cannot be switched during data synchronization of the HA cluster shared
device.
91017 HA Cluster Switchover Failure
91018 The HA cluster does not have this maintenance network address.
91049 Cluster-related software is not installed on the peer node.

91050 The HA cluster fails to be created # Contact ZTE technical support
91051 The heartbeat link configuration of the HA cluster is incorrect.
91052 Failed to format the shared block device # Check whether the shared block
device has been used.
91053 Failed to stop the original HA cluster # Try it again later.
91054 Failed to remove the original HA cluster # Try it again later.
91055 HA cluster startup failed # Retry later
91057 HA cluster property configuration failed # Try it again later.
91058 The floating IP address failed to be created.
91063 HA cluster initialization failed # Retry later
91068 HA cluster startup timed out. # Try it again later.
91069 Incorrect configuration of shared block device # The shared block device must
start with "/dev/."
91070 The peer node fails to go offline # Try it again later.
91071 Failed to disable the shared block device # Please try again later
91072 Failed to create metadata for the shared block device # Try it again later.
91073 Failed to enable the shared block device # Try it again later.
91074 Failed to get online on the peer node # Please try again later
91075 The shared block device does not exist # Check whether the shared block
device configuration is correct.
91076 The shared block device is used # Check whether the shared block device

configuration is correct.
91078 The network ports corresponding to the local node management network of the
HA cluster are different from those of the peer node management network #
Check whether the configuration of the cluster management network is correct.
91081 Insufficient user permission # Make sure that the user connected to the peer
node has the operation permission, or contact the system administrator to grant
the higher-level permission.
91082 The local node management software is not installed properly or the installation
is not completed. # Reinstall the management software.
91083 The management software of the peer node is not installed properly or is not
installed completely # Reinstall the management software.
91084 Inconsistent management software version # Install the management software
of the same version on the peer node.
91085 Failed to obtain the local user information # Ensure that the local user name is
correct.
91086 A maximum of five maintenance IP addresses can be created.
91087 The HA maintenance IP fails to be created. # Contact ZTE technical support.
91088 Failed to modify the HA maintenance IP. # Contact ZTE technical support.
91089 Failed to delete the HA maintenance IP. # Contact ZTE technical support.
91092 Failed to obtain the HA information.
91093 Failed to repair the shared block device # Contact ZTE technical support.
91094 The remote node Nginx fails to bind the interception IP address # Contact ZTE
technical support
91095 Nginx listening port binding IP address failed # Contact ZTE technical support
91096 Failed to reload the Nginx configuration file # Check whether the configuration
file "/etc/zstor-nginx/conf.d/zms.conf" is correct
91097 The Nginx configuration file does not exist.

91098 Failure to synchronize the Nginx configuration file
91099 The HA cluster status is abnormal.
92001 The request parameter cannot be null.
92002 Request parameter error
92003 Failed to create tecs alias
92004 Failed to create tecs back end
92005 The tecs back-end '{0}' already exists.
92006 The tecs back-end '{0}' does not exist.
92007 The tecs alias '{0}' already exists.
92008 Tecs alias '{0}' does not exist.
92009 The supported backend types are: "cinder," "nova," "glance" and
"cinder_backup."
92010 The host already exists.
92011 Failed to create the tecs host.
92012 Related tasks exist on the host '{0}'.
92013 TECS has relevant tasks running.
92014 No current task
92015 Ceph installation failure
92016 Failure to update TECS back end
92017 Failure to create tecs back-end user
92018 Failed to save the database.
92019 There is no task of the request type.
92020 Failed to update the database.
92021 The Glance user already exists.
92022 The Glance user does not exist. Please create the Glance user first.
92023 Failed to upload the file. Please confirm that the file is normal and try again.
92024 The private key file type must be'raw','hex' or'base64'.
92025 Failed to change the user's private key file.
92026 Nova back-end storage pool without '{0}' # Please add the storage pool as Nova
back-end.
92027 Tecs alias '{0}' has been used # Please use another name

92028 The length of the Ceph AES private key must be 128192256 bits.
92029 Coding failed. Please make sure that the file '{0}' and coding '{1}' are correct.
92100 The application '{0}' does not exist
92101 The application '{0}' already exists
92102 Application '{0}' exists in the user # Please delete the user first or choose to
force the deletion
92103 The Ceph user '{0}' does not exist.
92104 The Ceph user '{0}' already exists.
92105 The Ceph user '{0}' has been used by other applications.
100001 Failed to obtain the FTP user # Please try again later
100002 Failed to modify the FTP user. # Try to modify the FTP user again later.
100003 Failed to delete the FTP user # Try to delete the FTP user again later.
100004 The FTP user already exists # Please enter again
100005 FTP user does not exist # Refresh the page
100006 Failed to add an FTP user. # Try to add an FTP user later.
100101 The file system already exists # Please enter again
100102 The file system does not exist # Refresh the page
100103 The storage pool {0} has been used # Please enter again
100104 The MDS service is running # Disable the MDS service first
100105 The MDS service is disabled # Enable the MDS service first
100106 The file system {0} has no snapshot enabling right.
100107 The MDS service is offline and cannot be operated.
100108 There is an NAS instance in the file system # Delete the NAS instance first
100109 Only one file system can be created in the current version.
100150 Folder {0} already exists # Please enter again
100151 Folder {0} does not exist # Please enter again
100201 Version parameter error
100202 Illegal version file
100203 Failed to upload the version.
100204 Failed to create the local source.

100205 Failed to delete the version.
100206 The version is in use and cannot be deleted.
100207 The versions of the same version number must be deleted at the same time.
100208 The version fails to be uploaded, and a patch version cannot be uploaded
directly.
100209 The version does not exist.
100210 The component version does not exist.
100211 The management system configuration does not exist.
100212 The management system failed to be updated.
100213 The management system is not of the latest version. Please upgrade the
management system first.
100214 The cluster version is the latest version.
100301 Certificate file not supported. Select a certificate of the PEM type.
100302 Unsupported private key file. Select a private key file of the PEM type.
100303 Failed to upload the file. Please try again later.
100304 Failed to upload the certificate file. Please try again later.
100305 Failed to upload the private key file. Please try again later.
100306 The certificate does not match the private key. Select the certificate and private
key file that match with each other.
100307 Only the certificate of the RSA type is supported. Select a proper certificate file.
100308 Only a key of the RSA type is supported. Select a proper key file.
100309 The imported certificate is the same as that used by the server. Please select a
different certificate to upload.
100310 Certificate check failed. Please ensure that the certificate is complete and
available.
100311 The server is using the default certificate and does not need to be reset.
100312 Failed to reset the default certificate. Ensure that the default certificate and
private key are not damaged.
100313 No certificate needs to be updated.

100314 To enable two-way authentication, you must upload the root certificate of the
client.
100315 Ca certificates and private key files must be uploaded at the same time.
100316 Failed to change the certificate information of the remote server.
100317 The DSM server certificate cannot be deleted.
100318 The specified remote server certificate does not exist.
100319 The specified remote server certificate already exists.
100320 The certificate file of the remote server must be uploaded.
100321 The client certificate file must be uploaded.
100322 The certificate revocation list does not match the root certificate. Select the
certificate revocation list and the root certificate.
100323 The certificate has been revoked.
100400 The backup server does not exist.
100401 The backup policy is incorrect.
100402 The backup record does not exist.
100403 Failed to prepare backup files.
100404 The version of the backup and restoration file is different from the current
version.
100405 The backup file does not exist.
100406 Failed to download the backup file.
100407 Failed to upload the backup file.
100408 Failed to delete the backup file.
100409 Failed to restore the backup file.
100410 Check whether the version fails to be matched.
100411 Backup or restoration task in progress # Please try again later
100412 The backup server already exists.
100413 Failed to connect to the backup server # Check whether the server IP or port is
correct
100414 Failed to log in to the backup server # Check whether the username or
password of the server is correct.
100415 The backup server has been used.

100416 The upload path of the backup server is incorrect # Check whether the user has
the permission to create or operate the path
100417 The file already exists on the backup destination.
100418 The backup file is being used.
100419 The backup policy does not exist.
100420 The user already exists.
100421 The performance backup policy already exists.
100422 Service start failure # Please check whether port {0} is occupied
101500 Domain server connection failure
101501 Login is forbidden due to insufficient permissions.
101502 The LDAP user fails to be deleted.
101503 The LDAP server does not exist.
101504 Administrator DN or password error
101505 Certificate check failure
101506 Group of the currently logged-in user that cannot be operated.
100600 System configuration information does not exist
100601 The whitelist configuration does not exist.
100602 Failed to configure the whitelist # Check whether the parameters are correct.
100603 NTP Server Addition Failure
100604 Failed to obtain the internal clock source.
100700 The client network operation failed # Contact ZTE technical support.
100701 Client network {0} already exists
100702 The client network does not exist.
100703 The client network fails to be added.
100704 The client network fails to be deleted.
100705 Client network test timeout
100706 Client network check failure: {0}
100707 The client network fails to be updated.
100800 Failed to obtain the management network IP according to the synchronization

network segment. Verify that the synchronization network segment is correct.
100801 Failed to modify the NTP configuration file.
111000 Parameter error
111001 Timeout
111002 The operation is not supported.
111003 Operation error
112000 The NFS service is unavailable.
112001 NFS Startup Failure
112002 NFS Stop Failure
112003 The NFS fails to be restarted.
112004 NFS Initialization Failure
112005 Failed to add the export directory on the NFS.
112006 The NFS fails to delete the export directory.
112007 The NFS fails to update the export directory.
112008 Client Addition Failure in the NFS
112009 The NFS fails to delete the client.
112010 The NFS fails to update the client restriction configuration.
112011 The NFS export directory does not exist.
112012 Failed to modify the port number on the NFS.
112500 Samba initialization failure
112501 Samba startup failure
112502 Samba stop failure
112503 The samba fails to restart.
112504 The samba configuration fails to be reloaded.
112505 The samba configuration file fails to be parsed.
112506 Samba sharing already exists.
112507 Samba sharing does not exist.
112508 Unknown configuration error of samba
112509 The samba fails to obtain the service status.
112510 The samba shares the allowed guest account access.
112511 The samba sharing item does not exist.

113000 The ftp service is unavailable.
113001 Ftp startup failure
113002 Ftp stop failure
113003 Ftp restart failure
113004 Ftp initialization failure
113005 Failed to create ftp sharing
113006 Failure to delete ftp
113007 Failed to add the user.
113008 Failed to delete the user.
113009 Failed to modify user permissions.
113010 Failed to set anonymous access.
113011 Failed to set the LDAP service.
113012 Failed to cancel the LDAP service.
113013 Failed to set the transmission rate.
113014 Failed to set the port.
113015 The sharing already exists.
113016 The LDAP service is enabled.
113500 Ctdb configuration failure
113501 Ctdb startup failure
113502 Ctdb stop failure
113503 When ctdb is started, it fails to set auto-start upon startup.
113504 When ctdb is stopped, disable the autorun failure at startup.
113505 Ctdb cluster downgraded
113506 The ctdb cluster is unavailable.
113507 Failure to obtain ctdb cluster status
113508 Ctdb pre-initialization failure
113509 Ctdb initialization failure
113510 Ctdb restart failure
113511 The ctdb node status is unhealthy.
113512 Failed to obtain the ctdb node status
114000 Lvs initialization failure

114001 Lvs stop failure
114002 Lvs cluster downgrade
114003 The lvs cluster is unavailable.
114004 Failed to obtain the lvs cluster status
114500 DNS Startup Failure
114501 DNS restart failure
114502 Failed to add the primary DNS.
114503 The standby DNS fails to be added.
114504 The primary DNS fails to be deleted.
114505 The standby DNS fails to be deleted.
114506 Failed to delete the domain record.
114507 Failed to delete the domain file.
114508 Failed to add the domain.
114509 Failed to update the domain.
114510 The DNS service fails to be stopped.
115000 Ad Configuration Failure
115001 Failed to join the AD.
115002 Failure to shut down the NetworkManager service
115003 Failed to connect to the AD server.
115004 Failed to view the AD user group.
115005 Failed to View AD Users
115006 Failed to format the AD user.
115007 Failed to View AD User Groups and Users
115008 The node is not added to the AD.
115009 Failure to view AD users with wbinfo
115010 The winbind service is unavailable.
115011 Failed to exit the AD domain.
115012 Failed to delete the netbios name.
115013 Failed to read the AD configuration file.
115014 The AD configuration file fails to be written.
115015 Base64 decoding failure

115500 Failed to connect to the LDAP server.
115501 Failed to View LDAP User Groups
115502 Failed to View LDAP Users
115503 Failed to format the LDAP user.
115504 Failed to View LDAP User Groups and Users
115505 The nslcd service is unavailable.
115506 Failed to View the Status of the Node Adding to the LDAP Domain
115507 Failed to join the LDAP domain.
115508 Failed to exit the LDAP domain.
115509 The node is not added to the LDAP domain.
115510 LDAP binding password base64 decoding failure
116000 Failed to view the local user group.
116001 Failed to view local users.
116002 Failed to View Local User Groups and Users
116003 The user already exists.
116004 Failed to create a user.
116005 Failed to set the user password.
116006 This user is a Samba user.
116007 Failed to delete the user.
116008 The user group already exists.
116009 Failed to create the user group.
116010 Failed to delete the user group.
116011 Failed to modify user information.
116012 User password base64 decoding failure
116013 Failed to generate the encrypted user password.
116500 CEPH cluster connection failure
116501 Failed to connect to the file system.
116502 The directory does not exist.
116503 No quota attribute
116504 No permissions.
116505 Failed to set the directory capacity quota.

116506 Failed to obtain the directory capacity quota.
116507 Failed to set the directory file quota.
116508 Failed to obtain the directory file quota.
116509 Failed to set the user capacity quota.
116510 Failed to obtain the user capacity quota.
116511 Failed to set the group capacity quota.
116512 Failed to obtain the group capacity quota.
116513 Failed to set the WORM attribute of the directory
116514 Failed to modify the WORM attribute
116515 Failed to delete the WORM directory.
116516 Failed to obtain the WORM status.
116517 Failed to obtain the WORM attribute of the directory
116518 Failed to obtain the directory information.
116519 Failed to create a snapshot task.
116520 Failed to delete the snapshot task.
116521 Failed to restore the snapshot.
116522 Failed to create the directory.
116523 The directory already exists.
116524 The directory is not empty.
116525 Failed to delete the directory.
116526 Failed to change the directory permission.
116527 Failed to change the directory.
116528 Failed to modify the directory name.
116529 Failed to change the directory.
116530 Failed to create the file.
116531 Failed to obtain the status of the WORM file
116532 Failure to set the expiration time of the WORM file
116533 Failure to trigger the WORM file to enter the protection status
116534 Failure to trigger WORM file to enter the overdue status
116535 Failed to obtain the status information.
117500 Failed to enable the snapshot function.

117501 Failed to disable the snapshot function.

TECS-CloveStorageV07.20.20.07UME One-Click Deployment and Configuration CloveStorage Guide - R1.4

Uploaded by

Copyright:

Available Formats

You might also like

TECS-CloveStorageV07.20.20.07UME One-Click Deployment and Configuration CloveStorage Guide - R1.4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

TECS-CloveStorageV07.20.20.07UME One-Click Deployment and Configuration CloveStorage Guide - R1.4

Uploaded by

Copyright:

Available Formats

TECS-CloveStorageV07.20.20.07UME Daisyseed3.

0 One-click Deployment and Configurationand ConfigurationGuide Secret▲

<All rights reserved. No spreading without permission of ZTE.> Page1

This document is owned by ZTE Corporation. Without the written permission of

 Document No.: SJ-20220622131424-001

 Document version: 20220825-R1.3

<All rights reserved. No spreading without permission of ZTE.> Page2

2.1 PREPARE THE VERSION FILE..............................................................................................................5

4. DEPLOYMENT TABLE CONFIGURATION................................................................................................10

4.1 DAISYSEED TABLE CONFIGURATION......................................................................................................10

5. DAISYSEED ONE-CLICK DEPLOYMENT.................................................................................15

5.1 DAIYSEED SOFTWARE PREPARATION......................................................................................................15

6. UPDATING THE RAID CARD DRIVER..................................................................................................19

6.1 CHECK THE DRIVER VERSION BEFORE UPGRADE.....................................................................................19

APPENDIX 1 5300 G4X RAID CONFIGURATION.........................................................................21

APPENDIX 2 5300 G4X BIOS CONFIGURATION..........................................................................31

APPENDIX 3 CLOVESTORAGE ERROR CODE DESCRIPTIONS............................................33

<All rights reserved. No spreading without permission of ZTE.> Page3

Version Update Description

<All rights reserved. No spreading without permission of ZTE.> Page4

2.1 Prepare the version file.

Version Version File Name Description

OS Mimosa-x86_64-7.4-030886-FI.iso Storage resource operating system

daisy-2016.3.15-11.4.52135.el7.x86_64.rpm Daisy software package

daisyseed_win_V07.21.20.07_523.7z Daisyseed3.0 package

smartpqi-2.1.8-040.1_1.el7.x86_64.rpm Controller drive update package

update_data_cache_serial.zip This package is a tool for updating

<All rights reserved. No spreading without permission of ZTE.> Page5

Version Version File Name Description

after the server replaces the raid card.

clear_storage_script.zip Storing the Clearing Script

Client package used by the PaaS container

2.2 Environment networking planning

Figure 2.1 Networking Diagram

<All rights reserved. No spreading without permission of ZTE.> Page6

Figure 2.2 Final Delivery Deployment Diagram

<All rights reserved. No spreading without permission of ZTE.> Page7

Figure 2.3 Daisyseed One-Click Deployment CloveStorage Network Planning

2.3 Deployment precautions

<All rights reserved. No spreading without permission of ZTE.> Page8

<All rights reserved. No spreading without permission of ZTE.> Page9

4. Deployment Table Configuration

4.1 Daisyseed table configuration

<All rights reserved. No spreading without permission of ZTE.> Page10

4) Network Configuration table configuration

5) Fill in the Deploy File table.

4.2 TECS silent installation table configuration

Unzip the file.In the/UME_Template.zip file, fill in the following configuration

<All rights reserved. No spreading without permission of ZTE.> Page11

4.3 CloveStorage silent installation table

Unzip the file.In the/UME_Template.zip file, fill in the following configuration

<All rights reserved. No spreading without permission of ZTE.> Page12

4.4 CloveStorage configuration table configuration

Unzip the file./UME_Template.zip file fill in the CloveStorage configuration

4.5 Four tables for one-click deployment of are

<All rights reserved. No spreading without permission of ZTE.> Page13

5. Daisyseed one-click deployment

5.1 Daiyseed software preparation