Product Description - Huawei · A.1.2 Preparing for Commissioning ... All smart disks in a UDS system are interconnected to form a distributed node cluster ... Product Description

HUAWEI OceanStor UDS Massive Storage System

V100R002C01

Product Description

Issue 01

Date 2014-05-09

HUAWEI TECHNOLOGIES CO., LTD.

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

No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

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. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase 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 representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute a warranty of any kind, express or implied.

Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://enterprise.huawei.com

Issue 01 (2014-05-09) Huawei Proprietary and ConfidentialCopyright © Huawei Technologies Co., Ltd.

i

http://enterprise.huawei.com

About This Document

OverviewThis document describes the market positioning, product highlights, system networking,hardware components, software structure, system interfaces, technical specifications, standardsand certifications of HUAWEI OceanStor UDS massive storage system (UDS for short).

Intended AudienceThis document is intended for:

l Network planning engineersl Data configuration engineersl System deployment engineersl Routine maintenance engineers

Symbol ConventionsThe symbols that may be found in this document are defined as follows.

Symbol Description

DANGERIndicates an imminently hazardous situation which, if notavoided, will result in death or serious injury.

WARNINGIndicates a potentially hazardous situation which, if notavoided, could result in death or serious injury.

Indicates a potentially hazardous situation which, if notavoided, may result in minor or moderate injury.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description About This Document


ii

Symbol Description

Indicates a potentially hazardous situation which, if notavoided, could result in equipment damage, data loss,performance deterioration, or unanticipated results.NOTICE is used to address practices not related to personalinjury.

NOTE Calls attention to important information, best practices andtips.NOTE is used to address information not related to personalinjury, equipment damage, and environment deterioration.

Change HistoryChanges between document issues are cumulative. The latest document issue contains all thechanges made in earlier issues.

Issue 01 (2014-05-09)This issue is the first official release.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description About This Document


iii

Contents

About This Document.....................................................................................................................ii

1 Product Introduction.....................................................................................................................11.1 Market Positioning.........................................................................................................................................................21.2 Product Highlights..........................................................................................................................................................21.2.1 Flexible Scalability......................................................................................................................................................31.2.2 Solid Reliability...........................................................................................................................................................51.2.3 Easy Maintainability....................................................................................................................................................81.2.4 Diversified Security Protection Mechanisms..............................................................................................................91.2.5 Cost-Effective Deployment and Operation...............................................................................................................151.2.6 Open APIs..................................................................................................................................................................151.2.7 MDC..........................................................................................................................................................................151.2.8 Erasure Code..............................................................................................................................................................161.2.9 Deduplication.............................................................................................................................................................191.2.10 Data Compression....................................................................................................................................................211.2.11 License-based Features............................................................................................................................................221.3 Hardware Configuration Rules.....................................................................................................................................221.4 System Networking......................................................................................................................................................23

2 Product Structure.........................................................................................................................282.1 Hardware Components.................................................................................................................................................292.1.1 Cabinet.......................................................................................................................................................................292.1.2 A-Node......................................................................................................................................................................312.1.3 UDSN........................................................................................................................................................................382.1.4 SMS Modem..............................................................................................................................................................482.1.5 Access Switch............................................................................................................................................................492.2 Software Structure........................................................................................................................................................522.2.1 Logical Structure.......................................................................................................................................................532.2.2 Service Layer.............................................................................................................................................................532.2.3 Storage Layer.............................................................................................................................................................542.2.4 O&M Layer...............................................................................................................................................................55

3 System Interfaces.........................................................................................................................573.1 Physical Ports...............................................................................................................................................................58

HUAWEI OceanStor UDS Massive Storage SystemProduct Description Contents


iv

3.2 APIs..............................................................................................................................................................................60

4 Technical Specifications.............................................................................................................634.1 System Specifications...................................................................................................................................................644.2 Hardware Specifications...............................................................................................................................................644.3 Environmental Requirements.......................................................................................................................................69

5 Standards and Certifications.....................................................................................................755.1 Standards Compliance..................................................................................................................................................765.2 Certifications................................................................................................................................................................79

A How to Obtain Help...................................................................................................................84A.1 Preparations for Contacting Huawei............................................................................................................................85A.1.1 Collecting Fault Information....................................................................................................................................85A.1.2 Preparing for Commissioning...................................................................................................................................85A.2 How to Use the Document...........................................................................................................................................85A.3 How to Obtain Help from the Website........................................................................................................................85A.4 Ways to Contact Huawei.............................................................................................................................................86

B Glossary........................................................................................................................................87B.1 A-E...............................................................................................................................................................................88B.2 F-J................................................................................................................................................................................89B.3 K-O..............................................................................................................................................................................89B.4 P-T................................................................................................................................................................................91B.5 U-Z...............................................................................................................................................................................92

HUAWEI OceanStor UDS Massive Storage SystemProduct Description Contents


v

1 Product Introduction

About This Chapter

This chapter describes the market positioning, product highlights, hardware configuration rules,and system networking of the UDS.

1.1 Market PositioningThis section describes the market positioning and application scenarios for the UDS.

1.2 Product HighlightsThis section describes the highlights of the UDS in terms of flexible scalability, solid reliability,easy maintainability, diversified security protection mechanisms, cost-effective deployment andoperation, open APIs, MDC, erasure code, deduplication and data compression.

1.3 Hardware Configuration RulesThis section provides the UDS hardware configuration rules to give users a glimpse of thedeployment methods of the UDS devices in cabinets.

1.4 System NetworkingThis section describes the UDS network structure and planes.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description 1 Product Introduction


1

1.1 Market PositioningThis section describes the market positioning and application scenarios for the UDS.

The UDS is a massive object storage platform based on the Advanced RISC Machines (ARM)architecture of high-density and energy-efficient universal distributed storage nodes (UDSNs).It incorporates advanced technologies such as object storage, distributed storage engines, andclustering, and offers storage and sharing services for various types of data. The UDS alsosupports multiple cloud storage solutions by delivering services including web disk, cloudbackup, space lease, nearline data warehousing, and unified backup.

The UDS fits into the following scenarios:l Application scenarios of enterprise users: massive storage resource pool, online storage,

online backup, centralized backup, and active archivel Application scenarios of individual users: online storage and backup

Figure 1-1 shows the application scenarios of the UDS.

Figure 1-1 Application scenarios of the UDS

Centralized backup

Massive storage

resource pool

UDS

Online storage

Individual user

WAN

Enterprise user

Cross-region interconnection

Third-party services

Access/Backup gateway

Active archive

Online backup

1.2 Product HighlightsThis section describes the highlights of the UDS in terms of flexible scalability, solid reliability,easy maintainability, diversified security protection mechanisms, cost-effective deployment andoperation, open APIs, MDC, erasure code, deduplication and data compression.



2

1.2.1 Flexible ScalabilityTo meet these demanding requirements, the UDS employs the scale-out storage architecture andDistributed Hash Table (DHT) technology to achieve storage capacity expansion with linearperformance improvement.

l On-demand deployment and flexible expansion

– The distributed hash algorithm removes all central points on object access paths,eliminating data layout bottlenecks and leading to logically unlimited expansion.

– The UDS supports smooth expansion from tens of TB to hundreds of PB, that is, froma minimally configured cabinet housing 75 smart disks to multiple data centers (MDC)with tens of thousands of smart disks.

– Flexible expansion solutions are available. The UDS can be expanded by smart disk,UDSN, cabinet, and data center to meet various expansion requirements.

l Linear performance increase with capacityIn the traditional x86 architecture, multiple disks rely on one x86 CPU. Capacity andperformance therefore increase in an unbalanced way. When capacity increases to a certainlevel, performance remains unchanged. In the smart disk interconnection architecture, eachdisk has a dedicated CPU and connects to an IP switched network as an independent storageunit. All smart disks in a UDS system are interconnected to form a distributed node clusterwhose performance, including bandwidth, operations per second, and concurrentconnections, increases with capacity.

With the flexible scalability feature, the UDS supports on-demand expansion. If expansion isrequired, purchase an expansion license.

Application ScenarioThe flexible scalability applies to the following scenarios:l Deploying massive resource pools that support on-demand capacity expansion and

performance improvementl Expanding an existing UDS to support rapid service development

PrincipleThe UDS consists of an access cluster and a storage cluster. Multiple A-Nodes form the accesscluster, and massive smart disks in universal distributed storage nodes (UDSNs) make up thestorage cluster. Service workload is balanced among nodes in the access cluster, and data isbalanced among those in the storage cluster.

Figure 1-2 shows the UDS scale-out storage architecture.



3

Figure 1-2 Scale-out storage architecture

…...

…...

Object-based storage API

Access cluster

Storage cluster

Access service flow

LBS

A-Node 1

A-Node 2

A-Node 3 A-Node 4

A-Node 5

Smart disk 1

Smart disk 2

Smart disk 3Smart disk 4

Smart disk 5

Smart disk 6

Object-based storageAPI

A set of standard network application programming interfaces (APIs) that providethe object-based storage service (OBS). The object storage service APIs allow usersanywhere to obtain mass data using storage terminals that comply with standards.

LBS Load balancing subsystem (LBS). The LBS balances services and data among nodes.

Access cluster A-Nodes. An A-Node is a computing server dedicated to the UDS. It can be deployedas an object storage service controller (OSC), provisioning orchestration engine(POE), operation and maintenance service (OMS), or storage cluster controller.



4

Storage cluster Smart disks. A smart disk consists of hardware and software. The hardware includesa disk sheet, power-saving CPU, small memory, and network adapter. The softwareprovides key-value storage interfaces for external applications. A smart diskfunctions as an independent storage unit, and can be added onto an IP switchingnetwork to form a distributed storage cluster.

The working process of the scale-out storage architecture is as follows:

1. Mass data is scattered to multiple concurrent A-Nodes for processing and stored to multipleUDSNs to achieve load balancing.

2. A-Nodes and UDSNs can be added to enhance system performance. The recommendedproportion of A-Nodes to UDSNs after the expansion is 1:2 and the proportion of A-Nodesand to smart disks is 1:150.

3. Point-to-point access is implemented between A-Nodes and smart disks to eliminate theadverse impact of capacity expansion on system performance.

4. The UDS intelligently identifies newly added UDSNs and smart disks, and adds their spaceto the storage system.

5. After new UDSNs and smart disks are added, the UDS automatically migrates someservices and data to newly-added nodes according to load balancing rules.

The UDS scale-out storage architecture adopts the DHT technology to use massive smart disksto form a distributed storage cluster, which can be expanded on demand.

1.2.2 Solid ReliabilityBased on reliable software and hardware architecture, the UDS functions as a trustworthymassive storage system for service operators, enterprises, and end users. With the UDS,customers can easily cope with the challenges brought by the explosive growth of data.

The solid reliability feature applies but is not limited to the following scenarios:

l Service operators and enterprise users

Massive storage resource pool, online storage, online backup, centralized backup, andactive archiving

l Individual users

Online storage and online backup

Highly Reliable Hardware Architecture

Redundancy of key components

l Deployment of multiple data centers.

l Redundancy of the OMS on A-Nodes, enabling in-service switchovers between active andstandby OMSs. When the active OMS fails, the standby OMS takes over services from theactive OMS to ensure business continuity.

l Redundancy of key components on A-Nodes and UDSNs, enabling hot swap.

Table 1-1 provides details about the UDS hardware component redundancy.



5

Table 1-1 Component redundancy

Component Redundancy Mode

Power module l On A-Node: 1+1l On UDSN: 2+2

Fan module l On A-Node: 1+1l On UDSN: 11+1

UDSN switch board 1+1

Redundancy of network pathsl A-Nodes and UDSNs are connected in a redundant connection mode to two access switches,

which are configured to work in stack mode or VRRP active-standby mode. The failure ofa single network path does not interrupt services.

l 10GE ports of A-Nodes and UDSNs are bonded to achieve redundancy.l Smart disks on one UDSN are connected to each other through switch boards deployed in

1+1 redundancy mode.

Shockproof disks

The primary cause of disk failures is shock. The UDS adopts a shockproof design to ensure diskreliability.l Disk handles are made of shock absorption materials and adopt a buffer design. The design

slows down insertion and removal of disks, reducing the impact of shock and vibration.l Fan modules are fastened by rubber screws, reducing low-frequency vibration.l UDSN guide rails adopt a damping design. The design slows down the pull and push of

UDSNs, reducing shock.

Temperature control

Based on real-time temperature statistics, the UDS adjusts the cooling system working mode tokeep the working temperature within the normal range. If the working temperature grows beyondthe normal range, the UDS decreases the working frequency and service load of the overheatedcomponents. If the working temperature reaches the preset threshold, the UDS resets or powersoff overheated components to prevent component damage.

Highly Reliable Software ArchitectureRedundancy of key software modules

Key software modules such as the OSC, OMS, Network Time Protocol (NTP), domain nameservice (DNS), and storage cluster controllers work in High Availability (HA) redundancy mode,delivering reliable system management and service processing.

Diversified data reliability protection mechanismsl Data consistency

The UDS supports end-to-end data consistency verification. The UDS uses protocols withverification mechanisms, such as TCP/IP, and HTTPS for data transmission to ensure thatdata received by the UDS and sent to users is correct. On the OSC, the message digest



6

algorithm 5 (MD5) is used to implement object-level data verification. In the UDS, eachdata fragment is verified by the storage cluster. After data fragments and their parity dataare written to disks, disk sectors are verified.

l Data integrity

The UDS provides a comprehensive mechanism to protect data integrity. It supports datarecovery at four levels: sector level, fragment level (Erasure Code must be enabled), objectlevel, and data center level (multiple data centers are required).

When detecting data damage, the UDS implements sector-level data recovery using theparity data on the local sector. If the Erasure Code is enabled, the UDS implementsfragment-level data recovery by reading intact data in fragments. If fragment-level datarecovery fails, the UDS implements object-level data recovery using other fragments in thecluster. If all the previously described types of recovery fail, the UDS implements datacenter-level data recovery using backup data from the standby data center.

l Data security

