huawei oceanstor 2000 v3 -...

1HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Huawei OceanStor 2000 V3

Технический Вебинар


Содержание

1

2

3

Обзор и позиционирование

Функционал и особенности

Конкурентное сравнение

4 Квотирование


Семейство СХД OceanStor V3

2200 V3 2600 V3 5300 V3 - 5800 V3 6800 V3, 18000 V3

Простота в

использованииКонвергенция Надежность


OceanStor V3 Обзор СХД начального уровня

2200 V3 2600 V3

• 8G или 16G/контроллер, до 2

контроллеров, один слот

расширения

• Протоколы 8G FC/ 16G FC / 10GE /

GE

• Базовые функции Smart и Hyper

ПО

• Начальная SAN СХД, высокая

экономическая эффективность

особенно для небольших

конфигураций.

• 16G или 32G/контроллер, до 8

контролеров, два слота

расширения

• Протоколы 8G FC/16G FC / 10GE /

GE

• Расширенные функции Smart и

Hyper ПО

• Начальная SAN+NAS СХД,

Оптимальный баланс между

стоимостью, производительностью,

простотой и функциональностью


Продукт 2200 V3 2600 V3

Аппаратная Спецификация

Максимальное количество

Дисков300 500


контролеров2 8

Кеш (пара контроллеров) 16 GB/32 GB 32 GB/64 GB


портов подключения (пара

контролеров)

24 40

Программная спецификация

Защита информацииHyperCopy, HyperClone, HyperMirror,

HyperSnap, HyperReplication

HyperSnap, HyperCopy, HyperClone, HyperMirror,

HyperReplication, HyperLock (WORM), HyperMetro, HyperVault

Защита сервисов SmartQoS SmartQoS, SmartPartition

Улучшение использования

ресурсов

SmartTier, SmartCache, SmartThin,

SmartMotion, SmartMigration, SmartErase,

SmartVirtualization

SmartTier, SmartCache, SmartThin, SmartMotion,

SmartMigration, SmartErase, SmartVirtualization, SmartMulti-

Tenant, SmartCompression, SmartDedupe, SmartQuota

Простое конфигурированиеSmartConfig значительно упрощает конфигурирование для ИТ-администраторов. Они могут освоить методы конфигурации после краткого введения, и не нужно изучать профессиональные технологии хранения данных.

OceanStor V3 Спецификации СХД начального уровня


OceanStor 2200 V3 Внешний вид СХД начального уровня

Блок питания с встроенным

вентилятором

1+1 отказоустойчивость

94% КПД

Поддержка 100V~240V AC и 240V HVDC

Интерфейсные модули

1 слот с горячей заменой, только для хостов

Типы интерфейсов: GE, 10GE electrical, SmartIO

card (16G FC, 8G FC, 10Gb FCoE [VN2VF], и 10Gb

Eth [optical])

Предустановленные порты

4xGE порта в каждом

контроллере

SAS порты каскадирования

два SAS порта на каждом


Заглушка


OceanStor 2600 V3 Внешний вид СХД начального уровня

Блок питания с встроенным

вентилятором

1+1 отказоустойчивость

94% КПД

Поддержка 100V~240V AC и

240V HVDC и -48V~-60V DC

Интерфейсные модули

2 слота с горячей заменой, только для

хостов

Типы интерфейсов: GE, 10GE electrical,

SmartIO card (16G FC, 8G FC, 10Gb FCoE

[VN2VF], и 10Gb Eth [optical])

Предустановленные порты

4xGE порта в каждом


SAS порты каскадирования

два SAS порта на каждом



OceanStor V3 Внутренний вид СХД начального уровня

CBU

DIMM0

msata0

Interface card 0

Filler panel

2200 V3CBU

DIMM0

Interface card 1

Interface card 0

msata0

msata1

DIMM1

2600 V3

Differences between 2600 and 2200:

A. 2200 has one memory while 2600 has two.

B. 2200 has one MSATA low-rate disk while 2600 has two high-rate disks.

C. 2200 has one interface card while 2600 has two.


2200 V3/2600 V3 Системная архитектура

2U disk and controller integration (2600/2200)

1GE heartbeatController BController A

x4

SAS3.0

External JBOD

B ports

A ports

SAS

Expander

SAS

Expander24…10

FC/GE/10GE

Network

24…10SAS

Expander

CPU

SAS

Expander

CPU

Front interface

module

PCIE3.0 X4 mirror

Network

FC/GE/10GE

Front interface

module

B ports

A ports

x4

SAS3.0

x4

SAS3.0x4

SAS3.0

Распределение полос пропускания

внутри контролера

CPU

Interface

module 0

Interface

module 1Onboard GE

x4

PCIE3.0

x4

PCIE3.04*GE

Mirror unit

x4

PCIE3.0

Expander

X4

SAS3.0

Mirror

Expansion

port


2200 V3/2600 V3 Аппаратная архитектура

System

enclosure

Controller

Power-fan module

Disk module


Аппаратная архитектура полок расширения

Дисковые Модули

Блок Питания

Модуль расширения

Дисковые Модули

Модуль Охлаждения

Модуль расширения

Блок Питания

4 U дисковая полка : 24 x 3.5-inch

2 U дисковая полка : 25 x 2.5-inch


Contents

1

2

3

4




Квотирование


RAID2.0+ Architecture

Huawei RAID2.0+: bottom-layer media virtualization + upper-layer resource virtualization for fast data reconstruction and smart resource allocation

Fast data reconstruction: Data reconstruction time is reduced from 10 hours to only 30 minutes. The data reconstruction speed is improved by 20 times.

Adverse service impacts and disk failure rates are reduced.

All disks in a storage pool participate in reconstruction, and only service data is reconstructed. The traditional many-to-one reconstruction mode is

transformed to the many-to-many fast reconstruction mode.

Data reconstruction speed is accelerated by 20 times.

Pool (consisting

of physical disks)

Chunk CKG LUNs are visible to hosts.

Disks of diversified

types coexist in a

storage pool.

Space provided by each

disk is divided into chunks

of a small granularity.

Chunks from

different disks form

CKGs.

LUNs can be created within a

short time.

Extent

CKGs are divided

into space of a

smaller granularity.

Tiered

Not tiered

Volume

Multiple extents

form a volume.

Not tiered


• The system can be automatically reconstructed without using hot spare disks. Using a 9-

disk RAID 5 as an example, if data on CKG 0 and CKG 1 is damaged, the system

randomly selects CKs for data reconstruction.

01 03

0814 16

2126

28

515634

33

44

42

66

71

74

73

88

CKG 0 (RAID 5)

