gNodeB NR Basic Fault

Analysis and Handling

www.huawei.com

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

 Objectives

⚫ Upon completion of this course, you will be able to:

 Describe the fault type and impact

 Understand the methods of analyzing and handling gNodeB faults

 Troubleshooting the gNodeB fault

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

 Content

1. Fault Analysis and Troubleshooting Overview

2. Cell Fault Analysis and Handling

3. IP Transmission Fault Analysis and Troubleshooting

4. Clock Synchronization Faults Analysis and Troubleshooting

5. NSA Access Fault Analysis and Troubleshooting

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

General Troubleshooting Process
Start

Backing Up Data

Collecting Fault Information

Can the fault scope and type No

be determined?
Yes
Determine the fault scope and type.

Identify the fault cause.

Clear the fault. Contact Huawei.

No
Check whether the fault is
rectified.
Yes
End

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

Collecting Fault Information

⚫ Overview of Information Types and Collection Methods

Information Type Collection Method

Fault symptom, time, location, and occurrence Consult the personnel who report the fault, for
frequency example: Customer service center
Device running status, fault symptoms,
operations before the fault occurs, and Consult maintenance personnel.
measurement after the fault occurs.

Observe the board indicators, the O&M system,

Device software and hardware running status
and the alarm management system

Perform service demonstration, performance

Fault Scope and Impact
measurement, and interface/signaling tracing

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

Common Fault Maintenance Functions

⚫ The common maintenance functions are as follows:

 User tracing

 Interface tracing

 Comparison/Interchange

 Switchover/Reset

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

 Content

1. Fault Analysis and Troubleshooting Overview

2. Cell Fault Analysis and Handling

3. IP Transmission Fault Analysis and Troubleshooting

4. Clock Synchronization Faults Analysis and Troubleshooting

5. NSA Access Fault Analysis and Troubleshooting

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

Basic Concepts of Cells

⚫ CU cell:
 CU cell (NRCELL): NR cells manage DU cells and are added by running the ADD NRCELL command. All
the cells jointly provide coverage for the entire radio network.

⚫ DU cell:
 DU cell (NRDUCELL): NR DU cells manage the physical resources of the cell, including BBP resources and
sectors. NR DU cells are added by running the ADD NRDUCELL command.

RRU SECTOR SECTOREQM

RRU NRDUCELLTRP NRDUCELL NRCELL

COVERAGE
RRU
DU CU

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

The CU Cell is Unavailable
⚫ The CU cell is unavailable: ALM-29841 NR Cell Unavailable

⚫ Possible causes:
 The F1 signaling link for an NR cell is faulty.

 The NRDUCELL bound to an NR cell is faulty.

 The DuplexMode, and FrequencyBand configured for an NRCELL differs from that configured for the
corresponding NRDUCELL .

 Any other conditions leading to cell unavailability exist.

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

The CU Cell is Unavailable (Cont.)

⚫ CU Cell Unavailable Alarm

Alarm ID Alarm Name

29805 gNodeB F1 Interface Fault
25888 SCTP Link Fault
29870 NR Distribution Unit Cell TRP Unavailable

⚫ Check the traffic statistics when the CU cell is unavailable.

Counter ID Counter Name Counter Description

1542460374 VS.SctpLnk.Unavail Number of Times SCTP Link Unavailable
1542460373 VS.SctpLnk.Unavail.Dur Duration of SCTP Link Unavailable

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

The CU Cell is Unavailable (Cont.)

⚫ MML check and handling

No. Fault Category Check Method Recovery Method

1. The DSP NRCELL command output indicates

1 Cell blocked that the cell is blocked. Unblock the cell.
2. ALM-29842 NR Cell Block is reported.
1. The ACT NRCELL or DSP NRCELL command
output indicates that the cell setup failure is caused
by F1 faults. 1. Clear the alarm with the
The F1 interface is 2. ALM-29805 gNodeB F1 Interface Fault is recommended actions.
2
faulty. reported. .
3) Query the counters of the related SCTP link.
VS.SctpLnk.Unavail
VS.SctpLnk.Unavail.Dur

1. The DSP NRCELL command output indicates

that the NRDUCELL is unavailable. "Troubleshooting
The NRDUCELL is
3 2. The NR DU cell corresponding to the NR cell NRDUCELL
unavailable.
configured by NRCELL cannot be queried by Unavailability."
running the DSP NRDUCELL command.

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

CU Cell Unavailable

⚫ Cell Blocking:
◼ Check whether the Cell Latest State Change Reason field in the DSP NRCELL command output is NR Cell Blocked.

◼ Alternatively, check whether ALM-29842 NR Cell Blocked is generated.

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

CU Cell Unavailable

⚫ DU Cell Unavailability:
 In the DSP NRCELL command output of the faulty cell, check whether the value of the Cell Latest State
Change Reason field is NR DU Cell Unavailable.

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

The DU Cell is Unavailable

⚫ The following alarms are reported when the DU cell is unavailable:

 ALM-29870 NR DU Cell TRP Unavailable

 ALM-29871 NR DU Cell TRP Capability Degraded

⚫ The following table lists the traffic statistics to be checked when the NR DU CELL is unavailable.

Counter ID Counter Name Counter Description

1593835767 VS.RADIOEQM.Avail.Dur RF Unit Availability Duration

1593835676 VS.RADIOEQM.DL.Pwr.Max Maximum RF Unit TX Power

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

The DU Cell is Unavailable (Cont.)
⚫ Alarms associated with ALM-29870 NR DU Cell TRP Unavailable
Alarm ID Alarm Name Alarm ID Alarm Name
26230 BBU CPRI Optical Module Fault 26235 RF Unit Maintenance Link Failure
26819 Data Configuration Exceeding Licensed Limit 26538 RF Unit Clock Problem
26264 System Clock Unlocked 26524 RF Unit PA Overcurrent
26210 Board Blocked 26545 RF Unit TX Channel Switched Off Through Command
26200 Board Hardware Fault 26529 RF Unit VSWR Threshold Crossed
26104 Board Temperature Unacceptable 26503 RF Unit Optical Module Transmit/Receive Fault
26203 Board Software Program Error 26272 Inter-System RF Unit Parameter Settings Conflict
26205 BBU Board Maintenance Link Failure 26120 GPS Clock Output Unavailable
26252 Board Unrecognizable 26121 GPS Antenna Fault
26251 Board Type and Configuration Mismatch 26122 GPS Locked Satellites Insufficient
26204 Board Not In Position 26123 GPS Maintenance Link Failure
26214 Board Powered Off 26260 System Clock Failure
26253 Board Software Auto-Supply Failure 26261 External Clock Reference Not Configured
26254 Board Software Synchronization Failure 26262 External Clock Reference Problem
26533 RF Unit Software Program Error 26263 IP Clock Link Failure
26532 RF Unit Hardware Fault 26818 No License Running in System
26525 RF Unit Temperature Unacceptable

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

The DU Cell is Unavailable (Cont.)

⚫ Handling Procedure

Configuration Issue

RF Fault

Baseband Fault

NR DU Cell CPRI bandwidth insufficient

Unavailable
Abnormal Clock

Insufficient license resource

F1 Fault

Failed to check the delay

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

 The DU Cell is Unavailable (Cont.)

