144199018-Enodeb-Lmt-User-Guide-v100r004c00-01-PDF-En

eNodeBV100R004C00

LMT User Guide

Issue 01Date 2011-09-15

HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2011. All rights reserved.No part of this document may be reproduced or transmitted in any form or by any means without prior writtenconsent of Huawei Technologies Co., Ltd. Trademarks and Permissions

and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.All other trademarks and trade names mentioned in this document are the property of their respective holders. NoticeThe purchased products, services and features are stipulated by the contract made between Huawei and thecustomer. All or part of the products, services and features described in this document may not be within thepurchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,and recommendations in this document are provided "AS IS" without warranties, guarantees or representationsof any kind, either express or implied.

The information in this document is subject to change without notice. Every effort has been made in thepreparation of this document to ensure accuracy of the contents, but all statements, information, andrecommendations in this document do not constitute the warranty of any kind, express or implied. Huawei Technologies Co., Ltd.Address: Huawei Industrial Base

Bantian, LonggangShenzhen 518129People's Republic of China

Website: http://www.huawei.comEmail: [email protected]

Issue 01 (2011-09-15) Huawei Proprietary and ConfidentialCopyright Huawei Technologies Co., Ltd.

i

About This Document

PurposeThis document provides an overview of the local maintenance terminal (LMT) and describesthe procedures for logging in to the LMT, running man-machine language (MML) commands,and operating and maintaining the eNodeB.

Product VersionsThe following table lists the product versions related to this document.

Product Name Product VersionDBS3900 LTE V100R004C00DBS3900 LTE TDD V100R004C00BTS3900 LTE V100R004C00BTS3900A LTE V100R004C00BTS3900L LTE V100R004C00

Intended AudienceThis document is intended for:l System engineersl Field engineersl Shift operatorsl Network operators

eNodeBLMT User Guide About This Document


ii

Change HistoryFor changes in the document, see 1 Changes in the eNodeB LMT User Guide.

Organization1 Changes in the eNodeB LMT User GuideThis chapter describes the changes in the eNodeB LMT User Guide.2 Introduction to the eNodeB LMTThis section describes the functions, system requirements, and main window of the LMT.3 Getting Started with the eNodeB LMTThis section describes how to manage LMT rights and how to log in to and exit the eNodeBLMT. A minimum of 1 GB free space is required to ensure that the LMT runs properly.4 Running eNodeB MML CommandsThis section describes how to run MML commands on the LMT to operate and maintain theeNodeB.5 Managing eNodeB Alarms or EventsYou can analyze, identify, and clear faults by managing alarms or events on the LMT.6 Managing the eNodeB TracingAfter a message tracing task is created, the traced messages can be browsed and saved. By tracingmessages, you can verify data and identify faults.7 Monitoring eNodeB Performance in Real TimeReal-time performance monitoring allows you to track eNodeB performance in real time8 Managing eNodeB SoftwareManaging eNodeB software involves upgrading eNodeB software and data configuration fileusing the File Transfer Protocol (FTP) server.9 Enabling the eNodeB to Perform Self-TestThe eNodeB self-test function helps check the version of eNodeB software, running status ofcells and RRUs, and alarms.10 Commissioning eNodeB EquipmentYou can commission eNodeB equipment by sending transparent messages or enabling COMport redirection.11 FAQsThis section provides the answers to frequently asked questions (FAQs) during the LMT use.

ConventionsSymbol Conventions



iii

The symbols that may be found in this document are defined as follows.

Symbol DescriptionIndicates a hazard with a high level of risk, which if notavoided, will result in death or serious injury.

Indicates a hazard with a medium or low level of risk, whichif not avoided, could result in minor or moderate injury.

Indicates a potentially hazardous situation, which if notavoided, could result in equipment damage, data loss,performance degradation, or unexpected results.Indicates a tip that may help you solve a problem or savetime.Provides additional information to emphasize or supplementimportant points of the main text.

General ConventionsThe general conventions that may be found in this document are defined as follows.

Convention DescriptionTimes New Roman Normal paragraphs are in Times New Roman.Boldface Names of files, directories, folders, and users are in

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

Courier New.

Command ConventionsThe command conventions that may be found in this document are defined as follows.

Convention DescriptionBoldface The keywords of a command line are in boldface.Italic Command arguments are in italics.[ ] Items (keywords or arguments) in brackets [ ] are optional.{ x | y | ... } Optional items are grouped in braces and separated by

vertical bars. One item is selected.



iv

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

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

vertical bars. A minimum of one item or a maximum of allitems can be selected.

[ x | y | ... ]* Optional items are grouped in brackets and separated byvertical bars. Several items or no item can be selected.

GUI ConventionsThe GUI conventions that may be found in this document are defined as follows.

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

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

signs. For example, choose File > Create > Folder.

Keyboard OperationsThe keyboard operations that may be found in this document are defined as follows.

Format DescriptionKey Press the key. For example, press Enter and press Tab.Key 1+Key 2 Press the keys concurrently. For example, pressing Ctrl+Alt

+A means the three keys should be pressed concurrently.Key 1, Key 2 Press the keys in turn. For example, pressing Alt, A means

the two keys should be pressed in turn.

Mouse OperationsThe mouse operations that may be found in this document are defined as follows.

Action DescriptionClick Select and release the primary mouse button without moving

the pointer.Double-click Press the primary mouse button twice continuously and

quickly without moving the pointer.



v

Action DescriptionDrag Press and hold the primary mouse button and move the

pointer to a certain position.



vi

Contents

About This Document.....................................................................................................................ii1 Changes in the eNodeB LMT User Guide................................................................................12 Introduction to the eNodeB LMT...............................................................................................3

2.1 Functions of the eNodeB LMT...........................................................................................................................42.2 System Requirements for the LMT Installation.................................................................................................42.3 Components of the LMT Main Window............................................................................................................6

3 Getting Started with the eNodeB LMT.....................................................................................93.1 Managing Rights...............................................................................................................................................10

3.1.1 Concepts Related to Rights Management................................................................................................103.1.2 Managing User Accounts........................................................................................................................133.1.3 Managing Login Passwords.....................................................................................................................143.1.4 Managing Command Groups...................................................................................................................15

3.2 Logging In to the LMT.....................................................................................................................................153.3 Exiting the LMT...............................................................................................................................................18

4 Running eNodeB MML Commands........................................................................................194.1 Basic Concepts Related to MML Commands..................................................................................................20

4.1.1 Introduction to MML Commands............................................................................................................204.1.2 Components of the MML Command Window........................................................................................21

4.2 Running a Single MML Command..................................................................................................................234.3 Running MML Commands in Batches.............................................................................................................244.4 Setting Parameters............................................................................................................................................25

5 Managing eNodeB Alarms or Events......................................................................................275.1 Basic Concepts Related to eNodeB Alarm or Event Management..................................................................28

5.1.1 Basic Concepts Related to Alarms or Events..........................................................................................285.1.2 Alarm or Event Log.................................................................................................................................285.1.3 Alarm Severity.........................................................................................................................................295.1.4 NM Alarm Type......................................................................................................................................29

5.2 Handling eNodeB Alarms or Events................................................................................................................305.2.1 Browsing Active Alarms or Events.........................................................................................................305.2.2 Querying Alarm or Event Logs...............................................................................................................305.2.3 Querying Alarm or Event Configurations...............................................................................................32

eNodeBLMT User Guide Contents


vii

5.2.4 Setting Alarm or Event Query Properties................................................................................................335.2.5 Querying Alarm or Event Handling Suggestions....................................................................................345.2.6 Manually Refreshing Alarms or Events..................................................................................................355.2.7 Manually Clearing Alarms or Events......................................................................................................355.2.8 Deleting Cleared Alarms or Events.........................................................................................................365.2.9 Saving the Information About Alarms or Events....................................................................................36

