Huawei Operation and Maintenance ISSUE 1.00

MBTS GU V100R009 Operation and Maintenance P-1
Confidential Information of Huawei. No Spreading Without

Permission

Permission

Permission
 The BTS LMT is mainly used to support commissioning the BTS, locally locate faults,
and clear faults.
 You can operate and maintain the BTS through the LMT in the following scenarios:
 When the transmission between the BTS and the U2000 is unavailable, you
can commissioning the BTS through the LMT.
 When the communication between the BTS and the U2000 fails, you can
locate and clear faults through the LMT.
 When alarms are generated on the BTS and related boards need to be
replaced locally, you can locate and clear faults through the LMT.

Permission
 Before accessing the base station through the ETH port, ensure that an OM port has
been opened and the user has obtained required authorities for accessing the base
station through the OM port.
 The security of the USB port is ensured by encryption.
 The TST port is used for commissioning the base station rather than importing or
exporting the base station configuration.
 An adapter is used for local maintenance connects the USB port on the UMPT to an
Ethernet cable during local maintenance

Permission
 Prerequisites
 Before using the LMT, install the JAVA Platform Standard Edition Runtime Environment (JRE)
plug-in of jre-6u26-windows-i586 or a later version on the computer where the LMT is installed.
The JRE plug-in is a standard Java runtime environment plug-in, which can be downloaded from
http://java.com/.
 Connect the LMT to the base station.
 Use a crossover cable or USB-Ethernet adaption cable to connect the Ethernet port on the
computer where the LMT is installed to the WMPT, LMPT, or UMPT in the BBU.
 In the address box of the browser, enter the IP address of the main control board for local maintenance.
The default IP address is 192.168.0.49.
 Click Go. The Local Maintenance Terminal login window is displayed.
 After the LMT application software is successfully installed, you can log in to the LMT using
either of the following methods:
 Choose Start > All Programs > HUAWEI Local Maintenance Terminal > Web Local
Maintenance Terminal. The Local Maintenance Terminal window is displayed.
 In the address box of the browser, enter the IP address https://127.0.0.1:820. The
Local Maintenance Terminal window is displayed.
 Enter the user name, password, and verification code in the User name, Password, and Verification
code text boxes, respectively. Set User type to Local.
 By default, the user name and password for logging in to a base station are admin and
hwbs@com, which are case-sensitive. Change the password after you have logged in to the
LMT.
 Click Login. The LMT main window is displayed.

Permission
 Components of the LMT main window:

No. Component Parameter Description
1 Status bar - Displays the user name, connection status, and NE time.
2 Functions MML Used to run man-machine language (MML) commands.
Alarm/Event Used to query active alarms or events, alarm or event logs, and alarm or
event configurations.
Batch Used to run MML commands in batches.
Trace Used to trace base station messages.
Monitor Used to monitor the base station performance in real time.
Maintenance Used to manage equipment.
Selftest Enables the base station to perform self-tests.
3 Menu bar Configure Click Configure Emergent OM Channel on the LMT. On the displayed
Emergent OM Configure Emergent OM Channel dialog box, select and configure the
Channel target base station that requires emergency maintenance.
Obtain Choose Obtain Documentation List on the LMT.
Documentation
List
Command Some MML commands, GUI commands, and virtual commands are added
Group Settings to comprise a command group, command group is used to add commands
to a specified command group so that an admin user can add operation
authorities for authority-limited users.
FTP tool Used to download the File Transfer Protocol (FTP) tool.
Password Used to change the password.
About Displays the version information.
System Setting Used to set the automatic lockup.
Logout Used to log out of the LMT.
4 Others Help Used to open online help files.
Layout Used to indicate the layout management function. Four window layouts are
available: cascade, tile horizontal, tile vertical, and dock window.
Permission
 Components of the MML command window:

No. Field Description
1 Radio access You can choose Common or a specific RAT.
technology (RAT)
selection area
2 Common Maintenance Displays the output of an MML command..
tab
3 Operation Record tab Displays information about all the commands that have been
executed by the user.
4 Help tab Displays the help topics for an MML command.
5 Command output You can click Save Result, Auto Scroll, or Clear All.
handling options
6 Pane for manual input Displays the manually entered command and parameter values.
of an MML command
7 Command History text Records all the commands and parameters a user enters during
box one session.
8 Command text box Displays all the MML commands of the system. You can select
an MML command from the drop-down list or enter the
command directly.
9 Area for settings Displays all parameters that can be set in an MML command
parameters of an MML entered in the Command text box. The parameters in red are
command mandatory. The parameters in black are optional.

Permission
 Procedure
 In the LMT main window, click Device Maintenance.
 In the device maintenance navigation tree, double-click the required BTS
under Cabinet, and the corresponding BTS device panel is displayed in the
Device Panel tab page on the right.
 Right-click a board and choose a maintenance item. The board maintenance
menu varies with the board type.

Permission
 U2000 client online installation procedure:

1. Open IE browser, input the “http://U2000 server IP/cau”, press ”Enter”, an
online installation window displays.
2. Click “Setup” bottom to install U2000 client online.

Permission
 Start the U2000 client.

 In the Login dialog box, perform the following operations to select a server where you
want to log in:
 If there is no server list:
 Click next to Server drop-down list.
 In the Server List dialog box, click Add.
 In the Add Server Information dialog box, set Name, Server name (or IP
address), Port and Mode. Click OK.
 In the Server List dialog box, the new server is selected by default. Click OK.
 If servers are listed in the Server drop-down list:
 Select a server from the Server drop-down list.
 In the Login dialog box, enter the user name and password.
 Click Login.

Permission
 Users can switch the client display style to change the overall usability of the client
and the way client is launched. User can use either of the following two styles to
launch the client:
 Application style
 Traditional style
 Procedure
 Choose System > Preferences(traditional style) or File > Preferences
(application style).
 In the Preferences window, choose Client Display Style in the navigation
tree on the left.
 Select Application style or Traditional style for the client.
 Click OK.
Traditional Style Application Style
The client is launched with all The client is launched only with the applications as
the supported functions and required by a user.
applications.
Menu items cannot be Users can search for menu items.
searched for.
The Favorites feature is not You can add functions and menu items that are
supported. frequently used to the Favorites tab.
Traditional welcome page The welcome page features are not supported.
features are supported.
Permission
 Choose Topology > Main Topology (traditional style); alternatively, double-click

Topo View in Application Center and choose Topology > Main Topology
(application style) .
 In the topology window, you will find the BTS for operation.

Permission

 Right click the BTS, choose Maintenance Client.

Permission

Permission
 Alarms: refer to those generated when faults occur to devices or exception occurs to
key functions, such as a board fault. Alarms can be cleared. Alarms are more severe
than events.
 Events: refer to the event occasionally generated during the equipment running. They
indicate only the status of the running equipment at a certain time point. The system
generates some events periodically to notifying you of the equipment status. They do
not need manual handling.
 The differences between an alarm and an event are described as follows:
 An alarm is a special type of event. If the U2000 raises an alarm, it indicates
that a fault occurs on the U2000 or its managed object. The fault must be
rectified in time. Otherwise, the U2000 services cannot run properly because
the fault affects the functions of theU2000 or its devices.
 An event indicates that the status of a managed object changes. The change
may not affect services of the U2000.
 For example, Central Processing Unit (CPU) busy, hard disk failure, or network cable
disconnection are alarms.
 For example, succeeded in periodic export of operation logs is a events.

Permission
 Alarm severity :
 Critical
 The device or resource may be no longer available. The fault must be
removed immediately.
 Major
 The Quality of Service (QoS) of the device or resource decreases
greatly. Proper measures must be taken to recover the service.
 Minor
 The QoS of the device or resource decreases slightly. Proper
measures must be taken or further observation need to be done to
avoid more severe faults.
 Warning
 The QoS of the device or resource may be affected. Proper measures
must be taken.

Permission
 Choose Monitor > Synchronize NE Alarms (traditional style); alternatively, double-

click Fault Management in Application Center and choose Browse Alarm >
Synchronize NE Alarms (application style).
 In the Synchronize NE Alarms dialog box, set the NEs whose alarms you want to
synchronize and click OK.
 In the Confirm dialog box, click Yes.

Permission

 In the Main Topology window, right-click the icon of an NE that generates alarms.
From the displayed shortcut menu, choose menu items such as Query Alarm/Event
> Current Alarm or Query Alarm/Event > Alarm Logs.
 NOTE: In the window such as Browse Current Alarm-Alarm Source or
Alarm Logs-Alarm Source, all alarms generated by the NE are displayed.
 In the topology view, the color of an NE icon depends on the alarm severity. If an NE
generates multiple alarms at the same time, its icon displays the color of the highest
severity among these generated alarms.
 When you move the pointer to the icon of the NE that generates alarms, a tip is
displayed, prompting the alarm state, severity, and count.

Permission
 Choose System > NE Monitor (traditional style); alternatively, double-click

Configuration in Application Center and choose Browser > NE Monitor
 NOTE: In the NE Monitor window, the details of the NEs that are managed by the
U2000 are displayed.

Permission
 Choose Monitor > Display Alarm Panel (traditional style); alternatively, double-click
Fault Management in Application Center and choose Browse Alarm > Display
Alarm Panel (application style) or click the icon on the toolbar to open the alarm
panel.

Permission
 Choose Monitor > Query Alarm Bar Chart (traditional style); alternatively, double-click
Fault Management in Application Center and choose Browse Alarm > Query Alarm Bar
Chart (application style).
 The statistical results of the added current alarms templates are displayed in the Query
Alarm Bar Chart window.
 The U2000 provides the default bar chart named All objects. The default bar chart is used to
monitor all the alarms in the current alarms and cannot be deleted.
 The bar charts in the Query Alarm Bar Chart window correspond to the template displayed
on the alarm panel. When you add or delete an alarm bar chart in the Query Alarm Bar
Chart window, the corresponding alarm template is automatically added to or deleted from
the alarm panel. Similarly, when you perform the add or delete operation on the alarm panel,
the bar chart in the Query Alarm Bar Chart window is modified accordingly.
Task Operations
Set the contents and outlook to be Click Options. In the Options dialog box, set the
displayed contents and outlook to be displayed as required. Click
OK.
Add an alarm list template a.Click Add.
b.In the Choose dialog box, select an alarm list
template and click OK.
Delete a bar chart a.Select one bar chart that does not belong to All
objects, and click Delete to delete alarm list
templates.
b.In the Confirm dialog box, click Yes.
Locate a bar chart to the alarm list Select one bar chart, and then click Locate to Alarm
List to display the Browse Alarm List window.
Set as the monitoring template a.Select one bar chart and click Show on Alarm
Lamp.
Confidential Information of b.In the
Huawei. NoConfirm dialogWithout
Spreading box, click Yes.
Permission
 Choose Monitor > Browse Current Alarms (traditional style); alternatively, double-
