Huawei MBTS Operation and Maintenance

MBTS UL V100R017C10
Operation and Maintenance

www.huawei.com
Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Objectives
 Upon completion of this course, you will be able to:
 Perform routine operation and maintenance on the MAE and local
maintenance terminal (LMT).
 Perform alarm management, device maintenance, and transmission
tests.
 Perform operation and maintenance for MBTS UL V100R017C10.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 1

Contents
1. Alarm Management on the MAE
2. MBTS Device Maintenance
3. MBTS Transport Layer Maintenance
4. MBTS Radio Layer Maintenance
5. MBTS Tracing and Monitoring Management
6. MBTS System Management
7. MBTS Board Replacement

Alarm and Event
Recommendatio
Category Definition Related Concept Impact Handling
n
Alarms are physical or

A notification
logical factors that The system Clear alarms to
generated when Alarms can be
Alarm cause system failures, may fail to restore the
the system cleared.
such as hard disk work properly. system.
detects a fault
faults or board faults.
An event is a situation
Events cannot be
A notification of the managed Events have
cleared, but can Events do not
generated when object. For example, no negative
Event be acknowledged need to be
the system operation logs are impact on the
or handled.
detects an event successfully exported system.
unacknowledged.
at the scheduled time.

Alarm Severity
Alarm Severity Definition Handling Requirement
Faults that affect the services provided by the system are
Handle such faults
reported. These alarms need to be handled immediately even
Critical alarm immediately. Otherwise,
during non-working hours. For example, some devices or
the system may crash.
resources break down.
Handle such faults in
Faults that affect the quality of service (QoS) are reported. These time. Otherwise, the
Major alarm alarms need to be handled during working hours. For example, system may fail to
the performance of some devices or resources deteriorates. perform some major
functions.
Faults that are not serious enough to affect the QoS are
reported. These alarms can be handled as required or further Find and rectify any
Minor alarm
observed to prevent them from becoming more serious. For potential fault in time.
example, obsolete historical alarms need to be cleared.
Faults that are potential threats to system services are reported. You only need to know
Warning alarm These alarms need to be handled according to specific the system running
situations. An example is the OMU startup alarm. status.

Manually Synchronizing NE Alarms
 Due to issues such as network interruption, the alarm data on the MAE may be inconsistent with that on the
NEs.
 To obtain the latest alarm status of the NEs, you can synchronize the alarm data on the NEs with that on the
MAE to keep the data consistent.

Monitoring Alarms Through the Topology View

Monitoring Alarms Through the NE Monitoring
List
 By monitoring the NE status, you can view the name, type, severity, and status of the NEs
that are managed by the MAE.

Browsing Current Alarms
 Browse the alarms that require attention and handling by setting the conditions for
filtering current alarms.

Querying Alarm Logs
 Query the logs of each alarm in the log library after setting the conditions for querying
alarm logs.

Setting an Alarm/Event Template
 You can save frequently used query conditions or statistical conditions of alarms/events
as a template.
 If you want to query or collect statistics on alarms/events that meet the same conditions,
we can use the template.

Collecting Statistics on Alarm Logs
 You can set statistical conditions and export alarm log statistics.

Locating Objects Where Alarms Occur
 Use the locating function of topology to identify the NE that raises an alarm/event based
on the alarm/event record.

Acknowledging/Unacknowledging an Alarm
 Alarm acknowledgement indicates that an alarm has been handled and does not require
much attention.
NOTE
Operations are similar for BTS3900 and BTS5900 series base stations. They only differ in NE
Type.

Manually Clearing an Alarm
 If an alarm cannot be automatically cleared, or it is confirmed that the alarm does not
exist on the NE or the OSS, you can manually clear the alarm.
NOTE
Operations are similar for BTS3900 and BTS5900 series base stations. They only differ in NE
Type.

Recording Alarm/Event Maintenance Experience
 Record alarm/event maintenance experience to the experience library.
 When a similar alarm/event occurs, you can consult the experience library to handle it.

Contents