6 Managing the eNodeB Tracing.................................................................................................386.1 Overview of Message Tracing..........................................................................................................................406.2 Tracing Messages over the S1 Interface...........................................................................................................406.3 Tracing Messages over the X2 Interface..........................................................................................................426.4 Tracing Messages over the Uu Interface..........................................................................................................446.5 Tracing SCTP Messages...................................................................................................................................466.6 Tracing IFTS Messages....................................................................................................................................486.7 Tracing CMPv2 Messages................................................................................................................................506.8 MAC Tracing....................................................................................................................................................526.9 Tracing IEEE1588 V2 Messages......................................................................................................................546.10 General Operations Related to eNodeB Message Tracing.............................................................................56

6.10.1 Browsing Traced Messages Online.......................................................................................................566.10.2 Viewing the Properties of a Tracing Task.............................................................................................586.10.3 Viewing Message Details......................................................................................................................596.10.4 Automatically Saving Traced Messages................................................................................................596.10.5 Manually Saving Traced Messages.......................................................................................................606.10.6 Suspending a Message Tracing Task.....................................................................................................616.10.7 Resuming a Message Tracing Task.......................................................................................................626.10.8 Closing a Message Tracing Task...........................................................................................................626.10.9 Browsing Traced Messages Offline......................................................................................................63

7 Monitoring eNodeB Performance in Real Time....................................................................657.1 Overview of Real-time Performance Monitoring.............................................................................................667.2 Sector Performance Monitoring.......................................................................................................................667.3 RRU Performance Monitoring.........................................................................................................................687.4 Spectrum Detection..........................................................................................................................................717.5 General Operations Related to Real-time Performance Monitoring................................................................72

7.5.1 Browsing eNodeB Performance Monitoring Results Online..................................................................737.5.2 Setting the Chart Display Mode..............................................................................................................737.5.3 Saving eNodeB Performance Monitoring Results...................................................................................747.5.4 Browsing eNodeB Performance Monitoring Results Offline..................................................................74

7.6 Parameters for eNodeB Real-time Performance Monitoring...........................................................................757.6.1 Parameters for Sector Performance Monitoring......................................................................................757.6.2 Parameters for RRU Performance Monitoring........................................................................................757.6.3 Parameters for Clock Performance Monitoring.......................................................................................76

8 Managing eNodeB Software.....................................................................................................77



viii

8.1 Configuring the FTP Server.............................................................................................................................788.2 Managing eNodeB Software and Data Configuration File...............................................................................79

9 Enabling the eNodeB to Perform Self-Test............................................................................8210 Commissioning eNodeB Equipment.....................................................................................83

10.1 Enabling COM Port Redirection....................................................................................................................8410.2 Sending Transparent Messages......................................................................................................................8510.3 141 Test Overview..........................................................................................................................................86

10.3.1 Introduction to the 141 Test...................................................................................................................8610.3.2 Creating a Cell for 141 Tests.................................................................................................................8710.3.3 Conducting an Uplink 141 Test.............................................................................................................88

10.3.3.1 Testing the PRACH......................................................................................................................8910.3.3.2 Testing the PUCCH......................................................................................................................8910.3.3.3 Testing the PUSCH......................................................................................................................90

10.3.4 Conducting a Downlink 141 Test..........................................................................................................9210.3.4.1 Testing the Maximum Transmit Power........................................................................................9210.3.4.2 Testing the ACLR.........................................................................................................................9310.3.4.3 Testing the Frequency Error.........................................................................................................9410.3.4.4 Testing the Transmitter Intermodulation......................................................................................9510.3.4.5 Testing the EVM..........................................................................................................................9710.3.4.6 Testing the Transmitter Transient Period.....................................................................................9810.3.4.7 Testing the Transmit ON Or OFF Power.....................................................................................9910.3.4.8 Testing the Dynamic Range of Total TX Power........................................................................10010.3.4.9 Testing the Time Alignment Between Transmitter Branches....................................................10110.3.4.10 Testing the DL RS Power.........................................................................................................10210.3.4.11 Testing the Transmitter Spurious Emissions............................................................................10310.3.4.12 Testing the Occupied Bandwidth.............................................................................................10410.3.4.13 Testing the Operating Band Unwanted Emissions...................................................................105

10.4 Parameters for eNodeB Commissioning......................................................................................................10710.4.1 Parameters for COM Port Redirection................................................................................................10710.4.2 Parameters for Transparent Messages.................................................................................................10710.4.3 Parameters for the 141 Test.................................................................................................................107

10.4.3.1 Parameters for the PRACH Test.................................................................................................10710.4.3.2 Parameters for the PUCCH Test.................................................................................................10810.4.3.3 Parameters for the PUSCH Test.................................................................................................10910.4.3.4 Parameters for the Downlink 141 Test.......................................................................................110

11 FAQs...........................................................................................................................................11211.1 How to Switch a Minimum LMT Package to a Complete LMT Package....................................................11411.2 How to Handle Expiry of the Browser Cache..............................................................................................11511.3 How to Increase Responses During the Firefox Browser Use.....................................................................11611.4 How to Handle Incorrect Display of Colors of the LMT Main Window.....................................................11611.5 How to Handle Failed Display of the Verify Code in the LMT Login Dialog Box.....................................117



ix

11.6 How to Install OS Patches............................................................................................................................11811.7 How to Handle No Responses to the Operations Performed on the Menu of the LMT Main Window.......11811.8 How to Clear Garbled Characters That Occurred While Opening a CSV File in UTF-8 Coding...............11911.9 How to Set a Correct SSL Security Certificate............................................................................................12211.10 How to Rectify Errors That Occurred While Saving a File........................................................................12211.11 How to Rectify a Failure to Log In to the LMT Due to a High Default Internet Explorer Security Level..............................................................................................................................................................................123



x

1 Changes in the eNodeB LMT User GuideThis chapter describes the changes in the eNodeB LMT User Guide.

01 (2011-09-15)This is the first official release.Compared with draft A (2011-07-15) of V100R004C00, this issue adds the following topics:

Topic Change Description7.3 RRU Performance Monitoring Added the description about RRU

performance monitoring.10.3.3.1 Testing the PRACH Added the description about the PRACH test.10.4.3.1 Parameters for the PRACH Test Added the parameters for the PRACH test.

Compared with draft A (2011-07-15) of V100R004C00, this issue incorporates the followingchanges:

Topic Change Description10.3.3.2 Testing the PUCCH Modified the description about the PUCCH

test.10.3.3.3 Testing the PUSCH Modified the description about the PUSCH

test.10.4.3.2 Parameters for the PUCCH Test Modified the parameters for the PUCCH test.10.4.3.3 Parameters for the PUSCH Test Modified the parameters for the PUSCH test.

Compared with draft A (2011-07-15) of V100R004C00, this issue does not remove anyinformation.

eNodeBLMT User Guide 1 Changes in the eNodeB LMT User Guide


1

Draft A (2011-07-15)This is the draft.Compared with issue 04 (2011-06-10) of V100R003C00, this issue adds the following topics:

Topic Change Description2.3 Components of the LMT Main Window l Added names and IP addresses of NEs on

the title bar.l Added the current NE time in the LMT

window.l 6.2 Tracing Messages over the S1

Interfacel 6.3 Tracing Messages over the X2

Interfacel 6.4 Tracing Messages over the Uu

Interfacel 6.5 Tracing SCTP Messagesl 6.6 Tracing IFTS Messagesl 6.7 Tracing CMPv2 Messages

Added the description of the parameters andoutputs.

