Health Check PDF

U2000
V200R018C10
OSMU Health Check Verification Items
Issue 04
Date 2019-02-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2019. 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 the property 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://www.huawei.com
Email: support@huawei.com
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. i

U2000
OSMU Health Check Verification Items Contents
Contents
1 SUSE Verification Items .............................................................................................................. 1

1.1 Operating System (Linux) ................................................................................................................................ 1
1.1.1 210004_Verifying the Status of the Disk Space ...................................................................................... 1
1.1.2 210006_Verifying the Available Memory ............................................................................................... 3
1.1.3 230001_Verifying the Status of the FTP Service .................................................................................... 3
1.1.4 230006_Verifying the Disk Mirror Status ............................................................................................... 4
1.1.5 230008_Verifying the SUSE OS Version ................................................................................................ 7
1.1.6 230011_Verifying the OS logs ................................................................................................................ 7
1.1.7 500006_Check the IO speed of file system ............................................................................................. 9
1.1.8 500007_Check disk array monitor configuration .................................................................................... 9
1.1.9 500009_Check OSS backup status ........................................................................................................ 10
1.1.10 500015_Check Precaution .................................................................................................................. 10
1.1.11 500020_Check server IP conflict ........................................................................................................ 12
1.1.12 500025_Checking the disk size planned for the /export/home on the database node ......................... 12
1.2 Oracle Database ............................................................................................................................................. 13
1.2.1 320001_ Check the oracle user configure file ....................................................................................... 13
1.2.2 320002_Verifying the Operating Status of the Oracle Database ........................................................... 14
1.2.3 320003_Verifying the Oracle alert_log Information ............................................................................. 15
1.2.4 320007_Verifying the Configuration of Other Parameters for the Oracle Database ............................. 17
1.2.5 320016_ Check size of oracle log ......................................................................................................... 19
1.2.6 320017_Verifying the table space of the Oracle Database .................................................................... 20
1.3 Logical Volume Management......................................................................................................................... 22
1.3.1 350002_Check VxVm disk status ......................................................................................................... 22
1.3.2 350003_Check VxVm volume status .................................................................................................... 23
1.3.3 350005_Check LVM volume status ...................................................................................................... 24
1.4 VCS Cluster ................................................................................................................................................... 29
1.4.1 340009_Check VCS node running status .............................................................................................. 29
1.4.2 340010_Check VCS private network status .......................................................................................... 30
1.4.3 340011_Check VCS configuration ....................................................................................................... 31
1.4.4 340012_Check VCS resource group status ........................................................................................... 33
2 Common Verification Items...................................................................................................... 35

2.1 OSS Verification Items ................................................................................................................................... 36
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. ii

U2000
2.1.1 400000_Verifying the OSS Software Version ....................................................................................... 36

2.1.2 410001_ Check OSS Status .................................................................................................................. 36
2.1.3 410002_ Check the service standby blade routes integrity ................................................................... 37
2.1.4 410988_Collecting precaution information .......................................................................................... 38
2.1.5 500000_Check the file and directory permissions ................................................................................ 39
2.1.6 500005_ Check permission and owner of file and directory ................................................................. 41
2.1.7 500121_Check main directory link ....................................................................................................... 41
2.1.8 180023_Obtaining the Version of the U2000 and Smart_Assistant ...................................................... 51
2.1.9 422104_Checking the core dump path of the service ........................................................................... 51
2.2 Security Check Items ..................................................................................................................................... 53
2.2.1 340004_Check the Database Security Hardening ................................................................................. 53
2.2.2 340005_Check the Operating System Security Hardening ................................................................... 54
2.2.3 340006_ Check the security authentication log dump .......................................................................... 55
2.3 Sybase Database ............................................................................................................................................. 56
2.3.1 310003_Verifying that No Database Is Offline ..................................................................................... 56
2.3.2 310004_ Check sybase boot file parameter ........................................................................................... 57
2.3.3 310005_Check dbuser right .................................................................................................................. 58
2.3.1 310007_Verifying that No Error Is Logged Recently for the Sybase .................................................... 59
2.3.2 310008_ Check trunc log parameter of sybase database ....................................................................... 60
2.3.3 310041_ Collect Sybase information .................................................................................................... 63
2.3.4 500019_ Check Sybase Logsegment .................................................................................................... 64
2.4 S2600 Array Verification Items ...................................................................................................................... 65
2.4.1 150046_Check S2600 Array Disk ......................................................................................................... 65
2.4.2 150047_Check S2600 Array BBU ........................................................................................................ 67
2.4.3 150048_Check S2600 Array Controller ................................................................................................ 69
2.4.4 150053_Check S2600 Array Fibre Mode.............................................................................................. 71
2.4.5 150056_Check S2600 Array Lun .......................................................................................................... 73
2.4.6 150057_Check S2600 Array Physical Disk .......................................................................................... 75
2.4.7 150101_Check S2600 Cache Write Strategy or Policy ......................................................................... 77
2.4.8 150106_Check S2600 Fan Status .......................................................................................................... 81
2.4.9 150107_Check S2600 FC Link Rate ..................................................................................................... 83
2.4.10 150108_Check S2600 Hot Spare Disk ................................................................................................ 85
2.4.11 150110_Check S2600 LUN Write Back Without Mirroring ............................................................... 88
2.4.12 150112_Check S2600 Power Supply Status ....................................................................................... 91
2.5 S3100/S3200 Array Verification Items ........................................................................................................... 94
2.5.1 150061_Check S3100/S3200 Array Disk ............................................................................................. 94
2.5.2 150064_Check S3100/S3200 Array Volume Group .............................................................................. 95
2.5.3 150066_Check S3100/S3200 Array Volume ......................................................................................... 97
2.5.4 150067_Check S3100/S3200 Array Controller ..................................................................................... 99
2.5.5 150069_Check S3100/S3200 Array Power-fan .................................................................................. 101
2.5.6 150070_Check S3100/S3200 Array Power ......................................................................................... 104
2.5.7 150071_Check S3100/S3200 Array Fan ............................................................................................. 106
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. iii

U2000
2.6 S3900 Array Verification Items .................................................................................................................... 107

2.6.1 150074_Check S3900 array controller ................................................................................................ 107
2.6.2 150075_Check S3900 Array BBU ...................................................................................................... 109
2.6.3 150076_Check S3900 Array Disk ....................................................................................................... 111
2.6.4 150077_Check S3900 Array Fan ........................................................................................................ 113
2.6.5 150078_Check S3900 Array Lun ........................................................................................................ 115
2.6.6 150079_Check S3900 Array Power .................................................................................................... 117
2.6.7 500010_check 3900Array Single Path ................................................................................................ 120
2.6.8 150203_Check S3900 FC Link Rate ................................................................................................... 121
2.6.9 150204_Check S3900 Optical Transceiver Status .............................................................................. 123
2.6.10 150206_Check S3900 RAID Group Status ....................................................................................... 125
2.6.11 150207_Check S3900 System Status ................................................................................................ 127
3 Service Module Verification Items ........................................................................................ 130

3.1 Common Module ......................................................................................................................................... 130
3.1.1 450001_Verifying that the OSS FTP Folder Link is Normal .............................................................. 130
3.1.2 450002_Verifying that the Cert of Ftpserver is Normal ...................................................................... 133
3.1.3 450003_Verifying that the Password of is Abnormal .......................................................................... 134
3.1.4 450004_Verifying that the FTP Common Path Stat is Correct ........................................................... 136
3.1.5 450005_Verifying that the 3rdServer with NAT in Use ...................................................................... 137
3.1.6 450006_Verifying that the OSS Ftp Server Running Normal ............................................................. 138
3.1.7 450007_Verifying that the Ftp Configure is Normal ........................................................................... 140
3.1.8 450008_Verifying that the FTP Log File of /var/log/vsftpd.log and Ftp Log Dump Timer Task is
Normal. ........................................................................................................................................................ 142
3.1.9 450011_Verifying Permissions on the Configuration File of the sshd Service ................................... 144
3.1.10 450012_Verifying Permissions on the File Related to the NE License Export Task ......................... 145
3.1.11 450013_Verifying that the 3rdQueryExport Folder of the DCC Tool Contains No Trash Files ........ 147
3.2 Configuration Module .................................................................................................................................. 149
3.2.1 420005_Verifying that No Junk Data of NEs Exists ........................................................................... 149
3.2.2 420007_Verifying Permissions of System Users and Permissions on the Directory .......................... 150
3.2.3 420008_Verifying that Files of Installed Mediation Are Consistent with Database............................ 151
3.2.4 420023_Check right mask of process ................................................................................................. 153
3.2.5 420022_Check UsePAM configuration of Linux ................................................................................ 154
3.2.6 420010_Verifying that No Useless Meditation Exists ........................................................................ 155
3.2.7 420014_Verifying the Running Status of the Mediation Service ........................................................ 158
3.2.8 420015_Verifying incorrect Permissions for the Dynamic Directory Created by the Service Process159
3.2.9 422001_Check BTS3900NE's Function position on Topo .................................................................. 160
3.2.10 422002_Check whether omcdb has bad table ................................................................................... 161
3.2.11 422005_Check whether neinfo.dat exists .......................................................................................... 162
3.2.12 422007_Check the stauts of NE management task ........................................................................... 162
3.2.13 422008_Check auto search Ne .......................................................................................................... 163
3.2.14 422011_Check the permission and ownership of the target MML directory .................................... 164
3.2.15 422013_Check whether the MBTS relation is correct ...................................................................... 165
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. iv

U2000
3.2.16 422024_Check the big moi tables of omcdb ..................................................................................... 166

3.2.17 410061_Verifying That the OSS NE Belongs to the Core and Wireless Networks .......................... 168
3.2.18 500124_Checking whether the historical MML file exists ............................................................... 168
3.2.19 500125_Checking whether the configuration synchronization frequency is normal ........................ 172
3.2.20 500126_Checking the size of the cmsynch_MocChangeInfo table .................................................. 173
3.2.21 422105_ Check whether the CaptureAssistant is installed ................................................................ 176
3.3 Northbound Module ..................................................................................................................................... 178
3.3.1 460002_Verifying that the snmp Process Does Not Occupy Port 161 or Port 162 ............................. 178
3.3.2 460001_Check whether NBI Files (Corba) Are Accumulated ............................................................ 179
3.3.3 460003_Check the Version of NBI Interface Is New Or Old .............................................................. 179
3.3.4 460031_ Check the Sybase monitor tool installed status .................................................................... 180
3.3.5 460032_Check whether the subscribe info of NBI corba alarm interface is normal ........................... 181
3.4 Performance Module .................................................................................................................................... 181
3.4.1 430134_ Check status of the log truncate switch of pmdb and pmcomdb .......................................... 181
3.4.2 510053_ Check management capacity result ...................................................................................... 183
3.5 Alarm Module .............................................................................................................................................. 184
3.5.1 440014_Verifying that Uncleared Alarms for a Long Time do not Exist in the Current Alarm List ... 184
3.5.2 440015_Verifying that Alarms with Unknown Alarm Sources Do Not Exist in the Current Alarm List
..................................................................................................................................................................... 185
3.5.3 440032_Check whether alarm buffer is fully or not ........................................................................... 186
3.5.4 440033_Check whether alarm was stored in DB ................................................................................ 187
3.5.5 440034_Check alarm buffer cleared or not ......................................................................................... 188
3.5.6 440042_Check Whether Uncleared Important OSS Alarms Exist ...................................................... 189
3.6 CME ............................................................................................................................................................. 190
3.6.1 480006_ Verifying the CME database space ....................................................................................... 190
3.6.2 480018_ Verifying the system database or table space of the database .............................................. 191
3.6.3 480070_ Check precaution information about CME .......................................................................... 193
3.7 Trace Server Module .................................................................................................................................... 194
3.7.1 600002_Verifying the trace server version .......................................................................................... 194
3.7.2 600003_Verifying that the temp directorys of The trace server services are normal .......................... 194
3.7.3 600004_Verifying that the softlinks of the trace server services are normal ....................................... 195
3.7.4 600005_Verifying that the rights of the trace server are normal ......................................................... 196
3.7.5 600007_Verifying that the sftp of the trace server is normal .............................................................. 197
3.7.6 600008_Verifying that the result directories of the trace server services are ok ................................. 197
3.7.7 600010_ Verifying that the Sqlite3 database of the Trace Server is complete .................................... 198
3.8 iMAP Module ............................................................................................................................................... 199
3.8.1 800001_Check whether PartitionService is normal or not .................................................................. 199
3.8.2 800002_Check whether imapeventmgr is normal or not .................................................................... 200
3.9 ES&Mini ...................................................................................................................................................... 203
3.9.1 708050_ Check whether register the ES and whether the ES status is normal ................................... 203
3.9.2 708056_ Check whether have deployed ATAE Mini system .............................................................. 207
3.10 FMA ........................................................................................................................................................... 211
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. v

U2000
3.10.1 440043_Checking the Running Disk Resources of the FMA ........................................................... 211
3.10.2 440044_Checking the Equivalent NEs Managed by the FMA ......................................................... 212
3.10.3 440045_Checking the Available CPU Resources of the FMA .......................................................... 213
3.10.4 440046_Checking the Available Memory Resources of the FMA .................................................... 214
4 Inventory Data Collection Verification Items ..................................................................... 216

4.1 Basic Site Information .................................................................................................................................. 217
4.1.1 220018_Verifying the Country Name ................................................................................................. 217
4.1.2 220019_Verifying the City Name ....................................................................................................... 218
4.1.3 220020_Verifying the Customer Name ............................................................................................... 219
4.1.4 220002_Verifying the Server IP Address ............................................................................................ 220
4.1.5 220003_Verifying That Dual Planes Are Configured ......................................................................... 221
4.1.6 220014_Verifying the Floating IP Address ......................................................................................... 222
4.1.7 410058_Verifying the Validity of the OSS License ............................................................................ 223
4.1.8 490004_Verifying the Software Version of the PRS Deployed on the Server for the OSS ................. 224
4.1.9 480054_Verifying the Software Version of the CME Integrated into the OSS ................................... 224
4.1.10 410059_Verifying the Validity of the License of the CME Integrated into the OSS ......................... 226
4.1.11 410041_Verifying the Networking Mode of the Server .................................................................... 227
4.1.12 410009_ Verifying That the Operating System Security Hardening Software Is Installed ............... 228
4.1.13 410056_Verifying the Security Hardening Software Version ........................................................... 229
4.1.14 210008_Verifying the NTP Service Type .......................................................................................... 230
4.1.15 210010_Verifying the NTP Service Status ........................................................................................ 231
4.1.16 410062_Verifying That NAT Is Configured on the OSS ................................................................... 232
4.2 Outsourced Parts Information ...................................................................................................................... 233
4.2.1 110002_Verifying the HP/ATAE/IBM Server Model ......................................................................... 233
4.2.2 210011_Verifying the Memory Size ................................................................................................... 233
4.2.3 150040_Verifying Local Hard Disk Information ................................................................................ 234
4.2.4 350009_Verifying the VxVM Software Version ................................................................................. 235
4.2.5 350010_Verifying the Validity of the VxVM License......................................................................... 235
4.2.6 340015_Verifying the VCS Software Version ..................................................................................... 238
4.2.7 340016_Verifying the Validity of the VCS License ............................................................................ 239
4.2.8 110014_Verifying the Warranty Service of the Server ........................................................................ 240
4.2.9 230008_Verifying the SUSE OS Version ............................................................................................ 241
4.2.10 310001_Verifying the Sybase Database Version ............................................................................... 242
4.2.11 150084_Verifying the Disk Array Controller Version ....................................................................... 243
4.2.12 150081_Verifying the Disk Array Model .......................................................................................... 244
4.2.13 150082_Verifying That Disk Array Information Can Be Collected .................................................. 245
4.2.14 150083_Verifying the Serial Number of the Disk Array ................................................................... 246
4.2.15 170001_Verifying the Tape Drive Model .......................................................................................... 247
4.3 Third-Party Access Information ................................................................................................................... 248
4.3.1 460020_Verifying the Manufacturer of the NMS ............................................................................... 248
4.3.2 450058_Verifying the deployment status of the NBI line test interface .............................................. 249
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. vi

U2000
4.3.3 450057_Verifying the deployment status of the NBI TMF814 interface ............................................ 250
4.3.4 450056_Verifying the deployment status of the NBI TL1 interface ................................................... 251
4.3.5 450055_Verifying the deployment status of the NBI configuration SNMP interface ......................... 252
4.3.6 450054_Verifying the deployment status of the NBI Syslog interface ............................................... 253
4.3.7 450052_ Verifying the deployment status of the NBI CORBA security interface .............................. 254
4.3.8 450051_ Verifying the deployment status of the NBI RADIUS user authentication interface ........... 255
4.3.9 450050_ Verifying the deployment status of the NBI LDAP user authentication interface ................ 256
4.3.10 450049_ Verifying the deployment status of the NBI LDAP user management interface ................ 257
4.3.11 450048_ Verifying the deployment status of the NBI NE license file interface ................................ 258
4.3.12 450047_ Verifying the type of files exported from the NBI inventory file interface ........................ 259
4.3.13 450046_ Verifying the deployment status of the NBI inventory file interface .................................. 260
4.3.14 450044_ Verifying the deployment status of the NBI configuration database interface ................... 261
4.3.15 450043_ Verifying whether the NBI CME file interface uses the CORBA interface ....................... 262
4.3.16 450042_ Verifying the compression type of files exported from the NBI CME file interface .......... 263
4.3.17 450041_ Verifying the type of files exported from the NBI CME file interface ............................... 264
4.3.18 450040_ Verifying the deployment status of the NBI CME file interface ........................................ 265
4.3.19 450039_ Verifying the file export mode of the NBI configuration file interface .............................. 266
4.3.20 450038_ Verifying the compression type of files exported from the NBI configuration file interface
..................................................................................................................................................................... 267
4.3.21 450037_ Verifying the type of files exported from the NBI configuration file interface .................. 268
4.3.22 450036_ Verifying the deployment status of the NBI configuration file interface............................ 269
4.3.23 450035_ Verifying the deployment status of the NBI alarm database interface ............................... 270
4.3.24 450032_ Verifying the deployment status of the NBI alarm SNMP interface .................................. 271
4.3.25 450026_ Verifying the deployment status of the NBI CORBA alarm interface ................................ 272
4.3.26 450024_ Verifying the compression type of files exported from the NBI alarm file interface ......... 273
4.3.27 450023_ Verifying the type of files exported from the NBI alarm file interface .............................. 274
4.3.28 450022_ Verifying the deployment status of the NBI alarm file interface ........................................ 275
4.3.29 450020_ Verifying the performance counter interconnection mode of the NBI performance file
interface based on measurement units.......................................................................................................... 276
4.3.30 450019_ Verifying the compression type of files exported from the NBI performance file interface
based on measurement units ........................................................................................................................ 277
4.3.31 450018_ Verifying the type of files exported from the NBI performance file interface based on
measurement units ....................................................................................................................................... 278
4.3.32 450017_ Verifying the deployment status of the NBI performance file interface based on
measurement units ....................................................................................................................................... 279
4.3.33 450016_ Verifying the performance counter interconnection mode of the NBI performance file
interface based on NEs ................................................................................................................................. 280
4.3.34 450015_ Verifying the compression type of files exported from the NBI configuration file interface
..................................................................................................................................................................... 281
4.3.35 450014_ Verifying the deployment status of the NBI performance file interface based on NEs ...... 282
4.4 Severe Fault Quick Rectification Information ............................................................................................. 283
4.4.1 220021_Verifying That the OS Backup Is Available........................................................................... 283
4.4.2 220022_Verifying That the Static Data Backup Is Available .............................................................. 284
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. vii

U2000
OSMU Health Check Verification Items 1 SUSE Verification Items
1 SUSE Verification Items
1.1 Operating System (Linux)

1.1.1 210004_Verifying the Status of the Disk Space
Item Verifying the status of the disk space
Check ID 210004
Application SUSE
System
Detailed 210004-200 1. Alarm item

Solution CheckID : 210004
CheckItem : check_df
Status : WARNING
Desc : 210004-200: not get the usefull
of filesystem
Solution : NA
Autorepair : NA
Area : System
Message : not get the usefull of filesystem
2. Problem analysis and solution
Run the df -h command to verify the status of the
disk space. If the analysis results include this alarm,
the disk partition usage information is not collected.
Contact Huawei technical support engineers.
Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 1

U2000
210004-201 1. Alarm item

CheckID : 210004
CheckItem : check_df
Status : WARNING
Desc : 210004-201: the usefull of
filesytem is more than 80%..
Solution : NA
Autorepair : NA
Area : System
Message : The disk used is more the 80%
Run the df -h command to verify the status of the
disk space. If the analysis results include this alarm,
the disk partition usage information is not collected.
Basis Run the #df -h command to check whether the /export/home partition is
present on the disk, and whether the usage of each partition exceeds 80%.

U2000
1.1.2 210006_Verifying the Available Memory

Item Verifying the available system memory
Check ID 210006
Application SUSE
System

CheckItem : check_free_memory
Status : WARNING
Desc : 210006-200: the free memory is not
enough.
Standard : free memory less than all memory
1/64,the result is warning.
Solution : If the memory is not enough, the U2000
service may be slow or abnormal.If you have any question,
please contact Huawei technical support engineers.
Autorepair : NA
Area : System
Message : The free memery size is not enough
Run the vmstat 2 2 command to verify the available memory
and save the command output to the vmstat.out file. If the
analysis results include this alarm, the command execution
encounters an error. Manually run the following command as
user root:
# vmstat 2 2
Send the command output to Huawei technical support
engineers.
1.1.3 230001_Verifying the Status of the FTP Service

Item Verify the status of the FTP service
Check ID 230001
Application SUSE
System

CheckItem : check_ftpstatus
Status : WARNING
Desc : 230001-201: Please check ftp user
or ftp config file.
Standard : Check the configuration of the

U2000
FTP services on the server and check whether the

FTP services are running. In normal cases, the FTP
services are running properly
Solution : If ftp service is abnormal,please
contact Huawei technical support engineers.
Autorepair : NA
Area : System
Message : Please check ftp user or ftp config
file
Copy all contents in the /etc/vsftpd.conf file to the
vsftpdstatus.txt file and check whether the
configuration information is normal.
If the analysis results include this alarm, the
/etc/vsftpd.conf file is not obtained. Run the
following command manually as user root:
# cat /etc/vsftpd.conf
Send the command output to Huawei technical
support engineers.
230001-200 1. Alarm item
CheckID : 230001
CheckItem : check_ftpstatus
Status : NA
Standard : Check the configuration of the
FTP services on the server and check whether the FTP
services are running. In normal cases, the FTP
services are running properly
Desc : 230001-200:NA.
Solution : NA
the /etc/vsftpd.conf file. If the analysis results
include this alarm, the FTP service is not started. Run
the into. Run the /usr/sbin/ftpd & command to start
the FTP service. If the problem persists, contact
Huawei technical support engineers.
1.1.4 230006_Verifying the Disk Mirror Status

Item Verifying the disk mirror status
Check ID 230006
Application SUSE ia64

System

CheckItem : check_limit

U2000
Status : ERROR
Desc : 230006-200: there mirror status is
error.
Standard : run 'mdadm --detail /dev/md0
/dev/md1', then use (1)grep -E '/dev/sda|dev/sdb' | grep
-v 'active sync' (2)grep 'State :' | grep -v 'clean', when
there's no rows left, everything is ok. What's more, it's
means not involved if mdadm dosen't work
Solution : If Local harddisk failed,please
Autorepair : NA
Area : System
Message : The mdadm status is abnomal
Verify that the RAID configuration information in the
/dev/md0 and /dev/md1 files comply with
requirements. If the analysis results include this alarm,
the /dev/md0 and /dev/md1 files are not configured as
required. Log in to the OSS server as user root and run
the following command to collect information:
#mdadm --detail /dev/mdo /dev/md1
engineers.
230006-201 1. Alarm item
CheckID : 230006
Status : ERROR
Desc : 230006-201: the sda in the mirror is
error
Autorepair : NA
Area : System
Message : The sda in the mirror is error
# mdadm --detail /dev/mdo /dev/md1

U2000

engineers.
230006-202 1. Alarm item
CheckID : 230006
Status : ERROR
Desc : 230006-202: the sdb in the mirror is
error.
Autorepair : NA
Area : System
Message : The sdb in the mirror is error
requirements.
If the analysis results include this alarm, the /dev/md0
and /dev/md1 files are not configured as required. Log
in to the OSS server as user root and run the following
command to collect information:
engineers.
230006-101 1. Alarm item
CheckID : 230006
Status : NA
Desc : 230006-101: there is no mirror .
Solution : NA
Autorepair : NA
Area : System
Message : There is no mirror

U2000

engineers.
Remarks Only support HP rx7640 midrange computer
1.1.5 230008_Verifying the SUSE OS Version

Item Verifying the SUSE OS version
Check ID 230008
Application SUSE
System

Solution Check ID : 230008-102
Description : get the version of the OS
Info/log file : OS_Version_Number.txt
Detail : 230008-102: "there is no
/etc/SuSE-release."
Standard : Check the /etc/SuSE-release file
to verify the OS version.
Status : WARNING
Check the /etc/SuSE-release file to verify the OS
version, and save the command output to the
OS_Version_Number.txt file. If the analysis results
include this alarm, the information is not collected.
1.1.6 230011_Verifying the OS logs

Item Verifying the OS logs
Check ID 230011
Application SUSE
System

CheckItem : checkMessage
Status : WARNING
Desc : 230011-101: The message is

U2000
abnormal.
Standard : Check whether the error
information exists in the /var/log/messages file.
Solution : if the messages log contant error
info,the os may be abnormal,please contact Huawei
technical support engineers.
Autorepair : NA
Area : System
Message : The message is abnormal.
Verify that the /var/log/messages file has error
information. If the analysis results include this alarm,
the /var/log/messages file has error information. Log in
to the OSS server as user root and run the following
command to collect information:
#cat /var/log/messages
engineers.

U2000
1.1.7 500006_Check the IO speed of file system

Item Check the IO speed of file system
Check ID 500006
Application Linux
System

CheckItem : Check the IO speed of file system
Status : WARNING
Desc : 500006-200: The I/O speed is low.
Standard : Using dd command to create a file with
size 1G, and count the time,if the time is grant than 5
min,then the I/O speed is low.
Solution : If the I/O of diskarry or local disk is
poor, the service may be slow. Please contact Huawei
Autorepair : NA
Area : os
Test disk I/O. if the analysis results include this alarm, the
The I/O speed is low. ,contact Huawei technical support
engineers.
1.1.8 500007_Check disk array monitor configuration

Item Check disk array monitor configuration
Check ID 500007
Application PCServer
System

CheckItem : Check disk array monitor
configuration
Status : WARNING
Desc : 500007-200: The disk array monitor is
not configured.
Standard : Query Disk Array Type in the location
information, and configure the disk array monitoring
function again. For details, see the section about the
monitoring configuration for the corresponding disk array
type in the administrator guide of the corresponding
networking.
Solution : Please contact Huawei technical

U2000
support engineers.
Autorepair : NA
Area : os
Check disk array monitor config. if the analysis results
include this alarm, The disk array monitor is not
configured, Query Disk Array Type in the location
information, and configure the disk array monitoring
function again. For details, see the section about the
monitoring configuration for the corresponding disk array
type in the administrator guide of the corresponding
networking.
Remarks The ATAE Cluster networking is not supported.
1.1.9 500009_Check OSS backup status

Item Check OSS backup status
Check ID 500009
Application Linux
System

CheckItem : Check OSS backup status
Status : WARNING
Desc : 500009-400: The system backup was
failed.
Standard : Check whether the system backup is
ok.if the system backup less than 7 days,the result is ok,else
the result is error.
Solution : Please finish the dynamic data backup as
soon as possible. Make sure the data is safe. How to backup
the dynamic data, please see the chapter "Backing Up
U2000 Dynamic Data" in “U2000 administrator guide”.If
you have any question, please contact Huawei technical
support engineers.
Autorepair : NA
Area : os
Check backup status. if the analysis results include this
alarm, The system backup was failed ,contact Huawei
1.1.10 500015_Check Precaution

