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 V300R009C00 Operation Guide 10

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).
Storage Resource Allocation

Storage Resource Allocation

Storage Resource Allocation Introduction

Definition

eSight storage resource allocation function allows you to batch create storage pools, LUNs, and host mappings for different types of storage devices and provides resource reclamation function, achieving unified storage resource allocation and management.

Functions

The following functions can be implemented:

  • You can batch create storage pools, LUNs, and mappings on multiple storage devices.
    Figure 10-25 Creating a resource allocation task

  • Enables you to run the customized configuration script on the storage devices for user-defined configuration.
    Figure 10-26 Create a customized configuration

  • Resource reclamation. For LUNs that have been mapped to hosts, remove the mapping and delete the LUNs. For LUNs that have not been mapped to any hosts, directly delete the LUNs.
    Figure 10-27 Create a resource reclamation task

  • You can save configuration tasks as common configurations for subsequent use.

Application Restrictions

Only eSight that is equipped with the storage device management component can use the storage resource allocation function.

Key Parameters

None

Getting to Know Resource Configuration

eSight unified storage resource management platform allows you to batch create storage pools, LUNs, and host mappings for different types of storage devices, achieving unified storage resource allocation and management. When there is a large number of storage devices or hosts, you need to plan the storage resources. eSight allows you to integrate the storage resources into storage pools and LUNs and map them to specific hosts.

You can use eSight to flexibly configure resources on the web page or using customized scripts. You can also save configurations as common configuration tasks and directly use them next time.

NOTE:
  • Resource configuration tasks that have been executed cannot be undone, modified, or deleted. You need to plan resources and prepare data in advance. You can use the device management software to modify the resources that have been configured.
  • Storage pools can be created only in hard disks of the SSD, SAS, and NL-SAS types.
The resource configuration function is applicable to the following storage devices:
  • OceanStor 18800F(V100R001C00/V100R001C10/V100R001C20/V100R001C30)
  • OceanStor 18500/18800(V100R001C00/V100R001C10/V100R001C20/V100R001C30/V300R003/V300R006C00)
  • OceanStor S2600T/S5500T/S5600T/S5800T/S6800T(V200R002C00/V200R002C10/V200R002C20)
  • OceanStor S2600T/S5500T/S5600T/S5800T (V200R002C30)
  • OceanStor 2200 V3(V300R005C00/V300R006C00)
  • OceanStor 2600 V3(V300R001/V300R002/V300R005C00/V300R006C00)
  • OceanStor 2600F V3(V300R006C00)
  • OceanStor 2600 V3 for Video(V300R005C01)
  • OceanStor 2800 V3(V300R001/V300R002/V300R003C00/V300R003C20/V300R005C00/V300R006C00)
  • OceanStor 5100 V3(V300R001/V300R002)
  • OceanStor 5300 V3(V300R006C01)
  • OceanStor 5500 V3(V300R006C01)
  • OceanStor 5500F V3(V300R006C00)
  • OceanStor 5600F V3(V300R006C00)
  • OceanStor 5800F V3(V300R006C00)
  • OceanStor 6800 V3(V300R006C01)
  • OceanStor 6800 V3/5800 V3/5600 V3/5500 V3/5300 V3(V300R001/V300R002/V300R003/V300R005C00/V300R006C00)
  • OceanStor 6800F V3(V300R006C00)
  • OceanStor 6900 V3(V300R001/V300R002)
  • OceanStor 18500 V3(V300R006C01)
  • OceanStor 18800F V3(V300R006C00)
  • OceanStor 2600F V3/18500 V3/5800F V3/5500 V3/6800 V3/2800 V3/2200 V3/2600 V3/5300 V3/5800 V3/5500F V3/5600 V3/5600F V3/6800F V3/18800F V3/18800 V3/18500F V3(V300R006C10)
  • OceanStor 2100 V3/2200 V3/2600 V3/2600F V3/2600 V3 for Video/2800 V3/5300 V3/5500 V3/5600 V3/5800 V3/6800 V3/18500 V3/18800 V3/5500F V3/5600F V3/5800F V3/6800F V3/18500F V3/18800F V3(V300R006C20/V300R006C30)
  • OceanStor 2800 V5/5300 V5/5500 V5/5500 V5 Elite/5600 V5/5800 V5/6800 V5/18500 V5/18800 V5/5300F V5/5500F V5/5600F V5/5800F V5/6800F V5/18500F V5/18800F V5(V500R007C00/V500R007C10/V500R007C20)
The customized configuration function is applicable to the following storage devices:
  • OceanStor 18500/18800(V300R003/V300R006C00)
  • OceanStor 2200 V3(V300R005C00/V300R006C00)
  • OceanStor 2600 V3(V300R002/V300R005C00/V300R006C00)
  • OceanStor 2600F V3(V300R006C00)
  • OceanStor 2800 V3(V300R002/V300R001C00/V300R003C00/V300R003C20/V300R005C00/V300R006C00)
  • OceanStor 5100 V3(V300R002)
  • OceanStor 5300 V3(V300R006C01)
  • OceanStor 5500 V3(V300R006C01)
  • OceanStor 5500F V3(V300R006C00)
  • OceanStor 5600F V3(V300R006C00)
  • OceanStor 5800F V3(V300R006C00)
  • OceanStor 6800 V3(V300R006C01)
  • OceanStor 6800 V3/5800 V3/5600 V3/5500 V3/5300 V3(V300R002/V300R003/V300R005C00/V300R006C00)
  • OceanStor 6800F V3(V300R006C00)
  • OceanStor 6900 V3(V300R002)
  • OceanStor 18500 V3(V300R006C01)
  • OceanStor 18800F V3(V300R006C00)
  • OceanStor 2600F V3/18500 V3/5800F V3/5500 V3/6800 V3/2800 V3/2200 V3/2600 V3/5300 V3/5800 V3/5500F V3/5600 V3/5600F V3/6800F V3/18800F V3/18800 V3/18500F V3(V300R006C10)
  • OceanStor 2100 V3/2200 V3/2600 V3/2600F V3/2600 V3 for Video/2800 V3/5300 V3/5500 V3/5600 V3/5800 V3/6800 V3/18500 V3/18800 V3/5500F V3/5600F V3/5800F V3/6800F V3/18500F V3/18800F V3(V300R006C20/V300R006C30)
  • OceanStor 2800 V5/5300 V5/5500 V5/5500 V5 Elite/5600 V5/5800 V5/6800 V5/18500 V5/18800 V5/5300F V5/5500F V5/5600F V5/5800F V5/6800F V5/18500F V5/18800F V5(V500R007C00/V500R007C10/V500R007C20)