6.8 MAC Tracing Added the description about MAC tracing.6.9 Tracing IEEE1588 V2 Messages Added the description of IEEE1588 V2 clock

tracing.

Compared with issue 04 (2011-06-10) of V100R003C00, this issue does not incorporate anychanges.Compared with 04 (2011-06-10) of V100R003C00, this issue removes the following topics:l Removed the section "Parameters for eNodeB Tracing Management."l Removed the section "RRU Performance Monitoring."l Removed the section "Parameters for RRU Performance Monitoring."

eNodeBLMT User Guide 1 Changes in the eNodeB LMT User Guide


2

2 Introduction to the eNodeB LMTAbout This Chapter

This section describes the functions, system requirements, and main window of the LMT.

2.1 Functions of the eNodeB LMTThe eNodeB LMT deploys the eNodeB and identifies and clears faults locally.2.2 System Requirements for the LMT InstallationThis section describes the system requirements for the LMT installation.2.3 Components of the LMT Main WindowThis section describes the components of the LMT main window and the functions of eachcomponent.

eNodeBLMT User Guide 2 Introduction to the eNodeB LMT


3

2.1 Functions of the eNodeB LMTThe eNodeB LMT deploys the eNodeB and identifies and clears faults locally.Use the LMT to operate and maintain the eNodeB in any of the following scenarios:l When the transport link between the eNodeB and the M2000 is unavailable, use the LMT

to start the eNodeB locally.l When the eNodeB fails to communicate with the M2000, use the LMT to identify and clear

faults locally.l When alarms are generated on the eNodeB and related boards must be replaced locally,

use the LMT to identify and clear faults.NOTE

When the eNodeB communicates with the M2000 properly, Huawei recommends that you operate andmaintain the eNodeB at the network management center (NMC). When you must obtain information fromthe M2000 for fault identification, the M2000 may fail to provide adequate information because it managesmany network elements (NEs). At this time, use the LMT to operate and maintain the eNodeB.

The LMT provides a Graphical User Interface (GUI), which helps users operate and maintainthe eNodeB on the web page. It implements the following local operation and maintenance(O&M) functions:l Running eNodeB MML commandsl Managing eNodeB alarmsl Running MML commands in batchesl Tracing messagesl Monitoring eNodeB performance in real timel Software Managementl Enabling the eNodeB to perform self-testl Maintenance

2.2 System Requirements for the LMT InstallationThis section describes the system requirements for the LMT installation.

Hardware RequirementsTable 2-1 lists the hardware requirements for the LMT installation.

Table 2-1 Hardware requirementsItem Recommended

ConfigurationMinimum Configuration

CPU 2.8 GHz or higher 866 MHzRAM 1 GB 512 MBHard disk 80 GB 10 GB



4

Item RecommendedConfiguration

Minimum Configuration

Displayresolution

1024 x 768 or higher 800 x 600

CD-ROMdrive

- -

Networkadapter

10 Mbit/s or 100 Mbit/s 10 Mbit/s

Accessories Keyboard, mouse, modem,audio adapter, and speaker

Keyboard and mouse

Software RequirementsTable 2-2 lists the software requirements for the LMT installation.

Table 2-2 Software requirementsItem Recommended ConfigurationOperating system l Microsoft Windows XP

l Microsoft Windows 2003l Microsoft Windows 2008l Microsoft Windows Vistal Microsoft Windows 7NOTE

Currently, the LMT supports only web browsers and 32-bit operatingsystems.

Default language of theoperating system

English (United States)

Web browser l Microsoft Internet Explorer 8l Firefox 3.X (X indicates any digit)NOTEl You must set the security level of the web browser to medium or

low. Otherwise, the LMT menus cannot be viewed.l Internet Explorer 6 and Internet Explorer 7 are not recommended for

the LMT. If the LMT is terminated abnormally or has no responseswhen using Internet Explorer 6 or 7, a Firefox browser or an upgradefrom the Internet Explorer to Internet Explorer 8 is recommended.

JAVA Platform StandardEdition RuntimeEnvironment (JRE)

jre-6u11-windows-i586-p-s.exeNOTE

This file can be downloaded from http://java.com/ or http://support.huawei.com/.



5

Connection Port RequirementsIf the computer installed with the LMT cannot visit NEs because of firewalls between them,ports 20, 21, and 80 must be enabled by the firewall. If the computer must visit NEs using theHypertext Transfer Protocol Secure (HTTPS), port 433 must be enabled by the firewall.Ports 20 and 21 are used for the File Transfer Protocol (FTP). They need to be enabled in thecase of file transfer using FTP.Port 80 is used for the Hypertext Transfer Protocol (HTTP) by default. That is, the port is usedfor a web server by default.Port 433 is used for the HTTPS by default.

Communication Capability RequirementsThe computer installed with the LMT must support TCP/IP protocols.The minimum effective network bandwidth for the LMT is 512 kbit/s. The recommended valueis 2 Mbit/s or larger.

NOTEl The network bandwidth limits the web page opening speed. If the recommended effective bandwidth is

provided, the LMT runs fast. If a 512 kbit/s bandwidth is provided, all the functions can be performed butthe LMT runs slowly.

l The effective bandwidth is the bandwidth occupied by the LMT. If multiple applications compete for thebandwidth, the LMT may run slowly even if a 2 Mbit/s bandwidth is provided.

2.3 Components of the LMT Main WindowThis section describes the components of the LMT main window and the functions of eachcomponent.

Main WindowFigure 2-1 shows the LMT main window of DBS3900 LTE.

Figure 2-1 LMT main window



6

Table 2-3 describes the components of the LMT main window.

Table 2-3 Components of the LMT main windowComponent DescriptionTitle bar Displays names and IP addresses of NEs.MML Runs MML commands. For details, see 4.1.2 Components of the MML

Command Window.Alarm/Event Queries active alarms or events, alarm or event logs, and alarm or event

configurations.Batch Runs MML commands in batches.Trace Traces eNodeB messages.Monitor Monitors eNodeB performance in real time.Selftest Enables the eNodeB to perform self-test.SoftwareManagement

Manages eNodeB software.

Maintenance Enables COM port redirection, sends messages transparently, andconducts 141 tests (also called conformance tests).

Online HelpThe LMT provides two types of online help:l LMT helpl MML helpTable 2-4 describes the online help of the LMT.

Table 2-4 Online help of the LMTName Description Startup OperationLMT help Provides the

followinginformation:l LMT user

guidel Details of

alarmsl Details of

events

If using an Internet Explorer of Microsoft:l Press F1 or click Help in the LMT main window to

display the help information about the LMT.l Press F1 in the displayed dialog box to display the help

information about the dialog box.If using a Firefox browser, click Help in the LMT mainwindow to display the help information.



7

Name Description Startup OperationMMLhelp

Provides thefollowinginformationabout an MMLcommand:l Functionsl Precautionsl Parametersl Examplesl Outputs of a

querycommand

Type an MML command in the Command Input box. PressEnter or click Assist, and then click the Help Informationtab. The help information about the command is displayedon the tab page.



8

3 Getting Started with the eNodeB LMTAbout This Chapter

This section describes how to manage LMT rights and how to log in to and exit the eNodeBLMT. A minimum of 1 GB free space is required to ensure that the LMT runs properly.

3.1 Managing RightsManaging rights involves managing login accounts, user passwords, and command groups.3.2 Logging In to the LMTYou can log in to the LMT to manage the eNodeB locally. After the OM channel between theeNodeB and the M2000 server is established, you can log in to the eNodeB using the M2000server.3.3 Exiting the LMTIf you exit the LMT, the LMT is disconnected from the eNodeB.

eNodeBLMT User Guide 3 Getting Started with the eNodeB LMT


9

