No relevant resource is found in the selected language.

This site uses cookies. By continuing to browse the site you are agreeing to our use of cookies. Read our privacy policy>Search

Reminder

To have a better experience, please upgrade your IE browser.

upgrade

SmartMulti-Tenant Feature Guide for Block

OceanStor V5 Series V500R007

This document is applicable to OceanStor 5110 V5, 5110F V5, 5300 V5, 5300F V5, 5500 V5, 5500F V5, 5600 V5, 5600F V5, 5800 V5, 5800F V5, 6800 V5, 6800F V5, 18500 V5, 18500F V5, 18800 V5, and 18800F V5. This document describes the implementation principles and application scenarios of the SmartMulti-Tenant feature. Also, it explains how to configure and manage SmartMulti-Tenant.
Rate and give feedback :
Huawei uses machine translation combined with human proofreading to translate this document to different languages in order to help you better understand the content of this document. Note: Even the most advanced machine translation cannot match the quality of professional translators. Huawei shall not bear any responsibility for translation accuracy and it is recommended that you refer to the English document (a link for which has been provided).
Planning Service Data

Planning Service Data

To smoothly configure storage services, you must prepare or plan the required data based on the onsite requirements.

Scenario 1: Data Preparation (System Users)

In this scenario, system users complete all configuration tasks in the system view and vStore view. Table 2-8 lists the data to be prepared.

Table 2-8 Data to be prepared

Operation

Item

Default/Actual Value

Logging in to DeviceManager

IP addresses of the management network ports

IP address to be entered in the browser address box for logging in to DeviceManager of the storage system.

For a 2 U controller enclosure (OceanStor 5300 V5/5300F V5/5500 V5/5500F V5), the default IP addresses of the management network ports on controllers A and B are respectively 192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.255.0.

For a 3 U or 6 U controller enclosure (OceanStor 5600 V5/5600F V5/5800 V5/5800F V5/6800 V5/6800F V5), the default IP addresses of the management network ports on management modules 0 and 1 are respectively 192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.0.0.

User name and password

User name and password for logging in to DeviceManager of the storage system.

Super administrator user name: admin

Initial password: Admin@storage

Creating a disk domain

Disk domain name

Name of the disk domain to be created.

__________________

Disk type

Disk types in the disk domain, which determine the storage tiers that can be created. SSDs correspond to the high performance tier, SAS disks correspond to the performance tier, and NL-SAS disks correspond to the capacity tier.

High performance Tier (SSD)__________________

Performance Tier (SAS)__________________

Capacity Tier (NL-SAS)__________________

Creating a storage pool

Storage pool name

Name of the storage pool to be created.

__________________

Storage tier

The storage pool can have the high performance tier, performance tier, and capacity tier.

High performance Tier (SSD)__________________

Performance Tier (SAS)__________________

Capacity Tier (NL-SAS)__________________

RAID policy

Each tier is configured with a specific RAID policy. The default RAID policy on DeviceManager is recommended. For example, the default RAID policy of the performance tier on DeviceManager is RAID5 4D+1P, where D indicates the data block and P indicates the parity block.

High performance Tier__________________

Performance Tier__________________

Capacity Tier__________________

Capacity

Capacity of each storage tier. The value must be an integer on DeviceManager.

High performance Tier__________________

Performance Tier__________________

Capacity Tier__________________

Creating a vStore

vStore name

__________________

SAN capacity quota

Total capacity for SAN services

__________________

NAS capacity quota

Total capacity for NAS services

__________________

Creating a LUN

LUN name

If LUNs are created in a batch, the storage system automatically names each LUN by adding four digits after your specified LUN name.

__________________

SmartThin enabled or not

After SmartThin is enabled during LUN creation, the storage system does not allocate the configured capacity to the LUN at a time. Instead, the storage system dynamically allocates storage resources on demand based on site requirements.

Yes____

No____

Owning storage pool

Storage pool to which a LUN to be created belongs

__________________

Capacity

Space of the LUN to be created

__________________

Number of LUNs

Number of LUNs to be created in the storage system

__________________

Owning controller

Controller to which a LUN to be created belongs

Auto select__________________

CTE0.A__________________

CTE0.B__________________

Initial capacity allocation policy

Policy for the storage tier to allocate capacity to a LUN

Automatic allocation__________________

Allocate from the high-performance tier first__________________

Allocate from the performance tier first_________________

Allocate from the capacity tier first_________________

Cache policy

Policy that determines how data is written to and read from the LUN

Read Policy:

Resident________________

Default________________

Recycle________________

Write Policy:

Resident________________

Default________________

Recycle________________

Prefetch policy

When reading data, the storage system prefetches required data from disks to the cache in advance according to a preset policy.

No prefetch_________________

Intelligent prefetch________________

Constant prefetch_________________

Variable prefetch_________________

Scenario 2: Data Preparation (System Users + vStore Users)

