OMD-LTE TDD Guide To Avoiding Problems On The Live Network-20141215-A-V3.4

LTE TDD Guide to Avoiding
Problems on the Live Network
Issue 3.4
Date 2021-04-15
HUAWEI TECHNOLOGIES CO., LTD.

Copyright © Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior
written consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective
holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei
and the customer. All or part of the products, services and features described in this document may
not be within the purchase scope or the usage scope. Unless otherwise specified in the contract, all
statements, information, and recommendations in this document are provided "AS IS" without
warranties, guarantees or representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in
the preparation of this document to ensure accuracy of the contents, but all statements, information,
and recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue 3.3 (2021-04-15) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co.,
Ltd.
LTE TDD Guide to Avoiding Problems on the Live Network About This Document
About This Document
Author
Prepared By TDD Network Basic Date 2014-12-08
Performance Dept, WN
Reviewed By Wireless Product Maintenance Date 2021-04-15
Dept, GTAC, and CTAC
Change History
Date Version Description Author
2012-07-13 1.00 Completed the draft. WTL Network

I&V and
Maintenance
Dept, WN
2012-07-26 1.10 Added section 2.1"Multiple Versions." Sun Wenhai
(employee ID:
00131809)
2012-08-08 1.20  Added section 2.3.6"Equipment Certificate Sun Wenhai
of eNodeB Cannot Be Updated." (employee ID:
 Added section 2.1.13"Some RRUs in an 00131809)
SFN Cell Become Faulty and Recover
Repeatedly, Resulting in UE Network
Access Failures."
2012-08-21 1.30 Added the following sections: Sun Wenhai

 2.2.3ALM-26235 RF Unit Maintenance (employee ID:
Link Failure Alarm Is Reported 00131809)
 2.3.7FMU Electronic Label Fails To Be
Obtained After the FMU Is Changed
 Error: Reference source not found
 2.3.13Incorrect Value LLT1POWER01 of
License Identifier Is Displayed in the
Output of DSP LICENSE
Updated solutions to the following sections:
 2.3.2Internet Protocol (IP) Address
Conflicts Cannot Be Detected
 2.3.3ALM-29240 Cell Unavailable Is
Reported
 2.3.4Certificate Cannot Be Updated
 2.3.5CRL File Cannot Be Obtained
 2.3.6Equipment Certificate of eNodeB
Cannot Be Updated
2012-09-11 1.40 Added the following sections: Sun Wenhai
 Error: Reference source not found (employee ID:
00131809)
 2.1.1RET Configuration Is Unavailable on
the CME When the Built-in Template Is
Used to Configure eNodeBs
 2.3.9PMU/TCU Manufacturer Information
Is Incorrect
 2.3.10There Is a Possibility that ALM-
26529 RF Unit VSWR Threshold Crossed
Is Reported After the RRU3702 Is Soft-
Reset
 2.3.11Message Indicating that the Object
Does Not Exist Is Displayed After the
MOD RETPORT Command Is Run
2012-09-27 1.50 Added section 2.3.15"Cell Setup Fails Sun Wenhai
Because the Maximum Transmit Power of (employee ID:
Cells Is Larger than the Maximum Power 00131809)
Specified by RRUs After eNodeBs Are
Upgraded to V100R005C00SPC300 or Later.
"
Updated the following sections:
 2.3.13Incorrect Value LLT1POWER01 of
License Identifier Is Displayed in the
Output of DSP LICENSE
 Error: Reference source not found
2012-10-24 1.60 Added the following sections: Jiang Lin

 2.3.19The Time on the eNodeB Cannot Be (employee ID:
Synchronized and ALM-26266 Time 00188199)
Synchronization Failure Is Reported When
the Master NTPC Cannot Be Changed
Using the CME
 2.3.20Transmission Is Interrupted over 15
Minutes When IPsec Is Enabled on the
eNodeB, and the O&M Link Cannot
Recover Immediately After Transmission
Is Normal
 2.3.21When Transmission Recovers After
Being Interrupted Over 15 Minutes, ALM-
25902 Remote Maintenance Link Running
Data and Configuration Mismatch Is
Reported When You Log In to the
eNodeB Using the M2000
 2.3.22The Error Message (employee ID:
"PACKETFILTER: When 00188199)
SubboardType's value is
[BASE_BOARD], FilterMode's value
should be [ADV_ACL, L2_ACL,
ADV_AND_L2], but now the value is
NULL." Is Displayed on the M2000
During CME Calibration
 2.3.23CRL Configurations Cannot Be
Saved after the CME Is Used to Modify
eNodeB CRLTSK Settings and the
eNodeB Obtains the CRL Certificate
2012-11-20 1.80 Added section 2.3.24"(For Upgrade Jiang Lin
Scenarios) ALM-26223 Transmission Optical (employee ID:
Interface Performance Degraded or ALM- 00188199)
26222 Transmission Optical Interface Error Is
Reported After the eNodeB Is Upgraded to
V100R005C00SPC340 or Later Versions."
2012-12-03 1.90 Added section 2.3.25"The Cell Status Cannot Jiang Lin
Be Automatically Updated and Operator (employee ID:
Information Is Not Updated in the System 00188199)
Information After the ADD CELLOP or
RMV CELLOP Command Is Executed in
MOCN Scenarios."
2013-03-08 2.00 Added the following sections: Wu Zhi

 2.1.2Some Tasks Are Running Without (employee ID:
Data Reported in 4 to 5 Hours After 15 or 00139668)
More Performance Monitoring Tasks Are
Started at the Same Time
 2.1.3The SCTP Link Is in the Initialized
State and an S1 Interface Fault Occurs
After the ADD S1SIGIP, ADD MME, and
MOD MME Commands Are Executed in
Sequence
 2.1.4The Link Between the eNodeB and
M2000 Is Occasionally Disconnected
After a Nessus-based Scan Is Performed
on the eNodeB
 2.3.26You Cannot Log In to the Web LMT
Using Windows Resource Manager and
"This user session already exists" Is
Displayed
2013-04-17 2.10  Updated section 2.3.26"You Cannot Log In Wu Zhi
to the Web LMT Using Windows (employee ID:
Resource Manager and "This user session 00139668)
already exists" Is Displayed."
 Added section 2.4.1"eNodeB Repeatedly
Reset Due to Execution of More Than 64
Neighboring Cell Configuration
Commands in the Batch Processing Script.
"
 Multiple Alarms Are Reported on the (employee ID:
M2000 and a Board Is Unavailable After 00188199)
the Board Is Slowly Inserted into the BBU
 After Cells Are Activated and Deactivated,
the Cells Cannot Be Reactivated Using the
Same Batch Processing Script and ALM-
29240 Cell Unavailable Is Reported
00188199)
 2.1.8Newly Configured Data Is
Occasionally Lost When the UMPT Is
Used
 2.1.9ALM-29245 Cell Blocked Cannot Be
Cleared When the CME-based
Incremental Script Is Used to
Simultaneously Deliver the UBL CELL
and ACT CELL Commands

00188199)
 2.1.11IPRT Transmission Is Disconnected
After the IPRT-related DEVIP1 Is Deleted
and DEVIP2 that in the Same Network
Segment as DEVIP1 Is Added on the
CME
 2.1.12MAC Address May Be Lost at the
O&M Port, Causing Disconnection
Between the eNodeB and M2000 and
Service Interruption After UMPT or
LMPT Reset During the IP Address
Modification At the Local Site
 2.1.13Some RRUs in an SFN Cell Become (employee ID:
Faulty and Recover Repeatedly, Resulting 00188199)
in UE Network Access Failures
 2.1.14eNodeB Resets After an RF
Loopback Test Is Enabled for an
Unestablished Cell
 2.1.15After MOD APPCERT Is Executed
to Change an Expired Device Certificate
to the Activated Certificate, a Message
Indicating the Modification Failure Is
Displayed and the eNodeB Resets, and
Then ALM-26841 Certificate Invalid Is
Reported
 2.4.2ALM-26215 Inter-Board Service Link
Failure Is Occasionally Reported If a BBU
Houses Multiple LBBPd Boards
 2.4.3CPRI Line Bit Rate in the DSP
CPRILBR Command Output Occasionally
Differs from the Configured Fixed CPRI
Line Bit Rate After the Baseband
Processing Board Resets
 2.5.1IP Path for the X2 or S1 Interface Is
not Displayed in the LST ENODEBPATH
Command Output After MOD X2 or
MOD S1 Is Executed to Modify the X2 or
S1 Object
 2.5.2Primary Operator's X2 Self-setup Fails
When the X2 Object Is Configured Only
for the Primary Operator on the eNodeB
in RAN Sharing with a Common Carrier
Mode by Running ADD X2

 2.1.16eNodeB Resets Repeatedly After the (employee ID:
Service Ethernet Port of the LMPT 00188199)
Directly Connects to the TP-LINK TL-
HP8MU Hub and the eNodeB Powers On
 2.1.17eNodeB Service Link or the O&M
Channel Is Disconnected or Both Are
Disconnected, and ALM-25891 IKE
Negotiation Failure Is Not Reported on the
eNodeB
 2.5.3Baseband Processing Board Resets
After the License Control Items of the DL
CoMP Feature Are Updated
 2.5.4ALM-25952 User Plane Path Fault Is
Reported, and Other Alarms Cannot be
Reported
 2.5.5Simultaneously Network Accesses or
Handovers of Three or More UEs Fail
After the eNodeB Enables the S1 Self-
Setup Function and the S1 Interface User
Plane Link Is Not Configured
 2.1.18ALM-29240 Cell Unavailable Cannot (employee ID:
Be Cleared After the Cell Is Blocked and 00188199)
Deactivated
 2.2.4ALM-25902 Remote Maintenance
Link Running Data and Configuration
Mismatch May Be Reported When the
eNodeB Automatically Obtains the
OMCH Using the DHCP Mechanism
 2.5.6Some X2 or S1 Interfaces, SCTP
Links, and User-Plane Links Cannot Be
Set Up When More Than 32 SCTP Peers
Are Configured
 2.5.7One of the Two 2T2R RRUs Serving a
Multi-RRU Cell Cannot Be Activated and
the DSP CELL Command Output
Displays "Abnormal Baseband Unit" in
Cell Combination Scenarios
 2.5.8ALM-29243 Cell Capability Degraded
Cannot Be Cleared in an Inter-BBU SFN
Cell

 2.1.19Data Configuration File Downloaded (employee ID:
by Running the DLD CFGFILE 00188199)
Command Fails to Be Activated
 2.1.20Cisco Router May Disable Its Port
Connected to a UMPT
 2.5.9Configuration Files May Fail to Take
Effect After Being Successfully Activated
Using the CME
 2.5.10A Cell Fails to Be Activated
 2.5.11Multi-RRU Cell Reconstructed from
Normal Cells Cannot Be Activated
2014-02-10 2.90 Added the following chapters and sections: Jiang Lin
 2.1.21Reconfiguration May Fail to Take (employee ID:
Effect During Cell Activation 00188199)
 2.1.22A CODR Event Is Falsely Reported
for a Common or LampSite Sleeping Cell
Serving by Multiple LBBP Boards
 3Workarounds for the USU
 3.1.1ALM-29243 Cell Capability Degraded
Is Reported for the BBU Configured for
Primary Serving Cells when Inter-BBU
SFN Cells Are Activated in Multi-BBU
Interconnection Scenarios
2014-03-18 3.0 Added the following chapters and sections: Jiang Lin
 2.1.23Updating Neighboring GERAN Cell (employee ID:
Configurations Using the CME Fails 00188199)
 2.1.24LST EUTRANINTERNFREQ
Command Output Indicates a Non-default
Value of the Frequency Offset After
Neighboring E-UTRAN Frequencies Are
Added Upon Setup or Update of the X2
Interface
 2.1.25Command Fails to Be Executed for
Adding, Removing, or Modifying an
Active SFN Cell or Its Sector After a
Serving RRU Is Removed

 2.1.26Network Access Fails After Fast (employee ID:
ANR Is Enabled 00188199)
 2.1.27Bit Error Rate and Service Drop Rate
Increase in LampSite RF Combination
Scenarios
 2.1.28Checking the CME-based 8T8R RRU
Configuration Fails Due to Failed
Database Query
 2.6.1EUSECTOREQMGROUP and
EUSECTOREQMID2GROUP
Configurations of LampSite Sites Created
Using the Default CME Template Are
Lost
 2.1.29"BBI configuration failed" Is (employee ID:
Displayed When Some Cells Served by an 00188199)
LBBPd Bound with Four or More Cells
Failed to Be Activated
 2.1.30LBBPd Reference Signal Power May
Fail to Take Effect or ALM-29241 Cell
Reconfiguration Failed May Be Reported
After the MOD CELLDLPCPDSCHPA
Command Is Executed Following the
MOD PDSCHCFG Command
 2.1.31The DSP GPS Command Output
Indicates the RGPS Cannot Work
Properly

 2.1.32Packet Retransmissions Increase for (employee ID:
UEs in TM7 or TM8 Scenarios If the RS 00188199)
Power Is Not Set to the Recommended
Value
 2.7.1PER Increases and Cell Throughput
Decreases After TxdDci1aSwitch Is Set to
ON
 2.7.2Number of Preallocated RBs Is Not
Subject to the Limitation on the
Preallocated RB Proportion, Causing
Severe CCI If Preallocation Is Enabled
and Smart Preallocation and DRX Are
Disabled
 2.7.3eNodeB's UE Access and Processing
Performance Deteriorates After an
Incoming Inter-RAT Handover to a Local
Cell If Subframe Configuration 2 Is Used
and ACK Feedback Optimization Is
Enabled
 2.1.33Uplink Scheduling Capacity (employee ID:
Decreases When the 00188199)
UlEnhancedSrSchSwitch Check Box Is
Selected in DRX Scenarios, Resulting in
KPI Deterioration
 2.1.34Handover of a CA UE Fails When
the CA Feature Is Enabled and the
HoWithSccCfgSwitch Check Box Is
Selected
 2.1.35RF Channel Intelligent Shutdown
Function Is Frequently Started and
Stopped When the RfShutdownSwitch
Parameter Is Set to ON, the Number of
UEs in a Non-2T2R and Non-4T4R Cell
Changes Between 0 and Other Quantity,
and the Uplink or Downlink PRB Usage Is
0
LTE TDD Guide to Avoiding Problems on the Live Network Contents
Contents
About This Document....................................................................................................................ii

1 Overview.........................................................................................................................................1
1.1 Purpose...........................................................................................................................................................................1
1.2 Document Update Rules.................................................................................................................................................1
2 Workarounds for the eNodeB.....................................................................................................2