4214 56 868316 44 66 73 08 21 34 51 01 26 33 74

Disk 0 Disk 1 Disk 2 Disk 3 Disk 4 Disk 5 Disk 6 Disk 7 Disk 8

03 28 71 88

Pool

CKG 1 (RAID 5) CKG 2 (RAID 5) CKG 3 (RAID 5)

86

61 8161 81

Reconstruction

Reconstruction

RAID2.0+ процес восстановления данных


Конфигурирование: от простого к простейшему

Автоматическая настройка LUN и монтирование СХД к серверам через SmartConfig, которые ранее требовали ручные операций в традиционных системах хранения.

Распределение по требованию ресурсов хранения

Шагов

конфигурирования

10 шагов 3 шага

Время

конфигурирования

10 Минут 1 Минута

Не требуется

профессиональных

знаний

Простые операции


OceanStor SmartConfigOceanStor SmartConfig это функция

управления, которая помогает настроить

СХД Huawei начального и среднего

уровня.

Первые в отрасли Конкуренты не имеют подобного

решения.

Простые операции 3 шага

Не требуются знания СХД

Безопасность

корпоративного уровня Интеллектуальное создание пулов

хранения

Настройка резервирования дисков

автоматически осуществляется в

фоновом режиме

Step 1: Add a device.

Step 2: Add a remote disk.

Step 3: Discover a new disk.


OceanStor SmartConfig

Step 1: Add a device.

Ste 2: Add a remote disk.

Step 3: Discover a new disk.


Интерфейсный модуль — SmartIO Card

1 Power indicator/Hot Swap button

2 16 Gbit/s Fibre Channel, 8 Gbit/s Fibre

Channel, or 10Gbit/s eth/FCoE(VN2VF) port

3 Port Link/Active/Mode indicator

4 Module handle

5 Port mode label

1

2

3

4

5

FC

ET

H

Supports 8 Gbit/s and 16 Gbit/s Fibre Channel and 10Gbit/s eth/FCoE(VN2VF) ports.

Supports 10GE iWARP (Scale-out). A SmartI/O card in a specific slot (slot 1 in 2600 V3) can

provide IP Scale-out ports, including four 10 Gbit/s Ethernet ports that use iWARP RDMA to

connect to other 2600 V3 controllers, connecting 2 to 8 controllers over a direct-connection or

switch-based network.

Allows port mode switch between FC, and Scale-out in DeviceManager or CLI. The new port

mode takes effect after 10 to 20 seconds.

Supports 16 Gbit/s, 8 Gbit/s, and 10 Gbit/s optical modules. By default, a SmartIO module

does not have an optical module. You need to configure optical modules based on site

requirements.


8 Gbit/s Fibre Channel High-Density Interface Module

2200 V3 and 2600 V3 both support 8Gb FC high-density interface module. Each controller can be configured with one such module

at most.

Each high-density interface module provides two 4x8 Gbit/s Fibre Channel physical ports. Based on the MPO of a dedicated optical

fiber, each physical port is converted into four 8 Gbit/s Fibre Channel ports. (The output end does not contain optical modules.) In this

way, a single high-density interface module can provide eight optical ports that are used only as storage target ports to connect to

hosts.

1-to-4 dedicated optical fibers with a length of 15 meters or 5 meters are supported. If the distance exceeds 15 meters, use an ODF to

increase the transmission length.

MPO to 4xDLC

optical fiber

QSFP+ optical

module

Optical distribution frame (ODF)


IP Масштабирование (2600 V3, четыре контроллера прямое

подключение)

Establishes a four-controller direct-

connection redundant network.

Provides SmartIO cards for internal

connection, TCP/IP-based iWARP

protocol for data transmission, and 10

Gbit/s port bandwidth.

Divides 10GE ports to VLANs to

establish separate data and heartbeat

networks.

Cluster-based storage management:

Connects to the customer network from

management network ports of controller

0. Controllers can be added on demand.

Supports up to four controllers.


IP масштабирование (2600 V3, подключение через 10 Gb коммутатор)

Employs two CE6850 switches to establish

dual redundant planes for multi-controller

interconnection.

Provides SmartIO cards for internal

connection, TCP/IP-based iWARP protocol

for data transmission, and 10 Gbit/s port

bandwidth.

Divides 10GE ports to VLANs to establish

separate data and heartbeat networks.

Cluster-based storage management:

Connects to the customer network from

management network ports of controller 0.

Controllers can be added on demand.

CE6850 switch management: Connects to

the customer network through ETH

management network ports.

Supports up to eight controllers.

A direct-connection network cannot be

changed to a switch-based network online.


Software on V3 — Опции SAN

DeviceManager: single device management

eSight: cross-field multiple device

management in a DC

BCManager: inter-DC DR

Management simplifying suite

Data protection suite

HyperSnap: increment-based local data

protection

HyperClone: complete copy–based local

data protection

HyperCopy: inter-device data protection

HyperReplication: inter-DC DR protection

HyperMetro: active-active DC protection

Efficiency-improving software

EMC

HDS

IBM

HW

SmartVirtualizationCross-system data flow

SmartTierVertical data flow

SmartMotionHorizontal data flow

SmartThinThin provisioning

SmartQoSIntelligent service quality

control

Partition 1

Partition2

Partition

4

Partition5

Partition3

Partition N

SmartPartitionIntelligent partitioning

SmartDedupe &

SmartCompressionIntelligent deduplication &

compression

SmartCacheIntelligent SSD caching

APP APP APP

SmartMulti-tenantMulti-tenancy

SmartMigrationLUN migration

SmartEraseData destruction


HyperSnap (virtual snapshot)

Concept

A virtual snapshot is an identical data copy of the

source data at a specific point in time. Snapshot

technologies include virtual snapshot and LUN clone,

and virtual snapshot is associated with the source LUN.

Technical characteristics

Instant generation: A storage system can generate a

snapshot (an identical copy of the source data) within

seconds.

Small space occupation: The snapshot is not a

complete physical copy of the source data, so it only

occupies small storage space.

Application scenarios

Fast data backup and recovery (against mis-deletion or

viruses)

Constant data protection

Data analysis and test

1. Data is written to the system.

ab

c

e

f

gSource

LUN

Resource

space

2. A virtual snapshot is activated, so a mapping table is created to record

data relationship.

12

3

4

5

6

7Mapping

table

3. (Copy-on-write) Before new data is written to the system, the existing

data in the source LUN is moved to the resource space, the mapping

table is changed accordingly, and then new data is written to the

system.

dx

4. If another new data needs to be written to the data block in the source