3.1 Managing RightsManaging rights involves managing login accounts, user passwords, and command groups.

3.1.1 Concepts Related to Rights ManagementThis section describes rights control principles, command groups, user types, operator rights,login passwords, and operation time limits.Table 3-1 describes the concepts related to rights management.

Table 3-1 Concepts related to rights managementItem Description

Principlesfor rightscontrol

The LMT O&M subsystem allows operations by multiple users at the same time.To ensure system security, operator rights are controlled in the followingaspects:l User identity: A user must enter the correct user name and password when

logging in to the LMT.l Operator rights: Users of different levels are allowed to use different GUI

operations and MML operations.l Operation time limit: It specifies the time segment for a user to perform

operations.



10

Item Description

Commandgroup

The LMT provides 32 command groups G_0 to G_31. Command groups G22to G31 are reserved. The command groups are described as follows:l G_0: Basic Commandl G_1: System Commandl G_2: Alarm Queryl G_3: Alarm Managementl G_4: Performance Queryl G_5: Performance Managementl G_6: Device Queryl G_7: Device Managementl G_8: Trace Queryl G_9: Trace Managementl G_10: Wireless Queryl G_11: Wireless Managementl G_12: Transport Queryl G_13: Transport Managementl G_14: Security Queryl G_15: Security Managementl G_16: Time Queryl G_17: Time Managementl G_18: Software Queryl G_19: Software Managementl G_20: Test Queryl G_21: Test Management

User type

LMT users are categorized into local users and element management system(EMS) users, which are described as follows:l Local users: This type of users (including the default admin user) is managed

by the LMT. Local users can log in to the eNodeB using the LMT even whenit is disconnected from the M2000 server.

l EMS users: This type of users is managed by the M2000 server in centralizedmode. That is, EMS user accounts are created, modified, authenticated, andauthorized by the M2000 server. Only authorized EMS users are allowed tolog in to the eNodeB using the LMT. Authorized EMS users can also log into the M2000 server using the M2000 client to manage the eNodeB. To logdirectly in to the eNodeB as an EMS user, ensure that the eNodeB isconnected to the M2000 server properly.



11

Item Description

Operatorrights

LMT user accounts are classified into internal user account and external useraccount. Different accounts have different rights, which are described asfollows:l There is only one internal user account, which is named admin. Its login

password is set when the operation and maintenance unit (OMU) applicationsoftware is installed. This account has all rights and cannot be changed orremoved.

l There are five levels of external user accounts, and each level is allocateddifferent rights. The user accounts are described as follows: GUEST: The users with GUEST-level accounts are only allowed to view

data. They can use command groups G_0, G_2, G_4, G_6, G_8, G_10,G_12, G_14, G_16, G_18, and G_20. USER: The users with USER-level accounts have the rights of the users

with GUEST-level accounts and are allowed to operate and maintain thesystem. They can use all command groups other than G_15. OPERATOR: The users with OPERATOR-level accounts have the rights

of the users with USER-level accounts and are allowed to configure data.They can use all command groups other than G_15. ADMINISTRATOR: The user with the ADMINISTRATOR-level

account has all rights. It can use all command groups. CUSTOM: The users with CUSTOM-level accounts can be allocated any

command groups when they are created. The rights can be changed.Different users with CUSTOM-level accounts have different rights.

Loginpassword

Login password involves the password rules, initial password, and passwordchange permissions, which are described as follows:l Each user account is allocated a login password to ensure system security.

A user must enter the correct user name and password when logging in tothe LMT. The user can operate the OMU only after being verified.

l The login password of the admin user is set when the OMU applicationsoftware is installed. The admin user, user with the ADMINISTRATORaccount, and authorized users with CUSTOM-level accounts are allowed toset the login password of an external user account when creating the account.

l All users can change their own passwords. The admin user, user with theADMINISTRATOR-level account, and authorized users with CUSTOM-level accounts are allowed to change the login password of any external useraccount. Only the admin user is allowed to change the admin login password.



12

Item Description

Operationtime limit

Operation time limit involves the definition, principle, and settings, which aredescribed as follows:l The operation time limit specifies the time segment for a user to perform

operations. There is no operation time limit for the admin user, that is, theadmin user can perform operations anytime. The operation time limit of anexternal user account is specified when the account is created. If no time limitis set, the account can perform operations anytime.

l The operation time limit is represented by a combination of date, day, andtime.

l Only the admin user, user with the ADMINISTRATOR-level account, andauthorized users with CUSTOM-level accounts are allowed to set or changethe operation time limit of an external user account.

3.1.2 Managing User AccountsManaging user accounts involves creating, modifying, and removing external user accounts.Table 3-2 describes the tasks involved in the management of user accounts.

Table 3-2 Tasks involved in the management of user accountsTask Description

Creating anexternaluseraccount

Function

Creates an external user account and sets the login password, userlevel, command group (for users with the CUSTOM account only),and operation time limit for the new user account. Only the adminuser, user with the ADMINISTRATOR account, and authorizedusers with the CUSTOM account are allowed to create an externaluser account.

Procedure

Run the ADD OP command to create an external user account.

Modifyingan externaluseraccount

Function

Modifies the attributes of an external user account, including theuser name, login password, user level, operator rights, and operationtime limit. The new password takes effect upon the next login.Modifications of other attributes take effect immediately. Only theadmin user, user with the ADMINISTRATOR account, andauthorized users with the CUSTOM account are allowed to modifythe attributes of an external user account.

Procedure

Run the MOD OP command to modify the attributes of an externaluser account.

Removingan externaluseraccount

Function

Removes an external user account. Only the admin user, user withthe ADMINISTRATOR account, and authorized users with theCUSTOM account are allowed to remove an external user account.



13

Task DescriptionProcedure

Run the RMV OP command to remove an external user account.

NOTE

l New user accounts must be different from existing user accounts.l The admin user is an internal account and cannot be removed.

3.1.3 Managing Login PasswordsManaging login passwords involves setting and viewing password policies and changing thepasswords of current and external user accounts.Table 3-3 describes the tasks involved in the management of login passwords.

Table 3-3 Tasks involved in the management of login passwordsTask Description

Settingpasswordpolicies

Function

Password policies define how to set login passwords. The policiesset restrictions on the minimum length and complexity of passwords.Only the user with the ADMINISTRATOR account user isauthorized to set login passwords.

Procedure

Run the SET PWDPOLICY command to set login passwords.

Viewingpasswordpolicies

Function

Users can view password policies before setting correct loginpasswords.

Procedure

Run the LST PWDPOLICY command to view password policies.

Changingthepasswordof a currentuseraccount

Function

The current user can change its own password after login. The newpassword takes effect upon the next login.

Procedure

1. Click Password in the toolbar in the LMT main window. ThePassword dialog box is displayed.

2. Fill in the Old Password, New Password, and ConfirmPassword boxes, and then click OK.

Changingthepasswordof anexternaluseraccount

Function

Only the admin user, the user with the ADMINISTRATOR account,and authorized users with the CUSTOM account are allowed tochange the password of an external user account by modifyingpassword options.

Procedure

Run the MOD OP command to change the password of an externaluser account.



14

NOTEBe cautious when changing the password of the admin user. If you forget the password, you cannot log in.In this case, contact Huawei for technical support.

3.1.4 Managing Command GroupsManaging a command group involves viewing and naming a command group and changing thecommands in a command group.Table 3-4 describes the tasks involved in the management of command groups.

Table 3-4 Tasks involved in the management of command groupsTask Description

Viewing acommandgroup

Function

The eNodeB provides 32 command groups G_0 to G_31. Commandgroups G22 to G31 are reserved. Only the admin user, user with theADMINISTRATOR-level account, and authorized users with theCUSTOM-level account are allowed to view command groups.

