Security Level: Internal

Alarm Check and Trouble

Shooting Quick Guide for
Claro 3G Network
IUB INTERFACE

www.huawei.com
by Carlos Cesar

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential

Contents

• 1. IuB Topology
• 1. Basic Script Configuration
• 2. Monitoring RAN Current Fault Alarms
• 3. Main Fault Alarms and Troubleshooting – RNC
• 4. Main Fault Alarms and Troubleshooting – NodeB
 IuB Topology
NodeB over ATM:

ATM Network
SAAL Link RADIO RADIO
RNC MUX
MW E1

OF AAL2 Path
NodeB

NodeB over ATM & IP:

ATM & IP Network

SAAL Link RADIO RADIO

RNC MUX
MW E1+FE

AAL2 Path - ATM ROUTER

OF+FE
IP Path - IP NodeB

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 3

Contents

• 1. IuB Topology
• 1. Basic Script Configuration
• 2. Monitoring RAN Current Fault Alarms
• 3. Main Fault Alarms and Troubleshooting – RNC
• 4. Main Fault Alarms and Troubleshooting – NodeB
 NodeB Basic Script Configuration in RNC
NodeB over ATM:

Links for Signaling – Control Plane: Links for Traffic – User Plane:

3 SAAL LINK (ATM Link) 4 AAL2 Path (ID=1, 2, 3 and 4) (ATM Link)
NCP (associate in SAAL LINK)
CCP (associate in SAAL LINK) Link for OM Channel:
ADJNODE (ALCAP) (associate in SAAL LINK) NODEBIP and IPOAPVC (OM IP over ATM)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 5

 NodeB Basic Script Configuration in RNC
NodeB over ATM & IP:
Links for Signaling – Control Plane(ATM) : Links for Traffic – User Plane (ATM & IP):
ATM: 2 AAL2 PATH (ID=1 and 2) (ATM Link)
3 SAAL LiNK (ATM Link) IP: 2 IP PATH (ID=1 and 2) (IP Link)
NCP (associate in SAAL LINK)
CCP (associate in SAAL LINK) Link for OM Channel:
ADJNODE (ALCAP) (associate in SAAL LINK) NODEBIP and IPOAPVC (OM IP over ATM)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 6

 Cell Basic Script Configuration in RNC
NodeB over ATM and ATM & IP:
Main Configuration for Cells (per cell):

SAC (Service Area Code)

LOCELL (Local Cell)
QUICKCELLSETUP (Set up cell quickly)
CELLHSDPA (HSDPA parameters for cell)
CELLURA (UTRAN Registration Area (URA) of cell)

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 7

Contents

• 1. IuB Topology
• 1. Basic Script Configuration
• 2. Monitoring RAN Current Fault Alarms
• 3. Main Fault Alarms and Troubleshooting – RNC
• 4. Main Fault Alarms and Troubleshooting – NodeB
Monitoring RAN Current Fault Alarms (by M2000)

Prerequisite
Connection between the M2000 client and the M2000 server is operational.
You have the permission to query alarms.

Procedure
Step 1 Choose Monitor > Current Fault Alarms on the M2000 client. The Filter dialog box is displayed.
Step 2 Select the conditions in the Filter dialog box.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 9

Monitoring RAN Current Fault Alarms (by M2000)
Step 3 Click OK. Then the current fault alarms are displayed in the Current Fault Alarms tab.
Step 4 To view details of an alarm, double-click the alarm. The Detail Information dialog box is
displayed.
Step 5 In the Detail Information dialog box, double-click the Alarm Experience tab. Then you may
record the symptom, cause and handling method of the alarm in Modify Experience dialog box.
Step 6 Repeat Step 4 through Step 5 to handle the alarms one by one until no fault alarms are
generated.

NOTE
When select an alarm you can find some information:
In Alarm Detail Information tab you can find the details of an alarm
In Process Advice tab you can click the link to check the process advice of an alarm.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 10

Monitoring RAN Current Fault Alarms (by LMT)
Prerequisite
The LMT is started.

Procedure
In the Local Maintenance Terminal window, choose Fault Management > Browse Alarm to display
the Alarm Browse window. The upside of the window is the fault alarm browse pane and the downside
is the event alarm browse pane.
Browse alarms in the Alarm Browse windows.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 11

Monitoring RAN Current Fault Alarms (by LMT)
To learn the details of an alarm, double-click it. The Alarm Detailed Information dialog box
is displayed, as shown in Figure 1.

Click the following buttons as required.

Button Name Result
Previous Check the details of the previous alarm
Next Check the details of the next alarm
Solution Check the alarm meaning, the impact on the system, the system action, and the alarm handling.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 12

Contents

• 1. IuB Topology
• 1. Basic Script Configuration
• 2. Monitoring RAN Current Fault Alarms
• 3. Main Fault Alarms and Troubleshooting – RNC
• 4. Main Fault Alarms and Troubleshooting – NodeB
 Main Fault Alarms by RNC
Signaling Link Alarms:
Alarm: SAAL Link Unavailable
Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major SAAL Link Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, SAAL link No.=24, Cause=No response timer expiry., NodeB ID=128,
27/6/2010
NodeB01:55
Name=UMGULA21
1802
Major SAAL Link Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, SAAL link No.=26, Cause=No response timer expiry., NodeB ID=128,
27/6/2010
NodeB01:55
Name=UMGULA21
1802
Major SAAL Link Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, SAAL link No.=25, Cause=No response timer expiry., NodeB ID=128,
27/6/2010
NodeB01:55
Name=UMGULA21
1802

Alarm: NCP Faulty

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major NCP Faulty RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, NodeB ID=128, NodeB NAME=UMGULA21, SAAL Link No.=24, SCTP
27/6/2010
Link No.=NULL
01:55 2010
Major NCP Faulty RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=2, NodeB ID=135, NodeB NAME=UMGULA28, SAAL Link No.=0, SCTP
27/6/2010
Link No.=NULL
01:55 2010
Major NCP Faulty RNCMG06 Subrack No.=3, Slot No.=0, Subsystem No.=2, NodeB ID=115, NodeB NAME=UMGULA08, SAAL Link No.=12, SCTP
27/6/2010
Link No.=NULL
09:01 2010

Alarm: NodeB Unavailable

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major NodeB Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, NodeB ID=128, NodeB Name=UMGULA21, Cause=Port of the NodeB
27/6/2010
unavailable.
01:55 2026
Major NodeB Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=3, NodeB ID=144, NodeB Name=UMGULA37, Cause=Port of the NodeB
27/6/2010
unavailable.
01:55 2026
Major NodeB Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, NodeB ID=126, NodeB Name=UMGULA19, Cause=Port of the NodeB
27/6/2010
unavailable.
01:55 2026
Major NodeB Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=2, NodeB ID=135, NodeB Name=UMGULA28, Cause=Port of the NodeB
27/6/2010
unavailable.
01:55 2026

Alarm: CCP Faulty

Severity Name Alarm Source Location Information Occurrence Time(NT)
Alarm ID
Major CCP Faulty RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=3, NodeB ID=144, NodeB NAME=UMGULA37, CCP Port No.=0, SAAL
27/6/2010
link No.=10,
01:55SCTP link2011
No.=N
Major CCP Faulty RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, NodeB ID=126, NodeB NAME=UMGULA19, CCP Port No.=0, SAAL
27/6/2010
link No.=19,
01:55SCTP link2011
No.=N
Major CCP Faulty RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=2, NodeB ID=135, NodeB NAME=UMGULA28, CCP Port No.=0, SAAL
27/6/2010
link No.=1,
01:55
SCTP link 2011
No.=NU
Major CCP Faulty RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=3, NodeB ID=153, NodeB NAME=UMGULA46, CCP Port No.=0, SAAL
27/6/2010
link No.=37,
01:55SCTP link2011
No.=N

Alarm: AAL2 Adjacent Node Unavailable

Severity Name Alarm Source Location Information Occurrence Time(NT)
Alarm ID
Major AAL2 Adjacent Node Unavailable RNCMG06 Adjacent node ID=128, Adjacent node interface type=Iub interface, NodeB ID=128, NodeB Name=UMGULA21
27/6/2010 01:55 1615
Major AAL2 Adjacent Node Unavailable RNCMG06 Adjacent node ID=144, Adjacent node interface type=Iub interface, NodeB ID=144, NodeB Name=UMGULA37
27/6/2010 01:55 1615
Major AAL2 Adjacent Node Unavailable RNCMG06 Adjacent node ID=143, Adjacent node interface type=Iub interface, NodeB ID=143, NodeB Name=UMGULA36
27/6/2010 01:55 1615
Major AAL2 Adjacent Node Unavailable RNCMG06 Adjacent node ID=135, Adjacent node interface type=Iub interface, NodeB ID=135, NodeB Name=UMGULA28
27/6/2010 01:55 1615

Impact: In case of these alarms, the NodeB service will be impacted.

For handle the alarm, you can get the description and actions to fix this in Help Topics by M2000 or LMT
Software.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 14

 SAAL Link Unavailable
Troubleshooting Guide

1. Possible Causes
(1) Iu/Iur interface link error rate is too high. See the    An IMA group => Continue to procedure 2.
handling procedure 1 and 6.
    A UNI link => Continue to procedure 3.
(2) Iu/Iur interface link has no credit in a long period.
See the handling procedure 1 and 7.     An optical port => Continue to procedure 4.
(3) Timer_NO-RESPONSE expires. See the handling     A Fractional IMA Link => Continue to procedure 5.
procedure 1 and 8.
(4) Remote processor is faulty. See the handling (2) Check whether there is any alarm related with
procedure 1 and 9. the IMA group.
(5) Link is released by the peer end. See the handling 1) Check whether there is any alarm related with the
procedure 1 and 10.
IMA group with [Bearing IMA group No.] in the
(6) Link is released by the local SAAL upper user
NBAP/MTP3B. See the handling procedure 1 and 11. "Browse Alarm" window.
(7) No PDU is received from the peer end. See the     Y => Continue to step 2).
handling procedure 1 and 12.     N => Continue to procedure 6.
(8) Timer_CC expires. See the handling procedure 1 2) Clear the alarm according to the corresponding
and 13. solution procedure.
3) Check whether the alarm is cleared.
2. Handling Suggestions     Y => The alarm is cleared. No further actions are
(1) Query the bearer information of the SAAL link. required.
Use the following command: LST SAALLNK with the
following parameters in the alarm: [Subrack No.], [Slot     N => The alarm is not cleared. Continue to
No.], [Subsystem No.] and [SAAL link No.]. The bearer procedure 6.
information is shown as follows:
 

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 15

 SAAL Link Unavailable
Troubleshooting Guide

(3) Check whether there is an 1007 IMA/UNI Link

Loss Of Cell Delineation alarm. 3) Check whether the alarm is cleared.
1) Check whether there is an 1007 IMA/UNI Link     Y => The alarm is cleared. No further actions are
Loss Of Cell Delineation alarm with [Bearing UNI link required.
No.] in the "Browse Alarm" window.     N => The alarm is not cleared. Continue to
    Y => Continue to step 2). procedure 6.
    N => Continue to procedure 6.    
2) Clear the alarm according to the corresponding (5) Check whether there is any alarm related with
solution procedure. the Fractional IMA Link .
3) Check whether the alarm is cleared. 1) Check whether there is any alarm related with the
    Y => The alarm is cleared. No further actions are Fractional IMA Link [Bearing Fractional IMA Link No.]