2.1 Multiple Versions............................................................................................................................................................2
2.1.1 RET Configuration Is Unavailable on the CME When the Built-in Template Is Used to Configure eNodeBs..........2
2.1.2 Some Tasks Are Running Without Data Reported in 4 to 5 Hours After 15 or More Performance Monitoring Tasks
Are Started at the Same Time...............................................................................................................................................5
2.1.3 The SCTP Link Is in the Initialized State and an S1 Interface Fault Occurs After the ADD S1SIGIP, ADD MME,
and MOD MME Commands Are Executed in Sequence.....................................................................................................5
2.1.4 The Link Between the eNodeB and M2000 Is Occasionally Disconnected After a Nessus-based Scan Is Performed
on the eNodeB......................................................................................................................................................................6
2.1.5 Multiple Alarms Are Reported on the M2000 and a Board Is Unavailable After the Board Is Slowly Inserted into
the BBU................................................................................................................................................................................7
2.1.6 After Cells Are Activated and Deactivated, the Cells Cannot Be Reactivated Using the Same Batch Processing
Script and ALM-29240 Cell Unavailable Is Reported.........................................................................................................8
2.1.7 ALM-25888 SCTP Link Fault and ALM-29240 Cell Unavailable Are Repeatedly Reported After the LMPT Is
Used and Cell DT Tracing Is Enabled..................................................................................................................................8
2.1.8 Newly Configured Data Is Occasionally Lost When the UMPT Is Used.................................................................10
2.1.9 ALM-29245 Cell Blocked Cannot Be Cleared When the CME-based Incremental Script Is Used to Simultaneously
Deliver the UBL CELL and ACT CELL Commands.........................................................................................................11
2.1.10 An eNodeB May Fail to Restore the O&M Link with the M2000 After Problems for Triggering Transmission
Interruption Have Been Resolved.......................................................................................................................................11
2.1.11 IPRT Transmission Is Disconnected After the IPRT-related DEVIP1 Is Deleted and DEVIP2 that in the Same
Network Segment as DEVIP1 Is Added on the CME........................................................................................................12
2.1.12 MAC Address May Be Lost at the O&M Port, Causing Disconnection Between the eNodeB and M2000 and
Service Interruption After UMPT or LMPT Reset During the IP Address Modification At the Local Site.......................14
2.1.13 Some RRUs in an SFN Cell Become Faulty and Recover Repeatedly, Resulting in UE Network Access Failures
............................................................................................................................................................................................14
2.1.14 eNodeB Resets After an RF Loopback Test Is Enabled for an Unestablished Cell................................................15
2.1.15 After MOD APPCERT Is Executed to Change an Expired Device Certificate to the Activated Certificate, a
Message Indicating the Modification Failure Is Displayed and the eNodeB Resets, and Then ALM-26841 Certificate
Invalid Is Reported.............................................................................................................................................................16
2.1.16 eNodeB Resets Repeatedly After the Service Ethernet Port of the LMPT Directly Connects to the TP-LINK TL-
HP8MU Hub and the eNodeB Powers On.........................................................................................................................17
2.1.17 eNodeB Service Link or the O&M Channel Is Disconnected or Both Are Disconnected, and ALM-25891 IKE
Negotiation Failure Is Not Reported on the eNodeB.........................................................................................................18
2.1.18 ALM-29240 Cell Unavailable Cannot Be Cleared After the Cell Is Blocked and Deactivated..............................19
2.1.19 Data Configuration File Downloaded by Running the DLD CFGFILE Command Fails to Be Activated.............19
2.1.20 Cisco Router May Disable Its Port Connected to a UMPT.....................................................................................20
2.1.21 Reconfiguration May Fail to Take Effect During Cell Activation..........................................................................21
2.1.22 A CODR Event Is Falsely Reported for a Common or LampSite Sleeping Cell Serving by Multiple LBBP Boards
............................................................................................................................................................................................22
2.1.23 Updating Neighboring GERAN Cell Configurations Using the CME Fails...........................................................23
2.1.24 LST EUTRANINTERNFREQ Command Output Indicates a Non-default Value of the Frequency Offset After
Neighboring E-UTRAN Frequencies Are Added Upon Setup or Update of the X2 Interface...........................................24
2.1.25 Command Fails to Be Executed for Adding, Removing, or Modifying an Active SFN Cell or Its Sector After a
Serving RRU Is Removed..................................................................................................................................................24
2.1.26 Network Access Fails After Fast ANR Is Enabled..................................................................................................25
2.1.27 Bit Error Rate and Service Drop Rate Increase in LampSite RF Combination Scenarios......................................26
2.1.28 Checking the CME-based 8T8R RRU Configuration Fails Due to Failed Database Query...................................26
2.1.29 "BBI configuration failed" Is Displayed When Some Cells Served by an LBBPd Bound with Four or More Cells
Failed to Be Activated........................................................................................................................................................27
2.1.30 LBBPd Reference Signal Power May Fail to Take Effect or ALM-29241 Cell Reconfiguration Failed May Be
Reported After the MOD CELLDLPCPDSCHPA Command Is Executed Following the MOD PDSCHCFG Command
............................................................................................................................................................................................28
2.1.31 The DSP GPS Command Output Indicates the RGPS Cannot Work Properly.......................................................29
2.1.32 Packet Retransmissions Increase for UEs in TM7 or TM8 Scenarios If the RS Power Is Not Set to the
Recommended Value..........................................................................................................................................................30
2.1.33 Uplink Scheduling Capacity Decreases When the UlEnhancedSrSchSwitch Check Box Is Selected in DRX
Scenarios, Resulting in KPI Deterioration.........................................................................................................................30
2.1.34 Handover of a CA UE Fails When the CA Feature Is Enabled and the HoWithSccCfgSwitch Check Box Is
Selected...............................................................................................................................................................................31
2.1.35 RF Channel Intelligent Shutdown Function Is Frequently Started and Stopped When the RfShutdownSwitch
Parameter Is Set to ON, the Number of UEs in a Non-2T2R and Non-4T4R Cell Changes Between 0 and Other
Quantity, and the Uplink or Downlink PRB Usage Is 0.....................................................................................................32
2.2 V100R004C00..............................................................................................................................................................33
2.2.1 No ALM-26262 Clock Reference Problem Alarm Is Reported................................................................................33
2.2.2 UE Handovers Are Unavailable................................................................................................................................34
2.2.3 ALM-26235 RF Unit Maintenance Link Failure Alarm Is Reported........................................................................35
2.2.4 ALM-25902 Remote Maintenance Link Running Data and Configuration Mismatch May Be Reported When the
eNodeB Automatically Obtains the OMCH Using the DHCP Mechanism.......................................................................35
2.3 V100R005C000............................................................................................................................................................36
2.3.1 HDLC Link Cannot Be Set Up..................................................................................................................................36
2.3.2 Internet Protocol (IP) Address Conflicts Cannot Be Detected..................................................................................37
2.3.3 ALM-29240 Cell Unavailable Is Reported................................................................................................................38
2.3.4 Certificate Cannot Be Updated..................................................................................................................................39
2.3.5 CRL File Cannot Be Obtained...................................................................................................................................39
2.3.6 Equipment Certificate of eNodeB Cannot Be Updated.............................................................................................40

2.3.7 FMU Electronic Label Fails To Be Obtained After the FMU Is Changed................................................................41
2.3.8 S1 Link May Become Faulty Due to License Restriction After Activation of the eNodeB Configuration File.......42
2.3.9 PMU/TCU Manufacturer Information Is Incorrect...................................................................................................42
2.3.10 There Is a Possibility that ALM-26529 RF Unit VSWR Threshold Crossed Is Reported After the RRU3702 Is
Soft-Reset...........................................................................................................................................................................43
2.3.11 Message Indicating that the Object Does Not Exist Is Displayed After the MOD RETPORT Command Is Run..44
2.3.12 LBBPd Cannot Start Up and ALM-26254 Board Software Synchronization Failure Is Reported After the LBBPd
Replaces an LBBPc............................................................................................................................................................47
2.3.13 Incorrect Value LLT1POWER01 of License Identifier Is Displayed in the Output of DSP LICENSE..................48
2.3.14 Cell Setup Failure Is Reported When a Modified Cell Is Activated.......................................................................48
2.3.15 Cell Setup Fails Because the Maximum Transmit Power of Cells Is Larger than the Maximum Power Specified
by RRUs After eNodeBs Are Upgraded to V100R005C00SPC300 or Later.....................................................................49
2.3.16 CPU Usage Increases Periodically When the Optical Module Not Connected to RRUs Is Inserted into the LBBPd
............................................................................................................................................................................................49
2.3.17 ALM-26200 Board Hardware Fault Persists for Six to Eight Minutes Upon Power-Off, Removal, or Insertion of
the LBBPd During Startup, and Is Cleared After Startup..................................................................................................50
2.3.18 ALM-25891 IKE Negotiation Failure Is Falsely Cleared 15 Seconds After It Is Reported for the eNodeB..........51
2.3.19 The Time on the eNodeB Cannot Be Synchronized and ALM-26266 Time Synchronization Failure Is Reported
When the Master NTPC Cannot Be Changed Using the CME..........................................................................................52
2.3.20 Transmission Is Interrupted over 15 Minutes When IPsec Is Enabled on the eNodeB, and the O&M Link Cannot
Recover Immediately After Transmission Is Normal.........................................................................................................52
2.3.21 When Transmission Recovers After Being Interrupted Over 15 Minutes, ALM-25902 Remote Maintenance Link
Running Data and Configuration Mismatch Is Reported When You Log In to the eNodeB Using the M2000................53
2.3.22 The Error Message "PACKETFILTER: When SubboardType's value is [BASE_BOARD], FilterMode's value
should be [ADV_ACL, L2_ACL, ADV_AND_L2], but now the value is NULL." Is Displayed on the M2000 During
CME Calibration................................................................................................................................................................54
2.3.23 CRL Configurations Cannot Be Saved after the CME Is Used to Modify eNodeB CRLTSK Settings and the
eNodeB Obtains the CRL Certificate.................................................................................................................................55
2.3.24 (For Upgrade Scenarios) ALM-26223 Transmission Optical Interface Performance Degraded or ALM-26222
Transmission Optical Interface Error Is Reported After the eNodeB Is Upgraded to V100R005C00SPC340 or Later
Versions..............................................................................................................................................................................56
2.3.25 The Cell Status Cannot Be Automatically Updated and Operator Information Is Not Updated in the System
Information After the ADD CELLOP or RMV CELLOP Command Is Executed in MOCN Scenarios...........................57
2.3.26 You Cannot Log In to the Web LMT Using Windows Resource Manager and "This user session already exists" Is
Displayed............................................................................................................................................................................58
2.4 V100R005C01..............................................................................................................................................................59
2.4.1 eNodeB Repeatedly Reset Due to Execution of More Than 64 Neighboring Cell Configuration Commands in the
Batch Processing Script......................................................................................................................................................59
2.4.2 ALM-26215 Inter-Board Service Link Failure Is Occasionally Reported If a BBU Houses Multiple LBBPd Boards
............................................................................................................................................................................................60
2.4.3 CPRI Line Bit Rate in the DSP CPRILBR Command Output Occasionally Differs from the Configured Fixed
CPRI Line Bit Rate After the Baseband Processing Board Resets....................................................................................60
2.5 V100R006C00..............................................................................................................................................................61
2.5.1 IP Path for the X2 or S1 Interface Is not Displayed in the LST ENODEBPATH Command Output After MOD X2
or MOD S1 Is Executed to Modify the X2 or S1 Object...................................................................................................61
2.5.2 Primary Operator's X2 Self-setup Fails When the X2 Object Is Configured Only for the Primary Operator on the
eNodeB in RAN Sharing with a Common Carrier Mode by Running ADD X2...............................................................62
2.5.3 Baseband Processing Board Resets After the License Control Items of the DL CoMP Feature Are Updated.........63
2.5.4 ALM-25952 User Plane Path Fault Is Reported, and Other Alarms Cannot be Reported........................................63
2.5.5 Simultaneously Network Accesses or Handovers of Three or More UEs Fail After the eNodeB Enables the S1
Self-Setup Function and the S1 Interface User Plane Link Is Not Configured..................................................................64
2.5.6 Some X2 or S1 Interfaces, SCTP Links, and User-Plane Links Cannot Be Set Up When More Than 32 SCTP
Peers Are Configured.........................................................................................................................................................65
2.5.7 One of the Two 2T2R RRUs Serving a Multi-RRU Cell Cannot Be Activated and the DSP CELL Command
Output Displays "Abnormal Baseband Unit" in Cell Combination Scenarios...................................................................66
2.5.8 ALM-29243 Cell Capability Degraded Cannot Be Cleared in an Inter-BBU SFN Cell...........................................67
2.5.9 Configuration Files May Fail to Take Effect After Being Successfully Activated Using the CME.........................68
2.5.10 A Cell Fails to Be Activated....................................................................................................................................69
2.5.11 Multi-RRU Cell Reconstructed from Normal Cells Cannot Be Activated..............................................................70
2.6 V100R008C01..............................................................................................................................................................71
2.6.1 EUSECTOREQMGROUP and EUSECTOREQMID2GROUP Configurations of LampSite Sites Created Using
the Default CME Template Are Lost..................................................................................................................................71
2.7 BTS3900 V100R009C00..............................................................................................................................................72
2.7.1 PER Increases and Cell Throughput Decreases After TxdDci1aSwitch Is Set to ON..............................................72
2.7.2 Number of Preallocated RBs Is Not Subject to the Limitation on the Preallocated RB Proportion, Causing Severe
CCI If Preallocation Is Enabled and Smart Preallocation and DRX Are Disabled............................................................73
2.7.3 eNodeB's UE Access and Processing Performance Deteriorates After an Incoming Inter-RAT Handover to a Local
Cell If Subframe Configuration 2 Is Used and ACK Feedback Optimization Is Enabled for HARQ...............................74
3 Workarounds for the USU.........................................................................................................75

3.1 USU3900 V100R002C00.............................................................................................................................................75
3.1.1 ALM-29243 Cell Capability Degraded Is Reported for the BBU Configured for Primary Serving Cells when Inter-
BBU SFN Cells Are Activated in Multi-BBU Interconnection Scenarios.........................................................................75
LTE TDD Guide to Avoiding Problems on the Live Network 2 Workarounds for the eNodeB
1 Overview
1.1 Purpose
This document provides guidance for operators and onsite operation and maintenance (O&M)
personnel to avoid recurrence of certain faults and major accidents on the live network.
1.2 Document Update Rules

Huawei updates this document in one of the following scenarios:
 A document update period is specified.
 A new product version is released.
 Problems are found during network operating.
2 Workarounds for the eNodeB
2.1 Multiple Versions

2.1.1 RET Configuration Is Unavailable on the CME When the
Built-in Template Is Used to Configure eNodeBs
Symptom RET configuration is unavailable on the CME when the built-in template
of the CME is used to configure eNodeBs, as shown in the following
figure.
Impact The RET configuration workload increases.
Impacted LTE TDD

RAT
Impacted All versions

Version
Trigger The built-in template of the CME is used to configure eNodeBs, as
Condition shown in the following figure.
Root Cause RET antenna configuration is optional.
Workaround Perform the following workarounds:

1. Choose CM Express > LTE Application > Create eNodeB to
create a site using the built-in template.
In the displayed Create eNodeB dialog box, set Site Version,

Cabinet Type, eNodeB Template Name, Radio Template Name,
and Cell Template Name according to the plan of the live network.
2. In the navigation tree on the left, right-click an eNodeB under Root
and choose Device Panel from the shortcut menu. On the displayed
device panel, click RET. In the displayed dialog box, click to add
the RET configuration.
3. Save the configuration as a new template.
4. Use the new template for eNodeB configurations.
Recovery Implement the workaround to prepare the configuration file again.

Measure
Solution None
Version in This problem is not resolved in the product version, because RET
Which the configuration is optional.
Problem Will
Be Solved
2.1.2 Some Tasks Are Running Without Data Reported in 4 to 5

Hours After 15 or More Performance Monitoring Tasks Are
Started at the Same Time
Symptom Some tasks are running without data reported in 4 to 5 hours after
15 or more performance monitoring tasks are started at the same
time.
Impact No data is reported.
Impacted RAT LTE TDD
Impacted Version V100R004C00 and V100R005C00
Trigger Condition On the M2000, 15 or more performance monitoring tasks are

started at the same time within 30s for one site.
Root Cause Multiple tasks share same resources and resources are released
incorrectly.
Workaround If performance monitoring tasks need to be started on the M2000,
start a task every 30s to 1 min.
Recovery Stop the tasks without data reported and then restart them.
Measure
Solution The related software defect will be rectified.
Version in Which To be determined.

the Problem Will
Be Solved
2.1.3 The SCTP Link Is in the Initialized State and an S1 Interface

Fault Occurs After the ADD S1SIGIP, ADD MME, and MOD
MME Commands Are Executed in Sequence
Symptom The SCTP link is in the initialized state and an S1 interface fault
occurs after the ADD S1SIGIP, ADD MME, and MOD MME
commands are executed in sequence.
Impact An S1 interface fault occurs and the cells cannot be activated.
Impacted Version All V100R004C00 and V100R005C00 versions

Trigger Condition When an S1 interface is set up in end point configuration mode, the
negotiation between the eNodeB and MME takes 10s. After the
MOD MME command is executed within the 10s, this fault occurs.
Root Cause There are limitations in the mechanism for S1 interface and SCTP
link subscription.
Workaround Avoid running the ADD MME and MOD MME commands in the
same batch when an S1 interface is set up in end point configuration
mode. You can combine the two commands into one ADD MME
command.
Recovery Run the MOD MME command again after the fault occurs.
Measure
Solution Reconstruct the SON model.
Version in Which V100R006C00

the Problem Will
Be Solved
2.1.4 The Link Between the eNodeB and M2000 Is Occasionally

Disconnected After a Nessus-based Scan Is Performed on the
eNodeB
Symptom The link between the eNodeB and M2000 is occasionally
disconnected after a Nessus-based scan is performed on the
eNodeB.
Impact  The eNodeB cannot be maintained remotely due to link
disconnection between the eNodeB and M2000.
 The eNodeB cannot be maintained locally due to a failure in
logging in to the Web LMT.
Impacted Version V100R004C00SPH271 and earlier