The UDS offers diversified data protection mechanisms to ensure data security. For details,see Diversified Data Security Protection Mechanisms.

Fault self-healing

l Automatic fault detection

The UDS monitors hardware and software modules in real time, and automatically detectsdevice faults, service anomalies, and communication interruptions. If a preset threshold isexceeded, an alarm is reported in real time.

l Automatic creation of duplicates

If a disk on a UDSN fails, the UDS's response varies according to its storage mode. In tri-duplicate storage mode, the UDS automatically copies a replicate of data on the faulty diskfrom other disks. In Erasure Code storage mode, the UDS automatically generates areplicate of data on the faulty disk through calculation. Then the UDS stores the recovereddata on a normal disk.

l Data recovery acceleration

If a disk on a UDSN fails, the UDS recovers data from multiple disks concurrently,accelerating data recovery and minimizing the risk of data loss.

Disk reliability

l Periodic disk scan

In tri-duplicate storage mode, the UDS periodically verifies consistency of duplicates andrectifies inconsistency problems (if detected).

In Erasure Code storage mode, the UDS periodically scans all objects, and reads data blocksand parity blocks. When detecting that a block in an object data block group is lost, theUDS reads other data blocks from the object data block group and uses the Erasure Codealgorithm to recover the lost data. Then the UDS writes the recovered data again.

l Disk health status monitoring

The UDS employs the industry-leading Self-Monitoring Analysis and Reporting (SMART)technology to analyze the health status of disk motors, circuits, sheets, and heads. If ananomaly is detected, an alarm is reported and the disk rotational speed automatically slowsdown. In addition, data is backed up immediately upon the alarm to prevent data loss.

l Slow disk detection



7

Slow disks refer to failing disks whose read and write performance deteriorates severelydue to long service time. The UDS collects statistics about the average data response timewithin a specific period, and compares the average data response time with the standarddata response time. If the average data response time of a disk is much longer than thestandard data response time, the disk is considered to be a slow disk. An alarm is reportedand data rebalancing is enabled based on site requirements.

Human error prevention

To prevent data loss or system faults caused by misoperation, the UDS adopts a comprehensivehuman error prevention and recovery rollback mechanism.

l When users attempt to change key configuration information, the UDS prompts users toconfirm the change and informs them of the risks and consequences, preventingconfiguration information from being tampered with.

l The UDS verifies the validity of parameter settings. If invalid parameter values exist, theUDS reports an error and switches to the original parameter values.

1.2.3 Easy MaintainabilityBy providing a management graphical user interfaces (GUI) and functions of batch diskreplacement, online upgrade, and online expansion, the UDS offers enhanced self managementcapability, simplifying management and maintenance (O&M).

The easy maintainability feature applies but is not limited to the following scenarios:

l Service operators and enterprise usersMassive storage resource pool, online storage, online backup, centralized backup, andactive archiving

l Individual usersOnline storage and online backup

GUI

The HUAWEI OceanStor DeviceManager (DeviceManager for short) is used for systemconfiguration, performance monitoring, alarm monitoring, user management, and license filemanagement. Supporting alarm notification by short message (SM) and email, theDeviceManager helps users to handle alarms in a timely manner in order to keep the systemhealthy. In addition, the DeviceManager allows users to perform online upgrades and onlineexpansion, simplifying operations and ensuring reliability.

Batch Disk Replacement

When a smart disk is faulty or a new smart disk is added, the UDS automatically migrates datafrom the faulty disk to the other disks or from existing disks to the newly added disk to balanceload among the smart disks, balance service I/O and ensure service availability. Therefore, beforethe number of failed disks reaches the preset threshold, system service is not affected and usersdo not need to take maintenance measures. This avoids immediate maintenance upon a singledisk failure, reduces the number of spare parts needed on hand, shortens the update period, andminimizes the involvement of maintenance personnel.

When the number of failed disks reaches the preset threshold, an alarm is generated to promptusers to replace failed disks at one time. After automatically adding the storage space of the new



8

disks to the storage cluster, the UDS uses the intelligent data rebalancing technology toredistribute data evenly among disks.

Online UpgradeThe UDS automatically identifies software and firmware that need to be upgraded, and upgradesthem without interrupting ongoing services. Moreover, the UDS supports pre-upgrade healthstatus analysis and post-upgrade verification. If errors occur during an upgrade, the systemautomatically rolls back to the source version.l Intelligent component upgrade

The online upgrade package contains upgrade files for multiple components. The UDS onlyupgrades the components whose versions are inconsistent with those specified in theupgrade files. If errors occur during an upgrade, the UDS intelligently adjusts the upgradepolicy and rolls back the involved components to the source version.

l Automatic version synchronizationWhen detecting version inconsistency between components, the UDS automaticallysynchronizes the versions of these components.

Online ExpansionThe scale-out architecture of the UDS supports flexible expansion of A-Nodes, UDSNs, andsmart disks, meeting the increasing demands for performance and capacity. The expansion canbe implemented without interrupting ongoing services.

During the expansion, the expansion script adds new devices to the UDS automatically. Afterexpansion, the UDS uses the intelligent data rebalancing technology to redistribute data andachieve balance between UDSNs and between A-Nodes.

1.2.4 Diversified Security Protection MechanismsThe UDS employs diversified mechanisms to protect data security across networks,infrastructure, transfers, storage, access, and management.

The UDS adopts diversified mechanisms to ensure the security of networks, infrastructure, andmanagement, as shown in Figure 1-3. Data security covers the processes of data transfer, storage,access and destruction.



9

Figure 1-3 Application of diversified security protection mechanisms

ACL, permission control, security access policy

HTTPS

Transfer security

Operating system security, database reinforcement, security patches

Web security, isolated network planes, Communication ports open with security measures

Management of logs, permission, and internal accounts’ passwords

Storage security

Access security

Destructionsecurity

Fragmentation, user data

isolation, data encryption before transfer, AES-256

encryption

Fragmentation

Infrastructure security

Managementsecurity

Network security

Network SecurityWeb securityl HTTPS is used for portal login, ensuring the safety of data transmission paths.l System administrator accounts are guarded against brute-force cracking attacks. An image

verification code containing digits and non-numeric characters is required at the time ofthe login. An account is locked if login fails after several attempts.

l The latest security patches are installed on the web server to strengthen system safety.

Network plane isolation

The UDS consists of at most four network planes: management plane, service plane, storageplane, and multiple data centers (MDC) replication plane. The virtual local area networks(VLANs) are configured to isolate network planes, enhancing system security.l Management plane: supports system management and maintenance. On this plane,

administrators and technical support engineers perform routine management andmaintenance, and obtain charging information.

l Service plane: provides A-Nodes with object storage service API for service access.l Storage plane: manages and transfers data among all nodes in the UDS.l (Optional) MDC replication plane: supports data replication among data centers. This plane

is configured only when multiple data centers are deployed.

NOTE

To ensure network security, the UDS also supports other network isolation schemes, such as Virtual PrivateNetwork (VPN) and Access Control List (ACL). You are advised to configure VPN or ACL on theaggregation switches to isolate the network planes.



10

Communication ports open with security measures

The UDS provides communication ports required for implementing system functions andeliminating security risks caused by unknown ports. For details about communication ports, seethe HUAWEI OceanStor UDS Massive Storage System V100R002C01 CommunicationMatrix.

Infrastructure Security

Operating system security

To ensure device security, the UDS operating system is configured as follows:

l Operating system account and password

Unnecessary users and user groups are deleted. The complexity and length of passwordsmust comply with specific requirements.

l System service

Insecure services such as Telnet and Network File System (NFS) are disabled. Needlessand dangerous background processes and services are also disabled. Services can run onlyby using accounts that are granted specific permissions. Security protocols, such as SecureShell (SSH) V2, Secure File Transfer Protocol (SFTP), and Simple Network ManagementProtocol (SNMP) V3, are used.

l Operating system kernel

Execution stacks are protected against buffer overflow attacks. Functions such as IP addressforwarding, response to broadcast requests, and Internet Control Messages Protocol(ICMP) redirection requests receiving are disabled. IP spoofing prevention is enabled, andsocket sequences are guarded against attacks.

l File and folder permission

The permissions for files and folders are strictly controlled.

Database reinforcement

The UDS takes the following measures to reinforce its databases:

l Restricts the listener's listening address on the host with multiple IP addresses and changesthe standard listening port.

l According to the least privilege policy, permission is assigned by user group.

Security patches

Security patches can prevent virus attacks and hacker invasion. The UDS has the latest securitypatches installed before delivery and periodically receives newly released security patches.

Transfer Security

The UDS supports data transfer over HTTPS. If users use client software or web pages to transferdata, the UDS allows data transfer over HTTPS to prevent data from being damaged duringtransfer.

Figure 1-4 uses HTTPS access as an example to describe the technical principles of the datatransfer security technology.



11

Figure 1-4 Technical principles of the data transfer security technology

HTTPS1

3

4

2

1. A client sends a request for accessing an HTTPS resource.2. A unique session key is generated at the client site. The public key generated by the server

certificate is used to encrypt the session key, and then the session key is transferred to theserver.

3. After receiving the session key, the server uses its own private key to decrypt it.4. The connection is set up. The client can communicate with the server in secure mode.

Storage SecurityThe UDS uses diversified storage security technologies to ensure data security.l Fragmentation

After fragmentation, object data is stored on smart disks of different UDSNs randomlybased on the distributed hash algorithm. Unauthorized users cannot obtain complete datafrom a single UDSN or smart disk. After the lifecycle of a service ends or a service isterminated by users, the fragmentation technology implements data destruction in securitymode to prevent data leakage.

l User data isolationEach user has independent logical space and storage policies. In this way, any user's datais completely isolated from that of others. Data isolation ensures data security and privacy.

l Data encryption before transferIf client software is used to upload data to the UDS, users can encrypt data before transferto prevent data theft. Key authentication information, such as login passwords and accessrecords, is encrypted and stored in cookies. In this way, unauthorized users cannot obtainkey authentication information by analyzing the cookies. This protects data security.

l Sensitive user data encryptionBefore storage, the Advanced Encryption Standard (AES)-256 algorithm is used to encryptsensitive data and private data, such as authentication and email information.

Figure 1-5 describes the technical principles of the data storage security technologies.



12

Figure 1-5 Technical principles of the data storage security technologies

Object

D1

D2

D3

Dm

…

Space for user 1

Fragmentation User data isolation

Space for user 2

Space for user 3

…

Sensitive data encryption

Access Security

The UDS supports access data isolation, user permission control, and user-definable accesspolicies. These functions ensure user authentication security and controls access to resources.

Access data isolation

The UDS isolates data by account or bucket to prevent unauthorized accounts from accessingdata, ensuring data privacy.

l Account-specific data isolation

The UDS creates independent storage space for each account. Data access by each accountis controlled based on account identity and permission, preventing unauthorized accountsfrom accessing account data and account information.

l Bucket-specific data isolation

The UDS adopts an object storage mechanism, that is, each object must be stored in aspecific bucket. A bucket is the basic unit of object storage. The license code and signingkey are necessary for a user to access a bucket. Different buckets have different accesspermissions. To share resources, a resource owner can authorize other users who havelicense codes to access its resources.

User-definable access policies

Accounts can configure access policies based on access key IDs (AKs) and access IP addressesto enhance data access security. In a specific statistical period, if the number of access failuresof an AK, IP address, or AKs of one IP address exceeds the preset threshold, and the ratio ofaccess failures to legitimate access attempts exceeds the preset threshold, access is denied.

Security authentication

l Every request for accessing a bucket or object requires signature authentication.



13

l After signature authentication succeeds, bucket- and object-based access control list (ACL)authentication is performed. Only authenticated users can access their buckets and objects.

l The UDS provides AK-based account access authentication. In a specific statistical period,if an AK fails to access the IAM or the account management service using the RESTinterface for several consecutive times and the times reach a threshold, services to the AKis denied. In the current UDS version, this threshold is not user-configurable. By default,if an AK fails to be authenticated for five consecutive times within 3 minutes, it cannotaccess the UDS Account Management or the IAM service in the next 3 minutes.

Management Security

Operation logs management

The UDS supports centralized collection and storage of operation logs. The UDS usually storesoperation logs locally. Users can export and view operation logs on the DeviceManager, and login to the node to obtain the run log and operation log of the node. These logs help users learnthe system operating status, locate risky or malicious operations, and handle anomalies.

Password management

l Password change

The UDS supports batch password changes and can regularly and automatically changepart of the machine-machine password. The UDS can also automatically verify passwordcomplexity. Only the super administrator or the account administrator has the permissionto change passwords. For details about the changing passwords, see the HUAWEIOceanStor UDS Massive Storage System V100R002C01 Account List. This document canbe obtained from Huawei technical support engineers.

l Encryption for transfer and storage

After the password of an account is changed, the new password is encrypted and transferredto service nodes where the account passwords are encrypted before storage.

l Operation logs

All operations performed on passwords are recorded in logs. Those logs help users locatefaults and implement audits.

Permission management

The UDS provides role- and permission- specific permission management. In role-specificmanagement mode, the role of a user determines the permission of the user. If the permissionsof a user need to be changed based on site requirements, a different role can be assigned to theuser. By default, the UDS supports three administrator roles by default: super administrator,system administrator, and system viewer. The system administrator can create administratorsand assign different permissions to them, implementing flexible permission control. Differentadministrator roles have different management permission:

l Super administrator: a privileged user who has full management permissions. The superadministrator manages the whole system, and creates and manages other administrators.

l System administrator: a user who has the permission to operate alarms and logs and performroutine maintenance. This role is usually assigned to system maintenance personnel.

l System viewer: a user who can only view system information. This role is usually assignedto restricted system administrators.



14

l User-definable administrator: a system administrator created by the super administratorbased on site requirements. The super administrator assigns operation permissions to suchadministrators.

1.2.5 Cost-Effective Deployment and OperationThe UDS employs a hardware and software integrated architecture and offers energy-efficienthardware to reduce deployment cost and system power consumption.

l Low-power and high-density hardware architectureUDSNs use energy-efficient CPUs and high-density storage enclosures, improvingcomputing performance while reducing system power consumption.

