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

SmartMulti-Tenant Feature Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, 6800F V5, 18500 V5, 18500F V5, 18800 V5, and 18800F V5. This document describes the implementation principles and application scenarios of the SmartMulti-Tenant feature. Also, it explains how to configure and manage SmartMulti-Tenant.
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).
Creating a LUN

Creating a LUN

The storage space of a newly created storage pool cannot be identified by the host. The host can use the storage space only after the storage space of the storage pool is divided into LUNs and the LUNs are mapped to the host.

Prerequisites

At least one storage pool has been created. If the storage system has no storage pool, create one first.

Context

  • As a logical disk accessible to hosts, a thin LUN is configured with an initial capacity when created and then dynamically allocated required storage resources when its available capacity is insufficient.
  • As a logical disk accessible to hosts, a thick LUN is allocated the specified capacity during the creation based on the automatic provisioning technology.
NOTE:
  • When a host initially reads data from and writes data to a storage system, thick LUNs deliver better performance and thin LUNs boasts higher space utilization.
  • If you want to use a thin LUN, you need to import and activate the SmartThin license in the storage device.
  • A PE LUN does not provide storage space. Therefore, it cannot be allocated any capacity.
  • In the advanced properties of a PE LUN, you can only configure its owning controller.
  • Super administrators, administrators, SAN resource administrators, vStore administrators, and vStore data protection administrators can create a LUN.

