Sei sulla pagina 1di 67

Alarm Name

E1/T1 Alarm Indication Signal

Alarm Class

TX

E1/T1 Remote Alarm Indication TX

IMA Link Remote RX Fault

TX

IMA Link Remote RX Unusable

TX

Local Cell Blocked

SITE/CELL DOWN

IMA Group Configuration


Aborted

TX

Board Startup Abnormal Alarm

HARDWARE

SDH/SONET Loss of Signal

TX

Board Not In Position

HARDWARE

Monitoring Device Maintenance


HARDWARE
Link Failure

External Clock Reference


Problem

TX

IMA Link Loss of Frame

TX

WBBP-WBBP Interface Abnormal HARDWARE

RF Unit Maintenance Link


Failure

HARDWARE

Board Type and Configuration


Mismatch

HARDWARE

BBU Optical Module


Transmit/Receive Fault

HARDWARE

Local Cell Unusable

SITE/CELL DOWN

RF Unit VSWR Threshold


Crossed

HARDWARE

Ethernet Link Fault

TX

RF Unit RX Channel RTWP/RSSI


HARDWARE
Unbalanced

E1/T1 Remote Alarm Indication


TX
Signal

E1/T1 Loss of Signal

TX

Board Hardware Fault

HARDWARE

BBU Board Maintenance Link


Failure

HARDWARE

RF Unit Optical Module Fault

HARDWARE

Board Downlink Service


Processing Channel Abnormal

HARDWARE

E1/T1 Loss of Frame Alignment TX

IMA/ATM Link Loss of Cell


Delineation

TX

IMA Link Remote Failure


Indication

TX

IMA Link RX Unusable at Far


End

TX

E1/T1 Excessive Slip Frames

TX

IP Path Fault

TX

NPMU Communication
Abnormal

HARDWARE

NCMU Communication
Abnormal

HARDWARE

Board Maintenance Link


Abnormal

HARDWARE

Board Type Mismatch

HARDWARE

Inter-Board Service Data


Channel Abnormal

HARDWARE

Module Type Mismatch

HARDWARE

Reference Clock Source


Abnormal

TX

Board Uplink Service Processing


HARDWARE
Channel Abnormal

IP Clock Link Failure

TX

Remote Maintenance Link


Failure

Tx

E1/T1 Excessive Bit Error Rate

TX

MAC Excessive Frame Error


Rate

TX

RF Unit RX Channel RTWP/RSSI


HARDWARE
Too Low

Inter-System Communication
Failure

HARDWARE

Board BFN Abnormal

HARDWARE

BBU CPRI Optical Interface


Performance Degraded

TX

IP Path Excessive Packet Loss


Rate

TX

BBU CPRI Interface Error

HARDWARE

RF Unit Optical Interface


Performance Degraded

TX

IMA Group Activated Links


Insufficient

TX

Possible Causes

The
The
The
The

E1/T1 link is incorrectly configured.


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

E1/T1 settings are incorrect.


E1/T1 transmission line connection is abnormal.
The E1/T1 equipment of this NE is abnormal.
The E1/T1 trunk transmission fails.
The E1/T1 equipment at the peer end is abnormal.

Faulty
Faulty
Faulty
Faulty

E1/T1 link
IMA link
IMA link of the local NodeB
IMA link of the peer end

The IMA link at the remote end is faulty.


The RX link at the remote end is blocked.
The RX E1/T1 link at the remote end is faulty.
The user runs a command to block the local cell of
the NE.

The parameter settings of the local and peer IMA


group are inconsistent.
There is at least one looped IMA link in the IMA group.

The operation of reading or writing into the


configuration fails.
Errors occur during data configuration on the board.
The board is operating improperly.
The startup of the board times out.

The working mode of the local optical port is set


incorrectly.
The local optical module is incompatible with the
optical fiber.
The local optical module is not securely installed or
not in position.
The local optical connector is not securely installed.
The RX and TX ends of the local optical fiber are
reversely connected.
The local optical connector is dirty.
The local optical module is faulty.
The local optical sub-board is faulty.
On the peer end, the configuration of the optical port
is incorrect, the optical connection is faulty, the
optical module is incompatible with the optical fiber,
or the device is faulty.
The optical transmission link is faulty.

The board does not exist or is not securely installed.


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

The monitoring device is configured in the wrong


cabinet/subrack/slot, or configured with the wrong
serial port or communication address.
The monitoring device is not powered on or not in
position.
The cable connection between the BBU/RRU and the
monitoring device is faulty.
The cable connection between the BBU/RRU and the
monitoring device is loose or broken.
The DIP switch setting of the monitoring device is
wrong.
The monitoring device is faulty.
The BBU is faulty.

If the clock reference is GPS clock, the GPS antenna


may be faulty or the number of locked GPS satellites
may be insufficient.
If the clock reference is IPCLK, the IP clock link may
fail or the clock reference may become unavailable.
If the clock reference is line clock, the transmission
link between the base station and the clock reference
may fail, or the frequency deviation between the
clock reference and the local clock may be
excessively large.
The clock reference is incorrectly configured.
The hardware of the UTRP, USCU, or main control
board is faulty.

The
The
The
The

E1/T1 link is faulty.


configuration of the IMA link group is incorrect.
local IMA is faulty.
peer IMA is faulty.

The transmit board is faulty.


The receive board is faulty.
The BBU subrack is faulty.

The CPRI link between the current-level RF unit and


the BBU or upper-level RF unit is broken.
The RF unit is not powered on or running improperly.
The RF unit hardware is faulty.

An incorrect board is configured.


An incorrect board is installed in the slot.

The optical module on the CPRI port of the BBU is