Item Check Precaution

U2000
Check ID 500015
Application SUSE
System

CheckItem : Check Precaution
Status : ERROR
Desc : 500015-200: Some precaution
notice should be executed.
Standard : Check whether the precaution
notice need to excuted.
Solution : Please get the pecaution notice list
from 500015_PrecautionNotice directory in the
package.
Autorepair : NA
Area : os
Check whether the precaution notice need to
excuted, if there is precaution not executed,Please
contant Huawei technical support engineers for
help.
Precise Precaution List:

Precaution Notice-Bash Vulnerabilities in the Operating Systems of the
M2000, PRS, CME, and SONMaster-20141129-A-3.0
http://support.huawei.com/carrier/docview!docview?nid=SC2000000790
&path=PBI1-21262245/PBI1-21782535/PBI1-21782536/PBI1-1997500
5/PBI1-14033
Precaution Notice-NTP Vulnerabilities in the Operating Systems of the

U2000, PRS-20150119-A-1.0
http://support.huawei.com/carrier/docview?nid=SC2000001253&path=P
BI1-7851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/PBI1-1403
3
remark
Precaution Notice-GLIBC Vulnerabilities in the Operating Systems of

the M2000,U2000,PRS,CME and SONMaster-20150316-A-2.0
&path=PBI1-7851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/P
BI1-14033
Precaution Notice-NTP Vulnerabilities in the Operating Systems of the

U2000, PRS, CME and SONMaster-20150204-A-1.0
&path=PBI1-21262245/PBI1-21782535/PBI1-21782536/PBI1-1997500
5/PBI1-14033

U2000
Vague Precaution List:

Precaution Notice-Load on MED 1 in an U2000&U2000-M ATAE
Cluster System Capable of Managing More Than 800 Equivalent NEs
Exceeds Its Management Capacity-20141120-A-1.0
http://support.huawei.com/carrier/docview?nid=SC2000000652&path=P
BI1-7851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/PBI1-1403
3
1.1.11 500020_Check server IP conflict

Item Check server IP conflict
Check ID 500020
Application SUSE/Linux/PCserver
System

CheckItem : Check server IP conflict
Status : WARNING
Desc : 500020-200: IP conflict exists.
Standard : SuSE OS to SuSE execute command
arping,Detect ip whether the conflict.
Solution : Please replanning ip address
configuration, If you have any questiones, please contact
Autorepair : NA
Area : os
Check IP conflic. if the analysis results include this alarm, t
IP conflict exists, Please replanning ip address
configuration.
1.1.12 500025_Checking the disk size planned for the

/export/home on the database node
Item Checking the disk size planned for the /export/home on the database node
Check ID 500025
Applicati SUSE
on System

U2000

Solution 00 CheckID : 500025
CheckItem : Checking the disk size planned for the
/export/home on the database node
Status : WARNING
Desc : 500025-200: The disk size planned for the
/export/home on the database node is incorrect.
Standard : The disk size planned for the /export/home
on the database node is 50G.
Solution : Perform the operations provided in the technical
guide at the following website:
http://support.huawei.com/carrier/navi?coltype=software#col=
software&detailId=PBI1-23078645&path=PBI1-
7851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/PBI1-2
1427632
Autorepair : NA
Area : OS
Message : The disk size planned for the /export/home
on the database node is incorrect.
Perform the operations provided in the technical guide at the
following website:
http://support.huawei.com/carrier/navi?coltype=software#col=
software&detailId=PBI1-23078645&path=PBI1-
7851894/PBI1-7854702/PBI1-7275896/PBI1-21103986/PBI1-2
1427632
Remarks This check item applies only to virtualization pre-integration networking.
1.2 Oracle Database

1.2.1 320001_ Check the oracle user configure file
Item Check the oracle user configure file
Check ID 320001
Application SUSE
System

CheckItem : Check the oracle user configure
file
Status : ERROR

U2000
Desc : 320001-200: Check the oracle

user home directory.
Standard : There is error in /etc/passwd.
Solution : If encounted,may cause login
oracle fail,please contact GTAC M2000 group.
Autorepair : NA
Area : Database
Message : The oracle user home directory is
incorrect.
Check the /etc/passwd contains oracle
information,use:
cat /etc/passwd | grep oracle|awk -F":" ‘{print $6}’
320001-201 1. Alarm item
CheckID : 320001
CheckItem : Check the oracle user configure
file
Status : WARNING
Desc : 320001-201: Check
the .bash_profile.
Standard : The .bash_profile is WARNING.
Solution : If encounted,may cause login
oracle fail,please contact GTAC M2000 group.
Autorepair : NA
Area : Database
Message : The setting in
/opt/oracle/.bash_profile is incorrect.
The bash configuration file must contain an Oracle
environment variable, checking that the configuration
file content is /export/home/oracle/.bash_profile.
1.2.2 320002_Verifying the Operating Status of the Oracle

Database
Item Verifying the operating status of the Oracle database (currently, the
archive logs are not involved)
Check ID 320002
Application SUSE
System


U2000
CheckItem : checkOracleStatus
Status : ERROR
Desc : 320002-101: Oracle running status
is abnormal.
Solution : Oracle is abnormal, please contact
Autorepair : NA
Area : Database
Message : Oracle db is not running
or
CheckID : 320002
CheckItem : checkOracleStatus
Status : OK
Desc : 320002-101: Oracle running status is
abnormal.
Standard : The output of command 'ps -ef' must
contain all of the Oracle processes.
Solution : Please execute "ps -ef | grep ora_"
and "ps -ef | grep tnslsnr"
Autorepair : NA
Area : Database
Message : Oracle LISTENER is not running
Verify that the Oracle database listening process has
been started. If the analysis results include this alarm,
the listening process has not been started. Run the
following commands to start the listening process:
#su - oracle
>lsnrctl start
Query the command output to verify that the process is
started successfully. If the process fails to start, send
the command output to Huawei technical support
engineers.
1.2.3 320003_Verifying the Oracle alert_log Information

Item Verifying the Oracle database logs
Check ID 320003
Application System SUSE

CheckItem : check_Oracle_ORA

U2000
Status : ERROR
Desc : 320003-101: check the
alert_ossdb.log
Standard : The Oracle log file 'alert_ossdb.log'
contains no 'ORA-' information.
Solution : If ORA-00600,ORA-07445
occurred in alert log,please contact Huawei technical
support engineers.
Autorepair : NA
Area : Database
Message : can not find Oracle LOG
Verify that the Oracle database logs are available.
Check whether the alert_${DBNAME}.log file
contains the Oracle error information. Users must
manually check this item.
320003-102 1. Alarm item
CheckID : 320003
Status : ERROR
Desc : 320003-102: check the Oracle
ORA ERROR
support engineers.
Autorepair : NA
Area : Database
Message : There is ORA internal ERROR in
Oracle
Verify that the Oracle database logs are available. If the
analysis results include this alarm, the Oracle database
logs are not collected. Contact Huawei technical
support engineers.
320003-200 1. Alarm item
CheckID : 320003
Status : WARNING
Desc : 320003-200: check the Oracle
ORA WARNING

U2000

support engineers.
Autorepair : NA
Area : Database
Message : Oracle ORA ERROR is exist.
Verify that the Oracle database logs are available. If the
analysis results include this alarm, the Oracle database
logs are not collected. Contact Huawei technical
support engineers.
1.2.4 320007_Verifying the Configuration of Other Parameters for

the Oracle Database
Item Verifying the configurations of other parameters for the Oracle database
Check ID 320007
Application SUSE
System

CheckItem : check_other_parameter
Status : ERROR
Desc : 320007-101: the Oracle is not
available
Standard : In the Oracle parameters, the value
of 'open_cursors', 'processes', 'sessions' and
'max_dispatchers' must be set 3000, the value of
'recyclebin' must be set 'OFF'.
Solution : The database is abnormal,if having
question,Contact Huawei technical support engineers.
Autorepair : NA
Area : Database
Message : The Oracle is not available
Run the show_parameters command in the Oracle
database to collect the Oracle database system
parameters. If the analysis results include this alarm, the
information is not collected. Manually run the following
command to collect the information:
# ps -ef | grep ora_
engineers.
320007-201 1. Alarm item
CheckID : 320007

U2000
Status : WARNING
Desc : 320007-201: the other parameter is
error
Solution : The database is abnormal,if having
question,Contact Huawei technical support engineers.
Please pay attention. The change will take into effect
after restarting Oracle server,this may have impact on
business.Please perform restarting operation according
to administrator guide.
Autorepair : NA
Area : Database
Message : The other parameter is error
Oracle system configuration parameters do not meet the
plan requirements. Run the following commands to
collect information:
# su - oracle
$sqlplus / as sysdba
>show parameters;
>exit;
engineers.
320007-203 1. Alarm item
CheckID : 320007
Status : NA
Desc : 320007-203: NA
Solution : NA
Autorepair : NA
Area : Database
Message : The other parameter is WARNING

U2000

Oracle system configuration parameters do not meet the
plan requirements. Collect and send related information
to Huawei technical support engineers.
1.2.5 320016_ Check size of oracle log

Item Check size of oracle log
Check ID 320016
Application SUSE
System

CheckItem : Check size of oracle log
Status : WARNING
Desc : 320016-201: Check oracle listener
log
Standard : Can not find the listener log
Solution : If listener.log is not exist or size
large than
524288000KB ,please run the follwing command to
clear:$ cat /dev/null >
$ORACLE_BASE/diag/tnslsnr/`hostname`/listener/trac
e/listener.log.
Autorepair : NA
Area : Database
Message : Can not find the listener log.
Listener.log is not exist or size large than
524288000KB,run the follwing command: $ cat
/dev/null >
e/listener.log.
320016-202 1. Alarm item
CheckID : 320016
CheckItem : Check size of oracle log
Status : ERROR
Desc : 320016-202: Check oracle
listener log.
Standard : The listener log too large
Solution : If listener.log is not exist or
size large than 524288000KB ,please run the follwing
command to clear: $ cat /dev/null >
e/listener.log.

U2000
Autorepair : NA
Area : Database
Message : The listener log too large.
Listener.log is not exist or size large than
524288000KB,run the follwing command: $ cat
/dev/null >
e/listener.log.
320016-203 1. Alarm item
CheckID : 320016
CheckItem : NA
Status : NA
Desc : 320016-203: NA
Standard : NA
Solution : NA
Autorepair : NA
Area : Database
Message : NA
NA
1.2.6 320017_Verifying the table space of the Oracle Database

Item Verifying the table space of the Oracle Database
Check ID 320017
Application SUSE
System

CheckItem : check oracle table space
Status : WARNING
Desc : 320017-201: Can not find the info
file.
Solution : If tablespace.txt isn't exist or usage
large than 85%, please contact Huawei technical
support engineers.
Autorepair : NA
Area : Database
Message : Can not find the info file.

U2000
Verifying the table space of the Oracle Database. If the

analysis results include this alarm, the table space
information is not collected. Run the following
commands to collect information:
#su - oracle
>sqlplus / as sysdba
SQL> select TABLESPACE_NAME,
sum(bytes)/1024/1024 as free_size_M from
dba_free_space group by tablespace_name;
engineers.
320017-202 1. Alarm item
CheckID : 320017
CheckItem : check oracle table space
Status : ERROR
Desc : 320017-202: The table space is not
enough.
Standard : The used capacity of tablespace
must be less than 85% of total.
Solution : If tablespace.txt isn't exist or usage
large than 85%, please contact Huawei technical
support engineers.
Autorepair : NA
Area : Database
Message : The table space is not enough.
Verifying the table space of the Oracle Database . If the
analysis results include this alarm, the table space of the
Oracle Database is not enough. Please contact Huawei

U2000
1.3 Logical Volume Management

1.3.1 350002_Check VxVm disk status
Item Check VxVm disk status
Check ID 350002
Application Linux
System

Solution
CheckID : 350002
CheckItem : Check VxVm disk status
Status : NA
Desc : 350002-101: the VxVM is not
installed
Standard : The normal disk in the output of
vxdisk list.
Solution : NA
Autorepair : NA
Area : System
Message :NA.
Collect the vxdisk-list.out which is the information file of
VxVM. If the analysis results include this alarm, the
command execution encounters an error. Manually run
the following command as user root:
# vxdisk list
engineers.

U2000
350002-201 1. Alarm item

CheckID : 350002
CheckItem : Check VxVm disk status
Status : WARNING
Desc : 350002-201: the VxVM disk status is
abnormal
Standard : The normal disk in the output of
vxdisk list.
Solution : This problem illustrate there may be
some fauty disks, it will result in the service is
abnormalal. Please contact Huawei technical support
engineers.
Autorepair : NA
Area : System
Message : The VxVM disk status is abnormal.
Collect the information file of VxVM. If the analysis
results include this alarm, the command execution
encounters an error. Manually run the following command
as user root:
# vxdisk list
engineers.
1.3.2 350003_Check VxVm volume status

Item Check VxVm volume status
Check ID 350003
Application Linux
System

CheckItem : check VxVM volume status
Status : NA
Desc : 350003-101: the VxVM is not
installed
Standard : In the vxprint command output,
the key state of v, pl, and sd of all volumes must be
enabled. The v and pl of all volumes must be in the
active state.
Solution : NA
Autorepair : NA

U2000
Area : System
Message : The VxVM is not installed
encounters an error. Manually run the following
command as user root:
#vxprint
engineers.
350003-201 1. Alarm item

CheckID : 350003
CheckItem : check VxVM volume status
Status : WARNING
Desc : the 350003-201: the VxVM
volume status is abnormal
Standard : In the vxprint command output,
the key state of v, pl, and sd of all volumes must be
enabled. The v and pl of all volumes must be in the
active state.
Solution : This problem may cause service
abnormal,please run the following command.
# vxvol -g <diskgroupname> startall
Autorepair : NA
Area : System
Message : The VxVM volume status is
abnormal
encounters an error. Manually run the following
command as user root:
#vxprint
engineers.
1.3.3 350005_Check LVM volume status

Item Check LVM volume status
Check ID 350005
Application Linux
System

U2000

CheckItem : Check LVM volume status
Status : WARNING
Desc : 350005-201: Not found any logical
volumes info
Standard : Run the lvdisplay command to
check whether each logical volume is available. In normal
cases, all logical volumes must be available.
For HP rx7640 and HP rx6600, run the #lvdisplay
command to check whether the capacity of the
exporthome logical volume is 750 GB.
Check the /etc/fstab file to verify that the exporthome
logical volume has been mounted to the /export/home
directory.
Run the following command to check whether required
raw devices have been set up:
#ls -l /dev/raw/*
Solution : If database startup fail or mount
/export/home abnormal,Contact GTAC M2000 group
for assistance.
Autorepair : NA
Area : System
Message : Not found any logical volumes info
Collect information about the system volumes. If the
analysis results include this alarm, the volume
information is not collected.
Log in to the OSS server as user root, manually run the
following command, and send the command output to
Huawei technical support personnel.
#lvdisplay
350005-202 1. Alarm item
CheckID : 350005
Status : WARNING
Desc : 350005-202: Some volumes are not
available
directory.

U2000

#ls -l /dev/raw/*
for assistance.
Autorepair : NA
Area : System
Message : Some volumes are not available
Check the volume management information. If the
analysis results include this alarm, the volume
management information is not collected. Manually run
the following command and send the command output
to Huawei technical support personnel:
#lvdisplay
350005-203 1. Alarm item
CheckID : 350005
Status : WARNING
Desc : 350005-203: Some volumes are not
available
directory.
#ls -l /dev/raw/*
for assistance.
Autorepair : NA
Area : System
Message : No /export/home record in
/etc/fstab file
analysis results include this alarm, the volume creation
does not meet the plan requirements. Manually run the
following command and send the command output to

U2000
Huawei technical support personnel:

#lvdisplay
350005-204 1. Alarm item
CheckID : 350005
Status : WARNING
Desc : 350005-204: Not any record in
/dev/raw/ dir
directory.
#ls -l /dev/raw/*
for assistance.
Autorepair : NA
Area : System
Message : Not any record in /dev/raw/ dir
#lvdisplay
350005-205 1. Alarm item
CheckID : 350005
Status : WARNING
Desc : 350005-205: The raw device own
isn't Oracle

U2000

directory.
#ls -l /dev/raw/*
for assistance.
Autorepair : NA
Area : System
Message : The raw device own is not Oracle
#lvdisplay
350005-206 1. Alarm item
CheckID : 350005
Status : NA
Desc : 350005-206:The vcs is not installed
directory.
#ls -l /dev/raw/*
Solution : NA
Autorepair : NA
Area : System
Message : lvm is not install.
#lvdisplay

U2000
1.4 VCS Cluster

1.4.1 340009_Check VCS node running status
Item Check VCS node running status
Check ID 340009
Application Linux
System

CheckItem : Check VCS node running status
Status : NA
Desc : 340009-101: the vcs is not installed
Standard : Please execute command 'hasys
-state' check whether all node Value is RUNNING.
Solution : NA
Autorepair : NA
Area : System
Message : NA
Collect the VCS information. if the analysis results
include this alarm, the VCS information is not collected
correctly. Manually run the following command:
# hasys -state
engineers.

U2000
340009-201 1. Alarm item

CheckID : 340009
CheckItem : Check VCS node running status
Status : WARNING
Desc : 340009-201:the vcs status is
abnormal
Standard : Please execute command 'hasys
-state' check whether all node Value is RUNNING.
Solution : Use the command "hasys -state" to
query node status, if the status of one node is not
running, U2000 service may be abnormal, please log
the fauty server, run the following command to restart
the VCS, the operation will interrupt the current node
U2000 service.
# hastop -local -force
# hastart
If you have any questions, please contact Huawei
Autorepair : NA
Area : System
Message : The vcs status is WARNING
Verify the running status of VCS nodes. if the analysis
results include this alarm, the VCS node is not running.
Manually run the following command:
# hasys -state
engineers.
1.4.2 340010_Check VCS private network status

Item Check VCS private network status
Check ID 340010
Application Linux
System

CheckItem : Check VCS private network status
Status : WARNING
Desc : 340010-201: the heartbeat
connection is abnormal
Standard : Execute the command lltstat -nvv
to check that the status of OPEN is twice that of UP,
otherwise it is error.

U2000
Solution : please check whether the network

for heartbeat is loose. If you have any questions, please
Autorepair : NA
Area : System
Message : The heartbeat connection status is
abnormal
Verifying the VCS heartbeat connection. if the analysis
results include this alarm, the VCS private network is
not running. Log in to the OSS server as user root and
manually run the following command:
# lltstat -nvv
engineers.
340010-101 1. Alarm item
CheckID : 340010
CheckItem : Check VCS private network status
Status : NA
Desc : 340010-101: there exists no
heartbeat connection
Standard : Execute the command lltstat -nvv
to check that the status of OPEN is twice that of UP,
otherwise it is error.
Solution : NA
Autorepair : NA
Area : OS
Message : NA
Verifying the VCS heartbeat connection. if the analysis
results include this alarm, there exists no heartbeat
connection.
1.4.3 340011_Check VCS configuration

Item Check VCS configuration
Check ID 340011
Application Linux
System

CheckItem : Check VCS configuration
Status : NA
Desc : 340011-101: the vcs is not

U2000
installed
Standard : Normally run the command hacf
-verify /etc/VRTSvcs/conf/config,the output is
empty.
Solution :NA
Autorepair : NA
Area : System
Message : the vcs is not installed
Verify whether the VCS configuration information
is collected. if the analysis results include this alarm,
the VCS configuration information is not collected
correctly. Log in to the OSS server as user root and
# hacf -verify /etc/VRTSvcs/conf/config
support engineers.
340011-201 1. Alarm item
CheckID : 340011
CheckItem : Check VCS configuration
Status : WARNING
Desc : 340011-201: the vcs config is
incorrect
Standard : Normally run the command hacf
-verify /etc/VRTSvcs/conf/config,the output is
empty.
Solution : To log in to an abnormal server,
start VCS as root with the following command.
# hastart
# hastatus
If hastatus is still reported "Can not connect to VCS
engine" error, please execute the following
command to collect Veritas explorer information and
return with the inspection report package, contact
Huawei technical support engineers in-depth
analysis:
# /opt/VRTSspt/VRTSexplorer/VRTSexplorer
If prompted, please enter the carriage return to
continue. At the end of the execution, the result
packet storage path is printed.
Autorepair : NA
Area : System
Message : The vcs config is incorrect
Check the VCS configuration information. if the
analysis results include this alarm, the VCS

U2000
configuration is incorrect. Log in to the OSS server

as user root and manually run the following
command:
# hacf -verify /etc/VRTSvcs/conf/config
support engineers.
1.4.4 340012_Check VCS resource group status

Item Check VCS resource group status
Check ID 340012
Application Linux
System

CheckItem : Check VCS resource group status
Status : NA
Desc : 340012-101: Device group is not
exist,does not need to check it
Standard : All resources must be ONLINE
status on one node.
Solution : Device group is not exist,does not
need to check it
Autorepair : NA
Area : System
Message : Device group is not exist
Verify whether the VCS configuration information is
collected. if the analysis results include this alarm, the
VCS is not installed ,device group is not exist.
340012-201 1. Alarm item
CheckID : 340012
CheckItem : Check VCS resource group status
Status : NA
Desc : 340012-201: Some device group is
OFFLINE on active and backup
Standard : All resources must be ONLINE
status on one node.
Solution : Please restart the VCS as root and
execute the following command.
# hastop -local -force
# hastart
Autorepair : NA

U2000
Area : System
Message : Some device group is OFFLINE on
active and backup
Verify the VCS configuration information. if the analysis
results include this alarm, the VCS configuration is
incorrect. Log in to the OSS server as user root and
# hagrp -state
engineers.

U2000
OSMU Health Check Verification Items 2 Common Verification Items
2 Common Verification Items
This chapter describes the OSS check items, security check items, sybase database check
items, and disk array check items.

U2000
2.1 OSS Verification Items

2.1.1 400000_Verifying the OSS Software Version
Item Verifying the OSS software version
Check ID 400000
Application SUSE
System

Solution Check ID : 400000
Description : get the version of OSS
Info/log file : trace/displayVersion-c.out
Detail : 400000-200: "Can not get the
version of the OSS."
Status : WARNING
Standard :Collect the OSS version
information.
Verify the OSS software version. If the analysis results
include this alarm, the information is not collected.
2.1.2 410001_ Check OSS Status

Item Check OSS Status
Check ID 410001
Application SUSE
System

CheckItem : Check OSS Status
Status : NA
Desc : 410001-101: OSS is not install
Standard :The status of all OSS services must
be running.
Solution : NA
Autorepair : NA
Area : Business
Message : OSS is not install

U2000

Verify that the OSS process is functioning properly. If
the analysis results include this alarm, the information is
not collected. Contact Huawei technical support
engineers.
410001-200 1. Alarm item
CheckID : 410001
CheckItem : Check OSS Status
Status : ERROR
Desc : 410001-200: OSS services is
abnormal
Standard :The status of all OSS services must
be running.
Solution : This problem may cause service
abnormal,please run the following command,
# . /opt/oss/server/svc_profile.sh
# svc_adm -cmd startsvc <SystemService>
Feedback to Huawei technical support engineers.
Autorepair : NA
Area : Business
Message : OSS services is abnormal
Verify that the OSS process is functioning properly. If
the analysis results include this alarm, the OSS service
is not running. Start the OSS service by referring to the
corresponding administrator guide. If the OSS service
fails to start, contact Huawei technical support
engineers.
2.1.3 410002_ Check the service standby blade routes integrity

Item Check the service standby blade routes integrity
Check ID 410002
Application System Linux

Detailed Solution 410002-100 Alarm item
CheckID : 410002
CheckItem : Check the
service standby blade routes
integrity
Status : OK
Desc :
410002-100: There is no
problem of U2000 standby
blade routes.

U2000
Risk :NA
Standard : Check the
service standby blade
/etc/sysconfig/network/route
s co ntains all the routes of
the master and slave blade.
Solution : NA
Autorepair : NA
Area : Business
410002-200 Alarm item
CheckID : 410002
CheckItem : Check the
service standby blade routes
integrity
Status : ERROR
Desc :
410002-200: The service
standby blade routes does
not include all t he routes of
the master and the slave
blade
Risk : After the
servise on master or slave is
switched over to the
standby, there is a risk that
NE is disconnected.
Standard : Check the
service standby blade
/etc/sysconfig/network/route
s co ntains all the routes of
the master and slave blade.
Solution : Log in
to ATAE OSMU and add
missing routes to the
corresponding service
standby blade.
Autorepair : NA
Area : Business
Remarks This check item is executed only on the U2000 standby

board of the ATAE cluster.
2.1.4 410988_Collecting precaution information

Item Collecting precaution information
Check ID 410988
Application SUSE/Linux/PCServer

U2000
System

CheckItem : collect_precaution
Status : WARNING
Desc : 410988-200: there is no precaution
on this OSS.
Standard : Collect the precaution file if the file
SpecialOperation.dat exists.
Solution : Collect information about
precautions or workarounds implemented on the server.
If there is a warning message in the check result, no
precautions or workarounds are recorded on the server
Autorepair : NA
Area : Business
Message : there is no precaution on this OSS.
Collect information about precautions or workarounds
implemented on the server. If there is a warning message
in the check result, no precautions or workarounds are
recorded on the server.
2.1.5 500000_Check the file and directory permissions

Item Check the file and directory permissions
Check ID 500000
Application SUSE
System

CheckItem : Check the file and directory
permissions
Status : ERROR
Desc : 500000-200: Part of the files
permission is not right.
Standard : please check according the base file
Task_Check.xml.
Solution : Please get the
trace/500000_check_dir.log from the package and then
Autorepair : NA
Area : Business
Message : Part of the files permission is not
right.

U2000

Please get the trace/500000_check_dir.log from the
package and then contact Huawei technical support
engineers.
500000-300 1. Alarm item
CheckID : 500000
CheckItem : Check the file and directory
permissions
Status : WARNING
Desc : 500000-300: The configuration file
may be not OK.
Standard : please check according the base file
Task_Check.xml.
Solution : Please get the Task_Check.xml file
and then contact Huawei technical support engineers.
Autorepair : NA
Area : Business
Message : Unkown type, Please check the
Check_Dir.xml.
Please get the Task_Check.xml file and then contact

U2000
2.1.6 500005_ Check permission and owner of file and directory

Item Check permission and owner of file and directory
Check ID 500005
Application SUSE/Linux/PCServer
System

CheckItem : Check permission and owner of file
and directory
Status : WARNING
Desc : 500005-200: Check permission and
owner of file or directory is error.
Standard : Get right permission or owner from
CheckList.xml in package.
Solution : Run the following command with
user root to repair the inspection items apper problem.
If the command fails to execute,please contact Huawei
# cd /opt/oss/server/rancn/tools/SOPRecoverTool
# ./SysConfigRecover.sh repair
Autorepair : NA
Area : OS
Message : Check permission and owner of file
or directory is error.
If the analysis results include this alarm, please get the
CheckSystemDirLog from the package and then contact
Huawei technical support.
Remarks None
2.1.7 500121_Check main directory link

Item Check main directory link
Check ID 500121
Application SUSE
System

U2000

CheckItem : Check main directory link
Status : WARNING
Area : Business
Desc : 500121-101: Abnormal main
directory link. Risk: Core functions may be affected, such
as NBI export and performance result reporting.
Standard : Check whether the path link is
correct. /export/home/sysm/export/home/sysm/ftproot
-> ../../../ftproot
Solution :
Login the server which has problems as root user and
execute the following commands:
# mkdir -p /export/home/sysm/export/home/sysm
# chmod -R 750 /export/home/sysm/export
# chown -R ftpuser:ossgroup /export/home/sysm/export
# cd /export/home/sysm/export/home/sysm
# ln -sf ../../../ftproot ftproot
# chown -h ftpuser:ossgroup
/export/home/sysm/export/home/sysm/ftproot
Solution Impact: None
Autorepair : NA
NA.

