GBSS17.1&RAN17.1 Routine Maintenance Guide (01) (PDF) - en

GBSS17.1&RAN17.
Routine Maintenance Guide
Issue 01
Date 2015-03-25
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2015. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 01 (2015-03-25) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co., Ltd.
GBSS17.1&RAN17.1
Routine Maintenance Guide About This Document
About This Document
Overview
This document provides guidelines for daily, weekly, and monthly maintenance of the
GBSS&RAN and provides tables for recording the maintenance results.
Product Versions
The following table lists the product version and solution version related to this document.
Product Name Product Version Solution Version
BSC6900/BSC6910 V900R017C10/ SRAN10.1

V100R017C10 GBSS17.1
BTS3900 V100R009C10 RAN17.1
l GBTS: V100R010C10
BTS3900A
l eGBTS: V100R010C10
BTS3900L l NodeB: V100R010C10
BTS3900AL
DBS3900
MBTS V100R009C10
Intended Audience
This document is intended for:
l Shift operators
l System engineers
Organization
1 Change History
Issue 01 (2015-03-25) Huawei Proprietary and Confidential ii

GBSS17.1&RAN17.1
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes refer
to changes in functions of a specific product version. Editorial changes refer to changes in
wording or addition of information that was not described in the earlier version.
2 High-Risk Operations
3 GBSS&RAN Routine Maintenance Overview
The purpose of GBSS&RAN routine maintenance is to ensure the reliability, stability, and
optimum operational state of the BSC6900/BSC6910, NodeB, GBTS, and eGBTS. In addition,
routine maintenance can prevent potential accidents, and identify and resolve problems in time.
4 GBSS&RAN Daily Maintenance Guidelines
This chapter provides guidelines for performing the daily maintenance tasks on the
GBSS&RAN.
5 GBSS&RAN Weekly Maintenance Guidelines
This chapter provides guidelines for performing the weekly maintenance tasks on the
GBSS&RAN.
6 GBSS&RAN Monthly Maintenance Guidelines
This chapter provides guidelines for performing the monthly maintenance tasks on the
GBSS&RAN.
7 GBSS&RAN Routine Maintenance Record
Information about the equipment performance during the maintenance is recorded in routine
maintenance record tables.
Conventions
Symbol Conventions
The symbols that may be found in this document are defined as follows.
Symbol Description
Indicates an imminently hazardous situation which, if not

avoided, will result in death or serious injury.
Indicates a potentially hazardous situation which, if not

avoided, could result in death or serious injury.

avoided, may result in minor or moderate injury.
Issue 01 (2015-03-25) Huawei Proprietary and Confidential iii

GBSS17.1&RAN17.1
Symbol Description

avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Calls attention to important information, best practices and

tips.
NOTE is used to address information not related to personal
injury, equipment damage, and environment deterioration.
General Conventions
The general conventions that may be found in this document are defined as follows.
Convention Description
Times New Roman Normal paragraphs are in Times New Roman.
Boldface Names of files, directories, folders, and users are in

boldface. For example, log in as user root.
Italic Book titles are in italics.
Courier New Examples of information displayed on the screen are in

