Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document.
Note: Even the most advanced machine translation cannot match the quality of professional translators.
Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Common Operations
- Common SUSE Linux Operations
This section describes common operations performed on a SUSE Linux-based workstation. After learning this topic, you can improve the efficiency of the operations on the SUSE Linux OS. - Checking the Status of Two-Node Cluster Resources
This section describes how to check the status of two-node cluster resources. - Disabling Active/Standby Switchover
This command is used to disable the automatic active/standby switchover of the OMMHA. - Stopping eSight
To stop eSight, you must run the stop command on both the active and standby servers. eSight is successfully stopped only when both the active and standby servers are stopped. The stopping process takes about 5 minutes. - Starting eSight
To start eSight, you need to run the start command on both the active and standby servers. eSight can be started successfully when both active and standby servers are started successfully and the status of eSight two-node cluster resources is normal. The starting process takes about 10 minutes. - Restoring Active/Standby Switchover
This section describes how to restore the active/standby switchover function. - Manually Performing Active/Standby Switchover
You can manually switch the standby server to the active server and the original active server to the new standby server, implementing system reliability test or system maintenance. - Running the Fault Clearing Tool
If the NMSServer resource is faulty on the active server, the status of the NMSServer resource is displayed as exception. In this case, the active server becomes the standby server. You need to use the fault clearing tool to clear the status. Otherwise, the standby server cannot become the active server again. - Uninstalling eSight
If eSight is not used any more, installation personnel can uninstall eSight from the active and standby eSight servers using the service deployment system. - Starting the Maintenance Tool
This section describes how to start the eSight maintenance tool. - What Do I Do If eSight Displays a Security Certificate Error During Login
- Configuring the TLS Protocol Version for eSight
- Obtaining the IP Addresses of the Physical Machines Where VMs Are Located
This section describes how to obtain the IP addresses of the physical machines where VMs are located. - Checking and Disabling the Drive Cache of eSight Physical Machines
Before the installation, you need to check and disable the drive cache of all eSight physical machines, to prevent GaussDB from failing to be started after abnormal server power-off or shutdown and therefore ensure proper eSight startup.