Procedure

Run the LST CCG command.

Naming acommandgroup

Function

Only the admin user, user with the ADMINISTRATOR account, andauthorized users with the CUSTOM account are allowed to name acommand group.

Procedure

1. Run the LST CCGN command to view the name of a commandgroup.

2. Run the SET CCGN command to name a command group.

Changingthecommandsin acommandgroup

Function

Only the admin user, user with the ADMINISTRATOR account, andauthorized users with the CUSTOM account are allowed to changethe commands in a command group.

Procedure

1. Run the ADD CCG command to add commands to a commandgroup.

2. Run the RMV CCG command to remove commands from acommand group.

3.2 Logging In to the LMTYou can log in to the LMT to manage the eNodeB locally. After the OM channel between theeNodeB and the M2000 server is established, you can log in to the eNodeB using the M2000server.

PrerequisiteBefore using the LMT, you must install the JAVA Platform Standard Edition RuntimeEnvironment (JRE) plug-in of jre-6u11-windows-i586 or a later version in the computerconfigured with the LMT. The JRE plug-in is a standard Java runtime environment plug-in,which can be downloaded from http://java.com/ or http://support.huawei.com/.



15

l If the plug-in is not installed in the computer, the system prompts you to install it duringlogin.

l If the installed plug-in is not the latest version, the system prompts you to upgrade it duringlogin. You are advised to uninstall the existing version before installing the latest version.

l If you fail to log in to the LMT after the plug-in is upgraded to the latest version, restartthe browser and then log in.

ContextLMT users are categorized into local users and element management system (EMS) users. Fordetails, see 3.1.1 Concepts Related to Rights Management.A maximum of four local users and EMS users can log in to the LMT.If the colors of the LMT main window cannot be displayed, choose Tools > Internet Optionsfrom the menu of the Internet Explorer. On the General tab page, click Accessibility. Then,clear the Ignore colors specified on Web pages check box under Formatting.

WARNINGDo not change the system time or time zone of a computer installed with the LMT when theLMT is running. Otherwise, a critical fault may occur in the system. If the system time or timezone has to be changed, you must perform the operation after the LMT exits.

CAUTIONl The refresh function of the browser cannot be used on the LMT. If you use the refresh function

in the LMT main window, the window exits. If you use the refresh function on the monitoringpage, an error occurs in the script.

l When the LMT uses an Internet Explorer, do not change the properties of the file system.Otherwise, the Internet Explorer is automatically refreshed, and therefore an error occurs inthe LMT main window.

l If you start FTP services by choosing Start > Run, the LMT main window is replaced withthe login dialog box of the FTP server. To avoid this problem, choose Tools > InternetOptions from the menu of the Internet Explorer. On the Advanced tab page, clear the Reusewindows for launching shortcuts check box under Browse.

l Before an LMT version upgrade or rollback, you must clear the buffer and cookies of theInternet Explorer.

l If you press the ALT + key to restore the window. If the window cannot restore, youare advised to close the Internet Explorer and log in to the LMT again.

Procedurel To log in to the eNodeB using the LMT, perform the following steps:



16

1. Type the IP address of the LTE Main Processing and Transmission Unit (LMPT) forlocal maintenance in the address box of the Internet Explorer. The default IP addressis 192.168.0.49.

2. Click Go. The Local Maintenance Terminal dialog box is displayed, as shown inFigure 3-1.

Figure 3-1 Local Maintenance Terminal login dialog box

3. Fill in the User Name, Password, and Verify Code boxes. Set User Type to Local.

NOTE

By default, the user name and password are admin and admin123 respectively. They are case-sensitive.If the verification code is indistinct, click Obtain verify code to change the verification code.

4. Click Login. The LMT main window is displayed.NOTE

If the login fails because the provided information is incorrect, click Reset and enter the correctinformation. If the login failure persists, check the connection between the LMT and the LMPT.

l To log in to the eNodeB using the M2000, perform the following steps:1. Type the OM IP address of the LMPT in the address box of the Internet Explorer.

NOTE

If the LMT uses an Internet Explorer, perform the following settings before typing the IP address:1. Choose Tools > Internet Options from the menu bar. The Internet Options dialog box is

displayed. On the Connections tab page, click LAN Settings. In the displayed LAN Settingsdialog box, under Proxy server, select Use a proxy server for your LAN, and then type theIP address of the M2000 in the Address box and set Port Number to 80.

2. Choose Tools > Internet Options from the menu bar. The Internet Options dialog box isdisplayed. On the Advanced tab page, select Use HTTP1.1 through proxy connections underHTTP 1.1 settings.



17

2. Click Go. The Local Maintenance Terminal dialog box is displayed, as shown inFigure 3-1.

3. Fill in the User Name, Password, and Verify Code boxes. Set User Type to EMS.NOTE

EMS user names and passwords are authorized by the M2000 server.If the verification code is indistinct, click Obtain verify code to change the verification code.

4. Click Login. The LMT main window is displayed.NOTE

If the login fails because the provided information is incorrect, click Reset and enter the correctinformation. If the login failure persists, check the connection between the LMT and the LMPT.

----End

3.3 Exiting the LMTIf you exit the LMT, the LMT is disconnected from the eNodeB.

ProcedureStep 1 Click Logout in the toolbar in the LMT main window. The Confirm dialog box is displayed

for your confirmation.Step 2 Click OK. The LMT is disconnected from the existing eNodeB. A dialog box for logging in to

the LMT is displayed.Step 3 Close the Internet Explorer, and exit the LMT.

----End



18

4 Running eNodeB MML CommandsAbout This Chapter

This section describes how to run MML commands on the LMT to operate and maintain theeNodeB.

4.1 Basic Concepts Related to MML CommandsThe basic concepts related to MML commands consist of MML commands and Graphical UserInterface (GUI) of MML commands.4.2 Running a Single MML CommandYou can perform routine operation and maintenance by running MML commands one by one.4.3 Running MML Commands in BatchesTo perform an independent function or operation, you can compile a batch file and then runMML commands in batches.4.4 Setting ParametersYou can set parameters in the MML Setting dialog box.

eNodeBLMT User Guide 4 Running eNodeB MML Commands


19

4.1 Basic Concepts Related to MML CommandsThe basic concepts related to MML commands consist of MML commands and Graphical UserInterface (GUI) of MML commands.

4.1.1 Introduction to MML CommandsThis section describes the functions, formats, and types of operations performed using MMLcommands.

Functions of MML CommandsYou can operate and maintain the entire eNodeB using MML commands. The MML commandsenable you to perform the following operations:l System managementl Equipment managementl Transport managementl Radio configurationl Managing eNodeB alarmsl License management

Formats of MML CommandsThe format of an MML command can be "Command Word: Parameter Name=Value;".The command word is mandatory, whereas the parameter name and value are optional. Examplesof MML commands are as follows:l An example of an MML command with a command word and parameters: SET

ALMSHLD: AID=25600, SHLDFLG=UNSHIELDED;l An example of an MML command with only a command word: LST VER:;

Types of Operations Performed Using MML CommandsThe MML command format is denoted as Action + Object. Table 4-1 describes the mostcommonly used MML commands.

Table 4-1 Most commonly used MML CommandsAction MeaningACT ActivateADD AddBKP BackupBLK Block



20

Action MeaningDLD DownloadDSP Display (used for dynamic information)LST List (used for static information)MOD ModifyRMV RemoveRST ResetSET SetSTP Stop or closeSTR Start or openUBL UnblockULD UploadSCN ScanCLB Calibrate

4.1.2 Components of the MML Command WindowThis section describes the components of the MML command window.Figure 4-1 shows the MML command window.



21

Figure 4-1 MML command window