2.1 Hardware Maintenance on the MAE
2.2 Hardware Maintenance on the LMT
2.3 Software and File Management
2.4 Clock Maintenance
2.5 Antenna Test

Viewing Board Availability from the MAE
 Open the Device Panel window.

Viewing Board Labels on the MAE
 In the Device Panel window, right-click a board, and choose Query Board Inventory
from the shortcut menu.

Checking Health on the MAE
 Create a health check task.

Contents

2.5 Antenna Test

Introduction to the LMT
 Main window of an LMT for DBS5900 UL
1. Status bar 2. Functions 3. Menu bar 4. Help

Device Panel Interface

Blocking/Unblocking a Board
Block a board in GUI mode Unblock a board in GUI mode
Block board MML
Unblock board MML

Resetting a Board
The reset of the active main control board resets the UPEU/USCU/FAN.
GUI mode
MML

Querying Board Status
GUI mode
MML

Querying Board Information (GUI Mode)

Querying Board Information (MML)
Board manufacturing information
Board CPU/DSP
occupancy
Board version information

RRU Operation
GUI mode on the MML
MAE

Displaying CPRI Port Information
 Query the dynamic information about a CPRI port on an RF or a BBU.

Querying the Control Link

Contents

2.5 Antenna Test

Concepts Related to Software and Files
 Software and file types
Item Type
BootROM
Base station software
Software
Cold patch
Hot patch
Data configuration file
Maintenance and operation log
Main control log
File Board log
Routine received total wideband power (RTWP) test
log
Device archive file

Co-MPT Base Station Functional Structure
 BTS functional structure consists of BTS nodes, GBTS services, NodeB
services, and eNodeB services.

BTS Software Overview
Main area Standby area
MBTS MBTS
software A software B
Backup
Main area Standby area
MBTS MBTS
software B software A

Querying the Running Software Version
 Run the LST VER command.

Querying the Software Version Stored on the NE
 Run the LST SOFTWARE command.

Configuring the FTP Server
 Procedure for configuring a File Transfer Protocol (FTP) server

Downloading the BTS Software
 Download the BTS software from the FTP server to the base station.

Transferring the Extra Configuration File
 Download the BTS extra configuration file from the FTP server to the base
station.
Handle FTP server

panel configuration

Transferring the Data Configuration File
 Download or upload the data configuration file.

Backing Up Configuration Data (Based on LMT)
 Run the BKP/ULD CFGFILE command. (BKP CFGFILE is a high-risk
command.)

Backing Up Configuration Data (Based on MAE) (1)
 Manually back up NE data.

 Back up NE data on schedule.



Contents

2.5 Antenna Test

Querying the Clock Status

Contents

2.5 Antenna Test

VSWR Test on the MAE
 Test the VSWR of a base station.

VSWR Test through MML Commands
 Run the STR VSWRTEST command to start a VSWR test. (This is a high-
risk command.)

RF Interference Detection
 Perform RF interference detection to locate faults on RF devices.

Cross Feeder Connection Test
 Run the STR CROSFEEDTST command to start the cross feeder
connection test. (This is a high-risk command.)

Interference Detection Test
 Run the STR RFTEST command to start an interference detection test.
(This is a high-risk command.)

Contents

3.1 Transport Performance Test
3.2 Transport Link Maintenance

Transport Test Methods
 Connectivity test
 UDP loopback
 Ping test
 Trace route
 Performance test
 IP performance monitoring

Ping Test
 Check whether the TCP/IP network connection is normal and the target
host is reachable.

TRACERT (Trace Route) Overview
ICMP Echo Request (TTL = 1)
ICMP Echo Reply (Timeout)
eNode Router MAE

B ICMP Echo Request (TTL = 2)

TRACERT (Trace Route)
 Start route tracing.

IP Performance Monitoring
 Introduction to IP Performance Monitor (IP PM)
 IP PM is based on the E2E link check at the UDP or SCTP layer.
BWD RX 2 2 2 2 1 2 RNC
FWD TX 2 2 2 2 2 2 2 1 2 2
2 User packet
FWD RX 2 2 2 2 2 2 2 1 2 2 n BR
BWD TX 2 2 2 2 1 2 NodeB n FM