required.
in the "Browse Alarm" window.
    N => The alarm is not cleared. Continue to
procedure 6.     Y => Continue to step 2).
    N => Continue to procedure 6.
(4) Check whether there is any alarm related with 2) Clear the alarm according to the corresponding
the optical port. solution procedure.
1) Check whether there is any alarm related with the 3) Check whether the alarm is cleared.
optical port with [Bearing slot No.] and [Bearing port     Y => The alarm is cleared. No further actions are
No.] in the "Browse Alarm" window. required.
    Y => Continue to step 2).     N => The alarm is not cleared. Continue to
    N => Continue to procedure 6.
procedure 6.
2) Clear the alarm according to the corresponding
solution procedure.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 16

 SAAL Link Unavailable
Troubleshooting Guide

(6) Query the [Cause] parameter in the alarm. 2) Check whether the traffic record parameters are
The parameter value is shown as follows: consistent with those of the peer end. Use the
    The Iu/Iur interface link error rate is too high. following command: LST ATMTRF with the traffic
Continue to procedure 7. record index queried in step 1).
    The Iu/Iur interface link has no credit in a long     Y => Continue to step 5).
period. Continue to procedure 8.
    N => Continue to step 3).
    The no response timer expires. Continue to
procedure 9. 3) Reconfigure the parameters. Use the following
    The remote processor is faulty. Continue to command: MOD SAALLNK.
procedure 10. 4) Check whether the alarm is cleared.
    The link is released by the peer end. Continue to     Y => The alarm is cleared. No further actions are
procedure 11. required.
    The link is released by the local SAAL user.     N => The alarm is not cleared. Continue to step 5).
Continue to procedure 12. 5) Check whether the physical devices are well
    No PDU is received from the peer end. Continue connected.
to procedure 13.     Y => Continue to step 8).
    Unknown cause. Continue to procedure 14.     N => Continue to step 6).
6) Adjust the connection of the physical devices.
(7) Check the traffic record parameters, physical 7) Check whether the alarm is cleared.
devices, and BER of the physical devices.
    Y => The alarm is cleared. No further actions are
1) Query the PVC traffic record index. Use the
following command: LST SAALLNK. required.
    N => The alarm is not cleared. Continue to step 8).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 17

 SAAL Link Unavailable
Troubleshooting Guide (9) Increase the [No response timer] value.
1) Increase the [No response timer] value. Use the
8) Check whether the BER is normal for the following command: MOD SAALLNK.
transmission devices, if used. 2) Check whether the alarm is cleared.
    Y => Contact Support Engineer.     Y => The alarm is cleared. No further actions are
    N => Continue to step 9). required.
9) Adjust the connection of the physical devices.     N => The alarm is not cleared. Continue to step 3).
10) Check whether the alarm is cleared. 3) Contact the maintenance engineers of the peer
    Y => The alarm is cleared. No further actions are end.
required.
    N => The alarm is not cleared. Contact Support (10) Contact the maintenance engineers of the
Engineer.
peer end.
(8) Increase the [No credit timer] value.
1) Contact the maintenance engineers of the peer
1) Increase the [No credit timer] value. Use the end.
following command: MOD SAALLNK. 2) Check whether the alarm is cleared.
2) Check whether the alarm is cleared.     Y => The alarm is cleared. No further actions are
    Y => The alarm is cleared. No further actions are required.
required.     N => The alarm is not cleared. Contact Support
    N => The alarm is not cleared. Continue to step 3). Engineer.
3) Contact the maintenance engineers of the peer
end to increase the [Receiving window size] value of (11) Contact the maintenance engineers of the
the peer end.
peer end.
4) Check whether the alarm is cleared.
1) Contact the maintenance engineers of the peer
Y => The alarm is cleared. No further actions are
required. end.
    N => The alarm is not cleared. Contact Support 2) Check whether the alarm is cleared.
Engineer.     Y => The alarm is cleared. No further actions are
required.
    N => The alarm is not cleared. Contact Support
Page 18
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential
Engineer.
 SAAL Link Unavailable
Troubleshooting Guide

(12) Clear the 1413 MTP-3b Signaling Link

Unavailable alarm.
1) Clear the 1413 MTP-3b Signaling Link 3) Check whether the alarm is cleared.
Unavailable alarm according to the corresponding     Y => The alarm is cleared. No further actions are
solution procedure.
required.
2) Check whether the alarm is cleared.
    N => The alarm is not cleared. Contact Support
    Y => The alarm is cleared. No further actions are
required. Engineer.
    N => The alarm is not cleared. Contact Support
Engineer. (14) Perform procedure 7 or 13.
Note: If the alarm is triggered after the SPU board
(13) Check whether the optical port, VPI and VCI reset or switchover, the two most probable causes are
of this link are consistent with those of the peer that the Iu/Iur interface link error rate is too high or no
end. PDU is received from the peer end.
1) Check whether the optical port, VPI and VCI of
this link are consistent with those of the peer end.
Use the following command: LST SAALLNK with the
following parameters in the alarm: [Subrack No.],
[Slot No.], [Subsystem No.] and [SAAL link No.].
    Y => Contact Support Engineer.
    N => Continue to step 2).
2) Reconfigure the parameters so that they are
consistent with those at the peer end.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 19

 NCP Faulty
Troubleshooting Guide
2) Check whether there is the 1802 SAAL Link
1. Possible Causes Unavailable alarm, which has not been cleared and
The corresponding link of the NCP is faulty. has the SAAL link No. that matches the link No. of the
current alarm.
2. Handling Suggestions     Y => There is such an alarm. Continue to step 3).
(1) Check the link bearer type of the faulty NCP.     N => There is no such alarm. Contact Support
1) Query the link bearer type. Use the following Engineer.
command: LST IUBCP. Make sure the NodeB name 3) Check whether the operational status of the SAAL
of the command parameter matches the NodeB is "unavailable". Use the following command: DSP
name of the alarm parameter. SAALLNK.
2) Check the link bearer type.     Y => The operational status of the SAAL is
    SAAL => Continue to procedure (2). unavailable. Continue to step 4).
    SCTP => Continue to procedure (3).     N => Contact Support Engineer.
    SAAL-SCTP => Continue to procedure (2) and 4) Solve the transfer link related problem according to
(3).
the solution to the 1802 SAAL Link Unavailable.
When this problem is solved and the status of the
(2) Check the operational status of the SAAL that
bears the faulty NCP. bearer link works properly, continue to step 5).
1) Query the operational status of the SAAL that 5) Check whether this alarm is cleared.
bears the faulty NCP. Use the following command:    Y => The alarm is cleared. No further actions are
DSP SAALLNK. Make sure that the subrack No., the required.
SPU slot No., and the SPU subsystem No. of the    N => The alarm is not cleared. Contact Support
command parameter match those in the current
alarm. Engineer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 20

 NodeB Unavailable
Troubleshooting Guide

1. Possible Causes (2) Check the availability of CCP.

1) The NCP of this NodeB is unavailable. 1) Check whether the CCP of this NodeB exists. Use
2) All the CCPs of this NodeB are unavailable. the following command: LST IUBCP.
    Y => The CCP of this NodeB exists. Continue to
2. Handling Suggestions step 2).
(1) Check the availability of NCP.     N => The CCP of this NodeB does not exist.
1) Check whether the NCP of this NodeB exists. Use Continue to step 3).
the following command: LST IUBCP. 2) Check whether there is an alarm 2011 CCP Faulty.
    Y => The NCP of this NodeB exists. Continue to     Y => There is such an alarm. Continue to step 4).
step 2).
    N => There is no such alarm. Contact Support
    N => The NCP of this NodeB does not exist.
Continue to step 3). Engineer.
2) Check whether there is a 2010 NCP Faulty alarm. 3) Add CCP. Use the following command: ADD CCP.
    Y => There is such an alarm. Continue to step 4). Continue to step 5).
    N => There is no such alarm. Continue to 4) Clear the alarm 2011 according to the
procedure (2). corresponding handling suggestions. When the
3) Add the NCP. Use the following command: ADD problem is solved, continue to step 5).
NCP. Continue to step 5). 5) Check whether the alarm is cleared.
4) Clear the alarm 2010 according to the     Y => The alarm is cleared. No further actions are
corresponding handling suggestions. When the required.
problem is solved, continue to step 5).
5) Check whether the alarm is cleared.     N => The alarm is not cleared. Contact Support
    Y => The alarm is cleared. No further actions are Engineer.
required.
    N => The alarm is not cleared. Continue to
procedure (2).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 21

 CCP Faulty
Troubleshooting Guide
2) Check whether there is the 1802 SAAL Link
1. Possible Causes Unavailable alarm, which has not been cleared and
The corresponding link of the CCP is faulty. has the SAAL link No. that matches the link No. of the
current alarm.
2. Handling Suggestions     Y => There is such an alarm. Continue to step 3).
(1) Check the link bearer type of the faulty CCP.     N => There is no such alarm. Contact Support
1) Query the link bearer type. Use the following Engineer.
command: LST IUBCP. Make sure the NodeB name 3) Check whether the operational status of the SAAL
of the command parameter matches the NodeB is "unavailable". Use the following command: DSP
name of the alarm parameter. SAALLNK.
2) Check the link bearer type.     Y => The operational status of the SAAL is
    SAAL => Continue to procedure (2). unavailable. Continue to step 4).
    SCTP => Continue to procedure (3).     N => Contact Support Engineer.
    SAAL-SCTP => Continue to procedure (2) and 4) Solve the transfer link related problem according to
(3).
the solution to the 1802 SAAL Link Unavailable.
When this problem is solved and the status of the
(2) Check the operational status of the SAAL that
bears the faulty CCP. bearer link works properly, continue to step 5).
1) Query the operational status of the SAAL that 5) Check whether this alarm is cleared.
bears the faulty CCP. Use the following command:    Y => The alarm is cleared. No further actions are
DSP SAALLNK. Make sure that the subrack No., the required.
SPU slot No., and the SPU subsystem No. of the    N => The alarm is not cleared. Contact Support
command parameter match those in the current
alarm. Engineer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 22

 AAL2 Adjacent Node Unavailable N=> The current alarm is not caused by alarm 1802.
Contact Support Engineer.
Troubleshooting Guide 2) Handle the alarm in accordance with the handling
suggestions presented in alarm 1802. When the
problem is solved, continue to step 3).
1. Possible Causes
3) Check whether this alarm is cleared.
(1) If the type of interface between the RNC and this
adjacent node is Iub, the possible cause is that an     Y => This alarm is cleared. No further actions are
SAAL link for bearing signaling is broken. See the required.
handling procedure 1 and 2.     N => This alarm is not cleared. Contact Support
(2) If the type of interface between the RNC and this Engineer.
adjacent node is Iur/Iu, the possible cause is that the (3) Check whether there was a 1403 MTP-3b DSP
DSP of the MTP-3b is unavailable. See the handling
procedure 1 and 3. Inaccessible alarm generated at almost the same
time as the current alarm was generated.
2. Handling Suggestions 1) Check whether there was an alarm 1403 generated
(1) Check the interface type, and SAAL link No. at almost the same time as the current alarm was
(for Iub)/MTP-3b link No. (for Iu/Iur). generated.
1) Use the following command: LST ADJNODE.     Y=> The current alarm is caused by alarm 1403.
    Iub interface => Continue to procedure 2. Continue to step 2).
    Other interface types => Continue to procedure 3.     N=> The current alarm is not caused by alarm
