RAN Feature Description Table of Contents

Table of Contents28-1Chapter 28 Tracing Function

28-128.1 Introduction

28-128.1.1 Definition

28-128.1.2 Purposes

28-128.1.3 Terms

28-228.1.4 Abbreviations

28-328.2 Availability

28-328.2.1 Network Elements Involved

28-328.2.2 Software Releases

28-428.3 Impact

28-428.3.1 On System Performance

28-428.3.2 On Other Features

28-428.4 Technical Description

28-428.4.1 Overview of the Tracing Function

28-428.4.2 Control Modules

28-528.4.3 SPU

28-628.4.4 Working Principle of the Message Tracing

28-728.4.5 Authority for Tracing

28-728.4.6 Overview of the Tracing Management Function

28-828.4.7 Message Tracing over Standard Interfaces

28-928.4.8 Message Tracing of Transport Network Layer

28-1028.4.9 Call Tracing

28-1128.4.10 Cell Tracing

28-1128.4.11 OS Tracing

28-1128.4.12 Redirect Tracing

28-1228.4.13 CDT Tracing

28-1228.4.14 Location Tracing

28-1328.5 Capabilities

28-1328.6 Implementation

28-1328.6.1 Routine Operations of the Tracing Function

28-1328.6.2 Creating Trace Tasks

28-1628.6.3 Browsing Traced Messages Online

28-1728.6.4 Saving Tracing Results

28-1928.6.5 Stopping/Restarting Trace Tasks

28-2028.6.6 Closing Trace Tasks

28-2028.6.7 Browsing Traced Messages Offline

28-2328.6.8 Alarms

28-2328.6.9 Counters

28-2328.7 References

List of Figures28-5Figure 28-1 Diagram of message tracing

28-6Figure 28-2 Working principle of the message tracing

28-14Figure 28-3 Choosing a tracing object

28-15Figure 28-4 MTP3B Protocol Tracing dialog box

28-16Figure 28-5 Message browse window

28-17Figure 28-6 Message Browser dialog box

28-19Figure 28-7 Save dialog box

28-21Figure 28-8 Opening a file containing traced messages

28-22Figure 28-9 Displaying traced messages

List of Tables28-3Table 28-1 NEs required for the tracing function

28-3Table 28-2 RAN product and related version

28-8Table 28-3 Message tracing over standard interfaces

28-9Table 28-4 Message tracing of transport network layer

28-10Table 28-5 Call tracing

28-11Table 28-6 Cell tracing

28-11Table 28-7 OS tracing

28-11Table 28-8 Redirect tracing

28-12Table 28-9 CDT tracing

28-12Table 28-10 Location tracing

Chapter 28 Tracing Function28.1 Introduction28.1.1 DefinitionThe interface tracing function in a mobile telecommunications system is of key importance for the Operation and Maintenance (O&M). An operator who is familiar with the system procedures can verify the data and troubleshoot the problems through checking the interface messages traced by the BSC6800.The BSC6800 provides the following types of interface tracing: Message Tracing over Standard Interfaces Message Tracing of Transport Network Layer Call Tracing Cell Tracing OS Tracing Redirect Tracing CDT Tracing Location Tracing28.1.2 PurposesYou can quickly verify the data and troubleshoot a fault by checking the messages on different interfaces.

28.1.3 TermsTermDescription

UE tracingThe UE tracing consists of the following two types: UE tracing (on the user plane and the signaling plane)

This task is performed to trace the call-related information of a specified UE on the signaling plane and on the user plane during a call XE "UE Tracing (Signaling Plane and User Plane):tracing"

XE "tracing:UE Tracing (Signaling Plane and User Plane)" .

UE tracing (standard interface)

This task is performed to trace signaling messages of a specified UE over Iu, Iur, Iub, and Uu interfaces during a call.

IOS tracingThis task is performed to trace a specified number of calls which XE "tracing:IOS"