Browse Current Alarms (application style), or click on the toolbar.
 In the Filter dialog box, set filter criteria.
 If you have set the default template, or have specified that the Filter dialog
box is not automatically displayed by following the procedure described in
Alarm/Event Filtering, you need to click Filter to open the Filter dialog box.
 The BSs of a multimode base station share some common resources such as
power module and FAN unit. When faults occur in common resources, the BSs
report alarms to the U2000 simultaneously. Based on this feature, the U2000
provides the following enhanced functions to multimode base stations:
Function of filtering common alarms: determines whether common alarms are
contained in the alarm query data. On the Basic Setting tab page, click
Advanced.
 Function of viewing multimode base station alarms: The alarm data reported
by all BSs of a multimode base station is summarized and contained in a
report. The alarm data consists of the specific alarms of each BS and the
common alarms shared by several BSs in the multimode base station. In a
multimode base station, a common alarm is displayed according to the
priorities of relevant BSs. On the Alarm Source tab page, select Custom,
click Add, and choose MBTS from the drop-down menu.
 Click OK. The result is displayed in the Browse Current Alarms window.

Permission
 Choose Monitor > Query Alarm Logs (traditional style); alternatively, double-click
Fault Management in Application Center and choose Browse Alarm > Query
Alarm Logs (application style), or click on the toolbar.
 In the Filter dialog box, set the alarm filter criteria.
 Click OK. The result is displayed in the Query Alarm Logs window.

Permission
 Choose Monitor > Alarm Settings > Template Management (traditional style);
alternatively, double-click Fault Management in Application Center and choose

Permission
Alarm Settings > Template Management (application style).

 In the Template Management window, click Add.
 In the Add Template dialog box, enter a template name and description, select a
template type and template sharing, and then click Next.
 In the Add Template dialog box, set filter criteria.
 Click Finish.

Permission
 Collecting Statistics on Alarm Logs

 Choose Monitor > Alarm Log Statistics (traditional style); alternatively, double-
Alarm Log Statistics (application style).
 In the Filter dialog box, set the statistical criteria of alarm logs, and click OK.
 Collecting Statistics on Event Logs
 Choose Monitor > Event Log Statistics (traditional style); alternatively, double-
Event Log Statistics (application style).

Permission
 In the Filter dialog box, set the statistical criteria of event logs, and click OK.

Permission
 In the query result, right-click a record and choose Locate in Topology from the
shortcut menu.
The NE that generates the alarm is identified on the client.
 Optional: In the Main Topology, click on the toolbar, and select Display alarms
of selected objects.
The alarm browse area displays the alarms of the selected objects only.

Permission
Browse Current Alarms (application style).
 In the Filter dialog box, set filter criteria, and click OK.
 NOTE: If you have set the default template, or have specified that the Filter
dialog box is not automatically displayed by following the procedure described
in Alarm/Event Filtering, you need to click Filter to open the Filter dialog box.
 Select one or more alarms and click Acknowledge.

Permission
Browse Current Alarms (application style).
 In the Filter dialog box, set filter criteria, and click OK.
 NOTE: If you have set the default template, or have specified that the Filter
dialog box is not automatically displayed by following the procedure described
in Alarm/Event Filtering, you need to click Filter to open the Filter dialog box.
 Select one or more uncleared alarms, and then click Clear.
 Result
 If the fault related to the alarm has been rectified, the alarm will not be reported
again.
 If the fault related to the alarm persists, the alarm may be reported again.

Permission
 Choose Monitor > Alarm Settings > Experience (traditional style); alternatively,
double-click Fault Management in Application Center and choose Alarm Settings
> Experience (application style).
 In the Experience window, click Range. In the Search Range dialog box, specify a
search range and click OK.
 Enter an alarm or event name, group name, or handling experience in the Filter by
name text box.
In the Alarm/Event Name navigation tree, alarm or event names with the specified
keyword are listed.
 In the Alarm/Event Name navigation tree, select an alarm or event name, and then
click Modify.
 In the Experience dialog box, enter alarm or event handling experience. Click OK.

Permission

Permission
 In the rack view of the device panel, you can query information about a board or perform
operations on the board. The board information and operations on boards vary according to
the board types.
 You can open the Device Panel window using the following methods:
 Choose Maintenance > Device Panel (traditional style); alternatively, double-click

Permission
Trace and Maintenance in Application Center and choose Monitor > Device Panel
 You can open the Device Panel window through the main topology for an NE that
supports the device panel.
 For GBTS groups:
 Choose Topology > Main Topology and select GBTS Group View from the
Current View drop-down list. Then, in the topology navigation tree or topology
view, right-click a GBTS group and choose Device Maintenance from the
shortcut menu.
 For other NEs:
 Choose Topology > Main Topology and select Physical Root or Electronic
View from the Current View drop-down list. Then, in the topology navigation
tree or topology view, right-click an NE and choose Device Maintenance from
the shortcut menu.
 You can activate the Device Maintenance window in the main topology view for NEs
that support the device panel function. The Device Panel, MML Command, and
Signaling Trace tab pages are available in the Device Maintenance window, allowing
you to perform operations such as observing the panel, issuing MML commands, and
creating or managing trace tasks.

Permission
 Query Board Inventory

Permission
 A health check may be performed in the following scenarios:

 In the case of daily network maintenance, safeguard for significant festivals
and holidays, quarterly preventive maintenance inspection, or device recovery
after faults are rectified, the system engineers and network management
engineers need to learn about the potential threats to NEs on the network and
rectify them in time.
 In the case of an NE upgrade, system engineers and network management
engineers need to verify the upgrade by learning about the status of the NE
before and after the upgrade based on the health check results. In addition,
you can use the NHC in the case of a patch upgrade or preventive
maintenance inspection (PMI).
 Choose Maintenance > Network Health Check > NE Health Check from the main
menu (traditional style); alternatively, double-click Trace and Maintenance in
Application Center and choose Monitor > NE Health Check from the main menu
 In NE Health Check tab page, click .
 Select a scenario from the Scenario drop-down list in the Create Task dialog box.

Permission

Permission
 This section describes how to check the voltage standing wave ratio (VSWR) of a
base station. The VSWR, also referred to as standing wave ratio, is the standard used
for checking whether the antenna system is installed correctly. The U2000 can check
the VSWR of a base station remotely and centralizedly. This helps check whether the
ALD is installed properly.
 The VSWR check is classified into single-frequency VSWR check and multi-frequency
VSWR check.
 Single-frequency VSWR check: uses the center frequency to check the VSWR.
 Multi-frequency VSWR check: concurrently checks VSWRs of multiple
frequencies based on the frequencies set by users.
 Large VSWRs may shorten transmission distances of signals and cause damage to
power amplifiers, affecting the communication network negatively. The normal value
range of VSWR is 1 to 1.5. The U2000 provides the default threshold plan. You can
set the threshold plan before VSWR check as required.
 Testing VSWR leads to interruption of base station services. Therefore, you need to
perform this operation during non-busy hours or after base station services are
segregated.
 Choose Maintenance > Antenna Management > VSWR Test (traditional style);
alternatively, double-click Trace and Maintenance in Application Center and
choose Maintenance > Antenna Management > VSWR Test (application style). The

Permission
VSWR Test window is displayed.

Permission
 This section describes how to perform interference detection to locate faults on RF

devices. Generally, RF interference detection is performed during device cutover or
routine maintenance. You can perform interference detection on RF devices every
few days or months depending on the application scenario.
 In the U2000 main window, choose Maintenance > Antenna Management >
Interference Measurement (traditional style); alternatively, double-click Trace and
Maintenance in Application Center and choose Maintenance > Antenna
Management > Interference Measurement (application style).
 In the upper left area of the Interference Measurement window, select a detection
type.
 In the navigation tree below the area of detection types, select the objects to be
detected.
 Click Parameter Settings in the right pane of the Interference Measurement
window. The window for setting parameters is displayed.
 Set NE Type based on the objects to be detected and set detection parameters.
 After setting parameters, click Test to start RF interference detection.
 During the detection, you can stop a detection task as required.
 The detection result is displayed after the detection is complete.

Permission

Permission
 The boards supporting block include the BBP, RRU, RFU, UBRI, AARU and GTMU.
 IMMEDIATE (Immediate) means that the board is blocked and services carried on the
board are interrupted immediately after the command is executed.
 SHUTDOWN (Shutdown) means that the board is blocked when no service is carried
on the board.
 DELAY (Delay) means that the board is blocked when no service is carried on the
board or after the time specified by the Duration of the shutting down state parameter
is reached.
 In LTE mode, all the three block types are supported.
 In UMTS mode, only the IMMEDIATE type is supported, and the IMMEDIATE type
takes effect even when this parameter is set to SHUTDOWN or DELAY.
 In GSM mode, only the IMMEDIATE type is supported, and the board is blocked 10s
after the system tries to hand over traffic on this board when this parameter is set to
SHUTDOWN or DELAY.

Permission
 This command cannot be used to reset an unavailable board.

 The reset of a board causes interruption of services carried by the board.
 The reset of a board also causes the board to become unavailable before initialization.
 In a dual-mode BS, the common components of the other mode can be reset through
this command. The services carried on those components are accordingly interrupted.
 For an MBTS, services of the mode at the peer end will be interrupted after a multi-
mode RF unit is reset.
 For a multi-mode BS in CPRI MUX, if the local mode aggregates data, resetting the
main control board of the local mode or the baseband processing board that
aggregates data will interrupt the services of the peer mode.
 If the software is being supplemented or activated on the base station, reset the main
active board after the software supplementation or activation is complete.

Permission
 If the cabinet number, subrack number, or slot number is not specified, the information
about boards contained in all cabinets, subracks, or slots is displayed.
 The standby status of an UMPT or an LMPT can be queried by running this command.
The standby status of any other board is displayed as NULL.

Permission
 After the execution of DSP CPUUSAGE command, the usage of the master CPU,
slave CPU, and DSP (if any) is displayed. If a board works properly, its CPU usage is
lower than 75%. If the CPU usage is constantly higher than 75%, an ALM-26202
Board Overload alarm is reported.

