Eran Routine Maintenace Guide

eRAN Routine Maintenance Guide Page 1 of 35
eRAN Routine Maintenance Guide

Purpose
This document provides guidelines for the routine maintenance of an eNodeB, which involves 7x24, daily, weekly, and monthly maintenance operations. The
document also provides data sheets for recording the routine maintenance operations.
Product Version
The following table lists the product versions related to this document.
Product Name Solution Version Product Version

BTS3900 SRAN10.1 V100R010C10
BTS3900A
eRAN8.1
BTS3900L
eRAN TDD 8.1
BTS3900AL
DBS3900
DBS3900 LampSite
BTS3202E
Related Product Version
Related Product Name Product Version

U2000 iManager U2000 V200R015C01 and later versions.
Intended Audience
This document is intended for:
Shift operators
System engineers
Organization
Changes in the eRAN Routine Maintenance Guide

The following describes the changes in eRAN Routine Maintenance Guide.
Overview of eRAN Routine Maintenance
This chapter describes the scope of, tools for, and items and periods for eRAN routine maintenance. The eRAN routine maintenance ensures that the eNodeB
maintains high reliability and meets service requirements with best performance. Routine maintenance helps locate and rectify faults promptly.
7x24 Monitoring Operations
This chapter describes the 7x24 monitoring items and operations of an eNodeB. 7x24 stands for 7 days a week and 24 hours a day, which indicates round-the-
clock monitoring. 7x24 monitoring aims at monitoring fault alarms.
Daily Maintenance Operations
This chapter describes the daily maintenance items and operations of an eNodeB. Daily maintenance items involve monitoring equipment status, checking
busy-hour performance, and checking the connection status between the U2000 and NEs.
Weekly Maintenance Operations
This chapter describes the weekly maintenance items and operations of an eNodeB. Weekly maintenance items involve backing up the eNodeB configuration
data, preparing weekly reports on network performance, counting top alarms, auditing security logs, checking the voltage standing wave ratio (VSWR), and
checking the equipment transmit power.
Monthly Maintenance Operations
This chapter describes the monthly maintenance items and operations of an eNodeB. Monthly maintenance items involve checking power supply, analyzing
faults and customer complaints, preparing monthly report on the network performance, checking Security Patches for the OMU operating system, checking OS
and database hardening, and checking weak passwords and Others.
Routine Maintenance Data Sheet
An eRAN routine maintenance data sheet is used to record the equipment performance status information during the maintenance.
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
Changes in the eRAN Routine Maintenance Guide

The following describes the changes in eRAN Routine Maintenance Guide.
02 (2015-06-30)
This is the second release.
Compared with issue 01 (2015-03-23) of V100R010C10, this issue does not add topics.
Compared with issue 01 (2015-03-23) of V100R010C10, this issue includes the following changes:
Topic Change Description
Preparing Weekly Reports on Network Performance Updated the method of preparing weekly reports on network performance.
Preparing Monthly Reports on Network Performance Updated the method of preparing monthly reports on network performance.
No information in issue 01 (2015-03-23) of V100R010C10 is deleted from this issue.
01 (2015-03-23)
This is the first release.
file:///C:/Users/david/AppData/Local/Temp/~hh1F11.htm 29-03-2017
Compared with issue Draft A (2015-01-15) of V100R010C10, this issue has no changes.
Draft A (2015-01-15)
This is the Draft A release.
Compared with issue 02 (2014-06-25) of V100R009C00, this issue does not add topics.
Compared with issue 02 (2014-06-25) of V100R009C00, this issue includes the following changes:
Topic Change Description
Checking the Voltage Standing Wave Ratio Updated the information of the Warning dialog box.
No information in issue 02 (2014-06-25) of V100R009C00 is deleted from this issue.
Parent topic: eRAN Routine Maintenance Guide

Overview of eRAN Routine Maintenance

This chapter describes the scope of, tools for, and items and periods for eRAN routine maintenance. The eRAN routine maintenance ensures that the eNodeB
maintains high reliability and meets service requirements with best performance. Routine maintenance helps locate and rectify faults promptly.
Scope of Routine Maintenance
Routine maintenance of the eRAN involves performance monitoring and maintenance of the eNodeB on an U2000 client.
Routine maintenance of the U2000 and local maintenance of the eNodeB are not included in the eNodeB routine maintenance.
For details about the routine maintenance of the U2000, see U2000 Online Help.
For details about maintenance of eNodeBs, see the site maintenance guide of the corresponding eNodeB, for example, BTS3900(Ver.B) Site Maintenance
Guide, BTS3202E Site Maintenance Guide.
For details about maintenance of baseband units (BBUs) and remote radio units (RRUs), see BBU3900 Hardware Maintenance Guide and RRU Hardware
Maintenance Guide.
Tools for Routine Maintenance
The tools for eRAN routine maintenance are the U2000 client and PRS client. An U2000 client is used to simultaneously monitor multiple eNodeBs, manage system
logs, and manage alarms. A PRS client is used to query KPIs on network performance.
NOTE:
The view modes of the U2000 supported by V200R013C00B060 and later versions include the traditional style and application style. The default view mode of the
U2000 is the application style. On the U2000, you can set the view mode to the traditional style by choosing Files > Preferences > Client Display Style >
Traditional Style, clicking OK, and then restarting the U2000 client.
The item of preparing weekly reports on network performance is maintained on a PRS client. The item of analyzing faults and customer complaints can be maintained
on an U2000 client or a PRS client. Other items are maintained on an U2000 client.
Items and Periods for Routine Maintenance
According to the maintenance periods, routine maintenance items can be classified into 7x24 monitoring items, daily maintenance items, weekly maintenance items,
and monthly maintenance items.
Table 1, Table 2, Table 3, and Table 4 list the items and operation references for the 7x24 monitoring, daily maintenance, weekly maintenance, and monthly
maintenance. The items can be added or deleted according to site requirements.
Table 1 eNodeB 7x24 monitoring items

No. Item Applicable Product Reference
1 Monitoring fault alarms BTS3900, BTS3900A, BTS3900L, BTS3900AL, Monitoring Fault Alarms
DBS3900, BTS3202E
Table 2 Daily maintenance items of an eNodeB
1 Checking equipment status BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking Equipment Status
DBS3900, BTS3202E
2 Checking busy-hour performance BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking Busy-Hour Performance
DBS3900, BTS3202E
3 Checking the Connection Status Between the BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking the Connection Status Between the
U2000 and NEs DBS3900, BTS3202E U2000 and NEs
Table 3 Weekly maintenance items of an eNodeB
1 Backing up the eNodeB configuration data BTS3900, BTS3900A, BTS3900L, BTS3900AL, Backing Up the eNodeB Configuration Data
DBS3900, BTS3202E
2 Preparing weekly reports on network BTS3900, BTS3900A, BTS3900L, BTS3900AL, Preparing Weekly Reports on Network
performance DBS3900, BTS3202E Performance
3 Counting top alarms BTS3900, BTS3900A, BTS3900L, BTS3900AL, Counting Top Alarms
DBS3900, BTS3202E
4 Auditing security logs BTS3900, BTS3900A, BTS3900L, BTS3900AL, Auditing Security Logs
DBS3900, BTS3202E
5 Checking the voltage standing wave ratio BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking the Voltage Standing Wave Ratio
(VSWR) DBS3900, BTS3202E
6 Checking the equipment transmit power BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking the Equipment Transmit Power
DBS3900, BTS3202E
Table 4 Monthly maintenance items of an eNodeB
1 Checking power supply BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking Power Supply
and DBS3900
2 Analyzing faults and customer complaints BTS3900, BTS3900A, BTS3900L, BTS3900AL, Analyzing Faults and Customer Complaints
DBS3900, BTS3202E
3 Preparing monthly reports on network BTS3900, BTS3900A, BTS3900L, BTS3900AL, Preparing Monthly Reports on Network
performance DBS3900, BTS3202E Performance
4 Checking Security Patches for the OMU BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking Security Patches for the OMU
Operating System DBS3900, BTS3202E Operating System
5 Checking OS and Database Hardening BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking OS and Database Hardening
DBS3900, BTS3202E
6 Checking Weak Passwords and Others BTS3900, BTS3900A, BTS3900L, BTS3900AL, Checking Weak Passwords and Others
DBS3900, BTS3202E

7x24 Monitoring Operations

This chapter describes the 7x24 monitoring items and operations of an eNodeB. 7x24 stands for 7 days a week and 24 hours a day, which indicates round-the-clock
monitoring. 7x24 monitoring aims at monitoring fault alarms.
Monitoring Fault Alarms

All the current fault alarms of an eNodeB can be monitored on the U2000 client to clear the alarms and to rectify the faults as soon as possible. The systems to
be monitored involve the power, environment, signaling, trunk, hardware, and software systems.

Monitoring Fault Alarms

All the current fault alarms of an eNodeB can be monitored on the U2000 client to clear the alarms and to rectify the faults as soon as possible. The systems to be
monitored involve the power, environment, signaling, trunk, hardware, and software systems.
Prerequisites
The U2000 client is properly connected to the U2000 server.