LUN, the new data overwrites the existing data.

y

5. The snapshot is rolled back.

d

Snapshot

point

Non-

snapshot

point

Data at the

snapshot

point

HyperSnap working mechanism


HyperCopy (LUN copy)

Concept

LUN copy replicates data from a source LUN to a target

LUN in the same array or a different array.

HyperCopy (full LUN copy)

Full LUN copy refers to the process of copying all data

from a source LUN to a target LUN.

Write requests to the source LUN must be suspended

before a full LUN copy task. If the source LUN handles

write requests during the copy process, data on the

target LUN will become inconsistent.

Advantages and application scenarios

Support for third-party storage

A source LUN can be smaller than its target LUN.

Support for data migration within an array or between

arrays

Data backup

1Full LUN copy

Service

interruption

Source LUN Target LUN

LUN copy1 2 34 5 67 8 9

1 2 34 5 67 8 9

HyperCopy working mechanism


HyperClone (clone)

HyperClone working mechanism1. During initial synchronization, the primary LUN receives a write

request from the host and checks the synchronization progress.

2. If the data block at the target location has not been copied to the

secondary LUN, the new data is directly written to the primary LUN

and then a periodic synchronization task copies the data to the

secondary LUN.

3. If the data block has been copied, the new data is written to both the

primary and secondary LUNs.

4. If the data block is being copied, the new data is written to both the

primary and secondary LUNs after the copy process is completed.

5. After initial synchronization, the primary and secondary LUNs can be

split, and then they can be independently used for different purposes.

Bitmaps are used to record data block changes.

Advantages and application scenarios• The damage of a primary LUN does not affect the usage of its

secondary LUNs.

• Clone is mainly applicable to data backup, data protection, and data

test and analysis.Primary

LUN

Secondary

LUN

0 0 01 1 11 1 1

a b cd e fg h i

a b cInitial

synchro

nization

jk

The bitmaps for

the blocks that

have been copied

are 0 and for those

being copied are 1.

j

j

k

0

e

ll

0

fg h i

Split

mn

00 0 0

1 1

The bitmaps

for the same

data blocks

are 0 and for

different data

blocks are 1.

HyperClone working mechanismConceptClone is a snapshot technology. It generates a complete copy of the

source data at a specific point in time, and is a backup method with

incremental synchronization.

Progress

bitmap


HyperMirrorHyperMirror is a data backup technology. It creates multiple

physical mirror copies for a LUN to achieve continuous LUN

backup and protection. In this way, the reliability and

availability of the LUN are significantly improved.

Working principle

Creating a mirrored LUN

1. Converts a local LUN or an external LUN into a mirrored

LUN, creates a mirror copy, and adds a mirror copy for

the mirrored LUN for redundancy.

Performing synchronization

1. Initial synchronization: Replicates all data from the

mirrored LUN to the mirror copy and writes data

concurrently to both the mirrored LUN and mirror copy.

2. Incremental synchronization: Replicates data increment

from the mirrored LUN to the mirror copy after the mirror

copy is recovered from Splitting or Interruption.

Implementing splitting

1. The mirror copy is unavailable after splitting, but is

available before splitting.

1

2 3

Common

LUN

Common

LUN

Mirrored

LUN

Mirror

copy

Mirror

copy

A B

Mirrored LUN

creating

Initial

synchronization

Splitting

Incremental

synchronization

When synchronization

between the mirrored LUN

and mirror copy needs to be

suspended

After a mirror

copy is created or

added

When the mirror copy

is recovered from

Interruption

When data synchronization



resumed

When synchronization



suspended


HyperReplication/S (synchronous remote replication)

Concept

HyperReplication/S is a remote replication technology that synchronizes

data between arrays in real time, maximizing data consistency and

minimizing data loss during disasters.

HyperReplication /S working mechanism

When a synchronous remote replication task is created, an initial

synchronization process begins, and all data on the primary LUN is

copied to its secondary LUN.

After initial synchronization, the primary LUN handles a write request

according to the following procedure:

1. The primary site receives a write request from the host and sets

the differential log value to "different" for the data block

corresponding to the I/O.

2. The primary site writes the new data to the primary LUN (LUN A)

and sends the write request to the secondary site through the

replication link.

3. If data is successfully written to both LUN A and LUN B, the

previous differential log value is changed to "same". If the data

write fails, the value remains "different" and the data block will be

copied again in the next synchronization process.

4. A write success is returned to the host.

Synchronous

remote

replication

Cache Cache

LUN A LUN B

Primary

site

Secondary

site

1

2 2

2

3

3

34

HyperReplication/S working mechanism

Advantages and application scenarios

Zero data loss

The replication rate is up to 64:1 (HyperReplication/S +

HyperReplication/A).

The primary and secondary arrays can be mirrored for

each other.

Applicable to local or metropolitan DR

Source LUNs' support for snapshot-based rollback


HyperReplication/A (asynchronous remote replication)

Concept

HyperReplication/A is a remote replication technology that periodically

synchronizes data between arrays, minimizing latency and performance

reduction in long-distance transfer.

HyperReplication/A working mechanism

When an asynchronous remote replication task is created, an initial

synchronization process begins, and all data on the primary LUN is copied to

its secondary LUN.

After initial synchronization, the primary LUN handles a write request

according to the following procedure:

1. When a replication period starts, the caches of the primary LUN (LUN

A) and secondary LUN (LUN B) generate new timestamps (TPN+1 and

TPX+1).

2. The primary site receives a write request from the host.

3. The primary site writes the request into TPN+1 and returns a write

success to the host.

4. During data synchronization, the system copies data in the timestamp

of the previous period, TPN, from LUN A's cache to TPX+1 in LUN B's

cache. If LUN A's cache reaches its high watermark, its data is flushed

to disks, and a snapshot is generated for TPN data.

5. The snapshot for the flushed data is replicated to LUN B.

Asynchronous

remote

replication

Cache Cache

LUN A LUN B

Primary

site

Secondary

site

12

5

3

5

4N+1

N

X+1

X

1

Proprietary multi-timestamp cache technology (patent

number: CT/CN2013/080203) for second-level RPO

Asynchronous remote replication

with second-level RPO

Advantages and application scenarios Small impact on performance and down to 5-second RPO

The replication rate is up to 64:1 (HyperReplication/S +

HyperReplication/A).

The primary and secondary arrays can be mirrored for each other.

Applicable to local, metropolitan, or remote DR

Source LUNs' support for snapshot-based rollback


SmartMotion: horizontal data flow

Traditional storageHuawei SmartMotion

After N months

Capacity Performance

After N months




The system just

