(Optional) Commissioning the Driver

Prerequisites

• You have obtained the information listed in Table 5-2.
  Table 5-2 eSight information

  Item	Subitem
  eSight	System IP address of the active server
  	Password of the ossuser user on the active server. 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). To improve system security and prevent security risks (such as violent password cracking), change the initial password promptly and change the user password periodically (for example, every six months).
  	System IP address of the standby server
  	Password of the ossuser user on the standby server. 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). To improve system security and prevent security risks (such as violent password cracking), change the initial password promptly and change the user password periodically (for example, every six months).
  	Floating IP address of the active and standby servers if eSight is deployed in a local OMMHA system

• You have obtained the information listed in Table 5-3.
  Table 5-3 CloudOpera information

  Item	Subitem	Example Value
  BackendERService microservice on the O&M plane NOTE: In the Huawei Cloud scenario, collect the floating IP address of the LB to which CloudDriverService belongs. The BackendERService microservice belongs to the HRS service. The processes of the HRS service include backenderservice. In the multi-region deployment scenario, collect information about BackendERService on the O&M plane in the region where eSight is connected. In other scenarios, collect information about BackendERService on the O&M plane in the global region.	IP address NOTE: If BackendERService is deployed in a cluster (multiple nodes), collect the floating IP address of BackendERService. If BackendERService is deployed on a single node, collect the management IP address of the node.	192.168.10.12
  	Port number. The default value is 26330.	26330
  RESTConnectorService microservice on the O&M plane NOTE: In the Huawei Cloud scenario, collect the floating IP address of the LB to which CloudDriverService belongs. The RESTConnectorService microservice belongs to the DrvFrm service. The processes of the DrvFrm service include restconnectorservice. In the multi-region deployment scenario, collect information about RESTConnectorService in the region where eSight is connected. In other scenarios, collect information about RESTConnectorService in the global region.	Management IP addresses	192.168.10.13 192.168.10.14
  	Floating IP address NOTE: If RESTConnectorService is deployed on a single node, the floating IP address does not need to be collected.	10.10.10.13

• You have obtained the server.p12 and trust.jks certificates of BackendERService on the CloudOpera O&M plane.

  In the Huawei Cloud scenario, obtain the server.p12 and trust.jks certificates on any node where CloudDriverService is deployed.

• You have disabled CN verification for BackendERService on the CloudOpera O&M plane.

  In the Huawei Cloud scenario, disable CN verification for CloudDriverService.

Procedure

1. Copy the server.p12 and trust.jks files to the active eSight server and change the file permission.
   1. Use FileZilla to log in to the active eSight server as the ossuser user.
   2. Upload the server.p12 and trust.jks files to /opt/eSight/AppBase/etc/ies on the active eSight server.
   3. Use PuTTY to log in to the active eSight server as the ossuser user.
   4. Run the following commands to change the file permission:

      cd /opt/eSight/AppBase/etc/ies

      chmod 600 *

2. Perform the following operations to modify the parameters for interconnection with CloudOpera in the configuration file:
   1. Run the following commands to modify the parameters:

      cd /opt/eSight/AppBase/tools

      ./modifyConfig.sh

      Information similar to the following is displayed:

      No    Key                     Value
      1     ER_IP                   
      2     ER_port                 
      3     PmdataNotToDB           false
      4     Performance_Select      true
      5     Alarm_Select            true
      6     ApiGateway_Host_IP      
      7     ApiGateway_Host_Port    
      8     ApiGateway_StandBy_IP   
      9     ApiGateway_StandBy_Port 
      10    ApiGateway_Retry_Times  
      11    eSight_Token_Name       
      12    eSight_Token_Value      
      13    ApiGateway_Token_Time   
      14    KeyStorePath            /opt/eSight/AppBase/etc/ies/server.p12
      15    KeyStorePwd             Encrypted initial certificate password
      16    TrustStorePath          /opt/eSight/AppBase/etc/ies/trust.jks
      17    TrustStorePwd           Encrypted initial certificate password
      Please input the number of key(q to quit):

   2. Repeat the following operations to set the parameters listed in Table 5-4:
      1. Enter the SN of the parameter to be modified. For example, enter 1 and press Enter. The following information is displayed:

         Please input the value of ER_IP(q to cancel):

      2. Enter the new parameter value and press Enter.

         If the value is displayed in the Value column corresponding to the parameter, the parameter is modified successfully.

      Table 5-4 Parameter description

      Parameter	Description	Example Value
      ER_IP	Mandatory. Floating IP address of BackendERService on the O&M plane. For details, see Table 5-3.	192.168.10.12
      ER_port	Mandatory. Port number of BackendERService on the O&M plane. For details, see Table 5-3.	26330
      PmdataNotToDB	Optional. Whether to save performance data collected by eSight to the eSight database. If this parameter is set to true, you can view historical performance data on the eSight client. Otherwise, you can view only real-time performance data on the eSight client. false (default value): Performance data is saved to the eSight database. true: Performance data is not saved to the eSight database.	false
      Performance_Select	Optional. Whether to report performance data collected by eSight to the CloudOpera O&M plane. If this parameter is set to true, services on the CloudOpera O&M plane can obtain resource performance data reported by eSight. true (default value): Performance data is reported. false: Performance data is not reported.	true
      Alarm_Select	Optional. Whether to report alarms collected by the eSight Driver component to the CloudOpera O&M plane. If this parameter is set to true, you can view alarms reported by eSight on the CloudOpera O&M plane. true (default value): Alarms are reported. false: Alarms are not reported.	true

   3. Enter q to save the modification and exit.

