No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

eSight V300R010C00 Maintenance Guide 07

Rate and give feedback:
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).
Engineering

Engineering

Certificate Tool

This command is used only to import a CA certificate or generate a self-signed certificate. In a local HA system, you need to perform the operations only on the active server. The standby server automatically synchronizes data from the active server. In a remote HA system, you need to perform the operations on both the active and standby servers.

Syntax

SUSE Linux operating system: catool.sh

Euler and SUSE Linux operating systems: es_cli -cmd catool

Path

catool.sh: eSight installation directory/mttools/tools

es_cli -cmd catool: any directory

Prerequisites

The eSight service has been stopped.

The command is executed by the ossuser user in the Linux operating system.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Configure the certificate.
    • Configuration through a graphical tool (applicable only to the SUSE Linux operating system)

      cd eSight installation directory/mttools/tools

      ./catool.sh

      After the command is successfully executed, the operation UI is displayed.

    • Configuration through commands (applicable to the SUSE Linux and Euler operating systems)

      es_cli -cmd catool

      Configure information as prompted.

Control Console Startup Tool

The command starts the control console.

Syntax

Windows OS: run.bat

Path

eSight installation directory/bin

Prerequisites

The database has been started.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the Administrator user.
    NOTE:

    If security hardening has been completed for the Windows operating system, log in to the server as an SWMaster user.

  2. Run the following command to switch the directory:

    cd eSight installation directory/bin

  3. Run the following command to start the control console.

    run.bat

    After the command is successfully executed, the console operation UI is displayed.

HA Configuration Tool (Veritas)

The command is used to modify the HA configuration on the SUSE Linux operating system.

Syntax

Linux operating system: hacheck.sh

Path

eSight installation directory/mttools/tools

Prerequisites

The eSight service has been stopped.

The active and standby servers have been disconnected. If the active and standby servers are not disconnected, follow instructions in Disconnecting the Active and Standby Servers to disconnect them.

The mountFileRes resource is online.

The FloatIP resource is offline when you modify the system IP address of a local two-node cluster.

Precautions

After the configuration is complete, the network service of the operating system will be restarted. If the configuration is not performed on the management port, the connection may be interrupted after the network service is restarted. Use the new IP address to log in to the Linux server.

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Stop the maintenance tool process on the server.

    #cd /opt/eSight/mttools/bin

    #./stop-sysmon.sh

  3. Run the following command to switch the directory:

    cd eSight installation directory/mttools/tools

  4. Run the following command to start the HA configuration tool:

    ./hacheck.sh

    After the command is successfully executed, the operation UI is displayed.

Multi-subnet Configuration Tool

The command starts the multi-subnet configuration tool in the Linux operating system. In a HA system, you need to perform the operations on both the active and standby servers.

Syntax

SUSE Linux operating system: multi-subnetwork.sh

EulerOS and SUSE Linux operating systems: es_cli -cmd multisubnet

Path

multi-subnetwork.sh: eSight installation directory/mttools/tools

es_cli -cmd multisubnet: any path

Prerequisites

The eSight service has been stopped.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the ossuser user.
  2. Configure multi-subnet management.
    • Configuration through a graphical tool (applicable only to the SUSE Linux operating system)
      1. Run the following command to switch the directory:

        cd eSight installation directory/mttools/tools

      2. Run the following command to start the multi-subnet configuration tool:

        ./multi-subnetwork.sh

        After the command is successfully executed, the operation UI is displayed.

    • Configuration through commands (applicable to the SUSE Linux and EulerOS operating systems)

      es_cli -cmd multisubnet

      Configure information as prompted.

IP Address Change Tool

This command is used only to start the system IP configuration tool in a single-node system.

Syntax

SUSE Linux operating system: ipchange.sh

Euler and SUSE Linux operating systems: es_cli -cmd ipchange

Path

ipchange.sh: eSight installation directory/mttools/tools

es_cli -cmd ipchange: any directory

Prerequisites

The database has been started.

The eSight service has been stopped.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    cd eSight installation directory/mttools/tools

  3. Change the IP address.
    • Change the IP address using a graphical tool. This method is applicable only to the SUSE Linux operating system.

      cd eSight installation directory/mttools/tools

      ./ipchange.sh

    • Change the IP address using commands. This method is applicable to the SUSE Linux and Euler operating systems.

      es_cli -cmd ipchange

      Configure information as prompted.

eSight Directory Permission Modification Tool

The command modifies the eSight directory permission.

Syntax

Windows OS: caclsUser.bat

Path

eSight installation directory/mttools/tools

Prerequisites

The database has been started.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the Administrator user.
    NOTE:

    If security hardening has been completed for the Windows operating system, log in to the server as the SWMaster user.

  2. Run the following command to switch the directory:

    cd eSight installation directory/mttools/tools

  3. Run the following command to modify the permission of the eSight installation directory:

    caclsUser.bat

    After the command is successfully executed, the following message is displayed.

    repair Success.

Database Space Configuration Tool

The command enlarges the database space in the Linux operating system. In an HA system, you need to perform the operations only on the active server. The standby server automatically synchronizes data from the active server.

Syntax

SUSE Linux operating system: dbtool.sh

Euler and SUSE Linux operating systems: es_cli -cmd dbtool

Path

dbtool.sh: eSight installation directory/mttools/tools

es_cli -cmd dbtool: any directory

Prerequisites

The eSight service has been stopped.

In a single-node system, ensure that the database has been started. In an HA system, ensure that the database resource is online.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the ossuser user.
  2. Configure the database space.
    • Configure the database space using a graphical tool. This method is applicable only to the SUSE Linux operating system.

      cd eSight installation directory/mttools/tools

      ./dbtool.sh

      Start the configuration tool and modify the database space as prompted.

    • Configure the database space using commands. This method is applicable to the SUSE Linux and Euler operating systems.

      es_cli -cmd dbtool

      Configure the database space as prompted.

Fault Information Collection Tool

The command collects fault information. In a HA system, you need to perform the operations only on the active server because the eSight service is not started on the standby server.

Syntax

SUSE Linux operating system: maintain.sh

EulerOS and SUSE Linux operating systems: es_cli -cmd logcollect

Path

maintain.sh: eSight installation directory/mttools/tools

es_cli -cmd logcollect: any path

Prerequisites
  • In a single-node system, ensure that the data has been started.
  • In a two-node cluster, ensure that the database resources are online.
Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the ossuser user.
  2. Perform the following operations to collect fault information:
    • Collect fault information using a graphical tool. This method is applicable only to the SUSE Linux operating system.
      1. Run the following command to switch the directory:

        cd eSight installation directory/mttools/tools

      2. Run the following command to start the fault information collection tool:

        ./maintain.sh

        After the command is successfully executed, the operation UI is displayed.

    • Collect fault information using commands. This method is applicable to the SUSE Linux and EulerOS operating systems.

      es_cli -cmd logcollect

      Collect logs as prompted.