XE "IOS:tracing" access a specified cell continuously. The number of calls can be defined when the task is started.The number of calls can be set when the task is started.

The messages during the call procedure are traced.

Cell tracingThe cell tracing is used to measure the following two types of messages:

Common signaling messages on the Iub interface of one or more specified cells Customized messages that contain information about UEs in the cells

CDT tracingThe CDT tracing (detailed call tracing) is used to trace the following messages:

Standard interface messages of the UE Messages on the user plane and signaling plane of the UE

OS tracingOS tracing is used to trace the messages inside the Operating System (OS).

Redirect tracingRedirect tracing is used to trace the print information of the serial ports on the board subsystem.

OM-DBGOM-DBG is an internal module of the SPU. It has the following functions: Receiving tasks sent from the BAM Generating filter tables

Maintaining the task check between the BAM and the SPU Maintaining the message channels between the trace tasks and the LMT Informing the traffic processing module of the change of trace tasks

Providing message channels from the traffic processing module to the BAM or LMT Providing interfaces for reporting data messages of the traffic module

Providing interfaces for flow control

28.1.4 Abbreviations AbbreviationFull Spelling

BAMBack Administration Module

IMEIInternational Mobile Equipment Identity

IMSIInternational Mobile Subscriber Identity

LMTLocal Maintenance Terminal

P-TMSIPacket Temporary Mobile Subscriber Identity

RANRadio Access Network

SAALSignaling ATM Adaptation Layer

SCCPSignaling Connection and Control Part

SPUSignaling process Unit

TMSITemporary Mobile Subscriber Identity

LACLocation Area Code

LANLocal Area Network

RACRouting Area Code

UMTSUniversal Mobile Telecommunications System

28.2 Availability28.2.1 Network Elements InvolvedTable 28-1 describes the Network Element required for the tracing function.Table 28-1 NEs required for the tracing functionUENodeBRNCMSC

ServerMGWSGSNGGSNHLR

Note:

: Not required

: Required

( Note:

This chapter describes only the availability of the NodeB and the RNC.28.2.2 Software ReleasesTable 28-2 describes the version of RAN product that supports the tracing function.Table 28-2 RAN product and related versionProductVersion

RNCBSC6800V100R002 and later releases

28.3 Impact28.3.1 On System PerformanceA message trace task occupies a lot of system resources. Therefore, do not execute this task when the system carries heavy traffic. Ensure that the message tracing window is closed when a message trace task is completed.

To ensure effective use of the system resources, Huawei recommends that you start only one group of tasks in the following three groups: CDT tracing and UE trace (standard interface message) Call tracing and cell tracing

Message tracing over interfaces such as Iub, Iur, Iu, standard protocols such as Q.AAL2, SAAL, SCCP, MTP3-b tracing and realtime status monitoring function28.3.2 On Other Features

None.28.4 Technical Description XE "SRNS relocation:technical description" \i 28.4.1 Overview of the Tracing FunctionThe system that performs the tracing function consists of the following components:

Control modules for message tracing on the OMC side Signaling Processing Unit (SPU) on the RNC sideThis section describes functions, working principles, and process of message tracing performed on the whole system.28.4.2 Control ModulesControl modules consist of the LMT and the BAM, as shown in Figure 28-1.

Figure 28-2 Diagram of message tracingII. LMTThe LMT performs the following functions: Sending the trace task to the BAM Displaying the execution results that are sent from the BAMIII. BAMThe BAM broadcasts the trace task that is send from the LMT to the SPU on the corresponding board. For the non-call trace task, the BAM transparently transmits it to the SPU. For the call trace task, the call trace agent module in the BAM performs centralized management. The call trace agent has the following functions: Receiving the tracing requirements from the LMT Creating, modifying, or terminating a trace task Converting the requirements of the trace task into specified tracing conditions, and then sending them to the SPU Receiving the data report provided by the SPU and reporting it to the LMT or analyzing it28.4.3 SPUThe SPU can be embedded into the mobile services processing unit. The SPU performs the following functions: Receiving the tracing command sent from the control modules Determining the object to be traced

Tracing that object when it is triggered by a standard interface message or a customized message between the modules

Duplicating the traced message and sending it to the control modules

To carry more information, the data sent to the control modules can carry some other basic information such as the arriving time of the message.Tracing of the subscribers by the SPU consists of the following:

Tracing of messages on each standard interface on the RNC Tracing of customized messages between different interfaces on modules of the RNCThe tracing of the subscribers can be further divided into the following: Tracing of messages on a standard interface

Tracing of customized messages between different interfaces on multiple modules Tracing of messages of one type

Tracing of messages of all the types

Tracing of messages on all the interfaces

When a specified event related to the traced message occurs, the SPU copies the message and sends it to the trace agent of the control modules. Then the trace agent performs the following according to the message types: For the standard interface message, the trace agent decodes the message according to the interface type. For the customized message, the trace agent displays the message directly.

28.4.4 Working Principle of the Message Tracing

Figure 28-2 shows the working principles of the message tracing XE "tracing:principle"

XE "principle:tracing" .

Figure 28-3 Working principle of the message tracing

The internal process of the trace task creation is as follows:

2) The operator creates a trace task on the LMT, and the LMT sends a binary command to the BAM server to create the task.3) The BAM server assigns an ID to the task and forwards the command to the debugging module of the specified board.4) After receiving the command, the debugging module records the filter parameters of the tracing data in the filter table and notifies the service module.5) The service module updates the local filter table according to the message from the debugging module.