3. Modify the configuration file to remove the restriction on the number of times for invoking open APIs.
   1. Run the following commands to modify the roa.properties file:

      cd /opt/eSight/AppBase/etc/iemp.framework

      vi roa.properties

   2. Press I to enter the editing mode.
   3. Add the iemp.roa.access.rate.limit.enable parameter and set it to false.

      iemp.roa.access.rate.limit.enable=false

   4. Press Esc to exit the editing mode, and run the :wq command to save the file and exit.

4. Restart eSight for the settings to take effect. For details, see How Do I Restart the eSight System.

   If this is the first eSight system connected to CloudOpera, eSight is displayed in System Type on the System Access page of CloudOpera after the configuration is complete.

5. Configure CloudOpera information on eSight.
   1. Log in to the eSight client as the admin user.
      Open a browser, enter https://eSight IP address:31943 in the address box, and press Enter.

      eSight IP address: If eSight is deployed in a local HA system, the IP address is the eSight floating IP address. If eSight is deployed in a remote HA system, the IP address is the system IP address of the active eSight server.

   2. Choose System > System Settings > Northbound Integration from the main menu.
   3. In the navigation pane, choose Third-party System Settings.
   4. Click Create and configure third-party system information.
      • IP address: Management IP addresses and floating IP address of the active and standby nodes where RESTConnectorService is deployed on the CloudOpera O&M plane. Only one IP address can be configured at a time. Therefore, you need to create third-party system information for each IP address.
        • If RESTConnectorService is deployed on a single node, configure only the management IP address of the node where RESTConnectorService is deployed.
        • In the Huawei Cloud scenario, configure the floating IP address of the LB to which CloudDriverService belongs.
      • Protocol type: Select HTTPS.
      • System ID: Retain the default value.
   5. Click OK.

Prerequisites

• You have obtained the system IP address of the active eSight server.
• You have obtained the password of the ossuser user of the active eSight server.
• If eSight is deployed in a local OMMHA system, you have obtained the floating IP address of the active and standby servers.

Procedure

1. (Optional) Download the eSight certificate. If the default trust certificate of Huawei is preconfigured on CloudOpera, you do not need to download the eSight certificate.

   eSight provides a temporary certificate. You are advised to replace the temporary certificate with a certificate applied from the Certificate Authority (CA). To replace the temporary certificate, see "Operation and Maintenance > Maintenance Guide > Security Maintenance > Security Certificates > Replacing the Business Certificate > Updating the Preset PKI Certificate of eSight" in the eSight Product Documentation. Then, export the CA certificate matching the new certificate and import into CloudOpera for interconnecting with eSight.

   1. Use FileZilla to remotely log in to the active eSight server as the ossuser user.
   2. Download the eSight certificate file huaweica.der from the /opt/eSight/mttools/etc/certificate/pki directory to the local PC and rename it huaweica.crt.