U2000
500121-102 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /export/home/sysm/export/home/sysm/internalftp
-> ../../../internalftp/ link.
Solution :
# mkdir -p /export/home/sysm/export/home/sysm
# cd /export/home/sysm/export/home/sysm
# ln -sf ../../../internalftp internalftp
/export/home/sysm/export/home/sysm/internalftp
Autorepair : NA
NA.

U2000
500121-103 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /export/home/sysm/export/home/omc/var/fileint
-> ../../../../opt/oss/server/var/fileint
Solution :
# mkdir -p /export/home/sysm/opt/oss/server/var
# chmod -R 750 /export/home/sysm/opt
# chown -R ftpuser:ossgroup /export/home/sysm/opt
# cd /export/home/sysm/opt/oss/server/var/
# mkdir fileint
# chmod -R 750 fileint
# chown -R ossuser:ossgroup fileint
# mkdir -p /export/home/sysm/export/home/omc/var
# cd /export/home/sysm/export/home/omc/var
# ln -sf ../../../../opt/oss/server/var/fileint fileint
# chown -h ossuser:ossgroup
/export/home/sysm/export/home/omc/var/fileint
Autorepair : NA
NA.

U2000
500121-104 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /export/home/sysm/export/home/omc/var/itf_n
-> ../../../../opt/oss/server/var/itf_n
Solution :
# mkdir -p /export/home/sysm/opt/oss/server/var
# chmod -R 750 /export/home/sysm/opt
# chown -R ftpuser:ossgroup /export/home/sysm/opt
# cd /export/home/sysm/opt/oss/server/var/
# mkdir itf_n
# chmod -R 750 itf_n
# chown -R ossuser:ossgroup itf_n
# mkdir -p /export/home/sysm/export/home/omc/var
# cd /export/home/sysm/export/home/omc/var
# ln -sf ../../../../opt/oss/server/var/itf_n itf_n
/export/home/sysm/export/home/omc
Autorepair : NA
NA.

U2000
500121-105 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /export/home/omc/var/itf_n ->
/export/home/sysm/opt/oss/server/var/itf_n
Solution :
# mkdir -p /export/home/omc/var
# chmod 750 /export/home/omc/var
# chown ossuser:ossgroup /export/home/omc/var
# cd /export/home/omc/var
# ln -sf /export/home/sysm/opt/oss/server/var/itf_n itf_n
# chown -h ossuser:ossgroup /export/home/omc/var/itf_n
Autorepair : NA
NA.

U2000
500121-106 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /export/home/omc/var/fileint ->
/export/home/sysm/opt/oss/server/var/fileint
Solution :
# mkdir -p /export/home/omc/var
# chmod 750 /export/home/omc/var
# chown ossuser:ossgroup /export/home/omc/var
# cd /export/home/omc/var
# ln -sf /export/home/sysm/opt/oss/server/var/fileint
fileint
/export/home/omc/var/fileint
Autorepair : NA
NA.

U2000
500121-107 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /opt/oss/server/etc -> /export/home/omc/etc
Solution :
#cd /opt/oss/server
# ln -sf /export/home/omc/etc etc
# chown -h ossuser:ossgroup /opt/oss/server/etc
Autorepair : NA
NA.
500121-108 1. Alarm item
CheckID : 500121
Status : WARNING
Area : Business
correct. /opt/oss/server/var -> /export/home/omc/var
Solution :
# cd /opt/oss/server
# ln -sf /export/home/omc/var var
# chown -h ossuser:ossgroup /opt/oss/server/var
Autorepair : NA
NA.

U2000
500121-109 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /opt/oss/server/med -> /export/home/omc/med
Solution :
# ln -sf /export/home/omc/med med
# chown -h ossuser:ossgroup /opt/oss/server/med
Autorepair : NA
NA.
500121-110 1. Alarm item
CheckID : 500121
Status : WARNING
Area : Business
correct. /opt/oss/server/hedex -> /export/home/omc/hedex
Solution :
# ln -sf /export/home/omc/hedex hedex
# chown -h ossuser:ossgroup /opt/oss/server/hedex
Autorepair : NA
NA.

U2000
500121-111 1. Alarm item

CheckID : 500121
Status : WARNING
Area : Business
correct. /opt/oss/server/common/tomcat/webapps ->
/export/home/omc/webapps
Solution :
# cd /opt/oss/server/common/tomcat
# ln -sf /export/home/omc/webapps webapps
/opt/oss/server/common/tomcat/webapps
Autorepair : NA
NA.
500121-112 1. Alarm item
CheckID : 500121
Status : WARNING
Area : Business
correct. /opt/oss/server/common/sso/data ->
/export/home/omc/sso/data
Solution :
# cd /opt/oss/server/common/sso
# ln -sf /export/home/omc/sso/data data
/opt/oss/server/common/sso/data
Autorepair : NA
NA.

U2000
2.1.8 180023_Obtaining the Version of the U2000 and

Smart_Assistant
Check Item Obtaining the Version of the U2000 and Smart_Assistant
Check Item 180023

ID
Application SUSE
System
Solution 180023-100 1. Alarm item
Check item ID: 180023
Check item: Obtaining the Version of the U2000 and
Smart_Assistant
Status: OK
Area: service
Description: 180023-100: The version number can be
properly obtained.
Check criterion: The version of the U2000 and
Smart_Assistant can be properly obtained.
Solution: N/A
Auto-repair: N/A
Result: The version of the U2000 and Smart_Assistant
can be properly obtained.
N/A
180023-200 1. Alarm item
Check item ID: 180023
Check item: Obtaining the Version of the U2000 and
Smart_Assistant
Status: warning
Area: service
Description: 180023-200: Querying the version of the
U2000 and Smart_Assistant fails.
Solution: Contact Huawei technical support.
Auto-repair: N/A
Contact Huawei technical support.
2.1.9 422104_Checking the core dump path of the service

Item Checking the core dump path of the service
Check ID 422104

U2000
Application SUSE/Linux/PCserver
System

CheckItem : Checking the core dump path of the
service
Status : Normal
Desc : 422104-100: The core dump path of
the service is correct.
Standard : Check whether the value of
kernel.core_pattern is
/opt/oss/server/var/logs/core.%e.%p in the execution
result of the sysctl –a command.
Solution : N/A
Autorepair : N/A
Area : Service
Message : The core dump path of the service is
correct.
Log in to the U2000 server as user ossuser. Then, run the
sysctl -a |grep kernel.core_pattern command as user
root. If "kernel.core_pattern =
/opt/oss/server/var/logs/core.%e.%p" is displayed, the
core dump path of the service is correct. Otherwise,
contact Huawei technical support.
422104-200 1. Alarm item
CheckID : 422104
service
Status : WARNING
the service is incorrect.
Solution : Log in to the U2000 server as user
ossuser. Then, run the following command as user root
to correct the error:
/sbin/sysctl -w
kernel.core_pattern=/opt/oss/server/var/logs/core.%e.
%p 1>/dev/null 2>&1
Autorepair : N/A
Area : Service
Message : The core dump path of the service
is incorrect.

U2000

422104-300 1. Alarm item
CheckID : 422104
service
Status : N/A
the service does not need to be checked.
Solution : N/A
Autorepair : N/A
Area : Service
Message : N/A
2.2 Security Check Items

2.2.1 340004_Check the Database Security Hardening
Item Check the database security hardening
Check ID 340004
Application SUSE
System

CheckItem : Check the database security
hardening
Status : WARNING

U2000
Desc : 340004-200: Please install setdb

tool.
Standard : Use command setdb -v in the
system with database as user root to check whether
the setdb tool is installed.if the command can be
execute,setdb installed.
Solution : The database has the safty risk,
please refer to the SetDB tool guide to intall the
setDB.
Autorepair : NA
Area : Database
Message : Please install setdb tool.
Run the setdb -v command as user root and check
whether any command output is displayed. If no
command output is displayed, security hardening
has not been performed. Then, you need to perform
security hardening.
In an ATAE cluster system, you must log in to the
database board to perform this operation.
Remarks This check item is not applicable to the ATAE cluster offline remote
HA system.
2.2.2 340005_Check the Operating System Security Hardening

Item Check the operating system security hardening
Check ID 340005
Application SUSE
System

CheckItem : Check the operating system
security hardening
Status : WARNING
Desc : 340005-200: Please install
OS security hardening software.
Standard : Use command sek -v in the
system as user root to check whether the OS
security hardening software tool is installed
Solution : The server has the safty risk,
please refer to the SetSuSe tool guide to intall the
SetSuSe.
Autorepair : NA
Area :os

U2000
Message : Please install OS security

hardening software
Run the sek -v command as user root and check
whether any command output is displayed. If no
command output is displayed, security hardening
has not been performed. Then, you need to
perform security hardening.
Remarks This check item is not applicable to the ATAE cluster system database
board, ATAE cluster offline remote HA system.
2.2.3 340006_ Check the security authentication log dump

Item Check the security authentication log dump
Check ID 340006
Application SUSE
System

CheckItem : Check the security authentication
log dump
Status : WARNING
Desc : 340006-200: Authentication log
dump is set incorrectly.
Standard : The authentication log dump files
/etc/logrotate.d/auth and /etc/logrotate.d/secure should
exist and set dump parameter.
Solution : Please execute the precaution to
check:
http://support.huawei.com/carrier/docview!docview?n
id=SC2000001433&path=PBI1-7851894/PBI1-7
854702/PBI1-7275896/PBI1-21103986/PBI1-210434
97 Solution effect: It need restart syslog service of OS.
Autorepair : NA
Area :os
Message : The authentication logs do not set
rotate or the configuration files incorrectly. Risk: The
system log size is large and occupy lots of space for
root partition.
Check the security authentication log dump
configuration files /etc/logrotate.d/auth and
/etc/logrotate.d/secure exist and set correctly. If
files do not exist or set incorrectly, it need execute
precaution notice by manually.
Remarks This check item is not applicable to the ATAE cluster system database

U2000
board, ATAE cluster offline remote HA system.
2.3 Sybase Database

2.3.1 310003_Verifying that No Database Is Offline
Item Verifying that no database is offline
Check ID 310003
Application SUSE
System

CheckItem : Sybase online
Status : WARNING
Desc : 310003-200: The Sybase is
offline.
Standard : online when isql can log on the
database, or offline
Solution : Please log the server as dbuser
user, and run the command "showserver" to check the
sybase process is abnormal or not.
(1) If there are sybase processes, please try to log the
sybase.
(2)If there isn't sybase process, please restart the
sybase by <U2000 Administator Guide>.
(3) The password of sybase user is wrong, please try
connect the sybase again.
If you have any questiones, please contact Huawei

Autorepair : NA
Area : Database
Message : The sybase is offline.
Log in to the Sybase database as user dbuser and run
the sp_helpdb command to verify the database status.
If the analysis results include this alarm, the command
execution encounters an error. Contact Huawei

U2000
2.3.2 310004_ Check sybase boot file parameter

Item Check sybase boot file parameter
Check ID 310004
Application SUSE
System

CheckItem : Check sybase boot file parameter
Status : WARNING
Desc : 310004-101: Sybase boot file configure
is incorrect.
Standard : In the Sybase boot file, the parameters
must contain （1）ATAECluster SLS:
-T4803,-T7717,-T15384,-T589,-T15370,-T4805,-T757,-T598
and -T4084; （2）Other networking types:
-T4803,-T7717,-T15384,-T589,-T15370,-T4805 and -T757.
Solution :（1）ATAECluster SLS: Please use dbuser
to edit the sybase startup file, make sure the file contains the
following parameters.
-T4803 \
-T7717 \
-T15384 \
-T589 \
-T15370 \
-T4805 \
-T757 \
-T598 \
-T4084 \
（2）Other networking types: Please use dbuser to edit the
sybase startup file, make sure the file contains the following
parameters.
-T4803 \
-T7717 \
-T15384 \
-T589 \
-T15370 \
-T4805 \
-T757 \
Autorepair : NA
Area : Database
Message : Sybase bootfile configure is incorrect.

U2000
Log in to the Sybase database as user dbuser and check

whether the parameters of the RUN_SYB file in the /opt /
sybase/ASE-15_0/install directory are not fully included
（1）ATAECluster SLS:
-T4803,-T7717,-T15384,-T589,-T15370,-T4805,-T757,-T598
and -T4084; （2）Other networking types:
-T4803,-T7717,-T15384,-T589,-T15370,-T4805 and -T757.
If the analysis results include this alarm, the command
execution encounters an error. Contact Huawei technical
support engineers.
2.3.3 310005_Check dbuser right

Item Verifying the permissions of user dbuser
Check ID 310005
Application SUSE
System

CheckItem : Check_dbuser_right
Status : WARNING
Desc : 310005-101: dbuser's right is incorrect.
Standard : folds and files below '/opt/sybase',
'/opt/sybase/data', '/export/home/sybdev' and the folds
themselves's owner.group shouble be dbuser.dbgroup
Solution : Run the following commands to change
the owner and group of Sybase database directory by user
root. If the command fails to execute,please contact Huawei
# cd /opt/oss/server/rancn/tools/SOPRecoverTool
# ./SysConfigRecover.sh repair
Autorepair : NA
Area : Database
Message : Dbuser's right is incorrect.
Log in to the Sybase database as user dbuser to verify that
all files in the /opt/Sybase/, /data, /export/home/SYBdev
directories are owned by user dbuser. If the analysis results
include this alarm, the command execution encounters an
error. Contact Huawei technical support engineers.

U2000
2.3.1 310007_Verifying that No Error Is Logged Recently for the

Sybase
Item Verifying that no error is logged recently for the Sybase
Check ID 310007
Application SUSE
System

CheckItem :Check_Sybase_messages
Status : ERROR
Desc : 310007-101: Error messages exist in
Sybase messages.
Standard : collect the sybase log last three
months,and check error and warn information,if the log
contain this information,result is error or warning
Solution : If encounted,May cause database
services abnormal,According to the error code to lookup the
method in Sybase Troubleshooting.
Autorepair : NA
Area : Database
Message : Sybase messages exist error messages
Verify that no error is logged for the Sybase. If the analysis
results include this alarm, contact Huawei technical support
engineers.

U2000
310007-102 1. Alarm item

CheckID : 310007
Status : ERROR
Desc : 310007-102: warning messages exist in
Sybase messages.
Standard : run command tail -5000
$dir/${instance}.log | grep -E 'warning', it's normal when the
output is null, or abnormal
Solution : If encounted,May cause database
services abnormal,According to the error code to lookup
the method in Sybase Troubleshooting.
Autorepair : NA
Area : Database
Message : Sybase messages exist warning
messages.
engineers.
310007-103 1. Alarm item