l Energy-efficient system designThe energy-efficient system architecture intelligently lowers CPU frequency and fan speedand spins down disks when system load decreases, reducing energy consumption and,overall, its environmental footprint.

l Integrated platformThe hardware and software integrated platform provides Platform as a Service (PaaS)without the need to deploy extra hardware or software, minimizing deployment cost.

1.2.6 Open APIsThe UDS provides diversified standard APIs for users to integrate existing applications andconduct secondary development.

l Object storage service APIThe mainstream Representation State Transfer (REST) API enables the UDS tointerconnect with various applications and clients and store various types of data, includingimages, videos, audio, and files.

l Operation and maintenance APIThe portal-based operation and maintenance API allows maintenance personnel to performroutine maintenance on the UDS using a web-based management system.

l External operation APIs

The UDS provides external operation APIs including billing APIs (SFTP), accountmanagement APIs (REST), IAM APIs (REST), and OMS northbound maintenance APIsthat are compatible with REST and SNMP.

1.2.7 MDCThe UDS delivers the Multiple Data Centers (MDC) feature to increase disaster recoveryreliability by deploying a range of data centers across regions.

MDC supports two bucket-specific modes: replication mode and region mode. You can selecteither mode based on your requirements to enable data replication or unified resourcemanagement among MDC.

Service providers, enterprises, and individual users can benefit greatly from the MDC feature.

MDC allows service providers and enterprises to enlarge storage system capacity while boostingdata reliability by implementing data replication and isolation among MDC.



15

The MDC feature applies to two scenarios: across-DC replication and unified resource poolmanagement.

MDC is an optional feature. You must purchase a license to use this feature.

1.2.8 Erasure CodeTo avoid this problem, the UDS also provides the Erasure Code feature (also a storage mode),which improves the storage utilization without lowering data reliability.

Erasure Code is a feature that stores 1.x duplicates of data to achieve high data reliability withlow data redundancy. Objects are divided into data blocks of fixed length. Based on the ErasureCode algorithm, every M continuous data blocks have N parity blocks. The value of N is smallerthan that of M. The formula for calculating the coefficient (1.x) of data duplicate storage is asfollows: (M+N)/M = 1.x. Then the UDS combines the M data blocks and N parity blocks intoone data block group and stores them on different disks. In Erasure Code storage mode, the UDScan work correctly after N data blocks fail or are lost.

The Erasure Code feature applies to scenarios which require improvement of storage utilizationand reduction of hardware and maintenance costs.

The UDS supports both Erasure Code and tri-duplicate storage modes. The UDS system usesErasure Code by default, and only the administrator can change the storage mode. Enabling ordisabling the Erasure Code storage mode does not affect the system service operation. Thestorage mode is only applicable to buckets that are created by users after the storage mode ischanged.

Data Write ProcessFigure 1-6 shows the data write process after the Erasure Code storage mode is enabled.



16

Figure 1-6 Data write process

Object

D1 D2 D3 …...

P1 P2

2

3

Dm …...

Group

D1 D2 D3 …... Dm

…...

…...

Disk Disk Disk Disk Disk Disk Disk…...

Pn

…...

1

1 Objects uploaded by users are divided into data blocks of fixed length.

2 The Erasure Code algorithm is used to calculate N parity blocks for each M continuous data blocks.The value of N is smaller than that of M. Then the UDS combines the M data blocks and N parity blocksinto one data block group. In the previous figure, data blocks D1 to Dm and parity blocks P1 to Pn arecombined into one data block group.

3 Data blocks and parity blocks of the data block group are randomly stored on different disks of differentUDSNs.

Data Read Processl In normal conditions, the UDS reads only data blocks in Erasure Code storage mode.

Figure 1-7 shows the data read process in normal conditions.



17

Figure 1-7 Data read process in normal conditions

…...Disk Disk Disk Disk

Object

D1 D2 D3 …... Dm

1

2

…...P1 P2 …...

Disk Disk Disk …...

Pn

…...

1 The UDS obtains data blocks stored on different disks.

2 The UDS combines the obtained data blocks into a complete object and sends the object to users.

l The data read and recovery process upon data block damage is as follows:

– If the total number of damaged data blocks and parity blocks in a single data block groupis smaller or equal to N, lost data is automatically recovered based on other intact datablocks and parity blocks. The recovered data is stored on disks in normal state.

Figure 1-8 describes the data recovery process upon the failure of two disks after theErasure Code storage mode is enabled.

Figure 1-8 Data read and recovery process upon the data block damage

P1 P2D1 Fail Fail …... Dm

…...

…...

Disk Disk Disk Disk Disk Disk…...

Pn

Object

D1 D2 D3 …... Dm

1 5

D2 D3

Disk Disk

3

4

…...

Group

…...

2

Disk

1 The UDS obtains M data blocks stored on different disks.

2 The UDS detects data block damage and obtains parity blocks.



18

3 Based on the obtained data blocks and parity blocks, the UDS uses the Erasure Code algorithmto recover damaged data blocks. After the recovery, M data blocks are usable.

4 The UDS reads the M data blocks and combines them into a complete object and sends theobject to users.

5 The UDS stores recovered data on disks in normal state.

– If the total number of damaged data blocks and parity blocks in a single data block groupis larger than N, the UDS re-reads data blocks by smaller granularity to recover data ineach damaged data block. In normal conditions, the UDS reads data blocks by 1 MB.However, in this case, the UDS may re-read data blocks by 64 KB. In this way, the UDScan recover data blocks and parity blocks to the maximum.

NOTICEIf the number of damaged data and parity blocks is larger than N and the recoverymeasures fail to reduce the number to N or less.

1.2.9 DeduplicationThe UDS provides massive resource pools that can store billions of objects. As the number ofstored objects increases, multiple identical objects are stored, decreasing storage utilization. Insuch circumstances, the UDS employs the deduplication technology to delete duplicate data andretains only one copy of data, improving storage utilization.

Deduplication is a specialized data compression technique for eliminating coarse-grainedredundant data, typically to improve storage utilization. In the deduplication process, duplicatedata is deleted, leaving only one copy of the data to be stored, along with references to the uniquecopy of data. Deduplication is able to reduce the required storage capacity since only the uniquedata is stored.

The UDS supports offline object-based deduplication. When creating a user, you can enable ordisable the deduplication for feature the user based on site requirements. Enabling and disablingof the deduplication feature must be performed in the account management system.

The deduplication feature requires a license.

Application Scenario

The deduplication feature applies to the following scenarios:

Online storage

A large amount of duplicate data is generated due to file sharing and replication. With thededuplication feature, the UDS can detect and delete duplicate data when storing data in service.In this way, the deduplication feature helps decrease the growth rate of online storage spaceusage and reduce storage costs.

Data backup and archiving



19

Data that is rarely accessed is stored in a fixed storage location for archiving and retrieval. Sincethe archive data needs to be retained for a long period of time, the amount of archive dataincreases constantly. The deduplication feature helps minimize the storage space occupied byarchive data.

Disaster recovery system

A large amount of data is backed up to a remote storage system to ensure that the local data canbe recovered after data loss occurs. The growing amount of data poses great pressure on datatransfer links between the local and remote storage systems. The deduplication feature can deleteduplicate data before data is backed up to the remote system. This greatly improves data transferefficiency.

Application RestrictionThe deduplication feature of the UDS has the following restrictions:l Duplicate objects that are uploaded in a multipart upload task cannot be deduplicated.l Duplicate object copies generated by manual replication operations cannot be deduplicated.l Objects whose sizes are smaller than 4 KB (including 0 Byte) cannot be duplicated.l The feature can delete a maximum of 1000 duplicate objects.

Working ProcessAfter a user uploads objects, the access cluster stores the objects to the storage cluster and returnsthe user a message indicating that the objects have been uploaded. Then, the access cluster scansobjects in the storage cluster. Deduplication is started if the following conditions are met:l Deduplication has not been performed on the object.l The deduplication feature has been enabled for the bucket that owns the object.l The object is not a copy object generated by a manual replication operation.l The size of the object is larger than 4 kB.l The number of source objects that are referred does not exceed 1000.

Figure 1-9 shows the deduplication process.

Figure 1-9 Deduplication process

User

2

3

1

4

Access cluster Storage cluster

1 A user uploads an object. 3 The access cluster returns the user a messageindicating that the object has been uploadedsuccessfully.

2 The access cluster stores the object to thestorage cluster.

4 The access cluster starts deduplication.



20

Each object has one unique fingerprint. After deduplication is started, the UDS searches for anddeletes duplicate objects based on fingerprints. To prevent a conflict between download anddeletion of an object, the UDS records the deduplication time (current system time) of an objectin the object's metadata and still retains the object. If the UDS detects that the current systemtime is 24 hours or longer later than the deduplication time of an object, the object is automaticallydeleted.

Figure 1-10 shows the deduplication working process.

Figure 1-10 Deduplication working process

Deduplication

Before:Object quantity = 12

After:Object quantity = 5

1.2.10 Data CompressionThe UDS incorporates the data compression technology that compresses data before storage toboost storage utilization.

This technology leverages a compression algorithm to compress objects uploaded by users. TheUDS uses the GZIP compression algorithm to compress objects at the block level, delivering anaverage compression ratio of 50%.

The UDS supports user-specific data compression policies. Once a data compression policy isactivated, all objects in the buckets created by the user will be automatically compressed afterbeing uploaded to the UDS. If no data compression policy is configured, all objects in the bucketswill not be compressed. User-specific data compression policies can be modified anytime.However, bucket-specific data compression policies cannot be modified once configured.Changes in a user-specific data compression policy affect the user's new buckets only.

The data compression policies supported by the UDS comply with the following rules:

l Objects or data blocks not larger than 4 KB will not be compressed.

l Objects that are uploaded in parts will be compressed after all parts are uploaded andassembled.

l Only the objects belonging to the active data center will be compressed.

l If the HTTP request message of an object to be uploaded contains a Content-Type header,the UDS resolves the file type before compressing data. Image, video, and audio files willnot be compressed.

l Deduplicated objects will not be compressed.

Data compression is an optional feature. A license must be purchased to use this feature.



21

Figure 1-11 shows the data compression process.

Figure 1-11 Data compression process

User

2

3

1

4

Access cluster Storage cluster

1 A user uploads an object. 2 The access cluster stores the object to the storagecluster.

3 The access cluster returns the user amessage indicating that the object hasbeen uploaded successfully.

4 The access cluster initiates data compression.

After a data compression task is triggered, the system starts compressing the object if thebackground check program detects that the object metadata status is uncompressed, saves thecompressed object to the storage cluster to replace the original object, and simultaneouslyupdates the object metadata status to compressed.

When a user downloads an object, the access cluster determines whether the object iscompressed. If yes, the access cluster decompresses the object before sending it to the user. Ifnot, the access cluster reads the object from the storage cluster and sends it to the user.

1.2.11 License-based FeaturesThe license-based features of the UDS include MDC, deduplication, and data compression.

Table 1-2 License-based features

No. Feature License Description

1 Flexible Scalability You must purchase an expansionlicense if expansion is required.

2 MDC You must apply and import a licensefor each data center.

3 Deduplication None.

4 Data compression

1.3 Hardware Configuration RulesThis section provides the UDS hardware configuration rules to give users a glimpse of thedeployment methods of the UDS devices in cabinets.

A UDS system consists of one primary cabinet and several expansion cabinets. All primarycabinet and expansion cabinets contains A-Node, access switches, and UDSNs, and follows the



22

same configuration rules. The UDS can be equipped with only one primary cabinet for aminimum configuration. Multiple expansion cabinets can be easily added based on siterequirements.

The hardware configuration rules for a single UDS cabinet are as follows:

l The standard configuration is: 2 A-Nodes + 2 access switches + 4 UDSNs.

l For a cabinet with a power distribution box (PDB), a maximum of four UDSNs can beconfigured.

l For a cabinet with a power distribution unit (PDU), a maximum of seven UDSNs can beconfigured.

l Each cabinet must have two access switches and an optional number of A-Nodes andUDSNs based on site requirements.

l It is not recommended that a single cabinet house four A-Nodes and seven UDSNs at thesame time due to the power consumption and load bearing capacity of the equipment room.

1.4 System NetworkingThis section describes the UDS network structure and planes.

Network Structure

The UDS supports two networking modes. For details about network connections, refer to theHUAWEI OceanStor UDS Massive Storage System V100R002C01 Hardware InstallationGuide.

l Stack networking: The access switches in a cabinet are stacked to provide services so as toensure the network reliability. If aggregation switches are configured in stack mode, thestack networking mode is recommended for the UDS.

l VRRP active-standby networking: The access switches in a cabinet provide servicesindependently, and ensure the network reliability by connecting to the aggregation switcheswhich are configured in Virtual Router Redundancy Protocol (VRRP) active-standbymode. If aggregation switches are configured in VRRP mode, the VRRP active-standbynetworking mode is recommended for the UDS.

NOTE

During system installation, upgrade, node reinstallation, patch installation, and capacity expansion, theIPMI management network port on an A-Node is used to restart the A-Node so as to complete the task.So, you must connect the IPMI management network port on an A-Node to a 10/100/1000BASE-T Ethernetport on a UDSN in the same cabinet using a network cable. When the system is working normally, thiscable can be removed. Because the IPMI management IP address and the storage plane are on the samenetwork segment, you can access the IPMI management network port on an A-Node through the storageplane, exposing the UDS to security risks. If the network security of the storage plane can be guaranteed,connecting this cable facilitates installation and maintenance. If this cable is not connected during theinstallation, the installation status shown in the software installation wizard could be incorrect. Exercisecaution when you decide whether to connect the cable.

Stack networking

In stack networking mode, the UDS consists of primary cabinets and expansion cabinets. Figure1-12 shows the logical network structure.



23

Figure 1-12 Stack networking

Allows all network planes to pass.

Stack

Aggregation switches

Access switches

Stack

A-Nodes UDSNs

Allows all network planes to pass. Allows the storage plane to pass.

Allows the storage plane

to pass.

l When multiple cabinets are configured as a UDS system, every four cabinets form a cabinet