2. (Optional) Upload the eSight certificate to CloudOpera. If the default trust certificate of Huawei is preconfigured on CloudOpera, you do not need to upload the eSight certificate.
   1. Choose System > System Settings > System Access from the main menu.

      The menus vary depending on CloudOpera. For example, in the public cloud scenario, choose Services > Monitor and Fault Handling > Cloud Monitor Alarm from the main menu.

   2. In the navigation pane, choose Certificate Management > Trust Certificates.

      The menus vary depending on CloudOpera. For example, in the public cloud scenario, choose Alarm Data Source Settings > Trust Certificate from the navigation pane.

   3. Click Upload.
   4. Select Driver for Service Name, click File Name, and select the eSight certificate file obtained in 1.

      The GUI varies depending on CloudOpera. For example, in the public cloud scenario, Service name is not displayed. Click the File Name input box and select the file.

   5. Click Submit to import the eSight certificate file to CloudOpera.

      If the system displays a message, indicating that the certificate exists, you do not need to import the eSight certificate again.

3. Connect CloudOpera to eSight.
   1. Choose System > System Settings > System Access from the main menu.

      The menus vary depending on CloudOpera. For example, in the public cloud scenario, choose Services > Monitor and Fault Handling > Cloud Monitor Alarm from the main menu.

   2. Click eSight and then Create. Set the parameters based on Table 5-5.
      • The GUI varies depending on CloudOpera. For example, in the public cloud scenario, click Create an instance, set System type to eSight, and set the parameters based on Table 5-5.
      • Table 5-5 only describes the basic parameters that need to be set.
      Table 5-5 Basic parameters

      Parameter	Description	Example Value
      System name	Name of eSight that interconnects with CloudOpera.	eSight
      Version	Version of eSight that interconnects with CloudOpera. Set this parameter to v1.	v1
      IP address/Domain name	If eSight is deployed in a local OMMHA system, set this parameter to the floating IP address of the eSight system. If eSight is deployed in a remote OMMHA system, set this parameter to the IP address of the active eSight server.	192.168.8.9
      Driver name	Driver type of eSight that interconnects with CloudOpera. Set this parameter to plugin_driver_hw_esight.	plugin_driver_hw_esight
      Deploy zone	Region of eSight that interconnects with CloudOpera.	Global
      Logical position	Logical position of eSight. Set this parameter to the logical position of the eSight node planned on CloudOpera. If the logical position of the eSight node is not planned, this parameter does not need to be set. NOTE: Only one eSight system can be created at one logical position. If multiple eSight systems are interconnected at the same logical location, services are abnormal.	North of China
      Standby IP address	In the dual-DC cold backup DR scenario, set this parameter to the system IP address of the standby eSight server when eSight is deployed in a remote OMMHA system. This parameter does not need to be set in other scenarios.	192.168.8.12
      Active/Standby switchover policy	Whether to enable active/standby switchover. In the dual-DC cold backup DR scenario, set this parameter to Enable when eSight is deployed in a remote OMMHA system. This parameter does not need to be set in other scenarios.	Enable

   3. Click Next and set parameters described in Table 5-6.
      Table 5-6 Protocol parameters

      Parameter	Description
      User Name	eSight user that interacts with the CloudOpera driver framework service. Set this parameter to eSight.
      Encryption Algorithm	Abstract encryption algorithm of eSight. Set this parameter to SHA-256.
      Password	Password for the eSight user that interacts with the CloudOpera driver framework service. 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).

   4. Click OK to connect eSight.
      • If eSight is interconnected successfully, the connection status is displayed as .
      • If the interconnection fails, check the failure causes according to the error information. Click to modify the parameter settings. After the modification is complete, click to test the connectivity.

        If the test succeeds, the interconnection is successful.

        If the test fails, perform the following steps to delete the eSight system and create an access system again. If the interconnection still fails, contact Huawei technical support.

        1. Click to delete the eSight system.

           If the operation fails, contact Huawei technical support.

        2. (Optional) Delete the eSight trust certificate. If the default trust certificate of Huawei is preconfigured on CloudOpera, you do not need to delete the certificate.
           1. Choose Certificate Management > Trust Certificate to view the trust certificate list.
           2. Click to delete the trust certificate that includes eSight in the Issued By column.

Prerequisites

Log in to the CloudOpera O&M plane as the admin user.

Procedure