The permission for querying alarms is obtained.
Procedure
1. From the main menu of the U2000 client, choose Fault Management > Browse Alarm > > Query Alarm Logs (application style) or Monitor > Browse
Current Alarm (traditional style).
The Filter dialog box is displayed.
2. Set the filter criteria in the Filter dialog box, as shown in Figure 1. In this step, click All in the Type area.
Figure 1 Setting filter criteria
3. Click OK to query the alarms that meet the filtering criteria. The information about all the alarms is displayed in the Browse Current Alarm window.
NOTE:
When an alarm is selected, the following information is displayed:
The information about the alarm is displayed in the Details pane.
The hyperlink is displayed in the Handling Suggestions pane, by clicking which the handling suggestion for the alarm can be obtained.
4. Double-click an alarm. In the displayed Details dialog box, you can view detailed information about the alarm.
5. Instruct engineers responsible for the equipment where uncleared alarms are generated to handle the alarms, and analyze and acknowledge the alarms that are
automatically cleared.
6. Click Experience at the lower part of the Details dialog box, you can record the symptom, cause, and handling suggestion for an alarm.
7. Repeat 4 through 6 to handle each alarm until all the fault alarms are cleared.
NOTE:
It is recommended that the daily operations for counting alarms be set as a template for future use. To create a template, do as follows:
a. On the lower left of the Browse Current Alarm dialog box, choose Template > New.
b. Enter a name for the template and choose Yes or No from the Share drop-down list, and click Next.
c. Set the filter criteria, and click Finish.
d. In the Confirm dialog box, click Yes. The template is saved, and current fault alarms are filtered based on the template.
8. (Optional) Set communication parameters for sending emails or short message service (SMS) notifications.
Perform this step if fault alarms need to be reported to maintenance engineers by sending emails or SMS notifications, and communication parameters
related to emails or SMS notifications are not set.
Maintenance engineers cannot monitor the alarms 24 hours a day on the U2000 client. Therefore, the function of remote notification on the U2000
enables faults alarms to be reported to the engineers through emails or SMS notifications in real time.
a. From the main menu of the U2000 client, choose Fault Management > Alarm Setting > Remote Notification (application style) or Monitor > Alarm
Setting > Remote Notification (traditional style). The Remote Notification tab page is displayed.
b. At the lower left corner on the Remote Notification tab page, choose Setting > Communication Device Settings.
c. In the displayed Communication Device Settings dialog box, click Add.
d. In the Add Communication Device dialog box, enter the alias of the device, select the type of the sending device, and then click Next, as shown in
Figure 2.
NOTE:
Each device can be added once. You cannot add a device that is already configured.
Figure 2 Add Communication Device dialog box (1/2)
e. In the Add Communication Device dialog box shown in Figure 3, set the parameters as listed in Table 1. Then, click Finish.
The Add Communication Device dialog box is closed.

Figure 3 Add Communication Device dialog box (2/2)
Table 1 Communication parameters for setting emails and SMS notifications

Type Parameter Description
Email Host Name or IP Address Specifies the host name or IP address of the Simple Mail Transfer Protocol (SMTP) server.
of SMTP NOTE:
The U2000 server may fail to connect to the SMTP server due to the failure of domain name
resolution. To prevent this problem, it is recommended that the IP address of the SMTP server
be used.
Address of Sender Specifies the email address of the sender.
Enable Check Right Specifies whether to provide the user name and password of the SMTP server. If the SMTP
server requires to verify the right, select the Enable Check Right check box.
User Name of SMTP Specifies the user name of the SMTP server for right permission.
Sender Password Specifies the password of the SMTP server for right permission.
Encoding Specifies an email encoding format, such as, UTF-8 or GBK.
Send by Server Specifies whether to send the emails through the U2000 server.
Test on Server Specifies whether to test the email sending on the U2000 server.
Click Test on Server. In the displayed Email Notification Test dialog box, enter an email
address in the Email address for receiving test emails text box and then click Test. If the
displayed information indicating that emails are successfully sent, the parameters are correctly
set.
SSL Specifies whether to enable the function of SSL encryption.
Enable Specifies whether to enable the function of email notification.
Communication Host name or IP Specifies the host name or IP address of the SMS center.
parameters for SMS
notifications User Name Specifies the user name for logging in to the SMS center.
Password Specifies the password for logging in to the SMS center.
Code Protocol Specifies the code protocol of the SMS center.
Port Specifies the port number of the SMS center.
Send by Server Specifies whether to send the SMS notification through the U2000 server.
Test on Server Specifies whether to test the SMS notification sending on the U2000 server.
NOTE:
Enter the mobile phone number of a maintenance engineer in the Phone number for
receiving test SMS notifications text box. The phone number must contain the mobile
country code (MCC), such as, +86 is the MCC of China for the phone number
+8613800755500.
The phone number can have a maximum of 26 characters.
If the displayed information indicating that SMS notifications are successfully sent, the
parameters are correctly set.
Enable Specifies whether to enable the function of SMS notification.
f. In the Communication Device Settings dialog box, click Close.

g. At the lower left corner on the Remote Notification tab page, choose Setting > Message Format Settings.
h. In the displayed Message Format Settings dialog box, set the format of emails or SMS notifications as listed in Table 2 and click OK, as shown in
Figure 4.
Figure 4 Message Format Settings dialog box
Table 2 Parameters for email content and SMS content

Type Parameter Description
Email content Email subject Specifies a subject for the remote notification email.
Message head Specifies a prefix that is added before every alarm information in the email.
Message end Specifies a suffix that is added after every alarm information in the email.
Subtitle Specifies one or more subtitles as the additional information of the email subject.
Example Specifies an example of selected subtitles.
Email Content Setting Specifies the alarm fields to be contained in the email.
SMS content Message head Specifies a suffix that is added before every alarm information in the SMS
notification.
Message end Specifies a suffix that is added before every alarm information in the SMS
notification.
SMS Content Setting Specifies the alarm fields to be contained in the SMS notification.
i. At the lower left corner on the Remote Notification tab page, choose Setting > Delay Time.
j. In the displayed Delay Time dialog box, enter the delay time in the Delay time(min) spin box and then click OK.
A remote notification message is sent if the alarm is not cleared after the delay time expires. If the alarm is cleared, no remote notification message is
sent.
9. (Optional) Set alarms to be notified.
Perform this step when fault alarms need to be reported to maintenance engineers by sending emails or SMS notifications.
a. At the lower right corner on the Remote Notification tab page, choose Add > Alarm Notification Rule.
b. On the Basic Settings tab page of the Add Alarm Remote Notification Rule-Filter Criteria dialog box, set the severity, status, and type of the alarms
to be notified.
c. Click the Alarm Source tab, set the objects generating alarms. Then, click Next.
All objects: Select all objects.

Custom: Click Add at the lower right corner to customize objects generating alarms.
d. In the Add Alarm Remote Notification Rule-Notification Time dialog box, set the time at which the remote notification is sent and the time zone of the
receiver and then click Next.
e. In the Add Alarm Remote Notification Rule-Notification Address dialog box, enter the email addresses or phone numbers for receiving notifications.
Then, click Finish.
The U2000 sends the filtered alarms to receivers based on the settings by using emails or SMS notification.
Follow-up Procedure
If the alarm 26266 Time Synchronization Failure is reported, it is recommended that this alarm be cleared as soon as possible to prevent the impacts on the
monitoring of eNodeBs on the U2000 and the services carried on the eNodeBs.
If there are other alarms, rectify the related fault by referring to Procedure for this alarm in 3900 Series Base Station Alarm Reference, BTS3202E Alarm Reference.
Parent topic: 7x24 Monitoring Operations

Daily Maintenance Operations

This chapter describes the daily maintenance items and operations of an eNodeB. Daily maintenance items involve monitoring equipment status, checking busy-hour
performance, and checking the connection status between the U2000 and NEs.
Checking Equipment Status

Whether the equipment status is normal is checked on the U2000 client based on an NE health check (NHC) report. NE is short for network element.
Checking Busy-Hour Performance
This section describes how to determine the eNodeB performance based on the KPIs in busy hours queried on the U2000 client.
Checking the Connection Status Between the U2000 and NEs
This section describes how to check the connection status between the U2000 and NEs.

Checking Equipment Status

Whether the equipment status is normal is checked on the U2000 client based on an NE health check (NHC) report. NE is short for network element.
Prerequisites

The U2000 server properly communicates with the eNodeB.
NOTE:
The BTS3202E does not support humidity check during the environment status check.
Procedure
1. From the main menu of the U2000 client, choose Trace and Maintenance > Monitor > NE Health Check (application style) or Maintenance > Network
Health Check > NE Health Check (traditional style).
2. Click on the toolbar of the NE Health Check tab page.
3. Perform the following operations in the displayed Create Task dialog box.
a. Select Maintenance from the Scenario drop-down list.

b. Enter a name in the Task Name text box.
c. Select NEs to be checked in the Select NE area.
d. Click the Periodic option button in the Time Setting area.
e. Click Next.
Figure 1 shows the Create Task dialog box.
Figure 1 Create Task dialog box
4. Set health check period for the task and then click Finish, as shown in Figure 2.
Figure 2 Setting time and period for a task
5. After the task is complete, click Finished Tasks in the left-pane of the NE Health Check tab page.
6. Right-click the finished task and choose View Report from the shortcut menu.
7. In the displayed Health Check Report dialog box, select a report format by click the HTML Format or DOC Format tabs. Then, click Open to open the
report or click Save As to save the report onto a local disk.
NOTE:
The report in HTML format shows the statistics of check items that fail to pass the check, pass the check, or are manually checked. The report in an HTML
format is recommended because it is easy to read.
Figure 3 shows a health check report in HTML format.
Figure 3 Health check report
Follow-up Procedure
In NE Health Check Report, ensure that Not Passed and Failed to Execute are both 0. Manually check all check items listed in Manually Checked and ensure that
all check items succeed.
The detailed assessment is as follows:
Product type check: The product type is correct.

