Huawei Event Reference

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

V300R002
Event Reference
Issue
04
Date
2015-06-10
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2015. 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://enterprise.huawei.com
Issue 04 (2015-06-10)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

V3 Storage System
Event Reference
About This Document
About This Document
Intended Audience
This document describes the basic knowledge about the events of storage system in terms of
event definition, event level, impact on the system, possible cause, and handling procedure.
This document is intended for:
l
Technical support engineers
Maintenance engineers
Content 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 performance and capabilities of its product line,
Huawei Technologies Co., Ltd. from time to time releases revisions of its hardware and software.
Therefore, some functions described in this manual may not be supported by all revisions of the
software or hardware currently in use. For the most up-to-date information on product features,
refer to your product release notes.
If a product does not function as described in this manual, please contact your Huawei
Technologies Co., Ltd. technical support.
Change History
Changes between document issues are cumulative. The latest document issue contains all the
changes made in earlier issues.
Issue 04 (2015-06-10)
Fourth official release.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
About This Document
New events are included and some events are modified.
Issue 03 (2015-03-13)
Third official release.
Added 5300 V3 and 6800 V3.
Issue 02 (2014-12-25)
Second official release.
New events are included and some events are modified.
Issue 01 (2014-10-30)
Initial official release.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
Contents
About This Document.....................................................................................................................ii
1 Overview.........................................................................................................................................1
2 Troubleshooting Events...............................................................................................................3
2.1 0xF0C90001 License Is About To Expire....................................................................................................................12
2.2 0xF0C90002 License Has Expired...............................................................................................................................12
2.3 0xF0C90003 Invalid License........................................................................................................................................13
2.4 0xF00C90015 Controller Write Cache Is Disabled......................................................................................................14
2.5 0xF0C90006 The System Has Entered Safe Mode......................................................................................................15
2.6 0x100F0C9000C Controller Failed To Be Powered On Again....................................................................................16
2.7 0x100F0C90065 System Engine Is Working In Single Controller State.....................................................................16
2.8 0xF0CE0001 Failed To Monitor A Disk Enclosure.....................................................................................................17
2.9 0xF0CE0002 Disk Enclosure Quantity Exceeds The System Limit............................................................................18
2.10 0xF0CE0004 Failed To Identify An Engine Or Disk Enclosure................................................................................19
2.11 0xF0CE0005 Disk Enclosure Temperature Exceeds The Upper Limit......................................................................20
2.12 0xF0CE000A Disk Enclosure Temperature Is Far Beyond The Upper Limit...........................................................21
2.13 0xF0CE0007 Engine Or Disk Enclosure Temperature Is Below The Lower Limit...................................................22
2.14 0xF0CE0008 Engine Temperature Exceeds The Upper Limit...................................................................................23
2.15 0xF0CE0009 Engine Temperature Is Far Beyond The Upper Limit.........................................................................24
2.16 0xF00CE0015 Failed To Monitor An Engine............................................................................................................25
2.17 0xF00CE0018 Controller Failed To Monitor An Engine Rear Panel........................................................................26
2.18 0xF00CE001D Expansion Ports Are Working At Inconsistent Rates.......................................................................27
2.19 0xF00CE002A Disk Enclosure Is Working In Single Link State..............................................................................27
2.20 0xF0CF0006 Controller Is Removed.........................................................................................................................28
2.21 0xF00CF0014 Failed To Monitor The Controller......................................................................................................29
2.22 0xF0CF0003 Controller Is Faulty...............................................................................................................................30
2.23 0xF0CF0004 Incorrect Controller Memory Capacity................................................................................................30
2.24 0xF0CF0005 Abnormal Communication Between Controllers.................................................................................31
2.25 0x100F0CF0032 Controller Power Failure................................................................................................................32
2.26 0xF00CF0017 Incorrect Connection Between A Controller Port And A Switch Port...............................................33
2.27 0x200F00CF0022 Failed To Start A Controller.........................................................................................................34
2.28 0x100F00CF0027 Controller Restarts........................................................................................................................34
2.29 0x100F00CF002A Controller Cache Failed To Flush Data.......................................................................................35
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
2.30 0x100F00CF0034 A Controller Is Isolated................................................................................................................36

2.31 0xF00CF0035 The System Is Abnormal....................................................................................................................37
2.32 0xF00CF0036 Controller Services Are Abnormal.....................................................................................................37
2.33 0x100F00CF0037 Controller Is About To Restart.....................................................................................................38
2.34 0xF0050001 Expansion Module Is Removed............................................................................................................39
2.35 0xF0050002 Expansion Module Is Not Inserted........................................................................................................39
2.36 0xF0050003 Expansion Module Is Faulty..................................................................................................................40
2.37 0xF00D00014 Abnormal Communication Between Expansion Modules.................................................................41
2.38 0xF00D00016 Expansion Module Is Incorrectly Cabled...........................................................................................42
2.39 0xF0D10001 Management Module Is Removed........................................................................................................42
2.40 0xF0D10002 Management Module Is Faulty.............................................................................................................43
2.41 0xF0D10005 Interface Module Is Removed..............................................................................................................44
2.42 0xF0D10006 Interface Module Is Faulty...................................................................................................................44
2.43 0xF0D10008 Interface Module Is Unrecognizable....................................................................................................45
2.44 0xF0D10009 Interface Module Temperature Exceeds The Upper Limit...................................................................46
2.45 0xF0D1000A Incorrect Removal Of Interface Module..............................................................................................47
2.46 0xF010A0017 The Communication Between Controller And Management Module Is Disconnected.....................48
2.47 0xF00D1001E The System Failed To Monitor An Interface Module........................................................................49
2.48 0xF00A0001 Disk Is Faulty.......................................................................................................................................49
2.49 0xF00A0002 Unrecognizable Disk............................................................................................................................50
2.50 0xF00A0003 Disk Is About To Fail...........................................................................................................................51
2.51 0xF00A0004 Disk Temperature Exceeds The Upper Limit.......................................................................................52
2.52 0xF00A0008 Coffer Disk Is Faulty............................................................................................................................53
2.53 0xF00A000A Coffer Disks Not Found......................................................................................................................54
2.54 0xF000A0015 The System Failed To Monitor A Disk In A Disk Enclosure............................................................55
2.55 0xF00A000D Slow Disk Response............................................................................................................................56
2.56 0xF00A000E Incompatible Disk Model.....................................................................................................................57
2.57 0xF00A000C Disk Is In Single Link State.................................................................................................................58
2.58 0xF00A0006 Disk Has Too Many Bit Error..............................................................................................................58
2.59 0xF000A001A Disk Temperature Is Below The Lower Limit..................................................................................59
2.60 0xF000A004E Coffer Disks Not Found.....................................................................................................................60
2.61 0xF000A004F The Coffer Disk Is Inserted Into An Incorrect Slot............................................................................61
2.62 0xF0170001 Power Module Is Not Inserted...............................................................................................................62
2.63 0xF0170002 Power Module Is Removed...................................................................................................................63
2.64 0xF0170003 Power Module Is Faulty........................................................................................................................64
2.65 0xF0170004 Power Module Temperature Exceeds The Upper Limit........................................................................64
2.66 0xF0170005 Power Module Input Is Abnormal.........................................................................................................65
2.67 0xF00170014 Power Module Has No Input...............................................................................................................66
2.68 0xF00170017 The System Failed To Monitor A Power Module...............................................................................68
2.69 0x100F0170006 Power Module Incompatible...........................................................................................................68
2.70 0x100F0170008 Multi-Vendor Power Modules In The Same Enclosure..................................................................69
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
2.71 0xF0D20002 BBU Module Is Faulty.........................................................................................................................70

2.72 0xF0D20003 BBU Module Reaches Its Expiration Date Or Is Aging.......................................................................71
2.73 0xF0D20007 BBU Module Is About To Expire........................................................................................................71
2.74 0xF0D20004 BBU Module Is Removed....................................................................................................................72
2.75 0xF0D20005 BBU Module Temperature Exceeds The Upper Limit.........................................................................73
2.76 0xF00D2001B BBU Module Temperature Is Below The Lower Limit....................................................................74
2.77 0xF00D20014 The System Failed To Monitor A BBU Module................................................................................75
2.78 0xF0D30001 Fan Module Is Faulty............................................................................................................................76
2.79 0xF0D30002 Fan Module Is Not Inserted..................................................................................................................76
2.80 0xF0D30003 Fan Module Is Removed......................................................................................................................77
2.81 0xF00D30014 The System Failed To Monitor A Fan Module..................................................................................78
2.82 0xF0060002 Expansion Port Link Down...................................................................................................................79
2.83 0xF0060003 Expansion Port Is Faulty.......................................................................................................................80
2.84 0xF0060004 Host Port Link Down............................................................................................................................81
2.85 0xF0060005 Host Port Is Faulty.................................................................................................................................82
2.86 0xF0060006 Expansion Port Partially Damaged........................................................................................................82
2.87 0xF01080014 Expansion Port Has Too Many Bit Errors...........................................................................................83
2.88 0xF0060010 Expansion Port Isolated.........................................................................................................................84
2.89 0xF01080015 Host Port Has Too Many Bit Errors....................................................................................................85
2.90 0xF01080016 PCIE Port Partially Damaged..............................................................................................................86
2.91 0xF01080018 PCIE Port Is Faulty..............................................................................................................................87
2.92 0xF01080019 PCIE Port Disconnected......................................................................................................................87
2.93 0xF0108001A PCIE Port Has Too Many Bit Errors..................................................................................................88
2.94 0xF0060011 Network Port Is Working In Half-Duplex Mode..................................................................................89
2.95 0xF0108001D Port Negotiated Rate Is Smaller Than The Allowed Maximum........................................................90
2.96 0xF01080048 Management Network Port Is Faulty..................................................................................................91
2.97 0xF01080049 Management Network Port Is Disconnected.......................................................................................91
2.98 0xF0EA0003 Port Optical Module Is Faulty..............................................................................................................92
2.99 0xF0EA0004 Port Unavailable Due To Incompatible Optical Module Type............................................................93
2.100 0xF0EA0005 Optical Module Rate Is Inconsistent With That Of Its Port...............................................................94
2.101 0xF00EA0016 Optical Module Temperature Is Below The Lower Limit...............................................................94
2.102 0xF00EA0014 Abnormal Port Link.........................................................................................................................95
2.103 0xF00EA0015 The System Failed To Monitor An Optical Module........................................................................96
2.104 0xF00EA0017 Optical Module Temperature Exceeds The Upper Limit.................................................................97
2.105 0xF00B0001 LUN Is Faulty.....................................................................................................................................98
2.106 0xF00B0002 LUN Has A Medium Error.................................................................................................................99
2.107 0x100F000B0016 Switchover Failure Occurs On The Owning Controller Of A LUN...........................................99
2.108 0xF00B003D Snapshot LUN Is Faulty..................................................................................................................100
2.109 0xF000B0050 LUN Has A Medium Error.............................................................................................................101
2.110 0xF000B0051 LUN Has A Medium Error.............................................................................................................101
2.111 0xF0DB0002 Full LUN Copy Is Faulty.................................................................................................................102
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
2.112 0xF0DC0001 Clone Pair Is Abnormally Interrupted.............................................................................................103

2.113 0xF0DC0002 Clone Is Unavailable........................................................................................................................104
2.114 0xF0DC0003 Clone Pair Is Unavailable................................................................................................................104
2.115 0x100F01C0003 Data On The Primary LUN In The Remote Replication Fails To Be Rolled Back....................105
2.116 0xF00270038 Remote Replication Is Interrupted..................................................................................................106
2.117 0xF00270039 Remote Replication Is Unavailable.................................................................................................107
2.118 0xF0027003A Remote Replication Failed To Synchronize Data Automatically..................................................108
2.119 0x100F0027008B Failed To Roll Back The Secondary LUN In Remote Replication..........................................109
2.120 0xF0DD0001 Remote Replication Consistency Group Is Disconnected...............................................................109
2.121 0xF0DD0002 Remote Replication Consistency Group Is Unavailable.................................................................111
2.122 0xF01C0005 Remote Replication Consistency Group Failed To Synchronize Data Automatically.....................111
2.123 0x100F01B0001 Snapshot Rollback Stopped Unexpectedly.................................................................................112
2.124 0xE02050002 Snapshot Unavailable......................................................................................................................113
2.125 0x200F001B0046 Succeeded In Canceling Snapshot Rollback.............................................................................114
2.126 0x200F001B0047 Failed To Cancel Snapshot Rollback........................................................................................114
2.127 0xF0E10001 Replication Link Is Down.................................................................................................................115
2.128 0xF00E00014 No Backup Links Available............................................................................................................116
2.129 0xF0C90004 CPU Usage Is Too High...................................................................................................................117
2.130 0xF0C90005 Memory Usage Is Too High.............................................................................................................118
2.131 0xF00CF002F Inconsistent Memory Capacities Between Controllers..................................................................118
2.132 0xF010C0014 Number Of Initiators Connected To A Port Exceeds The System Limit.......................................119
2.133 0x100F010C0015 iSCSI Initiator Login Failed.....................................................................................................120
2.134 0x100F010C0030 Number Of Initiators Connected To A Port Exceeds The System Limit.................................121
2.135 0x100F010C0031 Initiator IP Address Is Changed................................................................................................121
2.136 0xF010D0027 BBU Firmware Is Incompatible With Storage Array Software.....................................................122
2.137 0xF010D0028 Interface Module Firmware Is Incompatible With Storage Array Software..................................123
2.138 0xF010D0029 Expansion Module Firmware Is Incompatible With Storage Array Software...............................124
2.139 0x200F010D0018 Failed To Delete A Hot Patch..................................................................................................124
2.140 0x200F010D001B Failed To Start An Upgrade.....................................................................................................125
2.141 0x200F010D001E Failed To Start The Upgrade Of Disk Firmware.....................................................................126
2.142 0x200F010D0021 Failed To Start The Upgrade Of Disk Converter Firmware.....................................................126
2.143 0x200F010D0024 Failed To Start Rollback...........................................................................................................127
2.144 0x100F010D0026 Rollback Failed.........................................................................................................................128
2.145 0x100F010D0027 Upgrade Failed.........................................................................................................................128
2.146 0xF00150019 Host Is Not Redundantly Connected To Storage Arrays................................................................129
2.147 0xF0015001A Link Between A Host And Storage Array Is Down.......................................................................130
2.148 0xF0015001B Link Between A Host And Storage Array Is Unstable...................................................................131
2.149 0x100F0015001C Ultrapath Is Not Installed Or Ultrapath Version Outdated.......................................................132
2.150 0xF0015001D Ultrapath Incompatible With Storage Array Software...................................................................133
2.151 0x100F00150036 Data Sent To A Storage Array Port By The Host Failed To Be Verified.................................134
2.152 0xF00310004 The Space That Stores Event Logs Is To Be Used Up....................................................................135
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
2.153 0xD80001 Storage Pool Remaining Capacity Is Insufficient.................................................................................135

2.154 0xD80002 Storage Pool Capacity Is About To Be Used Up..................................................................................136
2.155 0x10A0001 Disk Domain Is Degraded..................................................................................................................137
2.156 0x10A0002 Disk Domain Is Faulty........................................................................................................................138
2.157 0x10A0003 Disk Domain Is Offline......................................................................................................................139
2.158 0x10A0005 Hot Spare Capacity Of The Disk Domain Is Insufficient...................................................................139
2.159 0x10A0006 Inconsistent Disk Domain Disk Types...............................................................................................140
2.160 0x10A0007 Number Of Disks In A Disk Domain Does Not Meet Hot Spare Requirements...............................141
2.161 0x10A0008 A Disk Is Removed From A Disk Domain.........................................................................................142
2.162 0x1000010A000B The Disk Domain Reconstruction Failed.................................................................................142
2.163 0x1000010A000E Precopy Failed..........................................................................................................................143
2.164 0x1000010A0011 Data Balancing Failed...............................................................................................................144
2.165 0x10A001C Disk Domain Member Disk Is Inserted Into An Incorrect Slot.........................................................145
2.166 0x10C000B Controller Write Cache Is Disabled...................................................................................................145
2.167 0x10C000C Write Cache For A Cache Partition Is Disabled................................................................................146
2.168 0xFD0008 LUN Migration Is Faulty......................................................................................................................147
2.169 0xF00CE002B From An Expansion Port, Disk Enclosures And High-Density Disk Enclosures Are Mix-Connected
..........................................................................................................................................................................................148
2.170 0xF000B0063 External LUN Has Links To Only One Controller.........................................................................149
2.171 0xF000B0064 External LUN Offline.....................................................................................................................150
2.172 0xF000B0065 External LUN Faulty......................................................................................................................151
2.173 0xF000B0066 External LUN Downsized...............................................................................................................152
2.174 0xF000B0052 Incompatible Heterogeneous Array Connected To The System....................................................152
2.175 0xF000B005D FC Link Of Heterogeneous Array Disconnected...........................................................................153
2.176 0xF000B0060 iSCSI Link Of Heterogeneous Array Disconnected.......................................................................154
2.177 0xF000B0061 FC Link Of Heterogeneous Array Faulty.......................................................................................155
2.178 0xF000B0062 iSCSI Link Of Heterogeneous Array Faulty..................................................................................156
2.179 0x200F000A005B The Hard Disk Is Isolated........................................................................................................157
2.180 0xF00280045 File System Is Faulty.......................................................................................................................158
2.181 0xF00280046 File System Has A Medium Error...................................................................................................158
2.182 0xF00280047 Remaining Capacity In A File System Is Insufficient.....................................................................159
2.183 0xF00280048 Used Resource Of A File System Quota Exceeds The Soft Quota.................................................160
2.184 0xF00280049 File System Has A Checksum Error................................................................................................160
2.185 0x100F0028004A File System Has A Memory Allocation Error..........................................................................161
2.186 0x10A0021 Failed To Add The New Disk To The Disk Domain..........................................................................162
2.187 0x10A0020 A New Disk Fails to Be Added To The Disk Domain.......................................................................163
2.188 0xF4045000E Adding To An AD Domain Fails....................................................................................................164
2.189 0x200F4045000F No Domain Controller Is Available..........................................................................................165
2.190 0xF40020001 The Ndmp Service Process Is Abnormal........................................................................................166
2.191 0xF40020002 A Service Port Conflicts..................................................................................................................167
2.192 0xF0D30004 Fan Module Is Faulty........................................................................................................................167
2.193 0xF00D1001F Management Module Is Faulty......................................................................................................168
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
2.194 0xF00D10020 Interface Module Is Faulty.............................................................................................................169

2.195 0xF00170018 The Power Module Is Incompatible With The Storage System......................................................170
2.196 0xF00EA0018 The System Failed To Monitor An Optical/Electrical Module......................................................170
2.197 0x200F0D1000D The System Failed To Power Off An Interface Module............................................................171
2.198 0x200F0D10010 The System Failed To Power On An Interface Module.............................................................172
2.199 0x200F00D10017 The System Failed to Power Off An Interface Module............................................................173
2.200 0x200F00D1001C The System Failed to Power On An Interface Module............................................................173
2.201 0x200F00C90088 Succeeded In Deleting All Configurations Of System.............................................................174
2.202 0x200F00C90089 Failed To Delete All Configurations Of System......................................................................175
2.203 0xF00CA0008 The Super Administrator Needs To Review User Account Information.......................................176
2.204 0xF40450029 No LDAP/NIS Server Is Available.................................................................................................176
2.205 0xF02470010 Mirror Copy Is Abnormally Interrupted..........................................................................................177
2.206 0xF02470011 Mirror Copy Is Unavailable............................................................................................................178
2.207 0xF032C0001 The SSH Service Is Abnormal........................................................................................................179
2.208 0xF032C0002 The FTP Service Is Abnormal........................................................................................................180
2.209 0xF032C0003 NTP Time Synchronization Is Abnormal.......................................................................................180
2.210 0xF032C0004 The Network Protocol Stack Of A Controller Is Abnormal...........................................................181
2.211 0xF032C0005 The Process CPU Usage Is Too High.............................................................................................182
2.212 0xF032C0006 The Process Memory Usage Is Too High.......................................................................................182
2.213 0xF032C0007 A Directory Is Oversized................................................................................................................183
2.214 0xF032C0008 Excessive Files Exist In A Directory..............................................................................................184
2.215 0x200F00CF003A The Heartbeat Connection Between A Controller And A Management Module Is Interrupted
..........................................................................................................................................................................................184
2.216 0xF00D10011 The PCIe Channel Between An Interface Module And A Controller Is Abnormal.......................185
2.217 0xF000A005F Slow Disk Response.......................................................................................................................186
2.218 0x200F010D0029 Failed To Start Dispatch Upgrade Package..............................................................................187
2.219 0x100F010D0031 Dispatch Upgrade Package Failed............................................................................................188
2.220 0xF00D10012 Interface Module Is Inserted Into An Incorrect Slot.......................................................................189
2.221 0xF00280074 File System Metadata Is Damaged..................................................................................................189
2.222 0xF00280075 Write Protection Is Enabled For The File System...........................................................................190
2.223 0xF00280076 Files Or Directories Are Damaged..................................................................................................191
2.224 0xF000B0102 External LUN Is Changed To Command Device...........................................................................191
2.225 0xF00D10013 Some Statuses Of A Management Module Cannot Be Monitored.................................................192
2.226 0xF00CF004A Some Statuses Of A Controller Cannot Be Monitored..................................................................193
2.227 0xF01050017 Switch Temperature Is Below The Lower Limit.............................................................................194
2.228 0xF0105001E Switch Management Network Port Is Faulty..................................................................................195
2.229 0xF0105001F Switch Port Is Faulty.......................................................................................................................195
2.230 0xF01050022 Switch Port Optical Module Is Faulty.............................................................................................196
2.231 0xF01050024 Switch Port Negotiated Rate Is Smaller Than The Allowed Maximum.........................................197
2.232 0xF01050025 Switch Optical Module Temperature Is Below The Lower Limit..................................................198
2.233 0xF01050026 Link To A Switch Port Is Abnormal...............................................................................................199
2.234 0xF01050027 Failed To Monitor A Switch Optical Module.................................................................................199
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
2.235 0xF01050029 Switch Optical Module Temperature Is Too High..........................................................................200