1403. Contact Support Engineer.
(2) Check whether there was a 1802 SAAL Link 2) Handle the alarm in accordance with the handling
Unavailable alarm generated at almost the same
time as the current alarm was generated. suggestions presented in alarm 1403. When the
1) Check whether there was a 1802 SAAL Link problem is solved, continue to step 3).
Unavailable alarm generated at almost the same time 3) Check whether this alarm is cleared.
as the current alarm was generated.     Y => This alarm is cleared. No further actions are
    Y=> The current alarm is caused by alarm 1802. required.
Continue to step 2).
    N => This alarm is not cleared. Contact Support
    
Engineer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 23

 Main Fault Alarms by RNC

User Plane Links Alarms:

Alarm: Path Unavailable (Type=IP)

Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Major Path Unavailable RNCMG06 Subrack No.=1, Slot No.=0, Subsystem No.=2, Adjacent node ID=37, Path ID=1, Path transport type=IP, Cause=IPPATH
27/6/2010
ping11:58
fail, NodeB1711
ID=37, N
Major Path Unavailable RNCMG06 Subrack No.=1, Slot No.=0, Subsystem No.=2, Adjacent node ID=43, Path ID=1, Path transport type=IP, Cause=IPPATH
27/6/2010
ping11:58
fail 1711
Major Path Unavailable RNCMG06 Subrack No.=1, Slot No.=0, Subsystem No.=2, Adjacent node ID=43, Path ID=1, Path transport type=IP, Cause=IPPATH
27/6/2010
ping12:03
fail 1711

Alarm: Path Unavailable (Type=ATM)

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major Path Unavailable RNCMG02 Subrack No.=1, Slot No.=2, Subsystem No.=1, Adjacent node ID=131, Path ID=2, Path transport type=ATM, Cause=Path
10/7/2010 13:56
inner forbidden
1711caus
Major Path Unavailable RNCMG02 Subrack No.=1, Slot No.=2, Subsystem No.=1, Adjacent node ID=131, Path ID=2, Path transport type=ATM, Cause=Path
10/7/2010 14:08
inner forbidden
1711caus
Major Path Unavailable RNCMG02 Subrack No.=1, Slot No.=2, Subsystem No.=1, Adjacent node ID=131, Path ID=2, Path transport type=ATM, Cause=Path
10/7/2010 14:21
inner forbidden
1711caus

Impact: In case of these alarms, the NodeB service will be impacted.

For handle the alarm, you can get the description and actions to fix this in Help Topics by M2000 or
LMT Software.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 24

 Path Unavailable
Troubleshooting Guide

1. Possible Causes
(1) Failure in the bearing port of the path, the port Otherwise use the command LST PORTCTRLER to
including Ether port, PPP link, MLPPP link, UNI link, query whether the bearing port has been configured
IMA group, Fractional ATM link and NCOPT port. with the control SPU subsystem? If not, use the
(2) Path has no control SPU subsystem. command ADD PORTCTRLER to add the control
(3) Reset AAL2PATH fail, may caused by wrong SPU subsystem. If it is IPPATH, and the peer address
configuration of peer end. and the local address are in different subnet, then
(4) IPPATH ping check fail. check whether correct IP route is configured? If not,
use the command ADD IPRT to configure the IP
2. Handling Suggestions route.
(1) The cause is "Bearing port unavailable" or "All     N => Go to (3).
load balance ports unavailable"?
    Y => Use the command LST AAL2PATH or LST (3) The cause is "AAL2PATH reset fail"?
IPPATH to query the bearing port of the path, then     Y => Contact the maintenance engineers of the
check whether there is port fault alarm occur? If there peer end.
is the alarm, handle it in accordance with the handling     N => Go to (4).
suggestion.
    N => Go to (2). (4) The cause is "IPPATH ping fail"?
    Y => Check the IP address to be checked by LST
(2) The cause is "No control SPU sub-system"?
IPPATH command, and check whether the network
    Y => Use the command LST AAL2PATH to query connection is abnormal? If so, fix the network fault.
whether the bearing port is NULL. If it is NULL, modify     N => Contact Support Engineer.
it to a specific port.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 25

 Main Fault Alarms by RNC
Cell Alarms:
Alarm: Cell Unavailable
Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Major Cell Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=3, RNC ID=134, Cell ID=25729, NodeB ID=142, NodeB Name=UMGULA35,
27/6/2010
Cause=Common
01:55 2006
channel
Major Cell Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, RNC ID=134, Cell ID=4329, NodeB ID=128, NodeB Name=UMGULA21,
27/6/2010
Cause=NCP/CCP
01:55 failure.
2006
Major Cell Unavailable RNCMG06 Subrack No.=3, Slot No.=3, Subsystem No.=0, RNC ID=134, Cell ID=14329, NodeB ID=128, NodeB Name=UMGULA21,
27/6/2010
Cause=NCP/CCP
01:55 2006
failure.

Alarm: Cell Setup Failed

Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Major Cell Setup Failed RNCMG06 Subrack No.=2, Slot No.=4, Subsystem No.=1, RNC ID=134, Cell ID=5230, NodeB ID=182, NodeB Name=UMGURAR2,
27/6/2010
Cause=common
15:43 channel
2012
Major Cell Setup Failed RNCMG06 Subrack No.=2, Slot No.=4, Subsystem No.=1, RNC ID=134, Cell ID=15230, NodeB ID=182, NodeB Name=UMGURAR2,
27/6/2010
Cause=common
15:43 2012
channe
Major Cell Setup Failed RNCMG06 Subrack No.=2, Slot No.=4, Subsystem No.=1, RNC ID=134, Cell ID=25230, NodeB ID=182, NodeB Name=UMGURAR2,
27/6/2010
Cause=common
15:43 2012
channe

Alarm: Cell HSDPA Unavailable

Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Minor Cell HSDPA Unavailable RNCMG06 Subrack No.=1, Slot No.=3, Subsystem No.=3, RNC ID=134, Cell ID=1229, NodeB ID=71, NodeB NAME=UMGIUA04,29/6/2010
Cause=Empty
15:08 2030
Minor Cell HSDPA Unavailable RNCMG06 Subrack No.=1, Slot No.=3, Subsystem No.=3, RNC ID=134, Cell ID=11229, NodeB ID=71, NodeB NAME=UMGIUA04,
29/6/2010
Cause=Empty
15:08 2030
Minor Cell HSDPA Unavailable RNCMG06 Subrack No.=1, Slot No.=3, Subsystem No.=3, RNC ID=134, Cell ID=21229, NodeB ID=71, NodeB NAME=UMGIUA04,
29/6/2010
Cause=Empty
15:08 2030

Alarm: Cell Common Measurement Setup Failed

Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Critical Cell Common Measurement Setup Failed RNCMG06 Subrack No.=3, Slot No.=0, Subsystem No.=2, RNC ID=134, Cell ID=13029, NodeB ID=115, NodeB Name=UMGULA08,
27/6/2010
Meas Type=TCP
09:05 Periodic
2001
Critical Cell Common Measurement Setup Failed RNCMG06 Subrack No.=3, Slot No.=0, Subsystem No.=2, RNC ID=134, Cell ID=3029, NodeB ID=115, NodeB Name=UMGULA08,
27/6/2010
Meas Type=NonHsdpa
09:05 2001Tcp
Critical Cell Common Measurement Setup Failed RNCMG06 Subrack No.=3, Slot No.=0, Subsystem No.=2, RNC ID=134, Cell ID=3029, NodeB ID=115, NodeB Name=UMGULA08,
27/6/2010
Meas Type=TCP
09:05 Periodic
2001 M

Alarm: Cell Common Measurement Fault

Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Critical Cell Common Measurement Fault RNCMG06 Subrack No.=1, Slot No.=3, Subsystem No.=3, RNC ID=134, Cell ID=629, NodeB ID=45, NodeB Name=UMGCNS02,28/6/2010
Meas Type=RTWP
03:02 Periodic
2002
Critical Cell Common Measurement Fault RNCMG06 Subrack No.=1, Slot No.=3, Subsystem No.=2, RNC ID=134, Cell ID=20529, NodeB ID=44, NodeB Name=UMGCNS01,
28/6/2010
Meas Type=TCP
03:02 Periodic
2002
Critical Cell Common Measurement Fault RNCMG06 Subrack No.=1, Slot No.=3, Subsystem No.=2, RNC ID=134, Cell ID=20529, NodeB ID=44, NodeB Name=UMGCNS01,
28/6/2010
Meas Type=NonHsdpa
03:02 2002 T

Impact: In case of these alarms, the Cell service will be impacted.

For handle the alarm, you can get the description and actions to fix this in Help Topics by M2000 or
LMT Software.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 26

 Cell Unavailable
Troubleshooting Guide  Y => the AUDIT RESPONSE message from the
NodeB indicates this cell does not exist or cell
information is incorrect, so the RNC removes the cell.
1. Possible Causes Contact the maintenance engineers of the NodeB to
(1) Cell is removed (NBAP audit, the cell status is locate and solve the problem.
inconsistent between the RNC and NodeB).   N => go to (2).
(2) Cell is removed (NBAP resource state indication,
the cell status is inconsistent between the RNC and (2) The NodeB reports that the cell is unavailable
NodeB). Check whether the cause to the alarm is that the cell
(3) Common channel failure. reported by the NodeB is unavailable.
(4) Cell is blocked by NodeB.    Y => the AUDIT RESPONSE or RESOURCE
(5) NCP/CCP failure. STATUS INDICATION message indicates the cell is
(6) NodeB reports that the cell is unavailable for use. unavailable. Contact the maintenance engineers of
(7) Cell is configured with satellite transmission. the NodeB to locate and solve the problem.
However, the license of satellite transmission is    N => go to (3).
unavailable for use.
(8) When the cell load is light, the load-based multi- (3) Cell removed (NBAP resource state indication)
transceiver shutdown function deletes the cell. Check whether the cause to the alarm is cell removed
(NBAP resource state indication).
2. Handling Suggestions    Y => The RESOURCE STATUS INDICATION from
(1) Cell removed (NBAP audit) the NodeB indicates the corresponding LocalCell is
Check whether the cause to the alarm is cell removed removed, so the RNC removes the cell. Contact the
(NBAP audit) maintenance engineers of the NodeB to locate and
  solve the problem.
   N => go to (4).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 27

 Cell Unavailable
Troubleshooting Guide

(4) Common channel failure (6) NCP/CCP failure

Check whether there is an alarm 2008 Common 1) Check whether there is an alarm 2010 NCP Faulty
Channel Faulty not cleared. Wherein, [Cell ID] is the or 2011 CCP Faulty not cleared with the same
same as that in the current alarm. [NodeB ID] and [Cell ID] as those in the current alarm.
   Y => Handle this failure according to the related Where, the NodeB ID can be obtained through the
handling suggestions. command LST CELL.
   N => go to (5).   Y => handle this failure according to the related
handling suggestions.
(5) Cell blocked by NodeB   N => Contact Support Engineer.
Run the command DSP CELL to check whether the
cell is blocked.
   Y => No handling is necessary and the alarm