Table 4-2 describes the components of the MML command window.

Table 4-2 Components of the MML command windowSN Field Description1 Common

Maintenance tabDisplays the output of an MML command.

2 Operation Recordtab

Displays the information about all the historycommands executed by the operator.

3 Help Informationtab

Displays the help information about an MMLcommand.

4 Pane for manualinput of an MMLcommand

Displays the commands and parameter values manuallyentered.

5 HistoryCommand box

Records all the commands and parameters entered bythe operator during one session after login.



22

SN Field Description6 Command Input

boxDisplays all the MML commands of the system. Youcan select an MML command from the drop-down listor directly enter a command.

7 Pane for settingsparameters of anMML command

Displays all parameters that can be set in an MMLcommand entered in the Command Input box. It alsoprovides a dialog by which you can set parametervalues. The parameters in red are mandatory, forexample, Cabinet No. in Figure 4-1. The parametersin black are optional, for example, Subrack No. inFigure 4-1.

8 Save Result checkbox

You can click Save Result, Auto Scroll, or Clear All.

NOTE

For details about an MML command and relevant parameters, see the MML command help.

4.2 Running a Single MML CommandYou can perform routine operation and maintenance by running MML commands one by one.

PrerequisiteYou have logged in to the LMT.

ContextYou can run a single MML command using one of the following methods:l Type an MML command in the Command Input box.l Select an MML command from the History Command box.l Select an MML command from the MML Commands navigation tree.l Type an MML command in or copy an MML command script to the pane for manual input

of the command.

Procedurel Type an MML command in the Command Input box.

1. Type an MML command in the Command Input box. When typing an MMLcommand, select the command from the predictive drop-down list.

2. Press Enter or click Assist. The parameters related to the command are displayed inthe pane for settings parameters of the MML command.

3. Set relevant parameters in the pane.4. Press F9 or click Exec to run the command. The MML command execution result is

displayed on the Common Maintenance tab page.



23

l Select an MML command from the History Command box.1. Select a history command from the History Command box. (That is, press F7 or click

to select the previous command, and press F8 or click to select thenext command.) The parameters related to the command are displayed in the pane forsetting parameters of an MML command.


displayed on the Common Maintenance tab page.l Select an MML command from the MML Commands navigation tree.

1. Select an MML command from the MML Commands navigation tree and double-click it.


displayed on the Common Maintenance tab page.NOTEl The parameters in red are mandatory, and those in black are optional.l To obtain information about a parameter, move the pointer to the input box of the parameter.l When an MML command fails to be executed, the execution result in red is on the Common

Maintenance tab page.l Type an MML command in or copy an MML command script to the pane for manual input

of the command.1. Type an MML command in or copy an MML command script with complete

parameter settings to the pane for manual input of the command.2. Press F9 or click Exec to run the command. The MML command execution result is

displayed on the Common Maintenance tab page.----End

4.3 Running MML Commands in BatchesTo perform an independent function or operation, you can compile a batch file and then runMML commands in batches.

Prerequisitel You have logged in to the LMT.l The batch file is ready.

ContextThe batch file (also called data script file) is a text file. It contains a group of commands for aspecial task. The system automatically runs MML commands in sequence.

ProcedureStep 1 In the LMT main window, click the Batch tab.Step 2 Copy a group of command scripts with complete parameter values from the batch file to the

pane for MML commands, or manually enter a group of MML commands.



24

If... Then...Run the MML commands in batches indebug pattern

Go to Step 3.

Run the MML commands in batches incommon pattern

Go to Step 4.

Step 3 Click Go To Debug Pattern to specify an execution mode.

NOTE

You can choose one of the following execution modes.l Execute All: The system automatically runs all MML commands one by one.l Execute Step by Step: The system runs an MML command each time you click Go.l Execute with Breakpoint: After you mark a breakpoint by double-clicking a command and then click

Go, the system runs from the first command to the command before this breakpoint. After you click Goagain, the system continues to run from the breakpoint to the end or to the command before the nextbreakpoint.

l Execute Range: The system runs the MML commands within the specified range.Step 4 Click Go. The system runs the MML commands.

----End

4.4 Setting ParametersYou can set parameters in the MML Setting dialog box.


ProcedureStep 1 In the LMT main window, click the Setting tab. Then, the MML Setting dialog box is displayed,

as shown in Figure 4-2.



25

Figure 4-2 MML Setting dialog box

Step 2 Set related parameters as required.Step 3 Click OK. The settings are complete.

----End



26

5 Managing eNodeB Alarms or EventsAbout This Chapter

You can analyze, identify, and clear faults by managing alarms or events on the LMT.

5.1 Basic Concepts Related to eNodeB Alarm or Event ManagementBefore managing eNodeB alarms or events, you must understand basic concepts related toeNodeB alarms or events, alarm or event definition, alarm or event log, alarm or event severity,and network management (NM) alarm or event type.5.2 Handling eNodeB Alarms or EventsHandling eNodeB alarms or events involves browsing active alarms or events, querying alarmor event logs, querying alarm or event configurations, manually clearing alarms or events, andquerying alarm or event handling suggestions.

eNodeBLMT User Guide 5 Managing eNodeB Alarms or Events


27

5.1 Basic Concepts Related to eNodeB Alarm or EventManagement

Before managing eNodeB alarms or events, you must understand basic concepts related toeNodeB alarms or events, alarm or event definition, alarm or event log, alarm or event severity,and network management (NM) alarm or event type.

5.1.1 Basic Concepts Related to Alarms or EventsThis section describes the basic concepts related to fault, event, and engineering alarms.

Fault AlarmA fault alarm is generated when a hardware is faulty or a major function is abnormal. A faultalarm has a higher severity than an event. Based on the status of the faults, fault alarms can becategorized into active alarms and cleared alarms.l If a fault is cleared, the status of the alarm changes to cleared. This type of alarm is called

a cleared alarm.l If a fault is not cleared, the status of the alarm remains active. This type of alarm is called

an active alarm.NOTE

You can search a database for cleared alarms.

Event AlarmAn event notifies users of important information when the system is running properly. Usersneed not handle an event when it is generated.

Engineering Alarml If an NE is being installed, commissioned, upgraded, expanded, or relocated, the NE is in

the engineering state.l The following are engineering alarms: alarms reported by physical or logical equipment in

the engineering state; alarms that are generated by the peer equipment but are associatedwith the alarms reported by the equipment in the engineering state; cleared alarmscorresponding to engineering alarms.

5.1.2 Alarm or Event LogThe alarm or event logs record detailed information about each alarm or event generated by thesystem. In this way, all alarms or events can be easily queried.You can obtain the detailed information about eNodeB alarms or events from the alarm or eventlogs. For details about how to query the alarm or event logs, see 5.2.2 Querying Alarm or EventLogs.



28

5.1.3 Alarm SeverityThe alarm severity indicates the severity of an alarm. Based on the severity, all alarms can becategorized into four types: critical, major, minor, and warning.Table 5-1 describes alarm severities and handling suggestions.

Table 5-1 Alarm severities and handling suggestionsSeverity Definition Handling

SuggestionCritical Service-affecting condition. Critical alarms

require immediate attention, and must be clearedimmediately. For example, faulty devices arerepaired or unavailable resources are restored.

Alarms must becleared immediately.Otherwise, thesystem may breakdown.

Major Degradation of service, not a complete loss ofservice. Major alarms must be cleared duringworking hours. For example, device performanceand resource performance improve.

These alarms must becleared in time.Otherwise, someimportant functionscannot beimplemented.

Minor Non-service-affecting condition. Minor alarmsmust be handled within a certain period to avoidseverer problems.

This helpsmaintenancepersonnel identifyand clear potentialproblems in time.

