Professional Documents
Culture Documents
Huawei NodeB Fault Management
Huawei NodeB Fault Management
1 de 526
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
13/11/2012 9:15
Fault Management
2 de 526
13/11/2012 9:15
Fault Management
3 de 526
13/11/2012 9:15
Fault Management
4 de 526
13/11/2012 9:15
Fault Management
5 de 526
13/11/2012 9:15
Fault Management
6 de 526
1 Fault Management
Related Document
Description
13/11/2012 9:15
Fault Management
7 de 526
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
V200R014C00
V200R014C00
V200R014C00
V200R014C00
V200R014C00
V200R014C00
Intended Audience
This document is intended for:
Field engineers
System engineers
Shift operators
Site maintainers
Network operators
Concepts
Concept
Description
Alarm ID
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
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
13/11/2012 9:15
Fault Management
8 de 526
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
Parameters
Impact on the
System
System Actions
Possible
Causes
Issues that may result in an alarm. Possible causes are categorized into data configuration,
hardware, software, and other causes.
Procedure
Change History
For detailed alarm changes, see the release notes.
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-25600
Monitoring Device
Maintenance Link
Failure
Fault
Major
Communication
ALM-25601
Monitoring Device
Hardware Fault
Fault
Major
Hardware
ALM-25602
Sensor Failure
Fault
Major
Hardware
13/11/2012 9:15
Fault Management
9 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-25620
Monitoring Device
Power Supply
Problem
Fault
Major
Hardware
ALM-25621
Power Supply DC
Output Out of
Range
Fault
Major
Power
ALM-25622
Fault
Major
Power
ALM-25623
Major/Warning
Power
ALM-25624
Battery Power
Unavailable
Fault
Major/Warning
Power
ALM-25625
Battery Current
Out of Range
Fault
Major
Power
ALM-25626
Power Module
Abnormal
Fault
Major/Warning
Power
ALM-25628
AC Surge
Protector Fault
Fault
Major
Power
ALM-25630
Major
Power
ALM-25631
Fault
Major
Power
ALM-25632
Battery Cabin
Heater Fault
Fault
Major
Power
ALM-25633
PMU Internal
Interface
Communication
Failure
Fault
Major
Power
ALM-25634
Battery Not In
Position
Fault
Major
Power
ALM-25636
Loss of Power
Supply
Redundancy
Fault
Warning
Power
ALM-25650
Ambient
Temperature
Unacceptable
Fault
Major/Minor
Environment
ALM-25651
Ambient Humidity
Unacceptable
Fault
Minor
Environment
13/11/2012 9:15
Fault Management
10 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-25652
Cabinet
Temperature
Unacceptable
Fault
Major/Minor
Environment
ALM-25653
Cabinet Humidity
Unacceptable
Fault
Minor
Environment
ALM-25654
Battery
Temperature
Unacceptable
Fault
Major/Minor
Power
ALM-25655
Fault
Major/Minor
Environment
ALM-25656
Fault
Major/Minor
Environment
ALM-25657
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
Fault
Major
Hardware
ALM-25696
Diesel Generator
Low Fuel
Fault
Major
Hardware
ALM-25697
Diesel Generator
Startup Failure
Fault
Major
Hardware
ALM-25710
Loss of Solar
Array
Fault
Major
Hardware
ALM-25711
Fault
Major
Hardware
ALM-25713
Solar Controller
Temperature
Unacceptable
Fault
Minor
Hardware
ALM-25719
Major
Environment
ALM-25720
Inter-CCU Port
Connection Error
Fault
Major
Environment
ALM-25721
CCU-BBU
Communication
Fault
Minor
Environment
13/11/2012 9:15
Fault Management
11 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
Failure
ALM-25800
E1/T1 Loss of
Signal
Fault
Major
Trunk
ALM-25801
E1/T1 Alarm
Indication Signal
Fault
Major
Trunk
ALM-25802
E1/T1 Remote
Alarm Indication
Signal
Fault
Minor
Trunk
ALM-25803
E1/T1 Loss of
Frame Alignment
Fault
Major
Trunk
ALM-25804
E1/T1 Loss of
Multiframe
Alignment
Fault
Minor
Trunk
ALM-25805
E1/T1 Excessive
Slip Frames
Fault
Minor
Trunk
ALM-25806
E1/T1 Excessive
Bit Error Rate
Fault
Minor
Trunk
ALM-25807
E1/T1 Loopback
Fault
Minor
Trunk
ALM-25820
Fractional ATM
Link Loss of Cell
Delineation
Fault
Major
Trunk
ALM-25821
IMA/ATM Link
Loss of Cell
Delineation
Fault
Major
Trunk
ALM-25823
Fault
Major
Trunk
ALM-25824
Fault
Major
Trunk
ALM-25825
Fault
Minor
Trunk
ALM-25826
Fault
Major
Trunk
ALM-25827
IMA Link TX
Unusable at Far
End
Fault
Minor
Trunk
ALM-25828
IMA Link RX
Unusable at Far
End
Fault
Minor
Trunk
13/11/2012 9:15
Fault Management
12 de 526
Alarm ID
Alarm Name
ALM-25829
Alarm Type
Alarm Level
Event Type
Minor
Trunk
ALM-25830
IMA Group
Configuration
Aborted
Fault
Major
Trunk
ALM-25831
IMA Group
Fault
Configuration
Aborted at Far End
Minor
Trunk
ALM-25832
IMA Group
Activated Links
Insufficient
Fault
Major
Trunk
ALM-25833
IMA Group
Activated Links
Insufficient at Far
End
Fault
Minor
Trunk
ALM-25834
IMA Group
Fault
Blocked at Far End
Minor
Trunk
ALM-25835
NCP Fault
Fault
Major
Communication
ALM-25836
CCP Fault
Fault
Major
Communication
ALM-25837
ALCAP Fault
Fault
Major
Signaling
ALM-25838
Fault
Major
Trunk
ALM-25840
Fault
Major
Trunk
ALM-25841
SAAL Link
Congestion
Fault
Major
Trunk
ALM-25860
PPP/MLPPP Link
Fault
Fault
Major
Trunk
ALM-25861
MLPPP Group
Fault
Fault
Major
Trunk
ALM-25862
MLPPP Group
Excessive Packet
Loss Rate
Fault
Minor
Trunk
ALM-25863
PPP Link
Excessive Frame
Error Rate
Fault
Minor
Trunk
ALM-25879
Ethernet Port
Fault
Broadcast Packets
Exceeding Alarm
Major
Trunk
ALM-25880
Major
Trunk
13/11/2012 9:15
Fault Management
13 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-25881
MAC Excessive
Frame Error Rate
Fault
Minor
Trunk
ALM-25882
ETHOAM 3AH
Discovery Failure
Fault
Minor
Trunk
ALM-25883
ETHOAM 3AH
Local Fault
Fault
Minor
Trunk
ALM-25884
ETHOAM 3AH
Remote Fault
Fault
Minor
Trunk
ALM-25885
Minor
Trunk
ALM-25886
IP Path Fault
Fault
Major
Trunk
ALM-25887
Ethernet Trunk
Link Fault
Fault
Minor
Trunk
ALM-25888
Fault
Major
Trunk
ALM-25889
SCTP Link
Congestion
Fault
Minor
Trunk
ALM-25891
IKE Negotiation
Failure
Fault
Major
Trunk
ALM-25894
ETHOAM 3AH
Remote Loopback
Fault
Major
Trunk
ALM-25895
Ethernet Trunk
Group Fault
Fault
Major
Trunk
ALM-25896
IP Remote
Loopback
Fault
Major
Trunk
ALM-25897
IP Excessive
Frame Error Rate
Fault
Minor
Trunk
ALM-25898
IP Path Excessive
Packet Loss Rate
Fault
Minor
Trunk
ALM-25899
Fault
Minor
Trunk
ALM-25900
IP PM Activation
Failure
Fault
Minor
Trunk
ALM-25901
Remote
Maintenance Link
Failure
Fault
Major
Trunk
ALM-25902
Remote
Maintenance Link
Running Data and
Configuration
Mismatch
Fault
Minor
Trunk
13/11/2012 9:15
Fault Management
14 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-25920
SDH/SONET Loss
of Frame
Alignment
Fault
Major
Trunk
ALM-25921
SDH/SONET Loss
of Frame
Fault
Major
Trunk
ALM-25922
SDH/SONET Loss
of Signal
Fault
Major
Trunk
ALM-25923
SDH/SONET AU
Loss of Pointer
Fault
Major
Trunk
ALM-25924
SDH/SONET MS
Alarm Indication
Signal
Fault
Major
Trunk
ALM-25925
SDH/SONET MS
Remote Defect
Indication
Fault
Major
Trunk
ALM-25926
SDH/SONET Loss
of Cell Delineation
Fault
Major
Trunk
ALM-25927
SDH/SONET
Optical Port
Loopback
Fault
Warning
Trunk
ALM-25928
SDH/SONET RS
Trace Identifier
Mismatch
Fault
Minor
Trunk
ALM-25929
SDH/SONET RS
Fault
Excessive Bit Error
Rate
Minor
Trunk
ALM-25930
SDH/SONET MS
Fault
Excessive Bit Error
Rate
Minor
Trunk
ALM-25931
SDH/SONET MS
Signal Degraded
Fault
Major
Trunk
ALM-25932
SDH/SONET MS
Remote Error
Indication
Fault
Major
Trunk
ALM-25933
SDH/SONET AU
Alarm Indication
Signal
Fault
Major
Trunk
ALM-25934
SDH/SONET HP
Fault
Unequipped Defect
Major
Trunk
13/11/2012 9:15
Fault Management
15 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-25935
SDH/SONET HP
Signal Label
Mismatch
Fault
Minor
Trunk
ALM-25936
SDH/SONET HP
Trace Identifier
Mismatch
Fault
Minor
Trunk
ALM-25937
SDH/SONET HP
Remote Defect
Indication
Fault
Major
Trunk
ALM-25938
SDH/SONET HP
Remote Error
Indication
Fault
Major
Trunk
ALM-25949
Excessive Flood
Packet
Fault
Major
Trunk
ALM-25950
Major
Security
ALM-26101
Inter-Board
CANBUS
Communication
Failure
Fault
Minor
Hardware
ALM-26104
Board
Temperature
Unacceptable
Fault
Major/Minor
Environment
ALM-26106
Fault
Major
Hardware
ALM-26107
Board Input
Voltage Out of
Range
Fault
Major
Hardware
ALM-26110
Fault
Major
Hardware
ALM-26111
Fault
Major
Hardware
ALM-26112
BBU DC Output
Out of Range
Fault
Major
Power
ALM-26113
Base Station DC
Power Supply
Abnormal
Fault
Major
Power
ALM-26120
Fault
Minor
Hardware
ALM-26121
Minor
Hardware
13/11/2012 9:15
Fault Management
16 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26122
GPS Locked
Satellites
Insufficient
Fault
Minor
Running
ALM-26123
GPS Maintenance
Link Failure
Fault
Minor
Running
ALM-26200
Board Hardware
Fault
Fault
Major/Minor
Hardware
ALM-26201
Board Memory
Soft Failure
Fault
Minor
Hardware
ALM-26202
Board Overload
Fault
Minor
Running
ALM-26203
Board Software
Program Error
Fault
Major
Running
ALM-26204
Board Not In
Position
Fault
Major
Hardware
ALM-26205
BBU Board
Maintenance Link
Failure
Fault
Major
Hardware
ALM-26206
Main Control
Board in Wrong
Slot
Fault
Major
Hardware
ALM-26208
Fault
Major
Hardware
ALM-26210
Board Blocked
Fault
Major
Running
ALM-26214
Board Powered
Off
Fault
Major
Hardware
ALM-26215
Inter-Board
Service Link
Failure
Fault
Major
Hardware
ALM-26216
Board Not
Securely Installed
Fault
Major
Hardware
ALM-26220
Transmission
Optical Module
Fault
Fault
Warning
Hardware
ALM-26221
Transmission
Fault
Optical Module Not
In Position
Major
Hardware
ALM-26222
Transmission
Optical Interface
Error
Major/Minor
Hardware
Fault
13/11/2012 9:15
Fault Management
17 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26223
Transmission
Optical Interface
Performance
Degraded
Fault
Major/Minor
Communication
ALM-26230
Fault
Warning
Hardware
ALM-26231
Fault
Major
Hardware
ALM-26232
BBU Optical
Module
Transmit/Receive
Fault
Fault
Major/Minor
Hardware
ALM-26233
Fault
Major/Minor
Hardware
ALM-26234
BBU CPRI
Interface Error
Fault
Major
Hardware
ALM-26235
RF Unit
Maintenance Link
Failure
Fault
Major
Hardware
ALM-26236
RRU Cascading
Levels and
Configuration
Mismatch
Fault
Major
Hardware
ALM-26237
RRU Network
Breakpoint
Fault
Major
Hardware
ALM-26238
RRU Network
Fault
Topology Type and
Configuration
Mismatch
Major
Hardware
ALM-26240
Major
Hardware
ALM-26241
Configuration File
Update Failure
Fault
Major
Running
ALM-26242
Configuration File
Damaged
Fault
Major
Running
ALM-26245
Major
Running
13/11/2012 9:15
Fault Management
18 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26250
Active Workspace
Version
Unavailable
Fault
Major
Running
ALM-26251
Fault
Major
Running
ALM-26253
Board Software
Auto-Supply
Failure
Fault
Major
Running
ALM-26254
Board Software
Synchronization
Failure
Fault
Major
Running
ALM-26255
Automatic Version
Rollback
Fault
Major
Running
ALM-26260
System Clock
Failure
Fault
Major
Hardware
ALM-26261
External Clock
Reference Not
Configured
Fault
Minor
Hardware
ALM-26262
External Clock
Reference
Problem
Fault
Minor
Hardware
ALM-26263
IP Clock Link
Failure
Fault
Minor
Hardware
ALM-26264
System Clock
Unlocked
Fault
Major/Minor
Hardware
ALM-26265
Base Station
Frame Number
Synchronization
Error
Fault
Major
Hardware
ALM-26266
Time
Synchronization
Failure
Fault
Minor
Communication
ALM-26270
Inter-System
Communication
Failure
Fault
Major
Hardware
ALM-26271
Inter-System
Monitoring Device
Parameter
Settings Conflict
Fault
Warning
Running
13/11/2012 9:15
Fault Management
19 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26272
Inter-System RF
Unit Parameter
Settings Conflict
Fault
Major/Warning
Running
ALM-26273
Inter-System BBU
Board Parameter
Settings Conflict
Fault
Major/Warning
Running
ALM-26274
Inter-System
Board Object
Configuration
Conflict
Fault
Major
Running
ALM-26275
Inter-System
Cabinet
Configuration
Conflict
Fault
Minor
Running
ALM-26276
Inter-System
Site-Level
Configuration
Conflict
Fault
Major
Running
ALM-26277
Inter-System
Control Rights
Conflict
Fault
Major
Running
ALM-26278
RF Unit Working
Mode and Mode
Capability
Inconsistency
Fault
Major
Hardware
ALM-26279
Inter-System
Board Installation
and Configuration
Mismatch
Fault
Minor
Software
ALM-26310
Inter-BBU Optical
Module Fault
Fault
Warning
Hardware
ALM-26311
Inter-BBU Optical
Module Not in
Position
Fault
Major
Hardware
ALM-26312
Inter-BBU Optical
Module Receive
Failure
Fault
Major/Minor
Hardware
ALM-26313
Inter-BBU Optical
Module Transmit
Failure
Fault
Major/Minor
Hardware
ALM-26314
Inter-BBU Port
Failure
Fault
Major
Hardware
13/11/2012 9:15
Fault Management
20 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26315
Inter-BBU Port
Connection Error
Fault
Major
Hardware
ALM-26501
RF Unit Optical
Module or
Electrical Port Not
Ready
Fault
Major
Communication
ALM-26502
RF Unit Optical
Module Type
Mismatch
Fault
Major
Communication
ALM-26503
RF Unit Optical
Module
Transmit/Receive
Fault
Fault
Major
Communication
ALM-26504
RF Unit CPRI
Interface Error
Fault
Major
Communication
ALM-26506
RF Unit Optical
Interface
Performance
Degraded
Fault
Major
Communication
ALM-26507
RF Unit Optical
Module Fault
Fault
Warning
Communication
ALM-26520
RF Unit TX
Channel Gain Out
of Range
Fault
Minor
Hardware
ALM-26521
RF Unit RX
Channel
RTWP/RSSI Too
Low
Fault
Minor
Hardware
ALM-26522
RF Unit RX
Channel
RTWP/RSSI
Unbalanced
Fault
Minor
Hardware
ALM-26524
RF Unit PA
Overcurrent
Fault
Major
Hardware
ALM-26525
RF Unit
Temperature
Unacceptable
Fault
Major/Minor
Hardware
ALM-26527
RF Unit Input
Power Out of
Range
Fault
Major
Hardware
ALM-26529
RF Unit VSWR
Fault
Threshold Crossed
Major/Minor
Hardware
13/11/2012 9:15
Fault Management
21 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26530
RF Unit ALD
Current Out of
Range
Fault
Minor/Warning
Hardware
ALM-26531
RF Unit ALD
Switch
Configuration
Mismatch
Fault
Minor
Hardware
ALM-26532
RF Unit Hardware
Fault
Fault
Major/Minor
Hardware
ALM-26533
RF Unit Software
Program Error
Fault
Major
Running
ALM-26534
RF Unit Overload
Fault
Minor
Running
ALM-26536
Minor
Running
ALM-26538
RF Unit Clock
Problem
Fault
Major
Hardware
ALM-26540
RF Unit AC Input
Power Failure
Fault
Major
Power
ALM-26541
ALD Maintenance
Link Failure
Fault
Major
Communication
ALM-26542
RF Unit Backup
Power Device
Maintenance Link
Failure
Fault
Major
Communication
ALM-26543
RF Unit External
Device
Maintenance Link
Failure
Fault
Major
Communication
ALM-26544
RF Unit Power
Surge Protector
Fault
Fault
Major
Hardware
ALM-26545
RF Unit TX
Channel Switched
Off Through
Command
Fault
Warning
Running
ALM-26546
RF Unit External
Power Supply
Insufficient
Fault
Major/Minor
Hardware
ALM-26751
RET Antenna
Motor Fault
Fault
Minor
Hardware
13/11/2012 9:15
Fault Management
22 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26752
ALD Hardware
Fault
Fault
Major/Minor
Hardware
ALM-26753
Fault
Minor
Hardware
ALM-26754
Minor
Hardware
ALM-26755
TMA Bypass
Fault
Major
Hardware
ALM-26756
SASU VSWR
Fault
Threshold Crossed
Major
Hardware
ALM-26757
RET Antenna
Running Data and
Configuration
Mismatch
Fault
Minor
Hardware
ALM-26758
Minor
Hardware
ALM-26759
SASU Running
Data and
Configuration
Mismatch
Fault
Minor
Hardware
ALM-26760
SASU Bypass
Fault
Major
Hardware
ALM-26765
RHUB Hardware
Fault
Fault
Major/Minor
Hardware
ALM-26766
RHUB Software
Program Error
Fault
Major
Running
ALM-26767
RHUB Overload
Fault
Minor
Running
ALM-26768
RHUB Clock
Problem
Fault
Major
Hardware
ALM-26770
UPS Surge
Protection Device
Fault
Fault
Major
Hardware
ALM-26771
Mains Breakdown
with UPS
Fault
Major
Hardware
ALM-26772
UPS Battery
Undervoltage
Fault
Major
Hardware
ALM-26773
UPS Failure
Fault
Major
Hardware
ALM-26774
RHUB AC/DC
Maintenance Link
Failure
Fault
Major
Hardware
13/11/2012 9:15
Fault Management
23 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26775
RHUB AC/DC
Module Problem
Fault
Major
Hardware
ALM-26776
Fault
Major
Hardware
ALM-26777
Fault
Major
Hardware
ALM-26780
RHUB Optical
Module or
Electrical Port Not
Ready
Fault
Major
Communication
ALM-26781
RHUB Optical
Module Type
Mismatch
Fault
Major
Communication
ALM-26782
RHUB Optical
Module
Transmit/Receive
Fault
Fault
Major
Communication
ALM-26783
RHUB CPRI
Interface Error
Fault
Major
Communication
ALM-26785
RHUB Optical
Interface
Performance
Degraded
Fault
Major/Minor
Communication
ALM-26786
RHUB Optical
Module Fault
Fault
Minor
Communication
ALM-26787
Major
Communication
ALM-26810
Major
Running
ALM-26811
Configured
Capacity Limit
Exceeding
Licensed Limit
Fault
Major
Running
ALM-26812
System Dynamic
Traffic Exceeding
Licensed Limit
Fault
Major
Running
ALM-26830
Local User
Consecutive Login
Retries Failed
Fault
Minor
Security
ALM-26832
Peer Certificate
Expiry
Fault
Minor
Security
13/11/2012 9:15
Fault Management
24 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-26840
Imminent
Certificate Expiry
Fault
Minor
Security
ALM-26841
Certificate Invalid
Fault
Major
Security
ALM-26842
Automatic
Certificate Update
Failed
Fault
Minor
Security
ALM-28201
Fault
Minor
QoS
ALM-28203
Local Cell
Unusable
Fault
Major
QoS
ALM-28204
Cell DL Load
Simulation Startup
Fault
Minor
QoS
ALM-28205
Fault
Minor
QoS
ALM-28206
Local Cell
Capability Decline
Fault
Major
QoS
ALM-28207
Carrier Wave
Share Failure
Fault
Minor
QoS
ALM-28209
Cell No Traffic
Fault
Minor
QoS
ALM-28210
Frequency
Separation
Configuration
Mismatch
Fault
Minor
QoS
ALM-28211
Cell Configuration
Abnormal
Fault
Major
QoS
ALM-28221
Fault
Minor
QoS
ALM-28223
Fault
Major
QoS
ALM-28224
Fault
Minor
QoS
ALM-28225
Fault
Major
QoS
ALM-28226
IMB Cell
Configuration
Abnormal
Fault
Major
QoS
ALM-28230
Base Station
Service Overload
Fault
Minor
QoS
13/11/2012 9:15
Fault Management
25 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-28244
GPS Receiver
Hardware Fault
Fault
Minor
Hardware
ALM-28245
GPS Receiver
Antenna Power
Problem
Fault
Minor
Hardware
ALM-28246
GPS Receiver
Antenna Fault
Fault
Minor
Hardware
ALM-28247
GPS Receiver
Software Program
Error
Fault
Minor
Hardware
ALM-28248
GPS Receiver
Position Not
Locked
Fault
Minor
Hardware
ALM-28249
GPS Receiver
Maintenance Link
Failure
Fault
Minor
Communication
ALM-28250
GPS Receiver
Initialization
Configuration
Failure
Fault
Minor
Hardware
ALM-28253
Ethernet Link
Abnormal
Fault
Major
Trunk
ALM-28255
Transport
Configuration
Failure
Fault
Major
Running
ALM-28300
Board Uplink
Fault
Service Processing
Channel Abnormal
Major
Hardware
ALM-28301
Board Downlink
Fault
Service Processing
Channel Abnormal
Major/Minor
Hardware
ALM-28302
Board BFN
Abnormal
Fault
Major
Hardware
ALM-28303
WBBP-WBBP
Fault
Interface Abnormal
Major
Hardware
ALM-28329
RF Unit Input
Power Abnormal
Fault
Major
Hardware
ALM-28330
RF Unit Over
Backward Power
Alarm
Fault
Major
Hardware
13/11/2012 9:15
Fault Management
26 de 526
Alarm ID
Alarm Name
Alarm Type
Alarm Level
Event Type
ALM-28350
Board
Configuration
Inconsistent with
Resource Group
Configuration
Fault
Major
Running
ALM-28354
Transport Backup
Not Support
Fault
Major
Running
ALM-28355
Major
Running
ALM-28381
Board Startup
Abnormal Alarm
Fault
Major
Running
ALM-65033ALM-65233
External
Analog/Boolean
Alarm
Fault
Major
Environment
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Communication Address
Alarm Impact
Major
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.
13/11/2012 9:15
Fault Management
27 de 526
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.
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 3.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
28 de 526
13/11/2012 9:15
Fault Management
29 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
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.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
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.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
30 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
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)
Board Type
Alarm Impact
Major
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.
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.
13/11/2012 9:15
Fault Management
31 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
Major
System Actions
13/11/2012 9:15
Fault Management
32 de 526
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.
The corresponding monitoring device is faulty.
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
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 with recommended actions.
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 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.
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 3.
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.
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 4.
4. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
33 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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.
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:
25622 Mains Input Out of Range
25626 Power Module Abnormal
25711 Solar Array Fault
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.
13/11/2012 9:15
Fault Management
34 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
35 de 526
Board Type
Specific Problem Specific Problem of the alarm(AC Failure, AC Phase Loss, AC Overvoltage, AC
Undervoltage)
Alarm Impact
Major
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.
The monitoring device 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.
b. Run the MML command MOD PMU to set the alarm threshold based on the
configuration planning.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
36 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
37 de 526
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
Major
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.
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:
25622 Mains Input Out of Range
25626 Power Module Abnormal
25621 Power Supply DC Output Out of Range
25711 Solar Array Fault
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.
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. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
38 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem Specific Problem of the alarm(Low Voltage, High Temperature, Manual Stop, Remote
Control)
Alarm Impact
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
System Actions
None
Possible Causes
The mains input is out of range.
The power module is faulty.
The batteries are overheated.
The batteries are powered off manually.
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:
25622 Mains Input Out of Range
25626 Power Module Abnormal
25654 Battery Temperature Unacceptable
13/11/2012 9:15
Fault Management
39 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific
Problem
Alarm Impact
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
13/11/2012 9:15
Fault Management
40 de 526
Alarm Severity
Alarm Impact
station decreases and therefore the cell coverage area shrinks.
System Actions
None
Possible Causes
The batteries are not installed.
The power module is faulty.
The circuit breaker of the batteries is switched off or the battery contactor is switched off.
The batteries are faulty or worn-out.
The corresponding monitoring device is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check whether one of the following correlated alarms is reported on the M2000:
25626 Power Module Abnormal
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.
b. Clear the correlated alarm with recommended actions.
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. 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
13/11/2012 9:15
Fault Management
41 de 526
Parameters
13/11/2012 9:15
Fault Management
42 de 526
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem Specific Problem of the alarm(Power Module Fault, Power Module Protection, Power
Module Shutdown)
Alarm Impact
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.
The power module 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:
25652 Cabinet Temperature Unacceptable
25654 Battery Temperature Unacceptable
25650 Ambient Temperature Unacceptable
25622 Mains Input Out of Range
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.
13/11/2012 9:15
Fault Management
43 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
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.
The corresponding monitoring device is faulty.
Procedure
1. Check the cable connection between the surge protector and the monitoring device on site.
13/11/2012 9:15
Fault Management
44 de 526
a. Check whether the cable between the surge protector and the monitoring device is
functional and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 2.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.
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 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.
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 3.
3. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The power module is not installed or not in position. The faulty power module cannot
13/11/2012 9:15
Fault Management
45 de 526
Alarm Severity
Alarm Impact
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 power module is faulty.
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.
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.
c. Install the power module.
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 installation of the monitoring module on site.
a. Remove the monitoring module, and then reinstall it properly.
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 3.
3. Replace the power module on site.
a. Replace the power module.
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 4.
13/11/2012 9:15
Fault Management
46 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
47 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
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 -20C.
Y => Both the battery temperature and the ambient temperature are lower than -20C.
Go to sub-step b.
N => The battery temperature or the ambient temperature is not lower than -20C. Go
to step 2.
b. Replace the heater on site.
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 Miniature Circuit Breaker (MCB) state and connections of the AC input power cable of
the heater on site.
13/11/2012 9:15
Fault Management
48 de 526
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.
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 3.
3. Replace the temperature sensor in the battery cabin on site.
a. Replace the sensor.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The communication cable between the DSAC and the monitoring device fails.
The DSAC fails.
The corresponding monitoring device is faulty.
Procedure
1. Check the connections of the communication cable on site.
13/11/2012 9:15
Fault Management
49 de 526
a. Check whether the cable between the DSAC and the monitoring device is functional and
the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 2.
N => The cable is loose, worn-out, damaged, or incorrectly connected.. Go to sub-step
b.
b. Reconnect or replace the cable.
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. Replace the DSAC on site.
a. Replace the DSAC.
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 3.
3. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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
13/11/2012 9:15
Fault Management
50 de 526
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.
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 4.
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.
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 3.
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.
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 4.
4. Replace the monitoring device on site.
13/11/2012 9:15
Fault Management
51 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Load current
Load current
Battery current
Battery current
Voltage
DC Voltage
Alarm Impact
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Repeat step 1 until the alarm is cleared or until all the slots are occupied.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
52 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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.
The corresponding monitoring device is faulty.
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.
Y => The threshold is proper. Go to step 2.
N => The threshold is improper. Go to sub-step b.
b. Run the MML command MOD EMU to set the alarm threshold based on the
configuration planning.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
53 de 526
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
54 de 526
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
Minor
The equipment may be damaged, and the life span may be shortened.
System Actions
None
Possible Causes
The setting of the alarm threshold is improper.
The ambient humidity in the equipment room is abnormal.
The cable connection is faulty.
The humidity sensor malfunctions.
The corresponding monitoring device is faulty.
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.
Y => The threshold is proper. Go to step 2.
N => The threshold is improper. Go to sub-step b.
b. Run the MML command MOD EMU to set the alarm threshold based on the
configuration planning.
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 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.
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 3.
3. Check the cable connection between the humidity sensor and the monitoring device on site.
13/11/2012 9:15
Fault Management
55 de 526
a. Check whether the cable between the corresponding sensor and the monitoring device
is functional and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 4.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.
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 4.
4. Replace the humidity sensor on site.
a. Replace the sensor.
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 5.
5. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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
13/11/2012 9:15
Fault Management
56 de 526
None
Possible Causes
The ambient temperature is out of range.
The heat dissipation system of the cabinet is faulty.
The setting of the alarm threshold is improper.
The cable connection of the sensor is faulty.
The sensor is faulty.
The monitoring device is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:
25650 Ambient Temperature Unacceptable
25656 Cabinet Air Inlet Temperature Unacceptable
25655 Cabinet Air Outlet Temperature Unacceptable
25673 Fan Stalled
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.
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 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.
Check whether the alarm threshold is proper according to the configuration planning.
Y => The threshold is proper. Go to step 3.
N => The threshold is improper. Go to sub-step b.
b. Run the MML command MOD TCU to set the alarm threshold based on the
configuration planning.
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 3.
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.
Y => The cable is functional and the connection is correct. Go to step 4.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.
13/11/2012 9:15
Fault Management
57 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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.
The heat dissipation system of the cabinet is faulty.
The setting of the alarm threshold is improper.
The cable connection of the sensor is faulty.
The sensor is faulty.
13/11/2012 9:15
Fault Management
58 de 526
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:
25651 Ambient Humidity Unacceptable
25673 Fan Stalled
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.
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 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.
Check whether the alarm threshold is proper according to the configuration planning.
Y => The threshold is proper. Go to step 3.
N => The threshold is improper. Go to sub-step b.
b. Run the MML command MOD EMU to set the alarm threshold based on the
configuration planning.
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 3.
3. Check the cable connection between the humidity 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.
Y => The cable is functional and the connection is correct. Go to step 4.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.
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 4.
4. Replace the cabinet humidity sensor on site.
a. Replace the sensor.
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 5.
5. Replace the monitoring device on site.
13/11/2012 9:15
Fault Management
59 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
Major/Minor
System Actions
None
Possible Causes
The cabinet temperature is out of range.
The heater in the battery cabin is faulty.
The setting of the alarm threshold is improper.
The cable connection between the battery temperature sensor and the monitoring device is faulty.
The battery temperature 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:
25650 Ambient Temperature Unacceptable
25656 Cabinet Air Inlet Temperature Unacceptable
25655 Cabinet Air Outlet Temperature Unacceptable
25673 Fan Stalled
25632 Battery Cabin Heater Fault
13/11/2012 9:15
Fault Management
60 de 526
Fault Management
61 de 526
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
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific
Problem
Specific Problem of the alarm(Too High, Too Low, Cabinet Air Inlet-to-Outlet Temperature
Difference Too Large)
Alarm Impact
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 cabinet temperature is out of range.
The heat dissipation system of the cabinet is faulty.
The setting of the alarm threshold is improper.
The cable connection of the sensor is faulty.
The sensor is faulty.
The air filter is blocked.
The monitoring device is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:
25650 Ambient Temperature Unacceptable
25656 Cabinet Air Inlet Temperature Unacceptable
25673 Fan Stalled
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
13/11/2012 9:15
Fault Management
62 de 526
13/11/2012 9:15
Fault Management
63 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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 equipment is affected, and the services may be
disrupted.
System Actions
None
Possible Causes
The heat dissipation system of the cabinet malfunctions.
The ambient temperature is out of range.
The cable connection of the sensor is faulty.
The sensor is faulty.
The monitoring device is faulty.
13/11/2012 9:15
Fault Management
64 de 526
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:
25650 Ambient Temperature Unacceptable
25673 Fan Stalled
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.
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 cabinet temperature on the M2000.
a. Check for the correlated alarm on the M2000:
25652 Cabinet Temperature Unacceptable
25655 Cabinet Air Outlet Temperature Unacceptable
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.
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 4.
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.
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 4.
4. Check the cable connection between the temperature sensor and the monitoring device on site.
a. Check whether the cable between the temperature sensor and the monitoring device is
functional and the connection is correct.
13/11/2012 9:15
Fault Management
65 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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.
13/11/2012 9:15
Fault Management
66 de 526
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.
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 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
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.
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 3.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the TEC module.
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 4.
4. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
67 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Critical
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.
The corresponding 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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
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 3.
3. Check the cable connection between the sensor and the monitoring device on site.
13/11/2012 9:15
Fault Management
68 de 526
a. Check whether the cable between the corresponding sensor and the monitoring device
is functional and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 4.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.
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 4.
4. Replace the water sensor on site.
a. Replace the sensor.
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 5.
5. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Critical
System Actions
None
Possible Causes
The alarm disable function of the smoke alarm is configured incorrectly.
13/11/2012 9:15
Fault Management
69 de 526
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.
a. Run the MML command LST EMU(EMU)/LST PMU(PMU) on the M2000 to check
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.
b. Run the MML command MOD EMU(EMU)/MOD PMU(PMU) on the M2000 to disable
the smoke alarm. Then, run the MML command CLR PMUALM(PMU)/CLR
EMUALM(EMU) to clear the smoke alarm.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
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 3.
3. Check the cable connection between the sensor and the monitoring device on site.
a. Check whether the cable between the correlated sensor and the monitoring device is
functional and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 4.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
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.
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 4.
4. Replace the smoke sensor on site.
a. Replace the sensor. Then, run the MML command CLR PMUALM(PMU)/CLR
13/11/2012 9:15
Fault Management
70 de 526
EMUALM(EMU) on the M2000 to clear the smoke alarm. Wait for two minutes.
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 5.
5. Replace the monitoring device on site.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
Critical
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.
The sensor is faulty.
The corresponding 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.
13/11/2012 9:15
Fault Management
71 de 526
a. Run the MML command LST EMU(EMU)/LST PMU(PMU) on the M2000 to check
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.
b. Run the MML command MOD EMU(EMU)/MOD PMU(PMU) on the M2000 to disable
the door status alarm or infrared alarm.
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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
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.
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 3.
3. Check the cable connection between the sensor and the monitoring device on site.
a. Check whether the cable between the correlated sensor and the monitoring device is
functional and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 4.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the cable.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Based on the alarm detailed information, check whether "Board Type" is "EMU".
Y => The board type is EMU. Go to sub-step d.
13/11/2012 9:15
Fault Management
72 de 526
Parameters
Parameter
Name
Parameter Description
13/11/2012 9:15
Fault Management
73 de 526
Cabinet No.
Subrack No.
Slot No.
Fan No.
Faulty fan number (Inner air circulation fan, Outer air circulation fan, Main fan, Extension fan
group 1)
Board Type
Alarm Impact
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 corresponding monitoring device is faulty.
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.
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. (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
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.
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 3.
3. Check the fan module on site.
13/11/2012 9:15
Fault Management
74 de 526
a. Remove the fan subrack. Eliminate foreign objects around the fan, and then reinstall the
fan subrack.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the fan box.
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 4.
4. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The alarm cable connection between the diesel generator and the monitoring device is faulty.
The diesel generator is faulty.
The corresponding monitoring device is faulty.
Procedure
1. Check the alarm cable connection between the diesel generator and the monitoring device on site.
13/11/2012 9:15
Fault Management
75 de 526
a. Check whether the alarm cable between the diesel generator and the monitoring device
is functional and the connection is correct.
Y => The cable is functional and the connection is correct. Go to step 2.
N => The cable is loose, worn-out, damaged, or incorrectly connected. Go to sub-step
b.
b. Reconnect or replace the alarm cable.
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 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.
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 3.
3. Replace the monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
13/11/2012 9:15
Fault Management
76 de 526
None
Possible Causes
The fuel in the diesel generator is insufficient.
The alarm cable connection is faulty.
The sensor is faulty.
The corresponding monitoring device 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.
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 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.
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 alarm cable.
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 3.
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.
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 4.
4. Replace the corresponding monitoring device on site.
a. Replace the monitoring device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
77 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
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.
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:
25695 Diesel Generator Fault
25696 Diesel Generator Low Fuel
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.
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 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.
13/11/2012 9:15
Fault Management
78 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Array No.
Solar array No. If the array No. is 0, it indicates that the array is unknown.
Board Type
Alarm Impact
Major
The solar array cannot provide the power supply to the system.
System Actions
None
13/11/2012 9:15
Fault Management
79 de 526
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.
The monitoring device is faulty.
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.
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 3.
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.
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 4.
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.
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 5.
13/11/2012 9:15
Fault Management
80 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Array No.
Solar array No. If the array No. is 0, it indicates that the array is unknown.
Board Type
Alarm Impact
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.
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:
25710 Loss of Solar Array
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.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
81 de 526
Parameters
13/11/2012 9:15
Fault Management
82 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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 ambient temperature is out of range.
The setting of the alarm threshold is improper.
The internal temperature of the solar controller is too high.
The cables of the temperature sensor are faulty.
The temperature 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:
25650 Ambient Temperature Unacceptable
25656 Cabinet Air Inlet Temperature Unacceptable
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.
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. (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
configuration planning.
Y => The threshold is proper. Go to step 3.
13/11/2012 9:15
Fault Management
83 de 526
13/11/2012 9:15
Fault Management
84 de 526
This alarm is reported when the user-configured inter-CCU topology is inconsistent with the actual inter-CCU
topology.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Major
System Actions
None
Possible Causes
Data configuration of a CCU is incorrect.
The inter-CCU cables are incorrectly connected.
Procedure
1. Check for the correlated alarm on the M2000.
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
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 with recommended actions.
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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
85 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Specific Problem Fault type (FE_L connected to FE_L, FE_R connected to FE_R, Ring network, Other
network)
Alarm Impact
Major
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.
13/11/2012 9:15
Fault Management
86 de 526
13/11/2012 9:15
Fault Management
87 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Radio Access
Technology
Radio access technology (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Alarm Impact
Minor
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
1. Check for the correlated alarm on the M2000.
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
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 with recommended actions.
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 site configuration on the M2000.
a. Run the MML command LST CCU to check whether the cabinet/subrack/slot of the
13/11/2012 9:15
Fault Management
88 de 526
13/11/2012 9:15
Fault Management
89 de 526
hours.
Replace the BBU environment interface unit on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Major
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.
13/11/2012 9:15
Fault Management
90 de 526
13/11/2012 9:15
Fault Management
91 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Major
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 peer device is faulty.
Procedure
1. Check the E1/T1 configuration on site.
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.
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 E1/T1 transmission link on site.
a. Check whether the E1/T1 transmission link is normal. Check for the damaged cable,
13/11/2012 9:15
Fault Management
92 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
93 de 526
Port No.
Alarm Impact
Minor
System Actions
The system disables the associated E1/T1 link.
Possible Causes
The E1/T1 link is configured incorrectly.
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.
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.
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 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.
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 3.
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.
13/11/2012 9:15
Fault Management
94 de 526
a. Run the MML command RST BRD to reset the faulty board.
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 5.
5. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
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. 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.
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 7.
7. Check the peer device.
a. Troubleshoot the fault on the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Major
13/11/2012 9:15
Fault Management
95 de 526
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.
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.
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 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.
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 3.
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.
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 5.
5. Replace the faulty board on site.
13/11/2012 9:15
Fault Management
96 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Minor
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.
13/11/2012 9:15
Fault Management
97 de 526
Procedure
1. Check the E1/T1 configuration on site.
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.
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 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.
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 3.
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.
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 5.
5. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
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. Check whether the E1/T1 transmission trunk is functional.
13/11/2012 9:15
Fault Management
98 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
99 de 526
13/11/2012 9:15
Fault Management
100 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
13/11/2012 9:15
Fault Management
101 de 526
Alarm Severity
Alarm Impact
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.
a. Check for the correlated alarm on the M2000:
26262 External Clock Reference Problem
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 with recommended actions. Then, wait for 15 minutes.
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 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.
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 3.
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.
13/11/2012 9:15
Fault Management
102 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Loopback Type
Alarm Impact
Minor
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.
13/11/2012 9:15
Fault Management
103 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
104 de 526
Link No.
Alarm Impact
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:
26262 External Clock Reference Problem
Y => The correlated alarm exists. Go to sub-step c.
N => The correlated alarm does not exist. Go to step 2.
c. Clear the correlated alarm with recommended actions.
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 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.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
105 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
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 E1/T1 link is faulty.
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:
Y => The correlated alarm exists. Go to sub-step b.
13/11/2012 9:15
Fault Management
106 de 526
13/11/2012 9:15
Fault Management
107 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
13/11/2012 9:15
Fault Management
108 de 526
Alarm Severity
Alarm Impact
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 E1/T1 link is faulty.
The configuration of the IMA link group 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 link on the
M2000:
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 with recommended actions.
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 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.
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 MOD IMAGRP to change the local IMA group configuration.
Ensure that the local IMA group configuration matches the peer.
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 3.
3. Check the local IMA link on the M2000.
a. Perform the IMA link loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
109 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
110 de 526
System Actions
The system disables the associated IMA link.
Possible Causes
The E1/T1 link is faulty.
The local IMA link configuration 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 link on the
M2000:
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 with recommended actions.
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 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.
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 3.
3. Check the local IMA link on the M2000.
a. Perform the IMA link loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Run the MML command RST IMAGRP to reset the IMA link group.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Reconfigure the IMA link.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
111 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
Minor
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 E1/T1 link is faulty.
13/11/2012 9:15
Fault Management
112 de 526
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
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 with recommended actions.
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 local IMA link on the M2000.
a. Perform the IMA link loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Run the MML command RST IMAGRP to reset the IMA link group.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Reconfigure the IMA link.
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 3.
3. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the faulty board.
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 4.
4. Check whether the peer IMA is normal.
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.
13/11/2012 9:15
Fault Management
113 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
114 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
Minor
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 IMA link at the far end is unusable.
Procedure
1. Check whether the peer IMA is normal.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
115 de 526
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
Minor
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 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.
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
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 with recommended actions.
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 whether the peer IMA is normal.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
116 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Minor
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
117 de 526
Subrack No.
Slot No.
Group No.
Specific Problem
Alarm Impact
Major
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
1. Locate the cause of the alarm on the M2000.
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.
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 4.
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.
13/11/2012 9:15
Fault Management
118 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Minor
System Actions
The system automatically disables the IMA links of the IMA group and disables the IMA group.
Possible Causes
The parameter settings of the local and peer IMA group are inconsistent.
Procedure
13/11/2012 9:15
Fault Management
119 de 526
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.
N => The parameter settings are inconsistent. Go to step 2.
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.
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 3.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Major
13/11/2012 9:15
Fault Management
120 de 526
System Actions
None
Possible Causes
The IMA link is faulty.
The E1/T1 link is faulty.
The E1/T1 cable is connected incorrectly.
Procedure
1. Check the local 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
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 with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
121 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Minor
System Actions
None
Possible Causes
The IMA link is faulty.
The E1/T1 link is faulty.
Procedure
1. Check for the correlated alarm 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
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 with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. The E1/T1 cable malfunctions. Go to step 2.
2. Check whether the peer IMA is normal.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
122 de 526
Description
This alarm is reported when the IMA group at the far end is blocked.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Minor
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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
123 de 526
Alarm Impact
Major
The signaling link between the base station and the RNC is faulty. In this case, the
ongoing services are disrupted.
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.
Y => The correlated alarm exists. Go to sub-step c.
N => The correlated alarm does not exist. Go to sub-step d.
c. Clear the correlated alarm with recommended actions.
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 5.
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.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
124 de 526
13/11/2012 9:15
Fault Management
125 de 526
13/11/2012 9:15
Fault Management
126 de 526
Parameters
Parameter Name
Parameter Description
Alarm Impact
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.
The board hardware is faulty.
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/MLPPPcorrelated alarms on the link.
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to sub-step c.
b. Clear the correlated alarm with recommended actions.
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 5.
13/11/2012 9:15
Fault Management
127 de 526
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.
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 3.
3. Check the SCTP link on the M2000.
a. Check for the correlated alarms on the M2000:
25888 SCTP Link Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 4.
b. Clear the correlated alarm with recommended actions.
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 5.
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.
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 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.
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 5.
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.
b. Run the MML command LST SAALLNK to query the associated physical link bearing
the SAAL link.
13/11/2012 9:15
Fault Management
128 de 526
c. Check the link (UNI/IMA/Fractional ATM/SDH/SONET) bearing the SAAL link. Check for
Fractional ATM/UNI/IMA-correlated alarms, or SDH/SONET-correlated alarms on the
physical link.
Y => The correlated alarm exists. Go to sub-step d.
N => The correlated alarm does not exist. Go to step 6.
d. Clear the correlated alarm with recommended actions.
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 6.
6. Check the SAAL link on the M2000.
a. Check for the correlated alarms on the M2000:
25840 SAAL Link Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 7.
b. Clear the correlated alarm with recommended actions.
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 8.
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.
b. Run the MML command LST SAALLNK to query the attributes of the associated SAAL
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.
Y => The local settings are consistent with the peer settings. Go to step 8.
N => The local settings are inconsistent with the peer settings. Go to sub-step c.
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.
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 8.
8. Reset the faulty board.
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
129 de 526
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
Parameter Name
Parameter Description
Node Type
Node No.
Alarm Impact
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.
The board hardware is faulty.
Procedure
1. Check the physical link bearing the SAAL on the M2000.
a. Run the MML command LST AAL2NODE to query the SAAL link bearing the faulty
ALCAP.
b. Run the MML command LST SAALLNK to query the associated physical link bearing
the SAAL link for the ALCAP.
c. Check the link (UNI/IMA/Fractional ATM/SDH/SONET) bearing the SAAL link. Check for
Fractional ATM/UNI/IMA-correlated alarms, or SDH/SONET-correlated alarms on the
physical link.
Y => The correlated alarm exists. Go to sub-step d.
N => The correlated alarm does not exist. Go to step 2.
d. Clear the correlated alarm with recommended actions.
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 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.
13/11/2012 9:15
Fault Management
130 de 526
b. Run the MML command LST SAALLNK to query the attributes of the associated SAAL
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.
Y => The local settings are consistent with the peer settings. Go to step 3.
N => The local settings are inconsistent with the peer settings. Go to sub-step c.
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.
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 3.
3. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Alarm Impact
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.
13/11/2012 9:15
Fault Management
131 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
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.
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 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.
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 3.
b. Clear the correlated alarm according to the handling suggestions associated with the
E1/T1, UNI, IMA, Fractional ATM, or SDH/SONET alarms.
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 3.
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.
13/11/2012 9:15
Fault Management
132 de 526
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.
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 4.
4. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the faulty board.
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 5.
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.
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 6.
6. Reset the peer board on the AAL2 Path.
a. Reset the peer board on the AAL2 Path.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Alarm Impact
Major
System Actions
None
13/11/2012 9:15
Fault Management
133 de 526
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
1. Check the physical link bearing the SAAL 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 SAAL link.
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 with recommended actions.
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 parameter settings of the SAAL link on the M2000.
a. Run the MML command LST SAALLNK to query the attributes of the associated SAAL
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.
Y => The local settings are consistent with the peer settings. Go to step 3.
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.
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 3.
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.
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 4.
4. Reset the faulty board on the M2000.
13/11/2012 9:15
Fault Management
134 de 526
a. Run the MML command RST BRD to reset the faulty board.
b. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Bandwidth (bit/s)
Transmit bandwidth
Alarm Impact
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.
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. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
135 de 526
Description
This alarm is reported when the PPP/MLPPP link status is changed from UP to DOWN.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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 E1/T1 link is faulty.
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.
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 with recommended actions.
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 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
13/11/2012 9:15
Fault Management
136 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Major
System Actions
None
Possible Causes
The E1/T1 link is faulty.
The parameter settings on the two ends of the MLPPP group are inconsistent.
All the links in the MLPPP group are faulty.
13/11/2012 9:15
Fault Management
137 de 526
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.
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 with recommended actions.
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 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.
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 3.
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.
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 4.
4. Check the status of the negotiation on the M2000.
a. Run the MML command RST MPGRP to reset the MLPPP group.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
138 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Minor
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.
N => The threshold is improper. Go to sub-step b.
b. Run the MML command RMV MPGRP,ADD MPGRP to reconfigure the packet loss rate
threshold of the MLPPP group.
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 for the E1/T1-correlated alarms on the M2000.
a. Check for the E1/T1-correlated alarms on the M2000.
Y => The correlated alarm exists. Go to sub-step b.
13/11/2012 9:15
Fault Management
139 de 526
N => The correlated alarm does not exist. Contact Huawei Customer Service Center.
b. Clear the correlated alarm with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Alarm Impact
Minor
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.
Y => The threshold is proper. Go to step 2.
N => The threshold is improper. Go to sub-step b.
b. Run the MML command RMV PPPLNK,ADD PPPLNK to modify the FER threshold of
the PPP link.
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.
13/11/2012 9:15
Fault Management
140 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
141 de 526
13/11/2012 9:15
Fault Management
142 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Major
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.
N => The parameter settings are inconsistent. Go to step 2.
e. Check whether the parameter settings of the peer Ethernet port are consistent with the
network plan.
Y => The parameter settings are consistent. Go to step 4.
N => The parameter settings are inconsistent. Go to step 3.
2. Set the local Ethernet parameters on the M2000.
13/11/2012 9:15
Fault Management
143 de 526
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.
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 4.
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.
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 4.
4. Reset the local Ethernet port on the M2000.
a. Run the MML command RST ETHPORT to reset the local Ethernet port.
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 5.
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.
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 6.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
144 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
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
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.
N => The parameter settings are inconsistent. Go to step 2.
e. Check whether the parameter settings of the peer Ethernet port are consistent with the
network plan.
Y => The parameter settings are consistent. Go to step 4.
N => The parameter settings are inconsistent. Go to step 3.
2. Set the local Ethernet parameters on the M2000.
a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Run the MML
13/11/2012 9:15
Fault Management
145 de 526
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.
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 4.
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.
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 4.
4. Reset the local Ethernet port on the M2000.
a. Run the MML command RST ETHPORT to reset the local Ethernet port.
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 5.
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.
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 6.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
146 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Minor
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
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 with recommended actions.
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 9.
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.
13/11/2012 9:15
Fault Management
147 de 526
13/11/2012 9:15
Fault Management
148 de 526
13/11/2012 9:15
Fault Management
149 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Minor
The ongoing services carried over the Ethernet port deteriorate. The services may
even be disrupted.
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.
Procedure
1. 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 the OAM3AH is activated.
Y => The status of the Ethernet port is activated. Contact Huawei Customer Service
Center.
N => The status of the Ethernet port is not activated. Go to step 2.
13/11/2012 9:15
Fault Management
150 de 526
2. Check the settings of the local Ethernet port and the peer Ethernet port on the M2000.
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, Speed, and Duplex.
Y => The parameter settings are consistent. Go to step 5.
N => The parameter settings are inconsistent. Go to sub-step d.
d. Check whether the settings of the local Ethernet port are consistent with the network
plan.
Y => The parameter settings are consistent. Go to sub-step e.
N => The parameter settings are inconsistent. Go to step 3.
e. Check whether the settings of the peer Ethernet port are consistent with the network
plan.
Y => The parameter settings are consistent. Go to step 5.
N => The parameter settings are inconsistent. Go to step 4.
3. Change the settings of the local Ethernet port on the M2000.
a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Run the MML
command SET ETHPORT to change the Ethernet port attribute, maximum transmission
unit, speed, and duplex mode. Ensure that the local parameter settings are consistent
with the peer parameter settings.
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 5.
4. Change the settings of the peer Ethernet port on the M2000.
a. (For NodeBs, port attribute of the Ethernet port is unchangeable.) Change the Ethernet
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.
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 5.
5. Reset the local Ethernet port on the M2000.
a. Run the MML command RST ETHPORT to reset the Ethernet port.
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 6.
6. Check the Ethernet cables connected to the Ethernet port on site.
a. Check whether the RUN LED is running properly on the Ethernet port.
Y => The RUN LED is running properly. Go to step 7.
13/11/2012 9:15
Fault Management
151 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Minor
The ongoing services carried over the Ethernet port deteriorate. The services may
even be disrupted.
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 peer device is faulty.
Procedure
13/11/2012 9:15
Fault Management
152 de 526
13/11/2012 9:15
Fault Management
153 de 526
Parameters
Parameter Name
Parameter Description
IP Address
IP address
Cabinet No.
Subrack No.
Slot No.
Interface Type
Interface No.
Interface number
Alarm Impact
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.
13/11/2012 9:15
Fault Management
154 de 526
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.
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 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
IP Path No.
IP path number
Cabinet No.
Subrack No.
Slot No.
Description
13/11/2012 9:15
Fault Management
155 de 526
Alarm Severity
Alarm Impact
Major
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.
Y => The correlated alarm exists. Go to sub-step c.
N => The correlated alarm does not exist. Go to step 2.
c. Clear the correlated alarm with recommended actions.
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 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.
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 3.
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
13/11/2012 9:15
Fault Management
156 de 526
configuration.
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 4.
4. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Link No.
Alarm Impact
Minor
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.
Procedure
1. 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 the trunk link is activated.
Y => The status of the Ethernet port is activated. Contact Huawei Customer Service
Center.
13/11/2012 9:15
Fault Management
157 de 526
13/11/2012 9:15
Fault Management
158 de 526
Parameters
Parameter Name
Parameter Description
Description
Alarm Impact
Major
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.
13/11/2012 9:15
Fault Management
159 de 526
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.
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 with recommended actions.
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 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.
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 3.
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.
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 4.
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.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
160 de 526
Parameters
Parameter Name
Parameter Description
Description
Alarm Impact
Minor
The services are disrupted because the data cannot be transmitted due to
insufficient space of the sending buffer.
13/11/2012 9:15
Fault Management
161 de 526
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.
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 with recommended actions.
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. Reset the faulty board.
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Peer Name
Alarm Impact
13/11/2012 9:15
Fault Management
162 de 526
Alarm Severity
Alarm Impact
Major
System Actions
None
Possible Causes
The Ethernet link is faulty.
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
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 with recommended actions.
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 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.
Y=> The parameter settings are consistent. Go to step 3.
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.
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 3.
3. Check the peer device.
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.
13/11/2012 9:15
Fault Management
163 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Alarm Impact
Major
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.
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 3.
2. Stop the ETHOAM 3AH loopback test at the peer end.
a. Request the peer engineers to stop the ETHOAM 3AH loopback test.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
164 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Group No.
Alarm Impact
Major
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
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
13/11/2012 9:15
Fault Management
165 de 526
13/11/2012 9:15
Fault Management
166 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
Check whether the alarm is cleared.
Y=> The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
167 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Interface Type
Interface No.
Interface number
Alarm Impact
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/MLPPPcorrelated alarms on the associated link.
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 with recommended actions.
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.
13/11/2012 9:15
Fault Management
168 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
IP Path No.
IP path number
Description
Alarm Impact
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.
13/11/2012 9:15
Fault Management
169 de 526
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 .
Y=> The parameter settings are consistent. Go to step 2.
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.
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 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
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 3.
b. Clear the correlated alarm with recommended actions.
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 3.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
170 de 526
Cabinet No.
Subrack No.
Slot No.
BFD No.
Alarm Impact
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
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 with recommended actions.
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 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.
13/11/2012 9:15
Fault Management
171 de 526
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.
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 3.
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.
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 4.
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.
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 4.
4. Check the peer device or the peer BFD configuration.
a. Check whether the peer device is faulty (incorrect configuration, for example).
13/11/2012 9:15
Fault Management
172 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Session ID
IP PM Session ID
Alarm
Cause
Alarm Cause (Activation timeout, DSCP modified, Activation of peer ippmsession is forbidden,
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
Problem
Alarm Impact
Minor
The data packet loss or delay on the link between the base station and the peer
device cannot be detected.
System Actions
13/11/2012 9:15
Fault Management
173 de 526
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
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 with recommended actions.
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 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.
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 3.
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.
13/11/2012 9:15
Fault Management
174 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
175 de 526
13/11/2012 9:15
Fault Management
176 de 526
Parameters
Parameter Name
Parameter Description
Alarm Impact
Minor
The OMCH may fail. The subscribers may fail to access the network.
System Actions
None
Possible Causes
13/11/2012 9:15
Fault Management
177 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
Y => The parameter settings are consistent. Go to step 5.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
178 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
179 de 526
13/11/2012 9:15
Fault Management
180 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
181 de 526
Alarm Impact
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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
182 de 526
13/11/2012 9:15
Fault Management
183 de 526
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.
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 9.
9. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
184 de 526
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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Reinsert the connector of the optical fiber into the optical module on the board securely.
a. Reinsert the connector of the optical fiber into the optical module on the board securely.
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 4.
4. Check that the local optical module matches the optical fiber on site.
a. Check whether the local optical module matches the optical fiber.
13/11/2012 9:15
Fault Management
185 de 526
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.
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 5.
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.
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 6.
6. 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.
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 7.
7. (Skip this step and go to step 8 if the optical module is already replaced) Replace the optical
module on site.
a. Replace the optical module.
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 8.
8. 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. You can infer that the local optical sub-board is damaged.
Go to sub-step b.
N => The alarm is not cleared. Go to step 9.
b. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 9.
13/11/2012 9:15
Fault Management
186 de 526
9. 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 10.
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.
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 10.
10. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET AU No.
Alarm Impact
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
The system disables the corresponding optical link.
Possible Causes
13/11/2012 9:15
Fault Management
187 de 526
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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
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.
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 4.
4. Clean the connector of the local optical fiber on site.
a. Remove the connector and clean it by using absorbent cotton with absolute alcohol.
13/11/2012 9:15
Fault Management
188 de 526
13/11/2012 9:15
Fault Management
189 de 526
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
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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 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).
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, or
the device is faulty.
The optical transmission link is faulty.
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.
13/11/2012 9:15
Fault Management
190 de 526
13/11/2012 9:15
Fault Management
191 de 526
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
192 de 526
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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
The working mode of the local optical port is set incorrectly.
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 does not match 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 and multiplexing mode between the
local and 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 working mode of the local optical
port.
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 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.
13/11/2012 9:15
Fault Management
193 de 526
13/11/2012 9:15
Fault Management
194 de 526
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.
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 8.
8. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
13/11/2012 9:15
Fault Management
195 de 526
On the peer end, the configuration of the optical port is incorrect, the optical connection is faulty, 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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
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.
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 4.
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.
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 5.
13/11/2012 9:15
Fault Management
196 de 526
13/11/2012 9:15
Fault Management
197 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Warning
System Actions
The system disables the corresponding optical link.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
198 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Minor
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 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.
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 service configuration of the optical port on the peer device.
a. Contact the maintenance engineers responsible for the peer optical device, and ask
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.
b. Contact the maintenance engineers responsible for the peer optical device, and ask
them to change the service configuration of the optical port on the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
199 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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
The working mode of the local optical port is set incorrectly.
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.
13/11/2012 9:15
Fault Management
200 de 526
On the peer end, the configuration of the optical port is incorrect, the optical connection is faulty, 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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
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.
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 4.
4. 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.
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 5.
5. Replace the optical module on site.
a. Replace the optical module.
13/11/2012 9:15
Fault Management
201 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
202 de 526
Subrack No.
Slot No.
Alarm Impact
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
The working mode of the local optical port is set incorrectly.
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, 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 and multiplexing mode between the
local and 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.
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 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.
13/11/2012 9:15
Fault Management
203 de 526
13/11/2012 9:15
Fault Management
204 de 526
b. Contact the maintenance engineers responsible for the peer optical device, and ask
them to rectify the fault on the peer optical device.
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 8.
8. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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
The working mode of the local optical port is set incorrectly.
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 does not match the optical fiber, or the device is faulty.
The optical transmission link is faulty.
13/11/2012 9:15
Fault Management
205 de 526
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 and multiplexing mode between the
local and 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.
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 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 in position. Go to sub-step b.
b. Reinstall the optical module on the local board securely.
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 3.
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.
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 4.
4. 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.
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 5.
5. Replace the optical module on site.
a. Replace the optical module.
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 6.
13/11/2012 9:15
Fault Management
206 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
207 de 526
Alarm Impact
Major
The data carried over the optical port is lost, and the service quality is degraded.
System Actions
None
Possible Causes
The working mode of the local optical port is set incorrectly.
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, 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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
208 de 526
13/11/2012 9:15
Fault Management
209 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET AU No.
Alarm Impact
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
The working mode of the local optical port is set incorrectly.
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
device is faulty, or the peer device sends an indication signal for generating the alarm.
The optical transmission link is faulty.
Procedure
13/11/2012 9:15
Fault Management
210 de 526
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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
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.
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 4.
4. 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.
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 5.
5. Replace the optical module on site.
a. Replace the optical module.
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 6.
6. Check that the local optical sub-board works properly.
13/11/2012 9:15
Fault Management
211 de 526
a. Connect the TX port of the optical sub-board and its RX port by using an optical fiber
for loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. You can infer that the local optical sub-board is damaged.
Go to sub-step b.
N => The alarm is not cleared. Go to step 7.
b. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 7.
7. 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 8.
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.
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 8.
8. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET HP No.
13/11/2012 9:15
Fault Management
212 de 526
Alarm Impact
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.
b. Contact the maintenance engineers responsible for the peer optical device, and ask
them to change the value of C2.
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 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 multiplexing configuration is proper and the connection is correct. Contact
Huawei Customer Service Center.
N => The multiplexing configuration is improper and the connection is incorrect. Go to
sub-step b.
b. Contact the maintenance engineers responsible for the optical transmission link, and
ask them to change the multiplexing configuration and the connection.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
213 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET HP No.
Alarm Impact
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.
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.
b. Contact the maintenance engineers responsible for the peer optical device, and ask
them to change the value of C2.
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 service configuration of the optical port on the peer device.
a. Contact the maintenance engineers responsible for the peer optical device, and ask
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.
b. Contact the maintenance engineers responsible for the peer optical device, and ask
13/11/2012 9:15
Fault Management
214 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET HP No.
Alarm Impact
Minor
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.
13/11/2012 9:15
Fault Management
215 de 526
The multiplexing configuration of the transmission link or the optical fiber connection is incorrect.
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.
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 service configuration of the optical port on the peer device.
a. Contact the maintenance engineers responsible for the peer optical device, and ask
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.
b. Contact the maintenance engineers responsible for the peer optical device, and ask
them to change the service configuration of the SDH service.
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 3.
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 multiplexing configuration is proper and the connection is correct. Contact
Huawei Customer Service Center.
N => The multiplexing configuration is improper and the connection is incorrect. Go to
sub-step b.
b. Contact the maintenance engineers responsible for the optical transmission link, and
ask them to change the multiplexing configuration and the connection.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
216 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET HP No.
Alarm Impact
Major
The E1/T1 links in the peer high-order path cannot carry services.
System Actions
None
Possible Causes
The working mode of the local optical port is set incorrectly.
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 does not match 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 and multiplexing mode between the
local and 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.
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.
13/11/2012 9:15
Fault Management
217 de 526
13/11/2012 9:15
Fault Management
218 de 526
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 8.
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.
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 8.
8. Check that the optical transmission link works properly.
a. Check for the faults in the optical transmission link, and rectify the faults.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
SDH/SONET HP No.
Alarm Impact
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
The working mode of the local optical port is set incorrectly.
The local optical module is not securely installed or not in position.
13/11/2012 9:15
Fault Management
219 de 526
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 and multiplexing mode between the
local and 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.
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 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:
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
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.
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 4.
4. 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
220 de 526
13/11/2012 9:15
Fault Management
221 de 526
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
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
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.
d. Run the MML command MOD FLOODDEFEND to modify the parameters related to the
alarm and the protection against flood packets.
13/11/2012 9:15
Fault Management
222 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Specific
Problem
Specific Problem of the alarm(Excessive Flood Packet, Excessive Invalid Packet, ARP
Snoofing, IPSec Replay)
Alarm Impact
Major
System Actions
None
Possible Causes
The base station is under the flood attack.
The base station is under the invalid packet attack.
13/11/2012 9:15
Fault Management
223 de 526
Procedure
1. Locate the cause of the alarm on the M2000.
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.
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 5.
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.
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 4.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Check the interconnected devices on the M2000.
13/11/2012 9:15
Fault Management
224 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
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 8.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
13/11/2012 9:15
Fault Management
225 de 526
Alarm Impact
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 board hardware is faulty.
The hardware of the main control board (in the subrack that houses the board) is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board on the M2000:
26200 Board Hardware Fault
26204 Board Not In Position
26214 Board Powered Off
26216 Board Not Securely Installed
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 with recommended actions.
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. Reseat the faulty board properly on site.
a. Reseat the board.
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 3.
3. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 4.
4. Reseat the main control board in the subrack that houses the faulty board on site.
13/11/2012 9:15
Fault Management
226 de 526
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.
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 5.
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original main control board. Contact Huawei
Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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.
13/11/2012 9:15
Fault Management
227 de 526
Alarm Severity
Alarm Impact
Minor
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
1. Check for the correlated alarm on the M2000.
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)
25652 Cabinet Temperature Unacceptable
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 with recommended actions.
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. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.
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 3.
3. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
13/11/2012 9:15
Fault Management
228 de 526
This alarm is reported when the board detects that the clock input signals are unavailable.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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 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.
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 board hardware is faulty.
The main control board is not securely installed.
The hardware of the main control board is faulty.
The BBU subrack is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the main control board on the M2000:
26200 Board Hardware Fault
26216 Board Not Securely Installed
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 with recommended actions.
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.
13/11/2012 9:15
Fault Management
229 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
13/11/2012 9:15
Fault Management
230 de 526
Alarm Impact
Major
The board cannot work normally. The ongoing services carried on the board are
disrupted. 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.
System Actions
None
Possible Causes
The power monitoring board is faulty.
The board hardware is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the power monitoring board on the M2000:
26112 BBU DC Output Out of Range
26200 Board Hardware Fault
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 with recommended actions.
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. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
231 de 526
Subrack No.
Slot No.
Board Type
Alarm Impact
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.
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. Replace the BBU fan module on site.
a. Remove the faulty fan module and install a spare fan module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
13/11/2012 9:15
Fault Management
232 de 526
Alarm Impact
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.
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. Replace the BBU fan module on site.
a. Remove the faulty fan module and install a spare fan module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
13/11/2012 9:15
Fault Management
233 de 526
Alarm Severity
Alarm Impact
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
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the site on the M2000:
25622 Mains Input Out of Range
25626 Power Module Abnormal
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 with recommended actions.
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 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.
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 3.
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.
13/11/2012 9:15
Fault Management
234 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Input Voltage(0.1V)
Specific Problem
Alarm Impact
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.
a. Check for the correlated alarm on the M2000:
25622 Mains Input Out of Range
25626 Power Module Abnormal
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to sub-step c.
13/11/2012 9:15
Fault Management
235 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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
13/11/2012 9:15
Fault Management
236 de 526
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.
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.
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.
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. 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
13/11/2012 9:15
Fault Management
237 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
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
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.
13/11/2012 9:15
Fault Management
238 de 526
N => The voltage is not 5 +/- 0.5 V, the satellite card is faulty. Go to step b.
b. Replace the board.
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.
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.
Y => The voltage is 5 +/- 0.5 V, go to sub-step c.
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.
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 3.
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.
Y => The voltage is 5 +/- 0.5 V, go to sub-step c.
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.
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 4.
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.
13/11/2012 9:15
Fault Management
239 de 526
c. Remove rust from the GPS feeder connector, reconnect the GPS feeder to the
antenna, and waterproof the GPS feeder connector.
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 d.
d. Replace the feeder according to the GPS Satellite Antenna System Quick Installation
Guide.
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 5. Y => The alarm is cleared. No further
action is required.
N => The alarm is not cleared. Go to sub-step c.
5. Replace the antenna on site.
a. Replace the antenna according to the GPS Satellite Antenna System Quick Installation
Guide.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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
None
Possible Causes
13/11/2012 9:15
Fault Management
240 de 526
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty GPS satellite card on the M2000:
26121 GPS Antenna Fault
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 with recommended actions.
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 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.
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 3.
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.
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 4.
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.
13/11/2012 9:15
Fault Management
241 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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 GPS satellite card hardware is faulty.
The cables connected to the GPS satellite card are faulty.
13/11/2012 9:15
Fault Management
242 de 526
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.
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.
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.
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. 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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the RGPS module by referring to the RGPS installation manual.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
243 de 526
Description
This alarm is reported when the board hardware is faulty.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The board cannot work normally. The ongoing services carried on the board may be
disrupted. 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.
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.
The board hardware is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board on the M2000:
26104 Board Temperature Unacceptable
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 with recommended actions.
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. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.
13/11/2012 9:15
Fault Management
244 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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:
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.
System Actions
The system resets the faulty processor.
Possible Causes
External electromagnetic interference or radiation exists.
13/11/2012 9:15
Fault Management
245 de 526
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.
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. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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.
13/11/2012 9:15
Fault Management
246 de 526
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.
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. 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.
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 3.
3. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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:
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.
13/11/2012 9:15
Fault Management
247 de 526
System Actions
The board or component is automatically reset.
Possible Causes
The board software program error occurs.
The board hardware is faulty.
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.
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. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.
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 3.
3. Replace the faulty board onsite.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
13/11/2012 9:15
Fault Management
248 de 526
Alarm Impact
Major
The board cannot work normally. The ongoing services carried on the board are
disrupted. 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.
System Actions
The system automatically disables the board and isolates the board from all other boards.
Possible Causes
The board does not exist or is not securely installed.
The backplane slot is faulty.
The board hardware 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
1. Reseat the board properly on site.
a. Reseat the board.
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 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).
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 3.
3. Replace the faulty board on site.
13/11/2012 9:15
Fault Management
249 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The board may not work normally. The ongoing services carried on the board are
disrupted. 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.
13/11/2012 9:15
Fault Management
250 de 526
Alarm Severity
Alarm Impact
The faulty board is a baseband board that provides the aggregation function.
System Actions
The system automatically disables the board and isolates the board from all other boards.
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 hardware is faulty.
The board is powered off.
The hardware of the main control board (in the subrack that houses the board) is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check whether any of the following correlated alarms is reported on the faulty board on
the M2000:
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26202 Board Overload
26203 Board Software Program Error
26204 Board Not In Position
26208 Board File System Damaged
26214 Board Powered Off
26216 Board Not Securely Installed
Y => A correlated alarm is reported. Go to sub-step b.
N => A correlated alarm is not reported. Go to step 2.
b. Clear the correlated alarm with recommended actions.
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. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.
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 3.
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).
13/11/2012 9:15
Fault Management
251 de 526
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.
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 4.
4. Reseat the board properly on site.
a. Reseat the board.
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 5.
5. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 6.
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.
Reseat the main control board.
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 7.
7. Replace the main control board in the subrack that houses the faulty board on site.
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
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original main control board. Contact Huawei
Customer Service Center.
13/11/2012 9:15
Fault Management
252 de 526
This alarm is reported when the actual slot of the main control board is inconsistent with its configured slot.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
13/11/2012 9:15
Fault Management
253 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
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
13/11/2012 9:15
Fault Management
254 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The user runs a command to block the board.
Procedure
13/11/2012 9:15
Fault Management
255 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Power off
Cause
Power-off cause (Temperature Too High, Power Saving, User Command, BBU Power Not
Enough, Fault, Other Cause)
Alarm Impact
Major
The ongoing 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.
System Actions
The system automatically disables the board and isolates the board from all other boards.
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.
13/11/2012 9:15
Fault Management
256 de 526
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board on the M2000:
26104 Board Temperature Unacceptable
26101 Inter-Board CANBUS Communication Failure
26112 BBU DC Output Out of Range
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 with recommended actions.
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 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.
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 4.
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.
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 5.
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
13/11/2012 9:15
Fault Management
257 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
RX Board Type
TX Board Type
Alarm Impact
Major
The boards involved in the communication may not work normally. The ongoing
services carried on the boards are disrupted.
System Actions
The system automatically disables the board and isolates the board from all other boards.
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:
26200 Board Hardware Fault
26201 Board Memory Soft Failure
13/11/2012 9:15
Fault Management
258 de 526
13/11/2012 9:15
Fault Management
259 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The board may not work normally. The ongoing services carried on the board are
disrupted. 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.
System Actions
None
Possible Causes
The board does not exist or is not securely installed.
The backplane slot is faulty.
The board hardware is faulty.
Procedure
1. Reseat the board properly on site.
a. Reseat the board.
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 backplane slot in the BBU on site.
a. Remove the board. Then, check whether there is any bent or broken pin in the
13/11/2012 9:15
Fault Management
260 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Alarm Impact
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
13/11/2012 9:15
Fault Management
261 de 526
Possible Causes
The optical module on the transmission port of the BBU is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board on the M2000:
26200 Board Hardware Fault
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 with recommended actions.
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. Reseat the optical module on site.
a. Reseat the faulty optical module on site.
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 3.
3. Replace the optical module on site.
a. On the BBU side, replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
13/11/2012 9:15
Fault Management
262 de 526
Alarm Severity
Alarm Impact
Major
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
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
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.
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 3.
c. Reseat the optical module. Ensure that it is securely installed.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
13/11/2012 9:15
Fault Management
263 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Specific Problem Specific Problem of the alarm(Receive No Signal, Receive Power Too High, Receive Power
Too Low)
Alarm Impact
Major
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.
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.
13/11/2012 9:15
Fault Management
264 de 526
System Actions
None
Possible Causes
The optical module on the transmission port of the BBU is faulty or not installed securely, or the cable
connection on the optical module is not ready.
The optical connector on the transmission port of the BBU is dirty.
The board where the faulty transmission port is located is faulty.
The optical module on the transmission port of the peer transmission device is faulty or not installed
securely, the cable connection on the optical module is not ready, or the peer transmission device is
faulty.
The optical connection between the BBU and the peer transmission device is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the faulty transmission port of the BBU on the
M2000:
26220 Transmission Optical Module Fault
26221 Transmission Optical Module Not In Position
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 with recommended actions.
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 transmission port of the BBU on site.
a. Reseat the optical module and connector on the faulty transmission port of the BBU on
site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
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 3.
3. Connect the TX and RX ports of the optical module for transmission on the BBU on site.
a. Remove the optical fiber from the optical module for transmission on the BBU. Then,
connect the TX and RX ports of the optical module by using an optical fiber for
loopback.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
265 de 526
Parameters
13/11/2012 9:15
Fault Management
266 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Specific Problem
Alarm Impact
Major
When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the transmission link may decrease significantly, or the
transmission link is broken.
Minor
When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the transmission link may decrease to some extent.
System Actions
None
Possible Causes
The optical module on the transmission port of the BBU is worn-out or not installed securely, or the
cable connection on the optical module is loose.
The optical connector on the transmission port of the BBU is dirty.
The optical module on the transmission port of the BBU is not supported by the BBU, in terms of type
(single-mode or multi-mode) and rate.
The optical port on the peer transmission device malfunctions.
The optical fibers between the BBU and the peer transmission device are bent, deformed, or
worn-out. Or the length of optical fibers is excessive, which leads to a high attenuation of optical
signals.
Procedure
1. Check the transmission port of the BBU on site.
a. Reseat the optical module and connector on the faulty transmission port of the BBU on
site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
13/11/2012 9:15
Fault Management
267 de 526
c. Check whether the optical module on the transmission port is supported by the BBU, in
terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5 Gbit/s).
Y => The optical module on the transmission port is supported. Go to sub-step e.
N => The optical module on the transmission port is not supported. Go to sub-step d.
d. Select the optical module that is supported by the BBU.
e. Replace the optical module.
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 optical port of the peer transmission device.
a. Contact the maintenance engineers responsible for the peer transmission device to
troubleshoot the faults on the optical port of the peer transmission device.
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 3.
3. Check the optical connections.
a. Check the optical connections between the BBU and the peer transmission device.
Troubleshoot the improper optical connections, such as bent fiber, deformation, or
aging.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Check the length of the optical link between the BBU and the peer transmission device.
If the length is excessive, additional optical trunks are required.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
13/11/2012 9:15
Fault Management
268 de 526
Alarm Impact
Warning
System Actions
None
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the interface board of the BBU connecting to the
lower-level RF units on the M2000:
26200 Board Hardware Fault
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 with recommended actions.
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. Reseat the optical module on site.
a. Reseat the faulty optical module on site.
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 3.
3. Replace the optical module on site.
a. Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
269 de 526
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Alarm Impact
Major
System Actions
In ring topology, the active link of lower-level RF units is switched over to the standby link.
Possible Causes
A redundant RRU chain/ring is configured.
The optical module on the port of the BBU connecting to the lower-level RF units is not in position, or
the cable connection on the optical module or electrical port is not ready.
The optical module on the port of the BBU connecting to the lower-level RF units is faulty, or the
cable connected to the optical module or electrical port is faulty.
The connecting piece on the port of the BBU is faulty.
Procedure
1. Check for the redundant RRU chain/ring on the M2000.
a. Run the MML command LST RRUCHAIN to query the link networking of the faulty port.
Check whether the redundant RRU chain/ring is configured according to the site plan.
Y => The redundant RRU chain/ring is configured. Go to sub-step b.
N => There is no redundant RRU chain/ring. Go to step 2.
b. Run the MML command RMV RRUCHAIN to remove the redundant RRU chain/ring .
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the installation of the optical module, or check the cable connection on the CPRI optical
module or electrical port of the BBU on site.
13/11/2012 9:15
Fault Management
270 de 526
a. Check whether the optical module is installed, or whether the cable is connected to the
CPRI optical module or electrical port of the BBU on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the CPRI optical/electrical port.
c. Remove the optical module or the cable connected to the CPRI optical/electrical port,
and then reinstall it securely.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. In the case that the CPRI optical port is used, replace the optical module.
In the case that the CPRI electrical port is used, replace the cable connected to the
CPRI electrical port.
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 3.
3. Reseat the interface board where the faulty port is located on site.
a. Reseat the board.
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 4.
4. Replace the interface board where the faulty port is located on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
271 de 526
Port No.
Board Type
Specific Problem Specific Problem of the alarm(Receive No Signal, Receive Power Too High, Receive Power
Too Low)
Alarm Impact
Major
Minor
When the performance of the optical module of the BBU and the lower-level RF unit
deteriorates to some extent, the quality of services carried on the lower-level RF
units may decrease to some extent.
System Actions
In ring topology, the lower-level RF units automatically switch to the normal CPRI link.
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is faulty or not
installed securely, or the cable connection on the optical module is not ready.
The optical connector on the port of the BBU connecting to the lower-level RF units is dirty.
The optical module on the port of the BBU does not match that of the lower-level RF unit, in terms of
type (single-mode or multi-mode) and rate.
The optical module on the port of the lower-level RF unit is not supported by the lower-level RF unit,
in terms of type (single-mode or multi-mode) and rate.
The optical module on the port of the BBU connecting to the lower-level RF units does not match the
connected optical fiber, in terms of type (single-mode or multi-mode) and rate.
The interface board in the BBU connecting to the lower-level RF units is faulty.
The lower-level RF unit is not powered on.
The optical module or connector of the lower-level RF unit is improperly installed or the optical
module is faulty.
The optical connector of the lower-level RF unit is dirty.
The optical module on the port of the lower-level RF unit does not match the connected optical fiber,
in terms of type (single-mode or multi-mode) and rate.
The optical link between the BBU and the lower-level RF unit is faulty.
The lower-level RF unit is faulty.
13/11/2012 9:15
Fault Management
272 de 526
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the faulty port of the BBU on the M2000:
26230 BBU CPRI Optical Module Fault
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26233 BBU CPRI Optical Interface Performance Degraded
26506 RF Unit Optical Interface Performance Degraded
26540 RF Unit AC Input Power Failure
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 with recommended actions.
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. Locate the alarm cause on the M2000.
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "Receive No Signal" or "Receive Power Too Low", go to step 3.
If "Specific Problem" is "Receive Power Too High", go to step 9.
3. Check the port of the BBU connecting to the lower-level RF units on site.
a. Reseat the optical module and connector on the faulty port of the BBU on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol or a clean cigarette filter. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module at one end of the link matches the optical module at
the other end, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s, 2.5
Gbit/s or other rate). Note that single-mode optical modules are labeled "1310nm",
while multi-mode ones are labeled "850nm".
Y => The optical module at one end of the CPRI link matches the optical module at the
other end. Go to sub-step e.
N => The optical module at one end of the CPRI link does not match the optical module
at the other end. Go to sub-step d.
d. On the basis of the optical module at one end of the link, select the optical module at
the other end.
Replace the optical module.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
273 de 526
13/11/2012 9:15
Fault Management
274 de 526
13/11/2012 9:15
Fault Management
275 de 526
N => The alarm is not cleared. Reinstall the original board. Then, go to step 9.
8. Check the optical connections on site.
a. Check the optical connections between the BBU and the lower-level RF unit.
Troubleshoot the improper optical connections, such as bent fiber or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the optical fiber.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
9. Check the optical modules at both ends of the link and the optical fiber on site.
a. Check whether the optical module of the BBU matches the optical moduleof the
lower-level RF unit, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s,
2.5 Gbit/s or other rate). Note that single-mode optical modules are labeled "1310nm",
while multi-mode ones are labeled "850nm".
Y => The optical module at one end of the link matches the optical module at the other
end. Go to sub-step c.
N => The optical module at one end of the link does not match the optical module at the
other end. Go to sub-step b.
b. On the basis of the optical module at one end of the CPRI link, select the optical
module at the other end.
Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical fiber matches the optical modules.
Y => The optical fiber matches the optical modules. Contact Huawei Customer Service
Center.
N => The optical fiber does not match the optical modules. Go to sub-step d.
d. Choose the optical fiber that matches the optical modules. Note that multi-mode optical
fibers are orange, while single-mode ones are yellow.
Replace the optical module.
Or
Replace the Optical Fiber.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
276 de 526
This alarm is reported when the performance of the optical module on the port of the BBU connecting to the
lower-level RF units deteriorates.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Specific Problem
Alarm Impact
Major
When the performance of the optical module deteriorates significantly, the quality of
services carried on the link of the RF units may decrease significantly, or the ongoing
services carried on lower-level RF units may even be interrupted. The services of the
peer mode are interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty port provides the aggregation function.
Minor
When the performance of the optical module deteriorates to some extent, the quality
of services carried on the link of the RF units may decrease to some extent.
System Actions
None
Possible Causes
The optical module of the BBU connecting to the lower-level RF units is worn-out.
Procedure
1. Check the port of the BBU connecting to the lower-level RF units on site.
a. Reseat the optical module and connector on the faulty port of the BBU on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
277 de 526
Description
This alarm is reported when the link (at the link layer) between the BBU and the lower-level RF units
malfunctions.
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Specific
Problem
Specific Problem of the alarm(CPRI Interface Initialization Failure, CPRI Interface Transmit
Error, CPRI Interface Reception Error)
Alarm Impact
Major
System Actions
In ring topology, the lower-level RF units automatically switch to the normal link.
Possible Causes
If the optical transmission is used, the optical module or connector of the BBU or lower-level RF unit
may be improperly installed, the optical link is faulty, or the optical module is faulty.
If the electrical transmission is used, the cable connector of the BBU or lower-level RF unit may be
improperly installed, or the cable is faulty.
The BBU or lower-level RF unit is running improperly, or the hardware is faulty.
Data configuration is incorrect if a multi-mode base station reports the alarm. As a result, the timing
loop fails.
In multi-mode configuration, the inter-BBU connections are abnormal or the optical module used for
inter-BBU connection is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
13/11/2012 9:15
Fault Management
278 de 526
a. Check for the correlated alarm on the faulty port of the BBU on the M2000:
26230 BBU CPRI Optical Module Fault
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26232 BBU Optical Module Transmit/Receive Fault
26272 Inter-System RF Unit Parameter Settings Conflict
26238 RRU Network Topology Type and Configuration Mismatch
26314 Inter-BBU Port Failure
26240 BBU Topology and Configuration Mismatch
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 with recommended actions.
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 inter-BBU connections on the M2000.
a. Based on the alarm detailed information, run the MML command LST RRUCHAIN to
query the number of the chain/ring that holds the port.
b. Based on the queried chain/ring number, run the MML command LST RRU/DSP
RRUCHAINPHYTOPO to query the configured working mode of the RF unit. Check
whether the RF unit works in dual-mode configurations and whether the main control
boards of two modes are in different BBU subracks.
Y => The RF unit works in dual-mode configurations and the main control boards of two
modes are in different BBU subracks. Go to sub-step c.
N => The RF unit does not work in dual-mode configurations, or the main control boards
of two modes are in the same BBU subrack. Go to step 3.
c. Run the MML command LST SOFTWARE to query the software versions of two
modes. Based on the queried software versions, check whether both the two modes
support inter-BBU connection.
Y => Both the two modes support inter-BBU connection. Go to sub-step e.
N => Either of the two modes does not support inter-BBU connection. Go to sub-step d.
d. Upgrade the software of the mode that does not support inter-BBU connection by
referring to the relevant upgrade guide. Ensure that both the two modes support
inter-BBU connection.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Check for the correlated alarm on the faulty port of the BBU on the M2000: 26314
Inter-BBU Port Failure
26240 BBU Topology and Configuration Mismatch
Y => The correlated alarm exists. Go to sub-step f.
N => The correlated alarm does not exist. Go to step 3.
f. Clear the correlated alarm with recommended actions.
13/11/2012 9:15
Fault Management
279 de 526
13/11/2012 9:15
Fault Management
280 de 526
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
281 de 526
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
The RF unit automatically resets 10 minutes after the maintenance link is broken.
Possible Causes
The fiber optic cable or electrical cable between the BBU and the RF unit or between upper- and
lower-level RF units is faulty.
The optical module inside the BBU or RF unit is faulty.
The RF unit experiences an AC power failure, is not powered on, or is running improperly.
The hardware of the RF unit or BBU is faulty.
The RF unit is automatically reset due to a fault, or the RF unit is manually reset.
When the dual-mode CPRI MUX topology is adopted, the optical module of the baseband board
working in the mode that aggregates data is faulty.
When the dual-mode CPRI MUX topology is adopted, the backplane link between the baseband
boards working in two modes has insufficient resources, or the backplane link is faulty.
When the dual-mode CPRI MUX topology is adopted, the baseband board working in the mode that
aggregates data has hardware faults, is not installed, is not powered on, or is not configured.
When the dual-mode CPRI MUX topology is adopted, the hardware of the baseband board working
in either side does not support backplane aggregation.
Procedure
1. Check the topology of the faulty RF unit on the M2000. (For details about the CPRI MUX topology,
see the 3900 Series Base Station Technical Description.)
a. Based on the alarm detailed information, run the LST RRUCHAIN command to check
whether Access Type of the RRU chain/ring is set to PEERPORT(peer port).
Y => Access Type of the RRU chain/ring is set to PEERPORT(peer port). Go to
substep b.
N => Access Type of the RRU chain/ring is set to LOCALPORT(local port). Go to step
2.
b. Check whether this alarm is also reported in the mode that aggregates data on the
M2000.
Y => This alarm is reported in the mode that aggregates data. Clear the alarm in the
mode that aggregates data. Go to step 2.
N => This alarm is not reported in the mode that aggregates data. Go to step 3.
13/11/2012 9:15
Fault Management
282 de 526
13/11/2012 9:15
Fault Management
283 de 526
b. Run the ADD BRD command to add a baseband board to the mode that aggregates
data.
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 5.
5. Check the capability of the baseband boards working in both modes on the M2000.
a. Run the DSP BRDMFRINFO to query the types of the baseband boards. Check
whether the baseband boards in both sides support the CPRI MUX topology according
to the DBS3900 Hardware Description.
Y => The baseband boards support the CPRI MUX topology. Go to step 6.
N => The baseband boards do not support the CPRI MUX topology. Go to substep b.
b. Replace the baseband board with a board that supports the CPRI MUX topology.
Replace the Board.
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 6.
6. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
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 7.
7. Check the running status of the RF unit on site.
a. Check whether the RUN LED on the RF unit blinks (ON for 1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). Go to step 8.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). Go to sub-step b.
b. Power cycle the RF unit. Wait until the RUN LED blinks (ON for 1s and OFF for 1s).
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 8.
8. Replace the RF unit on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
13/11/2012 9:15
Fault Management
284 de 526
This alarm is reported when the actual RRU cascading levels mismatch the configuration.
Parameters
Parameter Name
Parameter Description
Alarm Impact
Major
When the actual RRU cascading levels mismatch the configuration, the RRUs that
are not configured cannot carry services.
System Actions
None
Possible Causes
The maintenance link for a cascaded RRU fails, or a cascaded RRU is powered off or not installed.
The RRU chain/ring configuration is incorrect.
In actual networking, the RRU cascading levels are incorrect.
Procedure
1. Check the RRU chain/ring configuration on the M2000.
a. Based on the alarm detailed information, check whether the RRU cascading levels in the
chain/ring configuration are consistent with the site plan.
Y => The RRU cascading levels are consistent with the site plan. Go to step 2.
N => The RRU cascading levels are inconsistent with the site plan. Go to sub-step b.
b. Add the RRU in the chain/ring according to the site plan.
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 actual RRU networking on site.
a. Check whether the actual RRU cascading levels are consistent with the RRU cascading
levels in the site plan.
Y => The actual RRU cascading levels are consistent with the site plan. Contact Huawei
Customer Service Center.
N => The actual RRU cascading levels are inconsistent with the site plan. Go to
sub-step b.
b. Remove the RRU according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
285 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Alarm Impact
Major
In chain topology, the RRUs lower than the breakpoint cannot carry services. The
services carried on the lower-level RRUs in the peer mode are interrupted when the
following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The port that carries the faulty chain provides the aggregation function.
In ring topology, the RRUs between two breakpoints cannot carry services. In this
case, the reliability of the RRU link decreases.
System Actions
None
Possible Causes
A breakpoint is set in the RRU chain/ring.
Procedure
1. Cancel the breakpoint in the RRU chain/ring on the M2000.
a. Consult the customer about the reason for the breakpoint in the RRU chain/ring. Check
whether it is allowed to cancel the breakpoint in the RRU chain/ring.
Y => It is allowed to cancel the breakpoint. Go to sub-step b.
N => It is not allowed to cancel the breakpoint. No further action is required.
b. Run the MML command MOD RRUCHAIN to cancel the breakpoint in the RRU
chain/ring.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
286 de 526
chain/ring topology.
Parameters
Parameter Name
Parameter Description
Inconsistency Type
Alarm Impact
Major
If the chain topology is configured but the ring topology is actually used, the reliability
of the RRU link decreases.
If the ring topology is configured but the chain topology is actually used, the RRU link
is not affected.
System Actions
None
Possible Causes
The user configures the RRU chain topology, but the RRU ring topology is actually used.
The user configures the RRU ring topology, but the RRU chain topology is actually used.
The topology configuration is consistent with the actual network (both are the ring topology), but
there is one (only one) configured port which is inconsistent with the actually used port.
In the dual-star topology, more than one RRU is connected to the RRU chain.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board on the M2000:
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26232 BBU Optical Module Transmit/Receive Fault
26501 RF Unit Optical Module or Electrical Port Not Ready
26503 RF Unit Optical Module Transmit/Receive Fault
26272 Inter-System RF Unit Parameter Settings Conflict
26274 Inter-System Board Object Configuration Conflict
13/11/2012 9:15
Fault Management
287 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
288 de 526
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
Data configuration is incorrect.
The optical inter-BBU connections are incorrect.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the inter-BBU interface of the UCIU on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
Y => The correlated alarm exists. Go to substep b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm with recommended actions.
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 data configuration on the M2000.
a. Run the MML command LST CTRLLNK to query the UCIU topology configuration in the
local mode. Check whether the UCIU topology configuration is correct based on the
configuration plan. Alternatively, run the MML command LST BBPLNK to query the
configuration for the WBBPf+WBBPf interconnection topology. Check whether the
13/11/2012 9:15
Fault Management
289 de 526
Parameters
None.
Alarm Impact
Major
The updated data configuration fails to be saved in the configuration file. After the NE
resets, the updated data configuration is lost.
System Actions
None
Possible Causes
The flash or file system error occurs.
Procedure
1. Reset the main control board on the M2000.
a. Note: Resetting the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
13/11/2012 9:15
Fault Management
290 de 526
Run the MML command RST BRD to reset the main control board. Wait until the board
startup is complete.
b. Run the configuration command again. Check whether the alarm is reported again.
Y => The alarm persists. Go to step 2.
N => The alarm is cleared. No further action is required.
2. Replace the main control board on site.
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.
b. Run the configuration command again. Check whether the alarm is reported again.
Y => The alarm persists. Contact Huawei Customer Service Center.
N => The alarm is cleared. No further action is required.
Parameters
None.
Alarm Impact
Major
When the configuration file is invalid, part of or all the data configuration of the
system is lost. In this case, the NE may fail to carry services.
System Actions
None
Possible Causes
The main control board is reset improperly or is powered off. In this case, the flash or file system
error occurs, and the configuration file is damaged.
The current configuration file does not match the software version.
Procedure
1. Obtain the backup configuration file for data recovery on the M2000.
a. Obtain the correct configuration file from the OMC.
b. Run the MML command DLD CFGFILE to download the configuration file to the NE.
c. Run the MML command SET CFGFILEENB to enable the configuration file to take
effect immediately.
13/11/2012 9:15
Fault Management
291 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Major
The system cannot work with the latest data that is configured by the user.
System Actions
None
Possible Causes
The software is running improperly.
Procedure
1. Reset the faulty board on the M2000.
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is reported again.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Reset the main control board on the M2000.
a. 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.
Check whether the alarm is reported again.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
292 de 526
A base station has two storage spaces, which are active workspace and standby workspace. The active
workspace stores the running software version and the standby workspace stores the earlier software version.
This alarm is reported when the software version in the active workspace is incomplete, unrecognizable, or
empty in the case of the NE startup.
Parameters
None.
Alarm Impact
Major
The NE cannot perform the software version check for boards and the board
software cannot be activated. If the board software mismatches the main control
software of the NE, the board cannot obtain the correct software version from the
active workspace. In this case, the board cannot carry services.
System Actions
None
Possible Causes
The memory for storing software in the active workspace is faulty.
Procedure
1. Check the software version in the standby workspace on the M2000.
a. Run the MML command LST SOFTWARE to check whether the software version in the
standby workspace is usable.
Y => The software version in the standby workspace is usable and is the currently
expected version. Go to sub-step b.
N => The software version in the standby workspace is unusable or is not the expected
version. Go to step 2.
b. Run the MML command ACT SOFTWARE to activate the NE software in the standby
workspace. Wait until the NE startup is complete.
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. Download and activate the NE software on the M2000.
a. Run the MML command DLD SOFTWARE to download the software package of the
same version as that in the site plan.
b. Run the MML command ACT SOFTWARE to activate the software package.
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 3.
3. Replace the main control board on site.
a. Note: Replacing the main control board interrupts all the ongoing services of the base
13/11/2012 9:15
Fault Management
293 de 526
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original main control board. Contact Huawei
Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Major
Services cannot be carried on the board. 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.
System Actions
The system automatically disables the board and isolates the board from all other boards.
Possible Causes
An incorrect board is configured.
An incorrect board is installed in the slot.
Procedure
1. Check the board configuration on the M2000.
a. Run the MML command DSP BRD to check whether the type of the configured board
or RF unit in the slot is consistent with the configuration plan.
Y => The type of the configured board or RF unit is consistent with the configuration
plan. Go to step 2.
13/11/2012 9:15
Fault Management
294 de 526
N => The type of the configured board or RF unit is inconsistent with the configuration
plan. Go to sub-step b.
b. Check whether the hardware type of the faulty board is a RF unit according to the
alarm detailed information on the M2000.
Y => The hardware type of the faulty board is a RF unit. Go to sub-step e.
N => The hardware type of the faulty board is not a RF unit. Go to sub-step c.
c. Run the MML command RMV BRD to remove the configured board in the slot.
d. Run the MML command ADD BRD to configure the correct board in the slot according
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.
e. Run the MML command RMV RRU to remove the configured RF unit in the slot.
f. Run the MML command ADD RRU to configure the correct RF unit in the slot according
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 configured sub-board type on the M2000.
a. Based on the alarm detailed information, check whether the board type is the UTRP.
Y => The board type is the UTRP. Go to sub-step b.
N => The board type is not the UTRP. Go to step 3.
b. Run the MML command DSP BRD to query the sub-board type. Check whether the
configured sub-board is consistent with the installed sub-board.
Y => The configured sub-board is consistent with the installed sub-board. Go to step 3.
N => The configured sub-board is inconsistent with the installed sub-board. Go to
sub-step c.
c. Run the MML command ADD BRD to change the sub-board type according to the
installed sub-board type.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Replace the board on site.
a. Based on the configured board type, replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
295 de 526
unavailable in the active workspace and the software auto-supply from the M2000 fails.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The board type has never been configured earlier or the file system of the base station is damaged,
and the communication between the NE and the M2000 fails.
The software to be supplemented is unavailable on the M2000.
Procedure
1. Check the maintenance link for the NE on the M2000.
a. Check for the correlated alarm on the M2000:
301 NE Is Disconnected
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 with recommended actions.
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. Manually start the software auto-supply for the NE on the M2000.
a. Check whether the software to be supplemented is available on the M2000.
Y => The software to be supplemented is available on the M2000. Go to sub-step b.
N => The software to be supplemented is unavailable on the M2000. Store the software
to be supplemented on the M2000 and then go to sub-step b.
b. Run the MML command SPL SOFTWARE to start the software auto-supply for the NE.
Wait until the process is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
296 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Possible
Cause
Possible cause of the activation failure (Board BootROM Incompatible with Software Version
to be Activated, Board Flash Available Space Insufficient, Other Internal Errors)
Alarm Impact
Major
System Actions
None
Possible Causes
The board software upgrade fails during the NE software upgrade. In this case, the board BootROM
upgrade fails.
The available flash memory of the board is insufficient.
The board hardware 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 "Board BootROM Incompatible with Software Version to be
Activated", go to step 2.
If "Specific Problem" is "Board Flash Available Space Insufficient", go to step 4.
If "Specific Problem" is "Other Internal Errors", go to step 3.
2. Upgrade the board BootROM version manually on the M2000.
a. Run the MML command DLD SOFTWARE to manually download the board BootROM
version. Select "BootROM" in the software type field.
b. Run the MML command ACT SOFTWARE to manually activate the board BootROM
version. Select "BootROM" in the software type field.
13/11/2012 9:15
Fault Management
297 de 526
c. Run the MML command RST BRD to reset the board. Wait until the board startup is
complete.
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 3.
3. Activate the board software on the M2000.
a. Run the MML command ACT SOFTWARE to activate the board software. Select
"Software" in the software type field. Wait until the board startup is complete.
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 4.
4. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
None.
Alarm Impact
Major
Version rollback leads to NE reset. During the reset, the ongoing services carried on
the NE are disrupted.
System Actions
None
Possible Causes
The target software version is incorrect.
The target software version does not support a smooth upgrade.
The OM link is abnormal after the upgrade.
Procedure
1. Check the target software version.
13/11/2012 9:15
Fault Management
298 de 526
Parameters
None.
Alarm Impact
Major
The quality of services of the base station decreases, resulting in handover failure
and call drop. In certain cases, the base station cannot provide services.
System Actions
None
13/11/2012 9:15
Fault Management
299 de 526
Possible Causes
The clock reference is not configured.
The clock reference malfunctions.
The board hardware malfunctions.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the site on the M2000:
26261 External Clock Reference Not Configured
26262 External Clock Reference Problem
26200 Board Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Contact Huawei Customer Service Center.
b. Clear the correlated alarm with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
None.
Alarm Impact
Minor
The system clock may be unusable if the base station does not obtain the clock
reference for a long period of time. As a result, the quality of services of the base
station decreases, resulting in handover failure and call drop. In certain cases, the
base station cannot provide services.
System Actions
None
Possible Causes
The external clock reference is not configured for the base station.
Procedure
1. Add the external clock reference for the base station on the M2000.
a. Run the MML command ADD GPS/ADD IPCLKLINK/ADD SYNCETH/ADD
LINECLK/ADD BITS/ADD PEERCLK to add the external clock reference for the base
13/11/2012 9:15
Fault Management
300 de 526
Parameters
Parameter
Name
Specific
Problem
Parameter Description
Specific Problem of the alarm(Clock Reference Lost, Clock Reference Unavailable, Excessive
Frequency Difference Between Clock Reference and Local Crystal Oscillator, Excessive
Frequency Variation of Clock Reference, Excessive Phase Difference Between Clock Reference
and Local Crystal Oscillator, Inconsistent Clock References, IPCLK Reference Unavailable due
to Unacceptable Quality, SYNCETH Clock Reference Unavailable due to Unacceptable Quality,
GPS Clock Reference Unavailable due to Unacceptable Quality, TOD Clock Reference
Unavailable due to Unacceptable Quality)
Alarm Impact
Minor
The base station fails to synchronize to the clock reference. The system clock may
be unusable if the base station does not obtain the clock reference for a long period
of time. As a result, the quality of services of the base station decreases, resulting in
handover failure and call drop. In certain cases, the base station cannot provide
services.
System Actions
None
Possible Causes
If the clock reference is GPS clock, the GPS antenna may be faulty or the number of locked GPS
satellites may be insufficient.
The clock reference is incorrectly configured.
If the clock reference is IPCLK, the IP clock link may fail.
If the clock reference is line clock, the transmission link between the base station and the clock
reference may fail, or the frequency deviation between the clock reference and the local clock may
be excessively large.
The hardware of the UTRP, USCU, or main control board is faulty.
The clock reference is unavailable due to unacceptable quality.
The frequency of the clock reference is unstable.
13/11/2012 9:15
Fault Management
301 de 526
Procedure
1. Check for this alarm on the M2000.
a. Check whether this alarm is reported on a large number of base stations on the M2000.
Y => This alarm is reported on a large number of base stations due to poor
transmission quality or faulty clock source. Go to sub-step b.
N => This alarm is reported only on a few base stations. Go to step 2.
b. Obtain the clock topology, and check the clock transmission link, clock configuration, or
clock source as indicated by the possible alarm cause.
Wait 5 to 120 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2
2. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty clock board or port on the M2000.
26121 GPS Antenna Fault
26122 GPS Locked Satellites Insufficient
26120 GPS Clock Output Unavailable
26123 GPS Maintenance Link Failure
26263 IP Clock Link Failure
25800 E1/T1 Loss of Signal
25880 Ethernet Link Fault
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault
25885 IP Address Conflict
26200 Board Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 3.
b. Clear the correlated alarm with recommended actions.
Wait for 5 to 120 minutes. 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 3.
3. Check the clock reference on the basis of configuration plan on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference is
consistent with the configuration plan.
Y => The clock reference is consistent with the configuration plan. Go to step 4.
N => The clock reference is inconsistent with the configuration plan. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference according to
the configuration plan.
Wait for 5 to 120 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
302 de 526
Parameters
Parameter Name
Parameter Description
Link No.
Alarm Impact
13/11/2012 9:15
Fault Management
303 de 526
Alarm Severity
Alarm Impact
Minor
The base station fails to synchronize to the IP clock reference. The system clock
may be unusable if the base station does not obtain the clock reference for a long
period of time. As a result, the quality of services of the base station decreases,
resulting in handover failure and call drop. In certain cases, the base station cannot
provide services.
System Actions
None
Possible Causes
The port used for the IP clock link is faulty.
The IPCLK link is incorrectly configured.
The route from the NE to the clock server is not configured.
The route from the NE to the clock server is not reachable.
The main control board hardware is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the port that bears the IPCLK link on the M2000.
26220 Transmission Optical Module Fault
26221 Transmission Optical Module Not In Position
26222 Transmission Optical Interface Error
26223 Transmission Optical Interface Performance Degraded
25880 Ethernet Link Fault
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault
25885 IP Address Conflict
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 with recommended actions.
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 IPCLK configuration on the M2000.
a. Run the MML command LST IPCLKLINK to check whether the IP address of the clock
server and the IPCLK type are consistent with the network plan.
Y => The IP address of the clock server and the IPCLK type are consistent with the
network plan. Go to step 3.
N => The IP address of the clock server and the IPCLK type are inconsistent with the
network plan. Go to sub-step b.
13/11/2012 9:15
Fault Management
304 de 526
b. Run the MML command RMV IPCLKLINK/ADD IPCLKLINK to change the configuration
of IPCLK link.
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 3.
3. Check the configuration of route from the NE to the clock server on the M2000.
a. Run the MML command LST IPRT to query all the current routes. Check whether an IP
route connecting the peer clock server exists.
Y => There is an IP route connecting the peer clock server. Go to step 4.
N => There is no IP route connecting the peer clock server. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route connecting the peer clock server.
Then, wait for at least five minutes.
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 4.
4. Check the reachability of route from the NE to the clock server on the M2000.
a. Run the MML command PING to check whether the route from the NE to the clock
server is reachable.
Y => The route is reachable. Go to sub-step d.
N => The route is not reachable. Go to sub-step b.
b. Contact the maintenance engineer responsible for the clock server to rectify the fault on
the clock server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Contact the maintenance engineer responsible for the routing device to rectify the route
fault.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. Contact the maintenance engineer responsible for the clock server to troubleshoot the
improper processes of the clock server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
305 de 526
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Specific
Problem
Specific Problem of the alarm(Software Phase Lock Loop Loss of Lock, Hardware Phase
Lock Loop Loss of Lock)
Alarm Impact
Minor
The system clock fails after a certain period (around 90 days). The ongoing services
carried on the board are disrupted.
Major
The system clock fails. The ongoing services carried on the board are disrupted.
System Actions
None
Possible Causes
The clock reference malfunctions.
The clock reference is not configured.
The main control board hardware is faulty.
If this alarm is reported on a non-main control board, the board may not be securely installed.
The board hardware is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the site on the M2000:
26261 External Clock Reference Not Configured
26262 External Clock Reference Problem
26200 Board Hardware Fault
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 with recommended actions.
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. Reset the faulty board through power-off on the M2000.
a. Reset the board through power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
306 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Major
System Actions
None
Possible Causes
The system clock phase-locked loop in the main control board is unlocked.
This board is not securely installed.
The board hardware is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board or main control board on the M2000:
26264 System Clock Unlocked
26200 Board Hardware Fault
13/11/2012 9:15
Fault Management
307 de 526
Parameters
Parameter Name
Parameter Description
Alarm Impact
Minor
The time of the base station fails to synchronize with the time of the M2000. As a
result, the time the base station reports alarms and logs is different from the time of
the M2000 and therefore inventory information on the M2000 cannot be automatically
updated, possibly leading to unreliable traffic statistics.
System Actions
None
13/11/2012 9:15
Fault Management
308 de 526
Possible Causes
The transmission port connected to the SNTP/NTP server is faulty.
The time reference is incorrectly configured.
The parameter settings on the SNTP/NTP client are incorrect.
The route from the NE to the SNTP/NTP server is not configured or is not reachable.
The SNTP/NTP server is not in service.
The GPS antenna is faulty.
The number of locked GPS satellites is insufficient.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the port used for time synchronization on the M2000.
25880 Ethernet Link Fault
26121 GPS Antenna Fault
26122 GPS Locked Satellites Insufficient
26120 GPS Clock Output Unavailable
26123 GPS Maintenance Link Failure
25800 E1/T1 Loss of Signal
25806 E1/T1 Excessive Bit Error Rate
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault
25885 IP Address Conflict
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 with recommended actions.
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 configuration of time reference on the basis of the configuration plan on the M2000.
a. Run the MML command LST TIMESRC to check whether the configuration of time
reference is consistent with the configuration plan.
Y => The configuration of time reference is consistent with the configuration plan. Go to
step 3.
N => The configuration of time reference is inconsistent with the configuration plan. Go
to sub-step b.
b. Run the MML command SET TIMESRC to change the configuration of time reference.
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 3.
13/11/2012 9:15
Fault Management
309 de 526
13/11/2012 9:15
Fault Management
310 de 526
Parameters
Parameter
Name
Peer Mode
Parameter Description
Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Alarm Impact
Major
System Actions
None
Possible Causes
The base station in the other mode is repeatedly reset because the connection between the base
station and the base station controller or M2000 is disrupted for a long time.
The base station in the other mode is repeatedly reset because the base station is installed but not
configured.
The base station in the other mode is reset after a software upgrade or after a reset command is
issued.
The main control board of the other mode is running improperly.
The main control board of the current mode is running improperly.
The main control board of the other mode is not installed securely.
The main control board of the current mode is not installed securely.
The hardware of the main control board of the other mode is faulty.
The hardware of the main control board of the current mode is faulty.
13/11/2012 9:15
Fault Management
311 de 526
In multi-mode configuration, the inter-BBU connections are abnormal or the optical module used for
inter-BBU connection is faulty.
Procedure
1. Check for the correlated alarms on the M2000.
a. Check whether any of the following alarms on the faulty port of the BBU on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
26315 Inter-BBU Port Connection Error
26240 BBU Topology and Configuration Mismatch
Y => A correlated alarm is reported. Go to sub-step b.
N => A correlated alarm is not reported. Go to step 2.
b. Clear the correlated alarm with recommended actions.
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 status of the main control board in the other mode on the M2000.
a. Click Device Panel on the M2000, and check whether the status of the main control
board in the other mode is normal.
Y => The status of the main control board in the other mode is normal. Go to step 3.
N => The status of the main control board in the other mode is abnormal. Go to
sub-step b.
b. Wait 5 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Reset the main control board of the current mode on the M2000.
a. 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 of the current mode.
Wait until the board startup is complete.
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 4.
4. Reset the main control board of the other mode on the M2000.
a. 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 of the other mode.
Wait until the board startup is complete.
13/11/2012 9:15
Fault Management
312 de 526
13/11/2012 9:15
Fault Management
313 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Warning
The parameter settings of a monitoring device in a mode are incorrect. In this case,
the related data configuration may not take effect in this mode, and alarms may be
falsely reported.
System Actions
None
Possible Causes
The parameter settings of a monitoring device in a mode are incorrect.
Procedure
1. Check the parameter settings of the monitoring device in two modes on the Configuration
Management Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty monitoring device.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the monitoring device in two modes according to the configuration
plan. Ensure the parameter consistency in two modes.
13/11/2012 9:15
Fault Management
314 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Configuration
Item
Configuration item (IF Offset, TX Gain, AGC Flag, DPD Flag, PAR Flag, CPRI Port
Configuration, SEM Enabling Flag, Receive Desensitivity, RTWP Correction Value, RF
Desensitivity, Delay Compensation, T1/L Timing Delay Compensation, VSWR Alarm Threshold,
Attenuation, ALD Current Threshold, VSWR Threshold, External Boolean Alarm Port, Alarm
Parameters, Radio Interconnection Mode, Topology Type, RF Unit Working Mode Conflict)
Board Type
Peer Mode
Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Alarm Impact
Major
If the configured working mode of an RF unit in one mode is inconsistent with that of
the same RF unit in the other mode, the software management of the RF unit is
affected. In this case, the ongoing services carried on the RF unit may be affected.
If other parameters of an RF unit in one mode are inconsistent with those of the
same RF unit in the other mode, the data configuration of the RF unit in one mode
cannot take effect. In this case, problems may occur.
Warning
If other parameters of an RF unit in one mode are inconsistent with those of the
same RF unit in the other mode, the data configuration of the RF unit in one mode
cannot take effect. In this case, problems may occur.
System Actions
If the configured working mode of an RF unit in one mode is inconsistent with that of the same RF unit in the
other mode, the system does not load the board software of the RF unit.
Possible Causes
The working mode of an RF unit is incorrectly configured in one mode.
The parameters of an RF unit in one mode are inconsistent with those of the same RF unit in the
13/11/2012 9:15
Fault Management
315 de 526
other mode.
Procedure
1. Check for inconsistent settings of RF unit parameters on the M2000.
a. Check the value of the "Configuration Item" parameter in the alarm information.
If the value of "Configuration Item" is "Radio Interconnection Mode", go to substep b.
If the value of "Configuration Item" is not "Radio Interconnection Mode", go to step 2.
b. Run the LST BTSRXUBP command on the GSM side to query the TX/RX mode of the
faulty RF unit. If the TX/RX mode is "Single Feeder(1TX + 2RX)", the RF unit is
interconnected with another RF unit.
Run the LST SEC command on the UMTS side to query the interconnection mode of the
faulty RF unit. If the value of "RF Interconnection Mode" is "TRUE", the RF unit is
interconnected with another RF unit.
c. Check whether the settings of the RF unit interconnection mode are consistent between
the GSM and UMTS sides.
Y => The settings are consistent. Contact Huawei Customer Service Center.
N => The settings are inconsistent. Go to substep d.
d. Run the SET BTSRXUBP command on the GSM side to change the TX/RX mode of the
faulty RF unit to the value specified in the configuration plan.
Run the RMV SEC and ADD SEC commands on the UMTS side to change the
interconnection mode of the faulty RF unit to the value specified in the configuration
plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the parameter settings of the RF unit in two modes on the Configuration Management
Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty RF unit.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the RF unit in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
316 de 526
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Configuration
Item
Configuration item (Dry Contact Alarm Level Conflict, GPS Parameters Conflict,
Convergency topology Conflict)
Board Type
Alarm Impact
Warning
If the configuration of dry contacts for the UPEU/UEIU in two modes is inconsistent,
alarms are falsely reported on the mode with wrong configuration.
If the GPS configuration for the USCU in two modes is inconsistent, the data
configuration on one mode cannot take effect.
Major
System Actions
None
Possible Causes
The configuration of dry contacts for the UPEU/UEIU in a mode is inconsistent with that in the other
mode.
The GPS configuration for the USCU in a mode is inconsistent with that in the other mode.
The networking configuration of the RF units is inconsistent between the two modes.
Procedure
1. Check the parameter settings of the board in two modes on the Configuration Management Express
(CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty board.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the board in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
317 de 526
In multi-mode configuration, this alarm is reported when the cabinet/subrack/slot configuration of a board is
inconsistent in different modes, when the cabinet/subrack/slot configuration of different boards is the same in
different modes, or when a board supporting only a certain mode is configured for different modes.
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Peer Mode
Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Board Type
Peer Cabinet Cabinet number of the faulty board in the peer working mode
No.
Peer Subrack Subrack number of the faulty board in the peer working mode
No.
Peer Slot No. Slot number of the faulty board in the peer working mode
Specific
Problem
Alarm Impact
Major
The board with configuration conflict cannot be maintained in the way that a common
board is handled. In this case, the inventory information error occurs. For the RF
units, the automatic software update fails in the case of software upgrades. In this
case, the ongoing services carried on the RF units are disrupted. When a board
supporting only one mode is configured for different modes, the board fails to work
normally.
System Actions
None
Possible Causes
When this alarm is reported on a monitoring board, the possible causes are as follows: Incorrect
cabinet, subrack, or slot number. Incorrect cabinet or subrack number of the device managing the
monitoring device. Incorrect serial port number. Incorrect communication IP address. When this
alarm is reported on other boards, the possible causes are that the cabinet, subrack, or slot number
of the board is incorrect.
A board supporting only a certain mode is configured for different modes.
Procedure
1. Locate the alarm cause on the M2000.
a. Locate the cause of the alarm based on the alarm detailed information.
13/11/2012 9:15
Fault Management
318 de 526
13/11/2012 9:15
Fault Management
319 de 526
a. Run the MML command LST RRU to check whether the cabinet/subrack/slot
configuration of the faulty RRU in the current mode is correct according to the
configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Go to step 7.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
b. Run the MML command RMV RRU to remove the RRU in the current mode.
c. Run the MML command ADD RRU to add the RRU in the current mode. Set the
cabinet/subrack/slot of the board 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 7.
7. Check the RRU configuration in the other mode on the M2000.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty RRU
in the other mode is correct according to the configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Contact Huawei Customer
Service Center.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
b. Remove the RRU in the other mode on the M2000.
c. Add the RRU in the other mode on the M2000. Set the cabinet/subrack/slot of the
board according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
8. Check the monitoring device configuration in the current mode on the M2000.
a. Run the MML command LST PMU(PMU)/LST TCU(TCU)/LST EMU(EMU)/LST
FMU(FMU) to check whether the cabinet/subrack/slot configuration of the faulty
monitoring device in the current mode is correct according to the configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Go to step 9.
N => The cabinet/subrack/slot configuration is incorrect. 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 monitoring device in the current mode.
c. Run the MML command ADD PMU(PMU)/ADD TCU(TCU)/ADD EMU(EMU)/ADD
FMU(FMU) to add the monitoring device in the current mode. Set the
cabinet/subrack/slot of the board 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 9.
9. Check the monitoring device configuration in the other mode on the M2000.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty
monitoring device in the other mode is correct according to the configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Contact Huawei Customer
Service Center.
13/11/2012 9:15
Fault Management
320 de 526
Parameters
Parameter Name Parameter Description
Cabinet No.
Configuration
Item
Peer Mode
Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Alarm Impact
Minor
The cabinet type in different modes conflicts, which affects the configuration,
maintenance of the cabinet, as well as the inventory information recording.
System Actions
None
Possible Causes
In a multi-mode base station, the cabinet type of one mode is incorrectly configured.
Procedure
1. Check the cabinet configuration in two modes on the Configuration Management Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty cabinet.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the cabinet in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
321 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Name
Parameter Description
Configuration
Item
Peer Mode
Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Alarm Impact
Major
When the clock source type configured for a mode is incorrect, the clock source in
the mode is unavailable. In this case, the system clock works in free-run mode.
Services are not affected during a short period (three months).
When the DID configured for a mode is incorrect, users cannot manage the mode by
DID.
System Actions
None
Possible Causes
The clock reference type of a mode is incorrect.
The DID of a mode is incorrect.
Procedure
1. Check the alarm cause on the M2000.
a. Check the cause of the alarm based on the alarm location information.
If the alarm is caused by a clock reference type configuration conflict, go to step 2.
If the alarm is caused by a DID configuration conflict, go to step 4.
2. Check the clock reference type of the local mode on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference type of
the local mode is correct according to the site plan.
Y => The clock reference type of the local mode is correct. Go to step 2.
N => The clock reference type of the local mode is incorrect. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference type of the
local mode according to the site plan.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
322 de 526
Parameters
Parameter
Name
Parameter Description
13/11/2012 9:15
Fault Management
323 de 526
Peer Mode
Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Alarm Impact
Major
When the loading control rights conflict, the software version of the USCU and the
shared RF units between different modes may be wrong. In this case, some
functions of the multi-mode base station fail and the reliability decreases.
System Actions
None
Possible Causes
The loading control rights are not configured after the multi-mode base station is deployed.
The loading control rights are not configured after the main control board is replaced in the
multi-mode base station.
The loading control rights are inconsistent between the current mode and the other mode.
Procedure
1. Set the loading control rights on the M2000.
a. Note: Before you set the loading control rights, query the software version of the
multi-mode base station and specify the loading control rights by referring to the
upgrade guide. The MML command should be executed in the mode requiring the
loading control rights and with the parameter EFTIMMFLAG set to YES (becoming
effective immediately).
In the mode requiring the loading control rights, run the MML command SET
LOADCTRL to set the loading control rights in the multi-mode base station.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
324 de 526
RF Unit Working
Mode
RF unit working mode (UO, GO, CO, WO, LO, TDLO, TDSO, GU, UL, GL, CL, TL,
WL, GUL, CU)
RF Unit Mode
Capability
RF unit mode capability (UO, GO, CO, WO, LO, TDLO, TDSO, GU, UL, GL, CL, TL,
WL, GUL, CU)
Alarm Impact
Major
System Actions
None
Possible Causes
The working mode of the RF unit is incorrectly configured in the system.
The model of the installed RF unit is incorrect.
Procedure
1. Check the configured working mode of the RF unit on the M2000.
a. Run the MML command LST RRU/DSP RRUCHAINPHYTOPO to check whether the
working mode of the faulty RF unit is correct according to the site plan.
Y => The working mode is correct. Go to step 2.
N => The working mode is incorrect. Go to sub-step b.
b. Run the MML command MOD RRU to change the working mode of the faulty RF unit
according to the site plan.
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. Replace the RF unit on site.
a. Replace the RF unit. Ensure that the actual capability of the new RF unit is consistent
with the configured working mode.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
325 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Minor
The BBU subrack and the boards in the BBU are displayed in disorder on the M2000.
In addition, the inventory information record is in disorder.
System Actions
None
Possible Causes
In a multi-mode base station, the cabinet/subrack number of a main control board of a mode is
incorrectly configured.
In a multi-mode base station, the installed position of a main control board of a mode is incorrect.
Procedure
1. Check the cabinet/subrack number of the BBU of each mode on the M2000.
a. Run the MML command DSP BRD to query the board configuration.
Check whether the cabinet/subrack number of the main control board of each mode is
correctly configured, according to the configuration plan.
Y => The cabinet/subrack number is correct. Go to step 2.
N => The cabinet/subrack number is incorrect. Go to sub-step b.
b. Run the MML command RMV BRD to delete the board that is incorrectly configured.
c. Run the MML command ADD BRD to add the board and set its cabinet/subrack/slot
number according to the configuration plan.
Ensure that the cabinet/subrack number of two main control boards in the same BBU is
the same, and the cabinet/subrack number of a main control board of one mode is
different from that of the other mode in a different BBU.
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 installation of main control board of each mode on site.
a. Check whether the main control board of each mode is installed correctly, according to
the configuration plan.
Y => The main control board of each mode is installed correctly. Contact Huawei
13/11/2012 9:15
Fault Management
326 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Port Description
Alarm Impact
Warning
System Actions
None
Possible Causes
The optical module on an inter-BBU port is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty optical module on the M2000:
26200 Board Hardware Fault
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 with recommended actions.
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.
13/11/2012 9:15
Fault Management
327 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Port Description
Alarm Impact
Major
System Actions
None
Possible Causes
13/11/2012 9:15
Fault Management
328 de 526
The cable for the optical module on an inter-BBU port or for the inter-BBU electrical port is not
installed or not connected securely.
The cable for the optical module on an inter-BBU port or for the inter-BBU electrical port is faulty.
The connecting piece on an inter-BBU port is faulty.
Procedure
1. Check the configurations of inter-BBU ports on the M2000.
a. Run the MML command LST CTRLLNK or LST BBPLNK to query the configurations of
inter-BBU ports. Check whether the configurations are correct according to the onsite
plan.
Y=> The configurations are correct. Go to step 2.
N=> The configurations are incorrect, and extra inter-BBU ports are configured. Go to
step 2.
b. Run the MML command RMV CTRLLNK or RMV BBPLNK to remove the extra
inter-BBU ports.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check cable connections for the optical module or electrical port onsite.
a. Check whether the cable for the optical module or electrical port is installed on the BBU
side.
Y => The cable is installed. Go to substep c.
Y => The cable is not installed. Go to substep b.
b. Install an optical module or install the cable for the electrical port.
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 3.
c. Remove and then insert the optical module or remove and then insert the electrical
cable, and check that the optical module is connected properly.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. If the inter-BBU port is an optical port, Replace the optical module.
If the inter-BBU port is an electrical port, replace the electrical cable.
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 3.
3. Remove and then insert the faulty board onsite.
a. Reseat the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
329 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Port Description
Specific Problem Specific Problem of the alarm(Receive No Signal, Receive Power Too High, Receive Power
Too Low)
Alarm Impact
Major
Minor
If the BBUs are interconnected by UCIU+UCIU/UMPT, the bit error rate (BER) of the
control information, clock information, and transmission information exchanged
between BBUs increases. As a result, the service quality of the lower-level BBU
deteriorates.
If the BBUs are interconnected by WBBPf+WBBPf, the bit error rate (BER) of the
13/11/2012 9:15
Fault Management
330 de 526
Alarm Severity
Alarm Impact
baseband data and signaling exchanged between BBUs increase, affecting service
quality.
System Actions
None
Possible Causes
The optical module on an inter-BBU port is faulty or not installed properly, or the cable connection on
the optical module is not ready.
The optical connector of an inter-BBU port is dirty.
The optical modules on both ends of an inter-BBU port do not match, in terms of type (single-mode
or multi-mode) and rate.
The optical module on an inter-BBU port does not match that supported by the board, in terms of
type (single-mode or multi-mode) and rate.
The optical module on an inter-BBU port does not match the connected fiber optic cable, in terms of
type (single-mode or multi-mode) and rate.
The UCIU is faulty.
The peer board of an inter-BBU port is not powered on.
The peer optical connector of an inter-BBU port or the optical module is not inserted properly, or the
optical module is faulty.
The peer optical connector of an inter-BBU port is dirty.
The optical module on an inter-BBU port does not match the connected fiber optic cable, in terms of
type (single-mode or multi-mode) and rate.
The fiber optic cable between inter-BBU ports is faulty.
The peer board of an inter-BBU port is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the inter-BBU port and the port of the peer board on
the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26313 Inter-BBU Optical Module Transmit Failure
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 with recommended actions.
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 optical module and fiber optic cable of an inter-BBU port onsite.
a. Remove and then insert the optical module and optical connector on the inter-BBU port
13/11/2012 9:15
Fault Management
331 de 526
13/11/2012 9:15
Fault Management
332 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Port Description
13/11/2012 9:15
Fault Management
333 de 526
Specific Problem Specific Problem of the alarm(Optical Module Performance Degraded, Optical Module
Transmit Error)
Alarm Impact
Major
Minor
Services are not affected temporarily. If the problem remains for a long time, the
alarm severity is changed to major.
System Actions
None
Possible Causes
The optical module on an inter-BBU port deteriorates.
Procedure
1. Check the inter-BBU port onsite.
a. Remove and then insert the optical module and optical connector of the inter-BBU port
on the BBU side.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Parameter Description
13/11/2012 9:15
Fault Management
334 de 526
Name
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Port
Description
Specific
Problem
Specific Problem of the alarm(CPRI Interface Initialization Failure, CPRI Interface Transmit
Error, CPRI Interface Reception Error)
Alarm Impact
Major
System Actions
None
Possible Causes
The peer optical connector of an inter-BBU port or the optical module is not inserted properly, or the
fiber optic cable fails to be connected. The electrical cable for the peer inter-BBU port is not securely
connected, or the electrical cable is faulty.
The peer board of an inter-BBU port does not work properly, or the hardware of the board is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty inter-BBU port on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26240 BBU Topology and Configuration Mismatch
26315 Inter-BBU Port Connection Error
13/11/2012 9:15
Fault Management
335 de 526
13/11/2012 9:15
Fault Management
336 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Fault Type
Fault Type (S Port Connected to S Port, M Port Connected to M Port, Ring Topology)
Port Description
Alarm Impact
Major
System Actions
None
Possible Causes
Inter-BBU interfaces of the same type are connected, or a ring network is set up in the case of an inter-BBU
connection.
Procedure
1. Locate the alarm cause on the M2000.
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "M Port Connected to M Port" or "S Port Connected to S Port",
go to step 2.
If "Specific Problem" is "Ring Topology", go to step 3.
2. Check the UCIU for the connection of inter-BBU ports of the same type on site.
a. Based on the alarm parameters, locate the UCIU port and the connected optical fiber.
Check whether the connection of inter-BBU ports of the same type exists on the UCIU
port.
Y => The connection of inter-BBU ports of the same type exists on the UCIU port. Go
to sub-step b.
N => The connection of inter-BBU ports of the same type does not exist on the UCIU
port. Contact Huawei Customer Service Center.
b. Reconnect the inter-BBU optical fibers based on the engineering plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Check the UCIU for a ring topology of inter-BBU connection on site.
13/11/2012 9:15
Fault Management
337 de 526
a. Based on the alarm parameters, locate the UCIU port and the connected optical fiber.
Check whether a ring topology of inter-BBU connection exists on the UCIU port.
Y => A ring topology of inter-BBU connection exists on the UCIU port. Go to sub-step
b.
N => A ring topology of inter-BBU connection does not exist on the UCIU port. Contact
Huawei Customer Service Center.
b. Reconnect the inter-BBU optical fibers based on the engineering plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Alarm Impact
Major
System Actions
In ring topology, the active link of lower-level RF units is switched over to the standby link.
Possible Causes
The networking of RF units is incorrect. Redundant lower-level RF units are configured.
The optical module on the port of the RF unit connecting to the peer device (upper- or lower-level RF
unit or the BBU) is not in position, or the cable connection on the optical module or electrical port is
not ready.
The optical module on the port of the RF unit connecting to the peer device (upper- or lower-level RF
13/11/2012 9:15
Fault Management
338 de 526
unit or the BBU) is faulty, or the cable connected to the optical module or electrical port is faulty.
The connecting piece on the port of the RF unit connecting to the peer device (upper- or lower-level
RF unit or the BBU) is faulty.
Procedure
1. Check for redundant lower-level RF units on the M2000.
a. Run the MML command LST RRUCHAIN to query the link networking of the faulty RF
unit. Check whether a redundant lower-level RF unit is configured according to the site
plan.
Y => A redundant lower-level RF unit is configured. Go to sub-step b.
N => There is no redundant lower-level RF unit. Go to step 2.
b. Run the MML command RMV RRU to remove the redundant lower-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the installation of the optical module, or check the cable connection on the optical module or
electrical port of the RF unit on site.
a. Check whether the optical module is installed, or whether the cable is connected to the
optical module or electrical port on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the optical/electrical port.
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 3.
c. Reseat the optical module or the cable connected to the optical/electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. Replace the optical module, or replace the cable on the electrical port.
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 3.
3. Power cycle the RF unit on site.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s).
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 4.
4. Replace the RF unit on site.
13/11/2012 9:15
Fault Management
339 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Installed Optical Module Type of the installed optical module (1.25Gbps, 2.5Gbps, 3.07Gbps, 4.9Gbps,
Type
6.14Gbps, 9.8Gbps, 3.84Gbps)
Alarm Impact
Major
The port of the RF unit connecting to the peer device (upper- or lower-level RF unit
or the BBU) does not work normally. The services carried on the RF unit are
disrupted.
System Actions
None
Possible Causes
The type of the optical module installed on an RF unit is not supported by the RF unit. For example, an RF unit
supports only an optical module of 2.5 Gbit/s, but an optical module of 1.25 Gbit/s is installed on the RF unit.
Procedure
1. Replace the optical module on site.
a. Replace the optical module of the RF unit on site. Ensure that the installed optical
module is supported by the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
340 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Port Type
Specific Problem
Alarm Impact
Major
System Actions
In ring topology, the current-level RF unit automatically switches to a normal port if its uplink port is faulty.
Possible Causes
The optical module or connector of the current-level RF unit is improperly installed, or the optical
module is faulty.
The optical connector of the current-level RF unit is dirty.
The current-level RF unit is faulty.
The peer device (upper-level/lower-level RF unit) is not powered on.
The optical module or connector of the peer device (upper-level/lower-level RF unit or BBU) is
improperly installed, or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RF unit or BBU) is dirty.
The peer device is faulty.
The optical link between the current-level RF unit and the peer device (upper-level/lower-level RF unit
or BBU) is faulty.
Procedure
13/11/2012 9:15
Fault Management
341 de 526
13/11/2012 9:15
Fault Management
342 de 526
13/11/2012 9:15
Fault Management
343 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Port Type
Specific Problem Specific Problem of the alarm(CPRI Interface Transmit Error, CPRI Interface Reception
Error)
Alarm Impact
Major
13/11/2012 9:15
Fault Management
344 de 526
Alarm Severity
Alarm Impact
ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RF unit automatically switches to a normal port if its uplink port is faulty.
Possible Causes
If the optical transmission is used, the optical module or connector of the RF unit or peer device may
be improperly installed, or the optical link is faulty.
If the electrical transmission is used, the cable connector of the RF unit or peer device may be
improperly installed, or the cable is faulty.
The RF unit or peer device malfunctions, or the hardware is faulty.
In multi-mode configuration, the inter-BBU connections are abnormal or the optical module used for
inter-BBU connection is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the faulty port of the RF unit on the M2000:
26501 RF Unit Optical Module or Electrical Port Not Ready
26503 RF Unit Optical Module Transmit/Receive Fault
26507 RF Unit Optical Module Fault
26502 RF Unit Optical Module Type Mismatch
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
26315 Inter-BBU Port Connection Error
26240 BBU Topology and Configuration Mismatch
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 with recommended actions.
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. Locate the alarm cause on the M2000.
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "CPRI Interface Transmit Error", go to step 3.
If "Specific Problem" is "CPRI Interface Reception Error", go to step 4.
3. Check the optical connections on site.
13/11/2012 9:15
Fault Management
345 de 526
a. Check the optical connections between the BBU and the peer end. Troubleshoot the
improper optical connections, such as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the optical module.
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 4.
4. Check the cable connections on the faulty port of the RF unit on site.
a. Check the cable connections on the optical or electrical port of the current-level RF unit
on site.
If the electrical transmission is used, Go to sub-step b.
If the optical transmission is used, Go to sub-step d.
b. Reseat the cable on the electrical port of the current-level RF unit and the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Replace the cable on the electrical port.
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 5.
d. Remove the connector from the optical module of the current-level RF unit. Clean the
connector by using absolute alcohol or a clean cigarette filter. Then, reinstall the
connector to the optical module of the current-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Check the optical connections between the current-level RF unit and the peer end.
Replace the faulty optical fibers to troubleshoot the improper optical connections, such
as fiber bending, deformation, damage, or loose optical connector/module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step f.
f. Remove the connector from the optical module of the lower-level RF unit. Clean the
connector by using absolute alcohol or a clean cigarette filter. Then, reinstall the
connector to the optical module of the lower-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Replace the optical module of the peer end.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
346 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Specific
Problem
Specific Problem of the alarm(Optical Module Performance Degraded, Reception Power Too
High, Reception Power Too Low)
Alarm Impact
Major
When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the link of the RF unit may decrease significantly, or the
13/11/2012 9:15
Fault Management
347 de 526
Alarm Severity
Alarm Impact
ongoing services carried on the RF unit may even be disrupted.
Minor
When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the link of the RF unit may decrease to some extent.
System Actions
None
Possible Causes
The optical module or connector of the current-level RF unit is improperly installed. Or the optical
module is worn-out.
The optical connector of the current-level RF unit is dirty.
The optical module on the port of the current-level RF unit is not supported by the current-level RF
unit, in terms of type (single-mode or multi-mode) and rate.
The optical module or connector of the peer device (upper-level/lower-level RF unit or BBU) is
improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RF unit or BBU) is dirty.
The optical module on the port of the peer device (upper-level/lower-level RF unit or BBU) is not
supported by the peer device, in terms of type (single-mode or multi-mode) and rate.
The optical fibers between the current-level RF unit and the peer device (upper-level/lower-level RF
unit or BBU) are bent, deformed, or worn-out. Or the length of optical fibers is excessive (longer than
40 km), which leads to a high attenuation of optical signals.
Procedure
1. Check the faulty port of the current-level RF unit on site.
a. Remove and reinstall the optical module and connector on the port of the current-level
RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Examine the label on the optical module to check whether the optical module on the port
is supported by the current-level RF unit, in terms of type (single-mode or multi-mode)
and rate (1.25 Gbit/s, 2.5 Gbit/s or other rate).
Y => The optical module is supported by the RF unit. Go to sub-step e.
N => The optical module is not supported by the RF unit. Go to sub-step d.
d. Select the optical module that is supported by the RF unit.
e. Replace the optical module.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
348 de 526
13/11/2012 9:15
Fault Management
349 de 526
Description
This alarm is reported when the optical module or electrical module on the port of the RF unit connecting to the
peer device (upper- or lower-level RF unit or the BBU) is faulty.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Alarm Impact
Warning
The information about the optical module or electrical module cannot be obtained.
System Actions
None
Possible Causes
The optical module or electrical module of the RF unit is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the RF unit on the M2000:
26532 RF Unit Hardware Fault
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 with recommended actions.
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. Query it's using optical module or electrical module:
a. Run the MML command DSP BTSBRD, and query the RUNPARA of the faulty RF
board, to check using optical module or electrical module.
Optical module, go to step 3;
Electrical module, go to step 5;
3. Reseat the optical module on site.
a. Reseat the faulty optical module on site.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
350 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
TX Channel No.
TX channel number
Board Type
Alarm Impact
Minor
When the gain on the TX channel is extremely high, the downlink coverage of the cell
is excessive. In this case, the interference caused by cross coverage occurs.
When the gain on the TX channel is extremely low, coverage holes exist in the
downlink coverage of the cell. In serious cases, the ongoing services carried on the
13/11/2012 9:15
Fault Management
351 de 526
Alarm Severity
Alarm Impact
RF unit may be disrupted.
System Actions
None
Possible Causes
The hardware of the RF unit is faulty.
Procedure
1. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
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. Replace the RF unit on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
RX Channel No.
RX channel number
Board Type
Alarm Impact
13/11/2012 9:15
Fault Management
352 de 526
Alarm Severity
Alarm Impact
Minor
System Actions
None
Possible Causes
The setting of attenuation of the RF unit is incorrect.
The TMA is faulty.
The feeder installation is improper. For example, the feeder connector is loose, soaked or damaged,
or the feeder is deformed.
The RX channel of the RF unit is faulty. For example, the low-noise amplifier, frequency mixer, analog
to digital converter (ADC), or field programmable gate array (FPGA) is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the faulty port of the RF unit on the M2000:
26532 RF Unit Hardware Fault
26530 RF Unit ALD Current Out of Range
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 with recommended actions.
Wait for 10 minutes after the correlated alarm is cleared.
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 attenuation of the RF unit on the M2000.
a. Calculate the attenuation of the RF unit.
Attenuation of RF unit = TMA gain - feeder loss
Where, feeder loss can be obtained from the acceptance report of the base station.
The installation personnel measure the feeder loss during the base station installation.
b. Run the MML command MOD RXBRANCH to set the attenuation on the main RX
channel and diversity RX channel of the RF unit to the calculated attenuation. Then, wait
for 10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Run the MML command MOD RXBRANCH to set the attenuation on the main RX
channel and diversity RX channel of the RF unit to 0. Then, wait for ten minutes.
13/11/2012 9:15
Fault Management
353 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
354 de 526
Carrier No.
Carrier number
Board Type
Alarm Impact
Minor
System Actions
None
Possible Causes
The main RX channel or diversity RX channel of the RF unit is faulty.
The setting of attenuation on the RX channel of the RF unit is incorrect.
External interferences exist only on the main or diversity antenna of the RF unit.
The feeder connected to the RF unit is faulty, which results in a high passive intermodulation power
of the main or diversity antenna.
The feeder installation is improper. For example, the feeder connector is loose, soaked or damaged,
or the feeder is deformed.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the RF unit on the M2000:
26521 RF Unit RX Channel RTWP/RSSI Too Low
26532 RF Unit Hardware Fault
26530 RF Unit ALD Current Out of Range
Y => The correlated alarm exists. Go to substep b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm with recommended actions.
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 parameter settings of the RF unit on the M2000.
a. Calculate the attenuation on the RX channel of the RF unit.
b. Run the MML command MOD RXBRANCH to set the attenuation on the main and
diversity RX channels of the RF unit to the calculated attenuation.
c. Wait for 40 minutes.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
355 de 526
13/11/2012 9:15
Fault Management
356 de 526
Description
This alarm is reported when the operating current of the Power Amplifier (PA) on a TX channel of the RF unit is
beyond the normal range.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
TX Channel No.
TX channel number
Board Type
PA Temperature (C/F)
Temperature of the PA
Alarm Impact
Major
The RF unit automatically switches off the TX channel. The ongoing services carried
on the TX channel are disrupted.
System Actions
The RF unit automatically switches off the faulty TX channel. The system waits for one minute and then switches
on the TX channel. After five minutes, the system checks the alarm. If the alarm persists, the RF unit
automatically switches off the TX channel again. If the alarm persists after three switching-on attempts, the
system alters to switch on the TX channel every 30 minutes, until the alarm is cleared or the RF unit is reset by
the user.
Possible Causes
The hardware of the RF unit is faulty.
Procedure
1. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
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. Replace the RF unit on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
13/11/2012 9:15
Fault Management
357 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
PA Temperature (C/F)
Temperature of the PA
Board Temperature(C/F)
Alarm Impact
Major
The RF unit automatically switches off the TX channel to prevent the hardware from
being burned out because of high temperature. The ongoing services carried on the
RF unit are disrupted.
Minor
The reliability of internal components of the RF unit may decrease when operating in
a high-temperature environment for a long period of time. Meanwhile, the quality of
services carried on the RF unit decreases.
System Actions
When the temperature of an RF unit exceeds the major alarm threshold, the RF unit automatically switches off
the TX channel. When the temperature of the RF unit drops to a certain value, the RF unit switches on the TX
channel again. To protect the power amplifier (PA) from being damaged by frequent switching-on and -off, this
alarm cannot be cleared after the TX channel has been switched off and on for three times. Under that
circumstance, users need to solve the temperature problem onsite and then manually reset the RF unit. When
the temperature of an RF unit is between the minor alarm threshold and the major alarm threshold, the BBU
limits the user access to a cell through the RF unit to prevent further power consumption and temperature
increase.
Possible Causes
The ambient temperature of the RF unit is extremely high, or the heat dissipation malfunctions.
The hardware of the RF unit is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:
13/11/2012 9:15
Fault Management
358 de 526
Parameters
13/11/2012 9:15
Fault Management
359 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RF unit automatically performs the amplitude limitation on input power. In this
case, the quality of services carried on the RF unit may decrease, and call drops
may occur on edge of coverage of the RF unit.
System Actions
The RF unit automatically performs the amplitude limitation on input power.
Possible Causes
When the input power of the RF unit approaches or reaches the maximum input power, the user
starts the stimulated downlink load.
The user access threshold is improper, which leads to the actual number of users to exceed the
allowed capacity of the RF unit.
The board in the BBU connected to the RF unit is running improperly.
Procedure
1. Check the state of stimulated downlink load on the M2000.
a. Run the MML command DSP DLSIM to check whether the stimulated downlink load is
started on the RF unit.
Y => The stimulated downlink load is started. Go to sub-step b.
N => The stimulated downlink load is not started. Go to step 2.
b. Run the MML command STP DLSIM to stop the stimulated downlink load.
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 user access threshold on the M2000.
a. If the user access threshold exists in the base station or RNC, check whether the
threshold is proper according to the network plan.
Y => The threshold is proper. Go to step 3.
N => The threshold is improper. Go to sub-step b.
b. Modify the user access threshold in the base station or RNC according to the network
plan.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
360 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
TX Channel No.
TX channel number
Board Type
VSWR
Alarm Impact
Major
The return loss at the antenna port is excessive. When the detected VSWR exceeds
the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When "VSWR alarm
post-processing switch" is set to "ON", the TX channel of the RF unit is switched off
and the alarm cannot be automatically cleared, and the ongoing services carried on
the TX channel are disrupted..When "VSWR alarm post-processing switch" is set to
"OFF", the power of the RF unit is automatically decreased (by 3 dB by default) to
13/11/2012 9:15
Fault Management
361 de 526
Alarm Severity
Alarm Impact
avoid hardware damage, and the alarm can be automatically cleared.
Minor
The return loss at the antenna port is relatively large. In this case, the output power
of the RF unit decreases and the cell coverage shrinks.
System Actions
When the detected VSWR exceeds the minor alarm threshold, the system does not handle the alarm. The alarm
is automatically cleared when the detected VSWR becomes smaller than the alarm threshold. When the
detected VSWR exceeds the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When "VSWR alarm post-processing switch" is set to
"ON", the TX channel of the RF unit is switched off and the alarm cannot be automatically cleared.When "VSWR
alarm post-processing switch" is set to "OFF", the power of the RF unit is automatically decreased (by 3 dB by
default) to avoid hardware damage. Once the detected VSWR becomes smaller than the alarm threshold, the
alarm is automatically cleared.
Possible Causes
The preset VSWR threshold is very low. It is recommended that the VSWR alarm threshold not be
used as the VSWR acceptance threshold.
The VSWR threshold is set to an excessively low value for the other mode of the multi-mode RF
units.
The installation of jumpers does not comply with the plan.
The feeder connector on the antenna port does not meet the requirements, is loose or waterlogged,
or has foreign objects.
The feeder connected to the antenna port of the RF unit is bent, deformed, or damaged.
The RF unit is faulty in hardware.
The frequency bands supported by the RF unit do not match the frequency bands supported by the
components of the antenna system. The components of the antenna system include antennas,
feeders, jumpers, combiner-dividers, filters, and tower-mounted amplifiers (TMAs).
A component of the antenna system is damaged.
Procedure
1. Check the VSWR threshold on the M2000.
a. Run the MML command LST RRU to query the VSWR threshold of the RF unit. If the
alarm severity is major, query the value of VSWR alarm post-processing threshold. If
the alarm severity is minor, query the value of VSWR alarm threshold.Check whether
the VSWR threshold is proper according to the configuration plan.
Y => The threshold is proper. Go to step 2.
N => The threshold is improper. Go to sub-step b.
b. If the RF unit works in multi-mode, run the MML command LST RRU to query the
VSWR threshold configured for the other mode. Check whether the VSWR thresholds
configured for the two modes are consistent.
Y => The VSWR thresholds configured for the two modes are consistent. Go to step 2.
N => The VSWR thresholds configured for the two modes are inconsistent. Go to
sub-step c.
c. Run the MML command MOD RRU to modify the VSWR threshold of the RF unit. If the
alarm severity is major, set the value of VSWR alarm post-processing threshold. If the
13/11/2012 9:15
Fault Management
362 de 526
13/11/2012 9:15
Fault Management
363 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Antenna Port
Board Type
Specific Problem
Alarm Impact
Minor
The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases.
Warning
The antenna device can work normally, but some secondary functions of the antenna
device fail.
System Actions
In the case of overcurrent, overcurrent protection, and open-circuit protection occurs on the antenna
device, the RF unit automatically switches off the power supply to the antenna device. Meanwhile,
the attenuation on the RX channel is set to 0 to minimize the impact of TMA fault on the receive
sensitivity of the corresponding RX channel.
In the case of overcurrent and overcurrent protection occurs on the antenna device, the RF unit
switches off the power supply to the antenna device and then attempts to switch on the power supply
every other minute. If the fault persists after three attempts, the RF unit does not retry any more.
Five minutes after open-circuit protection occurs and the the power supply to the antenna device is
13/11/2012 9:15
Fault Management
364 de 526
switched off, the RF unit begins the attempt to switch on the power supply to the antenna device
every other minute. If the fault persists after 26 attempts, the RF unit does not retry any more.
Possible Causes
The configuration of the ALD switch is incorrect.
The preset ALD current threshold of the RF unit is incorrect.
The feeder connector is loose or waterlogged.
The feeder is deformed.
The jumper between the feeder and the antenna device is loose.
The ALD power supply circuit of the RF unit is faulty.
The antenna device is faulty.
Procedure
1. Check the configuration of the ALD power supply switch on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT to query the status of
the ALD power supply switch of the RF unit. Check whether the status is correct
according to the configuration plan.
Y => The status of the ALD power supply switch is correct. Go to step 2.
N => The status of the ALD power supply switch is incorrect. Go to sub-step b.
b. Run the MML command MOD ANTENNAPORT/MOD RETPORT to modify the ALD
power supply switch configuration according to the configuration plan.
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 preset ALD current threshold of the RF unit on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT/LST
ANTENNAPORT/LST RETPORT to query the ALD current threshold of the RF unit.
Consult the related ALD manual for the operating current of the ALD. Check whether
the ALD current threshold is correct.
Y => The threshold is correct. Go to step 3.
N => The threshold is incorrect. Go to sub-step b.
b. Run the MML command MOD ANTENNAPORT/MOD RETPORT to modify the ALD
current threshold of the RF unit 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 3.
3. Reconnect the jumper to the antenna port of the RF unit on site.
a. Reconnect the jumper to the antenna port of the RF unit.
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 4.
13/11/2012 9:15
Fault Management
365 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
366 de 526
Subrack No.
Slot No.
Antenna Port
Board Type
Hardware Capability
Alarm Impact
Minor
The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases.
System Actions
None
Possible Causes
The coaxial ALD switch is configured, but actually the multi-wire cable is connected to the multi-wire
port.
The multi-wire ALD switch is configured, but actually the multi-wire cable is not connected to the
multi-wire port.
Procedure
1. Check the configuration of the ALD switch on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT to query the
configuration of the ALD switch of the RF unit. Check whether the configuration is
correct according to the configuration plan.
Y => The configuration is correct. Go to step 2.
N => The configuration is incorrect. Go to sub-step b.
b. Run the MML command MOD ANTENNAPORT/MOD RETPORT to modify the ALD
switch configuration 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 sub-step c.
c. Run the MML command DSP ANTENNAPORT/DSP RETPORT to check whether the
ALD switch configuration is consistent with the actual configuration.
Y => The ALD switch configuration is consistent with the actual configuration. Contact
Huawei Customer Service Center.
N => The ALD switch configuration is inconsistent with the actual configuration. Go to
step 2.
2. Reconnect the cable to the ALD port of the RF unit on site.
13/11/2012 9:15
Fault Management
367 de 526
a. Reconnect the cable to the ALD port of the RF unit on site 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. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RF unit may work improperly. The ongoing services carried on the RF unit may
be disrupted.
Minor
Some functions of the RF unit may fail and the quality of services carried on the RF
unit may decrease.
System Actions
When a critical component of an RF unit is faulty, the system automatically disables the faulty RX channel or TX
channel associated with the RF unit.
Possible Causes
The RF unit hardware is faulty.
Procedure
1. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
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. Replace the RF unit on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
368 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RF unit may work improperly. The RF unit will be automatically reset. The
ongoing services carried on the RF unit are disrupted during reset.
System Actions
The system automatically resets the RF unit.
Possible Causes
The software program of the RF unit runs improperly, such as suspension.
Procedure
1. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF to reset the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
369 de 526
Board Type
CPU Load(%)
CPU load
Alarm Impact
Minor
Some functions of the RF unit may fail, such as channel gain correction. In this case,
the quality of services carried on the RF unit decreases. Long-term CPU overload
may result in delayed response or timeout of maintenance tasks of the RF unit.
System Actions
None
Possible Causes
The user runs too many configuration or maintenance commands frequently on the RF unit.
The user starts too many test or measurement tasks on the RF unit.
The software program of the RF unit runs improperly.
Procedure
1. Stop the configuration and maintenance tasks on the RF unit on the M2000.
a. Stop the configuration and maintenance tasks on the RF unit. Then, wait for 15 minutes.
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. Stop all the test, tracing, and statistical tasks on the RF unit on the M2000
a. Stop all the site test, tracing, and statistical tasks on the RF unit. Then, wait for 15
minutes.
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 3.
3. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
370 de 526
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Configuration Item
Board Type
Mode of Original
Parameter
Mode of New
Parameter
Alarm Impact
Minor
This alarm is reported when the frequencies configured for different modes conflict in
multi-mode configuration.
System Actions
None
Possible Causes
This alarm is reported when the frequencies configured for different modes conflict in multi-mode configuration.
Procedure
1. Check the frequencies configured for different modes on the M2000.
a. Run the MML command LST LOCELL to check the frequency configuration of each
mode in multi-mode configuration of the RF unit. Locate the conflicting frequencies.
b. Run the MML command MOD LOCELL to modify the frequency configuration of each
mode of the RF unit according to the network plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
13/11/2012 9:15
Fault Management
371 de 526
Slot No.
Board Type
Alarm Impact
Major
Some components in the RF unit may work improperly. In certain cases, the ongoing
services carried on the RF unit may be disrupted.
System Actions
When the working clock of a critical component in the RF unit is faulty, the system automatically disables the
faulty RX channel or TX channel.
Possible Causes
The uplink interface of the RF unit is faulty, resulting in the faulty clock that is extracted at the
interface.
The clock chip or another component in the RF unit is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the port of the RF unit connecting to the peer device
(upper- or lower-level RF unit or the BBU) on the M2000.
26504 RF Unit CPRI Interface Error
26234 BBU CPRI Interface Error
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 with recommended actions.
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. Reset the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
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 3.
3. Replace the RF unit on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
13/11/2012 9:15
Fault Management
372 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The AC power supply to the RF unit fails.
Procedure
1. Check the AC power supply of the RF unit on site.
a. Check the AC power equipment of the RF unit on site. Take proper measures to
restore the AC power.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
ALD No.
Device Type
13/11/2012 9:15
Fault Management
373 de 526
Alarm Severity
Alarm Impact
Major
If the maintenance link of the RET antenna is broken, the antenna tilt cannot be
regulated. In this case, the state of the RET antenna cannot be monitored.
If the maintenance link of the TMA is broken, the TMA gain cannot be configured. In
this case, the state of the TMA cannot be monitored.
The maintenance link for the SASU is disconnected. Therefore, the gain of the SASU
cannot be set and the SASU status cannot be monitored.
System Actions
None
Possible Causes
The ALD current of the RF unit is out of range, or the configured ALD switch does not match the
actual type of the ALD port on the RF unit.
The ALD switch of the RF unit is not turned on.
The data configuration of the antenna is incorrect. For example, the vendor code, equipment serial
number, or antenna type is not configured or incorrect; the control port is incorrectly configured.
There are feeder problems, such as water damage, connector fault, or bent cable.
The hardware of the RF unit is faulty.
The antenna device is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the RF unit on the M2000.
26530 RF Unit ALD Current Out of Range
26531 RF Unit ALD Switch Configuration Mismatch
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 with recommended actions.
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. Set the ALD switch of the RF unit on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch. Then, turn on the ALD switch.
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 3.
3. Check the antenna device configuration of the RF unit on the M2000.
a. Run the MML command LST RET/LST TMA/LST SASU to check whether the antenna
device configuration, such as vendor code , equipment serial number, antenna type, and
control port is consistent with the actual situation.
13/11/2012 9:15
Fault Management
374 de 526
13/11/2012 9:15
Fault Management
375 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The system cannot monitor the input power, battery, or ambient temperature. The
backup power device cannot be controlled.
System Actions
None
Possible Causes
The backup power device is configured, but not required actually.
The backup power device is not installed. The monitoring board of the backup power device is also
not powered on or works improperly.
The address settings of the DIP switch on the backup power device are incorrect.
The connection between the RF unit and the backup power device is not ready, or the cables are
faulty.
The backup power device is faulty.
Procedure
1. Check the configuration of the backup power device on the M2000.
a. Run the MML command LST PMU(PMU)/LST TCU(TCU) to query the configuration of
the backup power device on the RF unit. Check whether the configuration of the backup
power device is required according to the site plan.
Y => The configuration is required. Go to step 2.
N => The configuration is not required. Go to sub-step b.
13/11/2012 9:15
Fault Management
376 de 526
b. Run the MML command RMV PMU(PMU)/RMV TCU(TCU) to remove the unnecessary
backup power device of the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the working state of the backup power device on site.
a. Check whether the RUN LED on the backup power device blinks (ON for 1s and OFF
for 1s) on site.
Y => The RUN LED blinks (ON for 1s and OFF for 1s). Go to step 3.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). Go to sub-step b.
b. Power cycle the backup power device. Wait until the RUN LED blinks (ON for 1s and
OFF for 1s).
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 3.
3. Check the address settings of the DIP switch on the backup power device on site.
a. Check whether the address settings of the DIP switch on the backup power device are
correct according to the configuration plan. For details, see the installation guide.
Y => The address settings are correct. Go to step 4.
N => The address settings are incorrect. Go to sub-step b.
b. Modify the address settings of the DIP switch on the backup power device according to
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 4.
4. Check the cable connections of the backup power device on site.
a. Reconnect the cables between the RF unit and the backup power device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the cables between the RF unit and the backup power device.
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 5.
5. Reset the monitoring board for the backup power device on site.
a. Reseat the monitoring board for the backup power device. Wait until the RUN LED on
the monitoring board blinks (ON for 1s and OFF for 1s).
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 6.
13/11/2012 9:15
Fault Management
377 de 526
6. Replace the monitoring board for the backup power device on site.
a. Remove the monitoring board for the backup power device. Install a new monitoring
board. Wait until the RUN LED on the monitoring board blinks (ON for 1s and OFF for
1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Link No.
Board Type
Device Address
Alarm Impact
Major
The system cannot monitor or control the general serial port device that is installed
by the user.
System Actions
None
Possible Causes
The serial port device is configured, but not installed actually.
The serial port device is not powered on, or works improperly.
The address settings of the DIP switch on the serial port device are incorrect.
The connection between the RF unit and the serial port device is not ready, or the cables are faulty.
The serial port device is faulty.
Procedure
1. Check the configuration of the serial port device on the M2000.
a. Run the MML command LST PMU(PMU)/LST TCU(TCU) to query the configuration of
the serial port device on the RF unit. Check whether the configuration of the serial port
device is required according to the site plan.
13/11/2012 9:15
Fault Management
378 de 526
13/11/2012 9:15
Fault Management
379 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The RF unit encounters lightning strikes. Therefore, open-circuit protection is implemented by in the power surge
protector of the RF unit.
Procedure
1. Check the surge protector on site.
a. Check whether the surge protector of the RF unit and external power device is
functional.
Y => The surge protector is functional. Go to step 2.
N => The surge protector malfunctions or is not installed. Go to sub-step b.
b. Rectify the fault in the surge protector, or install a functional surge protector.
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. Replace the RF unit on site.
a. Replace the RF unit.
13/11/2012 9:15
Fault Management
380 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
TX Channel No.
TX channel number
Board Type
Alarm Impact
Warning
System Actions
None
Possible Causes
The command is executed to turn off the switch of the TX channel of the RF unit.
Procedure
1. Turn on the switch of the TX channel of the RF unit on the M2000.
a. After the NE maintenance is complete, run the MML command MOD TXBRANCH to
turn on the switch.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Parameter Description
13/11/2012 9:15
Fault Management
381 de 526
Name
Cabinet No.
Subrack No.
Slot No.
Specific
Problem
Specific Problem of the alarm(Cabinet Power Supply Abnormal, Cabinet Type and RF Unit
type Mismatch)
Alarm Impact
Minor
The RF unit operates in power derating mode, and thereby affects the system
capacity.
Major
The RF unit operates in power derating mode or becomes unavailable, and thereby
affects the system capacity and coverage.
System Actions
If "Specific Problem" is "Cabinet Power Supply Abnormal", the RF unit operates in power derating
mode.
If "Specific Problem" is "Cabinet Type and RF Unit Type Mismatch", the RF unit is set to be
unavailable or in power derating mode.
Possible Causes
The abnormal mains supply leads to an insufficient battery voltage.
The PSU is faulty.
The cabinet type and the RF unit type mismatch.
Procedure
1. Locate the cause of the alarm on the M2000.
a. Check for the problem in the alarm detailed information on the M2000.
If "Specific Problem" is "Cabinet Type and RF Unit Type Mismatch", go to step 2.
If "Specific Problem" is "Cabinet Power Supply Abnormal", go to step 3.
2. Check whether the cabinet type and the RF unit type match on the M2000.
a. Run the MML command DSP BRDMFRINFO to check the description in the
manufacture information about the RF unit that reports the alarm. Check whether the
RF unit type is MRFUe or MRFUd.
Y => The RF unit type is MRFUe or MRFUd, go to sub-step b.
N => The RF unit type is not MRFUe or MRFUd, Contact Huawei Customer Service
Center.
b. Run the MML command DSP CABMFRINFO to check whether the cabinet description
contains one of the following characters: 303+, 103+, and 202+.
Y => The cabinet description contains one of the following characters: 303+, 103+, and
202+, Contact Huawei Customer Service Center.
N => The cabinet description does not contain any of the following characters: 303+,
13/11/2012 9:15
Fault Management
382 de 526
Parameters
13/11/2012 9:15
Fault Management
383 de 526
Parameter
Name
Parameter Description
ALD No.
ALD Info.
Specific
Problem
Specific Problem of the alarm(Motor Detection Failed, Motor Permanently Stalled, Motor
Temporarily Stalled)
Alarm Impact
Minor
System Actions
None
Possible Causes
The motor of the RET antenna is faulty.
Procedure
1. Reset the RET antenna on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the RET antenna.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the RET antenna.
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. Replace the RET antenna on site.
a. Replace the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
ALD No.
Device Type
ALD Info.
13/11/2012 9:15
Fault Management
384 de 526
Alarm Impact
Major
If the primary hardware of the TMA is faulty, the RX gain amplification function of the
TMA may fail. In this case, the ongoing services carried on the RX channel
associated with the TMA are disrupted.
The SASU malfunctions. As a result, the cell coverage may shrink.
Minor
If the hardware of the RET antenna is faulty, the antenna tilt may fail to be regulated.
In this case, the status of the RET antenna cannot be monitored.
If the secondary hardware of the TMA is faulty, the TMA gain cannot be configured.
In this case, the status of the TMA cannot be monitored.
The secondary hardware of the SASU is faulty. As a result, some secondary
functions of the SASU may fail.
System Actions
When the TMA or SASU is severely faulty (alarm severity: major), the TMA or SASU is automatically bypassed.
Meanwhile, the system automatically sets the attenuation on the corresponding RX channel to 0. After the fault in
the TMA or SASU is cleared, the system automatically restores the attenuation on the corresponding RX channel
to the configured value.
Possible Causes
The antenna device (RET antenna or TMA) hardware is faulty.
Procedure
1. Reset the antenna device on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the antenna device.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the antenna device.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Replace the antenna device on site.
a. Perform the corresponding operation according to the antenna device type.
In the case of the RET antenna, replace the RET antenna.
In the case of the TMA, replace the TMA.
In the case of the SASU, replace the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
385 de 526
Parameters
Parameter Name
Parameter Description
ALD No.
ALD Info.
Alarm Impact
Minor
The cell coverage on the RET antenna is inconsistent with the configuration.
System Actions
None
Possible Causes
A newly installed RET antenna is not calibrated.
The RET antenna is powered off when the antenna tilt is adjusted.
The configuration file of the RET antenna is downloaded again.
Procedure
1. Calibrate the RET antenna on the M2000.
a. Run the MML command CLB RET to calibrate the RET antenna.
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. Replace the RET antenna on site.
a. Replace the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
ALD No.
ALD Info.
13/11/2012 9:15
Fault Management
386 de 526
Alarm Severity
Alarm Impact
Minor
System Actions
None
Possible Causes
The RET antenna is powered off during data reconfiguration, which leads to data loss.
The flash memory of the RET antenna is damaged.
The RET antenna is newly installed without the data configuration file.
Procedure
1. Download the configuration file of the RET antenna on the M2000.
a. Run the MML command DLD RETCFGDATA to re-download the configuration file of the
RET antenna.
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. Reset the RET antenna on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the RET antenna.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the RET antenna.
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 3.
3. Replace the RET antenna on site.
a. Replace the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
ALD No.
ALD Info.
13/11/2012 9:15
Fault Management
387 de 526
Alarm Impact
Major
After the TMA is bypassed, the receive sensitivity of the RX channel decreases and
the sector coverage shrinks.
System Actions
The TMA is automatically bypassed. Meanwhile, the system automatically sets the attenuation on the
corresponding RX channel to 0.
Possible Causes
The TMA hardware is faulty.
Procedure
1. Reset the TMA on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the TMA.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the TMA.
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. Replace the TMA on site.
a. Replace the TMA.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
ALD No.
Subunit No.
ALD Info.
Alarm Impact
Major
The return loss at the antenna port of the SASU is relatively large. In this case, the
output power of the RF unit decreases and the cell coverage shrinks.
13/11/2012 9:15
Fault Management
388 de 526
System Actions
None
Possible Causes
The feeder connector on the antenna port of the SASU is loose or waterlogged.
The feeder connected to the antenna port of the SASU is bent, deformed, or damaged.
The VSWR detection circuit of the SASU is faulty.
Procedure
1. Reconnect the jumper to the antenna port of the SASU on site.
a. Reconnect the jumper to the antenna port of the SASU. Then, wait for 10 minutes.
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 installation of SASU feeders on site.
a. Check the installation of SASU feeders. Then, wait for 10 minutes.
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 3.
3. Reset the SASU on site.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the SASU.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the SASU. Then, wait for 10 minutes.
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 4.
4. Replace the SASU on site.
a. Replace the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
13/11/2012 9:15
Fault Management
389 de 526
Parameter Name
Parameter Description
ALD No.
ALD Info.
Alarm Impact
Minor
The cell coverage on the RET antenna is inconsistent with the configuration.
System Actions
None
Possible Causes
Because of RET antenna reset or maintenance link disconnection, the data configuration on the base
station is inconsistent with that on the RET antenna.
The configured data of the RET antenna is lost or modified on the base station.
The RET antenna works improperly, resulting in an automatic change of the downtilt.
The configured downtilt exceeds the antenna capability.
Procedure
1. Check the error range of the downtilt alarm on the M2000.
a. Run the MML command LST RETSUBUNIT to query the error range of the downtilt
alarm. Check whether the error range is consistent with the configuration plan.
Y => The error range is consistent with the configuration plan. Go to step 2.
N => The error range is inconsistent with the configuration plan. Go to sub-step b.
b. Run the MML command MOD RETSUBUNIT to modify the error range of the downtilt
alarm of the RET.
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. Set the RET antenna tilt on the M2000.
a. Check whether the configured downtilt exceeds the RET antenna capability.
Y => The configured downtilt exceeds the RET antenna capability. Go to substep b.
N => The configured downtilt does not exceed the RET antenna capability. Go to
substep d.
b. Check whether the downtilt is appropriate.
Y => The downtilt is appropriate, and the RET antenna capability is insufficient. Go to
step 4.
N => The downtilt is inappropriate. Go to substep c.
c. Reconfigure the downtilt.
d. Run the MML command MOD RETTILT to set the RET downtilt.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
390 de 526
Parameters
Parameter Name
Parameter Description
ALD No.
ALD Info.
Alarm Impact
Minor
System Actions
None
Possible Causes
Because of TMA reset or maintenance link disconnection, the data configuration on the base station
is inconsistent with that on the TMA.
The configured data of the TMA is lost or modified on the base station.
The TMA works improperly, resulting in an automatic change of the TMA gain or TMA work mode.
Procedure
13/11/2012 9:15
Fault Management
391 de 526
Parameters
Parameter Name
Parameter Description
ALD No.
ALD Info.
Alarm Impact
Minor
System Actions
None
Possible Causes
Because of SASU reset or maintenance link disconnection, the data configuration on the base station
13/11/2012 9:15
Fault Management
392 de 526
Procedure
1. Set the SASU parameters on the M2000.
a. Run the MML command MOD SASUSUBUNIT to set the SASU mode.
Run the MML command MOD SASUSUBUNIT to set the SASU gain.
Run the MML command MOD SASU to set the DC switch state of the SASU.
Run the MML command MOD SASU to set the DC load of the SASU.
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. Reset the SASU on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the SASU.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the SASU.
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 3.
3. Replace the SASU on site.
a. Replace the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
ALD No.
ALD Info.
Alarm Impact
Major
After the SASU is bypassed, the receive sensitivity of the RX channel decreases and
13/11/2012 9:15
Fault Management
393 de 526
Alarm Severity
Alarm Impact
the sector coverage shrinks.
System Actions
The SASU is automatically bypassed. Meanwhile, the system automatically sets the attenuation on the
corresponding RX channel to 0.
Possible Causes
The SASU hardware is faulty.
Procedure
1. Reset the SASU on the M2000.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the SASU.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the SASU.
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. Replace the SASU on site.
a. Replace the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RHUB may work improperly. The ongoing services carried on the RHUB may be
disrupted.
13/11/2012 9:15
Fault Management
394 de 526
Alarm Severity
Alarm Impact
Minor
Some functions of the RHUB may fail and the quality of services carried on the
PRRUs connected to the RHUB may decrease.
System Actions
When a critical component of an RHUB is faulty, the system automatically disables the RHUB.
Possible Causes
The hardware of the RHUB is faulty.
Procedure
1. Reset the RHUB on the M2000.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF to reset the RHUB on the M2000.
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. Replace the RHUB on site.
a. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RHUB may work improperly. The RHUB will be automatically reset. The ongoing
services carried on the PRRUs connected to the RHUB are disrupted during reset.
13/11/2012 9:15
Fault Management
395 de 526
System Actions
The system resets the RHUB.
Possible Causes
The software program of the RHUB runs improperly, such as suspension.
Procedure
1. Reset the RHUB on the M2000.
a. Run the MML command RST BRD to reset the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
CPU Load(%)
CPU load
Alarm Impact
Minor
The user access success rate and service quality may decrease.
Long-term CPU overload may result in delayed response or timeout of maintenance
tasks of the board.
The test or tracing tasks with low priority may be automatically suspended or
terminated.
System Actions
The flow control is started. The test or tracing tasks with low priority may be automatically suspended or
terminated.
Possible Causes
The user runs too many configuration or maintenance commands frequently on the RHUB.
The user starts too many test or measurement tasks on the RHUB.
The software program of the RHUB runs improperly.
13/11/2012 9:15
Fault Management
396 de 526
Procedure
1. Stop the configuration and maintenance tasks on the RHUB on the M2000.
a. Stop the configuration and maintenance tasks on the RHUB. Then, wait for 15 minutes.
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. Stop the test, tracing, and information collecting tasks in progress on the RHUB on the M2000.
a. Stop all the test, tracing, and information collecting tasks in progress on the RHUB.
Then, wait for 15 minutes.
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 3.
3. Reset the RHUB on the M2000.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF on the M2000 to reset the RHUB through
power-off. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
Some components in the RHUB may work improperly. In certain cases, the ongoing
services carried on the PRRUs connected to the RHUB may be disrupted.
System Actions
When the working clock of a critical component in the RHUB is faulty, the system automatically disables the
13/11/2012 9:15
Fault Management
397 de 526
faulty RHUB.
Possible Causes
The uplink CPRI interface of the RHUB is faulty, resulting in the faulty clock that is extracted at the
CPRI interface.
The clock processor or another component in the RHUB is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the CPRI port of the RHUB on the M2000:
26783 RHUB CPRI Interface Error
26234 BBU CPRI Interface Error
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.
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. Reset the RHUB on the M2000.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF on the M2000 to reset the RHUB through
power-off.
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 3.
3. Replace the RHUB on site.
a. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
398 de 526
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
The RHUB is not configured with the UPS.
The cable between the RHUB and the SPD is not ready or faulty.
The protection circuit of the SPD fails.
Procedure
1. Check the UPS configuration on site.
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 0.
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 cable connection between the RHUB and the SPD on site.
a. Check whether the cable connection between the RHUB and the SPD is normal.
Y => The cable connection is normal. Go to procedur 3.
N => The cable connection is faulty. Go to sub-step b.
b. Reconnect the cable between the RHUB and the SPD.
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 3.
3. Replace the SPD on site.
a. Replace the SPD on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
399 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RHUB is powered by the UPS when the AC mains supply fails. If the AC mains
supply is unavailable for a long time, the RHUB will be powered off when the battery
is exhausted. In this case, the ongoing services carried on all the PRRUs connected
to the RHUB are disrupted.
System Actions
None
Possible Causes
The RHUB is not configured with the UPS.
The monitoring cable between the RHUB and the UPS is faulty.
The AC mains supply for the UPS fails.
Procedure
1. Check the UPS configuration on site.
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 1.
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 cable between the RHUB and the UPS on site.
a. Check whether the monitoring cable between the RHUB and the UPS is normal.
13/11/2012 9:15
Fault Management
400 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The RHUB continues to operate for an additional short period after this alarm is
reported. When the UPS battery is exhausted, the RHUB is powered off and the
ongoing services carried on all the connected PRRUs are disrupted.
System Actions
None
Possible Causes
The RHUB is not configured with the UPS.
13/11/2012 9:15
Fault Management
401 de 526
The monitoring cable between the RHUB and the UPS is faulty.
The AC mains supply malfunctions for a long time, such as power failure, overvoltage, undervoltage,
or excessive frequency deviation.
The battery is damaged.
Procedure
1. Check the UPS configuration on site.
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 2.
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 cable between the RHUB and the UPS battery on site.
a. Check whether the monitoring cable between the RHUB and the UPS battery is normal.
Y => The monitoring cable is normal. Go to step 3.
N => The monitoring cable is faulty. Go to sub-step b.
b. Reconnect the monitoring cable between the RHUB and the UPS battery.
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 3.
3. Check the AC mains supply for the UPS on site.
a. Check whether the AC mains supply for the UPS malfunctions for a long time, such as
power failure, overvoltage, undervoltage, or excessive frequency deviation.
Y => The AC mains supply for the UPS malfunctions. Go to sub-step b.
N => The AC mains supply for the UPS is normal. Go to step 4.
b. Rectify the fault on the AC mains supply for the UPS. Wait until the AC mains supply is
available.
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 4.
4. Replace the battery on site.
a. Check whether the battery is damaged according to the maintenance manual offered by
the vendor.
Y => The battery is damaged. Go to sub-step b.
N => The battery is normal. Contact Huawei Customer Service Center.
b. Replace the faulty battery.
13/11/2012 9:15
Fault Management
402 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The UPS bypasses the AC mains supply to the RHUB when this alarm is reported.
The RHUB can continue to operate if the voltage and frequency of AC mains supply
meet the requirements of the RHUB.
System Actions
None
Possible Causes
The RHUB is not configured with the UPS.
The monitoring cable between the RHUB and the UPS is faulty.
The UPS is damaged.
Procedure
1. Check the UPS configuration on site.
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The UPS is configured. Go to step 2.
N => The UPS is not configured. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 3.
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 cable between the RHUB and the UPS on site.
13/11/2012 9:15
Fault Management
403 de 526
a. Check whether the monitoring cable between the RHUB and the UPS is normal.
Y => The monitoring cable is normal. Go to step 3.
N => The monitoring cable is faulty. Go to sub-step b.
b. Reconnect the monitoring cable between the RHUB and the UPS.
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 3.
3. Replace the UPS on site.
a. Replace the UPS on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The power supply for the RHUB may fail. In this case, the ongoing services carried
on all the PRRUs connected to the RHUB are disrupted.
System Actions
None
Possible Causes
The AC/DC module is installed improperly.
The AC/DC module is faulty.
The hardware of the RHUB is faulty.
Procedure
1. Remove and reinstall the AC/DC module on site.
a. Remove and reinstall the AC/DC module on the RHUB panel. Wait until the RHUB
13/11/2012 9:15
Fault Management
404 de 526
startup is complete.
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. Replace the AC/DC module on site.
a. Remove the AC/DC module from the RHUB panel and install a spare AC/DC module.
Wait until the RHUB startup is complete.
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 3.
3. Replace the RHUB on site.
a. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Cause
Board Type
Alarm Impact
Major
The RHUB and connected PRRUs may fail to work normally. In this case, the
ongoing services carried on the PRRUs are disrupted.
System Actions
None
Possible Causes
The AC mains supply malfunctions.
Overtemperature protection for the AC/DC module is triggered because the ambient temperature is
13/11/2012 9:15
Fault Management
405 de 526
extremely high.
The AC/DC module is installed improperly.
The AC/DC module is faulty.
The hardware of the RHUB is faulty.
Procedure
1. Check the AC mains supply on site.
a. Use a multimeter to measure the AC mains supply for the RHUB on site. Check whether
the AC mains supply is in overvoltage or undervoltage.
Y => The AC mains supply is in overvoltage or undervoltage. Go to sub-step b.
N => The AC mains supply is normal. Go to step 2.
b. Rectify the fault on the AC mains supply for the RHUB.
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 air vent of the RHUB on site.
a. Check whether the air vent of the RHUB is blocked by dusts or foreign objects.
Y => The air vent is blocked. Go to sub-step b.
N => The air vent is not blocked. Go to step 3.
b. Clean the air vent. Then, wait for 10 minutes.
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 3.
3. Remove and reinstall the AC/DC module on site.
a. Remove and reinstall the AC/DC module on the RHUB panel. Wait until the RHUB
startup is complete.
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 4.
4. Replace the AC/DC module on site.
a. Remove the AC/DC module from the RHUB panel and install a spare AC/DC module.
Wait until the RHUB startup is complete.
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 5.
5. Replace the RHUB on site.
a. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
406 de 526
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Faulty Port
Faulty Port
Cause
Board Type
Alarm Impact
Major
The PRRUs connected to the PSE may fail to work normally. In this case, the
ongoing services carried on the PRRUs are disrupted.
System Actions
None
Possible Causes
The cable between the RHUB and the PRRU is short-circuited.
The cable between the RHUB and the PRRU is disconnected.
The PRRU is faulty.
The RHUB is faulty.
Procedure
1. Remove and reinstall the cable between the RHUB and the PRRU on site.
a. Remove and reinstall the cable between the RHUB and the PRRU. Power off the PRRU
and then power it on. Wait until the PRRU startup is complete.
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. Use another PSE port on site.
a. Disconnect the cable from the faulty PSE port of the RHUB, and then connect the cable
to another idle PSE port of the RHUB. Power off the PRRU and then power it on. Wait
13/11/2012 9:15
Fault Management
407 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
PSE No.
PSE No.
Cause
Cause (Over Voltage, Below Voltage, Over Temperature Close, Oscillator Fault)
Board Type
Alarm Impact
Major
The PRRUs connected to the faulty PSE may fail to work normally. In this case, the
ongoing services carried on the PRRUs may be disrupted.
13/11/2012 9:15
Fault Management
408 de 526
System Actions
None
Possible Causes
The hardware of the RHUB is faulty.
Overtemperature protection for the PSE is triggered because the ambient temperature of the RHUB
is extremely high.
Procedure
1. Check the overtemperature protection state of the PSE on the M2000.
a. Check whether the fault cause is "Overtemperature Shutdown" according to the alarm
location information.
Y => The fault cause is "Overtemperature Shutdown". Go to step 2.
N => The fault cause is not "Overtemperature Shutdown". Go to step 3.
2. Check the air vent of the RHUB on site.
a. Check whether the air vent of the RHUB is blocked by dusts or foreign objects.
Y => The air vent is blocked. Go to sub-step b.
N => The air vent is not blocked. Go to step 3.
b. Clean the air vent and then wait for 10 minutes.
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 3.
3. Check the AC/DC module on the M2000.
a. Run the MML command LST ALMAF to query active alarms. Check for 26775 RHUB
AC/DC Module Problem.
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 4.
b. Clear the correlated alarm according to the relevant handling suggestions.
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 4.
4. Reset the RHUB on the M2000.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the RHUB. Wait until the RHUB startup is
complete.
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 5.
5. Replace the RHUB on site.
13/11/2012 9:15
Fault Management
409 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Alarm Impact
Major
In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the active CPRI link of lower-level devices is switched over to the standby CPRI link.
Possible Causes
The networking of RHUB and lower-level devices is incorrect. Redundant lower-level devices are
configured.
The optical module on the CPRI port of the RHUB is not in position, or the cable connection on the
CPRI optical module or electrical port is not ready.
The optical module on the CPRI port of the RHUB is faulty, or the cable connected to the CPRI
optical module or electrical port is faulty.
The connecting piece on the CPRI port of the RHUB is faulty.
Procedure
1. Check for redundant lower-level devices on the M2000.
a. Run the MML command LST RRUCHAIN to query the CPRI link networking of the faulty
13/11/2012 9:15
Fault Management
410 de 526
RHUB. According to the site planning, check whether the redundant lower-level devices
are configured.
Y => The redundant lower-level devices are configured. Go to sub-step b.
N => There is no redundant lower-level device. Go to step 2.
b. Run the MML command RMV RRU to remove the redundant lower-level devices.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the installation of the optical module, or check the cable connection on the CPRI optical
module or electrical port of the RHUB on site.
a. Check whether the optical module is installed, or whether the cable is connected to the
CPRI optical module or electrical port of the RHUB on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the CPRI optical/electrical port.
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 3.
c. Remove the optical module or the cable connected to the CPRI optical/electrical port,
and then reinstall it properly.
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 3.
3. Reset the RHUB on site.
a. Power off the RHUB on site and then power it on. Wait until the RHUB startup is
complete (the RUN LED blinking, ON for 1s and OFF for 1s).
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 4.
4. Replace the RHUB on site.
a. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
13/11/2012 9:15
Fault Management
411 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Alarm Impact
Major
The CPRI port of the RHUB does not work normally. The services carried on all the
PRRUs connected to the RHUB are disrupted.
System Actions
None
Possible Causes
The type of the optical module installed on an RHUB is not supported by the RHUB. For example, an RHUB
supports only an optical module of 2.5 Gbit/s, but an optical module of 1.25 Gbit/s is installed on the RHUB.
Procedure
1. Replace the optical module on site.
a. Replace the optical module of the RHUB on site. Ensure that the installed optical
module is supported by the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
13/11/2012 9:15
Fault Management
412 de 526
Port
Board Type
Port Type
Specific Problem
Alarm Impact
Major
In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RHUB automatically switches to a normal CPRI port if its uplink CPRI port is
faulty.
Possible Causes
The optical module or connector of the current-level RHUB is improperly installed. Or the optical
module is faulty.
The optical connector of the current-level RHUB is dirty.
The current-level RHUB is faulty.
The peer device (upper-level/lower-level RHUB, RF unit, or BBU) is not powered on.
The optical module or connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU)
is improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU) is dirty.
The peer device is faulty.
The optical link between the current-level RHUB and the peer device (upper-level/lower-level RHUB,
RF unit, or BBU) is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the faulty CPRI port of the RHUB on the M2000.
26780 RHUB Optical Module or Electrical Port Not Ready
26781 RHUB Optical Module Type Mismatch
26786 RHUB Optical Module Fault
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.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
413 de 526
13/11/2012 9:15
Fault Management
414 de 526
for 1s).
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 5.
5. Check the CPRI port of the peer device.
a. Remove and reinstall the optical module and connector on the CPRI port of the peer
device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
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 6.
6. Connect the TX and RX ports of the optical module at the peer device.
a. Remove the optical fiber from the optical module of the peer device. Then, connect the
TX and RX ports of the optical module by using an optical fiber for loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step b.
N => The alarm is not cleared. Go to sub-step c.
b. Disconnect the TX and RX ports of the optical module, and restore the optical
connection of the peer device. Then, Go to step 7.
c. Replace the optical module of the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. Power Cycle the Peer Device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Replace the peer device.
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 7.
7. Check the optical connections on site.
a. Check the optical connections between the current-level RHUB and the peer device.
Troubleshoot the improper optical connections, such as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
415 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Port Type
Alarm Impact
Major
In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RHUB automatically switches to a normal CPRI port if its uplink CPRI port is
faulty.
Possible Causes
If the CPRI optical transmission is used, the optical module or connector of the RHUB or peer device
may be improperly installed, or the optical link is faulty.
If the CPRI electrical transmission is used, the cable connector of the RHUB or peer device may be
improperly installed, or the cable is faulty.
The RHUB or peer device malfunctions, or the hardware is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
13/11/2012 9:15
Fault Management
416 de 526
a. Check for the correlated alarm on the faulty CPRI port of the RHUB on the M2000.
26780 RHUB Optical Module or Electrical Port Not Ready
26781 RHUB Optical Module Type Mismatch
26782 RHUB Optical Module Transmit/Receive Fault
26786 RHUB Optical Module Fault
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.
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. On site, check the cable connections on the CPRI electrical port of the RHUB.
a. Check the cable connections on the CPRI port of the current-level RHUB on site.
If the CPRI electrical transmission is used, Go to sub-step b.
If the CPRI optical transmission is used, Go to step 3.
b. Remove and reinstall the cable on the CPRI electrical port of the current-level RHUB
and the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Replace the cable on the CPRI electrical port.
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 3.
3. Check the running status of the RHUB or peer device on site.
a. Power off the RHUB on site and then power it on. Wait until the RHUB startup is
complete (the RUN LED blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Power Cycle the Peer Device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to sub-step d.
d. Replace the peer device.
13/11/2012 9:15
Fault Management
417 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Specific
Problem
Specific Problem of the alarm(Optical Module Performance Degraded, Reception Power too
High, Reception Power too Low)
Alarm Impact
Major
When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the CPRI link of the RHUB may decrease significantly,
or the ongoing services carried on the RHUB may even be disrupted.
Minor
When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the CPRI link of the RHUB may decrease to some
extent.
System Actions
None
Possible Causes
The optical module or connector of the current-level RHUB is improperly installed. Or the optical
module is aged.
The optical connector of the current-level RHUB is dirty.
The optical module on the CPRI port of the current-level RHUB is not supported by the current-level
RHUB, in terms of type (single-mode or multi-mode) and rate.
The optical module or connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU)
is improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU) is dirty.
The optical module on the CPRI port of the peer device (upper-level/lower-level RHUB, RF unit, or
BBU) is not supported by the peer device, in terms of type (single-mode or multi-mode) and rate.
13/11/2012 9:15
Fault Management
418 de 526
The optical fibers between the current-level RHUB and the peer device (upper-level/lower-level
RHUB, RF unit, or BBU) are bent, deformed, or aged. Or the length of optical fibers is excessive
(longer than 40 km), which leads to a high attenuation of optical signals.
Procedure
1. Check the CPRI port of the current-level RHUB on site.
a. Remove and reinstall the optical module and connector on the CPRI port of the
current-level RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module on the CPRI port is supported by the current-level
RHUB, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5
Gbit/s).
Y => The optical module is supported by the RHUB. Go to sub-step e.
N => The optical module is not supported by the RHUB. Go to sub-step d.
d. Select the optical module that is supported by the RHUB.
e. Replace the optical module.
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 CPRI port of the peer device on site.
a. Remove and reinstall the optical module and connector on the CPRI port of the peer
device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module on the CPRI port is supported by the peer device, in
terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5 Gbit/s).
Y => The optical module is supported by the peer device. Go to sub-step e.
N => The optical module is not supported by the peer device. Go to sub-step d.
d. Select the optical module that is supported by the peer device.
13/11/2012 9:15
Fault Management
419 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port
Board Type
Alarm Impact
Minor
System Actions
None
Possible Causes
13/11/2012 9:15
Fault Management
420 de 526
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the RHUB on the M2000:
26765 RHUB Hardware Fault
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.
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. Replace the optical module on site.
a. Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The CPRI interface between the RHUB and the PRRU malfunctions. In this case, the
maintenance link for the PRRU is broken and the PRRU cannot provide the services.
System Actions
None
Possible Causes
The cable connection between the RHUB and the PRRU is not ready.
The cable between the RHUB and the PRRU is faulty.
13/11/2012 9:15
Fault Management
421 de 526
Procedure
1. Remove and reinstall the cable between the RHUB and the PRRU on site.
a. Remove and reinstall the cable between the RHUB and the PRRU. Power off the PRRU
and then power it on. Wait until the PRRU startup is complete.
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. Use another PSE port of the RHUB on site.
a. Disconnect the cable from the faulty PSE port of the RHUB, and then connect the cable
to another idle PSE port of the RHUB. Power off the PRRU and then power it on. Wait
until the PRRU startup is complete.
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 3.
3. Replace the cable between the RHUB and the PRRU on site.
a. Replace the cable between the RHUB and the PRRU. Power off the PRRU and then
power it on. Wait until the PRRU startup is complete.
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 4.
4. Replace the PRRU on site.
a. Replace the PRRU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 5.
5. Replace the RHUB on site.
a. Replace the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
13/11/2012 9:15
Fault Management
422 de 526
None.
Alarm Impact
Major
The NE enters the default license mode. The NE services are subject to the default
license.
System Actions
The system works in default license mode.
Possible Causes
The license is unavailable.
The license is invalid.
The keep-alive period for the temporary license has expired.
Procedure
1. Check the license allocation on the M2000.
a. Check the license allocation on the M2000. Check whether the NE is allocated with the
license resources.
Y => The NE is allocated with the license resources. Go to sub-step c.
N => The NE is not allocated with the license resources. Go to sub-step b.
b. Adjust the license allocation among NEs on the M2000. Allocate the license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Operator Index
Alarm Impact
13/11/2012 9:15
Fault Management
423 de 526
Alarm Severity
Alarm Impact
Major
System Actions
None.
Possible Causes
The configured system capacity exceeds the currently allocated license limit for the system.
Procedure
1. Check the license allocation on the M2000.
a. Check the license allocation on the M2000. Check whether there are license resources
available for the current NE.
Y => There are license resources available for the current NE. Go to sub-step b.
N => There are no license resources available for the current NE. Go to step 2.
b. Adjust the license allocation among NEs on the M2000. Allocate more license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
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. Reconfigure the NE data on the M2000.
a. Change the values of NE data to be equal to or less than the limit values in the license.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. 3.
3. Order a license.
a. Based on hardware configuration and plan, order a license with a higher capacity limit.
End the alarm handling.
Parameters
Parameter Name
Parameter Description
Operator Index
13/11/2012 9:15
Fault Management
424 de 526
Usage
Current usage
Alarm Impact
Major
System Actions
None
Possible Causes
The traffic volume of the NE is beyond the licensed limit.
Procedure
1. Check the setting of the alarm threshold on the M2000.
a. Run the MML command LST LICENSEALMTHD to check whether the setting of the
alarm threshold is proper.
Y => The setting of the alarm threshold is proper. Go to step 2.
N => The setting of the alarm threshold is improper. Go to sub-step b.
b. Run the MML command SET LICENSEALMTHD to modify the alarm threshold.
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. Adjust the allocation of license resources among NEs on the M2000.
a. Check the license allocation on the M2000. Check whether there are license resources
available for the current NE.
Y => There are license resources available for the current NE. Go to sub-step b.
N => There are no license resources available for the current NE. Go to step 3.
b. Adjust the license allocation among NEs on the M2000. Allocate more license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
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 3.
3. Order a license.
a. Based on service requirements, order a license with a higher capacity limit. End the
alarm handling.
13/11/2012 9:15
Fault Management
425 de 526
maintenance terminal (LMT) due to one of the following reasons: (1) The number of invalid passwords that are
consecutively entered exceeds a pre-defined threshold. The default value of the threshold is three times. (2) The
user name is invalid.
Parameters
Parameter Name
Parameter Description
Service User IP
Specific Problem
Alarm Impact
Minor
The NE is exposed to security risks. The local user may be attacked by invalid users
or the NE is in an insecure network. The NE is vulnerable to attacks.
System Actions
If the user enters a valid user name but incorrect passwords, the corresponding local user account is locked.
Possible Causes
The user has forgotten the login password.
The NE is in an insecure network and is under attack.
Procedure
1. Check the validity of the local user account.
a. Based on the specific problem in the alarm detailed information, check whether the local
user account is valid.
Y => The local user account is valid, go to step 2.
N => The local user account is invalid, contact the network security center.
2. Check the identity of the login user.
a. Contact the owner of the login account. Check whether the login operation is initiated by
the owner.
Y => The login operation is initiated by the owner. Go to sub-step b.
N => The login operation is not initiated by the owner. Turn to the network security
center.
b. Check whether the owner of the account has forgotten the login password.
Y => The owner of the account has forgotten the login password. Go to sub-step c.
N => The owner of the account has not forgotten the login password. Go to sub-step d.
c. Run the MML command RST PWD to update the login password of the user on the
M2000. Inform the owner of the account about the new login password.
d. Run the MML command ULK USR to unlock the user on the M2000.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
426 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Service User IP
Alarm Impact
Minor
The NE is exposed to security risks, because the certificate of the peer has expired.
System Actions
The base station disconnects itself from the peer that uses an expired certificate.
Possible Causes
The peer certificate is not updated in time, and the peer certificate expires or the peer certificate is
revoked .
An invalid user attempts to connect to the base station with an expired certificate.
Procedure
1. Check the validity of the peer.
a. Check the validity of the peer based on the IP address of the peer that is reported in
the alarm detailed information.
Y => The peer is valid, go to step 2.
N => The peer is invalid, contact the network security center.
2. Update the certificate on the peer side.
a. Contact the staff on the peer side to update the certificate and then reestablish a
connection with the base station.
Check Whether the Alarm is Cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
427 de 526
Parameters
Parameter Name
Parameter Description
Certificate Type
Certificate Name
Alarm Impact
Minor
The Internet Key Exchange (IKE) or Security Socket Layer (SSL) negotiation
requires a valid certificate. If the base station adopts the IKE/SSL certificate
negotiation, an expired certificate may lead to a negotiation failure and disrupt the
ongoing services.
System Actions
None
Possible Causes
The time of the base station is incorrectly set.
Automatic certificate update fails.
The certificate is about to expire. That is, the time span between the current time and the expiration
time of the loaded certificate is below the user-defined threshold.
Procedure
1. Check for the correlated alarm on the M2000.
a. On the M2000, Check for the correlated alarm.
26266 Time Synchronization Failure
26842 Automatic Certificate Update Failed
Y => The correlated alarm exists. Go to sub-step b.
N=> The correlated alarm does not exist. Go to step2.
b. Clear the correlated alarm with recommended actions.
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 time setting of the base station on the M2000.
a. Run the MML command DSP TIME to check whether the current time of the base
station is correct.
Y => The time is correct. Contact Huawei Customer Service Center.
N => The time is incorrect. Go to sub-step b.
b. Run the MML command SET TIME to change the current time of the base station.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
428 de 526
Parameters
Parameter
Name
Parameter Description
Certificate Type
Certificate Name
Specific Problem
Specific Problem of the alarm(Expired, Lost, Damaged, Format Error, Other, Not Valid
Yet)
Alarm Impact
Major
The Internet Key Exchange (IKE) or Security Socket Layer (SSL) negotiation
requires a valid certificate. If the base station adopts the IKE/SSL certificate
negotiation, an invalid certificate may lead to a negotiation failure and disrupt the
ongoing services.
System Actions
None
Possible Causes
The certificate cannot be loaded.
The certificate expires or the certificate is revoked.
The certificate file is damaged.
The certificate file format is incorrect.
The certificate has not taken effect.
Procedure
1. Check for the correlated alarm on the M2000.
a. On the M2000, Check for the correlated alarm.
26266 Time Synchronization Failure
26842 Automatic Certificate Update Failed
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 with recommended actions.
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.
13/11/2012 9:15
Fault Management
429 de 526
13/11/2012 9:15
Fault Management
430 de 526
Parameters
Parameter Name
Parameter Description
Certificate Type
Certificate Name
Alarm Impact
Minor
System Actions
None
Possible Causes
The transmission network is faulty.
The task used to automatically update the certificate is not configured according to the configuration
plan, or the IP route is incorrectly configured.
The certificate and CRL server or the Certificate Authority (CA) server is abnormal.
The certificate is invalid(Expired, Damaged, Format Error, Not Valid Yet).
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarms of the port used for time synchronization on the M2000.
25880 Ethernet Link Fault
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 with recommended actions.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the settings of the automatic certificate update on the M2000.
a. On the M2000, determine the certificate type that induces the alarm based on the alarm
detailed information.
If "Certificate Type" is "CRL". Go to sub-step b.
If "Certificate Type" is "Application certificate". Go to sub-step d.
b. Run the MML command DSP CRL to check whether the CRL check task is configured
according to the configuration plan.
Y => If the CRL check task is configured according to the configuration plan. Go to step
3.
N => If the CRL check task is not configured according to the configuration plan. Go to
sub-step c.
13/11/2012 9:15
Fault Management
431 de 526
c. Run the MML command RMV CRL,ADD CRL to modify the CRL check task 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 3.
d. Run the MML command LST CERTCHKTSK to check whether the certificate check
task is configured according to the configuration plan.
Y => If the certificate check task is configured according to the configuration plan. Go
to step 3.
N => If the certificate check task is not configured according to the configuration plan.
Go to sub-step e.
e. Run the MML command SET CERTCHKTSK to modify the certificate check task
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 3.
3. Check whether the IP route from the NE to the certificate and CRL server or CA server is
configured on the M2000.
a. Run the MML command LST IPRT to check whether the IP route from the NE to the
certificate and CRL server or CA server exists.
Y => The route exists. Go to step 4.
N => The route does not exist. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route from the NE to the certificate and
CRL server or CA server.
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 4.
4. Check whether the route from the NE to the certificate and CRL server or CA server is available on
the M2000.
a. Run the MML command PING to start the PING test and check whether the CA server
or the server that stores the certificate and the CRL can be reached.
Y => The CA server or the server that stores the certificate and the CRL can be
reached. Go to step 5.
N => The CA server or the server that stores the certificate and the CRL cannot be
reached. Go to sub-step b.
b. Contact the maintenance center responsible for the routing device. Rectify the route
fault.
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 5.
5. Check whether the CA server or the server that stores the certificate and the CRL functions
normally.
13/11/2012 9:15
Fault Management
432 de 526
a. Contact the maintenance center responsible for the CA server or the server that stores
the certificate and the CRL. Check the status of the server and rectify the fault.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Local Cell ID
Local Cell ID
Alarm Impact
Minor
System Actions
None
Possible Causes
The user runs a command to block the local cell of the NE.
Procedure
1. Block the local cell on the M2000.
a. Run the MML command UBL LOCELL to block the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Name
Local Cell
ID
Parameter Description
Local Cell ID
13/11/2012 9:15
Fault Management
433 de 526
Specific
Problem
Alarm Impact
Major
System Actions
None
Possible Causes
User operations: The board is reset, blocked, not inserted, or not configured properly.
Configuration: The local cell configuration exceeds the capability supported by the hardware.
License capability: The license capability is lower than the local cell configuration capability.
Hardware capability: The CPRI bandwidth is insufficient.
Hardware faults: Board hardware is faulty, RF unit hardware is faulty, or the link between the
baseband interface board and RF unit is broken.
Software faults: The software of the board or RF unit malfunctions.
Procedure
1. Locate the cause of alarm on the M2000.
a. Locate the cause of alarm based on the alarm location information.
If "Specific Problem" is "Uplink common baseband resource unavailable", go to step 2.
If "Specific Problem" is "Downlink baseband resource unavailable", go to step 3.
If "Specific Problem" is "Baseband-RF interface resource unavailable", go to step 4.
If "Specific Problem" is "Uplink RF resource unavailable" or "Downlink RF resource
unavailable", go to step 5.
If "Specific Problem" is "License capability limited", go to step 7.
If "Specific Problem" is "Baseband board unavailable", go to step 8.
If "Specific Problem" is "RF board unavailable", go to step 9.
If "Specific Problem" is "Insufficient CPRI bandwidth", go to step 10.
2. Rectify the fault of uplink baseband resources on the M2000.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
13/11/2012 9:15
Fault Management
434 de 526
13/11/2012 9:15
Fault Management
435 de 526
13/11/2012 9:15
Fault Management
436 de 526
configured for the local cell, and then run the MML commands LST RRU and LST
RRUCHAIN to query the information about the interface board configured for the RRU.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the interface board-related alarms exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step c.
N => The alarms do not exist. Contact Huawei Customer Service Center.
c. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Rectify the RF resource fault on the M2000.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
alarms related to the RRU/RFU or the baseband board connected to the RRU/RFU.
26210 Board Blocked
26235 RF Unit Maintenance Link Failure
26237 RRU Network Breakpoint
26524 RF Unit PA Overcurrent
26525 RF Unit Temperature Unacceptable
26529 RF Unit VSWR Threshold Crossed
26532 RF Unit Hardware Fault
26538 RF Unit Clock Problem
26545 RF Unit TX Channel Switched Off Through Command
26765 RHUB Hardware Fault
26768 RHUB Clock Problem
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
437 de 526
13/11/2012 9:15
Fault Management
438 de 526
k. Check whether the maximum power configured in the local cell is within the power range
supported by the RRU or RFU. In transmit diversity and 0.5/0.5 same zone coverage
mode, the power allocated to each RRU or RFU is equal to half of the total power of
the local cell. Run the MML command DSP RRU to obtain the maximum transmit power
supported by the RRU or RFU.
Note: In the case of a multi-mode RRU or RFU, the RRU or RFU transmit power is
shared by multiple modes. The specifications of the RRU or RFU transmit power may
be restricted to the RRU or RFU hardware and the power lock.
Y => The maximum power configured in the local cell is out of the power range
supported by the RRU or RFU. Go to sub-step l.
N => The maximum power configured in the local cell is within the power range
supported by the RRU or RFU. Go to sub-step m.
l. Run the MML command MOD LOCELL to change the maximum transmit power of the
local cell to a value within the power range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step m.
m. Run the MML command LST RRU to obtain the information about the RRU or RFU
configured on the same chain/ring. Run the MML command LST LOCELL to obtain the
number of cells configured for the same RRU or RFU. Run the MML command DSP
SFP to obtain the transmission rate of the optical module. If the transmission rate is
1.25 Gbit/s, the CPRI interface supports only four local cells (2 TX + 2 RX). If the
transmission rate is 2.5 Gbit/s, the CPRI interface supports only eight local cells (2 TX
+ 2 RX). Check whether the allowed number of local cells on a chain/ring exceeds the
number of local cells corresponding to the transmission rate on the chain/ring.
Y => The allowed number of local cells on a chain/ring exceeds the number of local
cells corresponding to the transmission rate on the chain/ring. Go to sub-step n.
N => The allowed number of local cells on a chain/ring does not exceed the number of
local cells corresponding to the transmission rate on the chain/ring. Contact Huawei
Customer Service Center.
n. Run the MML command RMV LOCELL to delete the local cell whose resources are
unavailable, and then run the MML command ADD LOCELL to establish a local cell on
another RRU or RFU that has sufficient resources on the chain/ring.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step o.
o. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
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 6.
6. Replace the RRU on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
439 de 526
13/11/2012 9:15
Fault Management
440 de 526
13/11/2012 9:15
Fault Management
441 de 526
Parameters
Parameter Name
Parameter Description
Local Cell ID
Local Cell ID
Alarm Impact
Minor
System Actions
None
Possible Causes
The user starts the cell simulated load.
Procedure
1. Stop the cell simulated load.
a. Run the MML command STP DLSIM to stop the cell simulated load.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Local Cell ID
Local Cell ID
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Minor
The decrease in the NE output power causes a reduction in the cell coverage.
System Actions
None
13/11/2012 9:15
Fault Management
442 de 526
Possible Causes
The RRU is faulty or aged.
Procedure
1. Reset the RRU on the M2000.
a. According to the cabinet/subrack/slot number displayed in the alarm information, run the
MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is reported again. Go to step 2.
2. Replace the RRU on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
443 de 526
12. The local cell does not support DC+MIMO. This alarm is reported when the user configures DC+MIMO in
the local cell.
13. The local cell does not support ERACH. This alarm is reported when the user configures ERACH in the local
cell.
14. This alarm is reported when certain baseband boards in the uplink resource group used by the local cell do
not support Independent Demodulation of Signals from Multiple RRUs in One Cell.
15. This alarm is reported when the local cell cannot use all available uplink baseband resources in the uplink
resource group.
16. Users have configured the activation and deactivation capability for the supplementary carrier of a cell but
actually the activation and deactivation capability of the supplementary carrier is not supported.
17. Users have configured the HSUPA anti-interference scheduling capability for a cell but actually the cell does
not support the HSUPA anti-interference scheduling capability.
18. The local cell does not support DC-HSUPA. This alarm is reported when the user configures but actually the
cell does not support DC-HSUPA.
19. This alarm is reported when the CPRI bandwidth for UMTS cells is insufficient due to the bandwidth
occupation by cells of other systems.
Parameters
Parameter
Name
Parameter Description
Cause
(Some RRU(s) in the iDBS cell not usable, Number of occupied BBU CPRI ports connected to
RRUs in the iDBS cell exceeding six, RRU transmit power less than the transmit power required
by the local cell, Two TX channels not supported by the cell, Uplink 16QAM not supported by the
cell, Uplink L2+ not supported by the cell, Downlink 64QAM+MIMO not supported by the cell,
FDE not supported by the cell, IC not supported by the cell, DC not supported by the cell,
BOOST not supported by the cell, DCMIMO not supported by the cell, ERACH not supported by
the cell, MultiRRU Independ DemOver Cell not supported by WBBP Board, Cell can't use all
WBBP Board resources of the uplink resource group, ACT and DEA of Slave Carrier not
supported by the cell, Anti-Interference Scheduling for HSUPA not supported by the cell,
DC-HSUPA not supported by the cell, Insufficient CPRI bandwidth)
Local Cell
ID
Local Cell ID
Alarm Impact
Major
The coverage of the faulty local cell decreases, the RTWP reported by some RRUs
is discarded, the features configured on the local cell are not supported, or certain
demodulation capabilities of the uplink resource group used by the local cell are
unavailable.
System Actions
None
Possible Causes
Configuration: Parameter settings of the local cell are incorrect, or the local cell capability configured
by the user does not match the actual capability.
License capability: The license capability is lower than the local cell configuration capability.
13/11/2012 9:15
Fault Management
444 de 526
Hardware capability: The hardware capability of the baseband board or RF unit is insufficient, or the
CPRI bandwidth is insufficient.
Hardware faults: In scenarios of multiple RRUs in one cell, the hardware of an RRU that serves the
local cell is faulty, or the link between an RRU and the baseband interface board is broken.
Software faults: The software of the board or RF unit malfunctions.
Procedure
1. Locate the cause of alarm on the M2000.
a. Locate the cause of alarm based on the alarm location information.
If "Specific Problem" is "Some RRU(s) in the iDBS cell not usable", go to step 2.
If "Specific Problem" is "Number of occupied BBU CPRI ports connected to RRUs in the
iDBS cell exceeding six", go to step 4.
If "Specific Problem" is "RRU transmit power less than the transmit power required by
the local cell", go to step 5.
If "Specific Problem" is "Two TX channels not supported by the cell", go to step 6.
If "Specific Problem" is "Uplink 16QAM not supported by the cell", go to step 7.
If "Specific Problem" is "Uplink L2+ not supported by the cell", go to step 8.
If "Specific Problem" is "Downlink 64QAM+MIMO not supported by the cell", go to step
9.
If "Specific Problem" is "FDE not supported by the cell", go to step 10.
If "Specific Problem" is "IC not supported by the cell", go to step 11.
If "Specific Problem" is "DC not supported by the cell", go to step 12.
If Specific Problem is BOOST not supported by the cell,go to step 13.
If Specific Problem is DC+MIMO not supported by the cell,go to step 14.
If Specific Problem is ERACH not supported by the cell,go to step 15.
Identify the cause of the alarm based on the alarm location information:
If "Specific Problem" is "Independent Demodulation of Signals from Multiple RRUs in
One Cell not supported by certain baseband boards in the uplink resource group used
by the cell", go to step 16
If "Specific Problem" is "All available baseband resources in the uplink resource group
cannot be used by the cell", go to step 17
If Specific Problem is Users have configured the activation and deactivation capability
for the supplementary carrier of a cell but actually the activation and deactivation
capability of the supplementary carrier is not supported., go to step 18.
If Specific Problem is Users have configured the HSUPA anti-interference scheduling
capability for a cell but actually the cell does not support the HSUPA anti-interference
scheduling capability., go to step 19.
If Specific Problem is Users have configured but actually the cell does not support
DC-HSUPA, go to step 20.
If "Specific Problem" is "Insufficient CPRI bandwidth", go to step 21.
2. Check for redundant RRUs configured in the local cell on the M2000.
a. Run the MML command LST LOCELL to check the RRUs configured in the faulty local
cell. Check whether redundant RRUs exist according to the network planning.
Y => Redundant RRUs exist. Go to sub-step b.
13/11/2012 9:15
Fault Management
445 de 526
13/11/2012 9:15
Fault Management
446 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
6. Rectify the fault that the local cell does not support two TX channels on the M2000.
a. Check whether the local cell is required to support two TX channels.
Y => The local cell is required to support two TX channels. Go to sub-step c.
N => The local cell is not required to support two TX channels. Go to sub-step b.
b. Run the MML command MOD LOCELL to modify the configuration so that the local cell
does not support two TX channels.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Run the MML command LST LOCELL to query the cabinet/subrack/slot number of the
RRU configured for the local cell.
d. Run the MML command LST RRU to check whether the RRU for the local cell is
configured.
Y => The RRU is configured. Go to sub-step f.
N => The RRU is not configured. Go to sub-step e.
e. Run the MML command ADD RRU to add the RRU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step f.
f. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the alarms related to the RRU configured for the
local cell exist.
Y => The alarms exist. Go to sub-step g.
N => The alarms do not exist. Contact Huawei Customer Service Center.
g. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
7. Rectify the fault that the local cell does not support uplink 16QAM on the M2000.
a. Check whether the capability of the local cell to support uplink 16QAM is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support uplink 16QAM.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink 16QAM license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
13/11/2012 9:15
Fault Management
447 de 526
13/11/2012 9:15
Fault Management
448 de 526
13/11/2012 9:15
Fault Management
449 de 526
13/11/2012 9:15
Fault Management
450 de 526
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPb or WBBPd.
Y => The uplink resource group contains the WBBPb or WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPb or WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
new WBBPb or WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and downlink 64QAM+MIMO cannot be supported.
Go to sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new EBBC/EBBCd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
10. Rectify the fault that the local cell does not support FDE on the M2000.
a. Check whether the capability of the local cell to support FDE is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support FDE (checking that the local cell does not support
13/11/2012 9:15
Fault Management
451 de 526
13/11/2012 9:15
Fault Management
452 de 526
13/11/2012 9:15
Fault Management
453 de 526
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and IC cannot be supported. Go to sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
12. Rectify the fault that the local cell does not support DC on the M2000.
a. Check whether the capability of the local cell to support DC is required.
Y => The capability is required. Run the MML command LST DLDUALCELLGRP to
obtain a peer local cell that belongs to the same DC group as that for the local cell.
Then, go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command RMV DLDUALCELLGRP to change the settings of the local
cell. Ensure that the local cell does not support DC.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the IC license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
d. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
454 de 526
13/11/2012 9:15
Fault Management
455 de 526
13/11/2012 9:15
Fault Management
456 de 526
13/11/2012 9:15
Fault Management
457 de 526
13/11/2012 9:15
Fault Management
458 de 526
e. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step f.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and ERACH cannot be supported. Go to sub-step g.
f. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step h.
N => Go to sub-step g.
g. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
h. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
16. Remotely rectify the fault that baseband boards do not support Independent Demodulation of
Signals from Multiple RRUs in One Cell.
a. Run the MML command LST LOCELL to query the information about the local cell and
check the parameter "UL BB Resource Group No.". Run the MML command LST
ULGROUP to query the information about the uplink resource group used by the local
cell and check the following parameters of each board, ""Cabinet No. of UL Process
Unit", "Subrack No. of UL Process Unit", and "Slot No. of UL Process Unit". Then, run
the MML command DSP BRDMFRINFO to check whether the WBBPa is contained in
the uplink resource group used by the local cell.
Y =>The WBBPa is contained in the uplink resource group used by the local cell. Go to
sub-step b.
N => The WBBPa is not contained in the uplink resource group used by the local cell.
Contact Huawei Customer Service Center.
b. Run the MML command MOD ULGROUP to remove the WBBPa from the uplink
resource group used by the local cell. The WBBPa does not support Independent
Demodulation of Signals from Multiple RRUs in One Cell. It is recommended that the
WBBPa be replaced by the WBBPb or WBBPd or that the WBBPa is added to another
type of resource group.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
459 de 526
13/11/2012 9:15
Fault Management
460 de 526
Y => Go to sub-step b.
N => Go to sub-step d.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether license-related alarms concerning HSUPA
anti-interference scheduling exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => Go to sub-step c.
N => Contact Huawei Customer Service Center.
c. Clear the correlated alarm according to the online help.
Check whether the alarm is cleared.
Y=> The alarm is cleared. No further action is required.
N=> The alarm is not cleared. Contact Huawei Customer Service Center.
d. Run the MML command SET MACEPARA to modify the configuration so that the local
cell does not support HSUPA anti-interference scheduling.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
20. Rectify the fault that the local cell does not support DC-HSUPA on the M2000
a. Check whether the local cell is required to support DC-HSUPA.
Y => Go to sub-step b.
N => Go to sub-step d.
b. Check whether the cell supports DC. If not, enable DC for the cell.
If the cell supports DC-HSUPA after DC is enabled for the cell, end the task. If not, go
to c.
c. Check whether layer 2 enhancement is configured for the two cells in the DC group. If
not, configure the layer 2 enhancement.
Y=>The alarm is cleared. No further action is required.
N=>The alarm is not cleared. Go to sub-step d.
d. Run the MML command RMV ULDUALCELLGRP to modify the configuration so that
the local cell does not support DC-HSUPA.
Check whether the alarm is cleared.
Y =>The alarm is cleared. No further action is required.
N =>The alarm is not cleared. Contact Huawei Customer Service Center.
21. Locate the cause of CPRI bandwidth insufficiency on the M2000.
a. Run the MML command DSP CPRILBR to check whether the line rate of the RRU chain
meets the networking requirement.
Y => The line rate of the RRU chain meets the networking requirement. Go to sub-step
b.
N => The line rate of the RRU chain does not meet the networking requirement. Go to
sub-step c.
b. Query the carrier configuration for UMTS cells and the carrier configurations for cells of
13/11/2012 9:15
Fault Management
461 de 526
other systems that share CPRI bandwidths with the UMTS cells. Check whether the
carrier configuration exceeds the maximum typical configuration by referring to the
specifications of the MBTS CPRI networking in the 3900 Series Base Station Technical
Description.
Y => The carrier configuration exceeds the maximum typical configuration. Go to
sub-step d.
N => The carrier configuration does not exceed the maximum typical configuration.
Contact Huawei Customer Service Center.
c. Check the maximum configuration at each level in the MML command execution result,
and change the optical modules whose rates do not match.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
d. Adjust the base station configuration based on the specifications of the MBTS CPRI
networking in the 3900 Series Base Station Technical Description.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Name
Parameter Description
Cause
(The source cell is not R99 cell, The target cell is not DPA cell, License capability not support,
Source and target cells use different antennas)
Local Cell ID
Local Cell ID
Alarm Impact
Minor
The target cell cannot share the power of the source cell, and the HSDPA services
of the target cell fail to expand.
System Actions
None
Possible Causes
The source cell of the power sharing group is not an R99 cell.
The HSDPA services are not enabled within 10 minutes after the target logical cell in the power
sharing group is established.
The license does not support power sharing.
13/11/2012 9:15
Fault Management
462 de 526
Procedure
1. Locate the cause of alarm on the M2000.
a. Locate the cause of alarm based on the alarm location information.
If "Specific Problem" is "The source cell is not an R99 cell", go to step 2.
If "Specific Problem" is "The target cell is not a DPA cell", go to step 3.
If "Specific Problem" is "License capability limited", go to step 4.
If "Specific Problem" is "Source and target cells use different antennas", go to step 5.
2. Check that the HSDPA services are disabled in the source cell.
a. On the RNC, run the MML command LST UCELLHSDPA and check whether the query
result contains the information about the source cell.
Y => The query result contains the information about the source cell. Go to sub-step b.
N => The query result does not contain the information about the source cell. Contact
Huawei Customer Service Center.
b. On the RNC, run the MML command LST UCELLHSDPA to check whether the status
of the HSDPA services is ACTIVATED.
Y => The status of the HSDPA services is ACTIVATED. Go to sub-step c.
N => The status of the HSDPA services is not ACTIVATED. Contact Huawei Customer
Service Center.
c. On the RNC, run the MML command DEA UCELLHSDPA to disable the HSDPA
services of the source cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Check that the HSDPA services are enabled in the target cell.
a. On the RNC, run the MML command LST UCELLHSDPA and check whether the query
result contains the information about the target cell.
Y => The query result contains the information about the target cell. Go to sub-step b.
N => The query result does not contain the information about the target cell. Go to
sub-step c.
b. On the RNC, run the MML command LST UCELLHSDPA to check whether the status
of the HSDPA services is DEACTIVATED.
Y => The status of the HSDPA services is DEACTIVATED. Go to sub-step d.
N => The status of the HSDPA services is not DEACTIVATED. Contact Huawei
Customer Service Center.
c. On the RNC, run the MML command ADD UCELLHSDPA to add the HSDPA services
for the target cell.
d. On the RNC, run the MML command ACT UCELLHSDPA to enable the HSDPA
services for the target cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
463 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
4. Remotely check whether the license supports power sharing.
a. Run the MML command DSP LICENSE on the LMT to check whether the license
supports power sharing.
Y => The license supports power sharing. Contact Huawei Customer Service Center.
N => The license does not support power sharing. Go to sub-step b.
b. Configure a new license for the NodeB on the M2000 side. For details, see the online
help of ALM-26811 Configured Capacity Limit Exceeding Licensed Limit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Remotely check whether the antenna configuration supports power sharing.
a. Run the MML command LST LOCELL on the LMT to query the cell carrier information.
Check whether the source and target cells have the same settings of transmit channels.
Y => Same. Go to sub-step h.
N => Different. Go to sub-step b.
b. On the RNC, run the MML command DEA UCELL to deactivate the cell.
c. Run the MML command RMV PAGRP to remove the power sharing relationship
between the original cell and target cell.
d. Run the MML command RMV LOCELL to remove the original cell and target cell
respectively.
e. Run the MML command ADD LOCELL to add the source cell and target cell
respectively, in which the TX channels for carriers of the source cell and target cellmust
be consistent.
f. Run the MML command ADD PAGRP to add the power sharing relationship between
the source cell and target cell.
g. On the RNC, run the MML command ACT UCELL to activate the cell.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step h.
h. Run the MML command LST LOCELL on the LMT to check whether the source and
target cells have the same settings of transmit diversity.
Y => Same. Contact Huawei Customer Service Center.
N => Different. Go to sub-step i.
i. Run the MML command MOD LOCELL on the LMT to modify the settings of transmit
diversity so that the source and target cells have the same settings of transmit diversity.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
464 de 526
Parameters
Parameter
Name
Cause
Parameter Description
(Cell No Receive Radio link Setup Message, Cell No Receive Radio link Setup Message with
First Rls Flag for Long Time, Baseband Uplink Channel Soft Fault, Downlink Baseband
Resource Fault, High Error Rate of IUB Transmission, Radio link Setup Fail, Others)
Alarm Impact
Minor
Services of the current cell are affected and system self-healing fails.
System Actions
None
Possible Causes
NodeB hardware is faulty.
NodeB software is defective.
A NodeB component experiences a soft failure.
A third-party device, such as the antenna system, TMA, trunk amplifier, or transmission relay, is
faulty.
The parameter settings for the cell are incorrect on the NodeB or RNC.
On occasions such as public holidays or termination of large-scale gatherings, this alarm may be
reported with the alarm cause 0 or 1.
Procedure
1. Check for correlated Board alarms on the M2000.
a. Check for the correlated alarm on the M2000.
Y => The correlated alarm exists. Go to step 2.
N => The correlated alarm does not exist. Go to step 5.
2. Check the type of the board alarm on the M2000.
a. If the alarm 26200 Board Hardware Fault or 26532 RF Unit Hardware Fault is reported,
go to step 3.
b. If the 26203 Board Software Program Error or 26533 RF Unit Software Program Error
is reported, go to step 4.
3. On the M2000, check the type and status of the board where the correlated hardware alarm is
reported.
a. Run the MML command DSP BRD on the M2000 to display the type of the board
where the alarm is reported. Check whether the displayed board type is an RF board
and the MML command RST BRDPWROFF has not been executed on the RF board
within 2 hours before the alarm was reported.
Y => Run the MML command RST BRDPWROFF on the M2000 to power cycle the RF
13/11/2012 9:15
Fault Management
465 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
13/11/2012 9:15
Fault Management
466 de 526
Subrack No.
Slot No.
Type
(UpLink, DownLink)
Cause
Board Type
Alarm Impact
Minor
The services carried by the cell configured with incorrect frequency separation may
be affected. In this case, the KPIs related to network performance may deteriorate.
System Actions
None
Possible Causes
The data configuration is wrong.
Procedure
1. Check the frequency configuration of the cell on the M2000.
a. On the NodeB side, run the MML command LST LOCELL to query the parameters "UL
Frequency Channel Number" and "DL Frequency Channel Number" of the local cell that
is carried by the RF unit with incorrect frequency configuration. Check whether the cell
frequency configuration is consistent with the network planning.
Y => The cell frequency configuration is consistent with the network planning. Go to
step 2.
N => The cell frequency configuration is inconsistent with the network planning. Go to
sub-step b.
b. On the NodeB side, run the MML command DSP LOCELL to query the ID of the logic
cell corresponding to the local cell that is carried by the RF unit with incorrect frequency
configuration.
c. On the RNC side, run the MML command DEA UCELL to deactivate the logic cell.
Then, run the MML command MOD UCELLFREQUENCY to change the cell
frequencies. Ensure that the frequency configuration is consistent with the network
planning.
d. On the NodeB side, run the MML command MOD LOCELL to change the frequencies
of the local cell. Ensure that the frequency configuration is consistent with the network
planning.
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 frequency bandwidth on the M2000.
a. Run the MML command LST FREQBWH to query the parameter "Frequency
Bandwidth" of the RF unit. Check whether the cell frequency separation of the RF unit is
13/11/2012 9:15
Fault Management
467 de 526
Parameters
Parameter
Name
Parameter Description
Local Cell ID
Local Cell ID
Specific
Problem
Alarm Impact
Major
System Actions
None.
Possible Causes
The RF unit which carries the services in the local cell does not support the uplink or downlink
ARFCN of the local cell.
The uplink and downlink ARFCNs of the local cell conflict with ARFCNs of a cell in another mode.
The total maximum transmit power of faulty local cells and other local cells exceeds the maximum
13/11/2012 9:15
Fault Management
468 de 526
Procedure
1. Locate the alarm cause on the M2000.
a. Identify the alarm cause based on alarm location information.
If "Specific Problem" is "Uplink Frequency Configured Failure" or "Downlink Frequency
Configured Failure", go to step 2.
If "Specific Problem" is "Cell Power Exceeded RF Unit Power Specification", go to step
5.
2. Remotely check whether the RF unit used by the sector supports the ARFCNs configured in the
local cell.
a. Run the MML command LST LOCELL to query the information about the uplink and
downlink ARFCNs configured in the local cell.
b. Run the MML command DSP TXBRANCH and DSP RXBRANCH to query the maximum
and minimum ARFCNs supported by the RF unit in the uplink and downlink.
c. Check whether the uplink and downlink ARFCNs configured in the local cell are within
the allowed ARFCN range of the RF unit.
Y => Both the uplink and downlink ARFCNs are in the allowed ARFCN range of the RF
unit. Contact Huawei Customer Service Center.
N => The uplink or downlink ARFCN is not in the allowed ARFCN range of the RF unit.
Go to step 3.
3. Remotely check whether the uplink or downlink ARFCN is consistent with that in network planning.
a. Check whether the uplink or downlink ARFCN is consistent with that in network planning.
Y => Both the uplink and downlink ARFCNs are consistent with those in network
planning. Go to sub-step b.
N => Either the uplink or downlink ARFCN is inconsistent with that in network planning.
Go to step 4.
b. Check whether the RF unit is properly installed.
Y => The RF unit is properly installed. Contact Huawei Customer Service Center.
N => The RF unit is improperly installed. Go to sub-step c.
c. Replace the RF unit on site.
Replace the RF unit.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
4. Remotely modify the uplink or downlink ARFCN configured in the local cell.
a. Run the MML command DEA UCELL on the RNC side to deactivate the logical cell
corresponding to the local cell.
b. Run the MML command MOD LOCELL on the NodeB side to modify the uplink or
downlink ARFCN configured in the local cell to ensure that both the uplink and downlink
ARFCNs are consistent with those in network planning.
c. Run the MML command MOD UCELLFREQUENCY on the RNC side to modify the
uplink or downlink ARFCN to ensure that the uplink and downlink ARFCNs configured in
13/11/2012 9:15
Fault Management
469 de 526
the logical cell are consistent with those configured in the local cell.
d. Run the MML command ACT UCELL on the RNC side to activate the logical cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Check that the maximum transmit power of the local cell conforms to the network plan on the
M2000.
a. Run the MML command LST LOCELL to query the maximum transmit power of the
faulty local cell.
b. Check whether the maximum transmit power of the local cell conforms to the network
plan.
Note: For a multi-mode RF unit, the maximum transmit power is shared by multiple
modes. If multiple local cells share the transmit channel of one RF unit, the power of the
transmit channel is shared by the local cells. The maximum transmit power of the RF
unit may be restricted to the hardware and the power lock of the RF unit.
Y => The maximum transmit power of the local cell conforms to the network plan. Go to
step 7.
N => The maximum transmit power of the local cell does not conform to the network
plan. Go to step 6.
6. Change the maximum transmit power of the local cell based on the network plan on the M2000.
a. For a cell that has been activated, run the MML command DEA UCELL on the RNC to
deactivate the cell.
b. On the NodeB, run the MML command MOD LOCELL to change the information about
the maximum transmit power of the local cell to ensure that the total maximum transmit
power of all local cells on a transmit channel of an RF unit does not exceed the
maximum transmit power of the RF unit. In addition, the maximum transmit power of the
local cell cannot be smaller than the transmit power specified in the network plan.
c. On the RNC, run the MML command MOD UCELL to change the cell power information
to ensure that the maximum transmit power conforms to the network plan and the
power does not exceed the maximum transmit power of the local cell.
d. On the RNC, run the MML command ACT UCELL activate the cell.
Check whether the alarm is cleared.
Y => The alarm is cleared and is not reported again. No further action is required.
N => The alarm is not cleared or is reported again. Contact Huawei Customer Service
Center.
7. Replace the original RF unit with an RF unit with the larger maximum transmit power onsite.
a. Replace the original RF unit with an RF unit with the larger maximum transmit power to
ensure that the total maximum transmit power of all local cells on a transmit channel of
an RF unit does not exceed the maximum transmit power of the RF unit.
Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
470 de 526
Parameters
Parameter Name
Parameter Description
Local Cell ID
Local Cell ID
Alarm Impact
Minor
When a IMB local cell is blocked, the cell cannot carry services.
System Actions
None
Possible Causes
The user runs a command to block the IMB local cell of the NE.
Procedure
1. Block the IMB local cell on the M2000.
a. Run the MML command UBL LOCELL to block the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Name
Parameter Description
Alarm Impact
13/11/2012 9:15
Fault Management
471 de 526
Alarm Severity
Alarm Impact
Major
System Actions
None
Possible Causes
The baseband board is faulty.
The RF unit is faulty.
Data configuration is incorrect.
Baseband resources are insufficient.
License capability not enough.
Procedure
1. Locate the cause of alarm on the M2000.
a. Locate the cause of alarm based on the alarm location information.
If "Specific Problem" is "Downlink baseband resource unavailable", go to step 2.
If "Specific Problem" is "Baseband-RF interface resource unavailable", go to step 3.
If "Specific Problem" is "Downlink RF resource unavailable", go to step 4.
2. Rectify the fault of downlink baseband resources on the M2000.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the downlink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28301 Board Downlink Service Processing Channel Abnormal
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
13/11/2012 9:15
Fault Management
472 de 526
c. Run the MML command LST IMBLOCELL to query the IMB local cell information ("DL
BB Resource Group No."), and then run the MML command LST DLGROUP to query
the information about the downlink resource group used by the IMB local cell.
d. Run the MML command DSP BBPTC to query the number of cells supported by the
board in the downlink resource group.
e. Check whether the number of cells configured in the downlink resource group exceeds
the total number of cells allowed by the downlink resource group. The total number of
cells allowed by the downlink resource group is the accumulated value of the number of
cells supported by all boards in the downlink resource group and cannot exceed the
maximum number of cells allowed by the downlink resource group. For details about the
cell specification supported by the board, see the related hardware description.
Y => The number of cells configured for the downlink resource group exceeds the total
number of cells supported by the downlink resource group. Go to sub-step f.
N => The number of cells configured for the downlink resource group does not exceed
the IMB total number of cells supported by the downlink resource group. Contact
Huawei Customer Service Center.
f. Use either of the following methods to modify the configuration:
Method 1: Run the MML command RMV IMBLOCELL to delete the IMB local cell
whose resources are unavailable, and then run the MML command ADD IMBLOCELL
to establish a IMB local cell in another downlink resource group that has sufficient
resources.
Method 2: Add the WBBP, and then run the MML command MOD DLGROUP to add
the WBBP to the downlink resource group where the IMB local cell resides.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Rectify the fault of baseband and RF interface resources on the M2000.
a. Run the MML command LST IMBLOCELL to query the information about the RRU
configured for the IMB local cell, and then run the MML commands LST RRU and LST
RRUCHAIN to query the information about the interface board configured for the RRU.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the interface board-related alarms exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step c.
13/11/2012 9:15
Fault Management
473 de 526
N => The alarms do not exist. Contact Huawei Customer Service Center.
c. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
4. Rectify the RF resource fault on the M2000.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the alarms related to the RRU or RFU exist.
26210 Board Blocked
26235 RF Unit Maintenance Link Failure
26237 RRU Network Breakpoint
26524 RF Unit PA Overcurrent
26525 RF Unit Temperature Unacceptable
26529 RF Unit VSWR Threshold Crossed
26532 RF Unit Hardware Fault
26538 RF Unit Clock Problem
26545 RF Unit TX Channel Switched Off Through Command
26765 RHUB Hardware Fault
26768 RHUB Clock Problem
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Run the MML command LST IMBLOCELL to query the information about the IMB local
cell, such as the RRU or RFU used in the local cell, uplink and downlink UARFCNs, and
maximum output power.
d. Run the MML command DSP RRU to query the specifications of the RRU or RFU.
e. Check whether the u downlink frequencies configured in the local cell are within the
permissible frequency range of the RRU or RFU. (The conversion formula between
UARFCNs and actual frequencies is available in the help information of the MML
command ADD IMBLOCELL.)
Y => Go to sub-step g.
N => Go to sub-step f.
f. Run the MML command MOD IMBLOCELL to change the frequency of the local cell to
a value within the frequency range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Check whether the frequency spacing between the current IMB local cell and any of the
13/11/2012 9:15
Fault Management
474 de 526
other IMB local cells established on the RRU or RFU exceeds the allowed bandwidth of
the RRU or RFU (Minimum frequency spacing = 3.8 MHz; Maximum downlink frequency
spacing = TxUnitNo 0 Support Band Width - 3.8 MHz).
Y => The frequency spacing between the current IMB local cell and any of the other
IMB local cells established on the RRU or RFU exceeds the allowed bandwidth of the
RRU or RFU. Go to sub-step h.
N => The frequency spacing between the current IMB local cell and any of the other
IMB local cells established on the RRU or RFU does not exceed the allowed bandwidth
of the RRU or RFU. Go to sub-step i.
h. Run the MML command MOD IMBLOCELL to modify the frequency of the IMB local
cell to ensure that its frequency spacing with the other cells is within the range
supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step i.
i. Check whether the number of cells configured on the same RRU or RFU exceeds the
number of carriers supported by the RRU/RFU.
Y => The number of cells configured on the same RRU or RFU exceeds the number of
carriers supported by the RRU or RFU. Go to sub-step j.
N => The number of cells configured on the same RRU or RFU does not exceed the
number of carriers supported by the RRU or RFU. Go to sub-step k.
j. Run the MML command RMV IMBLOCELL to delete the IMB local cell whose
resources are unavailable, and then run the MML command ADD IMBLOCELL to
establish a IMB local cell on another resource group that has sufficient resources.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step k.
k. Check whether the maximum power configured in the IMB local cell is within the power
range supported by the RRU or RFU.
Y => The maximum power configured in the IMB local cell is out of the power range
supported by the RRU or RFU. Go to sub-step l.
N => The maximum power configured in the IMB local cell is within the power range
supported by the RRU or RFU. Go to sub-step m.
l. Run the MML command MOD IMBLOCELL to change the maximum transmit power of
the IMB local cell to a value within the power range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step m.
m. Run the MML command LST RRU to obtain the information about the RRU or RFU
configured on the same chain/ring. Run the MML command LST IMBLOCELL to obtain
the number of cells configured for the same RRU or RFU. Run the MML command DSP
SFP to obtain the transmission rate of the optical module. If the transmission rate is
1.25 Gbit/s, the CPRI interface supports only 8 IMB local cells. If the transmission rate
is 2.5 Gbit/s, the CPRI interface supports only 16 IMB local cells . Check whether the
allowed number of local cells on a chain/ring exceeds the number of IMB local cells
corresponding to the transmission rate on the chain/ring.
13/11/2012 9:15
Fault Management
475 de 526
Y => The allowed number of local cells on a chain/ring exceeds the number of IMB local
cells corresponding to the transmission rate on the chain/ring. Go to sub-step n.
N => The allowed number of local cells on a chain/ring does not exceed the number of
IMB local cells corresponding to the transmission rate on the chain/ring. Contact Huawei
Customer Service Center.
n. Run the MML command RMV IMBLOCELL to delete the IMB local cell whose
resources are unavailable, and then run the MML command ADD IMBLOCELL to
establish a IMB local cell on another RRU or RFU that has sufficient resources on the
chain/ring.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step o.
o. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
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 5.
5. Replace the RRU on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Local Cell ID
Local Cell ID
Cabinet No.
Subrack No.
Slot No.
Alarm Impact
Minor
The decrease in the NE output power causes a reduction in the cell coverage.
System Actions
None
13/11/2012 9:15
Fault Management
476 de 526
Possible Causes
The RRU is faulty or aged.
Procedure
1. Reset the RRU on the M2000.
a. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is reported again. Go to step 2.
2. Replace the RRU on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Name
Parameter Description
Cause
(Some RRU(s) in the iDBS cell not usable, Number of occupied BBU CPRI ports connected to
RRUs in the iDBS cell exceeding six, RRU transmit power less than the transmit power required
by the local cell, Two TX channels not supported by the cell, Uplink 16QAM not supported by the
cell, Uplink L2+ not supported by the cell, Downlink 64QAM+MIMO not supported by the cell,
FDE not supported by the cell, IC not supported by the cell, DC not supported by the cell,
BOOST not supported by the cell, DCMIMO not supported by the cell, ERACH not supported by
the cell, MultiRRU Independ DemOver Cell not supported by WBBP Board, Cell can't use all
WBBP Board resources of the uplink resource group, ACT and DEA of Slave Carrier not
supported by the cell, Anti-Interference Scheduling for HSUPA not supported by the cell)
Local Cell
ID
Local Cell ID
Alarm Impact
Major
The coverage of the faulty local cell decreases, the RTWP reported by some RRUs
is discarded, the features configured on the local cell are not supported, or certain
demodulation capabilities of the uplink resource group used by the local cell are
13/11/2012 9:15
Fault Management
477 de 526
Alarm Severity
Alarm Impact
unavailable.
System Actions
None
Possible Causes
Redundant RRUs are configured in the IMB local cell.
A certain RRU in the IMB local cell is faulty.
The number of occupied BBU CPRI ports connected to RRUs in the IMB local cell exceeds six, the
maximum number defined in the system.
A logical cell exists, and the maximum TX power of the IMB local cell exceeds the maximum output
power of RRUs.
The parameter settings are incorrect in the local cell.
The baseband resources are insufficient.
Due to limited capabilities of ports interconnecting baseband boards, certain demodulation
capabilities of the uplink resource group used by the local cell are unavailable.
Procedure
1. Locate the cause of alarm on the M2000.
a. Locate the cause of alarm based on the alarm location information.
If "Specific Problem" is "Some RRU(s) in the cell not usable", go to step 2.
If "Specific Problem" is "Number of occupied BBU CPRI ports connected to RRUs in the
iDBS cell exceeding six", go to step 4.
If "Specific Problem" is "RRU transmit power less than the transmit power required by
the IMB local cell", go to step 5.
2. Check for redundant RRUs configured in the local cell on the M2000.
a. Run the MML command LST IMBLOCELL to check the RRUs configured in the faulty
IMB local cell. Check whether redundant RRUs exist according to the network planning.
Y => Redundant RRUs exist. Go to sub-step b.
N => Redundant RRUs do not exist. Go to step 3.
b. Run the MML command RMV RRU to delete the redundant RRUs.
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 3.
3. Rectify the RRU fault on the M2000.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms. Check whether the RRUs configured in the faulty local cell are faulty.
Y => The RRUs are faulty. Go to sub-step b.
N => The RRUs are functional. Contact Huawei Customer Service Center.
b. Clear the correlated alarm according to the relevant handling suggestions.
13/11/2012 9:15
Fault Management
478 de 526
Parameters
Parameter
Name
Parameter Description
Local Cell ID
Local Cell ID
13/11/2012 9:15
Fault Management
479 de 526
Specific
Problem
Alarm Impact
Major
System Actions
None.
Possible Causes
The RF unit which carries the services in the IMB(Integrated Mobile Broadcast) local cell does not
support the uplink or downlink ARFCN of the local cell.
The uplink and downlink ARFCNs of the local cell conflict with ARFCNs of a cell in another mode.
The total maximum transmit power of faulty local cells and other local cells exceeds the maximum
transmit power of the RF unit.
Procedure
1. Locate the alarm cause on the M2000.
a. Identify the alarm cause based on alarm location information.
If "Specific Problem" is "Downlink Frequency Configured Failure", go to step 2.
If "Specific Problem" is "Cell Power Exceeded RF Unit Power Specification", go to step
5.
2. Remotely check whether the RF unit used by the sector supports the ARFCNs configured in the IMB
local cell.
a. Run the MML command LST IMBLOCELL to query the information about the sector to
which the IMB local cell belongs and information about the uplink and downlink ARFCNs
configured in the IMB local cell.
b. Run the MML command LST IMBSEC to query the configuration information of the RF
unit used by the sector.
c. Run the MML command DSP TXBRANCH to query the maximum and minimum
ARFCNs supported by the RF unit in the downlink.
d. Check whether the downlink ARFCNs configured in the IMB local cell are within the
allowed ARFCN range of the RF unit.
Y => Both the downlink ARFCNs are in the allowed ARFCN range of the RF unit.
Contact Huawei Customer Service Center.
N => The downlink ARFCN is not in the allowed ARFCN range of the RF unit. Go to
step 3.
3. Remotely check whether the uplink or downlink ARFCN is consistent with that in network planning.
a. Check whether the downlink ARFCN is consistent with that in network planning.
Y => Both the downlink ARFCNs are consistent with those in network planning. Go to
sub-step b.
N => Either the downlink ARFCN is inconsistent with that in network planning. Go to
13/11/2012 9:15
Fault Management
480 de 526
step 4.
b. Check whether the RF unit is properly installed.
Y => The RF unit is properly installed. Contact Huawei Customer Service Center.
N => The RF unit is improperly installed. Go to sub-step c.
c. Replace the RF unit on site.
Replace the RF unit.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
4. Remotely modify the uplink or downlink ARFCN configured in the local cell.
a. Run the MML command DEA UCELL on the RNC side to deactivate the logical cell
corresponding to the local cell.
b. Run the MML command MOD IMBLOCELL on the NodeB side to modify the downlink
ARFCN configured in the IMB local cell to ensure that both the downlink ARFCNs are
consistent with those in network planning.
c. Run the MML command MOD IMBLOCELL on the RNC side to modify the downlink
ARFCN to ensure that the downlink ARFCNs configured in the logical cell are consistent
with those configured in the IMB local cell.
d. Run the MML command ACT UCELL on the RNC side to activate the logical cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Check that the maximum transmit power of the local cell conforms to the network plan on the
M2000.
a. Run the MML command LST LOCELL to query the maximum transmit power of the
faulty local cell.
b. Check whether the maximum transmit power of the local cell conforms to the network
plan.
Note: For a multi-mode RF unit, the maximum transmit power is shared by multiple
modes. If multiple local cells share the transmit channel of one RF unit, the power of the
transmit channel is shared by the local cells. The maximum transmit power of the RF
unit may be restricted to the hardware and the power lock of the RF unit.
Y => The maximum transmit power of the local cell conforms to the network plan. Go to
step 7.
N => The maximum transmit power of the local cell does not conform to the network
plan. Go to step 6.
6. Change the maximum transmit power of the local cell based on the network plan on the M2000.
a. For a cell that has been activated, run the MML command DEA UCELL on the RNC to
deactivate the cell.
b. On the NodeB, run the MML command MOD LOCELL to change the information about
the maximum transmit power of the local cell to ensure that the total maximum transmit
power of all local cells on a transmit channel of an RF unit does not exceed the
maximum transmit power of the RF unit. In addition, the maximum transmit power of the
local cell cannot be smaller than the transmit power specified in the network plan.
13/11/2012 9:15
Fault Management
481 de 526
c. On the RNC, run the MML command MOD UCELL to change the cell power information
to ensure that the maximum transmit power conforms to the network plan and the
power does not exceed the maximum transmit power of the local cell.
d. On the RNC, run the MML command ACT UCELL activate the cell.
Check whether the alarm is cleared.
Y => The alarm is cleared and is not reported again. No further action is required.
N => The alarm is not cleared or is reported again. Contact Huawei Customer Service
Center.
7. Replace the original RF unit with an RF unit with the larger maximum transmit power onsite.
a. Replace the original RF unit with an RF unit with the larger maximum transmit power to
ensure that the total maximum transmit power of all local cells on a transmit channel of
an RF unit does not exceed the maximum transmit power of the RF unit.
Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
None.
Alarm Impact
Minor
The hardware capability is insufficient. Some terminals cannot use the services
provided by the network.
System Actions
None
Possible Causes
The NodeB receives calls too frequently and its signaling capability cannot handle.
The NodeB serves too many online users and its hardware cannot provide adequate uplink or
downlink CEs.
Procedure
1. Query the service overload alarm threshold on the M2000.
a. Run the MML command LST TRAFFICOVERLOADTHD to query the service overload
alarm threshold.
Check whether the service overload alarm threshold is set properly.
13/11/2012 9:15
Fault Management
482 de 526
Y=> The service overload alarm threshold is set properly. Contact Huawei Customer
Service Center to implement capacity expansion.
N=> The service overload alarm threshold is not set properly. Go to step 2.
2. Set the service overload alarm threshold on the M2000.
a. Run the MML command SET TRAFFICOVERLOADTHD. Set the service overload
alarm threshold based on service characteristics.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center to implement
capacity expansion.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Minor
The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The hardware of the GPS receiver is faulty.
Procedure
1. Reset the GPS receiver on the M2000.
a. Run the MML command RST SATCARD to reset the GPS receiver.
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. Replace the GPS receiver on site.
a. Replace the GPS receiver.
13/11/2012 9:15
Fault Management
483 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Minor
The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The power supply loop of the antenna of the GPS receiver is faulty.
Procedure
1. Wait for five minutes, and then check that the system can automatically clear the alarm.
a. Wait for five minutes. Then, check whether the system automatically clears the alarm.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Reset the GPS receiver on the M2000.
a. Run the MML command RST SATCARD to reset the GPS receiver.
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 3.
3. Replace the GPS receiver on site.
a. Replace the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
13/11/2012 9:15
Fault Management
484 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific Problem
Alarm Impact
Minor
The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The antenna system of the GPS receiver is not properly connected or is short-circuited.
The GPS receiver itself is faulty.
Procedure
1. Locate the cause of the alarm on the M2000.
a. Locate the cause of the alarm based on the alarm location information.
If "Specific Problem" is "Antenna Shorted", go to step 2.
If "Specific Problem" is " Antenna Open", go to step 4.
2. Disconnect the antenna system from the GPS receiver on site, and then wait for five minutes to
check that the alarm is cleared.
a. Disconnect the feeder at the antenna connector of the GPS receiver, and then wait for
five minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. The antenna system is faulty. Go to step 3.
N => The alarm is not cleared. The GPS receiver itself is faulty. Go to step 6.
3. Clear the fault in the antenna system on site.
a. Check the antenna system. Clear the fault of short circuit if any.
13/11/2012 9:15
Fault Management
485 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
13/11/2012 9:15
Fault Management
486 de 526
Specific
Problem
Specific Problem of the alarm(Position Solution Invalid, Clock Steering Disabled, Clock Model
Invalid, Almanac Invalid)
Alarm Impact
Minor
The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The calendar of the GPS receiver is invalid.
The GPS receiver itself is faulty.
The system mistakenly executes some commands.
Software error occurs in the GPS receiver.
Procedure
1. Wait for five minutes, and then check that the system can automatically clear the alarm.
a. Wait for five minutes. Then, check whether the system automatically clears the alarm.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Reset the GPS receiver on the M2000.
a. Run the MML command RST SATCARD to reset the GPS receiver.
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 3.
3. Replace the GPS receiver on site.
a. Replace the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
13/11/2012 9:15
Fault Management
487 de 526
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Minor
The GPS receiver cannot lock the satellite. The NodeB fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
The GPS receiver is automatically searching for a satellite.
The auto-search function of the GPS receiver fails.
Procedure
1. Check that the GPS receiver is automatically searching for a satellite on the M2000.
a. Run the MML command LST GPS to list the preset search duration of the GPS
receiver.
Wait for some time. Then, check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
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. Reset the GPS receiver on the M2000.
a. Run the MML command RST SATCARD to reset the GPS receiver.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
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 3.
3. Replace the GPS receiver on site.
a. Replace the GPS receiver.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
13/11/2012 9:15
Fault Management
488 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Minor
The NodeB cannot receive the valid GPS data and thus fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
The cable connections between the NodeB and the GPS receiver are faulty.
The GPS receiver itself is faulty.
Procedure
1. Check that the GPS receiver is properly connected to the NodeB on site.
a. Check whether the GPS receiver is properly connected to the NodeB. If necessary,
reconnect the cables properly between the NodeB and the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the cables between the NodeB and the GPS receiver.
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. Replace the GPS receiver on site.
a. Replace the GPS receiver.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
489 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Minor
The NodeB cannot receive the valid GPS data and thus fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
Software error occurs in the GPS receiver.
Procedure
1. Reset the GPS receiver on the M2000.
a. Run the MML command RST SATCARD to reset the GPS receiver.
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. Replace the GPS receiver on site.
a. Replace the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
490 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
The transmission link is disconnected, and the ongoing services carried on the link
are disrupted.
System Actions
The system attempts to select another route.
Possible Causes
The network transmission is faulty.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm of the faulty board on the M2000:
25880 Ethernet Link Fault
25895 Ethernet Trunk Group Fault
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.
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 that the network transmission is normal on the M2000.
a. Run the MML command CFMTRACE to perform a loopback test at the ends of the
disconnected link and check whether the loopback test is successful.
Y => The test is successful. Contact the maintenance personnel of the transport
network.
N => The test fails. Go to sub-step b.
b. Contact the maintenance personnel of the transport network to obtain the networking
configuration, and then run the MML command CFMTRACE to perform a loopback test
at the ends of the disconnected link and NodeB and check whether each
MIP(Maintenance Intermediate Point).
13/11/2012 9:15
Fault Management
491 de 526
Y => All the MIPs are reachable. Contact Huawei Customer Service Center.
N => Certain MIPs are unreachable. Contact the maintenance personnel of the
transport network.
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Transmission
Object Type
(Ethernet Port, Device IP Address, IP Path, Local IP, OM Channel, IP Route, E1/T1,
Resource Group, PPP Link, MLPPP Group, MLPPP Link, IP PM Session, IMA Group, IMA
Link, AAL2 Node, AAL2 Path, VCG, SAAL Link, Ethernet Trunk Group, SCTP Link, UNI Link,
Tree Link PVC, Fractional ATM Link, IP to Resource Group Mapping, Line Rate, HSDPA Flow
Control Para, Ethernet Trunk Link, BFD Session, CFM MA, CFM MEP, CFM Remote MEP,
CFM Binding IP, Timeslot Cross, STM-1, HSUPA Flow Control Para, CFM MD, TUNNEL,
Service IP)
Board Type
Fault Code
Fault Code
Object No.
Object No.
Alarm Impact
Major
The transport object for which this alarm is generated is unavailable and the ongoing
services carried on the transport object are disrupted.
System Actions
The transport object cannot carry any upper layer objects.
Possible Causes
The base station is in BOOTP state.
The hardware of the board is faulty.
The license capacity is lower than the system configuration.
The configuration data planning is incorrect.
Procedure
1. Check for the correlated alarm on the M2000.
a. Check for the correlated alarm on the M2000:
13/11/2012 9:15
Fault Management
492 de 526
13/11/2012 9:15
Fault Management
493 de 526
Description
This alarm is reported when uplink service processing channel of a board is faulty.
Parameters
Parameter
Name
Parameter Description
Slot No.
Specific Problem of the alarm(Dedicated Channel Demodulation Unit 1 Faulty, Access Channel
Demodulation Unit Faulty, AI Data Transmission Failure, DSP BFN Abnormal, APP Measurement
Failure, CHIP Register Configuration Abnormal, CPU-DSP Coding Unit Interface Frame Error,
SIR Data Transmission Failure, DSP Timing Interrupt Abnormal, DSP Peripheral Equipment
Abnormal, DSP External Interface Abnormal, CHIP Register Configuration Abnormal, DSP-Chip
Interrupt Timeout, PRBUS Interface Abnormal, Chip BFN Abnormal, DSP Kernel Abnormal, CPU
and DSP Disconnected, Decoding Module Internal Error, Decoding Module External Interface
Abnormal, ARM Disconnected, Dedicated Channel Demodulation Unit 0 Faulty)
Alarm Impact
Major
The faulty uplink resources are unavailable, resulting in decreased system capacity
or service interruption.
System Actions
When this alarm is generated, the system sets the corresponding uplink processing channel as unavailable
according to the fault code reported. If other uplink resources are available in the baseband subrack, the
services carried by the uplink processing channel are migrated to another uplink resource. If other uplink
resources are unavailable or the uplink processing channel becomes unavailable due to service migration failure,
the cells carried by the uplink processing channel become unavailable. In this case, the system automatically
notifies the RNC that the local cells are unavailable.
Possible Causes
The uplink dedicated demodulation channel, access demodulation channel, or encoding channel is faulty.
Procedure
1. Reset the faulty board on the M2000.
a. Note: Resetting the board disrupts some or even 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 board.
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.
13/11/2012 9:15
Fault Management
494 de 526
Parameters
Parameter
Name
Parameter Description
Slot No.
Specific Problem of the alarm(CHIP Register Configuration Abnormal, Power Control Interface
from FPGA to DL ASIC Abnormal, Modulation Interface from DL ASIC to FPGA Abnormal, DSP
Internal Error, Downlink Service Processing Unit Faulty, CHIP Register Configuration Abnormal,
DSP Kernel Abnormal, DSP Internal Abnormal, DSP External Interface Abnormal, Chip External
Interface Abnormal, CPU and DSP Disconnected, PRBUS Interface Abnormal, ARM
Disconnected, RTWP Channel Abnormal, Downlink Resource Coding Abnormal, PGBUS
Interface Abnormal, CPU-DSP Coding Unit Interface Frame Error)
Alarm Impact
Major
Minor
The faulty downlink resources are unavailable. The system still has resources that
are working normally. The system capacity decreases.
System Actions
When this alarm is generated, the system sets the corresponding downlink processing channel as unavailable
according to the fault code reported. If other downlink resources are available in the baseband subrack, the
services carried by the downlink processing channel are migrated to another downlink resource. If other
downlink resources are unavailable or the downlink processing channel becomes unavailable due to service
migration failure, the cells carried by the downlink processing channel become unavailable. In this case, the
system automatically notifies the RNC that the local cells are unavailable.
Possible Causes
13/11/2012 9:15
Fault Management
495 de 526
Procedure
1. Reset the faulty board on the M2000.
a. Note: Resetting the board disrupts some or even 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 board.
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. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Specific
Problem
Specific Problem of the alarm(Downlink DSP's ASIC Power Abnormal, BFN of the Decoding
Unit Abnormal, BFN of the Dedicated Channel Demodulation Unit 0 Abnormal, BFN of the
Access Channel Demodulation Unit Abnormal, BFN of the Encoding Unit Abnormal)
Alarm Impact
Major
Certain or all service resources of the faulty board are unavailable. The system
capacity decreases.
System Actions
When this alarm is generated, the system sets the corresponding service processing unit as unavailable
according to the fault code reported.
13/11/2012 9:15
Fault Management
496 de 526
Possible Causes
The board is not properly connected with the subrack.
Certain service processing units of the board are faulty.
Procedure
1. Reset the faulty board on the M2000.
a. Note: Resetting the board disrupts some or even 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 board.
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. Remove and reinstall the faulty board on site.
a. Reseat the Board.
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 3.
3. Replace the faulty board on site.
a. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 4.
4. Remove and reinstall the main control board on site.
a. Reseat the Board.
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 5.
5. Replace the main control board on site.
a. Replace the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Go to step 6.
6. Replace the BBU subrack on site.
a. Replace the subrack.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13/11/2012 9:15
Fault Management
497 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Alarm Impact
Major
Certain or all service resources of the faulty board are unavailable. The system
capacity decreases.
System Actions
The system sets the service data channel between the WBBPs as unavailable.
Possible Causes
The transmit board is faulty.
The receive board is faulty.
The BBU subrack is faulty.
Procedure
1. Reset the receive board on the M2000.
a. Note: Resetting the board disrupts some or even 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 receive board.
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. Remove and reinstall the receive board on site.
a. Reseat the Board.
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 3.
3. Replace the receive board on site.
a. Replace the board.
13/11/2012 9:15
Fault Management
498 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
Alarm Impact
Major
System Actions
None
Possible Causes
13/11/2012 9:15
Fault Management
499 de 526
Procedure
1. Reset the RRU on the M2000.
a. Run the MML command RST BRDPWROFF to reset the RRU module on which the
alarm is generated.
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 power supply of the RRU on site.
a. Check the power supply of the RRU for errors.
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 3.
3. Replace the RRU on site.
a. Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Board Type
VSWR (0.1)
VSWR (0.1)
Alarm Impact
Major
The uplink or downlink performance of the PRRU is degraded and the services
13/11/2012 9:15
Fault Management
500 de 526
Alarm Severity
Alarm Impact
carried by the PRRU may be interrupted.
System Actions
None
Possible Causes
The connection of the PRRU feeder is incorrect.
The reflected power detection circuit of the PRRU is faulty.
Procedure
1. Check the antenna feeder on site.
a. Check the Installation of Feeders for the RF Unit.
Wait for 10 minutes. 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.
Note: Only after the cell is reestablished, the PRRU starts to detect the reflected
power. Therefore, you need to wait for a longer time.
2. Replace the PRRU on site.
a. Replace the PRRU.
Wait for 10 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
Parameters
Parameter
Name
Cause
Parameter Description
(Uplink Process Unit Inconsistent with Uplink Resource Group Configuration, Downlink Process
Unit Inconsistent with Downlink Resource Group Configuration, This baseband board cannot
belong to multiple uplink resource groups)
13/11/2012 9:15
Fault Management
501 de 526
Alarm Severity
Alarm Impact
Major
If "Specific Problem" is "Uplink process unit inconsistent with uplink resource group
configuration" or "Downlink process unit inconsistent with downlink resource group
configuration", the services cannot be carried by the baseband processing resources
that are not added to a resource group. As a result, the baseband processing
capability is insufficient and the UE access is difficult. If "Specific Problem" is
"Baseband board not belonging to multiple UL resource groups", the baseband
processing resource is used by one of the UL group resources.
System Actions
None
Possible Causes
The UE configuration is incomplete. Not all the baseband processing resources are added to the resource group.
A certain board that cannot be added to multiple UL resource groups is added to multiple UL resource groups.
Procedure
1. Identify the cause of the alarm on the M2000.
a. Identify the cause of the alarm based on the alarm location information.
If "Specific Problem" is "Uplink process unit inconsistent with uplink resource group
configuration", go to step 2.
If "Specific Problem" is "Downlink process unit inconsistent with downlink resource
group configuration", go to step 3.
If "Specific Problem" is "Baseband board not belonging to multiple UL resource groups",
go to step 4.
2. Add all the uplink baseband processing resources to the uplink resource group on the M2000.
a. Run the MML command LST ULGROUP to query the configuration of the uplink
resource group. Run the MML command DSP BRD to query the status of the board and
determine whether there are any available uplink baseband processing resources that
are not added to the uplink resource group.
Y => Some available uplink baseband processing resources are not added to the uplink
resource group. Go to substep b.
N => All available uplink baseband processing resources are added to the uplink
resource group. Contact Huawei Customer Service Center.
b. Run the MML command MOD ULGROUP to add an idle baseband processing board to
the configured uplink baseband resource group (RGOPTYPE=ADDULPUNIT).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Add all the downlink baseband processing resources to the downlink resource group on the M2000.
a. Run the MML command LST DLGROUP to query the configuration of the downlink
resource group. Run the MML command DSP BRD to query the status of the board and
determine whether there are any available downlink baseband processing resources
that are not added to the downlink resource group.
Y => Some available downlink baseband processing resources are not added to the
13/11/2012 9:15
Fault Management
502 de 526
Parameters
Parameter
Name
Parameter Description
13/11/2012 9:15
Fault Management
503 de 526
Cabinet No.
Subrack No.
Slot No.
Cause
(Back-board not support, Board Type Mismatch, Board not support, Sub-board Type
Mismatch)
Board Type
Specific
Problem
Specific Problem of the alarm(Back-board not support, Board Type Mismatch, Board not
support, Sub-board Type Mismatch)
Alarm Impact
Major
The active/standby transmission is not supported, thus affecting the reliability of the
system transmission.
System Actions
None
Possible Causes
The backplane does not support the active/standby transmission.
The board types are inconsistent.
The board does not support the active/standby transmission.
The subboard does not support the active/standby transmission.
Procedure
1. Check the configuration data on the M2000.
a. Check the configuration data to determine whether the active/standby transmission
configuration is correct.
Y => The configuration is correct. Contact Huawei Customer Service Center.
N => The configuration is incorrect. Go to sub-step b.
b. Modify the Data Configuration File.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Parameter
Parameter Description
13/11/2012 9:15
Fault Management
504 de 526
Name
Specific
Problem
Specific Problem of the alarm(OAM configuration data illegal, Transport configuration data
illegal, Signal configuration data illegal)
Alarm Impact
Major
Some configuration data is illegal, or the NE cannot obtain the configuration data.
The NE has to operate with the default configuration data. In this case, the NE
cannot provide normal services.
System Actions
The NE operates with the default configuration data. If the transmission link is available but the IPoA channel
fails, the NE may start BOOTP.
Possible Causes
The configuration file does not exist.
The configuration file is illegal. For example, the file format is invalid or syntax errors exist in the file.
The flash is faulty.
Procedure
1. Upload the configuration file on the M2000.
a. Run the MML command ULD CFGFILE to upload the data configuration file from the
BBU. Enter the IP address of the FTP server according to the configuration of the FTP
server. Then, specify the destination path, user name, and password. Use the default
values for other parameters. Check whether the upload is successful based on the
command response.
Y => The upload is successful. Go to step 2.
N => The upload fails. The configuration file may be missing or the flash may be faulty.
Go to step 3.
2. Check the configuration file on the M2000.
a. Check whether the configuration file is correct. Ensure that the NE type and hardware
type in the file are consistent with the running data and that the file is in .xml format.
Y => The configuration file is correct. Go to step 3.
N => The configuration file is not correct. Go to sub-step b.
b. Modify the configuration file. Then, go to step 3.
3. Re-download the configuration file on the M2000.
a. Retrieve the correct configuration file or use the modified configuration file.
b. Run the MML command DLD CFGFILE to download the data configuration file to the
BBU. Enter the IP address of the FTP server according to the configuration of the FTP
server. Then, specify the source path, user name, and password.
c. Run the MML command SET CFGFILEENB (FLAG=ENABLE,
RSTMODE=IMMEDIATELY) to set the enabling flag of the downloaded data
configuration file.
13/11/2012 9:15
Fault Management
505 de 526
Parameters
Parameter
Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Cause
Board Type
Alarm Impact
Major
When the setting of the key parameters fails, the board becomes unavailable. When
13/11/2012 9:15
Fault Management
506 de 526
Alarm Severity
Alarm Impact
the setting of the unimportant parameters fails, the secondary functions of the board
cannot work properly. When the board cannot be started, the board fails to work
properly and the services carried by the board are interrupted.
System Actions
The system automatically disables the board when the setting of the key parameters fails or the board cannot
be started.
Possible Causes
The operation of reading or writing into the configuration fails.
Errors occur during data configuration on the board.
The board is operating improperly.
The startup of the board times out.
Procedure
1. Locate the cause of alarm on the M2000.
a. Locate the cause of alarm based on the alarm location information.
If "Specific Problem" is "Startup timeout", go to step 2.
If "Specific Problem" is "Key parameter config failure" or "Non-key parameter config
failure", go to step 4.
2. Check for the alarms indicating hardware failures and configuration failures of the board on the
M2000.
a. Check for the correlated alarm on the M2000:
26200 Board Hardware Fault
26532 RF Unit Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 3.
b. Clear the correlated alarm according to the relevant handling suggestions.
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 3.
3. Reset the board on the M2000.
a. Run the MML command RST BRD to reset the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
4. Download the configuration file from the M2000.
a. Modify the Data Configuration File.
Check whether the alarm is cleared.
13/11/2012 9:15
Fault Management
507 de 526
Parameters
Parameter Name
Parameter Description
Cabinet No.
Subrack No.
Slot No.
Port No.
Board Type
Specific Problem
Alarm Impact
Major
System Actions
None.
Possible Causes
In the case of the external analog device, the external analog alarm threshold is incorrect.
In the case of the external Boolean device, the external Boolean alarm enabling or signal level
configuration is incorrect.
The cable connection between the external analog equipment and the monitoring device is faulty.
The external analog equipment is faulty.
The corresponding monitoring device is faulty.
Procedure
1. Check the configuration on the M2000.
a. Check the external alarm is whether an external analog alarm or an external Boolean
alarm.
If the external analog alarm is defined, go to procedure b
If the external Boolean alarm is defined, go to step d
b. Run the MML command LST ALMPORT to check whether the threshold of the external
analog alarm or the alarm disable configuration and alarm valid level configuration of the
external Boolean alarm is consistent with that in the configuration planning.
13/11/2012 9:15
Fault Management
508 de 526
13/11/2012 9:15
Fault Management
509 de 526
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Version
The following table lists the product versions involved in this document.
Product Name
Version
V200R014C00
V200R014C00
V200R014C00
V200R014C00
V200R014C00
V200R014C00
Intended Audience
This document is intended for:
Field engineers
System engineers
Shift operators
Site maintainers
Network operators
Concepts
Concept
Description
Event ID
Event Name
Unique name of an event in one product. Event names clearly and accurately indicate event
meanings. There is a one-to-one mapping between event names and IDs.
Event Type
Event Level
Impact of an event on service quality. There are three event severity levels: major, minor,
and warning.
Major event: affects service quality and requires immediate action during working
hours.
Minor event: generally does not affect service quality, but requires handling or
observation in a reasonable amount of time to avoid more serious faults.
Warning event: indicates a potential error that may affect service quality. It
13/11/2012 9:15
Fault Management
510 de 526
Concept
Description
requires different actions depending on errors.
Event Type
Description
Parameters
Impact on the
System
Possible
Causes
Procedure
Change History
For detailed event changes, see the release notes.
Event Name
Event Type
Event Level
Event Type
EVT-25890
Event
Minor
Trunk
EVT-25893
Remote
Maintenance Link
Switchover
Event
Minor
Trunk
13/11/2012 9:15
Fault Management
511 de 526
Event ID
Event Name
Event Type
Event Level
Event Type
EVT-26212
Board Startup
Event
Minor
Running
EVT-26213
NE Startup
Event
Minor
Running
EVT-26256
NE Software
Download Started
Event
Warning
Running
EVT-26257
NE Software
Download Ended
Event
Warning
Running
EVT-26258
NE Software
Activation Started
Event
Warning
Running
EVT-26259
NE Software
Activation Ended
Event
Warning
Running
EVT-26505
RF Unit CPRI
Interface
Switchover
Event
Minor
Communication
EVT-26526
RF Unit TX
Channel Switched
Off
Event
Major
Hardware
EVT-26528
RF Unit TX
Channel Switched
On
Event
Minor
Hardware
EVT-26535
RF Unit Startup
Event
Minor
Hardware
EVT-26784
RHUB CPRI
Interface
Switchover
Event
Minor
Communication
EVT-26820
License
Emergency Status
Activated
Event
Warning
Running
EVT-26821
License
Emergency Status
Ceased
Event
Warning
Running
EVT-28200
Iub Common
Procedure Failure
Indication
Event
Major/Minor
Running
EVT-28202
Event
Major
QoS
EVT-28222
Event
Major
QoS
EVT-28251
Ethernet
Configuration
Changed
Event
Minor
Running
13/11/2012 9:15
Fault Management
512 de 526
Event ID
Event Name
Event Type
Event Level
Event Type
EVT-28252
IP RAN Object
Reset
Event
Major
Trunk
EVT-28352
Enable
Downloaded
Configuration File
Event
Minor
Running
EVT-28353
Disable
Downloaded
Configuration File
Event
Minor
Running
EVT-28380
NE Shutdown
Event
Major
Running
Parameters
Name
Meaning
Switchover
Direction
Description
Event Impact
Minor
During the switchover between the primary link and the secondary link of the SCTP,
the signaling communication fails temporarily. In this case, no terminal can access
the network during the switchover.
Possible Causes
The current link that carries the SCTP is faulty, and the SCTP switches to another link.
The automatic switchover is enabled. When the secondary link is used, the automatic switchover is
triggered if the primary link is restored.
Procedure
1. This is an event. No manual operation is required.
13/11/2012 9:15
Fault Management
513 de 526
Parameters
Name
Meaning
Switchover
Direction
Event Impact
Minor
None
Possible Causes
The current link for remote maintenance is faulty, and another link is used for remote maintenance.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Cabinet
No.
Subrack
No.
Slot No.
Board
Type
Reset
Cause
Reason of the board reset (Board Power Off, User Command, System Self-Reset, External
Operation Reset, Swap MPT, Exceptional Reset, Communication Abnormal, Unknown Reason)
Event Impact
Minor
Possible Causes
The board is reset due to a power failure, for example, removing and then inserting the board or
running a reset command through power-off.
The board is reset due to the execution of a command, for example, running a software activation
command, a board reset command, or a board addition command during an upgrade.
The board is reset due to internal negotiation of the system, for example, changing the environment
variables of the board, or the board is reset due to a transmission subsystem fault.
13/11/2012 9:15
Fault Management
514 de 526
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Reset
Cause
Reason of the NE reset (Board Power-Off, User Command, System Self-Reset, External
Operation, Active/Standby MPT Switchover, Exceptional Reset, Disconnected Link, Unknown)
Event Impact
Minor
Possible Causes
The base station is reset due to a power failure.
The base station is reset due to the execution of a base station reset command or a software
upgrade command .
The base station is reset due to internal negotiation of the system , a UTRPc/UMPT board fault and
signaling extension services unavailable, or a transmission subsystem fault.
The base station is reset due to an external operation.
The base station is reset when an active/standby switchover is triggered.
The base station is reset when it does not work properly.
The base station is reset due to link disconnection.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
13/11/2012 9:15
Fault Management
515 de 526
Software Type
Cause
Event Impact
Warning
None
Possible Causes
An operator is manually downloading NE software.
An operator is manually supplementing NE software.
The NE software automatic supplementation function is triggered. This function is triggered when a
new board is installed in the base station but the base station does not have the software for the
board.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Software Type
Result
Event Impact
Warning
None
Possible Causes
The download of the NE Software succeeds.
The download of the NE Software fails.
Procedure
1. This is an event. No manual operation is required.
13/11/2012 9:15
Fault Management
516 de 526
Parameters
Name
Meaning
Software Type
Event Impact
Warning
None
Possible Causes
A user starts to activate the NE software.
The software auto-activation starts.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Software Type
Result
Event Impact
Warning
None
Possible Causes
The activation of the NE Software succeeds.
The activation of the NE Software fails.
Procedure
1. This is an event. No manual operation is required.
Parameters
13/11/2012 9:15
Fault Management
517 de 526
Name
Meaning
Cabinet No.
Subrack No.
Slot No.
Board Type
Event Impact
Minor
In the case of a hot ring, the ongoing services are not affected. In the case of a cold
ring, the ongoing services are disrupted temporarily.
Possible Causes
The uplink of the RF unit is faulty.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Cabinet No.
Subrack No.
Slot No.
TX Channel No.
TX channel number
Board Type
Specific Problem
Event Impact
Major
Possible Causes
The cell is removed, blocked, or deactivated.
A critical fault occurs on the RF unit, such as PA overcurrent, critical overtemperature, or extremely
high VSWR.
The user sends a command to switch off the TX channel of the RF unit.
13/11/2012 9:15
Fault Management
518 de 526
When the AC mains failure occurs and the batteries are running out, the system automatically
switches off the TX channel of the RF unit to extend the operating time of the BBU and transmission
devices.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Cabinet No.
Subrack No.
Slot No.
TX Channel No.
TX channel number
Board Type
Event Impact
Minor
None
Possible Causes
A cell is activated.
The user sends a command to switch on the TX channel of an RF unit.
If a critical fault of an RF unit persists for some time, the system automatically switches on the TX
channel of the RF unit to detect the clearance of the critical fault
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Cabinet No.
13/11/2012 9:15
Fault Management
519 de 526
Slot No.
Board Type
Reset
Reason
Cause of the RF unit reset (Board Power-Off, User Command, Exceptional Reset,
Disconnected Link, Unknown Reason)
Event Impact
Minor
The RF unit starts. The services of the RF unit are set up again.
Possible Causes
The user sends the reset command to the RF unit.
The RF unit is powered on or reset.
The RF unit automatically resets after it is disconnected for a long period of time.
The RF unit automatically resets after the RF software activation or new configuration is complete.
The RF unit automatically resets after it exits the sleep mode.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Cabinet No.
Subrack No.
Slot No.
Board Type
Event Impact
Minor
In the case of a hot ring, the ongoing services are not affected. In the case of a cold
ring, the ongoing services are disrupted temporarily.
Possible Causes
The CPRI uplink of the RHUB is faulty.
13/11/2012 9:15
Fault Management
520 de 526
Procedure
1. This is an event. No manual operation is required.
Parameters
None.
Event Impact
Warning
The dynamic counting items and performance items in the license, such as the
number of channel elements (CEs) in the uplink and number of CEs in the downlink,
are set to their maximum values. Other types of license-controlled items use their
original values.
The system can keep in the emergency state for a maximum of seven days. Later,
the system is rolled back to the license state.
Possible Causes
The emergency status of a license is activated by someone in an emergency such as fire or earthquake.
Procedure
1. This is an event. No manual operation is required.
Parameters
None.
Event Impact
Warning
Possible Causes
The emergency status of a license remains active for seven days. After the seven-day period
elapses, the emergency status is automatically ceased.
The license is reloaded.
Procedure
1. This is an event. No manual operation is required.
13/11/2012 9:15
Fault Management
521 de 526
Parameters
Name
Meaning
Cause
(Common TRCH Setup Failure, Common TRCH RECFG Failure, Common MEA INIT Failure,
Common MEA Failure, Cell Setup Failure, Cell RECFG Failure, SYS MSG Update Failure, Shared
TRCH RECFG Failure, INFO EXCHANGE INIT Failure, INFO EXCHANGE Failure)
Cell ID
Cell ID
Specific
Problem
Specific Problem of the alarm(System Message Abnormal, Common Transport Channel Carried by
SCCPCH Abnormal, Common Transport Channel Carried by PRACH Abnormal, Other Transport
Channel Abnormal, RTWP Measurement Abnormal, Transmitted Carrier Power Measurement
Abnormal, Acknowledged PRACH Preambles Measurement Abnormal, GPS Timing of Cell Frames
Measurement Abnormal, Transmitted Carrier Power Measurement Abnormal Not Used for HSDPA,
HS-DSCH Required Power Measurement Abnormal, HS-DSCH Provided Bit Rate Measurement
Abnormal, ISCP Measurement Abnormal, APAP Measurement Abnormal, DPAP Measurement
Abnormal, SOTD Measurement Abnormal, Shared Transport Channel Reconfiguration Failure, INFO
EXCHANGE INIT Failure, INFO EXCHANGE Failure, Cell Procedure Abnormal)
Event Impact
Major
Minor
Possible Causes
Resources in the cell are insufficient or faulty. For example, the hardware of the board carrying the
traffic is faulty.
The software processing of the RNC or NE is improper.
The processing of the RNC is incorrect. As a result, the contents of the message that is sent to the
NE are incorrect.
Procedure
1. Check the local cell status of the NE on the M2000.
a. Run the MML command DSP LOCELL to check whether the local cell status of the
failed signaling is normal.
Y => Local Cell Status is Local Cell Available. The local cell is normal. Go to step 2.
N => Local Cell Status is Local Cell Unavailable. The local cell is faulty. The cause
may be that the hardware resources of the NE are faulty. Go to sub-step b.
b. Run the MML command LST ALMAF to check whether certain alarms of the NE are not
cleared.
Y => Certain alarms are not cleared. Go to sub-step c.
N => All alarms are cleared. Go to sub-step d.
13/11/2012 9:15
Fault Management
522 de 526
Parameters
Name
Meaning
Local Cell ID
Local Cell ID
Event Impact
Major
In the case that the event is reported because the local cell is faulty, only the faulty
13/11/2012 9:15
Fault Management
523 de 526
Event Severity
Event Impact
local cell and faulty logical cell are reestablished.
In the case that the event is reported because the resources of the local cell are not
optimum, all the available local cells and logical cells are reestablished.
Possible Causes
The local cell fails to provide services and the system attempts to the local cell reestablish the local
cell for recovery from the fault. This happens when: a) The SET NOACCESSALMPARA command is
executed and the AUTORCVRMTHD parameter is set to CELLRESTART. b) The cell has no output
power.
If the resources of the local cell are not optimum, the system attempts to optimize the resources.
This happens when: a) The STR REALLOCLOCELL command is executed to optimize baseband
resources.
Procedure
1. This is an event. No manual operation is required.
Parameters
Name
Meaning
Local Cell ID
Local Cell ID
Event Impact
Major
In the case that the event is reported because the IMB local cell is faulty, only the
faulty IMB local cell and faulty logical cell are reestablished.
In the case that the event is reported because the resources of the IMB local cell are
not optimum, all the available local cells and logical cells are reestablished.
Possible Causes
The IMB local cell is faulty and fails to provide services. Thus, the system attempts to recover from
the fault by reestablishing the IMB local cell.
If the resources of the IMB local cell are not optimum, the system attempts to optimize the resources
of the IMB local cell.
Procedure
1. This is an event. No manual operation is required.
13/11/2012 9:15
Fault Management
524 de 526
This event is reported when the auto negotiation is enabled for the local Ethernet electrical port but disabled for
the peer Ethernet electrical port.
Parameters
Name
Meaning
Cabinet No.
Subrack No.
Slot No.
Port No.
Port No.
Board Type
Event Impact
Minor
If the Ethernet electrical port carries heavy traffic, Ethernet frames may be lost,
causing the services to be interrupted for a short time.
Possible Causes
The auto negotiation is enabled for the local Ethernet electrical port but disabled for the peer port (full-duplex or
half-duplex).
Procedure
1. Perform the corresponding operation on the M2000 to allow the system to renegotiate the working
mode of the Ethernet ports.
a. Set the working mode of the Ethernet port on the peer device connected to the NE to
auto negotiation, and then run the MML command RST ETHPORT to reset the Ethernet
electrical port for which the event is triggered.
Parameters
Name
Meaning
Cabinet No.
Subrack No.
Slot No.
Object Type
Object No.
Object No.
Board Type
13/11/2012 9:15
Fault Management
525 de 526
Event Severity
Event Impact
Major
The signaling and services carried on the ETH port, MLPPP group, PPP link,
ETHTRUNK are interrupted for a short time.
Possible Causes
The MML command is executed to reset the objects of the IP transmission network (ETH port, MLPPP group,
PPP link, and ETHTRUNK).
Procedure
1. This is an event. No manual operation is required.
Parameters
None.
Event Impact
Minor
After the system is restarted, the downloaded configuration file takes effect and
overwrites the original configuration file.
Possible Causes
The command SET CFGFILEENB is executed with Enable Flag set to Enable.
Procedure
1. This is an event. No manual operation is required.
Parameters
None.
Event Impact
Minor
13/11/2012 9:15
Fault Management
526 de 526
Possible Causes
The command SET CFGFILEENB is executed with Enable Flag set to Disable.
The flag is enabled, but the user redownloads the configuration file.
The flag is enabled, but the user activates the CB.
The flag is enabled, but the user rolls back the CB.
Procedure
1. This is an event. No manual operation is required.
Parameters
None.
Event Impact
Major
Possible Causes
The user runs the command to reset the NE or the active WMPT/UMPT.
Procedure
1. This is an event. No manual operation is required.
13/11/2012 9:15