Configuration Categories

  • Creating configuration tasks
    • Creating storage pools

      You can batch create storage pools on storage devices.

    • Creating LUNs

      You can batch create LUNs in the storage pool of the specified device.

    • Creating host mappings

      You can map the LUNs of the specified storage device to hosts.

    • Creating customized configuration scripts

      You can execute customized configuration scripts on storage devices.

  • Creating common configuration templates

    You can preset a common configuration template for storage pool, LUN, and host mapping configuration. The template contains the required configuration parameters. You can directly use this template when creating similar allocation tasks.

Typical Scenarios

  • Storage pool initialization

    In a new environment, you need to initially allocate storage resources by creating storage pools and LUNs to integrate the storage resources for future use.

  • Host resource allocation

    When you need to allocate storage resources for a group of hosts, you can map a group of LUNs to this host group so that each host in the host group can have a LUN.

Task Management

Describes how to view/delet a Task.

viewing/deleting a task

Describes how to view/delet a Task.

Context

A task list displays the configuration tasks that you have executed. You can view configuration tasks executed at specific points in time to learn about resource usage.

Procedure

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

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

    A list is displayed showing all configuration tasks.

  3. You can classify and sort the tasks by name, configuration type, execution status, and description.
  4. You can query tasks by name, execution status, or configuration type.
  5. You can click a configuration task name to view its details.
  6. You can select a task and click Delete to delete a task.

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-34 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-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

  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-36 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-37 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 1.10.3.1 Creating a Storage Pool Configuration Task, 1.10.3.2 Creating a LUN Configuration Task, 1.10.3.3 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.

Reclaiming Resources

The storage system allows allocated storage LUN resources to be reclaimed. Two reclamation policies are available: For LUNs that have been mapped to hosts, remove the mapping and delete the LUNs. For LUNs that have not been mapped to any host, directly delete the LUNs.

Procedure

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

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

    Example:

    Name: recovery_LUN

    Description: reclaiming of storage resources

  4. Select a reclaiming policy.

    • Unmapping: Unmap LUNs from the host.
      1. If you want to unmap and delete LUNs, select Delete Unmapped LUNs in More Operation.
      2. After all LUNs mapped to the logical host are unmapped, you can select Delete Logical Host in More Operation to delete the logical host.
      3. After all hosts of a host group are deleted, you can select Delete Host Group in More Operation to delete the host group.
    NOTE:

    If all the LUN mappings in a LUN group are removed, the LUN group is renamed. The renaming rule is to suffix the LUN group name with _DEL. For example, if the name of a LNU group is LUNGroup_001, the LUN group is renamed as LUNGroup_001_DEL.

    • Deleting unmapped LUNs: For LUNs that have not been mapped to any host, directly delete the LUNs.

  5. Click Add.

    The Add LUN dialog box is displayed.

  6. Click the name of a storage device.

    LUNs on the selected storage device are displayed in the right area.

  7. Select the LUNs that you want to delete.

    You can search for LUNs that you want to delete by LUN name, Type, Capacity, Owning Storage Pool, Block Device Name, and Owning Device.

  8. Click OK.
  9. Select the LUNs that you want to delete.
  10. Click OK.

    The resource reclaiming task starts.

Customized Configuration Management

Describes how to create a customized configuration.

Creating a Customized Configuration

Describes how to create a customized configuration.

Context

You can configure storage resources using a web page or customized script. The customized configuration script is executed on storage devices to flexibly deploy your configuration. You can use a customized script to configure disk domains, storage pools, LUNs, hosts, host groups, port groups, mappings, file systems, and share permission.

Procedure

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

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

    For example:

    Name: disk_domain

    Description: Create a script for disk domain configuration.

  4. Select the storage device where you want to execute the script.
  5. Set configuration parameters.

    For details about the supported customized scripts and examples, see 1.10.5.2 Customized Script Usage Guide.

    • Configuration: You can create a new configuration task or use an existing one.
    • Script: Enter a configuration script. For example: create disk_domain name=domain1

  6. 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.
  7. Click Next.
  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.

Customized Script Usage Guide

This topic describes the commands that are used to execute the customized scripts for resource configuration.

create disk_domain

Function

create disk_domain is used to create a disk domain.

Format

create disk_domain name=? [ disk_domain_id=? ] disk_list=?

create disk_domain name=? [ disk_domain_id=? ] disk_number=? disk_type=?

Parameters

Parameter

Description

Value

name=?

Name of a disk domain.

The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).

disk_domain_id=?

ID of a disk domain.

  • The value is an integer from 0 to 63.
  • If this parameter is not specified, the system automatically allocates an ID for a new disk domain.

disk_list=?

List of disk IDs. When this parameter is specified, you cannot specified disk_type=? or disk_number=?.

The value can be all, disk ID range, or disk ID list, where:

  • all: All free disks are allocated to a disk domain.
  • disk ID range: The value is in the format of start disk ID-end disk ID, for example, DAE000.1-5.
  • disk ID list: Multiple disk IDs are separated with commas (,), for example, DAE000.1,DAE000.2,DAE000.3.

To obtain the value, you can run show disk general.

disk_number=?

Number of disks in a disk domain. This parameter is used together with disk_type=? to automatically allocate disks of specified types and quantity to a disk domain. If this parameter is specified, you cannot specify parameter disk_list=?.

The value is an integer from 1 to 2147483647.

disk_type=?

Disk type

The value can be SAS, NearLine_SAS or SSD, where:

  • SAS: a SAS disk.
  • NearLine_SAS: an NL-SAS disk.
  • SSD: an SSD.
NOTE:

The following describes the disk type supported by each storage tier:

  • Tier 0 (high performance tier): SSDs
  • Tier 1 (performance tier): SAS disks
  • Tier 2 (capacity tier): NL-SAS disks

Example

Create disk domain test that contains eight NL-SAS disks.

create disk_domain name=test disk_number=8 disk_type=NearLine_SAS

create storage_pool

Function

create storage_pool is used to create a storage pool. Storage systems use storage pools to provide storage space for application servers. A storage pool can use different RAID policy to combine independent disks, providing more storage capacity although improving the read performance and data security of disks.

Format

create storage_pool name=? disk_type=? capacity=? [ raid_level=? | full_threshold=? | disk_domain_id=? | pool_id=? | extent_size=? | stripe_depth=? | usage_type=? ] *