In this scenario, after system users configure global resources and create vStores and vStore users, vStore users need to log in to the vStore view to configure the vStores. Table 2-9 lists the data to be prepared.

Table 2-9 Data to be prepared

Operation

Item

Default/Actual Value

Logging in to DeviceManager

IP addresses of the management network ports

IP address to be entered in the browser address box for logging in to DeviceManager of the storage system.

For a 2 U controller enclosure (5300 V5/5300F V5/5500 V5/5500F V5), the default IP addresses of the management network ports on controllers A and B are respectively 192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.255.0.

For a 3 U or 6 U controller enclosure (OceanStor 5600 V5/5600F V5/5800 V5/5800F V5/6800 V5/6800F V5), the default IP addresses of the management network ports on management modules 0 and 1 are respectively 192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.0.0.

User name and password

User name and password for logging in to DeviceManager of the storage system.

Super administrator user name: admin

Initial password: Admin@storage

vStore name__________________

Password__________________

Creating a disk domain

Disk domain name

Name of the disk domain to be created.

__________________

Disk type

Disk types in the disk domain, which determine the storage tiers that can be created. SSDs correspond to the high performance tier, SAS disks correspond to the performance tier, and NL-SAS disks correspond to the capacity tier.

High performance Tier (SSD)__________________

Performance Tier (SAS)__________________

Capacity Tier (NL-SAS)__________________

Creating a storage pool

Storage pool name

Name of the storage pool to be created.

__________________

Storage tier

The storage pool can have the high performance tier, performance tier, and capacity tier.

High performance Tier (SSD)__________________

Performance Tier (SAS)__________________

Capacity Tier (NL-SAS)__________________

RAID policy

Each tier is configured with a specific RAID policy. The default RAID policy on DeviceManager is recommended. For example, the default RAID policy of the performance tier on DeviceManager is RAID5 4D+1P, where D indicates the data block and P indicates the parity block.

High performance Tier__________________

Performance Tier__________________

Capacity Tier__________________

Capacity

Capacity of each storage tier. The value must be an integer on DeviceManager.

High performance Tier__________________

Performance Tier__________________

Capacity Tier__________________

(Optional) Configuring domain authentication for a storage system

Server type

LDAP server__________________

Windows AD domain server__________________

Protocol

Encryption protocol used for domain authentication

LDAP__________________

LDAPS__________________

Base DN

Root directory of a server

__________________

Bind DN

Binding directory of a server

__________________

Bind password

Password used for accessing the directory corresponding to a bind DN

__________________

User directory

Directory of the domain account

__________________

User ID properties

ID properties of a storage user object, used to search for the user when the user ID is given

__________________

User name properties

Name properties of a storage user object, used to search for the user when the user name is given

__________________

User object type

Each entry in the LDAP directory is associated with one or more object types. The object types include: users, groups, emails, and maintenance terminals.

__________________

Group ID properties

A group can contain multiple users. This item indicates the storage group object ID and is used to find the group when the group ID is given.

__________________

Creating a vStore

vStore name

__________________

SAN capacity quota

Total capacity for SAN services

__________________

NAS capacity quota

Total capacity for NAS services

__________________

Creating a vStore user

Type

Type of the vStore to be created

Local user__________________

User name__________________

Password__________________

LDAP user (group)__________________

User name__________________

Role

User role to be created

vStore administrator__________________

vStore protocol administrator__________________

vStore data protection administrator__________________

Type

Classified into administrators and read-only users

Administrator__________________

Read-only user__________________

Creating a LUN

LUN name

If LUNs are created in a batch, the storage system automatically names each LUN by adding four digits after your specified LUN name.

__________________

SmartThin enabled or not

After SmartThin is enabled during LUN creation, the storage system does not allocate the configured capacity to the LUN at a time. Instead, the storage system dynamically allocates storage resources on demand based on site requirements.

Yes____

No____

Owning storage pool

Storage pool to which a LUN to be created belongs

__________________

Capacity

Space of the LUN to be created

__________________

Number of LUNs

Number of LUNs to be created in the storage system

__________________

Owning controller

Controller to which a LUN to be created belongs

Auto select__________________

CTE0.A__________________

CTE0.B__________________

Initial capacity allocation policy

Policy for the storage tier to allocate capacity to a LUN

Automatic allocation__________________

Allocate from the high-performance tier first__________________

Allocate from the performance tier first_________________

Allocate from the capacity tier first_________________

Cache policy

Policy that determines how data is written to and read from the LUN

Read Policy:

Resident________________

Default________________

Recycle________________

Write Policy:

Resident________________

Default________________

Recycle________________

Prefetch policy

When reading data, the storage system prefetches required data from disks to the cache in advance according to a preset policy.

No prefetch_________________

Intelligent prefetch________________

Constant prefetch_________________

Variable prefetch_________________

Translation
Download
Updated: 2019-07-11

Document ID: EDOC1000181478

Views: 29376

Downloads: 182

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