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 V100R006C10 Block Storage Service Troubleshooting Guide 04

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).
Server OS Faults

Server OS Faults

Symptom

The server login fails.

Possible Causes

  • The operating system (OS) on the server is faulty.
  • Hardware on the server is faulty.

Fault Diagnosis

None

Procedure

    Install the server OS and hardware drives.

    1. Perform the required operation based on the deployment scenario of FusionStorage.

      • In the FusionSphere system, restore the server OS. For details, see Host OS Fault in the FusionSphere product documentation.

        Obtain the FusionSphere product documentation as follows:

        For enterprise users, log in to http://support.huawei.com/enterprise. For carrier users, log in to http://support.huawei.com. Enter FusionSphere in the search box, and click the path displayed below the search box to enter the product page.

      • In the Server SAN system:
        • If FusionStorage is deployed in the VMware vSphere system and the faulty server is a computing server deployed either in converged or separated mode, install an OS for the server according to the VMware vSphere help documentation. If the faulty server is a storage server deployed in separated mode, install an OS for the server by performing operations provided in the Installing Operating Systems for Storage Nodes of the FusionStorage Block Storage Service Software Installation Guide.
        • If FusionStorage is deployed in the Microsoft Hyper-V system and the faulty server is a computing server deployed either in converged or separated mode, install an OS for the server according to the Microsoft Hyper-V help documentation. If the faulty server is a storage server deployed in separated mode, install an OS for the server by performing operations provided in the Installing Operating Systems for Storage Nodes of the FusionStorage Block Storage Service Software Installation Guide.
        • If FusionStorage is deployed on physical servers, install an OS for the server by performing operations provided in the Installation Process (Server SAN Deployed on Physical Servers) > Installing Operating Systems of the FusionStorage Block Storage Service Software Installation Guide.

    2. Install hardware drives. For details about the requirements for hardware drives, see System Requirements in FusionStorage Block Storage Service Software Installation Guide.
    3. (Optional) If the faulty server accommodates the FSM VM, restore the FSM VM according to the restoration guidelines of A Single FSM VM Fails.

    Determine the server status.

    1. Perform the required operation based on the server type and status.

      • If the faulty server is in the control cluster, go to 22.
        Log in to the FusionStorage Block Self-Maintenance Platform and choose Resource Pool > Summary. In the right pane, the values displayed under Server Running MDC and ZooKeeper in the Control Cluster area specify the IP addresses of the control cluster servers, as shown in Figure 4-1.
        Figure 4-1  Control cluster servers

      • If the faulty server is a computing server in the non-control cluster, go to 9.
      • If the faulty server is a storage server or a computing-storage converged server in the non-control cluster and the storage resources on the server have been removed from the storage pool, go to 5.
      • If the faulty server is a storage server or a computing-storage converged server in the non-control cluster and the storage resources on the server have not been removed from the storage pool (displayed as faulty on the disk topology page), go to 22.

    Reduce the storage pool capacity.

    This operation is required only for a storage server or a computing-storage converged server.

    1. On the FusionStorage Block Self-Maintenance Platform, choose Resource Pool > Storage Pools.

      The Storage Pools page is displayed.

    2. Select the storage pool accommodating the faulty server and click Capacity Reduction.

      The Capacity Reduction page is displayed.

    3. Select the server to be deleted and click Confirm.

      After the server is successfully deleted, the Storage Pools page is displayed, and the FusionStorage Block storage pool capacity is reduced.

    4. (Optional) If the server has been added to multiple storage pools, delete this server from other storage pools. For details, see 6 to 7.

    Install FusionStorage Agent (FSA) for the server using the command-line interface (CLI).

    1. Use PuTTY to log in to the FSM node.

      Ensure that the management IP address and username dsware are used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run command to install FSA for the server.

      Before installing FSA, ensure that the blockstorage role on the faulty node has been removed. Otherwise, an installation error will be reported.

      • If the username and password are used for login authentication, run the following command:
        NOTE:

        Since the system has been hardened, you need to enter the username and password for login authentication after running the dswareTool command of FusionStorage Block. The default username is cmdadmin, and its default password is IaaS@PORTAL-CLOUD9!.

        The system supports authentication using environment variables so that you do not need to repeatedly enter the username and password for authentication each time you run the dswareTool command. For details, see Authentication Using Environment Variables in the FusionStorage Block Storage Service Software Installation Guide.

        sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackage -ip Management IP address of the node accommodating the new storage device -method install -rpmName DSwareAgent.tar.gz -force true

        Example command: sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackage -ip 192.168.12.21 -method install -rpmName DSwareAgent.tar.gz -force true

        1. Enter the user name and password of the server as prompted.

          If you log in to the server as user root, enter user name root and its password as prompted.

          If you log in to the server as a non-root user, enter the user name and its password as well as the password of user root as prompted.

        2. Enter the user name and password for authentication as prompted.
      • If the public and private keys are used for login authentication, run the following command:

        sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackageByPrivateKey -ip Management IP address of the node accommodating the new storage device -method install -rpmName DSwareAgent.tar.gz -force true -privateKey Private key file

        Example command: sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackageByPrivateKey -ip 192.168.36.21 -method install -rpmName DSwareAgent.tar.gz -force true -privateKey /home/omm/.ssh/id_rsa

    Expand the storage pool capacity.

    This operation is required only for a storage server or a computing-storage converged server.

    1. On the FusionStorage Block Self-Maintenance Platform, choose Resource Pool > Storage Pools.

      The Storage Pools page is displayed.

    2. Select the storage pool accommodating the faulty server and click Capacity Expansion.

      The Capacity Expansion page is displayed.

    3. Click Add Storage Node.
    4. Click Add Server.

      A dialog box is displayed.

    5. In Main Storage Type and Cache Type areas, configure main storage and cache information for the server to be added.

      The main storage type and cache type of the server to be added are the same as those of the faulty server. Set slots for the server in this step.

      Both the main storage and cache support the following configuration modes:
      • Batch Select: Enter slots and the number of disks. After the server is added, the system automatically adds the disks in the specified slots as main storage or cache resources.
      • Manual Select: Manually select main storage and cache resources after the server is added.

    6. In the server list, select the server to be added to the storage pool.
    7. Click Yes.

      The Capacity Expansion page is displayed.

    8. Click Expand.

      The Storage Pools page is displayed, and the FusionStorage Block storage pool capacity is expanded.

    9. (Optional) If the server has been added to multiple storage pools, add this server to other storage pools. For details, see 12 to 18.

    Restore the block storage client.

    This operation is required only for a computing server, a computing-storage converged server, or a disaster recovery server.

    1. Use PuTTY to log in to the FSM node.

      Ensure that the management IP address and username dsware are used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run the following commands one by one to restore the block storage client on the disaster recovery node:

      cd /opt/dsware/client/bin

      sh dswareTool.sh --op createDSwareClient -ip Management IP address of the disaster recovery node where the block storage client is to be restored -nodetype typeflag

      In the command, if the server accommodating the to-be-restored block storage client is a disaster recovery server, set the typeflag value to 1. Otherwise, set the typeflag value to 0.

      After this operation is complete, no further action is required.

    Install FSA for the server using the CLI.

    1. Use PuTTY to log in to the FSM node.

      Ensure that the management IP address and username dsware are used to establish the connection.

      If the public and private keys are used to authenticate the login, perform the operations based on Using PuTTY to Log In to a Node in Key Pair Authentication Mode in the FusionStorage Block Storage Service Administrator Guide.

    2. Run command to install FSA for the server.

      Before installing FSA, ensure that the blockstorage role on the faulty node has been removed. Otherwise, an installation error will be reported.

      • If the username and password are used for login authentication, run the following command:
        NOTE:

        Since the system has been hardened, you need to enter the username and password for login authentication after running the dswareTool command of FusionStorage Block. The default username is cmdadmin, and its default password is IaaS@PORTAL-CLOUD9!.

        The system supports authentication using environment variables so that you do not need to repeatedly enter the username and password for authentication each time you run the dswareTool command. For details, see Authentication Using Environment Variables in the FusionStorage Block Storage Service Software Installation Guide.

        sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackage -ip Management IP address of the node accommodating the new storage device -method install -rpmName DSwareAgent.tar.gz -force true

        Example command: sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackage -ip 192.168.12.21 -method install -rpmName DSwareAgent.tar.gz -force true

        1. Enter the user name and password of the server as prompted.

          If you log in to the server as user root, enter user name root and its password as prompted.

          If you log in to the server as a non-root user, enter the user name and its password as well as the password of user root as prompted.

        2. Enter the user name and password for authentication as prompted.
      • If the public and private keys are used for login authentication, run the following command:

        sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackageByPrivateKey -ip Management IP address of the node accommodating the new storage device -method install -rpmName DSwareAgent.tar.gz -force true -privateKey Private key file

        Example command: sh /opt/dsware/client/bin/dswareTool.sh --op rpmPackageByPrivateKey -ip 192.168.36.21 -method install -rpmName DSwareAgent.tar.gz -force true -privateKey /home/omm/.ssh/id_rsa

    Restore storage resources.

    1. In the CLI of the active FSM node you have logged in to as user dsware, run the required command to restore storage resources:

      • Non-control cluster node: sh /opt/dsware/client/bin/dswareTool.sh --op restoreStorageNode -ip Management IP address of the host accommodating the new storage device -p Storage pool ID

        Example command: sh /opt/dsware/client/bin/dswareTool.sh --op restoreStorageNode -ip 192.168.60.31 -p 0

        If the server has been added to multiple storage pools, run this command multiple times to restore storage resources in each storage pool.

      • Control cluster node:
        • Run the following command to restore the control cluster node:

          sh /opt/dsware/client/bin/dswareTool.sh --op restoreControlNode -ip Management IP address of the node accommodating the new storage device

          Example command: sh /opt/dsware/client/bin/dswareTool.sh --op restoreControlNode -ip 192.168.60.31

        • Run the following command to restore the storage node:

          sh /opt/dsware/client/bin/dswareTool.sh --op restoreStorageNode -ip Management IP address of the node accommodating the new storage device -p Storage pool ID

          Example command: sh /opt/dsware/client/bin/dswareTool.sh --op restoreStorageNode -ip 192.168.60.31 -p 0

          If the server has been added to multiple storage pools, run this command multiple times to restore storage resources in each storage pool.

    2. (Optional) If this server has the block storage client deployed, restore the block storage client.

      For details, see 20 to 21.

Translation
Download
Updated: 2019-02-01

Document ID: EDOC1000175245

Views: 3178

Downloads: 3

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