Environmental Health Check Tool

The command checks the environment health. In a HA system, you need to perform the operations only on the active server because the eSight service is not started on the standby server.

Syntax

SUSE Linux operating system: cruiser.sh

EulerOS and SUSE Linux operating systems: es_cli -cmd healthcheck

Path

SUSE Linux operating system: eSight installation directory/mttools/tools

es_cli -cmd healthcheck: any path

Prerequisites
  • In a single-node system, ensure that the data has been started.
  • In a two-node cluster, ensure that the database resources are online.
Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the ossuser user.
  2. Perform the following operations to check the health status of the environment:
    • Check the environment health status using a graphical tool. This method is applicable only to the SUSE Linux operating system.
      1. Run the following command to switch the directory:

        cd eSight installation directory/mttools/tools

      2. Run the following command to start the environmental health check tool:

        ./cruiser.sh

        After the command is successfully executed, the operation UI is displayed.

    • Collect fault information using commands. This method is applicable to the SUSE Linux and EulerOS operating systems.

      es_cli -cmd healthcheck

Agile Reporter Data Synchronization Tool

The command is used to synchronize original performance data to Agile Reporter. For example, if a user wants to view data before the upgrade during which Agile Reporter is installed, this tool can be used to synchronize original performance data within the specified period of time. In a HA system, you need to perform the operations only on the active server. The standby server automatically synchronizes data from the active server.

Format

Linux OS: synctool.sh

Path

eSight installation directory/AppBase/UniBI_Server/tools/lib

Prerequisite

1. eSight has been started.

2. Before the upgrade, devices have been added to eSight, eSight has been running normally for a period of time, performance tasks have been normally executed, and collected data has been added to the database.

3. eSight is upgraded to V300R006C00SPC200 or a later version.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as an ossuser user.
  2. Run the following command to switch the directory.

    cd eSight installation directory/AppBase/UniBI_Server/tools/lib

  3. Run the following command to start the tool for synchronizing agile report data:

    ./synctool.sh

    After the command is successfully executed, the operation UI is displayed.

Distributed Connection Tool

This command is used to connect a distributed server to the primary server. If the distributed server is deployed in a two-node cluster, the command needs to be executed on both the active and standby distributed nodes.

Format

Linux OS: connect_tool.sh

Path

eSight installation directory/mttools/tools

Prerequisite

The eSight service has been closed.

The command is executed by the ossuser user on the Linux OS.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    cd eSight installation directory/mttools/tools

  3. Run the following command to start the distributed connection tool:

    ./connect_tool.sh

    After the command is successfully executed, the operation UI of the distributed connection tool is displayed.

Distributed Node Connection Tool

The command is used to connect distributed nodes in the Linux HA system.

Format

Linux OS: joinHA.sh

Path

eSight installation directory/mttools/tools/distributed

Prerequisite

The eSight service has been closed.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the active distributed server as the ossuser user.
    NOTE:

    This operation only needs to be performed on the active distributed server.

  2. Run the following command to switch the directory.

    cd eSight installation directory/mttools/tools/distributed

  3. Run the following command to connect distributed nodes in an HA system.

    ./joinHA.sh

HA System Separation Tool

The command is used to separate distributed nodes in the Linux HA system.

Format

Linux OS: splitHA.sh

Path

eSight installation directory/mttools/tools/distributed

Prerequisite

The eSight service has been closed.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the active distributed server as the ossuser user.
    NOTE:

    This operation only needs to be performed on the active distributed server.

  2. Run the following command to switch the directory.

    cd eSight installation directory/mttools/tools/distributed

  3. Run the following command to separate distributed nodes in an HA system.

    ./splitHA.sh

HA Tool Collection (Veritas)

The command is used to perform common operations in the Linux Veritas HA system.

Syntax

Linux operating system:

HA configuration tool: hatool.sh config

Tool for configuring the southbound IP address of the HA system: hatool.sh southip

Tool for bringing all Veritas resources online: hatool.sh startall

Tool for bringing all Veritas resources offline: hatool.sh stopall

Tool for starting the maintenance tool: hatool.sh startmt

Tool for stopping the maintenance tool: hatool.sh stopmt

Tool for freezing AppService resources: hatool.sh freeze

Tool for unfreezing AppService resources: hatool.sh unfreeze

Tool for displaying the status of all resources: hatool.sh status

Tool for clearing resource faults: hatool.sh clear

Path

eSight installation directory/mttools/tools

Prerequisites
  • The eSight service has been stopped.
  • The active and standby eSight servers have been disconnected.
  • The mountFileRes resource is online.
Precautions

If the HA configuration tool is used, the operating system network service will be restarted after the configuration is complete. If the configuration is not performed on the management port, the connection may be interrupted after the network service is restarted. Use the new IP address to log in to the Linux server.

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    cd eSight installation directory/mttools/tools

  3. Run the following command to modify the HA system configurations:

    ./hatool.sh config

HA Bond Tool(Veritas)

The command is only used to configure the bond on the SUSE Linux operating system in a two-node cluster with multiple subnets.

Format

Linux operating system: buildbond2.sh

Path

eSight installation directory/mttools/ha

Prerequisite

The eSight service has been stopped.

You have logged in through the management network port.

Operations are performed when the active and standby nodes are separated.

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd eSight installation directory/mttools/ha

  3. Run the following command to configure the bond:

    > ./buildbond2.sh

Setting Mutual Trust Between the Active and Standby Servers

This command is used to enable mutual trust between the active and standby servers.

Format

Linux OS: credit.sh

Path

eSight installation directory/mttools/ha/filecopy/

Prerequisite

NA

Precautions

NA

Related Commands

NA