processing ends.
   N => go to (6).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 28

 Cell Setup Failed
Troubleshooting Guide
Step1: DSP CELL to check the cause of the cell setup failed. According the reason of the latest cell setup failure, take
the different measure.
Step2: If the reason is NCP unavailable or CCP unavailable, need check whether the signaling alarms exist. If the SALL
Link unavailable alarm is generated, firstly fixed the SAAL link issue.
Step3: If the reason is FP synchronization fails or the common channel setup fails, you can infer that the transmission
may be faulty. Go to check the AAL2PATH and IPPATH status.
Step4: If the result shows that the maximum downlink powers do not match, check whether the maximum downlink
power configured on the NodeB is greater than that on the RNC. If the maximum downlink power configured on the
NodeB is not greater than that on the RNC, you must modify the maximum downlink power configured on the

NodeB greater than that on the RNC.

Step 5: If the reason is NodeB return cell setup failure or Local cell not reported:
• On the NodeB, check whether the local cell is available. If the local cell on the NodeB is not available,
consult the NodeB personnel and stop the operations on the RNC.
• Check whether the frequency of the NodeB local cell is the same as that of the RNC cell. If the
frequencies are not the same, modify the frequencies to the same frequency.
Step6: If the Reason of the latest cell setup failure is Common channel setup failed ， and Reason of the
latest common channel setup failureis L2 resource allocation failed :Go to check whether the user
plane resources (DPU board) are available. You can run the DSP BRD command to check the state
of the installed DPU board. If all DPU boards are not available, you must install new DPU boards or
replace the DPU boards. If only one or several DSPs are unavailable, try toINH or RST these DSPs.
Step7: Run the LST NodeB and DSP License commands to check whether the related License functions
are enabled or not.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 29

 Cell HSDPA Unavailable N => The local cell does not have the HSDPA
capability. Go to 3).
Troubleshooting Guide  3) Run the MML command ADD CELLHSDPA to add
the HSDPA parameters of a specified cell.
1. Possible Causes 4) Check whether the alarm is cleared.
(1)The NodeB sends RESOURCE STATUS    Y => The alarm is cleared. The alarm handling is
INDICATION or AUDIT RESPONSE to RNC, complete.
indicating that local cell dose not has HSDPA    N => The alarm is not cleared. Contact Support
capability. Engineer.
(2)The NodeB sends RESOURCE STATUS (2) Check the resource operation status.
INDICATION or AUDIT RESPONSE to RNC, 1) Start Iub Interface Tracing on the LMT.
indicating that HS-DSCH resource operational state is 2) Run the MML command ADT RES to check
disabled. whether the value of the IE hS-DSCH-Resources-
(3) The allocation of HSDPA channel resources fails. Information-AuditRsp in the NBAP_AUDIT_RSP
(4) Waiting for the response of the reconfiguration of message is resourceOperationalState:enabled (0).
NodeB downlink physical shared channel times out.    Y => The HS-DSCH operation status of the local
(5) The returning of the reconfiguration physical cell is available for use. Contact Support Engineer.
shared channel by the NodeB fails.    N => The HS-DSCH operation status of the local
cell is not available for use. Go to 3).
2. Handling Suggestions 3) Contact the NodeB maintenance engineers to
(1) Check HSDPA performance. locate and solve the problem.
1) Start Iub Interface Tracing on the LMT. 4) Check whether the alarm is cleared.
2) Run the MML command ADT RES to check    Y => The alarm is cleared. The alarm handling is
whether the value of the IE HSDPA- complete.
Capability:HSDPA-capable in the NBAP_AUDIT_RSP    N => The alarm is not cleared. Contact Support
message is HSDPA-capable(0). Engineer.
   Y => The local cell has the HSDPA capability. Go to (3) Other causes.
(2).      Contact Support Engineer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 30

 Cell Common Measurement Setup 3) Check whether the alarm is cleared.
Failed   Y => The alarm is cleared. The alarm handling is
Troubleshooting Guide complete.
  N => The alarm is not cleared. Go to (2).
1. Possible Causes (2) Check whether the RNC receives invalid
(1) NodeB sends COMMON MEASUREMENT measurement reports continuously.
INITIATION FAILURE. 1) Check whether the RNC receives invalid
(2) NodeB has not sent COMMON MEASUREMENT measurement reports continuously
INITIATION RESPONSE/FAILURE for a specified   Y => Go to 2).
period of time.   N => Go to (3).
2. Handling Suggestions 2) There are parameter errors in the common
(1) Check whether the NodeB responds with the measurement report sent by the NodeB. Contact the
COMMON MEASUREMENT FAILURE INDICATION maintenance engineers of the NodeB to locate and
message. solve the problem. Go to 3).
1) Check whether the NodeB responds with the 3) Check whether the alarm is cleared.
COMMON MEASUREMENT FAILURE INDICATION   Y => The alarm is cleared. The alarm handling is
message. complete.
  Y => The NodeB responds with the COMMON   N => The alarm is not cleared. Go to (3).
MEASUREMENT FAILURE INDICATION message. (3) Check whether the RNC receives the
Go to 2). measurement report 10 seconds after the common
  N => The NodeB do not respond with the COMMON cell measurement is established.
MEASUREMENT FAILURE INDICATION message. 1) Check whether the RNC receives the measurement
Go to (2). report 10 seconds after the common cell
2) The meaning of the cause value in the COMMON measurement is established.
MEASUREMENT FAILURE INDICATION message   Y => Contact Support Engineer.
sent by the NodeB is dependent on the NodeB. You   N => The RNC does not receive the measurement
are advised to consult the maintenance engineers of report 10 seconds after the common cell
the NodeB. Go to 3). measurement is established. Go to 2).

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 31

 Cell Common Measurement Setup
Failed
Troubleshooting Guide
2) Use the LST CELL command to obtain the NodeB
ID. Go to 3).
3) Check whether there is non-cleared alarm 2010
NCP Faulty with the same NodeB ID as that in the
current alarm.
  Y => Go to 4).
  N => Go to 5).
4) Solve the transmission problem based on the
handling suggestions of the alarm 2010 NCP Faulty.
Go to 6).
5) Contact the maintenance engineers of the NodeB
to locate and solve the problem that the measurement
report is not sent. Go to 6).
6) Check whether the alarm is cleared.
  Y => The alarm is cleared. The alarm handling is
complete.
  N => The alarm is not cleared. Contact Support
Engineer.

(4) The configuration information of neighboring

cells is faulty when establishing SFN-SFN
observation time difference measurements.
  Contact Support Engineer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 32

 Cell Common Measurement Fault 3) Check whether the alarm is cleared.
Troubleshooting Guide     Y => The alarm is cleared. No further actions are
required.
1. Possible Causes     N => The alarm is not cleared. Continue to
(1) NodeB sends COMMON MEASUREMENT procedure (2).
FAILURE INDICATION. (2)Check whether RNC continuously received
(2) RNC receives invalid measurement reports invalid measurement reports.
continuously. 1) Check whether RNC continuously received invalid
(3) RNC does not receive any measurement report in measurement reports.
a long time.     Y => Continue to step 2).
(4) When establishing SFN-SFN measurements, error     N => Continue to procedure (3).
occurs to the configuration information of the 2) There are parameter errors in the common
neighboring cells. measurement report sent by the NodeB. Contact the
maintenance engineers of the NodeB to locate and
2. Handling Suggestions solve the errors. Continue to step 3).
(1) Check whether NodeB has sent COMMON 3) Check whether the alarm is cleared.
MEASUREMENT FAILURE INDICATION.     Y => The alarm is cleared. No further actions are
1) Check whether NodeB has sent COMMON required.
MEASUREMENT FAILURE INDICATION.     N => The alarm is not cleared. Continue to
    Y => Continue to step 2). procedure (3).
    N => Continue to procedure (2). (3)Check whether RNC has received any
2) Consult with the maintenance engineers of the measurement report 10 seconds after the setup of
NodeB, since the meaning of the cause values in the cell common measurement.
COMMON MEASUREMENT FAILURE INDICATION 1) Check whether RNC has received any
message sent by the NodeB is dependent on the measurement report 10 seconds after the setup of cell
NodeB. Continue to step 3). common measurement.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 33

 Cell Common Measurement Fault
Troubleshooting Guide

   Y => Contact Support Engineer.

    N => RNC has not received any measurement
report 10 seconds after the setup of cell common
measurement. Continue to step 2).
2) Obtain NodeB ID. Use the following command: LST
CELL. Continue to step 3).
3) Check whether there is a 2010 NCP Faulty alarm,
which has the same NodeB ID as that in the current
alarm, and has not been cleared.
    Y => Continue to step 4).
    N => Continue to step 5).
4) Handle the transport problem according to the
handling suggestions offered in 2010 NCP Faulty.
Continue to step 6).
5) Contact the maintenance engineers of the NodeB
to locate and solve the problem of not sending
measurement reports. Continue to step 6).
6) Check whether the alarm is cleared.
    Y => The alarm is cleared. No further actions are
required.
    N => The alarm is not cleared. Contact Support
Engineer.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 34

Contents

• 1. IuB Topology
• 1. Basic Script Configuration
• 2. Monitoring RAN Current Fault Alarms
• 3. Main Fault Alarms and Troubleshooting – RNC
• 4. Main Fault Alarms and Troubleshooting – NodeB
 Main Fault Alarms by NodeB
Transmission Link Alarms:
Alarm: E1/T1 Alarm Indication Signal (SIA) (ATM)
Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major E1/T1 Alarm Indication Signal UBACAR05 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=4 9/7/2010 14:32 2501
Major E1/T1 Alarm Indication Signal UBACAJ07 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=0 9/7/2010 14:41 2501
Major E1/T1 Alarm Indication Signal UBAAMA06 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=3 9/7/2010 19:05 2501

Alarm: E1/T1 Remote Alarm Indication (ATM)

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Minor E1/T1 Remote Alarm Indication UBAAMA06 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=4 8/7/2010 12:35 2502

Alarm: E1/T1 Loss of Frame Alignment (ATM)

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major E1/T1 Loss Of Frame Alignment UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=0 10/7/2010 13:59 2503
Major E1/T1 Loss Of Frame Alignment UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=0 10/7/2010 14:13 2503
Major E1/T1 Loss Of Frame Alignment UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=0 10/7/2010 14:17 2503

Alarm: E1/T1 Loss Of Signal (ATM)

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major E1/T1 Loss Of Signal UMGBRT15 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=0 10/7/2010 13:54 2500
Major E1/T1 Loss Of Signal UMGBRT15 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=1 10/7/2010 13:54 2500
Major E1/T1 Loss Of Signal UMGBRT15 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, E1T1 Port No.=2 10/7/2010 13:54 2500

Alarm: FE Interface Fault (IP)

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major FE Interface Fault UMGITU01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, FE Port No.=0 10/7/2010 17:34 2751
Major FE Interface Fault UMGITU01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, FE Port No.=0 10/7/2010 17:37 2751
Major FE Interface Fault UMGITU01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, FE Port No.=0 10/7/2010 17:42 2751

Alarm: IMA Link Loss Of Frame (ATM)

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major IMA Link Loss Of Frame UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, IMA Link No.=0 10/7/2010 14:47 2700
Major IMA Link Loss Of Frame UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, IMA Link No.=0 10/7/2010 15:37 2700
Major IMA Link Loss Of Frame UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, IMA Link No.=0 10/7/2010 16:00 2700

