OceanStor Dorado 6.1 Basic Storage Service Configuration Guide For Block
OceanStor Dorado 6.1 Basic Storage Service Configuration Guide For Block
6.1
Issue 02
Date 2022-01-25
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees
or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website: https://e.huawei.com
Purpose
This document describes the basic storage services and explains how to configure
and manage them.
The following table lists the product models that this document is applicable to.
NOTICE
This document is updated periodically with the software version. The operations
described in this document use the latest version as an example. Note that the
supported functions and features vary according to the software version. The
content in this document is for reference only.
Intended Audience
This document is intended for:
● Technical support engineers
● Maintenance engineers
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Change History
Changes between document issues are cumulative. The latest document issue
contains all the changes made in earlier issues.
Issue 02 (2022-01-25)
This issue is the second official release.
Added the configuration of LLDP.
Issue 01 (2021-09-30)
This issue is the first official release.
Contents
6 FAQs....................................................................................................................................... 224
6.1 How Can I Enable Mapping Cancellation Fool-Proofing?.................................................................................... 224
6.2 How Can I Query the iSCSI Target Name of an Ethernet Port on a Storage System?...............................225
D Glossary.................................................................................................................................240
E Acronyms and Abbreviations............................................................................................255
1 Introduction
This chapter describes the organization of this guide, lists related documentation,
and provides tips for use.
Related Documentation
Refer to the following documents when performing certain basic configurations
and subsequent operations:
● Product description
Refer to the product description specific to your product if you want to
understand the market positioning, basic functions, and specifications of the
product.
● Installation guide
Refer to the guide specific to your product when initializing a storage system.
● Administrator guide
Refer to the guide specific to your product when planning user roles and
permissions.
● Host connectivity guide
Refer to the guide specific to your product for details on how to configure
host connectivity.
● Command reference
Refer to the guide specific to your product if you want to configure storage
services using the command-line interface (CLI).
Tips
GUIs may vary with product versions and models. The actual GUIs prevail.
This chapter describes basic concepts, basic storage principles, and application
scenarios of storage systems.
2.1 Basic Storage Principles
2.2 Symmetric Active-Active Architecture
2.3 Application Scenarios
● RAID columns
Stripe length of each CKG: N+M.
● Dynamic RAID
A new RAID algorithm that dynamically adjusts the number of CKs in CKGs to
ensure system reliability and storage capacity. If a CK is faulty and no CK is
available from disks, the system dynamically reconstructs the original N+M
CKs to (N-1)+M CKs. When an extra SSD is inserted, the system then migrates
data from (N-1)+M CKs to the newly constructed N+M CKs for efficient disk
usage.
● Grain
CKGs are divided into small, fixed-size blocks called grains (the default size of
a grain is 8 KB). Grains are the basic units that constitute a thin LUN.
● Disk domain
A disk domain consists of multiple disks. When a storage pool is created on
DeviceManager, a disk domain is automatically created within the storage
system but is not displayed on DeviceManager. By default, the capacity of a
storage pool is equal to the available capacity of the corresponding disk
domain.
NOTE
You can create disk domains and storage pools on the CLI. For details, see the
command reference specific to your product model and version.
● Storage pool
A storage resource container. The storage resources used by application
servers are all from storage pools.
● Hot spare space
Space used for data reconstruction of faulty blocks in block virtualization.
When a CK is faulty, the system lets a CK of the hot spare space take over and
instructs other CKs in the CKG to perform data reconstruction using the hot
spare space. This ensures data integrity and read/write performance.
● Hot spare policy
A policy that specifies the hot spare capacity of a storage pool. RAID 2.0+
allows all member disks in a storage pool to provide hot spare capacity. For
ease of understanding, the hot spare capacity is expressed in the number of
hot spare disks on DeviceManager.
● Redundancy policy
A policy that specifies whether disk or enclosure redundancy is used. The
redundancy policy of a storage pool cannot be changed once being specified
during storage pool creation.
– Disk redundancy: Chunks in a chunk group come from different SSDs.
This policy enables the system to tolerate a specific number of faulty
disks allowed by the RAID redundancy capacity.
– Enclosure redundancy: Chunks in a chunk group come from different
SSDs and are distributed in different enclosures if possible. In addition,
the number of chunks in each enclosure does not exceed the RAID
redundancy. With this redundancy policy used, the system can tolerate a
single disk enclosure failure without service interruption or data loss.
● LUN
Storage space in a storage pool is divided into logical units called LUNs. A
host can use storage space provided by LUNs after LUNs are mapped to it.
● LUN group
A collection of multiple LUNs. If the data of an application is stored on
multiple LUNs, you can create a LUN group for these LUNs. Operations on a
LUN group apply to all its member LUNs. A LUN group can contain one or
more LUNs.
● Host
A physical or virtual machine that can access a storage system.
● Host group
A collection of multiple hosts. If an application is deployed on a cluster
consisting of multiple hosts, these hosts will access the data volumes of the
application at the same time. In this case, you can create a host group for
these hosts.
● Port
Endpoint of a connection. For physical connections, ports are physical
interfaces, such as Fibre Channel ports and iSCSI ports.
● Port group
A collection of multiple physical ports. If a port group is specified during the
creation of a mapping, storage resources and application servers in the
mapping communicate with each other using only the ports in the specified
port group.
● Reconstruction
A process of restoring the data saved on a faulty disk to hot spare CKs and
replacing the CKs on the faulty disk with the hot spare CKs. During data
reconstruction, valid data and parity data must be read and processed to
restore the data saved on a faulty disk to hot spare space, thereby ensuring
data security and reliability. Traditional reconstruction technologies allow only
all disks in the same RAID group as the faulty disk to participate in
reconstruction. The RAID 2.0+ technology enables all disks in the same
storage pool as the faulty disk to participate in reconstruction, boosting data
reconstruction speed and shortening data recovery duration.
● Deduplication
Data reduction technology that deletes duplicate data in a storage system to
reduce the capacity required for storing data.
● Data compression
Technology that compresses data without causing data loss, improving the
efficiency in data storage, transfer, and processing.
Storage system uses RAID 2.0+ for fine-grained division of SSDs to evenly
distribute data to all LUNs on each SSD and balance loads.
Process
Figure 2-1 shows the RAID 2.0+ block virtualization process when disk redundancy
is used.
……..
……..
……..
CK
CKG
Grain
Advantages
RAID 2.0+ has the following advantages over traditional RAID:
M Values
RAID levels determine the values of M. Dynamic RAID reconstruction only changes
the value of N. Table 2-1 describes M values for disk redundancy.
RAID Level M
RAID 5 1
RAID 6 (default) 2
RAID-TP 3
● RAID 5
NOTE
NOTE
The methods for calculating the number of RAID columns in the following three scenarios
are slightly different:
● On OceanStor Dorado 5000 V6/OceanStor Dorado 6000 V6, a storage pool spans over
multiple controller enclosures and contains disks from smart disk enclosures.
● On OceanStor Dorado 8000 V6/OceanStor Dorado 18000 V6, eight controllers are
configured without back-end full interconnection, and a storage pool spans over
multiple controller enclosures.
● A storage pool with a single controller enclosure is expanded to span over multiple
controller enclosures.
Number of member disks in a storage pool in the preceding formulas refers to the
number of disks owned by a single controller enclosure for a storage pool.
Example:
For RAID 6 or RAID-TP:
Number of RAID columns = Min [Number of disks owned by a single controller enclosure
for a storage pool – Number of reserved columns/2 (rounded up), 25]
Number of reserved columns = Max (1, Number of hot spare disks)
Example
A storage pool consists of 25 disks with RAID 6 (default value) and a hot spare
policy of Low (1 disk). The number of RAID columns is calculated as follows:
Number of reserved columns = Max (1, Number of hot spare disks) = 1
Number of RAID columns = Min (Number of member disks in a storage pool –
Number of reserved columns, 25) = Min (25 – 1, 25) = 24
The number of RAID columns (N+M) is 24 in this example.
RAID Usage
RAID usage = [(Number of RAID columns – Number of RAID parity columns M)/
Number of RAID columns] x 100%
Example
The number of RAID columns (N+M) from the previous example is 24. The RAID
level is RAID 6, so M is 2. RAID usage is therefore calculated as follows:
RAID usage = [(Number of RAID columns – Number of RAID parity columns M)/
Number of RAID columns] x 100% = [(24 - 2)/24] x 100% = 91.67%
The RAID usage is 91.67%.
Context
In common RAID mode (disk redundancy), CKs are distributed to different disks,
and the system can tolerate disk failures within the RAID redundancy capacity.
However, the system cannot tolerate disk enclosure failure.
Core service systems, such as core financial transaction systems, require that
storage systems be able to tolerate disk enclosure failure.
Storage system provides enclosure redundancy to meet such requirements. A
storage pool with enclosure redundancy has the following features:
● With RAID 6 or RAID 10, the system can tolerate a single disk enclosure
failure without service interruption or data loss.
● With RAID-TP, the system can ensure that services are not interrupted and
data is not lost when one disk enclosure fails and then a single disk in
another disk enclosure fails.
● After hot spare reconstruction is completed for a faulty disk, the system can
further tolerate the failure of a single disk enclosure.
● Enclosure redundancy automatically restores after the faulty disk enclosure is
recovered.
Implementation
Enclosure redundancy is implemented based on disk redundancy with additional
concerns about distribution of disks in different enclosures. In this example, the
storage system is configured with four enclosures, each of which has three disks.
Figure 2-2 shows how enclosure redundancy is implemented. CKs in the same
color form a CKG.
● To ensure service continuity in the event of a single disk enclosure failure, CKs
in each CKG come from different enclosures if possible and the number of CKs
from each enclosure does not exceed the RAID redundancy. For example, with
RAID 6 configured, a maximum of two CKs can be selected from each
enclosure. After an enclosure is faulty, only two copies of data are lost in each
CKG, and the lost data can be restored using the two parity columns, ensuring
service continuity. With RAID-TP configured, a maximum of two CKs can be
selected from each enclosure to ensure that the system can further tolerate
the failure of a single disk after a single disk enclosure failure.
That is, the storage system preferentially allocates blocks across enclosures to
form a CKG, and ensures that no more than two disks in each enclosure are
selected to form a CKG.
● The stripe length of each CKG is reduced by one, that is, the number of RAID
columns is (N+M) = 2 x K - 1, to ensure that the number of RAID data
columns N does not decrease after reconstruction is completed for a single
disk failure and the system can still tolerate the failure of a single enclosure. K
is the number of enclosures (controller enclosures + disk enclosures) that
provide disks for a storage pool. For example, in Figure 2-2, the number of
RAID columns is 7 (2 x 4 – 1). That is, the stripe length of each CKG is 7.
Restrictions
● To use enclosure redundancy, a storage pool must have disks from at least
four enclosures (disk enclosures + controller enclosures), and each enclosure
must provide at least three disks.
– For a 2 U device, disks in a storage pool must come from at least one
controller enclosure and three disk enclosures or at least four disk
enclosures. In addition, each enclosure must provide at least three disks.
– For a 4 U device, disks in a storage pool must come from at least four
disk enclosures, and each disk enclosure must provide at least three disks.
Redundancy Restoration
After the faulty enclosure is recovered, the background redundancy recovery task
identifies CKGs that do not meet enclosure redundancy requirements and migrates
block data in these CKGs to the recovered enclosure. The number of allocated
columns in a single enclosure is reduced, and enclosure redundancy is recovered.
Redundancy Capability
With the enclosure redundancy policy, a storage pool may provide enclosure
redundancy or disk redundancy capacity, or does not provide any redundancy
capacity.
● Enclosure redundancy
On DeviceManager, you can perform the following steps to view the redundancy
policy and redundancy capability of a storage pool:
1. Choose System > Storage Pools.
2. Click the name of the storage pool. On the Summary page, check Redundancy
Policy and Redundancy Capability.
……..
……..
……..
CK
CKG
Grain
M Values
RAID levels determine the values of M. Table 2-2 lists the values of M for
enclosure redundancy.
RAID Level M
RAID 6 2
RAID-TP (default) 3
RAID 10 2
Table 2-3 lists the number of RAID columns for some enclosure configurations.
4 12 5+2 4+3
5 15 7+2 6+3
6 18 9+2 8+3
……
13 39 23+2 22+3
14 42 23+2 22+3
……
NOTE
The values of K in the preceding formula for calculating the number of RAID columns are
slightly different in the following scenarios:
● On OceanStor Dorado 5000 V6/OceanStor Dorado 6000 V6, a storage pool spans over
multiple controller enclosures and contains disks from smart disk enclosures.
● On OceanStor Dorado 8000 V6/OceanStor Dorado 18000 V6, eight controllers are
configured without back-end full interconnection, and a storage pool spans over
multiple controller enclosures.
● A storage pool with a single controller enclosure is expanded to span over multiple
controller enclosures.
In these scenarios, the value of K is the number of enclosures (controller enclosures + disk
enclosures) that provide disks owned by a single controller enclosure.
For RAID 10, the number of RAID columns (N+M) is 4, wherein the number of
data columns N is 2 and that of parity columns M is 2.
RAID Usage
RAID usage = [(Number of RAID columns – Number of RAID parity columns M)/
Number of RAID columns] x 100%
RAID group due to continuous disk faults or disk replacement. Guaranteeing user
data redundancy is impossible without reconstruction.
Storage system overcomes this problem with dynamic RAID reconstruction by CK.
If the total number of available disks in a storage pool is less than the number of
RAID member disks, the system retains the number of parity columns (M) and
reduces the number of data columns (N) during reconstruction. After the
reconstruction, the number of member disks in the RAID group decreases, but the
RAID redundancy level remains unchanged. After the faulty disk is replaced, the
system increases the number of data columns to N based on the number of
available disks in the storage pool. N+M mode is used to write new data and
gradually rebalance data from the fault period.
Example
A storage pool consists of 13 disks with RAID 6 and a hot spare policy of Low (1
disk). The stripe length of CKGs is N+M = 10+2.
RAID 2.0+ block virtualization uses CKs from 12 disks (Disk 0 to Disk 11) to form a
CKG using the stripe structure with N as 10 and M as 2.
If a disk fails, the system excludes the disk IDs of the current CKG with mapping
information and then performs the following operations:
● If new CKs are available from a disk outside of the CKG (for example, only
Disk 4 is faulty and Disk 12 is available), the system directly reconstructs the
failed CK and maintains the RAID level of N+M.
Figure 2-4 Reconstruction with CKs from a disk outside of the CKG
● If external CKs are unavailable (for example, Disk 4 and Disk 12 fail
simultaneously), the CKG is recycled with garbage collection. A new CKG
without the failed disk is formed. The number of RAID columns in the new
CKG decreases to (N-1)+M or less after reconstruction, but M remains
unchanged.
Figure 2-5 Reconstruction without CKs from a disk outside of the CKG
Dynamic RAID reconstruction reduces the number of RAID data disks. The
system addresses faulty CKs by choosing new CKs from the available member
disks for a new CKG to restore the corrupted data. The new CKG disks are all
normal, so data redundancy remains the same. In this example, the original
stripe is 10+2 and the new stripe is 9+2.
Identifies CKGs
with high
garbage
proportions.
Valid data
Garbage data
No data
The global garbage collection mechanism reduces the amount of migrated data
during garbage collection, minimizes the impact of garbage collection on system
performance, and ensures system performance stability.
● The storage system calculates the capacity as follows: 1 PB = 1,024 TB, 1 TB = 1,024 GB,
1 GB = 1,024 MB, 1 MB = 1,024 KB, 1 KB = 1,024 bytes
● If an effective capacity license is not imported, the system is in traditional capacity
mode. If an effective capacity license is imported, the system is in effective capacity
mode.
NOTE
● Write back: A caching technique in which the completion of a write request is signaled
as soon as the data is in cache, and actual writing to non-volatile media occurs at a
later time.
● Write protection: Data writing to storage systems is prohibited.
Table 2-4 Scenarios where the write mode of LUNs changes to write protection
Malfunction Scenario Impact and
Type Recommended Action
The storage system is divided into multiple vNodes. Each vNode corresponds to a
group of CPU and memory resources. For example, each controller in OceanStor
Dorado 18000 V6 has four CPUs, and each CPU belongs to a vNode. In this way,
CPU resource scheduling is reduced, improving CPU usage.
1. The storage system calculates the hash value (shard) of a host I/O based on
its logical block addressing (LBA) and the hash factor, that is:
Shard = hash (I/O LBA, hash factor)
2. The intelligent distribution algorithm distributes data to different vNodes
based on shard values, ensuring that host data to LUNs is evenly distributed
to all vNodes.
● When Huawei UltraPath is used, UltraPath works closely with the storage
system. UltraPath uses an intelligent distribution algorithm to calculate the
shard value of each I/O, searches for the vNode in the storage system based
on the shard value, and distributes the I/O to the front-end link corresponding
to the vNode. This prevents data forwarding between vNodes.
● OceanStor Dorado 8000 V6 and 18000 V6 use FIMs. FIMs use the same
intelligent distribution algorithm as UltraPath to distribute I/Os to each
controller.
● If neither UltraPath nor the FIM is used, the storage system calculates the
shard values upon reception of host I/Os and then forwards the I/Os to the
corresponding vNodes based on the shard values for later processing.
... ...
Networking
OceanStor Dorado V6
LAN/WAN
Management Management
server server
OceanStor Dorado V6 series storage systems OceanStor Dorado V6 series storage systems
Networking
OceanStor Dorado V6
This chapter describes how to plan storage resources and management user
accounts to facilitate subsequent configurations and management.
3.1 Planning Storage Resources
3.2 Planning Management User Accounts
For details about the available capacity and purchased capacity, contact your local
Huawei representative office or Huawei authorized distributor.
When planning the available capacity, you must consider the nominal disk
capacity, hot spare capacity, and RAID usage.
NOTE
NOTE
● RAID 2.0+ allows all member disks in a storage pool to provide hot spare capacity. For
ease of understanding, the hot spare capacity is expressed in the number of hot spare
disks on DeviceManager.
● Even if the hot spare space is used up, the system can use the free space of the storage
pool to reconstruct data, ensuring storage system reliability.
In the commands:
● provisioning_limit_switch indicates whether to enable the overcommitment
ratio of the storage pool. Possible values are off and on. The default value is
off, indicating that the system does not limit the ratio of the total LUN and
file system capacity to the total storage pool capacity.
● provisioning_limit indicates the upper limit for the percentage of the total
LUN and file system capacity to the total storage pool capacity. That is,
provisioning_limit = (Total capacity of LUNs and file systems/Total capacity
of the storage pool) x 100. For example, provisioning_limit=120 indicates
that the total LUN and file system capacity can be 120% of the total storage
pool capacity.
– When a LUN or file system is created, the system determines whether
[(Capacity of the new LUN or file system + Existing capacity)/Total
capacity of the storage pool] x 100 exceeds the specified storage pool
overcommitment ratio. If not, the creation is successful. If yes, the
creation fails.
– When the capacity of a LUN or file system is expanded, the system
determines whether [(Capacity added to the LUN or file system + Existing
capacity)/Total capacity of the storage pool] x 100 exceeds the specified
storage pool overcommitment ratio. If not, the expansion is successful. If
yes, the expansion fails.
– When the storage pool overcommitment ratio is modified, the system
only checks the parameter validity and does not check the capacity. For
example, if the total capacity of LUNs and file systems has reached 130%
of the total storage pool capacity and the current overcommitment ratio
is provisioning_limit=150, you can still change provisioning_limit to 120
to limit later new or expanded LUNs and file systems.
– The provisioning_limit field is valid only when
provisioning_limit_switch is set to on.
NOTE
● For versions earlier than 6.1.3, the storage pool overcommitment ratio takes effect only
for LUNs.
● For 6.1.3 and later versions, the storage pool overcommitment ratio takes effect for both
LUNs and file systems.
● The Provisioning Limit Switch and Provisioning Limit fields in the show storage_pool
general pool_id=? command output indicate the enabling status and configured value
of the overcommitment ratio.
● For details on this command, refer to the Command Reference.
NOTE
● In CLI mode, you can run the create disk_domain name=? disk_list=? and create
storage_pool name=? disk_list=? commands to create a disk domain and a
storage pool, respectively.
● If you run the create disk_domain name=? disk_list=? command to create a disk
domain, the default redundancy policy is disk redundancy. If you want to create a
storage pool with enclosure redundancy, add redundancy_strategy=enclosure in
the command to create a disk domain.
● In CLI mode, you can also directly run the create storage_pool name=? disk_list=?
command to create a storage pool. After a storage pool is created, the system
automatically creates the corresponding disk domain.
● This document describes how to configure storage services on the GUI. For details
about commands, refer to the command reference specific to your product model
and version.
● A storage system supports one or more storage pools.
– During the initial configuration of a storage system, you can configure
that all disks constitute a unique storage pool. After this configuration
applies, you do not need to manually create any storage pool.
NOTE
For details about how to initialize a storage system, see "Logging In and Starting
Initialization" in the initialization guide specific to your product model and
version.
– You can manually create one or more storage pools. DeviceManager
automatically selects appropriate disks to create a storage pool.
Alternatively, you can select desired disks to create a storage pool.
● With disk redundancy, a single storage pool requires at least eight normal
member disks. The minimum number of disks required for creating a storage
pool that spans multiple controller enclosures is calculated as follows:
Minimum number of disks = 8 x Number of controller enclosures that the
storage pool spans
● With enclosure redundancy, disks in a storage pool must come from at least
four enclosures (disk enclosures + controller enclosures), and each enclosure
must provide at least three disks. For a 4 U device, the minimum number of
disks required for creating a storage pool that spans multiple controller
enclosures is calculated as follows:
– With back-end full interconnection: Minimum number of disks = 8 x
Number of controller enclosures that the storage pool spans
– Without back-end full interconnection: Minimum number of disks = 12 x
Number of controller enclosures that the storage pool spans
Name User-defined
Description User-defined
Storage Pool Select the storage pool to which the LUN belongs.
Quantity User-defined
Map to Host Select the host for mapping with your created LUN.
Application Type Select an application type based on the service I/O model.
Preset application types are provided for typical applications.
In block service scenarios, possible options are Default,
Oracle_OLAP, Oracle_OLTP, Oracle_OLAP&OLTP,
SQL_Server_OLAP, SQL_Server_OLTP,
SQL_Server_OLAP&OLTP, SAP_HANA, Vmware_VDI,
Hyper-V_VDI, Others, and FusionAccess_VDI.
NOTE
● The preset application types specify the application request sizes.
When SmartCompression and SmartDedupe licenses are
imported to the system, the preset application types also display
whether SmartCompression and SmartDedupe are enabled. For
details, see SmartDedupe and SmartCompression Feature Guide
for Block of the desired product model and version.
● After you have set an application type for a LUN, you are unable
to change it in follow-up operations.
● If the application type configured for a LUN does not match the
actual I/O model, the LUN performance may deteriorate.
● If none of the preset application types matches the actual I/O
model, you can run the create lun_workload_type general
command to create one. For details on this command, refer to
the command reference.
● Only 6.1.3 and later versions support Others.
This chapter describes how to configure the storage system to divide the storage
space into LUNs and map them to application servers so that the application
servers can read and write the storage space.
4.1 Configuration Process
4.2 Check Before Configuration
4.3 Logging In to DeviceManager
4.4 Creating a Storage Pool
4.5 Creating a LUN
4.6 (Optional) Creating a LUN Group
4.7 Creating a Host
4.8 (Optional) Creating a Host Group
4.9 (Optional) Creating a Port Group
4.10 Creating a Mapping
4.11 Configuring the Host Connectivity
4.12 Using the Storage Space on an Application Server
4.13 More Configuration Scenarios
Start
Log in to DeviceManager.
Create a host.
Configure connectivity.
End
Mandatory Optional
NOTE
The above flowchart shows a common configuration process. DeviceManager uses a brand-
new interface interaction design, which simplifies resource allocation and supports various
flexible configurations of mappings. You can select a proper one based on service
requirements.
Checking Licenses
Log in to DeviceManager. Check whether licenses have been imported and contain
the same basic or value-added features you purchased.
● If the licenses are different from those you purchased, contact technical
support.
● If an effective capacity license has been purchased, ensure that the effective
capacity meets actual service requirements.
Connection When an iSCSI front- In the CLI of the application server, run
between the end port on the ping ip (if IPv4 is used) or ping -6 ip
storage storage system is (if IPv6 is used), where ip indicates the
system and used for connection, IP address of the iSCSI front-end port.
the check whether the ● If the application server receives
application iSCSI front-end port is data packets from the iSCSI front-
server (using communicating with end port, this indicates that the
a Windows the service network communication between the
application port on the storage system and application
server as an application server server is normal.
example) properly.
● If the application server receives no
data packets from the iSCSI front-
end port, replace the network cable,
change the IP address of the iSCSI
front-end port, or add a route
between the iSCSI front-end port
and service network port, and try
again.
For details on how to change the IP
address of an iSCSI front-end port
or add a route between an iSCSI
front-end port and a service
network port, see the
DeviceManager online help.
Procedure
Step 1 Choose System > Storage Pools.
NOTE
The screenshot is for reference only and the actual GUI may vary.
Data Encryption Indicates whether to enable data encryption for all self-
encrypting disks (SEDs) in the storage pool.
● If this function is disabled, the storage pool is not
encrypted.
● If this function is enabled, the storage pool is encrypted.
Ensure that you select only SEDs.
NOTE
If this function is enabled, the system automatically checks whether
the key service has been configured. If the key service has not been
configured, the system will prompt you to configure the key service.
For details, see the Disk Encryption User Guide specific to your
product model and version.
Parameter Description
Parameter Description
RAID Policy RAID policy of the storage pool. Dynamic RAID is used.
Dynamic RAID reconstruction uses the erasure coding (EC)
algorithm, which dynamically adjusts the number of chunks
in a chunk group under all-SSD configurations to ensure
system reliability and capacity. If a chunk is faulty and no
chunk is available from disks outside the storage pool, the
system dynamically reconstructs the original N+M chunks to
(N-1)+M chunks. When a new SSD is inserted, the system
migrates data from the (N-1)+M chunks to the newly
constructed N+M chunks for efficient disk usage.
The RAID levels are defined as follows:
● RAID 5: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
one chunk. RAID 5 is able to tolerate the failure on only
one chunk. If two or more chunks fail, data in the chunk
group cannot be recovered.
● RAID 6: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
two chunks. RAID 6 is able to tolerate simultaneous
failures on two chunks. If three or more chunks fail, data
in the chunk group cannot be recovered.
● RAID-TP: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
three chunks. RAID-TP is able to tolerate simultaneous
failures on three chunks. If four or more chunks fail, data
in the chunk group cannot be recovered.
NOTE
● When Redundancy Policy is set to Disk redundancy, possible
options for this parameter are RAID 5, RAID 6, and RAID-TP.
● When Redundancy Policy is set to Enclosure redundancy,
possible options for this parameter are RAID 6 and RAID-TP.
[Default value]
RAID 6 for disk redundancy and RAID-TP for enclosure
redundancy
Parameter Description
SmartTier Manually select drives of the SCM and SSD types to activate
SmartTier.
SCM drive types include SCM drives.
SSD drive types include SSDs and NVMe SSDs.
NOTE
This parameter is available only when Redundancy Policy is set to
Disk redundancy and the selected controller enclosure contains
SCM drives.
Parameter Description
Hot Spare Policy Hot spare policy of the storage pool. Hot spare space stores
data from the failed member disks to ensure system
continuity and reliability.
[Value range]
None, Low (1 disk), High (2 disks), Custom (3 disks),
Custom (4 disks), Custom (5 disks), Custom (6 disks),
Custom (7 disks), and Custom (8 disks)
[Default value]
Low (1 disk)
NOTE
● Hot spare capacity is provided by all member disks in each
storage pool because the storage system uses RAID 2.0+
virtualization technology. For ease of understanding, the hot
spare capacity is expressed in the number of hot spare disks on
DeviceManager.
● Even if the hot spare space is used up, the system can use the
free space of the storage pool to reconstruct data, ensuring
storage system reliability.
Parameter Description
NOTE
----End
Context
You can learn about storage principles such as redundancy policies, RAID policies,
and hot spare policies by referring to section "Basic Storage Principles." You can
learn how to plan storage pool parameters by referring to section "Planning
Storage Pools."
Procedure
Step 1 Choose System > Storage Pools.
NOTE
The screenshot is for reference only and the actual GUI may vary.
Parameter Description
Parameter Description
Data Encryption Indicates whether to enable data encryption for all self-
encrypting disks (SEDs) in the storage pool.
● If this function is disabled, the storage pool is not
encrypted.
● If this function is enabled, the storage pool is encrypted.
Ensure that you select only SEDs.
NOTE
If this function is enabled, the system automatically checks whether
the key service has been configured. If the key service has not been
configured, the system will prompt you to configure the key service.
For details, see the Disk Encryption User Guide specific to your
product model and version.
Parameter Description
RAID Policy RAID policy of the storage pool. Dynamic RAID is used.
Dynamic RAID reconstruction uses the erasure coding (EC)
algorithm, which dynamically adjusts the number of chunks
in a chunk group under all-SSD configurations to ensure
system reliability and capacity. If a chunk is faulty and no
chunk is available from disks outside the storage pool, the
system dynamically reconstructs the original N+M chunks to
(N-1)+M chunks. When a new SSD is inserted, the system
migrates data from the (N-1)+M chunks to the newly
constructed N+M chunks for efficient disk usage.
The RAID levels are defined as follows:
● RAID 5: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
one chunk. RAID 5 is able to tolerate the failure on only
one chunk. If two or more chunks fail, data in the chunk
group cannot be recovered.
● RAID 10: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
two chunks. RAID 10 is able to tolerate simultaneous
failures on two chunks. If three or more chunks fail, data
in the chunk group cannot be recovered. The number of
chunks in a chunk group is fixed to 4.
● RAID 6: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
two chunks. RAID 6 is able to tolerate simultaneous
failures on two chunks. If three or more chunks fail, data
in the chunk group cannot be recovered.
● RAID-TP: Parity data is distributed on different chunks. In
each chunk group, the parity data occupies the space of
three chunks. RAID-TP is able to tolerate simultaneous
failures on three chunks. If four or more chunks fail, data
in the chunk group cannot be recovered.
NOTE
● For 6.1.2 and later versions, RAID 5 can be configured only in CLI
mode.
● When Redundancy Policy is set to Disk redundancy, possible
options for this parameter are RAID 6 and RAID-TP.
● When Redundancy Policy is set to Enclosure redundancy,
possible options for this parameter are RAID 10, RAID 6 and
RAID-TP.
[Default value]
RAID 6 for disk redundancy and RAID-TP for enclosure
redundancy
Parameter Description
SmartTier Manually select drives of the SCM and SSD types to activate
SmartTier.
SCM drive types include SCM drives.
SSD drive types include SSDs and NVMe SSDs.
NOTE
This parameter is available only when Redundancy Policy is set to
Disk redundancy and the selected controller enclosure contains
SCM drives.
Parameter Description
Hot Spare Policy Hot spare policy of the storage pool. Hot spare space stores
data from the failed member disks to ensure system
continuity and reliability.
[Value range]
None, Low (1 disk), High (2 disks), Custom (3 disks),
Custom (4 disks), Custom (5 disks), Custom (6 disks),
Custom (7 disks), and Custom (8 disks)
[Default value]
Low (1 disk)
NOTE
● Hot spare capacity is provided by all member disks in each
storage pool because the storage system uses RAID 2.0+
virtualization technology. For ease of understanding, the hot
spare capacity is expressed in the number of hot spare disks on
DeviceManager.
● Even if the hot spare space is used up, the system can use the
free space of the storage pool to reconstruct data, ensuring
storage system reliability.
Parameter Description
NOTE
NOTE
After the task is created successfully, the Execution Result page is displayed. You can view
details about the current task on this page.
----End
Context
● All LUNs created in a storage system are thin LUNs, which are logical disks
accessible to hosts. The storage system dynamically allocates storage
resources to thin LUNs based on actual capacities used by hosts, instead of
allocating all preset capacities. The total capacity allocated to a thin LUN will
not exceed its preset capacity.
● For details about the specifications, visit Specifications Query.
● Before creating a LUN, you are advised to clear any alarms indicating that the
storage pool capacity is about to be used up.
● The total capacity configured for all LUNs in a storage pool can exceed the
actual capacity of the storage pool. If an alarm is generated, indicating that
the storage pool capacity is used up, you are advised to expand the storage
pool as soon as possible.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Click Create.
The Create LUN page is displayed on the right.
NOTE
The screenshot is for reference only and the actual GUI may vary.
NOTE
For some device models, you can click in the upper right corner of the page to enable
SmartGUI. SmartGUI mines users' historical operation data and builds a configuration
parameter recommendation model based on user profiles to recommend configuration
parameters for the block service and file service. After SmartGUI is enabled, the system
presets parameters based on recommendations when you create a LUN. You can click
Modify in the upper right corner to modify the parameters or directly click OK to create a
LUN.
Capacity Capacity of the LUN. This is the maximum capacity that will
be allocated to a thin LUN. The total storage resources
dynamically allocated to the thin LUN must not exceed the
value of this parameter.
NOTE
● The maximum capacity of the LUN must not exceed the system
specifications. For details about the specifications, visit
Specifications Query.
● You can set the capacity unit to Blocks to create LUNs by block.
A block is equal to 512 bytes. The LUN capacity must not be
smaller than 1024 blocks (that is, 512 KB).
● Storage system capacity equation: 1 PB = 1,024 TB, 1 TB = 1,024
GB, 1 GB = 1,024 MB, 1 MB = 1,024 KB, 1 KB = 1,024 bytes.
Parameter Description
Start Number Start number from which the system incrementally adds a
suffix number to the name of each LUN for distinction.
[Value range]
0 to (10000 – Number of LUNs created in a batch)
NOTE
● This parameter is displayed only when Quantity is greater than
1 and Advanced is selected.
● For example, if you want to create 300 LUNs, the value range of
the start number is 0 to 9700.
Application Type Application type of the LUN. Preset application types are
provided for typical applications. In block service scenarios,
possible options are Default, Oracle_OLAP, Oracle_OLTP,
Oracle_OLAP&OLTP, SQL_Server_OLAP, SQL_Server_OLTP,
SQL_Server_OLAP&OLTP, SAP_HANA, Vmware_VDI,
Hyper-V_VDI, and FusionAccess_VDI.
NOTE
● The preset application types specify the application request sizes.
When SmartCompression and SmartDedupe licenses are
imported to the system, the preset application types also display
whether SmartCompression and SmartDedupe are enabled.
Application Request Size is 32 KB for Oracle_OLAP and
SQL_Server_OLAP, and 8 KB for the other preset application
types. For details, see SmartDedupe and SmartCompression
Feature Guide for Block of the desired product model and
version.
● After you have set an application type for a LUN, you are unable
to change it in follow-up operations.
● If the application type configured for a LUN does not match the
actual I/O model, the LUN performance may deteriorate.
● If none of the preset application types matches the actual I/O
model, you can run the create lun_workload_type general
command to create one. For details on this command, refer to
the command reference.
● The application request sizes specified by preset application
types may vary with product models. The actual values displayed
on the page prevail.
Map to Host Host to which the LUN you are creating is mapped.
NOTE
● If no host is available in the system, click Create.
● You can also map the LUNs after creating them.
Parameter Description
NOTE
Description, Start ID, Start Number, Host LUN ID, and SmartCache Partition are hidden
parameters. You can click Advanced to display them.
----End
Context
● All LUNs created in a storage system are thin LUNs, which are logical disks
accessible to hosts. The storage system dynamically allocates storage
resources to thin LUNs based on actual capacities used by hosts, instead of
allocating all preset capacities. The total capacity allocated to a thin LUN will
not exceed its preset capacity.
● For details about the specifications, see the Specifications Query tool.
● Before creating a LUN, you are advised to clear any alarms indicating that the
storage pool capacity is about to be used up.
● The total capacity configured for all LUNs in a storage pool can exceed the
actual capacity of the storage pool. If an alarm is generated, indicating that
the storage pool capacity is used up, you are advised to expand the storage
pool as soon as possible.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
The screenshot is for reference only and the actual displayed information may vary.
For some device models, you can click in the upper right corner of the page to enable
SmartGUI. SmartGUI mines users' historical operation data and builds a configuration
parameter recommendation model based on user profiles to recommend configuration
parameters for the block service and file service. After SmartGUI is enabled, the system
presets parameters based on recommendations when you create a LUN. You can click
Modify in the upper right corner to modify the parameters or directly click OK to create a
LUN.
Capacity Capacity of the LUN. This is the maximum capacity that will
be allocated to a thin LUN. The total storage resources
dynamically allocated to the thin LUN must not exceed the
value of this parameter.
NOTE
● The maximum capacity of the LUN must not exceed the system
specifications. For details about the specifications, see the
Specifications Query tool.
● You can set the capacity unit to Blocks to create LUNs by block.
A block is equal to 512 bytes. The LUN capacity must not be
smaller than 1024 blocks (that is, 512 KB).
● The storage system uses the following capacity algorithms
defined by Windows: 1 PB = 1,024 TB, 1 TB = 1,024 GB, 1 GB =
1,024 MB, 1 MB = 1,024 KB, and 1 KB = 1,024 bytes.
Parameter Description
Add to LUN Existing LUN group to which the created LUN is added.
Group NOTE
Parameters Add to LUN Group and Map to Host cannot be
specified at the same time.
Parameter Description
Map to Host Host to which the LUN you are creating is mapped.
NOTE
● If no host is available in the system, click Create.
● You can also map the LUNs after creating them.
Port Group Port group to which the mapping is added. After this
parameter is specified, the LUN and its mapped host are
added to the port group for communication.
NOTE
● This parameter is displayed only when Map to Host is specified.
● If no port group is available, click Create to create one.
NOTE
Description, Start ID, SmartCache Partition, and Host LUN ID are hidden parameters. To
display hidden parameters, click Advanced.
NOTE
If the LUN is mapped to a host, after the task is created successfully, the Execution Result
page is displayed. You can view details about the current task on this page.
----End
Context
For details about the specifications, see the Specifications Query tool.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
The screenshot is for reference only and the actual displayed information may vary.
For some device models, you can click in the upper right corner of the page to enable
SmartGUI. SmartGUI mines users' historical operation data and builds a configuration
parameter recommendation model based on user profiles to recommend configuration
parameters for the block service and file service. After SmartGUI is enabled, the system
presets parameters based on recommendations when you create a LUN group. You can click
Modify in the upper right corner to modify the parameters or directly click OK to create a
LUN group.
NOTE
The following preset application types are provided for typical applications:
Default, Oracle_OLAP, Oracle_OLTP, Oracle_OLAP&OLTP,
SQL_Server_OLAP, SQL_Server_OLTP, SQL_Server_OLAP&OLTP,
SAP_HANA, Vmware_VDI, Hyper-V_VDI, Others, and FusionAccess_VDI
○ The preset application types specify the application request sizes. When
SmartCompression and SmartDedupe licenses are imported to the
system, the preset application types also display whether
SmartCompression and SmartDedupe are enabled. For details, see
SmartDedupe and SmartCompression Feature Guide for Block of the
desired product model and version.
○ After you have set an application type for a LUN, you are unable to
change it in follow-up operations.
○ If the application type configured for a LUN does not match the actual
I/O model, the LUN performance may deteriorate.
○ If none of the preset application types matches the actual I/O model,
you can run the create lun_workload_type general command to create
one. For details on this command, refer to the Command Reference.
○ Only 6.1.3 and later versions support Others.
ii. Specify the LUN name prefix, capacity per LUN, and quantity. Table
4-7 describes the parameters.
Parameter Description
Name Prefix Name prefix of the LUN. The names of the new
LUNs are numbered in sequence based on the
name prefix.
Parameter Description
iii. (Optional) When creating LUNs in a batch, click and set the
suffixes of the LUNs. Related parameters include Suffix Digits and
Suffix (start number of the suffixes). The system adds a suffix to the
end of each LUN name in ascending order based on the specified
start suffix number.
NOTE
You can select Only show the LUNs that do not belong to any LUN group to
view LUNs that do not belong to any LUN group.
If no host or host group exists in the system, click Create to create one.
b. Select a port group.
NOTE
▪ To display this option, select the host or host group to which the LUN group is
to be mapped.
c. Select Advanced in the upper right corner and set how to assign host
LUN IDs.
▪ Start ID: Set a start ID ranging from 0 to 4095. The system assigns a
host LUN ID to each LUN mapped to a host, starting from Start ID.
NOTE
After the task is created successfully, the Execution Result page is displayed. You can view
details about the current task on this page.
----End
Context
● DeviceManager not only allows users to manually create hosts but also
provides the host scan function. To use the host scan function, perform the
following operations:
a. Install UltraPath on a host and connect the host to the storage system
over a physical network.
b. On DeviceManager, choose Settings > Block Service. Click Modify in the
upper right corner of the page. In the UltraPath Host Scan area, enable
Scan for Host.
c. Scan for disks on hosts and wait for about 4 minutes.
d. On DeviceManager, choose Services > Block Service > Host Groups >
Hosts and click Scan for Host. The system automatically scans for all
hosts connected to the storage system, identifies their WWNs or IQNs,
and creates corresponding virtual hosts on the storage system. If a host
has multiple WWNs or IQNs, the system can automatically identify and
configure them on the same host.
● When a host is created, the storage system automatically sets the default host
access mode based on the host operating system. For example, in 6.1.3, if OS
is set to Windows or Solaris when a host is created, Host Access Mode is
Asymmetric by default. For details about how to change the host access
mode, see 5.7.14 Modifying the Properties of a Host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, choose Create > Create Host.
The Create Host page is displayed on the right.
NOTE
The screenshot is for reference only and the actual GUI may vary.
Parameter Description
NOTE
Parameters Description and Location are hidden. You can click Advanced to display them.
2. For an FC initiator, you need to select the vStore to which the initiator
belongs. An FC initiator whose owning vStore is the same as that of the
created host or whose owning vStore is -- can be added to the host.
For iSCSI and NVMe over RoCE initiators, you can only add initiators whose
owning vStore is the same as that of the created host to the host.
3. If initiators have been configured on the application server, select one or more
initiators in the initiator list. If no initiator is available in the list, click Create
Initiator below the initiator list to manually create an initiator.
NOTE
Step 6 (Optional) Click Create Initiator. On the Create Initiator page that is displayed,
set the related parameters.
NOTE
Parameter Description
Normal The normal session is the process during which the target
Authentication and initiator transmit data between each other after
connections have been set up. Authentication modes include:
● No authentication
● Unidirectional authentication
The target authenticates the initiator.
● Bidirectional authentication
The target and initiator authenticate each other.
Parameter Description
Discovery The discovery session is the process during which the target
Authentication and initiator are setting up connections. Authentication
modes include:
● No authentication
● Unidirectional authentication
The target authenticates the initiator.
● Bidirectional authentication
The target and initiator authenticate each other.
NOTE
When Normal Authentication or Discovery Authentication is set to
Bidirectional authentication, you need to specify the CHAP Name
and Password, and confirm the password in both the Target
Authenticates Initiator and Initiator Authenticates Target areas.
Parameter Description
Parameter Description
NOTE
After you click OK, the new initiator is automatically added to the list on the right.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, choose Create > Create Hosts.
The Create Hosts page is displayed on the right.
NOTE
The screenshot is for reference only and the actual GUI may vary.
Parameter Description
NOTE
Parameters Description and Location are hidden. You can click Advanced to display them.
----End
Context
Hosts in a host group can run different operating systems.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
The screenshot is for reference only and the actual GUI may vary.
Owning vStore vStore to which the newly created host group belongs.
NOTE
This parameter is mandatory when vStore is set to All
vStores in Step 2.
Step 5 Select one or more hosts from Available Hosts and add them to Selected Hosts.
NOTE
● You can select Only show the hosts that have not been added to any host group
below the host list, which helps you find the desired hosts.
● You can click Create Host below the host list to create a host.
----End
Procedure
Step 1 Choose Services > Block Service > Port Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
The screenshot is for reference only and the actual GUI may vary.
Step 4 Set parameters of the port group. Table 4-14 describes the parameters.
Parameter Description
Owning vStore Specifies the vStore to which the newly created host
belongs.
NOTE
This parameter is mandatory when vStore is set to All
vStores in Step 2.
Step 5 Select one or more desired ports from the port list on the left and they are
displayed in the port list on the right.
NOTE
----End
Context
● Skip this section if you have specified Map to Host when creating a LUN or
Map to Host (or Host Group) when creating a LUN group.
Creating a Mapping
DeviceManager provides various simple and flexible methods for you to create the
following mappings:
● Mapping between LUNs and a host
You can directly map one or more LUNs to a host in a simple application
scenario or when no LUN groups are required.
● Mapping between a LUN group and a host
If an application requires multiple LUNs, you can use a LUN group to manage
these LUNs. In this case, create a mapping between the LUN group and the
host.
● Mapping between a LUN group and a host group
If an application has its data stored on multiple LUNs and is deployed on a
cluster consisting of multiple hosts, you can use a LUN group to manage the
LUNs and a host group to manage the hosts. In this case, create a mapping
between the LUN group and the host group.
One LUN group One host + (optional) a 1. Choose Services > Block
port group Service > LUN Groups > LUN
Groups.
The LUN group management
page is displayed.
One host group One LUN group + 1. Choose Services > Block
(optional) a port group Service > Host Groups > Host
Groups.
The host group management
page is displayed.
2. Select a host group, choose
Map > Map LUN Group.
On the displayed Map LUN
Group page, set the required
parameters.
NOTE
● This section describes only the navigation paths in various scenarios. For details about
the operations, see corresponding sections in "Managing Basic Storage Services."
● GUIs may vary with product versions and models. The actual GUIs prevail.
Storage system uses logical ports to establish iSCSI connections with hosts. The
home ports of logical ports can be Ethernet ports, bond ports, or VLANs.
● If the storage system communicates with the host using logical ports that
reside on Ethernet ports, configure the storage service ports and other
connectivity configurations by referring to "Establishing iSCSI Connections" in
the Host Connectivity Guide.
● If the storage system communicates with the host using logical ports that
reside on bond ports or VLANs, configure the storage service ports by
following instructions in this section and then configure the connectivity by
referring to "Establishing iSCSI Connections" in the Host Connectivity Guide.
NOTE
If the storage system is connected to a host over Fibre Channel connections, configure the
host and storage system by referring to the Host Connectivity Guide.
Basic Concepts
Table 4-16 lists the basic concepts related to iSCSI Connections.
Bond port To improve reliability of paths for accessing file systems and
increase bandwidth, you can bond multiple Ethernet ports on
the same controller to form a bond port.
Logical port Logical ports are virtual ports created based on bond ports,
VLANs, or Ethernet ports. A unique IP address is allocated to
each logical port to carry host services.
Relationship Among Logical Ports, Ethernet Ports, VLANs, and Bond Ports
Logical ports can be created based on Ethernet ports, VLANs, or bond ports.
Figure 4-2 shows the relationship among logical ports, Ethernet ports, VLANs, and
bond ports.
Figure 4-2 Relationship among logical ports, Ethernet ports, VLANs, and bond
ports
Table 4-17 explains the meaning of each mark number in the preceding figure.
Prerequisites
The IP addresses of the Ethernet ports you want to bond have been cleared.
Ethernet ports that have IP addresses cannot be bonded.
Context
Port bonding provides more bandwidth and higher redundancy for links. Although
ports are bonded, each session still transmits data through a single port and the
total bandwidth can be increased only when there are multiple sessions.
Determine whether to bond ports based on site requirements.
NOTICE
To disable the TOE function of the bonded ports, contact Huawei technical
support.
For versions earlier than 6.1.3, OceanStor Dorado 8000 and OceanStor Dorado
18000 do not support cross-card bonding.
For the OceanStor Dorado 8000 and OceanStor Dorado 18000, each interface
module can use only one bonding mode. That is, an interface module does
not allow bonding across modules and bonding within the module at the
same time.
NOTICE
The link aggregation modes vary with switch manufacturers. If a switch from
another vendor is used, contact technical support of the switch manufacturer
for specific link aggregation configurations.
Procedure
Step 1 Choose Services > Network > Ethernet Network > Bond Ports.
Step 3 Set a bond name and select ports you want to bond.
1. Specify a name for the bond port in Name.
NOTE
----End
Follow-up Procedure
To configure an IP address for a bond port, run the change bond_port
ipv4_address bond_port_name=? ip=? mask=? or change bond_port
ipv6_address bond_port_name=? ip=? prefix_length=? command. For details
about this command, see the command reference specific to your product model.
Example:
admin:/>change bond_port ipv4_address bond_port_name=bond1 ip=192.168.1.1 mask=255.255.0.0
DANGER: You are about to change the IP address of port. This operation will disconnect the storage system
from hosts. This operation will also clear the configured routes on the IP address that is modified on this
port.
Suggestion:
1. Check whether there are redundant connections to hosts. If there are no redundant connections, stop
host services.
2. Ensure that the entered IP address is available.
Have you read danger alert message carefully?(y/n)y
Context
● VLANs are created on Ethernet or bond ports.
● VLANs cannot be created on the Ethernet ports that are configured with IP
addresses or carry services.
● A bond port instead of its member ports can be used to create a VLAN.
● The host ports and storage ports in the same VLAN must have the same
VLAN IDs.
Procedure
Step 1 Choose Services > Network > Ethernet Network > VLANs.
Step 2 Click Create.
The Create VLAN page is displayed on the right.
Step 3 In the Port Type drop-down list, select the type of the ports used to create VLANs.
Possible values are Ethernet Port and Bond Port.
Step 4 In the Home Port list, select a home port.
Step 5 In ID, specify the ID of a VLAN, and then click Add.
NOTE
● The VLAN ID ranges from 1 to 4094. You can specify multiple VLAN IDs one by one or in
a batch. When creating multiple VLANs and specifying VLAN IDs in a batch, the VLAN
IDs are in the following format: Start VLAN ID-End VLAN ID.
● To delete a VLAN ID, click next to it.
----End
Follow-up Procedure
When creating a logical port based on a VLAN, ensure that the port type is VLAN
and the home port is the VLAN's home port.
Context
Only logical ports that support iSCSI and NVMe over RoCE can be used to carry
block services. For iSCSI connections, select iSCSI as the data protocol for a logical
port.
Procedure
Step 1 Choose Services > Network > Logical Ports.
Parameter Description
Data Protocol Data protocol of the logical port. Possible values are NFS,
CIFS, NFS + CIFS, iSCSI, and NVMe over RoCE.
NOTE
● NFS, CIFS, and NFS + CIFS are applicable to file services. iSCSI
and NVMe over RoCE are applicable to block services.
● For iSCSI connections, select iSCSI.
IP Address Type IP address type of the logical port, which can be IPv4 or
IPv6.
Parameter Description
Port Type Type of the logical port. Possible values are Ethernet Port,
Bond Port, and VLAN.
NOTE
This parameter takes the fixed value of VLAN when Data Protocol
is NVMe over RoCE.
Home Port Ethernet port, bond port, or VLAN to which the logical port
belongs.
----End
Configuration Method
Verify that storage resources required by services have been successfully created
on the storage system. The storage resources include storage pools, LUNs, hosts,
and mappings between hosts/host groups and LUNs/LUN groups.
● Network using the iSCSI or FC-SCSI protocol
Configure the connectivity by following instructions in the "Configuring
Connectivity" in Host Connectivity Guide.
AIX https://support.huawei.com/enterprise/en/doc/
EDOC1100113069
HP-UX https://support.huawei.com/enterprise/en/doc/
EDOC1100117891
Solaris https://support.huawei.com/enterprise/en/doc/
EDOC1100113071
SUSE https://support.huawei.com/enterprise/en/doc/
EDOC1100117892
Windows https://support.huawei.com/enterprise/en/doc/
EDOC1100116985
Prerequisites
● The application server is communicating properly with the storage system.
● The planned storage capacity has been allocated to the application server.
● Multipathing software has been installed and configured for the application
server when redundant paths exist between the application server and the
storage system. This prevents multiple LUNs from being repetitively mapped
to the application server.
NOTE
Precautions
● Do not allocate disks in use to other applications. Otherwise, data security
will be compromised.
● If a host login error occurs, operations on disks affect the running of
applications.
● If compatibility issues occur, use of the storage space on application servers
may be compromised.
● When unmapping a LUN, delete the residual information of the original
mapping on the host side to prevent exceptions. For details, see section
"FAQs" in the Host Connectivity Guide.
Context
The maximum LUN capacity that can be identified by an application server varies
according to the operating system and file system used by the application server.
Table 4-20 lists the maximum LUN capacity supported by various operating
systems.
NOTE
● Plan the capacity of a LUN before mapping it to an application server. If the LUN
capacity exceeds the specifications, the application server will fail to identify the LUN.
● The above table lists the maximum LUN capacities supported by some common
operating systems. For the maximum LUN capacities of other operating systems, consult
technical support engineers. The actual specifications prevail.
Configuration Method
For details, see the Host Connectivity Guide.
Procedure
Step 1 Create a PE LUN and map it to a VMware ESXi host.
NOTE
● For details about how to configure basic storage services, such as creating a storage
pool, creating a PE LUN, creating a host, and mapping a PE LUN, see the corresponding
sections in this document.
● For details about how to configure the connectivity between a storage system and a
VMware ESXi host, see the Host Connectivity Guide.
Step 2 Configure the VVol function by following instructions in the eSDK Enterprise
Storage Plugins VASA user guide.
● Obtain the corresponding user guide.
a. Go to resource pages of eSDK Enterprise Storage Plugins.
Visit https://support.huawei.com/enterprise/, enter eSDK Enterprise
Storage Plugins in the search box, and select the automatically
associated path to go to the Documentation page.
b. Query the version mapping between the storage system and eSDK
Enterprise Storage Plugins and download the mapping VASA software
package.
i. On the Documentation page, obtain and view the eSDK Enterprise
Storage Plugins Version Mapping of the corresponding version.
ii. On the Software Download page, download the VASA software
package that matches the storage version and model.
c. On the Documentation page, download the eSDK Enterprise Storage
Plugins User Guide (VASA 2.0) that matches the storage version and
model.
● Perform the following operations by following instructions in the user guide:
NOTE
GUIs may vary with software versions. The actual GUIs prevail.
5. Right-click the vCenter data center, choose New Virtual Machine > New
Virtual Machine, and select an appropriate VM storage policy and a VVol
datastore to create a VM.
----End
● Only the super administrator can use the batch configuration function.
● During batch configuration, CLI commands are used. You can obtain
command reference of the related product to learn how to effectively use
these commands.
1. Download the configuration file template provided by the storage system and
edit commands in the template as required.
2. If the project is planned and designed using LLDesigner, you can contact
Huawei engineers or Huawei certified resellers to provide the .conf
configuration file exported from LLDesigner.
Prerequisites
DeviceManager is properly communicating with the storage system.
Context
● The exported default configuration file template is named Example.conf.
● The configuration file template downloaded from DeviceManager is in the
ANSI encoding format.
Procedure
Step 1 In the upper right corner of the home page, choose > Batch Configure.
----End
Prerequisites
Only configuration files not being executed can be imported.
Context
● If a configuration file fails system check or is not executed during the import
process, only the administrator who imports the configuration file can import
a new configuration file.
● The latest imported configuration file will overwrite the earlier configuration
file.
● The configuration file to be imported cannot be larger than 100 KB.
Procedure
----End
Follow-up Procedure
After a configuration file is uploaded, the storage system automatically verifies the
commands in the configuration file.
● If the verification is passed, the system displays the message Configuration
file uploaded successfully. You can start the batch configuration.
● If the verification fails, the system displays an error message. You need to
modify the configuration file.
Prerequisites
A configuration file has been imported.
Context
● The offline configuration command can be executed only by the user who
imports the configuration file.
● If the user logs out during the command execution, the storage system
immediately stops the offline configuration.
● The storage system executes the commands included in the configuration file
one by one.
Procedure
Step 1 Click Execute to implement batch configuration.
When the progress reaches 100%, the operation is successful.
NOTE
During the execution, you can click Stop to stop the configuration.
----End
Procedure
Step 1 Choose Services > Network > FC Network.
Step 2 View information about the FC network in the function pane. Table 5-1 describes
the parameters.
ID ID of an FC port.
NOTE
Click the name of a port to view its details, including Summary, Initiators, and Owning
Port Groups.
----End
Procedure
Step 1 Choose Services > Network > FC Network.
Step 2 Click the name of the desired FC port. In the upper right corner of the page that is
displayed, click Modify.
Step 3 In Configured Rate (Gbit/s), select a data transmission rate for the FC port.
NOTICE
● The FC port must have the same rate and mode as the HBA port on the
application server to prevent a communication failure.
● When two storage systems are interconnected by FC ports, ensure that the
rates and modes of the FC ports are the same on the two storage systems.
Using different rates or modes may cause communication failure.
NOTE
● If the maximum rate of the port is 4 Gbit/s, you can set the value to 2 Gbit/s or 4 Gbit/s.
● If the maximum rate of the port is 8 Gbit/s, you can set the value to 2 Gbit/s, 4 Gbit/s,
or 8 Gbit/s.
● If the maximum rate of the port is 16 Gbit/s, you can set the value to 4 Gbit/s, 8 Gbit/s,
or 16 Gbit/s.
● If the maximum rate of the port is 32 Gbit/s, you can set the value to 8 Gbit/s, 16 Gbit/s,
or 32 Gbit/s.
● If the value is set to Self-adaptive, the interconnected FC ports negotiate the rate
automatically. If the negotiated rates do not match, modify the rate manually.
----End
Procedure
Step 1 Choose Services > Network > FC Network.
Step 3 Query the bit error statistics of the Fibre Channel ports.
NOTE
----End
Procedure
Step 1 Choose Services > Network > Ethernet Network > Ethernet Ports.
Step 2 View information about Ethernet ports in the function pane. Table 5-2 describes
the parameters.
Parameter Description
ID ID of an Ethernet port.
Parameter Description
Logical Type Logical type of an Ethernet port. Possible values are Front-
end port, Management port, Maintenance port,
Expansion port, Scale-out interconnect port, Container
front-end port, and Container back-end port.
NOTE
You can click the name of an Ethernet port to view its details.
----End
Procedure
Step 1 Choose Services > Network > Ethernet Network > Ethernet Ports.
----End
Prerequisites
● The health status of the storage system is normal.
● The host or switch supports and has enabled the LLDP.
Context
● The Link Layer Discovery Protocol (LLDP) is a standard Layer 2 topology
discovery protocol defined in IEEE 802.1ab. LLDP allows a device to send local
management information such as management IP address, device ID, and
port ID to neighbors. Neighbors save the received information in their
management information bases (MIBs). The network management system
(NMS) can search required information in MIBs to determine link status.
● If the host or switch connected to the front-end service port of the storage
system also supports the LLDP, the host or switch can discover the port
information of the storage system through the LLDP.
● For Ethernet ports on a 4 U device, only their owning controller sends LLDP
packets. In addition, the peer device only displays the neighbor information of
the owning controller. If the owning controller of the port is faulty, the port
does not send LLDP packets.
Precautions
Only storage systems of 6.1.3 and later versions support link discovery between
storage systems and switches through the LLDP.
Procedure
Step 1 In developer mode, run the change system lldp working_mode=? command to
change the LLDP working mode.
Example:
developer:/>change system lldp working_mode=lldp_mode_txrx
WARNING: You are about to change the LLDP working mode.
After the working mode of the LLDP protocol is changed, the host or switch may discover the array port
information through the LLDP protocol, and the host or switch information may also be discovered by the
array through the LLDP protocol.
Suggestion: Before performing this operation, ensure that you want to perform this operation.
Have you read warning message carefully?(y/n)y
Are you sure you really want to perform the operation?(y/n)y
Command executed successfully.
NOTE
Step 2 In developer mode, run the show system lldp command to check whether the
LLDP working mode is successfully changed.
Example:
developer:/>show system lldp
Working Mode : lldp_mode_txrx
----End
Procedure
Step 1 Choose Services > Network > Ethernet Network > Bond Ports.
Step 2 View information about bond ports in the function pane. Table 5-3 describes the
parameters.
Parameter Description
ID ID of a bond port.
NOTE
You can click the name of a bond port to view its details and modify it.
----End
Prerequisites
● A bond port has been created.
● After the MTU is changed to a non-default value, ensure that the MTU is the
same as that of the peer device (switch or network adapter).
Procedure
Step 1 Choose Services > Network > Ethernet Network > Bond Ports.
Step 2 Click More on the right of the desired bond port and select Modify.
The Modify page is displayed.
NOTE
Alternatively, click the name of the desired port. In the upper right corner of the page that
is displayed, select Modify from the Operation drop-down list.
Step 3 Set MTU (Bytes) of the bond port. The value ranges from 1280 to 9000.
Step 4 In Logical Port, specify Name, IP Address, and Subnet Mask/Prefix of a logical
port bonded to the bond port.
NOTE
----End
Prerequisites
● All services on the bond port to be deleted have been stopped.
● No VLAN or logical port is created for the bond port to be deleted.
Precautions
After a bond port is deleted, the IP addresses of the bonded Ethernet ports are
cleared. You must reset IP addresses for the Ethernet ports if needed.
Procedure
Step 1 Choose Services > Network > Ethernet Network > Bond Ports.
Step 2 Select one or more desired bond ports and click Delete.
NOTE
You can also click More on the right of a desired bond port and select Delete.
----End
Procedure
Step 1 Choose Services > Network > Ethernet Network > VLANs.
Step 2 View information about VLANs in the function pane. Table 5-4 describes the
parameters.
ID ID of a VLAN.
----End
Procedure
Step 1 Choose Services > Network > Ethernet Network > VLANs.
Step 2 Click More on the right of the desired VLAN and select Modify.
The Modify VLAN page is displayed.
Step 3 Set MTU (Bytes).
Step 4 Click OK.
----End
Prerequisites
All services in the VLAN to be deleted have been stopped.
Procedure
Step 1 Choose Services > Network > Ethernet Network > VLANs.
Step 2 Select one or more desired VLANs and click Delete.
NOTE
You can also click More on the right of a desired VLAN and select Delete.
----End
Procedure
Step 1 Choose Services > Network > Logical Ports.
Step 2 View information about logical ports in the function pane. Table 5-5 describes the
parameters.
ID ID of a logical port.
Parameter Description
NOTE
You can click the name of a logical port to view its details and manage it.
----End
Procedure
Step 1 Choose Services > Network > Logical Ports.
Step 2 Click More on the right of the desired logical port and select Modify.
Parameter Description
IP Address Type IP address type of the logical port, which can be IPv4 or
IPv6.
----End
Prerequisites
A logical port has been configured with an IP address.
Procedure
Step 1 Choose Services > Network > Logical Ports.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select the desired logical port and click Manage Route.
The Manage Route dialog box is displayed.
NOTE
Alternatively, perform either of the following operations to go to the Manage Route page:
● Click More on the right of the desired logical port and select Manage Route.
● Click the name of the desired logical port. In the upper right corner of the page that is
displayed, click Manage Route from the Operation drop-down list.
Subnet Subnet mask of the IPv4 address or prefix of the IPv6 address
Mask/ for the destination service network port on the application
Prefix server or destination logical port on another storage system.
----End
Procedure
Step 1 Choose Services > Network > Logical Ports.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select the desired logical port and click Fail Back.
NOTE
Alternatively, perform either of the following operations to fail back a logical port:
● Click More on the right of the desired logical port, and select Fail Back.
● Click the name of the desired logical port. In the upper right corner of the page that is
displayed, click Fail Back from the Operation drop-down list.
----End
Prerequisites
All services on the logical port to be deleted have been stopped.
Procedure
Step 1 Choose Services > Network > Logical Ports.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
Step 3 Select one or more desired logical ports and click Delete.
NOTE
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > RoCE Ports.
Step 2 View information about RoCE ports in the function pane. Table 5-8 describes the
parameters.
Parameter Description
ID ID of a RoCE port.
Parameter Description
NOTE
You can click the name of a port to view its details, including Summary, Initiators, Owning
Port Groups, and VLANs.
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > RoCE Ports.
Step 2 Click the name of the desired RoCE port. In the upper right corner of the page
that is displayed, click Modify.
The Modify page is displayed.
Step 3 In Working Mode, select a working mode for the RoCE port.
NOTE
Step 4 In MTU (Bytes), enter a maximum transmission unit (MTU) for the packets
transmitted between the RoCE port and the application server.
Step 5 Determine whether to enable SNSD. When SNSD of a RoCE port is set to
Enabled, hosts detect the state changes of all logical ports of the RoCE port and
determine whether to automatically establish or cancel connections based on
logical port states.
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > RoCE Ports.
Step 2 Select desired RoCE ports and click Batch Set SNSD. Then select Batch Enable
SNSD or Batch Disable SNSD.
NOTE
When SNSD of a RoCE port is set to Enabled, hosts detect the state changes of all logical
ports of the RoCE port and determine whether to automatically establish or cancel
connections based on logical port states.
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > RoCE Ports.
----End
Procedure
Step 1 Log in to DeviceManager of the local and remote devices.
Step 2 Choose Services > Network > RoCE Network > VLANs.
● The same VLAN IDs must be configured for the interconnected replication ports on the
local device, remote device, and switch.
● The VLAN ID ranges from 1 to 4094. You can specify multiple VLAN IDs one by one or in
a batch. When creating multiple VLANs and specifying VLAN IDs in a batch, the VLAN
IDs are in the following format: Start VLAN ID-End VLAN ID.
● To delete a VLAN ID, click next to it.
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > VLANs.
Step 2 View information about VLANs in the function pane. Table 5-9 describes the
parameters.
ID ID of a VLAN.
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > VLANs.
Step 2 Click More on the right of the desired VLAN and select Modify.
The Modify VLAN page is displayed.
Step 3 Set MTU (Bytes).
Step 4 Click OK.
----End
Prerequisites
All services in the VLAN to be deleted have been stopped.
Procedure
Step 1 Choose Services > Network > RoCE Network > VLANs.
You can also click More on the right of a desired VLAN and select Delete.
----End
NOTE
Some device models may not support some interface modules. For details, visit
Specifications Query.
Prerequisites
An Ethernet interface module has been properly installed on a controller.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
Alternatively, you can choose Services > Network > Ethernet Network > Ethernet Ports.
Step 5 View the Ethernet port information in the displayed Ethernet Port: Port location
page on the right or the table in the lower function pane.
IPv4 Address/ IPv4 address and subnet mask of the Ethernet port.
Subnet Mask
IPv6 Address/ IPv6 address and prefix length of the Ethernet port.
Prefix
Logical Type Logical type of the Ethernet port. Possible values are
Front-end port, Management port, Maintenance port,
Expansion port, Scale-out interconnect port, Container
front-end port, and Container back-end port.
Parameter Description
iSCSI Target Name Target name of the iSCSI network where the Ethernet port
resides.
NOTE
● Click the Initiators or Owning Port Groups tab to view the initiators or owning port
groups of the Ethernet port.
● If one or more bond ports have been created for the Ethernet port, you can click the
Bond Ports tab to view details of the bond ports.
----End
Precautions
● Change the IP address of an Ethernet port only when necessary. Before
changing the IP address of an Ethernet port, either ensure that redundant
connections are available or stop services carried by this port.
● The IP address of an Ethernet port must be on a different network segment
from the internal heartbeat IP addresses.
The default IP addresses of internal heartbeat on a dual-controller storage
system are 127.127.127.10 and 127.127.127.11, and those on a four-controller
storage system are 127.127.127.10, 127.127.127.11, 127.127.127.12, and
127.127.127.13.
● Internal heartbeat links are established between controllers for the controllers
to detect each other's working status. Heartbeat links do not require separate
cable connections. The internal heartbeat IP addresses have been assigned
before delivery and cannot be changed.
● The IP address of an Ethernet port must not be in the same network segment
as that of a management network port.
● The IP address of an Ethernet port must not be in the same network segment
as that of a maintenance network port. The default IP address of the
maintenance network port must fall within the 172.31.XXX.XXX segment.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
Alternatively, you can choose Services > Network > Ethernet Network > Ethernet
Ports and click the name of the desired Ethernet port. In the upper right corner of the
page that is displayed, click Modify.
2. In Working Mode, select a working mode for the Ethernet port.
NOTE
NOTE
----End
Context
Modifying the management port will interrupt the existing connection between
the storage system and the maintenance terminal.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired management port resides.
Alternatively, you can choose Services > Network > Ethernet Network > Ethernet
Ports and click the name of the desired management port. In the upper right corner
of the page that is displayed, click Modify.
2. Set the IPv4 address.
a. Set IPv4 Address for the management port.
b. Set Subnet Mask for the management port.
c. Set IPv4 Gateway for the management port.
3. Set the IPv6 address.
a. Set IPv6 Address for the management port.
b. Set Prefix for the management port.
c. Set IPv6 Gateway for the management port.
Step 6 Click OK.
Confirm your operation as prompted.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
NOTE
Alternatively, you can choose Services > Network > Ethernet Network > Ethernet Ports
and click Bit Error Statistics.
Step 6 Select Ethernet Port from the drop-down list in the upper-right corner.
Step 7 Query the bit error statistics in the port list.
NOTE
----End
Prerequisites
You have configured an IP address for an Ethernet port.
NOTE
If redundant links are configured, you must configure an IP address and routing information
for each involved Ethernet port.
Precautions
● The IP address of an Ethernet port must be on a different network segment
from the internal heartbeat IP addresses.
The default IP addresses of internal heartbeat on a dual-controller storage
system are 127.127.127.10 and 127.127.127.11, and those on a four-controller
storage system are 127.127.127.10, 127.127.127.11, 127.127.127.12, and
127.127.127.13.
● Internal heartbeat links are established between controllers for the controllers
to detect each other's working status. Heartbeat links do not require separate
cable connections. The internal heartbeat IP addresses have been assigned
before delivery and cannot be changed.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
NOTE
Alternatively, perform any of the following operations to go to the Manage Route page:
● Click Manage Logical Port. On the Manage Logical Port page that is displayed, select
the desired logical port and click Manage Route.
● Choose Services > Network > Logical Ports.
– Select the desired logical port and click Manage Route.
– Click More on the right of the desired logical port and select Manage Route.
Subnet Subnet mask of the IPv4 address or prefix of the IPv6 address
Mask/ for the destination service network port on the application
Prefix server or destination Ethernet port on another storage system.
----End
Prerequisites
● A bond port has been created.
● After the MTU is changed to a non-default value, ensure that the MTU is the
same as that of the peer device (switch or network adapter).
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
NOTE
Alternatively, you can choose Services > Network > Ethernet Network > Bond Ports. Click
More on the right of the desired bond port and select Modify.
Step 6 Set the MTU (Bytes) of the bond port. The value ranges from 1280 to 9000.
Step 7 In Logical Port, specify Name, IP Address, and Subnet Mask/Prefix of the logical
port.
NOTE
----End
Prerequisites
All services running on the Ethernet ports for which you want to cancel bonding
have been stopped. This is necessary because canceling Ethernet port bonding
interrupts ongoing services.
Precautions
After Ethernet port bonding is canceled, the IP addresses of the Ethernet ports are
cleared. You must reset IP addresses for the Ethernet ports if needed.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
----End
Prerequisites
VLANs cannot be created on the Ethernet ports that are configured with IP
addresses or carry services.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired Ethernet port resides.
NOTE
Alternatively, you can choose Services > Network > Ethernet Network > VLANs.
ID ID of a VLAN.
Parameter Description
▪ The VLAN ID ranges from 1 to 4094. You can specify multiple VLAN IDs one
by one or in a batch. When creating multiple VLANs and specifying VLAN IDs
in a batch, the VLAN IDs are in the following format: Start VLAN ID-End
VLAN ID.
The size of a packet transmitted between a port and a host cannot exceed the
MTU of the Ethernet port.
c. Click OK.
● To delete a VLAN:
Select the desired VLAN and click Delete.
Confirm your operation as prompted.
NOTE
You can also click More on the right of the desired VLAN and select Delete.
----End
Prerequisites
An RDMA interface module has been correctly installed on a controller.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired RDMA port resides.
Alternatively, you can choose Services > Network > Ethernet Network > Ethernet Ports.
In Logical Type, select Expansion port or Scale-out interconnect port to filter out desired
ports.
Step 5 View the RDMA port information on the page displayed on the right or in the
table in the lower function pane.
Table 5-13 describes the parameters.
Parameter Description
Logical Type Logical type of the RDMA port. Possible values include:
● Expansion port: connects a controller enclosure to a
smart disk enclosure.
● Scale-out interconnect port: connects controller
enclosures.
Parameter Description
Port State State of the RDMA port. A port will be disconnected after it
is disabled.
----End
Prerequisites
A SAS interface module has been correctly installed on a controller.
Procedure
Step 1 Choose System > Hardware > Devices.
Port State State of the SAS port. A port will be disconnected after it is
disabled.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 5 Select SAS Port from the drop-down list in the upper-right corner.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired FC port resides.
Step 5 View the FC port information on the page displayed on the right or in the table in
the lower function pane.
ID ID of the FC port.
Port State Isolation status of the FC port. Possible values are Enabled
and Disabled. If Port State is Disabled, this port cannot
be used.
NOTE
You can click the Initiators tab on the displayed page to view detailed initiator information.
----End
Context
Note the following when modifying the properties of an FC port:
● When a storage system uses an FC port to connect to an application server,
ensure that the rate of the FC port on the storage system is the same as that
of the HBA port on the application server. Using different rates may cause
communication failure between the storage system and application server.
● When two storage systems are interconnected by FC ports, ensure that the
rates of the FC ports are the same on the two storage systems. Using different
rates may cause communication failure.
● Do not modify the properties of an FC port when services are running because
modifying the properties will interrupt the communication on this port.
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired FC port resides.
Alternatively, you can choose Services > Network > FC Network and click the name
of the desired FC port. In the upper right corner of the page that is displayed, click
Modify.
2. In Configured Rate (Gbit/s), select a data transmission rate for the FC port.
NOTICE
– The FC port must have the same rate and mode as the HBA port on the
application server to prevent a communication failure.
– When two storage systems are interconnected by FC ports, ensure that the
rates and modes of the FC ports are the same on the two storage systems.
Using different rates or modes may cause communication failure.
– If the maximum rate of the port is 4 Gbit/s, you can set the value to 2 Gbit/s or 4
Gbit/s.
– If the maximum rate of the port is 8 Gbit/s, you can set the value to 2 Gbit/s, 4
Gbit/s, or 8 Gbit/s.
– If the maximum rate of the port is 16 Gbit/s, you can set the value to 4 Gbit/s, 8
Gbit/s, or 16 Gbit/s.
– If the maximum rate of the port is 32 Gbit/s, you can set the value to 8 Gbit/s, 16
Gbit/s, or 32 Gbit/s.
– If the value is set to Self-adaptive, the interconnected FC ports negotiate the rate
automatically. If the negotiated rates do not match, modify the rate manually.
3. In Port Protocol, select FC-SCSI or FC-NVMe.
4. Determine whether to enable Immediate Data. In scenarios where FC
replication links are used to transmit service data between storage arrays, the
Immediate Data function can improve the data transmission performance.
You are advised to enable this function.
Step 6 Click OK.
Confirm your operation as prompted.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired FC port resides.
NOTE
Alternatively, you can choose Services > Network > FC Network and click Bit Error
Statistics.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired RoCE port resides.
Alternatively, you can choose Services > Network > RoCE Network > RoCE Ports.
Step 5 View the RoCE port information on the page displayed on the right or in the table
in the lower function pane.
Parameter Description
Parameter Description
iSCSI Target Name Target name of the iSCSI network where the RoCE port
resides.
Port State State of the RoCE port. A RoCE port will be disconnected
after it is disabled.
Parameter Description
NOTE
On the page displayed on the right, you can view information about Initiators, Owning
Port Groups, and VLANs.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired RoCE port resides.
Alternatively, you can choose Services > Network > RoCE Network > RoCE Ports and
click the name of the desired RoCE port. In the upper right corner of the page that is
displayed, click Modify.
2. In Working Mode, select a working mode for the RoCE port.
NOTE
----End
Procedure
Step 1 Choose Services > Network > RoCE Network > RoCE Ports.
Step 2 Select desired RoCE ports and click Batch Set SNSD. Then select Batch Enable
SNSD or Batch Disable SNSD.
NOTE
When SNSD of a RoCE port is set to Enabled, hosts detect the state changes of all logical
ports of the RoCE port and determine whether to automatically establish or cancel
connections based on logical port states.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired RoCE port resides.
NOTE
Alternatively, you can choose Services > Network > RoCE Network > RoCE Ports and click
Bit Error Statistics.
Step 6 Select RoCE Port from the drop-down list in the upper-right corner.
----End
Procedure
Step 1 Choose System > Hardware > Devices.
Step 2 Click the controller enclosure where the desired RoCE port resides.
NOTE
Alternatively, you can choose Services > Network > RoCE Network > VLANs.
Parameter Description
ID ID of a VLAN.
▪ The VLAN ID ranges from 1 to 4094. You can specify multiple VLAN IDs one
by one or in a batch. When creating multiple VLANs and specifying VLAN IDs
in a batch, the VLAN IDs are in the following format: Start VLAN ID-End
VLAN ID.
d. Click OK.
● To modify a VLAN:
a. Click More on the right of the desired VLAN and click Modify.
The Modify VLAN page is displayed.
b. Set MTU (Bytes).
NOTE
The size of a packet transmitted between a port and a host cannot exceed the
MTU of the RoCE port.
c. Click OK.
● To delete a VLAN:
Select the desired VLAN and click Delete.
Confirm your operation as prompted.
NOTE
You can also click More on the right of the desired VLAN and select Delete.
----End
Procedure
Step 1 Choose System > Storage Pools.
Step 2 View the storage pool information in the function pane. Table 5-18 describes the
parameters.
Parameter Description
Parameter Description
Data Protection Total capacity of all LUNs and file systems for data
protection in a storage pool.
NOTE
For example, if snapshots are created for LUNs in the storage pool,
the space occupied by the activated snapshots is the data protection
capacity.
Data Reduction Total amount of user data written to the storage pool
divided by the storage pool's used capacity.
NOTE
This parameter is valid only when SmartDedupe and
SmartCompression licenses are imported to the storage system.
Data Reduction Total amount of block data written to the storage pool
Ratio for Block divided by the storage pool's used block capacity.
NOTE
This parameter is valid only when SmartDedupe and
SmartCompression licenses are imported to the storage system.
Data Reduction Total amount of file data written to the storage pool divided
Ratio for File by the storage pool's used file capacity.
NOTE
This parameter is valid only when SmartDedupe and
SmartCompression licenses are imported to the storage system and
the product model supports file systems.
Total Subscribed Total capacity of all LUNs and file systems in a storage pool.
NOTE
If the current device model does not support file systems, the total
subscribed capacity is the total capacity configured for all LUNs in a
storage pool.
Parameter Description
Used Subscribed Total amount of data that has been written to all LUNs and
file systems in a storage pool.
NOTE
If the current device model does not support file systems, the used
subscribed capacity is the total amount of data that has been written
to all LUNs in a storage pool.
Step 3 (Optional) Click the name of a storage pool to query its summary and disk
information.
----End
Procedure
Step 1 Choose System > Storage Pools.
Step 2 Click Set Space Reclamation Policy.
The Set Space Reclamation Policy dialog box is displayed on the right.
Step 3 Set the parameters of the space reclamation policy.
Table 5-19 describes the parameters.
Parameter Description
Start Time Time when the background space reclamation task starts.
End Time Time when the background space reclamation task ends.
----End
Precautions
Service performance may deteriorate during space reclamation.
Procedure
Step 1 Choose System > Storage Pools.
Step 2 Click More on the right of the desired storage pool and select Reclaim Space.
NOTE
Alternatively, click the name of the desired storage pool. In the upper right corner of the
page that is displayed, select Reclaim Space from the Operation drop-down list.
----End
Procedure
Step 1 Choose System > Storage Pools.
Step 2 Click More on the right of the desired storage pool and select Stop Reclaiming
Space.
NOTE
Alternatively, click the name of the desired storage pool. In the upper right corner of the
page that is displayed, select Stop Reclaiming Space from the Operation drop-down list.
----End
Procedure
Step 1 Choose System > Storage Pools.
Step 2 Click More on the right of the desired storage pool and choose Export Disk
Configuration.
The Export Disk Configuration dialog box is displayed.
NOTE
Alternatively, click the name of the desired storage pool. In the upper right corner of the
page that is displayed, select Export Disk Configuration from the Operation drop-down
list.
----End
Procedure
Step 1 Choose System > Storage Pools.
Step 2 Click More on the right of the desired storage pool and choose Modify.
The Modify Storage Pool page is displayed on the right.
NOTE
Alternatively, click the name of the desired storage pool. In the upper right corner of the
page that is displayed, select Modify from the Operation drop-down list.
Parameter Description
Prerequisites
● LUNs and file systems in the storage pool have been deleted.
● If the storage pool stores historical monitoring data, Retain historical
monitoring data has been deselected and historical monitoring data has
been deleted from the storage pool.
NOTICE
NOTE
Procedure
Step 1 Choose System > Storage Pools.
Step 2 Click More on the right of the desired storage pool and choose Delete.
NOTE
Alternatively, click the name of the desired storage pool. In the upper right corner of the
page that is displayed, select Delete from the Operation drop-down list.
NOTICE
Parameter Description
Data Erasure Standard for overwriting disk data. Possible options are
Standard DoD 5220.22-M (E), DoD 5220.22-M (ECE), VSITR, and
Custom. This parameter is available only when Data
Erasure Mechanism is set to overwrite.
NOTE
When Data Erasure Standard is set to Custom, the system will
overwrite disk data according to Pattern Value and
Overwrites specified by users.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View the LUN information in the function pane. Table 5-22 describes the
parameters.
Parameter Description
ID ID of a LUN.
Parameter Description
Used Ratio of the used capacity (that is, the allocated capacity)
to the total capacity of a LUN.
Use Type Usage type of the LUN. The possible values are as follows:
● Internal: common LUN created in a local storage
system.
● External: external device LUN (eDevLUN) created for
taking over a LUN from an external storage system.
Takeover LUN WWN of the external LUN after takeover, that is, the
WWN eDevLUN WWN.
Step 4 (Optional) Click the name of a LUN to query its summary, topology, mapping, and
protection features.
NOTE
● If a LUN has been added to multiple LUN groups, click the Summary tab on the details
page, and click More on the right of Owning LUN Groups. On the Owning LUN
Groups page that is displayed, view the names and IDs of the owning LUN groups.
● On the Topology tab page, if the number of ports in a port group is greater than 3, you
can click to view details about all ports. When Port Type is Physical port, the
parameters are described in Table 5-23. When Port Type is Logical port, the
parameters are described in Table 5-24.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
Alternatively, perform either of the following operations to go to the Map LUN page:
● Click More on the right of the desired LUN and select Map.
● Click the name of the desired LUN. In the upper right corner of the page that is
displayed, select Map from the Operation drop-down list.
Step 4 Click on the right of Selected LUNs. In the Available LUNs list, select the
desired LUNs and add them to Selected LUNs.
NOTE
You can click Create to create a host on the Create Host page that is displayed.
Step 6 Select a port group from the Port Group drop-down list.
NOTE
You can click Create to create a port group on the Create Port Group page that is
displayed.
Step 7 Select Advanced in the upper right corner and set how to assign host LUN IDs.
● Automatic: The system assigns a host LUN ID to each LUN mapped to a host.
● Start ID: Set a start ID ranging from 0 to 4095. The system assigns a host
LUN ID to each LUN mapped to a host, starting from Start ID.
● Specified ID: Manually assign a host LUN ID to each LUN mapped to a host.
Step 8 If HyperMetro pairs have been created for the LUNs, determine whether to select
Same Host LUN ID. If you select it, the system forcibly ensures that the host LUN
IDs of the local and remote LUNs in the same HyperMetro pairs are the same. In
SAN-based HyperMetro scenarios involving ESX hosts, if the host LUN IDs of the
local and remote LUNs in the same HyperMetro pairs are different, data may be
inconsistent.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the LUN and choose Unmap.
The Unmap LUN page is displayed on the right.
NOTE
Alternatively, perform either of the following operations to go to the Unmap LUN page:
● Click the name of the desired LUN. In the upper right corner of the page that is
displayed, select Unmap from the Operation drop-down list.
● Click the name of the desired LUN. On the page that is displayed, click the Mapping tab
page, then click More on the right of the host, and select Unmap.
Skip this step if you unmap a LUN from the Mapping tab page.
----End
Configuration Guide
For details, see the specific data protection feature guide. For example, to create
snapshots for LUNs, refer to the HyperSnap feature guide for block specific to your
product model and version.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired LUN. On the page that is displayed, click the
Mapping tab.
Step 4 Select the desired host and click Add Port Group.
NOTE
Alternatively, choose Services > Block Service > VVol > PE LUNs and click the name of the
desired PE LUN. On the page that is displayed, click the Mapping tab, select the desired
host or host group, and click Add Port Group.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired LUN. On the page that is displayed, click the
Mapping tab.
Step 4 Select the desired host and click Remove Port Group.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the LUN and choose Modify.
NOTE
Alternatively, click the name of the desired LUN. In the upper right corner of the page that
is displayed, select Modify from the Operation drop-down list.
Parameter Description
----End
Context
● If the recycle bin is enabled when you delete a LUN, the LUN is moved to the
recycle bin. Data on the LUN will be deleted when the retention period
elapses. You can restore the LUN in the recycle bin.
● If the recycle bin is disabled when you delete a LUN, the data on the LUN is
deleted immediately.
Prerequisites
● The LUN to be deleted is not mapped.
● The child objects of the LUN to be deleted have been deleted or moved to the
recycle bin.
Precautions
Before deleting a LUN, verify that the data on it is of no use or has been backed
up.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > Recycle Bin.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View the LUN information in the function pane. Table 5-26 describes the
parameters.
ID ID of a LUN.
Child Objects Number of child objects in a LUN, that is, the number of
snapshots and cascading snapshots created using the LUN
as the source object.
Step 4 (Optional) Click the name of a LUN to view its summary and child objects.
NOTE
On the Child Objects tab page, you can delete child objects of a LUN.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > Recycle Bin.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 4 After the LUN is moved to the recycle bin, the name of the newly created LUN can
be the same as that of the LUN in the recycle bin. To prevent duplicate names
after restoration, you need to set the name of the restored LUN.
NOTE
After LUNs are restored, you can choose Services > Block Service > LUN Groups > LUNs to
manage them.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > Recycle Bin.
NOTE
● The configuration of the recycle bin takes effect for all vStores.
● Only 6.1.3 and later versions support multiple vStores.
After the recycle bin is disabled, the LUNs in the recycle bin will not be deleted. You
can manually delete them.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > Recycle Bin.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View the LUN group information in the function pane. Table 5-27 describes the
parameters.
Parameter Description
Parameter Description
Step 4 (Optional) Click the name of a LUN group to query its summary, member LUNs,
topology, mapping, and protection features.
NOTE
● On the Topology tab page, if the number of ports in a port group is greater than 3, you
can click to view details about all ports. When Port Type is Physical port, the
parameters are described in Table 5-28. When Port Type is Logical port, the
parameters are described in Table 5-29.
● On the Topology tab page, if the number of hosts in a host group is greater than 3, you
can click to view details about all hosts. Table 5-30 describes the parameters.
Parameter Description
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired LUN group. On the page that is displayed, click the
Mapping tab.
Step 4 Select the desired host or host group and click Add Port Group.
The Add Port Group page is displayed on the right.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired LUN group. On the page that is displayed, click the
Mapping tab.
Step 4 Select the desired host or host group and click Remove Port Group.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
Alternatively, perform either of the following operations to go to the Map LUN Group
page:
● Click More on the right of the desired LUN group and choose Map.
● Click the name of the desired LUN group. In the upper right corner of the page that is
displayed, select Map from the Operation drop-down list.
If no host or host group exists in the system, click Create to create one.
Step 7 Select Advanced in the upper right corner and determine whether to select Same
Host LUN ID. If you select it, the system forcibly ensures that the host LUN IDs of
the local and remote LUNs in the same HyperMetro pairs are the same. In SAN-
based HyperMetro scenarios involving ESX hosts, if the host LUN IDs of the local
and remote LUNs in the same HyperMetro pairs are different, data may be
inconsistent.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the LUN group and choose Unmap.
NOTE
Alternatively, perform either of the following operations to go to the Unmap LUN Group
page:
● Click the name of the desired LUN group. In the upper right corner of the page that is
displayed, select Unmap from the Operation drop-down list.
● Click the name of the desired LUN group. On the page that is displayed, click the
Mapping tab page, then click More on the right of the host or host group, and select
Unmap.
Skip this step if you unmap a LUN group from the Mapping tab page.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired LUN group and choose Add LUN.
NOTE
Alternatively, perform any of the following operations to go to the Add LUN page:
● Click the name of the desired LUN group. In the upper right corner of the page that is
displayed, select Add LUN from the Operation drop-down list.
● Click the name of the desired LUN group. On the page that is displayed, click the
Member LUNs tab page, and then click Add.
● Click the value in the LUNs column of the desired LUN group if the value is not 0. On
the Member LUNs tab page, click Add.
Step 4 Select one or more LUNs from Available LUNs to add them to Selected LUNs.
Step 5 If the LUN group has been mapped, select Advanced in the upper right corner and
set how to assign host LUN IDs.
● Automatic: The system assigns a host LUN ID to each LUN mapped to a host.
● Start ID: Set a start ID ranging from 0 to 4095. The system assigns a host
LUN ID to each LUN mapped to a host, starting from Start ID.
● Specified ID: Manually assign a host LUN ID to each LUN mapped to a host.
Step 6 If the LUN group has been mapped, determine whether to select Same Host LUN
ID. If you select it, the system forcibly ensures that the host LUN IDs of the local
and remote LUNs in the same HyperMetro pairs are the same. In SAN-based
HyperMetro scenarios involving ESX hosts, if the host LUN IDs of the local and
remote LUNs in the same HyperMetro pairs are different, data may be
inconsistent.
Step 7 If remote replication, HyperMetro, or DR Star is configured for the LUN group, add
LUNs by referring to the feature guide of the corresponding version and model.
Step 8 Click OK.
Confirm your operation as prompted.
NOTE
After the task is created successfully, the Execution Result page is displayed. You can view
details about the current task on this page.
----End
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired LUN group and choose Remove LUN.
The Remove LUN page is displayed on the right.
NOTE
Step 4 Select one or more LUNs from Available LUNs to add them to Selected LUNs.
NOTE
● Skip this step if you remove LUNs from the Member LUNs tab page.
● If a HyperMetro or remote replication consistency group (CG) has been created for the
LUN group, the related HyperMetro or remote replication pair will be removed from the
CG after you remove a LUN.
● If a DR Star trio has been created for the LUN group, when you remove a LUN from the
LUN group, the HyperMetro pair and two remote replication pairs corresponding to the
LUN are removed from the HyperMetro CG and two remote replication CGs that form
the DR Star trio.
NOTE
If a HyperMetro or remote replication CG or DR Star trio has been created for the LUN
group, after the task is created successfully, the Execution Result page is displayed. You can
view details about the current task on this page.
----End
Configuration Guide
For details, see the specific data protection feature guide. For example, to create
snapshots for a LUN group, refer to the HyperSnap feature guide for block specific
to your product model and version.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired LUN group and choose Modify.
NOTE
Alternatively, click the name of the desired LUN group. In the upper right corner of the
page that is displayed, select Modify from the Operation drop-down list.
Prerequisites
The LUN group to be deleted has not been mapped.
Procedure
Step 1 Choose Services > Block Service > LUN Groups > LUN Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired LUN group and choose Delete.
NOTE
Alternatively, click the name of the desired LUN group. In the upper right corner of the
page that is displayed, select Delete from the Operation drop-down list.
Context
PE LUNs are only used by virtual volumes (VVols) in VMware software-defined
storage. VVols provide storage space for VMs. A PE LUN is used as an I/O
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
The screenshot is for reference only and the actual GUI may vary.
Parameter Description
Parameter Description
Start Start number from which the system incrementally adds a suffix
Number number to the name of each PE LUN for distinction.
[Value range]
0 to (10000 – Number of PE LUNs created in a batch)
NOTE
● This parameter is displayed only when Quantity is greater than 1 and
Advanced is selected.
● For example, if you want to create 300 PE LUNs, the value range of
Start Number is 0 to 9700.
LUN Group After selecting Add to LUN Group, you must choose a LUN
group.
NOTE
You can click Create to create a LUN group.
Map To Specifies the host or host group to which the LUN group is
mapped.
NOTE
You can click Create to create a host or host group.
Port Group Port group you want to use for the mapping.
NOTE
● This option is displayed after you have selected a host or host group.
● If no port group exists in the system, click Create.
Parameter Description
NOTE
The Description, Start Number, and Host LUN ID are hidden parameters. You can click
Advanced to display them.
----End
Context
● On the PE LUN management page, click to refresh PE LUN information.
● On the PE LUN management page, click and select the PE LUN parameters
you want to view.
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View the PE LUN information in the function pane. Table 5-32 describes the
parameters.
Parameter Description
ID ID of the PE LUN.
Step 4 (Optional) Click the name of a PE LUN to view its Summary, Topology, and
Mapping.
NOTE
● If a PE LUN has been added to multiple LUN groups, click the Summary tab on the
details page, and click More on the right of Owning LUN Groups. On the Owning LUN
Groups page that is displayed, view the names and IDs of the owning LUN groups.
● On the Topology tab page, if the number of ports in a port group is greater than 3, you
can click to view details about all ports. When Port Type is Physical port, the
parameters are described in Table 5-33. When Port Type is Logical port, the
parameters are described in Table 5-34.
Parameter Description
Parameter Description
----End
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired PE LUN and choose Modify.
The Modify PE LUN page is displayed on the right.
NOTE
Alternatively, click the name of the desired PE LUN. In the upper right corner of the page
that is displayed, select Modify from the Operation drop-down list.
----End
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired PE LUN. On the page that is displayed, click the
Mapping tab.
Step 4 Select the desired host or host group and click Add Port Group.
The Add Port Group page is displayed on the right.
Step 5 Select a port group.
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired PE LUN. On the page that is displayed, click the
Mapping tab.
Step 4 Select the desired host or host group and click Remove Port Group.
----End
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click the name of the desired PE LUN. On the page that is displayed, click the
Mapping tab.
Step 4 Click More on the right of the desired host or host group and choose Modify Host
LUN ID.
Step 5 Set Host LUN ID. The value ranges from 0 to 4095.
----End
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
Alternatively, perform any of the following operations to go to the Map PE LUN page:
● Click More on the right of the desired PE LUN and select Map.
● Click the name of the desired PE LUN. In the upper right corner of the page that is
displayed, select Map from the Operation drop-down list.
Step 4 Select the PE LUNs you want to map. Click on the right of Selected LUNs. In
the Available LUNs list, select the desired LUNs and add them to Selected LUNs.
NOTE
Step 7 Select Advanced in the upper right corner and set how to assign host LUN IDs.
● Automatic
A host LUN ID is allocated by the storage system to a LUN mapped to a host.
If you select Automatic, the system automatically allocates a unique host
LUN ID to each LUN.
● Start ID
The system automatically allocates a unique host LUN ID to each LUN,
starting from Start ID.
----End
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired PE LUN and choose Unmap.
NOTE
Alternatively, perform either of the following operations to go to the Unmap PE LUN page:
● Click the name of the desired PE LUN. In the upper right corner of the page that is
displayed, select Unmap from the Operation drop-down list.
● Click the name of the desired PE LUN. On the page that is displayed, click the Mapping
tab page, then click More on the right of the host, and select Unmap.
This step is not needed if you unmap a PE LUN from the Mapping tab page.
----End
Prerequisites
The PE LUN you want to delete has not been mapped.
Precautions
Before deleting a PE LUN, confirm that its data is of no use or has been backed
up.
Procedure
Step 1 Choose Services > Block Service > VVol > PE LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
NOTE
----End
Context
● On the VVol LUN management page, click to refresh VVol LUN
information.
● On the VVol LUN management page, click and select the VVol LUN
parameters you want to view.
Procedure
Step 1 Choose Services > Block Service > VVol > VVol LUNs.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View the VVol LUN information in the function pane. Table 5-35 describes the
parameters.
Parameter Description
Owning vStore Name of the vStore to which the VVol LUN belongs.
NOTE
This parameter is available only when vStore is set to All vStores in
Step 2.
Parameter Description
Function Type Function type of a VVol LUN. Possible values are LUN and
Snapshot.
Use Type Usage type of the LUN. The value is VVol LUNs, indicating
that the LUN provides storage space for VMware VMs.
Step 4 (Optional) Click the name of a VVol LUN to view its summary and protection
information.
NOTE
The snapshots, remote replication pairs, and HyperCDP objects of VVol LUNs can only be
viewed, but cannot be configured and managed on DeviceManager.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, view the host information in the function pane. Table
5-36 describes the parameters.
Parameter Description
ID ID of the host.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click the name of the desired host. Click the Path Details
tab.
Step 4 View path details. Table 5-37 describes the related parameters.
Parameter Description
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click the name of the desired host. On the page that is
displayed, click the Mapping tab page.
Step 4 Click View Host LUN ID.
The View Host LUN ID page is displayed on the right.
Step 5 View the LUNs mapped to the host and their host LUN IDs.
----End
Prerequisites
Host services on the LUN have been stopped, and the virtual disk created by
multipathing software and physical disk corresponding to the LUN have been
uninstalled from the host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click the name of the desired host. On the page that is
displayed, click the Mapping tab.
Step 4 Click More on the right of the desired LUN or LUN group and choose Modify Host
LUN ID.
The Modify Host LUN ID page is displayed on the right.
NOTE
Alternatively, perform either of the following operations to go to the Modify Host LUN ID
page:
● On the Mapping tab page, click View Host LUN ID. On the View Host LUN ID page
that is displayed, click Modify in the upper right corner.
● Choose Services > Block Service > LUN Groups > LUNs and click the name of the
desired LUN. On the page that is displayed, click the Mapping tab, then click More on
the right of the host, and choose Modify Host LUN ID.
● Choose Services > Block Service > LUN Groups > LUN Groups and click the name of
the desired LUN group. On the page that is displayed, click the Mapping tab, then click
More on the right of the host or host group, and choose Modify Host LUN ID.
Step 5 Set the host LUN ID for each LUN. The value ranges from 0 to 4095.
Step 6 If HyperMetro pairs have been created for the LUNs or a LUN group is selected,
select Advanced in the upper right corner and determine whether to select Same
Host LUN ID. If you select it, the system checks whether the host LUN IDs of the
local and remote LUNs in the same HyperMetro pairs are the same when you
change the host LUN IDs. In SAN-based HyperMetro scenarios involving ESX hosts,
if the host LUN IDs of the local and remote LUNs in the same HyperMetro pairs
are different, data may be inconsistent.
----End
Follow-up Procedure
After a host LUN ID is modified, re-scan for disks on the host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click the name of the desired host. On the page that is
displayed, click the Mapping tab page.
Step 4 Select the desired LUN group and click Add Port Group.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click the name of the desired host. On the page that is
displayed, click the Mapping tab page.
Step 4 Select the desired LUN group and click Remove Port Group.
Confirm your operation as prompted.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, select the desired host and choose Map > Map LUN
Group.
The Map LUN Group page is displayed on the right.
NOTE
Alternatively, perform either of the following operations to go to the Map LUN Group
page:
● Click More on the right of the desired host and choose Map LUN Group.
● Click the name of the desired host. In the upper right corner of the page that is
displayed, select Map LUN Group from the Operation drop-down list.
The following preset application types are provided for typical applications:
Default, Oracle_OLAP, Oracle_OLTP, Oracle_OLAP&OLTP, SQL_Server_OLAP,
SQL_Server_OLTP, SQL_Server_OLAP&OLTP, SAP_HANA, Vmware_VDI, Hyper-
V_VDI, Others, and FusionAccess_VDI
▪ The preset application types specify the application request sizes. When
SmartCompression and SmartDedupe licenses are imported to the system, the
preset application types also display whether SmartCompression and
SmartDedupe are enabled. For details, see SmartDedupe and
SmartCompression Feature Guide for Block of the desired product model and
version.
▪ After you have set an application type for a LUN, you are unable to change it
in follow-up operations.
▪ If the application type configured for a LUN does not match the actual I/O
model, the LUN performance may deteriorate.
▪ If none of the preset application types matches the actual I/O model, you can
run the create lun_workload_type general command to create one. For
details on this command, refer to the Command Reference.
Name Prefix Name prefix of the LUN. The names of the new LUNs
are numbered in sequence based on the name prefix.
Parameter Description
d. (Optional) When creating LUNs in a batch, click and set the suffixes of
the LUNs. Related parameters include Suffix Digits and Suffix (start
number of the suffixes). The system adds a suffix to the end of each LUN
name in ascending order based on the specified start suffix number.
NOTE
▪ For example, if you want to create 300 LUNs, the value range of Suffix is 0 to
9700.
You can select Include mapped LUN groups to query the LUN groups that have been
mapped to the current host. For these LUN groups, mapping cannot be created
repeatedly.
hosts, if the host LUN IDs of the local and remote LUNs in the same HyperMetro
pairs are different, data may be inconsistent.
Step 8 Click OK.
Confirm your operation as prompted.
NOTE
After the task is created successfully, the Execution Result page is displayed. You can view
details about the current task on this page.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, select the desired host and choose Map > Map LUN.
The Map LUN page is displayed on the right.
NOTE
Alternatively, perform either of the following operations to go to the Map LUN page:
● Click More on the right of the desired host and choose Map LUN.
● Click the name of the desired host. In the upper right corner of the page that is
displayed, select Map LUN from the Operation drop-down list.
Parameter Description
▪ After you have set an application type for a LUN, you are
unable to change it in follow-up operations.
You can select Include mapped LUNs to query the LUNs that have been mapped to
the current host. For these LUNs, mapping cannot be created repeatedly.
Step 7 If HyperMetro pairs have been created for the selected LUNs, select Advanced in
the upper right corner and determine whether to select Same Host LUN ID. If you
select it, the system forcibly ensures that the host LUN IDs of the local and remote
LUNs in the same HyperMetro pairs are the same. In SAN-based HyperMetro
scenarios involving ESX hosts, if the host LUN IDs of the local and remote LUNs in
the same HyperMetro pairs are different, data may be inconsistent.
NOTE
After the task is created successfully, the Execution Result page is displayed. You can view
details about the current task on this page.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click More on the right of the desired host and choose
Unmap.
NOTE
Alternatively, perform either of the following operations to go to the Unmap Object page:
● Click the name of the desired host. In the upper right corner of the page that is
displayed, select Unmap from the Operation drop-down list.
● Click the name of the desired host. On the page that is displayed, click the Mapping tab
page, then click More on the right of the LUN or LUN group, and select Unmap.
Skip this step if you cancel the mapping between a host and LUNs or a LUN group from the
Mapping tab page.
----End
Prerequisites
The host scanning function has been enabled on the Block Service page (Settings
> Block Service).
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click More on the right of the desired host and choose
Add Initiator.
NOTE
Alternatively, perform either of the following operations to go to the Add Initiator page:
● Click the name of the desired host. In the upper right corner of the page that is
displayed, select Add Initiator from the Operation drop-down list.
● Click the name of the desired host. On the page that is displayed, click the Initiators tab
page, and then click Add.
Step 5 (Optional) Click Create Initiator. On the Create Initiator page that is displayed,
set the related parameters.
NOTE
Parameter Description
Parameter Description
Parameter Description
Normal The normal session is the process during which the target
Authentication and initiator transmit data between each other after
connections have been set up. Authentication modes include:
● No authentication
● Unidirectional authentication
The target authenticates the initiator.
● Bidirectional authentication
The target and initiator authenticate each other.
Discovery The discovery session is the process during which the target
Authentication and initiator are setting up connections. Authentication
modes include:
● No authentication
● Unidirectional authentication
The target authenticates the initiator.
● Bidirectional authentication
The target and initiator authenticate each other.
NOTE
When Normal Authentication or Discovery Authentication is set to
Bidirectional authentication, you need to specify the CHAP Name
and Password, and confirm the password in both the Target
Authenticates Initiator and Initiator Authenticates Target areas.
NOTE
After you click OK, the new initiator is automatically added to the list on the right.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click the name of the desired host.
The host details page is displayed.
Step 4 Click the Initiators tab page.
Step 5 Click More on the right of the desired initiator and choose Modify.
The Modify Initiator page is displayed on the right.
Step 6 (Optional) Set an alias for the initiator.
Step 7 Click OK.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click More on the right of the desired host and choose
Remove Initiator.
The Remove Initiator page is displayed on the right.
NOTE
NOTE
Skip this step if you remove initiators from the Initiators tab page.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, click More on the right of the desired host and choose
Modify.
NOTE
Alternatively, click the name of the desired host. In the upper right corner of the page that
is displayed, select Modify from the Operation drop-down list.
After the vStore to which the host belongs is modified, the vStore to which the
initiator of the host belongs changes accordingly.
3. (Optional) Modify the Description of the host.
4. Modify the OS of the host.
5. (Optional) Modify the IP Address of the host.
6. (Optional) Modify the Location of the host.
7. Select a Host Access Mode. The possible values are Load balancing and
Asymmetric.
NOTE
The host access mode indicates that a host accesses local and remote storage systems
in a HyperMetro pair.
– Load balancing: Hosts access local and remote devices with equal priority.
– Asymmetric: Hosts preferentially access the specified device.
If a LUN has been mapped to a host, restart the host for the modification to take
effect after you modify the host access mode. You do not need to restart the system
when configuring the mapping for the first time.
For details about how to configure the host access mode in different operating
systems, see the corresponding Host Connectivity Guide.
8. When Host Access Mode is Asymmetric, set Preferred Path for
HyperMetro.
----End
Prerequisites
The host to be deleted is not a member of any host group.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Hosts.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Hosts tab page, select the desired host and click Delete.
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Initiators.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Initiators tab page, select an initiator type and click Create.
● iSCSI initiator
Table 5-43 describes the parameters.
Parameter Description
Parameter Description
▪ Uppercase letters
▪ Lowercase letters
▪ Digits
NOTE
If you choose Bidirectional authentication, you must configure the CHAP name and
password for Target Authenticates Initiator and Initiator Authenticates Target.
● NVMe over RoCE initiator
Table 5-45 describes the parameters.
Parameter Description
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Initiators.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Initiators tab page, select an initiator type. In the function pane, view
information about initiators. Table 5-46 describes the parameters.
Parameter Description
Parameter Description
Associated with Indicates whether the initiator has been associated with a
Host host.
Associated Host Name of the host with which the initiator is associated.
Name
Associated Host IP address of the host with which the initiator is associated.
IP Address NOTE
This parameter is displayed only when the initiator type is iSCSI or
NVMe over RoCE.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Initiators.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 4 Click More on the right of the desired initiator and select Modify.
If an initiator has been added to a host, the owning vStore of the initiator can be
modified only on the host.
b. Set an alias for an FC initiator.
NOTE
▪ The name can contain only letters, digits, underscores (_), hyphens (-), and
periods (.).
● iSCSI initiator
Table 5-47 describes the parameters.
Parameter Description
▪ Uppercase letters
▪ Lowercase letters
▪ Digits
NOTE
If you choose Bidirectional authentication, you must configure the CHAP name and
password for Target Authenticates Initiator and Initiator Authenticates Target.
● NVMe over RoCE initiator
a. Select the vStore to which the initiator belongs from the Owning vStore
drop-down list.
NOTE
If an initiator has been added to a host, the owning vStore of the initiator can be
modified only on the host.
b. Set an alias for the NVMe over RoCE initiator.
NOTE
▪ The value can contain only letters, digits, underscores (_), hyphens (-), and
periods (.).
----End
Prerequisites
● An FC initiator whose owning vStore is the same as that of the created host
or whose owning vStore is -- can be added to the host.
● For iSCSI and NVMe over RoCE initiators, you can only add initiators whose
owning vStore is the same as that of the created host to the host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Initiators.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Alternatively, click More on the right of the initiator and select Associate with Host.
----End
Precautions
Removing an initiator will interrupt services on the host. Stop host services before
performing this operation.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Initiators.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Alternatively, click More on the right of the initiator and select Dissociate from Host.
----End
Prerequisites
● Status of the initiator is Offline.
● The initiator is not associated with any host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Initiators.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Alternatively, click More on the right of the initiator and select Delete to delete the desired
initiator.
----End
Prerequisites
At least one host group has been created.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, view the host group information in the function
pane. Table 5-48 describes the parameters.
Parameter Description
Step 4 (Optional) Click the name of the host group to query its summary, member hosts,
and mapping.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click the name of the desired host group. On the
page that is displayed, click the Mapping tab page.
Step 5 View the LUNs mapped to hosts in the host group and their host LUN IDs.
----End
Prerequisites
Host services on the LUN have been stopped, and the virtual disk created by
multipathing software and physical disk corresponding to the LUN have been
uninstalled from the host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click the name of the desired host group. On the
page that is displayed, click the Mapping tab.
Step 4 Click More on the right of the desired LUN or LUN group and choose Modify Host
LUN ID.
NOTE
Alternatively, perform either of the following operations to go to the Modify Host LUN ID
page:
● On the Mapping tab page, click View Host LUN ID. On the View Host LUN ID page
that is displayed, click Modify in the upper right corner.
● Choose Services > Block Service > LUN Groups > LUN Groups and click the name of
the desired LUN group. On the page that is displayed, click the Mapping tab, then click
More on the right of the host or host group, and choose Modify Host LUN ID.
Step 5 Set the host LUN ID for each LUN. The value ranges from 0 to 4095.
Step 6 Select Advanced in the upper right corner and determine whether to select Same
Host LUN ID. If you select it, the system checks whether the host LUN IDs of the
local and remote LUNs in the same HyperMetro pairs are the same when you
change the host LUN IDs. In SAN-based HyperMetro scenarios involving ESX hosts,
if the host LUN IDs of the local and remote LUNs in the same HyperMetro pairs
are different, data may be inconsistent.
----End
Follow-up Procedure
After a host LUN ID is modified, re-scan for disks on the host.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click the name of the desired host group. On the
page that is displayed, click the Mapping tab page.
Step 4 Select the desired LUN group and click Add Port Group.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click the name of the desired host group. On the
page that is displayed, click the Mapping tab page.
Step 4 Select the desired LUN group and click Remove Port Group.
Confirm your operation as prompted.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, choose Map > Map LUN Group.
The Map LUN Group page is displayed on the right.
NOTE
Alternatively, perform either of the following operations to go to the Map LUN Group
page:
● Click More on the right of the desired host group and choose Map LUN Group.
● Click the name of the desired host group. In the upper right corner of the page that is
displayed, select Map LUN Group from the Operation drop-down list.
NOTE
The following preset application types are provided for typical applications:
Default, Oracle_OLAP, Oracle_OLTP, Oracle_OLAP&OLTP, SQL_Server_OLAP,
SQL_Server_OLTP, SQL_Server_OLAP&OLTP, SAP_HANA, Vmware_VDI, Hyper-
V_VDI, Others, and FusionAccess_VDI
▪ The preset application types specify the application request sizes. When
SmartCompression and SmartDedupe licenses are imported to the system, the
preset application types also display whether SmartCompression and
SmartDedupe are enabled. For details, see SmartDedupe and
SmartCompression Feature Guide for Block of the desired product model and
version.
▪ After you have set an application type for a LUN, you are unable to change it
in follow-up operations.
▪ If the application type configured for a LUN does not match the actual I/O
model, the LUN performance may deteriorate.
▪ If none of the preset application types matches the actual I/O model, you can
run the create lun_workload_type general command to create one. For
details on this command, refer to the Command Reference.
Name Prefix Name prefix of the LUN. The names of the new LUNs
are numbered in sequence based on the name prefix.
Parameter Description
d. (Optional) When creating LUNs in a batch, click and set the suffixes of
the LUNs. Related parameters include Suffix Digits and Suffix (start
number of the suffixes). The system adds a suffix to the end of each LUN
name in ascending order based on the specified start suffix number.
NOTE
▪ For example, if you want to create 300 LUNs, the value range of Suffix is 0 to
9700.
You can select Include mapped LUN groups to query the LUN groups that have been
mapped to the current host group. For these LUN groups, mapping cannot be created
repeatedly.
hosts, if the host LUN IDs of the local and remote LUNs in the same HyperMetro
pairs are different, data may be inconsistent.
NOTE
After the task is created successfully, the Execution Result page is displayed. You can view
details about the current task on this page.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click More on the right of the desired host group
and choose Unmap.
NOTE
Alternatively, perform either of the following operations to go to the Unmap Object page:
● Click the name of the desired host group. In the upper right corner of the page that is
displayed, select Unmap from the Operation drop-down list.
● Click the name of the desired host group. On the page that is displayed, click the
Mapping tab page, then click More on the right of the LUN group, and select Unmap.
Skip this step if you cancel the mapping between a host group and a LUN group from the
Mapping tab page.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click More on the right of the desired host group
and choose Add Host.
NOTE
Alternatively, perform any of the following operations to go to the Add Host page:
● Click the name of the desired host group. In the upper right corner of the page that is
displayed, select Add Host from the Operation drop-down list.
● Click the name of the desired host group. On the page that is displayed, click the
Member Hosts tab page, and then click Add.
● Click the value in the Hosts column of the desired host group if the value is not 0. On
the Member Hosts tab page, click Add.
Step 4 Select one or more hosts from Available Hosts and add them to Selected Hosts.
NOTE
You can select Only show the hosts that have not been added to any host group below
the host list, which helps you find the desired hosts.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click More on the right of the desired host group
and choose Remove Host.
NOTE
Step 4 Select one or more hosts from Available Hosts and add them to Selected Hosts.
NOTE
Skip this step if you remove hosts from the Member Hosts tab page.
----End
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click More on the right of the desired host group
and choose Modify.
NOTE
Alternatively, click the name of the desired host group. In the upper right corner of the
page that is displayed, select Modify from the Operation drop-down list.
NOTE
----End
Prerequisites
The host group to be deleted is not mapped.
Procedure
Step 1 Choose Services > Block Service > Host Groups > Host Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 On the Host Groups tab page, click More on the right of the desired host group
and choose Delete.
NOTE
Alternatively, click the name of the desired host group. In the upper right corner of the
page that is displayed, select Delete from the Operation drop-down list.
----End
Procedure
Step 1 Choose Services > Block Service > Port Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View information about port groups in the function pane. Table 5-50 describes
the parameters.
Parameter Description
ID ID of a port group.
Step 4 (Optional) Click the name of a port group to query its summary and member
ports.
----End
Procedure
Step 1 Choose Services > Block Service > Port Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired port group and select Add Port.
The Add Port page is displayed on the right.
NOTE
Alternatively, perform any of the following operations to go to the Add Port page:
● Click the name of the desired port group. In the upper right corner of the page that is
displayed, select Add Port from the Operation drop-down list.
● Click the name of the desired port group. On the page that is displayed, click the
Member Ports tab page, and then click Add.
● Click the value in the Ports column of the desired port group if the value is not 0. On
the Member Ports tab page, click Add.
Step 4 In Available Ports, select one or more desired ports and they are added to
Selected Ports automatically.
NOTE
----End
Procedure
Step 1 Choose Services > Block Service > Port Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired port group and select Remove Port.
The Remove Port page is displayed on the right.
NOTE
Step 4 In Available Ports, select one or more desired ports and they are added to
Selected Ports automatically.
NOTE
Skip this step if you remove ports from the Member Ports tab page.
----End
Procedure
Step 1 Choose Services > Block Service > Port Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired port group and select Modify.
NOTE
Alternatively, click the name of the desired port group. In the upper right corner of the page
that is displayed, select Modify from the Operation drop-down list.
NOTE
----End
Prerequisites
The port group to be deleted has not been mapped.
Procedure
Step 1 Choose Services > Block Service > Port Groups.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 Click More on the right of the desired port group and select Delete.
NOTE
Alternatively, click the name of the desired port group. In the upper right corner of the page
that is displayed, select Delete from the Operation drop-down list.
----End
Procedure
Step 1 Choose Services > Block Service > Mapping Views.
Step 2 Select the desired vStore from the vStore drop-down list in the upper left corner.
NOTE
Step 3 View the mapping view information in the function pane. Table 5-51 describes the
parameters.
ID ID of a mapping view.
Owning vStore Name of the vStore to which the mapping view belongs.
NOTE
This parameter is available only when vStore is set to All vStores in
Step 2.
NOTE
Mapping views include mapping LUNs to hosts, mapping LUN groups to hosts, and
mapping LUN groups to host groups.
● In a mapping view where LUNs are mapped to a host, LUN Group and Host Group are
displayed as --. You can click the name of the mapping view and click the LUNs tab to
view the LUNs mapped to the host.
● In a mapping view where a LUN group is mapped to a host, Host Group is displayed as
--.
● In a mapping view where a LUN group is mapped to a host group, Host is displayed as
--.
● In a mapping view that does not contain a port group, Port Group is displayed as --.
----End
6 FAQs
This chapter describes the FAQs related to the basic storage service configuration
guide. You can also refer to this chapter to handle faults encountered during
configuration or maintenance.
6.1 How Can I Enable Mapping Cancellation Fool-Proofing?
6.2 How Can I Query the iSCSI Target Name of an Ethernet Port on a Storage
System?
NOTE
● Mapping cancellation operations include: unmap a LUN and a host, unmap a host and a
LUN group, unmap a host group and a LUN group, remove a LUN from a LUN group,
remove a host from a host group, and remove an initiator.
● After this function is enabled, the system checks whether there are I/O operations at the
point in time when an operation is performed. The system may incorrectly determine
the status of periodical or routine test services. Therefore, this function provides only
reference for you to determine the service status. You need to manually confirm
whether there are running services. If you confirm the involved LUN but the system still
displays a message indicating that I/O operations exist, disable this function and try
again.
● You can run the show tgt_switch map_foolproof command to check whether the
function is enabled. For more details, refer to the command reference specific to your
product version.
NOTE
Using DeviceManager
Method 1:
Choose Services > Network > Ethernet Network > Ethernet Ports. Click the
desired Ethernet port and view its iSCSI Target Name on the page that is
displayed.
Method 2:
Step 2 Click the controller enclosure where the desired Ethernet port resides.
----End
This section provides some CLI commands for configuring basic block storage
services.
NOTE
Configuration Process
The following flowchart shows the common configuration process.
Start
Create a host.
Configure connectivity.
End
Mandatory Optional
Logging in to the storage For details, see "Logging In to the CLI" in the
system using the CLI Initialization Guide.
Table A-3 Commands for creating mappings and configuring host connectivity
Procedure Command
Procedure Command
● Creating an initiator
– iSCSI connection:
create initiator iscsi
Using storage space For details, see "Scanning LUNs on the Host"
in the Host Connectivity Guide.
This section provides some CLI commands for managing basic block storage
services.
NOTE
Operation Command
Managing LUNs
Operation Command
Operation Command
Operation Command
Managing Hosts
Operation Command
Operation Command
Managing Initiators
Operation Command
Managing Mappings
● IPv6 network:
add logical_port ipv6_route
● IPv6 network:
remove logical_port ipv6_route
D Glossary
A
AC power module The module that transfers the external AC power
supply into the power supply for internal use.
Application server A service processing node (a computer device) on the
network. Application programs of data services run
on the application server.
Asynchronous remote A kind of remote replication. When the data at the
replication primary site is updated, the data does not need to be
updated synchronously at the mirroring site to finish
the update. In this way, performance is not reduced
due to data mirroring.
Air baffle It optimizes the ventilation channels and improves
the heat dissipation capability of the system.
Audit log guarantee A mode for recording audit logs. This mode
mode preferentially ensures that the audit log function is
normal and no audit log is missing.
Audit log non- A mode for recording audit logs. In this mode,
guarantee mode services are running properly. Audit logs may be
missing.
B
Backup A collection of data stored on (usually removable)
non-volatile storage media for purposes of recovery
in case the original copy of data is lost or becomes
inaccessible; also called a backup copy. To be useful
for recovery, a backup must be made by copying the
source data image when it is in a consistent state.
The act of creating a backup.
C
Cache hit ratio The ratio of the number of cache hits to the number
of all I/Os during a read task, usually expressed as a
percentage.
Captive screw Specially designed to lock into place on a parent
board or motherboard, allowing for easy installation
and removal of attached pieces without release of
the screw.
Challenge Handshake A password-based authentication protocol that uses a
Authentication challenge to verify that a user has access rights to a
Protocol system. A hash of the supplied password with the
challenge is sent for comparison so the cleartext
password is never sent over the connection.
Compliance mode A protection mode of WORM. In compliance mode,
files within their protection period cannot be changed
or deleted by either the file user or by the system
administrator. Files with expired protection periods
can be deleted but not changed by the file user or
the system administrator.
Controller The control logic in a disk or tape that performs
command decoding and execution, host data transfer,
serialization and deserialization of data, error
detection and correction, and overall management of
device operations. The control logic in a storage
subsystem that performs command transformation
and routing, aggregation (RAID, mirroring, striping, or
other), high-level error recovery, and performance
optimization for multiple storage devices.
Controller enclosure An enclosure that accommodates controllers and
provides storage services. It is the core component of
a storage system and generally consists of
components, such as controllers, power supplies, and
fans.
Copying A pair state. The state indicates that the source LUN
data is being synchronized to the target LUN.
Container root Space used to store the metadata for running
directory container images and container instances.
Container image An image is a special file system, which provides the
programs, libraries, resources, and configuration files
required for running containers. It also contains
configuration parameters, for example, for
anonymous disks, environment variables, and users.
The image does not contain dynamic data, and its
content will not be modified after construction.
Containerized An image can start multiple containers, and an
application application can contain one or a group of containers.
D
Data compression The process of encoding data to reduce its size. Lossy
compression (i.e., compression using a technique in
which a portion of the original information is lost) is
acceptable for some forms of data (e.g., digital
images) in some applications, but for most IT
applications, lossless compression (i.e., compression
using a technique that preserves the entire content of
the original data, and from which the original data
can be reconstructed exactly) is required.
Data flow A process that involves processing data extracted
from the source system. These processes include:
filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting
invalid data so that the processed data meets the
requirements of the destination system for the input
data.
Data migration A movement of data or information between
information systems, formats, or media. Migration is
performed for reasons such as possible decay of
storage media, obsolete hardware or software
(including obsolete data formats), changing
performance requirements, the need for cost
efficiencies etc.
Data source A system, database (database user; database
instance), or file that can make BOs persistent.
Deduplication The replacement of multiple copies of data — at
variable levels of granularity — with references to a
shared copy in order to save storage space and/or
bandwidth.
Dirty data Data that is stored temporarily on the cache and has
not been written onto disks.
E
eDevLUN Logical storage array space created by a third-party
storage array.
Expansion module A component used for expansion.
Expansion Connects a storage system to more disk enclosures
through connection cables, expanding the capacity of
the storage system.
F
Field replaceable unit A unit or component of a system that is designed to
be replaced in the field, i.e., without returning the
system to a factory or repair depot. Field replaceable
units may either be customer-replaceable or their
replacement may require trained service personnel.
Firmware Low-level software for booting and operating an
intelligent device. Firmware generally resides in read-
only memory (ROM) on the device.
Flash Translation Layer Flash Translation Layer (FTL) organizes and manages
host data, enables host data to be allocated to NAND
flash chips of SSDs in an orderly manner, maintains
the mapping relationship between logical block
addresses (LBAs) and physical block addresses
(PBAs), and implements garbage collection, wear
leveling, and bad block management.
Front-end port The port that connects the controller enclosure to the
service side and transfers service data. There are
three types of front-end ports: SAS, Fibre Channel,
and iSCSI.
Front-end interconnect On a storage device, all controllers share the front-
I/O module (FIM) end interface modules.
G
Garbage collection The process of reclaiming resources that are no
longer in use. Garbage collection has uses in many
aspects of computing and storage. For example, in
flash storage, background garbage collection can
improve write performance by reducing the need to
perform whole block erasures prior to a write.
Gateway A device that receives data via one protocol and
transmits it via another.
Global garbage With a view to defragmentation of storage arrays
collection and garbage collection of disks, global garbage
collection reduces garbage of disks by enabling
storage arrays to inform disks of not implementing
invalid data relocation and of controlling space
release so that disks and controllers consume less
space, reducing costs and prolonging the useful life
of storage arrays.
H
Hard disk tray The tray that bears the hard disk.
Heartbeat Heartbeat supports node communication, fault
diagnosis, and event triggering. Heartbeats are
protocols that require no acknowledgement. They are
transmitted between two devices. The device can
judge the validity status of the peer device.
Hit ratio The ratio of directly accessed I/Os from the cache to
all I/Os.
Hot swap The substitution of a replacement unit (RU) in a
system for a defective unit, where the substitution
can be performed while the system is performing its
normal functioning normally. Hot swaps are physical
operations typically performed by humans.
HyperMetro A value-added service of storage systems.
HyperMetro means two datasets (on two storage
systems) can provide storage services as one dataset
to achieve load balancing among applications and
failover without service interruption.
HyperMetro domain A HyperMetro configuration object generally; made
up of two storage arrays and one quorum server.
HyperMetro services can be created on a HyperMetro
domain.
HyperMetro vStore A HyperMetro vStore pair consists of two vStores,
pair that is, two tenants. After a HyperMetro relationship
is set up for a pair of vStores, the datasets in the two
vStores work in redundancy mode and provide
storage services in one dataset view, achieving hitless
service failover.
I
In-band management The management control information of the network
and the carrier service information of the user
network are transferred through the same logical
channel. In-band management enables users to
manage storage arrays through commands.
Management commands are sent through service
channels, such as I/O write and read channels. The
advantages of in-band management include high
speed, stable transfer, and no additional
management network ports required.
Initiator The system component that originates an I/O
command over an I/O interconnect. The endpoint
that originates a SCSI I/O command sequence. I/O
adapters, network interface cards, and intelligent I/O
interconnect control ASICs are typical initiators.
I/O Shorthand for input/output. I/O is the process of
moving data between a computer system's main
memory and an external device or interface such as a
storage device, display, printer, or network connected
to other computer systems. This encompasses
reading, or moving data into a computer system's
memory, and writing, or moving data from a
computer system's memory to another location.
Interface module A replaceable field module that accommodates the
service or management ports.
L
Load balance A method of adjusting the system, application
components, and data to averagely distribute the
applied I/Os or computing requests to physical
resources of the system.
Logical unit The addressable entity within a SCSI target that
executes I/O commands.
Logical unit number The SCSI identifier of a logical unit within a target.
Industry shorthand, when phrased as "LUN", for the
logical unit indicated by the logical unit number.
LUN formatting The process of writing 0 bits in the data area of the
logical drive and generating related parity bits so that
the logical drive can be in the ready state.
LUN mapping A storage system maps LUNs to application servers
so that application servers can access storage
resources.
LUN migration A method for the LUN data to migrate between
different physical storage spaces while ensuring data
integrity and uninterrupted operation of host
services.
LUN snapshot A type of snapshot created for a LUN. This snapshot
is both readable and writable and is mainly used to
provide a snapshot LUN from point-in-time LUN
data.
Lever A lever resides on the structural part of a module. It
is used to insert or remove a module into or from a
chassis, saving efforts.
Local image repository A private repository used to store the container
images and Helm charts imported by users. It is
different from the standard image repository. The
imported images and Helm charts must meet the
compatibility requirements of the system.
M
Maintenance terminal A computer connected through a serial port or
management network port. It maintains the storage
system.
Management interface The module that integrates one or more
module management network ports.
Management network An entity that provides means to transmit and
process network management information.
N
NVM Express A host controller interface with a register interface
and command set designed for PCI Express-based
SSDs.
NVMe SSD A solid state disk (SSD) with a non-volatile memory
express (NVMe) interface. Compared with other
SSDs, such SSDs can deliver higher performance and
shorter latency.
O
Out-of-band A management mode used during out-of-band
management networking. The management and control
information of the network and the bearer service
information of the user network are transmitted
through different logical channels.
P
Power failure When an external power failure occurs, the AC PEM
protection depends on the battery for power supply. This
ensures the integrity of the dirty data in the cache.
Pre-copy When the system monitors a failing member disk in a
RAID group, the system copies the data from the disk
to a hot spare disk in advance.
Palm-sized NVMe SSD A palm-sized NVMe SSD is a type of NVMe SSD of
which the dimensions (H x W x D) are 160 mm x 79.8
mm x 9.5 mm (neither 3.5-inch nor 2.5-inch).
Q
Quorum server A server that can provide arbitration services for
clusters or HyperMetro to prevent the resource access
conflicts of multiple application servers.
R
RAID level The application of different redundancy types to a
logical drive. A RAID level improves the fault
tolerance or performance of the logical drive but
reduces the available capacity of the logical drive.
You must specify a RAID level for each logical drive.
Reconstruction The regeneration and writing onto one or more
replacement disks of all of the user data and check
data from a failed disk in a mirrored or RAID array. In
most arrays, a rebuild can occur while applications
are accessing data on the array's virtual disks.
Redundancy The inclusion of extra components of a given type in
a system (beyond those required by the system to
carry out its function) for the purpose of enabling
continued operation in the event of a component
failure.
Remote replication A core technology for disaster recovery and a
foundation that implements remote data
synchronization and disaster recovery. This
technology remotely maintains a set of data mirrors
through the remote data connection function of the
storage devices that are separated in different places.
Even when a disaster occurs, the data backup on the
remote storage device is not affected. Remote
replication can be divided into synchronous remote
replication and asynchronous remote replication.
Reverse The process of restoring data from the redundancy
synchronization machine (RM) when the services of the production
machine (PM) are recovering.
Route The path that network traffic takes from its source to
its destination. On a TCP/IP network, each IP packet
is routed independently. Routes can change
dynamically.
S
Script A parameterized list of primitive I/O interconnect
operations intended to be executed in sequence.
Often used with respect to ports, most of which are
able to execute scripts of I/O commands
autonomously (without policy processor assistance).
A sequence of instructions intended to be parsed and
carried out by a command line interpreter or other
scripting language. Perl, VBScript, JavaScript and Tcl
are all scripting languages.
Serial port An input/output location (channel) that sends and
receives data (one bit at a time) to and from the CPU
of a computer or a communications device. Serial
ports are used for serial data communication and as
interfaces for some peripheral devices, such as mouse
devices and printers.
Service data The user and/or network information required for the
normal functioning of services.
Service network port The network port that is used to store services.
Simple network An IETF protocol for monitoring and managing
management protocol systems and devices in a network. The data being
monitored and managed is defined by an MIB. The
functions supported by the protocol are the request
and retrieval of data, the setting or writing of data,
and traps that signal the occurrence of events.
Single point of failure One component or path in a system, the failure of
which would make the system inoperable.
Slot A position defined by an upper guide rail and the
corresponding lower guide rail in a frame. A slot
houses a board.
Small computer system A collection of ANSI standards and proposed
interface standards that define I/O interconnects primarily
intended for connecting storage subsystems or
devices to hosts through host bus adapters. Originally
intended primarily for use with small (desktop and
desk-side workstation) computers, SCSI has been
extended to serve most computing needs, and is
arguably the most widely implemented I/O
interconnect in use today.
Snapshot A point in time copy of a defined collection of data.
Clones and snapshots are full copies. Depending on
the system, snapshots may be of files, LUNs, file
systems, or any other type of container supported by
the system.
Snapshot copy A copy of a snapshot LUN.
T
Target The endpoint that receives a SCSI I/O command
sequence.
Target LUN The LUN on which target data resides.
Thin LUN A logic disk that can be accessed by hosts. It
dynamically allocates storage resources from the thin
pool according to the actual capacity requirements of
users.
U
User interface The space where users interact with a machine.
U-shaped bracket It is an optional structural part like letter "U". It is
located between the mounting ear of a chassis and
the mounting bar of a cabinet or bay and is used to
adjust the locations of the chassis and mounting bar
of the cabinet or bay.
W
Wear leveling A set of algorithms utilized by a flash controller to
distribute writes and erases across the cells in a flash
device. Cells in flash devices have a limited ability to
survive write cycles. The purpose of wear leveling is
to delay cell wear out and prolong the useful life of
the overall flash device.
Write amplification Increase in the number of write operations by the
device beyond the number of write operations
requested by hosts.
Write amplification The ratio of the number of write operations on the
factor device to the number of write operations requested
by the host.
Z
Zone A collection of Fibre Channel N_Ports and/or
NL_Ports (i.e., device ports) that are permitted to
communicate with each other via the fabric. Any two
N_Ports and/or NL_Ports that are not members of at
least one common zone are not permitted to
communicate via the fabric. Zone membership may
be specified by: 1) port location on a switch, (i.e.,
Domain_ID and port number); or, 2) the device's
N_Port_Name; or, 3) the device's address identifier;
or, 4) the device's Node_Name. Well-known
addresses are implicitly included in every zone.
C
CHAP Challenge Handshake Authentication Protocol
CLI Command-Line Interface
F
FC Fiber Channel
G
GPT GUID Partition Table
GUI Graphical User Interface
H
HBA Host Bus Adapter
I
IE Internet Explorer
IP Internet Protocol
IQN iSCSI Qualified Name
iSCSI Internet Small Computer Systems Interface
iSNS Internet Storage Name Service
L
LDAP Lightweight Directory Access Protocol
LUN Logical Unit Number
W
WWN World Wide Name
WWPN World Wide Port Name