V100R005C00SPH374 and earlier
V100R005C01SPH305 and earlier
Trigger Condition A security scan using Nessus is performed on the eNodeB.
Root Cause The NCM_RECV task monitored a port (not the port 6007). The
port was selected after three TCP handshakes, and received an RST
packet sent by the Nessus before accepting the request. Then, the
port did not receive any connecting request, and the NCM_RECV
task was blocked and did not handle the connecting request of the
port 6007. As a result, the eNodeB was disconnected from the
M2000.
Workaround Do not perform a security scan using Nessus on the eNodeB.
Recovery 1. Use Nessus to scan the sites with this fault again.
Measure 5. Telnet ports 6000, 6006, and 4443.

the Problem Will
Be Solved
2.1.5 Multiple Alarms Are Reported on the M2000 and a Board Is

Unavailable After the Board Is Slowly Inserted into the BBU
Symptom When a board is slowly inserted into the BBU, the following alarms
are reported on the M2000:
 ALM-26101 Inter-Board CANBUS Communication Failure
 ALM-26200 Board Hardware Fault
 ALM-26841 Certificate Invalid
These alarms are cleared after the main control board resets.
The board can be a main control board or a baseband processing board.
Impact The newly inserted board is unavailable.
Impacted Version V100R004C00SPH271 and earlier versions

V100R005C00SPH374 and earlier versions
V100R005C01SPC300 and earlier versions
Trigger Condition The board is slowly inserted into the BBU.
Root Cause When the board is being slowly inserted into the BBU, the
CANBUS module attempts but fails to obtain the slot number of the
board, causing communication faults.
Workaround Insert the board into the BBU quickly and steadily using both
hands.
Recovery  Locally, reinsert the board.
Measure  Remotely, reset the main control board by running the RST
BRDPWROFF command.
Solution The CANBUS module now obtains the slot number of a newly
inserted board for several times after the board is powered on. If the
obtained slot numbers remain the same, the CANBUS module stops
obtaining the slot number. If the obtained slot numbers differ from
each other, the CANBUS module resets and then attempts to obtain
the slot number again.
Version in Which V100R005C01SPC400 and earlier versions
the Problem Will
Be Solved
2.1.6 After Cells Are Activated and Deactivated, the Cells Cannot
Be Reactivated Using the Same Batch Processing Script and ALM-
29240 Cell Unavailable Is Reported
Symptom After cells are activated and deactivated, the cells cannot be
reactivated using the same batch processing script and ALM-29240
Cell Unavailable is reported.
Impact The cells cannot be reactivated and ALM-29240 Cell Unavailable is
reported.
Impacted Version V100R004C00SPH271 and earlier versions

V100R005C00SPH374 and earlier versions
V100R005C01SPC300 and earlier versions
Trigger Condition The cells are to be reactivated using the same batch processing
script after being activated and deactivated.
Root Cause If cells are deactivated before being successfully activated, some
global variables related to the cells are residual.
Workaround Do not continuously activate and deactivate cells using the batch
processing script.
Recovery 1. Remove the cells by running the RMV CELL command.
Measure 6. Add the cells again by running the ADD CELL command.
7. Activate the cells by running the ACT CELL command.

the Problem Will
Be Solved
2.1.7 ALM-25888 SCTP Link Fault and ALM-29240 Cell

Unavailable Are Repeatedly Reported After the LMPT Is Used
and Cell DT Tracing Is Enabled
Symptom ALM-25888 SCTP Link Fault and ALM-29240 Cell Unavailable
are repeatedly reported after the LMPT is used and Cell DT tracing
is enabled.
Impact No service is available in this cell.
Impacted Version V100R005C00SPC378 and V100R005C00

V100R005C01SPC406 and V100R005C01
Trigger Condition More than three options are selected under the AC Layer Trace
Field check box when the LMPT is used and Cell DT tracing is
enabled at layer 2, as shown in the following figure.
Root Cause A low priority is configured for the queue for receiving eNodeB
internal messages by default, and therefore a delay is generated
when the SCTP link receives messages. In this case, eNodeB
software at the upper layer cannot receive SCTP packets.
Consequently, the SCTP link is interrupted.
Workaround Select a maximum of three options under the MAC Layer Trace
Field check box when enabling Cell DT tracing.
Recovery Clear some options under the MAC Layer Trace Field check box
Measure to allow a maximum of three options to be selected.

the Problem Will
Be Solved
2.1.8 Newly Configured Data Is Occasionally Lost When the
UMPT Is Used
Symptom Newly configured data is occasionally lost if the following
conditions are met:
1. The UMPT is used, and the configuration file exported from the
LMPT or the minimum configuration file is activated.
8. After activation succeeds, an MML command is run for
configuration modification.
9. The eNodeB is reset within 24 hours after the configuration
modification.
Impact Newly configured data is lost. If the data is related to transmission,
the eNodeB cannot be managed.
NOTE
If the CME instead of an MML command is used to modify the
configuration data, no impact occurs.
Impacted Version All patches of V100R005C00

V100R005C01SPC300
Trigger Condition The eNodeB is reset within 24 hours after the minimum
configuration file is activated.
The eNodeB is reset within 24 hours after the configuration file
exported from the LMPT is activated.
Root Cause Multiple tasks simultaneously read and write the trans logs.
Workaround Reset the eNodeB 24 hours later after activating the configuration
file and using an MML command to modify the configuration data.
Recovery  If the eNodeB is still managed, use the backup configuration file
Measure to restore the configuration data or run an MML command to
reconfigure the configuration data.
 If the eNodeB cannot be managed, restore the configuration data
onsite.
Version in Which V100R005C01SPC400

the Problem Will
Be Solved
2.1.9 ALM-29245 Cell Blocked Cannot Be Cleared When the CME-
based Incremental Script Is Used to Simultaneously Deliver the
UBL CELL and ACT CELL Commands
Symptom ALM-29245 Cell blocked cannot be cleared when the CME-based
incremental script is used to simultaneously deliver the UBL CELL
and ACT CELL commands.
Impact ALM-29245 Cell blocked cannot be cleared.
Impacted Version All versions earlier than V100R006C00SPC120
Trigger Condition The CME-based incremental script is used to simultaneously

deliver the UBL CELL and ACT CELL commands.
Root Cause The alarm clearance solution is unavailable for the scenario where
the cell management status and activation status are simultaneously
changed.
Workaround Do not use the CME-based incremental script to simultaneously
deliver the BLK CELL and UBL CELL commands.
Recovery Run the BLK CELL command to block the cell again. Run the
Measure UBL CELL command to unblock the cell again.

the Problem Will
Be Solved
2.1.10 An eNodeB May Fail to Restore the O&M Link with the
M2000 After Problems for Triggering Transmission Interruption
Have Been Resolved
Symptom An eNodeB may fail to restore the O&M link with the M2000 after
problems for triggering transmission interruption have been
resolved in either of the following scenarios:
 Site deployment
 eNodeB power-off and reset
 O&M transmission modification
 External transmission fault
Impact The O&M link between the eNodeB and M2000 is disconnected.
Impacted Version All V100R005C00 versions earlier than V100R005C00SPC340

All V100R005C1 versions earlier than V100R005C01SPC300
Trigger Condition This issue occurs when both the following two conditions are met:
 Devices using the ARP proxy cannot forwards packet to the
M2000.
 The site is newly deployed, the eNodeB powers off and resets, the
transmission settings changes, or the transmission is
disconnected.
Root Cause After Dynamic Host Configuration Protocol (DHCP) procedure
finishes on the eNodeB, a device with the ARP proxy function
receives the ARP messages from the M2000. This leads to that the
packets to be sent to the M2000 do not pass through the route and
are sent to the device using the ARP proxy function. However, the
device does not support packet forwarding. Therefore, the O&M
link between the eNodeB and the M2000 is disconnected.
Workaround Check whether the network has a device with the ARP proxy
function enabled and the device does not support packet forwarding
with the M2000. If yes, disable the ARP proxy function or allow the
device to support packet forwarding.
Recovery Perform the following two operations at the local site:
Measure  Remove and insert the Ethernet cable from and into the Ethernet
port on the eNodeB side.
 Run the RST ETHPORT command to reconfigure the Ethernet
port.
NOTE
The preceding operations may fail sometimes. In this case, try again.
Version in Which LTE TDD V100R005C00SPC340

the Problem Will LTE TDD V100R005C01SPC300
Be Solved
2.1.11 IPRT Transmission Is Disconnected After the IPRT-related

DEVIP1 Is Deleted and DEVIP2 that in the Same Network
Segment as DEVIP1 Is Added on the CME
Symptom The IPRT transmission is disconnected after the IPRT-related
DEVIP1 is deleted and DEVIP2 that in the same network segment
as the DEVIP1 is added on the CME.
Impact The impact varies based on the transmission objects bore on the IP
route:
 Services
Services are interrupted.
 O&M channel
The O&M channel is disconnected.
 Services and O&M channel
Both services and the O&M channel are disconnected.
Impacted Version V100R005C00SPC370 and versions earlier than V100R005C00

V100R005C01SPC406 and versions earlier than V100R005C01
Trigger Condition The IPRT-related DEVIP1 is deleted and then DEVIP2 in the same
network segment as the DEVIP1 is added on the CME.
NOTE
Using MML commands is not involved.
Root Cause DEVIP is the parent object of the IPRT, which takes effect based on
the DEVIP.
When the DEVIP is deleted and then added, the parent object that
the IPRT depends on is deleted. Due to a software defect, the newly
added DEVIP cannot be the parent object for the IPRT. Therefore,
the IPRT has no parent object.
Workaround Do not delete and then add the DEVIP using the CME incremental
scripts.
Recovery Take corresponding measures based on the transmission objects
Measure bore on the IP route:
 Services
Delete and add a route again or reset the eNodeB.
 O&M channel
Delete and add a route again or reset the eNodeB at the local
site.
 Services and O&M channel
Problem can be automatically resolved after the subsystem
abnormally reset.
Solution Change the IPRT's parent object from DEVIP to the
ETH/ETHTRK, which is the parent object of DEVIP.
the Problem Will
Be Solved
2.1.12 MAC Address May Be Lost at the O&M Port, Causing
Disconnection Between the eNodeB and M2000 and Service
Interruption After UMPT or LMPT Reset During the IP Address
Modification At the Local Site
Symptom The MAC address may be lost at the O&M port, causing
disconnection between the eNodeB and M2000 and service
interruption after UMPT or LMPT reset during the IP address
modification at the local site.
Impact The eNodeB is disconnected from the M2000 and services are
interrupted.
Impacted Version All versions of V100R004C00

Trigger Condition The UMPT or LMPT resets during IP address modification at the
local site.
Root Cause The UMPT or LMPT may be lost during IP address modification.
As a result, information about MAC in the flash memory may be
lost.
When the UMPT or LMPT restarts, the numbers in the MAC
address obtained by the RBs are 0, which fails the check. Then, the
transmission module fails to work, and therefore all transmission
are disconnected on the eNodeB.
Workaround Do not modify the IP address at the local O&M Ethernet port.
Recovery Replace the UMPT or LMPT or upgrade the version to

Measure V100R006C00SPC090 at the local site.

the Problem Will
Be Solved
2.1.13 Some RRUs in an SFN Cell Become Faulty and Recover

Repeatedly, Resulting in UE Network Access Failures
Symptom Some RRUs in an SFN cell become faulty and recover repeatedly.
As a result, UEs access and exit the network repeatedly. After the
RRUs recover, UEs cannot access the network.
Impact UEs cannot access the network.

Impacted Version V100R006C00SPC120 and all V100R006C00 versions earlier than
V100R006C00SPC120
V100R005C01SPC406 and all V100R005C01 versions earlier than
V100R005C01SPC406
Trigger Condition Both of the following conditions are met:
 Some RRUs become faulty and recover repeatedly. (ALM-26235
RF Unit Maintenance Link Failure, ALM-26504 RF Unit CPRI
Interface Error, or ALM-26538 RF Unit Clock Problem is
reported.)
 One or multiple UEs access and exit the network for multiple
times.
Root Cause Some RRUs in an SFN cell become faulty and recover repeatedly.
As a result, UEs access and exit the network repeatedly. During this
process, many resources are used, which are not released due to
code bugs. At last, after the RRUs recover, UEs cannot access the
network due to insufficient resources.
Workaround Solve the problem of RRUs in the SFN cell that become faulty and
recover repeatedly.
Recovery Reactivate the SFN cell.
Measure

the Problem Will
Be Solved
2.1.14 eNodeB Resets After an RF Loopback Test Is Enabled for

an Unestablished Cell
Symptom When an RF loopback test is enabled for an unestablished cell, the
eNodeB resets.
Impact The eNodeB resets.

V100R005C01SPC406 and all V100R005C01 versions earlier than
V100R005C01SPC406
Trigger Condition An RF loopback test is enabled for a cell that has not been
established.
Root Cause The eNodeB does not check the validity of the entered cell ID.
When the ID of an unestablished cell is entered, the RF loopback
test is still enabled for the cell. As a result, the eNodeB visits an
illegal memory and resets.
Workaround Do not start an RF loopback test for a cell that has not been
established.
Recovery None
Measure

the Problem Will
Be Solved
2.1.15 After MOD APPCERT Is Executed to Change an Expired

Device Certificate to the Activated Certificate, a Message
Indicating the Modification Failure Is Displayed and the eNodeB
Resets, and Then ALM-26841 Certificate Invalid Is Reported
Symptom When MOD APPCERT is executed to change an expired device
certificate to the activated device certificate, a message indicating
the modification failure is displayed. After the eNodeB resets,
ALM-26841 Certificate Invalid is reported. The IKE or SSL link
negotiated by using this certificate is disconnected, and services and
O&M channels carried on this link are disconnected.
Impact The IKE or SSL link negotiated by using this certificate is
disconnected. Services or O&M channels carried on the link are
disconnected.
Impacted Version V100R004C00 versions

V100R005C00 versions
Trigger Condition MOD APPCERT is executed to change an expired certificate to
the activated certificate and the eNodeB resets.
Root Cause The eNodeB does not check whether the certificate expires.
Workaround Before running MOD APPCERT to change the expired certificate

to the activated certificate, run DSP CERTMK to check whether
the certificate is valid and does not expire.
If the certificate is valid and does not expire, the certificate can be
activated.
If the certificate expires, apply for a new certificate and then
activate the certificate.
Recovery If the eNodeB does not reset, run MOD APPCERT to change the
Measure activated certificate to a normal certificate after ALM-26841
Certificate Invalid is reported.
If the eNodeB resets and not managed by the M2000, contact the
CA to revoke the certificate of the eNodeB and apply for a new
certificate. Alternatively, run MOD APPCERT to change the
activated certificate to a normal certificate.
Solution N/A
Version in Which N/A

the Problem Will
Be Solved
2.1.16 eNodeB Resets Repeatedly After the Service Ethernet Port

of the LMPT Directly Connects to the TP-LINK TL-HP8MU Hub
and the eNodeB Powers On
Symptom When the service Ethernet port of the LMPT directly connects to
the TP-LINK TL-HP8MU hub and the eNodeB powers on, the
eNodeB resets repeatedly.
Impact The eNodeB cannot be started.
Impacted Version V100R004C00 versions

Trigger Condition The service Ethernet port of the LMPT directly connects to the TP-
LINK TL-HP8MU hub, and the eNodeB powers on.
Root Cause If the Ethernet port connects to the PHY of the hub when the LMPT
starts and the Ethernet port is not activated, the Ethernet port is in
the UP state.
When the Ethernet port state is detected as UP in the Ethernet link
detection task, the heartbeat procedure starts.
Before the Ethernet port is activated, the SGMII channel of the
CPU is disabled. In this case, the heartbeat packets cannot be sent to
the FPGA. As a result, the heartbeat link is interrupted, and the
eNodeB resets after 30 seconds.
Workaround Connect the Ethernet port of the eNodeB to a switch instead of a
hub.
Recovery Change the interconnected hub type or change the interconnected
Measure hub into a switch.
Solution Fix the software bug to ensure that whether the Ethernet port is
activated will be monitored after the Ethernet link detection task
starts. If the Ethernet port is not activated, the heartbeat procedure
will not be performed.
the Problem Will
Be Solved
2.1.17 eNodeB Service Link or the O&M Channel Is Disconnected