⚫ Faults leading to NR DU cell unavailability

Fault category Check Method Recovery Method

The NRDUCELL TRP is not Run the ADD NRDUCELL TRP command to add the correct
LST NRDUCELLTRP
configured. configuration.

1. The DSP NRDUCELL command output indicates that

The sector equipment
the sector equipment configuration is incorrect. Add or modify the corresponding configuration.
configuration is incorrect.
2. Check the RRU and sector configuration.

The bandwidth configuration is The DSP NRDUCELL command output indicates that Modify the cell bandwidth: MOD NRDUCELL: NrDuCellId=xx,
incorrect. the bandwidth configuration is incorrect. DuplexMode=CELL_TDD, UlBandwidth=XX, DlBandwidth=XX;

Modify the frequency or replace the RRU/AAU. Run the DSP

BRDMFRINFO commands to query the RRU/AAU frequency band
The frequency configuration is The DSP NRDUCELL command output indicates that
range.
incorrect. the frequency configuration is incorrect.
MOD NRDUCELL: NrDuCellId=XX, DuplexMode=CELL_TDD,
UlNarfcnConfigInd=CONFIG, UlNarfcn=xxxx, DlNarfcn=xxxx;
Run the MOD NRDUCELLTRP command to modify the maximum
cell power.
The power configuration is The DSP NRDUCELL command output indicates that
For the maximum output power supported by the RRU, run the
incorrect. the power configuration is incorrect.
DSP BRDMFRINFO，command to query the maximum output
power of the TX channel hardware.

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

The DU Cell is Unavailable (Cont.)
⚫ Faults leading to NR DU cell unavailability

Fault category Check Method Recovery Method

Run the MOD NRDUCELL command to modify the subcarrier spacing of the
Check whether the NR DU Cell Latest State Change
faulty cell:
Unmatched Subcarrier Reason field in the DSP NRDUCELL command
MOD NRDUCELL: NrDuCellId=XX, DuplexMode=CELL_TDD,
Spacing output of the faulty cell indicates unmatched
SubcarrierSpacing=XXXX;
subcarrier spacing.

Check whether the NR DU Cell Latest State Change Run the MOD NRDUCELL command to modify the transmit and receive
Unmatched Transmit and Reason field in the DSP NRDUCELL command mode of the faulty cell:
Receive Modes output of the faulty cell indicates unmatched transmit MOD NRDUCELLTRP: NrDuCellTrpId=XX, TxRxMode=XXXX;
and receive modes.
Check whether the NR DU Cell Latest State Change
Run the MOD NRDUCELLPRACH command to modify the PRACH
Reason field in the DSP NRDUCELL command
configuration index of the faulty cell.
Incorrect PRACH Index output indicates that the value of the
MOD NRDUCELLTRP: NrDuCellTrpId=XX, TxRxMode=XXXX;
PrachConfigurationIndex parameter is out of the
valid range.

1. Perform the following operations one by one:

Check whether the NR DU Cell Latest State Change DEA NRCELL: NrCellId=x; ACT NRCELL: NrCellId=x;
No RF resource is Reason field in the DSP NRDUCELL command RST BRD: CN=x, SRN=xx, SN=x;
available. output of the faulty cell indicates unavailable RF RST BTSNODE:;
resources. 2. Handle the alarm according to the suggestions provided in Alarm
Reference.

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

 The DU Cell is Unavailable (Cont.)
⚫ Faults leading to NR DU cell unavailability
Fault category Check Method Recovery Method
A. The AAU Version Does Not Match the BBU
Version： Run the following command to manually add software:
Check whether ALM-26253 Board Software SPL SOFTWARE: MODE=IPV4, IP="X.X.X.X", USR="XXX", PWD="*****", SDL=YES;
Auto-Supply Failure is reported for the AAU
and is not cleared.

Abnormal RF Units 1. Perform the following operations one by one:

B.Other Exceptions: DEA NRCELL: NrCellId=x; ACT NRCELL: NrCellId=x;
Check whether the Cell Latest State Change RST BRD: CN=x, SRN=xx, SN=x;
Reason field in the DSP NRDUCELL RST BTSNODE:;
command output indicates abnormal RF units. 2. Collect and send the one-click logs of the MPTs, BBPs, and AAUs of the site to the
R&D personnel for analysis.

1. Check whether the NR DU Cell Latest State

Change Reason field in the DSP NRDUCELL
command output of the faulty cell indicates
No baseband unavailable baseband resources.
Reset the BBP. If the problem persists, replace the BBP.
resource is available 2. In the DSP BRD command output, the
value of the Config Type field is UBBP-W and
the value of the Operational Status field is
Disabled.

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

The DU Cell is Unavailable (Cont.)
⚫ Faults leading to NR DU cell unavailability
Fault
Check Method Recovery Method
category
Check whether the Cell Latest State Change Reason field in the DSP NRDUCELL command output indicates abnormal baseband units.
1. Perform the following operations one by one:
DEA NRCELL: NrCellId=x; ACT NRCELL: NrCellId=x;
A. BBP Faults:
RST BRD: CN=x, SRN=xx, SN=x;
There are alarms related to the baseband processing board.
RST BTSNODE:;
2. Replace the BBP.
B.Inconsistent Baseband Equipment IDs:
Run the following command to change the value of the BasebandEqmId
Check whether the value of the BASEBANDEQMID parameter in
parameter in the NRDUCellTrp MO to the actual baseband equipment ID:
the BASEBANDEQM MO is the same as that of the
The MOD NRDUCELLTRP: NrDuCellTrpId=XX, BasebandEqmId=XX
BasebandEqmId parameter of the faulty cell in the NRDUCellTrp
baseband MO. If not, the baseband equipment IDs are inconsistent.
units are C. Incorrect Baseband Equipment Cabinet, Subrack, and Slot
faulty. Configurations: Run the following command to change the cabinet, subrack, and slot numbers
Check whether the cabinet, subrack, and slot numbers in the in the BASEBANDEQM MO to the actual values:
BASEBANDEQM MO are consistent with the actual cabinet, MOD BASEBANDEQM: BASEBANDEQMID=xx,
subrack, and slot numbers configured of the BBP. If not, the BASEBANDEQMTYPE=ULDL, OPMODE=ADD, CN=xx, SRN=xx, SN=xx;
baseband equipment cabinet, subrack, and slot numbers are
incorrect.
D. Blocked BBPs:
Run the following command to unblock the BBP:
In the DSP BRD command output, the value of the Config Type
UBL BRD: CN=x, SRN=x, SN=x;
field is UBBP-W and the value of the Administrative State field is
Blocked.

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

 The DU Cell is Unavailable (Cont.)

⚫ Faults leading to NR DU cell unavailability