gets online.


The system just

gets online.

Technical principles Monitoring the CK utilization rate and I/Os of disks

in real time

Periodically migrating CKs to free disks to balance

disk capacity and performance

Combining "priority" with "flow control" to reduce

the adverse impact of migration

Technical advantages Horizontal flow of storage resources and load balance on disks

Data and performance are balanced after the addition of new disks

Ensured service continuity during performance tuning

100% dynamic balance between capacity and performance

The plan adaptability is improved by 4 times.


SmartThin: space optimization

32 MB

32 MB

32 MB

32 MB8 KB

Data volume: 32 KB

Allocated space: 256 KB

Data volume: 32 KB

Allocated space: 128 MB

8 KB

8 KB

8 KB 8 KB

8 KB

8 KB

8 KB

1. Write

operation

Thin LUN

2. Space allocation or

optimization according

to the mapping table.

Pool

Capacity

on write

Space

allocation

Physical spaceActual data

Technical principles Capacity on write: If the allocated space becomes insufficient,

new space is relocated with a 64 KB granularity by default.

Mapping table: Logical units and physical units (with a default

64 KB granularity) are associated through a mapping table.

Redirection-on-time: redirecting I/Os from logical units to

physical units through a mapping table.

Technical advantages Efficient allocation policy: The 64-KB allocation

granularity improves efficiency in small-data block

scenarios.

Diversified reclamation mechanisms: supporting

reclamation by VMware VAAI commands, Symantec

Storage Foundation commands, Windows Server 2012

commands, and full-zero page check reclamation


All-zero data block/Unused storage space

Non-all-zero data block/Used storage space

Working principle1. When receiving a write request from the host, the thin

LUN divides the request in terms of grain granularity

(the granularity of space allocation: 64 KB) and checks

whether the grains contain all-zero data blocks.

2. The thin LUN queries the space allocation mapping

table to check whether the all-zero grains have been

allocated physical storage space.

3. If the logical storage address of all-zero grains has not

been allocated physical storage space, the thin LUN

directly returns an acknowledgement indicating a

successful data write to the host without space

allocation.

4. If the logical address of all-zero grains has been

allocated physical storage space, the thin LUN

releases the physical storage space to the storage

resource pool and returns an acknowledgement

indicating a successful data write to the host.

Thin LUNMapping

table

Pool

1

2

34

4

Space

release

Data shrinking


SmartVirtualization (intelligent heterogeneous virtualization)

EMC

IBM

Huawei

Data availability after migration from

heterogeneous storage

Data remains available after being migrated from

legacy storage systems.

Data can be migrated among storage systems of

different levels. Functions and features of

enterprise-level storage systems improve original

storage systems' storage efficiency.

Cross-level data migration enables inactive data

to be relocated in lower-cost storage systems,

reducing the TCO.

Local HA solutions based on combination with

volume mirroring

Volume mirroring can be performed between

LUNs on heterogeneous storage and local LUNs

for redundancy.

HDS


SmartMigration

Application scenarios

Migrating data on other vendors' products by working

with SmartVirtualization

Conversion between thick LUNs and thin LUNs

RAID level relocation

Working principle

Service data synchronization

Data changes on the source LUN can be synchronized

to the target LUN using dual-write and DCL technologies.

LUN information exchange

The LUN IDs keep unchanged, but the data volume IDs

are switched. In this way, the physical storage space to

which the source LUN points becomes the target data

volume after data migration. The entire service

relocation process is transparent to users.

Local

cache

1

3 3

3

46

Source

LUN

Remote

cache

52

5

DCL

Target

LUNPair

Source

LUN

Target

LUN

LUN IDData

volume ID

0 0

LUN IDData

volume ID

0 0

LUN IDData

volume ID

0 1

LUN IDData

volume ID

1 1

LUN IDData

volume ID

1 1

LUN IDData

volume ID

1 0

Before

switching

During

switching

After

switching

LUN information exchange to change the mapping

relationship between the LUN ID and data volume ID


SmartErase

SmartErase provides the following data destruction

methods:

DoD 5220.22-M: A data destruction standard put

forward by the US Department of Defense (DoD). The

standard provides a software method of destroying data

on writable storage media, namely, three times of

overwriting.

1. Using an 8-bit character to overwrite all addresses

2. Using the complementary codes of the character

(complements of 0 and 1) to overwrite all addresses

3. Using a random character to overwrite all addresses

Customized: A system generates data based on

internal algorithms and uses the data to overwrite all

addresses of LUNs for specific times.

1. The times of overwriting range from 3 to 99. The

default value is 7.


SmartDedup & SmartCompression (Deduplication and Compression)

1. Fixed-length data

blocks are created. The

size of each data block

is the same as that of

thin LUN block.

Data write to

storage disksHost data

Data deduplication and

compression

2. The data is duplicated.

Fingerprint calculation

using SHA1

Fingerprint query and

comparison

Byte-by-byte comparison

(optional)

3.The deduplicated data is

compressed for storage.

User-customized

compression policies

Data block compression granularity (adaptive): 8 KB/12 KB/16 KB/20 KB/24 KB/28 KB/32 KB

− When the size of a new data block is larger than 32 KB, the storage system directly compresses the data.

− When the size of a new data block is smaller than 32 KB, the storage system adaptively compresses

multiple such data blocks together.

Compression policy:

Fast: This policy is used by default when no ACC card is configured. It enables fast compression and uses the LZ4 algorithm.

Deduplication and

compression can be

independently started and

configured.

Deduplication is performed

before compression to save

more space.

Supported by

2600 V3, not by

2200 V3


SmartDedupe (online deduplication)

Acceleration

cardController

CPU

Fixed-length data blocks

Fingerprint query and

comparison

Deduplicated data write onto

disks

Online deduplication of fixed-length data blocks: The size of a

deduplicated data block is the same as that allocated by thin

LUNs. The size ranges from 4 KB to 64 KB.

Data processing flow:

1. The fingerprint of a new data block is calculated using the

SHA1 algorithm. If an ACC card is configured, the ACC card is

used for data calculation. If no ACC card is configured, the

controller CPU calculates data fingerprints.

2. The new fingerprint is compared with those of existing data

blocks.

3. If the fingerprint is different from all existing ones, the new

data block is written onto a disk. If the fingerprint is the same

as an existing one, the new data block is deleted and the

existing data block is located.

4. (Optional) If the new fingerprint is the same as an existing

one and the byte-by-byte comparison is enabled (using the

CLI), the new and existing data blocks are compared byte-by-

byte. If the two data blocks are different, the new data block is

written onto a disk. If they are the same, the new data block is

