Fault Management Contents BBU Huawei-1-263

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.
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.
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.

N => The correlated alarm does not exist. Contact Huawei Customer Service Center.
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
SCTP Link No. SCTP link number
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.
Y=> The alarm is cleared. No further action is required.
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
25880 Ethernet Link Fault
25885 IP Address Conflict
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
26842 Automatic Certificate Update Failed

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
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.
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
Y => A correlated alarm is reported. Go to sub-step b.
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:
26201 Board Memory Soft Failure
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.

N => The alarm is not cleared. Go to sub-step d.
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

Fault Management Contents BBU Huawei-1-263

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

Fault Management Contents BBU Huawei-1-263

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