OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Maintenance Guide 06

OceanStor 5300 V3&5500 V3&5600 V3&5800
V3&6800 V3&6900 V3 Storage System

V300R001
Maintenance Guide
Issue 06
Date 2016-03-01
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2016. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent 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.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://e.huawei.com
Issue 06 (2016-03-01) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System
Maintenance Guide About This Document
About This Document
Intended Audience
This document applies to the system administrators who are responsible for carrying out
routine maintenance activities, monitoring the storage device, and rectifying common device
faults.
This document is intended for:

l Technical support engineers
l Maintenance engineers
Conventions
The purchased products, services, and features are stipulated by the commercial contract
made between Huawei and the customer. All or partial products, services and features
described in this document may not be within the purchased scope or the usage scope. Unless
otherwise agreed by the contract, all statements, information, and recommendations in this
document are provided "AS IS" without warranties, guarantees, or representations of any
kind, either express or implied.
As part of an effort to improve and enhance the product performance and capabilities, Huawei
Technologies Co., Ltd. periodically releases revisions of the hardware and software.
Therefore, some functions described in this document may not be supported by all versions of
the software or hardware currently in use. For the most up-to-date information about product
features, refer to the product release notes.
If a product does not function as described in this document, contact Huawei technical support
engineers.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 06 (2016-03-01)
This is the sixth official release.
Added below contents:
Issue 06 (2016-03-01) Huawei Proprietary and Confidential ii

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide About This Document
l Reclaiming space of a storage system.

l Connection change between the storage system and an application server.
Issue 05 (2015-06-30)
This is the fifth official release.
Optimizes some descriptions in documents.
Issue 04 (2015-01-09)
This is the fourth official release.
Issue 03 (2014-11-05)
This is the third official release.
Modified the section of managing a route.
Issue 02 (2014-08-30)
This is the second official release.
Issue 01 (2014-05-30)
This is the first official release.
Issue 06 (2016-03-01) Huawei Proprietary and Confidential iii

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Introduction to Routine Maintenance....................................................................................... 1
2 Safety Operation Guide............................................................................................................... 2
2.1 Alarm and Safety Symbols............................................................................................................................................. 3
2.2 ESD.................................................................................................................................................................................3
2.3 Using Lasers Safely........................................................................................................................................................ 4
2.4 Using Fibers Safely........................................................................................................................................................ 4
2.5 Short Circuit................................................................................................................................................................... 5
2.6 Operating the Equipment................................................................................................................................................5
3 Logging In to the DeviceManager..............................................................................................7

4 (Optional) Logging In to the DeviceManager Using a Tablet Computer.........................11
5 Routine Maintenance Record....................................................................................................13
6 Powering on or off the Storage Device....................................................................................15
6.1 Powering on the Storage Device.................................................................................................................................. 16
6.2 Powering off the Storage Device..................................................................................................................................17
6.3 Restarting the Storage Device...................................................................................................................................... 17
6.4 Powering off the Storage Device upon an Emergency................................................................................................. 18
6.5 Re-Powering on the Storage Device After an Emergency Power-off.......................................................................... 18
6.6 Powering on Interface Modules....................................................................................................................................19
6.7 Powering off Interface Modules................................................................................................................................... 19
7 Managing Permissions............................................................................................................... 21
7.1 Managing Users............................................................................................................................................................ 22
7.1.1 Creating a User Account............................................................................................................................................22
7.1.2 Modifying Users........................................................................................................................................................ 26
7.1.3 Logging Out a User................................................................................................................................................... 28
7.1.4 Removing a User....................................................................................................................................................... 29
7.1.5 User Permission List..................................................................................................................................................30
7.2 Configuring Security Policy......................................................................................................................................... 36
7.3 Setting Domain Authentication Server Information.....................................................................................................40
7.4 Configuring Authorized IP Addresses..........................................................................................................................45
Issue 06 (2016-03-01) Huawei Proprietary and Confidential iv

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
7.5 Replacing an OceanStor SystemReporter Security Certificate.................................................................................... 46
8 Adjusting Storage Resources.................................................................................................... 48

8.1 Expanding Storage Space............................................................................................................................................. 49
8.1.1 Expanding a Disk Domain.........................................................................................................................................49
8.1.2 Expanding a Storage Pool..........................................................................................................................................50
8.1.3 Expanding a LUN...................................................................................................................................................... 54
8.2 Adjusting Resource Allocation.....................................................................................................................................79
8.2.1 Modifying a Mapping View.......................................................................................................................................80
8.2.2 Adding an Object.......................................................................................................................................................81
8.2.3 Removing Object....................................................................................................................................................... 82
8.2.4 Adding or Removing a Host...................................................................................................................................... 83
8.2.5 Adding a Port.............................................................................................................................................................84
8.2.6 Removing a Port........................................................................................................................................................ 85
8.2.7 Creating SmartErase Task..........................................................................................................................................86
8.2.8 Deleting SmartErase Task..........................................................................................................................................88
8.2.9 Viewing the Mappings Between Host Disks and LUNs............................................................................................89
8.2.10 Viewing the Disk Path Information on a Host.........................................................................................................90
8.3 Changing Links.............................................................................................................................................................91
8.3.1 Managing Routes....................................................................................................................................................... 91
8.3.2 Bonding Ethernet Ports..............................................................................................................................................94
8.3.3 Canceling Ethernet Port Bonding.............................................................................................................................. 96
8.3.4 Modifying an Ethernet Port....................................................................................................................................... 96
8.3.5 Modifying a Fibre Channel Port................................................................................................................................ 98
8.3.6 Naming an iSCSI Device and an iSCSI Initiator.....................................................................................................100
8.3.7 Setting iSNS............................................................................................................................................................ 101
8.3.8 Changing IP Addresses of Management Network Ports......................................................................................... 101
9 Reclaiming Space of a Storage System..................................................................................107

9.1 Reclaiming Space of a Storage System (in Windows)................................................................................................111
9.1.1 Preparing for Space Reclamation (in Windows)......................................................................................................111
9.1.2 Reclaiming Space (in Windows)............................................................................................................................. 112
9.2 Reclaiming Space of a Storage System (in Linux)..................................................................................................... 115
9.2.1 Preparing for Space Reclamation (in Linux)........................................................................................................... 115
9.2.2 Space Reclamation (in Linux)................................................................................................................................. 116
9.3 Reclaiming Space of a Storage System (AIX)............................................................................................................119
9.3.1 Preparing for Space Reclamation (in AIX)..............................................................................................................119
9.3.2 Space Reclamation (in AIX)....................................................................................................................................120
9.4 Reclaiming Space of a Storage System (in HP-UX).................................................................................................. 123
9.4.1 Preparing for Space Reclamation (in HP-UX)........................................................................................................ 123
9.4.2 Space Reclamation (in HP-UX).............................................................................................................................. 124
9.5 Emergency Rollback of Space Reclamation...............................................................................................................127
10 Managing Application-Based Storage Resources............................................................. 129
Issue 06 (2016-03-01) Huawei Proprietary and Confidential v

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
10.1 Managing Microsoft Exchange Instances.................................................................................................................130

10.1.1 Browsing Information About a Microsoft Exchange Instance.............................................................................. 130
10.1.2 Modifying General Properties of a Microsoft Exchange Instance........................................................................ 131
10.1.3 Viewing the Owning Mapping View of a Microsoft Exchange Instance.............................................................. 132
10.1.4 Creating a Microsoft Exchange Snapshot............................................................................................................. 133
10.2 Managing VMware Instances................................................................................................................................... 135
10.2.1 Browsing Information About a VMware Instance................................................................................................ 135
10.2.2 Modifying the General Properties of a VMware Instance.....................................................................................136
10.2.3 Viewing the Owning Mapping View of a VMware Instance................................................................................ 137
10.2.4 Creating a VMware Snapshot................................................................................................................................138
10.3 Managing Hyper-V Instances................................................................................................................................... 140
10.3.1 Browsing Information About a Hyper-V Instance................................................................................................ 140
10.3.2 Modify the General Properties of a Hyper-V Instance.......................................................................................... 141
10.3.3 Viewing the Owning Mapping View of a Hyper-V Instance.................................................................................143
10.3.4 Creating a Hyper-V Snapshot................................................................................................................................ 143
10.4 Managing Oracle Instances...................................................................................................................................... 145
10.4.1 Browsing Information About an Oracle Instance..................................................................................................145
10.4.2 Modifying the General Properties of an Oracle Instance...................................................................................... 146
10.4.3 Viewing the Owning Mapping View of an Oracle Instance.................................................................................. 147
10.4.4 Creating an Oracle Snapshot................................................................................................................................. 148
10.5 Managing SQL Server Instances.............................................................................................................................. 150
10.5.1 Browsing Information About an SQL Server Instance......................................................................................... 150
10.5.2 Modifying the General Properties of an SQL Server Instance.............................................................................. 151
10.5.3 Viewing the Owning Mapping View of an SQL Server Instance..........................................................................153
10.5.4 Creating an SQL Server Snapshot......................................................................................................................... 153
10.6 Managing Application-based Snapshots.................................................................................................................. 155
10.6.1 Viewing Snapshot Information.............................................................................................................................. 155
10.6.2 Managing the Properties of a Snapshot................................................................................................................. 158
10.6.3 Activating a Snapshot............................................................................................................................................ 162
10.6.4 Deactivating a Snapshot........................................................................................................................................ 163
10.6.5 Rolling Back a Snapshot........................................................................................................................................164
10.6.6 Stopping Snapshot Rollback..................................................................................................................................165
10.6.7 Deleting a Snapshot............................................................................................................................................... 166
11 Managing Basic Information About a Storage System.................................................... 168

11.1 Setting Device Time................................................................................................................................................. 169
11.2 Setting Device Information.......................................................................................................................................170
11.3 Managing License Files............................................................................................................................................ 171
11.3.1 Preparations........................................................................................................................................................... 172
11.3.2 Applying for a License.......................................................................................................................................... 172
11.3.3 Importing a License............................................................................................................................................... 177
11.3.4 Activating a License file........................................................................................................................................ 178
11.3.5 Viewing an Activated License File........................................................................................................................178
Issue 06 (2016-03-01) Huawei Proprietary and Confidential vi

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
11.3.6 Backing Up an Active License File....................................................................................................................... 179
12 Obtaining System Version Information............................................................................. 181

12.1 Obtaining Current System Version Information....................................................................................................... 182
12.2 Obtaining System Historical Version Information................................................................................................... 183
13 Viewing System Interface Module Information............................................................... 184

13.1 Viewing Ethernet Port Information.......................................................................................................................... 185
13.1.1 Viewing Ethernet Port Information....................................................................................................................... 185
13.1.2 Viewing Bit Error Statistics................................................................................................................................... 187
13.2 Viewing Fibre Channel Host Port Information.........................................................................................................188
13.2.1 Viewing Fibre Channel Port Information.............................................................................................................. 188
13.2.2 Viewing Bit Error Statistics................................................................................................................................... 190
13.2.3 Querying the WWN of a Fibre Channel Port on an Application Server............................................................... 191
14 Checking the Operating Environment of the Storage Device........................................ 197

14.1 Checking the Equipment Room................................................................................................................................198
14.2 Checking Racks........................................................................................................................................................ 201
15 Checking Indicators................................................................................................................ 204

15.1 Checking Controller Enclosure Indicators (For the 5300 V3 and 5500 V3)............................................................205
15.2 Checking Controller Enclosure Indicators (For the 5600 V3/5800 V3)...................................................................211
15.3 Checking Controller Enclosure Indicators (For the 6800 V3/6900 V3)...................................................................218
15.4 Checking Disk Enclosure Indicators (2U Disk Enclosure)...................................................................................... 224
15.5 Checking Disk Enclosure Indicators (4U Disk Enclosure)...................................................................................... 227
15.6 Checking Disk Enclosure Indicators (High-density Disk Enclosure)...................................................................... 231
16 Checking the Running Status of the Storage Device....................................................... 235

16.1 Checking Controller Enclosures or Disk Enclosures............................................................................................... 237
16.2 Checking Controllers................................................................................................................................................ 238
16.3 Checking Power Modules.........................................................................................................................................239
16.4 Checking Controller Enclosure BBUs......................................................................................................................240
16.5 Checking Fan Modules............................................................................................................................................. 241
16.6 Checking Hard Disks................................................................................................................................................242
16.7 Checking Host Ports................................................................................................................................................. 243
16.8 Checking Interface Modules.....................................................................................................................................244
16.9 Checking Remote Devices........................................................................................................................................246
17 Managing Alarms.................................................................................................................... 247

17.1 Checking Alarms...................................................................................................................................................... 249
17.2 Checking Events....................................................................................................................................................... 250
17.3 Email Notification Management.............................................................................................................................. 252
17.3.1 Enabling the Email Notification Function.............................................................................................................252
17.3.2 Adding Recipient Email Addresses....................................................................................................................... 255
17.3.3 Changing Recipient Email Addresses................................................................................................................... 257
17.3.4 Testing Recipient Email Addresses....................................................................................................................... 258
Issue 06 (2016-03-01) Huawei Proprietary and Confidential vii

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
17.4 SM Notification Management.................................................................................................................................. 258

17.4.1 Enable SM Notification......................................................................................................................................... 258
17.4.2 Adding Recipient Mobile Phone Numbers............................................................................................................260
17.4.3 Changing Recipient Mobile Phone Numbers........................................................................................................ 261
17.4.4 Testing Recipient Mobile Phone Numbers............................................................................................................ 262
17.5 Configuring the System Status Notification Function..............................................................................................262
17.6 Enabling the Syslog Notification Function.............................................................................................................. 263
17.7 Setting the Alarm Buzzer......................................................................................................................................... 264
17.8 Modifying Alarm Dump Settings............................................................................................................................. 265
17.9 Managing Trap IP Addresses....................................................................................................................................269
17.9.1 Adding a Service IP Address.................................................................................................................................269
17.9.2 Changing a Service IP Address............................................................................................................................. 272
17.9.3 Testing Service IP Addresses.................................................................................................................................273
18 Monitoring a Storage System................................................................................................ 275

18.1 Viewing System Information....................................................................................................................................276
18.2 Viewing Power Consumption................................................................................................................................... 278
18.3 Configuring Performance Monitoring Statistics.......................................................................................................279
18.4 Modifying the Settings for Dumping Performance Monitoring Statistics............................................................... 280
18.5 Viewing Performance Monitoring Data....................................................................................................................282
18.6 Monitoring a Storage Pool........................................................................................................................................284
18.6.1 Modifying the Advanced Properties of a Storage Pool......................................................................................... 285
18.6.2 Forecasting Storage Pool Performance..................................................................................................................286
19 Checking the Running Status of Services.......................................................................... 288

19.1 Checking Disk Domain Status..................................................................................................................................290
19.2 Checking Storage Pools............................................................................................................................................290
19.3 Checking LUNs........................................................................................................................................................ 291
19.4 Checking Host Status................................................................................................................................................292
19.5 Viewing Mapping Status.......................................................................................................................................... 293
19.6 Checking Remote Replication Tasks........................................................................................................................ 294
19.7 Checking Consistency Groups..................................................................................................................................295
19.8 Checking Clone Tasks.............................................................................................................................................. 296
19.9 Checking Snapshot Tasks......................................................................................................................................... 297
19.10 Checking LUN Copy Tasks.................................................................................................................................... 298
19.11 Checking HyperMirror Status.................................................................................................................................300
19.12 Checking SmartMigration Status............................................................................................................................301
19.13 Checking Optimization Feature Status................................................................................................................... 302
20 Collecting Information and Reporting a Fault.................................................................. 304

20.1 Types of Information to Be Collected...................................................................................................................... 306
20.2 Exporting System Data............................................................................................................................................. 307
20.3 Backing Up Storage System Configuration Data..................................................................................................... 309
20.4 Exporting Alarms and Events...................................................................................................................................309
Issue 06 (2016-03-01) Huawei Proprietary and Confidential viii

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
20.5 Importing Storage System Configuration Data........................................................................................................ 310

20.6 Huawei Technical Support........................................................................................................................................311
21 Connection Change Between the Storage System and an Application Server........... 312
21.1 Operations After an HBA Replacement (in Windows)............................................................................................ 316
21.1.1 Preparing for Configuration (in Windows)............................................................................................................316
21.1.2 Configurations and Operations After an HBA Replacement (in Windows)......................................................... 318
21.2 Operations After an HBA Replacement (in Linux)..................................................................................................319
21.2.1 Preparing for Configuration (in Linux)................................................................................................................. 319
21.2.2 Configurations and Operations After an HBA Replacement (in Linux)............................................................... 320
21.3 Operations After an HBA Replacement (in AIX).................................................................................................... 321
21.3.1 Preparing for Configuration (in AIX)....................................................................................................................321
21.3.2 Configurations and Operations After an HBA Replacement (in AIX)..................................................................323
21.4 Operations After an HBA Replacement (in HP-UX)............................................................................................... 324
21.4.1 Preparing for Configuration (in HP-UX)...............................................................................................................324
21.4.2 Configurations and Operations After an HBA Replacement (in HP-UX)............................................................ 326
21.5 Emergency Rollback of Configurations and Operations After Replacing an HBA................................................. 327
A Alarm Notification Service Configurations........................................................................ 329

A.1 Configuring an FTP Server........................................................................................................................................330
A.2 Configuring an SMTP Server.................................................................................................................................... 331
A.3 Configuring an SMS Modem.....................................................................................................................................332
B How to Obtain Help................................................................................................................. 334

B.1 Preparations For Contacting Huawei......................................................................................................................... 335
B.1.1 Collecting Troubleshooting Information.................................................................................................................335
B.1.2 Making Debugging Preparations............................................................................................................................ 335
B.2 How to Use the Document......................................................................................................................................... 335
B.3 How to Obtain Help from Website............................................................................................................................ 335
B.4 Ways to Contact Huawei............................................................................................................................................336
C Glossary...................................................................................................................................... 337
D Acronyms and Abbreviations................................................................................................ 348
Issue 06 (2016-03-01) Huawei Proprietary and Confidential ix

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 1 Introduction to Routine Maintenance
1 Introduction to Routine Maintenance
Routine maintenance activities are the most common activities for the storage device,
including powering on or off the storage device, managing users, modifying basic parameters
of the storage device, and managing hardware components. This document applies to the
system administrators who are responsible for carrying out routine maintenance activities,
monitoring the storage device, and rectifying common device faults.
Safety Precautions
Follow the safety precautions for the storage device to protect yourself and devices. For
details about the safety precautions, see 2 Safety Operation Guide.
Maintenance Methods
You can maintain the storage system either in graphical user interface (GUI) mode or
command line interface (CLI) mode. This document exemplifies how to perform the routine
maintenance in GUI mode.
Related Information
To obtain detailed information about an feature or function of the storage device, refer to
other product manuals for the device. You can find up-to-date product manuals on our
technical support website: http://support.huawei.com/enterprise/.
Issue 06 (2016-03-01) Huawei Proprietary and Confidential 1

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 2 Safety Operation Guide
2 Safety Operation Guide
About This Chapter
This chapter provides guidelines to safety operations during activities such as installation,
maintenance, and troubleshooting. The guidelines consist of the safety regulations for
personnel and equipment. These guidelines must be followed to avoid personal injury and
equipment damage.
2.1 Alarm and Safety Symbols

When you install or maintain equipment, observe the precautions provided by alarms and
safety symbols to prevent personal injury or equipment damage.
2.2 ESD
When installing or maintaining the equipment, follow the ESD safety precautions to prevent
personal injury or equipment damage.
2.3 Using Lasers Safely
When installing or maintaining the equipment, follow the laser safety precautions to ensure
the safety of personnel and equipment.
2.4 Using Fibers Safely
Use fibers in a safe and correct manner, to ensure the normal operation of the equipment and
to prevent personal injury and equipment damage.
2.5 Short Circuit
When installing or maintaining equipment, use tools according to the regulations to avoid
short circuits.
2.6 Operating the Equipment
When operating the equipment, ensure safety precautions have been taken to prevent personal
injury and equipment damage.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2.1 Alarm and Safety Symbols

When you install or maintain equipment, observe the precautions provided by alarms and
safety symbols to prevent personal injury or equipment damage.
Table 2-1 lists the safety symbols stuck on equipment.
Table 2-1 Safety symbols stuck on equipment

Symbol Description
ESD Protection Symbol

Indicates a caution that you need to wear an electrostatic discharge
(ESD) wrist strap or glove to avoid personal injury or equipment
damage caused by electrostatic.
Enclosure Grounding Symbol

Indicates the position of the grounding point.
System Disk Swap and Install Warning Symbol

Indicates that you should be cautious to swap, install or pull out a
system disk.
2.2 ESD
When installing or maintaining the equipment, follow the ESD safety precautions to prevent
personal injury or equipment damage.
indicates an electrostatic sensitive area. When operating equipment in this area, wear
an ESD wrist strap, ESD clothes, and ESD gloves, to prevent personal injury or equipment
damage. Note the following:
l Do not wear an ESD strap while the equipment is powering on. This may cause a power
shock.
l Do not touch the device with bare hands to avoid damaging the electrostatic sensitive
devices (ESSDs) on the circuit board.
l The electronic line is very prone to electrostatic damage. Wear the ESD wrist strap, ESD
gloves, and ESD clothes properly when handling disks, especially bare disks. Hold only
the edge of the disk.
l Since an ESD wrist strap only prevents static electricity from the body, an ESD clothes is
required to prevent static electricity from clothes.
l Before installing or replacing devices, wear an ESD wrist strap, ESD gloves, and an ESD
clothes to prevent static electricity from causing damage to you and equipment.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l Use special ESD bags to carry or transport the parts.
2.3 Using Lasers Safely

When installing or maintaining the equipment, follow the laser safety precautions to ensure
the safety of personnel and equipment.
Laser safety precautions include:
l Personal injury
l Equipment damage
Personal Injury
DANGER
The laser emitted by the optical transceiver is invisible infrared ray, which may cause
permanent damage to human eyes. Do not look into the optical transceiver during device
maintenance.
Equipment Damage
To prevent equipment damage when you handle the equipment, be aware of the following
precautions:
l The optical transceivers on the equipment or the cables, which are not used, must be
covered with protective caps.
l When removing the cable that connects to the optical interface on the equipment, cover
the interface and the cable with dust-proof caps to prevent dust.
l When you perform the hardware loopback test by connecting the cable to the optical
transceiver, add an attenuator to avoid damage to the optical transceiver as a result of
strong optical power.
l When using the Optical Time Domain Reflectometer (OTDR), disconnect the cable
between the peer equipment and the local equipment to avoid damage to the optical
transceiver as a result of strong optical power.
l Do not remove or insert the optical transceiver connecting to cables at will.
2.4 Using Fibers Safely

Use fibers in a safe and correct manner, to ensure the normal operation of the equipment and
to prevent personal injury and equipment damage.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
DANGER
The laser beam on the optical interface board or from the fiber may cause injuries to eyes. Do
not stare into the optical interface or fiber connector during installation and maintenance of
optical interface boards or fibers.
Cleaning the Fiber Connectors and Optical Interfaces

Use the special cleaning tools and materials to clean the fiber connectors and optical
interfaces. Common tools and materials:
l Special cleaning solvent (Isoamylol is preferred, propyl alcohol is the next, alcohol and
formalin are forbidden.)
l Non-woven lens tissue
l Special compressed gas
l Cotton stick (medical cotton or long fiber cotton)
l Special cleaning roll (used with above mentioned special cleaning solvent)
l Magnifier for optical connectors
Replacing Fibers
Use filter caps to cap the connectors of the fibers that are not used temporarily.
2.5 Short Circuit

When installing or maintaining equipment, use tools according to the regulations to avoid
short circuits.
NOTICE
l Do not place tools on the air intake board of the enclosure. Otherwise, a short circuit may
be caused.
l Do not drop screws into the enclosure or the equipment. Otherwise, a short circuit may
be caused.
2.6 Operating the Equipment

When operating the equipment, ensure safety precautions have been taken to prevent personal
injury and equipment damage.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Power-on and Power-off
DANGER
l Before checking the device and cables, ensure that the system power supply is switched
off. Otherwise, incorrect or loose cable connections may result in personal injury or
equipment damage.
l Do not wear an ESD wrist strap when the equipment is being powered on. This may cause
a power shock.
l Do not swap cables and field replaceable units (FRUs) during system startup. Otherwise,
data loss may occur.
l After you switch off the power supply, wait at least one minute before switching it back
on.
l To avoid disk damage and data loss, do not switch the power supply off while any disk
running indicators are still blinking.
Troubleshooting
DANGER
l Do not touch the connectors of power cables or communication cables. Otherwise, an
electrical shock may result if there is current in the cables.
l Do not touch the device with bare hands in electrostatic sensitive areas. Wear an ESD
wrist strap, ESD gloves, or ESD clothes to prevent personal injury or equipment damage.
When you perform troubleshooting, be aware of the following precautions:

l Do not perform troubleshooting when lightning is present.
l Ensure that the power cable is intact and the grounding measures are safe and effective.
l Keep the troubleshooting area clean and dry.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 3 Logging In to the DeviceManager
3 Logging In to the DeviceManager
The DeviceManager is a device management program developed by Huawei Technologies

Co., Ltd. The DeviceManager has been loaded to the storage system before delivery. You can
log in to the DeviceManager on any maintenance terminal connected to the storage system by
using the management network port IP address of the storage system and the local or domain
user name in a browser.
Prerequisites
Verify that the maintenance terminal meets the following requirements before you use the
DeviceManager software:
l Operating system and browser versions
The DeviceManager is compatible with multiple types of operating systems and
browsers. However, the partially compatible browsers cannot provide guaranteed ease-
of-use experience for using the DeviceManager. Table 3-1 lists the operating systems
and browsers compatible with the DeviceManager.
Table 3-1 Operating systems and browsers compatible with DeviceManager
Operating System Fully Compatible Partially Compatible

Browser Browser
Windows 7 Professional for l Internet Explorer 9 Internet Explorer 8

x86/x64 to 11
l Firefox 24 to 28
l Chrome 27 to 35
Windows Server 2008 R2 l Internet Explorer 9 Internet Explorer 8

Enterprise Edition SP1 for x64 to 11
l Firefox 24 to 28
l Chrome 27 to 35
Mac OS X 10.5 and later Safari 5.5 to 8.0 -
Ubuntu 11 Firefox 24 to 28 -

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l The maintenance terminal communicates with the storage system properly.

l The super administrator can log in to the storage system using the Local user
authentication mode only.
l To use a Lightweight Directory Access Protocol (LDAP) domain user account to log in
to the DeviceManager, you must configure the LDAP server first, then set the LDAP
server parameters and create an LDAP user account on the DeviceManager.
Context
l DeviceManager only supports TSL protocols (including TLS 1.0, TLS 1.1, and TLS
1.2).
l For a 2 U controller enclosure (5300 V3/5500 V3), the default IP addresses of the
management network ports on controllers A and B are respectively 192.168.128.101 and
192.168.128.102, and the default subnet mask is 255.255.0.0. For a 3 U or 6 U controller
enclosure (5600 V3/5800 V3/6800 V3/6900 V3), the default IP addresses of the
management network ports on management modules 0 and 1 are respectively
192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.0.0.
l The default user name and password of the super administrator are admin and
Admin@storage.
l This document uses the Windows operating system as an example to explain how to log
in to the DeviceManager. The login operations on other operating systems need to be
adjusted accordingly.
Procedure
Step 1 Run Internet Explorer on the maintenance terminal.
Step 2 In the address box, type https://XXX.XXX.XXX.XXX:8088 and press Enter.

NOTE
l XXX.XXX.XXX.XXX represents the management network port IP address of the storage system.
l Your web browser may display that the website has a security certificate error. If the IP address is
correct, you can neglect the prompt and continue to access the storage system.
l If you have a usable security certificate, you are advised to use corresponding commands to import
the certificate to improve system security. For details about the corresponding commands, see
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001
Command Reference.
Step 3 Optional: Set the authentication mode and language.

1. Click Advanced.
2. From the Authentication mode list, select the authentication mode.
Local user: You will log in to the storage system in local authentication mode.
The super administrator can log in to the storage system using the Local user
authentication mode only.
LDAP user: You will log in to the storage system in LDAP domain authentication
mode.
You can log in to the storage system in LDAP domain authentication mode only
after the LDAP server is properly configured.
3. Choose a language from the Language list.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Type your user name and password in Username and Password respectively.
NOTE
l In Verification Code, enter the correct verification code.

l If LDAP user is selected, the user name and password must be a domain user name and password.
If you want to log in as the super administrator, the default user name and password are admin and
Admin@storage respectively.
l If the administrator or read-only user forgets the password, ask the super administrator to reset the
password. If you forget the user name or password of the super administrator account, contact
Huawei technical engineers.
l If you enter incorrect passwords a specified number of times (equal to the value specified in
Number of Incorrect Passwords on the Login Policy page), the account is automatically locked
for the period of lock time.
l You must change the default login password immediately when you are logging in to the storage
system for the first time and periodically change your login password in the future. This reduces
the password leakage risks. For details about how to change the password, see OceanStor 5300
V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Maintenance
Guide.
Step 5 Click Log In.

The DeviceManager main window is displayed.
Figure 3-1 shows the main window of the DeviceManager.
Figure 3-1 Main window of the DeviceManager
Table 3-2 describes DeviceManager components.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 3-2 DeviceManager components

No. Name Function
1 Function Displays the graphical user interfaces (GUIs) for completing a

pane specific activity on the DeviceManager.
2 Status bar Shows the name and login time of the currently logged-in user.
3 Navigation Lists available logical functional modules of the storage device.

bar
4 Log out and The log out and help area shows log out button and help button.
help area
5 Fault Displays different severities of device alarms, which can be

statistics checked by users to learn about the running status of the storage
pane device.
----End
Follow-up Procedure
If you need to log out of the DeviceManager, perform the following steps:
1. On the upper-right corner of the DeviceManager, click .

The Confirm dialog box is displayed.
2. Click OK and you have finished logging out the DeviceManager.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System 4 (Optional) Logging In to the DeviceManager Using a
Maintenance Guide Tablet Computer
4 (Optional) Logging In to the

DeviceManager Using a Tablet Computer
You can use a tablet computer to log in to a storage system and conduct basic maintenance
operations, such as checking alarms, performance statistics, and the basic information of the
storage system.
Prerequisites
A Wi-Fi network that is connected to the storage system's management network is available
onsite.
Context
l Customers can use a tablet computer to log in to the storage system through their
wireless routers. You can use iPad Air (Safari) and HUAWEI MediaPad 10 FHD
(Chrome) to log in to the storage system. This section uses iPad as an example to
describe how to log in to the DeviceManager. The login operations on other operating
systems are similar.
enclosure (5600 V3/5800 V3/6800 V3/6900 V3), the default IP addresses of the
management network ports on management modules 0 and 1 are respectively
192.168.128.101 and 192.168.128.102, and the default subnet mask is 255.255.0.0.
l The default user name and password of the super administrator are admin and
Admin@storage.
Procedure
Step 1 Connect the iPad to the Wi-Fi network.
1. On the iPad desktop, choose Settings > WLAN.
The system goes to the WLAN page.

2. In the CHOOSE A NETWORK area, choose the Wi-Fi network.
The Enter Password page is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System 4 (Optional) Logging In to the DeviceManager Using a
Maintenance Guide Tablet Computer
3. In the Password text box, enter the password.

4. Click Join.
The iPad is connected the Wi-Fi network.
Step 2 Log in to the DeviceManager.
1. On the iPad desktop, click Safari.
2. Set Address to https://xxx.xxx.xxx.xxx:8088/ismpad/login.html and click
Go.xxx.xxx.xxx.xxx is the IP address of management port on the storage system.
The DeviceManager login page is displayed.
3. Optional: Select a language from the Language check box.
4. In User Name and Password, enter the user name and password.
NOTE
The default user name and password are admin and Admin@storage.
If a verification code is required, enter the correct verification code.
Change the default login password immediately after you have logged in to the storage
system for the first time. Periodically change your login password. For details about how to
change the password, see 7.1.2 Modifying Users.
5. Click Login.
The system enters the management page, where you can check the alarms, performance
statistics, and the basic information of the storage system.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 5 Routine Maintenance Record
5 Routine Maintenance Record
Print the following table to record the status, remarks, and owner information for the listed
maintenance items.
Item Status Remarks Owner
Checking the equipment Normal Abnormal

room
Checking racks Normal Abnormal
Checking controller Normal Abnormal

enclosure indicators
Checking disk enclosure Normal Abnormal

indicators
Checking alarms Normal Abnormal
Checking events Normal Abnormal
Checking enclosures Normal Abnormal
Checking controllers Normal Abnormal
Checking power modules Normal Abnormal
Checking controller Normal Abnormal

enclosure BBUs
Checking fan modules Normal Abnormal
Checking hard disks Normal Abnormal
Checking host ports Normal Abnormal
Checking interface Normal Abnormal

modules
Checking storage pools Normal Abnormal
Checking LUNs Normal Abnormal

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 5 Routine Maintenance Record
Item Status Remarks Owner
Checking snapshot tasks Normal Abnormal
Checking LUN copy tasks Normal Abnormal
Checking remote Normal Abnormal

replication tasks
Checking consistency Normal Abnormal

groups
Checking clone tasks Normal Abnormal
......
Detected Errors and their solutions:
Known issues:
Verification results:
Date:

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 6 Powering on or off the Storage Device
6 Powering on or off the Storage Device
About This Chapter
Powering on or off the storage device includes powering on or off interface modules and other
hardware components. A correct power-on or power-off procedure effectively avoids device
damage caused by misoperations.
6.1 Powering on the Storage Device

This topic guides you through the process of re-powering on the storage device that has been
powered off.
6.2 Powering off the Storage Device
Respect the correct power-off sequence when you power off the storage device especially for
replacing cabinet subracks or removing power link failures.
6.3 Restarting the Storage Device
If you want to restart the storage system, perform operations described in this section.
6.4 Powering off the Storage Device upon an Emergency
Power off the storage device by learning about the following information when you encounter
critical emergencies.
6.5 Re-Powering on the Storage Device After an Emergency Power-off
Re-power on the storage device that was powered off upon on an emergency by learning
about the following information.
6.6 Powering on Interface Modules
If you want to use an interface module that is powered off, you can power on it on the
DeviceManager.
6.7 Powering off Interface Modules
Before replace the interface module, power off it at first, you can power off it on the
DeviceManager.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
6.1 Powering on the Storage Device

This topic guides you through the process of re-powering on the storage device that has been
powered off.
Prerequisites
The storage device contains coffer disks.
Precautions
Take the following precautions when you power on the storage device:
l Before powering on a dual-controller storage system for the first time or powering on a
dual-controller storage system after the system configurations are cleared, ensure that
controller A is correctly connected and inserted in the controller enclosure. Otherwise,
the storage system cannot be correctly powered on. Before powering on a four-controller
storage system for the first time or powering on a four-controller storage system after the
system configurations are cleared, ensure that controllers A and C are correctly
connected and inserted in the controller enclosures. Otherwise, the storage system cannot
be correctly powered on.
l Do not wear any ESD wrist straps during a power-on to avoid electric shocks.
l Do not remove or insert any optical fibers, network cables, coffer disks, and interface
modules during a power-on to avoid data loss.
l Do not online modify any expansion cable connections after the storage device has been
powered on; otherwise, device failures may occur.
l Complete expansion cable connections for a newly added disk enclosure before you
power on the enclosure. Also, do not modify any expansion cable connections after the
new disk enclosure has been powered on; otherwise, device failures may occur.
The correct storage device power-on sequence is as follows: turning on the external power
switches that map all devices pressing the power button of controller enclosure turning
on the power switches of Ethernet switches or Fibre Channel switches (if they are configured
but not powered on) turning on the power switches of application servers (if they are not
powered on).
Procedure
Step 1 Check that all of the power cables have snapped into place.
Step 2 Check the labels on the power cables and identify the power switches corresponding to those
cables in the power distribution unit (PDU).
Step 3 Sequentially switch on the identified power switches.
Step 4 Press the power button of controller enclosure.

NOTE
l During the power-on, the power indicator of the controller enclosure blinks until the storage
device is fully powered on in five to ten minutes.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Follow-up Procedure
After the storage device has been powered on, verify that the indicator of each hardware
component is in a normal state by referring to 16 Checking the Running Status of the
Storage Device. If you find an anomaly for any indicator, try to rectify it by referring to the
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System
V300R001 Event Reference or OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System V300R001 Troubleshooting.
6.2 Powering off the Storage Device

Respect the correct power-off sequence when you power off the storage device especially for
replacing cabinet subracks or removing power link failures.
Prerequisites
No service is running on the storage device.
Context
The correct power-off sequence is: stopping services running on the storage device
synchronously pressing and holding the power button on controller enclosure for five seconds
wait until the power-off completes, disconnecting the controller enclosure and disk
enclosures from their external power supplies.
To power off the storage device, you can either switch off controller enclosure synchronously
or utilize the DeviceManager. This document exemplifies how to power off the storage device
using the DeviceManager.
Procedure
Step 1 On the navigation bar of the DeviceManager, click .
Step 2 In the function pane, click Power Off Device in the Task area.
The Danger dialog box is displayed.
Step 3 Read the content of the dialog box carefully and select I have read the previous information
and understood subsequences of the operation. to confirm the information.
Step 4 Click OK.
The Success dialog box is displayed indicating the success of powering off the storage device.
Step 5 Click OK and you have finished powering off the storage device.
----End
6.3 Restarting the Storage Device

If you want to restart the storage system, perform operations described in this section.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
No service is running on the storage device.
Precautions
Exercise caution when you restart the storage device as doing so interrupts the services
running on the device.
Procedure
Step 2 In the function pane, click Restart Device in the Task area.
and understood subsequences of the operation. to confirm the information.
Step 4 Click OK.
The Success dialog box is displayed indicating the success of restarting the storage device.
Step 5 Click OK and you have finished restarting the storage device.
----End
6.4 Powering off the Storage Device upon an Emergency

Power off the storage device by learning about the following information when you encounter
critical emergencies.
NOTICE
Powering off the storage device in an irregular way may cause data loss or disrupt the services
for other clients. For this reason, perform this activity only when bodily injury or device
damage is involved.
Follow the electricity guidelines for your equipment room when you power off the storage
device.
6.5 Re-Powering on the Storage Device After an

Emergency Power-off
Re-power on the storage device that was powered off upon on an emergency by learning
about the following information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Re-powering on the storage device that was powered off in an irregular way may incur
exceptions. If this happens, record the error messages and contact our technical support
engineers for troubleshooting.
To power on a storage system that went through an emergency or unexpected power-off,

follow the correct power-on procedure. Note that you do not need to press the power button
because the engines will automatically power on after being connected to a power supply.
6.6 Powering on Interface Modules

If you want to use an interface module that is powered off, you can power on it on the
DeviceManager.
Procedure
Step 2 On the main window, click Device View to access the front view of the storage device.
Step 3 Click in the front view to switch to the rear view of the storage device.
Step 4 Click the interface module that you want to power on.
Step 5 In the dialog box that is displayed, click Power On.

The Success dialog box is displayed indicating the success of powering on the interface
module.
Step 6 Click OK and you have finished powering on the interface module.
----End
6.7 Powering off Interface Modules

Before replace the interface module, power off it at first, you can power off it on the
DeviceManager.
Prerequisites
All services related to the interface module have been stopped.
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Click the interface module that you want to power off.
Step 5 In the dialog box that is displayed, click Power Off.

and understood subsequences of the operation. to confirm the information. Then, click
OK.
The Success dialog box is displayed indicating the success of powering off the interface
module.
Step 7 Click OK and you have finished powering off the interface module.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 7 Managing Permissions
7 Managing Permissions
About This Chapter
After configuring basic storage services, you can manage user accounts and configure domain
authentication and accessible IP addresses to ensure the security of the storage system.
7.1 Managing Users
To prevent misoperations from affecting device stability and service data security, the storage
device defines three levels of users each with certain permissions.
7.2 Configuring Security Policy
Security policies include the username policy, password policy, login policy and advanced
settings. Security policies are used to protect the system security.
7.3 Setting Domain Authentication Server Information
To centrally manage user information, the DeviceManager allows users to log in to the storage
device in Lightweight Directory Access Protocol (LDAP) server authentication mode.
7.4 Configuring Authorized IP Addresses
To prevent unauthorized IP addresses from accessing DeviceManager, specify the IP
addresses that you permit to access the device from the DeviceManager. This ensures that the
DeviceManager is accessible only to the IP addresses or address segments in the IP address
list.
7.5 Replacing an OceanStor SystemReporter Security Certificate
The OceanStor SystemReporter uses a self-signed certificate, and you can replace the self-
signed certificate with a certificate trusted by the browser. This section describes how to
replace the OceanStor SystemReporter security certificate.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
7.1 Managing Users

To prevent misoperations from affecting device stability and service data security, the storage
device defines three levels of users each with certain permissions.
7.1.1 Creating a User Account

To protect device stability and service data security, create different levels of users based on
your requirements as super administrator. This operation enables you to add local users,
LDAP users, and LDAP user groups.
Prerequisites
A domain authentication server is available for creating LDAP users or LDAP user groups.
Context
The storage device defines the following levels of users:
l Super administrator: The super administrator has full administrative permissions on the
storage device, and is able to create the users at the administrator and read-only user
levels.
l Administrator: An administrator user has partial administrative permissions on the
storage device but cannot manage users, upgrade the storage device, modify system time,
activate license files. Local user administrator cannot import license files, and LDAP
user administrator cannot perform any import or export operation.
l Read-only user: A read-only user has only the access permission on the storage device.
After logging in to the storage device, read-only users can only query information about
the storage device.
For optimal reliability and security, create different user levels to control their operations on
the system.
Procedure
Step 1 Go to the Add User dialog box.
1. On the right navigation bar, click .

2. In the Viewing and Settings area, click Permission Settings.
The Permission Settings page is displayed.
3. In the left navigation tree, select the User Management node.
4. In the right function pane, click Add.
The Add User dialog box is displayed.
Step 2 Set user information.

l Select Local user from the Type list and configure the information about local users.
Table 7-1 describes related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 7-1 Local user parameters

Parameter Description Value
Username Name of a newly created [Value range]

user. The name contains 4 to
32 characters.
The name can only
contain letters, digits,
and underscores (_) and
must start with a letter.
The username must be
unique among all users.
[Example]
test123

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Password Password of a newly created [Value range]

user. The password contains 8
to 16 characters.
The password must
contain special
characters. Special
characters include !"#$
%&'()*+,-./:;<=>?
@[\]^`{_|}~ and spaces.
The password must
contain any two types of
uppercase letters,
lowercase letters and
digits.
The maximum number
of consecutive same
characters cannot exceed
3.
The password cannot be
the same as the
username or mirror
writing of the username.
NOTE
You can modify the password
policy in Configuring
Security Policy.
[Example]
a#123456
Confirm password Password for confirmation. [Value range]

The value must be the same
as that of Password.
[Example]
a#123456

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Level Level of a user. Possible [Example]

values are as follows: Administrator
Administrator: has partial
system administration
permissions. Specifically,
they cannot manage users,
upgrade storage devices,
modify system time,
import and activate
license files.
Read-only user: has only
the access permission for
the storage system and can
perform queries only.
l Select LDAP user or LDAP user group from the Type list and configure the
information about LDAP users or LDAP user groups respectively. Table 7-2 describes
related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 7-2 LDAP user or LDAP user group parameters

Username Name of a newly created LDAP [Value range]

user or LDAP user group. The username contains 1
NOTE to 64 characters.
The LDAP user or LDAP user
group to be created must reside on The username must not
the LDAP domain server. contain spaces, question
Otherwise, the login will fail. marks (?), single
quotation marks ('), or
double quotation marks
(").
The username must be
unique among all users.
[Example]
test123
Level Level of a newly created LDAP [Example]

user or LDAP user group. Administrator
Possible values are as follows:
Administrator: has partial
system administration
permissions. Specifically,
they cannot manage users,
upgrade storage devices,
modify system time, activate
license files, or perform any
import or export operation.
Read-only user: has only the
access permission for the
storage system and can
perform queries only.
Step 3 Confirm the user account creation.

1. Click OK.
The Success message box is displayed, indicating that the operation succeeded.
2. Click OK.
----End
7.1.2 Modifying Users

To ensure the storage system security, you can periodically change the password used for
logging in to the storage system, or the super administrator can adjust levels of lower-level
users or initialize the passwords of them.
Context
l To prevent security risks of the storage system due to password leakage, you need to
periodically change the password used for logging in to the storage system. This

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
operation is applicable to the super administrator, administrators, and read-only users

only.
l When the permissions of an administrator or read-only user do not meet actual
requirements, for example, a user cannot perform some operations on a storage device or
does not need the current permissions, the super administrator can adjust the level of the
current user. This operation is applicable to the super administrator only.
l When an administrator or read-only user forgets the password, the super administrator
can initialize the password. This operation is applicable to the super administrator only.
Procedure
l Change the login password of the current user
a. On the navigation bar of the DeviceManager, click .

b. In the function pane, click Permission Settings in the View and Settings area.
The permission configuration page is displayed.

c. In the navigation tree, choose User Management.
d. In the function pane, select a user name that you want to change and click Modify.
The Modify Password dialog box is displayed.

e. Modify the login password and click OK.
The Success dialog box is displayed indicating that the operation succeeded.
f. Click OK.
The system returns to the permission settings page. You have complete the
password modification.
l Adjust the level of a lower-level user or initialize the password of the user
a. On the navigation bar of the DeviceManager, click .

b. In the function pane, click Permission Settings in the View and Settings area.
The permission configuration page is displayed.

c. In the navigation tree, choose User Management.
d. In the function pane, select a user name that you want to change and click Modify.
The Modify User dialog box is displayed.
To initialize a password, select Initialize Password and enter New Password and
Confirm Password.
NOTE
If you are modifying the information about a LDAP user or LDAP user group, this operation
is unavailable.
e. Modify user information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
n Adjust the level of the current user.

1) In Level, adjust the level of the current user.
NOTE
When a user cannot perform some operations on a storage device or does not
need the current permissions, the super administrator can adjust the level of the
user. Otherwise, there is no need to adjust the user level.
2) Click OK.
The Info dialog box is displayed. Ensure that you have set a correct user
level.
3) Click OK.
The Execution Result dialog box is displayed indicating that the
operation succeeded.
n Initialize the password of the current user.
1) Select Initialize password.
NOTE
When a user forgets the password, the user can initialize the password.
Otherwise, there is no need to initialize the password.
2) Click OK.
The Execution Result dialog box is displayed indicating that the
operation succeeded.
f. Click Close. The user information modification is complete.
----End
7.1.3 Logging Out a User

A super administrator can prevent a logged-in user from using the storage device by forcibly
logging the user out of the DeviceManager.
Prerequisites
l Only a super administrator has the permission to perform this operation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l Users whose Status is Online can be logged out.
Precautions
Logout users are locked for 5 minutes. During that period, the logged-out users cannot log in
to the DeviceManager.
Procedure
Step 1 Go to the Permission Settings page.
1. In the navigation bar on the right, click .

2. In the function pane on the left, click Permission Settings in the Viewing and Settings
area.
Step 2 Force a user offline.
1. In the navigation tree, choose User Management.
2. In the function pane, select a user that you want to log out and click Offline.
NOTE
You can also right-click the user, and choose Offline.
Step 3 Confirm the logout of the user.

1. Carefully read the content in the dialog box and select I have read and understood the
consequences associated with performing this operation. to confirm the information.
2. Click OK.
3. Click OK.
----End
7.1.4 Removing a User

This operation enables you to remove an unwanted user.
Context
l Only a super administrator has the permission to remove the users at the administrator
and read-only user levels.
l Logged-in users cannot be removed.
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Step 2 Remove a user.
1. In the left navigation tree, select the User Management node.
2. In the middle function pane, select the user that you want to remove and click Remove.
Step 3 Confirm the user removal.
1. Confirm the information in the dialog box and select I have read and understood the
consequences associated with performing this operation..
2. Click OK.
3. Click OK.
----End
7.1.5 User Permission List

The storage system defines different management accounts and assigns different configuration
and maintenance permissions to these accounts.
Table 7-3 describes management accounts and password policies supported by the storage
system and provides user login information and configuration suggestions during storage
system maintenance.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 7-3 Login information and recommended configurations

User User Usage Default Default Password
Category Level User Passwor Changing
Name d Methoda
Built-in Root level The user is set _super_ad Admin@r For details about
controller to prevent the min evive how to change the
enclosure super password, see
user administrator OceanStor 5300
from forgetting V3&5500
the password V3&5600
and only can be V3&5800
logged in to V3&6800
through a serial V3&6900 V3
port. The old Storage System
password is V300R001
required when Restricted
the super Command
administrator Reference.
attempts to Contact Huawei
change the technical support.
password. The
user is used to
initialize the
password of the
super
administrator
and change the
password of
root.
Super The user ibc_os_hs Storage@ For details about

administra account can log 21st how to change the
tor level in to the password, see
storage system OceanStor 5300
through SFTP. V3&5500
V3&5600
V3&5800
V3&6800
V3&6900 V3
Storage System
V300R001
Restricted
Command
Reference.
Contact Huawei
technical support.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Name d Methoda
Super The user admin Admin@s For details about

administra completely torage how to change the
tor level controls a password, see
storage system 7.1.2 Modifying
and can create Users.
and manage
administrators
or read-only
users at the
same level or
lower levels
and initialize
the passwords
of users at
lower levels.
Machine- Initializes the mm_user mm_user For details about

machine resource file @storage how to change the
user when password, see
DeviceManage OceanStor 5300
r starts, and V3&5500
achieves some V3&5600
functions of V3&5800
CLI V3&6800
(Command V3&6900 V3
Line Interface) Storage System
or other V300R001
utilities. Command
Reference.
Contact Huawei
technical support.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Name d Methoda
Super The account is administrat Huawei12 For details about

administra used to access or #$ how to change a
tor the BMC password, see
system based OceanStor 5300
on a serial port. V3&5500
NOTE V3&5600
The account is V3&5800
only applicable V3&6800
to 3 U or 6 U V3&6900 V3
controller
Storage System
enclosures.
V300R001
Restricted
Command
Reference.
Contact Huawei
technical support
to obtain related
documents.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Name d Methoda
Super The account is admin Admin@s Method for

administra used to log in torage changing the
tor to disk password:
enclosures and 1. Log in to
2 U controller DeviceManage
enclosures r.
based on a
serial port. 2. Choose
> Viewing
and Settings
> Permission
Settings >
User
Management.
3. Select the user
whose
password you
want to change
and click
Modify.
4. In the Modify
User dialog
box that is
displayed,
change the
password of
the user.
5. Click OK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Name d Methoda
SNMP Administr The account is Kaimse ism@Stor For details about

account ator used to manage age how to change a
the storage password, see
system based OceanStor 5300
on the SNMP V3&5500
protocol. V3&5600
V3&5800
V3&6800
V3&6900 V3
Storage System
V300R001
Command
Reference.
Contact Huawei
technical support
to obtain related
documents.
NOTE
l When the
SNMPv1 and
SNMPv2c
protocols are
used, the
default read
and write
community
strings are
storage_publi
c and
storage_priva
te respectively.
l To ensure data
security, you
are advised to
use the
SNMPv3
protocol. By
default,
SNMPv3 uses
the Kaimse
account to
report trap
alarms.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Name d Methoda
Built-in Super The account is admin Admin@s For details about

SystemRe administra used to log in torage how to change a
porter user tor to the password, see the
OceanStor OceanStor
SystemReporte SystemReporter
r. Security
Hardening Guide.
Contact Huawei
technical support
to obtain related
documents.
a: You are advised to change the default login password immediately after you have logged
in to the storage system for the first time and periodically change your login password in
the future. This reduces the password leakage risks.
7.2 Configuring Security Policy

Security policies include the username policy, password policy, login policy and advanced
settings. Security policies are used to protect the system security.
Procedure
Step 1 Go to the Security Policies page.

2. In the Viewing and Setting area on the function pane, click Permission Settings.
3. In the left navigation tree, select Security Policies.
The Security Policies page is displayed.
Step 2 Configuring the password policy and login policy. Table 7-4 and Table 7-5 describe related
parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 7-4 Password Policy

Min. Length Minimum length of the user password. A [Value range]

complex password is recommended. Its value is an integer
ranging from 8 to 32.
[Default]
8
Max. Length Maximum length of the user password. This [Value range]
parameter prevents administrators from Its value is an integer
configuring lengthy passwords. ranging from 8 to 32.
[Default]
16

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Complexity Complexity of the user password. A complex [Value range]

password is recommended. Must contain special
characters and any two
types of uppercase
letters, lowercase
letters and digits or
Must contain special
characters, uppercase
letters, lowercase
letters and digits
[Default]
Contains special
characters and any two
types of uppercase
letters, lowercase
letters and digits
Number of Maximum number of consecutive duplicate [Value range]

Duplicate characters. Its value is Not limited
Characters or an integer ranging
from 1 to 9.
[Default]
3
Number of Number of retained historical passwords of the [Value range]

Retained account. A new password must be different Its value is an integer
Historical from retained historical passwords. If the ranging from 0 to 30.
Passwords value is 0, the number is not limited.
[Default]
3
Password Setting of the password's validity period. You [Value range]

Validity are advised to enable Password validity Its value is an integer
Period (Days) period. ranging from 1 to 999.
After Password Validity Period is enabled, [Default]
you need to set the password validity days.
After the validity period of a password 90
expires, the system prompts you to change the
password in a timely manner.
Password Number of days prior to password expiration [Value range]

Expiration that the user receives a warning message. Its value is an integer
Warning ranging from 1 to 99.
Period (Days)
[Default]
7

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Min. Minimum lifespan of a password. [Value range]

Password Its value is an integer
Lifespan ranging from 1 to 9999.
(Minutes)
[Default]
5
Table 7-5 Login Policy

Session Duration after which the system indicates [Value range]

Timeout timeout if a logged-in user performs no Its value is an integer
Duration operations during the period. After you click ranging from 1 to 100.
(Minutes) OK in the event of timeout, the system returns
to the login page. [Default]
30
Password Locking a user if the times of consecutively [Default]

Lock inputting incorrect passwords by the user Enabled
exceed Number of Incorrect Passwords
within 10 minutes.
Number of Times allowed for consecutively entering [Value range]

Incorrect incorrect passwords. When incorrect Its value is an integer
Passwords passwords are input exceeds the Number of ranging from 1 to 9.
Incorrect Passwords times, the user is
automatically locked. [Default]
NOTE 3
This parameter is available only when Password
Lock is enabled.
After the user is locked, the super administrator can
manually unlock the user. If the Lock Mode is
Temporary, after the duration is reached, the user
is automatically unlocked.
Lock Mode Mode of automatically locking a user. [Default]

l If you select Permanent, the administrator Temporary
or read-only user will be permanently
locked, the super administrator will be
automatically unlocked after being locked
for 15 minutes.
l If you select Temporary, you can set the
duration of locking the administrator or
read-only user.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Automatic Duration of user locking. After the lock [Value range]

Unlock in duration expires, the locked user is Its value is an integer
(Minutes) automatically unlocked. ranging from 3 to 2000.
l This parameter is available only when [Default]
Password Lock is enabled and Lock
Mode is Temporary. 15
l This parameter is available to automatic

lock only. This parameter is unavailable if
the user is manually locked. A manually
locked user can be manually unlocked
only.
l This parameter is available to the
administrator or read-only user only. The
super administrator will be automatically
unlocked after being locked for 15 minutes
whether you choose Permanent or
Temporary.
NOTE
The administrator or read-only user will be
automatically unlocked in 5 minutes if it is offline
by force.
Step 3 Confirm the operation.

1. Click Save.
The Execution Result dialog box is displayed, indicating that the operation succeeded.
2. Click Close.
----End
7.3 Setting Domain Authentication Server Information

To centrally manage user information, the DeviceManager allows users to log in to the storage
device in Lightweight Directory Access Protocol (LDAP) server authentication mode.
Prerequisites
The LDAP server has been configured.
Context
The LDAP protocol is a TCP/IP network protocol that enables users to access Directory
System Agents (DSAs). It involves some reduced functionality from X.500 DAP
specification.
The complexity of managing networks, especially users, increases as the number of network
applications grows. Most systems that provide a single service implement authentication in
"username-password" mode. However, each user has different permissions on various
network applications, which means each user requires a different username and password for

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
each application. In this condition, users need to enter different usernames and passwords to
access different applications. Then, directory services provided by the LDAP come to address
this issue through the following mechanism.
The principal purpose of LDAP-based authentication applications is to set up a directory-
oriented user authentication system, that is, an LDAP. When a client user needs to access
applications under the environment, the LDAP server compares the username and password
sent by the client with corresponding authentication information in the directory database for
identity verification.
For new-generation storage applications, client hierarchy information is stored in the LDAP
server, and the users who attempt to access the storage device will be authenticated by the
LDAP server.
LDAPS(LDAP over SSL): indicates that the system uses the LDAP over SSL to
communicate with the LDAP domain server if the LDAP domain server supports the SSL.
NOTE
Before selecting the LDAPS protocol, import the CA certificate file for the LDAP domain server.
Procedure

Step 2 Configure an LDAP server.
1. On the left navigation bar, click Domain Authentication Server Settings.
2. Click Add.
The Add dialog box is displayed.
3. In IP Address, enter the IP address of the LDAP server to be added.
4. Click OK.
The IP address is added to the IP Address list.
NOTE
To remove an IP address, select the IP address from the IP Address list and click Remove.
5. Set basis parameters of the LDAP server. Table 7-6 describes related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 7-6 LDAP server parameters

Port Port number of a server. [Value Range]

The default port number of The value ranges from 1 to
the LDAP server is 389, and 65535.
the default port number of the [Example]
LDAPS server is 636.
100
Server Type Type of a server. [Value Range]

Client hierarchy information The value can be Windows
is stored on an LDAP server. AD domain server or LDAP
Users are authenticated by the server.
LDAP server when they [Example]
attempt to access shares.
LDAP server
Protocol Encryption protocol. [Value Range]

NOTE The value can be LDAP or
Security risks arise if the LDAPS.
protocol is set to LDAP. You are
advised to select the LDAPS [Example]
protocol. LDAPS

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Root Directory Root directory of a server. [Example]

Each entry stored in LDAP cn=My
databases requires a unique Application,ou=applications,d
identification. The unique c=bigcorp,dc=com
identification of each entry in
LDAP databases is called its
Distinguished Name (DN).
The top hierarchy in an LDAP
directory tree is called the root
directory.
Bond DN Name of a bonded directory. [Value Range]

The LDAP client initiates a The default access account is
connection request and an administrator account. If
attempts to establish a session you use other account, you
to the LDAP server. This need to ensure that it has
process is also known as permissions of accessing to
bonding. During the bonding, the domain service of the
the client can specify users for LDAP server. The account
them to access directory names cannot contain spaces.
information on the server. To [Example]
access content, you must
search in this directory. cn=My
Application,ou=applications,d
c=bigcorp,dc=com
Bond Password Password for accessing the [Value Range]

bonded directory. It must contain 1 to 63
characters.
[Example]
password
Confirm Bond Confirm the password for [Example]

Password accessing the bonded password
directory.
NOTE
Confirm Bond Password must
be consistent with Bond
Password.
User Directory Directory of a created domain [Example]

user. ou=Users,dc=bigcorp,dc=com
Group Directory Directory of a created domain [Example]

user group. ou=Groups,dc=bigcorp,dc=co
m
6. Click Advanced and set advanced parameters of the LDAP server. Table 7-7 describes
related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 7-7 LDAP server advanced parameters

User ID Properties ID properties of a user. [Example]

This parameter defines the uidNumber
ID of a storage user object
and allows the query of a [Default]
specific user based on the uidNumber (LDAP
given ID. server)
uSNCreated (AD
server)
User Name Properties Name properties of a user. [Example]

This parameter defines the uid
name of a storage user
object and allows the [Default]
query of a specific user uid (LDAP server)
based on the given name. sAMAccountName
(AD server)
User Object Type Type of a user object. Each [Example]

entry under the LDAP posixAccount
directory is associated
with one or more object [Default]
types, including user, posixAccount (LDAP
group, email, and server)
maintenance terminal. user (AD server)
Group ID Properties ID property of a group. A [Example]

group can be composed of gidNumber
many users. This
parameter defines the ID [Default]
of a storage group object gidNumber (LDAP
and allows the query of a server)
specific group based on uSNCreated (AD
the given ID. server)
Group Name Properties Name property of a group. [Example]

This parameter defines the cn
name of a storage group
object and allows the [Default]
query of a specific group gidNumber (LDAP
based on the given name. server)
sAMAccountName
(AD server)

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Group Member Properties Member property of a [Example]

group. This parameter uniqueMember
defines a member of a
storage group. [Default]
uniqueMember (LDAP
server)
member (AD server)
Group Object Type Type of a group object. [Example]

Each entry under the groupOfUniqueNames
LDAP directory is
associated with one or [Default]
more object types, groupOfUniqueNames
including user, group, (LDAP server)
email, and maintenance group (AD server)
terminal.
NOTE
To restore a server to default settings, click Restore Default Settings.
Step 3 Confirm the operation.

1. Click Save.
2. Click Close. You have completed the server settings.
NOTE
After you have finished configuring the LDAP server on the storage system side, you need to log in to
the storage system using the LDAP user name. Therefore, you need to create the LDAP user name or
LDAP user group name on the storage system.
----End
7.4 Configuring Authorized IP Addresses

To prevent unauthorized IP addresses from accessing DeviceManager, specify the IP
addresses that you permit to access the device from the DeviceManager. This ensures that the
DeviceManager is accessible only to the IP addresses or address segments in the IP address
list.
Procedure


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Authorize IP addresses.

1. On the left navigation bar, click Authorized IP Addresses.
2. Select Enable.
3. Click Add.
The Add dialog box is displayed.
4. Enter the IP segment or IP address that is allowed to access the storage system.
To authorize an IP address segment, select By IP address segment and set Start IP
Address and End IP Address. IP addresses included in the IP address segment are
allowed to access the storage device.
To authorize IP addresses, select By IP address and set By IP address.
5. Click OK. The specified IP segment or IP address is added to the IP addresses/address
segments list.
NOTE
To disable an IP address or IP segment from accessing the storage system, select it from the IP
address list and click Remove.
6. Click Save.
Step 3 Click Close.
----End
7.5 Replacing an OceanStor SystemReporter Security

Certificate
The OceanStor SystemReporter uses a self-signed certificate, and you can replace the self-
signed certificate with a certificate trusted by the browser. This section describes how to
replace the OceanStor SystemReporter security certificate.
Prerequisites
The security certificate has been generated.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Context
l A certificate is a declaration with a digital signature from an entity (issuer). The
certificate provides identity authentication for the communications parties.
l Because the self-signed certificate of the OceanStor SystemReporter is not trusted by
users' browser. The users can replace the certificate with a certificate trusted by their
browser.
Procedure
Step 1 Log in as user Administrator to the server where the OceanStor SystemReporter is installed.
Step 2 Go to the installation directory of the OceanStor SystemReporter, for example, C:\Runtime
\bin.
Step 3 Double-click the shutdownSystem.bat file, enter y or Y, and press Enter to disable the
OceanStor SystemReporter service.
Step 4 On the CLI, run cd /DC:\Runtime\bin to switch from the current directory to the installation
directory.
1. On the CLI, run replace_cert.bat XXX, where XXX indicates a customized certificate
key.
2. Type the new location of the certificate file, for example, C:\customStore
\server.keystore, and press Enter.
Step 5 Type y or Y and press Enter to confirm the certificate replacement.
----End
Follow-up Procedure
Restart the OceanStor SystemReporter, then you can use the new certificate to log in.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 8 Adjusting Storage Resources
8 Adjusting Storage Resources
About This Chapter
If a storage system's storage space is insufficient for current services, current resources are
improperly allocated, or network links are changed due to the change of a customer's service
requirements, you can adjust storage resources to ensure the normal and stable running of the
services.
8.1 Expanding Storage Space
If the storage system's storage space cannot meet a customer's service requirements, you can
expand the LUNs, storage pools, or disk domains to ensure the normal and stable running of
the services.
8.2 Adjusting Resource Allocation
If the storage system's current resources cannot meet a customer's service requirements, you
can adjust storage resources to ensure the normal and stable running of the services. Adjusting
resource allocation involves modifying LUN groups, host groups, port groups, and mapping
groups.
8.3 Changing Links
If the storage system's current network links cannot meet a customer's service requirements,
you can adjust storage resources to ensure the normal and stable running of the services.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
8.1 Expanding Storage Space

If the storage system's storage space cannot meet a customer's service requirements, you can
expand the LUNs, storage pools, or disk domains to ensure the normal and stable running of
the services.
In actual services, there are three storage space expansion scenarios:

l Expanding existing LUNs
If existing LUNs are insufficient for service data, but the storage pool where the LUNs
reside has sufficient storage space, you can directly expand the LUNs.
l Expanding a storage pool
If existing LUNs and the storage pool where the LUNs reside are insufficient for
service data, you must expand the storage pool and then the LUNs.
If you want to create one or more LUNs for running services when the storage pool
does not have sufficient storage space, you must expand the storage pool and then
create LUNs.
l Expanding a disk domain
If you want to expand or create a storage pool when the disk domain does not have
sufficient storage space, you must expand the disk domain and then expand or create a
storage pool.
8.1.1 Expanding a Disk Domain

If you want to expand or create a storage pool when the disk domain does not have sufficient
storage space, this operation allows you to increase the storage space of the disk domain.
Prerequisites
Disks used for capacity expansion are available.
Procedure
Step 1 Go to the Expand Disk Pool page.

The Resource Allocation page is displayed.
2. Click Disk Domain.
The Disk Domain page is displayed.
3. Select the disk domain you want to expand and click Expand.
The Expand Disk Domain dialog box is displayed.
Step 2 Select a expansion method.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
The following expansion methods are available:

l Select All available disks to add all available disks to the disk domain.
l Select Specify disk type and add suitable types of disks to the disk domain.
l Select Manually select and click Select.... On the Select Disks page, add disks from
Available Disks to Selected Disks and click OK.
Step 3 Confirm the expansion of the disk domain.
1. Click OK.
2. Click OK.
----End
8.1.2 Expanding a Storage Pool

If you want to expand or create LUNs when the storage pool does not have sufficient storage
space, this operation allows you to increase the storage space of the storage pool.
Prerequisites
The disk domain has available storage space for capacity expansion of the storage pool.
Procedure
Step 1 Go to the Expand Storage dialog box.

2. Click Storage Pool.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
The Storage Pool page is displayed.

3. Select the storage pool you want to expand and click Expand.
The Expand Storage Pool dialog box is displayed.
Step 2 Expand the storage pool.

1. Select the storage tier you want to expand or create.
2. If creating a storage tier, configure the RAID policy and in Capacity, enter the capacity
of the storage tier.
3. If expanding a storage tier, in Added Capacity, enter the added capacity of the storage
tier.
NOTE
l You can create a new storage tier or expand the existing storage tier to expand storage pools. If the
storage pool consists of multiple storage tiers, you are advised to set a SmartTier policy. The policy
enables data to migrate among different types of disks, optimizing storage performance distribution.
l You can configure RAID policy only for new created storage tier. For the storage tier already exists in the
storage pool, you cannot modify its RAID policy.
l The number of RAID data disks of different storage pool tiers must be a multiple of 1, 2, 4, or 8.
Step 3 Optional: If there are multiple storage tiers, you are advised to set a SmartTier policy. The
policy enables data to migrate among different types of disks, optimizing storage performance
distribution. Table 8-1 lists related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 8-1 SmartTier policy of the storage pool
Parameter Description Setting
Service Monitoring Period Period of time during which [Default value]

the service is monitored and I/O monitoring disabled
hotspot statistics is collected
after you select Enable I/O
monitoring. The statistics
serves as guidance for data
to migrate among different
storage tiers.
You can specify the period
by setting days, Start Time,
and Duration.
Data Migration Plan The trigger policy of data [Default value]

relocation between the Manual
storage layers in a storage
pool. The policies include:
l Manual: You must
manually trigger the data
relocation among storage
tiers. The data relocation
process is transparent to
application servers.
Manual data relocation
can be performed
anytime.
l Periodical: You must
specify the start time and
duration of data
relocation for the storage
system to perform data
relocation automatically
at the specified time.
This reduces the
management cost and
complexity. The data
relocation process is
transparent to application
servers. Automatic data
relocation is performed
only at the specified
time.
NOTE
l If Data Migration Plan is set to Periodical, I/Os are monitored on a 7x24 basis by default.
l If the remaining capacity in a storage pool is equal to or smaller than 10% of the total capacity, data does
not migrate in the storage pool.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Optional: If there is new added storage tier, you can click Advanced to set the strip depth for
this tier.
The Advanced Property Setting dialog box is displayed. Table 8-2 describes the related
parameters.
Table 8-2 Strip Depth Parameter
Strip Depth Strip refers to that continuous data is [Default value]

divided into data blocks of the same size System auto select
and data blocks are distributed on different
disks of storage devices. In this way, I/O
loads are balanced among disks, improving
read/write performance.
Strip depth refers to strip size, indicating
the size of data blocks on each disk. Smaller
strip size indicates smaller data blocks.
These data blocks are distributed on more
disks, improving transmission performance.
However, more time is required to find
different data blocks, decreasing disk
locating performance. On the contrary,
fewer data blocks indicate lower
transmission performance but higher disk
locating performance.
The value of this parameter can be:
l System auto select
The system selects the optimal strip
depth based on the RAID policy of the
storage tier and data migration
granularity.
l 32 KB
l 64 KB
l 128 KB
128 KB is recommended for random
read/write services (such as in database
scenarios).
l 256 KB
l 512KB
512 KB is recommended for sequential
read/write services (such as media asset
scenarios)
NOTE
The parameter value cannot be changed after
being determined.
Step 5 Confirm the capacity expansion of the storage pool.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
1. Click OK.
The Warning dialog box is displayed.
2. Confirm the information in the dialog box and select I have read the previous
information and understood subsequences of the operation.
3. Click OK.
The Execution Result dialog box is displayed indicating that the operation succeeded.
4. Click Close.
----End
8.1.3 Expanding a LUN

If the capacity of a LUN is insufficient for service data, this operation allows you to expand
the capacity of the LUN to meet service requirements.
Prerequisites
The storage pool can provide sufficient storage space for LUN expansion.
Context
The following operations must be performed in sequence to expand the LUN:
1. Expand the LUN on the storage system.
2. Configure the application server as required. The configuration of the application server
varies with the operating system running on the application server. For details, see the
corresponding sections.
Locating a LUN to Be Expanded

Before expanding a LUN for storage services, determine information about the LUN where
current service data resides to ensure successful LUN expansion.
Prerequisites
l If a Fibre Channel network is used, ensure that the world wide name (WWN) of a Fibre
Channel initiator has been obtained.
l If an Internet Small Computer Systems Interface (iSCSI) network is used, ensure that the
iSCSI qualified name (IQN) of an iSCSI initiator has been obtained.
Procedure
Step 1 Log in to the CLI as a super administrator.
Step 2 Run the show initiator initiator_type=? [ wwn=? | iscsi_iqn_name=? ] command to query
host information based on the WWN or IQN of an initiator.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
initiator_type=? Type of an initiator. Possible values are FC and

iSCSI, where:
l iSCSI: iSCSI initiator
l FC: Fibre Channel
initiator
wwn=? WWN of a Fibre Channel To obtain the value, run the

initiator. This parameter is show initiator command
valid only when the value of without parameters.
initiator_type=? is FC.
iscsi_iqn_name=? IQN of an iSCSI initiator. To obtain the value, run the

This parameter is valid only show initiator command
when the value of without parameters.
initiator_type=? is iSCSI.
admin:/>show initiator initiator_type=FC wwn=21000024ff53b640
WWN : 21000024ff53b640
Running Status : Online
Free : Yes
Alias : suse2_01
Host ID : 2
Multipath Type : Default
The value of Host ID is the ID of a host corresponding to the WWN.
Step 3 Run the show host lun host_id=? command to view all LUNs mapped to the host in the
storage system.
host_id=? indicates a host ID.
admin:/>show host lun host_id=2
LUN ID LUN Name

------ ------------
34 lun_0000
35 lun_0001
36 lun_0002
The value of LUN ID is the ID of a LUN mapped to the host in the storage system.
Step 4 Run the show lun general lun_id=? command to view the WWN of the LUN mapped to the
host.
Step 5 On the multipathing software of an application server, run the show vlun command to view
the WWN of the LUN.
Step 6 Check whether the two WWNs are the same. If they are the same, you can determine that the
LUN is the one to be expanded.
NOTE
For details about the preceding commands, see the OceanStor 5300 V3&5500 V3&5600 V3&5800
V3&6800 V3&6900 V3 Storage System V300R001 Command Reference.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Expanding a LUN on a Storage System

This operation enables you expand the capacity of a LUN to meet service requirements.
Prerequisites
l The storage system has at least one formatted LUN.
l You cannot expand LUNs for which snapshot, remote replication, clone, LUN copy,
SmartMigration and HyperMirrors has been configured.
Precautions
To ensure data integrity, stop services on the LUN before LUN expansion.
When LUNs of different types are expanded, the capacity that can be expanded is restricted.
Specific conditions are as follows:
l The capacity of a thin LUN is restricted by its specifications and irrelevant to the
remaining capacity of the storage pool.
l The capacity of a thick LUN is restricted by its specifications. It cannot be larger than
the remaining capacity of the storage pool.
Rescan for the LUN on the server side after the capacity expansion.
Procedure
Step 1 Go to the Expand LUN dialog box.

2. Click LUN.
3. Select the LUN that you want to expand and click Expand.
The Expand LUN dialog box is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Set the parameters for expanding the LUN.

1. In the Added Capacity text box, enter the added capacity of the LUN after expansion.
NOTE
The total capacity of the thick LUN after expansion must be smaller than the available
capacity of the storage pool.
The total capacity of the thin LUN after expansion must be smaller than its specifications.
The total capacity of the LUN after expansion must be larger or equal than the original
capacity of the LUN.
2. Select a capacity unit from the drop-down list on the right of Added Capacity.
Possible values are Blocks, MB, GB, or TB.
Step 3 Confirm the LUN expansion.
1. Click OK.
The Info dialog box is displayed.
2. Click OK.
3. Click OK.
----End
Expanding a LUN on an Application Server in Windows

After expanding a LUN on its storage system, perform the expansion configuration on the
corresponding application server for it to identify and use the expanded storage space. This
task uses an application server running Windows Server 2008 as an example to describe how

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
to expand a LUN on an application server. For application servers running other versions of
Windows operating systems, adjust the operations based on actual conditions.
Prerequisites
A LUN has been expanded on the storage system.
Context
In the example of this section, the LUN is mapped as disk 3 on the application server. Its drive
letter is G:\, original capacity is 25 GB, and expanded capacity is 50 GB.
Procedure
Step 1 Log in to the Windows-based application server as administrator.
Step 2 On the Windows desktop, click Start and choose Administrative Tools > Server Manager
from the shortcut menu.
The Server Manager dialog box is displayed.
Step 3 On the left navigation bar of the Server Manager dialog box, right-click Disk Management
and choose Rescan Disks from the shortcut menu.
After the scanning is complete, the system displays the result as shown in Figure 8-1. On the
right of disk G, the capacity of the partition to be expanded is displayed.
Figure 8-1 Disk Scanning Result

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Right-click disk G and choose Extend Volume from the shortcut menu.
The Extend Volume Wizard dialog box is displayed, as shown in Figure 8-2.
Figure 8-2 Extend Volume Wizard
Step 5 Click Next.

The Select Disks page is displayed, as shown in Figure 8-3.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 8-3 Select Disks
NOTE
l Disk 3 is the disk mapped from the LUN to be expanded on the application server.
l You can change the expansion storage space in Select the amount of space in MB to suit your
need. By default, the maximum storage space is used.
Step 6 Click Next.
Step 7 Click Finish.

The Server Manager dialog box is displayed. You have completed configuring LUN
expansion on the application server.
----End
Result
In the Server Manager dialog box, view the capacity of disk G after expansion, as shown in
Figure 8-4.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 8-4 Operation result
Expanding a LUN on an Application Server in SUSE

task uses an application server running SUSE 11.0 as an example to describe how to expand a
LUN on an application server. For application servers running other versions of SUSE
operating systems, adjust the operations based on actual conditions.
Prerequisites
Context
In the example of the section, the capacity of the LUN to be expanded is 25 GB and it will be
expanded to 50 GB. The drive letter of the mapped disk on the application server is sdf.
Procedure
Step 1 Scan for disks on the SUSE-based application server.
1. Scan for disks.
If the UltraPath software is installed, run hot_add command.

If the UltraPath software is not installed, perform the following operations:

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
i. Run lsscsi command to obtain the ID of the host where the LUN resides. The
following is an example.
suse:~ # lsscsi
[5:0:0:0] disk HUAWEI XXXX 2101 /dev/sdf
In the preceding command output, 5 in [5:0:0:0] indicates the host ID, XXXX
indicates a specific product model or brand.
ii. Run echo '- - -' > /sys/class/scsi_host/hostN/scan command, where N
indicates the host ID obtained in the preceding step.
After the scan is complete, the disk capacity remains 25 GB.

2. Run echo 1 > /sys/block/sdf/device/rescan to rescan for disks.
After the scan is complete, the disk capacity becomes 50 GB.
NOTE
sdf is the drive letter of the disk mapped from the LUN on the application server. The actual drive
letter may be different.
Step 2 Run fdisk -l to view the information about all disks on the application server.
suse:~ # fdisk -l
Disk /dev/sdb: 598.0 GB, 597998698496 bytes
255 heads, 63 sectors/track, 72702 cylinders
Units = cylinders of 16065 * 512 = 8225280 bytes
Disk identifier: 0xc433d0ae
Device Boot Start End Blocks Id System

/dev/sdb1 * 1 9 72275+ 83 Linux
/dev/sdb2 10 271 2104514+ 83 Linux
/dev/sdb3 272 72703 581806279 83 Linux
/dev/sdb4 1 1 0+ ee GPT
Partition table entries are not in disk order
Disk /dev/sdf: 53.7 GB, 53687091200 bytes

Disk identifier: 0x00000000
Disk /dev/sdf doesn't contain a valid partition table
Step 3 To add the file system of the LUN to the new storage space, run resize2fs /dev/sdf.
l If the following command output is displayed, the file system is successfully expanded.
suse:~ # resize2fs /dev/sdf
resize2fs 1.41.9 (22-Aug-2009)
Resizing the filesystem on /dev/sdf to 13107200 (4k) blocks.
The filesystem on /dev/sdf is now 13107200 blocks long.
l If the following information is displayed, run the e2fsck -f /dev/sdf command and then
the resize2fs /dev/sdf command.
suse:~ # resize2fs /dev/sdf
resize2fs 1.41.9 (22-Aug-2009)
Please run 'e2fsck -f /dev/sdf' first.
----End
Using LVM to Expand a LUN (in SUSE)

After expanding a LUN on the storage system, perform the expansion configuration on the
corresponding application server to identify and use the expanded storage space. This section
uses SUSE 11.0 as an example to describe how to non-disruptively expand a LUN on an

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
application server using logical volume manager (LVM). For application servers running
other versions of SUSE operating systems, adjust the operations based on site conditions.
Prerequisites
l LUN expansion has completed on the storage system.
l A physical volume to be expanded has been determined.
Context
In the example of the section, sdb5 is a physical volume in the drive letter of the disk mapped
from the LUN on the application server. The primal capacity of sdb5 is 104 MB, and the
capacity after expansion is 120 MB.
Procedure
Step 1 On the application server, view the block device ID of the LUN in the operating system.
1. Run the hot_add command to scan for disks.
2. Run the show vlun command to query the LUN WWN.
UltraPath CLI #0 >show vlun
------------------------------------------------------------------------------
------------------------------------------------------
Vlun ID Disk Name Lun WWN
Status Capacity Ctrl(Own/Work) Array Name Dev Lun ID
0 sda WMQ_LUN_TEST_002 60022a11000beb2a0421c1cc000002d0
Normal 3.00GB 0B/0B Array8.1 --
1tagei sdb WMQ_LUN_TEST_003
60022a11000beb2a0421c2a2000002d1 Normal 3.00GB 0A/0A
Array8.1 --
2 sdc WMQ_LUN_TEST_004 60022a11000beb2a0421c365000002d2
Normal 3.00GB 0B/0B Array8.1 --
3 sdd WMQ_LUN_TEST_005 60022a11000beb2a0421c4bd000002d3
Normal 3.00GB 0A/0A Array8.1 --
------------------------------------------------------------------------------
------------------------------------------------------
Lun WWN is the WWN of a LUN and Disk is the drive letter of a disk mapped from the
LUN on the application server.
Step 2 Run the echo 1 > /sys/block/sdb5/device/rescan command to rescan for disks.
NOTE
sdb5 is a physical volume in the drive letter of the disk mapped from the LUN on the application server.
Adjust configuration operations based on an actual physical volume to be expanded.
Step 3 Run the pvresize /dev/sdb5 command to expand the physical volume.
Step 4 Run the lvextend -L +16M /dev/testvg/testlv command to expand a logical volume.
pro
lvextend -L +16M /dev/testvg/testlv
Extending logical volume testlv to 120.00 MB
Logical volume testlv successfully resized
testlv is a logical volume to be expanded.
Step 5 Run the resize2fs /dev/testvg/testlv command to expand the file system.
resize2fs /dev/testvg/testlv
resize2fs 1.41.9 (22-Aug-2009)

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Resizing the filesystem on /dev/testvg/testlv to 122800 (1k) blocks.

The filesystem on /dev/testvg/testlv is now 122800 blocks long.
----End
Expanding a LUN on an Application Server in RedHat

task uses an application server running Red Hat 6.4 as an example to describe how to expand
a LUN on an application server. For application servers running other versions of Red Hat
Prerequisites
Context
In the example of the section, the capacity of the LUN to be expanded is 25 GB and it will be
expanded to 50 GB. The drive letter of the mapped disk on the application server is sdh.
Procedure
Step 1 Scan for disks on the Red Hat-based application server.
1. Scan for disks.
If the UltraPath software is installed, run hot_add command.
If the UltraPath software is not installed, perform the following operations:
i. Run lsscsi command to obtain the ID of the host where the LUN resides. The
following is an example.
[root@localhost ~]# lsscsi
[5:0:0:0] disk HUAWEI XXXX 2101 /dev/sdh
In the preceding command output, 5 in [5:0:0:0] indicates the host ID, XXXX
indicates a specific product model or brand.
ii. Run echo '- - -' > /sys/class/scsi_host/hostN/scan command, where N
indicates the host ID obtained in the preceding step.
After the scan is complete, the disk capacity remains 25 GB.
2. Run echo 1 > /sys/block/sdh/device/rescan command to rescan for disks.
After the scan is complete, the disk capacity becomes 50 GB.
NOTE
sdh is the drive letter of the disk mapped from the LUN on the application server. The actual drive
letter may be different.
Step 2 Run fdisk -1 to view the information about all disks on the application server.
[root@localhost ~]# fdisk -l
Disk /dev/sdb: 16.1 GB, 16106127360 bytes

Sector size (logical/physical): 512 bytes / 512 bytes
I/O size (minimum/optimal): 512 bytes / 512 bytes

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Disk /dev/sde: 107.4 GB, 107374182400 bytes

Disk /dev/sdh: 53.7 GB, 53687091200 bytes

Step 3 To add the file system of the LUN to the new storage space, run resize2fs /dev/sdh.
[root@localhost ~]# resize2fs /dev/sdh
resize2fs 1.41.12 (17-May-2010)
Filesystem at /dev/sdh is mounted on /fs1; on-line resizing required
old desc_blocks = 2, new_desc_blocks = 4
Performing an on-line resize of /dev/sdh to 13107200 (4k) blocks.
The filesystem on /dev/sdh is now 13107200 blocks long.
----End
Expanding a LUN on an Application Server in Solaris

task uses an application server running Solaris 10 as an example to describe how to expand a
LUN on an application server. For application servers running other versions of Solaris
Prerequisites
l A LUN has been expanded on the storage system.
l Services on the LUN to be expanded have been stopped.
Context
This section uses the default disk-based UNIX File System (UFS) on a Solaris-based
application server as an example to describe how to expand a LUN and its file system on a
raw disk. The LUN will be expanded from 50 GB to 60 GB.
Procedure
Step 1 Run cfgadm -al to scan for the LUNs mapped to the application server.
root@solaris:~# cfgadm -al
Ap_Id Type Receptacle Occupant Condition
c2 scsi-sas connected configured unknown
c2::dsk/c2t6d0 CD-ROM connected configured unknown
c4::w5000cca0258a82e5,0 disk-path connected configured unknown
c5 scsi-sas connected unconfigured unknown
c6::w5000cca02570b521,0 disk-path connected configured unknown
c7 scsi-sas connected unconfigured unknown
c10 fc-private connected configured unknown

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
c10::20080022a10bc14f disk connected configured unknown

c11 fc connected unconfigured unknown
usb0/1 unknown empty unconfigured ok
usb2/2 usb-hub connected configured ok
usb2/2.1 unknown empty unconfigured ok
usb2/2.3 usb-hub connected configured ok
usb2/2.3.1 unknown empty unconfigured ok
usb2/2.3.2 usb-storage connected configured ok
usb2/2.3.3 usb-communi connected configured ok
usb2/2.4 usb-device connected configured ok
usb2/4 usb-hub connected configured ok
Step 2 Run umount /mnt/ to unmount corresponding disks of the LUN that you want to expand on
the application server.
/mnt/ indicates the mount directory of disks of the LUN.

NOTE
If disks of the LUN that you want to expand are not mounted, skip this operation.
Step 3 Run format to query the information about all disks detected by the the application server.
root@solaris:~# format
Searching for disks...done
AVAILABLE DISK SELECTIONS:

0. c0t5000CCA0258A82E4d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> solaris
/scsi_vhci/disk@g5000cca0258a82e4
/dev/chassis//SYS/HDD0/disk
1. c0t5000CCA02570B520d0 <SUN300G cyl 46873 alt 2 hd 20 sec 625> solaris
/scsi_vhci/disk@g5000cca02570b520
/dev/chassis//SYS/HDD4/disk
2. c10t5d0 <drive type unknown>
/pci@400/pci@2/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w20080022a10bc14f,0
3. c10t5d1 <HUAWEI-S5600T-2201 cyl 6398 alt 2 hd 64 sec 256>
/pci@400/pci@2/pci@0/pci@a/SUNW,qlc@0/fp@0,0/ssd@w20080022a10bc14f,1
Specify disk (enter its number):
In the preceding command output, c10t5d1 indicates the driver letter mapped by the LUN to
the application server.
Step 4 After Specify disk (enter its number), enter the corresponding ID 3 of c10t5d1.
Specify disk (enter its number): 3
selecting c10t5d1
[disk formatted]
Note: detected additional allowable expansion storage space that can be
added to current SMI label's computed capacity.
Select <partition> <expand> to adjust the label capacity.
FORMAT MENU:
disk - select a disk
type - select (define) a disk type
partition - select (define) a partition table
current - describe the current disk
format - format and analyze the disk

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
repair - repair a defective sector

label - write label to the disk
analyze - surface analysis
defect - defect list management
backup - search for backup labels
verify - read and display labels
save - save new disk/partition definitions
inquiry - show disk ID
volname - set 8-character volume name
!<cmd> - execute <cmd>, then return
quit
format>
Step 5 Run type to view the disk type.

format> type
AVAILABLE DRIVE TYPES:

0. Auto configure
1. Quantum ProDrive 80S
2. Quantum ProDrive 105S
3. CDC Wren IV 94171-344
4. SUN0104
5. SUN0207
6. SUN0327
7. SUN0340
8. SUN0424
9. SUN0535
10. SUN0669
11. SUN1.0G
12. SUN1.05
13. SUN1.3G
14. SUN2.1G
15. SUN2.9G
16. Zip 100
17. Zip 250
18. Peerless 10GB
19. SUN300G
20. HUAWEI-S5600T-2201
21. other
Specify disk type (enter its number)[20]:
Step 6 After Specify disk type (enter its number)[20]: , enter 0 to automatically update disks, re-
define the disk type, and refresh the disk capacity.
Specify disk type (enter its number)[20]: 0
c10t5d1: configured with capacity of 59.98GB
<HUAWEI-S5600T-2201 cyl 7678 alt 2 hd 64 sec 256>
selecting c10t5d1
[disk formatted]
After the operations are complete, the disk capacity becomes 60 GB.
Step 7 Run partition and then run print to view disk partitions.
format> partition
PARTITION MENU:
0 - change `0' partition
select - select a predefined table
modify - modify a predefined partition table
name - name the current table
print - display the current table

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
label - write partition map and label to the disk

!<cmd> - execute <cmd>, then return
quit
partition> print
Current partition table (default):
Total disk cylinders available: 7678 + 2 (reserved cylinders)
Part Tag Flag Cylinders Size Blocks

0 root wm 0 - 15 128.00MB (16/0/0) 262144
1 swap wu 16 - 31 128.00MB (16/0/0) 262144
2 backup wu 0 - 7677 59.98GB (7678/0/0) 125796352
3 unassigned wm 0 0 (0/0/0) 0
6 usr wm 32 - 7677 59.73GB (7646/0/0) 125272064
NOTE
Generally, if Part of a partition is numbered 2, the partition indicates the entire disk that mapped to the
application server.
Step 8 Run l and enter y to label the LUN that has been expanded.
partition> l
Ready to label disk, continue? y
Step 9 Run mount /dev/dsk/c10t5d1s6 /mnt/ to mount the disk.
Step 10 Run growfs -M /mnt /dev/rdsk/c10t5d1s6 to expand the file system of the LUN.
root@solaris:~# growfs -M /mnt /dev/rdsk/c10t5d1s6
/dev/rdsk/c10t5d1s6: 125272064 sectors in 20390 cylinders of 48 tracks, 128
sectors
61168.0MB in 1275 cyl groups (16 c/g, 48.00MB/g, 5824 i/g)
super-block backups (for fsck -F ufs -o b=#) at:
32, 98464, 196896, 295328, 393760, 492192, 590624, 689056, 787488, 885920,
Initializing cylinder groups:
.........................
super-block backups for last 10 cylinder groups at:
124360864, 124459296, 124557728, 124656160, 124754592, 124853024, 124951456,
125049888, 125148320, 125246752
Step 11 Run df -k to view the file system capacity.

root@solaris:~# df -k
Filesystem 1024-blocks Used Available Capacity Mounted on
rpool/ROOT/solaris 103219200 2269688 79378520 3% /
/devices 0 0 0 0% /devices
/dev 0 0 0 0% /dev
ctfs 0 0 0 0% /system/
contract
proc 0 0 0 0% /proc
mnttab 0 0 0 0% /etc/mnttab
swap 30640088 2272 30637816 1% /system/
volatile
objfs 0 0 0 0% /system/object
sharefs 0 0 0 0% /etc/dfs/
sharetab
fd 0 0 0 0% /dev/fd
rpool/ROOT/solaris/var
103219200 200868 79378520 1% /var
swap 30637816 0 30637816 0% /tmp
rpool/VARSHARE 103219200 48 79378520 1% /var/share
rpool/export 103219200 32 79378520 1% /export
rpool/export/home 103219200 31 79378520 1% /export/home
rpool 103219200 73 79378520 1% /rpool
/dev/dsk/c2t6d0s2 694700 694700 0 100% /media/

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Oracle_Solaris-11_1-Text-SPARC
/dev/dsk/c10t5d1s6 61687396 61185 61120192 1% /mnt
----End
Expanding a LUN on an Application Server in AIX

task uses an application server running AIX 6.1 as an example to describe how to expand a
LUN on an application server. For application servers running other versions of AIX
Prerequisites
Context
In the example of the section, the LUN to be expanded is LUN005 and its capacity is 25 GB.
The capacity of the file system created on the LUN is 24 GB. The LUN and file system will
be expanded to 50 GB and 48 GB respectively. The volume group name and logical volume
name of the LUN that you want to expand are vg1 and lv1 respectively. The mount directory
of the file system that uses the LUN is /mnt/lv1.
Procedure
Step 1 Scan for disks on the AIX-based application server.
NOTICE
l If the LUN that you want to expand has been mapped to the application server and has
mapping relationship with the application server, run rmdev -dl diskName to delete disk
information and perform the follow-up operations. In the command, diskName indicates
the disk of the LUN before expansion.
l If the mapping between the LUN and application server is canceled before expansion
and rebulit after expansion, directly perform the following operations.
Run cfgmgr -v to scan for the LUN.

After the LUN is scanned, AIX automatically identifies the LUN that is mapped to the
application server as a drive letter in hdisk format.
Step 2 Run lsdev -Cc disk command to view the information about disks that have been detected.
# lsdev -Cc disk
hdisk0 Available 01-08-00 SAS Disk Drive
hdisk1 Available 01-08-00 SAS Disk Drive
hdisk2 Available 04-00-02 MPIO Other FC SCSI Disk Drive
hdisk3 Available 04-00-02 MPIO Other FC SCSI Disk Drive
hdisk4 Available 03-01-02 Other FC SCSI Disk Drive
hdisk5 Available 04-01-02 HUAWEI XXXX FC Disk Drive

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
In the command output, XXXX indicates a specific product model or brand.

Step 3 Run upadm show lun to check the drive letter of the LUN that you want to expand.
# upadm show lun
Vendor of /dev/hdisk0 is not HUAWEI, XXXX, XXXX or XXXX
----------------------------------------------------------------------------------
-------------
Device Name: Lun Name: Vendor ID: Type: Serial Number: Device
WWN:
----------------------------------------------------------------------------------
-------------
/dev/hdisk5 LUN005 HUAWEI XXXX 1T50214955
60022a1100098e6703da136f0000000a
If there are multiple disks, run the upadm show lun command to check the drive letter of
each disk. At the bottom of the command output, the drive letter of the newly created LUN is
displayed. In this example, the LUN name is LUN005 and its drive letter is hdisk5. In the
command output, XXXX indicates a specific product model or brand.
Step 4 Run umount /mnt/lv1 to unmount the file system.
In the command output, /mnt/lv1 indicates the mount directory of the file system.
Step 5 Run varyoffvg vg1 to deactivate volume group vg1.
In the command output, vg1 indicates the name of the volume group corresponding to the
LUN that you want to expand.
Step 6 Run bootinfo -s hdiskX to check the LUN capacity after expansion. In the command, X
indicates the number of the drive letter. In this example, X is 5.
# bootinfo -s hdisk5
51200
In the preceding command output, if the unit is MB, the capacity is 51,200 MB (50 GB) that
is the same as the expansion result displayed on the storage system.
Step 7 Run varyonvg vg1 to activate volume group vg1.
Step 8 Refresh the capacity of the volume group corresponding to the LUN that you want to expand.
1. Run chvg -g vg1 to refresh the volume group of the LUN that you want to expand.
# chvg -g vg1
0516-1164 chvg: Volume group vg1 changed. With given characteristics vg1
can include up to 64 physical volumes with 2032 physical partitions
each.
2. Run lsvg vg1 to view parameters related to the volume group.

# lsvg vg1
VOLUME GROUP: vg1 VG IDENTIFIER:
00f6e07400004c00000000011660e3d1
VG STATE: active PP SIZE: 32 megabyte(s)
VG PERMISSION: read/write TOTAL PPs: 1599 (51168 megabytes)
MAX LVs: 512 FREE PPs: 62 (1984 megabytes)
LVs: 2 USED PPs: 1537 (49184 megabytes)
OPEN LVs: 0 QUORUM: 2 (Enabled)
TOTAL PVs: 1 VG DESCRIPTORS: 2
STALE PVs: 0 STALE PPs: 0
ACTIVE PVs: 1 AUTO ON: yes
MAX PPs per VG: 130048

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
MAX PPs per PV: 2032 MAX PVs: 64

LTG size (Dynamic): 256 kilobyte(s) AUTO SYNC: no
HOT SPARE: no BB POLICY: relocatable
In the command output, pay attention to the PP SIZE parameter. If you want to create or
modify a logical volume, you need to refer to the parameter to determine the size of the
logical volume. In the example of this section, the value of PP SIZE is 32 MB.
Step 9 Modify the capacity of the logical volume to meet the need for expanding the file system.
1. Run lslv lv1 to view parameters related to the logical volume.
# lslv lv1
LOGICAL VOLUME: lv1 VOLUME GROUP: vg1
LV IDENTIFIER: 00f6e07400004c00000000011660e3d1.1 PERMISSION: read/
write
VG STATE: active/complete LV STATE: closed/syncd
TYPE: jfs2 WRITE VERIFY: off
MAX LPs: 768 PP SIZE: 32 megabyte(s)
COPIES: 1 SCHED POLICY: parallel
LPs: 768 PPs: 768
STALE PPs: 0 BB POLICY: relocatable
INTER-POLICY: minimum RELOCATABLE: yes
INTRA-POLICY: middle UPPER BOUND: 128
MOUNT POINT: /mnt/lv1 LABEL: /mnt/lv1
MIRROR WRITE CONSISTENCY: on/ACTIVE
EACH LP COPY ON A SEPARATE PV ?: yes
Serialize IO ?: NO
lv1 indicates the name of a logical volume on the volume group. Pay attention to the
MAX LPs, LPs, and PP SIZE parameters in the command output. MAX LPs, LPs, and
PP SIZE indicate the maximum number of logical partitions, number of logical
partitions, and size of the physical partition respectively. The value of MAX LPs
multiplied by PP SIZE is the size of the logical volume, and the value of LPs multiplied
by PP SIZE is the capacity of the logical volume's file system. In the example of this
section, the values of MAX LPs and LPs are both 768, and the value of PP SIZE is 32
MB. Therefore, the capacities of the logical volume and the file system are both 24,576
MB (24 GB).
2. Run smit lv.
# smit lv
Logical Volumes
Move cursor to desired item and press Enter.
List All Logical Volumes by Volume Group

Add a Logical Volume
Set Characteristic of a Logical Volume
Show Characteristics of a Logical Volume
Remove a Logical Volume
Copy a Logical Volume
F1=Help F2=Refresh F3=Cancel Esc+8=Image

Esc+9=Shell Esc+0=Exit Enter=Do
3. In the command output, select Set Characteristic of a Logical Volume and press Enter.
Set Characteristic of a Logical Volume
Move cursor to desired item and press Enter.
Change a Logical Volume

Rename a Logical Volume
Increase the Size of a Logical Volume
Add a Copy to a Logical Volume
Remove a Copy from a Logical Volume

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4. In the command output, select Change a Logical Volume and press Enter.
Type or select a value for the entry field.

Press Enter AFTER making all desired changes.
[Entry Fields]
* LOGICAL VOLUME name [] +
5. Press Esc+4 to go to the logical volume name list. Select the logical volume you want to
modify and press Enter.
Type or select values in entry fields.

Press Enter AFTER making all desired changes.
[Entry Fields]
* Logical volume NAME lv1
Logical volume TYPE [jfs2] +
POSITION on physical volume middle +
RANGE of physical volumes minimum +
MAXIMUM NUMBER of PHYSICAL VOLUMES [128]
#
to use for allocation
Allocate each logical partition copy yes +
on a SEPARATE physical volume?
RELOCATE the logical volume during yes +
reorganization?
Logical volume LABEL [/mnt/lv1]
MAXIMUM NUMBER of LOGICAL PARTITIONS [1536]
#
SCHEDULING POLICY for writing/reading parallel
+
logical partition copies
PERMISSIONS read/write +
Enable BAD BLOCK relocation? yes +
Enable WRITE VERIFY? no +
Mirror Write Consistency? active +
Serialize IO? no +
Mirror Pool for First Copy +
Mirror Pool for Second Copy +
Mirror Pool for Third Copy +
6. In the command output, select the MAXIMUM NUMBER of LOGICAL

PARTITIONS parameter (that is, the MAX LPs parameter) and enter the maximum
number of logical partitions for the logical volume.
Because a file system is created on a logical volume, you need to expand the capacity of
the logical volume before the file system can be expanded. The capacity of the logical
volume must not be smaller than that of the file system. Otherwise, the file system will
fail to be expanded. In the example of this section, the capacity of the file system will be
expanded to 48 GB. First, you need to adjust the maximum number of logical partitions
to ensure that the capacity of the logical volume is not smaller than 48 GB. For example,
if the capacity of the file system needs to be expanded to 48 GB (49,152 MB), the
maximum number of logical partitions must be not smaller than 1536 (49,152/32).
7. After modifying the parameter, press Enter.
COMMAND STATUS
Command: OK stdout: no stderr: no
Before command completion, additional instructions may appear below.
8. Press Esc+0 to exit the logical volume configuration interface.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 10 Expand the file system on the lv1 logical volume.

1. Run chfs -a size=48G /mnt/lv1 to expand the file system of the volume group.
# chfs -a size=48G /mnt/lv1
Filesystem size changed to 100663296
As shown in the command output, the capacity of the file system has been expanded to
48 GB.
2. Run mount /mnt/lv1 to mount the file system again.
----End
Expanding a LUN on an Application Server in HP-UX

task uses an application server running HP-UX 11i v3 as an example to describe how to
expand a LUN on an application server. For application servers running other versions of HP-
UX operating systems, adjust the operations based on actual conditions.
Prerequisites
Context
In the example of the section, the capacity of the LUN will be expanded from 25 GB to 50
GB and its mount directory is /test/.
Procedure
Step 1 Scan for LUNs on the HP-UX-based application server.
1. Run ioscan command to scan for hardware.
2. Run ioscan -funNC disk to view information about detected LUNs.
bash-3.2# ioscan -funNC disk
Class I H/W Path Driver S/W State H/W Type Description
===================================================================
disk 2 64000/0xfa00/0x0 esdisk CLAIMED DEVICE HP
DG146ABAB4
/dev/disk/disk2 /dev/disk/disk2_p1 /dev/rdisk/
disk2 /dev/rdisk/disk2_p1
disk 3 64000/0xfa00/0x1 esdisk CLAIMED DEVICE HP
DG146ABAB4
/dev/disk/disk3 /dev/disk/disk3_p1 /dev/disk/
disk3_p2 /dev/disk/disk3_p3 /dev/rdisk/disk3 /dev/rdisk/disk3_p1 /dev/
rdisk/disk3_p2 /dev/rdisk/disk3_p3
disk 5 64000/0xfa00/0x2 esdisk CLAIMED DEVICE TEAC DV-28E-V
/dev/disk/disk5 /dev/rdisk/disk5
disk 399 64000/0xfa00/0x90 esdisk CLAIMED DEVICE HUAWEI S2600T
/dev/disk/disk399 /dev/rdisk/disk399
In this example, /dev/disk/disk399 indicates the device file of the LUN mapped to the
application server.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
If the operating system is HP-UX 11i v2 or HP-UX 11i v1, run the ioscan -funC disk command to view
LUNs detected by the application server.
Step 2 Run umount /test/ to unmount the file system of the LUN.
/test/ indicates the mount directory of the file system.
Step 3 Run extendfs -F vxfs /dev/disk/disk399 to expand the file system of the LUN.
vxfs indicates the file system type.
Step 4 Run mount /dev/disk/disk399 /test/ to mount the file system of the LUN.
Step 5 Run bdf to view the file system capacity after it is expanded.
bash-3.2# bdf
Filesystem kbytes used avail %used Mounted on
/dev/vg00/lvol3 1048576 920416 127376 88% /
/dev/vg00/lvol1 1835008 368824 1454800 20% /stand
/dev/vg00/lvol8 8912896 2309816 6552824 26% /var
/dev/vg00/lvol7 6553600 3012368 3513640 46% /usr
/dev/vg00/lvol4 524288 23504 497008 5% /tmp
/dev/vg00/lvol6 7864320 4358216 3479048 56% /opt
/dev/vg00/lvol5 131072 64088 66464 49% /home
/dev/disk/disk399 52428800 79504 49077472 0% /test
The preceding command output displays that the capacity of the file system becomes 50 GB.
----End
Expanding a LUN on an Application Server in VMware ESX

task uses an application server running VMware ESXi 5.1.0 as an example to describe how to
expand a LUN on an application server. For application servers running other versions of
VMware ESX operating systems, adjust the operations based on actual conditions.
Prerequisites
Context
In this example of the section, the capacity of the LUN to be expanded is 25 GB and it will be
expanded to 50 GB. The ID of the LUN to be expanded is 14.
Procedure
Step 1 In vSphere Client, click the Configuration tab.
Step 2 On the left navigation bar, click Storage.
Step 3 On the Storage page, click the Devices tab.
On the Devices page, view the device mapped from the LUN to be expanded on the
application server, as shown in Figure 8-5.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 8-5 Device mapped from the LUN to be expanded on the application server
Step 4 On the Devices page, click Rescan All.

The Rescan dialog box is displayed, as shown in Figure 8-6.
Figure 8-6 Rescan dialog box
Step 5 Click OK.

It takes 2 to 4 minutes to scan for new storage devices and VMFS volumes. You can check the
task status in the Recent Tasks area at the lower part of the main window.
l If the task status is In Progress as shown in Figure 8-7, the scanning is ongoing.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 8-7 Scanning ongoing
l If the task status is Completed as shown in Figure 8-8, the scanning is completed.
Figure 8-8 Scanning completed
Step 6 On the Storage page, click Datastores tab.

On the Datastores page, view the datastore mapped from the LUN to be expanded on the
application server, as shown in Figure 8-9.
Figure 8-9 Device mapped from the LUN to be expanded on the application server
Step 7 Right-click the datastore corresponding to the LUN to be expanded, and choose Properties
from the shortcut menu.
The DataStore_Extend Properties dialog box is displayed, as shown in Figure 8-10.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 8-10 DataStore_Extend Properties dialog box
Step 8 In the Volume Properties area, click Increase.

The Increase Datastore Capacity dialog box is displayed, as shown in Figure 8-11.
Figure 8-11 Increase Datastore Capacity dialog box

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 9 Select the datastore corresponding to the LUN to be expanded and click Next.
Step 10 View the current disk distribution and click Next.
Step 11 Set the size of the expansion data area. The maximum storage space is recommended, as
shown in Figure 8-12. Click Next.
Figure 8-12 Setting the size of the expansion data area
Step 12 Click Finish.

The DataStore_Extend Properties dialog box is displayed.
Step 13 Click Close.
----End
Result
l On the Datastores tab of Storage page, view the expanded datastore, as shown in
Figure 8-13.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 8-13 Datastore mapped from the expanded LUN on the application server
l On the Devices tab of Storage page, view the expanded device, as shown in Figure
8-14.
Figure 8-14 Device mapped from the expanded LUN on the application server
8.2 Adjusting Resource Allocation

If the storage system's current resources cannot meet a customer's service requirements, you
can adjust storage resources to ensure the normal and stable running of the services. Adjusting
resource allocation involves modifying LUN groups, host groups, port groups, and mapping
groups.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
8.2.1 Modifying a Mapping View

By modifying a mapping view, you can deal with the effect of service changes on the
mapping between a host group and a LUN group.
Procedure
Step 1 Go to the Modify Mapping View dialog box.

2. On the host management page, click Mapping View.
3. Select the mapping view you want to modify and click Modify Mapping View.
The Modify Mapping View dialog box is displayed.
Step 2 Optional: Modify the LUN group mapping in the mapping view.
1. Click .
The Select LUN Group dialog box is displayed.
NOTE
If your service requires a new LUN group, click Create to create one.
2. From the LUN group list, select the LUN group you want to add to the mapping view.
NOTE
To facilitate locating the LUN group, select Shows only the LUN groups that do not belong to any
mapping view in the lower left corner of the dialog box.
3. Optional: Select Set Host LUN ID, in Start ID, select an ID.
NOTE
Host LUN ID is an ID allocated by the storage system to a LUN mapped to a host.

Starting from the selected ID, the system will automatically assign a unique host LUN ID to each
LUN in the selected LUN group.
If you do not select Set Host LUN ID and there is no other mapped LUN in the host, the system
will automatically assign a unique host LUN ID (starting from 1) to each LUN in the selected LUN
group by default.
4. Click OK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 3 Optional: Modify the host group mapping in the mapping view.
1. Click .
The Select Host Group dialog box is displayed.
NOTE
If your service requires a new host group, click Create to create one.
2. From the host group list, select the host group you want to add to the mapping view.
3. Click OK.
Step 4 Optional: Modify the port group mapping in the mapping view.
1. Select the port group.
2. Click .
The Select Port Group dialog box is displayed.
NOTE
If your service requires a new port group, click Create to create one.
3. From the port group list, select the port group you want to add to the mapping view.
4. Click OK.
Step 5 Confirm the creation of the mapping view.

1. Click OK.
3. Click OK.
4. Click Close.
----End
8.2.2 Adding an Object

This operation enables you to add a LUN or snapshot for a LUN group to expand the LUN's
storage space.
Procedure
Step 1 Go to the Add Object dialog box.

2. Click LUN.
3. Click the LUN Group tab.
4. Select the LUN group you want to modify and click Add Object.
The Add Object dialog box is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Select the LUN or snapshot you want to add to the LUN group.
NOTE
To facilitate locating the LUN, select Shows only the LUNs that do not belong to any LUN group in
the lower left corner of the dialog box.
Step 3 Click Right Arrow and add a LUN or snapshot to Selected LUNs or Selected Snapshots.
Step 4 Confirm your operation.

1. Click OK.
The Execution Result message box is displayed, indicating that the operation
succeeded.
2. Click Close.
----End
8.2.3 Removing Object

This operation enables you to remove a LUN or snapshot from a LUN group when the LUN
or snapshot is not needed.
Procedure
Step 1 Go to the Remove Object dialog box.

2. Click LUN.
3. Click the LUN Group tab.
4. Select the LUN group you want to modify and click Remove Object.
The Remove Object dialog box is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Select the LUN or snapshot you want to remove from the LUN group.
Step 3 Click Right Arrow and add a LUN or snapshot to Selected LUNs or Selected Snapshots.

1. Click OK.
The Warning message box is displayed.
2. Carefully read the content in the dialog box. Then select I have read and understood
the consequences associated with performing this operation. for confirmation.
3. Click OK.
succeeded.
4. Click Close.
----End
8.2.4 Adding or Removing a Host

This operation enables you to add or remove a host.
Procedure
Step 1 Go to the Host Group page.

2. On the host management page, click Host.
3. Click the Host Group tab.
Step 2 Select the host group pertaining to your operation.
Step 3 Click Add Host or Remove Host to add or remove a host.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Select the host you want to add or remove. Click .

NOTE
l When adding a host, if hosts belong to different clusters, data access conflict may occur and cause
data loss.
l When adding a host, to facilitate locating the host, select Shows only the hosts that do not belong
to any host group in the lower left corner of the dialog box.

1. Click OK.
succeeded.
NOTE
If you click OK when you remove the host, a Warning dialog box is displayed.
2. Click Close.
----End
8.2.5 Adding a Port

This operation enables you to add a port.
Precautions
l Physical ports are bonded to create a bond port that cannot be added to the port group.
l After the physical ports that are bonded are added to the port group, the port mapping
does not take effect.
Procedure
Step 1 Go to the Add Port management page.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. On the host management page, click Host Port.

3. Click the Port Group tab.
4. Select the port group whose port you want to add and click Add Port.
The Add Port message box is displayed.
Step 2 From the Available Ports list, select the ports you want to add.
Step 3 Click Right Arrowto move the ports to the Selected Ports.

1. Click OK.
succeeded.
2. Click Close.
----End
8.2.6 Removing a Port

This operation enables you to remove a port.
Procedure
Step 1 Go to the Remove Port management page.

2. On the host management page, click Host Port.
3. Click the Port Group tab.
4. Select the port group whose port you want to remove and Click Remove Port.
The Remove Port dialog box is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 From the Added Ports list, select the ports you want to remove.
Step 3 Click Right Arrow to move the ports to the To-Be-Removed Ports.

1. Click OK.
2. Read the contents of the Warning dialog box carefully. Then click the check box next to
the statement I have read the previous information and understood subsequences of
the operation to confirm the information.
3. Click OK.
succeeded.
4. Click Close.
----End
8.2.7 Creating SmartErase Task

This operation enables you to sanitize the data on a LUN before discarding the LUN. The
sanitized data cannot be recovered, which ensures data security.
Context
The system provides the following two methods of data sanitation:
l DoD: The system overwrites a LUN in accordance with US Department of Defense
(DoD) Standards to destroy source data.
l Customize: The system overwrites a LUN according to the configured overwrite times.
Precautions
l The LUN to be destroyed must be a thick LUN. A thin LUN cannot be fully destroyed
because of capacity-on-write and space release.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l An abnormal LUN cannot be destroyed.

l A mapped LUN cannot be destroyed.
l A LUN for which value-added services are configured cannot be destroyed.
l A LUN whose migration property has not been set to No relocation cannot be destroyed.
Procedure
Step 1 Go to the Create SmartErase Task dialog box.

2. Click LUN.
3. Select a LUN whose data you want to sanitize, and choose More > Create SmartErase
Task.
The Create SmartErase Task dialog box is displayed.
Step 2 Configure the LUN data sanitation. For details about data sanitation parameters, see Table
8-3.
Table 8-3 Parameters for LUN data sanitation

DoD Overwrite data based on the [Example]

DoD standard to erase DoD
original data.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Custom The system overwrites the [Example]

selected LUN according to
the configured overwrite
times.
NOTE
If this parameter is selected,
Overwrite Times is valid.
Overwrite Times Customize data overwrite [Value range]

times. More overwrite times 3 to 99
indicate more thorough
erase. [Example]
7
Step 3 Confirm the LUN data sanitation.

NOTE
If you want to stop the ongoing data sanitation, right-click the LUN and choose Delete SmartErase
Task.
1. Click OK.
2. Carefully read the content in the dialog box. Then select I have read and understood
the consequences associated with performing this operation. for confirmation.
3. Click OK.
4. Click OK.
----End
8.2.8 Deleting SmartErase Task

Delete the SmartErase task after the SmartErase is completed.
Context
Deleting this LUN is recommended since keeping this LUN for value-added services may
cause service abnormalties after you have deleted the SmartErase task. Before deleting this
LUN, check that the data on it is of no use or has been backed up.
Procedure
Step 1 Go to the LUN management page.

2. Click LUN.
The LUN management page is displayed.
Step 2 Delete the SmartErase task.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
1. Select the LUN whose SmartErase task you want to delete and choose More > Delete
SmartErase Task.
2. Carefully read the content of the dialog box. Then click the check box next to the
statement I have read and understood the consequences associated with performing
this operation. to confirm the information.
3. Click OK.
4. Click Close.
----End
8.2.9 Viewing the Mappings Between Host Disks and LUNs

This section describes how to view the mappings between host disks and LUNs for fast
locating disks and LUNs during path change or capacity expansion.
Prerequisites
l If a Fibre Channel network is used, ensure that the world wide name (WWN) of a Fibre
Channel initiator has been obtained.
l If an Internet Small Computer Systems Interface (iSCSI) network is used, ensure that the
iSCSI qualified name (IQN) of an iSCSI initiator has been obtained.
l The UltraPath software has been installed on the host.
Procedure
Step 1 On the storage system, obtain the WWN of the LUN mapped to the host.
1. Log in to the command-line interface (CLI) of the storage system as a super
administrator.
2. Run show initiator initiator_type=? [ wwn=? | iscsi_iqn_name=? ] to show the host
corresponding to the WWN or iSCSI IQN.
initiator_type=? Type of an initiator Possible values are as

follows:
iSCSI: iSCSI initiator
FC: Fibre Channel
initiator
wwn=? WWN of a Fibre Channel To obtain the value, run

initiator. This parameter is the show initiator
available only when command without
initiator_type=? is FC. parameters.
iscsi_iqn_name=? IQN of an iSCSI initiator. To obtain the value, run

This parameter is available the show initiator
only when command without
initiator_type=? is iSCSI. parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
admin:/>show initiator initiator_type=FC wwn=21000024ff53b640
WWN : 21000024ff53b640
Running Status : Online
Free : Yes
Alias : suse2_01
Host ID : 2
Multipath Type : Default
The value of Host ID is the ID of a host corresponding to the WWN.

3. Run show host lun host_id=? to view all LUNs mapped to the host.
host_id=? represents the ID of a host.
admin:/>show host lun host_id=2
LUN ID LUN Name

------ ------------
34 lun_0000
35 lun_0001
36 lun_0002
The value of LUN ID is the ID of a LUN mapped to the host in the storage system.
4. Run the show lun general lun_id=? command to view the WWN of the LUN mapped to
the host.
Step 2 On the storage system, view the WWNs of vLUNs.
1. Log in to the CLI of UltraPath on the host.
2. On the host where UltraPath is installed, run show vlun to view the WWN of a disk on
the host.
NOTE
If UltraPath is installed on a Windows/Linux/AIX operating system, see the UltraPath User

Guide for that specific operating system to know how to use the show vlun command.
If UltraPath is installed on an HP-UX operating system, run scsimgr -p get_attr all_lun -a
device_file -a wwid to view the WWN of a disk on the host.
Step 3 Check whether the WWN of the LUN mapped to the host and that of the host disk are the
same. If they are, the LUN is just the one corresponding to the host disk.
NOTE
For details about related commands, see OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System V300R001 Command Reference.
----End
8.2.10 Viewing the Disk Path Information on a Host

This section describes how to view the disk path information on a host and know the initiator,
storage device, and path status corresponding to the disk.
Prerequisites
The UltraPath software has been installed on the host.
Procedure
Step 1 Log in to the CLI of UltraPath on the host.
Step 2 Run show path to show a disk on the host.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
l If UltraPath is installed on a Windows/Linux/AIX operating system, see the UltraPath User Guide
for that specific operating system to know how to use the show vlun command.
l If the operating system is HP-UX where the Native Multi-Pathing (NMP) software is installed, run
scsimgr lun_map to show a disk on the host.
The following is the disk path information on an AIX host queried by the UltraPath software:
UltraPath CLI #11 >show path
----------------------------------------------------------------------------------
-----------------------------------------------------
Vlun ID Path ID PhyPath ID Initiator Port Array Name Controller
Target Port Path State Port Type Port ID
2 0 0 10000090fa1c6b8c Huawei.Storage 2A
20080022a10e6421 Enabled FC ENG2.A1.P0
2 1 1 10000090fa1c6b8c Huawei.Storage 3B
2210200bc71fa9bd Enabled FC ENG3.B2.P0
2 2 2 10000090fa1c6b8d Huawei.Storage 0A
2400200bc71fa9be Enabled FC ENG0.A4.P0
2 3 3 10000090fa1c6b8d Huawei.Storage 1B
2210333533383336 Enabled FC ENG1.B2.P0
2210333533383336 Enabled FC ENG1.B2.P0
2210333533383336 Enabled FC ENG1.B2.P0
----------------------------------------------------------------------------------
-----------------------------------------------------
where Initiator Port indicates the WWN of the host HBA, Array Name indicates the storage
device where the LUN mapped to the host resides, and Target Port indicates the WWN of the
Fibre Channel port on the storage device.
----End
8.3 Changing Links

If the storage system's current network links cannot meet a customer's service requirements,
you can adjust storage resources to ensure the normal and stable running of the services.
8.3.1 Managing Routes

When iSCSI is used to constructing network and cross-segment transmission existed, you can
take advantage of this topic to guide you through the process of configuring routes to enable
data transmission across network segments.
Prerequisites
The IP address of an Ethernet port has been configured.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
l In redundant links, you must configure IP addresses and route for multiple Ethernet ports.
l When a domain controller exists, ensure that the logical IP addresses, domain controller, and DNS can
ping each other. If they cannot ping each other, add the logical IP addresses to the network segment route
between the domain controller and the DNS.
l When configuring NFS share access, if the NFS clients and logical IP addresses cannot ping each other,
add the logical IP addresses to the network segment route between the NFS clients.
Procedure
Step 1 Go to the Route Management dialog box.

2. In the Basic Information area of the function pane, click the device icon.
3. In the right function pane, click the cabinet whose Ethernet ports you want to view.
4. Click the controller enclosure where the Ethernet ports reside.
The system displays the front view of the controller enclosure.
5. Click to switch to the rear view.

6. Click the Ethernet port to which you want to add a route.
7. Click Route Management.
The Route Management dialog box is displayed.
Step 2 Set route information for the Ethernet port.
1. In IP Address, select the IP address of the Ethernet port.
2. Click Add.
The Add Route dialog box is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTICE
The default IP addresses of the internal heartbeat on the system are 127.127.127.1X.
Therefore, the IP address of the router cannot fall within the 127.127.127.XXX segment.
Besides, the IP address of the gateway cannot be 127.127.127.1X. Otherwise, routing
will fail. (Internal heartbeat links are established between controllers for these controllers
to detect each other's working status. You do not need to separately connect cables. In
addition, internal heartbeat IP addresses have been assigned before delivery, and you
cannot change these IP addresses).
3. In Type, select the type of the route to be added.
There are three route options:
Default route
Data is forwarded through this route by default if no preferred route is available.
The target address field and the target mask field (IPv4) or prefix (IPv6) of the
default route are automatically set to 0. To use this option, you only need to add a
gateway.
Host route
The host route is the route to an individual host. The target mask (IPv4) or prefix
(IPv6) of the host route are automatically set respectively to 255.255.255.255 or
128. To use this option, you only need to add the target address and a gateway.
Network segment route
The network segment route is the route to a network segment. You need to add the
target address, target mask (IPv4) or prefix (IPv6), and gateway.
4. Add Destination address.
If IP address is an IPv4 address, set Destination address to the IPv4 address or
network segment of the application server's service network port or the IPv4
address or network segment of the storage device's Ethernet port.
If IP address is an IPv6 address, set Destination address to the IPv6 address or
network segment of the application server's service network port or the IPv6
address or network segment of the storage device's Ethernet port.
5. Add Destination mask (IPv4) or Prefix (IPv6).
Add Destination mask for an IPv4 address. This parameter specifies the subnet
mask of the IP address for the service network port on the application server or on
the storage device that connects to the Ethernet port.
Add Prefix for an IPv6 address. This parameter specifies the prefix to the IPv6
address of the host's service network port or the prefix to the IPv6 address of the
storage device's Ethernet port.
6. In Gateway, enter the gateway where the local end Ethernet port's IP address resides.
Step 3 Click OK. The route information is added to the route list.
Step 4 Confirm the information in the dialog box and select I have read and understood the
consequences associated with performing this operation.
Step 5 Click OK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
To delete a route, select it and click Remove.
Step 6 Click Close.
----End
8.3.2 Bonding Ethernet Ports

To improve data transmission performance of Ethernet ports, bond them and set bonding
names and available ports.
Prerequisites
l The storage system supports bonding Ethernet ports.
l Given bonding Ethernet ports interrupts ongoing services, you must stop any services
running on the Ethernet ports that you want to bond.
Precautions
l After Ethernet ports are bound, the IP address assigned to each separate Ethernet port is
deleted. You need to assign an IP address to the bound Ethernet port.
l After a bonding is complete, MTU (Byte) of the bonded host ports becomes 1500.
l After bonding, the mode of all switch ports connected to the Ethernet port must be
configured to 802.3AD LACP.
l Bonding Ethernet ports is not available to read-only users.
l Physical ports are bonded to create a bond port that cannot be added to the port group.
l After the physical ports that are bonded are added to the port group, the port mapping
does not take effect.
Procedure
Step 1 Go to the Bond dialog box.

3. In the middle function pane, click the cabinet whose Ethernet ports you want to bond.
4. Click the controller enclosure where the Ethernet ports reside.

6. Click the Ethernet port you want to bond.
7. Click Bond.
The Bond dialog box and the selected port is displayed. The format of the port name is
controller enclosure ID.interface module ID.port ID.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Set the bonding name and available ports for the Ethernet port.
1. In Bond Name, enter a name for the port to be bound.
The name:
Can contain only letters, digits, periods (.), underscores (_), and hyphens (-).
Contains 1 to 31 characters.
2. From the Available Ports list, select the Ethernet ports you want to bond with the
current Ethernet port.
3. Click OK.
Step 3 Confirm the bonding of the Ethernet ports.

information and understood subsequences of the operation..
2. Click OK.
3. Click OK.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
8.3.3 Canceling Ethernet Port Bonding

This topic guides you through the process of unbinding Ethernet ports to use them separately.
Prerequisites
Given unbinding Ethernet ports interrupts ongoing services, you must stop any services
running on the Ethernet ports that you want to unbind.
Precautions
After an unbinding is complete, the IP addresses of the unbound Ethernet ports are cleared.
Procedure
Step 1 Go to the page for canceling Ethernet port bonding.

3. In the middle function pane, click the cabinet whose Ethernet port bonding you want to
cancel.
4. Click the controller enclosure where the bonded Ethernet ports reside.

6. Click the Ethernet port you want to cancel bonding.
Step 2 Cancel the port bonding.
1. Select the Ethernet port whose bonding you want to cancel and click Cancel Bonding.
3. Click OK.
4. Click OK.
----End
8.3.4 Modifying an Ethernet Port

When the networking mode between the storage device and application servers varies, modify
the settings of Ethernet ports to retain normal communication between them.
Precautions
l Given changing the IP address of an Ethernet port interrupts services, check that the
storage device is connected in a redundant way; otherwise, stop services running on the
storage device first. Do not change the IP address of the Ethernet port unless you are
asked to.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l The IP addresses of the ethernet port and internal heartbeat must be on different network
segments. The default IP addresses of the internal heartbeat on the storage system are
127.127.127.1X. (Internal heartbeat links are established between controllers for these
controllers to detect each other's working status. You do not need to separately connect
cables. In addition, internal heartbeat IP addresses have been assigned before delivery,
and you cannot change these IP addresses).
l The IP address of an Ethernet port cannot be in the same network segment as that of a
management network port.
l The IP address of the Ethernet port cannot be in the same network segment as that of a
maintenance network port.
l If the Ethernet port connects to an application server, the IP address of the Ethernet port
must be in the same network segment as that of the service network port on the
application server. If the Ethernet port connects to another storage device, the IP address
of the Ethernet port must be in the same network segment as that of the peer Ethernet
port on the other storage device. Add routes if available IP addresses become insufficient
for a network segment that you want to add an IP address to.
Procedure
Step 1 Go to the Ethernet Port dialog box.

3. In the middle function pane, click the cabinet whose Ethernet port you want to view.
4. Click the controller enclosure where the Ethernet port resides.

6. Click the Ethernet port whose information you want to view.
The Ethernet Port dialog box is displayed.
7. Click Modify.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Modify the Ethernet port.

1. In the IPv4 address or IPv6 address text box, enter an IP address for the Ethernet port.
2. In the Subnet Mask or Prefix area, enter the subnet mask or prefix of the Ethernet port.
3. In MTU (Byte), type a maximum transfer unit (MTU) for the packets transferred
between the Ethernet port and the application server.
The MTU must be an integer ranging from 1500 to 9000.
Step 3 Confirm the Ethernet port modification.
1. Click Apply.
3. Click OK.
4. Click OK.
----End
8.3.5 Modifying a Fibre Channel Port

When the networking mode between the storage device and application servers varies, modify
the settings of Fibre Channel ports to retain normal communication between them.
Context
Note the following when you modify Fibre Channel ports:

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l If the storage device connects to an application server through a Fibre Channel port,
ensure that the rate of the Fibre Channel port on the storage device is the same as that of
the peer host bus adapter (HBA) port on the application server.
l When two storage devices connect to each other through Fibre Channel ports, ensure that
the rates of the Fibre Channel ports on both storage device are the same.
l Given modifying the Fibre Channel ports interrupts the communication between the
storage device and application servers, do not modify any Fibre Channel port settings
when ongoing services are present on the storage device.
Procedure
Step 1 Go to the FC port dialog box.

3. In the middle function pane, click the cabinet whose Fibre Channel port you want to
view.
4. Click the controller enclosure where the Fibre Channel port resides.

6. Click the Fibre Channel port whose information you want to view.
The FC port dialog box is displayed.
7. Click Modify.
Step 2 In Configured Rate (Gbit/s), select a data transfer rate for the Fibre Channel port.
NOTICE
l The rate and mode of the Fibre Channel port on a storage system must be consistent with
those of the Fibre Channel HBA on the peer application server. If the rates and modes are
inconsistent, the communication fails.
l The rate and mode of the Fibre Channel ports on two storage systems that are connected to
each other must be consistent. If the rates and modes are inconsistent, the communication
fails.
Available rates of a Fibre Channel port are 2 Gbit/s, 4 Gbit/s, 8Gbit/s, 16Gbit/s and
Autonegotiation. Select a fixed value after learning the rate of the peer Fibre Channel port.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
l If the configured maximum rate of the port is 4 Gbit/s, you can set the value to be 2 Gbit/s or 4
Gbit/s.
l If the configured maximum rate of the port is 8 Gbit/s, you can set the value to be 2 Gbit/s, 4 Gbit/s,
or 8 Gbit/s.
l If the configured maximum rate of the port is 16 Gbit/s, you can set the value to be 4 Gbit/s, 8
Gbit/s, or 16 Gbit/s.
l If the configured rate of the port is Autonegotiation, the rate of the peer FC port can automatically
adjust. If adaptive rate mismatch occurs , please change the port rate to another value.
Step 3 Confirm the Fibre Channel port modification.

1. Click Apply.
3. Click OK.
4. Click OK.
----End
8.3.6 Naming an iSCSI Device and an iSCSI Initiator

Both iSCSI device name and iSCSI initiator name contain two parts: default name and user-
defined name. Only the user-defined name can be modified. The iSCSI target name is
dynamically generated based on the iSCSI device name and the identifier of a specific port.
(For details about how the iSCSI target name is generated, contact your maintenance
personnel.)
Procedure
Step 1 Go to the iSCSI Settings page.

2. In the Viewing and Settings area, choose iSCSI Settings.
The iSCSI Settings page is displayed.
Step 2 Change the iSCSI device name and initiator name.

1. Click the Name Settings node.
2. In iSCSI Device Name, enter the user-defined part of the iSCSI device name.
The name contains 0 to 31 characters.
3. In iSCSI Initiator Name, enter the user-defined part of the iSCSI initiator name.
The name contains 0 to 31 characters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4. Click Save.
5. Click Close.
----End
8.3.7 Setting iSNS

After configuring the Internet Storage Name Service (iSNS), you do not have to manually
configure the list of initiators or targets for each storage device but can discover and manage
them using the iSNS server. The iSNS server operates as a unified configuration node to
configure and manage the entire storage network including iSCSI and Fibre Channel devices.
Context
The traditional device-by-device mode used to configure and manage devices on a storage
network requires each storage device be configured with an initiator and a target separately.
This costs high management and maintenance expenses. After configuring the Internet
Storage Name Service (iSNS), you do not need to manually configure each initiator or the
initiator list for each storage device. Instead, the iSNS server takes over the initiator detection
and management work, greatly reducing the management and maintenance costs.
Procedure
Step 1 Go to the iSCSI configuration page.

2. In the function pane on the left, click iSCSI Settings in the Viewing and Settings area.
The iSCSI configuration page is displayed.
Step 2 Configure the iSNS Service.
1. In the navigation tree, choose iSNS Settings.
2. Type the IP address of the iSNS server in iSNS Server IP Address.

The IP address of an iSNS server can be an IPv4 or IPv6 address.
3. Click Save.
4. Click Close and you have finished configuring the iSNS service.
----End
8.3.8 Changing IP Addresses of Management Network Ports

If the IP address of the management network port on a controller module is on a different
network segment with that of the maintenance terminal connecting to the storage device, you
can change the IP address through a serial port. To use the DeviceManager to manage the

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
storage device, the IP addresses of management network ports on controller modules must be
on the same network segment as that of the maintenance terminal.
Prerequisites
The maintenance terminal has been connected to the serial port on the storage device through
a serial cable.
Precautions
When changing the IP address of the management network port, note the following:
l The maintenance terminal and storage device must be interconnected through a serial
port.
enclosure (5600 V3/5800 V3/6800 V3), the default IP addresses of the management
network ports on management modules 0 and 1 are respectively 192.168.128.101 and
192.168.128.102, and the default subnet mask is 255.255.0.0.
l The IP addresses of both management network ports and those of internal heartbeat IP
addresses or iSCSI host ports must be on different network segments. Otherwise, route
conflicts may occur. The default internal heartbeat IP addresses are 127.127.127.10 and
127.127.127.11 for a dual-controller storage system and are 127.127.127.10,
127.127.127.11, 127.127.127.12, and 127.127.127.13 for a four-controller storage
system, and the subnet mask is 255.255.255.0. Therefore, for a dual-controller system,
you cannot use IP addresses that belong to the 127.127.127.XXX network segment. For
a four-controller storage system, you cannot set IP addresses that belong to the
127.127.127.XXX, 172.16.126.XXX, 172.16.127.XXX, and 172.16.128.XXX network
segments.
NOTE
l Heartbeats are the packets, requiring no acknowledgement, transmitted between two devices.
The device can judge the validity status of the peer device. Heartbeat supports node
communication, fault diagnosis, and event triggering.
l Internal heartbeat links are established between controllers for these controllers to detect each
other's working status. You do not need to separately connect cables. In addition, internal
heartbeat IP addresses have been assigned before delivery, and you cannot change these IP
addresses.
l The IP addresses of both management network ports and those of maintenance network
ports must be on different network segments. Otherwise, route conflicts may occur. The
default IP addresses of maintenance network ports are 172.31.128.101 and
172.31.128.102, and the subnet mask is 255.255.0.0. You cannot use IP addresses that
belong to the 172.31.XXX.XXX. You are advised to only connect the management
network port to the network.
l Make sure that the IP addresses of the management network ports on both controllers are
in the same network segment.
Context
After connecting the controller enclosure to the maintenance terminal by using a network
cable, you can log in to the storage system by using any type of remote login software (This
document uses the PuTTY software as an example).

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
l This document uses the PuTTY software as an example. You can download the PuTTY software
from the http://www.chiark.greenend.org.uk.
l You are advised to use the latest version of PuTTY, otherwise you may fail to log in to the storage
system.
Procedure
Step 1 Run PuTTY.
The PuTTY Configuration dialog box is displayed, as show in Figure 8-15.
Figure 8-15 PuTTY Configuration dialog box
Step 2 Set Connection type to Serial. In the Serial line text box, enter the name of the serial port
that connects the maintenance terminal to the storage system, for example, COM1. In Speed,
enter 115200.
You can query the serial port that connects the maintenance terminal to the storage system as
follows (Windows 7 is used as an example):
1. Right-click the icon of Computer on the desktop of the maintenance terminal and
choose Manage from the shortcut menu.
2. In the navigation tree of the Computer Manager dialog box, choose System Tools >
Device Manager.
3. Click Ports. The serial port that connects the maintenance terminal to the storage
system, for example, COM1.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
There may be multiple serial port names, such as COM1, COM2, and COM3, on the
maintenance terminal. Try these ports until you can successfully log in to the storage
system.
Step 3 Log in to the serial port.
1. Click Open.
If the connectivity between the maintenance terminal and controller is normal,
information similar to Figure 8-16 is displayed.
Figure 8-16 Successful connection between the controller and the maintenance terminal
2. Enter the user name and password.

NOTE
The default user name for the storage system is admin, and the password is Admin@storage.
You must change the default login password immediately after you have logged in to the
storage system for the first time and periodically change your login password in the future.
This reduces the password leakage risks. For details about how to change a password, see
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System
V300R001 Maintenance Guide.
For security reasons, entering a password displays no local echo.
If the login is successful, the following message is displayed.

Authorized users only. All activity may be monitored and reported.
WARNING: You have accessed the system.

You are required to have a personal authorisation from the system
administrator before you use this computer. Unauthorised access to or misuse
of this system is prohibited.
System Name : xxxx

Health Status : Normal
Running Status : Normal
Total Capacity : 20.241TB
SN : xxxx
Location :

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Product Model : xxxx

Product Version : xxxx
Time : 2014-11-24/16:13:47 UTC+08:00
NOTE
When you log in to different devices, the login page displays different values. Obtain the correct
value based on actual conditions.
Step 4 Change the IP address of a management network port.
NOTICE
Ensure that the IP addresses of the two management network ports have been modified.
Run the change system management_ip command to change the IP address of the port, as
shown in Table 8-4.
Table 8-4 change system management_ip format and parameters

Command Format Description
change system l eth_port_id

management_ip eth_port_id Port ID. To obtain the value, run show system
ip_type mask [gateway] management_ip.
l ip_type
IP address type. Possible values are ipv4_address
and ipv6_address.
l mask
Subnet mask of the management network port.
l gateway
Gateway of the management network port.
For example:
Set the IPv4 address, subnet mask, and gateway of management module 0 to 172.16.190.2,
255.255.0.0, and 172.16.0.1.
admin:/>change system management_ip eth_port_id=CTE0.SMM0.MGMT0
ip_type=ipv4_address ipv4_address=172.16.190.2 mask=255.255.0.0
gateway_ipv4=172.16.0.1
WARNING: You are going to modify the network address of network port. If you
enter an unavailable network address, the O&M interface of the storage system is
inaccessible.
Suggestion: Before you perform this operation, ensure that you have entered an
available network address.
Have you read warning message carefully?(y/n)y

Command executed successfully.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
l For a 6 U controller enclosure, only ports 0 (CTE0.SMM0.MGMT0 and CTE0.SMM1.MGMT0)

on the two management modules are managements ports (there are also two management network
ports available on a 4-controller enclosure). Therefore, you only need to configure IP addresses for
the two management network ports.
l After changing the IP address of the management network port, you can run the show system
management_ip command to verify the IP address information about the controller.
l Changing the IP address of a management port may disconnect the storage device. Change the
management network's IP address only when necessary.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 9 Reclaiming Space of a Storage System
9 Reclaiming Space of a Storage System
About This Chapter
If all or some services of a storage system do not need to be running anymore, or some
expanded space is unused, you can reclaim the space used by these services or the unused
space and then use the space for new services, thereby enhancing storage space utilization.
Based on the range of reclaimed space, space reclamation can be classified into full
reclamation and partial reclamation. The major procedure of space reclamation is shown in
Figure 9-1 and Figure 9-2.
NOTICE
Before a space reclamation, ensure that the space to be reclaimed does not need to be used
anymore and data has been backed up, to avoid the data loss during space reclamation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 9-1 Major procedure of full space reclamation
Start
Back up disk information.
Check the running status of the host and

storage device.
Prepare for reclamation.
On the storage system, export
configuration data of the storage system.
Check the status of the connection

between the HBA and the storage device.
Reclaim WWNs, mapping views, LUN

groups, port groups, and host groups.
Rescan for disks on the host.
Uninstall UltraPath. Applicable to Windows,

Implement the reclamation. Linux and AIX hosts.
Restart the host. Applicable to Windows,

Linux and AIX hosts.
On the switch, delete ZONE-related

configurations.
Install UltraPath. Applicable to Windows,

Applicable to Windows,
Restart the host.
Roll back reclaimed WWNs, mapping

Perform an emergency views, LUN groups, port groups, and host
rollback. groups.
On the host, collect and verify information.
Mandatory Optional Mandatory Optional

End
parent items parent items subitems subitems

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 9-2 Major procedure of partial space reclamation
Start
Back up disk information.
Check the running status

Prepare for reclamation. of the host.
Check the running status

of the storage device.
On the storage system,

export configuration data
of the storage system.
Implement the reclamation. Reclaim LUNs in the LUN
group.
On the host, recognize

disks.
Roll back LUNs in the

reclaimed LUN group.
Check aggregated disks

Perform an emergency
generated by the multipath
rollback.
software.
On the host, collect and

verify information.
Mandatory Optional Mandatory

End
parent items parent items subitems
9.1 Reclaiming Space of a Storage System (in Windows)

This section describes if all or some services of a storage system do not need to be running
anymore, or some expanded space is unused in a Windows operating system, how to reclaim
space and then use it for new services, thereby enhancing storage space utilization.
9.2 Reclaiming Space of a Storage System (in Linux)
anymore, or some expanded space is unused in a Linux operating system, how to reclaim
9.3 Reclaiming Space of a Storage System (AIX)
anymore, or some expanded space is unused in an AIX operating system, how to reclaim
9.4 Reclaiming Space of a Storage System (in HP-UX)
Part or all of services in an HP-UX operating system may not need to be running anymore, or
some expanded space may be unused. In these cases, reclaim space and then use it for new
services, thereby enhancing storage space utilization.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
9.5 Emergency Rollback of Space Reclamation

This section describes how to perform an emergency rollback when you encounter an
abnormality or fault during space reclamation.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
9.1 Reclaiming Space of a Storage System (in Windows)

anymore, or some expanded space is unused in a Windows operating system, how to reclaim
9.1.1 Preparing for Space Reclamation (in Windows)

Before reclaiming space, you must finish preparatory work such as backing up disk
information and checking the host and storage device's running status to ensure that the space
reclamation can be successfully implemented.
Procedure
Step 1 Confirm the range of to-be-reclaimed storage space and back up disk information.
1. Confirm whether it is full reclamation or partial reclamation.
2. Back up disk Information.
a. Log in to the Windows Server 2008 application server as an administrator.
b. Press Windows+R (if the operation is performed remotely, perform it in full screen
mode) to open the Run dialog box.
c. Type diskmgmt.msc and press Enter.
d. In the Disk Management page that is displayed, view the host disk information.
3. Make sure that the to-be-reclaimed disk will not be used anymore.
Step 2 Check the host running status.

1. Check whether any error exists on the host.
a. Press Windows+R (if the operation is performed remotely, perform it in full screen
b. Run eventvwr.msc and devmgmt.msc and press Enter.
c. In the Event Viewer and Device Manager windows, Check whether any error
exists on the host. If there are, remove the errors and proceed to the next step.
2. Check the disk path status.
a. Run upadm show vlun to query the status of all vLUNs. Confirm that the status of
all vLUNs is Normal.
b. Run upadm show path and make sure that the system path status is Normal. If a
path whose status is Degrade exists, Run upadm set phypathnormal. Specify the
path whose status is Degrade using the path_id parameter.
Step 3 Check the storage system status. If there are alarms, clear them and then proceed to the next
step.
Step 4 On the storage system, export the storage system configuration data.
1. Log in to the command-line interface (CLI) of the storage system using PuTTY.
NOTE
The default user name and password are admin and Admin@storage respectively.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Run export running_data to export and save the current configuration file.
Step 5 Check the status of the connection between the host HBA and the storage device.
1. As planned, check whether the two devices (the HBA and the storage device) are
connected and whether the zoning on the switch is correct by using the WWN of the host
HBA and the front-end port of the storage device.
2. Run show port general to check whether the planned front-end network is connected.
Specify the front-end port using the port_id parameter.
If the planned front-end network is connected, its Type is Host Port and its Running
status is Link up.
3. Run show initiator initiator_type=FC isfree=yes to check whether the storage device
can query the initiator on the host and filter out initiators that are not assigned to the host.
In the command output, the planned HBA should exist and its running status should be
Online.
admin:/>show initiator initiator_type=FC isfree=yes
WWN Running Status Free Alias Host
ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
----End
9.1.2 Reclaiming Space (in Windows)

This section describes how to reclaim storage space used by a Windows host in full
reclamation or partial reclamation mode.
Full Reclamation
Step 1 Reclaim the World Wide Name (WWN).
1. Run show mapping_view general to query the ID of a host group in a mapping view to
be reclaimed. Specify which mapping view to reclaim using the mapping_view_id
parameter.
2. Obtain the information about hosts and initiators in the to-be-reclaimed host group.
a. Run show host_group host to show the host that has been added to the to-be-
reclaimed host group. Specify the ID of the to-be-reclaimed host group using the
mapping_view_id parameter.
b. Run show initiator to view the WWN about the host HBA that has been added to
the to-be-reclaimed host group. Specify the ID of the host in the to-be-reclaimed
host group using the host_id parameter.
3. Run remove host initiator initiator_type=FC to remove the WWN. Specify which WWN
to reclaim using the wwn parameter.
4. Run show initiator isfree=yes initiator_type=FC to check whether the WWN is
successfully deleted.
If the deleted WWN exists in the command output, the deletion is successful.
admin:/>show
initiator isfree=yes initiator_type=FC WWN Running
Status Free Alias Host ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------ 100000000000* Online
Yes -- -- Default

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
5. In DeviceManager, view the port information about the host.

Step 2 Run upadm show path to check the path status of the system. The reclaimed path should not
exist in the command output.
NOTE
Wait at least 15 minutes and confirm that no errors exist on disks of other hosts. Then proceed to the next
step.
Step 3 Delete the mapping view.

1. Run show mapping_view general to query and record the ID of a LUN group and host
group in a mapping view to be reclaimed. Specify which mapping view to reclaim using
the mapping_view_id parameter.
2. Run remove mapping_view lun_group to delete the LUN group mapped to the
mapping view. Specify which mapping view and LUN group to reclaim using the
mapping_view_id and lun_group_id parameters.
3. Run remove mapping_view port_group to delete the port group in the mapping view.
Specify which mapping view and port group to reclaim using the mapping_view_id and
port_group_id parameters.
4. Run remove mapping_view host_group to delete the host group in the mapping view.
Specify which mapping view and host group to reclaim using the mapping_view_id and
host_group_id parameters.
5. Run delete mapping_view to delete a mapping view. Specify which mapping view to
reclaim using the mapping_view_id parameter.
6. Run show mapping_view general to check whether that mapping view has been
deleted.
The deleted mapping view should not exist in the command output.
7. In DeviceManager, view all mapping views. The deleted mapping view should not exist.
Step 4 Deleting a LUN Group
1. Run remove lun_group lun to remove all LUNs in the LUN group. Specify the to-be-
reclaimed LUN group and the to-be-removed LUN using the lun_group_id and
lun_id_list parameters.
2. Run delete lun_group to delete a LUN group. Specify the to-be-reclaimed LUN group
using the lun_group_id parameter.
Step 5 Deleting a Port Group
1. Run remove port_group port to remove all ports in the port group. Specify the to-be-
reclaimed port group and to-be-removed ports using the port_group_id and port_id_list
parameters.
2. Run delete port_group to delete a port group. Specify the to-be-reclaimed port group
using the port_group_id parameter.
Step 6 Verify that a host group can be deleted.
1. Run remove host_group host to remove all hosts in the host group. Specify the to-be-
reclaimed host group and to-be-removed hosts using the host_group_id and host_id_list
parameters.
2. Run delete host_group to delete a host group. Specify the to-be-reclaimed host group
using the host_group_id parameter.
3. Run remove host initiator initiator_type=FC to remove all initiators of the to-be-
reclaimed host. Specify the to-be-removed initiator using the wwn parameter.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4. Run delete host to delete a to-be-reclaimed host. Specify the to-be-reclaimed host using
the host_id parameter.
Step 7 Scan for disks on the host.
1. Press Windows+R (if the operation is performed remotely, perform it in full screen
2. Type devmgmt.msc and press Enter.
3. In the Device Manager window that is displayed, click View and select Show hidden
devices.
4. Right-click Disk Drives and choose Scan for hardware changes to start scanning.
5. Check whether the number of newly generated UltraPath_Disks is the same as the
number of mapped LUNs. If they are different, check the LUN mapping and path
connection status on the storage device.
6. Check whether the number of newly generated SCSI disks (SCSI Disk Devices on the
Huawei storage device) doubles or quadruples the number of UltraPath_Disks in Step
7.5. If not, check the LUN mapping and path connection status on the storage device.
Step 8 Uninstall UltraPath.
2. Type appwiz.cpl and press Enter.
The Programs and Features page is displayed.
3. Right-click UltraPath and choose Uninstall from the shortcut menu.
4. Follow the wizard until UltraPath is uninstalled.
Step 9 Run shutdown -r -t 0 to restart the host.
Step 10 On the switch, delete ZONE or VLAN configurations.
----End
Partial Reclamation
Step 1 Remove the to-be-reclaimed LUN from the owning LUN group.
1. Run show mapping_view general to obtain the details about the to-be-reclaimed
mapping view. Specify the mapping view using the mapping_view_id parameter.
2. Run remove lun_group lun to remove the to-be-reclaimed LUN from the LUN group.
Specify the LUN group and to-be-reclaimed LUN using the lun_group_id and
3. Run show lun_group lun to check whether the to-be-reclaimed LUN has been deleted
from the LUN group successfully. Specify the LUN group using the lun_group_id
parameter.
The deleted LUN should not exist in the command output.
admin:/>show lun_group lun lun_group_id=LGID
ID Name Pool ID Capacity Helth Status Running
Status Type WWN
---- --------- ---------- ------------- ---------------
------------------- ------- ---------------------------------
1 LUN1 0 1.000TB Normal
Online Thin 60022a11000******************

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
devices.
4. Right-click Disk Drives and choose Scan for hardware changes to start scanning.
number of mapped LUNs. If they are different, check the LUN mapping and path
----End
9.2 Reclaiming Space of a Storage System (in Linux)

anymore, or some expanded space is unused in a Linux operating system, how to reclaim
9.2.1 Preparing for Space Reclamation (in Linux)

Procedure
2. Run vgdisplay -v, pvdisplay, and fdisk -l to view volume group (VG), physical volume
(PV), and disk information. Back up the information.
a. Run upadmin show vlun to view the mappings between the to-be-reclaimed LUN
and the disk on the host.
b. Run vgdisplay -v and make sure that the to-be-reclaimed disk is not in a VG.

1. Run more /var/log/messages to check whether there are any errors related to the storage
system on the host. If there are, remove the errors and proceed to the next step.
a. Run upadmin show vlun to query the status of all vLUNs. Confirm that the status
of all vLUNs is Normal.
b. Run upadmin show path and make sure that the system path status is Normal. If a
path whose status is Degrade exists, Run upadmin set phypathnormal. Specify
the path whose status is Degrade using the path_id parameter.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
3. Run upadmin set workingmode=0 to change the working mode of UltraPath.

4. Run upadmin set loadbalancemode=round-robin to change the I/O pathing mode of
UltraPath.
step.
NOTE
status is Link up.
Online.
ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
----End
9.2.2 Space Reclamation (in Linux)

This section describes how to reclaim the space used by a Linux host using full reclamation or
partial reclamation.
Full Reclamation
1. Run show mapping_view general to obtain the host group ID in the mapping view to be
reclaimed. Specify the mapping view using the mapping_view_id parameter.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
3. Run remove host initiator initiator_type=FC to remove the WWN. Specify the to-be-
reclaimed WWN using the wwn parameter.
admin:/>show initiator isfree=yes initiator_type=FC
ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default

Step 2 Run upadmin show path to check the path status of the system. The reclaimed path should
not exist in the command output.
NOTE
step.
Step 3 Delete a mapping view.

1. Run show mapping_view general to obtain the IDs of the LUN group and host group in
the mapping view to be reclaimed. Specify the mapping view using the
deleted.
Step 4 Delete a LUN Group
Step 5 Delete a port group.
parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 6 Delete a host group.

parameters.

1. Run the upRescan command to scan for disks.
#upRescan
Begin to delete LUNs whose mappings do not exist
Begin to delete LUNs whose mappings are changed
2. Run upadmin show vlun to check whether the number of disks managed by UltraPath is
the same as planned.
3. Run upadmin show path to check whether the disk path status is normal. If the status of
a path is Degrade, run upadmin set phypathnormal to set the path to Normal. In the
command, set path_id to the ID of the Degrade path.

1. Run rpm -e UltraPath to uninstall UltraPath.
2. Run rpm -qa | grep UltraPath to check whether the uninstallation is successful. If
information about UltraPath does not exist in the command output, the uninstallation is
successful.
Step 9 Run shutdown -r now to restart the host.
Step 10 Verify the storage environment on the host.

1. Run fdisk -l to check the host. In the command output, to-be-reclaimed disks should not
exist.
2. Run more /var/log/messages to check whether there are any errors related to the storage
system on the host. If there are, collect relevant information and remove the errors.
Step 11 On the switch, delete ZONE or VLAN configurations.
----End
Partial Reclamation

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
3. Run show lun_group lun to see whether the to-be-reclaimed LUN has been removed
from the LUN group. Specify the LUN group where the to-be-claimed LUN resides
Status Type WWN
---- ------------- ---------- ------------- ---------------
------------------- ------- ---------------------------------
Online Thin 60022a11000******************

1. Run the upRescan command to scan for disks.
#upRescan
3. Run upadmin show path to check whether the disk path status is normal. If the status of
a path is Degrade, run upadmin set phypathnormal to set the path to Normal. In the
command, set path_id to the ID of the Degrade path.
----End
9.3 Reclaiming Space of a Storage System (AIX)

anymore, or some expanded space is unused in an AIX operating system, how to reclaim
9.3.1 Preparing for Space Reclamation (in AIX)

Procedure
2. Run lsvg, lspv and lsdev -Cc disk to view volume group (VG), physical volume (PV),
and disk information. Back up the information.
3. Confirm that the to-be-reclaimed disk will not be used anymore.
a. Run upadm show vlun to view the mappings between the to-be-reclaimed LUN
b. Run lspv and make sure that the to-be-reclaimed disk is not in a VG.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
1. Run errpt to check whether there are any errors on the host. Remove the errors before
proceeding to the next step.
b. Run upadm show path. Check whether the system path status is Normal. If the
status of a path is Degrade, run upadm set phypathnormal. Specify the path using
the path_id parameter.
step.
NOTE
status is Link up.
Online.
ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
----End
9.3.2 Space Reclamation (in AIX)

This section describes how to reclaim the space used by an AIX host using full reclamation or
partial reclamation.
Full Reclamation
Step 1 Delete a disk device.
1. Run upadm show vlun and lsdev -Cc disk to show all LUNs and disks on the host.
2. Run rmdev -dl hdiskX to delete the aggregation device composed of the disks to be
reclaimed. hdiskX represents the aggregation device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
3. Run upadm show path and view the result in Step 1.1 to check whether the aggregation
device has been deleted.
4. Run lsdev -Cc disk and lsdev -Cc disk | wc -l and view the result in Step 1.1 to check
whether the device path file has been deleted.
1. Run show mapping_view general to obtain the host group ID in the mapping view to be
reclaimed. Specify the mapping view using the mapping_view_id parameter.
admin:/>show initiator isfree=yes initiator_type=FC WWN
Running Status Free Alias Host ID
Multipath Type ----------------- -------------------
----- ------- ---------- ------------------ 100000000000*
Online Yes -- --
Default

Step 3 Run upadm show path to check whether only the paths of the to-be-reclaimed disks are
Failed. If other paths are Failed, find out the cause and solve the problem.
NOTE
step.

deleted.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
parameters.
parameters.
1. Run lslpp -L | grep -i UltraPath to see the version of the installed UltraPath.
2. Run installp -u program_name to uninstall UltraPath, where program_name is the
name of UltraPath shown in Step 8.1.
3. Run lslpp -L | grep -i UltraPath. If the command output does not contain the UltraPath
shown in Step 8.1, the uninstallation is successful.
Step 9 Run shutdown -Fr to restart the host.
Step 10 On the switch, delete zone configurations.
----End
Partial Reclamation
Step 1 Delete a disk device.
1. Run upadm show vlun and lsdev -Cc disk to show all LUNs and disks on the host.
2. Run rmdev -dl hdiskX to delete the aggregation device composed of the disks to be
reclaimed. hdiskX represents the aggregation device.
3. Run upadm show path and view the result in Step 1.1 to check whether the aggregation
device has been deleted.
4. Run lsdev -Cc disk and lsdev -Cc disk | wc -l and view the result in Step 1.1 to check
whether the device path file has been deleted.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
admin:/>show lun_group lun
lun_group_id=LGID ID Name Pool ID Capacity
Helth Status Running Status Type WWN ----
------------- ---------- ------------- ---------------
-------------------
------- --------------------------------- 1 LUN1
0 1.000TB Normal Online
Thin 60022a11000******************
----End
9.4 Reclaiming Space of a Storage System (in HP-UX)

Part or all of services in an HP-UX operating system may not need to be running anymore, or
some expanded space may be unused. In these cases, reclaim space and then use it for new
services, thereby enhancing storage space utilization.
9.4.1 Preparing for Space Reclamation (in HP-UX)

Procedure
2. Run ioscan -fnkC disk and vgdisplay -v to view information about a disk in a volume
group (VG) and back up the information.
a. Run ioscan -fnkC disk to view the mappings between the to-be-reclaimed LUN
b. Run vgdisplay -v and make sure that the to-be-reclaimed disk is not in a VG.
1. Run tail -200 /var/adm/syslog/syslog.log to check the host status. If an error exists on
storage device, remove it and proceed to the next step.
a. Run scsimgr get_attr -a leg_mpath_enable and make sure that Native Multi-
Pathing (NMP) is enabled.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
b. Run scsimgr lun_map -D /dev/rdisk/diskX to view disk path information, where

diskX represents a disk on the host.
c. Run scsimgr get_info -D /dev/rdisk/diskX to view disk multipathing settings.
In the command output, make sure that the path status is ACTIVE and the load
balancing mode is round_robin.
step.
NOTE
status is Link up.
Online.
ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
----End
9.4.2 Space Reclamation (in HP-UX)

This section describes how to reclaim the space used by an HP-UX host in full reclamation or
partial reclamation mode using an HP-UX 11.31 host as an example.
Full Reclamation
1. Run show mapping_view general to obtain the host group ID in the to-be-reclaimed
mapping view. Specify which mapping view to reclaim using the mapping_view_id
parameter.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
admin:/>show initiator isfree=yes initiator_type=FC
ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default

Step 2 Run upadm show path to check the path status of the system. The reclaimed path should not
exist in the command output.
NOTE
step.

deleted.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
parameters.

parameters.
Step 7 Delete a device file.

1. Run ioscan -fNkC disk and ioscan -fNkC disk | grep -i HUAWEI | wc -l to show all
LUNs.
2. Delete a device path file.
a. Run ioscan -fNC disk to scan for system disks.
b. Run ioscan -fNkC disk | grep -i NO_HW to check whether there are disks whose
status is NO_HW.
c. Run ioscan -fNkC disk | grep -i NO_HW | awk '{ print $3}' | xargs -n1 rmsf -C
disk -H to delete disks whose status is NO_HW.
d. Run ioscan -fNkC disk | grep -i NO_HW to check whether there are disks whose
status is NO_HW. If there are, delete them.
3. Run ioscan -fNkC disk and ioscan -fNkC disk | grep -i HUAWEI | wc -l again and
view the result in Step 7.1 to check whether the device path file has been deleted.

1. Run ioscan -fNkC disk to check the status of the disk device file on the host. Disks
whose status is NO_HW should not exist.
2. Run tail -200 /var/adm/syslog/syslog.log to check whether there are any errors. If there
are, collect relevant information and remove the errors.
Step 9 On the switch, delete zone configurations.
----End
Partial Reclamation

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Status Type WWN
---- ------------- ---------- ------------- ---------------
------------------- ------- ---------------------------------
Online Thin 60022a11000******************

1. Run ioscan -fNC disk to scan the status of remaining disk paths.
2. Run tail -200 /var/adm/syslog/syslog.log to check whether there are any errors. If there
are, collect relevant information and remove the errors.
----End
9.5 Emergency Rollback of Space Reclamation

This section describes how to perform an emergency rollback when you encounter an
abnormality or fault during space reclamation.
Emergency rollback of space reclamation covers both the full reclamation and partial
reclamation scenarios. Figure 9-3 and Figure 9-4 shows the major procedures.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 9-3 Emergency rollback procedure (full reclamation)
Start
Applicable to Windows,
Reinstall UltraPath. Linux and AIX hosts.
Restart hosts. Applicable to Windows,

Create a LUN group and add to-be-

reclaimed LUNs to the LUN group.
Create a port group and add to-be-

reclaimed ports to the port group.
Create a host group and add to-be-

reclaimed hosts to the host group.
Add initiators to the to-be-

reclaimed host.
Create mapping views.
Mandatory Optional parent

End parent items items
Figure 9-4 Emergency rollback procedure (partial reclamation)
Start
Add reclaimed LUNs

back to the LUN group.
Rescan for disks on the

host.
End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 10 Managing Application-Based Storage Resources
10 Managing Application-Based Storage

Resources
About This Chapter
Supporting applications including email boxes, databases, and virtual machines, the storage
system automatically offers storage management best practices based on service
configurations.
10.1 Managing Microsoft Exchange Instances

After configuring storage resources allocated to Microsoft Exchange applications (Exchange
storage resources for short), you can adjust storage resource configurations to meet constantly
changing service requirements.
10.2 Managing VMware Instances
After configuring storage resources allocated to VMware applications (VMware storage
resources for short), you can adjust storage resource configurations to meet constantly
10.3 Managing Hyper-V Instances
After configuring storage resources allocated to Hyper-V applications (Hyper-V storage
10.4 Managing Oracle Instances
After configuring storage resources allocated to Oracle applications (Oracle storage resources
for short), you can adjust storage resource configurations to meet constantly changing service
requirements.
10.5 Managing SQL Server Instances
After configuring storage resources allocated to SQL Server applications (SQL Server storage
10.6 Managing Application-based Snapshots
You can create a snapshot for an application, and browse, modify, activate, deactivate, start
rolling back, stop rolling back, or delete the snapshot.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
10.1 Managing Microsoft Exchange Instances

After configuring storage resources allocated to Microsoft Exchange applications (Exchange
storage resources for short), you can adjust storage resource configurations to meet constantly
10.1.1 Browsing Information About a Microsoft Exchange

Instance
This operation allows you to view basic information about created Microsoft Exchange
instances.
Prerequisites
At least one Microsoft Exchange instance has been created in the storage system.
Procedure
Step 1 Go to the Microsoft Exchange management page.

2. In the View and Management area, click Application.
The Application management page is displayed.
3. Click Microsoft Exchange.
The Microsoft Exchange management page is displayed.
Step 2 In the function pane, view information about a Microsoft Exchange instance.
Table 10-1 Parameters of a Microsoft Exchange instance

Name Name of a Microsoft Exchange [Example]

instance. ExchangeApp_001
ID ID of a Microsoft Exchange [Example]

instance. 0
Version Version of the Microsoft Exchange [Example]

software. Exchange 2007
Capacity Total capacity allocated to a [Example]

Microsoft Exchange instance. 578.265 GB

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 3 Optional: Select a Microsoft Exchange instance to view Storage Resource and Snapshot of
the instance in the Details area.
----End
10.1.2 Modifying General Properties of a Microsoft Exchange

Instance
This operation allows you to modify the general properties of a Microsoft Exchange instance.
Procedure
Step 1 Go to the Properties of Exchange Storage Resource page.


3. Click Exchange.
The Exchange management page is displayed.

4. Select the Microsoft Exchange instance whose general properties you want to modify
and click Properties.
The Properties of Exchange Storage Resource dialog box is displayed.
Step 2 Click the General tab to modify the general properties of the selected Microsoft Exchange
instance.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-2 Parameters in the general properties of a Microsoft Exchange instance


instance. ExchangeApp_001
The name must meet the following
requirements so that the instance is
available to host applications:
l Must be unique.
l Contains only letters, digits,
underscores (_), periods (.), and
hyphens (-).
l Contains 1 to 22 characters.
Description Description of a Microsoft [Example]

Exchange instance. -
Step 3 Click OK.

The Execution Result dialog box is displayed indicating operation success.
Step 4 Click Close.
----End
10.1.3 Viewing the Owning Mapping View of a Microsoft

Exchange Instance
This operation allows you to view information about the mapping view to which a Microsoft
Exchange instance belongs.
Prerequisites
At least one Microsoft Exchange instance has been created in the storage system.
Context
After the application instance is successfully created, the system creates mapping view
xx_Mapping by default. xx indicates the instance name.
Procedure


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

4. Select the Microsoft Exchange instance whose owning mapping view you want to view
and click Properties.
The Properties of Exchange Storage Resource dialog box is displayed.
Step 2 Click the Owning Mapping View tab.
Table 10-3 Parameters of the owning mapping view of a Microsoft Exchange instance
Name Name of the owning mapping view [Example]

of a Microsoft Exchange instance. mappingview001
ID ID of the owning mapping view of [Example]

a Microsoft Exchange instance. 1
----End
10.1.4 Creating a Microsoft Exchange Snapshot

After a snapshot is created and activated for a Microsoft Exchange instance, a data duplicate
group of the Microsoft Exchange instance is generated. Users can read and write duplicates in
the duplicate group without changing the source data. The data security is enhanced.
Prerequisites
l At least one Microsoft Exchange instance has been created in the storage system.
l The snapshot license is valid.
Context
The snapshot created for a Microsoft Exchange instance is actually a snapshot group. Since
when you create a snapshot for a Microsoft Exchange instance, you actually create a snapshot
for each LUN contained in the Microsoft Exchange instance. You can choose Data
Protection > Snapshot to view the snapshot of each LUN contained in the Microsoft
Exchange instance.
Procedure
Step 1 Go to the Create Snapshot page.

2. In the Storage Configuration and Tuning area, click Application.


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

4. Select the Microsoft Exchange instance for which you want to create a snapshot and
click Create Snapshot.
The Create Snapshot dialog box is displayed.
Step 2 Set snapshot parameters.
Table 10-4 Parameters of a Microsoft Exchange snapshot


snapshot. ExchangeApp_001_Snap_001
The name must meet the following
requirements so that the snapshot
is available to host applications:
l Must be unique.
hyphens (-).
Description Description of a Microsoft [Example]

Exchange snapshot. -
Activate Now If this option is selected, a [Example]

snapshot is activated immediately Activate Now
after creation.
Step 3 Confirm your settings.

1. Click OK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Click Close.
----End
Follow-up Procedure
After Microsoft Exchange snapshots are created, you can select a Microsoft Exchange
instance and click the Snapshot tab in Details. Then you can operate the snapshot of the
Microsoft Exchange instance based on service requirements.
10.2 Managing VMware Instances

After configuring storage resources allocated to VMware applications (VMware storage
10.2.1 Browsing Information About a VMware Instance

This operation allows you to view basic information about created VMware instances.
Prerequisites
At least one VMware instance has been created in the storage system.
Procedure
Step 1 Go to the VMware management page.

3. Click VMware.
The VMware management page is displayed.
Step 2 In the function pane, view information about a VMware instance.

Table 10-5 Parameters of a VMware instance
Name Name of a VMware instance. [Example]

VMwareApp_002

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
ID ID of a VMware instance. [Example]

1
Type Type of a VMware instance. The [Example]

value can be Virtual desktop or Virtual desktop
Virtual server.
Capacity Total capacity allocated to a [Example]

VMware instance. 678.000 GB
Step 3 Optional: Select a VMware instance to view Storage Resource and Snapshot of the instance
in the Details area.
----End
10.2.2 Modifying the General Properties of a VMware Instance

This operation allows you to modify the general properties of a VMware instance.
Procedure
Step 1 Go to the Properties of VMware Storage Resource page.

3. Click VMware.
4. Select the VMware instance whose general properties you want to modify and click
Properties.
The Properties of VMware Storage Resource dialog box is displayed.
Step 2 Click the General tab to modify the general properties of the selected VMware instance.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-6 Parameters in the general properties of a VMware instance


The name must meet the following VMwareApp_002
l Must be unique.
hyphens (-).
Description Description of a VMware instance. [Example]

-
Step 3 Click OK.

Step 4 Click Close.
----End
10.2.3 Viewing the Owning Mapping View of a VMware Instance

This operation allows you to view information about the mapping view to which a VMware
instance belongs.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Context
Procedure
Step 1 Go to the Properties of VMware Storage Resource page.

3. Click VMware.
4. Select the VMware instance whose owning mapping view you want to view and click
Properties.
The Properties of VMware Storage Resource dialog box is displayed.
Table 10-7 Parameters of the owning mapping view of a VMware instance

Name Name of the owning mapping [Example]

view of a VMware instance. mappingview001

a VMware instance. 1
----End
10.2.4 Creating a VMware Snapshot

After a snapshot is created and activated for a VMware instance, a data duplicate group of the
VMware instance is generated. Users can read and write this duplicate without changing the
source data. The data security is enhanced.
Prerequisites
l At least one VMware instance has been created in the storage system.
Context
l The snapshot created for a VMware instance which doesn't use shared folders is actually
a snapshot group. Since when you create a snapshot for a VMware instance, you actually

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
create a snapshot for each LUN contained in the VMware instance. You can choose Data
Protection > Snapshot to view the snapshot of each LUN contained in the VMware
instance.
l The snapshot created for a VMware instance which use shared folders is actually a
snapshot for a file system.
Procedure

3. Click VMware.
4. Select the VMware instance for which you want to create a snapshot and click Create
Snapshot.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-8 Parameters of a VMware snapshot

The name must meet the following VMwareApp_002_Snap_001
l Must be unique.
underscores (_), periods (.),
and hyphens (-).
Description Description of a VMware [Example]

snapshot. -

after creation.

1. Click OK.
2. Click Close.
----End
Follow-up Procedure
After VMware snapshots are created, you can select a VMware instance and click the
Snapshot tab in Details. Then you can operate the snapshot of the VMware instance based on
service requirements.
10.3 Managing Hyper-V Instances

After configuring storage resources allocated to Hyper-V applications (Hyper-V storage
10.3.1 Browsing Information About a Hyper-V Instance

This operation allows you to view basic information about created Hyper-V instances.
Prerequisites
At least one Hyper-V instance has been created in the storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 Go to the Hyper-V management page.

3. Click Hyper-V.
The Hyper-V management page is displayed.
Step 2 In the function pane, view information about a Hyper-V instance.

Table 10-9 Parameters of a Hyper-V instance

Name Name of a Hyper-V instance. [Example]

HypervApp_003
ID ID of a Hyper-V instance. [Example]

2
Type The type of a Hyper-V instance can [Example]

be Virtual desktop or Virtual Virtual desktop
server.
Capacity Total capacity allocated to a Hyper- [Example]

V instance. 1.316 TB
Step 3 Optional: Select a Hyper-V instance to view Storage Resource and Snapshot of the instance
----End
10.3.2 Modify the General Properties of a Hyper-V Instance

This operation allows you to modify the general properties of a Hyper-V instance.
Procedure
Step 1 Go to the Properties of Hyper-V Storage Resource page.


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

3. Click Hyper-V.

4. Select the Hyper-V instance whose general properties you want to modify and click
Properties.
The Properties of Hyper-V Storage Resource dialog box is displayed.
Step 2 Click the General tab to modify the general properties of the selected Hyper-V instance.
Table 10-10 Parameters in the general properties of a Hyper-V instance
Name Name of a Hyper-V instance. [Example]

The name must meet the following HypervApp_003
requirements so that the instance
l Must be unique.
and hyphens (-).
Description Description of a Hyper-V instance. [Example]

-
Step 3 Click OK.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Click Close.
----End
10.3.3 Viewing the Owning Mapping View of a Hyper-V Instance

This operation allows you to view information about the mapping view to which a Hyper-V
instance belongs.
Context
Procedure
Step 1 Go to the Properties of Hyper-V Storage Resource management page.


3. Click Hyper-V.

4. Select the Hyper-V instance whose owning mapping view you want to view and click
Properties.
The Properties of Hyper-V Storage Resource dialog box is displayed.
Table 10-11 Parameters of the owning mapping view of a Hyper-V instance


of a Hyper-V instance. mappingview001

a Hyper-V instance. 1
----End
10.3.4 Creating a Hyper-V Snapshot

After a snapshot is created and activated for a Hyper-V instance, a data duplicate of the
Hyper-V instance is generated. Users can read and write this duplicate without changing the

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
l At least one Hyper-V instance has been created in the storage system.
Context
The snapshot created for a Hyper-V instance is actually a snapshot group. Since when you
create a snapshot for a Hyper-V instance, you actually create a snapshot for each LUN
contained in the Hyper-V instance. You can choose Data Protection > Snapshot to view the
snapshot of each LUN contained in the Hyper-V instance.
Procedure
Step 1 Go to the Create Snapshot management page.

3. Click Hyper-V.
4. Select the Hyper-V instance for which you want to create a snapshot and click Create
Snapshot.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-12 Parameters of a Hyper-V snapshot
Name Name of a Hyper-V snapshot. [Example]

The name must meet the following HypervApp_003_Snap_001
l Must be unique.
hyphens (-).
Description Description of a Hyper-V [Example]

snapshot. -

after creation.

1. Click OK.
2. Click Close.
----End
Follow-up Procedure
After Hyper-V snapshots are created, you can select a Hyper-V instance and click the
Snapshot tab in Details. Then you can operate the snapshot of the Hyper-V instance based on
service requirements.
10.4 Managing Oracle Instances

After configuring storage resources allocated to Oracle applications (Oracle storage resources
for short), you can adjust storage resource configurations to meet constantly changing service
requirements.
10.4.1 Browsing Information About an Oracle Instance

This operation allows you to view basic information about created Oracle instances.
Prerequisites
At least one Oracle instance has been created in the storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 Go to the Oracle management page.

3. Click Oracle.
The Oracle management page is displayed.
Step 2 In the function pane, view information about an Oracle instance.
Table 10-13 Parameters of an Oracle instance

Name Name of an Oracle instance. [Example]

OracleApp_004
ID ID of an Oracle instance. [Example]

3
Capacity Storage capacity allocated to an [Example]

Oracle instance. 186.000 GB
Step 3 Optional: Select an Oracle instance to view Storage Resource and Snapshot of the instance
----End
10.4.2 Modifying the General Properties of an Oracle Instance

This operation allows you to modify the general properties of an Oracle instance.
Procedure

3. Click Oracle.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4. Select the Oracle instance whose general properties you want to modify and click
Properties.
The Properties of Oracle Storage Resource dialog box is displayed.
Step 2 Click the General tab to modify the general properties of the selected Oracle instance.
Table 10-14 Parameters in the general properties of an Oracle instance

Name Name of an Oracle instance. [Example]

The name must meet the following OracleApp_004
l Must be unique.
hyphens (-).
Description Description of an Oracle instance. [Example]

-
Step 3 Click OK.

Step 4 Click Close.
----End
10.4.3 Viewing the Owning Mapping View of an Oracle Instance

This operation allows you to view information about the mapping view to which an Oracle
instance belongs.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Context
Procedure
Step 1 Go to the Properties of Oracle Storage Resource page.

3. Click Oracle.
4. Select the Oracle instance whose owning mapping view you want to view and click
Properties.
The Properties of Oracle Storage Resource dialog box is displayed.
Table 10-15 Parameters of the owning mapping view of an Oracle instance


of an Oracle instance. mappingview001

an Oracle instance. 1
----End
10.4.4 Creating an Oracle Snapshot

After a snapshot is created and activated for an Oracle instance, a data duplicate group of the
Oracle instance is generated. Users can read and write this duplicate without changing the
Prerequisites
l At least one Oracle instance has been created in the storage system.
Context
The snapshot created for an Oracle instance is actually a snapshot group. Since when you
create a snapshot for an Oracle instance, you actually create a snapshot for each LUN

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
contained in the Oracle instance. You can choose Data Protection > Snapshot to view the
snapshot of each LUN contained in the Oracle instance.
Procedure

3. Click Oracle.
4. Select the Oracle instance for which you want to create a snapshot and click Create
Snapshot.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-16 Parameters of an Oracle snapshot
Name Name of an Oracle snapshot. [Example]

The name must meet the following OracleApp_004_Snap_001
requirements so that the snapshot is
l Must be unique.
hyphens (-).
Description Description of an Oracle snapshot. [Example]

-
Activate Now If this option is selected, a snapshot [Example]

is activated immediately after Activate Now
creation.

1. Click OK.
2. Click Close.
----End
Follow-up Procedure
After Oracle snapshots are created, you can select an Oracle instance and click the Snapshot
tab in Details. Then you can operate the snapshot of the Oracle instance based on service
requirements.
10.5 Managing SQL Server Instances

After configuring storage resources allocated to SQL Server applications (SQL Server storage
10.5.1 Browsing Information About an SQL Server Instance

This operation allows you to view basic information about created SQL Server instances.
Prerequisites
At least one SQL Server instance has been created in the storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 Go to the SQL Server management page.

3. Click SQL Server.
The SQL Server management page is displayed.
Step 2 In the function pane, view information about an SQL Server instance.
Table 10-17 Parameters of an SQL Server instance

Name Name of an SQL Server instance. [Example]

SQLServerApp_004
ID ID of an SQL Server instance. [Example]

3
Capacity Total capacity allocated to an SQL [Example]

Server instance. 86.000 GB
Step 3 Optional: Select an SQL Server instance to view Storage Resource and Snapshot of the
instance in the Details area.
----End
10.5.2 Modifying the General Properties of an SQL Server

Instance
This operation allows you to modify the general properties of an SQL Server instance.
Procedure
Step 1 Go to the Properties of SQL Server Storage Resource page.


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

4. Select the SQL Server instance whose general properties you want to modify and click
Properties.
The Properties of SQL Server Storage Resource dialog box is displayed.
Step 2 Click the General tab to modify the general properties of the selected SQL Server instance.
Table 10-18 Parameters in the general properties of an SQL Server instance

Name Name of an SQL Server instance. [Example]

The name must meet the SQLServerApp_004
following requirements so that
the instance is available to host
applications:
l Must be unique.
and hyphens (-).
Description Description of an SQL Server [Example]

instance. -
Step 3 Click OK.

Step 4 Click Close.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
10.5.3 Viewing the Owning Mapping View of an SQL Server

Instance
This operation allows you to view information about the mapping view to which an SQL
Server instance belongs.
Context
Procedure
Step 1 Go to the Properties of SQL Server Storage Resource page.



4. Select the SQL Server instance whose owning mapping view you want to view and click
Properties.
The Properties of SQL Server Storage Resource dialog box is displayed.
Table 10-19 Parameters of the owning mapping view of an SQL Server instance
Name Name of the owning mapping [Example]

view of an SQL Server instance. mappingview001

an SQL Server instance. 1
----End
10.5.4 Creating an SQL Server Snapshot

After a snapshot is created and activated for an SQL Server instance, a data duplicate group of
the SQL Server instance is generated. Users can read and write this duplicate without
changing the source data. The data security is enhanced.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
l At least one SQL Server instance has been created in the storage system.
Context
The snapshot created for an SQL Server instance is actually a snapshot group. Since when
you create a snapshot for an SQL Server instance, you actually create a snapshot for each
LUN contained in the SQL Server instance. You can choose Data Protection > Snapshot to
view the snapshot of each LUN contained in the SQL Server instance.
Procedure

4. Select the SQL Server instance for which you want to create a snapshot and click Create
Snapshot.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-20 Parameters of an SQL Server snapshot

Name Name of an SQL Server snapshot. [Example]

The name must meet the SQLServerApp_004_Snap_001
following requirements so that the
snapshot is available to host
applications:
l Must be unique.
and hyphens (-).
Description Description of an SQL Server [Example]

snapshot. -

after creation.

1. Click OK.
2. Click Close.
----End
Follow-up Procedure
After SQL Server snapshots are created, you can select a SQL Server instance and click the
Snapshot tab in Details. Then you can operate the snapshot of the SQL Server instance based
on service requirements.
10.6 Managing Application-based Snapshots

You can create a snapshot for an application, and browse, modify, activate, deactivate, start
rolling back, stop rolling back, or delete the snapshot.
Context
An application-based snapshot is a snapshot group in essence. The snapshot group contains
snapshots of multiple LUNs of the application. Those LUNs are specifically created for the
application.
10.6.1 Viewing Snapshot Information

This operation enables you to view the information about snapshots, helping you learn about
the health status and running status of snapshots.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
At least one application-based snapshot has been created in the system.
Procedure
Step 1 Go to the Apply page of snapshots.

2. In the function pane on the left, click Snapshot.
3. In the function pane on the left, click the Apply tab.
Step 2 From the drop-down list in the upper area of the left function pane, select an application type.
Step 3 In the upper area of the left function pane, view the application-based snapshot information.
Table 10-21 Application-based snapshot information

Name Name of a snapshot. [Value range]

l The name
must be
unique.
l The name
contains
letters, digits,
underscores
(_), periods
(.), and
hyphens (-).
l The name
contains 1 to
31 characters.
[Example]
ExchangeApp_0
01_Snap_001
ID ID of a snapshot. [Example]
1
Source Resource Name of an application. [Example]

Name ExchangeApp_0
01
Step 4 In the upper area of the left function pane, select an application-based snapshot.
Step 5 In the lower area of the left function pane, view the information about the snapshot of each
LUN contained in the application-based snapshot. Table 10-22 describes related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 10-22 LUN snapshot information


l The name
must be
unique.
l The name
contains
letters, digits,
underscores
(_), periods
(.), and
hyphens (-).
l The name
contains 1 to
31 characters.
[Example]
ExchangeApp_0
01_Snap_001_1
ID ID of a snapshot. [Example]
2
Health Status Indicates whether a snapshot is normal. The [Example]

possible value can be Normal or Fault. Normal
Running Status Indicates whether a snapshot is working properly. [Example]

The possible value can be Activated, Restore, or Activated
Inactive.
Source LUN Name of the source LUN of a snapshot. [Example]

Source LUN is a LUN where source data resides. ExchangeApp_0
01_Email_1
Source LUN ID ID of the source LUN of a snapshot. [Example]

2
Source LUN Capacity of the source LUN of a snapshot. [Example]

Capacity 1.000 GB
Snapshot Capacity of a snapshot. [Example]

Capacity 1.000 MB
Activated At Time when a snapshot is activated. [Example]

2013-11-16
14:12:25 UTC
+08:00

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Mapping Indicates whether a snapshot is mapped to a [Example]

mapping view. The possible value can be Mapped Unmapped
or Unmapped.
WWN World Wide Name (WWN) of a snapshot. [Example]

210235G6LLZ0
B8000008
Rollback Started Time when a snapshot rollback is started. [Example]

At 2014-05-30
10:15:25 UTC
+08:00
Rollback Ended Time when a snapshot rollback is completed. [Example]

At 2014-05-30
10:15:45 UTC
+08:00
Rollback Progress of a snapshot rollback. [Example]

Progress (%) 50
Rollback Speed Rate at which a snapshot is rolled back. The [Example]

possible value can be Low, Medium, High, or High
Highest.
l Low or Medium, applies to scenarios where
the service load on the storage system is heavy.
l High or Highest, applies to scenarios where
the service load on the storage system is light.
----End
10.6.2 Managing the Properties of a Snapshot

This function allows you to view the properties of a snapshot and modify some of the
parameters.
Modifying the General Properties of an Application-based Snapshot

This operation enables you to view the general properties of a snapshot and modify some of
the parameters.
Prerequisites
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Step 3 In the upper area of the left function pane, select the snapshot that you want to modify and
click Properties on the menu bar.
The Properties of Snapshot dialog box is displayed.
Step 4 Modify the general properties of the snapshot.

Table 10-23 lists related parameters.
Table 10-23 General properties of a snapshot
Paramete Description Setting

r

l The name must
be unique.
l The name
contains letters,
digits,
underscores
(_), periods (.),
and hyphens
(-).
l The name
contains 1 to
31 characters.
[Example]
ExchangeApp_001
Descriptio Description of a snapshot. [Example]

n -
Step 5 Click OK.

The Results dialog box is displayed, indicating that the operation succeeded.
Step 6 Click Close.
----End
Modifying the General Properties of the Snapshot of a LUN

This operation enables you to view the general properties of a snapshot and modify some of
the parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
Procedure

Step 4 In the lower area of the left function pane, select the snapshot of a LUN and click Properties
on the menu bar.
Step 5 Modify the general properties of the snapshot.

1. Optional: Click the General tab.
2. Modify the general properties of the snapshot.
Table 10-24 lists related parameters.
Table 10-24 General properties of a snapshot

Paramet Description Setting
er

The name
must be
unique.
The name
contains
letters, digits,
underscores
(_), periods
(.), and
hyphens (-).
The name
contains 1 to
31 characters.
[Example]
ExchangeApp_00
1_Snap_001_1
Descripti Description of a snapshot. [Example]

on -

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
3. Click OK.
The Results dialog box is displayed, indicating that the operation succeeded.
4. Click Close.
----End
Viewing the Application-based Snapshot Group

This operation enables you to view the snapshot for each LUN contained in the application
instance.
Prerequisites
Context
The snapshot created for a application instance is actually a snapshot group. Since when you
create a snapshot for application instance, you actually create a snapshot for each LUN
contained in the application instance.
Procedure
Step 1 Go to the Application page of snapshots.

3. In the function pane on the left, click the Application tab.
Step 3 In the upper area of the left function pane, select an application-based snapshot and click
Properties on the menu bar.
Step 4 Click the Snapshot List tab, view the application-based snapshot group.
----End
Viewing the Owning LUN Group of the Snapshot of a LUN

This operation enables you to view the name and ID of a snapshot's owning LUN group.
Prerequisites
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Step 4 In the lower area of the left function pane, select the snapshot of a LUN and click Properties
on the menu bar.
Step 5 Viewing the owning LUN group of the snapshot.
1. Click the Owning LUN Group tab.
2. View the properties of the owning LUN group.
Table 10-25 Owning LUN group parameters

Name Name of the LUN [Value range]

group. The name can contain only
letters, digits, periods (.),
underscores (_), and hyphens
(-).
The name contains 1 to 31
characters.
The name must be unique.
[Example]
ExchangeApp_001_Snap_001
ID ID of the LUN group. [Example]

1
3. Click OK.
----End
10.6.3 Activating a Snapshot

After an application-based snapshot is activated, a data duplicate of the application at the
activation point in time is generated immediately.
Prerequisites
l At least one application-based snapshot has been created in the system.
l Health Status of the snapshot of each LUN contained in the application-based snapshot
is Normal.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l Running Status of the snapshot of each LUN contained in the application-based

snapshot is Inactive.
l Ensure that storage pools where LUNs contained in the application reside have enough
space to store snapshot data.
l When activating a snapshot, ensure that the used capacity of the storage pool does not
exceed the threshold. Otherwise, the snapshot fails to be activated.
Context
After an application-based snapshot is activated, all snapshots within the snapshot group are
activated. Data duplicates are generated for each LUN contained by the application at the
activation point in time.
Procedure

Step 3 In the upper area of the left function pane, select a snapshot that you want to activate and
choose More > Activate on the menu bar.
Step 4 Confirm the snapshot activation.

information and understood consequences of the operation.
2. Click OK.
3. Click Close.
----End
10.6.4 Deactivating a Snapshot

When the capacity of the storage pool where the source LUN resides becomes insufficient,
you can use this operation to cancel the snapshot function to release the capacity occupied by
snapshots for other snapshot tasks.
Prerequisites
snapshot is Activated.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Context
After an application-based snapshot group is deactivated, all snapshots contained in the
snapshot group are deactivated and become unavailable.
Procedure

Step 3 In the upper area of the left function pane, select a snapshot that you want to deactivate and
choose More > Deactivate on the menu bar.
Step 4 Confirm the snapshot deactivation.
2. Click OK.
3. Click Close.
----End
10.6.5 Rolling Back a Snapshot

You can roll back an application-based snapshot to the snapshot in time.
Prerequisites
l Health Status of the snapshot of each LUN contained in the application-based snapshot
is Normal.
snapshot is Activated.
Context
After an application-based snapshot group is rolled back, all snapshots contained in the
snapshot group are rolled back. Each LUN contained in the application is rolled back to the
snapshot activation point in time.
Precautions
l You can roll back only one snapshot of a source LUN at a time.
l You cannot roll back a snapshot if its source LUN is the primary LUN or slave LUN of a
remote replication.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l You cannot roll back a snapshot if its source LUN is used as the primary LUN of a clone.
l You can roll back a snapshot if its source LUN is used as the slave LUN of a clone, and
the clone pair is being split while the data of the primary LUN and slave LUN is
consistent or the reverse data of the primary LUN and slave LUN is inconsistent.
Procedure

Step 3 In the upper area of the left function pane, select a snapshot that you want to roll back and
choose More > Start Rollback on the menu bar.
The Roll Back Snapshot dialog box is displayed.
Step 4 Set the snapshot rollback speed.
1. From the Rollback Speed drop-down list, select a rollback speed. Available speeds are
Low, Medium, High, and Highest.
When the service load on the storage system is heavy, set the rollback speed to Low
or Medium.
When the service load on the storage system is light, set the rollback speed to High
or Highest.
2. Click OK.
Step 5 Roll back the snapshot.
2. Click OK.
3. Click Close.
----End
10.6.6 Stopping Snapshot Rollback

After you stop the rollback of an application-based snapshot, the snapshot becomes available
but the source data of the snapshot is inconsistent with the original data on the snapshot in
time.
Prerequisites
snapshot is Restore.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Context
After the rollback of an application-based snapshot group is stopped, the rollback of all
snapshots contained in the snapshot group is stopped. After the rollback is stopped, all
snapshots in the snapshot group turn into the activated state. However, the related source LUN
data is incomplete and is no longer the original data at the activation point in time.
Procedure

Step 3 In the upper area of the left function pane, select a snapshot that you want to roll back and
choose More > Stop Rollback on the menu bar.
Step 4 Confirm the snapshot rollback.

2. Click OK.
3. Click Close.
----End
10.6.7 Deleting a Snapshot

This operation deletes a snapshot. After a snapshot is deleted, resources occupied by the
snapshot are released.
Prerequisites
snapshot is Inactive.
l LUN snapshots contained in the application-based snapshot have not been mapped.
Precautions
When a snapshot LUN serves as the source LUN for LUN copy, the snapshot cannot be
deleted.
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Step 3 In the upper area of the left function pane, select a snapshot that you want to delete and click
Delete on the menu bar.
Step 4 Confirm the deletion of the snapshot.
1. Carefully read the content in the dialog box. Then select I have read the previous
information and understood consequences of the operation. for confirmation.
2. Click OK.
3. Click Close.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 11 Managing Basic Information About a Storage System
11 Managing Basic Information About a

Storage System
About This Chapter
Basic parameters of a storage system include the license file, storage system information
parameters, and system time parameters. By setting and modifying the basic parameters of a
storage system, you can record and manage the storage system.
11.1 Setting Device Time

If the system time of the storage system is inaccurate, change the system time of the storage
system. In this way, when alarms are generated, you can accurately determine the alarm
generation time based on alarm logs. This operation allows you to synchronize the client time
to the storage system and set NTP automatic synchronization or manually change the system
time.
11.2 Setting Device Information
This operation enables you to set device name and physical location of the device.
11.3 Managing License Files
License files are authority credentials for value-added functions of the storage device. During
routine maintenance, check that existing license files are available for their value-added
functions.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
11.1 Setting Device Time

If the system time of the storage system is inaccurate, change the system time of the storage
system. In this way, when alarms are generated, you can accurately determine the alarm
generation time based on alarm logs. This operation allows you to synchronize the client time
to the storage system and set NTP automatic synchronization or manually change the system
time.
Prerequisites
l Complete the NTP server configuration before setting NTP automatic synchronization.
For details about the operations, see related configuration documents of the NTP server.
l In an environment with the firewall function, when the NTP automatic synchronization
function is enabled, you need to enable port 123.
Context
l Network time protocol (NTP) is a computer system time synchronization protocol, which
can synchronize the computer system time to universal time coordinated (UTC). The
server supporting and running the NTP is referred to as the NTP server.
l By synchronizing the client time, you can adjust the storage system time to be consistent
with the client time.
l By configuring the NTP automatic synchronization, you can periodically and
automatically synchronize a storage device with the NTP server which serves as an
external time source.
Procedure
Step 1 Go to the Basic Information management page.

2. In the Viewing and Settings area, click Basic Information.
The Basic Information page is displayed.
Step 2 Change the storage device time.

1. Select the Device Time node.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Change the device time.

The storage device time can be changed in the following ways:
Synchronize client time
Select Client Time Synchronization.
NOTE
If the DeviceManager cannot obtain the time zone ID, Time Zone is displayed. Set Time
Zone to the time zone of the place where the client resides.
NTP Automatic Synchronization
i. Select NTP Automatic Synchronization.
ii. In Server IP Address, enter the IP address of the server whose time you want
to synchronize to the device.
iii. In Synchronization Period, set the period for synchronizing the server time to
the device time.
NOTE
You can set day, hours, minutes, and seconds of the synchronization period.
Manual
i. Select Manual.
ii. Click Modify.
The Change Time dialog box is displayed.
iii. Change the storage device time.
In the Date group box, change the device date.
In the Time group box, change the device time.
From the Current Time Zone drop-down list, select the time zone of the
storage device.
Step 3 Confirm the device time setting.
1. Click Save or OK.
3. Click OK.
4. Click Close.
----End
Follow-up Procedure
You can run the change system ntp command to enable or disable the Network Time
Protocol (NTP) time synchronization function. For details, see the OceanStor 5300 V3&5500
V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Command Reference.
11.2 Setting Device Information

This operation enables you to set device name and physical location of the device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 Go to the Basic Information management page.

2. In the Viewing and Settings area, click Basic Information.
The Basic Information page is displayed.
Step 2 Set the device information.

1. Select the Device Information node.
2. Set Device Name and Device Location.
Step 3 Confirm the configuration of basic information about storage devices.
1. Click Save.
2. Click Close.
----End
11.3 Managing License Files

License files are authority credentials for value-added functions of the storage device. During
routine maintenance, check that existing license files are available for their value-added
functions.
Context
A license file is a type of certificate that defines the usage scope, available functions, and
expiration date of a value-added feature. You must import a license file for each of the
following applications or functions:
l HyperSnap(Snapshot)
l HyperCopy(LUN Copy)
l HyperClone(Clone)
l HyperReplication(Remote Replication)
l HyperMirror
l SmartThin
l SmartTier
l SmartMotion
l SmartQoS
l SmartPartition
l SmartVirtualization

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l SmartMulti-Tenant
l SmartCache
l SmartMigration
l SmartErase
11.3.1 Preparations
Before applying for a license, make preparations to facilitate the license application.
Table 11-1 describes the preparations for license application.
Table 11-1 Preparations for license application
Item Description
GTS permission for the ESDP Users who have the GTS permission can apply
(applicable to Huawei service for licenses in Entitlement Activation mode. If
engineers) you do not have the GTS permission, click
Permission Application in the left navigation
tree of the ESDP home page and complete the
permission application.
ASP or Guest permission for the ESDP Users who have the ASP or Guest permission
(applicable to Huawei partners or can apply for licenses in Password Activation
customers) mode. Click Register Now on the ESDP home
page and fill in related registration information.
Then you are granted the ASP or Guest
permission.
Equipment Serial Number (ESN) An ESN is a unique character string that

identifies a device. It ensures that software is
licensed to the specified device. You can obtain
an ESN in the following ways:
l View the ESN on the mounting ear of your
device's front panel.
l On the navigation bar of the DeviceManager,
click . In the function pane, view SN

in the Basic Information area.
l Log in to the command-line interface (CLI).
Then, run the show system general
command and view SN.
11.3.2 Applying for a License

There are two ways to apply for a license: entitlement activation and password activation.
Select the application method based on your permission on the ESDP.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Applying for a License in Entitlement Activation Mode

This section describes how to apply for a license in entitlement activation mode. The
application method is suitable for users who have GTS permission.
Prerequisites
An applicant can log in to the ESDP platform (website: http://app.huawei.com/isdp).
Additionally, the applicant have the GTS permission.
If you have ASP or Guest permission only, apply for a license in Password Activation mode.
For details, see Applying for a License in Password Activation Mode.
Context
1. Concepts related to license application on the ESDP include the following:
Entitlement
Entitlement is a form of agreement between a software provider and a customer,
which entitles the customer to the scope, functions, validity period of the product
purchased or sold.
Entitlement ID
An entitlement ID is a unique ID that identifies entitlement.
Entitlement Line
An entitlement line is a unit of entitlement that can be activated. Entitlement
contains one or multiple entitlement lines.
Activation ID
An activation ID is a unique ID that identifies an entitlement line.
Equipment (Node)
A piece of equipment or node is a system device, entity, or node.
2. On the ESDP, entitlement is managed by equipment (node). License application is also
based on equipment (node).
Procedure
Step 1 Select entitlement.
1. On the home page of the ESDP, choose License Activation > Entitlement Activation.
The Step 1: Select Entitlement page is displayed.
2. In the Status field, select Ready and click Search.
The results are listed, as shown in Figure 11-1.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 11-1 Searching entitlement information
NOTE
To improve the accuracy of searching, you can input customer PO, product name, version, and
contract No. The ESDP supports fuzzy match.
3. Select one or more entitlement lines from the list. Click Next. The Step 2: Binding Of
ESN page is displayed.
Step 2 Bind the ESN.
1. Set ESN and Equipment (Node) Name, as shown in Figure 11-2.
NOTICE
Ensure that you have input the correct ESN to avoid application licenses is unavailable.
Figure 11-2 Inputting equipment (node) information
2. Select the activation information you want to operate, and click Next.
If the entitlement information differs from the equipment (node) information, the system
displays an error and asks you to reset the information. If the entitlement information is
correct, the Step 3: Confirm Activation page is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 3 Confirm all the information you have set.

If you find any information incorrect, click Back and rectify the information. If all
information is correct, click Activate License. The Step 4: Download The License page is
displayed.
Step 4 Download the license.
The information displayed depends on the number of the entitlement lines.
l If only one entitlement line is activated, the system displays Activate successfully. You
can click Download to download the license.
l If multiple entitlement lines are activated, the system generates an activation task and
displays Volume activation process. You can click To view tasks to check the status of
the task. If the task status is Success, you can download the license.
----End
Follow-up Procedure
After applying for the license, carefully store your license file, for it will be used in following
operations.
Applying for a License in Password Activation Mode

This section describes how to apply for a license in Password Activation mode. The
application method is suitable for users who have ASP or Guest permission.
Prerequisites
An applicant can log in to the ESDP platform (website: http://app.huawei.com/isdp).
Additionally, the applicant have the GTS permission.
The user has a valid license certificate that contains the activation password.
NOTE
If the user does not have a valid license certificate, the user can send the contract No. to the agent to
obtain the license certificate.
Context
1. Concepts related to license application on the ESDP include the following:
Entitlement
Entitlement is a form of agreement between a software provider and a customer,
which entitles the customer to the scope, functions, validity period of the product
purchased or sold.
Entitlement ID
An entitlement ID is a unique ID that identifies entitlement.
Entitlement Line
An entitlement line is a unit of entitlement that can be activated. Entitlement
contains one or multiple entitlement lines.
Activation ID
An activation ID is a unique ID that identifies an entitlement line.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Equipment (Node)
A piece of equipment or node is a system device, entity, or node.
2. On the ESDP, entitlement is managed by equipment (node). License application is also
based on equipment (node).
Procedure
Step 1 Enter your password for activation.
1. On the home page of the ESDP, choose License Activation > Password Activation.
The Step 1: Input Activation Password page is displayed. as shown in Figure 11-3.
Figure 11-3 Entering the Input Activation page
2. Confirm the information and select I have read the above carefully.
3. In the Activation Password field, enter the password for activation.
NOTE
Each activation password can be bound with the ESN only once. Therefore, ensure that all
information is correct to avoid application licenses is unavailable.
To enter more activation passwords, click Add.
4. Select the activation password you want to bind, and click Next. The Step 2: Input ESN
page is displayed.
Step 2 Bind the ESN.
1. In the ESN field, enter the ESN.
NOTICE
Ensure that you have input the correct ESN to avoid application licenses is unavailable.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Click Next. The Step 3: Confirm Activation page is displayed.
Step 3 Confirm all the information you have set.

1. If you find any information incorrect, click Back and rectify the information. If all
information is correct, enter a company name in the Company Name field for the
system to record and identify user information.
2. Click Activate to submit the activation task. The system displays the Operation Record
page.
For a password activation task, the name of the task generated by the system is Activate
License By Password.
Step 4 Download the license.
l Method 1: Check the task status in the task list of Operation Record. If the status
becomes Success, click Download to download the license.
l Method 2: After the task is successfully completed, the system automatically sends an
email to your registered email account. You can obtain the license from the email.
----End
Follow-up Procedure
After applying for the license, carefully store your license file, for it will be used in following
operations.
11.3.3 Importing a License

Before configuring value-added functions, ensure that the license files in use grant the
permissions to value-added functions.
Context
The license file is a *.dat file.
Procedure
Step 1 Import the license file on the DeviceManager.
1. On the navigation bar, click .

2. In the Viewing and Settings area, choose More > Manage License Files.
3. Click Inactive License tab.
4. Click Select.
5. Select the license file.
6. Click Open.
NOTE
Different web browsers may have differences on dialog box display, please operate according to
the actual display.
7. Click Upload.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Activate the license.

1. Click Activate.
2. Read the content in the dialog box carefully. After confirming the information, click OK.
The Success dialog box is displayed, stating Succeeded in activating the license file.
3. Click OK.
----End
11.3.4 Activating a License file

To enable a value-added function, import its license file to the storage device and activate the
file.
Procedure
Step 1 Go to the License Management page.

2. In the Viewing and Settings area, click More.
The More page is displayed.
3. Click License Management.
The License Management page is displayed.
Step 2 Activate a license file.

1. In the navigation tree, choose Inactive License.
2. In the function pane, click Activate.
Step 3 Confirm the activation of the license file.

1. Read the content of the dialog box carefully and click OK.
2. Click OK and you have finished activating the license file.
----End
11.3.5 Viewing an Activated License File

Before using value-added functions, check that their license files have been activated and
effective.
Procedure
Step 1 Go to the License Management page.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. In the function pane on the left, click More in the Viewing and Settings area.
Go to the More page.
3. Click License Management.
Go to the License Management page.
Step 2 Check the active license files.

1. In the navigation tree, choose Active License.
2. In the function pane, verify the information about active license files.
----End
11.3.6 Backing Up an Active License File

Back up license files so that you can re-import them if they are damaged after being activated.
Procedure
Step 1 Go to the license management page.

2. In the function pane on the left, click More in the Viewing and Settings area.
Go to the More page.
3. click License Management.
Go to the License Management page.
Step 2 Back up active license files.

1. In the navigation tree, choose Active License.
2. Click Back Up.
The File Download dialog box is displayed.
NOTE
Take IE for example.

3. Set a file name for and path to the exported license files.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4. Click Save and you have finished backing up the license files.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 12 Obtaining System Version Information
12 Obtaining System Version Information
About This Chapter
You can use DeviceManager and the command-line interface (CLI) to query and familiarize
yourself with storage system version information so that you can quickly determine matching
software versions based on the system version in maintenance. In addition, you can also use
the CLI to query historical versions of the storage system.
12.1 Obtaining Current System Version Information
12.2 Obtaining System Historical Version Information
You can use the command-line interface (CLI) to query and familiarize yourself with
historical versions of the storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
12.1 Obtaining Current System Version Information

Obtaining Current System Version Information Using DeviceManager
You can use DeviceManager to view the current storage system version.
Step 1 Log in to DeviceManager.
Go to the DeviceManager management page.
Step 2 In Basic Information, view Version. That is, you can view the current storage system
version, as shown in Figure 12-1.
Figure 12-1 Basic storage system information
You can understand the supported software version based on the obtained storage system
version and the Version Mapping when installing or upgrading UltraPath and Toolkit.
----End
Obtaining Current System Version Information Using the CLI

You can use the command-line interface (CLI) to query and familiarize yourself with storage
system version information so that you can quickly determine matching software versions
based on the system version in maintenance.
Step 2 Run the show system general command to view the storage system version.
admin:/>show system general

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
System Name : XXX.Storage

Health Status : Normal
Running Status : Normal
Total Capacity : 3.186TB
SN : XXX
Location :
Product Model : XXX
Product Version : VX00R00XCXX
High Water Level(%) : 80
Low Water Level(%) : 20
WWN : XXX
Time : 2015-07-07/15:34:05 UTC+08:00
Patch Version : SPCXXX
In the command output, the value of Product Version is the version of the current storage
system.
You can understand the supported software version based on the obtained storage system
version and the Version Mapping when installing or upgrading UltraPath and Toolkit.
----End
12.2 Obtaining System Historical Version Information

You can use the command-line interface (CLI) to query and familiarize yourself with
historical versions of the storage system.
Prerequisites
You can successfully log in to the CLI on site.
Procedure
Step 2 Run the show upgrade package command to view historical versions of the storage system.
admin:/>show upgrade package
Software Version
SN Name IP Current Version History Version Type

-------------------- ---- ------------ --------------- --------------- ----------
XXXXXXXXXXXXXXXXXXXX 0A 10.94.80.72 VX00R00XCXX -- Controller
XXXXXXXXXXXXXXXXXXXX 0B 10.94.80.73 VX00R00XCXX -- Controller
HotPatch Version
SN Name IP Current Version History Version Type

-------------------- ---- ------------ --------------- --------------- ----------
XXXXXXXXXXXXXXXXXXXX 0A 10.94.80.72 -- -- Controller
XXXXXXXXXXXXXXXXXXXX 0B 10.94.80.73 -- -- Controller
History Version indicates historical version information about the storage system, including
historical version information about the software and hot patches.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 13 Viewing System Interface Module Information
13 Viewing System Interface Module

Information
About This Chapter
System interface modules include iSCSI interface modules and Fibre Channel interface
modules. You can view information about desired interface modules based on service
requirements.
13.1 Viewing Ethernet Port Information
iSCSI interface modules are used to connect a storage system to application servers through
iSCSI links. You can view information about Ethernet ports based on service requirements.
13.2 Viewing Fibre Channel Host Port Information
Fibre Channel interface modules are used to connect a storage system to application servers
through Fibre Channel links. You can view information about Fibre Channel host ports based

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
13.1 Viewing Ethernet Port Information

iSCSI interface modules are used to connect a storage system to application servers through
iSCSI links. You can view information about Ethernet ports based on service requirements.
13.1.1 Viewing Ethernet Port Information

By viewing basic information about an Ethernet port, you can learn about its IP address,
subnet mask, and maximum transmission unit (MTU).
Prerequisites
An Ethernet interface module has been correctly installed on a controller.
Procedure
Step 1 Go to the Ethernet Port dialog box.

3. In the middle function pane, click the cabinet whose Ethernet port you want to view.
4. Click the controller enclosure where the Ethernet port resides.

6. Click the Ethernet port whose information you want to view.
The Ethernet Port dialog box is displayed.
Step 2 View the Ethernet port information. Table 13-1 describes related parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 13-1 Ethernet port parameters

Location Location of the Ethernet [Example]

port. XXX0.A1.P0 or
XXX0.R5.IOM0.P0
NOTE
The actual content displayed is
as product specifications and
user interface.
Health Status Health status of the Ethernet [Example]

port. Normal
Running Status Running status of the [Example]

Ethernet port. Link up
Working Rate (Gbit/s) Data transfer rate of the [Example]

Ethernet port. 1
IPv4 Address IPv4 address of the Ethernet [Example]

port. 192.168.1.100
Subnet Mask Subnet mask of IPv4 [Example]

address of the Ethernet port. 255.255.0.0
IPv6 Address IPv6 address of the Ethernet [Example]

port. 21DA:D3:0:2F3B:
2BB:FF:FE28:9C5B
Prefix Number of prefix characters [Example]

of IPv6 address of the 64
Ethernet port.
MAC Address MAC address of the [Example]

Ethernet port. 00:22:a1:0f:bc:90
Port Switch Switch of the Ethernet port. [Example]

Port connection will be Enable
disconnected if the port
switch is set to Disable.
MTU (Byte) Maximum size of a data [Example]

packet that can be 1500
transferred between the
Ethernet port and the
application server.
Bond Name Name of the bonded [Example]

Ethernet port. bond01

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
iSCSI Target Name Target name of the network [Example]

where the Ethernet port iqn.iscsi-target:oceanstor:
resides. 21004846fb8ca15c::
1020000:192.168.1.100;iqn.
iscsi-target:oceanstor:
21004846fb8ca15c::
1020000:21da:d3:0:2f3b:
2bb:ff:fe28:9c5b
----End
13.1.2 Viewing Bit Error Statistics

You can learn about the data transmission quality of a storage device port by checking its bit
error statistics. The access performance of application servers deteriorates upon a high bit
error rate.
Procedure
Step 1 Go to the Bit Error Statistics dialog box.

3. In the right function pane, click the cabinet whose Ethernet ports you want to view.
4. Click the controller enclosure where the bonded Ethernet ports reside.

6. Click the Ethernet port you want to view.
7. In the lower function pane, select the Ethernet port you want to view and click Bit Error
Statistics.
The Bit Error Statistics dialog box is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 View bit error information about the Ethernet port.

1. Select iSCSI from Port Type.
2. From the port list, select the port and view bit error statistics.
NOTE
To clear bit error statistics, click Clear.
----End
13.2 Viewing Fibre Channel Host Port Information

Fibre Channel interface modules are used to connect a storage system to application servers
through Fibre Channel links. You can view information about Fibre Channel host ports based
13.2.1 Viewing Fibre Channel Port Information

By viewing basic information about a Fibre Channel host port, you can learn about its
working rate, working mode, and running status.
Prerequisites
A Fibre Channel interface module has been correctly installed on a controller.
Procedure
Step 1 Go to the FC Port dialog box.

3. In the right function pane, click the cabinet whose Fibre Channel port you want to view.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

6. Click the Fibre Channel port whose information you want to view.
The FC Port dialog box is displayed.
Step 2 View the Fibre Channel port information. Table 13-2 describes related parameters.
Table 13-2 Fibre Channel port information
Location Location of the Fibre [Example]

Channel port. XXX0.A1.P0 or
XXX0.R5.IOM0.P0
NOTE
The actual content displayed is
as product specifications and
user interface.
Health Status Health status of the Fibre [Example]

Channel port. Normal
Running Status Running status of the Fibre [Example]

Channel port. Link Down
WWPN WWPN of the Fibre [Example]

Channel port. 24080035406ab5d2
Configured Rate (Gbit/s) Configured rate of the Fibre [Example]

Channel port. Autonegotiation
Working Rate (Gbit/s) Data transfer rate of the [Example]

Fibre Channel port. 1
Working Mode Working mode of the Fibre [Example]

Channel port. FC-AL

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Port Switch Switch of the Fibre Channel [Example]

port. Port connection will be Enable
disconnected if the port
switch is set to Disable.
----End
13.2.2 Viewing Bit Error Statistics

You can learn about the data transmission quality of a storage device port by checking its bit
error statistics. The access performance of application servers deteriorates upon a high bit
error rate.
Procedure
Step 1 Go to the Bit Error Statistics dialog box.

3. In the right function pane, click the cabinet whose Fibre Channel port you want to view.

6. Select the Fibre Channel port that you want to query.
7. In the lower function pane, select the Fibre Channel port you want to view and click Bit
Error Statistics.
The Bit Error Statistics dialog box is displayed.
Step 2 View bit error information about the Fibre Channel port.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
1. Select FC from Port type.

2. From the port list, select the port and view bit error statistics.
NOTE
To clear bit error statistics, click Clear.
----End
13.2.3 Querying the WWN of a Fibre Channel Port on an

Application Server
When a storage system is connected to multiple application servers through Fibre Channel,
identify the initiator to be added for a host by querying the World Wide Names (WWNs) of
Fibre Channel ports on the application servers.
Prerequisites
The Fibre Channel host bus adapter (HBA) driver is properly installed.
Windows-based application server

NOTE
The following procedure uses the Qlogic Fibre Channel HBA as an example. For details about how to
query the WWNs of other vendors' Fibre Channel HBAs, see their corresponding manuals.
Step 1 Install scli-1[1].06.16-29.windows.msi on the Windows-based application server.

NOTE
The scli-1[1].06.16-29.windows.msi software can be obtained from http://www.qlogic.com.
Step 2 Double-click the shortcut of scli-1[1].06.16-29.windows.msi on the desktop.

The software starts up automatically. The Main Menu screen is displayed, as shown in
Figure 13-1.
Figure 13-1 Main Menu screen

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 3 Type 4 after Enter Selection: and press Enter.

The HBA Selection Menu screen is displayed, as shown in Figure 13-2.
Figure 13-2 HBA Selection Menu screen
Step 4 Type 1 after Enter Selection: and press Enter.
Step 5 The HBA port information is displayed, as shown in Figure 13-3.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 13-3 WWN information screen
NOTE
The WWNs of the HBA are shown in the red frame in Figure 13-3.
----End
SUSE-based application server

NOTE
The following procedure uses the Qlogic Fibre Channel HBA as an example. For details about how to
query the WWNs of other vendors' Fibre Channel HBAs, see their corresponding manuals.
Step 1 Log in to the SUSE 9.0-based application server.

NOTE
For details about how to query the WWNs on the application servers running other versions of SUSE
Step 2 Run the cd /proc/scsi/qla2xxx command to go to the /proc/scsi/qla2xxx directory.
Step 3 Run the ls command to query the IDs of all Fibre Channel interface modules.
Step 4 Run the cat 4 |grep port command to query the information about Fibre Channel ports.
Figure 13-4 shows the information about Fibre Channel ports.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 13-4 Querying Fibre Channel port information on a SUSE-based application server
NOTE
The WWNs of the HBA are shown in the red frame in Figure 13-4.
----End
AIX-based application server

Step 1 Run the following command to query the working Fibre Channel HBA.
# lsdev -Cc adapter | grep fcs
fcs0 Available 0A-08 FC Adapter
Step 2 Run the following command to query the information about a Fibre Channel HBA.
# lscfg -vps -l fcs0
fcs0 U787F.001.DPM59Y0-P1-C1-T1
FC Adapter
Part Number.................03N5014
EC Level....................A
Serial Number...............1F8200CA1B
Manufacturer................001F
Customer Card ID Number.....280D
FRU Number.................. 03N5014
Device Specific.)ZM)........3
Network Address.............10000000C977835E
ROS Level and ID............02C82774
Device Specific.)Z0)........1036406D
Device Specific.)Z1)........00000000
Device Specific.)Z4)........FFC01231
Device Specific.)Z5)........02C82774
Device Specific.)Z8)........20000000C977835E
Device Specific.)Z9)........BS2.71X4
Device Specific.)ZA)........B1D2.70A5
Device Specific.)ZB)........B2D2.71X4
Device Specific.)ZC)........00000000
Hardware Location Code......U787F.001.DPM59Y0-P1-C1-T1
PLATFORM SPECIFIC

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Name: fiber-channel
Model: LP11000
Node: fiber-channel@1
Device Type: fcp
Physical Location: U787F.001.DPM59Y0-P1-C1-T1
NOTE
The value of Network Address in the command output indicates the WWN of the Fibre Channel HBA.
----End
Solaris-based application server

Step 1 Log in to the Solaris-based application server.
Step 2 Run the luxadm probe command.
----End
HP-UX-based application server

Step 1 Log in to the HP-UX-based application server as user root.
Step 2 Run the ioscan -fn command to query the I/O information.
The following output is displayed.

ioscan -fn Class I - H/W Path----Driver - S/W State - H/W Type ---Description
======================================================================
ba -------3 -0/3 -------lba ----- CLAIMED -BUS_NEXUS --Local PCI Bus Adapter
fc -------0 -0/3/0/0-----td ---- -CLAIMED -INTERFACE---HP TachyonTL/TS
Fibre
------------------------/dev/td0
fcp ------4 -0/3/0/0.2 -fcp ---- -CLAIMED -INTERFACE --FCP Domain
ext_bus -28 -0/3/0/0.2
-------------- .16.0.0 -fcparray -CLAIMED--INTERFACE --FCP ArrayInterfac ----
target ---6 -0/3/0/0.2--tgt ----- CLAIMED -DEVICE ---------.16.0.0.0
The output shows that the Fibre Channel HBA resides on /dev/td0.
Step 3 Run the fcsmutil command to query the WWN of the Fibre Channel HBA.
The following output is displayed.

fcsmutil /dev/td0
--------------------Vendor ID is = 0x00103c
--------------------Device ID is = 0x001028
--------------------PCI Sub-system Vendor ID is = 0x00103c
--------------------PCI Sub-system ID is = 0x000006
--------------------Topology = PTTOPT_FABRIC
--------------------Local N_Port_id is = 0x021c00
--------------------N_Port Node World Wide Name = 0x50060b0000072dad
--------------------N_Port Port World Wide Name = 0x50060b0000072dac
--------------------Driver state = ONLINE
--------------------Hardware Path is = 0/3/0/0
--------------------Number of Assisted IOs = 538248
--------------------Number of Active Login Sessions = 1
In this example, the output shows that the WWN of the Fibre Channel HBA is
0x50060b0000072dac.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Linux-based application server

Step 1 Log in to the Linux-based application server as user root.
Step 2 Run the cd /proc/scsi/qla2xxx command.
Step 3 Run the cat 4|grep port command to query the WWN of the Fibre Channel HBA.
The output shows that the WWN of the Fibre Channel HBA is the value of scsi-qlal-port0.
login as: root
root@192.168.11.211's password:
Last login: Tue Sep 28 01:40:54 2010 from 192.168.11.210
[root@localhost ~]# cd /proc/scsi/qla2xxx
[root@localhost qla2xxx]# cat 4|grep port
scsi-qla1-adapter-port=2101001b32bcda22;
scsi-qla1-port-0=21000022a100ef02:22030022a100ef02:0000e1:0;
[root@localhost qla2xxx]#
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System 14 Checking the Operating Environment of the Storage
Maintenance Guide Device
14 Checking the Operating Environment

of the Storage Device
About This Chapter
Check that the operating environment under which the storage device works meets associated
requirements to ensure the stable running of the device.
14.1 Checking the Equipment Room

The equipment room for accommodating the storage device must meet associated
requirements to ensure the stable running of the storage device. Inspect the equipment room
periodically to reduce the possibility of device failures.
14.2 Checking Racks
Properly installed racks of the storage device help ensure the stable and long-term running of
the storage device. Check rack conditions periodically to reduce device failure possibilities.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
14.1 Checking the Equipment Room

The equipment room for accommodating the storage device must meet associated
requirements to ensure the stable running of the storage device. Inspect the equipment room
periodically to reduce the possibility of device failures.
Impact on the System

The storage device imposes demanding requirements on the equipment room environment.
An unqualified environment impairs the proper running of the storage device.
Tools and Materials

Ensure that the tools and materials required for inspecting the equipment room are available.
The required tools include a thermometer, hygrometer, and multimeter.
Reference Standard
Table 14-1 lists the items and standards for inspecting an equipment room.
Table 14-1 Equipment room check items and standards

Check Item Standard
Temperature Operating temperature l 5C (41F) to 40C (104F) when the altitude

is lower than 1800 m
l The ambient temperature drops by 1C every
time the altitude increases by 220 m. when
the altitude is between 1800 m and 3000 m
Storage temperature -40C (-40F) to +70C (158F)
Humidity Operating humidity 10% R.H. to 90% R.H.
Storage humidity 5% R.H. to 95% R.H.
Altitude Operating altitude of l HDDs: -304.8 m to +3048 m (-999.99 ft. to

disks +9999.99 ft.)
l SSDs: -305 m to +3048 m (-1000.64 ft. to
+9999.99 ft.)
Non-operating altitude l HDDs: -305 m to +12192 m (-1000.64 ft. to

of disks +39999.51 ft.)
l SSDs: -305 m to +12192 m (-1000.64 ft. to
+39999.51 ft.)
Particle contaminants ISOa 14664-1 Class8

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Check Item Standard
Corrosive airborne contaminants l The copper corrosion rate is lower than 300
b/month (according to the ANSIc/
ISAd-71.04-1985 severity level G1).
l The silver corrosion rate is lower than 200 /
month.
Power Rated voltage and 5300 V3/5500 V3 AC:

supply current for controller l 200 V to 240 V,
enclosures 10%, 6 A, single-
phase, 50/60Hz
l Supports dual-live-
line input (2W
+PE), 200 V to 240
V, 10%
High voltage DC (N/A
for North America and
Canada) :
l 240 V, 20%, 6.5 A
DC:
l -48 V to -60 V,
20%, 30 A
5600 V3/5800 AC:

V3/6800 V3 l 200 V to 240 V,
10%, 10 A,
single-phase,
50/60Hz
l Supports dual-live-
line input (2W
+PE), 200 V to 240
V, 10%
Canada) :
l 240 V, 20%, 10 A

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Check Item Standard
Rated voltage and 5300 V3/5500 V3 AC:

current for disk l 100 V to 240 V,
enclosures 10%, 8 A, single-
phase, 50/60Hz
Canada) :
l 240 V, 20%, 3.5 A
DC:
l -48 V to -60 V,
20%, 18.5 A
5600 V3/5800 AC:

V3/6800 V3 l 100 V to 240 V,
10%, 8 A, single-
phase, 50/60Hz
Canada) :
l 240 V, 20%, 3.5 A
Rated voltage and l 100 V to 127 V, 10%, 10 A, single-phase,

current for high- 50/60Hz
density disk enclosure l 200 V to 240 V, 10%, 5 A, single-phase,
50/60Hz
a: International Organization for Standardization (ISO)

b: is a unit of length equal to 1/10000000000 (one ten billionth) of a meter
c: American National Standards Institute (ANSI)
d: Instrument Society of America (ISA)
Procedure
l Measure the ambient temperature using the thermometer.
l Measure the ambient humidity using the hygrometer.
l Measure the ambient altitude.
l Monitor the particle contaminants in the equipment room by a professional
environmental surveillance organization.
l Verify the power parameters of the equipment room.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Exception Handling
l If the measured temperature or humidity falls outside the normal range, tune the air
conditioners in the equipment room until the temperature or humidity falls within the
normal range.
l If a power parameter fails to meet the standard, append dedicated power lines and a
power transformer with sufficient capacity.
14.2 Checking Racks

Properly installed racks of the storage device help ensure the stable and long-term running of
the storage device. Check rack conditions periodically to reduce device failure possibilities.

The storage device imposes demanding requirements on rack conditions. An improperly
installed rack impairs the proper running of the storage device.
Tools and Materials

Ensure that the tools and materials for checking rack conditions are available. The required
tools include binding straps, an electroprobe, and a multimeter.
Reference Standard
Table 14-2 lists the items and standards for checking rack conditions.
Table 14-2 Rack condition check items and standards

Check Item Standard
General layout of Power cables (with strong electrical current) and service cables
cables (with weak electrical current) lay on different sides of a rack.
Layout of power cables Power cables are laid out orderly and arranged in a similar
manner to power cables on other racks.
Layout of service Service cables are laid out orderly and arranged in a similar
cables manner to service cables on other racks.
Cable labeling Labels are clearly marked and securely attached.
Empty slot Empty slots are covered with filler panels for proper heat
dissipation and a neat appearance.
Power cable plug One end of each power cable is fully plugged into an external
power socket and the other end into a storage device socket.
Signal cable plug Signal cables are fully plugged into appropriate device ports.
Ground cable One end of each ground cable is secured by a ground clip and the
other end is fastened to a rack ground terminal.
Power cable Two groups of power cables are available for redundancy.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Check Item Standard
Host port connection l For Ethernet ports:

1 Gbit/s Ethernet ports
One end of each network cable is fully plugged into a
storage device host port and the other end into an
application server port or a switch port.
10 Gbit/s TOE host ports
One end of each optical fiber is fully plugged into a
storage device host port and the other end into an
application server port or a switch port.
l For Fibre Channel or FCoE host ports, one end of each
optical fiber is fully plugged into a storage device host port
and the other end into an application server port or a switch
port.
Management network One end of each management network cable is fully plugged into
port connection a storage device management network port and the other end is
connected to the network where the maintenance terminal
resides.
Precaution
When you check power cables and ground cables, always follow the precautions described in
2.1 Alarm and Safety Symbols to avoid bodily injury and device damage.
Procedure
l Verify that power cables (with strong electrical current) and service cables (with weak
electrical current) lay on different sides of a rack.
l Verify that power cables and service cables are laid out orderly and arranged in a similar
manner to cables on other racks.
l Verify that labels are clearly marked and securely attached.
l Verify that vacant slots are covered with filler panels.
l Verify that one end of each power cable is fully plugged into an external power socket
and the other end into a storage device socket.
l Verify that signal cables are fully plugged into appropriate device ports.
l Verify that one end of each ground cable is secured by a ground clip and the other end is
fastened to a rack ground terminal.
l Verify that two groups of power cables are available for redundancy.
l Verify that one end of each network cable or optical fiber is fully plugged into a storage
device host port and the other end into an application server port or a switch port.
l Verify that one end of each management network cable is fully plugged into a storage
device management network port and the other end is connected to the network where
the maintenance terminal resides.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Exception Handling
If any check item fails to meet its standard, rectify the issue by referring to Table 14-2.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 15 Checking Indicators
15 Checking Indicators
About This Chapter
Indicators reflect the working status of hardware in real time. By observing these indicators,
you can quickly assess whether the hardware is correctly working.
15.1 Checking Controller Enclosure Indicators (For the 5300 V3 and 5500 V3)
Controller enclosure indicators show the running status of a controller enclosure. By checking
these indicators, you can promptly learn about the status of each module.
15.2 Checking Controller Enclosure Indicators (For the 5600 V3/5800 V3)
Controller enclosure indicators show the running status of the controller enclosure. By
checking these indicators, you can promptly learn about the status of each component module.
15.3 Checking Controller Enclosure Indicators (For the 6800 V3/6900 V3)
15.4 Checking Disk Enclosure Indicators (2U Disk Enclosure)
Disk enclosure indicators show the running status of a disk enclosure. By checking these
indicators, you can promptly learn about the status of each component module.
15.5 Checking Disk Enclosure Indicators (4U Disk Enclosure)
15.6 Checking Disk Enclosure Indicators (High-density Disk Enclosure)

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
15.1 Checking Controller Enclosure Indicators (For the

5300 V3 and 5500 V3)
Controller enclosure indicators show the running status of a controller enclosure. By checking
these indicators, you can promptly learn about the status of each module.
Reference Standard
Controller enclosure indicators are located on the front and rear panels of a controller
enclosure.
Figure 15-1, Figure 15-2, and Figure 15-3 depict the front-panel and rear-panel indicators of
the controller enclosure that has been correctly powered on.
Figure 15-1 Front-panel indicators of a 2 U 25-disk controller enclosure
1 Disk module Running indicator 2 Disk module Location/Alarm indicator
3 Controller enclosure Location indicator 4 Controller enclosure Alarm indicator
5 Controller enclosure Power indicator/Power button
Figure 15-2 Front-panel indicators of a 2 U 12-disk controller enclosure
Table 15-1 lists the states and their meanings of the controller enclosure front-panel indicators
shown in Figure 15-1 and Figure 15-2.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 15-1 Controller enclosure front-panel indicator states and their meanings
Module No. Indicator Normality Abnormality
Disk 1 Disk module l Steady green: Off: The disk

module Running indicator The disk module module is power
is working off or powered on
correctly. incorrectly.
l Blinking green:
Data is being
written to and
read from the
disk module.
2 Disk module Alarm/ Off: The disk l Steady red: The

Location indicator module is working disk module is
correctly or is hot- faulty.
swappable. l Blinking red:
The disk
module is being
located.
System 3 Controller enclosure Blinking blue: The Off: The controller

enclosure Location indicator controller enclosure enclosure is not
is being located. located.
4 Controller enclosure Off: The controller Steady red: A

Alarm indicator enclosure is working controller
correctly. enclosure alarm
was generated.
5 Controller enclosure l Steady green: Off: The controller

Power indicator/ The controller enclosure is
Power button enclosure is powered off or
powered on. powered by the
l Blinking green BBUs.
(0.5 Hz): The
controller
enclosure is being
powered on.
l Blinking green (1
Hz): The
controller
enclosure is in the
burn-in state.
l Blinking green (2
Hz): The
controller
enclosure is in the
operating system
boot process, or
is being powered
off.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 15-3 Rear-panel indicators on a controller enclosure (for 5500 V3 AC power)
1 Module Power indicator/Hot Swap button 2 16 Gbit/s Fibre Channel host port Link/Speed
indicator
3 Power module Running/Alarm indicator 4 Management network port Link/Active indicator
5 Management network port Speed indicator 6 Controller Power indicator
7 Controller Alarm indicator 8 Mini SAS HD expansion port indicator
9 8 Gbit/s Fibre Channel host port Link/Speed 10 BBU Running/Alarm indicator

indicator
Table 15-2 lists the states and their meanings of the controller enclosure rear-panel indicators
shown in Figure 15-3. This section lists only the indicator states and their meanings of some
interface modules. For details, see the OceanStor 5300 V3&5500 V3&5600 V3&5800
V3&6800 V3&6900 V3 Storage System V300R001 Hardware Description.
Table 15-2 Controller enclosure rear-panel indicator states and their meanings
Interface 1 Interface module l Steady green: The l Steady red: The

module Power indicator/Hot interface module interface
Swap button is working module is
correctly. faulty.
l Blinking green: l Off: The
The interface interface
module receives a module is
hot swap request. powered off or
is hot-
swappable.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2 16 Gbit/s Fibre l Steady blue: The l Steady red: The

Channel host port data transfer rate port is faulty.
Link/Speed indicator between the l Off: The link to
storage system the port is
and the down.
application server
is 16 Gbit/s.
l Blinking blue:
Data is being
transferred.
l Steady green: The
data transfer rate
between the
storage system
and the
application server
is 8 Gbit/s or 4
Gbit/s.
l Blinking green:
Data is being
transferred.
Power- 3 Power module l Steady green: The l Steady red: The

BBU Running/Alarm power supply is power module is
module indicator correct. faulty.
l Blinking green: l Off: No external
The power input is power is input.
normal but the
disk enclosure is
powered off.
Controlle 4 Management network l Steady green: The Off: The port is

r port Link/Active port is connected connected
indicator properly. abnormally.
l Blinking green:
Data is being
transferred.
5 Management network Steady orange: Data Off: The data

port Speed indicator is being transferred at transfer speed is
the highest rate. lower than the
highest speed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
6 Controller Power l Steady green: The Off: The controller

indicator controller is powered off.
enclosure is
correctly powered
on.
l The Power
indicator blinking
green and the
Alarm indicator
blinking red: The
controller is being
located
l Blinking green
(0.5 Hz): The
controller is
powered on and in
the BIOS boot
process.
l Blinking green (2
Hz): The
controller is in the
operating system
boot process, or is
being powered off.
7 Controller Alarm Off: The controller is l Steady red: A

indicator working correctly. controller alarm
was generated.
l The Alarm
indicator
blinking red and
the Power
indicator
blinking green:
The controller is
being located.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
8 Mini SAS HD l Steady blue: The l Steady red: The

expansion port data transfer rate port is faulty.
indicator between the l Off: The link to
controller the port is
enclosure and the down.
disk enclosure is 4
x 12 Gbit/s.
l Steady green: The
data transfer rate
between the
controller
enclosure and the
disk enclosure is 4
x 6 Gbit/s or 4 x 3
Gbit/s.
9 8 Gbit/s Fibre l Steady blue: The l Steady red: The

Channel host port data transfer rate port is faulty.
Link/Speed indicator is 8 Gbit/s. l Off: The link to
l Blinking blue: the port is
Data is being down.
transferred.
l Steady green: The
data transfer rate
is 4 Gbit/s or 2
Gbit/s.
l Blinking green:
Data is being
transferred.
Power- 10 BBU Running/Alarm l Steady green: The Steady red: The

BBU indicator BBU is fully BBU is faulty.
module charged.
l Blinking green (1
Hz): The BBU is
being charged.
l Blinking green (4
Hz): The BBU is
being discharged.
a: When the onboard port is a GE port, the indicators on both sides of the port are the Speed
indicator and Link/Active indicator. For details about these indicators, see 4 and 5.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
l Check onsite indicators on the front and rear panels of a controller enclosure according
to Figure 15-1, Figure 15-2 and Figure 15-3 Predetermine whether all components in
the controller enclosure are working properly.
----End
Exception Handling
If a module of the storage system is abnormal, refer to the OceanStor 5300 V3&5500
V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Hardware Description
to learn about detailed indicator meanings. Then, troubleshoot faults based on the detailed
fault information you have obtained.

5600 V3/5800 V3)
Reference Standard
Controller enclosure indicators locate on the front and rear panels of the controller enclosure.
Figure 15-4 and Figure 15-5 depict the front-panel and rear-panel indicators of the controller
enclosure that has been correctly powered on.
Figure 15-4 Controller enclosure front-panel indicators
1 2
BB U BB U BB U BB U 3
7 6 5 4
1 Running/Alarm indicator on a BBU 2 Location indicator on the controller enclosure
3 Alarm indicator on the controller enclosure 4 Power indicator/Power button on the controller enclosure
5 Fan module running/alarm indicator 6 Controller power indicator
7 Controller alarm indicator

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 15-3 lists the states and meanings of the controller enclosure front-panel indicators
shown in Figure 15-4.
BBU 1 Running/Alarm l Steady green: Steady red: The

indicator on a BBU The BBU is fully BBU is faulty.
charged.
l Blinking green (1
Hz): The BBU is
being charged.
l Blinking green (4
Hz): The BBU is
being discharged.
System 2 Location indicator on Blinking blue: The Off: The controller

enclosure the controller controller enclosure enclosure is not
enclosure is being located. located.
3 Alarm indicator on Off: The controller Steady red: An

the controller enclosure is working alarm about the
enclosure properly. controller
enclosure is
generated.
4 Power indicator/ l Steady green: Off: The controller

Power button on the The controller enclosure is
controller enclosure enclosure is powered off or
powered on. powered by BBUs.
l Blinking green
(0.5 Hz): The
controller
enclosure is
powered on for a
short time.
l Blinking green (1
Hz): The
controller
enclosure is in the
burn-in test.
l Blinking green (2
Hz): The
controller
enclosure is in the
operating system
boot process, or
is being powered
off.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Controller 5 Fan module running/ Steady green: Fan l Steady red: A

alarm indicator modules are working fan module is
correctly. faulty.
l Off: Fan
modules are
powered off.
6 Controller power l Steady green: Off: The controller

indicator The controller is cannot be detected
powered on. or is powered off.
l The controller
power indicator
blinking green
and the controller
alarm indicator
blinking red: The
controller is
being located.
l Blinking green
(0.5 Hz): The
controller is
powered on and
in the BIOS boot
process.
l Blinking green (2
Hz): The
controller is in
the operating
system boot
process.
7 Controller alarm l The controller Steady red: An

indicator alarm indicator alarm about the
blinking red and controller is
the controller generated.
power indicator
blinking green:
The controller is
being located.
l Off: The
controller is
working
correctly.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 15-5 Controller enclosure rear-panel indicators

1 2 34 5
12 11 10 9 8 76
1 Running/Alarm indicator on a power module 2 Power indicator on a management module
3 Management network port Speed indicator 4 Management network port Link/Active indicator
5 Power indicator/Hot Swap button on an interface 6 Speed indicator of a GE electrical port

module
7 Link/Active indicator of a GE electrical port 8 Link/Speed indicator of a 10 Gbit/s TOE port
9 Link/Speed indicator of a 10 Gbit/s FCoE port 10 Link/Speed indicator of a 16 Gbit/s Fibre

Channel port
11 Link/Speed indicator of an 8 Gbit/s Fibre Channel 12 Mini SAS HD expansion port indicator
port
Power 1 Running/Alarm l Steady green: The l Steady red: The

module indicator on a power power supply is power module is
module normal. faulty.
The power input is power input is
normal but the available.
device is powered
off.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Manage 2 Power indicator on a l Steady green: The l Steady red: The

ment management module module is working module is
module correctly. faulty.
The module module is
receives a hot powered off or
swap request. hot swappable.

highest speed.
4 Management network l Steady green: The Off: The port is

port Link/Active port is connected connected
l Blinking green:
Data is being
transferred.
Interface 5 Power indicator/Hot l Steady green: The l Steady red: The

module Swap button on an interface module interface
interface module is working module is
correctly. faulty.
swappable.
6 Speed indicator of a Steady orange: The Off: The data

GE electrical port data transfer rate transfer rate
between the between the
controller enclosure controller enclosure
and the application and the application
server is 1 Gbit/s. server is lower than
1 Gbit/s.
7 Link/Active indicator l Steady green: The Off: The

of a GE electrical port connection connection between
between the the controller
controller enclosure and the
enclosure and the application server
application server is incorrect.
is correct.
l Blinking green:
Data is being
transferred.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
8 Link/Speed indicator l Steady blue: The l Steady red: The

of a 10 Gbit/s TOE data transfer rate port is faulty.
port between the l Off: The link to
and the down.
application server
is 10 Gbit/s.
l Blinking blue:
Data is being
transferred.

of a 10 Gbit/s FCoE data transfer rate port is faulty.
and the down.
application server
is 10 Gbit/s.
l Blinking blue:
Data is being
transferred.

of a 16 Gbit/s Fibre data transfer rate port is faulty.
Channel port between the l Off: The link to
and the down.
application server
is 16 Gbit/s.
l Blinking blue:
Data is being
transferred.
l Steady green: The
data transfer rate
between the
storage system
and the
application server
is 8 or 4 Gbit/s.
l Blinking green:
Data is being
transferred.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

of an 8 Gbit/s Fibre data transfer rate port is faulty.
Channel port is 8 Gbit/s. l Off: The link to
Data is being down.
transferred.
l Steady green: The
data transfer rate
is 4 or 2 Gbit/s.
l Blinking green:
Data is being
transferred.

enclosure and a down.
disk enclosure is 4
x 12 Gbit/s.
l Steady green: The
data transfer rate
between the
controller
enclosure and a
disk enclosure is 4
x 6 Gbit/s or 43
Gbit/s.
Procedure
l Check onsite controller enclosure front-panel and rear-panel indicators according to
Figure 15-4 and Figure 15-5. Predetermine whether all component modules on the
controller enclosure are working properly.
----End
Exception Handling
If any module is abnormal, refer to the OceanStor 5300 V3&5500 V3&5600 V3&5800
V3&6800 V3&6900 V3 Storage System V300R001 Hardware Description to learn about
detailed indicator meanings. Then, troubleshoot faults based on the detailed fault information
you have obtained.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

6800 V3/6900 V3)
Reference Standard
Controller enclosure indicators locate on the front and rear panels of the controller enclosure.
Figure 15-6 and Figure 15-7 depict the front-panel and rear-panel indicators of the controller
Figure 15-6 Controller enclosure front-panel indicators
BB U BB U BB U BB U
7 6 54 3 2
1 Running/Alarm indicator on a BBU 2 Fan module running/alarm indicator
3 Controller power indicator 4 Alarm indicator on the controller enclosure
5 Power indicator/Power button on the controller enclosure 6 Location indicator on the controller enclosure
7 Controller alarm indicator
Table 15-5 lists the states and meanings of the controller enclosure front-panel indicators

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
BBU 1 Running/Alarm l Steady green: Steady red: The

indicator on a BBU The BBU is fully BBU is faulty.
charged.
l Blinking green (1
Hz): The BBU is
being charged.
l Blinking green (4
Hz): The BBU is
being discharged.
Controller 2 Fan module running/ l Steady green: Fan Off: Fan modules
alarm indicator modules are are powered off.
working
correctly.
l Steady red: A fan
module is faulty.
3 Controller power l Steady green: Off: The controller

indicator The controller is cannot be detected
powered on. or is powered off.
l The controller
power indicator
blinking green
and the controller
alarm indicator
blinking red: The
controller is
being located.
l Blinking green
(0.5 Hz): The
controller is
powered on and
in the BIOS boot
process.
l Blinking green (2
Hz): The
controller is in
the operating
system boot
process.
System 4 Alarm indicator on Off: The controller Steady red: An

enclosure the controller enclosure is working alarm about the
enclosure properly. controller
enclosure is
generated.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
5 Power indicator/ l Steady green: Off: The controller

Power button on the The controller enclosure is
controller enclosure enclosure is powered off or
powered on. powered by BBUs.
l Blinking green
(0.5 Hz): The
controller
enclosure is
powered on for a
short time.
l Blinking green (1
Hz): The
controller
enclosure is in the
burn-in test.
l Blinking green (2
Hz): The
controller
enclosure is in the
operating system
boot process, or
is being powered
off.
6 Location indicator on Blinking blue: The Off: The controller

the controller controller enclosure enclosure is not
enclosure is being located. located.
Controller 7 Controller alarm l The controller Steady red: An

indicator alarm indicator alarm about the
blinking red and controller is
the controller generated.
power indicator
blinking green:
The controller is
being located.
l Off: The
controller is
working
correctly.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 15-7 Controller enclosure rear-panel indicators
1 2
4
5
11 10 9 8 76
1 Running/Alarm indicator on a power module 2 Power indicator/Hot Swap button on an interface
module
3 Power indicator on a management module 4 Management network port Speed indicator
5 Management network port Link/Active indicator 6 Speed indicator of a GE electrical port
7 Link/Active indicator of a GE electrical port 8 Link/Speed indicator of a 10 Gbit/s FCoE port
9 Link/Speed indicator of a 16 Gbit/s Fibre Channel 10 Link/Speed indicator of an 8 Gbit/s Fibre

port Channel port
11 Mini SAS HD expansion port indicator
Power 1 Running/Alarm l Steady green: The l Steady red: The

module indicator on a power power supply is power module is
module normal. faulty.
The power input is power input is
normal but the available.
device is powered
off.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Interface 2 Power indicator/Hot l Steady green: The l Steady red: The

module Swap button on an interface module interface
interface module is working module is
correctly. faulty.
swappable.
Manage 3 Power indicator on a l Steady green: The l Steady red: The

ment management module module is working module is
module correctly. faulty.
The module module is
receives a hot powered off or
swap request. hot swappable.

highest speed.
5 Management network l Steady green: The Off: The port is

port Link/Active port is connected connected
l Blinking green:
Data is being
transferred.
Interface 6 Speed indicator of a Steady orange: The Off: The data

module GE electrical port data transfer rate transfer rate
between the between the
controller enclosure controller enclosure
and the application and the application
server is 1 Gbit/s. server is lower than
1 Gbit/s.
7 Link/Active indicator l Steady green: The Off: The

of a GE electrical port connection connection between
between the the controller
controller enclosure and the
enclosure and the application server
application server is incorrect.
is correct.
l Blinking green:
Data is being
transferred.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

of a 10 Gbit/s FCoE data transfer rate port is faulty.
and the down.
application server
is 10 Gbit/s.
l Blinking blue:
Data is being
transferred.

of a 16 Gbit/s Fibre data transfer rate port is faulty.
Channel port between the l Off: The link to
and the down.
application server
is 16 Gbit/s.
l Blinking blue:
Data is being
transferred.
l Steady green: The
data transfer rate
between the
storage system
and the
application server
is 8 or 4 Gbit/s.
l Blinking green:
Data is being
transferred.

of an 8 Gbit/s Fibre data transfer rate port is faulty.
Channel port is 8 Gbit/s. l Off: The link to
Data is being down.
transferred.
l Steady green: The
data transfer rate
is 4 or 2 Gbit/s.
l Blinking green:
Data is being
transferred.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

enclosure and a down.
disk enclosure is 4
x 12 Gbit/s.
l Steady green: The
data transfer rate
between the
controller
enclosure and a
disk enclosure is 4
x 6 Gbit/s or 43
Gbit/s.
Procedure
l Check onsite controller enclosure front-panel and rear-panel indicators according to
controller enclosure are working properly.
----End
Exception Handling
If any module is abnormal, refer to the OceanStor 5300 V3&5500 V3&5600 V3&5800
V3&6800 V3&6900 V3 Storage System V300R001 Hardware Description to learn about
detailed indicator meanings. Then, troubleshoot faults based on the detailed fault information
you have obtained.
15.4 Checking Disk Enclosure Indicators (2U Disk

Enclosure)
Reference Standard
Disk enclosure indicators locate on the front and rear panels of the disk enclosure.
Figure 15-8 and Figure 15-9 depict the front-panel and rear-panel indicators of the disk

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 15-8 Disk enclosure front-panel indicators

1 2 3
0 1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24
0 24
1 Running indicator of the disk module 2 Location/Alarm indicator of the disk module
3 Location indicator of the disk enclosure 4 Alarm indicator of the disk enclosure
5 Power indicator of the disk enclosure
Table 15-7 lists the states and their meanings of the disk enclosure front-panel indicators
Table 15-7 Disk enclosure front-panel indicator states and their meanings
Disk module 1 Running indicator l Steady green: Off: The disk

of the disk module The disk module module is
is working powered off or
correctly. powered on
l Blinking green: incorrectly.
Data is being
read and written
on the disk
module.
2 Alarm/Location l Blinking red: Steady red: The

indicator of the disk The disk module disk module is
module is being located. faulty.
l Off: The disk
module is
working
correctly or hot
swappable.
System 3 Location indicator Blinking blue: The Off: The disk

enclosure of the disk disk enclosure is enclosure is not
enclosure being located. detected.
4 Alarm indicator of Off: The disk Steady red: An

the disk enclosure enclosure is working alarm is generated
correctly. in the disk
enclosure.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
5 Power indicator of Steady green: The Off: The disk

the disk enclosure disk enclosure is enclosure is
powered on. powered off.
Figure 15-9 Disk enclosure rear-panel indicators

12 3 4
8A 8A
1 Alarm indicator of the expansion module 2 Power indicator of the expansion module
3 Mini SAS HD expansion port indicator 4 Running/Alarm indicator of the power module
Table 15-8 lists the states and their meanings of the disk enclosure rear-panel indicators
Table 15-8 Disk enclosure rear-panel indicator states and their meanings
Expansion 1 Alarm indicator of Off: The expansion Steady red: An

module the expansion module is working alarm is generated
module correctly. on the expansion
module.
2 Power indicator of Steady green: The Off: The

the expansion expansion module is expansion module
module powered on. is powered off.
3 Mini SAS HD l Steady green: l Steady red:

expansion port The link to the The port is
indicator expansion port is faulty.
normal and the l Off: The link
data transfer rate to the
is 4 x 6 Gbit/s or expansion port
4 x 3 Gbit/s. is down.
l Steady blue: The
link to the
expansion port is
normal and the
data transfer rate
is 4 x 12 Gbit/s.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Power module 4 Running/Alarm l Steady green: l Steady red:

indicator of the The power The power
power module supply is correct. supply is
l Blinking green: faulty.
The power input l Off: No
is normal but the external power
disk enclosure is input is found.
powered off.
Procedure
l Check onsite front-panel and rear-panel indicators of a disk enclosure according to
Figure 15-8 and Figure 15-9. Predetermine whether all component modules on the disk
enclosure are working properly.
----End
Exception Handling
In the event that a module of the storage system is abnormal, refer to the OceanStor 5300
V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Product
Description to learn about detailed indicator meanings. Then, troubleshoot faults based on the
detailed fault information you have obtained.
15.5 Checking Disk Enclosure Indicators (4U Disk

Enclosure)
Reference Standard

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

1 2 3
0 1 2 3
20 21 22 23
4
5
1 Running indicator of the disk module 2 Location/Alarm indicator of the disk module
3 Location indicator of the disk enclosure 4 Alarm indicator of the disk enclosure
5 Power indicator of the disk enclosure
Disk module 1 Running indicator l Steady green: Off: The disk

of the disk module The disk module module is
is working powered off or
correctly. powered on
l Blinking green: incorrectly.
Data is being
read and written
on the disk
module.
2 Alarm/Location l Blinking red: Steady red: The

indicator of the The disk module disk module is
disk module is being located. faulty.
l Off: The disk
module is
working
correctly or hot
swappable.
System 3 Location indicator Blinking blue: The Off: The disk

enclosure of the disk disk enclosure is enclosure is not
enclosure being located. detected.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4 Alarm indicator of Off: The disk Steady red: An

the disk enclosure enclosure is alarm is
working correctly. generated in the
disk enclosure.
5 Power indicator of Steady green: The Off: The disk

the disk enclosure disk enclosure is enclosure is
powered on. powered off.

1
8A 8A
54 3 2
1 Running/Alarm indicator of the fan module 2 Running/Alarm indicator of the power module
3 Mini SAS HD expansion port indicator 4 Power indicator of the expansion module
5 Alarm indicator of the expansion module

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Fan module 1 Running/Alarm Steady green: The l Steady red:

indicator of the fan fan module is The fan
module working correctly. module is
faulty.
l Off: The fan
module is
powered off.
Power module 2 Running/Alarm l Steady green: l Steady red:

indicator of the The power The power
power module supply is supply is
correct. faulty.
l Blinking green: l Off: No
The power input external
is normal but the power input is
disk enclosure is found.
powered off.
Expansion 3 Mini SAS HD l Steady green: l Steady red:

module expansion port The link to the The port is
indicator expansion port faulty.
is normal and l Off: The link
the data transfer to the
rate is 4 x 6 expansion
Gbit/s or 4 x 3 port is down.
Gbit/s.
l Steady blue: The
link to the
expansion port
is normal and
the data transfer
rate is 4 x 12
Gbit/s.
4 Power indicator of Steady green: The Off: The

the expansion expansion module expansion
module is powered on. module is
powered off.
5 Alarm indicator of Off: The expansion Steady red: An

the expansion module is working alarm is
module correctly. generated on the
expansion
module.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
disk enclosure are working properly.
----End
Exception Handling
V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Hardware
15.6 Checking Disk Enclosure Indicators (High-density

Disk Enclosure)
Reference Standard

1 2
6 3
5 4
1 High-density disk enclosure Location indicator 2 High-density disk enclosure over temperature Alarm
indicator
3 High-density disk enclosure internal module 4 High-density disk enclosure rear module Alarm
Alarm indicator indicator
5 High-density disk enclosure Power indicator 6 High-density disk enclosure Alarm indicator

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
System 1 High-density disk Blinking blue: The Off: The high-

enclosure enclosure Location high-density disk density disk
indicator enclosure has been enclosure is not
located. located.
2 High-density disk Off: The Steady red: The

enclosure temperature of the temperature of
overtemperature high-density disk the high-density
Alarm indicator enclosure is within disk enclosure is
the normal range. too high.
3 High-density disk Off: Internal disk l Steady red:

enclosure internal modules are Internal disk
module Alarm running correctly. modules of
indicator the high-
density disk
enclosure are
faulty.
l Blinking red:
Internal disk
modules of
the high-
density disk
enclosure fail.
4 High-density disk Off: Rear FRUs are Steady red: The

enclosure rear running correctly. number of rear
module Alarm field replaceable
indicator units (FRUs) is
fewer than half of
that in standard
configuration or
rear FRUs are
faulty.
NOTE
Modules on the
rear of the high-
density disk
enclosure include
power modules,
fan modules, and
expansion
modules.
5 High-density disk Steady green: The Off: The high-

enclosure Power high-density disk density disk
indicator enclosure is enclosure is not
powered on. powered on.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
6 High-density disk Off: The high- Steady red: A

enclosure Alarm density disk high-density disk
indicator enclosure is running enclosure alarm
correctly. was generated.

1
P0 P1 P2 P3
F0 F1
B A
0 PRI 1 0 EXP 1 0 PRI 1 0 EXP 1

ID ID
54 3 2
1 Power module Running indicator 2 Indicator of a mini SAS HD expansion port
3 Fan module Running/Alarm indicator 4 Expansion module Alarm indicator
5 Expansion module Power indicator
Power module 1 Power module Steady green: The Off: The power
Running indicator power module is module is not
running correctly. power on,
undervoltage, or
overvoltage.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Expansion 2 Indicator of a mini l Steady blue: The l Steady red:

module SAS HD expansion link is up and The expansion
port the rate is 4 x 6 port is faulty.
Gbit/s. l Off: The link
l Steady green: is down.
The link is up
and the rate is 4
x 3 Gbit/s.
Fan module 3 Fan module l Steady green: Steady red: The

Running/Alarm The fan module fan module is
indicator is running faulty.
correctly.
l Off: The fan
module is not
powered on.
Expansion 4 Expansion module Off: The expansion Steady red: The

module Alarm indicator module is not expansion
powered or is module is faulty.
running correctly.
5 Expansion module Steady green: The Off: The

Power indicator expansion module expansion
is running correctly. module is not
powered on.
Procedure
disk enclosure are working properly.
----End
Exception Handling
V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Hardware

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 16 Checking the Running Status of the Storage Device
16 Checking the Running Status of the

Storage Device
About This Chapter
Check the physical status of the storage device by examining its indicators and check the
functional status of the device on the DeviceManager. This allows you to sense device faults
in a timely manner.
16.1 Checking Controller Enclosures or Disk Enclosures
You can learn about the health and running status of the controller enclosure or a disk
enclosure by checking its status information on the DeviceManager.
16.2 Checking Controllers
Controllers of the storage device are responsible for running storage applications,
implementing storage mechanisms (StoragePool, LUN mapping, and striping), and managing
alarms. You can learn about the health and running status of a controller by checking its status
information on the DeviceManager.
16.3 Checking Power Modules
Power modules provide power for controller enclosures and disk enclosures, ensuring reliable
running of storage systems. You can learn about the health and running status of a power
module by checking its status information on the DeviceManager.
16.4 Checking Controller Enclosure BBUs
Controller enclosure backup battery units (BBUs) provide power failure protection for
controller enclosures, allowing data to be stored in the event of a power failure. You can learn
about the health and running status of a BBU by checking its status information on the
DeviceManager.
16.5 Checking Fan Modules
Fan modules in the controller enclosure or a disk enclosure provide a cyclic aeration system to
ensure the reliable running of the storage device. You can learn about the health and running
status of a fan module by checking its status information on the DeviceManager.
16.6 Checking Hard Disks
Hard disks are used to store data as a basic component of the storage device. You can learn
about the health and running status of a hard disk by checking its status information on the
DeviceManager.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
16.7 Checking Host Ports

Host ports enable service communication between the storage device and application servers.
You can learn about the health and running status of a host port by checking its status
16.8 Checking Interface Modules
Interface modules are used to house host ports and expansion ports. You can learn about the
health and running status of an interface module by checking its status information.
16.9 Checking Remote Devices
You can learn about the health and running status of a remote device connecting to the storage
device by using the DeviceManager.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
16.1 Checking Controller Enclosures or Disk Enclosures

You can learn about the health and running status of the controller enclosure or a disk
enclosure by checking its status information on the DeviceManager.

A fault on the controller enclosure or disk enclosure may impair read/write performance,
deteriorate reliability, disrupt services, and cause data loss on the enclosure.
Reference Standard
If the controller enclosure and disk enclosures are working properly, the following items are
true on the DeviceManager:
l All of the enclosures are in the Normal health status and Online running status.
l No enclosure alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 2 On the main window, click Device View to access the device view.
Step 3 Click the desired enclosure in the view.
The detailed information about the enclosure is displayed.
Step 4 View the enclosure information in the group box that is displayed.
Table 16-1 describes associated status parameters.
Table 16-1 Enclosure status parameters and their meanings
Parameter Description
Health Status Health status of an enclosure. The value can be:

l Normal: The functionality and operating performance of the
enclosure are normal.
l Fault: The enclosure is working improperly.
Running Status Running status of an enclosure. The value can be Online or Offline.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Exception Handling
If an enclosure alarm appears on the Current Alarms tab page, select the alarm and diagnose
the problem according to its details and repair suggestions.
16.2 Checking Controllers

Controllers of the storage device are responsible for running storage applications,
implementing storage mechanisms (StoragePool, LUN mapping, and striping), and managing
alarms. You can learn about the health and running status of a controller by checking its status

A fault on a controller may impair read/write performance, deteriorate reliability, disrupt
services, and cause data loss on the controller module.
Reference Standard
If controllers are working properly, the following items are true on the DeviceManager:
l All of the controllers are in the Normal health status and Online running status.
l No controller alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 3 Click the desired controller module in the view.
The detailed information about the controller module is displayed.
Step 4 View the controller module information in the group box that is displayed.
Table 16-2 Controller status parameters and their meanings
Health Status Health status of a controller module. The value can be:
l Normal: The functionality and operating performance of the controller
are normal.
l Fault: The controller is working improperly.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Running Running status of a controller module. The value can be Online or Offline.
Status
----End
Exception Handling
If a controller alarm appears on the Current Alarms tab page, select the alarm and diagnose
16.3 Checking Power Modules

Power modules provide power for controller enclosures and disk enclosures, ensuring reliable
running of storage systems. You can learn about the health and running status of a power
module by checking its status information on the DeviceManager.

l If a power module is faulty, data reliability deteriorates.
l If all of the power modules are faulty, service are interrupted and the storage device is
powered off.
Reference Standard
If power modules are working properly, the following items are true on the DeviceManager:
l All of the power modules are in the Normal health status and Online running status.
l No power module alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 3 Click in the front view to switch to the rear review of the storage device.
Step 4 Click the desired power module in the view.

The detailed information about the power module is displayed.
Step 5 View the power module information in the group box that is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 16-3 Power module status parameters and their meanings
Health Status Health status of a power module. The value can be:
l Normal: The functionality and operating performance of the power
module are normal.
l Fault: The power module is working improperly.
l No input: The power module has been installed but does not supply
power.
Running Running status of a power module. The value can be Online or Offline.
Status
----End
Exception Handling
If a power module alarm appears on the Current Alarms tab page, select the alarm and
diagnose the problem according to its details and repair suggestions.
16.4 Checking Controller Enclosure BBUs

Controller enclosure backup battery units (BBUs) provide power failure protection for
controller enclosures, allowing data to be stored in the event of a power failure. You can learn
about the health and running status of a BBU by checking its status information on the
DeviceManager.

Controller enclosure BBUs supply emergency power to the storage device when all of its
power modules become faulty or its external power supplies are disconnected. If the BBUs
also become faulty, cache data cannot be saved to disks upon power failure, resulting in data
loss.
Reference Standard
If controller enclosure BBUs are working properly, the following items are true on the
DeviceManager:
l All of the BBUs are in the Normal health status and Online running status.
l No BBU alarm appears on the Current Alarms tab page.
Procedure

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 3 Click the desired BBU in the view. The detailed information about the BBU is displayed.
Step 4 View the BBU information in the group box that is displayed.
Table 16-4 BBU status parameters and their meanings
Health Status Health status of a BBU. The value can be:

l Normal: The functionality and operating performance of the BBU are
normal.
l Fault: The BBU is working improperly.
l Insufficient power: The power level of the BBU is low though its
operating performance is normal.
Running Status Running status of a BBU. The value can be Online, Charging, or
Discharging.
----End
Exception Handling
If a BBU alarm appears on the Current Alarms tab page, select the alarm and diagnose the
problem according to its details and repair suggestions.
16.5 Checking Fan Modules

Fan modules in the controller enclosure or a disk enclosure provide a cyclic aeration system to
ensure the reliable running of the storage device. You can learn about the health and running
status of a fan module by checking its status information on the DeviceManager.

When fan modules become faulty, the ambient temperature of the controller enclosure or a
disk enclosure rises, hampering the proper running of the storage device.
Reference Standard
If fan modules are working properly, the following items are true on the DeviceManager:
l All of the fan modules are in the Normal health status and Running running status.
l No fan module alarm appears on the Current Alarms tab page.
Precaution
None

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 4 Click the desired fan module in the view. The detailed information about the fan module is
displayed.
Step 5 View the fan module information in the group box that is displayed.
Table 16-5 Fan module status parameters and their meanings

Health Status Health status of a fan module. The value can be:
l Normal: The functionality and operating performance of the fan
module are normal.
l Fault: The fan module is working improperly.
Running Running status of a fan module. The value can be Running or Not
Status running.
----End
Exception Handling
If a fan module alarm appears on the Current Alarms tab page, select the alarm and diagnose
16.6 Checking Hard Disks

Hard disks are used to store data as a basic component of the storage device. You can learn
about the health and running status of a hard disk by checking its status information on the
DeviceManager.

Faulty hard disks may impair read/write performance and cause data loss on the storage
device.
Reference Standard
If hard disks are working properly, the following items are true on the DeviceManager:
l All of the disks are in the Normal health status and Online running status.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l No disk alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 3 Click the desired disk in the view. The detailed information about the hard disk is displayed.
Step 4 View the disk information in the group box that is displayed.
Table 16-6 Hard disk status parameters and their meanings
Health Status Health status of a hard disk. The value can be:
l Normal: The functionality and operating performance of the hard disk
are normal.
l Fault: The hard disk is working improperly.
l Failing: The hard disk is about to fail.
Running Running status of a hard disk. The value can be Online or Offline.
Status
----End
Exception Handling
If a disk alarm appears on the Current Alarms tab page, select the alarm and diagnose the
16.7 Checking Host Ports

Host ports enable service communication between the storage device and application servers.
You can learn about the health and running status of a host port by checking its status

Faulty host ports may disable service communication between the storage device and
application servers.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Reference Standard
If front-end host ports are working properly, the following items are true on the
DeviceManager:
l All of the host ports are in the Normal health status and Link Up running status.
l No host port alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 4 Click the desired host port in the view. The detailed information about the host port is
displayed.
Step 5 View the host port information in the group box that is displayed.
Table 16-7 Host port status parameters and their meanings

Health Status Health status of a host port. The value can be:
l Normal: The functionality and operating performance of the host port
are normal.
l Fault: The host port is working improperly.
Running Running status of a host port. The value can be Link Up or Link Down.
Status
----End
Exception Handling
If a host port alarm appears on the Current Alarms tab page, select the alarm and diagnose
16.8 Checking Interface Modules

Interface modules are used to house host ports and expansion ports. You can learn about the
health and running status of an interface module by checking its status information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Faulty interface modules may disable the communication between the storage device and
application servers, controller enclosure and disk enclosures, or storage device and storage
devices.
Reference Standard
If interface modules are working properly, the following items are true on the
DeviceManager:
l All of the interface modules are in the Normal health status and Running running status.
l No interface module alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 4 Click the desired interface module in the view. The detailed information about the interface
module is displayed.
Step 5 View the interface module information in the group box that is displayed.
Table 16-8 Interface module status parameters and their meanings

Parameter Definition
Health Status Health status of an interface module. The value can be:
l Normal: The functionality and operating performance of the interface
module are normal.
l Fault: The interface module is working improperly.
Running Running status of an interface module. The value can be Running or

Status Powered off.
----End
Exception Handling
If an interface module alarm appears on the Current Alarms tab page, select the alarm and

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
16.9 Checking Remote Devices

You can learn about the health and running status of a remote device connecting to the storage
device by using the DeviceManager.

Faulty remote devices may cause data backup interruption or data loss.
Reference Standard
If remote devices are working properly, their Health Status is Normal and Running Status
is Link Up on the DeviceManager.
Precaution
None
Procedure
Step 2 In the function pane, click Remote Device.

The Remote Device page is displayed.
Step 3 On the Remote Device page, view the detailed information about the desired remote device.
Table 16-9 Remote device status parameters and their meanings
Health Status Health status of a remote device. The value can be:
l Normal: The remote device is working properly.
l Fault: The remote device is working improperly.
Running Running status of a remote device. The value can be Link Up or Link
Status Down.
----End
Exception Handling
For a remote device, if its Health Status is Fault or Running Status is Link Down, contact
our technical support engineers for troubleshooting.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 17 Managing Alarms
17 Managing Alarms
About This Chapter
This topic guides you through the process of viewing and configuring current alarms,
historical alarms, and alarm settings.
17.1 Checking Alarms

The alarm list on the DeviceManager contains information about existing alarms on the
storage device. You can easily clear a listed alarm by referring to the detailed description and
troubleshooting suggestions on the alarm.
17.2 Checking Events
The event list on the DeviceManager contains information about Info alarms and the others
that have been cleared from the storage device. You can learn about the operating and
historical status of the storage device by referring to the list.
17.3 Email Notification Management
The DeviceManager allows alarm information to be sent to specific email addresses, helping
engineers troubleshoot faults.
17.4 SM Notification Management
The DeviceManager allows alarm short messages to be sent to specific mobile phones,
allowing easy device monitoring.
17.5 Configuring the System Status Notification Function
This operation enables you to configure a sending period, during which emails and short
messages will be sent to a remote maintenance center to remotely monitor system status.
17.6 Enabling the Syslog Notification Function
This operation enables you to configure the receiving of syslog notifications for preset
severities of alarms from specific IP address.
17.7 Setting the Alarm Buzzer
After the sound alarm function is enabled, the client produces alarming sound when detecting
the corresponding severities of faults.
17.8 Modifying Alarm Dump Settings
After you enable the alarm dump function, alarm messages will be automatically dumped to a
specific application server or maintenance terminal when they accumulate to an amount that
exceeds a self-definable threshold.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
17.9 Managing Trap IP Addresses

Trap is a Simple Network Management Protocol (SNMP) message type used to indicate the
occurrence of an event. These types of messages are sent to a recipient using User Datagram
Protocol (UDP) and are not reliable. Specify trap IP addresses if SNMP is used to report
alarm messages. By setting trap IP addresses, The alarm messages of storage devices can be
sent to a specific application server or maintenance terminal.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
17.1 Checking Alarms

The alarm list on the DeviceManager contains information about existing alarms on the
storage device. You can easily clear a listed alarm by referring to the detailed description and
troubleshooting suggestions on the alarm.
Reference Standard
If the storage device is working properly, there is no alarm appears on the Current Alarms
tab page of the Alarms and Events page.
Precaution
None
Procedure
Step 1 On the navigation bar of the DeviceManager, click . In the function pane, click
Alarms and Events.
The Alarms and Events page is displayed.
Step 2 On the Alarms and Events page, click the Current Alarms tab.
Step 3 View existing alarms of the storage device.

Table 17-1 explains associated alarm parameters.
Table 17-1 Alarm parameters and their meanings

Alarm Level An alarm severity. Each severity is identified by an icon:
l indicates Critical.
l indicates Major.
l indicates Warning.
ID A hexadecimal number for identifying an alarm.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Occurred On Occurrence time of an alarm. The time format is YYYY-MM-DD

hh:mm:ss UTC+hh:mm, where:
l YYYY: indicates a year.
l MM: indicates a month.
l DD: indicates a day.
l hh: indicates an hour.
l mm: indicates a minute.
l ss: indicates a second.
l UTC+hh:mm: indicates a deviation from the Universal Time
Coordinated (UTC).
Details Detailed description of an alarm. It determines the module where the alarm
occurred.
Suggestion Repair suggestions on an alarm and the information about how to obtain
help.
NOTE
You can set filter conditions on the Current Alarms tab page to view specific severities of alarms. Also,
you can save the filtered alarms to a local computer.
----End
Exception Handling
If an alarm appears on the Current Alarms tab page, select the alarm and diagnose the
17.2 Checking Events

The event list on the DeviceManager contains information about Info alarms and the others
that have been cleared from the storage device. You can learn about the operating and
historical status of the storage device by referring to the list.
Reference Standard
None
Precaution
None

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 On the navigation bar of the DeviceManager, click . In the function pane, click
Alarms and Events. The Alarms and Events page is displayed.
Step 2 On the Alarms and Events page, click the All Events tab.
Step 3 View existing events of the storage device.

Table 17-2 explains associated event parameters.
Table 17-2 Event parameters and their meanings
Alarm Level An event severity. Each severity is identified by an icon:
l indicates Critical.
l indicates Major.
l indicates Warning.
l indicates Info.
ID A hexadecimal number for identifying an event.
Occurred On Occurrence time of an event. The time format is YYYY-MM-DD

hh:mm:ss UTC+hh:mm, where:
l UTC+hh:mm: indicates a deviation from the Universal Time
Coordinated (UTC).
Recovered Clearance time of an event. The time format is YYYY-MM-DD hh:mm:ss

On UTC+hh:mm, where:
l UTC+hh:mm: indicates a deviation from the UTC.
Details Detailed description of an event. It determines the module where the event
occurred.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Suggestion Repair suggestions on an event and the information about how to obtain
help.
NOTE
You can set filter conditions on the All Events tab page to view specific severities of events. Also, you
can save filtered events to a local computer.
----End
Exception Handling
None
17.3 Email Notification Management

The DeviceManager allows alarm information to be sent to specific email addresses, helping
engineers troubleshoot faults.
17.3.1 Enabling the Email Notification Function

This operation enables you to configure the sending of alarm notifications for preset severities
of alarms to specific personnel via email.
Prerequisites
l A Simple Mail Transfer Protocol (SMTP) server is available. Otherwise, specified email
addresses will not be able to receive any alarm messages.
l You have logged in to the DeviceManager as an administrator that has the permission.
The following administrators have the permission:
Super administrator
Administrator
Procedure
Step 1 Go to the alarm configuration page.

2. In the function pane on the left, click More > Alarm Settings in the Viewing and
Settings area.
The alarm configuration page is displayed.
Step 2 Configure an email address for receiving alarm messages.

1. In the navigation tree, choose Email notification.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Select Enable.
3. Set parameters for email notification. Table 17-3 describes the parameters.
Table 17-3 Email Notification Parameters

Sender Email Email address of a sender. [Example]

zhangsan@163.com
SMTP Server IP address or domain name [Note]

of the Simple Mail Configure the SMTP
Transfer Protocol (SMTP) server in standard mode.
server. An SMTP server is
an SMTP-compliant email [Example]
sending server. By using 192.168.1.100
the SMTP server, you can
send emails containing
alarm messages to specific
email addresses.
SMTP Port Indicates the port setting [Note]

of SMTP. The default The range of the smtp port
value is 25. is 1 to 65535.
[Example]
3

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Encryption mode The encryption mode [Example]

during network STARTTLS
communication between
system and email server.
Not encrypted: the data
transfer is not
encrypted.
NOTE
There are security risks
if you select Not
encrypted. You are
advised to select other
encryption mode to
improve data transfer
security.
SSL/TLS: SSL and
TLS are two different
security protocols used
to ensure the security
and data integrity
during network
communication. If you
select SSL/TLS, the
system automatically
selects one of them for
encryption based on the
email server type.
STARTTLS: Secure
Socket Layer (SSL) is
a secure protocol that
encrypts the segments
of network connections
above the transfer layer
to provide secure and
complete data for
network
communications.
Enabling SSL helps
improve data transfer
security.
SMTP Server Indicates whether the [Note]

Authentication SMTP server needs to Select the option button if
authenticate senders. If the SMTP server requires
SMTP Server authentication; otherwise,
Authentication is not leave the option button
selected, Username and unselected.
Password are unavailable.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Username SMTP account name of [Note]

the sender. When emails The value cannot be blank,
are sent through the SMTP and contains 1 to 63
server, the sender is characters.
prompted to type his/her
SMTP account name and [Example]
password for testuser
authentication.
Password Password of the SMTP [Example]

account. When emails are aJ1p23dySQ
sent through the SMTP
server, the sender is
prompted to type his/her
SMTP account name and
password for
authentication.
4. Add or modify recipient email addresses.

Add recipient email addresses.
i. Click Add.
The Add Recipient Information dialog box is displayed.
ii. Add recipient email addresses and specify the severities of alarms triggering
the alarm notification.
iii. Click OK.
Modify a recipient email address.
i. Select email addresses that you want to modify and click Modify.
The Modify Recipient Information dialog box is displayed.
ii. Modify the recipient email addresses and specify the severities of alarms
triggering the alarm notification.
iii. Click OK.
Step 3 (Optional) Click Test to test whether the email addresses are correctly configured.
l If the configuration is correct, the mail boxes corresponding to the email addresses can
receive the test mail.
l If the configuration is incorrect, the mail boxes cannot receive the test mail. Configure
the email addresses again.
Step 4 Click Save.
The Execution Result dialog box is displayed.
Step 5 Click Close.
----End
17.3.2 Adding Recipient Email Addresses

You can add a recipient email box for alarms by performing operations in this section.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
Super administrator
Administrator
l The email notification function has been enabled.
l An SMTP server is available and has been configured.
Context
Each alarm severity allows a maximum of 64 recipient emails to be configured. The total
number of recipient emails that are allowed by all alarm severities cannot exceed 96.
Procedure

Settings area.
Step 2 Add recipient email addresses and specify the severities of alarms triggering the email
notification.
2. Click Add.
3. Enter recipient email addresses and specify the severities of alarms triggering the email
notification.
NOTE
The alarm severity can be Critical, Major, or Warning.

If you select Major, Critical is selected automatically.
If you select Warning, Critical and Major are selected automatically.
The alarm severity is mandatory.
Step 3 Confirm the adding of the recipient email addresses.

1. Click OK.
2. Click Save.
3. Click Close.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Result
After the recipient email addresses are successfully added, you can view the added email
addresses in the recipient email address area.
17.3.3 Changing Recipient Email Addresses

This operation enables you to edit recipient email addresses and severities of alarms triggering
the email notification.
Prerequisites
Super administrator
Administrator
l Recipient email addresses have been added.
Procedure

Settings area.
Step 2 Change recipient email addresses.
2. In Recipient mobile number, select the recipient email addresses that you want to
change.
3. Click Modify.
4. Change recipient email addresses and severities of alarms triggering email notification.
Step 3 Confirm the modification of the recipient email addresses.
1. Click OK.
2. Click Save.
3. Click Close.
----End
Result
After recipient email addresses are successfully changed, you can view the new email
addresses in the recipient email address area.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
17.3.4 Testing Recipient Email Addresses

This operation enables you to test whether the recipient email addresses can receive emails.
Prerequisites
Super administrator
Administrator
l Recipient email addresses have been added.
Procedure

Settings area.
Step 2 Test whether recipient email addresses are correctly configured.
2. In Recipient email, select the recipient email addresses that you want to test.
3. Click Test.
If the configuration is correct, the recipient email corresponding to the email
addresses can receive the test mail.
If the configuration is incorrect, the mail boxes cannot receive the test mail.
Configure the recipient email addresses again.
----End
17.4 SM Notification Management

The DeviceManager allows alarm short messages to be sent to specific mobile phones,
allowing easy device monitoring.
17.4.1 Enable SM Notification

The following procedure guides you through the configuration for sending alarm notifications
for alarms in a specific level of severity to a specific recipient's mobile phone via text
message.
Prerequisites

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Super administrator
Administrator
l An SMS modem has been installed on the system or maintenance terminal. The COM
port of the SMS modem has been configured for sending short messages.
Context
The short message (SM) notification function is not available to read-only users.
Procedure

2. In the function pane, click More > Alarm Settings in the Viewing and Settings area.
Step 2 Set a mobile phone number for receiving alarm short messages.
1. In the navigation tree, choose SM notification.
2. Select Enable.
3. Set a phone number for the Short Message (SM) service center.
NOTE
The phone number must be in the following format: plus sign+country code+11-bit phone number
of your local SM service center.
4. Add a mobile phone number or change the existing one for receiving alarm short
messages.
Add a mobile phone number.
i. Click Add.
ii. Set a mobile phone number for receiving alarm short messages and select an
alarm severity for it.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
iii. Click OK.

Change the existing mobile phone number.
i. Select the mobile phone number that you want to change and click Modify.
ii. Update the mobile phone number and select an alarm severity for it.
iii. Click OK.
Step 3 (Optional) Click Test to verify the settings of the configured mobile phone number.
Step 4 Click OK.

l If the settings are correct, the mobile phone can receive test short messages.
l If the settings are incorrect, the mobile phone cannot receive any test short messages. In
this condition, reset the mobile phone number.
Step 5 Click Save.

The Execution Result dialog box is displayed
Step 6 Click Close.
----End
17.4.2 Adding Recipient Mobile Phone Numbers

This operation enables you to add recipient mobile phone numbers.
Prerequisites
Super administrator
Administrator
Procedure

Settings area.
Step 2 Add mobile phone numbers.

2. Click Add.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
3. Enter recipient mobile phone numbers and specify the severities of alarms triggering the
short message notification.
4. Click OK.
5. Click Save.
6. Click Close.
----End
Result
After the recipient mobile phone numbers are successfully added, you can view the added
mobile phone numbers in the recipient mobile phone number area.
17.4.3 Changing Recipient Mobile Phone Numbers

This operation enables you to change added recipient mobile phone numbers.
Prerequisites
l The short message notification function has been enabled.
l Recipient mobile phone numbers have been added.
Procedure

Settings area.
Step 2 Change the existing mobile phone number.

2. In Recipient mobile number, select the recipient mobile phone numbers that you want
to change.
3. Click Modify.

4. Change the recipient mobile phone numbers and severities of alarms triggering the short
message notification.
5. Click OK.
6. Click Save.
7. Click Close.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Result
After recipient mobile phone numbers are successfully changed, you can view the new mobile
phone numbers in the recipient mobile phone number area.
17.4.4 Testing Recipient Mobile Phone Numbers

This operation enables you to test added recipient mobile phone numbers.
Prerequisites
l The short message notification function has been enabled.
l Recipient mobile phone numbers have been added.
Context
The test aims to check whether recipient mobile phone numbers are correctly configured.
Procedure

Settings area.
Step 2 Test recipient mobile phone numbers.
2. In Recipient mobile number, select the recipient mobile phone numbers that you want
to test.
3. Click Test.
The Information dialog box is displayed.
4. Carefully read the content in the dialog box and click OK.
If the settings are correct, the mobile phone can receive test short messages.
If the settings are incorrect, the mobile phone cannot receive any test short
messages. In this condition, reset the mobile phone number.
----End
17.5 Configuring the System Status Notification Function

This operation enables you to configure a sending period, during which emails and short
messages will be sent to a remote maintenance center to remotely monitor system status.
Prerequisites
l The email notification and short message notification functions have been correctly
configured.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l The system notification function has been enabled.
Procedure

Settings area.
Step 2 Configure a sending period and customer information.
1. In the navigation tree, choose System notification.
2. In Sending cycle (h), enter a period. The value of the period is an integer ranging from 1
to 168 in hours.
3. In Customer information, enter the company name and contact information of the
customer, helping maintenance engineers search and locate faults.
NOTE
A maximum of 256 characters can be entered in Customer information.
Step 3 Confirm the configuration of the sending period and customer information.
1. Click Save.
2. Click Close.
----End
17.6 Enabling the Syslog Notification Function

This operation enables you to configure the receiving of syslog notifications for preset
severities of alarms from specific IP address.
Prerequisites
You have logged in to the DeviceManager as an administrator that has the permission. The
following administrators have the permission:

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l Super administrator
l Administrator
Context
Alarms, alarm recovery messages and system log information can be received by Syslog
service.
Procedure
Step 1 Go to the syslog notification configuration page.

Settings area.
3. In the navigation tree, choose Syslog Notification.
The syslog notification page is displayed.
Step 2 Configure the severity and IP address for receiving syslog messages.
1. Select Enable.
2. In Severity, select the severity of receiving syslog.
3. In Notification Type, select the type of alarm or event.
4. Add or remove receiver IP addresses.
Add receiver IP addresses.
i. Click Add.
The Add Receiver IP Address dialog box is displayed.
ii. Add receiver IP addresses.
iii. Click OK.
Remove receiver IP addresses.
i. Select receiver IP addresses that you want to remove and click Remove.
Step 3 Click Save.
The Success dialog box is displayed.
Step 4 Click OK.
----End
17.7 Setting the Alarm Buzzer

After the sound alarm function is enabled, the client produces alarming sound when detecting
the corresponding severities of faults.
Context
Based on your requirements, enable or disable the sound alarm function by clicking .

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 On the menu bar, click the list next to .

The Alarm Buzzer Settings dialog box is displayed.
Step 2 Specify the levels of faults triggering the alarming sound.
The Fault Level can be Critical, Major, or Warning.

l If you select Major, Critical is selected automatically.
l If you select Warning, Critical and Major are selected automatically.
Step 3 Confirm the settings of the sound alarm.
1. Click OK.
The Successed dialog box is displayed.
2. Click OK.
----End
17.8 Modifying Alarm Dump Settings

After you enable the alarm dump function, alarm messages will be automatically dumped to a
specific application server or maintenance terminal when they accumulate to an amount that
exceeds a self-definable threshold.
Prerequisites
l The alarm dump function has been enabled.
l The application server or maintenance terminal used to receive the alarm information is
normally in communication with the storage device.
l In an environment with the firewall function, when the FTP server is used to save
alarms, you need to enable port 21.
Context
l If alarm dump is not configured for the storage system
when the number of generated events reaches 45,000, the alarm named The Space
That Stores Event Logs Is To Be Used Up is triggered

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
when the number of generated events reaches 50,000 (upper limit), the earliest
10,000 events are automatically deleted.
l If alarm dump is configured for the storage system
when the number of generated events reaches 45,000, the alarm named The Space
That Stores Event Logs Is To Be Used Up is not triggered.
when the number of generated events reaches 50,000 (upper limit), the earliest
10,000 events are automatically dumped to the specified application server or
maintenance terminal.
NOTE
To ensure that all events generated by the storage system are retained, it is recommended that you
configure alarm dump.
Precaution
The following requirements must be met to implement the dump function:
l The server is connected to the management network port on the primary controller of the
storage system.
l The server and primary controller reside on the same LAN and their IP addresses fall
within the same network segment. Run the show controller general command on the
CLI. If Role of a controller is Master, the controller is the primary controller of the
storage system.
NOTE
If the server is connected to the management network port on the secondary controller of the storage system,
the dump function is unavailable.
Procedure
Step 1 Go to the page for setting alarms.

2. In the Viewing and Settings area, choose More > Alarm Settings.
The page for setting alarms is displayed.
Step 2 Modify parameters for the alarm dump.
1. In the left navigation tree, select the Alarm Dump node.
2. Modify alarm dump parameters. Table 17-4 describes the parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 17-4 Alarm Dump Parameters

Transport The transport protocol of the [Example]

protocol alarm dump, include SFTP and FTP
FTP.
NOTE
To ensure compatibility, the system
still supports File Transfer Protocol
(FTP). It is recommended to use the
Secure File Transfer Protocol
(SFTP) for data transfer security.
Username Name of a user on the server [Value range]

that will be used to store The value must be unique.
performance monitoring data.
It contains 1 to 63 characters.
[Example]
files
Password Password for logging in to a [Value range]

server. It contains 1 to 63 characters.
[Example]
123456

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Server IP IP address of a server. [Value range]

address An IPv4 address has the
following requirements:
n The 32-bit address is evenly
divided into four fields.
Each 8-bit field is expressed
in dotted-decimal.
n Each field of the IP address
cannot be blank and must be
an integer.
n The value of the first field
ranges from 1 to 223
(excluding 127).
n The values of other fields
range from 0 to 255.
n The IP address cannot be a
special address such as the
broadcast address.
An IPv6 address has the
following requirements:
n The 128-bit address is
evenly divided into eight
fields. Each 16-bit field is
expressed in hexadecimal
and separated with colons.
n In each 16-bit field, zeros
before integers can be
removed. However, at least
one digit must be reserved in
each field.
n If the IP address contains a
long string of zeros, you can
represent the neighboring
zeros with double colons (::)
in the colon-separated
hexadecimal field. Each IP
address contains only one
double-colons (::). The
double-colons (::) can also
be used to represent
neighboring zeros of the IP
address.
n The IP address cannot be a
special address such as
network address, loop
address, or multicast
address.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
[Example]
192.168.1.100
4300:20::3340
Save file to Path to a directory for storing [Example]

dumped performance If you set the path to G:\ and create
monitoring data. To enable this a folder named alarm on the FTP
parameter, you must set up a server, type alarm in Save file to.
path and create a folder under it,
and type the name of the folder
in Save file to on the
DeviceManager.
Step 3 Confirm the modification of parameters for the alarm dump.

1. Click Save.
The Results message box is displayed, indicating that the operation succeeded.
2. Click Close.
----End
17.9 Managing Trap IP Addresses

Trap is a Simple Network Management Protocol (SNMP) message type used to indicate the
occurrence of an event. These types of messages are sent to a recipient using User Datagram
Protocol (UDP) and are not reliable. Specify trap IP addresses if SNMP is used to report
alarm messages. By setting trap IP addresses, The alarm messages of storage devices can be
sent to a specific application server or maintenance terminal.
17.9.1 Adding a Service IP Address

After a Trap IP address is added, the alarm information about a storage system will be sent to
the application server or maintenance terminal corresponding to the Trap IP address.
Context
Trap is a type of Simple Network Management Protocol (SNMP) message that indicates the
occurrence of an event. By using the User Datagram Protocol (UDP) protocol, you can send
this type of messages which are partially reliable to recipients.
The DeviceManager provides the trap IP function to send the alarm messages of managed
storage devices to another network management system or to a device at a specific IP address.
If alarm messages are reported in SNMP mode, you must configure Trap IP addresses.
NOTE
To enable the trap IP function, install associated software on application servers. For example, you must
install MIB interface software on the application servers running Windows 2003. Click (Link) , and see
MIB_Interface_File_Usage_Guideto download software.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure

Step 2 Add a service IP address.
1. In the left navigation tree, select the Trap IP Addresses Management node.
2. Click Add.
The Add Server IP Address dialog box is displayed.
3. Set parameters for the service IP address.
Table 17-5 describes the parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 17-5 Service IP address parameters

Service IP Alarm information [Value range]

address about a storage device is When the IP address is an IPv4
reported to the address:
DeviceManager or
storage device on the n The 32-bit IPv4 address is
service IP address. divided into four 8-bit fields.
Each 8-bit field is written in
decimal format, and fields are
separated with periods (.).
n Each field of the IP address must
be an integer.
n From left to right, the value of the
first byte ranges from 1 to 223
(excluding 127).
n The values of the other fields
range from 0 to 255.
n The IP address cannot be set to a
special one, such as a network
address or broadcast address.
When the IP address is an IPv6
address:
n The 128-bit IPv6 address is
divided into eight 16-bit fields.
Each 16-bit field consists of four
colon-separated hexadecimal
numbers.
n The zeros at the beginning of
each field can be omitted for
simplicity but at least one digit is
reserved in each field.
n If an address includes a long
string of zeros, to achieve further
simplicity, you can incorporate
the consecutive zeros into double
colons (::). The double colons (::)
can display only once in one IPv6
address. They can also represent
the consecutive zeros at the
beginning or end of an IPv6
address.
n The IP address cannot be set to a
special one, such as a network
address, loopback address, or
multicast address.
[Example]
192.168.100.11

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4300:21::3000
Port Port information of the [Value range]

service IP address. 1 to 65,535
[Example]
2234
Version Version information [Example]

about the service IP SNMPv3
address. The value can
be SNMPv1,
SNMPv2c, or SNMPv3.
NOTE
To ensure the data
security, you are advised
to use SNMPv3.
Type Type of an alarm sent by [Example]

a storage device to the Parsed
trap server.
Parsed: alarms that
have been resolved.
Original: alarms that
have not been
resolved.
All: all alarms
including the Parsed
and Original alarms.
4. Click OK.
Step 3 Confirm the creation of the service IP address.
1. Click Save.
succeeded.
2. Click Close.
----End
17.9.2 Changing a Service IP Address

If you want to send the alarm information to another application server or maintenance
terminal, change the original Trap IP address to the IP address of the new application server
or maintenance terminal.
Context
l Changing service IP addresses is unavailable to read-only users.
l If the service IP address is not on the management network segment, configure routes to
interconnect storage devices with the servers pertaining to the service IP addresses.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTICE
Before changing service IP addresses, ensure that no alarm message is being reported to
network management systems or storage devices pertaining to those IP addresses.
Otherwise, alarm messages being reported at the time of the change will be lost.
Procedure

Step 2 Change a service IP address.
2. In the service IP address list, select the service IP address that you want to change and
click Modify.
The Modify server IP address dialog box is displayed.
3. Change the server IP address.
Step 3 Confirm the change of the service IP address.
1. Click OK.
2. Click Save.
succeeded.
3. Click Close.
----End
17.9.3 Testing Service IP Addresses

This operation enables you to test service IP addresses.
Prerequisites
A service IP address has been created.
Procedure


OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Step 2 Test service IP addresses.
2. In the service IP address list, select the service IP address that you want to test and click
Test.
The Execution Result dialog box is displayed
3. Click Close.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 18 Monitoring a Storage System
18 Monitoring a Storage System
About This Chapter
A storage system provides performance monitoring and system information and power
consumption viewing functions, allowing you to monitor the working status of the storage
system in real time.
18.1 Viewing System Information

Users can learn about the overall conditions of a storage system from the system information
view.
18.2 Viewing Power Consumption
Power consumption indicates how much power a storage system consumes per unit time. You
can view the total power consumption of a storage device or its power consumption on a
specified date.
18.3 Configuring Performance Monitoring Statistics
Configure performance monitoring settings to control the sampling interval, whether or not to
retain monitoring data and monitoring status on the storage device.
18.4 Modifying the Settings for Dumping Performance Monitoring Statistics
After enabling the dumping for performance monitoring statistics, you can dump performance
monitoring statistics to a specific server using File Transfer Protocol (FTP) or Secure File
Transfer Protocol (SFTP).
18.5 Viewing Performance Monitoring Data
After enabling the performance monitoring function, you can view the operating status and
basic information about a storage device component.
18.6 Monitoring a Storage Pool
A storage system provides the performance forecasting and capacity monitoring functions for
a storage pool. It can provide a recommended capacity ratio for a storage pool based on the
disk configuration and RAID policy.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
18.1 Viewing System Information

Users can learn about the overall conditions of a storage system from the system information
view.
Procedure
Step 1 On the right navigation bar, click .
Step 2 In the Basic Information area, check the system's basic information.
Table 18-1 Basic information

Device status Status of the storage device. [Example]

Normal
Device model Model of the storage device. [Example]

-
Total Capacity Total capacity of the storage space [Example]

provided by the storage system (The 100.000 TB
capacity is calculated based on the
sector size of 512 bytes. If the
sector size employed by a disk is
not 512 bytes, the value may be
different from the actual capacity).
Device location Geographical location of the storage [Example]

device. Chengdu

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Version Version of the storage device. [Example]

V300R001
SN Serial No. of the storage device. [Example]

65789AB65C7136CC98B5
WWN World Wide Name of the storage [Example]

device. 21004846fb8ca15c
Step 3 In the Alarms area, check the system's alarm information.

Table 18-2 Alarm information

Level Severity of the impact caused by an [Example]

alarm on a system. Critical
Description Description of an alarm. [Example]

-
Occurred on Time when an alarm occurred. [Example]

2012-07-23 11:02:43 UTC
+08:00
Step 4 In the System Capacity Trend area, view the system capacity trend of the storage system.
Table 18-3 System capacity trend information

Total Capacity All hard disk capacity of the storage [Example]

system. It contains the total used 100.000 TB
capacity, available capacity and
system loss capacity.
Used Capacity Total used capacity of all storage [Example]

pools in the storage system. 100.000 GB
Available The remaining capacity which is [Example]

Capacity available in the storage system. It 100.000 GB
contains the total capacity of the
free hard disks which do not join
the disk domains, available capacity
of the disk domains and storage
pools.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 5 In the Performance area, view the bandwidth and total IOPS of the storage system.
Table 18-4 Performance information

Block The average amount of I/O data per [Example]

bandwidth second in the storage system. 10.000 MB/s
Total IOPS The number of I/O requests per [Example]

second in the storage system. 10.000 IO/s
----End
18.2 Viewing Power Consumption

Power consumption indicates how much power a storage system consumes per unit time. You
can view the total power consumption of a storage device or its power consumption on a
specified date.
Procedure
Step 1 Go to the page for viewing Power Consumption.

2. In the left function pane, click Power Consumption.
The page for viewing Power Consumption is displayed.
Step 2 From the Year, Month, and Day lists next to Date, set a date.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
You can view system power consumption during a day, a month, or a year.
Step 3 Click View. The system power consumption is displayed in the lower graph.
You can also view power consumption at different points of time or during different time
ranges.
----End
18.3 Configuring Performance Monitoring Statistics

Configure performance monitoring settings to control the sampling interval, whether or not to
retain monitoring data and monitoring status on the storage device.
Context
l You can monitor the performance of the storage device only when the performance
monitoring status is Enable.
l In scenarios where controller software is upgraded, parts are replaced, or operations are
performed on hot patches or heterogeneous support packets, the performance statistics
switch is automatically disabled. After the operation, the status of the performance
statistics switch will automatically restore to the pre-operation state.
Procedure
Step 1 Go to the performance monitoring configuration page.

2. In the left function pane, click Performance Monitoring.
The performance monitoring page is displayed.
3. In the upper function pane, click Set Parameters.
The Set Performance Monitoring Parameters dialog box is displayed.
You can also go to the Set Performance Monitoring Parameters dialog box as follows:
a. On the right navigation bar, click .

b. In the left function pane, click Performance Monitoring Settings in the Viewing
and Settings area.
c. In the left navigation tree, choose Parameter Settings.
The performance monitoring configuration page is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 2 Modify performance monitoring settings.

1. Click Disable to disable performance monitoring.
2. Click Close.
3. In Sampling interval of real-time statistics collection (s), type a real-time performance
data sampling interval.
4. In Sampling interval of historical statistics collection (s), type a historical performance
monitoring period.
5. Determine whether or not to save performance monitoring data on the storage device.
If you want to store monitoring data on the storage device, select the Save monitoring
date on the device check box.
6. Click Enable.
7. Click Close and you have finished modifying performance monitoring settings.
----End
18.4 Modifying the Settings for Dumping Performance

Monitoring Statistics
After enabling the dumping for performance monitoring statistics, you can dump performance
monitoring statistics to a specific server using File Transfer Protocol (FTP) or Secure File
Transfer Protocol (SFTP).
Prerequisites
l The login account, password, and IP address of the FTP server for storing dumped
performance monitoring statistics have been obtained.
l The login account, password, and IP address of the SFTP server for storing dumped
performance monitoring statistics have been obtained.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
l The storage device communicates with the FTP or SFTP server properly.
Precaution
The following requirements must be met to dump performance monitoring data to a third-
party application server using FTP or SFTP:
l The third-party application server is connected to the management network port on the
primary controller of the storage system.
l The third-party application server and primary controller reside on the same LAN and
their IP addresses fall within the same network segment. Run the show controller
general command on the CLI. If Role of a controller is Master, the controller is the
primary controller of the storage system.
NOTE
If the third-party application server is connected to the management network port on the secondary controller
of the storage system, the dump function is unavailable.
Procedure
Step 1 Go to the performance monitoring configuration page.

2. In the function pane, click Performance Monitoring Settings in the Viewing and
Settings area.
The performance monitoring configuration page is displayed.
Step 2 Modify the settings for dumping performance monitoring statistics.

1. In the navigation tree, choose Dump Configuration.
2. Select Enable.
3. In Transport protocol, select SFTP or FTP.
NOTE
To ensure compatibility, the system still supports File Transfer Protocol (FTP). It is recommended
to use the Secure File Transfer Protocol (SFTP) for data transfer security.
4. In Username, type a username.
5. In Password, type a password for the username.
6. In Server IP address, type the IP address of the server.
7. In Save file to, type a path for storing the performance monitoring statistics to be
dumped.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
A saving path is set on the user FTP software. Users need to create a folder in the saving path.
Enter the folder name in Save file to. If you need to save the file to the root directory, Enter / in
Save file to.
Example: If the save path configured on the FTP is G:\ and the folder name is alarm, enter alarm
in Save file to on the DeviceManager interface.
8. Click Save.
9. Click Close and you have finished modifying the settings for dumping performance
monitoring statistics.
----End
18.5 Viewing Performance Monitoring Data

After enabling the performance monitoring function, you can view the operating status and
basic information about a storage device component.
Prerequisites
The performance monitoring function has been enabled.
Procedure
Step 1 Go to the real-time performance monitoring page.
1. On the navigation bar of the NMS, click .

2. In the function pane, click Real-Time Performance Monitoring.
The real-time performance monitoring page is displayed.
Step 2 Select the object and statistical item that you want to monitor.
NOTE
Click set parameters on Real-Time Performance Monitoring page, enables the performance monitoring
function.
l Single graph
a. Click Single-graph.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
b. Select the object type of the storage device that you want to monitor in Object
Type.
NOTE
If the Object Type is Remote Replication, the system only provides the performance statistics of
remote replication in Asynchronous mode.
c. Select the object of the storage device you want to monitor.
d. Select the data type of the statistics in Data Type.
e. Select the statistics items you want to monitor in Statistical Items.
The performance line graph is displayed in the Real-Time Performance
Monitoring dialog box.
NOTE
n For details about the parameter explanations of the related statistics items, please refer to
the appendix section of SystemReporter User Guide.
n When you place the cursor on the performance data sampling point, the statistic and
sampling time are displayed.
l Multiple graph
a. Click Multi-graph.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
b. Select the object type of the storage device that you want to monitor in Object
Type.
NOTE
If the Object Type is Remote Replication, the system only provides the performance statistics of
remote replication in Asynchronous mode.
c. Select the object of the storage device you want to monitor.
d. Select the statistics items you want to monitor in Statistics.
The performance line graph is displayed in the Real-Time Performance
Monitoring dialog box.
NOTE
n For details about the parameter explanations of the related statistics items, please refer
to the appendix section of SystemReporter User Guide.
n Click the icon in the top right corner, and you can view details of performance
monitoring data.
n When you place the cursor on the performance data sampling point, the statistic and
sampling time are displayed in the details page.
n The statistical item Ratio of cache flushes to write requests (%) might be larger than
100%.
The ratio of cache flushes to write requests (%) indicates the ratio of cache flushing
times to write request quantity in a specified period. Cache flushing is a background
thread that periodically writes data to disks. If the write request quantity is smaller than
the background cache flushing times, the ratio is greater than 100%.
Step 3 View performance monitoring data in the performance line graph.
----End
18.6 Monitoring a Storage Pool

A storage system provides the performance forecasting and capacity monitoring functions for
a storage pool. It can provide a recommended capacity ratio for a storage pool based on the
disk configuration and RAID policy.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
18.6.1 Modifying the Advanced Properties of a Storage Pool

This operation enables you to modify the advanced properties of a storage pool.
Procedure
Step 1 Go to the Storage Pool Properties dialog box.

3. Select the storage pool whose properties you want to modify and click Properties.
The Properties of Storage Pool dialog box is displayed.
Step 2 Set advanced properties for the storage pool.
1. In the Properties of Storage Pool dialog box, click the Advanced tab.
Table 18-5 describes the related parameters.
Table 18-5 Storage pool advanced parameters

Capacity The minimum capacity usage that [Value range]

Alarm triggers an alarm for a storage pool. 1 to 95
Threshold When the capacity usage of a storage
(%) [Default Value]
pool exceeds the capacity alarm
threshold, the system generates an alarm 80
asking you to expand the capacity of the
storage pool.
A proper capacity alarm threshold helps
you monitor the capacity usage of a
storage pool.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Data When ratio the data protection capacity [Value range]

Protection of the storage pool to the total capacity of 1 to 100
Capacity the storage pool exceeds the capacity
Alarm alarm threshold, the system generates an [Default value]
Threshold alarm. 100
(%)
2. Click OK.
3. Click Close.
----End
18.6.2 Forecasting Storage Pool Performance

After the performance forecasting function is enabled, the storage system can provide a
recommended capacity ratio for a storage pool based on the disk configuration and RAID
policy to achieve optimal performance.
Prerequisites
l At least a LUN whose relocation policy is Automatic relocation is available.
l The I/O monitoring of the storage pool has been enabled.
l LUNs have been accessed after the I/O monitoring is enabled.
Procedure
Step 1 Go to the Storage Pool Properties dialog box.

3. Select the storage pool whose properties you want to modify and click Properties.
The Properties of Storage Pool dialog box is displayed.
Step 2 Configure the performance forecasting function.
1. In the Properties of Storage Pool dialog box, click the Forecast Analysis tab.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Select Enable to enable the performance forecasting function.

3. From each of the High-performance Tier (SSD), Performance Tier (SAS), and
Capacity Tier (NL-SAS) drop-down lists, select the type of hard disks and RAID
policy.
Step 3 Click Apply.
The Execute Result dialog box is displayed indicating that the operation succeeded.
Step 4 Click Close.
You are returned to the Forecast Analysis tab page.
Step 5 Click Result.
The Execution Result dialog box is displayed.
NOTE
You can view the following information:

l Recommended capacity ratio configuration of each storage tier
l IOPS in the recommended capacity ratio configuration
l Bandwidth in the recommended capacity ratio configuration
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 19 Checking the Running Status of Services
19 Checking the Running Status of

Services
About This Chapter
Check the running status of various services running on the storage device by using the
DeviceManager. This allows you to discover service faults in a timely manner, preventing
data loss caused by service interruptions.
19.1 Checking Disk Domain Status
By checking the status of a disk domain, you can understand its health status, operating status
and used capacity. The operating status of a disk domain directly affects that of a storage pool.
19.2 Checking Storage Pools
A storage pool is a logical disk group consisting of independent physical disks. It provides
higher storage performance and redundancy than a single disk. You can learn about the health
and running status of a storage pool by checking its status information on the DeviceManager.
19.3 Checking LUNs
Logical unit numbers (LUNs) are basic storage resources of the storage device accessible to
application servers. You can learn about the health and running status of a LUN by checking
its status information on the DeviceManager.
19.4 Checking Host Status
You can view host information to understand host status.
19.5 Viewing Mapping Status
You can view mapping information to understand mapping status.
19.6 Checking Remote Replication Tasks
The remote replication function is critical to a disaster recovery system. It can implement real-
time disaster recovery over any distance and can protect application continuity and data
reliability. You can learn about the health and running status of a remote replication task by
checking its status information.
19.7 Checking Consistency Groups
A consistency group centrally manages remote replication tasks so that multiple replication
pairs can be synchronized or split in a batch. You can learn about the health and running status
of a consistency group by checking its status information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
19.8 Checking Clone Tasks

The clone function is mainly used for data backup. It can generate point-in-time complete
physical copies or consistent duplicates for the data on the storage device. You can learn about
the health and running status of a clone task by checking its status information.
19.9 Checking Snapshot Tasks
Snapshots can provide continuous data protection with quick data backup and recovery. You
can learn about the health and running status of a snapshot task by checking its status
19.10 Checking LUN Copy Tasks
The LUN copy function can copy data from a source LUN to a target LUN and can
implement storage tiering and remote backup. You can learn about the health and running
status of a LUN copy task by checking its status information.
19.11 Checking HyperMirror Status
HyperMirror provides mirror copies for LUNs and continuously protects LUNs without
affecting applications running on the host. By checking HyperMirror information, you can
learn about its health status and running status.
19.12 Checking SmartMigration Status
SmartMigration can migrate services from the source LUN to the target LUN without
interrupting services. By checking SmartMigration information, you can learn about its
running status.
19.13 Checking Optimization Feature Status
By checking the status of an optimization feature, you can understand its health status,
operating status, mapping, and associated LUNs. The operating status of an optimization
feature directly affects the performance of a storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
19.1 Checking Disk Domain Status

By checking the status of a disk domain, you can understand its health status, operating status
and used capacity. The operating status of a disk domain directly affects that of a storage pool.
Prerequisites
Log in to DeviceManager as a read-only user.
Procedure
Step 1 Go to the Disk Domain page.
1. In the navigation tree on the right, click .

The Provisioning page is displayed.
2. Click Disk Domain.
Go to the Disk Domain page.
Step 2 Check disk domain status.
1. On the Disk Domain page, check Health Status and Running Status of disk domains
to ensure that all disk domains are working correctly. If an alarm is displayed, handle it
in time based on the alarm information.
For details, click next to the table heading. From the drop-down list, select
indicators you are concerned with.
If the free capacity of a disk domain is insufficient, expand the disk domain within
the licensed capacity limit to ensure that the storage pools and LUNs in the disk
domain provide adequate storage space.
2. If you select a disk domain, the bottom area shows details about its capacity distribution
and contained storage pools and disks.
NOTE
You can also view the task progress of the disk domain you have selected. Click Properties, click
the General tab in the dialog box that is displayed, and view the progress of Precopy and
Reconstruction in the Progress area.
----End
19.2 Checking Storage Pools

A storage pool is a logical disk group consisting of independent physical disks. It provides
higher storage performance and redundancy than a single disk. You can learn about the health
and running status of a storage pool by checking its status information on the DeviceManager.

A faulty or degraded storage pool may impair read/write performance, disrupt services, and
cause data loss on the storage device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Reference Standard
If storage pools are working properly, the following items are true on the DeviceManager:
l All of the storage pools are in the Normal health status and Online running status.
l No storage pool alarm appears on the Current Alarms tab page.
Precaution
None
Procedure

Step 2 In the function pane, click Storage Pool.
Step 3 On the Storage Pool page, view the information about the desired storage pool.
Table 19-1 Storage pool status parameters and their meanings

Health Status Health status of a storage pool. The value can be:
l Normal: The functionality and operating performance of the storage
pool are normal.
l Degrade: The storage pool is working in a poor performance.
l Fault: The storage pool is working improperly.
Running Running status of a storage pool. The value can be Online,

Status Reconstruction, Precopy, Balanced, or Offline.
----End
Exception Handling
If a storage pool alarm appears on the Current Alarms tab page, select the alarm and
19.3 Checking LUNs

Logical unit numbers (LUNs) are basic storage resources of the storage device accessible to
application servers. You can learn about the health and running status of a LUN by checking
its status information on the DeviceManager.

Faulty LUNs may interrupt services and cause data loss on the storage device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Reference Standard
If LUNs are working properly, the following items are true on the DeviceManager:
l All of the LUNs are in the Normal health status and Online running status.
l No LUN alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 2 In the function pane, click LUN.

The LUN page is displayed.
Step 3 On the LUN page, view the information about the desired LUN.
Table 19-2 LUN status parameters and their meanings
Health Status Health status of a LUN. The value can be:

l Normal: The functionality and operating
performance of the LUN are normal.
l Fault: The LUN is working improperly.
Running Status Running status of a LUN. The value can be Online or

Offline.
----End
Exception Handling
If a LUN alarm appears on the Current Alarms tab page, select the alarm and diagnose the
19.4 Checking Host Status

You can view host information to understand host status.

A host fault may interrupt system services and cause data loss.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Reference Standard
If the host status is normal, on the DeviceManager management page:
l The Status of the host is Normal.
l No alarm about the host is displayed on the Current Alarms tab page.
Precaution
None
Procedure
Step 2 In the function pane on the left, click Host.

The Host page is displayed.
Step 3 On the Host tab of the Host page, view detailed information about the host.
----End
Exception Handling
If a new alarm about the host is displayed on the Current Alarms tab page, select the alarm,
and troubleshoot the fault according to the alarm details and repair suggestions.
19.5 Viewing Mapping Status

You can view mapping information to understand mapping status.

A mapping fault may interrupt system services and cause data loss.
Precaution
None
Procedure
Step 2 In the function pane on the left, click Mapping View.

The Mapping View page is displayed.
Step 3 On the Mapping View page, select a mapping you want to view.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 In the details area, view LUN group, host group, and port group information in the mapping.
----End
Exception Handling
If a new alarm about the host is displayed on the Current Alarms tab page, select the alarm,
and troubleshoot the fault according to the alarm details and repair suggestions.
19.6 Checking Remote Replication Tasks

The remote replication function is critical to a disaster recovery system. It can implement real-
time disaster recovery over any distance and can protect application continuity and data
reliability. You can learn about the health and running status of a remote replication task by
checking its status information.

Faulty remote replication tasks may interrupt data backup services and cause data loss.
Prerequisites
A license file is required for enabling the remote replication function.
Reference Standard
If remote replication tasks are running properly, the following items are true on the
DeviceManager:
l All of the remote replication tasks are in the Normal health status and Normal running
status.
l No remote replication alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 2 In the function pane, click Remote Replication.

The Remote Replication page is displayed.
Step 3 On the Remote Replication page, view the information about the desired remote replication
task.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Table 19-3 Remote replication status parameters and their meanings

Pair Health Health status of a remote replication task. The value can be:
Status l Normal: The functionality and operating performance of the remote
replication task are normal.
l Fault: One or more replication pairs for the remote replication task are
abnormal.
Pair Running Running status of a remote replication task. The value can be Normal,
Status Synchronizing, To be recovered, Interrupted, Split, or Invalid.
----End
Exception Handling
If a remote replication alarm appears on the Current Alarms tab page, select the alarm and
19.7 Checking Consistency Groups

A consistency group centrally manages remote replication tasks so that multiple replication
pairs can be synchronized or split in a batch. You can learn about the health and running status
of a consistency group by checking its status information.

l If a consistency group is disabled due to one or more faulty replication pairs, the remote
replication services carried by those pairs are interrupted and data loss occurs.
l If a consistency group is disabled due to a permanently disconnected link between two
disk arrays, delete the consistency group.
Prerequisites
A license file is required for enabling the consistency group function.
Reference Standard
If consistency groups are working properly, the following items are true on the
DeviceManager:
l All of the consistency groups are in the Normal health status and Normal running
status.
l No consistency group alarm appears on the Current Alarms tab page.
Precaution
The running status of a consistency group is the same as Pair Running Status of the remote
replications added to the consistency group. Only remote replications whose Pair Running
Status is Split can be added to a consistency group. When the status of any of the remote

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
replication members contained in a consistency group changes, the status of the remaining
members also changes accordingly.
Procedure
Step 2 In the function pane, click Remote Replication.

The Remote Replication page is displayed.
Step 3 On the Remote Replication Consistency Group tab, view the information about the desired
consistency group.
Table 19-4 Consistency group status parameters and their meanings
Health Status Health status of a consistency group. The value can be:
consistency group are normal.
l Fault: One or more replication pairs for the consistency group are
abnormal.
Running Running status of a consistency group. The value can be Normal,

Status Synchronizing, To be recovered, Interrupted, Split, or Invalid.
----End
Exception Handling
If a consistency group alarm appears on the Current Alarms tab page, select the alarm and
19.8 Checking Clone Tasks

The clone function is mainly used for data backup. It can generate point-in-time complete
physical copies or consistent duplicates for the data on the storage device. You can learn about
the health and running status of a clone task by checking its status information.

Faulty clone tasks may interrupt clone services and cause data loss.
Prerequisites
A license file is required for enabling the clone function.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Reference Standard
If clone tasks are running properly, the following items are true on the DeviceManager:
l All of the clone tasks are in the Normal health status and Normal running status.
l No clone alarm appears on the Current Alarms tab page.
Precaution
None
Procedure

Step 2 In the function pane, click Clone.
The Clone page is displayed.
Step 3 On the Clone page, view the information about the desired clone task.
Table 19-5 Clone status parameters and their meanings

Health Status Health status of a clone task. The value can be:
l Normal: The functionality and operating performance of the clone task
are normal.
l Fault: One or more mirror pairs for the clone task are abnormal.
Running Running status of a clone task. The value can be Normal, Synchronizing,
Status Reversely synchronizing, To be recovered, Interrupted, Split, or
Queuing.
----End
Exception Handling
If a clone alarm appears on the Current Alarms tab page, select the alarm and diagnose the
19.9 Checking Snapshot Tasks

Snapshots can provide continuous data protection with quick data backup and recovery. You
can learn about the health and running status of a snapshot task by checking its status

Faulty snapshot tasks may interrupt snapshot services and impair data security.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Prerequisites
A license file is required for enabling the snapshot function.
Reference Standard
If snapshot tasks are working properly, the following items are true on the DeviceManager:
l All of the snapshot tasks are in the Normal health status.
l No snapshot alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 2 In the function pane, click Snapshots.

The Snapshots page is displayed.
Step 3 On the Snapshots page, view the information about the desired snapshot task.
Table 19-6 Snapshot status parameters and their meanings

Health Status Health status of a snapshot task. The value can be:
snapshot task are normal.
l Fault: The snapshot task is running improperly.
Running Status Running status of a snapshot task. The value can be Activated,
Inactive, or Restore.
----End
Exception Handling
If an snapshot alarm appears on the Current Alarms tab page, select the alarm and diagnose
19.10 Checking LUN Copy Tasks

The LUN copy function can copy data from a source LUN to a target LUN and can
implement storage tiering and remote backup. You can learn about the health and running
status of a LUN copy task by checking its status information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

Faulty LUN copy tasks may interrupt LUN copy services and cause data loss.
Prerequisites
A license file is required for enabling the LUN copy function.
Reference Standard
If LUN copy tasks are running properly, the following items are true on the DeviceManager:
l All of the LUN copy tasks are in the Normal health status.
l No LUN copy alarm appears on the Current Alarms tab page.
Precaution
None
Procedure
Step 2 In the function pane, click LUN Copy.

The LUN Copy page is displayed.
Step 3 On the LUN Copy page, view the information about the desired LUN copy task.
Table 19-7 LUN copy status parameters and their meanings
Health Status Health status of a LUN copy task. The value can be:
l Normal: The functionality and operating performance of the LUN copy
task are normal.
l Fault: The LUN copy task is running improperly.
Running Running status of a LUN copy task. The value can be Not start, Stopped,
Status Copying, Paused, Queuing, or Completed.
----End
Exception Handling
If a LUN copy alarm appears on the Current Alarms tab page, select the alarm and diagnose

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
19.11 Checking HyperMirror Status

HyperMirror provides mirror copies for LUNs and continuously protects LUNs without
affecting applications running on the host. By checking HyperMirror information, you can
learn about its health status and running status.
Prerequisites
HyperMirror is license enabled.
Reference Standard
If the status of HyperMirror is normal, on the DeviceManager management page:
l Health Status is Normal.
l No alarms about HyperMirror are displayed on the Current alarms tab page.
Precaution
None
Procedure
Step 2 In the function pane, click HyperMirror.

The HyperMirror page is displayed.
Step 3 On the HyperMirror page, view details about HyperMirror.

Table 19-8 HyperMirror status parameters

Health status Health status of HyperMirror. The value can be:

l Normal: The functions and running performance of HyperMirror are
normal.
l Degraded: The functions of HyperMirror are normal but its running
performance deteriorates.
l Fault: The functions and running performance of HyperMirror are
abnormal.
Running Running status of volume mirroring. The status can be Normal,

status Initializing, Queuing, Synchronizing, Split, Interrupted, or Invalid.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Exception Handling
If a new alarm about HyperMirror is displayed on the Current alarms tab page, select the
alarm, and troubleshoot the fault according to the alarm details and recommended actions.
19.12 Checking SmartMigration Status

SmartMigration can migrate services from the source LUN to the target LUN without
interrupting services. By checking SmartMigration information, you can learn about its
running status.
Prerequisites
SmartMigration is license enabled.
Reference Standard
If the status of SmartMigration is normal, on the DeviceManager management page:
l Running Status is not Fault.
l No alarms about SmartMigration are displayed on the Current alarms tab page.
Precaution
None
Procedure

Step 2 In the View and Management area, click Resource Performance Tuning.
The Resource Performance Tuning page is displayed.
Step 3 Click SmartMigration.
Step 4 On the SmartMigration page, view details about SmartMigration.
Table 19-9 SmartMigration status parameters

Running Running status of SmartMigration. The status can be Migrating,

status Migrated, Fault, Normal or Queuing.
----End
Exception Handling
If a new alarm about SmartMigration is displayed on the Current alarms tab page, select the
alarm, and troubleshoot the fault according to the alarm details and recommended actions.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
19.13 Checking Optimization Feature Status

By checking the status of an optimization feature, you can understand its health status,
operating status, mapping, and associated LUNs. The operating status of an optimization
feature directly affects the performance of a storage system.
Prerequisites
Log in to DeviceManager as a read-only user.
Procedure
Step 1 In the navigation tree on the right, click .

The Provisioning page is displayed.
Step 2 In the Provisioning area on the left, click Resource Performance Tuning.
The Resource Performance Tuning page is displayed.
Step 3 Click an optimization feature that you want to view and check its status. If a fault occurs,
report it to maintenance personnel for handling. Table 19-10 provides items for checking
optimization features.
Table 19-10 Items for checking optimization features
Optimization Feature Status Check Method

Feature
SmartTier Check Migration Status, Migration Triggering Mode, To Be Moved

Up, To Be Moved Down, and Estimated Duration of all storage
pools for which SmartTier is configured.
SmartQoS l On the Priority Control tab page, check I/O Priority, Health
Status and Running Status of LUNs or snapshots.
l On the Traffic Control tab page, check Status and Control Type
of a SmartQoS policy.
SmartPartition View Type and Read Partition Size of a SmartPartition and check
Health Status and Running Status of LUNs in the SmartPartition.
SmartCache l On the SmartCache Pool tab page, view Total Capacity and Used
Capacity of a SmartCache pool and check Health Status and
Running Status of disks in the SmartCache pool.
l On the SmartCache Partition tab page, view Expect Capacity
and Used Capacity of a SmartCache partition.
SmartMigration Check Running Status of SmartMigration.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
To view details, click next to the table heading. From the drop-down list, select indicators
you are concerned with.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide 20 Collecting Information and Reporting a Fault
20 Collecting Information and Reporting a

Fault
About This Chapter
After a fault occurs, collect the basic information, fault information, storage device
information, network information, and application server information, and send it to
maintenance engineers. This can help maintenance engineers quickly locate and rectify the
fault. Please note that the information collection operations described in this chapter must be
authorized by customers in advance.
20.1 Types of Information to Be Collected
The information to be collected includes the basic information, fault information, storage
device information, network information, and application server information.
20.2 Exporting System Data
Periodically export the system data of a storage system and save it in a safe place. This helps
you know the operating status of the storage system and prevent the damage to the storage
system caused by system faults and unexpected disasters. When a system failure occurs, the
exported system data can be used to locate and analyze the failure. The system data to be
exported includes running data, system logs and disk logs.
20.3 Backing Up Storage System Configuration Data
All configuration data of a storage system must be backed up before a system upgrade or
capacity expansion. Backup data can be used to restore the storage system when the upgrade
or capacity expansion fails.
20.4 Exporting Alarms and Events
Alarms and Events record the faults and events that occur during storage system operation.
When the storage device is faulty, view the Alarms and Events to locate and rectify the fault.
20.5 Importing Storage System Configuration Data
When a system fails to be upgraded or malfunctions, you can import backed up system
configuration data to restore system configurations.
20.6 Huawei Technical Support
In the event of a storage system fault, you are advised to collect the information about the
fault, storage device, network, and application servers before contacting technical support

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
engineers. The mentioned information will help maintenance engineers quickly locate and
rectify the fault.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
20.1 Types of Information to Be Collected

The information to be collected includes the basic information, fault information, storage
device information, network information, and application server information.
Types of Information to Be Collected

Collect the types of information specified in Table 20-1 and send them to maintenance
engineers.
Table 20-1 Types of information to be collected
Information Item Action

Type
Basic Device serial Provide the serial number and version of the storage
information number and device.
version NOTE
You can log in to the DeviceManager and query the serial
number and version of the storage device in the General
area.
Customer Provide the customer's contact person and contact

information means.
Fault Occurrence Record the time when a fault occurs.

information time
Symptom Record the symptom when a fault occurs, for example,

an error dialog box or an event notification.
Operations Record the operations performed before a fault occurs.

performed
before a fault
occurs
Operations Record operations that are performed before reporting

performed after the fault to maintenance personnel.
a fault occurs
Storage device Hardware Record the configuration of the hardware modules in

information module the storage device.
configuration
Indicator status Record status of the storage device indicators,

especially the indicators in orange or red.
For details about indicator status, see the OceanStor
5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System V300R001 Hardware
Description.
System data Manually export the operating data, and system logs of
the storage device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Information Item Action

Type
Alarms and Manually export the alarms and events of the storage
events device.
Network Connection Describe the networking mode between application

information mode servers and the storage device, for example, Fibre
Channel or iSCSI networking.
Switch model Record the switch models if any switches exist on the
network.
Network Describe the network topology or provide the network

topology diagram.
IP address Describe the IP address allocation principle or provide

information an IP address allocation list if the iSCSI networking
mode is used.
Application Operating Record the types and versions of the operating systems
server system version installed on the application servers.
information
Port rate Record the port rates of the application servers
connected to the storage device. For details about how
to view port rate, see Help.
Operating View and export the operating system logs.

system logs
20.2 Exporting System Data

Periodically export the system data of a storage system and save it in a safe place. This helps
you know the operating status of the storage system and prevent the damage to the storage
system caused by system faults and unexpected disasters. When a system failure occurs, the
exported system data can be used to locate and analyze the failure. The system data to be
exported includes running data, system logs and disk logs.
Context
l Running data indicates the real-time running status of a storage system, such as, the
configuration information of LUN. The running data file is in *.txt format.
l System logs record the information about the running data, events, and debugging
operations on a storage system and can be used for analyzing the running status of the
storage system. The system log includes recent log and historical log. When the size of
recent log reaches 10 MB, the system will dump the recent log to historical log. The
system log file is in *.tgz format.
l DHA runtime log is the daily runtime log of disk. It mainly includes daily disk health
status and IO information. The DHA runtime log file is in *.tgz format.
l HSSD log is working log of HSSD, such as, the S.M.A.R.T information of disk. The
HSSD log file is in *.tgz format.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Before the download of system logs, DHA runtime logs, or HSSD logs, the system collects
those logs of controllers and shows the collection progress. After all logs are collected, you
can download your desired logs.
NOTICE
l It takes several minutes to collect and export system logs or disk logs.
l After the system starts collecting system logs, DHA run logs, or HSSD logs, you need to
wait for five minutes or download all the collected logs before you collect and download
other logs.
Procedure
Step 1 Go to the Export Data dialog box.

2. In the Task area, click Export Data.
The Export Data dialog box is displayed.
Step 2 Export data.
l In Running Data of the Export Data dialog box, click Download.
The system running data is exported.
l In System Log of the Export Data dialog box, click Download.
The system starts collecting logs and expands the log list. You can click Download to
download logs.
l In Disk Log of the Export Data dialog box, click Download DHA Runtime Log.
download logs.
l In Disk Log of the Export Data dialog box, click Download HSSD Log.
download logs.
NOTE
l Under System Log, if you select Export All Logs, the system exports all system logs. If not, the
system exports the recent system logs.
l If you export the data using the Firefox browser with the default settings , the data will be saved in
the default download path of the browser. You can choose Tools > Options and click the General >
Browser in the Options dialog box to view the default download path.
l If you export the data using the Google Chrome browser with the default settings , the data will be
saved in the default download path of the browser. You can choose Customize and Control Google
Chrome > Settings and view the default download path in the Download Content area of the
Settings page.
Step 3 Click Close.

The Export Data dialog box is closed.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
20.3 Backing Up Storage System Configuration Data

All configuration data of a storage system must be backed up before a system upgrade or
capacity expansion. Backup data can be used to restore the storage system when the upgrade
or capacity expansion fails.
Prerequisites
l The storage system can access the File Transfer Protocol (FTP) server correctly.
l The FTP service has been enabled on the FTP server.
l A folder has been created for saving configuration files.
Context
Configuration data of the storage system can be collected only on the CLI.
Precautions
l Running status data of the storage system is exported in a .dat file. Do not modify any
content in this file.
l If configuration files need to be imported when anomalies occur, contact Huawei
technical support.
Procedure
Step 2 Run the export configuration_data command to export configuration files to an FTP server.
NOTE
For details about this command, see the OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
----End
20.4 Exporting Alarms and Events

Alarms and Events record the faults and events that occur during storage system operation.
When the storage device is faulty, view the Alarms and Events to locate and rectify the fault.
Context
Specify the alarms to be exported by setting the alarm severity or time of occurrence.
This document uses Internet Explorer on a Windows server as an example. If you are using
other web browsers, adjust the operations accordingly.
Precautions
Alarms and system logs are saved in *.xls files. After they are exported, do not modify the file
content.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 1 Go to the Alarms and Events page.
1. On the right navigation bar of the DeviceManager, click .

2. On the left side, click Alarms and Events.
The Alarms and Events page is displayed.
Step 2 Export Alarms and Events.

1. Click the Current Alarms or All Events tab. In the list, choose Alarms and Events that
you want to export.
NOTE
On the Current Alarms tab page, critical alarms, major alarms, and warnings are displayed.
You can export all or specified entries on the Current Alarms tab page.
On the All Events tab page, alarms of all severities are displayed. Alarms on the Current
Alarms tab page are exported to All Events.
You can export all or specified entries on the All Events tab page.
To export alarms or events of a specific severity, set the filter condition before exporting them.
2. Click Save As to save selected or all entries.
3. The Download dialog box is displayed. Click Save.
4. The Save As dialog box is displayed. Select a save path and click Save.
----End
20.5 Importing Storage System Configuration Data

When a system fails to be upgraded or malfunctions, you can import backed up system
configuration data to restore system configurations.
Prerequisites
l The storage system can access the File Transfer Protocol (FTP) server correctly.
l The FTP service has been enabled on the FTP server.
l Ensure that the selected system configuration file is correct and has been backed up.
Context
Storage system configuration information can be imported only on the command-line
interface (CLI).
Precautions
l The type of configuration files to be imported is *.dat. Do not modify exported
configuration file contents.
l Do not perform any operation when importing configuration files.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Procedure
Step 2 Run the import configuration_dataip=xxx.xxx.xxx user=? password=? db_file=? command

to import configuration files from the FTP server to the storage system.
NOTE
For details about this command, see the OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
----End
20.6 Huawei Technical Support

In the event of a storage system fault, you are advised to collect the information about the
fault, storage device, network, and application servers before contacting technical support
engineers. The mentioned information will help maintenance engineers quickly locate and
rectify the fault.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of
China
Website: http://support.huawei.com/enterprise/

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
V3&6900 V3 Storage System 21 Connection Change Between the Storage System and an
Maintenance Guide Application Server
21 Connection Change Between the

Storage System and an Application Server
About This Chapter
After the connection between the storage system and an application server changes, relevant
configurations on the storage system and the application server must be changed. The purpose
is to allow the application server to use storage space through the new connection channels.
This chapter describes how to change configurations after replacing an HBA.
An HBA can be replacement either online or offline. The main configuration procedures after
an HBA replacement are shown in Figure 21-1 and Figure 21-2.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 21-1 Configuration procedure after an HBA offline replacement
Start
Back up the multipath software and

disk information.

configuration data of the storage
system.
Prepare for configurations.
Check whether the new HBA is
compatible with the storage system.
Check system status.
On the storage system, replace the

old WWN.
Implement the
configurations.

Delete the new WWN added to the

Perform an emergency host.
rollback.
Add the old WWN back to the host.
On the host, collect and verify

information.
Mandatory Optional Mandatory

End
parent items parent items subitems

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 21-2 Configuration procedure after an HBA online replacement
Start
Back up the multipath software and disk

information.

configuration data of the storage system.
Prepare for configurations. Delete the path from UltraPath.

Delete disk devices connected to the Applicable to HP-UX

path. and AIX hosts
On the storage system, replace the old

Implement the WWN.
configurations.
Delete the new WWN added to the host.

Perform an emergency
rollback.
On the host, collect and verify

information.
Mandatory Optional Mandatory Optional

End
parent items parent items subitems subitems
21.1 Operations After an HBA Replacement (in Windows)

This section describes after replacing the HBA of a Windows host, how to configure the HBA
on the storage system and the host to make it work correctly.
21.2 Operations After an HBA Replacement (in Linux)
This section describes after replacing the HBA of a Linux host, how to configure the HBA on
the storage system and the host to make it work correctly.
21.3 Operations After an HBA Replacement (in AIX)
This section describes after replacing the HBA of an AIX host, how to configure the HBA on
21.4 Operations After an HBA Replacement (in HP-UX)

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
This section describes after replacing the HBA of an HP-UX host, how to configure the HBA
21.5 Emergency Rollback of Configurations and Operations After Replacing an HBA
After replacing an HBA, if you encounter an abnormality or fault during configurations and
operations on the host or storage system, you can perform an emergency rollback as instructed
in this section.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
21.1 Operations After an HBA Replacement (in Windows)

This section describes after replacing the HBA of a Windows host, how to configure the HBA
21.1.1 Preparing for Configuration (in Windows)

Before configuring the new HBA, you must finish preparatory work such as backing up host
multipath and disk information and checking the storage device's running status to ensure that
the space configuration can be successfully implemented.
Prerequisites
l The old HBA of the host has been replaced.
Procedure
Step 1 Back up UltraPath and disk information.
1. Run upadm show vlun and upadm show path to view and back up the UltraPath status
information.
2. Back up disk Information.
a. Log in to the Windows Server 2008 application server as an administrator.
b. Press Windows+R (if the operation is performed remotely, perform it in full screen
c. Type diskmgmt.msc and press Enter.
d. In the Disk Management page that is displayed, view the host disk information.
3. Back up HBA information.
If the fcinfo software is installed on the host, do the following:
i. Press Window+R to open the Run dialog box.
ii. Type cmd and press Enter.
iii. In the command window that is displayed, run fcinfo to view the HBA
information.
If the fcinfo software is not installed on the host, do the following:
i. Press Window+R to open the Run dialog box.
ii. Type devmgmt.msc and press Enter to open the Device Manager page.
iii. Select Storage controllers and double-click Fibre Chanel Adapter. On the
Attribute page, view the vendor and version information.
step.
NOTE

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Step 4 Optional: If online replacement is used, you need to delete path information.
l If the HBA is replaced due to a failure, do the following:
a. Run upadm show path to show UltraPath status information.
b. Run upadm show iostat array_id=? to monitor the load balancing of paths.
Specify the storage device using the array_id parameter.
If I/Os are evenly distributed in the remaining paths and there are no errors after 30
seconds, press Ctrl+c to exit.
l If the HBA is replaced proactively, do the following:
a. Run upadm show path and upadm show vlun to show UltraPath status
information.
b. Run upadm set pathstate=disable to disable all paths connected to the old HBA.
Specify the path to be disabled using its path_id.
c. Run upadm show iostat array_id=? to monitor the load balancing of paths.
d. Run upadm show path to show UltraPath status information.
In the execution result, the states of all paths connected to the old HBA are Disable.
Step 5 Check whether the new HBA is compatible with the storage system.
1. Press Window+R to open the Run dialog box.
2. Type devmgmt.msc and press Enter to open the Device Manager page.
3. Select Storage controllers and double-click Fibre Chanel Adapter. On the Attribute
page, view the vendor and version information.

1. Check whether any error exists on the host.
a. Press Windows+R (if the operation is performed remotely, perform it in full screen
b. Run eventvwr.msc and devmgmt.msc and press Enter.
c. In the Event Viewer and Device Manager windows, Check whether any error
exists on the host. If there are errors, remove them and then proceed to the next
step.
2. Check disk path status.
b. Run upadm show path to check whether the system path status is Normal. If the
status of a path is Degrade, run upadm set phypathnormal. Specify the path using
the path_id.
Step 7 On the switch, check whether the zoning of the new HBA is complete.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
21.1.2 Configurations and Operations After an HBA Replacement

(in Windows)
Prerequisites
l The old HBA has been replaced and the new HBA has been correctly installed.
l The WWNs of the old and new HBAs have been obtained.
l UltraPath has been installed on the application server.
Procedure
Step 1 On the storage system, replace the old WWN.
1. Run show initiator initiator_type=FC to view the connection status between the HBA
and the storage device and obtain the ID of the host to which the old HBA belongs.

ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
2. Run remove host initiator initiator_type=FC to remove the WWN of the old HBA.
Specify the WWN of the old HBA using the wwn parameter.
3. Run add host initiator host_id=? initiator_type=FC wwn=? to add the new WWN to
the host. Specify the host and WWN of the new HBA using the host_id and wwn
parameters.
4. Run show initiator isfree=yes initiator_type=FC. If in the command output, the WWN
status of the new HBA is not Free, then the replacement is successful.
devices.
4. Right-click Disk Drives > Scan for hardware changes. The system will scan for disks
automatically.
number of mapped LUNs. If they are not the same, check the LUN mapping and path
Step 3 Run upadm show iostat array_id=? to monitor the load balancing of paths. Specify the
storage device using the array_id parameter.
If I/Os are evenly distributed in all paths and there are no errors after 30 seconds, press Ctrl+c
to exit.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
21.2 Operations After an HBA Replacement (in Linux)

This section describes after replacing the HBA of a Linux host, how to configure the HBA on
21.2.1 Preparing for Configuration (in Linux)

Prerequisites
Procedure
1. Run upadmin show vlun and upadmin show path to view and back up the UltraPath
status information.
2. Run vgdisplay and vgs to view and back up volume group (VG) information.
3. Run pvs -a to back up physical volume (PV) information.
4. Run fdisk -l|grep "Disk " and systool -c fc_host -v to back up disk and HBA
information.
step.
NOTE
a. Run upadmin show path to check whether the path status of the faulty HBA is
Fault. If the path status is Fault, run upadmin clear obsolete_path to delete the
faulty path. Specify the path whose status is Fault using its path_id.
b. Run upadmin show iostat array_id=? to monitor the load balancing of paths.
c. Run upadmin show path to show UltraPath status information.
The information about the deleted paths should not appear in the execution result.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

a. Run upadmin show path and upadmin show vlun to show UltraPath status
information.
b. Run upadmin set pathstate=disable to disable all paths connected to the old HBA.
Specify the path to be disabled using its path_id.
c. Run upadmin show iostat array_id=? to monitor the load balancing of paths.
d. Run upadmin show path to show UltraPath status information.
In the execution result, the states of all paths connected to the old HBA are Disable.
Step 5 Run systool -c fc_host -v to see whether the new HBA is compatible with the storage system.
If it is not compatible with the storage system, replace it.
Step 6 Check the system status and see whether there are disks or tapes connected to the HBA.
1. Run tail -200 /var/log/messages to check the storage system status. If an error exists on
the HBA or any disk, remove it and proceed to the next step.
2. Run grep scsiY /proc/scsi/scsi to see whether there are disks or tapes connected to the
new HBA, where scsiY indicates the device file name of the new HBA.
There should be no disk or tape under scsiY.
3. Run systool -c fc_host -v to obtain the WWN of the new HBA and record it, where
port_name indicates the WWN of the new HBA.
Step 7 On the switch, check whether the Zone of the new HBA is complete.
----End

(in Linux)
Prerequisites
Procedure

ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
parameters.
1. Run upRescan to scan for disks.
#upRescan
3. Run upadmin show path to check whether the disk path status is normal. If you find a
path whose status is Degrade, run upadmin set phypathnormal to set the path to
Normal. Specify the path whose status is Degrade using the path_id.
Step 3 Run upadmin show iostat array_id=? to monitor the load balancing of paths. Specify the
to exit.
----End
21.3 Operations After an HBA Replacement (in AIX)

This section describes after replacing the HBA of an AIX host, how to configure the HBA on
21.3.1 Preparing for Configuration (in AIX)

Prerequisites
Procedure
1. Run upadm show vlun and upadm show path to view and back up the UltraPath status
information.
2. Run lsvg and lsvg vgname to view and back up volume group (VG) information where
vgname represents the name of the VG.
3. Run lspv to back up physical volume (PV) information.
4. Run lsdev -Cc disk and lsdev -Cc adapter respectively to back up disk and HBA
information.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
step.
NOTE
a. Run upadm show path to show UltraPath status information.
b. Run rmpath -dl hdiskX -p fscsiY to delete paths whose parent is fscsiY, where
hdiskX and fscsiY indicates the device file name of a host disk and a to-be-replaced
HBA respectively.
d. Run upadm show path to show UltraPath status information.
a. Run upadm show path and upadm show vlun to show UltraPath status
information.
b. Run chpath -s disable -l hdiskX -p fscsiY to disable paths whose parent is fscsiY,
where hdiskX and fscsiY indicates the device file name of a host disk and a to-be-
replaced HBA.
d. Run rmpath -dl hdiskX -p fscsiY to delete all disabled links.
e. Run upadm show path to show UltraPath status information.
Step 5 Delete disk devices connected to the links.
1. Run lsdev -Cc disk and lsdev -Cc disk | wc -l to view system disk status.
2. Run lsdev -p fscsiY and lsdev -p fscsiY -c disk -F name | xargs -n1 rmdev -dl to delete
disks connected to the path.
3. Rerun lsdev -Cc disk and lsdev -Cc disk | wc -l to view system disk information in
which the deleted disks should not exist.
1. Run lscfg -vpl fcsY | grep Address to check whether the WWN of the new HBA is as
planned, where fcdY represents the new HBA.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Run fcstat fcsY to check whether the HBA model is compatible with the storage system.
1. Run errpt to check the storage system status. If an error exists on the HBA or any disk,
remove it and proceed to the next step.
2. Run lsdev -p fcsY and lsdev -p fscsiY to check whether there are disks or tapes
connected to the new HBA, where fcsY indicates the device file name of the new HBA
and fscsiY indicates the subdevice of fcsY.
There should be no disk or tape under fscsiY.
3. Modify the properties of the device fscsiY.
a. Run the lsattr -El fscsiY to command to check whether fc_err_recov is fast_fail
and dyntrk is yes. If yes, go to Step 7.4. If no, go to Step 7.3.b.
b. Run the rmdev -l fscsiY -R command to clear the configuration of device fscsiY.
c. Run the chdev -l fscsiY -a fc_err_recov=fast_fail and chdev -l fscsiY -a
dyntrk=yes commands to modify the properties of device fscsiY.
4. Run cfgmgr -vl fcsY to scan for the HBA and generate the fscsiY device.
5. Run lsattr -El fcsY and lsattr -El fscsiY to see whether device parameters are changed
successfully.
6. Run lscfg -vpl fcsY | grep Address to view the WWN of the new HBA and record it.
----End

(in AIX)
Prerequisites
Procedure

ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
parameters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
1. Run lsdev -Cc disk and lsdev -Cc disk | wc -l to show disks on the host.
2. Run cfgmgr -vl fcsY to scan for the HBA and recognize the storage device.
3. Rerun lsdev -Cc disk and lsdev -Cc disk | wc -l and compare the result with that in Step
2.1. The number of newly generated device files should be the same as expected, and the
vendors should all be Huawei.
4. Run upadm show vlun and compare the result with that in Step 2.1 to check whether
the number of disks managed by UltraPath is the same as planned.
5. Run upadm show path to check whether the disk path status is Enable. If you find a
path whose status is Degrade, run upadmin set phypathnormal to set the path to
Normal. Specify the path whose status is Degrade using the path_id.
Step 3 Run upadm show iostat array_id=? to monitor the load balancing of paths. Specify the
to exit.
----End
21.4 Operations After an HBA Replacement (in HP-UX)

This section describes after replacing the HBA of an HP-UX host, how to configure the HBA
21.4.1 Preparing for Configuration (in HP-UX)

Prerequisites
The old HBA of the host has been replaced.
Procedure
Step 1 Back up the NMP multipath and disk information.
1. Run scsimgr get_attr -a leg_mpath_enable to view and back up the multipath status.
2. Run vgdisplay -v to view and back up volume group (VG) information.
3. Run lspv to back up physical volume (PV) information.
4. Run ioscan -fkNC disk and ioscan -fnkC fc to back up disk and HBA information.
step.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
NOTE
Step 4 Optional: If online replacement is used, you need to delete link information from the NMP
multipath software.
a. Run scsimgr lun_map -D /dev/rdisk/diskX to view disk path information, where
b. Run ioscan -fnkC fc, ioscan -kfNC tgtpath, ioscan -P health -H xxx, and rmsf -
H xxx to delete links, where xxx indicates the ID of the HBA to be replaced.
c. Run sar -L 1 30 to monitor link I/Os.
d. Run scsimgr lun_map -D /dev/rdisk/diskX to view disk path information, where
The information about the deleted links should not appear in the command output.
a. Run scsimgr lun_map -D /dev/rdisk/diskX to view disk path information, where
b. Run ioscan -fnkC fc, scsimgr -f disable -H xxx and ioscan -P health -H xxx to
disable links, where xxx indicates the ID of the HBA to be replaced.
c. Run rmsf -H xxx to delete all disabled links.
d. Run sar -L 1 30 to monitor link I/Os.
e. Run scsimgr lun_map -D /dev/rdisk/diskX to view disk path information. The
information about the deleted links should not appear in the command output.
Step 5 Delete disk devices connected to the links.

1. Run ioscan -fnkC disk and ioscan -fnkC disk | grep -i HUAWEI | wc -l to view system
disk status.
2. Run ioscan -fnkC fc and ioscan -fnk -C disk -H hw_path | grep -i HUAWEI | awk
'{ print $3}' | xargs -n1 rmsf -C disk -H to delete disk devices connected to the links,
where hw_path indicates the path of the HBA to be replaced.
3. Run ioscan -fnkC disk and ioscan -fnkC disk | grep -i HUAWEI | wc -l again to check
the system disk status, which should not contain the status of deleted disk devices.
1. Run fcmsutil /dev/fcdY to check whether the WWN of the new HBA is as planned,
where fcdY represents the new HBA.
2. Run fcmsutil /dev/fcdY vpd to check whether the HBA is compatible with the storage
system.
1. Run tail -200 /var/adm/syslog/syslog.log to check the storage system status. If an error
exists on the HBA or any disk, remove it and proceed to the next step.
2. Run ioscan -fnkC fc and ioscan -fnkH HW Path to see whether there are disks or tapes
connected to the new HBA, where HW Path indicates the path of the HBA to be
replaced.
There should be no disk or tape under fcdY.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
----End

(in HP-UX)
Prerequisites
Procedure
1. Run show initiator initiator_type=FC command to view the connection status between
the HBA and the storage device and obtain the ID of the host to which the old HBA
belongs.

ID Multipath Type
----------------- ------------------- ----- -------
---------- ------------------
100000000000* Online Yes --
-- Default
2. Run remove host initiator initiator_type=FC command to remove the WWN of the old
HBA. Specify the WWN of the old HBA using the wwn parameter.
3. Run add host initiator host_id=? initiator_type=FC wwn=? command to add the new
WWN to the host. Specify the host and WWN of the new HBA using the host_id and
wwn parameters.
4. Run show initiator isfree=yes initiator_type=FC command. If in the command output,
the WWN status of the new HBA is not Free, then the replacement is successful.

1. Run ioscan -fnNkC disk and vgdisplay -v commands to show the disks and volume
groups (VGs) on the host.
2. Run ioscan -fNC disk command to scan for disks.
3. Rerun ioscan -fnkC disk command and compare the result with that in Step 2.1. The
number and the types of newly generated devices should be the same as planned.
4. Run insf -eC disk command and confirm that the LUN device files are generated.
5. Rerun ioscan -fnkC disk command and compare the result with that in Step 2.1. The
number and the types of newly generated devices should be the same as planned.
6. If the NMP software is installed on the host, do the following:
a. Run scsimgr get_attr -a leg_mpath_enable command and confirm that the NMP
is enabled.
b. Run ioscan -funC disk command to view the number of disk paths when NMP is
not enabled.
c. Rerun ioscan -funNC disk command and confirm that the number of newly
generated aggregated disks is the same as planned.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
d. Run ioscan -m dsf command to view the mappings between persistent disks and
legacy disks.
e. Run scsimgr lun_map -D /dev/rdisk/diskX command to view disk path
information with NMP enabled, where diskX represents a disk on the host.
Step 3 Run sar -L 1 30 command to monitor path I/Os.
to exit.
----End
21.5 Emergency Rollback of Configurations and

Operations After Replacing an HBA
After replacing an HBA, if you encounter an abnormality or fault during configurations and
operations on the host or storage system, you can perform an emergency rollback as instructed
in this section.
The main procedures for an emergency rollback are shown in Figure 21-3 and Figure 21-4.
Figure 21-3 Emergency rollback procedure after an offline HBA replacement
Start

Delete the new WWN added to the

host.
End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Figure 21-4 Emergency rollback procedure after an online HBA replacement
Start
Delete the new WWN

added to the host.
Add the old WWN back

to the host.
Rescan for disks on the

host.
End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide A Alarm Notification Service Configurations
A Alarm Notification Service

Configurations
Alarm notification service configurations include the basic configurations of File Transfer
Protocol (FTP) servers, Simple Mail Transfer Protocol (SMTP) servers, and short message
service (SMS) modems. These configurations ensure that common alarm management
operations can be correctly performed.
A.1 Configuring an FTP Server

You can install and configure a wide range of FTP servers. This section describes how to
configure an Xlight FTP server. For details about how configure other FTP servers, see the
related configuration documentation.
A.2 Configuring an SMTP Server
The email notification function is available only when the SMTP server runs correctly. This
section describes how to configure a Winmail Server.
A.3 Configuring an SMS Modem
A short message service enables a storage system to send alarm information to specified
mobile numbers, helping engineers locate and troubleshoot faults.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
A.1 Configuring an FTP Server

You can install and configure a wide range of FTP servers. This section describes how to
configure an Xlight FTP server. For details about how configure other FTP servers, see the
related configuration documentation.
Prerequisites
The FTP server software installation package is ready.
The IP address to be configured can correctly communicate with the storage system.
Procedure
Step 1 Start the Xlight FTP server software.
The Xlight FTP Server page is displayed.
Step 2 Configure a virtual server.
1. On the Xlight FTP Server page, click .

The New Virtual Server dialog box is displayed.
2. In the New Virtual Server dialog box, set IP Address, Port, and Protocol to the local
IP address, 21, and FTP, respectively.
3. Click OK.
The added virtual server is displayed in the Xlight FTP Server page that is displayed.
Step 3 Start the virtual server.
Select the added virtual server and click to start the server.
NOTE
You can select the added virtual server, right-click, and choose Start Server to start the server.
Step 4 Add a user.
1. On the Xlight FTP Server page, click .

The user list is displayed.
2. Click .
The adding users dialog box is displayed.
3. In the dialog box, enter Username and Password and set Home Directory.
4. Click OK.
The user is added, and user information is displayed on the user page.
Step 5 Set virtual directory permissions.
1. In the user list, select the added user and click .

The user name page is displayed.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. On the navigation bar on the left, click .

The user directory management page is displayed.
3. Select the access directory of the added user and click .

The Virtual Directory dialog box is displayed.
4. In the Permission area, set permissions.
5. Click OK.
Virtual directory permissions are configured.
----End
A.2 Configuring an SMTP Server

The email notification function is available only when the SMTP server runs correctly. This
section describes how to configure a Winmail Server.
Prerequisites
The SMTP server software installation package is ready.
The IP address to be configured can correctly communicate with the storage system.
Procedure
Step 1 Install the Winmail Server software.
Step 2 Log in to the Winmail Server management tool.

1. Open the Start menu and find Magic Winmail in Programs.
2. Run Magic Winmail Administration tool. The Connect Server dialog box is
displayed.
3. Enter the user name and password respectively in User name and Password.
4. Click OK to log in to the management tool.
Step 3 Check operating status of the email system.

1. In the navigation tree of the Winmail Server management tool, choose System Setup >
Services.
2. On the Services page, check whether SMTP, POP3, HTTP, and ADMIN services are
working correctly.
If the indicator is steady green, the services are working correctly. If the indicator is
steady red, the services are working incorrectly.
Step 4 Set a domain name.

1. In the navigation tree, choose Domain Setting > Domains.
2. On the Domains page, click Add.
The Domain dialog box is displayed.
3. In the Domain dialog box, set Domain name, Description, Storage of all mailbox,
Total of mailbox, and Mailbox min. quato.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
4. Click OK.
The created domain name is displayed in the domain name list.
Step 5 Set an email account.
1. In the navigation tree, choose User and Group > Users.
2. On the Users page, click Add.
The General dialog box is displayed.
3. In the General dialog box, set User name, Password, and Confirm password.
4. Click Next.
The Group page is displayed.
5. Optional: Select a group to which you want to add the user.
6. Click Next.
The Right page is displayed.
7. On the Right page, configure parameters in the Right and Auto forward areas.
8. Click Next.
The Quota page is displayed.
9. On the Quota page, set Mailbox quota, Number of mails, and Warning limit.
10. Click Finish.
The user and email account are configured. The user is displayed in the user list of the
Users page.
----End
Follow-up Procedure
After configuring the email server, you need to configure an email address for receiving
notifications. The detailed configuration steps vary depending on your email version.
A.3 Configuring an SMS Modem

A short message service enables a storage system to send alarm information to specified
mobile numbers, helping engineers locate and troubleshoot faults.
Prerequisites
The SMS modem to be installed is working correctly.
The subscriber identity module (SIM) card has a positive balance.
Procedure
Step 1 Set a baud rate for the SMS modem.
Ensure that the baud rate of the SMS modem is the same as that of the storage device.
NOTE
The default baud rage of Huawei storage systems is 115,200.
Step 2 Connect the SMS modem to the storage device.

1. Insert a normal SIM that has a positive balance to the SMS modem.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
2. Install the antenna for the SMS modem.

3. Use an RS232 serial cable to connect the serial port of the SMS modem to that of the
storage device.
Step 3 Check status of indicators on the SMS modem.
Check whether the SMS modem is successfully connected to the storage device by observing
the indicator status.
----End

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide B How to Obtain Help
B How to Obtain Help
If a tough or critical problem persists in routine maintenance or troubleshooting, contact

Huawei for technical support.
B.1 Preparations For Contacting Huawei

To better solve the problem, you need to collect troubleshooting information and make
debugging preparations before contacting Huawei.
B.2 How to Use the Document
Huawei provides guide documents shipped with the device. The guide documents can be used
to handle the common problems occurring in daily maintenance or troubleshooting.
B.3 How to Obtain Help from Website
Huawei provides users with timely and efficient technical support through the regional
offices, secondary technical support system, telephone technical support, remote technical
support, and onsite technical support.
B.4 Ways to Contact Huawei
Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and
service. For any assistance, contact our local office or company headquarters.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
B.1 Preparations For Contacting Huawei

To better solve the problem, you need to collect troubleshooting information and make
debugging preparations before contacting Huawei.
B.1.1 Collecting Troubleshooting Information

You need to collect troubleshooting information before troubleshoot.
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 phenomena
l Device type and software version
l Measures taken after the fault occurs and the related results
l Troubleshooting level and required solution deadline
B.1.2 Making Debugging Preparations

When you contact Huawei for help, the technical support engineer of Huawei might assist you
to do certain operations to collect information about the fault or rectify the fault directly.
Before contacting Huawei for help, you need to prepare the boards, port modules,
screwdrivers, screws, cables for serial ports, network cables, and other required materials.
B.2 How to Use the Document

Huawei provides guide documents shipped with the device. The guide documents can be used
to 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.
B.3 How to Obtain Help from Website

Huawei provides users with timely and efficient technical support through the regional
offices, secondary technical support system, telephone technical support, remote technical
support, and onsite technical support.
Contents of the Huawei technical support system are as follows:
l Huawei headquarters technical support department
l Regional office technical support center
l Customer service center
l Technical support website: http://support.huawei.com/enterprise/
You can query how to contact the regional offices at http://support.huawei.com/enterprise/.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
B.4 Ways to Contact Huawei

Huawei Technologies Co., Ltd. provides customers with comprehensive technical support and
service. For any assistance, contact our local office or company headquarters.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of
China
Website: http://enterprise.huawei.com/

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide C Glossary
C Glossary
A
AC power The module that transfers the external AC power supply into the
module power supply for internal use.
Application A service processing node (a computer device) in the network.
server Application programs of data services are run on the application
server.
Asynchronous A kind of remote replication. When the data on the primary site is
remote updated, the data does not need to be updated on the mirroring site
replication synchronously to finish the update. In this way, performance is not
reduced due to data mirroring.
B
Backup A periodic operation performed on the data stored in the database for
the purposes of database recovery in case that the database is faulty.
The backup also refers to data synchronization between active and
standby boards.
Bandwidth A range of transmission frequencies that a transmission line or
channel can carry in a network. In fact, it is the difference between
the highest and lowest frequencies the transmission line or channel.
The greater the bandwidth, the faster the data transfer rate.
Baud rate The number of times per second the signal can change on a
transmission line. Commonly, the transmission line uses only two
signal states, making the baud rate equal to the number of bits per
second that can be transferred. The underlying transmission technique
may use some of the bandwidth, so it may not be the case that user
data transfers at the line's specified bit rate.
Bit error A computer that is connected to the serial port or management
network port of the storage system for maintenance.
Bit error rate The percentage of bits that have errors relative to the total number of
bits received in a transmission.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Bonding Bonding can bind multiple independent physical network ports into a
logical port, which ensures the high availability of server network
connections and improving network performance.
Boundary scan A test methodology that uses shift registers in the output connections
of integrated circuits. One IC often is connected to the next. A data
pattern is passed through the chain and the observed returned data
stream affected by the circuit conditions gives an indication of any
faults present. The system is defined under IEEE standard 1149.1 and
is also often known as JTAG (Joint Test Action Group).
Browser/Server An architecture that defines the roles of browser and server, where the
browser is the service request party and the server is the service
provider.
C
Cache hit ratio The ratio of directly accessed I/O from Cache to all the I/O operation
during the read operation.
Cache prefetch According to the operation in which data has been read or is being
strategy read, the required data is read from a disk into the cache in advance.
Captive Screw After the screw is loosened, screw caps and bolts are not disconnected
from the main body.
Cascading Connect the storage system to more disk enclosures through
connection cables, thus expanding the capacity of the storage system.
CHAP A method to periodically verify the identity of the peer using a 3-way
handshake. During the establishment of a link, the authenticator sends
a "challenge" message to the peer. The peer responds with a value
calculated using a "one-way hash" function. The authenticator checks
the response against its own calculation of the expected hash value. If
the values match, the authentication is acknowledged. CHAP
provides protection against playback attack.
Clone A snapshot technology. The source data is completely copied to
generate a data duplicate; therefore the duplicate needs the storage
space as the same size as the source data. It is also called clone. In the
VIS system, it is also called third-mirror break-off snapshot.
Cluster A mechanism adopted to improve the system performance. Several
devices of the same type form a cluster. The exterior of a cluster is
some like a kind of equipment. In the interior of a cluster, the nodes
share the load.
Coffer A technology for ensuring data security and integrity in a storage
system. It is used to store the mission-critical data of the system.
Coffer disk Disks that build up the coffer.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Constant prefetch A cache prefetch strategy. The size of the data to be prefetched is the
size as set. This strategy applies to the applications that require
reading data of a fixed size in a certain order. An example is the
streaming media demanded by multiple subscribers who use the same
bit rate.
Controller The core module that processes services in a storage system. It
contains physical components such as system-level CPUs and
memory.
Controller An enclosure that accommodates controllers and provides storage
enclosure services. It is the core component of a storage system, and generally
consists of components such as controllers, power supplies, and fans.
Copyback The process of copying the data from the hot spare disk back to the
previous disk when the faulty member disk is restored or replaced by
a new one.
Copying A state of pair. The state indicates that the source LUN data is being
synchronized to the target LUN.
D
Data flow A process that involves processing the data extracted from the source
system, such as filtering, integration, calculation, and summary,
finding and solving data inconsistency, and deleting invalid data so
that the processed data meets the requirements of the destination
system for the input data.
Data migration It is the process to cleanse and transform historical data, and then load
them to the new system.
Data source A system, database, or file that can make BOs persistent. A data
source can be a database instance or a database user.
Data switch A data switch used for interconnections between controllers.
Dirty data The data that is stored temporarily on cache and has not been written
onto disks.
Disaster recovery A system deployment solution aiming at reducing loss in disasters. A
set of disaster recovery system that is the same as the production
system is deployed as a backup to store the production data when a
fault occurs in the production system. The applications are switched
over to the disaster recovery system before the production system
recovers. After the production system recovers, the applications are
switched back to the production system.
Disk array A set of disks from one or more commonly accessible disk
subsystem. These disks are combined and controlled by the control
software. The control software provides the storage capacity of these
disks for hosts as one or more virtual disks.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Disk Domain A combination of disks. A disk domain consists of the same type or
different types of disks. Disk domains are isolated from each other.
Therefore, services carried by different disk domains do not affect
each other in terms of performance and faults (if any).
Disk location Locate a hard disk, that is, determine the enclosure number and slot
number of the hard disk in the storage system.
Disk enclosure It consists of the following parts in redundancy: expansion module,
hard disk, power module, and fan module. System capacity can be
expanded by cascading multiple disk enclosures.
Disk utilization The percentage of used capacity in the total available capacity.
E
eDevLUN Logic space created by third-party storage systems.
(external device
LUN)
Engine Two controllers in one enclosure are called Engine.
Expansion Connecting a storage system to more disk enclosures through
connection cables, thus expanding the capacity of the storage system.
Expander module A component used for expanding.
F
Failover The automatic substitution of a functionally equivalent system
component for a failed one. The term failover is most often applied to
intelligent controllers connected to the same storage devices and host
computers. If one of the controllers fails, failover occurs, and the
survivor takes over its I/O load.
Field replaceable A unit that can function as a circuit board, part, or component of an
unit electronic device. It can be quickly and easily removed from a
personal computer or other electronic devices. If an FRU becomes
faulty, users can replace it with a new one instead of sending the
entire product or system for maintenance.
File Engine The component in a unified storage systems that provides file-level
service.
Firmware The programmable software part in a hardware component. A
firmware is a part of hardware, but is scalable as software.
Front-end host The port that connects the controller enclosure to the service side and
port transfers service data. There are three types of front-end host ports:
SAS, FC, and iSCSI.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Gateway The entrance node on another network.

Global system for The second-generation mobile networking standard defined by
mobile European Telecommunications Standards Institute (ETSI). It is aimed
communications at designing a standard for global mobile phone networks. The
standard allows a subscriber to use a phone globally. GSM consists of
three main parts: mobile switching subsystem (MSS), base station
subsystem (BSS), and mobile station (MS).
H
Hard disk A non-volatile storage device that stores digitally encoded data on
rapidly rotating platters with magnetic surfaces. Hard disks generally
offer more storage and quicker access to data than floppy disks do.
Hard disk tray The tray that bears the hard disk.
Heartbeat Heartbeats are the packets, requiring no acknowledgement,
transmitted between two devices. The device can judge the validity
status of the peer device. Heartbeat supports node communication,
fault diagnosis, and event triggering.
Hit ratio The ratio of directly accessed I/Os from cache to all I/Os.
Hot swap In a running system, inserting or removing a blade does not affect
normal running of the system.
I
I/O Data movement process between memory and peripheral devices in
the computer system. I/O is a collective name, indicating the
operations reading data into the memory and writing data to other
places from computer memory.
Initiator A system component that can initiate an I/O operation on an I/O bus
or on a network.
Intelligent A cache prefetch strategy. The system software calculates a proper
prefetch size of prefetched data. This strategy applies to a read application
involving a single bit stream or to the situations where you do not
know whether the data is read in a certain order. An example is
reading or writing a file.
Interface module interface module connects various types of front-end host port, such
as the front-end host ports of SAS, FC and iSCSI.
The interface module can be configured with one type of the
following host ports or expansion ports: 10Gb iSCSI, 8Gb FC, and
iSCSI host ports, or 4Gb FC and 6Gb SAS expansion ports.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Load balance A method of adjusting the system, application components and data to
averagely distribute the applied I/O or computing requests for
physical resources of the system.
Logical unit The entity is located inside the SCSI object, and can execute I/O
commands. After a SCSI I/O command is sent to an object, the logic
unit inside the object executes this command. Usually, each SCSI
physical disk has one logic unit. A tape drive and array controller may
have multiple logic units, which process different I/O commands.
Each logic unit inside an array controller corresponds to a virtual
disk.
Logical unit The SCSI identifier of the internal logical unit of a target.
number
LUN format The process of writing 0 bits in the data area on the logical drive and
generating related parity bits so that the logical drive can be in the
ready state.
LUN mapping The storage system maps LUNs to ASs so that the ASs can access the
storage reorganization.
SmartMigration It is also called LUN migration. It indicates a method for the data in
the LUN to migrate between different physical storage space while
ensuring data integrity and uninterrupted operation host services.
LUN copy The function of copying the original LUN data to one or multiple
target LUNs.
M
Maintenance The computer that is connected through a serial port or management
terminal network port and maintains the storage system.
Management An entity that provides a means to transmit and process the
network information related to network management.
Management The network port on the controller enclosure that is connected to the
network port maintenance terminal. It is provided for the remote maintenance
terminal.
N
Node A managed device in the network. For a device with a single frame,
one node stands for one device. For a device with multiple frames,
one node stands for one frame of the device.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Out-of-band A management mode used during out-of-band networking. In the out-

management of-band management mode, the management and control information
of the network and the bearer service information of the user network
are transmitted through different logical channels.
Original LUN The LUN where the original data of the copied LUNs is located.
Owning For a LUN, the user configures the owing controller, that is, specified
controller the created LUN to a certain controller. When the owning controller
of the LUN is invalid, another controller manages the LUN
automatically. When the owning controller of the LUN is restored, the
original controller manages the LUN again.
P
Power failure When the external power failure occurs, the AC PEM depends on the
protection battery for power supply, which ensures the integrity of the dirty data
in cache.
Pre-copy When the system monitors that a member disk in a RAID group is to
fail, the system copies the data on the disk to a hot spare disk in
advance. This technology is called pre-copy.
Primary storage The controller that plays a leading role in controlling the management
controller is the primary storage controller. It can perform relevant management
operations on the controller enclosure.
Primary/ A procedure during which the two controllers of the storage system
Secondary change their master/slave states.
switchover
Prior controller For the application server LUN, prior controller means that the
working controller is the owner controller of the corresponding array
LUN.
R
RAID level The application of different redundant types to a logical drive. A
RAID level improves the fault tolerance or performance of the logical
drive but reduces the available capacity of the logical drive. You must
specify a RAID level for each logical drive.
Reconstruction A function of the storage system. It refers to the process of restoring
the data saved in the faulty member disk in a storage pool.
Redundancy The scheme to add more than one channels, elements or parts that
have the same functions with the counterparts in the system or device
at a critical place. When a fault occurs, the system or device can work
well, and the reliability is then improved.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Remote A core technology for disaster recovery and a foundation that

replication implements remote data synchronization and disaster recovery. This
technology remotely maintains a set of data mirror through the remote
data connection function of the storage devices that are separated in
different places. Even when a disaster occurs, the data backup on the
remote storage device is not affected. Remote replication can be
divided into synchronous remote replication and asynchronous remote
replication by whether the host that requires mirrors needs the
confirmation information of the remote replication site.
Reverse The process of restoring data from the redundancy machine (RM)
synchronizing when the services of the production machine (PM) are recovering.
Route The path that network traffic takes from its source to its destination.
In a TCP/IP network, each IP packet is routed independently. Routes
can change dynamically.
S
Script A collection of data statements used to perform an operation.
Secondary (1) A controller that backs up service and management data of the
controller primary controller in a clustered system. When the primary controller
fails, the secondary controller is upgraded to the primary controller
and takes over the management and services of the controller
enclosure. (2) A controller that backs up the management data of the
primary controller in a block-level array. When the primary controller
fails, the secondary controller is upgraded to the primary controller
and takes over the management of the system.
Serial port An input/output location (channel) that sends and receives data to and
from a computer's CPU or a communications device one bit at a time.
Serial ports are used for serial data communication and as interfaces
with some peripheral devices, such as mice and printers.
Service data Data which is saved in data disk. Service data is the data source for
computing check data in parity disk.
Service network The network port that is used to store services.
port
SFP optical A component that can make data conversion between optical signals
transceiver and electrical signals and that can receive and transfer data.
Simple network A network management protocol of TCP/IP. It enables remote users to
management view and modify the management information of a network element.
protocol This protocol ensures the transmission of management information
between any two points. The polling mechanism is adopted to provide
basic function sets. According to SNMP, agents, which can be
hardware as well as software, can monitor the activities of various
devices on the network and report these activities to the network
console workstation. Control information about each device is
maintained by a management information block.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Single point A type of failure. Data transmission over a network is stopped and
failure cannot be recovered automatically if a single point failure occurs. The
point can be an interface, a board, a device, or a link.
Small computer A set of standards for physically connecting and transferring data
system interface between computers and peripheral devices. SCSI is most commonly
used for hard disks and tape drives, but it can connect a wide range of
other devices, including scanners, and optical drive.
SmartTenancy A feature of Huawei storage system. With SmartTenancy, multiple
virtual storage systems can be created in one physical storage system,
which allows tenants to share the same storage system hardware
resource without affecting data security and privacy of each other.
This feature achieves more flexible, easy-to-manage and low-cost
shared storage in a multi-protocol unified storage architecture.
Snapshot A data backup technology through which a fully usable copy of a data
object can be quickly generated. The duplicate contains the image of
the data object at a point in time.
Snapshot copy A copy of the snapshot LUN, which is also a snapshot LUN.
Storage system An integrated system. It consists of the following parts: controller,
storage array, host bus adapter, physical connection between storage
units, and all control software.
Storage unit An abstract definition of backup storage media for storing backup
data. The storage unit is connected with actual storage media, used to
back up data.
Streaming media A transmission mode in which data is consumed (read, listened to, or
watched) while it is being sent.
Stripe The set of strips at corresponding locations of each member extent of
a disk array which uses striped data mapping. The strips in a stripe are
associated with each other in a way (e.g. relative extent block
addresses) that allows membership in the stripe to be quickly and
uniquely determined by a computational algorithm. Parity RAID uses
stripes to map virtual disk block addresses to member extent block
addresses.
Subnet A type of smaller networks that form a larger network according to a
rule, for example, according to different districts. This facilitates the
management of the large network.
Subnet mask The technique used by the IP protocol to determine which network
segment packets are destined for. The subnet mask is a binary pattern
that is stored in the device and is matched with the IP address.
Synchronous A kind of remote replication. When the data on the primary site is
remote updated, the data must be synchronously updated on the mirroring site
replication before the update is complete. In this way, the data that is stored on
both the primary and mirroring sites can be synchronized.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Target A system component that can receive SCSI I/O operation commands.
Target LUN The target for LUN copy.
Thin provisioning A mechanism that offers on-demand allocation of storage space.
Thin LUN The thin LUN is a logic disk that can be accessed by hosts. The thin
LUN dynamically allocates storage resources from the thin pool
according to the actual capacity requirements of users.
Timing Snapshot To create snapshots periodically to continuously protect data.
Topology The logical layout where computer systems and network components
are interconnected with one another. The topological structure gives
the interconnection relationship among the components from the
viewpoint of communication, but the topological structure does not
specify the exact locations of components and the interconnection
mode.
Trap A type of SNMP message that indicates the occurrence of an event.
This type of message is transmitted to the received through UDP. The
transmission process is not completely reliable.
U
User datagram A TCP/IP standard protocol that allows an application program on
protocol one device to send a datagram to an application program on another.
User Datagram Protocol (UDP) uses IP to deliver datagram. UDP
provides application programs with the unreliable connectionless
packet delivery service. There is a possibility that UDP messages will
be lost, duplicated, delayed, or delivered out of order. The destination
device does not confirm whether a data packet is received.
User interface The space in which users interact with a machine.
V
Variable prefetch A cache prefetch strategy. The size of the data to be prefetched is the
multiple for prefetching multiplied by the length of a read command.
This strategy applies to the applications that require reading data of
variable size in a certain order or to the situations where multiple
subscribers read data concurrently but no fixed prefetch size can be
set, because the amount of pre-read data cannot be judged. An
example is the streaming media demanded by multiple subscribers
who use different bit rates.
vStore A property of SmartTenancy. In Huawei SmartTenancy, a tenant is
called a vStore, which represents a virtual storage system.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Working The controller used by the array LUN to read and write a disk.
controller
Write back A caching technology in which the completion of a write request is
signaled as soon as the data is in cache, and actual writing to non-
volatile media occurs at a later time. Write back includes an inherent
risk that an application will take some action predicated on the write
completion signal, and a system failure before the data is written to
non-volatile media will cause media contents to be inconsistent with
that subsequent action. For this reason, good write back
implementations include mechanisms to preserve cache contents
across system failures (including power failures) and to flush the
cache at system restart time.
Write through A caching technology in which the completion of a write request is
not signaled until data is safely stored on non-volatile media. Write
performance with the write through technology is approximately that
of a non-cached system, but if the data written is also held in cache,
subsequent read performance may be dramatically improved.
Z
Zone In the fiber channel, a collection of the N_Port or the NL_Port which
can communicate with each other in the optical network. Only the
N_Port or the NL_Port in the same partition can communicate with
each other through the optical network.

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide D Acronyms and Abbreviations
D Acronyms and Abbreviations
A
ANSI American National Standards Institute
B
BBU Backup Battery Unit
C
CLI Command Line Interface
E
ESN Equipment Serial Number
F
FC Fiber Channel
FRU Field Replaceable Unit
FTP File Transfer Protocol
G
GUI Graphical User Interface
H
HBA Host Bus Adapter

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800
Maintenance Guide D Acronyms and Abbreviations
I
I/O Input/Output
IP Internet Protocol
IPv4 Internet Protocol version 4
IPv6 Internet Protocol version 6
ISA Instrument Society of America
iSCSI Internet Small Computer Systems Interface
ISO International Organization for Standardization
L
LDAP Lightweight Directory Access Protocol
LUN Logical Unit Number
N
NTP Network Time Protocol
S
SAS Serial Attached SCSI
SMTP Simple Mail Transfer Protocol
SNMP Simple Network Management Protocol
T
TCP/IP Transmission Control Protocol/Internet Protocol
U
UDP User Datagram Protocol
UTC Coordinated Universal Time


OceanStor 5300 V3&amp;5500 V3&amp;5600 V3&amp;5800 V3&amp;6800 V3&amp;6900 V3 Storage System V300R001 Maintenance Guide 06

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

OceanStor 5300 V3&amp;5500 V3&amp;5600 V3&amp;5800 V3&amp;6800 V3&amp;6900 V3 Storage System V300R001 Maintenance Guide 06

Hochgeladen von

Copyright:

Verfügbare Formate

OceanStor 5300 V3&5500 V3&5600 V3&5800

V3&6800 V3&6900 V3 Storage System

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 06 (2016-03-01) Huawei Proprietary and Confidential i

About This Document

This document is intended for:

Added below contents:

Issue 06 (2016-03-01) Huawei Proprietary and Confidential ii

l Reclaiming space of a storage system.

Issue 06 (2016-03-01) Huawei Proprietary and Confidential iii

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

3 Logging In to the DeviceManager..............................................................................................7

Issue 06 (2016-03-01) Huawei Proprietary and Confidential iv

7.5 Replacing an OceanStor SystemReporter Security Certificate.................................................................................... 46

8 Adjusting Storage Resources.................................................................................................... 48

9 Reclaiming Space of a Storage System..................................................................................107

10 Managing Application-Based Storage Resources............................................................. 129

Issue 06 (2016-03-01) Huawei Proprietary and Confidential v

10.1 Managing Microsoft Exchange Instances.................................................................................................................130

11 Managing Basic Information About a Storage System.................................................... 168

Issue 06 (2016-03-01) Huawei Proprietary and Confidential vi

11.3.6 Backing Up an Active License File....................................................................................................................... 179

12 Obtaining System Version Information............................................................................. 181

13 Viewing System Interface Module Information............................................................... 184

14 Checking the Operating Environment of the Storage Device........................................ 197

15 Checking Indicators................................................................................................................ 204

16 Checking the Running Status of the Storage Device....................................................... 235

17 Managing Alarms.................................................................................................................... 247

Issue 06 (2016-03-01) Huawei Proprietary and Confidential vii

17.4 SM Notification Management.................................................................................................................................. 258

18 Monitoring a Storage System................................................................................................ 275

19 Checking the Running Status of Services.......................................................................... 288

20 Collecting Information and Reporting a Fault.................................................................. 304

Issue 06 (2016-03-01) Huawei Proprietary and Confidential viii

20.5 Importing Storage System Configuration Data........................................................................................................ 310

A Alarm Notification Service Configurations........................................................................ 329

B How to Obtain Help................................................................................................................. 334

Issue 06 (2016-03-01) Huawei Proprietary and Confidential ix

1 Introduction to Routine Maintenance

Issue 06 (2016-03-01) Huawei Proprietary and Confidential 1

2 Safety Operation Guide

About This Chapter

2.1 Alarm and Safety Symbols

Issue 06 (2016-03-01) Huawei Proprietary and Confidential 2

2.1 Alarm and Safety Symbols

Table 2-1 Safety symbols stuck on equipment

ESD Protection Symbol

Enclosure Grounding Symbol

System Disk Swap and Install Warning Symbol

Issue 06 (2016-03-01) Huawei Proprietary and Confidential 3

l Use special ESD bags to carry or transport the parts.

2.3 Using Lasers Safely

2.4 Using Fibers Safely

Issue 06 (2016-03-01) Huawei Proprietary and Confidential 4

Cleaning the Fiber Connectors and Optical Interfaces

2.5 Short Circuit

2.6 Operating the Equipment

Issue 06 (2016-03-01) Huawei Proprietary and Confidential 5

Power-on and Power-off

When you perform troubleshooting, be aware of the following precautions:

Issue 06 (2016-03-01) Huawei Proprietary and Confidential 6

3 Logging In to the DeviceManager

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Maintenance Guide 06

OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800 V3&6900 V3 Storage System V300R001 Maintenance Guide 06