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

eSight V300R010C00 Operation Guide 08

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).
Resource Configuration Management

Resource Configuration Management

Describes how to create a storage pool configuration task.

Creating a Storage Pool Configuration Task

Describes how to create a storage pool configuration task.

Prerequisites

Disk domains have been created on storage devices.

Context

You can batch create storage pools on storage devices.

Procedure
  1. On the menu bar, choose Resource > Storage Subnet.

  2. In the navigation tree, choose Storage Resources Allocation > Resource Configuration.
  3. Enter a name and description.

    For example:

    Name: Pool_01

    Description: S5800 storage pool configuration template

  4. Select Storage pool configuration as the configuration policy.
  5. From the Available Devices interface information, select the storage device to be configured.
  6. In Storage Pool Configuration, set configuration parameters.

    Table 10-33 Storage pool configuration parameters

    Parameter

    Description

    Example

    Basic Configuration

    Configuration

    You can create a new configuration task or to use an existing configuration task.

    Create new configuration

    Storage pool name

    Name of a storage pool.

    If multiple storage pools are created, a suffix is added to each storage pool name to distinguish the names from each other, for example, Pool5800_001.

    Pool5800

    Capacity

    Capacity of a storage pool.

    512 GB

    Number of storage pools

    Number of storage pools.

    5

    Total capacity

    Total capacity of storage pools

    -

    Advanced Configuration

    Storage media

    You can divide storage media that provides the same performance into a storage tier, set a RAID policy for each tier, and allocate capacity to each tier based on performance requirements.

    • High-performance tier (SSD): This tier provides the highest performance and contains costly storage media with small per disk capacity. This tier is applicable to applications that has high requirements for random read and write performance, for example, database indexes.
    • Performance tier (SAS): This tier provides relative high performance and contains reasonably priced storage media with relative large per disk capacity. This tier is highly reliable and applicable to common online applications.
    • Capacity tier (NL-SAS): This tier provides the lowest performance and contains storage media of low prices with large per disk capacity. This tier is applicable to non-critical applications such as backup.
    • High-performance tier (SSD)

      RAID 1 (2D)

      2 GB

    • Performance tier (SAS)

      RAID 5 (4D+1P)

      6 GB

    • Capacity tier (NL-SAS)

      RAID 6 (4D+2P)

      12 GB

    Capacity alarm threshold (%)

    Alarms will be reported when the storage pool capacity usage exceeds the threshold.

    For example, if the storage pool capacity is 20 GB and the alarm threshold is 80%, an alarm will be reported when the used storage capacity exceeds 16 GB.

    80

    Data migration granularity

    Data dynamically flows in the form of data migration units across different storage tiers.

    The default value of 4 MB is recommended. The value cannot be changed after being set.

    If you want to adjust the data migration granularity in different application scenarios such as stream media and video surveillance, contact technical support engineers.

    4 MB

  7. If you want to save the configured parameters as a common configuration task, select Save as a common configuration and enter a name for the task.
  8. If you want to create LUNs on the storage pool, select Continue to create LUNs and set LUN configuration parameters.

    Table 10-34 LUN configuration parameters

    Parameter

    Description

    Example

    Basic Configuration

    Configuration

    You can create a new configuration task or to use an existing configuration task.

    Create new configuration

    LUN name

    Name of a LUN.

    If multiple LUNs are created, a suffix is added to each LUN name to distinguish the names from each other, for example, LUN5800_0001.

    LUN5800

    Capacity

    Capacity of a LUN

    64 GB

    Thin

    After the thin function is enabled, the system allocates an initial capacity to a LUN, instead of allocating all LUN capacity at one time, and then dynamically adjusts the LUN capacity based on the capacity usage of hosts, achieving on-demand resource allocation.

    Initial capacity: 1 GB

    NOTE:

    Storage pool overcommitment ratio = Total capacity of all LUNs in a storage pool/Capacity of the storage pool

    The total capacity of all LUNs in a storage pool cannot be greater than the product of the capacity of the storage pool multiplied by the overcommitment ratio. Generally, the overcommitment ratio is not less than 1. The default value is 0.

    Initial capacity: 1 GB

    Number of LUNs

    Number of LUNs.

    8

    Total Capacity

    Total capacity of LUNs.

    512

    Advanced Configuration

    Initial Capacity Allocation Policy

    Storage tier to which capacity is preferentially allocated.

    Automatic allocation

    Cache Policy

    Read policy: cache read policy.

    • Resident: Applies to randomly accessed services, ensuring that data can be cached if possible to improve the read hit ratio.
    • Default: Applies to regular services, striking a balance between the hit ratio and disk access performance.
    • Recycle: Applies to sequentially accessed services, releasing cache resources for other services as soon as possible.

    Write policy: cache write policy.

    • Resident: Applies to randomly accessed services, ensuring that data can be cached if possible to improve the write hit ratio.
    • Default: Applies to regular services, striking a balance between the hit ratio and disk access performance.
    • Recycle: Applies to sequentially accessed services, releasing cache resources for other services as soon as possible.

    Read policy: Default

    Write policy: Default

    Prefetch Policy

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

    • No prefetch: The storage system reads data according to the prefetch 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: Intelligent 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 data is randomly read, no prefetch is performed and the data is read from disks. This policy applies to a scenario where sequential reads and random reads coexist or a scenario where you cannot determine data reads to be sequential or random.
    • Constant prefetch: A constant length of data is read from disks every time the cache reads data from the disks. The length is user-definable, ranging from 0 to 1024. This policy applies to sequential read applications with fixed-size data, for example, color ring back tone (CRBT) and multi-user streaming media video on demand (VoD) initiated by users at the same bit rate.
    • Variable prefetch: A variable length of data is read from disks every time the cache reads data from disks. The length is a multiple of that specified in the host I/O request. The multiple is user-defined, ranging from 0 to 1024. This policy applies to sequential read applications with variable-size data or to multi-user concurrent read applications with an unknown data prefetch amount, for example, multi-user streaming media VoD initiated by users at different bit rates.

    Intelligent prefetch

  9. If you want to save the configured parameters as a common configuration task, select Save as a common configuration and enter a name for the task.
  10. Confirm the configuration information and click Execute.

    A message box is displayed.

  11. Click OK.

    You can click to view the task execution results.

    The task details will be displayed on the Tasks page.