eNodeB software version check: The software version status is normal.
Cell state check: The cell status is normal.
Ethernet port properties check: The status of every port, link, and interface is normal.
Clock state check: The clock status is normal.
Environment status check: The temperature and humidity are normal.
Hardware status check: The board status, board central processing unit (CPU), and storage space usage are normal. The RF channels are enabled.
Config data consistent check: The configuration data is consistent with the actual operation data.
In an NE health check report, the number of Not Passed and Failed to Execute items must be 0, and the check items in Manually Checked must be checked and
pass the check.
If the numbers of Not Passed and Failed to Execute items are not 0, perform the following operations:
1. Click the hyperlink in the corresponding box. For example, if the number of the Failed to Execute items is not 0, click the hyperlink in the box under the
Failed to Execute item.
2. In the displayed check sub item list, click the check sub item one by one and rectify the fault based on Solution.
Figure 4 shows the detailed result of a check sub item.
Figure 4 Detailed result of a check sub item
3. Perform the check task again.
Right-click the task by clicking NE Health Check > Finished Tasks. Choose Restart.
If the number of Not Passed and Failed to Execute items is still 0, continue rectifying the fault until the number is 0.
If the number of Manually Checked is not 0, perform the following operations:
1. Click the hyperlink in the box under Manually Checked.

2. In the displayed check sub item list, click the check sub item one by one. Check the sub item manually based on Solution and ensure that the sub item pass the
check.
Parent topic: Daily Maintenance Operations

Checking Busy-Hour Performance

This section describes how to determine the eNodeB performance based on the KPIs in busy hours queried on the U2000 client.
Prerequisites
The KPIs to be queried and related reference standards are determined.

Procedure
1. From the main menu of the U2000 client, choose Performance > Measurement > Measurement Management (application style) or Performance >
Measurement Management (traditional style).
2. In the left-pane of the Measurement Management tab page, right-click the measurement item to be queried, and choose Query Result from the shortcut
menu, as shown in Figure 1.
Figure 1 Selecting measurement item
3. Select objects on the Object tab page, as shown in Figure 2.
Figure 2 Selecting objects
4. On the Counter tab page, select the performance counters to be queried, as shown in Figure 3.
Figure 3 Selecting counters
5. On the Time tab page, set other parameters such as query time and period, as shown in Figure 4.
Figure 4 Setting time parameters
6. After all the settings are complete, click Query.
NOTE:
Click Save at the lower right corner, and select a format for saving the query result. The query result is saved in .xls format by default.
7. Analyze the statistical result, and evaluate the eNodeB performance.
Follow-up Procedure
Provide the network performance report and ensure that counter values are not less than the corresponding values specified in busy hours.
Identify performance counters whose values do not meet the performance requirements, and submit these counters to network planning and optimization engineers for
further analysis.
Checking the Connection Status Between the U2000 and NEs

This section describes how to check the connection status between the U2000 and NEs.
Prerequisites

The permission for related operations is obtained.
Procedure
1. Choose Configuration > Browser > NE Monitor(application style) or System > NE Monitor (traditional style). The NE Monitor dialog box is displayed.
You can query the connection status of NEs. The connection status includes Normal and Offline. As shown in Figure 1.
Figure 1 NE Monitor
Follow-up Procedure
When NEs are in Normalstate, they are properly connected to the U2000.
When the U2000 and an NE version mismatch, NEs of this version are in Offline state. In this situation, query the NE version and install the NE version-specific
mediation on the U2000 server. For details, see the U2000 commissioning guide or contact Huawei technical support.

Weekly Maintenance Operations

This chapter describes the weekly maintenance items and operations of an eNodeB. Weekly maintenance items involve backing up the eNodeB configuration data,
preparing weekly reports on network performance, counting top alarms, auditing security logs, checking the voltage standing wave ratio (VSWR), and checking the
equipment transmit power.
Backing Up the eNodeB Configuration Data

The eNodeB configuration data can be automatically or manually backed up on the U2000 client. Automatic backup can be periodically performed and
therefore applies to periodic tasks, and manual backup applies to other tasks. For routine maintenance tasks, automatic backup is recommended.
Preparing Weekly Reports on Network Performance
Counting Top Alarms
eNodeB alarms can be counted on an U2000 client. Analyzing top alarms helps know the severity and quantity distribution of top alarms in a week, facilitating
network quality analysis, fault diagnosis, and threat prevention.
Auditing Security Logs
Security logs record security-related operations, such as login and password changes. You must query and audit security logs on an U2000 client every week to
check whether system operations are authorized.
Checking the Voltage Standing Wave Ratio
The antennas working with a high VSWR can be located and rectified by checking the VSWR. Therefore, cell coverage decrease or cell unavailability caused
by a high VSWR can be prevented.
Checking the Equipment Transmit Power
You can estimate and adjust the equipment status by checking the radio frequency (RF) transmit (TX) power on the U2000 client.

Backing Up the eNodeB Configuration Data

The eNodeB configuration data can be automatically or manually backed up on the U2000 client. Automatic backup can be periodically performed and therefore
applies to periodic tasks, and manual backup applies to other tasks. For routine maintenance tasks, automatic backup is recommended.
Automatically Backing Up eNodeB Configuration Data

This section describes how to automatically back up eNodeB configuration data on an U2000 client based on a specified period.
Manually Backing Up eNodeB Configuration Data
This section describes how to manually back up eNodeB configuration data by using graphical user interface (GUI) or man-machine language (MML)
commands on an U2000 client.
Parent topic: Weekly Maintenance Operations

Automatically Backing Up eNodeB Configuration Data

This section describes how to automatically back up eNodeB configuration data on an U2000 client based on a specified period.
Prerequisites

Procedure
1. From the main menu of the U2000 client, choose System Management > Task Schedule > Task Management (application style) or Maintenance > Task
Management (traditional style).
2. In the lower right of the Task Management dialog box, click New.
3. In the displayed New Task dialog box, set Task Name, set Task Type to Backup > NE Backup, and Execution Type to Periodic, and then click Next.
4. Set Execution interval to 1 in the unit of Weeks, set other parameters as required, and click Next, as shown in Figure 1.
Figure 1 Setting the time and period
5. Perform the following operations in the dialog box shown in Figure 2:
a. Set Backup Type to determine the range of NEs whose data is to be backed up.
b. If it is set to By NE Type or Specified NEs, click Select, the corresponding dialog box is displayed. After the NE type or NE whose data is to be backed
up is selected, click OK.
The dialog box shown in Figure 2 is displayed. Figure 3 shows the displayed dialog box when By NE Type is selected.
c. Click Finish.
The Task Management dialog box is displayed.
NOTE:
File Path is specified by the system and cannot be changed.
Figure 2 Setting the NE range
Figure 3 Selecting an NE
6. In the left pane, choose Task Type > Backup > NE Backup, and then in the task list of the right pane, view the execution of the created task.
NOTE:
When Progress is 100%, the task in this period is executed. When Execution Result is Successful, the data backup in this period is successful.
Follow-up Procedure
If Execution Result is displayed as Partly Successful or Failed, the backup of some or all NEs fails. You can query the NEs whose data fails to be backed up and the
failure causes in the Result Information area of the Task Management dialog box. Then, check whether there is a transmission-related alarm or an alarm related to
disconnection between the U2000 and the NE in the alarm log. If an alarm is generated, there is an icon on the NE.
If any alarm is generated, instruct the transmission network maintenance engineer or NE maintenance engineer to rectify the fault. After the fault is rectified,
back up data again.
If no alarm is generated, back up data again. If the task still fails, contact Huawei technical support engineers.
Restoring Configuration Data
Perform the following operations if data needs to be restored:
1. From the main menu of the U2000 client, choose Software Management > NE File > NE Backup (application style) or Maintenance > Backup
Management > NE Backup (traditional style).
2. Perform the following operations in the NE Backup dialog box:
a. From the navigation tree on the right, select eNodeB.
b. From the navigation tree, select the NE whose data needs to be restored.
c. In the NE Backup List area on the right, select a backup file, click Restore on the lower right under NE Backup List, as shown in Figure 4.
Figure 4 Restoring configuration data
Parent topic: Backing Up the eNodeB Configuration Data

Manually Backing Up eNodeB Configuration Data

This section describes how to manually back up eNodeB configuration data by using graphical user interface (GUI) or man-machine language (MML) commands on
an U2000 client.
Prerequisites

The permission for related operations is obtained.
If MML commands are used, the MML command configuration file corresponding to the current network element (NE) version has been downloaded.
Context
eNodeB configuration data can be manually backed up in either of the following modes:
In GUI mode: Configuration data of multiple eNodeBs can be simultaneously backed up in a simple and direct manner.
In MML command mode: Configuration data of a single eNodeB can be uploaded to the FTP server for backup.
Procedure
In GUI mode
Management > NE Backup (traditional style). The NE Backup dialog box is displayed.
2. From the navigation tree of the left of the NE Backup dialog box, select eNodeB, and then select the eNodeB whose data is to be backed up, as shown in
Figure 1.
NOTE:
You can select multiple eNodeBs for backup during the same session.
Figure 1 Selecting an eNodeB
3. Click Backup.
4. In the displayed Confirm dialog box, click Yes.
The backup task is displayed on the lower part of the NE Backup dialog box.
If Status is Completed, the task is complete. If Information is Succeeded, the task is successfully executed, as shown in Figure 2.
Figure 2 Backup result
In MML command mode

