BSC6900 Log Operation and Collection Methods INTERNAL

1 BSC6900 Log Operation and Collection

Methods

1.1 Description of the RNC Log Directory

1.1.1 Method for Querying the Main Working Area of the OMU
Run the LST OMUAREA command to check whether the current working area is version_a
or version_b and identify the directory where the software is running. Then, run the COL
LOG command to save the result to the directory of main working area.

1.1.2 COLLOG Result Directory

Run the LST LOGRSTINFO command to query the COLLOG result directory.

2023-11-03 Huawei Proprietary and Confidential 1

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.1.3 Directory of Original Log File and Description of Commonly

Used Directories
Directory Description

\mbsc\bam\common Indicates the directory that saves foreground

log files.
\mbsc\bam\common\fam Indicates the directory that saves host log
files.
\mbsc\bam\common\log Indicates the directory that saves OS log files.
\mbsc\bam\common\MeasResult Indicates the directory that saves traffic
indicator files.
\mbsc\bam\version_X\log Indicates the directory that saves OMU log
files.
\mbsc\bam\version_X\ftp Indicates the FTP root directory.
\mbsc\bam\version_X\ftp\COLLOGINFO Indicates the directory that saves COLLOG
information.

For details, see attachment 1 OMU Log File.

1.1.4 File Collection Methods