Example
  1. Log in to the active eSight server as ossuser.
  2. eSight is available. However, the active and standby servers cannot obtain the server information from each other.
    ossuser@eSightServer1:/ ping -c 4 10.137.63.225
    PING 10.137.63.225 (10.137.63.225) 56(84) bytes of data.
    64 bytes from 10.137.63.225: icmp_seq=1 ttl=64 time=0.477 ms
    64 bytes from 10.137.63.225: icmp_seq=2 ttl=64 time=0.439 ms
    64 bytes from 10.137.63.225: icmp_seq=3 ttl=64 time=0.437 ms
    64 bytes from 10.137.63.225: icmp_seq=4 ttl=64 time=0.384 ms
    
    --- 10.137.63.225 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2999ms
    rtt min/avg/max/mdev = 0.384/0.434/0.477/0.036 ms
    ossuser@eSightServer1:/ ping -c 4 192.168.122.1
    PING 192.168.122.1 (192.168.122.1) 56(84) bytes of data.
    64 bytes from 192.168.122.1: icmp_seq=1 ttl=64 time=0.018 ms
    64 bytes from 192.168.122.1: icmp_seq=2 ttl=64 time=0.016 ms
    64 bytes from 192.168.122.1: icmp_seq=3 ttl=64 time=0.015 ms
    64 bytes from 192.168.122.1: icmp_seq=4 ttl=64 time=0.014 ms
    
    --- 192.168.122.1 ping statistics ---
    4 packets transmitted, 4 received, 0% packet loss, time 2998ms
    rtt min/avg/max/mdev = 0.014/0.015/0.018/0.005 ms
  3. Run the following commands to change the private key password of the mutual trust key pair:

    > cd /opt/eSight/mttools/ha/filecopy

    > sh credit.sh

  4. Enter the heartbeat IP address and ossuser password as prompted.
    Please input the IP address for the standby node: 
    Please input the standby node password for ossuser: 

    If the OMMHA is deployed in a two-node cluster, the password verification step and related output information are added.

  5. Enter the private key password of the new key pair as prompted. The password must contain uppercase letters, lowercase letters, digits, and special characters.
    Please input the password for certificate private key: 
    Please input the password again: 
    build credit... 
    build credit finish.

    If build credit finish is displayed, the password is changed successfully.

  6. Check whether new trust has taken effect.
    1. Access the standby server using the SSH on the active server.

      > ssh Heartbeat IP address of the standby server

    2. Enter the private key password of the key pair.
      You are trying to access a restricted zone. Only Authorized Users allowed.   
      Enter passphrase for key '/ossuser/.ssh/id_rsa': 

      If the following information is displayed, you have logged in to the standby server successfully, and mutual trust has taken effect:

      Last login: Fri Jun ; 2 17:01:47 2017 from 192.168.122.11  ossuser@eSightServer2:/ossuser>

SQL Server Security Hardening Tool

The command enables security hardening for the SQL Server database.

Syntax

Windows OS: SQLServer.bat

Path

eSight installation directory\mttools\tools\securityharden\SQLServer

Prerequisites

The database has been started.

The eSight service has been stopped.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as the Administrator user.
    NOTE:

    If security hardening has been completed for the Windows operating system, log in to the server as the SWMaster user.

  2. Run the following command to switch the directory:

    cd eSight installation directory\mttools\tools\securityharden\SQLServer

  3. Run the following command to perform security hardening on the SQL Server database.

    SQLServer.bat

Oracle Security Hardening Tool

The command enables security hardening for the Oracle database. In the Veritas HA scenario, you do not need to perform this operation.

Format

Linux OS: Oracle.sh

Path

eSight installation directory/mttools/tools/securityharden/Oracle

Prerequisite

The database has been started.

The eSight service has been closed.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as an ossuser user.
  2. Run the following command to switch the directory.

    cd eSight installation directory/mttools/tools/securityharden/Oracle

  3. Run the following command to perform security hardening on the Oracle database.

    ./Oracle.sh

eSight Start on Linux

This command is only used to start eSight in the Linux single-node system.

Format

Linux OS: startup.sh

Path

eSight installation directory/bin

Prerequisite

The eSight service has been closed.

Precautions

NA

Related Commands

NA

Example
  1. Log in to the server as an ossuser user.
  2. Run the following command to switch the directory.

    cd eSight installation directory/bin

  3. Run the following command to start eSight:

    ./startup.sh

Starting eSight in the Linux Operating System (OMMHA)

This command is used only to start a server node of eSight.

Format

Linux OS: start.sh

Path

/opt/ommha/ha/bin

Prerequisite

The OMMHA has been disabled on the current server.

Precautions

If OMMHA is deployed in a two-node cluster, the active and standby OMMHA nodes need to run at the same time. Therefore, the command needs to be executed on both the active and standby nodes.

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/ommha/ha/bin

  3. Run the following command to start eSight:

    > ./start.sh

Stopping eSight in the Linux Operating System

This command is only used to stop eSight in the Linux single-node system.

Syntax

Linux operating system: shutdown.sh

Path

eSight installation directory/bin

Prerequisites

eSight has been started.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    cd eSight installation directory/bin

  3. Run the following command to stop eSight:

    ./shutdown.sh

Stopping eSight in the Linux Operating System (OMMHA)

This command is used only to stop a server node of eSight.

Format

Linux OS: stop.sh

Path

/opt/ommha/ha/bin

Prerequisite

The OMMHA has been enabled on the current server.

Precautions

If OMMHA is deployed in a two-node cluster, a standby OMMHA node exists. To stop eSight, you need to execute the command on both the active and standby nodes.

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/ommha/ha/bin

  3. Run the following command to stop eSight:

    > ./stop.sh

Querying the Two-Node Cluster Status (OMMHA)

This command is used to query the OMMHA two-node cluster status.

Format

Linux OS: status.sh

Path

/opt/ommha/ha/bin

Prerequisite

The OMMHA has been enabled on the current server.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/ommha/ha/bin

  3. Run the following command to check the two-node cluster status:

    > ./status.sh

Disabling Active/Standby Switchover (OMMHA)

This command is used to disableactive/standby switchover of an OMMHA two-node cluster.

Syntax

Linux operating system: forbidden_switch.sh

  • Parameter 1: forbidden indicates to disable active/standby switchover and cancel indicates to cancel the disabling.
  • Parameter 2: If parameter 1 is set to forbidden, parameter 2 is used to set the disabling time, in minutes.
Path

/opt/ommha/ha/bin

Prerequisites

The OMMHA two-node cluster is running properly.

The command must be executed on the active server.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/ommha/ha/bin

  3. Run the following command to disable active/standby switchover:

    > ./forbidden_switch.sh forbidden 30

  4. Run the following command to cancel the disabling:

    > ./forbidden_switch.sh cancel

Manually Performing Active/Standby Switchover (OMMHA)

This command is used to manually perform the active/standby switchover of the OMMHA two-node cluster.

Format

Linux OS: switchover.sh

Path

/opt/ommha/ha/bin

Prerequisite

The OMMHA two-node cluster is running properly.

The command must be executed on the active server.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/ommha/ha/bin

  3. Run the following command to perform the active/standby switchover:

    > ./switchover.sh

Running the Fault Clearing Tool (OMMHA)

This command is used to manually clear fault records of the OMMHA two-node cluster.

Format

Linux OS: clearrmfault.sh

Path

/opt/ommha/ha/bin

Prerequisite

The OMMHA two-node cluster is abnormal and contains abnormal resource items.

The command must be executed on the standby server.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/ommha/ha/bin

  3. Run the following command to manually clear the fault records:

    > ./clearrmfault.sh

Starting the Maintenance Tool (OMMHA)

This command is used to start the maintenance tool of eSight.

Format

Linux OS: start-sysmon-ha.sh

Path

/opt/eSight/mttools/bin

Prerequisite

The OMMHA two-node cluster has been installed properly.

The OMMHA is not started on both the active and standby servers.

The command must be executed on the active server.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    > cd /opt/eSight/mttools/bin

  3. Run the following command to start the maintenance tool of eSight:

    > ./start-sysmon-ha.sh

Connecting the Active and Standby Servers (OMMHA)