1. From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > MML Command (application style) or Maintenance >
MML Command (traditional style).
2. In the MML Command window, select the LTE NE type from the drop-down list above the navigation tree and then select an NE from the navigation
tree.
NOTE:
You can select multiple NEs of the same NE version.
If the corresponding MML command configuration file has not been downloaded. A dialog box indicating whether to download MML command
configuration file is displayed after an NE is selected. Click Yes. In the displayed Download dialog box, click OK after the downloading is complete.
3. On the right of the MML Command window, run the BKP CFGFILE command to generate a backup file.
4. Run the ULD CFGFILE command to upload the backup file to the FTP server.
NOTE:
Set Server IP to the IP address of the U2000 server, FTP User Name to the FTP user name of the U2000 server (which is ftpuser by default), and FTP
Password to the FTP password of the U2000 server (which is ftpuser by default).
You cannot select multiple NEs when uploading files. You must upload each file to a unique save path. If the save paths are the same for these NEs, an
earlier backup file will be replaced by a later backup file. Therefore, you are advised to name the save paths by backup time, for example,
C:/bak/20110110 or C:/bak/20110115.
After the uploading is complete, you can use the FTP client software to view the eNodeB configuration file in the save paths.
Follow-up Procedure
If data backup fails, check whether there is a transmission-related alarm or an alarm related to disconnection between the U2000 and the NE in the alarm log. If an
alarm is generated, there is an icon on the NE.
If any alarm is generated, instruct the transmission network maintenance engineer or NE maintenance engineer to rectify the fault. After the fault is rectified,
back up data again.
If no alarm is generated, back up data again. If the task still fails, contact Huawei technical support engineers.
Restoring Configuration Data (in GUI Mode)
Management > NE Backup (traditional style).
2. Perform the following operations in the NE Backup dialog box:
a. From the navigation tree on the right, select eNodeB.
b. From the navigation tree, select the NE whose data needs to be restored.
c. In the NE Backup List area on the right, select a backup file, click Restore on the lower right under NE Backup List, as shown in Figure 3.
Figure 3 Restoring configuration data
Restoring Configuration Data (in MML Command Mode)
1. On the left of the MML Command window, select the NE whose data is to be restored.
2. On the right, run the DLD CFGFILE command to download backup file to the NE.
3. After the downloading is complete, run the ACT CFGFILE command to activate the configuration file.
Parent topic: Backing Up the eNodeB Configuration Data

Preparing Weekly Reports on Network Performance

Prepare weekly reports on network performance using the performance surveillance (PRS).
Prerequisites
The PRS performance report management component has been installed.

The PRS client is properly connected to the PRS server.
You have logged in to the PRS client and been granted PRS operation permissions.
Procedure
1. Perform this step only when existing reports do not meet users' query requirements. Prepare a user-defined weekly report.
a. Choose Report > Report Management from the main menu of the PRS client.
b. Perform the following operations as required:
If You Need to... Then...
Create a report directly Perform substep c.
Change the properties of an existing report and save the report Perform substep d.
c. Directly create a user-defined report.
On the displayed Report Management tab page, click .
On the displayed tab page, specify NE type, Object type, Benchmark rule, and Report style.
Select an NE type: Set the vendor and NE type. By default, the first NE type of the first vendor is selected.
Select an object type: By default, the first object type in the object type list is selected.
You can select Sort by click times or Sort alphabetically to sort all object types. By default, Sort by click times is selected.
Select a benchmark rule: Select a benchmark rule from the drop-down list. By default, None is selected.
After the benchmark rules are set, Report style and Time dimension use their default values and the two parameters are not configurable.
Select a report style: Six report styles are available. By default, Time-Object-KPI (TOC) is selected.
Click Select Object. In the displayed dialog box, set the object instance and object attributes.
Select Object tab page: Select an object instance.
You can type a keyword in the search box or use advanced search to quickly locate the required object instance.
Select Object Attribute tab page: Set the object attribute that you want to view in the report.
Click Select KPI. In the displayed dialog box, select one or more KPIs for a subreport.
If Benchmark rule is not set to None, the options Include Benchmark and Only Benchmark can be selected.
If you select Include Benchmark, all KPIs, KPI's Benchmarks, and KPI's Benchmark Deltas are displayed in the left KPI navigation
tree.
NOTE:
KPI's Benchmark: Indicates the benchmark value of a KPI.
KPI's Benchmark Delta: Indicates the difference between the KPI's benchmark value and the actual KPI value.
If you select Only Benchmark, only KPIs that have benchmarks, corresponding Benchmarks, and Benchmark Deltas of such KPIs are
displayed in the left KPI navigation tree.
In the KPI navigation tree, if you double-click a function subset or select a function subset and click , all KPIs, KPI's Benchmarks,
and KPI's Benchmark Deltas under the function subset are added to the right area.
To delete unnecessary KPIs, KPI's Benchmarks, or KPI's Benchmark Deltas from the right area, you can select them and click .
In the right area, you can select a KPI, KPI's Benchmark, or KPI's Benchmark Delta and click or to adjust the
position of the selected object. The column position of the KPI, KPI's Benchmark, or KPI's Benchmark Delta will be changed in the
query result report.
Alternatively, you can select a KPI, KPI's Benchmark, or KPI's Benchmark Delta, and drag the selected object upwards or downwards
to adjust its position.
NOTE:
You can set aliases for KPIs, KPI's Benchmarks, or KPI's Benchmark Deltas in the Alias column. After the aliases are set, they are
displayed as the column headings of corresponding KPIs, KPI's Benchmarks, or KPI's Benchmark Deltas.
(Optional) Select the Filter Settings check box and click Filter Settings. Then a dialog box is displayed for you to set filtering
criteria.
NOTE:
The filtering criteria take effect only after you select the check box on the left of Filter Settings.
You can set filtering criteria only when Report style of the subreport is set to Time-Object-KPI (TOC).
On the Filter Criteria tab page, set filtering criteria.

Click to add a simple filtering criterion.
Click next to a simple filtering criterion to delete the filtering criterion.
For details, see Table 1.
Table 1 Parameters for Filtering Criteria

Parameter Description
Simple logic This parameter allows you to set a logical calculation formula for each selected KPI. The logical relationship
between different arithmetic calculation formulas can be set to and or or.
The following operators are allowed: =, !=, >=, >, <=, and <. The meanings of these operators are the same
as those in mathematics.
Complex logic This parameter allows you to set a complex logical calculation formula for all selected KPIs as required.
The following operators are allowed: and, or, =, !=, >=, >, <=, <, and parentheses. The meanings of these
operators are the same as those in mathematics.
An advanced filtering criterion consists of basic expressions and logical operators. The basic expression
format is as follows: [KPI name] Arithmetic operator {KPI value}.
Description
Comparison operators cannot be used between KPIs in an advanced filtering criterion.
In a basic expression, you can set the value in {} to numerals or leave it empty. Emptiness indicates a
null value.
A logical operator "and" or "or" connects two basic expressions. Only parentheses can connect
combinations of basic expressions.
The following is used as an example: [KPI1] < {12} and ([KPI2] > {-1} or [KPI3] != {10}).
NOTE:
You can set a maximum of six simple filtering criteria for a subreport.
Click the TopN Conditions tab. On the displayed tab page, specify KPI name and Condition. For details, see Table 2.
Table 2 Parameters for TopN Conditions
Parameter Value Range Description
KPI name - This parameter allows you to
select the KPIs for which you
want to set TopN filtering
criteria.
Condition None: Indicates that the TopN filtering is not performed. Set the value of N as required.
Top N: Indicates the TopN counter records sorted in
descending order.
Bottom N: Indicates the TopN counter records sorted in

ascending order.
Top N%: Indicates the TopM counter records sorted in
descending order. M = N% x Number of selected objects x
Number of selected time periods.
Bottom N%: Indicates the TopM counter records sorted in
ascending order. M = N% x Number of selected objects x
Object Top N: Indicates the TopN counter records sorted in
descending order for each object.
Object Bottom N: Indicates the TopN counter records sorted
in ascending order for each object.
Click Select Time. In the displayed dialog box, specify Time dimension, Day, Period, and Time format.
NOTE:
Performance reports can be classified by time into hourly, daily, weekly, monthly, overall, raw, user-defined, and busy-hour reports. Specify
Time dimension depending on your requirements. If you need a weekly report, set Time dimension to Week.
Click OK.
Optional: Click New Graph (Optional). In the displayed Select Graph Style dialog box, select a chart as required.
NOTE:
You can create a maximum of eight charts in a subreport.
You can change the layout of charts as required in the Layout area.
You can perform the following operations as required in a created chart:

Set an object Click Object in the upper left corner of the chart. In the displayed Select Object dialog box, select an object
instance as required.
Note:
When you query report data, click Switching object and KPI in the upper left corner of the chart. In the displayed
Switching object and KPI dialog box, select an object instance or a KPI as required.
Set a KPI Click KPI in the upper left corner of the chart. In the displayed Select counters dialog box, select a KPI as
required.
Note:
Set a value range for Click in the upper right corner of the chart. In the displayed Set Y-Axis Range dialog box, set the value range
the Y-axis for the Y-axis.
Copy a chart Click in the upper right corner of the chart. The same chart is displayed in the New Graph (Optional) area.
Zoom in on a chart Click in the upper right corner of the chart to zoom in on the chart.
Change the chart Click the chart heading or next to the heading. In the displayed Change Name dialog box, type the chart name.
name
Set series type Select a series from the KPI series under the chart, click it, and choose Series Type > ***.
Replace *** as required.