2.236 0xDA0005 A Member Disk Of A SmartCache Pool Gets A Fault........................................................................201
2.237 0x200F406E0013 An Ndmp Backup Task Fails....................................................................................................202
2.238 0xF406E0014 An Ndmp Recovery Task Fails.......................................................................................................203
2.239 0xF406E0015 Ndmp Authentication Fails, And The Ip Address Of Backup Software Is Locked........................204
2.240 0xF00270130 A Remote Replication Fails To Synchronize Data Automatically..................................................205
2.241 0xF00270112 A Remote Replication Is Unavailable.............................................................................................206
2.242 0xF00270113 A Remote Replication Is Abnormally Interrupted..........................................................................206
2.243 0xF00CF0056 Only One Cluster Link Is Available...............................................................................................208
2.244 0xF000A0084 The Disk Is Rejected By The System.............................................................................................208
2.245 0x1FFFFFFFFFFFFFFC Testing The Alarm Function..........................................................................................209
2.246 0xF00C9013D IP Address Conflict........................................................................................................................210
2.247 0xF010D0032 The Management Module Firmware Is Incompatible With Storage Array Software....................210
2.248 0xF01060060 Cache Partition Failed To Process Received I/O............................................................................211
2.249 0x100F01060063 Controller Is Overloaded...........................................................................................................212
2.250 0xF00D00017 Failed To Synchronize The Firmware Version Of An Expansion Module....................................213
2.251 0xF00CF0059 Heartbeat Connection Between A Controller And A Management Module Is Interrupted...........214
2.252 0xF00270137 Remote Replication Is Automatically Split.....................................................................................214
2.253 0xF0DD0004 Remote Replication Consistency Group Is Automatically Split.....................................................215
2.254 0xF40020005 Number Of NAS Client Connections Of A Controller Reaches The Upper Limit.........................216
2.255 0xF00D80119 Storage Pool Remaining Capacity Is Insufficient..........................................................................217
2.256 0xF00D80120 Storage Pool Capacity Is About To Be Used Up...........................................................................218
2.257 0xF01060043 Failed To Reach The Control Objective Of SmartQoS...................................................................218
2.258 0xF40020006 Number Of File Information Items To Be Backed Up Reaches The Upper Limit.........................219
2.259 0xF40440017 Controller Is Disconnected From An LDAP/NIS Server................................................................220
2.260 0x100F03300072 Failed To Restore A Virtual Machine.......................................................................................221
2.261 0x100F03300073 Failed To Shut Down A Virtual Machine.................................................................................222
2.262 0x100F03300074 Incomplete Virtual Machine Creation.......................................................................................222
2.263 0xF00280112 Number Of Files In A File System Is About To Exceed The Upper Limit....................................223
2.264 0xF00280113 Number Of Files In A Directory Of A File System Is About To Exceed The Upper Limit...........224
2.265 0xF00CF005C Number Of Opened Files On A Controller Is About To Exceed The Upper Limit.......................225
A How to Obtain Help.................................................................................................................226

A.1 Preparations For Contacting Huawei.........................................................................................................................227
A.1.1 Collecting Troubleshooting Information................................................................................................................227
A.1.2 Making Debugging Preparations............................................................................................................................227
A.2 How to Use the Document.........................................................................................................................................227
A.3 How to Obtain Help from Website............................................................................................................................227
A.4 Ways to Contact Huawei...........................................................................................................................................228
B Glossary......................................................................................................................................229
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contents
C Acronyms and Abbreviations................................................................................................241
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1 Overview
Overview
This chapter describes the event levels and event signal flows.
Event Level
An event level indicates the severity of the event to the system services. The event level is
displayed on the DeviceManager interface and can be classified into the following levels:
l
Critical
This level indicates that a fault has caused service interruption or device failure. Recovery
measures should be taken immediately.
Major
This level indicates that a fault has certain impact on the device or system performance.
Measures should be taken immediately to prevent more serious faults. All hardware faults
are of the level.
Warning
This level indicates that a fault has no impact on the device. The system detects a potential
or an imminent fault that is about to affect the services.
Event Signal Flow

If the storage system is faulty, the module in which the fault occurs reports the fault to the service
control module and alarm module. The service control module and alarm module analyze the
fault information. Then the service control module reports the fault information to the underlying
module for further handling. The alarm module reports the fault information to the device alarm
indicator to generate visual alarm, and to the DeviceManager through the maintenance interface
to display the alarm status and cause.
Figure 1-1 shows the event signal flow figure of the storage system.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1 Overview
Figure 1-1 Event signal flow figure

Underlying module
process
Service control module
Module fault
Alarm indicator
informs
Alarm module
Software interface
displays
(1) Indicates that a module is faulty, and the fault information is reported to the service control
module and alarm module.
(2) Indicates that the service control module and alarm module analyze the fault information,
and then respectively report it. Herein:
l
The service control module reports the fault information to the underlying module for
further handling.
The alarm module reports the fault information to the device alarm indicator to generate a
visual alarm, and to the DeviceManager through the maintenance interface to display the
alarm status and cause.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2 Troubleshooting Events
Troubleshooting Events
About This Chapter

This chapter describes the information about troubleshooting events, including event
description, event attribute, impact on system, possible causes, and handling procedure.
2.1 0xF0C90001 License Is About To Expire
2.2 0xF0C90002 License Has Expired
2.3 0xF0C90003 Invalid License
2.4 0xF00C90015 Controller Write Cache Is Disabled
2.5 0xF0C90006 The System Has Entered Safe Mode
2.6 0x100F0C9000C Controller Failed To Be Powered On Again
2.7 0x100F0C90065 System Engine Is Working In Single Controller State
2.8 0xF0CE0001 Failed To Monitor A Disk Enclosure
2.9 0xF0CE0002 Disk Enclosure Quantity Exceeds The System Limit
2.10 0xF0CE0004 Failed To Identify An Engine Or Disk Enclosure
2.11 0xF0CE0005 Disk Enclosure Temperature Exceeds The Upper Limit
2.12 0xF0CE000A Disk Enclosure Temperature Is Far Beyond The Upper Limit
2.13 0xF0CE0007 Engine Or Disk Enclosure Temperature Is Below The Lower Limit
2.14 0xF0CE0008 Engine Temperature Exceeds The Upper Limit
2.15 0xF0CE0009 Engine Temperature Is Far Beyond The Upper Limit
2.16 0xF00CE0015 Failed To Monitor An Engine
2.17 0xF00CE0018 Controller Failed To Monitor An Engine Rear Panel
2.18 0xF00CE001D Expansion Ports Are Working At Inconsistent Rates
2.19 0xF00CE002A Disk Enclosure Is Working In Single Link State
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.20 0xF0CF0006 Controller Is Removed

2.21 0xF00CF0014 Failed To Monitor The Controller
2.22 0xF0CF0003 Controller Is Faulty
2.23 0xF0CF0004 Incorrect Controller Memory Capacity
2.24 0xF0CF0005 Abnormal Communication Between Controllers
2.25 0x100F0CF0032 Controller Power Failure
2.26 0xF00CF0017 Incorrect Connection Between A Controller Port And A Switch Port
2.27 0x200F00CF0022 Failed To Start A Controller
2.28 0x100F00CF0027 Controller Restarts
2.29 0x100F00CF002A Controller Cache Failed To Flush Data
2.30 0x100F00CF0034 A Controller Is Isolated
2.31 0xF00CF0035 The System Is Abnormal
2.32 0xF00CF0036 Controller Services Are Abnormal
2.33 0x100F00CF0037 Controller Is About To Restart
2.34 0xF0050001 Expansion Module Is Removed
2.35 0xF0050002 Expansion Module Is Not Inserted
2.36 0xF0050003 Expansion Module Is Faulty
2.37 0xF00D00014 Abnormal Communication Between Expansion Modules
2.38 0xF00D00016 Expansion Module Is Incorrectly Cabled
2.39 0xF0D10001 Management Module Is Removed
2.40 0xF0D10002 Management Module Is Faulty
2.41 0xF0D10005 Interface Module Is Removed
2.42 0xF0D10006 Interface Module Is Faulty
2.43 0xF0D10008 Interface Module Is Unrecognizable
2.44 0xF0D10009 Interface Module Temperature Exceeds The Upper Limit
2.45 0xF0D1000A Incorrect Removal Of Interface Module
2.46 0xF010A0017 The Communication Between Controller And Management Module Is
Disconnected
2.47 0xF00D1001E The System Failed To Monitor An Interface Module
2.48 0xF00A0001 Disk Is Faulty
2.49 0xF00A0002 Unrecognizable Disk
2.50 0xF00A0003 Disk Is About To Fail
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.51 0xF00A0004 Disk Temperature Exceeds The Upper Limit

2.52 0xF00A0008 Coffer Disk Is Faulty
2.53 0xF00A000A Coffer Disks Not Found
2.54 0xF000A0015 The System Failed To Monitor A Disk In A Disk Enclosure
2.55 0xF00A000D Slow Disk Response
2.56 0xF00A000E Incompatible Disk Model
2.57 0xF00A000C Disk Is In Single Link State
2.58 0xF00A0006 Disk Has Too Many Bit Error
2.59 0xF000A001A Disk Temperature Is Below The Lower Limit
2.60 0xF000A004E Coffer Disks Not Found
2.61 0xF000A004F The Coffer Disk Is Inserted Into An Incorrect Slot
2.62 0xF0170001 Power Module Is Not Inserted
2.63 0xF0170002 Power Module Is Removed
2.64 0xF0170003 Power Module Is Faulty
2.65 0xF0170004 Power Module Temperature Exceeds The Upper Limit
2.66 0xF0170005 Power Module Input Is Abnormal
2.67 0xF00170014 Power Module Has No Input
2.68 0xF00170017 The System Failed To Monitor A Power Module
2.69 0x100F0170006 Power Module Incompatible
2.70 0x100F0170008 Multi-Vendor Power Modules In The Same Enclosure
2.71 0xF0D20002 BBU Module Is Faulty
2.72 0xF0D20003 BBU Module Reaches Its Expiration Date Or Is Aging
2.73 0xF0D20007 BBU Module Is About To Expire
2.74 0xF0D20004 BBU Module Is Removed
2.75 0xF0D20005 BBU Module Temperature Exceeds The Upper Limit
2.76 0xF00D2001B BBU Module Temperature Is Below The Lower Limit
2.77 0xF00D20014 The System Failed To Monitor A BBU Module
2.78 0xF0D30001 Fan Module Is Faulty
2.79 0xF0D30002 Fan Module Is Not Inserted
2.80 0xF0D30003 Fan Module Is Removed
2.81 0xF00D30014 The System Failed To Monitor A Fan Module
2.82 0xF0060002 Expansion Port Link Down
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.83 0xF0060003 Expansion Port Is Faulty

2.84 0xF0060004 Host Port Link Down
2.85 0xF0060005 Host Port Is Faulty
2.86 0xF0060006 Expansion Port Partially Damaged
2.87 0xF01080014 Expansion Port Has Too Many Bit Errors
2.88 0xF0060010 Expansion Port Isolated
2.89 0xF01080015 Host Port Has Too Many Bit Errors
2.90 0xF01080016 PCIE Port Partially Damaged
2.91 0xF01080018 PCIE Port Is Faulty
2.92 0xF01080019 PCIE Port Disconnected
2.93 0xF0108001A PCIE Port Has Too Many Bit Errors
2.94 0xF0060011 Network Port Is Working In Half-Duplex Mode
2.95 0xF0108001D Port Negotiated Rate Is Smaller Than The Allowed Maximum
2.96 0xF01080048 Management Network Port Is Faulty
2.97 0xF01080049 Management Network Port Is Disconnected
2.98 0xF0EA0003 Port Optical Module Is Faulty
2.99 0xF0EA0004 Port Unavailable Due To Incompatible Optical Module Type
2.100 0xF0EA0005 Optical Module Rate Is Inconsistent With That Of Its Port
2.101 0xF00EA0016 Optical Module Temperature Is Below The Lower Limit
2.102 0xF00EA0014 Abnormal Port Link
2.103 0xF00EA0015 The System Failed To Monitor An Optical Module
2.104 0xF00EA0017 Optical Module Temperature Exceeds The Upper Limit
2.105 0xF00B0001 LUN Is Faulty
2.106 0xF00B0002 LUN Has A Medium Error
2.107 0x100F000B0016 Switchover Failure Occurs On The Owning Controller Of A LUN
2.108 0xF00B003D Snapshot LUN Is Faulty
2.111 0xF0DB0002 Full LUN Copy Is Faulty
2.112 0xF0DC0001 Clone Pair Is Abnormally Interrupted
2.113 0xF0DC0002 Clone Is Unavailable
2.114 0xF0DC0003 Clone Pair Is Unavailable
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.115 0x100F01C0003 Data On The Primary LUN In The Remote Replication Fails To Be
Rolled Back
2.116 0xF00270038 Remote Replication Is Interrupted
2.117 0xF00270039 Remote Replication Is Unavailable
2.118 0xF0027003A Remote Replication Failed To Synchronize Data Automatically
2.119 0x100F0027008B Failed To Roll Back The Secondary LUN In Remote Replication
2.120 0xF0DD0001 Remote Replication Consistency Group Is Disconnected
2.121 0xF0DD0002 Remote Replication Consistency Group Is Unavailable
2.122 0xF01C0005 Remote Replication Consistency Group Failed To Synchronize Data
Automatically
2.123 0x100F01B0001 Snapshot Rollback Stopped Unexpectedly
2.124 0xE02050002 Snapshot Unavailable
2.125 0x200F001B0046 Succeeded In Canceling Snapshot Rollback
2.126 0x200F001B0047 Failed To Cancel Snapshot Rollback
2.127 0xF0E10001 Replication Link Is Down
2.128 0xF00E00014 No Backup Links Available
2.129 0xF0C90004 CPU Usage Is Too High
2.130 0xF0C90005 Memory Usage Is Too High
2.131 0xF00CF002F Inconsistent Memory Capacities Between Controllers
2.132 0xF010C0014 Number Of Initiators Connected To A Port Exceeds The System Limit
2.133 0x100F010C0015 iSCSI Initiator Login Failed
2.134 0x100F010C0030 Number Of Initiators Connected To A Port Exceeds The System Limit
2.135 0x100F010C0031 Initiator IP Address Is Changed
2.136 0xF010D0027 BBU Firmware Is Incompatible With Storage Array Software
2.137 0xF010D0028 Interface Module Firmware Is Incompatible With Storage Array Software
2.138 0xF010D0029 Expansion Module Firmware Is Incompatible With Storage Array Software
2.139 0x200F010D0018 Failed To Delete A Hot Patch
2.140 0x200F010D001B Failed To Start An Upgrade
2.141 0x200F010D001E Failed To Start The Upgrade Of Disk Firmware
2.142 0x200F010D0021 Failed To Start The Upgrade Of Disk Converter Firmware
2.143 0x200F010D0024 Failed To Start Rollback
2.144 0x100F010D0026 Rollback Failed
2.145 0x100F010D0027 Upgrade Failed
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.146 0xF00150019 Host Is Not Redundantly Connected To Storage Arrays

2.147 0xF0015001A Link Between A Host And Storage Array Is Down
2.148 0xF0015001B Link Between A Host And Storage Array Is Unstable
2.149 0x100F0015001C Ultrapath Is Not Installed Or Ultrapath Version Outdated
2.150 0xF0015001D Ultrapath Incompatible With Storage Array Software
2.151 0x100F00150036 Data Sent To A Storage Array Port By The Host Failed To Be Verified
2.152 0xF00310004 The Space That Stores Event Logs Is To Be Used Up
2.153 0xD80001 Storage Pool Remaining Capacity Is Insufficient
2.154 0xD80002 Storage Pool Capacity Is About To Be Used Up
2.155 0x10A0001 Disk Domain Is Degraded
2.156 0x10A0002 Disk Domain Is Faulty
2.157 0x10A0003 Disk Domain Is Offline
2.158 0x10A0005 Hot Spare Capacity Of The Disk Domain Is Insufficient
2.159 0x10A0006 Inconsistent Disk Domain Disk Types
2.160 0x10A0007 Number Of Disks In A Disk Domain Does Not Meet Hot Spare Requirements
2.161 0x10A0008 A Disk Is Removed From A Disk Domain
2.162 0x1000010A000B The Disk Domain Reconstruction Failed
2.163 0x1000010A000E Precopy Failed
2.164 0x1000010A0011 Data Balancing Failed
2.165 0x10A001C Disk Domain Member Disk Is Inserted Into An Incorrect Slot
2.166 0x10C000B Controller Write Cache Is Disabled
2.167 0x10C000C Write Cache For A Cache Partition Is Disabled
2.168 0xFD0008 LUN Migration Is Faulty
2.169 0xF00CE002B From An Expansion Port, Disk Enclosures And High-Density Disk
Enclosures Are Mix-Connected
2.170 0xF000B0063 External LUN Has Links To Only One Controller
2.171 0xF000B0064 External LUN Offline
2.172 0xF000B0065 External LUN Faulty
2.173 0xF000B0066 External LUN Downsized
2.174 0xF000B0052 Incompatible Heterogeneous Array Connected To The System
2.175 0xF000B005D FC Link Of Heterogeneous Array Disconnected
2.176 0xF000B0060 iSCSI Link Of Heterogeneous Array Disconnected
2.177 0xF000B0061 FC Link Of Heterogeneous Array Faulty
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.178 0xF000B0062 iSCSI Link Of Heterogeneous Array Faulty

2.179 0x200F000A005B The Hard Disk Is Isolated
2.180 0xF00280045 File System Is Faulty
2.181 0xF00280046 File System Has A Medium Error
2.182 0xF00280047 Remaining Capacity In A File System Is Insufficient
2.183 0xF00280048 Used Resource Of A File System Quota Exceeds The Soft Quota
2.184 0xF00280049 File System Has A Checksum Error
2.185 0x100F0028004A File System Has A Memory Allocation Error
2.186 0x10A0021 Failed To Add The New Disk To The Disk Domain
2.187 0x10A0020 A New Disk Fails to Be Added To The Disk Domain
2.188 0xF4045000E Adding To An AD Domain Fails
2.189 0x200F4045000F No Domain Controller Is Available
2.190 0xF40020001 The Ndmp Service Process Is Abnormal
2.191 0xF40020002 A Service Port Conflicts
2.193 0xF00D1001F Management Module Is Faulty
2.195 0xF00170018 The Power Module Is Incompatible With The Storage System
2.196 0xF00EA0018 The System Failed To Monitor An Optical/Electrical Module
2.197 0x200F0D1000D The System Failed To Power Off An Interface Module
2.198 0x200F0D10010 The System Failed To Power On An Interface Module
2.199 0x200F00D10017 The System Failed to Power Off An Interface Module
2.200 0x200F00D1001C The System Failed to Power On An Interface Module
2.201 0x200F00C90088 Succeeded In Deleting All Configurations Of System
2.202 0x200F00C90089 Failed To Delete All Configurations Of System
2.203 0xF00CA0008 The Super Administrator Needs To Review User Account Information
2.204 0xF40450029 No LDAP/NIS Server Is Available
2.205 0xF02470010 Mirror Copy Is Abnormally Interrupted
2.206 0xF02470011 Mirror Copy Is Unavailable
2.207 0xF032C0001 The SSH Service Is Abnormal
2.208 0xF032C0002 The FTP Service Is Abnormal
2.209 0xF032C0003 NTP Time Synchronization Is Abnormal
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.210 0xF032C0004 The Network Protocol Stack Of A Controller Is Abnormal

2.211 0xF032C0005 The Process CPU Usage Is Too High
2.212 0xF032C0006 The Process Memory Usage Is Too High
2.213 0xF032C0007 A Directory Is Oversized
2.214 0xF032C0008 Excessive Files Exist In A Directory
2.215 0x200F00CF003A The Heartbeat Connection Between A Controller And A Management
Module Is Interrupted
2.216 0xF00D10011 The PCIe Channel Between An Interface Module And A Controller Is
Abnormal
2.217 0xF000A005F Slow Disk Response
2.218 0x200F010D0029 Failed To Start Dispatch Upgrade Package
2.219 0x100F010D0031 Dispatch Upgrade Package Failed
2.220 0xF00D10012 Interface Module Is Inserted Into An Incorrect Slot
2.221 0xF00280074 File System Metadata Is Damaged
2.222 0xF00280075 Write Protection Is Enabled For The File System
2.223 0xF00280076 Files Or Directories Are Damaged.
2.224 0xF000B0102 External LUN Is Changed To Command Device
2.225 0xF00D10013 Some Statuses Of A Management Module Cannot Be Monitored
2.226 0xF00CF004A Some Statuses Of A Controller Cannot Be Monitored
2.227 0xF01050017 Switch Temperature Is Below The Lower Limit
2.228 0xF0105001E Switch Management Network Port Is Faulty
2.229 0xF0105001F Switch Port Is Faulty
2.230 0xF01050022 Switch Port Optical Module Is Faulty
2.231 0xF01050024 Switch Port Negotiated Rate Is Smaller Than The Allowed Maximum
2.232 0xF01050025 Switch Optical Module Temperature Is Below The Lower Limit
2.233 0xF01050026 Link To A Switch Port Is Abnormal
2.234 0xF01050027 Failed To Monitor A Switch Optical Module
2.235 0xF01050029 Switch Optical Module Temperature Is Too High
2.236 0xDA0005 A Member Disk Of A SmartCache Pool Gets A Fault
2.237 0x200F406E0013 An Ndmp Backup Task Fails
2.238 0xF406E0014 An Ndmp Recovery Task Fails
2.239 0xF406E0015 Ndmp Authentication Fails, And The Ip Address Of Backup Software Is
Locked
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.240 0xF00270130 A Remote Replication Fails To Synchronize Data Automatically

2.241 0xF00270112 A Remote Replication Is Unavailable
2.242 0xF00270113 A Remote Replication Is Abnormally Interrupted
2.243 0xF00CF0056 Only One Cluster Link Is Available
2.244 0xF000A0084 The Disk Is Rejected By The System
2.245 0x1FFFFFFFFFFFFFFC Testing The Alarm Function
2.246 0xF00C9013D IP Address Conflict
2.247 0xF010D0032 The Management Module Firmware Is Incompatible With Storage Array
Software
2.248 0xF01060060 Cache Partition Failed To Process Received I/O
2.249 0x100F01060063 Controller Is Overloaded
2.250 0xF00D00017 Failed To Synchronize The Firmware Version Of An Expansion Module
2.251 0xF00CF0059 Heartbeat Connection Between A Controller And A Management Module
Is Interrupted
2.252 0xF00270137 Remote Replication Is Automatically Split
2.253 0xF0DD0004 Remote Replication Consistency Group Is Automatically Split
2.254 0xF40020005 Number Of NAS Client Connections Of A Controller Reaches The Upper
Limit
2.255 0xF00D80119 Storage Pool Remaining Capacity Is Insufficient
2.256 0xF00D80120 Storage Pool Capacity Is About To Be Used Up
2.257 0xF01060043 Failed To Reach The Control Objective Of SmartQoS
2.258 0xF40020006 Number Of File Information Items To Be Backed Up Reaches The Upper
Limit
2.259 0xF40440017 Controller Is Disconnected From An LDAP/NIS Server
2.260 0x100F03300072 Failed To Restore A Virtual Machine
2.261 0x100F03300073 Failed To Shut Down A Virtual Machine
2.262 0x100F03300074 Incomplete Virtual Machine Creation
2.263 0xF00280112 Number Of Files In A File System Is About To Exceed The Upper Limit
2.264 0xF00280113 Number Of Files In A Directory Of A File System Is About To Exceed The
Upper Limit
2.265 0xF00CF005C Number Of Opened Files On A Controller Is About To Exceed The Upper
Limit
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.1 0xF0C90001 License Is About To Expire

Description
Feature license is about to expire. You need to purchase required license.
Attribute
ID
Event Level
Automatically Cleared
0xF0C90001
Warning
Yes
Impact on the System

A value-added feature is unavailable after its license expires.
Possible Causes
N/A.
Procedure
Purchase and import required license files.
----End
Related Information
None
2.2 0xF0C90002 License Has Expired

Description
Feature license has expired. You need to purchase required license.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0C90002
Major
Yes

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

V3 Storage System
Event Reference

After the license of a feature expires, the feature is for trial use only and will become invalid
two months later.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.3 0xF0C90003 Invalid License

Description
Feature license is invalid. You need to purchase required license.
Attribute
ID
Event Level
0xF0C90003
Critical
Yes