faulty or not installed securely, or the cable
connection on the CPRI optical module is not ready.
The optical connector on the CPRI port of the BBU is
dirty.
The optical module on the CPRI port of the BBU does
not match that of the lower-level RF unit, in terms of
type (single-mode or multi-mode) and rate.
The optical module on the CPRI port of the lower-level
RF unit is not supported by the lower-level RF unit, in
terms of type (single-mode or multi-mode) and rate.
The optical module on the CPRI port of the BBU does
not match the connected optical fiber, in terms of
type (single-mode or multi-mode) and rate.
The CPRI interface board in the BBU is faulty.
The lower-level RF unit is not powered on.
The optical module or connector of the lower-level RF
unit is improperly installed or the optical module is
faulty.
The optical connector of the lower-level RF unit is
dirty.
The optical module on the CPRI port of the lower-level
RF unit does not match the connected optical fiber, in
terms of type (single-mode or multi-mode) and rate.
The optical link between the BBU and the lower-level
RF unit is faulty.
The lower-level RF unit is fault

Uplink common baseband resource unavailable.


Downlink baseband resource unavailable.
Baseband-RF interface resource unavailable.
Uplink RF resource unavailable.
Downlink RF resource unavailable.
License capability limited.
Baseband board unavailable.
RF board unavailable.

The preset VSWR threshold is very low.


The installation of jumpers does not comply with the
plan.
The feeder connector on the antenna port is loose or
waterlogged.
The feeder connected to the antenna port of the RF
unit is bent, deformed, or damaged.
The VSWR detection circuit of the RF unit is faulty.

The parameter settings of the local Ethernet port are


inconsistent with those of the peer Ethernet port.
The Ethernet transmission link is faulty.
The local Ethernet is faulty.
The peer Ethernet is faulty.

The main RX channel or diversity RX channel of the


RF unit is faulty.
The setting of attenuation on the RX channel of the
RF unit is incorrect.
External interferences exist on the main or diversity
antenna of the RF unit.
The feeder connected to the RF unit is faulty, which
results in a high passive intermodulation power of the
main antenna.

The
The
The
The
The

E1/T1 link is configured incorrectly.


E1/T1 transmission link is faulty.
local device is faulty.
E1/T1 transmission trunk is faulty.
peer device is faulty.

The
The
The
The
The

E1/T1 link is incorrectly configured.


E1/T1 transmission link is faulty.
local device is faulty.
E1/T1 transmission trunk is faulty.
peer device is faulty.

The board temperature is out of range.


The board hardware is faulty.

The board automatically resets because of memory


soft failure or software program error.
The board file system is being formatted due to
errors.
The board does not exist or is not securely installed.
The board hardware is faulty.
The board is powered off.
The hardware of the main control board (in the
subrack that houses the board) is faulty.

The optical module of the RF unit is faulty.

The downlink encoding channel is faulty.

The
The
The
The
The

E1/T1 link is incorrectly configured.


E1/T1 transmission link is faulty.
local device is faulty.
E1/T1 transmission trunk is faulty.
peer device is faulty.

The E1/T1 link is faulty.


The configuration of the IMA link group/UNI link is
incorrect.
The local IMA is faulty.
The peer IMA is faulty.

The
The
The
The

E1/T1 link is faulty.


remote IMA link is faulty.
local IMA is faulty.
peer IMA is faulty.

The E1/T1 link bearing the remote IMA RX link is


faulty.
The remote IMA RX link is blocked.
The remote IMA link is faulty.

The local clock of the NE malfunctions.


The E1/T1 configuration is incorrect.
The E1/T1 grounding does not meet the grounding
requirements.
The performance of the E1/T1 transmission link is
poor.

The link bearing the IP path is faulty.


The peer route of the IP path is not configured.
The Ping detection is enabled on the IP path, but the
route of the bearing network is incorrectly configured,
or the Ping message is blocked by the bearing
network.
The hardware of the board carrying the IP path is
faulty.

The cabling between the RRU and the APM is


improper.
The NPMU is faulty.
The cabling between the BBU&RRU and the NCMU is
improper.
The NCMU is faulty.

The board is not installed in position, or is not in full


contact.
Hardware failure occurs on the board.
The WMPT is faulty.
The WMPT is not in full contact.

The board and the slot where it resides are


mismatched.

The TX board of the traffic channel is faulty.


The detection board of the traffic channel is faulty.

The type of the configured RRU is correct, but that of


the physical RRU is wrong.
The type of the physical RRU is correct, but that of
the configured RRU is wrong.

In the case of the GPS clock reference, possible


causes are:The GPS clock reference is not
configured.The GPS antenna is faulty.The GPS card is
faulty.The BBU is faulty.
In the case of the line clock reference, possible
causes are:The line clock source is not
configured.The E1/T1 link is faulty or the optical
interface is faulty.The upper-level NodeB clock
reference is abnormal.The RNC clock reference is
faulty.The clock reference of the transmission
equipment is faulty.The BBU is faulty.The clock
reference of the upper-level transmission equipment
is abnormal.
In the case of the IP clock reference, possible causes
are:The IP clock link is not configured.The BBU where
the IP clock link is located is faulty.The IP clock link is
abnormal.
In the case of the peer clock reference, the possible
cause is:The clock reference configured for the other
radio access technology (RAT) is abnormal.

The uplink dedicated demodulation channel, access


demodulation channel, or encoding channel is faulty.

The port used for the IP clock link is faulty.


The IPCLK link is incorrectly configured.
The route from the NE to the clock server is not
configured.
The route from the NE to the clock server is not
reachable.
The main control board hardware is faulty.

The
The
The
The

OMCH is not configured.


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

The local clock of the NE malfunctions.