Permission
 Use LST RRUCHAIN command to query the configuration of the RRU chain.
 Use DSP RRUCHAIN command to query the physical information of the RRU chain.
 Use DSP RRUCHAINPHYTOPO command to query the topology and hardware
information about the RRU chain or ring connected to a CPRI port.

Permission
 [Co-MPT,NodeB,eNodeB]When the specified CPRI port is on an RHUB, the CPRI port is

numbered 0 or 1, and the CPRI_E port is numbered from 2 to 9.
 Install Status: Indicates the in-position state of the CPRI port. If the base station uses CPRI
MUX, the queried value of this parameter is NULL on the converged party side.
 Port Type: Indicates the type of the CPRI port. If the base station uses CPRI MUX, the queried
value of this parameter is UNKNOWN on the converged party side.
 Administrative Status: Indicates the administrative state of the CPRI port, the administrative
state of the CPRI port can be blocked or unblocked. The queried value of this parameter is
unblocked when quering the configuration of the RRU or RFU. If the base station uses CPRI
MUX, the queried value of this parameter is NULL on the converged party side.
 CPRI Port Mode: Indicates the mode of the CPRI port. There are two modes: Maser and Slave.
All CPRI ports on a baseband processing board work in master mode. On the first-level RRU in
an RRU chain, the CPRI port connected to a baseband processing board works in slave mode
and the other CPRI port connected to the second-level RRU works in master mode. When an
RRU and the baseband processing boards are in dual-star topology, the two CPRI ports on the
RRU work in slave mode.
 CPRI Port Mux Status: Indicates the multiplexing status of a CPRI port. When the backplane
fails, "UNKNOWN" is displayed if you query the status of a CPRI port of the aggregated party
and "NULL" is displayed if you query the status of a CPRI port on an RRU.
 Availability Status:Indicates the availability state of the CPRI port, the availability state of the
CPRI port can be normal, in breakpoint, or NULL, when the CPRI port is in breakpoint, it
indicates that a breakpoint is configured on the RRU chain/ring. At this moment, although the
optical cables are connected, the CPRI link is disconnected. The breakpoint is configured to
prevent temporary alarms from being reported during network operations. When the CPRI port
is normal, it indicates that there is no breakpoint on the RRU chain/ring. If the base station
uses CPRI MUX, the queried value of this parameter is NULL on the converged party side.

Permission
 The control link is a logical concept. The physical entity of the control link is the
topology between the interconnected BBUs.
 In a multi-mode BS, this command must be executed on all sides to ensure that all
control links have the same configuration.
 When the upper-level node is a UCIU, the value of the Upper Port No. parameter
must range from 0 to 4. When the upper-level node is a UMPT, the value must be 8.
 DSP CTRLLNKSTAT: Use this command to query the bit error rate of a control link.
The statistical information mainly includes the number of received packets, number of
erroneous packets, total packet receiving time, and total erroneous packet receiving
time and reflects the transmission quality of the link.For the UCIU, this command can
be used to display the bit error rates (BERs) of ports 0 to 4 and port 8. For the UMPT,
this command can only be used to display the BER of port 8.

Permission

Permission
 Software Types
 BootROM All the boards on the base station is equipped with the BootROM. The BootROM
refers to the software bound with hardware. It provides basic device drive function and can be
started and updated manually.
 The BootROM is a re-writable storage medium, which is used to store binary data, that is, the
machine codes.
 NodeB software The NodeB software is the version software of a base station.
 Cold patch The NodeB cold patch is also known as the patch. It can upgrade a specific board or
module to improve functions or to fix some problems.
 Hot patch The hot patch is also known as the online patch. It supports the upgrade without
disrupting the system operation and rectify some function defects.
 File Types
 Data configuration file A data configuration file contains parameter settings for each module of
the base station.
 Maintenance and operation log A maintenance and operation log file records the information
about the maintenance and operation of the base station.
 Main control log A main control log file is a collection of logs including the original,
commissioning, or user alarm log, running log, call log, cell log, maintenance log, and operation
log.
 Board log A board log file is a collection of logs including the log of active and standby central
processing unit (CPU) breakdown, the detailed breakdown log, and the digital signal processor
(DSP) memory log.
 Routine received total wideband power (RTWP) test log After a routine RTWP test is started, the
system keeps a real-time RTWP log.
 device archive file records information about each board of the NodeB such as the

Permission
manufacturing information and running time.

Permission
 BTS Node: provides infrastructure and application platforms for a base station to
deploy GBTS Service, NodeB Service, and eNodeB Service. BTS nodes are
classified into single-mode, dual-mode, and multimode base stations according to the
types and amount of services deployed.
 Itf_Platform-Service: service control interface provided by BTS nodes, including the
service deployment interface, version upgrade interface, starting and restarting
interface, and status monitoring interface.
 Itf_Node-RAT: interface provided by BTS nodes to control the common resources in
a base station, including resource application, releasing, activation, and
reconfiguration interfaces. Common resources in a base station include transmission
resources, carrier resource, and universal resources such as SCTP links, RF TX and
RX channels, and CPU progress. SCTP is short for Signaling Control Transmission
Protocol.

Permission
 You can download the base station software, data configuration file, and license from
an File Transfer Protocol (FTP) server to the local maintenance terminal (LMT).
 Procedure
 Download the FTP server software. (Optional. Perform this step only when there is no
FTP server at the LMT computer.)
 In the upper right corner of the LMT main window, click FTP Tool. The File
Download-Security Warning dialog box is displayed.
 Click Save to save the FTP server software SFTPServer.exe to the LMT
computer.
 Double-click SFTPServer.exe. SFTPServer.exe is decompressed into an
SFTPServer folder.
 Open SFTPServer. Double-click SFTPServer.exe to start the FTP server. The
icon is displayed on the right side of the taskbar after the FTP server is started.
 Optional: If the FTP server starts for the first time, an FTP password config dialog
box is prompted, indicating to modify the password of the FTP server, enter the initial
password hwbs@com, and enter and confirm the new password. Then, click OK.
 Configure the FTP server.
 Double-click .
 Set User name, Password, Working directory, the default user name is
admin. Set Working directory to the root directory of the FTP server, which is
D:\FTP, and retain default values for other parameters.

Permission
 Click OK. The FTP server is successfully configured.

Permission
 Software management refers to all the operations on software, including version,

patch, as well as related settings to software.
 There are two areas inside MBTS to store version software and configuration file. The
area where current version and configuration is stored is called main area, while the
other area is called standby area.
 Main area and standby area can be switched over by the command ACT
SOFTWARE in upgrading scenario or by the command RBK SOFTWARE in roll back
scenario.

Permission
 The activate time in the output of the LST SOFTWARE command specifies the time
when the current software is activated after the software upgrade. If the software
upgrade fails or is not performed in a normal way, the activate time is displayed as
NULL.
 If the query result shows that the version of an application is located in the main area,
the software that is in this version and corresponds to this application has been
activated. If the query result shows that the version of an application is not located in
the main area, the software that is in this version and corresponds to this application
is not activated. An application has a maximum of two versions. If the two versions are
not activated, the query result shows that they are located in the standby area.

Permission

Permission
 Procedure
 In the navigation tree, choose BTS Maintenance > Common Maintenance >
Software Management. Double-click Software Management.
 The Software Management tab page is displayed.
 Set parameters related to FTP Server Configuration on the Software
Management tab page.
 Select tasks based on scenarios.
 Click Execute. The base station performs the selected tasks from top to
bottom as required. The operation results are displayed in Information.
 Clear Clear Message to clear all contents displayed in Information.
 MML mode
 Run the DLD SOFTWARE command to download software from the FTP to
server the base station.
 Directory structure of the software package :

Permission
 This section describes how to download the BTS extra configuration file from the FTP
server to the base station. The downloaded extra configuration files take effect after
activating.
 Downloading the extra configuration file requires that the FTP server be used to
download files to the base station. Therefore, this operation is available when you log
in to the base station using the LMT.
 Procedure
 In the navigation tree, choose BTS Maintenance > Common Maintenance.
Double-click Extra Configuration File Transfer.
 The Extra Configuration File Transfer tab page is displayed.
 Set related parameters on the Extra Configuration File Transfer tab page.
 Click Activate or Preactivate. The operation results are displayed in
Information.
 Clear Clear Message to clear all contents displayed in Information.
 NOTE:
 To enable the configuration data to take effect on the base station, click
Activate. To only check the correctness of the configuration data, click
Preactivate.

Permission
 Transferring the device archive file requires that the FTP server be used to upload
and download files to and from the base station. Therefore, this operation is available
when you log in to the base station using the LMT.
 Procedure
 GUI mode
Double-click Device Archive Transfer.
 The Device Archive Transfer tab page is displayed.
 Set related parameters on the Device Archive Transfer tab page.
 Click Start. The Progress dialog box is displayed, showing the operation
progress.
 MML mode
 Run the ULD DEVFILE command to upload the file from the base station to
the FTP server.
 Run the EXP DEVFILE command to export a device file.

Permission
 This section describes how to download the data configuration file from the File
Transfer Protocol (FTP) server to the base station, or upload the data configuration
file from the base station to the File Transfer Protocol (FTP) server. The downloaded
data configuration file takes effect after the base station restarts.
 Procedure
 Graphical user interface (GUI) mode
Double-click Data Configuration File Transfer.
 The Data Configuration File Transfer tab page is displayed.
 Set related parameters on the Data Configuration File Transfer tab page.
 Click Start.
 Man-machine language (MML) mode
 Run the ULD CFGFILE command to upload the file from the base station to
the FTP server.
 Run the DLD CFGFILE command to download the file from the FTP server to
the base station.
 Run the BKP CFGFILE command to back up the current configuration of the
BS.

Permission
 This section describes how to upload base station files to the FTP server. After the
base station files are uploaded, you can save, browse, and modify the files.
 Procedure
 GUI mode
Double-click Other File Transfer.
 The Other File Transfer tab page is displayed.
 Set related parameters on the Other File Transfer tab page.
 Click Start.
 MML mode
 Run the ULD FILE command to upload the file from the base station to the
FTP server.

Permission
 Files backed up using the BKP CFGFILE command and uploaded using the DLD
CFGFILE command are saved in the same directory on an NE. An existing file will be
overwritten by a new file with the same file name.
 If a configuration file generated by using this command is not activated within 24
hours, it will be automatically deleted.
 It is recommended that this command be not executed when ALM-26242