The value-added feature is unavailable after its license becomes invalid.
Possible Causes
N/A.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.4 0xF00C90015 Controller Write Cache Is Disabled

Description
Write cache of a controller is disabled.
Attribute
ID
Event Level
0xF00C90015
Major
Yes

System write performance may be compromised.
Possible Causes
l
Power modules are faulty.
BBU modules are faulty.
Fan modules are faulty.
Controllers are faulty.
The temperature is too high.
Disk or disk enclosures are faulty.
Procedure
Step 1 Check whether alarms are generated indicating power module faults.
1.
If yes, replace the faulty power modules. If alarm Controller Write Cache Is Disabled
persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated indicating BBU module faults.
1.
If yes, replace the faulty BBU modules. If alarm Controller Write Cache Is Disabled
persists=>Step 3.
2.
If no=>Step 3.
Step 3 Check whether alarms are generated indicating fan module faults.
1.
If yes, replace the faulty fan modules. If alarm Controller Write Cache Is Disabled
persists=>Step 4.
2.
If no=>Step 4.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Step 4 Check whether alarms are generated indicating controller faults.

1.
If yes, replace the faulty controllers. If alarm Controller Write Cache Is Disabled
persists=>Step 5.
2.
If no=>Step 5.
Step 5 Check whether the temperature is higher than the system limit.
1.
If yes, lower the existing air conditioners temperature or add more air conditioners. If alarm
Controller Write Cache Is Disabled persists=>Step 6.
2.
If no=>Step 6.
Step 6 Check whether alarms are generated indicating disk or disk enclosure faults.
1.
If yes, replace the faulty disks or disk enclosures. If alarm Controller Write Cache Is
Disabled persists=>Step 7.
2.
If no=>Step 7.
Step 7 Collect related information and contact technical support engineers.

----End
Related Information
None
2.5 0xF0C90006 The System Has Entered Safe Mode

Description
An abnormal controller startup causes the system to enter safe mode.
Attribute
ID
Event Level
0xF0C90006
Critical
Yes

The system cannot provide services.
Possible Causes
The system fails to be powered on.
Procedure
Collect related information and contact technical support engineers.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.6 0x100F0C9000C Controller Failed To Be Powered On

Again
Description
A controller failed to be powered on after being recovered from a fault.
Attribute
ID
Event Level
0x100F0C9000C
Major
Yes

The storage system cannot work correctly.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.7 0x100F0C90065 System Engine Is Working In Single

Controller State
Description
An engine is working in single controller state.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x100F0C90065
Major
Yes

The I/O performance of the storage system may deteriorate.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.8 0xF0CE0001 Failed To Monitor A Disk Enclosure

Description
A disk enclosure fails to be monitored.
Attribute
ID
Event Level
0xF0CE0001
Critical
Yes

The storage system cannot report disk enclosure faults, causing fault rectification to be delayed.
Possible Causes
l
The disk enclosure is powered off.
Expansion cables are removed or damaged.
Expansion modules are faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Expansion modules are removed.
Procedure
Step 1 Check the disk enclosure.
1.
If any power cable of the disk enclosure is not removed, insert the power cable and power
on the disk enclosure. If the alarm persists=>Step 1.2.
2.
If any power supply of the disk enclosure is faulty, replace the power supply and power on
the disk enclosure. If the alarm persists=>Step 2.
3.
If all power supplies of the disk enclosure are normal=>Step 2.
Step 2 Check expansion cables.

1.
If any expansion cable is removed, reinsert it. If the alarm persists=>Step 2.2.
2.
Replace the expansion cable. If the alarm persists=>Step 3.
Step 3 Check whether any expansion module is removed.

1.
If yes, reinsert the expansion module. If the alarm persists=>Step 4.
2.
If no=>Step 4.
Step 4 Check whether alarms are generated indicating expansion module faults.
1.
If yes, replace the faulty expansion modules. If the alarm persists=>Step 5.
2.
If no=>Step 5.

----End
Related Information
None
2.9 0xF0CE0002 Disk Enclosure Quantity Exceeds The

System Limit
Description
The number of disk enclosures exceeds the system limit.
Attribute
ID
Event Level
0xF0CE0002
Warning
Yes

No more disk enclosures can be added to the storage system.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
Disk enclosure quantity exceeds the system limit.
Procedure
Step 1 Check whether disk enclosure IDs are correctly assigned to all disk enclosures connected to the
storage system.
1.
If any disk enclosure is not assigned an ID, the number of disk enclosures exceeds the
system limit. Remove the extra disk enclosure. If the alarm persists=>Step 2.
2.
If all disk enclosures are assigned IDs=>Step 2.
Step 2 Check whether any information about a disconnected disk enclosure is found in system
configuration information.
1.
If yes, delete the information about the disconnected disk enclosure and reinsert expansion
cables of the connected disk enclosures. If the alarm persists=>Step 3.
2.
If no=>Step 3.

----End
Related Information
None
2.10 0xF0CE0004 Failed To Identify An Engine Or Disk

Enclosure
Description
The storage system failed to identify an engine or disk enclosure.
Attribute
ID
Event Level
0xF0CE0004
Major
Yes

The storage system failed to identify an engine or disk enclosure.
Possible Causes
The enclosure MAC address or serial number is invalid.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.11 0xF0CE0005 Disk Enclosure Temperature Exceeds The

Upper Limit
Description
The working temperature of a disk enclosure exceeds the upper limit.
Attribute
ID
Event Level
0xF0CE0005
Major
Yes

The normal operation of the storage system may be adversely affected.
Possible Causes
l
Heat dissipation channels in the disk enclosure are blocked.
The ambient temperature exceeds the upper limit.
Procedure
1.
If yes, replace the faulty fan modules. If alarm Disk Enclosure Temperature Exceeds the
Upper Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether heat dissipation channels in the disk enclosure are blocked.
1.
If yes, clear the heat dissipation channels. If alarm Disk Enclosure Temperature Exceeds
the Upper Limit persists=>Step 3.
2.
If no=>Step 3.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Step 3 Check whether the ambient temperature is too high.

1.
Disk Enclosure Temperature Exceeds the Upper Limit persists=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
2.12 0xF0CE000A Disk Enclosure Temperature Is Far

Beyond The Upper Limit
Description
The temperature of a disk enclosure is far beyond the upper limit.
Attribute
ID
Event Level
0xF0CE000A
Major
Yes

Possible Causes
l
Heat dissipation channels in the disk enclosure are blocked.
Procedure
1.
If yes, replace the faulty fan modules. If alarm Disk Enclosure Temperature Is Far Beyond
2.
If no=>Step 2.
Step 2 Check whether heat dissipation channels in the disk enclosure are blocked.
1.
Issue 04 (2015-06-10)
If yes, clear the heat dissipation channels. If alarm Disk Enclosure Temperature Is Far
Beyond the Upper Limit persists=>Step 3.
21
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

V3 Storage System
Event Reference
2.
If no=>Step 3.

1.
Disk Enclosure Temperature Is Far Beyond the Upper Limit persists=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
2.13 0xF0CE0007 Engine Or Disk Enclosure Temperature Is

Below The Lower Limit
Description
The working temperature of an engine or disk enclosure is below the lower limit.
Attribute
ID
Event Level
0xF0CE0007
Major
Yes

The normal operation of the storage system is adversely affected.
Possible Causes
The ambient temperature is below the lower limit.
Procedure
Step 1 Increase the existing air conditioners temperature or add more air conditioners. If the alarm
persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.14 0xF0CE0008 Engine Temperature Exceeds The Upper

Limit
Description
The working temperature of an engine exceeds the upper limit.
Attribute
ID
Event Level
0xF0CE0008
Major
Yes

Possible Causes
l
Heat dissipation channels are blocked.
Procedure
1.
If yes, replace the faulty fan modules. If alarm Engine Temperature Exceeds the Upper
Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether heat dissipation channels are blocked.

1.
If yes, clear the heat dissipation channels. If alarm Engine Temperature Exceeds the Upper
2.
If no=>Step 3.

1.
Engine Temperature Exceeds the Upper Limit persists=>Step 4.
2.
If no=>Step 4.

----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.15 0xF0CE0009 Engine Temperature Is Far Beyond The

Upper Limit
Description
The working temperature of an engine exceeds the upper limit.
Attribute
ID
Event Level
0xF0CE0009
Critical
Yes

Possible Causes
l
Heat dissipation channels are blocked.
Procedure
1.
If yes, replace the faulty fan modules. If alarm Engine Temperature Is Far Beyond the Upper
2.
If no=>Step 2.

1.
If yes, clear the heat dissipation channels. If alarm Engine Temperature Is Far Beyond the
2.
If no=>Step 3.

1.
Engine Temperature Is Far Beyond the Upper Limit persists=>Step 4.
2.
If no=>Step 4.

----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.16 0xF00CE0015 Failed To Monitor An Engine

Description
An engine failed to be monitored.
Attribute
ID
Event Level
0xF00CE0015
Critical
Yes

The storage system cannot report engine faults, causing fault rectification to be delayed.
Possible Causes
l
The engine is powered off.
The engine fails to be powered on.
All controllers of the engine are faulty.
The engine ports that connect to other engines and switches are faulty.
Procedure
Step 1 Check the power supplies of the engine.
1.
If any power cable of the engine is removed, insert the power cable and power on the engine.
If the alarm persists=>Step 1.2.
2.
If any power module of the engine is faulty, replace the faulty power module and power
on the engine. If the alarm persists=>Step 2.
3.
If all power supplies of the engine are normal=>Step 2.
Step 2 Check the engine state.

1.
If the running indicator on the engine keeps blinking for over 10 minutes=>Step 5.
2.
If the engine enters safe mode=>Step 5.
3.
If the engine is powered on correctly=>Step 3.
Step 3 Check whether alarms are generated indicating the faults of controllers in the engine.
1.
If yes, replace the faulty controllers. If alarm Failed to Monitor an Engine persists=>Step
4.
2.
If no=>Step 4.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Step 4 Check whether the engine is correctly cabled to other engines and switches.
1.
If no, cable the engine with other engines and switches correctly. If alarm Failed to Monitor
an Engine persists=>Step 5.
2.
If yes=>Step 5.

----End
Related Information
None
2.17 0xF00CE0018 Controller Failed To Monitor An Engine

Rear Panel
Description
A controller failed to monitor an engine rear panel.
Attribute
ID
Event Level
0xF00CE0018
Critical
Yes

The controller cannot report engine faults.
Possible Causes
l
The I2C communication is abnormal.
Engine rear panels are faulty.
Procedure
Step 1 Replace the controller. If the alarm persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.18 0xF00CE001D Expansion Ports Are Working At

Inconsistent Rates
Description
Expansion ports are working at inconsistent rates.
Attribute
ID
Event Level
0xF00CE001D
Warning
Yes

N/A.
Possible Causes
The expansion ports are working at inconsistent rates.
Procedure
Step 1 Replace the cable of the expansion port of a lower rate. If the alarm persists=>Step 2.
Step 2 Replace the expansion module connected to the expansion port of a lower rate. If the alarm
persists=>Step 3.
----End
Related Information
None
2.19 0xF00CE002A Disk Enclosure Is Working In Single

Link State
Description
A disk enclosure is working in single link state.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00CE002A
Major
Yes

A disk enclosure working in single link state may go offline.
Possible Causes
l
Expansion cables are incorrectly connected or removed.
Expansion modules are incorrectly inserted or removed.
Expansion cables are damaged.
Procedure
Step 1 Check expansion cables and expansion modules.
1.
If any expansion cable or expansion module is removed, reinsert it. If the alarm
persists=>Step 1.2.
2.
Replace the expansion cables. If the alarm persists=>Step 1.3.
3.
Replace the expansion modules. If the alarm persists=>Step 2.

----End
Related Information
None
2.20 0xF0CF0006 Controller Is Removed

Description
A controller is removed.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0CF0006
Major
Yes

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

V3 Storage System
Event Reference

The system performance deteriorates and data loss may occur.
Possible Causes
The controller is removed.
Procedure
Step 1 Check whether the controller is removed.
1.
If yes, reinsert the controller. If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether the controller is firmly inserted.

1.
If no, reinsert the controller correctly. If the alarm persists=>Step 3.
2.
If yes=>Step 3.

----End
Related Information
None
2.21 0xF00CF0014 Failed To Monitor The Controller

Description
The controller failed to be monitored.
Attribute
ID
Event Level
0xF00CF0014
Critical
Yes

The storage system cannot report controller faults, causing fault rectification to be delayed.
Possible Causes
l
The controller is restarting.
The controller is faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.22 0xF0CF0003 Controller Is Faulty

Description
Controller hardware is faulty.
Attribute
ID
Event Level
0xF0CF0003
Major
Yes

The system performance is compromised and data may be lost.
Possible Causes
The components of the controller are faulty.
Procedure
----End
Related Information
None
2.23 0xF0CF0004 Incorrect Controller Memory Capacity

Description
The memory capacity is not supported.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0CF0004
Major
Yes

The system performance deteriorates and data loss may occur.
Possible Causes
Memory capacity of the controller does not meet system requirements.
Procedure
----End
Related Information
None
2.24 0xF0CF0005 Abnormal Communication Between

Controllers
Description
The communication between controllers in an engine is abnormal.
Attribute
ID
Event Level
0xF0CF0005
Major
Yes

The normal operation of the storage system is not affected.
Possible Causes
l
Controller components are faulty.
Backplane components are faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Heartbeat connections are down.
Mirrored links are down.
Procedure
Step 1 Replace any abnormal controller described in the alarm information. If the alarm persists=>Step
2.
Step 2 Reinsert the removed controller and try another controller. If the alarm persists=>Step 3.
Step 3 Collect related information and contact technical support engineers to replace the engine.
----End
Related Information
None
2.25 0x100F0CF0032 Controller Power Failure

Description
A controller is powered off and the system is about to stop working.
Attribute
ID
Event Level
0x100F0CF0032
Major
Yes

The controller is powered off and the system is about to stop working.
Possible Causes
l
Power cables are incorrectly connected.
Power cables loosen up or are damaged.
No power is input.
Power supplies are faulty.
Procedure
Step 1 Check whether power cables are correctly connected.
1.
If yes=>Step 2.
2.
If no, connect the power cables correctly. If the alarm persists=>Step 2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Step 2 Check power cables.

1.
If any power cable is removed, reinsert it. If the alarm persists=>Step 2.2.
2.
Replace the power cable. If the alarm persists=>Step 3.
Step 3 Check whether external power is input correctly.

1.
If yes=>Step 4.
2.
If no, supply power to the storage system correctly. If the alarm persists=>Step 4.
Step 4 Check whether any power module is faulty.

1.
If yes, replace the faulty power module. If the alarm persists=>Step 5.
2.
If no=>Step 5.

----End
Related Information
None
2.26 0xF00CF0017 Incorrect Connection Between A

Controller Port And A Switch Port
Description
A controller port is incorrectly connected to a switch port.
Attribute
ID
Event Level
0xF00CF0017
Major
Yes

The application server cannot communicate correctly with the storage system.
Possible Causes
The two ports are incorrectly cabled.
Procedure
Step 1 Cable the switch port and the controller port correctly. If the alarm persists=>Step 2.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.27 0x200F00CF0022 Failed To Start A Controller

Description
A user failed to start a controller.
Attribute
ID
Event Level
0x200F00CF0022
Warning
Yes

The storage system cannot work correctly.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.28 0x100F00CF0027 Controller Restarts

Description
A controller restarts.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x100F00CF0027
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
l
user power down/restart.
Faults occur on the controller and it restarts to rectify the faults.
Procedure
If restart or power-off is triggered by the user, please ignore it. Otherwise, collect related
information and contact technical support engineers.
----End
Related Information
None
2.29 0x100F00CF002A Controller Cache Failed To Flush Data

Description
Controller cache failed to flush data.
Attribute
ID
Event Level
0x100F00CF002A
Major
Yes

The reliability of the storage system deteriorates.
Possible Causes
The controller is running incorrectly.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.30 0x100F00CF0034 A Controller Is Isolated

Description
A controller is isolated.
Attribute
ID
Event Level
0x100F00CF0034
Critical
Yes

N/A.
Possible Causes
The PCIe link to the controller is down.
Procedure
Step 1 Check whether the device is connected through PCIe switch.
1.
If yes=>Step 2.
2.
If no=>Step 3.
Step 2 Check whether the cable connection is correct.

1.
If yes=>The cable may be damaged, requiring a replacement. After the replacement, if the
alarm persists=>Step 4.
2.
If no=>Connect the cable correctly. After that, if the alarm persists=>Step 4.
Step 3 PCIe link connection problem occurs=>Step 4.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.31 0xF00CF0035 The System Is Abnormal

Description
The system is abnormal.
Attribute
ID
Event Level
0xF00CF0035
Critical
Yes

The system is abnormal and cannot provide services.
Possible Causes
Procedure
----End
Related Information
None
2.32 0xF00CF0036 Controller Services Are Abnormal

Description
Controller services are abnormal.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF00CF0036
Critical
Yes

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

V3 Storage System
Event Reference

The controller cannot provide services.
Possible Causes
l
Service recovery failed when the controller is being powered on.
Service switchover failed before you replace the PCIe interface module online.
Procedure
Please collect log with Export Data button on DeviceManager and contact technical support
engineers.
----End
Related Information
None
2.33 0x100F00CF0037 Controller Is About To Restart

Description
A controller is about to restart.
Attribute
ID
Event Level
0x100F00CF0037
Warning
Yes

N/A.
Possible Causes
The controller version does not meet system requirements.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.34 0xF0050001 Expansion Module Is Removed

Description
An expansion module is removed. As a result, a link between the disk enclosure that houses the
expansion module and another disk enclosure or an engine is down.
Attribute
ID
Event Level
0xF0050001
Major
Yes

l
If an expansion module is redundantly connected to a disk enclosure or an engine, the

expansion module removal will compromise storage system performance and reliability.
If an expansion module is connected to a disk enclosure or an engine through only one link,
the expansion module removal will fail data transmission between the expansion module
and the disk enclosure or the engine.
Possible Causes
The expansion module is removed.
Procedure
Step 1 Reinsert the expansion module. If the alarm persists=>Step 2.
----End
Related Information
None
2.35 0xF0050002 Expansion Module Is Not Inserted

Description
An expansion module is removed. As a result, a link between the disk enclosure that houses the
expansion module and another disk enclosure or an engine is down.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0050002
Major
Yes

Data cannot be transferred between a removed expansion module and a disk enclosure or an
engine.
Possible Causes
N/A.
Procedure
Step 1 Reinsert the expansion module. If the alarm persists=>Step 2.
----End
Related Information
None
2.36 0xF0050003 Expansion Module Is Faulty

Description
Expansion module hardware is faulty.
Attribute
ID
Event Level
0xF0050003
Major
Yes

l

expansion module removal will compromise storage system performance and reliability.
the expansion module removal will fail data transmission between the expansion module
and the disk enclosure or the engine.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
The expansion module is faulty.
Procedure
Step 1 Replace the expansion module. If the alarm persists=>Step 2.
----End
Related Information
None
2.37 0xF00D00014 Abnormal Communication Between

Expansion Modules
Description
Communications between expansion modules are abnormal.
Attribute
ID
Event Level
0xF00D00014
Major
Yes

Possible Causes
l
Engine or Disk enclosure backplanes are faulty.
Procedure
Step 1 Replace expansion module A. If the alarm persists=>Step 2.
Step 2 Replace expansion module B. If the alarm persists=>Step 3.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.38 0xF00D00016 Expansion Module Is Incorrectly Cabled

Description
An expansion module is incorrectly cabled.
Attribute
ID
Event Level
0xF00D00016
Major
Yes

Possible Causes
Cables are incorrectly connected to the expansion module.
Procedure
Step 1 Recable the expansion module based on the cable connection rules provided in product
documents. If the alarm persists=>Step 2.
----End
Related Information
None
2.39 0xF0D10001 Management Module Is Removed

Description
A management module is removed.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0D10001
Major
Yes

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

V3 Storage System
Event Reference

l
The security of the storage system deteriorates.
Possible Causes
The management module is removed.
Procedure
Step 1 Reinsert the management module. If the alarm persists=>Step 2.
----End
Related Information
None
2.40 0xF0D10002 Management Module Is Faulty

Description
Management module hardware is faulty.
Attribute
ID
Event Level
0xF0D10002
Major
Yes

l
Possible Causes
l
The management module is faulty.
SSDs are faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Replace the management module. If the alarm persists=>Step 2.
----End
Related Information
None
2.41 0xF0D10005 Interface Module Is Removed

Description
An interface module is removed.
Attribute
ID
Event Level
0xF0D10005
Major
Yes

All ports on the interface module fail to function.
Possible Causes
The interface module is removed.
Procedure
Step 1 Reinsert the interface module. If the alarm persists=>Step 2.
----End
Related Information
None

Description
Interface module hardware is faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0D10006
Major
Yes

Possible Causes
The interface module is faulty.
Procedure
Step 1 Replace the interface module. If the alarm persists=>Step 2.
----End
Related Information
None
2.43 0xF0D10008 Interface Module Is Unrecognizable

Description
The storage system failed to identify an interface module in an engine or a disk enclosure.
Attribute
ID
Event Level
0xF0D10008
Major
Yes

The interface module cannot work correctly.
Possible Causes
l
The interface module is damaged.
An incorrect interface module is inserted.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.44 0xF0D10009 Interface Module Temperature Exceeds

The Upper Limit
Description
The working temperature of an interface module exceeds the upper limit due to ambient
temperature increase or fan faults.
Attribute
ID
Event Level
0xF0D10009
Warning
Yes

Services on the interface module may be abnormal.
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating the overheating of the enclosure that houses the
interface module.
1.
If yes, handle alarms with recommended actions. If alarm Interface Module Temperature
Exceeds the Upper Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated for fan modules of the enclosure that houses the interface
module.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
If yes, handle alarms with recommended actions. If alarm Interface Module Temperature
Exceeds the Upper Limit persists=>Step 3.
2.
If no=>Step 3.
Step 3 Check whether alarms are generated indicating interface module faults.
1.
If yes, replace the faulty interface modules. If alarm Interface Module Temperature Exceeds

----End
Related Information
None
2.45 0xF0D1000A Incorrect Removal Of Interface Module

Description
An interface module is removed unexpectedly.
Attribute
ID
Event Level
0xF0D1000A
Critical
Yes

Controllers may not work correctly.
Possible Causes
l
The interface module is removed without following a correct process.
The interface module is damaged.
Procedure
Step 1 Check whether the interface module is removed based on a correct hot swap process.
1.
If yes=>Step 2.
2.
If no, reinsert the interface module. If the system still cannot identify the interface module,
restart related controllers. If the alarm persists=>Step 2.
1.
If yes, replace the faulty interface modules. If the alarm persists=>Step 3.
2.
If no=>Step 3.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.46 0xF010A0017 The Communication Between Controller

And Management Module Is Disconnected
Description
The communication between controller and management module is disconnected.
Attribute
ID
Event Level
0xF010A0017
Major
Yes

N/A.
Possible Causes
l
Engine rear panels are faulty.
Procedure
Step 1 Replace the faulty management module. If the alarm persists=>Step 2.
Step 2 Replace the faulty controller. If the alarm persists=>Step 3.
Step 3 Replace the faulty engine rear panels. If the alarm persists=>Step 4.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.47 0xF00D1001E The System Failed To Monitor An

