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).
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.
Procedure
- Log in to the active eSight server as the ossuser user. For the preset password, see the eSight User List released with the version (Support: https://support.huawei.com/carrier/docview!docview?nid=DOC1100890341; Support-E: https://support.huawei.com/enterprise/en/doc/EDOC1100227876).
- Run the following commands to start the eSight system:
cd /opt/ommha/ha/bin
./start.sh
If the following information is displayed, the operation is successful:
start HA successfully.
- Log in to the standby eSight server as the ossuser user.
- Run the following commands to start the eSight system:
cd /opt/ommha/ha/bin
./start.sh
If the following information is displayed, the operation is successful:
start HA successfully.
- Check whether the status of the two-node cluster is normal. If yes, eSight is started successfully. Otherwise, contact Huawei technical support.
- Log in to the active eSight server as the ossuser user.
- Run the following commands to check the status of the two-node cluster resources:
cd /opt/ommha/ha/bin
./status.sh
If information similar to the following is displayed, the status is normal:
HAMode double NodeName HostName HAVersion StartTime HAActive HAAllResOK HARunPhase ha1 Primaster V100R001C01 2017-02-22 16:44:01 active normal Actived ha2 Secmaster V100R001C01 2017-02-22 16:46:45 standby normal Deactived NodeName ResName ResStatus ResHAStatus ResType ha1 Database Active_normal Normal Active_standby ha1 NMSServer Normal Normal Single_active ha2 Database Standby_normal Normal Active_standby ha2 NMSServer Stopped Unknown Single_active