Fault category Check Method Recovery Method
Check whether the Cell Latest State Change Reason field in the DSP NRDUCELL command output indicates insufficient baseband
processing capabilities.
Currently, CPRI and eCPRI cells cannot be established on the same BBP. Run the following
CPRI and eCPRI Cells Are Configured on
command to bind CPRI and eCPRI cells to different BBPs:
the Same BBP.
Insufficient BBU ADD BASEBANDEQM: BASEBANDEQMID=xx, BASEBANDEQMTYPE=ULDL,
Capabilities UMTSDEMMODE=NULL, CN1=xx, SRN1=xx, SN1=xx;
If cells cannot be removed, add BBPs and baseband equipment.
The Number of Cells Exceeds the BBP ADD BRD: SN=x, BT=UBBP-W, BBWS=NR-1;
Specifications ADD BASEBANDEQM: BASEBANDEQMID=xx, BASEBANDEQMTYPE=ULDL,
UMTSDEMMODE=NULL, SN1=xx;
1. Run the MOD RRUCHAIN command to modify the CPRI line rate.
Run the following command to modify the CPRI line rate for a CPRI module:
MOD RRUCHAIN: RCN=XX, TT=TRUNK_CHAIN, AT=LOCALPORT, CONNPORTNUM=1,
CONNCR1=xx, PROTOCOL=CPRI;
Check whether the Cell Latest State Change
Run the following command to modify the CPRI line rate for an eCPRI module:
Insufficient CPRI Reason field in the DSP NRDUCELL
MOD RRUCHAIN: RCN=xx, TT=CHAIN, BM=COLD, AT=LOCALPORT, HSRN=xx, HSN=xx,
Bandwidth command output indicates insufficient CPRI
HPN=xx, PROTOCOL=eCPRI, CR=xx, USERDEFRATENEGOSW=OFF;
bandwidths.
2. Run the following command to start CPRI line rate negotiation:
STR CPRILBRNEG: RCN=xx;
3. Use small form-factor pluggable (SFP) optical modules of enhanced specifications to
replace the existing ones.

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

 The DU Cell is Unavailable (Cont.)

⚫ Faults leading to NR DU cell unavailability

Fault category Check Method Recovery Method
If time synchronization is not configured for TDD cells, run the SET
The DSP NRDUCELL command output indicates
The clock is abnormal. GNBTDDCLKMODESW: ClkUnavlbCellActvSw=ON command to enable
that the clock is abnormal.
the TDD cell to be activated even when the clock is not available.
Apply for the license again and run the following command to load the
Check whether the Cell Latest State Change Reason
license:
Insufficient Licenses field in the DSP NRDUCELL command output
INS LICENSE: DIR="xxxx", FN="xxxx", FLG=YES, MODE=IPV4,
indicates insufficient licenses.
IP="x.x.x.x", USR="xxxxx", PWD="*****", FUNCTIONTYPE=gNodeB;
The cell corresponding to The DSP NRDUCELL command output indicates
Add the cell corresponding to SUL.
the SUL does not exist. that the cell corresponding to SUL does not exist.
Check whether the Cell Latest State Change Reason
Solve the faulty F1 transmission link based on the alarm information for
The F1 interface is faulty. field in the DSP NRDUCELL command output
the transmission link.
indicates an F1 fault.
1. Perform the following operations one by one:
(1) Check whether optical fibers or optical modules are faulty. If yes,
Check whether the Cell Latest State Change Reason remove and then insert or replace the optical fibers or optical modules.
Delay Check Failures field in the DSP NRDUCELL command output (2) Deactivate and then activate the cell.
indicates delay check failures. (3) Reset the BBP.
(4) Reset the AAU.
2. If the problem persists, contact R&D engineers for problem locating.

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

Case 1: DU Cell Unavailable

⚫ Symptom: The cell fails to be activated, and an error message is displayed, indicating that the RF
resource is abnormal.

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

Case 1: DU Cell Unavailable(Cont.)

⚫ Problem analysis:
 Configuration check: Run the LST NRDUCELLTRP command to query the sector equipment ID = 3 bound
to the cell. The TX/RX mode is 64T64R.

 LST SECTOREQM Query the subrack number, slot number, and slot number of the RRU to which the
sector equipment ID is bound. RRU cabinet No. = 0 RRU subrack No. = 63 RRU slot No. = 0

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

Case 1: DU Cell Unavailable (Cont.)

⚫ Problem analysis:
 Run the LST RRU command to query
the ANTNUM=4 configured for the
sector equipment bound to the cell.
The cell activation fails because the
TX/RX mode of the antenna is
inconsistent.

⚫ Solve the problem.

 MOD NRDUCELLTRP After the
TX/RX mode of the antenna is
changed to 4T4R, the cell is
successfully set up.

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

Case 2: DU Cell Unavailable

⚫ Problem description:Three cells of operator M's new 5G site in SDR networking (NR and LTE share
AAUs) fail to be activated. An error message is displayed, indicating incorrect power configurations.

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

Case 2: DU Cell Unavailable (Cont.)

⚫ Problem analysis:
 check the cell configurations on the NR side and calculate the power of the three cells on the
NR side.

◼ The power of NR cell 0 is 119 W.

◼ The power of NR cell 1 is 119 W.

◼ The power of NR cell 2 is 119 W.

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

Case 2: DU Cell Unavailable (Cont.)

⚫ Problem analysis:
 Check the AAUs serving the three cells on the 5G side based on the configurations.

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

Case 2: DU Cell Unavailable (Cont.)

⚫ Problem analysis:
 In co-SDR scenarios, the cabinet, subrack, and slot numbers of the AAUs configured on the LTE side must
be the same as those configured on the NR side. Find the sector equipment and AAU serving the LTE cells
based on the configurations on the LTE side.
◼ Sector equipment 3 serves LTE cells 0, 3, and 6 and corresponds to AAU 150.

◼ Sector equipment 4 serves LTE cells 1, 4, and 7 and corresponds to AAU 151.

◼ Sector equipment 5 serves LTE cells 2, 5, and 8 and corresponds to AAU 152

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

Case 2: DU Cell Unavailable (Cont.)

⚫ Problem analysis:
 Calculate the actual power configured for each AAU based on the cell power calculated on the NR and LTE
sides.
◼ LocalCellID = 0: The RSRP is 13, channel power is 0.81 W, cell power is 51.84 W (0.81 W x 64) (TxRxMode = 64T64R).

◼ LocalCellID = 3: The RSRP is 0, channel power is 0.6 W, cell power is 38.4 W (0.6 W x 64) (TxRxMode = 64T64R).

◼ LocalCellID = 6: The RSRP is 0, channel power is 0.6 W, cell power is 38.4 W (0.6 W x 64) (TxRxMode = 64T64R).

◼ AAU 150 :LTE (LocalCellID = 0, 3, and 6) + NR (NrDuCellTrpId = 0) = (51.84 + 38.4 + 38.4) + 119 W = 247.64 W

◼ The DSP BRDMFRINFO command output shows that the maximum output power supported by the AAU is 240 W. The
actual configured power exceeds the maximum capability supported by the AAU. As a result, the cell fails to be set up.

⚫ Solution
 Modify the LTE cell power configuration

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

 Content

1. Fault Analysis and Troubleshooting Overview

2. Cell Fault Analysis and Handling

3. IP Transmission Fault Analysis and Troubleshooting

4. Clock Synchronization Faults Analysis and Troubleshooting

5. NSA Access Fault Analysis and Troubleshooting

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

General procedure for locating transmission faults

⚫ Generally, transmission faults are

located layer by layer based on the
transport protocol stack.

⚫ Compared with troubleshooting of

LTE IP transmission faults, 5G
troubleshooting of IP transmission
faults covers X2 interface faults in
non-standalone (NSA) scenarios.

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