This command is used to connect the active and standby servers and configure the two-node cluster based on the input information.

Syntax

Linux operating system: config.sh

Path

/opt/ommha/config

Prerequisites

The OMMHA two-node cluster has been installed.

The two-node cluster configuration needs to be modified.

The command must be executed on the active server.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user and switch to the root user.
    # su - root
  2. Run the following command to switch the directory:

    > export TMOUT=0

    > cd /opt/ommha/config

  3. Run the following command and enter the new configuration as prompted to connect the active and standby servers:

    > ./config.sh

    NOTE:

    Both IPv4 and IPv6 addresses are supported.

Password Change Using BME

Changing passwords periodically prevents theft of the passwords and unauthorized access.

Changing Passwords on the eSight Server Running the Linux Operating System
  1. Log in to the eSight server as the ossuser user.

    NOTE:

    Remotely log in to the server as the ossuser user and switch to the root user if the Linux operating system is hardened.

  2. Use the encryption tool to encrypt the passwords.

    cd eSight installation directory/AppBase/tools/bmetool/encrypt

    ./encrypt.sh 0

    The following information is displayed:

    Enter the password to be encrypted:       
    9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d

    9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d indicates the cipher-text password.

  3. Replace preset passwords with cipher-text passwords.
Changing Passwords on the eSight Server Running the Windows Operating System
  1. Log in to the eSight server as the Administrator user.

    NOTE:

    If security hardening has been completed for the Windows operating system, log in to the server as the SWMaster user.

  2. Choose Start > Run. In the Run dialog box, enter cmd and press Enter.
  3. Use the encryption tool to encrypt the passwords.

    cd /d eSight installation directory\AppBase\tools\bmetool\encrypt

    encrypt.bat 0

    The following information is displayed:

    Enter the password to be encrypted:       
    9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d

    9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d indicates the cipher-text password.

  4. Replace preset passwords with cipher-text passwords.

Debugging Log for UniBI

The command enables the debugging log for the UniBI. This operation is used only to enable eSight running logs during fault locating. In HA scenarios, this operation does not need to be performed on the standby node because the eSight service is not started on the standby node. Therefore, you only need to perform the operation on the active server.

Format

Linux OS: enableDebugLogging.sh

Windows OS: enableDebugLogging.bat

Path

eSight installation directory/AppBase/UniBI_Server/bin

Prerequisite

eSight has been started.

Precautions

NA

Related Commands

To disable the debugging log of the UniBI and restore the default log level, run the following command:

Linux OS: enableDefaultLogging.sh

Windows OS: enableDefaultLogging.bat

Security Information

The following information is displayed when the debug log function is enabled for the UniBI:

The operation may print session ID and other infomations in the log, and it is recommended that the users turn off the switch in time after use!

Example
  • Windows OS
    1. Log in to the server as the Administrator user.

      Open the command line tool: Choose Start > Run, enter cmd, and press Enter.

    2. Run the following command to switch the directory.

      cd /d eSight installation directory/AppBase/UniBI_Server/bin

    3. Run the following command to enable the debugging log.

      enableDebugLogging.bat

  • Linux OS
    1. Log in to the server as an ossuser user.
    2. Run the following command to switch the directory.

      cd eSight installation directory/AppBase/UniBI_Server/bin

    3. Run the following command to enable the debugging log.

      ./enableDebugLogging.sh

Core File Restoration Tool

This tool is used to process core file errors reported during environment check.

Format

Linux OS: corefile_backup.sh

Windows OS: corefile_backup.bat

Path

eSight installation directory/mttools/tools

Prerequisite

Core file errors are reported during eSight environment check.

Precautions

NA

Related Commands

After a core file error is reported, run the command to restore the faulty core file.

Linux OS: corefile_backup.sh

Windows OS: corefile_backup.bat

Example
  • Windows OS
    1. Log in to the server as the Administrator user.

      Open the command line tool: Choose Start > Run, enter cmd, and press Enter.

    2. Run the following command to switch the directory:

      cd /d eSight installation directory/mttools/tools

    3. Run the following command to restore the core file:

      corefile_backup.bat

  • Linux OS
    NOTE:

    In an HA system, you need to perform the operations only on the active server.

    1. Log in to the server as the ossuser user.
    2. Run the following command to switch the directory:

      cd eSight installation directory/mttools/tools

    3. Run the following command to restore the core file:

      ./corefile_backup.sh

Southbound IP Address Configuration Tool

This command is used only to start the southbound IP address configuration tool in a single-node system.

Syntax

SUSE Linux operating system: southip.sh

SUSE Linux and Euler operating systems: es_cli -cmd southip

Path

southip.sh: eSight installation directory/mttools/tools

es_cli -cmd southip: any directory

Prerequisites

The database has been started.

The eSight service has been stopped.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Change the southbound IP address.
    • Change the southbound IP address using a graphical tool. This method is applicable only to the SUSE Linux operating system.

      cd eSight installation directory/mttools/tools

      ./southip.sh

    • Change the southbound IP address using commands. This method is applicable to the SUSE Linux and Euler operating systems.

      es_cli -cmd southip

      Configure information as prompted.

Installing eSight in Silent Mode (SUSE OMMHA)

In the OMMHA scenario, you can run this command to complete silent installation of eSight. The installed components include all components supported in the OMMHA scenario.

Syntax

Linux operating system: ./install_silent.sh

Path

/opt/install

Prerequisites
  • The Linux operating system has been installed on both the active and standby servers.
  • The operating system firewalls of the active and standby servers have been disabled.
  • The operating system names of the active and standby servers have been changed.
  • The time and time zones of the active and standby servers must be the same.
Precautions

The language of the NMS is determined by the operating system.

Related Commands

N/A