Creating a LUN Configuration Task

Describes how to create a LUN configuration task.

Prerequisites

Storage pools have been created on the storage device where you want to create LUNs.

Context

You can create a LUN configuration task to batch create LUNs in storage pools on the specified storage devices. After the task is created, the system automatically creates the same LUNs in the specified resource pools.

Procedure
  1. On the menu bar, choose Resource > Storage Subnet.

  2. In the navigation tree, choose Storage Resources Allocation > Resource Configuration.
  3. Enter a name and description.

    For example:

    Name: LUN_01

    Description: S5800 LUN configuration

  4. Select LUN configuration as the configuration policy.
  5. From the Available Devices interface information, click Add to add the storage pool to be configured.

    You can select the storage pool to be configured in multiple storage devices for several times.

  6. In LUN Configuration, set configuration parameters.

    Table 10-35 LUN configuration parameters

    Parameter

    Description

    Example

    Basic Configuration

    Configuration

    You can create a new configuration task or to use an existing configuration task.

    Create new configuration

    LUN name

    Name of a LUN.

    If multiple LUNs are created, a suffix is added to each LUN name to distinguish the names from each other, for example, LUN5800_0001.

    LUN5800

    Capacity

    Capacity of a LUN

    64 GB

    Thin

    After the thin function is enabled, the system allocates an initial capacity to a LUN, instead of allocating all LUN capacity at one time, and then dynamically adjusts the LUN capacity based on the capacity usage of hosts, achieving on-demand resource allocation.

    Initial capacity: 1 GB

    NOTE:

    Storage pool overcommitment ratio = Total capacity of all LUNs in a storage pool/Capacity of the storage pool

    The total capacity of all LUNs in a storage pool cannot be greater than the product of the capacity of the storage pool multiplied by the overcommitment ratio. Generally, the overcommitment ratio is not less than 1. The default value is 0.

    Initial capacity: 1 GB

    Number of LUNs

    Number of LUNs.

    8

    Total Capacity

    Total capacity of LUNs.

    512

    Advanced Configuration

    Initial capacity allocation policy

    Storage tier to which capacity is preferentially allocated.

    Automatic allocation

    Cache Policy

    Read policy: cache read policy.

    • Resident: Applies to randomly accessed services, ensuring that data can be cached if possible to improve the read hit ratio.
    • Default: Applies to regular services, striking a balance between the hit ratio and disk access performance.
    • Recycle: Applies to sequentially accessed services, releasing cache resources for other services as soon as possible.

    Write policy: cache write policy.

    • Resident: Applies to randomly accessed services, ensuring that data can be cached if possible to improve the write hit ratio.
    • Default: Applies to regular services, striking a balance between the hit ratio and disk access performance.
    • Recycle: Applies to sequentially accessed services, releasing cache resources for other services as soon as possible.

    Read policy: Default

    Write policy: Default

    Prefetch Policy

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

    • No prefetch: The storage system reads data according to the prefetch 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: Intelligent 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 data is randomly read, no prefetch is performed and the data is read from disks. This policy applies to a scenario where sequential reads and random reads coexist or a scenario where you cannot determine data reads to be sequential or random.
    • Constant prefetch: A constant length of data is read from disks every time the cache reads data from the disks. The length is user-definable, ranging from 0 to 1024. This policy applies to sequential read applications with fixed-size data, for example, color ring back tone (CRBT) and multi-user streaming media video on demand (VoD) initiated by users at the same bit rate.
    • Variable prefetch: A variable length of data is read from disks every time the cache reads data from disks. The length is a multiple of that specified in the host I/O request. The multiple is user-defined, ranging from 0 to 1024. This policy applies to sequential read applications with variable-size data or to multi-user concurrent read applications with an unknown data prefetch amount, for example, multi-user streaming media VoD initiated by users at different bit rates.

    Intelligent prefetch

  7. If you want to save the configured parameters as a common configuration task, select Save as a common configuration and enter a name for the task.
  8. Confirm the configuration information and click Execute.

    A message box is displayed.

  9. Click OK.

    You can click to view the task execution results.

    The task details will be displayed on the Tasks page.