group. In each cabinet group, there are one primary cabinet and three expansion cabinets.The access switches in the primary cabinet connect to the aggregation switches, and theaccess switches in the expansion cabinets connect to the access switches in the primarycabinet, as shown in Figure 1-13.

l A minimally configured UDS system has only one primary cabinet.l The cabinet which the operation and maintenance service (OMS) is deployed in must be

the primary cabinet of its cabinet group.l Each cabinet must contain A-Nodes, UDSNs, and access switches.



24

Figure 1-13 Cabinet group

Aggregation Layer

……

Primary cabinet

Expansion cabinet -1



Cabinet group -n

Primary cabinet




Cabinet group -1

Primary cabinetl Each primary cabinet has two to four A-Nodes. When a primary cabinet is used for

deploying the OMS, two of the A-Nodes are configured with OMS and object-based storageservice controller (OSC) and the others with OSC only. The two OMSs work in active/standby mode.

l Each primary cabinet has two stacked access switches. Each access switch provides 2410GE ports. Three 10GE ports are aggregated through link aggregation control protocol(LACP) and connect to upstream aggregation switches. Four 10GE ports serve as stackports. A few ports are used to connect the access switches in expansion cabinets and theA-Nodes and UDSNs in the same cabinet which the switch is deployed in, and the otherports are reserved for redundancy expansion.

Expansion cabinetl Each expansion cabinet has a maximum of four A-Nodes. OSC is deployed on each of

them.l Each expansion cabinet has two stacked access switches. Each access switch provides 24

10GE ports. Two 10GE ports are aggregated through LACP and connect to upstream accessswitches in the primary cabinet. Four 10GE ports serve as stack ports. Some ports are usedto connect the A-Nodes and UDSNs in the same cabinet which the switch is deployed in,and the remaining ports are reserved for redundancy expansion.



25

NOTICEIf the primary cabinet is faulty, all nodes in the cabinet group will be unable to provide services.If the primary cabinet in which the OMS is deployed becomes faulty, the DeviceManager willbecome unavailable, and you cannot use the monitor and alarm functions of the UDS.Meanwhile, users cannot access the object storage service. You are advised to use a uppernetwork management system to monitor the floating management IP address of the UDS todetect the UDS system status in real time.

VRRP active-standby networking

In VRRP active-standby networking mode, device connections and configurations in eachcabinet are similar. Figure 1-14 shows the logical network structure.l Each cabinet must contain A-Nodes, UDSNs, and access switches.l Two to four A-Nodes can be configured in each cabinet. Only one cabinet's two A-Nodes

can be used to deploy both the OMS and OSC, which are presented as active-standby OMSnodes. Other A-Nodes are used for deploying only OSC.

l Two access switches are configured in each cabinet. Each switch provides 24 10GE ports.Two 10GE ports connect to aggregation switches. Four 10 GB ports are available forexpansion connection to ensure that nodes in the same cabinet can communicate with eachother. The other ports connect to the A-Nodes and UDSNs in the same cabinet, with a fewreserved for redundancy and expansion.

NOTICEIf a cabinet is faulty, all nodes in this cabinet will be unable to provide services. If the cabinetin which the OMS is deployed becomes faulty, the DeviceManager will also become unavailable,and you cannot use the monitor and alarm functions of the UDS. Meanwhile, users cannot accessthe object storage service. You are advised to use a upper network management system tomonitor the floating management IP address of the UDS to detect the UDS system status in realtime.



26

Figure 1-14 VRRP active-standby networking

Allows all network planes to pass.

Aggregation switches

Access switches

A-Nodes UDSNs

Allows all network planes to pass. Allows the storage plane to pass.

VRRPactive-standby

Allows the storage plane

to pass.

VRRPHeartbeat

Expansion connection

Network PlanesThe UDS can be divided into four network planes by service type.l Management plane: the network plane to which management and maintenance systems

belong. All IP addresses on the management plane reside on the same subnet.l Service plane: the network plane on which OSCs offer object storage service API, account

management API and identity and access management (IAM) API for externalcommunication. All IP addresses on the service plane reside on the same subnet.

l Storage plane: the network plane on which OSCs, OMSs, and smart disks communicatewith one another. This plane is used for internal management and communication amongnodes. The management IP addresses of access switches reside on the storage plane.

l Multiple data centers (MDC) replication plane: an optional network plane used for datareplication between data centers. This plane needs to be planned when the MDC that usesthe replication mode (communicated on the VPN) is deployed. VPN is short for VirtualPrivate Network. The MDC replication plane of each data center must reside on the samenetwork segment. The plane does not need to be planned when the MDC that uses the regionmode (communicated on the public network or using NAT) is deployed. NAT is short forNetwork Address Translation.



27

2 Product Structure

About This Chapter

This chapter describes the hardware components and software structure of the UDS.

2.1 Hardware ComponentsThis section describes the functions, appearance, and specifications of the UDS cabinet, A-Node,UDSN, and switch.

2.2 Software StructureThis section describes the functions of the service layer, storage layer, and operation andmaintenance (O&M) layer based on the logical structure of the UDS.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description 2 Product Structure


28

2.1 Hardware ComponentsThis section describes the functions, appearance, and specifications of the UDS cabinet, A-Node,UDSN, and switch.

2.1.1 CabinetThis section describes the functions, appearance, physical structure, heat dissipation, andtechnical specifications of a UDS cabinet.

FunctionsUDS uses the DKBA41002413.ASM-FR42611 cabinet (FR42611 for short) of the Arki seriesof cabinets developed by Huawei. FR42611 is 42 U (1866.9 mm or 73.5 in.) in height and houseshardware components including cabinet power supplies, A-Nodes, UDSNs, and access switches.

AppearanceFigure 2-1 shows an FR42611 cabinet.

Figure 2-1 FR42611 cabinet



29

Structure

Figure 2-2 shows the structure of an FR42611 cabinet.

Figure 2-2 Structure of an FR42611 cabinet

1 Front door 2 Top cover

3 Rear door 4 Side panel

5 Mounting bar 6 Rack



30

Heat DissipationThe FR42611 cabinet is equipped with front and rear mesh doors and supports front-to-rearcooling and underfloor ventilation. Figure 2-3 shows the heat dissipation of the cabinet.

Figure 2-3 Heat dissipation of the FR42611 cabinet

2.1.2 A-NodeThe UDS uses T3200 G3 servers as A-Nodes. The T3200 G3 adopts a modular design andconsists of a system enclosure, a main control board enclosure, and two power modules.

StructureFigure 2-4 shows the structure of an A-Node.

NOTE

The A-Node supports AC power modules only.



31

Figure 2-4 Structure of an A-Node

1 System enclosure 2 Power module

3 Main control board enclosure 4 Backplane

Front ViewFigure 2-5 shows the front view of an A-Node.

Figure 2-5 Front view of an A-Node

1 USB port 2 System enclosure

3 Disk filler panel 4 System Power indicator/Power button

Rear ViewFigure 2-6 shows the rear view of an A-Node.



32

Figure 2-6 Rear view of an A-Node

1 System enclosure 2 Power module handle

3 Main control board enclosure handle 4 10GE SFP+ port

5 SAS card 6 System disk module

7 Power module 8 Power module socket

9 VGA port 10 Serial port

11 USB port 12 IPMI management network port

13 GE port 14 PCIe expansion slot

Componentsl System enclosure

The system enclosure integrates a backplane to provide signal and power connectivity forall enclosed modules.Figure 2-7 shows a system enclosure.

Figure 2-7 System enclosure

l Main control board enclosureThe main control board enclosure provides storage services, receives configuration andmanagement commands, and saves configuration information.Figure 2-8 shows a main control board enclosure.



33

Figure 2-8 Main control board enclosure

l System disk moduleAn A-Node is equipped with two 2.5-inch 10k rpm SAS disks as system disks configuredfor RAID 1. Each system disk has 300 GB capacity and stores system data.

NOTICEl The two system disks must be of the same disk type.l Do not insert or remove the system disks unless absolutely necessary. System data may

be damaged.

Figure 2-9 shows a system disk.



34

Figure 2-9 System disk

1 Disk label 2 Disk handle

3 Disk latch 4 Disk Alarm/Location indicator

5 Disk Running indicator 6 Disk

7 Disk tray

l Power moduleAn A-Node provides two AC power modules in 1+1 redundancy mode. These powermodules enable the A-Node to work properly under maximum power consumption.Figure 2-10 shows an AC power module.



35

Figure 2-10 AC power module

1 Power module latch 2 Power module handle

3 Power module built-in fan 4 Power module socket

5 Power module Running/Alarm indicator

Indicators

Figure 2-11 shows the indicators on the front panel of an A-Node.

Figure 2-11 Indicators on the front panel of an A-Node

Table 2-1 describes the indicators on the front panel of an A-Node.

Table 2-1 Indicators on the front panel of an A-Node

Module No. Indicator Description

Systemenclosure 1

System Powerindicator/Powerbutton

l Steady green: The A-Node is powered on.l Off: The A-Node is powered off.



36


2 System Alarmindicator

l Steady red: An alarm is generated on the A-Node.

l Blinking read: An alarm is generated on thepower module.

l Off: The A-Node is running correctly.

3SystemLocationindicator

l Steady blue: The A-Node has been located.l Off: The A-Node has not been located.

Figure 2-12 shows the indicators on the rear panel of an A-Node.

Figure 2-12 Indicators on the rear panel of an A-Node

Table 2-2 describes the indicators on the rear panel of an A-Node.

Table 2-2 Indicators on the rear panel of an A-Node


Powermodule

1 Power moduleRunning/Alarmindicator

l Steady green: The power module is runningcorrectly.

l Blinking green: The power input is normal andthe A-Node is powered off.

l Steady red: The power module is faulty.l Blinking red: Undervoltage (including power-

off) or overvoltage is occurring.l Off: No external power input is found.

Maincontrolboardenclosure

2 10GE SFP+port indicator

l Steady blue: The data transfer rate is 10 Gbit/s.

l Blinking blue: Data is being transferred.l Steady red: The port is faulty.l Off: The link to the port is down.



37


3 Disk Runningindicator

l Blinking green: Data is being transferred.l Steady green: No data is being transferred.l Off: The interface module is powered off.

4 Disk Alarm/Locationindicator

l Steady blue: The disk module has been located.l Steady red: An alarm is generated on the disk

module.l Off: The disk module has not been located, nor

an alarm is generated on the disk module.

5 System Alarmindicator

l Steady red: An alarm is generated on the A-Node.

l Blinking red: An alarm is generated on thepower module.

l Off: The A-Node is running correctly.

6 SystemLocationindicator

l Steady blue: The A-Node has been located.l Off: The A-Node has not been located.

7 LNK indicatorof the IPMImanagementnetwork port

l Steady green: The link to the IPMImanagement network port is up.

l Off: The link to the IPMI management networkport is down.

8 ACT indicatorof the IPMImanagementnetwork port

l Blinking yellow: Data is being transferred.l Off: No data is being transferred.

9 ACT indicatorof a GE port

l Blinking yellow: Data is being transferred.l Off: No data is being transferred.

10 LNK indicatorof a GE port

l Steady green: The data transfer rate betweenthe A-Node and the access switch is 1000 Mbit/s.

l Steady orange: The data transfer rate betweenthe A-Node and the application server is 100Mbit/s or 10 Mbit/s.

l Off: The link to the access switch is down orthe cable is disconnected.

2.1.3 UDSNThe UDSN adopts a modular design and consists of a system enclosure, fan modules, powermodules, switch board modules, and smart disk modules.



38

Structure

Figure 2-13 shows the structure of a UDSN.

NOTE

The UDSN supports AC power modules only.

Figure 2-13 Structure of a UDSN

1 System enclosure 2 Power module

3 Fan module 4 Switch board module

5 Smart disk module

Front View

Figure 2-14 shows the front view of a UDSN.

Figure 2-14 Front view of a UDSN

1 System enclosure 2 UDSN handle

3 Captive screw



39

Rear ViewFigure 2-15 shows the rear view of a UDSN.

Figure 2-15 Rear view of a UDSN

1 System enclosure 2 Power module handle

3 Power module 4 Power module socket

5 Fan module 6 Fan module handle

7 Serial port 8 Management network port

9 Switch board module A 10 10/100/1000BASE-T Ethernet port

11 Switch board module B 12 10GE SFP+ port

13 Switch board module latch 14 Switch board module handle

NOTE

A dust-proof plug is inserted in the 10GE SFP+ port numbered 1 when not in use. If you need to use theport for network connection, remove the dust-proof plug.

Componentsl System enclosure

A system enclosure integrates a backplane to provide signal and power connectivity formodules.Figure 2-16 shows a system enclosure.



40

Figure 2-16 System enclosure

l Smart disk moduleA smart disk module provides storage capacity for service data.Figure 2-17 shows a smart disk module.

Figure 2-17 Smart disk module

1 Smart disk module latch 2 Smart disk module handle

3 Smart disk module indicator 4 Disk

5 CPU

l Power moduleA UDSN provides four AC power modules in 2+2 redundancy mode. These power modulesenable the UDSN to work properly under maximum power consumption.



41

Figure 2-18 shows an AC power module.

Figure 2-18 AC power module

1 Power module fan 2 Power module label

3 Power module socket 4 Power module latch

5 Power module handle

l Fan moduleA UDSN houses two fan modules and each fan module has six fans. The 12 fans work in11+1 redundancy mode. Each fan module has 16 speeds controlled intelligently based onsystem temperature to reduce power consumption and noise.Figure 2-19 shows of a fan module.



42

Figure 2-19 Fan module

1 Fan module handle 2 Fan module latch

3 Fan module Running/Alarm indicator

l Switch board moduleA UDSN houses two switch board modules in 1+1 redundancy mode. A switch boardmodule provides two 10GE SFP+ ports for communicating with access switches.Figure 2-20 shows a switch board module.

Figure 2-20 Switch board module

1 10/100/1000BASE-T Ethernet port 2 10GE SFP+ port

3 Serial port 4 Management network port



43

5 Switch board module Alarm indicator 6 Switch board module Power indicator