or Both Are Disconnected, and ALM-25891 IKE Negotiation
Failure Is Not Reported on the eNodeB
Symptom If AH Authentication Algorithm or ESP Authentication
Algorithm is set to SHA256 for an IPsec proposal configured by
running ADD IPSECPROPOSAL, the eNodeB service link or the
O&M channel is disconnected or both are disconnected, and ALM-
25891 IKE Negotiation Failure is not reported on the eNodeB.
Impact If IPsec transmission is adopted only for services, services become
unavailable.
If IPsec transmission is adopted only for the O&M channel, the
O&M channel will be disconnected and the eNodeB cannot be
managed by the M2000.
If IPsec transmission is adopted for both services and the O&M
channel, services become unavailable and the O&M channel is
disconnected.
Impacted Version All versions earlier than V100R005C01 (including V100R004C00

and V100R005C00 versions)
Trigger Condition In the IPsec transmission scenario, AH Authentication Algorithm
or ESP Authentication Algorithm is set to SHA256 for an IPsec
proposal.
Root Cause The implementation of the SHA256 authentication algorithm of the
IPsec protocol is inconsistent with that of standard protocols. As a
result, decryption at two ends fails.
Workaround Do not set AH Authentication Algorithm or ESP Authentication
Algorithm to SHA256 when configuring an IPsec proposal by
running ADD IPSECPROPOSAL.
Recovery If the O&M channel is disconnected, process this problem onsite.
Measure If the O&M channel is normal but services are unavailable, modify
the eNodeB configuration remotely and change AH
Authentication Algorithm or ESP Authentication Algorithm to
values other than SHA256 by running MOD IPSECPROPOSAL.
the Problem Will
Be Solved
2.1.18 ALM-29240 Cell Unavailable Cannot Be Cleared After the

Cell Is Blocked and Deactivated
Symptom ALM-29240 Cell Unavailable cannot be cleared after the cell is
blocked by running the BLK CELL command with the
CellAdminState parameter set to CELL_HIGH_BLOCK(High
block) and is deactivated.
Impact ALM-29240 Cell Unavailable cannot be cleared.
Trigger Condition The cell is blocked by running the BLK CELL command with the
CellAdminState parameter set to CELL_HIGH_BLOCK(High
block) after ALM-29240 Cell Unavailable is reported.
Root Cause The eNodeB does not process ALM-29240 Cell Unavailable after
the cell is deactivated.
Workaround Unblock and then deactivate the cell.
Recovery To clear ALM-29240 Cell Unavailable, perform the following

Measure steps:
1. Unblock the cell.
10. Reactivate the cell.
11. Deactivate the cell.

the Problem Will
Be Solved
2.1.19 Data Configuration File Downloaded by Running the

DLD CFGFILE Command Fails to Be Activated
Symptom After eNodeB configurations are uploaded by running the ULD
CFGFILE command in an eNodeB upgrade, the data configuration
file downloaded by running the DLD CFGFILE command fails to
be activated by running the ACT CFGFILE command.
Impact The data configuration file fails to be activated.

Impacted Version All DBS3900 LTE TDD V100R005C00 versions
All BTS3900 V100R008C00 versions earlier than
V100R008C00SPC233
Trigger Condition  eNodeB software is upgraded from V100R004C00 or an earlier
version to the impacted version.
 The current eNodeB configurations are uploaded by running the
ULD CFGFILE command and the data configuration file
downloaded by running the DLD CFGFILE command is to be
activated by running the ACT CFGFILE command.
Root Cause Before the upgrade, no ALMPORT MO exists under the RRU or
UPEU MO in the data configuration file, which does not meet the
requirements for the mappings between parent and child MOs in the
file. In the upgrade, the eNodeB does not verify the configuration
rules. After the upgrade, when the data configuration file is to be
activated, the configuration rules fail to be verified.
Workaround Before the data configuration file is downloaded by running the
DLD CFGFILE command, run the LST RRU and DSP BRD
commands to check whether the RRU and UPEU have been
configured, and run the LST ALMPORT command to check
whether alarm ports have been configured at the same installation
positions of the RRU and UPEU. If no RRU or UPEU has been
configured or no alarm port has been configured at the same
installation positions of the RRU and UPEU, this problem occurs.
To resolve this problem, remove the RRU or UPEU for which no
alarm port is configured, and then add an RRU or UPEU by running
the ADD RRU or ADD BRD command, respectively.
Recovery Measure See the workaround.
Version in Which BTS3900 V100R008C00SPC233

the Problem Will
Be Solved
2.1.20 Cisco Router May Disable Its Port Connected to a UMPT

Symptom There is a low probability that the Cisco router disables its port
connected to a UMPT.
Impact The service Ethernet port on the UMPT becomes unreachable, and
the O&M channel or service channel carried on the Ethernet port is
disconnected.

V100R008C00SPC210
Trigger Condition  A UMPTa or UMPTb is connected to the Cisco router through its
optical port.
 The UMPT resets.
 The Cisco router is working in forced linkup mode.
 The link-flap error detected function has been enabled on the
Cisco router.
Root Cause When the UMPT starts up, its optical module has been enabled.
The optical module sends some random signals to the router. As a
result, the port on the router connected to the UMPT experiences
repeated link-ups/downs. When five link-ups/downs occur within
10s, the router disables its port connected to the UMPT.
Workaround To resolve this problem, use any of the following workarounds:
 Replace the optical module on the UMPT side or router side. If
the problem persists, try more optical modules.
 Replace the UMPT.
 Configure the Cisco router so that it works in auto-negotiation
mode or disable the link-flap error detected function.
NOTE
Workaround 1 is recommended.

the Problem Will
Be Solved
2.1.21 Reconfiguration May Fail to Take Effect During Cell

Activation
Symptom There is a low probability that reconfiguration may fail to take
effect during cell activation.
Impact The reconfiguration fails to take effect.

All V100R008C00 versions earlier than BTS3900
V100R008C00SPC233
Trigger Condition The configuration is modified during cell activation (within 3s after
the ACT CELL command is executed).
Root Cause The configuration cannot be updated during cell establishment. If
configurations are modified by running MML commands, related
features may not take effect.
Workaround Modify the configuration after the cell is successfully activated by
running the ACT CELL command.
Recovery Measure Reactivate the cell, or modify the configuration again.

the Problem Will
Be Solved
2.1.22 A CODR Event Is Falsely Reported for a Common or

LampSite Sleeping Cell Serving by Multiple LBBP Boards
Symptom A cell outage detection and recovery (CODR) event is falsely
reported for a common or LampSite sleeping cell serving by
multiple LBBP boards.
Impact A CODR event is falsely reported for a common or LampSite
sleeping cell, without affecting services in the cell.

All V100R008C00 versions earlier than BTS3900
V100R008C00SPC234
Trigger Condition Common or LampSite cells are served by multiple LBBP boards.
The TDLOFD-002012 Cell Outage Detection and Compensation
feature is enabled.
Root Cause The fact, that Layer 1 is separated from Layer 2, is not taken into
account for common or LampSite cells serving by multiple LBBP
boards. As a result, the LBBP configured only for Layer 1 cells
considers that the Layer 1 reported data is greater than the Layer 2
reported data. Therefore, a CODR event is reported.
Workaround Do not configure multiple LBBP boards for common or LampSite
cells.
Recovery Measure Delete the reported CODR event manually.

the Problem Will
Be Solved
2.1.23 Updating Neighboring GERAN Cell Configurations Using
the CME Fails
Symptom The configurations of neighboring GERAN cells cannot be updated
using the CME.
Impact GERAN cell configurations cannot be updated in batches using the
CME.
Impacted Version All BTS3900 V100R008C00 versions earlier than

V100R008C00SPC810
V100R008C01SPC240
Trigger Condition A script including the following commands is executed using the
CME to update GERAN cell configurations:
 MOD GERANNCELL
 MOD GERANNFREQGROUP
 ADD GERANNFREQGROUPARFCN
 RMV GERANNFREQGROUPARFCN
Note: This problem occurs regardless of the sequence of these
commands in the script.
Root Cause When the script is executed using the CME, the system fails to
sequence the previous commands due to their association, thereby
causing timeout of script execution.
Workaround Include the previous commands into different scripts to avoid
command sequencing failures.
Recovery Modifying the script to be executed using the CME. For details, see
Measure the workaround.
Version in Which BTS3900 V100R008C00SPC810 and BTS3900

the Problem Will V100R008C01SPC240
Be Solved
2.1.24 LST EUTRANINTERNFREQ Command Output Indicates a
Non-default Value of the Frequency Offset After Neighboring E-
UTRAN Frequencies Are Added Upon Setup or Update of the X2
Interface
Symptom When the X2 interface is set up or updated, neighboring E-UTRAN
frequencies are automatically added. However, the output of the
LST EUTRANINTERNFREQ command executed afterwards
indicates that the Frequency offset parameter is set to 1dB, instead
of the default value 0dB.
Impact The frequency offset is set to a non-default value.

V100R008C00SPC810
V100R008C01SPC290
Trigger Condition Neighboring E-UTRAN frequencies are automatically added when
the X2 interface is set up or updated.
Root Cause The Frequency offset parameter is incorrectly set for
automatically-added neighboring E-UTRAN frequencies.
Workaround Run the ADD EUTRANINTERNFREQ command to manually
add neighboring E-UTRAN frequencies.
Recovery Run the ADD EUTRANINTERNFREQ command with the
Measure Frequency offset parameter set to the default value dB0(0dB).
Version in Which BTS3900 V100R008C00SPC810 and BTS3900

Be Solved
2.1.25 Command Fails to Be Executed for Adding, Removing, or

Modifying an Active SFN Cell or Its Sector After a Serving RRU
Is Removed
Symptom A command for adding, removing, or modifying an active SFN cell
or its sector fails to be executed if an RRU serving the cell is
removed.
Impact A command for adding, removing, or modifying an SFN cell or its
sector fails to be executed.
V100R008C00SPC810
V100R008C01SPC290
Trigger Condition An RRU serving an active SFN cell is removed.
Root Cause No restriction is placed on RRU removal.
Workaround Remove an RRU only after the SFN cell served by this RRU is
deactivated.
Recovery Run the command again after deactivating the SFN cell.
Measure
Solution To be determined
Version in Which To be determined

the Problem Will
Be Solved
2.1.26 Network Access Fails After Fast ANR Is Enabled

Symptom Network access fails after fast ANR is enabled.
Impact New users cannot access the network.

V100R008C00SPC234
V100R008C01SPC290
Trigger Condition The value of the FastAnrRprtAmount parameter in the ANR MO
multiplied by the value of the FastAnrRprtInterval parameter in
the same MO indicates a duration longer than 8 minutes.
Root Cause The FastAnrRprtAmount and FastAnrRprtInterval parameters
in the ANR MO are set to large values when fast ANR is enabled.
As a result, UE resources are not released in time. Insufficient
resources cause network access failures.
Workaround Change the values of the FastAnrRprtAmount and
FastAnrRprtInterval parameters in the ANR MO. (The default
values are recommended.)
Recovery Take the workaround measures, and then reset the eNodeB.
Measure

the Problem Will
Be Solved
2.1.27 Bit Error Rate and Service Drop Rate Increase in LampSite
RF Combination Scenarios
Symptom The bit error rate and service drop rate increase when multiple
pRRUs serve the same cell in a LampSite scenario.
Impact The bit error rate and service drop rate of the cell increase.

V100R008C00SPC810
V100R008C01SPC290
Trigger Condition RF signals of pRRUs are combined.
Root Cause The equivalent power of pRRUs is incorrectly calculated in case of

RF combination.
Workaround Do not use RF combination for the impacted versions.
Recovery Disable RF combination.

Measure

the Problem Will BTS3900 V100R008C01SPC290
Be Solved
2.1.28 Checking the CME-based 8T8R RRU Configuration Fails

Due to Failed Database Query
Symptom After 8T8R RRUs are configured using the CME, execution of the
STR CFGCHK command fails with an error message displayed,
denoting a database query failure.
Impact Configuration check fails.

V100R008C00SPC810
Trigger Condition The STR CFGCHK command is executed after 8T8R RRU
configuration data is added using the CME.
Root Cause The internal Rx/Tx channels of an RRU are numbered from 1, that
is, the channels are numbered 1 through 8, to ensure compliance
with the RRU's Tx/Rx antenna numbers. However, the Rx/Tx
channels are numbered from 0 (that is, 0 through 7) according to the
CME configuration principle. During configuration check, the
system attempts to retrieve the data of channels 1 through 8 from
the database and cannot retrieve the data of Tx/Rx channel 8. As a
result, the command execution fails.
Workaround Use MML commands instead of the CME to configure 8T8R
RRUs.
Recovery Run the RMV RRU command to remove RRUs and then the ADD
Measure RRU command to add the RRUs again.
Solution To be determined
Version in Which To be determined

the Problem Will
Be Solved
2.1.29 "BBI configuration failed" Is Displayed When Some Cells

Served by an LBBPd Bound with Four or More Cells Failed to Be
Activated
Symptom The message "BBI configuration failed" is displayed when some
cells served by an LBBPd bound with four or more cells failed to be
activated.
Impact Some cells failed to be activated.
Impacted Version V100R009C00SPC800, V100R009C00SPC820, and all

V100R009C00 versions earlier than V100R009C00SPC150.
Trigger Condition An LBBPd is bound with four or more cells, including physical
cells. The cells with the same subframe assignment but different
special subframe assignments exist.
Root Cause A fault occurs when the eNodeB imposes a restriction on the
LBBPd that supports different cells with different special subframe
assignments.
Workaround Do not bind more than three cells with different special subframe
assignments to one LBBPd.
Recovery Measure Reduce the number of cells bound to the LBBPd to three or less.

the Problem Will
Be Solved
2.1.30 LBBPd Reference Signal Power May Fail to Take Effect or

ALM-29241 Cell Reconfiguration Failed May Be Reported After
the MOD CELLDLPCPDSCHPA Command Is Executed
Following the MOD PDSCHCFG Command
Symptom LBBPd reference signal power may fail to take effect or ALM-
29241 Cell Reconfiguration Failed may be reported after the MOD
CELLDLPCPDSCHPA command is executed following the
MOD PDSCHCFG command.
Impact LBBPd reference signal power may fail to take effect or ALM-
29241 Cell Reconfiguration Failed may be reported.
Impacted Version All V100R008C00 versions earlier than V100R008C00810 and all
V100R008C01 versions earlier than V100R008C01SPC310.
Trigger Condition The MOD CELLDLPCPDSCHPA command is executed within
1s after the MOD PDSCHCFG command is executed.
Root Cause Lack of exclusion protection leads to rewritten of some data.
Workaround Run the CELLDLPCPDSCHPA command 5s after the MOD

PDSCHCFG command is executed.
Recovery Run the MOD CELLDLPCPDSCHPA command again 5s after
Measure the MOD PDSCHCFG command is executed.

Be Solved
2.1.31 The DSP GPS Command Output Indicates the RGPS
Cannot Work Properly
Symptom The DSP GPS command output is RETCODE = 806486156 RRU
is configuring now, indicating that the RGPS cannot work
properly.
Impact The RGPS cannot work properly. If the RGPS is activated, the
system clock input is abnormal and cannot be locked. As a result,
ALM-26262 External Clock Reference Problem is reported.

All BTS3900 LTE V100R008C00 and BTS3900 LTE
BTS3900 LTE V100R009C00SPC800 and BTS3900 LTE
V100R009C00SPC820
All BTS3900 LTE V100R009C00 versions earlier than
V100R009C00SPC150
Trigger Condition After the RRU maintenance link is faulty, the following operations
are performed for an eNodeB working in LTE TDD mode and
using the RGPS as the clock source:
1. Bind RGPS m to RRU a.
2. Remove RGPS m.
3. Remove RRU a.
4. Add RRU a.
5. Bind RGPS n to RRU a. (0 < m < n ≤ 17)
6. Add RRU a.
Root Cause The RGPS m is not removed completed. As a result, the RGPS n
added later cannot work properly.
Workaround Do not add or remove an RGPS or RRU when the RRU
maintenance link is faulty.
Recovery When the RRU maintenance link is normal, run the RMV GPS
Measure command to remove RGPS n and then run the ADD GPS command
to configure the RGPS n again.

the Problem Will
Be Solved
2.1.32 Packet Retransmissions Increase for UEs in TM7 or TM8
Scenarios If the RS Power Is Not Set to the Recommended Value
Symptom The number of packet retransmissions for a UE increase in a cell
whose reference signal (RS) power is set to a value other than the
recommended value if the transmission mode TM7 or TM8 is used
for the UE.
Impact Packets of the UE are retransmitted four times.
Impacted Version All BTS3900 V100R008C00 and BTS3900 V100R008C01 versions

V100R009C00SPC180
Trigger Condition  TM7 or TM8 is used for UEs.
 The RS power of the cell is set to a value other than the