Impact: In case of these alarms, the NodeB service will be impacted.

For handle the alarm, you can get the description and actions to fix this in Help Topics by M2000 or
LMT Software.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 36

 E1/T1 Alarm Indication Signal
E1/T1 Remote Alarm Indication Check Whether E1/T1 Settings Are Correct
There are three types of  E1/T1 cables:
E1/T1 Loss of Frame Alignment 75Ω E1 cable - 120Ω E1 cable - 100Ω T1 cable -
NodeB and RNC trunk cables can be  interconnected in balance mode or imbalance
E1/T1 Loss Of Signal mode.
Balanced mode: E1/T1 signals are transmitted through two differential cables (twisted
Troubleshooting Guide pair cables) with the impedance of 75 ohms (E1) and 100 ohms (T1).
Unbalanced mode: E1/T1 signals are transmitted through one grounding cable and
one data cable (coaxial cable) with the impedance of 125 ohms.
1. Possible Causes 1) In balance mode, NodeB adopts 120Ω double twisted cable. Check whether the
1) E1/T1 settings are incorrect. setting of DIP switches S3 to S10 on the NDTI is as follows: The matched impedance
is 120 ohm. Neither the receive E1/T1 line nor the transmit E1/T1 line is grounded. 
2) E1/T1 transmission line connection is abnormal.
3) The E1/T1 equipment of this NodeB is abnormal. 2) In imbalance mode, NodeB adopts 75Ω coaxcial cable. Set DIP switches S3 to
S10 on the NDTI as follows: 
4) The E1/T1 trunk transmission fails. The matched impedance is 75 ohm. 
5) The E1/T1 equipment at the peer end is abnormal. The transmit E1/T1 cable is grounded and the receive E1/T1 cable is not grounded. 
Check whether the setting of DIP switches  matches the actual physical link setting.. 

2. Handling Suggestions 3) Execute DSP E1T1WORKMODE to display the work mode, clock mode, line code,
frame structure, loopback mode, transmission mode and matching impedance of the
1 Check the corresponding E1/T1 settings. alarming E1/T1 port. 
a.Check whether the E1/T1 settings are correct: Check whether the displayed information is consistent with the DIP switch settings
and the E1/T1 settings of the far end.
Y => The E1/T1 settings are correct. Go to Y => The displayed information is consistent with the DIP switch settings and the
Procedure 2. E1/T1 settings of the far end. The settings are correct.
N => The displayed information is not consistent with the DIP switch settings and the
N => The E1/T1 settings are incorrect. Go to step b. E1/T1 settings of the far end. The settings are not correct.
b.Correct E1/T1 settings. Note:
There are four E1/T1 line coding modes, including E1/HDB3, E1/AMI, T1/B8ZS, and
c.Check whether the alarm is cleared T1/AMI_ZCS.
Y => The alarm is cleared. The alarm handling ends. The default line coding mode in the E1 mode is HDB3. Different from HDB3 in line
coding principles, AMI has intrinsic defects. Interfacing between AMI and HDB3 will
N => The alarm is not cleared. Go to procedure 2. result in repetitive generation and clearance of E1/T1 LFA alarms and E1/T1 LMFA
alarms on AMI side. Therefore, AMI is not  recommended.
The default line coding mode in the T1 mode is B8ZS. Different from B8ZS in line
coding principles, AMI_ZCS has intrinsic defects. Interfacing between AMI_ZCS and
B8ZS will result in repetitive generation and clearance of E1/T1 LFA alarms and
E1/T1 LMFA alarms on AMI_ZCS side. Therefore, AMI_ZCS is not recommended.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 37

 E1/T1 Alarm Indication Signal
E1/T1 Remote Alarm Indication Y => The E1/T1 equipment of this NodeB is faulty. Go
to step b.
E1/T1 Loss of Frame Alignment N => The E1/T1 equipment of this NodeB is normal.
E1/T1 Loss Of Signal Go to procedure 4.
Troubleshooting Guide b.Handle E1/T1 equipment faults of this NodeB.
c.Check whether the alarm is cleared.
Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Go to procedure 4.
2 Check the connection of the corresponding
E1/T1 transmission line.
a.Check whether the connection of the corresponding Check the Connection of Corresponding E1/T1
E1/T1 transport line is secure: Transmission Link
Y => The connection of the E1/T1 transmission line is Check whether the connection of E1/T1 connector is correct. If the connector and
normal. Go to procedure 3. the cable are not joint properly, screw down the connector.

N => The connection of the E1/T1 transmission line is

not normal. Go to step b.
b.Reconnect the E1/T1 transmission line.
Check Whether E1/T1 Equipment of NodeB Is
c.Check whether the alarm is cleared:
Faulty
Y => The alarm is cleared. The alarm handling ends. There are two approaches to check whether the E1/T1 equipment of the NodeB is
N => The alarm is not cleared. Go to procedure 3. faulty :
Approach 1:
1)Execute SET E1T1LOP to set the E1/T1 link to local loop mode. 
2) Check whether the alarm is cleared.
3 Check the E1/T1 equipment of the NodeB. Y => The alarm is cleared. The E1/T1 equipment is not faulty.
a.Check whether the E1/T1 equipment of the NodeB N => The alarm is not cleared. The E1/T1 equipment is faulty.
Note: Execute SET E1T1LOP to stop the local loopback on the faulty E1/T1 after
is faulty: the check.
Approach 2:
1) Short-circuit the transmit and receive ends by using a functional E1/T1 link. 
2) Check whether the alarm is cleared.
Y => The alarm is cleared. The E1/T1 equipment is not faulty.
N => The alarm is not cleared. The E1/T1 equipment is faulty.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 38

 E1/T1 Alarm Indication Signal
E1/T1 Remote Alarm Indication
E1/T1 Loss of Frame Alignment
E1/T1 Loss Of Signal
Troubleshooting Guide

4 Check E1/T1 trunk transmission between the

Check Whether E1/T1 Trunk between NodeB and
NodeB and its peer end.
Far End Is Faulty
a.Check whether the E1/T1 trunk between the NodeB 1. Set the E1/T1 link connected with the far end to remote loopback mode.
and the far end is faulty: 2. Execute STR E1T1OFFLTST on the maintenance terminal to start offline test on
the BER of the alarming E1/T1 link. 
Y => The E1/T1 trunk is faulty. Go to step b. Check whether the BER is greater than 10-7.
N => The E1/T1 trunk is normal. Go to step c Y => The BER is greater than 10-7. The E1/T1 trunk between the NodeB and the far
end is faulty.
b.Ask the transmission maintenance personnel on the N => The BER is equal to or less than 10-7. The E1/T1 trunk between the NodeB
customer's side to check trunk lines. and the far end is normal.

c.The transmission devices at the far end are faulty.

Fix the devices.
d.The alarm handling ends.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 39

 FE Interface Fault 2 Check the parameters configured on both ends
Troubleshooting Guide a.Check the parameters configured on the FE port at
the peer end.
b.Carry out "LST ETHPORT" and check the
parameters configured on the FE port at the local
1. Possible Causes end.
1) The FE transmission line fails to connect well. c.Check if parameters configured on the FE ports at
2) Parameters configured on both ends of the FE both ends are consistent, such as the maximum
ports are inconsistent. transmission unit, bit rate and duplexing mode:
3) The FE port at the local end is faulty. Y => Parameters configured on the FE ports at both
4) The FE port at the peer end is faulty. ends are consistent. Go to procedure 4.
N => Parameters configured on the FE ports at both
2. Handling Suggestions ends are inconsistent. Go to step c to modify the
FE port configuration.
1 Check the Ethernet cable between FE ports.
a.Check if the Ethernet cables between the FE ports 3 Modify parameters configured on the FE ports.
are well connected. a.Negotiate the parameters on the FE ports at both
Y => The Ethernet cable is available. Go to procedure ends.
2. b.Carry out "SET ETHPORT" to keep parameters
N => The Ethernet cable is unavailable. Go to step b configured on the FE ports at both ends
to replace the Ethernet cable. consistent.
b.Replace the Ethernet cable. Parameters to be modified include:
c.Check whether the alarm is cleared. Maximum transmission unit
Y => The alarm is cleared. The alarm handling ends. Bit rate
N => The alarm is not cleared. Contact Huawei for Duplexing mode
technical support. c.Check whether the alarm is cleared:
Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Go to the procedure 4.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 40

 FE Interface Fault
Troubleshooting Guide

4 Check the FE port at the local end.

a.Carry out "RST ETHPORT" to reset the FE port.
Caution: Resetting the FE port shall interrupt services
carried on that port.
b.Check whether the alarm is cleared.
Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Go to procedure 5.

5 Check the FE port at the peer end.

a.Check if FE port at the peer end is faulty:
Y => The FE port at the peer end is faulty. Go to step
b.
N => The FE port at the peer end is normal. Contact
Huawei.
b.Handle the fault on the FE port at the peer end.
c.Check whether the alarm is cleared:
Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Contact Huawei for
technical support.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 41

 IMA Link Loss Of Frame
Troubleshooting Guide
1. Possible Causes
1) The E1/T1 link is faulty. 2 Check whether the setting of the IMA group that
2) The setting of the IMA group that hosts the IMA link hosts the IMA link is correct.
on the NodeB is faulty. a.Carry out "LST IMAGRP" on the maintenance
3) The IMA link on the local NodeB is faulty. terminal to query the configuration of the IMA
4) The IMA link on the peer end (RNC or NodeB group that hosts the IMA link on the NodeB.
connected with this NodeB) is faulty. b.Query the configuration of the IMA group that hosts
the IMA link at the far end RNC.
2. Handling Suggestions c.Check whether the scramble modes and IMA
1 Check whether the E1/T1 link is faulty. protocol versions of the IMA groups on the two
a.Carry out "LST ALMAF" on the maintenance ends are consistent. If not, set the IMA group as
terminal and check whether there is any alarm the negotiated scramble mode.
below on the E1/T1 link that holds the IMA link: d.Check whether the alarm is cleared:
"ALM-2500 E1/T1 Loss of Signal". Y => The alarm is cleared. The alarm handling ends.
"ALM-2501 E1/T1 Alarm Indication Signal". N => The alarm is not cleared. Go to procedure 3.
"ALM-2502 E1/T1 Remote Alarm Indication".
"ALM-2503 E1/T1 Loss of Frame Alignment". 3 Handle the faults in the IMA link of NodeB.
"ALM-2504 E1/T1 Loss of Multiframe Alignment". a.Carry out "RST IMAGRP" to reset the IMA group
Y => There is such an alarm. Go to step b. that hosts the IMA link.
N => There is no such alarm. Go to procedure 2. Caution: The IMA group reset will interrupt the service
b.Clear the alarm on the E1/T1 link according to the on the group.
handling suggestions of it. b.Check whether the alarm is cleared.
c.Check whether the alarm is cleared. Y => The alarm is cleared. The alarm handling ends.
Y => The alarm is cleared. The alarm handling ends. N => The alarm is not cleared. Go to step c.
N => The alarm is not cleared. Go to step b.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 42

 IMA Link Loss Of Frame
Troubleshooting Guide

c.Carry out "LST SAALLNK", "LST AAL2PATH" and