Differences Between NR and LTE IP Transmission Problems
NSA Network
⚫ Compared with the 4G LTE IP transmission architecture,
the 4G LTE IP transmission architecture has the following
differences:
 In the NSA scenario, the NR S1 has only the user plane and
does not have the S1 signaling plane.

 In the NSA scenario, the X2 interface between LTE-NRs is

added.

SA Network

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

Troubleshooting of Physical Layer Faults
⚫ The following alarm is often reported when physical ports on the base station side are disconnected:
 ALM-25880 Ethernet Link Fault

⚫ If fiber optic cables are used for transmission on the base station side, the following alarms are
often reported:

Alarm Name Alarm Name

ALM-25920 SDH/SONET Loss of Frame Alignment ALM-25928 SDH/SONET RS Trace Identifier Mismatch
ALM-25921 SDH/SONET Loss of Frame ALM-25934 SDH/SONET HP Unequipped Defect
ALM-25922 SDH/SONET Loss of Signal ALM-25935 SDH/SONET HP Signal Label Mismatch
ALM-25923 SDH/SONET AU Loss of Pointer ALM-25936 SDH/SONET HP Trace Identifier Mismatch
ALM-25924 SDH/SONET MS Alarm Indication Signal ALM-25937 SDH/SONET HP Remote Defect Indication
ALM-25925 SDH/SONET MS Remote Defect Indication ALM-25938 SDH/SONET HP Remote Error Indication
ALM-25926 SDH/SONET Loss of Cell Delineation ALM-26220 Transmission Optical Module Fault
ALM-25927 SDH/SONET Optical Port Loopback ALM-26221 Transmission Optical Module Not In Position
ALM-26222 Transmission Optical Interface Error

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

Troubleshooting of Physical Layer Faults (Cont.)

⚫ Possible Cause
 The network cable, fiber optic cable, or optical module is faulty or improperly connected.

 The negotiation modes of an Ethernet port are inconsistent between the two ends.

⚫ Troubleshooting Procedure
 Step 1: Viewing Alarms on the Base Station Side
◼ Check for alarms related to fiber optic cables or optical modules on the base station. Troubleshoot the related problems
by referring to the online help.

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

Troubleshooting of Physical Layer Faults (Cont.)

⚫ Troubleshooting Procedure
 Step 2: Check the status of the physical port.
◼ If the DSP ETHPORT command output shows that the
port status is unavailable, perform the following
operations:
◼ Check whether the FE/GE port is properly connected and
the network cable is normal.
◼ Check whether the peer FE/GE port is normal.
◼ Check whether the port rate and the negotiation mode are
consistent with those of the interconnected device.
◼ Check whether the maximum transmission distance
covered by the network cable is within 100 m.

 Step 3: Check the negotiation mode of the port.

◼ Run the LST ETHPORT command to check whether the
negotiation mode and port rate are consistent with those
on the peer transmission device.

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

Troubleshooting Data Link Layer Faults

⚫ Common Fault Symptoms

 No ARP table

 The base station fails to ping the NMS address

⚫ Possible Cause
 The link layer configuration of the VLAN ID is incorrect.

 The transmission network is faulty.

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

Troubleshooting Data Link Layer Faults (Cont.)

⚫ Troubleshooting Procedure
 Step 1: Check whether the ARP table is normal.

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

Troubleshooting Data Link Layer Faults (Cont.)

⚫ Troubleshooting Procedure
 Step 2: Check whether the VLAN configuration is consistent with the planning

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

Troubleshooting Data Link Layer Faults (Cont.)
⚫ Troubleshooting Procedure
 Step 3: Capture packets or mirror the Ethernet port to analyze the exchange of ARP packets. If the base
station does not send or respond to the ARP request, the base station is considered faulty and further
analysis by R&D engineers is required. If the peer end does not send or respond to the ARP request, the
base station gateway is considered faulty and further analysis by transmission bearer personnel is required.

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

Troubleshooting IP Layer Faults
⚫ Common Fault Symptoms
 When disconnection occurs at the IP layer on the base station side, the following alarms may be
generated: ALM-25885 IP Address Conflict and ALM-25896 IP Remote Loopback

⚫ Possible Cause
 The physical layer or the data link layer is abnormal.

 The IP address or route is not or improperly configured.

 The transmission link is disconnected.

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

Troubleshooting IP Layer Faults (Cont.)
⚫ Troubleshooting Procedure
 Step 1: Check alarms on the base station side
◼ Check whether the physical layer and data link layer are abnormal

 Step 2: Check the routing table

◼ Check whether the IP address and route are not or improperly configured

◼ For a destination route (queried by running the DSP IPRT command): If the destination IP address and route mask of
the service match the destination IP address of the route, the route is properly configured

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

Troubleshooting IP Layer Faults (Cont.)

⚫ Troubleshooting Procedure
 Step 3: Testing Connectivity
◼ During ping tests, use packets of different sizes and with different DSCP values. Typical packet sizes are 20 bytes, 500
bytes, and 1500 bytes and typical DSCP values are 48, 46, 34, 18, 10, and 0

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

Troubleshooting IP Layer Faults (Cont.)

⚫ Troubleshooting Procedure
 Step 4: TraceRT
◼ Check whether the intermediate transmission link is disconnected.

◼ The trace route operation can be used to determine the disconnection scope at the IP layer.

◼ As shown in the following figure, route tracing to the destination address succeeds.

◼ The following figure is abnormal.

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

Troubleshooting IP Layer Faults (Cont.)
⚫ Troubleshooting Procedure
 Step 5: Check whether packet loss occurs on the base station, this step is used to check whether
the intermediate transmission link is disconnected
◼ Check whether the number of discarded bytes (indicated by VS.IP.RxDropBytes) received at the IP layer is
measured

◼ Check whether packet loss items are measured in the DSP IPSTAT command output

◼ If the ping operation fails, you can run the DSP IPSTAT command to query the statistics on sent and received
packets on the base station to check whether packet loss occurs

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

Troubleshooting IP Layer Faults (Cont.)
⚫ Troubleshooting Procedure
 Step 6: Start packet capture or IP layer tracing

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

OM Channel Establishment and OM Channel Fault

⚫ OM Channel Establishment Problem Troubleshooting

 Common problems: The following figure shows the status of a successful PnP-based base station
deployment. If automatic OM channel establishment fails, Failed will be displayed in the Check OM channel
field

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

OM Channel Establishment and OM Channel Fault (Cont.)

⚫ OM Channel Establishment Problem

Troubleshooting
 Remote handling through the U2020
◼ Step 1: For details about the DHCP message
interaction, see the next page.

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

OM Channel Establishment and OM Channel Fault (Cont.)

⚫ OM Channel Establishment Problem Troubleshooting

Message Exchange Networking Scenario Possible Cause Suggestion

The DHCP relay configuration is

abnormal on the layer 3 device near the Check the DHCP relay configuration.
base station side
The U2020 serves as the
DHCP server and layer 3
networking is used between The configuration of the uplink route from Check the route configuration of the
the base station and U2020 the router to the U2020 is abnormal router.
The U2020 does not
receive any DHCP Discover
message from the base The base station does not send any
Check gNodeB
station DHCP Discover message

