[LLD_Config]
main_site.default = Primary site
backup_site.default = Secondary site
third_part_site.default = Third-party site
DR_INFO = Primary and Secondary Site
NCE_Node_Site_Name_Config = Primary and Secondary Site Names
NCE_Node_Config_header_siterole = Site Role
NCE_Node_Config_header_login_ip = OMP_01 Login IP Address
NCE_Node_Config_header_set_up_site_name = Site Name
NCE_Node_Config_header_set_up_site_name.remark = The site name contains 1 to 32 characters, including uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
NCE_Node_Config_header_heartbeat_ip = DR Heartbeat IP Address
site_name_error = Incorrect site name format, the site name contains 1 to 32 characters, including uppercase letters, lowercase letters, digits, hyphens (-), and underscores (_).
dr_system_config = DR Parameters
id_replication_direction_select_config = Description, Option, Remarks
replication_direction_select_label.default = Data replication direction
primary_to_secondary = Primary to Secondary
secondary_to_primary = Secondary to Primary
replication_direction_select_remark_1.default = If you select Primary to Secondary, data at the secondary site will be overwritten.
replication_direction_select_remark_2.default = If you select Secondary to Primary, data at the primary site will be overwritten.
automatic_switch_label.default = Automatic switchover
enable = Enabled
disable = Disabled
automatic_switch_select_remark.default = If automatic switchover is enabled, the secondary site takes over services based on the optimal policy when the primary site is faulty.
ARBI_HARDWARE = Third-Party Site Hardware
blade_bmc_pwd_config_taishan2280 = iBMC
id_blade_bmc_pwd_config_taishan2280_01 = iBMC Username
id_blade_bmc_pwd_config_taishan2280_02 = iBMC IP Address
id_blade_bmc_pwd_config_taishan2280_03.remark = The password must be the same as the iBMC password of the server on the live network.
id_blade_bmc_pwd_config_taishan2280_03 = iBMC Password
id_blade_bmc_config_taishan2280 = Server ID, iBMC IP Address, Subnet Mask, Gateway
namespace1.network_plane_config = Network Plane
namespace1.network_plane_config.remark = Bond is a virtual network interface card technology. On the Linux OS, the bond technology is used to form a virtual layer above the NIC driver and below the data link layer. This technology binds IP addresses and MAC addresses of two NICs connected to a switch into one IP address and one MAC address to form a virtual NIC. In VM scenarios, bond does not need to be configured for virtual NICs. In physical machine scenarios, NCE requires that physical NICs be bonded in primary and secondary mode. When one NIC is faulty, services are automatically switched to the other NIC for protection between NICs.
id_network_plane_config = Communication Network, NIC Name, NIC Ports
netcard_login_lab.default = Arbitration Node Login Network
netcard_connnect_lab.default = Arbitration Node Communication Network
netcard_login_lab.remark = Used to log in to the third-party site during arbitration installation and maintenance.
netcard_connnect_lab.remark = Used for communication between the arbitration nodes at the third-party sites and primary/secondary sites after the installation.
netcard_reg_error = Incorrect NIC port format.
netcard_bond_error = Incorrect NIC port format.
netcard_first = Physical NIC Port 1
netcard_second = Physical NIC Port 2
id_node_header = Node Name
id_nic_header = NIC
id_ip_header = IP Address
id_mask_header = Mask
id_destip_header = Destination Network Segment
id_destip_header.remark = Destination network segment: specifies the destination network segment to be configured when you configure a static route. The destination network segment is used to allow hosts on the destination network to connect to VM nodes through the routing table.
id_destmask_header = Destination Mask
id_destmask_header.remark = Destination mask: Subnet mask of the destination network.
id_destgw_header = Gateway IP Address
id_destgw_header.remark = Gateway IP address: Next-hop IP address of the node IP address. The next-hop IP address must be in the same network segment as the node IP address. When configuring the gateway IP address, you must also configure the destination network segment and destination mask. Otherwise, the gateway fails to be configured.
ARBI_SOFTWARE = Arbitration Software
Arbitration_Node_Config = Arbitration Node at the Primary and Secondary Sites
Arbitration_Node_Config_header_siterole = Site Role
Arbitration_Node_Config_header_sitename = Primary and Secondary Site Names
Arbitration_Node_Config_header_sitename.remark = The site name must be the same as that configured in the DR task. The site name contains 1 to 32 characters, including uppercase letters, lowercase letters, digits, underscores (_), and hyphens (-). It cannot start with a hyphen (-).
Arbitration_Node_Config_header_node_name = Node Name
Arbitration_Node_Config_header_communitation_ip = Arbitration Node Communication IP Address
Arbitration_Node_Config_header_communitation_ip.remark = |text1$Enter the DR communication IP address of the management node. |text1$This IP address is recommended in the default planning scenario. Generally, you do not need to change it.
Arbitration_Node_Config_header_root_pwd = root Password
Arbitration_Node_Config_Third = Arbitration Node at the Third-Party Site
Arbitration_Node_Config_header_communitation_ip_third = Arbitration Node Communication IP Address
Arbitration_Node_Config_header_communitation_ip_third.remark = |text1$This IP address must be able to communicate with the communication IP address of the primary and secondary arbitration nodes. |text1$If the third-party site has only one IP address, this IP address can be used as either the communication IP address or the login IP address.
Arbitration_Node_Config_header_login_ip = Arbitration Node Login IP Address
Arbitration_Node_Config_header_login_ip.remark = This IP address is used by the executor where EasySuite resides to access the arbitration node. |text1$The primary and secondary arbitration nodes forward data through the third-party site. |text1$You do not need to set the arbitration node login IP address The arbitration node login IP address of the third-party site must be able to communicate with the executor where EasySuite resides.
Arbitration_Node_Config_header_login_user = Arbitration Node Username
Arbitration_Node_Config_header_login_user.remark = Username for logging in to the arbitration node. If security hardening has been performed, set this parameter to the remote connection user sopuser. If security hardening has not been performed, set this parameter to root.
Arbitration_Node_Config_header_login_pwd = Arbitration Node Password
Arbitration_Node_Config_header_login_pwd.remark = Password for logging in to the arbitration node.
arbitration_site_hardware = Arbitration Node at the Third-Party Site
id_arbitration_site_hardware = Site Role, Node Name, Arbitration Node Communication IP Address, Arbitration Node Login IP Address
node_arbiter_site_name.default = Third-party site
Arbitration_Third_Node_OS_Config = Third-Party Site User Creation
Arbitration_Third_Node_OS_Config_Item = Configuration item
Arbitration_Third_Node_OS_Config_Set = Setting
Arbitration_Third_Node_OS_Config_Extra = Remarks
Arbitration_Third_OS_global_pwd_label.default = Global Password Configuration
Arbitration_Third_OS_global_pwd_extra.default = Automatically fills in the passwords for the sopuser, ossadm, and root users.
Arbitration_Third_OS_sopuser.default = Create sopuser user password
Arbitration_Third_OS_ossadm.default = Create ossadm user password
Arbitration_Third_OS_root.default = Create root user password
os_user_sopuser_extra.default = Common user, which is used to remotely log in to the third-party site in SSH mode. It is automatically created during the installation of the arbitration software at the third-party site. After the arbitration software is installed, use the new password to log in to the third-party site.
os_user_ossadm_extra.default = Common user, which is automatically created during the installation of the arbitration software at the third-party site. After the arbitration software is installed, use the new password to log in to the third-party site.
os_user_root_extra.default = OS administrator who can perform operations on any file, directory, or process.
third_node_sek_select_label.default = Third-party site security hardening
third_node_sek_select_extra.default = After the arbitration software is installed, the root user cannot be used for remote connection. For the Kylin OS that does not support security hardening, set this parameter to No. For other OSs, set this parameter to Yes.
third_node_sek_select_yes = Yes
third_node_sek_select_no = No
third_node_sek_select_increment_install_extra.default = If the security hardening software is of a higher version, security hardening will be performed again.
node_os_tzone_label.default = Third-party site OS time zone
Arbitration_Third_Node_NTP_Config = NTP Server at the Third-Party Site
NTP_Config_header_label = IP Address Type
NTP_Config_header_value = IP Address
NTP_Config_header_Extra = Remarks
netcard_internal_lab_1.default = IP address of the active external clock source
netcard_internal_lab_2.default = IP address of the standby external clock source
netcard_internal_lab_2.remark = If only one external clock source is available, the IP address of the standby external clock source must be the same as that of the active external clock source.
netcard_internal_lab_3.default = IP address of the active NTP server
netcard_internal_lab_4.default = IP address of the standby NTP server
primary_ntp_config_extra.default = You are advised to enter the IP address of the management node at the primary site that can communicate with the third-party site to trace the time at the primary site. If an independent NTP server is deployed, you can also trace the external clock source.
secondary_ntp_config_extra.default = You are advised to enter the IP address of the management node at the secondary site that can communicate with the third-party site to trace the time at the secondary site when the primary site is faulty. If an independent NTP server is deployed, you can also trace the external clock source.