Parameters

Parameter

Description

Value

name=?

Storage pool name

The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).

disk_type=?

Physical type of a member disk.

NOTE:

Only the disk type supported by a storage tier can be specified.

The value can be SAS, NearLine_SAS or SSD, where:

  • SAS: a SAS disk.
  • Nearline_SAS: an NL-SAS disk.
  • SSD: an SSD.
NOTE:

The following describes the disk type supported by each storage tier:

  • Tier 0 (high performance tier): SSDs
  • Tier 1 (performance tier): SAS disks
  • Tier 2 (capacity tier): NL-SAS disks

capacity=?

Capacity of a storage pool.

The value is an integer, expressed in GB or TB.

The value ranges from 1 GB to 12864 TB.

raid_level=?

RAID policy of a storage pool.

NOTE:

Disks added to a disk domain are divided into logical blocks. These blocks are combined by the system based on the specified RAID policy. The logical blocks are categorized as data blocks and parity blocks.

The value can be RAID 6-4, RAID 6-6, RAID 6-10, RAID 5-3, RAID 5-5, RAID 5-9, RAID 50-6, RAID 50-10, RAID 50-18, RAID 3-3, RAID 3-5, RAID 3-9, RAID 0, RAID 10, RAID 1-2, or RAID 1-4, where:

  • RAID 6-4: indicates RAID 6 that contains 4 logical blocks.
  • RAID 6-6: indicates RAID 6 that contains 6 logical blocks.
  • RAID 6-10: indicates RAID 6 that contains 10 logical blocks.
  • RAID 5-3: indicates RAID 5 that contains 3 logical blocks.
  • RAID 5-5: indicates RAID 5 that contains 5 logical blocks.
  • RAID 5-9: indicates RAID 5 that contains 9 logical blocks.
  • RAID 50-6: indicates RAID 50 that contains 6 logical blocks.
  • RAID 50-10: indicates RAID 50 that contains 10 logical blocks.
  • RAID 50-18: indicates RAID 50 that contains 18 logical blocks.
  • RAID 3-3: indicates RAID 3 that contains 3 logical blocks.
  • RAID 3-5: indicates RAID 3 that contains 3 logical blocks.
  • RAID 3-9: indicates RAID 3 that contains 9 logical blocks.
  • RAID 0: indicates RAID 0 that contains logical blocks whose quantity is automatically specified by the system.
  • RAID 10: indicates RAID 10 that contains logical blocks whose quantity is automatically specified by the system.
  • RAID 1-2: indicates RAID 1 that contains 2 logical blocks.
  • RAID 1-4: indicates RAID 1 that contains 4 logical blocks.

full_threshold=?

Capacity alarm threshold.

The value ranges from 50 to 85, expressed in percentage.

The default value is 80.

disk_domain_id=?

ID of a disk domain where a storage pool resides.

To obtain the value, run show disk_domain general.

pool_id=?

Storage pool ID.

The value is an integer from 0 to 127.

If this parameter is not specified, the system automatically allocates an ID for a new storage pool.

extent_size=?

Data migration granularity

The value can be 512 KB, 1 MB, 2 MB, 4 MB, 8 MB, 16 MB, 32 MB, or 64 MB.

The default value is 4 MB.

NOTE:

If you specify raid_level to a non-typical configuration, extent_size will be automatically calculated by the system.

stripe_depth=?

This parameter is only valid in developer mode.

The value can be 32 KB, 64 KB, 128 KB, 256 KB, or 512 KB.

The default value is 64 KB.

usage_type=?

Storage pool usage.

The value can be lun or file_system, where:

  • lun: block storage service
  • file_system: file storage service

The default value is lun.

Example

Create storage pool poolTest, set its disk type to SAS and capacity to 8 GB, and use default settings for the other parameters.

create storage_pool name=poolTest disk_type=SAS capacity=8GB

create lun

Function

create lun is used to create a LUN. You can divide the space of a newly created storage pool into one or multiple LUNs so that storage resources can be appropriately allocated to application servers.

Format

create lun name=? [ number=? | lun_id=? | lun_id_list=? ] pool_id=? capacity=? [ lun_type=? [ initial_capacity=? | thresholds_switch=? | thresholds_percent=? ] | write_policy=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | relocation_policy=? | allocation_policy=? | owner_controller=? | read_cache_policy=? | write_cache_policy=? | io_priority=? | dif_switch=? | compression_enabled=? | compression_method=? | dedup_enabled=? | bytecomparison_enabled=? | grain_size=? | smart_cache_state=? ]

create lun name=? [ number=? | lun_id_list=? ] copy_lun_id=? [ override_capacity=? | override_pool_id=? ] *

create lun name=? remote_lun_wwn_list=? storage_pool_id=? [ write_policy=? ] [ prefetch_policy=? ] [ prefetch_multiple=? ] [ prefetch_value=? ] [ relocation_policy=? ] [ allocation_policy=? ] [ io_priority=? ] [ read_cache_policy=? ] [ write_cache_policy=? ] [ owner_controller=? ] [ lun_id=? ] [ dif_switch=? ]

Parameters

Parameter

Description

Value

name=?

Name of a LUN.

  • The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).
  • When you batch create LUNs (by specifying number=?), the system automatically numbers the LUN names by adding a four-digit suffix to each name. The suffix starts from 0000. For example, if you specify the LUN name to LUN, the newly created LUNs are automatically names as LUN0000, LUN0001, and so on.
NOTE:

When batch creating LUNs, name=? cannot exceed 27 characters.

number=?

Number of batch created LUNs.

If this parameter is specified, you cannot specify parameter lun_id=? or lun_id_list=?.

The value ranges from 2 to 100.

The default value is 1.

lun_id=?

LUN ID.

This parameter is invalid when number=? or lun_id_list=? is specified.

The value is an integer from 0 to 8191.

If this parameter is not specified, the system automatically allocates an ID for a new LUN.

pool_id=?

ID of the storage pool where a LUN resides.

To obtain the value, run show storage_pool general.

capacity=?

Capacity of a LUN

  • The value is in the format of capacity value + unit, expressed in KB, MB, GB, TB, or block.
  • The value ranges from 512 KB to 256 TB.
  • One block is equal to 512 bytes.
  • The value can be a decimal when the unit is GB or TB.
  • If variable remain is added to this parameter, the remaining space of a storage pool will be used to create LUNs.

lun_type=?

Type of a LUN.