The internal process of the trace task closure is as follows:

6) The operator closes a trace task on the LMT, and the LMT sends a binary command to the BAM server to delete the task.

7) The BAM server forwards the command to the specified board according to the task number.

8) The debugging and service modules delete the task from the filter table.The internal process for the service module to report traced messages to the LMT is as follows:9) The service module filters the collected messages according to the filter parameters in the local filter table and reports the messages meeting the requirements to the BAM server.10) The BAM server forwards the traced messages to the LMT that creates the task according to the task number.11) The LMT translates the messages and displays them on the interface.28.4.5 Authority for Tracing

The operators at the following levels can execute the trace tasks XE "tracing:authority"

XE "authority:tracing" :

admin USER OPERATOR ADMINISTRATOR CUSTOM entitled to use command group G_1028.4.6 Overview of the Tracing Management Function

This function is used to trace:

Messages over standard interfaces

Messages on signaling links

Internal messages

It is applicable to routine equipment XE "tracing:function"

XE "function:tracing" maintenance, debugging, and fault location.

The BSC6800 provides the following tracings:

Message Tracing over Standard Interfaces Message Tracing of Transport Network Layer Call Tracing Cell Tracing OS Tracing Redirect Tracing CDT Tracing Location Tracing28.4.7 Message Tracing over Standard Interfaces This task is performed to trace messages over the Iu, Iur, Iub, and Uu interfaces XE "tracing:standard interface"

XE "standard interface:tracing" , as listed in Table 28-3.

Table 28-3 Message tracing over standard interfacesTaskFunction

Iu interface tracingThis task is performed to trace signaling messages over the Iu interface, including connection-oriented messages and connectionless messages. You can start the Iu interface XE "tracing:Iu interface"

XE "Iu interface:tracing" tracing in the LMT to monitor the exchange situations of signaling messages over the Iu interface.

You can specify different Destination Point Codes (DPC) or WSPUb subsystems for tracing. For tracing, you can either specify all message types or only the message types concerned.

Iur interface tracingThis task is performed to trace signaling messages over the Iur interface, including connection-oriented messages and connectionless messages. You can start the Iur interface XE "tracing:Iur interface"