IP PM Principles
 IP Performance Monitor (IP PM)
Duration for
transmitting
packets IP header
FM UDP header
Statistical Statistical
area IP PM packet
area
BR
FM: forward monitoring
Duration for
receiving BR: backward reporting
packets

IP PM Application
 Run the ADD IPPMSESSION command to add an IP PM session.

IP PM Application
 Run the DSP IPPMSESSION command to query the status of an IP PM
session.

Introduction to TWAMP
 The TWAMP measurement process and negotiation process are as follows:

TWAMP Controller Function Configuration
 Run the ADD TWAMPCLIENT or ADD TWAMPSENDER command to
activate a test.

TWAMP Responder Function Configuration
 Run the ADD TWAMPRESPONDER command to enable the TWAMP
Responder function.

Activation Verification (1)
 The local end serves as the TWAMP controller. Run the DSP
TWAMPCLIENT command to query the local client status.

 The local end serves as the TWAMP controller. Run the DSP
TWAMPSENDER command to query the local sender status.

 The local end serves as the TWAMP responder. Run the DSP
TWAMPRESPONDER command to query the local responder status.

Differences
 TWAMP and Huawei-private IP PM are mutually complementary. When there are ongoing
services, IP PM is recommended for testing connections between the eNodeB and Huawei S-
GW, and TWAMP is recommended for testing connections between the base station and
transmission devices on the transport network.
Item Huawei-Private IP PM TWAMP
The peer end must be a The peer end can be any device
Interconnection
Huawei device. supporting TWAMP.
Transmission QoS of online Service packets are simulated. Offline tests

Test
services is detected. on transmission links are recommended.
Depends on online services.
• Packet injection affects ongoing services
No test can be conducted
Restriction and occupies some bandwidth.
when no services are
• The peer device must support TWAMP.
running.

IP Loopback Test
 Function
 Connectivity and link quality at the Iub interface

IP Loopback Procedure
Start
Start the remote loop of IP level on MBTS.
Start the IP loopback test on the peer end.
Query the result on the peer end.
Stop the IP loopback test.
End

Start the Remote Loop of IP Level on MBTS
 Run the SET UDPLOOP command to set UDP loopback. (This is a high-risk command.)

Start the IP Loopback Test on the Peer End (RNC)
 Run the STR IPLOPTST command to start the IP loopback test.

Query the Result of the Loopback Test at the IP
Layer on the Peer End (RNC/BSC)
 Run the DSP IPLOPTST command to display the IP loopback test result.

Stop IP Loopback Test (on the RNC)
 Run the SET UDPLOOP command on the MBTS to stop the UDP loopback test. (This is a
high-risk command.)

Contents

3.1 Transport Performance Test
3.2 Transport Link Maintenance

IP Address Definition on MBTS
LOCALIP
ETH
IP
DEVIP
address
ETHTRK
OMCH
Local maintenance Remote

maintenance
LMT
MAE or LMT
Remote MAE server

Local O&M IP MBTS O&M IP LMT

Typical Transport Networking
 Example of network topology for co-transmission on the co-MPT UL multimode base
station side

Sketch Map of the Transport Structure
 Maintenance MML commands in the link mode on the protocol stack
DSP
S1INTERFACE
LST/DS DSP
P IUBCP X2INTERFACE LST
NOBEBPATH
Dedicated
LST ENOBEBPATH
transport
data
LST IPPATH
Common LST/DSP LST DEVIP/ IPRT

transport CPBEARER DIFPRI
data LST VLANMAP
DSP ARP
LST/DSP LST/DSP
SCTPLNK ETHPORT

MO Planning of the Transport Layer
 Link mode

Physical Layer Operation
 LST/DSP ETHPORT

Data Link Layer Operation (1)
 Run the DSP ARP command to query the active ARP table entries of the system.

Data Link Layer Operation (2)
 Run the LST VLANMAP command to query mapping from the next hop IP to VLAN.