The value can be thick or thin, where:

  • thick: A thick LUN is always assigned a fixed amount of capacity.
  • thin: When being created, a thin LUN is assigned an initial capacity (specified by the initial_capacity parameter). When the available capacity of the thin LUN is insufficient, the capacity is automatically expanded but cannot exceed the maximum value (specified by the capacity parameter).

The default value is thick.

initial_capacity=?

Initial capacity of a thin LUN.

This parameter is valid and mandatory when lun_type=? is specified to thin.

  • The value is in the format of capacity value + unit, expressed in KB, MB, GB, TB, or block.
  • The value ranges from 512 KB to the capacity of created LUNs (specified by parameter capacity=?).

write_policy=?

Cache write policy.

The value can be write_through or write_back, where:

  • write_through: The system considers that a data write is successful only after data is written to disks. Disks are accessed in each data write.
  • write_back: After data is written to the cache of the local controller, the system considers that a data write is successful. In addition, the data will be written to the cache of the peer controller as a mirror. When certain conditions are met, the caches write data to disks.

The default value is write_back.

prefetch_policy=?

Cache prefetch policy.

The value can be none, constant, variable, or intelligent, where:

  • none: non-prefetch.
  • constant: constant prefetch.
  • variable: variable prefetch.
  • intelligent: intelligent prefetch.

The default value is intelligent.

prefetch_multiple=?

Multiple of cache prefetch. This parameter is mandatory when parameter prefetch_policy=? is specified to variable.

The value ranges from 0 to 1024.

prefetch_value=?

Cache prefetch value. This parameter is mandatory when parameter prefetch_policy=? is specified to constant.

The value ranges from 0 to 1024, expressed in KB.

relocation_policy=?

SmartTier policy.

The value can be none, automatic, lowest_available, or highest_available, where:

  • none: Migration is not performed.
  • automatic: The system automatically determines the migration direction.
  • lowest_available: Data is migration to a lower performance tier, for example, from the high performance tier to the performance tier.
  • highest_available: Data is migration to a higher performance tier, for example, from the performance tier to the high performance tier.

The default value is automatic.

allocation_policy=?

Initial capacity allocation policy.

The value can be automatic, extreme_performance, performance, or capacity, where:

  • automatic: The system automatically allocates the available capacity of storage tiers to a LUN.
  • extreme_performance: The capacity of the high performance tier is preferentially allocated.
  • performance: The capacity of the performance tier is preferentially allocated.
  • capacity: The capacity of the capacity tier is preferentially allocated.

The default value is automatic.

read_cache_policy=?

Cache read policy of a LUN.

The value can be Low, Middle, or High, where:

  • Low: low priority.
  • Middle: medium priority.
  • High: high priority.

The default value is Middle.

write_cache_policy=?

Cache write policy of a LUN.

The value can be Low, Middle, or High, where:

  • Low: low priority.
  • Middle: medium priority.
  • High: high priority.

The default value is Middle.

io_priority=?

I/O priority of a LUN.

The value can be Low, Middle, or High, where:

  • Low: low priority.
  • Middle: medium priority.
  • High: high priority.

The default value is Low.

copy_lun_id=?

ID of the source LUN whose properties you want to copy If this parameter is specified, the new LUN has the same properties as the source LUN. The properties include owning resource pool ID, type, capacity, initial allocation capacity, write policy, mirror policy, prefetch policy, and prefetch policy value.

To obtain the value, run show lun general.

override_capacity=?

-

  • The value is in the format of capacity value + unit, expressed in KB, MB, GB, or TB.
  • The value ranges from 512 KB to 256 TB.

If this parameter is not specified, the capacity of the new LUN is the same as the source LUN.

override_pool_id=?

ID of the storage pool that owns the new LUN created by copying the source LUN properties

To obtain the value, run show storage_pool general.

If this parameter is not specified, the new LUN belongs to the same storage pool as the source LUN.

owner_controller=?

Owning controller of a LUN.

The value format is XA, XB, XC, or XD, the value of X are related to the NE type.

dif_switch=?

Whether to enable the DIF function.

Possible values are:

  • yes: enables the DIF function.
  • no: disables the DIF function.

remote_lun_wwn_list=?

WWN of a remote LUN.

To obtain the value, run show remote_lun general.

storage_pool_id=?

ID of the storage pool where a LUN resides.

To obtain the value, run show storage_pool general.

compression_enabled=?

Whether to enable data compression.

The value can be yes or no, where:

  • yes: enables the compression function.
  • no: disables the compression function.

The default value is no.

compression_method=?

LUN data compression algorithm

The value can be fast or deep, where:

  • fast: speed preferred.
  • deep: compression ratio preferred.

The default value is fast.

dedup_enabled=?

Whether to enable data deduplication.

The value can be yes or no, where:

  • yes: enables the deduplication function.
  • no: disables the deduplication function.

The default value is no.

bytecomparison_enabled=?

Whether to enable the byte-by-byte comparison.

The value can be yes or no, where:

  • yes: enables the byte-by-byte comparison.
  • no: disables the byte-by-byte comparison.

The default value is no.

grain_size=?

Thin LUN granularity

The value can be 4 KB, 8 KB, 16 KB, 32 KB, or 64 KB, where:

  • 4 KB: 4 KB granularity.
  • 8 KB: 8 KB granularity.
  • 16 KB: 16 KB granularity.
  • 32KB: 32 KB granularity.
  • 64 KB: 64 KB granularity.

The default value is 64 KB.

thresholds_switch=?

Alarm threshold switch for a thin LUN.

The value can be on or off, where:

  • off: disables the threshold alarm switch.
  • on: enables the threshold alarm switch.

The default value is off.

thresholds_percent=?

Alarm threshold for a thin LUN.

The value ranges from 50 to 99, expressed as a percentage. The default value is 90.

smart_cache_state=?

Whether to enable the SmartCache function.

The value can be on or off, where:

  • off: disables SmartCache.
  • on: enables SmartCache.

The default value is off.

lun_id_list=?

LUN ID list. This parameter is invalid when number=? or lun_id=? is specified.

The value is an integer from 0 to 65535. Use comma (,) or hyphen (-) to separate LUN IDs, for example, 0,5-8.