XE "Iur interface:tracing" tracing in the LMT to monitor the exchange situations of signaling messages over the Iur interface.You can specify different DPCs or WSPUb subsystems for tracing. For tracing, you can specify either all message types or only the message types concerned.

Iub interface tracingThis task is performed to trace signaling messages over the Iub interface, that is, NodeB Application Part (NBAP) messages.

You can start the Iub interface XE "tracing:Iub interface"

XE "Iub interface:tracing" tracing in the LMT to monitor the exchange situations of signaling messages over the Iub interface.You can specify all NodeBs, or all ports of a NodeB, or one port of a NodeB for tracing. Also, you can trace either the messages processed by one or several WSPUb subsystems, or the messages of one type or of all the types concerned.

Uu interface tracingThis task is performed to trace signaling messages over the Uu interface.

You can start the Uu interface XE "Uu:interface tracing"

XE "tracing:Uu:interface" tracing in the LMT to monitor the exchange situations of signaling messages over the Uu interface.You can specify one or more cells or RNCs for tracing. Also, you can trace all Uu interface message types or only the message types concerned.

( Note:

A maximum of six trace tasks can be performed simultaneously over the lu, lur, lub, and Uu interfaces.

28.4.8 Message Tracing of Transport Network LayerThis task is performed to trace the messages of the following:

Q.ATM Adaptation Layer type 2 (QAAL2) Signaling XE "transport network layer:tracing"

XE "tracing:transport network layer" Connection and Control Part (SCCP) Message Transfer Part level 3 - Broadband (MTP3-B) Signaling ATM Adaptation Layer (SAAL) Stream Control Transmission Protocol (SCTP)For details, refer to Table 28-4. Table 28-4 Message tracing of transport network layerTaskFunction

QAAL2 protocol tracingThis task is performed to trace messages of the QAAL2.It is performed to detect the setup failure or release abnormality of an ATM Adaptation Layer type 2 (AAL2) connection on the user plane. XE "QAAL2:tracing"

XE "tracing:QAAL2" It also helps you judge whether the local or peer end is normal or not by checking whether the ESTABLISH_REQUEST message is sent and by checking the replied messages.

SCCP protocol tracingThis task is performed to trace messages of the SCCP, including connection-oriented messages and connectionless messages.It is performed to locate the problems that lead to the failure of the Iu or Iur connection XE "tracing:SCCP"

XE "SCCP:tracing" setup and the release abnormity.

MTP3-B protocol tracingThis task is performed to trace messages of the MTP3-B, including XE "tracing:MTP3-B"

XE "MTP3-B:tracing" :

MTP3-B upper layer (QAAL2 and SCCP) messages MTP3-B signaling link test messages MTP3-B signaling network management messagesIt is performed to locate the problem that leads to the unavailability of an MTP3B link when the corresponding SAAL link is available. The method is to check the consistency of the Originating signaling Point Code (OPC), DPC, and Signaling Link Selection code (SLS) in the sent and received SLTM messages with the negotiated data.

SAAL protocol tracingThis task is performed to trace messages of the SAAL.It is performed to locate the problem that leads to the unavailability of the SAAL link XE "tracing:SAAL" . XE "SAAL:tracing" If there are only outgoing but no incoming RNC messages, it is an indication that the lower layer link (PVC) or the peer end works abnormally.

SCTP protocol tracingThis task is performed to trace messages of the SCTP.It is performed to locate the problem that leads to the unavailability of the SCTP link XE "tracing:SAAL" .When the NCP or CCP is not functional, you can start the SCTP protocol trace task to query the information of the SCTP link concerned. XE "SAAL:tracing"

28.4.9 Call TracingDuring a call, this task is performed to trace messages of a UE over:

Standard interfaces XE "tracing:call"

XE "call:tracing" Signaling plane User planeIt is also performed to trace multiple calls simultaneously (IOS tracing). For details, refer to Table 28-5.

Table 28-5 Call tracingTaskFunction

UE tracing (standard interface)This task is performed to trace signaling messages of a specified UE over Iu, Iur, Iub, and Uu interfaces during a call.To start a trace task, first specify the identifier of the UE (IMSI, TMSI, P-TMSI, or IMEI).

You can choose one or more interfaces to trace.You can choose Close dedicated measurement report XE "UE (Standard Interface):tracing"

XE "tracing:UE (Standard Interface)" and Close RRC measurement report to mask the dedicated measurement report for the Iub interface and the RRC measurement report for the Uu interface.

UE tracing (signaling plane and user plane)This task is performed to trace the call-related information of a specified UE on the signaling plane and on the user plane during a call XE "UE Tracing (Signaling Plane and User Plane):tracing"

XE "tracing:UE Tracing (Signaling Plane and User Plane)" .

To start a trace task, first specify the identifier of the UE to trace (IMSI, TMSI, P-TMSI, or IMEI), and then choose the events to trace the required signaling plane and user plane information.

IOS tracingThis task is performed to trace a specified number of calls which XE "tracing:IOS"

XE "IOS:tracing" access a specified cell continuously. To be more specific, it is performed to trace the messages generated by the calls.Suppose that the specified number of continuous calls is N. If N calls are already being traced, the system does not trace any newly accessed calls. If the number becomes less than N because of the termination of some calls, the system automatically traces new calls till the number of calls being traced reaches N.You can choose the message types by choosing trace events.

You can also choose one or more cells to trace.

28.4.10 Cell TracingTable 28-6 describes the cell tracing.

Table 28-6 Cell tracing

TaskFunction

Cell tracingThis task is performed to trace NBAP common messages or XE "tracing:cell"

XE "cell:tracing" USER_VOLUME events in one or more specified cells. The USER_VOLUME event includes some customized messages of UE statistical information.You can specify one or more cells to trace.

You can also choose the message types by choosing trace events.A maximum of 32 cells can be traced simultaneously.

28.4.11 OS TracingThis task is performed to trace the internal messages of the Operating System (OS). For details, refer to Table 28-7.

Table 28-7 OS tracing

TaskFunction

OS tracingThis task is performed to trace messages between:

The exchange module of the BAM and the XE "tracing:OS"

XE "OS:tracing" internal modules of the boards in the WRBSs

The internal modules of boards in the WRBSs.

In addition to the messages between different modules, this task can be performed to trace messages sent by and to a module itself.

You can choose the tracing types.

28.4.12 Redirect TracingThis task is performed to trace the COM port printing information of a specified board subsystem. For details, refer to Table 28-8.

Table 28-8 Redirect tracingTaskFunction

Redirect tracingThis task is performed to redirect the COM port XE "tracing:redirect"

XE "redirect:tracing" printing information of a specified subsystem to the message browse window of the LMT.To start a trace task, specify the subrack and slot numbers of the board and the subsystem number.

28.4.13 CDT Tracing

Table 28-9 describes the Call Data Tracing (CDT) tracing.

Table 28-9 CDT tracing

TaskFunction

CDT tracingThis task is performed to trace messages of a UE over standard interfaces, on user plane, and on signaling plane during a call.It helps you monitor the signaling exchange procedures over standard interfaces and the user plane, in addition to the uplink and downlink data during the whole call procedure.To start a CDT, specify the UE to be traced XE "tracing:CDT"

XE "CDT:tracing" .You can also choose the interfaces and message types to trace.A maximum of two CDT trace tasks can be performed simultaneously.

( Note:

The task of UE tracing (standard interface) and the task of CDT tracing cannot be performed simultaneously for the same UE.

A maximum of six CDT and UE tracing (standard interface) tasks can be performed simultaneously for different UEs. Among the six tasks, at most two CDT trace tasks can be performed simultaneously.

A maximum of 15 IOS and UE tracing (signaling plane and user plane) tasks can be performed simultaneously. Among the 15 tasks, at most 8 IOS or UE tracing (signaling plane and user plane) tasks can be performed simultaneously.

28.4.14 Location Tracing XE "tracing:location"

XE "location:tracing" Table 28-10 describes the location tracing.

Table 28-10 Location tracingTaskFunction

Location TracingThis task is performed to trace the results of a location tracing initiated by the CN. This task can also simulate the CN to initiate a location tracing and trace the results.Based on different settings, this task can simulate location tracing for different situations.

28.5 CapabilitiesNone.28.6 Implementation XE "SRNS relocation:implementation" \i 28.6.1 Routine Operations of the Tracing Function This section describes the following:

Creating Trace Tasks Browsing Traced Messages Online Saving Tracing Results Stopping/Restarting Trace Tasks Closing Trace Tasks Browsing Traced Messages Offline28.6.2 Creating Trace TasksI. Task DescriptionThis task is performed to create a trace task. After a task is created, the system begins tracing messages. The results are displayed in the message browse window in real time.

( Note:

The trace task occupies a lot of resources. Therefore, execute the task when the system is not busy.II. Prerequisites

There are two prerequisites:

The LMT is started.

You have logged in to the BSC6800 system with an account authorized for the tracing management.III. Operation Procedure

Take creating the task of tracing messages of MTP3-B as an example. The procedure is as follows:1) Click the Maintenance tab on the Local Maintenance Terminal window.

2) Unfold the Trace Management node, and then unfold the Interface Trace Task node.The tracing objects are displayed, as shown in Figure 28-3.

Figure 28-4 Choosing a tracing object

( Note:

For the location tracing, unfold the Trace Management node, and then unfold the Location Trace node. Choose Location Reporting Control.3) Double-click the tracing object MTP3B.The MTP3B Protocol Tracing dialog box as shown in Figure 28-4 opens up for parameter setting.

Figure 28-5 MTP3B Protocol Tracing dialog box

( Note:

If the Autosave to File checkbox is selected, the system saves the tracing results in the .tmf format. For details, refer to 28.6.4 "Saving Tracing Results."

4) Set the parameters in the dialog box.

5) Click OK to start the trace task. The system displays traced signaling messages in the message browse window in real time, as shown in Figure 28-5.

