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

File Access and Protocols Feature Guide 13

OceanStor 18500 V3 and 18800 V3 Mission Critical Storage System V300R003

This document describes the implementation principles and application scenarios of the NAS feature. Also, it explains how to configure and manage NAS.
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 a Network

Configuring a Network

This section describes how to use DeviceManager to configure IP addresses for a storage system.

Procedure

  1. Log in to DeviceManager and choose Provisioning > Port.

    The Port page is displayed.

  2. Optional: Create a bond port.

    Port bonding provides more bandwidth and redundancy for links. After Ethernet ports are bonded, MTU changes to the default value and you must set the link aggregation mode for the ports. On Huawei switches, you must set the ports to work in static LACP mode.

    • The port bond mode of a storage system has the following restrictions:
      • On the same controller, a bond port is formed by a maximum of eight Ethernet ports.
      • Only the interface modules with the same port rate (GE or 10GE) can be bonded.
      • The port cannot be bonded across controllers. Non-Ethernet network ports cannot be bonded.
      • SmartIO cards cannot be bonded if they work in cluster or FC mode or run FCoE service in FCoE/iSCSI mode.
      • The MTU value of the SmartIO port must be the same as that of the host.
      • Read-only users are unable to bind Ethernet ports.
      • Each port only allows to be added to one bonded port. It cannot be added to multiple bonded ports.
      • Physical ports are bonded to create a bond port that cannot be added to the port group.
    • Although ports are bonded, each host still transmits data through a single port and the total bandwidth can be increased only when there are multiple hosts. Determine whether to bond ports based on site requirements.
    • The link aggregation modes vary with switch manufacturers. If a non-Huawei switch is used, contact technical support of the switch manufacturer for specific link aggregation configurations.

    1. In Ethernet Ports, select a Ethernet port and click More > Bond Port.

      The Bond Port dialog box is displayed.

    2. Enter bond port information. Table 3-4 describes related parameters.

      Table 3-4  Bond port parameters

      Parameter

      Description

      Value

      Bond Name

      Name of the bond port.

      [Example]

      bond01

      Available Ports

      Ports that you select and ports to which you want to bond the selected ports.

      [Example]

      CTE0.A.IOM1.P0

    3. Click OK.

      The Danger dialog box is displayed.

    4. Select I have read and understood the consequences associated with performing this operation. And click OK.
  3. Create a logical port.

    NOTE:
    The number of logical ports created for each controller is recommended not more than 64. If the number exceeds 64 and a large number of ports do not work properly, logical ports drift towards the small number of ports available. As a result, service performance deteriorates.

    1. Select Logical Ports and click Create.

      The Create Logical Port dialog box is displayed.

    2. Enter logical port information. Table 3-5 describes related parameters.

      Table 3-5  Create Logical Port parameters

      Parameter

      Description

      Value

      Name

      Name of the logical port.

      [Example]

      logip

      IP Address Type

      Type of the IP address: IPv4 Address or IPv6 Address.

      [Example]

      IPv4 Address

      IPv4 Address (IPv6 Address)

      IP address of the logical port.

      [Example]

      172.16.128.10

      Subnet Mask (Prefix)

      Subnet mask (Prefix) of the logical port.

      [Example]

      255.255.255.0

      IPv4 Gateway (IPv6 Gateway)

      Address of the gateway.

      [Example]

      172.16.128.1

      Primary Port

      Physical port preferred by the logical port.

      [Example]

      CTE0.A.IOM0.P0

      IP Address Floating

      Whether IP address floating is enabled.

      OceanStor 18500 V3/18800 V3 support IP address floating. When the primary port is disabled, the IP address will be floated to another port that can be used. For details, see OceanStor 18500 V3&18800 V3 Mission Critical Storage System V300R003 IP Address Floating Deployment Guide.
      NOTE:

      Shares of file systems do not support the multipathing mode. IP address floating is used to improve reliability of links.

      [Example]

      Enable

      Failback Mode

      Failback mode of the IP address: Automatic and Manual.
      NOTE:
      • If Failback Mode is Manual, ensure that the link to the primary port is normal before the failback. Services will manually fail back to the primary port only when the link to the primary port keeps normal for over five minutes.
      • If Failback Mode is Automatic, ensure that the link to the primary port is normal before the failback. Services will auto fail back to the primary port only when the link to the primary port keeps normal for over five minutes.

      [Example]

      Automatic

      Activate Now

      Whether the logical port is activated immediately. After activated, the logical IP can be used to access the shared space.

      [Example]

      Enable

    3. Click OK.

      The Success dialog box is displayed.

    4. Click OK.
  4. Optional: Managing a Route.

    You need to configure a route when the CIFS server and the storage system are not on the same network.

    • When a domain controller server exists, ensure that the logical IP addresses, domain controller server, and DNS can ping each other. If they cannot ping each other, add routes from the logical IP addresses to the network segment of the domain controller server and the DNS.
    • When configuring CIFS share access, if the CIFS server and logical IP addresses cannot ping each other, add a route from the logical IP addresses to the network segment of the CIFS server.

    1. Select the locical port for which you want to add a route and click Route Management.

      The Route Management dialog box is displayed.

    2. Configure the route information for the logical port.

      1. In IP Address, select the IP address of the logical port.
      2. Click Add.
        The Add Route dialog box is displayed.

        The default IP addresses of the internal heartbeat on the dual-controller storage system are 127.127.127.10 and 127.127.127.11, and the default IP addresses of the internal heartbeat on the four-controller storage system are 127.127.127.10, 127.127.127.11, 127.127.127.12, and 127.127.127.13. Therefore, the IP address of the router cannot fall within the 127.127.127.XXX segment. Besides, the IP address of the gateway cannot be 127.127.127.10, 127.127.127.11, 127.127.127.12, or 127.127.127.13. Otherwise, routing will fail. (Internal heartbeat links are established between controllers for these controllers to detect each other's working status. You do not need to separately connect cables. In addition, internal heartbeat IP addresses have been assigned before delivery, and you cannot change these IP addresses).

      3. In Type, select the type of the route to be added.
        There are three route options:
        • Default route

          Data is forwarded through this route by default if no preferred route is available. The target address field and the target mask field (IPv4) or prefix (IPv6) of the default route are automatically set to 0. To use this option, you only need to add a gateway.

        • Host route

          The host route is the route to an individual host. The target mask (IPv4) or prefix (IPv6) of the host route are automatically set respectively to 255.255.255.255 or 128. To use this option, you only need to add the target address and a gateway.

        • Network segment route

          The network segment route is the route to a network segment. You need to add the target address, target mask (IPv4) or prefix (IPv6), and gateway. Such as the target address is 172.17.0.0, target mask is 255.255.0.0, and gateway is 172.16.0.1.

      4. Set Destination Address.
        • If IP Address is an IPv4 address, set Destination Address to the IPv4 address or network segment of the application server's service network port or that of the other storage system's logical port.
        • If IP Address is an IPv6 address, set Destination Address to the IPv6 address or network segment of the application server's service network port or that of the other storage system's logical port.
        • Set Destination Mask (IPv4) or Prefix (IPv6).
        • If a Destination Mask is set for an IPv4 address, this parameter specifies the subnet mask of the IP address for the service network port on the application server or storage device.
        • If a Prefix is set for an IPv6 address, this parameter specifies the prefix of the IPv6 address for application server's service network port or that of the other storage system's logical port.
      5. In Gateway, enter the gateway of the local storage system's logical port IP address.

    3. Click OK. The route information is added to the route list.

      The Danger dialog box is displayed.

    4. Confirm the information of the dialog box and select I have read and understood the consequences associated with performing this operation..
    5. Click OK.

      The Success dialog box is displayed indicating that the operation succeeded.

      NOTE:

      To remove a route, select it and click Remove.

    6. Click Close.
Translation
Download
Updated: 2019-08-14

Document ID: EDOC1000084098

Views: 32834

Downloads: 72

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