Set a display mode Select a series from the KPI series under the chart, click it, and select Display Value.
Set the Y-axis Select a series from the KPI series under the chart, click it, and choose Set Y-Axis > ***.

Set series color Select a series from the KPI series under the chart, click it, and select Set the color. In the displayed Change
Colors dialog box, select a color.
Set Default display in query result page.
Note:
The PRS displays query results based on the value of Default display in query result page.
Click Save. In the displayed dialog box, specify Name, Directory, and Description.
d. Create a user-defined report by changing the properties of an existing report and saving the report.
1. In the report list area, select a report and choose > Report Properties.
You can select a system or user-defined report.
2. On the displayed Report Properties page, modify related properties.

3. Click Save As. In the displayed Save as Report dialog box, set Name, Directory, and Description.
4. Click OK.
Related Operations
Perform the following operations as required:
Change a user-defined report 1. In the navigation tree of the Report Management page, select a directory of a user-defined report whose
name name you want to change. All reports in the directory are displayed in the report list area in the right pane.
2. Select the user-defined report whose name you want to change and click next to the report name.
3. In the displayed Modify Report Details dialog box, set Name and Description.
4. Click OK.
View properties of a user- 1. In the navigation tree of the Report Management page, select a directory of a user-defined report whose
defined report properties you want to view. All reports in the directory are displayed in the report list area in the right
pane.
2. Select the user-defined report whose properties you want to view and choose > Report Properties
next to the report name.
2. Create a periodic report task. You can set a periodic task for an existing report as required. Then, the PRS generates reports periodically and distributes the
reports to mailboxes, SMS recipients, or FTP servers.
a. Choose Report > Report Management.

b. Select a report directory from the navigation tree in the left pane. All reports in the directory are displayed in the report list area in the right pane.
c. In the report list area, select a report and choose > New Periodic Task next to the report name.
d. On the displayed New Periodic Task tab page, set parameters in the Basic Settings and Optional Settings areas.
e. Click OK.
After a periodic task is created, the PRS automatically generates reports, distributes the reports, and deletes the expired reports upon the preset time. The
generated reports are stored on the PRS server.
Follow-up Procedure
You can view, modify, or delete a periodic report task you have created as required.

View a periodic report task 1. Select a task and click in the Operation column.
2. On the displayed tab page, view parameters in the Basic Settings and Optional Settings areas.
3. Click OK.
Modify a periodic report task 1. Select a task and click in the Operation column.
2. On the displayed tab page, change the values of parameters in the Basic Settings and Optional Settings areas
as required.
3. Click OK.
Delete a periodic report task 1. Select a task you want to delete and click in the Operation column.
2. In the displayed dialog box, click OK.
f. Analyze the statistical result to evaluate network performance.
Follow-up Procedure
Provide a network performance report and ensure that counter values meet the busy-hour performance requirements.
Identify performance counters whose values do not meet the performance requirements. Submit these counters to network planning and optimization engineers for
further analysis.

Counting Top Alarms

eNodeB alarms can be counted on an U2000 client. Analyzing top alarms helps know the severity and quantity distribution of top alarms in a week, facilitating
network quality analysis, fault diagnosis, and threat prevention.
Prerequisites

The permission for querying alarms is obtained.
Procedure
1. From the main menu of the U2000 client, choose System Management > Task Schedule > Task Management (application style) or Maintenance > Task
Management (traditional style).
2. In the lower right of the Task Management dialog box, click New.
3. In the New Task dialog box, set Task Name, set Task Type to Other > Alarm Check, set Execution Type to Periodic, and click Next.
4. Set Execution interval to 1 in the unit of Weeks, set other parameters as required, and click Next, as shown in Figure 1.
Figure 1 Setting the time and period
5. On the Alarm Basic Parameter tab page, select Common Alarm TopNs Analysis, enter the check item name, NE, number of top alarms, and other
parameters, and then click Add, as shown in Figure 2.
The check item is displayed under Common Alarm TopNs Analysis. You can repeat this step to add more check items.
Figure 2 Setting alarm basic parameters
NOTE:
The alarm check items are classified as follows:
Alarm Trend Analysis: All the alarms are collected on the basis of periods, and the trend of the alarms of different severities is displayed in curved lines
in the NHC report.
Alarm Comparison Analysis: The numbers of alarms generated during two periods are compared and displayed in a bar chart so that an abrupt change
in the number of alarms in different severities can be known.
Common Alarm TopNs Analysis: The alarm IDs or NE objects of the same type with the top N presence frequencies for the alarms and events during a
specified period are analyzed and displayed. In addition, the number of times for the generation of the alarms, alarm names, and alarm severities are also
displayed.
TopN Alarm Features Analysis: The NE objects of a certain type with the top N presence frequencies during a period are analyzed and displayed. In
addition, the number of times for the generation of the alarms, alarm names, and alarm severities are also displayed.
Alarm Maintenance Analysis: The alarms that are not cleared or confirmed are collected. The severities of the alarms to be collected are critical and
major.
Fault Alarm Statistics: The information about all the faulty eNodeBs and cells, including the NE name, eNodeB name, cell name, number of faulty
times, and overall faulty duration, is collected.
6. Click the Alarm Data Time Range tab, set Period to Week, and then click Finish.
The new task is created, and the task is automatically executed at the preset time.
The Task Management dialog box is displayed.
7. From the navigation tree on the left of the Task Management dialog box, select Task Type > Other > Alarm Check to check the task execution.
When Progress is 100%, the task in this period is executed. When Execution Result is Successful, the task in this period is successfully executed, as shown in
Figure 3.
Figure 3 Task completion status
8. Right-click a finished task, and choose Alarm Check Report.

9. In the Alarm Check Report dialog box, double-click a report name, or select a report and click Open to open it, as shown in Figure 4.
Figure 4 Top alarm statistics
Follow-up Procedure
View the statistical data to analyze potential problems. For example, if a large number of transmission links are broken and then recovered, the transmission
equipment may be intermittent. If a board is reset due to a fault, the board may have a hardware fault. In addition, you are advised to analyze frequent faults, find out
causes, and rectify the faults.

Auditing Security Logs

Security logs record security-related operations, such as login and password changes. You must query and audit security logs on an U2000 client every week to check
whether system operations are authorized.
Prerequisites

Procedure
1. From the main window of the U2000 client, choose Security Management > Log Management > Security Log Statistics (application style) or System > Log
Management > Security Log Statistics (traditional style).
2. Set Statistical Items and Filter Criteria in the Filter dialog box as required, and then click OK, as shown in Figure 1 and Figure 2.
You can view the example in the Example area when you are setting Statistical Items.
Figure 1 Setting Statistical Items
Figure 2 Setting the filter criteria
In the displayed Security Log Statistics dialog box, the statistical results are displayed.
NOTE:
If no statistical result is displayed, no record meeting the filter criteria is displayed.
3. Click Save As. The selected security log is saved in .xls format by default.
Follow-up Procedure
Analyze and judge the statistical result. You are advised to identify and exclude abnormal operations according to the actual security standards.

Checking the Voltage Standing Wave Ratio

The antennas working with a high VSWR can be located and rectified by checking the VSWR. Therefore, cell coverage decrease or cell unavailability caused by a
high VSWR can be prevented.
Prerequisites

Context
The voltage standing wave ratio (VSWR) is the ratio of the maximum load voltage to the minimum load voltage. It is used to judge whether the antenna system works
properly. The minimum VSWR value is 1. A high VSWR indicates a reduced signal transmission distance and easily damages the power amplifier (PA). In this case,
the operations of the communications system are affected.
By default, the VSWR on each transmit (TX) channel can be in any of the following conditions:
If the VSWR ranges from 1 to VSWR alarm threshold, the antenna system is normal. If the VSWR is greater than 1 and close to 1, the antenna system works
in the best performance.
If the VSWR ranges from VSWR alarm threshold to VSWR alarm post-processing threshold, the antenna system is abnormal. The cell coverage is affected
and an alarm is reported.
If the VSWR is greater than or equal to VSWR alarm post-processing threshold, the RF channels are disabled.
Therefore, if the VSWR is greater than or equal to VSWR alarm threshold, the antenna system is abnormal and the faults need to be rectified.
NOTE:
To query the VSWR alarm threshold and VSWR alarm post-processing threshold, run theLST RRU command for Macro eNodeB , run theLST BRU command
for BTS3202E.
Procedure
Check the VSWR in real time.

NOTICE:
Checking the VSWR interrupts services in the cell for a few minutes, except checking a multi-mode RRU in a TDS&TDL dual-mode base station or an RRU3152e,
RRU3251, RRU3252, or RRU3253 in a TDD eNodeB. Therefore, you are advised to perform the operations during the period with the lowest traffic volume.
From the main menu of the U2000 client, choose Trace and Maintenance > Maintenance > Antenna Management > VSWR Test (application style) or
Maintenance > Antenna Management > VSWR Test (traditional style). Choose eNodeB in the left-pane of the VSWR Test tab page, and select an NE from the
navigation tree, as shown in Figure 1.
Figure 1 Choosing NEs for checking the VSWR
At the lower right corner, click Test. In the displayed Warning dialog box, click Yes, as shown in Figure 2.
Figure 2 Warning dialog box
If the progress in the VSWR Test dialog box reaches 100%, click Close. The result is displayed in the right-hand pane of the VSWR Test tab page, as shown in
Figure 3.
Figure 3 Test Result tab page
NOTE:
The checking result of the VSWR may be displayed as NULL in the following situations:
The VSWR alarm post-processing switch is set to ON and a major VSWR alarm is generated.
The current output power of the RRU\RU is 15 dB or more less than the maximum output power.
The current time is within two minutes away from the time when the RRU\RU was powered on or reset, because the periodic detection of the standing wave has
not been started in this case.
The specified TX channel does not exist.
Follow-up Procedure
If the VSWR is greater than VSWR alarm threshold, rectify faults by referring to ALM-26529 RF Unit VSWR Threshold Crossed in 3900 Series Base Station
Alarm Reference or BTS3202E Alarm Reference.