Indicators

l Indicators on the front panel

Figure 2-21 shows the indicators on the front panel of a UDSN.

Figure 2-21 Indicators on the front panel of a UDSN

Table 2-3 describes the indicators on the front panel of a UDSN.

Table 2-3 Indicators on the front panel of a UDSN

Module No. Indicator Status and Description

Systemenclosure

1 UDSN Location indicator l Blinking blue: The UDSN hasbeen located.

l Off: The UDSN has not beenlocated.

2 UDSN OvertemperatureAlarm indicator

l Steady red: The temperature ofthe UDSN is too high.

l Off: The temperature of theUDSN is within the normalrange.

3 UDSN internal moduleAlarm indicator

l Steady red: Internal fieldreplaceable units (FRUs) ofthe UDSN are faulty.NOTE

Internal FRUs of a UDSN includesmart disk modules and etc.

l Blinking red: Internal FRUs ofthe UDSN have failed.

l Off: Internal FRUs are runningcorrectly.



44


4 UDSN rear module Alarmindicator

l Steady red: The number of rearFRUs is less than half of that inthe standard configuration orthe rear FRUs are faulty.NOTE

Rear FRUs of a UDSN includepower modules, fan modules, andswitch board modules.

l Off: Rear FRUs are runningcorrectly.

5 UDSN Power indicator l Steady green: The UDSN ispowered on.

l Blinking green: The UDSN isbeing powered on or off.

l Off: The UDSN is poweredoff.

6 UDSN Alarm indicator l Steady red: An alarm isgenerated on the UDSN.

l Off: The UDSN is runningcorrectly.

l Indicators on the rear panel

Figure 2-22 shows the indicators on the rear panel of a UDSN.

Figure 2-22 Indicators on the rear panel of a UDSN

Table 2-4 describes the indicators on the rear panel of a UDSN.



45

Table 2-4 Indicators on the front panel of a UDSN


Powermodule

1 Power module Runningindicator

l Steady green: The powermodule is running correctly.

l Off: The power module ispowered off, or undervoltage,overvoltage, overtemperature,or short-circuit has occurred.

Switchboardmodule

2 Active indicator of themanagement network port

l Steady orange: No data isbeing transferred.

l Blinking orange: Data is beingtransferred.

l Off: The link to the port isdown.

3 Link indicator of themanagement network port

l Steady green: The link to theport is up.


Fan module 4 Fan module Running/Alarm indicator

l Steady green: The fan moduleis running correctly.

l Steady red: The fan module isfaulty.

l Off: The fan module ispowered off.

Switchboardmodule

5 Speed indicator of a10/100/1000BASE-TEthernet port

l Steady orange: The datatransfer rate is 1 Gbit/s.

l Off: The data transfer rate is 10Mbit/s or 100 Mbit/s.

6 Link/Active indicator of a10/100/1000BASE-TEthernet port

l Steady green: The link to theport is up.

l Blinking green: Data is beingtransferred.




46


7 10GE SFP+ port indicator l Steady blue: The data transferrate is 10 Gbit/s.

l Blinking blue: Data is beingtransferred.

l Steady green: The data transferrate is 1 Gbit/s.

l Blinking green: Data is beingtransferred.

l Steady red: The port is faulty.l Off: The link to the port is

down.

8 Switch board moduleAlarm indicator

l Steady red: An alarm isgenerated on the switch boardmodule.

l Blinking red and the switchboard module Power indicatorblinking green: The switchboard module has been locatedor its firmware is beingupgraded.

l Off: The switch board moduleis powered off or is runningcorrectly.

9 Switch board modulePower indicator

l Steady green: The switchboard module is runningcorrectly.

l Blinking green and the switchboard module Alarm indicatorblinking red: The switch boardmodule has been located or itsfirmware is being upgraded.

l Off: The switch board moduleis powered off.

l Smart disk indicator

Figure 2-23 shows the indicator on a smart disk module.

Figure 2-23 Smart disk module indicator

Table 2-5 describes the indicator on a smart disk module.



47

Table 2-5 Smart disk module indicator

Module Indicator Status and Description

Smart diskmodule

Smart disk moduleindicator

l Steady green: The smart disk module isrunning correctly.

l Blinking green: The smart disk module isbeing started.

l Steady red: The smart disk module isfaulty.

l Blinking red: The smart disk module isgoing to fail.

l Blinking blue: The smart disk module isbeing located.

l Off: The smart disk module is powered off.

2.1.4 SMS ModemThe UDS uses a modem for alarm notification so that maintenance personnel can be informedabout the network status in a timely manner. The HUAWEI OceanStor DeviceManager(DeviceManager for short) at the system management layer supports remote alarm notificationby email or short message for maintenance personnel to learn about network element (NE)alarms, facilitating fault handling.

An SMS modem is an optional component of the UDS. The DeviceManager uses an SMS modemfor data conversion to implement alarm notification by short message. When maintenancepersonnel are not on site and cannot receive emails, you can configure the SMS notificationserver to enable alarm notification by SMS to send alarm information to the maintenancepersonnel's mobile phones in the form of short messages. This method helps the maintenancepersonnel learn about the network and heath status of the UDS system in a timely manner. Figure2-24 shows an SMS modem.

Figure 2-24 SMS modem

1 DB9 serial port 2 Power socket



48

2.1.5 Access SwitchAccess switches are deployed in a UDS cabinet for connecting to downstream A-Nodes andUDSNs in the same cabinet and to upstream aggregation switches or access switches in theprimary cabinet. The UDS supports S6324 and S6724 switches. The two types of switches haveidentical functions, ports, and indicators. This document uses the S6324 switch as an example.

Front ViewFigure 2-25 shows the front view of an S6324 switch.

Figure 2-25 Front view of an S6324 switch

1 GE/10GE BASE-X Ethernet optical port 2 Console port

3 Mode Switch button 4 USB port

5 Management network port

NOTE

If you press the Mode Switch button once, the Mode Switch indicator is steady green and the service portindicators indicate the port speed. If you press this button twice, the Mode Switch indicator is steady redand the service port indicators indicate stacking information. If this button is not pressed for 45 seconds,the Mode Switch indicator is restored to its default mode (off).

Rear ViewFigure 2-26 shows the rear view of an S6324 switch.

Figure 2-26 Rear view of an S6324 switch

1 ESD jack 2 Fan module

3 Fan module handle 4 Power module handle

5 Power module switch 6 Power module socket

Indicatorsl Indicators on the front panel

Figure 2-27 shows the indicators on the front panel of an S6324 switch.



49

Figure 2-27 Indicators on the front panel of an S6324 switch

Table 2-6 describes the indicators on the front panel of an S6324 switch.

Table 2-6 Indicators on the front panel of an S6324 switch

No. Indicator ID IndicatorName

Status and Description

1 PWR1 Powerindicator

l Steady green: The power supply isrunning correctly.

l Steady red:

– In the case of a dual-powerconfiguration, power supplies arein position but the switch is notturned on.

– The power supply is disconnected.

– The power supply is faulty.l Off: Power supplies cannot be

detected, or the power supply isworking incorrectly when only onepower supply is configured.

2 PWR2 Powerindicator

l Steady green: The power supply isrunning correctly.

l Steady red:

– In the case of a dual-powerconfiguration, power supplies arein position but the switch is notturned on.

– The power supply is disconnected.

– The power supply is faulty.l Off: Power supplies cannot be

detected, or the power supply isworking incorrectly when only onepower supply is configured.



50



3 SYS SystemRunningindicator

l Steady green: The system is runningincorrectly or is being started.

l Blinking green: The system is runningcorrectly.

l Steady orange: The system isperforming a power on self-test(POST).

l Steady red: The system is runningincorrectly after the switch isregistered or an alarm about the powersupplies, fans, or temperature isgenerated.

l Off: The system is not started.

4 MODE ModeSwitchindicator

l Steady green: The service portindicators are temporarily used toindicate port speed and this indicatorwill be restored to its default mode(off) in 45 seconds.

l Steady red: The service port indicatorsare temporarily used to indicate thedevice stack ID and this indicator willbe restored to its default mode (OFF)in 45 seconds.

l Off: A service port indicator isworking in its default mode. In thiscondition, the port is working in STATmode.

5 link/ACT Managementnetwork portindicator

l Steady green: The link to the port is up.l Blinking green: Data is being

transferred.l Off: The link to the port is down.

l Indicators on the rear panel

Figure 2-28 shows the indicators on the rear panel of an S6324 switch.

Figure 2-28 Indicators on the rear panel of an S6324 switch



51

Table 2-7 describes the indicators on the rear panel of an S6324 switch.

Table 2-7 Indicators on the rear panel of an S6324 switch



1 STATUS Fan moduleindicator

l Blinking green slowly: The fanmodule is running and communicatingcorrectly.

l Blinking green fast: The fan module isrunning correctly but communicatingabnormally.

l Steady red: The fan module is faulty.l Blinking red slowly: An alarm is

generated on the fan module andrequires handling. The causes for thisproblem include dual in-line package(DIP) switch errors, short circuits, fanblocking, and fan defects.

l Off: The fan module is not running.

2 INPUT Powermoduleindicator

l Steady green: The power input isnormal.

l Steady red: Undervoltage orovervoltage is occurring.

l Off: The power cable is looselyconnected or no AC power input isfound.

3 OUTPUT Powermoduleindicator

l Steady green: The power output isnormal.

l Steady red: The power module fan isfaulty, or overvoltage, currentlimiting, short-circuit, orovertemperature protection isoccurring.

l Off: The power cable is looselyconnected or no AC power input isfound.

2.2 Software StructureThis section describes the functions of the service layer, storage layer, and operation andmaintenance (O&M) layer based on the logical structure of the UDS.



52

2.2.1 Logical StructureLogically, the UDS is divided into the service layer, storage layer, and operation and maintenance(O&M) layer. The UDS is adaptable to multiple scenarios including massive storage pool,centralized backup, online backup, online storage, and active archive. The storage solutionprovided by the UDS features robust reliability, flexible scalability, and easy management.

Figure 2-29 shows the logical structure of the UDS.

Figure 2-29 UDS logical structure

l Service layerProvides standard application programming interfaces (APIs) to establish transfer channelsbetween the UDS and clients, billing centers, and storage systems across regions, andcontrols user and client access to the UDS.

l Storage layerProvides distributed object data storage, supports upper-layer applications, and providessecurity and access control, storage policy management, and storage resource management.

l O&M layerProvides routine management and maintenance functions. Maintenance engineers canperform routine management and maintenance for the storage system using a web-basedportal and maintenance tools.

2.2.2 Service LayerThis section describes the functions of the service layer, including operation interconnection,object storage service, billing management, permission management, multiple data centers(MDC) deployment, and quota management.

l Operation interconnectionThe service layer provides standard Representational State Transfer (REST) and SecureFile Transfer Protocol (SFTP) APIs for users to integrate and invoke the UDS. These APIsare compatible with various types of clients and applications, facilitating the customers'service expansion.

l Object storage serviceThe service layer supports uploading, downloading, querying, and deleting objects.



53

l Billing management

Every user operation generates a charging data record (CDR). The UDS periodicallycollects used capacity and operation information for each user, generates billinginformation, and allows the billing center to obtain CDRs externally through the billingAPI.

l Permission management

Different users are granted different permissions. Every user operation request needs to beauthenticated. A user can access an object or perform an operation only when the user hasthe appropriate permissions.

l MDC deployment

Several UDS storage systems deployed in different places can form multiple data centers(MDC). MDC supports replication mode and region mode, intended for cross-DCreplication and unified resource pool management scenarios, respectively. User data canbe copied and backed up between DCs by asynchronous remote replication. Alternatively,a region can be specified for storing objects to provide higher data reliability.

l Quota management

The storage space quota is a basic piece of property belong to users and buckets. Users canmodify their own quotas.

2.2.3 Storage LayerThis section describes the functions of the storage layer, including storage resource management,storage policy management, distributed object storage, and security and access control.

l Storage resource management

This function quickly and accurately calculates storage resources, network resources, andservice processing capability, and provides a summary to help with quota management.

l Storage policy management

The UDS supports the following storage policies:

– EC and tri-duplicate: The UDS supports erasure code (EC) and tri-duplicate storagepolicies. User data is stored by using the EC policy by default. Users can switch to thetri-duplicate policy based on site requirements.

– Deduplication: The deduplication function is user-specific.

– Data compression: The data compression function is user-specific.

l Distributed object storage

User data is stored in the UDS as objects and can be managed and used through HTTPAPIs. The UDS uses the distributed hash algorithm to remove all central points on objectaccess paths, eliminating object layout bottlenecks and providing scalable, secure, reliable,and cost-effective data storage services.

l Security and access control

– User data is sliced into data blocks and saved onto different UDSNs. This storage modeprevents malicious users from obtaining user data from a single UDSN or smart disk.

– Virtualization technology is employed to logically isolate users.

– Sensitive user data is encrypted using the AES-256 algorithm before storage.

– The access control list (ACL) is used to control buckets and object access.



54

2.2.4 O&M LayerThis section describes the functions of the operation and maintenance (O&M) layer, includinginstallation, capacity expansion, upgrade, patch installation and uninstallation, log collection,alarm management, scheduled preventive maintenance inspection, performance statistics,service monitoring, and network topology.

NOTICEDuring system installation, capacity expansion, upgrade, and patch installation, the UDS usesFile Transfer Protocol (FTP) and Trivial File Transfer Protocol (TFTP) to transfer the softwarepackages to be installed. Because FTP and TFTP are insecure protocols, the UDS uses themonly for internal network communication on the storage plane. Therefore, do not deploy theUDS storage plane on the Internet for security purposes.

l Installation

Users can import their network data configuration files using the installation wizard. Then,the UDS starts automated node installation and network data configuration.

l Capacity expansion

Users can expand system capacity online following the node and smart disk expansionwizards.

l Upgrade

Users can upgrade system software following the system upgrade wizard and upgrade smartdisk firmware following the smart disk firmware upgrade wizard. The UDS supports bothonline and offline upgrades.

l Patch installation and uninstallation