CheckID : 310007
Status : NA
Desc : 310007-103: Sybase messages is not
exist.
Standard : it’s normal when log exists, or abnormal
Solution : execute 'ls -l
/opt/sybase/ASE-*/install/*.log'. If log file is not exist, May
cause database startup abnormal.If you have any question,
please contact Huawei technical support engineers.
Autorepair : NA
Area : Database
Message : Not found Sybase messages
engineers.
2.3.2 310008_ Check trunc log parameter of sybase database

Item Check trunc log parameter of sybase database
Check ID 310008

U2000
Application SUSE
System

Solution
CheckID : 310008
CheckItem : Check trunc log parameter of
sybase database
Status : WARNING
Desc : 310008-200: The trunc log
parameter of database is not exist.
Standard : If the trunc log parameter of
database is not exist,result is error or warning.
Solution : Please login the database to add
log truncation parameter manually, Take pmdb as an
example.
1> sp_dboption pmdb,"trunc log on chkpt",true
2> go
1> use pmdb
2> go
1> checkpoint
2> go
Autorepair : NA
Area : Database
Message : The trunc log parameter of
database is not exist.
Please return the health check result package and contact

U2000
310008-201 1. Alarm item

CheckID : 310008
CheckItem : Check trunc log parameter of
sybase database
Status : WARNING
Desc : 310008-201: Do not collect the
information of OSS.
Standard : If can not collect the information
of OSS,result is error or warning.
Solution : Please return the health check
result package and contact Huawei technical support
engineers.
Autorepair : NA
Area : Database
Message : Do not collect the information of
OSS.
Please return the health check result package and contact

U2000
2.3.3 310041_ Collect Sybase information

Item Collect Sybase information
Check ID 310041
Application SUSE
System

CheckItem : Collect Sybase information
Status : WARNING
Desc : 310041-200: Collect the sybase
information
Standard : Collect sybase information
failed.
Solution : If the database can not login, it is
may be the user or password is not right, may be tempdb
is full or other issue. If you have any question, please
Autorepair :NA
Area : Database
Message : Collect sybase information
failed.
If the database can not login, it is may be the user or
password is not right, may be tempdb is full or other issue.
If you have any question, please contact Huawei technical
support engineers.

U2000
2.3.4 500019_ Check Sybase Logsegment

Item Check Sybase Logsegment
Check ID 500019
Application SUSE
System

CheckItem : check sybase logsegment
Status : WARNING
Desc : 500019-200: There are one or more
databases log segment using more than 90%.
Standard : Use sp_helpdb command to determine
the usage of log segment, if the usage exceeds 90%, then
alarm.
Solution :Please manually clear the log segment, If
you have any question, please contact Huawei technical
support engineers.
Autorepair : NA
Area : Database
Message : NA
Use sp_helpdb command to determine the usage of log
segment, If the analysis results include this alarm, need to
manually clear the log segment.

U2000
2.4 S2600 Array Verification Items

2.4.1 150046_Check S2600 Array Disk
Item Check S2600 array disk
Check ID 150046
Application SUSE
System

CheckItem : check_2600Array_disk
Status : NA
Desc : 150046-101:Array Type is not
2600.
Standard : Collect disk array information, then
check disk status from showdisk.txt
Solution : NA
Autorepair : NA
Area : Hardware
Message : Array Type is not 2600
Check 2600Array disk,if the analysis results include this
alarm,the array type is not 2600.

U2000
150046-200 1. Alarm item

CheckID : 150046
Status : ERROR
Desc : 150046-200:the 2600 array disk is
not normal.
Solution : the array's disk is abnormal,it may
lead to the U2000 services abnormally.please replace
disk.if having question,please Contact Huawei technical
support engineers.
Autorepair : NA
Area : Hardware
Message : The 2600 array disk is not normal
alarm, the 2600 array disk is not normal.
150046-201 1. Alarm item
CheckID : 150046
Status : WARNING
Desc : 150046-201:Can not find the info
file.
Solution : it has not collected the disk array
information and has the risk of U2000 services
abnormally.if having question,please Contact Huawei
Autorepair : NA
Area : Hardware
Message : Can not find the info file
alarm,the 2600Array disk information is not collected.

U2000
150046-300 1. Alarm item

CheckID : 150046
Status : WARNING
Desc : 150046-300:Check failed.
Solution : the script's checking failed,and has
the risk of U2000 services abnormally.if having
question,please Contact Huawei technical support
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 2600Array disk failed.
Basis None
2.4.2 150047_Check S2600 Array BBU

Item Check S2600 array BBU
Check ID 150047
Application SUSE
System

CheckItem : check_2600Array_BBU
Status : NA
2600.
Standard : Collect disk array information,then
check BBU from showbbu.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600Array BBU,if the analysis results include this

U2000
150047-200 1. Alarm item

CheckID : 150047
Status : ERROR
Desc : 150047-200:the 2600 array BBU is
not normal.
Solution : the array's bbu is abnormal,it may
lead to the U2000 services abnormally.please replace it.if
having question,please Contact Huawei technical support
engineers.
Autorepair : NA
Area : Hardware
Message : The 2600 array BBU is not normal
alarm, the 2600 array BBU is not normal.
150047-201 1. Alarm item
CheckID : 150047
Status : WARNING
file.
Autorepair : NA
Area : Hardware
alarm,the 2600Array BBU information is not collected.

U2000
150047-300 1. Alarm item

CheckID : 150047
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 2600Array BBU failed.
Basis None
2.4.3 150048_Check S2600 Array Controller

Item Check S2600 array controller
Check ID 150048
Application SUSE
System

CheckItem : check_2600Array_controller
Status : NA
2600.
check array controller from showctrlinfo.txt.
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600Array controller,if the analysis results
include this alarm,the array type is not 2600.

U2000
150048-200 1. Alarm item

CheckID : 150048
Status : ERROR
Desc : 150048-200:the 2600 array
controller is not normal.
Solution : the array's controller is abnormal,it
may lead to the U2000 services abnormally.if having
engineers.
Autorepair : NA
Area : Hardware
Message : The 2600 array controller is not
normal
include this alarm, the 2600 array controller is not
normal.
150048-201 1. Alarm item
CheckID : 150048
Status : WARNING
file.
Autorepair : NA
Area : Hardware
include this alarm,the 2600Array controller information
is not collected.

U2000
150048-300 1. Alarm item

CheckID : 150048
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
include this alarm, check 2600Array controller failed.
Basis None
2.4.4 150053_Check S2600 Array Fibre Mode

Item Check S2600 array fibre mode
Check ID 150053
Application SUSE
System

CheckItem : check_2600Array_fibreMode
Status : NA
2600.
check fibre module from showfibremodule.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600Array fibreMode,if the analysis results

U2000
150053-200 1. Alarm item

CheckID : 150053
Status : ERROR
Desc : 150053-200:the 2600 array
fibreMode is not normal.
Solution : the array's fiber mode is abnormal,it
may lead to the U2000 services abnormally.please repair
it.if having question,please Contact Huawei technical
support engineers.
Autorepair : NA
Area : Hardware
Message : The 2600 array fibreMode is not
normal
include this alarm, the 2600 array fibreMode is not
normal.
150053-201 1. Alarm item
CheckID : 150053
Status : WARNING
file.
Autorepair : NA
Area : Hardware
include this alarm,the 2600Array fibreMode information
is not collected.

U2000
150053-300 1. Alarm item

CheckID : 150053
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
include this alarm, check 2600Array fibreMode failed.
Basis None
2.4.5 150056_Check S2600 Array Lun

Item Check S2600 array lun
Check ID 150056
Application SUSE
System

CheckItem : check_2600Array_lun
Status : NA
2600.
check LUN status from showlun.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600Array lun,if the analysis results include this

U2000
150056-200 1. Alarm item

CheckID : 150056
Status : ERROR
Desc : 150056-200:the 2600 array lun is
not normal.
Solution : the array's lun is abnormal,it may
lead to the U2000 services abnormally.if having
engineers.
Autorepair : NA
Area : Hardware
Message : The 2600 array lun is not normal
alarm, the 2600 array lun is not normal.
150056-201 1. Alarm item
CheckID : 150056
Status : WARNING
file.
Autorepair : NA
Area : Hardware
alarm,the 2600Array lun information is not collected .

U2000
150056-300 1. Alarm item

CheckID : 150056
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 2600Array lun failed.
Basis None
2.4.6 150057_Check S2600 Array Physical Disk

Item Check S2600 array physical disk
Check ID 150057
Application SUSE
System

CheckItem : check_2600Array_PhyDisk
Status : NA
2600.
check disk status of array from showdisk-p.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600Array PhyDisk,if the analysis results include
this alarm,the array type is not 2600.

U2000
150057-200 1. Alarm item

CheckID : 150057
Status : ERROR
Desc : 150057-200:the 2600 array PhyDisk
is not normal.
engineers.
Autorepair : NA
Area : Hardware
Message : The 2600 array PhyDisk is not
normal
this alarm, the 2600 array PhyDisk is not normal.
150057-201 1. Alarm item
CheckID : 150057
Status : WARNING
file.
Autorepair : NA
Area : Hardware
this alarm,the 2600Array PhyDisk information is not
collected .

U2000
150057-300 1. Alarm item

CheckID : 150057
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 2600Array PhyDisk failed.
Basis None
2.4.7 150101_Check S2600 Cache Write Strategy or Policy

Item Check S2600 Cache Write Strategy or Policy
Check ID 150101
Application SUSE
System

U2000

CheckItem : Cache Write Strategy or Policy
Status : NA
2600.
Standard : 1 If the values of "Whether Private
LUN" is "Yes" in the info file showlun-i.txt, it's private
LUN, do not need to check it. Otherwise, Check the
LUN as the following criterion:(1) If the values of
"Cache Write Strategy" and "Running Cache Write
Strategy" are the same(or "Cache Write Policy" and
"Running Cache Write Policy" are the same), the check
passed. (2) If the value of "Cache Write Strategy"(or
"Cache Write Policy") is "Write back mandatory;
Mirroring" and the value of "Running Cache Write
Strategy"(or "Running Cache Write Policy") is "Write
back; Mirroring", the check passed. (3) If the value of
"Cache Write Strategy"("Cache Write Policy") is "Write
back mandatory; No mirroring" and the value of
"Running Cache Write Strategy"(or "Running Cache
Write Policy") is "Write back; No mirroring", the check
passed. (4) In other cases, the check failed.
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600 array Cache Write Strategy or Policy,if the
analysis results include this alarm,the array type is not
2600.

U2000
150101-200 1. Alarm item

CheckID : 150101
Status : ERROR
Desc : 150101-200:the 2600 array power is
not normal.
Solution : Please return the health check result
package and contact the headquarters Huawei technical
support engineer.
Autorepair : NA
Area : Hardware
analysis results include this alarm, the 2600 array Cache
Write Strategy or Policy is not normal.

U2000
150101-201 1. Alarm item

CheckID : 150101
Status : WARNING
file.
Autorepair : NA
Area : Hardware
analysis results include this alarm,the 2600Array Cache
Write Strategy or Policy is not collected .

U2000
150101-300 1. Alarm item

CheckID : 150101
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
Check 2600 Array Cache Write Strategy or Policy,if the
analysis results include this alarm, check 2600 Array
Cache Write Strategy or Policy failed.
Basis None
2.4.8 150106_Check S2600 Fan Status

Item Check S2600 Fan Status
Check ID 150106
Application SUSE
System

U2000

CheckItem : Fan Status
Status : NA
2600.
Standard : If "Status" of fan in the online
enclosures in the output of command "showfan -s
Subrack ID" is "Normal", each online enclosure has two
fan, the check passed. In other cases, the check failed.
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600 Fan Status,if the analysis results include this
150106-200 1. Alarm item
CheckID : 150106
Status : ERROR
Desc : 150106-200:the 2600 Fan Status is
not normal.
Solution : Please replace the abnormal FAN.
Solution Effect:The operation will not affect the U2000
services.
Autorepair : NA
Area : Hardware
alarm, the 2600 Fan Status is not normal.

U2000
150106-201 1. Alarm item

CheckID : 150106
Status : WARNING
file.
Autorepair : NA
Area : Hardware
alarm,the 2600 Fan Status information is not collected .
150106-300 1. Alarm item
CheckID : 150106
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 2600 Fan Status failed.
Basis None
2.4.9 150107_Check S2600 FC Link Rate

Item Check S2600 FC Link Rate

U2000
Check ID 150107
Application SUSE
System

CheckItem : FC Link Rate
Status : NA
2600.
Standard : If all value of "Speed" and "Cfg
Speed" is "2G" in the output of command "showfps", the
check result is optimization recommended. In other
cases, the check passed
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600 FC Link Rate,if the analysis results include
150107-200 1. Alarm item
CheckID : 150107
Status : ERROR
Desc : 150107-200:the 2600 FC Link Rate
is not normal.
package and contact Huawei technical support engineers.
Autorepair : NA
Area : Hardware
this alarm, the 2600 FC Link Rate is not normal.

U2000
150107-201 1. Alarm item

CheckID : 150107
Status : WARNING
file.
Autorepair : NA
Area : Hardware
this alarm,the 2600 FC Link Rate information is not
collected .
150107-300 1. Alarm item
CheckID : 150107
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 2600 FC Link Rate failed.
Basis None
2.4.10 150108_Check S2600 Hot Spare Disk

Item Check S2600 Hot Spare Disk

U2000
Check ID 150108
Application SUSE
System

CheckItem : Hot Spare Disk
Status : NA
2600.
Standard : If any RAID group (except RAID
0) does not have required hot spare disks (whose physical
states are normal, physical types are the same, and
logical capacity of each is or larger than the smallest disk
in the RAID group), the check failed. Otherwise, the
check passed.
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600 Hot Spare Disk,if the analysis results include
150108-200 1. Alarm item
CheckID : 150108
Status : ERROR
Desc : 150108-200:the 2600 Hot Spare
Disk is not normal.
check passed.
Solution : Please replace the abnormal hot
spare disks.
Solution Effect :The operation will not affect the
U2000 services.
Autorepair : NA
Area : Hardware
this alarm, the 2600 Hot Spare Disk is not normal.

U2000
150108-201 1. Alarm item

CheckID : 150108
Status : WARNING
file.
check passed.
Autorepair : NA
Area : Hardware
this alarm,the 2600 Hot Spare Disk information is not
collected .
150108-300 1. Alarm item
CheckID : 150108
Status : WARNING
check passed.
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 2600 Hot Spare Disk failed.
Basis None

U2000
Basis None
2.4.11 150110_Check S2600 LUN Write Back Without Mirroring

Item Check S2600 LUN Write Back Without Mirroring
Check ID 150110
Application SUSE
System

CheckItem : LUN Write Back Without Mirroring
Status : NA
2600.
LUN" is "Yes" in the output of command "showlun -i
lunID", it's private LUN, do not need to check it. 2 If the
LUN is not private LUN, the value of "Running Cache
Write Strategy" in the output of command "showlun -i
lunID" does not contain "Write back; No mirroring" (or
the value of "Running Cache Policy" does not contain
"Write back; No mirroring"), the check passed.
Otherwise, the check failed.
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600 LUN Write Back Without Mirroring,if the
analysis results include this alarm,the array type is not
2600.

U2000
150110-200 1. Alarm item

CheckID : 150110
Status : ERROR
Desc : 150110-200:the 2600 LUN Write
Back Without Mirroring is not normal.
Solution : Please reffer to the following link to
change the LUN write policy to write back with
mirroring.
http://support.huawei.com/ehedex/hdx.do?docid=DOC10
00005746&id=t_r5_ft_guide_0023
Solution Effect :The operation will not affect the
U2000 services.
Autorepair : NA
Area : Hardware
analysis results include this alarm, the 2600 LUN Write
Back Without Mirroring is not normal.

U2000
150110-201 1. Alarm item

CheckID : 150110
Status : WARNING
file.
Autorepair : NA
Area : Hardware
analysis results include this alarm,the 2600 LUN Write
Back Without Mirroring information is not collected .

U2000
150110-300 1. Alarm item

CheckID : 150110
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
analysis results include this alarm, check 2600 LUN
Write Back Without Mirroring failed.
Basis None
2.4.12 150112_Check S2600 Power Supply Status

Item Check S2600 Power Supply Status
Check ID 150112
Application SUSE
System

U2000

CheckItem : Power Supply Status
Status : NA
2600.
Standard : If "Status" of power supplies in the
online enclosures in the output of command
"showpowerinfo" is normal, each online enclosure has
two power supplies, the check passed. In other cases, the
check failed.
Solution : NA
Autorepair : NA
Area : Hardware
Check 2600 Power Supply Status,if the analysis results
150112-200 1. Alarm item
CheckID : 150112
Status : ERROR
Desc : 150112-200:the 2600 Power Supply
Status is not normal.
check failed.
Solution : Please replace the abnormal power
supply.
Solution Effect:The operation will not affect the U2000
services.
Autorepair : NA
Area : Hardware
include this alarm, the 2600 Power Supply Status is not
normal.

U2000
150112-201 1. Alarm item

CheckID : 150112
Status : WARNING
file.
check failed.
Autorepair : NA
Area : Hardware
include this alarm,the 2600 Power Supply Status
information is not collected .
150112-300 1. Alarm item
CheckID : 150112
Status : WARNING
check failed.
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
include this alarm, check 2600 Power Supply Status
failed.
Basis None

U2000
2.5 S3100/S3200 Array Verification Items

2.5.1 150061_Check S3100/S3200 Array Disk
Item Check S3100/S3200 array disk
Check ID 150061
Application SUSE
System

CheckItem : check_3x00Array_disk
Status : NA
3x00.
check disk array status from show_storageArray.txt.
Solution : NA
Autorepair : NA
Area : Hardware
Message : Array Type is not 3x00
Check 3x00Array disk,if the analysis results include this
alarm,the array type is not 3x00.
150061-200 1. Alarm item
CheckID : 150061
Status : ERROR
Desc : 150061-200:the 3x00 array disk is
not normal.
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array disk is not normal
alarm, the 3x00 array disk is not normal.

U2000
150061-201 1. Alarm item

CheckID : 150061
Status : WARNING
file.
Autorepair : NA
Area : Hardware
alarm,the 3x00Array disk information is not collected .
150061-300 1. Alarm item
CheckID : 150061
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, Check 3x00Array disk failed.
Basis None
2.5.2 150064_Check S3100/S3200 Array Volume Group

Item Check S3100/S3200 array volume group
Check ID 150064
Application SUSE
System

U2000

CheckItem : check_3x00Array_VolumeGroup
Status : NA
Desc : 150064-101:Array Type is not 3x00.
Standard : Collect disk array info,then check
volume group from show_storageArray.txt file.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3x00Array volumegroup,if the analysis results
include this alarm,the array type is not 3x00.
150064-200 1. Alarm item
CheckID : 150064
Status : ERROR
Desc : 150064-200:the 3x00 array
VolumeGroup is not normal.
Solution : the array's ossdg-group is
abnormal,it may lead to the U2000 services abnormally.if
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array VolumeGroup is not
normal
include this alarm, the 3x00 array VolumeGroup is not
normal.

U2000
150064-201 1. Alarm item

CheckID : 150064
Status : WARNING
Desc : 150064-201:Can not find the info file.
Autorepair : NA
Area : Hardware
include this alarm,the 3x00Array volumegroup information
is not collected .
150064-300 1. Alarm item
CheckID : 150064
Status : WARNING
Solution : the script's checking failed,and has the
risk of U2000 services abnormally.if having
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
include this alarm, check 3x00Array volumegroup failed.
Basis None
2.5.3 150066_Check S3100/S3200 Array Volume

Item Check S3100/S3200 array volume
Check ID 150066
Application SUSE
System

U2000

CheckItem : check_3x00Array_Volume
Status : NA
volume from show_storageArray.txt file.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3x00Array volume,if the analysis results include
this alarm,the array type is not 3x00.
150066-200 1. Alarm item
CheckID : 150066
Status : ERROR
Desc : 150066-200:the 3x00 array volume
is not normal.
Solution : the disk array's volume is abnormal,it
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array volume is not normal
this alarm, the 3x00 array volume is not normal.

U2000
150066-201 1. Alarm item

CheckID : 150066
Status : WARNING
file.
Autorepair : NA
Area : Hardware
this alarm,the 3x00Array volume is not collected .
150066-300 1. Alarm item
CheckID : 150066
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3x00Array volume failed.
Basis None
2.5.4 150067_Check S3100/S3200 Array Controller

Item Check S3100/S3200 array controller
Check ID 150067
Application SUSE
System

U2000

CheckItem : check_3x00Array_controller
Status : NA
check controller status from show_storageArray.txt.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3x00Array controller,if the analysis results include
150067-200 1. Alarm item
CheckID : 150067
Status : ERROR
controller is not normal.
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array controller is not
normal
this alarm, the 3x00 array controller is not normal.

U2000
150067-201 1. Alarm item

CheckID : 150067
Status : WARNING
file.
Autorepair : NA
Area : Hardware
this alarm,the 3x00Array controller information is not
collected .
150067-300 1. Alarm item
CheckID : 150067
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3x00Array controller failed.
Basis None
2.5.5 150069_Check S3100/S3200 Array Power-fan

Item Check S3100/S3200 array power-fan
Check ID 150069

U2000
Application SUSE
System

CheckItem : check_3x00Array_Power-fan
Status : NA
Standard : Collect disk array information,
then check power-fan from show_storageArray.txt files.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3x00Array power-fan,if the analysis results
include this alarm,the array type is not 3x00.
150069-200 1. Alarm item
CheckID : 150069
Status : ERROR
Power-fan is not normal.
Solution : the array's power's fan is abnormal,it
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array Power-fan is not
normal
include this alarm, the 3x00 array Power-fan is not
normal.

U2000
150069-201 1. Alarm item

CheckID : 150069
Status : WARNING
file.
Autorepair : NA
Area : Hardware
include this alarm,the 3x00Array power-fan information
is not collected .
150069-300 1. Alarm item
CheckID : 150069
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
include this alarm, check 3x00Array power-fan failed.
Basis None

U2000
2.5.6 150070_Check S3100/S3200 Array Power

Item Check S3100/S3200 array power
Check ID 150070
Application SUSE
System

CheckItem : check_3x00Array_Power
Status : NA
check power status from show_storageArray.txt file.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3x00Array power,if the analysis results include
150070-200 1. Alarm item
CheckID : 150070
Status : ERROR
Desc : 150070-200:the 3x00 array Power is
not normal.
Solution : the array's power is abnormal,it may
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array Power is not normal
this alarm, the 3x00 array Power is not normal.

U2000
150070-201 1. Alarm item

CheckID : 150070
Status : WARNING
file.
Autorepair : NA
Area : Hardware
this alarm,the 3x00Array power information is not
collected .
150070-300 1. Alarm item
CheckID : 150070
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3x00Array power failed.
Basis None

U2000
2.5.7 150071_Check S3100/S3200 Array Fan

Item Check S3100/S3200 array fan
Check ID 150071
Application SUSE
System

CheckItem : check_3x00Array_fan
Status : NA
check fan status from show_storageArray.txt file.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3x00Array fan,if the analysis results include this
alarm,the array type is not 3x00.
150071-200 1. Alarm item
CheckID : 150071
Status : ERROR
Desc : 150071-200:the 3x00 array fan is not
normal.
lead to the U2000 services abnormally.please replace it.if
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array fan is not normal
alarm, the 3x00 array fan is not normal.

U2000
150071-201 1. Alarm item

CheckID : 150071
Status : WARNING
file.
Autorepair : NA
Area : Hardware
alarm,the 3x00Array fan information is not collected .
150071-300 1. Alarm item
CheckID : 150071
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 3x00Array fan failed.
Basis None
2.6 S3900 Array Verification Items

2.6.1 150074_Check S3900 array controller
Item Check S3900 array controller

U2000
Check ID 150074
Application SUSE
System

Status : NA
Desc : 150074-101:Array Type is not 3900.
Standard :Collect disk array information,then
check controller status from showctrl.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900Array controller,if the analysis results include
150074-200 1. Alarm item
CheckID : 150074
Status : ERROR
Desc : 150074-200:the 3900 array controller
is not normal.
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array controller is not
normal
this alarm, the 3x00 array controller is not normal.

U2000
150074-201 1. Alarm item

CheckID : 150074
Status : WARNING
Autorepair : NA
Area : Hardware
this alarm,the 3900Array controller information is not
collected .
150074-300 1. Alarm item
CheckID : 150074
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3900Array controller failed.
Basis None
2.6.2 150075_Check S3900 Array BBU

Item Check S3900 array BBU
Check ID 150075
Application SUSE
System

U2000

Status : NA
check BBU status from showbbu.txt
Solution : NA
Autorepair : NA
Area : Hardware
150075-200 1. Alarm item
CheckID : 150075
Status : ERROR
Desc : 150075-200:the 3900 array BBU is
not normal.
Solution : the array's bbu is abnormal,it may lead
to the U2000 services abnormally.please replace it.if
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array BBU is not normal
alarm, the 3x00 array BBU is not normal.

U2000
150075-201 1. Alarm item

CheckID : 150075
Status : WARNING
Autorepair : NA
Area : Hardware
alarm,the 3900Array BBU information is not collected .
150075-300 1. Alarm item
CheckID : 150075
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware:
Message : Failed!
alarm, check 3900Array BBU failed.
Basis None
2.6.3 150076_Check S3900 Array Disk

Item Check S3900 array disk
Check ID 150076
Application SUSE
System

U2000

Status : NA
Standard :Collect disk information,then check
disk status from showdisk.txt
Solution : NA
Autorepair : NA
Area : Hardware
150076-200 1. Alarm item
CheckID : 150076
Status : ERROR
Desc : 150076-200:the 3900 array disk is not
normal.
lead to the U2000 services abnormally.please replace
disk.if having question,please Contact Huawei technical
support engineers.
Solution : Collect the infomation of array and
check it
Autorepair : NA
Area : Hardware
Message : The 3x00 array disk is not normal
alarm, the 3x00 array disk is not normal.

U2000
150076-201 1. Alarm item

CheckID : 150076
Status : WARNING
information and has the risk of U2000 services abnormally.
Autorepair : NA
Area : Hardware
alarm,the 3900Array disk information is not collected .
150076-300 1. Alarm item
CheckID : 150076
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 3900Array disk failed.
Basis None
2.6.4 150077_Check S3900 Array Fan

Item Check S3900 array fan
Check ID 150077
Application SUSE
System

U2000

CheckItem : check_3900Array_Fan
Status : NA
Standard :Collect disk array information, then
check fun status from showfan.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900Array fan,if the analysis results include this
150077-200 1. Alarm item
CheckID : 150077
Status : ERROR
Desc : 150077-200:the 3900 array Fan is
not normal.
Solution : the array's fan is abnormal,it may
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array Fan is not normal
alarm, the 3x00 array Fan is not normal.

U2000
150077-201 1. Alarm item

CheckID : 150077
Status : WARNING
file.
Autorepair : NA
Area : Hardware
alarm,the 3900Array fan information is not collected .
150077-300 1. Alarm item
CheckID : 150077
Status : WARNING
the risk of U2000 services abnormally.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 3900Array fan failed.
Basis None
2.6.5 150078_Check S3900 Array Lun

Item Check S3900 array lun
Check ID 150078
Application SUSE
System

U2000

Status : NA
Solution : NA
Autorepair : NA
Area : Hardware
150078-200 1. Alarm item
CheckID : 150078
Status : ERROR
Desc : 150078-200:the 3900 array lun is not
normal.
Solution : the array's lun is abnormal,it may lead
to the U2000 services abnormally.
Autorepair : NA
Area : Hardware
Message : The 3x00 array lun is not normal
alarm, the 3x00 array lun is not normal.

U2000
150078-201 1. Alarm item

CheckID : 150078
Status : WARNING
information and has the risk of U2000 services abnormally.
Autorepair : NA
Area : Hardware
alarm,the 3900Array lun information is not collected .
150078-300 1. Alarm item
CheckID : 150078
Status : WARNING
risk of U2000 services abnormally.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 3900Array lun failed.
Basis None
2.6.6 150079_Check S3900 Array Power

Item Check S3900 Array Power
Check ID 150079
Application SUSE
System

U2000

CheckItem : check_3900Array_power
Status : NA
check power status from showpower.txt
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900Array power,if the analysis results include this
150079-200 1. Alarm item
CheckID : 150079
Status : ERROR
Desc : 150079-200:the 3900 array power is
not normal.
engineers.
Autorepair : NA
Area : Hardware
Message : The 3x00 array power is not normal
alarm, the 3x00 array power is not normal.

U2000
150079-201 1. Alarm item

CheckID : 150079
Status : WARNING
Autorepair : NA
Area : Hardware
alarm,the 3900Array power information is not collected .
150079-300 1. Alarm item
CheckID : 150079
Status : WARNING
risk of U2000 services abnormally. if having
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
alarm, check 3900Array power failed.
Basis None

U2000
2.6.7 500010_check 3900Array Single Path

Item check 3900Array Single Path
Check ID 500010
Application SUSE
System

CheckItem : check 3900Array Single Path
Status : NA
Standard : There is no "Single path" disk in the
3900 array normally.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900Array Single Path,if the analysis results include
500010-200 1. Alarm item
CheckID : 500010
Status : ERROR
Desc : 500010-200: The status of disks in the
3900 array contains "Single path".
Solution : the disk array contain single path,it
may lead to the U2000 services abnormally.please repair
it.if having question,please Contact Huawei technical
support engineers.
Autorepair : NA
Area : Hardware
Message : The status of disks in the 3900 array
contains "Single path".
this alarm, The status of disks in the 3900 array contains
"Single path".

U2000
500010-201 1. Alarm item

CheckID : 500010
Status : WARNING
Autorepair : NA
Area : Hardware
this alarm,the 3900Array disk information is not collected .
500010-300 1. Alarm item
CheckID : 500010
Status : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3900Array Single Path failed.
Basis None
2.6.8 150203_Check S3900 FC Link Rate

Check ID 150203
Application SUSE
System

U2000

Status : NA
3900.
Standard : If Configured Speed and Current
Speed are "AUTO", "1G", "2G", "4G", "8G" or "--" in
the output of command "showfcspeed", the rate is
normal.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900FC Link Rate,if the analysis results include
150203-200 1. Alarm item
CheckID : 150203
Status : ERROR
Desc : 150203-200:the 2600 FC Link Rate
is not normal.
normal.
Autorepair : NA
Area : Hardware
this alarm, the 3900FC Link Rate is not normal.

U2000
150203-201 1. Alarm item

CheckID : 150203
Status : WARNING
file.
normal.
Autorepair : NA
Area : Hardware
this alarm,the 3900 FC Link Rate information is not
collected .
150203-300 1. Alarm item
CheckID : 150203
Status : WARNING
normal.
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3900 FC Link Rate failed.
Basis None
2.6.9 150204_Check S3900 Optical Transceiver Status


U2000
Check ID 150204
Application SUSE
System

CheckItem : Optical Transceiver Status
Status : NA
3900.
Standard : In the output of command
"showfibremodule", the Status: "Normal" indicates that
the optical transceiver is in a normal state.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900 Optical Transceiver Status,if the analysis
results include this alarm,the array type is not 3900.
150204-200 1. Alarm item
CheckID : 150204
Status : ERROR
Desc : 150204-200:the 2600 Optical
Transceiver Status is not normal.
the optical transceiver is in a normal
state.Solution : Please return the health check
engineers.
Autorepair : NA
Area : Hardware
results include this alarm, the 3900 Optical Transceiver
Status is abnormal.

U2000
150204-201 1. Alarm item

CheckID : 150204
Status : WARNING
file.
Autorepair : NA
Area : Hardware
results include this alarm,the 3900 Optical Transceiver
Status information is not collected .
150204-300 1. Alarm item
CheckID : 150204
CheckItem : Optical Transceiver
StatusStatus : WARNING
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
results include this alarm, check 3900 Optical
Transceiver Status failed.
Basis None
2.6.10 150206_Check S3900 RAID Group Status


U2000
Check ID 150206
Application SUSE
System

CheckItem : RAID Group Status
Status : NA
3900.
"showrg", the Status: "Normal" indicates that the RAID
group is in a normal state.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900 RAID Group Status ,if the analysis results
150206-200 1. Alarm item
CheckID : 150206
Status : ERROR
Desc : 150206-200:the 2600 RAID Group
Status is not normal.
engineers.
Autorepair : NA
Area : Hardware
Check 3900 RAID Group Status,if the analysis results
include this alarm, the 3900 RAID Group Status is
abnormal.

U2000
150206-201 1. Alarm item

CheckID : 150206
Status : WARNING
file.
Autorepair : NA
Area : Hardware
include this alarm,the 3900 RAID Group Status
information is not collected .
150206-300 1. Alarm item
CheckID : 150206
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
include this alarm, check 3900 RAID Group Status
failed.
Basis None
2.6.11 150207_Check S3900 System Status


U2000
Check ID 150207
Application SUSE
System

CheckItem : System Status
Status : NA
3900.
Standard : n the output of command
"showsys", the Current System Mode: "Double
Controllers Normal" or "Single Controller Normal"
indicates that the system runs properly. If Current System
Mode is abnormal, the check will not pass.
Solution : NA
Autorepair : NA
Area : Hardware
Check 3900System Status ,if the analysis results include
150207-200 1. Alarm item
CheckID : 150207
Status : ERROR
Desc : 150207-200:the 2600 System Status
is not normal.
engineers.
Autorepair : NA
Area : Hardware
Check 3900 System Status,if the analysis results include
this alarm, the 3900 System Status is abnormal.

U2000
150207-201 1. Alarm item

CheckID : 150207
Status : WARNING
file.
Autorepair : NA
Area : Hardware
this alarm,the 3900 System Status information is not
collected .
150207-300 1. Alarm item
CheckID : 150207
engineers.
Autorepair : NA
Area : Hardware
Message : Failed!
this alarm, check 3900 System Status failed.
Basis None

U2000
OSMU Health Check Verification Items 3 Service Module Verification Items
3 Service Module Verification Items
3.1 Common Module

3.1.1 450001_Verifying that the OSS FTP Folder Link is Normal
Item Verifying That The Oss Ftp Folder Link Is Normal
Check ID 450001
Application SUSE
System

CheckItem : Check Ftp Link Action
Status : OK
Level :bussiness
Action Description: 450001-100: OSS FTP folder link is
normal
Standard : Check whether the ftp folder link under
/export/home/sysm/export/home/sysm/ is exist
Solution : NA
Autorepair : NA
Action Message : OSS FTP folder link is normal
NA

U2000
450001-110 1. Alarm item

CheckID : 450001
Status : ERROR
Level :bussiness
Action Description: 450001-110: Both nbi ftp folder link
and ne ftp folder lost.
Solution :
Login OSS server using root then execute following
command to rebuild ftp link:
# kill -9 `ps -ef | grep \/usr\/sbin\/ftpd | grep -v grep | awk
'{ print $2 }'`/;
# rm -rf /export/home/sysm/export/home/sysm/ftproot /;
# mkdir -p /export/home/sysm/export/home/sysm /;
# chmod -R 750 /export/home/sysm/export /;
# chown -R ftpuser:ossgroup /export/home/sysm/export /;
# cd /export/home/sysm/export/home/sysm /;
# ln -sf ../../../ftproot ftproot /;
/export/home/sysm/export/home/sysm/ftproot /;
# rm -rf /export/home/sysm/export/home/omc/var /;
# mkdir -p /export/home/sysm/export/home/omc/var /;
# chmod -R 750 /export/home/sysm/export/home/omc /;
# chown -R ftpuser:ossgroup
/export/home/sysm/export/home/omc /;
# cd /export/home/sysm/export/home/omc/var /;
# ln -sf ../../../../opt/oss/server/var/itf_n itf_n /;
# chown -h ossuser:ossgroup itf_n /;
# ln -sf ../../../../opt/oss/server/var/fileint fileint /;
# chown -h ossuser:ossgroup fileint
Autorepair : NA
Action Message : Both nbi ftp folder link and ne ftp
folder lost
Verifying that the oss ftp folder link is normal. If there are
incorrect configuration items, the he ftp folder link is lost.
If the solution coul not resolve this problem, contact

U2000
450001-120 1. Alarm item

CheckID : 450001
Status : OK
Level :bussiness
Action Description: 450004-120: NBI ftp folder link lost.
Solution :
# rm -rf /export/home/sysm/export/home/omc/var /;
# mkdir -p /export/home/sysm/export/home/omc/var /;
# chmod -R 750 /export/home/sysm/export/home/omc /;
# chown -R ftpuser:ossgroup
/export/home/sysm/export/home/omc /;
# cd /export/home/sysm/export/home/omc/var /;
# ln -sf ../../../../opt/oss/server/var/itf_n itf_n /;
# chown -h ossuser:ossgroup itf_n /;
# ln -sf ../../../../opt/oss/server/var/fileint fileint /;
# chown -h ossuser:ossgroup fileint
Autorepair : NA
Action Message : NBI ftp folder link lost.
Check whether the ftp folder link under
/export/home/sysm/export/home/omc/var is exist. If it is not
exist, rebuild it.

U2000
450001-130 1. Alarm item

CheckID : 450001
Status : ERROR
Level :bussiness
Action Description: 450004-130: NE ftp folder link lost.
Solution :
# kill -9 `ps -ef | grep \/usr\/sbin\/ftpd | grep -v grep | awk
'{ print $2 }'`/;
# rm -rf /export/home/sysm/export/home/sysm/ftproot /;
# mkdir -p /export/home/sysm/export/home/sysm /;
# chmod -R 750 /export/home/sysm/export /;
# chown -R ftpuser:ossgroup /export/home/sysm/export /;
# cd /export/home/sysm/export/home/sysm /;
# ln -sf ../../../ftproot ftproot /;
/export/home/sysm/export/home/sysm/ftproot
Autorepair : NA
Action Message : NE ftp folder link lost.
Check whether the ftp folder link under
/export/home/sysm/export/home/sysm/ftproot is exist. If it
is not exist, rebuild it.
3.1.2 450002_Verifying that the Cert of Ftpserver is Normal

Item Verifying that the cert of ftpserver is normal
Check ID 450002
Application SUSE
System

U2000

CheckItem : Check Ftp Cert Action
Status : OK
Level :bussiness
Action Description: 450002-100: OSS FTP certificate is
normal
Standard : Check whether the Cert of ftpserver is
normal
Solution : NA
Autorepair : NA
Action Message : OSS FTP certificate is normal
NA
450002-110 1. Alarm item
CheckID : 450002
CheckItem : Check Ftp Cert Action
Status : WARNING
Level :bussiness
Action Description: 450002-110: OSS FTP certificate is
abnormal
Standard : Check whether the Cert of ftpserver is
normal
Solution : Please download Toolkit from the same
package of SA and install MicroFtpSys
Autorepair : NA
Action Message : OSS FTP certificate is abnormal
Verifying that the cert of ftpserver is normal. If there are
incorrect configuration items, the cert of ftpserver is
abnormal. If the solution coul not resolve this problem,
3.1.3 450003_Verifying that the Password of is Abnormal

Item Verifying that the password of is abnormal
Check ID 450003
Application SUSE
System

U2000

CheckItem : Check Ftpuser Passwd Status
Status : OK
Level :bussiness
Action Description: 450003-100: The passwd of ftpuser is
normal
Standard : Check whether the ftpuser password is
abnormal
Solution : NA
Autorepair : NA
Action Message : The passwd of ftpuser is normal
NA
450003-110 1. Alarm item
CheckID : 450003
Status : ERROR
Level :bussiness
Action Description: 450003-110: The passwd of ftpuser has
been locked
Standard : Check whether the ftpuser password
is abnormal
Solution : Please login OSS master/slaver with
root and execute following command to unlock ftpuser:
1) chage -M -1 -E -1 ftpuser
2) passwd -u ftpuser
Autorepair : NA
Action Message : The passwd of ftpuser has been locked
Verifying that the password of is abnormal. If there are
incorrect configuration items, The passwd of ftpuser has
been locked. If the solution coul not resolve this problem,

U2000
450003-120 1. Alarm item

CheckID : 450003
Status : ERROR
Level :bussiness
Action Description: 450004-120: The passwd of ftpuser has
been locked
Standard : Check whether the ftpuser password
is abnormal
Solution : Please login OSS master/slaver with
root and execute following command to unlock ftpuser:
1) usermod -e 01/01/30 ftpuser
2) passwd -x -1 ftpuser
3) passwd -u ftpuser
Autorepair : NA
Action Message : The passwd of ftpuser has been locked
Verifying that the password of is abnormal. If there are
incorrect configuration items, The passwd of ftpuser has
been locked. If the solution coul not resolve this problem,
3.1.4 450004_Verifying that the FTP Common Path Stat is Correct

Item Verifying that the ftp common path stat is correct
Check ID 450004
Application SUSE
System

U2000

CheckItem : Check Ftp Common Path Status
Status : OK
Level :bussiness
Action Description: 450004-100: FTP Common path stat is
correct
Standard : Check whether the ftp Common path
stat is correct
Solution : NA
Autorepair : NA
Action Message : FTP Common path stat is correct
NA
450004-110 1. Alarm item
CheckID : 450004
CheckItem : Check Ftp Common Path Status
Status : WARNING
Level :bussiness
Action Description: 450004-110: FTP Common path stat is
not correct
Standard : Check whether the ftp Common path
stat is correct
Solution : Please download report decompressing
it and execute command in trace/checkftpcommonpath.txt
which existed in the server's IP path.
Autorepair : NA
Action Message : FTP Common path stat is not correct
Verifying that the ftp common path stat is correct. If there
are incorrect configuration items, FTP Common path stat is
not correct. Please download report decompressing it and
execute command in result/trace/checkftpcommonpath.txt
which existed in the server's IP path. Or contact Huawei
3.1.5 450005_Verifying that the 3rdServer with NAT in Use

Item Verifying that the 3rdserver with nat in use
Check ID 450005
Application SUSE
System

U2000

CheckItem : Check Ftp 3rdserver NAT Status
Status : OK
Level :bussiness
Action Description: 450005-100: FTP 3rd file server is
normal
Standard : Check whether the 3rdserver with nat
in use
Solution : NA
Autorepair : NA
Action Message : FTP 3rd file server is normal
NA
450005-110 1. Alarm item
CheckID : 450005
CheckItem : Check Ftp 3rdserver NAT Status
Status : WARNING
Level :bussiness
Action Description: 450005-110: FTP 3rd file server is
abnormal
Standard : Check whether the 3rdserver with nat
in use
Solution :
Please check the ne in tbl_Transfer, login OSS client,
SoftWare->file server setting; chang the ne' file server to
be OSS：X.X.X.X.
Autorepair : NA
Action Message : FTP 3rd file server is abnormal
Verifying that the 3rdserver with nat in use. If the analysis
results include this alarm, the FTP 3rd file server is
abnormal. Contact Huawei technical support engineers.
3.1.6 450006_Verifying that the OSS Ftp Server Running Normal

Item Verifying that the oss ftp server running normal
Check ID 450006
Application SUSE
System

U2000

CheckItem : Check Ftp Server Status
Status : OK
Level :bussiness
Action Description: 450006-100: FTP Server is running
normal
Standard : Check whether the OSS ftp server
running normal
Solution : NA
Autorepair : NA
Action Message : FTP Server is running normal
NA
450006-110 1. Alarm item
CheckID : 450006
Status : ERROR
Level :bussiness
Action Description: 450006-110: FTP server monitor is
broken
Standard : Check whether the OSS ftp server
running normal
Solution : Please execute command following to
reinstall ftp server:
1) bash /opt/oss_sudobin/imap/ftp/files/config_ftp_ip.sh "
default"
2) bash /opt/oss_sudobin/imap/ftp/files/start_ftp_server.sh
then check OSS function, if any problem please contact
OSS R&D
Autorepair : NA
Action Message : FTP server monitor is broken
Verifying that the oss ftp server running normal. If the
analysis results include this alarm, FTP server monitor is
broken. Contact Huawei technical support engineers.
450006-120 1. Alarm item
CheckID : 450006
Status : ERROR
Level :bussiness
Action Description: 450006-120: FTP server is not running
Standard : Check whether the configuration item
of rsa_cert_file in /etc/vsftpd.conf is normal.
Solution : Please check and repair other ftp check

U2000
item, then if still problem please contact OSS R&D

Autorepair : NA
Action Message : FTP server is not running
Verifying that the oss ftp server running normal. If the
analysis results include this alarm, FTP server is not
running. Contact Huawei technical support engineers.
3.1.7 450007_Verifying that the Ftp Configure is Normal

Item Verifying that the ftp configure is normal
Check ID 450007
Application SUSE
System

CheckItem : Check Ftp Conf Action
Status : OK
Level :bussiness
Action Description: 450007-100: FTP configure is normal
Standard : Check whether the ftp configure is
normal
Solution : NA
Autorepair : NA
Action Message : FTP configure is normal
NA
450007-110 1. Alarm item
CheckID : 450007
Status : ERROR
Level :bussiness
Action Description: 450007-110: FTP configure is
abnormal
normal
Solution : Please login master/slaver using root
then execute following command:
1) cp /etc/vsftpd.conf /etc/vsftpd.conf.quickrecoverybak
2) cp /opt/oss/server/3rdTools/ftp/files/vsftpd.conf
/etc/vsftpd.conf

U2000
default"
Autorepair : NA
Action Message : FTP configure is abnormal
FTP configure is abnormal will lead the service of FTP
works abnormally, please refer to the solution to resolve
this problem
450007-120 1. Alarm item
CheckID : 450007
Status : ERROR
Level :bussiness
Action Description: 450007-120: FTP configure is not exist
normal
Solution : Please login master/slaver using root
then execute following command:
1) cp /etc/vsftpd.conf /etc/vsftpd.conf.quickrecoverybak
2) cp /opt/oss/server/3rdTools/ftp/files/vsftpd.conf
/etc/vsftpd.conf
default"
Autorepair : NA
Action Message : FTP configure is not exist
Verify /etc/vsftpd.conf is existed. This file effects the
operation of FTP. If /etc/vsftpd.conf is not exist , the
backup of it would be used.
450007-130 1. Alarm item
CheckID : 450007
Status : WARNING
Level :bussiness
Action Description: 450007-130: Repeat configuration
items existed in vsftpd.conf
normal
Solution : Please download report decompressing
it and execute command in
result/trace/450007_checkftpconfigresult.txt which existed
in the server's IP path.
Autorepair : NA

U2000
Action Message : FTP configure is not exist

Repeat configuration items existed in vsftpd.conf will lead
the service of FTP works abnormally; please refer to the
solution to resolve this problem.
3.1.8 450008_Verifying that the FTP Log File of /var/log/vsftpd.log

and Ftp Log Dump Timer Task is Normal.
Item Verifying that the ftp log file of /var/log/vsftpd.log and ftp log dump timer
task is normal.
Check ID 450008
Application SUSE
System

CheckItem : Check FTP Log and dump timer task
Action
Status : WARNING
Level :bussiness
Action Description: 450008-100: OSS FTP log is abnormal
and FTP log timer task not exist
Standard : Check whether the FTP log file of
/var/log/vsftpd.log and FTP log dump timer task is normal
Solution : Please login master/slaver server using
root user then execute following command :
1) echo "" > /var/log/vsftpd.log
2) bash /opt/oss_sudobin/imap/ftp/files/vsftpd_adm.sh
"enableFTP"
Autorepair : NA
Action Message : OSS FTP log is abnormal and FTP log
timer task not exist
Please login master/slaver server using root user then
execute following command :
"enableFTP"
Autorepair : NA
Action Message : OSS FTP log is abnormal and FTP log
timer task not exist
450008-200 1. Alarm item

U2000
CheckID : 450008
Action
Status : WARNING
Level :bussiness
Action Description: 450008-200: OSS FTP log is abnormal
Solution : Please login master/slave server using
root, then execute following command :
Autorepair : NA
Action Message : OSS FTP log is abnormal
Clear up the /var/log/vsftpd.log file manually. Please login
master/slave server using root, then execute following
command :
450008-300 1. Alarm item

CheckID : 450008
Action
Status : WARNING
Level :bussiness
Action Description: 450008-300: OSS FTP log dump timer
task not exist
Solution : Please login the server using root , then
execute following command:
"enableFTP"
Autorepair : NA
Action Message : OSS FTP log dump timer task not exist
Please login the server using root , then execute following
command:
"enableFTP"
450008-400 1. Alarm item

CheckID : 450008
Action
Status : OK

U2000
Level :bussiness
Action Description: 450008-400: OSS FTP log is normal
and FTP log dump timer task exist
Solution : NA
Autorepair : NA
Action Message : OSS FTP log is normal and FTP log
dump timer task exist
NA
3.1.9 450011_Verifying Permissions on the Configuration File of

the sshd Service
Item Verifying permissions on the configuration file of the sshd service
Check ID 450011
Application SUSE
System

CheckItem : CheckSshdFile_Action
Status : OK
Desc : 450011-100: SshdFile is normal.
Standard :In the sshd configuration file
/etc/ssh/sshd_config, the parameters must contain
'Subsystem' and 'sftp'.
Solution : NA
Autorepair : NA
Version :
Message : OK
NA

U2000
450011-110 1. Alarm item

CheckID : 450011
Status : WARNING
Desc : 450011-110: SshdFile is Abnormal
Solution : please check the item begin with
Subsystem in SshdFile /etc/ssh/sshd_config
Autorepair : NA
Version :
Message : SshdFile is Abnormal
Verify permissions on the configuration file of the sshd
service. If the analysis results include this alarm, the
configuration file of the sshd service is different from the
standard file. Contact Huawei technical support engineers.
450011-120 1. Alarm item
CheckID : 450011
Status : ERROR
Desc : 450011-120: SshdFile is not exist
Solution : please check /etc/ssh/sshd_config.
Autorepair : NA
Version :
Message : SshdFile is not exist
Verify permissions on the configuration file of the sshd
service. If the analysis results include this alarm, the
configuration file of the sshd service is different from the
standard file. Contact Huawei technical support engineers.
3.1.10 450012_Verifying Permissions on the File Related to the NE

License Export Task
Item Verifying permissions on the file related to the NE license export task
Check ID 450012

U2000
Application SUSE
System

CheckItem : CheckNeExportTask_Action
Status : OK
Desc : 450012-100: OSS NeExportTask is
normal.
Standard : The owner of file
/export/home/sysm/ftproot/nelicense/nblic/ExportNodeBLi
c.csv should be ossuser.
Solution : NA
Autorepair : NA
Version :
Message : OK
NA.
450012-110 1. Alarm item
CheckID : 450012
CheckItem : CheckNeExportTask_Action
Status : WARNING
Desc : 450012-110: OSS NeExportTask is
abnormal.
Standard : The owner of file
c.csv should be ossuser.
Solution : The owner of file
c.csv must be ossuser.
Autorepair : NA
Version :
Message : OSS NeExportTask is Abnormal.
Verify that the NE license export task is normal. If the
analysis results include this alarm, the NE license export
task is abnormal. Contact Huawei technical support
engineers.

U2000
3.1.11 450013_Verifying that the 3rdQueryExport Folder of the

DCC Tool Contains No Trash Files
Item Verifying that the 3rdQueryExport folder of the data collect channel
(DCC) tool contains no trash files
Check ID 450013
Application SUSE
System

CheckItem : CheckDccExpiredDir_Action
Status : OK
Desc : 450013-100: OSS DccExpiredDir is
normal.
Standard : Directory /export /home
/sysm/ftproot/3rdQueryExport should not exist documents
created the day before yesterday.
Solution : NA
Autorepair : NA
Version :
Message : OK
NA.
450013-110 1. Alarm item
CheckID : 450013
CheckItem : CheckDccExpiredDir_Action
Status : WARNING
Desc : 450013-110: OSS DccExpiredDir is
Abnormal .
Standard : Directory /export /home
/sysm/ftproot/3rdQueryExport should not exist documents
created the day before yesterday.
Solution : Please login in the OSS master server
with user root, then do then operation as follow: find
/export/home/sysm/ftproot/3rdQueryExport -mtime +1 !
-type d | xargs rm -r
Autorepair : NA
Version :
Message : WARNING
Check for junk data generated by the DCC tool. If the
analysis results include this alarm, the
/export/home/sysm/ftproot/3rdQueryExport directory

U2000
keeps files for more than 24 hours. Clear junk data in time.

U2000
3.2 Configuration Module

3.2.1 420005_Verifying that No Junk Data of NEs Exists
Item Verifying that no junk data of NEs exists
Check ID 420005
Application SUSE
System

Description : Check junk data for NE.
Info/log file : trace/420005_junkdata_ne.out
Detail : 420005-100: No junk NE data
exists.
Standard : Please check whether NE data exists
in omcdb.tbl_AllNeInfo, topodb.TSNode and
eamdb.tbl_ne.
Status : OK
Solution : NA
Autorepair : NA
TraceCollection :NA
NA.

U2000
420005-101 1. Alarm item

Check ID : 420005
Description : Check junk data for NE.
Info/log file : trace/420005_junkdata_ne.out
Detail : 420005-101: Junk NE data exists.
Standard : Please check whether NE data
exists in omcdb.tbl_AllNeInfo, topodb.TSNode and
eamdb.tbl_ne.
Status : ERROR
Solution : Please check whether to delete junk
NEs listed in the file trace/420005_junkdata_ne.out. To
delete, please run .
$IMAP_ROOT/rancn/bin/cleanJunkNe.sh.
Autorepair : NA
TraceCollection :NA
Junk data is produced in the server environment or when
services are terminated improperly. Junk data causes
improper operation of services.
Confirm whether to delete junk NEs.
3.2.2 420007_Verifying Permissions of System Users and

Permissions on the Directory
Item Verifying permissions of system users and permissions on the
synchronization and data export directories
Check ID 420007
Application SUSE
System

Description : Check right for user and directory.
Info/log file : trace/420007_right_dir.out and
trace/420007_right_user.out
Status : OK
Detail : 420007-100: User directory rights are
normal.
Risk : NA
Standard : Please run the command ls -l to
check whether user directory rights are normal.
Solution : NA
Solution effect : NAAutorepair : NA

U2000
TraceCollection :NA
NA.
420007-101 1. Alarm item
Check ID : 420007
Description : Check right for user and directory.
Info/log file : trace/420007_right_dir.out and
trace/420007_right_user.out
Status : ERROR
Detail : 420007-101: User directory rights
are abnormal.
Risk: Configuration Management including Inventory
Management, NE Synchronization couldn't run normally.
Standard : Please run the command ls -l to
check whether user directory rights are normal.
Solution : Please log in to the U2000 server as
user root, and run the following command to repair
directory rights(directory: the real directory,
ossuser,ossgroup: the real ownership,XXXX：the real
permission):chown ossuser:ossgroup directory,chmod
XXXX directory
Solution effect: None
Autorepair : NA
TraceCollection :NA
If user rights and user groups of the OSS are set
improperly, service failure may occur.
Check whether the user and user group are correct.
3.2.3 420008_Verifying that Files of Installed Mediation Are

Consistent with Database
Item Verifying the status of installed mediation
Check ID 420008
Application SUSE
System

U2000

Description : Check whether mediation files are
consistent with database.
Info/log file :
trace/420008_mediation_installed.out
Status : OK
Detail : 420008-100: The mediation files
are consistent with database.
Standard : Please check whether mediation
directory exists in $IMAP_ROOT/med whose isInstall is 1
in omcdb.ne2_MatchInfo.
Solution : NA
Autorepair : NA
TraceCollection :NA
NA.
420008-101 1. Alarm item
Check ID : 420008
Description : Check whether mediation files are
consistent with database.
Status : ERROR
Info/log file :
trace/420008_mediation_installed.out
Detail : 420008-101: The mediation files
are not consistent with database.
Standard : Please check whether mediation
directory exists in $IMAP_ROOT/med whose isInstall is 1
in omcdb.ne2_MatchInfo.
Risk: NEs using these abnormal mediations couldn't be
managed normally.
Solution : Please re-install Mediations list in
trace/420008_mediation_installed.out(The OSS will
change to restrict mode while installing Mediation).
Autorepair : NA
TraceCollection :NA
If the mediation file does not exist in the system mediation
directory, services may work improperly.
Check whether the mediation is successfully installed.
Solution effect: The OSS will change to restrict mode while
installing mediations.

U2000
3.2.4 420023_Check right mask of process

Item Check right mask of process
Check ID 420023
Application SUSE
System

Description : Check right mask of process.
Info/log file : NA
Status : OK
Detail : 420023-100: User process rights are
normal.
Standard : Please run the command ls -ld
/export/home/sysm/ftproot/TimerTask to check whether
directory rights are normal..
Solution : NA
Autorepair : NA
TraceCollection :NA
NA.
420023-101 1. Alarm item
Check ID : 420023
Description : Check right mask of process.
Info/log file : NA
Status : NA
Detail : 420023-101: User process rights
are abnormal.
Standard : Please run the command ls -ld
/export/home/sysm/ftproot/TimerTask to check whether
directory rights are normal..
Solution : Please get <Precautions on
Incorrect Permissions for the Dynamic Directory Created
by the Service Process on iManager U2000
V200R014C00SPC220 Previous version of
R014-20141015-A-1.0> from
http://support.huawei.com/carrier/docview?nid=SE000076
2994 to operate.
Autorepair : NA
TraceCollection :NA
NA.

U2000
3.2.5 420022_Check UsePAM configuration of Linux

Item Check UsePAM configuration of Linux
Check ID 420022
Application SUSE/Linux
System

Description : Check UsePAM configuration of
Linux.
Info/log file : NA
Status : OK
Detail : 420022-100: Succeeded in check
UsePAM.
Standard : Check if UsePAM of
/etc/ssh/sshd_config is yes.
Solution : NA
Autorepair : NA
TraceCollection :NA
NA.
420022-101 1. Alarm item
Check ID : 420022
Description : Check UsePAM configuration of
Linux.
Info/log file : NA
Status : ERROR
Detail : 420022-101: Failed to check
UsePAM.
Standard : Check if UsePAM of
/etc/ssh/sshd_config is yes.
Solution : Please get <After version U2000
V200R012 NCCService started Fail due to the parameters
of OS incorrectly> from
http://3ms.huawei.com/icase/#!icase/workflow/viewCase.ht
ml?casecode=TC0002825561 to operate.
Autorepair : NA
TraceCollection :NA
NA.

U2000
3.2.6 420010_Verifying that No Useless Meditation Exists

Item Verifying the status of installed mediation
Check ID 420010
Application SUSE
System

Description : Check no use mediations
Info/log file : trace/420010_mediation_nouse.out
Detail : 420010-100: Unused mediations do
not exist.
Standard : Compared the mediation installed in
omcdb.ne2_MatchInfo with the mediation used by NEs in
$IMAP_ROOT/var/neinfo.dat. Check whether any
mediation is not used by NEs.
Status : OK
Risk :NA
Solution : NA
Autorepair : NA
TraceCollection : NA
NA.
Solution effect : NA

U2000
420010-101 1. Alarm item

Check ID : 420010
Detail : 420010-101: Unused mediations exist.
Status : WARNING
Risk: The useless mediations expend database and disk
space.
Solution : Please check whether to uninstall the
mediations listed in the report.
Autorepair : NA
Some installed mediations are not used by any NE.
Remove useless mediations.
Solution effect: Uninstall Mediation need stop all the OSS
services.
420010-102 1. Alarm item

Check ID : 420010
Detail : 420010-102: Unused mediations exist.
Status : WARNING
space.
mediations listed in file
trace/420010_mediation_nouse.out.
Autorepair : NA
Some installed mediations are not used by any NE.
Remove useless mediations.
services.

U2000
420010-103 1. Alarm item

Check ID : 420010
Detail : 420010-103: A large number of
unused mediations exist.
Status : ERROR
space.
mediations listed in file
trace/420010_mediation_nouse.out.
Autorepair : NA
A large number of installed mediations are not used by any
NE. Remove useless mediations.
services.
420010-104 1. Alarm item

Check ID : 420010
Detail : 420010-104: There is no need to
check unused mediations.
Status : OK
Risk : NA
Solution : NA
Autorepair : NA
NA.

U2000
3.2.7 420014_Verifying the Running Status of the Mediation

Service
Item Verifying the running status of the mediation service
Check ID 420014
Application SUSE
System

CheckItem : med_status_check
Status : ERROR
Desc : 420014-200: Part of the
MediationServices are not running.
Standard : Check whether all
MediationService services are running properly.
Solution : Run the svc_adm -cmd status
command to verify mediation services which are not
started, and run the svc_adm -cmd startsvc name of the
abnormal service command.
Autorepair :NA
Version :Business
Result information :A part of MediationServices stop
running.
NE data cannot be uploaded to OSS because some
mediation services in the system work improperly.
Run the svc_adm -cmd status command to verify
mediation services which are not started, and run the
svc_adm -cmd startsvc name of the abnormal service
command.

U2000
420014-300 1. Alarm item

Check ID : 420014
CheckItem : med_status_check
Status : ERROR
Desc : 420014-300: All the
MediationServices are not running.
Standard : Check whether all
MediationService services are running properly.
Solution : Run the svc_adm -cmd status
command to verify mediation services which are not
started, and run the svc_adm -cmd startsvc name of the
abnormal service command.
Autorepair :NA
Version :Business
Result information : All Mediation services stop
running.
NE data cannot be uploaded to OSS because some
mediation services in the system work improperly.
Run the svc_adm -cmd status command to verify
mediation services which are not started, and run the
svc_adm -cmd startsvc name of the abnormal service
command.
3.2.8 420015_Verifying incorrect Permissions for the Dynamic

Directory Created by the Service Process
Item Verifying incorrect Permissions for the Dynamic Directory Created by the
Service Process
Check ID 420015
Application HP, ATAE

System

U2000

CheckItem : check_permission_directory
Status : OK
Desc : 420015-100: No incorrect
permissions for the directory, umask value exists.
Standard : check incorrect permissions for the
directory, umask value exists or not.
Solution : Please refer to
http://support.huawei.com/support/pages/kbcenter/view/pro
duct.do?actionFlag=detailManuscript&web_doc_id=SE000
0762994&doc_type=TechPost&doc_type=TechPost.
Autorepair :NA
420015-101 1. Alarm item
Check ID : 420015
CheckItem : check_permission_directory
Status : ERROR
Desc : 420015-101: incorrect permissions
for the directory, umask value exists.
Standard : check incorrect permissions for the
directory, umask value exists or not.
Solution : Please refer to
http://support.huawei.com/support/pages/kbcenter/view/pro
duct.do?actionFlag=detailManuscript&web_doc_id=SE000
0762994&doc_type=TechPost&doc_type=TechPost.
Autorepair :NA
3.2.9 422001_Check BTS3900NE's Function position on Topo

Item Check whether the NodeBFunction and GBTSFunction hanging in RNC
or BSC
Check ID 422001
Application SUSE
System

U2000

Description : Check whether BTS3900NE's
Function position on Topo is normal.
Status : OK
Detail : 422001-100: BTS3900NE's
function position is normal.
Standard : Check whether the NodeBFunction
and GBTSFunction hanging in RNC or BSC.
Risk :NA
Solution : NA
Autorepair : NA
NA.
422001-101 1. Alarm item
Check ID : 422001
Description : Check the stauts of NE management
task.
Status : ERROR
Detail : 422001-101: BTS3900NE's
function position is abnormal.
Standard : Check whether the NodeBFunction
and GBTSFunction hanging in RNC or BSC.
Risk : NE Alarm location error and NE
business interruption risk exists.
Solution : Please configure the base station IP
and the base station IP on the controller, to ensure that
they're the same.
Autorepair : NA
TraceCollection :NA
Some NodeBFunction or GBTSFunction on Topo not hang
in RNC or BSC, will cause some business facing error such
as NELicense, please refer to the Sulotion to repair that.
3.2.10 422002_Check whether omcdb has bad table

Item Check whether omcdb has bad table
Check ID 422002

U2000
Application SUSE
System

CheckItem : check_omc_badtable
Status : ERROR
Desc : 422002-100: The omcdb has bad
table.
Standard : Check whether omcdb has bad
table.
Solution : Please feedback the health check
Autorepair :NA
3.2.11 422005_Check whether neinfo.dat exists

Item Check whether neinfo.dat exists
Check ID 422005
Application ALL
System

CheckItem : check_neinfo_file
Status : ERROR
Desc : 422005-200: The neinfo.dat file
does not exist.
Standard : Check whether neinfo.dat exists.
Solution : Please log in to the U2000 server
as user ossuser and run:. /opt/oss/server/svc_profile.sh;
svc_adm -cmd restartsvc CMEngine.
Solution effect: NE creation and deletion couldn't be
executed when restarting services.
Autorepair :NA
3.2.12 422007_Check the stauts of NE management task

Item Check the stauts of NE management task(Create NE,Delete NE,Modify
NE)
Check ID 422007
Application ALL
System

U2000

task.
Status : OK
Detail : 422007-100: NE management task
is normal.
Standard : Check whether the creationTime in
omcdb.session_Session of Create NE,Delete NE,Modify
NE task over one day.
Solution : NA
Autorepair : NA
NA.
422007-101 1. Alarm item
Check ID : 422007
task.
Status : ERROR
Detail : 422007-101: NE management task
is abnormal.
Standard : Check whether the creationTime in
omcdb.session_Session of Create NE,Delete NE,Modify
NE task over one day.
Autorepair : NA
TraceCollection :NA
NA.
3.2.13 422008_Check auto search Ne

Item Check auto search Ne
Check ID 422008
Application ALL
System

U2000

CheckItem : check_ne_autosearch
Status : ERROR
Desc : 422008-100: NE search is
abnormal
Standard : Check whether NE search is
normal.
as user ossuser and run:. /opt/oss/server/svc_profile.sh;
cleanJunkNe.sh
If business couldn't be restored, please feedback the health
check package and contact Huawei technical support
engineers.
Solution effect: NA
Autorepair : NA
3.2.14 422011_Check the permission and ownership of the target

MML directory
Item Check the permission and ownership of the target MML directory
Check ID 422011
Application ALL
System

CheckItem : check_destmmldirpermission
Status : ERROR
Desc : 422011-100: The permission of the
target MML directory is incorrect.
Standard : check whether MML directory
permission is 770.
as user root, and run the following commands:
chown -Rf ossuser:ossgroup
/export/home/sysm/ftproot/intver
chmod -Rf 770 /export/home/sysm/ftproot/intver
Solution effect: NA
Autorepair : NA

U2000
422011-200 1. Alarm item

Check ID : 422011
CheckItem : check_destmmldirpermission
Status : ERROR
Desc : 422011-200: The ownership of the
target MML directory is incorrect.
Standard : check whether MML directory
ownership is ossuser :ossgroup.
as user root, and run the following commands:
chown -Rf ossuser:ossgroup
/export/home/sysm/ftproot/intver
chmod -Rf 770 /export/home/sysm/ftproot/intver
Solution effect: NA
Autorepair : NA
3.2.15 422013_Check whether the MBTS relation is correct

Item Check whether the MBTS relation is correct
Check ID 422013
Application SUSE
System

Description : Check whether the MBTS Relation
is correct.
Status : OK
Detail : 422013-100: The MBTS relation is
right.
Standard : check whether the MBTS
information and sub NEs on topodb.TSNode table,
omcdb.MBTS table, omcdb.MBTSRelation table and
omcdb.gv_MBTS_Site table is match.
Solution : NA
Autorepair : NA
NA.

U2000
422013-101 1. Alarm item

Check ID : 422013
Description : Check whether the MBTS Relation
is correct.
Status : ERROR
Detail : 422013-101:There are something
wrong on MBTS Relation.
Standard : check whether the MBTS
information and sub NEs on topodb.TSNode table,
omcdb.MBTS table, omcdb.MBTSRelation table and
omcdb.gv_MBTS_Site table is match.
Autorepair : NA
TraceCollection :NA
NA.
3.2.16 422024_Check the big moi tables of omcdb

Item Check the big moi tables of omcdb
Check ID 422024
Application SUSE
System

Description : Check the big moi tables of omcdb.
Status : OK
Detail : 422024-100: There is no big moi
table in omcdb.
Standard : check the MOC data table that from
${IMAP_ROOT}/etc/CBB/platform/objectToClaim.txt,
which the data count is larget than 1000000.
Solution : NA
Autorepair : NA
NA.

U2000
422024-200 1. Alarm item

Check ID : 422024
Description : Check the big moi tables of omcdb.
Status.
Status : ERROR
Detail : 422024-200: There are big moi
tables exist in omcdb.
Standard : check the MOC data table that
from
${IMAP_ROOT}/etc/CBB/platform/objectToClaim.txt,
which the data count is larget than 1000000.
Solution : Please get the solution from trace/
check_bigMoiTables/solution.txt to resolve it.
Autorepair : NA
TraceCollection :NA
Reduce the data count by this method that clear the useless
data.
Solution effect: need to stop all CmDcService service during
execute the solution.

U2000
3.2.17 410061_Verifying That the OSS NE Belongs to the Core and

Wireless Networks
Item Verifying that the OSS NE belongs to the core and wireless networks
Check ID 410061
Application SUSE
System
Detailed 410061-200 1. QuantityCheck alarm item

Description : check the mobile or core network
NE type.
Info/log file :
Status : WARNING
Detail : 410061-200: "Can not get NE
type."
Standard : Get NE name from
trace/quantity_ne_type_output file in package, then check
NE type with /opt/oss/server/etc/CBB/ne/NeTypeList.xml
and /opt/oss/server/etc/CBB/ne/NeTypeList_CN.xml.
Solution effect : None
Verify that the OSS NE belongs to the core and wireless
networks. If the analysis results include this alarm, the
required information is not collected. Contact Huawei
Remarks None
3.2.18 500124_Checking whether the historical MML file exists

Item Checking whether the historical MML file exists
Check ID 500124
Application SUSE
System

U2000

CheckItem : Checking whether the historical
MML file exists
Info/log file : N/A
Detail : 500124-100: The historical MML
file does not exist.
Risk : N/A
Standard :
Check whether the CMServer service is running. If the
service is running, check whether a file exists in the
following path (if a file exists and it was modified 90
days earlier, it is a historical file. A message must be
displayed to instruct users to delete the file):
/export/home/omc/var/TimerTask/{TaskId}/ history
/export/home/omc/var/TimerTask/{TaskId}/output
/export/home/omc/var/TimerTask/{TaskId}/bulk
Status : OK
Solution : N/A
Autorepair : N/A
TraceCollection : N/A
N/A
Solution effect: N/A

U2000
500124-200 1. Alarm item

CheckID : 500124
MML file exists
Info/log file : N/A
Detail : 500124-200: The MML history
file exists and you need to delete by yourself.
Risk : It will take up disk space if the MML
file is not deleted
Standard :
/export/home/omc/var/TimerTask/{TaskId}/ history
Status : WARNING
Solution : The MML history file exists in the
current version,Please check the MML files list in the
path of
trace/check_MML_historyfile/check_MML_historyfile.
txt which under the directory named master and slave
server IP in the oss health check package.
Autorepair : N/A
N/A
Solution effect: none

U2000
500124-300 1. Alarm item

CheckID : 500124
MML file exists
Info/log file : N/A
Detail : 500124-300: Have no CMServer,no
need to check.
Risk : N/A
Standard :
/export/home/omc/var/TimerTask/{TaskId}/history
Status : N/A
Solution : N/A
Autorepair : N/A
N/A

U2000
3.2.19 500125_Checking whether the configuration

synchronization frequency is normal
Item Checking whether the configuration synchronization frequency is normal
Check ID 500125
Application SUSE
System

CheckItem : Checking whether the configuration
Info/log file : N/A
Detail : 500125-100: The configuration
synchronization frequency is normal.
Risk : N/A
Standard : Execute the following statement to
check the configuration synchronization result table:
select * from synch_SynchInfo where
SYN_RESULT='Failed'
Status : OK
Solution : N/A
Autorepair : N/A
N/A

U2000
500125-200 1. Alarm item

CheckID : 500125
CheckItem : Checking whether the configuration
Info/log file : N/A
Detail : 500125-200: The configuration
synchronization frequency is abnormal.
Risk : N/A
check the configuration synchronization result table:
select * from synch_SynchInfo where
SYN_RESULT='Failed'
Status : INFO
Solution : Contact Huawei technical support.
Autorepair : N/A
N/A
3.2.20 500126_Checking the size of the cmsynch_MocChangeInfo

table
Item Checking the size of the cmsynch_MocChangeInfo table
Check ID 500126
Application SUSE
System

U2000

CheckItem : Checking the size of the
cmsynch_MocChangeInfo table
Info/log file : N/A
Detail : 500126-100: The size of the
cmsynch_MocChangeInfo table is normal.
Risk : N/A
check whether the number of data records in the
cmsynch_MocChangeInfo table exceeds 2,000,000:
select count(EntityId) from cmsynch_MocChangeInfo
Status : OK
Solution : N/A
Autorepair : N/A
N/A

U2000
500126-200 1. Alarm item

CheckID : 500126
CheckItem : Checking the size of the
cmsynch_MocChangeInfo table
Info/log file : N/A
Detail : 500126-200: The size of the
cmsynch_MocChangeInfo table is over large.
Risk : N/A
check whether the number of data records in the
cmsynch_MocChangeInfo table exceeds 2,000,000:
select count(EntityId) from cmsynch_MocChangeInfo
Status : INFO
Solution : Access the database and delete the
historical data generated one day ago. Before the deletion,
you must set the number of rows in which data is to be
deleted at a time to 50,000.
Oracle:
Execute the following statement to clear historical data:
delete from cmsynch_MocChangeInfo where
TimeLabel < (sysdate - 1);
Sybase:
Execute the following statements to set the number of
rows in which data is to be deleted:
use omcdb
go
set rowcount 50000
go
Execute the following statements repeatedly to clear
historical data till "0 rows affected" is displayed:
delete from cmsynch_MocChangeInfo where
TimeLabel < dateadd (day, -1, getdate())
go
Autorepair : N/A
N/A

U2000
3.2.21 422105_ Check whether the CaptureAssistant is installed
Item Check whether the CaptureAssistant is installed
Check ID 422105
Application SUSE
System

CheckItem : Check whether the
CaptureAssistant is installed
Info/log file : N/A
Detail : 422105-100: The
CaptureAssistant tool is not installed.
Risk : N/A
Standard : Check whether the dir
/export/home/omc/var/logs/CaptureAssistant/ exist, if it
does not exist, return ok.
Status : OK
Solution : N/A
Autorepair : N/A
N/A

U2000
422105-200 1. Alarm item

CheckID : 422105
CheckItem : CaptureAssistant tool is not
installed.
Info/log file : N/A
Detail : 422105-200: The
CaptureAssistant tool is installed,it need to be
uninstalled.
Risk : N/A
Standard : If there is a directory
Use the command: ls -lsRt / export / home / omc / var /
logs / CaptureAssistant / traverse the entire directory.
(2 minutes after the completion of the order prompt to
uninstall the tool)
Status : INFO
Solution : Please use ossuser to login to the
OSS slave server or master server which was installed
the CaptureAssistant tool.Then,please switch to root and
run the following commands:
su - root
. /opt/oss/server/svc_profile.sh
cd /export/home/omc/var/logs/CaptureAssistant
./restore.sh
rm -rf /export/home/omc/var/logs/CaptureAssistant
Autorepair : N/A
N/A

U2000
422105-300 1. Alarm item

CheckID : 422105
CheckItem : CaptureAssistant tool is not
installed.
Info/log file : N/A
Detail : 422105-300: The
CaptureAssistant tool generates too many files.
Risk : N/A
Standard : If there is a directory, then
Use the command:ls -lsRt
/export/home/omc/var/logs/CaptureAssistant/ through
the entire directory.
(2 minutes before the command execution is finished
need script halts the command is executed, the system
will prompt the content relatively much needs to return
the preventive maintenance packages)
Status : INFO
Solution : Please contact Huawei technical
support.
Autorepair : N/A
N/A
3.3 Northbound Module

3.3.1 460002_Verifying that the snmp Process Does Not Occupy
Port 161 or Port 162
Item Verifying that the snmp process does not occupy port 161 or port 162
Check ID 460002
Application SUSE
System

U2000

Description : Check whether the port of the
snmp_agent service is 161 or 162.
Standard : Get the configuration in
$IMAP_ROOT/etc/nbi/snmp/snmpagent.xml.
Info/log file : NA
Detail : 460002-200: The port is 161 or 162.
Status : Error
Port 161 or port 162 cannot be occupied by the snmp
process. Contact Huawei technical support engineers.
3.3.2 460001_Check whether NBI Files (Corba) Are Accumulated

Item Check whether northbound CORBA performance files are accumulated.
Path for check: /export/home/omc/var/itf_n/FileTransferIRP/PM
In a ATAE cluster system, this check item is performed on both the master
and slave servers.
Check ID 460001
Application SUSE
System

Description : Check whether the NBI performance
CORBA files are accumulated.
Detail : 460001-200: The NBI performance
CORBA files are accumulated.
Standard : Check the files in
$IMAP_ROOT/var/itf_n/FileTransferIRP/PM.
Info/log file : NA
Status : Error
If NBI files are accumulated, the system resources are
insufficient, and the backup task on the OSS cannot be
completed within a long period. Contact Huawei technical
support engineers.
3.3.3 460003_Check the Version of NBI Interface Is New Or Old

Item Check the version of NBI interface is new or old.

U2000
itf_SRAN70: use SRAN7.0 interface, itf_new: use new interface
Check ID 460003
Application SUSE
System

Description : check_nbi_interface_version
Standard : Get the configuration from
$IMAP_ROOT/etc/CBB/itfn/NeModelNbiCompatible.xml.
Info/log file : NA
Detail : 460003-200: Failed to check the
version of NBI interface is new or old.
Status : WARNING
If the status is “WARNING”. Contact Huawei technical
support engineers.
3.3.4 460031_ Check the Sybase monitor tool installed status

Item Check whether it need to run system using U2000 NorthBound database
interface of Sybase have serious database problem Precaution Notice
Check ID 460031
Application SUSE
System
Detailed 460031-200 CheckID : 460031

Solution Description : Check whether it need to run system
using U2000 NorthBound database interface of Sybase
have serious database problem Precaution Notice.
Standard : Check whether it need to run system
using U2000 NorthBound database interface of Sybase
have serious database problem Precaution Notice.
Info/log file : NA
Detail : 460031-200: Check whether it need
to run system using U2000 NorthBound database interface
of Sybase have serious database problem Precaution
Notice.
Status : ERROR
Please run the Precaution Notice:
Precaution of the system using U2000 NorthBound
database interface of Sybase have serious database problem
http://support.huawei.com/carrier/docview?nid=SC200000

U2000
0633&path=PBI1-7851894/PBI1-7854702/PBI1-7275896/
PBI1-21103986/PBI1-14033
3.3.5 460032_Check whether the subscribe info of NBI corba alarm

interface is normal
Item Check whether the subscribe info of NBI corba alarm interface is normal.
Path for check:
$IMAP_ROOT/var/itf_n/NotificationIRP/SubscribeInfos.xml
Check ID 460032
Application SUSE
System

Solution Description : Check whether the subscribe info of
NBI corba alarm interface is normal.
Standard : Check whether the file of
$IMAP_ROOT/var/itf_n/NotificationIRP/SubscribeInfos.x
ml is normal.
Info/log file : NA
Detail : 460032-101: The subscribe info of
corba alarm interface is abnormal.
Status : Error
The subscribe info of corba alarm interface is abnormal.
3.4 Performance Module

3.4.1 430134_ Check status of the log truncate switch of pmdb and
pmcomdb
Item Check status of the log truncate switch of pmdb and pmcomdb
Check ID 430134
Application SUSE
System

Solution Description : Check status of the log truncate
switch of pmdb and pmcomdb.
Standard : The log truncate switch of pmdb and
pmcomdb is open.
Info/log file : NA

U2000
Detail : 430134-200: The log truncate switch

of the pmdb and pmcomdb is closed.
Status : WARNING
Please login database and run the SQL to open the switch of
pmdb and pmcomdb=Please login database and run the
SQL to open the switch of pmdb:
.1>use master
2>go
1> sp_dboption pmdb, "trunc log on chkpt", true
2>go
1>use pmdb
2>go
1>checkpoint
2>go
and pmcomdb
1>use master
2>go
1> sp_dboption pmcomdb, "trunc log on chkpt", true
2>go
1>use pmcomdb
2>go
1>checkpoint
2>go
430134-202 CheckID : 430134
Description : Check status of the log truncate
switch of pmdb and pmcomdb.
Standard : The log truncate switch of the pmdb is
closed.
Info/log file : NA
Detail : 430134-202: The log truncate switch
of the pmdb is closed.
Status : WARNING
.1>use master
2>go
1> sp_dboption pmdb, "trunc log on chkpt", true
2>go
1>use pmdb
2>go
1>checkpoint
2>go

U2000
3.4.2 510053_ Check management capacity result

Item Check management capacity result infomation
CheckID 510053
Application SUSE
System

Description : Check management capacity result
Information.
Standard : Check if the usage of management
capacity less than 70%.
Info/log file : NA
Detail : 510053-100: The management capacity
is ok.
Status : OK
NA
510053-200 1. Alarm item
CheckID : 510053
Information.
Standard : Check if it can get the usage of
management capacity successfuly.
Info/log file : NA
Detail : 510053-200: Get the management
capacity fail.
Status : INFO
Please contact Huawei technical support engineers.

U2000
510053-300 1. Alarm item

CheckID : 510053
Information.
capacity surpassed 70%.
Info/log file : NA
Detail : 510053-300: The usage of management
capacity has surpassed 70%.
Status : WARNING
Get the U2000 management capacity report from U2000
OSMU OSSCAT to check the detail manament capacity
information.
510053-400 1. Alarm item
CheckID : 510053
Information.
capacity surpassed 100%.
Info/log file : NA
Detail : 510053-400: The usage of management
capacity has surpassed 100%.
Status : ERROR
Get the U2000 management capacity report from U2000
OSMU OSSCAT to check the detail manament capacity
information.
3.5 Alarm Module

3.5.1 440014_Verifying that Uncleared Alarms for a Long Time do
not Exist in the Current Alarm List
Item Verifying that uncleared alarms for a long time do not exist in the current
alarm list
Check ID 440014
Application SUSE
System

U2000

CheckItem : Check alarms uncleared for a long
time
Status : WARNING
Desc : 440014-200: The alarm that remains
uncleared for a long time exists in tbl_cur_alm.
Solution : By default, the system verifies alarms
uncleared for more than 90 days. Check whether the alarms
uncleared for a long time affect the operation of the live
network, and clear these alarms.
Autorepair : Rectify the fault by referring to the
operations mentioned in the related alarm document. The
alarm is automatically cleared after the fault is rectified. If
you are sure that the fault has been rectified, manually clear
the alarm.
Message : The alarm that remains uncleared for a
long time exists in tbl_cur_alm.
By default, the system verifies alarms uncleared for more
than 90 days. Check whether the alarms uncleared for a
long time affect the operation of the live network, and clear
these alarms.
3.5.2 440015_Verifying that Alarms with Unknown Alarm Sources

Do Not Exist in the Current Alarm List
Item Verifying that alarms with unknown alarm sources do not exist in the
current alarm list
Check ID 440015
Application SUSE
System
CheckItem : Check the alarms existing with
unknown alarm sources.
Status : WARNING
Desc : 440015-200: Uncleared alarm with
unknown alarm sources exists.
Standard : Check whether an alarm that lasts for
more than 90 days exists in the database (tbl_cur_alm). If
such alarm does not exist, the result is normal.
Solution : Junk alarm data exists in the alarm
database. Rectify the fault by referring to the operations

U2000
mentioned in the related alarm document. The alarm is

automatically cleared after the fault is rectified. If you are
sure that the fault has been rectified, manually clear the
alarm.
Autorepair : Rectify the fault by referring to the
operations mentioned in the related alarm document. The
alarm is automatically cleared after the fault is rectified. If
you are sure that the fault has been rectified, manually clear
the alarm.
Standard : Check whether an alarm that has
unknown source and is not cleared exists in the database
(tbl_cur_alm). If such alarm does not exist, the result is
normal.
Message : Uncleared alarm with unknown alarm
sources exists.
Junk alarm data exists in the alarm database. Rectify the
fault by referring to the operations mentioned in the related
alarm document. The alarm is automatically cleared after
the fault is rectified. If you are sure that the fault has been
rectified, manually clear the alarm.
3.5.3 440032_Check whether alarm buffer is fully or not
Item Check whether alarm buffer is fully or not

Check ID 440032
Application SUSE
System
CheckItem : Check whether alarm buffer is fully or
not
Status : WARNING
Desc : 440032-101: Alarm buffer is full or
near full.
Standard : Single server:login server by
“ossuser”,execute the following command: .
/opt/oss/server/svc_profile.sh, Switch to the path of
/opt/oss/server/var/logs/, execute the following command:
cat iMAP.ifms_agent.trace |grep "pushAlarmSeq,preBuff is
full or nearly full",if have the output, the alarm buffer is
full or near full.
distribute server:master server is not involved; login slave
server, execute the following command: .
/opt/oss/server/svc_profile.sh, Switch to the path of
/opt/oss/server/var/logs/, execute the following command:

U2000
cat iMAP.FMPreService*_agent.trace |grep

"pushAlarmSeq,preBuff is full or nearly full", if have the
output, the alarm buffer is full or near full.
Risk : The alarm buffer will be cleared when
it is full, the alarms will be lost.
Solution : Please collect information as
following operation,and contact Huawei technical support
engineers to analyse: login OSMU by ”ossuser“ > Smart
Assistant >Trouble Shooting >Trace Collection > Fault
Module> Receiving NE alarms is delay(selelct any NE on
this server, take two days logs contain current time. )
Autorepair : NA
Message : Alarm buffer is full or near full.
Please collect information as following operation,and
contact Huawei technical support engineers to analyse:
login OSMU by ”ossuser“ > Smart Assistant >Trouble
Shooting >Trace Collection > Fault Module > Receiving
NE alarms is delay(selelct any NE on this server, take two
days logs contain current time. )
3.5.4 440033_Check whether alarm was stored in DB

Item Check whether alarm was stored in DB
Check ID 440033
Application SUSE
System
CheckItem : Check whether alarm was stored in
DB
Status : ERROR
Desc : 440033-101: Alarm store into DB fail.
Standard : Check IMAP.ifms_agent.trace file on
the master to detect whether the following information
"StoreIntoDB***failed".
Risk : Alarms on U2000 may be incorrect.
engineers to analyse: login OSMU by "ossuser" > Smart
Module > Failed to receive NE alarms.
Autorepair : NA

U2000
Message : Alarm store into DB fail

Please contact Huawei technical support engineers.
3.5.5 440034_Check alarm buffer cleared or not
Item Check alarm buffer cleared or not

Check ID 440034
Application SUSE
System
CheckItem : Check alarm buffer cleared or not
Status : ERROR
Desc : 440033-101: The alarm buffer has
been cleared.
Standard : Check IMAP.ifms_agent.trace file on
the master to detect whether the following information
"AR@Cur fullprocess".
Risk : Alarms on U2000 may be inconsistent
with those on NEs.
engineers to analyse: login OSMU by "ossuser" > Smart
Module > Failed to receive NE alarms.
Autorepair : NA
Message : The alarm buffer has been cleared.
Please collect information as following operation,and
contact Huawei technical support engineers to analyse:
login OSMU by "ossuser" > Smart Assistant >Trouble
Shooting >Trace Collection > Fault Module > Failed to
receive NE alarms.
CheckItem : Check alarm buffer cleared or not
Status : WARNING
Desc : 440034-102: It's going to clear alarm
buffer.
Standard : Check the total number of alarms in
the alarm table (tbl_cur_alm). If the number almost reaches

U2000
the maximum capacity of the alarm table (tbl_cur_alm), the

alarm buffer is about to be cleared.
Risk : U2000 is going to clear alarm buffer,
alarms will be lost.
Solution : You are advised to set Auto
Acknowledgement (for Server) to Real-time and set
Lifecycle for the alarm to 0 hours. Clear the alarms that
have been generated for a long period of time to reduce the
alarm amount, thereby preventing the buffer from being
cleared.
Autorepair : NA
Message : It's going to clear alarm buffer.
You are advised to set Auto Acknowledgement (for Server)
to Real-time and set Lifecycle for the alarm to 0 hours.
Clear the alarms that have been generated for a long period
of time to reduce the alarm amount, thereby preventing the
buffer from being cleared.
3.5.6 440042_Check Whether Uncleared Important OSS Alarms

Exist
Item Check Whether Uncleared Important OSS Alarms Exist
Check ID 440042
Application SUSE
System
CheckItem : Check Whether Uncleared Important
OSS Alarms Exist
Status : WARNING
Desc : 440042-200: Uncleared important
OSS alarms are detected.
Standard : Check OSS alarms in the current alarm
table tbl_cur_alm. If uncleared important OSS alarms
exist, export the key alarm information (Log Serial
Number, Alarm ID, Name, Severity, Location Information,
and Occurred On) to the oss_alarm.csv file.
Solution : View the uncleared important OSS
alarms in the check result. Rectify the faults based on the
alarm handling solutions provided in U2000 Alarm
Reference in the U2000 product documentation.
Autorepair : NA
TraceCollection : Obtain the alarm data table

U2000
tbl_cur_alm.
Message : Uncleared important OSS alarms are
detected. For detailed alarm information, see the
oss_alarm.csv file in the check result.
View the uncleared important OSS alarms in the check
result. Rectify the faults based on the alarm handling
solutions provided in U2000 Alarm Reference in the
U2000 product documentation.
3.6 CME
Check ID Application Description
System
480006 SUSE Verifying the CME database space

480018 SUSE Verifying the system database or table space of the
database; verifying the space of
tempdb/master/tmp_dev of Sybase and the space of
SYSAUX/SYSTEM/UNDOTBS1 of Oracle.
480070 SUSE Check precaution information about CME
3.6.1 480006_ Verifying the CME database space

Item Verifying the CME database space
Check ID 480006
Application SUSE
System

CheckItem : Verifying the CME database space
Status : WARNING
Desc : 480006-200: The cmedb data
space is abnormal.
Standard : An error message is displayed if
the log space usage of the database exceeds 80% or the
database space usage exceeds 90%
Solution : Clear the database or expand the
database capacity in the non-standard delivery
environment. Clear the database in the standard delivery

U2000
environment.
Autorepair : NA.
TraceCollection : NA..
Message : The cmedb data space is abnormal.
Risk: The function of CME will be affected with the
high database usage of cmedb.
Clear the database or expand the database capacity in
the non-standard delivery environment. Clear the
database in the standard delivery environment.
Solution effect: None.
480006-201 1. Alarm item
CheckID : 480006
CheckItem : Verifying the CME database space
Status : WARNING
Desc : 480006-201: The cmedb log data
space is abnormal.
Standard : An error message is displayed if
the log space usage of the database exceeds 80% or the
database space usage exceeds 90%.
Solution : Clear the database or expand the
database capacity in the non-standard delivery
environment. Clear the database in the standard delivery
environment..
Autorepair : NA.
TraceCollection : NA.
Message : The cmedb log data space is
abnormal.
high database usage of cmedb.
Clear the database or expand the database capacity in
the non-standard delivery environment. Clear the
database in the standard delivery environment.
3.6.2 480018_ Verifying the system database or table space of the

database
Item Verifying the system database or table space of the database
Check ID 480018
Application SUSE

U2000
System

CheckItem : Verifying the system database or
table space of the database
Status : WARNING
Desc : 480018-200: The tempdb space is
abnormal.
Standard : An error message is displayed
when the tempdb space usage of the Sybase database
exceeds 90% or when the UNDOTBS1, SYSTEM, or
SYSAUX space usage of the Oracle database exceeds
90%.
Solution : Expand the database capacity or
clear the database.
Autorepair : NA.
Message : The tempdb space is abnormal.
high database usage of cmedb..
Expand the database capacity or clear the database.
480018-201 1. Alarm item

CheckID : 480018
CheckItem : Verifying the system database or
table space of the database
Status : WARNING
Desc : 480018-201: The
UNDOTBS1/SYSTEM/SYSAUX space is abnormal.
Standard : An error message is displayed
when the tempdb space usage of the Sybase database
exceeds 90% or when the UNDOTBS1, SYSTEM, or
SYSAUX space usage of the Oracle database exceeds
90%.
Solution : Expand the database capacity or
clear the database.
Autorepair : NA.
Message : The
UNDOTBS1/SYSTEM/SYSAUX space is abnormal.
high database usage of
UNDOTBS1/SYSTEM/SYSAUX.

U2000
Expand the database capacity or clear the database.

3.6.3 480070_ Check precaution information about CME

Item Check precaution information about CME
Check ID 480070
Application SUSE
System

CheckItem : Check precaution information
about CME
Status : WARNING
Desc : 480070-400: Check precaution
information about CME successfully, please check
Action Message for the detailed precaution information
about current CME version.
Standard : Check whether all the relative
precautions are executed.
Solution : Please check whether all the
relative precautions listed in Action Message are
executed.Then please execute the relative precautions
which has not been executed.
Autorepair : NA.
Message : The relative precautions list which
has not been executed.
Please check whether all the relative precautions listed
in Action Message are executed.Then please execute the
relative precautions which has not been executed.

3.7 Trace Server Module
3.7.1 600002_Verifying the trace server version

Item Verifying the trace server version
Check ID 600002
Application SUSE
System

Solution Action ID : 600002
Action Name : Verifying the trace server version
Status : WARNING
Action Description : 600002-101: Failed to collect the
trace server version.
Standard : Run the .
/opt/oss/server/svc_profile.sh ;displayVersion -c
command to check the current version.
Solution : Contact Huawei technical support
engineers.
Autorepair : NA.
Action Message : Failed to collect the trace
server version.
Failed to collect the trace server version, contact Huawei
3.7.2 600003_Verifying that the temp directorys of The trace server

services are normal
Item Verifying that the temp directorys of The trace server services are normal.
Check ID 600003
Application SUSE
System

Action Name : Check whether the used space of
the temporary directorys of the Trace Server are normal
or not.
Status : WARNING

Action Description : 600003-101: The temp directorys
of The trace server services are abnormal.
Standard : Run the df –h command to check
whether the temporary directory
(export/home/sysm/export/home/sysm/ftproot/SauService
/rawdata) is mounted.
Solution : Use the command umount
/export/home/sysm/ftproot/SauService/rawdata mount
temporary directory, use the df -h command to check the
mount is successful, if unsuccessful contact Huawei
Autorepair : NA.
Action Message : The temp directorys of The trace
server services are abnormal.
The temp directorys of The trace server services are
abnormal., follow the solution.
3.7.3 600004_Verifying that the softlinks of the trace server services

are normal
Item Verifying that the softlinks of the trace server services are normal
Check ID 600004
Application SUSE
System

Action Name : Verifying that the softlinks of the
Trace Server services are normal or abnormal.
Status : WARNING
Action Description : 600004-101: The softlinks of the
trace server services are abnormal.
Standard : Check whether the soft links of the
following directories exist:
/export/home/sysm/ftproot
/export/home/sysm/internalftp
/export/home/omc/var/filein
Solution : (1) Log in to the Trace Server board
as user ossuser, and switch to user root.
(2) Check and rectify soft links.
(a) Check and rectify the ftproot soft link:
#cd /export/home/sysm/export/home/sysm
If the ftproot soft link does not exist, run the following
commands:

#ln -s ../../../ftproot/ ftproot
#chown -h ftpuser:ossgroup ftproot
(b) Check and rectify the internalftp soft link:

#cd /export/home/sysm/export/home/sysm
If the internalftp soft link does not exist, run the following
commands:
ln -s ../../../internalftp/ internalftp
chown -h ftpuser:ossgroup internalftp
(c) Check and rectify the fileint soft link:

#cd /export/home/omc/var/
If the fileint soft link does not exist, run the following
commands:
#ln -s export/home/omc/var/fileint/ fileint
#chown -h ossuser:ossgroup fileint
Autorepair : NA.
Action Message : The softlinks of the trace
server services are abnormal.
The softlinks of the trace server services are abnormal,
follow the solution.
3.7.4 600005_Verifying that the rights of the trace server are normal
Item Verifying that the rights of the trace server are normal
Check ID 600005
Application SUSE
System

Action Name : Verifying that the rights of the trace
server are normal.
Status : WARNING
Action Description : 600005-101: The rights of the trace
server are abnormal.
Standard : Check whether the permission on
/export/home/omc is 750 ossuser:ossgroup
Solution : (1) Log in to each Trace Server
board as user ossuser and switch to user root:
su - root
PassWord: password of user root
(2) Run the following commands to modify the

permission:
cd /export/home
chown ossuser:ossgroup omc
chmod 750 omc.
Autorepair : NA.
Action Message : The rights of the trace server are
abnormal.
The rights of the trace server are abnormal,follow the
solution.
3.7.5 600007_Verifying that the sftp of the trace server is normal

Item Verifying that the sftp of the trace server is normal
Check ID 600007
Application SUSE
System

Action Name : Verifying that the sftp of the trace
server is normal.
Status : WARNING
Action Description : 600007-101: The sftp
of the trace server is abnormal.
Standard : Check whether SFTP login as user
ftpuser is successful.
Solution : Log in to the Trace Server as user
ossuser and switch to user root.
Run the sftp ftpuser@127.0.0.1 command and enter the
password of user ftpuser.
If user ftpuser cannot log in to the Trace Server using
SFTP, contact Huawei technical support.
Autorepair : NA.
Action Message : The sftp of the trace server is
abnormal.
The sftp of the trace server is abnormal,follow the
solution.
3.7.6 600008_Verifying that the result directories of the trace server

services are ok
Item Verifying that the result directories of the trace server services are ok

Check ID 600008
Application SUSE
System

Action Name : Verifying that the result directories
of the trace server services are ok or not.
Status : WARNING
Action Description : 600008-101: The result directories of
the trace server services are not ok.
Standard : Check whether the number of nodes
occupied by
/export/home/sysm/internalftp/var/SauService/filter
subdirectories (EBC, eCoordinator, Nastar, and NIC)
exceeds 50000000.
engineers.
Autorepair : NA.
Action Message : The result directories of the
trace server services are not ok.
The result directories of the trace server services are not
ok, contact Huawei technical support engineers.
3.7.7 600010_ Verifying that the Sqlite3 database of the Trace Server
is complete
Item Verifying that the Sqlite3 database of the Trace Server is complete
Check ID 600010
Application SUSE
System

Action Name : Verifying that the Sqlite3 database
of the Trace Server is complete
Status : WARNING
Action Description : 600010-200: The
Sqlite3 database of Trace Server is not complete.
Standard : Run the sqlite3 DBFile "Pragma
integrity_check" command. (DBFile indicates the
absolute path of the sqlite3 file.)
engineers.

Autorepair : NA.
Action Message : The Sqlite3 database of Trace Server
is not complete.
The Sqlite3 database of Trace Server is not complete,
3.8 iMAP Module

3.8.1 800001_Check whether PartitionService is normal or not
Item Check whether PartitionService is normal or not
Check ID 800001
Application SUSE
System

Description : Check whether PartitionService is
normal or not
Standard : Check the log of PartitionService,
whether there is abnormal information.
Info/log file : Logs within two hours
/opt/oss/server/var/logs/iMAP.partition_agent.trace
/opt/oss/server/var/logs/tracebak/iMAP.partition_agent.trac
e*
Detail : 800001-100: PartitionService is
normal.
Status : OK
NA

CheckID : 800001
Description : Check whether PartitionService is
normal or not
Standard : Check the log of PartitionService,
whether there is abnormal information.
Info/log file : Logs within two hours
/opt/oss/server/var/logs/tracebak/iMAP.partition_agent.trac
e*
Detail : 800001-101: PartitionService is
abnormal.

Status : ERROR
1) Collect the follow informations about the time of using
this tool：
/opt/oss/server/var/logs/iMAP.script.trace
/opt/oss/server/var/logs/iMAP.imapsysd.trace
/opt/oss/server/var/logs/iMAP.svc_adm.trace
/opt/oss/server/var/logs/iMAP.imap_sysmonitor.trace
/opt/oss/server/var/logs/tracebak/iMAP.script.trace*
/opt/oss/server/var/logs/tracebak/iMAP.imapsysd.trace*
/opt/oss/server/var/logs/tracebak/iMAP.svc_adm.trace*
/opt/oss/server/var/logs/tracebak/iMAP.imapeventmgr.trace
*
/opt/oss/server/var/logs/mrblog/iMapSysd_p65_*
/opt/oss/server/var/logs/mrblog/iMAPMrb_p2_*
/opt/oss/server/var/logs/mrblog/imap_sysmonitor_p66_*
2) Please send those information and the test paper to the
huawei engineers for further analysis.
3.8.2 800002_Check whether imapeventmgr is normal or not

Item Check whether imapeventmgr is normal or not
Check ID 800002
Application SUSE
System

Description : Check whether imapeventmgr is
normal or not
Standard : 1) Whether there is core files of
imapeventmgr.
2) Check whether the time between the last trace in
iMAP.imapevents.trace and the time now is bigger than 30
minutes or not.
Info/log file : 1) Core files in
/opt/oss/server/var/logs
2) /opt/oss/server/var/logs/ iMAP.imapevents.trace
Detail : 800002-100: imapeventmgr is
normal.
Status : OK
NA

CheckID : 800002
normal or not
imapeventmgr.
minutes or not.
Detail : 800002-101: imapeventmgr is
warning.
Status : WARNING
1) Collect the follow files：
/opt/oss/server/var/logs/core.imapeventmgr*

CheckID : 800002
normal or not
imapeventmgr.
minutes or not.
Detail : 800002-102: imapeventmgr is error.
Status : ERROR
1) Collect the follow informations about the time of using
this tool：
/opt/oss/server/var/logs/iMAP.imapeventmgr.trace
/opt/oss/server/var/logs/iMAP.script.trace
/opt/oss/server/var/logs/iMAP.imapsysd.trace
/opt/oss/server/var/logs/iMAP.svc_adm.trace
/opt/oss/server/var/logs/iMAP.imap_sysmonitor.trace
/opt/oss/server/var/logs/tracebak/iMAP.script.trace*
/opt/oss/server/var/logs/tracebak/iMAP.imapsysd.trace*

/opt/oss/server/var/logs/tracebak/iMAP.svc_adm.trace*
/opt/oss/server/var/logs/tracebak/iMAP.imapeventmgr.trace
*
/opt/oss/server/var/logs/mrblog/iMapSysd_p65_*
/opt/oss/server/var/logs/mrblog/iMAPMrb_p2_*
/opt/oss/server/var/logs/mrblog/imap_sysmonitor_p66_*

3.9 ES&Mini
3.9.1 708050_ Check whether register the ES and whether the
ES status is normal
Item Check whether register the ES and whether the ES status is normal
Check ID 708050
Application SUSE
System

Description : Check whether register the ES and
whether the ES status is normal
Standard ：please run emgproxy_adm -c status
on OSS master board to check whether register the ES
and whether the ES status is normal, if the status
abnormal, Please contact Huawei technical support.
If there are alarm, please check this file
708050_check_es_status.log
Action Description: Check the ES status successfully
Detail : 708050-100: Check the ES status
successfully
Status : OK
NA

Action Description : Have not registered ES to
OSS
Detail : 708050-200: Have not registered ES to
OSS
Status : WARNING
Please refer to the part <Setting Up the Mapping
Between the Emergency System and the Primary System>
on the document <ATAE Cluster Emergency System User
Guide> to register ES.For Your Attention: Mini system
and ES system Can not coexist.

Action Description : The ES status is
abnormal, Please contact Huawei technical
support.<br>Risk:The data can not be synchronized
from OSS to ES abnormally, then ES will not take over
the business abnormally
Detail : 708050-300: The ES status is
Status : ERROR
Please send the health check report to HQ, and contact

Action Description : There is no task to
synchronize data.<br>Risk:The data can not be
synchronized from OSS to ES abnormally, then ES will
not take over the business abnormally
Detail : 708050-400: There is no task to
synchronize data.<br>Risk:The data can not be
Status : ERROR

Action Description : There are alarm on ES,
please check detail in this file
708050_check_es_status.log. Risk:The data can not be
Detail : 708050-500: There are alarm on ES,
please check detail in this file
708050_check_es_status.log. Risk:The data can not be
Status : ERROR

Action Description : NA
Detail : 708050-600: NA
Status : NA
NA

Action Description : The ES status is
Detail : 708050-700: Have not registered ES to
OSS
Status : WARNING
Please refer to the part <Setting Up the Mapping
Between the Emergency System and the Primary System>
on the document<Virtual Emergency System User Guide>
to register ES.For Your Attention: Mini system and
ES system Can not coexist.
3.9.2 708056_ Check whether have deployed ATAE Mini

system
Item Check whether have deployed ATAE Mini system
Check ID 708056
Application SUSE
System

Description : Check whether have
deployed ATAE Mini system
Standard ：Log in to ATAE OSMU board, and run
the command: crontab -l|grep mini , if following
information is displayed: 0 3 * * *
/opt/mini_sys/mini_sys_tools/mini_sys/miniRoutine
Sync.sh , the deployment is complete; then run the
command: cat
/opt/mini_sys/mini_sys_tools/mini_sys/syncdatares
ult.dat |grep Success ,if the information "Success"
is displayed, the data backup is complete. If the ATAE
Mini system have not deployed, please according to
deployment guide to do.
Action Description : The ATAE Mini system is
normal.
Detail : 708056-100: The ATAE Mini system is
normal
Status : OK
NA

command: cat
Action Description : The U2000 have registered
ES, no need to deploy ATAE Mini system.
Detail : 708056-200: No need to deploy ATAE
Mini system
Status : OK
NA

command: cat
Action Description : Have not deployed ATAE
Mini system
Detail : 708056-300: Have not deployed ATAE
Mini system
Status : WARNING
Please refer to the "Installing the ATAE Mini
Emergency System" in <U2000 ATAE Mini Emergency
System User Guide> to deploy Mini system. For Your
Attention: Mini system and ES system Can not coexist.

command: cat
Action Description : Backup data failed on
ATAE Mini system. Risk:The data backup on ATAE Mini
system is abnormal, then ATAE Mini system will not
take over the business abnormally
Detail : 708056-400: Backup data failed on
ATAE Mini system. Risk:The data backup on ATAE Mini
system is abnormal, then ATAE Mini system will not
take over the business abnormally
Status : ERROR
NA

command: cat
Action Description : NA
Detail : 708056-500: NA
Status : NA
NA
3.10 FMA
3.10.1 440043_Checking the Running Disk Resources of the FMA
Item Checking the running disk resources of the FMA
Check ID 440043
Application SUSE
System

Description : Check the running disk resources of the
FMA.
Status : OK
Area : Business
Detail : 440043-100: Check the running disk
resources of the FMA.
Solution : N/A
Autorepair : N/A
Message : Available disk resources are sufficient
for the FMA.
N/A
440043-200 1. Alarm item
CheckID : 440043
Description : Check the running disk resources of the
FMA.
Status : WARNING
Area : Business
Detail : 440043-200: Check the running disk
Solution : Running resources are sufficient for the
FMA. Yo need to add FMA boards or clean up disks.
Autorepair : N/A
Message : Running resources are insufficient for
the FMA. The available hard disk space is less then 100 GB.
Risk : The FMA or U2000 performance is
affected. FMA services may automatically stop.
3.10.2 440044_Checking the Equivalent NEs Managed by the FMA

Item Checking the equivalent NEs managed by the FMA
Check ID 440044
Application SUSE
System

Description : Check the equivalent NEs managed by
the FMA.
Status : OK
Area : Business
Detail : 440044-100: Check the equivalent
NEs managed by the FMA.
Solution : N/A
Autorepair : N/A
Message : Equivalent NEs are managed by the
FMA properly.
N/A
440044-200 1. Alarm item
CheckID : 440044
Description : Check the equivalent NEs managed by
the FMA.
Status : WARNING
Area : Business
Detail : 440044-200: Check the equivalent
NEs managed by the FMA.
Solution : Running resources are insufficient for
the FMA. You need to add FMA boards.
Autorepair : N/A
the FMA. The FMA manages more than 1200 equivalent NEs.
3.10.3 440045_Checking the Available CPU Resources of the FMA

Item Checking the available CPU resources of the FMA
Check ID 440045
Application SUSE
System

Description : Check the available CPU resources of
the FMA.
Status : OK
Area : Business
Detail : 440045-100: Check the available
CPU resources of the FMA.
Solution : N/A
Autorepair : N/A
Message : Available CPU resources are sufficient
for the FMA.
N/A
440045-200 1. Alarm item
CheckID : 440045
Description : Check the available CPU resources of
the FMA.
Status : WARNING
Area : Business
CPU resources of the FMA.
Solution : Running resources are insufficient for
the FMA. You need to add FMA boards.
Autorepair : N/A
the FMA. The available CPU resources account for 35%.
3.10.4 440046_Checking the Available Memory Resources of the

FMA
Item Checking the available memory resources of the FMA
Check ID 440046
Application SUSE
System

Description : Check the available memory resources
of the FMA.
Status : OK
Area : Business
Detail : 440046-100: Check the available CPU
Solution : N/A
Autorepair : N/A
Message : Available memory resources are
sufficient for the FMA.
N/A
440046-200 1. Alarm item
CheckID : 440046
Description : Check the available memory resources
of the FMA.
Status : WARNING
Area : Business
memory resources of the FMA.
Solution : Running resources are insufficient
for the FMA. You need to add FMA boards.
Autorepair : N/A
Message : Running resources are insufficient
for the FMA. The size of the available memory is smaller
than 5 GB.

U2000
OSMU Health Check Verification Items 4 Inventory Data Collection Verification Items
4 Inventory Data Collection Verification

Items
After the inventory data collection tool performs tasks, verification items in the analysis
results are categorized and sorted based on fields in the EXCEL file generated for the task.
If the inventory data collection tool performs tasks on different operating systems (OSs), such
as the SUSE OSs, a field is contained in the analysis results of multiple verification items. In
this case, the verification items are in the same category.

U2000
4.1 Basic Site Information

4.1.1 220018_Verifying the Country Name
Item Verifying the country name
Check ID 220018
Application SUSE
System

Description : get the country name.
Info/log file :
country name."
Standard : Collect country name through
entering information at foreground
Status : WARNING
Collect country name in which such special characters as
~ ! @ # $ % ^ & * ( ) _ + { } | " : ? > < ` - = [ ] \ ; ' , . / are
not allowed through entering information at foreground,
And the maximum number of input characters in the
country name is 50. If the analysis results include this
alarm, the required information is not collected. Contact
Remarks None

U2000
4.1.2 220019_Verifying the City Name

Item Verifying the city name
Check ID 220019
Application SUSE
System

Description : get the city name.
Info/log file :
Detail : 220019-200: "Can not get the city
name."
Standard : Collect city name through entering
information at foreground
Status : WARNING
Collect city name in which such special characters as ~ !
@ # $ % ^ & * ( ) _ + { } | " : ? > < ` - = [ ] \ ; , . / are not
allowed through entering information at foreground, And
the maximum number of input characters in the city name
is 50. If the analysis results include this alarm, the
Remarks None

U2000
4.1.3 220020_Verifying the Customer Name

Item Verifying the customer name
Check ID 220020
Application SUSE
System

Description : get the customer name.
Info/log file :
customer name."
Standard : Collect customer name through
entering information at foreground
Status : WARNING
Collect customer name in which such special characters as
~ ! @ # $ % ^ & * ( ) _ + { } | " : ? > < ` - = [ ] \ ; ' , . / are
not allowed through entering information at foreground ,
And the maximum number of input characters in the
customer name is 50. If the analysis results include this
Remarks None

U2000
4.1.4 220002_Verifying the Server IP Address

Item Verifying the server IP address
Check ID 220002
Application SUSE
System

Description : check the ip address of the node
Info/log file : hosts hostname.out ifconfig_a.out
Detail : 220002-200: "can not get the ip
address of the node."
Standard : Run the hostname and ifconfig -a
commands and check the /etc/hosts file to verify the server
IP address.
Status : WARNING
Run the hostname and ifconfig -a commands and check
the /etc/hosts file to verify the server IP address. If the
analysis results include this alarm, the required
information is not collected. Contact Huawei technical
support engineers.
Remarks None

U2000
4.1.5 220003_Verifying That Dual Planes Are Configured

Item Verifying that dual planes are configured
Check ID 220003
Application SUSE
System

Description : check the ipmp or bond
configuration
Info/log file : ifconfig_a.out
Detail : 220003-101: "The ipmp is not
configured."
Standard : Run the ifconfig -a command to
verify that dual planes are configured; Bond dual planes
apply to the Linux OS.
Status : NA
Run the ifconfig -a command to verify that dual planes
are configured. If the analysis results include this alarm,
IPMP dual planes are not configured on the server.
Determine whether to configure dual planes based on live
network conditions. For details about how to configure
dual planes, see the guide to software initial installation of
the required version.
220003-103 1. QuantityCheck alarm item
Check ID : 220003-103
Description : check the ipmp or bond
configuration
Info/log file : ifconfig_a.out
Detail : 220003-103: "The bond is not
configured."
Standard : Run the ifconfig -a command to
verify that dual planes are configured; Bond dual planes
apply to the Linux OS.
Status : NA
Run the ifconfig -a command to verify that dual planes
are configured. If the analysis results include this alarm,
Bond dual planes are not configured on the server.
Determine whether to configure dual planes based on live
network conditions. For details about how to configure
dual planes, see the guide to software initial installation of
the required version.

U2000
4.1.6 220014_Verifying the Floating IP Address

Item Verifying the floating IP address
Check ID 220014
Application SUSE
System

Description : check the float ip of the server.
Info/log file :
Detail : 220014-101: "There is no float ip."
Standard : Query environment variables and
network mode to verify the floating IP address.
Status : NA
Query environment variables and network mode to verify
the floating IP address. If the analysis results include this
alarm, do not need to configure float ip address.
Check ID : 220014-200
Description : check the float ip of the server.
Info/log file :
Detail : 220014-200: "can not check the
float ip."
Standard : Query environment variables and
network mode to verify the floating IP address.
Status : WARNING
Query environment variables and network mode to verify
the floating IP address. If the analysis results include this
Remarks None

U2000
4.1.7 410058_Verifying the Validity of the OSS License

Item Verifying the validity of the OSS license
Check ID 410058
Application SUSE
System

Description : check the license of OSS
Info/log file : omc_license.out
Status : WARNING
Detail : 410058-200: "can not get the
license of the OSS."
Standard :The OSS license must be
commercial.
Verify the validity of the OSS license and save the
command output to the omc_license.out file. If the
support engineers.

Check ID : 410058-201
Description : check the license of OSS
Info/log file : omc_license.out
Status : WARNING
Detail : 410058-201: " the license of OSS is
not PERMANENT."
Standard :The OSS license must be
commercial.
Verify the validity of the OSS license and save the
command output to the omc_license.out file. If the
analysis results include this alarm, the OSS license expires
or is a non-commercial license. Please update the OSS
commercial license by referring to section " Loading or
Updating the U2000 License" in the administrator guide
of the required version.
Remarks None

U2000
4.1.8 490004_Verifying the Software Version of the PRS Deployed

on the Server for the OSS
Item Verifying the software version of the PRS deployed on the server for the
OSS
Check ID 490004
Application SUSE
System

Description : get the version of OSS integrated
PRS
Info/log file : omcprs_version.out
Status : NA
Detail : 490004-101: "The PRS integrated
with OSS is not installed."
Standard : Collect the PRS version
information.
Verify the software version of the PRS deployed on the
server on which the OSS is deployed. If the analysis
results include this alarm, the PRS integrated with OSS is
not installed.
Check ID : 490004-200
PRS
Status : WARNING
version of the PRS integrated with OSS."
Standard : Collect the PRS version
information.
Verify the software version of the PRS deployed on the
server on which the OSS is deployed. If the analysis
results include this alarm, the required information is not
collected. Contact Huawei technical support engineers.
Remarks None
4.1.9 480054_Verifying the Software Version of the CME

Integrated into the OSS

U2000
Item Verifying the software version of the CME integrated into the OSS
Check ID 480054
Application SUSE
System

CME
Info/log file : CMEBizVersion.xml
Status : WARNING
version of the CME integrated with U2000."
Verify the software version of the CME integrated into the
OSS. If the analysis results include this alarm, the required
support engineers.
Remarks None

U2000
4.1.10 410059_Verifying the Validity of the License of the CME

Integrated into the OSS
Item Verifying the validity of the license of the CME integrated into the OSS
Check ID 410059
Application SUSE
System

Description : check the license of the CME
integrated with U2000
Info/log file : cmelicense.out
Status : WARNING
license of the CME integrated with U2000."
Standard : The CME license must be
commercial.
Verify the validity of the license of the CME integrated
into the OSS and save the command output to the
cmelicense.out file. If the analysis results include this

Check ID : 410059-201
Status : WARNING
Description : check the license of the CME
integrated with U2000
Info/log file : cmelicense.out
Detail : 410059-201: "the license of the
CME integrated with U2000is not PERMANENT."
Standard : The CME license must be
commercial.
Verify the validity of the license of the CME integrated
into the OSS and save the command output to the
cmelicense.out file. If the analysis results include this
alarm, the CME license expires or is a non-commercial
license. Contact Huawei technical support engineers.
Remarks None

U2000
4.1.11 410041_Verifying the Networking Mode of the Server

Item Verifying the networking mode of the server
Check ID 410041
Application SUSE
System

Description : check the network mode of the
server
Info/log file : N/A
network mode of the server."
Standard : Query framework environment
variables to verify the networking mode of the server.
Status : WARNING
Query framework environment variables to verify the
networking mode of the server. If the analysis results
include this alarm, the required information is not
Remarks None

U2000
4.1.12 410009_ Verifying That the Operating System Security

Hardening Software Is Installed
Item Verifying that the operating system security hardening software is
installed
Check ID 410009
Application SUSE
System

Description : check the installation of operating
system security hardening software
Detail : 410009-101: "operating system
security hardening software is not installed."
Standard : If sek command is exist,Security
hardening software of OS is installed.
Status : NA
Verify that the operating system security hardening
software is installed. If the analysis results include this
descriptive item, the operating system security hardening
software is not installed. Determine whether to install the
operating system security hardening software. For details
about how to install the operating system security
hardening software, see the security hardening-related
documents.
Remarks None

U2000
4.1.13 410056_Verifying the Security Hardening Software Version

Item Verifying the security hardening software version
Check ID 410056
Application SUSE
System

Description : get the version of security
hardening software
Detail : 410056-101: "Security hardening
software is not installed."
Standard : Run the sek -v command to verify
the security hardening software version
Status : NA
Run the sek -v command to verify the security hardening
software version. If the analysis results include this alarm,
it illuminate security hardening software is not installed.
Check ID : 410056-200
Description : get the version of security
hardening software
version of security hardening software."
Standard : Run the sek -v command to verify
the security hardening software version
Status : WARNING
Run the sek -v command to verify the security hardening
software version. If the analysis results include this alarm,
the required information is not collected. Contact Huawei
Remarks None

U2000
4.1.14 210008_Verifying the NTP Service Type

Item Verifying the NTP service type
Check ID 210008
Application SUSE
System

Description : check the type of NTP service.
Info/log file : ntp.conf
Detail : 210008-200: "Can not get the type
of NTP service."
Standard : Resolve the /etc/ntp.conf or
/etc/inet/ntp.conf file to verify the NTP service type.
Status : WARNING
Resolve the /etc/ntp.conf or /etc/inet/ntp.conf file to
verify the NTP service type and save related information
to the ntp.conf file. If the analysis results include this
alarm and the NTP service has been configured, verify the
NTP service setting or running status by referring to
U2000 Administrator Guide. If no NTP service has been
configured, ignore this verification item.
Remarks None

U2000
4.1.15 210010_Verifying the NTP Service Status

Item Verifying the NTP service status
Check ID 210010
Application SUSE
System

Description : check the status of NTP service.
Info/log file : ntpq-p.out
Detail : 210010-200: "Can not get the status
of NTP service."
Standard : Run the ntpq -q command to get the
NTP service status.
Status : WARNING
Run the ntpq -q command to verify the NTP service
status and save the command output to the ntpq-p.out
file. If the analysis results include this alarm and the NTP
service has been configured, verify the NTP service
setting or running status by referring to U2000
Administrator Guide. If no NTP service has been
Check ID : 210010-201
Description : check the status of NTP service.
Info/log file : ntpq-p.out
Detail : 210010-201: " Ntp service is not
running."
Standard : Run the ntpq -q command to get the
NTP service status.
Status : WARNING
Run the ntpq -q command to verify the NTP service
status and save the command output to the ntpq-p.out
file. If the analysis results include this alarm and the NTP
service has been configured, verify the NTP service
setting or running status by referring to U2000
Administrator Guide. If no NTP service has been
Remarks None

U2000
4.1.16 410062_Verifying That NAT Is Configured on the OSS

Item Verifying that NAT is configured on the OSS
Check ID 410062
Application SUSE
System

Description : Check if NAT is configured
Info/log file : tao.cfg ipmap.cfg
Status : NA
Detail : 410062-101: The NAT is not
configured.
Standard :The NAT configuration files
'tao.cfg' and 'ipmap.cfg' must be exist.
NA
Check ID : 410062
Description : Check if NAT is configured
Info/log file : tao.cfg ipmap.cfg
Detail : 410062-200: " Can not check the
NAT configuration."
Status : WARNING
Standard :The NAT configuration files
'tao.cfg' and 'ipmap.cfg' must be exist.
Verify that NAT is configured on the OSS. If the analysis
Remarks None

U2000
4.2 Outsourced Parts Information

4.2.1 110002_Verifying the HP/ATAE/IBM Server Model
Item Verifying the HP/ATAE/IBM server model
Check ID 110002
Application SUSE
System

Description : check the type of the server
Standard : dmidecode -t 1 command to verify
the HP/ATAE/IBM server model
Info/log file : prtdiag.out
Detail : 110002-200: "can not get the type
of machine."
Status : WARNING
Run the dmidecode -t 1 command to verify the
HP/ATAE/IBM server model. If the analysis results
Remarks None
4.2.2 210011_Verifying the Memory Size

Item Verifying the memory size
Check ID 210011
Application SUSE
System

U2000

Description : get the total memory of the server.
Info/log file : prtconf.txt meminfo.txt
Detail : 210011-200: "can not get the total
memory."
Standard : Check the file /proc/meminfo (Suse)
to verify the memory size.
Status : WARNING
Check the /proc/meminfo file to verify the memory size.
If the analysis results include this alarm, the required
support engineers.
Remarks None
4.2.3 150040_Verifying Local Hard Disk Information

Item Verifying the size and number of local hard disks
Check ID 150040
Application SUSE
System

Description : check the local disk info.
Standard : Execute similar command "prtvtoc
/dev/dsk/c0t0d0s2" to verify size and number of local
disks.
Solution : Please see the /proc/partitions file
(SuSE) to get the info.
Info/log file : prtvtoc_c0t0d0.out
Detail : 150040-200: "can not get the local
disk info."
Status : WARNING
Run the prtvtoc command to verify the size and number
of local hard disks. If the analysis results include this
Remarks None

U2000
4.2.4 350009_Verifying the VxVM Software Version

Item Verifying the VxVM software version
Check ID 350009
Application SUSE
System

Description : verify VxVM disk status
Info/log file : rpm_vrts.out
Detail : 350009-101: "VxVM is not
installed."
Status : NA
Standard : Collect the output of command
'rpm -qa | grep VRTS' on Linux.
Solution : NA
Run the rpm -qa | grep VRTS command to verify the
VxVM software version and save the command output to
the rpm_vrts.out file. If the analysis results include this
alarm,it illuminate VxVM is not installed.
Check ID : 350009-200
Description : verify VxVM disk status
version of VxVM."
Status : WARNING
Solution : Please run the command rpm -qa
| grep VRTSvxvm (SuSE) to show the version.
VxVM software version and save the command output to
rpm_vrts.out file. If the analysis results include this
Remarks None
4.2.5 350010_Verifying the Validity of the VxVM License

Item Verifying the validity of the VxVM license

U2000
Check ID 350010
Application SUSE
System

Description : check the license of VxVM
Info/log file : vxlicrep _is.out
Detail : 350010-101 "VxVM is not
installed."
Status : NA
'vxlicrep -is', the value of 'License Type' must be
'PERMANENT'.
Run the vxlicrep -is command to verify the validity of the
VxVM license and save the command output to the
vxlicrep_is.out file. If the analysis results include this
alarm, it illuminate VxVM is not installed.
Check ID : 350010-200
Description : check the license of VxVM
Info/log file : vxlicrep _is.out
Detail : 350010-200 "can not get the license
of VxVM"
Status : WARNING
'PERMANENT'.

U2000

Check ID : 350010-201
Description : verify VERTAS volume maganer
License
Info/log file : ha/vxlicrep_is.out
Status : WARNING
Detail : 350010-201: " the license of VxVM
is not PERMANENT."
'PERMANENT'.
alarm, the VxVM license expires or is a non-commercial
license. Run the vxlicinst command on the server and
enter a commercial license.
Remarks The VxVM license must be permanent.

License Type = PERMANENT

U2000
4.2.6 340015_Verifying the VCS Software Version

Item Verifying the VCS software version
Check ID 340015
Application SUSE
System

Description : get the version of VCS
Detail : 340015-101: " VCS is not
installed."
Status : NA
VCS software version and save the command output to the
alarm, it illuminate VCS is not installed.
Check ID : 340015-200
Description : get the version of VCS
Detail : 340015-200: " can not get the
version of VCS."
Status : WARNING
VCS software version and save the command output to the
Remarks None

U2000
4.2.7 340016_Verifying the Validity of the VCS License

Item Verifying the validity of the VCS license
Check ID 340016
Application SUSE
System

Info/log file : vxlicrep_is.out
Detail : 340016-101：VCS is not installed."
Status : NA
Description : check the license of VCS
'PERMANENT'.
VCS license and save the command output to the
alarm, it illuminate VCS is not installed.
Check ID : 340016-200
license of VCS."
Status : WARNING
'PERMANENT'.

U2000

Check ID : 340016-201
'PERMANENT'.
Detail : 340016-201: " the license of VCS
is not PERMANENT."
Status : WARNING
alarm, the VCS license expires or is a non-commercial
license. Run the vxlicinst command on the server and
enter a commercial license.
Remarks The VCS license must be permanent.

License Type = PERMANENT
4.2.8 110014_Verifying the Warranty Service of the Server

Item Verifying the warranty service of the server
Check ID 110014
Application SUSE
System

Description : get the warranty service.
Info/log file : NA
Detail : 110014-101: "The input contains no
characters."
Standard : Input the warranty service info
manually.
Status : INFO
Verify the warranty service of the server manually. If the
analysis results include this alarm,it illuminate do not
input information about this item.

U2000

Check ID : 110014-200
Description : get the warranty service.
Info/log file : NA
warranty service."
Standard : Input the warranty service info
manually.
Status : WARNING
Verify the warranty service of the server manually. If the
support engineers.
Remarks None
4.2.9 230008_Verifying the SUSE OS Version

Item Verifying the SUSE OS version
Check ID 230008
Application SUSE
System

Description : get the version of the OS
Info/log file : OS_Version_Number.txt
Detail : 230008-200: "there is no
/etc/SuSE-release."
Status : WARNING
Check the /etc/SuSE-release file to verify the SUSE OS
version and save the command output to the
OS_Version_Number.txt file. If the analysis results
Remarks This verification item only applies to the SUSE Linux OS.

U2000
4.2.10 310001_Verifying the Sybase Database Version

Item Verifying the Sybase database version
Check ID 310001
Application SUSE
System

CheckItem : Get the version of sybase database
Status : NA
Desc : 310001-101: "The sybase database is
not installed."
Solution : NA
Autorepair : NA
Area : Database
Message : NA
QuantityCheck 310001 get the sybase version, if it shows
this warning,it illuminate it is not install sybase database.
CheckID : 310001
CheckItem : Get the version of sybase database
Status : WARNING
Desc : 310001-200: "Can not get the
version of sybase"
Standard : su - dbuser and run command cd
/opt/sybase/ASE*/bin;./dataserver -v to show the version
Solution : Please switch to user dbuser using su
- dbuser and run the command cd
/opt/sybase/ASE*/bin;./dataserver -v to show the version.
Autorepair : NA
Area : Database
Message : Can not get the version of sybase
QuantityCheck 310001 get the sybase version, if it shows
this warning please get the information as below(ATAE
Cluster need login database board):
# su - dbuser
$ /opt/sybase/ASE-*/bin/dataserver -v.
Remarks None