"LST TREELNKPVC" on the maintenance
terminal to check whether the IMAGRP is carried
on SAALLNK, AAL2PATH, and TREELNKPVC. If j.Check whether the alarm is cleared.
the IMAGRP is carried on these links, use the Y => The alarm is cleared. The alarm handling ends.
commands "RMV SAALLNK" and "RMV N => The alarm is not cleared. Go to procedure 4.
TREELNKPVC" to remove SAALLNK and
TREELNKPVC respectively. 4 Handle the faults in the IMA link of the peer end.
d.Carry out "RMV IMALNK" on the maintenance a.Check whether the IMA link of the peer end is faulty:
terminal to remove the IMA link from the IMA Y => The IMA link of the peer end is faulty. Go to step
group. b.
e.Carry out "ADD IMALNK" on the maintenance N => The IMA link of the peer end is not faulty.
terminal to add the IMA link back to the original Contact Huawei.
IMA group. b.Handle the faults in the IMA link faults of the peer
f.Check whether the alarm is cleared: end.
Y => The alarm is cleared. The alarm handling ends. c.Check whether the alarm is cleared:
N => The alarm is not cleared. Go to step h Y => The alarm is cleared. The alarm handling ends.
g.Reset the BBU. N => The alarm is not cleared. Contact Huawei.
h.Check whether the alarm is cleared:
Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Go to step j.
i.Replace the BBU.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 43

 Main Fault Alarms by NodeB
Signaling and Control Plane Link Alarms:
Alarm: ALCAP Fault
Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Critical ALCAP Fault UMGBRT15 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, Node Type=LOCAL 10/7/2010 13:54 2802
Critical ALCAP Fault UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, Node Type=LOCAL 10/7/2010 14:33 2802
Critical ALCAP Fault UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, Node Type=LOCAL 10/7/2010 14:47 2802

Alarm: CCP Fault

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major CCP Fault UMGBRT15 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, CCP Port Index=0 10/7/2010 13:54 2801
Major CCP Fault UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, CCP Port Index=0 10/7/2010 14:33 2801
Major CCP Fault UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, CCP Port Index=0 10/7/2010 14:47 2801

Alarm: NCP Fault

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Critical NCP Fault UMGBRT15 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL 10/7/2010 13:54 2800
Critical NCP Fault UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL 10/7/2010 14:47 2800
Critical NCP Fault UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL 10/7/2010 15:37 2800

Alarm: IPPATH Fault Alarm

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major IPPATH Fault Alarm UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, IP Path No.=1 10/7/2010 13:58 2760
Major IPPATH Fault Alarm UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, IP Path No.=1 10/7/2010 13:59 2760
Major IPPATH Fault Alarm UMGCKD01 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, IP Path No.=1 10/7/2010 13:59 2760

Alarm: AAL2 PATH Abnormal

Severity Name Alarm Source Location Information Occurrence Time(NT) Alarm ID
Major AAL2 PATH Abnormal UMGBET08 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, AAL2 Path Node Type=0, AAL2
10/7/2010
Path No.=4
20:15 2803
Major AAL2 PATH Abnormal UMGBET08 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, AAL2 Path Node Type=0, AAL2
10/7/2010
Path No.=4
21:08 2803
Major AAL2 PATH Abnormal UMGBET08 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, AAL2 Path Node Type=0, AAL2
10/7/2010
Path No.=4
21:12 2803

Impact: In case of these alarms, the NodeB service will be impacted.

For handle the alarm, you can get the description and actions to fix this in Help Topics by M2000 or
LMT Software.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 44

 ALCAP Fault
Troubleshooting Guide

1. Possible Causes 2 Check whether the property settings of the

1) The physical link that carries the ALCAP is faulty. SAAL link and the PVC that carries the ALCAP
2) The properties of the PVC that carries the ALCAP are correct.
are not consistent with those at the peer end. a.Run "LST AAL2NODE" on the LMT to query the
3) The property settings of the SAAL link that carries number of the SAAL link that carries the faulty
the ALCAP are not correct. ALCAP. Then run "LST SAALLNK" to query the
4) The hardware of BBU board is faulty. property settings of the related SAAL link and the
ATM link.
2. Handling Suggestions b.Check whether the settings of the port number, VPI,
1 Check the physical link that carries the ALCAP VCI, and PVC and the property settings of the
node.
a.Use "LST AAL2NODE" on the maintenance SAAL link are consistent with the peer end.
terminal to query the number of the SAAL link that Y => The properties on the two ends are consistent.
carries the faulty ALCAP. Go to procedure 3.
b.Use "LST ALMAF" to check whether alarms related N => The properties on the two ends are not
to the lower-layer links that carry the SAAL link are consistent. Go to step c.
reported. The lower-layer links consist of UNI link,
IMA link, fractional ATM link, and STM-1 link. c.Run "LST AAL2PATH" on the LMT to query all the
Y => Alarms are reported. Go to step 3. AAL2PATHs configured on this ALCAP.
N => Aalarms are not reported. Go to procedure 2. d.Run "RMV AAL2PATH" on the LMT to remove all
c.Handle the alarms related the lower-layer links. the AAL2PATHs configured on this ALCAP.
d.Check whether the alarm is cleared: Caution: It will cause all services of the NodeB
Y => The alarm is cleared. The alarm handling ends. interrupted to remove this ALCAP node.
N => The alarm is not cleared. Go to procedure 2. Removing this ALCAP node interrupts all the
services carried on the NodeB.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 45

 ALCAP Fault
Troubleshooting Guide

Replace BBU
e.Run "RMV AAL2NODE" on the LMT to remove the Caution: Replace BBU with discretion because the it will interrupt the
services carried on it.
faulty ALCAP node. Follow the procedure below to replace BBU:
f.Run "ADD AAL2NODE" on the LMT to add a new 1)Execute ULD CFGFILE to upload NodeB data configuration file. Back
up the NodeB data configuration file to local maintenance terminal.
ALCAP node. The value of PVC and the SAAL 2)Turen off the BBU. Disconnect all the cables on the BBU.
link properties are consistent with those at the 3)Replace the faulty BBU.
4)Reconnect all the cables to the new BBU. Turn on the new BBU. Wait
peer end. until the BBU is started.
g.Run "ADD AAL2PATH" on the LMT to reset AAL2 5)Execute LST VER to list the active software version and BOOTROM
version. Check whether the versions are correct.
paths to the new ALCAP. Y => Versions are correct. Go to step 7).
h.Check whether the alarm is cleared: N => Versions are incorrect. Execute DLD SOFTWARE to download the
NodeB software version and BOOTROM version.
Y => The alarm is cleared. The alarm handling ends. 6)Execute ACT SOFTWARE to activate NodeB BOOTROM version, and
then the software version. Wait until BBU is started.
N => The alarm is not cleared. Go to procedure 3. 7)Execute DLD CFGFILE to download standby NodeB data configuration
file.
8)Execute RST NODEB to restart NodeB. Wait until BBU is started.
3 Replace the BBU. 9)Execute LST ALMAF ti list all the active alarms. Check whether there is
a.Replace the BBU. an alarm of "ALM-3500 Board Version Not Match"
Y => There is such an alarm. Go to step 10).
b.Check whether the alarm is cleared: N => There is no such alarm. Go to step 12).
Y => The alarm is cleared. The alarm handling ends. 10)Execute ACT SOFTWARE to activate BOOTROM version of BBU.
N => The alarm is not cleared. Contact Huawei. 11)Execute RST BRD to reset BBU.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 46

 CCP Fault Go to "2 Check whether the SCTP bearing physical
Troubleshooting Guide link is faulty."
N => The SCTP link is not configured. Go to "4
Check whether the SAAL bearing physical link
1. Possible Causes is faulty".
1) The links carried the active and the standby CCPs
are faulty. 4 Check whether the SAAL bearing physical link
2) The PVC property settings of the SAAL that carries is faulty.
the CCP is inconsistent with the settings of the a.Use the MML command "LST IUBCP" to query the
peer end. faulty CCP bearing links and whether the SAAL
3) The property settings of the SAAL that carries the link is configured.
CCP are unreasonable. Y => The SAAL link is configured. Use "LST
4) The IP route between the NodeB and the RNC is SAALLNK" to query the SAAL link that carries the
not configured on the SCTP that carries the CCP. CCP. Go to b.
5) The property settings of the SCTP that carries the N => The SAAL link is not configured. Go to "6 Check
CCP are unreasonable. whether the alarm is cleared."
6) The hardware of the board is faulty. b.Use "LST ALMAF" to check whether there are any
alarms generated on the low-layer links that carry
2. Handling Suggestions the SAAL link. The low-layer links consist of the
1 Check the type of the corresponding bearing UNI link, IMA link, fractional ATM link, and STM-1
physical link. link.
a.Use "LST IUBCP" to query the link that carries the Y => There are alarms generated on the low-layer
faulty CCP. Check whether the SCTP link is links. Go to c.
configured. N => There is not any alarm generated on the low-
Y => The SCTP link is configured. Then use "LST layer links. Go to "5 Check whether the PVC
SCTPLNK" to query the corresponding physical settings and the property settings of the SAAL
link. link is correct."

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 47

 CCP Fault
Troubleshooting Guide c.Use "RMV IUBCP" to remove the faulty CCP and
use "RMV SAALLNK" to remove the
corresponding SAAL link.
c.Handle the alarms that are related to the lower-layer d.Use "ADD SAALLNK" and "ADD IUBCP" to
links. reestablish the CCP link. Here, the PVC property
d.Check whether the alarm is cleared: and link property of the SAAL link should be set
Y => The alarm is cleared. Go to "7 Check whether to be consistent with those of the peer end.
the status of the SAAL link is normal."
N => The alarm is not cleared. Go to "5 Check 6 Check whether the alarm is cleared:
whether the PVC settings and the property a.Y => The alarm is cleared. "Go 7 Check whether the
settings of the SAAL link is correct." status of the SAAL link is normal."
N => The alarm is not cleared. Go to "8 Replace the
5 Check whether the PVC settings and the Board."
property settings of the SAAL link is correct.
a.Use "LST IUBCP" to query the link number of the 7 Check whether the status of the SAAL link is
CCP bearing SAAL link. Then use "LST normal.
SAALLNK" to query the property settings of the 8 Replace the board
corresponding SAAL link and the ATM link. a.Replace the Board
b.Check whether the port number, VPI, VCI, PVC b.Check whether the fault of the board is cleared:
bandwidth, and the SAAL link property are set to Y => The alarm is cleared. Go to "8 Check whether
be consistent with those of the peer end. the status of the CCP bearing link is normal."
Y => Consistent. Go to "6 Check whether the alarm is Y => The alarm is cleared. Go to "10 Contact
cleared." Huawei."
N=> Inconsistent. Go to c. 9 Check whether the status of the CCP bearing
link is normal.
10 Contact Huawei.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 48

 4 Check whether the SAAL bearing physical link is