Users can install and uninstall a system patch following the patch installation anduninstallation wizards.

l Log collection

The log service centrally collects, manages, stores, and backs up logs generated on all nodes.Maintenance engineers can use maintenance tools to obtain logs generated on specifiednodes in a specified period to facilitate fault locating.

NOTICEThe UDS does not log these operations on its operating systems (OSs) and databases thatbypass its external interfaces. These operations are recorded by the OSs and databases. Thisjeopardizes log audits and UDS system security. Therefore, it is highly recommended thatoperations on OSs and databases not bypass the external interfaces of the UDS.

l Alarm management

Users can manage current and historical alarms with the alarm reporting, viewing, clearing,dumping, masking, and notification functions. By viewing alarms, maintenance engineers



55

can monitor system and device anomalies and locate faulty services or nodes in a timelymanner.

l Scheduled preventive maintenance inspection (PMI)Scheduled tasks help engineers monitor time-specific system data and learn about systemrunning status at different points in time.

l Performance statisticsThis function quickly and accurately collects, calculates, and analyzes the statistics aboutsystem response to user requests, including request latency, number of failed requests.

l System monitoring

– Monitored data is displayed in lists, images, and files on web pages, allowingmaintenance engineers to learn about system running status in a timely and intuitiveway.

– If a UDS service or device is abnormal, alarms are generated to notify maintenanceengineers.

l Network topologyThe hardware device topology view enables maintenance engineers to view the appearance,status, names, specifications, alarm and performance statistics of physical devices,including A-Nodes, UDSNs, and access switches, as shown in Figure 2-30.

Figure 2-30 Network topology



56

3 System Interfaces

About This Chapter

This chapter describes the physical ports and external application programming interfaces (APIs)provided by the UDS.

3.1 Physical PortsThis section describes the physical ports provided by UDS access switches, A-Nodes, andUDSNs.

3.2 APIsThis section describes external application programming interfaces (APIs) provided by the UDSand their functions.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description 3 System Interfaces


57

3.1 Physical PortsThis section describes the physical ports provided by UDS access switches, A-Nodes, andUDSNs.

Table 3-1 describes the physical ports provided by the UDS.

Table 3-1 Physical ports

Device Port Name Function

Accessswitch

GE/10GE BASE-XEthernet optical port

Transmits and receives services.

Console port Connects to the switch console for switchconfiguration and maintenance.

USB port Connects to a USB drive for deployment, andconfiguration and upgrade file transfer.

Management networkport

Connects to a configuration terminal or networkmanagement workstation for building an onsite orremote configuration environment.

A-Node 10GE SFP+ port Connects to a GE/10GE BASE-X Ethernet opticalport on an access switch for the A-Node to operateand maintain the storage cluster.

GE port Connects to an application server for managementand maintenance of the A-Node.



58


IPMI managementnetwork port

Connects to a 10/100/1000BASE-T Ethernet port ona UDSN for remote operation and maintenance ofthe A-Node.NOTE

l During system installation, upgrade, nodereinstallation, patch installation, and capacityexpansion, the IPMI management network port on anA-Node is used to restart the A-Node so as to completethe task. So, you must connect the IPMI managementnetwork port on an A-Node to a 10/100/1000BASE-T Ethernet port on a UDSN in the same cabinet usinga network cable. When the system is workingnormally, this cable can be removed. Because theIPMI management IP address and the storage planeare on the same network segment, you can access theIPMI management network port on an A-Nodethrough the storage plane, exposing the UDS tosecurity risks. If the network security of the storageplane can be guaranteed, connecting this cablefacilitates installation and maintenance. Exercisecaution when you decide whether to connect the cable.

l After a UDS system is successfully installed, each A-Node on which the aforementioned network cable isdisconnected reports the ALM-60179873859 A-Node IPMI Management Port Is Abnormal alarm.This alarm has no adverse impact on the system. Youcan handle this alarm flexibly.

USB port Connects a mouse, keyboard, or another USBdevice, for example, a USB CD-ROM drive.

Serial port Extends the functions of the operating system andthird-party software. The serial port on the A-Nodedeployed as the active OMS is used to connect tothe SMS modem.

VGA port Connects to a monitor.

UDSN 10GE SFP+ port Connects to a GE/10GE BASE-X Ethernet opticalport on an access switch for UDSN clustering anddata transfer.



59


10/100/1000BASE-TEthernet port

Connects to an IPMI management port on an A-Node for baseboard management controller (BMC)data transfer.NOTE

l During system installation, upgrade, nodereinstallation, patch installation, and capacityexpansion, the IPMI management network port on anA-Node is used to restart the A-Node so as to completethe task. So, you must connect the IPMI managementnetwork port on an A-Node to a 10/100/1000BASE-T Ethernet port on a UDSN in the same cabinet usinga network cable. When the system is workingnormally, this cable can be removed. Because theIPMI management IP address and the storage planeare on the same network segment, you can access theIPMI management network port on an A-Nodethrough the storage plane, exposing the UDS tosecurity risks. If the network security of the storageplane can be guaranteed, connecting this cablefacilitates installation and maintenance. Exercisecaution when you decide whether to connect the cable.

l After a UDS system is successfully installed, each A-Node on which the aforementioned network cable isdisconnected reports the ALM-60179873859 A-Node IPMI Management Port Is Abnormal alarm.This alarm has no adverse impact on the system. Youcan handle this alarm flexibly.

Serial port Used for device fault locating or fieldcommissioning.

Management networkport

Used for UDSN configuration and status query.

3.2 APIsThis section describes external application programming interfaces (APIs) provided by the UDSand their functions.

The UDS provides open and standard APIs for interconnection with multiple types ofapplications. Figure 3-1 shows and Table 3-2 describes the interfaces and protocols usedbetween the UDS and interconnected entities.



60

Figure 3-1 Interfaces and protocols supported by the UDS

Object storage service application

BSS OSS

Billing center

UDS

Object storage

service API

Account

management API

Billing API

IAM API

OMS northbound API

Table 3-2 Interfaces and protocols supported by the UDS

InterfaceName

Function InterconnectedEntity

Protocol Name

Billing API The UDS works as the SecureFile Transfer Protocol (SFTP)server to provide billing APIs(SFTP APIs) externally for filetransfer. The billing centeraccesses the UDS as the SFTPclient to obtain charging datarecords (CDRs).

Billing center SFTP

Object storageservice API

The UDS provides standardRepresentational State Transfer(REST) APIs for third-partybackup and storage software toaccess buckets and objects afterauthentication and achieveobject storage.

Object storageservice application

HTTP/HTTPS



61

InterfaceName

Function InterconnectedEntity

Protocol Name

AccountmanagementAPI andIdentity andAccessManagement(IAM) API

The UDS provides the accountmanagement API and IAM API,which are standard RESTinterfaces, for third-partybusiness support systems(BSSs) to manage accounts,service delivery, accountcertifications, storage policyconfiguration, account quota,account statistics query, andaccount access authentication.

BSS software HTTP/HTTPS

OMSnorthboundAPI

The UDS provides the OMSnorthbound API that iscompatible with standard RESTinterfaces and SNMP interfacesfor third-party operationssupport systems (OSSs) toobtain monitoring, alarm, andtopology data for management.

OSS software HTTPS/SNMP



62

4 Technical Specifications

About This Chapter

This chapter describes the system specifications, hardware specifications, and environmentalrequirements of the UDS.

4.1 System SpecificationsThis section describes the physical storage capacity and maximum number of buckets, objects,and registered users supported by the UDS.

4.2 Hardware SpecificationsThis section describes the specifications of the cabinet, A-Node, UDSN, and access switch.

4.3 Environmental RequirementsThis section describes the requirements of the UDS on temperature, humidity, contaminants,heat dissipation, and noise to help you maintain favorable operating conditions.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description 4 Technical Specifications


63

4.1 System SpecificationsThis section describes the physical storage capacity and maximum number of buckets, objects,and registered users supported by the UDS.

Table 4-1 describes the system specifications of the UDS in a single data center.

Table 4-1 System specifications

Item Indicator

Maximum physical storage capacity 100.8 PB (25,200 4 TB disks) for one datacenter (DC)

Maximum number of buckets l 100 million per systeml 100 per account

Maximum number of objects l 50 million per bucketl 10 billion per system

Maximum number of registered users 10 million

4.2 Hardware SpecificationsThis section describes the specifications of the cabinet, A-Node, UDSN, and access switch.

Table 4-2 Cabinet specifications

Item Value

Cabinet model DKBA41002413.ASM-FR42611

Power supply 110 V AC, 220 V AC

Dimensions (H x W x D) 2000 mm x 600 mm x 1100 mm (78.74 in. x23.62 in. x 43.31 in.)

Available height 42 U (1866.9 mm or 73.5 in.)

Unloaded cabinet weight 120 kg (264.55 lb)

Static bearable weight 1200 kg (2645.55 lb)

Dynamic bearable weight 1000 kg (2204.62 lb)

Power distribution modules 2 PDUs



64

Table 4-3 Typical cabinet configurations

Configuration Item Value

2 A-Nodes + 2 accessswitches + 1 UDSN

Overall weight (including the cabinet) 322 kg (709.89 lb)

Single point of load 455 kg/m2 (1003.10 lb/m2)

Evenly distributed load 228 kg/m2 (502.65 lb/m2)

Cabinet input voltage/current (220 VAC PDU)

380V AC (three-phase)/16A or 220 VAC (single-phase)/32A


208 V AC (three-phase)/50 A

Heat dissipation 210 CFM (25oC or77oF) and 390 CFM(35oC or 95oF)

Overall power consumption 2358 W

System heat consumption 8041 BTU/h

2 A-Nodes + 2 accessswitches + 4 UDSNs


Single point of load 969 kg/m2 (2136.26 lb/m2)








System heat consumption 21,848 BTU/h





65

Configuration Item Value

Single point of load 1452 kg/m2 (3201.08lb/m2)

Evenly distributed load 726 kg/m2 (1600.54 lb/m2)w






Overall power consumption 10,457 W




Single point of load 1044 kg/m2 (2301.60lb/m2)






Heat dissipation 590 CFM (25oC or oF)and 1100 CFM (35oCor 95oF)





66

Table 4-4 A-Node specifications

Item Value

Hardwaremodel

T3200 G3

Equipment Dimensions (H x W xD)

86.1 mm x 446.0 mm x 582.0 mm (3.39 in. x 17.56in. x 22.91 in.)

Weight ≤ 21 kg (46.29 lb)

System heatconsumption

856 BTU/h

Powersupply

Input voltage range 100 V AC to 240 V AC

Frequency range 50 Hz to 60 Hz

Maximum powerconsumption

350 W

Power moduleredundancy mode

1+1 redundancy

Environment

Temperature Operating temperature:

l 0 m to 1800 m (0 ft. to 5905.44 ft.): 5oC to 35oC(41oF to 95oF)

l 1800 m to 3000 m (5905.44 ft. to 9842.4 ft.): Thehighest temperature at which the device remainsfunctional decreasing by 1oC (1.8oF) with everyincrease of 220 m (721.78 ft.) in altitude

Storage temperature: -40oC to +70oC (-40oF to+158oF)

Humidity Operating humidity: 20% RH to 80% RH(noncondensing)Storage humidity: 5% RH to 95% RH(noncondensing)

Operating altitude ≤ 3000 m (9842.4 ft.)

Performance Disk compatibility Two 300 GB SAS disks as system disks configuredfor RAID 1

Table 4-5 UDSN specifications

Item Value

Hardwaremodel

UDSN0750XGE



67

Item Value


176.5 mm x 446 mm x 790 mm (6.95 in. x 17.56 in.x 31.10 in.)

Weight Unloaded (without cable trays and guide rails): ≤36.5 kg (80.47 lb)Fully loaded (without cable trays and guide rails):≤ 98 kg (216.05 lb)Smart disk: 0.8 kg (1.76 lb)/diskGuide rail: 6.5 kg (14.33 lb)/pair


4433 BTU/h

Heat dissipation 180 CFM

Powersupply

Input voltage range 100 V AC to 127 V AC, or 200 V AC to 240 V AC

Power consumption Maximum power consumption: 1350 WTypical power consumption: 1100 WPower consumption in idle mode: 1080 WPower consumption in standby mode: 165 W


2+2 redundancy

Environment


l 0 m to 1800 m (0 ft. to 5905.44 ft.): 5oC to 35oC(41oF to 95oF)



Humidity Operating humidity: 20% RH to 80% RH(noncondensing)Storage unit: 5% RH to 95% RH (noncondensing)


Performance Disk compatibility 3.5-inch 4 TB 7.2k rpm SATA disk



68

Table 4-6 Access switch specifications

Item Value

Hardwaremodel

S6324-EI


43.6 mm x 442.0 mm x 420.0 mm (1.72 in. x 17.40in. x 16.54 in.)

Weight Unloaded: ≤ 5 kg (11.02 lb)

Fully loaded: ≤ 8.5 kg (14.33 lb)


523 BTU/h

Powersupply

Input voltage range 100 V AC to 240 V AC

Maximum powerconsumption

153.6 W


1+1 redundancy

Environment


l 0 m to 1800 m (0 ft. to 5905.44 ft.): -5oC to+50oC (23oF to 122oF)



Humidity Operating humidity: 10% RH to 90% RH(noncondensing)Storage unit: 10% RH to 90% RH (noncondensing)


4.3 Environmental RequirementsThis section describes the requirements of the UDS on temperature, humidity, contaminants,heat dissipation, and noise to help you maintain favorable operating conditions.

Temperature and HumidityTable 4-7 describes the requirements on ambient temperature and humidity.



69

Table 4-7 Requirements on ambient temperature and humidity

Item Sub-Item Requirement

Temperature Operating temperature 5°C to 40°C (41°F to 104°F) whenthe altitude is lower than 1800 m(5905.44 ft.)

5°C to 30°C (41°F to 86°F) whenthe altitude is between 1800 mand 3000 m (5905.44 ft. and9842.4 ft.)

Storage temperature -40°C to +70°C (-40°F to 158°F)

Humidity Operating humidity 10% RH to 90% RH