Interface Module
Description
The system failed to monitor an interface module.
Attribute
ID
Event Level
0xF00D1001E
Major
Yes

N/A.
Possible Causes
l
Procedure
1.
If yes, replace the faulty interface modules. If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace related controllers. If the alarm persists=>Step 3.

----End
Related Information
None
2.48 0xF00A0001 Disk Is Faulty

Description
Disk hardware is faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00A0001
Critical
Yes

l
Storage pools will degrade, causing storage system I/O performance deterioration and
possible data loss.
Storage pools will become faulty, causing storage pool data loss and service interruption.
Possible Causes
The disk is faulty.
Procedure
Step 1 Replace the disk. If the alarm persists=>Step 2.
----End
Related Information
None
2.49 0xF00A0002 Unrecognizable Disk

Description
A disk is not authenticated.
Attribute
ID
Event Level
0xF00A0002
Warning
Yes

The disk cannot function correctly.
Possible Causes
The disk is not authenticated.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.50 0xF00A0003 Disk Is About To Fail

Description
A disk is about to fail.
Attribute
ID
Event Level
0xF00A0003
Major
Yes

If a disk about to fail is a member of a storage pool, the storage pool may degrade.
Possible Causes
The disk is about to fail.
Procedure
Step 1 Check whether it is a member disk.
1.
If yes, pre-copy the disk, and replace the disk after a message is displayed indicating that
the precopy succeeds. If the alarm persists=>Step 2.
2.
If no, replace the disk. If the alarm persists=>Step 2.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.51 0xF00A0004 Disk Temperature Exceeds The Upper

Limit
Description
The working temperature of a disk exceeds the upper limit due to overheated ambient
temperature or fan module faults.
Attribute
ID
Event Level
0xF00A0004
Warning
Yes

The disk may become faulty.
Possible Causes
l
The disk is overheated.
The heat dissipation system is faulty.
Procedure
Step 1 Check whether alarms are generated indicating the overheating of the disk enclosure that houses
the disk.
1.
Disk Temperature Exceeds the Upper Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated indicating the faults of fan modules in the disk enclosure
that houses the disk.
1.
If yes, replace the faulty fan modules. If alarm Disk Temperature Exceeds the Upper Limit
persists=>Step 3.
2.
If no=>Step 4.

1.
If yes, clear the heat dissipation channels. If alarm Disk Temperature Exceeds the Upper
2.
If no=>Step 4.

----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.52 0xF00A0008 Coffer Disk Is Faulty

Description
A coffer disk is faulty.
Attribute
ID
Event Level
0xF00A0008
Major
Yes

There is a higher risk of data loss.
Possible Causes
l
The coffer disk is faulty.
The coffer disk is removed.
Procedure
Step 1 Check whether any coffer disk is removed.
1.
If yes, insert a coffer disk. The newly inserted coffer disk must be of the same capacity and
type as other existing coffer disks. If alarm Coffer Disk Is Faulty persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated indicating disk faults.

1.
If yes, replace the faulty disks. If alarm Coffer Disk Is Faulty persists=>Step 3.
2.
If no=>Step 3.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.53 0xF00A000A Coffer Disks Not Found

Description
No coffer disks are found in the storage system. As a result, the storage system failed to start.
Attribute
ID
Event Level
0xF00A000A
Critical
Yes

There is a higher risk of data loss.
Possible Causes
l
The disk enclosure that houses coffer disks is not powered on.
Coffer disks are faulty.
Coffer disks are removed.
The expansion cables of the disk enclosure that houses coffer disks are incorrectly
connected.
Procedure
Step 1 Check whether the disk enclosure that houses coffer disks is powered on.
1.
If no, power on the disk enclosure. If alarm No Coffer Disks Found persists=>Step 2.
2.
If yes=Step 2.
Step 2 Check whether alarms are generated indicating coffer disk faults.
1.
If yes, replace the faulty coffer disks. If alarm No Coffer Disks Found persists=>Step 3.
2.
If no=>Step 3.
Step 3 Check whether coffer disks are correctly inserted.

1.
If no, reinsert the coffer disks. If alarm No Coffer Disks Found persists=>Step 4.
2.
If yes=>Step 4.
Step 4 Check whether the expansion cables of the disk enclosure that houses coffer disks are correctly
connected to an engine.
1.
If no, connect the expansion cables correctly. If alarm No Coffer Disks Found
persists=>Step 5.
2.
If yes=>Step 5.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.54 0xF000A0015 The System Failed To Monitor A Disk In

A Disk Enclosure
Description
The system failed to monitor a disk in a disk enclosure.
Attribute
ID
Event Level
0xF000A0015
Major
Yes

The storage system cannot report disk enclosure faults, causing fault rectification to be delayed.
Possible Causes
l
The disk is faulty.
The disk is loosely inserted into its slot.
Disk enclosure backplanes are faulty.
Procedure
1.
If yes, replace the faulty disks. If alarm The System Failed to Monitor a Disk
persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether the disk is firmly inserted into its slot.
1.
If no, reinsert the disk correctly. If alarm The System Failed to Monitor a Disk
persists=>Step 3.
2.
If yes=>Step 3.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
If yes, replace the faulty expansion modules. If alarm The System Failed to Monitor a Disk
persists=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
2.55 0xF00A000D Slow Disk Response

Description
A disk responds slowly.
Attribute
ID
Event Level
0xF00A000D
Major
Yes

The storage pool that houses the disk may have compromised I/O performance or even degrade.
Possible Causes
l
The disk is faulty.
Expansion ports are partially damaged.
The disk is incorrectly inserted into its slot.
Procedure
1.
If yes, replace the faulty disks. If alarm Slow Disk Response persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether any expansion port is faulty.

1.
If yes, replace the interface module where the faulty port resides. If alarm Slow Disk
Response persists=>Step 3.
2.
If no=>Step 3.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Step 3 Check whether the disk is firmly inserted.

1.
If no, reinsert the disk. If alarm Slow Disk Response persists=>Step 4.
2.
If yes=>Step 4.
1.
If yes, replace the faulty expansion modules. If alarm Slow Disk Response persists=>Step
5.
2.
If no=>Step 5.

----End
Related Information
None
2.56 0xF00A000E Incompatible Disk Model

Description
The model of a disk is incompatible with the storage system.
Attribute
ID
Event Level
0xF00A000E
Major
Yes

The disk cannot be detected by the storage system.
Possible Causes
The disk model is incompatible with the storage system.
Procedure
Step 1 Replace the disk with a qualified one. If the alarm persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.57 0xF00A000C Disk Is In Single Link State

Description
A disk is in single-link state.
Attribute
ID
Event Level
0xF00A000C
Major
Yes

N/A.
Possible Causes
The disk is in single-link state.
Procedure
----End
Related Information
None
2.58 0xF00A0006 Disk Has Too Many Bit Error

Description
A disk has too many bit errors.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF00A0006
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
l
The disk has too many bit errors.
Cables or ports are damaged.
Procedure
Step 1 Replace the disk. If alarm Disk Has Too Many Bit Errors persists=>Step 2.
Step 2 Check whether alarms are generated indicating the partial damage of expansion ports.
1.
If yes, replace the interface modules where the faulty expansion ports reside. If alarm Disk
Has Too Many Bit Errors persists=>Step 3.
2.
If no=>Step 3.

1.
If yes=>Step 4.
2.
If no, reinsert the disk. If alarm Disk Has Too Many Bit Errors persists=>Step 4.
1.
If yes, replace the faulty expansion modules. If alarm Disk Has Too Many Bit Errors
persists=>Step 5.
2.
If no=>Step 5.

----End
Related Information
None
2.59 0xF000A001A Disk Temperature Is Below The Lower

Limit
Description
The working temperature of a disk is below the lower limit.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF000A001A
Warning
Yes

l
The storage system may not work correctly.
Possible Causes
l
The ambient temperature is too low.
The disk is faulty.
Procedure
Step 1 Check whether alarms are generated indicating the overcooling of the disk enclosure that houses
the disk.
1.
If yes, increase the existing air conditioners temperature or add more air conditioners. If
alarm Disk Temperature Is Below the Lower Limit persists=>Step 2.
2.
If no=>Step 2.

1.
If yes, replace the faulty disks. If the alarm Disk Temperature Is Below the Lower Limit
persists=>Step 3.

----End
Related Information
None
2.60 0xF000A004E Coffer Disks Not Found

Description
Coffer disks are not found in disk enclosure.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF000A004E
Critical
Yes

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

V3 Storage System
Event Reference

The storage system to fail to start.
Possible Causes
l
The disk enclosure that houses coffer disks is not powered on.
Coffer disks are faulty.
Coffer disks are removed.
The expansion cables of the disk enclosure that houses coffer disks are incorrectly
connected.
Procedure
Step 1 Check whether the disk enclosure that houses coffer disks is powered on.
1.
If no, power on the disk enclosure. If alarm Coffer Disk Not Found persists=>Step 2.
2.
If yes=>Step 2.
Step 2 Check whether alarms are generated indicating coffer disk faults.
1.
If yes, replace the faulty coffer disks. If alarm Coffer Disk Not Found persists=>Step 3.
2.
If no=>Step 3.
Step 3 Check whether any coffer disk is removed.

1.
If no, insert the removed coffer disk. If alarm Coffer Disk Not Found persists=>Step 4.
2.
If no=>Step 4.
Step 4 Check whether the expansion cables between the disk enclosure that houses coffer disks and an
engine are correctly connected.
1.
If yes=>Step 5.
2.
If no, connect the expansion cables correctly. If alarm Coffer Disk Not Found
persists=>Step 5.

----End
Related Information
None
2.61 0xF000A004F The Coffer Disk Is Inserted Into An

Incorrect Slot
Description
The coffer disk is inserted into an incorrect slot.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF000A004F
Major
No

N/A.
Possible Causes
The coffer disk is not inserted into its original slot.
Procedure
Reinsert the coffer disk into the correct slot. Ensure that the coffer disk is inserted into its original
slot.
----End
Related Information
None
2.62 0xF0170001 Power Module Is Not Inserted

Description
A power module is not inserted.
Attribute
ID
Event Level
0xF0170001
Major
Yes

l
Possible Causes
The power module is not inserted.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check whether the power module is inserted.
1.
If yes=>Step 2.
2.
If no, insert a power module. If the alarm persists=>Step 2.
Step 2 Check whether the power module is firmly inserted.

1.
If yes=>Step 3.
2.
If no, reinsert the power module correctly. If the alarm persists=>Step 3.

----End
Related Information
None
2.63 0xF0170002 Power Module Is Removed

Description
A power module is removed.
Attribute
ID
Event Level
0xF0170002
Major
Yes

l
Possible Causes
The power module is removed.
Procedure
Step 1 Insert the power module. If the alarm persists=>Step 2.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.64 0xF0170003 Power Module Is Faulty

Description
A power module is faulty.
Attribute
ID
Event Level
0xF0170003
Major
Yes

l
Possible Causes
The power module is faulty.
Procedure
Step 1 1 Check whether the power cable is securely connected to the power module involved in the
alarm. If not, securely connect the power cable. If the alarm persists==>Step 2.
Step 2 Replace the power module. If the alarm persists=>Step 3.
----End
Related Information
None
2.65 0xF0170004 Power Module Temperature Exceeds The

Upper Limit
Description
The temperature of a power module exceeds the upper limit.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0170004
Warning
Yes

l
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating the overheating of the disk enclosure or engine
that houses power module.
1.
Power Module Temperature Exceeds the Upper Limit persists=>Step 2.
2.
If no=>Step 2.
1.
If yes, replace the faulty fan modules. If alarm Power Module Temperature Exceeds the
2.
If no=>Step 3.
1.
If yes, replace the faulty power modules. If alarm Power Module Temperature Exceeds the
2.
If no=>Step 4.

----End
Related Information
None
2.66 0xF0170005 Power Module Input Is Abnormal

Description
The input to a power module is abnormal.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0170005
Major
Yes

l
Possible Causes
l
Power cables are removed or damaged.
The input voltage is too high or too low.
Procedure
Step 1 Check the power cables connected to the power module.
1.
If any power cable is removed, reinsert the power cable. If alarm Input to a Power Module
Is Abnormal persists=>Step 1.2.
2.
Replace the power cable. If alarm Power Module Input Is Abnormal persists=>Step 2.
Step 2 Check whether the input power voltage is too high or too low.
1.
If yes, stabilize the input power voltage. If alarm Power Module Input Is Abnormal
persists=>Step 3.
2.
If no=>Step 3.
1.
If yes, replace the faulty power modules. If alarm Power Module Input Is Abnormal
persists=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
2.67 0xF00170014 Power Module Has No Input

Description
There is no power input to a power module.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00170014
Major
Yes

The storage system fails to start.
Possible Causes
l
Power cables are incorrectly connected.
Power cables are removed or damaged.
The power module is incorrectly inserted.
No external power is input.
Procedure
Step 1 Check whether power cables are connected correctly.
1.
If yes=>Step 2.
2.
If no, connect the power cables correctly. If the alarm persists=>Step 2.
Step 2 Check power cables.

1.
If any power cable is removed, reinsert it. If the alarm persists=>Step 2.2.
2.
Replace the power cable. If the alarm persists=>Step 3.
Step 3 Check whether the power module is inserted.

1.
If yes=>Step 4.
2.
If no, reinsert the power module. If the alarm persists=>Step 4.
Step 4 Check whether any external power is input to the power module.
1.
If yes=>Step 5.
2.
If no, supply power to the storage system correctly. If the alarm persists=>Step 5.
Step 5 Replace the power module. If the alarm persists=>Step 6.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.68 0xF00170017 The System Failed To Monitor A Power

Module
Description
The system failed to monitor a power module.
Attribute
ID
Event Level
0xF00170017
Major
Yes

The system failed to monitor a power module.
Possible Causes
l
Procedure
1.
If yes, replace the faulty power modules. If alarm The System Failed to Monitor a Power
Module persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace the controller of the engine that houses the power module. If alarm The System Failed
to Monitor a Power Module persists=>Step 3.
----End
Related Information
None
2.69 0x100F0170006 Power Module Incompatible

Description
A power module is incompatible with the storage system.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x100F0170006
Warning
Yes

Possible Causes
N/A.
Procedure
----End
Related Information
None
2.70 0x100F0170008 Multi-Vendor Power Modules In The

Same Enclosure
Description
Power modules in the same enclosure are from different vendors.
Attribute
ID
Event Level
0x100F0170008
Warning
Yes

Possible Causes
N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.71 0xF0D20002 BBU Module Is Faulty

Description
A BBU module is faulty.
Attribute
ID
Event Level
0xF0D20002
Major
Yes

Possible Causes
N/A.
Procedure
Step 1 Replace the BBU module. If the alarm persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.72 0xF0D20003 BBU Module Reaches Its Expiration Date

Or Is Aging
Description
A BBU module reaches its expiration date or is aging.
Attribute
ID
Event Level
0xF0D20003
Major
Yes

Possible Causes
The BBU module reaches its expiration date or is aging.
Procedure
Step 1 Replace the BBU module. If the alarm persists=>Step 2.
----End
Related Information
None
2.73 0xF0D20007 BBU Module Is About To Expire

Description
A BBU module is about to expire.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0D20007
Warning
Yes

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

V3 Storage System
Event Reference

Possible Causes
The BBU module is about to expire.
Procedure
Step 1 Replace the BBU module in three months. If the alarm persists=>Step 2.
----End
Related Information
None
2.74 0xF0D20004 BBU Module Is Removed

Description
A BBU module is removed.
Attribute
ID
Event Level
0xF0D20004
Major
Yes

Possible Causes
The BBU module is removed.
Procedure
Step 1 Insert the BBU module. If the alarm persists=>Step 2.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.75 0xF0D20005 BBU Module Temperature Exceeds The

Upper Limit
Description
The working temperature of the BBU module exceeds the upper limit.
Attribute
ID
Event Level
0xF0D20005
Major
Yes

Possible Causes
l
The BBU module is faulty.
Procedure
Step 1 Check whether alarms are generated indicating the overheating of the engine that houses the
BBU module.
1.
BBU Module Temperature Exceeds the Upper Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated indicating the faults of fan modules in the engine that houses
the BBU module.
1.
If yes, replace the faulty fan modules. If alarm BBU Module Temperature Exceeds the
2.
If no=>Step 3.
1.
If yes, replace the faulty BBU modules. If alarm BBU Module Temperature Exceeds the
2.
If no=>Step 4.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.76 0xF00D2001B BBU Module Temperature Is Below The

Lower Limit
Description
The working temperature of a BBU module is below the lower limit.
Attribute
ID
Event Level
0xF00D2001B
Major
Yes

Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating the overcooling of the engine that houses the
BBU module.
1.
alarm BBU Module Temperature Is Below the Lower Limit persists=>Step 2.
2.
If no=>Step 2.
1.
If yes, replace the faulty BBU modules. If alarm BBU Module Temperature Is Below the
Lower Limit persists=>Step 3.
2.
If no=>Step 3.

----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.77 0xF00D20014 The System Failed To Monitor A BBU

Module
Description
The system failed to monitor a BBU module.
Attribute
ID
Event Level
0xF00D20014
Major
Yes

N/A.
Possible Causes
l
Procedure
1.
If yes, replace the faulty BBU modules. If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace the controller of the engine that houses the BBU module. If the alarm persists=>Step
3.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

Description
Fan hardware is faulty, causing abnormal fan speed.
Attribute
ID
Event Level
0xF0D30001
Major
Yes

l
Engines or disk enclosures will overheat, affecting the normal operation of the storage
system.
The storage I/O performance may deteriorate.
Possible Causes
The fan module is faulty.
Procedure
Step 1 Replace the fan module. If the alarm persists=>Step 2.
----End
Related Information
None
2.79 0xF0D30002 Fan Module Is Not Inserted

Description
A fan module is not inserted.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0D30002
Major
Yes

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

V3 Storage System
Event Reference

l
system.
Possible Causes
The fan module is not inserted.
Procedure
Step 1 Check whether the fan module is inserted.
1.
If yes=>Step 2.
2.
If no, insert a fan module. If the alarm persists=>Step 2.
Step 2 Check whether the fan module is firmly inserted.

1.
If yes=>Step 3.
2.
If no, reinsert the fan module correctly. If the alarm persists=>Step 3.

----End
Related Information
None
2.80 0xF0D30003 Fan Module Is Removed

Description
A fan module is removed.
Attribute
ID
Event Level
0xF0D30003
Major
Yes

l
system.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
The fan module is removed.
Procedure
Step 1 Insert the fan module. If the alarm persists=>Step 2.
----End
Related Information
None
2.81 0xF00D30014 The System Failed To Monitor A Fan

Module
Description
The system failed to monitor a fan module.
Attribute
ID
Event Level
0xF00D30014
Major
Yes

N/A.
Possible Causes
l
Procedure
1.
If yes, replace the faulty fan modules. If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace the controller of the engine that houses the fan module. If the alarm persists=>Step 3.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.82 0xF0060002 Expansion Port Link Down

Description
A link between an expansion module and a disk enclosure or engine is down.
Attribute
ID
Event Level
0xF0060002
Major
Yes

l

expansion port link down will compromise storage system performance and reliability.
the expansion port link down will fail data transmission between the expansion module and
the disk enclosure or the engine.
Possible Causes
l
Disk enclosures are offline.
Procedure
1.
If any expansion cable is removed, reinsert it. If alarm Expansion Port Link Down
persists=>Step 1.2.
2.
Step 2 Check whether alarms are generated indicating disk enclosure offline.
1.
If yes, handle alarms with recommended actions. If alarm Expansion Port Link Down
persists=>Step 3.
2.
If no=>Step 3.
1.
If yes, replace the faulty expansion modules. If alarm Expansion Port Link Down
persists=>Step 4.
2.
If no=>Step 4.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.83 0xF0060003 Expansion Port Is Faulty

Description
An expansion module fault causes an expansion port to be unavailable.
Attribute
ID
Event Level
0xF0060003
Major
Yes

l

Possible Causes
The expansion port is faulty.
Procedure
Step 1 Replace the module where the expansion port resides. If the alarm persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.84 0xF0060004 Host Port Link Down

Description
A host port is disconnected from the application server or other devices.
Attribute
ID
Event Level
0xF0060004
Major
Yes

The application server or other devices cannot communicate with the storage system through
the host port.
Possible Causes
l
The cables are removed or damaged.
The optical module of a port is faulty.
Procedure
Step 1 Check whether the cable connected to the host port is removed or damaged.
1.
If the cable is removed, connect it back. If the alarm persists=>Step 1.2.
2.
If the cable is damaged, replace it with an intact one. If the alarm persists=>Step 1.3.
3.
If the host port has an optical module=>Step 2. Otherwise=>Step 1.4.
4.
If no exception is found=>Step 3.
Step 2 Check whether the optical module is faulty.

1.
Reinsert the optical module and connect the cable. If the alarm persists=>Step 2.2.
2.
Replace the optical module and connect the cable. If the alarm persists=>Step 3.
Step 3 Check the port configuration.

1.
Check whether the topological mode of the local port matches that of the peer end. If not,
change the mode to match the two ends. If the alarm persists after this operation =>Step
3.2.
2.
Check whether the speed of the local port matches that of the peer end. If not, change the
mode to match the two ends. If the alarm persists after this operation =>Step 4.
Step 4 Contact technical support engineers for further handling.

----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.85 0xF0060005 Host Port Is Faulty

Description
A host port is faulty.
Attribute
ID
Event Level
0xF0060005
Major
Yes

the host port.
Possible Causes
The host port is faulty.
Procedure
----End
Related Information
None
2.86 0xF0060006 Expansion Port Partially Damaged

Description
An expansion module is partially damaged.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0060006
Major
Yes

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

V3 Storage System
Event Reference

l

Possible Causes
l
Expansion cables are removed or faulty, causing bit errors to occur.
Procedure
1.
If any expansion cable is removed, reinsert it and wait three minutes. If the alarm
persists=>Step 1.2.
2.
----End
Related Information
None
2.87 0xF01080014 Expansion Port Has Too Many Bit Errors

Description
An expansion port has too many bit errors.
Attribute
ID
Event Level
0xF01080014
Major
Yes

Data cannot be transferred between the storage system and disk enclosures through the expansion
port.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
Expansion cables are loosen up or damaged.
Procedure
1.
If any expansion cable is not firmly inserted, reinsert it. If the alarm persists=>Step 1.2.
2.
Step 2 Replace faulty modules where the faulty expansion port resides. If the alarm persists=>Step 3.
----End
Related Information
None
2.88 0xF0060010 Expansion Port Isolated

Description
An expansion port on an engine or disk enclosure is isolated.
Attribute
ID
Event Level
0xF0060010
Major
Yes

The expansion port is isolated and becomes unavailable.
Possible Causes
l
Expansion cables loosen up or are damaged, causing bit errors.
Procedure
Step 1 Check whether any expansion cable is faulty.
1.
Issue 04 (2015-06-10)
If yes, replace the faulty expansion cable. If the alarm persists=>Step 2.

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

V3 Storage System
Event Reference
2.
If no=>Step 2.
Step 2 Check whether expansion cables are firmly inserted.

1.
If yes=>Step 3.
2.
If no, reinsert the expansion cables and wait three minutes. If the alarm persists=>Step 3.
----End
Related Information
None
2.89 0xF01080015 Host Port Has Too Many Bit Errors