Configuration File Damaged is reported.
 Execution of this command will increase the CPU usage, and CPU overload may
affect UE access. Therefore, it is recommended that you run this command when the
system has a light load.
 If a backup configuration file is encrypted, you need to decrypt the file before running
the ACT CFGFILE command to activate the file.
 [Co-MPT]Configuration files backed up on the U2000 and LMT are both named
CFGDATA.XML.
 [NodeB]Configuration files backed up on the U2000 and LMT are both named
NodebCfg.XML.
 [eNodeB]The backup file is automatically named according to the OM terminal type
(LMT or U2000) after you run this command. For example, after you run this
command on the LMT to back up an XML-format configuration file, the name of the
backup file is LMT.XML; after you run this command on the U2000 to back up an
XML-format configuration file, the name of the backup file is M2000.XML.

Permission
 Manually Backing Up NE Data

 Choose Maintenance > Backup Management > NE Backup (traditional style);
alternatively, double-click Software Management in Application Center and choose
NE File > NE Backup (application style). The NE Backup window is displayed.
 Select an NE type from the drop-down list.
 In the navigation tree, select the NEs whose data needs to be backed up.
 Click Backup. Click Yes in the displayed Confirm dialog boxes, respectively.
 Backing Up NE Data on Schedule
 Choose Maintenance > Task Management (traditional style); alternatively, double-
click System Management in Application Center and choose Task Schedule >
Task Management (application style). The Task Management window is displayed.
 Click New. The New Task dialog box is displayed.
 Set the basic information about the task.
 Type the name of a scheduled task in the Task Name field.
 Select NE Backup from the Task Type area.
 Select One-time or Periodic from the Execution Type area.
 Click Next to set the time for performing the task.
 Click . In the displayed Select Time dialog box, specify the time for starting the
task.
 Perform relevant operations according to the task type.
 Click Next, set encryption options of NE backup files and select the backup mode.
 Click Finish.

Permission

Permission
 A multimode base station can be configured with the following common reference
clocks:
 GPS reference clock
 Building integrated timing supply (BITS) reference clock
 IPCLK(IP Clock)
 SYNCETH(SyncEth Clock)
 LINECLK(Line Clock)
 TOD(TOD Clock)
 PEERCLK(Peer Clock)
 INTERCLK(Inter Clock)
 The UMTS currently does not support "SyncEth Clock+IP Clock" and "GPS
Clock+SyncEth Clock" function.
 Clock Working Mode
 Manual indicates that a clock source must be specified by the user.
 Auto indicates that the system automatically selects a clock source based on
the priority and availability of the clock source.
 Free indicates that the system clock works in free-running mode, that is, the
system clock does not trace any reference clock source.

Permission
 PLL status indicates the working mode of the clock. It also indicates whether the
system clock is stable. The working mode of the clock can be Fast tracking, Locked,
Holdover, or Free running.

Permission

Permission
 For performance GBTS RF Test ,you can select the Task from Device Panel.

Permission
 This section describes how to set the start time and period for scanning frequencies of
a cell.
 In the navigation tree, choose BTS Maintenance > GSM Maintenance.
Double-click Configure Frequency Scan.
 The Configure Frequency Scan dialog box is displayed.
 Set related parameters in the Configure Frequency Scan dialog box.
 Click Start.
 Man-machine language (MML) command mode
 Run the SET GCELLFREQSCAN command.

Permission
 This section describes how to query the maximum and average of the main level and
diversity level. By checking whether the signal strength of a frequency is greater than
0, you can determine whether there is interference to the uplink frequency.
 This task is specific to GSM.
 Each carrier has two receive channels. One is the main receive channel and the other
is the diversity receive channel. The main level is the uplink signal level on the main
receive channel, and the diversity level is the uplink signal level on the diversity
receive channel.
 Procedure
Double-click Query Frequency Scan. The Query Frequency Scan tab page
is displayed.
 Set related parameters in the Query Frequency Scan dialog box.
 Click Start.

Permission

Double-click Monitor Channel Status. The Monitor Channel Status tab
page is displayed.
 Set related parameters on the Monitor Channel Status tab page.
 Click Start.
 NOTE:
 A dot under a channel indicates a sub-channel. The standalone
dedicated control channel (SDCCH) has eight sub-channels, and the
traffic channel (TCH) has one sub-channel.
 The * mark to the upper right side of a carrier number indicates that the
carrier works in mutual-aid mode.
 The channel status monitoring window is fixed in size and does not
change with the web page.
 Run the DSP GTRXCHNSTAT command.

Permission
 BTS Speech Loop Test

 The BTS voice loopback test is performed on the TCHs to check the
connection status of the TRX speech channel between the Um interface and
the DBUS of the BTS. During the test, the TMU loops back the DBUS timeslot
of the speech channel to be tested. If the MS that occupies the tested speech
channel can hear its own voice, it indicates that the speech channel among the
Um interface, the TRX, and the DBUS is properly connected; otherwise, it
indicates that the speech channel is not properly connected.
 TRX Speech Loop Test
 The TRX voice loopback test is performed on the TCHs to check the
connection status of the TRX speech channel between the Um interface and
the DSP is normal. During the test, the DSP encodes and then sends the data.
If the MS that occupies the TCH can hear its own voice, it indicates that the
speech channel between the Um interface and the TRX is properly connected;
otherwise, it indicates that the speech channel is not properly connected.

Permission
 BIU Loop Test

 The BIU Loop Test tests the timeslot transmission of the TRX service channel
on the BTS DBUS. The TRX sends the service channel data to the service
timeslot of the BTS DBUS. After the loopback through the TMU, the TRX
receives the data sent by the TRX itself. The TRX compares the data with the
original data, and then reports the error ratio to get link quality of the service
channel on the BTS DBUS.
 TRX RF Self Loop Test
 The TRX RF Self Loop Test tests the quality of the RX and TX channels. The
TRX RF self loop starts from the DSP, passes the BBU, loops back from the
RRU, and then passes the BBU again to come back to the DSP. The DSP
then compares the data from the original data to learn the RX and TX channel
quality of the BTS.

Permission
 BIU loopback test:

 The BIU loopback test is used to test the transmission of the TRX channels over the timeslots of the DBUS
of the BTS. During the test, the TRX sends the data of the service channel to the service timeslot of the
DBUS. The TMU loops back the data so that the TRX can receive the data that is sent. The TRX compares
the data and reports BER. From the BER, the testing technicians know the quality of the service channel of
the DBUS.
 RF self-loopback test
 This test is used to check the quality of the receiving and sending channels of the TRX. This test is initiated
by the signal process of the TRX, passes the baseband unit, is looped by the RF unit, passes the baseband
unit again, and returns to the signal process. The signal process compares the data and reports BER. From
the BER, the testing technicians know the quality of the receiving and sending channels of the BTS.
 BTS voice loopback test
 The BTS voice loopback test is used to test the transmission of the voice service from the air interface to
the DBUS of the BTS. During the test, the TMU loops back the DBUS timeslot that carries the service
channel. If the user who occupies the channel can listen to the voice, it indicates the channel is good;
otherwise it indicates the channel is disconnected.
 TRX voice loopback test
 The TRX voice loopback test is used to test the transmission of the voice service from the air interface to
the signal process. During the test, the signal process directly codes and sends the decoded data. If the
user who occupies the channel can listen to the voice, it indicates the channel is good; otherwise it
indicates the channel is disconnected.
 In the navigation tree, choose BTS Maintenance > GSM Maintenance. Double-click Test Channel
Loopback.
 The Test Channel Loopback tab page is displayed.
 Set related parameters on the Test Channel Loopback tab page.
 Click Start.
 Run the following commands to perform a channel loopback test:
 Run the STR GBTSTST command to start the test.

Permission
 Run the STP GBTSTST command to stop the test.

Permission
 BIU loopback test: This task is used to test the timeslots of the TRX channel over the
DBUS of the BTS. During the test, the TRX sends the data of the signaling channel to
the signaling timeslot of the DBUS; the TMU loops back the data so that the TRX can
receive the data that it sent. The TRX compares the data and reports BER. From the
BER, the testing technician knows the quality of the signaling channel of the DBUS.
Double-click Test TRX Loopback.
 The Test TRX Loopback dialog box is displayed.
 Set related parameters in the Test TRX Loopback dialog box.
 Click Start.
 Run the following commands to perform a TRX loopback test:

Permission

Permission
 LOCK indicates that both the local cell and its logical cell are unavailable. MSs that
have accessed the logical cell bound to the local cell are forcibly handed over to other
normal cells.
 UNLOCK indicates that the local cell is available.
Double-click Modify Cell Management Status.
 The Modify Cell Management Status tab page is displayed.
 Set related parameters on the Modify Cell Management Status tab page.
 Click Apply.
 MML mode
 The administrative status of a cell can be modified by running MML commands.
 To block a local cell, run the BLK GLOCELL command.
 To unblock a local cell, run the UBL GLOCELL command.

Permission
 This section describes how to test idle timeslots in the network to maximize
interference in the network.
 To obtain information about the maximum interference level in the network during
network optimization phase, you can maximize the interference purposely. To achieve
this, transmit bursts on downlink idle channels under the condition that normal
services are not affected. The transmission of bursts on idle channels maximizes the
downlink interference and the uplink interference stimulated by downlink signals.
 Procedure
Double-click Test Idle Timeslot.
 The Test Idle Timeslot dialog box is displayed.
 Set related parameters in the Test Idle Timeslot dialog box.
 Click Start.
 Run the following commands to test idle timeslots:

Permission

Permission
 VSWR, Voltage Standing Wave Ratio

 This is a high-risk MML command.
 Use this command to start the VSWR test on the TX channel to check whether the
antenna system is properly installed. If the numbers of the cabinet, subrack, slot, and
antenna port are not specified, the VSWR information of all the RRUs or RFUs are
queried in batch.
 Different types of RF module operate within different frequency bands. Therefore, use
the frequency specified during the configuration of the cell as the frequency for the
VSWR test.
 Ensure that no operation is performed on the RRU or RFU during the test.
 If the VSWR test result of a RF module is NULL, you can start the VSWR test on this
RF module separately to get the detailed reason of the failure.
 If the VSWR is greater than the value required by the engineering quality, the
connection of the antenna is abnormal. In this case, you need to check the antenna
connection and the ALD.
 The VSWR queried by the DSP VSWR command is the result of the test that uses the