IP Layer Operation
 Run the LST/DSP IPRT command to query the IP route.
Source IP address Next hop IP address Destination IP address
VOICE
IP route

SCTP Link Operation
 Run the LST/DSP/BLK/UBL SCTPLNK command. (BLK SCTPLNK is a high-risk
command.)

IP Path Operation
 Run the LST/DSP IPPATH command.

Control Port Bearer Operation
 Run the LST/DSP CPBEARER command to query the status of the control port bearer.

Transport Layer Operation Dedicated to UMTS (1)
 LST/DSP/RMV IUBCP (These are high-risk commands.)

Transport Layer Operation Dedicated to UMTS (2)
 LST/RMV NODEBPATH (These are high-risk commands.)

Transport Layer Operation Dedicated to LTE (1)
 DSP/MOD/RMV/BLK/UBL/RST S1INTERFACE (MOD S1INTERFACE, RMV
S1INTERFACE, BLK S1INTERFACE, and RST S1INTERFACE are high-risk commands.)

Transport Layer Operation Dedicated to LTE (2)
 LST/MOD/RMV ENODEBPATH

Transport Layer Configuration Scheme
GSM UMTS LTE

Control plane Link mode Link mode Endpoint mode
User plane Link mode Endpoint mode Endpoint mode
IPsec Link mode

Sketch Map of the Transport Structure
 Maintenance MML commands based in the endpoint mode on the protocol stack
DSP S1INTERFACE
DSP
LST/DSP X2INTERFACE
IUBCP (Auto) LST
EPGROUP
(LTE/UMTS)
Dedicated LST S1
transport data LST X2
LST IPPATH (GSM)
Common LST VLANMAP

LST/DSP CPBEARER LST EPGROUP (LTE)
transport data DSP ARP
UMTS: Manual
LTE: Auto
LST/DSP ETHPORT
LST/DSP LST LST DEVIP/IPRT LST USERPLANEHOST

SCTPLNK SCTPHOST/SCTPPEER LST DIFPRI (LTE/UMTS)
LST SCTPTEMPLATE (LTE)
MO Planning of the Transport Layer
 Endpoint mode
Endpoint Mode MO Planning
IUBCP (NCP) IUBCP (CCP) IUB SI X2
CPBEARER CPBEARER EPGROUP EPGROUP EPGROUP

EPGROUP 1 EPGROUP 2
1 2 0 3 4
USERPLA
SCTPHOST SCTPPEER USERPLAN
SCTPLNK 1 SCTPLNK 2 N
0 0 EHOST 1
EHOST 1
UMTS control plane LTE control plane UMTS user plane LTE user plane

MML Command Differences Between Link Mode
and Endpoint Mode
Item Link Mode Endpoint Mode
Physical layer DSP ETHPORT DSP ETHPORT
DSP ARP DSP ARP
Data link layer
LST VLANMAP/VLANCLASS LST VLANMAP/VLANCLASS
LST/DSP IPRT; LST DEVIP

LST/DSP IPRT; LST DEVIP LST/DSP SCTPLNK/CPBEARER
LST IPPATH LST SCTPHOST/SCTPPEER/SCTPTEMPLATE
Transport layer LST/DSP SCTPLNK/CPBEARER LST USERPLANEHOST/USERPLANEPEER
LST DIFPRI LST EPGROUP
DSP DIAGNOSE LST DIFPRI
DSP DIAGNOSE
Transport data dedicated to LST GBTSPATH LST/DSP IUBCP

UMTS LST/DSP IUBCP LST IUB
LST ENODEBPATH DSP/MOD/RMV/BLK/UBL/RST
Transport data dedicated to LTE DSP/MOD/RMV/BLK/UBL/RST S1INTERFACE/X2INTERFACE
S1INTERFACE/X2INTERFACE LST S1/X2
Automatically Establishing Objects in Endpoint
Mode
Automatic Object Establishment on the Automatic Object Establishment on the User
Control Plane Plane
DSP SCTPPEER
DSP/LST SCTPLNK
DSP/LST CPBEARER DSP/LST USERPLANEPEER
DSP S1INTERFACE
DSP X2INTERFACE
Control Plane Operation (Endpoint Mode) (1)
 Run the LST SCTPHOST/SCTPPEER command to check the SCTP host and SCTP peer