Checking the Equipment Transmit Power

You can estimate and adjust the equipment status by checking the radio frequency (RF) transmit (TX) power on the U2000 client.
Prerequisites

Context
The actual TX power of an RF module is normal if it is 0.5 dBm greater or less than the theoretical TX power.
For a cell with empty load, the theoretical TX power of an RF module is calculated based on the configured reference signal (RS) power. The formula used to
calculate the theoretical TX power is as follows: Theoretical TX power = RS power - 10log (14/ (Number of resource blocks (RBs) x Number of RSs on each RB)).
In this formula,
RS power indicates the configured RS power, which can be queried by running the LST PDSCHCFG command.
Number of RBs indicates the total number of RBs under a cell bandwidth, which can be queried by running the LST CELL command.
For details about Number of RSs on each RB, see 3GPP TS 36.211.
NOTE:
This check item is used only to trace the carrier TX power of a single RF module in real time.
Procedure
1. From the main menu of the U2000 client, choose Trace and Maintenance > Signaling Trace > Signaling Trace Management (application style) or Monitor
> Signaling Trace > Signaling Trace Management (traditional style).

2. In the navigation tree, choose Trace Type > Base Station Device and Transport > Device Monitoring > RRU/RFU/BRU Output Power Monitoring.
3. At the lower right corner, click New.
4. In the displayed RRU/RFU/BRU Output Power Monitoring dialog box, set the parameters as listed in Table 1 and click Next.
NOTE:
When creating a tracing task, the mediation file corresponding to the NE version needs to be selected. If the mediation file has not been downloaded, the
Download Mediation File dialog box is displayed.
Figure 1 RRU/RFU/BRU Output Power Monitoring dialog box
Table 1 Setting parameters for creating a tracing task

Parameter Setting
Trace Name Enter a user-defined tracing name that is a string of 1 to 50 characters.
NE In the NE navigation tree, choose NEs to be traced.
Trace Duration Set the tracing start time and end time by selecting the Scheduled start time and Scheduled end time check boxes. Tasks
can start and end at the specified time.
Running Mode Server: The U2000 server analyzes the data reported by NEs in real time and then saves the data into the server
database. The running of a server task has a greater impact on server performances.
Client: The U2000 server does not analyze the data reported by NEs and transfers the data to the U2000 client. The
U2000 client analyzes the data and saves the data onto the local disk. The running of a client task has a lower impact
on server performances.
5. In the displayed RRU/RFU/BRU Output Power Monitoring dialog box, set the cabinet number, subrack number, slot number of the monitored
RRU/RFU/BRU, and the monitoring period. Then, click Finish, as shown in Figure 2.
Return to the Signaling Trace Management tab page, and the created task can be viewed in the tracing list.
NOTE:
The RRU/RFU/BRU subrack number range from 60 to 254 and from 4 to 5, respectively. The BTS3202E subrack number is 0. Subrack No. must be set to the
actual subrack number of the RF module or BTS3202E.
Figure 2 RRU/RFU/BRU Output Power Monitoring dialog box
6. Double-click the tracing task, or right-click and choose Query Result.
In the Query Result tab page, the tracing result is displayed. The equipment output power is Output power(0.1dBm) x 0.1. In the Figure 3, the equipment
output power is 342 x 0.1 = 34.2 dBm.
Figure 3 An example of RRU/RFU/BRU output power tracing result
Follow-up Procedure
If the RRU/RFU/BRU output power is abnormal, it is recommended that the following operations be performed:
1. Rectify faults by referring to ALM-29240 Cell Unavailable in eNodeB Alarm Reference.

2. Check whether the cell status is normal.
If the cell is abnormal, rectify faults by referring to ALM-29240 Cell Unavailable in 3900 Series Base Station Alarm Reference, BTS3202E Alarm
Reference.
If the cell is normal but the RRU/RFU/BRU output power is still abnormal, contact Huawei technical support.

Monthly Maintenance Operations

This chapter describes the monthly maintenance items and operations of an eNodeB. Monthly maintenance items involve checking power supply, analyzing faults and
customer complaints, preparing monthly report on the network performance, checking Security Patches for the OMU operating system, checking OS and database
hardening, and checking weak passwords and Others.
Checking Power Supply

Checking power supply includes checking the alarms related to power supply and storage batteries, the status of power monitoring unit (PMU), and the status of
storage batteries.
Analyzing Faults and Customer Complaints
Analyzing customer complaints helps identify causes and analyze the fault trends to facilitate troubleshooting.
Preparing Monthly Reports on Network Performance
Checking Security Patches for the OMU Operating System

This section describes how to check security patches for the OMU operating system and configure the system security policy in real time to ensure stable
running of the system.
Checking OS and Database Hardening
This section describes how to check operating system (OS) hardening and configure the system security policy in real time to ensure stable running of the
system.
Checking Weak Passwords and Others
This section describes how to check all password policies used in the system for security. The password policies involve LMT, operating system (OS), and FTP
passwords.

Checking Power Supply

Checking power supply includes checking the alarms related to power supply and storage batteries, the status of power monitoring unit (PMU), and the status of
storage batteries.
Prerequisites

The power supply module or storage batteries are installed in the eNodeB.
Context
No fault alarm related to power supply and storage batteries is reported. Any active alarms are cleared promptly.
The BBU3900 input voltage (Busbar Voltage (V)) ranges from -38.4 V DC to -57 V DC.
The rated BBU3900 input voltage is -48 V DC.
The storage battery capacity is greater than 30%.

The storage battery temperature is lower than 50C.
The storage battery use efficiency is higher than 80%.
NOTE:
The BTS3202E does not support power supply check.
Procedure
Check whether fault alarms related to power supply and storage batteries are existed.
Check alarms by referring to "Procedure" in section Monitoring Fault Alarms.
Check the BBU3900 input voltage.

tree.
NOTE:
3. In the right-hand pane of the MML Command tab page, run the DSP PMU command.
Figure 1 shows the query result. The value of Busbar Voltage (V) is the BBU3900 input voltage.
Figure 1 Query result of BBU3900 input voltage
Check the storage battery use efficiency.

tree.
NOTE:
3. Run the STR BATTST command to test a storage battery.

4. Run the DSP BATTERY command to query the spare battery capacity.
5. Run the DSP BATTR command to query the storage battery use efficiency, as shown in Figure 2.
Figure 2 Query result of the storage battery use efficiency
Follow-up Procedure
If any alarms related to power supply or storage battery exist, clear the alarms by referring to the sections about these alarms in 3900 Series Base Station Alarm
Reference.
If the BBU3900 input voltage (Busbar Voltage (V)) is out of the range from -38.4 V DC to -57 V DC, check the input power supply.
If the input power supply is normal, contact Huawei for technical support.
If the input power supply is abnormal, contact the maintenance personnel of the input power supply for fault rectification.
If the capacity of the storage battery is less than 30%, charge the storage battery.
If the temperature of the storage battery is higher than 50C and less than 53C, check whether a blackout occurs repeatedly during battery charging in the case
that the operating temperature of the storage battery is normal and the ventilation is proper.
If yes, check the temperature of the storage battery after power supply becomes normal.
If no, replace the storage battery.
If the temperature is higher than 53C, replace the storage battery.
If the storage battery efficiency is less than 80%, replace the storage battery.
Parent topic: Monthly Maintenance Operations
Analyzing Faults and Customer Complaints

Analyzing customer complaints helps identify causes and analyze the fault trends to facilitate troubleshooting.
Procedure
1. Collect customer complaints of this month and determine related fault scopes and categories.
2. Identify the fault causes. To be specific, analyze and compare various possible causes of the faults, eliminate the unlikely causes, and then determine the causes
for the faults.
3. Collect the fault and exception statistics on a monthly basis, and then analyze the fault trends.
4. Analyze the frequent faults, identify the causes, and then rectify the faults in time.
5. Summarize the experience for handling the complaints of the month and propose suggestions for improvements.
Follow-up Procedure
For details about common fault diagnosis and handling suggestions, see 3900 Series Base Station Alarm Reference, BTS3202E Alarm Reference.
Summarize fault causes, analyze frequent faults and fault trends, and propose optimization suggestions.

Preparing Monthly Reports on Network Performance

Prepare monthly reports on network performance using the performance surveillance (PRS).
Prerequisites
The PRS performance report management component has been installed.