deleted and the existing data block is located.

SHA1 fingerprint calculation

algorithm

Host data write onto cache


Recommended scenarios for SmartDedupe and

SmartCompression

Data/Application Type SmartDedupe SmartCompression Space Saved

File service √ √ 70%

Virtual desktop infrastructure

(VDI) application√ √ 75%

Oracle database X √ 60%

Email service X √ 40%

Engineering data √ √ 78%

Earthquake and geological

dataX √ 40%

Notes:

1. SmartDedupe is not recommended for database scenarios because timestamps created

upon database table storage cannot be deduplicated.

2. Varying types of data of the email service has little chance of being deduplicated, but such

data can be compressed.

3. Geological data mainly consisting of unstructured data can be deduplicated or compressed.

The industry's recommendation and space saved (for reference):

Note: The space

saved is closely

related to the

nature of data.

Supported by 2600 V3, not by 2200 V3


Ease-of-Use by high-efficiency

Cache partitionbusiness isolation

QoSService Level Agreement

highpriority

Automatic tiered storage

business performance according to priority

and traffic limit

cache can be set quotas, avoid business

influence each other

to identify hot spots data in time and

migrated to the high-performance media

SSD

Disk Resource

CPU resource

low priority

Cache resource

SAS NL-SAS

App1APP2


SmartTier

Relocation mode

Manual and automatic relocation modes are available. I/O

monitoring and relocation periods can be configured.

Relocation speed

SmartTier provides three levels of relocation speed: high,

medium, and low.

Relocation policy

Four relocation modes are optional: Automatic relocation,

Relocation to a higher performance tier, Relocation to a

lower performance tier, and No relocation.

Value

SmartTier meets the requirements of enterprises on

both performance and capacity. By preventing historical

data from occupying expensive storage media, it

ensures effective investment and eliminates energy

consumption caused by useless capacities, reducing

TCO and optimizing cost-effectiveness.

The IOPS of the virtual hybrid load mode (18 Exchange VMs,

2 database VMs, and 2 application VMs) is up to 26,564.

Indicator With SmartTier Without SmartTier

Configuration

12 x 200 GB SSDs36 x 300 GB 10k rpm SAS disks

132 x 300 GB 10k rpm SAS disks

Number of 2 U disk enclosures

2 6

Application I/O latency on tier 0

2 ms 10 ms

Application I/O latency on tier 1

7 ms 20 ms

Storage spaceutilization

70% 20%

Power 500 W 1500 W

I/O monitoring

Data placement analysis

Data relocation

The I/O monitoring module collects statistics

on the activity levels of each data block.

The data relocation module relocates data

based on the rank and relocation policy.

The data placement analysis module ranks

the activity level of each data block.


SmartQoS: prioritizing key applications (1)

Limit the performance of

ordinary applications.

Start flow control.The ordinary application performance is

too high, and key applications are affected.

Start priority control.

SmartQoS (intelligent service quality control)

prioritizes applications by setting different

performance goals for them and ensures the

performance of key applications. It is applicable

to hybrid application scenarios.

Priority policy: The system allocates internal I/O

queues into different classes (high, medium, and

low), and arranges system resources such as

front-end parallel capability, CPU, cache, and

back-end disks to these I/O queues based on

their class level.

Setting upper limits in the flow control mechanism:

Limit the performance of non-critical applications by

setting upper limits for their IOPS, bandwidth, and

latency, preventing these applications from occupying

too many system resources.

Key applications (high)

Important applications

(medium)

Ordinary applications

(low)

General performance

General

performance

Ordinary

applications

Key applications


SmartPatition: facilitating key applications

SmartPartition (intelligent cache partitioning)

partitions system cache resources and protects the

performance of key applications.

Technical principles

Divides system cache resources into cache partitions

of different sizes.

Allocates cache partitions to different applications.

Adjusts the host concurrency and disk access

concurrency capabilities for each cache partition, and

controls the service quality of each application.

Benefits

Dedicated cache partitions for service isolation and

high reliability

Reserved cache resources for key applications,

improving service quality

Applicable to hybrid application scenarios

Service 1 Service 2 Service 3 Service N

Host

concurrency

Cache

Disk

concurrency


SmartCache (intelligent data caching)

Uses SSDs as the level-2 cache for RAM Cache as well as

the read cache for data deduplication.

SmartCache pool: Manages SSDs and allocates and

reclaims SSD resources for SmartCache partitions at a

granularity of 8 MB. Each controller has in independent

SmartCache pool, and each SmartCache pool belongs to a

controller. An SSD can belong only to one SmartCache

pool.

Supports dynamic capacity expansion and reduction of

SmartCache pools.