The E1/T1 configuration is incorrect.
The E1/T1 grounding does not meet the grounding
requirements.
The performance of the E1/T1 transmission link is
poor.

The transmission performance of the Ethernet cable


may be poor.

The setting of attenuation of the RF unit is incorrect.


The TMA is faulty.
The feeder installation is improper. For example, the
feeder connector is loose, soaked or damaged, or the
feeder is deformed.
The RF unit is faulty.

The base station in the other mode is repeatedly


reset because the connection between the base
station and M2000 is disrupted for a long time.
The base station in the other mode is repeatedly
reset because the base station is not configured.
The base station in the other mode is reset after a
software upgrade or after a reset command is issued.
The main control board of the other mode is running
improperly.
The main control board of the current mode is
running improperly.
The main control board of the other mode is not
installed securely.
The main control board of the current mode is not
installed securely.
The hardware of the main control board of the other
mode is faulty.
The hardware of the main control board of the current
mode is faulty.

The board is not properly connected with the


subrack.
Certain service processing units of the board are
faulty.

The optical module of the BBU is worn-out.

The bandwidth configuration of the IP path on the NE


side is inconsistent with that on the RNC side.
The bit error rate (BER) or frame error rate (FER) of
the link bearing the IP path is extremely high.
The bandwidth of the physical link between the NE
and the RNC is restricted.

If the CPRI optical transmission is used, the optical


module or connector of the BBU or lower-level RF unit
may be improperly installed, or the optical link is
faulty.
If the CPRI electrical transmission is used, the cable
connector of the BBU or lower-level RF unit may be
improperly installed, or the cable is faulty.
The BBU or lower-level RF unit is running improperly,
or the hardware is faulty.
Data configuration is incorrect if a multi-mode base
station reports the alarm.

The optical module or connector of the current-level


RF unit is improperly installed. Or the optical module
is worn-out.
The optical connector of the current-level RF unit is
dirty.
The optical module on the CPRI port of the currentlevel RF unit is not supported by the current-level RF
unit, in terms of type (single-mode or multi-mode)
and rate.
The optical module or connector of the peer device
(upper-level/lower-level RF unit or BBU) is improperly
installed. Or the optical module is faulty.
The optical connector of the peer device (upperlevel/lower-level RF unit or BBU) is dirty.
The optical module on the CPRI port of the peer
device (upper-level/lower-level RF unit or BBU) is not
supported by the peer device, in terms of type
(single-mode or multi-mode) and rate.
The optical fibers between the current-level RF unit
and the peer device (upper-level/lower-level RF unit
or BBU) are bent, deformed, or worn-out. Or the
length of optical fibers is excessive (longer than 40
km), which leads to a high attenuation of optical
signals.

The IMA link is faulty.


The E1/T1 link is faulty.
The E1/T1 cable is connected incorrectly.

Solution

1. Check whether the E1/T1 configuration on site is correct.


- Configure the E1/T1 link properly.

2. Check whether the E1/T1 transmission link on site is normal. Check for the damaged cable, loose
connector.
- Replace or reconnect the E1/T1 cables.
3. Check whether the local E1/T1 device on site is functional.
- Reset the faulty board on the M2000 or on site.
Run the MML command RST BRD to reset the faulty board.
- Replace the faulty board on site.
(Reinstall the original board if alarm is not cleared.)
4. Troubleshoot the fault on the peer device.
1. Check whether the E1/T1 settings are correct.
Correct E1/T1 settings.
2. Check whether the connection of the corresponding E1/T1 transport line is secure:
Reconnect the E1/T1 transmission line.
3. Check whether the E1/T1 equipment of the NE is faulty:
Handle E1/T1 equipment faults of this NE.
4. Check whether the E1/T1 trunk between the NE and the far end is faulty.
1. Check whether the E1/T1 link is faulty.
2. Check whether the IMA link is faulty.
3. Rectify the local IMA link fault.
4. Rectify the peer IMA link fault.
1. Check for the IMA link fault at the remote end.
2. Check whether the IMA link at the remote end is blocked.
3. Check for the E1/T1 link fault at the remote end.
1. Unblock the local cell on the M2000.
- Run the MML command UBL LOCELL to unblock the local cell.

1. Locate the cause of the alarm on the M2000.


Check the cause of the alarm according to the alarm detailed information.
(a) If "Specific Problem" is "Configuration Aborted":
- Check the parameter settings of the local and peer IMA group on the M2000.
Obtain the parameter settings of the peer IMA group.
Run the MML command LST IMAGRP to check the parameter settings of the local IMA group.
Check whether the parameter settings of the local IMA group are consistent with those of the peer
protocol version.

(i) If the scramble mode at both ends are inconsistent:


- Change the scramble mode on the M2000.
Perform the parameter negotiation on the scramble mode at both ends.
Run the MML command SET SCRAM to change the scramble mode of the IMA group. Ensure that the
(ii) If the IMA protocol version at both ends is inconsistent.
- Change the IMA protocol version on the M2000.
Perform the parameter negotiation on the IMA protocol version at both ends.
Reconfigure the IMA group to change the IMA protocol version of the IMA group.
(b) If "Specific Problem" is "Link Deleted in the Group":
- Check for the looped link in the IMA group on the M2000.
Run the MML command DSP E1T1 to check whether the status of the port for the IMA link is looped.
- Release the looped IMA link on the M2000.
Check the E1/T1 link bearing the IMA link. Release the looped IMA link.

1. Check for the alarms indicating hardware failures and configuration failures of the board on the M
Check for the correlated alarm on the M2000:
26200 Board Hardware Fault
26532 RF Unit Hardware Fault
Clear the correlated alarm according to the relevant handling suggestions.
2. Reset the board on the M2000.
Run the MML command RST BRD to reset the board.
3. Download the configuration file from the M2000.
Modify the Data Configuration File.