1. Create the drivermgr role.
   1. Choose Security > User Management from the main menu.
   2. Select Roles in the navigation tree on the left and click Create.
   3. Set the role name to drivermgr, and click Next.
   4. Click Next.
   5. Click to expand the application-level operation permissions panel, and find the System Access and Driver Management permissions, select the following permissions:
      • Select System Access Query permission in the System Access.
      • Select Configuration Management and DriverInstance Management permissions in the Driver Management.

        For different versions of CloudOpera, the Driver Management name may not be consistent. If the Driver Management does not exist, select Driver LifeCycle Management.

   6. Use default values for other parameters, and click Finish.

      If the created role is displayed in the role list, the role is created successfully.

2. Create the eSight user for interacting with the ApiGateway.
   1. Select Users in the navigation tree on the left and click Create.
   2. Configure basic information about the user and click Next.

      Configuration item	Configuration Description
      User name	Set the user name as prompted, but cannot be eSight.
      Password	Set the password as prompted, for example, Examples123.
      Type	Set the type to Third-party system access.
      Advanced Settings	If the option Change the password at the first login is in the advanced settings, ensure that this option is not selected.

   3. Select the following roles and click Next:
      • NBI User Group/APIManager
      • The role to invoke southbound APIs
      • drivermgr

      For different versions of CloudOpera, the role name may not be consistent.

      • NBI User Group/APIManager: If NBI User Group and APIManager both exist, select APIManager.
      • The role to invoke southbound APIs: If The role to invoke southbound APIs does not exist, select southapis.roles.operation.
   4. Click Finish.

Prerequisites

• You have obtained the information listed in Table 5-7.
  Table 5-7 eSight information

  Item	Subitem
  eSight	System IP address of the active server
  	Password of the ossuser user on the active server. 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). To improve system security and prevent security risks (such as violent password cracking), change the initial password promptly and change the user password periodically (for example, every six months).
  	System IP address of the standby server
  	Password of the ossuser user on the standby server. 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). To improve system security and prevent security risks (such as violent password cracking), change the initial password promptly and change the user password periodically (for example, every six months).
  	Floating IP address of the active and standby servers if eSight is deployed in a local OMMHA system

• You have obtained the information listed in Table 5-8.
  Table 5-8 CloudOpera information

  Item	Subitem	Example Value
  APIMLBService microservice on the O&M plane NOTE: In the multi-region deployment scenario, collect information about APIMLBService in the region where eSight is connected. In other scenarios, collect information about APIMLBService in the global region. If two DCs are deployed in cold standby mode, collect information about APIMLBService in the active and standby DCs. The APIMLBService microservice belongs to the MinApiMgr or ApiMgr service. The processes of the MinApiMgr or ApiMgr service include apimlb.	Floating IP address	192.168.10.12
  	Port number. The default value is 26335.	26335
  RestConnectorService microservice on the O&M plane NOTE: In the CloudOpera Orchestrator CloudVPN scenario, collect the southbound client IP addresses of the nodes where DriverFrameworkService is deployed. In the multi-region deployment scenario, collect information about RestConnectorService in the region where eSight is connected. In other scenarios, collect information about RestConnectorService in the global region. If two DCs are deployed in cold standby mode, collect information about RestConnectorService in the active and standby DCs. The RestConnectorService microservice belongs to the DrvFrm service. The processes of the DrvFrm service include restconnectorservice.	Management IP addresses	192.168.10.13 192.168.10.14
  	Floating IP address NOTE: If RestConnectorService is deployed on a single node, the floating IP address does not need to be collected.	10.10.10.13

• You have obtained the trust.jks trust certificate of APIMLBService on the CloudOpera O&M plane and the certificate password.

Procedure

1. Upload the trust.jks certificate of APIMLBService on the O&M plane to the active eSight server.
   1. Use FileZilla to log in to the active eSight server as the ossuser user.
   2. Upload the trust.jks certificate to /opt/eSight/AppBase/etc/ies on the active eSight server.
   3. Use PuTTY to log in to the active eSight server as the ossuser user.
   4. Run the following commands to change the file permission:

      cd /opt/eSight/AppBase/etc/ies

      chmod 600 *