Example
  1. Log in to the eSight server as the root user.
  2. Run the following command to create a temporary directory /opt/install:

    # mkdir -p /opt/install

  3. Copy the eSight_VxxxRxxxCxxSPCxxx_MySQLHA_SUSE.zip file to the "/opt/install" directory on the server.
  4. Run the following commands to decompress the installation software package:

    # cd /opt/install

    # unzip eSight_VxxxRxxxCxxSPCxxx_MySQLHA_SUSE.zip

    After the installation package is decompressed, the install_silent.sh file is generated in the current directory.

  5. Run the following commands to install eSight:

    # chmod u+x install_silent.sh

    # ./install_silent.sh

  6. Select the installation language and a local or remote two-node cluster as prompted.
    Welcome to eSight installation & configuration Wizard
    Please select language [1:Chinese, 2:English]: 
    >1
    Please select HA type, 1(local-HA)  2(remote-HA)
  7. Enter the system IP address, heartbeat IP address, and floating IP address of the active server as prompted.
    Please input local system ip address: 10.137.97.37 
    Please input local heartbeat ip address: 172.28.12.41 
    Please input float ip address: 10.137.97.50 
  8. Configure southbound and northbound service isolation as prompted.
    • In the scenario where southbound services are isolated from northbound services, enter y and press Enter. Enter the planned southbound floating IP address as prompted.
      Enter 'y' to apply the setting of South float IP, or 'n' to use the same IP with float ip(y/n)
      y
      Please input south float ip address: 10.10.11.3 
    • In the scenario where southbound services are not isolated from northbound services, enter n and press Enter.
      Enter 'y' to apply the setting of South float IP, or 'n' to use the same IP with float ip(y/n)
      n
  9. Enter the system IP address and heartbeat IP address of the standby server as prompted.
    Please input remote system ip address: 10.137.97.39 
    Please input remote heartbeat ip address: 172.28.12.42 
  10. Confirm the configuration information.
    Please confirm the following configurations...
    ****************************************
    		local system ip
    		10.137.97.37
    		local heartbeat ip
    		172.28.12.41
    		south float ip
    		10.10.11.3 
    		float ip
    		10.137.97.50
    		remote system ip
    		10.137.97.39
    		remote heartbeat ip
    		172.28.12.42
    Enter 'y' to apply these values and proceed to the next step, or 'n' to return to make any changes (y/n):y
  11. Enter the password of the root user of the standby server as prompted.
    Please input remote root password:
  12. If information similar to the following is displayed, the installation is successful:
    begin init...
    Shutting down the listening SSH daemon..done
    Starting SSH daemon..done
    Shutting down the listening SSH daemon..done
    Starting SSH daemon..done
    init finish
    begin to stop ommha
    stop ommha finish
    begin to check local parameters...
    check parameters finish
    begin to check remote parameters...
    check remote parameters finish
    begin to install ha...
    enter force-installation mode...
    install ha successfully.
    begin to install eSight...
    eSight install finish.
    begin to config local Database...
    config Database finish.
    build credit...
    build credit finish
    begin to rsync...
    rsync finish.
    begin to startup...
    HAMode 
    double
    NodeName                                 HostName                                 HAVersion                StartTime                HAActive             HAAllResOK           HARunPhase          
    ha1                                      eSightServer37                           V100R001C01              2017-09-14 11:12:15      active               normal               Actived             
    ha2                                      eSightServer39                           V100R001C01              2017-09-14 11:16:31      standby              normal               Deactived          
    
    NodeName                                 ResName                                  ResStatus                ResHAStatus              ResType             
    ha1                                      Database                                    Active_normal            Normal                   Active_standby      
    ha1                                      NMSServer                                Normal                   Normal                   Single_active       
    ha1                                      RMFloatIp                                Normal                   Normal                   Single_active       
    ha2                                      Database                                    Standby_normal           Normal                   Active_standby      
    ha2                                      NMSServer                                Stopped                  Unknown                  Single_active       
    ha2                                      RMFloatIp                                Stopped                  Normal                   Single_active
  13. After eSight is successfully installed, delete the patch installation package and temporary files from the server.

    # rm -rf /opt/install

Silent eSight Installation (Veritas)

In the Veritas scenario, you can run this command to complete silent installation of eSight. The installed components include all components supported in the Veritas scenario.

Syntax

Linux operating system: ./setup_silent.sh

Path

/opt/install

Prerequisites
  • The Oracle and Veritas have been installed.
  • The NIC has been enabled.
Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the operating system on the active server as the root user.
  2. Upload the software package to the /opt/install directory on the active and standby servers as the root user.
    NOTE:

    When installing eSight using the CD-ROM, you need to copy the software package to the installation directory in advance.

  3. Run the following command to grant permissions on the installation package:

    # chmod -R 755 /opt/install/

  4. Run the following commands:

    # hares -online FloatIP -sys Name of the host where eSight is to be installed

    # hares -online Netlsnr -sys Name of the host where eSight is to be installed

    # hares -online RVGPrimary -sys Name of the host where eSight is to be installed

    NOTE:

    You can run the # hostname command to query the host name.

  5. Run the following commands in the installation package directory as the root user:

    # cd /opt/install/Directory to which the software package is decompressed

    # ./setup_silent.sh

  6. The installation takes about 10 minutes. If the following information is displayed, the active server is installed successfully:
    ===============< Installation Completed >===============
    Finish
  7. Run the following commands:

    # hares -offline Netlsnr -sys Name of the host where eSight is to be installed

    # hares -offline FloatIP -sys Name of the host where eSight is to be installed

  8. Repeat steps 1 to 7 to install the other server.
Post-processing Operation
  • For a local HA system, follow instructions in the installation guide to connect the active and standby servers.
  • For a remote HA system, follow instructions in the installation guide to connect the active and standby servers.

sshdPermitRootLogin.sh(OMMHA)

This command is used only to configure whether the root user can log in to the host using SSH.

After security hardening, only the ossuser user can log in to the local host using SSH by default. However, in the OMMHA scenario, the root user can log in to the local host using SSH. The following needs to be implemented:

  • The ossuser and root users can use any IP address to log in to the local host using SSH.
  • Only the ossuser user can use any IP address to log in to the local host using SSH.
  • The ossuser user can use any IP address to log in to the local host using SSH. The root user can use only the specified IPv4 address to log in to the local host using SSH.
Format

Linux operating system: sshdPermitRootLogin.sh

Path

/opt/ommha/config

Prerequisites
  • The OMMHA two-node cluster has been installed and security hardening has been performed on eSight.
  • In the Linux operating system, the command is executed by the root user.
Precautions

Since the status needs to be switched between three options, the script uses a parameter to specify the corresponding setting. If the parameter input is invalid, the following help information is displayed:

Usage: sshdPermitRootLogin.sh OPTION
Modify the sshd configuration item PermitRootLogin and make the modification take effect immediately. The options are as follows:
-y, --yes           The ossuser and root users can use SSH to log in to the local host using any IP address.
-n, --no            Only the ossuser user can use SSH to log in to the local host using any IP address.
-a, --allow IPV4    The ossuser user can use SSH to log in to the local host using any IP address. The root user can use SSH to log in to the local host using the specified IPv4 address.
Examples:
./sshdPermitRootLogin.sh -y
./sshdPermitRootLogin.sh -n
./sshdPermitRootLogin.sh -a 192.168.1.100
Related Commands

NA

Example
  1. Log in to the server as the root user, log in to the server as the ossuser user and run the su - root command to switch to the root user.
  2. Run the following command to switch the directory:

    cd /opt/ommha/config

  3. Perform one of the following operations as required:
    • The ossuser and root users use any IP address to log in to the local host using SSH.

      ./sshdPermitRootLogin.sh -y or

      ./sshdPermitRootLogin.sh --yes

    • Only the ossuser user can use any IP address to log in to the local host using SSH.

      ./sshdPermitRootLogin.sh -n or

      ./sshdPermitRootLogin.sh --no

    • The ossuser user can use any IP address to log in to the local host using SSH. The root user can use only the specified IPv4 address (for example, 192.168.1.100) to log in to the local host using SSH.

      ./sshdPermitRootLogin.sh -a 192.168.1.100 or

      ./sshdPermitRootLogin.sh --allow 192.168.1.100