settings based on the network plan, and check the consistency of frame format and multiplexing m

- Run the MML command SET STM1 to change the settings of the working mode of the local optical p
2. Check that the local optical module is in position on site.
- Run the MML command DSP OPTMODULE to check whether the local optical module is in position.
- Reinstall the optical module on the local board securely.
3. Reinsert the connector of the optical fiber into the optical module on the board securely.
4. Check whether the local optical module matches the optical fiber on site.
- Replace the local optical module with an optical module that is compatible with the optical fiber.
5. Check whether the local optical fiber is incorrectly connected.
- Replace or reconnect the optical fiber. Ensure that the optical fiber is correctly connected.
6. Clean the connector of the local optical fiber on site.
- Remove the connector and clean it by using absorbent cotton with absolute alcohol. Then, insert
7. Replace the optical module on site.
- Remove the optical fiber from the panel of the BBU or RF unit.
- Remove the optical module to be replaced.
- Install a spare optical module.
- Reconnect the optical fiber to the panel of the BBU or RF unit.

8. Check that the local optical sub-board works properly.


- Connect the TX port of the optical sub-board and its RX port by using an optical fiber for loopback
If the alarm is cleared. You can infer that the local optical sub-board is damaged.
- Replace the board.
If the alarm is not cleared after replacing the board, reinstall the original board.
9. Check that the peer device with the optical port works properly.

1. Reseat the board properly on site.


2. Check the backplane slot in the BBU on site.
- Remove the board. Then, use a flashlight to check whether there is any bent or broken pin in the

If the backplane slot that holds the board malfunctions. Check whether there is another idle backpl

If there is another idle backplane slot.


- Run the MML command RMV BRD to remove the board in the faulty slot.
Run the MML command ADD BRD to add the board in the idle slot.
Remove the board from the faulty slot and install it in the idle slot. Wait until the board startup is c
and OFF for 1s).
3. Replace the faulty board on site.
4. Reseat the main control board properly in the subrack that houses the faulty board on site.
5. Replace the main control board in the subrack that houses the faulty board on site.

1. Check the configuration on the M2000.


- Run the MML command LST PMU(PMU)/LST TCU(TCU)/LST EMU(EMU)/LST FMU(FMU) to check whethe
port, and communication address of the faulty monitoring device are consistent with the configura
If inconsistent:
- Run the MML command RMV PMU(PMU)/RMV TCU(TCU)/RMV EMU(EMU)/RMV FMU(FMU) to remove the
- Run the MML command ADD PMU(PMU)/ADD TCU(TCU)/ADD EMU(EMU)/ADD FMU(FMU) to add the mo
planning.

2. Check the monitoring device on site.


- Check whether the monitoring device specified in the alarm location parameters is powered on or
ON and the RUN LED is lighted, it indicates that the monitoring device is powered on.
- Power on the monitoring device, or reinstall the monitoring device and then power it on.

3. Check whether the cable is properly connected between the monitoring device and the BBU/RRU
- Reconnect the cable between the monitoring device and the BBU/RRU.
4. Check whether the cable between the monitoring device and the BBU/RRU is functional and the
- Reconnect or replace the cable.

5. Check the DIP switch settings of the monitoring device, if any.


- Power off the monitoring device. Set the DIP switch correctly and power on the monitoring device
6. Replace the monitoring device on site.

7. Replace the faulty unit of the BBU on site.


Note: If there is only one UPEU configured for the BBU, replacing the UPEU disrupts all the ongoing
perform this replacement in low-traffic hours.
- Replace the BBU environment interface unit on site.

Note: Replacing the main control board disrupts all the ongoing services of the base station. Theref
hours. The base station software upgrade may be required during board replacement, so the correc
advance.
- Replace the main control board on site.

26121
26122
26120
26123
26263
25800
25806
25880
25881
25883
25884
25885
26200

GPS Antenna Fault


GPS Locked Satellites Insufficient
GPS Clock Output Unavailable
GPS Maintenance Link Failure
IP Clock Link Failure
E1/T1 Loss of Signal
E1/T1 Excessive Bit Error Rate
Ethernet Link Fault
MAC Excessive Frame Error Rate
ETHOAM 3AH Local Fault
ETHOAM 3AH Remote Fault
IP Address Conflict
Board Hardware Fault

- Clear the correlated alarm with recommended actions.


Wait for five minutes. Check whether the alarm is cleared.

2. Check the clock reference on the basis of configuration plan on the M2000.
-Run the MML command LST CLKMODE to check whether the clock reference is consistent with the c
If the clock reference is inconsistent with the configuration plan:
- Run the MML command SET CLKMODE to change the clock reference according to the configuration
Wait for five minutes. Check whether the alarm is cleared.
3. Locate the cause of the alarm on the M2000.
Locate the cause of the alarm based on the alarm location information.

If "Specific Problem" is "Clock Reference Unavailable":


- Handle the unavailable IP clock reference problem.
Contact maintenance personnel of the IP Clock server to solve the unavailable IP clock reference pr
meets the requirements of the base station. Wait for five minutes. Check whether the alarm is clea

If "Specific Problem" is "Excessive Frequency Difference Between Clock Reference and Local Crysta
- Handle the link clock fault caused by transmission link failures.

1. Check the E1/T1 link on the M2000.


Check for the E1/T1-correlated alarms on the E1/T1 link that bears the IMA link on the M2000:
Clear the correlated alarm with recommended actions.

2. Check the configuration of the IMA link group on the M2000.