recommended value.
Root Cause The number of REs allocated to the concerned UE in special
subframes is incorrectly calculated and fails the L1 verification.
Therefore, the UE's packets are discarded and then retransmitted.
Workaround Change the RS power to the recommended value in the
PDSCHCFG MO.
Recovery Change the RS power to the recommended value in the
Measure PDSCHCFG MO.

the Problem Will
Be Solved
2.1.33 Uplink Scheduling Capacity Decreases When the

UlEnhancedSrSchSwitch Check Box Is Selected in DRX
Scenarios, Resulting in KPI Deterioration
Symptom When UEs are in DRX state and the UlEnhancedSrSchSwitch
check box under the UlSchSwitch parameter is selected, the uplink
scheduling capability and the KPI values related to the network
access success rate, service drop rate, and throughput decrease.
Impact The uplink scheduling capability and the KPI values related to the
network access success rate, service drop rate, and throughput
decrease.
Impacted Version BTS3900 V100R009C00SPC130, BTS3900
V100R009C00SPC170, and BTS3900 V100R009C00SPC180
V100R010C00SPC170
Trigger Condition The DrxAlgSwitch parameter is set to ON and the
UlEnhancedSrSchSwitch check box under the UlSchSwitch
parameter is selected.
Root Cause The enhanced uplink SR scheduling function does not take effect
after the UlEnhancedSrSchSwitch check box is selected.
Workaround Run the following command to disable the enhanced uplink SR
scheduling function:
MOD CELLALGOSWITCH: LocalCellId=x,
UlSchSwitch=UlEnhancedSrSchSwitch-0;
Recovery See the workaround.

Measure

Be Solved
2.1.34 Handover of a CA UE Fails When the CA Feature Is

Enabled and the HoWithSccCfgSwitch Check Box Is Selected
Symptom When the carrier aggregation (CA) feature is enabled and the
HoWithSccCfgSwitch check box under the CaAlgoSwitch
parameter is selected, the handover of a CA UE fails.
Impact The handover success rate of the eNodeB decreases.
Impacted Version BTS3900 V100R009C00SPC170 and all earlier BTS3900

V100R010C00SPC150
Trigger Condition  A handover is initiated for a CA UE.
 The HoWithSccCfgSwitch check box under the CaAlgoSwitch
parameter is selected.
 The cell radio network temporary identifier (C-RNTI) of the UE
conflicts with that of another UE.
Root Cause When a secondary component carrier (SCC) has been configured
for a CA and a C-RNTI conflict occurs during the handover, the
handover module retries the handover upon receiving a conflict
error message. However, the handover module fails to verify the
data radio bearer (DRB) information carried in RB-related
parameters because the message sent by the RB module to the
handover module did not carry DRB setup success information.
Workaround Run the following command to disable the SCC-configured
handover function:
MOD ENODEBALGOSWITCH: CaAlgoSwitch=HoWithSccCfgSwitch-0

Measure

Be Solved
2.1.35 RF Channel Intelligent Shutdown Function Is Frequently

Started and Stopped When the RfShutdownSwitch Parameter Is
Set to ON, the Number of UEs in a Non-2T2R and Non-4T4R Cell
Changes Between 0 and Other Quantity, and the Uplink or
Downlink PRB Usage Is 0
Symptom The RF intelligent shutdown function is frequently started and
stopped when all of the following conditions are met:
 The RfShutdownSwitch parameter is set to ON.
 The number of UEs in a non-2T2R and non-4T4R cell changes
between 0 and other quantity.
 The uplink or downlink PRB usage is 0.
Impact The RF intelligent shutdown function is frequently started and
stopped.
Impacted Version All BTS3900 V100R800C00 versions

All BTS3900 V100R800C01 versions
Trigger Condition  The cell is not a 2T2R or 4T4R cell.
 The RfShutdownSwitch parameter is set to ON.
 The value of Uplink/Downlink PRB offset plus that of
Uplink/Downlink PRB threshold is 0.
Root Cause The eNodeB does not impose the penalty when a non-2T2R and
non-4T4R cell exits the RF channel intelligent shutdown mode.
Workaround Run the MOD CELLRFSHUTDOWN command with the
RfShutdownSwitch parameter set to OFF for non-2T2TR and non-
4T4R cells.
Measure
Version in Which All BTS3900 V100R009C00 versions

the Problem Will
Be Solved
2.2 V100R004C00
2.2.1 No ALM-26262 Clock Reference Problem Alarm Is Reported
Symptom The GPS and IEEE 1588V2 clocks are unavailable, but ALM-
26262 External Clock Reference Problem is not reported.
Impact The fault identification efficiency is affected.
Impacted Version All versions earlier than DBS3900 LTE V100R005C00SPC340
Trigger Condition The eNodeB is configured with GPS and IP clocks, and the
automatic clock working mode is used. The GPS clock and the IP
clock are unavailable.
Root Cause In the automatic clock working mode, the reference source
repeatedly switches between the IP clock and GPS clock.
Therefore, ALM-26262 External Clock Reference Problem cannot
be reported.
Workaround Run the DSP CLKSRC MML command to check whether the
clock source is available.
%%DSP CLKSRC:;%%
RETCODE = 0 Operation succeeded.
Display Clock Source State
--------------------------
Clock Source No. Clock Source Type Clock Source Priority

Clock Source State License Authorized
0 GPS Clock 4
Available N/A
0 IP Clock 4
Unavailable Allow
(Number of results = 2)
--- END
Recovery Rectify the faults of GPS clock and IP clock.
Measure
Version in Which All eRAN3.0 versions

the Problem Will
Be Solved
2.2.2 UE Handovers Are Unavailable

Symptom When carrier frequencies are changed using the CME, UE
handovers cannot be supported.
Impact UE handovers cannot be supported and the call drop rates increase.
Impacted Version All eRAN2.2 versions
Trigger Condition The eNodeB is configured with neighboring cells and frequencies
are changed by using the CME.
Root Cause When the CME delivers batch configuration information to the
eNodeB for changing the cell frequencies, the neighboring cell
information in the memory is removed by the eNodeB.
Therefore, after batch configuration is complete using the CME, the
neighboring cell information can be queried in the database, but the
neighboring cell information in the memory has been removed.
Therefore, neighboring cell information cannot be found during
handovers.
If intra-frequency neighboring cells are removed or modified on the
CME, the eNodeB reports the cell removal or modification failure.
Workaround 1. Remove all the neighboring cell information.
12. Change the cell frequencies.
13. Add all the neighboring cell information by reconfiguring the
neighboring cells.
Recovery Add all the neighboring cell information again after removing it.
Measure
Solution When changing the cell frequencies for the new version, do not
remove the neighboring cell information.
Version in Which All eRAN3.0 versions
the Problem Will
Be Solved
2.2.3 ALM-26235 RF Unit Maintenance Link Failure Alarm Is
Reported
Symptom ALM-26235 RF Unit Maintenance Link Failure Alarm and ALM-
26202 Board Overload are reported.
Impact The High-Level Data Link Control (HDLC) link of the RRU cannot
be set up, which results in service interruption.
Impacted Version All eRAN2.2 versions
Trigger Condition Uploading of many logs, too many users, and other unknown
reasons cause the CPU overload of the main control board and the
ALM-26202 Board Overload.
Root Cause The overload of main control board lasting for about five minutes
causes a baseband processing board reset. After the baseband
processing board reset, there is a low possibility that the sequence
of initializing the HDLC information and sending requests for
setting up the HDLC link reversed. In this case, the HDLC link
cannot be set up.
Workaround None
Recovery Reset the related baseband processing board.

Measure
Version in Which None

the Problem Will
Be Solved
2.2.4 ALM-25902 Remote Maintenance Link Running Data and

Configuration Mismatch May Be Reported When the eNodeB
Automatically Obtains the OMCH Using the DHCP Mechanism
Symptom The eNodeB may report ALM-25902 Remote Maintenance Link
Running Data and Configuration Mismatch when all of the
following conditions are true:
 The IP route and the route bound with the OMCH are configured
in the same network segment.
 The next hop of the IP route is the same as that of the route bound
with the OMCH.
 The eNodeB automatically obtains the OMCH using the DHCP
mechanism 15 minutes after the transmission link is interrupted.
Impact ALM-25902 Remote Maintenance Link Running Data and
Configuration Mismatch is a false alarm, affecting user experience.
Impacted Version All V100R004C00 versions
Trigger Condition The IP route and the route bound with the OMCH are configured in
the same network segment.
The next hop of the configured IP route is the same as that of the
route bound with the OMCH.
The eNodeB automatically obtains the OMCH using the DHCP
mechanism 15 minutes after the transmission link is interrupted.
Root Cause An IP route to the M2000 has been configured, and the OMCH
obtained using the DHCP mechanism may not be bound with a
route. As a result, when the configured OMCH is bound with a
route, the eNodeB reports ALM-25902 Remote Maintenance Link
Running Data and Configuration Mismatch.
Workaround Configure the route bound with the OMCH in a network segment
different from those of the other configured routes.
Recovery Modify the OMCH information according to the DSP OMCH
Measure command output.

the Problem Will
Be Solved
2.3 V100R005C000
2.3.1 HDLC Link Cannot Be Set Up
Symptom The HDLC link cannot be set up when the RRU3235 in eRAN2.2 is
connected to the LBBPd and the common public radio interface
(CPRI) line rate is 9.8 Gbit/s.
Impact When the RRU3235 with the version of MARP 1.7C00 in eRAN2.2
is connected to the LBBPd using a 10 Gbit/s optical module and the
CPRI Line Rate(Gbit/s) parameter is set to AUTO, the CPRI link
is set up properly but the HDLC link cannot be set up. As a result,
the RRU3235 is not available (the link to the RRU3235 is not
reachable and the software version cannot be upgraded).
Impacted Version All LBBPd versions in eRAN3.0
Trigger Condition The RRU3235 in eRAN2.2 is connected to the LBBPd, and the
CPRI Line Rate(Gbit/s) parameter is set to AUTO.
Root Cause The version of the RRU3235 matching eRAN2.2 is MARP 1.7C00.
In this RRU version, errors occur when the CPRI CBB is parsing
the HDLC control word message.
Workaround Connect the RRU in eRAN2.2 to the LBBPc, upgrade the RRU to
eRAN3.0, and then connect the RRU to the LBBPd.
Recovery Run the Add RRUCHAIN command to set the CPRI Line
Measure Rate(Gbit/s) parameter to 4.9. After the setting is complete, the
link between the RRU and BBU can be set up properly. After the
link is set up, the RRU software is automatically upgraded to the
version that matches the LBBPd. After the upgrade is complete, set
the CPRI Line Rate(Gbit/s) parameter to AUTO. Then, the link
can be set up when the CPRI line rate is 9.8 Gbit/s.
Solution None

the Problem Will
Be Solved
2.3.2 Internet Protocol (IP) Address Conflicts Cannot Be Detected

Symptom VLAN tags cannot be attached to the free ARP packets sent by the
LMPT, and therefore IP address conflicts cannot be detected.
Impact In inter-board VLAN networks, the IP address conflict cannot be
detected.
An IP address conflict leads to link interruption. In this scenario,
the O&M channel interruption or intermittent disconnection may
occur, but the services are not affected.
Trigger Condition In inter-board VLAN networks (LMPT + UTRP, the UTRP is used
for physical transmission, and the LMPT is configured with the
O&M channel and signaling), the local IP address of the O&M
channel on the LMPT and the device IP address of the port on the
UTRP are in the same network segment but with different values.
Root Cause In inter-board VLAN networks, the IP address contained in the
ARP packets cannot be found in the IP address of the local port
when the ARP packets are transmitted over the UTRP. In this case,
the IP address cannot be found and the VLAN tags cannot be
attached to the free ARP packets.
Workaround Set the local IP address of the O&M channel on the LMPT and the
device IP address of the port on the UTRP to the same value.
Recovery Set the local IP address of the O&M channel on the LMPT and the
Measure device IP address of the port on the UTRP to the same value.

Version in Which DBS3900 LTE V100R005C00SPC340
the Problem Will
Be Solved
2.3.3 ALM-29240 Cell Unavailable Is Reported

Symptom There is a probability that ALM-29240 Cell Unavailable is reported
in either of the following cases:
 When the MOD CELL command is used to change the cell
configuration.
 When the DSP CELL command is used to activate a cell.
 The output of DSP CELL command indicates that the RRU
cannot be correctly configured.
Impact Services are interrupted.
Trigger Condition Either of the following conditions is met when the MOD CELL or
ACT CELL command is run:
1. The CPRI link is unsteady, which can be confirmed by querying
whether ALM-26234 BBU CPRI Interface Error is reported.
14. The CPU usage of the LMPT, LBBP, or RRU is greater than
80%, which can be confirmed by running the DSP CPUUSAGE
command.
Root Cause A BBU periodically checks the RRU configuration. After a cell is
activated, the BBU checks the RRU configuration again. However,
if the first check is not finished, this check is ignored. As a result,
the check timer times out and the cell does not provide services.
Workaround None
Recovery 1. The alarm can be cleared automatically by the cell

Measure reestablishment mechanism, which lasts about 10 minutes.
15. Run the DEA CELL command to deactivate the cell and run the
ACT CELL command to activate the cell again, and the alarm
can be cleared immediately.

the Problem Will
Be Solved
2.3.4 Certificate Cannot Be Updated
Symptom When the UPD DEVCERT command is used to update the
certificate, the "Progress report: in negotiation" message is
occasionally displayed.
When the command is used to update the certificate again, the
"Progress report: device certificate not uploaded" message is
displayed.
Impact The certificate cannot be updated.
Trigger Condition The UPD DEVCERT command is used to update the certificate
after the certificate is activated.
Root Cause Activating and updating the certificate involve two independent
procedures. If the certificate is updated after it is activated, the two
procedures interfere with each other, resulting in an internal status
disorder.
Workaround Update the certificate 10 minutes later after activating it.
Recovery 1. Run the DSP CERTMK command to query the eNodeB device
Measure certificate.
16. Run the MOD APPCERT command to change the current
certificate to another one, and then change it to the required
certificate.
NOTE
If the O&M channel is set up between the eNodeB and the M2000, set the
APPTYPE parameter to SSL. If it is set up between the eNodeB and security
gateway, set this parameter to IKE.
17. Run the UPD DEVCERT command to update the certificate.

the Problem Will
Be Solved
2.3.5 CRL File Cannot Be Obtained

Symptom The ADD CRLTSK command is successfully executed, but no
CRL file is obtained.
Impact The CRL file cannot be obtained.

Trigger Condition The ADD CRLTSK command is used to periodically obtain the
CRL file, with the CRLGETMETHOD parameter set to LDAP
and the SEARCHDN parameter set to NULL.
Root Cause The SEARCHDN parameter is mandatory for updating the CRL
file. If it is empty, the CRL file cannot be obtained.
Workaround Run the ADD CRLTSK command with the SEARCHDN
parameter set to a correct value.
Recovery 1. Run the RMV CRLTSK command to remove the configuration
Measure of the empty SEARCHDN parameter.
18. Run the ADD CRLTSK command with the SEARCHDN
parameter set to a correct value.

the Problem Will
Be Solved
2.3.6 Equipment Certificate of eNodeB Cannot Be Updated

Symptom When the UPD DEVCERT command is run to update the eNodeB
equipment certificate, a message indicating an internal error with
error code 4034 is displayed.
Impact The failure of the eNodeB equipment certificate update affects user
experience.
Trigger Condition 1. The certificate server (such as an HP server) sends a

modification response message with the certificate in the
ExtraCert field to the eNodeB. The RSA CA server does not
carry this certificate.
19. The UPD DEVCERT command is run to update the eNodeB
equipment certificate.
Root Cause The ExtraCert field is optional in the RFC4210. If the RA server is
used, the certificate may be carried in the ExtraCert field. During
the certificate uploading, the port protocol is incompatible with the
RA server protocol, resulting in an abnormal update report.
However, this report has no impact on the certificate update
function.
Workaround No measures are required.
Recovery No measures are required.

Measure

the Problem Will
Be Solved
2.3.7 FMU Electronic Label Fails To Be Obtained After the FMU Is

Changed
Symptom If the fan monitor unit (FMU) is changed, the FMU electronic label
fails to be obtained by running the DSP CABMFRINFO command.
Impact The cabinet electronic label cannot be obtained. FMU operation is not
affected.
Impacted All versions earlier than DBS3900 LTE V100R005C00SPC340

