Professional Documents
Culture Documents
BSC6900 GSM Product Documentation V900R021C10 - 05 20231115164709
BSC6900 GSM Product Documentation V900R021C10 - 05 20231115164709
Alarm Description
This alarm is reported when the DC output of the power system is abnormal.
Alarm Attribute
GBTS: version
25621 Major Fault G
earlier than
V100R010C10
Alarm Parameters
Name Meaning
Impact on System
The DC output overvoltage may cause damage to the boards of the base station.
Major
In this case, the ongoing services carried on the boards are disrupted.
The DC output undervoltage may lead to board power-off at the base station. In
this case, the ongoing services carried on the boards are disrupted.
System Actions
None.
Possible Causes
Software None
Prerequisites
Obtain the product documents and ensure that the following chapters have been read and
understood:
• Safety Information
• Initial Configuration Guide
Before performing this procedure, the following are required:
• Access to other documentation referenced within this procedure.
• Access to the site is secured, if required for on-site activities.
Preprocessing
1. Check whether the PSU is being charged
Check for the root alarms on the Check whether root alarms have been 1 None
U2020. reported:
• 25622 Mains Input Out If they have, clear these root alarms.
of Range If they have not, continue handling this
• 25626 Power Module alarm.
Abnormal
• 25711 Solar Array Fault
On the U2020, record the All alarm information has been correctly 1 None
following alarm information to recorded.
facilitate subsequent processing:
"Location Information",
Procedure Items to Be Confirmed Duration Impact
(min.)
Configuration Handling
1. Troubleshoot the DC output alarm threshold configuration
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Check and correct the alarm thresholds for the DC output abnormal
alarm
Run the MML command LST Ensure that the configurations are 5 See
BTSAPMUBP. consistent with the plan. help
View the alarm thresholds for info
the DC output abnormal alarm of r
on power devices. com
"DC Voltage Alarm Upper
Threshold(0.1V)"
"DC Voltage Alarm Lower
Threshold(0.1V)"
Determine whether the settings
of the alarm thresholds are
appropriate according to the
configuration plan. If no, run
the SET BTSAPMUBP command
to configure the alarm threshold
as planned.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
Remote Handling
1. Reset the monitoring device
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Reset a board
Resetting the main control The MML command has been 3 See
board interrupts all services of successfully executed. (Note: The main help
the base station. Perform this control board or CCU runs properly after info
operation in low-traffic hours about 3 minutes, and other boards run of r
(for example, at midnight) properly after about 1 minute.) com
Run the MML command RST
BTSBRD to reset a board.
Run the MML command DSP The MML command has been successfully 1
BTSBRD to check the board executed.
status.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. opened, and the NE related to the alarm has
On the U2020, right-click the been selected.
alarm and choose "Locate in
Topology" from the shortcut
menu.
Right-click the BSC controlling The Inventory Management tab page for the 1
the GBTS that reports the alarm base station related to the alarm has been
and choose "Inventory opened.
Management" from the shortcut
menu.
Right-click the BSC controlling The Inventory Information tab page for the 1
the GBTS that reports the alarm board related to the alarm has been opened.
and choose "Synchronize" from
the shortcut menu. After
synchronization is complete,
select a GBTS under the NE.
Then, click the navigation tree to
find inventory information about
corresponding boards.
Run the MML command LST The MML command has been 3 See
BTSAPMUBP to query the successfully executed. The upper and help
thresholds of the DC voltage lower thresholds of the DC voltage alarm info
alarm. Input have been recorded. of r
parameters:[Cabinet No.] = com
"Cabinet No." in the alarm
parameters
[Subrack No.] = "Subrack No."
in the alarm parameters
[Slot No.] = "Slot No." in the
alarm parameters
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
3. Collect information
a. Collect log information of the main control board using the one-click
method
Run the MML command STR The log has been successfully uploaded to 15
BTSLOG to use the one-click the specified directory. This information
method to collect log information needs to be provided to Huawei.
about the active main control
board.
Obtain a record and photos of the The correct field information has been -
operations by the field engineers. provided to Huawei's engineers.
Onsite Preparation
Obtain the spare Obtain the boards according to the Ensure that the inventory information
parts information provided by the remote about the spare parts received is
maintenance personnel. consistent with that provided by the
remote maintenance personnel.
Operation Procedure Items to Be Confirmed
Prepare the tools Obtain a flat-head screwdriver (M4, Ensure that all the tools are ready and
M6), a Philips screwdriver (M4, M6), are in good conditions.
ESD wrist straps or gloves, a pen,
paper, a multimeter, binding tapes, and
diagonal pliers.
Onsite Handling
1. Check the storage batteries
a. Measure the voltage of batteries
c. Charge batteries
Turn off the power distribution All the indicators on the monitoring 1 The
switch for the corresponding device are off. (It requires 60 minutes to envi
monitoring device if the switch report ALM-25632.) mon
is available, or turn off the fails
input power switch if the
power distribution switch is
unavailable for the
Procedure Items to Be Confirmed Duration Imp
(min.)
corresponding monitoring
device.
If a PMU is used, power off it
by a hot swap.
Turn on the power distribution After the monitoring device starts, the RUN 3
switch for the monitoring device indicator is on.
if the switch is available, or turn The pairing operation on the eBAT or
on the input power switch if the eBOX is complete, and the indicator blinks
power distribution switch is slowly.
unavailable for the monitoring
device.
For the eBAT or eBOX sensor,
perform the pairing operation.
For details, see DBS3900
Installation Guide.
Turn off the power distribution All the indicators on the monitoring 1 The
switch for the corresponding device are off. (It requires 60 minutes to envi
monitoring device if the switch report ALM-25632.) mon
is available, or turn off the fails
input power switch if the
Procedure Items to Be Confirmed Duration Imp
(min.)
Label all the cables connected to All the cables are labeled. 1
the monitoring device.
Disconnect all the cables from The cables are disconnected from the 1 The
the monitoring device. Note monitoring device. envi
that some cable connectors are mon
tightened with captive screws, fails
which must be loosened first.
Loosen the screws or lowering The monitoring device has been removed. 1 The
the ejector levers for the faulty envi
monitoring device, and then mon
remove the device. fails
Insert the standby monitoring Ensure that the standby monitoring device 5
device and tighten the screws on is installed.
the handle to 0.6 N·m (5.31
lbf·in.). If there is a DIP switch
on the monitoring device, set the
DIP switch correctly.
Reconnect the cables between The cables between monitoring devices and 1
monitoring devices and other other devices are correctly connected.
devices according to the labels.
Turn on the power distribution After the monitoring device starts, the RUN 3
switch for the monitoring device indicator is on.
if the switch is available, or turn The pairing operation on the eBAT or
on the input power switch if the eBOX is complete, and the indicator blinks
power distribution switch is slowly.
unavailable for the monitoring
device.
For the eBAT or eBOX sensor,
perform the pairing operation.
For details, see DBS3900
Installation Guide.
Notify the personnel at the The operations required by the remote 1 None
remote maintenance center that maintenance center have been successfully
onsite processing is complete, performed. The remote maintenance center
and ask them to confirm whether has confirmed that onsite processing is
the alarm has been cleared and complete and onsite engineers can leave.
whether the equipment is running
properly. Perform the operations
required by the remote
maintenance center.
Connect the cables back to the Ensure that the cable connections are 1
panel according to the record. consistent with those of the original
monitoring device.
Related Information
None.
Alarm Description
This alarm is reported when the carrier attributes are configured incorrectly.
Alarm Attribute
Alarm ID Alarm Severity Alarm Type Applicable Mode Introduced in
Version...
GBTS: version
28010 Major/Warning Fault G
earlier than
V100R010C10
Alarm Parameters
Name Meaning
Specific Problem Specific problem of the alarm (ARFCN and TRX Type Mismatch, Incorrect
Signaling Channel Configuration, Co-Cell Configuration Error, Carrier
Configuration Error-Configuration, Carrier Configuration Error-RAN Sharing,
Carrier Configuration Error-ARFCN, Carrier Configuration Error-Bandwidth,
Carrier Configuration Error-Frequency, Carrier Configuration Error-Power,
Carrier Configuration Error-UMTS Conflict, Dual RRU Power Sharing
Configuration Error-Bandwidth, RAN Sharing Carrier Configuration Error-
Excessive Power, Carrier Configuration Exceeds Resource Limitation, Co-Cell
Carrier Power Configuration Too Low, Carrier Configuration Error-Antenna,
Antenna Hopping Configuration Error-Mutual Exclusion Between Functions,
Antenna Hopping Configuration Error-Configuration Exceeds RF Capability,
Carrier Configuration Exceeds Device Capability, Baseband and RF interface
processing resource insufficiency, Power Increase Failure)
Impact on System
Alarm Severity Alarm Impact
Warning The carrier cannot be enabled with the antenna hopping function.
Power increase does not take effect.
System Actions
None.
Possible Causes
Software None
Hardware The RF unit is faulty.
Miscellaneous None
Prerequisites
Obtain the product documents and ensure that the following chapters have been read and
understood:
• Safety Information
• Initial Configuration Guide
Before performing this procedure, the following are required:
• Access to other documentation referenced within this procedure.
• Access to the site is secured, if required for on-site activities.
Preprocessing
1. Record alarm information
Procedure Items to Be Confirmed Duration Impact
(min.)
On the U2020, record the All alarm information has been correctly 1 None
following alarm information to recorded.
facilitate subsequent processing:
"Location Information",
"Equipment Alarm Serial
Number", and "Last Occurred".
Run the MML command LST The user does not perform fast and dynamic 10
OPTLOG to obtain the operation configuration to a large number of TRXs in
log. Check whether a user has batches on one BTS.
performed fast and dynamic
configuration to a large number
of TRXs in batches on one BTS.
The interval between batch
processing commands is short.
When a large number of such
commands are executed, the BSC
and BTS cannot process data
timely, leading to abnormal TRX
configuration. Generally, the
alarm can be automatically
cleared within 5 to 10 minutes.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
Locate the alarm and check the The specific problems about the alarm are 1 None
specific problems of the alarm. recorded.
Then, handle the alarm according
to corresponding procedures.
Configuration Handling
1. The steps for troubleshooting ARFCN and TRX type mismatch, or Carrier
Configuration Error-ARFCN, or Carrier Configuration Error-Frequency, or
Carrier Configuration Error-UMTS Conflict are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
Procedure Items to Be Confirmed Duration
(min.)
Run the MML command LST The configured frequencies are within the 1
GTRX to check the frequencies planned frequency range and are consistent
configured on the TRX. with the network planning. During cross-
module frequency hopping, the configured
frequencies are within the frequency range
supported by the associated module.
Run the MML command MOD The parameter settings are modified 1 See
GTRX to modify the frequencies successfully and consistent with the help
on the TRX. planned settings. info
of r
com
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command SET The parameter settings are modified 1 See
GTRXCHAN to modify the type successfully and consistent with the help
of the TRX channel. planned settings. info
of r
com
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command LST The configuration for the multi-site cell is 1
BTSLOCGRP to check whether the consistent with the network planning.
configuration for a co-cell is
consistent with the network
planning.
Run the MML command MOD The parameter settings are modified 1 See
BTSLOCGRP to modify the successfully and consistent with the help
configuration for the co-cell to planned settings. info
be consistent with the network of r
planning. com
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
4. The steps for troubleshooting Carrier Configuration Error-Configuration or RAN
Sharing Carrier Configuration Error-Excessive Power are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command LST The power mode and power configurations 1
GTRXDEV and LST of the TRX, and number of TRXs bound to
TRXBIND2PHYBRD to check
Procedure Items to Be Confirmed Duration
(min.)
Run the MML command SET The parameter settings are modified 1 See
GTRXDEV and RMV successfully and consistent with the help
TRXBIND2PHYBRD and ADD planned settings. info
TRXBIND2PHYBRD to modify of r
the power mode and power com
configurations of the TRX, and
number of TRXs bound to a
channel on an RF module to be
consistent with the network
planning.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
Run the MML command LST The parameter settings are consistent with 1
BTSRXUBP to check whether the the network planning.
values of Sending Receiving
Mode and RANSharing Support
Procedure Items to Be Confirmed Duration
(min.)
Run the MML command SET The parameter settings are modified 1 See
BTSRXUBP to modify the values successfully and consistent with the help
of Sending Receiving Mode planned settings. info
and RANSharing Support to be of r
consistent with the network com
planning.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
j. Check whether the RF board working modes include the GSM mode
1. Run the MML command LST Check that the RF board is configured 1 See
TRXBIND2PHYBRD to query with the GSM mode. help
information about the RF board info
where the faulty TRX is of r
configured. com
2. Run the MML command LST
BTSRXUBP to check whether
the value of Working Standard
includes GSM. If no, run the
MML command SET
BTSRXUBP to modify the
configuration, ensuring that the
Procedure Items to Be Confirmed Duration Imp
(min.)
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
1. Run the MML commands Check that the CPRI interface board type 1 See
LST TRXBIND2PHYBRD and LST is consistent with the network plan. help
BTSRXUBRD to query info
information about the RF board of r
on which the faulty TRX is com
configured.
2. Run the MML command LST
BTSRXUCHAIN to query the
number of the slot where the
CPRI interface board
corresponding to the RRU
chain resides.
3. Run the MML command DSP
BTSBRD to query the board
running parameters and record
the board type.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
5. The steps for troubleshooting Carrier Configuration Error-RAN Sharing are as
follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command LST The parameter settings are consistent with 1
BTSRXUBP to check whether the the network planning.
values of Sending Receiving
Procedure Items to Be Confirmed Duration
(min.)
Run the MML command SET The parameter settings are modified 1 See
BTSRXUBP to modify the values successfully and consistent with the help
of Sending Receiving Mode planned settings. info
and RANSharing Support to be of r
consistent with the network com
planning.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
6. The steps for troubleshooting Carrier Configuration Error- Power are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
If non-co-cell scenario, Run the The parameter settings are modified 1 See
MML command LST GTRXDEV successfully and consistent with the help
and SET GTRXDEV to modify planned settings. info
the power mode and power of r
configurations of the TRX to be com
consistent with the network
planning.
If non-co-cell scenario, Run the The parameter settings are modified 1 See
MML command LST successfully and consistent with the help
BTSLOCGRP and MOD planned settings. info
BTSLOCGRP to modify the of r
configuration for the co-cell to com
be consistent with the network
planning.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
7. The steps for troubleshooting Dual RRU Power Sharing Configuration Error-
Bandwidth are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Query the binding between logical TRX and channel on TRX board
Run the MML command LST The numbers of two involved boards are 1
TRXBIND2PHYBRD to check the recorded. The binding is the same as that
binding between faulty TRX and specified in the network planning.
the boards. Find two boards on
which the alarm is reported.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Query bandwidth
Run the MML command DSP Confirm that the occupied bandwidth of all 1
BTSBRD to check whether the carriers for GSM and non-GSM networks
occupied bandwidth of all does not exceed the supported bandwidth.
carriers for GSM and non-GSM
networks exceeds the supported
bandwidth (select
"RUNPARA(Running
Parameter)" in the "Information
Type" drop-down list).
e. Query FH mode
Run the MML command LST The associated board function is recorded. 1
BTSRXUBP to check whether
Associated Board Function is set
to RF_FH (RF Frequency
Hopping Between Boards). If the
serving TRXs work in inter-
module RF FH mode, go to "
Query the binding between
logical TRX and channel on TRX
board ". Otherwise, go to
"Modify cell frequencies".
g. Query the binding between logical TRX and channel on TRX board
Run the MML command LST All logical TRXs are bound to two RRU 1
TRXBIND2PHYBRD to check the boards, which is consistent with the
binding between the faulty TRX network planning.
and the board.
Run the MML command ADD Ensure that the receive bandwidth 1 See
GCELLFREQ and RMV occupied by all carriers (including the help
GCELLFREQ to modify carrier that reports the alarm) of GSM and info
frequencies of a cell. non-GSM modes does not exceed one of r
board's, and the transmit bandwidth com
Procedure Items to Be Confirmed Duration Imp
(min.)
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
Run the MML command MOD Ensure that the occupied bandwidth of all 1 See
GTRX to modify the frequencies carriers for GSM and non-GSM networks help
on the TRX does not exceed the supported bandwidth, info
and they are consistent with the plan. In of r
addition, ensure that intermodulation hit com
does not occur.
Run the MML command ADD Ensure that the occupied bandwidth of all 1 See
GCELLFREQ and RMV carriers for GSM and non-GSM networks help
GCELLFREQ to modify does not exceed the supported bandwidth, info
frequencies of a cell. and they are consistent with the plan. In of r
addition, ensure that intermodulation hit com
does not occur.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Check TRX configurations
Run the MML command LST Record the number of TRXs bound to the 1
TRXBIND2PHYBRD to query the RF unit where the faulty TRX locates.
binding relationship between the
faulty TRX and the RF unit.
Obtain the number of TRXs
bound to the RF unit where the
faulty TRX locates.
Check whether the number of The binding relationship has been - See
TRXs is consistent with the modified successfully so that it is help
network planning. If no, run the consistent with the network planning. info
MML command RMV of r
TRXBIND2PHYBRD to modify com
the binding relationship
between TRXs and RF units.
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
10. The steps for troubleshooting Co-Cell Carrier Power Configuration Too Low are
as follows:
a. Display the Main Topology tab page
Procedure Items to Be Confirmed Duration
(min.)
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML commands LST The output power of the subsite is 1 See
BTSLOCGRP and MOD consistent with the network planning. help
BTSLOCGRP to check and info
modify Output Power of a of r
subsite. com
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
11. The steps for troubleshooting Carrier Configuration Error-Antenna are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Query TX/RX mode
Run the MML command LST Confirm the TX/RX mode of the RF unit is 1
BTSRXUBP to check whether the consistent with RF hardware capability.
TX/RX mode of the RF unit is
consistent with RF hardware
capability.
Run the MML command SET The parameter settings are modified 1 See
BTSRXUBP to change the successfully and consistent with the help
TX/RX mode of the RF unit planned settings. info
according to the RF hardware of r
capability. com
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Procedure Items to Be Confirmed Duration
(min.)
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Check whether functions that are mutually exclusive with the antenna
FH function are enabled
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML commandLST Check that Cell Antenna Hopping is set to 1
GCELLHOPANT to check whether Yes for the cell served by the TRX
Cell Antenna Hopping is set to reporting an alarm.
Yes for the cell served by the
TRX reporting an alarm.
If the cell served by the TRX Record the bandwidth interval between the 1
reporting an alarm supports maximum and minimum frequencies.
antenna hopping, run the MML
command LST GTRX to query the
configurations of frequencies on
all TRXs of the RF module
carrying the TRX reporting an
Procedure Items to Be Confirmed Duration
(min.)
If the bandwidth interval Check that the TRX frequencies have 1 See
exceeds the RF module been modified successfully, which is help
capability, run the MML consistent with the network planning. info
command MOD GTRX to modify of r
the configurations of com
frequencies on all TRXs of the
RF module and ensure that the
bandwidth interval between the
maximum and minimum
frequencies is within the RF
module capability.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
14. The steps for troubleshooting Carrier Configuration Exceeds Device Capability
are as follows:
a. Display the Main Topology tab page
Procedure Items to Be Confirmed Duration
(min.)
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command LST Record the TRX receive mode. 1
GTRXDEV to check whether
Receive Mode for the TRX is set
to FOURDIVERSITY (Four
Diversity Receiver).
If Receive Mode for the TRX is Check that the parameter has been 1 See
FOURDIVERSITY (Four successfully modified. help
Diversity Receiver), run the info
MML command SET of r
GTRXDEV to set Receive com
Mode to a value other than
FOURDIVERSITY (Four
Diversity Receiver).
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
1. Run the MML command LST 1. Check that the binding relationship 3 See
TRXBIND2PHYBRD to query the between the TRX and board channel is help
binding relationship between consistent with the network plan. info
the faulty TRX and board 2. Check that the RF board supports the of r
channel. GSM mode. com
2. Check whether the binding
relationship is consistent with
the network plan. If no, run the
MML commands RMV
TRXBIND2PHYBRD and ADD
TRXBIND2PHYBRD to modify
the binding relationship to be
consistent with the network
plan.
3. Run the MML command DSP
BTSBRD to query and record the
board running parameters.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
1. Run the MML commands Check that the TX and RX capability of 3 See
LST TRXBIND2PHYBRD and LST the RF board channel is consistent with help
BTSRXUBRD to query the the TX and RX type of the faulty TRX. info
binding relationship between of r
the faulty TRX and board com
channel.
2. Run the MML command DSP
BTSBRD to query the board
basic information and RF board
type to determine the TX and
RX capability.
3. Run the MML command LST
GTRXDEV to query the TX and
RX mode of the faulty TRX.
4. Check whether the TX and
RX capability of the RF board
channel is consistent with the
TX and RX type of the faulty
TRX. If no, run the MML
command SET GTRXDEV to
modify the TX and RX type,
ensuring that the modification
is successful.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
15. The steps for troubleshooting Baseband and RF interface processing resource
insufficiency are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
d. Check the number of the slot where the CPRI interface board resides
1. Run the MML commands Check that the number of the slot where 1 See
LST TRXBIND2PHYBRD and LST the CPRI interface board resides is help
BTSRXUBRD to query consistent with the network plan. info
Procedure Items to Be Confirmed Duration Imp
(min.)
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
1. Run the MML commands Check that the number of TRXs 1 See
LST TRXBIND2PHYBRD and LST configured on the chain is consistent with help
BTSRXUBRD to query the network plan. info
information about the RF board of r
on which the faulty TRX is com
configured.
2. Run the MML command LST
BTSRXUCHAIN to query the
chain configuration.
3. Check whether the number of
TRXs configured on the chain
is consistent with the network
plan. If no, run the MML
command RMV GTRX to remove
TRXs, ensuring that the number
TRXs is consistent with the
network plan.
g. Check whether the alarm is cleared
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
1. Run the MML command DSP Check that the CPRI port status and rate 1 See
BTSCPRIPORT to query are consistent with the network plan. help
dynamic information about the info
CPRI optical port that is of r
connected to the faulty TRX. com
2. Record the CPRI port status
and rate.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
16. The steps for troubleshooting Power Increase Failure are as follows:
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
Run LST TRXBIND2PHYBRD and The channel power, TRX number, and 1
LST BTSRXUBP to query the bandwidth of the downlink coordinating
channel of the downlink transmit TRX do not exceed the hardware
coordinating transmit TRX used specification and are consistent with the
in downlink power increase network plan.
based on the TRX binding
relationship and board TX and
RX modes.
Run the MML command LST This alarm is not included in the command 1
ALMAF to query the active alarms output.
with specified serial numbers.
Remote Handling
1. Notify and assist field engineers
a. Display the Main Topology tab page
If the faulty NE has been located The Main Topology tab page has been 1
on the topology, skip this step. displayed and the alarm NE is selected.
On the U2020, right-click the
alarm and choose "Locate in
Topology" from the shortcut
menu.
On the Main Topology tab page The "MML Command" tab page has been 1
of the U2020, right-click the NE opened successfully.
(If the NE is a BTS, click the
BSC that the BTS belongs to.)
selected in the previous step and
then choose "MML Command"
from the shortcut menu.
Run the MML command DSP The TRX type is consistent with the 1
BTSBRD with Information Type planned type.
set to RUNPARA(Running
Parameter) to check whether the
TRX type is consistent with the
network planning. If inconsistent,
Notify field engineers to replace
the RF unit on site. Ensure that
the new RF unit supports the
configured ARFCNs
Run the MML command LST Check whether no alarm is recorded in the 1
ALMAF to query the records of an command response packet.
active alarm with a specific alarm
serial number.
2. Collect information
a. Collect logs for a faulty board
Run the MML commands STR The logs have been collected correctly. 15
BTSLOG to collect the log for a
faulty board. The log of the main
control board is also needed if the
faulty board is not the main
control board.
Obtain a record and photos of the The correct field information has been -
operations by the field engineers. provided to Huawei's engineers.
Onsite Preparation
Prepare the tools Obtain the following tools: a hammer All the tools are ready and are in good
used to replace the drill, ESD gloves, a vacuum cleaner, a conditions.
RF unit heat gun, a Phillips screwdriver (M3-
M6), a flat-head screwdriver (M3-M6),
a rubber mallet, a COAX crimping
tool, a wire stripper, a guarded blade
utility knife, a cable cutter, an
adjustable wrench (size ≥ 32 mm), a
level, a torque screwdriver, a torque
wrench, a combination wrench, a
multimeter, a marker (diameter ≤ 10
mm), and a measuring tape.
Obtain the spare Obtain the spare RF unit based on the The inventory information about the
RF unit information provided by the remote spare RF unit is consistent with that
maintenance personnel. provided by the remote maintenance
personnel.
Onsite Handling
1. Replace the RF unit
a. Power off the RF unit
Disconnect the power cable All the indicators on the RF unit are off. 5 The
from the RF unit. beco
of se
Rem
main
cann
perfo
on th
frequ
(RF)
conn
to fi
optic
cabl
Record the cable connections to The cable connections to the RF unit have 1
the RF unit. been recorded.
Remove all the cables connected All the cables have been removed from the 5
to the RF unit. These cables are a RF unit.
power cable, optical fibers,
feeders, and interconnection
cables.
Install the RF unit by following The RF unit has been installed securely. 5
the Site Maintenance Guide.
Install cables to the RF unit by Cables are securely installed to the RF unit. 5
following the recorded
Procedure Items to Be Confirmed Duration
(min.)
Install the power cable to the RF After the RF unit is restarted, the RUN 5
unit, and then power on the RF indicator is on for 1s and off for 1s, which
unit. indicates that the RF unit runs properly.
Disconnect the power cable All the indicators on the RF unit are off. 5 The
from the RF unit. beco
of se
Rem
main
cann
perfo
on th
frequ
(RF)
conn
to fi
Procedure Items to Be Confirmed Duration Imp
(min.)
optic
cabl
Record the cable connections to The cable connections to the RF unit have 1
the RF unit. been recorded.
Remove all the cables connected All the cables have been removed from the 5
to the RF unit. These cables are a RF unit.
power cable, optical fibers,
feeders, and interconnection
cables.
Install the RF unit by following The RF unit has been installed securely. 5
the Site Maintenance Guide.
Install cables to the RF unit by Cables are securely installed to the RF unit. 5
following the recorded
connections and the Site
Maintenance Guide.
Install the power cable to the RF After the RF unit is restarted, the RUN 5
unit, and then power on the RF indicator is on for 1s and off for 1s, which
unit. indicates that the RF unit runs properly.
Notify the personnel at the The operations required by the remote 1 None
remote maintenance center that maintenance center have been successfully
onsite processing is complete, performed. The remote maintenance center
and ask them to confirm whether has confirmed that onsite processing is
the alarm has been cleared and complete and onsite engineers can leave.
whether the equipment is running
properly. Perform the operations
required by the remote
maintenance center.
Related Information
None.