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 08

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).
Basic Management

Basic Management

Starting All Processes

This common is used to start the eSight process and maintenance tool process. It is not applicable to the HA system.

Syntax

Linux operating system: startup.sh [hidden | noAgent]

NOTE:

If the operating system is Windows, start the eSight process on the eSight Console.

Path

eSight installation directory/bin

Parameter Description

Parameter

Description

hidden|noAgent

  • hidden: The message "Press any key to continue..." is not displayed after a command is successfully executed. Instead, the command-line interface is displayed for users to enter other commands.
  • noAgent: Only start the daemon and maintenance tool processes, but not start the eSight service. If this parameter is not specified, all processes and the eSight service will be started.
Prerequisites
  • The database has been started.
  • This operation is performed by the ossuser user.
Precautions
Related Commands

shutdown.sh: used to stop all processes on Linux.

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 start all processes:

    ./startup.sh

    After the command is successfully executed, the following information is displayed:

     
    Runtime Environment Checking... 
    Runtime Environment is OK. 
    starting eSight system 
    starting ntc system 
    starting sysagent ntc 
    starting watchdog 
    starting watchdog done. 
    starting sysmonitor 
    starting sysmonitor done. 
    starting eSight daemons 
    --------------------------- 
    4 services will be executed 
    ---------------------------  
    smsmodemAgent   ............    RUNNING 
    iempssoAgent    ............    RUNNING 
    nodejs  ............    RUNNING 
    nginx   ............    RUNNING 
    starting eSight daemons done. 
    starting eSight svc agents 
    --------------------------- 
    2 services will be executed 
    --------------------------- 
    unibi   ............    RUNNING 
    eSightAgent     ............    RUNNING 
    starting eSight svc agents done. 
    starting ntc svc agents 
    -------------------------- 
    1 service will be executed 
    -------------------------- 
    ntcAgent        ............    RUNNING 
    starting ntc svc agents done. 
    starting eSight system succeeded.     

Stopping All Processes

This common is used to stop the eSight process and maintenance tool process. It is not applicable to the HA system.

Syntax

Linux operating system: shutdown.sh

NOTE:

If the operating system is Windows, stop the eSight process on the eSight Console.

Path

eSight installation directory/bin

Prerequisites
  • The database is started.
  • This operation is performed by the ossuser user.
Precautions
Related Commands

startup.sh: used to start all processes on Linux.

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 all processes:

    ./shutdown.sh

  4. When the system displays the message "Are you sure you want to stop the system? (Please enter y or n)", enter y.

    After the command is successfully executed, the following information is displayed:

     
    Runtime Environment Checking... 
    stopping eSight system 
    stopping sysmonitor 
    stopping sysmonitor done. 
    stopping watchdog 
    stopping watchdog done. 
    stopping svc agents 
    --------------------------- 
    2 services will be executed 
    --------------------------- 
    unibi   ............    STOPPED 
    eSightAgent     ............    STOPPED 
    stopping svc agents done. 
    stopping daemons 
    --------------------------- 
    4 services will be executed 
    --------------------------- 
    nginx   ............    STOPPED 
    smsmodemAgent   ............    STOPPED 
    iempssoAgent    ............    STOPPED 
    nodejs  ............    STOPPED 
    stopping daemons done. 
    stopping svc agents 
    -------------------------- 
    1 service will be executed 
    -------------------------- 
    ntcAgent        ............    STOPPED 
    stopping svc agents done. 
    stopping eSight system succeeded.     

Starting the Maintenance Tool Process

This command is used to start the maintenance tool process. It is not applicable to the HA system.

Syntax

Linux operating system: start-sysmon.sh [hidden] [-help]

NOTE:

If the operating system is Windows, start the eSight maintenance tool process on the Start menu.

Path

eSight installation directory/mttools/bin

Parameter Description

Parameter

Description

hidden

The message "Press any key to continue..." is not displayed after a command is successfully executed. Instead, the command-line interface is displayed for users to enter other commands.

-help

Display the help.

Prerequisites

This operation is performed by the ossuser user.

