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

FusionInsight HD 6.5.0 Administrator Guide 02

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).
Changing a Key

Changing a Key

Scenario

The administrator needs to periodically change the access key to ensure data key security.

Prerequisites

  • You have obtained the SetupTool, and upload the tool script to the active management node.
  • You have prepared a string of characters as the content of a new access key.
  • All root users of nodes share the same password.

Procedure

  1. Use PuTTY to log in to the active management node as user root.
  2. Run the following command to disable PuTTY logout upon timeout:

    TMOUT=0

  3. Run the following command to go to the directory where SetupTool is decompressed, for example, the cluster directory in /opt/FusionInsight_SetupTool.

    cd /opt/FusionInsight_SetupTool/preinstall/tools/cluster

  4. Run the following command to generate a key file. The key file name can be changed to a new one based on the site requirements, for example,keyfile.

    dd if=/dev/random of=keyfile bs=4k count=1

  5. Run the following command to change the access key to a new key file.

    sh replace_cluster_key.sh Access key New key file

    Among the preceding command, Access key indicates a specified key to be changed and its values can be accessKey1or accessKey2.

    accessKey1 indicates a primary access key and accessKey2 indicates a secondary access key.

    New key file indicates the path of the access key. If the key file is not in the current directory, its full path is required.

    For example, if you use the keyfile key to change the primary access key, run the following command:

    sh replace_cluster_key.sh accessKey1 keyfile

    If the following information is displayed, the access key is successfully changed. By default, the primary access keys are changed for all nodes on which the encrypted partitions are enabled in the cluster.

    Success to replace cluster key 1 with /opt/FusionInsight_SetupTool/preinstall/tools/cluster/keyfile.

Download
Updated: 2019-05-17

Document ID: EDOC1100074522

Views: 6170

Downloads: 12

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