NCP Fault faulty.
Troubleshooting Guide a.Use the MML command "LST IUBCP" to query the
faulty NCP bearing links and whether the SAAL
link is configured.
1. Possible Causes Y => The SAAL link is configured. Use "LST
1) The links carried the active and the standby NCPs are SAALLNK" to query the SAAL link that carries the
faulty. NCP. Go to b.
2) The PVC property settings of the SAAL that carries the N => The SAAL link is not configured. Go to "6 Check
NCP is inconsistent with the settings of the peer end. whether the alarm is cleared."
3) The property settings of the SAAL that carries the NCP b.Use "LST ALMAF" to check whether there are any
are unreasonable.
alarms generated on the low-layer links that carry
4) The IP route between the NodeB and the RNC is not
the SAAL link. The low-layer links consist of the
configured on the SCTP that carries the NCP.
5) The property settings of the SCTP that carries the NCP UNI link, IMA link, fractional ATM link, and STM-1
are unreasonable. link.
6) The hardware of the board is faulty. Y => There are alarms generated on the low-layer
2. Handling Suggestions links. Go to c.
1 Check the type of the corresponding bearing N => There are not any alarms generated on the low-
physical link. layer links. Go to "5 Check whether the PVC
a.Run "LST IUBCP" to query the NCP bearing links. Check settings are correct."
whether the SCTP link is configured. c.Handle the alarms that are related to the lower-layer
Y => The SCTP link is configured. Then use "LST links.
SCTPLNK" to query the corresponding physical link. d.Check whether the alarm is cleared:
Go to "2 Check whether the SCTP bearing physical Y => The alarm is cleared. Go to "7 Check whether
link is faulty."
the status of the SAAL link is normal."
N => The SCTP link is not configured. Go to "4 Check
N => There are not any alarms generated on the low-
whether the SAAL bearing physical link is faulty".
layer links. Go to "5 Check whether the PVC
settings are correct."

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 49

 NCP Fault
Troubleshooting Guide

6 Check whether the alarm is cleared:

5 Check whether the property settings of the a.Y => The alarm is cleared. Go to "7 Check whether
SAAL link and the PVC that carries the NCP the status of the SAAL link is normal."
are correct. N => The alarm is not cleared. Go to "8 Replace the
a.Use "LST IUBCP" to query the link number of the Board."
NCP bearing SAAL link. Then use "LST
SAALLNK" to query the property settings of the
corresponding SAAL link and the ATM link. 7 Check whether the status of the SAAL link is
b.Check whether the port number, VPI, VCI, PVC normal.
bandwidth, and the SAAL link property are set to
be consistent with those of the peer end. 8 Replace the board
Y => Consistent. Go to "6 Check whether the alarm is a.Replace the Board
cleared." b.Check whether the fault of the board is cleared:
N=> Inconsistent. Go to c. Y => The alarm is cleared. Go to "9 Check whether
c.Use "RMV IUBCP" and "RMV SAALLNK" on the the status of the NCP bearing link is normal."
maintenance terminal to remove the faulty NCP Y => The alarm is cleared. Go to "10 Contact
link and the corresponding SAAL link. Huawei."
d.Use "ADD SAALLNK" and "ADD IUBCP" to
reestablish the NCP link. Here, the PVC property 9 Check whether the status of the NCP bearing
and link property of the SAAL link should be set link is normal.
to be consistent with those of the peer end. 10 Contact Huawei.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 50

 IPPATH Fault Alarm
Y => The alarm is cleared. The alarm handling ends.
Troubleshooting Guide
N => The alarm is not cleared. Go to procedure 2.
2 Check whether the route is correctly configured.
1. Possible Causes a.Run "DSP IPRT" to check whether the IP route of
1) The FE port that carries the IP path, the PPP link, the link that carries the IP path is configured.
the MP group, or the PPPoE link is faulty. Y => Configured. Go to procedure 3.
2) The IP route between the NodeB and the RNC is N => Not configured. Go to step b.
not configured. b.Run "ADD IPRT" to add the IP route of the related
3) Ping the IP path. The route of the carrier network in link.
the middle is not correctly configured, or the c.Check whether the alarm is cleared.
carrier network shields the ping message. Y => The alarm is cleared. The alarm handling ends.
4) The hardware of the board that carries the IP path Y => The alarm is not cleared. Go to procedure 3.
is faulty.
2. Handling Suggestions 3 Check whether the carrier network
1 Check whether the link that carries the IP path configuration is correct.
is operational. a.Contact the network administrator to check whether
a.Run "LST IPPATH" to query the link that carries the the route of the carrier network is correctly
faulty IP path. configured and the carrier network does not
b.Run "LST ALMAF" to check whether the alarms shield the ping message. If the route of the carrier
related to the link that carries the IP path are network is correctly configured and the carrier
reported. network does not shield the ping message, Go to
Y =>Reported. Go to step c. procedure 4. Otherwise, ask the network
N =>Not reported. Go to procedure 2. administrator to correct the network configuration.
c.Handle the alarms related to the link that carries the b.Check whether the alarm is cleared.
IP path. Y => The alarm is cleared. The alarm handling ends.
d.Check whether the alarm is cleared. N => The alarm is not cleared. Go to procedure 4.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 51

 IPPATH Fault Alarm
Troubleshooting Guide

Replace Board
Caution ： Replace Board with discretion because it will
interrupt the services carried on it.
1) Disconnect the cables from the board, and then
remove the board.
4 Replace the board. 2) Install a new board. Then connect the cables to the
a.Replace the Board. board. Wait until the board is started.
b.Check whether the alarm is cleared. 3) Execute DSP BRDVER to check if the BootRom
Y => The alarm is cleared. The alarm handling ends. version and software version of the board are correct:
N => The alarm is not cleared, Contact Huawei. Y => correct. Go to step 4.
N => incorrect. Execute ACT SOFTWARE to activate the
BootRom and software.
4) The board replacement is complete.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 52

 AAL2 PATH Abnormal
c.Wait until the upper level NodeB resetting is
Troubleshooting Guide
completed and the NodeB works normally. Check
whether the alarm is cleared:
1. Possible Causes Y => The alarm is cleared. The alarm handling ends.
1) The upper level NodeB is reset. N => The alarm is not cleared. Go to step d.
2) The PVC setting of the upper level NodeB is d.Carry out "LST TREELNKPVC" on the maintenance
incorrect. terminal to check whether the networking PVC
3) The physical link that holds the AAL2 PATH is setting of the upper level NodeB is correct.
faulty. Y => The setting is correct. Go to procedure 2.
4) The E1/T1 or fiber connection between RNC and N => The setting is not correct. Go to step e.
NodeB is incorrect. e.Carry out "RMV TREELNKPVC" or "ADD
5) The board on the NodeB is faulty. TREELNKPVC" on the maintenance terminal to
6) The board on the RNC is faulty. modify the networking PVC setting of the upper
level NodeB.
2. Handling Suggestions f.Check whether the alarm is cleared:
Y => The alarm is cleared. The alarm handling ends.
1 Clear the faults in the upper level NodeB. N => The alarm is not cleared. Go to procedure 2.
a.Check whether the local NodeB has any upper level
NodeB: 2 Check whether there is any alarm on the
Y => There is an upper level NodeB of the local physical link holding the AAL2 PATH.
NodeB. Go to step b. a.Carry out "LST ALMAF" on the maintenance
N => There is no upper level NodeB of the local terminal and check whether there is any alarm on
NodeB. Go to procedure 2. the physical link that holds the AAL2 PATH,
b.Check whether the upper level NodeB is reset: regarding E1, UNI, IMA, Fractional ATM or fiber:
Y => The upper level NodeB is reset. Go to step c. Y => There is such an alarm. Go to step b.
N => The upper level NodeB is not reset. Go to step N => There is no such alarm. Go to procedure 3.
d.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 53
 AAL2 PATH Abnormal
Troubleshooting Guide

b.Handle the alarms of E1/T1, UNI, Fractional ATM 4 Reset the NodeB board holding the AAL2 PATH.
and fiber. a.Reset the BBU.
c.Check whether the alarm is cleared: b.Check whether the alarm is cleared:
Y => The alarm is cleared. The alarm handling ends. Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Go to procedure 3. N => The alarm is not cleared. Go to procedure 5.

3 Check E1/T1 and fiber connection between 5 Reset the RNC board holding the AAL2 PATH.
NodeB and RNC. a.Reset the RNC board holding the AAL2 PATH. The
a.Check whether the E1/T1 or fiber connection board can be WOIE, WBIE or WXIE.
between RNC and NodeB is correct. b.Check whether the alarm is cleared:
Y => The E1/T1 or fiber connection between RNC and Y => The alarm is cleared. The alarm handling ends.
NodeB is correct. Go to procedure 4. N => The alarm is not cleared. Contact Huawei.
N => The E1/T1 or fiber connection between RNC
and NodeB is not correct. Go to step b.
b.Reconnect the E1/T1 cable or optical fiber correctly.
c.Check whether the alarm is cleared.
Y => The alarm is cleared. The alarm handling ends.
N => The alarm is not cleared. Go to procedure 4.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 54

 Main Fault Alarms by NodeB
Cell Alarms:

Alarm: BBU Optical Interface Abnormal

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Critical BBU Optical Interface Abnormal UMGBAR09 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, Faulty Module=Optical module
10/7/2010
2, Cause=Rx
14:46 abnormal
1001
Critical BBU Optical Interface Abnormal UMGARG07 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, Faulty Module=Optical module
12/7/2010
2, Cause=Rx
15:43 abnormal
1001
Critical BBU Optical Interface Abnormal UMGBAR09 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=NULL, Faulty Module=Optical module
13/7/2010
1, Cause=Rx
10:43 abnormal
1001

Alarm: Local Cell Unusable

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major Local Cell Unusable UMGBAR09 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=4, Local Cell ID=2 10/7/2010 14:46 4033
Major Local Cell Unusable UMGBET12 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=1, Local Cell ID=0 11/7/2010 11:07 4033
Major Local Cell Unusable UMGBET12 Cabinet No.=0, Subrack No.=0, Slot No.=0, Board type=HBBU, Fault code=1, Local Cell ID=1 11/7/2010 11:07 4033

Alarm: RRU Communication Abnormal

Severity Name Alarm Source Location Information Occurrence Time(NT)Alarm ID
Major RRU Communication Abnormal UMGBAR09 Cabinet No.=0, Subrack No.=22, Slot No.=0, Board type=MRRU, Fault code=NULL 10/7/2010 14:46 1156
Major RRU Communication Abnormal UMGARG06 Cabinet No.=0, Subrack No.=21, Slot No.=0, Board type=MRRU, Fault code=NULL 12/7/2010 09:25 1156
Major RRU Communication Abnormal UMGARG07 Cabinet No.=0, Subrack No.=22, Slot No.=0, Board type=MRRU, Fault code=NULL 12/7/2010 15:43 1156

Impact: In case of these alarms, the Cell service will be impacted.

For handle the alarm, you can get the description and actions to fix this in Help Topics by M2000 or
LMT Software.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 55

 BBU Optical Interface Abnormal 2. Handling Suggestions