Description
A host port has too many bit errors.
Attribute
ID
Event Level
0xF01080015
Major
Yes

the host port.
Possible Causes
l
Cables are loosen up or damaged.
The port is faulty.
Interface modules are faulty.
Procedure
Step 1 Check cables.
1.
If any cable is not firmly inserted, reinsert it. If the alarm persists=>Step 1.2.
2.
Replace the cable. If the alarm persists=>Step 2.
Step 2 Check whether any optical module is on the host port and the host ports peer port.
1.
Issue 04 (2015-06-10)
If yes, replace the optical modules. If the alarm persists=>Step 3.

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

V3 Storage System
Event Reference
2.
If no=>Step 3.
Step 3 Replace the interface modules that house the host port and its peer port. If the alarm
persists=>Step 4.
----End
Related Information
None
2.90 0xF01080016 PCIE Port Partially Damaged

Description
A PCIe port is partially damaged but still works.
Attribute
ID
Event Level
0xF01080016
Major
Yes

N/A.
Possible Causes
l
The PCIe cables are removed or damaged, causing bit errors.
The PCIe port is faulty.
Procedure
Step 1 Check PCIe cables.
1.
If any PCIe cable is removed, reinsert it. If the alarm persists=>Step 1.2.
2.
Replace the PCIe cable. If the alarm persists=>Step 2.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.91 0xF01080018 PCIE Port Is Faulty

Description
A PCIe port is faulty.
Attribute
ID
Event Level
0xF01080018
Major
Yes

The interface module where the port resides cannot provide services.
Possible Causes
The PCIe port is faulty.
Procedure
Step 1 Replace the interface module where the PCIe port resides. If the alarm persists=>Step 2.
----End
Related Information
None
2.92 0xF01080019 PCIE Port Disconnected

Description
A PCIe port is disconnected.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF01080019
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
PCIe cables are removed or damaged.
Procedure
Step 1 Check PCIe cables.
1.
If any PCIe cable is removed, reinsert it. If the alarm persists=>Step 1.2.
2.
Replace the PCIe cable. If the alarm persists=>Step 2.

----End
Related Information
None
2.93 0xF0108001A PCIE Port Has Too Many Bit Errors

Description
A PCIe port has too many bit errors but still works.
Attribute
ID
Event Level
0xF0108001A
Major
Yes

N/A.
Possible Causes
The PCIe port has too many bit errors.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.94 0xF0060011 Network Port Is Working In Half-Duplex

Mode
Description
A network port is working in half-duplex mode.
Attribute
ID
Event Level
0xF0060011
Major
Yes

N/A.
Possible Causes
l
The host or switch where the network ports peer port resides supports only half-duplex.
Expansion cables loosen up or are damaged.
Network port components are faulty.
Procedure
Step 1 Check the working mode of the network ports peer port.
1.
If the peer port is working in half-duplex mode, change the working mode to full-duplex.
If the alarm persists=>Step 1.2.
2.
If the peer port supports only half-duplex mode, adjust network connections to ensure that
full-duplex is supported. If the alarm persists=>Step 2.
3.
If the peer port meets requirements=>Step 2.
Step 2 Check cables.

1.
If any cable is removed, reinsert it. If the alarm persists=>Step 2.2.
2.
Step 3 Replace the module where the network port resides. If the alarm persists=>Step 4.
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.95 0xF0108001D Port Negotiated Rate Is Smaller Than The

Allowed Maximum
Description
The negotiated rate of a port is smaller than the allowed maximum.
Attribute
ID
Event Level
0xF0108001D
Major
Yes

Possible Causes
l
The rate supported by the network ports peer port is smaller than that of the network port.
Network port components are faulty.
Procedure
Step 1 Check whether the speed supported by the network ports peer port is smaller than that of the
network port.
1.
If yes, ignore this alarm.
2.
If no=>Step 2.

1.
If any expansion cable is removed, reinsert it. If the alarm persists=>Step 2.2.
2.
Step 3 Check whether any optical module is installed.

1.
If no=>Step 4.
2.
If yes, replace the optical modules on the network port and its peer port. If the alarm
persists=>Step 3.3.
3.
Replace the interface modules where the network port and its peer port reside. If the alarm
persists=>Step 4.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.96 0xF01080048 Management Network Port Is Faulty

Description
A management network port is faulty.
Attribute
ID
Event Level
0xF01080048
Major
Yes

Storage devices cannot be managed or maintained through a faulty management network port.
Possible Causes
Management network port hardware is faulty.
Procedure
----End
Related Information
None
2.97 0xF01080049 Management Network Port Is

Disconnected
Description
A management network port is disconnected.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF01080049
Warning
Yes

Storage devices cannot be managed or maintained through a disconnected management network
port.
Possible Causes
Management network cables are removed or damaged.
Procedure
Step 1 Check management network cables.
1.
If any management network cable is removed, reinsert it. If the alarm persists=>Step 1.2.
2.
Replace the management network cable. If the alarm persists=>Step 2.

----End
Related Information
None
2.98 0xF0EA0003 Port Optical Module Is Faulty

Description
The optical module of a port is faulty.
Attribute
ID
Event Level
0xF0EA0003
Major
Yes

The optical module cannot provide services.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
The optical module is faulty.
Procedure
Step 1 Replace the optical module with a new one that meets requirements. If the alarm persists=>Step
2.
----End
Related Information
None
2.99 0xF0EA0004 Port Unavailable Due To Incompatible

Optical Module Type
Description
The type of an optical module is incompatible with its port, causing the port to be unavailable.
Attribute
ID
Event Level
0xF0EA0004
Warning
Yes

Possible Causes
A single-mode optical module is inserted into the port.
Procedure
Step 1 Replace the single-mode optical module with a multi-mode optical module. If the alarm
persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.100 0xF0EA0005 Optical Module Rate Is Inconsistent With

That Of Its Port
Description
The rate of an optical module is inconsistent with that of its port, causing the port to be
unavailable.
Attribute
ID
Event Level
0xF0EA0005
Major
Yes

Possible Causes
The rate of the optical module is different from that of its port.
Procedure
Step 1 Replace the optical module with a new one that meets requirements. If the alarm persists=>Step
2.
----End
Related Information
None
2.101 0xF00EA0016 Optical Module Temperature Is Below

The Lower Limit
Description
The temperature of an optical module is below the lower limit.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00EA0016
Major
Yes

N/A.
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating the overcooling of the engine or enclosure that
houses the optical module.
1.
alarm Optical Module Temperature Is Below the Lower Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated indicating optical module faults.
1.
If yes, replace the faulty optical modules. If alarm Optical Module Temperature Is Below
the Lower Limit persists=>Step 3.
2.
If no=>Step 3.

----End
Related Information
None
2.102 0xF00EA0014 Abnormal Port Link

Description
The link to a port housing an optical module is down due to the link down between the host port
and the application server or another device, a fault on the optical module, or a fault on the port.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF00EA0014
Major
Yes

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

V3 Storage System
Event Reference

the host port.
Possible Causes
l
The cable connected to the optical module is not firmly inserted or damaged.
The optical module or its peer port is faulty.
The port or its peer port is faulty.
Procedure
Step 1 Check cable connections.
1.
If any cable is not firmly inserted, reinsert it. If the alarm persists=>Step 1.2.
2.
Step 2 Replace the optical module of the port and that of the ports peer port. If the alarm
persists=>Step 3.
Step 3 Replace the modules where the port and its peer port reside. If the alarm persists=>Step 4.
----End
Related Information
None
2.103 0xF00EA0015 The System Failed To Monitor An

Optical Module
Description
The system failed to monitor an optical module.
Attribute
ID
Event Level
0xF00EA0015
Major
Yes

N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
Procedure
1.
If yes, replace the optical modules. If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace the module where the optical module resides. If the alarm persists=>Step 3.
----End
Related Information
None
2.104 0xF00EA0017 Optical Module Temperature Exceeds

The Upper Limit
Description
The temperature of an optical module exceeds the upper limit.
Attribute
ID
Event Level
0xF00EA0017
Major
Yes

N/A.
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating the overheating of the engine or enclosure that
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
Optical Module Temperature Exceeds the Upper Limit persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether alarms are generated indicating the faults of fan modules in the engine or
enclosure that houses the optical module.
1.
If yes, replace the faulty fan modules. If alarm Optical Module Temperature Exceeds the
2.
If no=>Step 3.
Step 3 Replace the optical module. If alarm Optical Module Temperature Exceeds the Upper Limit
persists=>Step 4.
----End
Related Information
None
2.105 0xF00B0001 LUN Is Faulty

Description
If a storage system works in single-storage pool state and bad sectors are detected by a host
during data read, the storage system reports a LUN fault.
Attribute
ID
Event Level
0xF00B0001
Critical
Yes

Data on a faulty LUN may be lost.
Possible Causes
Disks are faulty.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None

Description
A medium error occurs on a LUN in the storage pool, causing possible data loss.
Attribute
ID
Event Level
0xF00B0002
Critical
Yes

The reliability of data stored on the LUN deteriorates.
Possible Causes
Bad sectors are detected on disks.
Procedure
Step 1 Check whether the LUN has a backup.
1.
If yes, restore data on the LUN from the backup LUN.
2.
If no=>Step 2.

----End
Related Information
None
2.107 0x100F000B0016 Switchover Failure Occurs On The

Owning Controller Of A LUN
Description
A switchover failure occurs on the owning controller of a LUN.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x100F000B0016
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.108 0xF00B003D Snapshot LUN Is Faulty

Description
A snapshot LUN is faulty, causing snapshot unavailability or snapshot data loss.
Attribute
ID
Event Level
0xF00B003D
Critical
Yes

The snapshot becomes unavailable or snapshot data is lost.
Possible Causes
Snapshot LUNs are faulty.
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None

Description
A medium error occurs on a LUN in the storage pool, causing possible data loss and LUN no
longer available to the host.
Attribute
ID
Event Level
0xF000B0050
Critical
No

The reliability of data stored on the LUN deteriorates and LUN will be no longer available to
the host.
Possible Causes
Procedure
----End
Related Information
None

Description
A medium error occurs on a LUN in the storage pool, causing possible data loss.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF000B0051
Warning
No

The reliability of data stored on the LUN deteriorates.
Possible Causes
Procedure
----End
Related Information
None
2.111 0xF0DB0002 Full LUN Copy Is Faulty

Description
A full LUN copy is faulty due to a source LUN or target LUN fault, or link down between storage
devices.
Attribute
ID
Event Level
0xF0DB0002
Critical
Yes

Except deleting the LUN copy and deleting the target LUN, other operations related to the LUN
copy cannot be performed.
Possible Causes
l
Issue 04 (2015-06-10)
Links for LUN copy between storage arrays are unavailable.

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

V3 Storage System
Event Reference
The source LUN or target LUNs are abnormal.
The external source LUN or target LUNs are in the sleep state and will be automatically
waked up later.
Procedure
Step 1 Check whether the links between storage arrays are down.
1.
If yes, replace the faulty optical fibers or network cables. If the alarm persists=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.112 0xF0DC0001 Clone Pair Is Abnormally Interrupted

Description
A clone pair is abnormally interrupted.
Attribute
ID
Event Level
0xF0DC0001
Critical
Yes

Data cannot be written onto or read from the primary or secondary LUN of the clone.
Possible Causes
l
The storage pool is faulty.
The primary LUN of a clone is faulty.
The secondary LUN of a clone is faulty.
Procedure
Step 1 Check whether alarms are generated for the storage pools that house the primary and secondary
LUNs.
1.
Issue 04 (2015-06-10)
If yes, handle alarms with recommended actions. If the alarm clone pair is abnormally
interrupted persists=>Step 2.
103
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

V3 Storage System
Event Reference
2.
If no=>Step 2.

----End
Related Information
None
2.113 0xF0DC0002 Clone Is Unavailable

Description
A clone is unavailable.
Attribute
ID
Event Level
0xF0DC0002
Critical
Yes

Except deleting the secondary LUN from the clone and deleting the clone, other operations
related to the clone cannot be performed.
Possible Causes
Configurations of the clone are abnormal.
Procedure
----End
Related Information
None
2.114 0xF0DC0003 Clone Pair Is Unavailable

Description
A clone pair is unavailable.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0DC0003
Critical
Yes

The clone pair is unavailable.
Possible Causes
Configurations of the clone are abnormal.
Procedure
----End
Related Information
None
2.115 0x100F01C0003 Data On The Primary LUN In The

Remote Replication Fails To Be Rolled Back
Description
Data on the primary LUN in the remote replication fails to be rolled back.
Attribute
ID
Event Level
0x100F01C0003
Critical
Yes

N/A.
Possible Causes
l
The storage pool is abnormal.
The primary LUN in the remote replication is faulty or has a medium error.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check whether the storage pool is abnormal.
1.
if yes, please resolve problems. If the alarm persists, =>Step 2.
2.
if no, =>Step 2.

----End
Related Information
None
2.116 0xF00270038 Remote Replication Is Interrupted

Description
Remote replication is interrupted.
Attribute
ID
Event Level
0xF00270038
Critical
Yes

Except deleting the secondary LUN from the remote replication and deleting the remote
replication, other operations related to the remote replication cannot be performed.
Possible Causes
l
Links are down.
Links are unstable.
Storage pools are faulty.
The service load on the remote replication devices is heavy.
The primary LUN of the remote replication is faulty.
The secondary LUN of the remote replication is faulty.
Procedure
Step 1 Check whether alarms are generated indicating link down.
1.
If yes, handle alarms with recommended actions. If alarm Remote Replication Is Interrupted
persists=>Step 2.
2.
If no=>Step 2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Step 2 Check whether cables are correctly connected.

1.
If yes=>Step 3.
2.
If no, replace faulty optical fibers or network cables to ensure that all links work correctly.
If alarm Remote Replication Is Interrupted persists=>Step 3.
LUNs.
1.
If yes, handle alarms with recommended actions. If alarm Remote Replication Is Interrupted
persists=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
2.117 0xF00270039 Remote Replication Is Unavailable

Description
The properties of the local and remote storage devices of remote replication are inconsistent,
causing remote replication to be unavailable.
Attribute
ID
Event Level
0xF00270039
Major
Yes

Data cannot be backed up correctly.
Possible Causes
l
Remote replication is deleted on the local end after being interrupted.
When an asynchronous remote replication session is setting the secondary LUN to writable,
the secondary LUN rollback failed.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.118 0xF0027003A Remote Replication Failed To

Synchronize Data Automatically
Description
Remote replication failed to synchronize data automatically.
Attribute
ID
Event Level
0xF0027003A
Major
No

N/A.
Possible Causes
l
Storage pool capacity is used up.
Network connectivity is abnormal.
Procedure
Step 1 Check whether alarms are generated indicating storage system faults.
1.
If yes, handle alarms with recommended actions. If alarm Remote Replication Failed to
Synchronize Data Automatically persists=>Step 2.
2.
If no, synchronize data manually. If alarm Remote Replication Failed to Synchronize Data
Automatically persists=>Step 2.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.119 0x100F0027008B Failed To Roll Back The Secondary

LUN In Remote Replication
Description
Failed to roll back the secondary lUN in remote replication.
Attribute
ID
Event Level
0x100F0027008B
Critical
Yes

N/A.
Possible Causes
l
The secondary LUN is faulty.
Procedure
Step 1 Check whether alarms are generated for the storage pool that houses the secondary LUN.
1.
If yes, handle alarms with recommended actions. If alarm Failed to Roll Back the Secondary
LUN in a Remote Replication persist=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.120 0xF0DD0001 Remote Replication Consistency Group

Is Disconnected
Description
Remote replication consistency group is disconnected abnormally.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0DD0001
Critical
Yes

A consistency group disconnected due to storage array link down is available only after the links
are back to normal. If the links are down permanently, the consistency group must be deleted.
Possible Causes
l
Links are down.
Links are unstable.
The service load on the remote replication destination is heavy.
The primary LUN of the remote replication is faulty.
The secondary LUN of the remote replication is faulty.
Procedure
Step 1 Check whether alarms are generated indicating link down.
1.
If yes, handle alarms with recommended actions. If alarm Remote Replication Consistency
Group Is Disconnected persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether cables are correctly connected.

1.
If yes=>Step 3.
2.
If no, replace faulty optical fibers or network cables to ensure that all links work correctly.
If alarm Remote Replication Consistency Group Is Disconnected persists=>Step 3.
LUNs.
1.
Group Is Disconnected persists=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

Is Unavailable
Description
A remote replication consistency group is unavailable.
Attribute
ID
Event Level
0xF0DD0002
Major
Yes

N/A.
Possible Causes
l
After the consistency group is disconnected, primary/secondary switchover is forcibly

performed.
The consistency group is deleted after being disconnected.
The consistency group contains unavailable remote replication.
Procedure
----End
Related Information
None
2.122 0xF01C0005 Remote Replication Consistency Group

Failed To Synchronize Data Automatically
Description
A remote replication consistency group failed to synchronize data automatically.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF01C0005
Major
No

N/A.
Possible Causes
l
Storage pool capacity is used up.
Procedure
1.
Group Failed to Synchronize Data Automatically persists=>Step 2.
2.
If no, synchronize data manually. If alarm Remote Replication Consistency Group Failed
to Synchronize Data Automatically persists=>Step 2.

----End
Related Information
None
2.123 0x100F01B0001 Snapshot Rollback Stopped

Unexpectedly
Description
Snapshot rollback stopped unexpectedly.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x100F01B0001
Warning
Yes

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

V3 Storage System
Event Reference

Data on the source LUN may be inconsistent.
Possible Causes
l
The snapshot failed.
The source LUN is faulty.
Procedure
Step 1 Check whether the snapshot is in the normal state.
1.
If yes, roll back the snapshot manually. If the rollback fails=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.124 0xE02050002 Snapshot Unavailable

Description
Storage pool space is used up or the source LUN is faulty, causing snapshots to be unavailable.
Attribute
ID
Event Level
0xE02050002
Major
Yes

The snapshot becomes unavailable or snapshot data is lost.
Possible Causes
The remaining capacity of storage pools is insufficient.
Procedure
Step 1 Check whether alarms are generated indicating insufficient storage pool capacity.
1.
Issue 04 (2015-06-10)
If yes, add disks to storage pools and activate the snapshot.

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

V3 Storage System
Event Reference
2.
If no=>Step 2.

----End
Related Information
None
2.125 0x200F001B0046 Succeeded In Canceling Snapshot

Rollback
Description
Succeeded in canceling snapshot rollback.
Attribute
ID
Event Level
0x200F001B0046
Major
Yes

Possible Causes
N/A.
Procedure
----End
Related Information
None
2.126 0x200F001B0047 Failed To Cancel Snapshot Rollback

Description
Canceling snapshot rollback failed.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x200F001B0047
Major
Yes

Possible Causes
l
The snapshot failed.
The source LUN is faulty.
Procedure
Step 1 Check whether the snapshot is in the normal state.
1.
If yes, roll back the snapshot manually. If the rollback fails=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.127 0xF0E10001 Replication Link Is Down

Description
The replication link between a local and remote storage arrays is down, causing the failure to
access the remote storage array.
Attribute
ID
Event Level
0xF0E10001
Major
Yes

l
Issue 04 (2015-06-10)
If a local storage array is redundantly connected to a remote storage array, one link down
will compromise storage system performance and reliability.
115
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

V3 Storage System
Event Reference
If a local storage array is connected to a remote storage array through only one link, the
link down will interrupt the LUN copy between storage arrays or between the primary and
secondary LUNs of remote replication.
Possible Causes
l
The replication link is down.
Remote storage arrays are faulty or restarting.
Local storage arrays are faulty.
Procedure
Step 1 Check all cable connections.
1.
2.
3.
If all cable connections are normal=>Step 2.
Step 2 Check all remote storage arrays.

1.
If any remote storage array is faulty, handle the fault with recommended actions. If the
alarm persists=>Step 2.2.
2.
If any remote storage array is restarting, wait until the restart completes. If the alarm
persists=>Step 3.
3.
If all remote storage arrays are working correctly=>Step 3.
Step 3 Check all local storage arrays.

1.
If any local storage array is faulty, handle the fault with recommended actions. If the alarm
persists=>Step 4.
2.
If all local storage arrays are working correctly=>Step 4.

----End
Related Information
None
2.128 0xF00E00014 No Backup Links Available

Description
No backup links available.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF00E00014
Warning
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
No backup links are configured for the remote device.
Procedure
Step 1 Configure backup links for the remote device. If the alarm persists=>Step 2.
----End
Related Information
None
2.129 0xF0C90004 CPU Usage Is Too High

Description
The CPU usage of the controller exceeds the threshold.
Attribute
ID
Event Level
0xF0C90004
Warning
Yes

The performance of the storage system deteriorates.
Possible Causes
The service load is too heavy.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.130 0xF0C90005 Memory Usage Is Too High

Description
The memory utilization rate threshold has been reached.
Attribute
ID
Event Level
0xF0C90005
Warning
Yes

The performance of the storage system deteriorates.
Possible Causes
Procedure
----End
Related Information
None
2.131 0xF00CF002F Inconsistent Memory Capacities

Between Controllers
Description
Memory capacities of two controllers are inconsistent.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00CF002F
Major
Yes

The controllers may not restart correctly.
Possible Causes
Memory capacities of controllers are inconsistent.
Procedure
----End
Related Information
None
2.132 0xF010C0014 Number Of Initiators Connected To A

Port Exceeds The System Limit
Description
The number of initiators connected to a port exceeds the system limit, causing some initiators
to fail to be connected.
Attribute
ID
Event Level
0xF010C0014
Major
Yes

Some initiators fail to be connected.
Possible Causes
The number of initiators exceeds the system limit.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Adjust the service network and ensure that the number of initiators connected to each port meet
requirements. If the alarm persists=>Step 2.
----End
Related Information
None
2.133 0x100F010C0015 iSCSI Initiator Login Failed

Description
The initiator login failed.
Attribute
ID
Event Level
0x100F010C0015
Major
Yes

N/A.
Possible Causes
CHAP user name and password are incorrect.
Procedure
Step 1 Use correct CHAP user name and password for login. If the alarm persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.134 0x100F010C0030 Number Of Initiators Connected To

A Port Exceeds The System Limit
Description
The number of initiators connected to a port exceeds the system limit.
Attribute
ID
Event Level
0x100F010C0030
Major
Yes

Hosts access to storage arrays fail.
Possible Causes
The number of initiators connected to a port exceeds the system limit.
Procedure
Step 1 Delete initiators whose state is offline. If the alarm persists=>Step 2.
----End
Related Information
None
2.135 0x100F010C0031 Initiator IP Address Is Changed

Description
The IP address of an initiator is changed.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x100F010C0031
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
l
The host corresponding to the initiator is connected to the storage system through different
IP addresses.
The initiator is used by different hosts to connect to the storage system.
Procedure
Step 1 Check whether the two different IP addresses are used by the same host.
1.
If yes, ignore this alarm.
2.
If no=>Step 2.
Step 2 Check whether the same initiator ID is used by two hosts to connect to the storage system.
1.
If yes, change the initiator ID of either host and ensure that the two initiator IDs are different.
2.
If no=>Step 3.

----End
Related Information
None
2.136 0xF010D0027 BBU Firmware Is Incompatible With

