GBSS16.0 Routine Maintenance Guide (02) (PDF) - en

GBSS16.
Routine Maintenance Guide

Issue
02
Date
2014-09-10
HUAWEI TECHNOLOGIES CO., LTD.
Copyright Huawei Technologies Co., Ltd. 2014. 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 02 (2014-09-10)
Huawei Proprietary and Confidential

Copyright Huawei Technologies Co., Ltd.
GBSS16.0
About This Document
About This Document

Purpose
This document provides guidelines for daily, weekly, and monthly maintenance of the GBSS
and also table templates for recording maintenance results.
Product Version
This document is intended for the GBSS16.0 solution. The following table lists the product
versions related to this document.
Product Name
Product Version
Solution Version
BSC6900
V900R016C00
GBSS16.0
BSC6910
V100R016C00
BTS3900
V100R009C00
BTS3900A
The mapping single-mode

base station versions are:
BTS3900L
l GBTS: V100R016C00
BTS3900AL
l eGBTS: V100R016C00
DBS3900
Intended Audience
This document is intended for:
l
Shift operators
System engineers
Organization
1 Changes History
Issue 02 (2014-09-10)

ii
GBSS16.0
About This Document
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 Routine Maintenance Overview
The purpose of GBSS routine maintenance is to ensure the reliability, stability, and optimum
operational state of the BSC6900/BSC6910, GBTS, and eGBTS. In addition, routine
maintenance helps prevent potential accidents, and identify and resolve problems in time.
4 GBSS Daily Maintenance Guidelines
This chapter provides guidelines for performing daily maintenance tasks on the GBSS.
5 GBSS Weekly Maintenance Guidelines
This chapter provides guidelines for performing weekly maintenance tasks on the GBSS.
6 GBSS Monthly Maintenance Guidelines
This chapter provides guidelines for performing monthly maintenance tasks on the GBSS.
7 GBSS 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.
avoided, could result in equipment damage, data loss,
performance deterioration, or unanticipated results.
NOTICE is used to address practices not related to personal
injury.
Issue 02 (2014-09-10)

iii
GBSS16.0
About This Document
Symbol
Description
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.
Convention
Description
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.
[ x | y | ... ]*
Optional items are grouped in brackets and separated by

vertical bars. Several items or no item can be selected.
GUI Conventions
Issue 02 (2014-09-10)

iv
GBSS16.0
About This Document
The GUI conventions that may be found in this document are defined as follows.
Convention
Description
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.
Issue 02 (2014-09-10)
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.

GBSS16.0
Contents
Contents
About This Document.....................................................................................................................ii
1 Changes History.............................................................................................................................1
2 High-Risk Operations...................................................................................................................3
3 GBSS Routine Maintenance Overview.....................................................................................4
3.1 Scope..............................................................................................................................................................................5
3.2 GBSS Tools....................................................................................................................................................................5
3.3 GBSS 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.......................................................................................................................................8
4 GBSS Daily Maintenance Guidelines.......................................................................................9

4.1 Monitoring GBSS Alarms and Events..........................................................................................................................10
4.1.1 Alarm Handling Procedure........................................................................................................................................10
4.1.2 Monitoring GBSS Alarms.........................................................................................................................................12
4.1.3 Monitoring GBSS Events..........................................................................................................................................13
4.1.4 Collecting GBSS Alarm and Event Statistics............................................................................................................14
4.2 Monitoring the GBSS Performance..............................................................................................................................15
4.2.1 Monitoring Performance Counters............................................................................................................................15
4.2.2 Saving Performance Measurement Results...............................................................................................................17
4.3 Monitoring Cell Status and Cell Resources..................................................................................................................18
4.3.1 Monitoring Cell Status...............................................................................................................................................18
4.3.2 Monitoring Cell Resources........................................................................................................................................20
4.4 Querying and Saving BSC6900/BSC6910 Operation Logs.........................................................................................21
4.5 Querying and Saving Other Logs of the BSC6900/BSC6910......................................................................................24
4.6 Checking the GBTS Running Status............................................................................................................................30
4.7 Checking the Scheduled NE Backup Function.............................................................................................................31
5 GBSS Weekly Maintenance Guidelines.................................................................................33

5.1 Performing NE Health Check.......................................................................................................................................35
5.2 Checking the Running Status of the OMU...................................................................................................................37
5.3 Checking the Running Status of a GBAM Server........................................................................................................39
Issue 02 (2014-09-10)

vi
GBSS16.0
Contents
5.4 Checking the BSC6900/BSC6910 Board Status..........................................................................................................40

5.5 Checking the Base Station Board Status......................................................................................................................41
5.6 Checking the BSC6900/BSC6910 Clock Status..........................................................................................................42
5.7 Checking the Base Station Clock Status.......................................................................................................................44
5.8 Backing Up and Restoring the GBSS System Data.....................................................................................................45
5.8.1 Creating a Scheduled Backup Task (on the U2000)..................................................................................................45
5.8.2 Manually Backing up NE Data (on the U2000)........................................................................................................46
5.8.3 Restoring NE Data (on the U2000)...........................................................................................................................47
5.8.4 Manually Backing Up and Restoring NE Data (on the LMT)...................................................................................48
5.9 Backing Up License Information.................................................................................................................................50
5.10 Analyzing Performance Measurement Results...........................................................................................................51
5.11 Collecting Historical Alarm and Event Statistics.......................................................................................................52
5.12 Checking Communication Between NEs and the U2000...........................................................................................53
6 GBSS Monthly Maintenance Guidelines...............................................................................55

6.1 Analyzing Customer Complaints..................................................................................................................................57
6.2 Preparing an NE Running Report.................................................................................................................................57
6.3 Preparing a Performance Report...................................................................................................................................59
6.4 Checking the Disk Space on the Terminal System.......................................................................................................59
6.5 Checking the Maintenance Terminal System for Viruses............................................................................................60
6.6 Checking the Connectivity of Port Links.....................................................................................................................60
6.7 Checking Security Patches for the OMU OS...............................................................................................................61
6.8 Checking OS Hardening...............................................................................................................................................63
6.9 Checking Weak Passwords and Others........................................................................................................................68
6.10 Updating the OMU Key.............................................................................................................................................69
7 GBSS Routine Maintenance Record........................................................................................70

