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 an eDevLUN

Creating an eDevLUN

After an eDevLUN is created, you can map it to an application server or use it to configure value-added services. eDevLUNs reside in storage pools on the local storage system.

Prerequisites

  • The remote LUNs mapped by the heterogeneous storage devices have been added to the LUN list by automatic scanning.
  • Number of LUNs (including local LUNs and eDevLUNs) in a storage pool = Available capacity of the storage pool/512 MB. Before creating an eDevLUN, make an appropriate plan to ensure that the storage pool has sufficient capacity for the eDevLUN.
  • The status of the external LUN must be normal.
  • If external LUNs to be taken over reside on a heterogeneous Huawei device, eDevLUNs can be created without the SmartVirtualization license. If external LUNs to be taken over reside on a heterogeneous third-party device, the SmartVirtualization license is required to create eDevLUNs.

Context

  • By default, the LUN Write Policy of the eDevLUN is Write through. The write policy of the masqueraded eDevLUN cannot be modified after created. It can be modified only when you manually take over the masqueraded eDevLUN by CLI.
  • After eDevLUNs are created, you can modify a write policy for eDevLUNs in the Advanced tab of eDevLUN properties.
  • Super administrators, administrators, SAN resource administrators, and vStore administrators can create an eDevLUN.

Precautions

Remote LUNs on a heterogeneous device that have been mapped to the local storage system cannot be mapped to other hosts or storage systems.

Procedure

  1. Log in to DeviceManager.
  2. Go to the eDevLUN 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 > More > Create eDevLUN.
    • vStore user: In the vStore view, choose Provisioning > LUN > More > Create eDevLUN.

  3. Choose a heterogeneous remote device that you want to create an eDevLUN on and click OK.

    The Create eDevLUN dialog box is displayed.

  4. Create an eDevLUN.

    1. Select a storage pool for the eDevLUN to be created.
      NOTE:
      • When you create eDevLUNs, the system automatically generates a default name which can be modified for every eDevLUN.
      • If there is no available storage pool, click Create to create one.
    2. Select a type of LUN masquerading for the eDevLUN to be created.

      LUN masquerading indicates replacing identification information for LUNs on the local device with that for LUNs on the remote device to take over heterogeneous LUNs on the remote device online.

      • Basic masquerading: This type replaces the basic information about an eDevLUN with the basic information (such as the WWN) about an external LUN when the LUN is taken over. If UltraPath V100R008C20 or later is installed on the application server, select basic masquerading.
      • Extended masquerading: This type replaces the basic information as well as extended LUN information including the SCSI protocol version and master controller when the LUN is taken over. If UltraPath V100R008C20 or earlier or third-party multipath software is installed on the application server, select extended masquerading.
      • Not masquerading: This type applies to offline takeover. The services of the local storage system are interrupted temporarily when it is taking over heterogeneous devices. If you want to create eDevLUNs for external LUNs on third-party storage devices, you can only select this type of LUN masquerading.

        After a masqueraded eDevLUN is created, you need to manually take over it by CLI, or you cannot perform the value-added service configuration. For details about manually taking over a masqueraded eDevLUN, refer to SmartVirtualization Feature Guide.

    3. Select a remote LUN that you want to create as an eDevLUN in the lower list.
    4. (Optional) Click Advanced, and set the advanced properties of the eDevLUN.
      1. Set the advanced properties of the eDevLUN. Click the Properties and Tuning tabs to set related parameters, as described in Table 5-4 and Table 5-5 respectively.
        Table 5-4 Properties parameters

        Parameter

        Description

        Setting

        Owning Controller

        Owning controller of an eDevLUN. You are advised to allocate eDevLUNs 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 eDevLUN.

        [Example]

        Auto select

        Read Policy

        Update rate of data in a cache. Possible values are Resident, Default, and Recycle.

        The system supports the following read policies.

        • Resident: For random cache access. Data is retained in cache the longest to improve the read hit ratio.
        • Default: For regular cache access. Keep balance between read hit ratio and disk access performance.
        • Recycle: For sequential cache access. The idle cache resources are released for other access requests.

        [Value range]

        The value can be Resident, Default, or Recycle.

        [Example]

        Default

        [Default value]

        Default

        Write Policy

        Update rate of data in a cache. Possible values are Resident, Default, and Recycle.

        The system supports the following write policies.

        • Resident: For random cache access. Data is retained in cache the longest to improve the write hit ratio.
        • Default: For regular cache access. Keep balance between write hit ratio and disk access performance.
        • Recycle: For sequential cache access. The idle cache resources are released for other access requests.
        NOTE:

        If the LUN Write Policy of eDevLUN is Write through, this parameter is invalid.

        [Value range]

        The value can be Resident, Default, or Recycle.

        [Example]

        Default

        [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

        LUN Write Policy

        The LUN write policy can be:

        • Write back: Data is written onto the cache. The cache schedules the data and writes the data to disks.
        • Write through: Data is directly written onto disks without passing the cache.
        NOTE:

        Writing data onto the cache is fast. Therefore, write back delivers better write performance than write through.

        [Value range]

        The value can be Write back and Write through.

        [Example]

        Write through

        [Default value]

        Write through

        Table 5-5 Tuning parameters

        Parameter

        Description

        Setting

        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.

        [Example]

        Low

        [Default value]

        Low

        Traffic Control

        Traffic control policy of the SmartQoS.

        NOTE:

        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 eDevLUN. 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 the eDevLUN manually, and this controller must be the same as the owning controllers of SmartCache partition, or SmartCache is unavailable.

        If no SmartCache partition exists, click Create to create one.

        [Default value]

        -

        SmartPartition

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

        NOTE:
        • To apply this policy, you must apply for SmartPartition license. Some device models do not support this feature. For details about device models that support this feature, see Product Documentation from the Support website or consult the product provider.
        • Select the owning controller of eDevLUN manually, and this controller must be the same as the owning controllers of SmartPartition, or SmartPartition is unavailable.

        If no SmartPartition exists, click Create to create one.

        [Default value]

        -

      2. Click OK.

  5. Confirm the creation of the eDevLUN.

    1. Click OK.

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

    2. Click Close.

Follow-up Procedure

After creating an eDevLUN, the eDevLUN is created successfully when Used or Not of the remote LUN in the lower information area is Yes. Then you can choose Provisioning > LUN to view and manage the eDevLUN.

Before configuring a value-added feature for an eDevLUN without masquerading properties, comply with the following principles to modify the write policy of the eDevLUN:

  • If you want to configure the HyperMirror feature for the eDevLUN, set the write policy of the eDevLUN to Write through and the write policy of the mirror copy generated on the local storage system to Write back to ensure data consistency between the heterogeneous storage system and the local storage system.
  • If the SmartMigration feature is configured for the eDevLUN, set the write policy of the eDevLUN to Write through to ensure data consistency between the heterogeneous storage system and local storage system.
  • If the snapshot, remote replication, or HyperMetro is configured for the eDevLUN, set the write policy of the eDevLUN to Write back to ensure performance of the local storage system.
  • If HyperMirror and snapshot, HyperMirror and remote replication, or HyperMirror and HyperMetro are configured simultaneously for the eDevLUN, set the write policy of the eDevLUN to Write back.
  • If no value-added feature is configured for the eDevLUN, you do not need to modify its write policy. Keep the default Write through policy.
Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181478

Views: 32283

Downloads: 196

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