Вы находитесь на странице: 1из 4

ALM-29204 X2 Interface Fault

Page 1 of 4

ALM-29204 X2 Interface Fault

Description

This alarm is reported when the processing errors occur at the X2 Application Protocol (X2AP) layer, or when the related Stream Control Transmission Protocol (SCTP) link malfunctions.

Parameters

Parameter Name Parameter Description X2INTERFACEID X2 interface ID CN Operator ID Index of the operator
Parameter Name
Parameter Description
X2INTERFACEID
X2 interface ID
CN Operator ID
Index of the operator
Problem
Specific problem (Lower-layer link fault, X2 link setup failure)
Description
Description of the target element
Impact on the System Alarm Severity Alarm Impact Major The local base station releases the
Impact on the System
Alarm Severity
Alarm Impact
Major
The local base station releases the UEs involved in the inter-base station handover procedure on the correlated X2
interface. Before the alarm is cleared, the local base station cannot allow the inter-base station handover on the faulty X2
interface, and the local base station does not support the inter-cell interference coordination with the corresponding base
station on the correlated X2 interface.

System Actions

The X2 interface setup procedure is initiated again if the X2 interface setup procedure fails.

Possible Causes

The status of the SCTP link is abnormal.

The configuration of X2 interface has errors.

The X2 interface is not configured for the peer base station.

The local base station or the peer base station does not have an activated cell.

https://192.168.0.49/interface/en/F512081023/weblmt/lte/lte-enodeb-alarm-reference/alm-29204.html?f=F512081023

8/15/2014

ALM-29204 X2 Interface Fault

Page 2 of 4

The SCTP link is blocked.

The local base station is blacklisted by the peer base station.

The S1 interface of the peer base station is blocked.

Procedure

1. Check for the correlated alarm on the M2000.

a. Check for the correlated alarm on the M2000.

25888 SCTP Link Fault

Y

=> The correlated alarm exists. Go to sub-step b.

N

=> The correlated alarm does not exist. Go to step 2.

b. Clear the correlated alarm with recommended actions.

Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Go to step 2.

2. Check the configuration of the X2 interface on the M2000.

a. Run the MML command DSP X2INTERFACE to check whether the configuration of the SCTP link corresponding to the X2 interface is correct.

Y

=> The configuration of the SCTP link is correct. Go to step 3.

N

=> The configuration of the SCTP link is incorrect. Go to sub-step b.

b. Run the MML command RMV X2INTERFACE to remove the configuration of the X2 interface. If the X2 interface was set up automatically using SON, run the MML command RMV X2ENODEB. The command removes the X2ENODEB with which the corresponding X2 interface, SCTP link, and IP path will be automatically removed.

c. Run the MML command ADD X2INTERFACE and configure the X2 interface correctly. If an X2 interface needs to be automatically set up using SON, run the MML command ADD X2ENODEB. The command adds the X2ENODEB with which the corresponding X2 interface, SCTP link, and IP path will be automatically added.

Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Go to step 3.

3. Check the status of the SCTP link used by the X2 interface.

https://192.168.0.49/interface/en/F512081023/weblmt/lte/lte-enodeb-alarm-reference/alm-29204.html?f=F512081023

8/15/2014

ALM-29204 X2 Interface Fault

Page 3 of 4

a. Run the MML command LST SCTPLNK/LST SCTPLNK6 to check whether the SCTP link used by the X2 interface is blocked.

Y

=> The SCTP link is blocked. Go to sub-step b.

N

=> The SCTP link is not blocked. Go to step 4.

b. Run the MML command UBL SCTPLNK/UBL SCTPLNK6 to unblock the SCTP link. Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

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

4. Check the configured X2 interface of the peer base station on the M2000.

a. Run the MML command DSP X2INTERFACE to check whether the X2 interface is configured for the peer base station.

Y

=> The X2 interface is configured for the peer base station. Go to step 5.

N

=> The X2 interface is not configured for the peer base station. Go to sub-step b.

b. Run the MML command ADD X2INTERFACE to configure the X2 interface for the peer base station. Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Go to step 5.

5. Check the activated cell under the peer base station on the M2000.

a. Run the MML command DSP CELL to check whether there is an activated cell under the peer base station.

Y

=> There is an activated cell under the peer base station. Go to step 6.

N

=> There is no activated cell under the peer base station. Go to sub-step b.

b. Run the MML commands ADD CELL and ACT CELL to add and activate a cell under the peer base station. Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Go to step 6.

6. Check the local base station in the blacklist of the peer base station.

a. Run the MML command LST X2BLACKWHITELIST to check whether the local base station is blacklisted by the peer base station.

Y => The local base station is blacklisted by the peer base station. Go to sub-step b.

https://192.168.0.49/interface/en/F512081023/weblmt/lte/lte-enodeb-alarm-reference/alm-29204.html?f=F512081023

8/15/2014

ALM-29204 X2 Interface Fault

Page 4 of 4

N => The local base station is not blacklisted by the peer base station. Go to step 7.

b. Check whether the blacklist and whitelist of the peer base station need to be modified.

Y

=> The blacklist and whitelist need to be modified. Go to sub-step c.

Y

=> The blacklist or whitelist does not need to be modified. No further action is required.

c. Run the MML command RMV X2BLACKWHITELIST to remove the local base station from the blacklist of the peer base station.

Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Go to step 7.

7. Check the status of the S1 interface of the peer base station.

a. Run the MML command DSP S1INTERFACE to check whether the S1 interface of the peer base station is blocked.

Y

=> The S1 interface is blocked. Go to sub-step b.

N

=> The S1 interface is not blocked. Go to step 8.

b. Run the MML command UBL S1INTERFACE to unblock the blocked S1 interface of the peer base station.

Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Go to step 8.

8. Remove the faulty X2 interface and add an X2 interface.

a. Run the MML command RMV X2INTERFACE to remove the faulty X2 interface.

b. Run the MML command ADD X2INTERFACE to add an X2 interface.

Check whether the alarm is cleared.

Y

=> The alarm is cleared. No further action is required.

N

=> The alarm is not cleared. Contact Huawei Customer Service Center.

Huawei Proprietary and Confidential Copyright © Huawei Technologies Co., Ltd.

https://192.168.0.49/interface/en/F512081023/weblmt/lte/lte-enodeb-alarm-reference/alm-29204.html?f=F512081023

8/15/2014