2. Perform the following operations to modify the parameters for interconnection with CloudOpera in the configuration file:
   1. Run the following commands to open the config.properties file:

      cd /opt/eSight/AppBase/etc/ies

      vi config.properties

   2. Press I to enter the editing mode.
   3. Modify the following parameters based on Table 5-9:

      ApiGateway_Host_IP=
      ApiGateway_Host_Port=
      ApiGateway_StandBy_IP=
      ApiGateway_StandBy_Port=
      ApiGateway_Retry_Times=
      eSight_Token_Name=
      eSight_Token_Value=
      ApiGateway_Token_Time=
      TrustStorePwd=
      PmdataNotToDB=
      Performance_Select=
      Alarm_Select=

      Table 5-9 Parameter description

      Parameter	Description	Example Value
      ApiGateway_Host_IP	Mandatory. Floating IP address of APIMLBService. For details, see Table 5-8. NOTE: If two DCs are deployed in cold standby mode, set this parameter to the floating IP address of APIMLBService in the active DC.	192.168.10.12
      ApiGateway_Host_Port	Mandatory. Port number of APIMLBService. For details, see Table 5-8. The default port number is 26335. NOTE: If two DCs are deployed in cold standby mode, set this parameter to the port number of APIMLBService in the active DC.	26335
      ApiGateway_StandBy_IP	Optional. If two DCs are deployed in cold standby mode, set this parameter to the floating IP address of APIMLBService in the standby DC. This parameter does not need to be set in other scenarios.	192.168.10.13
      ApiGateway_StandBy_Port	Optional. If two DCs are deployed in cold standby mode, set this parameter to the port number of APIMLBService in the standby DC. The default port number is 26335. This parameter does not need to be set in other scenarios.	26335
      ApiGateway_Retry_Times	Mandatory. Set this parameter to 3.	3
      eSight_Token_Name	Mandatory. User name created in Creating User for Interacting with the ApiGateway in CloudOpera.	eSightAPI
      eSight_Token_Value	Mandatory. Run the following commands to use the encryption tool to encrypt the user password created in Creating User for Interacting with the ApiGateway in CloudOpera: cd /opt/eSight/AppBase/tools/bmetool/encrypt ./encrypt.sh 0 Enter the password to be encrypted twice as prompted. The encrypted password is displayed. Set this parameter to the encrypted password.	-
      ApiGateway_Token_Time	Optional. Request timeout interval, in minutes. The value is an integer greater than 0 and less than or equal to 600. If this parameter is left empty, the default interval is 10 minutes.	10
      TrustStorePwd	Mandatory. Run the following commands to use the encryption tool to encrypt the password of the trust.jks certificate of APIMLBService on the O&M plane: cd /opt/eSight/AppBase/tools/bmetool/encrypt ./encrypt.sh 0 Enter the password to be encrypted twice as prompted. The encrypted password is displayed. Set this parameter to the encrypted password.	-
      PmdataNotToDB	Optional. Whether to save performance data collected by eSight to the eSight database. If this parameter is set to true, you can view historical performance data on the eSight client. Otherwise, you can view only real-time performance data on the eSight client. false (default value): Performance data is saved to the eSight database. true: Performance data is not saved to the eSight database.	false
      Performance_Select	Optional. Whether to report performance data collected by eSight to the CloudOpera O&M plane. If this parameter is set to true, services of the CloudOpera O&M plane can obtain resource performance data reported by eSight. true (default value): Performance data is reported. false: Performance data is not reported.	true
      Alarm_Select	Optional. Whether to report eSight alarms to the CloudOpera O&M plane. If this parameter is set to true, you can view alarms reported by eSight on the CloudOpera O&M plane. true (default value): Alarms are reported. false: Alarms are not reported.	true

   4. Press Esc to exit the editing mode, and run the :wq command to save the file and exit.

3. Modify the configuration file to remove the restriction on the number of times for invoking open APIs.
   1. Run the following commands to modify the roa.properties file:

      cd /opt/eSight/AppBase/etc/iemp.framework

      vi roa.properties

   2. Press I to enter the editing mode.
   3. Add the iemp.roa.access.rate.limit.enable parameter and set it to false.

      iemp.roa.access.rate.limit.enable=false

   4. Press Esc to exit the editing mode, and run the :wq command to save the file and exit.

4. Restart eSight for the settings to take effect. For details, see How Do I Restart the eSight System.

   If this is the first eSight system connected to CloudOpera, eSight is displayed in System Type on the System Access page of CloudOpera after the configuration is complete.