- Run the MML command LST IMAGRP to query the configuration of the local IMA link group.
Query the configuration of the peer IMA link group. Check whether the local configuration matches
mode and IMA protocol version.
- Run the MML command MOD IMAGRP to change the local IMA group configuration. Ensure that the
peer.
- Check the local IMA link on the M2000.
Perform the IMA link loopback.
- Run the MML command RST IMAGRP to reset the IMA link group.
- Reconfigure the IMA link.
3. Reset the faulty board on the M2000.
Run the MML command RST BRD to reset the faulty board.
4. Check whether the peer IMA is normal.
- Rectify the fault on the peer IMA.

1. Reset the receive board on the M2000.


Note: Resetting the board disrupts some or even all the ongoing services of the base station. There
hours.
- Run the MML command RST BRD to reset the receive board.
2. Remove and reinstall the receive board on site.
- Reseat the Board.
3. Replace the receive board on site.
If the alarm is not cleared. Reinstall the original board.
4. Remove and reinstall the transmit board on site.
- Reseat the Board.
5. Replace the transmit board on site.
If the alarm is not cleared. Reinstall the original board.
6. Replace the BBU subrack on site.
- Replace the subrack.

1. Change the fiber connectiong to RRU


2. Reset the RF unit on the M2000.
- Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through power-off.
3. Replace the RF unit on site.

1. Check the board configuration on the M2000.


Run the MML command DSP BRD to check whether the type of the configured board in the slot is co
Run the MML command RMV BRD to remove the configured board in the slot.
Run the MML command ADD BRD to configure the correct board in the slot according to the configur
2. Check the configured sub-board type on the M2000.
Based on the alarm detailed information, check whether the board type is the UTRP.

Run the MML command DSP BRD to query the sub-board type. Check whether the configured sub-bo
board.
Run the MML command ADD BRD to change the sub-board type according to the installed sub-board
3. Replace the board on site.

1. Check for the correlated alarm on the faulty CPRI port of the BBU on the M2000:
26230
26231
26233
26506
26540

BBU CPRI Optical Module Fault


BBU CPRI Optical Module or Electrical Port Not Ready
BBU CPRI Optical Interface Performance Degraded
RF Unit Optical Interface Performance Degraded
RF Unit AC Input Power Failure

Clear the correlated alarm with recommended actions.


2. Check the CPRI port of the BBU on site.
- Run the MML command DSP OPTMODULE to query the transmission mode of the optical module.
3. Connect the TX and RX ports of the optical module on the BBU on site.
4. Check the running status of the lower-level RF unit on site.
5. Check the CPRI port of the lower-level RF unit on site.
6. Connect the TX and RX terminals of the optical fiber on the lower-level RF unit on site.
7. Check the optical connections on site.
8. Check the optical modules at both ends of the CPRI link and the optical fiber on site.

26106
26200
26201
26204
26205
26210
26264
26265
28302
28303
28381

Board Clock Input Unavailable


Board Hardware Fault
Board Memory Soft Failure
Board Not In Position
BBU Board Maintenance Link Failure
Board Blocked
System Clock Unlocked
Base Station Frame Number Synchronization Error
Board BFN Abnormal
WBBP-WBBP Interface Abnormal
Board Startup Abnormal Alarm

Clear the correlated alarm according to the relevant handling suggestions.

4. Rectify the RF resource fault on the M2000.


Open the alarm browsing window or run the MML command LST ALMAF to check for alarms related t
connected to the RRU/RFU.
26210
26235
26237
26524
26525
26529
26532
26538
26545
26765
26768

Board Blocked
RF Unit Maintenance Link Failure
RRU Network Breakpoint
RF Unit PA Overcurrent
RF Unit Temperature Unacceptable
RF Unit VSWR Threshold Crossed
RF Unit Hardware Fault
RF Unit Clock Problem
RF Unit TX Channel Switched Off Through Command
RHUB Hardware Fault
RHUB Clock Problem

Clear the correlated alarm according to the relevant handling suggestions.

1. Check the VSWR threshold on the M2000.


- Run the MML command LST RRU to query the VSWR threshold of the RF unit. Check whether the V
configuration plan.
- Run the MML command MOD RRU to modify the VSWR threshold of the RF unit.
2. Check whether the installation of the RF unit and jumpers on site is consistent with the plan.
- Reinstall the jumpers for the RF unit according to the plan.
3. Reconnect the jumper to the antenna port of the RF unit on site.
4. Check the installation of feeders for the RF unit on site.
- Using Site Master
5. Reset the RF unit on site or on the M2000.
After the startup of the RF unit is complete, wait for 10 minutes.
6. Replace the RF unit on site.
If the alarm is not cleared, reinstall the original board.

1. Check the settings of the local and peer Ethernet ports on the M2000.
Run the MML command LST ETHPORT to check the parameter settings of the local Ethernet port.
2. Reset the local Ethernet port on the M2000.
Run the MML command RST ETHPORT to reset the local Ethernet port.
3. Check the Ethernet cable connected to the local Ethernet port on site.
4. Check the peer Ethernet.

1. Check for the correlated alarm of the RF unit on the M2000:


26521 RF Unit RX Channel RTWP/RSSI Too Low
Clear the correlated alarm with recommended actions.

1. Check whether the E1/T1 configuration on site is correct.


Configure the E1/T1 link properly.

2. Check whether the E1/T1 transmission link on site is normal. Check for the damaged cable, loose
connector.
Replace or reconnect the E1/T1 cables.
3. Check whether the local E1/T1 device on site is functional.
4. Run the MML command RST BRD to reset the faulty board.
5. Replace the faulty board on site.

6. Check the E1/T1 transmission trunk between the local device and the peer device on site.
Check whether the E1/T1 transmission trunk is functional.
Contact the transmission engineer of the customer to troubleshoot the fault on the transmission tru
7. Check the peer device.