Precautions
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 start the maintenance tool process:

    ./start-sysmon.sh

    After the command is successfully executed, the following information is displayed:

    starting mttools ..... 
    start mttools done.     

Stopping the Maintenance Tool Process

This command is used to stop the maintenance tool process. It is not applicable to the HA system.

Syntax

Linux operating system: stop-sysmon.sh [hidden] [-help]

NOTE:

If the operating system is Windows, stop the maintenance tool process on the eSight Console.

Path

eSight installation directory/mttools/bin

Parameter Description

Parameter

Description

hidden

The message "Press any key to continue..." is not displayed after a command is successfully executed. Instead, the command-line interface is displayed for users to enter other commands.

-help

Display the help.

Prerequisites

This operation is performed by the ossuser user.

Precautions

For details about how to stop processes in an HA system, see Taking a Resource Group Offline and Taking a Resource Offline.

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 the maintenance tool process:

    ./stop-sysmon.sh

    After the command is successfully executed, the following information is displayed:

    stopping mttools ..... 
    stop mttools done.     

Querying eSight Log Levels

This command is used to query the eSight log levels.

Syntax
  • Windows operating system: omscli.bat log <[all|logname]>
  • Linux operating system: omscli.sh log <[all|logname]>
Path

eSight installation directory/AppBase/bin

Parameter Description

Parameter

Description

all|logname

  • all: queries the log levels of all modules.
  • logname: queries the log levels of a module, such as the BME. For details about the logname list, see the eSight Log Reference.
Prerequisites
  • eSight has been started.
  • eSight uses log4j to print logs. The log levels are DEBUG, INFO, WARN, ERROR, and FATAL. The default log level is ERROR.
  • The command is executed by the Administrator user in the Windows operating system and by the ossuser user in the Linux operating system.
Example

The following describes how to query all log levels of eSight:

  • Windows operating system
    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 /d eSight installation directory/AppBase/bin

    3. Run the following command to view all log levels:

      omscli.bat log all

      After the command is successfully executed, the following information is displayed:

      No   Name                  Level  File 
      1    KeyBusiness           INFO   D:\eSight\AppBase\var\iemp\log\enterprise\common\KeyBusiness.log 
      2    SnmpAgent             ERROR  D:\eSight\AppBase\var\iemp\log\oms\nbi\snmp\SnmpAgent.log 
      3    apache                WARN   D:\eSight\AppBase\var\iemp\log\oms\core\apache.log 
      4    apex                  ERROR  D:\eSight\AppBase\var\iemp\log\esight\apex\apex.log 
      5    audit                 ERROR  D:\eSight\AppBase\var\iemp\log\oms\audit\audit.log 
      6    audit_sdk             ERROR  D:\eSight\AppBase\var\iemp\log\oms\audit\audit_sdk.log 
      7    autodis_ds            ERROR  D:\eSight\AppBase\var\iemp\log\oms\autodis\autodis_ds.log 
           
  • Linux operating system
    1. Log in to the server as the ossuser user.
      NOTE:

      In a Veritas two-node cluster, you need to perform the operations only on the active server.

    2. Run the following command to switch the directory:

      cd eSight installation directory/AppBase/bin

    3. Run the following command to view all log levels of eSight:

      ./omscli.sh log all

      After the command is successfully executed, the following information is displayed:

      No   Name                  Level  File 
      1    KeyBusiness           INFO   /opt/eSight/AppBase/var/iemp/log/enterprise/common/KeyBusiness.log 
      2    SnmpAgent             ERROR  /opt/eSight/AppBase/var/iemp/log/oms/nbi/snmp/SnmpAgent.log 
      3    apache                WARN   /opt/eSight/AppBase/var/iemp/log/oms/core/apache.log 
      4    apex                  ERROR  /opt/eSight/AppBase/var/iemp/log/esight/apex/apex.log 
      5    audit                 ERROR  /opt/eSight/AppBase/var/iemp/log/oms/audit/audit.log 
      6    audit_sdk             ERROR  /opt/eSight/AppBase/var/iemp/log/oms/audit/audit_sdk.log 
      7    autodis_ds            ERROR  /opt/eSight/AppBase/var/iemp/log/oms/autodis/autodis_ds.log     