Method 1: FTP
Use FTP software (ftp://FtpUsr@1BAMIP/) or Windows resource manager.
Method 2: File manager

2023-11-03 Huawei Proprietary and Confidential 2

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.2 Database Backup

1.2.1 Summary
Log collection does not apply to the rectification of all OMU database abnormalities. To
accurately locate the cause of an OMU abnormality in certain cases, you need to collect the
backup file of the OMU. Therefore, it is necessary to master the method of collecting the
backup file of an OMU. If the backup file of the abnormal OMU is already available, you can
recover the services quickly by restoring the database.
A database can be backed up by running an MML command or using the OMUBackup tool.

1.2.2 Database Backup Through the MML Command

Prerequisite: You have successfully logged in to the Web LMT client.
1. Run the BKP DB command in the MML window on the LMT client and set the backup file
directory and file name and then save the file in a designated directory.
Example:
In the Windows operating system, run the following command:
BKP DB: BACKUPPATH="D:\BACKUP", FN="2010.08.20.BAK";
In the Linux operating system, run the following command:
BKP DB:BACKUPPATH= "\",FN="20020930.BAK";

2023-11-03 Huawei Proprietary and Confidential 3

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If no value is assigned to the BACKUPPATH parameter, the path information about the backup file that
is saved automatically will be displayed after a command is executed successfully.
Also, you can run the LST OMUAREA command to query the current working area. The default path
of a backup DB file is as follows (the path differs in different working areas):
ftp:\\xx.xxx.xxx.xxx\bam\ version_a(version_b)\data\backup\
If no value is assigned to the FILENAME parameter, the structure of the default value is BKPDB +
VERSION + TIME.bak, for example, BKPDB_V900R012C01SPC300_20100824164836.bak.

2. Obtain the backup data.

Log in to the OMU through FTP or through the telnet and obtain the backup file from the
designated directory (or default directory).

1.2.3 Database Backup with the OMUBackup Tool

1. Run the omu_backup_linker command that is saved in the directory mbsc\bam\common\
services\ on the OMU.
a. In the Windows operating system, log in to the active OMU with Remote Desktop
Connection client and then start the omu_backup_linker.exe tool.
b. In the Linux operating system, log in to the active OMU with SSH client and run the cd \
mbsc\bam\common\services command. Then, the current directory is switched to the
directory in which the tool locates
Run the \omu_backup_linker command and then press Enter to start the tool, as shown in
the following figure:

2. Start making a backup.

After a Please input a valid bkp_res_type prompt is displayed, type in backup and press
Enter.

Input a valid backup file pathname and press Enter.

2023-11-03 Huawei Proprietary and Confidential 4

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

After the preceding operation, the system starts backing up. If a "Backup OMU database
succeed!" message is displayed, it indicates that the backing up is successful and data is
backed up on the OMU.

1.3 OMU Log Collection

1.3.1 Summary
OMU logs are used to locate causes of problems such as the data inconsistency between the
host boards and the BAM, OM channel abnormality, traffic statistics missing, and board
restarting abnormality. As long as a problem involves the OMU, the OMU logs are required.
By category, the logs on the OMU are classified into OMU logs, operation logs, and alarm
logs. The BSC supports the function of collecting logs selectively according to the actual
need.

1.3.2 OMU Log Collection

Run the following MML command on the Web LMT:
COL LOG: LOGTYPE=HISTORY_ALARM-1&OPT_LOG-1&OMU_LOG-1;
After the command is executed, the OMU logs are saved to the
ftp://xx.xxx.xxx.xxx/bam/version_a/ftp/COLLOGINFO folder. The onsite engineers can log
in to the OMU through FTP or through the telnet to obtain the file.

Version_a in the path is only an example. In actual situation, you need to run the LST OMUAREA
command to check whether the current working area is Version_a or Version_b.

Onsite engineers can obtain the collected OMU logs from the COLLOGINFO folder
according to the preceding method.
If operation logs are required, send only the file in the OPT-LOG folder to the staff of the
R&D Department.
If alarm logs are required, send only the file in the ALM-LOG folder to the staff of the R&D
Department.
You can also run the LST LOGRSTINFO command to query the specific path of logs that
are saved this time.

2023-11-03 Huawei Proprietary and Confidential 5

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.4 Alarm Log Collection

1.4.1 Summary
Alarm logs can be used in locating almost every fault related to the platform and services.

1.4.2 Procedure
1. To collect alarm information, run the following command:
COL LOG: LOGTYPE=HISTORY_ALARM-1&HISTORY_FAULT-
1&ALM_SYSTEM_CFG-1;

After the command is executed, alarm information is saved to the directory: ftp:\\
XX.XXX.XXX.XXX\bam\version_Y\ftp\COLLOGINFO\LM-LOG. To obtain alarm
information, enter the OMU directory through FTP or File Manager on the LMT.
Run the LST OMUAREA command to check whether the current working area is Version_a
or Version_b and fill out the blue part according to the queried result.

1.5 Operation Logs Collection

1.5.1 Summary
Operation logs can be used in locating almost every fault related to the platform and services.

1.5.2 Procedure
To collect operation logs, run the following command:
COL LOG: LOGTYPE=OPT_LOG-1;

2023-11-03 Huawei Proprietary and Confidential 6

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

After the command is executed, operation logs are saved to the folder: ftp:\\
XX.XXX.XXX.XXX\bam\version_Y\ftp\COLLOGINFO\ OPT-LOG. To obtain the operation
logs, enter the OMU directory through FTP or File Manager on the LMT.
Run the LST OMUAREA command to check whether the current working area is Version_a
or Version_b and fill out the blue part according to the queried result.

1.6 Configuration Script Collection

1.6.1 Summary
Configuration script can be used in locating almost every fault related to the platform and
services.

1.6.2 Procedure
1. To collect the configuration script, run the following command:
COL LOG: LOGTYPE=BSC_CFG_MML-1;

After the command is executed, the configuration script is saved to the folder: ftp:\\
XX.XXX.XXX.XXX\bam\version_Y\ftp\COLLOGINFO\CFG-LOG\ExportCfgmml. To
obtain the configuration script, enter the OMU directory through FTP or File Manager on the
LMT.
Run the LST OMUAREA command to check whether the current working area is Version_a
or Version_b and fill out the blue part according to the queried result.
2. To obtain the internal configuration script, run the following command:
EXP INNERCFGMML:;

After the command is executed, the internal configuration script is saved to the folder: ftp:\\
XX.XXX.XXX.XXX\bam\version_Y\ftp\export_cfgmml. To obtain the internal configuration
script, enter the OMU directory through FTP or File Manager on the LMT.

2023-11-03 Huawei Proprietary and Confidential 7

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

Run the LST OMUAREA command to check whether the current working area is Version_a
or Version_b and fill out the blue part according to the queried result. The exported
configuration script’s default filename is CFGMML-RNCID-YYYYMMDDHHmmSS.txt

1.7 FAM Logs & Last Words

1.7.1 Summary
FAM logs record abnormalities, last words, and key statistics of each running board. In the
location of non-service problems, FAM logs are more useful.
Last words record the dying information of board resetting on the host.

1.7.2 Procedure
1. Last words:
COL LOG: LOGTYPE=LAST_WORD-1;
Go to the following path through FTP to obtain the required last words:
ftp:\\xx.xxx.xxx.xxx\bam\common\fam\ fad20100830121428.zip
Log in to the BAM through the telnet to obtain the last words.
The last words are saved in the directory \mbsc\bam\common\fam\ fad20100830121428.zip.
2. FAM Log:
COL FAMLOG: SRN=x, TP=NORMAL;
Go to the following path through FTP to obtain the FAM log file:
ftp:\\xx.xxx.xxx.xxx\bam\common\fam\famlog\
Log in to the BAM through the telnet to obtain the log file.
The file is saved in the directory \mbsc\bam\common\fam\famlog.
The format of a FAM log file is as follows:
BSC1000_00Log20100830141655_20100830143328.log.zip
"BSC1000" indicates an RNC ID and "00" indicates a subrack number.
"20100830141655_20100830143328" indicates the time when a file recording task is started
and ended. The format of a starting or ending time is year-month-day-hour-minute-second.

NOTE
Select a log file of the subrack where the fault occurs, and the time when the file is recorded must cover
the time when the fault occurs.

2023-11-03 Huawei Proprietary and Confidential 8

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.8 CHR & PCHR &CALLFAULT&DEBUG Log Collection

1.8.1 Summary
V911 Call history records (CHRs) are the information of all abnormal calls, including key
processes and error information.
In the versions later than V912, the original CHR log is divided into three parts: PCHR,
CALLFAULT, and CHR. The details are as follows:
1. PCHR, records 20 signaling messages and the status of the air interface before services of a
user are terminated. PCHR is used to analyze problems related to KPIs.
2. CALLFAULT, records the faults related to access and call drop. CALLFAULT is used to
analyze the causes to these faults.
3. CHR, records the exceptions (except the faults related to access and call drop) that occur in
the calling process. CHR is used to analyze the causes to these exceptions that occur in the
processes such as soft handover, hard handover, migration, and cell update.
Debug logs are the logs of most modules in the MPU, used for the location of resource
allocation and service problems.

1.8.2 Procedure
1. Collection methods for V911
Method 1:
ftp:// xx.xxx.xxx.xxx /bam/common/fam/famlogfmt/
Method 2:
Log in to the BAM remotely and then access the \\mbsc\bam\common\fam\famlogfmt
installation directory.
The prefix of the file name is UCHR or DEBG.
2. Collection methods for V912 or a later version
Method 1:
ftp://xx.xxx.xxx.xxx//bam/common/fam/famlogfmt/
Method 2:
Log in to the BAM remotely.
Installation directory: \\mbsc\bam\common\fam\famlogfmt
The prefix of the file name is CHR, PCHR, CALLFAULT, or DEBG.
The format of a log is as follows:
BSC1000_[XXXX]00Log20100829103008_20100830000047.log.zip
The parameter BSC1000 indicates an RNC ID. The parameter
20100829103008_20100830000047 indicates the time when a file recording task is started
and ended. The format of a start or end time is year-month-day-hour-minute-second.
The method of getting the CHR&PCHR&DEBUG&CALLFAULT file:

2023-11-03 Huawei Proprietary and Confidential 9

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

Choose WebLMT > File Manager to open the WebLMT File Manager window, find the
famlogfmt directory below, and download the CHR&PCHR& DEBUG&CALLFAULT file to
local directory.

To provide CHRs, debug logs, and text logs in a quick and effective manner, the onsite engineers should
know the specific occurrence time of the fault and the faulty subrack No., and then obtain the useful logs
according to the occurrence time and faulty subrack No. Thus, the size of the file can be minimized,
reducing the delay of file transmission.

1.9 Measurement Data Collection

1.9.1 Summary
The measurement data records various counter values on the RNC. As the basis for network
KPIs, the measurement data reflects the changes of KPIs and the direct cause of KPI
degradation.

1.9.2 Performance Data Procedure

Method 1: Download the selected files to local directory, and compress manually.
Recommend for use.
Method 2: Compress both the normal period and short period file automatically to PFM-
LOG.zip according to the input date.
Method 1: Go to the following directory to obtain the measurement result file that is saved
automatically:
\bam\common\MeasResult

2023-11-03 Huawei Proprietary and Confidential 10

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

The format of a measurement result file is as follows:

A20100830.1400+0800-1430+0800_EMS-NORMAL.mrf.bz2
"20100830" indicates year, month, and date. "1400+0800-1430+0800" indicates the recording
starts from 14:00 to 14:30. Onsite engineers can send the logs collected during a specific
period of time to the staff of the R&D Department.
Method 2: COL LOG: LOGTYPE=PFM_RESULT-1;
Fill in the start time and end time.
The measurement data is stored in the \bam\version_x\ftp\COLLOGINFO\PFM-LOG\PFM-
LOG.zip
Version_x is the current working area. Get the result by LST OMUAREA command to check
whether the current working area is Version_a or Version_b.
You can go to the preceding directory through FTP to obtain the corresponding measurement
result file.

1.9.3 KPI Data

1. EXP UKPI:;
2. Get the result at the directory below:
/bam/version_x/ftp/kpi_file/
Version_x is the current working area, get the result by LST OMUAREA command to check
whether the current working area is Version_a or Version_b.

1.9.4 Subsystem Performance Data

1. Get the result at the directory below:
/bam/common/fam/pfm/
2. The format of subsystem performance data is as follows:
MeasRslt_0_0_0_201105111805_05.hmr
The value 0_0_0 indicates subrack/slot/subsystem, the value 20110511 indicates
year/month/date, and the value 1805 indicates the record period between 18:00 and 18:05.

1.10 WebLMT Data Collection

BSC/RNC Version: Recording the specific version of the BSC6900 whose WebLMT runs
improperly.
Detailed Description: Recording the operation procedure in details, with following two items
included:
 The function used, for example, which MML commands are executed
 The Internet explorer version, such as Internet Explorer 6, Internet Explorer 7, Internet
Explorer 8, or Firefox 3.X.X.

2023-11-03 Huawei Proprietary and Confidential 11

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

Screen Shot or Video of the Fault: Providing the fault description in full-screen shots. It is
highly recommended that technical personnel record the fault in video using the following
tool: Unzip the file, and run Screen2Exe.exe.

Time: Recording the local time when the fault occurs. It is highly recommended that technical
personnel record the specific time when the fault is detected and how long it lasts.
Recurring Fault or Not: If this fault will not recur, collect all the following information.
Abnormal PC environment info: Record the info using the following tool: Unzip the file, and
run start.bat, feedback the screen shot of the check result.

2023-11-03 Huawei Proprietary and Confidential 12

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

Host Boards Logs on the Web LMT: Retrieve this log from C:\Web LMT\trace\tracefile
(Close all the WebLMT windows before copy or compress the directory to avoid the file
access conflict.)
OMU Log on the Web LMT: Retrieve all the files named WebLMT such as weblmt.out and
weblmt.log from the OMU directory mbsc\bam\version_a\log or mbsc\bam\version_Y\log.
Run the LST OMUAREA command to check whether the current working area is Version_a
or Version_b and fill out the blue part according to the queried result.

1.11 IU Interface Trace

1.11.1 IU Interface SCTP Trace
1. Get the SCTPLNK control subsystem: DSP SCTPLNK.

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace.

2023-11-03 Huawei Proprietary and Confidential 13

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. only choice the correct control subsystem of SCTP (setp1 result), and Trace Type is selected
SCTP.

4. Fill in correct the SCTP link number, SCTP Message reserve the default list and add to select
the "flowstat" "flowtrace".

5. Then click Submit to start the trace.

1.11.2 IU Interface M3UA Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 14

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Trace Type is selected M3UA, Active CPUS Subsystem reserve Select ALL

3. Fill in the correct M3UA link set index and link ID (fault link info from Alarm log or from
the configuration of fault node)

2023-11-03 Huawei Proprietary and Confidential 15

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Then click Submit to start the trace

1.11.3 IU Interface SCTPLNK and M3UA Combined Trace

1. Get the SCTPLNK control subsystem: DSP SCTPLNK.

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace.

2023-11-03 Huawei Proprietary and Confidential 16

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. only choice the correct control subsystem of SCTP (setp1 result), and Trace Type is selected
SCTP and M3UA.

4. Fill in correct the SCTP link number, SCTP Message reserve the default list and add to select
the "flowstat" "flowtrace".

2023-11-03 Huawei Proprietary and Confidential 17

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Fill in the correct M3UA link set index and link ID (fault link info from Alarm log or from
the configuration of fault node)

6. Then click Submit to start the trace

2023-11-03 Huawei Proprietary and Confidential 18

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.11.4 IU Interface SAAL Trace

1. Get the SAALLNK control subsystem: DSP SAALLNK

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

3. only choice the correct control subsystem of SAAL LNK (setp1 result), and Trace Type is
selected SAAL:

2023-11-03 Huawei Proprietary and Confidential 19

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Fill in correct the SAAL link number, Trace Object reserve the default list and add to select
the "flowstat" "flowtrace".

5. Then click Submit to start the trace.

1.11.5 IU Interface MTP3 Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 20

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Trace Type is selected MTP3, Active CPUS Subsystem reserve Select ALL

3. Fill in the correct MTP3 link set index and link ID (fault link info from Alarm log or from the
configuration of fault node)

2023-11-03 Huawei Proprietary and Confidential 21

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Then click Submit to start the trace.

1.11.6 IU Interface SAALNK and MTP3LNK Combined Trace

1. Get the SAALLNK control subsystem: DSP SAALLNK

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 22

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. only choice the correct control subsystem of SAAL LNK(setp1 result), and Trace Type is
selected SAAL and MTP3

4. Fill in correct the SAAL link number, Trace Object reserve the default list and add to select
the "flowstat" "flowtrace".

2023-11-03 Huawei Proprietary and Confidential 23

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Fill in the correct MTP3 link set index and link ID (fault link info from Alarm log or from the
configuration of fault node)

6. Then click Submit to start the trace

1.11.7 IU Interface QAAL2 Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 24

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Trace Type is selected QAAL2, Active CPUS Subsystem reserve Select ALL

3. Select trace QAAL2 according to ANI or DPC, fill in the correct ADJNODE ID or DPC
Index (from Alarm log or from the configuration of fault node)

2023-11-03 Huawei Proprietary and Confidential 25

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Then click Submit to start the trace.

1.11.8 IU Interface SCCP Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2. DPC Trace Type is selected Specified DPC, fill in the correct DPC; Trace Type is selected
SCCP; Active CPUS Subsystem reserve Select ALL

2023-11-03 Huawei Proprietary and Confidential 26

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. Then click Submit to start the trace.

1.12 IUR Interface Trace

1.12.1 IUR Interface SCTP Trace
1. Get the SCTPLNK control subsystem: DSP SCTPLNK.

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace.

2023-11-03 Huawei Proprietary and Confidential 27

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. only choice the correct control subsystem of SCTP (setp1 result), and Trace Type is selected
SCTP.

4. Fill in correct the SCTP link number, SCTP Message reserve the default list and add to select
the "flowstat" "flowtrace".

2023-11-03 Huawei Proprietary and Confidential 28

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Then click Submit to start the trace.

1.12.2 IUR Interface M3UA Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2. Trace Type is selected M3UA; Active CPUS Subsystem reserve Select ALL

2023-11-03 Huawei Proprietary and Confidential 29

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. Fill in the correct M3UA link set index and link ID (fault link info from Alarm log or from
the configuration of fault node)

4. Then click Submit to start the trace

1.12.3 IUR Interface SCTPLNK and M3UA Combined Trace

1. Get the SCTPLNK control subsystem: DSP SCTPLNK.

2023-11-03 Huawei Proprietary and Confidential 30

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace.

3. only choice the correct control subsystem of SCTP (setp1 result), and Trace Type is selected
SCTP and M3UA

2023-11-03 Huawei Proprietary and Confidential 31

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Fill in correct the SCTP link number, SCTP Message reserve the default list and add to select
the "flowstat" "flowtrace".

5. Fill in the correct M3UA link set index and link ID (fault link info from Alarm log or from
the configuration of fault node)

2023-11-03 Huawei Proprietary and Confidential 32

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

6. Then click Submit to start the trace

1.12.4 IUR Interface SAAL Trace

1. Get the SAALLNK control subsystem: DSP SAALLNK

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 33

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. only choice the correct control subsystem of SAAL LNK(setp1 result), and Trace Type is
selected SAAL:

4. Fill in correct the SAAL link number, Trace Object reserve the default list and add to select
the "flowstat" "flowtrace".

2023-11-03 Huawei Proprietary and Confidential 34

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Then click Submit to start the trace.

1.12.5 IUR Interface MTP3 Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2. Trace Type is selected MTP3, Active CPUS Subsystem reserve Select ALL

2023-11-03 Huawei Proprietary and Confidential 35

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. Fill in the correct MTP3 link set index and link ID (fault link info from Alarm log or from the
configuration of fault node)

4. Then click Submit to start the trace.

1.12.6 IUR Interface SAAL and MTP3LNK Combined Trace

1. Get the SAALLNK control subsystem: DSP SAALLNK

2023-11-03 Huawei Proprietary and Confidential 36

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

3. only choice the correct control subsystem of SAAL LNK(setp1 result), and Trace Type is
selected SAAL and MTP3

2023-11-03 Huawei Proprietary and Confidential 37

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Fill in correct the SAAL link number, Trace Object reserve the default list and add to select
the "flowstat" "flowtrace".

5. Fill in the correct MTP3 link set index and link ID (fault link info from Alarm log or from the
configuration of fault node)

2023-11-03 Huawei Proprietary and Confidential 38

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

6. Then click Submit to start the trace.

1.12.7 IUR Interface QAAL2 Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2. Trace Type is selected QAAL2, Active CPUS Subsystem reserve Select ALL

2023-11-03 Huawei Proprietary and Confidential 39

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. Select trace QAAL2 according to ANI or DPC, fill in the correct ADJNODE ID or DPC
Index (from Alarm log or from the configuration of fault node)

4. Then click Submit to start the trace.

1.12.8 IUR Interface SCCP Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 40

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. DPC Trace Type is selected Specified DPC, fill in the correct DPC; Trace Type is selected
SCCP; Active CPUS Subsystem reserve Select ALL

3. Then click Submit to start the trace.

2023-11-03 Huawei Proprietary and Confidential 41

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.13 IUB Interface Trace

1.13.1 IUB Interface SCTP Trace
1. Get the SCTPLNK control subsystem: DSP SCTPLNK.

2. Open the WEBLMT > TRACE > UMTS Services > IUB Interface Trace.

3. only choice the correct control subsystem of SCTP (setp1 result), and Trace Type is selected
SCTP.

2023-11-03 Huawei Proprietary and Confidential 42

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Fill in correct the SCTP link number, SCTP Message reserve the default list and add to select
the "flowstat" "flowtrace".

5. Then click Submit to start the trace.

1.13.2 IUB Interface SAAL Trace

1. Get the SAALLNK control subsystem: DSP SAALLNK

2023-11-03 Huawei Proprietary and Confidential 43

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Open the WEBLMT > TRACE > UMTS Services > IUB Interface Trace

3. only choice the correct control subsystem of SAAL LNK (setp1 result), and Trace Type is
selected SAAL:

2023-11-03 Huawei Proprietary and Confidential 44

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

The trace file name can be modified, for example, when we trace SAAL, we can add SAAL
link number to the file name.
4. Fill in correct the SAAL link number, Trace Object reserve the default list and add to select
the "flowstat" "flowtrace".

5. Then click Submit to start the trace.

1.13.3 IUB Interface QAAL2 Trace

1. Open the WEBLMT > TRACE > UMTS Services > IU Interface Trace

2023-11-03 Huawei Proprietary and Confidential 45

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2. Trace Type is selected QAAL2, Active CPUS Subsystem reserve Select ALL

3. QAAL2 Trace Type is selected Specified NodeB; fill in the correct NODEB ID (from Alarm
log or from the configuration of fault node)

2023-11-03 Huawei Proprietary and Confidential 46

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Then click Submit to start the trace.

1.14 Transparent Message

1.14.1 Summary
Transparent messages refer to the information queried by running serial commands reserved
during product development, used for further locating the causes of problems that cannot be
solved through common logs. As a supplement to common logs, transparent messages can be
sent only after the R&D engineers demand for information collection and issue explicit
commands.

Transparent messages vary, depending on the version and scenario. Without permission, the onsite
engineers must not send transparent messages. Incorrect transparent messages may cause serious faults,
such as board resetting.
This document provides the operation procedure for sending transparent messages but spares the
description of transparent messages for each specific scenario.

1.14.2 Procedure
Prerequisite: You have successfully logged in to the Web LMT client.
1. Close the Device Maintenance tab.
2. Enable the internal adjusting mode. Setting Method refer to the hyperlink Internal Trace
Setting.
3. Click Device Maintenance and then click Test in the folded options.

2023-11-03 Huawei Proprietary and Confidential 47

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If there is not Test Tab, please go back to last step, Internal Trace Setting.

4. Select Send Transparent Message.

Specify the Subrack No., Slot No., and Subsystem No..

Enter a binary command in the Input Contents window.

The binary command must undergo strict review by the R&D engineers. Incorrect input may result in
serious negative impact.

5. View and save the execution result in the Text File window.

2023-11-03 Huawei Proprietary and Confidential 48

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.15 RNC CDT Collection Method

1.15.1 Summary
When the cause of a problem cannot be located through standard signaling tracing, call data
tracing (CDT) becomes the most effective location means. Using CDT, you can view the
abnormality information and key information of the service process for analyzing the direct
cause of the problem. You can also trace the information reported from the user plane, even
data packets from the user plane, which facilitates the location of user plane problems such as
voice quality and data transmission problem.

1.15.2 RNC CDT Trace Method (Debug + L2 Statistics)

1. By default, the CDT trace function cannot trace or record L2 statistics. In this case, you need
to set the function of internal trace. For details, see Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

2023-11-03 Huawei Proprietary and Confidential 49

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Open the UE Trace and select the Debug Mode check box.

4. Trace the CDT log with L2 statistics.

a. V911

2023-11-03 Huawei Proprietary and Confidential 50

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

b. V912

2023-11-03 Huawei Proprietary and Confidential 51

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

c. V913

5. Collect CDT data.

After CDT trace is created, the CDT data is automatically saved to the specified path if
configured. In this case, you can directly get the CDT data under the path.

If the path for saving CDT data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

2023-11-03 Huawei Proprietary and Confidential 52

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

6. Browse the file offline.

Use the service data trace tool of the LMT offline tool (delivered along with the product) to
open a trace file.
After the installation is complete, you need to modify the file on the local PC.
Installation directory: \HW LMT\adaptor\clientadaptor\BSC6900\V900R012C01SPH202\
style\defaultstyle\locale\en_US\rnctest
The RncTestConfig.xml file is available in the directory.
Find the RncTestConfig.xml file and open it by using UltraEdit or Notepad. Then, search for
the keyword CDT and replace all 0s with 1s.

1.15.3 RNC CDT Trace Method (Debug + Internal Printed

Information)
1. By default, the CDT trace function cannot trace or record the internal printed information. In
this case, you need to set the function of internal trace. For details, see Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

2023-11-03 Huawei Proprietary and Confidential 53

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Open the UE Trace and select the Debug Mode check box. In this way, you can trace the
internal printed information.

4. Collect CDT data.

After CDT trace is created, the CDT data is automatically saved to the specified path if
configured. In this case, you can directly get the CDT data under the path.

If the path for saving CDT data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

2023-11-03 Huawei Proprietary and Confidential 54

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Browse the file offline.

Use the service data trace tool of the LMT offline tool (delivered along with the product) to
open a trace file.
After the installation is complete, you need to modify the file on the local PC.
Installation directory: \HW LMT\adaptor\clientadaptor\BSC6900\V900R012C01SPH202\
style\defaultstyle\locale\en_US\rnctest
The RncTestConfig.xml file is available in the directory.
Find the RncTestConfig.xml file and open it by using UltraEdit or Notepad. Then, search for
the keyword CDT and replace all 0s with 1s.

1.15.4 RNC CDT Trace Method (Debug + L2 Statistics + Internal

Printed Information + SRB Datagram Report)
1. By default, the CDT trace function cannot trace or record the L2 information and the internal
printed information. In this case, you need to set the function of internal trace. For details, see
Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

2023-11-03 Huawei Proprietary and Confidential 55

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Open the UE Trace and select the Debug Mode check box.

4. Set the parameters related to L2 statistics and SRB datagram report.

a. V911

2023-11-03 Huawei Proprietary and Confidential 56

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

b. V912

c. V913

2023-11-03 Huawei Proprietary and Confidential 57

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Collect CDT data.

After CDT trace is created, the CDT data is automatically saved to the specified path if
configured. In this case, you can directly get the CDT data under the path.

If the path for saving CDT data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

6. Browse the file offline.

Use the service data trace tool of the LMT offline tool (delivered along with the product) to
open a trace file.
After the installation is complete, you need to modify the file on the local PC.

2023-11-03 Huawei Proprietary and Confidential 58

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

Installation directory: \HW LMT\adaptor\clientadaptor\BSC6900\V900R012C01SPH202\

style\defaultstyle\locale\en_US\rnctest
The RncTestConfig.xml file is available in the directory.
Find the RncTestConfig.xml file and open it by using UltraEdit or Notepad. Then, search for
the keyword CDT and replace all 0s with 1s.

1.15.5 RNC CDT Trace Method (Debug + L2 Statistics + Internal

Printed Information + SRB Datagram Report + TRB Datagram
Report)
1. By default, the CDT trace function cannot trace or record the L2 information and the internal
printed information. In this case, you need to set the function of internal trace. For details, see
Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

2023-11-03 Huawei Proprietary and Confidential 59

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Open the UE Trace and select the Debug Mode check box.

4. Set the parameters related to L2 statistics, SRB datagram report, and TRB datagram report.
a. V911

2023-11-03 Huawei Proprietary and Confidential 60

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

b. V912

c. V913

2023-11-03 Huawei Proprietary and Confidential 61

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Collect CDT data.

After CDT trace is created, the CDT data is automatically saved to the specified path if
configured. In this case, you can directly get the CDT data under the path.

If the path for saving CDT data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

6. Browse the file offline.

Use the service data trace tool of the LMT offline tool (delivered along with the product) to
open a trace file.
After the installation is complete, you need to modify the file on the local PC.
Installation directory: \HW LMT\adaptor\clientadaptor\BSC6900\V900R012C01SPH202\
style\defaultstyle\locale\en_US\rnctest
The RncTestConfig.xml file is available in the directory.
Find the RncTestConfig.xml file and open it by using UltraEdit or Notepad. Then, search for
the keyword CDT and replace all 0s with 1s.

2023-11-03 Huawei Proprietary and Confidential 62

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.15.6 RNC CDT Trace Method (Debug)

1. Open the UE Trace and select the Debug Mode check box. In this way, you can trace the
inter-module information.

2. Collect CDT data.

After CDT trace is created, the CDT data is automatically saved to the specified path if
configured. In this case, you can directly get the CDT data under the path.

If the path for saving CDT data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

3. Browse the file offline.

Use the service data trace tool of the LMT offline tool (delivered along with the product) to
open a trace file.
After the installation is complete, you need to modify the file on the local PC.
Installation directory: \HW LMT\adaptor\clientadaptor\BSC6900\V900R012C01SPH202\
style\defaultstyle\locale\en_US\rnctest

2023-11-03 Huawei Proprietary and Confidential 63

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

The RncTestConfig.xml file is available in the directory.

Find the RncTestConfig.xml file and open it by using UltraEdit or Notepad. Then, search for
the keyword CDT and replace all 0s with 1s.

1.16 IOS Signaling Trace Method

1.16.1 Summary
With the IOS trace feature, you can trace multiple UEs in multiple cells. It is effective in
solving KPI problems or problems of tremendous negative impact.
Up to 32 cells can be traced simultaneously, and only 12 normal IOS traces or 6 DEBUG
mode IOS traces can be launched simultaneously.
To avoid flow-control, you are advised not to enable L2 trace in DEBUG mode IOS traces.

In the DRD scenario, when tracing the IOS of cell F2, you need also to set cell F1.

1.16.2 IOS Signaling Trace Method (Debug + L2 Statistics)

1. By default, the IOS trace function cannot trace or record L2 statistics. In this case, you need to
set the function of internal trace. For details, see Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

2023-11-03 Huawei Proprietary and Confidential 64

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Enable the trace function in IOS debug mode.

Choose Trace > UMTS Service on the navigation tree. Then, double-click the IOS Trace
node.
In the dialog box that is displayed, set the parameters such as Call Count and Cell ID.
Set the Call Count parameter according to the actual condition. In the debug mode, the
maximum value is 6, which is also the recommended value. In the Cell ID text box, enter the
ID of a faulty cell. You can enter the IDs of multiple cells. Use the default values for other
parameters.

2023-11-03 Huawei Proprietary and Confidential 65

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Set the parameters related to L2 statistics.

a. V911

b. V912

c. V913

2023-11-03 Huawei Proprietary and Confidential 66

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

5. Collect IOS data.

After IOS trace is created, the IOS data is automatically saved to the specified path if
configured. In this case, you can directly get the IOS data under the path.

If the path for saving IOS data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

1.16.3 IOS Signaling Trace Method (Debug + Internal Printed

Information)
1. By default, the IOS trace function cannot trace or record the internal printed information. In
this case, you need to set the function of internal trace. For details, see Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

2023-11-03 Huawei Proprietary and Confidential 67

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Enable the trace function in IOS debug mode.

Choose Trace > UMTS Service on the navigation tree. Then, double-click the IOS Trace
node.
In the dialog box that is displayed, set the parameters such as Call Count and Cell ID.
Set the Call Count parameter according to the actual condition. In the debug mode, the
maximum value is 6, which is also the recommended value. In the Cell ID text box, enter the
ID of a faulty cell. You can enter the IDs of multiple cells. Use the default values for other
parameters.

4. Collect IOS data.

After IOS trace is created, the IOS data is automatically saved to the specified path if
configured. In this case, you can directly get the IOS data under the path.

If the path for saving IOS data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

2023-11-03 Huawei Proprietary and Confidential 68

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.16.4 IOS Signaling Trace Method (Debug + L2 Statistics +

Internal Printed Information + SRB Datagram Report)
1. By default, the IOS trace function cannot trace or record the L2 information and the internal
printed information. In this case, you need to set the function of internal trace. For details, see
Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Enable the trace function in IOS debug mode.

Choose Trace > UMTS Service on the navigation tree. Then, double-click the IOS Trace
node.
In the dialog box that is displayed, set the parameters such as Call Count and Cell ID.
Set the Call Count parameter according to the actual condition. In the debug mode, the
maximum value is 6, which is also the recommended value. In the Cell ID text box, enter the
ID of a faulty cell. You can enter the IDs of multiple cells. Use the default values for other
parameters.

2023-11-03 Huawei Proprietary and Confidential 69

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Set the parameters related to L2 statistics and SRB datagram report.

a. V911

b. V912

2023-11-03 Huawei Proprietary and Confidential 70

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

c. V913

5. Collect IOS data.

After IOS trace is created, the IOS data is automatically saved to the specified path if
configured. In this case, you can directly get the IOS data under the path.

If the path for saving IOS data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

2023-11-03 Huawei Proprietary and Confidential 71

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.16.5 IOS Signaling Trace Method (Debug + L2 Statistics +

Internal Printed Information + SRB Datagram Report + TRB
Datagram Report)
1. By default, the IOS trace function cannot trace or record the L2 information and the internal
printed information. In this case, you need to set the function of internal trace. For details, see
Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Enable the trace function in IOS debug mode.

Choose Trace > UMTS Service on the navigation tree. Then, double-click the IOS Trace
node.
In the dialog box that is displayed, set the parameters such as Call Count and Cell ID.
Set the Call Count parameter according to the actual condition. In the debug mode, the
maximum value is 6, which is also the recommended value. In the Cell ID text box, enter the
ID of a faulty cell. You can enter the IDs of multiple cells. Use the default values for other
parameters.

2023-11-03 Huawei Proprietary and Confidential 72

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Set the parameters related to L2 statistics, SRB datagram report, and TRB datagram report.
a. V911

b. V912

2023-11-03 Huawei Proprietary and Confidential 73

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

c. V913

5. Collect IOS data.

After IOS trace is created, the IOS data is automatically saved to the specified path if
configured. In this case, you can directly get the IOS data under the path.

2023-11-03 Huawei Proprietary and Confidential 74

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

If the path for saving IOS data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

1.16.6 IOS Signaling Trace Method (Default Method)

1. Enable the IOS trace function.
Choose Trace > UMTS Service on the navigation tree. Then, double-click the IOS Trace
node.
In the dialog box that is displayed, set the parameters such as Call Count and Cell ID.
Set the Call Count parameter according to the actual condition. The maximum value is 30
and the recommended value is 10. In the Cell ID text box, enter the ID of a faulty cell. You
can enter the IDs of multiple cells. Use the default values for other parameters.

2. Collect IOS data.

After IOS trace is created, the IOS data is automatically saved to the specified path if
configured. In this case, you can directly get the IOS data under the path.

If the path for saving IOS data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

2023-11-03 Huawei Proprietary and Confidential 75

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.17 Cell Trace

1.17.1 Summary
The cell trace function can trace all the interacted messages of the cell. It takes effect in
locating the problems related to creation of common channels and call drop in common
channels.

1.17.2 Cell Trace Method (Debug + L2 Datagram Report)

1. By default, the Cell trace function cannot trace or record L2 data. In this case, you need to set
the function of internal trace. For details, see Internal Trace Setting.
2. Set internal trace parameters.

This step is applicable only to V912 or a later version.

If the Message Setting option is not available, you have to re-set the function of internal trace.

3. Enable the trace function in cell debug mode.

2023-11-03 Huawei Proprietary and Confidential 76

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

4. Set the parameters related to L2 statistics.

a. Run the LST USCCPCH: CellId=XX command to get the number of SCCPCH
channels configured for the cell and the SCCPCH ID. In the case of one SCCPCH
channel, set SCCPCH1. In the case of two SCCPCH channels, set SCCPCH1 and
SCCPCH2.

b. It is recommended that you set Report Period to 20.

c. The trace setting page is shown in the following figure.
 V911 and V912

2023-11-03 Huawei Proprietary and Confidential 77

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

 V913

5. Collect Cell trace data.

After Cell trace is created, the cell data is automatically saved to the specified path if
configured. In this case, you can directly get the cell data under the path.

If the path for saving cell data has not been changed, the default path is as follows:
C:\Web LMT\output\MBSC\trace\tmfFile

2023-11-03 Huawei Proprietary and Confidential 78

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.18 Timing Trace Task

1.18.1 Summary
When Trace Mode is set to Save to OMU, you can set the start time and end time of the trace
task. After the setting is applied successfully, the trace task can trace specified messages.
Size of OMU space: The size of OMU space reserved for the trace task is 500 MB. If this size
is exceeded, the system deletes the earliest data.

1.18.2 Procedure
The following section takes tracing of IOS messages as an example.
1. Set a timing trace task and apply the settings to create it.

2. The path that saves trace files is as follows:

\bam\common\fam\trace

3. Manage trace tasks including querying, deleting, stopping, and resuming a task.

2023-11-03 Huawei Proprietary and Confidential 79

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

2023-11-03 Huawei Proprietary and Confidential 80

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

1.19 Appendix 1 OMU Logs Specifications

Knowing the structure of OMU application files helps technical personnel in maintaining
OMU, locating faults, collecting information, and raising the efficiency of troubleshooting.
Therefore, the following file is provided for your reference.

1.20 Internal Trace Setting

Introduction:
Recommend use when it is necessary. It is switch of whether to monitor the detail running
information. There are two methods to switch on the function.
Setting Method 1:
Modification at client side, only available in this time of the WebLMT access. It is easy to
operate. (Note: This method is first used in V911 and is applicable to a version later than
RAN12SPC200 for CDT trace.)

Setting Method 2:
Modification the file at OMU side, available for all visitors. Have to recover the setting when
unnecessary. It is complicated to operate. (This method is applicable to all versions.)
Setting Method 1
Condition: Log in the WebLMT successfully
1. Close the Device Maintenance, Trace and Monitor.
2. Open the internal debug mode.
Method:
Open About page. Click LOGO first, then click the word by following the sequence 3-1-4-2
below, and finally click the logo.

2023-11-03 Huawei Proprietary and Confidential 81

Copyright © Huawei Technologies Co.,
Ltd
BSC6900 Log Operation and Collection Methods INTERNAL

3. Internal trace setting

Setting in the related page. Detail in the text.
Setting Method 2:
According to the attach file.

2023-11-03 Huawei Proprietary and Confidential 82

Copyright © Huawei Technologies Co.,
Ltd