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

Basic Storage Service Configuration Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5300 V5, 5500 V5, 5600 V5, 5800 V5, 6800 V5, 5300F V5, 5500F V5, 5600F V5, 5800F V5, 6800F V5, 18500 V5, 18800 V5, 18500F V5, and 18800F V5. It describes the basic storage services and explains how to configure and manage them.
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

After creating a storage pool, you must create LUNs in it and map the LUNs to hosts. This allows the hosts to use the storage resources provided by the storage pool.

Prerequisites

  • At least one storage pool has been created.
  • You are an administrator or super administrator.

Context

  • A thin LUN is a logical disk accessible to hosts. The system dynamically allocates storage resources to a thin LUN on demand within the capacity configured for the thin LUN.
  • A thick LUN, a logical disk accessible to hosts, 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 provide higher space utilization.
    • To use thin LUNs, you must import and activate the SmartThin license on the storage system.
  • A PE LUN does not provide storage space and therefore cannot be allocated any capacity.
  • You can only configure the owning controller of a PE LUN in its advanced properties.

Precautions

  • Before creating a LUN, clear any existing Available Space In The Storage Pool Is Insufficient alarm.
  • If a storage pool has thin LUNs and the capacity of all LUNs exceeds that of the storage pool, you are advised to expand the storage pool when the No Available Space In The Storage Pool alarm is reported.