SmartCache partition: Provides SSD cache resources (at a

fine-grained granularity (from 4 KB to 128 KB) for services.

Different services can share one SmartCache partition, or

use their own SmartCache partitions.

Utilizes SSD resources in cyclic sequential write mode to

reduce garbage collection within SSDs, ensuring SSD

write performance while prolonging SSD service life.

RAM Cache

LUN/FileSystem

SmartCache

SSD HDD

Dedupe Meta


Most Cost-efficient Active-Active Arrays in Industry

DC A

SAN/NAS

DC B

2600 V3

SAN/NAS

2600 V3

HyperMetro

Oracle RACcluster

DB2 (PowerHA)

SQLServer (MSFC)

VMware vSphere cluster

FusionSphere cluster

Real active-active, RTO = 0

Cross-site service load sharing

SCSI optimization, improving

performance by 30%

No gateway, simple and reliable

Heterogeneous deployment, reuse

of old devices

Upgrade to 3DC without

interrupting services

Active-active arrays (HyperMetro)

★ Not supported by 2200 V3

★


HUAWEI ENTERPRISE ICT SOLITIONS A BETTER WAY

Arbitration server mode (recommended)

Static priority mode

HyperMetro (active-active solutions) — active-active arbitration (1)

Arbitration devices are deployed in 3rd-party sites and in

different fault domains from the DCs.

When faults such as split-brain occur, the storage arrays

apply for arbitration. The winning array continues services

while the losing one stops services. Preferred arrays enjoy

arbitration preference.

UltraPath supports preferred selection of local paths.

If arbitration devices malfunction, the mode switches to the

static priority mode after a certain period of time.

Requires no arbitration servers.

For each active-active pair, you can set the storage array

at either end as the preferred site and that on the other end

as the non-preferred site.

When a split-brain occurs or the non-preferred site

malfunctions, LUNs in the preferred site continue services

while those in the non-preferred site stop services.

However, if the preferred site becomes faulty, the non-

preferred site will not take over services and services will

then stop.

Arbitration deployment

• Arbitration device: a physical or virtual server

• Arbitration link: any link reachable by IP addresses

• Mechanism: The array winning the arbitration server survives.

Storage resource

pool

Quorum

disk 1

Arbitration device

Storage array A Storage array B


HUAWEI ENTERPRISE ICT SOLITIONS A BETTER WAY

HyperMetro (array active-active solution) — active-active arbitration (2)

No. Diagram Arbitration Result

1Fault: arbitration failure

Arbitration result: Both H1 and H2 continues running.

2Fault: link fault between H1/H2 and the arbitration device

Arbitration result: Both H1 and H2 continues running.

3Fault: H1/H2 failure

Arbitration result: H1/H2 stops running while H2/H1 continues running.

4Fault: inter-array link interruption

Arbitration result: H2 stops running while H1 (the preferred array) continues

running.

5Fault: interruption of links between H1 and H2 and between H1 and the

arbitration device

Arbitration result: H1 stops running while H2 continues running.

H1 H2

C

H1 H2

C

H1 H2

C

H1 H2

C

H1 H2

C


Сравнение SAN функционала между 2200 V3 и 2600 V3

Feature 2200 V3 Single-

Controller

2200 V3 Dual-

Controller

2600 V3 /5300 V3

HyperSnap × √ √

HyperClone × √ √

HyperCopy × √ √

HyperReplication × √ √

HyperMirror × √ √

HyperMetro × × √

SmartThin × √ √

SmartQoS √ √ √

SmartTier × √ √

SmartPartition × × √

SmartMigration × √ √

SmartVirtualization √ √ √

SmartMulti-Tenant × × √

SmartCache × √ √

SmartDedupe/Smart

Compression× × √ (sold with limitation, 2600 V3 does not

support ACC cards for deduplication

and compression)

SmartErase √ √ √

SmartMotion √ √ √

2600 V3 has similar software

features to 5300 V3.

Compared with 2600 V3, 2200

V3 (dual-controller) does not

support the following functions:

SmartCache, SmartPartition,

SmartMulti-Tenant,

SmartDedupe/SmartCompression,

and HyperMetro.

The 2600 V3 function "

SmartDedupe/SmartCompression

" is controlled by license and sold

with limitation. It can be enabled

only when a LUN is being created.

This function is mutually exclusive

with HyperSnap,

HyperReplication, HyperClone,

HyperMirror, SmartTier,

SmartMigration, SmartCache, and

SmartPartition.

2600 V3 does not support ACC

cards for deduplication and

compression.


SmartMulti-Tenant

Storage

administrator

A storage administrator manages all resources in a storage array and

all tenants.

A tenant administrator can only manage resources in its vStore.

SmartMulti-Tenant efficiently separates the

resource data of tenants and assigns the

management work of some resources to tenants

to make tenants manage resources in their own

vStores.

Working principle

Rights- and domain-based management

1. Tenant administrators can manage LUNs and

monitor LUN performance.

2. The storage administrator can allocate LUNs to

tenants, and assign and manage tenant

administrators.

Resource management

1. The storage administrator has full resource

management permission, whereas tenant

administrators can only query resources.


V3 software for NAS

CIFS NFS NDMP

Common Internet File System Network File System Network Data Management Protocol

SmartQos

Intelligent service quality control

SmartCache

Intelligent SSD cache

NAS features

SmartPartition

Intelligent cache partitioning

SmartThin

Thin provisioning

SmartQuotaQuota management

SmartCompression

Intelligent compression

SmartDedupe

Intelligent data deduplication

HyperReplication

Remote replication

HyperSnap

Snapshot

HyperLock

File system WORM


V3 file system: unified storage software architecture

OR

System

Control

Storage Pool

Object

File Semantics

File Service

(CIFS/NFS)

NAS

CacheVolume

LUN Semantics

Block Service

(FC/iSCSI)

SAN Parallel: NAS and SAN software

protocol stacks are parallel. File

systems are in ROW mode. Thin LUNs

and thick LUNs are in COW mode

adaptive to different scenarios.

Converged: NAS and SAN resources

are converged in allocation on the

management plane. Disk data blocks

are allocated based on the RAID2.0

architecture and cache resources are

shared, improving resource utilization.


Contents

1

2

3

4






Huawei EMC NETAPP IBM HP HDS DELL

2600 V3

VNX5600

VNX5400

VNX5200

VNXe3200

FAS8040

FAS8020

FAS2554

FAS2552

FAS2520

V7000 Gen2

V5000

StoreServ 8200

StoreServ 7200

VSP G200

HUS 150

HUS 130

SC8000

SC4020

2200 V3VNXe1600 V3700

V3500

EVA P6500

EVA P6300

MSA 2040

MSA1040

HUS 110

8 GB, 120 disks

EqualLogic PS6000

EqualLogic PS4000

MD3800/3400

MD3600/3200

SCv2000

OceanStor V3 Entry-level Storage Product Competitive Positioning


2200 V3: Comparison of Specifications 1 (Specifications, Ease-of-Use,

Interface Number, and Features)

Specifications OceanStor 2200 V3DELL MD3200i

/MD3220iDELL MD3600f

HP P2000 G3

MSA2040IBM V3500 IBM V3700

Controller Single/Dual Single/Dual Single/Dual Dual Dual Dual

Cache Size (per

controller)8 GB/16 GB 2 GB/4 GB 2 GB/4 GB/8 GB 2 GB/4 GB 4 GB 4 GB/8 GB

Host Port

(per controller)

4×1 Gb iSCSI + 4x8Gb FC or

4x16Gb FC or 4×1Gb iSCSI

or 4×10GE/FCOE + 8x8Gb

FC

4 x 1 Gb iSCSI 4 x 8Gb FC

2 x 8Gb FC or 2 x 8Gb FC

+ 2 x 1Gb iSCSI or 2 x

10GbE or 4 x 1Gb iSCSI；16Gb 8Gb FC,10G,1G

iSCSI, max. 4 interfaces

4 x 1Gb iSCSI

or 4 x 8Gb FC

1 Gbps iSCSI and 6

Gbps SAS,

Optional: 8G FC/6G

SAS/10GE/FCoe

Disks Quantity 300 192 19296 LFF/149 SFF

96 LFF/199 SFF12 LFF/24 SFF 120 LFF/240 SFF

Expansion Port

(per controller)2 x 12 Gbit/s SAS 4x 1 x 6 Gbit/s SAS 4x NULL

1 x 6 Gbit/s SAS 4x

Disk Type SAS, NL SAS, SSDSAS, NL SAS,

SSD

SAS, NL SAS,

SSD

SAS, SATA;

SAS, NL SAS, SSDSAS, NL SAS SAS, NL SAS, SSD

RAID Level RAID 0, 1, 3, 5, 6, 10, 50 RAID 0, 1, 10, 5, 6 RAID 0, 1, 3, 5, 6, 10, 50RAID 0, 1, 10,

5, 6RAID 0, 1, 10, 5, 6

Host ConnectionsFC interfaces: 1024

iSCSI interfaces: 25632 64 64 / 64

Data Service

Standard features: SnapShot,

LUN Copy, Thin, Replication

Smart features: Virtualization,

Cache, Tier, Motion, QOS,

Cloud features: SmartConfig

Thin provision, LUN copy(VDC),

Snapshot, remote replication, SSD

Cache, HPT, Tier

Thin provision, LUN copy,

Snapshot, remote

replication, Cache,Tier

Thin,

Flashcopy

(Snapshot),

Data migration

Thin provision,

Flashcopy, RemoteMirror,

Data migration, Easytier,

TurboPerformance


2600 V3: Comparison of Specifications 1 (Architecture, Features, and

Ease-of-Use)

Specifications OceanStor 2600 V3 NetApp FAS2500 EMC VNXe3200 DELL SC4020

Maximum Number of

Controllers8 8 2 8

All-in-one unified storage YES YES YES NO

Cache Size (per controller) 16GB/32GB 18GB 24GB 16GB

Host Port (per controller)

4×1Gb iSCSI + (4x8Gb FC or 4x16Gb

FC or 4×1Gb iSCSI or 4×10GE/FCOE

+ 8x8Gb FC)*2

8G FC, 16G FC, 10GE/FCOE,

6G SAS8G FC, 10GE 8G FC, 16G FC, 10GE

Disks Quantity 500 576 150 768

Expansion Port (per

controller)2 x 12 Gbit/s SAS 4x 2 x 6 Gbit/s SAS 4x 2 x 6 Gbit/s SAS 4x 2 x 6 Gbit/s SAS 4x

RAID Level RAID 0, 1, 3, 5, 6, 10, 50 RAID 0, 1, 5, 6, 10 RAID 1, 5, 6, 10 RAID 0, 1, 5, 6, 10

Data Service

SnapShot, LUN Copy, Thin,

Replication, Virtualization, Cache, Tier,

Motion, QOS, Partition,

SystemReportor, Multi-Tenant,

HyperMetro, HyperVault

SmartConfig

Snapshot, remote replication,

QoS, mirror, Tier

Snapshot, remote

replication, Thin, Cache,

Tier

Snapshot, remote replication,

Thin, Tier

Leading features and ease-of-use


Specific

ationsOceanStor

2600 V3EMC VNX5600 NetApp FAS8020

NetApp

FAS8040

HP StoreServ

7400HDS HUS 150 HDS G200

Dell Compellent

SC8000

Macrosan

MS5580IBM V7000 (U)

Cache

capacity per

controller

32/64GB 48GB 48GB 64GB 32-64GB 32GB 64GB 32/128GB 32-768GB 64/128GB

Number of

controllers2-8 2 2-8 2-8 2-4 2 2 2 2/4 2-8

Max. number

of disks500 500 480 720 480 960 264 960 2032 1056

Supported

frontend host

interface

types

8/16Gb FC,

1/10GE,

FCoE,

SmartIO (4

interfaces,

supporting

8/16Gb

FC/10GE and

FCoE)

8Gb FC,

1Gb iSCSI,

10Gb iSCSI,

10Gb FCoE

8/16Gb FC,

1/10Gb iSCSI,

10Gb FCoE,

UTA2 (2 interfaces,

supporting

10GbE/FCoE 16 Gb

FC)

8/16Gb FC,

1/10Gb iSCSI,

10Gb FCoE,

UTA2 (2

interfaces,

supporting

10GbE/FCoE 16

Gb FC)

8Gb FC,

10Gb iSCSI,

8Gb FC,10Gb

iSCSI

8/16Gb FC,10Gb

iSCSI

8/16Gb FC,

1/10Gb iSCSI,

10Gb FCoE

8/16Gb FC,

1Gb iSCSI,

10Gb iSCSI,

10Gb FCoE

8/16Gb FC,

1Gb iSCSI,

10Gb iSCSI,

10Gb FCoE

Max. number

of host

interfaces

(every two

controllers)

8Gb FC: 32

16Gb FC: 16

GE : 24

10GE/FCoE: 16

FC: 40

1/10GE: 16

10GE FCoE: 20

8Gb FC: 20

16Gb FC: 12

10GE: 16

GE : 20

10GE FCoE: 12

8Gb FC: 40

16Gb FC: 24

10GE: 32

GE : 40

10GE FCoE: 24

FC: 24

10GE: 8

8Gb FC: 16

10GE: 8

8Gb FC: 8+10GE:

8

8Gb FC:

16

10GE: 8

16Gb FC: 8GE: 8

8/16Gb FC: 32

1/10GE: 20

10GE FCoE: 20

32

8Gb FC: 16

16Gb FC: 16

GE : 6

10GE/FCoE: 8

Disk interface

type12Gb SAS 6Gb SAS

6Gb/12Gb SAS

8Gb FC

6Gb/12Gb SAS

8Gb FC6Gb SAS 6Gb SAS 12Gb SAS

3/6Gb SAS

2/4/8Gb FC6Gb SAS 6Gb SAS

Supported

disk types

SAS/SSD/NL

SASSAS/NL-SAS/SSD SSD/SAS/FC/SATA

SSD/SAS/FC/S

ATA SSD/SAS/NL-SAS SAS/NL-SAS/SSD SAS/NL-SAS/SSD SAS/FC/SATA SSD/SAS/SATA SSD/SAS/NLSAS

2600 V3: Comparison of Specifications 2 (Hardware Specifications)


Contents

1

2

3

4






Quotation Elements of V3 Entry-level Storage Products

集群NAS引擎

其组件

存储单元

Interface card/optical fiber/Mini SAS cable

Specifications (AC/DC, cache size)

Disk unit (SAS/NL SAS/SSD)

Disk enclosure

Modem/cabinet/switch

Interface card

and cable

Controller

enclosure

Storage unit

Mapping devices

(optional)

Value-added

software

Value added storage features (mandatory for the

block basic package, and optional for others)


Select value-added

functions.

Select the hardware type and input the number.

Select the disk enclosure type and input the number (standard configuration: two 1m SAS cables).

Select the interface card type and input the number (in unit of pairs).

Select a controller enclosure type (2.5 or 3.5，16GB or 32GB) and input the number.

Select the optical fiber type and input the number.

Configure the

controller enclosure.

Configure disks.

Configure the

disk enclosure.

Configure the

interface card.

Configure optical

fibers and cables.

Select the value-added functions and input the number

(the number of block storage basic software packages is not configurable

and must be configured during the configuration of the controller enclosure.)

OceanStor 2200 V3 Configuration Procedure

Select a product model in Unistar. (Green means optional.)


OceanStor 2600 V3 Product Configuration Procedure

Select the frontend

extended I/O module.

Select the backend

extended I/O module.

Select the disk

types and number.

Configure the array

unit one by one.

The system automatically configures the number of disk enclosures when a user configures the number of disks.

Only two controller enclosures can be directly connected, but if switches are connected, multiple controller enclosures can form a large network.

Controller enclosures of 2200 and 2600 that support AC can adaptively support high voltage DC (not in North America).

Select SAN or SAN+NAS.

Set the controller enclosures to be directly connected

or the switches to be connected.

Select a product model in Unistar.

Basic

configurations

(Green means optional.)

Select the controller

enclosure type (2,4,8).

Select the

networking type.

Select the optical fiber type and input the number.Configure optical

fibers and cables.

Select value-added

functions.

Notes:

Select the value-added functions and input the number

(the number of block storage basic software packages is not configurable

and must be configured during the configuration of the controller enclosure.)

Select the power model (AC/DC). Select SAN or SAN+NAS.


Configuration Item Configuration and Quotation

4*SmartIO I/O module (SFP+, 10Gb ETH) Optional (recommended), sold and configured in pairs

Supporting FcoE on 10GE and VN2VF interfaces

4*SmartIO I/O module (SFP+, 8Gb FC) Optional (recommended), sold and configured in pairs

4*SmartIO I/O module (SFP+, 16Gb FC) Optional (recommended), sold and configured in pairs

4*1Gbps Ethernet I/O module Optional, sold and configured in pairs

4*8Gbps Fibre Channel I/O module (4 ports) In the active-active scenario, if the distance between two sites is over 25 km and the

sites are connected through FC, it is advised to use common 4*8Gb FC modules

(non-Smart I/O module), because FC protocol optimization is supported to achieve

better transmission performance between remote arrays. If it is used on a host

interface connected to a server, the effect is the same as that of a Smart I/O module.

8*8Gb FC I/O module (QSFP+) Optional. High-density cards use QSFP+ interfaces. Each controller supports a

maximum of two cards.

Some customers may not accept the form. Be sure to communicate with customers in

advance. For details about the form, see the technical white paper.

4 ports 10Gb Eth I/O module (RJ45) Optional, sold and configured in pairs

Notes about Selecting OceanStor V3 Entry-level Storage Interface

Cards


Software and Value-added Functions Configuration and Quotation

Basic

software

package

2200 V3: Device Management, HyperSnap, HyperCopy, SmartThin, SmartMotion,

SmartErase, SmartConfig, SystemReporter, Ultrapath

2600 V3: Device Management, SmartThin, SmartMultiTenant, SmartMigration, Sma

rtErase, SmartMotion, SmartConfig, Ultrapath, SystemReporter, CloudService

Required for SAN

Basic software package for upgrading block storage to unified storage:

SmartDedupe&SmartCompression(for Files), NFS, CIFS, NDMP, SmartQuota)