1. Check whether the E1/T1 configuration on site is correct.


Configure the E1/T1 link properly.

2. Check whether the E1/T1 transmission link on site is normal. Check for the damaged cable, loose
connector.
Replace or reconnect the E1/T1 cables.
3. Check whether the local E1/T1 device on site is functional.
4. Run the MML command RST BRD to reset the faulty board.
5. Replace the faulty board on site.

6. Check the E1/T1 transmission trunk between the local device and the peer device on site.
Contact the transmission engineer of the customer to troubleshoot the fault on the transmission tru
7. Check the peer device.

1. Check for the correlated alarm on the M2000.


Check for the correlated alarm of the faulty board on the M2000:
26104 Board Temperature Unacceptable
Clear the correlated alarm with recommended actions.
2. Reset the faulty board through power-off on the M2000.
Reset the board through power-off.
3. Replace the faulty board on site.

1.Check for the correlated alarm of the faulty board on the M2000:
26200
26201
26202
26203
26204
26208
26214
26216

Board
Board
Board
Board
Board
Board
Board
Board

Hardware Fault
Memory Soft Failure
Overload
Software Program Error
Not In Position
File System Damaged
Powered Off
Not Securely Installed

Clear the correlated alarm with recommended actions.

2. Check the state of board file system on site.


Check whether the RUN LED on the faulty board blinks quickly (ON for 0.125s and OFF for 0.125s).
Wait until the RUN LED on the board blinks slowly (ON for 1s and OFF for 1s). Generally, the file sys
minutes.
3. Reseat the board properly on site.
4. Replace the faulty board on site.
5. Reseat the main control board in the subrack that houses the faulty board on site.
6. Replace the main control board in the subrack that houses the faulty board on site.

1. Check for the correlated alarm of the RF unit on the M2000:


26532 RF Unit Hardware Fault
Clear the correlated alarm with recommended actions.
2. Reseat the faulty optical module on site.
3. Replace the optical module on site.
1. Reset the faulty board on the M2000.
Run the MML command RST BRD to reset the board.
2. Replace the faulty board on site.

1. Check whether the E1/T1 configuration on site is correct.


Configure the E1/T1 link properly.

2. Check whether the E1/T1 transmission link on site is normal. Check for the damaged cable, loose
connector.
Replace or reconnect the E1/T1 cables.
3. Check whether the local E1/T1 device on site is functional.
4. Reset the faulty board on the M2000 or on site.
Run the MML command RST BRD to reset the faulty board.
5. Replace the faulty board on site.

6. Check the E1/T1 transmission trunk between the local device and the peer device on site.
Check whether the E1/T1 transmission trunk is functional.
Contact the transmission engineer of the customer to troubleshoot the fault on the transmission tru
7. Check the peer device.
Troubleshoot the fault on the peer device.

1. Check for the E1/T1-correlated alarms on the E1/T1 link that bears the IMA/UNI link on the M200
Clear the correlated alarm with recommended actions.
2. Run the MML command LST IMALNK and LST UNILNK to check the link type.

3. Run the MML command LST IMAGRP to query the configuration of the local IMA link group.
Query the configuration of the peer IMA link group. Check whether the local configuration matches
mode, 16th timeslot support, and IMA protocol version.
Run the MML command MOD IMAGRP to change the local IMA group configuration. Ensure that the lo
peer.
4. Check the local IMA link on the M2000.
Perform the IMA link loopback.
Run the MML command RST IMAGRP to reset the IMA link group.
Reconfigure the IMA link.
5. Run the MML command RST BRD to reset the faulty board.
6. Check whether the peer IMA is normal.
Rectify the fault on the peer IMA.
7. Check the UNI link configuration on the M2000.
Run the MML command LST UNILNK to query the local UNI link configuration.
Check whether the local configuration matches the peer configuration, including the parameter of
Run the MML command RMV UNILNK , ADD UNILNK to change the local UNI link configuration. Ensure
the peer.
8. Reset the faulty board on the M2000.
Run the MML command RST BRD to reset the faulty board.

1. Check for the correlated alarm on the E1/T1 link that bears the IMA link on the M2000:
E1/T1-Correlated Alarms:
25823 IMA Link Loss of Frame
25824 IMA Link Out of Delay Synchronization
25821 IMA/ATM Link Loss of Cell Delineation
- Clear the correlated alarm with recommended actions.
2. Check the local IMA link on the M2000.
- Perform the IMA link loopback.
- If IMA link loopback fail, Run the MML command RST IMAGRP to reset the IMA link group.
- Reconfigure the IMA link.
3. Reset the faulty board on the M2000.
- Run the MML command RST BRD to reset the faulty board.
4. Check whether the peer IMA is normal.
- Rectify the fault on the peer IMA.

1. Check for the correlated alarm on the E1/T1 link that bears the IMA link on the M2000:
E1/T1-Correlated Alarms:
25823 IMA Link Loss of Frame
25824 IMA Link Out of Delay Synchronization
25821 IMA/ATM Link Loss of Cell Delineation
- Clear the correlated alarm with recommended actions.
2. Check whether the peer IMA is normal.
- Rectify the fault on the peer IMA.

1. Check for the correlated alarm on the M2000:


26262 External Clock Reference Problem
Clear the correlated alarm with recommended actions. Then, wait for ten minutes.
2. Reset the faulty board on the M2000 or on site.
Run the MML command RST BRD to reset the faulty board.
3. Check whether the E1/T1 configuration on site is correct.
Configure the E1/T1 link properly.
4. Check whether the E1/T1 grounding meets the requirements.
Ground the E1/T1 transmission cables properly and then wait for 15 minutes.