MySQL Backup and Restore Tool

If the eSight server using the MySQL database is powered off unexpectedly (for example, the equipment room is powered off) and the data is being written into the MySQL database at a high frequency, data files may be damaged. As a result, the MySQL database cannot be started normally when the eSight server is restarted upon power-on and eSight is unavailable. This tool is used to restore data files in the MySQL database in this scenario.

Syntax

Linux operating system: mysql_recovery.sh

Windows operating system: mysql_recovery.bat

NOTE:

In the Linux operating system, execute this tool as the ossuser user. In the Windows operating system, execute this tool as the administrator with the read and write permission on the MySQL installation directory.

Path

Linux operating system: eSight installation directory/mttools/tools

Windows operating system: eSight installation directory\mttools\tools

Prerequisites

eSight and the MySQL database have been stopped.

  1. In the Windows operating system, you need to open the command prompt as the administrator and run the sc stop eSightMySQL command to stop the eSightMySQL service after eSight is stopped.
  2. In the OMMHA two-node cluster, perform operations in • OMMHA two-node cluster environment operation guide.
Precautions
  • Before restoring the entire database, ensure that the entire database has been backed up.
  • Before using the tool, configure related information correctly on the Database Parameters panel.
Related Commands

N/A

Example
  • Tool Interface

    The tool consists of two panels: Database Parameters and Backup and Recovery.
    • Database Parameters

      The Database Parameters panel contains the following items:

      • DB IP: Set it to the listening IP address of the MySQL database. On eSight, the default listening IP address of MySQL is 127.0.0.1.
      • DB Port: Set it to the listening port of the MySQL database. Check the configuration item port=Port in esight.ini in the MySQL database installation directory.
      • Admin User: Set it to the super user name of the MySQL database. On eSight, the default super user name of the MySQL database is dbadmin.
      • Password: Set it to the password of the super user of the MySQL database.
      • MySQL Path: Set it to the installation directory of the MySQL database.
      • Backup Path: Set it to an available directory for backing up data files in the MySQL database. Do not set this parameter to a directory in the eSight installation directory.
    • Backup and Recovery

      The main functions of the tool are integrated on this panel. This panel consists of three tab pages:

      • Entire DB: Restore the entire database.
      • Single: Restore a single database or data table.
      • Entire Backup: Back up the entire database.
  • Entire DB

    This function uses the backup files in the backup directory specified on the Database Parameters panel to fully restore data files in the MySQL database. It restores the data in the MySQL database to the backup data. Data added after backup will be lost.

    If no backup file exists in the directory specified by Backup Path, the tool tries to use the existing data files to restore the database files. However, the restoration may fail.

    Click Begin to start the restoration. The information such as the execution process and error message is displayed in the Output area.

  • Single

    This function is used to restore a single database or data table and does not depend on backup files. It is applicable to the scenario where the MySQL database cannot be started because a few data files are damaged.

    This function deletes all files in the directory specified by Backup Path and backs up the selected database or data table files to this directory.

    Configure the database information correctly.
    • Database: Set it to the name of the database to be restored.
    • Table (Optional): Set it to the name of the data table to be restored.

    After setting the database and table correctly, click Begin to restore the database or data table.

  • Entire Backup

    This function is used to back up the entire database.

    If the directory specified by Backup Path contains backup files (regardless of whether the backup files are full database backup files or single database and table backup files), the database will not be backed up.

    Click Backup to start the backup. Do not specify a directory in the eSight installation directory as the backup directory.

  • Command modes of the tool

    If you cannot run the tool on the GUI, execute the tool script. The following information is displayed:

    Option 'IP Address'('-h') is mandatory.
    Usage: ./mysql_recovery.sh [ <option>=<value> | <option> <value> ]
      -h <value>   -- IP Address
      -P <value>   -- port
      -u <value>   -- username
      -p <value>   -- password
      -i <value>   -- mysql installation directory
      -b <value>   -- backup directory
      -r <value>   -- recover action: all | single | onlybackup
    When in single recover action, need specify:
      -db <value>   -- database name
      -tbl <value>   -- table name, optional

    In this case, run related commands to start the tool. The command format is as follows:

    • Entire Backup

      >./mysql_recovery.sh -h Listening IP address of the database -P Listening port of the database -u Database administrator -p Database administrator password -i Database installation directory -b Database file backup directory -r onlybackup

    • Entire DB

      >./mysql_recovery.sh -h Listening IP address of the database -P Listening port of the database -u Database administrator -p Database administrator password -i Database installation directory -b Database file backup directory -r all

    • Single

      >./mysql_recovery.sh -h Listening IP address of the database -P Listening port of the database -u Database administrator -p Database administrator password -i Database installation directory -b Database file backup directory -r single -db Database to be restored -tbl Data table to be restored

  • OMMHA two-node cluster environment operation guide

    Before running the tool, follow instructions in Stopping eSight to stop eSight and the MySQL database. Do not set the MySQL database file backup directory to a directory in the eSight installation directory.

    • Entire Backup

      Follow previous operations to log in to the active and standby servers to back up the entire database.

    • Entire DB

      Follow previous operations to log in to the active and standby servers to restore the entire database. After the restoration is complete, follow instructions in "Synchronizing MySQL database files" to synchronize the MySQL database files between the active and standby servers.

    • Single

      Follow previous operations to log in to the active and standby servers to restore a database or table. After the restoration is complete, follow instructions in ▪ Synchronizing MySQL database files to synchronize the MySQL database files between the active and standby servers.

    • Synchronizing MySQL database files

      Perform the following operations:

      1. Log in to the active and standby servers and stop the MySQL database on the local host.

      > cd /opt/eSight/MySQL/bin

      > sh stop.sh

      1. Follow instructions in Starting eSight to start the active and standby servers.
      2. Log in to the active server and run the following commands to synchronize data between the active and standby servers:

        > cd /opt/eSight/mttools/tools

        > ./hadatasyncrecover.sh

        When the following information is displayed, type the password of the database administrator and press Enter:

        Please input super password of Database:

        If the following information is displayed, the database is successfully restored. Otherwise, contact Huawei technical support.

        Database recover success

Upgrade Evaluation Tool

This command is used only to evaluate eSight in the upgrade scenario. In a HA system, you need to perform the operations only on the active server because the eSight service is not started on the standby server.

Syntax

SUSE Linux operating system: upgradechecktool.sh

EulerOS and SUSE Linux operating systems: es_cli -cmd upgradecheck

Operation User

ossuser

Path

upgradechecktool.sh: eSight installation directory/mttools/tools

es_cli -cmd upgradecheck: any path