Storage Array Software
Description
The firmware version of a BBU module is incompatible with storage array software.
Attribute
ID
Event Level
0xF010D0027
Warning
Yes

The normal operation of the BBU module is not adversely affected.
Possible Causes
The firmware version of a BBU module is incompatible with storage array software.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.137 0xF010D0028 Interface Module Firmware Is

Incompatible With Storage Array Software
Description
The firmware version of an interface module is incompatible with storage array software.
Attribute
ID
Event Level
0xF010D0028
Major
Yes

The interface module fails to function.
Possible Causes
The firmware version of the interface module is incompatible with storage array software.
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.138 0xF010D0029 Expansion Module Firmware Is

Description
The firmware version of an expansion module is incompatible with storage array software.
Attribute
ID
Event Level
0xF010D0029
Major
Yes

Ports on the expansion module are isolated.
Possible Causes
The firmware version of the expansion module is incompatible with storage array software.
Procedure
----End
Related Information
None
2.139 0x200F010D0018 Failed To Delete A Hot Patch

Description
Failed to delete a hot patch.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x200F010D0018
Warning
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.140 0x200F010D001B Failed To Start An Upgrade

Description
Failed to start an upgrade.
Attribute
ID
Event Level
0x200F010D001B
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.141 0x200F010D001E Failed To Start The Upgrade Of Disk

Firmware
Description
It is failed to start the upgrade of disk firmware.
Attribute
ID
Event Level
0x200F010D001E
Warning
No

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.142 0x200F010D0021 Failed To Start The Upgrade Of Disk

Converter Firmware
Description
Failed to start the upgrade of disk converter firmware
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x200F010D0021
Warning
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.143 0x200F010D0024 Failed To Start Rollback

Description
Failed to start a rollback.
Attribute
ID
Event Level
0x200F010D0024
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.144 0x100F010D0026 Rollback Failed

Description
Rollback failed.
Attribute
ID
Event Level
0x100F010D0026
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.145 0x100F010D0027 Upgrade Failed

Description
Upgrade failed.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x100F010D0027
Warning
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.146 0xF00150019 Host Is Not Redundantly Connected To

Storage Arrays
Description
A host is not redundantly connected to storage arrays.
Attribute
ID
Event Level
0xF00150019
Major
Yes

N/A.
Possible Causes
l
The host is not redundantly connected to storage array controllers.
LUN mappings incorrectly added.
Disk scan is not performed on the host after LUN mappings are added, causing the failure
to discover some or all disks.
Procedure
Step 1 Check whether the host is connected only to one controller.
1.
Issue 04 (2015-06-10)
If yes, connect the host to multiple controllers. If the alarm persists=>Step 2.

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

V3 Storage System
Event Reference
2.
If no=>Step 2.
Step 2 Check whether initiators configured for the host are consistent with the actual condition.
1.
If yes=>Step 3.
2.
If no, add all initiators to the host based on the actual condition. If the alarm persists=>Step
3.
Step 3 Scan for disks on the host and confirm that the number of detected disks is correct. If the alarm
persists=>Step 4.
----End
Related Information
None
2.147 0xF0015001A Link Between A Host And Storage Array

Is Down
Description
The link between a host and storage array is down.
Attribute
ID
Event Level
0xF0015001A
Major
Yes

N/A.
Possible Causes
l
Cables between the host and the storage array are removed or damaged.
Optical modules are faulty.
Interface modules are faulty.
The host HBA is faulty.
Switches are faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check the cables connected between the host and the storage array.
1.
2.
1.
If yes, handle the alarms by taking recommended actions. If the alarm persists=>Step 3.
2.
If no=>Step 3.
Step 3 Check whether alarms are generated indicating port faults.

1.
2.
If no=>Step 4.
1.
2.
If no=>Step 5.
Step 5 Check whether alarms are generated indicating controller faults.

1.
2.
If no=>Step 6.
Step 6 Check the HBAs on the host. Contact the HBA provider for help when necessary.
Step 7 Check related switches. Contact the switch provider for help when necessary.
----End
Related Information
None
2.148 0xF0015001B Link Between A Host And Storage Array

Is Unstable
Description
A link between a host and storage array is unstable.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0015001B
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
l
Cables between the host and the storage array are loose or damaged.
Optical modules are faulty.
The host HBA is faulty.
Switches are faulty.
Procedure
Step 1 Check the cables connected between the host and the storage array.
1.
If any cable is loose, reinsert it. If the alarm persists=>Step 1.2.
2.
1.
2.
If no=>Step 3.
Step 3 Check whether alarms are generated indicating port faults.

1.
2.
If no=>Step 4.
Step 4 Check the HBAs on the host. Contact the HBA provider for help when necessary.
Step 5 Check related switches. Contact the switch provider for help when necessary.
----End
Related Information
None
2.149 0x100F0015001C Ultrapath Is Not Installed Or

Ultrapath Version Outdated
Description
UltraPath is not installed or the version of UltraPath is outdated.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x100F0015001C
Major
Yes

N/A.
Possible Causes
l
UltraPath is not installed on the host.
The version of the installed UltraPath is outdated.
Procedure
Step 1 Install UltraPath of the latest version on the host. If the alarm persists=>Step 2.
----End
Related Information
None
2.150 0xF0015001D Ultrapath Incompatible With Storage

Array Software
Description
UltraPath on the host is incompatible with disk array software.
Attribute
ID
Event Level
0xF0015001D
Major
Yes

N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
The UltraPath version is outdated.
The storage array software version is outdated.
Procedure
Step 1 Upgrade storage array software or UltraPath to a compatible version. If the alarm
persists=>Step 2.
----End
Related Information
None
2.151 0x100F00150036 Data Sent To A Storage Array Port By

The Host Failed To Be Verified
Description
Data sent to a storage array port by the host failed to be verified.
Attribute
ID
Event Level
0x100F00150036
Major
Yes

Data write may fail.
Possible Causes
l
The host is faulty.
The port is faulty or the link between the host and the port is down.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.152 0xF00310004 The Space That Stores Event Logs Is To

Be Used Up
Description
The space that stores event logs is to be used up.
Attribute
ID
Event Level
0xF00310004
Warning
Yes

After the number of events reaches the upper limit, earlier events are deleted.
Possible Causes
N/A.
Procedure
Step 1 Configure the event log dumping server and open the dumping switch. After the dumping
finished, if the alarm persists=>Step 2.
----End
Related Information
None
2.153 0xD80001 Storage Pool Remaining Capacity Is

Insufficient
Description
The used capacity of a storage pool reachs the threshold.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xD80001
Major
Yes

N/A.
Possible Causes
The used capacity of the storage pool reachs the threshold.
Procedure
Step 1 Expand the capacity of the storage pool. If the alarm persists=>Step 2.
----End
Related Information
None
2.154 0xD80002 Storage Pool Capacity Is About To Be Used

Up
Description
The storage pool capacity is about to be used up, which may cause service interruption on this
pool.
Attribute
ID
Event Level
0xD80002
Critical
Yes

Some services on the storage pool may be interrupted.
Possible Causes
The storage pool capacity is about to be used up.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.155 0x10A0001 Disk Domain Is Degraded

Description
A disk domain is degraded.
Attribute
ID
Event Level
0x10A0001
Major
Yes

Storage pools using the disk domain may become faulty, causing LUNs and snapshots to fail.
Possible Causes
l
Member disks are removed.
Member disks are faulty.
Procedure
Step 1 Check whether alarms are generated indicating disk removal.
1.
If yes, reinsert the removed disks. If the alarm persists=>Step 2.
2.
If no=>Step 2.

1.
If yes, replace the faulty disks. If the alarm persists=>Step 3.
2.
If no=>Step 3.

----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.156 0x10A0002 Disk Domain Is Faulty

Description
A disk domain is faulty.
Attribute
ID
Event Level
0x10A0002
Critical
Yes

Storage pools using the disk domain may become faulty, causing LUNs and snapshots to fail.
Possible Causes
l
Procedure
1.
If yes, reinsert the removed disks.
2.
If no=>Step 2.

1.
2.
If no=>Step 3.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.157 0x10A0003 Disk Domain Is Offline

Description
A disk domain is offline.
Attribute
ID
Event Level
0x10A0003
Critical
Yes

All LUNs and snapshots in the disk domain go offline.
Possible Causes
l
Procedure
1.
If yes, reinsert the removed disks.
2.
If no=>Step 2.

1.
2.
If no=>Step 3.

----End
Related Information
None
2.158 0x10A0005 Hot Spare Capacity Of The Disk Domain

Is Insufficient
Description
The host spare capacity for a disk domain is insufficient.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x10A0005
Major
Yes

N/A.
Possible Causes
The remaining hot spare capacity is lower than the threshold.
Procedure
Step 1 Add disks to the disk domain. If the alarm persists=>Step 2.
----End
Related Information
None
2.159 0x10A0006 Inconsistent Disk Domain Disk Types

Description
Disks in a disk domain are different in type.
Attribute
ID
Event Level
0x10A0006
Major
Yes

The disk fails to work.
Possible Causes
The type of the newly added disk is inconsistent with that of the existing disks in the disk domain.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Replace the newly added disk with a one that meets system requirements. If the alarm
persists=>Step 2.
----End
Related Information
None
2.160 0x10A0007 Number Of Disks In A Disk Domain Does

Not Meet Hot Spare Requirements
Description
The number of disks in a disk domain does not meet hot spare requirements.
Attribute
ID
Event Level
0x10A0007
Warning
Yes

N/A.
Possible Causes
The number of disks in the disk domain is insufficient.
Procedure
Step 1 Add disks to the disk domain. If the alarm persists=>Step 2.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.161 0x10A0008 A Disk Is Removed From A Disk Domain

Description
A disk is removed from a disk domain.
Attribute
ID
Event Level
0x10A0008
Major
Yes

N/A.
Possible Causes
A disk is removed from a disk domain.
Procedure
Step 1 Add the removed disk to the disk domain. If the alarm persists=>Step 2.
----End
Related Information
None
2.162 0x1000010A000B The Disk Domain Reconstruction

Failed
Description
Disk domain reconstruction failed.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x1000010A000B
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
l
Disk domain capacity is insufficient.
Disks are removed.
Disks are faulty.
Procedure
Step 1 Check whether alarms are generated indicating insufficient disk domain capacity.
1.
If yes, add disks to the disk domain. If the alarm persists=>Step 2.
2.
If no=>Step 2.

1.
2.
If no=>Step 3.

1.
2.
If no=>Step 4.

----End
Related Information
None
2.163 0x1000010A000E Precopy Failed

Description
The precopy of a disk domain failed.
Attribute
ID
Event Level
0x1000010A000E
Major
Yes

N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
Disk domain capacity is insufficient.
Disks are removed.
Disks are faulty.
Procedure
Step 1 Check whether alarms are generated indicating insufficient disk domain capacity.
1.
If yes, add disks to the disk domain. If the alarm persists=>Step 2.
2.
If no=>Step 2.

1.
2.
If no=>Step 3.

----End
Related Information
None
2.164 0x1000010A0011 Data Balancing Failed

Description
A disk domain failed to balance data automatically.
Attribute
ID
Event Level
0x1000010A0011
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.165 0x10A001C Disk Domain Member Disk Is Inserted

Into An Incorrect Slot
Description
Disk domain member disk is inserted into an lncorrect slot.
Attribute
ID
Event Level
0x10A001C
Major
Yes

N/A.
Possible Causes
The member disk is inserted into a slot different from where it was inserted before being
removed.
Procedure
Step 1 Insert the disk into the slot where it resided before it was removed. If the alarm persists=>Step
2.
----End
Related Information
None
2.166 0x10C000B Controller Write Cache Is Disabled

Description
Controller write cache is disabled.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x10C000B
Major
Yes

N/A.
Possible Causes
l
Disks are removed.
Disks are faulty.
Procedure
Step 1 Check whether any disk is removed.
1.
If yes, reinsert the removed disk. If alarm Controller Write Cache Is Disabled
persists=>Step 2.
2.
If no=>Step 2.

1.
If yes, replace the faulty disks. If alarm Controller Write Cache Is Disabled persists=>Step
3.
2.
If no=>Step 3.

----End
Related Information
None
2.167 0x10C000C Write Cache For A Cache Partition Is

Disabled
Description
Write cache for a cache partition is disabled.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x10C000C
Major
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
l
Disks are removed.
Disks are faulty.
Procedure
Step 1 Check whether any disk is removed.
1.
If yes, reinsert the removed disk. If the alarm persists=>Step 2.
2.
If no=>Step 2.

1.
2.
If no=>Step 3.

----End
Related Information
None
2.168 0xFD0008 LUN Migration Is Faulty

Description
LUN Migration is faulty.
Attribute
ID
Event Level
0xFD0008
Major
Yes

N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
The source LUN of LUN migration is faulty.
The target LUN of LUN migration is faulty.
Procedure
Step 1 Check whether alarms are generated for the storage pools that house the source and target LUNs.
1.
If yes, handle alarms with recommended actions. If the alarm persists=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.169 0xF00CE002B From An Expansion Port, Disk

Enclosures And High-Density Disk Enclosures Are MixConnected
Description
From an expansion port, disk enclosures and high-density disk enclosures are mix-connected.
Attribute
ID
Event Level
0xF00CE002B
Warning
Yes

Subsequent disk enclosures that are of different types cannot be connected.
Possible Causes
From the same expansion port, disk enclosures and high-density disk enclosures are mixconnected.
Procedure
Step 1 Check whether from the port the connected disk enclosures are of the same type.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
If yes=>Step 2.
2.
If no=>Replace some disk enclosures to ensure that all disk enclosures connected from the
expansion port are of the same type. If the alarm persists=>Step 2.

----End
Related Information
None
2.170 0xF000B0063 External LUN Has Links To Only One

Controller
Description
External LUN has links to only one controller.
Attribute
ID
Event Level
0xF000B0063
Major
Yes

As no redundant link is available, the reliability is reduced and online upgrade may fail.
Possible Causes
l
Only one link is connected.
The initiator of a link is deleted.
The mapping of the external LUN is deleted.
Procedure
Step 1 Check whether only one controller has a link to the external LUN.
1.
If yes, connect the link based on the standard network in the related product manual.
2.
If no=>Step 2.
Step 2 Check whether the initiator of a link is removed.

1.
If yes, add the initiator back.
2.
If no=>Step 3.
Step 3 Check whether the mapping of the corresponding external LUN has been deleted.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
If yes, add the mapping.
2.
If no=>Step 4.
Step 4 Collect related event information and contact technical support.

----End
Related Information
None
2.171 0xF000B0064 External LUN Offline

Description
External LUN is offline.
Attribute
ID
Event Level
0xF000B0064
Major
Yes

The eDevLUN and related features become faulty.
Possible Causes
l
The external LUN's link is disconnected.
The initiator of the external LUN's link is deleted.
Procedure
Step 1 Check whether link between the external array and the local array is disconnected.
1.
If yes, connect the link based on the standard network in the related product manual. If the
fault persists=>Step 2.
2.
If no=>Step 2.

1.
If yes, add the initiator back. If the fault persists=>Step 3.
2.
If no=>Step 3.
1.
If yes, add the mapping. If the fault persists=>Step 4.
2.
If no=>Step 4.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.172 0xF000B0065 External LUN Faulty

Description
External LUN is faulty.
Attribute
ID
Event Level
0xF000B0065
Major
Yes

The eDevLun and related features become faulty.
Possible Causes
l
The external LUN is faulty.
The initiator of the external LUN's link is deleted.
Procedure
Step 1 Check whether any disk is removed from the external array.
1.
If yes, reinsert the disk to recover the external LUN. If the fault persists=>Step 2.
2.
If no=>Step 2.

1.
2.
If no=>Step 3.
1.
If yes, add the mapping. If the fault persists=>Step 4.
2.
If no=>Step 4.
Step 4 Run the LUN scan command on the heterogeneous array to which the external LUN belongs. If
the alarm persists=>Step 5.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.173 0xF000B0066 External LUN Downsized

Description
External LUN is downsized.
Attribute
ID
Event Level
0xF000B0066
Major
Yes

The eDevLUN and related features become faulty.
Possible Causes
The external LUN is downsized.
Procedure
Step 1 Expand the capacity of the corresponding external LUN to not less than its original capacity. If
Step 2 Run the LUN scan command on the heterogeneous array to which the external LUN belongs.
----End
Related Information
None
2.174 0xF000B0052 Incompatible Heterogeneous Array

Connected To The System
Description
Incompatible heterogeneous array is connected to the system.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF000B0052
Warning
No

The incompatibility issue may interrupt services.
Possible Causes
l
An incorrect storage array is connected.
The system lacks the support package for the heterogeneous array.
Procedure
Step 1 If the external LUNs of this heterogeneous array have been used to create eDevLUN, please
delete these eDevLUNs first.
Step 2 Disconnect all physical links between the heterogeneous array and the local array. If the system
has connected to other heterogeneous arrays whose SN can not be obtained, or the system has
connected to other incompatible arrays, you need to manually clear the alarms.
Step 3 If you have to connect this heterogeneous array, load the support package first and then reconnect
the heterogeneous array.
----End
Related Information
None
2.175 0xF000B005D FC Link Of Heterogeneous Array

Disconnected
Description
FC link of heterogeneous array is disconnected.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF000B005D
Major
No

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

V3 Storage System
Event Reference

This may cause the external LUN to have a single link or get offline.
Possible Causes
l
The external array is powered off.
An FC switch is powered off.
An FC link is disconnected.
Procedure
Step 1 Check whether the external array is powered off. If the external array is powered off, power it
on again. If the alarm persists=>Step 2.
Step 2 Check whether any FC switch is powered off. If any FC switch is powered off, power it on again.
If the alarm persists=>Step 3.
Step 3 Check whether any FC link is removed or damaged.
1.
If any FC link is removed, reconnect it correctly. If the alarm persists=>Step 4.
2.
If any FC link is damaged, replace it with a new link and connect the new link correctly.
Step 4 Collect related event information and contact technical support engineers.
----End
Related Information
None
2.176 0xF000B0060 iSCSI Link Of Heterogeneous Array

Disconnected
Description
iSCSI link of heterogeneous array is disconnected.
Attribute
ID
Event Level
0xF000B0060
Major
No

This may cause the external LUN to have a single link or get offline.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
The external array is powered off.
An GE switch is powered off.
An iSCSI link is disconnected.
Procedure
Step 1 Check whether the external array is powered off. If the external array is powered off, power it
on again. If the alarm persists=>Step 2.
Step 2 Check whether any GE switch is powered off. If any GE switch is powered off, power it on
again. If the alarm persists=>Step 3.
Step 3 Check whether any iSCSI link is removed or damaged.
1.
If any iSCSI link is removed, reconnect it correctly. If the alarm persists=>Step 4.
2.
If any iSCSI link is damaged, replace it with a new link and connect the new link correctly.
----End
Related Information
None
2.177 0xF000B0061 FC Link Of Heterogeneous Array Faulty

Description
FC link of heterogeneous array is faulty.
Attribute
ID
Event Level
0xF000B0061
Major
No

Data cannot be transferred over this link, reducing reliability.
Possible Causes
l
The initiator is deleted.
The link has a bit error.
The link connection is faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check whether the initiator of the link has been removed.
1.
2.
If no=>Step 2.
Step 2 Check whether the link is properly connected or damaged.

1.
If the link is not properly connected, reinsert it. If the fault persists=>Step 3.
2.
If the link is damaged, replace it with a new one and insert the new one to the original port.
If the fault persists=>Step 3.
Step 3 Check whether any switch is damaged. If a switch is damaged, replace it with a new one and
reinsert all links to the new switch correctly. If the fault persists=>Step 4.
----End
Related Information
None
2.178 0xF000B0062 iSCSI Link Of Heterogeneous Array

Faulty
Description
iSCSI link of heterogeneous array is faulty.
Attribute
ID
Event Level
0xF000B0062
Major
No

Data cannot be transferred over this link, reducing reliability.
Possible Causes
l
The initiator is deleted.
The link has a bit error.
The link connection is faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check whether the initiator of the link has been removed.
1.
2.
If no=>Step 2.
Step 2 Check whether the link is properly connected or damaged.

1.
If the link is not properly connected, reinsert it. If the fault persists=>Step 3.
2.
If the link is damaged, replace it with a new one and insert the new one to the original port.
If the fault persists=>Step 3.
Step 3 Check whether any switch is damaged. If a switch is damaged, replace it with a new one and
reinsert all links to the new switch correctly. If the fault persists=>Step 4.
----End
Related Information
None
2.179 0x200F000A005B The Hard Disk Is Isolated

Description
The hard disk is isolated.
Attribute
ID
Event Level
0x200F000A005B
Major
Yes

The hard disk is in single-link state.
Possible Causes
N/A.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.180 0xF00280045 File System Is Faulty

Description
File system is faulty.
Attribute
ID
Event Level
0xF00280045
Critical
Yes

File systems cannot be accessed.
Possible Causes
The related disks are faulty.
Procedure
----End
Related Information
None
2.181 0xF00280046 File System Has A Medium Error

Description
File system has a medium error.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF00280046
Critical
Yes

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

V3 Storage System
Event Reference

The reliability of data stored on the file system deteriorates.
Possible Causes
The disk has bad sectors.
Procedure
Step 1 1 Check whether the file system has a backup.
1.
If yes, rewrite the file system by using the backup data for data recovery purposes.
2.
If no, contact technical support engineers.
----End
Related Information
None
2.182 0xF00280047 Remaining Capacity In A File System Is

Insufficient
Description
The remaining capacity in a file system is insufficient.
Attribute
ID
Event Level
0xF00280047
Major
Yes

l
Files may be writted in writethrough mode, degrading file system read and write
performance.
Users may fail to write data into the file system.
Possible Causes
The rate of used capacity in the file system exceeds the alarm threshold.
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Expand the capacity of the file system or delete unnecessary files.

----End
Related Information
None
2.183 0xF00280048 Used Resource Of A File System Quota

Exceeds The Soft Quota
Description
Used resource of a file system quota exceeds the soft quota.
Attribute
ID
Event Level
0xF00280048
Major
Yes

N/A.
Possible Causes
Used resource of a file system quota exceeds the soft quota.
Procedure
Please expand the soft quota or delete some files.
----End
Related Information
None
2.184 0xF00280049 File System Has A Checksum Error

Description
File system has a checksum error.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00280049
Critical
Yes

None
Possible Causes
N/A.
Procedure
Step 1 Check whether the filesystem has a backup.
1.
If yes, rewrite the filesystem by using the backup data for data recovery purposes.
2.
If no =>Step 2.

----End
Related Information
None
2.185 0x100F0028004A File System Has A Memory

Allocation Error
Description
File system has a memory alloc error.
Attribute
ID
Event Level
0x100F0028004A
Critical
Yes

None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.186 0x10A0021 Failed To Add The New Disk To The Disk

Domain
Description
The encrypt type of the new disk is inconsistent with the disk domain.
Attribute
ID
Event Level
0x10A0021
Major
No

The type of disk domain is different from the new disk. The new disk is unavailable.
Possible Causes
l
The disk domain is not encrypted, but the encryption function of the disk is enabled.
The disk domain is encrypted, but the disk does not have the encryption function.
The encryption type of the new disk is different from that of the disks in the disk domain.
Procedure
Step 1 Check the encrypt status of the disk domain.
1.
Check encrypt status of the disk domain.