current power of the RF module as the test power, and the VSWR test started by the
STR VSWRTEST command is based on single tone and uses the maximum power of
the RF unit as the test power. The precision of the two kinds of VSWR tests is
different and so the test results are different.
 The VSWR is displayed in the result of this command and is not used to light the

Permission
VSWR indicator or report a VSWR alarm.

Permission

 Use this command to detect a crossed pair connection. Crossed pair connection is a wiring error in
twisted pair cabling where both the main and diversity in a sector are incorrectly connected to different
antennas at both sides.
 The VSWR test has a great impact on the precision of this test because the VSWR will cause a gain loss.
You are advised to perform a high-precision VSWR test before running this command. If the VSWR is
greater than 2.5, you are not advised to run this command.
 This command applies to the scenario where RF modules are in 2T2R mode. If this command is
executed in other scenarios, the result may be incorrect.
 This command does not apply to a multi-RRU/RFU cell or a distributed cell.
 This command does not apply to the scenario where all antennas of one sector are connected to another
sector.
 If less than two sectors in the same frequency band support this test, this test returns failure.
 This test is an offline test and the execution of this command interrupts services. If this command is
executed on a multi-mode RF module, the services of the peer mode carried by this RF module are also
interrupted.
 In the scenario where a filter is configured in the antenna system, the STFREQ and ETFREQ parameters
in this command must be set to the start frequency and end frequency of the filter, respectively. If the
bandwidth between the start frequency and end frequency is smaller than 10 MHz, the execution output
is not reliable.
 If crossed feeder connections are detected, you need to check whether an external filter or narrowband
filter equipment exists in the antenna system first.
 Running this command on a multi-mode RF unit of a multi-mode BS or on RF units of different modes
that share the antenna system will interrupt services of both modes.
 The result of this command is "Unknown" means that can not judge if crossed feeder connected or not.

Permission

 If an RF module's output power is controlled by the output power locking and the
output power of a single TX channel is less than 40, when the Test Type parameter is
set to PIMON2TONE_2TONE or PIMON2TONE_SWEEP, the output power locking
becomes ineffective and the output power of a single TX channel can reach 2x20 W.
After the test is completed, the output power locking becomes effective again.
 a. The values of Freq1 and Freq2 or Start Freq and End Freq must supported by the
RF module.

Permission

Permission

Permission
Loopback mode:
 NOLOOP : Loopback mode is cancelled.
 REMOTE : Remote loopback, which means that data goes through a loop of E1
cables between BTS and peer end. it is used to check whether the E1 cables are
normal.
 LOCAL: Local loopback, which means that data goes through a loop within a BTS
instead of through E1 cables. It is used to check whether the transmission chips are
normal.
 After we execute the SET E1T1LOP as REMOTE mode on A side, we can execute
DSP E1T1 on B side to query E1 state, if the state is normal, that means the physical
transmission from A to B is normal, otherwise, it means the transmission is faulty.

Permission
 Local end loopback, which means that data goes through a loop within a NodeB
instead of through E1 cables. It is used to check whether the transport chips are
normal.
 The E1/T1 loopback supports self-deactivation. After the loopback duration times out,
the E1/T1 loopback is automatically deactivated.
 An E1/T1 port can start only one type of loopback at the same time.
 Setting a loopback on an E1/T1 port interrupts services carried on this port. In addition,
the E1/T1 loopback alarm is reported, and at the same time the loopback mode of the
E1/T1 port is changed to loopback.
 [Co-MPT,NodeB]After deactivating a loopback on an E1/T1 port that belongs to an
IMA group, you must reset the IMA group by running the RST IMAGRP command.
 [Co-MPT,NodeB]After the board is reset, the loop mode (LM) is automatically
switched to NOLOOP.

Permission
 Link Running Status: Indicates the link running status.

 Loop Left Time(min): Indicates the left loop time of the E1/T1 port.

Permission
 After we execute the SET E1T1LOP as REMOTE mode on A side, we can execute
DSP E1T1 on B side to query E1 state, if the state is normal, that means the physical
transmission from A to B is normal, otherwise, it means the transmission is faulty.

Permission
 This is a high-risk MML command, and therefore exercise caution when executing this
command. Running this command may cause the following major impacts:
 A maximum of three users can start the online performance test simultaneously on
each port.
 You cannot start an online performance test at the port where an offline performance
test is already started. Conversely, you cannot start an offline performance test at the
port where an online performance test is already started.
 You can start the online performance test on multiple ports on the same board.
 If the online performance test encounters a turnover, the number of error bits after the
turnover is reported.
 An online performance test is applicable to a transmission link working properly and
having error bits. You are advised to check the E1/T1 link status before starting an
online test. If the link is faulty, you are not advised to start an online performance test.
In this case, you can start an E1/T1 offline performance test and rectify the E1/T1 link
fault.
 When Period Report Switch is set to ON, the test result within a second is reported
every other second. When Period Report Switch is set to OFF, you can run the STP
E1T1ONLTST command to obtain the test result.

Permission
 An E1/T1 offline performance test is used to determine the BER of an E1/T1 link.
Before starting the test, set the E1/T1 port at the peer end to remote loopback or set
the E1/T1 port at the local end to local loopback or physical loopback. The test is
invalid if no loopback is specified.
 When the E1/T1 port at the peer end is set to remote loopback or physical loopback is
implemented at the local end, there is a possibility that the physical layer cannot
detect the existence of the physical loopback due to bit errors on the link. As a result,
you may run the DSP E1T1 command to check whether the associated E1/T1 ports
are in physical loopback state. Note that the E1/T1 offline performance test can be
started only when physical loopback is in effect implemented.
 A loopback is specified for the E1/T1 offline performance test. This may disrupt
services.

Permission
 The PING, TRACERT, CFMTRACE, CFMPING, and UDPECHO commands cannot

be executed simultaneously on one board.
 If CONTPING is set to ENABLE, press Ctrl+Q to terminate the PING command.
 If IPSec networking is used, APPTIF of the PING command must be set to NO.
 When the Appoint Interface parameter is set to YES(Yes), the Port Type parameter
can be set to TUNNEL(Tunnel) only for the WMPT and UMPT boards.
 [NodeB,eNodeB]If the route corresponding to the destination IP address is a tunnel
route, the source IP address must be specified.
 [NodeB,eNodeB]If the local IP address of a remote maintenance channel is the same
as a device IP address and is used as the source IP address for a ping operation, the
slot number for the ping operation must be the same as that of the board where the
device IP address is configured.
 An example of PING

Permission
 Traceroute sends a sequence of Internet Control Message Protocol (ICMP) packets

addressed to a destination host. Tracing the intermediate routers traversed involves
control of the time-to-live (TTL) Internet Protocol parameter. Routers decrement this
parameter and discard a packet when the TTL value has reached zero, returning an
ICMP error message (ICMP Time Exceeded) to the sender.
 Traceroute works by increasing the TTL value of each successive batch of packets
sent. The first three packets sent have a time-to-live (TTL) value of one, expecting
that they are not forwarded by the first router. The next three packets have a TTL
value of 2, so that the second router will send the error reply. This continues until the
destination host receives the packets and returns an ICMP Echo Reply message.
 The traceroute utility uses the returning ICMP messages to produce a list of hosts that
the packets have traversed in transit to the destination. The three timestamp values
returned for each host along the path are the delay (aka latency) values, typically
measured in milliseconds for each packet in the batch.

Permission
 You can press Ctrl+Q to stop running the TRACERT command.

 The PING, TRACERT, CFMTRACE, CFMPING, and UDPECHO commands cannot
be executed simultaneously on one board.
 If the source IP address is not specified, it must be the configured device IP address
or the local IP address of the remote maintenance channel. You can run the LST
DEVIP and LST OMCH commands to query these two types of IP addresses,
respectively.
 If a destination IP address elicits no response during route tracing but can be pinged,
check and remove redundant IP addresses on the egress port, which are on the same
network segment as the planned IP address.
 In TRACERT packets, "*" indicates that the detection expires, "!" indicates that the
port is unreachable, "!N" indicates that the network is unreachable, "!Y" indicates that
the IP address is unreachable, "!P" indicates the protocol is unavailable, "!S" indicates
that the source route fails, and "!H" indicates that the host is unreachable.
 If the destination IP address is used to search for the outbound interface or next hop,
TRACERT detection is not performed.
 [NodeB,eNodeB]If the route corresponding to the destination IP address is a tunnel
route, the source IP address must be specified.
 [NodeB,eNodeB]If the source IP address is not specified or it is 255.255.255.255, in a
routing domain the BS uses the IP address of the egress port closest to the

Permission
destination IP address as the source IP address for the route tracing.

Permission
 IP PM
 The transmitting end periodically sends FM packets indicating number of local
packets and the receiving end responds to the FM packets with a BR packet
indicating the number of received packets and delay, Then the sending end
calculates the QoS based on the BR packets.
 FM is short for forwarding monitoring.
 BR is short for backward reporting.

Permission
 For the IP PM on the RNC side, the RNC periodically sends FM packets indicating the
number of local packets and bytes and local transmission duration. After receiving the
FM packets, the NodeB responds with a BR packet indicating the number of received
packets and bytes, duration for receiving FM packets, and BR response duration. The
RNC measures packet loss rate, delay, and delay variation based on the BR
response from the NodeB. The number of packets and bytes contained in FM and BR
packets is for service packets and does not include FM and BR frames.

Permission
 Bind IP Path Meaning

 Indicates whether to bind the IP PM session to an IP path. If the IP PM session is
bound to an IP path, the IP PM session uses the local and peer IP addresses of the IP
path in data transmission. In addition, if TXBWASW or RXBWASW is set to ON and
TCSW is set to ENABLE in the algorithm for the transmission resource group
associated with the IP path, the system dynamically adjusts the TX or RX bandwidth of
the transmission resource group based on the IP PM detection result.
 Activate Direction Meaning
 Indicates that the activation direction of the IP PM session. For this parameter to be
valid, the peer must also support the IP PM session. If this parameter is set to UP, the
IP PM session initiated by the BS is activated. If this parameter is set to BIDIR, the IP
PM sessions initiated by BS and the peer are activated.
 Round Trip Time(ms)
 Indicates the round-trip delay calculated by an IP PM session detection. The round-trip
delay is the time that is consumed to transmit IP PM detection packets to and fro
between the local and peer ends.
 RX Jitter(ms)
 Indicates the DL jitter calculated by an IP PM session detection.
 TX Jitter(ms)
 Indicates the UL jitter calculated by an IP PM session detection.
 RX Loss Rate(per mill)
 Indicates the DL packet loss rate calculated by an IP PM session detection.