The PRS client is properly connected to the PRS server.
You have logged in to the PRS client and been granted PRS operation permissions.
Procedure
1. Perform this step only when existing reports do not meet users' query requirements. Prepare a user-defined monthly report.
a. Choose Report > Report Management from the main menu of the PRS client.
b. Perform the following operations as required:
Create a report directly Perform substep c.
Change the properties of an existing report and save the report Perform substep d.
c. Directly create a user-defined report.
On the displayed Report Management tab page, click .
On the displayed tab page, specify NE type, Object type, Benchmark rule, and Report style.
Select an NE type: Set the vendor and NE type. By default, the first NE type of the first vendor is selected.
Select an object type: By default, the first object type in the object type list is selected.
You can select Sort by click times or Sort alphabetically to sort all object types. By default, Sort by click times is selected.
Select a benchmark rule: Select a benchmark rule from the drop-down list. By default, None is selected.
After the benchmark rules are set, Report style and Time dimension use their default values and the two parameters are not configurable.
Select a report style: Six report styles are available. By default, Time-Object-KPI (TOC) is selected.
Click Select Object. In the displayed dialog box, set the object instance and object attributes.
Select Object tab page: Select an object instance.
You can type a keyword in the search box or use advanced search to quickly locate the required object instance.
Select Object Attribute tab page: Set the object attribute that you want to view in the report.
Click Select KPI. In the displayed dialog box, select one or more KPIs for a subreport.
If Benchmark rule is not set to None, the options Include Benchmark and Only Benchmark can be selected.
If you select Include Benchmark, all KPIs, KPI's Benchmarks, and KPI's Benchmark Deltas are displayed in the left KPI navigation
tree.
NOTE:
KPI's Benchmark: Indicates the benchmark value of a KPI.
KPI's Benchmark Delta: Indicates the difference between the KPI's benchmark value and the actual KPI value.
If you select Only Benchmark, only KPIs that have benchmarks, corresponding Benchmarks, and Benchmark Deltas of such KPIs are
displayed in the left KPI navigation tree.
In the KPI navigation tree, if you double-click a function subset or select a function subset and click , all KPIs, KPI's Benchmarks,
and KPI's Benchmark Deltas under the function subset are added to the right area.
To delete unnecessary KPIs, KPI's Benchmarks, or KPI's Benchmark Deltas from the right area, you can select them and click .
In the right area, you can select a KPI, KPI's Benchmark, or KPI's Benchmark Delta and click or to adjust the
position of the selected object. The column position of the KPI, KPI's Benchmark, or KPI's Benchmark Delta will be changed in the
query result report.
Alternatively, you can select a KPI, KPI's Benchmark, or KPI's Benchmark Delta, and drag the selected object upwards or downwards
to adjust its position.
NOTE:
You can set aliases for KPIs, KPI's Benchmarks, or KPI's Benchmark Deltas in the Alias column. After the aliases are set, they are
displayed as the column headings of corresponding KPIs, KPI's Benchmarks, or KPI's Benchmark Deltas.
(Optional) Select the Filter Settings check box and click Filter Settings. Then a dialog box is displayed for you to set filtering
criteria.
NOTE:
The filtering criteria take effect only after you select the check box on the left of Filter Settings.
You can set filtering criteria only when Report style of the subreport is set to Time-Object-KPI (TOC).
On the Filter Criteria tab page, set filtering criteria.

Click to add a simple filtering criterion.
Click next to a simple filtering criterion to delete the filtering criterion.
For details, see Table 1.
Table 1 Parameters for Filtering Criteria

Parameter Description
Simple logic This parameter allows you to set a logical calculation formula for each selected KPI. The logical relationship
between different arithmetic calculation formulas can be set to and or or.
The following operators are allowed: =, !=, >=, >, <=, and <. The meanings of these operators are the same
as those in mathematics.
Complex logic This parameter allows you to set a complex logical calculation formula for all selected KPIs as required.
The following operators are allowed: and, or, =, !=, >=, >, <=, <, and parentheses. The meanings of these
operators are the same as those in mathematics.
An advanced filtering criterion consists of basic expressions and logical operators. The basic expression
format is as follows: [KPI name] Arithmetic operator {KPI value}.
Description
Comparison operators cannot be used between KPIs in an advanced filtering criterion.
In a basic expression, you can set the value in {} to numerals or leave it empty. Emptiness indicates a
null value.
A logical operator "and" or "or" connects two basic expressions. Only parentheses can connect
combinations of basic expressions.
The following is used as an example: [KPI1] < {12} and ([KPI2] > {-1} or [KPI3] != {10}).
NOTE:
You can set a maximum of six simple filtering criteria for a subreport.
Click the TopN Conditions tab. On the displayed tab page, specify KPI name and Condition. For details, see Table 2.
Table 2 Parameters for TopN Conditions
Parameter Value Range Description
KPI name - This parameter allows you to
select the KPIs for which you
want to set TopN filtering
criteria.
Condition None: Indicates that the TopN filtering is not performed.
Set the value of N as required.
Top N: Indicates the TopN counter records sorted in

descending order.
Bottom N: Indicates the TopN counter records sorted in
ascending order.
Top N%: Indicates the TopM counter records sorted in
descending order. M = N% x Number of selected objects x
Bottom N%: Indicates the TopM counter records sorted in
ascending order. M = N% x Number of selected objects x
Object Top N: Indicates the TopN counter records sorted in
descending order for each object.
Object Bottom N: Indicates the TopN counter records sorted
in ascending order for each object.
Click Select Time. In the displayed dialog box, specify Time dimension, Day, Period, and Time format.
NOTE:
Performance reports can be classified by time into hourly, daily, weekly, monthly, overall, raw, user-defined, and busy-hour reports. Specify
Time dimension depending on your requirements. If you need a monthly report, set Time dimension to Month.
Click OK.
Optional: Click New Graph (Optional). In the displayed Select Graph Style dialog box, select a chart as required.
NOTE:
You can create a maximum of eight charts in a subreport.
You can change the layout of charts as required in the Layout area.
You can perform the following operations as required in a created chart:

Set an object Click Object in the upper left corner of the chart. In the displayed Select Object dialog box, select an object
instance as required.
Note:
Set a KPI Click KPI in the upper left corner of the chart. In the displayed Select counters dialog box, select a KPI as
required.
Note:
Set a value range for Click in the upper right corner of the chart. In the displayed Set Y-Axis Range dialog box, set the value range
the Y-axis for the Y-axis.
Copy a chart
Click in the upper right corner of the chart. The same chart is displayed in the New Graph (Optional) area.
Zoom in on a chart Click in the upper right corner of the chart to zoom in on the chart.
Change the chart Click the chart heading or next to the heading. In the displayed Change Name dialog box, type the chart name.
name
Set series type Select a series from the KPI series under the chart, click it, and choose Series Type > ***.

Set a display mode Select a series from the KPI series under the chart, click it, and select Display Value.
Set the Y-axis Select a series from the KPI series under the chart, click it, and choose Set Y-Axis > ***.

Set series color Select a series from the KPI series under the chart, click it, and select Set the color. In the displayed Change
Colors dialog box, select a color.
Set Default display in query result page.
Note:
The PRS displays query results based on the value of Default display in query result page.
Click Save. In the displayed dialog box, specify Name, Directory, and Description.
d. Create a user-defined report by changing the properties of an existing report and saving the report.
1. In the report list area, select a report and choose > Report Properties.
You can select a system or user-defined report.
2. On the displayed Report Properties page, modify related properties.

3. Click Save As. In the displayed Save as Report dialog box, set Name, Directory, and Description.
4. Click OK.
Related Operations
Perform the following operations as required:

Change a user-defined report 1. In the navigation tree of the Report Management page, select a directory of a user-defined report whose
name name you want to change. All reports in the directory are displayed in the report list area in the right pane.
2. Select the user-defined report whose name you want to change and click next to the report name.
3. In the displayed Modify Report Details dialog box, set Name and Description.
4. Click OK.
View properties of a user- 1. In the navigation tree of the Report Management page, select a directory of a user-defined report whose
defined report properties you want to view. All reports in the directory are displayed in the report list area in the right
pane.
2. Select the user-defined report whose properties you want to view and choose > Report Properties
next to the report name.
2. Create a periodic report task. You can set a periodic task for an existing report as required. Then, the PRS generates reports periodically and distributes the
reports to mailboxes, SMS recipients, or FTP servers.
a. Choose Report > Report Management.

b. Select a report directory from the navigation tree in the left pane. All reports in the directory are displayed in the report list area in the right pane.
c. In the report list area, select a report and choose > New Periodic Task next to the report name.
d. On the displayed New Periodic Task tab page, set parameters in the Basic Settings and Optional Settings areas.
e. Click OK.
After a periodic task is created, the PRS automatically generates reports, distributes the reports, and deletes the expired reports upon the preset time. The
generated reports are stored on the PRS server.
Follow-up Procedure
You can view, modify, or delete a periodic report task you have created as required.

View a periodic report task 1. Select a task and click in the Operation column.
2. On the displayed tab page, view parameters in the Basic Settings and Optional Settings areas.
3. Click OK.
Modify a periodic report task 1. Select a task and click in the Operation column.
2. On the displayed tab page, change the values of parameters in the Basic Settings and Optional Settings areas
as required.
3. Click OK.
Delete a periodic report task
1. Select a task you want to delete and click in the Operation column.
2. In the displayed dialog box, click OK.
f. Analyze the statistical result to evaluate network performance.
Follow-up Procedure
Provide a network performance report and ensure that counter values meet the busy-hour performance requirements.
Identify performance counters whose values do not meet the performance requirements. Submit these counters to network planning and optimization engineers for
further analysis.

Checking Security Patches for the OMU Operating System