Usage Guide

  • You can use either of the following methods to create LUNs:
    • Manually specify LUN parameters: create lun name=? [ number=? | lun_id=? lun_id_list=? ] pool_id=? capacity=? [ lun_type=? [ initial_capacity=? | thresholds_switch=? | thresholds_percent=? ] | write_policy=? | prefetch_policy=? [ prefetch_multiple=? ] [ prefetch_value=? ] | relocation_policy=? | allocation_policy=? | owner_controller=? | read_cache_policy=? | write_cache_policy=? | io_priority=? | dif_switch=? ] *
    • Copy the properties of a LUN to create a new LUN:create lun name=? [ number=? | lun_id_list=? ] copy_lun_id=? [ override_capacity=? | override_pool_id=? ] *
  • The capacity of a new LUN cannot be larger than the free capacity of the storage pool.
  • The scheduled migration policy automatically migrates data between tier 0, tier 1, and tier 2 at the specified time. For example, the policy migrates seldom accessed data to the low-performance and large-capacity storage tier 2 and migrates the frequently accessed data to the highest performance storage tier 0. This way of data migration strikes a balance between performance, capacity, and cost by taking full advantage of different types of physical disks.
  • When you batch create LUNs and set parameter capacity to remain, the capacity of the last created LUN may be different from that of the other LUNs or some LUNs cannot be created due to insufficient space because of the extent size alignment in LUN capacity allocation.
  • If you do not specify parameter compression_enabled=yes or dedup_enabled=yes when creating LUNs, parameter grain_size cannot be specified.

Example

  • Create a LUN and specify its parameters as follows:
    • Name: newlun
    • Owning storage pool ID: 1
    • LUN capacity: 100 MB

      create lun name=newlun pool_id=1 capacity=100MB

  • Create two LUNs and specify their parameters as follows:
    • Prefix of LUN names: newlun-clone
    • ID of the source LUN whose properties are copied: 2
    • LUN capacity: 200 MB

      create lun name=newlun-clone copy_lun_id=2 override_capacity=200MB number=2

  • Create a thin LUN with compression enabled and specify its parameters as follows:
    • Name: asdf
    • Owning storage pool ID: 0
    • LUN capacity: 2 GB
    • LUN type: thin
    • Initial capacity of the thin LUN: 1 GB
    • Compression switch status: yes

      create lun name=asdf pool_id=0 capacity=2GB lun_type=thin initial_capacity=1GB compression_enabled=yes

create lun_group

Function

create lun_group is used to create a LUN group.

Format

create lun_group name=? [ lun_group_id=? ] [ lun_id_list=? ]

Parameters

Parameter

Description

Value

name=?

LUN group name.

The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).

lun_group_id=?

LUN group ID.

The value is an integer from 0 to 8191.

If you do not specify this parameter, the system automatically allocates an ID for a new LUN group.

lun_id_list=?

LUN ID list. If this parameter is specified, LUNs with the specified IDs will be added to a LUN group.

To obtain the value, run show lun general. When multiple LUNs need to be added to a LUN group, separate these LUN IDs with commas (,).

Example

Create LUN group LUNGroupTest and add LUNs 0, 1, and 2 to this group.

create lun_group name=LUNGroupTest lun_id_list=0,1,2

create port_group

Function

create port_group is used to create a port group.

Format

create port_group name=? [ port_group_id=? ] [ port_type=? port_id_list=? ]

Parameters

Parameter

Description

Value

name=?

Name of the port group.

The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).

lun_group_id=?

ID of a port group.

The value is an integer from 0 to 8191.

If this parameter is not specified, the system automatically allocates an ID for a new port group.

port_type=?

Type of a port that you want to add to a port group. If this parameter is specified, you must specify parameter port_id_list=?.

The value can be FC, ETH, or FCoE, where:

  • FC: Fibre Channel ports.
  • ETH: ETH ports.
  • FCoE: FCoE ports.

port_id_list=?

ID of a port that you want to add to a port group. This parameter is valid only when parameter port_type=? is specified.

  • To obtain the value, run show port general.
  • When multiple ports need to be added, separate these port IDs with commas (,).

Example

Create port group test_portgroup.

create port_group name=test_portgroup

create host

Function

create host is used to create a host.

Format

create host name=? operating_system=? [ ip=? | network_name=? | location=? | model=? | host_id=? ] *

Parameters

Parameter

Description

Value

name=?

Name of a host.

The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).

operating_system=?

Operating system of a host.

Possible values are:

  • Linux
  • Windows
  • Solaris
  • HP-UX
  • AIX
  • XenServer
  • Mac_OS
  • VIS6000
  • VMware_ESX
  • Windows_Server_2012
NOTE:

Windows Server 2012 can be used only when the host needs to reclaim space when accessing thin LUNs.

ip=?

Host IP address.

-

network_name=?

Name of the network to which a host belongs.

The value is a character string from 1 to 255.

location=?

Location of a host.

The value is a character string from 1 to 127.

model=?

Host model.

The value is a character string from 1 to 127.

host_id=?

Host ID.

The value is an integer from 0 to 8191. If this parameter is not specified, the system automatically assigns a value.

Example

  • Create host whose name and operating system are newhost000 and Windows:

    create host name=newhost000 operating_system=Windows

  • Create host whose name, operating system, location, model, network, IP address, and host ID are newhost001, Linux, newlocation, 2058, newnetwork, 192.168.3.53, and 1.

    create host name=newhost001 operating_system=Linux location=newlocation model=2058 network_name=newnetwork ip=192.168.3.53 host_id=1

create host_group

Function

create host_group is used to create a host group.

Format

create host_group name=? [ host_group_id=? | host_id_list=? ] *

Parameters

Parameter

Description

Value

name=?

Name of a host group.

The value contains 1 to 31 digits, letters, underscores (_), hyphens (-), and periods (.).

host_group_id=?

ID of a host group.

The value is an integer from 0 to 8191. If this parameter is not specified, the system automatically allocates an ID for a new host group.

host_id_list=?

Host ID. When this parameter is specified, the hosts with the specified IDs are added to a host group.

  • To obtain the value, run show host general.
  • When multiple hosts need to be added, separate these host IDs with commas (,).

Example

Create a host group whose name is test.

create host_group name=test

create mapping_view

Function

create mapping_view is used to create a mapping view.

Format

create mapping_view name=? [ mapping_view_id=? ] [ lun_group_id=? ] [ host_group_id=? ] [ port_group_id=? ]

Parameters

Parameter

Description

Value

name=?

Mapping view name.

The value contains 1 to 31 ASCII characters, including digits, letters, underscores (_), hyphens (-), and colons (:).

mapping_view_id=?

Mapping view ID.

The value is an integer from 0 to 8191. If this parameter is not specified, the system automatically assigns a value.