Figure 28-6 Message browse window28.6.3 Browsing Traced Messages OnlineI. Task DescriptionThis task is performed to browse or query the traced messages in the message browse window after the trace task is created XE "tracing:online browse"

XE "online browsing:traced message"

XE "tracing:browse online"

XE "browsing online:traced message" .

II. Prerequisites

There are two prerequisites:

A trace task is started.

Traced messages are reported.III. Operation Procedure

1) Browse or query the traced messages in the message browse window.

( Note:

You can right-click the message browse window, and perform the following operations:

Choose Stop Trace Task to stop the task.

Choose Restart Trace Task to restart the task.

Choose Auto Scroll, and the messages in the window are automatically refreshed in real time and are scrolled upward.

Choose Clear Messages to remove all messages in the window.

Choose Close All xxx Message Trace Tasks (xxx stands for specific trace tasks) to close the trace tasks.

Choose Property to query the task properties.

2) To learn about the details of a message, double-click it.The Message Browser dialog box as shown in Figure 28-6 opens up, displaying the details of the message.

Figure 28-7 Message Browser dialog box

28.6.4 Saving Tracing ResultsThere are two ways of saving tracing results: auto saving and manual saving XE "saving:tracing result"

XE "tracing result:saving" .

I. Task DescriptionThis task is performed to save the traced messages in the LMT.