Troubleshooting Guide 1 Check the RRU chain configuration
a.Carry out "LST RRUCHAIN" to check whether the
faulty optical interface is configured with
redundant RRU chain:
Y =>There is redundant RRU chain. Go to step b.
1. Possible Causes N =>There is no redundant RRU chain. Go to
1) The optical cable between BBU and RRU is faulty. procedure 2.
2) The optical connector on the BBU is not in good b.Carry out "RMV RRUCHAIN" to remove the
contact. redundant RRU chain.
3) The optical module on the BBU is not in good c.Check whether the alarm is cleared.
contact. Or the optical module is faulty. Y =>The alarm is cleared. The alarm handling ends.
4) The BBU is faulty. N =>The alarm is not cleared. Go to procedure 2.
5) The optical connector on the lower level RRU is not
in good contact. 2 Check the BBU optical connector.
6) The optical module on the lower level RRU is not in a.In the BBU near end, check the optical connector on
good contact. Or the optical module is faulty. the faulty optical interface and re-insert it tightly.
7) The lower level RRU is faulty. b.Check whether the alarm is cleared.
8) The RRU chain is not correctly configured. The Y =>The alarm is cleared. The alarm handling ends.
RRU chain is configured in the unused optical N =>The alarm is not cleared. Go to step c.
interface. c.Carry out optical loopback in the near end.
9) The optical modules are mismatching between d.Check whether the alarm is cleared.
BBU and RRU. Y => The alarm is cleared. Cancel the optical
loopback and restore the optical connection. Go
to procedure 3.
N =>The alarm is not cleared. Go to step e.
e.Re-insert the optical module.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 56

 BBU Optical Interface Abnormal
Troubleshooting Guide
3 Check the RRU optical connector.
a.In the near end of the lower level RRU of the BBU,
check the optical connector on the optical
interface, then reinsert it tightly.
f.Check whether the alarm is cleared. b.Check whether the alarm is cleared.
Y =>The alarm is cleared. Go to step j. Y =>The alarm is cleared. The alarm handling ends.
N =>The alarm is not cleared. Go to step g. N =>The alarm is not cleared. Go to step c.
g.Replace the optical interface module. c.Carry out the optical loopback in the near end.
h.Check whether the alarm is cleared. d.Check whether the alarm is cleared.
Y =>The alarm is cleared. Go to step j. Y =>The alarm is cleared. Cancel the optical loopback
N =>The alarm is not cleared. Go to step i. and restore the optical connection. Go to
i.Replace the BBU. procedure 4.
j.Cancel the optical loopback and restore the optical N =>The alarm is not cleared. Go to step e.
connection. Check whether the alarm is cleared. e.Re-insert the optical module tightly.
Y =>The alarm is cleared. The alarm handling ends. f.Check whether the alarm is cleared.
N =>The alarm is not cleared. Go to procedure 3. Y =>The alarm is cleared. Go to step j.
N =>The alarm is not cleared. Go to step g.
g.Replace the optical interface module.
h.Check whether the alarm is cleared.
Replace the optical interface module Y =>The alarm is cleared. Go to step j.
1) Pull out the fiber from the BBU or RRU.
2) Pull out the optical module. Insert a new optical module. N =>The alarm is not cleared. Go to step i.
3) Reinsert the fiber to the BBU or RRU. i.Replace the RRU.
j.Cancel the optical loopback and restore the optical
connection. Check whether the alarm is cleared.
Y =>The alarm is cleared. The alarm handling ends.
N =>The alarm is not cleared. Go to procedure 4.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 57

 BBU Optical Interface Abnormal
Troubleshooting Guide

4 Check the optical modules type between BBU

and RRU. Replace the RRU
Caution: Replace RRU with discretion because the it will interrupt the
a.Check the optical modules type between BBU and services carried on it.
RRU(Single-Mode/ Multi-mode Follow the procedure below to replace RRU:
, 1.25G/2.5G). 1)Turen off the RRU.
2)Disconnect all the cables on the RRU such as optical fibers and
Y =>Type matching. Go to step c. feeders..
N =>Type mismatching. Go to step b. 3)Pull out the faulty RRU.
4)Insert the back up RRU.
b.Replace the optical interface module. 5)Reconnect all the cables to the new RRU.
c.Check whether the alarm is cleared. 6)Turn on the new RRU. Wait until the RRU is started.
Y =>The alarm is cleared. The alarm handling ends. 7)Execute LST BRDVER to list the active BOOTROM version. Check
whether the version is correct.
N =>The alarm is not cleared. Go to procedure 5. Y => Version is correct. Go to step 10).
N => Version is incorrect. Go to step 8).
8)Execute ACT SOFTWARE to activate board BOOTROM version.
5 Check the optical cable between BBU and RRU. 9)Execute RST BRD to reset RRU.
a.Check the optical cable between BBU and RRU. 10)RRU is replaced.
b.Check whether the alarm is cleared.
Y =>The alarm is cleared. The alarm handling ends.
N =>The alarm is not cleared. Contact Huawei.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 58

 Local Cell Unusable
Troubleshooting Guide
b.Clear the alarm according to help information.
1. Possible Causes c.Check whether the alarm is cleared:
1) BBU failure. Y =>The alarm is cleared. The alarm handling ends.
2) RRU failure. N =>The alarm is not cleared. Contact Huawei.
3) Data Configuration Error. 3 Clear the fault of DL baseband resources
4) Baseband resources are insufficient. a.List active alarms in the alarm management system.
Then check if there are alarms related to the
2. Handling Suggestions BBU.
1 Find out possible causes of the fault. Y => Alarms on the BBU persist. Go to step b.
a.Find out possible causes of the fault from alarm N => No alarms on the BBU persist. Carry out "DSP
parameters: LOCELL" to check whether the cell configuration
Fault code = 0: Go to procedure 2. is beyond the processing capability of the
Fault code = 1: Go to procedure 3. baseband resources.
Fault code = 2: Go to procedure 4. b.Clear the alarm according to help information.
Fault code = 3 or 4: Go to procedure 5. c.Check whether the alarm is cleared:
Fault code = 5: Go to procedure 6. Y =>The alarm is cleared. The alarm handling ends.
N =>The alarm is not cleared. Contact Huawei.
4 Clear the fault in the baseband and RF interface
2 Clear the fault of UL baseband resources processing resources
a.List active alarms in the alarm management system. a.List active alarms in the alarm management system.
Then check if there are alarms related to the Then check if there are alarms related to the
BBU. BBU.
Y => Alarms on the BBU persist. Go to step b. b.Clear the alarm according to help information.
N => No alarms on the BBU persist. Carry out "DSP c.Check whether the alarm is cleared:
LOCELL" to check whether the cell configuration Y =>The alarm is cleared. The alarm handling ends.
is beyond the processing capability of the N =>The alarm is not cleared. Contact Huawei.
baseband resources.
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 59
 Local Cell Unusable
Troubleshooting Guide

6 Clear the incompatibility between the sector

5 Clear the fault of RF resources configuration and the physical equipment
a.List active alarms in the alarm management system. a.Check whether the configuration of the sector is the
Then check if there are alarms related to the same as the actual physical equipment and
RRU. whether different types of RRU are
b.Clear the alarm according to help information. interconnected:
c.Check the following configurations: Y=> Different types of RRU is interconnected. Go to
a) Whether the local cell frequency is within the step 2.
frequency range that the RRU supports. N=> No different types of RRU is interconnected.
b) Whether the local cell power is within the power Contact Huawei.
range that the RRU supports. b.Remove the cell and sector, reestablish the sector
c) Whether the local cell power of the same RRU is and cell with correct configurations or Replace
within the power range that the RRU supports. the RRU to make the configuration of the sector
d.Modify the configurations according to the result. the same as the actual physical equipment.
e.Clear the incompatibilty between the sector c.Check whether the alarm is cleared:
configuration and the physical equipment Y =>The alarm is cleared. The alarm handling ends.
according to procedure 6. N =>The alarm is not cleared. Contact Huawei.
f.Check whether the alarm is cleared:
Y =>The alarm is cleared. The alarm handling ends.
N =>The alarm is not cleared. Contact Huawei.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 60

 RRU Communication Abnormal configured on the correct optical port and whether the
Troubleshooting Guide RRU is configured on the correct RRU chain/ring.
Y => The configuration is correct. Go to procedure 3.
1. Possible Causes N => The configuration is wrong. Go to procedure 2.
1) The RRU configuration is wrong. 2 Modify the RRU configuration.
2) The optical module on the BBU unit is not in a.Run the MML commands "SET RRUBREAKPOS",
position or is faulty. "RMV RRU", and "RMV RRUCHAIN" to remove
3) The connector of the optical cable on the BBU unit the wrong configuration. Run the MML
is not in position. commands "ADD RRUCHAIN" and "ADD RRU"
4) The connector of the optical cable on the lower- to re-configure the RRU.
level RRU is not in position. b.Check whether the alarm is cleared.
5) The optical module on the lower-level RRU is not in Y =>The alarm is cleared. No further action is
position or is faulty. required.
6) The uplink or downlink optical module on the N =>The alarm is not cleared. Go to procedure 3.
upper-level RRU is not in position or is faulty. 3 Check the BBU unit.
7) The uplink or downlink connector of the optical a.Open the alarm browsing window or run the MML
cable on the upper-level RRU is not in position. command "LST ALMAF" to query the current
8) The uplink optical module on the current-level RRU alarms. Check for "ALM-5025 Board
is not in position or is faulty. Communication Abnormal".
9) The uplink connector of the optical cable on the Y => The alarm is generated. Clear the alarm
current-level RRU is not in position. according to the handling procedures of the
10) The current-level RRU itself is faulty. related alarm. Then, go to step b.
11) The BBU unit is faulty. N => The alarm is not generated. Go to procedure 4.
2. Handling Suggestions b.Check whether the alarm is cleared.
1 Check the RRU configuration. Y => The alarm is cleared. No further action is
a.Run the MML commands "LST RRUCHAIN" and required.
"LST RRU" to check whether the RRU chain/ring N => The alarm is not cleared. Go to procedure 4.
is
HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 61
 RRU Communication Abnormal
Troubleshooting Guide
Y => The alarm is cleared. No further action is
required.
4 Check the CPRI interface of the BBU unit and N => The alarm is not cleared. Go to step c.
the upper-level RRU. c.On the lower-level RRU side, replace the uplink
a.Open the alarm browsing window or run the MML optical module of the RRU. Go to step d.
command "LST ALMAF" to query the current d.Check whether the alarm is cleared.
alarms. Check for "ALM-1002 BBU CPRI Y => The alarm is cleared. No further action is
Interface Abnormal". Check for "ALM-1304 required.
Downlink CPRI Interface Abnormal" generated on N => The alarm is not cleared. Go to procedure 6.
the upper-level RRU.
Y => The alarm is generated. Clear the alarm 6 Power off and reset the RRU.
according to the handling procedures of the a.On the RRU side, power off and then Reset the
related alarm. Then, go to step b. RRU. Wait until the RRU startup is complete.
N => The alarm is not generated. Go to procedure 5. b.Check whether the alarm is cleared.
b.Check whether the alarm is cleared. Y => The alarm is cleared. No further action is
Y => The alarm is cleared. No further action is required.
required. N => The alarm is not cleared. Go to procedure 7.
N => The alarm is not cleared. Go to procedure 5.
7 Replace the RRU.
5 Check the optical module and the connector of a.Replace the RRU.
the optical cable of the current-level RRU. b.Check whether the alarm is cleared.
a.On the lower-level RRU side, plug the uplink Y => The alarm is cleared. No further action is
connector into the optical module to ensure that required.
they are in good contact. Go to step b. N => The alarm is not cleared. Contact Huawei.
b.Check whether the alarm is cleared.

HUAWEI TECHNOLOGIES CO., LTD. Huawei Confidential Page 62

Thank you
www.huawei.com