Storage humidity 5% RH to 95% RH

Particle ContaminantsThe concentration level of particle contaminants in the data center must meet the requirementslisted in the white paper entitled 2011 Gaseous and Particulate Contamination Guidelines forData Centers published by American Society of Heating Refrigerating and Air-conditioningEngineers (ASHRAE) Technical Committee (TC) 9.9.

ASHRAE, affiliated to International Organization for Standardization (ISO), is an internationalorganization operated for the exclusive purpose of advancing the arts and sciences of heating,ventilation, air-conditioning, and refrigeration (HVAC & R). The Gaseous and ParticulateContamination Guidelines for Data Centers is prepared by the members of ASHRAE TC 9.9:AMD, Cisco, Cray, Dell, EMC, Hitachi, HP, IBM, Intel, Seagate, SGI, and Sun and is widelyaccepted in the industry.

According to the Guidelines, particle contaminants in the data center must meet the cleanlinessrequirements of ISO 14644-1 Class 8:l Each cubic meter of air contains no more than 3,520,000 particles equal to or greater than

0.5 μm in size.l Each cubic meter of air contains no more than 832,000 particles equal to or greater than 1

μm in size.l Each cubic meter of air contains no more than 29,300 particles equal to or greater than 5

μm in size.

You are recommended to use an efficient filter to process the air flowing into the data centerand to use a filtering system to periodically clean the air in the data center.

ISO 14644-1 Cleanrooms Associated Controlled Environments-Part 1: ISO 14644-1Cleanrooms and Associated Controlled Environments - Part 1: Classification of Air Cleanlinessis the prime global standard that classifies air cleanliness into several levels based on particleconcentration. Table 4-8 lists the air cleanliness classification by particle concentration.



70

Table 4-8 Air cleanliness classification by particle concentration

ISOClass

Maximum Allowable Concentrations (Particles/m3) for Particles EqualTo and Greater Than the Following Sizes

≥ 0.1 μm ≥ 0.2 μm ≥ 0.3 μm ≥ 0.5 μm ≥ 1 μm ≥ 5 μm

Class 1 10 2 - - - -

Class 2 100 24 10 4 - -

Class 3 1000 237 102 35 8 -

Class 4 10,000 2,370 1,020 352 83 -

Class 5 100,000 23,700 10,200 3520 832 29

Class 6 1,000,000 237,000 102,000 35,200 8320 293

Class 7 - - - 352,000 83,200 2930

Class 8 - - - 3,520,000 832,000 29,300

Class 9 - - - - 8,320,000 293,000

Corrosive GasesTable 4-9 lists common corrosive gases and their sources.

Table 4-9 Common corrosive gases and their sources

Gas Source

H2S Geothermal emissions, microbiological activities, fossil fuelprocessing, wood rot, sewage treatment

SO2 and SO3 Coal combustion, petroleum products, automobile emissions, oresmelting, sulfuric acid manufacture

S Foundries, sulfur manufacture, volcanoes

HF Fertilizer manufacture, aluminum manufacture, ceramicsmanufacture, steel manufacture, electronics device manufacture

NOx Automobile emissions, fossil fuel combustion, chemical industry

NH3 Microbiological activities, sewage, fertilizer manufacture,geothermal emissions, refrigeration equipment

C Incomplete combustion (aerosol constituent), foundry

CO Combustion, automobile emissions, microbiological activities,tree rot



71

Gas Source

Cl2 and CIO2 Chlorine manufacture, aluminum manufacture, zinc manufacture,refuse decomposition

HCI Automobile emissions, combustion, forest fire, oceanicprocesses, polymer combustion

HBr and HI Automobile emissions

O3 Atmospheric photochemical processes mainly involving nitrogenoxides and oxygenated hydrocarbons

CNHN Automobile emissions, animal waste, sewage, tree rot

The concentration level of corrosive gases in the data center must meet the requirements listedin the white paper entitled Gaseous and Particulate Contamination Guidelines for DataCenters published in 2011 by American Society of Heating Refrigerating and Air-conditioningEngineers (ASHRAE) Technical Committee (TC) 9.9.

According to the guidelines, corrosive gases in the data center must meet the followingrequirements:

l Copper corrosion rate

Less than 300 Å/month, meeting the requirement of ANSI/ISA-71.04-1985 severity G1

l Silver corrosion rate

Less than 200 Å/month.

NOTE

Å (Ångström) is a unit of length. One Å equals 1/10,000,000,000 meter.

According to ANSI/ISA-71.04-1985 Environmental Conditions for Process Measurement andControl Systems: Airborne Contaminants, the gaseous corrosivity levels are G1 (mild), G2(moderate), G3 (harsh), and GX (severe), as described in Table 4-10:

Table 4-10 Gaseous corrosivity levels of ANSI/ISA-71.04-1985

SeverityLevel

CopperReactivity Level

Description

G1 (mild) 300 Å/month An environment sufficiently well-controlled suchthat corrosion is not a factor in determiningequipment reliability.

G2 (moderate) 300 Å/month to1000 Å/month

An environment in which the effects of corrosion aremeasurable and may be a factor in determiningequipment reliability.

G3 (harsh) 1000 Å/month to2000 Å/month

An environment in which there is high probabilitythat corrosive attack will occur.



72

SeverityLevel

CopperReactivity Level

Description

GX (severe) > 2000 Å/month An environment in which only specially designedand packaged equipment would be expected tosurvive.

Table 4-11 describes the requirements on the copper and silver corrosion rates.

Table 4-11 Requirements on corrosive gas concentration in a data center

Group Gas Unit Concentration

Group A H2S ppba < 3

SO2 ppb < 10

Cl2 ppb < 1

NO2 ppb < 50

Group B HF ppb < 1

NH3 ppb < 500

O3 ppb < 2

a: Parts per billion (ppb) is the number of units of mass of a contaminant per 1000 millionunits of total mass.

Group A and group B are common gas groups in a data center. Group A's or group B'sconcentration limit values that correspond to copper reactivity level G1 are calculated on thecondition that relative humidity in the data center is lower than 50% and that the gases in thegroup interact with each other.

Corrosion is not determined by a single factor, but by comprehensive environmental factors suchas temperature, relative humidity, corrosive gases, and ventilation.

Heat DissipationThe UDS is equipped with six fans for heat dissipation. It can run steadily for a long time at anambient temperature of 5°C to 40°C (41°F to 104°F) at an altitude below 1800 m (5905.44 ft.)or at an ambient temperature of 5°C to 30°C (41°F to 86°F) at an altitude between 1800 m to3000 m (5905.44 ft. to 9842.4 ft.).

To prevent the exhausted hot air from entering the air intake vent of another cabinet, separateventilation channels for hot air and those for cool air, and install hot-air extractors in the ceiling.



73

CAUTIONIf the UDS is stationed on a raised floor, you are advised to install a vented floor panel in frontof each cabinet to achieve even heat dissipation, avoiding damage caused by overheated parts.

To facilitate maintenance, ventilation, and heat dissipation, comply with the following ruleswhen installing the UDS into the cabinet:

l Keep cabinets at least 100 cm (39.37 in.) away from the surrounding walls and a clearanceof at least 120 cm (47.24 in.) between each other for smooth ventilation.

l Do not keep enclosed space in a cabinet to maintain a convective air transfer between thecabinet and the equipment room, you are recommended to leave 1 U (1 U = 44.45 mm or1.75 in.) space above and below each device.

NoiseDisks and fans, especially fans, emit noise when they are working.

Table 4-12 lists the parameter of noise generated by the UDS when the ambient temperature is25°C (77°F).

Table 4-12 UDS noise specifications

Item Value

Noise power < 72 dBA



74

5 Standards and Certifications

About This Chapter

This chapter describes the standards compliance and certifications related to electromagneticcompatibility (EMC), security, and environment of the UDS.

5.1 Standards ComplianceThis section describes the industry standards that the storage system complies with.

5.2 CertificationsThis section describes the certifications that the storage system has passed.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description 5 Standards and Certifications


75

5.1 Standards ComplianceThis section describes the industry standards that the storage system complies with.

Protocol StandardsTable 5-1 lists the protocol standards that the UDSN complies with.

Table 5-1 Protocol standards that the UDSN complies with

Name Standard No.

IEEE system IEEE 802.3

IEEE 802.3u

IEEE 802.3z

IEEE 802.3ab

IEEE 802.3ae

IEEE 802.3ad

IEEE 802.3ah

IEEE 802.1x

IEEE 802.1Q

IEEE 802.1ag

IEEE 1588 and IEEE 802.1AS

RFC3176 sFlow traffic monitoring

IEEE 802.1D

IEEE 802.1S

IEEE 802.1W

IEEE 802.1ad

IEEE 802.1ah

IEEE 802.1Qay

IEEE 1149.1-2001

SCSI system SATA II Phase 1 specifications

TCP/IP system SNMP trap RFC2578

IPMI 2.0

PCIe system PCI Express Base Specification R1.1



76

Name Standard No.

HTTP HTTP 1.1

SOAP SOAP 1.2

Table 5-2 lists the protocol standards that the A-Node complies with.

Table 5-2 Protocol standards that the A-Node complies with

Name Standard No.

IEEE system IEEE 802.3

IEEE 802.3u

IEEE 802.3z

IEEE 1149.1-2001

IPMI2.0 Intelligent Platform Management Interface Specification SecondGeneration v2.0, Document Revision 1.0, February 12, 2004

SMBIOS System Management BIOS (SMBIOS) Reference Specification,Version 2.5, Status: Final Standard, September 5, 2006

SAS2.1 Information technology-Serial Attached SCSI-2

ACPI Advanced Configuration and Power Interface Specification, Revision3.0, September 2, 2004

IP RFC0791: Internet Protocol

HTTP HTTP 1.1

SOAP SOAP 1.2

Safety and EMC Standards

Table 5-3 lists the safety and EMC standards that the storage system complies with.

Table 5-3 Safety and EMC standards

Name Standard No.

China safety standard GB 4943

North America safetystandard

UL 60950-1

European safety directive LVD 2006/95/EC



77

Name Standard No.

European safety standard EN 60950-1

China EMC standard GB9254-2008 (idt CISPR 22: 2006)

GB17625.1-2003 (idt IEC 61000-3-2: 2001)

Canada EMC standard ICES-003: 2004

CAN/CSA-CEI/IEC CISPR 22:02

North America EMCstandard

FCC, CFR 47 Part 15, Subpart B

European EMC directive EMC Directive 2004/108/EC

European EMC standard EN 55022

EN 55024

Industry StandardsTable 5-4 lists the industry standards that the storage system complies with.

Table 5-4 Industry standards

Name Standard No.

Procedure for failure modesand effects analysis (FMEA)

IEC 812

Presentation of reliability,maintainability andavailability predictions

IEC 863

ETSI standard(environment)

ETS 300 019

ETSI standard (power) ETS 300 132

ETSI standard (noise) ETS 300 753

ETSI standard(environment)

ETS 300 119

ETSI standard (grounding) ETS 300 253

ITUT standard (grounding) ITUT K.27

Environmental protection ECMA TR/70

Reliability GR-929, Telcordia SR-332



78

Name Standard No.

Clean room and relatedcontrolled environments

ISO 14664-1 Class8

Airborne contaminants andenvironment standards

ANSI/ISA-71.04-1985 severity level G1

5.2 CertificationsThis section describes the certifications that the storage system has passed.

Table 5-5 lists the reliability certifications that the storage system has passed.

Table 5-5 Reliability certifications

Name Icon Description

CB None The IEC System for Conformity Testing andCertification of Electrical Equipment(IECEE) is based on the use of specific IECstandards for electrical equipment. TheCertification Bodies (CB) Scheme isapplicable to electrical equipment within thescope of IEC standards for safety, acceptedfor use in the IECEE. The Scheme becomesoperative for such standards as soon as at leastone National Certification Body has declaredtheir recognition of CB Test Certificates. TheCB scheme is designed for eliminating theinternational commerce barriers resultedfrom the compliance with certifications andapproval guidelines of different countries.The CB Scheme is based on IEC standards. Ifmember countries' national standards are notcompletely consistent with IEC standards, thedifferences are allowed but must be disclosedto the other members. A CB test certificate isused in the Scheme to prove that a testedproduct sample has passed CB tests and meetsrelated IEC and member countries'requirements.



79


CCC CCC stands for China CompulsoryCertification.According to Regulations on CompulsoryProduct Certification issued by GeneralAdministration of Quality Inspection,Supervision and Quarantine of the People'sRepublic of China, Certification andAccreditation Administration of the People'sRepublic of China organizes and implementsCCC of products related to human health andsafety, animal and plant life and health,environmental protection, and publicsecurity.

FCC None Federal Communications Commission(FCC) authorizes and manages all RFtransmission facilities and devices except forthose used by the federal government. It isalso responsible for the environmentaldamages generated by the facilities anddevices it approves.

IC None Industry Canada (IC) sets up the teststandards for analog and digital terminaldevices and specifies corresponding EMCcertificates that all import electronic productsmust obtain.

UL Underwriters Laboratories Inc. (UL): The ULis a non-profit agency engaged in productsafety testing.UL is a certification method of AmericanNationally Recognized Testing Laboratory(NRTL). UL has its own certification systemfor the entire system, components, andmaterials. All electric products that areexported to the USA must pass the ULcertification.



80


CE Conformite Europeenne (CE): Productsmarked with CE conform to EMC (2004/108/EC) and low-voltage (2006/95/EC)specifications published by EU.If this product has telecommunicationfunctionality, the R_TTE Directive (1999/5/EC) that complies with the directivesmentioned previously implies conformity tothe following European norms (inparentheses are the equivalent internationalstandards and regulations):l EN 55022 (CISPR 22)-Electro Magnetic

Interferencel EN 55024 (IEC61000-4-2, 3, 4, 5, 6, 8,

11)-Electro Magnetic Immunityl EN 60950 (IEC 60950)-Product Safety