configurations.
 Run the LST SCTPTEMPLATE command to check the SCTP template configuration.
 Run the LST EPGROUP command to check the endpoint group configuration.
User Plane Operation (Endpoint Mode) (1)
 Run the LST USERPLANEHOST command to check the user plane host configuration.
User Plane Operation (Endpoint Mode) (2)
 Run the LST EPGROUP command to check the endpoint group configuration.
IUB/S1/X2 Object
 Run the LST IUB/S1/X2 command to list the IUB/S1/X2 configuration.
Contents

4.1 Basic Concept
4.2 Carrier Resource Management
4.3 Cell Management
Sector and Cell
 Sector, cell, and sector equipment
Sector
equipment
Case for Sector and Sector Equipment
Contents

4.1 Basic Concept
4.3 Cell Management
Sector Equipment Operation
 LST/MOD/RMV SECTOR
 LST/MOD/RMV SECTOREQM (MOD
SECTOREQM is a high-risk command.)
Local Cell Sector Equipment (UMTS)
 LST/MOD/RMV ULOCELLSECTOREQM (MOD ULOCELLSECTOREQM and RMV
ULOCELLSECTOREQM are high-risk commands.)
Cell Sector Equipment (LTE)
 LST/MOD/RMV EUCELLSECTOREQM (MOD EUCELLSECTOREQM and RMV
EUCELLSECTOREQM are high-risk commands.)
Contents

4.1 Basic Concept
4.3 Cell Management
UMTS Cell Operation
 LST/DSP/MOD/RMV/BLK/UBL ULOCELL (MOD ULOCELL, RMV ULOCELL, and BLK
ULOCELL are high-risk commands.)
LTE Cell Operation
 LST/DSP/MOD/RMV/BLK/UBL/ACT/DEA CELL (MOD CELL, RMV CELL, BLK CELL, and
DEA CELL are high-risk commands.)
Contents
Message Tracing Type
 Common tracing
 Tracing transport link messages
 Tracing IP security messages
 Tracing RF messages
 UMTS-specific tracing
 Iub interface messages
 LTE-specific tracing
 S1/X2/Uu interface messages
Message Tracing Operation
Performance Monitoring Type
 Functions
 Track the base station performance in real time.
 Monitor the running status of services and equipment.
 Analyze exceptions to maintain devices and rectify faults.
 Monitoring types
 Common monitoring
 UMTS-specific monitoring
 LTE-specific monitoring
Performance Monitoring Operation
Contents
6.1 Permission Management
6.2 Log Management
6.3 License Management
User Types
 Local user: Accounts of local users (including the default admin account)
are managed by the LMT.
 EMS user: Accounts of EMS users are centrally managed by the MAE.
Command Group
 An NE provides 32 command groups.
 G_0 to G_21 command groups are predefined by the system.
 G_22 to G_31 are reserved.
 Different command groups can be assigned to different operators,
so that they will have different operation permissions.
Operation Permissions
Operator Level Authorized Command Group Permission Remarks
ADMINISTRATO
G_0 to G_21 Full permissions
R
 Permissions of a
Any command groups other than G_1,
OPERATOR USER-level operator
G_14, or G_15 The permissions are
 Data configuration
predefined by the
 Permissions of a system and cannot be
USER Any command groups other than G_1, changed.
GUEST-level operator
G_14, or G_15  System O&M
G_0, G_2, G_4, G_6, G_8, G_10, G_12,

GUEST Data query
G_16, G_18, and G_20
Users with CUSTOM-level accounts Changeable: Different
can be allocated any command Permissions are specified CUSTOM-level
CUSTOM
groups when the accounts are during account addition. operators can have
created. different permissions.
Management of User Accounts
 Run the ADD OP command to add a local operator.