Prerequisites
  • In a single-node system, ensure that the data has been started.
  • In a two-node cluster, ensure that the database resources are online.
Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Perform the following operations to start the upgrade evaluation tool:
    • Start the tool through a graphical tool (applicable only to the SUSE Linux operating system)
      1. Run the following command to switch the directory:

        cd eSight installation directory/mttools/tools

      2. Run the following command to start the upgrade evaluation tool:

        ./upgradechecktool.sh

        After the command is successfully executed, the operation UI is displayed.

    • Start the tool through commands (applicable to the EulerOS and SUSE Linux operating systems)

      es_cli -cmd upgradecheck

Stopping eSight Without Stopping the Maintenance Tool (Veritas)

This command is used only when the maintenance tool is used for manual restoration in the Veritas HA system. It is used to bring the NMSServer resource offline and keep the maintenance tool running.

Syntax

Linux operating system: stop-application-ha.sh

NOTE:

In the Linux operating system, run this command as the ossuser user.

Path

eSight installation directory/mttools/bin

Prerequisites

The eSight service has been started.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    cd eSight installation directory/mttools/bin

  3. Run the following command to stop eSight without stopping the maintenance tool:

    ./stop-application-ha.sh

    If the message "eSight is stopped." is displayed, eSight is successfully stopped. In this case, you can still log in to the maintenance tool.

Restoring the Soft Link of the Veritas HA System

Syntax

Linux operating system: syncLinkFixit.sh

NOTE:
  • This tool can be used only in the Veritas HA system. Run this tool as the ossuser user. During the execution of this command, you need to enter the password of the root user.
  • If the active and standby servers are connected, run the tool on the active server. If they are not connected, run the tool on the server where the alarm of damaged soft link is generated.
Path

eSight installation directory/mttools/bin

Prerequisites

1. The NMSServer resource has been brought offline.

2. The moutFileRes resource has been brought online.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user.
  2. Run the following command to switch the directory:

    cd eSight installation directory/mttools/bin

  3. Run the following command to restore the damaged soft link:

    > sh syncLinkFixit.sh

    The following information is displayed:

    Please input root password in order to create link whose owner is root: 

    Enter the password of the root user and create a soft link for the root user.

    NOTE:
    • If the message "Cannot fix the problem when data replication status is Primary-Primary." is displayed, the HA system is in dual-active state. In this case, this tool cannot be used for restoration. Contact Huawei technical support engineers.
    • If any of the following messages is displayed, information about the standby server cannot be obtained. Contact Huawei technical support engineers:
      • Cannot get remote system hostname. System will exit.
      • Cannot get remote system ip address. System will exit.
      • Cannot connect standby server.
    • If the message "Please make sure that the NMSServer is offline." is displayed, bring the NMSServer resource offline by referring to the product documentation and then run the tool again.
    • If the message "Please use this tool on Primary server." is displayed, run the tool on the active server.

    The syncLinkFixit.sh tool will display the detected soft link that is faulty and try to restore it.

    The following takes the abnormal soft link AppBase/etc/license as an example. If the following information is displayed, the soft link is successfully restored:

    Problem Solved. AppBase/etc/license is OK.

    If the following information is displayed, the soft link cannot be restored:

    Sorry, we cannot fix AppBase/etc/license. Please ask for help.

    Contact Huawei technical support engineers.

Changing the Number of File Handles on the Linux Operating System

This command is used only when the number of file handles on the Linux operating system is less than 65,535. In an HA system, run this command on both the active and standby servers.

Syntax

Linux operating system: modifySysCfg.sh ulimit

Path

eSight installation directory/mttools/tools

Prerequisites

N/A

Precautions

N/A

Related Commands

N/A

Example
  • Single-node system
    1. Log in to the eSight server as the ossuser user and run the following commands:

      > cd eSight installation directory/mttools/tools

      > sh modifySysCfg.sh ulimit

    1. Run the following commands to stop eSight:

      > cd eSight installation directory/bin

      > sh shutdown.sh

    1. Switch to the root user and run the following command to restart the operating system:
      NOTE:

      Restarting the operating system is a high-risk operation. Exercise caution.

      # reboot

    1. After the operating system is restarted, log in as the ossuser user and run the following commands to start eSight:

      > cd eSight installation directory/bin

      > sh startup.sh

  • OMMHA HA system
    1. Log in to the active eSight server as the ossuser user and run the following commands:

      > cd eSight installation directory/mttools/tools

      > sh modifySysCfg.sh ulimit

    1. Run the following commands to disable active/standby switchover:

      > cd /opt/ommha/ha/bin

      > ./forbidden_switch.sh forbidden 30

    1. Stop the OMMHA HA system.

      > ./stop.sh

    1. Switch to the root user and run the following command to restart the operating system:
      NOTE:

      Restarting the operating system is a high-risk operation. Exercise caution.

      # reboot

    1. After the operating system is restarted, the OMMHA HA system automatically starts with the operating system. Ensure that the HA system is started before subsequent operations are performed.
    2. Run the following commands to cancel disabling of the active/standby switchover:

      > cd /opt/ommha/ha/bin

      > ./forbidden_switch.sh cancel

    1. Log in to the standby eSight server as the ossuser user and run the following commands:

      > cd eSight installation directory/mttools/tools

      > sh modifySysCfg.sh ulimit

    1. Stop the OMMHA system.

      > ./stop.sh

    1. Switch to the root user and run the following command to restart the operating system:
      NOTE:

      Restarting the operating system is a high-risk operation. Exercise caution.

      # reboot

  • Veritas HA system
    1. Log in to the active eSight server as the ossuser user and run the following commands:

      > cd eSight installation directory/mttools/tools

      > sh modifySysCfg.sh ulimit

    1. Switch to the root user and run the following command to bring the NMSServer resource offline:

      # hares -offline NMSServer -sys Host name of the active server

    1. Log in to the standby server as the root user and run the following command to freeze the AppService resource group:

      # hagrp -freeze AppService

    1. Run the following command on the active server as the root user to restart the operating system:
      NOTE:

      Restarting the operating system is a high-risk operation. Exercise caution.

      # reboot

    1. After the operating system is restarted, run the following command on the standby server as the root user to unfreeze the AppService resource group:

      # hagrp -unfreeze AppService

    1. Perform an active/standby switchover. For details, see Manual Switchover Between Active and Standby Servers. After the preceding operations are complete, perform 1 to 5 again.
      NOTE:

      You can run the following command to distinguish between the active and standby servers:

      # vradmin -g <diskgroupname> repstatus <rvgname>

    2. Perform an active/standby switchover again. For details, see Manual Switchover Between Active and Standby Servers.

silentConfigSso

This command is used for configuring the login address when eSight is interconnected with the UniSSO. Import of the SSO server certificate is not involved.

Syntax

Linux operating system: sh silentConfigSso.sh <[unisso|rollback]> <[SSO Server Login URL]> <[SSO Server Logout URL]> <[Local system URL]>

Path

eSight installation directory/AppBase/tools

Parameter Description

Parameter

Description

Example

