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 V100R006C20 Block Storage Service Software Installation 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).
Configuring the 10GE Network

Configuring the 10GE Network

Scenarios

If a server uses the 10GE NIC, perform operations in this section to enable the NIC.

Prerequisites

Conditions

  • The FSA nodes have been installed.
  • The control cluster has not been created.
  • The NIC driver has been installed.

Data

You have obtained the management IP addresses of the FSA nodes.

Procedure

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

      Ensure that username dsware and the management plane floating IP address are used to establish the connection. The default password of user dsware is IaaS@OS-CLOUD9!.

      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.

    2. Run the following command to switch to the specified directory:

      cd /opt/dsware/client/bin

    3. Run the following command to bind network ports in batches:

      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.

      • Using VLANs:

        sh dswareTool.sh --op batchCreatePortAggr -n fsb_bond -p Port name -m 1 -ip Management IP address of the FSA node

        Example command: sh dswareTool.sh --op batchCreatePortAggr -n fsb_bond -p eth2,eth3 -m 1 -ip 192.168.1.110-192.168.1.112,192.168.1.114

      • Not using VLANs:

        sh dswareTool.sh --op batchCreatePortAggr -n fsb_data0 -p Port name -m 1 -ip Management IP address of the FSA node

        Example command: sh dswareTool.sh --op batchCreatePortAggr -n fsb_data0 -p eth2,eth3 -m 1 -ip 192.168.1.110-192.168.1.112,192.168.1.114

      NOTE:
      • The management IP address of the FSA node can be either an IP address or an IP address segment.
      • After the command is successfully executed, take note of the taskid value in the command output.
      • If the command execution fails, you can run the sh dswareTool.sh --op deleteBond -n bondName -ip ip1-ip2,ip3... command to delete the failed bond port. Then use the command provided by the OS to create bond ports on the FSA node. For details, see the OS's official document.

    4. Run the following command to query whether the bonded port has been successfully created:

      sh dswareTool.sh --op queryTaskInfo -id taskid

      taskid specifies the taskid value obtained in 3.

      If the obtained task status is partially succeeded, you can run the sh dswareTool.sh --op queryChildrenTaskInfo -id taskid command to query information about the failed subtasks.

    5. Run the following command to enter editing mode of the IP configuration file:

      vi /opt/dsware/client/conf/ip_config.xml

    6. Press i to enter editing mode.
    7. Modify configuration information.

      Table 8-14 lists the configuration parameters to be modified.

      Table 8-14  Configuration parameters

      Parameter

      Description

      nodeMgrIp

      Specifies the management IP address of the FSA node.

      name

      The value must be fsb_data0.

      bondName

      Specifies the name of the bonded port to be created in the storage plane VLAN.
      • If VLANs are used, set this parameter to fsb_bond.
      • If VLANs are not used, set this parameter to fsb_data0.
      NOTE:
      If the node OS is Red Hat Linux 6.5 or earlier, or CentOS 6.5 or earlier, the VLAN name cannot be set to fsb_data0. Use the actual VLAN name of the storage plane, and the format is vlan+vlanId, for example, vlan3.

      vlanId

      Specifies the VLAN ID of the storage plane. If VLANs are not used, this parameter does not need to be configured.

      netAddr

      Specifies the storage IP addresses of the FSA nodes to be configured. The sequence and number of the storage IP addresses must be consistent with those set in nodeMgrIp.

      netMask

      Specifies the subnet mask of the storage plane.

      gateway

      Specifies the gateway of the storage plane. If this parameter is not planned, you do not need to set it.

    8. Press Esc and enter :wq to save the modification and exit the vi editor.
    9. Run the following command to configure storage IP addresses of FSA nodes in batches:

      sh dswareTool.sh --op batchSetServerIp -f /opt/dsware/client/conf/ip_config.xml

      After the command is successfully executed, take note of the taskid value in the command output.

    10. Run the following command to query whether the storage IP addresses have been successfully configured:

      sh dswareTool.sh --op queryTaskInfo -id taskid

      taskid specifies the taskid value obtained in 9.

      If the obtained task status is partially succeeded, you can run the sh dswareTool.sh --op queryChildrenTaskInfo -id taskid command to query information about the failed subtasks.

Translation
Download
Updated: 2019-06-29

Document ID: EDOC1100016637

Views: 25481

Downloads: 14

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