II. Prerequisites

There are two prerequisites:

A trace task is started.

Traced messages are reported.III. Automatically Saving Traced MessagesWhen a trace task is created, the default setting is to save all messages displayed in the message browse window in the .tmf format.

The default saving path is \client\output\main\BSC6800\\trace.( Note:

The system saves every 5,000 messages in a file. From message 5,001, a serial number is added in the file name. For example, MTP3-B messages 5,001 to 10,000 are saved in a file with the name of office name_MTP3B_yy-mm-dd_hh-mm-ss_1.tmf.

You can use the Trace Viewer to browse offline the messages saved in the .tmf format. For detail, refer to 28.6.7 "Browsing Traced Messages Offline."

IV. Manually Saving Traced MessagesWhen the trace task is running, you can manually save all or part of the messages in the message browse window in the .tmf, .txt or .csv format. The procedure is as follows:

1) Create a trace task in the LMT. For detail, refer to 28.6.2 "Creating Trace Tasks."

2) Right-click the message browse window, and choose Save All Messages on the shortcut menu. Or choose the messages to be saved, right-click them and choose Save Selected Messages on the shortcut menu.The Save dialog box as shown in Figure 28-7 opens up.

Figure 28-8 Save dialog box3) Enter a file name, and choose the file type and saving path.