l The disk domain is encrypted=>Step 2.
l The disk domain is not encrypted=>Step 1.2.
2.
Issue 04 (2015-06-10)
Disable the encryption function of the disk manually or insert a disk without the encryption
function.
162
OceanStor 5300 V3&5500 V3&5600 V3&5800 V3&6800

V3 Storage System
Event Reference
l If the alarm persists=>Step 3.

Step 2 Check encrypt status of the disk.
1.
Check the disk encrypt status.

l The disk is not encrypted=>Step 2.3.
l The disk is encrypted=>Step 2.2.
2.
Check the encrypt type of the new disk and the other disks in the disk domain.
l The encrypted type of disks is the same=>Step 3.
l If not =>Step 2.3.
3.
Insert another disk with the same encryption type.

l If the alarm persists=>Step 3.

----End
Related Information
None
2.187 0x10A0020 A New Disk Fails to Be Added To The Disk

Domain
Description
The capacity of the newly replaced disk is insufficient so that the disk cannot be added to this
disk domain.
Attribute
ID
Event Level
0x10A0020
Major
Yes

The disk fails to work.
Possible Causes
A member disk of the disk domain is replaced by a new disk with smaller capacity.
Procedure
Step 1 Replace the newly added disk with a disk that meets system requirements. If the alarm persists
=>Step 2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.188 0xF4045000E Adding To An AD Domain Fails

Description
Adding to an AD domain([domain_name]) fails.
Attribute
ID
Event Level
0xF4045000E
Major
No

Domain authentication fails. Domain services are affected.
Possible Causes
l
The device is incorrectly communicating with the AD domain controller.
The DNS of the device is incorrectly configured.
The system time of the device is different from that of the AD domain controller.
Procedure
Step 1 Check the network connectivity between the device and AD domain controller.
1.
Check whether the device is correctly communicating with the AD domain controller.
l If yes=>Step 2.
l If no=>Step 1.2.
2.
Contact the network administrator to rectify the network fault. Then check whether the
alarm is cleared.
l If yes=>Step 2.
l If no=>no further action is required.
Step 2 Check the DNS configuration of the device.

1.
Check whether the DNS of the device is incorrectly configured.

l If yes=>Step 3.
l If no=>Step 2.2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.
Reconfigure the DNS. Then check whether the alarm is cleared.

l If yes=>Step 3.
Step 3 Check the system time of the device and that of the AD domain controller.
1.
Check whether the difference between the system time of the device and that of the AD
domain controller is less than 5 minutes.
l If yes=>Step 4.
l If no=>Step 3.2.
2.
Ensure that the difference between the system time of the device and that of the AD domain
controller is less than 5 minutes. Then check whether the alarm is cleared.
l If yes=>Step 4.
Step 4 Contact technical support engineers.

----End
Related Information
None
2.189 0x200F4045000F No Domain Controller Is Available

Description
A NAS node is disconnected from all domain controllers.
Attribute
ID
Event Level
0x200F4045000F
Major
No

Domain authentication fails. Domain services are affected.
Possible Causes
l
The AD domain controller is shut down.
The device is incorrectly communicating with the AD domain controller.
Procedure
Step 1 Check the status of the AD domain controller.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
Check whether the AD domain controller is started.

l If yes=>Step 2.
l If no=>Step 1.2.
2.
Start the AD domain controller. Then check whether the alarm is cleared.
l If yes=>no further action is required.
l If no=>Step 2.
Step 2 Check the network connectivity between the device and AD domain controller.
1.
Check whether the device is correctly communicating with the AD domain controller.
l If yes=>Step 3.
l If no=>Step 2.2.
2.
alarm is cleared.
l If no=>Step 3.

----End
Related Information
None
2.190 0xF40020001 The Ndmp Service Process Is Abnormal

Description
The NDMP service process is abnormal.
Attribute
ID
Event Level
0xF40020001
Major
No

N/A.
Possible Causes
The critical process is abnormal.
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Contact technical support engineers.

----End
Related Information
None
2.191 0xF40020002 A Service Port Conflicts

Description
A service port conflicts.
Attribute
ID
Event Level
0xF40020002
Major
No

Service cannot be accessed.
Possible Causes
The service port is occupied by another program.
Procedure
View the system port list and stop the program that occupies the service port.
----End
Related Information
None

Description
Fan hardware is faulty, causing abnormal fan speed.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0D30004
Major
Yes

l
system.
Possible Causes
Procedure
Step 1 Replace the fan module. If the alarm persists=>Step 2.
----End
Related Information
None
2.193 0xF00D1001F Management Module Is Faulty

Description
Management module hardware is faulty.
Attribute
ID
Event Level
0xF00D1001F
Major
Yes

l
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
SSDs are faulty.
Procedure
Step 1 Replace the management module. If the alarm persists=>Step 2.
----End
Related Information
None

Description
Interface module hardware is faulty.
Attribute
ID
Event Level
0xF00D10020
Major
Yes

Possible Causes
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.195 0xF00170018 The Power Module Is Incompatible With

The Storage System
Description
The power module is incompatible with the storage system.
Attribute
ID
Event Level
0xF00170018
Major
Yes

l
Possible Causes
The power module is incompatible with the storage system.
Procedure
----End
Related Information
None
2.196 0xF00EA0018 The System Failed To Monitor An

Optical/Electrical Module
Description
The system failed to monitor an optical/electrical module.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00EA0018
Major
Yes

N/A.
Possible Causes
l
The electrical module is faulty.
Procedure
Step 1 Check whether an alarm is generated indicating an optical/electrical module fault.
1.
If yes, replace the faulty optical/electrical module. If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace the interface module where the faulty optical/electrical module resides. If the alarm
persists =>Step 3.
Step 3 Replace the controller corresponding to the faulty optical/electrical module. If the alarm
persists=>Step 4.
----End
Related Information
None
2.197 0x200F0D1000D The System Failed To Power Off An

Interface Module
Description
The system failed to power off an interface module.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0x200F0D1000D
Warning
Yes

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

V3 Storage System
Event Reference

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.198 0x200F0D10010 The System Failed To Power On An

Interface Module
Description
The system failed to power on an interface module.
Attribute
ID
Event Level
0x200F0D10010
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.199 0x200F00D10017 The System Failed to Power Off An

Interface Module
Description
The system failed to power off an interface module.
Attribute
ID
Event Level
0x200F00D10017
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.200 0x200F00D1001C The System Failed to Power On An

Interface Module
Description
The system failed to power on an interface module.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x200F00D1001C
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.201 0x200F00C90088 Succeeded In Deleting All

Configurations Of System
Description
Succeeded in deleting all configurations of system.
Attribute
ID
Event Level
0x200F00C90088
Warning
Yes

N/A.
Possible Causes
N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
N/A.
----End
Related Information
None
2.202 0x200F00C90089 Failed To Delete All Configurations

Of System
Description
Failed to delete all configurations of system.
Attribute
ID
Event Level
0x200F00C90089
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
N/A.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.203 0xF00CA0008 The Super Administrator Needs To

Review User Account Information
Description
When the user account information review switch is on, the super administrator needs to review
user account information periodically. Clear the alarm manually when it is done.
Attribute
ID
Event Level
0xF00CA0008
Warning
No

N/A.
Possible Causes
The super administrator needs to review user account information periodically.
Procedure
After reviewing user account information, clear the alarm manually.
----End
Related Information
None
2.204 0xF40450029 No LDAP/NIS Server Is Available

Description
A NAS node is disconnected from all LDAP/NIS Servers.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF40450029
Major
Yes

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

V3 Storage System
Event Reference

LDAP/NIS authentication fails. LDAP/NIS services are affected.
Possible Causes
l
The LDAP/NIS server is shut down.
The device is incorrectly communicating with the LDAP/NIS server.
Procedure
Step 1 Check the status of the LDAP/NIS server.
1.
Check whether the LDAP/NIS server is started.

l If yes=>Step 2.
l If no=>Step 1.2.
2.
Start the LDAP/NIS server. Then check whether the alarm is cleared.
l If no=>Step 2.
Step 2 Check the network connectivity between the device and LDAP/NIS server.
1.
Check whether the device is correctly communicating with the LDAP/NIS server.
l If yes=>Step 3.
l If no=>Step 2.2.
2.
alarm is cleared.
l If no=>Step 3.

----End
Related Information
None
2.205 0xF02470010 Mirror Copy Is Abnormally Interrupted

Description
A mirror copy is abnormally interrupted.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF02470010
Critical
Yes

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

V3 Storage System
Event Reference

Data cannot be written onto or read from the mirror copy.
Possible Causes
l
The storage pool is faulty.
The mirror copy is faulty.
Procedure
Step 1 Check whether alarms are generated for the storage pool that houses the mirror copy.
1.
If yes, handle alarms with recommended actions. If the alarm persists=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.206 0xF02470011 Mirror Copy Is Unavailable

Description
A mirror copy is unavailable.
Attribute
ID
Event Level
0xF02470011
Critical
Yes

The mirror copy is unavailable.
Possible Causes
Configurations of the mirror copy are abnormal.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Please remove the mirror copy. If the operation fails=>Step 2.
----End
Related Information
None
2.207 0xF032C0001 The SSH Service Is Abnormal

Description
The SSH service of a controller is abnormal, so users cannot log in to the controller using SSH.
Attribute
ID
Event Level
0xF032C0001
Warning
No

Users cannot log in to the controller using SSH.
Possible Causes
l
The SSH-based login management process is abnormal.
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.208 0xF032C0002 The FTP Service Is Abnormal

Description
The FTP service of a controller is abnormal, so data cannot be transferred through FTP.
Attribute
ID
Event Level
0xF032C0002
Warning
No

Data such as log management data cannot be transferred.
Possible Causes
l
The FTP-based file transfer process is abnormal.
Procedure
----End
Related Information
None
2.209 0xF032C0003 NTP Time Synchronization Is Abnormal

Description
A controller is incorrectly connected to an NTP server, so time synchronization between them
fails.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF032C0003
Warning
No

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

V3 Storage System
Event Reference

Time synchronization between the controller and NTP server fails.
Possible Causes
l
The NTP client is faulty.
The NTP server is faulty.
Procedure
Step 1 Check whether the network connection between the controller and NTP server is correct.
1.
If yes=>Step 2.
2.
If no=>rectify the network connection fault. If the alarm persists=>Step 2.
Step 2 Check whether the NTP service of the NTP server is correct.
1.
If yes=>Step 3.
2.
If no=>recover the NTP service. If the alarm persists=>Step 3.

----End
Related Information
None
2.210 0xF032C0004 The Network Protocol Stack Of A

Controller Is Abnormal
Description
A controller fails to ping 127.0.0.1.
Attribute
ID
Event Level
0xF032C0004
Critical
No

Network packets fail to be sent.
Possible Causes
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.211 0xF032C0005 The Process CPU Usage Is Too High

Description
The CPU usage of a process in a controller exceeds a threshold.
Attribute
ID
Event Level
0xF032C0005
Warning
No

Storage system performance deteriorates.
Possible Causes
Procedure
Step 1 Check whether the service load of the host is too heavy.
----End
Related Information
None
2.212 0xF032C0006 The Process Memory Usage Is Too High

Description
The memory usage of a process in a controller exceeds a threshold.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF032C0006
Warning
No

Possible Causes
Procedure
----End
Related Information
None
2.213 0xF032C0007 A Directory Is Oversized

Description
Disk space occupied by all the files in a directory exceeds a threshold.
Attribute
ID
Event Level
0xF032C0007
Warning
No

Possible Causes
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.214 0xF032C0008 Excessive Files Exist In A Directory

Description
The number of files in a directory exceeds a threshold.
Attribute
ID
Event Level
0xF032C0008
Warning
No

Possible Causes
Procedure
----End
Related Information
None
2.215 0x200F00CF003A The Heartbeat Connection Between

A Controller And A Management Module Is Interrupted
Description
The heartbeat connection between a controller and a management module is interrupted. As a
result, the controller cannot access the management module.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x200F00CF003A
Major
Yes

The controller cannot access the management module.
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating management module faults.
1.
If yes, replace the faulty management module. If the alarm persists, =>Step 2.
2.
If no, =>Step 2.
Step 2 Replace the corresponding controller. If the alarm persists, =>Step 3.

----End
Related Information
None
2.216 0xF00D10011 The PCIe Channel Between An Interface

Module And A Controller Is Abnormal
Description
The PCIe channel between an interface module and a controller is abnormal.
Attribute
ID
Event Level
0xF00D10011
Major
Yes

The interface module fails to work correctly.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
Procedure
1.
If yes, replace the faulty interface module. If the alarm persists, =>Step 2.
2.
If no, =>Step 2.
Step 2 Replace the corresponding controller. If the alarm persists, =>Step 3.

----End
Related Information
None
2.217 0xF000A005F Slow Disk Response

Description
A disk responds slowly.
Attribute
ID
Event Level
0xF000A005F
Major
Yes

The storage pool that houses the disk may have compromised I/O performance or even degrade.
Possible Causes
l
The disk is faulty.
Expansion ports are partially damaged.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
1.
If yes, replace the faulty disks. If alarm Slow Disk Response persists=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether any expansion port is faulty.

1.
If yes, replace the interface module where the faulty port resides. If alarm Slow Disk
Response persists=>Step 3.
2.
If no=>Step 3.

1.
If no, reinsert the disk. If alarm Slow Disk Response persists=>Step 4.
2.
If yes=>Step 4.
1.
If yes, replace the faulty expansion modules. If alarm Slow Disk Response persists=>Step
5.
2.
If no=>Step 5.

----End
Related Information
None
2.218 0x200F010D0029 Failed To Start Dispatch Upgrade

Package
Description
Failed To Start Dispatch Upgrade Package
Attribute
ID
Event Level
0x200F010D0029
Warning
Yes

N/A.
Possible Causes
N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
----End
Related Information
None
2.219 0x100F010D0031 Dispatch Upgrade Package Failed

Description
Dispatch Upgrade Package Failed
Attribute
ID
Event Level
0x100F010D0031
Warning
Yes

N/A.
Possible Causes
N/A.
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.220 0xF00D10012 Interface Module Is Inserted Into An

Incorrect Slot
Description
An interface module is inserted into an incorrect slot in an engine or a disk enclosure.
Attribute
ID
Event Level
0xF00D10012
Major
Yes

l
The interface module fails to work.
Controllers may fail to start.
Possible Causes
Interface module is inserted into an incorrect slot.
Procedure
Step 1 Insert the interface module into a correct slot. If the alarm persists=>Step 2.
----End
Related Information
None
2.221 0xF00280074 File System Metadata Is Damaged

Description
File system data is damaged.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF00280074
Critical
Yes

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

V3 Storage System
Event Reference

Some services will be damaged and some data may lose.
Possible Causes
None.
Procedure
----End
Related Information
None
2.222 0xF00280075 Write Protection Is Enabled For The File

System
Description
Write protection is enabled for the file system.
Attribute
ID
Event Level
0xF00280075
Critical
Yes

The file can be read only.
Possible Causes
N/A.
Procedure
----End
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Related Information
None
2.223 0xF00280076 Files Or Directories Are Damaged.

Description
Files or directories are damaged.
Attribute
ID
Event Level
0xF00280076
Major
Yes

Some data in the damaged files or directories may lose.
Possible Causes
N/A.
Procedure
----End
Related Information
None
2.224 0xF000B0102 External LUN Is Changed To Command

Device
Description
External LUN is changed to command device.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF000B0102
Major
No

When reconnecting the physical links related, this LUN can not access.
Possible Causes
The remote LUN related is changed to command device.
Procedure
Step 1 Confirm the reason for this operation of this LUN.
1.
If the customer changed this LUN to command device on purpose=>Step 2.
2.
If it's a misoperation, change this LUN back to normal LUN=>Step 4.
Step 2 Check whether the LUN is used or not.

1.
If the LUN is used, stop dispatching I/O to this LUN and delete the eDevLUN
related=>Step 3.
2.
if the LUN is not used=>Step 3.
Step 3 Unmap this LUN and rescan for remote LUNs=>Step 4.

Step 4 Clear the alarm manually.
----End
Related Information
None
2.225 0xF00D10013 Some Statuses Of A Management

Module Cannot Be Monitored
Description
Some statuses of a management module cannot be monitored, because internal communication
links are faulty. As a result, the system cannot determine whether the management module is
correctly inserted.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00D10013
Major
Yes

l
The system cannot monitor some statuses of the management module.
The system cannot detect whether the management module is correctly inserted.
Possible Causes
l
Procedure
Step 1 Replace the faulty management module. If the alarm persists=>Step 2.
----End
Related Information
None
2.226 0xF00CF004A Some Statuses Of A Controller Cannot

Be Monitored
Description
Some statuses of a controller cannot be monitored, because internal communication links are
faulty. As a result, the system cannot determine whether the controller is correctly inserted.
Attribute
ID
Event Level
0xF00CF004A
Major
Yes

l
Issue 04 (2015-06-10)
Service switchover between controllers is affected.

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

V3 Storage System
Event Reference
The system cannot monitor some statuses of the controller.
The system cannot detect whether the controller is correctly inserted.
Possible Causes
l
Procedure
Step 1 Replace the faulty controller. If the alarms persist=>Step 2.
----End
Related Information
None
2.227 0xF01050017 Switch Temperature Is Below The Lower

Limit
Description
The temperature of a switch is below the lower limit.
Attribute
ID
Event Level
0xF01050017
Major
Yes

Possible Causes
Procedure
Step 1 Check whether the ambient temperature is too low.
1.
2.
If no=>Step 2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.228 0xF0105001E Switch Management Network Port Is

Faulty
Description
The management network port on a switch is faulty.
Attribute
ID
Event Level
0xF0105001E
Warning
Yes

N/A.
Possible Causes
The management network port is faulty.
Procedure
----End
Related Information
None
2.229 0xF0105001F Switch Port Is Faulty

Description
A switch port module is faulty.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF0105001F
Major
Yes

N/A.
Possible Causes
The port is faulty.
Procedure
----End
Related Information
None
2.230 0xF01050022 Switch Port Optical Module Is Faulty

Description
The optical module of a switch port is faulty.
Attribute
ID
Event Level
0xF01050022
Major
Yes

N/A.
Possible Causes
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Replace the PCIe cable. If the alarm persists=>Step 2.
----End
Related Information
None
2.231 0xF01050024 Switch Port Negotiated Rate Is Smaller

Than The Allowed Maximum
Description
The negotiated rate of a switch port is smaller than the allowed maximum.
Attribute
ID
Event Level
0xF01050024
Warning
Yes

Possible Causes
l
The rate of the ports peer port is smaller than that of the port.
The cable to the port is loose or damaged.
A port component is faulty.
Procedure
Step 1 Check whether the rate of the ports peer port is smaller than that of the port.
1.
If no=>Step 2.
2.
If yes=>no further action is required.

1.
Connect the cable correctly to the port. If the alarm persists=>Step 2.2.
2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference

----End
Related Information
None
2.232 0xF01050025 Switch Optical Module Temperature Is

Below The Lower Limit
Description
The temperature of a switch optical module is below the lower limit.
Attribute
ID
Event Level
0xF01050025
Major
Yes

N/A.
Possible Causes
l
Procedure
Step 1 Check whether the ambient temperature is too low.
1.
2.
If no=>Step 2.
1.
If yes, replace the PCIe cable. If the alarm persists=>Step 3.
2.
If no=>Step 3.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.233 0xF01050026 Link To A Switch Port Is Abnormal

Description
The link to a switch port is abnormal.
Attribute
ID
Event Level
0xF01050026
Major
Yes

N/A.
Possible Causes
l
Cables are damaged or not firmly inserted into its slot.
The optical module of the port or that of the ports peer port is faulty.
The port or its peer port is faulty.
Procedure
1.
Reinsert the cable. If the alarm persists=>Step 1.2.
2.
----End
Related Information
None
2.234 0xF01050027 Failed To Monitor A Switch Optical

Module
Description
The system failed to monitor a switch optical module.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF01050027
Major
Yes

N/A.
Possible Causes
l
Procedure
1.
If yes, replace the faulty PCIe cable. If the alarm persists=>Step 2.
2.
If no=>Step 2.

----End
Related Information
None
2.235 0xF01050029 Switch Optical Module Temperature Is

Too High
Description
The temperature of a switch optical module exceeds the upper limit.
Attribute
ID
Event Level
0xF01050029
Major
Yes

N/A.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating the overheating of the engine or enclosure that
1.
If yes, lower the existing air conditioners temperature or add more air conditioners. If the
alarm persists=>Step 2.
2.
If no=>Step 2.
1.
If yes, replace the faulty PCIe cable. If the alarm persists=>Step 3.
2.
If no=>Step 3.

----End
Related Information
None
2.236 0xDA0005 A Member Disk Of A SmartCache Pool Gets

A Fault
Description
A member disk of a SmartCache pool gets a fault.
Attribute
ID
Event Level
0xDA0005
Major
Yes

The I/O performace of LUN and file system accelerated by SmartCache may be compromised.
Possible Causes
l
The disk is pulled out.
The disk gets a fault.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check whether the disk is pulled out.
1.
If yes, insert in the disk which has been pulled out. If the alarm persists after you perform
this operation=>Step 3.
2.
If no=>Step 2.
Step 2 Check whether the disk gets a fault.

1.
If yes, replace the faulty disk with a new disk. If the alarm persists after you perform this
operation=>Step 3.
2.
If no=>Step 3.

----End
Related Information
None
2.237 0x200F406E0013 An Ndmp Backup Task Fails

Description
An NDMP backup task fails.
Attribute
ID
Event Level
0x200F406E0013
Major
No

N/A.
Possible Causes
l
The protected directory cannot be backed up directly.
The file system snapshot fails to be created.
The file system snapshot fails to be deleted.
For example, NetBackup actively stops the backup task; the file system fails to be accessed;
the tape library fails to be accessed.
Procedure
Step 1 Check the network connection.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
1.
Check whether the network connection is correct.

l If yes=>Step 2.
l If no=>Step 1.2.
2.
Reconnect the cables. Then check whether the alarm is cleared.

l If no=>Step 2.
Step 2 Check the tape library.

1.
Ensure that the tape drive is in the up state. Then check whether the alarm is cleared.
l If no=>Step 2.2.
2.
Ensure the tape library is functional. Then check whether the alarm is cleared.
l If no=>Step 3.

----End
Related Information
None
2.238 0xF406E0014 An Ndmp Recovery Task Fails

Description
An NDMP recovery task fails.
Attribute
ID
Event Level
0xF406E0014
Major
No

N/A.
Possible Causes
l
The protected directory cannot be used as a recovery directory.
For example, NetBackup actively stops the recovery task; the file system fails to be
accessed; the tape library fails to be accessed.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Check the network connection.
1.
Check whether the network connection is correct.

l If yes=>Step 2.
l If no=>Step 1.2.
2.
Reconnect the cables. Then check whether the alarm is cleared.

l If no=>Step 2.
Step 2 Check the tape library.

1.
Ensure that the tape drive is in the up state. Then check whether the alarm is cleared.
l If no=>Step 2.2.
2.
Ensure the tape library is functional. Then check whether the alarm is cleared.
l If no=>Step 3.

----End
Related Information
None
2.239 0xF406E0015 Ndmp Authentication Fails, And The Ip

Address Of Backup Software Is Locked
Description
NDMP authentication fails, and the IP address of backup software is locked.
Attribute
ID
Event Level
0xF406E0015
Major
Yes