7.1 Daily Maintenance Record...........................................................................................................................................71
7.2 Weekly Maintenance Record........................................................................................................................................72
7.3 Monthly Maintenance Record......................................................................................................................................73
Issue 02 (2014-09-10)

vii
GBSS16.0
1 Changes History
Changes 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.
02 (2014-09-10)
This issue includes the following changes.
Change Type
Function
change
Editorial
change
Change Description
Added
None
Modified
Updated the description of 6.7 Checking Security Patches

for the OMU OS.
Deleted
None
None
01 (2014-04-29)
Change Type
Function
change
Change Description
Added
None
Modified
Deleted
Editorial
change
Issue 02 (2014-09-10)
None

GBSS16.0
1 Changes History
Draft B (2014-02-28)
Change Type
Function
change
Editorial
change
Change Description
Added
None
Modified
Added operations of encrypting NE backup files. For

details, see 5.8.1 Creating a Scheduled Backup Task (on
the U2000), 5.8.4 Manually Backing Up and Restoring
NE Data (on the LMT), and 5.8.2 Manually Backing up
NE Data (on the U2000).
Deleted
None
None
Draft A (2014-01-27)
Compared with Issue 02 (2013-07-30) of GBSS15.0, this issue includes the following changes.
Change Type
Function
change
Change Description
Added
Added the function of updating the OMU key. For details,

see 6.10 Updating the OMU Key.
Added the function of checking the OS security patches. For
details, see 6.7 Checking Security Patches for the OMU
OS.
Added the function of checking weak passwords. For
details, see 6.9 Checking Weak Passwords and Others.
Added the function of checking OS hardening. For details,
see 6.8 Checking OS Hardening.
Editorial
change
Issue 02 (2014-09-10)
Modified
Added the following types of logs in the log information

description: PFM_NOM_RESULT, OMU_SIM_LOG,
and SDBG_LOG. For details, see 4.5 Querying and
Saving Other Logs of the BSC6900/BSC6910.
Deleted
None
None

GBSS16.0
2 High-Risk Operations
High-Risk Operations
Table 2-1 High-risk operations

Type
Operation Risk
Reference
Operations on
hardware
Some operations on hardware,

such as board replacement, may
affect the system operating.
Therefore, perform these
operations when traffic is light, for
example, in the early morning. In
addition, perform these operations
as quickly as possible to reduce the
impact on the system.
High-Risk Hardware Operations in

BSC6900 GSM Site Maintenance
Guide
Board replacement may have

different impacts on the system
due to their different functions.
Commands
Issue 02 (2014-09-10)
Incorrect execution of some

commands may affect the system
operating. Exercise caution when
running these commands.
High-Risk Command List in

BSC6900 GSM MML Command
Reference

GBSS16.0
GBSS Routine Maintenance Overview
About This Chapter

The purpose of GBSS routine maintenance is to ensure the reliability, stability, and optimum
operational state of the BSC6900/BSC6910, GBTS, and eGBTS. In addition, routine
maintenance helps prevent potential accidents, and identify and resolve problems in time.
3.1 Scope
GBSS routine maintenance is performed on a U2000 or LMT to ensure the reliable operation of
the BSC6900/BSC6910 and BTS.
3.2 GBSS Tools
The tools for GBSS routine maintenance consist of the U2000 client and LMT.
3.3 GBSS Routine Maintenance Tasks Based on Maintenance Frequency
Based on the maintenance frequency, routine maintenance is classified into daily, weekly, and
monthly maintenance.
Issue 02 (2014-09-10)

GBSS16.0
3.1 Scope
GBSS routine maintenance is performed on a U2000 or LMT to ensure the reliable operation of
the BSC6900/BSC6910 and BTS.
GBSS routine maintenance is a process in which the BSC6900/BSC6910, GBTS, and eGBTS
are monitored and maintained. Routine maintenance does not include the routine maintenance
on the U2000 and the site maintenance.
l
To perform site maintenance, see BSC6900 GSM Site Maintenance Guide or BSC6910
GSM Site Maintenance Guide.
To perform the routine maintenance on the U2000, see U2000 Product Documentation.
To modify GBSS configurations, see GBSS Reconfiguration Guide.
3.2 GBSS Tools

The tools for GBSS routine maintenance consist of the U2000 client and LMT.
U2000 Client
The U2000 works in client/server mode to simultaneously monitor multiple NEs. You can
perform operations only after logging in to the server through the client.
LMT
The LMT is used to perform routine maintenance on a single NE.
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.
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. It can be used for remotely logging in to the Dopra
Linux operating system.
You can use PuTTY to log in to the BSC6900/BSC6910 OMU to perform remote operation and
maintenance.
Issue 02 (2014-09-10)

GBSS16.0
Contact Huawei engineers who can obtain PuTTY by performing the following operation:
Visit http://support.huawei.com/support/. Choose Software Center > Controlled Tool
(Mini-tool Software) > Wireless Product Line > Wireless Performance & RNP &
RNO > iManager Nastar > Nastar Tools to download the PuTTY software.
Start PuTTY.
1.
Double-click putty.exe. The PuTTY Configuration dialog box 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 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 prohibited, 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 BSC6900 GSM
OMU Administration Guide or BSC6910 GSM OMU Administration Guide.
3.3 GBSS 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 Table 3-1. You
can perform specific maintenance tasks according to actual requirements.
Table 3-1 Daily maintenance tasks
Issue 02 (2014-09-10)
SN
Task
Reference
Monitor the GBSS alarms.
4.1.2 Monitoring GBSS Alarms
Monitor the GBSS events.
4.1.3 Monitoring GBSS Events
Collect the GBSS alarm and event

statistics.
4.1.4 Collecting GBSS Alarm and

Event Statistics
Monitor the performance counters.
4.2.1 Monitoring Performance

Counters
Save the performance measurement

results.
4.2.2 Saving Performance