This section describes how to check security patches for the OMU operating system and configure the system security policy in real time to ensure stable running of
the system.
Prerequisites
You have the permissions to scan viruses and update antivirus components.
Context
Maintenance terminal system with viruses will cause abnormal configuration data and maintenance failure.
NOTE:
Antivirus solutions for operating systems are applicable to only Windows and SUSE Linux.
SUSE Linux: The SUSE Linux antivirus solution currently works only for x86 servers. The U2000 provides the Trend Server Protect antivirus software for U2000
servers.
Windows 2003: The Windows antivirus solution works for Windows-based computers, such as U2000 clients, LMT clients, and Citrix servers. The U2000 provides
the Trend OfficeScan antivirus software for these computers.
Procedure
1. Update the virus definition files.

2. Remove viruses on the computer by using copyrighted antivirus software.
NOTE:
Customers should purchase antivirus software.

Checking OS and Database Hardening

This section describes how to check operating system (OS) hardening and configure the system security policy in real time to ensure stable running of the system.
Context
Real-time configuration of system security policies helps ensure stable running of the system.
NOTE:
Before delivery, security hardening has been performed on the OS in U2000 V200R011 and later and on the database in U2000 V200R013 and later.
Procedure
1. The security hardening items differ slightly, depending on U2000 applications. To perform security hardening for items outside the hardening policies, contact
Huawei technical support engineers in advance to prevent impacts on U2000 applications.
Checking Weak Passwords and Others

This section describes how to check all password policies used in the system for security. The password policies involve LMT, operating system (OS), and FTP
passwords.
Purpose
Check whether all password policies used by the system are secure.
NOTE:
It is recommended that you change the password upon your first login and change the password every three months.
Prerequisites
You have logged in to the LMT.

You have permissions to execute MML commands on the LMT.
Procedure
1. Method for changing passwords:

a. For details about how to change passwords for admin, administrator, operator, User, guest, and custom, see see section Changing Users' Passwords in
U2000 User Management User Guideand 3900 Series Base Station LMT User Guide.
b. For details about how to change the password for the OS administrator, see section Changing the Administrator Password of the Operating System in
U2000 Administrator Guide
2. Password complexity policy:
a. The passwords for admin, administrator, operator, User, guest, custom, and OS administrator must comply with the password complexity policy.
NOTE:
The passwords for admin, administrator, operator, User, guest, and custom must comply with the password policy configured by running the SET
PWDPOLICYcommand.
Run the LST PWDPOLICY command to query the configured user password policies. Run the SET PWDPOLICY command to change the
password policies.
b. For details about the password policy configured of OS administrator see U2000 Administrator Guide
3. Others: For details about how to check other security configurations, see section Specific Security Policiesin Security Overview Feature Parameter
Description.

Routine Maintenance Data Sheet

An eRAN routine maintenance data sheet is used to record the equipment performance status information during the maintenance.
7x24 Monitoring Data Sheet

The eNodeB 7x24 monitoring data sheet is used to record the execution of 7x24 monitoring items onsite.
Daily Maintenance Data Sheet
The eNodeB daily maintenance data sheet is used to record the execution of the daily maintenance items onsite.
Weekly Maintenance Data Sheet
The eNodeB weekly maintenance data sheet is used to record the execution of the weekly maintenance items. The sheet is in the same format as the daily
maintenance data sheet.
Monthly Maintenance Data Sheet
The eNodeB monthly maintenance data sheet is used to record the execution of the monthly maintenance items.

7x24 Monitoring Data Sheet

The eNodeB 7x24 monitoring data sheet is used to record the execution of 7x24 monitoring items onsite.
After monitoring items are performed, the results are recorded in Table 1.
Table 1 eNodeB 7x24 monitoring data sheet

Basic Information Operator
Duration
SN Item Reference Standard Description on the Result
1 Monitoring fault alarms All alarms are cleared. -
Parent topic: Routine Maintenance Data Sheet

Daily Maintenance Data Sheet

The eNodeB daily maintenance data sheet is used to record the execution of the daily maintenance items onsite.
After the daily maintenance items are performed, the results are recorded in Table 1.
Table 1 eNodeB daily maintenance data sheet

Basic information Operator
Duration
1 Monitoring equipment status The number of Not Passed and Failed to Execute items is 0 -
in the NE health check (NHC) report. The check items in the
Manually Checked are checked and passed.
2 Checking busy-hour performance Reports on busy-hour network performance are generated, in -
which the value of each performance counter is greater than
or equal to the busy-hour performance requirement.
3 Checking the Connection Status Between The NEs are in Normal state. -
the U2000 and NEs

Weekly Maintenance Data Sheet

The eNodeB weekly maintenance data sheet is used to record the execution of the weekly maintenance items. The sheet is in the same format as the daily
maintenance data sheet.
After the weekly maintenance items are performed, the results are recorded in Table 1.
Table 1 eNodeB weekly maintenance data sheet

Duration
1 Backing up the eNodeB configuration The configuration data is successfully backed up. -
data
2 Preparing weekly reports on the network Weekly reports on busy-hour network performance are -
performance generated, in which the value of each performance counter is
greater than or equal to the weekly performance requirement.
3 Counting top alarms Top alarm statistics are generated, and top alarms are -
cleared.
4 Auditing security logs Operations, such as the login, logout, and password -
modification, meet security requirements.
5 Checking the voltage standing wave ratio The VSWR ranges from 1 to 2. -
(VSWR)
6 Checking the equipment transmit power The equipment transmit power is the theoretical transmit -
power with a tolerance of 0.5 dBm.

Monthly Maintenance Data Sheet

The eNodeB monthly maintenance data sheet is used to record the execution of the monthly maintenance items.
After the monthly maintenance items are performed, the results are recorded in Table 1.
Table 1 eNodeB monthly maintenance data sheet

Duration
1 Checking power supply No fault alarm related to power supply and storage -
batteries is reported. Any active alarms are cleared
promptly.
The BBU3900 input voltage (Busbar Voltage (V))
ranges from -38.4 V DC to -57 V DC.
The storage battery capacity is greater than 30%.
The storage battery temperature is lower than 50C.
The storage battery usage efficiency is more than 80%.
2 Analyzing customer complaints Complaints and fault data are collected, fault and exception -
records are analyzed, frequent faults are checked and
rectified, and an analysis report is generated for this month.
3 Preparing monthly reports on the Monthly network performance reports are generated, in -
network performance which the value of each performance counter is greater than
or equal to the monthly performance requirement.
4 Checking Security Patches for the OMU No risks are found on the OMU operating system. -
Operating System
5 Checking OS and Database Hardening Security policies are promptly configured on the operating -
system.
6 Checking Weak Passwords and Others All password policies for the LMT, operating system, and -
FTP server are secure.


Eran Routine Maintenace Guide

Hochgeladen von

Dokumentinformationen

Copyright

Verfügbare Formate

Dieses Dokument teilen

Dokument teilen oder einbetten

Freigabeoptionen

Stufen Sie dieses Dokument als nützlich ein?

Sind diese Inhalte unangemessen?

Copyright:

Verfügbare Formate

Eran Routine Maintenace Guide

Hochgeladen von

Copyright:

Verfügbare Formate

eRAN Routine Maintenance Guide Page 1 of 35

eRAN Routine Maintenance Guide

Product Name Solution Version Product Version

Related Product Version

Related Product Name Product Version

This document is intended for:

Changes in the eRAN Routine Maintenance Guide

Huawei Proprietary and Confidential

Changes in the eRAN Routine Maintenance Guide

This is the second release.

No information in issue 01 (2015-03-23) of V100R010C10 is deleted from this issue.

This is the first release.

This is the Draft A release.

No information in issue 02 (2014-06-25) of V100R009C00 is deleted from this issue.

Parent topic: eRAN Routine Maintenance Guide

Huawei Proprietary and Confidential

Overview of eRAN Routine Maintenance

Scope of Routine Maintenance

Tools for Routine Maintenance

Items and Periods for Routine Maintenance

Table 1 eNodeB 7x24 monitoring items

Huawei Proprietary and Confidential

7x24 Monitoring Operations

Monitoring Fault Alarms

Parent topic: eRAN Routine Maintenance Guide

Huawei Proprietary and Confidential

Monitoring Fault Alarms

The U2000 client is properly connected to the U2000 server.

The Filter dialog box is displayed.

Figure 1 Setting filter criteria

Figure 2 Add Communication Device dialog box (1/2)

The Add Communication Device dialog box is closed.

Table 1 Communication parameters for setting emails and SMS notifications

f. In the Communication Device Settings dialog box, click Close.

Figure 4 Message Format Settings dialog box

Table 2 Parameters for email content and SMS content

9. (Optional) Set alarms to be notified.

All objects: Select all objects.

Parent topic: 7x24 Monitoring Operations

Huawei Proprietary and Confidential

Daily Maintenance Operations

Checking Equipment Status

Parent topic: eRAN Routine Maintenance Guide

Huawei Proprietary and Confidential

Checking Equipment Status

The U2000 client is properly connected to the U2000 server.

a. Select Maintenance from the Scenario drop-down list.

Figure 2 Setting time and period for a task

Figure 3 shows a health check report in HTML format.

Figure 3 Health check report

The detailed assessment is as follows:

Product type check: The product type is correct.

3. Perform the check task again.

If the number of Manually Checked is not 0, perform the following operations:

1. Click the hyperlink in the box under Manually Checked.

Parent topic: Daily Maintenance Operations

Huawei Proprietary and Confidential

Checking Busy-Hour Performance

The KPIs to be queried and related reference standards are determined.

Figure 1 Selecting measurement item

3. Select objects on the Object tab page, as shown in Figure 2.

Figure 2 Selecting objects

Figure 3 Selecting counters

Figure 4 Setting time parameters