U2000
4.2.11 150084_Verifying the Disk Array Controller Version

Item Verifying the disk array controller version
Check ID 150084
Application SUSE
System

Description : get the disk array controller
version.
Info/log file : showsn.txt inquiry-data.txt
Detail : 150084-200: "can not get the disk
array controller version."
Standard : Run the showctrlinfo command or
check the storageArrayProfile.txt file to verify the disk
array controller version.Only support 6140 and S2600
disk array.
Status : WARNING
Run the showctrlinfo command or check the
storageArrayProfile.txt file to verify the disk array
controller version. If the analysis results include this
Remarks Information about disk arrays on the standby server in distributed

deployment mode is not required. Information about the S2600 disk array
can be collected.

U2000
4.2.12 150081_Verifying the Disk Array Model

Item Verifying the disk array model
Check ID 150081
Application SUSE
System

Description : check the type of the disk array
Info/log file : format.out prtvtoc.out rpm_qa.out
lsscsi.out
Detail : 150081-101: "There is no disk
array."
Standard : Check disk array type used
command lsscsi (SUSE).
Status : NA
Verify the model of the disk array used by the server. If
the analysis results include this alarm, There is no disk
array.
Check ID : 150081-200
Description : check the type of the disk array
Standard : Check disk array type used
command lsscsi (SUSE).
lsscsi.out
of the disk array."
Status : WARNING
Verify the model of the disk array used by the server. If
the analysis results include this alarm, the required
support engineers.
Remarks The following disk array models can be identified: S3X00, S3200,
S2600.