CU The Customs Union comprised of Russia,Belrus, and Kazakhstan comply with theTechnical Regulations of the Customs Unionon Safety of Low-Voltage Equipment that hasbeen compulsively effective since February15, 2013. The technical regulations cover anextensive range of electrical products thatwork under the voltage from 50 V AC to 1000V AC and from 75 V DC to 1500 V DC,including household appliances, audio andvideo devices, IT devices, and lightingdevices. CU's certificate is valid for fiveyears.

C-TICK A mandatory certification issued byAustralian Communications Authority(ACA) for communication equipment,mainly concerning EMC requirements.

SONCAP None As required by Standards Organization ofNigeria, products exported to Nigeria must becertified by SON Conformity AssessmentProgram (SONCAP) before customclearance. As SONCAP aims at protectinghuman safety, its standards are alsoconcerned about safety requirements inaddition to performance.



81


SASO None Saudi Arabian Standards Organization(SASO), authorized by Saudi Arabiangovernment, organizes and implementsInternational Conformity CertificationProgram (ICCP) for market access. Productsexported to Saudi Arabia must meet SASO'smarket access requirements and obtain theCOC certificate before custom clearance.

MexicoCOC

None On august 17, 2010, Mexico governmentissued a new resolution. In this resolution,Mexico announced that Mexico recognizesNRTL certificates corresponding to NOM001/016/019 standards and that importers canuse COC certificates issued by NRTLorganizations for custom clearance.

VCCI None Voluntary Control Council for Interference(VCCI) is a Japanese organization governingelectromagnetic interference.

Table 5-6 describes the environmental protection certifications that the storage system haspassed.

Table 5-6 Environmental protection certifications


REACH None REACH is short for REGULATIONconcerning the Registration, Evaluation,Authorization and Restriction of Chemicalsof the European Union (EU). REACHrequires all chemical products that are bothimported and produced in Europe must beregistered, assessed, authorized, andrestricted. In this way, customers can easilyrecognize the chemical elements. Therefore,both humans and environment are protected.



82


RoHS The restriction of the use of certain hazardoussubstances in electrical and electronicequipment (RoHS) is the directive thatrestricts the use of certain hazardoussubstances in the electrical, electronicequipment.RoHS is an EU compulsory standard that isdesigned to regulate the materials and thetechnical standard of the electrical andelectronic products. In this way, it does goodto human health and environment protection.That is, the six hazardous substances of lead(Pb), mercury (Hg), cadmium (Cd),hexavalent chromium (Cr6 +),polybrominated biphenyl (PBB),polybrominated diphenyl ethers (PBDE)cannot exceed the specified limits.

WEEE The EU Directive on Waste of Electric andElectronic Equipment.Electrical and electronic products sold in theEU market must comply with this directiveand have the mark of cross out wheeled bin.



83

A How to Obtain Help

If a problem persists in routine maintenance or troubleshooting, contact Huawei for technicalsupport.

A.1 Preparations for Contacting HuaweiTo better solve the problem, you need to collect fault information and prepare for commissioningbefore contacting Huawei.

A.2 How to Use the DocumentHuawei provides guide documents shipped with the device. The guide documents can be usedto handle the common problems occurring in daily maintenance or troubleshooting.

A.3 How to Obtain Help from the WebsiteHuawei provides users with timely and efficient technical support through the local offices,secondary technical support system, and remote and onsite technical support.

A.4 Ways to Contact HuaweiHuawei Technologies Co., Ltd. provides customers with comprehensive technical support andservice. For any assistance, contact our local offices or company headquarters.

HUAWEI OceanStor UDS Massive Storage SystemProduct Description A How to Obtain Help


84

A.1 Preparations for Contacting HuaweiTo better solve the problem, you need to collect fault information and prepare for commissioningbefore contacting Huawei.

A.1.1 Collecting Fault InformationYou need to collect fault information before troubleshooting.

You need to collect the following information:

l Name and address of the customer

l Contact person and telephone number

l Time when the fault occurred

l Description of the fault symptom

l Device type and software version

l Measures taken after the fault occurred and results

l Severity and expected settling time

A.1.2 Preparing for CommissioningWhen you contact Huawei for help, the technical support engineer of Huawei might assist youto do certain operations to collect more fault information or rectify the fault.

Before contacting Huawei for help, you need to prepare the boards, interface modules,screwdrivers, screws, serial cables, network cables, and other required materials.

A.2 How to Use the DocumentHuawei provides guide documents shipped with the device. The guide documents can be usedto handle the common problems occurring in daily maintenance or troubleshooting.

To better solve the problems, use the documents before you contact Huawei for technical support.

A.3 How to Obtain Help from the WebsiteHuawei provides users with timely and efficient technical support through the local offices,secondary technical support system, and remote and onsite technical support.

Huawei technical support system includes:

l Huawei headquarters technical support department

l Local office technical support center

l Customer service center

l Technical support website: http://support.huawei.com/enterprise/

You can query how to contact local Huawei offices at http://support.huawei.com/enterprise/



85

http://support.huawei.com/enterprise/

http://support.huawei.com/enterprise/

A.4 Ways to Contact HuaweiHuawei Technologies Co., Ltd. provides customers with comprehensive technical support andservice. For any assistance, contact our local offices or company headquarters.

Huawei Technologies Co., Ltd.

Address: Administration Building, Huawei Technologies Co., Ltd., Bantian, Longgang District,Shenzhen, 518129, P.R.China

Website: http://enterprise.huawei.com



86

http://enterprise.huawei.com

B Glossary

B.1 A-E

B.2 F-J

B.3 K-O

B.4 P-T

B.5 U-Z

HUAWEI OceanStor UDS Massive Storage SystemProduct Description B Glossary


87

B.1 A-E

A

A-Node See access node

access node A computing server dedicated to the UDS. It can be used to deploy the object storageservice controller, service distribution engine, operation and maintenance service, orstorage cluster controller.

access cluster A cluster consists of access nodes (A-Nodes) where object storage service controllers(OSCs) are deployed.

access key ID An ID that confirms the identity of a user accessing the object-based storage system.One access key ID belongs to only one user, but one user can have multiple access keyIDs. The object-based storage system recognizes the users accessing the system by theiraccess key IDs.

active archive The archiving of near-line data that requires central storage after generation but isconstantly invoked for analysis and sharing purposes. Compared with traditional archive,active archive features more data activities and higher added values.

AK See access key ID

B

bucket A container used to store objects. A bucket name must be unique.

C

CDC See Common Data Center

Common Data Center Data centers other than the GADC or GSDC in a multi-data center cluster. There can beno or multiple CDCs.

D

data durability A measurement of data storage reliability that is expressed in percentage (for example,99.999%). Data durability is determined by the reliability of data storage equipment(such as enterprise-level disks or consumer disks) and storage polices (such as the storagein RAID groups or in duplicates).

data rebalancing A data migration technology in a cluster that distributes data evenly across all nodes ina cluster. When a node is faulty or a new node is added to a cluster, data in the cluster isrebalanced.

data self-healing A technology that uses rebalance to automatically migrate data from a faulty node toother nodes in the cluster for self-healing.

data transfer quota A threshold that limits the amount of data traffic users can use in a specified period.



88

deduplication Data de-duplication is a specialized data compression technique for eliminating coarse-grained redundant data, typically to improve storage utilization. In the deduplicationprocess, duplicate data is deleted, leaving only one copy of the data to be stored, alongwith references to the unique copy of data. Deduplication is able to reduce the requiredstorage capacity since only the unique data is stored.

E

EC See Erasure Code

Erasure Code Erasure Code is a feature that stores 1.x duplicates of data to achieve high data reliabilitywith low data redundancy.Objects are divided into data blocks of fixed length. Based onthe algorithm, every M continuous data blocks have N parity blocks. The value of N issmaller than that of M.

B.2 F-J

G

GADC See Global Active Data Center

Global Active DataCenter

A globally unique data center in a multi-data center system. It stores location informationabout all buckets, based on which, all object storage operations initiated to the GADCcan be redirected to specific data centers where the buckets that contain the objects reside.

Global Standby DataCenter

A standby data center that provides backup and disaster recovery for a GADC, preventingservice interruption caused by the failure of the GADC.

GSDC See Global Standby Data Center

I

IAM See identity and access management

identity and accessmanagement

A service module for authenticating and authorizing user permission.

B.3 K-O

L

local centralizedbackup

A technology that backs up an enterprise's data files from the production environmentor office environment to the cloud storage system. After the data files are successfullybacked up, users can access the cloud storage system through the intranet, and downloadthe desired data files to local for use.



89

M

massive resource pool A resource pool in a cloud service solution that provides massive storage space for upper-layer applications to meet their diversified storage requirements. The upper-layerapplications must comply with interface standards (such as Amazon S3, NFS, CIFS, andPOSIX). The platform running the massive resource pool must support the smoothexpansion of capacity and performance, and provide high data security, easy storagemanagement, and optimal energy efficiency.

MDC See Multiple Data Centers

multi-tenant A software architecture technology. It enables multiple tenants to use the same systemor software while separating their data.

Multiple Data Centers The MDC feature enables a customer to deploy multiple data centers across regions toincrease data reliability or unified resource pool management.

O

object A basic data unit in object-based storage. It consists of object data and object metadatathat describes object attributes.

object integrity service A service that protects data integrity. Its repairs the object data fails to be read from orwritten to the storage cluster, and periodically checks and maintains object data.

object storage servicecontroller

An access point of the object storage service that provides the object storage API that iscompatible with Amazon S3. The object storage service controller(OSC) processesrequests initiated by clients and sets up object transmission channels to implement accesscontrol over requests initiated by clients. In addition, it manages metadata, collectsinformation about user traffic and operations, and provides functions such as datarouting, striping, and fragmenting.

object-based storageservice

An object-based cloud storage service. It provides data storage of easy extensibility, highsecurity, proven reliability, and high cost efficiency. Users can manage and use objectsthrough HTTP-based interfaces. The object-based storage service (OBS) is applicableto large-scale data storage services, such as the Internet contents (videos, images, photos,books, media, and magazines), web disks, digital media, backup, and archiving.

OBS See object-based storage service

OIS See object integrity service

OMA See operation and maintenance service agent

OMS See operation and maintenance service

online storage A technology that provides a remote storage space for users to store and manage data inreal time. Users can access data in the space through a web browser, a PC virtual disk,or an intelligent terminal. The most advantage of online storage is that the storage devicesand data are always online, and can be accessed and modified in any time.

operation andmaintenance service

Services performed by the administrator to operate and maintain the system. Thecommon operation and maintenance services include alarming, configuration, statistics,and monitoring.



90

operation andmaintenance serviceagent

An agent deployed on the instance that needs to be operated and maintained, and providesoperation and maintenance services by proxy.

OSC See object storage service controller

B.4 P-T

P

POE See provisioning orchestration engine

provisioningorchestration engine

An engine that provides a service provisioning API to implement user management,including opening, suspending, reinstating, and withdrawing an account, and servicesubscription.

R

remote online backup A data protection technology that backs up data files to a remote storage space throughthe Internet in real time. After the data files are successfully backed up, users can accessthe remote storage space through the Internet, and download the desired data files tolocal for use.

S

sea of disks A unified storage engine of proven reliability, easy extensibility, convenientmaintenance, and high density. It provides key-value storage interfaces for externalapplications, while data storage, replication, consistency check, rebalance, and self-healing for internal data. It, in essence, is a cluster system that consists of self-organization and self-management smart disks.

secret access key An authentication key for a user to access an object-based storage system. A secret accesskey and a request header form a set of authentication information for a user. Secret accesskeys and access key IDs are in one-to-one match.

SK See secret access key

smart disk A disk that combines hardware and software. The hardware consists of a disk, a power-saving CPU, a small memory, and a network adapter. The software provides key-valuestorage interfaces for external applications. A smart disk functions as an independentstorage unit, and can be added to an IP switching network to form a distributed storagecluster.

SoD See sea of disks

space lease service A self service for tenants to manage and use storage space. A tenant can create sub-tenants, and the sub-tenants own specific logical subsets of the tenant's space, and inheritsand adjusts the tenant's storage policy.

storage cluster A storage cluster refers to a cluster consisting of smart disks from universal distributedstorage nodes (UDSNs).



91

storage clustercontroller

A unit that controls storage cluster services. It provides data configuration, faultdiagnosis, and node self-healing for the storage cluster, and load balances storage clusterdata.

storage cluster server A unit that provides storage cluster services. It is usually deployed on smart disks, andprovides key-value storage interfaces for external applications.

storage quota A threshold that limits the capacity of storage space users can use in a specified period.

T

tenant A user of storage resources. The user can have a dedicated storage policy, an SLA,analytical and chargeable resource service units, and a unique access identifier. Thehierarchy of tenants includes tenants and sub-tenants, and tenants can manage sub-tenants.

B.5 U-Z

U

UDS See UDS massive storage system

UDS massive storagesystem

Based on the ARM architecture, the UDS comprises energy-saving and high-densitystorage nodes. It sets up an infrastructural platform for massive object storage byintegrating the object storage, P2P distributed storage engine, and cluster applicationtechnologies. In addition to storing and sharing various data of external applications, thisplatform is applied to various cloud storage solutions including the massive resourcepool, remote online backup, local centralized backup, and active archive to offer a richset of applications such as web disk, cloud backup, unified backup, and datawarehousing.

UDSN See universal distributed storage node

universal distributedstorage node

An energy-saving and high-density storage device dedicated to the UDS. A storage nodemainly consists of self-organization and self-management smart disks.

UPF See user profile function

user profile function A function instance that stores the subscription and authentication data of users.

V

virtual hosting A method that logically divides some or all services of a server into multiple serviceunits, and these service units are represented as multiple servers to the external. In thisway, the server hardware resources are fully utilized. It is applicable to HTTP, FTP, andemail applications.



92

W

web disk An online storage service that provides file management functions such as storage,access, backup, and sharing. A web disk can be considered as a disk located on thenetwork. Users can access the disk from any place where the Internet is available, andmanage, edit the files in the web disk conveniently.



93

Documents

Product Description - Huawei · A.1.2 Preparing for Commissioning ... All smart disks in a UDS system are interconnected to form a distributed node cluster ... Product Description