Version
Trigger The FMU has two versions. Character string FMUB on the bar code
Condition indicates the old version, and other character strings indicate the new
version.
The FMU electronic label fails to be obtained when the following
conditions are met:
 The broken FMU on the live networks is replaced.
 The version of the new FMU board is different from the original one.
Root Cause The electronic labels uploaded by the two FMU versions are different.
If the new version is replaced by the old version, the upload fails.
Workaround Different versions of FMUs must not be configured to use the same
address.
Run the MOD FMU command to change the communication address
if two versions of FMUs are configured to use the same address.
If the ADD FMU command is executed, the default value of Address
sets to 14, change it to the other value by running the ADD FMU
command.
Recovery Reset the main control board.

Measure
Version in DBS3900 LTE V100R005C00SPC340

Which the
Problem Will
Be Solved
2.3.8 S1 Link May Become Faulty Due to License Restriction After

Activation of the eNodeB Configuration File
Symptom When the S1 link is in normal state, the eNodeB resets after the
configuration file is downloaded and activated by running the
following command:
ACT CFGFILE: EFT=IMMEDIATELY;
After the eNodeB resets, the S1 link is faulty. The cause value of
the S1 link fault is License Restriction.
Impact Cells cannot be activated and services cannot be provided.
Trigger Condition There is a possibility that the S1 link becomes faulty when the
configuration file is downloaded and activated by running the
following command:
ACT CFGFILE: EFT=IMMEDIATELY;
Root Cause The S1 link setup is implemented earlier than the license
configuration takes effect.
Workaround None
Recovery Use MML commands to delete the S1 configuration and add the S1
Measure configuration.

the Problem Will
Be Solved
2.3.9 PMU/TCU Manufacturer Information Is Incorrect

Symptom The PMU/TCU manufacturer information in the inventory file
displayed on the M2000 or in the DSP BRDMFRINFO command
output is incorrect.
Impact User experience is affected.
Impacted Version Versions earlier than V100R005C00SPC340

Trigger Condition The inventory information about the PMU/TCU provided by other
vendors is exported after the PMU/TCU is configured and starts up
successfully.
Root Cause When the PMU/TCU manufacturer information is generated, the
PMU/TCU is incorrectly regarded as common boards of which the
manufacturer is Huawei.
Workaround If a faulty PMU/TCU must be replaced, check for the manufacturer
information onsite or according to BOM codes.
Recovery None
Measure
Solution Fix the bug so that the correct information about the manufacturer
of the PMU/TCU is configured in the inventory board information.
the Problem Will
Be Solved
2.3.10 There Is a Possibility that ALM-26529 RF Unit VSWR

Threshold Crossed Is Reported After the RRU3702 Is Soft-Reset
Symptom There is a possibility that ALM-26529 RF Unit VSWR Threshold
Crossed is reported after the RRU3702 is soft-reset.
Impact The cell served by the RRU3702 cannot be activated, and services
are interrupted.

Trigger Condition 1. The RRU3702 is reset by running the RST BRD command, or
the eNodeB is reset by running the RST eNodeB command.
20. The cell served by the RRU3702 is activated before soft reset is
initiated.
Root Cause Even if the RRU3702 is soft-reset after the cell is activated, the
BBU periodically sends the RRU a delay configuration message
indicating an abnormally large delay.
As a result, the RRU obtains a period longer than 10 ms, which
causes ALM-26529 RF Unit VSWR Threshold Crossed.
Workaround Run the DEA CELL command to deactivate the cell before soft-
resetting the RRU3702.
Recovery 1. Run the DEA CELL command to deactivate the cell.
Measure 21. Run the RST BRDPWROFF command to reset the RRU3702.
22. Run the ACT CELL command to activate the cell.
Solution The mechanism for obtaining 10-ms period information is
optimized. If the obtained period is longer than 10 ms, the period
configuration is not used.
the Problem Will
Be Solved
2.3.11 Message Indicating that the Object Does Not Exist Is

Displayed After the MOD RETPORT Command Is Run
Symptom A message indicating that the object does not exist is displayed
after the following command is run:
MOD RETPORT:CN=0,SRN=60,SN=0,PWRSWITCH=ON;
NER_Ryneveld_Park
+++ HUAWEI 2012-09-03 11:34:18
O&M #9133
%%/*333624*/MOD RETPORT:CN=0,SRN=60,SN=0,PWRSWITCH=ON;%%
RETCODE = 855834693 The object does not exist.
Impact The ALD power switch cannot be turned on.
Trigger Condition The templates built in the CME are used.
Root Cause The RetPort item is lost in the built-in template. As a result, the
built-in template of the CME cannot be used to configure RET port
data.
Workaround Perform the following operations:
1. Choose CM Express > LTE Application > Create eNodeB to
create a site using the built-in template.
In the displayed Create eNodeB dialog box, set Site Version,

Cabinet Type, eNodeB Template Name, Radio Template
Name, and Cell Template Name according to the plan of the
live network.
23. In the navigation tree on the left, right-click an eNodeB under

Root and choose Device Panel from the shortcut menu. On the
displayed device panel, remove the RRU and add it again.
NOTE
The RetPort item is also added in this step.
24. Save the new template.
25. Use the new template for eNodeB configurations.
Recovery Prepare the configuration file by referring to the previous

Measure workaround.
Solution Add the RetPort item in the eNodeB template.

the Problem Will
Be Solved
2.3.12 LBBPd Cannot Start Up and ALM-26254 Board Software

Synchronization Failure Is Reported After the LBBPd Replaces an
LBBPc
Symptom After an LBBPd replaces an LBBPc, there is a possibility that the
following situations occur:
 The LBBPd cannot start up after about 5 minutes elapses.
 The value of the Status parameter in the DSP SOFTSTATUS
command output is always 0%.
 ALM-26254 Board Software Synchronization Failure is reported.
Impact Services are interrupted in the cell served by the LBBPd.
Impacted Version All versions
Trigger Condition  An LBBPd replaces an LBBPc.

 The RRU connected to the LBBPd works in eRAN2.2-specific
BootROM version.
 The RRU connected to the LBBPd is RRU3232 or RRU3235.
Root Cause When the RRU works with eRAN2.2-specific BootROM version,
the LBBPd connected to the RRU returns the broadcast packets
transmitted by the main control board to the same main control
board. As a result, the route table on the main control board records
incorrect route data, and the LBBPd cannot obtain the software
version from the main control board.
Workaround Perform one of the following workarounds:
1. During the replacement, connect the unconfigured RRU after the
value of the Availability Status parameter is Normal for the
LBBPd in the DSP BRD command output.
26. Upgrade LBBPd software to the software version of the main
control board before the LBBPd replaces the LBBPc.
27. Upgrade the BootROM of the RRU to the eRAN3.0-specific
version before the LBBPd replaces the LBBPc.
Recovery After this problem occurs, disconnect the LBBPd from all the
Measure connected RRUs, and reconnect them after the LBBPd starts up
successfully.
Version in Which eRAN3.0 versions

the Problem Will
Be Solved
2.3.13 Incorrect Value LLT1POWER01 of License Identifier Is
Displayed in the Output of DSP LICENSE
Symptom After the DSP LICENSE command is executed, incorrect value
LLT1POWER01 of License Identifier is displayed.
Impact The license identifier value of the RRU serving the cell is greater
than the required, but this does not affect any service.
Impacted Version All versions on the live network
Trigger Condition Remove the corresponding sector by running the ADD CELL
command after adding a cell by running the RMV SEC command.
Root Cause Removal information is not updated to the other modules after the
sector is removed.
Workaround None
Recovery Add a cell by running the ADD CELL command after it is removed
Measure by running the RMV CELL command.

the Problem Will
Be Solved
2.3.14 Cell Setup Failure Is Reported When a Modified Cell Is

Activated
Symptom After a cell is modified, cell setup failure is reported when the
modified cell is activated by running the ACT CELL command.
Impact Services are interrupted if the cell establishment fails.
Impacted Version All versions on the live network
Trigger Condition After a cell is removed, the MOD CELL command is executed to
change the value of MultiRruCellMode from
DIGITAL_COMBINATION to another or from another value to
DIGITAL_COMBINATION.
Root Cause Incorrect uplink and downlink channels are set up after the cell is
modified.
Workaround To change the type of a cell, remove the cell and then add it. Do not
modify the cell by running the MOD CELL command.
Recovery Add a cell by running the ADD CELL command after it is removed
Measure by running the RMV CELL command.

the Problem Will
Be Solved
2.3.15 Cell Setup Fails Because the Maximum Transmit Power of

Cells Is Larger than the Maximum Power Specified by RRUs
After eNodeBs Are Upgraded to V100R005C00SPC300 or Later
Symptom Cell setup fails because the maximum transmit power of cells is
larger than the maximum power specified by RRUs after eNodeBs
are upgraded to V100R005C00SPC300 or later.
Impact Cell setup fails.
Trigger Condition 1. Versions are upgraded to V100R005C00SPC300.

28. The configuration combination of power (Pa, Pb) is different
from (0, 0), (-3, 1), (-4.77, 2), and (-6, 3).
Root Cause The calculation of maximum transmit power of cells is incorrect in
the source versions.
Workaround Before a software upgrade, check the configuration of (Pa, Pb). If
the configuration of (Pa, Pb) is not (0, 0), (-3, 1), (-4.77, 2) or (-6,
3), provide feedback to Huawei headquarters, and reach solutions as
required.
Recovery Provide feedback to the headquarters, and reach solutions as
Measure required.

the Problem Will
Be Solved
2.3.16 CPU Usage Increases Periodically When the Optical

Module Not Connected to RRUs Is Inserted into the LBBPd
Symptom CPU usage increases periodically when the optical module not
connected to RRUs is inserted into the LBBPd.
Impact Service flows are controlled and services are interrupted.
Impacted Version V100R005C00SPC310 and the earlier V100R005C00 versions
Trigger Condition An optical module not connected to RRUs is inserted into the
LBBPd.
Root Cause If an optical module not connected an RRU is inserted into the
LBBPd, the CPRI CBB module periodically uses the optical time-
consumption function of DOPRA to perform rate negotiation.
Workaround Do not insert an optical module into the LBBPd if the optical
module is not connected to an RRU.
Recovery Remove the optical module in the idle state onsite.
Measure
Solution The mechanism of reading message on the optical module is

optimized. The message of the optical module is read and saved
only when the connected status of the optical module changes.
the Problem Will
Be Solved
2.3.17 ALM-26200 Board Hardware Fault Persists for Six to Eight

Minutes Upon Power-Off, Removal, or Insertion of the LBBPd
During Startup, and Is Cleared After Startup
Symptom ALM-26200 Board Hardware Fault persists for six to eight minutes
if the LBBPd is power off, removed, or inserted during the startup
process, and is cleared after the startup is completed.
Impact In this situation, this alarm is incorrectly reported and can be
automatically cleared.
Trigger Condition The LBBPd board is power off, removed, or inserted during the
startup process.
Root Cause If the LBBPd board is power off, removed, or inserted during the
startup process, it may reset abnormally, and the flash file may be
damaged. In this case, the LBBPd board obtains the version from
the main control board in the security mode. The controller area
network BUS (CANBUS) software on the LBBPd board detects the
three clock signals provided by the field programmable gate array
(FPGA). If the FPGA is not loaded to the LBBPd board within 1
minute, the alarm is displayed on the M2000. If the LBBPd enters
security mode and attempts to obtain software from the main
control board, ALM-26200 Board Hardware Fault persists for six to
eight minutes.
Workaround Do not power off, remove, or insert the LBBPd board during the
LBBPd startup process.
Recovery None
Measure
Solution N/A
Version in Which N/A

the Problem Will
Be Solved
2.3.18 ALM-25891 IKE Negotiation Failure Is Falsely Cleared 15

Seconds After It Is Reported for the eNodeB
Symptom ALM-25891 IKE Negotiation Failure is falsely cleared 15 seconds
after it is reported for the eNodeB.
Impact If ALM-25891 IKE Negotiation Failure is falsely cleared 15
seconds after it is reported, operators cannot be notified of the
alarm.
Trigger Condition This problem occurs on the network using IPsec when the following
conditions are met:
 The eNodeB uses the IKEv1 exchange mode. (IKEv2 is not
involved in this problem.)
 IKE negotiation fails due to transmission link fault that occurs
after the IPsec negotiation succeeds.
Root Cause After the IKEv1 rekeying fails (if 70% of SA lifetime has elapsed),
ALM-25891 IKE Negotiation Failure is reported, and the Fading
status flag bit is added to the IKE SA. This flag bit, however, is
unrecognizable to the eNodeB for the alarm processing. As a result,
the eNodeB considers that the IKE SA negotiation succeeds, and
clears the alarm.
Workaround None
Recovery If the IKE negotiation failure is caused by modifying configuration,
Measure check the parameters used for IKE negotiation on the eNodeB and
the security gateway (SeGW), and ensure the parameter consistency
between the eNodeB and the SeGW. If the IKE negotiation failure
is caused by a network fault, wait for the network to recover.

the Problem Will
Be Solved
2.3.19 The Time on the eNodeB Cannot Be Synchronized and

ALM-26266 Time Synchronization Failure Is Reported When the
Master NTPC Cannot Be Changed Using the CME
Symptom The time on the eNodeB cannot be synchronized and ALM-26266
Time Synchronization Failure is reported when the master NTPC
cannot be changed using the CME.
Impact The time on the eNodeB cannot be synchronized and ALM-26266
Time Synchronization Failure is reported.
Trigger Condition The CME adds or modifies multiple NTPCs when delivering
incremental configuration, and it adjusts the master flag of an
NTPC.
NOTE
This issue does not occur when MML commands are executed to add or
modify NTPCs.
Root Cause To ensure that there is only one NTPC on the eNodeB when the
CME delivers incremental configuration, the CME changes the
master/slave flag of all NTPCs if the master NTPC is specified. As
a result, batch configuration does not take effect, causing a failure
in changing the master NTPC.
Workaround Run the SET MASTERNTPS command instead of using the CME
to set the master/slave flag of multiple NTPCs.
Recovery Run the STR CFGCHK command to check the configuration and
Measure then run the STR CFGCHKSYNC command to synchronize the
configuration.

the Problem Will
Be Solved
2.3.20 Transmission Is Interrupted over 15 Minutes When IPsec Is
Enabled on the eNodeB, and the O&M Link Cannot Recover
Immediately After Transmission Is Normal
Symptom Transmission is interrupted over 15 minutes when IPsec is enabled
on the eNodeB. The O&M link cannot recover immediately after
transmission is normal.
Impact The eNodeB can be maintained 10 minutes after transmission is
normal.
Trigger Condition This issue occurs when the following three conditions are met:
When IPsec is enabled on the eNodeB, the public SeGW and the
serving SeGW are not on the same server, and the ESP
authentication algorithm, ESP encryption algorithm, and IKE
version are inconsistent on the public and serving SeGWs.
An OMCH is configured on the eNodeB.
The OMCH is interrupted over 15 minutes.
Root Cause When IPsec is enabled on the eNodeB, IPsec negotiation parameter
settings are inconsistent on the public and serving SeGWs.
Therefore, IPsec negotiation fails and an OMCH cannot be
established.
Workaround Deliver a configuration file in which the ESP authentication
algorithm, ESP encryption algorithm, and IKE version are
consistent between the public SeGW and the serving SeGW.
NOTE
If the public SeGW and the serving SeGW are on the same server, there is no
risk.

Measure

the Problem Will
Be Solved
2.3.21 When Transmission Recovers After Being Interrupted Over
15 Minutes, ALM-25902 Remote Maintenance Link Running Data
and Configuration Mismatch Is Reported When You Log In to the
eNodeB Using the M2000
Symptom When transmission is normal after being interrupted over 15
minutes, ALM-25902 Remote Maintenance Link Running Data and
Configuration Mismatch is reported when you log in to the eNodeB
using the M2000.
Impact A false alarm is reported, affecting user experience.
Trigger Condition The OMCH is bound to the slot where the UTRP is located, and it
is not bound to the route available between the eNodeB and the
M2000.
Root Cause After transmission is interrupted 15 minutes, an OMCH is created
based on the DHCP response. If the route is not bound to the
OMCH, the OMCH will be bound to the slot where the main
control board is located by default. This is inconsistent with the slot
where the UTRP is located. Therefore, an alarm is reported.
Workaround See the recovery measure.
Recovery 1. Bind the OMCH to the slot where the main control board is
Measure located to clear the alarm. However, the eNodeB configuration
file cannot be exported using the CME because the check by the
CME fails. Note that you can run an MML command to modify
the configuration.
29. Remove the configured route before binding the OMCH to the
slot where the UTRP is located. However, the eNodeB will be
disconnected.
NOTE
For a new eNodeB, take measure 29.
For existing eNodeBs, there are risks when you take the workaround or
recovery measure.

