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

FusionStorage 8.0.0 Software Installation 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).
Installing a Server Operating System

Installing a Server Operating System

Scenarios

  • Perform this operation only when management nodes and storage nodes do not use RA.
    • If management nodes and storage nodes are deployed separately, perform this operation on them separately.
    • If management nodes and storage nodes are deployed together, you only need to perform this operation on the storage nodes.
  • For details about the operating system type and version, see Compatibility. For details about how to install the operating system, see the related document of the official website. This section describes only the installation requirements.

Prerequisites

  • Operating system disks have been configured as RAID 1. For details about how to create a RAID, see the RAID Controller Card User Guide of the corresponding server.
  • You have obtained the operating system software package.
  • You have disabled the firewall of the installation PC.
  • You have obtained the user name and password of the server, such as users root and iBMC.
  • You have obtained the IP addresses of the server.
  • The system disks of a TaiShan server cannot be installed in slots on the front panel.

Procedure

  1. Install the operating system.

    For details about how to install the operating system, see the official website. This section describes only the requirements of FusionStorage for operating system partitions. Partition the operating system according to Table 2-23.

    • If partitions exist, delete all existing partitions and create partitions again.
    • The operating system language must be English.
    Table 2-23 Partition requirements

    Mount Point

    Description

    Recommended Partition Size (GB)

    /

    Indicates the system root directory.

    20

    swap

    Indicates the memory swap partition.

    20

    /boot

    Indicates the kernel of the operating system and the file used in the boot process.

    0.4

    /boot/efi

    This partition is required for the server that uses EFI BIOS.

    0.3

    /usr

    Indicates the directory used to store system programs.

    20

    /opt

    Indicates the directory used to store the third-party software.

    40

    /tmp

    Indicates the directory used to store temporary files generated by users or running programs.

    40

    /var

    Indicates the directory used to store changed data during system running.

    5

    /var/log

    Indicates the log partition.

    60

    /var/log/audit

    Indicates the audit log partition.

    1

    /var/crash

    Indicates the crash log partition.

    30

    /opt/zk_disk

    Indicates a directory used to store the data of ZooKeeper.

    65

    /opt/ccdb_disk

    Indicates a directory used to store global distributed configuration data.

    20

    /opt/ccdb_disk2

    Indicates another directory used to store global distributed configuration data.

    20

    /opt/data_accelerate

    Indicates the dedicated partition for the CCDB and ZooKeeper acceleration.

    5

    /opt/coffer_data

    Indicates the partition with power failure protection capabilities.

    32

    NOTE:

    /boot and /boot/efi must use independent partitions, and other partitions must use LVM logical partitions.

  2. For a V5 server, if the Secure Boot function is enabled in BIOS, disable the Secure Boot function by referring to Disabling the Secure Boot Function.
  3. Optional: Install the operating system dependency package.

    NOTE:

    The dependency package does not need to be installed for EulerOS.

    1. Log in to the operating system of a node.
    2. Run the following command to disable the firewall and disable firewall start upon node startup: If the firewall is not disabled, communication between storage nodes fails.

      The following commands are only examples. For details about the command operation guide, visit the official website of the corresponding operating system vendor.

      • Red Hat 6.9/6.10 and CentOS 6.9/6.10
        • To stop the firewall program, run the service iptables stop command.
        • To disable firewall start upon node startup, run the chkconfig iptables off command.
      • Red Hat 7.4/7.5/7.6, CentOS 7.4/7.5/7.6, and Oracle
        • To stop the firewall program, run the systemctl stop firewalld command.
        • To disable the firewall starting upon startup, run the systemctl disable firewalld command.
      • SUSE
        • Run the following commands to stop the firewall program:

          systemctl stop SuSEfirewall2.service

        • Run the following commands to disable firewall start upon node startup:

          systemctl disable SuSEfirewall2.service

    3. Run the following command to decompress the FusionStorage_Tools_version.tar.gz software package:

      tar -xzf FusionStorage_Tools_version.tar.gz

      Obtain the operating system dependency package scripts in the install_lib directory as follows:

      • Red Hat Linux: install_lib_for_rhel.sh
      • SUSE Linux: install_lib_for_suse.sh
      • CentOS Linux: install_lib_for_centos.sh
      • Oracle Linux: install_lib_for_oel.sh
    4. If a software repository is configured onsite, you need to modify the script.
      • SUSE Linux: Edit the install_lib_for_suse.sh file on the local host and modify the following fields:
        • Change the value of REPO_NAME to the actual name of the software repository. You can run the zypper lr command in the operating system to query the name of the software repository.
        • Change the value of ZYPPER_REPO_IS_EXIST to 1.
      • Other operating systems: Edit the file obtained in 3.c on the local host and change the value of YUM_REPO_IS_EXIST to 1.
    5. Upload the script to a directory on the node, for example, /tmp.
    6. Obtain the operating system image file. If the software repository is available, you do not need to obtain the operating system image file.
      • If images can be mounted, mount the operating system image file.
      • If images cannot be mounted, upload the local operating system image file to the node.
    7. Use PuTTY to log in to the first server using the management IP address as user root. For details, see Logging In to the Server Using PuTTY (Network Port Mode).
    8. Run the cd path command to go to the directory where the script for installing the dependency package is stored.
    9. Run the following script to install the operating system dependency package.
      • If images cannot be mounted, run the sh sh Operating system dependency package script Image file command. After the dependency package is installed, the server automatically restarts.

        Example: sh install_lib_for_rhel.sh /tmp/CentOS-7-x86_64-DVD-1611.iso

      • In other conditions, run the sh Operating system dependency package script command to install the operating system dependency package.

        The installation takes about 20 minutes. The time required depends on the hardware configuration and whether a software repository is used.

    10. Repeat the preceding steps to install the operating system dependency package on other nodes.

  4. Install the hardware driver.

    1. Install the NIC driver. For details, see the documents of the corresponding vendor. For details about how to install and maintain the 1822 network adapter, see Installation and Maintenance in the Huawei IN200 NIC User Guide.

      For example, run the following command to install the NIC driver of Mellanox:

      mlnxofedinstall --without-mlnx-nvme

      /etc/init.d/openibd restart

      NOTE:
      • Parameter without-mlnx-nvme indicates not to install the NVMe driver. You can run the mlnxofedinstall -h command to learn how to use the preceding command.
      • If the IB NIC and RoCE NIC use the same vendor's device and the device drivers are the same, install the driver only once. For example, the IB NIC and RoCE NIC of Mellanox use the same driver.
    2. Install related software of the main storage. For details, see the documents of the corresponding vendor.

      For ES3000, see Installation and Configuration in the ES3000 V5 NVMe PCIe SSD User Guide.

  5. If an operating system other than EulerOS is used, the sum of values of formatted LBA size and formatted metadata size of an NVMe device must be 512. If the sum of values is not 512, format the NVMe device again.

    1. Log in to a node as user root. For details, see Logging In to the Server Using PuTTY (Network Port Mode).
    2. Query information about the NVMe device.
      [root@FSA214 network-scripts]# hioadm info
      NVMe SSD Information
            Controller    Namespace
      |---- nvme0 (032BEGFSJ4000324) 
            |------------ nvme0n1 (3200.6GB)
    3. Check the NVMe device.
      [root@FSA214 network-scripts]# hioadm info -d nvme0
      Namespace<1> size:  3200.6GB,    3200631791616Byte
                   formatted LBA size:         512 Byte
                   formatted metadata size:    0 Byte
      maximum capacity              : 3200.6GB 
      current capacity              : 3200.6GB
      volatile write cache          : Enable
      serial number                 : 032BEGFSJ4000324
      model number                  : HWE36P43032M000N
      firmware version              : 3.10
      NVMe version                  : 1.2
      device status                 : healthy

      If the sum of values of formatted LBA size and formatted metadata size is not 512, perform 5.d to format the NVMe device.

    4. Format the NVMe device.
      [root@FSA214 network-scripts]# hioadm format -d nvme0 -t 0
      WARNING! The formatting operation will erase all user data.
      Proceed with this operation? (Y|N): y
      Formatting Progress...100%
      The formatting operation succeeded.
      The current LBA Format type : <0> lba=512  metadata=0

  6. The RAID configuration of main storage disks varies with RAID controller cards. For details about requirements, see Compatibility. For details, see the documents of the corresponding vendor.

After the operating system is installed on the TaiShan server, the system disk cannot be removed and inserted into the slots on the front panel.

Translation
Download
Updated: 2019-07-12

Document ID: EDOC1100081424

Views: 1763

Downloads: 7

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