5. Check whether the E1/T1 transmission link is functional. Check for the damaged cable, loose con
Replace or reconnect the E1/T1 cables.
6. Check whether the local E1/T1 device on site is functional.
7. Replace the faulty board on site.

8. Check whether the E1/T1 transmission trunk between the local device and the peer device on si
Contact the transmission engineer of the customer to troubleshoot the fault on the transmission tru
9. Troubleshoot the fault on the peer device.

1. Check the corresponding bearing link on the M2000.


Run the MML command LST IPPATH to query the corresponding link bearing the faulty IP path.

2. Check the route on the M2000.


Run the MML command DSP IPRT to check whether the IP route to the peer devices is configured fo
path.
Run the MML command ADD IPRT to add the IP route to the peer devices for the corresponding link.

3. Check the configuration of the bearing network.


Contact the administrator of the bearing network to check whether the route of the bearing networ
message is not blocked.
Contact the engineers responsible for network administration to correct the network configuration.
4. Reset the faulty board on the M2000.
Run the MML command RST BRD to reset the faulty board.
1. Check the cabling between the RRU and the APM.
2. Replace the NPMU.
1. Check the cabling between the BBU&RRU and the NCMU.
2. Replace the NCMU.

1. Check whether the board is installed in the slot.


2. Remove and reinstall the board. Wait until the board is started.
Check whether the alarm is cleared.
3. Replace the board.

4. Install the board in the slot. Wait until the board is started.
Run the MML command DSP BRDVER to query the BootROM version of the board. Check whether the
related instructions in the upgrade guide.
Run the MML command ACT SOFTWARE to activate the BootROM version of the board.
Run the MML command RST BRD to reset the board.
Check whether the alarm is cleared.
5. Check whether the alarm is generated in all the links through the alarm management system.
Check whether the maintenance link alarm is generated on all the boards.

6. Remove and reinstall the WMPT. Wait until the board is restarted and the RUN LED blinks normal
7. Replace the WMPT.

8. Remove and reinstall the board in the faulty link. Wait until the board is restated and the RUN LE
9. Replace the board in the faulty link.

1. Replace the board according to system configuration.


Carry out DSP BRD on the maintenance terminal to query the type of board in the faulty slot accord
Replace the board with the one whose type matches the board type in system configuration.

1. Reset the faulty board.


Based on the parameters for faulty board location that are reported in the alarm, reset the faulty b

2. Reset the detection board.


Based on the parameters for detection board location that are reported in the alarm, reset the dete

3. Replace the faulty board.


Based on the parameters for faulty board location that are reported in the alarm, replace the faulty

4. Replace the detection board.


Based on the parameters for detection board location that are reported in the alarm, replace the de
1. Ensure that the type of the RRU is correct.
2. Replace the physical RRU.
3. Modify the configuration of the RRU.
Carry out RMV RRU to remove the configured RRU with a wrong type.
Carry out ADD RRU to add an RRU. Ensure that the new RRU match with the physical RRU.

1. Run LST CLKMODE to query the clock reference mode.


2. Configure clock reference accordingly.
GPS:
LST GPSSRC , ADD GPSSRC
LINE:
DSP LNKSRC , ADD LNKSRC

IP:
LST IPCLKLNK , RMV IPCLKLNK , ADD IPCLKLNK

1. Reset the faulty board on the M2000.


Note: Resetting the board disrupts some or even all the ongoing services of the base station. There
hours.
Run the MML command RST BRD to reset the board.
2. Replace the faulty board on site.

1. Check for the correlated alarm on the M2000.


Check for the correlated alarm of the port that bears the IPCLK link on the M2000.
26221
25880
25881
25883
25884
25885

Transmission Optical Module Not In Position


Ethernet Link Fault
MAC Excessive Frame Error Rate
ETHOAM 3AH Local Fault
ETHOAM 3AH Remote Fault
IP Address Conflict

Clear the correlated alarm with recommended actions.

2. Check the IPCLK configuration on the M2000.


Run the MML command LST IPCLKLINK to check whether the IP address of the clock server and the I
plan.
Run the MML command RMV IPCLKLINK / ADD IPCLKLINK to change the configuration of IPCLK link.

3. Check the configuration of route from the NE to the clock server on the M2000.
Run the MML command LST IPRT to query all the current routes. Check whether an IP route connect
Run the MML command ADD IPRT to add an IP route connecting the peer clock server. Then, wait for

4. Check the reachability of route from the NE to the clock server on the M2000.
Run the MML command PING to check whether the route from the NE to the clock server is reachab

1. Check the data configuration of the remote maintenance link on site.


Run the MML command LST OMCH to check whether the OMCH is configured.
Run the MML command ADD OMCH to configure the data of the OMCH based on the configuration pl
Run the MML command MOD OMCH to configure the data of the OMCH based on the configuration p
Run the MML command LST IPRT to check whether the configuration of the IP route used by the OM
Run the MML command RMV IPRT,ADD IPRT to modify the configuration of the IP route according to t
2. Check for the correlated alarms on site.
Check for the correlated alarms of the OMCH on the LMT:
25821
25820
25860
25861
25880
25885
25895
25921
25922

IMA/ATM Link Loss of Cell Delineation


Fractional ATM Link Loss of Cell Delineation
PPP/MLPPP Link Fault
MLPPP Group Fault
Ethernet Link Fault
IP Address Conflict
Ethernet Trunk Group Fault
SDH/SONET Loss of Frame
SDH/SONET Loss of Signal

Clear the correlated alarm with recommended actions.

3. Check the M2000.


Contact the maintenance personnel in charge of the M2000 to check whether the M2000 is operati
station is correct on the M2000.
Contact the maintenance personnel in charge of the M2000 to rectify the fault.
4. Check for faults in the transmission network on site.