N/A.
Possible Causes
The number of NDMP authentication failures has reached the threshold.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Wait for the system to automatically unlock the IP address and retry again.
----End
Related Information
None
2.240 0xF00270130 A Remote Replication Fails To

Synchronize Data Automatically
Description
A remote replication fails to synchronize data automatically.
Attribute
ID
Event Level
0xF00270130
Major
No

N/A.
Possible Causes
l
The storage pools are used up.
Procedure
1.
If yes, handle the alarms with recommended actions. If synchronization still fails=>Step
2.
2.
If no, manually start a synchronization. If synchronization still fails=>Step 2.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.241 0xF00270112 A Remote Replication Is Unavailable

Description
A remote replication is unavailable.
Attribute
ID
Event Level
0xF00270112
Critical
Yes

Except deleting the remote replication, other operations related to the remote replication cannot
be performed.
Possible Causes
l
When the remote replication is interrupted abnormally, the secondary file system is deleted
locally. As a result, remote replication properties are inconsistent.
During the startup of the file system remote replication service, metadata fails to be read.
Procedure
----End
Related Information
None
2.242 0xF00270113 A Remote Replication Is Abnormally

Interrupted
Description
A remote replication is abnormally interrupted.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00270113
Major
Yes

Data cannot be backed up correctly.
Possible Causes
l
Links are interrupted.
Links are unstable.
The secondary file system or the storage pool where the secondary file system resides is
full.
The service load on the secondary storage system is heavy.
The primary file system in the remote replication is faulty.
The secondary file system in the remote replication is faulty.
The storage pools are faulty.
Procedure
Step 1 Check whether alarms are generated indicating link interruption.
1.
If yes, handle the alarms with recommended actions. If the alarms still persist=>Step 2.
2.
If no=>Step 2.
Step 2 Check whether links are stable.

1.
If yes=>Step 3.
2.
If no, ensure that links are stable.
Step 3 Check whether there are alarms about the storage pools where the primary and secondary file
systems reside.
1.
If yes, handle the alarms with recommended actions. If the alarms still persist=>Step 4.
2.
If no=>Step 4.

----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.243 0xF00CF0056 Only One Cluster Link Is Available

Description
Only one cluster link is available.
Attribute
ID
Event Level
0xF00CF0056
Warning
Yes

The faulty node has only one link available. If you do not resolve the problem promptly, the
controller will go offline as soon as the last available link is interrupted.
Possible Causes
l
The optical fiber is faulty.
The cable is not connected securely.
The cluster link is faulty.
Procedure
Step 1 Check whether the physical link is normal.
1.
If no, please repair it. If the alarm persists=>Step 2.
2.
If yes=>Step 2.

----End
Related Information
None
2.244 0xF000A0084 The Disk Is Rejected By The System

Description
The disk is from other engine.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF000A0084
Major
Yes

The disk cannot be detected by the storage system.
Possible Causes
The disk is from other engine.
Procedure
----End
Related Information
None
2.245 0x1FFFFFFFFFFFFFFC Testing The Alarm Function

Description
Simulating the reporting of a fault alarm.
Attribute
ID
Event Level
0x1FFFFFFFFFFFFFFC
Critical
No

This alarm is a simulated one to test the alarm function of the device.
Possible Causes
The alarm function of the device is being tested.
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
This alarm is simulated to test the alarm function of the device. Manually clear the alarm after
the test.
----End
Related Information
None
2.246 0xF00C9013D IP Address Conflict

Description
IP address conflict.
Attribute
ID
Event Level
0xF00C9013D
Major
Yes

It may cause net invalid.
Possible Causes
N/A.
Procedure
Modify the conflicting IP address.
----End
Related Information
None
2.247 0xF010D0032 The Management Module Firmware Is

Description
The firmware version of a management module is incompatible with storage array software.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF010D0032
Major
Yes

The management module firmware is incompatible with storage array software.
Possible Causes
The firmware version of the management module is incompatible with storage array software.
Procedure
----End
Related Information
None
2.248 0xF01060060 Cache Partition Failed To Process

Received I/O
Description
The I/O is beyond maximum I/O grain size of the Cache partition and can not be handled. The
business may be interrupted.
Attribute
ID
Event Level
0xF01060060
Critical
No

I/O error, and business might be interrupted.
Possible Causes
The size of I/O from host is beyond maximum I/O grain size of the Cache partition.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Please modify the Cache partition size at least to 512MB.
----End
Related Information
None
2.249 0x100F01060063 Controller Is Overloaded

Description
CPU or memory resource usage of a controller has exceeded the overload threshold, and the
controller enters the overloaded state.
Attribute
ID
Event Level
0x100F01060063
Warning
Yes

The controller starts overload protection to reduce the number of front-end I/Os in a time unit,
which may increase the I/O latency.
Possible Causes
The workload on the controller is too heavy.
Procedure
Reduce services carried by the controller or expand the system. For details, contact technical
support engineers.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.250 0xF00D00017 Failed To Synchronize The Firmware

Version Of An Expansion Module
Description
The firmware version fails to be synchronized after an expansion module is inserted.
Attribute
ID
Event Level
0xF00D00017
Major
Yes

Ports on the expansion module are isolated.
Possible Causes
l
The cable is faulty or not securely connected.
The interface module is removed or faulty.
The expansion module is faulty.
Procedure
Step 1 Check whether the cable is removed or damaged.
1.
If the cable is removed, reinsert it. If the alarm persists=>Step 1.2.
2.
Replace the cable with an intact one. If the alarm persists=>Step 2.
Step 2 Check whether the interface module is removed or damaged.

1.
If the interface module is removed, reinsert it. If the alarm persists=>Step 2.2.
2.
Replace the interface module. If the alarm persists=>Step 3.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.251 0xF00CF0059 Heartbeat Connection Between A

Controller And A Management Module Is Interrupted
Description
The heartbeat connection between a controller and a management module is interrupted, so the
controller cannot access the management module.
Attribute
ID
Event Level
0xF00CF0059
Major
Yes

The controller cannot access the management module.
Possible Causes
l
Procedure
Step 1 Check whether alarms are generated indicating management module faults.
1.
If yes, replace the faulty management module.If the alarm persists=>Step 2.
2.
If no=>Step 2.
Step 2 Replace the controller.If alarm persists=>Step 3.

----End
Related Information
None
2.252 0xF00270137 Remote Replication Is Automatically

Split
Description
Remote replication is automatically split.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF00270137
Warning
Yes

The remote replication is not synchronized automatically. It must be manually synchronized
after storage pool expansion.
Possible Causes
The capacity of the storage pool that houses the primary LUN or secondary LUN of the remote
replication is insufficient.
Procedure
Step 1 Check whether the capacity of the storage pool that houses the primary LUN or secondary LUN
of the remote replication is insufficient.
1.
If yes, expand the capacity of the storage pool and manually synchronize the remote
replication.
2.
If no=>Step 2.

----End
Related Information
None

Is Automatically Split
Description
Remote replication consistency group is automatically split.
Attribute
Issue 04 (2015-06-10)
ID
Event Level
0xF0DD0004
Warning
Yes

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

V3 Storage System
Event Reference

The remote replication consistency group is not synchronized automatically. It must be manually
synchronized after storage pool expansion.
Possible Causes
The capacity of the storage pool that houses the primary LUN or secondary LUN of a remote
replication pair in the consistency group is insufficient.
Procedure
Step 1 Check whether the capacity of the storage pool that houses the primary LUN or secondary LUN
of a remote replication pair in the consistency group is insufficient.
1.
If yes, expand the capacity of the storage pool and manually synchronize the remote
replication consistency group.
2.
If no=>Step 2.

----End
Related Information
None
2.254 0xF40020005 Number Of NAS Client Connections Of

A Controller Reaches The Upper Limit
Description
The number of NAS client connections of a controller reaches the upper limit.
Attribute
ID
Event Level
0xF40020005
Major
Yes

New connections cannot be connected to the controller, causing NAS client exceptions.
Possible Causes
The number of TCP connections reaches the upper limit.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Relocate some services running on the controller to other controllers or reduce the number of
NAS client connections.
----End
Related Information
None
2.255 0xF00D80119 Storage Pool Remaining Capacity Is

Insufficient
Description
The used capacity of a storage pool reachs the threshold.
Attribute
ID
Event Level
0xF00D80119
Major
Yes

N/A.
Possible Causes
The used capacity of the storage pool reachs the threshold.
Procedure
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.256 0xF00D80120 Storage Pool Capacity Is About To Be

Used Up
Description
The storage pool capacity is about to be used up, which may cause service interruption on this
pool.
Attribute
ID
Event Level
0xF00D80120
Critical
Yes

which may cause service interruption on this pool.
Possible Causes
The storage pool capacity is about to be used up.
Procedure
----End
Related Information
None
2.257 0xF01060043 Failed To Reach The Control Objective

Of SmartQoS
Description
Failed to reach the control objective of SmartQoS by all means. Please confirm the rationality
of configuration.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0xF01060043
Major
No

The whole performance would be declined.
Possible Causes
The business pressure of the LUN in the SmartQoS is not enough, but the control objective is
configured too high.
Procedure
Please confirm the business pressure of the LUN in the SmartQoS policy. Deactivate the policy
and modify the control objective, then activate the policy again.
----End
Related Information
None
2.258 0xF40020006 Number Of File Information Items To Be

Backed Up Reaches The Upper Limit
Description
When the failover function is used, the controller backs up file information. The number of file
information items reaches the upper limit.
Attribute
ID
Event Level
0xF40020006
Major
Yes

New file information cannot be backed up. If the failover function is used, service switchover
may fail.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Possible Causes
The number of file information items to be backed up for the failover function reaches the upper
limit.
Procedure
Step 1 Migrate some services to other controllers. If the alarm persists=>Step 2.
----End
Related Information
None
2.259 0xF40440017 Controller Is Disconnected From An

LDAP/NIS Server
Description
A controller is disconnected from an LDAP/NIS server.
Attribute
ID
Event Level
0xF40440017
Major
Yes

LDAP/NIS authentication fails. NFS services are affected, and the data cannot be accessed
normally.
Possible Causes
l
The LDAP/NIS server is shut down.
The device is incorrectly communicating with the LDAP/NIS server.
Procedure
Step 1 Check the status of the LDAP/NIS server.
1.
Check whether the LDAP/NIS server is started.

l If yes=>Step 2.
l If no=>Step 1.2.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.
Start the LDAP/NIS server. Then check whether the alarm is cleared.
l If no=>Step 2.
Step 2 Check the network connectivity between the device and LDAP/NIS server.
1.
Check whether the device is correctly communicating with the LDAP/NIS server.
l If yes=>Step 3.
l If no=>Step 2.2.
2.
alarm is cleared.
l If no=>Step 3.

----End
Related Information
None
2.260 0x100F03300072 Failed To Restore A Virtual Machine

Description
Failed to restore a virtual machine.
Attribute
ID
Event Level
0x100F03300072
Warning
Yes

Failed to restore the virtual machine's operating status.
Possible Causes
l
The virtual machine status is abnormal.
The container does not have sufficient resources.
Procedure
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Check and power on the virtual machine manually.

----End
Related Information
None
2.261 0x100F03300073 Failed To Shut Down A Virtual

Machine
Description
Failed to shut down a virtual machine.
Attribute
ID
Event Level
0x100F03300073
Warning
Yes

Some virtual machine data may be lost.
Possible Causes
The virtual machine is running under a heavy service load and is not powered off correctly.
Procedure
Step 1 Check whether the virtual machine can be correctly powered on when the controller is working
correctly.
To repair a damaged virtual machine, contact technical support engineers.
----End
Related Information
None
2.262 0x100F03300074 Incomplete Virtual Machine Creation

Description
The creation of a virtual machine is incomplete.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Attribute
ID
Event Level
0x100F03300074
Warning
Yes

The virtual machine is unavailable.
Possible Causes
The controller is powered off during virtual machine creation.
Procedure
Delete the virtual machine and create it using the original template.
----End
Related Information
None
2.263 0xF00280112 Number Of Files In A File System Is

About To Exceed The Upper Limit
Description
The number of files in a file system is about to exceed the upper limit.
Attribute
ID
Event Level
0xF00280112
Major
Yes

File system performance may deteriorate.
Possible Causes
The number of files in the file system is about to exceed the upper limit.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
Procedure
Step 1 Stop writing new files into the file system.
Step 2 Delete unnecessary files from the file system.
----End
Related Information
None
2.264 0xF00280113 Number Of Files In A Directory Of A File

System Is About To Exceed The Upper Limit
Description
The number of files in a directory of a file system is about to exceed the upper limit.
Attribute
ID
Event Level
0xF00280113
Major
Yes

Directory read performance deteriorates.
Possible Causes
The number of files in the directory of the file system is about to exceed the upper limit.
Procedure
Step 1 Stop writing new files into the directory.
Step 2 Delete unnecessary files from the directory.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
2.265 0xF00CF005C Number Of Opened Files On A

Controller Is About To Exceed The Upper Limit
Description
The number of opened files on a controller is about to exceed the upper limit.
Attribute
ID
Event Level
0xF00CF005C
Major
Yes

Files fail to be opened, and services are interrupted.
Possible Causes
The number of opened files on the controller is about to exceed the upper limit.
Procedure
Close the opened files on the controller.
----End
Related Information
None
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
A How to Obtain Help
How to Obtain Help
If a tough or critical problem persists in routine maintenance or troubleshooting, contact Huawei

for technical support.
A.1 Preparations For Contacting Huawei
To better solve the problem, you need to collect troubleshooting information and make
debugging preparations before contacting Huawei.
A.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.
A.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.
A.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.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
A.1 Preparations For Contacting Huawei

To better solve the problem, you need to collect troubleshooting information and make
debugging preparations before contacting Huawei.
A.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
Contact person and telephone number
Time when the fault occurred
Description of the fault phenomena
Device type and software version
Measures taken after the fault occurs and the related results
Troubleshooting level and required solution deadline
A.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.
A.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.
A.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
Regional office technical support center
Customer service center
Technical support website: http://support.huawei.com/enterprise/
You can query how to contact the regional offices at http://support.huawei.com/enterprise/.

Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
A.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.
Huawei Technologies Co., Ltd.
Address: Huawei Industrial Base Bantian, Longgang Shenzhen 518129 People's Republic of
China
Website: http://enterprise.huawei.com/
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
B Glossary
Glossary
A
AC power module The module that transfers the external AC power supply into the power
supply for internal use.
Application
server
A service processing node (a computer device) in the network.

Application programs of data services are run on the application server.
Asynchronous
remote
replication
A kind of remote replication. When the data on the primary site is

updated, the data does not need to be updated on the mirroring site
synchronously to finish the update. In this way, performance is not
reduced due to data mirroring.
Issue 04 (2015-06-10)
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 a transmission line or channel can

carry in a network. In fact, the bandwidth is the difference between the
highest and lowest frequencies in 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
An incompatibility between a bit in a transmitted digital signal and the

corresponding bit in the received digital signal.
Bit error rate
The percentage of bits that have errors relative to the total number of
bits received in a transmission.

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

V3 Storage System
Event Reference
B Glossary
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.
Issue 04 (2015-06-10)
Cache hit ratio
The ratio of directly accessed I/O from Cache to all the I/O operation
during the read operation.
Cache prefetch
strategy
According to the operation in which data has been read or is being 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.
Command device
A special LUN through which the host can send inband commands to
storage devices.

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

V3 Storage System
Event Reference
B Glossary
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
enclosure
An enclosure that accommodates controllers and provides storage

services. It is the core component of a storage system, and generally
consists of components such as controllers, power supplies, and fans.
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.
Issue 04 (2015-06-10)
Data compression
Encoding data to take up less storage space and less bandwidth for
transmission.
Data
deduplication
A specialized data compression technique for eliminating coarsegrained redundant data, typically to improve storage utilization. In the
deduplication process, duplicate data is deleted, leaving only one copy
of the data to be stored, along with references to the unique copy of data.
Deduplication is able to reduce the required storage capacity since only
the unique data is stored.
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 history 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.

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

V3 Storage System
Event Reference
B Glossary
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.
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
The process of locating a hard disk, that is, determining the enclosure
ID and slot ID 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
(external device
LUN)
Logic space created by third-party storage systems.
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
Issue 04 (2015-06-10)
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.

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

V3 Storage System
Event Reference
B Glossary
Field replaceable
unit
A unit that can function as a circuit board, part, or component of an

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
port
The port that connects the controller enclosure to the service side and
transfers service data. There are three types of front-end host ports: SAS,
FC, and iSCSI.
G
Gateway
The entrance node on another network.
Global system for

mobile
communications
The second-generation mobile networking standard defined by

European Telecommunications Standards Institute (ETSI). It is aimed
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.
Hard quota
The value to limit the space used in quota configuration. If the space
used arrives hard quota, file operation is not allowed to continue.
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.
Issue 04 (2015-06-10)

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

V3 Storage System
Event Reference
B Glossary
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.
Inband
management
Inband management means that the management control information of

the network and the carrier service information of the user network are
transferred through the same logical channel. Inband management
enables users to manage storage arrays through commands.
Management commands are sent through service channels, that is, I/O
write and read channels. The advantages of inband management include
high speed, stable transfer, and no additional management network ports
required.
Initiator
A system component that can initiate an I/O operation on an I/O bus or

on a network.
Intelligent
prefetch
A cache prefetch strategy. The system software calculates a proper 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.
Issue 04 (2015-06-10)
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
number
The SCSI identifier of the internal logical unit of a target.
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.

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

V3 Storage System
Event Reference
B Glossary
LUN migration
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
terminal
The computer that is connected through a serial port or management

network port and maintains the storage system.
Management
network
An entity that provides a means to transmit and process the information

related to network management.
Management
network port
The network port on the controller enclosure that is connected to the

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.
O
Out-of-band
management
A management mode used during out-of-band networking. In the outof-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
controller
For a LUN or file system, the user configures the owing controller, that
is, specified the created LUN or file system to a certain controller. When
the owning controller of the LUN or file system is invalid, another
controller manages the LUN or file system automatically. When the
owning controller of the LUN or file system is restored, the original
controller manages the LUN or file system again.
P
Power failure
protection
Issue 04 (2015-06-10)
When the external power failure occurs, the AC PEM depends on the
battery for power supply, which ensures the integrity of the dirty data
in cache.

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

V3 Storage System
Event Reference
B Glossary
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
controller
The controller that plays a leading role in controlling the management

is the primary storage controller. It can perform relevant management
operations on the controller enclosure.
Primary/
Secondary
switchover
A procedure during which the two controllers of the storage system

change their master/slave states.
Prior controller
For the application server LUN, prior controller means that the working
controller is the owner controller of the corresponding array LUN.
Q
Quota tree
A first-level directory of file system that can be managed with quota.
Issue 04 (2015-06-10)
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.
Remote
replication
A core technology for disaster recovery and a foundation that

implements remote data synchronization and disaster recovery. This
technology remotely maintains a set of data 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
synchronizing
The process of restoring data from the redundancy machine (RM) when
the services of the production machine (PM) are recovering.
Route
The path that network traffic takes from its source to its destination. In
a TCP/IP network, each IP packet is routed independently. Routes can
change dynamically.

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

V3 Storage System
Event Reference
B Glossary
Issue 04 (2015-06-10)
Script
A collection of data statements used to perform an operation.
Secondary
controller
(1) A controller that backs up service and management data of the

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
port
The network port that is used to store services.
SFP optical
transceiver
A component that can make data conversion between optical signals

and electrical signals and that can receive and transfer data.
Simple network
management
protocol
A network management protocol of TCP/IP. It enables remote users to

view and modify the management information of a network element.
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.
Single point
failure
A type of failure. Data transmission over a network is stopped and

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
system interface
A set of standards for physically connecting and transferring data

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.

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

V3 Storage System
Event Reference
B Glossary
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.
Soft quota
The value to alarm space usage in quota configuration. After used space
arrives this value, an alarm triggered; if space used from above this value
becomes lower than, the previous alarm eliminated.
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
remote
replication
A kind of remote replication. When the data on the primary site is

updated, the data must be synchronously updated on the mirroring site
before the update is complete. In this way, the data that is stored on both
the primary and mirroring sites can be synchronized.
Issue 04 (2015-06-10)
Target
A system component that can receive SCSI I/O operation commands.
Target LUN
The target for LUN copy.
Tenant
A property of SmartTenancy, which represents a virtual storage system

in a physical one. The private and independent logical resource of a
tenant mainly includes disk domain space, LUN, file system and ports.
Tenants get complete storage services, but also remain resource and
network isolation with other tenants, which avoids interference.

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

V3 Storage System
Event Reference
B Glossary
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
protocol
A TCP/IP standard protocol that allows an application program on 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.
W
Working
controller
Issue 04 (2015-06-10)
The controller that reads data from and writes data onto LUNs or file
systems in a storage array.

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

V3 Storage System
Event Reference
B Glossary
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
Issue 04 (2015-06-10)
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.

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

V3 Storage System
Event Reference
C Acronyms and Abbreviations
Acronyms and Abbreviations
B
BBU
Backup Battery Unit
F
FC
Fiber Channel
H
HBA
Host Bus Adapter
I
iSCSI
Internet Small Computer Systems Interface
L
LUN
Logical Unit Number
M
MAC
Issue 04 (2015-06-10)
Medium Access Control

241

Huawei Event Reference

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei Event Reference

Uploaded by

Copyright:

Available Formats

OceanStor 5300 V3&5500 V3&5600 V3&5800

V3&6800 V3 Storage System

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2015. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

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

About This Document

About This Document

Technical support engineers

Huawei Proprietary and Confidential

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

About This Document

New events are included and some events are modified.

Huawei Proprietary and Confidential

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

Huawei Proprietary and Confidential

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

2.30 0x100F00CF0034 A Controller Is Isolated................................................................................................................36

Huawei Proprietary and Confidential

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

2.71 0xF0D20002 BBU Module Is Faulty.........................................................................................................................70

Huawei Proprietary and Confidential

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

2.112 0xF0DC0001 Clone Pair Is Abnormally Interrupted.............................................................................................103

Huawei Proprietary and Confidential

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

2.153 0xD80001 Storage Pool Remaining Capacity Is Insufficient.................................................................................135

Huawei Proprietary and Confidential

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

2.194 0xF00D10020 Interface Module Is Faulty.............................................................................................................169

Huawei Proprietary and Confidential

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

2.235 0xF01050029 Switch Optical Module Temperature Is Too High..........................................................................200

A How to Obtain Help.................................................................................................................226

Huawei Proprietary and Confidential

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

C Acronyms and Abbreviations................................................................................................241

Huawei Proprietary and Confidential

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

Event Signal Flow

Huawei Proprietary and Confidential

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

Figure 1-1 Event signal flow figure

Service control module

Huawei Proprietary and Confidential

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

About This Chapter

Huawei Proprietary and Confidential

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

2.20 0xF0CF0006 Controller Is Removed

Huawei Proprietary and Confidential

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

2.51 0xF00A0004 Disk Temperature Exceeds The Upper Limit

Huawei Proprietary and Confidential

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

2.83 0xF0060003 Expansion Port Is Faulty

Huawei Proprietary and Confidential

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

Huawei Proprietary and Confidential

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

2.146 0xF00150019 Host Is Not Redundantly Connected To Storage Arrays