lun_group_id=?

LUN group ID. If this parameter is specified, the storage system adds the LUN group with the specified ID to a mapping view.

To obtain the value, run show lun_group general.

host_group_id=?

Host group ID. If this parameter is specified, the storage system adds the host group with the specified ID to a mapping view.

To obtain the value, run show host_group general.

port_group_id=?

Port group ID. If this parameter is specified, the storage system adds the port group with the specified ID to a mapping view. This parameter is valid only when parameter host_group_id=? is specified.

To obtain the value, run show port_group general.

Example

Create a mapping view whose name and ID are mapping_Test and 1 and add LUN group 1, host group 0, and port group 0 to the mapping view.

create mapping_view name=mapping_Test mapping_view_id=1 lun_group_id=1 host_group_id=0 port_group_id=0

create file_system general

Function

create file_system general is used to create a file system. You can divide the space of a newly created storage pool into one or multiple file systems so that storage resources can be appropriately allocated to application servers.

Format

create file_system general name=? pool_id=? [ initial_distribute_policy=? ] [ capacity=? ] [ file_system_id=? ] [ alloc_type=? ] [ number=? ] [ owner_controller=? ] [ io_priority=? ] [ checksum_enabled=? ] [ atime_enabled=? ] [ show_enabled=? ] [ auto_delete_snapshot_enabled=? ] [ timing_snapshot_enabled=? ] [ block_size=? ] [ capacity_threshold=? ] [ snapshot_reserve=? ] [ timing_snapshot_max_number=? ]

Parameters

Parameter

Description

Value

name=?

File system name.

  • The value contains 1 to 255 ASCII characters, including digits, letters, underscores (_), hyphens (-), and periods (.).
  • When you batch create file systems (by specifying number=?), the system automatically numbers the file system names by adding a four-digit suffix to each name. The suffix starts from 0000. For example, if you specify the file system name to LUN, the newly created file systems are automatically named as FS0000, FS0001, and so on.
NOTE:

When you batch create file systems, the value of name=? cannot exceed 251 characters.

pool_id=?

ID of the storage pool that owns a file system.

To obtain the value, run show storage_pool general.

capacity=?

File system capacity.

  • The value is in the format of capacity value + unit, expressed in KB, MB, GB, TB, or block.
  • The value ranges from 1 GB to 16384 TB.
  • If the value is set to all, the file system does not have a capacity limit and all storage pool capacity can be allocated to the file system.
  • The value can be set to all only for thin file systems.
  • One block is equal to 512 bytes.

file_system_id=?

File system ID.

The value is an integer from 0 to 8191. If this parameter is not specified, the system automatically allocates an ID for a new file system.

alloc_type=?

File system type.

The value can be thick or thin, where:

  • thick: A thick file system is always assigned a fixed amount of capacity.
  • thin: A thin file system is assigned an initial capacity and this capacity is automatically expanded when more capacity is required. The maximum capacity of a thin file system is specified by parameter capacity.

The default value is thick.

number=?

Number of batch created file systems. This parameter cannot be used together with file_system_id=?.

The value ranges from 2 to 100. The default value is 1.

owner_controller=?

Owning controller of a file system.

The value format is XA or XB, where X ranges from 0 to 3.

io_priority=?

I/O priority of a file system.

The value can be Low, Middle, or High, where:

  • Low: low priority.
  • Middle: medium priority.
  • High: high priority.

The default value is Low.

checksum_enabled=?

Whether to enable the checksum function.

The value can be yes or no, where:

  • yes: enables the checksum function.
  • no: disables the checksum function.

atime_enabled=?

Whether to enable the atime function.

The value can be yes or no, where:

  • yes: enables the atime function.
  • no: disables the atime function.

show_enabled=?

Whether to set a snapshot directory visible.

The value can be yes or no, where:

  • yes: sets the snapshot directory to visible.
  • no: sets the snapshot directory to invisible.

auto_delete_snapshot_enabled=?

Whether to enable the automatic deletion of periodic snapshots.

The value can be yes or no, where:

  • yes: enables the automatic deletion of periodic snapshots.
  • no: disables the automatic deletion of periodic snapshots.

timing_snapshot_enabled=?

Whether to enable periodic snapshots.

The value can be yes or no, where:

  • yes: enables periodic snapshots.
  • no: disables periodic snapshots.

block_size=?

File system block size.

The value can be 4 KB, 8 KB, 16 KB, 32 KB, or 64 KB. The default value is 64 KB.

capacity_threshold=?

File system capacity alarm threshold. Alarms are reported when the file system capacity usage exceeds the threshold.

  • The value is a percentage (an integer).
  • The value ranges from 50 to 90.

snapshot_reserve=?

Capacity percentage reserved for snapshots.

  • The value is a percentage (an integer).
  • The value ranges from 0 to 50.

timing_snapshot_max_number=?

Maximum number of periodic snapshots.

The value ranges from 1 to 2048. The default value is 16.

initial_distribute_policy=?

Initial allocation policy of a file system.

The value can be automatic, extreme_performance, performance, or capacity, where:

  • automatic: The system automatically allocates the available capacity of storage tiers to a LUN.
  • extreme_performance: The capacity of the high performance tier is preferentially allocated.
  • performance: The capacity of the performance tier is preferentially allocated.
  • capacity: The capacity of the capacity tier is preferentially allocated.

The default value is automatic.

Example

Create a file system whose name is fs001 and specify the storage id, capacity, and allocation type to 0, 10 GB, and thick.

create file_system general name=fs001 pool_id=0 initial_distribute_policy=automatic capacity=10GB alloc_type=thick\

create share cifs

Function

create share cifs is used to create a common Internet file system (CIFS) share.

Format

create share cifs name=? local_path=? [ oplock_enabled=? ] [ notify_enabled=? ] [ file_system_id=? ]

Parameters

Parameter

Description

Value

name=?

CIFS share name.

The vale contains 1 to 80 characters excluding \"/\\[]:|<>+;,?*=.

local_path=?

Local path.

The value contains 1 to 1023 characters.

oplock_enabled=?

oplock switch. If the switch is enabled, clients can lock a file and servers can unlock the file.

The value can be yes or no. The default value is yes.

  • yes: enables the oplock function.
  • no: disables the oplock function.

notify_enabled=?

Notification switch.

The value can be yes or no. The default value is yes.

  • yes: enables the notify function.
  • no: disables the notify function.

file_system_id=?

ID of the file system to which a CIFS share belongs.