Warning Potential service-affecting condition. Warningalarms must be cleared as required.

You only need tolearn about theoperating status ofthe system.

5.1.4 NM Alarm TypeBased on network management (NM) standards, alarms are categorized as follows:l Power alarm: related to the power systeml Environment alarm: related to environment of the equipment rooml Signaling alarm: related to service signalingl Trunk alarm: related to the transport subsysteml Hardware alarm: related to boardsl Software alarm: related to softwarel Running alarm: related to system runningl Communication alarm: related to the communication systeml QoS alarm: related to QoS.



29

l Integrity violation alarm: a type of security alarm, which indicates that information maybe modified, added, or removed without permission.

l Operation violation alarm: a type of security alarm, which indicates that services areunavailable or unreachable due to incorrect operations, faults, or other reasons.

l Physical violation alarm: a type of security alarm, which indicates that physical resourcesare unavailable due to possible attacks.

l Security violation alarm: a type of security alarm, which indicates that the security serviceor security mechanism detects that the system is experiencing attacks.

l Time domain violation alarm: a type of security alarm, which indicates that unexpectedevents have occurred.

l Processing error alarm: related to other exceptions.

5.2 Handling eNodeB Alarms or EventsHandling eNodeB alarms or events involves browsing active alarms or events, querying alarmor event logs, querying alarm or event configurations, manually clearing alarms or events, andquerying alarm or event handling suggestions.

5.2.1 Browsing Active Alarms or EventsNormal alarms, events, and engineering alarms that are reported to the LMT are displayed onthe Browse Alarm/Event tab page in real time. You can view the detailed information aboutsuch alarms or events to determine the real-time running status of the system.


ProcedureStep 1 In the LMT main window, click the Alarm/Event tab, and then click the Browse Alarm/

Event tab on the displayed Alarm/Event tab page. The Browse Alarm/Event tab page containsNormal Alarm, Event, and Engineering Alarm sub-tab pages.

NOTEOn the Normal Alarm sub-tab page, normal alarms are generated when the eNodeB is in the common state.On the Event sub-tab page, event alarms are generated. On the Engineering Alarm sub-tab page, engineeringalarms are generated when the eNodeB is in the engineering state.

Step 2 View the alarm or event information on the Browse Alarm/Event tab page.Step 3 To determine the detailed information about an alarm or event, double-click the record of the

alarm or event. The Detailed Information dialog box is displayed.Step 4 In the Detailed Information dialog box, click the Solution tab to query the meaning of an alarm

or event record, impacts on the system, self-handling process, and handling suggestions.----End

5.2.2 Querying Alarm or Event LogsYou can determine the previous running status of the equipment by querying the historical alarmsor events from the alarm or event logs.



30


Procedurel To query alarm or event logs in GUI mode, perform the following steps:

1. In the LMT main window, click the Alarm/Event tab, and then click the QueryAlarm/Event Log tab on the Alarm/Event tab page. The Query Alarm/EventLog tab page is displayed, as shown in Figure 5-1.

Figure 5-1 Query Alarm/Event Log tab page

To query the alarms or events generated and cleared within the specified time, clickthe General Option tab. Table 5-2 describes the fields on the tab page.

Table 5-2 Description of the fields on the General Option tab pageField DescriptionType Alarm or event type to be selected. By default, all the types

are selected.Raised Time l If you select the Raised Time check box, the alarms

or events generated within the specified time aredisplayed.

l If you do not select the Raised Time check box, thealarms or events generated in the following time aredisplayed by default: Any date as the start date and any time as the start

time The current date as the end date and the current time

as the end timeSeverity Severities of the alarms or events to be selected. All the

severities are selected by default.



31

Field DescriptionSpecial Flag Special flag by which to select an alarm or event. All is

selected by default.Return Amount Number of records in the query result. A maximum of

1,000 records can be displayed.

To query a type of alarm or event based on the serial number, ID, event type, andboard location, click the Detailed Option tab. The Detailed Option tab page isdisplayed. Table 5-3 describes the fields on the Detailed Option tab page.Detailed Option tab page

Table 5-3 Description of the fields on the Detailed Option tab pageField DescriptionEvent Type Event types of the alarms or events to be selected. All the

types are selected by default.ID IDs of the alarms or events to be selected.Serial No. Serial numbers of the alarms or events to be selected.Board Location Position of a board where alarms or events are reported, for

example, Cabinet No., Subrack No., Slot No..

2. Set search criteria as required.3. Click Query. The query results are displayed in the Result area.4. To view detailed alarm or event information, double-click the record of the alarm or

event. The Detailed Information dialog box is displayed.5. In the Detailed Information dialog box, click the Solution tab to query the meaning

of an alarm or event record, impacts on the system, self-handling process, and handlingsuggestions.

6. Click Close to exit the dialog box.l To query alarm or event logs in MML mode, perform the following steps:

Run the LST ALMLOG command.----End

5.2.3 Querying Alarm or Event ConfigurationsBy querying alarm or event configurations, you can determine alarm severities, masking status,and modification information.




32

ContextThe search criteria that can be set are as follows:l IDl Severityl Modification Flagl Shield Flagl Return Amount

ProcedureStep 1 In the LMT main window, click the Alarm/Event tab, and then click the Query Alarm or Event

Configuration tab on the displayed Alarm/Event tab page.Step 2 Set search criteria as required.Step 3 Click Query. The query results are displayed in the Result area.

NOTE

l To modify alarm or event configurations, right-click in the blank area and then choose ModifyConfiguration or click the Modify Configuration tab in the lower right corner.

l To restore alarm or event configurations, right-click in the blank area and then choose RestoreConfiguration or click the Restore Configuration tab in the lower right corner.

----End

5.2.4 Setting Alarm or Event Query PropertiesSetting alarm or event query properties specifies the settings in an alarm display dialog box. Youcan customize a color for each alarm or event severity and set alarm or event display columns.


ProcedureStep 1 In the LMT main window, click the Alarm/Event tab. The Alarm tab page is displayed.Step 2 Click Setting in the upper right corner of the Alarm/Event tab page. The Setting dialog box is

displayed, as shown in Figure 5-2.



33

Figure 5-2 Setting dialog box

NOTE

If Enable is selected from the Tips drop-down list, the detailed information about the alarm or event is displayedwhen you move the pointer on an alarm or event record on the Browse Alarm/Event or Query Alarm/EventLog tab page.

Step 3 Set the properties of the alarm or event display dialog box as required.NOTE

To restore the settings to default settings, click Default.

Step 4 Click OK.----End

5.2.5 Querying Alarm or Event Handling SuggestionsYou can query the detailed help information about an alarm or event based on alarm or eventhandling suggestions.


ContextThe detailed help information about an alarm or event involves:l Descriptionl Parametersl Impact on the systeml System actions



34

l Possible causesl Handling procedure

ProcedureStep 1 Double-click an alarm on the Browse Alarm/Event or Query Alarm or Event Log tab page.

The Detailed Information dialog box is displayed.Step 2 In the displayed Detailed Information dialog box, click Solution. The online help of the alarm

or event is displayed.NOTE

After you click an alarm or event, right-click Solution. The online help of the alarm or event is displayed.

Step 3 View the meaning, impact on the system, system actions, and handling procedure.Step 4 Click X in the upper right corner of the online help to exit the online help.

----End

5.2.6 Manually Refreshing Alarms or EventsWhen browsing or querying alarms or events, you can manually refresh the alarms or eventsdisplayed on the Browse Alarm/Event or Query Alarm/Event Log tab page.


ProcedureStep 1 Click Refresh or right-click Refresh on the Browse Alarm/Event, Query Alarm/Event

Log, or Query Alarm/Event Configuration tab page.NOTE