Permission
 Principle
 After the IP loopback test is started, the DSP sends loopback packets to the
BTS in a specified period and then the BTS returns the loopback packets to
the DSP
 You can determine the connectivity and link quality according to the received
loopback packets
 MBTS support IP loopback operation, but don’t support IP loopback test.
 BSC support IP loopback test only.

Permission

Permission
 Use this command to set the UDP-type IP packet loopback. The UDP-type IP packet
loopback can be used to check the connectivity and quality of the network based on
the UDP packets sent by the peer end.
 Only one loopback mode can be configured for IP packets. The new loopback
configuration overwrites the existing loopback configuration.
 Loopback Mode Meaning: Indicates the UDP loopback mode.
 If this parameter is set to SPECIALIPUDPPORTREMOTE, the UDP packets
from a BS that meet the specified conditions are looped back to the peer
device.
 If this parameter is set to ALLIPREMOTE, all the UDP packets received on a
BS are looped back to the peer device.
 If this parameter is set to SPECIALIPREMOTE, the UDP packets received on
a BS, whose local and peer IP addresses are the same as the specified
address couple, are looped back to the peer device.
 [eNodeB]If LM is set to SPECIALIPUDPPORTREMOTE or
SPECIALIPUDPPORTLOCAL, the services in the same routing domain carried by the
IP addresses and UDP ports specified in this command are interrupted.
 DSP UDPLOOP command to query the parameters of the User Datagram Protocol
(UDP) loopback.

Permission
 Use this command to start the IP loopback test. The function is to check the
connectivity between DSP and the interface boards or the peer equipment.This
command is applicable to the FG2a, GOUa, FG2d, FG2c, GOUd, GOUc and GOUe
boards.
 Only one IP loopback test can be started for one DSP.
 This command is used to start the IP loopback test on the Iub or Abis interface. When
the parameter LOPT is set as REMOTE_LOOP, you need to enable the IP remote
loopback function by setting IP address and port number on the NodeB or BTS.
Otherwise, the function is unavailable.
 The quaternary group information (Local IP address, Peer IP address, Src Port NO.
and Dst Port NO.) set in each IP loopback detection cannot be the same.
 If the subrack No. of the interface board is not specified, the interface board is
considered to be in the same subrack as the DSP.
 An IP loopback test can be started on a UMTS DPU that functions as UUP logically or
a GSM DPU that functions as GPCU logically.
 The parameter PEERIP need to be negotiated with the peer end.

Permission
 Use this command to query the result of the loopback test at the IP layer. This
command is applicable to the FG2a, GOUa, FG2d, FG2c, GOUd and GOUc boards.

Permission

Permission

Permission
 LOCALIP: The IP address of the local maintenance channel. The IP address refers to
the IP address of the local commissioning Ethernet port on the board. Generally it is
same for every site, the default value is 192.168.0.49.
 OMCH：The local IP address of a remote maintenance channel.
 ETH: The IP for specific physical FE/GE ports.
 ETHTRK: If the FE/GE ports are combined as an Ethernet trunk, then it can be used
to define the trunk IP.
 LOOPINT: the logic IP.
LOCALIP: 192.168.0.49

Permission
Item Instance Remarks

Device IP address of the BSC 10.10.10.10/32 -
Port IP address of the BSC 21.21.21.1/24 -
IP address of the port on the router that 21.21.21.254/24 -
is connected to the BSC
IP address of the port on the router that 11.11.11.254/24 -
is connected to the RNC
P address of the port on the router that 20.20.20.1/24 -
is connected to the UMPT_GUL
IP address of the port on the 20.20.20.188/24 Device IP address during configuration on the CME. This IP
UMPT_GUL address is configured on the co-transmission port.
OM IP address 30.30.30.1/24 GSM&UMTS&LTE: Management plane IP address. This is a
logical IP address and is configured on the UMPT_GUL.
In this scenario, only one OM IP address is configured

because the multimode base station is configured with one
OM channel.
Signaling/service IP address of the 32.32.32.1/24 UMTS: control plane/user plane IP address. This is a logical
NodeB IP address and is configured on the UMPT_GUL.
Device IP address of the RNC 15.15.15.15/24 -

Port IP address of the RNC 11.11.11.11/24 -
IP address of the U2000 60.60.60.60/24 GSM&UMTS&LTE: Peer IP address for the OM channel
Signaling/service IP address of the BTS 35.35.35.188/24 GSM: control plane/user plane IP address. This is a logical IP
address and is configured on the UMPT_GUL.
IP address of the MME 40.40.40.40/24 LTE: peer IP address for the SCTP link
IP address of the S-GW 50.50.50.50/24 LTE: peer IP address for the IP path
Signaling/service IP address of the 33.33.33.188/24 LTE: control plane/user plane IP address. This is a logical IP
eNodeB address and is configured on the UMPT_GUL.

Permission
 the UMPT board shared by the Abis, Iub interfaces is responsible for protocol
processing at the physical layer, data link layer, network layer (IP), Stream Control
Transmission Protocol(SCTP) and transport link layer (UDP). The protocols at other
layers are processed on the control plane processing boards and user plane
processing boards of GSM and UMTS separately.

Permission

Permission
 Use LST ETHPORT command to list the Ethernet port configuration, including the
speed, duplex mode, and port attribute.
 Use DSP ETHPORT command to query the status of an Ethernet port, including the
maximum transfer unit, speed, MAC address, duplex mode, physical layer status, and
traffic information.
 Port Status: Indicates the status of the Ethernet port.
 Physical Layer Status: Indicates the physical layer status of the Ethernet port.
 ARP Proxy: Indicates whether to enable the proxy ARP function. If this function
is enabled, the BS serves as an ARP proxy for the IP address of a loopback
interface on the BS or a port IP address of a lower-level BS. If this function is
disabled, an external device can access a loopback interface in the BS or a
lower-level BS on the same subnet only by using a route. After the Ethernet
port is added to an Ethernet trunk, this parameter stops taking effect and
whether the proxy ARP function is enabled for the Ethernet port depends on
the setting of the same parameter in the Ethernet trunk.

Permission
 Use this command to query the active Address Resolution Protocol (ARP) table
entries of the system. An ARP table entry records mapping from the IP address of the
peer port acquired by the BS to a MAC address.

Permission
 VLAN Mode
 Indicates the VLAN mode. When this parameter is set to SINGLEVLAN, the
configured VLAN ID and VLAN priority can be directly used to label the VLAN
tag.
 If this parameter is set to VLANGROUP, the next hop IP addresses are
mapped to the VLAN groups, and then mapped to the VLAN tags in the VLAN
groups according to the DSCPs of the IP packets. In VLAN group mode,
ensure that the VLAN groups have been configured by running the ADD
VLANCLASS command.
 Set VLAN Priority
 Indicates whether to set priority of a single VLAN. When this parameter is set
to DISABLE, the default DSCP-VLAN priority mapping is applied if the
mapping is not configured by running the SET DSCPMAP command.
Otherwise, the configured mapping is applied. When this parameter is set to
ENABLE, the DSCP-VLAN priority mapping configured by the ADD VLANMAP
command is applied even if the SET DSCPMAP command is executed.

Permission
 Preference
 Indicates the priority of the routing table entry. A smaller parameter value
indicates a higher priority.
 Route Type
 Indicates the type of route. If this parameter is set to NEXTHOP, all the IP
packets that meet the route direction are first forwarded to the specified next
hop IP address. If this parameter is set to IF, all the IP packets that meet the
route direction are first forwarded to the specified egress port.

Permission
 Control Mode: Indicates whether the object can be modified or deleted by the system.
The value MANUAL_MODE means that only the user can modify or delete the object.
The value AUTO_MODE means that both the system and the user can modify or
delete the object.
 Auto Config Flag: Indicates whether the object is created by the system.
MANUAL_CREATED means that the object is configured by the user manually.
AUTO_CREATED means that the object is created by the system.

Permission
 Transport Resource Type

 Indicates the type of transport resource for the IP path. The value HQ indicates
high-quality transport resources, and the value LQ indicates low-quality
transport resources. This parameter must be set in the hybridtransmission
scenario. In other scenarios, the default value of this parameter is used. The
parameter takes effect only in LTE.
 IPMUX Switch Flag
 Packet multiplexing is adopted to enhance the transport efficiency. Using FP
MUX feature, multiple FP packets with same source IP, destination IP and
DSCP (DiffServ Code Point) are packed into one UDP/IP packet, with
compressed UDP information. Since less packet head, higher transport
efficiency is achieved.
 Path Type
 Indicates the type of the IP path. FIXED indicates that this IP path is used to
carry the service with specified Quality of Service (QoS), that is, with a
specified DSCP. ANY indicates that this IP Path can be used to carry services
of any QoS and hence is used to carry the service without a specified DSCP.
 IP Path Check Result
 Indicates the check result for the GTP-U static detection of an IP path. The
parameter takes effect only in LTE.

Permission
 Auto Config Flag

 Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.
 Flag Meaning:
 Indicates whether the transport channel carried on the CP bearer is a master
or slave channel.
 Control Mode Meaning:
 Indicates whether the object can be modified or deleted by the system. The
value MANUAL_MODE means that only the user can modify or delete the
object. The value AUTO_MODE means that both the system and the user can
modify or delete the object.

Permission
 Control Port Bearing Status

 Indicates the transmission bearing status of the control port: AVAILABLE and
UNAVAILABLE. When this parameter is set to AVAILABLE, the control port
can bear control data transmission. When this parameter is set to
UNAVAILABLE, the control port cannot bear control data transmission.

Permission

Permission
 Port Type
 Indicates the type of Iub control port. The control port type is classified into
NodeB Control Port (NCP) and Communication Control Port (CCP). The NCP
carries a common signaling channel, while the CCP carries a dedicated
signaling channel of a cell. There is only one NCP and multiple CCPs in the
system.

Permission

Permission
 GSM and UMTS control plane support only link mode;

 GSM and UMTS user plane support link mode and endpoint;
 Two planes of LTE support link mode and endpoint;
 The MML commands of Operation and Maintenance based on link mode are same as
preceding part, so they are not listed on this part.

Permission

Permission

Permission

Permission

Permission

Permission
 This command is used to list a transmission object on the Iub interface.