The value is an integer from 0 to 8189. To obtain the value, run show file_sytem general.

Usage Guide

You must specify name, file_system_id, and local_path at the same time.

Example

Creates a CIFS share.

create share cifs name=cifs0 file_system_id=0 local_path=/fs001

create share_permission cifs

Function

create share_permission cifs is used to create a common Internet file system (CIFS) share permission.

Format

create share_permission cifs access_name=? share_id=? permission_type=?

Parameters

Parameter

Description

Value

access_name=?

Access name. The name can be a resource user or user group.

  • The value is a string containing 1 to 288 characters.
  • If the name is a resource user group, add an at sign (@) at the beginning of the user group name to distinguish it from resource users.

share_id=?

Share ID.

-

permission_type=?

Permission type.

The value can be read_only, read_write, no_access, or all_control, where:

  • read_only: read only.
  • read_write: writable and writable.
  • no_access: no permission.
  • all_control: full control.

Usage Guide

You must specify access_name, share_id, and permission_type at the same time.

Example

  • Create a CIFS share permission and specify access_name to a resource user.

    create share_permission cifs access_name=user1 share_id=4 permission_type=all_control

  • Create a CIFS share permission and specify access_name to a resource user group.

    create share_permission cifs access_name=@group1 share_id=4 permission_type=all_control

create share nfs

Function

create share nfs is used to create a network file system (NFS) share.

Format

create share nfs local_path=? [ file_system_id=? ]

Parameters

Parameter

Description

Value

file_system_id=?

File system ID.

The value ranges from 0 to 8191.

local_path=?

Absolute path of an NFS share.

The value contains 1 to 1023 characters.

Example

Creates an NFS share.

create share nfs file_system_id=0 local_path=/fs110

create share_permission nfs

Function

create share_permission nfs is used to create a network file system (NFS) share permission.

Format

create share_permission nfs access_name=? share_id=? access_type=? sync_enabled=? all_squash_enabled=? root_squash_enabled=?

Parameters

Parameter

Description

Value

access_name=?

File system ID.

The value contains 1 to 127 characters.

share_id=?

Absolute path of an NFS share.

The value is a positive integer.

access_type=?

Access permission for an NFS share.

The value can be read_only or read_write, where:

  • read_only: read only.
  • read_write: read and write.

sync_enabled=?

Synchronous write permission for an NFS share.

The value can be yes or no, where:

  • yes: synchronous write.
  • no: asynchronous write.

all_squash_enabled=?

Compression permission for all NFS share users.

The value can be yes or no, where:

  • yes: grants the permission.
  • no: does not grant the permission.

root_squash_enabled=?

Compression permission for NFS share users.

The value can be yes or no, where:

  • yes: grants the permission.
  • no: does not grant the permission.

Example

None

Common Configuration Management

Describes how to create a common configuration template.

Creating a Common Configuration Template

Describes how to create a common configuration template.

Context

You can preset a common configuration template for storage pool, LUN, and host mapping configuration. The template contains the required configuration parameters. You can directly use this template when creating similar configuration tasks.

Procedure

  • Creating a template for common storage pool configuration
    1. Go to the common configuration page.
      1. On the menu bar, choose Resource > Storage Subnet.

      2. In the navigation tree, choose Storage Resources Allocation > Manage Common Configuration.
    2. Click Create.

      The common configuration page is displayed.

    3. Set common configuration parameters.
      Table 10-38 Common configuration parameters

      Parameter

      Description

      Example

      Basic Configuration

      Name

      Name of a common configuration.

      PoolCfgName

      Type

      Type of a common configuration.

      Storage pool configuration

      Description

      Description of a common configuration.

      S5800 storage pool common 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

    1. Click Save.

      A message box is displayed.

    2. Click OK.
  • Creating a template for common LUN configuration
    1. Go to the common configuration page.
      1. On the menu bar, choose Resource > Storage Subnet.

      2. In the navigation tree, choose Storage Resources Allocation > Manage Common Configuration.
    2. Click Create.

      The common configuration page is displayed.

    3. Set common configuration parameters.
      Table 10-39 Common configuration parameters

      Parameter

      Description

      Example

      Basic Configuration

      Name

      Name of a common configuration.

      LUNCfgName

      Type

      Type of a common configuration.

      LUN configuration

      Description

      Description of a common configuration.

      S5800 LUN common 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

    1. Click Save.

      A message box is displayed.

    2. Click OK.
  • Creating a template for common host mapping configuration
    1. Go to the common configuration page.
      1. On the menu bar, choose Resource > Storage Subnet.

      2. In the navigation tree, choose Storage Resources Allocation > Manage Common Configuration.
    2. Click Create.

      The common configuration page is displayed.

    3. Set common configuration parameters.
      Table 10-40 Common configuration parameters

      Parameter

      Description

      Example

      Name

      Name of a common configuration.

      HostCfgName

      Type

      Type of a common configuration.

      Mapping configuration

      Description

      Description of a common configuration.

      Common configuration of host mapping Host01

      Mapping Mode

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

      Share

      Number of LUNs

      Number of LUNs that you want to map.

      The entered number must be smaller than that of LUNs you have queried.

      5

      Capacity

      Capacity of LUNs that you want to query

      64 GB

      LUN type

      Type of LUNs that you want to query

      Thick LUN

      Performance

      Performance of LUNs that you want to query

      • Automatic: Automatically selects LUNs.
      • 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

      Protocol type

      All the hosts of the selected protocol type will be queried.

      iSCSI

    1. Click Save.

      A message box is displayed.

    2. Click OK.
  • Creating a customized configuration script
    1. Go to the common configuration page.
      1. On the menu bar, choose Resource > Storage Subnet.

      2. In the navigation tree, choose Storage Resources Allocation > Manage Common Configuration.
    2. Click Create.

      The common configuration page is displayed.

    3. Set common configuration parameters.
    4. For details about the supported customized scripts and examples, see Customized Script Usage Guide.
      Table 10-41 Common configuration parameters

      Parameter

      Description

      Example

      Name

      Name of a common configuration.

      disk_domain

      Type

      Type of a common configuration.

      Customized script configuration

      Description

      Description of a common configuration.

      Create a disk domain configuration.

      Script

      Configuration script.

      create disk_domain name=domain1

    1. Click Save.

      A message box is displayed.

    2. Click OK.

----End

Viewing or Modifying or Deleting a Common Configuration Template

Describes how to view/modify/delete a common configuration template.

Context