Management of User Accounts
 Modify the password of the active user account.
 Run the SET PWDPOLICY command to set the password policy.
Contents
6.2 Log Management
Log Types
 Node
 DBGLOG, OPRLOG, RUNLOG, SECLOG, CBDLOG, BDTLOG
 NodeB
 DBGLOG, CHRLOG, CALLLOG, SIGLOG, CELLLOG
 eNodeB
 DBGLOG, CHRLOG, SIGLOG, TRCLOG, SONLOG, ECRLOG, CMSLOG, UCRLOG
Querying Logs
 Run the LST OPTLOG command to query operation logs.
 Run the LST SECLOG command to query security logs.
Uploading Log Files
 Run the ULD LOG command to upload log files on the NE to a specified FTP server.
 Run the LST LOGFILE command to list log files.
Contents
6.2 Log Management
License Management
 Classification of NE licenses
License
Description Applicable NE
Type
The controller license defines available functions and

Controller
resources for a BSC. Each controller has an independent BSC (GBTS)/RNC
license
license.
The NodeB license of an RNC defines the functions and NodeBs and co-MPT
NodeB
resources available for the NodeBs managed by this RNC base stations involving
license
in normal scenarios. UMTS
eNodeB and co-MPT

Standalone The standalone license refers to the license which is used
base stations involving
license by each NE independently and saved on the NE device.
LTE
NodeB License Management
 NodeB license management process
NodeB License Operation Process
 NodeB license operation process
Start
Are NodeB
No
licenses
sufficient on the (Optional) Allocate NodeB
RNC? Query the ESN of the
licenses to operators.
Yes RNC.
Adjust NodeB license allocation
Adjust NodeB license
values for new NodeBs. Apply for new NodeB licenses. allocation values.
Deliver NodeB license Upload NodeB licenses to the Deliver NodeB

allocation values. MAE server. license allocation
values.
(Optional) Set the NodeB View the NodeB license
End license allocation threshold. allocation result.
End
eNodeB License Management
 The eNodeB license is stored on the NE, and each eNodeB uses an independent license.
NE License State
State Description
If the NE license state is Default, all the NE functions are in the Default state, and eNodeB
Default
is running with the allowed least resources and functions.
If a standalone license is applied for during NE commissioning, the license is in the

Commissioning state. In this status, you can use NE functions in a certain period. After the
Commissioning
license expires, the system cannot work properly. Apply for a commercial license before the
license expires.
Normal After the commercial license is installed, the NE is in Normal state.
After the NE license expires, you have a grace period of certain days to apply for a new
Grace Period
license. Control items included in the license are still available.
In emergencies such as disasters, you can set the license state of an NE to Emergency.
When an NE license is in Emergency state, the license restrictions on the corresponding NE
Emergency
are undone and the NE has the maximum capacity. This protects NE services against
damages.
Contents
Background Knowledge for Board Replacement
 When the UMPT, UBBP, RRU, or RFU is replaced, the services over them are interrupted.
 When the UPEU is replaced, the BBU is powered off, the UPEU needs to be replaced
within 10 minutes.
 When the UEIU is replaced, the external devices cannot be monitored, the UEIU needs to
be replaced within 5 minutes.
 When the FAN is replaced, the BBU cannot dissipate heat, the operating temperature
may rise, and a high-temperature alarm may be reported, the FAN needs to be replaced
within 3 minutes.
Prerequisites for Board Replacement
 You have queried the e-label of the board from the MAE or Web LMT to determine the
faulty board type
 MML command: DSP ELABEL
 You have prepared the following tools and materials: torque wrench, ESD wrist straps or
gloves, Phillips screwdriver, ESD box, ESD bag, dust free cloth, and keys to the cabinet
door.
 You have determined the quantity and type of board to be replaced.
 You are authorized to enter the site and bring the keys.
Step 1 of Replacing the UMPT
 Perform the following preparations on the RNC:
 Run the BLK UCELL command on the base station to block all cells under the base station.
 Perform the following preparations on the eNodeB:

 Run the BLK CELL command (which is a high-risk command) to block all cells under the