Permission
 LST IUB is used to list a transmission object on the Iub interface.

 LST S1 command is used to list the S1 object information.
 LST X2 command is used to list the X2 object information.

Permission

Permission
 With IPsec, two communicating peers (also known as IPsec peers) ensure the
following security features of IP packets transmitted on the network by encrypting the
packets and authenticating the data source:
 Confidentiality: An IPsec entity encrypts user data and transmits the data in
ciphertext to prevent the data from being disclosed on the transmission path.
The IPsec entity is the network element (NE) or network equipment that uses
IPsec for communication.
 Integrity: The IPsec entity checks the received data to ensure that it has not
been tampered with.
 Authenticity: The IPsec entity authenticates the data source.
 Anti-replay protection: The IPsec entity identifies and rejects packets that are
intercepted and repeatedly sent by malicious users.

Permission
 SA-Security Association
 Before using IPsec tunnels for secure data transmission, an SA must be established
between communicating peers. An SA defines security policies negotiated between
communicating peers to protect data flows.

Permission
 The operator can configure one or multiple IPsec policies according to actual network
conditions. Each IPsec policy is bound to one ACL. In an ACL, one or multiple ACL rules
can be configured for data flows that need to be protected by IPsec. The base station
provides IPsec for data flows that comply with the ACL rules. An IPsec policy takes effect
only after it is bound to a transmission port.
 ACL-Access Control List
 IKE-Internet Key Exchange, IPsec SAs can be manually configured. However, due to an
increase in security equipment on the network, manual configuration is difficult and can
hardly ensure security. IKE can be used to automatically establish SAs to simplify using
and managing IPsec. Currently, IPsec SAs can be established for base stations by using
IKE, not manual configuration.

Permission
 Public key infrastructure( PKI) is the foundation and core of network security
construction. It uses an asymmetric cryptographic algorithm to provide information
security and digital certificate management.
 For Huawei products, digital certificates apply to the following scenarios:
 Authentication during the setup of an Internet Protocol Security (IPSec) tunnel
between a base station and an SeGW in a radio bearer network
 Authentication during the setup of a Secure Sockets Layer (SSL) connection
between an eGBTS/NodeB/eNodeB and the U2000 at the application layer
 802.1X-based access control for the eGBTS/NodeB/eNodeB, which uses
digital certificates for identity authentication

Permission

Permission

Permission

Permission
 An IKE proposal consists of the encryption algorithm, verification algorithm, authentication

method, DH group, PRF algorithm, and IKE SA lifetime.
 During IKE negotiation, the IKE local end uses its IKE proposal to negotiate with the IKE peer
end and establishes an IKE SA, thereby providing security services for IPsec SA negotiation.
 IP and IPsec are unidirectional and connectionless. When IPsec peers communicate, there is a
probability that one end may not know if the other end because of abnormalities such as a
system failure. If this occurs, the normal end continues to transmit IPsec traffic, resulting in
traffic loss. To prevent traffic loss of this kind, dead peer detection (DPD) is introduced to
detect the peer status (online or offline) for base stations. DPD can be enabled by setting
the DPD parameter to PERIODIC.
 The local end starts DPD only when both of the following conditions are met:
 The local end does not receive IPsec packets from the peer end within the period
specified by the DPDIDLETIME parameter.
 The local end needs to send IPsec packets to the peer end.
 DPD Mode
 Indicates whether to enable the dead peer detection (DPD) function.
 DPD Idle Time(s)
 Indicates the DPD idle time. If the local end does not receive encrypted packets for a
time defined by this parameter, it sends a DPD packet to perform dead peer detection.
The interval for sending a DPD packet slightly varies in various network environments.

Permission
 Encapsulation Mode
 Indicates the encapsulation mode of an IPSec proposal, which can be set to
TUNNEL or TRANSPORT. In TRANSPORT mode, only data is encrypted. In
TUNNEL mode, the whole IP packet is protected, and a new IP header is
added to the original IP packet. The source IP address and the destination IP
address of the new IP header are the IP addresses of two ends of the security
tunnel. Both the TRANSPORT mode and the TUNNEL mode are used for end-
to-end IPSec protection. The TUNNEL mode, however, is also applied to the
protection of a certain segment.
 Transform
 Indicates the security protocol used in an IPSec proposal. The value AH
indicates the Authentication Header (AH) protocol specified in RFC2402. The
value ESP indicates the Encapsulating Security Payload (ESP) protocol
specified in RFC2406. The value AH_ESP indicates that the ESP protocol is
preferentially used to protect packets, but not the AH protocol.

Permission
 Control Mode
 Indicates whether the object can be modified or deleted by the system. The
value MANUAL_MODE means that only the user can modify or delete the
object. The value AUTO_MODE means that both the system and the user can
modify or delete the object.
 Auto Config Flag
 Indicates whether the object is created by the system. MANUAL_CREATED
means that the object is configured by the user manually. AUTO_CREATED
means that the object is created by the system.
 Action
 Indicates the action taken on the data that matches the ACL rule. When the
ACL to which the ACL rule belongs is referenced by a packet filter, the BS
accepts or transmits the data that matches the rule if this parameter is set to
PERMIT, and rejects the data if this parameter is set to DENY. When the ACL
is referenced by an IPSec policy, the BS encrypts or decrypts the data that
matches the rule if this parameter is set to PERMIT, and does not perform any
encryption or decryption on the data if this parameter is set to DENY.

Permission
 SA Duration Mode
 Indicates the configuration mode of the IPSec SA life cycle. If this parameter is
set to GLOBAL, the default SA life cycle is used. In this case, LTS and LTKB
are set to the default values 3600 and 69120000, respectively. If this
parameter is set to LOCAL, the SA life cycle is configurable.
 Lifetime Based On Time(s)
 Indicates the life cycle of an IPSec SA. An IPSec SA becomes invalid once its
life cycle specified by this parameter elapses. Before the life cycle of an IPSec
SA elapses, the IPSec policy is used in an attempt to establish a new IPSec
SA through negotiation to ensure secure transmission; before the negotiation
is complete, the original IPSec SA is still used. After the negotiation is
complete, the new SA is immediately. IPSec SA negotiation takes a period. To
prevent SA updating from affecting communication security, a life cycle longer
than 900 seconds is recommended.

Permission

Permission
 Keepalive Interval(s)
 Indicates the time interval for sending the keepalive packets. If the parameter
is set to 0, keepalive packets are not sent.
 Keepalive Timeout(s)
 Indicates the timeout duration for waiting for the keepalive packets. If this
parameter is set to 0, keepalive packets are not sent.

Permission

Permission
 A sector is a geographical area with radio coverage and a sub-area of a cell. Each
sector is served by one or multiple radio carriers. Each radio carrier occupies either
single or multiple frequencies.
 Sectors and radio carriers form a cell, the fundamental unit for MS access.
 sector equipment is a combination of RF channels in a sector.
 The SectorEqm defines antenna channels and their working modes in a sector. An
antenna channel can work in Tx mode, Rx mode, or Tx/Rx mode, or serve as the
master or slave channel.A sector can be equipped with multiple pieces of sector
equipment.

Permission

Permission

Permission
 If Sector Equipment ID is not specified, the basic information about all sector
equipment is displayed, but the information about sector equipment antennas is not
displayed. If Sector Equipment ID is specified, information about the sector equipment
and sector equipment antennas is displayed.

Permission
 Maximum Power(0.1dBm)
 Indicates the maximum power provided for the TRX group by the sector
equipment which needs to share the antenna system with the logical cell in the
same mode provided by other operators. 65535 indicates that the maximum
allowed transmitting power provided by the sector equipment.

Permission
 Max Output Power(0.1dBm)

 Indicates the maximum output power of the sector equipment, in units of 0.1
dBm.

Permission

Permission
 Work Mode
 If each sector equipment serving the TRX group meets the requirements for
the frequency and power of TRXs in the TRX group, this parameter is set to
INDEPENDENT.
 If the bandwidth of the frequency set in the TRX group exceeds the maximum
transmitting bandwidth of its serving sector equipment and all sector
equipment serving the TRX group need to cooperate with each other, this
parameter is set to INTERPARFFH.
 If the power of the TRXs in the TRX group exceeds the power specification for
single sector equipment and all sector equipment serving the TRX group need
to cooperate with each other, this parameter is set to INTERPAPS.

Permission
 Use this command to query the status for local cells, such as local cell status, local
cell administration status, status of the logical cell corresponding to the local cell, cell
baseband deployment, and cell aid status.
 Cell Status: Indicates the status of a logical cell: AVAILABLE and UNAVAILABLE. If
the local cell is not bound to a logical cell, this parameter displays as NULL. Note:
AVAILABLE indicates that the logical cell is normal. UNAVAILABLE indicates that
users cannot access the logical cell.
 Cell Administration Status: Indicates the administration status of a logical cell: LOCK
and UNLOCK. If no logical cell is bound to the local cell, this parameter displays as
NULL. Note: LOCK indicates that the logical cell is blocked and unavailable, and MSs
that have accessed the cell are forcibly handed over to other normal cells. UNLOCK
indicates that the logical cell is available.
 Baseband Deployment: Indicates the actual baseband deployment in the local cell. It
falls into two types: embedded baseband deployment and baseband equipment
deployment.
 License Authorized: Indicates whether the specified TRX has an authorized license.
The values of this parameter are LICENSED and UNLICENSED.
 Effective Status: Indicates the actual effective status of TRXs: EFFECTIVE and
INEFFECTIVE. When the TRX is not licensed or the DSS TRX is deactivated, the
parameter displays as INEFFECTIVE.

Permission
 DSP ULOCELL is used to display the status of a specified local cell and logical cell or
all ones, diversity characteristic, and cell setup date.
 Local Cell Administration Status
 Indicates the local cell administration status. Blocked: The previous services in
the cell are released and the cell is unavailable. Shutting down: Non-high-
priority cells are selected but the cells do meet the blocking condition.
 BLK ULOCELL is a high-risk MML command, and therefore execise caution when
executing this command.
 After the cell blocked successfully, the Local Cell Blocked alarm appears.
 If the Local Cell ID is not specified, all the local cells in the NodeB will be blocked, and
the Block PRI must be set to "HIGH". Otherwise, the execution of this command fails.
 If the local cell is not bearing any logical cell, you can block the local cell immediately
no matter which block priority is applied to the cell. Otherwise, the local cell can be
blocked only after the RNC responds a block message.
 If you set the Block PRI to "HIGH", immediately the local cells shall be blocked no
