List Alarm PDF

Fault Management http://localhost:7890/printtopics.html?time=Tue Nov 13 2012 09:15:0...
Fault Management
Contents
1 Fault Management
1.1 NodeB Alarm Reference
1.1.1 NodeB Alarm List
1.1.2 ALM-25600 Monitoring Device Maintenance Link Failure
1.1.3 ALM-25601 Monitoring Device Hardware Fault
1.1.4 ALM-25602 Sensor Failure
1.1.5 ALM-25620 Monitoring Device Power Supply Problem
1.1.6 ALM-25621 Power Supply DC Output Out of Range
1.1.7 ALM-25622 Mains Input Out of Range
1.1.8 ALM-25623 Load Disconnected
1.1.9 ALM-25624 Battery Power Unavailable
1.1.10 ALM-25625 Battery Current Out of Range
1.1.11 ALM-25626 Power Module Abnormal
1.1.12 ALM-25628 AC Surge Protector Fault
1.1.13 ALM-25630 Power Module and Monitoring Module Communication Failure
1.1.14 ALM-25631 Load Fuse Broken
1.1.15 ALM-25632 Battery Cabin Heater Fault
1.1.16 ALM-25633 PMU Internal Interface Communication Failure
1.1.17 ALM-25634 Battery Not In Position
1.1.18 ALM-25636 Loss of Power Supply Redundancy
1.1.19 ALM-25650 Ambient Temperature Unacceptable
1.1.20 ALM-25651 Ambient Humidity Unacceptable
1.1.21 ALM-25652 Cabinet Temperature Unacceptable
1.1.22 ALM-25653 Cabinet Humidity Unacceptable
1.1.23 ALM-25654 Battery Temperature Unacceptable
1.1.24 ALM-25655 Cabinet Air Outlet Temperature Unacceptable
1.1.25 ALM-25656 Cabinet Air Inlet Temperature Unacceptable
1.1.26 ALM-25657 TEC Cooler Fault
1.1.27 ALM-25670 Water Alarm
1.1.28 ALM-25671 Smoke Alarm
1.1.29 ALM-25672 Burglar Alarm
1.1.30 ALM-25673 Fan Stalled
1.1.31 ALM-25695 Diesel Generator Fault
1.1.32 ALM-25696 Diesel Generator Low Fuel
1.1.33 ALM-25697 Diesel Generator Startup Failure
1.1.34 ALM-25710 Loss of Solar Array
1.1.35 ALM-25711 Solar Array Fault
1.1.36 ALM-25713 Solar Controller Temperature Unacceptable
1.1.37 ALM-25719 CCU Topology and Configuration Mismatch
1.1.38 ALM-25720 Inter-CCU Port Connection Error
1.1.39 ALM-25721 CCU-BBU Communication Failure
1.1.40 ALM-25800 E1/T1 Loss of Signal
1.1.41 ALM-25801 E1/T1 Alarm Indication Signal
1.1.42 ALM-25802 E1/T1 Remote Alarm Indication Signal
1.1.43 ALM-25803 E1/T1 Loss of Frame Alignment
1.1.44 ALM-25804 E1/T1 Loss of Multiframe Alignment
1.1.45 ALM-25805 E1/T1 Excessive Slip Frames
1.1.46 ALM-25806 E1/T1 Excessive Bit Error Rate
1 de 526 13/11/2012 9:15

1.1.47 ALM-25807 E1/T1 Loopback

1.1.48 ALM-25820 Fractional ATM Link Loss of Cell Delineation
1.1.49 ALM-25821 IMA/ATM Link Loss of Cell Delineation
1.1.50 ALM-25823 IMA Link Loss of Frame
1.1.51 ALM-25824 IMA Link Out of Delay Synchronization
1.1.52 ALM-25825 IMA Link Remote Failure Indication
1.1.53 ALM-25826 IMA Link RX Fault
1.1.54 ALM-25827 IMA Link TX Unusable at Far End
1.1.55 ALM-25828 IMA Link RX Unusable at Far End
1.1.56 ALM-25829 IMA Group Startup at Far End
1.1.57 ALM-25830 IMA Group Configuration Aborted
1.1.58 ALM-25831 IMA Group Configuration Aborted at Far End
1.1.59 ALM-25832 IMA Group Activated Links Insufficient
1.1.60 ALM-25833 IMA Group Activated Links Insufficient at Far End
1.1.61 ALM-25834 IMA Group Blocked at Far End
1.1.62 ALM-25835 NCP Fault
1.1.63 ALM-25836 CCP Fault
1.1.64 ALM-25837 ALCAP Fault
1.1.65 ALM-25838 AAL2 Path Fault
1.1.66 ALM-25840 SAAL Link Fault
1.1.67 ALM-25841 SAAL Link Congestion
1.1.68 ALM-25860 PPP/MLPPP Link Fault
1.1.69 ALM-25861 MLPPP Group Fault
1.1.70 ALM-25862 MLPPP Group Excessive Packet Loss Rate
1.1.71 ALM-25863 PPP Link Excessive Frame Error Rate
1.1.72 ALM-25879 Ethernet Port Broadcast Packets Exceeding Alarm
1.1.73 ALM-25880 Ethernet Link Fault
1.1.74 ALM-25881 MAC Excessive Frame Error Rate
1.1.75 ALM-25882 ETHOAM 3AH Discovery Failure
1.1.76 ALM-25883 ETHOAM 3AH Local Fault
1.1.77 ALM-25884 ETHOAM 3AH Remote Fault
1.1.78 ALM-25885 IP Address Conflict
1.1.79 ALM-25886 IP Path Fault
1.1.80 ALM-25887 Ethernet Trunk Link Fault
1.1.81 ALM-25888 SCTP Link Fault
1.1.82 ALM-25889 SCTP Link Congestion
1.1.83 ALM-25891 IKE Negotiation Failure
1.1.84 ALM-25894 ETHOAM 3AH Remote Loopback
1.1.85 ALM-25895 Ethernet Trunk Group Fault
1.1.86 ALM-25896 IP Remote Loopback
1.1.87 ALM-25897 IP Excessive Frame Error Rate
1.1.88 ALM-25898 IP Path Excessive Packet Loss Rate
1.1.89 ALM-25899 BFD Session Fault
1.1.90 ALM-25900 IP PM Activation Failure
1.1.91 ALM-25901 Remote Maintenance Link Failure
1.1.92 ALM-25902 Remote Maintenance Link Running Data and Configuration Mismatch
1.1.93 ALM-25920 SDH/SONET Loss of Frame Alignment
1.1.94 ALM-25921 SDH/SONET Loss of Frame
1.1.95 ALM-25922 SDH/SONET Loss of Signal
1.1.96 ALM-25923 SDH/SONET AU Loss of Pointer
1.1.97 ALM-25924 SDH/SONET MS Alarm Indication Signal
1.1.98 ALM-25925 SDH/SONET MS Remote Defect Indication
1.1.99 ALM-25926 SDH/SONET Loss of Cell Delineation
1.1.100 ALM-25927 SDH/SONET Optical Port Loopback
1.1.101 ALM-25928 SDH/SONET RS Trace Identifier Mismatch
2 de 526 13/11/2012 9:15

1.1.102 ALM-25929 SDH/SONET RS Excessive Bit Error Rate

1.1.103 ALM-25930 SDH/SONET MS Excessive Bit Error Rate
1.1.104 ALM-25931 SDH/SONET MS Signal Degraded
1.1.105 ALM-25932 SDH/SONET MS Remote Error Indication
1.1.106 ALM-25933 SDH/SONET AU Alarm Indication Signal
1.1.107 ALM-25934 SDH/SONET HP Unequipped Defect
1.1.108 ALM-25935 SDH/SONET HP Signal Label Mismatch
1.1.109 ALM-25936 SDH/SONET HP Trace Identifier Mismatch
1.1.110 ALM-25937 SDH/SONET HP Remote Defect Indication
1.1.111 ALM-25938 SDH/SONET HP Remote Error Indication
1.1.112 ALM-25949 Excessive Flood Packet
1.1.113 ALM-25950 Base Station Being Attacked
1.1.114 ALM-26101 Inter-Board CANBUS Communication Failure
1.1.115 ALM-26104 Board Temperature Unacceptable
1.1.116 ALM-26106 Board Clock Input Unavailable
1.1.117 ALM-26107 Board Input Voltage Out of Range
1.1.118 ALM-26110 BBU Fan Stalled
1.1.119 ALM-26111 BBU Fan Not at Full Speed
1.1.120 ALM-26112 BBU DC Output Out of Range
1.1.121 ALM-26113 Base Station DC Power Supply Abnormal
1.1.122 ALM-26120 GPS Clock Output Unavailable
1.1.123 ALM-26121 GPS Antenna Fault
1.1.124 ALM-26122 GPS Locked Satellites Insufficient
1.1.125 ALM-26123 GPS Maintenance Link Failure
1.1.126 ALM-26200 Board Hardware Fault
1.1.127 ALM-26201 Board Memory Soft Failure
1.1.128 ALM-26202 Board Overload
1.1.129 ALM-26203 Board Software Program Error
1.1.130 ALM-26204 Board Not In Position
1.1.131 ALM-26205 BBU Board Maintenance Link Failure
1.1.132 ALM-26206 Main Control Board in Wrong Slot
1.1.133 ALM-26208 Board File System Damaged
1.1.134 ALM-26210 Board Blocked
1.1.135 ALM-26214 Board Powered Off
1.1.136 ALM-26215 Inter-Board Service Link Failure
1.1.137 ALM-26216 Board Not Securely Installed
1.1.138 ALM-26220 Transmission Optical Module Fault
1.1.139 ALM-26221 Transmission Optical Module Not In Position
1.1.140 ALM-26222 Transmission Optical Interface Error
1.1.141 ALM-26223 Transmission Optical Interface Performance Degraded
1.1.142 ALM-26230 BBU CPRI Optical Module Fault
1.1.143 ALM-26231 BBU CPRI Optical Module or Electrical Port Not Ready
1.1.144 ALM-26232 BBU Optical Module Transmit/Receive Fault
1.1.145 ALM-26233 BBU CPRI Optical Interface Performance Degraded
1.1.146 ALM-26234 BBU CPRI Interface Error
1.1.147 ALM-26235 RF Unit Maintenance Link Failure
1.1.148 ALM-26236 RRU Cascading Levels and Configuration Mismatch
1.1.149 ALM-26237 RRU Network Breakpoint
1.1.150 ALM-26238 RRU Network Topology Type and Configuration Mismatch
1.1.151 ALM-26240 BBU Topology and Configuration Mismatch
1.1.152 ALM-26241 Configuration File Update Failure
1.1.153 ALM-26242 Configuration File Damaged
1.1.154 ALM-26245 Configuration Data Inconsistency
1.1.155 ALM-26250 Active Workspace Version Unavailable
1.1.156 ALM-26251 Board Type and Configuration Mismatch
3 de 526 13/11/2012 9:15

1.1.157 ALM-26253 Board Software Auto-Supply Failure

1.1.158 ALM-26254 Board Software Synchronization Failure
1.1.159 ALM-26255 Automatic Version Rollback
1.1.160 ALM-26260 System Clock Failure
1.1.161 ALM-26261 External Clock Reference Not Configured
1.1.162 ALM-26262 External Clock Reference Problem
1.1.163 ALM-26263 IP Clock Link Failure
1.1.164 ALM-26264 System Clock Unlocked
1.1.165 ALM-26265 Base Station Frame Number Synchronization Error
1.1.166 ALM-26266 Time Synchronization Failure
1.1.167 ALM-26270 Inter-System Communication Failure
1.1.168 ALM-26271 Inter-System Monitoring Device Parameter Settings Conflict
1.1.169 ALM-26272 Inter-System RF Unit Parameter Settings Conflict
1.1.170 ALM-26273 Inter-System BBU Board Parameter Settings Conflict
1.1.171 ALM-26274 Inter-System Board Object Configuration Conflict
1.1.172 ALM-26275 Inter-System Cabinet Configuration Conflict
1.1.173 ALM-26276 Inter-System Site-Level Configuration Conflict
1.1.174 ALM-26277 Inter-System Control Rights Conflict
1.1.175 ALM-26278 RF Unit Working Mode and Mode Capability Inconsistency
1.1.176 ALM-26279 Inter-System Board Installation and Configuration Mismatch
1.1.177 ALM-26310 Inter-BBU Optical Module Fault
1.1.178 ALM-26311 Inter-BBU Optical Module Not in Position
1.1.179 ALM-26312 Inter-BBU Optical Module Receive Failure
1.1.180 ALM-26313 Inter-BBU Optical Module Transmit Failure
1.1.181 ALM-26314 Inter-BBU Port Failure
1.1.182 ALM-26315 Inter-BBU Port Connection Error
1.1.183 ALM-26501 RF Unit Optical Module or Electrical Port Not Ready
1.1.184 ALM-26502 RF Unit Optical Module Type Mismatch
1.1.185 ALM-26503 RF Unit Optical Module Transmit/Receive Fault
1.1.186 ALM-26504 RF Unit CPRI Interface Error
1.1.187 ALM-26506 RF Unit Optical Interface Performance Degraded
1.1.188 ALM-26507 RF Unit Optical Module Fault
1.1.189 ALM-26520 RF Unit TX Channel Gain Out of Range
1.1.190 ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low
1.1.191 ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced
1.1.192 ALM-26524 RF Unit PA Overcurrent
1.1.193 ALM-26525 RF Unit Temperature Unacceptable
1.1.194 ALM-26527 RF Unit Input Power Out of Range
1.1.195 ALM-26529 RF Unit VSWR Threshold Crossed
1.1.196 ALM-26530 RF Unit ALD Current Out of Range
1.1.197 ALM-26531 RF Unit ALD Switch Configuration Mismatch
1.1.198 ALM-26532 RF Unit Hardware Fault
1.1.199 ALM-26533 RF Unit Software Program Error
1.1.200 ALM-26534 RF Unit Overload
1.1.201 ALM-26536 RF Unit Multi-Mode Configuration Conflict
1.1.202 ALM-26538 RF Unit Clock Problem
1.1.203 ALM-26540 RF Unit AC Input Power Failure
1.1.204 ALM-26541 ALD Maintenance Link Failure
1.1.205 ALM-26542 RF Unit Backup Power Device Maintenance Link Failure
1.1.206 ALM-26543 RF Unit External Device Maintenance Link Failure
1.1.207 ALM-26544 RF Unit Power Surge Protector Fault
1.1.208 ALM-26545 RF Unit TX Channel Switched Off Through Command
1.1.209 ALM-26546 RF Unit External Power Supply Insufficient
1.1.210 ALM-26751 RET Antenna Motor Fault
1.1.211 ALM-26752 ALD Hardware Fault
4 de 526 13/11/2012 9:15

1.1.212 ALM-26753 RET Antenna Not Calibrated

1.1.213 ALM-26754 RET Antenna Data Loss
1.1.214 ALM-26755 TMA Bypass
1.1.215 ALM-26756 SASU VSWR Threshold Crossed
1.1.216 ALM-26757 RET Antenna Running Data and Configuration Mismatch
1.1.217 ALM-26758 TMA Running Data and Configuration Mismatch
1.1.218 ALM-26759 SASU Running Data and Configuration Mismatch
1.1.219 ALM-26760 SASU Bypass
1.1.220 ALM-26765 RHUB Hardware Fault
1.1.221 ALM-26766 RHUB Software Program Error
1.1.222 ALM-26767 RHUB Overload
1.1.223 ALM-26768 RHUB Clock Problem
1.1.224 ALM-26770 UPS Surge Protection Device Fault
1.1.225 ALM-26771 Mains Breakdown with UPS
1.1.226 ALM-26772 UPS Battery Undervoltage
1.1.227 ALM-26773 UPS Failure
1.1.228 ALM-26774 RHUB AC/DC Maintenance Link Failure
1.1.229 ALM-26775 RHUB AC/DC Module Problem
1.1.230 ALM-26776 RHUB PSE Power Supply Failure
1.1.231 ALM-26777 RHUB PSE Fault
1.1.232 ALM-26780 RHUB Optical Module or Electrical Port Not Ready
1.1.233 ALM-26781 RHUB Optical Module Type Mismatch
1.1.234 ALM-26782 RHUB Optical Module Transmit/Receive Fault
1.1.235 ALM-26783 RHUB CPRI Interface Error
1.1.236 ALM-26785 RHUB Optical Interface Performance Degraded
1.1.237 ALM-26786 RHUB Optical Module Fault
1.1.238 ALM-26787 RHUB-PRRU CPRI Interface Error
1.1.239 ALM-26810 License Data Loss
1.1.240 ALM-26811 Configured Capacity Limit Exceeding Licensed Limit
1.1.241 ALM-26812 System Dynamic Traffic Exceeding Licensed Limit
1.1.242 ALM-26830 Local User Consecutive Login Retries Failed
1.1.243 ALM-26832 Peer Certificate Expiry
1.1.244 ALM-26840 Imminent Certificate Expiry
1.1.245 ALM-26841 Certificate Invalid
1.1.246 ALM-26842 Automatic Certificate Update Failed
1.1.247 ALM-28201 Local Cell Blocked
1.1.248 ALM-28203 Local Cell Unusable
1.1.249 ALM-28204 Cell DL Load Simulation Startup
1.1.250 ALM-28205 Cell Output Power too Low
1.1.251 ALM-28206 Local Cell Capability Decline
1.1.252 ALM-28207 Carrier Wave Share Failure
1.1.253 ALM-28209 Cell No Traffic
1.1.254 ALM-28210 Frequency Separation Configuration Mismatch
1.1.255 ALM-28211 Cell Configuration Abnormal
1.1.256 ALM-28221 IMB Local Cell Blocked
1.1.257 ALM-28223 IMB Local Cell Unusable
1.1.258 ALM-28224 IMB Cell Output Power too Low
1.1.259 ALM-28225 IMB Local Cell Capability Decline
1.1.260 ALM-28226 IMB Cell Configuration Abnormal
1.1.261 ALM-28230 Base Station Service Overload
1.1.262 ALM-28244 GPS Receiver Hardware Fault
1.1.263 ALM-28245 GPS Receiver Antenna Power Problem
1.1.264 ALM-28246 GPS Receiver Antenna Fault
1.1.265 ALM-28247 GPS Receiver Software Program Error
1.1.266 ALM-28248 GPS Receiver Position Not Locked
5 de 526 13/11/2012 9:15

1.1.267 ALM-28249 GPS Receiver Maintenance Link Failure

1.1.268 ALM-28250 GPS Receiver Initialization Configuration Failure
1.1.269 ALM-28253 Ethernet Link Abnormal
1.1.270 ALM-28255 Transport Configuration Failure
1.1.271 ALM-28300 Board Uplink Service Processing Channel Abnormal
1.1.272 ALM-28301 Board Downlink Service Processing Channel Abnormal
1.1.273 ALM-28302 Board BFN Abnormal
1.1.274 ALM-28303 WBBP-WBBP Interface Abnormal
1.1.275 ALM-28329 RF Unit Input Power Abnormal
1.1.276 ALM-28330 RF Unit Over Backward Power Alarm
1.1.277 ALM-28350 Board Configuration Inconsistent with Resource Group Configuration
1.1.278 ALM-28354 Transport Backup Not Support
1.1.279 ALM-28355 Data Configuration File Error
1.1.280 ALM-28381 Board Startup Abnormal Alarm
1.1.281 ALM-65033-ALM-65233 External Analog/Boolean Alarm
1.2 NodeB Event Reference
1.2.1 NodeB Event List
1.2.2 EVT-25890 SCTP Link Path Switchover
1.2.3 EVT-25893 Remote Maintenance Link Switchover
1.2.4 EVT-26212 Board Startup
1.2.5 EVT-26213 NE Startup
1.2.6 EVT-26256 NE Software Download Started
1.2.7 EVT-26257 NE Software Download Ended
1.2.8 EVT-26258 NE Software Activation Started
1.2.9 EVT-26259 NE Software Activation Ended
1.2.10 EVT-26505 RF Unit CPRI Interface Switchover
1.2.11 EVT-26526 RF Unit TX Channel Switched Off
1.2.12 EVT-26528 RF Unit TX Channel Switched On
1.2.13 EVT-26535 RF Unit Startup
1.2.14 EVT-26784 RHUB CPRI Interface Switchover
1.2.15 EVT-26820 License Emergency Status Activated
1.2.16 EVT-26821 License Emergency Status Ceased
1.2.17 EVT-28200 Iub Common Procedure Failure Indication
1.2.18 EVT-28202 Local Cell Rebuild
1.2.19 EVT-28222 IMB Local Cell Rebuild
1.2.20 EVT-28251 Ethernet Configuration Changed
1.2.21 EVT-28252 IP RAN Object Reset
1.2.22 EVT-28352 Enable Downloaded Configuration File
1.2.23 EVT-28353 Disable Downloaded Configuration File
1.2.24 EVT-28380 NE Shutdown
1 Fault Management
Related Document Description
NodeB Alarm Reference This document describes NodeB alarm reference.
NodeB Event Reference This document describes NodeB event reference.
1.1 NodeB Alarm Reference

Purpose
This document describes all the alarms of the BTS3900 WCDMA, BTS3900A WCDMA, BTS3900L WCDMA,
6 de 526 13/11/2012 9:15

BTS3900C WCDMA, BTS3900AL WCDMA, and DBS3900 WCDMA. The MML commands involved in this
document takes NodeB_2U for example.
Version
The following table lists the product versions involved in this document.
Product Name Version
BTS3900 WCDMA (hereinafter referred to as BTS3900) V200R014C00
BTS3900A WCDMA (hereinafter referred to as BTS3900A) V200R014C00
BTS3900L WCDMA (hereinafter referred to as BTS3900L) V200R014C00
BTS3900C WCDMA (hereinafter referred to as BTS3900C) V200R014C00
BTS3900AL WCDMA (hereinafter referred to as BTS3900AL) V200R014C00
DBS3900 WCDMA (hereinafter referred to as DBS3900) V200R014C00
Intended Audience
This document is intended for:
Field engineers
System engineers
Shift operators
Site maintainers
Network operators
Concepts
Concept Description
Alarm ID Unique identifier of an alarm in one product.
Alarm Name Unique name of an alarm in one product. Alarm names clearly and accurately indicate alarm
meanings. There is a one-to-one mapping between alarm names and IDs.
Alarm Type There is only one alarm type: fault.
Alarm Level Impact of an alarm on service quality. There are four alarm severity levels: critical, major,
minor, and warning.
Critical alarm: affects service quality. If a critical alarm is generated, immediate
actions are necessary even when the fault occurs during non-working hours.
Major alarm: affects service quality and requires immediate action during working
hours.
Minor alarm: generally does not affect service quality, but requires handling or
observation in a reasonable amount of time to avoid more serious faults.
Warning alarm: indicates a potential error that may affect service quality. It
requires different actions depending on errors.
Event Type There are 16 event types based on monitored objects.

Power alarm: relates to the power system.
7 de 526 13/11/2012 9:15

Concept Description
Environment alarm: relates to equipment room environment variables, such as

temperature, humidity, and door control.
Signaling alarm: relates to channel associated signaling (for example, SS1) and
common channel signaling (for example, SS7).
Trunk alarm: relates to the trunk system, including trunk circuits and boards.
Hardware alarm: relates to hardware, such as the clock unit and CPU.
Software alarm: relates to software.
System alarm: generated during system operation.
Communication alarm: relates to communication.
Service quality alarm: relates to service quality.
Unexpected operation alarm: generated when an exception occurs.
OMC alarm: generated when the OMC is not working properly.
Integrity alarm: generated when information is illegally modified or deleted.
Operation alarm: generated when service is unavailable or inaccessible because
of inappropriate operations.
Physical resource alarm: generated when physical resources are damaged by a
suspected security attack.
Security alarm: generated when security service or a security mechanism has
detected that the system encounters security attacks.
Time domain alarm: generated when an event occurs at an unexpected or
forbidden time.
Description Conditions in which an alarm is generated.
Parameters Parameters related to alarms.
Impact on the Impact of an alarm on the system or services.

System
System Actions Actions taken by the system when an alarm is generated.
Possible Issues that may result in an alarm. Possible causes are categorized into data configuration,
Causes hardware, software, and other causes.
Procedure Procedure for clearing an alarm step by step.
Change History
For detailed alarm changes, see the release notes.
1.1.1 NodeB Alarm List
Alarm ID Alarm Name Alarm Type Alarm Level Event Type
ALM-25600 Monitoring Device Fault Major Communication

Maintenance Link
Failure
ALM-25601 Monitoring Device Fault Major Hardware

Hardware Fault
ALM-25602 Sensor Failure Fault Major Hardware
8 de 526 13/11/2012 9:15

ALM-25620 Monitoring Device Fault Major Hardware

Power Supply
Problem
ALM-25621 Power Supply DC Fault Major Power

Output Out of
Range
ALM-25622 Mains Input Out of Fault Major Power

Range
ALM-25623 Load Disconnected Fault Major/Warning Power
ALM-25624 Battery Power Fault Major/Warning Power

Unavailable
ALM-25625 Battery Current Fault Major Power

Out of Range
ALM-25626 Power Module Fault Major/Warning Power

Abnormal
ALM-25628 AC Surge Fault Major Power

Protector Fault
ALM-25630 Power Module and Fault Major Power

Monitoring Module
Communication
Failure
ALM-25631 Load Fuse Broken Fault Major Power
ALM-25632 Battery Cabin Fault Major Power

Heater Fault
ALM-25633 PMU Internal Fault Major Power

Interface
Communication
Failure
ALM-25634 Battery Not In Fault Major Power

Position
ALM-25636 Loss of Power Fault Warning Power

Supply
Redundancy
ALM-25650 Ambient Fault Major/Minor Environment

Temperature
Unacceptable
ALM-25651 Ambient Humidity Fault Minor Environment

Unacceptable
9 de 526 13/11/2012 9:15

ALM-25652 Cabinet Fault Major/Minor Environment

Temperature
Unacceptable
ALM-25653 Cabinet Humidity Fault Minor Environment

Unacceptable
ALM-25654 Battery Fault Major/Minor Power

Temperature
Unacceptable
ALM-25655 Cabinet Air Outlet Fault Major/Minor Environment

Temperature
Unacceptable
ALM-25656 Cabinet Air Inlet Fault Major/Minor Environment

Temperature
Unacceptable
ALM-25657 TEC Cooler Fault Fault Major Environment
ALM-25670 Water Alarm Fault Critical Environment
ALM-25671 Smoke Alarm Fault Critical Environment
ALM-25672 Burglar Alarm Fault Critical Environment
ALM-25673 Fan Stalled Fault Major Hardware
ALM-25695 Diesel Generator Fault Major Hardware

Fault

Low Fuel

Startup Failure
ALM-25710 Loss of Solar Fault Major Hardware

Array
ALM-25711 Solar Array Fault Fault Major Hardware
ALM-25713 Solar Controller Fault Minor Hardware

Temperature
Unacceptable
ALM-25719 CCU Topology and Fault Major Environment

Configuration
Mismatch
ALM-25720 Inter-CCU Port Fault Major Environment

Connection Error
ALM-25721 CCU-BBU Fault Minor Environment

Communication
10 de 526 13/11/2012 9:15

Failure
ALM-25800 E1/T1 Loss of Fault Major Trunk

Signal
ALM-25801 E1/T1 Alarm Fault Major Trunk

Indication Signal
ALM-25802 E1/T1 Remote Fault Minor Trunk

Alarm Indication
Signal
ALM-25803 E1/T1 Loss of Fault Major Trunk

Frame Alignment
ALM-25804 E1/T1 Loss of Fault Minor Trunk

Multiframe
Alignment
ALM-25805 E1/T1 Excessive Fault Minor Trunk

Slip Frames
ALM-25806 E1/T1 Excessive Fault Minor Trunk

Bit Error Rate
ALM-25807 E1/T1 Loopback Fault Minor Trunk
ALM-25820 Fractional ATM Fault Major Trunk

Link Loss of Cell
Delineation
ALM-25821 IMA/ATM Link Fault Major Trunk

Loss of Cell
Delineation
ALM-25823 IMA Link Loss of Fault Major Trunk

Frame
ALM-25824 IMA Link Out of Fault Major Trunk

Delay
Synchronization
ALM-25825 IMA Link Remote Fault Minor Trunk

Failure Indication
ALM-25826 IMA Link RX Fault Fault Major Trunk
ALM-25827 IMA Link TX Fault Minor Trunk

Unusable at Far
End
ALM-25828 IMA Link RX Fault Minor Trunk

Unusable at Far
End
11 de 526 13/11/2012 9:15

ALM-25829 IMA Group Startup Fault Minor Trunk

at Far End
ALM-25830 IMA Group Fault Major Trunk

Configuration
Aborted
ALM-25831 IMA Group Fault Minor Trunk

Configuration
Aborted at Far End
ALM-25832 IMA Group Fault Major Trunk

Activated Links
Insufficient

Activated Links
Insufficient at Far
End

Blocked at Far End
ALM-25835 NCP Fault Fault Major Communication
ALM-25836 CCP Fault Fault Major Communication
ALM-25837 ALCAP Fault Fault Major Signaling
ALM-25838 AAL2 Path Fault Fault Major Trunk
ALM-25840 SAAL Link Fault Fault Major Trunk
ALM-25841 SAAL Link Fault Major Trunk

Congestion
ALM-25860 PPP/MLPPP Link Fault Major Trunk

Fault
ALM-25861 MLPPP Group Fault Major Trunk

Fault
ALM-25862 MLPPP Group Fault Minor Trunk

Excessive Packet
Loss Rate
ALM-25863 PPP Link Fault Minor Trunk

Excessive Frame
Error Rate
ALM-25879 Ethernet Port Fault Major Trunk

Broadcast Packets
Exceeding Alarm
ALM-25880 Ethernet Link Fault Fault Major Trunk
12 de 526 13/11/2012 9:15

ALM-25881 MAC Excessive Fault Minor Trunk

Frame Error Rate
ALM-25882 ETHOAM 3AH Fault Minor Trunk

Discovery Failure

Local Fault

Remote Fault
ALM-25885 IP Address Conflict Fault Minor Trunk
ALM-25886 IP Path Fault Fault Major Trunk
ALM-25887 Ethernet Trunk Fault Minor Trunk

Link Fault
ALM-25888 SCTP Link Fault Fault Major Trunk
ALM-25889 SCTP Link Fault Minor Trunk

Congestion
ALM-25891 IKE Negotiation Fault Major Trunk

Failure
ALM-25894 ETHOAM 3AH Fault Major Trunk

Remote Loopback
ALM-25895 Ethernet Trunk Fault Major Trunk

Group Fault
ALM-25896 IP Remote Fault Major Trunk

Loopback
ALM-25897 IP Excessive Fault Minor Trunk

Frame Error Rate
ALM-25898 IP Path Excessive Fault Minor Trunk

Packet Loss Rate
ALM-25899 BFD Session Fault Fault Minor Trunk
ALM-25900 IP PM Activation Fault Minor Trunk

Failure
ALM-25901 Remote Fault Major Trunk

Maintenance Link
Failure
ALM-25902 Remote Fault Minor Trunk

Maintenance Link
Running Data and
Configuration
Mismatch
13 de 526 13/11/2012 9:15

ALM-25920 SDH/SONET Loss Fault Major Trunk

of Frame
Alignment

of Frame

of Signal
ALM-25923 SDH/SONET AU Fault Major Trunk

Loss of Pointer
ALM-25924 SDH/SONET MS Fault Major Trunk

Alarm Indication
Signal

Remote Defect
Indication

of Cell Delineation
ALM-25927 SDH/SONET Fault Warning Trunk

Optical Port
Loopback
ALM-25928 SDH/SONET RS Fault Minor Trunk

Trace Identifier
Mismatch
ALM-25929 SDH/SONET RS Fault Minor Trunk

Excessive Bit Error
Rate
ALM-25930 SDH/SONET MS Fault Minor Trunk

Excessive Bit Error
Rate

Signal Degraded

Remote Error
Indication
ALM-25933 SDH/SONET AU Fault Major Trunk

Alarm Indication
Signal
ALM-25934 SDH/SONET HP Fault Major Trunk

Unequipped Defect
14 de 526 13/11/2012 9:15

ALM-25935 SDH/SONET HP Fault Minor Trunk

Signal Label
Mismatch
ALM-25936 SDH/SONET HP Fault Minor Trunk

Trace Identifier
Mismatch

Remote Defect
Indication

Remote Error
Indication
ALM-25949 Excessive Flood Fault Major Trunk

Packet
ALM-25950 Base Station Being Fault Major Security

Attacked
ALM-26101 Inter-Board Fault Minor Hardware

CANBUS
Communication
Failure
ALM-26104 Board Fault Major/Minor Environment

Temperature
Unacceptable
ALM-26106 Board Clock Input Fault Major Hardware

Unavailable
ALM-26107 Board Input Fault Major Hardware

Voltage Out of
Range
ALM-26110 BBU Fan Stalled Fault Major Hardware
ALM-26111 BBU Fan Not at Fault Major Hardware

Full Speed
ALM-26112 BBU DC Output Fault Major Power

Out of Range
ALM-26113 Base Station DC Fault Major Power

Power Supply
Abnormal
ALM-26120 GPS Clock Output Fault Minor Hardware

Unavailable
ALM-26121 GPS Antenna Fault Fault Minor Hardware
15 de 526 13/11/2012 9:15

ALM-26122 GPS Locked Fault Minor Running

Satellites
Insufficient
ALM-26123 GPS Maintenance Fault Minor Running

Link Failure
ALM-26200 Board Hardware Fault Major/Minor Hardware

Fault
ALM-26201 Board Memory Fault Minor Hardware

Soft Failure
ALM-26202 Board Overload Fault Minor Running
ALM-26203 Board Software Fault Major Running

Program Error
ALM-26204 Board Not In Fault Major Hardware

Position
ALM-26205 BBU Board Fault Major Hardware

Maintenance Link
Failure
ALM-26206 Main Control Fault Major Hardware

Board in Wrong
Slot
ALM-26208 Board File System Fault Major Hardware

Damaged
ALM-26210 Board Blocked Fault Major Running
ALM-26214 Board Powered Fault Major Hardware

Off
ALM-26215 Inter-Board Fault Major Hardware

Service Link
Failure
ALM-26216 Board Not Fault Major Hardware

Securely Installed
ALM-26220 Transmission Fault Warning Hardware

Optical Module
Fault
ALM-26221 Transmission Fault Major Hardware

Optical Module Not
In Position
ALM-26222 Transmission Fault Major/Minor Hardware

Optical Interface
Error
16 de 526 13/11/2012 9:15

ALM-26223 Transmission Fault Major/Minor Communication

Optical Interface
Performance
Degraded
ALM-26230 BBU CPRI Optical Fault Warning Hardware

Module Fault
ALM-26231 BBU CPRI Optical Fault Major Hardware

Module or
Electrical Port Not
Ready
ALM-26232 BBU Optical Fault Major/Minor Hardware

Module
Transmit/Receive
Fault
ALM-26233 BBU CPRI Optical Fault Major/Minor Hardware

Interface
Performance
Degraded
ALM-26234 BBU CPRI Fault Major Hardware

Interface Error
ALM-26235 RF Unit Fault Major Hardware

Maintenance Link
Failure
ALM-26236 RRU Cascading Fault Major Hardware

Levels and
Configuration
Mismatch
ALM-26237 RRU Network Fault Major Hardware

Breakpoint
ALM-26238 RRU Network Fault Major Hardware

Topology Type and
Configuration
Mismatch
ALM-26240 BBU Topology and Fault Major Hardware

Configuration
Mismatch
ALM-26241 Configuration File Fault Major Running

Update Failure
ALM-26242 Configuration File Fault Major Running

Damaged
ALM-26245 Configuration Data Fault Major Running

Inconsistency
17 de 526 13/11/2012 9:15

ALM-26250 Active Workspace Fault Major Running

Version
Unavailable
ALM-26251 Board Type and Fault Major Running

Configuration
Mismatch

Auto-Supply
Failure

Synchronization
Failure
ALM-26255 Automatic Version Fault Major Running

Rollback
ALM-26260 System Clock Fault Major Hardware

Failure
ALM-26261 External Clock Fault Minor Hardware

Reference Not
Configured
ALM-26262 External Clock Fault Minor Hardware

Reference
Problem
ALM-26263 IP Clock Link Fault Minor Hardware

Failure
ALM-26264 System Clock Fault Major/Minor Hardware

Unlocked
ALM-26265 Base Station Fault Major Hardware

Frame Number
Synchronization
Error
ALM-26266 Time Fault Minor Communication

Synchronization
Failure
ALM-26270 Inter-System Fault Major Hardware

Communication
Failure
ALM-26271 Inter-System Fault Warning Running

Monitoring Device
Parameter
Settings Conflict
18 de 526 13/11/2012 9:15

ALM-26272 Inter-System RF Fault Major/Warning Running

Unit Parameter
Settings Conflict
ALM-26273 Inter-System BBU Fault Major/Warning Running

Board Parameter
Settings Conflict
ALM-26274 Inter-System Fault Major Running

Board Object
Configuration
Conflict
ALM-26275 Inter-System Fault Minor Running

Cabinet
Configuration
Conflict

Site-Level
Configuration
Conflict

Control Rights
Conflict
ALM-26278 RF Unit Working Fault Major Hardware

Mode and Mode
Capability
Inconsistency
ALM-26279 Inter-System Fault Minor Software

Board Installation
and Configuration
Mismatch
ALM-26310 Inter-BBU Optical Fault Warning Hardware

Module Fault
ALM-26311 Inter-BBU Optical Fault Major Hardware

Module Not in
Position
ALM-26312 Inter-BBU Optical Fault Major/Minor Hardware

Module Receive
Failure
ALM-26313 Inter-BBU Optical Fault Major/Minor Hardware

Module Transmit
Failure
ALM-26314 Inter-BBU Port Fault Major Hardware

Failure
19 de 526 13/11/2012 9:15

ALM-26315 Inter-BBU Port Fault Major Hardware

Connection Error
ALM-26501 RF Unit Optical Fault Major Communication

Module or
Electrical Port Not
Ready

Module Type
Mismatch

Module
Transmit/Receive
Fault
ALM-26504 RF Unit CPRI Fault Major Communication

Interface Error

Interface
Performance
Degraded
ALM-26507 RF Unit Optical Fault Warning Communication

Module Fault
ALM-26520 RF Unit TX Fault Minor Hardware

Channel Gain Out
of Range
ALM-26521 RF Unit RX Fault Minor Hardware

Channel
RTWP/RSSI Too
Low
ALM-26522 RF Unit RX Fault Minor Hardware

Channel
RTWP/RSSI
Unbalanced
ALM-26524 RF Unit PA Fault Major Hardware

Overcurrent
ALM-26525 RF Unit Fault Major/Minor Hardware

Temperature
Unacceptable
ALM-26527 RF Unit Input Fault Major Hardware

Power Out of
Range
ALM-26529 RF Unit VSWR Fault Major/Minor Hardware

Threshold Crossed
20 de 526 13/11/2012 9:15

ALM-26530 RF Unit ALD Fault Minor/Warning Hardware

Current Out of
Range
ALM-26531 RF Unit ALD Fault Minor Hardware

Switch
Configuration
Mismatch
ALM-26532 RF Unit Hardware Fault Major/Minor Hardware

Fault
ALM-26533 RF Unit Software Fault Major Running

Program Error
ALM-26534 RF Unit Overload Fault Minor Running
ALM-26536 RF Unit Multi-Mode Fault Minor Running

Configuration
Conflict
ALM-26538 RF Unit Clock Fault Major Hardware

Problem
ALM-26540 RF Unit AC Input Fault Major Power

Power Failure
ALM-26541 ALD Maintenance Fault Major Communication

Link Failure
ALM-26542 RF Unit Backup Fault Major Communication

Power Device
Maintenance Link
Failure
ALM-26543 RF Unit External Fault Major Communication

Device
Maintenance Link
Failure
ALM-26544 RF Unit Power Fault Major Hardware

Surge Protector
Fault
ALM-26545 RF Unit TX Fault Warning Running

Channel Switched
Off Through
Command
ALM-26546 RF Unit External Fault Major/Minor Hardware

Power Supply
Insufficient
ALM-26751 RET Antenna Fault Minor Hardware

Motor Fault
21 de 526 13/11/2012 9:15

ALM-26752 ALD Hardware Fault Major/Minor Hardware

Fault
ALM-26753 RET Antenna Not Fault Minor Hardware

Calibrated
ALM-26754 RET Antenna Data Fault Minor Hardware

Loss
ALM-26755 TMA Bypass Fault Major Hardware
ALM-26756 SASU VSWR Fault Major Hardware

Threshold Crossed
ALM-26757 RET Antenna Fault Minor Hardware

Running Data and
Configuration
Mismatch
ALM-26758 TMA Running Data Fault Minor Hardware

and Configuration
Mismatch
ALM-26759 SASU Running Fault Minor Hardware

Data and
Configuration
Mismatch
ALM-26760 SASU Bypass Fault Major Hardware
ALM-26765 RHUB Hardware Fault Major/Minor Hardware

Fault
ALM-26766 RHUB Software Fault Major Running

Program Error
ALM-26767 RHUB Overload Fault Minor Running
ALM-26768 RHUB Clock Fault Major Hardware

Problem
ALM-26770 UPS Surge Fault Major Hardware

Protection Device
Fault
ALM-26771 Mains Breakdown Fault Major Hardware

with UPS
ALM-26772 UPS Battery Fault Major Hardware

Undervoltage
ALM-26773 UPS Failure Fault Major Hardware
ALM-26774 RHUB AC/DC Fault Major Hardware

Maintenance Link
Failure
22 de 526 13/11/2012 9:15

ALM-26775 RHUB AC/DC Fault Major Hardware

Module Problem
ALM-26776 RHUB PSE Power Fault Major Hardware

Supply Failure
ALM-26777 RHUB PSE Fault Fault Major Hardware
ALM-26780 RHUB Optical Fault Major Communication

Module or
Electrical Port Not
Ready

Module Type
Mismatch

Module
Transmit/Receive
Fault
ALM-26783 RHUB CPRI Fault Major Communication

Interface Error
ALM-26785 RHUB Optical Fault Major/Minor Communication

Interface
Performance
Degraded
ALM-26786 RHUB Optical Fault Minor Communication

Module Fault
ALM-26787 RHUB-PRRU CPRI Fault Major Communication

Interface Error
ALM-26810 License Data Loss Fault Major Running
ALM-26811 Configured Fault Major Running

Capacity Limit
Exceeding
Licensed Limit
ALM-26812 System Dynamic Fault Major Running

Traffic Exceeding
Licensed Limit
ALM-26830 Local User Fault Minor Security

Consecutive Login
Retries Failed
ALM-26832 Peer Certificate Fault Minor Security

Expiry
23 de 526 13/11/2012 9:15

ALM-26840 Imminent Fault Minor Security

Certificate Expiry
ALM-26841 Certificate Invalid Fault Major Security
ALM-26842 Automatic Fault Minor Security

Certificate Update
Failed
ALM-28201 Local Cell Blocked Fault Minor QoS
ALM-28203 Local Cell Fault Major QoS

Unusable
ALM-28204 Cell DL Load Fault Minor QoS

Simulation Startup
ALM-28205 Cell Output Power Fault Minor QoS

too Low
ALM-28206 Local Cell Fault Major QoS

Capability Decline
ALM-28207 Carrier Wave Fault Minor QoS

Share Failure
ALM-28209 Cell No Traffic Fault Minor QoS
ALM-28210 Frequency Fault Minor QoS

Separation
Configuration
Mismatch
ALM-28211 Cell Configuration Fault Major QoS

Abnormal
ALM-28221 IMB Local Cell Fault Minor QoS

Blocked
ALM-28223 IMB Local Cell Fault Major QoS

Unusable
ALM-28224 IMB Cell Output Fault Minor QoS

Power too Low
ALM-28225 IMB Local Cell Fault Major QoS

Capability Decline
ALM-28226 IMB Cell Fault Major QoS

Configuration
Abnormal
ALM-28230 Base Station Fault Minor QoS

Service Overload
24 de 526 13/11/2012 9:15

ALM-28244 GPS Receiver Fault Minor Hardware

Hardware Fault

Antenna Power
Problem

Antenna Fault

Software Program
Error

Position Not
Locked
ALM-28249 GPS Receiver Fault Minor Communication

Maintenance Link
Failure

Initialization
Configuration
Failure
ALM-28253 Ethernet Link Fault Major Trunk

Abnormal
ALM-28255 Transport Fault Major Running

Configuration
Failure
ALM-28300 Board Uplink Fault Major Hardware

Service Processing
Channel Abnormal
ALM-28301 Board Downlink Fault Major/Minor Hardware

Service Processing
Channel Abnormal
ALM-28302 Board BFN Fault Major Hardware

Abnormal
ALM-28303 WBBP-WBBP Fault Major Hardware

Interface Abnormal
ALM-28329 RF Unit Input Fault Major Hardware

Power Abnormal
ALM-28330 RF Unit Over Fault Major Hardware

Backward Power
Alarm
25 de 526 13/11/2012 9:15

ALM-28350 Board Fault Major Running

Configuration
Inconsistent with
Resource Group
Configuration
ALM-28354 Transport Backup Fault Major Running

Not Support
ALM-28355 Data Configuration Fault Major Running

File Error
ALM-28381 Board Startup Fault Major Running

Abnormal Alarm
ALM-65033- External Fault Major Environment

ALM-65233 Analog/Boolean
Alarm
1.1.2 ALM-25600 Monitoring Device Maintenance Link Failure

Description
This alarm is reported when the maintenance link between the BBU/RRU and the monitoring device fails or the
maintenance link between monitoring devices fails.
Parameters
Parameter Name Parameter Description
Cabinet No. Cabinet number of the monitoring device
Subrack No. Subrack number of the monitoring device
Slot No. Slot number of the monitoring device
Board Type Type of the monitoring device
Connect Port No. Serial port No. connected to the monitoring device
Communication Address Communication address of the monitoring device
Impact on the System
Alarm Severity Alarm Impact
Major The system cannot monitor the status of the monitoring device.
Operators cannot configure or maintain the monitoring device.
System Actions
None
Possible Causes
The monitoring device is configured in a wrong cabinet/subrack/slot, or configured with a wrong serial
port or communication address.
26 de 526 13/11/2012 9:15

The monitoring device is not powered on or fails to be detected.
The cable connections are faulty between the BBU/RRU and the monitoring device, between CCUs,
or between a CCU and another monitoring device.
The cable is loose, worn-out, or broken between the BBU/RRU and the monitoring device, between
CCUs, or between a CCU and another monitoring device.
The DIP switch setting of the monitoring device is wrong.
The monitoring device is faulty.

The BBU is faulty.
Procedure
1. Check the configuration on the M2000.
a. Run the MML command SCN RS485 to check whether the cabinet/subrack/slot,
connected serial port, and communication address of the faulty monitoring device, as
well as the cabinet/subrack/slot of the device managing the faulty monitoring device are
consistent with the configuration plan.
Y => The information is consistent. Go to step 2.
N => The information is inconsistent. Go to sub-step b.
b. Run the MML command RMV PMU(PMU)/RMV TCU(TCU)/RMV EMU(EMU)/RMV
FMU(FMU) to remove the faulty monitoring device.
Run the MML command ADD PMU(PMU)/ADD TCU(TCU)/ADD EMU(EMU)/ADD
FMU(FMU) to add the monitoring device according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the monitoring device on site.
a. Check whether the monitoring device specified in the alarm location parameters is
properly installed and powered on. When the power switch is turned on and the RUN
indicator is on, it indicates that the monitoring device is powered on.
Y => The monitoring device is properly installed and powered on. Go to step 3.
N => The monitoring device is improperly installed or not powered on. Go to sub-step b.
b. Install the monitoring device properly and power it on.

3. Check the cable connections for the monitoring device on site.
a. Check whether the cables for the monitoring device are properly connected based on
the installation guide.
Y => The cables are properly connected. Go to sub-step c.
N => The cables are improperly connected. Go to sub-step b.
b. Reconnect the cables properly for the monitoring device.

27 de 526 13/11/2012 9:15

N => The alarm is not cleared. Go to sub-step c.
c. Check whether the cables for the monitoring device are functional and the connections
are correct.
Y => The cables are functional and the connections are correct. Go to step 4.
N => The cables are loose, worn-out, damaged, or incorrectly connected. Go to
sub-step d.
d. Reconnect or replace the cables.

4. (Skip this step and go to step 5 if the device is not configured with the DIP switch) Check the
communication address of the monitoring device on site.
a. Check the DIP switch settings of the monitoring device.

Y => The DIP switch settings are correct. Go to step 5.
N => The DIP switch settings are incorrect. Go to sub-step b.
b. Power off the monitoring device, set the DIP switch correctly, and then power on the
monitoring device.
5. Replace the monitoring device on site.
a. Replace the monitoring device.

6. Replace the faulty unit of the BBU on site.
a. Note: If there is only one UPEU configured in the BBU or there are two UPEUs
configured in the high-power-consumption BBU, replacing the UPEU interrupts all the
ongoing services of the base station. Therefore, perform the replacement in low-traffic
hours.
Replace the BBU environment interface unit on site.
N => The alarm is not cleared. Go to sub-step b.
b. Note: Replacing the main control board interrupts all the ongoing services of the base
station. Therefore, perform the replacement in low-traffic hours. A base station
software upgrade may be required during board replacement, so the correct software
version must be ready for use in advance.
Replace the main control board on site.
28 de 526 13/11/2012 9:15

N => The alarm is not cleared. Contact Huawei Customer Service Center.
1.1.3 ALM-25601 Monitoring Device Hardware Fault

Description
This alarm is reported when the hardware of the monitoring device is faulty.
Parameters
Major Some or all the monitoring functions of the monitoring device fail.
System Actions
None
Possible Causes
The software of the monitoring device malfunctions.

The hardware of the monitoring device is faulty.
Procedure
1. Reset the monitoring device on the M2000.
a. Run the MML command RST BRD to reset the faulty monitoring device on the M2000.
Wait until the startup is complete, Check whether the alarm is cleared.
2. Power cycle the monitoring device on site.
a. Power cycle the faulty monitoring device, or remove and then insert the faulty
monitoring device on site.
Wait until the startup is complete, Check whether the alarm is cleared.

29 de 526 13/11/2012 9:15

1.1.4 ALM-25602 Sensor Failure

Description
This alarm is reported when a sensor is faulty.
Parameters
Parameter
Name Parameter Description
Sensor No. Faulty sensor number (Battery temperature sensor 1, Battery temperature sensor 2, Cabinet
humidity sensor, Cabinet temperature sensor 1, Cabinet temperature sensor 2, Cabinet ambient
temperature sensor, Air inlet temperature sensor, Air outlet temperature sensor, Current sensor
of the diesel generator)
Major The system cannot monitor the alarms detected by the sensor.
System Actions
None
Possible Causes
The cable connection of the sensor is faulty.

The sensor is faulty.
The corresponding monitoring device is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:

25600 Monitoring Device Maintenance Link Failure (the "Board Type" parameter is
TCU.)
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm according to the relevant handling suggestions.

30 de 526 13/11/2012 9:15

2. Check the sensor and its cable connection on site.
a. Check whether the cable between the monitoring device and the sensor is functional
and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 3.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.

3. Replace the sensor on site.
a. Replace the sensor.


1.1.5 ALM-25620 Monitoring Device Power Supply Problem

Description
This alarm is reported when the DC input to the monitoring device has a problem.
Parameters
Specific Problem Specific Problem of the alarm(DC Overvoltage, DC Undervoltage, DC Failure)
Major Some or all the monitoring functions of the monitoring device fail.
If the monitoring device is an EDU, the devices carried on the EDU may be powered
off. In this case, the ongoing services are disrupted.
System Actions
31 de 526 13/11/2012 9:15

If the monitoring device is an EDU, the devices carried on the EDU are powered off.
Possible Causes
The power cable for the monitoring device is faulty. For example, the power cable is loosely
connected, worn-out, or damage.
The input power malfunctions.
Procedure
1. Check for the correlated alarm of the base station on the M2000.
a. Check for the correlated alarm on the M2000.

25621 Power Supply DC Output Out of Range
b. Clear the correlated alarm with recommended actions.

2. Check the power cable of the monitoring device on site.
a. Check whether the power cable between the monitoring device and the power supply
device is normal.
Y => The power cable is functional and its connection is correct. Go to step 3.
N => The power cable malfunctions or its connection is incorrect. Go to sub-step b.
b. Reconnect or replace the power cable.

3. Check the input power of the monitoring device on site.
a. Check whether the input power voltage of the monitoring device is within the normal
range.
Y => The input power voltage is within the normal range. Go to step 4.
N => The input power voltage is beyond the normal range. Go to sub-step b.
b. Contact the customer to set the input power voltage of the non-Huawei power supply
device within the normal range.

32 de 526 13/11/2012 9:15


1.1.6 ALM-25621 Power Supply DC Output Out of Range

Description
This alarm is reported when the DC output of the power system is out of range.
Parameters
Specific Problem Specific Problem of the alarm(DC Overvoltage, DC Undervoltage)
Major The DC output overvoltage may cause damage to the boards of the base station. In
this case, the ongoing services carried on the boards are disrupted.
The DC output undervoltage may lead to board power-off at the base station. In this
case, the ongoing services carried on the boards are disrupted.
System Actions
None
Possible Causes
The AC input is out of range.

The PSU is faulty.
The alarm threshold setting is incorrect.

The battery charge is insufficient.
Procedure

25622 Mains Input Out of Range
25626 Power Module Abnormal
25711 Solar Array Fault
33 de 526 13/11/2012 9:15


2. Check the threshold of the power supply DC output out of range alarm of the power supply system.
a. Run the MML command LST PMU to query the settings for the power supply DC output
out of range alarm. Check whether the alarm threshold is correct according to the
configuration planning.
Y => The alarm threshold is correct. Go to step 3.
N => The alarm threshold is incorrect. Go to sub-step b.
b. Run the MML command MOD PMU to set the alarm threshold based on the
3. Check the batteries on site.
a. Measure the voltage of the battery to check whether the voltage is lower than the
undervoltage threshold obtained in step 2.
Y => The battery voltage is lower than the alarm threshold. Go to sub-step b.
N => The battery voltage is not lower than the alarm threshold. Go to step 4.
b. Start the diesel generator to charge batteries.

N => The alarm is not cleared. Go to step 4

1.1.7 ALM-25622 Mains Input Out of Range

Description
This alarm is reported when the mains input is out of range.
Parameters
Parameter
34 de 526 13/11/2012 9:15

Specific Problem Specific Problem of the alarm(AC Failure, AC Phase Loss, AC Overvoltage, AC
Undervoltage)
Major In the case that AC failure or AC phase loss occurs:

If batteries are configured, the NE is powered by batteries and operates normally
until the batteries are depleted. If Load Low Voltage Disconnected (LLVD) is
enabled, the load is powered off when the LLVD threshold is reached. In this case,
the ongoing services carried on the load are disrupted.
In the case that AC undervoltage occurs:
The DC output power decreases and therefore some boards are powered off. In this
case, the life span of power system is shortened.
In the case that AC overvoltage occurs:
The power module may stop providing power. Some boards may be powered off. In
this case, the life span of power system is shortened.
System Actions
None
Possible Causes
The alarm threshold setting is improper.

The AC Miniature Circuit Breaker (MCB) is switched off.
The AC input power cable is faulty.
The AC power network or the power distribution is faulty.
Procedure
1. Locate the cause of the alarm on the M2000.
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "AC Overvoltage" or "AC Undervoltage", go to step 2.
If "Specific Problem" is "AC Failure" or "AC Phase Loss", go to step 3.
2. Check the threshold of the mains input out of range alarm.
a. Run the MML command LST PMU to query the mains input out of range alarm. Check
whether the alarm threshold is proper according to the configuration planning.
Y => The threshold is proper. Go to step 4.
N => The threshold is improper. Go to sub-step b.
35 de 526 13/11/2012 9:15

3. Check the setting of the AC MCB on site.
a. Check whether the AC MCB is switched on.

Y => The AC MCB is switched on. Go to step 4.
N => The AC MCB is switched off. Go to sub-step b.
b. Switch on the AC MCB.
4. Check the connections of the AC input power cable on site.
a. Check whether the AC input power cable is properly connected.

Y => The cable is properly connected. Go to step 5.
N => The cable is improperly connected. Go to sub-step b.

5. Check the AC power network and power distribution on site.
a. Check whether the AC power network and power distribution are functional.
Y => The AC power network and power distribution are functional. Go to step 6.
N => The AC power network or power distribution malfunctions. Go to sub-step b.
b. Rectify the fault in the power supply for the base station.

1.1.8 ALM-25623 Load Disconnected

Description
This alarm is reported when the load (including the RF unit) is powered off.
Parameters
36 de 526 13/11/2012 9:15

Specific Problem Specific Problem of the alarm(Low Voltage, High Temperature, Remote Control)
Major The ongoing services carried on the load are disrupted.
Warning The load is powered off remotely, and the ongoing services carried on the load are
disrupted.
System Actions
None
Possible Causes
The AC input is out of range.
The power module is faulty.
The solar array fails to provide the DC output.
The solar array is faulty.
Procedure

25621 Power Supply DC Output Out of Range
25711 Solar Array Fault

37 de 526 13/11/2012 9:15

1.1.9 ALM-25624 Battery Power Unavailable

Description
This alarm is reported when the batteries are depleted, the battery temperature is extremely high, or when the
batteries are powered off manually or remotely.
Parameters
Parameter
Specific Problem Specific Problem of the alarm(Low Voltage, High Temperature, Manual Stop, Remote
Control)
Major When the batteries are disconnected due to low voltage, the base station stops
working and all related services are disrupted. The services are resumed only after
the AC power supply is available.
When the batteries are shut down at a high temperature, the battery charging or
discharging is stopped. If the AC power supply is unavailable, the base station stops
working and the ongoing services are disrupted. If the AC power supply is available,
the base station continues normal operation.
Warning The batteries cannot provide any power.
System Actions
None
Possible Causes
The mains input is out of range.

The batteries are overheated.

The batteries are powered off manually.
Procedure

25654 Battery Temperature Unacceptable
38 de 526 13/11/2012 9:15

25655 Cabinet Air Outlet Temperature Unacceptable


2. Check the battery button on the panel of the PMU on site.
a. Press the BAT ON button on the panel of the PMU and hold it for 5 to 10 seconds.
Ensure that the batteries are powered on.

1.1.10 ALM-25625 Battery Current Out of Range

Description
This alarm is reported when the battery current is out of range during charging and discharging.
Parameters
Parameter
Specific Specific Problem of the alarm(Loop Broken, Charging Overcurrent, Discharging Imbalance,
Problem Discharging Overcurrent)
Major If overcurrent occurs during battery charging, the life span of batteries is shortened.
The batteries cannot work because the battery loop is broken.
The voltage of the batteries is imbalanced, which makes the backup power capacity
of batteries insufficient.
If overcurrent occurs during battery discharging, the power consumption of the base
39 de 526 13/11/2012 9:15

station decreases and therefore the cell coverage area shrinks.
System Actions
None
Possible Causes
The batteries are not installed.
The circuit breaker of the batteries is switched off or the battery contactor is switched off.
The batteries are faulty or worn-out.
Procedure
a. Check whether one of the following correlated alarms is reported on the M2000:
25624 Battery Power Unavailable
Y => A correlated alarm is reported. Go to sub-step b.
N => A correlated alarm is not reported.Go to step 2.
2. Locate the alarm cause on the M2000.
a. Locate the cause of alarm based on the alarm detailed information.

If "Specific Problem" is "Discharging Overcurrent", go to sub-step b
If "Specific Problem" is the other value, go to step 3.
b. Raise the batter capacity or reduce the traffic load (for example,by shutting down an
RF unit) based on the configuration plan.
3. Check the batteries onsite.
a. Check whether the batteries are installed.

Y => The batteries are installed. Go to step 4.
N => The batteries are not installed. Go to sub-step b.
b. Check whether the batteries are required based on the configuration plan.
Y => The batteries are required. Go to sub-step c.
N => The batteries are not required. Go to sub-step d.
40 de 526 13/11/2012 9:15

c. Install the batteries.

d. Run the MML command RMV BATTERY to remove the batteries.

4. Check the circuit breaker and fuse of the batteries on site.
a. Check whether the circuit breaker is switched off or the fuse of batteries is
disconnected.
Y => The circuit breaker is switched off or the fuse is disconnected. Go to sub-step b.
N => The circuit breaker is switched on and the fuse is connected. Go to step 5.
b. Switch on the circuit breaker or replace the faulty fuse.

5. Check the difference between the battery voltage and the midpoint voltage of the battery group on
site.
a. Measure the battery voltage and the midpoint voltage of the battery group. Check
whether their difference exceeds the threshold. If the battery voltage is larger than
(midpoint voltage x 2 + 0.6) or lower than (midpoint voltage x 2 - 0.6), you can infer that
the difference exceeds the threshold.
Y => The difference exceeds the threshold. Go to sub-step b.
N => The difference is lower than the threshold. Go to step 6.
b. Inform the maintenance personnel to diagnose and clear the fault on site.

1.1.11 ALM-25626 Power Module Abnormal

Description
This alarm is reported when the power module fails.
Parameters
41 de 526 13/11/2012 9:15

Parameter
PSU Slot No. Slot number of the faulty power module
Specific Problem Specific Problem of the alarm(Power Module Fault, Power Module Protection, Power
Module Shutdown)
Major The power module is faulty. The faulty power module cannot provide the DC power
and cannot be recovered automatically. This fault weakens the DC power capability
of the base station and may affect some services.
The power module self-protection is being performed. The faulty power module
cannot output DC power supply, but it can be recovered automatically after the fault
is rectified. The services may be affected for a while.
Warning The power module is shut down. The faulty power module operates normally, but
cannot output DC power supply for a while because the power module is shut down
manually or the AC power supply is cut off. The services may be affected for a
while.
System Actions
None
Possible Causes
The cabinet is overheated.

The mains input is out of range.

Procedure

25652 Cabinet Temperature Unacceptable
25654 Battery Temperature Unacceptable
25650 Ambient Temperature Unacceptable
42 de 526 13/11/2012 9:15


2. Replace the power module on site.
a. Replace the power module.


1.1.12 ALM-25628 AC Surge Protector Fault

Description
This alarm is reported when the AC surge protector of the base station is faulty.
Parameters
Major The AC surge protection function fails.
System Actions
None
Possible Causes
The cable connection between the AC surge protector and the monitoring device is loose or broken.
The AC surge protector fails.

Procedure
1. Check the cable connection between the surge protector and the monitoring device on site.
43 de 526 13/11/2012 9:15

a. Check whether the cable between the surge protector and the monitoring device is
functional and the connection is correct.
b.

2. Check the surge protector.
a. Check whether the alarm output port of the surge protector is closed.
Y => The alarm output port is closed. Go to step 3.
N => The alarm output port is open. Go to sub-step b.
b. Replace the surge protector.

1.1.13 ALM-25630 Power Module and Monitoring Module Communication

Failure
Description
This alarm is reported when the monitoring module fails to communicate with the power module properly.
Parameters
PSU Slot No. Slot number of the faulty power module
Major The power module is not installed or not in position. The faulty power module cannot
44 de 526 13/11/2012 9:15

provide the DC power. This fault weakens the DC power capability of the base
station and may affect some services.
The power module is in position, but its communication with the monitoring module
fails. The faulty power module is not in control of the monitoring module. The services
may be affected for a while.
System Actions
None
Possible Causes
The power module is not secure or not in position.
The monitoring module is not securely installed.
The monitoring module is faulty.
Procedure
1. Check the power module on site.
a. Check whether the power module is installed in the slot of the subrack of the cabinet
specified in the alarm detailed information on site.
Y => The power module is installed. Go to sub-step b.
N => The power module is not installed. Go to sub-step c.
b. Remove the power module, and then reinstall it properly.

c. Install the power module.

2. Check the installation of the monitoring module on site.
a. Remove the monitoring module, and then reinstall it properly.

a. Replace the power module.

45 de 526 13/11/2012 9:15

4. Replace the monitoring module on site.

1.1.14 ALM-25631 Load Fuse Broken

Description
This alarm is reported when a load fuse is broken.
Parameters
Major The equipment associated with the broken fuse is powered off, which interrupts the
ongoing services carried by the equipment.
System Actions
None
Possible Causes
The load fuse is broken or not in position.
Procedure
1. Check the load fuse on site.
a. Check whether the load fuse is installed.

Y => The load fuse is installed. Go to sub-step c.
N => The load fuse is not installed. Go to sub-step b.
b. Install a spare fuse.

c. Locate the faulty fuse by checking the output voltage of the power system, the solar
controller, or the equipment which is powered off, and then replace the load fuse.
46 de 526 13/11/2012 9:15

1.1.15 ALM-25632 Battery Cabin Heater Fault

Description
This alarm is reported when the heater of the battery cabin is faulty.
Parameters
Major The performance of batteries is degraded and the life span is shortened.
System Actions
None
Possible Causes
The AC input power cable of the heater is not properly connected.

The heater is faulty.
The temperature sensor in the battery cabin is faulty.
Procedure
1. Check the battery temperature and ambient temperature on the M2000.
a. After the AC power supply for the heater operates normally for one hour, run the MML
command DSP PMU to query the battery temperature, and run the MML command
DSP EMU to query the ambient temperature.
Check whether both the battery temperature and the ambient temperature are lower
than -20°C.
Y => Both the battery temperature and the ambient temperature are lower than -20°C.
Go to sub-step b.
N => The battery temperature or the ambient temperature is not lower than -20°C. Go
to step 2.
b. Replace the heater on site.
2. Check the Miniature Circuit Breaker (MCB) state and connections of the AC input power cable of
the heater on site.
47 de 526 13/11/2012 9:15

a. Check whether the AC input power cable of the heater is functional, and check whether
the MCB of the heater is switched on.
Y => The cable is functional and the MCB is switched on. Go to step 3.
N => The cable is loose, worn-out, damaged, incorrectly connected, or the MCB is not
switched on. Go to sub-step b.
b. Reconnect or replace the cable, or switch on the MCB.

3. Replace the temperature sensor in the battery cabin on site.

1.1.16 ALM-25633 PMU Internal Interface Communication Failure

Description
This alarm is reported when the PMU cannot communicate with the DSAC (signal access board) properly.
Parameters
Major The system cannot monitor the status of the monitoring device.
The system cannot configure or maintain the monitoring device.
System Actions
None
Possible Causes
The communication cable between the DSAC and the monitoring device fails.
The DSAC fails.
Procedure
1. Check the connections of the communication cable on site.
48 de 526 13/11/2012 9:15

a. Check whether the cable between the DSAC and the monitoring device is functional and
the connection is correct.
N => The cable is loose, worn-out, damaged, or incorrectly connected.. Go to sub-step
b.

2. Replace the DSAC on site.
a. Replace the DSAC.


1.1.17 ALM-25634 Battery Not In Position

Description
This alarm is reported when the batteries fail to be detected.
Parameters
Major The batteries cannot supply the backup power. Therefore, the entire system is
powered off when the AC input fails.
System Actions
None
Possible Causes
49 de 526 13/11/2012 9:15

The battery parameters are incorrectly set.
The batteries are not installed or the cable connections are abnormal.
The circuit breaker of the battery cabinet is not switch on.
Procedure
1. Check the battery configuration on the M2000.
a. Check whether the cabinet needs to be configured with batteries based on the
configuration plan on the M2000.
Y => The batteries need to be configured. Go to step 2.
N => The batteries do not need to be configured. Go to sub-step b.
b. Run the MML command RMV BATTERY to remove the batteries on the M2000.
2. Check the installation of batteries on site.
a. Check whether the batteries are installed on site.

Y => The batteries are installed. Go to step 3.
N => The batteries are not installed. Go to sub-step b.
b. Reinstall the batteries properly. Then, switch on the circuit breaker.
c. Run the MML command RST BRD on the M2000 to reset the corresponding monitoring
device. Alternatively, power cycle or reseat the corresponding monitoring device on site.
Wait until its startup is complete.
3. Check the battery loop on site.
a. Check whether the battery loop is functional and all circuit breakers are switched on.
Y => The battery loop is functional and all circuit breakers are switched on. Go to step
4.
N => The battery loop malfunctions or a circuit breaker is not switched on. Go to
sub-step b.
b. Reconnect the cables of batteries.
c. Run the MML command RST BRD on the M2000 to reset the corresponding monitoring
device. Alternatively, power cycle or reseat the corresponding monitoring device on site.
Wait until its startup is complete.
50 de 526 13/11/2012 9:15


1.1.18 ALM-25636 Loss of Power Supply Redundancy

Description
This alarm is reported when N+1 backup of power modules cannot be achieved because the number of
configured power modules in the power system is insufficient.
Parameters
Load current Load current
Battery current Battery current
Voltage DC Voltage
Warning N+1 backup of power modules cannot be achieved. The power supply capability of
the power system will be insufficient if a power module malfunctions.
System Actions
None
Possible Causes
The number of configured power modules is insufficient and N+1 backup of power modules cannot be achieved.
Procedure
1. Add a power module on site.
a. Install a power module on site. Then, configure the new power module by running the
MML command ADD PSU on the M2000. Wait for at least 15 minutes.
b. Repeat step 1 until the alarm is cleared or until all the slots are occupied.
51 de 526 13/11/2012 9:15

1.1.19 ALM-25650 Ambient Temperature Unacceptable

Description
This alarm is reported when the ambient temperature is too high or too low.
Parameters
Specific Problem Specific Problem of the alarm(Too High, Too Low)
Major The device may be damaged because of a high temperature. In this case, the
ongoing services are disrupted.
Minor The normal operation of the device is affected, and the ongoing services may be
disrupted.
System Actions
None
Possible Causes
The setting of the alarm threshold is improper.

The ambient temperature in the equipment room is abnormal.
The cable connection is faulty.

The temperature sensor malfunctions.
Procedure
1. Check the threshold setting for the ambient temperature alarm of the monitoring device on the
M2000.
a. Run the MML command LST EMU to query the threshold of ambient temperature
alarm. Check whether the alarm threshold is proper according to the configuration
planning.
b. Run the MML command MOD EMU to set the alarm threshold based on the
52 de 526 13/11/2012 9:15


2. Check the ambient temperature in the equipment room on site.
a. Check whether the ambient temperature in the equipment room is normal by checking
the environment monitoring device (like the thermometer) in the equipment room.
Y => The temperature is within the normal range. Go to step 3.
N => The temperature is out of range. Go to b.
b. Check the air conditioner or other air-conditioning device in the equipment room, and
clear the fault.
3. Check the cable connection between the temperature sensor and the monitoring device on site.
a. Check whether the cable between the corresponding sensor and the monitoring device
is functional and the connection is correct.
b.
4. Replace the temperature sensor on site.


1.1.20 ALM-25651 Ambient Humidity Unacceptable

Description
This alarm is reported when the ambient humidity is too high or too low.
Parameters
53 de 526 13/11/2012 9:15

Minor The equipment may be damaged, and the life span may be shortened.
System Actions
None
Possible Causes
The ambient humidity in the equipment room is abnormal.
The cable connection is faulty.

The humidity sensor malfunctions.
Procedure
1. Check the threshold setting for the ambient humidity alarm of the monitoring device on the M2000.
a. Run the MML command LST EMU to query the threshold of ambient humidity alarm.
Check whether the alarm threshold is proper according to the configuration planning.
2. Check the ambient humidity of the equipment room on site.
a. Check whether the humidity in the equipment room is normal.

Y => The humidity in the equipment room is within the normal range. Go to step 3.
N => The humidity in the equipment room is out of range. Go to sub-step b.
b. Check the air conditioner in the equipment room, and clear the fault if any.
3. Check the cable connection between the humidity sensor and the monitoring device on site.
54 de 526 13/11/2012 9:15

b.

4. Replace the humidity sensor on site.


1.1.21 ALM-25652 Cabinet Temperature Unacceptable

Description
This alarm is reported when the cabinet temperature is too high or too low.
Parameters
disrupted.
System Actions
55 de 526 13/11/2012 9:15

None
Possible Causes
The ambient temperature is out of range.
The heat dissipation system of the cabinet is faulty.

Procedure

25656 Cabinet Air Inlet Temperature Unacceptable
25673 Fan Stalled
2. Check the threshold setting for the cabinet temperature alarm on the M2000.
a. Run the MML command LST TCU to query the threshold of cabinet temperature alarm.
b. Run the MML command MOD TCU to set the alarm threshold based on the
b.
56 de 526 13/11/2012 9:15


4. Replace the temperature sensor of the cabinet on site.


1.1.22 ALM-25653 Cabinet Humidity Unacceptable

Description
This alarm is reported when the cabinet humidity is too high or too low.
Parameters
Minor The normal operation of the device is affected, and the services may be disrupted.
System Actions
None
Possible Causes
The ambient humidity is out of range.


57 de 526 13/11/2012 9:15

Procedure

25651 Ambient Humidity Unacceptable
25673 Fan Stalled

2. Check the threshold setting for the cabinet humidity alarm on the M2000.
a. Run the MML command LST EMU to query the threshold of cabinet humidity alarm.
3. Check the cable connection between the humidity sensor and the monitoring device on site.
b.
4. Replace the cabinet humidity sensor on site.

58 de 526 13/11/2012 9:15


1.1.23 ALM-25654 Battery Temperature Unacceptable

Description
This alarm is reported when the battery temperature is too high or too low.
Parameters
Major/Minor The performance of batteries is degraded and the life span is shortened.
System Actions
None
Possible Causes
The cabinet temperature is out of range.
The heater in the battery cabin is faulty.

The cable connection between the battery temperature sensor and the monitoring device is faulty.
The battery temperature sensor is faulty.

Procedure

25673 Fan Stalled
25632 Battery Cabin Heater Fault
59 de 526 13/11/2012 9:15


2. Check the threshold setting for the battery temperature alarm of the monitoring device on the
M2000.
a. Run the MML command LST BATTERY to query the threshold of cabinet temperature
alarm. Check whether the alarm threshold is proper according to the configuration
planning.
b. Run the MML command MOD BATTERY to set the alarm threshold based on the
3. Check the cable connection between the battery temperature sensor and the monitoring device on
site.
b.

4. Replace the battery temperature sensor on site.


1.1.24 ALM-25655 Cabinet Air Outlet Temperature Unacceptable
60 de 526 13/11/2012 9:15

Description
This alarm is reported when the temperature at the air outlet of the cabinet is too high or too low, or the
temperature difference between the air outlet and the air inlet is excessive.
Parameters
Parameter
Specific Specific Problem of the alarm(Too High, Too Low, Cabinet Air Inlet-to-Outlet Temperature
Problem Difference Too Large)
disrupted.
System Actions
None
Possible Causes
The cabinet temperature is out of range.
The air filter is blocked.

Procedure

25673 Fan Stalled
61 de 526 13/11/2012 9:15


a. Locate the cause of the alarm according to the alarm detailed information on the
M2000.
If "Specific Problem" is "Cabinet Air Inlet-to-Outlet Temperature Difference Too Large",
go to step 7.
If "Specific Problem" is "Too High" or "Too Low", go to step 3.
3. Check the threshold setting for the cabinet air outlet temperature alarm on the M2000.
a. Run the MML command LST EMU(EMU)/LST PMU(PMU)/LST TCU(TCU) to query

the threshold of cabinet air outlet temperature alarm. Check whether the alarm
threshold is proper according to the configuration plan.
b. Run the MML command MOD EMU(EMU)/MOD PMU(PMU)/MOD TCU(TCU) to set

the alarm threshold based on the configuration plan.
b.

5. Replace the temperature sensor of the cabinet air outlet on site.


62 de 526 13/11/2012 9:15


7. Check the air filter on site.
a. Check whether the air inlet or air outlet of the cabinet is blocked by an foreign object.
Y => The air inlet or air outlet is blocked by an foreign object. Go to sub-step b.
N => There is no foreign object at the air inlet or air outlet. Go to sub-step c.
b. Remove the foreign object from the the air inlet or air outlet.
c. Replace the air filter by referring to the user manual of the product.
1.1.25 ALM-25656 Cabinet Air Inlet Temperature Unacceptable

Description
This alarm is reported when the temperature at the air inlet of the cabinet is too high or too low.
Parameters
Minor The normal operation of the equipment is affected, and the services may be
disrupted.
System Actions
None
Possible Causes
The heat dissipation system of the cabinet malfunctions.


63 de 526 13/11/2012 9:15

Procedure

25673 Fan Stalled

2. Check the cabinet temperature on the M2000.

Y => The correlated alarm exists. The cabinet temperature is out of range. Go to step
3.
N => The correlated alarm does not exist. The cabinet temperature is within the normal
range. Go to step 4.
3. Clear the cabinet temperature alarm.
a. Locate the cause of the alarm according to the alarm detailed information on the
M2000.
If "Specific Problem" is "Too High", go to sub-step b.
If "Specific Problem" is "Too Low", go to sub-step c.
b. Replace the fan box on site.

c. (Skip this sub-step and go to step 4 if no heater is configured) Check whether the
heater is working on site.
Y => The heater is working. Go to step 4.
N => The heater is not working. Go to sub-step d.
d. Replace the heater on site.

a. Check whether the cable between the temperature sensor and the monitoring device is
64 de 526 13/11/2012 9:15


b.

5. Replace the temperature sensor of the cabinet air inlet on site.


1.1.26 ALM-25657 TEC Cooler Fault

Description
This alarm is reported when the air conditional of the Thermal Energy Converter (TEC) malfunctions.
Parameters
Major The base station works properly. However, the temperature of the batteries may be
too high, thus affecting the safe operation of the batteries.
System Actions
None
Possible Causes
The cable connection of the TEC is faulty.
The TEC module group is faulty.
65 de 526 13/11/2012 9:15

Procedure
1. Reset the corresponding monitoring device on the M2000.
a. Run the MML command RST BRD to reset the monitoring device where the faulty TEC
is located.
2. Check the cable connection between the TEC and the monitoring device on site.
a. Check whether the cable between the TEC and the monitoring device is functional and
b.

3. Check the TEC on site.
a. Arrange the cables of the TEC, and remove foreign objects around the fan. Then,
reinstall the cables and power on the TEC.
b. Replace the TEC module.


1.1.27 ALM-25670 Water Alarm

Description
This alarm is reported when the equipment room or the cabinet is waterlogged.
Parameters
66 de 526 13/11/2012 9:15

Critical The device is damaged and the services may be disrupted.
System Actions
None
Possible Causes
The alarm disable function of the water alarm is configured incorrectly.
The equipment room or the cabinet is waterlogged.
The cable connection between the water sensor and the monitoring device is faulty.
The water sensor is faulty.
Procedure
1. (Skip this step and go to step 2 if the board type is not EMU or PMU.) Check the configuration of
the water sensor on the M2000.
a. Run the MML command LST EMU(EMU)/LST PMU(PMU) on the M2000 to check
whether the status of the water alarm is consistent with the configuration plan.
Y => The status of the water alarm is consistent with the configuration plan. Go to step
2.
N => The status of the water alarm is inconsistent with the configuration plan. Go to
sub-step b.
b. Run the MML command MOD EMU(EMU)/MOD PMU(PMU) on the M2000 to disable
the water alarm.
2. Check the equipment room or the cabinet on site.
a. Check whether the equipment room or the cabinet is waterlogged on site. Remove the
water, and then waterproof the equipment room and the cabinet.
3. Check the cable connection between the sensor and the monitoring device on site.
67 de 526 13/11/2012 9:15

b.

4. Replace the water sensor on site.


1.1.28 ALM-25671 Smoke Alarm

Description
This alarm is reported when high density smoke is detected in the equipment room.
Parameters
Critical The equipment may be burnt out.
System Actions
None
Possible Causes
The alarm disable function of the smoke alarm is configured incorrectly.
68 de 526 13/11/2012 9:15

The equipment room or the equipment is on fire.
The cable connection between the smoke sensor and the monitoring device is faulty.
The smoke sensor is faulty.
Procedure
1. (Skip this step and go to step 2 if the board type is not EMU or PMU.) Check the configuration of
the smoke sensor on the M2000.
whether the status of the smoke alarm is consistent with the configuration plan.
Y => The status of the smoke alarm is consistent with the configuration plan. Go to
step 2.
N => The status of the smoke alarm is inconsistent with the configuration plan. Go to
sub-step b.
the smoke alarm. Then, run the MML command CLR PMUALM(PMU)/CLR
EMUALM(EMU) to clear the smoke alarm.
2. Check the equipment room or the equipment.
a. Check whether the equipment room or the equipment is on fire on site. Extinguish the
fire if any. If there is no fire, go to step 3.
After the fire is extinguished, run the MML command CLR PMUALM(PMU)/CLR
EMUALM(EMU) to clear the smoke alarm on the M2000.
a. Check whether the cable between the correlated sensor and the monitoring device is
b.
b. Reconnect or replace the cable. Then, run the MML command CLR
PMUALM(PMU)/CLR EMUALM(EMU) on the M2000 to clear the smoke alarm. Wait
for two minutes.
4. Replace the smoke sensor on site.
a. Replace the sensor. Then, run the MML command CLR PMUALM(PMU)/CLR
69 de 526 13/11/2012 9:15

EMUALM(EMU) on the M2000 to clear the smoke alarm. Wait for two minutes.
a. Replace the monitoring device. Then, run the MML command CLR
PMUALM(PMU)/CLR EMUALM(EMU) on the M2000 to clear the smoke alarm. Wait
for two minutes.
1.1.29 ALM-25672 Burglar Alarm

Description
This alarm is reported when a person enters the equipment room or the door of the cabinet is open.
Parameters
Specific Problem Specific Problem of the alarm(Door Status Alarm, Infrared Alarm)
Critical The equipment may be damaged or stolen.
System Actions
None
Possible Causes
The function of the door status or infrared alarms is configured incorrectly.
The door of the equipment room or the cabinet is open.
The cable connection between the sensor and the monitoring device is faulty.

Procedure
1. (Skip this step and go to step 2 if the board type is not EMU or PMU.) Check the configuration on
the M2000.
70 de 526 13/11/2012 9:15

whether the status of the door status alarm or infrared alarm is consistent with the
configuration plan.
Y => The status of the door status alarm or infrared alarm is consistent with the
configuration plan. Go to step 2.
N => The status of the door status alarm or infrared alarm is inconsistent with the
configuration plan. Go to sub-step b.
the door status alarm or infrared alarm.
2. Check the door of the equipment room or the cabinet on site.
a. Check whether the door of the equipment room or the cabinet is open on site.
Y => The door is open. Go to sub-step b.
N => The door is closed. Go to step 3.
b. Close the door.

c. Check whether the parameter "Board Type" is "EMU" according to the alarm detailed
information.
Y => The board type is EMU. Go to sub-step d.
N => The board type is not EMU. Go to step 3.
d. Run the MML command CLR EMUALM on the M2000 to clear the burglar alarm. Wait
for two minutes.
a. Check whether the cable between the correlated sensor and the monitoring device is
b.
c. Based on the alarm detailed information, check whether "Board Type" is "EMU".
Y => The board type is EMU. Go to sub-step d.
71 de 526 13/11/2012 9:15

d. Run the MML command CLR EMUALM on the M2000 to clear the burglar alarm. Wait
for two minutes.
4. Replace the door status sensor or infrared sensor on site.

b. Based on the alarm detailed information, check whether "Board Type" is "EMU".
Y => The board type is EMU. Go to sub-step c.
c. Run the MML command CLR EMUALM on the M2000 to clear the burglar alarm. Wait
for two minutes.

b. Based on the alarm detailed information, check whether "Board Type" is "EMU".
Y => The board type is EMU. Go to sub-step c.
N => The board type is not EMU. Contact Huawei Customer Service Center.
c. Run the MML command CLR EMUALM on the M2000 to clear the burglar alarm. Wait
for two minutes.
1.1.30 ALM-25673 Fan Stalled

Description
This alarm is reported when a fan is faulty.
Parameters
Parameter
72 de 526 13/11/2012 9:15

Fan No. Faulty fan number (Inner air circulation fan, Outer air circulation fan, Main fan, Extension fan
group 1)
Major The normal operation of the equipment is affected, and the services may be
disrupted.
System Actions
None
Possible Causes
The cable connection of the fan is faulty.

The fan is blocked.
The fan is worn-out.
The fan speed cannot be controlled.
Procedure
1. Reset the corresponding monitoring device on the M2000.
a. Run the MML command RST BRD on the M2000 to reset the monitoring device where
the fan is located.
2. (For the NodeB, skip this step and go to step 3.) Check the cable connection between the fan and
the monitoring device on site.
a. Check whether the cable between the fan and the monitoring device is functional and
b.

3. Check the fan module on site.
73 de 526 13/11/2012 9:15

a. Remove the fan subrack. Eliminate foreign objects around the fan, and then reinstall the
fan subrack.
b. Replace the fan box.


1.1.31 ALM-25695 Diesel Generator Fault

Description
This alarm is reported when the diesel generator cannot supply the power because the diesel generator startup
fails or an error occurs during the operation of the diesel generator.
Parameters
Major There is no AC power supply. The system may be powered off.
System Actions
None
Possible Causes
The alarm cable connection between the diesel generator and the monitoring device is faulty.
The diesel generator is faulty.

Procedure
1. Check the alarm cable connection between the diesel generator and the monitoring device on site.
74 de 526 13/11/2012 9:15

a. Check whether the alarm cable between the diesel generator and the monitoring device
b.
b. Reconnect or replace the alarm cable.

2. Check the diesel generator on site.
a. Check for alarms related to diesel generator on the control panel of the diesel
generator on site.
Y => The diesel generator is faulty. Go to sub-step b.
N => The diesel generator is functional. Go to step 3.
b. Contact the relevant professionals to repair the diesel generator.


1.1.32 ALM-25696 Diesel Generator Low Fuel

Description
This alarm is reported when the fuel in the diesel generator is insufficient.
Parameters
Major There is no AC power supply. The system may be powered off.
System Actions
75 de 526 13/11/2012 9:15

None
Possible Causes
The fuel in the diesel generator is insufficient.
The alarm cable connection is faulty.
Procedure
1. Check the fuel in the diesel generator on site.
a. Check whether the fuel in the diesel generator is sufficient.

Y => The fuel is sufficient. Go to step 2.
N => The fuel is insufficient. Go to sub-step b.
b. Shut down the diesel generator, and add fuel to a proper level.
2. Check the alarm cable connection between the diesel generator and the monitoring device on site.
a. Check whether the alarm cable between the diesel generator that reports the alarm and
the monitoring device is functional and the connection is correct.
b.
b. Reconnect or replace the alarm cable.

3. Check the sensor on site.
a. Check whether the alarm output port of the sensor for the diesel generator is functional.
Y => The alarm output port of the sensor is functional. Go to step 4.
N => The alarm output port of the sensor malfunctions. Go to sub-step b.
b. Replace the sensor.
4. Replace the corresponding monitoring device on site.

76 de 526 13/11/2012 9:15

1.1.33 ALM-25697 Diesel Generator Startup Failure

Description
This alarm is reported when the diesel generator fails to be started.
Parameters
Major The diesel generator cannot provide the power supply.
System Actions
None
Possible Causes
The diesel generator is faulty.
The fuel in the diesel generator is insufficient.
The diesel generator is shut down.
The power cable that transmits the startup signals of the diesel generator is faulty.
Procedure

25695 Diesel Generator Fault
25696 Diesel Generator Low Fuel

2. Check the operating status of the diesel generator on site.
a. Check whether the controller of the diesel generator works in auto mode.
Y => The diesel generator is in auto mode. Go to step 3.
77 de 526 13/11/2012 9:15

N => The diesel generator is not in auto mode. Go to sub-step b.
b. Changes the operating status of the diesel generator to auto mode.

3. Check the power cable that transmits the startup signals of the diesel generator on site.
a. Check whether the power cable that transmits the startup signals of the diesel
generator is functional and the connection is correct.
b.


1.1.34 ALM-25710 Loss of Solar Array

Description
This alarm is reported when the loop of the solar array is broken or the modules of the solar array are lost.
Parameters
Array No. Solar array No. If the array No. is 0, it indicates that the array is unknown.
Major The solar array cannot provide the power supply to the system.
System Actions
None
78 de 526 13/11/2012 9:15

Possible Causes
The solar array cannot receive any sunshine for a long period.
The solar array is lost.
The loop of the solar array is broken, or the Miniature Circuit Breaker (MCB) is switched off.
The solar array is shielded from sunshine.
Procedure
1. Check the weather.
a. Check whether the weather has remained cloudy and rainy for at least four days.
Y => It has been cloudy and rainy for more than four days. In this case, ignore the
alarm. No further action is required.
N => It has not been cloudy or rainy. Go to step 2.
2. Check the solar array on site.
a. Check whether the solar array is in position on site.

Y => The solar array is in position. Go to step 3.
N => The solar array in not in position. Go to sub-step b.
b. Install the solar array at the required position. For details about the installation, see the
Power2000 Quick Installation Guide.
3. Check the MCB of the solar array on site.
a. Check whether the MCBs of all solar arrays are switched on.
Y => The MCBs are switched on. Go to step 4.
N => The MCBs are switched off. Go to sub-step b.
b. Switch on the MCBs.

4. Check the solar array on site.
a. Check whether there is any shield around the solar array on site.
Y => There is a shield around the solar array. Go to sub-step b.
N => There is no shield around the solar array. Go to step 5.
b. Remove the shield.
79 de 526 13/11/2012 9:15


1.1.35 ALM-25711 Solar Array Fault

Description
This alarm is reported when the open-circuit voltage/current or the operating voltage/current of the solar array is
out of range.
Parameters
Array No. Solar array No. If the array No. is 0, it indicates that the array is unknown.
Major The solar array cannot provide the power supply for the system.
System Actions
None
Possible Causes
The solar array is lost.

The connection mode of the solar array is incorrect.
The PSU is short-circuited or disconnected.

Procedure

25710 Loss of Solar Array

80 de 526 13/11/2012 9:15


2. Check the connection mode of the solar array on site.
a. Check whether the connection mode of the solar array is consistent with the site
planning. For the detailed cable connections, see the Power2000 Quick Installation
Guide.
Y => The connection mode is consistent with that in the site planning. Go to step 3.
N => The connection mode is inconsistent with that in the site planning. Go to sub-step
b.
b. Set the connection mode of the solar array according to the site planning.
3. Check the PSU on site.
a. Check whether the MOS transistor of the PSU is damaged on site.

Y => The MOS transistor is damaged. Go to sub-step d.
N => The MOS transistor is functional. Go to sub-step b.
b. On the control panel of the solar array, set the state of solar array to OFF. Then, use a
clamp meter to check whether the open-circuit current of the PSU is larger than 2 A.
Y => The open-circuit current is larger than 2 A. Go to sub-step d.
N => The open-circuit current is 0. Go to sub-step c.
c. On the control panel of the solar array, set the state of solar array to ON. Then, use a
multimeter to check whether the operating voltage of the PSU is larger than 5 V DC.
Y => The operating voltage is larger than 5 V DC. Go to sub-step d.
N => The operating voltage is within the normal range. Go to step 4.
d. Use a screwdriver to remove the PSU. Then, install a new PSU.


1.1.36 ALM-25713 Solar Controller Temperature Unacceptable

Description
This alarm is reported when the internal temperature of the solar controller is too high.
Parameters
81 de 526 13/11/2012 9:15

Minor The normal operation of the equipment is affected, and the solar array may fail to
provide any output power.
System Actions
None
Possible Causes

The internal temperature of the solar controller is too high.
The cables of the temperature sensor are faulty.

The temperature sensor is faulty.
Procedure

2. (For the NodeB, skip this step and go to step 3.) Check the threshold setting for the solar controller
temperature alarm on the M2000.
a. Run the MML command LST PMU to query the threshold of the solar controller
temperature alarm. Check whether the alarm threshold is proper according to the
82 de 526 13/11/2012 9:15

3. Check the internal temperature of the solar controller on site.
a. Use a thermometer to measure whether the internal temperature of the solar controller
is higher than the threshold of the solar controller temperature alarm.
Y => The temperature is higher than the threshold. Go to sub-step b.
N => The temperature is not higher than the threshold. Go to step 4.
b. The heat dissipation inside the solar controller fails. If the ventilation loop is blocked,
remove the foreign objects and wait for 20 minutes.
a. Check whether the cable between the sensor and the monitoring device is functional
and the connection is correct.
b.

5. Replace the temperature sensor on site.


1.1.37 ALM-25719 CCU Topology and Configuration Mismatch

Description
83 de 526 13/11/2012 9:15

This alarm is reported when the user-configured inter-CCU topology is inconsistent with the actual inter-CCU
topology.
Parameters
Major CCUs cannot share control information. Device monitoring may malfunction.
System Actions
None
Possible Causes
Data configuration of a CCU is incorrect.
The inter-CCU cables are incorrectly connected.
Procedure
a. Check for the correlated alarm of the inter-CCU topology on the M2000:
25600 Monitoring Device Maintenance Link Failure
25601 Monitoring Device Hardware Fault
2. Check the configuration of inter-CCU topology on the M2000.
a. Run the MML command LST CCU to query the inter-CCU topology.
Check whether the configured networking mode and the port connection conform to the
site plan.
Y => The configuration conforms to the site plan. Go to step 3.
N => The configuration does not conform to the site plan. Go to sub-step b.
b. Run the MML command MOD CCU to modify the inter-CCU topology.
Ensure that the configuration conforms to the site plan.
84 de 526 13/11/2012 9:15

3. Check the inter-CCU topology on site.
a. Check whether the inter-CCU topology conforms to the site plan on site.
Y => The inter-CCU topology conforms to the site plan. Contact Huawei Customer
Service Center.
N => The inter-CCU topology does not conform to the site plan. Go to sub-step b.
b. Reconnect the inter-CCU cables. Ensure that the inter-CCU topology conforms to the
site plan.
1.1.38 ALM-25720 Inter-CCU Port Connection Error

Description
An inter-CCU port can be an FE_L port type or an FE_R port type. Inter-CCU ports of the same type cannot be
connected, and a ring network is not allowed if inter-CCU ports are connected. This alarm is reported when
inter-CCU ports of the same type are connected, or a ring network is set up in the case of an inter-CCU port
connection.
Parameters
Parameter
Specific Problem Fault type (FE_L connected to FE_L, FE_R connected to FE_R, Ring network, Other
network)
Major CCUs cannot share control information. Device monitoring may malfunction.
System Actions
None
Possible Causes
Inter-CCU ports of the same type are connected.
A ring network is set up after inter-CCU ports are connected.

An inter-CCU port is connected to a non-inter-CCU port.
Procedure
1. Locate the cause of alarm on the M2000.
85 de 526 13/11/2012 9:15

a. Locate the cause of alarm based on the alarm information.

If "Specific Problem" is "FE_L connected to FE_L" or "FE_R connected to FE_R", go to
step 2.
If "Specific Problem" is "Ring network", go to step 3.
If "Specific Problem" is "Other network", go to step 4.
2. Check for the connection of inter-CCU ports of the same type on site.
a. Based on alarm parameters, locate the faulty inter-CCU port and the connected cable.
Check whether the faulty inter-CCU port is connected to an inter-CCU port of the same
type.
Y => The inter-CCU port is connected to an inter-CCU port of the same type. Go to
substep b.
N => The inter-CCU port is connected to an inter-CCU port of a different type. Contact
Huawei Customer Service Center.
b. Reconnect the inter-CCU cables based on the engineering plan.

3. Check for a ring topology of inter-CCU connection on site.
Check whether a ring topology of inter-CCU connection exists on the inter-CCU port.
Y => A ring topology of inter-CCU connection exists. Go to sub-step b.
N => A ring topology of inter-CCU connection does not exist. Contact Huawei Customer
Service Center.
4. Check for connection between an inter-CCU port and a non-inter-CCU port onsite.
Check whether the faulty inter-CCU port is connected to a non-inter-CCU port.
Y => An inter-CCU port is connected to a non-inter-CCU port. Go to substep b.
N => An inter-CCU port is not connected to a non-inter-CCU port. Contact Huawei
Customer Service Center.

1.1.39 ALM-25721 CCU-BBU Communication Failure

Description
In a multi-mode base station, this alarm is reported when communication fails between a CCU and a BBU that
86 de 526 13/11/2012 9:15

does not control the CCU.
Parameters
Port No. Port number, reserverd parameter
Radio Access Radio access technology (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Technology Unknown)
Minor The status of monitoring devices becomes unknown.
System Actions
None
Possible Causes
The BBU is not powered on or fails to be detected.
The cable connections between the BBU and the monitoring device are incorrect.
The cable connections between the BBU and the monitoring device are loose, worn-out, or damaged.
The BBU is faulty.
Procedure
a. Check for the correlated alarm of the faulty BBU on the M2000:
26101 Inter-Board CANBUS Communication Failure
26200 Board Hardware Fault
26204 Board Not In Position
26214 Board Powered Off
26216 Board Not Securely Installed

2. Check the site configuration on the M2000.
a. Run the MML command LST CCU to check whether the cabinet/subrack/slot of the
87 de 526 13/11/2012 9:15

BBU is consistent with the configuration plan.

Y => The information is consistent. Go to step 2.
N => The information is inconsistent. Go to sub-step b.

FMU(FMU) to remove the faulty monitoring device.
Run the MML command ADD PMU(PMU)/ADD TCU(TCU)/ADD EMU(EMU)/ADD
FMU(FMU) to add the monitoring device according to the configuration plan.
3. Check the BBU status on site.
a. Check whether the BBU is properly installed and powered on. When the power switch is
set to ON and the RUN LED is lighted, it indicates that the BBU is powered on.
Y => The BBU is properly installed and powered on. Go to step 4.
N => The BBU is not properly installed or not powered on. Go to sub-step b.
b. Install the required board properly into the BBU and power it on.
4. Check the cable connections of the monitoring device on site.
a. Check whether the cable connections are proper between the monitoring device and the
BBU based on the installation guide.
Y => The cable connections are proper. Go to sub-step c.
N => The cable connections are improper. Go to sub-step b.
b. Reconnect the cables between the monitoring device and the BBU.
c. Check whether the cables between the monitoring device and the BBU are functional
and the connections are correct.
Y => The cables are functional and the connections are correct. Go to step 5.
N => The cables are loose, worn-out, damaged, or incorrectly connected. Go to
sub-step d.
d. Reconnect or replace the cables.

5. Replace the faulty part in the BBU on site.
a. Note: If there is only one UPEU configured in the BBU or there are two UPEUs
configured in the high-power-consumption BBU, replacing the UPEU interrupts all the
ongoing services of the base station. Therefore, perform the replacement in low-traffic
88 de 526 13/11/2012 9:15

hours.
Replace the BBU environment interface unit on site.
b. Note: Replacing the main control board interrupts all the ongoing services of the base
station. Therefore, perform this replacement in low-traffic hours. The base station
software upgrade may be required during board replacement, so the correct software
version must be ready for use in advance.
Replace the main control board on site.
1.1.40 ALM-25800 E1/T1 Loss of Signal

Description
This alarm is reported when Loss of Signal (LOS) is detected on the E1/T1 RX port.
Parameters
Cabinet No. Cabinet number of the faulty board
Subrack No. Subrack number of the faulty board
Slot No. Slot number of the faulty board
Port No. Port number of the E1/T1
Major The ongoing services carried on the E1/T1 link are disrupted.
System Actions
The system disables the associated E1/T1 link.
Possible Causes
The E1/T1 link is incorrectly configured.

The E1/T1 transmission link is faulty.
The local device is faulty.

The E1/T1 transmission trunk is faulty.
The peer device is faulty.
Procedure
1. Check the E1/T1 configuration on site.
89 de 526 13/11/2012 9:15

a. Check whether the E1/T1 configuration is correct.

Y => The E1/T1 configuration is correct. Go to step 2.
N => The E1/T1 configuration is incorrect. Go to sub-step b.
b. Configure the E1/T1 link properly.

2. Check the E1/T1 transmission link on site.
a. Check whether the E1/T1 transmission link is normal. Check for the damaged cable,
loose connector, or bent/broken pin on the connector.
Y => The E1/T1 transmission link is normal. Go to step 3.
N => The E1/T1 transmission link is faulty. Go to sub-step b.
b. Replace or reconnect the E1/T1 cables.

3. Check the local E1/T1 device on site.
a. Check whether the local E1/T1 device is functional.

Y => The local E1/T1 device is functional. Go to step 6.
N => The local E1/T1 device is faulty. Go to step 4.
4. Reset the faulty board on the M2000 or on site.
a. Run the MML command RST BRD to reset the faulty board.
5. Replace the faulty board on site.
a. Replace the board.

N => The alarm is not cleared. Reinstall the original board. Go to step 6.
6. Check the E1/T1 transmission trunk between the local device and the peer device on site.
a. Contact the transmission engineer of the customer to troubleshoot the fault on the
transmission trunk.
7. Check the peer device.
a. Troubleshoot the fault on the peer device.
90 de 526 13/11/2012 9:15


1.1.41 ALM-25801 E1/T1 Alarm Indication Signal

Description
This alarm is reported when the all 1s signal (Alarm Indication Signal, abbreviated as AIS) is detected on the
E1/T1 RX port.
Parameters
System Actions
Possible Causes


Procedure

91 de 526 13/11/2012 9:15






1.1.42 ALM-25802 E1/T1 Remote Alarm Indication Signal

Description
The peer E1/T1 device sends Remote Alarm Indication (RAI) to the local E1/T1 device when the peer E1/T1
device cannot detect the frame synchronization signals correctly. This alarm is reported when Remote Alarm
Indication (RAI) is detected on the E1/T1 RX port.
Parameters
92 de 526 13/11/2012 9:15

Minor The ongoing services carried on the E1/T1 link are disrupted.
System Actions
Possible Causes
The E1/T1 link is configured incorrectly.

Procedure


93 de 526 13/11/2012 9:15


a. Check whether the E1/T1 transmission trunk is functional.

Y => The E1/T1 transmission trunk is functional. Go to step 7.
N => The E1/T1 transmission trunk is faulty. Go to sub-step b.
b. Contact the transmission engineer of the customer to troubleshoot the fault on the
transmission trunk.

1.1.43 ALM-25803 E1/T1 Loss of Frame Alignment

Description
This alarm is reported when Loss of Frame Alignment (LFA) is detected on the E1/T1 RX port.
Parameters
94 de 526 13/11/2012 9:15

System Actions
Possible Causes

Procedure




95 de 526 13/11/2012 9:15



transmission trunk.

1.1.44 ALM-25804 E1/T1 Loss of Multiframe Alignment

Description
This alarm is reported when Loss of Multiframe Alignment (LMFA) is detected on the E1/T1 RX port.
Parameters
Minor The ongoing services carried on the E1/T1 link are disrupted.
System Actions
Possible Causes
96 de 526 13/11/2012 9:15

Procedure





97 de 526 13/11/2012 9:15


transmission trunk.

1.1.45 ALM-25805 E1/T1 Excessive Slip Frames

Description
This alarm is reported when the number of slip frames in one hour on the E1/T1 link exceeds the preset
threshold.
Parameters
Minor The quality of services carried on the E1/T1 link decreases. The ongoing services
may be disrupted.
System Actions
None
Possible Causes
The local clock of the NE malfunctions.
The E1/T1 configuration is incorrect.

The E1/T1 grounding does not meet the grounding requirements.
The performance of the E1/T1 transmission link is poor.
Procedure
1. Check the local clock of the NE on the M2000.
98 de 526 13/11/2012 9:15


26262 External Clock Reference Problem
b. Clear the correlated alarm with recommended actions. Then, wait for ten minutes.


4. Check the E1/T1 grounding on site.
a. Check whether the E1/T1 grounding meets the requirements.

Y => The E1/T1 grounding meets the requirements. Go to step 5.
N => The E1/T1 grounding does not meet the requirements. Go to sub-step b.
b. Ground the E1/T1 transmission cables properly and then wait for 15 minutes.
a. Check whether the E1/T1 transmission link is functional. Check for the damaged cable,
Y => The E1/T1 transmission link is functional. Go to step 6.
N => The E1/T1 transmission link malfunctions. Go to sub-step b.
99 de 526 13/11/2012 9:15




transmission trunk.

1.1.46 ALM-25806 E1/T1 Excessive Bit Error Rate

Description
This alarm is reported when the bit error rate (BER) on the E1/T1 link exceeds the preset threshold (1E-5 by
default, user-definable).
Parameters
100 de 526 13/11/2012 9:15

Minor The quality of services carried on the E1/T1 link decreases. The ongoing services
may be disrupted.
System Actions
None
Possible Causes
The local clock of the NE malfunctions.

The E1/T1 configuration is incorrect.
The E1/T1 grounding does not meet the grounding requirements.
The performance of the E1/T1 transmission link is poor.
Procedure
1. Check the local clock of the NE on the M2000.

b. Clear the correlated alarm with recommended actions. Then, wait for 15 minutes.
2. Check that the local E1/T1 configuration is consistent with the peer E1/T1 configuration on the
M2000.
a. Run the MML command DSP E1T1 to check whether the line code of the faulty E1/T1
is consistent with that of the peer E1/T1.
Y => The line code of the faulty E1/T1 is consistent with that of the peer E1/T1. Go to
step 3.
N => The line code of the faulty E1/T1 is inconsistent with that of the peer E1/T1. Go to
sub-step b.
b. Run the MML command SET E1T1 to change the line code of the local E1/T1. Ensure
that the line code of the local E1/T1 is consistent with that of the peer E1/T1.
3. Check the E1/T1 grounding on site.
a. Check whether the E1/T1 grounding meets the requirements.

Y => The E1/T1 grounding meets the requirements. Go to step 4.
N => The E1/T1 grounding does not meet the requirements. Go to sub-step b.
b. Ground the E1/T1 transmission cables properly and then wait for 15 minutes.
101 de 526 13/11/2012 9:15


a. Check whether the E1/T1 transmission link is functional. Check for the damaged cable,
Y => The E1/T1 transmission link is functional. Contact Huawei Customer Service
Center.
N => The E1/T1 transmission link malfunctions. Go to sub-step b.

1.1.47 ALM-25807 E1/T1 Loopback

Description
This alarm is reported when the user sets the local or remote loopback on the E1/T1 link through the MML
command, or when the E1/T1 physical loopback is performed.
Parameters
Loopback Type Loopback type (Remote Loopback, Local Loopback, Physical Loopback)
Minor The E1/T1 link is unusable.
System Actions
None
Possible Causes
The user sets the local or remote loopback on the E1/T1 link.
The E1/T1 physical loopback is performed.
Procedure
1. Check the E1/T1 loopback mode on the M2000.
a. Check the E1/T1 loopback mode according to the alarm detailed information.
102 de 526 13/11/2012 9:15

If "Loopback Mode" is "Remote Loopback" or "Local Loopback", Go to step 2.

If "Loopback Mode" is "Physical Loopback", Go to step 3.
2. Cancel the E1/T1 loopback on the M2000.
a. Run the MML command DSP E1T1 to check whether the faulty E1/T1 link is in remote
loopback or local loopback mode.
Y => The E1/T1 loopback mode is "Remote Loopback" or "Local Loopback". Go to
sub-step b.
N => The E1/T1 loopback mode is not "Remote Loopback" or "Local Loopback". Go to
step 3.
b. Run the MML command SET E1T1LOP to cancel the E1/T1 loopback.
3. Cancel the E1/T1 physical loopback on site.
a. Check whether the E1/T1 physical loopback exists.

Y => The E1/T1 physical loopback exists. Go to sub-step b.
N => The E1/T1 physical loopback does not exist. Go to step 4.
b. Reconnect the E1/T1 cable to cancel the physical loopback.

4. Cancel the remote loopback of the peer device.
a. Check whether the remote loopback exists on the peer device of the E1/T1 link.
Y => The remote loopback exists. Go to sub-step b.
N => The remote loopback does not exist. Contact Huawei Customer Service Center.
b. Cancel the remote loopback of the peer device.
1.1.48 ALM-25820 Fractional ATM Link Loss of Cell Delineation

Description
This alarm is reported when Loss of Cell Delineation (LCD) occurs on the Fractional ATM link.
Parameters
103 de 526 13/11/2012 9:15

Link No. Link number of the fractional ATM
Major The ongoing services carried on the Fractional ATM link are disrupted.
System Actions
The system disables the associated Fractional ATM link.
Possible Causes
The E1/T1 link is faulty.

The phase-locked loop of the receive clock is out of synchronization.
The configuration of the Fractional ATM link mismatches between the local end and the peer end.
Procedure
1. Check the E1/T1 link and local clock on the M2000.
a. Check for the correlated alarm on the E1/T1 link that bears the Fractional ATM link on
the M2000:
E1/T1-Correlated Alarms.
Y => The correlated alarm exists. Go to sub-step c.
N => The correlated alarm does not exist. Go to sub-step b.
b. Check for the correlated alarm on the M2000:

c. Clear the correlated alarm with recommended actions.

2. Check the Fractional ATM link configuration on the M2000.
a. Run the MML command LST FRAATM to query the local Fractional ATM link
configuration.
b. Query the peer Fractional ATM link configuration. Check whether the local configuration
matches the peer configuration, including the number of occupied timeslots and timeslot
numbering.
Y => The local configuration matches the peer configuration. Go to step 3.
N => The local configuration does not match the peer configuration. Go to sub-step c.
c. Run the MML command RMV FRAATM,ADD FRAATM to change the local Fractional
ATM link configuration. Ensure that the local Fractional ATM link configuration matches
the peer configuration.
104 de 526 13/11/2012 9:15


3. Reset the faulty board on the M2000.
1.1.49 ALM-25821 IMA/ATM Link Loss of Cell Delineation

Description
This alarm is reported when Loss of Cell Delineation (LCD) occurs on the IMA/UNI link.
Parameters
Link No. Link number of the IMA/UNI
Major In the case of the User Network Interface (UNI) link, the ongoing services carried on
the link are disrupted.
In the case of the Inverse Multiplexing over ATM (IMA) link, the bandwidth of the
relevant IMA link group is reduced. If the IMA link is the only link in the IMA group,
the ongoing services carried on the IMA group are disrupted.
System Actions
The system disables the associated IMA/UNI link.
Possible Causes

The configuration of the IMA link group/UNI link is incorrect.
The local IMA is faulty.
The peer IMA is faulty.
Procedure
1. Check the E1/T1 link on the M2000.
a. Check for the E1/T1-correlated alarms on the E1/T1 link that bears the IMA/UNI link on
the M2000:
105 de 526 13/11/2012 9:15


2. Check the link type on the M2000.
a. Run the MML command LST IMALNK and LST UNILNK to check the link type.
In the case of the IMA link, Go to step 3.
In the case of the UNI link, Go to step 7.
3. Check the configuration of the IMA link group on the M2000.
a. Run the MML command LST IMAGRP to query the configuration of the local IMA link
group.
b. Query the configuration of the peer IMA link group. Check whether the local
configuration matches the peer configuration, including scramble mode, 16th timeslot
support, and IMA protocol version.
c. Run the MML command MOD IMAGRP to change the local IMA group configuration.
Ensure that the local IMA group configuration matches the peer.
4. Check the local IMA link on the M2000.
a. Perform the IMA link loopback.

b. Run the MML command RST IMAGRP to reset the IMA link group.
c. Reconfigure the IMA link.

106 de 526 13/11/2012 9:15

6. Check the peer IMA.
a. Check whether the peer IMA is normal.

Y => The peer IMA is normal. Contact Huawei Customer Service Center.
N => The peer IMA malfunctions. Go to sub-step b.
b. Rectify the fault on the peer IMA.
7. Check the UNI link configuration on the M2000.
a. Run the MML command LST UNILNK to query the local UNI link configuration.
b. Query the configuration of the peer UNI link. Check whether the local configuration
matches the peer configuration, including the parameter of the 16th timeslot support.
c. Run the MML command RMV UNILNK,ADD UNILNK to change the local UNI link
configuration. Ensure that the local UNI link configuration matches the peer.
1.1.50 ALM-25823 IMA Link Loss of Frame

Description
This alarm is reported when Loss of IMA Frame (LIF) occurs.
Parameters
Link No. Link number of the IMA
107 de 526 13/11/2012 9:15

Major The IMA link is unusable, and the bandwidth of the relevant IMA link group is
reduced. If the IMA link is the only link in the IMA group, the ongoing services carried
on the IMA group are disrupted.
System Actions
The system disables the associated IMA link.
Possible Causes
The configuration of the IMA link group is incorrect.
Procedure
a. Check for the E1/T1-correlated alarms on the E1/T1 link that bears the IMA link on the
M2000:

2. Check the configuration of the IMA link group on the M2000.
a. Run the MML command LST IMAGRP to query the configuration of the local IMA link
group.
b. Query the configuration of the peer IMA link group. Check whether the local
configuration matches the peer configuration, including scramble mode and IMA
protocol version.
c. Run the MML command MOD IMAGRP to change the local IMA group configuration.
Ensure that the local IMA group configuration matches the peer.

108 de 526 13/11/2012 9:15


5. Check whether the peer IMA is normal.

1.1.51 ALM-25824 IMA Link Out of Delay Synchronization

Description
This alarm is reported when Link Out of Delay Synchronization (LODS) occurs on the IMA link.
Parameters
109 de 526 13/11/2012 9:15

System Actions
Possible Causes
The local IMA link configuration is incorrect.

Procedure
a. Check for the E1/T1-correlated alarms on the E1/T1 link that bears the IMA link on the
M2000:

2. Check the local configuration on the M2000.
a. Run the MML command DSP E1T1 to check whether the loopback is set for the E1/T1
link that bears the faulty IMA link. Note that the E1/T1 link number is the IMA link
number.
Y => The loopback is set for the E1/T1 link. Go to sub-step b.
N => The loopback is not set for the E1/T1 link. Go to step 3.
b. Run the MML command SET E1T1LOP to set NO LOOP for this link.


110 de 526 13/11/2012 9:15



1.1.52 ALM-25825 IMA Link Remote Failure Indication

Description
The remote IMA module sends the Remote Failure Indicator (RFI) to the local IMA module when the remote IMA
module detects an error in the receive link, such as Loss of Cell Delineation (LCD), Loss of IMA Frame (LIF), or
Link Out of Delay Synchronization (LODS). This alarm is reported when the local IMA module receives the RFI
from the remote IMA module.
Parameters
Minor The IMA link is unusable, and the bandwidth of the relevant IMA link group is
System Actions
Possible Causes
111 de 526 13/11/2012 9:15

The remote IMA link is faulty.
Procedure
1. Check the remote IMA link on the M2000.
a. Check for the correlated alarm on the E1/T1 link that bears the IMA link on the M2000:
E1/T1-Correlated Alarms
25823 IMA Link Loss of Frame
25824 IMA Link Out of Delay Synchronization
25821 IMA/ATM Link Loss of Cell Delineation




112 de 526 13/11/2012 9:15


1.1.53 ALM-25826 IMA Link RX Fault

Description
This alarm is reported when the received IMA parameters (symmetry mode, frame length, IMA ID, protocol
version, link number, and ICP offset) mismatch between the local and peer of the IMA link or when the received
IMA parameters are improper.
Parameters
System Actions
Possible Causes
The E1/T1 cables bearing the IMA link are incorrectly connected.
Procedure
1. Check the connected E1/T1 cables on site.
a. Check whether the TX cable and RX cable of the E1/T1 link are short-circuited.
Y => The TX cable and RX cable of the E1/T1 link are short-circuited. Go to sub-step
b.
N => The TX cable and RX cable of the E1/T1 link are not short-circuited. Go to
sub-step c.
b. Adjust the E1/T1 connections properly. Ensure that the TX/RX of each E1/T1 cable is
correctly connected to the peer end.
c. Run the MML command RST IMAGRP to reset the IMA link group.
113 de 526 13/11/2012 9:15

1.1.54 ALM-25827 IMA Link TX Unusable at Far End

Description
This alarm is reported when the IMA TX link at the far end is unusable.
Parameters
System Actions
Possible Causes
The IMA link at the far end is unusable.
Procedure


1.1.55 ALM-25828 IMA Link RX Unusable at Far End

Description
This alarm is reported when the IMA RX link at the far end is unusable.
Parameters
114 de 526 13/11/2012 9:15

System Actions
Possible Causes
The E1/T1 link bearing the remote IMA RX link is faulty.
The remote IMA RX link is blocked.
The remote IMA link is faulty.
Procedure
1. Check for the correlated alarm on the IMA link on the M2000.


115 de 526 13/11/2012 9:15

1.1.56 ALM-25829 IMA Group Startup at Far End

Description
This alarm is reported when the IMA group at the far end is started.
Parameters
Group No. IMA group number
Minor The ongoing services carried on the IMA group are disrupted.
System Actions
The system automatically disables the IMA links of the IMA group and disables the IMA group.
Possible Causes
The IMA group at the far end is being started.
Procedure
1. Check the state of the peer IMA group.
a. Check whether the peer IMA group is being established.

Y => The peer IMA group is being established. Go to sub-step b.
N => The peer IMA group is already established. Contact Huawei Customer Service
Center.
b. Wait until the peer IMA group establishment is complete.
1.1.57 ALM-25830 IMA Group Configuration Aborted

Description
This alarm is reported when the parameter settings of the local IMA group are inconsistent with the parameter
settings of the remote IMA group, or when some IMA links of the IMA group are looped in the case of the IMA
group reset.
Parameters
116 de 526 13/11/2012 9:15

Specific Problem Specific Problem of the alarm(Configuration Aborted, Link Deleted in the Group)
Major The ongoing services carried on the IMA group are disrupted.
System Actions
If the cause of the alarm is "Link Deleted in the Group", the system deletes the looped IMA links in the IMA
group.
Possible Causes
The parameter settings of the local and peer IMA group are inconsistent.
There is at least one looped IMA link in the IMA group.
Procedure
a. Check the cause of the alarm according to the alarm detailed information.
If "Specific Problem" is "Configuration Aborted", go to step 2.
If "Specific Problem" is "Link Deleted in the Group", go to step 5.
2. Check the parameter settings of the local and peer IMA group on the M2000.
a. Obtain the parameter settings of the peer IMA group.

b. Run the MML command LST IMAGRP to check the parameter settings of the local IMA
group.
c. Check whether the parameter settings of the local IMA group are consistent with those
of the peer IMA group, including scramble mode and IMA protocol version.
Y => The parameter settings are consistent. Contact Huawei Customer Service Center.
N => The parameter settings are inconsistent. Go to step 3.
3. (Skip this step and go to step 4 if the scramble mode at both ends is consistent) Change the
scramble mode on the M2000.
a. Perform the parameter negotiation on the scramble mode at both ends.
b. Run the MML command SET SCRAM to change the scramble mode of the IMA group.
Ensure that the scramble mode is consistent at both ends.
4. (Skip this step and contact Huawei customer service center if the IMA protocol version at both ends
is consistent) Change the IMA protocol version on the M2000.
117 de 526 13/11/2012 9:15

a. Perform the parameter negotiation on the IMA protocol version at both ends.
b. Reconfigure the IMA group to change the IMA protocol version of the IMA group.
5. Check for the looped link in the IMA group on the M2000.
a. Run the MML command DSP E1T1 to check whether the status of the port for the IMA
link is looped.
Y => The status of the port is looped. This indicates that an IMA link is looped. Go to
step 6.
N => The status of the port is not looped. This indicates that no IMA link is looped.
Contact Huawei Customer Service Center.
6. Release the looped IMA link on the M2000.
a. Check the E1/T1 link bearing the IMA link. Release the looped IMA link.
b. Check whether the alarm is cleared.
1.1.58 ALM-25831 IMA Group Configuration Aborted at Far End

Description
This alarm is reported when the IMA group at the far end does not accept parameter settings of the local IMA
group.
Parameters
System Actions
Possible Causes
The parameter settings of the local and peer IMA group are inconsistent.
Procedure
118 de 526 13/11/2012 9:15

1. Check the parameter settings of the local and peer IMA group on the M2000.
a. Obtain the parameter settings of the peer IMA group.
b. Run the MML command LST IMAGRP to check the parameter settings of the local IMA
group.
c. Check whether the parameter settings of the local IMA group are consistent with those
of the peer IMA group, including scramble mode and IMA protocol version.
Y => The parameter settings are consistent. Contact Huawei Customer Service Center.
2. (Skip this step and go to step 3 if the scramble mode on both ends is consistent) Change the
scramble mode on the M2000.
a. Perform the parameter negotiation on the scramble mode at both ends.
b. Run the MML command SET SCRAM to change the scramble mode of the IMA group.
Ensure that the scramble mode is consistent at both ends.
3. (Skip this step and contact Huawei customer service center if the IMA protocol version at both ends
is consistent) Change the IMA protocol version on the M2000.
a. Perform the parameter negotiation on the IMA protocol version at both ends.
b. Reconfigure the IMA group to change the IMA protocol version of the IMA group.
1.1.59 ALM-25832 IMA Group Activated Links Insufficient

Description
This alarm is reported when the number of activated links in the IMA group is less than the required number in
the local IMA group for activation.
Parameters
Major The ongoing services carried on the IMA group are disrupted.
119 de 526 13/11/2012 9:15

System Actions
None
Possible Causes
The IMA link is faulty.
The E1/T1 cable is connected incorrectly.
Procedure

N => The alarm is not cleared. The E1/T1 cable may malfunction. Go to step 2.
2. Check that the E1/T1 cable is correctly connected.
a. Run the MML command STR E1T1OFFLTST on the M2000 to check whether the
offline test on the E1/T1 link bearing the associated IMA group can be successfully
started.
Y => The offline test can be successfully started. Contact Huawei Customer Service
Center.
N => The offline test cannot be started. Go to sub-step b.
b. Check the local and peer E1/T1 connections on site. Ensure that the RX (TX) end of the
local E1/T1 cable is connected to the TX (RX) end of the corresponding peer E1/T1
cable.
1.1.60 ALM-25833 IMA Group Activated Links Insufficient at Far End

Description
This alarm is reported when the number of activated links in the IMA group at the far end is less than the
required number of links in the IMA group at the far end for activation.
Parameters
120 de 526 13/11/2012 9:15

System Actions
None
Possible Causes
The IMA link is faulty.
Procedure

N => The alarm is not cleared. The E1/T1 cable malfunctions. Go to step 2.

1.1.61 ALM-25834 IMA Group Blocked at Far End
121 de 526 13/11/2012 9:15

Description
This alarm is reported when the IMA group at the far end is blocked.
Parameters
System Actions
Possible Causes
The IMA group at the far end is blocked.
Procedure
1. Check the state of the peer IMA group.
a. Check whether the peer IMA group is blocked.

Y => The peer IMA group is blocked. Go to sub-step b.
N => The peer IMA group is not blocked. Contact Huawei Customer Service Center.
b. Unblock the peer IMA group.

1.1.62 ALM-25835 NCP Fault

Description
The NodeB Control Port (NCP), which can be carried on the SCTP or SAAL link, consists of the active NCP and
the standby NCP. This alarm is reported when the bearing links for both the active and the standby NCPs are
faulty if the CP Switch Flag is set to ENABLE. And this alarm is reported when the current NCP bearing link is
faulty if the CP Switch Flag is set to DISABLE.
Parameters
NCP Port Type NCP port type (Master NCP, Slave NCP)
Master NCP State Master NCP state (Normal, Abnormal, Not Configured)
122 de 526 13/11/2012 9:15

Slave NCP State Slave NCP state (Normal, Abnormal, Not Configured)
Major The signaling link between the base station and the RNC is faulty. In this case, the
System Actions
The system disables the associated NCP link.
Possible Causes
The bearing links for both the active and the standby NCPs are faulty.
The PVC attributes of the SAAL link bearing the NCP are inconsistent with the PVC attributes on the
peer end.
The attribute settings of the SAAL link bearing the NCP are incorrect.
The IP route between the NE and the RNC is not configured for the SCTP link bearing the NCP.
The attribute settings of the SCTP link bearing the NCP are incorrect.
The board hardware is faulty.
Procedure
1. Check the bearing link type on the M2000.
a. Run the MML command LST IUBCP to query the bearing link for the faulty NCP. Check
whether the SCTP link is configured.
Y => The SCTP link is configured. Go to step 2.
N => The SCTP link is not configured. Go to step 5.
2. Check the physical link bearing the SCTP on the M2000.
a. Run the MML command LST SCTPLNK to query the associated bearing link.
b. Check the link bearing the SCTP. Check for Ethernet-correlated alarms or
PPP/MLPPP-correlated alarms on the link.
N => The correlated alarm does not exist. Go to sub-step d.

d. Run the MML command DSP IPRT to check whether the IP route between the NE and
the RNC is configured for the link bearing the SCTP.
Y => The IP route is configured. Go to step 3.
N => The IP route is not configured. Go to sub-step e.
e. Run the MML command ADD IPRT to add an IP route.

123 de 526 13/11/2012 9:15


3. Check the SCTP link on the M2000.
a. Check for the correlated alarms on the M2000:

25888 SCTP Link Fault

4. Check the parameter settings of the SCTP link on the M2000.
a. Run the MML command LST IUBCP to query the number of the SCTP link bearing the
faulty NCP. Then, run the MML command LST SCTPLNK to query the parameter
settings of the associated link.
b. Check the parameter settings of the SCTP link bearing the faulty NCP, such as the local
IP address, local SCTP port number, peer IP address, and peer SCTP port number.
Check whether the local settings are consistent with the peer settings.
Y => The local settings are consistent with the peer settings. Go to step 5.
N => The local settings are inconsistent with the peer settings. Go to sub-step c.
c. Run the MML command RMV IUBCP to remove the faulty NCP.
d. Run the MML command MOD SCTPLNK to modify the configuration of the SCTP link
bearing the faulty NCP.
e. Run the MML command ADD IUBCP to rebuild the associated NCP.
5. Check the link bearing the SAAL on the M2000.
a. Run the MML command LST IUBCP to query the bearing link for the faulty NCP. Check
whether the SAAL link is configured.
Y => The SAAL link is configured. Go to sub-step b.
N => The SAAL link is not configured. Go to step 8.
b. Run the MML command LST SAALLNK to query the associated physical link bearing
the SAAL link.
c. Check the link (UNI/IMA/Fractional ATM/SDH/SONET) bearing the SAAL. Check for
Fractional ATM/UNI/IMA-correlated alarms, or SDH/SONET-correlated alarms on the
link.
Y => The correlated alarm exists. Go to sub-step d.
d. Clear the correlated alarm with recommended actions.

124 de 526 13/11/2012 9:15


6. Check the SAAL link on the M2000.

25840 SAAL Link Fault

7. Check the PVC attributes and parameter settings of the SAAL link bearing the NCP.
a. Run the MML command LST IUBCP to query the number of the SAAL link bearing the
NCP.
b. Run the MML command LST SAALLNK to query the attributes of the associated SAAL
link and the ATM link.
c. Check whether the local settings are consistent with the peer settings, including port
number, VPI, VCI, PVC bandwidth, and SAAL attributes.
N => The local settings are inconsistent with the peer settings. Go to sub-step d.
d. Run the MML command RMV IUBCP and RMV SAALLNK to remove the NCP and the
associated SAAL link.
e. Run the MML command ADD SAALLNK and ADD IUBCP to rebuild the NCP link. The
PVC attributes of the SAAL link and the SAAL attributes should be consistent with those
on the peer end.
8. Reset the faulty board.
1.1.63 ALM-25836 CCP Fault

Description
The Communication Control Port (CCP), which can be carried on the SCTP or SAAL link, consists of the active
CCP and the standby CCP. This alarm is reported when the bearing links for both the active and the standby
CCPs are faulty if the CP Switch Flag is set to ENABLE. And this alarm is reported when the current CCP
bearing link is faulty if the CP Switch Flag is set to DISABLE.
125 de 526 13/11/2012 9:15

Parameters
CCP Port No. CCP port number
CCP Port Type CCP port type (Master CCP, Slave CCP)
Master CCP State Master CCP state (Normal, Abnormal, Not Configured)
Slave CCP State Slave CCP state (Normal, Abnormal, Not Configured)
Major The ongoing services over the CCP port are affected. In this case, the radio link
control (RLC) malfunctions on the CCP port.
System Actions
The system disables the associated CCP port.
Possible Causes
The bearing links for both the active and the standby CCPs are faulty.
The PVC attributes of the SAAL link bearing the CCP are inconsistent with the PVC attributes on the
peer end.
The attribute settings of the SAAL link bearing the CCP are incorrect.
The IP route between the NE and the RNC is not configured for the SCTP link bearing the CCP.
The attribute settings of the SCTP link bearing the CCP are incorrect.
Procedure
1. Check the physical link type of the bearing link on the M2000.
a. Run the MML command LST IUBCP to query the bearing link for the faulty CCP. Check
whether the SCTP link is configured.
Y => The SCTP link is configured. Go to step 2.
N => The SCTP link is not configured. Go to step 5.
2. Check the physical link type bearing the SCTP on the M2000.
a. Run the MML command LST SCTPLNK to query the associated link bearing the SCTP.
Check the link bearing the SCTP for Ethernet-correlated alarms or PPP/MLPPP-
correlated alarms on the link.
N => The correlated alarm does not exist. Go to sub-step c.

126 de 526 13/11/2012 9:15

c. Run the MML command DSP IPRT to check whether the IP route between the NE and
the RNC is configured for the link bearing the faulty CCP.
Y => The IP route is configured. Go to step 3.
N => The IP route is not configured. Go to sub-step d.
d. Run the MML command ADD IPRT to add an IP route.
3. Check the SCTP link on the M2000.

25888 SCTP Link Fault

4. Check the parameter settings of the SCTP link on the M2000.
a. Run the MML command LST IUBCP to query the number of the SCTP link bearing the
faulty CCP. Then, run the MML command LST SCTPLNK to query the parameter
settings of the associated link.
b. Check the parameter settings of the SCTP link bearing the faulty CCP, such as the local
IP address, local SCTP port number, peer IP address, and peer SCTP port number.
Check whether the local settings are consistent with the peer settings.
c. Run the MML command RMV IUBCP to remove the faulty CCP.
d. Run the MML command MOD SCTPLNK to modify the configuration of the SCTP link
bearing the faulty CCP.
e. Run the MML command ADD IUBCP to rebuild the associated CCP.
5. Check the physical link bearing the SAAL on the M2000.
a. Run the MML command LST IUBCP to query the bearing link for the faulty CCP. Check
whether the SAAL link is configured.
Y => The SAAL link is configured. Go to sub-step b.
N => The SAAL link is not configured. Go to step 8.
the SAAL link.
127 de 526 13/11/2012 9:15

c. Check the link (UNI/IMA/Fractional ATM/SDH/SONET) bearing the SAAL link. Check for
physical link.

6. Check the SAAL link on the M2000.

25840 SAAL Link Fault
7. Check the parameter settings of the SAAL link and the PVC bearing the CCP.
a. Run the MML command LST IUBCP to query the number of the SAAL link bearing the
CCP.
link and the ATM link. Check whether the local settings are consistent with the peer
settings, including port number, VPI, VCI, PVC bandwidth, and SAAL attributes.
c. Run the MML command RMV IUBCP and RMV SAALLNK to remove the CCP and the
associated SAAL link.
d. Run the MML command ADD SAALLNK and ADD IUBCP to rebuild the CCP link. The
PVC attributes of the SAAL link and the SAAL attributes should be consistent with those
on the peer end.
1.1.64 ALM-25837 ALCAP Fault
128 de 526 13/11/2012 9:15

Description
This alarm is reported when the Access Link Control Application Part (ALCAP) signaling communication fails
because the transmission link bearing the ALCAP is faulty or because the ALCAP state is improper.
Parameters
Node Type ALCAP node type (MASTER LOCAL, HUB, ADJNODE, SLAVE LOCAL)
Node No. ALCAP node number
Major The calling services fails and the base station cannot provide the services.
System Actions
The system disables the associated ALCAP link.
Possible Causes
The physical link bearing the ALCAP is faulty.
The PVC attributes of the link bearing the ALCAP are inconsistent with the PVC attributes on the
peer end.
The attribute settings of the SAAL link bearing the ALCAP are incorrect.
Procedure
a. Run the MML command LST AAL2NODE to query the SAAL link bearing the faulty
ALCAP.
the SAAL link for the ALCAP.
c. Check the link (UNI/IMA/Fractional ATM/SDH/SONET) bearing the SAAL link. Check for
physical link.

2. Check the PVC attributes and parameter settings of the SAAL link bearing the ALCAP on the
M2000.
a. Run the MML command LST AAL2NODE to query the number of the SAAL link bearing
the ALCAP.
129 de 526 13/11/2012 9:15

c. Run the MML command RMV AAL2NODE and RMV SAALLNK to remove the ALCAP
and the associated SAAL link.
d. Run the MML command ADD SAALLNK and ADD AAL2NODE to rebuild the ALCAP
link. The PVC attributes of the SAAL link and the SAAL attributes should be consistent
with those on the peer end.
1.1.65 ALM-25838 AAL2 Path Fault

Description
This alarm is reported when the data transmission or reception on the ATM Adaptation Layer type 2 (AAL2)
Path is faulty.
Parameters
AAL2 Path No. AAL2 path number
Major The data transmission or reception on the AAL2 Path is faulty. In this case, some or
all the ongoing services carried on the NE using the AAL2 Path are disrupted.
System Actions
None
Possible Causes
The upper-level NE resets.
The PVC configuration (VPI/VCI of the AAL2 Path) of the current-level NE is inconsistent with that of
the upper-level NE.
The activated physical link bearing the AAL2 Path is faulty.
The E1/T1 or optical connection between the NE and the RNC is faulty.
130 de 526 13/11/2012 9:15

The board on the NE side is faulty.
The board on the RNC side is faulty.
Procedure
1. Check the upper-level NE on the M2000.
a. Check whether the current NE has an upper-level NE according to the network plan.
Y => The current NE has an upper-level NE. Go to sub-step b.
N => The current NE does not have an upper-level NE. Go to step 2.
b. Check whether the upper-level NE is reset.
Y => The upper-level NE is reset. Go to sub-step c.
N => The upper-level NE is not reset. Go to sub-step d.
c. Wait until the upper-level NE reset is complete and starts to operate normally.
N => The alarm is not cleared. Go to sub-step d.
d. On the upper-level NE side, run the MML command LST TREELNKPVC to check
whether the PVC configuration (VPI/VCI of the AAL2 Path) of the current-level NE is
consistent with that of the upper-level NE.
Y => The PVC configuration is consistent. Go to step 2.
N => The PVC configuration is inconsistent. Go to sub-step e.
e. On the upper-level NE side, run the MML commands RMV TREELNKPVC and ADD
TREELNKPVC to remove and add the PVC configuration (VPI/VCI of the AAL2 Path)
according to the network plan. Ensure that the PVC configuration (VPI/VCI of the AAL2
Path) of the current-level NE is consistent with that of the upper-level NE.
2. Check the physical link bearing the AAL2 Path on the M2000.
a. On the M2000, check for E1/T1-correlated alarms, Fractional ATM/UNI/IMA-correlated

alarms, or SDH/SONET-correlated alarms on the physical link bearing the AAL2 Path.
b. Clear the correlated alarm according to the handling suggestions associated with the
E1/T1, UNI, IMA, Fractional ATM, or SDH/SONET alarms.
3. Check the E1/T1 cables or optical fibers on site.
a. Check whether the E1/T1 cables or optical fibers are correctly connected to the peer
device. Check for incorrect connections between the local and peer device. Check for
crossed pair connections.
131 de 526 13/11/2012 9:15

Y => The E1/T1 cables or optical fibers are correctly connected. Go to step 4.
N => The E1/T1 cables or optical fibers are incorrectly connected. Go to sub-step b.
b. Replace or reconnect the E1/T1 cables or optical fibers properly.
5. Check that the AAL2 Path is activated on the peer device.
a. Check whether the AAL2 Path is activated on the peer device.

Y => The AAL2 Path is activated. Go to step 6.
N => The AAL2 Path is not activated. Go to sub-step b.
b. Activate the AAL2 Path on the peer device.

6. Reset the peer board on the AAL2 Path.
a. Reset the peer board on the AAL2 Path.

1.1.66 ALM-25840 SAAL Link Fault

Description
This alarm is reported when the Signaling ATM Adaptation Layer (SAAL) link is unusable.
Parameters
SAAL Link No. SAAL link number
Major The ongoing services carried on the base station are disrupted.
System Actions
None
132 de 526 13/11/2012 9:15

Possible Causes
The physical link bearing the SAAL link is faulty.
The SAAL link configuration on the local device is inconsistent with that on the peer device.
The Ethernet cables are not connected properly.
Procedure
a. On the M2000, check for E1/T1-correlated alarms, Fractional ATM/UNI/IMA-correlated

alarms, or SDH/SONET-correlated alarms on the physical link bearing the SAAL link.
2. Check the parameter settings of the SAAL link on the M2000.
a. Run the MML command LST SAALLNK to query the attributes of the associated SAAL
N => The local settings are inconsistent with the peer settings. Go to sub-step b.
b. Run the MML command RMV SAALLNK to remove the associated SAAL link.
c. Run the MML command ADD SAALLNK to rebuild the SAAL link. The PVC attributes of
the SAAL link and the SAAL attributes should be consistent with those on the peer end.
3. Verify the Ethernet cable connections between devices.
a. Contact engineers responsible for the bearer network to veriy the Ethernet cable
connections between devices in the bearer network, check whether the connections are
consistent with the configurations.
Y => The Ethernet cable connections are consistent with the configurations. Go to step
4.
N => The Ethernet cable connections are inconsistent with the configurations. Go to
sub-step b.
b. Contact engineers responsible for the bearer network to reconnect the Ethernet cables.
133 de 526 13/11/2012 9:15

b. Check whether the alarm is cleared.

1.1.67 ALM-25841 SAAL Link Congestion

Description
This alarm is reported when the data transmitted on the SAAL link is discarded because the data transmission
bandwidth exceeds the data bearing bandwidth of the SAAL link.
Parameters
SAAL Link No. SAAL link number
Bandwidth (bit/s) Transmit bandwidth
Major The key information may be discarded due to insufficient bandwidth. In this case, the
services are disrupted.
System Actions
None
Possible Causes
The SAAL bandwidth is insufficient.
Procedure
1. Check the alarm information on the M2000 to learn the actual SAAL link bandwidth.
a. Consult the network planners. If necessary, reconfigure the bandwidth based on service
requirements.
b. Add the SAAL bandwidth according to the new network plan.
1.1.68 ALM-25860 PPP/MLPPP Link Fault
134 de 526 13/11/2012 9:15

Description
This alarm is reported when the PPP/MLPPP link status is changed from UP to DOWN.
Parameters
PPP/MLPPP Link No. PPP/MLPPP link number
Major When the status of the Point-to-Point Protocol (PPP) link is DOWN, the services
carried on the PPP link are disrupted.
When the status of the Multi-Link Point-to-Point Protocol (MLPPP) link is DOWN, the
bandwidth of the MLPPP group is decreased.
System Actions
None
Possible Causes
The parameter settings at both ends of the PPP/MLPPP link are inconsistent.
Procedure
1. Check for the E1/T1-correlated alarm on the M2000.
a. Check for the E1/T1-correlated alarms on the E1/T1 link that bears the PPP/MLPPP
link on the M2000.
2. Check the parameter settings at both ends of the PPP/MLPPP link on the M2000.
a. Check the parameter settings of the peer PPP/MLPPP link.

b. Run the MML command LST PPPLNK/LST MPLNK to check the parameter settings of
the local PPP/MLPPP link.
c. Check whether the local parameter settings are consistent with the peer parameter
settings. (In the case of the PPP link, check the following parameters: local IP address,
peer IP address, timeslot number, authentication type, user name, and password. In
135 de 526 13/11/2012 9:15

the case of the MLPPP link, check the timeslot number.)

Y => The parameter settings at both ends of the PPP/MLPPP link are consistent. Go to
step 4.
N => The parameter settings at both ends of the PPP/MLPPP link are inconsistent. Go
to step 3.
3. Reconfigure the PPP/MLPPP link on the M2000.
a. Run the MML command RMV PPPLNK/RMV MPLNK to remove the PPP/MLPPP link.
b. Run the MML command ADD PPPLNK/ADD MPLNK to add the PPP/MLPPP link.
4. Check the status of the negotiation on the M2000.
a. Run the MML command RST PPPLNK,RMV MPLNK,ADD MPLNK to reset the PPP
link or reconfigure the MLPPP link.
1.1.69 ALM-25861 MLPPP Group Fault

Description
This alarm is reported when the MLPPP group status is changed from UP to DOWN.
Parameters
Group No. MLPPP group number
Major The services carried on the MLPPP group are disrupted.
System Actions
None
Possible Causes

The parameter settings on the two ends of the MLPPP group are inconsistent.
All the links in the MLPPP group are faulty.
136 de 526 13/11/2012 9:15

Procedure
1. Check for the alarms related to the E1/T1 on the M2000.
a. Check for the E1/T1-correlated alarms on the E1/T1 link that bears the MLPPP group
on the M2000.

2. Check the consistency of the parameter settings at both ends of the MLPPP group on the M2000.
a. Check the parameter settings of the peer MLPPP group.
b. Run the MML command LST MPGRP to check the parameter settings of the local
MLPPP group.
c. Check whether the local parameter settings are consistent with the peer parameter
settings of the MLPPP group. The parameters are local IP address, peer IP address,
authentication type, user name, and password.
Y => The parameter settings at both ends of the MLPPP group are consistent. Go to
step 3.
N => The parameter settings at both ends of the MLPPP group are inconsistent. Go to
sub-step d.
d. Run the MML command RMV MPGRP,ADD MPGRP to set the parameters related to
the MLPPP group correctly.
3. Check the MPlink in the MLPPP group on the M2000.
a. Run the MML command LST MPLNK to query the MPlink in the MLPPP group.
Y => The MPlink exists. Go to step 4.
N => The MPlink does not exist. Go to sub-step b.
b. Run the MML command ADD MPLNK to add the MPlink in the MLPPP group.
4. Check the status of the negotiation on the M2000.
a. Run the MML command RST MPGRP to reset the MLPPP group.
137 de 526 13/11/2012 9:15

1.1.70 ALM-25862 MLPPP Group Excessive Packet Loss Rate

Description
This alarm is reported when the packet loss rate of the MLPPP group exceeds the preset threshold (100 permil
by default, user-definable).
Parameters
Group No. MLPPP group number
Packet Loss Rate (per mill) Packet loss rate of the MLPPP group
Minor The services carried by the MLPPP group may be disrupted.
System Actions
None
Possible Causes
The setting of the threshold is improper.
The quality of the E1/T1 transmission is so poor that the transmission delay of MLPPP links in the
MLPPP group differs greatly from each other.
Procedure
1. Check the packet loss rate threshold on the M2000.
a. Run the MML command LST MPGRP to query the packet loss rate threshold of the
MLPPP group. Check whether the threshold is proper according to the configuration
plan.
Y=> The threshold is proper. Go to step 2.
b. Run the MML command RMV MPGRP,ADD MPGRP to reconfigure the packet loss rate
threshold of the MLPPP group.
2. Check for the E1/T1-correlated alarms on the M2000.
a. Check for the E1/T1-correlated alarms on the M2000.

138 de 526 13/11/2012 9:15

N => The correlated alarm does not exist. Contact Huawei Customer Service Center.

1.1.71 ALM-25863 PPP Link Excessive Frame Error Rate

Description
This alarm is reported when the Frame Error Rate (FER) of the PPP link exceeds the threshold (10 permil by
default, user-definable).
Parameters
Link No. PPP Link number
Current FER(per mill) Current frame error rate
Minor The ongoing services carried on the PPP link may be disrupted.
System Actions
None
Possible Causes
The preset threshold is improper.
The E1/T1 transmission performance is poor.
Procedure
1. Check the FER threshold on the M2000.
a. Run the MML command LST PPPLNK to query the FER threshold of the PPP link.
Check whether the FER threshold is proper according to the configuration plan.
b. Run the MML command RMV PPPLNK,ADD PPPLNK to modify the FER threshold of
the PPP link.
139 de 526 13/11/2012 9:15

2. Check for the E1/T1-correlated alarm on the M2000.
a. Check for the E1/T1-correlated alarms on the M2000.


1.1.72 ALM-25879 Ethernet Port Broadcast Packets Exceeding Alarm

Description
This alarm is reported when the average number of broadcast packets received on the Ethernet port per second
reaches the alarm threshold within a detection period.
Parameters
Port No. Ethernet port number
Receive Bc. Packets Average number of broadcast Packets received in a second among the 30 seconds
Per Sec. before the alarm is generated
Major The quality of services carried on the Ethernet port deteriorates. In serious cases,
the ongoing services may be interrupted.
System Actions
None.
Possible Causes
The alarm threshold is not set properly.

Network loop exists on the network, the network adapter is faulty, or cables are not connected
properly.
Some programs or protocols that may generate broadcast packets exist on the network, such as
hackers or viruses.
Procedure
1. Check the alarm threshold on the M2000.
a. Run the MML command LST ETHPORT,DSP ETHPORT to check whether the Ethernet
port is configured properly.
140 de 526 13/11/2012 9:15

Y=>The Ethernet port is configured properly. Go to step 2.

N=>The Ethernet port is not configured properly. Go to sub-step b.
b. Run the MML command SET ETHPORT to reset the alarm threshold.
2. Check the operating status of the peer device.
a. Contact maintenance engineers responsible for the peer device to check whether the
peer device or port works properly.
Y=>The peer device or port works properly. Go to step 3.
N=>The peer device or port does not work properly. Go to sub-step b.
b. Contact maintenance engineers responsible for the peer device to rectify faults.
3. Check the network loop.
a. Contact maintenance engineers responsible for the transmission device to check the
intermediate transmission device.
Y=>Network loop exists on the transmission path. Go to sub-step b.
N=>No network loop exists on the transmission path. Go to step 4.
b. Identify and rectify loop faults based on the network topology.

4. Check the programs or protocols that may generate broadcast packets.
a. Contact maintenance engineers responsible for the transmission device to check

whether the network experiences attacks from viruses or hackers, such as Address
Resolution Protocol (ARP) or Internet Control Message Protocol (ICMP) packets, port
scanning, or error packets.
Y=>The network experiences attacks from viruses or hackers. Go to sub-step b.
N=>The network does not experience attacks from viruses or hackers. Contact Huawei
b. Contact maintenance engineers responsible for the transmission device to remove
viruses or isolate the network.
1.1.73 ALM-25880 Ethernet Link Fault

Description
141 de 526 13/11/2012 9:15

This alarm is reported when the Ethernet link is disconnected.
Parameters
Major The ongoing services carried on the Ethernet link are disrupted.
System Actions
None
Possible Causes
The parameter settings of the local Ethernet port are inconsistent with those of the peer Ethernet
port.
The Ethernet transmission link is faulty.

The local Ethernet is faulty.
The peer Ethernet is faulty.
Procedure
1. Remotely check the settings of the local and the peer Ethernet ports.
a. Check the parameter settings of the peer Ethernet port.

b. Run the MML command LST ETHPORT,DSP ETHPORT to check the parameter
settings of the local Ethernet port.
c. Check whether the parameter settings of the local Ethernet port are consistent with
those of the peer Ethernet port, including port attribute, maximum transfer unit, port
speed, and duplex mode.
Y => The parameter settings are consistent. Go to step 4.
N => The parameter settings are inconsistent. Go to sub-step d.
d. Check whether the parameter settings of the local Ethernet port are consistent with the
network plan.
Y => The parameter settings are consistent. Go to sub-step e.
e. Check whether the parameter settings of the peer Ethernet port are consistent with the
network plan.
2. Set the local Ethernet parameters on the M2000.
142 de 526 13/11/2012 9:15

a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Run the MML
command SET ETHPORT to modify the Ethernet port parameters, such as port
attribute, maximum transfer unit, port speed, and duplex mode. Ensure that the
parameter settings are consistent on the local end and peer end.
3. Set the peer Ethernet parameters.
a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Change the peer
Ethernet port attribute, maximum transmission unit, speed, and duplex mode. Ensure
that the local parameter settings are consistent with the peer parameter settings.
4. Reset the local Ethernet port on the M2000.
a. Run the MML command RST ETHPORT to reset the local Ethernet port.
5. Check the Ethernet cable connected to the local Ethernet port on site.
a. Check whether the LED on the Ethernet port is blinking normally.

Y=> The LED is blinking normally. Go to step 6.
N => The LED is not blinking normally. Go to sub-step b.
b. Replace the Ethernet cable.

6. Check the peer Ethernet.
a. Check whether the peer Ethernet is functional.

Y => The peer Ethernet is functional. Contact Huawei Customer Service Center.
N => The peer Ethernet malfunctions. Go to sub-step b.
b. Rectify the fault on the peer Ethernet.
1.1.74 ALM-25881 MAC Excessive Frame Error Rate

Description
This alarm is reported when the Frame Error Rate (FER) at the MAC layer on the Ethernet port exceeds the
preset threshold (10 permil by default, user-definable).
143 de 526 13/11/2012 9:15

Parameters
Current FER(per mill) Current frame error rate
Minor The transmission quality of the Ethernet link decreases. The ongoing services may
even be disrupted.
System Actions
None
Possible Causes
The parameter settings of the local Ethernet port are inconsistent with those of the peer Ethernet
port.
The transmission performance of the Ethernet cable may be poor.
Procedure
a. Check the parameter settings of the peer Ethernet port.
b. Run the MML command LST ETHPORT,DSP ETHPORT to check the parameter
settings of the local Ethernet port.
c. Check whether the parameter settings of the local Ethernet port are consistent with
those of the peer Ethernet port, including port attribute, maximum transfer unit, port
speed, and duplex mode.
d. Check whether the parameter settings of the local Ethernet port are consistent with the
network plan.
e. Check whether the parameter settings of the peer Ethernet port are consistent with the
network plan.
2. Set the local Ethernet parameters on the M2000.
144 de 526 13/11/2012 9:15

command SET ETHPORT to modify the Ethernet port parameters, such as port
attribute, maximum transfer unit, port speed, and duplex mode. Ensure that the
parameter settings are consistent on the local end and peer end.
3. Set the peer Ethernet parameters.
a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Change the peer
Ethernet port attribute, maximum transmission unit, speed, and duplex mode. Ensure
that the local parameter settings are consistent with the peer parameter settings.
5. Check the FER threshold on the M2000.
a. Run the MML command LST ETHPORT to check whether the parameter "MAC Frame
Error Rate Occur Threshold" for the Ethernet port is set properly.
Y => The packet loss threshold is proper. Go to step 6.
N => The packet loss threshold is improper. Go to sub-step b.
b. Run the MML command SET ETHPORT to change the setting of the parameter "MAC
Frame Error Rate Occur Threshold" for the Ethernet port.
6. Check the Ethernet cable connected to the local Ethernet port on site.
a. Check whether the LED on the Ethernet port is blinking normally.

Y => The LED is blinking normally. Contact Huawei Customer Service Center.
N => The LED is not blinking normally. Go to sub-step b.
b. Replace the Ethernet cable.
1.1.75 ALM-25882 ETHOAM 3AH Discovery Failure

Description
This alarm is reported when the IEEE 802.3ah standard cannot be applied to the Ethernet port for
145 de 526 13/11/2012 9:15

implementation of Ethernet Operation, Administration and Management (OAM).
Parameters
Minor The OAM monitoring for the Ethernet link fails.
System Actions
None
Possible Causes
The settings of the local Ethernet port are incorrect.
The settings of the peer Ethernet port are incorrect.
The Ethernet link is faulty.
The ETHOAM 3AH settings are inconsistent with the network plan.
The working modes of ETHOAM 3AH at both the local end and the peer end are set to PASSIVE.
The peer device does not support the IEEE 802.3ah standard.
Procedure
1. Check for the alarms correlated to the Ethernet on the M2000.
a. On the M2000, check for the correlated alarm on the Ethernet port:
Ethernet-Correlated Alarms

2. Check the status of the Ethernet port on the M2000.
a. Run the MML command DSP ETHPORT to check whether the status of the Ethernet
port bearing ETHOAM 3AH is activated.
Y => The status of the Ethernet port is activated. Go to step 9.
N => The status of the Ethernet port is not activated. Go to step 3.
3. Check the settings of the local Ethernet port and the peer Ethernet port on the M2000.
146 de 526 13/11/2012 9:15

a. Check the settings of the peer Ethernet port.
b. Run the MML command LST ETHPORT,DSP ETHPORT to check the settings of the
local Ethernet port.
c. Check whether the settings of the local Ethernet port are consistent with those of the
peer Ethernet port. The related parameters are port attribute, maximum transmission
unit, port speed, and duplex mode.
d. Check whether the settings of the local Ethernet port are consistent with the network
plan.
e. Check whether the settings of the peer Ethernet port are consistent with the network
plan.
4. Change the settings of the local Ethernet port on the M2000.
command SET ETHPORT to change the Ethernet port attribute, maximum transmission
unit, port speed, and duplex mode. Ensure that the local parameter settings are
consistent with the peer parameter settings.
5. Change the settings of the peer Ethernet port.
a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Change the Ethernet
port attribute, maximum transmission unit, port speed, and duplex mode of the peer
end. Ensure that the local parameter settings are consistent with the peer parameter
settings.
7. Check the Ethernet cables connected to the Ethernet port on site.
a. Check whether the LEDs are running properly on the Ethernet port.
Y => The LEDs are running properly. Go to step 8.
N => The LEDs are running improperly. Go to sub-step b.
147 de 526 13/11/2012 9:15

b. Replace the Ethernet cables.

a. Check whether the peer Ethernet works properly.

Y => The peer Ethernet works properly. Go to step 9.
N => The peer Ethernet works improperly. Go to sub-step b.
b. Rectify the fault of the peer Ethernet.

9. Check the ETHOAM 3AH settings based on the network plan.
a. Run the MML command LST ETHOAM3AH to check whether the ETHOAM 3AH
settings are consistent with the network plan.
Y => The ETHOAM 3AH settings are consistent with the network plan. Go to step 10.
N => The ETHOAM 3AH settings are inconsistent with the network plan. Go to sub-step
b.
b. Run the MML command DEA ETHOAM3AH,ACT ETHOAM3AH to change the

ETHOAM 3AH settings. Ensure that the ETHOAM 3AH settings are consistent with the
network plan.
10. Check the working modes of ETHOAM 3AH at the local end and the peer end on the M2000.
a. Run the MML command LST ETHOAM3AH to check whether the working mode of
ETHOAM 3AH is set to ACTIVE.
Y => The working mode is set to ACTIVE. Go to step 11.
N => The working mode is set to PASSIVE. Go to sub-step b.
b. Contact the engineer at the peer end to check whether the working mode of ETHOAM
3AH is set to ACTIVE.
Y => The working mode is set to ACTIVE. Go to step 11.
N => The working mode is set to PASSIVE. Go to sub-step c.
c. Run the MML command DEA ETHOAM3AH,ACT ETHOAM3AH to change the working
mode of ETHOAM 3AH to ACTIVE at the local end.
11. Check that the peer device supports the IEEE 802.3ah standard.
a. Check whether the peer device supports the IEEE 802.3ah standard.
148 de 526 13/11/2012 9:15

Y => The peer device supports the IEEE 802.3ah standard. Contact Huawei Customer
Service Center.
N => The peer device does not support the IEEE 802.3ah standard. Go to sub-step b.
b. Run the MML command DEA ETHOAM3AH to deactivate the local IEEE 802.3ah
detection function.
1.1.76 ALM-25883 ETHOAM 3AH Local Fault

Description
This alarm is reported when the base station detects a faulty Ethernet port.
This alarm is not used any more. The alarm information, however, is reserved in the alarm reference and
northbound interface data to keep compatibility with the northbound interface.
Parameters
Minor The ongoing services carried over the Ethernet port deteriorate. The services may
even be disrupted.
System Actions
None
Possible Causes

Procedure
port bearing the OAM3AH is activated.
Y => The status of the Ethernet port is activated. Contact Huawei Customer Service
Center.
149 de 526 13/11/2012 9:15

peer Ethernet port. The related parameters are Port Attribute, Maximum Transmission
Unit, Speed, and Duplex.
plan.
plan.
unit, speed, and duplex mode. Ensure that the local parameter settings are consistent
with the peer parameter settings.
4. Change the settings of the peer Ethernet port on the M2000.
port attribute, maximum transmission unit, speed, and duplex mode of the peer end.
Ensure that the local parameter settings are consistent with the peer parameter
settings.
a. Run the MML command RST ETHPORT to reset the Ethernet port.
a. Check whether the RUN LED is running properly on the Ethernet port.
Y => The RUN LED is running properly. Go to step 7.
150 de 526 13/11/2012 9:15

N => The RUN LED is running improperly. Go to sub-step b.


Y => The peer Ethernet works properly. Contact Huawei Customer Service Center.

1.1.77 ALM-25884 ETHOAM 3AH Remote Fault

Description
This alarm is reported when the base station is informed that the peer Ethernet port is faulty.
Parameters
Minor The ongoing services carried over the Ethernet port deteriorate. The services may
even be disrupted.
System Actions
None
Possible Causes

Procedure
151 de 526 13/11/2012 9:15

port bearing the OAM3AH is activated.
Center.

plan.
plan.
4. Change the settings of the peer Ethernet port on the M2000.
settings.
152 de 526 13/11/2012 9:15


a. Check whether the RUN LED is running properly on the Ethernet port.
Y => The RUN LED is running properly. Go to step 7.
N => The RUN LED is running improperly. Go to sub-step b.


Y => The peer Ethernet works properly. Contact Huawei Customer Service Center.

1.1.78 ALM-25885 IP Address Conflict

Description
This alarm is reported when the IP address of the device conflicts with the IP address of an external device.
Parameters
IP Address IP address
Interface Type Interface type (PPP, PPPOE, MP, ETHERNET, TRUNK, LOOPINTF)
Interface No. Interface number
Minor The services over the conflicting IP address of the device are disrupted.
System Actions
The system automatically disables the conflicting IP address of the device.
153 de 526 13/11/2012 9:15

Possible Causes
The IP address of the device is incorrectly configured.
The IP address of the external device is incorrectly configured.
Procedure
1. Check the configuration of the conflicting IP address of the device on the M2000.
a. Run the MML command LST DEVIP/DSP DEVIP to query the configuration of the
conflicting IP address of the device. Then, check whether the configured IP address is
correct according to the configuration plan.
Y => The configured IP address is correct. Go to step 2.
N => The configured IP address is incorrect. Go to sub-step b.
b. Run the MML command RMV DEVIP/RMV OMCH to delete the conflicting IP address.
c. Run the MML command ADD DEVIP to add a correct IP address according to the
configuration plan of the IP addresses.
2. Check the configuration of the IP address of the external device.
a. Check whether the configured IP address of the external device is correct.

Y => The configured IP address is correct. Contact Huawei Customer Service Center.
N => The configured IP address is incorrect. Go to sub-step b.
b. Contact the maintenance engineers responsible for the external device to change the
conflicting IP address.
1.1.79 ALM-25886 IP Path Fault

Description
This alarm is reported when it is detected that the IP path cannot communicate with the peer devices.
Parameters
IP Path No. IP path number
Description Peer description information
154 de 526 13/11/2012 9:15

Major The services carried on the IP path cannot be normally processed.
System Actions
The system automatically disables the faulty IP path.
Possible Causes
The link bearing the IP path is faulty.

The peer route of the IP path is not configured.
The Ping detection is enabled on the IP path, but the route of the bearing network is incorrectly
configured, or the Ping message is blocked by the bearing network.
The hardware of the board carrying the IP path is faulty.
Procedure
1. Check the corresponding bearing link on the M2000.
a. Run the MML command LST IPPATH to query the corresponding link bearing the faulty
IP path.
b. Check for the Ethernet-correlated alarms or PPP/MLPPP-correlated alarms of the link

bearing the faulty IP path on the M2000.

2. Check the route on the M2000.
a. Run the MML command DSP IPRT to check whether the IP route to the peer devices is
configured for the corresponding link bearing the faulty IP path.
Y => The IP route to the peer devices is configured. Go to step 3.
N => The IP route to the peer devices is configured. Go to sub-step b.
b. Run the MML command ADD IPRT to add the IP route to the peer devices for the
corresponding link.
3. Check the configuration of the bearing network.
a. Contact the administrator of the bearing network to check whether the route of the
bearing network is correctly configured and the Ping message is not blocked.
Y => The route of the bearing network is correctly configured. Go to step 4.
N => The route of the bearing network is incorrectly configured. Go to sub-step b.
b. Contact the engineers responsible for network administration to correct the network
155 de 526 13/11/2012 9:15

configuration.
1.1.80 ALM-25887 Ethernet Trunk Link Fault

Description
This alarm is reported when the system detects that the Ethernet trunk link is faulty.
Parameters
Group No. Group number of the trunk link
Link No. Link number in the trunk group
Minor The Ethernet trunk link cannot bear the services.
System Actions
None
Possible Causes
Procedure
port bearing the trunk link is activated.
Center.
156 de 526 13/11/2012 9:15

plan.
plan.
a. Run the MML command RMV ETHTRKLNK to remove the Ethernet trunk sublink.
b. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Run the MML
c. Run the MML command ADD ETHTRKLNK to add the Ethernet trunk sublink.
4. Remotely change the settings of the peer Ethernet port.
settings.
157 de 526 13/11/2012 9:15

a. Check whether the LEDs are running properly on the Ethernet port.
Y => The LEDs are running properly. Go to step 7.
N => The LEDs are running improperly. Go to sub-step b.

7. Check the peer Ethernet network.
a. Check whether the peer Ethernet network works properly.

Y => The peer Ethernet network works properly. Contact Huawei Customer Service
Center.
N => The peer Ethernet network works improperly. Go to sub-step b.
b. Rectify the fault on the peer Ethernet network.
1.1.81 ALM-25888 SCTP Link Fault

Description
This alarm is reported when the base station detects that the Stream Control Transmission Protocol (SCTP) link
cannot process services.
Parameters
SCTP Link No. SCTP link number
Major The SCTP link cannot process signaling.
System Actions
None
Possible Causes
The link bearing the SCTP is faulty.
The parameter settings of the local device are inconsistent with those of the peer device.
The route to the peer devices is unreachable.
The Ethernet cables are not connected properly.
158 de 526 13/11/2012 9:15

Procedure
1. Check for the alarms correlated to the bearing link on the M2000.
a. Check for Ethernet-correlated alarms or PPP/MLPPP-correlated alarms on the

(ETH/PPP/MLPPP) link bearing the SCTPLNK on the M2000.
2. Check the parameter settings on both ends of the SCTP link on the M2000.
a. Run the MML command LST SCTPLNK to check whether the configuration parameters
of the local SCTP link are consistent with the configuration plan (such as the local IP
address, local SCTP port No., peer IP address, and peer SCTP port No.).
Y=> The parameter settings are consistent. Go to step 3.
N => The parameter settings are inconsistent. Go to step b.
b. Run the MML command MOD SCTPLNK to modify the incorrect configuration
parameters.
3. Check the IP route on the M2000.
a. Run the MML command DSP IPRT to check whether the IP route to the peer device is
configured for the link bearing the faulty SCTP.
Y => The IP route to the peer device is configured. Go to step 4.
N => The IP route to the peer device is not configured. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route to the peer device for the link
bearing the SCTP.
4. Check the configuration of the bearing network.
a. Consult the engineers responsible for the bearing network. Check whether the route
settings of the bearing network are correct, and the Ping messages are not blocked.
Y => The configuration of the bearing network is correct. Go to step 5.
N => The configuration of the bearing network is incorrect. Go to sub-step b.
b. Contact the engineers responsible for the bearing network to modify the network
configuration.
159 de 526 13/11/2012 9:15


5. Verify the Ethernet cable connections between devices.
a. Contact engineers responsible for the bearer network to veriy the Ethernet cable
connections between devices in the bearer network, check whether the connections are
consistent with the configurations.
Y => The Ethernet cable connections are consistent with the configurations. Go to step
6.
N => The Ethernet cable connections are inconsistent with the configurations. Go to
sub-step b.
b. Contact engineers responsible for the bearer network to reconnect the Ethernet cables.
a. Check whether the peer device works properly.

Y => The peer device works properly. Contact Huawei Customer Service Center.
N => The peer device does not work properly. Go to sub-step b.
b. Rectify the fault of the peer device.
1.1.82 ALM-25889 SCTP Link Congestion

Description
This alarm is reported when the SCTP sending buffer is occupied by a large number of data that requires to be
retransmitted and the occupancy rate of the data to the buffer reaches the congestion triggering threshold.
Parameters
Current transmit buffer usage (%) Current Sending Buffer Usage
Congestion Triggering Threshold (%) Triggering threshold of congestion
Congestion Clearance Threshold (%) Clearance threshold of congestion
Minor The services are disrupted because the data cannot be transmitted due to
insufficient space of the sending buffer.
160 de 526 13/11/2012 9:15

System Actions
None
Possible Causes
The data of the receiving buffer is not processed by the peer device in time. Therefore, the available
space of the receiving buffer is insufficient, which leads to the failure of receiving the data. As a
result, a large number of data that requires to be retransmitted exists in the sending buffer at the
local end, and then the congestion occurs.
When the packet loss occurs in the lower-layer link, a great number of data waits for retransmitting in
the sending buffer, which leads to the congestion.
The lower-layer link is instantaneously intermittent due to the reset of the FE port or PPP, or other
causes. The SCTP does not process the data congested in the sending buffer in a timely manner
during the link intermittence but retransmits the old data in the sending buffer. Subsequently, the new
data is placed in the sending buffer, which leads to the congestion.
Procedure
1. Check for the alarms correlated to the bearing link on the M2000.
a. Check for Ethernet-correlated alarms or PPP/MLPPP-correlated alarms on the

(ETH/PPP/MLPPP) link bearing the SCTPLNK on the M2000.
1.1.83 ALM-25891 IKE Negotiation Failure

Description
This alarm is reported when the base station detects the failure of the Internet Key Exchange (IKE) negotiation
with the peer device.
Parameters
Peer Name IKE Peer Name
161 de 526 13/11/2012 9:15

Major The system cannot perform bearer services.
System Actions
None
Possible Causes
The parameters configured for the local device are inconsistent with the parameters configured for
the peer device.
The certificate is invalid.
Procedure
1. Check for the correlated alarm of the Ethernet port on the M2000.
a. Check for the correlated alarm of the Ethernet port on the M2000:
25880 Ethernet Link Fault
26832 Peer Certificate Expiry
26841 Certificate Invalid
26842 Automatic Certificate Update Failed

2. Check the local configuration parameters on the M2000.
a. Run the MML commands LST IKEPEER and LST IKEPROPOSAL to check whether all
the configuration parameters of the IKE Peer and all the configuration parameters of the
IKE security association are consistent with those of the configuration plan.
N => The parameter settings are inconsistent. Go to step b.
b. Run the MML commands MOD IKEPEER and MOD IKEPROPOSAL to modify the IKE
configuration parameters that are inconsistent with those of the configuration plan.
a. Check whether the peer device works properly.

Y => The peer device works properly. Contact Huawei Customer Service Center.
N => The peer device does not work properly. Go to sub-step b.
b. Rectify the fault of the peer device.
162 de 526 13/11/2012 9:15


1.1.84 ALM-25894 ETHOAM 3AH Remote Loopback

Description
This alarm is reported when the ETHOAM 3AH remote loopback occurs with the cooperation of the local end.
Parameters
Major The Ethernet port cannot carry any service.
System Actions
None
Possible Causes
The ETHOAM 3AH remote loopback test is initiated at the peer end.
Procedure
1. Check whether the ETHOAM 3AH remote loopback test is in progress with the cooperation of the
local end on the M2000.
a. Run the MML command DSP ETHOAM3AH to check whether the ETHOAM 3AH
remote loopback test is in progress with the cooperation of the local end.
Y => The remote loopback test is in progress with the cooperation of the local end. Go
to sub-step b.
N => The remote loopback test is not in progress with the cooperation of the local end.
Go to step 2.
b. Wait till the test is complete.

2. Stop the ETHOAM 3AH loopback test at the peer end.
a. Request the peer engineers to stop the ETHOAM 3AH loopback test.
163 de 526 13/11/2012 9:15


3. Disable the remote loopback test at the peer end.
a. Run the MML command DEA ETHOAM3AH,ACT ETHOAM3AH, set the Loopback Flag
to DISABLE so that the remote loopback function is disabled.
1.1.85 ALM-25895 Ethernet Trunk Group Fault

Description
This alarm is reported when the system detects that the Ethernet trunk group is faulty.
Parameters
Group No. Group number of the trunk link
Major The service over the trunk port cannot be processed.
System Actions
None
Possible Causes
The FE/GE port configured as the port in the local trunk group is faulty.
The FE/GE port configured as the port in the peer trunk group is faulty.
The ports in the local trunk group and those in the peer trunk group are incorrectly connected.
The configuration parameters of the trunk group on the local end are inconsistent with those on the
peer end.
Procedure
1. Check for the alarm correlated with the local Ethernet on the M2000.
a. Check whether the correlated alarm of the ports in the Ethernet trunk group exists on
the M2000.
25887 Ethernet Trunk Link Fault
164 de 526 13/11/2012 9:15


2. Check for the correlated alarms of the peer Ethernet.
a. Check whether the correlated alarm of the ports in the trunk group of the peer Ethernet
exists.
b. Rectify the fault in the ports in the trunk group of the peer Ethernet.
3. Check that the ports in the trunk group of the local Ethernet are correctly connected to those of the
peer Ethernet.
a. Run the MML command LST ETHTRK to obtain the port number of the local trunk
group. Then, contact the maintenance engineers of the peer devices to obtain the port
number of the peer trunk group.
b. Check whether the ports in the trunk group of the local Ethernet are correctly connected
to those of the peer Ethernet.
Y=> The ports are correctly connected. Go to step 5.
N => The ports are incorrectly connected. Go to step 4.
4. Reconnect the ports in the trunk group of the local Ethernet to the ports in the trunk group of the
peer Ethernet.
a. Connect the ports correctly. For example, it is queried that the GE/FE ports 0 and 1 at
both ends are in the Ethernet trunk group but port 0 at the local end is connected to
port 2 at the peer end. In this case, reconnect port 0 at the local end to port 0 or port 1
at the peer end.
5. Check that the Ethernet trunk group configuration at both ends is consistent.
a. Contact the maintenance engineers of the peer devices to obtain the configuration of
the trunk group and its ports of the peer Ethernet.
Run the MML command LST ETHTRK to query the configuration of trunk group of the
local Ethernet.
b. Check whether the configuration of the Ethernet trunk group at both ends is consistent.
(Specifically, check the related parameters "Trunk Type" and "ArpProxy", and check the
number of members in the trunk group and the Ethernet ports.)
Y => The configuration of the Ethernet trunk group at both ends is consistent. Contact
N => The configuration of the Ethernet trunk group at both ends is inconsistent. Go to
165 de 526 13/11/2012 9:15

step 6.
6. Modify the configuration of the trunk group of the local Ethernet.
a. Run the MML command MOD ETHTRK to reconfigure the parameters related to the
trunk group of the Ethernet.
7. Modify the configuration of the trunk group of the peer Ethernet.
a. Reconfigure the parameters related to the trunk group of the peer Ethernet.
1.1.86 ALM-25896 IP Remote Loopback

Description
This alarm is reported when the IP remote loopback is enabled on the interface board.
Parameters
Major After the IP remote loopback is enabled, the corresponding IP data packet is looped
back to the peer end, and thus the quality of services deteriorates.
System Actions
The system disables the corresponding IP link.
Possible Causes
The IP remote loopback is enabled on the interface board.
Procedure
1. Cancel the loopback or wait for the loopback timeout.
a. Run the MML command SET UDPLOOP to set the loopback mode to "NOLOOP" to
disable the IP remote loopback.
Y=> The alarm is cleared. No further action is required.
166 de 526 13/11/2012 9:15

1.1.87 ALM-25897 IP Excessive Frame Error Rate

Description
This alarm is reported when the packet loss rate of the IP layer exceeds the alarm threshold of the IP layer.
Parameters
Interface Type Interface type (PPP, PPPOE, MP, ETHERNET, TRUNK, LOOPINTF)
Interface No. Interface number
Packet Loss Rate (per mill) Packet loss rate of the IP layer
Minor The IP data packet of the NE is discarded, which leads to the deterioration of the
quality of services carried on this port.
System Actions
When this alarm is reported and the packet loss rate is too high, the system disables the corresponding IP link.
Possible Causes
The packet is discarded due to an error (for example, an external attack) during the resolving of the
IP header.
The packet is discarded due to the failure in the segmentation and reassembling of the packet.
The packet is discarded due to insufficient resources in the system (for example, no resource is
allocated to the memory). This cause is of low probability.
Procedure
1. Check that the bearing link works properly.
a. Check for the E1/T1-correlated alarms, Ethernet-correlated alarms, or PPP/MLPPP-

correlated alarms on the associated link.

167 de 526 13/11/2012 9:15

2. Check that the bearing network is configured properly.
a. Run the MML command LST IPRT to check whether the static route is configured.
Y => The static route is configured. Go to sub-step b.
N => The static route is not configured. Go to sub-step c.
b. Run the MML command DSP IPRT to check whether the dynamic route is configured
correctly.
Y => The dynamic route is configured correctly. Contact Huawei Customer Service
Center.
N => The dynamic route is configured incorrectly. Go to sub-step c.
c. Run the MML command RMV IPRT to delete the incorrect route and run the MML
command ADD IPRT add the IP route to the peer device for the corresponding bearing
link.
1.1.88 ALM-25898 IP Path Excessive Packet Loss Rate

Description
This alarm is reported when the average packet loss rate is higher than the preset alarm threshold during 10
minutes, in the case that the IP PM function is activated on the uplink of the IP path.
Parameters
IP Path No. IP path number
Packet Loss Rate (per mill) Packet loss rate of the IP path
Minor The data packet on the link between the NE and the RNC is discarded, and the
services carried on this IP path cannot be performed normally.
System Actions
None
Possible Causes
The bandwidth configuration of the IP path on the NE side is inconsistent with that on the RNC side.
The bit error rate (BER) or frame error rate (FER) of the link bearing the IP path is extremely high.
168 de 526 13/11/2012 9:15

The bandwidth of the physical link between the NE and the RNC is restricted.
Procedure
1. Check that the bandwidth of the IP path is configured correctly.
a. Run the MML command LST IPPATH to check whether the receive bandwidth and
transmit bandwidth of the IP path are consistent with those configured on the RNC .
N => The parameter settings are inconsistent. Go to sub-step b.
b. Reconfigure the receive bandwidth and transmit bandwidth of the IP path to keep them
consistent with those configured on the RNC.
Wait for 10 minutes.
2. Check for the correlated alarm of the link bearing the IP path on the M2000.
a. On the M2000, check for the correlated alarm of the link bearing the IP path:
Ethernet-correlated alarms
PPP/MLPPP-correlated alarms

3. Check the bandwidth of the physical link between the NE and the RNC.
a. Contact the network plan engineers to check whether the configured bandwidth of the
link between the RNC and the NE meets the service requirements. If the configured
bandwidth cannot meet the service requirements, the network replan is required.
b. Increase the link bandwidth according to the network replan.
1.1.89 ALM-25899 BFD Session Fault

Description
This alarm is reported when the Bidirectional Forwarding Detection (BFD) session between the base station and
the destination IP address is faulty.
Parameters
169 de 526 13/11/2012 9:15

BFD No. BFD process number
Minor The fast fault location of the BFD on the link fails between the base station and the
destination IP address.
System Actions
The route handover is triggered when the BFD session in reliability detection is configured.
Possible Causes
The local transmission port is faulty.
The local BFD session configuration is incorrect.
The local route configuration is incorrect.
The peer device is faulty or its configuration is incorrect.
The transmission link is faulty.
Procedure
1. Check for the correlated alarm on the local transmission port.
a. On the M2000, check for the correlated alarm of the faulty port or transmission link at
the physical layer or link layer.
Ethernet-correlated alarms
25885 IP Address Conflict

2. Check the local BFD session configuration.
a. Run the MML command LST BFDSESSION to query the configuration of the local BFD
session.
b. Consult the maintenance personnel in charge of the peer device for the configuration of
the peer BFD session. Check whether the local BFD session configuration is consistent
with the peer BFD session configuration. The related parameters are "Source IP
Address", "Destination IP Address", and "Hop Type".
Y => The local BFD session configuration is consistent with the peer BFD session
configuration. Go to sub-step c.
170 de 526 13/11/2012 9:15

N => The local BFD session configuration is inconsistent with the peer BFD session
configuration. Go to sub-step d.
c. Check whether the "Hop Type" parameter is "Single Hop" or "Multiple Hops".
Y => The "Hop Type" parameter is "Single Hop". Go to sub-step e.
N => The "Hop Type" parameter is "Multiple Hops". Go to step 3.
d. Run the MML command RMV BFDSESSION,ADD BFDSESSION to modify the local
BFD session configuration according to the configuration plan.
e. Run the MML command LST DEVIP to check the subnet mask of the source IP
address of the BFD session. Based on the subnet mask, decide whether the source IP
address and the destination IP address of the BFD session are in the same network
segment.
Y => The source IP address and the destination IP address of the BFD session are in
the same network segment. Go to step 4.
N => The source IP address and the destination IP address of the BFD session are not
in the same network segment. Go to sub-step f.
f. Check whether the IP address of the device is consistent with the configuration plan.
Y => The IP address of the device is consistent with the configuration plan. Go to step
4.
N => The IP address of the device is inconsistent with the configuration plan. Go to step
g.
g. Run the MML commands RMV BFDSESSION and RMV DEVIP to delete the conflicting
IP address.
h. Run the MML commands ADD DEVIP and ADD BFDSESSION to add the correct IP
address based on the IP address plan.
3. Check the route in the case of the multi-hop BFD.
a. Run the MML command LST IPRT to check whether the route is configured for the
destination IP address of the BFD session.
Y => The route is configured. Go to step 4.
N => The route is not configured. Go to sub-step b.
b. Run the MML command ADD IPRT to add a route to the destination IP address of the
BFD session.
4. Check the peer device or the peer BFD configuration.
a. Check whether the peer device is faulty (incorrect configuration, for example).
171 de 526 13/11/2012 9:15

Y => The peer device is faulty. Go to sub-step b.

N => The peer device is functional. Go to step 5.
b. Contact the maintenance personnel in charge of the peer device to rectify the fault.
5. Check the transmission network.
a. Contact the maintenance personnel in charge of the transmission network to check for
the faulty intermediate nodes.
Y => A faulty intermediate node exists. Go to sub-step b.
N => There is no faulty intermediate node. Contact Huawei Customer Service Center.
b. Contact the maintenance personnel in charge of the intermediate devices to rectify the
fault.
1.1.90 ALM-25900 IP PM Activation Failure

Description
This alarm is reported when the system detects that the IP Performance Monitoring (PM) is in deactivated state.
Parameters
Parameter
Session ID IP PM Session ID
Alarm Alarm Cause (Activation timeout, DSCP modified, Activation of peer ippmsession is forbidden,
Cause Peer rule out of range, Peer version is not supported, Backward activation of peer ippmsession
is not supported, Request of four turple(DSCP) in backward activation of ippmsession is not
supported, long-time without FM frame received, long-time without BR frame received )
Specific Specific Problem of the alarm(Downlink, Uplink)

Problem
Minor The data packet loss or delay on the link between the base station and the peer
device cannot be detected.
System Actions
172 de 526 13/11/2012 9:15

None
Possible Causes
The bearing link of IP PM is faulty.
The IP PM configured on the peer device side is inconsistent with that configured on the base station
side.
The boards on the peer device side do not support the IP PM.
Procedure
1. Check for alarms correlated to the bearing link on the M2000.
a. Check for alarms correlated to the bearing link of IP PM on the M2000:

Ethernet-Correlated Alarms

2. Check the IP PM configurations on both sides on the M2000.
a.
Run the MML command DSP IPPMSESSION to check whether the DSCP configured
for the IP PM session is consistent with the DSCP configured on the peer device side.
Y => The DSCP configured on the base station side is consistent with the DSCP on the
peer device side. Go to step 3.
N => The DSCP configured on the base station side is inconsistent with the DSCP on
the peer device side. Go to sub-step b.
b. Run the MML command RMV IPPMSESSION,ADD IPPMSESSION to change the

DSCP on the base station side. Ensure the DSCP consistency between the base
station side and the peer device side. Then, wait for eight seconds.
3. Remotely check that the peer board that is configured with the peer IP address supports the IP PM
function.
a. Remotely check whether the peer board that is configured with the peer IP address
supports the IP PM function or whether the peer board is configured with the
corresponding IP path.
Y => The peer board supports the IP PM function or is configured with the
corresponding IP path. Contact Huawei Customer Service Center.
N => The peer board does not support the IP PM function or is not configured with the
corresponding IP path. Go to sub-step b.
b. On the peer device side, configure the peer IP address of IP PM on the board that
supports the IP PM function, or configure the corresponding IP path for the peer board.
173 de 526 13/11/2012 9:15


1.1.91 ALM-25901 Remote Maintenance Link Failure

Description
This alarm is reported when the base station cannot be maintained because of the Operation and Maintenance
CHannel (OMCH) failure.
Parameters
Major The OMCH is broken, and the user cannot maintain the remote equipment.
System Actions
The base station attempts to re-establish the OMCH.
Possible Causes
The OMCH is not configured.

The OMCH is configured incorrectly.
The transmission network is faulty.
The M2000 malfunctions.

Security authentication fails.
Procedure
1. Check the data configuration of the remote maintenance link on site.
a. Run the MML command LST OMCH to check whether the OMCH is configured.
Y => The OMCH is configured. Go to step b.
N => The OMCH is not configured. Go to sub-step c.
b. Check whether the data configuration of the OMCH is consistent with the configuration
plan, such as local IP address and peer IP address.
Y => The data configuration is consistent with the configuration plan. Go to step e.
N => The data configuration is inconsistent with the configuration plan. Go to sub-step
d.
c. Run the MML command ADD OMCH to configure the data of the OMCH based on the
configuration plan.
174 de 526 13/11/2012 9:15


d. Run the MML command MOD OMCH to configure the data of the OMCH based on the
configuration plan.
e. Run the MML command LST OMCH to check whether the parameter "binding route" is
set to "YES".
Y=> A IP route is bound to the OMCH. Go to step 2.
N=> No IP route is bound to the OMCH. Go to sub-step f.
f. Run the MML command LST IPRT to check whether the configuration of the IP route
used by the OMCH is correct according to the site plan.
Y => The configuration of the IP route is correct. Go to step 2.
N => The configuration of the IP route is incorrect. Go to sub-step g.
g. Run the MML command RMV IPRT and ADD IPRT to modify the configuration of the IP
route according to the site plan.
2. Check for the correlated alarms on site.
a. Check for the correlated alarms of the OMCH on the LMT:

25820 Fractional ATM Link Loss of Cell Delineation
25860 PPP/MLPPP Link Fault
25861 MLPPP Group Fault
25891 IKE Negotiation Failure
25895 Ethernet Trunk Group Fault
25921 SDH/SONET Loss of Frame
25922 SDH/SONET Loss of Signal
26832 Peer Certificate Expiry
26841 Certificate Invalid

175 de 526 13/11/2012 9:15

3. Check the M2000.
a. Contact the maintenance personnel in charge of the M2000 to check whether the
M2000 is operating properly and the configuration of base station is correct on the
M2000.
Y => The M2000 is operating properly and the configuration of base station is correct
on the M2000. Go to step 4.
N => The M2000 is not operating properly or the configuration of base station is not
correct on the M2000. Go to sub-step b.
b. Contact the maintenance personnel in charge of the M2000 to rectify the fault.
4. Check for faults in the transmission network on site.
a. Contact the maintenance personnel in charge of the transmission network to check

whether a fault exists.
Y => A fault exists. Go to sub-step b.
N => There is no fault. Contact Huawei Customer Service Center.
b. Contact the maintenance personnel in charge of the transmission network to rectify the
fault.
1.1.92 ALM-25902 Remote Maintenance Link Running Data and

Configuration Mismatch
Description
This alarm is reported when the running data of the remote maintenance link (OMCH) detected by the base
station is inconsistent with the OMCH data in the configuration file.
Parameters
OMCH Active/Standby Flag OMCH active/standby flag (Active OMCH, Standby OMCH)
Minor The OMCH may fail. The subscribers may fail to access the network.
System Actions
None
Possible Causes
176 de 526 13/11/2012 9:15

The OMCH configuration of the base station has errors.
The data in the configuration file is inconsistent with the active data on the base station.
The data configuration of other devices on the OMCH has errors.
Procedure
1. Query the result of automatic establishment of the remote maintenance channel
a. Run the MML command DSP DHCPRSLT to check the value of the "BS Running State"
parameter.
Y => The value of the "BS Running State" parameter is "NORMAL". Go to step 2.
N => The value of the "BS Running State" parameter is "OMCH auto-establish is
running". Go to step 4.
2. Check the OMCH data configuration on the M2000.
a. Run the MML commands LST OMCH and DSP OMCH to check whether the configured
OMCH data is consistent with the running OMCH data.
Y => The configured OMCH data is consistent with the running OMCH data. Contact
the engineers responsible for the corresponding device on the OMCH. Ask them to
modify the data configuration of the corresponding device according to the configuration
plan.
N => The configured OMCH data is inconsistent with the running OMCH data. Go to
step 3.
3. Modify the OMCH data configuration on the M2000.
a. Run the MML command MOD OMCH to modify the OMCH data configuration according
to the configuration plan.
4. Verify that the transmission configuration of the base station is correct on the M2000.
a. View the data configuration of the remote maintenance link for the base station on the
M2000. Run the MML command DSP DHCPRSLT to display the data configuration.
Then, check whether the data configuration displayed on the M2000 is consistent with
the data configuration obtained by running the MML command. The relevant parameters
include Local IP, Local Mask, Destination IP, Destination Mask, Next Hop IP, Interface
Type, Bearer Type, and VLAN ID of the remote maintenance link.
N => The parameter settings are inconsistent. Prepare a correct configuration file of the
base station on the M2000, and then go to step 5.
5. Download and activate the configuration file on the M2000.
a. Run the MML command DLD CFGFILE to download the configuration file.
b. Run the MML command SET CFGFILEENB to activate the configuration file.
177 de 526 13/11/2012 9:15

1.1.93 ALM-25920 SDH/SONET Loss of Frame Alignment

Description
This alarm is reported when Out Of Frame (OOF) is detected on the optical RX port.
Parameters
SDH/SONET Port No. SDH/SONET port number
Major The receiving optical link is broken. In this case, the ongoing services carried over
the optical port are disrupted.
System Actions
The system disables the corresponding optical link.
Possible Causes
The working mode of the local optical port is set incorrectly.
The local optical module is incompatible with the optical fiber.
The local optical module is not securely installed or not in position.
The local optical connector is not securely installed.
The local optical connector is dirty.

The local optical module is faulty.
The local optical sub-board is faulty.

On the peer end, the configuration of the optical port is incorrect, the optical connection is faulty, the
optical module is incompatible with the optical fiber, or the device is faulty.
The optical transmission link is faulty.
Procedure
1. Check the working mode of the local optical port on the M2000.
a. Run the MML command DSP STM1 to check whether the working mode of the local
optical port is set correctly. (Check the transmit clock settings based on the network
plan, and check the consistency of frame format between the local end and the peer
end.)
Y => The working mode of the local optical port is set correctly. Go to step 2.
N => The working mode of the local optical port is set incorrectly. Go to sub-step b.
b. Run the MML command SET STM1 to change the settings of the working mode of the
local optical port.
178 de 526 13/11/2012 9:15


2. Check that the local optical module is in position on site.
a. Run the MML command DSP SFP to check whether the local optical module is in
position.
Y => The local optical module is in position. Go to step 3.
N => The local optical module is not in position. Go to sub-step b.
b. Reinstall the optical module on the local board securely.
Check whether the alarm is cleared:
3. Check that the connector of the optical fiber is fixed to the optical module on the board securely on
site.
a. Reinsert the connector of the optical fiber into the optical module on the board securely.
4. Check that the local optical module matches the optical fiber on site.
a. Check whether the local optical module matches the optical fiber.
Y => The local optical module matches the optical fiber. Go to step 5.
N => The local optical module does not match the optical fiber. Go to sub-step b.
b. Replace the local optical module with an optical module that is compatible with the
optical fiber.
5. Clean the connector of the local optical fiber on site.
a. Remove the connector and clean it by using absorbent cotton with absolute alcohol.
Then, insert the connector properly.
6. (Skip this step and go to step 7 if the optical module is already replaced) Replace the optical
module on site.
a. Replace the optical module.

179 de 526 13/11/2012 9:15

7. Check that the local optical sub-board works properly.
a. Connect the TX port of the optical sub-board and its RX port by using an optical fiber
for loopback.
Y => The alarm is cleared. You can infer that the local optical sub-board is damaged.
Go to sub-step b.
b. Replace the board.

8. Check that the peer device with the optical port works properly.
a. Contact the maintenance engineers responsible for the peer optical device, and ask
them to check whether the optical port configuration, cable connection, and functionality
of the peer device are proper.
Y => The optical port configuration, cable connection, and functionality of the peer
device are proper. Go to step 9.
N => The optical port configuration, cable connection, or functionality of the peer device
is improper. Go to sub-step b.
b. Contact the maintenance engineers responsible for the peer optical device, and ask
them to rectify the fault on the peer optical device.
9. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
1.1.94 ALM-25921 SDH/SONET Loss of Frame

Description
This alarm (abbreviated as LOF) is reported when the alarm SDH/SONET Loss of Frame Alignment persists on
the optical RX port for 3 ms.
Parameters
180 de 526 13/11/2012 9:15

System Actions
Possible Causes



Procedure
plan, and check the consistency of frame format and multiplexing mode between the
local and peer end.)
local optical port.
position.

181 de 526 13/11/2012 9:15

site.
optical fiber.
module on site.

for loopback.
Go to sub-step b.

182 de 526 13/11/2012 9:15

1.1.95 ALM-25922 SDH/SONET Loss of Signal

Description
This alarm (abbreviated as LOS) is reported when the amplitude of signals on the optical RX port is lower than
the preset threshold for 100 us. That is, all 0s signals are received.
Parameters
System Actions
Possible Causes
183 de 526 13/11/2012 9:15

The RX and TX ends of the local optical fiber are reversely connected.

Procedure
local optical port.
position.

3. Reinsert the connector of the optical fiber into the optical module on the board securely.
184 de 526 13/11/2012 9:15

optical fiber.
5. Check that the local optical fiber is incorrectly connected on site.
a. Check whether the local optical fiber is incorrectly connected.

Y => The local optical fiber is incorrectly connected. Go to sub-step b.
N => The local optical fiber is correctly connected. Go to step 6.
b. Replace or reconnect the optical fiber. Ensure that the optical fiber is correctly
connected.
module on site.

for loopback.
Go to sub-step b.

185 de 526 13/11/2012 9:15

1.1.96 ALM-25923 SDH/SONET AU Loss of Pointer

Description
This alarm is reported when an unknown administration unit pointer is detected on the optical port.
Parameters
SDH/SONET AU No. SDH/SONET administrative unit number
Major If the port is an unchannelized optical port, the optical links cannot carry services.
If the port is a channelized optical port, the E1/T1 links in the administration unit
cannot carry services.
System Actions
Possible Causes
186 de 526 13/11/2012 9:15

On the peer end, the configuration of the optical port is incorrect, the optical connection is faulty, or
the device is faulty.
Procedure
local optical port.
position.

site.
187 de 526 13/11/2012 9:15


5. Replace the optical module on site.

for loopback.
Go to sub-step b.

1.1.97 ALM-25924 SDH/SONET MS Alarm Indication Signal
188 de 526 13/11/2012 9:15

Description
This alarm is reported when bit 6 to bit 8 of the K2 bytes in three consecutive frames received by the optical port
are 111.
Parameters
System Actions
Possible Causes
The internal clock of the system is faulty (when the sending clock of the optical port uses the external
8 kHz clock), or the clock of the peer device is faulty (when the sending clock of the optical port uses
the recovery clock of the receiving end).


Procedure
1. Check the setting of the sending clock of the optical port on site.
a. Run the MML command DSP STM1 to check whether the working mode of the sending
clock of the local optical port is the same as that in the network plan.
Y => The working mode is the same as that in the networking plan, and the working
mode is the external 8 kHz clock or the recovery clock of the receiving end. Go to
sub-step c.
N => The working mode is different from that in the networking plan. Go to sub-step b.
b. Run the MML command SET STM1 to change the working mode of the sending clock
of the local optical port, and then wait for 30 minutes.
189 de 526 13/11/2012 9:15


c. Run the MML command DSP CLKSTAT to check whether the status of the clock is
normal.
Y => The clock is operating properly. Go to step 2.
N => The clock malfunctions. Go to sub-step d.
d. Troubleshoot the clock failure of the NE with recommended actions of clock-related
alarms in this document.
N => The alarm is not cleared. Go to sub-step e.
e. Check for faults in the clock of the peer device and perform troubleshooting.
position.
site.
190 de 526 13/11/2012 9:15


for loopback.
Go to sub-step b.
1.1.98 ALM-25925 SDH/SONET MS Remote Defect Indication

Description
This alarm is reported when the peer end sends a defect indication signal to the local end because the alarm
SDH/SONET MS Alarm Indication Signal or the alarm SDH/SONET MS Excessive Bit Error Rate is detected on
the optical RX port of the peer end.
Parameters
191 de 526 13/11/2012 9:15

Major The data carried over the optical port is lost, and the services carried over the
optical port may be disrupted.
System Actions
None
Possible Causes

optical module does not match the optical fiber, or the device is faulty.
Procedure
b. Run the MML command SET STM1 to change the working mode of the local optical
port.
position.
192 de 526 13/11/2012 9:15


site.

for loopback.
Go to sub-step b.
193 de 526 13/11/2012 9:15

1.1.99 ALM-25926 SDH/SONET Loss of Cell Delineation

Description
This alarm (abbreviated as LCD) is reported when the optical port link fails to recover the cell data from the SDH
frame.
Parameters
System Actions
Possible Causes



194 de 526 13/11/2012 9:15

Procedure
local optical port.
position.
site.
optical fiber.
195 de 526 13/11/2012 9:15

module on site.

for loopback.
Go to sub-step b.

196 de 526 13/11/2012 9:15

1.1.100 ALM-25927 SDH/SONET Optical Port Loopback

Description
This alarm is reported when a user sets link loopback for the optical port chip on site or on the M2000.
Parameters
Warning The services carried over the optical port are disrupted.
System Actions
Possible Causes
A user sets link loopback for the optical port chip on site or on the M2000.
Procedure
1. Check the loopback status of the optical port.
a. Run the MML command DSP STM1 to check whether the local/remote loopback exists
on the optical port.
Y => The local/remote loopback exists. Go to step 2.
N => The local/remote loopback does not exist. Contact Huawei Customer Service
Center.
2. Cancel the loopback on the optical port.
a. Run the MML command SET STM1LOP to set "NOLOOP" on the optical port.
1.1.101 ALM-25928 SDH/SONET RS Trace Identifier Mismatch

Description
This alarm is reported when the trace identifier J0 received by the optical port is different from the trace
identifier J0 expected.
Parameters
197 de 526 13/11/2012 9:15

Minor The receiving optical link is broken. In this case, the ongoing services carried over
System Actions
Possible Causes
The J0 is incorrectly set on the local device or does not match.
The J0 is incorrectly set on the peer device or does not match.
The multiplexing configuration of the optical transmission link is incorrect, or the optical fiber is
incorrectly connected.
Procedure
1. Check the settings of J0 on site and on the M2000.
a. Run the MML command DSP SDHJ0J1 to check whether J0 configured on the local
device is the same as J0 received.
Y => J0 configured on the local device is the same as J0 received. Go to step 2.
N => J0 configured on the local device is different from J0 received. Go to sub-step b.
b. Run the MML command SET SDHJ0J1 to change the setting of J0 on the local device
to ensure that J0 is the same as J0 received.
2. Check the service configuration of the optical port on the peer device.
them to check whether the service configuration of the optical port on the peer device is
correct.
Y => The service configuration is correct. Go to step 3.
N => The service configuration is incorrect. Go to sub-step b.
them to change the service configuration of the optical port on the peer device.
198 de 526 13/11/2012 9:15

3. Check the multiplexing configuration and connection of the optical transmission link.
a. Contact the maintenance engineers responsible for the optical transmission link, and
ask them to check whether the multiplexing configuration is proper and the connection is
correct.
Y => The configuration is proper, and the connection is correct. Contact Huawei
N => The configuration is improper, or the connection is incorrect. Go to step b.
b. Contact the maintenance engineers responsible for the optical transmission link, and
ask them to correct the configuration or the connection.
1.1.102 ALM-25929 SDH/SONET RS Excessive Bit Error Rate

Description
This alarm is reported when the bit error rate of the regeneration section exceeds the signal invalid threshold
because of poor signal quality over the optical port.
Parameters
Minor The data carried over the optical port is lost, or the services carried over the optical
port are disrupted.
System Actions
None
Possible Causes



199 de 526 13/11/2012 9:15

Procedure
local optical port.
position.
site.
200 de 526 13/11/2012 9:15


for loopback.
Go to sub-step b.
1.1.103 ALM-25930 SDH/SONET MS Excessive Bit Error Rate

Description
This alarm is reported when the bit error rate of the multiplex section exceeds the signal invalid threshold
because of poor signal quality over the optical port.
Parameters
201 de 526 13/11/2012 9:15

Minor The data carried over the optical port is lost, or the services carried over the optical
port are disrupted.
System Actions
None
Possible Causes

Procedure
local optical port.
position.
202 de 526 13/11/2012 9:15


site.

for loopback.
Go to sub-step b.

203 de 526 13/11/2012 9:15

1.1.104 ALM-25931 SDH/SONET MS Signal Degraded

Description
This alarm is reported when the error bit rate of the multiplex section exceeds the signal degradation threshold.
Parameters
Major The data carried over the optical port is lost, or the services carried over the optical
port are disrupted.
System Actions
None
Possible Causes



204 de 526 13/11/2012 9:15

Procedure
local optical port.
position.
N => The local optical module is in position. Go to sub-step b.

site.

205 de 526 13/11/2012 9:15

for loopback.
Go to sub-step b.

1.1.105 ALM-25932 SDH/SONET MS Remote Error Indication

Description
When the peer optical port detects that the bit error rate of the remote regeneration section exceeds the
threshold, the peer optical port sends the M1 byte to the local device. This alarm is reported when the local
device detects the remote error bit indication through the B2 byte.
Parameters
206 de 526 13/11/2012 9:15

Major The data carried over the optical port is lost, and the service quality is degraded.
System Actions
None
Possible Causes


Procedure
local optical port.
position.

207 de 526 13/11/2012 9:15

site.

for loopback.
Go to sub-step b.
208 de 526 13/11/2012 9:15


1.1.106 ALM-25933 SDH/SONET AU Alarm Indication Signal

Description
This alarm is reported when the administration unit received by the optical port is all 1s (including AU-PTR).
Parameters
SDH/SONET AU No. SDH/SONET administrative unit number
Major Services carried by the administration unit of the optical port are disrupted, and the
E1/T1 links in the administration unit cannot carry services.
System Actions
None
Possible Causes



device is faulty, or the peer device sends an indication signal for generating the alarm.
Procedure
209 de 526 13/11/2012 9:15

local optical port.
position.

site.

210 de 526 13/11/2012 9:15

for loopback.
Go to sub-step b.

1.1.107 ALM-25934 SDH/SONET HP Unequipped Defect

Description
This alarm is reported when C2 bytes in five consecutive frames sent over the high-order path of the optical port
are all 0s.
Parameters
SDH/SONET HP No. SDH/SONET high-order path number
211 de 526 13/11/2012 9:15

Major The equipped data cannot be recovered from the VC3 or VC4 frame. The services
carried over the optical port are disrupted, and the E1/T1 links in the high-order path
cannot carry services.
System Actions
None
Possible Causes
The C2 byte is set to all 0s.
The multiplexing configuration of the transmission link or the optical fiber connection is incorrect.
Procedure
1. Check the configuration of C2.
a. Run the MML command DSP SDHJ0J1 to query the overhead byte of the optical port
and check whether the value of C2 is TUG STRUCT.
Y => The value is TUG STRUCT. Go to step 2.
N => The value is not TUG STRUCT. Go to sub-step b.
them to change the value of C2.
correct.
Y => The multiplexing configuration is proper and the connection is correct. Contact
N => The multiplexing configuration is improper and the connection is incorrect. Go to
sub-step b.
ask them to change the multiplexing configuration and the connection.
1.1.108 ALM-25935 SDH/SONET HP Signal Label Mismatch

Description
This alarm is reported when the C2 byte received by the high-order path of the optical port is different from the
C2 byte expected.
212 de 526 13/11/2012 9:15

Parameters
Minor The equipped data cannot be recovered from the SDH frame. The services carried
over the optical port are disrupted, and the E1/T1 links in the high-order path cannot
carry services.
System Actions
None
Possible Causes
The signal label (C2) expected by the local device is different from the signal label (C2) sent by the
peer device.
The service configuration of the optical port on the peer device is incorrect.
Procedure
1. Check the configuration of C2.
a. Run the MML command DSP SDHJ0J1 to query the overhead byte of the optical port
and check whether the value of C2 is TUG STRUCT.
Y => The value is TUG STRUCT. Go to step 2.
N => The value is not TUG STRUCT. Go to sub-step b.
them to change the value of C2.
correct.
213 de 526 13/11/2012 9:15

them to change the service configuration of the SDH service.

correct.
sub-step b.
1.1.109 ALM-25936 SDH/SONET HP Trace Identifier Mismatch

Description
This alarm is reported when the trace identifier J1 received by the high-order path of the optical port is different
from the trace identifier J1 expected.
Parameters
Minor The E1/T1 links in the high-order path cannot carry services.
System Actions
None
Possible Causes
The channel trace byte expected by the local device is different from the channel trace byte sent by
the peer device.
The service configuration of the optical port on the peer device is incorrect.
214 de 526 13/11/2012 9:15

Procedure
1. Check the channel trace bytes configured on the local device and the peer device.
a. Run the MML command DSP SDHJ0J1 to check whether the channel trace bytes
configured on the local device and the peer device are the same.
Y => The channel trace bytes are the same. Go to step 2.
N => The channel trace bytes are different. Go to sub-step b.
b. Run the MML command SET STM1 to change the settings of the channel trace bytes to
be sent.
correct.
them to change the service configuration of the SDH service.
correct.
sub-step b.
1.1.110 ALM-25937 SDH/SONET HP Remote Defect Indication

Description
This alarm is reported when the local device receives a message from the peer device indicating the high-order
path tracing identifier mismatch (HP-TIM) or high-order path signal label mismatch (HP-SLM) for signals received
215 de 526 13/11/2012 9:15

on the peer end.
Parameters
Major The E1/T1 links in the peer high-order path cannot carry services.
System Actions
None
Possible Causes

Procedure
local optical port.
216 de 526 13/11/2012 9:15

position.

site.

for loopback.
Go to sub-step b.
217 de 526 13/11/2012 9:15

1.1.111 ALM-25938 SDH/SONET HP Remote Error Indication

Description
When the remote optical port detects the error bit, it sends the number of error blocks to the local device. This
alarm is reported when the local device detects that the number of remote error blocks exceeds the threshold.
Parameters
Major Serious defects exist in the TX direction of the E1/T1 link of the high-order path,
which may result in loss of data over the link or service degradation.
System Actions
None
Possible Causes
218 de 526 13/11/2012 9:15

Procedure
local optical port.
position.

site.
219 de 526 13/11/2012 9:15


for loopback.
Go to sub-step b.
1.1.112 ALM-25949 Excessive Flood Packet

Description
This alarm is reported when the flood packet rate reaches the specified threshold after the excessive flood
packet alarm switch is turned on.
220 de 526 13/11/2012 9:15

Parameters
Flood Packet Type Flood attack packet type (ARP, ICMP, TCP, SYN, UDP)
Current received packet rate(packet/s) Current received flood packet rate
Major The board CPU usage increases, the performance deteriorates, and packets may be
discarded, affecting the quality of services. In serious cases, the ongoing services
may be interrupted.
System Actions
None
Possible Causes
The parameter settings of the protection against flood packets or the alarm are not set properly.
The base station receives large quantities of flood packets from peer devices.
Procedure
1. Check the parameter settings of the protection against flood packets and the alarm at the local end.
a. Run the MML command LST FLOODDEFEND to check whether the local end is
protected against flood packets.
Y=>The local end is protected against flood packets. Go to sub-step b.
N=>The local end is not protected against flood packets. Go to sub-step c.
b. Based on the flood packet type and receive rate, check whether the threshold for
protecting against flood packets and the alarm threshold are set properly.
Y=>The threshold for protecting against flood packets and the alarm threshold are set
properly. Go to step 2.
N=>The threshold for protecting against flood packets or the alarm threshold is not set
properly. Go to sub-step d.
c. Run the MML command MOD FLOODDEFEND to set the parameters related to the
protection against flood packets based on the packet type and receive rate.
d. Run the MML command MOD FLOODDEFEND to modify the parameters related to the
alarm and the protection against flood packets.
221 de 526 13/11/2012 9:15


2. Check the security of the peer devices.
a. Check whether the peer devices in the bearer network work properly and whether they
keep sending large quantities of flood packets to the local device.
Y=>The peer devices do not work properly and the peer devices keep sending large
quantities of flood packets to the local device. Go to sub-step b.
N=>The peer devices work properly and they do not keep sending large quantities of
flood packets to the local device. Contact Huawei Customer Service Center.
b. Contact the network administrator to modify the network configuration and to restrict
the packet receive rate.
1.1.113 ALM-25950 Base Station Being Attacked

Description
This alarm is reported when the base station is under flood attack, invalid packet attack, Address Resolution
Protocol (ARP) spoofing, and IPSec replay.
Parameters
Parameter
Specific Specific Problem of the alarm(Excessive Flood Packet, Excessive Invalid Packet, ARP
Problem Snoofing, IPSec Replay)
Major The packet forwarding capability of transmission boards is decreased. If the packet
forwarding capability of transmission boards is exceeded, packet loss occurs,
affecting service quality.
System Actions
None
Possible Causes
The base station is under the flood attack.

The base station is under the invalid packet attack.
222 de 526 13/11/2012 9:15

The base station is under the ARP spoofing.
The base station is under the IPSec replay.
Procedure
a. If "Specific Problem" is "Excessive Flood Packets", go to step 2.

If "Specific Problem" is "Excessive Invalid Packets", go to step 3.
If "Specific Problem" is "ARP Spoofing", go to step 6.
If "Specific Problem" is "IPSec Replay", go to step 7.
2. Check the settings of flood packet defense and the alarm parameters on the M2000.
a. Run the MML command LST FLOODDEFEND to check whether the settings of the
flood packet type, flood packet defense threshold, and flood packet alarm threshold are
appropriate.
Y => The settings are appropriate. Go to step 5.
N => The settings are inappropriate. Go to sub-step b.
b. Run the MML command MOD FLOODDEFEND to change the flood packet type, flood
packet defense threshold, and flood packet alarm threshold.
3. Check the invalid packet alarm threshold on the M2000.
a. Run the MML command LST IPGUARD to check whether the setting of the invalid
packet alarm threshold is appropriate.
Y => The setting is appropriate. Go to step 4.
N => The setting is inappropriate. Go to sub-step b.
b. Run the MML command SET IPGUARD to change the invalid packet alarm threshold.
4. Find out the attack source based on the buffered packets on the M2000.
a. Run the MML command DSP INVALIDPKTINFO to check whether the discarded
packets are invalid packets.
Y => The discarded packets are invalid packets. Go to step 5.
N => The discarded packets are not invalid packets. Go to sub-step b.
b. Run the MML command MOD ACLRULE to change the filter for invalid packets.
5. Check the interconnected devices on the M2000.
223 de 526 13/11/2012 9:15

a. Check the interconnected devices to locate the source of the invalid or flood packets.
Request the network administrator to correct the network configuration to limit the rate
of invalid or flood packets.
6. Query the ARP blacklist of the peer device.
a. Run the MML command DSP ARPSPOOFING to query the IP address with different
MAC addresses. Then, find out the attack source.
7. Check the IPSec replay alarm threshold on the M2000.
a. Run the MML command LST IPGUARD to check whether the setting of the IPSec
replay alarm threshold is appropriate.
Y => The setting is appropriate. Go to step 8.
N => The setting is inappropriate. Go to sub-step b.
b. Run the MML command SET IPGUARD to change the IPSec replay alarm threshold.
8. Check the source of the replayed packets on the M2000.
a. Run the MML command DSP INVALIDPKTINFO to check the type and contents of the
packets that are discarded because of incompliance with the IPSec replay rules. Then,
find out the attack source.
1.1.114 ALM-26101 Inter-Board CANBUS Communication Failure

Description
CANBUS is a type of communication bus which is used for device management in the base station. This alarm is
reported when the CANBUS communication fails between the main control board and other boards.
Parameters
Board Type Type of the faulty board
224 de 526 13/11/2012 9:15

Minor The user fails to power on/off the board, perform hot plugging, or obtain the
electronic label. The voltage and temperature of the board cannot be monitored. In
this case, the board reliability decreases.
System Actions
None
Possible Causes
The board does not exist or is not securely installed.
The board is powered off.

The hardware of the main control board (in the subrack that houses the board) is faulty.
Procedure
a. Check for the correlated alarm of the faulty board on the M2000:

2. Reseat the faulty board properly on site.
a. Reseat the board.


4. Reseat the main control board in the subrack that houses the faulty board on site.
225 de 526 13/11/2012 9:15

a. Note: Removing or reseating the main control board disrupts all the ongoing services of
the base station. Therefore, perform this operation in low-traffic hours.
Reseat the main control board.
5. Replace the main control board in the subrack that houses the faulty board on site.
a. Note: Replacing the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. The base station software
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board.
N => The alarm is not cleared. Reinstall the original main control board. Contact Huawei
1.1.115 ALM-26104 Board Temperature Unacceptable

Description
This alarm is reported when the board temperature is out of normal range. The rated operating temperature
range is a hardware specification of boards. This range varies depending on the type of the board.
Parameters
Current Board Temperature Current board temperature (Celsius and Fahrenheit inclusive)
(C/F)
Specific Problem Specific Problem of the alarm(Temperature too High, Temperature too
Low)
Major The board is automatically powered off to prevent burnout when the temperature of
the board becomes excessively high. Services carried on the board are interrupted.
The services of the peer mode are interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty board is a baseband board that provides the aggregation function or is a
main control board.
226 de 526 13/11/2012 9:15

Minor The board that works in an extremely high-temperature or low-temperature

environment for long may be running improperly. In this case, the quality of services
carried on the board decreases.
System Actions
When the board temperature is too high, the BBU fans are set to full speed.
Possible Causes
The ambient temperature of the BBU subrack is extremely high or low.
The BBU fans are stalled.
The temperature sensor for the board is faulty.
Procedure
a. Check for the correlated alarm of the BBU that houses the faulty board on the M2000.
26110 BBU Fan Stalled
26111 BBU Fan Not at Full Speed
26204 Board Not In Position (the BBU fan unit not in position)

2. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.


N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
1.1.116 ALM-26106 Board Clock Input Unavailable

Description
227 de 526 13/11/2012 9:15

This alarm is reported when the board detects that the clock input signals are unavailable.
Parameters
Major The board cannot work normally. The ongoing services carried on the board are
interrupted. The services of the peer mode are interrupted when the following
conditions are met:
The faulty board is a baseband board that provides the aggregation function.
System Actions
If one of the two clock inputs malfunctions, the system automatically switches to the other clock
input.
If both of the clock inputs malfunction, the system automatically disables the faulty board and isolates
the board from all other boards.
Possible Causes
The board is not securely installed.

The main control board is not securely installed.
The hardware of the main control board is faulty.
The BBU subrack is faulty.
Procedure
a. Check for the correlated alarm of the main control board on the M2000:
228 de 526 13/11/2012 9:15

2. Reseat the board properly on site.


4. Reseat the main control board in the subrack that houses the faulty board on site.
1.1.117 ALM-26107 Board Input Voltage Out of Range

Description
This alarm is reported when the board detects that the input voltage is extremely high or low.
Parameters
Specific Problem Specific Problem of the alarm(Overvoltage, Undervoltage)
229 de 526 13/11/2012 9:15

disrupted. The services of the peer mode are interrupted when the following
conditions are met:
System Actions
None
Possible Causes
The power monitoring board is faulty.

Procedure
a. Check for the correlated alarm of the power monitoring board on the M2000:
26112 BBU DC Output Out of Range


Service Center.
1.1.118 ALM-26110 BBU Fan Stalled

Description
This alarm is reported when the rotation speed of the BBU fan is extremely low.
Parameters
230 de 526 13/11/2012 9:15

Major The heat dissipation capability of the BBU is degraded. The BBU that works in a
high-temperature environment for long may be running improperly. In this case, the
life cycle of the BBU decreases.
System Actions
None
Possible Causes
There are foreign objects in the BBU fan.

The BBU fan is faulty.
Procedure
1. Check the BBU fan module on site.
a. Remove the BBU fan module on site. Clean the air inlet and air outlet of the fan module.
Remove foreign objects. Then, reinstall the fan module.
2. Replace the BBU fan module on site.
a. Remove the faulty fan module and install a spare fan module.
1.1.119 ALM-26111 BBU Fan Not at Full Speed

Description
This alarm is reported when the actual rotation speed of the BBU fan is lower than 80% of the preset full speed.
Parameters
231 de 526 13/11/2012 9:15

Major The heat dissipation capability of the BBU is degraded. The BBU that works in a
high-temperature environment for long may be running improperly. In this case, the
life cycle of the BBU decreases.
System Actions
None
Possible Causes
There are foreign objects in the BBU fan.
The BBU fan is faulty.
Procedure
1. Check the BBU fan module on site.
a. Remove the BBU fan module on site. Clean the air inlet and air outlet of the fan module.
Remove foreign objects. Then, reinstall the fan module.
2. Replace the BBU fan module on site.
a. Remove the faulty fan module and install a spare fan module.
1.1.120 ALM-26112 BBU DC Output Out of Range

Description
This alarm is reported when the 12 V DC output of the power module in the BBU is out of range (overvoltage or
undervoltage).
Parameters
232 de 526 13/11/2012 9:15

Major The boards in the BBU may be reset or powered off unexpectedly. In this case, the
ongoing services carried on the BBU are disrupted.
System Actions
None
Possible Causes
The AC mains supply fails or the power cabinet is faulty, resulting in an improper -48 V DC input
supplied for the BBU.
The cables for the power module are faulty or are not properly connected.
The power module is not switched on.
The power module of the BBU is faulty.
Procedure
a. Check for the correlated alarm of the site on the M2000:


2. Check the cable connections for the power module onsite.
a. Check whether the cables are functional and are properly connected to the power
module.
Y => The cables are functional and are properly connected to the power module. Go to
step 3.
N => The cables are faulty or are improperly connected to the power module. Go to
substep b.
b. Reconnect or replace the cables.

3. Check the switch on the panel of the power module on site.
a. Check whether the switch on the panel of the power module is set to off.
Y => The switch is set to off. Go to sub-step b.
N => The switch is set to on. Go to step 4.
b. Set the switch of the power module to on.
233 de 526 13/11/2012 9:15


a. Replace the BBU power module.

1.1.121 ALM-26113 Base Station DC Power Supply Abnormal

Description
This alarm is reported when the input voltage of the BBU is lower than the preset alarm threshold.
Parameters
Input Voltage(0.1V) BBU input voltage
Specific Problem Specific Problem of the alarm(Overvoltage, Undervoltage)
Major The BBU may be powered off. In this case, the ongoing services carried on the BBU
are disrupted.
System Actions
None
Possible Causes
The AC mains or the power system malfunctions.
The power module of the BBU is faulty.
Procedure
1. Check the AC mains and the power system on the M2000.

N => The correlated alarm does not exist. Go to sub-step c.
234 de 526 13/11/2012 9:15


c. Check whether the power system is provided by Huawei.

Y => The power system is provided by Huawei. Go to step 2.
N => The power system is provided by a third-party manufacturer. Go to sub-step d.
d. Contact the maintenance personnel of the third-party manufacturer responsible for the
power system. Ask them to check whether the AC mains and the power system are
functional.
Y => The AC mains and the power system are functional. Go to step 2.
N => The AC mains or the power system malfunctions. Go to sub-step e.
e. Contact the maintenance personnel of the third-party manufacturer responsible for the
power system. Ask them to rectify the fault in power supply.
a. Replace the BBU power module.

1.1.122 ALM-26120 GPS Clock Output Unavailable

Description
This alarm is reported when the GPS 1PPS clock output is unavailable.
Parameters
Minor The base station fails to synchronize to the GPS clock. The system clock may be
unusable if the base station does not obtain the clock reference for a long period of
time. As a result, the quality of services of the base station decreases, resulting in
handover failure and call drop. In certain cases, the base station cannot provide
services.
System Actions
235 de 526 13/11/2012 9:15

The GPS satellite card is reset.
Possible Causes
The software of the GPS satellite card is running improperly.
The hardware of the GPS satellite card is faulty.
Procedure
1. Reset the board holding the GPS satellite card on the M2000.
a. Confirm the type of the board that is connected with the faulty GPS satellite card.
If the board is the Universal Satellite card and Clock Unit (USCU), go to sub-step b.
If the board is the main control board, go to sub-step c.
If the GPS satellite card uses Remote GPS (RGPS), go to step 3.
b. Run the MML command RST BRDPWROFF to reset the USCU.
c. Note: Resetting the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the main control board.
2. Replace the board holding the GPS satellite card on site.
a. Use a multimeter to measure the voltage between the shielding layer and the core wire
on the GPS connector. Check whether the voltage is in the range 4 V to 6 V.
Y => The voltage is in the normal range. Contact Huawei Customer Service Center.
N => The voltage is beyond the normal range. The GPS satellite card is faulty. Go to
sub-step b.
b. Replace the board, which is the USCU or main control board.
Service Center.
3. Check the cable connections between the RGPS and the USCU or between the RGPS and the RRU
on site.
a. Check the cable connections between the RGPS and the USCU or between the RGPS
and the RRU on site. Rectify the faults on cable connections, including improper or
damaged connections.
236 de 526 13/11/2012 9:15

b. Replace the RGPS module by referring to the RGPS installation manual.

1.1.123 ALM-26121 GPS Antenna Fault

Description
This alarm is reported when the connection between the GPS satellite card and the antenna is broken, or when
the feeder current is too low or too high.
Parameters
Specific Problem Specific Problem of the alarm(Antenna Short-Circuited, Antenna Open-Circuited)
services.
System Actions
None
Possible Causes
The GPS satellite card hardware is faulty.
The signal cable between the BBU and the GPS surge protector is open-circuited or short-circuited.
The GPS surge protector is faulty.
The GPS feeder is open-circuited or shot-circuited.

The antenna is faulty.
Procedure
1. Check the satellite card on site
a. Disconnect the GPS feeder from the board, and measure the voltage between the
shield layer and the wire of the GPS feeder using a multimeter. Check whether the
voltage is 5 +/- 0.5 V.
Y => The voltage is 5 +/- 0.5 V, go to sub-step c.
237 de 526 13/11/2012 9:15

N => The voltage is not 5 +/- 0.5 V, the satellite card is faulty. Go to step b.

c. Reconnect the GPS feeder to the board. Then, go to step 2.
2. Check the signal cable between the BBU and the GPS surge protector on site.
a. Disconnect the signal cable from the Protect end on the GPS surge protector, and
measure the voltage between the shield layer and the wire of the signal cable using a
multimeter. Check whether the voltage is 5 +/- 0.5 V.
N => The voltage is not 5 +/- 0.5 V, the signal cable between the BBU and the GPS
surge protector is open-circuited or short-circuited. Go to step b.
b. Replace the signal cable between the BBU and the GPS surge protector.
c. Reconnect the signal cable to the Protect end on the GPS surge protector. Go to step
3.
3. Check the GPS surge protector on site.
a. Disconnect the GPS feeder from the GPS surge protector, and measure the voltage
between the shield layer and the wire of the GPS feeder at the Surge end using a
multimeter. Check whether the voltage is 5 +/- 0.5 V.
N => The voltage is not 5 +/- 0.5 V, the GPS surge protector is faulty. Go to step b.
b. Replace the GPS surge protector according to the GPS Satellite Antenna System
Quick Installation Guide.
c. Reconnect the GPS feeder to the GPS surge protector. Go to step 4.
4. Check the feeder on site.
a. Disconnect the GPS feeder from the antenna, and measure the voltage between the
shield layer and the wire of the GPS feeder using a multimeter. Check whether the
voltage is 5 +/- 0.5 V.
Y => The voltage is 5 +/- 0.5 V, go to step 5.
N => The voltage is not 5 +/- 0.5 V, the feeder is open-circuited or short-circuited. Go
to step b.
b. Check whether the GPS feeder connector is rusty.

If it is rusty, go to step c.
If it is not rusty, go to step d.
238 de 526 13/11/2012 9:15

c. Remove rust from the GPS feeder connector, reconnect the GPS feeder to the
antenna, and waterproof the GPS feeder connector.
N => The alarm is not cleared. Go to step d.
d. Replace the feeder according to the GPS Satellite Antenna System Quick Installation
Guide.
N => The alarm is not cleared. Go to step 5. Y => The alarm is cleared. No further
action is required.
5. Replace the antenna on site.
a. Replace the antenna according to the GPS Satellite Antenna System Quick Installation
Guide.
N => The alarm is not cleared. contact Huawei Customer Service Center.
1.1.124 ALM-26122 GPS Locked Satellites Insufficient

Description
This alarm is reported when the number of locked satellites at a site is insufficient.
Parameters
services.
System Actions
None
Possible Causes
239 de 526 13/11/2012 9:15

The GPS antenna is faulty.
The clock reference is incorrectly configured.
The working mode of the GPS satellite card is incorrectly configured.
Interference or barrier exists around the GPS antenna.
Procedure
a. Check for the correlated alarm of the faulty GPS satellite card on the M2000:
26121 GPS Antenna Fault

2. Check the clock reference on the basis of site plan on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference is
consistent with the site plan.
Y => The clock reference is consistent with the site plan. Go to step 3.
N => The clock reference is inconsistent with the site plan. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference.
3. Check the working mode of the GPS satellite card on the M2000.
a. Run the MML command LST GPS to check whether the working mode of the GPS
satellite card is consistent with the configuration plan.
Y => The working mode of the GPS satellite card is consistent with the configuration
plan. Go to step 4.
N => The working mode of the GPS satellite card is inconsistent with the configuration
plan. Go to sub-step b.
b. Run the MML command MOD GPS to change the working mode of the GPS satellite
card.
4. Check for the interference or barrier around the GPS antenna on site.
a. Check the surroundings of the GPS antenna, and then rectify the fault by referring to
the installation manual of GPS antenna system.
240 de 526 13/11/2012 9:15


5. Check the GPS satellite card on site.
sub-step b.
b. Reset the board through power-off.

c. Replace the board.

Service Center.
1.1.125 ALM-26123 GPS Maintenance Link Failure

Description
This alarm is reported when the maintenance link for the GPS satellite card fails.
Parameters
Minor The base station cannot communicate with the GPS satellite card.
System Actions
None
Possible Causes
The software of the GPS satellite card is running improperly.
The cables connected to the GPS satellite card are faulty.
241 de 526 13/11/2012 9:15

Procedure
1. Reset the board holding the GPS satellite card on the M2000.
a. Check the board connected with the GPS antenna.

If the board is the Universal Satellite card and Clock Unit (USCU), go to sub-step b.
If the board is the main control board, go to sub-step c.
If the GPS satellite card uses Remote GPS (RGPS), go to step 3.
b. Run the MML command RST BRD to reset the USCU.

c. Note: Resetting the main control board disrupts all the ongoing services of the base
2. Replace the board holding the GPS satellite card on site.
sub-step b.
b. Replace the board, which is the USCU or main control board.

Service Center.
3. Check the cable connections between the RGPS and the USCU or between the RGPS and the RRU
on site.
a. Check the cable connections between the RGPS and the USCU or between the RGPS
and the RRU on site. Rectify the faults on cable connections, including improper or
damaged connections.
b. Replace the RGPS module by referring to the RGPS installation manual.
1.1.126 ALM-26200 Board Hardware Fault
242 de 526 13/11/2012 9:15

Description
This alarm is reported when the board hardware is faulty.
Parameters
Major The board cannot work normally. The ongoing services carried on the board may be
conditions are met:
Minor Some functions of the board fail. The board reliability decreases. The services
carried on the board may malfunction in the long term.
System Actions
If a critical component of the board is faulty, the faulty board is isolated from all other boards. Meanwhile, the
faulty board begins automatic software reloading and resets.
Possible Causes
The board temperature is out of range.

Procedure
26104 Board Temperature Unacceptable

243 de 526 13/11/2012 9:15




1.1.127 ALM-26201 Board Memory Soft Failure

Description
This alarm is reported when part of data in the memory of the processor in the board is overwritten due to
external electromagnetic interference or radiation.
Parameters
Minor The service processing capability of the board decreases. The ongoing services
carried on the board may even be disrupted. The service processing capability of the
peer mode is decreased or the services of the peer mode are interrupted when the
following conditions are met:
System Actions
The system resets the faulty processor.
Possible Causes
External electromagnetic interference or radiation exists.
244 de 526 13/11/2012 9:15

Procedure
1. Check the automatic clearance of the fault.
a. Check whether the alarm persists for more than five minutes.
Y => The alarm persists for more than five minutes. Go to step 2.
N => The alarm persists for less than five minutes. Go to sub-step b.
b. Wait until the system automatic actions are complete; the process lasts for about five
minutes.

1.1.128 ALM-26202 Board Overload

Description
This alarm is reported when the processor usage of the board is excessive.
Parameters
Minor The user access success rate and service quality may decrease.
Long-term CPU overload may result in delayed response or timeout for maintenance
tasks of the board.
The test or tracing tasks with low priority may be automatically suspended or
terminated.
System Actions
The flow control is started. The test or tracing tasks with low priority may be automatically suspended or
terminated.
Possible Causes
Too many configuration or maintenance operations are performed on the board.
245 de 526 13/11/2012 9:15

Too many test, tracing, or statistical tasks are started on the board.
The board software program error occurs.
Procedure
1. Stop all the site configuration and maintenance operations on the M2000.
a. Stop all the site configuration and maintenance operations. Then, wait for 15 minutes.
2. Stop all the site test, tracing, and statistical tasks on the M2000.
a. Stop all the site test, tracing, and statistical tasks. Then, wait for 15 minutes.
Y =>The alarm is cleared. No further action is required.
N =>The alarm is not cleared. Go to step 3.
a. Run the MML command RST BRD to reset the board.

1.1.129 ALM-26203 Board Software Program Error

Description
This alarm is reported when the board software program error occurs.
Parameters
Major The faulty board cannot work normally. The service processing capability of the
board decreases, or the ongoing services carried on the board are disrupted. The
service processing capability of the peer mode is decreased or the services of the
peer mode are interrupted when the following conditions are met:
246 de 526 13/11/2012 9:15

System Actions
The board or component is automatically reset.
Possible Causes
The board software program error occurs.
Procedure
1. Check the automatic clearance of the fault.
a. Check whether the alarm persists for more than five minutes.
Y => The alarm persists for more than five minutes. Go to step 2.
N => The alarm persists for less than five minutes. Go to sub-step b.
b. Wait until the system automatic actions are complete; the process lasts for about five
minutes.

3. Replace the faulty board onsite.

Service Center.
1.1.130 ALM-26204 Board Not In Position

Description
This alarm is reported when the board-in-position signal is not detected.
Parameters
247 de 526 13/11/2012 9:15

conditions are met:
System Actions
The system automatically disables the board and isolates the board from all other boards.
Possible Causes

The backplane slot is faulty.

The main control board (in the subrack that houses the board) is not securely installed.
The hardware of the main control board is faulty.
Procedure

2. Check the backplane slot in the BBU on site.
a. Remove the board. Then, check whether there is any bent or broken pin in the
backplane slot that holds the board.
Y => The backplane slot that holds the board malfunctions. Go to sub-step b.
N => The backplane slot that holds the board is normal. Go to step 3.
b. Check whether there is another idle backplane slot compatible with the board.
Y => There is another idle backplane slot. Go to sub-step c.
N => There is no idle backplane slot. Contact Huawei Customer Service Center.
c. Run the MML command RMV BRD to remove the board in the faulty slot.
d. Run the MML command ADD BRD to add the board in the idle slot.
e. Remove the board from the faulty slot and install it in the idle slot. Wait until the board
startup is complete (the RUN LED blinking, ON for 1s and OFF for 1s).
248 de 526 13/11/2012 9:15


4. Reseat the main control board properly in the subrack that houses the faulty board on site.
1.1.131 ALM-26205 BBU Board Maintenance Link Failure

Description
This alarm is reported when the maintenance link between the main control board and the other boards in the
subrack malfunctions.
Parameters
Major The board may not work normally. The ongoing services carried on the board are
conditions are met:
249 de 526 13/11/2012 9:15

System Actions
Possible Causes
The board automatically resets because of memory soft failure or software program error.
The board file system is being formatted due to errors.

The board is not installed or is not securely installed.

The board is powered off.
The hardware of the main control board (in the subrack that houses the board) is faulty.
Procedure
a. Check whether any of the following correlated alarms is reported on the faulty board on
the M2000:
26201 Board Memory Soft Failure
26202 Board Overload
26203 Board Software Program Error
26208 Board File System Damaged
N => A correlated alarm is not reported. Go to step 2.

3. Check the state of board file system on site.
a. Check whether the RUN indicator on the faulty board blinks quickly (ON for 0.125s and
OFF for 0.125s).
250 de 526 13/11/2012 9:15

Y => The RUN indicator blinks quickly. The board file system is being formatted. Go to
sub-step b.
N => The RUN indicator does not blink quickly. The board file system is not being
formatted. Go to step 4.
b. Wait until the RUN indicator on the board blinks slowly (ON for 1s and OFF for 1s).
Generally, the file system formatting process lasts for about 40 minutes.


6. Remove and then insert the main control board in the subrack that houses the faulty board on site.
a. Note: Removing and inserting the main control board interrupts the main control board
disrupts all the ongoing services of the base station. Therefore, perform this operation
in low-traffic hours.
a. Note: Replacing the main control board interrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. A base station software
1.1.132 ALM-26206 Main Control Board in Wrong Slot

Description
251 de 526 13/11/2012 9:15

This alarm is reported when the actual slot of the main control board is inconsistent with its configured slot.
Parameters
Major The data configuration of the main control board cannot take effect.
System Actions
The system automatically sets the configuration and running status of the active main control board to be
configured.
Possible Causes
The actual slot of the main control board is inconsistent with its configured slot.
The main control board is not configured.
Procedure
1. Check the actual cause of the alarm on the M2000.
a. Run the MML command DSP BRD to check whether the main control board is
configured.
Y => The main control board is configured. Go to sub-step b.
N => The main control board is not configured. Go to step 2.
b. Run the MML command DSP BRD to check whether the slot configured for the main
control board is consistent with the configuration plan.
Y => The slot configured for the main control board is consistent with the configuration
plan. It indicates that the fault is located at the actual installation of the main control
board. Go to step 4.
N => The slot configured for the main control board is inconsistent with the configuration
plan. Go to step 3.
2. Add a main control board on the M2000.
a. Run the MML command ADD BRD to add a main control board.
3. Modify the data configuration on the M2000.
a. Run the MML command ADD BRD to add a main control board. Then, run the MML
command RMV BRD to remove the wrong data configuration on the M2000.
252 de 526 13/11/2012 9:15


4. Remove the main control board and install it in the configured slot.
a. Run the MML command DSP BRD to query the configured slot of the main control
board on the M2000.
b. Remove the main control board, and then install it in the configured slot on site.
1.1.133 ALM-26208 Board File System Damaged

Description
This alarm is reported when the board file system is damaged.
Parameters
Major During the process of file system formatting, the board cannot be started, the
maintenance link is broken, and the ongoing services carried on the board are
disrupted.
The active workspace may be unusable when the file system of the main control
board is damaged.
The logs are lost when the file system of a board is damaged.
System Actions
The file system of the faulty board is automatically formatted by the system. Generally, the formatting process
lasts for about 40 minutes. During this process, the RUN LED on the faulty board blinks (ON for 0.125s and OFF
for 0.125s).
Possible Causes
The board flash is faulty.
Power failure occurs while the board data reading or writing is in progress. In this case, the file
system is damaged.
Procedure
253 de 526 13/11/2012 9:15

1. Check the state of board file system on site.
a. Check whether the RUN LED on the faulty board blinks quickly (ON for 0.125s and OFF
for 0.125s).
Y => The RUN LED blinks quickly (ON for 0.125s and OFF for 0.125s). The board file
system is being formatted. Go to sub-step b.
N => The RUN LED does not blink quickly (ON for 0.125s and OFF for 0.125s). The
board file system is not being formatted. Go to step 2.
b. Wait until the RUN LED on the board blinks slowly (ON for 1s and OFF for 1s).

Service Center.
1.1.134 ALM-26210 Board Blocked

Description
This alarm is reported when a board is blocked by the user.
Parameters
Major The ongoing services carried on the board are disrupted.
System Actions
None
Possible Causes
The user runs a command to block the board.
Procedure
254 de 526 13/11/2012 9:15

1. Unblock the board on the M2000.
a. The purpose of blocking a board is for service test or fault isolation. After the test is
complete or the fault is rectified, you are required to run the MML command UBL BRD
to unblock the board.
1.1.135 ALM-26214 Board Powered Off

Description
This alarm is reported when a board is powered off or cannot be powered on.
Parameters
Parameter
Power off Power-off cause (Temperature Too High, Power Saving, User Command, BBU Power Not
Cause Enough, Fault, Other Cause)
Major The ongoing services carried on the board are interrupted. The services of the peer
mode are interrupted when the following conditions are met:
System Actions
Possible Causes
The board is automatically powered off to prevent burnout in the case of a too high board
temperature.
The inter-board CANBUS communication is abnormal.
The BBU DC output is abnormal.

If the user enables the energy conserving strategy, the board is automatically powered off when the
energy conserving condition is met.
The board is powered off because of a user command.
The power supply capability of the BBU power module is insufficient.
255 de 526 13/11/2012 9:15

Procedure
26104 Board Temperature Unacceptable
26101 Inter-Board CANBUS Communication Failure
26112 BBU DC Output Out of Range
2. Check the energy conserving strategy of the board on the M2000.
a. Run the MML command LST LOWPOWERPARA to check whether the energy
conserving strategy of the board is consistent with the site plan.
Y => The energy conserving strategy of the board is consistent with the site plan. No
further action is required.
N => The energy conserving strategy of the board is inconsistent with the site plan. Go
to sub-step b.
b. Run the MML command MOD LOWPOWERPARA to change the energy conserving
strategy according to the site plan. Then, go to step 3.
3. Power on the board on the M2000.
a. Run the MML command OPR BRDPWR to power on the board.

4. Check the configuration of power modules.
a. Run the MML command DSP BRD to check whether only one UPEU is configured.
Y => Only one UPEU is configured. Go to sub-step b.
N => Two UPEUs are configured. Go to step 5.
b. Run the MML command ADD BRD to add a UPEU.
c. Install a UPEUc in the BBU on site.

5. Replace the power module.
a. Run the MML command DSP BRDMFRINFO to check whether the installed two UPEU
boards are both UPEUc boards.
Y => The installed two UPEU boards are both UPEUc boards. Contact Huawei
256 de 526 13/11/2012 9:15


N => One of the installed two UPEU boards is not the UPEUc board. Go to sub-step b.
b. Replace the UPEU with a UPEUc on site. Ensure that the two UPEU boards in the BBU
are both the UPEUc boards.
1.1.136 ALM-26215 Inter-Board Service Link Failure

Description
This alarm is reported when the inter-board communication fails on control plane or user plane in the BBU.
Parameters
TX Board Slot No. Slot number of the TX(peer) board
RX Board Slot No. Slot number of the RX(local) board
RX Board Type Type of the RX(local) board
TX Board Type Type of the TX(peer)board
Major The boards involved in the communication may not work normally. The ongoing
services carried on the boards are disrupted.
System Actions
Possible Causes
The transmit board automatically resets because of memory soft failure or software program error.
The file system in the transmit board is being formatted due to errors.
The transmit board is powered off.
The transmit board or receive board does not exist or is not securely installed.
The hardware of the transmit board or receive board is faulty.
Procedure
1. Check for the correlated alarm of the transmit board and receive board on the M2000.
a. Check for the correlated alarm of the transmit board and receive board on the M2000:
257 de 526 13/11/2012 9:15

26203 Board Software Program Error

26208 Board File System Damaged
2. Check the state of file system of the transmit board and receive board on site.
a. Check whether the RUN LED on the faulty board blinks quickly (ON for 0.125s and OFF
for 0.125s).
Y => The RUN LED blinks quickly (ON for 0.125s and OFF for 0.125s). The board file
system is being formatted. Go to sub-step b.
N => The RUN LED does not blink quickly (ON for 0.125s and OFF for 0.125s). The
board file system is not being formatted. Go to step 3.
b. Wait until the RUN LED on the board blinks slowly (ON for 1s and OFF for 1s).
3. Reseat the transmit board properly on site.

4. Replace the transmit board on site.

5. Reseat the receive board properly on site.

6. Replace the receive board on site.
258 de 526 13/11/2012 9:15


Service Center.
1.1.137 ALM-26216 Board Not Securely Installed

Description
This alarm is reported when the board is not securely installed.
Parameters
Major The board may not work normally. The ongoing services carried on the board are
conditions are met:
System Actions
None
Possible Causes

The backplane slot is faulty.
Procedure

2. Check the backplane slot in the BBU on site.
a. Remove the board. Then, check whether there is any bent or broken pin in the
259 de 526 13/11/2012 9:15

backplane slot that holds the board.

Y => The backplane slot that holds the board malfunctions. Go to sub-step b.
N => The backplane slot that holds the board is normal. Go to step 3.
b. Check whether there is another idle backplane slot compatible with the board.
Y => There is another idle backplane slot. Go to sub-step c.
N => There is no idle backplane slot. Contact Huawei Customer Service Center.
c. Run the MML command RMV BRD to remove the board in the faulty slot.
d. Run the MML command ADD BRD to add the board in the idle slot.
e. Remove the board from the faulty slot and install it in the idle slot. Wait until the board
startup is complete (the RUN LED blinking, ON for 1s and OFF for 1s).

Service Center.
1.1.138 ALM-26220 Transmission Optical Module Fault

Description
This alarm is reported when the optical module on the transmission port of the BBU is faulty.
Parameters
Cabinet No. Cabinet number of the faulty port
Subrack No. Subrack number of the faulty port
Slot No. Slot number of the faulty port
Port No. Faulty port number
Warning The transmission link on the faulty port is broken. If a backup transmission port or
backup route exists, a failover occurs and the ongoing services are not affected. If
transmission load sharing is configured on the faulty port, the available transmission
bandwidth decreases and data throughput is reduced.
System Actions
The system automatically isolates the faulty transmission port. If a backup transmission port or backup route
260 de 526 13/11/2012 9:15

exists, a failover occurs.
Possible Causes
The optical module on the transmission port of the BBU is faulty.
Procedure

2. Reseat the optical module on site.
a. Reseat the faulty optical module on site.

a. On the BBU side, replace the optical module.

1.1.139 ALM-26221 Transmission Optical Module Not In Position

Description
This alarm is reported when the optical module on the transmission port of the BBU is not in position.
Parameters
261 de 526 13/11/2012 9:15

Major The transmission link on the faulty port is broken. If a backup transmission port or
System Actions
The system automatically isolates the faulty transmission port. If a backup transmission port or backup route
exists, a failover occurs.
Possible Causes
Redundant transmission links are configured on the BBU.

The optical module on the transmission port of the BBU is not installed or securely inserted.
The optical module on the transmission port of the BBU is faulty.

The connecting piece on the transmission port of the BBU is faulty.
Procedure
1. Check for the redundant transmission links on the M2000.
a. Run the MML command LST OMCH/LST AAL2PATH/LST TREELNKPVC/LST

SAALLNK/LST DEVIP/LST SYNCETH to check whether the redundant transmission
links are configured on the faulty port according to the site plan.
Y => The redundant transmission links are configured on the faulty port. Go to sub-step
b.
N => There is no redundant transmission link on the faulty port. Go to step 2.
b. Run the MML command RMV OMCH/RMV AAL2PATH/RMV TREELNKPVC/RMV

SAALLNK/RMV DEVIP/RMV SYNCETH to remove the redundant transmission links on
the faulty port according to the site plan.
2. Check the installed optical module on site.
a. On the BBU side, check whether the optical module is installed.

Y => The optical module is installed. Go to sub-step c.
N => The optical module is not installed. Go to sub-step b.
b. Install the optical module and optical fiber.

c. Reseat the optical module. Ensure that it is securely installed.
262 de 526 13/11/2012 9:15

d. Replace the optical module.

3. Reseat the board where the faulty port is located on site.

4. Replace the board where the faulty port is located on site.

Service Center.
1.1.140 ALM-26222 Transmission Optical Interface Error

Description
This alarm is reported when the optical transmission malfunctions on the transmission port of the BBU.
Parameters
Parameter
Specific Problem Specific Problem of the alarm(Receive No Signal, Receive Power Too High, Receive Power
Too Low)
Major The transmission link on the faulty port is broken. If a backup transmission port or
Minor The quality of the transmission link on the faulty port decreases. If a backup
transmission port or backup route exists, a failover occurs and the ongoing services
are not affected. If transmission load sharing is configured on the faulty port, the
available transmission bandwidth decreases and data throughput is reduced.
263 de 526 13/11/2012 9:15

System Actions
None
Possible Causes
The optical module on the transmission port of the BBU is faulty or not installed securely, or the cable
connection on the optical module is not ready.
The optical connector on the transmission port of the BBU is dirty.

The board where the faulty transmission port is located is faulty.
The optical module on the transmission port of the peer transmission device is faulty or not installed
securely, the cable connection on the optical module is not ready, or the peer transmission device is
faulty.
The optical connection between the BBU and the peer transmission device is faulty.
Procedure
a. Check for the correlated alarm on the faulty transmission port of the BBU on the
M2000:
26220 Transmission Optical Module Fault
26221 Transmission Optical Module Not In Position

2. Check the transmission port of the BBU on site.
a. Reseat the optical module and connector on the faulty transmission port of the BBU on
site.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
3. Connect the TX and RX ports of the optical module for transmission on the BBU on site.
a. Remove the optical fiber from the optical module for transmission on the BBU. Then,
connect the TX and RX ports of the optical module by using an optical fiber for
loopback.
264 de 526 13/11/2012 9:15

Y => The alarm is cleared. Go to sub-step b.

b. Disconnect the TX and RX ports of the optical module, and restore the optical
connection of the BBU.
c. Replace the optical module.

d. Reseat the board.

e. Replace the board.

Service Center.
4. Check the optical port on the peer transmission device.
a. Contact the maintenance engineers responsible for the peer transmission device to
troubleshoot the faults on the optical port of the peer transmission device.
5. Check the optical connections.
a. Check the optical connections between the BBU and the peer transmission device.
Troubleshoot the improper optical connections, such as bent fiber, deformation, or
aging.
1.1.141 ALM-26223 Transmission Optical Interface Performance

Degraded
Description
This alarm is reported when the TX/RX performance of the optical module on the transmission port of the BBU
deteriorates.
Parameters
265 de 526 13/11/2012 9:15

Specific Problem Specific Problem of the alarm(Optical Module Performance Degraded)
Major When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the transmission link may decrease significantly, or the
transmission link is broken.
Minor When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the transmission link may decrease to some extent.
System Actions
None
Possible Causes
The optical module on the transmission port of the BBU is worn-out or not installed securely, or the
cable connection on the optical module is loose.
The optical connector on the transmission port of the BBU is dirty.

The optical module on the transmission port of the BBU is not supported by the BBU, in terms of type
(single-mode or multi-mode) and rate.
The optical port on the peer transmission device malfunctions.

The optical fibers between the BBU and the peer transmission device are bent, deformed, or
worn-out. Or the length of optical fibers is excessive, which leads to a high attenuation of optical
signals.
Procedure
1. Check the transmission port of the BBU on site.
a. Reseat the optical module and connector on the faulty transmission port of the BBU on
site.
266 de 526 13/11/2012 9:15

c. Check whether the optical module on the transmission port is supported by the BBU, in
terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5 Gbit/s).
Y => The optical module on the transmission port is supported. Go to sub-step e.
N => The optical module on the transmission port is not supported. Go to sub-step d.
d. Select the optical module that is supported by the BBU.
e. Replace the optical module.

2. Check the optical port of the peer transmission device.
a. Contact the maintenance engineers responsible for the peer transmission device to
troubleshoot the faults on the optical port of the peer transmission device.
3. Check the optical connections.
a. Check the optical connections between the BBU and the peer transmission device.
Troubleshoot the improper optical connections, such as bent fiber, deformation, or
aging.
b. Check the length of the optical link between the BBU and the peer transmission device.
If the length is excessive, additional optical trunks are required.
1.1.142 ALM-26230 BBU CPRI Optical Module Fault

Description
This alarm is reported when the optical module on the port of the BBU connecting to the lower-level RF units is
faulty.
Parameters
267 de 526 13/11/2012 9:15

Warning The information about the optical module cannot be obtained.
System Actions
None
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is faulty.
Procedure
a. Check for the correlated alarm on the interface board of the BBU connecting to the
lower-level RF units on the M2000:



1.1.143 ALM-26231 BBU CPRI Optical Module or Electrical Port Not

Ready
Description
This alarm is reported when the optical module on the port of the BBU connecting to the lower-level RF units is
not in position or when the cable connection on the optical module or electrical port is not ready.
Parameters
268 de 526 13/11/2012 9:15

Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted. The services of the peer mode are
interrupted when the following conditions are met:
The faulty port provides the aggregation function.
In ring topology, the reliability of the link decreases. In this case, the active link of
lower-level RF units is switched over to the standby link. In the case of a hot ring, the
ongoing services are not affected. In the case of a cold ring, the ongoing services
are disrupted temporarily.
System Actions
In ring topology, the active link of lower-level RF units is switched over to the standby link.
Possible Causes
A redundant RRU chain/ring is configured.
The optical module on the port of the BBU connecting to the lower-level RF units is not in position, or
the cable connection on the optical module or electrical port is not ready.
The optical module on the port of the BBU connecting to the lower-level RF units is faulty, or the
cable connected to the optical module or electrical port is faulty.
The connecting piece on the port of the BBU is faulty.
Procedure
1. Check for the redundant RRU chain/ring on the M2000.
a. Run the MML command LST RRUCHAIN to query the link networking of the faulty port.
Check whether the redundant RRU chain/ring is configured according to the site plan.
Y => The redundant RRU chain/ring is configured. Go to sub-step b.
N => There is no redundant RRU chain/ring. Go to step 2.
b. Run the MML command RMV RRUCHAIN to remove the redundant RRU chain/ring .
2. Check the installation of the optical module, or check the cable connection on the CPRI optical
module or electrical port of the BBU on site.
269 de 526 13/11/2012 9:15

a. Check whether the optical module is installed, or whether the cable is connected to the
CPRI optical module or electrical port of the BBU on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the CPRI optical/electrical port.
c. Remove the optical module or the cable connected to the CPRI optical/electrical port,
and then reinstall it securely.
d. In the case that the CPRI optical port is used, replace the optical module.
In the case that the CPRI electrical port is used, replace the cable connected to the
CPRI electrical port.
3. Reseat the interface board where the faulty port is located on site.

4. Replace the interface board where the faulty port is located on site.

Service Center.
1.1.144 ALM-26232 BBU Optical Module Transmit/Receive Fault

Description
This alarm is reported when the BBU cannot properly receive signals through the optical link (at the physical
layer) from the lower-level RF units.
Parameters
Parameter
270 de 526 13/11/2012 9:15

Too Low)
Minor When the performance of the optical module of the BBU and the lower-level RF unit
deteriorates to some extent, the quality of services carried on the lower-level RF
units may decrease to some extent.
System Actions
In ring topology, the lower-level RF units automatically switch to the normal CPRI link.
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is faulty or not
installed securely, or the cable connection on the optical module is not ready.
The optical connector on the port of the BBU connecting to the lower-level RF units is dirty.
The optical module on the port of the BBU does not match that of the lower-level RF unit, in terms of
type (single-mode or multi-mode) and rate.
The optical module on the port of the lower-level RF unit is not supported by the lower-level RF unit,
in terms of type (single-mode or multi-mode) and rate.
The optical module on the port of the BBU connecting to the lower-level RF units does not match the
connected optical fiber, in terms of type (single-mode or multi-mode) and rate.
The interface board in the BBU connecting to the lower-level RF units is faulty.
The lower-level RF unit is not powered on.

The optical module or connector of the lower-level RF unit is improperly installed or the optical
module is faulty.
The optical connector of the lower-level RF unit is dirty.
The optical module on the port of the lower-level RF unit does not match the connected optical fiber,
in terms of type (single-mode or multi-mode) and rate.
The optical link between the BBU and the lower-level RF unit is faulty.
The lower-level RF unit is faulty.
271 de 526 13/11/2012 9:15

Procedure
a. Check for the correlated alarm on the faulty port of the BBU on the M2000:
26230 BBU CPRI Optical Module Fault
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26233 BBU CPRI Optical Interface Performance Degraded
26506 RF Unit Optical Interface Performance Degraded
26540 RF Unit AC Input Power Failure

If "Specific Problem" is "Receive No Signal" or "Receive Power Too Low", go to step 3.
If "Specific Problem" is "Receive Power Too High", go to step 9.
3. Check the port of the BBU connecting to the lower-level RF units on site.
a. Reseat the optical module and connector on the faulty port of the BBU on site.
alcohol or a clean cigarette filter. Then, reinstall the connector to the optical module.
c. Check whether the optical module at one end of the link matches the optical module at
the other end, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s, 2.5
Gbit/s or other rate). Note that single-mode optical modules are labeled "1310nm",
while multi-mode ones are labeled "850nm".
Y => The optical module at one end of the CPRI link matches the optical module at the
other end. Go to sub-step e.
N => The optical module at one end of the CPRI link does not match the optical module
at the other end. Go to sub-step d.
d. On the basis of the optical module at one end of the link, select the optical module at
the other end.
Replace the optical module.
272 de 526 13/11/2012 9:15


e. Run the MML command DSP SFP to query the transmission mode of the optical
module. The single-mode optical fiber is yellow in color and the multi-mode optical fiber
is orange in color. Check whether the optical module matches the connected optical
fiber, in terms of type (single-mode or multi-mode) and rate.
Y => The optical module matches the connected optical fiber. Go to step 4.
N => The optical module does not match the connected optical fiber. Go to sub-step f.
f. Replace the optical module.

4. Connect the TX and RX ports of the optical module on the BBU on site.
a. Remove the optical fiber from the optical module of the BBU. Then, connect the TX and
RX ports of the optical module by using an optical fiber for loopback.
b. Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the BBU. Then, Go to step 5.

Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the BBU.


Service Center.
5. Check the running status of the lower-level RF unit on site.
a. On the lower-level RF unit side, check whether the RUN LED on the RF unit blinks
normally (ON for 1s and OFF for 1s).
Y => The RUN LED blinks normally. Go to step 6.
N => The RUN LED does not blink normally. Go to sub-step b.
b. Power cycle the RF unit. Wait until the RUN LED blinks normally.
273 de 526 13/11/2012 9:15


6. Check the port of the lower-level RF unit on site.
a. Reseat the optical module and connector on the CPRI port of the lower-level RF unit.
alcohol or a clean cigarette filter. Then, reinstall the connector to the optical module.
c. Check whether the optical module on the CPRI port is supported by the lower-level RF
unit, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s, 2.5 Gbit/s or
other rate).
Y => The optical module is supported. Go to sub-step e.
N => The optical module is not supported. Go to sub-step d.
d. Select the optical module that is supported by the RF unit.

7. Connect the TX and RX terminals of the optical fiber on the lower-level RF unit on site.
a. Remove the optical fiber from the optical module of the RF unit. Then, connect the TX
and RX terminals of the optical fiber by using a flange.
Y => The alarm is cleared. Go to sub-step c.
connection of the RF unit. Then, go to step 8.

Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the RF unit.
d. Replace the RF unit.

274 de 526 13/11/2012 9:15

N => The alarm is not cleared. Reinstall the original board. Then, go to step 9.
8. Check the optical connections on site.
a. Check the optical connections between the BBU and the lower-level RF unit.
Troubleshoot the improper optical connections, such as bent fiber or deformation.
b. Replace the optical fiber.

9. Check the optical modules at both ends of the link and the optical fiber on site.
a. Check whether the optical module of the BBU matches the optical moduleof the
lower-level RF unit, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s,
2.5 Gbit/s or other rate). Note that single-mode optical modules are labeled "1310nm",
while multi-mode ones are labeled "850nm".
Y => The optical module at one end of the link matches the optical module at the other
end. Go to sub-step c.
N => The optical module at one end of the link does not match the optical module at the
other end. Go to sub-step b.
b. On the basis of the optical module at one end of the CPRI link, select the optical
module at the other end.
c. Check whether the optical fiber matches the optical modules.

Y => The optical fiber matches the optical modules. Contact Huawei Customer Service
Center.
N => The optical fiber does not match the optical modules. Go to sub-step d.
d. Choose the optical fiber that matches the optical modules. Note that multi-mode optical
fibers are orange, while single-mode ones are yellow.
Or
Replace the Optical Fiber.
1.1.145 ALM-26233 BBU CPRI Optical Interface Performance Degraded

Description
275 de 526 13/11/2012 9:15

This alarm is reported when the performance of the optical module on the port of the BBU connecting to the
lower-level RF units deteriorates.
Parameters
Specific Problem Specific Problem of the alarm(Optical Module Performance Degraded)
Major When the performance of the optical module deteriorates significantly, the quality of
services carried on the link of the RF units may decrease significantly, or the ongoing
services carried on lower-level RF units may even be interrupted. The services of the
peer mode are interrupted when the following conditions are met:
Minor When the performance of the optical module deteriorates to some extent, the quality
of services carried on the link of the RF units may decrease to some extent.
System Actions
None
Possible Causes
The optical module of the BBU connecting to the lower-level RF units is worn-out.
Procedure
1. Check the port of the BBU connecting to the lower-level RF units on site.
a. Reseat the optical module and connector on the faulty port of the BBU on site.
b. Replace the optical module.
1.1.146 ALM-26234 BBU CPRI Interface Error
276 de 526 13/11/2012 9:15

Description
This alarm is reported when the link (at the link layer) between the BBU and the lower-level RF units
malfunctions.
Parameters
Parameter
Specific Specific Problem of the alarm(CPRI Interface Initialization Failure, CPRI Interface Transmit
Problem Error, CPRI Interface Reception Error)
System Actions
In ring topology, the lower-level RF units automatically switch to the normal link.
Possible Causes
If the optical transmission is used, the optical module or connector of the BBU or lower-level RF unit
may be improperly installed, the optical link is faulty, or the optical module is faulty.
If the electrical transmission is used, the cable connector of the BBU or lower-level RF unit may be
improperly installed, or the cable is faulty.
The BBU or lower-level RF unit is running improperly, or the hardware is faulty.
Data configuration is incorrect if a multi-mode base station reports the alarm. As a result, the timing
loop fails.
In multi-mode configuration, the inter-BBU connections are abnormal or the optical module used for
inter-BBU connection is faulty.
Procedure
277 de 526 13/11/2012 9:15

a. Check for the correlated alarm on the faulty port of the BBU on the M2000:
26232 BBU Optical Module Transmit/Receive Fault
26272 Inter-System RF Unit Parameter Settings Conflict
26238 RRU Network Topology Type and Configuration Mismatch
26314 Inter-BBU Port Failure
26240 BBU Topology and Configuration Mismatch
2. Check the inter-BBU connections on the M2000.
a. Based on the alarm detailed information, run the MML command LST RRUCHAIN to
query the number of the chain/ring that holds the port.
b. Based on the queried chain/ring number, run the MML command LST RRU/DSP
RRUCHAINPHYTOPO to query the configured working mode of the RF unit. Check
whether the RF unit works in dual-mode configurations and whether the main control
boards of two modes are in different BBU subracks.
Y => The RF unit works in dual-mode configurations and the main control boards of two
modes are in different BBU subracks. Go to sub-step c.
N => The RF unit does not work in dual-mode configurations, or the main control boards
of two modes are in the same BBU subrack. Go to step 3.
c. Run the MML command LST SOFTWARE to query the software versions of two
modes. Based on the queried software versions, check whether both the two modes
support inter-BBU connection.
Y => Both the two modes support inter-BBU connection. Go to sub-step e.
N => Either of the two modes does not support inter-BBU connection. Go to sub-step d.
d. Upgrade the software of the mode that does not support inter-BBU connection by
referring to the relevant upgrade guide. Ensure that both the two modes support
inter-BBU connection.
e. Check for the correlated alarm on the faulty port of the BBU on the M2000: 26314
Inter-BBU Port Failure
Y => The correlated alarm exists. Go to sub-step f.
f. Clear the correlated alarm with recommended actions.
278 de 526 13/11/2012 9:15


3. Check the type of cables on the M2000.
a. Run the MML command DSP SFP to check whether the optical module uses electrical
ports for transmission.
Y => The optical module uses electrical ports for transmission. Go to step 6.
N => The optical module does not use electrical ports for transmission. Go to step 4.
4. Connect the TX and RX ports of the optical module on the BBU side by using an optical fiber for
loopback.
a. Remove the connector of the optical module in the BBU. Use the absolute alcohol to
clean the connector. Then, reinstall the connector into the optical module.
b. Remove the optical fibers from the optical module in the BBU. Then, connect the TX and
RX ports of the optical module by using an optical fiber for loopback.
Y => The alarm is cleared. Disconnect the optical fiber from the TX and RX ports of the
optical module, and restore the optical connection of the BBU. Then, go to step 5.
c. Replace the optical module on the BBU side.



5. Connect the TX and RX terminals of the optical fibers for the RF unit onsite.
a. Remove the connector of the optical module in the RF unit. Use the absolute alcohol to
clean the connector. Then, reinstall the connector into the optical module.
b. Remove the optical fibers from the optical module of the RF unit. Then, connect the TX
279 de 526 13/11/2012 9:15

and RX terminals of the optical fibers by using a flange.

Y => The alarm is cleared. Go to step d.
c. Replace the optical fiber.

d. Replace the optical module of the lower-level RF unit.

6. Replace the electrical cable or interface board of the RF unit onsite.
a. Remove and then insert the electrical cable between the BBU and lower-level RF units
on the BBU side.
b. Replace the electrical cable on the BBU side.
c. Replace the board in the BBU.

7. Replace the lower-level RF unit on site.
a. Replace the RF Unit on site.

Service Center.
1.1.147 ALM-26235 RF Unit Maintenance Link Failure

Description
The BBU is connected to RF units by electrical cables or fiber optic cables. This alarm is reported when the
maintenance link between the BBU and an RF unit malfunctions.
Parameters
280 de 526 13/11/2012 9:15

Cabinet No. Cabinet number of the faulty RF unit
Subrack No. Subrack number of the faulty RF unit
Slot No. Slot number of the faulty RF unit
Major The ongoing services carried on the RF unit are interrupted.
System Actions
The RF unit automatically resets 10 minutes after the maintenance link is broken.
Possible Causes
The fiber optic cable or electrical cable between the BBU and the RF unit or between upper- and
lower-level RF units is faulty.
The optical module inside the BBU or RF unit is faulty.
The RF unit experiences an AC power failure, is not powered on, or is running improperly.
The hardware of the RF unit or BBU is faulty.
The RF unit is automatically reset due to a fault, or the RF unit is manually reset.
When the dual-mode CPRI MUX topology is adopted, the optical module of the baseband board
working in the mode that aggregates data is faulty.
When the dual-mode CPRI MUX topology is adopted, the backplane link between the baseband
boards working in two modes has insufficient resources, or the backplane link is faulty.
When the dual-mode CPRI MUX topology is adopted, the baseband board working in the mode that
aggregates data has hardware faults, is not installed, is not powered on, or is not configured.
When the dual-mode CPRI MUX topology is adopted, the hardware of the baseband board working
in either side does not support backplane aggregation.
Procedure
1. Check the topology of the faulty RF unit on the M2000. (For details about the CPRI MUX topology,
see the 3900 Series Base Station Technical Description.)
a. Based on the alarm detailed information, run the LST RRUCHAIN command to check
whether Access Type of the RRU chain/ring is set to PEERPORT(peer port).
Y => Access Type of the RRU chain/ring is set to PEERPORT(peer port). Go to
substep b.
N => Access Type of the RRU chain/ring is set to LOCALPORT(local port). Go to step
2.
b. Check whether this alarm is also reported in the mode that aggregates data on the
M2000.
Y => This alarm is reported in the mode that aggregates data. Clear the alarm in the
mode that aggregates data. Go to step 2.
N => This alarm is not reported in the mode that aggregates data. Go to step 3.
281 de 526 13/11/2012 9:15

a. Check for the correlated alarm on the port of the RF unit on the M2000:
26234 BBU CPRI Interface Error
26233 BBU CPRI Optical Interface Performance Degraded
26501 RF Unit Optical Module or Electrical Port Not Ready
26502 RF Unit Optical Module Type Mismatch
26503 RF Unit Optical Module Transmit/Receive Fault
26504 RF Unit CPRI Interface Error
26506 RF Unit Optical Interface Performance Degraded
26507 RF Unit Optical Module Fault
26532 RF Unit Hardware Fault

3. Check for the correlated alarms in the mode whose data is aggregated on the M2000.
a. Check whether any of the following correlated alarms is reported on a baseband board
working in the mode whose data is aggregated:
26215 Inter-Board Service Link Failure
Y => One of the preceding alarms is reported. Go to substep b.
N => None of the preceding alarms is reported. Go to step 4.
b. Clear the alarm with the recommended actions.
4. Check the configuration of the baseband board in the mode that aggregates data on the M2000.
a. Run the DSP BRD command to check whether the baseband board is configured in the
mode that aggregates data.
Y => The baseband board is configured. Go to step 5.
N => The baseband board is not configured. Go to substep b.
282 de 526 13/11/2012 9:15

b. Run the ADD BRD command to add a baseband board to the mode that aggregates
data.
5. Check the capability of the baseband boards working in both modes on the M2000.
a. Run the DSP BRDMFRINFO to query the types of the baseband boards. Check
whether the baseband boards in both sides support the CPRI MUX topology according
to the DBS3900 Hardware Description.
Y => The baseband boards support the CPRI MUX topology. Go to step 6.
N => The baseband boards do not support the CPRI MUX topology. Go to substep b.
b. Replace the baseband board with a board that supports the CPRI MUX topology.
Replace the Board.
6. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
7. Check the running status of the RF unit on site.
a. Check whether the RUN LED on the RF unit blinks (ON for 1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). Go to step 8.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). Go to sub-step b.
b. Power cycle the RF unit. Wait until the RUN LED blinks (ON for 1s and OFF for 1s).
8. Replace the RF unit on site.
a. Replace the RF unit.

Service Center.
1.1.148 ALM-26236 RRU Cascading Levels and Configuration Mismatch

Description
283 de 526 13/11/2012 9:15

This alarm is reported when the actual RRU cascading levels mismatch the configuration.
Parameters
RRU Chain No. Number of the faulty RRU chain
Configured Cascading Levels Configured cascading levels
Actual Cascading Levels Cascading levels actually detected
Major When the actual RRU cascading levels mismatch the configuration, the RRUs that
are not configured cannot carry services.
System Actions
None
Possible Causes
The maintenance link for a cascaded RRU fails, or a cascaded RRU is powered off or not installed.
The RRU chain/ring configuration is incorrect.

In actual networking, the RRU cascading levels are incorrect.
Procedure
1. Check the RRU chain/ring configuration on the M2000.
a. Based on the alarm detailed information, check whether the RRU cascading levels in the
chain/ring configuration are consistent with the site plan.
Y => The RRU cascading levels are consistent with the site plan. Go to step 2.
N => The RRU cascading levels are inconsistent with the site plan. Go to sub-step b.
b. Add the RRU in the chain/ring according to the site plan.

2. Check the actual RRU networking on site.
a. Check whether the actual RRU cascading levels are consistent with the RRU cascading
levels in the site plan.
Y => The actual RRU cascading levels are consistent with the site plan. Contact Huawei
N => The actual RRU cascading levels are inconsistent with the site plan. Go to
sub-step b.
b. Remove the RRU according to the site plan.
284 de 526 13/11/2012 9:15

1.1.149 ALM-26237 RRU Network Breakpoint

Description
This alarm is reported when a breakpoint is set in the RRU chain/ring.
Parameters
Major In chain topology, the RRUs lower than the breakpoint cannot carry services. The
services carried on the lower-level RRUs in the peer mode are interrupted when the
following conditions are met:
The port that carries the faulty chain provides the aggregation function.
In ring topology, the RRUs between two breakpoints cannot carry services. In this
case, the reliability of the RRU link decreases.
System Actions
None
Possible Causes
A breakpoint is set in the RRU chain/ring.
Procedure
1. Cancel the breakpoint in the RRU chain/ring on the M2000.
a. Consult the customer about the reason for the breakpoint in the RRU chain/ring. Check
whether it is allowed to cancel the breakpoint in the RRU chain/ring.
Y => It is allowed to cancel the breakpoint. Go to sub-step b.
N => It is not allowed to cancel the breakpoint. No further action is required.
b. Run the MML command MOD RRUCHAIN to cancel the breakpoint in the RRU
chain/ring.
1.1.150 ALM-26238 RRU Network Topology Type and Configuration

Mismatch
Description
This alarm is reported when the user-configured RRU chain/ring topology is inconsistent with the actual RRU
285 de 526 13/11/2012 9:15

chain/ring topology.
Parameters
Inconsistency Type Type of inconsistency between topology and configuration (Chain Head
Configuration Error, Chain Tail Configuration Error, Dual-Star Configuration Error)
Configured Slot No. of RF Slot number of the RF interface board configured by the user
Interface Board
Configured Port No. of RF Port number of the RF interface board configured by the user
Interface Board
Actual Slot No. of RF Slot number of the RF interface board actually used
Interface Board
Actual Port No. of RF Port number of the RF interface board actually used
Interface Board
Major If the chain topology is configured but the ring topology is actually used, the reliability
of the RRU link decreases.
If the ring topology is configured but the chain topology is actually used, the RRU link
is not affected.
System Actions
None
Possible Causes
The user configures the RRU chain topology, but the RRU ring topology is actually used.
The user configures the RRU ring topology, but the RRU chain topology is actually used.
The topology configuration is consistent with the actual network (both are the ring topology), but
there is one (only one) configured port which is inconsistent with the actually used port.
In the dual-star topology, more than one RRU is connected to the RRU chain.
Procedure
26274 Inter-System Board Object Configuration Conflict
286 de 526 13/11/2012 9:15


2. Check the RRU chain/ring configuration on the M2000.
a. Run the MML command LST RRUCHAIN to check whether the configured RRU
networking mode and port settings are consistent with the site plan.
Y => The configured RRU networking mode and port settings are consistent with the
site plan. Go to step 3.
N => The configured RRU networking mode and port settings are inconsistent with the
site plan. Go to sub-step b.
b. In the case of the inconsistent networking mode, change the RRU networking mode.
In the case of the inconsistent port settings, run the MML command MOD RRUCHAIN
to modify the RRU chain/ring port settings according to the site plan.
3. Check the actual RRU networking mode on site.
a. Check whether the actual RRU networking mode and port settings are consistent with
the site plan.
Y => The actual RRU networking mode and port settings are consistent with the site
plan. Contact Huawei Customer Service Center.
N => The actual RRU networking mode and port settings are inconsistent with the site
b. Adjust the connections between RRUs and the peer device (upper- or lower-level RRU
or the BBU) according to the site plan. Ensure that the actual RRU networking mode
and port settings are consistent with the site plan.
1.1.151 ALM-26240 BBU Topology and Configuration Mismatch

Description
This alarm is reported when the user-configured inter-BBU connection topology is inconsistent with the actual
inter-BBU connection topology. This alarm is only reported by a 2U BBU.
Parameters
287 de 526 13/11/2012 9:15

Slot No. of the Upper-Level Board Slot number of the board connected to the BBU
Port No. of the Upper-Level Board Port number of the board connected to the BBU
Major If the BBUs are interconnected by UCIU+UCIU/UMPT, the BBUs cannot share
control data, clock signal, and transmission data. Services may be interrupted.
If the BBUs are interconnected by WBBPf+WBBPf, then:
The baseband data and signaling exchange between BBUs are affected.
Services are not provided on the side where this alarm is reported, or the service
processing capability decreases.
System Actions
None
Possible Causes
Data configuration is incorrect.
The optical inter-BBU connections are incorrect.
Procedure
a. Check for the correlated alarm on the inter-BBU interface of the UCIU on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
Y => The correlated alarm exists. Go to substep b.
2. Check the data configuration on the M2000.
a. Run the MML command LST CTRLLNK to query the UCIU topology configuration in the
local mode. Check whether the UCIU topology configuration is correct based on the
configuration plan. Alternatively, run the MML command LST BBPLNK to query the
configuration for the WBBPf+WBBPf interconnection topology. Check whether the
288 de 526 13/11/2012 9:15

topology configuration is correct based on the configuration plan.

Y => The topology configuration is correct. Go to step 3.
N => The topology configuration is incorrect. Go to substep b.
b. Run the MML command MOD CTRLLNK to modify the UCIU topology configuration in
the local mode, based on the configuration plan. Alternatively, run the MML command
MOD BBPLNK to modify the configuration for the WBBPf+WBBPf interconnection
topology.
3. Reconnect the inter-BBU cables onsite
a. Based on the alarm parameters, locate the port on the faulty UCIU and its
interconnected port on the upper-level board. Then, change the inter-BBU cable
connections on the port of the UCIU based on the configuration plan. Ensure that the
inter-BBU connection topology is consistent with the configuration plan.
1.1.152 ALM-26241 Configuration File Update Failure

Description
During the base station operation, the updated data configuration may fail to be saved in the configuration file.
This alarm is reported when the running data of a base station is inconsistent with the data in the configuration
file of the base station.
Parameters
None.
Major The updated data configuration fails to be saved in the configuration file. After the NE
resets, the updated data configuration is lost.
System Actions
None
Possible Causes
The flash or file system error occurs.
Procedure
1. Reset the main control board on the M2000.
a. Note: Resetting the main control board disrupts all the ongoing services of the base
289 de 526 13/11/2012 9:15

Run the MML command RST BRD to reset the main control board. Wait until the board
startup is complete.
b. Run the configuration command again. Check whether the alarm is reported again.
Y => The alarm persists. Go to step 2.
N => The alarm is cleared. No further action is required.
2. Replace the main control board on site.
b. Run the configuration command again. Check whether the alarm is reported again.
Y => The alarm persists. Contact Huawei Customer Service Center.
N => The alarm is cleared. No further action is required.
1.1.153 ALM-26242 Configuration File Damaged

Description
The system performs validity check on the configuration file in the case of startup. This alarm is reported when
the configuration file is invalid.
Parameters
None.
Major When the configuration file is invalid, part of or all the data configuration of the
system is lost. In this case, the NE may fail to carry services.
System Actions
None
Possible Causes
The main control board is reset improperly or is powered off. In this case, the flash or file system
error occurs, and the configuration file is damaged.
The current configuration file does not match the software version.
Procedure
1. Obtain the backup configuration file for data recovery on the M2000.
a. Obtain the correct configuration file from the OMC.
b. Run the MML command DLD CFGFILE to download the configuration file to the NE.
c. Run the MML command SET CFGFILEENB to enable the configuration file to take
effect immediately.
290 de 526 13/11/2012 9:15

Check whether the alarm is reported again.

Y => The alarm is reported again. Contact Huawei Customer Service Center.
N => The alarm is not reported. No further action is required.
1.1.154 ALM-26245 Configuration Data Inconsistency

Description
This alarm is reported when the running data of the NE is inconsistent with the user-configured data during the
data consistency check.
Parameters
Major The system cannot work with the latest data that is configured by the user.
System Actions
None
Possible Causes
The software is running improperly.
Procedure
2. Reset the main control board on the M2000.
1.1.155 ALM-26250 Active Workspace Version Unavailable

Description
291 de 526 13/11/2012 9:15

A base station has two storage spaces, which are active workspace and standby workspace. The active
workspace stores the running software version and the standby workspace stores the earlier software version.
This alarm is reported when the software version in the active workspace is incomplete, unrecognizable, or
empty in the case of the NE startup.
Parameters
None.
Major The NE cannot perform the software version check for boards and the board
software cannot be activated. If the board software mismatches the main control
software of the NE, the board cannot obtain the correct software version from the
active workspace. In this case, the board cannot carry services.
System Actions
None
Possible Causes
The memory for storing software in the active workspace is faulty.
Procedure
1. Check the software version in the standby workspace on the M2000.
a. Run the MML command LST SOFTWARE to check whether the software version in the
standby workspace is usable.
Y => The software version in the standby workspace is usable and is the currently
expected version. Go to sub-step b.
N => The software version in the standby workspace is unusable or is not the expected
version. Go to step 2.
b. Run the MML command ACT SOFTWARE to activate the NE software in the standby
workspace. Wait until the NE startup is complete.
2. Download and activate the NE software on the M2000.
a. Run the MML command DLD SOFTWARE to download the software package of the
same version as that in the site plan.
b. Run the MML command ACT SOFTWARE to activate the software package.
a. Note: Replacing the main control board interrupts all the ongoing services of the base
292 de 526 13/11/2012 9:15

1.1.156 ALM-26251 Board Type and Configuration Mismatch

Description
This alarm is reported when the actual board type in the slot is different from the configured board/sub-board
type.
Parameters
Board Hardware Type Hardware type of the faulty board
Configured Logical Type Configured logical type
Major Services cannot be carried on the board. The services of the peer mode are
System Actions
Possible Causes
An incorrect board is configured.
An incorrect board is installed in the slot.
Procedure
1. Check the board configuration on the M2000.
a. Run the MML command DSP BRD to check whether the type of the configured board
or RF unit in the slot is consistent with the configuration plan.
Y => The type of the configured board or RF unit is consistent with the configuration
plan. Go to step 2.
293 de 526 13/11/2012 9:15

N => The type of the configured board or RF unit is inconsistent with the configuration
b. Check whether the hardware type of the faulty board is a RF unit according to the
alarm detailed information on the M2000.
Y => The hardware type of the faulty board is a RF unit. Go to sub-step e.
N => The hardware type of the faulty board is not a RF unit. Go to sub-step c.
c. Run the MML command RMV BRD to remove the configured board in the slot.
d. Run the MML command ADD BRD to configure the correct board in the slot according
e. Run the MML command RMV RRU to remove the configured RF unit in the slot.
f. Run the MML command ADD RRU to configure the correct RF unit in the slot according
2. Check the configured sub-board type on the M2000.
a. Based on the alarm detailed information, check whether the board type is the UTRP.
Y => The board type is the UTRP. Go to sub-step b.
N => The board type is not the UTRP. Go to step 3.
b. Run the MML command DSP BRD to query the sub-board type. Check whether the
configured sub-board is consistent with the installed sub-board.
Y => The configured sub-board is consistent with the installed sub-board. Go to step 3.
N => The configured sub-board is inconsistent with the installed sub-board. Go to
sub-step c.
c. Run the MML command ADD BRD to change the sub-board type according to the
installed sub-board type.
3. Replace the board on site.
a. Based on the configured board type, replace the board.

1.1.157 ALM-26253 Board Software Auto-Supply Failure

Description
This alarm is reported when the system detects a new board type but the matching board software is
294 de 526 13/11/2012 9:15

unavailable in the active workspace and the software auto-supply from the M2000 fails.
Parameters
Major Services cannot be carried on the board.
System Actions
None
Possible Causes
The board type has never been configured earlier or the file system of the base station is damaged,
and the communication between the NE and the M2000 fails.
The software to be supplemented is unavailable on the M2000.
Procedure
1. Check the maintenance link for the NE on the M2000.

301 NE Is Disconnected

2. Manually start the software auto-supply for the NE on the M2000.
a. Check whether the software to be supplemented is available on the M2000.

Y => The software to be supplemented is available on the M2000. Go to sub-step b.
N => The software to be supplemented is unavailable on the M2000. Store the software
to be supplemented on the M2000 and then go to sub-step b.
b. Run the MML command SPL SOFTWARE to start the software auto-supply for the NE.
Wait until the process is complete.
295 de 526 13/11/2012 9:15

1.1.158 ALM-26254 Board Software Synchronization Failure

Description
This alarm is reported when the base station detects that the board software mismatches the base station
software, and the automatic version synchronization fails.
Parameters
Parameter
Possible Possible cause of the activation failure (Board BootROM Incompatible with Software Version
Cause to be Activated, Board Flash Available Space Insufficient, Other Internal Errors)
Major Services cannot be carried on the board.
System Actions
None
Possible Causes
The board software upgrade fails during the NE software upgrade. In this case, the board BootROM
upgrade fails.
The available flash memory of the board is insufficient.

Procedure
If "Specific Problem" is "Board BootROM Incompatible with Software Version to be
Activated", go to step 2.
If "Specific Problem" is "Board Flash Available Space Insufficient", go to step 4.
If "Specific Problem" is "Other Internal Errors", go to step 3.
2. Upgrade the board BootROM version manually on the M2000.
a. Run the MML command DLD SOFTWARE to manually download the board BootROM
version. Select "BootROM" in the software type field.
b. Run the MML command ACT SOFTWARE to manually activate the board BootROM
version. Select "BootROM" in the software type field.
296 de 526 13/11/2012 9:15

c. Run the MML command RST BRD to reset the board. Wait until the board startup is
complete.
3. Activate the board software on the M2000.
a. Run the MML command ACT SOFTWARE to activate the board software. Select
"Software" in the software type field. Wait until the board startup is complete.

Service Center.
1.1.159 ALM-26255 Automatic Version Rollback

Description
This alarm is reported when the automatic version rollback occurs in the case that the current version is
improper.
Parameters
None.
Major Version rollback leads to NE reset. During the reset, the ongoing services carried on
the NE are disrupted.
System Actions
None
Possible Causes
The target software version is incorrect.
The target software version does not support a smooth upgrade.

The OM link is abnormal after the upgrade.
Procedure
1. Check the target software version.
297 de 526 13/11/2012 9:15

a. Check whether the target software version is correct.

Y => The target software version is correct. Go to sub-step 2.
N => The target software version is incorrect. Go to sub-step b.
b. Choose a correct target software version.
Go to sub-step 4.
2. Verify that the target software version supports a smooth upgrade.
a. Check whether the target software version supports a smooth upgrade.

Y => The target software version supports a smooth upgrade. Go to sub-step 3.
N => The target software version does not support a smooth upgrade. Go to sub-step
b.
b. Change the target software version to one that supports a smooth upgrade.
Go to sub-step 4.
3. Check the OM link.
a. Check whether the OM link works properly after the upgrade.

Y => The OM link works properly. Contact Huawei Customer Service Center.
N => The OM link does not work properly. Go to sub-step b.
b. Perform the software upgrade for the NE.
4. Evaluate the significance of software upgrade.
a. Check whether the software upgrade is required.

Y => The software upgrade is required. Go to sub-step b.
N => The software upgrade is not required. Go to sub-step c.
b. Perform the software upgrade for the NE.
c. Clear the alarm manually.
1.1.160 ALM-26260 System Clock Failure

Description
This alarm is reported when the base station uses the local crystal oscillator longer than its duration limit (90
days).
Parameters
None.
Major The quality of services of the base station decreases, resulting in handover failure
and call drop. In certain cases, the base station cannot provide services.
System Actions
None
298 de 526 13/11/2012 9:15

Possible Causes
The clock reference is not configured.
The clock reference malfunctions.
The board hardware malfunctions.
Procedure

26261 External Clock Reference Not Configured
1.1.161 ALM-26261 External Clock Reference Not Configured

Description
This alarm is reported when the external clock reference for the base station is not configured.
Parameters
None.
Minor The system clock may be unusable if the base station does not obtain the clock
reference for a long period of time. As a result, the quality of services of the base
station decreases, resulting in handover failure and call drop. In certain cases, the
base station cannot provide services.
System Actions
None
Possible Causes
The external clock reference is not configured for the base station.
Procedure
1. Add the external clock reference for the base station on the M2000.
a. Run the MML command ADD GPS/ADD IPCLKLINK/ADD SYNCETH/ADD

LINECLK/ADD BITS/ADD PEERCLK to add the external clock reference for the base
299 de 526 13/11/2012 9:15

station according to the site plan.

Check Whether the Alarm is Cleared:
1.1.162 ALM-26262 External Clock Reference Problem

Description
This alarm is reported in the case of clock reference loss, external clock reference unavailability due to
unacceptable quality, excessive frequency deviation between the clock reference and the local oscillator, or
unstable frequency of the clock reference.
Parameters
Parameter
Specific Specific Problem of the alarm(Clock Reference Lost, Clock Reference Unavailable, Excessive
Problem Frequency Difference Between Clock Reference and Local Crystal Oscillator, Excessive
Frequency Variation of Clock Reference, Excessive Phase Difference Between Clock Reference
and Local Crystal Oscillator, Inconsistent Clock References, IPCLK Reference Unavailable due
to Unacceptable Quality, SYNCETH Clock Reference Unavailable due to Unacceptable Quality,
GPS Clock Reference Unavailable due to Unacceptable Quality, TOD Clock Reference
Unavailable due to Unacceptable Quality)
Minor The base station fails to synchronize to the clock reference. The system clock may
be unusable if the base station does not obtain the clock reference for a long period
of time. As a result, the quality of services of the base station decreases, resulting in
services.
System Actions
None
Possible Causes
If the clock reference is GPS clock, the GPS antenna may be faulty or the number of locked GPS
satellites may be insufficient.
The clock reference is incorrectly configured.
If the clock reference is IPCLK, the IP clock link may fail.

If the clock reference is line clock, the transmission link between the base station and the clock
reference may fail, or the frequency deviation between the clock reference and the local clock may
be excessively large.
The hardware of the UTRP, USCU, or main control board is faulty.
The clock reference is unavailable due to unacceptable quality.

The frequency of the clock reference is unstable.
300 de 526 13/11/2012 9:15

Procedure
1. Check for this alarm on the M2000.
a. Check whether this alarm is reported on a large number of base stations on the M2000.
Y => This alarm is reported on a large number of base stations due to poor
transmission quality or faulty clock source. Go to sub-step b.
N => This alarm is reported only on a few base stations. Go to step 2.
b. Obtain the clock topology, and check the clock transmission link, clock configuration, or
clock source as indicated by the possible alarm cause.
Wait 5 to 120 minutes. Check whether the alarm is cleared.
N => The alarm is not cleared. Go to step 2
a. Check for the correlated alarm of the faulty clock board or port on the M2000.
26122 GPS Locked Satellites Insufficient
26120 GPS Clock Output Unavailable
26123 GPS Maintenance Link Failure
26263 IP Clock Link Failure
25800 E1/T1 Loss of Signal
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault

Wait for 5 to 120 minutes. Check whether the alarm is cleared.
3. Check the clock reference on the basis of configuration plan on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference is
consistent with the configuration plan.
Y => The clock reference is consistent with the configuration plan. Go to step 4.
N => The clock reference is inconsistent with the configuration plan. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference according to
the configuration plan.
301 de 526 13/11/2012 9:15

a. Locate the cause of the alarm based on the alarm location information.
If "Specific Problem" is "IPCLK Reference Unavailable due to Unacceptable Quality", go
to step 5.
If "Specific Problem" is "Excessive Frequency Difference Between Clock Reference and
Local Crystal Oscillator" or unstable frequency of the clock reference, go to step 6.
.
If "Specific Problem" is "SYNCETH Clock Reference Unavailable due to Unacceptable
Quality", check the quality of synchronous Ethernet clock signals extracted from the
upper-level network node.
If "Specific Problem" is "GPS Clock Reference Unavailable due to Unacceptable
Quality", check the status of GPS equipment or the environment.
If "Specific Problem" is "TOD Clock Reference Unavailable due to Unacceptable
Quality", check the quality of TOD clock signals.
If "Specific Problem" is not one of the preceding causes, Contact Huawei Customer
Service Center.
5. Handle the unavailable IP clock reference problem.
a. Contact maintenance personnel of the IP Clock server to solve the unavailable IP clock
reference problem so that the IP clock reference quality meets the requirements of the
base station.
6. Handle the link clock fault caused by transmission link failures.
a. Contact maintenance personnel of transport equipment to restore the transmission link

and hence solve the fault.
1.1.163 ALM-26263 IP Clock Link Failure

Description
This alarm is reported when the IP clock link connected to the clock server fails.
Parameters
Link No. Link number of the faulty IP clock
302 de 526 13/11/2012 9:15

Minor The base station fails to synchronize to the IP clock reference. The system clock
may be unusable if the base station does not obtain the clock reference for a long
period of time. As a result, the quality of services of the base station decreases,
resulting in handover failure and call drop. In certain cases, the base station cannot
provide services.
System Actions
None
Possible Causes
The port used for the IP clock link is faulty.
The IPCLK link is incorrectly configured.

The route from the NE to the clock server is not configured.
The route from the NE to the clock server is not reachable.
The main control board hardware is faulty.
Procedure
a. Check for the correlated alarm of the port that bears the IPCLK link on the M2000.
26220 Transmission Optical Module Fault
26221 Transmission Optical Module Not In Position
26222 Transmission Optical Interface Error
26223 Transmission Optical Interface Performance Degraded

2. Check the IPCLK configuration on the M2000.
a. Run the MML command LST IPCLKLINK to check whether the IP address of the clock
server and the IPCLK type are consistent with the network plan.
Y => The IP address of the clock server and the IPCLK type are consistent with the
network plan. Go to step 3.
N => The IP address of the clock server and the IPCLK type are inconsistent with the
network plan. Go to sub-step b.
303 de 526 13/11/2012 9:15

b. Run the MML command RMV IPCLKLINK/ADD IPCLKLINK to change the configuration
of IPCLK link.
3. Check the configuration of route from the NE to the clock server on the M2000.
a. Run the MML command LST IPRT to query all the current routes. Check whether an IP
route connecting the peer clock server exists.
Y => There is an IP route connecting the peer clock server. Go to step 4.
N => There is no IP route connecting the peer clock server. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route connecting the peer clock server.
Then, wait for at least five minutes.
4. Check the reachability of route from the NE to the clock server on the M2000.
a. Run the MML command PING to check whether the route from the NE to the clock
server is reachable.
Y => The route is reachable. Go to sub-step d.
N => The route is not reachable. Go to sub-step b.
b. Contact the maintenance engineer responsible for the clock server to rectify the fault on
the clock server.
c. Contact the maintenance engineer responsible for the routing device to rectify the route
fault.
d. Contact the maintenance engineer responsible for the clock server to troubleshoot the
improper processes of the clock server.
1.1.164 ALM-26264 System Clock Unlocked

Description
This alarm is reported when a clock phase-locked loop in the board is unlocked.
Parameters
304 de 526 13/11/2012 9:15

Parameter
Specific Specific Problem of the alarm(Software Phase Lock Loop Loss of Lock, Hardware Phase
Problem Lock Loop Loss of Lock)
Minor The system clock fails after a certain period (around 90 days). The ongoing services
carried on the board are disrupted.
Major The system clock fails. The ongoing services carried on the board are disrupted.
System Actions
None
Possible Causes
The clock reference malfunctions.
The clock reference is not configured.
The main control board hardware is faulty.
If this alarm is reported on a non-main control board, the board may not be securely installed.
Procedure

26261 External Clock Reference Not Configured


305 de 526 13/11/2012 9:15


4. Replace the faulty board.

Service Center.
1.1.165 ALM-26265 Base Station Frame Number Synchronization Error

Description
This alarm is reported when the frame number received on the board for synchronization has errors.
Parameters
Major The ongoing services carried on the board are disrupted.
System Actions
None
Possible Causes
The system clock phase-locked loop in the main control board is unlocked.
This board is not securely installed.

Procedure
a. Check for the correlated alarm of the faulty board or main control board on the M2000:
26264 System Clock Unlocked
306 de 526 13/11/2012 9:15





Service Center.
1.1.166 ALM-26266 Time Synchronization Failure

Description
This alarm is reported when the time synchronization between the NE and the time synchronization server fails.
Parameters
Time Source Type Faulty time source type (NTP, GPS)
Minor The time of the base station fails to synchronize with the time of the M2000. As a
result, the time the base station reports alarms and logs is different from the time of
the M2000 and therefore inventory information on the M2000 cannot be automatically
updated, possibly leading to unreliable traffic statistics.
System Actions
None
307 de 526 13/11/2012 9:15

Possible Causes
The transmission port connected to the SNTP/NTP server is faulty.
The time reference is incorrectly configured.
The parameter settings on the SNTP/NTP client are incorrect.
The route from the NE to the SNTP/NTP server is not configured or is not reachable.
The SNTP/NTP server is not in service.

The GPS antenna is faulty.
The number of locked GPS satellites is insufficient.
Procedure
a. Check for the correlated alarm of the port used for time synchronization on the M2000.
26122 GPS Locked Satellites Insufficient
26120 GPS Clock Output Unavailable
26123 GPS Maintenance Link Failure
25800 E1/T1 Loss of Signal
25806 E1/T1 Excessive Bit Error Rate
2. Check the configuration of time reference on the basis of the configuration plan on the M2000.
a. Run the MML command LST TIMESRC to check whether the configuration of time
reference is consistent with the configuration plan.
Y => The configuration of time reference is consistent with the configuration plan. Go to
step 3.
N => The configuration of time reference is inconsistent with the configuration plan. Go
to sub-step b.
b. Run the MML command SET TIMESRC to change the configuration of time reference.
308 de 526 13/11/2012 9:15

3. Check the parameter settings on the NTP/SNTP server on the M2000.
a. Run the MML command LST SNTPCLTPARA to check whether the IP address and
port No. of the NTP/SNTP server are consistent with the network plan.
Y => The parameter settings are consistent. Go to sub-step c.
N => The parameter settings are inconsistent. Go to sub-step b.
b. Run the MML command SET SNTPCLTPARAto change the IP address and port No. of
the NTP/SNTP server.
c. Run the MML command LST SNTPCLTPARA to check whether the NTP/SNTP
synchronization service is started.
Y => The NTP/SNTP synchronization service is started. Go to step 4.
N => The NTP/SNTP synchronization service is not started. Go to sub-step d.
d. Run the MML command SET SNTPCLTPARA to start the NTP/SNTP synchronization
service.
4. Check the configuration of route from the NE to the NTP/SNTP server on the M2000.
a. Run the MML command LST IPRT to query all the current routes.
Check whether an IP route connecting the SNTP/NTP server exists.
Y => There is an IP route connecting the SNTP/NTP server. Go to step 5.
N => There is no IP route connecting the SNTP/NTP server. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route connecting the NTP/SNTP
server.
5. Check the reachability of route from the NE to the NTP/SNTP server on the M2000.
a. Run the MML command PING to check whether the NTP/SNTP server can be
connected.
Y => The NTP/SNTP server can be connected. Go to sub-step d.
N => The NTP/SNTP server cannot be connected. Go to sub-step b.
b. Contact the maintenance engineer responsible for the NTP/SNTP server to rectify the
fault on the NTP/SNTP server.
c. Contact the maintenance engineer responsible for the routing device to rectify the route
fault.
309 de 526 13/11/2012 9:15


d. Contact the maintenance engineer responsible for the NTP/SNTP server to troubleshoot
the improper processes of the NTP/SNTP server.
1.1.167 ALM-26270 Inter-System Communication Failure

Description
The main control boards in different modes of a multi-mode base station periodically exchange control
information. If the main control board in one mode does not receive any handshake response message from its
counterpart within about 45s, this alarm is reported This alarm is cleared when the main control board in one
mode successfully receives a handshake response message from its counterpart within about 30s.
Parameters
Parameter
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Major The consistency check cannot be performed for inter-RAT configuration. Common
alarms cannot be identified, affecting alarm monitoring.
System Actions
None
Possible Causes
The base station in the other mode is repeatedly reset because the connection between the base
station and the base station controller or M2000 is disrupted for a long time.
The base station in the other mode is repeatedly reset because the base station is installed but not
configured.
The base station in the other mode is reset after a software upgrade or after a reset command is
issued.
The main control board of the other mode is running improperly.
The main control board of the current mode is running improperly.

The main control board of the other mode is not installed securely.
The main control board of the current mode is not installed securely.
The hardware of the main control board of the other mode is faulty.
The hardware of the main control board of the current mode is faulty.
310 de 526 13/11/2012 9:15

Procedure
1. Check for the correlated alarms on the M2000.
a. Check whether any of the following alarms on the faulty port of the BBU on the M2000:
26315 Inter-BBU Port Connection Error
N => A correlated alarm is not reported. Go to step 2.

2. Check the status of the main control board in the other mode on the M2000.
a. Click Device Panel on the M2000, and check whether the status of the main control
board in the other mode is normal.
Y => The status of the main control board in the other mode is normal. Go to step 3.
N => The status of the main control board in the other mode is abnormal. Go to
sub-step b.
b. Wait 5 minutes. Check whether the alarm is cleared.
3. Reset the main control board of the current mode on the M2000.
Run the MML command RST BRD to reset the main control board of the current mode.
Wait until the board startup is complete.
4. Reset the main control board of the other mode on the M2000.
Run the MML command RST BRD to reset the main control board of the other mode.
Wait until the board startup is complete.
311 de 526 13/11/2012 9:15


5. Reseat the main control board of the current mode on site.
6. Reseat the main control board of the other mode on site.
7. Replace the main control board of the current mode on site.
8. Replace the main control board of the other mode on site.
1.1.168 ALM-26271 Inter-System Monitoring Device Parameter Settings

Conflict
Description
In multi-mode configuration, this alarm is reported when the parameter settings of a monitoring device in a mode
are inconsistent with those of the same monitoring device in the other mode.
312 de 526 13/11/2012 9:15

Parameters
Parameter
Configuration Configuration item (Alarm Suppression/Enabling Settings, EMU Configuration Parameter

Item Settings, Output Port Status Settings, Standby Analog Sensor Configuration, Boolean Alarm
Level Configuration, Power System Controlling Parameter Settings, Battery Management
Parameter Settings, Battery Group Temperature Compensation Parameter Settings, Power
Module Parameter Settings, Environment Parameter Settings, Standby Parameter Settings,
High-Temperature Shutdown Protection Parameter Settings, Battery Group Capacity Detection
Parameter Settings, Voltage Measurement Reference Settings, Power Distribution Analog
Calibration Coefficient Settings, Alarm Severity Settings, Battery Auto-Test Parameter Settings,
Power System Parameter Settings, PSU Intelligent Shutdown Parameter Settings, Battery
Intelligent Management Parameter Settings, Board Speed Regulation Settings, Speed
Regulation Message Delivery, High/Low Temperature Alarm Threshold Settings, Heater
Controlling Parameter Settings, Temperature Control Parameter Settings in the Temperature
Control System, Speed Regulation Settings, Speed Regulation Message Settings, High/Low
Temperature Alarm Threshold Settings of Air Inlet, Speed Regulation Controlling Parameter
Settings, Environmental Alarm Suppression/Enabling Settings)
Warning The parameter settings of a monitoring device in a mode are incorrect. In this case,
the related data configuration may not take effect in this mode, and alarms may be
falsely reported.
System Actions
None
Possible Causes
The parameter settings of a monitoring device in a mode are incorrect.
Procedure
1. Check the parameter settings of the monitoring device in two modes on the Configuration
Management Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty monitoring device.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the monitoring device in two modes according to the configuration
plan. Ensure the parameter consistency in two modes.
313 de 526 13/11/2012 9:15


1.1.169 ALM-26272 Inter-System RF Unit Parameter Settings Conflict

Description
In multi-mode configuration, this alarm is reported when the parameter settings of an RF unit in a mode are
inconsistent with those of the same RF unit in the other mode, such as the working mode or other RF
parameters.
Parameters
Parameter
Configuration Configuration item (IF Offset, TX Gain, AGC Flag, DPD Flag, PAR Flag, CPRI Port
Item Configuration, SEM Enabling Flag, Receive Desensitivity, RTWP Correction Value, RF
Desensitivity, Delay Compensation, T1/L Timing Delay Compensation, VSWR Alarm Threshold,
Attenuation, ALD Current Threshold, VSWR Threshold, External Boolean Alarm Port, Alarm
Parameters, Radio Interconnection Mode, Topology Type, RF Unit Working Mode Conflict)
Board Type Type of the faulty RF unit
Unknown)
Major If the configured working mode of an RF unit in one mode is inconsistent with that of
the same RF unit in the other mode, the software management of the RF unit is
affected. In this case, the ongoing services carried on the RF unit may be affected.
If other parameters of an RF unit in one mode are inconsistent with those of the
same RF unit in the other mode, the data configuration of the RF unit in one mode
cannot take effect. In this case, problems may occur.
Warning If other parameters of an RF unit in one mode are inconsistent with those of the
same RF unit in the other mode, the data configuration of the RF unit in one mode
cannot take effect. In this case, problems may occur.
System Actions
If the configured working mode of an RF unit in one mode is inconsistent with that of the same RF unit in the
other mode, the system does not load the board software of the RF unit.
Possible Causes
The working mode of an RF unit is incorrectly configured in one mode.
The parameters of an RF unit in one mode are inconsistent with those of the same RF unit in the
314 de 526 13/11/2012 9:15

other mode.
Procedure
1. Check for inconsistent settings of RF unit parameters on the M2000.
a. Check the value of the "Configuration Item" parameter in the alarm information.
If the value of "Configuration Item" is "Radio Interconnection Mode", go to substep b.
If the value of "Configuration Item" is not "Radio Interconnection Mode", go to step 2.
b. Run the LST BTSRXUBP command on the GSM side to query the TX/RX mode of the
faulty RF unit. If the TX/RX mode is "Single Feeder(1TX + 2RX)", the RF unit is
interconnected with another RF unit.
Run the LST SEC command on the UMTS side to query the interconnection mode of the
faulty RF unit. If the value of "RF Interconnection Mode" is "TRUE", the RF unit is
interconnected with another RF unit.
c. Check whether the settings of the RF unit interconnection mode are consistent between
the GSM and UMTS sides.
Y => The settings are consistent. Contact Huawei Customer Service Center.
N => The settings are inconsistent. Go to substep d.
d. Run the SET BTSRXUBP command on the GSM side to change the TX/RX mode of the
faulty RF unit to the value specified in the configuration plan.
Run the RMV SEC and ADD SEC commands on the UMTS side to change the
interconnection mode of the faulty RF unit to the value specified in the configuration
plan.
2. Check the parameter settings of the RF unit in two modes on the Configuration Management
Express (CME).
CME help. Check for the error(s) corresponding to the faulty RF unit.
parameter settings of the RF unit in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
1.1.170 ALM-26273 Inter-System BBU Board Parameter Settings Conflict

Description
In multi-mode configuration, this alarm is reported when the parameter settings of boards in a BBU in a mode
are inconsistent with those in the same BBU in the other mode.
Parameters
315 de 526 13/11/2012 9:15

Parameter
Configuration Configuration item (Dry Contact Alarm Level Conflict, GPS Parameters Conflict,
Item Convergency topology Conflict)
Warning If the configuration of dry contacts for the UPEU/UEIU in two modes is inconsistent,
alarms are falsely reported on the mode with wrong configuration.
If the GPS configuration for the USCU in two modes is inconsistent, the data
configuration on one mode cannot take effect.
Major If the networking configuration of the RF units is inconsistent between the two
modes, the multi-mode RF units cannot work properly.
System Actions
None
Possible Causes
The configuration of dry contacts for the UPEU/UEIU in a mode is inconsistent with that in the other
mode.
The GPS configuration for the USCU in a mode is inconsistent with that in the other mode.
The networking configuration of the RF units is inconsistent between the two modes.
Procedure
1. Check the parameter settings of the board in two modes on the Configuration Management Express
(CME).
CME help. Check for the error(s) corresponding to the faulty board.
parameter settings of the board in two modes according to the configuration plan.
1.1.171 ALM-26274 Inter-System Board Object Configuration Conflict

Description
316 de 526 13/11/2012 9:15

In multi-mode configuration, this alarm is reported when the cabinet/subrack/slot configuration of a board is
inconsistent in different modes, when the cabinet/subrack/slot configuration of different boards is the same in
different modes, or when a board supporting only a certain mode is configured for different modes.
Parameters
Parameter
Unknown)
Peer Cabinet Cabinet number of the faulty board in the peer working mode
No.
Peer Subrack Subrack number of the faulty board in the peer working mode
No.
Peer Slot No. Slot number of the faulty board in the peer working mode
Specific Specific Problem of the alarm(Cabinet/Subrack/Slot Configuration Inconsistency on One Board,

Problem Cabinet/Subrack/Slot Configuration Conflict for Different Boards, Duplicate Configuration on
One Board)
Major The board with configuration conflict cannot be maintained in the way that a common
board is handled. In this case, the inventory information error occurs. For the RF
units, the automatic software update fails in the case of software upgrades. In this
case, the ongoing services carried on the RF units are disrupted. When a board
supporting only one mode is configured for different modes, the board fails to work
normally.
System Actions
None
Possible Causes
When this alarm is reported on a monitoring board, the possible causes are as follows: Incorrect
cabinet, subrack, or slot number. Incorrect cabinet or subrack number of the device managing the
monitoring device. Incorrect serial port number. Incorrect communication IP address. When this
alarm is reported on other boards, the possible causes are that the cabinet, subrack, or slot number
of the board is incorrect.
A board supporting only a certain mode is configured for different modes.
Procedure
317 de 526 13/11/2012 9:15

If "Specific Problem" is "Duplicate Configuration on One Board", go to step 2.

If "Specific Problem" is "Cabinet/Subrack/Slot Configuration Inconsistency on One
Board" or "Cabinet/Subrack/Slot Configuration Conflict for Different Boards", go to step
3.
2. Remove the configured board on the M2000.
a. Run the MML command RMV BRD to remove the board in a mode based on the
configuration plan.
3. Locate the board type of the alarm on the M2000.
a. Locate the board type of the alarm based on the alarm location information.
If "Board Type" is a board of BBU, go to step 4.
If "Board Type" is RRU, go to step 6.
If "Board Type" is a monitoring device, go to step 8.
4. Check the board configuration in the current mode on the M2000.
a. Run the MML command DSP BRD to check whether the cabinet/subrack/slot
configuration of the faulty board in the current mode is correct according to the
configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Go to step 5.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
b. Run the MML command RMV BRD to remove the board in the current mode.
c. Run the MML command ADD BRD to add the board in the current mode. Set the
cabinet/subrack/slot of the board according to the configuration plan.
5. Check the board configuration in the other mode on the M2000.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty board
in the other mode is correct according to the configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Contact Huawei Customer
Service Center.
b. Remove the board in the other mode on the M2000.
c. Add the board in the other mode on the M2000. Set the cabinet/subrack/slot of the
board according to the configuration plan.
6. Check the RRU configuration in the current mode on the M2000.
318 de 526 13/11/2012 9:15

a. Run the MML command LST RRU to check whether the cabinet/subrack/slot
configuration of the faulty RRU in the current mode is correct according to the
configuration plan.
b. Run the MML command RMV RRU to remove the RRU in the current mode.
c. Run the MML command ADD RRU to add the RRU in the current mode. Set the
7. Check the RRU configuration in the other mode on the M2000.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty RRU
in the other mode is correct according to the configuration plan.
Service Center.
b. Remove the RRU in the other mode on the M2000.

c. Add the RRU in the other mode on the M2000. Set the cabinet/subrack/slot of the
board according to the configuration plan.
8. Check the monitoring device configuration in the current mode on the M2000.
a. Run the MML command LST PMU(PMU)/LST TCU(TCU)/LST EMU(EMU)/LST

FMU(FMU) to check whether the cabinet/subrack/slot configuration of the faulty
monitoring device in the current mode is correct according to the configuration plan.

FMU(FMU) to remove the monitoring device in the current mode.
c. Run the MML command ADD PMU(PMU)/ADD TCU(TCU)/ADD EMU(EMU)/ADD

FMU(FMU) to add the monitoring device in the current mode. Set the
9. Check the monitoring device configuration in the other mode on the M2000.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty

monitoring device in the other mode is correct according to the configuration plan.
Service Center.
319 de 526 13/11/2012 9:15

b. Remove the monitoring device in the other mode on the M2000.
c. Add the monitoring device in the other mode on the M2000. Set the cabinet/subrack/slot
of the board according to the configuration plan.
1.1.172 ALM-26275 Inter-System Cabinet Configuration Conflict

Description
In a multi-mode base station, this alarm is reported when the cabinet configuration of one mode is inconsistent
with that of the other mode, such as the cabinet type.
Parameters
Configuration Configuration item (Cabinet Type Configuration Conflict)

Item
Unknown)
Minor The cabinet type in different modes conflicts, which affects the configuration,
maintenance of the cabinet, as well as the inventory information recording.
System Actions
None
Possible Causes
In a multi-mode base station, the cabinet type of one mode is incorrectly configured.
Procedure
1. Check the cabinet configuration in two modes on the Configuration Management Express (CME).
CME help. Check for the error(s) corresponding to the faulty cabinet.
parameter settings of the cabinet in two modes according to the configuration plan.
320 de 526 13/11/2012 9:15

1.1.173 ALM-26276 Inter-System Site-Level Configuration Conflict

Description
In multi-mode configuration, this alarm is reported when the site-level configuration in a mode conflicts with that
in the other mode. The site-level configuration includes the clock reference type and deployment ID (DID).
Parameters
Parameter
Configuration Configuration item (Clock Reference Type Configuration Conflict, DeployMent Id

Item Configuration Conflict)
Unknown)
Major When the clock source type configured for a mode is incorrect, the clock source in
the mode is unavailable. In this case, the system clock works in free-run mode.
Services are not affected during a short period (three months).
When the DID configured for a mode is incorrect, users cannot manage the mode by
DID.
System Actions
None
Possible Causes
The clock reference type of a mode is incorrect.
The DID of a mode is incorrect.
Procedure
1. Check the alarm cause on the M2000.
a. Check the cause of the alarm based on the alarm location information.
If the alarm is caused by a clock reference type configuration conflict, go to step 2.
If the alarm is caused by a DID configuration conflict, go to step 4.
2. Check the clock reference type of the local mode on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference type of
the local mode is correct according to the site plan.
Y => The clock reference type of the local mode is correct. Go to step 2.
N => The clock reference type of the local mode is incorrect. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference type of the
local mode according to the site plan.
321 de 526 13/11/2012 9:15


3. Check the clock reference type of the other mode on the M2000.
a. Check whether the clock reference type of the other mode is correct according to the
site plan.
Y => The clock reference type of the other mode is correct. Contact Huawei Customer
Service Center.
N => The clock reference type of the other mode is incorrect. Go to sub-step b.
b. Change the clock reference type of the other mode according to the site plan.
4. Check the DID of the local mode on the M2000.
a. Run the MML command LST EQUIPMENT to check whether the DID of the local mode
is correct according to the site plan.
Y => The DID of the local mode is correct. Go to step 5.
N => The DID of the local mode is incorrect. Go to sub-step b.
b. Run the MML command SET EQUIPMENT to change the DID of the local mode
according to the site plan.
5. Check the DID of the other mode on the M2000.
a. Check whether the DID of the other mode is correct according to the site plan.
Y => The DID of the other mode is correct. Contact Huawei Customer Service Center.
N => The DID of the other mode is incorrect. Go to sub-step b.
b. Change the DID of the other mode according to the site plan.
1.1.174 ALM-26277 Inter-System Control Rights Conflict

Description
In multi-mode configuration, this alarm is reported when the loading control rights are not configured or
inconsistent between different modes in the base station.
Parameters
Parameter
322 de 526 13/11/2012 9:15

Unknown)
Major When the loading control rights conflict, the software version of the USCU and the
shared RF units between different modes may be wrong. In this case, some
functions of the multi-mode base station fail and the reliability decreases.
System Actions
None
Possible Causes
The loading control rights are not configured after the multi-mode base station is deployed.
The loading control rights are not configured after the main control board is replaced in the
multi-mode base station.
The loading control rights are inconsistent between the current mode and the other mode.
Procedure
1. Set the loading control rights on the M2000.
a. Note: Before you set the loading control rights, query the software version of the
multi-mode base station and specify the loading control rights by referring to the
upgrade guide. The MML command should be executed in the mode requiring the
loading control rights and with the parameter EFTIMMFLAG set to YES (becoming
effective immediately).
In the mode requiring the loading control rights, run the MML command SET
LOADCTRL to set the loading control rights in the multi-mode base station.
1.1.175 ALM-26278 RF Unit Working Mode and Mode Capability

Inconsistency
Description
In multi-mode configuration, this alarm is reported when the configured working mode of an RF unit mismatches
the actual capability of the RF unit.
Parameters
323 de 526 13/11/2012 9:15

RF Unit Working RF unit working mode (UO, GO, CO, WO, LO, TDLO, TDSO, GU, UL, GL, CL, TL,
Mode WL, GUL, CU)
RF Unit Mode RF unit mode capability (UO, GO, CO, WO, LO, TDLO, TDSO, GU, UL, GL, CL, TL,
Capability WL, GUL, CU)
Major The ongoing services carried on the RF unit are disrupted.
System Actions
None
Possible Causes
The working mode of the RF unit is incorrectly configured in the system.

The model of the installed RF unit is incorrect.
Procedure
1. Check the configured working mode of the RF unit on the M2000.
a. Run the MML command LST RRU/DSP RRUCHAINPHYTOPO to check whether the
working mode of the faulty RF unit is correct according to the site plan.
Y => The working mode is correct. Go to step 2.
N => The working mode is incorrect. Go to sub-step b.
b. Run the MML command MOD RRU to change the working mode of the faulty RF unit
according to the site plan.
a. Replace the RF unit. Ensure that the actual capability of the new RF unit is consistent
with the configured working mode.
1.1.176 ALM-26279 Inter-System Board Installation and Configuration

Mismatch
Description
In multi-mode configuration, this alarm is reported when the cabinet/subrack number of two main control boards
in the same BBU is different, or when the cabinet/subrack number of a main control board of one mode is the
same as that of the other mode in a different BBU.
Parameters
324 de 526 13/11/2012 9:15

Peer Cabinet No. Cabinet number of the faulty board in the peer working mode
Peer Subrack No. Subrack number of the faulty board in the peer working mode
Peer Slot No. Slot number of the faulty board in the peer working mode
Minor The BBU subrack and the boards in the BBU are displayed in disorder on the M2000.
In addition, the inventory information record is in disorder.
System Actions
None
Possible Causes
In a multi-mode base station, the cabinet/subrack number of a main control board of a mode is
incorrectly configured.
In a multi-mode base station, the installed position of a main control board of a mode is incorrect.
Procedure
1. Check the cabinet/subrack number of the BBU of each mode on the M2000.
a. Run the MML command DSP BRD to query the board configuration.
Check whether the cabinet/subrack number of the main control board of each mode is
correctly configured, according to the configuration plan.
Y => The cabinet/subrack number is correct. Go to step 2.
N => The cabinet/subrack number is incorrect. Go to sub-step b.
b. Run the MML command RMV BRD to delete the board that is incorrectly configured.
c. Run the MML command ADD BRD to add the board and set its cabinet/subrack/slot
number according to the configuration plan.
Ensure that the cabinet/subrack number of two main control boards in the same BBU is
the same, and the cabinet/subrack number of a main control board of one mode is
different from that of the other mode in a different BBU.
2. Check the installation of main control board of each mode on site.
a. Check whether the main control board of each mode is installed correctly, according to
Y => The main control board of each mode is installed correctly. Contact Huawei
325 de 526 13/11/2012 9:15


N => The main control board of a mode is installed incorrectly. Go to sub-step b.
b. Reinstall the main control board according to the configuration plan. Ensure that the
main control board of each mode is installed in the correct BBU.
1.1.177 ALM-26310 Inter-BBU Optical Module Fault

Description
This alarm is reported when the optical module on an inter-BBU port is faulty.
Parameters
Port No. Number of the faulty port
Port Description Faulty port description
Warning The information about the optical module cannot be obtained.
System Actions
None
Possible Causes
The optical module on an inter-BBU port is faulty.
Procedure
a. Check for the correlated alarm of the faulty optical module on the M2000:

326 de 526 13/11/2012 9:15

2. Remove and then insert the optical module onsite.
a. Remove and then insert the faulty optical module onsite.

3. Replace the faulty optical module onsite.

1.1.178 ALM-26311 Inter-BBU Optical Module Not in Position

Description
This alarm is reported when the optical module on an inter-BBU port is improperly configured or when the cable
for the inter-BBU electrical port is improperly connected. This alarm is only reported by a 2 U BBU.
Parameters
Major If the BBUs are interconnected by UCIU+UCIU/UMPT, then:

The control information, clock information, and transmission information fail to be
exchanged between BBUs.
A multi-mode base station cannot share power equipment, reference clocks, and
transport resources.
The services carried by the lower-level BBUs cannot be provided normally.
System Actions
None
Possible Causes
327 de 526 13/11/2012 9:15

The cable for the optical module on an inter-BBU port or for the inter-BBU electrical port is not
installed or not connected securely.
The cable for the optical module on an inter-BBU port or for the inter-BBU electrical port is faulty.
The connecting piece on an inter-BBU port is faulty.
Procedure
1. Check the configurations of inter-BBU ports on the M2000.
a. Run the MML command LST CTRLLNK or LST BBPLNK to query the configurations of
inter-BBU ports. Check whether the configurations are correct according to the onsite
plan.
Y=> The configurations are correct. Go to step 2.
N=> The configurations are incorrect, and extra inter-BBU ports are configured. Go to
step 2.
b. Run the MML command RMV CTRLLNK or RMV BBPLNK to remove the extra
inter-BBU ports.
2. Check cable connections for the optical module or electrical port onsite.
a. Check whether the cable for the optical module or electrical port is installed on the BBU
side.
Y => The cable is installed. Go to substep c.
Y => The cable is not installed. Go to substep b.
b. Install an optical module or install the cable for the electrical port.
c. Remove and then insert the optical module or remove and then insert the electrical
cable, and check that the optical module is connected properly.
d. If the inter-BBU port is an optical port, Replace the optical module.

If the inter-BBU port is an electrical port, replace the electrical cable.
3. Remove and then insert the faulty board onsite.

328 de 526 13/11/2012 9:15

4. Replace the faulty board onsite.

Service Center.
1.1.179 ALM-26312 Inter-BBU Optical Module Receive Failure

Description
This alarm is reported when the optical link (at the physical layer) between BBU ports fails to receive optical
signals. This alarm is only reported by a 2U BBU.
Parameters
Parameter
Too Low)

Minor If the BBUs are interconnected by UCIU+UCIU/UMPT, the bit error rate (BER) of the
control information, clock information, and transmission information exchanged
between BBUs increases. As a result, the service quality of the lower-level BBU
deteriorates.
If the BBUs are interconnected by WBBPf+WBBPf, the bit error rate (BER) of the
329 de 526 13/11/2012 9:15

baseband data and signaling exchanged between BBUs increase, affecting service
quality.
System Actions
None
Possible Causes
The optical module on an inter-BBU port is faulty or not installed properly, or the cable connection on
the optical module is not ready.
The optical connector of an inter-BBU port is dirty.
The optical modules on both ends of an inter-BBU port do not match, in terms of type (single-mode
or multi-mode) and rate.
The optical module on an inter-BBU port does not match that supported by the board, in terms of
The optical module on an inter-BBU port does not match the connected fiber optic cable, in terms of
The UCIU is faulty.
The peer board of an inter-BBU port is not powered on.

The peer optical connector of an inter-BBU port or the optical module is not inserted properly, or the
optical module is faulty.
The peer optical connector of an inter-BBU port is dirty.
The optical module on an inter-BBU port does not match the connected fiber optic cable, in terms of
The fiber optic cable between inter-BBU ports is faulty.
The peer board of an inter-BBU port is faulty.
Procedure
a. Check for the correlated alarm of the inter-BBU port and the port of the peer board on
the M2000:

2. Check the optical module and fiber optic cable of an inter-BBU port onsite.
a. Remove and then insert the optical module and optical connector on the inter-BBU port
330 de 526 13/11/2012 9:15

on the BBU side.

b. Remove the optical connector from the optical module, and clean the connector using
alcohol or cigarette filter tip. Then, reinstall the connector to the optical module.
c. Check whether the optical modules on both ends of the inter-BBU port match, in terms
of type (single-mode or multi-mode) and rate (4.9152 Gbit/s). 1310nm is labeled on a
single-mode optical module, and 850nm is labeled on a multi-mode optical module.
Y => The optical modules on both ends of the inter-BBU port match. Go to sub-step e.
N => The optical modules on both ends of the inter-BBU port do not match. Go to
sub-step d.
d. Based on the type of one end of the inter-BBU port, select an optical module that
matches the type. Replace the optical module.
e. Run the MML command DSP SFP to query the transmission mode of the optical
module. A blue fiber optic cable is used for the single-mode optical module, and an
orange fiber optic cable is used for the multi-mode optical module. Check whether the
optical module matches the connected fiber optic cable, in terms of type (single-mode
or multi-mode) and rate.
Y => The optical module matches the connected fiber optic cable. Go to step 3.
N => The optical module does not match the connected fiber optic cable. Go to
sub-step f.
f. Replace the optical module.

3. Check the running status of the peer board onsite.
a. Check the running status of the peer board onsite by observing the RUN indicator on the
board. Check whether the RUN indicator blinks normally (on for 1s and off for 1s).
Y => The RUN indicator blinks normally. Go to step 4.
N => The RUN indicator does not blink normally. Go to sub-step b.
b. Rower on the peer board again and wait until the RUN indicator blinks normally (on for
1s and off for 1s).
331 de 526 13/11/2012 9:15

4. Check the fiber optic cable onsite.
a. Verify that the fiber optic cable between the BBUs is not bent or deformed.
N => The alarm is not cleared. Go to substep b.

5. Replace the optical module for the BBU interconnection on the peer board onsite.

6. Replace the peer board onsite.


Service Center.
1.1.180 ALM-26313 Inter-BBU Optical Module Transmit Failure

Description
This alarm is reported when the optical module on an inter-BBU port fails to transmit data. This alarm is only
reported by a 2U BBU.
Parameters
Parameter
332 de 526 13/11/2012 9:15

Specific Problem Specific Problem of the alarm(Optical Module Performance Degraded, Optical Module
Transmit Error)

Minor Services are not affected temporarily. If the problem remains for a long time, the
alarm severity is changed to major.
System Actions
None
Possible Causes
The optical module on an inter-BBU port deteriorates.
Procedure
1. Check the inter-BBU port onsite.
a. Remove and then insert the optical module and optical connector of the inter-BBU port
on the BBU side.

1.1.181 ALM-26314 Inter-BBU Port Failure

Description
This alarm is reported when an inter-BBU port fails to transmit or receive data. This alarm is only reported by a
2U BBU.
Parameters
Parameter
Parameter Description
333 de 526 13/11/2012 9:15

Name
Port Faulty port description

Description
Specific Specific Problem of the alarm(CPRI Interface Initialization Failure, CPRI Interface Transmit
Problem Error, CPRI Interface Reception Error)

System Actions
None
Possible Causes
The peer optical connector of an inter-BBU port or the optical module is not inserted properly, or the
fiber optic cable fails to be connected. The electrical cable for the peer inter-BBU port is not securely
connected, or the electrical cable is faulty.
The peer board of an inter-BBU port does not work properly, or the hardware of the board is faulty.
Procedure
a. Check for the correlated alarm of the faulty inter-BBU port on the M2000:
334 de 526 13/11/2012 9:15


2. Reset the board for BBU interconnection on the M2000.
a. Run the RST BRD command to reset the faulty board for BBU interconnection, and wait
until the board is restarted.
b. Run the RST BRD command to reset the peer board and wait until the board is
restarted.
3. Remove and then insert the faulty UCIU onsite.
a. Check the faulty UCIU. Reseat the board.

4. Replace the faulty UCIU onsite.

5. Replace the peer board of the faulty port onsite.
a. Replace the peer board of the faulty port. Replace the board.
Service Center.
1.1.182 ALM-26315 Inter-BBU Port Connection Error

Description
An inter-BBU interface on the UCIU can be an M port or an S port. Inter-BBU interfaces of the same type cannot
be connected, and a ring network is not allowed if inter-BBU interfaces are connected. This alarm is reported
when inter-BBU interfaces of the same type are connected, or a ring network is set up in the case of an
inter-BBU connection.
335 de 526 13/11/2012 9:15

Parameters
Fault Type Fault Type (S Port Connected to S Port, M Port Connected to M Port, Ring Topology)
Major BBUs cannot share control information, clock information, and transmission
information. Services may be interrupted.
System Actions
None
Possible Causes
Inter-BBU interfaces of the same type are connected, or a ring network is set up in the case of an inter-BBU
connection.
Procedure
If "Specific Problem" is "M Port Connected to M Port" or "S Port Connected to S Port",
go to step 2.
If "Specific Problem" is "Ring Topology", go to step 3.
2. Check the UCIU for the connection of inter-BBU ports of the same type on site.
a. Based on the alarm parameters, locate the UCIU port and the connected optical fiber.
Check whether the connection of inter-BBU ports of the same type exists on the UCIU
port.
Y => The connection of inter-BBU ports of the same type exists on the UCIU port. Go
to sub-step b.
N => The connection of inter-BBU ports of the same type does not exist on the UCIU
port. Contact Huawei Customer Service Center.
b. Reconnect the inter-BBU optical fibers based on the engineering plan.
3. Check the UCIU for a ring topology of inter-BBU connection on site.
336 de 526 13/11/2012 9:15

a. Based on the alarm parameters, locate the UCIU port and the connected optical fiber.
Check whether a ring topology of inter-BBU connection exists on the UCIU port.
Y => A ring topology of inter-BBU connection exists on the UCIU port. Go to sub-step
b.
N => A ring topology of inter-BBU connection does not exist on the UCIU port. Contact
b. Reconnect the inter-BBU optical fibers based on the engineering plan.

1.1.183 ALM-26501 RF Unit Optical Module or Electrical Port Not Ready

Description
This alarm is reported when the optical module on the port of the RF unit connecting to the peer device (upper-
or lower-level RF unit or the BBU) is not in position or when the cable connection on the optical module or
electrical port is not ready.
Parameters
Port CPRI port (Port 0(West), Port 1(East))
carried on lower-level RF units are disrupted.
are disrupted for about ten seconds.
System Actions
In ring topology, the active link of lower-level RF units is switched over to the standby link.
Possible Causes
The networking of RF units is incorrect. Redundant lower-level RF units are configured.
The optical module on the port of the RF unit connecting to the peer device (upper- or lower-level RF
unit or the BBU) is not in position, or the cable connection on the optical module or electrical port is
not ready.
The optical module on the port of the RF unit connecting to the peer device (upper- or lower-level RF
337 de 526 13/11/2012 9:15

unit or the BBU) is faulty, or the cable connected to the optical module or electrical port is faulty.
The connecting piece on the port of the RF unit connecting to the peer device (upper- or lower-level
RF unit or the BBU) is faulty.
Procedure
1. Check for redundant lower-level RF units on the M2000.
a. Run the MML command LST RRUCHAIN to query the link networking of the faulty RF
unit. Check whether a redundant lower-level RF unit is configured according to the site
plan.
Y => A redundant lower-level RF unit is configured. Go to sub-step b.
N => There is no redundant lower-level RF unit. Go to step 2.
b. Run the MML command RMV RRU to remove the redundant lower-level RF unit.
2. Check the installation of the optical module, or check the cable connection on the optical module or
electrical port of the RF unit on site.
optical module or electrical port on site.
b.
b. Install the optical module or connect the cable to the optical/electrical port.
c. Reseat the optical module or the cable connected to the optical/electrical port.
d. Replace the optical module, or replace the cable on the electrical port.
3. Power cycle the RF unit on site.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s).
338 de 526 13/11/2012 9:15


Service Center.
1.1.184 ALM-26502 RF Unit Optical Module Type Mismatch

Description
This alarm is reported when the optical module installed on the port of the RF unit connecting to the peer device
(upper- or lower-level RF unit or the BBU) is not supported by the RF unit.
Parameters
Valid Optical Module Valid optical module type (1.25Gbps, 2.5Gbps, 3.07Gbps, 4.9Gbps, 6.14Gbps,
Type 9.8Gbps, 3.84Gbps)
Installed Optical Module Type of the installed optical module (1.25Gbps, 2.5Gbps, 3.07Gbps, 4.9Gbps,
Type 6.14Gbps, 9.8Gbps, 3.84Gbps)
Major The port of the RF unit connecting to the peer device (upper- or lower-level RF unit
or the BBU) does not work normally. The services carried on the RF unit are
disrupted.
System Actions
None
Possible Causes
The type of the optical module installed on an RF unit is not supported by the RF unit. For example, an RF unit
supports only an optical module of 2.5 Gbit/s, but an optical module of 1.25 Gbit/s is installed on the RF unit.
Procedure
a. Replace the optical module of the RF unit on site. Ensure that the installed optical
module is supported by the RF unit.
339 de 526 13/11/2012 9:15

1.1.185 ALM-26503 RF Unit Optical Module Transmit/Receive Fault

Description
This alarm is reported when the optical transmission on the optical link (at the physical layer) is abnormal
between the RF unit and the peer device (upper-level/lower-level RF unit or BBU).
Parameters
Port Type CPRI port type (Uplink, Downlink)
Specific Problem Specific Problem of the alarm(Transmit Error, Reception Error)
In ring topology, the reliability of the link of RF units decreases. In this case, the
active link of lower-level RF units is switched over to the standby link. In the case of
a hot ring, the ongoing services are not affected. In the case of a cold ring, the
ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RF unit automatically switches to a normal port if its uplink port is faulty.
Possible Causes
The optical module or connector of the current-level RF unit is improperly installed, or the optical
module is faulty.
The optical connector of the current-level RF unit is dirty.
The current-level RF unit is faulty.
The peer device (upper-level/lower-level RF unit) is not powered on.
The optical module or connector of the peer device (upper-level/lower-level RF unit or BBU) is
improperly installed, or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RF unit or BBU) is dirty.
The optical link between the current-level RF unit and the peer device (upper-level/lower-level RF unit
or BBU) is faulty.
Procedure
340 de 526 13/11/2012 9:15

a. Check for the correlated alarm on the faulty port of the RF unit on the M2000:
2. Check the faulty port of the current-level RF unit on site.
a. On the current-level RF unit side, remove and reinstall the optical module and connector
on the faulty port.
3. Connect the TX and RX terminals of the optical fiber at the current-level RF unit on site.
a. Remove the optical fiber from the optical module of the RF unit. Then, connect the TX
connection of the RF unit. Then, Go to step 4.
d. Power off the RF unit on site and then power it on. Wait until the RF unit startup is
complete (the RUN LED blinking, ON for 1s and OFF for 1s).
e. Replace the RF unit.
341 de 526 13/11/2012 9:15


N => The alarm is not cleared. Reinstall the original board. Then, Go to step 4.
4. Check the running status of the peer device.
a. On the peer device side, check whether the RUN LED on the peer device blinks (ON for
1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). The peer device is running
normally. Go to step 5.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). The peer device is
running improperly. Go to sub-step b.
b. Reset the peer device on site. Wait until the RUN LED blinks (ON for 1s and OFF for
1s).
5. Check the port of the peer device.
a. Remove and reinstall the optical module and connector on the port of the peer device.
6. Connect the TX and RX ports of the optical module at the peer device.
a. Remove the optical fiber from the optical module of the peer device. Then, connect the
TX and RX ports of the optical module by using an optical fiber for loopback.
connection of the peer device. Then, Go to step 7.
c. Replace the optical module of the peer device.

d. Power Cycle the Peer Device.

342 de 526 13/11/2012 9:15

e. Replace the peer device.

a. Check the optical connections between the current-level RF unit and the peer device.
Replace the faulty optical fibers to troubleshoot the improper optical connections, such
as fiber bending or deformation.

1.1.186 ALM-26504 RF Unit CPRI Interface Error

Description
This alarm is reported when the data transmission on the link (at the link layer) is abnormal between the RF unit
and the peer device (upper-level/lower-level RF unit or BBU).
Parameters
Parameter
Port Type CPRI port type (Uplink, Downlink)
Specific Problem Specific Problem of the alarm(CPRI Interface Transmit Error, CPRI Interface Reception
Error)
In ring topology, the reliability of the link of RF units decreases. In this case, the
active link of lower-level RF units is switched over to the standby link. In the case of
a hot ring, the ongoing services are not affected. In the case of a cold ring, the
343 de 526 13/11/2012 9:15

ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RF unit automatically switches to a normal port if its uplink port is faulty.
Possible Causes
If the optical transmission is used, the optical module or connector of the RF unit or peer device may
be improperly installed, or the optical link is faulty.
If the electrical transmission is used, the cable connector of the RF unit or peer device may be
The RF unit or peer device malfunctions, or the hardware is faulty.

Procedure
If "Specific Problem" is "CPRI Interface Transmit Error", go to step 3.
If "Specific Problem" is "CPRI Interface Reception Error", go to step 4.
344 de 526 13/11/2012 9:15

a. Check the optical connections between the BBU and the peer end. Troubleshoot the
improper optical connections, such as fiber bending or deformation.

4. Check the cable connections on the faulty port of the RF unit on site.
a. Check the cable connections on the optical or electrical port of the current-level RF unit
on site.
If the electrical transmission is used, Go to sub-step b.
If the optical transmission is used, Go to sub-step d.
b. Reseat the cable on the electrical port of the current-level RF unit and the peer device.
c. Replace the cable on the electrical port.

d. Remove the connector from the optical module of the current-level RF unit. Clean the
connector by using absolute alcohol or a clean cigarette filter. Then, reinstall the
connector to the optical module of the current-level RF unit.
e. Check the optical connections between the current-level RF unit and the peer end.
as fiber bending, deformation, damage, or loose optical connector/module.
N => The alarm is not cleared. Go to sub-step f.
f. Remove the connector from the optical module of the lower-level RF unit. Clean the
connector by using absolute alcohol or a clean cigarette filter. Then, reinstall the
connector to the optical module of the lower-level RF unit.
N => The alarm is not cleared. Go to sub-step g.
g. Replace the optical module of the peer end.

345 de 526 13/11/2012 9:15


5. Check the running status of the RF unit or peer device on site.
b. Power cycle the peer device.
c. Replace the RF unit.

N => The alarm is not cleared. Reinstall the original board. Then, Go to sub-step d.
d. Replace the peer device.

1.1.187 ALM-26506 RF Unit Optical Interface Performance Degraded

Description
This alarm is reported when the TX/RX performance of the optical module of the RF unit deteriorates.
Parameters
Parameter
Specific Specific Problem of the alarm(Optical Module Performance Degraded, Reception Power Too
Problem High, Reception Power Too Low)
quality of services carried on the link of the RF unit may decrease significantly, or the
346 de 526 13/11/2012 9:15

ongoing services carried on the RF unit may even be disrupted.
quality of services carried on the link of the RF unit may decrease to some extent.
System Actions
None
Possible Causes
The optical module or connector of the current-level RF unit is improperly installed. Or the optical
module is worn-out.
The optical connector of the current-level RF unit is dirty.
The optical module on the port of the current-level RF unit is not supported by the current-level RF
unit, in terms of type (single-mode or multi-mode) and rate.
The optical module or connector of the peer device (upper-level/lower-level RF unit or BBU) is
improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RF unit or BBU) is dirty.
The optical module on the port of the peer device (upper-level/lower-level RF unit or BBU) is not
supported by the peer device, in terms of type (single-mode or multi-mode) and rate.
The optical fibers between the current-level RF unit and the peer device (upper-level/lower-level RF
unit or BBU) are bent, deformed, or worn-out. Or the length of optical fibers is excessive (longer than
40 km), which leads to a high attenuation of optical signals.
Procedure
1. Check the faulty port of the current-level RF unit on site.
a. Remove and reinstall the optical module and connector on the port of the current-level
RF unit.
c. Examine the label on the optical module to check whether the optical module on the port
is supported by the current-level RF unit, in terms of type (single-mode or multi-mode)
and rate (1.25 Gbit/s, 2.5 Gbit/s or other rate).
Y => The optical module is supported by the RF unit. Go to sub-step e.
N => The optical module is not supported by the RF unit. Go to sub-step d.
d. Select the optical module that is supported by the RF unit.

347 de 526 13/11/2012 9:15


2. Check the port of the peer device on site.
a. Remove and reinstall the optical module and connector on the port of the peer device.
c. Examine the label on the optical module to check whether the optical module on the port
is supported by the peer device, in terms of type (single-mode or multi-mode) and rate
(1.25 Gbit/s, 2.5 Gbit/s or other rate).
Y => The optical module is supported by the peer device. Go to sub-step e.
N => The optical module is not supported by the peer device. Go to sub-step d.
d. Select the optical module that is supported by the peer device.

a. Check the optical connections between the current-level RF unit and the peer device.
as fiber bending or deformation.
b. Check the length of the optical link between the current-level RF unit and the peer
device. If the length is excessive (longer than 40 km), add an optical trunk or use
another cascaded RF unit as the optical trunk.
c. Replace the optical fibers between the current-level RF unit and the peer device.
1.1.188 ALM-26507 RF Unit Optical Module Fault
348 de 526 13/11/2012 9:15

Description
This alarm is reported when the optical module or electrical module on the port of the RF unit connecting to the
peer device (upper- or lower-level RF unit or the BBU) is faulty.
Parameters
Warning The information about the optical module or electrical module cannot be obtained.
System Actions
None
Possible Causes
The optical module or electrical module of the RF unit is faulty.
Procedure
a. Check for the correlated alarm of the RF unit on the M2000:

2. Query it's using optical module or electrical module:
a. Run the MML command DSP BTSBRD, and query the RUNPARA of the faulty RF
board, to check using optical module or electrical module.
Optical module, go to step 3;
Electrical module, go to step 5;

349 de 526 13/11/2012 9:15



5. Remove and reinstall the electrical module and cable on site.
a. Remove and reinstall the faulty electrical module and cable on site.
6. Replace the electrical module and cable on site.
a. Replace the electrical module and cable .

1.1.189 ALM-26520 RF Unit TX Channel Gain Out of Range

Description
This alarm is reported when the difference between the actual gain and the standard gain on the TX channel of
the RF unit is greater than 2.5 dB.
Parameters
TX Channel No. TX channel number
Input Power (0.1 dBFs) Input power of the RF unit
Output Power (0.1 dBm) Output power of the RF unit
Minor When the gain on the TX channel is extremely high, the downlink coverage of the cell
is excessive. In this case, the interference caused by cross coverage occurs.
When the gain on the TX channel is extremely low, coverage holes exist in the
downlink coverage of the cell. In serious cases, the ongoing services carried on the
350 de 526 13/11/2012 9:15

RF unit may be disrupted.
System Actions
None
Possible Causes
The hardware of the RF unit is faulty.
Procedure
power-off.

Service Center.
1.1.190 ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low

Description
This alarm is reported when the RTWP/RSSI on the RX channel of the RF unit is lower than -114 dBm. RTWP is
shortened from received total wideband power, consisting of signal power and noise power. RSSI is shortened
from received signal strength indicator.
Parameters
RX Channel No. RX channel number
RTWP (0.1 dBm) RTWP of the faulty RX channel
351 de 526 13/11/2012 9:15

Minor The receive sensitivity of the RF unit decreases. The demodulation performance of
the cell deteriorates. The uplink coverage shrinks.
If the RTWP/RSSI on all RX channels of the cell is too low, the ongoing services of
the cell may be disrupted.
System Actions
None
Possible Causes
The setting of attenuation of the RF unit is incorrect.
The TMA is faulty.
The feeder installation is improper. For example, the feeder connector is loose, soaked or damaged,
or the feeder is deformed.
The RX channel of the RF unit is faulty. For example, the low-noise amplifier, frequency mixer, analog
to digital converter (ADC), or field programmable gate array (FPGA) is faulty.
Procedure
26530 RF Unit ALD Current Out of Range

Wait for 10 minutes after the correlated alarm is cleared.
2. Check the attenuation of the RF unit on the M2000.
a. Calculate the attenuation of the RF unit.

Attenuation of RF unit = TMA gain - feeder loss
Where, feeder loss can be obtained from the acceptance report of the base station.
The installation personnel measure the feeder loss during the base station installation.
b. Run the MML command MOD RXBRANCH to set the attenuation on the main RX
channel and diversity RX channel of the RF unit to the calculated attenuation. Then, wait
for 10 minutes.
c. Run the MML command MOD RXBRANCH to set the attenuation on the main RX
channel and diversity RX channel of the RF unit to 0. Then, wait for ten minutes.
352 de 526 13/11/2012 9:15


Y => The alarm is cleared. Go to sub-step d.
d. Run the MML command MOD RXBRANCH to set the attenuation on the main RX
channel and diversity RX channel of the RF unit back to the calculated attenuation.
Then, Go to step 3.
3. Reconnect the jumper to the antenna port of the RF unit on site.
a. Reconnect the jumper to the antenna port of the RF unit. Then, wait for 10 minutes.
4. Replace the TMA on site.
a. Replace the TMA.

blinking, ON for 1s and OFF for 1s). Then, wait for 10 minutes.
a. Replace the RF unit, and then wait for 10 minutes.

Service Center.
1.1.191 ALM-26522 RF Unit RX Channel RTWP/RSSI Unbalanced

Description
This alarm is reported when the difference between the RTWP/RSSI of the main RX channel and the
RTWP/RSSI of the diversity RX channel exceeds 10 dB. RTWP is shortened from received total wideband
power, consisting of signal power and noise power. RSSI is shortened from received signal strength indicator.
Parameters
353 de 526 13/11/2012 9:15

Carrier No. Carrier number
RTWP of Main RX Channel (0.1 dBm) RTWP of the main RX channel
RTWP of Diversity RX Channel (0.1 dBm) RTWP of the diversity RX channel
Minor The receive sensitivity of the RF unit decreases. The demodulation performance of
the cell deteriorates. The uplink coverage shrinks.
System Actions
None
Possible Causes
The main RX channel or diversity RX channel of the RF unit is faulty.
The setting of attenuation on the RX channel of the RF unit is incorrect.
External interferences exist only on the main or diversity antenna of the RF unit.
The feeder connected to the RF unit is faulty, which results in a high passive intermodulation power
of the main or diversity antenna.
The feeder installation is improper. For example, the feeder connector is loose, soaked or damaged,
or the feeder is deformed.
Procedure
a. Check for the correlated alarm of the RF unit on the M2000:

26521 RF Unit RX Channel RTWP/RSSI Too Low
Y => The correlated alarm exists. Go to substep b.

2. Check the parameter settings of the RF unit on the M2000.
a. Calculate the attenuation on the RX channel of the RF unit.

b. Run the MML command MOD RXBRANCH to set the attenuation on the main and
diversity RX channels of the RF unit to the calculated attenuation.
c. Wait for 40 minutes.
354 de 526 13/11/2012 9:15


3. On the LMT, check for external interference on the main and diversity antennas.
a. On the LMT, start the uplink frequency scanning . Check whether the external
interferences exist (by distinct bulges near the uplink frequencies in the scanned
diagram).
Y => The external interference exists. Go to sub-step b.
N => A single cell uses a 4R or higher configuration and there is not interference. Go to
step 4.
N => A single cell uses a 2R or lower configuration and there is not interference. Go to
step 5.
b. Eliminate the external interference.
c.
Wait for 40 minutes.
4. Locate the faulty channel on the M2000.
a. On the LMT, start the uplink frequency scanning. Monitor the results for 30 minutes to
locate the faulty channel (whose RTWP or RSSI is lower than that of other channels).
Go to step 5.
a. Reconnect the jumper to the antenna port of the RF unit. Then, wait for 30 minutes.
blinking, ON for 1s and OFF for 1s). Then, wait for 30 minutes.

Service Center.
1.1.192 ALM-26524 RF Unit PA Overcurrent
355 de 526 13/11/2012 9:15

Description
This alarm is reported when the operating current of the Power Amplifier (PA) on a TX channel of the RF unit is
beyond the normal range.
Parameters
PA Temperature (C/F) Temperature of the PA
Major The RF unit automatically switches off the TX channel. The ongoing services carried
on the TX channel are disrupted.
System Actions
The RF unit automatically switches off the faulty TX channel. The system waits for one minute and then switches
on the TX channel. After five minutes, the system checks the alarm. If the alarm persists, the RF unit
automatically switches off the TX channel again. If the alarm persists after three switching-on attempts, the
system alters to switch on the TX channel every 30 minutes, until the alarm is cleared or the RF unit is reset by
the user.
Possible Causes
Procedure
power-off.

Service Center.
356 de 526 13/11/2012 9:15

1.1.193 ALM-26525 RF Unit Temperature Unacceptable

Description
This alarm is reported when the operating temperature of an RF unit is out of the normal range.
The rated operating temperature range is a hardware specification of RF units. This range varies depending on
the type of the RF unit.
Parameters
PA Temperature (C/F) Temperature of the PA
Board Temperature(C/F) Temperature of the board
Major The RF unit automatically switches off the TX channel to prevent the hardware from
being burned out because of high temperature. The ongoing services carried on the
RF unit are disrupted.
Minor The reliability of internal components of the RF unit may decrease when operating in
a high-temperature environment for a long period of time. Meanwhile, the quality of
services carried on the RF unit decreases.
System Actions
When the temperature of an RF unit exceeds the major alarm threshold, the RF unit automatically switches off
the TX channel. When the temperature of the RF unit drops to a certain value, the RF unit switches on the TX
channel again. To protect the power amplifier (PA) from being damaged by frequent switching-on and -off, this
alarm cannot be cleared after the TX channel has been switched off and on for three times. Under that
circumstance, users need to solve the temperature problem onsite and then manually reset the RF unit. When
the temperature of an RF unit is between the minor alarm threshold and the major alarm threshold, the BBU
limits the user access to a cell through the RF unit to prevent further power consumption and temperature
increase.
Possible Causes
The ambient temperature of the RF unit is extremely high, or the heat dissipation malfunctions.
Procedure
357 de 526 13/11/2012 9:15


25601 Monitoring Device Hardware Fault
25673 Fan Stalled
power-off.
3. Check the ambient temperature of the RF unit on site.
a. Check the ambient temperature and heat dissipation of the RF unit. Check whether the
ambient temperature is normal.
Y => The ambient temperature is normal. Go to step 4.
N => The ambient temperature is extremely high. Go to sub-step b.
b. Take proper measures to reduce the ambient temperature of the RF unit. Then, wait for
10 minutes.

Service Center.
1.1.194 ALM-26527 RF Unit Input Power Out of Range

Description
This alarm is reported when the baseband input power from the BBU to the RF unit is beyond the normal power
range of the RF unit.
Parameters
358 de 526 13/11/2012 9:15

Major The RF unit automatically performs the amplitude limitation on input power. In this
case, the quality of services carried on the RF unit may decrease, and call drops
may occur on edge of coverage of the RF unit.
System Actions
The RF unit automatically performs the amplitude limitation on input power.
Possible Causes
When the input power of the RF unit approaches or reaches the maximum input power, the user
starts the stimulated downlink load.
The user access threshold is improper, which leads to the actual number of users to exceed the
allowed capacity of the RF unit.
The board in the BBU connected to the RF unit is running improperly.
Procedure
1. Check the state of stimulated downlink load on the M2000.
a. Run the MML command DSP DLSIM to check whether the stimulated downlink load is
started on the RF unit.
Y => The stimulated downlink load is started. Go to sub-step b.
N => The stimulated downlink load is not started. Go to step 2.
b. Run the MML command STP DLSIM to stop the stimulated downlink load.
2. Check the user access threshold on the M2000.
a. If the user access threshold exists in the base station or RNC, check whether the
threshold is proper according to the network plan.
b. Modify the user access threshold in the base station or RNC according to the network
plan.
359 de 526 13/11/2012 9:15


3. Reset the board in the BBU connected to the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF to reset the board through power-off in the
BBU that is connected to the RF unit.
4. Replace the board in the BBU connected to the RF unit on site.

Service Center.
1.1.195 ALM-26529 RF Unit VSWR Threshold Crossed

Description
The voltage standing wave ratio (VSWR) measures the signal power that the load actually receives from the
transmission line. This alarm is reported when the VSWR at the antenna port of the TX channel of an RF unit is
higher than the preset threshold.
Parameters
VSWR Alarm Threshold (0.1) VSWR alarm threshold configured by the user
VSWR Detected VSWR, the precision is 0.1
Major The return loss at the antenna port is excessive. When the detected VSWR exceeds
the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When "VSWR alarm
post-processing switch" is set to "ON", the TX channel of the RF unit is switched off
and the alarm cannot be automatically cleared, and the ongoing services carried on
the TX channel are disrupted..When "VSWR alarm post-processing switch" is set to
"OFF", the power of the RF unit is automatically decreased (by 3 dB by default) to
360 de 526 13/11/2012 9:15

avoid hardware damage, and the alarm can be automatically cleared.
Minor The return loss at the antenna port is relatively large. In this case, the output power
of the RF unit decreases and the cell coverage shrinks.
System Actions
When the detected VSWR exceeds the minor alarm threshold, the system does not handle the alarm. The alarm
is automatically cleared when the detected VSWR becomes smaller than the alarm threshold. When the
detected VSWR exceeds the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When "VSWR alarm post-processing switch" is set to
"ON", the TX channel of the RF unit is switched off and the alarm cannot be automatically cleared.When "VSWR
alarm post-processing switch" is set to "OFF", the power of the RF unit is automatically decreased (by 3 dB by
default) to avoid hardware damage. Once the detected VSWR becomes smaller than the alarm threshold, the
alarm is automatically cleared.
Possible Causes
The preset VSWR threshold is very low. It is recommended that the VSWR alarm threshold not be
used as the VSWR acceptance threshold.
The VSWR threshold is set to an excessively low value for the other mode of the multi-mode RF
units.
The installation of jumpers does not comply with the plan.
The feeder connector on the antenna port does not meet the requirements, is loose or waterlogged,
or has foreign objects.
The feeder connected to the antenna port of the RF unit is bent, deformed, or damaged.
The RF unit is faulty in hardware.
The frequency bands supported by the RF unit do not match the frequency bands supported by the
components of the antenna system. The components of the antenna system include antennas,
feeders, jumpers, combiner-dividers, filters, and tower-mounted amplifiers (TMAs).
A component of the antenna system is damaged.
Procedure
1. Check the VSWR threshold on the M2000.
a. Run the MML command LST RRU to query the VSWR threshold of the RF unit. If the
alarm severity is major, query the value of VSWR alarm post-processing threshold. If
the alarm severity is minor, query the value of VSWR alarm threshold.Check whether
the VSWR threshold is proper according to the configuration plan.
b. If the RF unit works in multi-mode, run the MML command LST RRU to query the
VSWR threshold configured for the other mode. Check whether the VSWR thresholds
configured for the two modes are consistent.
Y => The VSWR thresholds configured for the two modes are consistent. Go to step 2.
N => The VSWR thresholds configured for the two modes are inconsistent. Go to
sub-step c.
c. Run the MML command MOD RRU to modify the VSWR threshold of the RF unit. If the
alarm severity is major, set the value of VSWR alarm post-processing threshold. If the
361 de 526 13/11/2012 9:15

alarm severity is minor, set the value of VSWR alarm threshold.

2. Check the frequency bands supported by the RF unit and the components of the antenna system
onsite.
a. Check whether the frequency bands supported by the RF unit are consistent with the
frequency bands supported by the components of the antenna system based on the
network planning data.
Y => The frequency bands are consistent. Go to step 3.
Y => The frequency bands are inconsistent. Go to sub-step b.
b. Replace the components of the antenna system with the components specified in the
network planning data according to the instructions in the antenna system installation
guide. If the severity of the alarm is major and the TX channel of the RF unit is switched
off automatically, power off and then power on the RF unit onsite, and wait until the RF
unit is restarted.
Wait for 10 minutes. Check whether the alarm is cleared.
3. Check the connections between the RF unit and jumpers onsite.
a. Check whether the installation of the RF unit and jumpers is consistent with the plan.
Y => The installation of jumpers is correct. Go to step 4.
N => The installation of jumpers is incorrect. Go to sub-step b.
b. Reinstall the jumpers for the RF unit according to the plan. If the alarm severity is major
and the TX channel of the RF unit is switched off automatically, power off and then
power on the RF unit onsite, and wait until the RF unit is restarted.
a. Reconnect the jumper to the antenna port of the RF unit. If the detected VSWR
exceeds the major alarm threshold and the TX channel of the RF unit is switched off,
power off and then power on the RF unit onsite, and wait until the RF unit is restarted.
5. Check the installation of feeders for the RF unit on site.
a. Check the installation of feeders for the RF unit. If the alarm severity is major and the
TX channel of the RF unit is switched off, power off and then power on the RF unit
onsite, and wait until the RF unit is restarted.
362 de 526 13/11/2012 9:15


Service Center.
1.1.196 ALM-26530 RF Unit ALD Current Out of Range

Description
This alarm is reported when the current supplied by the RF unit to the antenna device through feeder or
multi-wire cable is beyond the normal range.
Parameters
Antenna Port Antenna port (ANT A, ANT B, RET, ANT C, ANT D)
ALD Working Current Working current of the ALD

(mA)
Specific Problem Specific Problem of the alarm(Overcurrent, Undercurrent, Overcurrent Protection,

Disconnection Protection)
Minor The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases.
Warning The antenna device can work normally, but some secondary functions of the antenna
device fail.
System Actions
In the case of overcurrent, overcurrent protection, and open-circuit protection occurs on the antenna
device, the RF unit automatically switches off the power supply to the antenna device. Meanwhile,
the attenuation on the RX channel is set to 0 to minimize the impact of TMA fault on the receive
sensitivity of the corresponding RX channel.
In the case of overcurrent and overcurrent protection occurs on the antenna device, the RF unit
switches off the power supply to the antenna device and then attempts to switch on the power supply
every other minute. If the fault persists after three attempts, the RF unit does not retry any more.
Five minutes after open-circuit protection occurs and the the power supply to the antenna device is
363 de 526 13/11/2012 9:15

switched off, the RF unit begins the attempt to switch on the power supply to the antenna device
every other minute. If the fault persists after 26 attempts, the RF unit does not retry any more.
Possible Causes
The configuration of the ALD switch is incorrect.
The preset ALD current threshold of the RF unit is incorrect.
The feeder connector is loose or waterlogged.
The feeder is deformed.

The jumper between the feeder and the antenna device is loose.
The ALD power supply circuit of the RF unit is faulty.
The antenna device is faulty.
Procedure
1. Check the configuration of the ALD power supply switch on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT to query the status of
the ALD power supply switch of the RF unit. Check whether the status is correct
according to the configuration plan.
Y => The status of the ALD power supply switch is correct. Go to step 2.
N => The status of the ALD power supply switch is incorrect. Go to sub-step b.
b. Run the MML command MOD ANTENNAPORT/MOD RETPORT to modify the ALD
power supply switch configuration according to the configuration plan.
2. Check the preset ALD current threshold of the RF unit on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT/LST

ANTENNAPORT/LST RETPORT to query the ALD current threshold of the RF unit.
Consult the related ALD manual for the operating current of the ALD. Check whether
the ALD current threshold is correct.
Y => The threshold is correct. Go to step 3.
N => The threshold is incorrect. Go to sub-step b.
current threshold of the RF unit according to the configuration plan.
a. Reconnect the jumper to the antenna port of the RF unit.

364 de 526 13/11/2012 9:15

a. Check the installation of feeders for the RF unit.

5. Check the installation of jumper between the feeder and the antenna device on site.
a. Check the installation of jumper between the feeder and the antenna device.

N => The alarm is not cleared. Reinstall the original board. Then, Go to step 8.
8. Replace the antenna device on site.
a. Perform the corresponding operation according to the antenna device type.

In the case of the RET antenna, replace the RET antenna.
In the case of the TMA, replace the TMA.
In the case of the SASU, replace the SASU.
1.1.197 ALM-26531 RF Unit ALD Switch Configuration Mismatch

Description
An RF unit supports two ALD port types, which are coaxial port (ANT port) and multi-wire port (RET port). This
alarm is reported when the configured ALD switch type does not match the actual type of the ALD port on the
RF unit.
Parameters
365 de 526 13/11/2012 9:15

Antenna Port Antenna port (ANT A, ANT B, RET, ANT C, ANT D)
Hardware Capability Hardware capability (Switch Type Not Supported, Switch Type Supported)
Configured Switch Type Type of the configured switch (ANT Switch, RET Switch)
Installed Switch Type Installed switch type (RET Switch, ANT Switch)
Minor The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases.
System Actions
None
Possible Causes
The coaxial ALD switch is configured, but actually the multi-wire cable is connected to the multi-wire
port.
The multi-wire ALD switch is configured, but actually the multi-wire cable is not connected to the
multi-wire port.
Procedure
1. Check the configuration of the ALD switch on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT to query the

configuration of the ALD switch of the RF unit. Check whether the configuration is
Y => The configuration is correct. Go to step 2.
N => The configuration is incorrect. Go to sub-step b.
switch configuration according to the configuration plan.
c. Run the MML command DSP ANTENNAPORT/DSP RETPORT to check whether the
ALD switch configuration is consistent with the actual configuration.
Y => The ALD switch configuration is consistent with the actual configuration. Contact
N => The ALD switch configuration is inconsistent with the actual configuration. Go to
step 2.
2. Reconnect the cable to the ALD port of the RF unit on site.
366 de 526 13/11/2012 9:15

a. Reconnect the cable to the ALD port of the RF unit on site according to the
configuration plan.
1.1.198 ALM-26532 RF Unit Hardware Fault

Description
This alarm is reported when the RF unit hardware is faulty.
Parameters
Major The RF unit may work improperly. The ongoing services carried on the RF unit may
be disrupted.
Minor Some functions of the RF unit may fail and the quality of services carried on the RF
unit may decrease.
System Actions
When a critical component of an RF unit is faulty, the system automatically disables the faulty RX channel or TX
channel associated with the RF unit.
Possible Causes
The RF unit hardware is faulty.
Procedure
power-off.

367 de 526 13/11/2012 9:15


1.1.199 ALM-26533 RF Unit Software Program Error

Description
This alarm is reported when the software program of the RF unit runs improperly, such as suspension.
Parameters
Major The RF unit may work improperly. The RF unit will be automatically reset. The
ongoing services carried on the RF unit are disrupted during reset.
System Actions
The system automatically resets the RF unit.
Possible Causes
The software program of the RF unit runs improperly, such as suspension.
Procedure
a. Run the MML command RST BRDPWROFF to reset the RF unit.

1.1.200 ALM-26534 RF Unit Overload

Description
This alarm is reported when the CPU usage of the RF unit is beyond the operating threshold.
Parameters
368 de 526 13/11/2012 9:15

CPU Load(%) CPU load
Minor Some functions of the RF unit may fail, such as channel gain correction. In this case,
the quality of services carried on the RF unit decreases. Long-term CPU overload
may result in delayed response or timeout of maintenance tasks of the RF unit.
System Actions
None
Possible Causes
The user runs too many configuration or maintenance commands frequently on the RF unit.
The user starts too many test or measurement tasks on the RF unit.
The software program of the RF unit runs improperly.
Procedure
1. Stop the configuration and maintenance tasks on the RF unit on the M2000.
a. Stop the configuration and maintenance tasks on the RF unit. Then, wait for 15 minutes.
2. Stop all the test, tracing, and statistical tasks on the RF unit on the M2000
a. Stop all the site test, tracing, and statistical tasks on the RF unit. Then, wait for 15
minutes.
power-off. Then, wait for 15 minutes.
1.1.201 ALM-26536 RF Unit Multi-Mode Configuration Conflict

Description
This alarm is reported when the frequencies configured for different modes conflict in multi-mode configuration.
Parameters
369 de 526 13/11/2012 9:15

Configuration Item Conflicted configuration item (Carrier)
Mode of Original Mode of the original parameter (Reserved, TD-SCDMA, LTE-TDD, LTE-FDD,
Parameter WIMAX, CDMA, GSM, UMTS, Unknown)
Mode of New Mode of the new parameter (Reserved, TD-SCDMA, LTE-TDD, LTE-FDD, WIMAX,
Parameter CDMA, GSM, UMTS, Unknown)
Minor This alarm is reported when the frequencies configured for different modes conflict in
multi-mode configuration.
System Actions
None
Possible Causes
This alarm is reported when the frequencies configured for different modes conflict in multi-mode configuration.
Procedure
1. Check the frequencies configured for different modes on the M2000.
a. Run the MML command LST LOCELL to check the frequency configuration of each
mode in multi-mode configuration of the RF unit. Locate the conflicting frequencies.
b. Run the MML command MOD LOCELL to modify the frequency configuration of each
mode of the RF unit according to the network plan.
1.1.202 ALM-26538 RF Unit Clock Problem

Description
This alarm is reported when the interface clock of the RF unit connecting to the peer device (upper- or
lower-level RF unit or the BBU) is faulty, or the working clock of an internal component is faulty.
Parameters
370 de 526 13/11/2012 9:15

Major Some components in the RF unit may work improperly. In certain cases, the ongoing
services carried on the RF unit may be disrupted.
System Actions
When the working clock of a critical component in the RF unit is faulty, the system automatically disables the
faulty RX channel or TX channel.
Possible Causes
The uplink interface of the RF unit is faulty, resulting in the faulty clock that is extracted at the
interface.
The clock chip or another component in the RF unit is faulty.
Procedure
a. Check for the correlated alarm on the port of the RF unit connecting to the peer device
(upper- or lower-level RF unit or the BBU) on the M2000.
26504 RF Unit CPRI Interface Error

power-off.

Service Center.
371 de 526 13/11/2012 9:15

1.1.203 ALM-26540 RF Unit AC Input Power Failure

Description
This alarm is reported when the AC power supply to the RF unit (with the AC-DC converter) fails.
Parameters
Major The ongoing services carried on the RF unit are disrupted.
System Actions
None
Possible Causes
The AC power supply to the RF unit fails.
Procedure
1. Check the AC power supply of the RF unit on site.
a. Check the AC power equipment of the RF unit on site. Take proper measures to
restore the AC power.
1.1.204 ALM-26541 ALD Maintenance Link Failure

Description
This alarm is reported when the maintenance link between the RF unit and the ALD (RET antenna, TMA, or
SASU) malfunctions.
Parameters
ALD No. Number of the antenna device
Device Type Type of the antenna device (RET, TMA, SASU)
372 de 526 13/11/2012 9:15

Major If the maintenance link of the RET antenna is broken, the antenna tilt cannot be
regulated. In this case, the state of the RET antenna cannot be monitored.
If the maintenance link of the TMA is broken, the TMA gain cannot be configured. In
this case, the state of the TMA cannot be monitored.
The maintenance link for the SASU is disconnected. Therefore, the gain of the SASU
cannot be set and the SASU status cannot be monitored.
System Actions
None
Possible Causes
The ALD current of the RF unit is out of range, or the configured ALD switch does not match the
actual type of the ALD port on the RF unit.
The ALD switch of the RF unit is not turned on.
The data configuration of the antenna is incorrect. For example, the vendor code, equipment serial
number, or antenna type is not configured or incorrect; the control port is incorrectly configured.
There are feeder problems, such as water damage, connector fault, or bent cable.
The antenna device is faulty.
Procedure
a. Check for the correlated alarm of the RF unit on the M2000.

26531 RF Unit ALD Switch Configuration Mismatch
2. Set the ALD switch of the RF unit on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch. Then, turn on the ALD switch.
3. Check the antenna device configuration of the RF unit on the M2000.
a. Run the MML command LST RET/LST TMA/LST SASU to check whether the antenna
device configuration, such as vendor code , equipment serial number, antenna type, and
control port is consistent with the actual situation.
373 de 526 13/11/2012 9:15

Y => The configuration is consistent with the actual situation. Go to step 4.

N => The configuration is inconsistent with the actual situation. Go to sub-step b.
b. Run the MML command MOD RET/MOD TMA/MOD SASU/MOD RETSUBUNIT/MOD
TMASUBUNIT/MOD SASUSUBUNIT to modify the antenna device configuration of the
RF unit, such as vendor code, equipment serial number, antenna type, and control port
according to the actual situation.
a. Reconnect the jumper to the antenna port of the RF unit.

a. Check the installation of feeders for the RF unit.

6. Check the installation of jumper between the feeder and the antenna device on site.
a. Check the installation of jumper between the feeder and the antenna device.


374 de 526 13/11/2012 9:15


1.1.205 ALM-26542 RF Unit Backup Power Device Maintenance Link

Failure
Description
This alarm is reported when the maintenance link between the RF unit and the backup power device fails.
Parameters
Major The system cannot monitor the input power, battery, or ambient temperature. The
backup power device cannot be controlled.
System Actions
None
Possible Causes
The backup power device is configured, but not required actually.

The backup power device is not installed. The monitoring board of the backup power device is also
not powered on or works improperly.
The address settings of the DIP switch on the backup power device are incorrect.
The connection between the RF unit and the backup power device is not ready, or the cables are
faulty.
The backup power device is faulty.
Procedure
1. Check the configuration of the backup power device on the M2000.
a. Run the MML command LST PMU(PMU)/LST TCU(TCU) to query the configuration of
the backup power device on the RF unit. Check whether the configuration of the backup
power device is required according to the site plan.
Y => The configuration is required. Go to step 2.
N => The configuration is not required. Go to sub-step b.
375 de 526 13/11/2012 9:15

b. Run the MML command RMV PMU(PMU)/RMV TCU(TCU) to remove the unnecessary
backup power device of the RF unit.
2. Check the working state of the backup power device on site.
a. Check whether the RUN LED on the backup power device blinks (ON for 1s and OFF
for 1s) on site.
b. Power cycle the backup power device. Wait until the RUN LED blinks (ON for 1s and
OFF for 1s).
3. Check the address settings of the DIP switch on the backup power device on site.
a. Check whether the address settings of the DIP switch on the backup power device are
correct according to the configuration plan. For details, see the installation guide.
Y => The address settings are correct. Go to step 4.
N => The address settings are incorrect. Go to sub-step b.
b. Modify the address settings of the DIP switch on the backup power device according to
4. Check the cable connections of the backup power device on site.
a. Reconnect the cables between the RF unit and the backup power device.
b. Replace the cables between the RF unit and the backup power device.
5. Reset the monitoring board for the backup power device on site.
a. Reseat the monitoring board for the backup power device. Wait until the RUN LED on
the monitoring board blinks (ON for 1s and OFF for 1s).
376 de 526 13/11/2012 9:15

6. Replace the monitoring board for the backup power device on site.
a. Remove the monitoring board for the backup power device. Install a new monitoring
board. Wait until the RUN LED on the monitoring board blinks (ON for 1s and OFF for
1s).
1.1.206 ALM-26543 RF Unit External Device Maintenance Link Failure

Description
This alarm is reported when the maintenance link between the RF unit and the general serial port device
malfunctions.
Parameters
Link No. Communication link No. of the external device
Device Address Address of the external device
Major The system cannot monitor or control the general serial port device that is installed
by the user.
System Actions
None
Possible Causes
The serial port device is configured, but not installed actually.
The serial port device is not powered on, or works improperly.

The address settings of the DIP switch on the serial port device are incorrect.
The connection between the RF unit and the serial port device is not ready, or the cables are faulty.
The serial port device is faulty.
Procedure
1. Check the configuration of the serial port device on the M2000.
a. Run the MML command LST PMU(PMU)/LST TCU(TCU) to query the configuration of
the serial port device on the RF unit. Check whether the configuration of the serial port
device is required according to the site plan.
377 de 526 13/11/2012 9:15

Y => The configuration is required. Go to step 2.

N => The configuration is not required. Go to sub-step b.
b. Run the MML command RMV PMU(PMU)/RMV TCU(TCU) to remove the unnecessary
serial port device of the RF unit.
2. Check the working state of the serial port device on site.
a. Check whether the RUN LED on the serial port device blinks (ON for 1s and OFF for
1s) on site.
b. Power cycle the serial port device. Wait until the RUN LED blinks (ON for 1s and OFF
for 1s).
3. According to the base station installation guide, check the address settings of the DIP switch on the
serial port device on site.
a. Check whether the address settings of the DIP switch on the serial port device are
Y => The settings are correct. Go to step 4.
N => The settings are incorrect. Go to sub-step b.
b. Modify the address settings of the DIP switch on the serial port device according to the
configuration plan.
4. Check the cable connections of the serial port device on site.
a. Reconnect the cables between the RF unit and the serial port device.
b. Replace the cables between the RF unit and the serial port device.
5. Power cycle the serial port device on site.
a. Power cycle the serial port device on site. Wait until the serial port device startup is
complete.
378 de 526 13/11/2012 9:15

6. Replace the serial port device on site.
a. Replace the serial port device.

1.1.207 ALM-26544 RF Unit Power Surge Protector Fault

Description
This alarm is reported when the power surge protector of the RF unit is faulty.
Parameters
Major The power surge protection function of the RF unit fails.
System Actions
None
Possible Causes
The RF unit encounters lightning strikes. Therefore, open-circuit protection is implemented by in the power surge
protector of the RF unit.
Procedure
1. Check the surge protector on site.
a. Check whether the surge protector of the RF unit and external power device is
functional.
Y => The surge protector is functional. Go to step 2.
N => The surge protector malfunctions or is not installed. Go to sub-step b.
b. Rectify the fault in the surge protector, or install a functional surge protector.
379 de 526 13/11/2012 9:15


Service Center.
1.1.208 ALM-26545 RF Unit TX Channel Switched Off Through Command

Description
This alarm is reported when a command is executed to turn off the switch of the TX channel of the RF unit.
Parameters
Warning The services carried over the TX channel are disrupted.
System Actions
None
Possible Causes
The command is executed to turn off the switch of the TX channel of the RF unit.
Procedure
1. Turn on the switch of the TX channel of the RF unit on the M2000.
a. After the NE maintenance is complete, run the MML command MOD TXBRANCH to
turn on the switch.
1.1.209 ALM-26546 RF Unit External Power Supply Insufficient

Description
The alarm is reported if the RF unit detects an insufficiency in the capability of the external power supply.
Parameters
Parameter
380 de 526 13/11/2012 9:15

Name
Specific Specific Problem of the alarm(Cabinet Power Supply Abnormal, Cabinet Type and RF Unit
Problem type Mismatch)
Minor The RF unit operates in power derating mode, and thereby affects the system
capacity.
Major The RF unit operates in power derating mode or becomes unavailable, and thereby
affects the system capacity and coverage.
System Actions
If "Specific Problem" is "Cabinet Power Supply Abnormal", the RF unit operates in power derating
mode.
If "Specific Problem" is "Cabinet Type and RF Unit Type Mismatch", the RF unit is set to be
unavailable or in power derating mode.
Possible Causes
The abnormal mains supply leads to an insufficient battery voltage.
The PSU is faulty.
The cabinet type and the RF unit type mismatch.
Procedure
a. Check for the problem in the alarm detailed information on the M2000.
If "Specific Problem" is "Cabinet Type and RF Unit Type Mismatch", go to step 2.
If "Specific Problem" is "Cabinet Power Supply Abnormal", go to step 3.
2. Check whether the cabinet type and the RF unit type match on the M2000.
a. Run the MML command DSP BRDMFRINFO to check the description in the
manufacture information about the RF unit that reports the alarm. Check whether the
RF unit type is MRFUe or MRFUd.
Y => The RF unit type is MRFUe or MRFUd, go to sub-step b.
N => The RF unit type is not MRFUe or MRFUd, Contact Huawei Customer Service
Center.
b. Run the MML command DSP CABMFRINFO to check whether the cabinet description
contains one of the following characters: 303+, 103+, and 202+.
Y => The cabinet description contains one of the following characters: 303+, 103+, and
202+, Contact Huawei Customer Service Center.
N => The cabinet description does not contain any of the following characters: 303+,
381 de 526 13/11/2012 9:15

103+, and 202+, go to step 6.
3. Check the type of power supply for the cabinet on the M2000.
a. Run the MML command DSP BRD to check whether the base station is configured with
the PMU.
Y => The base station is configured with the PMU, go to step 5.
N=> The base station is not configured with the PMU, go to step 4.
4. Check the DC power supply system for the base station cabinet on site.
a. Check whether the DC power system and the mains supply for the base station cabinet
are normal on site.
Y => The power supply for the base station is normal, Contact Huawei Customer
Service Center.
N => The power supply for the base station is abnormal, go to sub-step b.
b. Restore the DC power system and the mains supply for the base station cabinet.
Check Whether the Alarm is Cleared.
5. Check the AC power supply system for the base station cabinet on site.


a. Replace the RF unit that reports the alarm with an RU whose type is not MRFUe or
MRFUd.
Replace the RF Unit.
Service Center.
1.1.210 ALM-26751 RET Antenna Motor Fault

Description
This alarm is reported when the motor of the RET antenna is faulty.
Parameters
382 de 526 13/11/2012 9:15

Parameter
ALD Info. Description of the antenna device
Specific Specific Problem of the alarm(Motor Detection Failed, Motor Permanently Stalled, Motor
Problem Temporarily Stalled)
Minor The RET antenna tilt cannot be regulated.
System Actions
None
Possible Causes
The motor of the RET antenna is faulty.
Procedure
1. Reset the RET antenna on the M2000.
switch of the RF unit connected to the RET antenna.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
2. Replace the RET antenna on site.
a. Replace the RET antenna.

1.1.211 ALM-26752 ALD Hardware Fault

Description
This alarm is reported when the hardware of the antenna device (RET antenna, TMA or SASU) is faulty.
Parameters
Device Type Type of the antenna device (RET, TMA, SASU)
383 de 526 13/11/2012 9:15

Major If the primary hardware of the TMA is faulty, the RX gain amplification function of the
TMA may fail. In this case, the ongoing services carried on the RX channel
associated with the TMA are disrupted.
The SASU malfunctions. As a result, the cell coverage may shrink.
Minor If the hardware of the RET antenna is faulty, the antenna tilt may fail to be regulated.
In this case, the status of the RET antenna cannot be monitored.
If the secondary hardware of the TMA is faulty, the TMA gain cannot be configured.
In this case, the status of the TMA cannot be monitored.
The secondary hardware of the SASU is faulty. As a result, some secondary
functions of the SASU may fail.
System Actions
When the TMA or SASU is severely faulty (alarm severity: major), the TMA or SASU is automatically bypassed.
Meanwhile, the system automatically sets the attenuation on the corresponding RX channel to 0. After the fault in
the TMA or SASU is cleared, the system automatically restores the attenuation on the corresponding RX channel
to the configured value.
Possible Causes
The antenna device (RET antenna or TMA) hardware is faulty.
Procedure
1. Reset the antenna device on the M2000.
switch of the RF unit connected to the antenna device.
switch of the RF unit connected to the antenna device.

1.1.212 ALM-26753 RET Antenna Not Calibrated

Description
This alarm is reported when the base station detects that the RET antenna is not calibrated.
384 de 526 13/11/2012 9:15

Parameters
Minor The cell coverage on the RET antenna is inconsistent with the configuration.
System Actions
None
Possible Causes
A newly installed RET antenna is not calibrated.

The RET antenna is powered off when the antenna tilt is adjusted.
The configuration file of the RET antenna is downloaded again.
Procedure
1. Calibrate the RET antenna on the M2000.
a. Run the MML command CLB RET to calibrate the RET antenna.

1.1.213 ALM-26754 RET Antenna Data Loss

Description
This alarm is reported when the configured data of the RET antenna is lost.
Parameters
385 de 526 13/11/2012 9:15

Minor The RET antenna tilt may fail to be regulated.
System Actions
None
Possible Causes
The RET antenna is powered off during data reconfiguration, which leads to data loss.
The flash memory of the RET antenna is damaged.
The RET antenna is newly installed without the data configuration file.
Procedure
1. Download the configuration file of the RET antenna on the M2000.
a. Run the MML command DLD RETCFGDATA to re-download the configuration file of the
RET antenna.

1.1.214 ALM-26755 TMA Bypass

Description
This alarm is reported when the TMA is automatically bypassed in the case of a critical fault.
Parameters
386 de 526 13/11/2012 9:15

Major After the TMA is bypassed, the receive sensitivity of the RX channel decreases and
the sector coverage shrinks.
System Actions
The TMA is automatically bypassed. Meanwhile, the system automatically sets the attenuation on the
corresponding RX channel to 0.
Possible Causes
The TMA hardware is faulty.
Procedure
1. Reset the TMA on the M2000.
switch of the RF unit connected to the TMA.
a. Replace the TMA.

1.1.215 ALM-26756 SASU VSWR Threshold Crossed

Description
This alarm is reported when the VSWR on the antenna port of the SASU is beyond the VSWR alarm threshold.
Parameters
Subunit No. Number of the Subunit
Major The return loss at the antenna port of the SASU is relatively large. In this case, the
output power of the RF unit decreases and the cell coverage shrinks.
387 de 526 13/11/2012 9:15

System Actions
None
Possible Causes
The feeder connector on the antenna port of the SASU is loose or waterlogged.
The feeder connected to the antenna port of the SASU is bent, deformed, or damaged.
The VSWR detection circuit of the SASU is faulty.
Procedure
1. Reconnect the jumper to the antenna port of the SASU on site.
a. Reconnect the jumper to the antenna port of the SASU. Then, wait for 10 minutes.
2. Check the installation of SASU feeders on site.
a. Check the installation of SASU feeders. Then, wait for 10 minutes.

3. Reset the SASU on site.
switch of the RF unit connected to the SASU.
switch of the RF unit connected to the SASU. Then, wait for 10 minutes.
4. Replace the SASU on site.
a. Replace the SASU.

1.1.216 ALM-26757 RET Antenna Running Data and Configuration

Mismatch
Description
This alarm is reported when the base station detects that the running data of the RET antenna is inconsistent
with the configuration. For example, the actual antenna tilt is inconsistent with the configuration.
Parameters
388 de 526 13/11/2012 9:15

Minor The cell coverage on the RET antenna is inconsistent with the configuration.
System Actions
None
Possible Causes
Because of RET antenna reset or maintenance link disconnection, the data configuration on the base
station is inconsistent with that on the RET antenna.
The configured data of the RET antenna is lost or modified on the base station.
The RET antenna works improperly, resulting in an automatic change of the downtilt.
The configured downtilt exceeds the antenna capability.
Procedure
1. Check the error range of the downtilt alarm on the M2000.
a. Run the MML command LST RETSUBUNIT to query the error range of the downtilt
alarm. Check whether the error range is consistent with the configuration plan.
Y => The error range is consistent with the configuration plan. Go to step 2.
N => The error range is inconsistent with the configuration plan. Go to sub-step b.
b. Run the MML command MOD RETSUBUNIT to modify the error range of the downtilt
alarm of the RET.
2. Set the RET antenna tilt on the M2000.
a. Check whether the configured downtilt exceeds the RET antenna capability.
Y => The configured downtilt exceeds the RET antenna capability. Go to substep b.
N => The configured downtilt does not exceed the RET antenna capability. Go to
substep d.
b. Check whether the downtilt is appropriate.
Y => The downtilt is appropriate, and the RET antenna capability is insufficient. Go to
step 4.
N => The downtilt is inappropriate. Go to substep c.
c. Reconfigure the downtilt.

d. Run the MML command MOD RETTILT to set the RET downtilt.
389 de 526 13/11/2012 9:15



1.1.217 ALM-26758 TMA Running Data and Configuration Mismatch

Description
This alarm is reported when the base station detects that the running data of the TMA is inconsistent with the
configuration. For example, the TMA gain or working mode is inconsistent with the configuration.
Parameters
Minor The receive sensitivity of the RX channel is extremely low or high, resulting in
improper sector coverage.
System Actions
None
Possible Causes
Because of TMA reset or maintenance link disconnection, the data configuration on the base station
is inconsistent with that on the TMA.
The configured data of the TMA is lost or modified on the base station.
The TMA works improperly, resulting in an automatic change of the TMA gain or TMA work mode.
Procedure
390 de 526 13/11/2012 9:15

1. Set the TMA gain on the M2000.
a. Run the MML command MOD TMASUBUNIT to set the TMA gain.
Run the MML command MOD TMASUBUNIT to set the TMA mode.
2. Reset the TMA on the M2000.
a. Replace the TMA.

1.1.218 ALM-26759 SASU Running Data and Configuration Mismatch

Description
This alarm is reported when the base station detects that the running data of the SASU is inconsistent with the
configuration. For example, the working mode, gain, state of the DC switch, or DC load of the SASU is
inconsistent with the configuration.
Parameters
Minor The receive sensitivity is extremely low or high, resulting in improper sector
coverage.
System Actions
None
Possible Causes
Because of SASU reset or maintenance link disconnection, the data configuration on the base station
391 de 526 13/11/2012 9:15

is inconsistent with that on the SASU.
The configured data of the SASU is lost or modified on the base station.
The SASU works improperly, resulting in an automatic change of the SASU gain or SASU work
mode.
Procedure
1. Set the SASU parameters on the M2000.
a. Run the MML command MOD SASUSUBUNIT to set the SASU mode.
Run the MML command MOD SASUSUBUNIT to set the SASU gain.
Run the MML command MOD SASU to set the DC switch state of the SASU.
Run the MML command MOD SASU to set the DC load of the SASU.
2. Reset the SASU on the M2000.

1.1.219 ALM-26760 SASU Bypass

Description
This alarm is reported when the SASU is automatically bypassed in the case of a critical fault.
Parameters
Major After the SASU is bypassed, the receive sensitivity of the RX channel decreases and
392 de 526 13/11/2012 9:15

the sector coverage shrinks.
System Actions
The SASU is automatically bypassed. Meanwhile, the system automatically sets the attenuation on the
corresponding RX channel to 0.
Possible Causes
The SASU hardware is faulty.
Procedure
1. Reset the SASU on the M2000.

1.1.220 ALM-26765 RHUB Hardware Fault

Description
This alarm is reported when the hardware of the RHUB is faulty.
Parameters
Major The RHUB may work improperly. The ongoing services carried on the RHUB may be
disrupted.
393 de 526 13/11/2012 9:15

Minor Some functions of the RHUB may fail and the quality of services carried on the
PRRUs connected to the RHUB may decrease.
System Actions
When a critical component of an RHUB is faulty, the system automatically disables the RHUB.
Possible Causes
The hardware of the RHUB is faulty.
Procedure
1. Reset the RHUB on the M2000.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF to reset the RHUB on the M2000.
2. Replace the RHUB on site.
a. Replace the RHUB.

Service Center.
1.1.221 ALM-26766 RHUB Software Program Error

Description
This alarm is reported when the software program of the RHUB runs improperly, such as suspension.
Parameters
Major The RHUB may work improperly. The RHUB will be automatically reset. The ongoing
services carried on the PRRUs connected to the RHUB are disrupted during reset.
394 de 526 13/11/2012 9:15

System Actions
The system resets the RHUB.
Possible Causes
The software program of the RHUB runs improperly, such as suspension.
Procedure
a. Run the MML command RST BRD to reset the RHUB.

1.1.222 ALM-26767 RHUB Overload

Description
This alarm is reported when the CPU usage of the RHUB is beyond the operating threshold.
Parameters
CPU Load(%) CPU load
Minor The user access success rate and service quality may decrease.
Long-term CPU overload may result in delayed response or timeout of maintenance
tasks of the board.
The test or tracing tasks with low priority may be automatically suspended or
terminated.
System Actions
The flow control is started. The test or tracing tasks with low priority may be automatically suspended or
terminated.
Possible Causes
The user runs too many configuration or maintenance commands frequently on the RHUB.
The user starts too many test or measurement tasks on the RHUB.
The software program of the RHUB runs improperly.
395 de 526 13/11/2012 9:15

Procedure
1. Stop the configuration and maintenance tasks on the RHUB on the M2000.
a. Stop the configuration and maintenance tasks on the RHUB. Then, wait for 15 minutes.
2. Stop the test, tracing, and information collecting tasks in progress on the RHUB on the M2000.
a. Stop all the test, tracing, and information collecting tasks in progress on the RHUB.
Then, wait for 15 minutes.
Run the MML command RST BRDPWROFF on the M2000 to reset the RHUB through
power-off. Then, wait for 15 minutes.
1.1.223 ALM-26768 RHUB Clock Problem

Description
This alarm is reported when the CPRI interface clock of the RHUB is faulty, or the working clock of an internal
component is faulty.
Parameters
Major Some components in the RHUB may work improperly. In certain cases, the ongoing
services carried on the PRRUs connected to the RHUB may be disrupted.
System Actions
When the working clock of a critical component in the RHUB is faulty, the system automatically disables the
396 de 526 13/11/2012 9:15

faulty RHUB.
Possible Causes
The uplink CPRI interface of the RHUB is faulty, resulting in the faulty clock that is extracted at the
CPRI interface.
The clock processor or another component in the RHUB is faulty.
Procedure
a. Check for the correlated alarm on the CPRI port of the RHUB on the M2000:
26783 RHUB CPRI Interface Error
Run the MML command RST BRDPWROFF on the M2000 to reset the RHUB through
power-off.

Service Center.
1.1.224 ALM-26770 UPS Surge Protection Device Fault

Description
This alarm is reported by the external alarm port 0 of the RHUB when the UPS surge protection device (SPD)
fails because its protection circuit is damaged.
Parameters
397 de 526 13/11/2012 9:15

Major The RHUB may be damaged due to possible lightning strikes.
System Actions
None
Possible Causes
The RHUB is not configured with the UPS.
The cable between the RHUB and the SPD is not ready or faulty.
The protection circuit of the SPD fails.
Procedure
1. Check the UPS configuration on site.
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 0.
2. Check the cable connection between the RHUB and the SPD on site.
a. Check whether the cable connection between the RHUB and the SPD is normal.
Y => The cable connection is normal. Go to procedur 3.
N => The cable connection is faulty. Go to sub-step b.
b. Reconnect the cable between the RHUB and the SPD.
3. Replace the SPD on site.
a. Replace the SPD on site.

398 de 526 13/11/2012 9:15

1.1.225 ALM-26771 Mains Breakdown with UPS

Description
This alarm is reported by the external alarm port 1 of the RHUB configured with the UPS when the AC mains
supply fails.
Parameters
Major The RHUB is powered by the UPS when the AC mains supply fails. If the AC mains
supply is unavailable for a long time, the RHUB will be powered off when the battery
is exhausted. In this case, the ongoing services carried on all the PRRUs connected
to the RHUB are disrupted.
System Actions
None
Possible Causes
The monitoring cable between the RHUB and the UPS is faulty.
The AC mains supply for the UPS fails.
Procedure
alarm port 1.
2. Check the monitoring cable between the RHUB and the UPS on site.
a. Check whether the monitoring cable between the RHUB and the UPS is normal.
399 de 526 13/11/2012 9:15

Y => The monitoring cable is normal. Go to step 3.

N => The monitoring cable is faulty. Go to sub-step b.
b. Reconnect the monitoring cable between the RHUB and the UPS.
3. Check the AC mains supply for the UPS on site.
a. Check whether the AC mains supply for the UPS is normal on site.
Y => The AC mains supply for the UPS is normal. Contact Huawei Customer Service
Center.
N => The AC mains supply for the UPS fails. Go to sub-step b.
b. Rectify the fault on the AC mains supply for the UPS. Wait until the AC mains supply is
available.
1.1.226 ALM-26772 UPS Battery Undervoltage

Description
This alarm is reported by the external alarm port 2 of the RHUB configured with the UPS. When the AC mains
supply fails, the UPS starts to work and is powered by the battery. This alarm is reported when the UPS battery
voltage drops to the undervoltage threshold.
Parameters
Major The RHUB continues to operate for an additional short period after this alarm is
reported. When the UPS battery is exhausted, the RHUB is powered off and the
ongoing services carried on all the connected PRRUs are disrupted.
System Actions
None
Possible Causes
400 de 526 13/11/2012 9:15

The AC mains supply malfunctions for a long time, such as power failure, overvoltage, undervoltage,
or excessive frequency deviation.
The battery is damaged.
Procedure
alarm port 2.
2. Check the monitoring cable between the RHUB and the UPS battery on site.
a. Check whether the monitoring cable between the RHUB and the UPS battery is normal.
b. Reconnect the monitoring cable between the RHUB and the UPS battery.
3. Check the AC mains supply for the UPS on site.
a. Check whether the AC mains supply for the UPS malfunctions for a long time, such as
power failure, overvoltage, undervoltage, or excessive frequency deviation.
Y => The AC mains supply for the UPS malfunctions. Go to sub-step b.
N => The AC mains supply for the UPS is normal. Go to step 4.
b. Rectify the fault on the AC mains supply for the UPS. Wait until the AC mains supply is
available.
4. Replace the battery on site.
a. Check whether the battery is damaged according to the maintenance manual offered by
the vendor.
Y => The battery is damaged. Go to sub-step b.
N => The battery is normal. Contact Huawei Customer Service Center.
b. Replace the faulty battery.
401 de 526 13/11/2012 9:15


1.1.227 ALM-26773 UPS Failure

Description
This alarm is reported by the external alarm port 3 of the RHUB configured with the UPS when the UPS is
damaged.
Parameters
Major The UPS bypasses the AC mains supply to the RHUB when this alarm is reported.
The RHUB can continue to operate if the voltage and frequency of AC mains supply
meet the requirements of the RHUB.
System Actions
None
Possible Causes

The UPS is damaged.
Procedure
Y => The UPS is configured. Go to step 2.
N => The UPS is not configured. Go to sub-step b.
alarm port 3.
2. Check the monitoring cable between the RHUB and the UPS on site.
402 de 526 13/11/2012 9:15

a. Check whether the monitoring cable between the RHUB and the UPS is normal.
b. Reconnect the monitoring cable between the RHUB and the UPS.
3. Replace the UPS on site.
a. Replace the UPS on site.

1.1.228 ALM-26774 RHUB AC/DC Maintenance Link Failure

Description
This alarm is reported when the maintenance link for the AC/DC module of the RHUB fails.
Parameters
Major The power supply for the RHUB may fail. In this case, the ongoing services carried
on all the PRRUs connected to the RHUB are disrupted.
System Actions
None
Possible Causes
The AC/DC module is installed improperly.
The AC/DC module is faulty.
Procedure
1. Remove and reinstall the AC/DC module on site.
a. Remove and reinstall the AC/DC module on the RHUB panel. Wait until the RHUB
403 de 526 13/11/2012 9:15

2. Replace the AC/DC module on site.
a. Remove the AC/DC module from the RHUB panel and install a spare AC/DC module.
Wait until the RHUB startup is complete.

Service Center.
1.1.229 ALM-26775 RHUB AC/DC Module Problem

Description
This alarm is reported when the AC/DC module of the RHUB malfunctions.
Parameters
Cause Cause (AC/DC Module Fault, AC/DC Module Protection)
Major The RHUB and connected PRRUs may fail to work normally. In this case, the
ongoing services carried on the PRRUs are disrupted.
System Actions
None
Possible Causes
The AC mains supply malfunctions.
Overtemperature protection for the AC/DC module is triggered because the ambient temperature is
404 de 526 13/11/2012 9:15

extremely high.
The AC/DC module is installed improperly.
The AC/DC module is faulty.
Procedure
1. Check the AC mains supply on site.
a. Use a multimeter to measure the AC mains supply for the RHUB on site. Check whether
the AC mains supply is in overvoltage or undervoltage.
Y => The AC mains supply is in overvoltage or undervoltage. Go to sub-step b.
N => The AC mains supply is normal. Go to step 2.
b. Rectify the fault on the AC mains supply for the RHUB.

2. Check the air vent of the RHUB on site.
a. Check whether the air vent of the RHUB is blocked by dusts or foreign objects.
Y => The air vent is blocked. Go to sub-step b.
N => The air vent is not blocked. Go to step 3.
b. Clean the air vent. Then, wait for 10 minutes.
3. Remove and reinstall the AC/DC module on site.
a. Remove and reinstall the AC/DC module on the RHUB panel. Wait until the RHUB
4. Replace the AC/DC module on site.
a. Remove the AC/DC module from the RHUB panel and install a spare AC/DC module.
Wait until the RHUB startup is complete.

405 de 526 13/11/2012 9:15

Service Center.
1.1.230 ALM-26776 RHUB PSE Power Supply Failure

Description
This alarm is reported when the RHUB detects that the power supply for the PSE is disconnected or in
overcurrent mode.
Parameters
Faulty Port Faulty Port
Cause Cause (Remote supply fault)
Major The PRRUs connected to the PSE may fail to work normally. In this case, the
ongoing services carried on the PRRUs are disrupted.
System Actions
None
Possible Causes
The cable between the RHUB and the PRRU is short-circuited.
The cable between the RHUB and the PRRU is disconnected.

The PRRU is faulty.
The RHUB is faulty.
Procedure
1. Remove and reinstall the cable between the RHUB and the PRRU on site.
a. Remove and reinstall the cable between the RHUB and the PRRU. Power off the PRRU
and then power it on. Wait until the PRRU startup is complete.
2. Use another PSE port on site.
a. Disconnect the cable from the faulty PSE port of the RHUB, and then connect the cable
to another idle PSE port of the RHUB. Power off the PRRU and then power it on. Wait
406 de 526 13/11/2012 9:15

until the PRRU startup is complete.

3. Replace the cable between the RHUB and the PRRU on site.
a. Replace the cable between the RHUB and the PRRU. Power off the PRRU and then
power it on. Wait until the PRRU startup is complete.
4. Replace the PRRU on site.
a. Replace the PRRU.


Service Center.
1.1.231 ALM-26777 RHUB PSE Fault

Description
This alarm is reported when the PSE of the RHUB is faulty.
Parameters
PSE No. PSE No.
Cause Cause (Over Voltage, Below Voltage, Over Temperature Close, Oscillator Fault)
Major The PRRUs connected to the faulty PSE may fail to work normally. In this case, the
ongoing services carried on the PRRUs may be disrupted.
407 de 526 13/11/2012 9:15

System Actions
None
Possible Causes
Overtemperature protection for the PSE is triggered because the ambient temperature of the RHUB
is extremely high.
Procedure
1. Check the overtemperature protection state of the PSE on the M2000.
a. Check whether the fault cause is "Overtemperature Shutdown" according to the alarm
location information.
Y => The fault cause is "Overtemperature Shutdown". Go to step 2.
N => The fault cause is not "Overtemperature Shutdown". Go to step 3.
2. Check the air vent of the RHUB on site.
a. Check whether the air vent of the RHUB is blocked by dusts or foreign objects.
Y => The air vent is blocked. Go to sub-step b.
N => The air vent is not blocked. Go to step 3.
b. Clean the air vent and then wait for 10 minutes.

3. Check the AC/DC module on the M2000.
a. Run the MML command LST ALMAF to query active alarms. Check for 26775 RHUB
AC/DC Module Problem.

Run the MML command RST BRD to reset the RHUB. Wait until the RHUB startup is
complete.
408 de 526 13/11/2012 9:15


Service Center.
1.1.232 ALM-26780 RHUB Optical Module or Electrical Port Not Ready

Description
This alarm is reported when the optical module on the CPRI port of the RHUB is not in position or when the
cable connection on the CPRI optical module or electrical port is not ready.
Parameters
Port CPRI port (Port 0(East), Port 1(West))
Major In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the active CPRI link of lower-level devices is switched over to the standby CPRI link.
Possible Causes
The networking of RHUB and lower-level devices is incorrect. Redundant lower-level devices are
configured.
The optical module on the CPRI port of the RHUB is not in position, or the cable connection on the
CPRI optical module or electrical port is not ready.
The optical module on the CPRI port of the RHUB is faulty, or the cable connected to the CPRI
optical module or electrical port is faulty.
The connecting piece on the CPRI port of the RHUB is faulty.
Procedure
1. Check for redundant lower-level devices on the M2000.
a. Run the MML command LST RRUCHAIN to query the CPRI link networking of the faulty
409 de 526 13/11/2012 9:15

RHUB. According to the site planning, check whether the redundant lower-level devices
are configured.
Y => The redundant lower-level devices are configured. Go to sub-step b.
N => There is no redundant lower-level device. Go to step 2.
b. Run the MML command RMV RRU to remove the redundant lower-level devices.
2. Check the installation of the optical module, or check the cable connection on the CPRI optical
module or electrical port of the RHUB on site.
CPRI optical module or electrical port of the RHUB on site.
b.
b. Install the optical module or connect the cable to the CPRI optical/electrical port.
c. Remove the optical module or the cable connected to the CPRI optical/electrical port,
and then reinstall it properly.
3. Reset the RHUB on site.
a. Power off the RHUB on site and then power it on. Wait until the RHUB startup is

Service Center.
1.1.233 ALM-26781 RHUB Optical Module Type Mismatch

Description
This alarm is reported when the optical module (1.25 Gbit/s or 2.5 Gbit/s) installed on the CPRI port of the
RHUB is not supported by the RHUB.
410 de 526 13/11/2012 9:15

Parameters
Valid Optical Module Type Valid optical module type (1.25 Gbps, 2.5 Gbps)
Installed Optical Module Type Installed optical module type (1.25 Gbps, 2.5 Gbps)
Major The CPRI port of the RHUB does not work normally. The services carried on all the
PRRUs connected to the RHUB are disrupted.
System Actions
None
Possible Causes
The type of the optical module installed on an RHUB is not supported by the RHUB. For example, an RHUB
supports only an optical module of 2.5 Gbit/s, but an optical module of 1.25 Gbit/s is installed on the RHUB.
Procedure
a. Replace the optical module of the RHUB on site. Ensure that the installed optical
module is supported by the RHUB.
1.1.234 ALM-26782 RHUB Optical Module Transmit/Receive Fault

Description
This alarm is reported when the optical transmission on the optical link (at the physical layer) is abnormal
between the RHUB and the peer device (upper-level/lower-level RHUB, RF unit, or BBU).
Parameters
411 de 526 13/11/2012 9:15

Port Type CRPI port type (Uplink, Downlink)
Specific Problem Specific Problem of the alarm(Transmit Error, Reception Error)
System Actions
In ring topology, the current-level RHUB automatically switches to a normal CPRI port if its uplink CPRI port is
faulty.
Possible Causes
The optical module or connector of the current-level RHUB is improperly installed. Or the optical
module is faulty.
The optical connector of the current-level RHUB is dirty.
The current-level RHUB is faulty.
The peer device (upper-level/lower-level RHUB, RF unit, or BBU) is not powered on.
The optical module or connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU)
is improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU) is dirty.
The optical link between the current-level RHUB and the peer device (upper-level/lower-level RHUB,
RF unit, or BBU) is faulty.
Procedure
a. Check for the correlated alarm on the faulty CPRI port of the RHUB on the M2000.
26780 RHUB Optical Module or Electrical Port Not Ready
26781 RHUB Optical Module Type Mismatch
26786 RHUB Optical Module Fault
412 de 526 13/11/2012 9:15

2. Check the CPRI port of the current-level RHUB on site.
a. On the current-level RHUB side, remove and reinstall the optical module and connector
on the faulty CPRI port.
3. Connect the TX and RX terminals of the optical fiber at the current-level RHUB on site.
a. Remove the optical fiber from the optical module of the RHUB. Then, connect the TX
connection of the RHUB. Then, Go to step 4.

d. Power off the RHUB on site and then power it on. Wait until the RHUB startup is
e. Replace the RHUB.

4. Check the running status of the peer device.
a. On the peer device side, check whether the RUN LED on the peer device blinks (ON for
1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). The peer device is running
normally. Go to step 5.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). The peer device is
running improperly. Go to sub-step b.
b. Power cycle the peer device on site. Wait until the RUN LED blinks (ON for 1s and OFF
413 de 526 13/11/2012 9:15

for 1s).
5. Check the CPRI port of the peer device.
a. Remove and reinstall the optical module and connector on the CPRI port of the peer
device.
6. Connect the TX and RX ports of the optical module at the peer device.
a. Remove the optical fiber from the optical module of the peer device. Then, connect the
TX and RX ports of the optical module by using an optical fiber for loopback.
connection of the peer device. Then, Go to step 7.
c. Replace the optical module of the peer device.

d. Power Cycle the Peer Device.

e. Replace the peer device.
a. Check the optical connections between the current-level RHUB and the peer device.
Troubleshoot the improper optical connections, such as fiber bending or deformation.
414 de 526 13/11/2012 9:15


1.1.235 ALM-26783 RHUB CPRI Interface Error

Description
This alarm is reported when the data transmission on the CPRI link (at the link layer) is abnormal between the
RHUB and the peer device (upper-level/lower-level RHUB, RF unit, or BBU).
Parameters
Port Type CRPI port type (Uplink, Downlink)
System Actions
In ring topology, the current-level RHUB automatically switches to a normal CPRI port if its uplink CPRI port is
faulty.
Possible Causes
If the CPRI optical transmission is used, the optical module or connector of the RHUB or peer device
may be improperly installed, or the optical link is faulty.
If the CPRI electrical transmission is used, the cable connector of the RHUB or peer device may be
The RHUB or peer device malfunctions, or the hardware is faulty.
Procedure
415 de 526 13/11/2012 9:15

a. Check for the correlated alarm on the faulty CPRI port of the RHUB on the M2000.
26780 RHUB Optical Module or Electrical Port Not Ready
26781 RHUB Optical Module Type Mismatch
26782 RHUB Optical Module Transmit/Receive Fault
26786 RHUB Optical Module Fault
2. On site, check the cable connections on the CPRI electrical port of the RHUB.
a. Check the cable connections on the CPRI port of the current-level RHUB on site.
If the CPRI electrical transmission is used, Go to sub-step b.
If the CPRI optical transmission is used, Go to step 3.
b. Remove and reinstall the cable on the CPRI electrical port of the current-level RHUB
and the peer device.
c. Replace the cable on the CPRI electrical port.

3. Check the running status of the RHUB or peer device on site.
a. Power off the RHUB on site and then power it on. Wait until the RHUB startup is
b. Power Cycle the Peer Device.

c. Replace the RHUB.
N => The alarm is not cleared. Reinstall the original board. Go to sub-step d.
d. Replace the peer device.
416 de 526 13/11/2012 9:15


Service Center.
1.1.236 ALM-26785 RHUB Optical Interface Performance Degraded

Description
This alarm is reported when the TX/RX performance of the optical module of the RHUB deteriorates.
Parameters
Parameter
Specific Specific Problem of the alarm(Optical Module Performance Degraded, Reception Power too
Problem High, Reception Power too Low)
quality of services carried on the CPRI link of the RHUB may decrease significantly,
or the ongoing services carried on the RHUB may even be disrupted.
quality of services carried on the CPRI link of the RHUB may decrease to some
extent.
System Actions
None
Possible Causes
The optical module or connector of the current-level RHUB is improperly installed. Or the optical
module is aged.
The optical connector of the current-level RHUB is dirty.
The optical module on the CPRI port of the current-level RHUB is not supported by the current-level
RHUB, in terms of type (single-mode or multi-mode) and rate.
The optical module or connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU)
is improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU) is dirty.
The optical module on the CPRI port of the peer device (upper-level/lower-level RHUB, RF unit, or
BBU) is not supported by the peer device, in terms of type (single-mode or multi-mode) and rate.
417 de 526 13/11/2012 9:15

The optical fibers between the current-level RHUB and the peer device (upper-level/lower-level
RHUB, RF unit, or BBU) are bent, deformed, or aged. Or the length of optical fibers is excessive
(longer than 40 km), which leads to a high attenuation of optical signals.
Procedure
1. Check the CPRI port of the current-level RHUB on site.
a. Remove and reinstall the optical module and connector on the CPRI port of the
current-level RHUB.
c. Check whether the optical module on the CPRI port is supported by the current-level
RHUB, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5
Gbit/s).
Y => The optical module is supported by the RHUB. Go to sub-step e.
N => The optical module is not supported by the RHUB. Go to sub-step d.
d. Select the optical module that is supported by the RHUB.

2. Check the CPRI port of the peer device on site.
a. Remove and reinstall the optical module and connector on the CPRI port of the peer
device.
c. Check whether the optical module on the CPRI port is supported by the peer device, in
terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5 Gbit/s).
Y => The optical module is supported by the peer device. Go to sub-step e.
N => The optical module is not supported by the peer device. Go to sub-step d.
d. Select the optical module that is supported by the peer device.
418 de 526 13/11/2012 9:15


a. Check the optical connections between the current-level RHUB and the peer device.
Troubleshoot the improper optical connections, such as fiber bending or deformation.
b. Check the length of the optical link between the current-level RHUB and the peer
device. If the length is excessive (longer than 40 km), add an optical trunk or use
another cascaded RHUB as the optical trunk.
c. Replace the optical fibers between the current-level RHUB and the peer device.
1.1.237 ALM-26786 RHUB Optical Module Fault

Description
This alarm is reported when the optical module on the CPRI port of the RHUB is faulty.
Parameters
Minor The information about the optical module cannot be obtained.
System Actions
None
Possible Causes
419 de 526 13/11/2012 9:15

The optical module of the RHUB is faulty.
Procedure
a. Check for the correlated alarm of the RHUB on the M2000:

26765 RHUB Hardware Fault


1.1.238 ALM-26787 RHUB-PRRU CPRI Interface Error

Description
This alarm is reported when the CPRI interface between the RHUB and the PRRU malfunctions.
Parameters
Major The CPRI interface between the RHUB and the PRRU malfunctions. In this case, the
maintenance link for the PRRU is broken and the PRRU cannot provide the services.
System Actions
None
Possible Causes
The cable connection between the RHUB and the PRRU is not ready.
The cable between the RHUB and the PRRU is faulty.
420 de 526 13/11/2012 9:15

The PRRU is faulty.
The RHUB is faulty.
Procedure
1. Remove and reinstall the cable between the RHUB and the PRRU on site.
a. Remove and reinstall the cable between the RHUB and the PRRU. Power off the PRRU
and then power it on. Wait until the PRRU startup is complete.
2. Use another PSE port of the RHUB on site.
a. Disconnect the cable from the faulty PSE port of the RHUB, and then connect the cable
to another idle PSE port of the RHUB. Power off the PRRU and then power it on. Wait
until the PRRU startup is complete.
3. Replace the cable between the RHUB and the PRRU on site.
a. Replace the cable between the RHUB and the PRRU. Power off the PRRU and then
power it on. Wait until the PRRU startup is complete.


Service Center.
1.1.239 ALM-26810 License Data Loss

Description
This alarm is reported when the NE license becomes invalid.
Parameters
421 de 526 13/11/2012 9:15

None.
Major The NE enters the default license mode. The NE services are subject to the default
license.
System Actions
The system works in default license mode.
Possible Causes
The license is unavailable.
The license is invalid.
The keep-alive period for the temporary license has expired.
Procedure
1. Check the license allocation on the M2000.
a. Check the license allocation on the M2000. Check whether the NE is allocated with the
license resources.
Y => The NE is allocated with the license resources. Go to sub-step c.
N => The NE is not allocated with the license resources. Go to sub-step b.
b. Adjust the license allocation among NEs on the M2000. Allocate the license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
1.1.240 ALM-26811 Configured Capacity Limit Exceeding Licensed Limit

Description
This alarm is reported when the system detects that the configured capacity limit exceeds the licensed limit in
the case of system startup.
Parameters
Operator Index Index of the operator owning the license
Mismatched Control Item Licensed control item that is lower than system configuration
422 de 526 13/11/2012 9:15

Major The NE services are subject to the license.
System Actions
None.
Possible Causes
The configured system capacity exceeds the currently allocated license limit for the system.
Procedure
1. Check the license allocation on the M2000.
a. Check the license allocation on the M2000. Check whether there are license resources
available for the current NE.
Y => There are license resources available for the current NE. Go to sub-step b.
N => There are no license resources available for the current NE. Go to step 2.
b. Adjust the license allocation among NEs on the M2000. Allocate more license resources
to the current NE.
2. Reconfigure the NE data on the M2000.
a. Change the values of NE data to be equal to or less than the limit values in the license.
N => The alarm is not cleared. 3.
3. Order a license.
a. Based on hardware configuration and plan, order a license with a higher capacity limit.
End the alarm handling.
1.1.241 ALM-26812 System Dynamic Traffic Exceeding Licensed Limit

Description
This alarm is reported when the traffic volume of the NE is beyond the capacity limit (configurable) of the license
consistently. This alarm is cleared when the traffic volume of the NE stays below 90% (configurable) of the
capacity limit of the license consistently.
Parameters
Operator Index Index of the operator owning the license
Excessive Control Item Control item that exceeds the licensed limit
423 de 526 13/11/2012 9:15

Usage Current usage
Major The traffic beyond the licensed limit is not allowed.
System Actions
None
Possible Causes
The traffic volume of the NE is beyond the licensed limit.
Procedure
1. Check the setting of the alarm threshold on the M2000.
a. Run the MML command LST LICENSEALMTHD to check whether the setting of the
alarm threshold is proper.
Y => The setting of the alarm threshold is proper. Go to step 2.
N => The setting of the alarm threshold is improper. Go to sub-step b.
b. Run the MML command SET LICENSEALMTHD to modify the alarm threshold.
2. Adjust the allocation of license resources among NEs on the M2000.
a. Check the license allocation on the M2000. Check whether there are license resources
available for the current NE.
Y => There are license resources available for the current NE. Go to sub-step b.
N => There are no license resources available for the current NE. Go to step 3.
b. Adjust the license allocation among NEs on the M2000. Allocate more license resources
to the current NE.
3. Order a license.
a. Based on service requirements, order a license with a higher capacity limit. End the
alarm handling.
1.1.242 ALM-26830 Local User Consecutive Login Retries Failed

Description
This alarm is reported if a local user account is locked when used to log in to an NE through the local
424 de 526 13/11/2012 9:15

maintenance terminal (LMT) due to one of the following reasons: (1) The number of invalid passwords that are
consecutively entered exceeds a pre-defined threshold. The default value of the threshold is three times. (2) The
user name is invalid.
Parameters
Service User Name Name of the service user
Service User IP IP address of the service user
Specific Problem Specific Problem of the alarm(Password Error, Invalid User Name)
Minor The NE is exposed to security risks. The local user may be attacked by invalid users
or the NE is in an insecure network. The NE is vulnerable to attacks.
System Actions
If the user enters a valid user name but incorrect passwords, the corresponding local user account is locked.
Possible Causes
The user has forgotten the login password.
The NE is in an insecure network and is under attack.
Procedure
1. Check the validity of the local user account.
a. Based on the specific problem in the alarm detailed information, check whether the local
user account is valid.
Y => The local user account is valid, go to step 2.
N => The local user account is invalid, contact the network security center.
2. Check the identity of the login user.
a. Contact the owner of the login account. Check whether the login operation is initiated by
the owner.
Y => The login operation is initiated by the owner. Go to sub-step b.
N => The login operation is not initiated by the owner. Turn to the network security
center.
b. Check whether the owner of the account has forgotten the login password.
Y => The owner of the account has forgotten the login password. Go to sub-step c.
N => The owner of the account has not forgotten the login password. Go to sub-step d.
c. Run the MML command RST PWD to update the login password of the user on the
M2000. Inform the owner of the account about the new login password.
d. Run the MML command ULK USR to unlock the user on the M2000.
425 de 526 13/11/2012 9:15

1.1.243 ALM-26832 Peer Certificate Expiry

Description
During the operation of the base station, the alarm is reported when the peer attempts to establish a connection
with the base station by performing security authentication with an expired certificate.
Parameters
Certificate Application Type Certificate Application Type (SSL, IPSec)
Service User IP IP address of the service user
Minor The NE is exposed to security risks, because the certificate of the peer has expired.
System Actions
The base station disconnects itself from the peer that uses an expired certificate.
Possible Causes
The peer certificate is not updated in time, and the peer certificate expires or the peer certificate is
revoked .
An invalid user attempts to connect to the base station with an expired certificate.
Procedure
1. Check the validity of the peer.
a. Check the validity of the peer based on the IP address of the peer that is reported in
the alarm detailed information.
Y => The peer is valid, go to step 2.
N => The peer is invalid, contact the network security center.
2. Update the certificate on the peer side.
a. Contact the staff on the peer side to update the certificate and then reestablish a
connection with the base station.
1.1.244 ALM-26840 Imminent Certificate Expiry

Description
This alarm is reported when the time span between the current time and the expiration time of the loaded
certificate is below the user-defined threshold.
426 de 526 13/11/2012 9:15

Parameters
Certificate Type Type of certificate (Application certificate, Trust certificate, Cross certificate, CRL)
Certificate Name Name of the certificate
Minor The Internet Key Exchange (IKE) or Security Socket Layer (SSL) negotiation
requires a valid certificate. If the base station adopts the IKE/SSL certificate
negotiation, an expired certificate may lead to a negotiation failure and disrupt the
ongoing services.
System Actions
None
Possible Causes
The time of the base station is incorrectly set.
Automatic certificate update fails.
The certificate is about to expire. That is, the time span between the current time and the expiration
time of the loaded certificate is below the user-defined threshold.
Procedure
a. On the M2000, Check for the correlated alarm.

26266 Time Synchronization Failure
N=> The correlated alarm does not exist. Go to step2.

2. Check the time setting of the base station on the M2000.
a. Run the MML command DSP TIME to check whether the current time of the base
station is correct.
Y => The time is correct. Contact Huawei Customer Service Center.
N => The time is incorrect. Go to sub-step b.
b. Run the MML command SET TIME to change the current time of the base station.
427 de 526 13/11/2012 9:15

1.1.245 ALM-26841 Certificate Invalid

Description
This alarm is reported when the NodeB detects any of the following: certificate expiry, certificate file loss,
certificate file damage, certificate not-yet-effective, or a certificate file format error.
Parameters
Parameter
Specific Problem Specific Problem of the alarm(Expired, Lost, Damaged, Format Error, Other, Not Valid
Yet)
Major The Internet Key Exchange (IKE) or Security Socket Layer (SSL) negotiation
requires a valid certificate. If the base station adopts the IKE/SSL certificate
negotiation, an invalid certificate may lead to a negotiation failure and disrupt the
ongoing services.
System Actions
None
Possible Causes
The certificate cannot be loaded.

The certificate expires or the certificate is revoked.
The certificate file is damaged.

The certificate file format is incorrect.
The certificate has not taken effect.
Procedure
a. On the M2000, Check for the correlated alarm.

26266 Time Synchronization Failure
428 de 526 13/11/2012 9:15

2. Check the time setting of the base station on the M2000.
a. Run the MML command DSP TIME to check whether the current time of the base
station is correct.
Y => The time is correct. Go to step 3.
N => The time is incorrect. Go to sub-step b.
b. Run the MML command SET TIME to change the current time of the base station.
3. Check the certificate type that induces the alarm on the M2000.
a. Check the certificate type based on the alarm detailed information.

If "Certificate Type" is "Application certificate". Go to step 4.
If "Certificate Type" is "Trust certificate". Go to step 5.
If "Certificate Type" is "CRL". Go to step 6.
4. Update the certificate on the M2000.
a. Run the MML command REQ DEVCERT to apply for a device certificate.
b. Run the MML command MOD APPCERT to activate the device certificate.
5. Update the trusted certificate on the M2000.
a. Run the MML command RMV TRUSTCERT to remove the trusted certificate.
b. Run the MML command DLD CERTFILE to download the trusted certificate.
c. Run the MML command ADD TRUSTCERT to add the trusted certificate.
6. Update the Certificate Revocation List (CRL) on the M2000.
a. Run the MML command RMV CRL to remove the CRL.
b. Run the MML command DLD CERTFILE to download the CRL.
c. Run the MML command ADD CRL to add the CRL.

1.1.246 ALM-26842 Automatic Certificate Update Failed

Description
This alarm is reported when the automatic certificate update fails.
429 de 526 13/11/2012 9:15

Parameters
Minor The certificate cannot be automatically updated as scheduled, which may bring
security risks. If this alarm is not handled immediately, the certificate will expire in a
period of time and services will be disrupted.
System Actions
None
Possible Causes
The transmission network is faulty.

The task used to automatically update the certificate is not configured according to the configuration
plan, or the IP route is incorrectly configured.
The certificate and CRL server or the Certificate Authority (CA) server is abnormal.
The certificate is invalid(Expired, Damaged, Format Error, Not Valid Yet).
Procedure
a. Check for the correlated alarms of the port used for time synchronization on the M2000.
2. Check the settings of the automatic certificate update on the M2000.
a. On the M2000, determine the certificate type that induces the alarm based on the alarm
detailed information.
If "Certificate Type" is "CRL". Go to sub-step b.
If "Certificate Type" is "Application certificate". Go to sub-step d.
b. Run the MML command DSP CRL to check whether the CRL check task is configured
Y => If the CRL check task is configured according to the configuration plan. Go to step
3.
N => If the CRL check task is not configured according to the configuration plan. Go to
sub-step c.
430 de 526 13/11/2012 9:15

c. Run the MML command RMV CRL,ADD CRL to modify the CRL check task according
d. Run the MML command LST CERTCHKTSK to check whether the certificate check
task is configured according to the configuration plan.
Y => If the certificate check task is configured according to the configuration plan. Go
to step 3.
N => If the certificate check task is not configured according to the configuration plan.
Go to sub-step e.
e. Run the MML command SET CERTCHKTSK to modify the certificate check task
3. Check whether the IP route from the NE to the certificate and CRL server or CA server is
configured on the M2000.
a. Run the MML command LST IPRT to check whether the IP route from the NE to the
certificate and CRL server or CA server exists.
Y => The route exists. Go to step 4.
N => The route does not exist. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route from the NE to the certificate and
CRL server or CA server.
4. Check whether the route from the NE to the certificate and CRL server or CA server is available on
the M2000.
a. Run the MML command PING to start the PING test and check whether the CA server
or the server that stores the certificate and the CRL can be reached.
Y => The CA server or the server that stores the certificate and the CRL can be
reached. Go to step 5.
N => The CA server or the server that stores the certificate and the CRL cannot be
reached. Go to sub-step b.
b. Contact the maintenance center responsible for the routing device. Rectify the route
fault.
5. Check whether the CA server or the server that stores the certificate and the CRL functions
normally.
431 de 526 13/11/2012 9:15

a. Contact the maintenance center responsible for the CA server or the server that stores
the certificate and the CRL. Check the status of the server and rectify the fault.
1.1.247 ALM-28201 Local Cell Blocked

Description
The user can restrict the RNC from using a certain resource or all local cell resources by blocking local cells.
This alarm is reported when local cells are blocked.
Parameters
Local Cell ID Local Cell ID
Minor When a local cell is blocked, the cell cannot carry services.
System Actions
None
Possible Causes
The user runs a command to block the local cell of the NE.
Procedure
1. Block the local cell on the M2000.
a. Run the MML command UBL LOCELL to block the local cell.
1.1.248 ALM-28203 Local Cell Unusable

Description
This alarm is reported when the local cell is unavailable due to physical or logical resource faults.
Parameters
Parameter
Local Cell Local Cell ID

ID
432 de 526 13/11/2012 9:15

Specific Specific Problem of the alarm(Downlink Baseband Resource Unavailable, Baseband-RF

Problem Interface Resource Unavailable, Uplink RF Resource Unavailable, Downlink RF Resource
Unavailable, License Capability Limited, Uplink Common Baseband Resource Unavailable,
Baseband Board Unavailable, RF Board Unavailable, Insufficient CPRI bandwidth)
Major The logical cell cannot be established.
System Actions
None
Possible Causes
User operations: The board is reset, blocked, not inserted, or not configured properly.
Configuration: The local cell configuration exceeds the capability supported by the hardware.
License capability: The license capability is lower than the local cell configuration capability.
Hardware capability: The CPRI bandwidth is insufficient.
Hardware faults: Board hardware is faulty, RF unit hardware is faulty, or the link between the
baseband interface board and RF unit is broken.
Software faults: The software of the board or RF unit malfunctions.
Procedure
a. Locate the cause of alarm based on the alarm location information.

If "Specific Problem" is "Uplink common baseband resource unavailable", go to step 2.
If "Specific Problem" is "Downlink baseband resource unavailable", go to step 3.
If "Specific Problem" is "Baseband-RF interface resource unavailable", go to step 4.
If "Specific Problem" is "Uplink RF resource unavailable" or "Downlink RF resource
unavailable", go to step 5.
If "Specific Problem" is "License capability limited", go to step 7.
If "Specific Problem" is "Baseband board unavailable", go to step 8.
If "Specific Problem" is "RF board unavailable", go to step 9.
If "Specific Problem" is "Insufficient CPRI bandwidth", go to step 10.
2. Rectify the fault of uplink baseband resources on the M2000.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26205 BBU Board Maintenance Link Failure
433 de 526 13/11/2012 9:15

26210 Board Blocked

26265 Base Station Frame Number Synchronization Error
28300 Board Uplink Service Processing Channel Abnormal
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.

c. Run the MML command LST LOCELL to query local cell information, such as the
parameters "UL BB Resource Group No.", "Local Cell Radius", "High Speed Movement
Mode", and "Remote Cell Mode". Run the MML command LST ULGROUP to query the
information about the uplink resource group used by the local cell.
d. Run the MML command DSP BRD to query the property and status of the boards
contained in the uplink resource group.
e. Check whether the number of cells configured in the uplink resource group exceeds the
total number of cells allowed by the uplink resource group. The total number of cells
allowed by the uplink resource group is the accumulated value of the number of cells
supported by all boards in the uplink resource group and cannot exceed the maximum
number of cells allowed by the uplink resource group. For details about the cell
specification supported by the board, see the related hardware description.
Y => The uplink capacity consumed by the local cell exceeds the total capacity of the
uplink resource group. Go to sub-step f.
N => The uplink capacity consumed by the local cell does not exceed the total capacity
of the uplink resource group. Contact Huawei Customer Service Center.
f. Use either of the following methods to modify the configuration:

Method 1: Run the MML command RMV LOCELL to delete the local cell whose
resources are unavailable, and then run the MML command ADD LOCELL to establish
a local cell on another uplink resource group that has sufficient resources.
Method 2: Add the WBBP, and then run the MML command MOD ULGROUP to add
the WBBP to the uplink resource group where the local cell resides.
3. Rectify the fault of downlink baseband resources on the M2000.
active alarms to determine whether the downlink-related alarms of the WBBP exist.
434 de 526 13/11/2012 9:15


26210 Board Blocked
28301 Board Downlink Service Processing Channel Abnormal

c. Run the MML command LST LOCELL to query the local cell information ("DL BB
Resource Group No."), and then run the MML command LST DLGROUP to query the
information about the downlink resource group used by the local cell.
d. Run the MML command DSP BBPTC to query the number of cells supported by the
board in the downlink resource group.
e. Check whether the number of cells configured in the downlink resource group exceeds
the total number of cells allowed by the downlink resource group. The total number of
cells allowed by the downlink resource group is the accumulated value of the number of
cells supported by all boards in the downlink resource group and cannot exceed the
maximum number of cells allowed by the downlink resource group. For details about the
cell specification supported by the board, see the related hardware description.
Y => The number of cells configured for the downlink resource group exceeds the total
number of cells supported by the downlink resource group. Go to sub-step f.
N => The number of cells configured for the downlink resource group does not exceed
the total number of cells supported by the downlink resource group. Contact Huawei
Method 1: Run the MML command RMV LOCELL to delete the local cell whose
resources are unavailable, and then run the MML command ADD LOCELL to establish
a local cell in another downlink resource group that has sufficient resources.
Method 2: Add the WBBP, and then run the MML command MOD DLGROUP to add
the WBBP to the downlink resource group where the local cell resides.
4. Rectify the fault of baseband and RF interface resources on the M2000.
a. Run the MML command LST LOCELL to query the information about the RRU
435 de 526 13/11/2012 9:15

configured for the local cell, and then run the MML commands LST RRU and LST
RRUCHAIN to query the information about the interface board configured for the RRU.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the interface board-related alarms exist.
26210 Board Blocked
Y => The alarms exist. Go to sub-step c.
N => The alarms do not exist. Contact Huawei Customer Service Center.
c. Clear the correlated alarm according to the relevant handling suggestions.

5. Rectify the RF resource fault on the M2000.
alarms related to the RRU/RFU or the baseband board connected to the RRU/RFU.
26210 Board Blocked
26235 RF Unit Maintenance Link Failure
26237 RRU Network Breakpoint
26524 RF Unit PA Overcurrent
26525 RF Unit Temperature Unacceptable
26529 RF Unit VSWR Threshold Crossed
26538 RF Unit Clock Problem
26545 RF Unit TX Channel Switched Off Through Command
26768 RHUB Clock Problem

436 de 526 13/11/2012 9:15

c. Run the MML command LST LOCELL to query the information about the local cell,
such as the RRU or RFU used in the local cell, uplink and downlink UARFCNs, and
maximum output power.
d. Run the MML command DSP RRU to query the specifications of the RRU or RFU.
e. Check whether the uplink and downlink frequencies configured in the local cell are within
the permissible frequency range of the RRU or RFU. (The conversion formula between
UARFCNs and actual frequencies is available in the help information of the MML
command ADD LOCELL.)
Y => Go to sub-step g.
N => Go to sub-step f.
f. Run the MML command MOD LOCELL to change the frequency of the local cell to a
value within the frequency range supported by the RRU or RFU.
g. Check whether the frequency spacing between the current local cell and any of the
other local cells established on the RRU or RFU exceeds the allowed bandwidth of the
RRU or RFU (Minimum frequency spacing = 3.8 MHz; Maximum uplink frequency
spacing = UL Support Band Width - 3.8 MHz; Maximum downlink frequency spacing =
TxUnitNo 0 Support Band Width - 3.8 MHz).
Y => The frequency spacing between the current local cell and any of the other local
cells established on the RRU or RFU exceeds the allowed bandwidth of the RRU or
RFU. Go to sub-step h.
N => The frequency spacing between the current local cell and any of the other local
cells established on the RRU or RFU does not exceed the allowed bandwidth of the
RRU or RFU. Go to sub-step i.
h. Run the MML command MOD LOCELL to modify the frequency of the local cell to
ensure that its frequency spacing with the other cells is within the range supported by
the RRU or RFU.
N => The alarm is not cleared. Go to sub-step i.
i. Check whether the number of cells configured on the same RRU or RFU exceeds the
number of carriers supported by the RRU/RFU.
Y => The number of cells configured on the same RRU or RFU exceeds the number of
carriers supported by the RRU or RFU. Go to sub-step j.
N => The number of cells configured on the same RRU or RFU does not exceed the
number of carriers supported by the RRU or RFU. Go to sub-step k.
j. Run the MML command RMV LOCELL to delete the local cell whose resources are
unavailable, and then run the MML command ADD LOCELL to establish a local cell on
another uplink resource group that has sufficient resources.
N => The alarm is not cleared. Go to sub-step k.
437 de 526 13/11/2012 9:15

k. Check whether the maximum power configured in the local cell is within the power range
supported by the RRU or RFU. In transmit diversity and 0.5/0.5 same zone coverage
mode, the power allocated to each RRU or RFU is equal to half of the total power of
the local cell. Run the MML command DSP RRU to obtain the maximum transmit power
supported by the RRU or RFU.
Note: In the case of a multi-mode RRU or RFU, the RRU or RFU transmit power is
shared by multiple modes. The specifications of the RRU or RFU transmit power may
be restricted to the RRU or RFU hardware and the power lock.
Y => The maximum power configured in the local cell is out of the power range
supported by the RRU or RFU. Go to sub-step l.
N => The maximum power configured in the local cell is within the power range
supported by the RRU or RFU. Go to sub-step m.
l. Run the MML command MOD LOCELL to change the maximum transmit power of the
local cell to a value within the power range supported by the RRU or RFU.
N => The alarm is not cleared. Go to sub-step m.
m. Run the MML command LST RRU to obtain the information about the RRU or RFU
configured on the same chain/ring. Run the MML command LST LOCELL to obtain the
number of cells configured for the same RRU or RFU. Run the MML command DSP
SFP to obtain the transmission rate of the optical module. If the transmission rate is
1.25 Gbit/s, the CPRI interface supports only four local cells (2 TX + 2 RX). If the
transmission rate is 2.5 Gbit/s, the CPRI interface supports only eight local cells (2 TX
+ 2 RX). Check whether the allowed number of local cells on a chain/ring exceeds the
number of local cells corresponding to the transmission rate on the chain/ring.
Y => The allowed number of local cells on a chain/ring exceeds the number of local
cells corresponding to the transmission rate on the chain/ring. Go to sub-step n.
N => The allowed number of local cells on a chain/ring does not exceed the number of
local cells corresponding to the transmission rate on the chain/ring. Contact Huawei
n. Run the MML command RMV LOCELL to delete the local cell whose resources are
unavailable, and then run the MML command ADD LOCELL to establish a local cell on
another RRU or RFU that has sufficient resources on the chain/ring.
N => The alarm is not cleared. Go to sub-step o.
o. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
6. Replace the RRU on site.

438 de 526 13/11/2012 9:15

7. Remotely check the number of local cells supported by the license.
a. Run the MML command DSP LICENSE on the LMT to check whether the value of
"Local Cell Num" specified in the license file is smaller than the number of configured
local cells.
Y => The value of "Local Cell Num" specified in the license file is smaller than the
number of configured local cells. Go to sub-step b.
N => The value of "Local Cell Num" specified in the license file is greater than or equal
to the number of configured local cells. Contact Huawei Customer Service Center.
b. Configure a new license for the NodeB on the M2000 side. For details, see the online
help of ALM-26811 Configured Capacity Limit Exceeding Licensed Limit.
8. Rectify the fault of Baseband Board on the M2000.
active alarms to determine whether the uplink-related alarms of the WBBP exist.
26210 Board Blocked

9. Rectify the fault of RF Board on the M2000.
active alarms to determine whether the alarms related to the RRU or RFU exist.
26210 Board Blocked
439 de 526 13/11/2012 9:15



10. Locate the cause of CPRI bandwidth insufficiency on the M2000.
a. Run the MML command DSP CPRILBR to check whether the line rate of the RRU chain
meets the networking requirement.
Y => The line rate of the RRU chain meets the networking requirement. Go to sub-step
b.
N => The line rate of the RRU chain does not meet the networking requirement. Go to
sub-step c.
b. Query the carrier configuration for UMTS cells and the carrier configurations for cells of
other systems that share CPRI bandwidths with the UMTS cells. Check whether the
carrier configuration exceeds the maximum typical configuration by referring to the
specifications of the MBTS CPRI networking in the 3900 Series Base Station Technical
Description.
Y => The carrier configuration exceeds the maximum typical configuration. Go to
sub-step d.
N => The carrier configuration does not exceed the maximum typical configuration.
c. Check the maximum configuration at each level in the MML command execution result,
and change the optical modules whose rates do not match.
d. Adjust the base station configuration based on the specifications of the MBTS CPRI
networking in the 3900 Series Base Station Technical Description.
1.1.249 ALM-28204 Cell DL Load Simulation Startup

Description
This alarm is reported when the cell simulated load is started.
440 de 526 13/11/2012 9:15

Parameters
Minor The system capacity decreases.
System Actions
None
Possible Causes
The user starts the cell simulated load.
Procedure
1. Stop the cell simulated load.
a. Run the MML command STP DLSIM to stop the cell simulated load.
1.1.250 ALM-28205 Cell Output Power too Low

Description
This alarm is reported when the output power of an NE is at least 2 dB lower than the sum of the common
channel power configured by the RNC.
Parameters
Output Power (0.1 dBm) Output Power (0.1 dBm)
Minor The decrease in the NE output power causes a reduction in the cell coverage.
System Actions
None
441 de 526 13/11/2012 9:15

Possible Causes
The RRU is faulty or aged.
Procedure
1. Reset the RRU on the M2000.
a. According to the cabinet/subrack/slot number displayed in the alarm information, run the
MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
N => The alarm is reported again. Go to step 2.

1.1.251 ALM-28206 Local Cell Capability Decline

Description
This alarm is reported in any of the following cases:

1. In the case of indoor coverage iDBS cell or a local cell(sector configuration mod 0.5/0.5 or mod Independent
Demodulation of Signals from Multiple RRUs) is configured with multiple RRUs. This alarm is reported when one
of the RRUs fails and therefore the capability of the local cell is reduced.
2. The system defines that the maximum number of occupied BBU CPRI ports connected to RRUs in the local
cell is six. This alarm is reported when the number of occupied BBU CPRI ports connected to RRUs exceeds six
and the RTWP of some RRUs fails to be processed.
3. The TX power on the channel of the RRU varies with the number of carriers. When a logical cell exists, this
alarm is reported if the maximum TX power of a local cell exceeds the capacity of RRUs.
4. The local cell does not support two TX channels. This alarm is reported when the user configures two TX
channels in the local cell.
5. The local cell does not support uplink 16QAM. This alarm is reported when the user configures uplink 16QAM
in the local cell.
6. The local cell does not support uplink L2+. This alarm is reported when the user configures uplink L2+ in the
local cell.
7. The local cell does not support downlink 64QAM+MIMO. This alarm is reported when the user configures
downlink 64QAM+MIMO in the local cell.
8. The local cell does not support frequency domain equalization (FDE). This alarm is reported when the user
configures FDE in the local cell.
9. The local cell does not support interference cancellation (IC). This alarm is reported when the user configures
IC in the local cell.
10. The local cell does not support Dual Cell (DC). This alarm is reported when the user configures DC in the
local cell.
11. The local cell does not support BOOST. This alarm is reported when the user configures BOOST in the local
cell.
442 de 526 13/11/2012 9:15

12. The local cell does not support DC+MIMO. This alarm is reported when the user configures DC+MIMO in
the local cell.
13. The local cell does not support ERACH. This alarm is reported when the user configures ERACH in the local
cell.
14. This alarm is reported when certain baseband boards in the uplink resource group used by the local cell do
not support Independent Demodulation of Signals from Multiple RRUs in One Cell.
15. This alarm is reported when the local cell cannot use all available uplink baseband resources in the uplink
resource group.
16. Users have configured the activation and deactivation capability for the supplementary carrier of a cell but
actually the activation and deactivation capability of the supplementary carrier is not supported.
17. Users have configured the HSUPA anti-interference scheduling capability for a cell but actually the cell does
not support the HSUPA anti-interference scheduling capability.
18. The local cell does not support DC-HSUPA. This alarm is reported when the user configures but actually the
cell does not support DC-HSUPA.
19. This alarm is reported when the CPRI bandwidth for UMTS cells is insufficient due to the bandwidth
occupation by cells of other systems.
Parameters
Parameter
Cause (Some RRU(s) in the iDBS cell not usable, Number of occupied BBU CPRI ports connected to
RRUs in the iDBS cell exceeding six, RRU transmit power less than the transmit power required
by the local cell, Two TX channels not supported by the cell, Uplink 16QAM not supported by the
cell, Uplink L2+ not supported by the cell, Downlink 64QAM+MIMO not supported by the cell,
FDE not supported by the cell, IC not supported by the cell, DC not supported by the cell,
BOOST not supported by the cell, DCMIMO not supported by the cell, ERACH not supported by
the cell, MultiRRU Independ DemOver Cell not supported by WBBP Board, Cell can't use all
WBBP Board resources of the uplink resource group, ACT and DEA of Slave Carrier not
supported by the cell, Anti-Interference Scheduling for HSUPA not supported by the cell,
DC-HSUPA not supported by the cell, Insufficient CPRI bandwidth)

ID
Major The coverage of the faulty local cell decreases, the RTWP reported by some RRUs
is discarded, the features configured on the local cell are not supported, or certain
demodulation capabilities of the uplink resource group used by the local cell are
unavailable.
System Actions
None
Possible Causes
Configuration: Parameter settings of the local cell are incorrect, or the local cell capability configured
by the user does not match the actual capability.
License capability: The license capability is lower than the local cell configuration capability.
443 de 526 13/11/2012 9:15

Hardware capability: The hardware capability of the baseband board or RF unit is insufficient, or the
CPRI bandwidth is insufficient.
Hardware faults: In scenarios of multiple RRUs in one cell, the hardware of an RRU that serves the
local cell is faulty, or the link between an RRU and the baseband interface board is broken.
Software faults: The software of the board or RF unit malfunctions.
Procedure

If "Specific Problem" is "Some RRU(s) in the iDBS cell not usable", go to step 2.
If "Specific Problem" is "Number of occupied BBU CPRI ports connected to RRUs in the
iDBS cell exceeding six", go to step 4.
If "Specific Problem" is "RRU transmit power less than the transmit power required by
the local cell", go to step 5.
If "Specific Problem" is "Two TX channels not supported by the cell", go to step 6.
If "Specific Problem" is "Uplink 16QAM not supported by the cell", go to step 7.
If "Specific Problem" is "Uplink L2+ not supported by the cell", go to step 8.
If "Specific Problem" is "Downlink 64QAM+MIMO not supported by the cell", go to step
9.
If "Specific Problem" is "FDE not supported by the cell", go to step 10.
If "Specific Problem" is "IC not supported by the cell", go to step 11.
If "Specific Problem" is "DC not supported by the cell", go to step 12.
If “Specific Problem” is “BOOST not supported by the cell”,go to step 13.
If “Specific Problem” is “DC+MIMO not supported by the cell”,go to step 14.
If “Specific Problem” is “ERACH not supported by the cell”,go to step 15.
Identify the cause of the alarm based on the alarm location information:
If "Specific Problem" is "Independent Demodulation of Signals from Multiple RRUs in
One Cell not supported by certain baseband boards in the uplink resource group used
by the cell", go to step 16
If "Specific Problem" is "All available baseband resources in the uplink resource group
cannot be used by the cell", go to step 17
If “Specific Problem” is “Users have configured the activation and deactivation capability
for the supplementary carrier of a cell but actually the activation and deactivation
capability of the supplementary carrier is not supported.”, go to step 18.
If “Specific Problem” is “Users have configured the HSUPA anti-interference scheduling
capability for a cell but actually the cell does not support the HSUPA anti-interference
scheduling capability.”, go to step 19.
If “Specific Problem” is “Users have configured but actually the cell does not support
DC-HSUPA”, go to step 20.
If "Specific Problem" is "Insufficient CPRI bandwidth", go to step 21.
2. Check for redundant RRUs configured in the local cell on the M2000.
a. Run the MML command LST LOCELL to check the RRUs configured in the faulty local
cell. Check whether redundant RRUs exist according to the network planning.
Y => Redundant RRUs exist. Go to sub-step b.
444 de 526 13/11/2012 9:15

N => Redundant RRUs do not exist. Go to step 3.
b. Run the MML command RMV RRU to delete the redundant RRUs.
3. Rectify the RRU fault on the M2000.
active alarms. Check whether the RRUs configured in the faulty local cell are faulty.
Y => The RRUs are faulty. Go to sub-step b.
N => The RRUs are functional. Contact Huawei Customer Service Center.
4. Rectify the fault that the number of occupied BBU CPRI ports connected to RRUs in the iDBS cell
exceeds six on the M2000.
a. Run the MML command LST LOCELL to query all the RRUs configured in the current
local cell. Check whether the number of occupied BBU CPRI ports connected to RRUs
exceeds six.
Y => The number of occupied BBU CPRI ports connected to RRUs exceeds six. Go to
sub-step b.
N => The number of occupied BBU CPRI ports connected to RRUs does not exceed
six. Contact Huawei Customer Service Center.
b. Reconfigure the position or number of RRUs in the local cell. Ensure that the number of
occupied BBU CPRI ports connected to RRUs is less than or equal to six.
5. Rectify the fault that the power of the RRU does not support the maximum TX power of the local cell
on the M2000.
a. Run the MML command DSP RRU to query the maximum output power of the RRU,
and run the MML command LST LOCELL to query the maximum TX power of the local
cell.
b. When the logical cell is established, check whether the maximum output power of the
RRU is smaller than the maximum TX power of the local cell.
Y => The maximum output power of the RRU is smaller than the maximum TX power of
the local cell. Go to sub-step c.
N => The maximum output power of the RRU is greater than or equal to the maximum
TX power of the local cell. Contact Huawei Customer Service Center.
c. Run the MML command RMV LOCELL to delete the other local cells on this RRU.
445 de 526 13/11/2012 9:15

6. Rectify the fault that the local cell does not support two TX channels on the M2000.
a. Check whether the local cell is required to support two TX channels.

Y => The local cell is required to support two TX channels. Go to sub-step c.
N => The local cell is not required to support two TX channels. Go to sub-step b.
b. Run the MML command MOD LOCELL to modify the configuration so that the local cell
does not support two TX channels.
c. Run the MML command LST LOCELL to query the cabinet/subrack/slot number of the
RRU configured for the local cell.
d. Run the MML command LST RRU to check whether the RRU for the local cell is
configured.
Y => The RRU is configured. Go to sub-step f.
N => The RRU is not configured. Go to sub-step e.
e. Run the MML command ADD RRU to add the RRU.

N => The alarm is not cleared. Go to sub-step f.
f. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the alarms related to the RRU configured for the
local cell exist.
Y => The alarms exist. Go to sub-step g.
g. Clear the correlated alarm according to the relevant handling suggestions.

7. Rectify the fault that the local cell does not support uplink 16QAM on the M2000.
a. Check whether the capability of the local cell to support uplink 16QAM is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support uplink 16QAM.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink 16QAM license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
446 de 526 13/11/2012 9:15

Y => The alarms exist. Go to sub-step d.

N => The alarms do not exist. Go to sub-step e.
d. Clear the correlated alarm according to the relevant handling suggestions.
e. Run the MML command LST LOCELL to check the parameter "UL BB Resource Group
No." of the local cell. Then, run the MML command LST ULGROUP to query the
parameters "Cabinet No. of UL Process Unit", "Subrack No. of UL Process Unit", and
"Slot No. of UL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPd.
Y => The uplink resource group contains the WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPd. The configuration is
incorrect. Go to sub-step f.
f. Add the WBBPd. Then, run the MML command MOD ULGROUP to add the new
WBBPd in the uplink resource group of the local cell.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and uplink 16QAM cannot be supported. Go to
sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
447 de 526 13/11/2012 9:15


8. Rectify the fault that the local cell does not support uplink L2+ on the M2000.
a. Check whether the capability of the local cell to support uplink L2+ is required.
that the local cell does not support uplink L2+.
active alarms to determine whether the uplink L2+ license-related alarms exist.

WBBPb or WBBPd.
Y => The uplink resource group contains the WBBPb or WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPb or WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
new WBBPb or WBBPd in the uplink resource group of the local cell.
the WBBPb or WBBPd.
448 de 526 13/11/2012 9:15

baseband resource is insufficient and uplink L2+ cannot be supported. Go to sub-step i.
9. Rectify the fault that the local cell does not support downlink 64QAM+MIMO on the M2000.
a. Check whether the capability of the local cell to support downlink 64QAM+MIMO is
required.
that the local cell does not support downlink 64QAM+MIMO.
active alarms to determine whether the downlink 64QAM+MIMO license-related alarms
exist.
449 de 526 13/11/2012 9:15

WBBPb or WBBPd.
Y => The uplink resource group contains the WBBPb or WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPb or WBBPd. The
f. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
the WBBPb or WBBPd.
baseband resource is insufficient and downlink 64QAM+MIMO cannot be supported.
Go to sub-step i.
new EBBC/EBBCd in the downlink resource group of the local cell. Run the MML
10. Rectify the fault that the local cell does not support FDE on the M2000.
a. Check whether the capability of the local cell to support FDE is required.
that the local cell does not support FDE (checking that the local cell does not support
450 de 526 13/11/2012 9:15

uplink 16QAM in advance).

active alarms to determine whether the FDE license-related alarms exist.

WBBPd.
Y => The uplink resource group of the local cell contains the WBBPd. Go to sub-step g.
N => The uplink resource group of the local cell does not contain the WBBPd. The
the WBBPb or WBBPd.
baseband resource is insufficient and FDE cannot be supported. Go to sub-step i.
451 de 526 13/11/2012 9:15


11. Rectify the fault that the local cell does not support IC on the M2000.
a. Check whether the capability of the local cell to support IC is required.

that the local cell does not support IC.
active alarms to determine whether the IC license-related alarms exist.

WBBPd.
452 de 526 13/11/2012 9:15

the WBBPb or WBBPd.
baseband resource is insufficient and IC cannot be supported. Go to sub-step i.
12. Rectify the fault that the local cell does not support DC on the M2000.
a. Check whether the capability of the local cell to support DC is required.

Y => The capability is required. Run the MML command LST DLDUALCELLGRP to
obtain a peer local cell that belongs to the same DC group as that for the local cell.
Then, go to sub-step c.
b. Run the MML command RMV DLDUALCELLGRP to change the settings of the local
cell. Ensure that the local cell does not support DC.
active alarms to determine whether the IC license-related alarms exist.

453 de 526 13/11/2012 9:15


e. Run the MML command LST LOCELL to query the information about the local cell.
Check whether the local cell is a distributed cell (a field "RRU Mode" is displayed in the
case of a distributed cell).
Y => The local cell is a distributed cell. Go to sub-step f.
N => The local cell is not a distributed cell. Go to sub-step h.
f. Run the MML command LST LOCELL to query the information about the local cell
(RRU configuration of the distributed cell: number of configured RRUs,
cabinet/subrack/slot number of the first RRU and last RRU). You need to check whether
the RRU configuration of the local cell is the same as that of the peer local cell.
Y => The RRU configuration of the local cell is the same as that of the peer local cell.
Go to sub-step h.
N => The RRU configuration of the local cell is different from that of the peer local cell.
Go to sub-step g.
g. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the RRU configurations of the two local cells in the DC group are the same.
N => The alarm is not cleared. Go to sub-step h.
h. Run the MML command LST LOCELL to query the information about the local cell
(uplink resource group number). Run the MML command LST ULGROUP to query the
uplink resource group used by the local cell. Query the uplink resource group used by
the local cell and the peer local cell respectively, and check whether the WBBPb or
WBBPd are configured in the uplink resource groups of both the two local cells.
Y => Yes. Go to sub-step j.
N => No. Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
N => The alarm is not cleared. Go to sub-step j.
j. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step k.
baseband resource is insufficient and IC cannot be supported. Go to sub-step l.
k. Run the MML command DSP LOCELLRES to query the downlink resource
configuration of the local cell and the peer local cell respectively. Check whether the
downlink resources of the two local cells are established on the same WBBPb or
WBBPd.
Y => Yes. Contact Huawei Customer Service Center.
454 de 526 13/11/2012 9:15

N => No. The downlink baseband resources are insufficient. Go to sub-step m.
l. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
m. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
13. Rectify the fault that the local cell does not support BOOST
a. Check whether the capability of the local cell to support BOOST is required.
that the local cell does not support BOOST.
active alarms to determine whether the BOOST license-related alarms exist.
WBBPd.
455 de 526 13/11/2012 9:15


the WBBPb or WBBPd.
baseband resource is insufficient and BOOST cannot be supported. Go to sub-step i.
14. Rectify the fault that the local cell does not support DC+MIMO.
a. Check whether the local cell needs to support DC+MIMO.

Y => The local cell needs to support DC+MIMO. Go to sub-step c.
N => The local cell does not need to support DC+MIMO. Go to sub-step b.
b. Run the MML command MOD LOCELL to modify the cell configuration to ensure that
the local cell does not support DC+MIMO.
active alarms to determine whether the DC+MIMO license-related alarms exist.
456 de 526 13/11/2012 9:15


e. Run the MML command DSP LOCELL to check whether the local cell supports MIMO.
Y => The local cell supports MIMO. Go to sub-step g.
Y => The local cell does not support MIMO. Go to sub-step f.
f. Rectify the fault that the local cell does not support 2-way transmit diversity by referring
to sub-step 6.
g. Run the MML command DSP LOCELL to check whether the local cell supports DC.
N=> The local cell supports DC. Contact Huawei Customer Service Center.
Y => The local cell does not support DC. Go to sub-step h.
h. Go to sub-step 12 to rectify the fault that the local cell does not support DC.
N=> The alarm is not cleared. Contact Huawei Customer Service Center.
15. Rectify the fault that the local cell does not support ERACH.
a. Check whether the local cell needs to support ERACH.

Y => The local cell needs to support ERACH. Go to sub-step c.
N => The local cell does not need to support ERACH. Go to sub-step b.
b. Run the MML command MOD LOCELL to modify the cell configuration to ensure that
the local cell does not support ERACH.
c. Run the MML command DSP LOCELLRES to obtain parameters "Cabinet No. of UL
Process Unit", "Subrack No. of UL Process Unit", and "Slot No. of UL Process Unit".
Then, run the MML command DSP BRDMFRINFO to check whether uplink baseband
resources are established on the WBBPb or WBBPd.
Y => Uplink baseband resources are established on the WBBPb or WBBPd. Baseband
resources in the local cell are sufficient to support ERACH. Go to sub-step e.
N => Uplink baseband resources are not established on the WBBPb or WBBPd.
Baseband resources in the local cell are insufficient to support ERACH. Go to sub-step
d.
d. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
457 de 526 13/11/2012 9:15

e. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step f.
baseband resource is insufficient and ERACH cannot be supported. Go to sub-step g.
f. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Y => Go to sub-step h.
N => Go to sub-step g.
g. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
h. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
16. Remotely rectify the fault that baseband boards do not support Independent Demodulation of
Signals from Multiple RRUs in One Cell.
a. Run the MML command LST LOCELL to query the information about the local cell and
check the parameter "UL BB Resource Group No.". Run the MML command LST
ULGROUP to query the information about the uplink resource group used by the local
cell and check the following parameters of each board, ""Cabinet No. of UL Process
Unit", "Subrack No. of UL Process Unit", and "Slot No. of UL Process Unit". Then, run
the MML command DSP BRDMFRINFO to check whether the WBBPa is contained in
the uplink resource group used by the local cell.
Y =>The WBBPa is contained in the uplink resource group used by the local cell. Go to
sub-step b.
N => The WBBPa is not contained in the uplink resource group used by the local cell.
b. Run the MML command MOD ULGROUP to remove the WBBPa from the uplink
resource group used by the local cell. The WBBPa does not support Independent
Demodulation of Signals from Multiple RRUs in One Cell. It is recommended that the
WBBPa be replaced by the WBBPb or WBBPd or that the WBBPa is added to another
type of resource group.
458 de 526 13/11/2012 9:15


17. Remotely rectify the fault that the local cell cannot use all available uplink baseband resources in the
uplink resource group.
a. If the NodeB uses over four baseband boards, check whether any of the following
alarms is reported on the board installed in slot 2 or 3:
Board software error alarm
board start failure alarm
board software activation failure alarm
board version mismatch alarm
board type mismatch alarm
board start alarm
If any of the preceding alarms is reported, clear the alarm by referring to related
handling suggestions. After the alarm is cleared, check whether "Specific Problem" is
"All available baseband resources in the uplink resource group cannot be used by the
cell". If the problem persists, Contact Huawei Customer Service Center.
18. Solve the problem remotely that the activation and deactivation capability for the supplementary
carrier of the local cell is not supported.
a. Check whether the local cell is required to support the activation and deactivation
capability for the supplementary carrier.
Y => Go to sub-step b.
N => Go to sub-step d.
active alarms to determine whether license-related alarms concerning activation and
deactivation for the supplementary carrier exist.
Y => Go to sub-step c.
N => Contact Huawei Customer Service Center.

d. Run the MML command SET MACHSPARA to modify the configuration so that the local
cell does not support the activation and deactivation capability for the supplementary
carrier.
19. Solve the problem remotely that the local cell does not support the HSUPA anti-interference
scheduling capability.
a. Check whether the local cell is required to support the HSUPA anti-interference
scheduling capability.
459 de 526 13/11/2012 9:15

active alarms to determine whether license-related alarms concerning HSUPA
anti-interference scheduling exist.
Y => Go to sub-step c.
c. Clear the correlated alarm according to the online help.

d. Run the MML command SET MACEPARA to modify the configuration so that the local
cell does not support HSUPA anti-interference scheduling.
20. Rectify the fault that the local cell does not support DC-HSUPA on the M2000
a. Check whether the local cell is required to support DC-HSUPA.

b. Check whether the cell supports DC. If not, enable DC for the cell.
If the cell supports DC-HSUPA after DC is enabled for the cell, end the task. If not, go
to c.
c. Check whether layer 2 enhancement is configured for the two cells in the DC group. If
not, configure the layer 2 enhancement.
Y=>The alarm is cleared. No further action is required.
N=>The alarm is not cleared. Go to sub-step d.
d. Run the MML command RMV ULDUALCELLGRP to modify the configuration so that
the local cell does not support DC-HSUPA.
Y =>The alarm is cleared. No further action is required.
N =>The alarm is not cleared. Contact Huawei Customer Service Center.
21. Locate the cause of CPRI bandwidth insufficiency on the M2000.
a. Run the MML command DSP CPRILBR to check whether the line rate of the RRU chain
meets the networking requirement.
Y => The line rate of the RRU chain meets the networking requirement. Go to sub-step
b.
N => The line rate of the RRU chain does not meet the networking requirement. Go to
sub-step c.
b. Query the carrier configuration for UMTS cells and the carrier configurations for cells of
460 de 526 13/11/2012 9:15

other systems that share CPRI bandwidths with the UMTS cells. Check whether the
carrier configuration exceeds the maximum typical configuration by referring to the
specifications of the MBTS CPRI networking in the 3900 Series Base Station Technical
Description.
Y => The carrier configuration exceeds the maximum typical configuration. Go to
sub-step d.
N => The carrier configuration does not exceed the maximum typical configuration.
c. Check the maximum configuration at each level in the MML command execution result,
and change the optical modules whose rates do not match.
d. Adjust the base station configuration based on the specifications of the MBTS CPRI
networking in the 3900 Series Base Station Technical Description.
1.1.252 ALM-28207 Carrier Wave Share Failure

Description
When the power sharing among carriers is configured, this alarm is reported if the logical cell does not meet the
power sharing requirements.
Parameters
Parameter
Cause (The source cell is not R99 cell, The target cell is not DPA cell, License capability not support,
Source and target cells use different antennas)
Minor The target cell cannot share the power of the source cell, and the HSDPA services
of the target cell fail to expand.
System Actions
None
Possible Causes
The source cell of the power sharing group is not an R99 cell.
The HSDPA services are not enabled within 10 minutes after the target logical cell in the power
sharing group is established.
The license does not support power sharing.
461 de 526 13/11/2012 9:15

Source and target cells use different antennas.
Procedure

If "Specific Problem" is "The source cell is not an R99 cell", go to step 2.
If "Specific Problem" is "The target cell is not a DPA cell", go to step 3.
If "Specific Problem" is "License capability limited", go to step 4.
If "Specific Problem" is "Source and target cells use different antennas", go to step 5.
2. Check that the HSDPA services are disabled in the source cell.
a. On the RNC, run the MML command LST UCELLHSDPA and check whether the query
result contains the information about the source cell.
Y => The query result contains the information about the source cell. Go to sub-step b.
N => The query result does not contain the information about the source cell. Contact
b. On the RNC, run the MML command LST UCELLHSDPA to check whether the status
of the HSDPA services is ACTIVATED.
Y => The status of the HSDPA services is ACTIVATED. Go to sub-step c.
N => The status of the HSDPA services is not ACTIVATED. Contact Huawei Customer
Service Center.
c. On the RNC, run the MML command DEA UCELLHSDPA to disable the HSDPA
services of the source cell.
3. Check that the HSDPA services are enabled in the target cell.
a. On the RNC, run the MML command LST UCELLHSDPA and check whether the query
result contains the information about the target cell.
Y => The query result contains the information about the target cell. Go to sub-step b.
N => The query result does not contain the information about the target cell. Go to
sub-step c.
b. On the RNC, run the MML command LST UCELLHSDPA to check whether the status
of the HSDPA services is DEACTIVATED.
Y => The status of the HSDPA services is DEACTIVATED. Go to sub-step d.
N => The status of the HSDPA services is not DEACTIVATED. Contact Huawei
c. On the RNC, run the MML command ADD UCELLHSDPA to add the HSDPA services
for the target cell.
d. On the RNC, run the MML command ACT UCELLHSDPA to enable the HSDPA
services for the target cell.
462 de 526 13/11/2012 9:15

4. Remotely check whether the license supports power sharing.
a. Run the MML command DSP LICENSE on the LMT to check whether the license
supports power sharing.
Y => The license supports power sharing. Contact Huawei Customer Service Center.
N => The license does not support power sharing. Go to sub-step b.
b. Configure a new license for the NodeB on the M2000 side. For details, see the online
help of ALM-26811 Configured Capacity Limit Exceeding Licensed Limit.
5. Remotely check whether the antenna configuration supports power sharing.
a. Run the MML command LST LOCELL on the LMT to query the cell carrier information.
Check whether the source and target cells have the same settings of transmit channels.
Y => Same. Go to sub-step h.
N => Different. Go to sub-step b.
b. On the RNC, run the MML command DEA UCELL to deactivate the cell.
c. Run the MML command RMV PAGRP to remove the power sharing relationship
between the original cell and target cell.
d. Run the MML command RMV LOCELL to remove the original cell and target cell
respectively.
e. Run the MML command ADD LOCELL to add the source cell and target cell
respectively, in which the TX channels for carriers of the source cell and target cellmust
be consistent.
f. Run the MML command ADD PAGRP to add the power sharing relationship between
the source cell and target cell.
g. On the RNC, run the MML command ACT UCELL to activate the cell.
N => The alarm is not cleared. Go to sub-step h.
h. Run the MML command LST LOCELL on the LMT to check whether the source and
target cells have the same settings of transmit diversity.
Y => Same. Contact Huawei Customer Service Center.
N => Different. Go to sub-step i.
i. Run the MML command MOD LOCELL on the LMT to modify the settings of transmit
diversity so that the source and target cells have the same settings of transmit diversity.
1.1.253 ALM-28209 Cell No Traffic

Description
This alarm is reported when no traffic is detected in the local cell during the specified period of time or when
there is no cell traffic because the KPI values indicating the corresponding logical cell access are abnormal.
463 de 526 13/11/2012 9:15

Parameters
Parameter
Cause (Cell No Receive Radio link Setup Message, Cell No Receive Radio link Setup Message with
First Rls Flag for Long Time, Baseband Uplink Channel Soft Fault, Downlink Baseband
Resource Fault, High Error Rate of IUB Transmission, Radio link Setup Fail, Others)
Minor Services of the current cell are affected and system self-healing fails.
System Actions
None
Possible Causes
NodeB hardware is faulty.
NodeB software is defective.
A NodeB component experiences a soft failure.
A third-party device, such as the antenna system, TMA, trunk amplifier, or transmission relay, is
faulty.
The parameter settings for the cell are incorrect on the NodeB or RNC.
On occasions such as public holidays or termination of large-scale gatherings, this alarm may be
reported with the alarm cause 0 or 1.
Procedure
1. Check for correlated Board alarms on the M2000.

Y => The correlated alarm exists. Go to step 2.
2. Check the type of the board alarm on the M2000.
a. If the alarm 26200 Board Hardware Fault or 26532 RF Unit Hardware Fault is reported,
go to step 3.
b. If the 26203 Board Software Program Error or 26533 RF Unit Software Program Error
is reported, go to step 4.
3. On the M2000, check the type and status of the board where the correlated hardware alarm is
reported.
a. Run the MML command DSP BRD on the M2000 to display the type of the board
where the alarm is reported. Check whether the displayed board type is an RF board
and the MML command RST BRDPWROFF has not been executed on the RF board
within 2 hours before the alarm was reported.
Y => Run the MML command RST BRDPWROFF on the M2000 to power cycle the RF
464 de 526 13/11/2012 9:15

board. No further action is required.

N => Go to substep b.
b. Replace the faulty board onsite. Check whether the cell becomes functional onsite.
Y => The cell becomes functional. No further action is required.
N => The cell still has no traffic. Contact Huawei Customer Service Center.
4. Check whether the alarm board need be reset.
a. Check whether the board has been reset within 2 hours before the alarm was initially
reported.
Y => Go to step 6.
N => Reset the board. No further action is required.
5. Check the alarm cause.
a. Check whether the alarm cause is 0 (Radio Link Setup messages not received within a
long period) or 1 (Radio Link Setup messages with the First Rls flag not received within
a long period).
Y => The alarm cause is 0 or 1. Go to step 7.
N => The alarm cause is not 0 or 1. Go to step 6.
6. Check whether the NodeB need be reset.
a. Check whether the NodeB has been reset within 2 hours before the alarm was initially
reported.
Y => Contact Huawei Customer Service Center..
N => Reset the NodeB. No further action is required.
7. Check whether users can access the cell onsite.
a. On the M2000, confirm with the network planning engineers whether the alarm is
reported on occasions such as holidays or termination of large-scale gatherings.
Y => No further action is required.
N => Go to substep b.
b. On the M2000, confirm with the network planning engineers whether the parameter
settings of the cell have been adjusted.
Y => Request the network planning engineers to perform further actions.
1.1.254 ALM-28210 Frequency Separation Configuration Mismatch

Description
When a logic cell is established, this alarm is reported if the system detects that the frequency separation
between the frequency of the cell to be established and the frequency of the existing cell carried by the RF unit
is less than the parameter "Frequency Bandwidth" of the RF unit.
Parameters
465 de 526 13/11/2012 9:15

Type (UpLink, DownLink)
Cause (UU Frequency Gap Less than Minimum Gap)
Minor The services carried by the cell configured with incorrect frequency separation may
be affected. In this case, the KPIs related to network performance may deteriorate.
System Actions
None
Possible Causes
The data configuration is wrong.
Procedure
1. Check the frequency configuration of the cell on the M2000.
a. On the NodeB side, run the MML command LST LOCELL to query the parameters "UL
Frequency Channel Number" and "DL Frequency Channel Number" of the local cell that
is carried by the RF unit with incorrect frequency configuration. Check whether the cell
frequency configuration is consistent with the network planning.
Y => The cell frequency configuration is consistent with the network planning. Go to
step 2.
N => The cell frequency configuration is inconsistent with the network planning. Go to
sub-step b.
b. On the NodeB side, run the MML command DSP LOCELL to query the ID of the logic
cell corresponding to the local cell that is carried by the RF unit with incorrect frequency
configuration.
c. On the RNC side, run the MML command DEA UCELL to deactivate the logic cell.
Then, run the MML command MOD UCELLFREQUENCY to change the cell
frequencies. Ensure that the frequency configuration is consistent with the network
planning.
d. On the NodeB side, run the MML command MOD LOCELL to change the frequencies
of the local cell. Ensure that the frequency configuration is consistent with the network
planning.
2. Check the frequency bandwidth on the M2000.
a. Run the MML command LST FREQBWH to query the parameter "Frequency
Bandwidth" of the RF unit. Check whether the cell frequency separation of the RF unit is
466 de 526 13/11/2012 9:15

greater than or equal to the parameter "Frequency Bandwidth" of the RF unit.

Y => The cell frequency separation of the RF unit is greater than or equal to the
parameter "Frequency Bandwidth". Contact Huawei Customer Service Center.
N => The cell frequency separation of the RF unit is less than the parameter
"Frequency Bandwidth". Go to sub-step b.
b. Run the MML command DSP LICENSE to check whether "Flexible frequency
separation between G/U" is supported.
Y => "Flexible frequency separation between G/U" is supported. Go to sub-step c.
N => "Flexible frequency separation between G/U" is not supported. Purchase and
activate the license. Then, go to sub-step c.
c. Run the MML command SET FREQBWH to modify the parameter "Frequency
Bandwidth" of the RF unit. Ensure that the cell frequency separation of the RF unit is
greater than or equal to the parameter "Frequency Bandwidth" of the RF unit.
1.1.255 ALM-28211 Cell Configuration Abnormal

Description
This alarm is reported when the uplink or downlink ARFCN fails to be configured or the total maximum transmit
power of all local cells on an RF unit exceeds the maximum transmit power of the RF unit.
Parameters
Parameter
Specific Specific Problem of the alarm(Uplink Frequency Configured Failure, Downlink Frequency
Problem Configured Failure, Cell Power Exceeded RF Unit Power Specification)
Major If the uplink or downlink frequency configuration fails, services cannot be connected.
If the total cell power exceeds the RF unit specifications, KPIs deteriorate when the
logical cell is operating under heavy traffic. In serious scenarios, the power amplifier
will be damaged.
System Actions
None.
Possible Causes
The RF unit which carries the services in the local cell does not support the uplink or downlink
ARFCN of the local cell.
The uplink and downlink ARFCNs of the local cell conflict with ARFCNs of a cell in another mode.
The total maximum transmit power of faulty local cells and other local cells exceeds the maximum
467 de 526 13/11/2012 9:15

transmit power of the RF unit.
Procedure
a. Identify the alarm cause based on alarm location information.

If "Specific Problem" is "Uplink Frequency Configured Failure" or "Downlink Frequency
Configured Failure", go to step 2.
If "Specific Problem" is "Cell Power Exceeded RF Unit Power Specification", go to step
5.
2. Remotely check whether the RF unit used by the sector supports the ARFCNs configured in the
local cell.
a. Run the MML command LST LOCELL to query the information about the uplink and
downlink ARFCNs configured in the local cell.
b. Run the MML command DSP TXBRANCH and DSP RXBRANCH to query the maximum
and minimum ARFCNs supported by the RF unit in the uplink and downlink.
c. Check whether the uplink and downlink ARFCNs configured in the local cell are within
the allowed ARFCN range of the RF unit.
Y => Both the uplink and downlink ARFCNs are in the allowed ARFCN range of the RF
unit. Contact Huawei Customer Service Center.
N => The uplink or downlink ARFCN is not in the allowed ARFCN range of the RF unit.
Go to step 3.
3. Remotely check whether the uplink or downlink ARFCN is consistent with that in network planning.
a. Check whether the uplink or downlink ARFCN is consistent with that in network planning.
Y => Both the uplink and downlink ARFCNs are consistent with those in network
planning. Go to sub-step b.
N => Either the uplink or downlink ARFCN is inconsistent with that in network planning.
Go to step 4.
b. Check whether the RF unit is properly installed.

Y => The RF unit is properly installed. Contact Huawei Customer Service Center.
N => The RF unit is improperly installed. Go to sub-step c.
c. Replace the RF unit on site.

Replace the RF unit.
4. Remotely modify the uplink or downlink ARFCN configured in the local cell.
a. Run the MML command DEA UCELL on the RNC side to deactivate the logical cell
corresponding to the local cell.
b. Run the MML command MOD LOCELL on the NodeB side to modify the uplink or
downlink ARFCN configured in the local cell to ensure that both the uplink and downlink
ARFCNs are consistent with those in network planning.
c. Run the MML command MOD UCELLFREQUENCY on the RNC side to modify the
uplink or downlink ARFCN to ensure that the uplink and downlink ARFCNs configured in
468 de 526 13/11/2012 9:15

the logical cell are consistent with those configured in the local cell.
d. Run the MML command ACT UCELL on the RNC side to activate the logical cell.
5. Check that the maximum transmit power of the local cell conforms to the network plan on the
M2000.
a. Run the MML command LST LOCELL to query the maximum transmit power of the
faulty local cell.
b. Check whether the maximum transmit power of the local cell conforms to the network
plan.
Note: For a multi-mode RF unit, the maximum transmit power is shared by multiple
modes. If multiple local cells share the transmit channel of one RF unit, the power of the
transmit channel is shared by the local cells. The maximum transmit power of the RF
unit may be restricted to the hardware and the power lock of the RF unit.
Y => The maximum transmit power of the local cell conforms to the network plan. Go to
step 7.
N => The maximum transmit power of the local cell does not conform to the network
plan. Go to step 6.
6. Change the maximum transmit power of the local cell based on the network plan on the M2000.
a. For a cell that has been activated, run the MML command DEA UCELL on the RNC to
deactivate the cell.
b. On the NodeB, run the MML command MOD LOCELL to change the information about
the maximum transmit power of the local cell to ensure that the total maximum transmit
power of all local cells on a transmit channel of an RF unit does not exceed the
maximum transmit power of the RF unit. In addition, the maximum transmit power of the
local cell cannot be smaller than the transmit power specified in the network plan.
c. On the RNC, run the MML command MOD UCELL to change the cell power information
to ensure that the maximum transmit power conforms to the network plan and the
power does not exceed the maximum transmit power of the local cell.
d. On the RNC, run the MML command ACT UCELL activate the cell.
Y => The alarm is cleared and is not reported again. No further action is required.
N => The alarm is not cleared or is reported again. Contact Huawei Customer Service
Center.
7. Replace the original RF unit with an RF unit with the larger maximum transmit power onsite.
a. Replace the original RF unit with an RF unit with the larger maximum transmit power to
ensure that the total maximum transmit power of all local cells on a transmit channel of
an RF unit does not exceed the maximum transmit power of the RF unit.
469 de 526 13/11/2012 9:15

1.1.256 ALM-28221 IMB Local Cell Blocked

Description
The user can restrict the RNC from using a certain resource or all IMB(Integrated Mobile Broadcast) local cell
resources by blocking local cells. This alarm is reported when IMB local cells are blocked.
Parameters
Minor When a IMB local cell is blocked, the cell cannot carry services.
System Actions
None
Possible Causes
The user runs a command to block the IMB local cell of the NE.
Procedure
1. Block the IMB local cell on the M2000.
a. Run the MML command UBL LOCELL to block the local cell.
1.1.257 ALM-28223 IMB Local Cell Unusable

Description
This alarm is reported when the system detects that a IMB(Integrated Mobile Broadcast) local cell is
unavailable.
Parameters
Parameter
Specific Specific Problem of the alarm(Downlink Baseband Resource Unavailable, Baseband-RF

Problem Interface Resource Unavailable, Uplink RF Resource Unavailable, Downlink RF Resource
Unavailable, License Capability Limited, Uplink Common Baseband Resource Unavailable)
470 de 526 13/11/2012 9:15

Major The logical cell cannot be established.
System Actions
None
Possible Causes
The baseband board is faulty.
The RF unit is faulty.

Data configuration is incorrect.
Baseband resources are insufficient.

License capability not enough.
Procedure

If "Specific Problem" is "Downlink baseband resource unavailable", go to step 2.
If "Specific Problem" is "Baseband-RF interface resource unavailable", go to step 3.
If "Specific Problem" is "Downlink RF resource unavailable", go to step 4.
2. Rectify the fault of downlink baseband resources on the M2000.
active alarms to determine whether the downlink-related alarms of the WBBP exist.
26210 Board Blocked
28301 Board Downlink Service Processing Channel Abnormal
471 de 526 13/11/2012 9:15

c. Run the MML command LST IMBLOCELL to query the IMB local cell information ("DL
BB Resource Group No."), and then run the MML command LST DLGROUP to query
the information about the downlink resource group used by the IMB local cell.
d. Run the MML command DSP BBPTC to query the number of cells supported by the
board in the downlink resource group.
e. Check whether the number of cells configured in the downlink resource group exceeds
the total number of cells allowed by the downlink resource group. The total number of
cells allowed by the downlink resource group is the accumulated value of the number of
cells supported by all boards in the downlink resource group and cannot exceed the
maximum number of cells allowed by the downlink resource group. For details about the
cell specification supported by the board, see the related hardware description.
Y => The number of cells configured for the downlink resource group exceeds the total
number of cells supported by the downlink resource group. Go to sub-step f.
N => The number of cells configured for the downlink resource group does not exceed
the IMB total number of cells supported by the downlink resource group. Contact

Method 1: Run the MML command RMV IMBLOCELL to delete the IMB local cell
whose resources are unavailable, and then run the MML command ADD IMBLOCELL
to establish a IMB local cell in another downlink resource group that has sufficient
resources.
Method 2: Add the WBBP, and then run the MML command MOD DLGROUP to add
the WBBP to the downlink resource group where the IMB local cell resides.
3. Rectify the fault of baseband and RF interface resources on the M2000.
a. Run the MML command LST IMBLOCELL to query the information about the RRU
configured for the IMB local cell, and then run the MML commands LST RRU and LST
RRUCHAIN to query the information about the interface board configured for the RRU.
active alarms to determine whether the interface board-related alarms exist.
26210 Board Blocked
Y => The alarms exist. Go to sub-step c.
472 de 526 13/11/2012 9:15


4. Rectify the RF resource fault on the M2000.
active alarms to determine whether the alarms related to the RRU or RFU exist.
26210 Board Blocked
26545 RF Unit TX Channel Switched Off Through Command

c. Run the MML command LST IMBLOCELL to query the information about the IMB local
cell, such as the RRU or RFU used in the local cell, uplink and downlink UARFCNs, and
maximum output power.
d. Run the MML command DSP RRU to query the specifications of the RRU or RFU.
e. Check whether the u downlink frequencies configured in the local cell are within the
permissible frequency range of the RRU or RFU. (The conversion formula between
UARFCNs and actual frequencies is available in the help information of the MML
command ADD IMBLOCELL.)
Y => Go to sub-step g.
N => Go to sub-step f.
f. Run the MML command MOD IMBLOCELL to change the frequency of the local cell to
a value within the frequency range supported by the RRU or RFU.
g. Check whether the frequency spacing between the current IMB local cell and any of the
473 de 526 13/11/2012 9:15

other IMB local cells established on the RRU or RFU exceeds the allowed bandwidth of
the RRU or RFU (Minimum frequency spacing = 3.8 MHz; Maximum downlink frequency
spacing = TxUnitNo 0 Support Band Width - 3.8 MHz).
Y => The frequency spacing between the current IMB local cell and any of the other
IMB local cells established on the RRU or RFU exceeds the allowed bandwidth of the
RRU or RFU. Go to sub-step h.
N => The frequency spacing between the current IMB local cell and any of the other
IMB local cells established on the RRU or RFU does not exceed the allowed bandwidth
of the RRU or RFU. Go to sub-step i.
h. Run the MML command MOD IMBLOCELL to modify the frequency of the IMB local
cell to ensure that its frequency spacing with the other cells is within the range
supported by the RRU or RFU.
N => The alarm is not cleared. Go to sub-step i.
i. Check whether the number of cells configured on the same RRU or RFU exceeds the
number of carriers supported by the RRU/RFU.
Y => The number of cells configured on the same RRU or RFU exceeds the number of
carriers supported by the RRU or RFU. Go to sub-step j.
N => The number of cells configured on the same RRU or RFU does not exceed the
number of carriers supported by the RRU or RFU. Go to sub-step k.
j. Run the MML command RMV IMBLOCELL to delete the IMB local cell whose
resources are unavailable, and then run the MML command ADD IMBLOCELL to
establish a IMB local cell on another resource group that has sufficient resources.
N => The alarm is not cleared. Go to sub-step k.
k. Check whether the maximum power configured in the IMB local cell is within the power
range supported by the RRU or RFU.
Y => The maximum power configured in the IMB local cell is out of the power range
supported by the RRU or RFU. Go to sub-step l.
N => The maximum power configured in the IMB local cell is within the power range
supported by the RRU or RFU. Go to sub-step m.
l. Run the MML command MOD IMBLOCELL to change the maximum transmit power of
the IMB local cell to a value within the power range supported by the RRU or RFU.
N => The alarm is not cleared. Go to sub-step m.
m. Run the MML command LST RRU to obtain the information about the RRU or RFU
configured on the same chain/ring. Run the MML command LST IMBLOCELL to obtain
the number of cells configured for the same RRU or RFU. Run the MML command DSP
SFP to obtain the transmission rate of the optical module. If the transmission rate is
1.25 Gbit/s, the CPRI interface supports only 8 IMB local cells. If the transmission rate
is 2.5 Gbit/s, the CPRI interface supports only 16 IMB local cells . Check whether the
allowed number of local cells on a chain/ring exceeds the number of IMB local cells
corresponding to the transmission rate on the chain/ring.
474 de 526 13/11/2012 9:15

Y => The allowed number of local cells on a chain/ring exceeds the number of IMB local
cells corresponding to the transmission rate on the chain/ring. Go to sub-step n.
N => The allowed number of local cells on a chain/ring does not exceed the number of
IMB local cells corresponding to the transmission rate on the chain/ring. Contact Huawei
n. Run the MML command RMV IMBLOCELL to delete the IMB local cell whose
resources are unavailable, and then run the MML command ADD IMBLOCELL to
establish a IMB local cell on another RRU or RFU that has sufficient resources on the
chain/ring.
N => The alarm is not cleared. Go to sub-step o.
o. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.

1.1.258 ALM-28224 IMB Cell Output Power too Low

Description
This alarm is reported when the output power of an NE is at least 2 dB lower than the sum of the common
channel power configured by the RNC.
Parameters
Output Power (0.1 dBm) Output Power (0.1 dBm)
Minor The decrease in the NE output power causes a reduction in the cell coverage.
System Actions
None
475 de 526 13/11/2012 9:15

Possible Causes
The RRU is faulty or aged.
Procedure
a. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
N => The alarm is reported again. Go to step 2.

1.1.259 ALM-28225 IMB Local Cell Capability Decline

Description
This alarm is reported in any of the following cases:

1. This alarm is reported when one of the RRUs fails and therefore the capability of the IMB(Integrated Mobile
Broadcast) local cell is reduced.
2. Users have configured the activation and deactivation capability for the supplementary carrier of a cell but
actually the activation and deactivation capability of the supplementary carrier is not supported.
Parameters
Parameter
Cause (Some RRU(s) in the iDBS cell not usable, Number of occupied BBU CPRI ports connected to
RRUs in the iDBS cell exceeding six, RRU transmit power less than the transmit power required
by the local cell, Two TX channels not supported by the cell, Uplink 16QAM not supported by the
cell, Uplink L2+ not supported by the cell, Downlink 64QAM+MIMO not supported by the cell,
FDE not supported by the cell, IC not supported by the cell, DC not supported by the cell,
BOOST not supported by the cell, DCMIMO not supported by the cell, ERACH not supported by
the cell, MultiRRU Independ DemOver Cell not supported by WBBP Board, Cell can't use all
WBBP Board resources of the uplink resource group, ACT and DEA of Slave Carrier not
supported by the cell, Anti-Interference Scheduling for HSUPA not supported by the cell)

ID
Major The coverage of the faulty local cell decreases, the RTWP reported by some RRUs
is discarded, the features configured on the local cell are not supported, or certain
demodulation capabilities of the uplink resource group used by the local cell are
476 de 526 13/11/2012 9:15

unavailable.
System Actions
None
Possible Causes
Redundant RRUs are configured in the IMB local cell.

A certain RRU in the IMB local cell is faulty.
The number of occupied BBU CPRI ports connected to RRUs in the IMB local cell exceeds six, the
maximum number defined in the system.
A logical cell exists, and the maximum TX power of the IMB local cell exceeds the maximum output
power of RRUs.
The parameter settings are incorrect in the local cell.
The baseband resources are insufficient.
Due to limited capabilities of ports interconnecting baseband boards, certain demodulation

capabilities of the uplink resource group used by the local cell are unavailable.
Procedure

If "Specific Problem" is "Some RRU(s) in the cell not usable", go to step 2.
If "Specific Problem" is "Number of occupied BBU CPRI ports connected to RRUs in the
iDBS cell exceeding six", go to step 4.
If "Specific Problem" is "RRU transmit power less than the transmit power required by
the IMB local cell", go to step 5.
2. Check for redundant RRUs configured in the local cell on the M2000.
a. Run the MML command LST IMBLOCELL to check the RRUs configured in the faulty
IMB local cell. Check whether redundant RRUs exist according to the network planning.
Y => Redundant RRUs exist. Go to sub-step b.
N => Redundant RRUs do not exist. Go to step 3.
b. Run the MML command RMV RRU to delete the redundant RRUs.
3. Rectify the RRU fault on the M2000.
active alarms. Check whether the RRUs configured in the faulty local cell are faulty.
Y => The RRUs are faulty. Go to sub-step b.
N => The RRUs are functional. Contact Huawei Customer Service Center.
477 de 526 13/11/2012 9:15


4. Rectify the fault that the number of occupied BBU CPRI ports connected to RRUs in the cell
exceeds six on the M2000.
a. Run the MML command LST IMBLOCELL to query all the RRUs configured in the
current IMB local cell. Check whether the number of occupied BBU CPRI ports
connected to RRUs exceeds six.
Y => The number of occupied BBU CPRI ports connected to RRUs exceeds six. Go to
sub-step b.
N => The number of occupied BBU CPRI ports connected to RRUs does not exceed
six. Contact Huawei Customer Service Center.
b. Reconfigure the position or number of RRUs in the IMB local cell. Ensure that the
number of occupied BBU CPRI ports connected to RRUs is less than or equal to six.
5. Rectify the fault that the power of the RRU does not support the maximum TX power of the local cell
on the M2000.
a. Run the MML command DSP RRU to query the maximum output power of the RRU,
and run the MML command LST IMBLOCELL to query the maximum TX power of the
IMB local cell.
b. When the logical cell is established, check whether the maximum output power of the
RRU is smaller than the maximum TX power of the IMB local cell.
Y => The maximum output power of the RRU is smaller than the maximum TX power of
the IMB local cell. Go to sub-step c.
N => The maximum output power of the RRU is greater than or equal to the maximum
TX power of the local cell. Contact Huawei Customer Service Center.
c. Run the MML command RMV IMBLOCELL to delete the other local cells on this RRU.
1.1.260 ALM-28226 IMB Cell Configuration Abnormal

Description
This alarm is reported when the uplink or downlink ARFCN fails to be configured or the total maximum transmit
power of all local cells on an RF unit exceeds the maximum transmit power of the RF unit.
Parameters
Parameter
478 de 526 13/11/2012 9:15

Specific Specific Problem of the alarm(Uplink Frequency Configured Failure, Downlink Frequency
Problem Configured Failure, Cell Power Exceeded RF Unit Power Specification)
Major Service access in the cell possibly fails.
System Actions
None.
Possible Causes
The RF unit which carries the services in the IMB(Integrated Mobile Broadcast) local cell does not
support the uplink or downlink ARFCN of the local cell.
The uplink and downlink ARFCNs of the local cell conflict with ARFCNs of a cell in another mode.
The total maximum transmit power of faulty local cells and other local cells exceeds the maximum
transmit power of the RF unit.
Procedure
a. Identify the alarm cause based on alarm location information.

If "Specific Problem" is "Downlink Frequency Configured Failure", go to step 2.
If "Specific Problem" is "Cell Power Exceeded RF Unit Power Specification", go to step
5.
2. Remotely check whether the RF unit used by the sector supports the ARFCNs configured in the IMB
local cell.
a. Run the MML command LST IMBLOCELL to query the information about the sector to
which the IMB local cell belongs and information about the uplink and downlink ARFCNs
configured in the IMB local cell.
b. Run the MML command LST IMBSEC to query the configuration information of the RF
unit used by the sector.
c. Run the MML command DSP TXBRANCH to query the maximum and minimum
ARFCNs supported by the RF unit in the downlink.
d. Check whether the downlink ARFCNs configured in the IMB local cell are within the
allowed ARFCN range of the RF unit.
Y => Both the downlink ARFCNs are in the allowed ARFCN range of the RF unit.
N => The downlink ARFCN is not in the allowed ARFCN range of the RF unit. Go to
step 3.
3. Remotely check whether the uplink or downlink ARFCN is consistent with that in network planning.
a. Check whether the downlink ARFCN is consistent with that in network planning.
Y => Both the downlink ARFCNs are consistent with those in network planning. Go to
sub-step b.
N => Either the downlink ARFCN is inconsistent with that in network planning. Go to
479 de 526 13/11/2012 9:15

step 4.
b. Check whether the RF unit is properly installed.

Y => The RF unit is properly installed. Contact Huawei Customer Service Center.
N => The RF unit is improperly installed. Go to sub-step c.
c. Replace the RF unit on site.

4. Remotely modify the uplink or downlink ARFCN configured in the local cell.
a. Run the MML command DEA UCELL on the RNC side to deactivate the logical cell
corresponding to the local cell.
b. Run the MML command MOD IMBLOCELL on the NodeB side to modify the downlink
ARFCN configured in the IMB local cell to ensure that both the downlink ARFCNs are
consistent with those in network planning.
c. Run the MML command MOD IMBLOCELL on the RNC side to modify the downlink
ARFCN to ensure that the downlink ARFCNs configured in the logical cell are consistent
with those configured in the IMB local cell.
d. Run the MML command ACT UCELL on the RNC side to activate the logical cell.
5. Check that the maximum transmit power of the local cell conforms to the network plan on the
M2000.
a. Run the MML command LST LOCELL to query the maximum transmit power of the
faulty local cell.
b. Check whether the maximum transmit power of the local cell conforms to the network
plan.
Note: For a multi-mode RF unit, the maximum transmit power is shared by multiple
modes. If multiple local cells share the transmit channel of one RF unit, the power of the
transmit channel is shared by the local cells. The maximum transmit power of the RF
unit may be restricted to the hardware and the power lock of the RF unit.
Y => The maximum transmit power of the local cell conforms to the network plan. Go to
step 7.
N => The maximum transmit power of the local cell does not conform to the network
plan. Go to step 6.
6. Change the maximum transmit power of the local cell based on the network plan on the M2000.
a. For a cell that has been activated, run the MML command DEA UCELL on the RNC to
deactivate the cell.
b. On the NodeB, run the MML command MOD LOCELL to change the information about
the maximum transmit power of the local cell to ensure that the total maximum transmit
power of all local cells on a transmit channel of an RF unit does not exceed the
maximum transmit power of the RF unit. In addition, the maximum transmit power of the
local cell cannot be smaller than the transmit power specified in the network plan.
480 de 526 13/11/2012 9:15

c. On the RNC, run the MML command MOD UCELL to change the cell power information
to ensure that the maximum transmit power conforms to the network plan and the
power does not exceed the maximum transmit power of the local cell.
d. On the RNC, run the MML command ACT UCELL activate the cell.
Y => The alarm is cleared and is not reported again. No further action is required.
N => The alarm is not cleared or is reported again. Contact Huawei Customer Service
Center.
7. Replace the original RF unit with an RF unit with the larger maximum transmit power onsite.
a. Replace the original RF unit with an RF unit with the larger maximum transmit power to
ensure that the total maximum transmit power of all local cells on a transmit channel of
an RF unit does not exceed the maximum transmit power of the RF unit.
1.1.261 ALM-28230 Base Station Service Overload

Description
This alarm is reported when the ratio of the number of times the system cannot provide services to the number
of connection attempts is higher than the preset threshold (10% by default).
Parameters
None.
Minor The hardware capability is insufficient. Some terminals cannot use the services
provided by the network.
System Actions
None
Possible Causes
The NodeB receives calls too frequently and its signaling capability cannot handle.
The NodeB serves too many online users and its hardware cannot provide adequate uplink or
downlink CEs.
Procedure
1. Query the service overload alarm threshold on the M2000.
a. Run the MML command LST TRAFFICOVERLOADTHD to query the service overload
alarm threshold.
Check whether the service overload alarm threshold is set properly.
481 de 526 13/11/2012 9:15

Y=> The service overload alarm threshold is set properly. Contact Huawei Customer
Service Center to implement capacity expansion.
N=> The service overload alarm threshold is not set properly. Go to step 2.
2. Set the service overload alarm threshold on the M2000.
a. Run the MML command SET TRAFFICOVERLOADTHD. Set the service overload
alarm threshold based on service characteristics.
N => The alarm is not cleared. Contact Huawei Customer Service Center to implement
capacity expansion.
1.1.262 ALM-28244 GPS Receiver Hardware Fault

Description
The alarm is reported when the system detects that the hardware of the GPS receiver is faulty.
Parameters
Minor The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The hardware of the GPS receiver is faulty.
Procedure
1. Reset the GPS receiver on the M2000.
a. Run the MML command RST SATCARD to reset the GPS receiver.
2. Replace the GPS receiver on site.
a. Replace the GPS receiver.
482 de 526 13/11/2012 9:15


1.1.263 ALM-28245 GPS Receiver Antenna Power Problem

Description
The alarm is reported when the system detects that the antenna of the GPS receiver is not powered on.
Parameters
System Actions
None
Possible Causes
The power supply loop of the antenna of the GPS receiver is faulty.
Procedure
1. Wait for five minutes, and then check that the system can automatically clear the alarm.
a. Wait for five minutes. Then, check whether the system automatically clears the alarm.

483 de 526 13/11/2012 9:15

1.1.264 ALM-28246 GPS Receiver Antenna Fault

Description
The alarm is reported when the antenna system between the NodeB and the GPS receiver is faulty.
Parameters
Specific Problem Specific Problem of the alarm(Antenna Shorted, Antenna Open)
System Actions
None
Possible Causes
The antenna system of the GPS receiver is not properly connected or is short-circuited.
The GPS receiver itself is faulty.
Procedure
a. Locate the cause of the alarm based on the alarm location information.
If "Specific Problem" is "Antenna Shorted", go to step 2.
If "Specific Problem" is " Antenna Open", go to step 4.
2. Disconnect the antenna system from the GPS receiver on site, and then wait for five minutes to
check that the alarm is cleared.
a. Disconnect the feeder at the antenna connector of the GPS receiver, and then wait for
five minutes.
Y => The alarm is cleared. The antenna system is faulty. Go to step 3.
N => The alarm is not cleared. The GPS receiver itself is faulty. Go to step 6.
3. Clear the fault in the antenna system on site.
a. Check the antenna system. Clear the fault of short circuit if any.
484 de 526 13/11/2012 9:15

b. Reconnect the antenna system to the GPS receiver.

4. Check that the antenna system is properly connected to the GPS receiver on site.
a. Check whether the antenna system is properly connected to the GPS receiver.
Reconnect the antenna system if necessary.
Y => The alarm is cleared. Reconnect the antenna system to the GPS receiver. The
alarm handling is complete.

1.1.265 ALM-28247 GPS Receiver Software Program Error

Description
The alarm is reported when the system detects that the software program error occurs in the GPS receiver.
Parameters
Parameter
485 de 526 13/11/2012 9:15

Specific Specific Problem of the alarm(Position Solution Invalid, Clock Steering Disabled, Clock Model
Problem Invalid, Almanac Invalid)
System Actions
None
Possible Causes
The calendar of the GPS receiver is invalid.

The system mistakenly executes some commands.
Software error occurs in the GPS receiver.
Procedure
1. Wait for five minutes, and then check that the system can automatically clear the alarm.
a. Wait for five minutes. Then, check whether the system automatically clears the alarm.

1.1.266 ALM-28248 GPS Receiver Position Not Locked

Description
This alarm is reported when the GPS receiver is searching for a satellite or cannot automatically search for a
satellite.
Parameters
486 de 526 13/11/2012 9:15

Minor The GPS receiver cannot lock the satellite. The NodeB fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
The GPS receiver is automatically searching for a satellite.
The auto-search function of the GPS receiver fails.
Procedure
1. Check that the GPS receiver is automatically searching for a satellite on the M2000.
a. Run the MML command LST GPS to list the preset search duration of the GPS
receiver.
Wait for some time. Then, check whether the alarm is cleared.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
487 de 526 13/11/2012 9:15


1.1.267 ALM-28249 GPS Receiver Maintenance Link Failure

Description
The alarm is reported when the communication between the NodeB and the GPS receiver fails.
Parameters
Minor The NodeB cannot receive the valid GPS data and thus fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
The cable connections between the NodeB and the GPS receiver are faulty.
Procedure
1. Check that the GPS receiver is properly connected to the NodeB on site.
a. Check whether the GPS receiver is properly connected to the NodeB. If necessary,
reconnect the cables properly between the NodeB and the GPS receiver.
b. Replace the cables between the NodeB and the GPS receiver.

488 de 526 13/11/2012 9:15


1.1.268 ALM-28250 GPS Receiver Initialization Configuration Failure

Description
The NodeB performs the initialization configuration on the GPS receiver. This alarm is reported when the GPS
receiver fails to respond or responds unexpectedly upon receiving the controlling message from the NodeB.
Parameters
Minor The NodeB cannot receive the valid GPS data and thus fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
Software error occurs in the GPS receiver.
Procedure

1.1.269 ALM-28253 Ethernet Link Abnormal

Description
You can test the connectivity of the NodeB. This alarm is reported if the connectivity test is unsuccessful.
489 de 526 13/11/2012 9:15

Parameters
MEP Port No. MEP Port No.
MEP Port Type (Ethernet Port, Ethernet Trunk Group)
Major The transmission link is disconnected, and the ongoing services carried on the link
are disrupted.
System Actions
The system attempts to select another route.
Possible Causes
The network transmission is faulty.
Procedure
25895 Ethernet Trunk Group Fault
2. Check that the network transmission is normal on the M2000.
a. Run the MML command CFMTRACE to perform a loopback test at the ends of the
disconnected link and check whether the loopback test is successful.
Y => The test is successful. Contact the maintenance personnel of the transport
network.
N => The test fails. Go to sub-step b.
b. Contact the maintenance personnel of the transport network to obtain the networking
configuration, and then run the MML command CFMTRACE to perform a loopback test
at the ends of the disconnected link and NodeB and check whether each
MIP(Maintenance Intermediate Point).
490 de 526 13/11/2012 9:15

Y => All the MIPs are reachable. Contact Huawei Customer Service Center.
N => Certain MIPs are unreachable. Contact the maintenance personnel of the
transport network.
1.1.270 ALM-28255 Transport Configuration Failure

Description
This alarm is reported when the system detects that one transport object cannot be configured to the board and
therefore the configuration data cannot take effect.
Parameters
Parameter
Transmission (Ethernet Port, Device IP Address, IP Path, Local IP, OM Channel, IP Route, E1/T1,
Object Type Resource Group, PPP Link, MLPPP Group, MLPPP Link, IP PM Session, IMA Group, IMA
Link, AAL2 Node, AAL2 Path, VCG, SAAL Link, Ethernet Trunk Group, SCTP Link, UNI Link,
Tree Link PVC, Fractional ATM Link, IP to Resource Group Mapping, Line Rate, HSDPA Flow
Control Para, Ethernet Trunk Link, BFD Session, CFM MA, CFM MEP, CFM Remote MEP,
CFM Binding IP, Timeslot Cross, STM-1, HSUPA Flow Control Para, CFM MD, TUNNEL,
Service IP)
Fault Code Fault Code
Object No. Object No.
Major The transport object for which this alarm is generated is unavailable and the ongoing
services carried on the transport object are disrupted.
System Actions
The transport object cannot carry any upper layer objects.
Possible Causes
The base station is in BOOTP state.
The hardware of the board is faulty.
The license capacity is lower than the system configuration.
The configuration data planning is incorrect.
Procedure
491 de 526 13/11/2012 9:15



2. Check for this alarm in the lower layer objects of the bearer object on the M2000.
a. Determine whether the faulty object belongs to the following types: AAL2 path, device
IP address, Fractional ATM link, IMA link, IP path, PPP link, SAAL link, SCTP link,
structured CES channel, networking PVC, time slot cross, non-structured CES channel,
UNI link, transmission resource group, IP clock switch, IP clock link, AAL2 node, AAL2
adjacent node,and Trunk link.
Y => The faulty object belongs to one of the preceding types. Go to sub-step b.
N => The faulty object does not belong to these types. Go to step 3.
b. Run the MML command LST ALMAF to check whether this alarm is generated on the
lower layer object that carries the faulty object.
Y => The alarm is generated on the lower layer object that carries the faulty object. Go
to sub-step c
Y => The alarm is not generated on the lower layer object that carries the faulty object.
Go to step 3.
c. Handle the alarm based on the processing suggestions.
3. Check that the type of the board type supports the configuration parameters of the object on the
M2000.
a. Based on the type of the transport object in the alarm information, run the
corresponding MML command to query the status of the transport object. Run the MML
command DSP BRD or DSP BRD to query the type of the board where the object
resides. Check the user manual to determine whether the type of the board supports
the configuration parameters of the object.
Y => The type of the board supports all the configuration parameters of the object.
N => The type of the board does not support certain configuration parameters of the
object. Go to sub-step b.
b. Modify the configuration of the object according to the user manual.

1.1.271 ALM-28300 Board Uplink Service Processing Channel Abnormal
492 de 526 13/11/2012 9:15

Description
This alarm is reported when uplink service processing channel of a board is faulty.
Parameters
Parameter
Subrack Subrack number of the monitoring device

No.
Specific Specific Problem of the alarm(Dedicated Channel Demodulation Unit 1 Faulty, Access Channel
Problem Demodulation Unit Faulty, AI Data Transmission Failure, DSP BFN Abnormal, APP Measurement
Failure, CHIP Register Configuration Abnormal, CPU-DSP Coding Unit Interface Frame Error,
SIR Data Transmission Failure, DSP Timing Interrupt Abnormal, DSP Peripheral Equipment
Abnormal, DSP External Interface Abnormal, CHIP Register Configuration Abnormal, DSP-Chip
Interrupt Timeout, PRBUS Interface Abnormal, Chip BFN Abnormal, DSP Kernel Abnormal, CPU
and DSP Disconnected, Decoding Module Internal Error, Decoding Module External Interface
Abnormal, ARM Disconnected, Dedicated Channel Demodulation Unit 0 Faulty)
Major The faulty uplink resources are unavailable, resulting in decreased system capacity
or service interruption.
System Actions
When this alarm is generated, the system sets the corresponding uplink processing channel as unavailable
according to the fault code reported. If other uplink resources are available in the baseband subrack, the
services carried by the uplink processing channel are migrated to another uplink resource. If other uplink
resources are unavailable or the uplink processing channel becomes unavailable due to service migration failure,
the cells carried by the uplink processing channel become unavailable. In this case, the system automatically
notifies the RNC that the local cells are unavailable.
Possible Causes
The uplink dedicated demodulation channel, access demodulation channel, or encoding channel is faulty.
Procedure
a. Note: Resetting the board disrupts some or even all the ongoing services of the base
Run the MML command RST BRD to reset the board.
493 de 526 13/11/2012 9:15


Service Center.
1.1.272 ALM-28301 Board Downlink Service Processing Channel

Abnormal
Description
This alarm is reported when the downlink service processing channel of a board is faulty.
Parameters
Parameter
Subrack Subrack number of the monitoring device

No.
Specific Specific Problem of the alarm(CHIP Register Configuration Abnormal, Power Control Interface
Problem from FPGA to DL ASIC Abnormal, Modulation Interface from DL ASIC to FPGA Abnormal, DSP
Internal Error, Downlink Service Processing Unit Faulty, CHIP Register Configuration Abnormal,
DSP Kernel Abnormal, DSP Internal Abnormal, DSP External Interface Abnormal, Chip External
Interface Abnormal, CPU and DSP Disconnected, PRBUS Interface Abnormal, ARM
Disconnected, RTWP Channel Abnormal, Downlink Resource Coding Abnormal, PGBUS
Interface Abnormal, CPU-DSP Coding Unit Interface Frame Error)
Major The faulty downlink resources are unavailable, resulting in decreased system
capacity or service interruption.
Minor The faulty downlink resources are unavailable. The system still has resources that
are working normally. The system capacity decreases.
System Actions
When this alarm is generated, the system sets the corresponding downlink processing channel as unavailable
according to the fault code reported. If other downlink resources are available in the baseband subrack, the
services carried by the downlink processing channel are migrated to another downlink resource. If other
downlink resources are unavailable or the downlink processing channel becomes unavailable due to service
migration failure, the cells carried by the downlink processing channel become unavailable. In this case, the
system automatically notifies the RNC that the local cells are unavailable.
Possible Causes
494 de 526 13/11/2012 9:15

The downlink encoding channel is faulty.
Procedure

Service Center.
1.1.273 ALM-28302 Board BFN Abnormal

Description
This alarm is reported when the system detects that the frame number received on the board for synchronization
has errors.
Parameters
Parameter
Specific Specific Problem of the alarm(Downlink DSP's ASIC Power Abnormal, BFN of the Decoding
Problem Unit Abnormal, BFN of the Dedicated Channel Demodulation Unit 0 Abnormal, BFN of the
Access Channel Demodulation Unit Abnormal, BFN of the Encoding Unit Abnormal)
Major Certain or all service resources of the faulty board are unavailable. The system
capacity decreases.
System Actions
When this alarm is generated, the system sets the corresponding service processing unit as unavailable
according to the fault code reported.
495 de 526 13/11/2012 9:15

Possible Causes
The board is not properly connected with the subrack.
Certain service processing units of the board are faulty.
Procedure
2. Remove and reinstall the faulty board on site.
a. Reseat the Board.


4. Remove and reinstall the main control board on site.

a. Replace the main control board.

6. Replace the BBU subrack on site.
a. Replace the subrack.

496 de 526 13/11/2012 9:15

1.1.274 ALM-28303 WBBP-WBBP Interface Abnormal

Description
This alarm is generated when the service data channel between the WBBPs is faulty.
Parameters
TX Board Slot No. TX Board Slot No.
RX Board Slot No. RX Board Slot No.
Major Certain or all service resources of the faulty board are unavailable. The system
capacity decreases.
System Actions
The system sets the service data channel between the WBBPs as unavailable.
Possible Causes
The transmit board is faulty.
The receive board is faulty.
The BBU subrack is faulty.
Procedure
1. Reset the receive board on the M2000.
Run the MML command RST BRD to reset the receive board.
2. Remove and reinstall the receive board on site.

3. Replace the receive board on site.
497 de 526 13/11/2012 9:15


4. Remove and reinstall the transmit board on site.

5. Replace the transmit board on site.

6. Replace the BBU subrack on site.
a. Replace the subrack.

1.1.275 ALM-28329 RF Unit Input Power Abnormal

Description
This alarm is reported when the RRU detects that the voltage of its power supply is higher than or lower than the
rated voltage.
Parameters
Major The RRU may fail to work normally.
System Actions
None
Possible Causes
498 de 526 13/11/2012 9:15

The input voltage of the RRU is too high or too low.
The AC/DC module in the RRU is faulty.
Procedure
a. Run the MML command RST BRDPWROFF to reset the RRU module on which the
alarm is generated.
2. Check the power supply of the RRU on site.
a. Check the power supply of the RRU for errors.


1.1.276 ALM-28330 RF Unit Over Backward Power Alarm

Description
This alarm is reported when the PRRU detects that the reflected power of the antenna connector is too high.
Parameters
VSWR Alarm Threshold (0.1) VSWR Alarm Threshold (0.1)
VSWR (0.1) VSWR (0.1)
Average Forward Power (0.1 dBm) Average Forward Power (0.1 dBm)
Average Backward Power (0.1 dBm) Average Backward Power (0.1 dBm)
Major The uplink or downlink performance of the PRRU is degraded and the services
499 de 526 13/11/2012 9:15

carried by the PRRU may be interrupted.
System Actions
None
Possible Causes
The connection of the PRRU feeder is incorrect.

The reflected power detection circuit of the PRRU is faulty.
Procedure
1. Check the antenna feeder on site.
a. Check the Installation of Feeders for the RF Unit.

Note: Only after the cell is reestablished, the PRRU starts to detect the reflected
power. Therefore, you need to wait for a longer time.

Service Center.
1.1.277 ALM-28350 Board Configuration Inconsistent with Resource

Group Configuration
Description
When one of the following situations occurs in the system, this alarm is generated.
The system detects that available uplink or downlink baseband processing resources are not added to any uplink
or downlink resource groups.
The system detects that a certain board that cannot be added to multiple UL resource groups is added to
multiple UL resource groups.
Parameters
Parameter
Cause (Uplink Process Unit Inconsistent with Uplink Resource Group Configuration, Downlink Process
Unit Inconsistent with Downlink Resource Group Configuration, This baseband board cannot
belong to multiple uplink resource groups)
500 de 526 13/11/2012 9:15

Major If "Specific Problem" is "Uplink process unit inconsistent with uplink resource group
configuration" or "Downlink process unit inconsistent with downlink resource group
configuration", the services cannot be carried by the baseband processing resources
that are not added to a resource group. As a result, the baseband processing
capability is insufficient and the UE access is difficult. If "Specific Problem" is
"Baseband board not belonging to multiple UL resource groups", the baseband
processing resource is used by one of the UL group resources.
System Actions
None
Possible Causes
The UE configuration is incomplete. Not all the baseband processing resources are added to the resource group.
A certain board that cannot be added to multiple UL resource groups is added to multiple UL resource groups.
Procedure
1. Identify the cause of the alarm on the M2000.
a. Identify the cause of the alarm based on the alarm location information.
If "Specific Problem" is "Uplink process unit inconsistent with uplink resource group
configuration", go to step 2.
If "Specific Problem" is "Downlink process unit inconsistent with downlink resource
group configuration", go to step 3.
If "Specific Problem" is "Baseband board not belonging to multiple UL resource groups",
go to step 4.
2. Add all the uplink baseband processing resources to the uplink resource group on the M2000.
a. Run the MML command LST ULGROUP to query the configuration of the uplink
resource group. Run the MML command DSP BRD to query the status of the board and
determine whether there are any available uplink baseband processing resources that
are not added to the uplink resource group.
Y => Some available uplink baseband processing resources are not added to the uplink
resource group. Go to substep b.
N => All available uplink baseband processing resources are added to the uplink
resource group. Contact Huawei Customer Service Center.
b. Run the MML command MOD ULGROUP to add an idle baseband processing board to
the configured uplink baseband resource group (RGOPTYPE=ADDULPUNIT).
3. Add all the downlink baseband processing resources to the downlink resource group on the M2000.
a. Run the MML command LST DLGROUP to query the configuration of the downlink
resource group. Run the MML command DSP BRD to query the status of the board and
determine whether there are any available downlink baseband processing resources
that are not added to the downlink resource group.
Y => Some available downlink baseband processing resources are not added to the
501 de 526 13/11/2012 9:15

downlink resource group. Go to substep b.

N => All available downlink baseband processing resources are added to the downlink
resource group. Contact Huawei Customer Service Center.
b. Run the MML command MOD DLGROUP to add an idle baseband processing board to
the configured downlink baseband resource group (RGOPTYPE=ADDULPUNIT).
4. Check the board capability and board configurations.
a. Check whether the board needs to be added to multiple UL resource groups in base
station configuration plan.
Y => The board needs to be added to multiple UL resource groups in base station
configuration plan. Go to substep b.
N => The board does not need to be added to multiple UL resource groups in base
station configuration plan. Go to substep c.
b. Run the MML command DSP BBPTC to query the capability of the baseband board.
Based on the command output and the board capability described in the Hardware
Description, determine whether the board can be added to two uplink transmission
resource groups.
Y => The board can be added to two uplink transmission resource groups. Contact
N => The board cannot be added to two uplink transmission resource groups. Go to
step 5.
c. Run the MML command MOD ULGROUP to delete the board that is not needed in the
resource group.
5. Replace the baseband board with a board that can be added to two UL resource groups onsite.

1.1.278 ALM-28354 Transport Backup Not Support

Description
This alarm is reported when the system detects that the current board cannot serve as the backup of the
transmission of another board after the board is started.
Parameters
Parameter
502 de 526 13/11/2012 9:15

Cause (Back-board not support, Board Type Mismatch, Board not support, Sub-board Type
Mismatch)
Specific Specific Problem of the alarm(Back-board not support, Board Type Mismatch, Board not
Problem support, Sub-board Type Mismatch)
Major The active/standby transmission is not supported, thus affecting the reliability of the
system transmission.
System Actions
None
Possible Causes
The backplane does not support the active/standby transmission.
The board types are inconsistent.

The board does not support the active/standby transmission.
The subboard does not support the active/standby transmission.
Procedure
1. Check the configuration data on the M2000.
a. Check the configuration data to determine whether the active/standby transmission

configuration is correct.
Y => The configuration is correct. Contact Huawei Customer Service Center.
N => The configuration is incorrect. Go to sub-step b.
b. Modify the Data Configuration File.

1.1.279 ALM-28355 Data Configuration File Error

Description
This alarm is reported when the system detects that the configuration file does not exist, the file format is illegal,
or the file data is illegal after the NE is started or the configuration file is re-downloaded.
Parameters
Parameter
503 de 526 13/11/2012 9:15

Name
Specific Specific Problem of the alarm(OAM configuration data illegal, Transport configuration data
Problem illegal, Signal configuration data illegal)
Major Some configuration data is illegal, or the NE cannot obtain the configuration data.
The NE has to operate with the default configuration data. In this case, the NE
cannot provide normal services.
System Actions
The NE operates with the default configuration data. If the transmission link is available but the IPoA channel
fails, the NE may start BOOTP.
Possible Causes
The configuration file does not exist.
The configuration file is illegal. For example, the file format is invalid or syntax errors exist in the file.
The flash is faulty.
Procedure
1. Upload the configuration file on the M2000.
a. Run the MML command ULD CFGFILE to upload the data configuration file from the
BBU. Enter the IP address of the FTP server according to the configuration of the FTP
server. Then, specify the destination path, user name, and password. Use the default
values for other parameters. Check whether the upload is successful based on the
command response.
Y => The upload is successful. Go to step 2.
N => The upload fails. The configuration file may be missing or the flash may be faulty.
Go to step 3.
2. Check the configuration file on the M2000.
a. Check whether the configuration file is correct. Ensure that the NE type and hardware
type in the file are consistent with the running data and that the file is in .xml format.
Y => The configuration file is correct. Go to step 3.
N => The configuration file is not correct. Go to sub-step b.
b. Modify the configuration file. Then, go to step 3.
3. Re-download the configuration file on the M2000.
a. Retrieve the correct configuration file or use the modified configuration file.
b. Run the MML command DLD CFGFILE to download the data configuration file to the
server. Then, specify the source path, user name, and password.
c. Run the MML command SET CFGFILEENB (FLAG=ENABLE,

RSTMODE=IMMEDIATELY) to set the enabling flag of the downloaded data
configuration file.
504 de 526 13/11/2012 9:15

If "Reset Mode" is "Immediately reset", the NE will be automatically reset. Otherwise,

the NE needs to be reset manually.
Replace the main control board. Wait until the startup of the main control board is
complete.
b. Run the MML command DLD CFGFILE to download the data configuration file to the
server. Then, specify the destination path, user name, and password.
c. Run the MML command SET CFGFILEENB (FLAG=ENABLE,
RSTMODE=IMMEDIATELY) to set the enabling flag of the downloaded data
configuration file.
If "Reset Mode" is "Immediately reset", the NE will be automatically reset. Otherwise,
the NE needs to be reset manually.
Service Center.
1.1.280 ALM-28381 Board Startup Abnormal Alarm

Description
This alarm is reported when the main control board fails to set parameters on a board during the startup of the
board or the board cannot be started.
Parameters
Parameter
Cause (Key Parameter Configuration Failure, Non-Key Parameter Configuration Failure, Startup
Timeout)
Major When the setting of the key parameters fails, the board becomes unavailable. When
505 de 526 13/11/2012 9:15

the setting of the unimportant parameters fails, the secondary functions of the board
cannot work properly. When the board cannot be started, the board fails to work
properly and the services carried by the board are interrupted.
System Actions
The system automatically disables the board when the setting of the key parameters fails or the board cannot
be started.
Possible Causes
The operation of reading or writing into the configuration fails.
Errors occur during data configuration on the board.
The board is operating improperly.

The startup of the board times out.
Procedure

If "Specific Problem" is "Startup timeout", go to step 2.
If "Specific Problem" is "Key parameter config failure" or "Non-key parameter config
failure", go to step 4.
2. Check for the alarms indicating hardware failures and configuration failures of the board on the
M2000.


3. Reset the board on the M2000.
a. Run the MML command RST BRD to reset the board.

4. Download the configuration file from the M2000.
a. Modify the Data Configuration File.

506 de 526 13/11/2012 9:15


1.1.281 ALM-65033~ALM-65233 External Analog/Boolean Alarm

Description
This alarm is reported when the external analog signal is too strong or too weak or when the external Boolean
indicates the external Boolean device is faulty.
Parameters
Port No. Port number of the user-defined analog/boolean alarm
Specific Problem Specific problem of the alarm (Only for analog alarm)
Major The normal operation of the external analog/boolean equipment is affected.
System Actions
None.
Possible Causes
In the case of the external analog device, the external analog alarm threshold is incorrect.
In the case of the external Boolean device, the external Boolean alarm enabling or signal level
configuration is incorrect.
The cable connection between the external analog equipment and the monitoring device is faulty.
The external analog equipment is faulty.

Procedure
1. Check the configuration on the M2000.
a. Check the external alarm is whether an external analog alarm or an external Boolean
alarm.
If the external analog alarm is defined, go to procedure b
If the external Boolean alarm is defined, go to step d
b. Run the MML command LST ALMPORT to check whether the threshold of the external
analog alarm or the alarm disable configuration and alarm valid level configuration of the
external Boolean alarm is consistent with that in the configuration planning.
507 de 526 13/11/2012 9:15

Y => The configuration is consistent with that in the planning. Go to procedure 2.

N => The configuration is inconsistent with that in the planning. Go to step c.
c. Run the MML command SET ALMPORT to set the threshold of external analog alarm
or the alarm disable configuration and alarm valid level configuration based on the
d. Run the MML command LST ALMPORT to check whether the alarm disable
configuration and alarm valid level configuration of the external Boolean alarm is
consistent with that in the configuration planning.
Y => The configuration is consistent with that in the planning. Go to procedure 2.
N => The configuration is inconsistent with that in the planning. Go to step e.
e. Run the MML command SET ALMPORT to set the alarm disable configuration and
alarm valid level configuration based on the configuration planning.
2. Check the cable connection between the external analog/boolean equipment and the monitoring
device on site.
a. Check whether the cable between the corresponding external analog/boolean

equipment and the monitoring device is slack or broken.
Y => The cable is functional and the connection is correct. Go to procedure 3.
N => The cable is slack or broken. Go to step b.

N => The alarm is not cleared. Go to procedure 3.
3. Check the external analog/boolean equipment on site.
a. Check whether the external analog/boolean equipment is functional.

Y => The external device is functional. Go to procedure 4.
N => The external device malfunctions. Go to step b.
b. Clear the fault of the external analog/boolean equipment.

N => The alarm is not cleared. Go to procedure 4.

508 de 526 13/11/2012 9:15

1.2 NodeB Event Reference

Purpose
This document describes all the events of the BTS3900 WCDMA, BTS3900A WCDMA, BTS3900L WCDMA,
BTS3900C WCDMA, BTS3900AL WCDMA, and DBS3900 WCDMA. The MML commands involved in this
document takes NodeB_2U for example.
Version
The following table lists the product versions involved in this document.
Product Name Version
BTS3900 WCDMA (hereinafter referred to as BTS3900) V200R014C00
BTS3900A WCDMA (hereinafter referred to as BTS3900A) V200R014C00
BTS3900L WCDMA (hereinafter referred to as BTS3900L) V200R014C00
BTS3900C WCDMA (hereinafter referred to as BTS3900C) V200R014C00
BTS3900AL WCDMA (hereinafter referred to as BTS3900AL) V200R014C00
DBS3900 WCDMA (hereinafter referred to as DBS3900) V200R014C00
Intended Audience
This document is intended for:
Field engineers
System engineers
Shift operators
Site maintainers
Network operators
Concepts
Concept Description
Event ID Unique identifier of an event in one product.
Event Name Unique name of an event in one product. Event names clearly and accurately indicate event
meanings. There is a one-to-one mapping between event names and IDs.
Event Type There is only one event type: event.
Event Level Impact of an event on service quality. There are three event severity levels: major, minor,
and warning.
Major event: affects service quality and requires immediate action during working
hours.
Minor event: generally does not affect service quality, but requires handling or
observation in a reasonable amount of time to avoid more serious faults.
Warning event: indicates a potential error that may affect service quality. It
509 de 526 13/11/2012 9:15

Concept Description
requires different actions depending on errors.
Event Type There are 16 event types based on monitored objects.

Power event: relates to the power system.
Environment event: relates to equipment room environment variables, such as
temperature, humidity, and door control.
Signaling event: relates to channel associated signaling (for example, SS1) and
common channel signaling (for example, SS7).
Trunk event: relates to the trunk system, including trunk circuits and boards.
Hardware event: relates to hardware, such as the clock unit and CPU.
Software event: relates to software.
System event: occurs during system operation.
Communication event: relates to communication.
Service quality event: relates to service quality.
Unexpected operation event: occurs when an exception happens.
OMC event: occurs when the OMC is not working properly.
Integrity event: occurs when information is illegally modified or deleted.
Operation event: occurs when service is unavailable or inaccessible because of
inappropriate operations.
Physical resource event: occurs when physical resources are damaged by a
suspected security attack.
Security event: occurs when security service or a security mechanism has
detected that the system encounters security attacks.
Time domain event: occurs at an unexpected or forbidden time.
Description Conditions in which an event occurs.
Parameters Parameters related to events.
Impact on the Impact of an event on the system or services.

System
Possible Issues that may result in an event.

Causes
Procedure Procedure for clearing an event step by step.
Change History
For detailed event changes, see the release notes.
1.2.1 NodeB Event List
Event ID Event Name Event Type Event Level Event Type
EVT-25890 SCTP Link Path Event Minor Trunk

Switchover
EVT-25893 Remote Event Minor Trunk

Maintenance Link
Switchover
510 de 526 13/11/2012 9:15

EVT-26212 Board Startup Event Minor Running
EVT-26213 NE Startup Event Minor Running
EVT-26256 NE Software Event Warning Running

Download Started

Download Ended

Activation Started

Activation Ended
EVT-26505 RF Unit CPRI Event Minor Communication

Interface
Switchover
EVT-26526 RF Unit TX Event Major Hardware

Channel Switched
Off
EVT-26528 RF Unit TX Event Minor Hardware

Channel Switched
On
EVT-26535 RF Unit Startup Event Minor Hardware
EVT-26784 RHUB CPRI Event Minor Communication

Interface
Switchover
EVT-26820 License Event Warning Running

Emergency Status
Activated
EVT-26821 License Event Warning Running

Emergency Status
Ceased
EVT-28200 Iub Common Event Major/Minor Running

Procedure Failure
Indication
EVT-28202 Local Cell Rebuild Event Major QoS
EVT-28222 IMB Local Cell Event Major QoS

Rebuild
EVT-28251 Ethernet Event Minor Running

Configuration
Changed
511 de 526 13/11/2012 9:15

EVT-28252 IP RAN Object Event Major Trunk

Reset
EVT-28352 Enable Event Minor Running

Downloaded
Configuration File
EVT-28353 Disable Event Minor Running

Downloaded
Configuration File
EVT-28380 NE Shutdown Event Major Running
1.2.2 EVT-25890 SCTP Link Path Switchover

Description
The SCTP link consists of the active path and the standby path. This event is reported when the SCTP protocol
stack detects that the current path is unavailable and the SCTP switches to another path.
Parameters
Name Meaning
Switchover SCTP link path switchover direction (Main-to-Standby Switchover, Standby-to-Main Path
Direction Switchover)
Event Severity Event Impact
Minor During the switchover between the primary link and the secondary link of the SCTP,
the signaling communication fails temporarily. In this case, no terminal can access
the network during the switchover.
Possible Causes
The current link that carries the SCTP is faulty, and the SCTP switches to another link.
The automatic switchover is enabled. When the secondary link is used, the automatic switchover is
triggered if the primary link is restored.
Procedure
1. This is an event. No manual operation is required.
1.2.3 EVT-25893 Remote Maintenance Link Switchover

Description
This event is reported when the switchover of the maintenance link between the base station and the M2000
occurs.
512 de 526 13/11/2012 9:15

Parameters
Name Meaning
Switchover OM link switchover direction (Active-to-Standby Switchover, Standby-to-Active

Direction Switchover)
Minor None
Possible Causes
The current link for remote maintenance is faulty, and another link is used for remote maintenance.
Procedure
1.2.4 EVT-26212 Board Startup

Description
This event is reported when a board is reset due to the execution of a command or exception.
Parameters
Name Meaning
Cabinet Cabinet number of the faulty board

No.
Subrack Subrack number of the faulty board

No.
Board Type of the faulty board

Type
Reset Reason of the board reset (Board Power Off, User Command, System Self-Reset, External
Cause Operation Reset, Swap MPT, Exceptional Reset, Communication Abnormal, Unknown Reason)
Minor The ongoing services carried on the board are interrupted.
Possible Causes
The board is reset due to a power failure, for example, removing and then inserting the board or
running a reset command through power-off.
The board is reset due to the execution of a command, for example, running a software activation
command, a board reset command, or a board addition command during an upgrade.
The board is reset due to internal negotiation of the system, for example, changing the environment
variables of the board, or the board is reset due to a transmission subsystem fault.
513 de 526 13/11/2012 9:15

The board is reset due to an external operation.
The board is reset when an active/standby switchover is triggered.
The board is reset due to an exception, for example, memory software failure.
The board is reset due to the disconnection between the board and the upper-level node.
Procedure
1.2.5 EVT-26213 NE Startup

Description
This event is reported when the base station is reset due to the execution of a command, software upgrade, or
exception.
Parameters
Name Meaning
Reset Reason of the NE reset (Board Power-Off, User Command, System Self-Reset, External
Cause Operation, Active/Standby MPT Switchover, Exceptional Reset, Disconnected Link, Unknown)
Minor The ongoing services carried on the base station are interrupted.
Possible Causes
The base station is reset due to a power failure.

The base station is reset due to the execution of a base station reset command or a software
upgrade command .
The base station is reset due to internal negotiation of the system , a UTRPc/UMPT board fault and
signaling extension services unavailable, or a transmission subsystem fault.
The base station is reset due to an external operation.

The base station is reset when an active/standby switchover is triggered.
The base station is reset when it does not work properly.

The base station is reset due to link disconnection.
Procedure
1.2.6 EVT-26256 NE Software Download Started

Description
This event is reported when the NE downloads the software to the main control board from the server.
Parameters
Name Meaning
514 de 526 13/11/2012 9:15

Software Type Software type (Software, Firmware, Patch, Hot patch)
Cause Cause (Software upgrade, Automatic supply, Manual supply)
Warning None
Possible Causes
An operator is manually downloading NE software.

An operator is manually supplementing NE software.
The NE software automatic supplementation function is triggered. This function is triggered when a
new board is installed in the base station but the base station does not have the software for the
board.
Procedure
1.2.7 EVT-26257 NE Software Download Ended

Description
This event is reported when the NE succeeds in downloading or fails to download software to the main control
board from the server.
Parameters
Name Meaning
Result Software download result (Success, Failure)
Warning None
Possible Causes
The download of the NE Software succeeds.
The download of the NE Software fails.
Procedure
1.2.8 EVT-26258 NE Software Activation Started

Description
This event is reported when the NE downloads the software to each board to be activated from the main control
board and updates the software.
515 de 526 13/11/2012 9:15

Parameters
Name Meaning
Warning None
Possible Causes
A user starts to activate the NE software.

The software auto-activation starts.
Procedure
1.2.9 EVT-26259 NE Software Activation Ended

Description
This event is reported when the NE downloads the software to each board to be activated from the main control
board and succeeds in updating or fails to update the software.
Parameters
Name Meaning
Result Software activation result (Success, Failure)
Warning None
Possible Causes
The activation of the NE Software succeeds.
The activation of the NE Software fails.
Procedure
1.2.10 EVT-26505 RF Unit CPRI Interface Switchover

Description
In ring topology, the uplink and downlink of the RF unit cooperate in active/standby mode. If the uplink is faulty,
the RF unit automatically switches to the downlink. This event is reported in this case.
Parameters
516 de 526 13/11/2012 9:15

Name Meaning
Minor In the case of a hot ring, the ongoing services are not affected. In the case of a cold
ring, the ongoing services are disrupted temporarily.
Possible Causes
The uplink of the RF unit is faulty.
Procedure
1.2.11 EVT-26526 RF Unit TX Channel Switched Off

Description
This event is reported when the RF unit automatically switches off the TX channel due to a critical fault on the RF
unit, or when the user sends a command to switch off the TX channel.
Parameters
Name Meaning
Specific Problem Specific Problem of the alarm(Automatically, Fault)
Major The ongoing services carried on the TX channel are disrupted.
Possible Causes
The cell is removed, blocked, or deactivated.
A critical fault occurs on the RF unit, such as PA overcurrent, critical overtemperature, or extremely
high VSWR.
The user sends a command to switch off the TX channel of the RF unit.
517 de 526 13/11/2012 9:15

When the AC mains failure occurs and the batteries are running out, the system automatically
switches off the TX channel of the RF unit to extend the operating time of the BBU and transmission
devices.
Procedure
1.2.12 EVT-26528 RF Unit TX Channel Switched On

Description
This event is reported when the user sends a command to switch on the TX channel of an RF unit, or when a cell
is activated.
Parameters
Name Meaning
Minor None
Possible Causes
A cell is activated.
The user sends a command to switch on the TX channel of an RF unit.

If a critical fault of an RF unit persists for some time, the system automatically switches on the TX
channel of the RF unit to detect the clearance of the critical fault
Procedure
1.2.13 EVT-26535 RF Unit Startup

Description
This event is reported when the RF unit is powered on or reset.
Parameters
Name Meaning
518 de 526 13/11/2012 9:15

Reset Cause of the RF unit reset (Board Power-Off, User Command, Exceptional Reset,
Reason Disconnected Link, Unknown Reason)
Minor The RF unit starts. The services of the RF unit are set up again.
Possible Causes
The user sends the reset command to the RF unit.
The RF unit is powered on or reset.
The RF unit automatically resets after it is disconnected for a long period of time.
The RF unit automatically resets after the RF software activation or new configuration is complete.
The RF unit automatically resets after it exits the sleep mode.
Procedure
1.2.14 EVT-26784 RHUB CPRI Interface Switchover

Description
In ring topology, the CPRI uplink and downlink of the RHUB cooperate in active/standby mode. If the CPRI uplink
is faulty, the RHUB automatically switches to the CPRI downlink. This event is reported in this case.
Parameters
Name Meaning
Uplink Port Before Switchover Uplink port before switchover (Port 0(West), Port 1(East))
Uplink Port After Switchover Uplink port after switchover (Port 0(West), Port 1(East))
Minor In the case of a hot ring, the ongoing services are not affected. In the case of a cold
ring, the ongoing services are disrupted temporarily.
Possible Causes
The CPRI uplink of the RHUB is faulty.
519 de 526 13/11/2012 9:15

Procedure
1.2.15 EVT-26820 License Emergency Status Activated

Description
This event is reported when the emergency status of a license is activated.
Parameters
None.
Warning The dynamic counting items and performance items in the license, such as the
number of channel elements (CEs) in the uplink and number of CEs in the downlink,
are set to their maximum values. Other types of license-controlled items use their
original values.
The system can keep in the emergency state for a maximum of seven days. Later,
the system is rolled back to the license state.
Possible Causes
The emergency status of a license is activated by someone in an emergency such as fire or earthquake.
Procedure
1.2.16 EVT-26821 License Emergency Status Ceased

Description
This event is reported when the emergency status of a license is ceased.
Parameters
None.
Warning The original status of license-controlled items is restored.
Possible Causes
The emergency status of a license remains active for seven days. After the seven-day period
elapses, the emergency status is automatically ceased.
The license is reloaded.
Procedure
520 de 526 13/11/2012 9:15

1.2.17 EVT-28200 Iub Common Procedure Failure Indication

Description
This event is reported when the NBAP common signaling processing over the Iub interface fails.
Parameters
Name Meaning
Cause (Common TRCH Setup Failure, Common TRCH RECFG Failure, Common MEA INIT Failure,
Common MEA Failure, Cell Setup Failure, Cell RECFG Failure, SYS MSG Update Failure, Shared
TRCH RECFG Failure, INFO EXCHANGE INIT Failure, INFO EXCHANGE Failure)
Cell ID Cell ID
Specific Specific Problem of the alarm(System Message Abnormal, Common Transport Channel Carried by
Problem SCCPCH Abnormal, Common Transport Channel Carried by PRACH Abnormal, Other Transport
Channel Abnormal, RTWP Measurement Abnormal, Transmitted Carrier Power Measurement
Abnormal, Acknowledged PRACH Preambles Measurement Abnormal, GPS Timing of Cell Frames
Measurement Abnormal, Transmitted Carrier Power Measurement Abnormal Not Used for HSDPA,
HS-DSCH Required Power Measurement Abnormal, HS-DSCH Provided Bit Rate Measurement
Abnormal, ISCP Measurement Abnormal, APAP Measurement Abnormal, DPAP Measurement
Abnormal, SOTD Measurement Abnormal, Shared Transport Channel Reconfiguration Failure, INFO
EXCHANGE INIT Failure, INFO EXCHANGE Failure, Cell Procedure Abnormal)
Major Services within the cell may fail.
Minor Common measurement may fail.
Possible Causes
Resources in the cell are insufficient or faulty. For example, the hardware of the board carrying the
traffic is faulty.
The software processing of the RNC or NE is improper.
The processing of the RNC is incorrect. As a result, the contents of the message that is sent to the
NE are incorrect.
Procedure
1. Check the local cell status of the NE on the M2000.
a. Run the MML command DSP LOCELL to check whether the local cell status of the
failed signaling is normal.
Y => “Local Cell Status” is “Local Cell Available”. The local cell is normal. Go to step 2.
N => “Local Cell Status” is “Local Cell Unavailable”. The local cell is faulty. The cause
may be that the hardware resources of the NE are faulty. Go to sub-step b.
b. Run the MML command LST ALMAF to check whether certain alarms of the NE are not
cleared.
Y => Certain alarms are not cleared. Go to sub-step c.
N => All alarms are cleared. Go to sub-step d.
521 de 526 13/11/2012 9:15

d. Run the MML command RMV LOCELL to delete the local cell that is faulty.
e. Run the MML command ADD LOCELL to add the deleted cell again.
f. Wait for 1 minute, and then run the MML command DSP LOCELL to check whether the
local cell status of the failed signaling is normal.
Y => “Local Cell Status” is “Local Cell Available”. The local cell is normal. Go to step 2.
N => “Local Cell Status” is “Local Cell Unavailable”. The local cell is faulty. Contact
2. Check the logical cell status of the NE on the M2000.
a. Run the MML command DSP CELLCFG to check whether the logical cell status of the
failed signaling is normal.
Y => The logical cell is normal. Go to step 3.
N => The logical cell is faulty. The cause may be that the transmission resources of the
NE are faulty. Go to sub-step b.
b. Run the MML command LST ALMAF to check whether active alarms exist on the NE.
Y => There is one or more active alarms on the NE. Go to sub-step c.
N => There is no active alarm on the NE. Go to sub-step d.
d. Delete the faulty logical cell from the RNC.

e. Add and activate the logical cell on the RNC.
f. Wait for one minute, and then run the MML command DSP CELLCFG to check whether
the logical cell status is normal.
Y => The logical cell is normal. Go to step 3.
N => The logical cell is faulty. Contact Huawei Customer Service Center.
3. Check for this alarm again on the M2000.
a. Check whether this alarm is reported again. If this alarm is reported, Contact Huawei
1.2.18 EVT-28202 Local Cell Rebuild

Description
This event is reported when the system attempts to reestablish the local cell for recovery from the fault upon
service interruption caused by a local cell failure, or when the local cell is reestablished for resource optimization.
Parameters
Name Meaning
Major In the case that the event is reported because the local cell is faulty, only the faulty
522 de 526 13/11/2012 9:15

local cell and faulty logical cell are reestablished.

In the case that the event is reported because the resources of the local cell are not
optimum, all the available local cells and logical cells are reestablished.
Possible Causes
The local cell fails to provide services and the system attempts to the local cell reestablish the local
cell for recovery from the fault. This happens when: a) The SET NOACCESSALMPARA command is
executed and the AUTORCVRMTHD parameter is set to CELLRESTART. b) The cell has no output
power.
If the resources of the local cell are not optimum, the system attempts to optimize the resources.
This happens when: a) The STR REALLOCLOCELL command is executed to optimize baseband
resources.
Procedure
1.2.19 EVT-28222 IMB Local Cell Rebuild

Description
This event is reported when the system attempts to reestablish the IMB( Integrated Mobile Broadcast) local cell
for recovery from the fault upon service interruption caused by a IMB local cell failure, or when the IMB local cell
is reestablished for resource optimization.
Parameters
Name Meaning
Major In the case that the event is reported because the IMB local cell is faulty, only the
faulty IMB local cell and faulty logical cell are reestablished.
In the case that the event is reported because the resources of the IMB local cell are
not optimum, all the available local cells and logical cells are reestablished.
Possible Causes
The IMB local cell is faulty and fails to provide services. Thus, the system attempts to recover from
the fault by reestablishing the IMB local cell.
If the resources of the IMB local cell are not optimum, the system attempts to optimize the resources
of the IMB local cell.
Procedure
1.2.20 EVT-28251 Ethernet Configuration Changed

Description
523 de 526 13/11/2012 9:15

This event is reported when the auto negotiation is enabled for the local Ethernet electrical port but disabled for
the peer Ethernet electrical port.
Parameters
Name Meaning
Port No. Port No.
Minor If the Ethernet electrical port carries heavy traffic, Ethernet frames may be lost,
causing the services to be interrupted for a short time.
Possible Causes
The auto negotiation is enabled for the local Ethernet electrical port but disabled for the peer port (full-duplex or
half-duplex).
Procedure
1. Perform the corresponding operation on the M2000 to allow the system to renegotiate the working
mode of the Ethernet ports.
a. Set the working mode of the Ethernet port on the peer device connected to the NE to
auto negotiation, and then run the MML command RST ETHPORT to reset the Ethernet
electrical port for which the event is triggered.
1.2.21 EVT-28252 IP RAN Object Reset

Description
This event is reported when the MML command is executed to reset the ETH port, MLPPP group, PPP link, and
ETHTRUNK.
Parameters
Name Meaning
Object Type (Ethernet Port, MLPPP Group, PPP Link, Ethernet Trunk Group)
Object No. Object No.
524 de 526 13/11/2012 9:15

Major The signaling and services carried on the ETH port, MLPPP group, PPP link,
ETHTRUNK are interrupted for a short time.
Possible Causes
The MML command is executed to reset the objects of the IP transmission network (ETH port, MLPPP group,
PPP link, and ETHTRUNK).
Procedure
1.2.22 EVT-28352 Enable Downloaded Configuration File

Description
This event is reported when the operation of running the command SET CFGFILEENB with Enable Flag set to
Enable is successful.
Parameters
None.
Minor After the system is restarted, the downloaded configuration file takes effect and
overwrites the original configuration file.
Possible Causes
The command SET CFGFILEENB is executed with Enable Flag set to Enable.
Procedure
1.2.23 EVT-28353 Disable Downloaded Configuration File

Description
This event is reported when the operation of running the command SET CFGFILEENB with Enable Flag set to
Disable is successful.
This event is also reported in the scenario where the system automatically disables the flag that has been
enabled after the user redownloads the configuration file, activates the configuration baseline (CB), or rolls back
the CB.
Parameters
None.
Minor The flag of the downloaded configuration file is disabled.
525 de 526 13/11/2012 9:15

Possible Causes
The command SET CFGFILEENB is executed with Enable Flag set to Disable.
The flag is enabled, but the user redownloads the configuration file.
The flag is enabled, but the user activates the CB.
The flag is enabled, but the user rolls back the CB.
Procedure
1.2.24 EVT-28380 NE Shutdown

Description
This event is reported when the user runs the command to reset the NE or the active WMPT/UMPT.
Parameters
None.
Major The services carried by the NE are completely interrupted.
Possible Causes
The user runs the command to reset the NE or the active WMPT/UMPT.
Procedure
526 de 526 13/11/2012 9:15

List Alarm PDF

Uploaded by

Document Information

Original Description:

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

List Alarm PDF

Uploaded by

Copyright:

Available Formats

Fault Management http://localhost:7890/printtopics.html?time=Tue Nov 13 2012 09:15:0...

1 de 526 13/11/2012 9:15

1.1.47 ALM-25807 E1/T1 Loopback

2 de 526 13/11/2012 9:15

1.1.102 ALM-25929 SDH/SONET RS Excessive Bit Error Rate

3 de 526 13/11/2012 9:15

1.1.157 ALM-26253 Board Software Auto-Supply Failure

4 de 526 13/11/2012 9:15

1.1.212 ALM-26753 RET Antenna Not Calibrated

5 de 526 13/11/2012 9:15

1.1.267 ALM-28249 GPS Receiver Maintenance Link Failure

Related Document Description

NodeB Alarm Reference This document describes NodeB alarm reference.

NodeB Event Reference This document describes NodeB event reference.

1.1 NodeB Alarm Reference

6 de 526 13/11/2012 9:15

Product Name Version

BTS3900 WCDMA (hereinafter referred to as BTS3900) V200R014C00

BTS3900A WCDMA (hereinafter referred to as BTS3900A) V200R014C00

BTS3900L WCDMA (hereinafter referred to as BTS3900L) V200R014C00

BTS3900C WCDMA (hereinafter referred to as BTS3900C) V200R014C00

BTS3900AL WCDMA (hereinafter referred to as BTS3900AL) V200R014C00

DBS3900 WCDMA (hereinafter referred to as DBS3900) V200R014C00

This document is intended for:

Alarm ID Unique identifier of an alarm in one product.

Alarm Type There is only one alarm type: fault.

Event Type There are 16 event types based on monitored objects.

7 de 526 13/11/2012 9:15

Environment alarm: relates to equipment room environment variables, such as

Description Conditions in which an alarm is generated.

Parameters Parameters related to alarms.

Impact on the Impact of an alarm on the system or services.

System Actions Actions taken by the system when an alarm is generated.

Procedure Procedure for clearing an alarm step by step.

For detailed alarm changes, see the release notes.

1.1.1 NodeB Alarm List

Alarm ID Alarm Name Alarm Type Alarm Level Event Type

ALM-25600 Monitoring Device Fault Major Communication

ALM-25601 Monitoring Device Fault Major Hardware

ALM-25602 Sensor Failure Fault Major Hardware

8 de 526 13/11/2012 9:15

Alarm ID Alarm Name Alarm Type Alarm Level Event Type

ALM-25620 Monitoring Device Fault Major Hardware

ALM-25621 Power Supply DC Fault Major Power

ALM-25622 Mains Input Out of Fault Major Power

ALM-25623 Load Disconnected Fault Major/Warning Power

ALM-25624 Battery Power Fault Major/Warning Power

ALM-25625 Battery Current Fault Major Power

ALM-25626 Power Module Fault Major/Warning Power

ALM-25628 AC Surge Fault Major Power

ALM-25630 Power Module and Fault Major Power

ALM-25631 Load Fuse Broken Fault Major Power

ALM-25632 Battery Cabin Fault Major Power

ALM-25633 PMU Internal Fault Major Power

ALM-25634 Battery Not In Fault Major Power

ALM-25636 Loss of Power Fault Warning Power

ALM-25650 Ambient Fault Major/Minor Environment

ALM-25651 Ambient Humidity Fault Minor Environment

9 de 526 13/11/2012 9:15

Alarm ID Alarm Name Alarm Type Alarm Level Event Type

ALM-25652 Cabinet Fault Major/Minor Environment

ALM-25653 Cabinet Humidity Fault Minor Environment