Procedure

  1. Log in to DeviceManager.
  2. Go to the LUN page.

    The operation path varies with user types:

    • System user: Click vStore, select the desired vStore, and click Details to go to the vStore view. Choose Provisioning > LUN.
    • vStore user: In the vStore view, choose Provisioning > LUN.

  3. Click Create.

    The Create LUN dialog box is displayed.

  4. Set basic properties for the LUN.

    Table 3-8 describes related parameters.

    Table 3-8 LUN parameters

    Parameter

    Description

    Value

    Name

    Name of a newly created LUN.

    [Value range]

    • The name must be unique.
    • The name can contain only letters, digits, periods (.), underscores (_), and hyphens (-).
    • The name contains 1 to 31 characters.

    [Example]

    LUN001

    Description

    Description of a LUN.

    [Example]

    -

    Start ID

    ID of a LUN.

    NOTE:
    • The system automatically allocates an ID to a new created LUN by default.
    • If you want to manually set a LUN ID, do not select Automatic allocate and enter an ID manually.
    • When creating a single LUN, the value you enter is the ID of the LUN.
    • When creating LUNs in batches, the system automatically allocates an ID to each LUN, starting from the specified value.

    [Example]

    2

    Use Type

    Use type of a LUN.

    • Common LUN

      A logical disk accessible to the host, including thin LUN and thick LUN.

    • PE LUN

      PE LUNs are used only as VVOL LUNs in VMware software defined storage. VVOL provides storage space for VMs. A PE LUN is used as an I/O demultiplexer to simplify the connection between a VM and a VVOL LUN. VM I/Os are sent to the corresponding VVOL LUN through a PE LUN.

    [Default value]

    Common LUN

    SmartThin

    Enables the SmartThin function for you to create thin LUNs.

    NOTE:
    • To apply this function, you must apply for a SmartThin license.
    • After SmartThin is enabled, the storage system does not allocate the configured capacity to the LUN at a time. Within configured capacity, the storage system allocates the storage resource to the LUN on demand, based on the actual capacity used by the host.

    [Example]

    Enable

    Owning Storage Pool

    The storage pool to which the LUN you are creating belongs.

    NOTE:

    If the storage system has no storage pool, click Create to create one.

    [Example]

    Storagepool002

    Capacity

    Capacity of a LUN. A user specifies the capacity when creating a LUN.

    • When SmartThin is enabled, the maximum capacity will be allocated to a thin LUN. The maximum capacity means the total capacity dynamically allocated to the thin LUN.
    • When SmartThin is disabled, a fixed capacity will be allocated to a thick LUN.

    [Value range]

    • The maximum capacity of thick LUNs must be less than or equal to the available capacity of the storage pool.
    • The maximum capacity of thin LUNs must be less than or equal to its specifications.
    • The system support creating block-level LUN. Select capacity unit Blocks when creating LUN. One block equals to 512 bytes.

    [Example]

    5 GB

    Use all the free capacity of the owning storage pool

    If this option is selected, all free space of the owning storage pool is allocated to this LUN.

    [Example]

    -

    Quantity

    Number of LUNs created in a batch. Set this parameter based on your need.

    NOTE:
    • LUNs created in batches have the same capacity.
    • The total capacity of LUNs created in batches must be less than or equal to the available capacity of the storage pool.

    [Value range]

    1 to 500

    [Example]

    2

    Manually specify the suffix

    When creating multiple LUNs, the system automatically appends a suffix number to each LUN name for LUN distinction. You can manually set the start suffix number after selecting this option.

    NOTE:

    If this option is not selected, the suffix number starts at 0000 by default.

    [Example]

    -

    Start Number

    This parameter is valid after Manually specify the suffix is selected. From the start number you configured, the system incrementally appends a suffix number to the name of each LUN for LUN distinction.

    [Value range]

    0 to (10000 - the quantity of LUNs to create)

    NOTE:

    If you want to create 300 LUNs, the start number is from 0 to 9700.

    NOTE:

    Start ID, Use Type, Manually specify the suffix, and Start Number are hidden options. If you want to display these options, click All options.

  5. (Optional) Set advanced properties for the LUN.

    • If a common LUN is created, execute the following steps.
      1. Click Advanced. The Advanced dialog box is displayed.
      2. Set advanced properties for the LUN. Click the Properties and Tuning tabs to set related parameters, as described in Table 3-9 and Table 3-10 respectively.
        Table 3-9 Properties parameters

        Parameter

        Description

        Value

        Owning Controller

        Owning controller of a LUN.

        • For a dual-controller storage system, possible values are as follows:
          • Auto select: The system automatically specifies the owning controller of LUNs and allocates LUNs evenly to different controllers by default.
          • CTE0.A: Allocates LUNs in the storage system to controller A.
          • CTE0.B: Allocates LUNs in the storage system to controller B.
        • For a four-controller storage system, possible values are as follows:
          • Auto select: The system automatically specifies the owning controller of LUNs and allocates LUNs evenly to different controllers by default.
          • CTE0.A: Allocates LUNs in the storage system to controller A.
          • CTE0.B: Allocates LUNs in the storage system to controller B.
          • CTE0.C: Allocates LUNs in the storage system to controller C.
          • CTE0.D: Allocates LUNs in the storage system to controller D.
        NOTE:
        • To allocate LUNs to controllers for load balancing, you are advised to select Auto select.
        • For a four-controller storage system, after a LUN is created, its owning controller can switch between only paired controllers, that is, between controller A and controller B, or between controller C and controller D.

          For example, if you select CTE0.A as the owning controller when creating a LUN, you can select only CTE0.A or CTE0.B as LUN's owning controller when modifying the LUN's advanced properties.

        [Value range]

        Based on actually available controllers of the storage system.

        [Example]

        Auto select

        [Default value]

        Auto select

        Initial Capacity Allocation Policy

        Policy for the storage tier to allocate capacity to a LUN

        • Automatic allocation: The storage system allocates capacity to a LUN from the performance tier first. If the capacity of the performance tier is insufficient, the storage system allocates capacity from the other storage tiers, first from the capacity tier and then from the high performance tier.
        • Allocate from the high performance tier first: The storage system allocates capacity to a LUN from the high performance tier first. If the capacity of the high performance tier is insufficient, the storage system allocates capacity from the other storage tiers, first from the performance tier and then from the capacity tier.
        • Allocate from the performance tier first: The storage system allocates capacity to a LUN from the performance tier first. If the capacity of the performance tier is insufficient, the storage system allocates capacity from the other storage tiers, first from the capacity tier and then from the high performance tier.
        • Allocate from the capacity tier first: The storage system allocates capacity to a LUN from the capacity tier first. If the capacity of the capacity tier is insufficient, the storage system allocates capacity from the other storage tiers, first from the performance tier and then from the high performance tier.

        [Value range]

        The value can be Automatic allocation, Allocate from the high performance tier first, Allocate from the performance tier first, or Allocate from the capacity tier first.

        [Example]

        Automatic allocation

        [Default value]

        Automatic allocation

        Read Policy

        Data read policy of a cache.

        The system supports the following read policies.

        • Resident: It is suitable for random access. The policy caches data as long as possible to improve the read hit ratio.
        • Default: It is suitable for common access. The policy strikes a balance between the read hit ratio and disk access performance.
        • Recycle: It is suitable for sequential access. The policy releases idle cache resources as soon as possible for other services to use.

        [Value range]

        The value can be Resident, Default, or Recycle.

        [Example]

        Resident

        [Default value]

        Default

        Write Policy

        Data write policy of a cache.

        The system supports the following write policies.

        • Resident: It is suitable for random access. The policy caches data as long as possible to improve the write hit ratio.
        • Default: It is suitable for common access. The policy strikes a balance between the write hit ratio and disk access performance.
        • Recycle: It is suitable for sequential access. The policy releases idle cache resources as soon as possible for other services to use.

        [Value range]

        The value can be Resident, Default, or Recycle.

        [Example]

        Resident

        [Default value]

        Default

        Prefetch Policy

        Read mode of a LUN. When reading data, the storage system prefetches required data from disks to the cache in advance according to a preset policy.

        • No prefetch: The storage system reads data based on the read length specified in the I/O request.

          As a low read hit ratio may lead to performance degradation, No prefetch is recommended for random read services.

        • Intelligent prefetch: The smart prefetch analyzes the continuity of the read requests from the host. If the read requests are continuous, the data following the current read request is prefetched from hard disks to the cache. In this way, the cache hit ratio can be increased. If they are not, the data is read directly from hard disks.

          This policy is applicable to the scenario where sequential reads and random reads coexist or to the read applications that cannot be determined sequential or random.

        • Constant prefetch: A constant length of data is read from hard disks every time when the cache reads data from the hard disks. The length is user-defined, ranging from 0 to 1024 KB.

          Constant prefetch is applicable to the sequential read applications with fixed-size data blocks, for example, ring back tone (RBT) and requests initiated by multiple users for playing multimedia on demand at the same bit rate.

        • Variable prefetch: The cache reads data from disks based on a multiple of the read length specified in the I/O request. The multiple is user-defined, ranging from 0 to 1024 KB.

          This policy is applicable to the sequential read applications that have an unfixed size or for the multi-user concurrent read applications whose prefetch data amount cannot be determined, for example, requests initiated by multiple users for playing multimedia on demand at different bit rates.

        [Value range]

        The value can be No prefetch, Intelligent prefetch, Constant prefetch, or Variable prefetch.

        [Example]

        Intelligent prefetch

        [Default value]

        Intelligent prefetch

        Masquerading

        Masquerading replaces the identification information of the LUN on the local device with that on the heterogeneous remote device so that heterogeneous remote LUNs can take over online.

        Inherited Masquerading can be set for local LUNs. Enable Inherited Masquerading and select Remote Device. After Inherited Masquerading is set for a LUN, the LUN can inherit the LUN information on the remote device. The information includes VID, PID, and SCSI protocol version.

        NOTE:

        Inherited masquerading enables local LUN masquerading for LUN capacity expansion when the remote device has insufficient LUN space.

        [Default]

        Disabled

        Table 3-10 Tuning parameters

        Parameter

        Description

        Setting

        SmartTier Policy

        Policy for the storage system to relocate data among storage tiers.

        NOTE:
        • To apply this policy, you must apply for the SmartTier license.
        • If LUN formatting is not complete, the data in the extents that are not formatted in the LUN is not migrated.
        • No relocation: Select this policy when the access frequency of the LUN is stable and the current storage tier is suitable for the services.
        • Automatic relocation: Select this policy when you are unclear about the service type and access frequency of the LUN. This policy enables the storage system to collect and analyze performance data and then relocate data among storage tiers based on the activity level of the data.
        • Relocation to high-performance tier: Select this policy when data on the LUN is frequently accessed. This policy enables the storage system promotes data to a storage tier with better performance, improving access efficiency.
        • Relocation to low-performance tier: Select this policy when data on the LUN will not be accessed after a period of time. This policy enables the storage system to relocate data to a storage tier that provides moderate performance at a low cost, releasing high-performance storage space for hotspot data.

        [Value range]

        Possible values are No relocation, Automatic relocation, Relocation to high-performance tier, and Relocation to low-performance tier.

        [Example]

        No relocation

        [Default value]

        No relocation

        Priority Control

        Priority control of the SmartQoS.

        NOTE:

        To apply this policy, you must apply for the SmartQoS license.

        The system provides three priorities:

        • Low
        • Medium
        • High

        [Value range]

        The value can be Low, Medium, or High.

        A LUN, snapshot or file system with a high priority can obtain system resources preferentially. You can set different values for specific LUNs or snapshots based on service priorities, ensuring critical service performance.

        [Example]

        Low

        [Default value]

        Low

        Traffic Control

        Traffic control policy of the SmartQoS. There are two types of traffic control policies:

        • Upper-limit traffic control policy: controls the upper limits of bandwidth and IOPS.
        • Lower-limit traffic control policy: controls the lower limits of bandwidth and IOPS and the upper limit of latency.
        NOTE:
        • You can only select LUNs, snapshots and file systems with high I/O priority for a lower-limit traffic control policy, and you must not change the priorities of the LUNs, snapshots and file systems that are working with a lower-limit traffic control policy.
        • To apply this policy, you must apply for the SmartQoS license.

        If no traffic control policy exists, click Create to create one.

        [Value range]

        The value is user defined.

        [Example]

        -

        [Default value]

        -

        SmartCache Partition

        To specify SmartCache partition for the LUN. In the scenario that read operations are more than write operations and hot spot data exists, use the SSDs as cache by employing SSD high read performance to improve system read performance.

        NOTE:
        • To apply this policy, you must apply for SmartCache license.
        • Select the owning controller of a LUN manually. The controller must be the same as the owning controller of SmartCache. Otherwise, SmartCache is unavailable.
        • If no SmartCache partition exists, click Create to create one.

        [Default value]

        -

        SmartDedupe&SmartCompression

        The SmartDedupe and SmartCompression policy.

        NOTE:
        • SmartDedupe and SmartCompression are value-added features. To make the policy take effect, you need to apply for the licenses of SmartDedupe and SmartCompression and enable the SmartThin function.
        • Enable data compression: Decrease the storage space occupied by data.
        • Enable deduplication: After the finger prints of data blocks being compared, the data blocks with same finger prints are confirmed as the same data blocks. The duplicated data block is deleted and only the original data block is kept.
        NOTE:

        Virtual Desktop Infrastructure (VDI) is a typical application scenario of SmartDedupe. Database, file service, and engineering, earthquake, and geological exploration data are typical application scenarios of SmartDedupe.

        The efficiency of storage space saving is closely related to the type of data. Regarding the choice of feature, comply with the following rules:

        • For non-duplicate archive data such as image files or encrypted data, you are advised not to use SmartDedupe and SmartCompression.
        • For data that has been compressed or encrypted by a hardware device or application (backup or archive application), you are advised not to use SmartDedupe and SmartCompression.

        [Value range]

        The value is user defined.

        [Example]

        -

        [Default value]

        -

        SmartPartition

        To specify SmartPartition for the LUN. SmartPartition allocates cache resources of the storage system to the LUN to meet the cache hit ratio required by different applications.

        NOTE:
        • To apply this policy, you must apply for SmartPartition license.
        • Select the owning controller of a LUN manually. The controller must be the same as the owning controller of SmartPartition. Otherwise, SmartPartition is unavailable.

        If no SmartPartition exists, click Create to create one.

        [Default value]

        -

      3. Click OK. The Create LUN dialog box is displayed.
    • If a PE LUN is created, perform the following steps.
      1. Click Advanced. The Advanced dialog box is displayed.
      2. Select the owning controller of the PE LUN. Table 3-11 describes the related parameter.
        Table 3-11 Advanced properties of PE LUN

        Parameter

        Description

        Setting

        Owning Controller

        Owning controller of a LUN. You are advised to allocate LUNs to controllers for load balancing.

        If you are not sure about the owning controller, select Auto select. The storage system will automatically select the owning controller for the LUN.

        [Example]

        Auto select

      3. Click OK. The Create LUN dialog box is displayed.

  6. Confirm the creation of the LUN.

    1. Click OK.

      The Execution Result dialog box is displayed, indicating that the operation succeeded.

    2. Click Close.

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181478

Views: 29587

Downloads: 182

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