The default saving path is \client\output\main\BSC6800\\trace. The default name is office name_trace type _yy-mm-dd_hh-mm-ss.tmf.

4) Click Save to save the file in the specified path.

28.6.5 Stopping/Restarting Trace Tasks

I. Task DescriptionYou can stop a trace task when it is not needed, and restart it later XE "trace:stopping/restarting"

XE "stopping:trace"

XE "restarting:trace" .

II. Prerequisite

A trace task is started.III. Operation ProcedureTo stop the trace task, right-click the message browse window, and choose Stop Trace Task.To restart the trace task, right-click the message browse window, and choose Restart Trace Task.28.6.6 Closing Trace Tasks

I. Task DescriptionThis task is performed to close a trace task when it is not needed any more XE "trace:closing"

XE "closing:trace" .

II. Prerequisite

A trace task is started.III. Operation Procedure

You can choose either of the following operations to close the task:

Click in the top right corner of the message browse window.

Right-click the message browse window, and choose Close All xxx Message Trace Tasks (xxx stands for specific trace tasks, for example, Close All MTP3BMessage Trace Tasks).

28.6.7 Browsing Traced Messages Offline I. Task DescriptionThis task is performed to use the Trace Viewer to browse offline the traced messages saved in the .tmf format XE "trace:offline browsing"

XE "offline browsing:traced message"

XE "trace:browsing offline"

XE "browsing offline:traced message" .

( Note:

You can find the .txt or .csv files in the saving directory. You can double-click them to read the traced messages.II. Prerequisite

The traced messages have been saved in the .tmf format.III. Operation Procedure

To browse traced messages offline, perform the following steps:1) Choose either of the following ways to start Trace Viewer.

Click on the toolbar on the Local Maintenance Terminal window. Choose Start > All Programs > Huawei Local Maintenance Terminal > Trace Viewer.The Open dialog box as shown in Figure 28-8 opens up.

Figure 28-9 Opening a file containing traced messages 2) Choose a file and click Open. Or double-click the file.

The default path for the files is \client\output\main\BSC6800\\trace. The window displays traced messages saved in the file, as shown in Figure 28-9.

Figure 28-10 Displaying traced messages

3) Browse these messages, or double-click one to learn about its details, as shown in Figure 28-6.

4) To browse other saved messages, choose File > Open. In the Open dialog box, choose and open files to read the traced messages saved in the files.

( Note:

In the Trace Viewer, you can also perform the following operations:

Right-click and choose Save All Messages to save all the messages in the window in .tmf or .txt format.

Right-click and choose Save Selected Messages to save selected messages in .tmf or .txt format.

Right-click and choose Find to locate a message.

Right-click and choose Properties to learn about the properties of the task that the tracing result corresponds to.

Click any button on the title bar to sequence the messages in the window by No., time, subrack No., direction, DPC, or content.

28.6.8 AlarmsNone.28.6.9 CountersNone.28.7 ReferencesNone.

Huawei Technologies Proprietary i