unisso|rollback

  • unisso: Configures interconnection with the UniSSO. If this value is used, the rest three parameters are mandatory.
  • rollback: Rolls back the configuration. If this value is used, the rest three parameters do not need to be set.

unisso

SSO Server Login URL

URL for logging in to the SSO server.

https://10.10.10.10:31943/unisso

SSO Server Logout URL

URL for logging out of the SSO server.

https://10.10.10.10:31943/unisso/logout

Local system URL

URL for logging in to eSight. The port number is 31942.

https://10.10.10.20:31942

Prerequisites

1. This command must be executed as the ossuser user.

2. This command is used only for configuring the login address when eSight is interconnected with the UniSSO. Import of the SSO server certificate is not involved.

Precautions

N/A

Related Commands

NA

Example (Interconnection with U2020 SSO)
  1. Obtain the login address and logout address of the U2020 SSO server, and the eSight login address.
  2. Log in to the eSight server as the ossuser user and run the following commands:

    > cd eSight installation directory/AppBase/tools

    > sh silentConfigSso.sh unisso https://10.10.10.10:31943/unisso https://10.10.10.10:31943/unisso/logout https://10.10.10.20:31942

  1. Restart eSight.
Example (Rollback)
  1. Log in to the eSight server as the ossuser user and run the following commands:

    > cd eSight installation directory/AppBase/tools

    > sh silentConfigSso.sh rollback

  1. Restart eSight.

config_silent

This command is used to connect the active and standby servers.

Syntax

Linux operating system: ./config_silent.sh [option] ...[value]

Path

/opt/ommha/config

Parameter Description

Parameter

Description

Example

-x

Local or remote HA system. (This parameter is mandatory.)

1: local HA system; 2: remote HA system

-y

Indicates whether to enable southbound and northbound isolation. (This parameter is mandatory.)

1: southbound and northbound non-isolation; 2: southbound and northbound isolation

-a

IP address of the local system. (This parameter is mandatory.)

192.168.1.101

-b

Local heartbeat IP address. (This parameter is mandatory.)

192.168.2.101

-c

Local southbound IP address. (This parameter is mandatory for the remote two-node cluster when southbound and northbound isolation is enabled.)

192.168.3.101

-h

IP address of the remote system. (This parameter is mandatory.)

192.168.1.102

-i

Remote heartbeat IP address. (This parameter is mandatory.)

192.168.2.102

-j

Remote southbound IP address. (This parameter is mandatory for the remote two-node cluster when southbound and northbound isolation is enabled.)

192.168.3.102

-f

Floating IP address. (This parameter is mandatory for the local two-node cluster.)

192.168.1.100

-s

Southbound floating IP address. (This parameter is mandatory for the local two-node cluster when southbound and northbound isolation is enabled.)

192.168.3.100

-p

Password of the root user for logging in to the remote VM. (This parameter is mandatory.)

Changeme123

Prerequisites
  • The OMMHA two-node cluster has been installed.
  • The command must be executed on the active server.
Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the ossuser user and switch to the root user.
    > su - root
  2. Run the following command to switch the directory:

    # cd /opt/ommha/config

  3. Run the following command to connect the active and standby servers:

    # ./config_silent.sh -x 1 -y 1 -a 192.168.1.101 -b 192.168.2.101 -h 192.168.1.102 -i 192.168.2.102 -f 192.168.1.100 -p Changeme123

roatool

This command is used to configure the roa whitelist.

Syntax

Linux operating system: ./roatool.sh [option]

Windows operating system: roatool.bat [option]

Path

Linux operating system: eSight installation directory/mttools/tools

Windows operating system: eSight installation directory\mttools\tools

Parameter Description

Parameter

Description

Example

rollback

(Optional) Rolls back the roa whitelist.

rollback

Prerequisites

eSight has been stopped.

Precautions

N/A

Related Commands

N/A

Example
  • Windows operating system
    1. Log in to the server as the Administrator user.

      Choose Start > Run, enter cmd, and press Enter to open the command line tool.

    2. Run the following command to switch the directory:

      cd /d eSight installation directory/mttools/tools

    3. Run the following command to configure the roa whitelist:

      roatool.bat

  • Linux operating system
    1. Log in to the server as the ossuser user.
    2. Run the following command to switch the directory:

      cd eSight installation directory/mttools/tools

    3. Run the following command to configure the roa whitelist:

      ./roatool.sh

sem_tool

This command is used to configure the system IP address, bond, and host name in the Euler operating system.

Syntax

Euler operating system: sem_tool -cmd [option]

Path

Euler operating system: any directory

Parameter Description

Parameter

Level-2 Parameter

Description

Example

ifconfig

-name

NIC name.

The command for configuring an IP address on the NIC eth2 is as follows:

sem_tool -cmd ifconfig -name eth2 -ip 10.137.117.141 -mask 255.255.254.0 -gateway 10.137.116.1

-ip

IP address to be configured.

-mask

Subnet mask.

-gateway

Gateway.

unifconfig

-name

NIC name.

The command for deleting information about NIC eth2 is as follows:

sem_tool -cmd unifconfig -name eth2

bond

-nics

Name of NICs to be bonded.

The command for configuring a bond is as follows:

sem_tool -cmd bond -name bond3 -nics eno3,ens1f2 -mode active-backup -ip 192.168.9.210 -mask 255.255.0.0

-mode

Bond mode. The options include active-backup (active-standby mode) and 802.3ad (aggregation mode).

-ip

IP address to be configured.

-mask

Subnet mask.

unbond

-name

Name of NICs whose bond needs to be deleted.

The command for deleting the bond is as follows:

sem_tool -cmd unbond -name bond3

hostname

-name

Host name.

The command for modifying the server host name is as follows:

sem_tool -cmd hostname -name eSightServer02

Prerequisites

eSight has been stopped.

Precautions

N/A

Related Commands

N/A

Example
  1. Log in to the server as the root user.
  2. Run the following command to modify the server IP address:

    sem_tool -cmd ifconfig -name eth2 -ip 10.137.117.141 -mask 255.255.254.0 -gateway 10.137.116.1

hadatasyncrecover

hadatasyncrecover is used to restore the database in an HA system.

Syntax

Linux operating system: ./hadatasyncrecover.sh

Path

Linux operating system: "/opt/eSight/mttools/tools"

Parameter Description

N/A

Precautions

N/A

Related Commands

N/A

Example
  1. Log to the active servers as the ossuser user.
  2. Run the following commands to restore data:

    > cd /opt/eSight/mttools/tools

    > ./hadatasyncrecover.sh

    When the following information is displayed, type the password of the database administrator and press Enter:

    Please input super password of Database:

    If the following information is displayed, the database is successfully restored. Otherwise, contact Huawei technical support.

    Database recover success

Translation
Download
Updated: 2019-06-30

Document ID: EDOC1100044373

Views: 25016

Downloads: 74

Average rating:
This Document Applies to these Products
Related Documents
Related Version
Share
Previous Next