the Problem Will
Be Solved
2.3.22 The Error Message "PACKETFILTER: When
SubboardType's value is [BASE_BOARD], FilterMode's value
should be [ADV_ACL, L2_ACL, ADV_AND_L2], but now the
value is NULL." Is Displayed on the M2000 During CME
Calibration
Symptom The error message "PACKETFILTER: When SubboardType's
value is [BASE_BOARD], FilterMode's value should be
[ADV_ACL, L2_ACL, ADV_AND_L2], but now the value is
NULL." is displayed on the M2000 during CME calibration.
Impact When the summary template is used to configure data (including
PACKETFILTER), the CME cannot import the configured data.
Trigger Condition Configure the eNodeB data (including PACEETFILTER) in the

summary template, and use the CME to generate eNodeB data.
Root Cause The PACEETFILTER parameter is mandatory. However, this
parameter is not set in the summary template. As a result, the CME
fails to calibrate generated eNodeB data.
Workaround Manually use the CME or run the ADD PACEETFILTER
command to configure the PACEETFILTER parameter.
Recovery None
Measure

the Problem Will
Be Solved
2.3.23 CRL Configurations Cannot Be Saved after the CME Is

Used to Modify eNodeB CRLTSK Settings and the eNodeB
Obtains the CRL Certificate
Symptom CRL configurations cannot be saved after the CME is used to
modify eNodeB CRLTSK settings and the eNodeB obtains the CRL
certificate.
Impact After eNodeB CRLTSK configurations are modified on the CME,
the incremental script successfully takes effect. However, the
eNodeB fails to save the CRL configurations. As a result, the
configurations are lost after the eNodeB resets.
Trigger Condition Use the CME to modify eNodeB CRLTSK configurations.
Root Cause Exclusivity protection prevents CRLTSK configurations from being

saved into the database.
Workaround Do not use the CME to modify eNodeB CRLTSK configurations.
To modify CRLTSK configurations, run the following MML
commands in sequence:
 RMV CRLTSK
 ADD CRLTSK
Recovery Run the RMV CRLTSK and ADD CRLTSK commands in
Measure sequence.

the Problem Will
Be Solved
2.3.24 (For Upgrade Scenarios) ALM-26223 Transmission Optical

Interface Performance Degraded or ALM-26222 Transmission
Optical Interface Error Is Reported After the eNodeB Is Upgraded
to V100R005C00SPC340 or Later Versions
Symptom When an eNodeB is upgraded from V100R005C00SPC310 or
V100R005C00 versions earlier than V100R005C00SPC310 to
V100R005C00SPC340 or later versions, ALM-26223 Transmission
Optical Interface Performance Degraded or ALM-26222
Transmission Optical Interface Error may be reported.
Impact After the upgrade, ALM-26223 Transmission Optical Interface
Performance Degraded or ALM-26222 Transmission Optical
Interface Error is reported.
Impacted Version V100R005C00SPC310 and V100R005C00 versions earlier than

V100R005C00SPC310
Trigger Condition 1. The UMPT functions as the main control board and is
configured with the optical module.
30. No alarm is reported although the transmit and receive power of
the optical module already exceed the threshold before the
upgrade.
NOTE
 Run the DSP SFP command to query the transmit and receive power of the
optical module.
 When the transmit power of the optical module is larger than 501.1 uw or
smaller than 125.9 uw, ALM-26223 Transmission Optical Interface
Performance Degraded is reported.
 When the transmit power of the optical module is larger than 501.1 uw or
smaller than 50 uw, ALM-Transmission Optical Interface Error is
reported.
Root Cause Before the upgrade, the eNodeB may incorrectly recognize the
optical port as the electrical port. In this situation, ALM-26223
Transmission Optical Interface Performance Degraded or ALM-
26222 Transmission Optical Interface Error is not reported. If the
transmit and receive power of the optical module exceed the
threshold before the upgrade and the optical port is recognized by
the eNodeB, ALM-26223 Transmission Optical Interface
Interface Error is reported.
NOTE
1. Before the upgrade, ALM-26223 Transmission Optical Interface
Performance Degraded or ALM-26222 Transmission Optical Interface
Error is reported correctly if the eNodeB can recognize the optical port.
2. The thresholds configured for ALM-26223 Transmission Optical Interface
Performance Degraded and ALM-26222 Transmission Optical Interface
Error remain the same before and after the upgrade.
Workaround Before the upgrade, run the DSP SFP command to query the power
of the optical module. If the power of the optical module exceeds
the threshold but ALM-26223 Transmission Optical Interface
Interface Error is not reported on the M2000, locate the fault for the
optical module or fiber at the site to ensure the transmit and receive
power of the optical module within the normal range.
Recovery After the upgrade, if ALM-26223 Transmission Optical Interface
Measure Performance Degraded or ALM-26222 Transmission Optical
Interface Error is reported, locate the fault for the optical module or
fiber at the site to ensure the transmit and receive power of the
optical module within the normal range.

the Problem Will
Be Solved
2.3.25 The Cell Status Cannot Be Automatically Updated and
Operator Information Is Not Updated in the System Information
After the ADD CELLOP or RMV CELLOP Command Is Executed
in MOCN Scenarios
Symptom The cell status cannot be automatically updated and operator
information is not updated in the system information after the ADD
CELLOP or RMV CELLOP command is executed in MOCN
scenarios.
Impact A cell operator can be added or deleted in MOCN scenarios only
after the cell is manually deactivated and then activated.
Impacted Version V100R005C00SPC370
Trigger Condition A cell operator is added or deleted in MOCN scenarios.
Root Cause The cell operator ID is not registered and the configuration cannot
be delivered. Therefore, the cell cannot be automatically
reestablished.
Workaround Deactivate and then activate the cell manually after a cell operator
is added or deleted in MOCN scenarios.
Recovery Reactivate the cell manually.
Measure
Version in Which Versions later than V100R005C00SPC370

the Problem Will
Be Solved
2.3.26 You Cannot Log In to the Web LMT Using Windows

Resource Manager and "This user session already exists" Is
Displayed
Symptom You cannot log in to the Web LMT using Windows resource
manager and a message "This user session already exists" is
displayed.
Impact You cannot log in to the Web LMT.
Impacted Version V100R005C00SPC370 and later

Trigger Condition This fault occurs when the following conditions are met:
1. You have logged in to the Web LMT for this site.
31. You have entered the IP address of the eNodeB in the Windows
resource manager to log in to the Web LMT on the IE.
32. The IE6 or IE7 is running properly.
Root Cause If the IE is redirected using the resource manager, the newly created
IE session conflicts with the existing IE session.
Workaround Open the IE browser, and then enter the IP address of the eNodeB
in the address box to log in to the Web LMT. Alternatively, upgrade
the IE browser to IE8 or IE9.
Recovery N/A
Measure
Solution Add the scenarios where the Web LMT cannot work properly to
eNodeB Web LMT User Guide.
Version in Which V100R005C00SPC385 and later versions
the Problem Will
Be Solved
2.4 V100R005C01
2.4.1 eNodeB Repeatedly Reset Due to Execution of More Than 64
Neighboring Cell Configuration Commands in the Batch
Processing Script
Symptom eNodeB Repeatedly Resets after more than 64 neighboring cell
configuration commands are executed by using the ACT
BATCHFILE batch processing script.
Impact Services are interrupted.
Impacted Version V100R005C00 series

V100R005C01 series
Trigger Condition More than 64 neighboring cell configuration commands are
contained in the ACT BATCHFILE batch processing script.
Root Cause Large amounts of X2 configurations are triggered to update after
many neighboring cell configuration commands are executed by
using the ACT BATCHFILE batch processing script. Each X2
configuration update message requests for 60 KB memory to
inform the peer eNodeBs of the update. The memory can be
released only after the eNodeB responds or the update fails for
more than three times. Therefore, when the ACT BATCHFILE
batch processing script is used, most of the eNodeB memory is
occupied, leading to abnormal reset of eNodeB.
Workaround Either of following solution can prevent this problem:
Solution 1: Ensure that no more than 64 neighboring cell
configuration commands are contained in the ACT BATCHFILE
batch processing script.
Solution 2: Change the execution sequence of the MML commands
contained in the ACT BATCHFILE batch processing script.
The procedure for executing MML commands in the ACT
BATCHFILE batch processing script is as follows:
1. The RMV X2INTERFACE and RMV X2ENODEB
commands are executed to remove all X2 interfaces and peer
eNodeBs, respectively.
33. The neighboring cell configuration commands are executed.
34. The ADD X2INTERFACE and ADD X2ENODEB commands
are executed to add X2 interfaces and peer eNodeBs,
respectively.
Recovery None
Measure
Solution To be determined.

the Problem Will
Be Solved
2.4.2 ALM-26215 Inter-Board Service Link Failure Is Occasionally

Reported If a BBU Houses Multiple LBBPd Boards
Symptom If a BBU houses multiple LBBPd boards, ALM-26215 Inter-Board
Service Link Failure is occasionally reported.
Impact Inter-board cells cannot be activated.
Impacted Version LTE TDD V100R005C01SPC305

 Multiple LBBPd boards are installed in a BBU.
 The inter-board link cannot be initialized.
Root Cause The inter-board link cannot be initialized when the BBU houses
multiple LBBPd boards.
Workaround Reset the LBBP for which the alarm is reported.
Recovery Reset the LBBP for which the alarm is reported.

Measure

the Problem Will
Be Solved
2.4.3 CPRI Line Bit Rate in the DSP CPRILBR Command Output
Occasionally Differs from the Configured Fixed CPRI Line Bit
Rate After the Baseband Processing Board Resets
Symptom After the baseband processing board resets, the CPRI line rate in the
DSP CPRILBR command output occasionally differs from the
configured fixed CPRI line bit rate.
Impact If the CPRI line bit rate in the command output is less than the
configured fixed rate, services are affected.
Impacted Version LTE TDD V100R005C01
Trigger Condition The CPRI line bit rate between the BBU and the RRU is set to a
fixed value, and the baseband processing board resets.
Root Cause After the baseband processing board resets, the configuration
restoration procedure and CPRI link bit rate initial negotiation
procedure are triggered. The configuration restoration procedure is
to restore the configured fixed CPRI link bit rate to the initial
configuration. The CPRI link bit rate initial negotiation procedure is
to negotiate the CPRI link bit rate, which is determined by the
negotiation result. However, the two procedures are performed at
the same time, resulting in modification conflict, and the
modification fails.
Workaround Set CPRI Line Rate to AUTO.
Recovery Run STR CPRILBRNEG to initiate a CPRI line bit rate

Measure negotiation procedure again.
Solution None

the Problem Will
Be Solved
2.5 V100R006C00
2.5.1 IP Path for the X2 or S1 Interface Is not Displayed in the LST
ENODEBPATH Command Output After MOD X2 or MOD S1 Is
Executed to Modify the X2 or S1 Object
Symptom After MOD X2 or MOD S1 is executed to modify the X2 or S1
object, the IP path for the X2 or S1 interface is not displayed in the
LST ENODEBPATH command output.
Impact If the X2 object is modified by running MOD X2, handovers over
the X2 interface fail.
If the S1 object is modified by running MOD S1, UEs cannot
access the network.
Trigger Condition MOD X2 or MOD S1 is executed to modify the configuration of an

X2 or S1 object.
Root Cause After the S1 or X2 object is modified, the S1-U or X2-U self-setup
fails due to code bugs.
Workaround Run ADD ENODEBPATH to add an IP path for the X2-U or S1-U
interface.
Recovery Run RMV S1 or RMV X2 to delete the S1 or X2 object, and run
Measure ADD S1 or ADD X2 to add the S1 or X2 object.

the Problem Will
Be Solved
2.5.2 Primary Operator's X2 Self-setup Fails When the X2 Object

Is Configured Only for the Primary Operator on the eNodeB in
RAN Sharing with a Common Carrier Mode by Running ADD X2
Symptom When the X2 object is configured only for the primary operator on
the eNodeB in RAN sharing with a common carrier mode by
running ADD X2, X2 self-setup for the primary operator fails.
Impact X2 self-setup for the primary operator fails. (The X2 interface
cannot be queried by running LST X2INTERFACE.) Handovers
over the X2 interface fail.
Trigger Condition All of the following conditions are met:

 The eNodeB works in RAN sharing with a common carrier mode.
 The X2 object is configured only for the primary operator.
 UEs served by the network of the secondary operation are
preferentially handed over before those served by the network of
the primary operator.
Root Cause This scenario is not taken into consideration during software design.
Workaround Run ADD X2 to add the X2 object for the secondary operator.
Recovery Run ADD X2 to add the X2 object for the secondary operator.
Measure

the Problem Will
Be Solved
2.5.3 Baseband Processing Board Resets After the License Control

Items of the DL CoMP Feature Are Updated
Symptom The baseband processing board resets after the license control items
of the DL CoMP feature are updated.
Impact The baseband processing board resets.

 The downlink CoMP algorithm switch is enabled.
 License control items of the DL CoMP feature in the license file
are updated.
Root Cause When a cell set changes, the cells in this set are reconfigured. In this
case, memory overwriting occurs, and the baseband processing
board resets.
Workaround Run the MOD CELLALGOSWITCH command to turn off the
downlink CoMP algorithm switch and then update the license
control items. After the update completes, turn on the downlink
CoMP algorithm switch.
Recovery The baseband processing board automatically recovers after it
Measure resets.

the Problem Will
Be Solved
2.5.4 ALM-25952 User Plane Path Fault Is Reported, and Other

Alarms Cannot be Reported
Symptom More than 64 USERPLANEPEER MOs are configured for the
eNodeB and are added to the EPGROUP MO. The EPGROUP
MO is associated with the X2 or S1 link. ALM-25952 User Plane
Path Fault is reported, and more than 64 alarm records are
generated. As a result, other alarms cannot be reported because the
alarm console can display a maximum of 64 alarm records.
Impact Other alarms cannot be reported.
Trigger Condition More than 64 USERPLANEPEER MOs are configured and are
added to the EPGROUP MO. The EPGROUP MO is associated
with the X2 or S1 link.
The GTP-U static check is enabled.
The IP path is faulty in the DSP IPPATH command output.
Root Cause When the GTP-U static check is enabled, ALM-25952 User Plane
Path Fault is reported each time when the eNodeB detects that an IP
path is faulty. If more than 64 USERPLANEPEER MOs are
configured, more than 64 ALM-25952 User Plane Path Fault
records will be reported. However, a maximum of 64 alarm records
can be displayed in the alarm console. As a result, other alarms
cannot be reported.
Workaround Run the MOD GTPU command to change the value of Static
Check Switch from Enable to Disable.
Recovery Rectify the IP path faults to clear ALM-25952 User Plane Path
Measure Fault.
Manually delete ALM-25952 User Plane Path Fault.

the Problem Will
Be Solved
2.5.5 Simultaneously Network Accesses or Handovers of Three or
More UEs Fail After the eNodeB Enables the S1 Self-Setup
Function and the S1 Interface User Plane Link Is Not Configured
Symptom The eNodeB enables the S1 self-setup function and the S1 interface
user plane link is not configured. When three or more UEs initiate
network accesses or handovers simultaneously within 1 second, the
network access or handover fails because the IP path self-setup
fails.
Impact IP path setup fails. As a result, UEs cannot perform network access
or handover.
Trigger Condition Three or more UEs served by the eNodeB initiate network accesses
and handovers within 1 second.
Three or more S-GW IP addresses are configured on the eNodeB
when three or more UEs initiate network accesses or handovers
simultaneously.
The eNodeB enables the S1 self-setup function.
The S-GW user plane IP address is not configured on the eNodeB.
Root Cause The eNodeB stores the IP path setup requests to the buffer, and the
eNodeB can establish IP paths to only two S-GWs. As a result, the
eNodeB cannot process other IP path setup requests, and network
accesses of UEs are affected.
Workaround If the eNodeB connects to three or more than three S-GWs, do not
enable the S1 self-setup function. Run the following commands to
configure the IP path between the eNodeB and the S-GW:
 Run the ADD USERPLANEPEER command to add a user plane
peer.
 Run the ADD UPPEER2EPGRP command to add a user-plane
peer to an end point group.
Recovery Same as the workaround.
Measure