5. Configure CloudOpera information on eSight.
   1. Log in to the eSight client as the admin user.
      Open a browser, enter https://eSight IP address:31943 in the address box, and press Enter.

      eSight IP address: If eSight is deployed in a local HA system, the IP address is the eSight floating IP address. If eSight is deployed in a remote HA system, the IP address is the system IP address of the active eSight server.

   2. Choose System > System Settings > Northbound Integration from the main menu.
   3. In the navigation pane, choose Third-party System Settings.
   4. Click Create and configure third-party system information.
      • IP address: Management IP addresses and floating IP address of the nodes where RESTConnectorService is deployed on the CloudOpera O&M plane. Only one IP address can be configured at a time. Therefore, you need to create third-party system information for each IP address.
        • In the CloudOpera Orchestrator CloudVPN scenario, configure the southbound client IP addresses of the nodes where DriverFrameworkService is deployed.
        • If RESTConnectorService is deployed on a single node, configure only the management IP address of the node where RESTConnectorService is deployed.
        • If two DCs are deployed in cold standby mode, configure the management IP addresses and floating IP address of the nodes where RESTConnectorService is deployed in both the active and standby DCs.
      • Protocol type: Select HTTPS.
      • System ID: Retain the default value.
   5. Click OK.

Prerequisites

• You have obtained the system IP address of the active eSight server.
• You have obtained the ossuser password of the active eSight server.
• If the eSight is deployed in local OMMHA two-node cluster, you have to obtain the floating IP address of eSight servers.

Procedure

1. (Optional) Download the eSight certificate. If the default trust certificate of Huawei is preconfigured on CloudOpera, you do not need to download the eSight certificate.

   eSight provides a temporary certificate. You are advised to replace the temporary certificate with a certificate applied from the Certificate Authority (CA). To replace the temporary certificate, see "Operation and Maintenance > Maintenance Guide > Security Maintenance > Security Certificates > Replacing the Business Certificate > Updating the Preset PKI Certificate of eSight" in the eSight Product Documentation. Then, export the CA certificate matching the new certificate and import into CloudOpera for interconnecting with eSight.

   1. Use FileZilla to remotely log in to the active eSight server as the ossuser user.
   2. Download the eSight certificate file huaweica.der from the /opt/eSight/mttools/etc/certificate/pki directory to the local PC and rename it huaweica.crt.

2. (Optional) Upload the eSight certificate to CloudOpera. If the default trust certificate of Huawei is preconfigured on CloudOpera, you do not need to upload the eSight certificate.
   1. Choose System > System Settings > System Access from the main menu.

      The menus vary depending on CloudOpera. For example, in the public cloud scenario, choose Services > Monitor and Fault Handling > Cloud Monitor Alarm from the main menu.

   2. In the navigation pane, choose Certificate Management > Trust Certificates.

      The menus vary depending on CloudOpera. For example, in the public cloud scenario, choose Alarm Data Source Settings > Trust Certificate from the navigation pane.

   3. Click Upload.
   4. Select Driver for Service Name, click File Name, and select the eSight certificate file obtained in 1.

      The GUI varies depending on CloudOpera. For example, in the public cloud scenario, Service name is not displayed. Click the File Name input box and select the file.

   5. Click Submit to import the eSight certificate file to CloudOpera.

      If the system displays a message, indicating that the certificate exists, you do not need to import the eSight certificate again.