Automatically configured during upgrading of SAN

to unified storage or SAN+NAS

FileCIFS (Internet file system), NFS (network file system), NDMP (network data

management protocol), SmartQuota

HyperLock (WORM), HyperVault

File engine software quotation:

1. Select the file functions (the functions in red

are included in the basic software package.

2. Select other NAS value-added functions as

required.

Block

HyperCopy, HyperClone, HyperMirror, HyperSnap, HyperReplication,

HyperMetroOptional value-added functions

SmartCache, SmartQos, SmartPartition, SmartDedup & SmartCompression,

SmartTier, SmartVirtualizationOptional value-added functions

OceanStor multipathing software licenseMandatory. Contained in the basic software

package.

Cloud Service remote maintenance and management Optional value-added functions

• The features in bold blue are supported by both SAN and NAS.

Configuration and Quotation of Software and Value-added Functions


Optical module:

8G FC, FCoE, 10GE, and 16G FC interface cards are already configured with optical modules and do not require extra ones.

Installation Materials and Auxiliary Devices

Installation Materials Configuration and Quotation

Optical fiberAutomatically configured according to the number of fiber ports on the host of 2600 V3. The

default length is 3m. Users can select more if necessary.

High Speed Cable,Mini SAS HD Cable,3m,(SFF 8644

plug),(28AWG*4P*2B(S)),(SFF 8644 Plug),Indoor use

By default, each disk enclosure is configured with two 1m SAS cable. Users can select more if

necessary. The maximum cable length between a controller enclosure and a disk enclosure is

3m, while that between disk enclosures is 15m. To prevent wrong configurations, the items of 5m

and 15m cables are unavailable in the quoter. You can select 5m and 15m cables from the

quoter of other V3 products.

Configuration and Quotation

MODEM(Wireless GPRS,48Kbps,Radio Interface) Optional. Configured according to customer requirements.

MODEM(56Kbps,2 Wire Dedicated Wire/Data/Fax,External Type) Optional. Configured according to customer requirements.

Cabinet Configuration and Quotation

46U AC cabinet/ 46U DC cabinet/ 42U AC cabinet Optional. Configured according to customer requirements.

Input power cable (such as power cable and ground cable)

The length is automatically configured during cabinet selection and the number can be

configured as required. (The IT product line requires to streamline configurations and set major

cables as quotation items to ensure delivery quality.)

Cabinet installation suite (such as the cabinet door)Automatically configured during cabinet selection. (The IT product line requires to streamline

configurations and set major auxiliary devices as quotation items to ensure delivery quality.)

www.huawei.com

Copyright © Huawei Technologies Co., Ltd. 2016. All rights reserved.

All logos and images displayed in this document are the sole property of their respective copyright holders. No endorsement, partnership, or affiliation is suggested or implied. The

information in this document may contain predictive statements including, without limitation, statements regarding the future financial and operating results, future product portfolio,

new technology, etc. There are a number of factors that could cause actual results and developments to differ materially from those expressed or implied in the predictive

statements. Therefore, such information is provided for reference purpose only and constitutes neither an offer nor an acceptance. Huawei may change the information at any time

without notice.

huawei oceanstor 2000 v3 -...

Documents