Changing eSight Log Levels

This command is used to change the eSight log levels.

Syntax
  • Windows operating system: omscli.bat log <[all|logname]> <[level|default]>
  • Linux operating system: omscli.sh log <[all|logname]> <[level|default]>
Path

eSight installation directory/AppBase/bin

Parameter Description

Parameter

Description

all|logname

  • all: changes the log levels of all modules.
  • logname: changes the log levels of a module, such as the BME. For details about the logname list, see eSight Log Reference.

level|default

  • level: changes the log level to a specified one, such as DEBUG.
  • default: changes the log level to the default one (ERROR).
Prerequisites
  • eSight has been started.
  • eSight uses log4j to print logs. The log levels are DEBUG, INFO, WARN, ERROR, and FATAL. The default log level is ERROR.
  • The command is executed by the Administrator user in the Windows operating system and by the ossuser user in the Linux operating system.
Related Commands
  • omscli.bat log <[all|logname]>: Queries eSight log levels in the Windows operating system.
  • omscli.sh log<[all|logname]>: Queries eSight log levels in the Linux operating system.
Example

The following describes how to change all log levels of eSight:

  • Windows operating system
    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 /d eSight installation directory/AppBase/bin

    3. Run the following command to change the all log levels of eSight:

      omscli.bat log all default

      After the command is successfully executed, the following information is displayed:

      Change log level of apache               from WARN  to ERROR  
      Change log level of asutil               from DEBUG to ERROR  
      Change log level of base                 from DEBUG to ERROR  
      Change log level of bme                  from DEBUG to ERROR  
      Change log level of cache                from DEBUG to ERROR  
      Change log level of configure            from DEBUG to ERROR  
      Change log level of dbevtutil            from DEBUG to ERROR  
      Change log level of dis_frame            from DEBUG to ERROR  
      Change log level of dis_lldp             from DEBUG to ERROR  
      Change log level of dis_snmp             from DEBUG to ERROR  
      Change log level of dump_ds              from DEBUG to ERROR      
  • Linux operating system
    1. Log in to the server as the ossuser user.
      NOTE:

      In a Veritas two-node cluster, you need to perform the operations only on the active server.

    2. Run the following command to switch the directory:

      cd eSight installation directory/AppBase/bin

    3. Run the following command to change the all log levels of eSight:

      ./omscli.sh log all default

      After the command is successfully executed, the following information is displayed:

      Change log level of apache               from WARN  to ERROR  
      Change log level of asutil               from DEBUG to ERROR  
      Change log level of base                 from DEBUG to ERROR  
      Change log level of bme                  from DEBUG to ERROR  
      Change log level of cache                from DEBUG to ERROR  
      Change log level of configure            from DEBUG to ERROR  
      Change log level of dbevtutil            from DEBUG to ERROR  
      Change log level of dis_frame            from DEBUG to ERROR  
      Change log level of dis_lldp             from DEBUG to ERROR  
      Change log level of dis_snmp             from DEBUG to ERROR  
      Change log level of dump_ds              from DEBUG to ERROR      

Encryption Command Tool

This script encrypts passwords to generate ciphertext.

Syntax
  • Windows:

    encrypt.bat 0 -stdin

    encrypt.bat 1 -stdin

    encrypt.bat 2 -stdin

    encrypt.bat old -stdin

    encrypt.bat -help

  • Linux:

    encrypt.sh 0 -stdin

    encrypt.sh 1 -stdin

    encrypt.sh 2 -stdin

    encrypt.sh old -stdin

    encrypt.sh -help

Path
  • eSight installation directory/eSight/tools/bmetool/encrypt
  • eSight installation directory/mttools/tools/bmetool/encrypt
Parameter Description

Parameter

Description

0 -stdin

0 indicates the AES encryption algorithm. The -stdin parameter is optional. The password to be encrypted must be obtained from the pipe if this parameter exists. This parameter is called by scripts. For details, see Example 2.