IP over FE/GE is used on the

The FE/GE port is faulty Check gNodeB Connection
base station side

VLAN isolation is performed The VLAN ID and attribute of the

Check the VLAN configuration of the
between the base station side transmission port on the switch are
transmission port on the switch
and the layer 2 switch improperly configured

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

OM Channel Establishment and OM Channel Fault (Cont.)

⚫ OM Channel Establishment Problem Troubleshooting

Message Exchange Networking Scenario Possible Cause Suggestion

The U2020 receives a DHCP

The configuration data of the base station
Discover message from the Check whether the subrack number, slot
in the deployment list is incorrect or the
base station but does not Not closely related number, and ESN of the base station are
electronic serial number (ESN) is not
return a DHCP Offer consistent with the configuration data.
bound.
message

The U2020 receives a DHCP The U2020 serves as the

The configuration of the downlink route
Discover message from the DHCP server and layer 3
from the U2020 to the base station is Check the route configuration of the U2020
base station and returns a networking is used between
abnormal
DHCP Offer message the base station and U2020

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

OM Channel Establishment and OM Channel Fault (Cont.)
⚫ OM Channel Establishment Problem Troubleshooting
 Remote Troubleshooting
◼ Step 2: Check the connectivity. When the U2020 functions as the DHCP server of a base station and the OM channel is
not secure, ping the next-hop IP address of the base station on the U2020. If the ping operation fails, check the
configuration of the downlink route from the U2020 to the base station. If no problem is found, check the transmission.

◼ Ping command: # ping 10.146.36.113

Normal
◼ Traceroute command: traceroute 10.146.36.113
Result

Abnormal
Result

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

OM Channel Establishment and OM Channel Fault (Cont.)
⚫ OM Channel Establishment Problem Troubleshooting
 Remote Troubleshooting
◼ Step 3: Check the BTS data configuration. Focus on the subrack number, slot
number, ESN, DID binding, and topology. If any of these parameters is incorrect,
the U2020 will not return a DHCP Offer message. In this case, correct the
configuration and restart deployment.

◼ Step 4: Check the U2020 SSL link status. If the DHCP process is normal and the
U2020 can successfully ping the base station, change the connection mode of
the base station to the non-SSL mode to check the SSL status.

◼ Step 5: Check whether the transmission device shields the TCP connection port
number of the OM channel. If the TCP connection fails when the DHCP process
is normal and the U2020 can successfully ping the base station, check the
settings of the transmission firewall to determine whether source port 6007 and
destination ports 1024 to 65535 are shielded.

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

OM Channel Establishment and OM Channel Fault (Cont.)

⚫ OM Channel Establishment Problem Troubleshooting

 Onsite Troubleshooting
◼ Step 1: Check whether the DHCP Switch is enabled.

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

OM Channel Establishment and OM Channel Fault (Cont.)

⚫ OMCH Faults Troubleshooting

 Common symptoms: The U2020 reports the ALM-301 NE Is Disconnected alarm.

 Remote Troubleshooting
◼ Step 1: Check the connectivity.

◼ Step 2: Check the U2020 SSL link status.

◼ Step 3: Check whether the transmission device shields the port number of the OMCH TCP connection.

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

OM Channel Establishment and OM Channel Fault
⚫ OMCH Faults Troubleshooting
 Onsite Troubleshooting
◼ Step 1: Check alarms on the base station side.

◼ Step 2: Check the connectivity

◼ Step 3: Perform IP Transmission Self-Check

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

Troubleshooting SCTP Link Faults
⚫ Common fault symptoms are as follows: When SCTP link disconnection occurs, ALM-25888 SCTP
Link Fault may be generated

⚫ Possible causes:
 Any fault occurs at the physical layer, data link layer, or IP layer.

 Incorrect parameter settings at the two ends of an SCTP link cause negotiation failures. The settings include
IP address, VLAN ID, and port number

⚫ Troubleshooting Procedure
 The method of troubleshooting SCTP link disconnection is as follows:
◼ Check for alarms related to the SCTP link.

◼ Check whether related alarms are generated at the physical layer, data link layer, and IP layer.

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

Troubleshooting SCTP Link Faults (Cont.)
⚫ Troubleshooting Procedure
 Step 1: Check the IP layer connectivity. Specify the ping packet size (32Bytes and 1500Bytes) and the
DSCP value from the SCTP local address PING SCTP peer address. If the ping fails, rectify the fault by
referring to the troubleshooting procedure at the IP layer. If the fault persists, go to the next step.
 Step 2: Analyze the SCTP fault diagnosis Based on the diagnosis results, determine the next check
scheme. The following table describes the possible diagnosis results.

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

Troubleshooting SCTP Link Faults (Cont.)
⚫ Troubleshooting Procedure
 Step 3: SCTP signaling tracing
◼ The four steps of the SCTP link establishment are as follows:

◼ The SCTP heartbeat detection process is as follows:

⚫ Step 4: Start packet capture or IP layer tracing, If you need to check whether packets are normally
sent and received at the transport layer of the base station, trace messages at the transport layer
(MAC tracing/IP layer tracing) and analyze the exchange process such as through SCTP message
tracing.

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

Troubleshooting the QoS Problem of the SCTP Link
⚫ Common fault symptoms are as follows: The alarms related to the signaling link congestion on the
BTS side are as follows: ALM-25889 SCTP Link Congestion
⚫ Possible causes:
 The QoS of the transmission network is poor
 Intermittent disconnection occurs due to incorrect parameter settings at the two ends of the SCTP link
 The end-to-end MTU size is improperly configured, which causes loss of large packets
 The SCTP control plane is congested due to heavy traffic on the upper layer

⚫ Troubleshooting Procedure
 The method of troubleshooting signaling link congestion is as follows: Check for alarms related to the
signaling link. Then check whether related alarms are generated at the physical layer, data link layer, and IP
layer. If any alarm exists, clear the alarms based on the alarm information. Check whether parameter
settings at the two ends of the signaling link are consistent or proper. Analyze the signaling tracing result

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

Troubleshooting the QoS Problem of the SCTP Link (Cont.)

⚫ Troubleshooting
Procedure
 Step 1: Continuous
PING

 Step 2: TraceRT
Check whether the
MTU and DSCP are
modified.

 Step 3: SCTP Real-

Time Monitoring

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

Troubleshooting the QoS Problem of the SCTP Link (Cont.)

⚫ Troubleshooting Procedure
 Step 4: Check the SCTP traffic statistics. Pay attention to the following counters:
Counter Name Counter Description Check Focus

VS.SctpLnk.RxMaxSpeed Maximum IP packet receive rate on the SCTP link Whether the maximum bandwidth of the base station is reached

VS.SctpLnk.RxMeanSpeed Average IP packet receive rate on the SCTP link Whether the maximum bandwidth of the base station is reached

VS.SctpLnk.TxMaxSpeed Maximum IP packet transmit rate on the SCTP link Whether the maximum bandwidth of the base station is reached

VS.SctpLnk.TxMeanSpeed Average IP packet transmit rate on the SCTP link Whether the maximum bandwidth of the base station is reached

VS.SctpLnk.RePkts Number of chunks retransmitted from the SCTP link Whether the transmission QoS is poor