You can view, modify, or delete a common configuration template based on the storage resource usage.

Procedure

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

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

    A list is displayed showing all common configuration template.

  3. You can query common configuration templates by name or type.
  4. You can click a configuration template name to view its details.

    For details about configuration parameters, see Creating a Common Configuration Template.

  5. You can click to modify the parameters of a common configuration template.

    For details about configuration parameters, see Creating a Common Configuration Template.

  6. You can click to delete a common configuration template or click Delete after selecting a configuration template.

Typical Scenarios

Describes typical scenarios.

Initially Configuring Storage Resources

Describes how to initially configure storage resources.

Context

In a new environment, you need to initially allocate storage device resources. You can batch create storage pools and LUNs to integrate the storage resources for future use.

Figure 10-28 shows the process for initial storage resource configuration.

Figure 10-28 Process for initial storage resource configuration

Procedure

  1. Before initially configuring storage resources, you need to plan the resources, including plan the capacity, number, and names of storage pools, storage tier capacity, and the capacity, number, and names of LUNs.

    This topic uses a fully-configured S6800T as an example. This storage system has 15 disk enclosures each containing 24 SAS disks. The total available capacity of the storage system is 40 TB.

    Disk domains must be created before you configure storage resources. The following describes two situations for creating disk domains:

    • Situation 1: Only one disk domain is required or no disk domain is required. In this situation, you do not need to create disk domains. Use the batch configuration function to configure resources.
    • Situation 2: Multiple disk domains (for example, four) are required. In this situation, create four disk domains on the storage devices and then use the batch configuration function to configure resources.

    Perform the following steps to complete batch configuration:

    • Create a storage pool configuration task.

      This task batch creates four storage pools Storage_001, Storage_002, Storage_003, and Storage_004. The capacity of each storage pool is 10 TB and the RAID policy is RAID 5 (4D+1P).

    • Create a LUN configuration task.

      This task batch creates a total of 400 LUNs, 100 LUNs for each storage pool. The capacity of each LUN is 100 GB. The LUNs are name from LUN_0001 to LUN_0400.

    Table 10-42 and Table 10-43 list the resource planning.

    The LUN names in each storage pool may vary in actual configuration.

    Table 10-42 Resource planning (situation 1)

    Disk Domain

    Storage Pool (10 TB), RAID 5 (4D+1P)

    LUN (100 GB)

    DiskDomain

    Storage_001

    LUN_0001 to LUN_0100

    Storage_002

    LUN_0101 to LUN_0200

    Storage_003

    LUN_0201 to LUN_0300

    Storage_004

    LUN_0301 to LUN_0400

    Table 10-43 Resource planning (situation 2)

    Disk Domain

    Storage Pool (10 TB), RAID 5 (4D+1P)

    LUN (100 GB)

    DiskDomain1

    Storage_001

    LUN_0001 to LUN_0100

    DiskDomain2

    Storage_002

    LUN_0101 to LUN_0200

    DiskDomain3

    Storage_003

    LUN_0201 to LUN_0300

    DiskDomain4

    Storage_004

    LUN_0301 to LUN_0400

  2. Create resource configuration tasks based on the planned data to batch create storage pools and LUNs.

    1. Go to the batch configuration page and set task names and description.
    2. Select Storage pool configurationas the configuration policy.
    3. Select devices where you want to execute the configuration tasks.
    4. Set configuration parameters.

    5. View the summary information and run task execution commands.
    NOTE:

    Click Execute. Note that a task being executed cannot be undone. If a storage pool failed to be created on a storage device, LUNs will not be created on the storage device, but LUN creation on the other devices till not be affected.

  3. After configuration tasks are executed, you can view the newly created storage pools and LUNs on the details page.

    Method:

    1. On the navigation bar, choose Resource > Storage Subnet.
    2. In the left navigation tree, select a storage type.
    3. Right-click a storage device in the device list.
    4. Choose Free Space > Storage Pools or Free Space > Unmapped LUNs.

Allocating Host Resources

Describes how to allocate host resources.

Context

When you need to allocate storage resources for a group of hosts, you can map a group of LUNs to this host group so that each host in the host group can have a LUN.

Figure 10-29 shows the process for allocating host resources.

Figure 10-29 Process for initial storage resource configuration

Procedure

  1. Before allocating host resources, plan the resources based on the host scale and resource usage and map LUNs to hosts.
  2. Check whether the storage resources meet the requirements of host resource allocation.

    Method:

    1. On the navigation bar, choose Resource > Storage Subnet.
    2. In the left navigation tree, select a storage type.
    3. Right-click a storage device in the device list.
    4. Choose Free Space > Storage Pools or Free Space > Unmapped LUNs.

  3. Batch create storage pools and LUNs based on the resource planning. For details, see 1.10.7.1 Initially Configuring Storage Resources.
  4. Create a host mapping configuration task.

    For example, if you want to map 10 LUNs in resource pool Storage_001 to host123, perform the following steps:

    1. Create a configuration task and enter a name and description.
    2. Select Mapping configuration as the configuration policy.
    3. Select a storage device.
    4. Set configuration parameters.
    5. View the information summary and run the task execution command.

  5. After the configuration task is executed, you can view the mappings between LUNs and hosts.

    Method:

    1. On the navigation bar, choose Resource > Storage Subnet.
    2. In the left navigation tree, select a storage type.
    3. Right-click the storage device in the device list.
    4. Choose Resource > Mapping.

Batch Creating LUNs

Describes how to batch create LUNs.

Context

If you want to create LUNs in the existing storage resource pools, you can create a batch task to create LUNs on the specified storage pools.

Procedure

  1. You can view the available storage resource pools on the device details page.

    Method:

    1. On the navigation bar, choose Resource > Storage Subnet.
    2. In the left navigation tree, select a storage type.
    3. Right-click the storage device in the device list.
    4. Choose Free Space > Storage Pools.

  2. Create a configuration task and enter a name and description.
  3. Select LUN configuration as the configuration policy.
  4. Select a storage device.
  5. Set LUN configuration parameters.
  6. View the information summary and run the task execution command.
  7. After configuration tasks are executed, you can view the newly created LUNs on the details page.

    Method:

    1. On the navigation bar, choose Resource > Storage Subnet.
    2. In the left navigation tree, select a storage type.
    3. Click the device name in the storage device list.
    4. Choose Free Space > Unmapped LUNs.

Translation
Download
Updated: 2019-09-07

Document ID: EDOC1100011877

Views: 331181

Downloads: 660

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