NOTE:

The password must contain 8 to 32 characters.

1 -stdin

1 indicates the AES encryption algorithm required by the OSS self-maintenance unit (OSMU). The -stdin parameter is optional. The password to be encrypted must be obtained from the pipe if this parameter exists. This parameter is called by scripts. For details, see Example 2.

NOTE:

The password must be one specific to OSMU, and cannot be used in other scenarios.

2 -stdin

2 indicates the PBKDF2 encryption algorithm. The -stdin parameter is optional. The password to be encrypted must be obtained from the pipe if this parameter exists. This parameter is called by scripts. For details, see Example 2.

NOTE:

The password must contain 8 to 32 characters.

old -stdin

old indicates the AES encryption algorithm. The -stdin parameter is optional. The password to be encrypted must be obtained from the pipe if this parameter exists. This parameter is called by scripts. For details, see Example 2.

NOTE:

The password must contain 8 to 32 characters.

-help

Displays help information.

Precautions

You are advised to run the command by entering encrypt.bat 0 or encrypt.bat 1 in interaction mode.

The -stdin parameter is used only by machine-to-machine interfaces to enter passwords using the pipe. For details, see Example 2.

Example
  • Windows
    Example 1:
    1. Log in to the server as the Administrator user.
    2. Start a CMD console.
    3. Run the following command to switch the directory.

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

    4. Run the following command to generate the ciphertext for the password:

      encrypt.bat 0

    5. Enter the new password as prompted.

      After the command is successfully executed, the following information is displayed:

      D:\iEMP\iEMP\tools\bmetool\encrypt>encrypt.bat 0
      Please input the password:
      
      Please input the password again:
      
      @010200000000c1544318a76ac71591f8590c697613e19a538cb50e82eca7552ca1be44366789
    Example 2:
    1. Log in to the server as the Administrator user.
    2. Start a CMD console.
    3. Run the following command to switch the directory.

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

    4. Run the following command to generate the ciphertext for the password:

      echo Changeme_123 | encrypt.bat 0 -stdin

      After the command is successfully executed, the following information is displayed:
      D:\iEMP\iEMP\tools\bmetool\encrypt> echo Changeme_123 |encrypt.bat 0 -stdin
      Please input the encrypt password:
      @010200000000c1544318a76ac71591f8590c697613e19a538cb50e82eca7552ca1be44366789
  • Linux
    Example 1:
    1. Log in to the server as the ossuser user.
    2. Run the following command to open the directory of the encrypt tool.

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

    3. Run the following command to generate the ciphertext for the password:

      ./encrypt.sh 0

    4. Enter the new password as prompted.

      After the command is successfully executed, the following information is displayed:

      ossuser@linux-z3tu:/opt/iEMP/iEMP/tools/bmetool/encrypt> ./encrypt.sh 0
      Please input the password:
      
      Please input the password again:
      
      @010200000000c1544318a76ac71591f8590c697613e19a538cb50e82eca7552ca1be44366789
    Example 2:
    1. Log in to the server as the ossuser user.
    2. Run the following command to open the directory of the encrypt tool.

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

    3. Run the following command to generate the ciphertext for the password:

      echo Changeme_123 | ./encrypt.sh 0 -stdin

      After the command is successfully executed, the following information is displayed:
      ossuser@linux-z3tu:/opt/iEMP/iEMP/tools/bmetool/encrypt> echo Changeme_123 |./encrypt.sh 0 -stdin
      Please input the encrypt password:
      @010200000000c1544318a76ac71591f8590c697613e19a538cb50e82eca7552ca1be44366789

Northbound SNMP Encryption Command

This command is used to encrypt the read and write community names of SNMPv1 and SNMPv2c northbound interfaces, and the user passwords of SNMPv3 in the snmpagent.xml file. The encryption ensures data transmission security.

Syntax
NOTE:

SNMPv1, SNMPv2c, and SNMPv3 are available. SNMPv1 and SNMPv2c have security risks. SNMPv3 is recommended.

  • Windows operating system: GenerateNBPass.bat -e
  • Linux operating system: GenerateNBPass -e