U2000
4.2.13 150082_Verifying That Disk Array Information Can Be

Collected
Item Verifying that disk array information can be collected
Check ID 150082
Application SUSE
System

Description : check if the information of the disk
array can be collected
Standard : Connect disk array, make sure disk
array info whether can be collected.
lsscsi.out smcli_d_i.txt sccli_list.txt exit.txt
Detail : 150082-200: "the information of the
disk array can not be collected."
Status : WARNING
Verify that disk array information can be collected. If the
information is not collected. Check whether the disk array
IP address can be pinged or whether the login password is
correct.
Check ID : 150082-201
Description : check if the information of the
disk array can be collected.
Standard : Connect disk array, make sure disk
array info whether can be collected.
lsscsi.out smcli_d_i.txt sccli_list.txt exit.txt
Detail : 150082-201: "can not determine if
the information can be collected."
Status : WARNING
Verify that disk array information can be collected. If the
support engineers.
Remarks Information about disk arrays on the standby server in distributed

deployment mode is not required. The following disk array models can be
identified: S3X00, S3200, S2600.

U2000
4.2.14 150083_Verifying the Serial Number of the Disk Array

Item Verifying the serial number of the disk array
Check ID 150083
Application SUSE
System

Description : get the disk array serial number.
Standard : Run the showsn and show
inquiry-data command to verify the serial number of the
disk array. Information about the S2600 disk array can be
collected.
Info/log file : showsn.txt inquiry-data.txt
Detail : 150083-200: "can not get the disk
array serial number."
Status : WARNING
Run the showsn and show inquiry-data command to
verify the serial number of the disk array. If the analysis