VS.SctpLnk.RxDropPkts Number of discarded IP packets received on the SCTP link Whether packets are received incorrectly

 Step 5: Signaling tracing

 Step 6: Packet capture/IP layer statistics (IP-layer protocol tracing)

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

Troubleshooting User Plane Faults

⚫ Common fault symptoms are as follows: The following alarms are often generated when user-plane
connectivity faults occur on the base station side:
 ALM-25952 User Plane Path Fault

 ALM-25954 User Plane Fault

⚫ Possible causes:
 The physical layer, data link layer, or IP layer is faulty.

 The user plane is not configured or is incorrectly configured, such as the IP address, route, and VLAN ID.

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

Troubleshooting User Plane Faults

⚫ Troubleshooting Procedure
 The method of troubleshooting user-plane path disconnection is as follows:
◼ Check for alarms related to the user plane.

◼ Check whether related alarms are generated at the physical layer, data link layer, and IP layer. If any alarm exists, clear
the alarms based on the alarm information.

◼ Check whether transmission congestion occurs.

◼ Check whether user-plane parameter settings are correct.

 Step 1: Determine the local and peer IP addresses of the faulty user-plane link.

 Step 2: Testing Connectivity

 Step 3: Packet Capture or IP Layer Statistics (GTPU Trace)

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

Troubleshooting QoS Problem of User Plane (Cont.)
⚫ Common fault symptoms are as follows: The following alarm is often reported when user-plane congestion occurs
on the base station side: ALM-28052 IP Path Excessive Packet Loss Rate.

⚫ Possible causes:
 The QoS at the physical layer, data link layer, or IP layer is poor.

 The end-to-end MTU size is improperly configured, which causes loss of large packets.

 The DSCP value is changed by the transmission network, which causes packet loss on user-plane paths when traffic is heavy
and transmission congestion occurs.

⚫ Troubleshooting Procedure
 Step 1: Continuous PING

 Step 2: TraceRT Check whether the MTU and DSCP are modified.

 Step 3: If the MTU and DSCP values are incorrect, confirm with the

transmission department.

 Step 4: User Plane IPPM Performance Measurement

 Step 5: Packet Capture/IP Layer Statistics

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

Troubleshooting NSA X2 Link Faults
⚫ Common fault symptoms are as follows:
 The following alarms are often reported for the gNodeB NSA X2 link faults:
 ALM-25888 SCTP Link Fault
 ALM-29800 gNodeB X2 Interface Fault,
 ALM-25952 User Plane Path Fault (Service Type: gNBX2)
 ALM-25954 User Plane Fault (Service Type: gNBX2)
⚫ Possible causes:
 Any fault occurs at the physical layer, data link layer, or IP layer.
 Incorrect parameter settings at the two ends of the SCTP link or user-plane path causes negotiation failures. The
settings include IP address, VLAN ID, and port number.
⚫ Troubleshooting procedure:
 The method of troubleshooting X2 link disconnection is as follows:
◼ Check for alarms related to the signaling link.
◼ Check whether related alarms are generated at the physical layer, data link layer, and IP layer.
◼ Check whether parameter settings at the two ends of the X2 link are consistent or proper. Analyze the signaling tracing result.

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

Troubleshooting NSA X2 Link Faults (Cont.)

⚫ Troubleshooting procedure:
 Step 1: Query the status of the SCTP link corresponding to the faulty X2 link.

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

Troubleshooting NSA X2 Link Faults (Cont.)
⚫ Troubleshooting procedure:
 Step 2: Check whether the peer eNodeB is configured with an X2 interface.
◼ If the same EMS is used, you can directly switch to the U2020 window of the peer eNodeB. (Right-click the NR NE and
choose Query Available Peer LTE Base Stations from the shortcut menu.)

◼ You can also run the DSP GNBCUX2INTERFACE command to query the ID of the peer eNodeB.

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

 Content

1. Fault Analysis and Troubleshooting Overview

2. Cell Fault Analysis and Handling

3. IP Transmission Fault Analysis and Troubleshooting

4. Clock Synchronization Faults Analysis and Troubleshooting

5. NSA Access Fault Analysis and Troubleshooting

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

Clock Synchronization Fault
ALM-29240 Cell
⚫ The external clock sources of Unavailable

the 5G RAN include GPS and

ALM-26264 System Clock
See the description of
IEEE 1588. When a Unlocked
or
other reasons in the alarm
reference.
ALM-26260 System Clock Failure
synchronization fault occurs,
the base station cannot ALM-26261 External
Clock Reference
ALM-26262 External
Clock Reference
ALM-26200 Board
Hardware Fault
Not Configured Problem
provide services for the cell. In
addition, the following alarms ALM-26122 GPS
Locked Satellites
ALM-26120 GPS
Clock Output
ALM-26123 GPS
Maintenance Link
ALM-26263 IP
Clock Link Failure
Insufficient Unavailable Failure
may be reported:
ALM-26121 GPS See the description of
One of the following alarms IP clock server
Antenna Fault other reasons in the alarm may be reported: fault
reference. ALM-25880 Ethernet Link Fault
ALM-25881 MAC Excessive
Frame Error Rate
ALM-25885 IP Address Conflict
GPS clock source ALM-26222 Transmission
Optical Interface Error
ALM-26223 Transmission
Optical Interface Performance
Degraded

IEEE1588 V2 clock source

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

Clock Synchronization Fault

⚫ The results of synchronization cannot be locked. You can run the DSP CLKSTAT command to
query the results

Key parameters Abnormal Value Normal value

Current clock source Unknown GPS Clock or IP clock

Lost, Unavailable, Jitter, Frequency

Current clock source status Deviation, Phase out scope, and Normal

Inconsistent Clock References

Phase-locked loop status (PLL Status) Fast tracking, holdover, or free running Locked

Clock Synchronization Mode Unknown Time synchronization

⚫ If one of the preceding items is not normal, it indicates that the synchronization is faulty

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

Troubleshooting GPS Clock Faults

⚫ Common symptoms:
 ALM-26122 GPS Locked Satellites Insufficient

 ALM-26120 GPS Clock Output Unavailable

 ALM-26123 GPS Maintenance Link Failure

⚫ Possible causes:
 The configuration is incorrect

 The board is faulty

 The DA value is abnormal

 The GPS clock source is fault

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

Troubleshooting GPS Clock Faults (Cont.)

⚫ Handling process:
 Step 1: Run the MML command LST CLKSYNCMODE to set the
synchronization mode to the required time synchronization.

 Check whether the clock source is properly configure. Run the MML
command LST GPS to check whether the clock source is properly
configured.

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

Troubleshooting GPS Clock Faults (Cont.)

⚫ Handling process:
 Run the MML command DSP GPS to check whether the gNodeB correctly selects a clock source.

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

Troubleshooting GPS Clock Faults (Cont.)

⚫ Handling process:
 Step 4: Verify the DA value , Check the values of the counters listed in the table below. If the maximum and
minimum DA values of the gNodeB deviate towards a single direction and the deviation is greater than 500
compared with the central DA value, there may be an interference source.

1593835647 VS.Node.ClockDA.CurrentDA.Max Maximum Current DA Value of the Base Station Clock