Path

eSight installation directory/AppBase/app/nbi/bin

Parameter Description

None

Prerequisites

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

Example
  • Windows operating system
    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 /d eSight installation directory/AppBase/app/nbi/bin

    3. Run the following command for encryption:

      GenerateNBPass.bat -e

    4. Enter a new password, and confirm the password as prompted.

      After the command is successfully executed, the following information is displayed:

      Encrypt password result: 9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d     
NOTE:
  • 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/AppBase/app/nbi/bin

    3. Run the following command for encryption:

      ./GenerateNBPass -e

    4. Enter a new password, and confirm the password as prompted.

      After the command is successfully executed, the following information is displayed:

      Encrypt password result: 9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d     
NOTE:

aestool

This command is used to encrypt a password.

Syntax

aestool e

aestool e password

aestool -modifykey keysize

aestool -help

Path
  • eSight installation directory/AppBase/tools
  • eSight installation directory/mttools/tools
Prerequisites

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

Parameter Description

Parameter

Description

e

Enters a password in interactive mode.

e password

Indicates the password to be encrypted.

-modifykey keysize

Modifies the Nginx encryption key. This command is invoked by the system but cannot be manually executed.

-help

Displays the help information.

Precautions

You are advised to use the aestool e command.

Example
  • Windows operating system
    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 /d eSight installation directory/AppBase/tools

    3. Run the following command to encrypt the password:

      aestool e

      Enter a new password, and confirm the password as prompted. After the command is successfully executed, the following information is displayed:

      9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d
  • 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/AppBase/tools

    3. Run the following command to encrypt the password:

      ./aestool e

      Enter a new password, and confirm the password as prompted.

      After the command is successfully executed, the following information is displayed:

      9d7961bc8af54d05ce509e03b13ffce3abc7587373e7719b62555fd5aff9908d

JKS2PFX

This command is used to convert a certificate generated using Java into a PEM certificate.

Syntax
  • Windows operating system

    JKS2PFX.bat <keystore> <password> <alias> <exportname>

    JKS2PFX.bat <keystore> <alias> <exportname>

    JKS2PFX.bat -help

  • Linux operating system

    JKS2PFX.sh <keystore> <password> <alias> <exportname>

    JKS2PFX.sh <keystore> <alias> <exportname>

    JKS2PFX.sh -help

Path
  • eSight installation directory/AppBase/tools/jks2pfx
  • eSight installation directory/mttools/tools/jks2pfx
Prerequisites

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

NOTE:

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

Parameter Description

Parameter

Description

keystore

Key store path before conversion.

password

Key store password. If this parameter is not transferred, the password is transferred in interactive mode.

alias

Key pair alias

exportname

Path of the converted key file.

-help

Help information.

Precautions

Ensure that the certificate contains a private key. Otherwise, the format conversion fails. You are advised to use JKS2PFX.bat <keystore> <alias> <exportname> in the Windows operating system and JKS2PFX.sh <keystore> <alias> <exportname> in the Linux operating system.

Example
  • Windows operating system

    JKS2PFX.bat mykestore test2 newkestore

    After the command is successfully executed, the following information is displayed:

    Enter the password: 
     Re-enter the password: 
     MAC verified OK
  • Linux operating system

    ./JKS2PFX.sh mykestore test2 newkestore

After the command is successfully executed, the following information is displayed:

Enter the password: 
 Re-enter the password: 
 Loading 'screen' into random state - done 
 MAC verified OK

keytool

Function

This command is provided by the JRE.

http://docs.oracle.com/javase/7/docs/

http://www.oracle.com/technetwork/java/javase/jre-7-readme-430162.html

http://regrunreanimator.com/research/uncategorized/javatmplatform/java.htm

Syntax
  • Windows: keytool.exe
  • Linux: keytool