matter whether the local cell bears the logical cell.

Permission

Permission
 Message tracing traces interfaces, signaling links, and UEs. It applies to routine
equipment maintenance and fault location.
 By tracing messages, you can verify data and identify faults. After a message tracing
task is created, the traced messages can be browsed and saved.
 Only when the OM channel is established between the U2000 and the base station,
and the correct data configuration file is downloaded from the U2000 to the base
station, the tracing task can be performed on the LMT.
 On the local maintenance terminal (LMT), common tracing tasks and GSM, UMTS,
and LTE-specific tracing tasks can be performed.

Permission
 In the LMT main window, click the Trace tab.

 In the navigation tree, choose Trace > Common Services. Double-click *** Trace.
 The *** Trace dialog box is displayed.
 Set related parameters in the *** Trace dialog box.
 Click Submit.

Permission

Permission

Permission
 In the LMT main window, click Monitor.

 In the navigation tree, choose Monitor > Common Monitoring. Double-click ***
Monitoring.
 The *** Monitoring dialog box is displayed.
 Set related parameters in the *** Monitoring dialog box.
 Click Submit.

Permission

Permission
 Local user: Account of local user (including the default admin user) is managed by the
LMT. Local user can use the LMT to log in to the base station when he is
disconnected from the U2000 server.
 EMS users: Accounts of EMS users are centrally managed by the U2000 server. EMS
user accounts are created, modified, authenticated, and authorized by the U2000
server. Only authorized EMS users are permitted to use the LMT to log in to the base
station. Authorized EMS users can also log in to the U2000 server from the U2000
client to manage the base station. To directly log in to the base station as an EMS
user, ensure that the base station is connected to the U2000 server.
 The local maintenance terminal (LMT) operation and maintenance (OM) subsystem
enables multiple users to perform operations at the same time. To ensure system
security, user rights are controlled in the following aspects:
 User identity: A user must enter the correct user name and password when
logging in to the LMT.
 User rights: Users of different levels are allowed to use different graphical user
interface (GUI) operations and man-machine language (MML) operations.
 Operation time limit: It specifies the time during which a user can perform
operations.

Permission
 managing command groups

 Run the ADD CCG command to add commands to a command group.
 Run the RMV CCG command to remove commands from a command group.
 Run the LST CCG command to view a command group
 Run the LST CCGN command to view the name of a command group.
 Run the SET CCGN command to name a command group.

Permission
 LMT user accounts are classified into internal user accounts and external user
accounts. Different accounts have different rights, which are described as follows: The
internal user account includes a super user account. The super user name is admin
and the default password is hwbs@com. A super user has all rights.
 Five levels of external user accounts are provided, and each level is allocated
different rights.

Permission
 If the added operator belongs to the Custom user group, the operator cannot have
more rights than the user who adds the account.
 G_0 is a group of commands that all users are permitted to use by default. It cannot
be removed.

Permission
 Use MOD OP command to modify a local operator account.

 For a customer account, the MOD OP command cannot be executed to make other
accounts have more rights than a customer account.
 For a default admin account, only the password can be changed and the password
must be changed on the U2000. In addition, the administrator cannot run the MOD OP
command to change its own password.

Permission

Permission
 Operation log:
 The operation log is mainly used to analyze the relationships between device
faults and performed operations.
 Security log:
 The security log is used for auditing and tracing security events.
 Running log:
 The running log helps you in fault location, routine inspection, and device
running monitoring.

Permission
 LST OPTLOG
 Source: Indicates the source of the log record.
 Value Range: EMS(EMS), LMT(LMT), INVALID(INVALID),
OTHER(OTHER)
 Operator: Account of the operator
 Domain Name: Domain name of the operator to be queried
 Value Range: LOCAL(Local), EMS(EMS), EMSOP(U2000)
 LST SECLOG
 Event Type: Indicates the event type that triggers the security log.
 Value Range: AUTHENTICATION(Log on and Authentication),
ACCOUNT_MANAGEMENT(Account Management),
ACCESS_CONTROL(Access Control), OTHER(Other),
NETWORKATTACK(Network Attack)
 Event Level: Indicates the event level that triggers the security log.
 CRITICAL(Critical), MAJOR(Major), MINOR(Minor)

Permission
 You need to run the LST LOGFILE command to query the log file name before
uploading a log file.
 This command uploads only one log at a time. If logs need to be uploaded in batches
based on the log type, run the ULD FILE command.
 The operations of uploading files to the base station are exclusive.

Permission

Permission
 The license is a contract that Huawei and telecom operators provide for users with a
specific function, application scope, and duration of a product. Telecom operators can
select the network function and capacity for a certain stage by purchasing a specific
license. This protects the investment. The U2000 provides the function of managing
the NE license, including uploading, activating, and allocating the license.
 Controller license: BSC (GBTS)/RNC
 eGBTS license: co-MPT base stations involving the eGBTS technology
 NodeB license: NodeBs and co-MPT base stations involving the UMTS technology
 Standalone license: eNodeBs and co-MPT base stations involving the LTE
technology

Permission
 An eGBTS license is generated based on the electronic serial number (ESN) of the
BSC to which the eGBTS belongs, and is shared by all eGBTSs managed by this
BSC. The license allocation values can be modified between eGBTSs.
 The eGBTS license files are saved on the U2000 server.
 The total number of resources allocated to all eGBTSs managed by a BSC cannot
exceed the number of resources specified in the corresponding eGBTS license. In
addition, the resources of one BSC cannot be allocated to eGBTSs managed by
another BSC.
 eGBTS licenses are classified into the following types:
 Commercial license: Users need to purchase commercial licenses from
Huawei. After the purchase, the eGBTSs of this user can use all resources
within a time period specified in the commercial license.
 Trial license: Users can obtain trial licenses from Huawei for free. After a user
has obtained a trial license, the eGBTSs of this user can use certain resources
within a time period specified in the trial license during BSC commissioning.
The default validity period of a trial license is three months.

Permission
 A NodeB license is generated based on the electronic serial number (ESN) of an

RNC, and is shared by all NodeBs managed by this RNC.
 NodeB license files are saved on the U2000 server instead of on NodeBs. The U2000
allocates NodeB licenses to NodeBs, and the allocated NodeB licenses take effect
immediately after they are delivered to U2000 NodeBs.
 The total number of resources allocated to all NodeBs managed by an RAN cannot
exceed the number of resources specified in the corresponding NodeB license. In
addition, the resources of one RNC cannot be allocated to the NodeBs managed by
another RNC.
 The NodeB license is classified into the following types: Commercial license:
 Users need to purchase commercial licenses from Huawei. After a user has
purchased a commercial license, the NodeBs of this user can use all
resources and provide all functions within a time period specified in the
commercial license.
 Trial license: Users can obtain trial licenses from Huawei directly and do not
need to pay for them. After a user has obtained a trial license, the NodeBs of
this user can use trial resources and provide trial functions within a time period
specified in the trial license. The default validity period of a trial license is three
months.

Permission
 eGBTS License Operation Scenaario

 Creating an eGBTS
 Scenario: Creating a BSC
 Changing the BSC ESN
 Upgrading an eGBTS
 Expanding an eGBTS
 Scenario: Reparenting an eGBTS
 Evolving a GBTS into an eGBTS
 Common Operations on the eGBTS License
 Querying the BSC ESN
 Uploading the eGBTS License to the U2000 Server
 Modifying eGBTS License Allocation Values
 Modifying eGBTS License Allocation Values
 Viewing Detailed eGBTS License Information
 Viewing Detailed eGBTS License Information
 Synchronizing an eGBTS License
 Manually Downloading an eGBTS License

Permission

Permission
 NodeB:
 Choose License > NE License Management > NodeB (traditional style);
alternatively, double-click Software Management in Application Center and
choose NE License > NodeB (application style). The NodeB License
Management window is displayed.
 eGBTS:
 Choose License > NE License Management > eGBTS (traditional style);
alternatively, double-click Software Management in Application Center and
choose NE License > eGBTS (application style). The eGBTS License
Management window is displayed.

Permission
 Modify NodeB license allocation values.

 In the Modify dialog box, you can modify allocation values in batches for the same
operator's license control items with the same value ranges by clicking Copy to.
 In the Modify dialog box, select the control item of an operator and modify its
value as required.
 click Copy to at the bottom. In the displayed Setting dialog box, select the
control items to modify in batches.
 Click OK. The control items are successfully modified in batches in the Modify
dialog box.

Permission
 You can upload multiple eGBTS licenses for one BSC. Only one license can be active
at a time.
 System time refers to the time on the U2000 server rather than the time on the U2000
client.
 If a license fails to be uploaded, you can view the cause of the failure in uploading
logs.
 After an eGBTS license is uploaded to the U2000 server, you can double-click it to
view details.

Permission

Permission

Permission

Huawei Operation and Maintenance ISSUE 1.00

Încărcat de

Informații document

Descriere originală:

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Huawei Operation and Maintenance ISSUE 1.00

Încărcat de

Drepturi de autor:

Formate disponibile

MBTS GU V100R009 Operation and Maintenance P-1

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

 Components of the LMT main window:

 Components of the MML command window:

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

 U2000 client online installation procedure:

Confidential Information of Huawei. No Spreading Without

 Start the U2000 client.

Confidential Information of Huawei. No Spreading Without

 Choose Topology > Main Topology (traditional style); alternatively, double-click

Confidential Information of Huawei. No Spreading Without

 Choose Topology > Main Topology (traditional style); alternatively, double-click

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

 Choose Monitor > Synchronize NE Alarms (traditional style); alternatively, double-

Confidential Information of Huawei. No Spreading Without

 Choose Topology > Main Topology (traditional style); alternatively, double-click

Confidential Information of Huawei. No Spreading Without

 Choose System > NE Monitor (traditional style); alternatively, double-click

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Alarm Settings > Template Management (application style).

Confidential Information of Huawei. No Spreading Without

 Collecting Statistics on Alarm Logs

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

 Query Board Inventory

Confidential Information of Huawei. No Spreading Without

 A health check may be performed in the following scenarios:

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

VSWR Test window is displayed.

Confidential Information of Huawei. No Spreading Without

 This section describes how to perform interference detection to locate faults on RF

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

 This command cannot be used to reset an unavailable board.

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

Confidential Information of Huawei. No Spreading Without

 [Co-MPT,NodeB,eNodeB]When the specified CPRI port is on an RHUB, the CPRI port is

Confidential Information of Huawei. No Spreading Without