l The alarms or events are displayed on the Browse Alarm/Event tab page in real time. Therefore, the clearedalarms or events are not displayed after you refresh the tab page.

l The alarm or events are not displayed on the Query Alarm/Event Log tab page. Therefore, the alarms orevents are updated and displayed based on original search criteria after you manually refresh the tab page.

----End

5.2.7 Manually Clearing Alarms or EventsWhen the cause of an alarm or event is located or the alarm or event can be ignored, you canmanually clear the alarm or event.


ProcedureStep 1 Select an alarm or event to be manually cleared on the Browse Alarm/Event or Query Alarm/

Event Log tab page.



35

Step 2 Right-click Clear. The Confirm dialog box is displayed for your confirmation.Step 3 Click OK. The selected alarm or event is cleared, and its color automatically changes to the

color of a cleared one.----End

5.2.8 Deleting Cleared Alarms or EventsWhen browsing active alarms or events or querying alarm or event logs, you can delete thecleared alarms or events displayed on the Browse Alarm/Event or Query Alarm/Event Logtab page.


ProcedureStep 1 On the Browse Alarm/Event or Query Alarm/Event Log tab page, click Delete All, Delete

All Cleared Alarms, or Delete Selected Cleared Alarms to clear alarms as required. Table5-4 describes the functions of menu items.

Table 5-4 Functions of menu itemsItem DescriptionDelete All Deletes all the alarms on the Browse Alarm/Event or Query

Alarm/Event Log tab page.Delete All ClearedAlarms

Deletes all the cleared alarms on the Query Alarm/Event Log tabpage or on the Normal Alarm and Engineering Alarm sub-tabpages of the Browse Alarm/Event tab page.

Delete SelectedCleared Alarms

Deletes all the selected cleared alarms on the Query Alarm/EventLog tab page.

----End

5.2.9 Saving the Information About Alarms or EventsYou can save part or all of the alarm or event records displayed on the Browse Alarm/Eventor Query Alarm/Event Log tab page as files in .csv format for future reference.


ProcedureStep 1 On the Browse Alarm/Event or Query Alarm/Event Log tab page, select an alarm or event

record to be saved, and then right-click Save Selected. The Save dialog box is displayed.



36

Step 2 Enter the file name and specify the save path and file type.Step 3 Click Save.

----End



37

6 Managing the eNodeB TracingAbout This Chapter

After a message tracing task is created, the traced messages can be browsed and saved. By tracingmessages, you can verify data and identify faults.

6.1 Overview of Message TracingThe section describes message tracing management functions and the internal process ofmessage tracing.6.2 Tracing Messages over the S1 InterfaceThis section describes how to trace all control plane messages over the S1 interface. Tracedmessages can be automatically or manually saved. You can browse the traced messages onlineor offline. In addition, when analyzing the traced messages, you can view the InformationElements (IEs) contained in the messages.6.3 Tracing Messages over the X2 InterfaceThis section describes how to trace all control plane messages over the X2 interface. Tracedmessages can be automatically or manually saved. You can browse the traced messages onlineor offline. In addition, when analyzing the traced messages, you can view the InformationElements (IEs) contained in the messages.6.4 Tracing Messages over the Uu InterfaceThis task is used to trace all or part of signaling messages over the Uu interface of specified cellsor all the cells in an eNodeB. Traced messages can be automatically or manually saved. Youcan browse the traced messages online or offline.6.5 Tracing SCTP MessagesThis section describes how to trace Stream Control Transmission Protocol (SCTP) messagesand to identify faults on SCTP links. Traced messages can be automatically or manually saved.You can browse the traced messages online or offline.6.6 Tracing IFTS MessagesThis section describes how to trace the messages of a single UE in a specific cell and the statisticalresult of data transfer on the user plane based on the causes for the RRC connection setup sothat abnormal UE procedures are detected. The UE messages to be traced include the controlplane messages over the S1, X2, or Uu interface. Traced messages can be automatically ormanually saved. You can browse the traced messages online or offline.

eNodeBLMT User Guide 6 Managing the eNodeB Tracing


38

6.7 Tracing CMPv2 MessagesThis task is used to trace CMPv2 messages. Traced messages can be automatically or manuallysaved. You can browse the traced messages online or offline. In addition, when analyzing thetraced messages, you can view the Information Elements (IEs) contained in the messages.6.8 MAC TracingThis section describes how to trace synchronization status messages (SSMs) and to identifyfaults on synchronous Ethernet links.6.9 Tracing IEEE1588 V2 MessagesThis section describes how to trace IEEE1588 V2 messages and to identify faults on IEE1588clock links.6.10 General Operations Related to eNodeB Message TracingThe general operations for tracing involves browsing, querying, and saving traced messages andsuspending, recreating, and closing a tracing task. The operations are applicable to all messagetracing tasks.



39

6.1 Overview of Message TracingThe section describes message tracing management functions and the internal process ofmessage tracing.

Functions of Message Tracing ManagementMessage tracing management traces interfaces, signaling links, UEs, and internal messages. Itapplies to routine equipment maintenance, debugging, and fault location.Tracing functions are as follows:l Tracing messages over the S1 interfacel Tracing messages over the X2 interfacel Tracing messages over the Uu interfacel Tracing SCTP messagesl Tracing IFTS messagesl Tracing CMPv2 messagesl Tracing MAC messagesl Tracing IEEE1588 V2 messages

Internal Process of Message TracingThe internal process of message tracing involves creating a tracing task on the LMT and reportingresults to the LMT.l Creating a tracing task on the LMT

1. After you create a tracing task on the LMT, the LMT sends a binary command to theeNodeB to create the task.

2. The eNodeB allocates an ID to the task and forwards the command to the tracingmanagement module of a specified board.

3. After receiving the command, the tracing management module records the parametersfor tracing contained in the command in the filter table and sends messages to theservice processing module.

4. The service processing module updates the local filter table based on the messagesfrom the tracing management module.

l Reporting results to the LMT1. After receiving messages from the tracing management module, the service processing

module verifies that the parameters in the local filter table are updated. Then, it reportsthe messages meeting filter criteria to the LMT based on the task IDs contained in themessages.

2. The LMT analyzes the messages and displays tracing results in the window.

6.2 Tracing Messages over the S1 InterfaceThis section describes how to trace all control plane messages over the S1 interface. Tracedmessages can be automatically or manually saved. You can browse the traced messages online



40

or offline. In addition, when analyzing the traced messages, you can view the InformationElements (IEs) contained in the messages.

ContextA maximum of 12 message tracing tasks can be performed simultaneously on each S1 interface,and the parameters for each task cannot be identical.

ProcedureStep 1 In the LMT main window, click the Trace tab.Step 2 In the Trace Navigation Tree pane, choose Interface Trace Task > S1 Trace. Double-click

S1 Trace. The S1 Trace dialog box is displayed, as shown in Figure 6-1.

Figure 6-1 S1 Trace dialog box

Step 3 Set related parameters in the displayed S1 Trace dialog box. For details about parameter settings,

see Table 6-1.



41

Table 6-1 Parameters for message tracing over the S1 interfaceParameter

Description

TraceDirection

It can be set to Trace Both, Trace Sender, or Trace Receiver based on the directionof the message to be traced over the S1 interface.

TraceType

It can be set to All MME or Appoint MME based on the MME to be traced. WhenAppoint MME is selected, only the messages related to the MME are traced if S1ID is set. If S1 ID is not set, the messages related to all MMEs are traced.

MessageType

You can select all message types or one or more message types. When Select Allis selected, all messages are traced. Otherwise, only the selected type

Documents

144199018-Enodeb-Lmt-User-Guide-v100r004c00-01-PDF-En