1593835648 VS.Node.ClockDA.CurrentDA.Min Minimum Current DA Value of the Base Station Clock
1593835649 VS.Node.ClockDA.CenterDA Center DA Value of the Base Station Clock

 Handle alarms. Please handle the following alarms with the recommended actions in the alarm reference if
any of them is reported:
◼ ALM-26200 Board Hardware Fault

◼ ALM-26122 GPS Locked Satellites Insufficient

◼ ALM-26120 GPS Clock Output Unavailable

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

Troubleshooting IEEE 1588 V2 Clock Faults

⚫ Common symptoms: ALM-26263 IP Clock Link Failure

⚫ Possible causes: If the gNodeB fails to receive synchronization packets from a clock source, the
external clock source is lost. This issue can be caused by the following reasons:
 The transmission network becomes faulty and the gNodeB fails to receive synchronization packets from a
clock source. The clock link is disconnected.

 Large amounts of packet loss appears in the transmission network. The clock packets are discarded due to
the unstable transmission. The gNodeB fails to continuously receive synchronization packets from a clock
source and the clock link is disconnected.

 The network firewall imposes restrictions on ports and shuts down the transmission port (319 or 320) for
transmitting clock packets. Therefore, IP clock packets cannot reach the gNodeB.

 The IP clock server is abnormal.

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

Troubleshooting IEEE 1588 V2 Clock Faults (Cont.)

⚫ Handling process:
 Step 1: Check whether the clock synchronization
mode is set to a specified mode . Run the MML
command LST CLKSYNCMODE to check the
synchronization.

 Step 2: Run the MML command LST IPCLKLINK to

check whether the clock source is properly
configured.

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

Troubleshooting IEEE 1588 V2 Clock Faults (Cont.)
⚫ Handling process:
 Step 3: Check whether the IP clock server can be pinged.
◼ Run the MML command LST IPRT to check whether there is a route to the IP clock server. If there is no route to the IP
clock server and the IP addresses of the gNodeB and IP clock server are not configured in the same segment, run the
MML command ADD IPRT to add a route.

◼ If the IP clock server can be pinged, check whether there is jitter or delay by using the IP clock data collection function
on the U2020 .

 Step 4: License authorized. In normal cases, License Authorized in the DSP CLKSRC command output
can be Allow or Not Limit. Check whether the License Authorized is Allow. If License Authorized is
Forbid, apply for a license supporting gNodeB synchronization

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

Troubleshooting IEEE 1588 V2 Clock Faults (Cont.)

⚫ Handling process:
 Step 5: Run the DSP IPCLKLINK:LN=0; command to check whether the eNodeB selects a clock source
successfully.

◼ If the current reference clock source has been activated, the clock source has been selected successfully. If the current
reference clock source is available but not activated, run the SET CLKMODE command to set MANUAL to forcibly
select the corresponding clock source.

 Step 6: Handle the ALM-26200 Board Hardware Fault alarm by referring to the Alarm Reference.
Copyright © Huawei Technologies Co., Ltd. All rights reserved. Page72
Troubleshooting IEEE 1588 V2 Clock Faults (Cont.)

⚫ Handling process:
 Step 7: ALM-26263 IP Clock Link Failure
◼ In normal cases, if the external clock source is properly added on the gNodeB, the clock source is physically properly
connected to the gNodeB, and the gNodeB can properly receive clock signals from this clock source, the clock source
state is available. To query the clock source status, run the MML command DSP CLKSRC. Check whether the value of
reference clock source status in the command output is Available.

◼ If the value of clock source state or link available state is Unavailable, check the clock as follows:
– Check whether the physical link between the gNodeB and the clock source is properly connected and is functional.

– Check whether the gNodeB can properly receive clock signals.

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

Troubleshooting IEEE 1588 V2 Clock Faults (Cont.)

⚫ Handling process:
 Step 8: Measure the IP
clock quality and trace IP
clock packets.
◼ In addition, for the IP
clock, check whether
jitter occurs using the IP
clock data collection
function on the U2020. If
the jitter is within ±1.5us
and the change trend is
always the same, it
indicates that the clock is
normal.

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

 Content

1. Fault Analysis and Troubleshooting Overview

2. Cell Fault Analysis and Handling

3. IP Transmission Fault Analysis and Troubleshooting

4. Clock Synchronization Faults Analysis and Troubleshooting

5. NSA Access Fault Analysis and Troubleshooting

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

Access Failure on the LTE Side

⚫ In NSA networking, UEs need to access the LTE network first before establishing connection to NR. When 5G
signals are unavailable, the problem may not be caused by the 5G network. Instead, UEs may fail to access the
LTE network.

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

Access Failure on the LTE Side

⚫ Problem Location
 The CPE does not initiate access to the LTE network because the LTE device-pipe synergy switch is turned
off.
◼ Enable the Swith:
MOD UECOOPERATIONPARA: LocalCellId=X, SpecUserCooperationSwitch=SpecUeIdentifySwitch-1;

 The LTE cell status configuration is abnormal.

 The UE initiates an attach procedure on the LTE network and is rejected by the CN. Contact CN engineers
and terminal engineers to locate the problem.

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

NR Measurement Is Not Delivered

⚫ Symptom: The NR measurement message

is carried in the RRC reconfiguration
message over the air interface. An NR
measurement control message contains the
following information elements (IEs) (key
information includes the NR frequency,
bandwidth, and B1 threshold RSRP):

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

NR Measurement Is Not Delivered (Cont.)

⚫ Possible Causes and Handling Methods

 Run the following command to check whether the NSA switch is turned on: LST NSADCMGMTCONFIG

 Querying the SCG Frequency Configuration: LST NRSCGFREQCONFIG

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

NR Measurement Is Not Delivered (Cont.)

⚫ Possible Causes and Handling Methods

 Query the configuration. Ensure that the LTE cell bandwidth is greater than 5 MHz , if the LTE bandwidth is
less than 5 MHz, NSA is not supported.

 Check whether the EARFCN of the LTE cell is consistent with that of the PCC anchor.

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

NR Measurement Is Not Delivered

⚫ Possible Causes and Handling Methods Board Option 3 Option 3X

 The CAMGTCFG.CellMaxPccNumber parameter is set to 0 (the UMPTe (PDCP
Supported Supported
normal value is 65535). This parameter is used to control the Up)
UMPTe (PDCP
maximum number of CA UEs. Currently, this parameter is also Not supported Supported
Not Up)
used for NSA. Therefore, if this parameter is set to 0, NR cannot be
UMPTa Not supported Not supported
set up.
UMPTb Not supported Supported

UBBPdx Supported Supported

UBBPex Supported Supported

LMPT Not supported Not supported

 The UE does not report the NSA DC capability (check whether the
LBBP Not supported Not supported
UE capability reported by the LTE side carries the R15 field). As a
result, the UE cannot access the network. LBBPdx Not supported Not supported
 The LTE hardware does not support NSA. The LTE NSA hardware
support is as follows:

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

NR Measurement Is Not Delivered

⚫ Possible Causes and Handling Methods

 UE MR-DC capability supports the combination of
candidate PCC and NR SCG frequency. If the UE
capabilities carry the MR-DC capability, the base
station determines whether the LTE-NR band
combinations in the MR-DC capability include the
combination of the candidate PCC and NR SCG
frequency.

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