3. Connect CloudOpera to eSight.
   1. Choose System > System Settings > System Access from the main menu.

      The menus vary depending on CloudOpera. For example, in the public cloud scenario, choose Services > Monitor and Fault Handling > Cloud Monitor Alarm from the main menu.

   2. Click eSight and then Create. Set the parameters based on Table 5-10.
      • The GUI varies depending on CloudOpera. For example, in the public cloud scenario, click Create an instance, set System type to eSight, and set the parameters based on Table 5-10.
      • Table 5-10 only describes the basic parameters that need to be set.
      Table 5-10 Basic parameters

      Parameter	Description	Example Value
      System name	Name of eSight that interconnects with CloudOpera.	eSight
      Version	Version of eSight that interconnects with CloudOpera. Set this parameter to v1.	v1
      IP address/Domain name	If eSight is deployed in a local OMMHA system, set this parameter to the floating IP address of the eSight system. If eSight is deployed in a remote OMMHA system, set this parameter to the IP address of the active eSight server.	192.168.8.9
      Driver name	Driver type of eSight that interconnects with CloudOpera. Set this parameter to plugin_driver_hw_esight.	plugin_driver_hw_esight
      Deploy zone	Region of eSight that interconnects with CloudOpera.	Global
      Logical position	Logical position of eSight. Set this parameter to the logical position of the eSight node planned on CloudOpera. If the logical position of the eSight node is not planned, this parameter does not need to be set. NOTE: Only one eSight system can be created at one logical position. If multiple eSight systems are interconnected at the same logical location, services are abnormal.	North of China
      Standby IP address	In the dual-DC cold backup DR scenario, set this parameter to the system IP address of the standby eSight server when eSight is deployed in a remote OMMHA system. This parameter does not need to be set in other scenarios.	192.168.8.12
      Active/Standby switchover policy	Whether to enable active/standby switchover. In the dual-DC cold backup DR scenario, set this parameter to Enable when eSight is deployed in a remote OMMHA system. This parameter does not need to be set in other scenarios.	Enable

   3. Click Next and set parameters described in Table 5-11.
      Table 5-11 Protocol parameters

      Parameter	Description
      User Name	eSight user that interacts with the CloudOpera driver framework service. Set this parameter to eSight.
      Encryption Algorithm	Abstract encryption algorithm of eSight. Set this parameter to SHA-256.
      Password	Password for the eSight user that interacts with the CloudOpera driver framework service. 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).

   4. Click OK to connect eSight.
      • If eSight is interconnected successfully, the connection status is displayed as .
      • If the interconnection fails, check the failure causes according to the error information. Click to modify the parameter settings. After the modification is complete, click to test the connectivity.

        If the test succeeds, the interconnection is successful.

        If the test fails, perform the following steps to delete the eSight system and create an access system again. If the interconnection still fails, contact Huawei technical support.

        1. Click to delete the eSight system.

           If the operation fails, contact Huawei technical support.

        2. (Optional) Delete the eSight trust certificate. If the default trust certificate of Huawei is preconfigured on CloudOpera, you do not need to delete the certificate.
           1. Choose Certificate Management > Trust Certificate to view the trust certificate list.
           2. Click to delete the trust certificate that includes eSight in the Issued By column.

Symptom

How do I restart the eSight system?

Solution

1. Stop the eSight system.
   1. Log in to the standby eSight server as the ossuser user.
   2. Run the following commands to stop the eSight system:

      cd /opt/ommha/ha/bin

      ./stop.sh

      The following information indicates that the operation is performed successfully:

      stop HA successfully.

   3. Log in to the active eSight server as the ossuser user.
   4. Run the following commands to stop the eSight system:

      cd /opt/ommha/ha/bin

      ./stop.sh

      The following information indicates that the operation is performed successfully:

      stop HA successfully.

2. Start the eSight system.
   1. Log in to the active eSight server as the ossuser user.
   2. Run the following commands to start the eSight system:

      cd /opt/ommha/ha/bin

      ./start.sh

      The following information indicates that the operation is performed successfully:

      start HA successfully.

   3. Log in to the standby eSight server as the ossuser user.
   4. Run the following commands to start the eSight system:

      cd /opt/ommha/ha/bin

      ./start.sh

      The following information indicates that the operation is performed successfully:

      start HA successfully.

Question

What can I do if the eSight resource data cannot be reported to the third-party system after the IT component is incrementally installed?

Answer

If the IT component is incrementally installed after eSight is installed, you need to execute the changeDriver4IT.sh script on the active eSight server. Otherwise, eSight resource data cannot be reported to the third-party system CloudOpera. The changeDriver4IT.sh script checks whether to delete the configuration file global.datasource.xml based on whether the eSight IT component is installed, ensuring that the eSight resource data can be properly reported to the CloudOpera.

1. Use PuTTY to log in to the active eSight server as the ossuser user.

2. Execute the changeDriver4IT.sh script.

   cd /opt/eSight/AppBase/tools

   sh changeDriver4IT.sh

   If the following information is displayed when the changeDriver4IT.sh script is executed the first time, the execution is successful. If the script is not executed the first time, only the information "succeeded!" is displayed.

   deleting: META-INF/spring/global.datasource.xml 
   succeed!