U2000
4.2.15 170001_Verifying the Tape Drive Model

Item Verifying the tape drive model
Check ID 170001
Application SUSE
System

Description : check the type of the tape drive
Standard : Pleas run the command lsscsi to get
the tape info.
Info/log file : lsscsi.out
Detail : 170001-101: "There is no tape
drive."
Status : NA
Verify the model of the tape drive used by the server. If
the analysis results include this alarm, There is no tape
drive.
Check ID : 170001-200
Description : check the type of the tape drive
Standard : Pleas run the command lsscsi to get
the tape info.
Info/log file : lsscsi.out
of the tape drive."
Status : WARNING
Verify the model of the tape drive used by the server. If
support engineers.
Remarks None

U2000
4.3 Third-Party Access Information

4.3.1 460020_Verifying the Manufacturer of the NMS
Item Verifying the manufacturer of the NMS
Check ID 460020
Applicatio SUSE
n System

Description : Get the NMS vendor's name.
Standard : Get the NMS vendor's name from
input.
Info/log file : N/A
Detail : 460020-101: "No NMS vendor's
name exists."
Status : NA
Collect the manufacturer of the NMS in which such
special characters as ~ ! @ # $ % ^ & * ( ) _ + { } | " : ? > <
` - = [ ] \ ; ' , . / are not allowed through entering
information at foreground, And the maximum number of
input characters in the manufacturer of the NMS is 50. If
information is not collected. Check whether an NMS
device is available on the live network. If yes, enter the
correct NMS information.
Remarks None

U2000
4.3.2 450058_Verifying the deployment status of the NBI line test

interface
Item Verifying the deployment status of the NBI line test interface
Check ID 450058
Applicatio SUSE
n System

Description : Get the deployment status of the NBI
line test interface.
Standard : Check the service status of
NGNNI112Service.
Info/log file : N/A
Detail : 450058-200: "Failed to get the
deployment status of the NBI line test interface."
Status : NA
Verifying the deployment status of the NBI line test
interface. If the analysis results include this alarm, the
Remarks None

U2000
4.3.3 450057_Verifying the deployment status of the NBI TMF814

interface
Item Verifying the deployment status of the NBI TMF814 interface
Check ID 450057
Applicatio SUSE
n System

TMF814 interface.
CorbaAgent.
Info/log file : N/A
Detail : 450057-200: " Failed to get the
deployment status of the NBI TMF814 interface."
Status : NA
Verifying the deployment status of the NBI TMF814
Remarks None

U2000
4.3.4 450056_Verifying the deployment status of the NBI TL1

interface
Item Verifyingthe deployment status of the NBI TL1 interface
Check ID 450056
Applicatio SUSE
n System

TL1 interface.
NGNNIServic.
Info/log file : N/A
deployment status of the NBI TL1 interface."
Status : NA
Verifying the deployment status of the NBI TL1 interface.
If the analysis results include this alarm, the required
support engineers.
Remarks None

U2000
4.3.5 450055_Verifying the deployment status of the NBI

configuration SNMP interface
Item Verifying the deployment status of the NBI configuration SNMP interface
Check ID 450055
Applicatio SUSE
n System

Description : Getthe deployment status of the NBI
configuration SNMP interface.
Standard : Check the status of SnmpAgent and
the configuration of nms users in snmpagent.xml.
Info/log file : N/A
deployment status of the NBI configuration SNMP
interface."
Status : NA
Verifying the deployment status of the NBI configuration
SNMP interface. If the analysis results include this alarm,
the required information is not collected. Contact Huawei
Remarks None

U2000
4.3.6 450054_Verifying the deployment status of the NBI Syslog

interface
Item Verifying the deployment status of the NBI Syslog interface
Check ID 450054
Applicatio SUSE
n System

Syslog interface.
Standard : Check the data in
omcdb..tbl_SyslogServer.
Info/log file : N/A
deployment status of the NBI Syslog interface."
Status : NA
Verifying the deployment status of the NBI Syslog
Remarks None

U2000
4.3.7 450052_ Verifying the deployment status of the NBI CORBA

security interface
Item Verifying the deployment status of the NBI CORBA security interface
Check ID 450052
Applicatio SUSE
n System

Description : Get the deployment status of the
NBI CORBA security interface.
Standard : Check the existance of
/export/home/omc/var/itf_n/SecurityIRP/2.ior.
Info/log file : N/A
deployment status of the NBI CORBA security interface."
Status : WARNING
Verify the deployment status of the NBI CORBA security
Remarks None

U2000
4.3.8 450051_ Verifying the deployment status of the NBI

RADIUS user authentication interface
Item Verifying the deployment status of the NBI RADIUS user authentication
interface
Check ID 450051
Applicatio SUSE
n System

NBI RADIUS user authentication interface.
SecurityService and the configuration in
$IMAP_ROOT/etc/security/auth.cfg and the value of
/imap/security/common/LoginMode.
Info/log file : N/A
deployment status of the NBI RADIUS user
authentication interface."
Status : WARNING
Verify the deployment status of the NBI RADIUS user
authentication interface. If the analysis results include this
Remarks None

U2000
4.3.9 450050_ Verifying the deployment status of the NBI LDAP

user authentication interface
Item Verifying the deployment status of the NBI LDAP user authentication
interface
Check ID 450050
Applicatio SUSE
n System

NBI LDAP user authentication interface.
SecurityService and the configuration in
$IMAP_ROOT/etc/security/auth.cfg and the value of
/imap/security/common/LoginMode.
Info/log file : N/A
deployment status of the NBI LDAP user authentication
interface."
Status : WARNING
Verify the deployment status of the NBI LDAP user
authentication interface. If the analysis results include this
Remarks None

U2000
4.3.10 450049_ Verifying the deployment status of the NBI LDAP

user management interface
Item Verifying the deployment status of the NBI LDAP user management
interface
Check ID 450049
Applicatio SUSE
n System

NBI LDAP user management interface.
Standard : Check the status of SMLDAPServic.
Info/log file : N/A
deployment status of the NBI LDAP user management
interface."
Status : WARNING
Verify the deployment status of the NBI LDAP user
management interface. If the analysis results include this
Remarks None

U2000
4.3.11 450048_ Verifying the deployment status of the NBI NE

license file interface
Item Verifying the deployment status of the NBI NE license file interface
Check ID 450048
Applicatio SUSE
n System

NBI NE license file interface.
$IMAP_ROOT/var/fileint/lm.
Info/log file : N/A
deployment status of the NBI NE license file interface."
Status : WARNING
Verify the deployment status of the NBI NE license file
Remarks None

U2000
4.3.12 450047_ Verifying the type of files exported from the NBI
inventory file interface
Item Verifying the type of files exported from the NBI inventory file interface
Check ID 450047
Applicatio SUSE
n System

Description : Get the type of files exported from
the NBI inventory file interface.
Standard : Get the type of files exported in
$IMAP_ROOT/var/fileint/cm/InvtTimerExport.
Info/log file : N/A
Detail : 450047-200: "Failed to get the type
of files exported from the NBI inventory file interface."
Status : WARNING
Verify the type of files exported from the NBI inventory
file interface. If the analysis results include this alarm, the
Remarks None

U2000

inventory file interface
Item Verifying the deployment status of the NBI inventory file interface
Check ID 450046
Applicatio SUSE
n System

inventory file interface.
$IMAP_ROOT/var/fileint/cm/InvtTimerExport.
Info/log file : N/A
deployment status of the NBI inventory file interface."
Status : WARNING
Verify the deployment status of the NBI inventory file
Remarks None

U2000

configuration database interface
Item Verifying the deployment status of the NBI configuration database
interface
Check ID 450044
Applicatio SUSE
n System

NBI configuration database interface.
Standard : Check the configuration in
$IMAP_ROOT/etc/CMExport/ModuleDef.xml.
Info/log file : N/A
deployment status of the NBI configuration database
interface."
Status : WARNING
Verify the deployment status of the NBI configuration
database interface. If the analysis results include this
Remarks None

U2000
4.3.15 450043_ Verifying whether the NBI CME file interface uses
the CORBA interface
Item Verifying whether the NBI CME file interface uses the CORBA interface
Check ID 450043
Applicatio SUSE
n System

Description : Check whether the NBI CME file
interface uses the CORBA interface.
$IMAP_ROOT/etc/IRPService/itf_n_config.xml.
Info/log file : N/A
Detail : 450043-200: "Failed to check
whether the NBI CME file interface uses the CORBA
interface."
Status : WARNING
Verify whether the NBI CME file interface uses the
CORBA interface. If the analysis results include this
Remarks None

U2000
4.3.16 450042_ Verifying the compression type of files exported

from the NBI CME file interface
Item Verifying the compression type of files exported from the NBI CME file
interface
Check ID 450042
Applicatio SUSE
n System

Description : Check the compression type of files
exported from the NBI CME file interface.
Standard : Check the compression type of files
exported in $IMAP_ROOT/var/fileint/cm/0.
Info/log file : N/A
Detail : 450042-200: "Failed to check the
compression type of files exported from the NBI CME file
interface."
Status : WARNING
Verify the compression type of files exported from the
NBI CME file interface. If the analysis results include this
Remarks None

U2000
CME file interface
Item Verifying the type of files exported from the NBI CME file interface
Check ID 450041
Applicatio SUSE
n System

the NBI CME file interface.
$IMAP_ROOT/var/fileint/cm/0.
Info/log file : N/A
of files exported from the NBI CME file interface."
Status : WARNING
Verify the type of files exported from the NBI CME file
Remarks None

U2000
4.3.18 450040_ Verifying the deployment status of the NBI CME

file interface
Item Verifying the deployment status of the NBI CME file interface
Check ID 450040
Applicatio SUSE
n System

NBI CME file interface.
$IMAP_ROOT/var/fileint/cm/0.
Info/log file : N/A
deployment status of the NBI CME file interface."
Status : WARNING
Verify the deployment status of the NBI CME file
Remarks None

U2000
4.3.19 450039_ Verifying the file export mode of the NBI

configuration file interface
Item Verifying the file export mode of the NBI configuration file interface
Check ID 450039
Applicatio SUSE
n System

Description : Get the file export mode of the NBI
configuration file interface.
$IMAP_ROOT/etc/CMExport/NbiDataExportPara.xml.
Info/log file : N/A
Detail : 450039-200: "Failed to get the file
export mode of the NBI configuration file interface."
Status : WARNING
Verify the file export mode of the NBI configuration file
Remarks None

U2000

from the NBI configuration file interface
Item Verifying the compression type of files exported from the NBI
Check ID 450038
Applicatio SUSE
n System

Description : Get the compression type of files
exported from the NBI configuration file interface.
$IMAP_ROOT/etc/CMExport/NbiDataExportPara.xml.
Info/log file : N/A
compression type of files exported from the NBI
configuration file interface."
Status : WARNING
NBI configuration file interface. If the analysis results
Remarks None

U2000
Item Verifying the type of files exported from the NBI configuration file
interface
Check ID 450037
Applicatio SUSE
n System

the NBI configuration file interface.
$IMAP_ROOT/var/fileint/cm/autoExport.
Info/log file : N/A
of files exported from the NBI configuration file
interface."
Status : WARNING
Verify the type of files exported from the NBI
configuration file interface. If the analysis results include
this alarm, the required information is not collected.
Remarks None

U2000

Item Verifying the deployment status of the NBI configuration file interface
Check ID 450036
Applicatio SUSE
n System

NBI configuration file interface.
$IMAP_ROOT/var/fileint/cm/autoExport.
Info/log file : N/A
deployment status of the NBI configuration file interface."
Status : WARNING
Verify the deployment status of the NBI configuration file
Remarks None

U2000
4.3.23 450035_ Verifying the deployment status of the NBI alarm

database interface
Item Verifying the deployment status of the NBI alarm database interface
Check ID 450035
Applicatio SUSE
n System

NBI alarm database interface.
Standard : Check the existance of AutoCfg and
its right for fmdb.
Info/log file : N/A
deployment status of the NBI alarm database interface."
Status : WARNING
Verify the deployment status of the NBI alarm database
Remarks None

U2000

SNMP interface
Item Verifying the deployment status of the NBI alarm SNMP interface
Check ID 450032
Applicatio SUSE
n System

NBI alarm SNMP interface.
Standard : Check the status of SnmpAgent and
the configuration of nms users in snmpagent.xml.
Info/log file : N/A
deployment status of the NBI alarm SNMP interface."
Status : WARNING
Verify the deployment status of the NBI alarm SNMP
Remarks None

U2000

CORBA alarm interface
Item Verifying the deployment status of the NBI CORBA alarm interface
Check ID 450026
Applicatio SUSE
n System

NBI CORBA alarm interface.
Standard : Check the existence of
$IMAP_ROOT/etc/IRPService/itf_n_config.xml.
Info/log file : N/A
deployment status of the NBI CORBA alarm interface."
Status : WARNING
Verify the deployment status of the NBI CORBA alarm
Remarks None

U2000

from the NBI alarm file interface
Item Verifying the compression type of files exported from the NBI alarm file
interface
Check ID 450024
Applicatio SUSE
n System

exported from the NBI alarm file interface.
Standard : Get the compression type of files
exported in $IMAP_ROOT/var/fileint/fm.
Info/log file : N/A
compression type of files exported from the NBI alarm
file interface."
Status : WARNING
NBI alarm file interface. If the analysis results include this
Remarks None

U2000
alarm file interface
Item Verifying the type of files exported from the NBI alarm file interface
Check ID 450023
Applicatio SUSE
n System

the NBI alarm file interface.
Standard : Check the type of NBI alarm file in
$IMAP_ROOT/var/fileint/fm.
Info/log file : N/A
of files exported from the NBI alarm file interface."
Status : WARNING
Verify the type of files exported from the NBI alarm file
Remarks None

U2000

file interface
Item Verifying the deployment status of the NBI alarm file interface
Check ID 450022
Applicatio SUSE
n System

NBI alarm file interface.
Standard : Check the NBI alarm file in
$IMAP_ROOT/var/fileint/fm.
Info/log file : N/A
deployment status of the NBI alarm file interface."
Status : WARNING
Verify the deployment status of the NBI alarm file
Remarks None

U2000
4.3.29 450020_ Verifying the performance counter interconnection

mode of the NBI performance file interface based on
measurement units
Item Verifying the performance counter interconnection mode of the NBI
performance file interface based on measurement units
Check ID 450020
Applicatio SUSE
n System

Description : Get the performance counter
interconnection mode of the NBI performance file
interface based on measurement units.
PMExpParam.xml.
Info/log file : N/A
performance counter interconnection mode of the NBI
performance file interface based on measurement units."
Status : WARNING
Verify the performance counter interconnection mode of
the NBI performance file interface based on measurement
units. If the analysis results include this alarm, the
Remarks None

U2000

from the NBI performance file interface based on measurement
units
Check ID 450019
Applicatio SUSE
n System

exported from the NBI performance file interface based
on measurement units.
PMExpParam.xml.
Info/log file : N/A
performance file interface based on measurement units."
Status : WARNING
NBI performance file interface based on measurement
units. If the analysis results include this alarm, the
Remarks None

U2000
Item Verifying the type of files exported from the NBI performance file
interface based on measurement units
Check ID 450018
Applicatio SUSE
n System

the NBI performance file interface based on measurement
units.
Standard : Check the type of the NBI
performance file in $IMAP_ROOT/var/fileint/pm.
Info/log file : N/A
of files exported from the NBI performance file interface
based on measurement units."
Status : WARNING
Verify the type of files exported from the NBI
performance file interface based on measurement units. If
support engineers.
Remarks None

U2000

Item Verifying the deployment status of the NBI performance file interface
based on measurement units
Check ID 450017
Applicatio SUSE
n System

NBI performance file interface based on measurement
units.
Standard : Check NBI performance file in
$IMAP_ROOT/var/fileint/pm.
Info/log file : N/A
deployment status of the NBI performance file interface
based on measurement units."
Status : WARNING
Verify the deployment status of the NBI performance file
interface based on measurement units. If the analysis
Remarks None

U2000
4.3.33 450016_ Verifying the performance counter interconnection

mode of the NBI performance file interface based on NEs
Item Verifying the performance counter interconnection mode of the NBI
performance file interface based on NEs
Check ID 450016
Applicatio SUSE
n System

Description : Get the performance counter
interconnection mode of the NBI performance file
interface based on NEs.
Standard : Check configuration in
$IMAP_ROOT/etc/MediationService/MedExpParam.xml.
Info/log file : N/A
performance counter interconnection mode of the NBI
performance file interface based on NEs."
Status : WARNING
Verify the performance counter interconnection mode of
the NBI performance file interface based on NEs. If the
support engineers.
Remarks None

U2000

from the NBI configuration file interface
Check ID 450015
Applicatio SUSE
n System

exported from the NBI configuration file interface.
Standard : Check configuration in
$IMAP_ROOT/etc/MediationService/MedExpParam.xml.
Info/log file : N/A
performance file interface based on NEs."
Status : WARNING
NBI configuration file interface. If the analysis results
Remarks None

U2000

performance file interface based on NEs
Item Verifying the deployment status of the NBI performance file interface
based on NEs
Check ID 450014
Applicatio SUSE
n System

NBI performance file interface based on NEs.
Standard : Check data in
itfndb..tbl_MedExportMeas.
Info/log file : N/A
deployment status of the NBI performance file interface
based on NEs."
Status : WARNING
Verify the deployment status of the NBI performance file
interface based on NEs. If the analysis results include this
Remarks None

U2000
4.4 Severe Fault Quick Rectification Information

4.4.1 220021_Verifying That the OS Backup Is Available
Item Verifying that the OS backup is available
Check ID 220021
Applicatio SUSE
n System

Description : check if the server has operating
system backup.
Standard : Collect system backup info
through entering information at foreground.
Info/log file :
Detail : 220021-101: "The input contains
no characters."
Status : INFO
Query environment variables to verify that the static data
backup is available. If the analysis results include this
alarm, it illuminate do not input the information about this
item.
Check ID : 220021-200
Description : check if the server has operating
system backup.
Standard : Collect system backup info
Info/log file :
operating system backup."
Status : WARNING
Query environment variables to verify that the OS backup
is available. If the analysis results include this alarm, the
Remarks None

U2000
4.4.2 220022_Verifying That the Static Data Backup Is Available

Item Verifying that the static data backup is available
Check ID 220022
Applicatio SUSE
n System

Description : check if the server has static data
backup.
Standard : Collect static data backup info
Info/log file :
Detail : 220022-101: "The input contains
no characters."
Status : INFO
alarm, it illuminate do not input the information about this
item.
Check ID : 220022-200
Description : check if the server has static data
backup.
Standard : Collect static data backup info
Info/log file :
static data backup."
Status : WARNING
Remarks None

Health Check PDF

Uploaded by

Document Information

Original Title

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

Health Check PDF

Uploaded by

Copyright:

Available Formats

U2000

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. i

1 SUSE Verification Items .............................................................................................................. 1

2 Common Verification Items...................................................................................................... 35

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. ii

2.1.1 400000_Verifying the OSS Software Version ....................................................................................... 36

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. iii

2.6 S3900 Array Verification Items .................................................................................................................... 107

3 Service Module Verification Items ........................................................................................ 130

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. iv

3.2.16 422024_Check the big moi tables of omcdb ..................................................................................... 166

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. v

4 Inventory Data Collection Verification Items ..................................................................... 216

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. vi

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. vii

1 SUSE Verification Items

1.1 Operating System (Linux)

Detailed 210004-200 1. Alarm item

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 1

210004-201 1. Alarm item

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 2

1.1.2 210006_Verifying the Available Memory

Detailed 210006-200 1. Alarm item

1.1.3 230001_Verifying the Status of the FTP Service

Detailed 230001-201 1. Alarm item

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 3

FTP services on the server and check whether the

1.1.4 230006_Verifying the Disk Mirror Status

Application SUSE ia64

Detailed 230006-200 1. Alarm item

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 4

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 5

Send the command output to Huawei technical support

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 6

/dev/md0 and /dev/md1 files comply with

Remarks Only support HP rx7640 midrange computer

1.1.5 230008_Verifying the SUSE OS Version

Detailed 230008-200 1. Alarm item

1.1.6 230011_Verifying the OS logs

Detailed 230011-101 1. Alarm item

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 7

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 8

1.1.7 500006_Check the IO speed of file system

Detailed 500006-200 1. Alarm item

1.1.8 500007_Check disk array monitor configuration

Detailed 500007-200 1. Alarm item

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 9

Remarks The ATAE Cluster networking is not supported.

1.1.9 500009_Check OSS backup status

Detailed 500009-400 1. Alarm item

1.1.10 500015_Check Precaution

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 10

Detailed 500015-200 1. Alarm item

Precise Precaution List:

Precaution Notice-NTP Vulnerabilities in the Operating Systems of the

Precaution Notice-GLIBC Vulnerabilities in the Operating Systems of

Precaution Notice-NTP Vulnerabilities in the Operating Systems of the

Issue 04 (2019-02-15) Copyright © Huawei Technologies Co., Ltd. 11

Vague Precaution List:

1.1.11 500020_Check server IP conflict