Measurement Results
Monitor the cell status.
4.3.1 Monitoring Cell Status
Monitor the condition of cell

resources.
4.3.2 Monitoring Cell Resources

GBSS16.0
SN
Task
Reference
Query and save BSC6900/

BSC6910 operation logs.
4.4 Querying and Saving BSC6900/

BSC6910 Operation Logs
Query and save other logs of the

BSC6900/BSC6910.
4.5 Querying and Saving Other Logs of

the BSC6900/BSC6910
10
Check the GBTS running status.
4.6 Checking the GBTS Running

Status
11
Check the automatic NE backup

function.
4.7 Checking the Scheduled NE

Backup Function
3.3.2 Weekly Maintenance Tasks

This section introduces weekly maintenance tasks and their references, as listed in Table 3-2.
You can perform specific maintenance tasks according to actual requirements.
Table 3-2 Weekly maintenance tasks
Issue 02 (2014-09-10)
SN
Task
Reference
Perform the NE health check.
5.1 Performing NE Health Check
Check the running status of the OMU.
5.2 Checking the Running Status of

the OMU
Check the running status of the GBAM

server.
5.3 Checking the Running Status of

a GBAM Server
Check the BSC6900/BSC6910 board

status.
5.4 Checking the BSC6900/

BSC6910 Board Status
Check the BTS board status.
5.5 Checking the Base Station Board

Status
Check the BSC6900/BSC6910 clock

status.
5.6 Checking the BSC6900/

BSC6910 Clock Status
Check the base station clock status.
5.7 Checking the Base Station Clock

Status
Back up and restore the GBSS system

data.
5.8 Backing Up and Restoring the

GBSS System Data
Back up the license information.
5.9 Backing Up License Information
10
Analyze the performance

measurement results.
5.10 Analyzing Performance

Measurement Results
11
Collect historical alarms and events.
5.11 Collecting Historical Alarm

and Event Statistics

GBSS16.0
SN
Task
Reference
12
Check the communication between

NEs and the U2000.
5.12 Checking Communication

Between NEs and the U2000
3.3.3 Monthly Maintenance Tasks

This section introduces monthly maintenance tasks and their references, as listed in Table 3-3.
You can perform specific maintenance tasks according to actual requirements.
Table 3-3 Monthly maintenance tasks
Issue 02 (2014-09-10)
SN
Task
Reference
Analyze customer complaints.
6.1 Analyzing Customer Complaints
Prepare an NE performance report.
6.2 Preparing an NE Running Report
Prepare a performance report.
6.3 Preparing a Performance Report
Check the disk space on the terminal

system.
6.4 Checking the Disk Space on the

Terminal System
Check the maintenance terminal

system for viruses.
6.5 Checking the Maintenance

Terminal System for Viruses
Check the connectivity of port links.
6.6 Checking the Connectivity of Port

Links
Check security patches for the OMU

operating system.
6.7 Checking Security Patches for the

OMU OS
Check the OS hardening.
6.8 Checking OS Hardening
Check weak passwords and others.
6.9 Checking Weak Passwords and

Others
10
Update the OMU key.
6.10 Updating the OMU Key

GBSS16.0
GBSS Daily Maintenance Guidelines
About This Chapter

This chapter provides guidelines for performing daily maintenance tasks on the GBSS.
4.1 Monitoring GBSS Alarms and Events
Monitor active alarms and events of the BSC6900/BSC6910, GBTS, and eGBTS on a U2000
client.
4.2 Monitoring the GBSS Performance
Users can monitor the performance of the BSC6900/BSC6910, GBTS, and eGBTS and save the
performance measurement results on a U2000 client.
4.3 Monitoring Cell Status and Cell Resources
Users 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 Checking the GBTS Running Status
This section describes how to query the GBTS running status on a U2000 client or LMT.
4.7 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.
Issue 02 (2014-09-10)

GBSS16.0
4.1 Monitoring GBSS Alarms and Events

Monitor active alarms and events of the BSC6900/BSC6910, GBTS, and eGBTS on a U2000
client.
4.1.1 Alarm Handling Procedure

This section describes the alarm handling procedure. After the U2000 detects an alarm, you are
advised to handle the alarm following the procedure.
Flowchart
Figure 4-1 shows the alarm handling flowchart.
Issue 02 (2014-09-10)

10
GBSS16.0
Figure 4-1 Alarm Handling Chart
Issue 02 (2014-09-10)

11
GBSS16.0
Procedure Description
Table 4-1 lists the procedure for handling an alarm.
Table 4-1 Procedure for handling an alarm
St
ep
Operation
Description
Receive an alarm.
After receiving an alarm, start the alarm handling procedure. To

ensure that you are notified of an alarm in time after the alarm
occurs, set alarm notification methods on the U2000.
View the alarm

details.
View the alarm details, including the alarm location information,

alarm help, and alarm handling experience.
Acknowledge the
alarm.
Acknowledge the alarm to prevent it from being simultaneously

processed by others.
Collect the fault

information.
Identify the alarm and query the alarm information to find out the
symptom of the alarm.
Analyze the
causes of the
alarm.
Analyze the causes for the alarm based on the alarm symptom.
Work out the

fault handling
scheme.
Work out the fault handling scheme according to the alarm details,
device manuals, network status, and maintenance experience.
Carry out the

fault handling
scheme.
Carry out the fault handling scheme to rectify the fault that leads to
the alarm.
Clear the alarm.
Clear the conditions that cause the alarm. After the alarm is cleared,
the U2000 receives a clear alarm.
Check whether
the fault is
rectified.
Check the handling results after you rectify the fault.
10
Record the
maintenance
experience.
Record the maintenance experience when the alarm handling is

complete.
4.1.2 Monitoring GBSS Alarms

This section describes how to monitor active alarms of the BSC6900/BSC6910, GBTS, and
eGBTS on a U2000 client.
Prerequisites
l
Issue 02 (2014-09-10)
You have logged in to the U2000 client, and it is properly communicating with related NEs.
12
GBSS16.0
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). 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 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 Events

This section describes how to monitor events of the BSC6900/BSC6910, GBTS, and eGBTS on
a U2000 client.
Prerequisites
l
You have the 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.
Issue 02 (2014-09-10)

13
GBSS16.0
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.
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 Alarm and Event Statistics

This section describes how to collect statistics on alarms and events of the BSC6900/
BSC6910, GBTS, and eGBTS on a U2000 client by severity and type and how to save the alarm
and event statistics for easy query.
Prerequisites
l
You have the permission to collect alarm and event statistics.
Procedure
Step 1 On the U2000 client:
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.
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.
Issue 02 (2014-09-10)

14
GBSS16.0
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.
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 Performance

Users can monitor the performance of the BSC6900/BSC6910, 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 15 minutes, 60 minutes, or 24 hours on a U2000 client. Based on the measurement
results, you can determine whether the BSC6900/BSC6910, GBTS, and eGBTS are running
correctly.
Prerequisites
l
Measurement objects are available.
You have the permission to query measurement results of performance counters.
Context
Key performance indicators (KPIs) and performance counters are used to evaluate network
performance. Users can choose specific KPIs and performance counters for routine maintenance
based on the network status and evaluation criteria.
Table 4-2 provides the recommended KPIs for monitoring on a GSM network. Additionally,
the recommended performance counters are related to these recommended KPIs.
NOTE
For details about definitions of the listed KPIs, see GBSS KPI Reference. For details about counters related to
KPIs, see BSC6900 GSM Performance Counter Reference and BSC6910 GSM Performance Counter
Reference.
Issue 02 (2014-09-10)

15
GBSS16.0
Table 4-2 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%
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.
Issue 02 (2014-09-10)

16
GBSS16.0
If...
Then...
No template is available
Go to Step 3.
Step 2 In the left Template navigation tree, double-click a template to query 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). Expand the BSC6900 GSM or
BSC6910 GSM node and select the object type or function subset to be queried. The NE
objects are listed in the Available Objects area in the form of navigation tree.
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 whether to view the details. To view 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
prevent data loss.
Issue 02 (2014-09-10)

17
GBSS16.0
Prerequisites
l
Performance measurement results have been generated. For details about how to query the
performance measurement results, see 4.2.1 Monitoring Performance Counters.
You have the 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.
----End
Result
You can obtain the performance measurement result file in the specified directory.
4.3 Monitoring Cell Status and Cell Resources

Users 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 properly communicating with the
BSC6900/BSC6910.
You have the permission to run MML commands.
Context
GSM cell status includes states of cell initialized, cell service, automatically blocked, and
manually blocked. Table 4-3 provides details about GSM cell status.
Table 4-3 GSM cell status and descriptions
State
Description
Cell
initialized
Whether a cell has been initialized. The cell can enter the service state only
after being initialized.
l Yes: The cell has been initialized.
l No: The cell has not been initialized.
Issue 02 (2014-09-10)

18
GBSS16.0
State
Description
Cell
service
Whether a cell is in the service state, namely, whether a cell is running correctly.
l Yes: The cell is in the service state.
l No: The cell is out of service.
Automatic
ally
blocked
Whether some TRXs in a cell are automatically blocked.

l Yes: Some TRXs in the cell are automatically blocked and these TRXs are
unavailable.
l No: No TRX in the cell is automatically blocked. TRXs in the cell are
available.
Manually
blocked
Whether some channels in a cell are manually 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, 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 GCELLSTAT command and set parameters as follows to query the operating
status of all cells:
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.
Issue 02 (2014-09-10)

19
GBSS16.0
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.
----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
in the 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 how to monitor measurement objects
as an example.
Prerequisites
l
Context
For GSM, the measurement counters listed in Table 4-4 are used to determine the current
performance status of a cell.
Table 4-4 Measurement counters of cell resources
Performance Item
Measurement
Counter
Description
Expected Result
Percentage of TCHs
in the busy state
CELL.CHAN.BUS
Y.NUM.TCH.RATE
Measurement object:
GCELL
This counter
provides the
percentage of busy
TCHFs or TCHHs in
all cells within a
measurement period.
Location of counters:
Measurement of
GSM Cell
Performance
(GCELL) >
Channel State
Measurement per
Cell
(CHAN.StateNum.
CELL)
If the value of this

counter is 0, there is
no UE in the cell, and
a fault may occur in
the cell.
Procedure
Step 1 Choose Performance > Result > Query Result (application style) or Performance > Query
Result (traditional style). The Query Result window is displayed.
Issue 02 (2014-09-10)

20
GBSS16.0
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.
3.

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
l
BSC6900/BSC6910.
The 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.
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:
Issue 02 (2014-09-10)

21
GBSS16.0
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.
Issue 02 (2014-09-10)
In the result query window, view NE operation logs by referring to the parameter
information in the following table.
Parameter Name
Parameter Meaning
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.

22
GBSS16.0
Parameter Name
Parameter Meaning
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, if the
Operation column displays MOD
GCELL: IDTYPE=BYID,
CELLID=0,
NEWCELLNAME="gcell2", the
Rollback MML column displays MOD
GCELL: IDTYPE=BYID,
CELLID=0,
NEWCELLNAME="gcell3", MOD
GCELL: IDTYPE=BYID,
CELLID=0,
NEWCELLNAME="gcell2" is
executed after 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 CMCTRLSW: CTRLSW=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.
Issue 02 (2014-09-10)

23
GBSS16.0

NOTE
Right-click a log in the query window and choose Details from the shortcut menu, or doubleclick 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.
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.

NOTE
When you back up the operation logs for the first time, set Backup Style to ENTIRE(Entire
Backup). In subsequent operation log backup, set Backup Style to INCREMENTAL
(Incremental Backup).
----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
l
BSC6900/BSC6910.
Context
Table 4-5 provides the types, save paths, and description of other logs of the BSC6900/
BSC6910.
Issue 02 (2014-09-10)

24
GBSS16.0
Table 4-5 Information of other logs
Issue 02 (2014-09-10)
Log Type
Save Path
Description
PFM_RESULT
(Performance Result File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
The log records the traffic

statistics reported by a
network element (NE) to the
U2000. It is used for
analyzing traffic statistics.
PFM_NOM_RESULT
(Performance Result File in
Normal Period)
/bam/version_a/ftp/
COLLOGINFO/PFMNOM-LOG/

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

statistics reported by a board
to the OMU. It is used for
analyzing board traffic
statistics.
ACTIVE_DEF_MEAS_FIL
E(Active Default
Measurement Task File)
/bam/version_a/ftp/
COLLOGINFO/PFM-LOG/
This is the active definition

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

file for traffic statistics
delivered by the U2000 to an
traffic statistics.
PFM_SWITCHS(The
Switches Information for
Performance)
Enumeration values are

reserved.
HISTORY_ALARM
(Historical Alarm File)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
The log records all the alarms

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

which cause historical
alarms. It is used for
analyzing alarm reporting
and clearing.

25
GBSS16.0
Issue 02 (2014-09-10)
Log Type
Save Path
Description
ALM_SYSTEM_CFG(The
Configured Information of
Alarm)
/bam/version_a/ftp/
COLLOGINFO/ALM-LOG/
The log records the

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

the information about
historical security-related
operations.
OPT_LOG(Operation Logs)
/bam/version_a/ftp/
COLLOGINFO/OPT-LOG/
This is the operation log of an

the operation and
maintenance on the NE.
OMU_LOG(The Log
Information of OMU)
/bam/version_a/ftp/
COLLOGINFO/SINGLEBAM/
This is the running log and

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

running information and
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
Configure File of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
ExportCfgmml/
The log records the BSC

configuration data
information. It is used for
checking the configuration
data during data restoration.
CELL_BASIC_INFO(The
Basic Information of Cells)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
CellBasicInfo/
The log records the cell basic

checking the mapping
between the cell ID and
internal cell ID.
BSC_SERIES_NO(The
Series No. of the BSC)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/

equipment serial number
(ESN) information. It is used
for license check. The ESN
uniquely identifies a BSC.

26
GBSS16.0
Issue 02 (2014-09-10)
Log Type
Save Path
Description
DB_BAK(The Backup File

of the Database)
/bam/version_a/ftp/
COLLOGINFO/CFG-LOG/
MysqlDbBak/
The log records the

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

information of OMU
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
Basic Information of Sites)
mbsc/bam/version_a/ftp/
COLLOGINFO/BTS-LOG
The log records basic

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
Examination File of BTS)
COLLOGINFO/BTS-LOG
The log records base station

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

logs, including temperature
logs, board replacement logs,
compressed logs, common
logs, and frequency scan
logs.
BTS_CHR_LOG(The CHR
Log of BTS)

reserved.
TRX_LOG(The TRX Log)

reserved.
BTS_NET_TABLE(The Net
Table Information of BTS)

reserved.

27
GBSS16.0
Issue 02 (2014-09-10)
Log Type
Save Path
Description
DEBUG_LOG(The
Common Debug Log)
/bam/common/fam/
famlogfmt/
The log records the

information of abnormal
software running. It is used
for analyzing software
defects.
SDBG_LOG (Channel Fault

Log)
/bam/common/fam/
famlogfmt/
The log records information

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

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

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

status of the host.
2G_CHR_LOG(The CHR
Log for GSM)
/bam/common/fam/
famlogfmt/gchr/
The log records the system

resources used, call status
change time, and signaling. It
is used for analyzing whether
the call procedure is normal.
2G_UNILATERAL_CONNECT(The Unilateral
Connection Log for GSM)
/bam/common/fam/
famlogfmt/
The log records the time of

and the system resources
used by the call with
problems, such as one-way
audio and cross-talk. It is
used for analyzing the cause
for voice faults.
BSC_INFO(The Basic
Information of the BSC)
/bam/version_a/ftp/
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.

28
GBSS16.0
Issue 02 (2014-09-10)
Log Type
Save Path
Description
GCSR_LOG(The CHR Log

for Single User of GSM CS)
/bam/common/fam/
famlogfmt/
The log records the basic

information of abnormal
calls, such as call initiating
time, site, cell, and TRX
where the call is initiated.
GPSR_LOG(The CHR Log

for Single User of GSM PS)
/bam/common/fam/
famlogfmt/gphr/
The log records the basic

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
Dial Diagnose Log)
/bam/common/fam/
famlogfmt/
The log records the A

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

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

access failures and call drops.
It is used for analyzing the
cause for network access
failures and call drops.
PCHR_LOG(PCHR Log)
/bam/common/fam/
famlogfmt/pchr
The log records detailed

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
(SYSFAULT Log)
/bam/common/fam/
famlogfmt/sysfault/
The log records serious

software or hardware faults,
such as resource leakage and
device fault. It is used for
network health check.

29
GBSS16.0
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
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
Result
You can obtain the target logs in the specified directory.
4.6 Checking the GBTS Running Status

This section describes how to query the GBTS running status on a U2000 client or LMT.
Prerequisites
l
You have logged in to the U2000 client or BSC LMT, and the U2000 client is properly
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
Issue 02 (2014-09-10)

30
GBSS16.0
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.
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.7 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
Context
Before checking the NE backup function, learn about the following information:
l
A scheduled backup file must be named AUTOBAKDATA+current time.
Avoid enabling the scheduled NE backup function during busy hours because this function
occupies too many system resources.
The scheduled NE backup task can be performed once or periodically (by day, week, or
month).
The U2000 supports a maximum of 50 scheduled NE backup tasks.
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.
Issue 02 (2014-09-10)

31
GBSS16.0
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

tasks
The scheduled NE backup function is normal.
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.
Step 6 Click Next, set Backup Type to By NE, and select target NEs.
Step 7 Click Finish.
----End
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.
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).
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.
Issue 02 (2014-09-10)

32
GBSS16.0
GBSS Weekly Maintenance Guidelines
About This Chapter

This chapter provides guidelines for performing weekly maintenance tasks on the GBSS.
This section describes how to perform health check on the BSC6900/BSC6910, 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.
5.8 Backing Up and Restoring the GBSS 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.
Issue 02 (2014-09-10)

33
GBSS16.0

This section describes how to back up BSC6900/BSC6910 license information and 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 that performance counters fluctuate, 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 by alarm
severity, alarm ID, or network management type on the U2000 client. 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. This section uses how to collect
alarm statistics as an example to describe the statistics collection procedure.
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.
Issue 02 (2014-09-10)

34
GBSS16.0

This section describes how to perform health check on the BSC6900/BSC6910, GBTS, and
eGBTS on a U2000 client. The NE health check is carried out based on the default maintenance
scenario.
Prerequisites
l
BSC6900/BSC6910, GBTS, and eGBTS.
You have the permission to perform NE health check.
Context
Table 5-1 provides the BSC6900/BSC6910 health check items.
Table 5-1 BSC6900/BSC6910 health check items
No.
Check Item
Interface status
BTS running status
Network performance
Cell status
Software version
License
Board status
Hardware
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

is displayed.
Issue 02 (2014-09-10)
on the upper left. The Create Task dialog box

35
GBSS16.0
3.
In the displayed dialog box, choose Maintenance from the Scenario Management dropdown 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 NE area.
5.
In the Time Setting area, select Scheduled.
6.
Click Next. In the displayed dialog box, specify Start Time and Run Times, and set
Period to Week. 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.
Issue 02 (2014-09-10)

36
GBSS16.0
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.
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
l
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
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:
Issue 02 (2014-09-10)

37
GBSS16.0
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

OMU
l The value of State of all service modules is Started.
Status of the
standby OMU
l The value of Startup Type is Automatic.

For debug_log, ftp_server, omu_manager, sntp, and software:
l The value of State is Started.
l The value of Startup Type is Automatic.
For other services rather than debug_log, ftp_server, omu_manager,
sntp, and software:
l The value of State is Stopped.
l The value of Startup Type is Disabled.
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
Issue 02 (2014-09-10)
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.
38
GBSS16.0
3.
Run the rm file name or rm -r folder name command to remove useless files.
If the OMU configuration information is different from the planned configuration, modify
the OMU configuration accordingly.
If the OMU operational state and data synchronization state is Abnormal, rectify the fault
according to handling suggestions for ALM-20704 OMU Data Synchronization Failure.
If the running status of the OMU modules is inconsistent with the expected result, rectify
the fault according to handling suggestions for ALM-20707 OMU Process Abort.
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
l
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.
Issue 02 (2014-09-10)

39
GBSS16.0
l Run the rm file name or rm -r folder name command to remove unnecessary files in this
folder.
----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
l
BSC6900/BSC6910.
You have logged in to the LMT, and it is properly communicating with the BSC6900/
BSC6910.
For a BSC6900, the status of DSP subsystems on the DPUa/DPUc/DPUd/DPUf/DPUg

board is queried, and the status can be queried only by running MML commands.
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.
Checking the board status or board subsystem status using an MML command on the U2000
Context
Procedure
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/DPUc/DPUd/DPUf/DPUg board in a specific subrack. In
this step, do not specify Slot No.
Expected result: The value of DSP operational state is Normal.
5.
Issue 02 (2014-09-10)
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.
40
GBSS16.0
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.
2.
On the BSC Maintenance tab page, choose BSC Maintenance > Maintain Device
> Query BSC Board Information. The Query eCoordinator Board Information
dialog box is displayed.
3.
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.
Prerequisites
l
You have logged in to the LMT, and it is properly communicating with related NEs.
Checking the GBTS board status using an MML command on the U2000 client
Procedure
1.
Issue 02 (2014-09-10)
41
GBSS16.0
2.
3.
Run the DSP BTSBRD command to query the status of a board in a specific subrack.
Checking the status of an eGBTS board using an MML command on the U2000 client
1.
2.
Select the target NE 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.
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.
Checking the status of an eGBTS board using the GUI on the LMT
1.
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.
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
l
BSC6900/BSC6910.
BSC6910.
Issue 02 (2014-09-10)

42
GBSS16.0
Context
The BSC6900/BSC6910 clock source is divided into five levels: 0 to 4 (from the highest level
to the lowest). 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.
Available: The clock source of this level can be used.
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.
Fast tracking: A clock source is available, and the clock source enters the fast tracking
mode.
Trace: The clock source meets the precision requirement, and the clock source enters the
trace state.
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 source clock status by using an MML command on the U2000
1.
2.
NOTE
is complete.
3.
l
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.
Checking the source clock status using the LMT GUI

1.
2.
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
Issue 02 (2014-09-10)

43
GBSS16.0
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.
In all-IP transmission mode, the system is not configured with a clock source:
Clock source state with levels 0 through 4 is Initialization.
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 Clock source state and Phase-locked loop state of current
clock are the same as those described in the operation results.
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
l
You have logged in to the LMT, and it is properly communicating with related NEs.
Checking the status of a GBTS clock using an MML command on the U2000 client
Procedure
l
Issue 02 (2014-09-10)
1.
2.
3.
Run the DSP BTSATTR command with BTS Attribute set to CLKATTR to query
the clock attributes of a base station.
Checking the status of an eGBTS clock using an MML command on the U2000 client
1.
2.
Select the target NE 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.
Checking the status of a GBTS clock using the GUI on the LMT
44
GBSS16.0
1.
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.
Checking the status of an eGBTS clock using the GUI on the LMT
1.
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
Follow-up Procedure
Normally, Clock attribute and Management state of the GBTS are Available and Lock,
respectively. Current clock source state of the eGBTS 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 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,
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
l
You have the permission to back up data.
Context
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.
Issue 02 (2014-09-10)

45
GBSS16.0
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.
2.
Set Task Type to NE Backup.
3.
Step 4 Click Next, and specify Start Time and Period Settings. In the Period Settings area, specify
Repeat times or End time.
Step 5 Click Next and select All NEs, By NE Type, By NE, or By Region for Backup Type.
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.
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).
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.
Prerequisites
l
The FTP server has been configured.
You have the permission to back up data.
Issue 02 (2014-09-10)

46
GBSS16.0
Context
Before manually backing up the NE data, learn the following information:
l
A manual backup file must be named BAKDATA+current time.
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.
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
l
You have the permission to restore data.
Issue 02 (2014-09-10)

47
GBSS16.0
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
Backup files uploaded from a local PC to the U2000 server
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 BSC6900/BSC6910 data by running
MML commands on the LMT.
Issue 02 (2014-09-10)

48
GBSS16.0
Prerequisites
You have logged in to the BSC6900/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.
NOTICE
l
Back up the system data on the active OMU if the OMUs work in active/standby mode.
Back up the OMU database before you perform capacity expansion or upgrade.
Backing up the system data by running an MML command
Procedure
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.
Issue 02 (2014-09-10)

49
GBSS16.0

This section describes how to back up BSC6900/BSC6910 license information and 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.
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).
The backup file is named after the license, for example: ON1020093_GO1.dat.
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.
The backup can be performed for a specific NE type or NE once or periodically (by day,
week, or month).
The U2000 manages GBTS and eGBTS licenses in a centralized manner. During routine
maintenance, you can export and save the license allocation information for all 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:
4.
a.
b.
Set Task Type to NE License Backup.
c.
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
Issue 02 (2014-09-10)
Manually backing up BSC6900/BSC6910 license information on the LMT

50
GBSS16.0
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, BSC01LICECO01LIC.dat.
Expected result: You can obtain the backup file of the target NE in the specified directory.
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.
Expected result: You can obtain the backup file of the target NE in the specified directory.
----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 that performance counters fluctuate, analyze them based on the network conditions.
Prerequisites
l
Measurement objects are available.
Context
For details about performance counters, see BSC6900 GSM Performance Counter Reference or
BSC6910 GSM Performance Counter Reference. You can specify the routine maintenance
standards based on the network conditions and assessment standards.
Issue 02 (2014-09-10)

51
GBSS16.0
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.
3.

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 by alarm
severity, alarm ID, or network management type on the U2000 client. 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. This section uses how to collect
alarm statistics as an example to describe the statistics collection procedure.
Prerequisites
l
You have the 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.
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
Issue 02 (2014-09-10)

ID.
52
GBSS16.0
Alarm Statistical Mode
Description
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.
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
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.
Issue 02 (2014-09-10)

53
GBSS16.0
Prerequisites
l
You have logged in to the U2000 client and the U2000 client and server are communicating
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
5-1.
on the upper left of the NE, as shown in Figure
Figure 5-1 U2000 network topology
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.
Issue 02 (2014-09-10)

54
GBSS16.0
GBSS Monthly Maintenance Guidelines
About This Chapter

This chapter provides guidelines for performing monthly maintenance tasks on the GBSS.
This section describes how to locate the causes and tendency of faults, facilitating problem
handling at points of frequent faults.
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, GBTS, and eGBTS and prepare the NE running report.
This section describes show to prepare a performance report by analyzing the performance of
the BSC6900/BSC6910, 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.
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
Issue 02 (2014-09-10)

55
GBSS16.0
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.
The OMU key needs to be updated periodically (recommended period: 6 months) to prevent it
from being disclosed.
Issue 02 (2014-09-10)

56
GBSS16.0

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
For details about how to handle 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 located.
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

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, 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.
Table 6-1 Alarm statistics collection methods
Alarm Statistics Collection Mode
Description
By alarm severity

severity.
There are four alarm severities: critical, major,
minor, and warning.
Issue 02 (2014-09-10)

57
GBSS16.0
Alarm Statistics Collection Mode
Description
By alarm ID

ID.
By alarm type

type.
By top N base stations with the

maximum number of alarms
The alarm statistics about the current monitoring

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

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


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


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.
Step 3 Collect statistics about alarms generated in this month by referring to 4.1.4 Collecting GBSS
Alarm and Event Statistics.
Step 4 Analyze the historical alarms to learn the running status of NEs.
Step 5 Prepare a monthly NE running report according to the performance measurement results and
historical alarms.
----End
Issue 02 (2014-09-10)

58
GBSS16.0

This section describes show to prepare a performance report by analyzing the performance of
the BSC6900/BSC6910, GBTS, and eGBTS according to the fault occurrence tendency.
Context
For details about performance counters that you need to focus on and collect, see GBSS16.0 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.
You have the 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.
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.
Issue 02 (2014-09-10)

59
GBSS16.0
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 the 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.
Prerequisites
l
BSC6900/BSC6910.
The port is enabled with the Ethernet Port Load Sharing function.
Checking the connectivity of BSC6900/BSC6910 port links on the U2000 client
Procedure
Issue 02 (2014-09-10)

60
GBSS16.0
1.
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.
Checking the connectivity of port links of the eGBTS on the U2000 client
1.
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.
Prerequisites
l
You have logged in to the LMT.
You have the permission to execute MML commands on the LMT.

NOTE
Check security patches for the OMU OS every half a year.
Issue 02 (2014-09-10)

61
GBSS16.0
Context
l
You do not need to install security patches for the OMU OS if the BSC6900 OMU OS is
SUSE Linux.
This document uses an upgrade in dual-OMU mode as an example. The upgrade in singleOMU mode is similar.
Checking the security patch version of the OMU OS (BSC6900)
Procedure
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. In the Software Center area, choose Version Software > Wireless
Product Line > SingleRAN > MBSC 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.
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.
Windows OS/SUSE Linux OS
1.
Issue 02 (2014-09-10)

Product Line > SingleRAN > SRAN O&M tools to obtain Dopra_Linux_USB
Disks.zip.
62
GBSS16.0
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
1.

Product Line > SingleRAN > MBSC 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.
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.

In the Software Center area, choose Version Software > Wireless Product Line >
SingleRAN > MBSC 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.
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.
1.

In the Software Center area, choose Version Software > Wireless Product Line >
SingleRAN > MBSC to obtain BSC6910 Guide to RTOS Remote Patch Upgrade.
2.
Install security patches by referring to the downloaded BSC6910 Guide to RTOS

Remote Patch Upgrade.
----End

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.
Issue 02 (2014-09-10)

63
GBSS16.0
Prerequisites
l
Checking whether the OMU OS hardening is required
Procedure
Whether to harden the OMU OS is determined by 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.
Figure 6-2 Dialog box displayed during the remote login
3.
Issue 02 (2014-09-10)

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.
64
GBSS16.0
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 RDPTcp 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.
Figure 6-3 Terminal services configuration interface
Issue 02 (2014-09-10)

65
GBSS16.0
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
Issue 02 (2014-09-10)

66
GBSS16.0
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.
l
Issue 02 (2014-09-10)
If the OMU OS needs to be hardened as queried in 4, go to Implementing OS

Hardening. Otherwise, no more operations are required.
Implementing OS hardening
67
GBSS16.0
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.
1.

In the Software Center area, choose 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.
l

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
OMU Administration Guide Changing Users' Passwords.
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, root user, db_user, FtpUsr, and OS administrator comply with the
password complexity policy.
l
Passwords for root user and db_user consist of upper- and lower-case letters, digits, special
characters (such as `~!@#$%^&*()-_=+\|[{}];:'",<.>/?), and space. The password length
range from 8 to 32 characters.
The password for the administrator of the operating system must comply with the password
policy queried by running the DSP OSPWDPOLICY command. The password policy can
be set by running the SET OSPWDPOLICY command.
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.
Issue 02 (2014-09-10)

68
GBSS16.0

The OMU key needs to be updated periodically (recommended period: 6 months) to prevent it
from being disclosed.
Prerequisites
l
BSC6910.
Procedure
Step 1 Run the UPD KEYMATERIAL command.
----End
Issue 02 (2014-09-10)

69
GBSS16.0
GBSS 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.
Issue 02 (2014-09-10)

70
GBSS16.0
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
Monitor the GBSS fault

alarms.
No BSC6900/BSC6910 or base
station alarms exist.
Monitor the GBSS events.
No BSC6900/BSC6910 or base
station events exist.
Collect the GBSS alarm

and event statistics.
Monitor the cell status.
The initialization status of the

cells should be Yes and the
channel fault status should be
No.
Monitor the condition of

cell resources.
Monitor the performance

counters.
Values meet the requirements.
Save the performance

Query and save

BSC6900/BSC6910
operation logs.
Query and save other logs

of the BSC6900/
BSC6910.
10
Check the GBTS running

status.
All GBTSs are running

correctly.
11
Check the automatic NE

backup function.
The automatic NE backup

function is normal.
Operation
Record
You can download the daily maintenance record.
Issue 02 (2014-09-10)

71
GBSS16.0
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
Issue 02 (2014-09-10)
Task
Expected Result
Perform the NE health

check.
All checked items are normal.
Check the running status of

the OMU.
See Table 1 in "Procedure" in 5.2

Checking the Running Status of
the OMU.
Check the running status of

the GBAM server.
The hard disk and memory space

are sufficient.
Check the BSC6900/

BSC6910 board status.
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 Standby normal.
Check the base station

board status.
The status of each board is normal.
Check the BSC6900/

BSC6910 clock.
The clock source status is normal.
Check the base station

clock status.
The clock source status is normal.
Back up the system data.
Back up the license

information.
10
Analyze the performance

11
Collect historical alarms

and events.
12
Check the communication

between NEs and the
U2000.
All NEs communicate with the

U2000 normally.

Operation
Record
72
GBSS16.0
You can download the 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
SN
Task
Expected Result
Analyze customer complaints.
Prepare an NE performance
report.
Prepare a performance report.
Check the disk space on the

terminal system.
The disk space on the

terminal system meets the
requirements.
Check the maintenance terminal

system for viruses.
The system is free of any

virus.
Check the connectivity of port

links.
The port links are

connected.
Check security patches for the

OMU operating system.
The patches of the local

operating system are the
latest patches on the
network.
Check the OS hardening.
Check weak passwords and

others.
The password complexity

strategy is followed.
10
Update the OMU key.
Operation
Record
You can download the monthly maintenance record.
Issue 02 (2014-09-10)

73

GBSS16.0 Routine Maintenance Guide (02) (PDF) - en

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GBSS16.0 Routine Maintenance Guide (02) (PDF) - en

Uploaded by

Copyright:

Available Formats

GBSS16.

Routine Maintenance Guide

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Huawei Industrial Base

Huawei Proprietary and Confidential

About This Document

About This Document

The mapping single-mode

Huawei Proprietary and Confidential

About This Document

Huawei Proprietary and Confidential

About This Document

Times New Roman

Normal paragraphs are in Times New Roman.

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

Book titles are in italics.

Examples of information displayed on the screen are in

The keywords of a command line are in boldface.

Command arguments are in italics.

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

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Optional items are grouped in braces and separated by

Optional items are grouped in brackets and separated by

Huawei Proprietary and Confidential

About This Document

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

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

Press the keys concurrently. For example, pressing Ctrl+Alt

Press the keys in turn. For example, pressing Alt, A means

Select and release the primary mouse button without moving

Press the primary mouse button twice continuously and

Huawei Proprietary and Confidential

4 GBSS Daily Maintenance Guidelines.......................................................................................9

5 GBSS Weekly Maintenance Guidelines.................................................................................33

Huawei Proprietary and Confidential

5.4 Checking the BSC6900/BSC6910 Board Status..........................................................................................................40

6 GBSS Monthly Maintenance Guidelines...............................................................................55

7 GBSS Routine Maintenance Record........................................................................................70

Huawei Proprietary and Confidential

Updated the description of 6.7 Checking Security Patches

Huawei Proprietary and Confidential

Added operations of encrypting NE backup files. For

Added the function of updating the OMU key. For details,

Added the following types of logs in the log information

Huawei Proprietary and Confidential

Table 2-1 High-risk operations

Some operations on hardware,

High-Risk Hardware Operations in

Board replacement may have

Incorrect execution of some

High-Risk Command List in

Huawei Proprietary and Confidential

3 GBSS Routine Maintenance Overview

GBSS Routine Maintenance Overview

About This Chapter

Huawei Proprietary and Confidential

3 GBSS Routine Maintenance Overview

To modify GBSS configurations, see GBSS Reconfiguration Guide.

3.2 GBSS Tools