eNodeB.
 Prepare for restoring software and configuration data.
 Remove the faulty UMPT.
 Record all cable connections on the panel of the UMPT to be replaced.
 Disconnect the transmission cable from the UMPT.
 Loosen the two M3 screws on the panel, raise the ejector levers, and then pull out the UMPT.
 Perform the following operation on the MBTS:
 Set the DIP switches on the new board according to the settings of the DIP switches
on the faulty board.
 Install the new board and reconnect the cables.
 Check the status of the indicators to determine whether the new board works
properly.
 Restore software and configuration data.
 Run the UBL CELL command to unblock all the cells of the base station.
 Browse current alarms to compare the alarms queried with the alarms queried before the
replacement.
 Synchronize the inventory information manually on the MAE.
 Ask the site engineer to verify the services.
Step 1 of Replacing the UBBP
 On the MBTS, run the BLK BRD command (which is a high-risk command) to block the UBBP.
 Remove the faulty UBBP on the MBTS.
 Record all the cable connections on the panel of the UBBP to be replaced.
 Disconnect the CPRI cable from the UBBP.
 Loosen the two M3 screws on the panel, raise the ejector levers, and then pull out the UBBP.
 Perform the following operations on the MBTS:
 Set the DIP switches on the new board according to the settings of the
DIP switches on the faulty board.
 Install the new board and reconnect the cables.
 Check the status of the indicators to determine whether the new board
works properly.
 After the board starts up, wait for 15 minutes. Then determine whether
the board is functional according to the status of the indicators on the
board.
 On the MBTS, run the UBL BRD command to unblock the UBBP.
 Compare the alarms queried before and after the replacement.
Step 1 of Replacing the RFU
 Lock the TRX of RFU board
 Log in to the LMT and run the BLK BRD command (which is a high-risk
command) to block the RFU.
 Instruct the site engineer to replace the RFU.
 Put on an ESD wrist strap or a pair of ESD gloves.
 Power off the RFU.
 Disconnect the cables on the faulty RRU.
 Remove the RFU from cabinet.
 Place the new RFU into cabinet.
 Connect the cables on the RFU.
 Reconnect the corresponding power cable connector to the DCDU panel to power on
the RFU.
 Run the UBL BRD command to unblock the RFU.
 Compare the alarms queried before and after the replacement.
Q&A
1. How do I manually synchronize NE alarms?
2. How do I set an alarm template?
Contents
Thank You
www.huawei.co
m

Huawei MBTS Operation and Maintenance

Uploaded by

Document Information

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Huawei MBTS Operation and Maintenance

Uploaded by

Copyright:

Available Formats

MBTS UL V100R017C10

Operation and Maintenance

Copyright © Huawei Technologies Co., Ltd. All rights reserved.

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 1

2. MBTS Device Maintenance

3. MBTS Transport Layer Maintenance

4. MBTS Radio Layer Maintenance

5. MBTS Tracing and Monitoring Management

6. MBTS System Management

7. MBTS Board Replacement

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 2

Alarms are physical or

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 3

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 4

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 5

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 6

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 7

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 8

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 9

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 10

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 11

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 12

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 13

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 14

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 15

2. MBTS Device Maintenance

2.2 Hardware Maintenance on the LMT

2.3 Software and File Management

2.4 Clock Maintenance

2.5 Antenna Test

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 16

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 17

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 18

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 19

2. MBTS Device Maintenance

2.2 Hardware Maintenance on the LMT

2.3 Software and File Management

2.4 Clock Maintenance

2.5 Antenna Test

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 20

1. Status bar 2. Functions 3. Menu bar 4. Help

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 21

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 22

Block board MML

Unblock board MML

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 23

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 24

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 25

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 26

Board version information

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 27

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 28

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 29

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 31

2. MBTS Device Maintenance

2.2 Hardware Maintenance on the LMT

2.3 Software and File Management

2.4 Clock Maintenance

2.5 Antenna Test

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 32

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 33

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 35

Main area Standby area

Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page 36