Courier New.
Command Conventions
The command conventions that may be found in this document are defined as follows.
Boldface The keywords of a command line are in boldface.
Italic Command arguments are in italics.
[] Items (keywords or arguments) in brackets [ ] are optional.
{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.
[ x | y | ... ] Optional items are grouped in brackets and separated by

vertical bars. One item is selected or no item is selected.
{ x | y | ... }* Optional items are grouped in braces and separated by

vertical bars. A minimum of one item or a maximum of all
items can be selected.
Issue 01 (2015-03-25) Huawei Proprietary and Confidential iv

GBSS17.1&RAN17.1
[ x | y | ... ]* Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
The GUI conventions that may be found in this document are defined as follows.
Boldface Buttons, menus, parameters, tabs, window, and dialog titles

are in boldface. For example, click OK.
> Multi-level menus are in boldface and separated by the ">"

signs. For example, choose File > Create > Folder.
Keyboard Operations
The keyboard operations that may be found in this document are defined as follows.
Format Description
Key Press the key. For example, press Enter and press Tab.
Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt
+A means the three keys should be pressed concurrently.
Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means
the two keys should be pressed in turn.
Mouse Operations
The mouse operations that may be found in this document are defined as follows.
Action Description
Click Select and release the primary mouse button without moving
the pointer.
Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.
Drag Press and hold the primary mouse button and move the
pointer to a certain position.
Issue 01 (2015-03-25) Huawei Proprietary and Confidential v

GBSS17.1&RAN17.1
Routine Maintenance Guide Contents
Contents
About This Document.....................................................................................................................ii

1 Change History..............................................................................................................................1
2 High-Risk Operations...................................................................................................................2
3 GBSS&RAN Routine Maintenance Overview........................................................................3
3.1 Scope..............................................................................................................................................................................4
3.2 GBSS&RAN Tools.........................................................................................................................................................4
3.3 GBSS&RAN Routine Maintenance Tasks Based on Maintenance Frequency..............................................................6
3.3.1 Daily Maintenance Tasks............................................................................................................................................6
3.3.2 Weekly Maintenance Tasks.........................................................................................................................................7
3.3.3 Monthly Maintenance Tasks.......................................................................................................................................7
4 GBSS&RAN Daily Maintenance Guidelines..........................................................................9

4.1 Monitoring GBSS&RAN Alarms and Events..............................................................................................................11
4.1.1 Alarm Handling Procedure........................................................................................................................................11
4.1.2 Monitoring GBSS&RAN Alarms..............................................................................................................................13
4.1.3 Monitoring GBSS&RAN Events...............................................................................................................................14
4.1.4 Collecting GBSS&RAN Alarm and Event Statistics................................................................................................15
4.2 Monitoring the GBSS&RAN Performance..................................................................................................................16
4.2.1 Monitoring Performance Counters............................................................................................................................16
4.2.2 Saving Performance Measurement Results...............................................................................................................20
4.3 Monitoring Cell Status and Cell Resources..................................................................................................................21
4.3.1 Monitoring Cell Status...............................................................................................................................................21
4.3.2 Monitoring Cell Resources........................................................................................................................................23
4.4 Querying and Saving BSC6900/BSC6910 Operation Logs.........................................................................................25
4.5 Querying and Saving Other Logs of the BSC6900/BSC6910......................................................................................28
4.6 Querying and Saving NodeB Operation Logs..............................................................................................................35
4.7 Querying and Saving Other Logs of the NodeB...........................................................................................................36
4.8 Checking the GBTS Running Status............................................................................................................................38
4.9 Checking the Scheduled NE Backup Function.............................................................................................................39
5 GBSS&RAN Weekly Maintenance Guidelines....................................................................42

5.1 Performing NE Health Check.......................................................................................................................................44
Issue 01 (2015-03-25) Huawei Proprietary and Confidential vi

GBSS17.1&RAN17.1
Routine Maintenance Guide Contents
5.2 Checking the Running Status of the OMU...................................................................................................................46

5.3 Checking the Running Status of a GBAM Server........................................................................................................48
5.4 Checking the BSC6900/BSC6910 Board Status..........................................................................................................49
5.5 Checking the Base Station Board Status......................................................................................................................50
5.6 Checking the BSC6900/BSC6910 Clock Status..........................................................................................................52
5.7 Checking the Base Station Clock Status.......................................................................................................................54
5.8 Backing Up and Restoring the GBSS&RAN System Data..........................................................................................55
5.8.1 Creating a Scheduled Backup Task (on the U2000)..................................................................................................55
5.8.2 Manually Backing up NE Data (on the U2000)........................................................................................................56
5.8.3 Restoring NE Data (on the U2000)...........................................................................................................................57
5.8.4 Manually Backing Up and Restoring NE Data (on the LMT)...................................................................................58
5.9 Backing Up License Information.................................................................................................................................59
5.10 Analyzing Performance Measurement Results...........................................................................................................61
5.11 Collecting Historical Alarm and Event Statistics.......................................................................................................62
5.12 Checking Communication Between NEs and the U2000...........................................................................................64
6 GBSS&RAN Monthly Maintenance Guidelines..................................................................66

6.1 Analyzing Customer Complaints..................................................................................................................................68
6.2 Preparing an NE Running Report.................................................................................................................................68
6.3 Preparing a Performance Report...................................................................................................................................70
6.4 Checking the Disk Space on the Terminal System.......................................................................................................70
6.5 Checking the Maintenance Terminal System for Viruses............................................................................................71
6.6 Checking the Connectivity of Port Links.....................................................................................................................71
6.7 Checking Security Patches for the OMU OS...............................................................................................................72
6.8 Checking OS Hardening...............................................................................................................................................75
6.9 Checking Weak Passwords and Others........................................................................................................................80
6.10 Updating Key Material...............................................................................................................................................81
7 GBSS&RAN Routine Maintenance Record...........................................................................82

7.1 Daily Maintenance Record...........................................................................................................................................83
7.2 Weekly Maintenance Record........................................................................................................................................84
7.3 Monthly Maintenance Record......................................................................................................................................85
Issue 01 (2015-03-25) Huawei Proprietary and Confidential vii

GBSS17.1&RAN17.1
Routine Maintenance Guide 1 Change History
1 Change History
This section provides information about the changes in different document versions. There are
two types of changes, including function changes and editorial changes. Function changes refer
to changes in functions of a specific product version. Editorial changes refer to changes in
wording or addition of information that was not described in the earlier version.
01 (2015-03-25)
This issue does not include any changes.
Draft A (2015-01-15)
Compared with Issue 02 (2014-05-31) of V900R016C00, this issue includes the following
changes.
Change Type Change Description
Function Added None.

change
Modified
Deleted
Editorial Combined the description of GBSS and RAN into this document.
change
Issue 01 (2015-03-25) Huawei Proprietary and Confidential 1

GBSS17.1&RAN17.1
Routine Maintenance Guide 2 High-Risk Operations
2 High-Risk Operations
Table 2-1 High-risk operations
Type Operation Risk Reference
Operations on Some operations on hardware, High-Risk Hardware Operations in

hardware such as board replacement, may l BSC6900 GSM Site
affect system operating. Maintenance Guide
Therefore, perform these
operations when the traffic is light, l BSC6900 GU Site Maintenance
for example, in the early morning. Guide
In addition, perform these l BSC6900 UMTS Site
operations as quickly as possible to Maintenance Guide
reduce the impact on the system. l BSC6910 GSM Site
The impact of board replacement Maintenance Guide
varies with the board function. l BSC6910 GU Site Maintenance
Guide
l BSC6910 UMTS Site
Maintenance Guide
Commands Incorrect execution of some High-Risk Command List in

commands may affect system l BSC6900 GSM MML Command
operating. Exercise caution when Reference
running these commands.
l BSC6900 GU MML Command
Reference
l BSC6900 UMTS MML
Command Reference
l BSC6910 GSM MML Command
Reference
l BSC6910 GU MML Command
Reference
l BSC6910 UMTS MML
Command Reference

GBSS17.1&RAN17.1
Routine Maintenance Guide 3 GBSS&RAN Routine Maintenance Overview
3 GBSS&RAN Routine Maintenance

Overview
About This Chapter
The purpose of GBSS&RAN routine maintenance is to ensure the reliability, stability, and
optimum operational state of the BSC6900/BSC6910, NodeB, GBTS, and eGBTS. In addition,
routine maintenance can prevent potential accidents, and identify and resolve problems in time.
3.1 Scope
GBSS&RAN routine maintenance is performed on a U2000 or LMT to ensure the reliable
operation of the BSC6900/BSC6910, NodeB, and BTS.
3.2 GBSS&RAN Tools

The tools for GBSS&RAN routine maintenance consist of the U2000 client and LMT.
3.3 GBSS&RAN Routine Maintenance Tasks Based on Maintenance Frequency

Based on the maintenance frequency, routine maintenance is classified into daily, weekly, and
monthly maintenance.

GBSS17.1&RAN17.1
3.1 Scope
GBSS&RAN routine maintenance is performed on a U2000 or LMT to ensure the reliable
operation of the BSC6900/BSC6910, NodeB, and BTS.
GBSS&RAN routine maintenance is performed to monitor and maintain the BSC6900/

BSC6910, NodeB, GBTS, and eGBTS. Routine maintenance does not include the routine
maintenance on the U2000 and the site maintenance.
l To perform site maintenance, see .

– BSC6900 UMTS Site Maintenance Guide
– BSC6900 GU Site Maintenance Guide
– BSC6900 GSM Site Maintenance Guide
– BSC6910 UMTS Site Maintenance Guide
– BSC6910 GU Site Maintenance Guide
– BSC6910 GSM Site Maintenance Guide
l To perform the routine maintenance on the U2000, see U2000 Product Documentation.
l To modify GBSS&RAN configuration, see .
– RAN Reconfiguration Guide
– GBSS&RAN Reconfiguration Guide
– GBSS Reconfiguration Guide
3.2 GBSS&RAN Tools

The tools for GBSS&RAN routine maintenance consist of the U2000 client and LMT.
U2000 Client
The U2000 adopts the client/server mode and the U2000 client is used to simultaneously monitor
multiple NEs. You can perform operations only after logging in to the server through the client.
NOTE
When the RAN Sharing feature is enabled, the operations support systems (OSSs) of telecom operators
that share GBSS equipment are connected to the U2000 through northbound interfaces. In this case,
permissions of the operators are as follows:
l An operator has no permission to view the configurations, status, alarms, and performance of cells
provided by other operators.
l Operators have permission to view the configurations, status, alarms, and performance of shared
resources but have no permission to modify them.
l Operators have permission to view and modify the configurations, status, alarms, and performance of
their own cells.
LMT
The LMT is used to perform routine maintenance on a single NE.

GBSS17.1&RAN17.1
When the U2000 client detects a fault in an NE, users can log in to the NE through the LMT to
locate, analyze, and rectify the fault.
l Log in to the BSC6900/BSC6910 LMT: Type the external virtual IP address of the OMU
in the address bar of the web browser. Press Enter or click Go next to the address bar to
visit the login page of the BSC6900/BSC6910.
l Log in to the BTS3900 LMT: Type the local maintenance IP address of the main control
board in the address bar of the web browser to visit the login page of Local Maintenance
Terminal.
NOTE
If the WMPT board is used, install the LMT client, and then type the local maintenance IP address
of the main control board on the LMT client to visit the login page of Local Maintenance
Terminal.
PuTTY
NOTE
PuTTY is an SSH client program that supports SSH and can be used for remotely logging in to the Linux
operating system.
You can use PuTTY to log in to the BSC6900/BSC6910 OMU to perform remote operation and
maintenance.
l Contact Huawei engineers to obtain PuTTY by performing the following operation:

Visit http://support.huawei.com/support/. Choose Software Center > Version
Software > Wireless Product Line > SingleRAN > SRAN O&M tools > Tools for
remote login linux to download the PuTTY software.
l Start PuTTY.
1. Double-click putty.exe. A dialog box PuTTY Configuration is displayed.
2. In the Specify the destination you want to connect to area, specify Host Name(or
IP address) by entering the IP address of the OMU board, and set Connection type
to SSH.
3. Click Open. Enter the user name and password of the operating system to log in to
the OMU.
NOTE
If the login fails, contact the administrator to check whether the login by a root user is prohibited
due to security hardening. If yes, log in to the OMU according to the instructions in "Switching from
Non-Root User to Root User" under "Disabling Root User Remote Login" in .
l BSC6900 GSM OMU Administration Guide
l BSC6900 GU OMU Administration Guide
l BSC6900 UMTS OMU Administration Guide
l BSC6910 GSM OMU Administration Guide
l BSC6910 GU OMU Administration Guide
l BSC6910 UMTS OMU Administration Guide

GBSS17.1&RAN17.1
3.3 GBSS&RAN Routine Maintenance Tasks Based on

Maintenance Frequency
Based on the maintenance frequency, routine maintenance is classified into daily, weekly, and
monthly maintenance.
3.3.1 Daily Maintenance Tasks

This section introduces daily maintenance tasks and their references, as listed in the following
table. You can perform specific maintenance tasks according to actual requirements.
Table 3-1 Daily maintenance tasks
SN Task Reference
1 Monitor the GBSS&RAN alarms. 4.1.2 Monitoring GBSS&RAN Alarms
2 Monitor the GBSS&RAN events. 4.1.3 Monitoring GBSS&RAN Events
3 Collect the GBSS&RAN alarm and 4.1.4 Collecting GBSS&RAN Alarm

event statistics. and Event Statistics
4 Monitor the performance counters. 4.2.1 Monitoring Performance

Counters
5 Save the performance measurement 4.2.2 Saving Performance

results. Measurement Results
6 Monitor the cell status. 4.3.1 Monitoring Cell Status
7 Monitor cell resources. 4.3.2 Monitoring Cell Resources
8 Query and save BSC6900/ 4.4 Querying and Saving BSC6900/

BSC6910 operation logs. BSC6910 Operation Logs
9 Query and save other logs of the 4.5 Querying and Saving Other Logs of
BSC6900/BSC6910. the BSC6900/BSC6910
10 Query and save the NodeB 4.6 Querying and Saving NodeB
operation logs. Operation Logs
11 Query and save other logs of the 4.7 Querying and Saving Other Logs of
NodeB. the NodeB
12 Check the GBTS running status. 4.8 Checking the GBTS Running
Status
13 Check the automatic NE backup 4.9 Checking the Scheduled NE

function. Backup Function

GBSS17.1&RAN17.1
3.3.2 Weekly Maintenance Tasks

This section introduces weekly maintenance tasks and their references, as listed in table. You
can perform specific maintenance tasks according to actual requirements.
Table 3-2 Weekly maintenance tasks
SN Task Reference
1 Perform the NE health check. 5.1 Performing NE Health Check
2 Check the running status of the OMU. 5.2 Checking the Running Status of
the OMU
3 Check the running status of the 5.3 Checking the Running Status of a
GBAM server. GBAM Server
4 Check the BSC6900/BSC6910 board 5.4 Checking the BSC6900/BSC6910

status. Board Status
5 Check the BTS board status. 5.5 Checking the Base Station Board
Status
6 Check the BSC6900/BSC6910 clock 5.6 Checking the BSC6900/BSC6910

status. Clock Status
7 Check the base station clock status. 5.7 Checking the Base Station Clock
Status
8 Back up and restore the GBSS&RAN 5.8 Backing Up and Restoring the
system data. GBSS&RAN System Data
9 Back up the license information. 5.9 Backing Up License Information
10 Analyze the performance 5.10 Analyzing Performance

measurement results. Measurement Results
11 Collect historical alarms and events. 5.11 Collecting Historical Alarm and
Event Statistics
12 Check the communication between 5.12 Checking Communication

NEs and the U2000. Between NEs and the U2000
3.3.3 Monthly Maintenance Tasks

This section introduces monthly maintenance tasks and their references, as listed in table. You
can perform specific maintenance tasks according to actual requirements.
Table 3-3 Monthly maintenance tasks
SN Task Reference
1 Analyze customer complaints. 6.1 Analyzing Customer Complaints

GBSS17.1&RAN17.1
SN Task Reference
2 Prepare an NE performance report. 6.2 Preparing an NE Running Report
3 Prepare a performance report. 6.3 Preparing a Performance Report
4 Check the disk space on the terminal 6.4 Checking the Disk Space on the
system. Terminal System
5 Check the maintenance terminal 6.5 Checking the Maintenance

system for viruses. Terminal System for Viruses
6 Check the connectivity of port links. 6.6 Checking the Connectivity of Port
Links
7 Check security patches for the OMU 6.7 Checking Security Patches for the
operating system. OMU OS
8 Check the OS hardening. 6.8 Checking OS Hardening
9 Check weak passwords and others. 6.9 Checking Weak Passwords and
Others
10 Update the OMU key. 6.10 Updating Key Material

GBSS17.1&RAN17.1
Routine Maintenance Guide 4 GBSS&RAN Daily Maintenance Guidelines
4 GBSS&RAN Daily Maintenance Guidelines
About This Chapter
This chapter provides guidelines for performing the daily maintenance tasks on the
GBSS&RAN.
4.1 Monitoring GBSS&RAN Alarms and Events

Active alarms and events of the BSC6900/BSC6910, NodeB, GBTS, and eGBTS can be
monitored on a U2000 client.
4.2 Monitoring the GBSS&RAN Performance
This section describes how to monitor the performance of the BSC6900/BSC6910, NodeB,
GBTS, and eGBTS and save the performance measurement results on a U2000 client.
4.3 Monitoring Cell Status and Cell Resources
You can monitor the cell status and cell resources on a U2000 client.
4.4 Querying and Saving BSC6900/BSC6910 Operation Logs
Operations performed by O&M engineers on the BSC6900/BSC6910 are recorded in operation
logs. These operation logs are used to locate faults. You are advised to browse and save the
operation logs on a U2000 client every day so that you can check whether any unauthorized
operations are performed on the equipment.
4.5 Querying and Saving Other Logs of the BSC6900/BSC6910
This section describes how to query and save other logs of a BSC6900/BSC6910 on a U2000
client. The other logs include the host log, OMU log, database log, system event log, operation
log, OMU installation log, remote upgrade log, and alarm information.
4.6 Querying and Saving NodeB Operation Logs
This section describes how to query and save the NodeB operations performed by the
administrator on a U2000 client. You can query the information on graphic user interface and
save the results in categories.
4.7 Querying and Saving Other Logs of the NodeB
This section describes how to query and save other logs of a NodeB on a U2000 client. The other
logs include NodeB one—click logs, cell RF information files, NodeB commissioning logs, DSP
exceptional logs, DSP running logs, RRU interference detection files, RRU interference
detection power files, and RTWP routine test result logs.

GBSS17.1&RAN17.1
4.8 Checking the GBTS Running Status

This section describes how to query the GBTS running status on a U2000 client or LMT.
4.9 Checking the Scheduled NE Backup Function

This section describes how to check the scheduled network element (NE) backup function on a
U2000 client. After this function is enabled, NE data is saved as backup files in a specified
directory on the U2000 server. This prevents data loss and helps NE data restoration when the
NE is faulty.

GBSS17.1&RAN17.1
4.1 Monitoring GBSS&RAN Alarms and Events

Active alarms and events of the BSC6900/BSC6910, NodeB, GBTS, and eGBTS can be
monitored on a U2000 client.
4.1.1 Alarm Handling Procedure

This section describes the alarm handling procedure. If the U2000 detects an alarm, handle the
alarm following the procedure described in this section.
Flowchart
Figure 4-1 shows the alarm handling flowchart.

GBSS17.1&RAN17.1
Figure 4-1 Alarm Handling Chart
Procedure Description
Table 4-1 lists the procedure for handling an alarm.
Table 4-1 Procedure for handling an alarm
St Operation Description
ep
1 Receive an alarm. After receiving an alarm, start the alarm handling procedure. To
ensure that you are notified in time after an alarm occurs, set alarm
notification methods on the U2000.

GBSS17.1&RAN17.1
St Operation Description
ep
2 View the alarm View the alarm details, including the alarm location, alarm help,
details. and alarm maintenance experience.
3 Acknowledge the Acknowledge the alarm to prevent it from being processed by

alarm. others.
4 Collect the fault Identify the alarm and query the alarm information to find out the
information. symptom of the alarm.
5 Analyze the Analyze the causes for the alarm based on the alarm symptom.
causes of the
alarm.
6 Work out the Work out the fault handling scheme according to the alarm details,
fault handling device manuals, network status, and maintenance experience.
scheme.
7 Carry out the Carry out the fault handling scheme to rectify the fault that leads to
fault handling the alarm.
scheme.
8 Clear the alarm. Clear the conditions that cause the alarm. After the alarm is cleared,
the U2000 receives a clear alarm.
9 Check whether Check the handling results after you rectify the fault.
the fault is
rectified.
10 Record the Record the maintenance experience when the alarm handling is
maintenance complete.
experience.
4.1.2 Monitoring GBSS&RAN Alarms

This section describes how to monitor active alarms of the BSC6900/BSC6910, NodeB, GBTS,
and eGBTS on a U2000 client.
Prerequisites
l You have logged in to the U2000 client, and it is correctly communicating with the related
NEs.
l You have the permission to query alarms.
Procedure
Step 1 On the U2000 client, choose Fault Management > Browse Alarm > Query Alarm Logs
(application style) or Monitor > Query Alarm logs (traditional style).

GBSS17.1&RAN17.1
Step 2 In the Filter dialog box, set search criteria. If you need to save the current settings of search
criteria, click Save Template, enter the template name, and click OK.
Step 3 Click OK. The active alarms are displayed on the Query Alarm Logs tab page.
NOTE
You are advised to set a template of daily search criteria using either of the following methods:
l Choose Template > Save As in the lower left area to save the current criteria as a template.
l Choose Template > Add to add a new template.
Step 4 Double-click an alarm to view the details in the displayed dialog box.
NOTE
In the Details dialog box, you can obtain the alarm handling suggestions by clicking the link in the Reason and
Advice area.
Step 5 Contact the related personnel to handle the uncleared alarms following the procedure in 4.1.1
Alarm Handling Procedure. Analyze the automatically cleared alarms.
Step 6 Click Modify in the Details dialog box to record the symptoms, causes, and handling procedures
in the Experience area.
Step 7 Repeat Step 4 through Step 6 to handle the alarms one by one until there is no active alarm on
the Query Alarm Logs tab page.
----End
4.1.3 Monitoring GBSS&RAN Events

This section describes how to monitor events of the BSC6900/BSC6910, NodeB, GBTS, and
eGBTS on a U2000 client.
Prerequisites
NEs.
l You have permission to query events.
Procedure
Step 1 On the U2000 client, choose Fault Management > Browse Alarm > Query Event Logs
(application style) or Monitor > Query Event logs (traditional style). The Filter dialog box is
displayed.
Step 2 In the Filter dialog box, set search criteria. If you need to save the current settings of search
criteria, click Save Template, enter the template name, and click OK.
Step 3 Click OK. The active events are displayed on the Query Event Logs tab page.
NOTE
You are advised to set a template of daily search criteria using either of the following methods:
Step 4 Double-click an event to view the details in the displayed dialog box.

GBSS17.1&RAN17.1
NOTE
In the Details dialog box, you can obtain the event handling suggestions by clicking the link in the Reason and
Advice area.
Step 5 Contact the related personnel to handle the events following the procedure in 4.1.1 Alarm
Handling Procedure.
Step 6 Click Modify in the Details dialog box to record the symptoms, causes, and handling procedures
in the Experience area.
Step 7 Repeat Step 4 through Step 6 to handle the events one by one.
----End
4.1.4 Collecting GBSS&RAN Alarm and Event Statistics

This section describes how to collect statistics on alarms and events of the BSC6900/
BSC6910, NodeB, GBTS, and eGBTS on a U2000 client by severity and type and how to save
the alarm and event statistics for easy query.
Prerequisites
NEs.
l You have permission to collect alarm and event statistics.
Procedure
Step 1 On the U2000 client, perform the following operations:
l To collect the alarm statistics, choose Fault Management > Browse Alarm > Alarm Log
Statistics (application style) or Monitor > Alarm Log Statistics (traditional style). The
Filter dialog box is displayed.
l To collect the event statistics, choose Fault Management > Browse Alarm > Event Log
Statistics (application style) or Monitor > Event Log Statistics (traditional style). The
Filter dialog box is displayed.
Step 2 In the Filter dialog box, set statistics collection criteria. If you need to save the current settings
of statistics collection criteria, click Save Template, enter the template name, and click OK.
Step 3 Click OK. The statistical results are displayed on the Alarm Log Statistics or Event Log
Statistics tab page.
NOTE
You are advised to set a template of daily statistics collection criteria using either of the following methods:
The statistical results are displayed on the Table and Pie tab pages.
l On the Table tab page, the results are displayed in a table.
l On the Pie tab page, the results are displayed in pie charts.
Step 4 Click Save as in the displayed dialog box, select the save path, file name, and file type for the
statistical results, and click Save.

GBSS17.1&RAN17.1
l If you click the Table tab, the results can be saved in .txt, .html, .csv, .pdf, .xlsx, or xls format.
If you save the results in .txt format, the coding scheme must be ISO-8859-1 or UTF-8. If
you save the results in .csv format and there are more than 256 columns in the .csv file, you
cannot open this file in the Excel format. In this case, you need to use UltraEdit or Notepad.
l If you click the Pie tab, the results can be saved in the .jpg format.
Step 5 Record the alarm statistics information in the Daily Maintenance Table.
----End
4.2 Monitoring the GBSS&RAN Performance

This section describes how to monitor the performance of the BSC6900/BSC6910, NodeB,
GBTS, and eGBTS and save the performance measurement results on a U2000 client.
4.2.1 Monitoring Performance Counters

This section describes how to query the measurement results of performance counters
reported at an interval of 5 minutes, 30 minutes, or 24 hours for UMTS, or 15 minutes, 60
minutes, or 24 hours for GSM on a U2000 client. Based on the measurement results, you can
determine whether the BSC6900/BSC6910, NodeB, GBTS, and eGBTS are running correctly.
Prerequisites
NEs.
l Measurement objects are available.
l You have permission to query measurement results of performance counters.
Context
Key performance indicators (KPIs) and performance counters are used to evaluate network
performance. You can choose specific KPIs and performance counters for routine maintenance
based on the network status and evaluation criteria.
Table 4-2 lists the recommended KPIs for monitoring on a UMTS network. Table 4-3 lists the
recommended KPIs for monitoring on a GSM network. Additionally, the recommended
performance counters are related to these recommended KPIs.

GBSS17.1&RAN17.1
NOTE
For details about definitions of the listed KPIs, see
l RAN KPI Reference
l GSBSS KPI Reference
l GBSS&RAN KPI Reference
. For details about counters related to KPIs, see
l BSC6900 UMTS Performance Counter Reference
l BSC6900 GSM Performance Counter Reference
l BSC6900 GU Performance Counter Reference
l BS6910 GSM Performance Counter Reference
.
Table 4-2 Recommended UMTS KPIs
KPI Type KPI Name
Accessibility Radio Access Success Ratio

PS Radio Access Success Ratio
CS Radio Access Success Ratio
RRC Setup Success Ratio
AMR RAB Setup Success Ratio
VP RAB Setup Success Ratio
VP RAB Setup Success Ratio
HSDPA RAB Setup Success Ratio
HSUPA RAB Setup Success Ratio
PS E-FACH RAB Setup Success Ratio
CS over HSPA RAB Setup Success Ratio
HSDPA 64QAM RAB Setup Success Ratio
HSDPA MIMO RAB Setup Success Ratio
Coverage Soft Handover Overhead
Mobility Soft Handover Success Ratio

Service Cell Change Success Ratio with SHO (H2H)
Inter-frequency Hard Handover Success Ratio
CS W2G Inter-RAT Handover Out Success Ratio
PS W2G Inter-RAT Handover Out Success Ratio
E-DCH Soft Handover Success Ratio
E-DCH Cell Change Success Ratio with SHO

GBSS17.1&RAN17.1
KPI Type KPI Name
Retainability CS Service Drop Ratio

AMR Call Drop Ratio
VP Call Drop Ratio
PS Call Drop Ratio
PS R99 Call Drop Ratio
PS BE Call Drop Ratio
HSDPA Call Drop Ratio
HSUPA Call Drop Ratio
Service Integrity Average UL Throughput for PS R99 Service

Average DL Throughput for PS R99 Service
HSDPA Throughput
HSUPA Throughput
Traffic R99 Service UL Traffic Volume

R99 Service DL Traffic Volume
CS Equivalent Erlang of RNC
Number of CS Users
Number of HSDPA Users
Number of HSDPA 64QAM Users
Number of HSDPA MIMO Users
HSDPA RLC Traffic Volume
Number of HSUPA Users
HSUPA RLC Traffic Volume
Table 4-3 Recommended GSM KPIs and Reference Values
KPI Reference Value
Immediate Assignment Success Rate > 92%
Assignment Success Rate > 94%
Call Establishment Success Rate > 92%
Call Drop Rate on TCH per Cell (Including Handover) < 2%
Call Drop Rate on TCH per Cell (Excluding Handover) < 2%
Call Drop Rate on SDCCH < 2%
TCH Congestion Rate (Overflow) < 5%
Congestion Rate on SDCCH per Cell (Due to Busy) < 5%

GBSS17.1&RAN17.1
KPI Reference Value
Intra-BSC Handover Success Rate > 92%
Incoming Inter-BSC Handover Success Rate > 86%
Outgoing Inter-BSC Handover Success Rate > 86%
Traffic Volume on TCH Depending on

network conditions
Traffic Call Drop Rate per Cell Depending on

network conditions
SDCCH Availability > 98%
TCH Availability > 98%
Uplink Assignment Success Rate > 90%
Downlink Assignment Success Rate > 80%
Uplink TBF Congestion Rate < 5%
Downlink TBF Congestion Rate < 5%
PDCH Occupation Rate Depending on

network conditions
Procedure
Step 1 Choose Performance > Result > Query Result (application style) or Performance > Query
Result (traditional style). The Query Result window is displayed.
If... Then...
A template is available Go to Step 2.
No template is available Go to Step 3.
Step 2 In the left Template navigation tree, double-click a template to check the performance counter
results.
Step 3 Click New Query.
Step 4 In the displayed New Query dialog box, perform the following operations:
1. In the Display By area of the left navigation tree, set query results to be displayed by Query
type or Function subset (Function subset by default). For UMTS, expand the BSC6900
UMTS or BSC6910 UMTS, for GSM, expand the BSC6900 GSM or BSC6910 GSM, for
GU, expand the BSC6900 GU or BSC6910 GU node and select the object type or function
subset to be queried. Then, the NE objects are listed in the Available Objects area in the
form of navigation tree.

GBSS17.1&RAN17.1
2. On the Object tab page, move the available objects to the Selected Objects list box.
3. On the Counter tab page, move the available counters to the Selected Counters area.
4. On the Other tab page, set search criteria in the Time Mode and Date Range areas.
5. Optional: If you need to save the preceding settings as a template, click Save Template.
6. Click Query. The query result is displayed.
NOTE
The query result can be displayed in three forms: table, line chart, and bar chart. You can specify the form
in the View area.
In the measurement result table, right-click a measurement result and choose Reliability from the shortcut
menu.
l If the original result is reliable, the message The reliability of original result is 100.00%. is displayed.
l If the original result is unreliable, a dialog box is displayed showing the reliability of the original result
and querying whether to query the details. To see the details, click Yes. The periods with reliability set
to 0 are displayed. Reliabilities of measurement results are displayed in different colors. Only the
measurement results in white are valid.
----End
Result
Compare the performance counter values with onsite reference values to check whether
performance counters can meet the onsite requirements.
Follow-up Procedure
If any measured value is inconsistent with the reference value, contact related engineers for
troubleshooting until all the performance counters meet the onsite requirements.
4.2.2 Saving Performance Measurement Results

This section describes how to save performance measurement results on a U2000 client to avoid
data loss.
Prerequisites
NEs.
l Performance measurement results have been generated. For details about how to query the
performance measurement results, see 4.2.1 Monitoring Performance Counters.
l You have permission to save performance measurement results.
Procedure
Step 1 In the Query Result window, click Save or use the shortcut menu to the save the information.
l If you click the Table tab, the results can be saved in .txt, .html, .csv, .pdf, .xlsx, or xls format.
If you save the results in .txt format, the coding scheme must be ISO-8859-1 or UTF-8. If
you save the results in .csv format and there are more than 256 columns in the .csv file, you
cannot open this file in the Excel format. In this case, you need to use UltraEdit or Notepad.

GBSS17.1&RAN17.1
----End
Result
You can obtain the performance measurement result file in the specified directory.
4.3 Monitoring Cell Status and Cell Resources

You can monitor the cell status and cell resources on a U2000 client.
4.3.1 Monitoring Cell Status

This section describes how to monitor cell status and record query results on a U2000 client.
Prerequisites
l You have logged in to the U2000 client, and it is correctly communicating with the
BSC6900/BSC6910.
l You have permission to run MML commands.
Context
UMTS cell status includes the operational state and administrative state. Table 4-4 lists details
about UMTS cell status.
Table 4-4 UMTS cell status and descriptions
Status Description
Operationa Whether a cell is available. When all necessary resources (such as common
l state channels and ports) of a cell are available and the administrative state of the
cell is Not blocked, Operational state of the cell is Available.
l Available: The cell is available and UEs can access the cell.
l Unavailable: UEs cannot access the cell.
Administra Whether a cell is blocked.

tive state l Local blocked: The cell cannot provide services, and UEs cannot access the
cell.
l High-priority block preparation: UEs that have accessed the cell are not
affected, but new UEs cannot access the cell.
l Not blocked: The cell cannot provide services, and UEs can access the cell.
GSM cell status includes: cell initialized, cell service, automatically blocked, and manually
blocked. Table 4-5 lists details about GSM cell status.

GBSS17.1&RAN17.1
Table 4-5 GSM cell status and descriptions
State Description
Cell Whether a cell has been initialized. A cell can enter the service state only after
initialized being initialized.
l Yes: The cell has been initialized.
l No: The cell has not been initialized.
Cell Whether a cell is in the service state, namely, whether a cell is running correctly.
service l Yes: The cell is in the service state.
l No: The cell is out of service.
Automatic Whether some TRXs in a cell are automatically blocked.

ally l Yes: Some TRXs in the cell are automatically blocked and these TRXs are
blocked unavailable.
l No: No TRX in the cell is automatically blocked. TRXs in the cell are
available.
Manually Whether some channels in a cell are manually blocked.

blocked l Yes: Some channels in the cell are manually blocked.
l No: No channel in the cell is manually blocked.
Procedure
Step 1 Choose Trace and Maintenance > Maintenance > MML Command (application style) or
Maintenance > MML Command (traditional style). The MML Command window is
displayed.
Step 2 Select the target BSC6900/BSC6910 in the left navigation tree. The navigation tree of
BSC6900/BSC6910 MML commands is displayed.
NOTE
If this method is used for the first time, the following message is displayed:
The MML command file of the current version does not exist. Are you sure you want to download
this file from the server?
Click Yes to start downloading the file. When the download is complete, click OK.
Step 3 For UMTS cells, run the DSP UCELL command with parameters set as follows to query the
operating status of all UMTS cells:
l Set Query type to BYCELL(Query by cell).
l Do not specify Cell ID.
Expected result: The value of Operational state of the cell is Available. If any returned result
is different from the expected result, contact the related engineers for troubleshooting until the
two are consistent. For details about command output descriptions, see Help Information.
Step 4 For GSM cells, run the DSP GCELLSTAT command and set parameters as follows to query
the operating status of all GSM cells:

GBSS17.1&RAN17.1
l Do not specify Index Type.

l Select CELLINIT(Cell Initialized), SRVSTAT(Cell Service State), AUTOCLOSE
(Blocked Automatically), CHLFAULT(Channel Fault), MANUALBLK(Blocked
Manually), and DYNSWITCH(Dynamic Switch) for the Cell Attribute parameter.
Expected result:
l The value of Cell Initialized is Yes.
l The value of Cell Service State is Yes.
l The value of Blocked Automatically is No.
l The value of Channel Fault is No.
l The value of Blocked Manually is No.
l The value of Cell Dynamic Switch is No.
If any returned result is different from the expected result, contact the related engineers for
troubleshooting until they are consistent. For details about command output descriptions, see
Help Information.
----End
Follow-up Procedure
To save the query results, right-click on the Common Maintenance tab page and choose Save
As from the shortcut menu. Specify the file name and path and click Save. The results are saved
as a file.
4.3.2 Monitoring Cell Resources

This section describes how to monitor cell resources on a U2000 client. This helps you determine
the current performance status of a cell. This section uses measurement objects as an example.
Prerequisites
NEs.
Context
The measurement counters listed in Table 4-6 are used to determine the current performance
status of a UMTS cell.

GBSS17.1&RAN17.1
Table 4-6 Measurement counters of UMTS cell resources
Performan Measurement Description Expected Result

ce Item Counter
Number of VS.CellDCHUEs Measurement object: The two counters

UEs in VS.CellFACHU UCELL provide the number of
different Es Location of counters: UEs using dedicated
RRC Measurement of Radio Cell channels and the number
connection Performance > RRC state of UEs using common
states in a measurement<Cell> channels, respectively.
cell If the values of both
counters are 0, there is no
UE in the cell and a fault
may occur in the cell.
Average VS.MeanRTWP Measurement object: These counters provide

received VS.MaxRTWP UCELL the uplink load in a cell.
total Location of counters: Cell load is directly
wideband VS.MinRTWP
Measurement of Radio Cell proportional to the
power Performance > Cell TX and measurement results of
(RTWP) in a RX Power Measurement these counters.
cell per cell
The measurement counters listed in Table 4-7 are used to determine the current performance
status of a GSM cell.
Table 4-7 Measurement counters of GSM cell resources
Performance Item Measurement Description Expected Result

Counter
Percentage of TCHs CELL.CHAN.BUS Measurement object: This counter

in the busy state Y.NUM.TCH.RATE GCELL provides the
Location of counters: percentage of busy
Measurement of TCHFs or TCHHs in
GSM Cell all cells within a
Performance measurement period.
(GCELL) > If the value of this
Channel State counter is 0, there is
Measurement per no UE in the cell, and
Cell a fault may occur in
(CHAN.StateNum. the cell.
CELL)

GBSS17.1&RAN17.1
Procedure
Step 1 Choose Performance > Result > Query Result (application style) or Performance > Query
Result (traditional style). The Query Result window is displayed.
Step 2 Click New Query.
1. Select the measurement object type in the left navigation tree.
2. Set parameters on the Object Settings, Counter Settings, and Other Settings tab pages.
NOTE
The query result can be displayed in three forms: table, line chart, and bar chart. You can specify the form
in the View Type area.
In the measurement result table, right-click a measurement result and choose Reliability from the shortcut
menu. In the displayed Information dialog box, click Yes. The periods with reliability set to 0 are displayed.
Reliabilities of measurement results are displayed in different colors. Only the measurement results in white
are valid.
Step 4 Compare the query results with the required values onsite. If they are inconsistent, contact related
engineers for troubleshooting until all the counters meet the onsite requirements.
----End
4.4 Querying and Saving BSC6900/BSC6910 Operation Logs

Operations performed by O&M engineers on the BSC6900/BSC6910 are recorded in operation
logs. These operation logs are used to locate faults. You are advised to browse and save the
operation logs on a U2000 client every day so that you can check whether any unauthorized
operations are performed on the equipment.
Prerequisites
BSC6900/BSC6910.
l BSC6900/BSC6910 operation logs have been synchronized to the U2000 server. For details
about how to synchronize and upload NE logs, see U2000 product documentation.
Context
Operation logs cover the information about the user, user type, terminal, start Time, end time,
result, operation command, information, NE type, NE name, and rollback command.
Procedure
l Using menus
1. On the U2000 client, choose Security Management > Log Management > Query
NE Operation Logs (application style) or System > Log Management > Query NE
Operation Logs (traditional style). The Filter Criteria dialog box is displayed.

GBSS17.1&RAN17.1
2. In the Filter Criteria window, set filter criteria, and click OK.
You can also click Cancel, and query logs in the Query NE Operation Logs window
using either of the following methods:
– Click Template, and select Open. Select a template from the template list, and
click Open to use an existing template to query logs.
– Click Filter. Set search criteria in the Filter Criteria window, and click OK to
query logs.
3. In the result query window, view NE operation logs by referring to the parameter
information in the following table.
Parameter Name Description
User Name of the user that performs an

operation.
User Type Domain attributes of the user

corresponding to an NE operation log,
such as EMS, Local, and EMSOP.
Terminal IP address of the terminal on which the

operation is performed.
Start Time Start time of the operation. The format

is consistent with Setting the Time
Format of the Client and Setting the
Date Format of the Client in the region
settings, for example, YYYY-MM-DD
HH:MM:SS.
End Time End time of the operation. The format is

consistent with Setting the Time
Format of the Client and Setting the
Date Format of the Client in the region
settings, for example, YYYY-MM-DD
HH:MM:SS.
Result Whether the operation is successful.
MML MML commands for performing

operations on an NE.
Information Details of the operation.
NE Type Type of the NE corresponding to the

operation.
NE Name Name of the NE corresponding to the

operation.

GBSS17.1&RAN17.1
Parameter Name Description
Rollback MML Rollback MML displays the MML

commands before Operation and helps
users to compare the operations before
and after data modification. For
example, in an NE operation log, MOD
GCELL: IDTYPE=BYID,
CELLID=0,
NEWCELLNAME="gcell2" is
executed after MOD GCELL:
IDTYPE=BYID, CELLID=0,
NEWCELLNAME="gcell3" if both
of the following conditions are met:
l The Operation column displays
MOD GCELL: IDTYPE=BYID,
CELLID=0,
NEWCELLNAME="gcell2".
l The Rollback MML column
displays MOD GCELL:
IDTYPE=BYID, CELLID=0,
NEWCELLNAME="gcell3",
If the value of Rollback MML is null,
the Rollback MML function is not
supported. Currently, the NEs that
support the Rollback MML function
are the BSC6900 GSM, BSC6910 GSM,
BSC6910 GU, and BSC6900 GU. The
following prerequisites must be met:
l The current operations refer to the
setting and modification operations
that support the rollback by
executing the MOD and SET
commands.
l The configuration authority on the
NE is enabled, and the quick
configuration mode is disabled.
NOTE
By default, the configuration authority
and the quick configuration mode on the
NE are both disabled. You can run the
SET QUICKCFG: MODE=ON;
command to enable the configuration
authority through the U2000 or the
LMT. You can run the SET
QUICKCFG: MODE=OFF;
command to disable the quick
configuration mode.

GBSS17.1&RAN17.1
NOTE
Right-click a log in the query window and choose Details from the shortcut menu, or double-
click the log to view the operation time, operation terminal, or results of the operation that
generates the log.
4. Save operation logs.
Perform the following operations as required:
– Click Print to print log query results.
– Click Save to save log query results in a file in the TXT, HTML, CSV, PDF, XLSX
or XLS format. The default file format is XLS.
l Running MML commands
1. On the U2000 client, choose Trace and Maintenance > Maintenance > MML
Command (application style) or Maintenance > MML Command (traditional
style). The MML Command window is displayed.
NOTE
If this method is used for the first time, you will be prompted with a message The MML
command file of the current version does not exist. Are you sure you want to download
this file from the server? Click Yes to start downloading the file. Click OK when the download
is complete.
2. Run the BKP LOGDB command to back up operation logs.
----End
Result
Operation logs are saved in the specified directory.
4.5 Querying and Saving Other Logs of the BSC6900/

BSC6910
This section describes how to query and save other logs of a BSC6900/BSC6910 on a U2000
client. The other logs include the host log, OMU log, database log, system event log, operation
log, OMU installation log, remote upgrade log, and alarm information.
Prerequisites
BSC6900/BSC6910.
Context
Table 4-8 provides the types, save paths, and description of other logs of the BSC6900/
BSC6910.

GBSS17.1&RAN17.1
Table 4-8 Information of other logs
Log Type Save Path Description
PFM_RESULT /bam/version_a/ftp/ The log records the traffic

(Performance Result File) COLLOGINFO/PFM-LOG/ statistics reported by a
network element (NE) to the
U2000. It is used for
analyzing traffic statistics.
PFM_NOM_RESULT /bam/version_a/ftp/ The log records the traffic

(Performance Result File in COLLOGINFO/PFM- statistics in normal periods
Normal Period) NOM-LOG/ reported by an NE to the
U2000. It is used for
analyzing traffic statistics.
HOST_PFM_RESULT /bam/version_a/ftp/ The log records the traffic

(Performance Result File COLLOGINFO/PFM-LOG/ statistics reported by a board
from Host) to the OMU. It is used for
analyzing board traffic
statistics.
ACTIVE_DEF_MEAS_FIL /bam/version_a/ftp/ This is the active definition

E(Active Default COLLOGINFO/PFM-LOG/ file for traffic statistics
Measurement Task File) delivered by the U2000 to an
NE. It is used for analyzing
traffic statistics.
STANDBY_DEF_MEAS_F /bam/version_a/ftp/ This is the standby definition

ILE(Standby Default COLLOGINFO/PFM-LOG/ file for traffic statistics
Measurement Task File) delivered by the U2000 to an
traffic statistics.
PFM_SWITCHS(The - Enumeration values are

Switches Information for reserved.
Performance)
HISTORY_ALARM /bam/version_a/ftp/ The log records all the alarms

(Historical Alarm File) COLLOGINFO/ALM-LOG/ and events reported by the
alarm and event reporting
and clearing.
HISTORY_FAULT /bam/version_a/ftp/ The log records all the faults

(Historical Fault File) COLLOGINFO/ALM-LOG/ which cause historical
alarms. It is used for
analyzing alarm reporting
and clearing.

GBSS17.1&RAN17.1
ALM_SYSTEM_CFG(The /bam/version_a/ftp/ The log records the

Configured Information of COLLOGINFO/ALM-LOG/ configuration information
Alarm) related to alarm
management. It is used for
analyzing alarm and event
reporting and clearing.
SECURITY_LOG(Security /bam/version_a/ftp/ This is the security log of an

Logs) COLLOGINFO/SEC-LOG/ NE. It is used for analyzing
the information about
historical security-related
operations.
OPT_LOG(Operation Logs) /bam/version_a/ftp/ This is the operation log of an

COLLOGINFO/OPT-LOG/ NE. It is used for analyzing
the operation and
maintenance on the NE.
OMU_LOG(The Log /bam/version_a/ftp/ This is the running log and

Information of OMU) COLLOGINFO/SINGLE- status log of the OMU. It is
BAM/ used for analyzing the OMU
problems and status.
OMU_SIM_LOG (Simple /bam/version_a/ftp/ The log records the OMU

OMU Log) COLLOGINFO/SINGLE- running information and
SIM-BAM/ status in a simple manner. It
is used for rapidly locating
OMU problems and
analyzing the status in
accident scenarios.
BSC_CFG_MML(The Data /bam/version_a/ftp/ The log records the BSC

Configure File of the BSC) COLLOGINFO/CFG-LOG/ configuration data
ExportCfgmml/ information. It is used for
checking the configuration
data during data restoration.
CELL_BASIC_INFO(The /bam/version_a/ftp/ The log records the cell basic

Basic Information of Cells) COLLOGINFO/CFG-LOG/ information. It is used for
CellBasicInfo/ checking the mapping
between the cell ID and
internal cell ID.
BSC_SERIES_NO(The /bam/version_a/ftp/ The log records the BSC

Series No. of the BSC) COLLOGINFO/CFG-LOG/ equipment serial number
(ESN) information. It is used
for license check. The ESN
uniquely identifies a BSC.

GBSS17.1&RAN17.1
DB_BAK(The Backup File /bam/version_a/ftp/ The log records the

of the Database) COLLOGINFO/CFG-LOG/ information of OMU
MysqlDbBak/ database that has been
backed up. It is used for data
restoration.
MEM_DB_BAK(The /bam/version_a/ftp/ The log records the

Backup File of the Database COLLOGINFO/CFG-LOG/ information of OMU
in Memory) MemDbBak/ memory database that has
been backed up. It is used for
locating the problem of
inconsistency between
memory database and
MYSQL database.
BTS_BASIC_INFO(The mbsc/bam/version_a/ftp/ The log records basic

Basic Information of Sites) COLLOGINFO/BTS-LOG information of base station
boards, base station
attributes, and base station
compressed logs. It is used
for analyzing basic base
station equipment
information.
BTS_CHECK_LOG(The mbsc/bam/version_a/ftp/ The log records base station

Examination File of BTS) COLLOGINFO/BTS-LOG logs, including temperature
logs, board replacement logs,
compressed logs, common
logs, and frequency scan
logs.
BTS_DEBUG_LOG(The mbsc/bam/version_a/ftp/ The log records base station

Debug File of BTS) COLLOGINFO/BTS-LOG logs, including temperature
logs, board replacement logs,
compressed logs, common
logs, and frequency scan
logs.
BTS_CHR_LOG(The CHR - Enumeration values are

Log of BTS) reserved.
TRX_LOG(The TRX Log) - Enumeration values are

reserved.
BTS_NET_TABLE(The Net - Enumeration values are

Table Information of BTS) reserved.

GBSS17.1&RAN17.1
DEBUG_LOG(The /bam/common/fam/ The log records the

Common Debug Log) famlogfmt/ information of abnormal
software running. It is used
for analyzing software
defects.
SDBG_LOG (Channel Fault /bam/common/fam/ The log records information

Log) famlogfmt/ about channel faults.
LAST_WORD(The Last /bam/common/fam The log records the last

Word Log) words information before the
board is abnormally reset. It
is used for locating the
problem of abnormal board
reset.
DSP_DEBUG_LOG(The /bam/common/fam/ The log records the DSP

Debug Log of DSP) famlogfmt/ abnormal information during
software running. It is used
for locating DSP faults.
HOST_LOG(The Running /bam/common/fam/famlog/ The log records the running

Log of the Host) status of the host.
2G_CHR_LOG(The CHR /bam/common/fam/ The log records the system

Log for GSM) famlogfmt/gchr/ resources used, call status
change time, and signaling. It
is used for analyzing whether
the call procedure is normal.
3G_CHR_LOG(The CHR /bam/common/fam/ The log records abnormal

Log for UMTS) famlogfmt/ call procedures except call
access and call drop. It is used
for analyzing the reason for
failed soft handover, hard
handover, relocation, or cell
update.
2G_UNILATERAL_CON- /bam/common/fam/ The log records the time of

NECT(The Unilateral famlogfmt/ and the system resources
Connection Log for GSM) used by the call with
problems, such as one-way
audio and cross-talk. It is
used for analyzing the cause
for voice faults.

GBSS17.1&RAN17.1
BSC_INFO(The Basic /bam/version_a/ftp/ The log records the BSC

Information of the BSC) COLLOGINFO/BSC-LOG/ software patch information,
and the bar code, software
information, hardware
information, loading
software information, and
license of each board. It is
used for querying whether
the software version, data,
and license loaded on the
board are correct.
GCSR_LOG(The CHR Log /bam/common/fam/ The log records the basic

for Single User of GSM CS) famlogfmt/ information of abnormal
calls, such as call initiating
time, site, cell, and TRX
where the call is initiated.
GPSR_LOG(The CHR Log /bam/common/fam/ The log records the basic

for Single User of GSM PS) famlogfmt/gphr/ information (such as cell
index, CGI, IMSI, and
TLLI), internal messages,
and messages over the Um,
Abis, and Gb interfaces for a
call. It is used for locating
faults during a PS call.
AIDG_LOG(A Interface /bam/common/fam/ The log records the A

Dial Diagnose Log) famlogfmt/ interface dialing test
information. It is used for
locating the call faults caused
by transmission failures on
the A interface.
BIOS_LOG(BIOS Log) /bam/common/fam/ The log records abnormal

famlogfmt/ running of the BIOS system
on the board. It is used for
locating BIOS faults.
CALLFAULT_LOG /bam/common/fam/ The log records network

(CALLFAULT Log) famlogfmt/ access failures and call drops.
It is used for analyzing the
cause for network access
failures and call drops.

GBSS17.1&RAN17.1
PCHR_LOG(PCHR Log) /bam/common/fam/ The log records detailed

famlogfmt/pchr information about each call,
including service access, call
release, handover, dynamic
channel configuration
control (DCCC), and signal
quality. It is used for key
performance indicator (KPI)
analysis and as a reference
when handling user
complaints.
SYSFAULT_LOG /bam/common/fam/ The log records serious

(SYSFAULT Log) famlogfmt/sysfault/ software or hardware faults,
such as resource leakage and
device fault. It is used for
network health check.
NOTE
l version_a is the active workspace of OMU. When the active workspace of the OMU is version_b,
change "version_a" in the preceding save paths to "version_b".
l The following log files will not be saved: files that are not compressed in the BZ2 format in the OMU
active workspace installation directory\common\fam\famlog and the OMU active workspace
installation directory\common\fam\famlogfmt directories.
Procedure
Step 1 On the U2000 client, choose Trace and Maintenance > Maintenance > MML Command
(application style) or Maintenance > MML Command (traditional style). The MML
Command window is displayed.
Step 2 Select the target NE in the left navigation tree. The navigation tree of BSC6900/BSC6910 MML
commands is displayed.
NOTE
If this method is used for the first time, you will be prompted with a message The MML command file
of the current version does not exist. Are you sure you want to download this file from the server?
Click Yes to start downloading the file. Click OK when the download is complete.
Step 3 Run the COL LOG command with the parameters set as follows to query logs:
l Set Type to ALL.
l Set Start Time to maintenance start time of the last day and End Time to the current
maintenance start time.
----End

GBSS17.1&RAN17.1
Result
The directories of log files collected this time can be obtained by running the LST
LOGRSTINFO command. The amount and directory are different lied on the log type.
4.6 Querying and Saving NodeB Operation Logs

This section describes how to query and save the NodeB operations performed by the
administrator on a U2000 client. You can query the information on graphic user interface and
save the results in categories.
Prerequisites
l The U2000 client and server are correctly communicating with each other.
l You have synchronized U2000 user logs with NodeB operations logs. For details about
how to synchronize logs, see U2000 Product Documentation.
Procedure
Step 1 On the U2000 client, choose Security Management > Log Management > Query NE
Operation Logs (application style) or System > Log Management > Query NE Operation
Logs (traditional style).
Step 2 In the displayed Filter Criteria dialog box, set search criteria for the NE operation logs.
Table 4-9 Parameters for querying NE operation logs
Search Criteria Description Setting
User Query NE operation logs by

user. Click , and then select
one or multiple items from
the Select User dialog box.
Terminal Query NE operation logs by

terminal. Click , and then select
one or multiple items from
the Select Terminal dialog
box.
User Type Query NE operation logs by Select one or multiple items

user type. from the User Type area.
The user type can be Local,
EMS, or EMSOP.
Result Query NE operation logs by Select one or multiple items

operation result. from the Result area.
The result can be Succeeded
or Failed.

GBSS17.1&RAN17.1
Search Criteria Description Setting
MML Query NE operation logs by Enter the MML command to

MML command. be filtered out in the text box
in the MML area.
NOTE
The filtering of MML
commands supports the
accurate search. You only need
to enter a part of an MML
command, and then the system
queries the NE operation logs
containing the entered MML
command.
Time Range Query NE operation logs by Select From and To, and
time range. enter the date and time in the
From indicates the start time, text box. Alternatively, click
and To indicates the end , and in the Select Time
time. dialog box, set the date and
the time.
For example, set the time
range to 2012-02-09
00:00:00 2013-02-09
00:00:00.
NE Name Query NE operation logs by

Click , and then
NE.
select one or multiple items
from the Select NE dialog
box.
Step 3 Click OK. The query results are displayed in the Query NE Operation Logs window.
Perform either of the following operations as required:

l Click Print to print the statistical result.
l Click Save to save the statistical result.
----End
4.7 Querying and Saving Other Logs of the NodeB

This section describes how to query and save other logs of a NodeB on a U2000 client. The other
logs include NodeB one—click logs, cell RF information files, NodeB commissioning logs, DSP
exceptional logs, DSP running logs, RRU interference detection files, RRU interference
detection power files, and RTWP routine test result logs.
Prerequisites
l The U2000 client and server are properly communicating with each other.

GBSS17.1&RAN17.1
l The FTP server has been set up.

l The FTP server has been configured in the same Intranet as the NodeB and they are properly
communicating with each other.
l No firewall has been configured between the FTP server and NodeB.
l You have the permission to run MML commands for querying NodeB information.
Procedure
l Performing menu operations on the U2000 client:
1. On the U2000 client, choose Software Management > NE File > NE File
Transfer (application style) or Software > NE File Transfer (traditional style).
The Software Browser tab and the NE File Transfer window are displayed.
2. Perform the following operations:
a. Set Direction to From NE to OSS Client.
b. Select the NE type from the NE type dropdown list.
c. Set File type to Other.
d. Select the corresponding base station in the NEs to Be Selected area.
e. Select the types of the files to be uploaded in the Files to Be Selected area.
f. Set the corresponding parameters in the Set Parameter area.
g. Set Local path in the Destination Path area to specify the path of the logs saving
on the client.
h. Click OK, and the upload starts.
l Running MML commands on the U2000 client:
2. Select a NodeB in the left navigation tree. The navigation tree of the NodeB MML
commands is displayed.
3. Run the ULD FILE command with the related parameters specified to upload NodeB
logs to a specified path. For details about parameter descriptions, see Table 4-10.
Table 4-10 Parameter description
Base Paramete Description

Station r
Type
3900 series Function Specifies the system that the base station supports.
WCDMA Type For the NodeB NE, select NODEB.
base station

GBSS17.1&RAN17.1
Base Paramete Description

Station r
Type
Source File Specifies the types of the file to be uploaded.

Type When Function Type is NODEB, you can set this
parameter to one in the following:
l BRDLOG-NODEB(NODEB Compositive Log)
l CELLRFINFO(CELL RF Information File)
l DBGLOG-NODEB(NODEB Commissioning
Log)
l DSPEXPT(DSP Exceptional Log)
l DSPRUNLOG(DSP Running Log)
l RRUIQDATA(RRU Interference Detection file)
l RRURXPOWER(RRU Interference Detection
power file)
l RTWPTEST(RTWP Routine Test Result Log)
Destinatio Specifies the file to be uploaded to the FTP server.

n File
Name
IP Mode Specifies the IP mode, including IPV4 and IPV6.
FTP Server Specifies the FTP server that stores data files to be
IP uploaded.
User Name Specifies the user name for logging in to the FTP
server.
Password Specifies the password for logging in to the FTP server.
Compressi Specifies whether to use the compressed mode.

on Flag
Guage Specifies whether to indicate the progress of file

Option transfer.
Flow Specifies whether to implement flow control.

Control
Option
The NodeB logs are backed up and saved in the specified path on the FTP server.
----End
4.8 Checking the GBTS Running Status

This section describes how to query the GBTS running status on a U2000 client or LMT.

GBSS17.1&RAN17.1
Prerequisites
l You have logged in to the U2000 client or BSC LMT, and the U2000 client is correctly
communicating with the BSC6900/BSC6910.
Context
You are advised to use the U2000 to query the running status of multiple base stations and use
the LMT to query the running status of a single base station.
Expected result: All the GBTSs are running correctly.
You can query the running status of multiple GBTSs simultaneously, which facilitates
maintenance and troubleshooting because information of all faulty GBTSs or boards is displayed
at a time. By routinely querying the information in this way, you can obtain the running status
of the GBTSs and promptly replace faulty boards.
Procedure
l Checking the running status using an MML command on the U2000
1. Choose Network Monitor > Maintenance > MML Command (application style)
or Maintenance > MML Command (traditional style). The MML Command
window is displayed.
2. Run the DSP BTSSTAT command to query the running status of base stations.
l Checking the running status using the LMT GUI
1. Click Device Maintenance. The Device Maintenance window is displayed.
2. On the BTS Maintenance tab page, choose BTS Maintenance > Query BTS
Running Status. The Query BTS Running Status tab page is displayed.
3. On the BTS Running Status Query tab page, select a base station and click
Confirm to query the running status of the base station.
NOTE
Alternatively, you can right-click a base station in Device Navigation Tree and choose Query
BTS Running Status to query the running status.
----End
4.9 Checking the Scheduled NE Backup Function

This section describes how to check the scheduled network element (NE) backup function on a
U2000 client. After this function is enabled, NE data is saved as backup files in a specified
directory on the U2000 server. This prevents data loss and helps NE data restoration when the
NE is faulty.
Prerequisites
You have logged in to the U2000 client, and it is correctly communicating with the related NEs.

GBSS17.1&RAN17.1
Context
Before checking the NE backup function, learn about the following information:
l A scheduled backup file must be named AUTOBAKDATA+current time.

l Avoid enabling the scheduled NE backup function during busy hours because this function
occupies too many system resources.
l The scheduled NE backup task can be performed once or periodically (by day, week, or
month).
l The U2000 supports a maximum of 50 scheduled NE backup tasks.
l A maximum of three backup files can be stored on the U2000 server for each NE, including
manual and scheduled backup files. When the fourth backup file is generated on the U2000
server, the earliest backup file will be removed.
Procedure
Step 1 On the U2000 client, choose System Settings > Task Schedule > Task Management
(application style) or Maintenance > Task Management (traditional style). The Task
Management window is displayed.
Step 2 In the left navigation tree, expand Backup and click NE Backup to check whether there are any
existing scheduled NE backup tasks.
If... Then...
There are existing scheduled NE backup The scheduled NE backup function is normal.
tasks
There is no scheduled NE backup task Perform Step 3 through Step 7.
Step 3 Click New. The New Task dialog box is displayed.
Step 4 Set the basic information about the task as follows:
1. Enter a name in the Task Name text box.

2. Set Task Type to NE Backup.
3. Set Execution Type to Periodic.
Step 5 Click Next, and specify Start Time and Period Settings. In the Period Settings area, specify
Repeat times or End time.
NOTE
The value of Start time must be later than the current time on the server.
Step 6 Click Next, set Backup Type to By NE, and select target NEs.
Step 7 Click Finish.
----End

GBSS17.1&RAN17.1
Result
After settings of the scheduled NE backup are completed, you can obtain backup files of the
target NEs in the specified directory.
Follow-up Procedure
l If there is no scheduled backup file, check the status of the scheduled NE backup task.
Ensure that the scheduled NE backup task is functional.
l If the scheduled NE backup task fails, you can manually back up data. For details, see 5.8.2
Manually Backing up NE Data (on the U2000).
l To permanently reserve the backup files, you can download them to a local PC. For details,
see section "Viewing/Downloading NE Backup Files" in U2000 Product Documentation.

GBSS17.1&RAN17.1
Routine Maintenance Guide 5 GBSS&RAN Weekly Maintenance Guidelines
5 GBSS&RAN Weekly Maintenance

Guidelines
About This Chapter
This chapter provides guidelines for performing the weekly maintenance tasks on the
GBSS&RAN.
5.1 Performing NE Health Check

This section describes how to perform health check on the BSC6900/BSC6910, NodeB, GBTS,
and eGBTS on a U2000 client. The NE health check is carried out based on the default
maintenance scenario.
5.2 Checking the Running Status of the OMU

This section describes how to check the OMU running status on a U2000 client. The check items
are the OMU server status, basic configuration information, operational state, data
synchronization status, running status of service modules, and consistency between startup types
of service modules and active/standby OMUs.
5.3 Checking the Running Status of a GBAM Server

This section describes how to check the running status of a GBAM server regularly. The check
items include the CPU usage, memory usage, and hard disk space. You can perform the check
only on the BSC6900.
5.4 Checking the BSC6900/BSC6910 Board Status

This section describes how to check the BSC6900/BSC6910 board status and board subsystem
status on a U2000 client or LMT.
5.5 Checking the Base Station Board Status

This section describes how to check the status of a base station board on a U2000 client or LMT.
5.6 Checking the BSC6900/BSC6910 Clock Status

This section describes how to check the clock status of a GCGa/GCGb/GCUa/GCUb board on
a U2000 client or LMT.
5.7 Checking the Base Station Clock Status

This section describes how to check the clock status of a base station on a U2000 client or LMT.

GBSS17.1&RAN17.1
5.8 Backing Up and Restoring the GBSS&RAN System Data

This section describes how to back up the system data on the U2000 client. The system data
consists of the configuration data, performance data, and alarm data.
5.9 Backing Up License Information

This section describes how to back up BSC6900/BSC6910 license information and NodeB,
GBTS, and eGBTS license allocation information. The backup can be performed automatically
on a U2000 or manually on an LMT.
5.10 Analyzing Performance Measurement Results

This section describes how to analyze performance measurement results on a U2000 client. You
are advised to collect the performance measurement results of a week. If measurement results
show performance counter fluctuations, analyze them based on the network conditions.
5.11 Collecting Historical Alarm and Event Statistics

This section describes how to collect statistics about historical alarms and events on the U2000
client based on the alarm severity, alarm ID, or network management type. It also describes how
to obtain the statistical tables and analytic diagrams and how to save the statistical results. The
procedures for collecting alarm and event statistics are the same. The following part focuses on
the collection of alarm statistics.
5.12 Checking Communication Between NEs and the U2000

This section describes how to check the communication between NEs and a U2000 in the network
topology.

GBSS17.1&RAN17.1
5.1 Performing NE Health Check

This section describes how to perform health check on the BSC6900/BSC6910, NodeB, GBTS,
and eGBTS on a U2000 client. The NE health check is carried out based on the default
maintenance scenario.
Prerequisites
BSC6900/BSC6910, NodeB, GBTS, and eGBTS.
l You have permission to perform NE health check.
Context
Table 5-1 lists the BSC6900/BSC6910 health check items.
Table 5-1 BSC6900/BSC6910 health check items
No. Check Item
1 Interface status
2 BTS running status
3 Network performance
4 Cell status
5 Software version
6 License
7 Board status
8 Hardware
9 Clock status
10 OMU status
11 Physical transmission link
Procedure
Step 1 Create an NE health check task.
1. On the U2000 client, choose Trace and Maintenance > Monitor > NE Health Check
(application style) or Maintenance > Network Health Check > NE Health Check
(traditional style).
2. In the NE Health Check window, click on the upper left. The Create Task dialog box
is displayed.

GBSS17.1&RAN17.1
3. In the displayed dialog box, choose Maintenance from the Scenario drop-down list. The
Task Name text box will be automatically filled based on the application scenario and the
task creating time (accurate to second).
4. Select target NEs for health check in the Select NEs area.
5. In the Execution Type area, select Scheduled.
6. Click Next. In the displayed dialog box, set Health check period. Then, Click Finish.
NOTE
The executed health check task is listed under the Finished Tasks node in the navigation tree on the left
side.
Step 2 Check the NE health check result.

1. Expand the Finished Tasks node in the navigation tree on the left side. Right-click a
finished task and choose View Report from the shortcut menu.
2. In the displayed Health Check Report dialog box, click HTML Format or DOC
Format to open the report.
If... Then...
The HTML format is selected Select the report from the report list and view the
report in either of the following ways:
l Click Open to directly open the report in the
HTML format.
l Click Save As and select the path for saving the
report in the displayed Save dialog box to save the
report in the HTML format.
The DOC format is selected Select the report from the report list and view the
report in either of the following ways:
l Click Open to directly open the report in the DOC
format.
l Click Save As and select the path for saving the
report in the displayed Save dialog box to save the
report in the DOC format.
NOTE
The health check report is compressed as a .zip file. To view the report, double-click the .zip file,
and double-click the report file "index.html" in the .zip file browser.
----End
Result
In the NE health check report, the values of Not Passed and Failed to Execute are 0 and all the
check items listed in Manually Checked have passed the check.

GBSS17.1&RAN17.1
Follow-up Procedure
l If the values of Not Passed and Failed to Execute are not 0, perform the following
operations:
1. Click the number in the corresponding cell. For example, if the value of Failed to
Execute is not 0, click the number in the cell under Failed to Execute.
2. Check the items in the displayed check item list one by one according to Solution
until all the items have passed the check.
3. In the left navigation tree on the NE Health Check tab page, expand Finished
Tasks, right-click the target task, and choose Restart. If the value of Not Passed and
Failed to Execute are still not 0, continue troubleshooting until both values are 0.
l If any check item listed in Manually Checked fails to pass the check, perform the following
operations:
1. Click the number in the cell under Manually Checked.
2. Check the items in the displayed check item list one by one according to Solution
until all the items have passed the check.
5.2 Checking the Running Status of the OMU

This section describes how to check the OMU running status on a U2000 client. The check items
are the OMU server status, basic configuration information, operational state, data
synchronization status, running status of service modules, and consistency between startup types
of service modules and active/standby OMUs.
Prerequisites
BSC6900/BSC6910.
Procedure
Step 1 On the U2000 client, choose Trace and Maintenance > Maintenance > MML Command
Step 2 Select the BSC6900/BSC6910 in the left navigation tree. The navigation tree of BSC6900/
BSC6910 MML commands is displayed.
NOTE
If this method is used for the first time, you will be prompted with a message The MML command file
of the current version does not exist. Are you sure you want to download this file from the server?
Click Yes to start downloading the file. Click OK when the download is complete.
Step 3 Run the DSP OMUSRV command to query the OMU running status.
Expected result: Free space of each partition on the OMU hard disk is at least 20%.
Step 4 Run the DSP OMU command to query the basic configuration information, operational state,
and data synchronization status of active and standby OMU subsystems.
Expected result:

GBSS17.1&RAN17.1
l The values of Computer name, Internal network fixed IP, External network fixed IP,
Internal network virtual IP, and External network virtual IP in query results are the same
as those planned.
l The values of Operational state for active and standby OMUs are Active normal and
Standby normal, respectively. For an independent OMU, the value of Operational state is
Normal. The values of Internal network virtual IP state, External network virtual IP
state, Internal network link state, External network link state, and Backup network link
state are all Normal.
l The value of Data-sync state for active and standby OMUs is Data synchronization is
successful.
Step 5 Run the DSP OMUMODULE command to query the running status and startup types of the
service modules of active and standby OMUs.
Table 5-2 provides the expected results.
Table 5-2 Expected results of checking running status of service modules of the OMUs
Check Item Expected Result
Status of the active l The value of State of all service modules is Started.
OMU l The value of Startup Type is Automatic.
Status of the For debug_log, ftp_server, omu_manager, sntp, and software:

standby OMU l The value of State is Started.
l The value of Startup Type is Automatic.
Step 6 Optional: When the OMU works in active/standby mode, run the CHK PEERCFG command
to query the configuration information about the active and standby OMUs.
Expected result: The configurations of active and standby OMUs are Consistent.
----End
Follow-up Procedure
If any operation result is inconsistent with the expected result in the preceding operations,
perform the following operations:
l If Free space of each partition on the OMU hard disk is less than 20%, remove useless
files from the OMU server by performing the following operations:
1. Run the SSH terminal (for example, PuTTY) on the PC and enter the OMU IP address
to log in to the OMU.
2. Run the cd target directory command to go to the directory where the useless files
are located.
3. Run the rm file name or rm -r folder name command to remove useless files.
NOTE
Ensure that you have execute permission for this command before running this command.

GBSS17.1&RAN17.1
l If the OMU configuration information is not the same as the planned configuration, modify
the OMU configuration accordingly.
l If the OMU operational state and data synchronization state is Abnormal, troubleshoot the
fault according to handling suggestions for ALM-20704 OMU Data Synchronization
Failure.
l If the running status of the OMU modules is inconsistent with the expected result,
troubleshoot the fault according to handling suggestions for ALM-20707 OMU Process
Abort.
l When the OMU works in active/standby mode and the configurations between the active
and standby OMUs are inconsistent, modify the configurations according to the planned
data to ensure the configuration consistency.
5.3 Checking the Running Status of a GBAM Server

This section describes how to check the running status of a GBAM server regularly. The check
items include the CPU usage, memory usage, and hard disk space. You can perform the check
only on the BSC6900.
Prerequisites
BSC6900.
Context
Check and clean up the hard disk space of the GBAM server regularly to ensure that the available
space in each directory is at least 20% of the total space.
Check the size and usage of the GBAM server memory and the swap space. Before installing
the OMU software, ensure that the available space of the memory is at least 512 MB.
Procedure
Step 1 On the U2000 client, choose Network Monitor > Maintenance > MML Command
Step 2 Select the BSC6900 in the left navigation tree. The navigation tree of BSC6900 MML commands
is displayed.
Step 3 Run the DSP OMUSRV command to query the OMU running status.
If the available space of any partition on the OMU hard disk is less than 20%, perform the
following operations:
l Run the SSH terminal (for example, PuTTY) on the PC and enter the OMU IP address to log
in to the OMU.
l Run the cd target directory command to go to the directory where the files to be deleted are
located.
l Run the rm file name or rm -r folder name command to remove unnecessary files in this
folder.

GBSS17.1&RAN17.1
NOTE
Ensure that you have execute permission for this command before running this command.
----End
5.4 Checking the BSC6900/BSC6910 Board Status

This section describes how to check the BSC6900/BSC6910 board status and board subsystem
status on a U2000 client or LMT.
Prerequisites
BSC6900/BSC6910.
l You have logged in to the LMT, and it is correctly communicating with the BSC6900/
BSC6910.
Context
l For a BSC6900, the status of DSP subsystems on the DPUa/DPUb/DPUc/DPUd/DPUe/
DPUf/DPUg/DEUa board is queried, and the status can be queried only by running MML
commands.
l For a BSC6910, the status of subsystems on all boards except EOMUa and ESAUa board
is queried, and the status can be queried only by running MML commands.
Procedure
l Checking the board status or board subsystem status using an MML command on the U2000
1. Choose Trace and Maintenance > Maintenance > MML Command (application
style) or Maintenance > MML Command (traditional style). The MML
2. Select the BSC6900/BSC6910 in the left navigation tree. The navigation tree of
NOTE
is complete.
3. Run the DSP BRD command with Status set to FAULT(FAULT) to query all the
faulty boards.
Expected result: No board Status is FAULT(FAULT).
4. For a BSC6900, run the DSP DSP command with Subrack No. specified to query
the DSP status of the DPUa/DPUb/DPUc/DPUd/DPUe/DPUf/DPUg/DEUa board in
a specific subrack. In this step, do not specify Slot No.
Expected result: The value of DSP operational state is Normal.
5. For a BSC6910, run the DSP SUBSYS command to query the subsystem status of the
faulty board in a specific subrack. In this step, set Operator Type to BYPOS(By
Position) and Status to FAULT(FAULT), and specify Subrack No.

GBSS17.1&RAN17.1
Expected result: The values of State for all subsystems are all not FAULT
(FAULT).
l Checking the board status using the LMT GUI
1. On the LMT, click Device Maintenance. The Device Maintenance tab page is
displayed in the BSC device panel.
2. In the BSC device panel, right-click a target board and choose Query BSC Board
Information from the shortcut menu. The Query BSC Board Information dialog
box is displayed.
Expected result:
– For a BSC6900, if the board works in independent mode, CPU status is
Normal; if the board works in active/standby mode, CPU status of the active board
is Active normal and CPU status of the standby board is Standby normal.
– For a BSC6910, if the board works in independent mode, Board status is
Normal; if the board works in active/standby mode, Board status of the active
board is Active normal and Board status of the standby board is Standby
normal.
3. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device
> Query BSC Board Information. The Query eCoordinator Board Information
dialog box is displayed.
4. Set parameters in the Query BSC Board Information dialog box and click Query
to query the board information.
NOTE
You can also query the board status in the following way: right-click a board on the BSC device
panel and choose Query BSC Board Information from the shortcut menu.
Expected result:
– For a BSC6900, if the board works in independent mode, CPU status is
Normal; if the board works in active/standby mode, CPU status of the active board
is Active normal and CPU status of the standby board is Standby normal.
– For a BSC6910, if the board works in independent mode, Board status is
Normal; if the board works in active/standby mode, Board status of the active
board is Active normal and Board status of the standby board is Standby
normal.
----End
Follow-up Procedure
l If the board status is Fault, contact the related engineers to rectify the fault. Ensure that the
status of all boards is Normal. For an active/standby board, the status of the active board
is Active normal and the status of the standby board is Standby normal.
5.5 Checking the Base Station Board Status

This section describes how to check the status of a base station board on a U2000 client or LMT.

GBSS17.1&RAN17.1
Prerequisites
l You have logged in to the U2000 client and the LMT, and they are correctly communicating
with the related NEs.
Procedure
l Checking the GBTS board status using an MML command on the U2000 client
3. Run the DSP BTSBRD command to query the status of a board in a specific subrack.
l Checking the status of an eGBTS or NodeB board using an MML command on the U2000
client
2. Select the target in the left navigation tree. The navigation tree of MML commands
is displayed.
3. Run the DSP BRD command to query the status of a specific base station board.
l Checking the status of a GBTS board using the GUI on the LMT
1. Click Device Maintenance. The BSC Device Panel tab page is displayed in the
Device Maintenance window.
2. In the Device Navigation Tree, expand BSC and click a base station. The device
panel of this base station will be displayed in the BTS Device Panel tab page.
3. In the BTS device panel, right-click a board that can be detected, and choose Query
Board Information from the shortcut menu. The Query Board Information dialog
box is displayed.
l Checking the status of an eGBTS or NodeB board using the GUI on the LMT
2. On the Device Panel tab page, select the target base station from the left pane. The
device panel of the base station is displayed on the Device Panel tab page.
3. In the BTS device panel, right-click a board that can be detected, and choose Query
Board Information from the shortcut menu. The Query Board Information dialog
box is displayed.
----End
Follow-up Procedure
If any fault occurs on a board, contact the related engineers to rectify the fault. Ensure that the
status of all boards is Normal.

GBSS17.1&RAN17.1
5.6 Checking the BSC6900/BSC6910 Clock Status

This section describes how to check the clock status of a GCGa/GCGb/GCUa/GCUb board on
a U2000 client or LMT.
Prerequisites
BSC6900/BSC6910.
BSC6910.
Context
The BSC6900/BSC6910 The clock source is divided into five levels: 0 to 4. Level 0 indicates
that the clock works in the free run state. Levels 1 to 4 indicate the levels of an external clock
source. Level 1 indicates the highest level and level 4 indicates the lowest level. If no clock
source is configured and the clock status is free run or if the configured clock source is
unavailable, the system uses the clock source as the system clock. The clock source on each
level can be configured with only one clock type,and the status of clock source on each level
includes:
l Initialization: The clock source of this level is not configured.

l Available: The clock source of this level can be used.
l Unavailable: The clock source of this level cannot be used.
The BSC6900/BSC6910 clock synchronization status includes:
l Free-run: The board just starts up or no clock source is available now.

l Fast tracking: A clock source is available, and the clock source enters the fast tracking
mode.
l Trace: The clock source meets the precision requirement, and the clock source enters the
trace state.
l Holdover: If the source clock is not running correctly during the trace state, the clock source
enters the holdover state.
NOTE
l You are advised to query the clock running status of GCGa/GCGb/GCUa/GCUb boards only. For these
boards, you can query the clock source status and phase-locked loop status of the current clock.
l For the BSC6900, the GCGa/GCGb/GCUa/GCUb boards are permanently configured in slots 12 and
13 in the main processing subrack (MPS).
l For the BCS6910BSC6910, the GCGa/GCGb/GCUa/GCUb boards are permanently configured in slots
14 and 15 in the MPS.
Procedure
l Checking the clock source status by using an MML command on the U2000

GBSS17.1&RAN17.1
NOTE
is complete.
3. Run the DSP CLK command to query the status of clock boards in the MPS. In this
step, set Subrack No. to the MPS subrack No. and specify Slot No.
l Checking the clock source status using the LMT GUI
2. On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device
> Query BSC Board Clock Status. The Query BSC Board Clock Status dialog
box is displayed.
3. Set parameters in the Query BSC Board Clock Status dialog box and click Query
to query the board clock status.
You can also query the board clock status in the following way: right-click a clock
board on the BSC device panel and choose Query BSC Board Clock Status from
the shortcut menu.
4. Right-click a board on the BSC device panel and choose Query BSC Board Clock
Status from the shortcut menu to query the BSC board clock status.
----End
Result
The clock source status and phase-locked loop status of the current clock vary depending on the
transmission mode:
l In hybrid transmission mode, the system must be configured with a clock source:
– Clock source state with levels 0 through 4 is Available.
– Phase-locked loop state of current clock is Trace.
l In all-IP transmission mode, the system is not configured with a clock source:
– Clock source state with levels 1 through 4 is Initialization.
– Clock source state with levels 0 is Available.
– Phase-locked loop state of current clock is Free running.
Follow-up Procedure
In hybrid transmission mode, if Clock source state is Unavailable or Phase-locked loop state
of current clock is Unknown, the clock source is lost. In this case, contact related engineers
for troubleshooting and ensure that Clock source state and Phase-locked loop state of current
clock are the same as those described in the operation results.

GBSS17.1&RAN17.1
5.7 Checking the Base Station Clock Status

This section describes how to check the clock status of a base station on a U2000 client or LMT.
Prerequisites
NEs.
l You have logged in to the LMT, and it is correctly communicating with the related NEs.
Procedure
l Checking the GBTS clock status using an MML command on the U2000 client
3. Run the DSP BTSATTR command with BTS Attribute set to CLKATTR to query
the clock attributes of a base station.
l Checking the status of an eGBTS or NodeB clock using an MML command on the U2000
client
2. Select the target in the left navigation tree. The navigation tree of MML commands
is displayed.
3. Run the DSP CLKSTAT command to query the clock status of a specific base station.
l Checking the status of a GBTS clock using the GUI on the LMT
2. On the BTS Maintenance tab page, choose BTS Maintenance > Query BTS
Attribute. The Query BTS Attribute tab page is displayed.
3. On the Query BTS Attribute tab page, select Clock Attribute in the Select
Attribute drop-down list box and click Query to query the clock attribute of a base
station clock.
l Checking the status of an eGBTS or NodeB clock using the GUI on the LMT
2. On the Device Panel tab page, select the target base station from the left pane. The
device panel of the base station is displayed on the Device Panel tab page.
3. In the BTS device panel, right-click the main control board and choose Query Clock
Current Status from the shortcut menu. The Query Clock Current Status dialog
box is displayed.
----End

GBSS17.1&RAN17.1
Follow-up Procedure
Normally, Clock attribute and Management state of the GBTS are Available and Lock,
respectively. Current clock source state of the eGBTS and NodeB is Normal. If the query
results are inconsistent with the preceding values, the clock source is not functional. Contact the
related engineers for troubleshooting.
5.8 Backing Up and Restoring the GBSS&RAN System Data

This section describes how to back up the system data on the U2000 client. The system data
consists of the configuration data, performance data, and alarm data.
5.8.1 Creating a Scheduled Backup Task (on the U2000)

This section describes how to create a scheduled task of backing up the BSC6900/BSC6910,
NodeB, GBTS, and eGBTS data on a U2000 client. After this task is created, NE data is saved
as backup files in a specified directory on the U2000 server. This prevents data loss and helps
NE data restoration when the NE is faulty.
Prerequisites
NEs.
l You have permission to back up data.
Context
A maximum of three backup files can be stored on the U2000 server for each NE, including
manual and scheduled backup files. If a new backup file is generated when there have been three
backup files on the U2000 server, the earliest one will be removed.
Procedure
Step 1 On the U2000 client, choose System Settings > Task Schedule > Task Management
(application style) or Maintenance > Task Management (traditional style). The Task
Management window is displayed.
Step 2 Click New. The New Task dialog box is displayed.
Step 3 Set the basic information about the task as follows:

1. Enter a name in the Task Name text box.
2. Set Task Type to NE Backup.
3. Set Execution Type to Periodic.
Step 4 Click Next, and specify Start Time and Period Settings. In the Period Settings area, specify
Repeat times or End time.
NOTE
The value of Start time must be later than the current time on the server.
Step 5 Click Next and select All NEs, By NE Type, By NE, or By Region for Backup Type.

GBSS17.1&RAN17.1
Step 6 Click Encryption Option to specify whether to encrypt NE backup files or not.
If you need to encrypt the files, select Enable Encryption and specify Passcode and Confirm
Passcode. If you do not need to encrypt the files, deselect Enable Encryption.
Step 7 Click Finish.
----End
Result
If the NE data is backed up regularly, you can obtain backup files in the specified directory after
the scheduled backup task is completed.
Follow-up Procedure
l If no backup file exists in the specified directory, check the status of the scheduled backup
task. If the status is Suspended, the task cannot be performed. If you need to resume the
scheduled backup task, see section "Resuming Timing Tasks" in U2000 Product
Documentation.
l If the scheduled NE backup task fails, you can manually back up data. For details, see 5.8.2
Manually Backing up NE Data (on the U2000).
l To permanently reserve the backup files, you can download them to a local PC. For details,
see section "Viewing/Downloading NE Backup Files" in U2000 Product Documentation.
5.8.2 Manually Backing up NE Data (on the U2000)

This section describes how to manually back up network element (NE) data on a U2000 client.
Manual backup is an alternative method for backing up NE data.
Prerequisites
NEs.
l The FTP server has been configured.
l You have permission to back up data.
Context
Before manually backing up the NE data, learn the following information:
l A manual backup file must be named BAKDATA+current time.

l A maximum of three backup files can be stored on the U2000 server for each NE, including
a maximum of one manual or scheduled backup file. If a new backup file is generated when
there have been three backup files on the U2000 server, the earliest one will be removed.
Procedure
Step 1 On the U2000 client, choose Software Management > NE File > NE Backup (application
style) or Maintenance > Backup Management > NE Backup (traditional style). The NE
Backup window is displayed.

GBSS17.1&RAN17.1
Step 2 Choose the NE type, expand the navigation tree, and select an NE.
l You can press and hold Ctrl to select multiple NEs at a time. To select all the NEs, click the
root node.
l If the selected NE contains sub-NEs, a dialog box is displayed, prompting you whether to
back up the data of all the sub-NEs under the selected NE. You can choose to back up data
of all the sub-NEs or only some of them.
Step 3 Click Backup, and then click Yes in the displayed Confirm dialog box.
Step 4 Click Encryption Option to specify whether to encrypt NE backup files or not.
If you need to encrypt the files, select Enable Encryption and specify Passcode and Confirm
Passcode. If you do not need to encrypt the files, deselect Enable Encryption.
----End
Result
When the backup task is started, the progress and detailed information about the backup task
are displayed on the Immediate Task tab page at the bottom of the NE Backup window. When
the manual backup is completed, you can obtain the manual backup files by clicking Path in the
NE Backup List area.
Follow-up Procedure
To permanently reserve the backup files, you can download them to a local PC. For details, see
section "Viewing/Downloading NE Backup Files" in U2000 Product Documentation.
5.8.3 Restoring NE Data (on the U2000)

This section describes how to restore the backup network element (NE) data stored on a U2000
server on an NE by using a U2000 client.
Prerequisites
NEs.
l You have permission to restore data.
Context
NOTICE
After the data restoration is completed, the NE will restart.
You can use only one backup file at a time for restoring NE data. The backup files can be either
of the following:
l Scheduled backup files or manual backup files stored on the U2000 server
l Backup files uploaded from a local PC to the U2000 server

GBSS17.1&RAN17.1
Only one backup file for each NE can be uploaded to the U2000 server. If another backup file
is uploaded, the previous one will be removed.
NOTE
Restoring the backup file on the NE will change NE data. Ensure that the backup file to be uploaded is
downloaded from the U2000 server to the local PC.
Procedure
Step 1 On the U2000 client, choose Software Management > NE File > NE Backup (application
style) or Maintenance > Backup Management > NE Backup (traditional style). The NE
Backup window is displayed.
Step 2 Choose the NE type, expand the navigation tree, and select an NE.
NOTE
You can click the root node to select multiple NEs at a time. To select all the NEs, directly select the root
node.
Step 3 Select a backup file from NE Backup List or press and hold Ctrl to select multiple backup files
from NE Backup List at a time.
Step 4 Click Restore, and then click Yes in the displayed Confirm dialog box.
----End
Result
If the NE data restoration is completed and the NE is running correctly, the NE data is
successfully restored.
Follow-up Procedure
Perform NE health check. For details about how to the check, see 5.1 Performing NE Health
Check. In the NE Health Check Report, ensure that the values of Not Passed and Failed to
Execute are both 0. Manually check the listed items in Manually Checked and ensure that all
have passed the check.
5.8.4 Manually Backing Up and Restoring NE Data (on the LMT)

This section describes how to manually back up and restore BSC6910 data by running MML
commands on the LMT.
Prerequisites
You have logged in to the BSC6910 LMT.
Context
You can back up and restore system data on a U2000. However, you can only use the LMT when
no U2000 is configured on the network or when the related network elements (NEs) cannot
communicate with the U2000.

GBSS17.1&RAN17.1
NOTICE
l Back up the system data on the active OMU if the OMUs work in active/standby mode.
l Back up the OMU database before you perform capacity expansion or upgrade.
Procedure
l Backing up the system data by running an MML command
1. Run the BKP DB command with Path of Backup File and Backup File Name
specified to back up the data in a specified directory on the OMU hard disk.
2. Obtain the backup data file from the specified path.
If you need to encrypt the backup data file, set Encrypted Mode to Password
Encrypted and specify File Encryption Password for the file.
Expected result: After the backup is completed, you can obtain the specific system backup
file in the specified directory.
l Restoring the system data by running MML commands
1. Run the RTR DB command to with File Name specified to restore the system data
on the OMU server.
If the file to be restored has been encrypted, set Encrypted Mode to Password
Encrypted and enter the specified File Encryption Password.
2. Run the RST BSC command so that the restored configuration data takes effect.
Expected result: After the system data is restored, the NE is working correctly and services
are running.
----End
Follow-up Procedure
After the system data backup is completed, you are advised to upload the backup system data
to a U2000 server.
After the system data restoration is completed, perform NE health check according to operations
in 5.1 Performing NE Health Check. In the NE Health Check Report, ensure that the values
of Not Passed and Failed to Execute are both 0. Manually check the listed items in Manually
Checked and ensure that all have passed the check.
5.9 Backing Up License Information

This section describes how to back up BSC6900/BSC6910 license information and NodeB,
GBTS, and eGBTS license allocation information. The backup can be performed automatically
on a U2000 or manually on an LMT.
Context
Currently, the U2000 supports only the periodic license information backup for the BSC6900/
BSC6910.

GBSS17.1&RAN17.1
l The backup file is stored in the following directory on the U2000 server: /export/home/
sysm/ftproot/NE type/License/NE FDN. The NE FDN is an ID that uniquely identifies
a network element (NE).
l The backup file is named after the license, for example: ON1020093_GO1.dat.
l There is no restriction on the number of license backup files that can be saved on the server.
However, the name of a backup file cannot be a duplicate of an existing file on the U2000
server; otherwise, the backup file will overwrite the existing file.
l The backup can be performed for a specific NE type or NE once or periodically (by day,
week, or month).
The U2000 manages NodeB, GBTS, and eGBTS licenses in a centralized manner. During routine
maintenance, you can export and save the license allocation information for all NodeBs, GBTSs,
and eGBTSs under a BSC6900/BSC6910 at a time.
Procedure
l Automatically backing up BSC6900/BSC6910 license information on the U2000
1. On the U2000 client, choose System Settings > Task Schedule > Task
Management (application style) or Maintenance > Task Management (traditional
style). The Task Management window is displayed.
2. Click New. The New Task dialog box is displayed.
3. Set the basic information about the task as follows:
a. Enter a name in the Task Name text box.
b. Set Task Type to NE License Backup.
c. Set Execution Type to Periodic.
4. Click Next, and specify Start Time and Period Settings. In the Period Settings area,
specify Repeated times or End Time based on the actual requirement.
NOTE
The values of Start time must be later than the current time on the server.
5. Click Next and select Backup Type and a target NE.
6. Click Finish.
Expected result: After the automatic backup is completed, you can obtain the backup file
of the target NE in a specified directory.
l Manually backing up BSC6900/BSC6910 license information on the LMT
1. Log in to the BSC6900/BSC6910 LMT and click FTP Tool at the upper right corner
to start the local FTP server.
2. Run the BSC6900/BSC6910 command ULD LICENSE to upload the BSC6900/
BSC6910 license file to the PC through FTP. In this step, enter the IP address of the
local PC in IP Address, a directory for saving the backup file in Directory, and a file
name in File Name.
NOTE
The file name must contain .dat, for example, BSC01LIC.dat.
Expected result: You can obtain the backup file of the target NE in the specified directory.
l Backing up NodeB license allocation information

GBSS17.1&RAN17.1
1. On the U2000 client, choose Software Management > NE License > NodeB
(application style) or License > NE License Management > NodeB (traditional
style). The NodeB License Management window is displayed.
2. In the NodeB License Management window, click . In the displayed Export

License File dialog box, choose a NE, specify the path and file name for exporting
the file, and click Confirm.
NOTE
After the file export starts, you can check the progress on the FTP Task tab page in the NodeB
License Management window. After the export is completed, you can check the exported
information locally.
The NodeB license allocation information is exported in the .csv format.
l Backing up eGBTS license allocation information
1. On the U2000 client, choose Software Management > NE License > eGBTS
(application style) or License > NE License Management > eGBTS (traditional
style). The eGBTS License Management window is displayed.
2. In the left navigation tree in the eGBTS License Management window, click an
eGBTS. The operator and license information about the eGBTS is displayed in the
right pane. Specify a local path and a file name for saving the backup file. Then, click
OK.
NOTE
After the file export starts, you can check the progress on the FTP Task tab page in the eGBTS
License Management window. After the export is completed, you can check the exported
information locally.
The eGBTS license allocation information is exported in the .csv format.
----End
5.10 Analyzing Performance Measurement Results

This section describes how to analyze performance measurement results on a U2000 client. You
are advised to collect the performance measurement results of a week. If measurement results
show performance counter fluctuations, analyze them based on the network conditions.
Prerequisites
NEs.
l Measurement objects are available.
Context
For details about performance counters, see

GBSS17.1&RAN17.1

You can specify the routine maintenance standards based on the network conditions and
assessment standards.
Procedure
Step 1 On the U2000 client, choose Performance > Result > Query Result (application style) or
Performance > Query Result (traditional style). The Query Result window is displayed.
Step 2 In the lower area of the Query Result window, click New Query.
1. Select the object type or function subset in the left navigation tree.
2. On the Object, Counter, and Other tab pages on the right pane, specify the object, counter,
and period for measurement.
NOTE
The query result can be displayed in three forms: table, line chart, and bar chart.
Step 4 Compare the performance counter values with those required for the office. If the values are
inconsistent, contact the related engineers for troubleshooting.
----End
5.11 Collecting Historical Alarm and Event Statistics

This section describes how to collect statistics about historical alarms and events on the U2000
client based on the alarm severity, alarm ID, or network management type. It also describes how
to obtain the statistical tables and analytic diagrams and how to save the statistical results. The
procedures for collecting alarm and event statistics are the same. The following part focuses on
the collection of alarm statistics.
Prerequisites
NEs.
l You have permission to collect alarm and event statistics.
Context
Table 5-3 lists alarm statistical modes. You can choose any of them based on the actual
requirement.

GBSS17.1&RAN17.1
Table 5-3 Alarm statistical modes
Alarm Statistical Mode Description
By alarm severity The alarm statistics are collected based on the alarm
severity.
Alarms have four severities: critical, major, minor,
and warning.
By alarm ID The alarm statistics are collected based on the alarm

ID.
By network management type The alarm statistics are collected based on the
network management type.
Procedure
l Collecting alarm statistics according to statistical conditions
1. On the U2000 client, choose Fault Management > Browse Alarm > Alarm Log
Statistics (application style) or Monitor > Alarm Log Statistics (traditional style).
The Filter dialog box is displayed.
2. In the displayed Filter dialog box, set fault alarm statistical conditions, and then click
OK.
NOTE
The statistical results are displayed on the Table and Pie tab pages.
l On the Table tab page, the results are displayed in a table.
l On the Pie tab page, the results are displayed in pie charts.
l Collecting alarm statistics according to template
1. Choose Fault Management > Browse Alarm > Alarm Log Statistics (application
style) or Monitor > Alarm Log Statistics (traditional style).
2. In the displayed Filter dialog box, click Cancel.
3. In the Alarm Log Statistics window, click Template. If no template is available,
select Add to create a template.
4. In the Add Template dialog box, specify Template name and Description, and set
Share to Yes. Then, click Next.
5. In the Filter Criteria dialog box, set alarm statistical conditions and click Finish.
6. In the Confirm dialog box, click Yes. The statistics of historical alarms are displayed.
----End
Follow-up Procedure
1. Right-click an alarm in the Alarm Log Statistics window and choose Save As to save the
selected or all the results in a file.
l If you click the Table tab, the results can be saved in .txt, .html, .csv, .pdf, .xlsx, or xls
format. If you save the results in .txt format, the coding scheme must be ISO-8859-1 or
UTF-8. If you save the results in .csv format and there are more than 256 columns in

GBSS17.1&RAN17.1
the .csv file, you cannot open this file in the Excel format. In this case, you need to use
UltraEdit or Notepad.
2. On the Table tab page, click Print to print the results.
5.12 Checking Communication Between NEs and the U2000

This section describes how to check the communication between NEs and a U2000 in the network
topology.
Prerequisites
l You have logged in to the U2000 client and the U2000 client and server are communicating
l You have the required permission.
Context
All the NEs are communicating with the U2000. If the communication between an NE and the
U2000 is interrupted, there is an icon on the upper left of the NE, as shown in Figure
5-1.
Figure 5-1 U2000 network topology

GBSS17.1&RAN17.1
Procedure
Step 1 Log in to the U2000 and choose Topo View > Topology > Main Topology (application style)
or Topology > Main Topology (traditional style) to check the status of all NEs in the topology.
----End
Follow-up Procedure
Most connectivity problems are caused by network failures. If any connectivity problem occurs,
contact system engineers for troubleshooting.

GBSS17.1&RAN17.1
Routine Maintenance Guide 6 GBSS&RAN Monthly Maintenance Guidelines
6 GBSS&RAN Monthly Maintenance

Guidelines
About This Chapter
This chapter provides guidelines for performing the monthly maintenance tasks on the
GBSS&RAN.
6.1 Analyzing Customer Complaints

This section describes how to locate the causes and tendency of faults, facilitating problem
handling at points of frequent faults.
6.2 Preparing an NE Running Report

This section describes how to prepare an NE running report. Collecting statistics about fault
alarms on a monthly basis helps analyze the fault alarms generated on the BSC6900/
BSC6910, NodeB, GBTS, and eGBTS and prepare the NE running report.
6.3 Preparing a Performance Report

This section describes show to prepare a performance report by analyzing the performance of
the BSC6900/BSC6910, NodeB, GBTS, and eGBTS according to the fault occurrence tendency.
6.4 Checking the Disk Space on the Terminal System

This section describes how to check the disk space on the terminal system. The disk space
available on the terminal system must meet specified requirements.
6.5 Checking the Maintenance Terminal System for Viruses

This section describes how to check and maintain the maintenance terminal system for keeping
it free of any virus. The maintenance terminal system consists of the U2000 client and LMT.
6.6 Checking the Connectivity of Port Links

This section describes how to check the connectivity of port links.
6.7 Checking Security Patches for the OMU OS

This section describes how to check security patches for the OMU operating system (OS)and
configure the system security policy in real time to ensure stable running of the system.
6.8 Checking OS Hardening

GBSS17.1&RAN17.1
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.
6.9 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.
6.10 Updating Key Material

The key material(key parameter) needs to be updated periodically (recommended period: 6
months) to prevent it from being disclosed.

GBSS17.1&RAN17.1
6.1 Analyzing Customer Complaints

This section describes how to locate the causes and tendency of faults, facilitating problem
handling at points of frequent faults.
Prerequisites
Customer complaint records are obtained.
Context
Handle the GSM faults by referring to the GBSS Troubleshooting Guide.
l For details about how to handle the UMTS faults, see RAN Troubleshooting Guide.
l For details about how to handle the GSM faults, see GBSS Troubleshooting Guide.
Procedure
Step 1 Based on customer complaints, collect information about faults on a monthly basis and identify
the scope and category of the faults.
Step 2 Locate the causes of the faults. To be specific, analyze and compare possible causes until the
root cause is identified.
Step 3 Collect statistics on the monthly faults and analyze the fault tendency.
Step 4 Collect fault and exception statistics on a monthly basis, locate problems, and handle the
problems.
Step 5 Summarize the troubleshooting experience and offer suggestions.
----End
6.2 Preparing an NE Running Report

This section describes how to prepare an NE running report. Collecting statistics about fault
alarms on a monthly basis helps analyze the fault alarms generated on the BSC6900/
BSC6910, NodeB, GBTS, and eGBTS and prepare the NE running report.
Context
Table 6-1 lists the alarm statistics collection modes. You can select the collection mode
according to the actual requirements and the number of alarms generated in the month.

GBSS17.1&RAN17.1
Table 6-1 Alarm statistics collection methods
Alarm Statistics Collection Mode Description
By alarm severity The alarm statistics are collected based on the alarm
severity.
There are four alarm severities: critical, major,
minor, and warning.
By alarm ID The alarm statistics are collected based on the alarm

ID.
By alarm type The alarm statistics are collected based on the alarm
type.
By top N base stations with the The alarm statistics about the current monitoring
maximum number of alarms group are collected based on the number of alarms
generated on the base stations in this group.
The system collects statistics on the N base stations
that have the maximum number of alarms and the
alarms generated by the base stations.
By top N cells with the maximum The alarm statistics about the current monitoring
number of alarms group are collected based on the number of alarms
generated in the cells in this group.
The system collects statistics on the N cells that
have the maximum number of alarms and the alarms
generated in the cells.
By top N signaling links with the The alarm statistics about the current monitoring
generated on the signaling links in this group.
The system collects statistics on the N cells that
have the maximum number of alarms and the alarms
generated on the signaling links.
By top N E1/T1 links with the The alarm statistics about the current monitoring
generated on the E1/T1 links in this group.
The system collects statistics on the N E1/T1 links
that have the maximum number of alarms and the
alarms generated on the E1/T1 links.
Procedure
Step 1 Obtain the performance measurement results in the month by referring to 5.10 Analyzing
Performance Measurement Results.
Step 2 Analyze the performance measurement results to know the performance change tendency.

GBSS17.1&RAN17.1
Step 3 Collect statistics about alarms generated in this month by referring to 4.1.4 Collecting
GBSS&RAN Alarm and Event Statistics.
Step 4 Analyze the historical alarms to know the running status of NEs.
Step 5 Prepare a monthly NE running report according to the performance measurement results and
historical alarms.
----End
6.3 Preparing a Performance Report

This section describes show to prepare a performance report by analyzing the performance of
the BSC6900/BSC6910, NodeB, GBTS, and eGBTS according to the fault occurrence tendency.
Context
For details about performance counters that you need to focus on and collect, see GBSS KPI
Reference,RAN KPI Reference,GBSS&RAN KPI Reference.
Procedure
Step 1 Locate and analyze the faults occurring in this month. For details, see 6.2 Preparing an NE
Running Report.
Step 2 Collect the monthly performance data, such as performance statistics, historical performance
data, and system monitoring data. Catch the change tendency in the monthly performance data.
Step 3 Collect daily and weekly monitoring reports on routine network performance, and then catch
the performance change tendency.
Step 4 Prepare a monthly performance report according to the collected statistics.
----End
6.4 Checking the Disk Space on the Terminal System

This section describes how to check the disk space on the terminal system. The disk space
available on the terminal system must meet specified requirements.
Prerequisites
l You have logged in to the U2000 client.
l You have permission to remove files from the OMU.
Context
The specified requirements for the disk space are as follows:
l For the U2000 client, the available space on the hard disk is at least 50% of the total capacity.

GBSS17.1&RAN17.1
l The available space of each partition on the OMU hard disk is at least 20% of the partition
capacity.
Procedure
Step 1 Check the available space on the hard disk of the U2000 client. If the available space is lower
than 50% of the total capacity, delete the temporary files, unnecessary software programs, and
unnecessary backup files.
Step 2 Check the available space of each partition on the OMU hard disk by referring to 5.2 Checking
the Running Status of the OMU. If the available space is lower than 20% of the capacity of
each partition, delete the temporary files and unnecessary backup files.
NOTICE
Generally, files are removed only by engineers of the operator. However, Huawei engineers can
remove the files from the hard disk only with the permission of these engineers if required.
----End
6.5 Checking the Maintenance Terminal System for Viruses

This section describes how to check and maintain the maintenance terminal system for keeping
it free of any virus. The maintenance terminal system consists of the U2000 client and LMT.
Prerequisites
You have permission to operate the U2000 client and LMT.
Context
A maintenance terminal system with viruses causes configuration data exceptions and
maintenance failures.
Procedure
Step 1 Update the antivirus database.
Step 2 Remove viruses on the computer by using copyrighted antivirus software.
----End
6.6 Checking the Connectivity of Port Links

This section describes how to check the connectivity of port links.

GBSS17.1&RAN17.1
Prerequisites
BSC6900/BSC6910.
l The port is enabled with the Ethernet Port Load Sharing function.
Procedure
l Checking the connectivity of BSC6900/BSC6910 port links on the U2000 client
NOTE
If the method is used for the first time, you will be prompted with a message asking whether
you want to download this file from the server. Click Yes to continue. Click OK when the
download is complete.
2. Run the PING IP command with related parameters specified to check the
connectivity of port links.
In the returned results, the packet loss rate should be 0. If the rate is not 0, perform
Step 3.
3. Run the TRC IPADDR command with related parameters specified to check the
connectivity between different pieces of equipment. Troubleshoot the equipment with
connectivity problems.
l Checking the connectivity of port links of the eGBTS or NodeB on the U2000 client
NOTE
If the method is used for the first time, you will be prompted with a message asking whether
you want to download this file from the server. Click Yes to continue. Click OK when the
download is complete.
2. Run the PING command with related parameters specified to check the connectivity
of port links.
In the returned results, the packet loss rate should be 0. If the rate is not 0, perform
Step 3.
3. Run the TRC IPADDR command with related parameters specified to check the
connectivity between different pieces of equipment. Troubleshoot the equipment with
connectivity problems.
----End
6.7 Checking Security Patches for the OMU OS

This section describes how to check security patches for the OMU operating system (OS)and
configure the system security policy in real time to ensure stable running of the system.

GBSS17.1&RAN17.1
Prerequisites
l You have logged in to the LMT.
l You have permission to execute MML commands on the LMT.
NOTE
Check security patches for the OMU OS every half a year.
Context
l You do not need to install security patches for the OMU OS if the BSC6900 OMU OS is
SUSE Linux.
l This document uses an upgrade in dual-OMU mode as an example. The upgrade in single-
OMU mode is similar.
Procedure
l Checking the security patch version of the OMU OS (BSC6900)
– Windows OS
The Windows Server 2003 operating system matching the OMU is about to be end of
service (EOS) and needs to be switched to the latest Dopra Linux operating system.
– Dopra Linux OS
1. Visit http://support.huawei.com/ and log in using the account of a Huawei
engineer. Choose Software > Wireless Network > GSM&UMTS&LTE >
SingleRAN > SingleRAN MBSC > MBSC O&M tools to check the latest
security patch version of the OMU OS.
Figure 6-1 uses a DopraLinuxV200R003C02SPC090 patch package as an
example to show the name format of a Dopra Linux OS patch package on the
technical support website. Check the latest patch version based on the upload time.
Figure 6-1 Name format of a DOPRA Linux OS patch package
2. Run the LST VER command to query the patch version of the current BSC6900
OMU OS (including active and standby OMUs), which is indicated by OS service
pack version in the command output.
3. Check whether the patch version queried in 1 is the same as that queried in 2. If
yes, no more operations are required. If no, go to Installing Security Patches for
the OMU Operating System.
l Installing Security Patches for the OMU OS (BSC6900)
NOTICE
OMU services need to be stopped and OMU boards need to be reset during the security
patch installing procedure. This disconnects the OMU from the U2000 but does not affect
services.

GBSS17.1&RAN17.1
– Windows OS/SUSE Linux OS

SingleRAN > SingleRAN MBSC > SRAN O&M tools to obtain
Dopra_Linux_USB Disks.zip.
2. Decompress the package to obtain Operation Guide to Switching OMU Operating
System Through USB Disks.
3. Switch the operating system to the Dopra Linux operating system of the latest
version by referring to Operation Guide to Switching OMU Operating System
Through USB Disks.
– Dopra Linux OS

SingleRAN > SingleRAN MBSC > MBSC O&M tools to obtain Guide to Dopra
Linux Operating System Remote Patch Upgrade.
2. Install security patches by referring to the downloaded Guide to Dopra Linux
Operating System Remote Patch Upgrade.
l Checking the security patch version of the OMU OS (BSC6910)
1. Visit http://support.huawei.com/ and log in using the account of a Huawei engineer.

Choose Software > Wireless Network > GSM&UMTS&LTE > SingleRAN >
SingleRAN MBSC > MBSC O&M tools to check the latest security patch version
of the OMU OS.
NOTE
Take a Doprax86_64RTOS-V100R001C00SPC080 OS patch package as an example, the name
format of the patch package on the technical support website is
RTOSV100R001C00SPC080.zip. Check the latest patch version based on the upload time.
2. Run the LST VER command to query the patch version of the current BSC6910 OMU
OS (including active and standby OMUs), which is indicated by OS service pack
version in the command output.
3. Check whether the patch version queried in 1 is the same as that queried in 2. If yes,
no more operations are required. If no, go to Installing Security Patches for the
OMU Operating System.
l Installing security patches for the OMU OS (BSC6910)
NOTICE
OMU services need to be stopped and OMU boards need to be reset during the security
patch installing procedure. This disconnects the OMU from the U2000 but does not affect
services.

Choose Software > Wireless Network > GSM&UMTS&LTE > SingleRAN >
SingleRAN MBSC > MBSC O&M tools to obtain BSC6910 Guide to RTOS Remote
Patch Upgrade.

GBSS17.1&RAN17.1
2. Install security patches by referring to the downloaded BSC6910 Guide to RTOS

Remote Patch Upgrade.
----End
6.8 Checking OS 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.
Prerequisites
Procedure
l Checking whether the OMU OS hardening is required
Whether to harden the OMU OS is checked based on the type of the OMU OS. If the OMU
works in active/standby mode, perform the following operations to check whether to harden
the OS for the active and standby OMUs, separately.
– Windows OS
Perform the following steps to check whether to harden the OMU OS:
1. Run mstsc.exe on a local PC to log in to the OMU.
NOTE
For details about how to log in to the OMU by running mstsc.exe, see BSC6900 OMU
Administration Guide/BSC6910 OMU Administration Guide in BSC6900/BSC6910
Product Documentation.
2. If the dialog box shown in Figure 6-2 is displayed during the remote login, go to
3. If this dialog box is not displayed during the remote login, go to Enhancing
System Security.

GBSS17.1&RAN17.1
Figure 6-2 Dialog box displayed during the remote login

engineer. In the Documentation area, choose Wireless > WCDMA-RAN >
WCDMA-RNC > Technical Guides > Deployment Guide to obtain Deployment
Guide to the Installation and upgrade of OfficeScan 10.0 Server and Client.
4. Check whether antivirus software has been installed on the OMU. If yes, go to 5.
If no, go to Enhancing System Security. For details about how to check whether
antivirus software has been installed on the OMU, see section 3.2.3 "Checking the
Client" in Deployment Guide to the Installation and upgrade of OfficeScan 10.0
Server and Client.
5. Enter the terminal service configuration interface by choosing Start >
Programs > Administrative Tools > Terminal Services Configuration or
Start > Administrative Tools > Terminal Services Configuration, as shown in
Figure 6-3. Right-click RDP-Tcp and choose Property. In the displayed RDP-
Tcp Properties window, click the General tab page. Check whether the terminal
service configurations are the same as those marked in red square boxes in Figure
6-4. If yes, OS hardening is not required. If no, go to Implementing OS
Hardening.

GBSS17.1&RAN17.1
Figure 6-3 Terminal Services Configuration interface

GBSS17.1&RAN17.1
Figure 6-4 RDP-Tcp Properties window
– SUSE Linux OS
Perform the following steps to check whether to harden the OMU OS:
1. Log in to the OMU using PuTTY.
NOTE
For details about how to log in to the OMU using PuTTY, see BSC6900 OMU
Administration Guide/BSC6910 OMU Administration Guide in BSC6900/BSC6910
Product Documentation.
2. Run the sek –v command to query whether OS hardening software has been
installed on the OMU. If the execution result is the same as that shown in Figure
6-5, go to 3. If no, go to Enhancing System Security.
Figure 6-5 Execution result of the sek –v command

GBSS17.1&RAN17.1
3. Run the sek command to start the OS hardening software. If a dialog box shown
in Figure 6-6 is displayed during the startup of the OS hardening software, click
OK to enter the main page of the OS hardening software.
NOTE
If other windows are displayed during the startup of the OS hardening software, contact
Huawei engineers for technical support.
Figure 6-6 Dialog box displayed during the startup of the OS hardening software
4. Choose Configuration > Recently imported file to query the configured system
security policy. If the queried result contains the file marked by the red square box
shown in Figure 6-7, the OMU OS hardening is not required. If the queried result
does not contain the file, the OMU OS must be hardened.
Figure 6-7 Security enhancing policy files configured on the OMU
5. Click OK to close the result query window shown in Figure 6-7. Choose Policy
> Exit. A dialog box shown in Figure 6-8 is displayed. Click Yes to exit the OS
hardening software.
Figure 6-8 Dialog box for exiting the security enhancing software
6. If the OMU OS needs to be hardened as queried in 4, go to Implementing OS

Hardening. Otherwise, no more operations are required.
l Implementing OS hardening

GBSS17.1&RAN17.1
NOTICE
If the OMU OS is Windows, OMU services need to be stopped and OMU boards need to
be reset during the OS hardening procedure. This disconnects the OMU from the U2000
but does not affect services.

Choose Tools > Controlled Tool (Mini-tool Software) > Wireless Product Line >
Security Tools > public to obtain Guide to Enhancing the BSC6900 Operating
System/Guide to Enhancing the BSC6910 Operating System.
2. Enhance system security by referring to Guide to Enhancing the BSC6900 Operating
System/Guide to Enhancing the BSC6910 Operating System.
----End
6.9 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.

NOTE
You are advised to change the password upon your first login and change the password every three months.
Method for changing passwords

l For details about how to change passwords for admin, root user, db_user, and FtpUsr, see
Changing Users' Passwords in OMU Administration Guide.
l For details about how to change the password for the OS administrator, see Changing the
Administrator Password of the Operating System in OMU Administration Guide.
Password complexity policy

Passwords for the admin, db_user, FtpUsr, and OS administrator comply with the password
complexity policy.
l Passwords for db_user consist of upper-case and lower-case letters, digits, special
characters (such as-?[]_+{}), and space. The password length range from 8 to 32 characters.
l The password for the OS administrator must comply with the password policy returned by
running the DSP OSPWDPOLICY command. The password policy can be set by running
the SET OSPWDPOLICY command.
l Passwords for the admin and FtpUsr comply with the password policy configured by
running the SET PWDPOLICY command.
Others
For details about how to check other security configurations, see Specific Security Policies in
Security Overview Feature Parameter Description.

GBSS17.1&RAN17.1
6.10 Updating Key Material

The key material(key parameter) needs to be updated periodically (recommended period: 6
months) to prevent it from being disclosed.
Prerequisites
BSC6910.
Procedure
Step 1 Run the UPD KEYMATERIAL command.
----End

GBSS17.1&RAN17.1
Routine Maintenance Guide 7 GBSS&RAN Routine Maintenance Record
7 GBSS&RAN Routine Maintenance Record
About This Chapter
Information about the equipment performance during the maintenance is recorded in routine
maintenance record tables.
7.1 Daily Maintenance Record

This section introduces the daily maintenance record table.
7.2 Weekly Maintenance Record

This section introduces the weekly maintenance record table.
7.3 Monthly Maintenance Record

This section introduces the monthly maintenance record table.

GBSS17.1&RAN17.1
7.1 Daily Maintenance Record

This section introduces the daily maintenance record table.
After performing daily routine maintenance, record the result. Table 7-1 is the record table
template.
Table 7-1 Daily maintenance record
SN Task Expected Result Operation

Record
Monitor the GBSS&RAN No BSC6900/BSC6910 or base

1 alarms. station alarms exist.
Monitor the GBSS&RAN No BSC6900/BSC6910 or base

2 events. station events exist.
Collect the GBSS&RAN

3 alarm and event statistics. -
For GSM cells, the initialization

status of cells should be Yes and
the channel fault status should be
No. For UMTS cells, the cell
operating status should be
4 Monitor the cell status. Available.
Monitor the condition of

5 cell resources. -
Monitor the performance

6 counters. Values meet the requirements.
Save the performance

7 measurement results. -
Query and save

BSC6900/BSC6910
8 operation logs. -
Query and save other logs

of the BSC6900/
9 BSC6910. -
Query and save the

10 NodeB operation logs. -
Query and save other logs

11 of the NodeB. -
Check the GBTS running All GBTSs are running

12 status. correctly.

GBSS17.1&RAN17.1

Record
Check the automatic NE The automatic NE backup

13 backup function. function is normal.
You can download the daily maintenance record.

l For UMTS: daily maintenance record
l For GSM: daily maintenance record
l For GU: daily maintenance record
7.2 Weekly Maintenance Record

This section introduces the weekly maintenance record table.
After performing weekly routine maintenance, record the result. Table 7-2 is the record table
template.
Table 7-2 Weekly maintenance record
SN Task Expected Result Operati

on
Record
All checked items are

1 Perform the NE health check. normal.
See Table 1 in
"Procedure" in 5.2
Checking the Running
2 Check the running status of the OMU. Status of the OMU.
The hard disk and

Check the running status of the GBAM memory space are
3 server. sufficient.
CPU status or Board

status of each board is
Normal. For a board
working in active/
standby mode, CPU
status or Board status
of the active board is
Active normal; CPU
status or Board status
of the standby board is
4 Check the BSC6900/BSC6910 board status. Standby normal.

GBSS17.1&RAN17.1
SN Task Expected Result Operati

on
Record
The status of each board

5 Check the base station board status. is normal.
The clock source status

6 Check the BSC6900/BSC6910 clock. is normal.
The clock source status

7 Check the base station clock status. is normal.
8 Back up the system data. -
9 Back up the license information. -
Analyze the performance measurement

10 results. -
11 Collect historical alarms and events. -
All NEs communicate

Check the communication between NEs and with the U2000
12 the U2000. normally.
You can download the weekly maintenance record.

l For UMTS: weekly maintenance record
l For GU: weekly maintenance record
l For GSM: weekly maintenance record
7.3 Monthly Maintenance Record

This section introduces the monthly maintenance record table.
After performing monthly routine maintenance, record the result. Table 7-3 is the record table
template.
Table 7-3 Monthly maintenance record

Record
1 Analyze customer complaints. -
Prepare an NE performance
2 report. -
3 Prepare a performance report. -

GBSS17.1&RAN17.1

Record
The disk space on the

Check the disk space on the terminal system meets the
4 terminal system. requirements.
Check the maintenance terminal The system is free of any

5 system for viruses. virus.
Check the connectivity of port The port links are

6 links. connected.
Check security patches for the The patches of the local

OMU operating system. operating system are the
latest patches on the
7 network.
8 Check the OS hardening. -
Check weak passwords and The password complexity

9 others. strategy is followed.
10 Update the OMU key. -
You can download monthly maintenance record.


GBSS17.1&RAN17.1 Routine Maintenance Guide (01) (PDF) - en

Caricato da

Informazioni sul documento

Titolo originale

Copyright

Formati disponibili

Condividi questo documento

Condividi o incorpora il documento

Opzioni di condivisione

Hai trovato utile questo documento?

Questo contenuto è inappropriato?

Copyright:

Formati disponibili

GBSS17.1&RAN17.1 Routine Maintenance Guide (01) (PDF) - en

Caricato da

Copyright:

Formati disponibili

GBSS17.1&RAN17.

Routine Maintenance Guide

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 01 (2015-03-25) Huawei Proprietary and Confidential i

About This Document

Product Name Product Version Solution Version

BSC6900/BSC6910 V900R017C10/ SRAN10.1

Issue 01 (2015-03-25) Huawei Proprietary and Confidential ii

3 GBSS&RAN Routine Maintenance Overview

4 GBSS&RAN Daily Maintenance Guidelines

5 GBSS&RAN Weekly Maintenance Guidelines

6 GBSS&RAN Monthly Maintenance Guidelines

7 GBSS&RAN Routine Maintenance Record

Indicates an imminently hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Indicates a potentially hazardous situation which, if not

Issue 01 (2015-03-25) Huawei Proprietary and Confidential iii

Indicates a potentially hazardous situation which, if not

Calls attention to important information, best practices and

Times New Roman Normal paragraphs are in Times New Roman.

Boldface Names of files, directories, folders, and users are in

Italic Book titles are in italics.

Courier New Examples of information displayed on the screen are in

Boldface The keywords of a command line are in boldface.

Italic Command arguments are in italics.

[] Items (keywords or arguments) in brackets [ ] are optional.

{ x | y | ... } Optional items are grouped in braces and separated by

[ x | y | ... ] Optional items are grouped in brackets and separated by

{ x | y | ... }* Optional items are grouped in braces and separated by

Issue 01 (2015-03-25) Huawei Proprietary and Confidential iv

[ x | y | ... ]* Optional items are grouped in brackets and separated by

Boldface Buttons, menus, parameters, tabs, window, and dialog titles

> Multi-level menus are in boldface and separated by the ">"

Double-click Press the primary mouse button twice continuously and

Issue 01 (2015-03-25) Huawei Proprietary and Confidential v

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

4 GBSS&RAN Daily Maintenance Guidelines..........................................................................9

5 GBSS&RAN Weekly Maintenance Guidelines....................................................................42

Issue 01 (2015-03-25) Huawei Proprietary and Confidential vi

5.2 Checking the Running Status of the OMU...................................................................................................................46

6 GBSS&RAN Monthly Maintenance Guidelines..................................................................66

7 GBSS&RAN Routine Maintenance Record...........................................................................82

Issue 01 (2015-03-25) Huawei Proprietary and Confidential vii

Change Type Change Description

Function Added None.

Issue 01 (2015-03-25) Huawei Proprietary and Confidential 1

Table 2-1 High-risk operations

Type Operation Risk Reference

Operations on Some operations on hardware, High-Risk Hardware Operations in

Commands Incorrect execution of some High-Risk Command List in

Issue 01 (2015-03-25) Huawei Proprietary and Confidential 2

3 GBSS&RAN Routine Maintenance

About This Chapter

3.2 GBSS&RAN Tools

3.3 GBSS&RAN Routine Maintenance Tasks Based on Maintenance Frequency

Issue 01 (2015-03-25) Huawei Proprietary and Confidential 3

GBSS&RAN routine maintenance is performed to monitor and maintain the BSC6900/

l To perform site maintenance, see .

3.2 GBSS&RAN Tools

Issue 01 (2015-03-25) Huawei Proprietary and Confidential 4

l Contact Huawei engineers to obtain PuTTY by performing the following operation: