BSC6900/BSC6910 GSM Fault Location Information Collection P-0

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-1

 《Fault Location Information Collection》 is the first one of the troubleshooting series
courses. Master a variety of collection methods of fault location information, you can lay
the foundation for learning the following troubleshooting courses.
 If we focus on collecting a variety of original information in the early stage of
troubleshooting, in many cases, it can help the maintenance personnel to narrow the
scope of fault diagnosis greatly, to speed up and improve the accuracy of fault location. It
has positive significance for improving the timeliness and effectiveness of troubleshooting,
reducing the risk of incorrect operation to the equipment.
 Please guide the trainee that the troubleshooting introduced in this course is categorized
on the basis of common 6 phenomena from the live network, but not the causes of fault.
Please focus on what need to be collected and how to collect the location information
when we meet with a specific fault phenomenon.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-2

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-3

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-4

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-5

 Single-OMU Mode
 When the BSC6900 is configured with one OMUa/OMUb/OMUc board, it works in single-OMU
mode.
 When the BSC6910 is configured with one EOMUa board, it works in single-OMU mode.
 If the OMU is faulty, you cannot perform OM on the BSC6900/BSC6910. Therefore, the system is
unreliable when the OMU works in single-OMU mode.
 Dual-OMU Mode
 When the BSC6900 is configured with two OMUa/OMUb/OMUc boards, it works in dual-OMU
mode.
 When the BSC6910 is configured with two EOMUa boards, it works in dual-OMU mode.
 In dual-OMU mode, the OMUa/OMUb/OMUc/EOMUa board working in active mode is called the
active OMUa board, that is, the active OMU; the OMUa/OMUb/OMUc/EOMUa board working in
standby mode is called the standby OMUa board, that is, the standby OMU.
 When the BSC6900/BSC6910 is in dual-OMU mode, the OMU can operate properly with high
reliability. When a hardware or software fault occurs on the active OMU, the standby OMU is
automatically switched over and works in active mode. It continues to provide services for users and
the host
 BSC6900/BSC6910 GSM Fault Location Information Collection P-6

 . Active/Standby Workspaces of the OMU

 The active/standby workspaces of the OMU refer to the active/standby workspaces for storing the
version files on the OMU. Each workspace is used to store files of different versions.
 The relation between the active/standby workspaces is relative. The active/standby relation depends on
the storage location of the running version. The workspace that stores the running OMU version files is
the active workspace, and the other is the standby workspace.
 The active/standby workspaces of the OMU are used for the upgrade and rollback of the
BSC6900/BSC6910 versions, thus enabling quick switching between versions.
 The active and standby workspaces of the active OMU correspond to the active and standby
workspaces of the standby OMU respectively. Between the active and standby OMUs, the files in the
active workspaces are automatically synchronized in real time, but those in the standby workspaces
need to be synchronized manually.
 BSC6900/BSC6910 GSM Fault Location Information Collection P-7

 Data Synchronization
 The OMU data is dynamic, which changes when the BSC6900/BSC6910 is working. After
the standby OMU starts, the active OMU data is fully synchronized, and the increments are
synchronized. This ensures that the OMU can work normally after a switchover.
 The standby OMU synchronizes its data with that of the active OMU board every second.
 File Synchronization
 The synchronization between active and standby OMU files is mainly applicable to dynamic
files. The dynamic files include the license file, board program, BOOTROM file, DSP file,
patch file, and performance statistics file. The software management module on the
standby OMU regularly checks the active OMU files and synchronizes the dynamic files on
the standby OMU with those on the active OMU. This ensures that the files on the active
and standby OMUs are the same.
 Duration of the synchronization between the active OMU files and standby OMU files is
seven minutes. The time needed for the synchronization varies according to the size and
quantity of the files to be synchronized.
 Time Synchronization
 Time synchronization means that the sntp module on the standby OMU regularly
synchronizes the time with the sntp module on the active OMU. This ensures that the time
on the active and standby OMUs is the same.
 Run the command LST SNTPCLTPARA can query the parameter values of the SNTP client
and the information of the SNTP server. The results of the execution include the
synchronization period, normally the value is 60 minutes.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-8

 Directory Structure
 The version_a and version_b folders save active and standby OMU workspace
files, respectively, or in reverse order.
 You can run the LST OMUAREA command to query the OMU workspaces. If the
Workarea flag is version_a, the version_a folder saves active workspace files.
 Command SWP OMUAREA can be used to switch over the active and standby
OMU workspaces for OMU version upgrade and rollback. Please don't use this
command in other cases.
 Description of common file folders
 /bam/common/fam/pfm/: Stores traffic statistics reported by an NE to the
M2000.
 /bam/version_a/ftp/COLLOGINFO/: Stores log collection results.
 /bam/version_a/ftp/export_cfgmml/: Stores exported MML scripts.
 /bam/version_a/ftp/trace/: Stores files recording traced message.
 /upgrade/: Stores the software package of the version to be upgraded.
 /weblmt/: Stores host files and files recording LMT online help associated with
the LMT.
 Note:
 If the /upgrade directory does not exist, run the mkdir /mbsc/upgrade command
to create the installation directory on the OMU.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-9

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-10

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-11

 Please guide the trainee that the troubleshooting introduced in this course is categorized
on the basis of common 6 phenomena from the live network, but not the causes of fault.
Please focus on what need to be collected and how to collect the location information
when we meet with a specific fault phenomenon.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-12

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-13

Common Fault On-site Location Information Back-office Location Information

MS can’t access 1. BSC configuration data file 1. Log files: Debug log files,
to the GSM 2. Alarm files Host running log files, BTS log
network 3. Original traffic measurement files, Lastwords, *.hrdlog,
files Fault log files, OMU logs
4. Log file: Operation log files (bootp logs and ftp logs)
5. Signaling trace files: Abis 2. Hardware related: Bar code
interface LAPD/OML/RSL trace of a board (including the bar
files, A interface trace files, Um codes of subboards)
interface CS trace files, Single 3. TEMS DT information
user CS trace files
6. Transmission related: Query
result of E1/T1 ports status and
parameters, Results of BERS
monitoring

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-14

Common Fault On-site Location Information Back-office Location Information

MS can make a call, but 1. BSC configuration data file 1. Log files: Debug log files, Host running
the voice quality is poor 2. Alarm files log files, BTS log files, Lastwords,
3. Traffic statistics result files: *.hrdlog, Fault log files, OMU logs (bootp
Channel related, Interference band logs and ftp logs), DSP debug
traffic statistics, Receive quality traffic logs(BSC6900)/UP debug logs(BSC6910)
statistics 2. Hardware related: Bar code of a board
4. Log files: Operation log files, The (including the bar codes of subboards)
unilateral connection log for GSM
5. Signaling trace files: Abis interface
LAPD/OML/RSL trace files, Single user
CS trace files
6. Snapshot of the channel status
query result
7. Test call records
8. Transmission related: Query result
of E1/T1 ports status and parameters,
Results of BERS monitoring

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-15

 Export Configuration Data MML Script: EXP CFGMML

 Use this command to export the configuration data on the OMU as an MML script
file. By default, the MML script is located in the /ftp/export_cfgmml directory on
the active workspace of the active OMU and named CFGMML-BSCX-IP-
YYYYMMDDHHMMSS.zip (X is the BSCID).
 You can download the data file from OMU to the PC using File Manager or FTP
Tools.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-16

 The File Manager doesn’t support download by file folders.

 The File Manager can display a maximum of 1,000 pieces of data. If the number of files in
the directory exceeds 1,000, some log files may not be displayed. Therefore, you must use
other methods to obtain required information.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-17

 Procedure
 Choose Task Schedule > Task Management (application style) or Maintenance > Task
Management (traditional style). The Task Management window is displayed.
 Click New. The New Task dialog box is displayed.
 TIP: Choose Task Type > Backup > NE Backup in the navigation tree. Double-click the
NE Backup node. The New Task dialog box is displayed. By default, the system sets Task
Type to NE Backup.
 Set the basic information about the task.
 Type the name of a scheduled task in the Task Name field.
 Select NE Backup from the Task Type area.
 Select One-time or Periodic from the Execution Type area.
 Click Next to set the time for performing the task.
 Click . In the displayed Date/Time Selection dialog box, select the start time for performing
the task.
 NOTE: Start Time must be later than the current server time.
 The One-time task supports Run At Once.
 Perform relevant operations according to the task type, that is, one-time task or periodic task.
 Click Next, and select the backup mode. You can select All NEs, By NE Type, or By NE in the
Backup Type area. By default, the system selects All NEs. All NEs on the network are to be backed
up.
 Click Finish.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-18

 Procedure
 Choose NE File > NE Backup (application style) or Maintenance > Backup
Management > NE Backup (traditional style). The NE Backup window is displayed.
 Select an NE type from the drop-down list.
 In the navigation tree, select the NEs whose data needs to be backed up.
 NOTE: To back up data of a CGPOMU sub-NE, select and back up the CGPOMU
data.
 If the icon in front of an NE is displayed as , it indicates that the NE is
disconnected. In such a case, the NE data cannot be backed up or restored.
 TIP: To select all the NEs, click the root node.
 You can click and enter NE names in Name to filter NEs in the navigation
tree.
 Click to sort NEs alphabetically.
 Click Backup.
Click Yes in the displayed Confirm dialog boxes, respectively.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-19

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-20

 Set the storage capacity and time limit of the alarm log (SET ALMCAPACITY)
 If the alarm logs exceed the maximum storage capacity or time limit, the system
will automatically clear the earliest logs.
 In the database, the current alarm data, alarm log data, and event log data are stored in
three separate tables. The M2000 provides the function of exporting data from tables
when the size of the data in tables exceeds the threshold. This function is implemented
through the configuration of the M2000 server. The function cannot be modified on the
M2000 client.
 List of current alarms (tbl_cur_alm): Saves the details of uncleared alarms,
unacknowledged alarms, and cleared and acknowledged alarms whose lifecycle is
not terminated.
 List of history alarm logs (tbl_alm_log_SN): Saves cleared and acknowledged fault
alarms.
 List of event logs (tbl_event_log_SN): Saves the raw data about event alarms.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-21

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-22

 The size of the FM database is limited. As the size of the alarm/event data becomes
increasingly large, the free space of the alarm/event database decreases. As a result, the
handling performance of the FM database deteriorates. To avoid this problem, you need to
dump some alarm/event data to the specified file.
 The M2000 allows you to export alarm/event data if the data size exceeds the threshold. In
the Task Management window on the M2000 client, choose Database Capacity
Management > Alarm/Event Data. Then, set the conditions for exporting alarms/events.
Threshold export indicates that the M2000 exports and deletes the alarms/events that
expire at the specific time every day. On the M2000 client, you can set the number of days
during which the saved data needs to be exported, the time for exporting data, and the
format of the file that data is exported as. Currently, data is exported as an .xml or .csv file.
 Procedure
 Choose Task Schedule > Task Management (application style).
 In the Task Management window, choose Database Capacity Management in
the navigation tree.
 In the Task Management window, double-click the Alarm/Event Log Dump
task in the task list.
 In the Attribute dialog box, modify common and extended parameters.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-23

 Procedure
Step Operation Description
1 Choose Task Schedule > Task Management (application style)
2 In the navigation tree on the left of the Task Management window, choose Alarm/Event Log
Dump.

3 In the navigation tree on the left of the Task Management window, choose Database Capacity
Management, In the Task Management window, double-click the Alarm/Event Log Dump task in
the task list.
4 In the Attribute dialog box, modify common and extended parameters.
Click OK.
Note:
 Compress file after dump(Default value: ): Indicates whether
exported files are compressed. It is recommended to compress export files when a user
wants to store them or when the disk space is insufficient. Export files are compressed in
ZIP format, and original files are deleted after compression.
 File type(Default value: ): This parameter indicates the format
of the dump files of logs.
 File path: This parameter indicates that dump log files are saved to the specified path on
the server.
The dump path of alarm data is ( )

The default value cannot be changed.

 Storage period in database (Default value: ): Number of days

for which historical alarm or event logs are stored in the database. The M2000 dumps
historical alarm or event logs whose storage durations exceed this specified value. A
historical alarm or event log table in the database stores at most seven days' data. To
improve dump performance, the M2000 dumps an entire historical alarm or event log
table instead of part of a table. Therefore, the database may store historical alarm or
event logs of zero to seven days before the duration specified by Storage period in
database.
 File size (Default value: ): If the size of files in the dump
directory exceeds the value of this parameter, the M2000 deletes the oldest dump files
until the size of files in this directory becomes less than the value of this parameter.
 File count(Default value: ): If the number of files in the dump
directory exceeds the value of this parameter, the M2000 deletes the oldest dump files
until the number of files in this directory becomes less than the value of this parameter.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-24

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-25

 A performance measurement task must contain the following information: measurement

counters, measured objects, and measurement periods.
 The NE performance measurement range set on the M2000 client is the basis for saving
the NE results to the performance database. The counter results of only the NE objects that
are set for measurement can be analyzed by the mediation and then saved to the M2000
performance database.
 By default, the M2000 collects and stores common counter measurement results of
common objects. In such a case, manual settings are not required and the results
collected by default can meet the data requirements in most OM scenarios.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-26

 Operations

Step Operation Description

1 Choose Result > Query Result (application style), or click . The Query Result window is
displayed.
2 Click New Query, or right-click any node except OSS and System in the navigation tree, and then
choose New Query from the shortcut menu.

Set Organization Style to Object type or Function subset, choose the types of measurement
objects or the function subsets.
3 On the Object Settings, Counter Settings, and Other Settings tab pages, set the conditions for
querying the measurement results.
Note:

The counters that are not measured are displayed in grey in the Available Counters list. If the
counters are needed to be measured, measurement setting should be done firstly.

4 Click Query. In the displayed Result Query dialog box, the query results are displayed in a table. You
can display the query results in a line chart or a bar chart as required

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-27

 Period calculation: End time - start time = traffic measurement period

 The information about traffic measurements can be obtained by BSC local information
collection and running the COL LOG command. This method is simple and is not error-
prone.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-28

 Preparations

 Run the COL LOG command to download the performance result files.

 Run the LST LOGRSTINFO command to query the directory of the performance
result files saved in the OMU.

 Save the files from the OMU directory to the local PC using File Manager or FTP
mode.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-29

 Note
 If the performance results fail to be queried, please check whether the conditions'
setting is correct, make sure the performance results need to be queried are exiting
in the path of HW LMT\adaptor\clientadaptor\pfbTool\data.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-30

 The boards of the BSC6900/BSC6910 collect performance measurement data and

periodically report the data to the performance measurement module of the OMU.
According to the task file, the performance measurement module reports the
measurement data to the M2000 periodically. The OMU stores the maximum
performance measurement data of 25 GB or within the last 14 days. If the capacity or time
is exceeded, the data for the earliest day is deleted.
 The traffic measurement data are saved in M2000 file storage for 3 days at most, they are
used for the resynchronization after the NE is disconnected or the traffic measurement data
are lost because of other reasons. The save path of the performance measurement result files
is: /export/home/sysm/ftproot/pm
 When the performance result files enter the M2000 file storage, they will be transferred to
M2000 database at the same time. The operation like query the performance results should be
accomplished from this database. They are saved for 30 days by default and 90 days at most.
The specific saving time is also restricted by the hard disk space.
 The M2000 checks the performance database, namely, pmdb once an hour. When
the usage of the performance database reaches 90%, an alarm indicating insufficient
free space of the performance database is generated.
 The performance result files can be dumped to the specific directory at last, they are saved for
15 days by default, 3 days at least and 30 days at most. The specific saving time is also
restricted by the hard disk space.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-31

 Database capacity management tasks are system scheduled tasks that run once every day.
Their execution period cannot be modified.
 Procedure
 Choose Task Schedule > Task Management (application style). The Task
Management window is displayed.
 In the navigation tree in the left pane, choose Task Type > Database Capacity
Management > Performance Data. The created database capacity management
task is displayed in the task list in the right pane.
 Double-click the task or select the task and then click Attribute. The Attribute
dialog box is displayed.
 Set the parameters of performance database capacity.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-32

 Parameters of performance database capacity include the storage duration of the data in
the performance database, and whether to export the data and relevant parameters. The
system regularly deletes expired data from the database according to user settings.
Through database capacity management tasks, the database capacity is maintained within
a proper range to avoid database faults caused by insufficient database capacity.
 Database capacity management tasks are system scheduled tasks that run once every day.
Their execution period cannot be modified.
Step Operation Description
1 Choose Task Schedule > Task Management (application style). The Task
Management window is displayed.
2 In the navigation tree in the left pane, choose Task Type > Database Capacity
Management > Performance Data.

3 The created database capacity management task is displayed in the task list in the right
pane.

4 Double-click the task or select the task and then click Attribute. The Attribute dialog box
is displayed.
5 Set the parameters of performance database capacity.

Number of days within which data can be stored in the performance database. The
performance data whose storage duration expires is automatically dumped or deleted.
Common Mode: You must manually set No.Of Hold Days in The Database.
Configuration Mode: The system automatically reads the number of days within which
the files can be stored from the configuration file.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-33

 Query the collected files: LST LOGRSTINFO

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-34

 FTP Client and File Manager have the same function which can obtain log, upload data
configuration file and so on.
 When the OMU is installed, the default user name is FtpUsr, initial password is
hwbs@com.
 If you forget the password, you can run the MOD FTPPWD command to change the
password of the FTP user name to the designated one.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-35

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-36

 The operations of Collecting BSC Local Information collect the BSC or BTS statistics, including the
performance statistics, logs, and alarm files.
 Through menu operations
 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is
displayed.
 In the BSC Maintenance tab page, choose Maintain BSC > Maintain User Resources >
Collect BSC Local Information. The Collect BSC Local Information tab page is
displayed.
 Set the time period for collecting the statistics in the Time Setting area.
 Select the fault type from the Fault List in the Set Basic Information area to collect the
required fault statistics. The corresponding file type is automatically selected. You can select
more file types from the File Type List to collect the corresponding statistical files.
 Set the FTP server parameters in the Upload configure area, and click Execute to collect
the BSC statistics. The progress of collecting the statistics is displayed in the Progress(%)
bar, and the collected files are displayed in the Result tab page.
 Enter the IP address of the FTP server in the FTP Server IP box, specify the path
for saving the uploaded files on the FTP server in the Upload Path box. FTP User
Name and FTP Password are admin by default. You can also change the default
settings on the FTP server.
 To upload the collected logs from the OMU to the FTP server, click Upload. Then, you can
retrieve the files in the specified upload path.
 To delete the collected logs, click Delete File.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-37

 Operation

Step Operation Description

1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page is displayed. In
the BSC Maintenance tab page, choose Maintain BSC > Maintain User Resources > Collect BSC
Local Information. The Collect BSC Local Information tab page is displayed.
2 Set the time period for collecting the statistics in the Time Setting area.

Note:
If you select All Time, the LMT retrieves the time limit from the configuration file. The time limit is 30
days by default.
3 Select the fault type from the Fault List in the Set Basic Information area to collect the required fault
statistics. The corresponding file type is automatically selected. You can select more file types from the
File Type List to collect the corresponding statistical files.

Note:
If you select BTS Fault from the Fault List, the Select Sites area is activated so that you can further
specify the target BTS to collecting the statistics.

4 Set the FTP server parameters in the Upload configure area, and click Execute to collect the BSC
statistics. The progress of collecting the statistics is displayed in the Progress (%) bar, and the collected
files are displayed in the Result tab page.

 Enter the IP address of the FTP server in the FTP Server IP box, specify the path for saving the
uploaded files on the FTP server in the Upload Path box. FTP User Name is admin and FTP
Password is hwbs@com by default. You can also change the default settings on the FTP server.
 If you select The common debug log in the File Type List, the Subrack No. in the Setting
area can be specified. Otherwise, the files of all the subracks are uploaded by default.
 If the FTP server is not started, run the FTP server through downloading the FTP Tool.
5 To upload the collected logs from the OMU to the FTP server, click Upload. Then, you can retrieve the
files in the specified upload path.
6 To delete the collected logs, click Delete File.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-38

 Description about logs (Suppose version_a is the active workspace of OMU)

Log Type Save Path Description

PFM_RESULT(Performance /bam/version_a/ftp/CO The log records the traffic statistics reported by a
Result File) LLOGINFO/PFM-LOG/ network element (NE) to the M2000. It is used for
analyzing traffic statistics.
HOST_PFM_RESULT(Performa /bam/version_a/ftp/CO The log records the traffic statistics reported by a
nce Result File from LLOGINFO/PFM-LOG/ board to the OMU. It is used for analyzing board
Host) traffic statistics.
ACTIVE_DEF_MEAS_FILE(Act /bam/version_a/ftp/CO This is the active definition file for traffic
ive Default Measurement LLOGINFO/PFM-LOG/ statistics delivered by the M2000 to an NE. It is
Task File) used for analyzing traffic statistics.
STANDBY_DEF_MEAS_FILE(St /bam/version_a/ftp/CO This is the standby definition file for traffic
andby Default LLOGINFO/PFM-LOG/ statistics delivered by the M2000 to an NE. It is
Measurement Task File) used for analyzing traffic statistics.
PFM_SWITCHS(The Switches – Enumeration values are reserved.
Information for
Performance)
HISTORY_ALARM(Historical /bam/version_a/ftp/CO The log records all the alarms and events reported
Alarm File) LLOGINFO/ALM-LOG/ by the NE. It is used for analyzing alarm and event
reporting and clearing.
HISTORY_FAULT(Historical /bam/version_a/ftp/CO The log records all the faults which cause
Fault File) LLOGINFO/ALM-LOG/ historical alarms. It is used for analyzing alarm
reporting and clearing.
ALM_SYSTEM_CFG(The /bam/version_a/ftp/CO The log records the configuration information
Configured Information LLOGINFO/ALM-LOG/ related to alarm management. It is used for
of Alarm) analyzing alarm and event reporting and clearing.
SECURITY_LOG(Security /bam/version_a/ftp/CO This is the security log of an NE. It is used for
Logs) LLOGINFO/SEC-LOG/ analyzing the information about historical security-
related operations.
OPT_LOG(Operation Logs) /bam/version_a/ftp/CO This is the operation log of an NE. It is used for
LLOGINFO/OPT-LOG/ analyzing the operation and maintenance on the NE.
OMU_LOG(The Log /bam/version_a/ftp/CO This is the running log and status log of the OMU.
Information of OMU) LLOGINFO/SINGLE-BAM/ It is used for analyzing the OMU problems and
status.
BSC_CFG_MML(The Data /bam/version_a/ftp/CO The log records the BSC configuration data
Configure File of the LLOGINFO/CFG- information. It is used for checking the
BSC) LOG/ExportCfgmml/ configuration data during data restoration.
CELL_BASIC_INFO(The /bam/version_a/ftp/CO The log records the cell basic information. It is
Basic Information of LLOGINFO/CFG- used for checking the mapping between the cell ID
Cells) LOG/CellBasicInfo/ and internal cell ID.
BSC_SERIES_NO(The Series /bam/version_a/ftp/CO The log records the BSC equipment serial number
No. of the BSC) LLOGINFO/CFG-LOG/ (ESN) information. It is used for license check. The
ESN uniquely identifies a BSC.
DB_BAK(The Backup File /bam/version_a/ftp/CO The log records the information of OMU database that
of the Database) LLOGINFO/CFG- has been backed up. It is used for data restoration.
LOG/MysqlDbBak/
MEM_DB_BAK(The Backup /bam/version_a/ftp/CO The log records the information of OMU memory
File of the Database in LLOGINFO/CFG- database that has been backed up. It is used for
Memory) LOG/MemDbBak/ locating the problem of inconsistency between memory
database and MYSQL database.
BTS_BASIC_INFO(The Basic mbsc/bam/version_a/ft The log records basic information of base station
Information of Sites) p/COLLOGINFO/BTS-LOG boards, base station attributes, and base station
compressed logs. It is used for analyzing basic base
station equipment information.
BTS_CHECK_LOG(The mbsc/bam/version_a/ft The log records base station logs, including
Examination File of BTS) p/COLLOGINFO/BTS-LOG temperature logs, board replacement logs, compressed
logs, common logs, and frequency scan logs.
Confidential Information of Huawei. No Spreading Without Permission
 BSC6900/BSC6910 GSM Fault Location Information Collection P-39
Log Type Save Path Description
BTS_DEBUG_LOG(The mbsc/bam/version_a/ The log records base station logs, including temperature
Debug File of ftp/COLLOGINFO/BTS- logs, board replacement logs, compressed logs, common
BTS) LOG logs, and frequency scan logs.
BTS_CHR_LOG(The – Enumeration values are reserved.
CHR Log of BTS)
TRX_LOG(The TRX – Enumeration values are reserved.
Log)
BTS_NET_TABLE(The – Enumeration values are reserved.
Net Table
Information of
BTS)
DEBUG_LOG(The /bam/common/fam/fam The log records the information of abnormal software
Common Debug Log) logfmt/ running. It is used for analyzing software defects.
LAST_WORD(The /bam/common/fam The log records the last words information before the
Last Word Log) board is abnormally reset. It is used for locating the
problem of abnormal board reset.
(BSC6900)DSP_DEBU /bam/common/fam/fam The log records the DSP abnormal information during
G_LOG(The Debug logfmt/ software running. It is used for locating DSP faults.
Log of DSP)
(BSC6910)UP_DEBUG /bam/common/fam/fam The log records the CPUs abnormal information during
_LOG(The Debug logfmt/ software running. It is used for locating EGPU faults.
Log of CPUs)
HOST_LOG(The /bam/common/fam/fam The log records the running status of the host.
Running Log of log/
the Host)
2G_CHR_LOG(The /bam/common/fam/fam The log records the system resources used, call status
CHR Log for GSM) logfmt/gchr/ change time, and signaling. It is used for analyzing
whether the call procedure is normal.
2G_UNILATERAL_CON /bam/common/fam/fam The log records the time of and the system resources used
NECT(The logfmt/ by the call with problems such as one-way audio and
Unilateral cross-talk. It is used for analyzing the cause for voice
Connection Log faults.
for GSM)
BSC_INFO(The /bam/version_a/ftp/ The log records the BSC software patch information, and
Basic Information COLLOGINFO/BSC-LOG/ the bar code, software information, hardware information,
of the BSC) loading software information, and license of each board.
It is used for querying whether the software version,
data, and license loaded on the board are correct.
GCSR_LOG(The CHR /bam/common/fam/fam The log records the basic information of abnormal calls,
Log for Single logfmt/ such as call initiating time, site, cell, and TRX where
User of GSM CS) the call is initiated.
GPSR_LOG(The CHR /bam/common/fam/fam The log records the basic information (such as cell
Log for Single logfmt/gphr/ index, CGI, IMSI, and TLLI), internal messages, and
User of GSM PS) messages over the Um, Abis, and Gb interfaces for a call.
It is used for locating faults during a PS call.
AIDG_LOG(A /bam/common/fam/fam The log records the A interface dialing test information.
Interface Dial logfmt/ It is used for locating the call faults caused by
Diagnose Log) transmission failures on the A interface.
BIOS_LOG(BIOS /bam/common/fam/fam The log records abnormal running of the BIOS system on
Log) logfmt/ the board. It is used for locating BIOS faults.
CALLFAULT_LOG(CAL /bam/common/fam/fam The log records network access failures and call drops.
LFAULT Log) logfmt/ It is used for analyzing the cause for network access
failures and call drops.
PCHR_LOG(PCHR /bam/common/fam/fam The log records detailed information about each call,
Log) logfmt/pchr 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(SYSF /bam/common/fam/fam The log records serious software or hardware faults such
AULT Log) logfmt/sysfault/ as resource leakage and device fault. It is used for
network health check.
 BSC6900/BSC6910 GSM Fault Location Information Collection P-40

 Note:
 Time modes include ONTIME (Fixed Time) and RELATIVE_T (Relative Time).
"ONTIME" indicates the time between two exact time. "RELATIVE_T" indicates
the time before the current time.
 The time rules are as follows: If the start time and end time are not specified, the
records from the earliest time to the latest time are exported by default. If only
the start time is specified, the records from the start time to the latest time are
exported. If only the end time is specified, the records from the earliest time to the
end time are exported.
 The file is saved as a text file in the ftp\operator_log directory of the main area
directory of the OMU.
 When the user privacy-related information is collected, the privacy-related
information may be anonymity for user's privacy protection" all the context.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-41

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-42

 The trace modes of signaling tracing on an interface are divided into the following two
types:
 Report
 In this mode, the trace results are reported in real time. The OMU sends the traced
messages to an LMT PC directly, and the output file is automatically saved to the
LMT PC in the *.tmf format.
 Save to OMU
 In this mode, you can set the trace interval. The traced messages are saved on the
OMU and are not reported to the LMT PC. The output file is saved to the OMU in
the *.tmf format. The default path is \mbsc\bam\common\fam\trace directory of
the OMU.
 Note:
 When user privacy-related information is involved all the context(for example IMSI/
IMSI/ IMEI/MSISDN/MAC address/IP address), the privacy-related information may
be anonymity for user's privacy protection" .

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-43

 Procedure
 Choose Start > All Programs > Huawei Local Maintenance Terminal >
TrafficRecording Review Tool.
 The Open dialog box is displayed, prompting you to select the target file. Browse
to the folder where the trace files are saved, and select the target file.
 Click Open or double-click the file. The contents of the file are displayed in the
TrafficRecording Review Tool window.
 Browse the messages or double-click a specific one to read the details.
 To view the contents of more files, choose File > Open. In the Open dialog box,
select and open files to view the traced messages that are saved in the files.
 You can further perform the following operations by right-clicking in the
TrafficRecording Review Tool window.
If... Then...
You choose Save All Messages from All the messages are saved in the window in
the shortcut menu, .tmf or .txt format.
You choose Save Selected Messages The selected messages are saved in .tmf or .txt
from the shortcut menu, format.
You choose Filter By Byte from the Set the filter to selectively display the
shortcut menu, information.
You choose Filter By Column from Filter the information by column to selectively
the shortcut menu, display the information.
You choose Find from the shortcut Locate the message that you want.
menu,
Confidential Information of Huawei. No Spreading Without Permission
 BSC6900/BSC6910 GSM Fault Location Information Collection P-44

 Channel status:
 Idle indicates that the channel is normal but not occupied.
 Working indicates that the channel is normal and occupied.
 Locked/Shut down indicates that the channel is blocked.
 Subordinate Channel indicates that a channel sharing the same TRX as the
current channel is transmitting power. This is a normal state.
 Faulty indicates that the channel is faulty.
 Uninstalled indicates that the channel is not activated.
 Loopback indicates that a loopback test is being performed on the channel.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-45

 Obtaining channel status through MML command.

Step Operation Description
1 Run the MML command DSP CHNSTAT with Object Type set to SITE (Site), and BTS
Index set to an appropriate value to obtain channel status information.

 Obtaining channel status through menu operations.

Step Operation Description

1 Click Device Maintenance on the LMT main page. The Device Maintenance tab page
is displayed.
2 In the BTS Maintenance tab page, choose BTS Maintenance > Monitor Channel
Status.
3 In the displayed Monitor Channel Status tab page, set the parameters as required, and
then click Start to monitor the channel status.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-46

 If the value of Port state is Activated, network cables connected to the Ethernet port are
properly connected, but it is uncertain that Ethernet configuration is correct.

 If the value of Port state is Not Activated, network cables connected to the Ethernet
port are not properly connected.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-47

 On the LMT, click Monitor. The Monitor tab page is displayed.

 In the Monitor Navigation Tree, choose Monitor > Common Monitoring. Then,
double-click BERS Monitoring.
 In the BERS Monitoring dialog box that is displayed, set the relevant parameters. Then,
click Submit.
 The POUc board of BSC6910 supports this function.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-48

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-49

 Please connect to BSC6900/BSC6910 and fill in the blanks to finish the tasks in the
following table.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-50

 Please connect to BSC6900/BSC6910 and fill in the blanks to finish the tasks in the
following table.

Collection Item Collection Method

Debug log files 1. Run the MML command COL LOG with Log File Type set to
to collect common debugging logs.
1. Run the MML command LST LOGRSTINFO to query the path in which the common debugging log
file is saved.
The format of the file name is:
.
For example:
“BSC0000_[DEBG]00Log20101203102457_
20101203113504.log.zip” indicates that the common debugging logs were recorded for subrack
0 between 10:24:57 and 11:35:04 on December 3, 2010.
1. Obtain the common debugging log file from the queried path. The default save path is:
.
Lastwords 1. Run the MML command COL LOG with Log File Type set to
to collect lastword log files.
1. Run the MML command LST LOGRSTINFO to query the path in which the lastword log file is
saved.
The format of the file name is: .
For example: fad20120321002235.zip.
1. Obtain the lastword log file from the queried path. The default save path is :
.
Host running 1. Run the MML command COL LOG with Log File Type set to
log files to collect host running logs.
1. Run the MML command LST LOGRSTINFO to query the path in which the host running log file is
saved.
The format of the file name is:
.
For example,
BSC0000_00Log20101203102457_20101203113504.log.zip indicates that host running logs
were recorded for subrack 0 between 10:24:57 and 11:35:04 on December 3, 2010.
1. Obtain the host running log file from the queried path. The default save path is:
.
OMU logs 1. Run the MML COL LOG with Log File Type set to
(bootp logs and to collect OMU logs.
ftp logs) 1. Run the MML command LST LOGRSTINFO to query the path in which the host running log file is
saved.
The format of the file name is:
.
3. Obtain the OMU log file from the queried path. The default save path is:
.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-51

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-52

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-53

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-54

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-55

 Note:
 The DSP resources can be traced by the Traffic measurements that related to Abis
timeslot release application of BSC6900.
 The CPUS resources can be traced by the Traffic measurements that related to Abis
timeslot release application of BSC6910.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-56

 Note:

Common Fault
On-site Location Information Back-office Location Information
Phenomena
MS can’t access to 1. BSC configuration data file 1. Log files: Debug log files, Lastwords,
2. Alarm files Host running log files, BTS main
the GPRS network 3. Traffic statistics result files: Original control log files
traffic measurement files, BSC FE/GE 2. TEMS signaling trace
traffic statistics result files
4. Log file: Operation log files
5. Signaling trace files: PS Um message
trace files/GB PTP message trace file
in the cell with a problem or top
problems
6. Snapshot of the channel status query
result
7. Transmission related: Cell status
information queried by MML
commands, FE/GE port status, Check
whether the speed, duplex mode,
MTU configuration of the FE/GE ports
in two interconnected devices and
ports of the middle transmission
devices are consistent
MS can access to 1. BSC configuration data file 1. Log files: Debug log files, Lastwords,
2. Alarm files
the GPRS network, 3. Traffic statistics result files: G_Abis Host running log files, BTS main
but the GPRS traffic measurements, Traffic control log files
measurements related to Abis
service is 2. Trace files on the MS side
timeslot release application/
abnormal PDCH/DSP/CPUs resources/ GB
NS/GB LLC PDU/TBF
4. Log file: Operation log files
5. Signaling trace files: PS Um interface
message trace files, Abis interface
message trace files, Gb interface SIG
message trace files, Gb interface PTP
message trace files, Single user PS
trace files
6. Snapshot of the channel status query
result
7. PS basic MML query results

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-57

 PS basic MML query results

Step Operation Description
1 Run the MML command to query the status of the Network Service Virtual
Link (NSVL) to be verified.
Expected result: The value of NSVL State is Normal.
2 Run the MML command to query the status of the IP connection to be verified
on the Gb interface.
Expected result: The value of State is Normal.
3 Run the MML command to query the SIGBVC status of the NSE to be verified.
Expected result: The value of SIG BVC State is Normal.
4 Run the MML command to query the PTPBVC status of the NSE to be verified.
Expected result: The value of Service State is Normal.

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-58

 Note:
 Run the MML command STR BTSLOG with Log Type set to CMPLOG(Compress
Log), Board Type set to TMU(TMU/DTMU), and BTS Index set to an
appropriate value to collect BTS logs.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-59

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-60

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-61

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-62

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-63

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-64

Confidential Information of Huawei. No Spreading Without Permission

 BSC6900/BSC6910 GSM Fault Location Information Collection P-65

 Method 1
 Log in to the OMU
 Run the df -h command to query the hard disk partitioning and usage.
 If the usage of any hard disk partition exceeds 80%,
a. Save the files in the partition to another hard disk if needed. There are
two methods of transferring the files on the OMU: using the function of
file management on the LMT and running commands.
b. Log in to the OMU.
c. Run the cd target directory to go to the directory where the files to be
deleted are saved.
d. Run the rm file name or rm –r folder name command to delete the
unneeded files.
 Method 2
 Run the DSP OMUSRV command to query the available space of the partitions on the
OMU hard disk.
 If the free space of any partition on the OMU hard disk is less than 20%,
a. Back up the files on the partition that needs to be saved to a hard disk.
b. Log in to the OMU.
c. Run the cd target directory to go to the directory where the files to be
deleted are saved.
d. Run the rm file name or rm –r folder name command to delete the
unneeded files.

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-66

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-67

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-68

Confidential Information of Huawei. No Spreading Without Permission

BSC6900/BSC6910 GSM Fault Location Information Collection P-69

Confidential Information of Huawei. No Spreading Without Permission