Procedure

  1. Log in to DeviceManager.
  2. Choose Provisioning > LUN.
  3. Click Create.

    The Create LUN dialog box is displayed.

    NOTE:

    GUIs may vary with product versions and models. The actual GUIs prevail.

  4. Set basic properties for the LUN.

    Table 4-11 describes the related parameters.

    Table 4-11 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 must contain 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 newly created LUN by default.
    • If you want to manually set a LUN ID, do not select Automatic allocate. Instead, enter an ID manually.
    • When a single LUN is created, the value you enter is the ID of the LUN.
    • When creating LUNs in batches, the system automatically allocates an ID starting from the value you have entered to each LUN.

    [Example]

    Automatic allocate

    Use Type

    Use type of a LUN.

    • Common LUN

      Including thin LUNs and thick LUNs.

    • PE LUN

      PE LUNs are dedicated to 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

    You can enable SmartThin to create thin LUNs.

    NOTE:
    • SmartThin requires a license.
    • If SmartThin is enabled, the storage system creates thin LUNs and dynamically allocates storage capacity to thin LUNs based on the actual capacity used by hosts instead of allocating all the preset capacity to thin LUNs, achieving on-demand allocation.

    [Example]

    Disable

    Owning Storage Pool

    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]

    StoragePool001

    Capacity

    Capacity of a LUN.

    • When SmartThin is enabled, this parameter indicates the maximum capacity that can be allocated to a thin LUN. That is, the total storage resources dynamically allocated to the thin LUN cannot exceed the value of this parameter.
    • When SmartThin is disabled, this parameter indicates the capacity allocated to a thick LUN at a time.

    [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 system specifications.
    • The system can create block-level LUNs. To create a block-level LUN, select capacity unit Blocks. One block is 512 bytes.

    Use all the available 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 one batch. Set this parameter based on your needs.

    NOTE:
    • All LUNs created in a batch 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 configured start number, the system incrementally appends a suffix number to the name of each LUN for LUN distinction.

    [Value range]

    0 to (10000 – Number of LUNs to be created)

    NOTE:

    If you want to create 300 LUNs, the value range of the start number is 0 to 9700.

    NOTE:
    • By default, Start ID, Use Type, Manually specify the suffix, and Start Number are not displayed. To display these options, click All options.
    • When you configure Capacity and Quantity for LUNs, consider that the number of LUNs will affect the management complexity. For example, fifty 1 TB LUNs are easier to manage than a hundred of 500 GB LUNs.

  5. Optional: Set advanced properties for the LUN.

    • If a common LUN is created, perform the following steps:
      1. Click Advanced.

        The Advanced dialog box is displayed.

      2. Click the Properties and Tuning tabs to set related parameters.
        NOTE:

        GUIs may vary with product versions and models. The actual GUIs prevail.

        Table 4-12 Property 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 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 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 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 other storage tiers, first from the performance tier and then from the high-performance tier.
        NOTE:

        This parameter is not supported by some product versions or models. The actual GUIs prevail.

        [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 storage system supports the following read policies:

        • Resident: suitable for random access. The storage system caches data as long as possible to improve the read hit ratio.
        • Default: suitable for common access. The storage system strikes a balance between the read hit ratio and disk access performance.
        • Recycle: suitable for sequential access. The storage system 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 storage system supports the following write policies:

        • Resident: suitable for random access. The storage system caches data as long as possible to improve the write hit ratio.
        • Default: suitable for common access. The storage system strikes a balance between the write hit ratio and disk access performance.
        • Recycle: suitable for sequential access. The storage system 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. The storage system supports the following prefetch policies:

        • 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 storage system analyzes the continuity of read requests from hosts. If the read requests are continuous, the data following the current read request is prefetched from disks to the cache. In this way, the cache hit ratio can be increased. If the requests are random reads, the data is read directly from 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 disks each time when the cache reads data from the disks. The length is user-defined, ranging from 0 to 1024 KB.

          This policy is applicable to 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.

          This policy is applicable to sequential read applications with unfixed-size data blocks or 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

        Alarm Threshold (%)

        The system will generate a capacity alarm if the percentage of the used LUN capacity in the total LUN capacity reaches the specified alarm threshold.

        NOTE:

        This parameter applies only to LUNs enabled with SmartThin.

        [Value range]

        1 to 95

        [Default value]

        80

        Masquerading

        Masquerading replaces the identification information of local LUNs with that of heterogeneous remote LUNs to take over heterogeneous remote LUNs online.

        Inherited masquerading can be set for local LUNs. You can enable Inherited masquerading and set Remote Device. After Inherited masquerading is set for a LUN, the LUN can inherit the remote LUN's information, including the 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

        NOTE:

        Functions may vary with product models. For details, see the product description specific to your product model.

        Table 4-13 Tuning parameters

        Parameter

        Description

        Setting

        SmartTier Policy

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

        • 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 to promote 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 hot data.
        NOTE:
        • The SmartTier feature requires a license.
        • If LUN formatting is not complete, the data in the extents that are not formatted in the LUN will not be migrated.
        • This parameter is not supported by some product versions or models. The actual GUIs prevail.

        [Value range]

        The value can be No relocation, Automatic relocation, Relocation to high-performance tier, or Relocation to low-performance tier.

        [Example]

        No relocation

        [Default value]

        No relocation

        Priority Control

        Priority control of SmartQoS.

        NOTE:

        The SmartQoS feature requires a license.

        [Value range]

        The value can be Low, Medium, or High.

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

        [Example]

        Low

        [Default value]

        Low

        Traffic Control

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

        • Upper limit control: controls the upper limits of bandwidth and IOPS.
        • Lower limit control: controls the lower limits of bandwidth and IOPS and the upper limit of latency.

        If no traffic control policy exists, click Create to create one. For details, see "Creating a Traffic Control Policy" in the SmartQoS feature guide.

        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, or file systems that are working with a lower-limit traffic control policy.
        • The SmartQoS feature requires a license.

        [Value range]

        The value is user defined.

        [Example]

        -

        [Default value]

        -

        SmartCache Partition

        SmartCache partition for the LUN. In the scenario where reads are more than writes and hot data exists, SmartCache uses SSDs as cache to improve the system read performance.

        If no SmartCache partition exists, click Create to create one. For details, see "Creating a SmartCache Partition" in the SmartCache feature guide.

        NOTE:
        • The SmartCache feature requires a license.
        • Select the owning controller of a LUN manually. The controller must be the same as the owning controller of the SmartCache partition. Otherwise, SmartCache is unavailable.
        • SmartCache does not support self-encrypting SSDs.
        • This parameter is not supported by some product versions or models. The actual GUIs prevail.

        [Default value]

        -

        SmartDedupe&SmartCompression

        SmartDedupe and SmartCompression policies.

        • Enable deduplication: Upon receiving a data block, the storage system compares its fingerprint with those of existing data blocks. If the same fingerprint exists, the data block is considered as a duplicated one and is deleted.
        • Enable data compression: decreases the storage space occupied by data.
        NOTE:
        • SmartDedupe and SmartCompression require licenses and SmartThin be enabled.
        • SmartDedupe and SmartCompression can be enabled only during LUN creation.
        • SmartDedupe typically applies to Virtual Desktop Infrastructure (VDI). SmartCompression typically applies to databases, file services, engineering data, as well as earthquake and geological exploration data.
        • The efficiency of storage space saving is closely related to the type of data. SmartDedupe and SmartCompression are not recommended for:

          Non-duplicate archive data such as image files or encrypted data

          Data that has been compressed or encrypted by a hardware device or application (backup or archive application)

        [Value range]

        The value is user defined.

        [Example]

        -

        [Default value]

        -

        SmartPartition

        SmartPartition policies. SmartPartition allocates cache resources to LUNs to meet the cache hit ratio required by different applications.

        If no SmartPartition exists, click Create to create one. For details, see "Creating a SmartPartition" in the SmartPartition feature guide.

        NOTE:
        • The SmartPartition feature requires a 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.

        [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 4-14 describes the related parameter.
        Table 4-14 Advanced properties of a PE LUN

        Parameter

        Description

        Setting

        Owning Controller

        Owning controller of the PE LUN. You are advised to allocate LUNs to different 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. Click OK.

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

  7. Click Close.
Download
Updated: 2019-08-30

Document ID: EDOC1000181506

Views: 78473

Downloads: 590

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