1. Check the local clock of the NE on the M2000.


Check for the correlated alarm on the M2000:
26262 External Clock Reference Problem
Clear the correlated alarm with recommended actions. Then, wait for 15 minutes.

2. Check that the local E1/T1 configuration is consistent with the peer E1/T1 configuration on the M
Run the MML command DSP E1T1 to check whether the line code of the faulty E1/T1 is consistent w
Run the MML command SET E1T1 to change the line code of the local E1/T1. Ensure that the line cod
the peer E1/T1.
3. Check the E1/T1 grounding on site.
Check whether the E1/T1 grounding meets the requirements.
Ground the E1/T1 transmission cables properly and then wait for 15 minutes.

4. Check the E1/T1 transmission link on site.


Check whether the E1/T1 transmission link is functional. Check for the damaged cable, loose conne
Replace or reconnect the E1/T1 cables.

1. Check the FER threshold on the M2000.


Run the MML command LST ETHPORT to check whether the parameter "MAC Frame Error Rate Occu
properly.
Run the MML command SET ETHPORT to change the setting of the parameter "MAC Frame Error Rat
2. Check the Ethernet cable connected to the local Ethernet port on site.
Check whether the LED on the Ethernet port is blinking normally.
3. Replace the Ethernet cable.

1. Check for the correlated alarm on the M2000.


Check for the correlated alarm on the faulty CPRI port of the RF unit on the M2000:
26532 RF Unit Hardware Fault
26530 RF Unit ALD Current Out of Range
Clear the correlated alarm with recommended actions.
2. Check the attenuation of the RF unit on the M2000.
3. Reconnect the jumper to the antenna port of the RF unit on site.
4. Replace the TMA on site.
5. Power cycle the RF unit on site.
6. Replace the RF unit on site.

1. Check the status of the main control board in the other mode on the M2000.
Open Device Panel on the M2000, and check whether the status of the main control board in the ot
Wait 5 minutes. Check whether the alarm is cleared.

2. Reset the main control board of the current mode on the M2000.
Run the MML command RST BRD to reset the main control board of the current mode. Wait until the

3. Reset the main control board of the other mode on the M2000.
Run the MML command RST BRD to reset the main control board of the other mode. Wait until the b
4. Reseat the main control board of the current mode on site.
5. Reseat the main control board of the other mode on site.
6. Replace the main control board of the current mode on site.
7. Replace the main control board of the other mode on site.

1. Reset the faulty board on the M2000.


Note: Resetting the board disrupts some or even all the ongoing services of the base station. There
hours.
Run the MML command RST BRD to reset the board.
2. Remove and reinstall the faulty board on site.
3. Replace the faulty board on site.
4. Remove and reinstall the main control board on site.
5. Replace the main control board on site.
6. Replace the BBU subrack on site.
1. Check the CPRI port of the BBU on site.
(a) Reseat the optical module and connector on the faulty CPRI port of the BBU on site.
(b) Replace the optical module.

1. Check that the bandwidth of the IP path is configured correctly.


Run the MML command LST IPPATH to check whether the receive bandwidth and transmit bandwidt
configured on the RNC .
2. Check the bandwidth of the physical link between the NE and the RNC.

1. Check for the correlated alarm on the M2000.


Check for the correlated alarm on the faulty CPRI port of the BBU on the M2000:
26230
26231
26232
26272
26238

BBU CPRI Optical Module Fault


BBU CPRI Optical Module or Electrical Port Not Ready
BBU Optical Module Transmit/Receive Fault
Inter-System RF Unit Parameter Settings Conflict
RRU Network Topology Type and Configuration Mismatch

Clear the correlated alarm with recommended actions.

2. Check the optical connections on site.


Check the optical connections between the BBU and the lower=level RF units. Troubleshoot the imp
bending or deformation.
3. Check the cable connections on the CPRI port of the BBU on site.
4. Replace the lower-level RF unit on site.
5. Clear the fault in the BBU on site.
(a) On the BBU side, reseat the board.
(b) Replace the board.

1. Check the CPRI port of the current-level RF unit on site.


2. Check the CPRI port of the peer device on site.
3. Check the optical connections on site.

1. Check the local IMA link on the M2000.


Check for the correlated alarm on the E1/T1 link that bears the IMA link on the M2000:
E1/T1-Correlated Alarms:
25823 IMA Link Loss of Frame
25824 IMA Link Out of Delay Synchronization
25821 IMA/ATM Link Loss of Cell Delineation
Clear the correlated alarm with recommended actions.

2. Check that the E1/T1 cable is correctly connected.


Run the MML command STR E1T1OFFLTST on the M2000 to check whether the offline test on the E1/
be successfully started.

Alarm

BBU CPRI Interface Error


BBU CPRI Optical Interface Performance Degraded
BBU CPRI Optical Module or Electrical Port Not Ready
BBU Optical Module Transmit/Receive Fault
Board Hardware Fault
Board Hardware Indication Fault
Board Maintenance Link Abnormal Alarm
Fan Stalled
Radio Signaling Link Disconnected
RF Unit Clock Problem
RF Unit Maintenance Link Failure
RF Unit Optical Interface Performance Degraded
RF Unit RX Channel Fault
RF Unit VSWR Threshold Crossed
ESL Link Fault
GSM Cell Manually Blocked
GSM Cell out of Service
OML Fault
TRX Manually Blocked
E1/T1 Alarm Indication Signal
E1/T1 Loss of Frame Alignment
E1/T1 Loss of Signal
E1/T1 Remote Alarm Indication Signal

Class

Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Hardware
Site Down
Site Down
Site Down
Site Down
Site Down
Transmission
Transmission
Transmission
Transmission

Potrebbero piacerti anche