the Problem Will
Be Solved
2.5.6 Some X2 or S1 Interfaces, SCTP Links, and User-Plane Links
Cannot Be Set Up When More Than 32 SCTP Peers Are
Configured
Symptom Some X2 or S1 interfaces, SCTP links, and user-plane links cannot
be set up when both of the following conditions are met:
 More than 32 SCTP peers are configured and are added to the
end point group for the X2 or S1 interface.
 The X2 or S1 interface removed by running the RMV X2 or
RMV S1 command is added again by running the ADD X2 or
ADD S1 command.
Impact Some X2 or S1 interfaces, SCTP links, and user-plane links cannot
be set up.
Impacted Version All V100R006 versions earlier than V100R006C00SPC130
Trigger Condition  More than 32 SCTP peers are configured and are added to the end
point group for the X2 or S1 interface.
 The X2 or S1 interface removed by running the RMV X2 or
RMV S1 command is added again by running the ADD X2 or
ADD S1 command.
Root Cause  When more than 32 SCTP peers are configured, a large number
of objects need to be created. However, only 32 buffering
queues are available. As a result, the eNodeB repeatedly
attempts to create these objects and the message processing
mechanism is overloaded.
 When the message processing mechanism is overloaded, the CFG
module fails to receive any response. As a result, configuration
commands fail to be executed, and the objects fail to be created.
Workaround Remove all the SCTP peers from the end point group by running
the RMV SCTPPEER2EPGRP command, and then add them to
the end point group again by running the ADD
SCTPPEER2EPGRP command.
Measure

the Problem Will
Be Solved
2.5.7 One of the Two 2T2R RRUs Serving a Multi-RRU Cell
Cannot Be Activated and the DSP CELL Command Output
Displays "Abnormal Baseband Unit" in Cell Combination
Scenarios
Symptom In cell combination scenarios, one of the two 2T2R RRUs serving a
multi-RRU cell fails to be activated and the DSP CELL command
output displays "Fault on the LBBP" when all of the following
conditions are true:
 LBBP resource groups are not bound to the cell.
 Two common cells and one multi-RRU cell served by two 2T2R
RRUs are configured on the LBBP.
 The fault in the RRU is rectified.
Impact The RRU cannot be activated and the DSP CELL command output
displays "Fault on the LBBP."
Trigger Condition One of the RRUs serving a multi-RRU cell is faulty and the
recovers.
Root Cause When the fault in the RRU is rectified in the preceding scenarios,
the main control board incorrectly calculates the number of Layer 3
cells. As a result, the LBBP capabilities become insufficient.
Workaround Deactivate and then reactivate the multi-RRU cell.

Measure

the Problem Will
Be Solved
2.5.8 ALM-29243 Cell Capability Degraded Cannot Be Cleared in

an Inter-BBU SFN Cell
Symptom ALM-29243 Cell Capability Degraded is reported in an inter-BBU
SFN cell when the total number of sector equipment associated with
the primary and secondary BBUs exceeds the SectorEqmNum
parameter value and the SFN cell is activated. After the sector
equipment associated with the secondary BBUs is removed, this
alarm persists.
Impact ALM-29243 Cell Capability Degraded cannot be cleared.
Trigger Condition For an inter-BBU SFN cell, the total number of sector equipment
associated with the primary and secondary BBUs exceeds the
SectorEqmNum parameter value.
Root Cause  The number of RRUs configured on the secondary BBUs exceeds
the upper limit. As a result, the inter-BBU SFN cell fails to be
activated on the secondary BBUs.
 There is a bug in the mechanism for determining whether to clear
ALM-29243 Cell Capability Degraded.
Workaround Verify that the total number of sector equipment associated with the
primary and secondary BBUs does not exceed the SectorEqmNum
parameter value.
Measure

the Problem Will
Be Solved
2.5.9 Configuration Files May Fail to Take Effect After Being
Successfully Activated Using the CME
Symptom The configuration files may fail to take effect after being
successfully activated using the CME. When this fault occurs, the
message "The object does not exist" is displayed.
Impact The configuration file cannot be activated and service channels are
disconnected when two or more of the following parameter pairs are
added or removed using the CME.
1 SCTPPEER SCTPPEERREF
2 SCTPHOST SCTPHOSTREF
3 USERPLANEHOST USERPLANEHOSTR
EF
4 USERPLANEPEER USERPLANEPEERR
EF

V100R008C00SPC230
Trigger Condition Two or more of the preceding parameter pairs have been added or
removed using the CME.
For example, the parameters SCTPPEER 0+SCTPPEERREF 0
and SCTPPEER 1+SCTPPEERREF 1 have been added.
Root Cause  To ensure that the configuration file successfully takes effect, the
XXXPEER or XXXHOST parameter must be added prior to the
XXXREF parameter and the XXXREF parameter must be
removed prior to the XXXPEER or XXXHOST parameter.
 After eNodeB configurations are delivered to the eNodeB, the
eNodeB arranges the parameters of each parameter pair in
sequence. If the parameter sequence does not meet the related
requirements, the configuration file fails to be activated.
Workaround Use either of the following workarounds:
 Workaround 1: Set these parameters by running MML
commands.
 Workaround 2: On the CME, add or remove one parameter pair
each time, or add or remove the XXXPEER or XXXHOST
parameters, and then add or remove the XXXREF parameters.
Recovery Measure Reset the eNodeB to make the configuration file take effect.

the Problem Will
Be Solved
2.5.10 A Cell Fails to Be Activated
Symptom A cell fails to be activated and the message "BBI configuration
failed" is displayed.
Impact A cell fails to be activated.

V100R008C00SPC230
Trigger Condition The number of antenna ports for transmitting CRSs is greater than
the number of antennas used in the cell, which does not match the
transmit/receive mode.
Root Cause When the cell is being added, the eNodeB does not check whether
the number of antenna ports for transmitting CRSs matches the
transmit/receive mode. After the cell is added, the eNodeB fails the
verification.
Workaround Configure the number of antenna ports for transmitting CRSs so that
it is equal to or less than the number of antennas used in the cell.

the Problem Will
Be Solved
2.5.11 Multi-RRU Cell Reconstructed from Normal Cells Cannot
Be Activated
Symptom When 18 normal cells configured on the LMPT are reconstructed
into a multi-RRU cell without removing these normal cells, the
multi-RRU cell cannot be activated. After the multi-RRU cell is
reconstructed back into normal cells, these normal cells also cannot
be activated.
Impact The multi-RRU cell cannot be activated on some RRUs, and
information about the RRUs on which the multi-RRU cell is
successfully activated differs from that displayed in the DSP CELL
command output.
Normal cells reconstructed from the multi-RRU cell cannot be
activated.

V100R008C00SPC233
Trigger Condition  The LMPT is fully configured.
 Normal cells configured on the LMPT are reconstructed into a
multi-RRU cell without removing these normal cells.
Root Cause The RRU status is abnormally processed and thereby cannot be
properly displayed.
Workaround Before reconstructing normal cells into a multi-RRU cell, remove
these normal cells.
Recovery Measure Remove the original normal cells and the multi-RRU cell, and then
reconstruct the normal cells into a multi-RRU cell.

the Problem Will
Be Solved
2.6 V100R008C01
2.6.1 EUSECTOREQMGROUP and EUSECTOREQMID2GROUP
Configurations of LampSite Sites Created Using the Default CME
Template Are Lost
Symptom LampSite sites created using the default CME template do not have
EUSECTOREQMGROUP and EUSECTOREQMID2GROUP
configurations.
Impact CME-based configuration check fails.
Trigger Condition The default template of the CME is used to create LampSite sites.
Root Cause The LampSite-specific default template does not include the
EUSECTOREQMGROUP and EUSECTOREQMID2GROUP
MOs.
Workaround Configure the MOs in a summary data file.
Recovery Configure the MOs in a summary data file.

Measure

the Problem Will
Be Solved
2.7 BTS3900 V100R009C00
2.7.1 PER Increases and Cell Throughput Decreases After
TxdDci1aSwitch Is Set to ON
Symptom After the TxdDci1aSwitch paramter is set to ON for a cell, the
packet error rate (PER) increases and the cell throughput decreases.
Impact The PER increases, and the cell throughput decreases.
Impacted Version BTS3900 V100R009C00SPC150

BTS3900 V100R009C00SPC800
BTS3900 V100R009C00SPC820
BTS3900 V100R009C00SPC160
BTS3900 V100R009C00SPC170
Trigger Condition The TxdDci1aSwitch paramter is set to ON. (The default value is
OFF.)
Root Cause Two processes use the same variable simultaneously due to a
software bug.
Workaround Run the MOD CELLDLSCHALGO command with the
TxdDci1aSwitch paramter set to OFF.
Recovery Run the MOD CELLDLSCHALGO command with the
Measure TxdDci1aSwitch paramter set to OFF.
Solution Fix the software bug.

the Problem Will
Be Solved
2.7.2 Number of Preallocated RBs Is Not Subject to the Limitation
on the Preallocated RB Proportion, Causing Severe CCI If
Preallocation Is Enabled and Smart Preallocation and DRX Are
Disabled
Symptom The number of preallocated RBs is not subject to the limitation on
the proportion of preallocated RBs if the following conditions are
met:
 Preallocation is enabled.
 Smart preallocation is disabled.
 Discontinuous reception (DRX) is disabled.
As a result, the co-channel interference (CCI) becomes severe.
Impact The proportion of preallocated RBs exceeds its upper limit. CCI
becomes severe.
Impacted Version BTS3900 V100R009C00SPC820/160/170
Trigger Condition  Preallocation is enabled.

 Smart preallocation is disabled.
 DRX is disabled.
Root Cause Preallocation, which has the lowest priority, increases the PRB
usage on the uplink. In CCI scenarios, the increased PRB usage
leads to more severe interference. As a result, uplink channel
quality deteriorates.
Workaround  If DRX is not allowed at sites for which services must be
guaranteed with the highest priority, run the following
commands to enable smart preallocation and configure the smart
preallocation duration:
MOD CELLALGOSWITCH: LocalCellId=X,
UlSchSwitch=SmartPreAllocationSwitch-1;
MOD CELLULSCHALGO: LocalCellId=X,
SmartPreAllocationDuration=50;
 For other sites, run the following command to enable DRX:
MOD DRX: DrxAlgSwitch=ON;
Recovery Same as the workarounds.
Measure

the Problem Will
Be Solved
2.7.3 eNodeB's UE Access and Processing Performance
Deteriorates After an Incoming Inter-RAT Handover to a Local
Cell If Subframe Configuration 2 Is Used and ACK Feedback
Optimization Is Enabled for HARQ
Symptom eNodeB's performance on UE access and processing deteriorates
after an incoming inter-RAT handover to a local cell if subframe
configuration 2 is used and ACK feedback optimization is enabled
for HARQ.
Impact A subprocess of the main control board (UMPT or LMPT) or the
UBBP resets. During the reset, the UE access and processing
capability of the eNodeB decreases by 1/3. After about 15s, the
eNodeB performance recovers. (No alarm is reported for
subprocess resetting.)
Impacted Version BTS3900 V100R009C00SPC170 and all earlier BTS3900

Trigger Condition  Subframe configurations 2 is used for a cell.
 The TddAckFbModeCfgOptSwitch option is selected under the
HarqAlgoSwitch parameter in the CELLALGOSWITCH
MO. (This option is cleared by default.)
 A UE accesses the cell after an inter-RAT handover.
Root Cause No protection is provided for ACK feedback optimization for
HARQ.
Workaround Run the MOD CELLALGOSWITCH command with the
TddAckFbModeCfgOptSwitch check box cleared under the
HarqAlgoSwitch parameter.
Recovery Same as the workaround.
Measure

the Problem Will
Be Solved
3 Workarounds for the USU
3.1 USU3900 V100R002C00

3.1.1 ALM-29243 Cell Capability Degraded Is Reported for the
BBU Configured for Primary Serving Cells when Inter-BBU SFN
Cells Are Activated in Multi-BBU Interconnection Scenarios
Symptom In application scenarios where multiple BBUs are interconnected
using USUs, ALM-29243 Cell Capability Degraded is reported
for the BBU configured for primary serving cells when inter-BBU
single frequency network (SFN) cells are activated. However,
cells serving by each single BBU can be activated successfully.
Impact Inter-BBU SFN cells cannot be activated. The fault rate is about
0.5%.
Impacted Version All USU3900 versions earlier than USU3900

V100R002C00SPC500
Trigger Condition Multi-BBU interconnection is achieved using USU subracks and

multiple BBU subracks to allow the inter-BBU SFN feature to
work.
However, only BBU subracks are reset after their ODIIDs are
configured by running the SET EQUIPMENT command. USU
subracks are not reset.
Root Cause USU subracks are not reset after the ODIIDs of BBU subracks are
configured by running the SET EQUIPMENT command.
Therefore, the LAN switch port on the UCIU is not protected by
the USU3900 software. In this case, the rate over the LAN switch
port on the UCIU frequently changes with the negotiated rate over
the CI port on the UMPT. As a result, faults occur in the LAN
switch, only one of the two IDX1 channels is normal, and inter-
BBU services are unavailable.
Workaround Reset both the BBU and USU subracks after the ODIIDs of BBU
subracks are configured by running the SET EQUIPMENT
command, to ensure that the open datalink interface (ODI) link
between the BBU and USU is normal.
Recovery Measure Reset the UCIU or SMPT board on the USU subrack by running
the RST BRD command.
Solution Disable the LAN switch on the UCIU during rate negotiation
among inter-BBU optical modules. This prevents the rate over the
LAN switch port being changed.
Version in Which USU3900 V100R002C00SPC500

the Problem Will
Be Solved

OMD-LTE TDD Guide To Avoiding Problems On The Live Network-20141215-A-V3.4

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

OMD-LTE TDD Guide To Avoiding Problems On The Live Network-20141215-A-V3.4

Uploaded by

Copyright:

Available Formats

LTE TDD Guide to Avoiding

Problems on the Live Network

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue 3.3 (2021-04-15) Huawei Proprietary and Confidential i

About This Document

2012-07-13 1.00 Completed the draft. WTL Network

Date Version Description Author

2012-08-21 1.30 Added the following sections: Sun Wenhai

Date Version Description Author

2012-10-24 1.60 Added the following sections: Jiang Lin

Date Version Description Author

2013-03-08 2.00 Added the following sections: Wu Zhi

Date Version Description Author

2013-08-01 2.40 Added the following sections: Jiang Lin

Date Version Description Author

2013-10-09 2.60 Added the following sections: Jiang Lin

Date Version Description Author

2014-01-13 2.80 Added the following sections: Jiang Lin

Date Version Description Author

2014-04-30 3.1 Added the following sections: Jiang Lin

Date Version Description Author

2014-11-18 3.3 Added the following sections: Jiang Lin

About This Document....................................................................................................................ii

2 Workarounds for the eNodeB.....................................................................................................2

2.3.6 Equipment Certificate of eNodeB Cannot Be Updated.............................................................................................40

3 Workarounds for the USU.........................................................................................................75

1.2 Document Update Rules

2.1 Multiple Versions

Impact The RET configuration workload increases.

Impacted LTE TDD

Impacted All versions

Root Cause RET antenna configuration is optional.

Workaround Perform the following workarounds:

In the displayed Create eNodeB dialog box, set Site Version,

3. Save the configuration as a new template.

4. Use the new template for eNodeB configurations.

Recovery Implement the workaround to prepare the configuration file again.

2.1.2 Some Tasks Are Running Without Data Reported in 4 to 5

Impacted RAT LTE TDD

Impacted Version V100R004C00 and V100R005C00

Trigger Condition On the M2000, 15 or more performance monitoring tasks are

Solution The related software defect will be rectified.

Version in Which To be determined.

2.1.3 The SCTP Link Is in the Initialized State and an S1 Interface

Impacted RAT LTE TDD

Impacted Version All V100R004C00 and V100R005C00 versions

Solution Reconstruct the SON model.

Version in Which V100R006C00

2.1.4 The Link Between the eNodeB and M2000 Is Occasionally

Impacted Version V100R004C00SPH271 and earlier

Version in Which To be determined.

2.1.5 Multiple Alarms Are Reported on the M2000 and a Board Is

The board can be a main control board or a baseband processing board.

Impact The newly inserted board is unavailable.

Impacted RAT LTE TDD

Impacted Version V100R004C00SPH271 and earlier versions

Impacted Version V100R004C00SPH271 and earlier versions

Version in Which To be determined.

2.1.7 ALM-25888 SCTP Link Fault and ALM-29240 Cell

Impacted RAT LTE TDD

Impacted Version V100R005C00SPC378 and V100R005C00