The NR Cell Cannot Be Measured

⚫ The air interface message reported in the NR

measurement report

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

The NR Cell Cannot Be Measured (Cont.)
NE Check Item Troubleshooting Method Recovery Measures
The NR frequency configuration Check whether the ScgDlArfcn is consistent with
Modify the configuration
is incorrect. gNB SSB
LTE
Check whether the B1 threshold
NsaDcB1ThldRsrp Reduce the NsaDcB1ThldRsrp threshold
is set too high.
RF Weak coverage The actual signal cannot reach the B1 threshold. Optimized coverage
The NR cell status is abnormal. DSP NRCELL Ensure that the cell status is normal.

1. Increase the transmit power of the AAU.MOD

The transmit power of the AAU is Cell Performance Monitoring > AAU Channel NRDUCELLTRP: NrDuCellTrpId=0, MaxTransmitPower=XX;
abnormal. Power Monitoring shows that the output power of 2. Increase the PBCH and synchronization signal power.
the AAU channel is less than 50. MOD NRDUCELLCHNPWR: PbchPowerOffset=2000,
NR
SchPowerOffset=2000.
DSP NRDUCELLCHNCALIB: NrDuCellId=x; Query
AAU Channel Calibration Failure Perform channel calibration again.
the latest channel calibration results.
Cell search fails due to Use the frequency scanner or TUE spectrum
Remove the downlink interference source or modify the center
interference from neighboring 5G scanning function to check whether downlink
frequency.
cells. neighboring cell interference exists.
No NR cell is found because the After the LTE and NR base station factors are
UE Use other UEs to isolate problems.
UE problem excluded, check whether the UE is problem
The number of inter-frequency
Check the number of inter-frequency and inter- Use the inter-frequency MR blacklist to prohibit inter-frequency
measurement objects is too large,
E2E RAT measurement objects for the UE through MRs and check whether the problem is solved.
resulting in slow UE
signaling.
measurement and 3s timeout.

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

B1 Measurement Result Is Reported But No SgNB Addition
Procedure Is Initiated
⚫ After the UE reports the B1 measurement result, the LTE network initiates an SgNB addition
procedure to the cell corresponding to the PCI carried in the B1 measurement result through the X2
interface.

⚫ Troubleshooting:
 Check whether the X2 interface has been established by running the DSP X2INTERFACE command.

 Check whether NrExterCell and NrnRelationShip are correctly configured and correspond to the
configurations on the NR side

 Check whether PCI conflicts exist.

 Check whether the PLMN configured on the 4G is the same as that configured on the 5G.

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

Access Preparation on the NR Side

⚫ The SgNB Add Req message is the

first message sent from the LTE
network due to NSA UE access. The
message carries the bearer setup
message.

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

Access Preparation on the NR Side (Cont.)
⚫ The NR side returns an X2AP_SGNB_ADD_ACK response to the LTE network to inform the LTE
network of the address allocated by the NR side.

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

Access Preparation on the NR Side (Cont.)
⚫ The NR side returns an
X2AP_SGNB_ADD_ACK
response to the LTE network to
inform the LTE network of the
address allocated by the NR side

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

Access Preparation Failure on the NR Side

⚫ Possible Symptom
 No SgNB Add Req Message is received from the X2 Interface on the NR side

 The NR side receives the SgNB Add Req Message but rejects the request

 The NR side Initiates a release procedure immediately After the NR side sends an SgNB Addition Response

 The NR side does not return a response to LTE after receiving the SgNB Addition Request

 The NR side does not receive the SgNB Reconfiguration Complete Message

 The NR side initiates a release immediately after receiving an SgNB Reconfiguration Complete Message

 The LTE side initiates a release immediately after the NR side receives an SgNB Reconfiguration Complete
Message

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

Access Preparation Failure on the NR Side (Cont.)

⚫ Troubleshooting

Problem
Version Items to Be Checked Correction Method
Description
The gNBIntegrityCapb configured for the NR site must have an MOD GNBINTEGRITYCAPB:
ALL intersection with the encryption algorithm configured for the UE. IntegrityAlgoPriority=FIRST,
Otherwise, the SgNB Add will be rejected by the NR. IntegrityAlgo=XXX;
The rejection cause is "No Radio Resources Available". The UE
Modify the frequency combination of LTE and
2.1 MRDC capability does not support the PCC and NR SCG
SgNB Add 5G, or change the UEs.
frequency groups.
is rejected
If the rejection cause is "Transmission resource unavailable",
by NR. ALL Solve the transmission problem.
check whether X2-U or S1-U is disconnected.
The rejection cause is " Cell-not-available". " Check whether the
NCELLPLMNLIST:gNBIdLength configured on the LTE side is Modify the value of gNBIdLength on the LTE
2.1 consistent with the actual GNODEBFUNCTION:gNBIdLength side to be the same as that of 5G.
configured on the 5G, or whether there are conflicting gNBIds on Resolving the gNBId conflicts problem.
the same NMS.

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

Access Preparation Failure on the NR Side (Cont.)

⚫ Troubleshooting

Problem Description Version Items to Be Checked Correction Method

If the rejection cause is "No Radio Resources
Available", check whether the 5G NSA switch is turned
on, NRCELLALGOSWITCH: NsaDcSwitch=ON； Turn on the NSA switch.
All
Check whether the Number of UEs in RRC Connected Apply sufficient licenses.
Mode License (NR) /RE (Resource Unit) License(NR) is
SgNB Add is sufficient
rejected by NR.
The rejection cause is "unknown MME code". Check This field is transparently transmitted and is
whether the 5G is configured as an MOCN cell and sent from the MME. Confirm the
2.1 whether the SgNB Add Req message send by the LTE S1AP_INITIAL_CONTEXT_SETUP_REQ
does not contain the servingPLMN field in the delivered by the MME does not carry this
handoverRestrictionList. field. If yes, contact MME side to solve it
After receiving the
SGNB_ADD_REQ_
The LTE initiates a release cause "bearer-operation- The RLC mode of the QCI corresponding to
ACK message, the
All not-supported". Check whether the RLC mode of the the LTE and 5G must be set to the same
LTE network
QCI is consistent between the LTE and 5G. value.
immediately
releases the SCG.

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

NSA Access Failure Case

⚫ Symptom:
 On a newly deployed site, the SGC add are rejected by the
gNodeB, X2AP_SGNB_ADD_REJ and no-radio-resources-
available-in-target-cell.

⚫ Troubleshooting:
 The MRDC of the UE capability of the CPE is (LTE Band39+
NR Band79), the bandCombinationIndex of the
X2AP_SGNB_ADD_REQ is 0x5 (5), it means the frequency
band combination is LTE Band39+ NR Band78. The
verification fails, and the 5G returns a rejection message to
the LTE.

⚫ Solution:
 Configure the EARFCN of on the LTE side and the frequency
information of the NR side to be consistent with those
reported by the CPE.

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

 Summary

⚫ Fault Analysis and Troubleshooting Overview

⚫ Cell Fault Analysis and Handling

⚫ IP Transmission Fault Analysis and Troubleshooting

⚫ Clock Synchronization Faults Analysis and Troubleshooting

⚫ NSA Access Fault Analysis and Troubleshooting

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

 Thank You
www.huawei.com

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