Path
  • eSight installation directory/AppBase/jre/bin
  • eSight installation directory/AppBase/uninstall/ComptInsEnv/jre/jre_win/bin
  • eSight installation directory/AppBase/uninstall/ComptInsEnv/jre/jre_win_64/bin
  • eSight installation directory/AppBase/uninstall/jre/jre_win/bin
  • eSight installation directory/AppBase/uninstall/jre/jre_win_64/bin
  • eSight installation directory/AppBase/uninstall/jre/jre_linux/bin
  • eSight installation directory/mttools/jre/bin
  • eSight installation directory/AppBase/uninstall/ComptInsEnv/jre/jre_linux/bin
Prerequisites

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

NOTE:

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

Precautions

None

Example

None

resetSysPerm.sh

Command Function

This command is used to reset the permissions for the key configuration files in ${Produce name}/etc/iemp.mttools/kfilelist/*.properties.

Syntax

resetSysPerm.sh

Path

<Installation directory>/mttools/lbin

Prerequisites
  • You cannot configure different permission rules on a file. If different rules have been configured, the system cannot determine which rule takes effect.
  • If the permission for a file cannot be reset, the command continues to reset the permissions for other files.
  • If the permissions for all files are reset successfully, 0 is returned.
  • If the permission for a file cannot be reset, 1 is returned.
  • If the configuration file ${Produce name}/etc/iemp.mttools/kfilelist/*.properties does not exist, 2 is returned.
Example

None

Changing Server Keys

This command is used to change keys of all servers on eSight.

  • Windows operating system

    keymanager.bat -cmd modifyWorkKey

    keymanager.bat -cmd modifyRootKey

  • Linux operating system

    keymanager.sh -cmd modifyWorkKey

    keymanager.sh -cmd modifyRootKey

Path

eSight installation directory/mttools/bin

Parameter Description

None

Prerequisites
  • The command is executed by the Administrator user in the Windows operating system and by the ossuser user in the Linux operating system.
  • All eSight and maintenance tool processes are stopped.
Example
  • Windows operating system
    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 /d eSight installation directory/mttools/bin

    3. Run the following command to change the working keys of the entire system:

      keymanager.bat -cmd modifyWorkKey

      After the command is successfully executed, the following information is displayed:

      Modify work key successfully
  • Linux operating system
    1. Log in to the server as the ossuser user.
      NOTE:

      In a Veritas or OMMHA two-node cluster, you need to perform the operations only on the active server.

    2. Run the following command to switch the directory:

      cd eSight installation directory/mttools/bin

    3. Run the following command to change the working keys of the entire eSight system:

      ./keymanager.sh -cmd ModifyWorkKey

      After the command is successfully executed, the following information is displayed:

      Modify work key successfully

Upgrading OpenSSH

This command is used to upgrade OpenSSH. After the eSight patch package has been upgraded, run this command to upgrade OpenSSH.

Syntax

Windows: upgrade_mttools.bat

Path

eSight installation/eSight/uninstall/scripts/openssh

eSight installation/eSight/uninstall/ComptInsEnv/scripts/openssh

Prerequisites
  • On Windows, this operation is performed by the Administrator user.
  • During an OpenSSH upgrade, no backup and restoration tasks and other upgrade tasks are running.
  • In a distributed scenario, you cannot upgrade the maintenance tool and OpenSSH simultaneously.
Precautions

Rollback is not allowed after OpenSSH is upgraded.

Example

Windows

  1. Log in to the server as the Administrator user.
  2. Run the following command to access to the directory.

    cd /d eSight installation/eSight/uninstall/scripts/openssh

  1. Run the following command to upgrade OpenSSH:

    upgrade_openssh.bat

  2. Enter the password for the administrator as prompted.

After the command is executed, the task manager shows that the OpenSSHd service is running properly.

During the OpenSSH upgrade, the backup file "C:\openssh_bk" is generated. If a rollback is required because the upgrade is abnormal, manually delete the "C:\openssh" file, rename "C:\openssh_bk" "C:\openssh", and restart the OpenSSHd service.

Translation
Download
Updated: 2019-08-03

Document ID: EDOC1100044373

Views: 26939

Downloads: 90

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