Creating a Host Mapping Configuration Task

Describes how to create a host mapping configuration task.

Prerequisites

LUN resources are available on storage devices.

Context

You can create a host mapping configuration task to map LUNs of the specified storage devices to hosts. After the task is created, the system automatically maps the desired LUNs to the specified hosts. You can map LUNs to the existing hosts or newly added hosts.

Procedure
  1. On the menu bar, choose Resource > Storage Subnet.

  2. In the navigation tree, choose Storage Resources Allocation > Resource Configuration.
  3. Enter a name and description.

    For example:

    Name: Hostmap_01

    Description: common configuration for Host01

  4. Select Mapping configuration as the configuration policy.
  5. In Protocol type, select the host networking protocol.
  6. Select the host to which you want to map LUNs.
  7. If you want to add a new host, click Add Host in the upper right corner of Selected Devices.
  8. Set configuration parameters.

    Table 10-36 Host mapping configuration parameters

    Parameter

    Description

    Example

    Configuration

    You can create a new configuration task or to use an existing configuration task.

    Create a new configuration task.

    Mapping mode

    • Sharing: All hosts share mapped LUNs. It is recommended that the hosts be in one cluster.
    • Exclusive: Each host exclusively uses mapped LUNs.

    Sharing

    Host group name

    Name of the host group to which a host belongs.

    Host1

    Number of LUNs

    Number of LUNs to be mapped. The value varies depending on the mapping mode (sharing or exclusive).

    If the number of LUNs to be mapped is N:

    • N LUNs are mapped to all hosts when the sharing mode is used.
    • N LUNs are mapped to each host when the exclusive mode is used.

    5

    Capacity

    Capacity of a mapped LUN.

    64 GB

    LUN type

    Type of a mapped LUN.

    • Thin LUN: After the thin function is enabled for a LUN, the system allocates an initial capacity to the LUN, instead of allocating all LUN capacity at one time, and then dynamically adjusts the LUN capacity based on the capacity usage of hosts, achieving on-demand resource allocation.
    • Thick LUN: LUN for which the thin function is disabled.
    NOTE:

    Storage pool overcommitment ratio = Total capacity of all LUNs in a storage pool/Capacity of the storage pool

    The total capacity of all LUNs in a storage pool cannot be greater than the product of the capacity of the storage pool multiplied by the overcommitment ratio. Generally, the overcommitment ratio is not less than 1. The default value is 0.

    Thick LUN

    Performance

    Performance of a mapped LUN.

    • Automatic: Automatically selects a LUN.
    • High: Selects a LUN from the high performance tier.
    • Medium: Selects a LUN from the performance tier.
    • Low: Selects a LUN from the capacity tier.

    Automatic

  9. If you want to save the configured parameters as a common configuration task, select Save as a common configuration and enter a name for the task.
  10. In the Available Devices area, click Add to add the storage pool to be configured.

    You can select the storage pool to be configured in multiple storage devices for several times.

  11. Confirm the configuration information and click Execute.

    A message box is displayed.

  12. Click OK.

    You can click to view the task execution results.

    The task details will be displayed on the Tasks page.

Configuring Resources Using a Template

To batch configure resources with different specifications for devices, you can use a template to create multiple resource configuration tasks.

Procedure
  1. On the menu bar, choose Resource > Storage Subnet.

  2. In the navigation tree, choose Storage Resources Allocation > Resource Configuration.

    The template configuration page is displayed.

  3. Click the download link in Download Template.

    Save the EXCEL template to a local computer.

  4. Select the configuration operations that you want to perform, fill parameters and information in related tables, and save the EXCEL file.

    For details about the parameters, see Creating a Storage Pool Configuration Task, Creating a LUN Configuration Task, Creating a Host Mapping Configuration Task.

    NOTE:

    Carefully read requirements and restrictions on the Homepage tab page of the template and fill in the contents based on the requirements in the template.

  5. Click in Upload to select the configured EXCEL template file.
  6. Click Upload to upload the EXCEL template.

    After the template is uploaded, the information about the devices is displayed.

    NOTE:

    By default, devices with correct information entries are selected. If an entry of information is incorrectly entered, this entry is dimmed and an error message is displayed.

  7. From the Template Configuration Type drop-down list, select the template configuration type.
  8. Select the devices to be configured and click OK.

    The configuration starts.

    • If the configuration is successful, Success is displayed in the Result column.
    • If the information about some devices that fail to be configured, modify the information and configure the storage devices again.

Translation
Download
Updated: 2019-08-03

Document ID: EDOC1100044378

Views: 63937

Downloads: 344

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