Professional Documents
Culture Documents
Fault ManagemeBU Huawei
Fault ManagemeBU Huawei
System Actions
None
Possible Causes
The optical module on the transmission port of the BBU is faulty or not installed securely, or the cable
connection on the optical module is not ready.
The optical module on the transmission port of the peer transmission device is faulty or not installed
securely, the cable connection on the optical module is not ready, or the peer transmission device is
faulty.
The optical connection between the BBU and the peer transmission device is faulty.
Procedure
a. Check for the correlated alarm on the faulty transmission port of the BBU on the
M2000:
26220 Transmission Optical Module Fault
26221 Transmission Optical Module Not In Position
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. Reseat the optical module and connector on the faulty transmission port of the BBU on
site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Connect the TX and RX ports of the optical module for transmission on the BBU on site.
a. Remove the optical fiber from the optical module for transmission on the BBU. Then,
connect the TX and RX ports of the optical module by using an optical fiber for
loopback.
Check whether the alarm is cleared.
b. Disconnect the TX and RX ports of the optical module, and restore the optical
connection of the BBU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Contact the maintenance engineers responsible for the peer transmission device to
troubleshoot the faults on the optical port of the peer transmission device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. Check the optical connections between the BBU and the peer transmission device.
Troubleshoot the improper optical connections, such as bent fiber, deformation, or
aging.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the TX/RX performance of the optical module on the transmission port of the BBU
deteriorates.
Parameters
Major When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the transmission link may decrease significantly, or the
transmission link is broken.
Minor When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the transmission link may decrease to some extent.
System Actions
None
Possible Causes
The optical module on the transmission port of the BBU is worn-out or not installed securely, or the
cable connection on the optical module is loose.
The optical fibers between the BBU and the peer transmission device are bent, deformed, or
worn-out. Or the length of optical fibers is excessive, which leads to a high attenuation of optical
signals.
Procedure
a. Reseat the optical module and connector on the faulty transmission port of the BBU on
site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module on the transmission port is supported by the BBU, in
terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5 Gbit/s).
Y => The optical module on the transmission port is supported. Go to sub-step e.
N => The optical module on the transmission port is not supported. Go to sub-step d.
a. Contact the maintenance engineers responsible for the peer transmission device to
troubleshoot the faults on the optical port of the peer transmission device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Check the optical connections between the BBU and the peer transmission device.
Troubleshoot the improper optical connections, such as bent fiber, deformation, or
aging.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Check the length of the optical link between the BBU and the peer transmission device.
If the length is excessive, additional optical trunks are required.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the optical module on the port of the BBU connecting to the lower-level RF units is
faulty.
Parameters
System Actions
None
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is faulty.
Procedure
a. Check for the correlated alarm on the interface board of the BBU connecting to the
lower-level RF units on the M2000:
26200 Board Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the optical module on the port of the BBU connecting to the lower-level RF units is
not in position or when the cable connection on the optical module or electrical port is not ready.
Parameters
Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted. The services of the peer mode are
interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty port provides the aggregation function.
In ring topology, the reliability of the link decreases. In this case, the active link of
lower-level RF units is switched over to the standby link. In the case of a hot ring, the
ongoing services are not affected. In the case of a cold ring, the ongoing services
are disrupted temporarily.
System Actions
In ring topology, the active link of lower-level RF units is switched over to the standby link.
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is not in position, or
the cable connection on the optical module or electrical port is not ready.
The optical module on the port of the BBU connecting to the lower-level RF units is faulty, or the
cable connected to the optical module or electrical port is faulty.
The connecting piece on the port of the BBU is faulty.
Procedure
a. Run the MML command LST RRUCHAIN to query the link networking of the faulty port.
Check whether the redundant RRU chain/ring is configured according to the site plan.
Y => The redundant RRU chain/ring is configured. Go to sub-step b.
N => There is no redundant RRU chain/ring. Go to step 2.
b. Run the MML command RMV RRUCHAIN to remove the redundant RRU chain/ring .
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the installation of the optical module, or check the cable connection on the CPRI optical
module or electrical port of the BBU on site.
a. Check whether the optical module is installed, or whether the cable is connected to the
CPRI optical module or electrical port of the BBU on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the CPRI optical/electrical port.
c. Remove the optical module or the cable connected to the CPRI optical/electrical port,
and then reinstall it securely.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. In the case that the CPRI optical port is used, replace the optical module.
In the case that the CPRI electrical port is used, replace the cable connected to the
CPRI electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Reseat the interface board where the faulty port is located on site.
4. Replace the interface board where the faulty port is located on site.
This alarm is reported when the BBU cannot properly receive signals through the optical link (at the physical
layer) from the lower-level RF units.
Parameters
Parameter
Name Parameter Description
Specific Problem Specific Problem of the alarm(Receive No Signal, Receive Power Too High, Receive Power
Too Low)
Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted. The services of the peer mode are
interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty port provides the aggregation function.
In ring topology, the reliability of the link decreases. In this case, the active link of
lower-level RF units is switched over to the standby link. In the case of a hot ring, the
ongoing services are not affected. In the case of a cold ring, the ongoing services
are disrupted temporarily.
Minor When the performance of the optical module of the BBU and the lower-level RF unit
deteriorates to some extent, the quality of services carried on the lower-level RF
units may decrease to some extent.
System Actions
In ring topology, the lower-level RF units automatically switch to the normal CPRI link.
Possible Causes
The optical module on the port of the BBU connecting to the lower-level RF units is faulty or not
installed securely, or the cable connection on the optical module is not ready.
The optical connector on the port of the BBU connecting to the lower-level RF units is dirty.
The optical module on the port of the BBU does not match that of the lower-level RF unit, in terms of
type (single-mode or multi-mode) and rate.
The optical module on the port of the lower-level RF unit is not supported by the lower-level RF unit,
in terms of type (single-mode or multi-mode) and rate.
The optical module on the port of the BBU connecting to the lower-level RF units does not match the
connected optical fiber, in terms of type (single-mode or multi-mode) and rate.
The interface board in the BBU connecting to the lower-level RF units is faulty.
The optical module on the port of the lower-level RF unit does not match the connected optical fiber,
in terms of type (single-mode or multi-mode) and rate.
The optical link between the BBU and the lower-level RF unit is faulty.
Procedure
a. Check for the correlated alarm on the faulty port of the BBU on the M2000:
26230 BBU CPRI Optical Module Fault
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26233 BBU CPRI Optical Interface Performance Degraded
26506 RF Unit Optical Interface Performance Degraded
26540 RF Unit AC Input Power Failure
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "Receive No Signal" or "Receive Power Too Low", go to step 3.
If "Specific Problem" is "Receive Power Too High", go to step 9.
3. Check the port of the BBU connecting to the lower-level RF units on site.
a. Reseat the optical module and connector on the faulty port of the BBU on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol or a clean cigarette filter. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module at one end of the link matches the optical module at
the other end, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s, 2.5
Gbit/s or other rate). Note that single-mode optical modules are labeled "1310nm",
while multi-mode ones are labeled "850nm".
Y => The optical module at one end of the CPRI link matches the optical module at the
other end. Go to sub-step e.
N => The optical module at one end of the CPRI link does not match the optical module
at the other end. Go to sub-step d.
d. On the basis of the optical module at one end of the link, select the optical module at
the other end.
Replace the optical module.
Check whether the alarm is cleared.
e. Run the MML command DSP SFP to query the transmission mode of the optical
module. The single-mode optical fiber is yellow in color and the multi-mode optical fiber
is orange in color. Check whether the optical module matches the connected optical
fiber, in terms of type (single-mode or multi-mode) and rate.
Y => The optical module matches the connected optical fiber. Go to step 4.
N => The optical module does not match the connected optical fiber. Go to sub-step f.
4. Connect the TX and RX ports of the optical module on the BBU on site.
a. Remove the optical fiber from the optical module of the BBU. Then, connect the TX and
RX ports of the optical module by using an optical fiber for loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step b.
N => The alarm is not cleared. Go to sub-step c.
b. Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the BBU. Then, Go to step 5.
c. Replace the optical module.
Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the BBU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
a. On the lower-level RF unit side, check whether the RUN LED on the RF unit blinks
normally (ON for 1s and OFF for 1s).
Y => The RUN LED blinks normally. Go to step 6.
N => The RUN LED does not blink normally. Go to sub-step b.
b. Power cycle the RF unit. Wait until the RUN LED blinks normally.
a. Reseat the optical module and connector on the CPRI port of the lower-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol or a clean cigarette filter. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module on the CPRI port is supported by the lower-level RF
unit, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s, 2.5 Gbit/s or
other rate).
Y => The optical module is supported. Go to sub-step e.
N => The optical module is not supported. Go to sub-step d.
7. Connect the TX and RX terminals of the optical fiber on the lower-level RF unit on site.
a. Remove the optical fiber from the optical module of the RF unit. Then, connect the TX
and RX terminals of the optical fiber by using a flange.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step c.
N => The alarm is not cleared. Go to sub-step b.
b. Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the RF unit. Then, go to step 8.
N => The alarm is not cleared. Reinstall the original board. Then, go to step 9.
a. Check the optical connections between the BBU and the lower-level RF unit.
Troubleshoot the improper optical connections, such as bent fiber or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
9. Check the optical modules at both ends of the link and the optical fiber on site.
a. Check whether the optical module of the BBU matches the optical moduleof the
lower-level RF unit, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s,
2.5 Gbit/s or other rate). Note that single-mode optical modules are labeled "1310nm",
while multi-mode ones are labeled "850nm".
Y => The optical module at one end of the link matches the optical module at the other
end. Go to sub-step c.
N => The optical module at one end of the link does not match the optical module at the
other end. Go to sub-step b.
b. On the basis of the optical module at one end of the CPRI link, select the optical
module at the other end.
Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical fiber matches the optical modules.
Y => The optical fiber matches the optical modules. Contact Huawei Customer Service
Center.
N => The optical fiber does not match the optical modules. Go to sub-step d.
d. Choose the optical fiber that matches the optical modules. Note that multi-mode optical
fibers are orange, while single-mode ones are yellow.
Replace the optical module.
Or
Replace the Optical Fiber.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the performance of the optical module on the port of the BBU connecting to the
lower-level RF units deteriorates.
Parameters
Major When the performance of the optical module deteriorates significantly, the quality of
services carried on the link of the RF units may decrease significantly, or the ongoing
services carried on lower-level RF units may even be interrupted. The services of the
peer mode are interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty port provides the aggregation function.
Minor When the performance of the optical module deteriorates to some extent, the quality
of services carried on the link of the RF units may decrease to some extent.
System Actions
None
Possible Causes
The optical module of the BBU connecting to the lower-level RF units is worn-out.
Procedure
1. Check the port of the BBU connecting to the lower-level RF units on site.
a. Reseat the optical module and connector on the faulty port of the BBU on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Description
This alarm is reported when the link (at the link layer) between the BBU and the lower-level RF units
malfunctions.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(CPRI Interface Initialization Failure, CPRI Interface Transmit
Problem Error, CPRI Interface Reception Error)
Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted. The services of the peer mode are
interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty port provides the aggregation function.
In ring topology, the reliability of the link decreases. In this case, the active link of
lower-level RF units is switched over to the standby link. In the case of a hot ring, the
ongoing services are not affected. In the case of a cold ring, the ongoing services
are disrupted temporarily.
System Actions
In ring topology, the lower-level RF units automatically switch to the normal link.
Possible Causes
If the optical transmission is used, the optical module or connector of the BBU or lower-level RF unit
may be improperly installed, the optical link is faulty, or the optical module is faulty.
If the electrical transmission is used, the cable connector of the BBU or lower-level RF unit may be
improperly installed, or the cable is faulty.
Data configuration is incorrect if a multi-mode base station reports the alarm. As a result, the timing
loop fails.
In multi-mode configuration, the inter-BBU connections are abnormal or the optical module used for
inter-BBU connection is faulty.
Procedure
a. Check for the correlated alarm on the faulty port of the BBU on the M2000:
26230 BBU CPRI Optical Module Fault
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26232 BBU Optical Module Transmit/Receive Fault
26272 Inter-System RF Unit Parameter Settings Conflict
26238 RRU Network Topology Type and Configuration Mismatch
26314 Inter-BBU Port Failure
26240 BBU Topology and Configuration Mismatch
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. Based on the alarm detailed information, run the MML command LST RRUCHAIN to
query the number of the chain/ring that holds the port.
b. Based on the queried chain/ring number, run the MML command LST RRU/DSP
RRUCHAINPHYTOPO to query the configured working mode of the RF unit. Check
whether the RF unit works in dual-mode configurations and whether the main control
boards of two modes are in different BBU subracks.
Y => The RF unit works in dual-mode configurations and the main control boards of two
modes are in different BBU subracks. Go to sub-step c.
N => The RF unit does not work in dual-mode configurations, or the main control boards
of two modes are in the same BBU subrack. Go to step 3.
c. Run the MML command LST SOFTWARE to query the software versions of two
modes. Based on the queried software versions, check whether both the two modes
support inter-BBU connection.
Y => Both the two modes support inter-BBU connection. Go to sub-step e.
N => Either of the two modes does not support inter-BBU connection. Go to sub-step d.
d. Upgrade the software of the mode that does not support inter-BBU connection by
referring to the relevant upgrade guide. Ensure that both the two modes support
inter-BBU connection.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Check for the correlated alarm on the faulty port of the BBU on the M2000: 26314
Inter-BBU Port Failure
26240 BBU Topology and Configuration Mismatch
Y => The correlated alarm exists. Go to sub-step f.
N => The correlated alarm does not exist. Go to step 3.
a. Run the MML command DSP SFP to check whether the optical module uses electrical
ports for transmission.
Y => The optical module uses electrical ports for transmission. Go to step 6.
N => The optical module does not use electrical ports for transmission. Go to step 4.
4. Connect the TX and RX ports of the optical module on the BBU side by using an optical fiber for
loopback.
a. Remove the connector of the optical module in the BBU. Use the absolute alcohol to
clean the connector. Then, reinstall the connector into the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the optical fibers from the optical module in the BBU. Then, connect the TX and
RX ports of the optical module by using an optical fiber for loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. Disconnect the optical fiber from the TX and RX ports of the
optical module, and restore the optical connection of the BBU. Then, go to step 5.
N => The alarm is not cleared. Go to sub-step c.
c. Replace the optical module on the BBU side.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
5. Connect the TX and RX terminals of the optical fibers for the RF unit onsite.
a. Remove the connector of the optical module in the RF unit. Use the absolute alcohol to
clean the connector. Then, reinstall the connector into the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the optical fibers from the optical module of the RF unit. Then, connect the TX
a. Remove and then insert the electrical cable between the BBU and lower-level RF units
on the BBU side.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
The BBU is connected to RF units by electrical cables or fiber optic cables. This alarm is reported when the
maintenance link between the BBU and an RF unit malfunctions.
Parameters
System Actions
The RF unit automatically resets 10 minutes after the maintenance link is broken.
Possible Causes
The fiber optic cable or electrical cable between the BBU and the RF unit or between upper- and
lower-level RF units is faulty.
The RF unit experiences an AC power failure, is not powered on, or is running improperly.
The RF unit is automatically reset due to a fault, or the RF unit is manually reset.
When the dual-mode CPRI MUX topology is adopted, the optical module of the baseband board
working in the mode that aggregates data is faulty.
When the dual-mode CPRI MUX topology is adopted, the backplane link between the baseband
boards working in two modes has insufficient resources, or the backplane link is faulty.
When the dual-mode CPRI MUX topology is adopted, the baseband board working in the mode that
aggregates data has hardware faults, is not installed, is not powered on, or is not configured.
When the dual-mode CPRI MUX topology is adopted, the hardware of the baseband board working
in either side does not support backplane aggregation.
Procedure
1. Check the topology of the faulty RF unit on the M2000. (For details about the CPRI MUX topology,
see the 3900 Series Base Station Technical Description.)
a. Based on the alarm detailed information, run the LST RRUCHAIN command to check
whether Access Type of the RRU chain/ring is set to PEERPORT(peer port).
Y => Access Type of the RRU chain/ring is set to PEERPORT(peer port). Go to
substep b.
N => Access Type of the RRU chain/ring is set to LOCALPORT(local port). Go to step
2.
b. Check whether this alarm is also reported in the mode that aggregates data on the
M2000.
Y => This alarm is reported in the mode that aggregates data. Clear the alarm in the
mode that aggregates data. Go to step 2.
N => This alarm is not reported in the mode that aggregates data. Go to step 3.
a. Check for the correlated alarm on the port of the RF unit on the M2000:
26234 BBU CPRI Interface Error
26230 BBU CPRI Optical Module Fault
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26232 BBU Optical Module Transmit/Receive Fault
26233 BBU CPRI Optical Interface Performance Degraded
26200 Board Hardware Fault
26204 Board Not In Position
26501 RF Unit Optical Module or Electrical Port Not Ready
26502 RF Unit Optical Module Type Mismatch
26503 RF Unit Optical Module Transmit/Receive Fault
26504 RF Unit CPRI Interface Error
26506 RF Unit Optical Interface Performance Degraded
26507 RF Unit Optical Module Fault
26532 RF Unit Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 6.
3. Check for the correlated alarms in the mode whose data is aggregated on the M2000.
a. Check whether any of the following correlated alarms is reported on a baseband board
working in the mode whose data is aggregated:
26200 Board Hardware Fault
26204 Board Not In Position
26215 Inter-Board Service Link Failure
Y => One of the preceding alarms is reported. Go to substep b.
N => None of the preceding alarms is reported. Go to step 4.
4. Check the configuration of the baseband board in the mode that aggregates data on the M2000.
a. Run the DSP BRD command to check whether the baseband board is configured in the
mode that aggregates data.
Y => The baseband board is configured. Go to step 5.
N => The baseband board is not configured. Go to substep b.
b. Run the ADD BRD command to add a baseband board to the mode that aggregates
data.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
5. Check the capability of the baseband boards working in both modes on the M2000.
a. Run the DSP BRDMFRINFO to query the types of the baseband boards. Check
whether the baseband boards in both sides support the CPRI MUX topology according
to the DBS3900 Hardware Description.
Y => The baseband boards support the CPRI MUX topology. Go to step 6.
N => The baseband boards do not support the CPRI MUX topology. Go to substep b.
b. Replace the baseband board with a board that supports the CPRI MUX topology.
Replace the Board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
a. Check whether the RUN LED on the RF unit blinks (ON for 1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). Go to step 8.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). Go to sub-step b.
b. Power cycle the RF unit. Wait until the RUN LED blinks (ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 8.
This alarm is reported when the actual RRU cascading levels mismatch the configuration.
Parameters
Major When the actual RRU cascading levels mismatch the configuration, the RRUs that
are not configured cannot carry services.
System Actions
None
Possible Causes
The maintenance link for a cascaded RRU fails, or a cascaded RRU is powered off or not installed.
Procedure
a. Based on the alarm detailed information, check whether the RRU cascading levels in the
chain/ring configuration are consistent with the site plan.
Y => The RRU cascading levels are consistent with the site plan. Go to step 2.
N => The RRU cascading levels are inconsistent with the site plan. Go to sub-step b.
a. Check whether the actual RRU cascading levels are consistent with the RRU cascading
levels in the site plan.
Y => The actual RRU cascading levels are consistent with the site plan. Contact Huawei
Customer Service Center.
N => The actual RRU cascading levels are inconsistent with the site plan. Go to
sub-step b.
b. Remove the RRU according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Major In chain topology, the RRUs lower than the breakpoint cannot carry services. The
services carried on the lower-level RRUs in the peer mode are interrupted when the
following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The port that carries the faulty chain provides the aggregation function.
In ring topology, the RRUs between two breakpoints cannot carry services. In this
case, the reliability of the RRU link decreases.
System Actions
None
Possible Causes
Procedure
a. Consult the customer about the reason for the breakpoint in the RRU chain/ring. Check
whether it is allowed to cancel the breakpoint in the RRU chain/ring.
Y => It is allowed to cancel the breakpoint. Go to sub-step b.
N => It is not allowed to cancel the breakpoint. No further action is required.
b. Run the MML command MOD RRUCHAIN to cancel the breakpoint in the RRU
chain/ring.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the user-configured RRU chain/ring topology is inconsistent with the actual RRU
chain/ring topology.
Parameters
Inconsistency Type Type of inconsistency between topology and configuration (Chain Head
Configuration Error, Chain Tail Configuration Error, Dual-Star Configuration Error)
Configured Slot No. of RF Slot number of the RF interface board configured by the user
Interface Board
Configured Port No. of RF Port number of the RF interface board configured by the user
Interface Board
Actual Slot No. of RF Slot number of the RF interface board actually used
Interface Board
Actual Port No. of RF Port number of the RF interface board actually used
Interface Board
Major If the chain topology is configured but the ring topology is actually used, the reliability
of the RRU link decreases.
If the ring topology is configured but the chain topology is actually used, the RRU link
is not affected.
System Actions
None
Possible Causes
The user configures the RRU chain topology, but the RRU ring topology is actually used.
The user configures the RRU ring topology, but the RRU chain topology is actually used.
The topology configuration is consistent with the actual network (both are the ring topology), but
there is one (only one) configured port which is inconsistent with the actually used port.
In the dual-star topology, more than one RRU is connected to the RRU chain.
Procedure
a. Check for the correlated alarm of the faulty board on the M2000:
26231 BBU CPRI Optical Module or Electrical Port Not Ready
26232 BBU Optical Module Transmit/Receive Fault
26501 RF Unit Optical Module or Electrical Port Not Ready
26503 RF Unit Optical Module Transmit/Receive Fault
26272 Inter-System RF Unit Parameter Settings Conflict
26274 Inter-System Board Object Configuration Conflict
a. Run the MML command LST RRUCHAIN to check whether the configured RRU
networking mode and port settings are consistent with the site plan.
Y => The configured RRU networking mode and port settings are consistent with the
site plan. Go to step 3.
N => The configured RRU networking mode and port settings are inconsistent with the
site plan. Go to sub-step b.
b. In the case of the inconsistent networking mode, change the RRU networking mode.
In the case of the inconsistent port settings, run the MML command MOD RRUCHAIN
to modify the RRU chain/ring port settings according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Check whether the actual RRU networking mode and port settings are consistent with
the site plan.
Y => The actual RRU networking mode and port settings are consistent with the site
plan. Contact Huawei Customer Service Center.
N => The actual RRU networking mode and port settings are inconsistent with the site
plan. Go to sub-step b.
b. Adjust the connections between RRUs and the peer device (upper- or lower-level RRU
or the BBU) according to the site plan. Ensure that the actual RRU networking mode
and port settings are consistent with the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the user-configured inter-BBU connection topology is inconsistent with the actual
inter-BBU connection topology. This alarm is only reported by a 2U BBU.
Parameters
Slot No. of the Upper-Level Board Slot number of the board connected to the BBU
Port No. of the Upper-Level Board Port number of the board connected to the BBU
Major If the BBUs are interconnected by UCIU+UCIU/UMPT, the BBUs cannot share
control data, clock signal, and transmission data. Services may be interrupted.
If the BBUs are interconnected by WBBPf+WBBPf, then:
The baseband data and signaling exchange between BBUs are affected.
Services are not provided on the side where this alarm is reported, or the service
processing capability decreases.
System Actions
None
Possible Causes
Procedure
a. Check for the correlated alarm on the inter-BBU interface of the UCIU on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
Y => The correlated alarm exists. Go to substep b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command LST CTRLLNK to query the UCIU topology configuration in the
local mode. Check whether the UCIU topology configuration is correct based on the
configuration plan. Alternatively, run the MML command LST BBPLNK to query the
configuration for the WBBPf+WBBPf interconnection topology. Check whether the
a. Based on the alarm parameters, locate the port on the faulty UCIU and its
interconnected port on the upper-level board. Then, change the inter-BBU cable
connections on the port of the UCIU based on the configuration plan. Ensure that the
inter-BBU connection topology is consistent with the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
During the base station operation, the updated data configuration may fail to be saved in the configuration file.
This alarm is reported when the running data of a base station is inconsistent with the data in the configuration
file of the base station.
Parameters
None.
Major The updated data configuration fails to be saved in the configuration file. After the NE
resets, the updated data configuration is lost.
System Actions
None
Possible Causes
Procedure
a. Note: Resetting the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the main control board. Wait until the board
startup is complete.
b. Run the configuration command again. Check whether the alarm is reported again.
Y => The alarm persists. Go to step 2.
N => The alarm is cleared. No further action is required.
a. Note: Replacing the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. The base station software
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board.
b. Run the configuration command again. Check whether the alarm is reported again.
Y => The alarm persists. Contact Huawei Customer Service Center.
N => The alarm is cleared. No further action is required.
The system performs validity check on the configuration file in the case of startup. This alarm is reported when
the configuration file is invalid.
Parameters
None.
Major When the configuration file is invalid, part of or all the data configuration of the
system is lost. In this case, the NE may fail to carry services.
System Actions
None
Possible Causes
The main control board is reset improperly or is powered off. In this case, the flash or file system
error occurs, and the configuration file is damaged.
The current configuration file does not match the software version.
Procedure
1. Obtain the backup configuration file for data recovery on the M2000.
b. Run the MML command DLD CFGFILE to download the configuration file to the NE.
c. Run the MML command SET CFGFILEENB to enable the configuration file to take
effect immediately.
This alarm is reported when the running data of the NE is inconsistent with the user-configured data during the
data consistency check.
Parameters
Major The system cannot work with the latest data that is configured by the user.
System Actions
None
Possible Causes
Procedure
a. Run the MML command RST BRD to reset the faulty board.
Check whether the alarm is reported again.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Note: Resetting the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the main control board.
Check whether the alarm is reported again.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
A base station has two storage spaces, which are active workspace and standby workspace. The active
workspace stores the running software version and the standby workspace stores the earlier software version.
This alarm is reported when the software version in the active workspace is incomplete, unrecognizable, or
empty in the case of the NE startup.
Parameters
None.
Major The NE cannot perform the software version check for boards and the board
software cannot be activated. If the board software mismatches the main control
software of the NE, the board cannot obtain the correct software version from the
active workspace. In this case, the board cannot carry services.
System Actions
None
Possible Causes
Procedure
a. Run the MML command LST SOFTWARE to check whether the software version in the
standby workspace is usable.
Y => The software version in the standby workspace is usable and is the currently
expected version. Go to sub-step b.
N => The software version in the standby workspace is unusable or is not the expected
version. Go to step 2.
b. Run the MML command ACT SOFTWARE to activate the NE software in the standby
workspace. Wait until the NE startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command DLD SOFTWARE to download the software package of the
same version as that in the site plan.
b. Run the MML command ACT SOFTWARE to activate the software package.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Note: Replacing the main control board interrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. The base station software
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original main control board. Contact Huawei
Customer Service Center.
This alarm is reported when the actual board type in the slot is different from the configured board/sub-board
type.
Parameters
Major Services cannot be carried on the board. The services of the peer mode are
interrupted when the following conditions are met:
The RF units use the CPRI MUX topology.
The local mode provides the aggregation function.
The faulty board is a baseband board that provides the aggregation function.
System Actions
The system automatically disables the board and isolates the board from all other boards.
Possible Causes
Procedure
a. Run the MML command DSP BRD to check whether the type of the configured board
or RF unit in the slot is consistent with the configuration plan.
Y => The type of the configured board or RF unit is consistent with the configuration
plan. Go to step 2.
N => The type of the configured board or RF unit is inconsistent with the configuration
plan. Go to sub-step b.
b. Check whether the hardware type of the faulty board is a RF unit according to the
alarm detailed information on the M2000.
Y => The hardware type of the faulty board is a RF unit. Go to sub-step e.
N => The hardware type of the faulty board is not a RF unit. Go to sub-step c.
c. Run the MML command RMV BRD to remove the configured board in the slot.
d. Run the MML command ADD BRD to configure the correct board in the slot according
to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
e. Run the MML command RMV RRU to remove the configured RF unit in the slot.
f. Run the MML command ADD RRU to configure the correct RF unit in the slot according
to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Based on the alarm detailed information, check whether the board type is the UTRP.
Y => The board type is the UTRP. Go to sub-step b.
N => The board type is not the UTRP. Go to step 3.
b. Run the MML command DSP BRD to query the sub-board type. Check whether the
configured sub-board is consistent with the installed sub-board.
Y => The configured sub-board is consistent with the installed sub-board. Go to step 3.
N => The configured sub-board is inconsistent with the installed sub-board. Go to
sub-step c.
c. Run the MML command ADD BRD to change the sub-board type according to the
installed sub-board type.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the system detects a new board type but the matching board software is
unavailable in the active workspace and the software auto-supply from the M2000 fails.
Parameters
System Actions
None
Possible Causes
The board type has never been configured earlier or the file system of the base station is damaged,
and the communication between the NE and the M2000 fails.
Procedure
b. Run the MML command SPL SOFTWARE to start the software auto-supply for the NE.
Wait until the process is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the base station detects that the board software mismatches the base station
software, and the automatic version synchronization fails.
Parameters
Parameter
Name Parameter Description
Possible Possible cause of the activation failure (Board BootROM Incompatible with Software Version
Cause to be Activated, Board Flash Available Space Insufficient, Other Internal Errors)
System Actions
None
Possible Causes
The board software upgrade fails during the NE software upgrade. In this case, the board BootROM
upgrade fails.
Procedure
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "Board BootROM Incompatible with Software Version to be
Activated", go to step 2.
If "Specific Problem" is "Board Flash Available Space Insufficient", go to step 4.
If "Specific Problem" is "Other Internal Errors", go to step 3.
a. Run the MML command DLD SOFTWARE to manually download the board BootROM
version. Select "BootROM" in the software type field.
b. Run the MML command ACT SOFTWARE to manually activate the board BootROM
version. Select "BootROM" in the software type field.
c. Run the MML command RST BRD to reset the board. Wait until the board startup is
complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Run the MML command ACT SOFTWARE to activate the board software. Select
"Software" in the software type field. Wait until the board startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
This alarm is reported when the automatic version rollback occurs in the case that the current version is
improper.
Parameters
None.
Major Version rollback leads to NE reset. During the reset, the ongoing services carried on
the NE are disrupted.
System Actions
None
Possible Causes
Procedure
b. Change the target software version to one that supports a smooth upgrade.
Go to sub-step 4.
This alarm is reported when the base station uses the local crystal oscillator longer than its duration limit (90
days).
Parameters
None.
Major The quality of services of the base station decreases, resulting in handover failure
and call drop. In certain cases, the base station cannot provide services.
System Actions
None
Possible Causes
Procedure
This alarm is reported when the external clock reference for the base station is not configured.
Parameters
None.
Minor The system clock may be unusable if the base station does not obtain the clock
reference for a long period of time. As a result, the quality of services of the base
station decreases, resulting in handover failure and call drop. In certain cases, the
base station cannot provide services.
System Actions
None
Possible Causes
The external clock reference is not configured for the base station.
Procedure
1. Add the external clock reference for the base station on the M2000.
This alarm is reported in the case of clock reference loss, external clock reference unavailability due to
unacceptable quality, excessive frequency deviation between the clock reference and the local oscillator, or
unstable frequency of the clock reference.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Clock Reference Lost, Clock Reference Unavailable, Excessive
Problem Frequency Difference Between Clock Reference and Local Crystal Oscillator, Excessive
Frequency Variation of Clock Reference, Excessive Phase Difference Between Clock Reference
and Local Crystal Oscillator, Inconsistent Clock References, IPCLK Reference Unavailable due
to Unacceptable Quality, SYNCETH Clock Reference Unavailable due to Unacceptable Quality,
GPS Clock Reference Unavailable due to Unacceptable Quality, TOD Clock Reference
Unavailable due to Unacceptable Quality)
Minor The base station fails to synchronize to the clock reference. The system clock may
be unusable if the base station does not obtain the clock reference for a long period
of time. As a result, the quality of services of the base station decreases, resulting in
handover failure and call drop. In certain cases, the base station cannot provide
services.
System Actions
None
Possible Causes
If the clock reference is GPS clock, the GPS antenna may be faulty or the number of locked GPS
satellites may be insufficient.
The clock reference is incorrectly configured.
Procedure
a. Check whether this alarm is reported on a large number of base stations on the M2000.
Y => This alarm is reported on a large number of base stations due to poor
transmission quality or faulty clock source. Go to sub-step b.
N => This alarm is reported only on a few base stations. Go to step 2.
b. Obtain the clock topology, and check the clock transmission link, clock configuration, or
clock source as indicated by the possible alarm cause.
Wait 5 to 120 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2
a. Check for the correlated alarm of the faulty clock board or port on the M2000.
26121 GPS Antenna Fault
26122 GPS Locked Satellites Insufficient
26120 GPS Clock Output Unavailable
26123 GPS Maintenance Link Failure
26263 IP Clock Link Failure
25800 E1/T1 Loss of Signal
25880 Ethernet Link Fault
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault
25885 IP Address Conflict
26200 Board Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 3.
3. Check the clock reference on the basis of configuration plan on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference is
consistent with the configuration plan.
Y => The clock reference is consistent with the configuration plan. Go to step 4.
N => The clock reference is inconsistent with the configuration plan. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference according to
the configuration plan.
Wait for 5 to 120 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
a. Locate the cause of the alarm based on the alarm location information.
If "Specific Problem" is "IPCLK Reference Unavailable due to Unacceptable Quality", go
to step 5.
If "Specific Problem" is "Excessive Frequency Difference Between Clock Reference and
Local Crystal Oscillator" or unstable frequency of the clock reference, go to step 6.
.
If "Specific Problem" is "SYNCETH Clock Reference Unavailable due to Unacceptable
Quality", check the quality of synchronous Ethernet clock signals extracted from the
upper-level network node.
If "Specific Problem" is "GPS Clock Reference Unavailable due to Unacceptable
Quality", check the status of GPS equipment or the environment.
If "Specific Problem" is "TOD Clock Reference Unavailable due to Unacceptable
Quality", check the quality of TOD clock signals.
If "Specific Problem" is not one of the preceding causes, Contact Huawei Customer
Service Center.
a. Contact maintenance personnel of the IP Clock server to solve the unavailable IP clock
reference problem so that the IP clock reference quality meets the requirements of the
base station.
Wait for 5 to 120 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the IP clock link connected to the clock server fails.
Parameters
Minor The base station fails to synchronize to the IP clock reference. The system clock
may be unusable if the base station does not obtain the clock reference for a long
period of time. As a result, the quality of services of the base station decreases,
resulting in handover failure and call drop. In certain cases, the base station cannot
provide services.
System Actions
None
Possible Causes
Procedure
a. Check for the correlated alarm of the port that bears the IPCLK link on the M2000.
26220 Transmission Optical Module Fault
26221 Transmission Optical Module Not In Position
26222 Transmission Optical Interface Error
26223 Transmission Optical Interface Performance Degraded
25880 Ethernet Link Fault
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault
25885 IP Address Conflict
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. Run the MML command LST IPCLKLINK to check whether the IP address of the clock
server and the IPCLK type are consistent with the network plan.
Y => The IP address of the clock server and the IPCLK type are consistent with the
network plan. Go to step 3.
N => The IP address of the clock server and the IPCLK type are inconsistent with the
network plan. Go to sub-step b.
b. Run the MML command RMV IPCLKLINK/ADD IPCLKLINK to change the configuration
of IPCLK link.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Check the configuration of route from the NE to the clock server on the M2000.
a. Run the MML command LST IPRT to query all the current routes. Check whether an IP
route connecting the peer clock server exists.
Y => There is an IP route connecting the peer clock server. Go to step 4.
N => There is no IP route connecting the peer clock server. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route connecting the peer clock server.
Then, wait for at least five minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
4. Check the reachability of route from the NE to the clock server on the M2000.
a. Run the MML command PING to check whether the route from the NE to the clock
server is reachable.
Y => The route is reachable. Go to sub-step d.
N => The route is not reachable. Go to sub-step b.
b. Contact the maintenance engineer responsible for the clock server to rectify the fault on
the clock server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Contact the maintenance engineer responsible for the routing device to rectify the route
fault.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. Contact the maintenance engineer responsible for the clock server to troubleshoot the
improper processes of the clock server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when a clock phase-locked loop in the board is unlocked.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Software Phase Lock Loop Loss of Lock, Hardware Phase
Problem Lock Loop Loss of Lock)
Minor The system clock fails after a certain period (around 90 days). The ongoing services
carried on the board are disrupted.
Major The system clock fails. The ongoing services carried on the board are disrupted.
System Actions
None
Possible Causes
If this alarm is reported on a non-main control board, the board may not be securely installed.
Procedure
This alarm is reported when the frame number received on the board for synchronization has errors.
Parameters
System Actions
None
Possible Causes
The system clock phase-locked loop in the main control board is unlocked.
Procedure
a. Check for the correlated alarm of the faulty board or main control board on the M2000:
26264 System Clock Unlocked
26200 Board Hardware Fault
This alarm is reported when the time synchronization between the NE and the time synchronization server fails.
Parameters
Minor The time of the base station fails to synchronize with the time of the M2000. As a
result, the time the base station reports alarms and logs is different from the time of
the M2000 and therefore inventory information on the M2000 cannot be automatically
updated, possibly leading to unreliable traffic statistics.
System Actions
None
Possible Causes
The route from the NE to the SNTP/NTP server is not configured or is not reachable.
Procedure
a. Check for the correlated alarm of the port used for time synchronization on the M2000.
25880 Ethernet Link Fault
26121 GPS Antenna Fault
26122 GPS Locked Satellites Insufficient
26120 GPS Clock Output Unavailable
26123 GPS Maintenance Link Failure
25800 E1/T1 Loss of Signal
25806 E1/T1 Excessive Bit Error Rate
25881 MAC Excessive Frame Error Rate
25883 ETHOAM 3AH Local Fault
25884 ETHOAM 3AH Remote Fault
25885 IP Address Conflict
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm with recommended actions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the configuration of time reference on the basis of the configuration plan on the M2000.
a. Run the MML command LST TIMESRC to check whether the configuration of time
reference is consistent with the configuration plan.
Y => The configuration of time reference is consistent with the configuration plan. Go to
step 3.
N => The configuration of time reference is inconsistent with the configuration plan. Go
to sub-step b.
b. Run the MML command SET TIMESRC to change the configuration of time reference.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Run the MML command LST SNTPCLTPARA to check whether the IP address and
port No. of the NTP/SNTP server are consistent with the network plan.
Y => The parameter settings are consistent. Go to sub-step c.
N => The parameter settings are inconsistent. Go to sub-step b.
b. Run the MML command SET SNTPCLTPARAto change the IP address and port No. of
the NTP/SNTP server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Run the MML command LST SNTPCLTPARA to check whether the NTP/SNTP
synchronization service is started.
Y => The NTP/SNTP synchronization service is started. Go to step 4.
N => The NTP/SNTP synchronization service is not started. Go to sub-step d.
d. Run the MML command SET SNTPCLTPARA to start the NTP/SNTP synchronization
service.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
4. Check the configuration of route from the NE to the NTP/SNTP server on the M2000.
a. Run the MML command LST IPRT to query all the current routes.
Check whether an IP route connecting the SNTP/NTP server exists.
Y => There is an IP route connecting the SNTP/NTP server. Go to step 5.
N => There is no IP route connecting the SNTP/NTP server. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route connecting the NTP/SNTP
server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
5. Check the reachability of route from the NE to the NTP/SNTP server on the M2000.
a. Run the MML command PING to check whether the NTP/SNTP server can be
connected.
Y => The NTP/SNTP server can be connected. Go to sub-step d.
N => The NTP/SNTP server cannot be connected. Go to sub-step b.
b. Contact the maintenance engineer responsible for the NTP/SNTP server to rectify the
fault on the NTP/SNTP server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Contact the maintenance engineer responsible for the routing device to rectify the route
fault.
The main control boards in different modes of a multi-mode base station periodically exchange control
information. If the main control board in one mode does not receive any handshake response message from its
counterpart within about 45s, this alarm is reported This alarm is cleared when the main control board in one
mode successfully receives a handshake response message from its counterpart within about 30s.
Parameters
Parameter
Name Parameter Description
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Major The consistency check cannot be performed for inter-RAT configuration. Common
alarms cannot be identified, affecting alarm monitoring.
System Actions
None
Possible Causes
The base station in the other mode is repeatedly reset because the connection between the base
station and the base station controller or M2000 is disrupted for a long time.
The base station in the other mode is repeatedly reset because the base station is installed but not
configured.
The base station in the other mode is reset after a software upgrade or after a reset command is
issued.
The main control board of the 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.
In multi-mode configuration, the inter-BBU connections are abnormal or the optical module used for
inter-BBU connection is faulty.
Procedure
a. Check whether any of the following alarms on the faulty port of the BBU on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
26315 Inter-BBU Port Connection Error
26240 BBU Topology and Configuration Mismatch
Y => A correlated alarm is reported. Go to sub-step b.
N => A correlated alarm is not reported. Go to step 2.
2. Check the status of the main control board in the other mode on the M2000.
a. Click Device Panel on the M2000, and check whether the status of the main control
board in the other mode is normal.
Y => The status of the main control board in the other mode is normal. Go to step 3.
N => The status of the main control board in the other mode is abnormal. Go to
sub-step b.
b. Wait 5 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Reset the main control board of the current mode on the M2000.
a. Note: Resetting the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the main control board of the current mode.
Wait until the board startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
4. Reset the main control board of the other mode on the M2000.
a. Note: Resetting the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the main control board of the other mode.
Wait until the board startup is complete.
a. Note: Removing or reseating the main control board disrupts all the ongoing services of
the base station. Therefore, perform this operation in low-traffic hours.
Reseat the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
a. Note: Removing or reseating the main control board disrupts all the ongoing services of
the base station. Therefore, perform this operation in low-traffic hours.
Reseat the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
a. Note: Replacing the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. The base station software
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 8.
a. Note: Replacing the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. The base station software
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the parameter settings of a monitoring device in a mode
are inconsistent with those of the same monitoring device in the other mode.
Parameters
Parameter
Name Parameter Description
Warning The parameter settings of a monitoring device in a mode are incorrect. In this case,
the related data configuration may not take effect in this mode, and alarms may be
falsely reported.
System Actions
None
Possible Causes
Procedure
1. Check the parameter settings of the monitoring device in two modes on the Configuration
Management Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty monitoring device.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the monitoring device in two modes according to the configuration
plan. Ensure the parameter consistency in two modes.
In multi-mode configuration, this alarm is reported when the parameter settings of an RF unit in a mode are
inconsistent with those of the same RF unit in the other mode, such as the working mode or other RF
parameters.
Parameters
Parameter
Name Parameter Description
Configuration Configuration item (IF Offset, TX Gain, AGC Flag, DPD Flag, PAR Flag, CPRI Port
Item Configuration, SEM Enabling Flag, Receive Desensitivity, RTWP Correction Value, RF
Desensitivity, Delay Compensation, T1/L Timing Delay Compensation, VSWR Alarm Threshold,
Attenuation, ALD Current Threshold, VSWR Threshold, External Boolean Alarm Port, Alarm
Parameters, Radio Interconnection Mode, Topology Type, RF Unit Working Mode Conflict)
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Major If the configured working mode of an RF unit in one mode is inconsistent with that of
the same RF unit in the other mode, the software management of the RF unit is
affected. In this case, the ongoing services carried on the RF unit may be affected.
If other parameters of an RF unit in one mode are inconsistent with those of the
same RF unit in the other mode, the data configuration of the RF unit in one mode
cannot take effect. In this case, problems may occur.
Warning If other parameters of an RF unit in one mode are inconsistent with those of the
same RF unit in the other mode, the data configuration of the RF unit in one mode
cannot take effect. In this case, problems may occur.
System Actions
If the configured working mode of an RF unit in one mode is inconsistent with that of the same RF unit in the
other mode, the system does not load the board software of the RF unit.
Possible Causes
other mode.
Procedure
a. Check the value of the "Configuration Item" parameter in the alarm information.
If the value of "Configuration Item" is "Radio Interconnection Mode", go to substep b.
If the value of "Configuration Item" is not "Radio Interconnection Mode", go to step 2.
b. Run the LST BTSRXUBP command on the GSM side to query the TX/RX mode of the
faulty RF unit. If the TX/RX mode is "Single Feeder(1TX + 2RX)", the RF unit is
interconnected with another RF unit.
Run the LST SEC command on the UMTS side to query the interconnection mode of the
faulty RF unit. If the value of "RF Interconnection Mode" is "TRUE", the RF unit is
interconnected with another RF unit.
c. Check whether the settings of the RF unit interconnection mode are consistent between
the GSM and UMTS sides.
Y => The settings are consistent. Contact Huawei Customer Service Center.
N => The settings are inconsistent. Go to substep d.
d. Run the SET BTSRXUBP command on the GSM side to change the TX/RX mode of the
faulty RF unit to the value specified in the configuration plan.
Run the RMV SEC and ADD SEC commands on the UMTS side to change the
interconnection mode of the faulty RF unit to the value specified in the configuration
plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the parameter settings of the RF unit in two modes on the Configuration Management
Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty RF unit.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the RF unit in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the parameter settings of boards in a BBU in a mode
are inconsistent with those in the same BBU in the other mode.
Parameters
Parameter
Name Parameter Description
Configuration Configuration item (Dry Contact Alarm Level Conflict, GPS Parameters Conflict,
Item Convergency topology Conflict)
Warning If the configuration of dry contacts for the UPEU/UEIU in two modes is inconsistent,
alarms are falsely reported on the mode with wrong configuration.
If the GPS configuration for the USCU in two modes is inconsistent, the data
configuration on one mode cannot take effect.
Major If the networking configuration of the RF units is inconsistent between the two
modes, the multi-mode RF units cannot work properly.
System Actions
None
Possible Causes
The configuration of dry contacts for the UPEU/UEIU in a mode is inconsistent with that in the other
mode.
The GPS configuration for the USCU in a mode is inconsistent with that in the other mode.
The networking configuration of the RF units is inconsistent between the two modes.
Procedure
1. Check the parameter settings of the board in two modes on the Configuration Management Express
(CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty board.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the board in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the cabinet/subrack/slot configuration of a board is
inconsistent in different modes, when the cabinet/subrack/slot configuration of different boards is the same in
different modes, or when a board supporting only a certain mode is configured for different modes.
Parameters
Parameter
Name Parameter Description
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Peer Cabinet Cabinet number of the faulty board in the peer working mode
No.
Peer Subrack Subrack number of the faulty board in the peer working mode
No.
Peer Slot No. Slot number of the faulty board in the peer working mode
Major The board with configuration conflict cannot be maintained in the way that a common
board is handled. In this case, the inventory information error occurs. For the RF
units, the automatic software update fails in the case of software upgrades. In this
case, the ongoing services carried on the RF units are disrupted. When a board
supporting only one mode is configured for different modes, the board fails to work
normally.
System Actions
None
Possible Causes
When this alarm is reported on a monitoring board, the possible causes are as follows: Incorrect
cabinet, subrack, or slot number. Incorrect cabinet or subrack number of the device managing the
monitoring device. Incorrect serial port number. Incorrect communication IP address. When this
alarm is reported on other boards, the possible causes are that the cabinet, subrack, or slot number
of the board is incorrect.
Procedure
a. Locate the cause of the alarm based on the alarm detailed information.
a. Run the MML command RMV BRD to remove the board in a mode based on the
configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Locate the board type of the alarm based on the alarm location information.
If "Board Type" is a board of BBU, go to step 4.
If "Board Type" is RRU, go to step 6.
If "Board Type" is a monitoring device, go to step 8.
a. Run the MML command DSP BRD to check whether the cabinet/subrack/slot
configuration of the faulty board in the current mode is correct according to the
configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Go to step 5.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
b. Run the MML command RMV BRD to remove the board in the current mode.
c. Run the MML command ADD BRD to add the board in the current mode. Set the
cabinet/subrack/slot of the board according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty board
in the other mode is correct according to the configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Contact Huawei Customer
Service Center.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
b. Remove the board in the other mode on the M2000.
c. Add the board in the other mode on the M2000. Set the cabinet/subrack/slot of the
board according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Run the MML command LST RRU to check whether the cabinet/subrack/slot
configuration of the faulty RRU in the current mode is correct according to the
configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Go to step 7.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
b. Run the MML command RMV RRU to remove the RRU in the current mode.
c. Run the MML command ADD RRU to add the RRU in the current mode. Set the
cabinet/subrack/slot of the board according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
a. On the M2000, check whether the cabinet/subrack/slot configuration of the faulty RRU
in the other mode is correct according to the configuration plan.
Y => The cabinet/subrack/slot configuration is correct. Contact Huawei Customer
Service Center.
N => The cabinet/subrack/slot configuration is incorrect. Go to sub-step b.
c. Add the RRU in the other mode on the M2000. Set the cabinet/subrack/slot of the
board according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
8. Check the monitoring device configuration in the current mode on the M2000.
9. Check the monitoring device configuration in the other mode on the M2000.
c. Add the monitoring device in the other mode on the M2000. Set the cabinet/subrack/slot
of the board according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In a multi-mode base station, this alarm is reported when the cabinet configuration of one mode is inconsistent
with that of the other mode, such as the cabinet type.
Parameters
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Minor The cabinet type in different modes conflicts, which affects the configuration,
maintenance of the cabinet, as well as the inventory information recording.
System Actions
None
Possible Causes
In a multi-mode base station, the cabinet type of one mode is incorrectly configured.
Procedure
1. Check the cabinet configuration in two modes on the Configuration Management Express (CME).
a. Start the CME and check data consistency of the multi-mode base station based on the
CME help. Check for the error(s) corresponding to the faulty cabinet.
Y => There is an error. Go to sub-step b.
N => There is no error. Contact Huawei Customer Service Center.
b. Based on the detected error(s) and the common parameter checklist, modify the
parameter settings of the cabinet in two modes according to the configuration plan.
Ensure the parameter consistency in two modes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the site-level configuration in a mode conflicts with that
in the other mode. The site-level configuration includes the clock reference type and deployment ID (DID).
Parameters
Parameter
Name Parameter Description
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Major When the clock source type configured for a mode is incorrect, the clock source in
the mode is unavailable. In this case, the system clock works in free-run mode.
Services are not affected during a short period (three months).
When the DID configured for a mode is incorrect, users cannot manage the mode by
DID.
System Actions
None
Possible Causes
Procedure
a. Check the cause of the alarm based on the alarm location information.
If the alarm is caused by a clock reference type configuration conflict, go to step 2.
If the alarm is caused by a DID configuration conflict, go to step 4.
2. Check the clock reference type of the local mode on the M2000.
a. Run the MML command LST CLKMODE to check whether the clock reference type of
the local mode is correct according to the site plan.
Y => The clock reference type of the local mode is correct. Go to step 2.
N => The clock reference type of the local mode is incorrect. Go to sub-step b.
b. Run the MML command SET CLKMODE to change the clock reference type of the
local mode according to the site plan.
Check whether the alarm is cleared.
3. Check the clock reference type of the other mode on the M2000.
a. Check whether the clock reference type of the other mode is correct according to the
site plan.
Y => The clock reference type of the other mode is correct. Contact Huawei Customer
Service Center.
N => The clock reference type of the other mode is incorrect. Go to sub-step b.
b. Change the clock reference type of the other mode according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Run the MML command LST EQUIPMENT to check whether the DID of the local mode
is correct according to the site plan.
Y => The DID of the local mode is correct. Go to step 5.
N => The DID of the local mode is incorrect. Go to sub-step b.
b. Run the MML command SET EQUIPMENT to change the DID of the local mode
according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. Check whether the DID of the other mode is correct according to the site plan.
Y => The DID of the other mode is correct. Contact Huawei Customer Service Center.
N => The DID of the other mode is incorrect. Go to sub-step b.
b. Change the DID of the other mode according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the loading control rights are not configured or
inconsistent between different modes in the base station.
Parameters
Parameter
Name Parameter Description
Peer Mode Working mode of the peer end (UMTS, GSM, CDMA, WiMAX, LTE, UMB, TD-SCDMA,
Unknown)
Major When the loading control rights conflict, the software version of the USCU and the
shared RF units between different modes may be wrong. In this case, some
functions of the multi-mode base station fail and the reliability decreases.
System Actions
None
Possible Causes
The loading control rights are not configured after the multi-mode base station is deployed.
The loading control rights are not configured after the main control board is replaced in the
multi-mode base station.
The loading control rights are inconsistent between the current mode and the other mode.
Procedure
a. Note: Before you set the loading control rights, query the software version of the
multi-mode base station and specify the loading control rights by referring to the
upgrade guide. The MML command should be executed in the mode requiring the
loading control rights and with the parameter EFTIMMFLAG set to YES (becoming
effective immediately).
In the mode requiring the loading control rights, run the MML command SET
LOADCTRL to set the loading control rights in the multi-mode base station.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the configured working mode of an RF unit mismatches
the actual capability of the RF unit.
Parameters
RF Unit Working RF unit working mode (UO, GO, CO, WO, LO, TDLO, TDSO, GU, UL, GL, CL, TL,
Mode WL, GUL, CU)
RF Unit Mode RF unit mode capability (UO, GO, CO, WO, LO, TDLO, TDSO, GU, UL, GL, CL, TL,
Capability WL, GUL, CU)
System Actions
None
Possible Causes
Procedure
a. Run the MML command LST RRU/DSP RRUCHAINPHYTOPO to check whether the
working mode of the faulty RF unit is correct according to the site plan.
Y => The working mode is correct. Go to step 2.
N => The working mode is incorrect. Go to sub-step b.
b. Run the MML command MOD RRU to change the working mode of the faulty RF unit
according to the site plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Replace the RF unit. Ensure that the actual capability of the new RF unit is consistent
with the configured working mode.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
In multi-mode configuration, this alarm is reported when the cabinet/subrack number of two main control boards
in the same BBU is different, or when the cabinet/subrack number of a main control board of one mode is the
same as that of the other mode in a different BBU.
Parameters
Peer Cabinet No. Cabinet number of the faulty board in the peer working mode
Peer Subrack No. Subrack number of the faulty board in the peer working mode
Peer Slot No. Slot number of the faulty board in the peer working mode
Minor The BBU subrack and the boards in the BBU are displayed in disorder on the M2000.
In addition, the inventory information record is in disorder.
System Actions
None
Possible Causes
In a multi-mode base station, the cabinet/subrack number of a main control board of a mode is
incorrectly configured.
In a multi-mode base station, the installed position of a main control board of a mode is incorrect.
Procedure
1. Check the cabinet/subrack number of the BBU of each mode on the M2000.
a. Run the MML command DSP BRD to query the board configuration.
Check whether the cabinet/subrack number of the main control board of each mode is
correctly configured, according to the configuration plan.
Y => The cabinet/subrack number is correct. Go to step 2.
N => The cabinet/subrack number is incorrect. Go to sub-step b.
b. Run the MML command RMV BRD to delete the board that is incorrectly configured.
c. Run the MML command ADD BRD to add the board and set its cabinet/subrack/slot
number according to the configuration plan.
Ensure that the cabinet/subrack number of two main control boards in the same BBU is
the same, and the cabinet/subrack number of a main control board of one mode is
different from that of the other mode in a different BBU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Check whether the main control board of each mode is installed correctly, according to
the configuration plan.
Y => The main control board of each mode is installed correctly. Contact Huawei
b. Reinstall the main control board according to the configuration plan. Ensure that the
main control board of each mode is installed in the correct BBU.
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.
This alarm is reported when the optical module on an inter-BBU port is faulty.
Parameters
System Actions
None
Possible Causes
Procedure
a. Check for the correlated alarm of the faulty optical module on the M2000:
26200 Board Hardware Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
This alarm is reported when the optical module on an inter-BBU port is improperly configured or when the cable
for the inter-BBU electrical port is improperly connected. This alarm is only reported by a 2 U BBU.
Parameters
System Actions
None
Possible Causes
The cable for the optical module on an inter-BBU port or for the inter-BBU electrical port is not
installed or not connected securely.
The cable for the optical module on an inter-BBU port or for the inter-BBU electrical port is faulty.
Procedure
a. Run the MML command LST CTRLLNK or LST BBPLNK to query the configurations of
inter-BBU ports. Check whether the configurations are correct according to the onsite
plan.
Y=> The configurations are correct. Go to step 2.
N=> The configurations are incorrect, and extra inter-BBU ports are configured. Go to
step 2.
b. Run the MML command RMV CTRLLNK or RMV BBPLNK to remove the extra
inter-BBU ports.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check cable connections for the optical module or electrical port onsite.
a. Check whether the cable for the optical module or electrical port is installed on the BBU
side.
Y => The cable is installed. Go to substep c.
Y => The cable is not installed. Go to substep b.
b. Install an optical module or install the cable for the electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
c. Remove and then insert the optical module or remove and then insert the electrical
cable, and check that the optical module is connected properly.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
This alarm is reported when the optical link (at the physical layer) between BBU ports fails to receive optical
signals. This alarm is only reported by a 2U BBU.
Parameters
Parameter
Name Parameter Description
Specific Problem Specific Problem of the alarm(Receive No Signal, Receive Power Too High, Receive Power
Too Low)
Minor If the BBUs are interconnected by UCIU+UCIU/UMPT, the bit error rate (BER) of the
control information, clock information, and transmission information exchanged
between BBUs increases. As a result, the service quality of the lower-level BBU
deteriorates.
If the BBUs are interconnected by WBBPf+WBBPf, the bit error rate (BER) of the
baseband data and signaling exchanged between BBUs increase, affecting service
quality.
System Actions
None
Possible Causes
The optical module on an inter-BBU port is faulty or not installed properly, or the cable connection on
the optical module is not ready.
The optical connector of an inter-BBU port is dirty.
The optical modules on both ends of an inter-BBU port do not match, in terms of type (single-mode
or multi-mode) and rate.
The optical module on an inter-BBU port does not match that supported by the board, in terms of
type (single-mode or multi-mode) and rate.
The optical module on an inter-BBU port does not match the connected fiber optic cable, in terms of
type (single-mode or multi-mode) and rate.
The UCIU is faulty.
The optical module on an inter-BBU port does not match the connected fiber optic cable, in terms of
type (single-mode or multi-mode) and rate.
Procedure
a. Check for the correlated alarm of the inter-BBU port and the port of the peer board on
the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26313 Inter-BBU Optical Module Transmit Failure
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
2. Check the optical module and fiber optic cable of an inter-BBU port onsite.
a. Remove and then insert the optical module and optical connector on the inter-BBU port
b. Remove the optical connector from the optical module, and clean the connector using
alcohol or cigarette filter tip. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical modules on both ends of the inter-BBU port match, in terms
of type (single-mode or multi-mode) and rate (4.9152 Gbit/s). 1310nm is labeled on a
single-mode optical module, and 850nm is labeled on a multi-mode optical module.
Y => The optical modules on both ends of the inter-BBU port match. Go to sub-step e.
N => The optical modules on both ends of the inter-BBU port do not match. Go to
sub-step d.
d. Based on the type of one end of the inter-BBU port, select an optical module that
matches the type. Replace the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Run the MML command DSP SFP to query the transmission mode of the optical
module. A blue fiber optic cable is used for the single-mode optical module, and an
orange fiber optic cable is used for the multi-mode optical module. Check whether the
optical module matches the connected fiber optic cable, in terms of type (single-mode
or multi-mode) and rate.
Y => The optical module matches the connected fiber optic cable. Go to step 3.
N => The optical module does not match the connected fiber optic cable. Go to
sub-step f.
a. Check the running status of the peer board onsite by observing the RUN indicator on the
board. Check whether the RUN indicator blinks normally (on for 1s and off for 1s).
Y => The RUN indicator blinks normally. Go to step 4.
N => The RUN indicator does not blink normally. Go to sub-step b.
b. Rower on the peer board again and wait until the RUN indicator blinks normally (on for
1s and off for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Verify that the fiber optic cable between the BBUs is not bent or deformed.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to substep b.
5. Replace the optical module for the BBU interconnection on the peer board onsite.
This alarm is reported when the optical module on an inter-BBU port fails to transmit data. This alarm is only
reported by a 2U BBU.
Parameters
Parameter
Name Parameter Description
Specific Problem Specific Problem of the alarm(Optical Module Performance Degraded, Optical Module
Transmit Error)
Minor Services are not affected temporarily. If the problem remains for a long time, the
alarm severity is changed to major.
System Actions
None
Possible Causes
Procedure
a. Remove and then insert the optical module and optical connector of the inter-BBU port
on the BBU side.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
This alarm is reported when an inter-BBU port fails to transmit or receive data. This alarm is only reported by a
2U BBU.
Parameters
Parameter
Parameter Description
Name
Specific Specific Problem of the alarm(CPRI Interface Initialization Failure, CPRI Interface Transmit
Problem Error, CPRI Interface Reception Error)
System Actions
None
Possible Causes
The peer optical connector of an inter-BBU port or the optical module is not inserted properly, or the
fiber optic cable fails to be connected. The electrical cable for the peer inter-BBU port is not securely
connected, or the electrical cable is faulty.
The peer board of an inter-BBU port does not work properly, or the hardware of the board is faulty.
Procedure
a. Check for the correlated alarm of the faulty inter-BBU port on the M2000:
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26240 BBU Topology and Configuration Mismatch
26315 Inter-BBU Port Connection Error
a. Run the RST BRD command to reset the faulty board for BBU interconnection, and wait
until the board is restarted.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to substep b.
b. Run the RST BRD command to reset the peer board and wait until the board is
restarted.
Check 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.
a. Replace the peer board of the faulty port. Replace the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
An inter-BBU interface on the UCIU can be an M port or an S port. Inter-BBU interfaces of the same type cannot
be connected, and a ring network is not allowed if inter-BBU interfaces are connected. This alarm is reported
when inter-BBU interfaces of the same type are connected, or a ring network is set up in the case of an
inter-BBU connection.
Parameters
Fault Type Fault Type (S Port Connected to S Port, M Port Connected to M Port, Ring Topology)
Major BBUs cannot share control information, clock information, and transmission
information. Services may be interrupted.
System Actions
None
Possible Causes
Inter-BBU interfaces of the same type are connected, or a ring network is set up in the case of an inter-BBU
connection.
Procedure
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "M Port Connected to M Port" or "S Port Connected to S Port",
go to step 2.
If "Specific Problem" is "Ring Topology", go to step 3.
2. Check the UCIU for the connection of inter-BBU ports of the same type on site.
a. Based on the alarm parameters, locate the UCIU port and the connected optical fiber.
Check whether the connection of inter-BBU ports of the same type exists on the UCIU
port.
Y => The connection of inter-BBU ports of the same type exists on the UCIU port. Go
to sub-step b.
N => The connection of inter-BBU ports of the same type does not exist on the UCIU
port. Contact Huawei Customer Service Center.
b. Reconnect the inter-BBU optical fibers based on the engineering plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Based on the alarm parameters, locate the UCIU port and the connected optical fiber.
Check whether a ring topology of inter-BBU connection exists on the UCIU port.
Y => A ring topology of inter-BBU connection exists on the UCIU port. Go to sub-step
b.
N => A ring topology of inter-BBU connection does not exist on the UCIU port. Contact
Huawei Customer Service Center.
This alarm is reported when the optical module on the port of the RF unit connecting to the peer device (upper-
or lower-level RF unit or the BBU) is not in position or when the cable connection on the optical module or
electrical port is not ready.
Parameters
Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted.
In ring topology, the reliability of the link decreases. In this case, the active link of
lower-level RF units is switched over to the standby link. In the case of a hot ring, the
ongoing services are not affected. In the case of a cold ring, the ongoing services
are disrupted for about ten seconds.
System Actions
In ring topology, the active link of lower-level RF units is switched over to the standby link.
Possible Causes
The optical module on the port of the RF unit connecting to the peer device (upper- or lower-level RF
unit or the BBU) is not in position, or the cable connection on the optical module or electrical port is
not ready.
The optical module on the port of the RF unit connecting to the peer device (upper- or lower-level RF
unit or the BBU) is faulty, or the cable connected to the optical module or electrical port is faulty.
The connecting piece on the port of the RF unit connecting to the peer device (upper- or lower-level
RF unit or the BBU) is faulty.
Procedure
a. Run the MML command LST RRUCHAIN to query the link networking of the faulty RF
unit. Check whether a redundant lower-level RF unit is configured according to the site
plan.
Y => A redundant lower-level RF unit is configured. Go to sub-step b.
N => There is no redundant lower-level RF unit. Go to step 2.
b. Run the MML command RMV RRU to remove the redundant lower-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the installation of the optical module, or check the cable connection on the optical module or
electrical port of the RF unit on site.
a. Check whether the optical module is installed, or whether the cable is connected to the
optical module or electrical port on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the optical/electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
c. Reseat the optical module or the cable connected to the optical/electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
d. Replace the optical module, or replace the cable on the electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
This alarm is reported when the optical module installed on the port of the RF unit connecting to the peer device
(upper- or lower-level RF unit or the BBU) is not supported by the RF unit.
Parameters
Valid Optical Module Valid optical module type (1.25Gbps, 2.5Gbps, 3.07Gbps, 4.9Gbps, 6.14Gbps,
Type 9.8Gbps, 3.84Gbps)
Installed Optical Module Type of the installed optical module (1.25Gbps, 2.5Gbps, 3.07Gbps, 4.9Gbps,
Type 6.14Gbps, 9.8Gbps, 3.84Gbps)
Major The port of the RF unit connecting to the peer device (upper- or lower-level RF unit
or the BBU) does not work normally. The services carried on the RF unit are
disrupted.
System Actions
None
Possible Causes
The type of the optical module installed on an RF unit is not supported by the RF unit. For example, an RF unit
supports only an optical module of 2.5 Gbit/s, but an optical module of 1.25 Gbit/s is installed on the RF unit.
Procedure
a. Replace the optical module of the RF unit on site. Ensure that the installed optical
module is supported by the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the optical transmission on the optical link (at the physical layer) is abnormal
between the RF unit and the peer device (upper-level/lower-level RF unit or BBU).
Parameters
Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted.
In ring topology, the reliability of the link of RF units decreases. In this case, the
active link of lower-level RF units is switched over to the standby link. In the case of
a hot ring, the ongoing services are not affected. In the case of a cold ring, the
ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RF unit automatically switches to a normal port if its uplink port is faulty.
Possible Causes
The optical module or connector of the current-level RF unit is improperly installed, or the optical
module is faulty.
The optical module or connector of the peer device (upper-level/lower-level RF unit or BBU) is
improperly installed, or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RF unit or BBU) is dirty.
The peer device is faulty.
The optical link between the current-level RF unit and the peer device (upper-level/lower-level RF unit
or BBU) is faulty.
Procedure
a. Check for the correlated alarm on the faulty port of the RF unit on the M2000:
26501 RF Unit Optical Module or Electrical Port Not Ready
26502 RF Unit Optical Module Type Mismatch
26507 RF Unit Optical Module Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. On the current-level RF unit side, remove and reinstall the optical module and connector
on the faulty port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Connect the TX and RX terminals of the optical fiber at the current-level RF unit on site.
a. Remove the optical fiber from the optical module of the RF unit. Then, connect the TX
and RX terminals of the optical fiber by using a flange.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step c.
N => The alarm is not cleared. Go to sub-step b.
b. Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the RF unit. Then, Go to step 4.
d. Power off the RF unit on site and then power it on. Wait until the RF unit startup is
complete (the RUN LED blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
a. On the peer device side, check whether the RUN LED on the peer device blinks (ON for
1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). The peer device is running
normally. Go to step 5.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). The peer device is
running improperly. Go to sub-step b.
b. Reset the peer device on site. Wait until the RUN LED blinks (ON for 1s and OFF for
1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. Remove and reinstall the optical module and connector on the port of the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
6. Connect the TX and RX ports of the optical module at the peer device.
a. Remove the optical fiber from the optical module of the peer device. Then, connect the
TX and RX ports of the optical module by using an optical fiber for loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step b.
N => The alarm is not cleared. Go to sub-step c.
b. Disconnect the TX and RX ports of the optical module, and restore the optical
connection of the peer device. Then, Go to step 7.
a. Check the optical connections between the current-level RF unit and the peer device.
Replace the faulty optical fibers to troubleshoot the improper optical connections, such
as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
This alarm is reported when the data transmission on the link (at the link layer) is abnormal between the RF unit
and the peer device (upper-level/lower-level RF unit or BBU).
Parameters
Parameter
Name Parameter Description
Specific Problem Specific Problem of the alarm(CPRI Interface Transmit Error, CPRI Interface Reception
Error)
Major In chain topology, the link of lower-level RF units is disconnected. The services
carried on lower-level RF units are disrupted.
In ring topology, the reliability of the link of RF units decreases. In this case, the
active link of lower-level RF units is switched over to the standby link. In the case of
a hot ring, the ongoing services are not affected. In the case of a cold ring, the
System Actions
In ring topology, the current-level RF unit automatically switches to a normal port if its uplink port is faulty.
Possible Causes
If the optical transmission is used, the optical module or connector of the RF unit or peer device may
be improperly installed, or the optical link is faulty.
If the electrical transmission is used, the cable connector of the RF unit or peer device may be
improperly installed, or the cable is faulty.
Procedure
a. Check for the correlated alarm on the faulty port of the RF unit on the M2000:
26501 RF Unit Optical Module or Electrical Port Not Ready
26503 RF Unit Optical Module Transmit/Receive Fault
26507 RF Unit Optical Module Fault
26502 RF Unit Optical Module Type Mismatch
26310 Inter-BBU Optical Module Fault
26311 Inter-BBU Optical Module Not in Position
26312 Inter-BBU Optical Module Receive Failure
26313 Inter-BBU Optical Module Transmit Failure
26314 Inter-BBU Port Failure
26315 Inter-BBU Port Connection Error
26240 BBU Topology and Configuration Mismatch
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. Locate the cause of the alarm based on the alarm detailed information.
If "Specific Problem" is "CPRI Interface Transmit Error", go to step 3.
If "Specific Problem" is "CPRI Interface Reception Error", go to step 4.
a. Check the optical connections between the BBU and the peer end. Troubleshoot the
improper optical connections, such as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
4. Check the cable connections on the faulty port of the RF unit on site.
a. Check the cable connections on the optical or electrical port of the current-level RF unit
on site.
If the electrical transmission is used, Go to sub-step b.
If the optical transmission is used, Go to sub-step d.
b. Reseat the cable on the electrical port of the current-level RF unit and the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
d. Remove the connector from the optical module of the current-level RF unit. Clean the
connector by using absolute alcohol or a clean cigarette filter. Then, reinstall the
connector to the optical module of the current-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Check the optical connections between the current-level RF unit and the peer end.
Replace the faulty optical fibers to troubleshoot the improper optical connections, such
as fiber bending, deformation, damage, or loose optical connector/module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step f.
f. Remove the connector from the optical module of the lower-level RF unit. Clean the
connector by using absolute alcohol or a clean cigarette filter. Then, reinstall the
connector to the optical module of the lower-level RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Power cycle the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
This alarm is reported when the TX/RX performance of the optical module of the RF unit deteriorates.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Optical Module Performance Degraded, Reception Power Too
Problem High, Reception Power Too Low)
Major When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the link of the RF unit may decrease significantly, or the
Minor When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the link of the RF unit may decrease to some extent.
System Actions
None
Possible Causes
The optical module or connector of the current-level RF unit is improperly installed. Or the optical
module is worn-out.
The optical module on the port of the current-level RF unit is not supported by the current-level RF
unit, in terms of type (single-mode or multi-mode) and rate.
The optical module or connector of the peer device (upper-level/lower-level RF unit or BBU) is
improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RF unit or BBU) is dirty.
The optical module on the port of the peer device (upper-level/lower-level RF unit or BBU) is not
supported by the peer device, in terms of type (single-mode or multi-mode) and rate.
The optical fibers between the current-level RF unit and the peer device (upper-level/lower-level RF
unit or BBU) are bent, deformed, or worn-out. Or the length of optical fibers is excessive (longer than
40 km), which leads to a high attenuation of optical signals.
Procedure
a. Remove and reinstall the optical module and connector on the port of the current-level
RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Examine the label on the optical module to check whether the optical module on the port
is supported by the current-level RF unit, in terms of type (single-mode or multi-mode)
and rate (1.25 Gbit/s, 2.5 Gbit/s or other rate).
Y => The optical module is supported by the RF unit. Go to sub-step e.
N => The optical module is not supported by the RF unit. Go to sub-step d.
a. Remove and reinstall the optical module and connector on the port of the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Examine the label on the optical module to check whether the optical module on the port
is supported by the peer device, in terms of type (single-mode or multi-mode) and rate
(1.25 Gbit/s, 2.5 Gbit/s or other rate).
Y => The optical module is supported by the peer device. Go to sub-step e.
N => The optical module is not supported by the peer device. Go to sub-step d.
a. Check the optical connections between the current-level RF unit and the peer device.
Replace the faulty optical fibers to troubleshoot the improper optical connections, such
as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Check the length of the optical link between the current-level RF unit and the peer
device. If the length is excessive (longer than 40 km), add an optical trunk or use
another cascaded RF unit as the optical trunk.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Replace the optical fibers between the current-level RF unit and the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Description
This alarm is reported when the optical module or electrical module on the port of the RF unit connecting to the
peer device (upper- or lower-level RF unit or the BBU) is faulty.
Parameters
Warning The information about the optical module or electrical module cannot be obtained.
System Actions
None
Possible Causes
Procedure
a. Run the MML command DSP BTSBRD, and query the RUNPARA of the faulty RF
board, to check using optical module or electrical module.
Optical module, go to step 3;
Electrical module, go to step 5;
a. Remove and reinstall the faulty electrical module and cable on site.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
This alarm is reported when the difference between the actual gain and the standard gain on the TX channel of
the RF unit is greater than 2.5 dB.
Parameters
Minor When the gain on the TX channel is extremely high, the downlink coverage of the cell
is excessive. In this case, the interference caused by cross coverage occurs.
When the gain on the TX channel is extremely low, coverage holes exist in the
downlink coverage of the cell. In serious cases, the ongoing services carried on the
System Actions
None
Possible Causes
Procedure
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the RTWP/RSSI on the RX channel of the RF unit is lower than -114 dBm. RTWP is
shortened from received total wideband power, consisting of signal power and noise power. RSSI is shortened
from received signal strength indicator.
Parameters
Minor The receive sensitivity of the RF unit decreases. The demodulation performance of
the cell deteriorates. The uplink coverage shrinks.
If the RTWP/RSSI on all RX channels of the cell is too low, the ongoing services of
the cell may be disrupted.
System Actions
None
Possible Causes
The feeder installation is improper. For example, the feeder connector is loose, soaked or damaged,
or the feeder is deformed.
The RX channel of the RF unit is faulty. For example, the low-noise amplifier, frequency mixer, analog
to digital converter (ADC), or field programmable gate array (FPGA) is faulty.
Procedure
a. Check for the correlated alarm on the faulty port of the RF unit on the M2000:
26532 RF Unit Hardware Fault
26530 RF Unit ALD Current Out of Range
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
c. Run the MML command MOD RXBRANCH to set the attenuation on the main RX
channel and diversity RX channel of the RF unit to 0. Then, wait for ten minutes.
a. Reconnect the jumper to the antenna port of the RF unit. Then, wait for 10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s). Then, wait for 10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
This alarm is reported when the difference between the RTWP/RSSI of the main RX channel and the
RTWP/RSSI of the diversity RX channel exceeds 10 dB. RTWP is shortened from received total wideband
power, consisting of signal power and noise power. RSSI is shortened from received signal strength indicator.
Parameters
Minor The receive sensitivity of the RF unit decreases. The demodulation performance of
the cell deteriorates. The uplink coverage shrinks.
System Actions
None
Possible Causes
External interferences exist only on the main or diversity antenna of the RF unit.
The feeder connected to the RF unit is faulty, which results in a high passive intermodulation power
of the main or diversity antenna.
The feeder installation is improper. For example, the feeder connector is loose, soaked or damaged,
or the feeder is deformed.
Procedure
3. On the LMT, check for external interference on the main and diversity antennas.
a. On the LMT, start the uplink frequency scanning . Check whether the external
interferences exist (by distinct bulges near the uplink frequencies in the scanned
diagram).
Y => The external interference exists. Go to sub-step b.
N => A single cell uses a 4R or higher configuration and there is not interference. Go to
step 4.
N => A single cell uses a 2R or lower configuration and there is not interference. Go to
step 5.
c.
Wait for 40 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. On the LMT, start the uplink frequency scanning. Monitor the results for 30 minutes to
locate the faulty channel (whose RTWP or RSSI is lower than that of other channels).
Go to step 5.
a. Reconnect the jumper to the antenna port of the RF unit. Then, wait for 30 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s). Then, wait for 30 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
Description
This alarm is reported when the operating current of the Power Amplifier (PA) on a TX channel of the RF unit is
beyond the normal range.
Parameters
Major The RF unit automatically switches off the TX channel. The ongoing services carried
on the TX channel are disrupted.
System Actions
The RF unit automatically switches off the faulty TX channel. The system waits for one minute and then switches
on the TX channel. After five minutes, the system checks the alarm. If the alarm persists, the RF unit
automatically switches off the TX channel again. If the alarm persists after three switching-on attempts, the
system alters to switch on the TX channel every 30 minutes, until the alarm is cleared or the RF unit is reset by
the user.
Possible Causes
Procedure
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the operating temperature of an RF unit is out of the normal range.
The rated operating temperature range is a hardware specification of RF units. This range varies depending on
the type of the RF unit.
Parameters
Major The RF unit automatically switches off the TX channel to prevent the hardware from
being burned out because of high temperature. The ongoing services carried on the
RF unit are disrupted.
Minor The reliability of internal components of the RF unit may decrease when operating in
a high-temperature environment for a long period of time. Meanwhile, the quality of
services carried on the RF unit decreases.
System Actions
When the temperature of an RF unit exceeds the major alarm threshold, the RF unit automatically switches off
the TX channel. When the temperature of the RF unit drops to a certain value, the RF unit switches on the TX
channel again. To protect the power amplifier (PA) from being damaged by frequent switching-on and -off, this
alarm cannot be cleared after the TX channel has been switched off and on for three times. Under that
circumstance, users need to solve the temperature problem onsite and then manually reset the RF unit. When
the temperature of an RF unit is between the minor alarm threshold and the major alarm threshold, the BBU
limits the user access to a cell through the RF unit to prevent further power consumption and temperature
increase.
Possible Causes
The ambient temperature of the RF unit is extremely high, or the heat dissipation malfunctions.
The hardware of the RF unit is faulty.
Procedure
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Check the ambient temperature and heat dissipation of the RF unit. Check whether the
ambient temperature is normal.
Y => The ambient temperature is normal. Go to step 4.
N => The ambient temperature is extremely high. Go to sub-step b.
b. Take proper measures to reduce the ambient temperature of the RF unit. Then, wait for
10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
This alarm is reported when the baseband input power from the BBU to the RF unit is beyond the normal power
range of the RF unit.
Parameters
Major The RF unit automatically performs the amplitude limitation on input power. In this
case, the quality of services carried on the RF unit may decrease, and call drops
may occur on edge of coverage of the RF unit.
System Actions
Possible Causes
When the input power of the RF unit approaches or reaches the maximum input power, the user
starts the stimulated downlink load.
The user access threshold is improper, which leads to the actual number of users to exceed the
allowed capacity of the RF unit.
Procedure
a. Run the MML command DSP DLSIM to check whether the stimulated downlink load is
started on the RF unit.
Y => The stimulated downlink load is started. Go to sub-step b.
N => The stimulated downlink load is not started. Go to step 2.
b. Run the MML command STP DLSIM to stop the stimulated downlink load.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. If the user access threshold exists in the base station or RNC, check whether the
threshold is proper according to the network plan.
Y => The threshold is proper. Go to step 3.
N => The threshold is improper. Go to sub-step b.
b. Modify the user access threshold in the base station or RNC according to the network
plan.
Check whether the alarm is cleared.
3. Reset the board in the BBU connected to the RF unit on the M2000.
a. Run the MML command RST BRDPWROFF to reset the board through power-off in the
BBU that is connected to the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
The voltage standing wave ratio (VSWR) measures the signal power that the load actually receives from the
transmission line. This alarm is reported when the VSWR at the antenna port of the TX channel of an RF unit is
higher than the preset threshold.
Parameters
VSWR Alarm Threshold (0.1) VSWR alarm threshold configured by the user
Major The return loss at the antenna port is excessive. When the detected VSWR exceeds
the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When "VSWR alarm
post-processing switch" is set to "ON", the TX channel of the RF unit is switched off
and the alarm cannot be automatically cleared, and the ongoing services carried on
the TX channel are disrupted..When "VSWR alarm post-processing switch" is set to
"OFF", the power of the RF unit is automatically decreased (by 3 dB by default) to
Minor The return loss at the antenna port is relatively large. In this case, the output power
of the RF unit decreases and the cell coverage shrinks.
System Actions
When the detected VSWR exceeds the minor alarm threshold, the system does not handle the alarm. The alarm
is automatically cleared when the detected VSWR becomes smaller than the alarm threshold. When the
detected VSWR exceeds the major alarm threshold, the system determines whether to switch off the TX
channel of the RF unit based on the actual configurations. When "VSWR alarm post-processing switch" is set to
"ON", the TX channel of the RF unit is switched off and the alarm cannot be automatically cleared.When "VSWR
alarm post-processing switch" is set to "OFF", the power of the RF unit is automatically decreased (by 3 dB by
default) to avoid hardware damage. Once the detected VSWR becomes smaller than the alarm threshold, the
alarm is automatically cleared.
Possible Causes
The preset VSWR threshold is very low. It is recommended that the VSWR alarm threshold not be
used as the VSWR acceptance threshold.
The VSWR threshold is set to an excessively low value for the other mode of the multi-mode RF
units.
The installation of jumpers does not comply with the plan.
The feeder connector on the antenna port does not meet the requirements, is loose or waterlogged,
or has foreign objects.
The feeder connected to the antenna port of the RF unit is bent, deformed, or damaged.
The frequency bands supported by the RF unit do not match the frequency bands supported by the
components of the antenna system. The components of the antenna system include antennas,
feeders, jumpers, combiner-dividers, filters, and tower-mounted amplifiers (TMAs).
Procedure
a. Run the MML command LST RRU to query the VSWR threshold of the RF unit. If the
alarm severity is major, query the value of VSWR alarm post-processing threshold. If
the alarm severity is minor, query the value of VSWR alarm threshold.Check whether
the VSWR threshold is proper according to the configuration plan.
Y => The threshold is proper. Go to step 2.
N => The threshold is improper. Go to sub-step b.
b. If the RF unit works in multi-mode, run the MML command LST RRU to query the
VSWR threshold configured for the other mode. Check whether the VSWR thresholds
configured for the two modes are consistent.
Y => The VSWR thresholds configured for the two modes are consistent. Go to step 2.
N => The VSWR thresholds configured for the two modes are inconsistent. Go to
sub-step c.
c. Run the MML command MOD RRU to modify the VSWR threshold of the RF unit. If the
alarm severity is major, set the value of VSWR alarm post-processing threshold. If the
2. Check the frequency bands supported by the RF unit and the components of the antenna system
onsite.
a. Check whether the frequency bands supported by the RF unit are consistent with the
frequency bands supported by the components of the antenna system based on the
network planning data.
Y => The frequency bands are consistent. Go to step 3.
Y => The frequency bands are inconsistent. Go to sub-step b.
b. Replace the components of the antenna system with the components specified in the
network planning data according to the instructions in the antenna system installation
guide. If the severity of the alarm is major and the TX channel of the RF unit is switched
off automatically, power off and then power on the RF unit onsite, and wait until the RF
unit is restarted.
Wait for 10 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Check whether the installation of the RF unit and jumpers is consistent with the plan.
Y => The installation of jumpers is correct. Go to step 4.
N => The installation of jumpers is incorrect. Go to sub-step b.
b. Reinstall the jumpers for the RF unit according to the plan. If the alarm severity is major
and the TX channel of the RF unit is switched off automatically, power off and then
power on the RF unit onsite, and wait until the RF unit is restarted.
Wait for 10 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Reconnect the jumper to the antenna port of the RF unit. If the detected VSWR
exceeds the major alarm threshold and the TX channel of the RF unit is switched off,
power off and then power on the RF unit onsite, and wait until the RF unit is restarted.
Wait for 10 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. Check the installation of feeders for the RF unit. If the alarm severity is major and the
TX channel of the RF unit is switched off, power off and then power on the RF unit
onsite, and wait until the RF unit is restarted.
Wait for 10 minutes. Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
This alarm is reported when the current supplied by the RF unit to the antenna device through feeder or
multi-wire cable is beyond the normal range.
Parameters
Minor The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases.
Warning The antenna device can work normally, but some secondary functions of the antenna
device fail.
System Actions
In the case of overcurrent, overcurrent protection, and open-circuit protection occurs on the antenna
device, the RF unit automatically switches off the power supply to the antenna device. Meanwhile,
the attenuation on the RX channel is set to 0 to minimize the impact of TMA fault on the receive
sensitivity of the corresponding RX channel.
In the case of overcurrent and overcurrent protection occurs on the antenna device, the RF unit
switches off the power supply to the antenna device and then attempts to switch on the power supply
every other minute. If the fault persists after three attempts, the RF unit does not retry any more.
Five minutes after open-circuit protection occurs and the the power supply to the antenna device is
switched off, the RF unit begins the attempt to switch on the power supply to the antenna device
every other minute. If the fault persists after 26 attempts, the RF unit does not retry any more.
Possible Causes
Procedure
1. Check the configuration of the ALD power supply switch on the M2000.
a. Run the MML command DSP ANTENNAPORT/DSP RETPORT to query the status of
the ALD power supply switch of the RF unit. Check whether the status is correct
according to the configuration plan.
Y => The status of the ALD power supply switch is correct. Go to step 2.
N => The status of the ALD power supply switch is incorrect. Go to sub-step b.
b. Run the MML command MOD ANTENNAPORT/MOD RETPORT to modify the ALD
power supply switch configuration according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the preset ALD current threshold of the RF unit on the M2000.
b. Run the MML command MOD ANTENNAPORT/MOD RETPORT to modify the ALD
current threshold of the RF unit according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
5. Check the installation of jumper between the feeder and the antenna device on site.
a. Check the installation of jumper between the feeder and the antenna device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
An RF unit supports two ALD port types, which are coaxial port (ANT port) and multi-wire port (RET port). This
alarm is reported when the configured ALD switch type does not match the actual type of the ALD port on the
RF unit.
Parameters
Hardware Capability Hardware capability (Switch Type Not Supported, Switch Type Supported)
Configured Switch Type Type of the configured switch (ANT Switch, RET Switch)
Installed Switch Type Installed switch type (RET Switch, ANT Switch)
Minor The antenna device cannot work normally. In the case of an RET antenna, the
antenna tilt cannot be regulated. In the case of a TMA, the receive sensitivity
decreases.
System Actions
None
Possible Causes
The coaxial ALD switch is configured, but actually the multi-wire cable is connected to the multi-wire
port.
The multi-wire ALD switch is configured, but actually the multi-wire cable is not connected to the
multi-wire port.
Procedure
a. Reconnect the cable to the ALD port of the RF unit on site according to the
configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Major The RF unit may work improperly. The ongoing services carried on the RF unit may
be disrupted.
Minor Some functions of the RF unit may fail and the quality of services carried on the RF
unit may decrease.
System Actions
When a critical component of an RF unit is faulty, the system automatically disables the faulty RX channel or TX
channel associated with the RF unit.
Possible Causes
Procedure
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the software program of the RF unit runs improperly, such as suspension.
Parameters
Major The RF unit may work improperly. The RF unit will be automatically reset. The
ongoing services carried on the RF unit are disrupted during reset.
System Actions
Possible Causes
Procedure
This alarm is reported when the CPU usage of the RF unit is beyond the operating threshold.
Parameters
Minor Some functions of the RF unit may fail, such as channel gain correction. In this case,
the quality of services carried on the RF unit decreases. Long-term CPU overload
may result in delayed response or timeout of maintenance tasks of the RF unit.
System Actions
None
Possible Causes
The user runs too many configuration or maintenance commands frequently on the RF unit.
The user starts too many test or measurement tasks on the RF unit.
Procedure
1. Stop the configuration and maintenance tasks on the RF unit on the M2000.
a. Stop the configuration and maintenance tasks on the RF unit. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Stop all the test, tracing, and statistical tasks on the RF unit on the M2000
a. Stop all the site test, tracing, and statistical tasks on the RF unit. Then, wait for 15
minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the frequencies configured for different modes conflict in multi-mode configuration.
Parameters
Mode of Original Mode of the original parameter (Reserved, TD-SCDMA, LTE-TDD, LTE-FDD,
Parameter WIMAX, CDMA, GSM, UMTS, Unknown)
Mode of New Mode of the new parameter (Reserved, TD-SCDMA, LTE-TDD, LTE-FDD, WIMAX,
Parameter CDMA, GSM, UMTS, Unknown)
Minor This alarm is reported when the frequencies configured for different modes conflict in
multi-mode configuration.
System Actions
None
Possible Causes
This alarm is reported when the frequencies configured for different modes conflict in multi-mode configuration.
Procedure
a. Run the MML command LST LOCELL to check the frequency configuration of each
mode in multi-mode configuration of the RF unit. Locate the conflicting frequencies.
b. Run the MML command MOD LOCELL to modify the frequency configuration of each
mode of the RF unit according to the network plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the interface clock of the RF unit connecting to the peer device (upper- or
lower-level RF unit or the BBU) is faulty, or the working clock of an internal component is faulty.
Parameters
Major Some components in the RF unit may work improperly. In certain cases, the ongoing
services carried on the RF unit may be disrupted.
System Actions
When the working clock of a critical component in the RF unit is faulty, the system automatically disables the
faulty RX channel or TX channel.
Possible Causes
The uplink interface of the RF unit is faulty, resulting in the faulty clock that is extracted at the
interface.
Procedure
a. Check for the correlated alarm on the port of the RF unit connecting to the peer device
(upper- or lower-level RF unit or the BBU) on the M2000.
26504 RF Unit CPRI Interface Error
26234 BBU CPRI Interface Error
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. Run the MML command RST BRDPWROFF on the M2000 to reset the RF unit through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the AC power supply to the RF unit (with the AC-DC converter) fails.
Parameters
System Actions
None
Possible Causes
Procedure
a. Check the AC power equipment of the RF unit on site. Take proper measures to
restore the AC power.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the maintenance link between the RF unit and the ALD (RET antenna, TMA, or
SASU) malfunctions.
Parameters
Major If the maintenance link of the RET antenna is broken, the antenna tilt cannot be
regulated. In this case, the state of the RET antenna cannot be monitored.
If the maintenance link of the TMA is broken, the TMA gain cannot be configured. In
this case, the state of the TMA cannot be monitored.
The maintenance link for the SASU is disconnected. Therefore, the gain of the SASU
cannot be set and the SASU status cannot be monitored.
System Actions
None
Possible Causes
The ALD current of the RF unit is out of range, or the configured ALD switch does not match the
actual type of the ALD port on the RF unit.
The ALD switch of the RF unit is not turned on.
The data configuration of the antenna is incorrect. For example, the vendor code, equipment serial
number, or antenna type is not configured or incorrect; the control port is incorrectly configured.
There are feeder problems, such as water damage, connector fault, or bent cable.
Procedure
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch. Then, turn on the ALD switch.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Run the MML command LST RET/LST TMA/LST SASU to check whether the antenna
device configuration, such as vendor code , equipment serial number, antenna type, and
control port is consistent with the actual situation.
6. Check the installation of jumper between the feeder and the antenna device on site.
a. Check the installation of jumper between the feeder and the antenna device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
a. Power cycle the RF unit on site. Wait until the RF unit startup is complete (the RUN LED
blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 8.
This alarm is reported when the maintenance link between the RF unit and the backup power device fails.
Parameters
Major The system cannot monitor the input power, battery, or ambient temperature. The
backup power device cannot be controlled.
System Actions
None
Possible Causes
The address settings of the DIP switch on the backup power device are incorrect.
The connection between the RF unit and the backup power device is not ready, or the cables are
faulty.
Procedure
a. Run the MML command LST PMU(PMU)/LST TCU(TCU) to query the configuration of
the backup power device on the RF unit. Check whether the configuration of the backup
power device is required according to the site plan.
Y => The configuration is required. Go to step 2.
N => The configuration is not required. Go to sub-step b.
b. Run the MML command RMV PMU(PMU)/RMV TCU(TCU) to remove the unnecessary
backup power device of the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Check whether the RUN LED on the backup power device blinks (ON for 1s and OFF
for 1s) on site.
Y => The RUN LED blinks (ON for 1s and OFF for 1s). Go to step 3.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). Go to sub-step b.
b. Power cycle the backup power device. Wait until the RUN LED blinks (ON for 1s and
OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Check the address settings of the DIP switch on the backup power device on site.
a. Check whether the address settings of the DIP switch on the backup power device are
correct according to the configuration plan. For details, see the installation guide.
Y => The address settings are correct. Go to step 4.
N => The address settings are incorrect. Go to sub-step b.
b. Modify the address settings of the DIP switch on the backup power device according to
the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Reconnect the cables between the RF unit and the backup power device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the cables between the RF unit and the backup power device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
5. Reset the monitoring board for the backup power device on site.
a. Reseat the monitoring board for the backup power device. Wait until the RUN LED on
the monitoring board blinks (ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
6. Replace the monitoring board for the backup power device on site.
a. Remove the monitoring board for the backup power device. Install a new monitoring
board. Wait until the RUN LED on the monitoring board blinks (ON for 1s and OFF for
1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the maintenance link between the RF unit and the general serial port device
malfunctions.
Parameters
Major The system cannot monitor or control the general serial port device that is installed
by the user.
System Actions
None
Possible Causes
The connection between the RF unit and the serial port device is not ready, or the cables are faulty.
Procedure
a. Run the MML command LST PMU(PMU)/LST TCU(TCU) to query the configuration of
the serial port device on the RF unit. Check whether the configuration of the serial port
device is required according to the site plan.
a. Check whether the RUN LED on the serial port device blinks (ON for 1s and OFF for
1s) on site.
Y => The RUN LED blinks (ON for 1s and OFF for 1s). Go to step 3.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). Go to sub-step b.
b. Power cycle the serial port device. Wait until the RUN LED blinks (ON for 1s and OFF
for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. According to the base station installation guide, check the address settings of the DIP switch on the
serial port device on site.
a. Check whether the address settings of the DIP switch on the serial port device are
correct according to the configuration plan.
Y => The settings are correct. Go to step 4.
N => The settings are incorrect. Go to sub-step b.
b. Modify the address settings of the DIP switch on the serial port device according to the
configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Reconnect the cables between the RF unit and the serial port device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the cables between the RF unit and the serial port device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. Power cycle the serial port device on site. Wait until the serial port device startup is
complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
This alarm is reported when the power surge protector of the RF unit is faulty.
Parameters
System Actions
None
Possible Causes
The RF unit encounters lightning strikes. Therefore, open-circuit protection is implemented by in the power surge
protector of the RF unit.
Procedure
a. Check whether the surge protector of the RF unit and external power device is
functional.
Y => The surge protector is functional. Go to step 2.
N => The surge protector malfunctions or is not installed. Go to sub-step b.
b. Rectify the fault in the surge protector, or install a functional surge protector.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when a command is executed to turn off the switch of the TX channel of the RF unit.
Parameters
System Actions
None
Possible Causes
The command is executed to turn off the switch of the TX channel of the RF unit.
Procedure
a. After the NE maintenance is complete, run the MML command MOD TXBRANCH to
turn on the switch.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
The alarm is reported if the RF unit detects an insufficiency in the capability of the external power supply.
Parameters
Parameter
Parameter Description
Name
Specific Specific Problem of the alarm(Cabinet Power Supply Abnormal, Cabinet Type and RF Unit
Problem type Mismatch)
Minor The RF unit operates in power derating mode, and thereby affects the system
capacity.
Major The RF unit operates in power derating mode or becomes unavailable, and thereby
affects the system capacity and coverage.
System Actions
If "Specific Problem" is "Cabinet Power Supply Abnormal", the RF unit operates in power derating
mode.
If "Specific Problem" is "Cabinet Type and RF Unit Type Mismatch", the RF unit is set to be
unavailable or in power derating mode.
Possible Causes
Procedure
a. Check for the problem in the alarm detailed information on the M2000.
If "Specific Problem" is "Cabinet Type and RF Unit Type Mismatch", go to step 2.
If "Specific Problem" is "Cabinet Power Supply Abnormal", go to step 3.
2. Check whether the cabinet type and the RF unit type match on the M2000.
a. Run the MML command DSP BRDMFRINFO to check the description in the
manufacture information about the RF unit that reports the alarm. Check whether the
RF unit type is MRFUe or MRFUd.
Y => The RF unit type is MRFUe or MRFUd, go to sub-step b.
N => The RF unit type is not MRFUe or MRFUd, Contact Huawei Customer Service
Center.
b. Run the MML command DSP CABMFRINFO to check whether the cabinet description
contains one of the following characters: 303+, 103+, and 202+.
Y => The cabinet description contains one of the following characters: 303+, 103+, and
202+, Contact Huawei Customer Service Center.
N => The cabinet description does not contain any of the following characters: 303+,
3. Check the type of power supply for the cabinet on the M2000.
a. Run the MML command DSP BRD to check whether the base station is configured with
the PMU.
Y => The base station is configured with the PMU, go to step 5.
N=> The base station is not configured with the PMU, go to step 4.
4. Check the DC power supply system for the base station cabinet on site.
a. Check whether the DC power system and the mains supply for the base station cabinet
are normal on site.
Y => The power supply for the base station is normal, Contact Huawei Customer
Service Center.
N => The power supply for the base station is abnormal, go to sub-step b.
b. Restore the DC power system and the mains supply for the base station cabinet.
Check Whether the Alarm is Cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Check the AC power supply system for the base station cabinet on site.
a. Replace the RF unit that reports the alarm with an RU whose type is not MRFUe or
MRFUd.
Replace the RF Unit.
Check Whether the Alarm is Cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
This alarm is reported when the motor of the RET antenna is faulty.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Motor Detection Failed, Motor Permanently Stalled, Motor
Problem Temporarily Stalled)
System Actions
None
Possible Causes
Procedure
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the RET antenna.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the hardware of the antenna device (RET antenna, TMA or SASU) is faulty.
Parameters
Major If the primary hardware of the TMA is faulty, the RX gain amplification function of the
TMA may fail. In this case, the ongoing services carried on the RX channel
associated with the TMA are disrupted.
The SASU malfunctions. As a result, the cell coverage may shrink.
Minor If the hardware of the RET antenna is faulty, the antenna tilt may fail to be regulated.
In this case, the status of the RET antenna cannot be monitored.
If the secondary hardware of the TMA is faulty, the TMA gain cannot be configured.
In this case, the status of the TMA cannot be monitored.
The secondary hardware of the SASU is faulty. As a result, some secondary
functions of the SASU may fail.
System Actions
When the TMA or SASU is severely faulty (alarm severity: major), the TMA or SASU is automatically bypassed.
Meanwhile, the system automatically sets the attenuation on the corresponding RX channel to 0. After the fault in
the TMA or SASU is cleared, the system automatically restores the attenuation on the corresponding RX channel
to the configured value.
Possible Causes
Procedure
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the antenna device.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the antenna device.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the base station detects that the RET antenna is not calibrated.
Parameters
Minor The cell coverage on the RET antenna is inconsistent with the configuration.
System Actions
None
Possible Causes
Procedure
a. Run the MML command CLB RET to calibrate the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the configured data of the RET antenna is lost.
Parameters
System Actions
None
Possible Causes
The RET antenna is powered off during data reconfiguration, which leads to data loss.
The flash memory of the RET antenna is damaged.
The RET antenna is newly installed without the data configuration file.
Procedure
a. Run the MML command DLD RETCFGDATA to re-download the configuration file of the
RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the RET antenna.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the TMA is automatically bypassed in the case of a critical fault.
Parameters
Major After the TMA is bypassed, the receive sensitivity of the RX channel decreases and
the sector coverage shrinks.
System Actions
The TMA is automatically bypassed. Meanwhile, the system automatically sets the attenuation on the
corresponding RX channel to 0.
Possible Causes
Procedure
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the TMA.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the TMA.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the VSWR on the antenna port of the SASU is beyond the VSWR alarm threshold.
Parameters
Major The return loss at the antenna port of the SASU is relatively large. In this case, the
output power of the RF unit decreases and the cell coverage shrinks.
System Actions
None
Possible Causes
The feeder connector on the antenna port of the SASU is loose or waterlogged.
The feeder connected to the antenna port of the SASU is bent, deformed, or damaged.
Procedure
a. Reconnect the jumper to the antenna port of the SASU. Then, wait for 10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the SASU.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the SASU. Then, wait for 10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
This alarm is reported when the base station detects that the running data of the RET antenna is inconsistent
with the configuration. For example, the actual antenna tilt is inconsistent with the configuration.
Parameters
Minor The cell coverage on the RET antenna is inconsistent with the configuration.
System Actions
None
Possible Causes
Because of RET antenna reset or maintenance link disconnection, the data configuration on the base
station is inconsistent with that on the RET antenna.
The configured data of the RET antenna is lost or modified on the base station.
The RET antenna works improperly, resulting in an automatic change of the downtilt.
Procedure
a. Run the MML command LST RETSUBUNIT to query the error range of the downtilt
alarm. Check whether the error range is consistent with the configuration plan.
Y => The error range is consistent with the configuration plan. Go to step 2.
N => The error range is inconsistent with the configuration plan. Go to sub-step b.
b. Run the MML command MOD RETSUBUNIT to modify the error range of the downtilt
alarm of the RET.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Check whether the configured downtilt exceeds the RET antenna capability.
Y => The configured downtilt exceeds the RET antenna capability. Go to substep b.
N => The configured downtilt does not exceed the RET antenna capability. Go to
substep d.
b. Check whether the downtilt is appropriate.
Y => The downtilt is appropriate, and the RET antenna capability is insufficient. Go to
step 4.
N => The downtilt is inappropriate. Go to substep c.
d. Run the MML command MOD RETTILT to set the RET downtilt.
Check whether the alarm is cleared.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the RET antenna.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the RET antenna.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
This alarm is reported when the base station detects that the running data of the TMA is inconsistent with the
configuration. For example, the TMA gain or working mode is inconsistent with the configuration.
Parameters
Minor The receive sensitivity of the RX channel is extremely low or high, resulting in
improper sector coverage.
System Actions
None
Possible Causes
Because of TMA reset or maintenance link disconnection, the data configuration on the base station
is inconsistent with that on the TMA.
The configured data of the TMA is lost or modified on the base station.
The TMA works improperly, resulting in an automatic change of the TMA gain or TMA work mode.
Procedure
a. Run the MML command MOD TMASUBUNIT to set the TMA gain.
Run the MML command MOD TMASUBUNIT to set the TMA mode.
Check 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.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the TMA.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the TMA.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the base station detects that the running data of the SASU is inconsistent with the
configuration. For example, the working mode, gain, state of the DC switch, or DC load of the SASU is
inconsistent with the configuration.
Parameters
Minor The receive sensitivity is extremely low or high, resulting in improper sector
coverage.
System Actions
None
Possible Causes
Because of SASU reset or maintenance link disconnection, the data configuration on the base station
The configured data of the SASU is lost or modified on the base station.
The SASU works improperly, resulting in an automatic change of the SASU gain or SASU work
mode.
Procedure
a. Run the MML command MOD SASUSUBUNIT to set the SASU mode.
Run the MML command MOD SASUSUBUNIT to set the SASU gain.
Run the MML command MOD SASU to set the DC switch state of the SASU.
Run the MML command MOD SASU to set the DC load of the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the SASU.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the SASU is automatically bypassed in the case of a critical fault.
Parameters
Major After the SASU is bypassed, the receive sensitivity of the RX channel decreases and
System Actions
The SASU is automatically bypassed. Meanwhile, the system automatically sets the attenuation on the
corresponding RX channel to 0.
Possible Causes
Procedure
a. Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn off the ALD
switch of the RF unit connected to the SASU.
Run the MML command MOD ANTENNAPORT/MOD RETPORT to turn on the ALD
switch of the RF unit connected to the SASU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
Parameters
Major The RHUB may work improperly. The ongoing services carried on the RHUB may be
disrupted.
Minor Some functions of the RHUB may fail and the quality of services carried on the
PRRUs connected to the RHUB may decrease.
System Actions
When a critical component of an RHUB is faulty, the system automatically disables the RHUB.
Possible Causes
Procedure
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF to reset the RHUB on the M2000.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the software program of the RHUB runs improperly, such as suspension.
Parameters
Major The RHUB may work improperly. The RHUB will be automatically reset. The ongoing
services carried on the PRRUs connected to the RHUB are disrupted during reset.
System Actions
Possible Causes
Procedure
This alarm is reported when the CPU usage of the RHUB is beyond the operating threshold.
Parameters
Minor The user access success rate and service quality may decrease.
Long-term CPU overload may result in delayed response or timeout of maintenance
tasks of the board.
The test or tracing tasks with low priority may be automatically suspended or
terminated.
System Actions
The flow control is started. The test or tracing tasks with low priority may be automatically suspended or
terminated.
Possible Causes
The user runs too many configuration or maintenance commands frequently on the RHUB.
The user starts too many test or measurement tasks on the RHUB.
Procedure
1. Stop the configuration and maintenance tasks on the RHUB on the M2000.
a. Stop the configuration and maintenance tasks on the RHUB. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Stop the test, tracing, and information collecting tasks in progress on the RHUB on the M2000.
a. Stop all the test, tracing, and information collecting tasks in progress on the RHUB.
Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF on the M2000 to reset the RHUB through
power-off. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the CPRI interface clock of the RHUB is faulty, or the working clock of an internal
component is faulty.
Parameters
Major Some components in the RHUB may work improperly. In certain cases, the ongoing
services carried on the PRRUs connected to the RHUB may be disrupted.
System Actions
When the working clock of a critical component in the RHUB is faulty, the system automatically disables the
faulty RHUB.
Possible Causes
The uplink CPRI interface of the RHUB is faulty, resulting in the faulty clock that is extracted at the
CPRI interface.
Procedure
a. Check for the correlated alarm on the CPRI port of the RHUB on the M2000:
26783 RHUB CPRI Interface Error
26234 BBU CPRI Interface Error
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRDPWROFF on the M2000 to reset the RHUB through
power-off.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported by the external alarm port 0 of the RHUB when the UPS surge protection device (SPD)
fails because its protection circuit is damaged.
Parameters
System Actions
None
Possible Causes
The cable between the RHUB and the SPD is not ready or faulty.
Procedure
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 0.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the cable connection between the RHUB and the SPD on site.
a. Check whether the cable connection between the RHUB and the SPD is normal.
Y => The cable connection is normal. Go to procedur 3.
N => The cable connection is faulty. Go to sub-step b.
This alarm is reported by the external alarm port 1 of the RHUB configured with the UPS when the AC mains
supply fails.
Parameters
Major The RHUB is powered by the UPS when the AC mains supply fails. If the AC mains
supply is unavailable for a long time, the RHUB will be powered off when the battery
is exhausted. In this case, the ongoing services carried on all the PRRUs connected
to the RHUB are disrupted.
System Actions
None
Possible Causes
The monitoring cable between the RHUB and the UPS is faulty.
Procedure
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 1.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the monitoring cable between the RHUB and the UPS on site.
a. Check whether the monitoring cable between the RHUB and the UPS is normal.
a. Check whether the AC mains supply for the UPS is normal on site.
Y => The AC mains supply for the UPS is normal. Contact Huawei Customer Service
Center.
N => The AC mains supply for the UPS fails. Go to sub-step b.
b. Rectify the fault on the AC mains supply for the UPS. Wait until the AC mains supply is
available.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported by the external alarm port 2 of the RHUB configured with the UPS. When the AC mains
supply fails, the UPS starts to work and is powered by the battery. This alarm is reported when the UPS battery
voltage drops to the undervoltage threshold.
Parameters
Major The RHUB continues to operate for an additional short period after this alarm is
reported. When the UPS battery is exhausted, the RHUB is powered off and the
ongoing services carried on all the connected PRRUs are disrupted.
System Actions
None
Possible Causes
The monitoring cable between the RHUB and the UPS is faulty.
The AC mains supply malfunctions for a long time, such as power failure, overvoltage, undervoltage,
or excessive frequency deviation.
Procedure
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The RHUB is configured with the UPS. Go to step 2.
N => The RHUB is not configured with the UPS. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 2.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the monitoring cable between the RHUB and the UPS battery on site.
a. Check whether the monitoring cable between the RHUB and the UPS battery is normal.
Y => The monitoring cable is normal. Go to step 3.
N => The monitoring cable is faulty. Go to sub-step b.
b. Reconnect the monitoring cable between the RHUB and the UPS battery.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Check whether the AC mains supply for the UPS malfunctions for a long time, such as
power failure, overvoltage, undervoltage, or excessive frequency deviation.
Y => The AC mains supply for the UPS malfunctions. Go to sub-step b.
N => The AC mains supply for the UPS is normal. Go to step 4.
b. Rectify the fault on the AC mains supply for the UPS. Wait until the AC mains supply is
available.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Check whether the battery is damaged according to the maintenance manual offered by
the vendor.
Y => The battery is damaged. Go to sub-step b.
N => The battery is normal. Contact Huawei Customer Service Center.
This alarm is reported by the external alarm port 3 of the RHUB configured with the UPS when the UPS is
damaged.
Parameters
Major The UPS bypasses the AC mains supply to the RHUB when this alarm is reported.
The RHUB can continue to operate if the voltage and frequency of AC mains supply
meet the requirements of the RHUB.
System Actions
None
Possible Causes
Procedure
a. Check whether the RHUB is configured with the UPS on site. This alarm is required only
when the UPS is configured.
Y => The UPS is configured. Go to step 2.
N => The UPS is not configured. Go to sub-step b.
b. Run the MML command SET ALMPORT to disable the Boolean alarm of the external
alarm port 3.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the monitoring cable between the RHUB and the UPS on site.
a. Check whether the monitoring cable between the RHUB and the UPS is normal.
Y => The monitoring cable is normal. Go to step 3.
N => The monitoring cable is faulty. Go to sub-step b.
b. Reconnect the monitoring cable between the RHUB and the UPS.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the maintenance link for the AC/DC module of the RHUB fails.
Parameters
Major The power supply for the RHUB may fail. In this case, the ongoing services carried
on all the PRRUs connected to the RHUB are disrupted.
System Actions
None
Possible Causes
Procedure
a. Remove and reinstall the AC/DC module on the RHUB panel. Wait until the RHUB
startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Remove the AC/DC module from the RHUB panel and install a spare AC/DC module.
Wait until the RHUB startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the AC/DC module of the RHUB malfunctions.
Parameters
Major The RHUB and connected PRRUs may fail to work normally. In this case, the
ongoing services carried on the PRRUs are disrupted.
System Actions
None
Possible Causes
Overtemperature protection for the AC/DC module is triggered because the ambient temperature is
extremely high.
Procedure
a. Use a multimeter to measure the AC mains supply for the RHUB on site. Check whether
the AC mains supply is in overvoltage or undervoltage.
Y => The AC mains supply is in overvoltage or undervoltage. Go to sub-step b.
N => The AC mains supply is normal. Go to step 2.
a. Check whether the air vent of the RHUB is blocked by dusts or foreign objects.
Y => The air vent is blocked. Go to sub-step b.
N => The air vent is not blocked. Go to step 3.
b. Clean the air vent. Then, wait for 10 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Remove and reinstall the AC/DC module on the RHUB panel. Wait until the RHUB
startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
a. Remove the AC/DC module from the RHUB panel and install a spare AC/DC module.
Wait until the RHUB startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
This alarm is reported when the RHUB detects that the power supply for the PSE is disconnected or in
overcurrent mode.
Parameters
Major The PRRUs connected to the PSE may fail to work normally. In this case, the
ongoing services carried on the PRRUs are disrupted.
System Actions
None
Possible Causes
Procedure
1. Remove and reinstall the cable between the RHUB and the PRRU on site.
a. Remove and reinstall the cable between the RHUB and the PRRU. Power off the PRRU
and then power it on. Wait until the PRRU startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Disconnect the cable from the faulty PSE port of the RHUB, and then connect the cable
to another idle PSE port of the RHUB. Power off the PRRU and then power it on. Wait
3. Replace the cable between the RHUB and the PRRU on site.
a. Replace the cable between the RHUB and the PRRU. Power off the PRRU and then
power it on. Wait until the PRRU startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
Parameters
Cause Cause (Over Voltage, Below Voltage, Over Temperature Close, Oscillator Fault)
Major The PRRUs connected to the faulty PSE may fail to work normally. In this case, the
ongoing services carried on the PRRUs may be disrupted.
System Actions
None
Possible Causes
Overtemperature protection for the PSE is triggered because the ambient temperature of the RHUB
is extremely high.
Procedure
a. Check whether the fault cause is "Overtemperature Shutdown" according to the alarm
location information.
Y => The fault cause is "Overtemperature Shutdown". Go to step 2.
N => The fault cause is not "Overtemperature Shutdown". Go to step 3.
a. Check whether the air vent of the RHUB is blocked by dusts or foreign objects.
Y => The air vent is blocked. Go to sub-step b.
N => The air vent is not blocked. Go to step 3.
a. Run the MML command LST ALMAF to query active alarms. Check for 26775 RHUB
AC/DC Module Problem.
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 4.
a. Note: Resetting the RHUB disrupts all the ongoing services on the PRRUs connected to
the RHUB. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the RHUB. Wait until the RHUB startup is
complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
This alarm is reported when the optical module on the CPRI port of the RHUB is not in position or when the
cable connection on the CPRI optical module or electrical port is not ready.
Parameters
Major In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the active CPRI link of lower-level devices is switched over to the standby CPRI link.
Possible Causes
The networking of RHUB and lower-level devices is incorrect. Redundant lower-level devices are
configured.
The optical module on the CPRI port of the RHUB is not in position, or the cable connection on the
CPRI optical module or electrical port is not ready.
The optical module on the CPRI port of the RHUB is faulty, or the cable connected to the CPRI
optical module or electrical port is faulty.
Procedure
a. Run the MML command LST RRUCHAIN to query the CPRI link networking of the faulty
RHUB. According to the site planning, check whether the redundant lower-level devices
are configured.
Y => The redundant lower-level devices are configured. Go to sub-step b.
N => There is no redundant lower-level device. Go to step 2.
b. Run the MML command RMV RRU to remove the redundant lower-level devices.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
2. Check the installation of the optical module, or check the cable connection on the CPRI optical
module or electrical port of the RHUB on site.
a. Check whether the optical module is installed, or whether the cable is connected to the
CPRI optical module or electrical port of the RHUB on site.
Y => The optical module is installed, and the cable is connected. Go to sub-step c.
N => The optical module is not installed, or the cable is not connected. Go to sub-step
b.
b. Install the optical module or connect the cable to the CPRI optical/electrical port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
c. Remove the optical module or the cable connected to the CPRI optical/electrical port,
and then reinstall it properly.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Power off the RHUB on site and then power it on. Wait until the RHUB startup is
complete (the RUN LED blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
This alarm is reported when the optical module (1.25 Gbit/s or 2.5 Gbit/s) installed on the CPRI port of the
RHUB is not supported by the RHUB.
Parameters
Valid Optical Module Type Valid optical module type (1.25 Gbps, 2.5 Gbps)
Installed Optical Module Type Installed optical module type (1.25 Gbps, 2.5 Gbps)
Major The CPRI port of the RHUB does not work normally. The services carried on all the
PRRUs connected to the RHUB are disrupted.
System Actions
None
Possible Causes
The type of the optical module installed on an RHUB is not supported by the RHUB. For example, an RHUB
supports only an optical module of 2.5 Gbit/s, but an optical module of 1.25 Gbit/s is installed on the RHUB.
Procedure
a. Replace the optical module of the RHUB on site. Ensure that the installed optical
module is supported by the RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the optical transmission on the optical link (at the physical layer) is abnormal
between the RHUB and the peer device (upper-level/lower-level RHUB, RF unit, or BBU).
Parameters
Major In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RHUB automatically switches to a normal CPRI port if its uplink CPRI port is
faulty.
Possible Causes
The optical module or connector of the current-level RHUB is improperly installed. Or the optical
module is faulty.
The peer device (upper-level/lower-level RHUB, RF unit, or BBU) is not powered on.
The optical module or connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU)
is improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU) is dirty.
The peer device is faulty.
The optical link between the current-level RHUB and the peer device (upper-level/lower-level RHUB,
RF unit, or BBU) is faulty.
Procedure
a. Check for the correlated alarm on the faulty CPRI port of the RHUB on the M2000.
26780 RHUB Optical Module or Electrical Port Not Ready
26781 RHUB Optical Module Type Mismatch
26786 RHUB Optical Module Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
a. On the current-level RHUB side, remove and reinstall the optical module and connector
on the faulty CPRI port.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Connect the TX and RX terminals of the optical fiber at the current-level RHUB on site.
a. Remove the optical fiber from the optical module of the RHUB. Then, connect the TX
and RX terminals of the optical fiber by using a flange.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step c.
N => The alarm is not cleared. Go to sub-step b.
b. Disconnect the TX and RX terminals of the optical fiber, and restore the optical
connection of the RHUB. Then, Go to step 4.
a. On the peer device side, check whether the RUN LED on the peer device blinks (ON for
1s and OFF for 1s).
Y => The RUN LED blinks (ON for 1s and OFF for 1s). The peer device is running
normally. Go to step 5.
N => The RUN LED does not blink (ON for 1s and OFF for 1s). The peer device is
running improperly. Go to sub-step b.
b. Power cycle the peer device on site. Wait until the RUN LED blinks (ON for 1s and OFF
for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
a. Remove and reinstall the optical module and connector on the CPRI port of the peer
device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
6. Connect the TX and RX ports of the optical module at the peer device.
a. Remove the optical fiber from the optical module of the peer device. Then, connect the
TX and RX ports of the optical module by using an optical fiber for loopback.
Check whether the alarm is cleared.
Y => The alarm is cleared. Go to sub-step b.
N => The alarm is not cleared. Go to sub-step c.
b. Disconnect the TX and RX ports of the optical module, and restore the optical
connection of the peer device. Then, Go to step 7.
a. Check the optical connections between the current-level RHUB and the peer device.
Troubleshoot the improper optical connections, such as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
This alarm is reported when the data transmission on the CPRI link (at the link layer) is abnormal between the
RHUB and the peer device (upper-level/lower-level RHUB, RF unit, or BBU).
Parameters
Major In chain topology, the CPRI link of lower-level devices is disconnected. The services
carried on lower-level devices are disrupted.
In ring topology, the reliability of the CPRI link decreases. In this case, the active
CPRI link of lower-level devices is switched over to the standby CPRI link. In the
case of a hot ring, the ongoing services are not affected. In the case of a cold ring,
the ongoing services are disrupted temporarily.
System Actions
In ring topology, the current-level RHUB automatically switches to a normal CPRI port if its uplink CPRI port is
faulty.
Possible Causes
If the CPRI optical transmission is used, the optical module or connector of the RHUB or peer device
may be improperly installed, or the optical link is faulty.
If the CPRI electrical transmission is used, the cable connector of the RHUB or peer device may be
improperly installed, or the cable is faulty.
Procedure
a. Check for the correlated alarm on the faulty CPRI port of the RHUB on the M2000.
26780 RHUB Optical Module or Electrical Port Not Ready
26781 RHUB Optical Module Type Mismatch
26782 RHUB Optical Module Transmit/Receive Fault
26786 RHUB Optical Module Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. On site, check the cable connections on the CPRI electrical port of the RHUB.
a. Check the cable connections on the CPRI port of the current-level RHUB on site.
If the CPRI electrical transmission is used, Go to sub-step b.
If the CPRI optical transmission is used, Go to step 3.
b. Remove and reinstall the cable on the CPRI electrical port of the current-level RHUB
and the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
a. Power off the RHUB on site and then power it on. Wait until the RHUB startup is
complete (the RUN LED blinking, ON for 1s and OFF for 1s).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
This alarm is reported when the TX/RX performance of the optical module of the RHUB deteriorates.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Optical Module Performance Degraded, Reception Power too
Problem High, Reception Power too Low)
Major When the TX/RX performance of the optical module deteriorates significantly, the
quality of services carried on the CPRI link of the RHUB may decrease significantly,
or the ongoing services carried on the RHUB may even be disrupted.
Minor When the TX/RX performance of the optical module deteriorates to some extent, the
quality of services carried on the CPRI link of the RHUB may decrease to some
extent.
System Actions
None
Possible Causes
The optical module or connector of the current-level RHUB is improperly installed. Or the optical
module is aged.
The optical module or connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU)
is improperly installed. Or the optical module is faulty.
The optical connector of the peer device (upper-level/lower-level RHUB, RF unit, or BBU) is dirty.
The optical module on the CPRI port of the peer device (upper-level/lower-level RHUB, RF unit, or
BBU) is not supported by the peer device, in terms of type (single-mode or multi-mode) and rate.
The optical fibers between the current-level RHUB and the peer device (upper-level/lower-level
RHUB, RF unit, or BBU) are bent, deformed, or aged. Or the length of optical fibers is excessive
(longer than 40 km), which leads to a high attenuation of optical signals.
Procedure
a. Remove and reinstall the optical module and connector on the CPRI port of the
current-level RHUB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module on the CPRI port is supported by the current-level
RHUB, in terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5
Gbit/s).
Y => The optical module is supported by the RHUB. Go to sub-step e.
N => The optical module is not supported by the RHUB. Go to sub-step d.
d. Select the optical module that is supported by the RHUB.
a. Remove and reinstall the optical module and connector on the CPRI port of the peer
device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Remove the connector of the optical module. Clean the connector by using absolute
alcohol. Then, reinstall the connector to the optical module.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Check whether the optical module on the CPRI port is supported by the peer device, in
terms of type (single-mode or multi-mode) and rate (1.25 Gbit/s or 2.5 Gbit/s).
Y => The optical module is supported by the peer device. Go to sub-step e.
N => The optical module is not supported by the peer device. Go to sub-step d.
a. Check the optical connections between the current-level RHUB and the peer device.
Troubleshoot the improper optical connections, such as fiber bending or deformation.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Check the length of the optical link between the current-level RHUB and the peer
device. If the length is excessive (longer than 40 km), add an optical trunk or use
another cascaded RHUB as the optical trunk.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Replace the optical fibers between the current-level RHUB and the peer device.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the optical module on the CPRI port of the RHUB is faulty.
Parameters
System Actions
None
Possible Causes
Procedure
This alarm is reported when the CPRI interface between the RHUB and the PRRU malfunctions.
Parameters
Major The CPRI interface between the RHUB and the PRRU malfunctions. In this case, the
maintenance link for the PRRU is broken and the PRRU cannot provide the services.
System Actions
None
Possible Causes
The cable connection between the RHUB and the PRRU is not ready.
The cable between the RHUB and the PRRU is faulty.
Procedure
1. Remove and reinstall the cable between the RHUB and the PRRU on site.
a. Remove and reinstall the cable between the RHUB and the PRRU. Power off the PRRU
and then power it on. Wait until the PRRU startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Disconnect the cable from the faulty PSE port of the RHUB, and then connect the cable
to another idle PSE port of the RHUB. Power off the PRRU and then power it on. Wait
until the PRRU startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Replace the cable between the RHUB and the PRRU on site.
a. Replace the cable between the RHUB and the PRRU. Power off the PRRU and then
power it on. Wait until the PRRU startup is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
Parameters
None.
Major The NE enters the default license mode. The NE services are subject to the default
license.
System Actions
Possible Causes
Procedure
a. Check the license allocation on the M2000. Check whether the NE is allocated with the
license resources.
Y => The NE is allocated with the license resources. Go to sub-step c.
N => The NE is not allocated with the license resources. Go to sub-step b.
b. Adjust the license allocation among NEs on the M2000. Allocate the license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the system detects that the configured capacity limit exceeds the licensed limit in
the case of system startup.
Parameters
Mismatched Control Item Licensed control item that is lower than system configuration
System Actions
None.
Possible Causes
The configured system capacity exceeds the currently allocated license limit for the system.
Procedure
a. Check the license allocation on the M2000. Check whether there are license resources
available for the current NE.
Y => There are license resources available for the current NE. Go to sub-step b.
N => There are no license resources available for the current NE. Go to step 2.
b. Adjust the license allocation among NEs on the M2000. Allocate more license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Change the values of NE data to be equal to or less than the limit values in the license.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. 3.
3. Order a license.
a. Based on hardware configuration and plan, order a license with a higher capacity limit.
End the alarm handling.
This alarm is reported when the traffic volume of the NE is beyond the capacity limit (configurable) of the license
consistently. This alarm is cleared when the traffic volume of the NE stays below 90% (configurable) of the
capacity limit of the license consistently.
Parameters
Excessive Control Item Control item that exceeds the licensed limit
System Actions
None
Possible Causes
Procedure
a. Run the MML command LST LICENSEALMTHD to check whether the setting of the
alarm threshold is proper.
Y => The setting of the alarm threshold is proper. Go to step 2.
N => The setting of the alarm threshold is improper. Go to sub-step b.
b. Run the MML command SET LICENSEALMTHD to modify the alarm threshold.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Check the license allocation on the M2000. Check whether there are license resources
available for the current NE.
Y => There are license resources available for the current NE. Go to sub-step b.
N => There are no license resources available for the current NE. Go to step 3.
b. Adjust the license allocation among NEs on the M2000. Allocate more license resources
to the current NE.
c. Manually trigger the NE license synchronization on the M2000. Wait until the
synchronization is complete.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Order a license.
a. Based on service requirements, order a license with a higher capacity limit. End the
alarm handling.
This alarm is reported if a local user account is locked when used to log in to an NE through the local
maintenance terminal (LMT) due to one of the following reasons: (1) The number of invalid passwords that are
consecutively entered exceeds a pre-defined threshold. The default value of the threshold is three times. (2) The
user name is invalid.
Parameters
Specific Problem Specific Problem of the alarm(Password Error, Invalid User Name)
Minor The NE is exposed to security risks. The local user may be attacked by invalid users
or the NE is in an insecure network. The NE is vulnerable to attacks.
System Actions
If the user enters a valid user name but incorrect passwords, the corresponding local user account is locked.
Possible Causes
Procedure
a. Based on the specific problem in the alarm detailed information, check whether the local
user account is valid.
Y => The local user account is valid, go to step 2.
N => The local user account is invalid, contact the network security center.
a. Contact the owner of the login account. Check whether the login operation is initiated by
the owner.
Y => The login operation is initiated by the owner. Go to sub-step b.
N => The login operation is not initiated by the owner. Turn to the network security
center.
b. Check whether the owner of the account has forgotten the login password.
Y => The owner of the account has forgotten the login password. Go to sub-step c.
N => The owner of the account has not forgotten the login password. Go to sub-step d.
c. Run the MML command RST PWD to update the login password of the user on the
M2000. Inform the owner of the account about the new login password.
d. Run the MML command ULK USR to unlock the user on the M2000.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
During the operation of the base station, the alarm is reported when the peer attempts to establish a connection
with the base station by performing security authentication with an expired certificate.
Parameters
Minor The NE is exposed to security risks, because the certificate of the peer has expired.
System Actions
The base station disconnects itself from the peer that uses an expired certificate.
Possible Causes
The peer certificate is not updated in time, and the peer certificate expires or the peer certificate is
revoked .
An invalid user attempts to connect to the base station with an expired certificate.
Procedure
a. Check the validity of the peer based on the IP address of the peer that is reported in
the alarm detailed information.
Y => The peer is valid, go to step 2.
N => The peer is invalid, contact the network security center.
a. Contact the staff on the peer side to update the certificate and then reestablish a
connection with the base station.
Check Whether the Alarm is Cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the time span between the current time and the expiration time of the loaded
certificate is below the user-defined threshold.
Parameters
Certificate Type Type of certificate (Application certificate, Trust certificate, Cross certificate, CRL)
Minor The Internet Key Exchange (IKE) or Security Socket Layer (SSL) negotiation
requires a valid certificate. If the base station adopts the IKE/SSL certificate
negotiation, an expired certificate may lead to a negotiation failure and disrupt the
ongoing services.
System Actions
None
Possible Causes
The certificate is about to expire. That is, the time span between the current time and the expiration
time of the loaded certificate is below the user-defined threshold.
Procedure
a. Run the MML command DSP TIME to check whether the current time of the base
station is correct.
Y => The time is correct. Contact Huawei Customer Service Center.
N => The time is incorrect. Go to sub-step b.
b. Run the MML command SET TIME to change the current time of the base station.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the NodeB detects any of the following: certificate expiry, certificate file loss,
certificate file damage, certificate not-yet-effective, or a certificate file format error.
Parameters
Parameter
Name Parameter Description
Certificate Type Type of certificate (Application certificate, Trust certificate, Cross certificate, CRL)
Specific Problem Specific Problem of the alarm(Expired, Lost, Damaged, Format Error, Other, Not Valid
Yet)
Major The Internet Key Exchange (IKE) or Security Socket Layer (SSL) negotiation
requires a valid certificate. If the base station adopts the IKE/SSL certificate
negotiation, an invalid certificate may lead to a negotiation failure and disrupt the
ongoing services.
System Actions
None
Possible Causes
Procedure
a. Run the MML command DSP TIME to check whether the current time of the base
station is correct.
Y => The time is correct. Go to step 3.
N => The time is incorrect. Go to sub-step b.
b. Run the MML command SET TIME to change the current time of the base station.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Check the certificate type that induces the alarm on the M2000.
a. Run the MML command REQ DEVCERT to apply for a device certificate.
b. Run the MML command MOD APPCERT to activate the device certificate.
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.
a. Run the MML command RMV TRUSTCERT to remove the trusted certificate.
b. Run the MML command DLD CERTFILE to download the trusted certificate.
c. Run the MML command ADD TRUSTCERT to add the trusted certificate.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
Certificate Type Type of certificate (Application certificate, Trust certificate, Cross certificate, CRL)
Minor The certificate cannot be automatically updated as scheduled, which may bring
security risks. If this alarm is not handled immediately, the certificate will expire in a
period of time and services will be disrupted.
System Actions
None
Possible Causes
The task used to automatically update the certificate is not configured according to the configuration
plan, or the IP route is incorrectly configured.
The certificate and CRL server or the Certificate Authority (CA) server is abnormal.
Procedure
a. Check for the correlated alarms of the port used for time synchronization on the M2000.
25880 Ethernet Link Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
a. On the M2000, determine the certificate type that induces the alarm based on the alarm
detailed information.
If "Certificate Type" is "CRL". Go to sub-step b.
If "Certificate Type" is "Application certificate". Go to sub-step d.
b. Run the MML command DSP CRL to check whether the CRL check task is configured
according to the configuration plan.
Y => If the CRL check task is configured according to the configuration plan. Go to step
3.
N => If the CRL check task is not configured according to the configuration plan. Go to
sub-step c.
c. Run the MML command RMV CRL,ADD CRL to modify the CRL check task according
to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
d. Run the MML command LST CERTCHKTSK to check whether the certificate check
task is configured according to the configuration plan.
Y => If the certificate check task is configured according to the configuration plan. Go
to step 3.
N => If the certificate check task is not configured according to the configuration plan.
Go to sub-step e.
e. Run the MML command SET CERTCHKTSK to modify the certificate check task
according to the configuration plan.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
3. Check whether the IP route from the NE to the certificate and CRL server or CA server is
configured on the M2000.
a. Run the MML command LST IPRT to check whether the IP route from the NE to the
certificate and CRL server or CA server exists.
Y => The route exists. Go to step 4.
N => The route does not exist. Go to sub-step b.
b. Run the MML command ADD IPRT to add an IP route from the NE to the certificate and
CRL server or CA server.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 4.
4. Check whether the route from the NE to the certificate and CRL server or CA server is available on
the M2000.
a. Run the MML command PING to start the PING test and check whether the CA server
or the server that stores the certificate and the CRL can be reached.
Y => The CA server or the server that stores the certificate and the CRL can be
reached. Go to step 5.
N => The CA server or the server that stores the certificate and the CRL cannot be
reached. Go to sub-step b.
b. Contact the maintenance center responsible for the routing device. Rectify the route
fault.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
5. Check whether the CA server or the server that stores the certificate and the CRL functions
normally.
a. Contact the maintenance center responsible for the CA server or the server that stores
the certificate and the CRL. Check the status of the server and rectify the fault.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
The user can restrict the RNC from using a certain resource or all local cell resources by blocking local cells.
This alarm is reported when local cells are blocked.
Parameters
Minor When a local cell is blocked, the cell cannot carry services.
System Actions
None
Possible Causes
The user runs a command to block the local cell of the NE.
Procedure
a. Run the MML command UBL LOCELL to block the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the local cell is unavailable due to physical or logical resource faults.
Parameters
Parameter
Name Parameter Description
System Actions
None
Possible Causes
User operations: The board is reset, blocked, not inserted, or not configured properly.
Configuration: The local cell configuration exceeds the capability supported by the hardware.
License capability: The license capability is lower than the local cell configuration capability.
Hardware faults: Board hardware is faulty, RF unit hardware is faulty, or the link between the
baseband interface board and RF unit is broken.
Procedure
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
c. Run the MML command LST LOCELL to query local cell information, such as the
parameters "UL BB Resource Group No.", "Local Cell Radius", "High Speed Movement
Mode", and "Remote Cell Mode". Run the MML command LST ULGROUP to query the
information about the uplink resource group used by the local cell.
d. Run the MML command DSP BRD to query the property and status of the boards
contained in the uplink resource group.
e. Check whether the number of cells configured in the uplink resource group exceeds the
total number of cells allowed by the uplink resource group. The total number of cells
allowed by the uplink resource group is the accumulated value of the number of cells
supported by all boards in the uplink resource group and cannot exceed the maximum
number of cells allowed by the uplink resource group. For details about the cell
specification supported by the board, see the related hardware description.
Y => The uplink capacity consumed by the local cell exceeds the total capacity of the
uplink resource group. Go to sub-step f.
N => The uplink capacity consumed by the local cell does not exceed the total capacity
of the uplink resource group. Contact Huawei Customer Service Center.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the downlink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
c. Run the MML command LST LOCELL to query the local cell information ("DL BB
Resource Group No."), and then run the MML command LST DLGROUP to query the
information about the downlink resource group used by the local cell.
d. Run the MML command DSP BBPTC to query the number of cells supported by the
board in the downlink resource group.
e. Check whether the number of cells configured in the downlink resource group exceeds
the total number of cells allowed by the downlink resource group. The total number of
cells allowed by the downlink resource group is the accumulated value of the number of
cells supported by all boards in the downlink resource group and cannot exceed the
maximum number of cells allowed by the downlink resource group. For details about the
cell specification supported by the board, see the related hardware description.
Y => The number of cells configured for the downlink resource group exceeds the total
number of cells supported by the downlink resource group. Go to sub-step f.
N => The number of cells configured for the downlink resource group does not exceed
the total number of cells supported by the downlink resource group. Contact Huawei
Customer Service Center.
f. Use either of the following methods to modify the configuration:
Method 1: Run the MML command RMV LOCELL to delete the local cell whose
resources are unavailable, and then run the MML command ADD LOCELL to establish
a local cell in another downlink resource group that has sufficient resources.
Method 2: Add the WBBP, and then run the MML command MOD DLGROUP to add
the WBBP to the downlink resource group where the local cell resides.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Run the MML command LST LOCELL to query the information about the RRU
configured for the local cell, and then run the MML commands LST RRU and LST
RRUCHAIN to query the information about the interface board configured for the RRU.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the interface board-related alarms exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step c.
N => The alarms do not exist. Contact Huawei Customer Service Center.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
alarms related to the RRU/RFU or the baseband board connected to the RRU/RFU.
26210 Board Blocked
26235 RF Unit Maintenance Link Failure
26237 RRU Network Breakpoint
26524 RF Unit PA Overcurrent
26525 RF Unit Temperature Unacceptable
26529 RF Unit VSWR Threshold Crossed
26532 RF Unit Hardware Fault
26538 RF Unit Clock Problem
26545 RF Unit TX Channel Switched Off Through Command
26765 RHUB Hardware Fault
26768 RHUB Clock Problem
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.
c. Run the MML command LST LOCELL to query the information about the local cell,
such as the RRU or RFU used in the local cell, uplink and downlink UARFCNs, and
maximum output power.
d. Run the MML command DSP RRU to query the specifications of the RRU or RFU.
e. Check whether the uplink and downlink frequencies configured in the local cell are within
the permissible frequency range of the RRU or RFU. (The conversion formula between
UARFCNs and actual frequencies is available in the help information of the MML
command ADD LOCELL.)
Y => Go to sub-step g.
N => Go to sub-step f.
f. Run the MML command MOD LOCELL to change the frequency of the local cell to a
value within the frequency range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Check whether the frequency spacing between the current local cell and any of the
other local cells established on the RRU or RFU exceeds the allowed bandwidth of the
RRU or RFU (Minimum frequency spacing = 3.8 MHz; Maximum uplink frequency
spacing = UL Support Band Width - 3.8 MHz; Maximum downlink frequency spacing =
TxUnitNo 0 Support Band Width - 3.8 MHz).
Y => The frequency spacing between the current local cell and any of the other local
cells established on the RRU or RFU exceeds the allowed bandwidth of the RRU or
RFU. Go to sub-step h.
N => The frequency spacing between the current local cell and any of the other local
cells established on the RRU or RFU does not exceed the allowed bandwidth of the
RRU or RFU. Go to sub-step i.
h. Run the MML command MOD LOCELL to modify the frequency of the local cell to
ensure that its frequency spacing with the other cells is within the range supported by
the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step i.
i. Check whether the number of cells configured on the same RRU or RFU exceeds the
number of carriers supported by the RRU/RFU.
Y => The number of cells configured on the same RRU or RFU exceeds the number of
carriers supported by the RRU or RFU. Go to sub-step j.
N => The number of cells configured on the same RRU or RFU does not exceed the
number of carriers supported by the RRU or RFU. Go to sub-step k.
j. Run the MML command RMV LOCELL to delete the local cell whose resources are
unavailable, and then run the MML command ADD LOCELL to establish a local cell on
another uplink resource group that has sufficient resources.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step k.
k. Check whether the maximum power configured in the local cell is within the power range
supported by the RRU or RFU. In transmit diversity and 0.5/0.5 same zone coverage
mode, the power allocated to each RRU or RFU is equal to half of the total power of
the local cell. Run the MML command DSP RRU to obtain the maximum transmit power
supported by the RRU or RFU.
Note: In the case of a multi-mode RRU or RFU, the RRU or RFU transmit power is
shared by multiple modes. The specifications of the RRU or RFU transmit power may
be restricted to the RRU or RFU hardware and the power lock.
Y => The maximum power configured in the local cell is out of the power range
supported by the RRU or RFU. Go to sub-step l.
N => The maximum power configured in the local cell is within the power range
supported by the RRU or RFU. Go to sub-step m.
l. Run the MML command MOD LOCELL to change the maximum transmit power of the
local cell to a value within the power range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step m.
m. Run the MML command LST RRU to obtain the information about the RRU or RFU
configured on the same chain/ring. Run the MML command LST LOCELL to obtain the
number of cells configured for the same RRU or RFU. Run the MML command DSP
SFP to obtain the transmission rate of the optical module. If the transmission rate is
1.25 Gbit/s, the CPRI interface supports only four local cells (2 TX + 2 RX). If the
transmission rate is 2.5 Gbit/s, the CPRI interface supports only eight local cells (2 TX
+ 2 RX). Check whether the allowed number of local cells on a chain/ring exceeds the
number of local cells corresponding to the transmission rate on the chain/ring.
Y => The allowed number of local cells on a chain/ring exceeds the number of local
cells corresponding to the transmission rate on the chain/ring. Go to sub-step n.
N => The allowed number of local cells on a chain/ring does not exceed the number of
local cells corresponding to the transmission rate on the chain/ring. Contact Huawei
Customer Service Center.
n. Run the MML command RMV LOCELL to delete the local cell whose resources are
unavailable, and then run the MML command ADD LOCELL to establish a local cell on
another RRU or RFU that has sufficient resources on the chain/ring.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step o.
o. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 6.
a. Run the MML command DSP LICENSE on the LMT to check whether the value of
"Local Cell Num" specified in the license file is smaller than the number of configured
local cells.
Y => The value of "Local Cell Num" specified in the license file is smaller than the
number of configured local cells. Go to sub-step b.
N => The value of "Local Cell Num" specified in the license file is greater than or equal
to the number of configured local cells. Contact Huawei Customer Service Center.
b. Configure a new license for the NodeB on the M2000 side. For details, see the online
help of ALM-26811 Configured Capacity Limit Exceeding Licensed Limit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Contact Huawei Customer Service Center.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the alarms related to the RRU or RFU exist.
26210 Board Blocked
26235 RF Unit Maintenance Link Failure
26237 RRU Network Breakpoint
26524 RF Unit PA Overcurrent
26525 RF Unit Temperature Unacceptable
a. Run the MML command DSP CPRILBR to check whether the line rate of the RRU chain
meets the networking requirement.
Y => The line rate of the RRU chain meets the networking requirement. Go to sub-step
b.
N => The line rate of the RRU chain does not meet the networking requirement. Go to
sub-step c.
b. Query the carrier configuration for UMTS cells and the carrier configurations for cells of
other systems that share CPRI bandwidths with the UMTS cells. Check whether the
carrier configuration exceeds the maximum typical configuration by referring to the
specifications of the MBTS CPRI networking in the 3900 Series Base Station Technical
Description.
Y => The carrier configuration exceeds the maximum typical configuration. Go to
sub-step d.
N => The carrier configuration does not exceed the maximum typical configuration.
Contact Huawei Customer Service Center.
c. Check the maximum configuration at each level in the MML command execution result,
and change the optical modules whose rates do not match.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
d. Adjust the base station configuration based on the specifications of the MBTS CPRI
networking in the 3900 Series Base Station Technical Description.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
Parameters
System Actions
None
Possible Causes
Procedure
a. Run the MML command STP DLSIM to stop the cell simulated load.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the output power of an NE is at least 2 dB lower than the sum of the common
channel power configured by the RNC.
Parameters
Minor The decrease in the NE output power causes a reduction in the cell coverage.
System Actions
None
Possible Causes
Procedure
a. According to the cabinet/subrack/slot number displayed in the alarm information, run the
MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is reported again. Go to step 2.
12. The local cell does not support DC+MIMO. This alarm is reported when the user configures DC+MIMO in
the local cell.
13. The local cell does not support ERACH. This alarm is reported when the user configures ERACH in the local
cell.
14. This alarm is reported when certain baseband boards in the uplink resource group used by the local cell do
not support Independent Demodulation of Signals from Multiple RRUs in One Cell.
15. This alarm is reported when the local cell cannot use all available uplink baseband resources in the uplink
resource group.
16. Users have configured the activation and deactivation capability for the supplementary carrier of a cell but
actually the activation and deactivation capability of the supplementary carrier is not supported.
17. Users have configured the HSUPA anti-interference scheduling capability for a cell but actually the cell does
not support the HSUPA anti-interference scheduling capability.
18. The local cell does not support DC-HSUPA. This alarm is reported when the user configures but actually the
cell does not support DC-HSUPA.
19. This alarm is reported when the CPRI bandwidth for UMTS cells is insufficient due to the bandwidth
occupation by cells of other systems.
Parameters
Parameter
Name Parameter Description
Cause (Some RRU(s) in the iDBS cell not usable, Number of occupied BBU CPRI ports connected to
RRUs in the iDBS cell exceeding six, RRU transmit power less than the transmit power required
by the local cell, Two TX channels not supported by the cell, Uplink 16QAM not supported by the
cell, Uplink L2+ not supported by the cell, Downlink 64QAM+MIMO not supported by the cell,
FDE not supported by the cell, IC not supported by the cell, DC not supported by the cell,
BOOST not supported by the cell, DCMIMO not supported by the cell, ERACH not supported by
the cell, MultiRRU Independ DemOver Cell not supported by WBBP Board, Cell can't use all
WBBP Board resources of the uplink resource group, ACT and DEA of Slave Carrier not
supported by the cell, Anti-Interference Scheduling for HSUPA not supported by the cell,
DC-HSUPA not supported by the cell, Insufficient CPRI bandwidth)
Major The coverage of the faulty local cell decreases, the RTWP reported by some RRUs
is discarded, the features configured on the local cell are not supported, or certain
demodulation capabilities of the uplink resource group used by the local cell are
unavailable.
System Actions
None
Possible Causes
Configuration: Parameter settings of the local cell are incorrect, or the local cell capability configured
by the user does not match the actual capability.
License capability: The license capability is lower than the local cell configuration capability.
Hardware capability: The hardware capability of the baseband board or RF unit is insufficient, or the
CPRI bandwidth is insufficient.
Hardware faults: In scenarios of multiple RRUs in one cell, the hardware of an RRU that serves the
local cell is faulty, or the link between an RRU and the baseband interface board is broken.
Procedure
2. Check for redundant RRUs configured in the local cell on the M2000.
a. Run the MML command LST LOCELL to check the RRUs configured in the faulty local
cell. Check whether redundant RRUs exist according to the network planning.
Y => Redundant RRUs exist. Go to sub-step b.
b. Run the MML command RMV RRU to delete the redundant RRUs.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms. Check whether the RRUs configured in the faulty local cell are faulty.
Y => The RRUs are faulty. Go to sub-step b.
N => The RRUs are functional. Contact Huawei Customer Service Center.
4. Rectify the fault that the number of occupied BBU CPRI ports connected to RRUs in the iDBS cell
exceeds six on the M2000.
a. Run the MML command LST LOCELL to query all the RRUs configured in the current
local cell. Check whether the number of occupied BBU CPRI ports connected to RRUs
exceeds six.
Y => The number of occupied BBU CPRI ports connected to RRUs exceeds six. Go to
sub-step b.
N => The number of occupied BBU CPRI ports connected to RRUs does not exceed
six. Contact Huawei Customer Service Center.
b. Reconfigure the position or number of RRUs in the local cell. Ensure that the number of
occupied BBU CPRI ports connected to RRUs is less than or equal to six.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Rectify the fault that the power of the RRU does not support the maximum TX power of the local cell
on the M2000.
a. Run the MML command DSP RRU to query the maximum output power of the RRU,
and run the MML command LST LOCELL to query the maximum TX power of the local
cell.
b. When the logical cell is established, check whether the maximum output power of the
RRU is smaller than the maximum TX power of the local cell.
Y => The maximum output power of the RRU is smaller than the maximum TX power of
the local cell. Go to sub-step c.
N => The maximum output power of the RRU is greater than or equal to the maximum
TX power of the local cell. Contact Huawei Customer Service Center.
c. Run the MML command RMV LOCELL to delete the other local cells on this RRU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
6. Rectify the fault that the local cell does not support two TX channels on the M2000.
c. Run the MML command LST LOCELL to query the cabinet/subrack/slot number of the
RRU configured for the local cell.
d. Run the MML command LST RRU to check whether the RRU for the local cell is
configured.
Y => The RRU is configured. Go to sub-step f.
N => The RRU is not configured. Go to sub-step e.
7. Rectify the fault that the local cell does not support uplink 16QAM on the M2000.
a. Check whether the capability of the local cell to support uplink 16QAM is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support uplink 16QAM.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink 16QAM license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
e. Run the MML command LST LOCELL to check the parameter "UL BB Resource Group
No." of the local cell. Then, run the MML command LST ULGROUP to query the
parameters "Cabinet No. of UL Process Unit", "Subrack No. of UL Process Unit", and
"Slot No. of UL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPd.
Y => The uplink resource group contains the WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPd. The configuration is
incorrect. Go to sub-step f.
f. Add the WBBPd. Then, run the MML command MOD ULGROUP to add the new
WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and uplink 16QAM cannot be supported. Go to
sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
8. Rectify the fault that the local cell does not support uplink L2+ on the M2000.
a. Check whether the capability of the local cell to support uplink L2+ is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support uplink L2+.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the uplink L2+ license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
e. Run the MML command LST LOCELL to check the parameter "UL BB Resource Group
No." of the local cell. Then, run the MML command LST ULGROUP to query the
parameters "Cabinet No. of UL Process Unit", "Subrack No. of UL Process Unit", and
"Slot No. of UL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPb or WBBPd.
Y => The uplink resource group contains the WBBPb or WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPb or WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
new WBBPb or WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
9. Rectify the fault that the local cell does not support downlink 64QAM+MIMO on the M2000.
a. Check whether the capability of the local cell to support downlink 64QAM+MIMO is
required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support downlink 64QAM+MIMO.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the downlink 64QAM+MIMO license-related alarms
exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPb or WBBPd.
Y => The uplink resource group contains the WBBPb or WBBPd. Go to sub-step g.
N => The uplink resource group does not contain the WBBPb or WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
new WBBPb or WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and downlink 64QAM+MIMO cannot be supported.
Go to sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new EBBC/EBBCd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
10. Rectify the fault that the local cell does not support FDE on the M2000.
a. Check whether the capability of the local cell to support FDE is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support FDE (checking that the local cell does not support
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the FDE license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
e. Run the MML command LST LOCELL to check the parameter "UL BB Resource Group
No." of the local cell. Then, run the MML command LST ULGROUP to query the
parameters "Cabinet No. of UL Process Unit", "Subrack No. of UL Process Unit", and
"Slot No. of UL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPd.
Y => The uplink resource group of the local cell contains the WBBPd. Go to sub-step g.
N => The uplink resource group of the local cell does not contain the WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPd. Then, run the MML command MOD ULGROUP to add the new
WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and FDE cannot be supported. Go to sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
11. Rectify the fault that the local cell does not support IC on the M2000.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support IC.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the IC license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
e. Run the MML command LST LOCELL to check the parameter "UL BB Resource Group
No." of the local cell. Then, run the MML command LST ULGROUP to query the
parameters "Cabinet No. of UL Process Unit", "Subrack No. of UL Process Unit", and
"Slot No. of UL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPd.
Y => The uplink resource group of the local cell contains the WBBPd. Go to sub-step g.
N => The uplink resource group of the local cell does not contain the WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPd. Then, run the MML command MOD ULGROUP to add the new
WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step h.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and IC cannot be supported. Go to sub-step i.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
12. Rectify the fault that the local cell does not support DC on the M2000.
b. Run the MML command RMV DLDUALCELLGRP to change the settings of the local
cell. Ensure that the local cell does not support DC.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the IC license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
e. Run the MML command LST LOCELL to query the information about the local cell.
Check whether the local cell is a distributed cell (a field "RRU Mode" is displayed in the
case of a distributed cell).
Y => The local cell is a distributed cell. Go to sub-step f.
N => The local cell is not a distributed cell. Go to sub-step h.
f. Run the MML command LST LOCELL to query the information about the local cell
(RRU configuration of the distributed cell: number of configured RRUs,
cabinet/subrack/slot number of the first RRU and last RRU). You need to check whether
the RRU configuration of the local cell is the same as that of the peer local cell.
Y => The RRU configuration of the local cell is the same as that of the peer local cell.
Go to sub-step h.
N => The RRU configuration of the local cell is different from that of the peer local cell.
Go to sub-step g.
g. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the RRU configurations of the two local cells in the DC group are the same.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step h.
h. Run the MML command LST LOCELL to query the information about the local cell
(uplink resource group number). Run the MML command LST ULGROUP to query the
uplink resource group used by the local cell. Query the uplink resource group used by
the local cell and the peer local cell respectively, and check whether the WBBPb or
WBBPd are configured in the uplink resource groups of both the two local cells.
Y => Yes. Go to sub-step j.
N => No. Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
new WBBPb or WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step j.
j. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step k.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and IC cannot be supported. Go to sub-step l.
k. Run the MML command DSP LOCELLRES to query the downlink resource
configuration of the local cell and the peer local cell respectively. Check whether the
downlink resources of the two local cells are established on the same WBBPb or
WBBPd.
Y => Yes. Contact Huawei Customer Service Center.
l. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
m. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
13. Rectify the fault that the local cell does not support BOOST
a. Check whether the capability of the local cell to support BOOST is required.
Y => The capability is required. Go to sub-step c.
N => The capability is not required. Go to sub-step b.
b. Run the MML command MOD LOCELL to change the settings of the local cell. Ensure
that the local cell does not support BOOST.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the BOOST license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
d. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step d.
e. Run the MML command LST LOCELL to check the parameter "UL BB Resource Group
No." of the local cell. Then, run the MML command LST ULGROUP to query the
parameters "Cabinet No. of UL Process Unit", "Subrack No. of UL Process Unit", and
"Slot No. of UL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the uplink resource group of the local cell contains the
WBBPd.
Y => The uplink resource group of the local cell contains the WBBPd. Go to sub-step g.
N => The uplink resource group of the local cell does not contain the WBBPd. The
configuration is incorrect. Go to sub-step f.
f. Add the WBBPd. Then, run the MML command MOD ULGROUP to add the new
WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
h. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step j.
N => Go to sub-step i.
i. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
j. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
14. Rectify the fault that the local cell does not support DC+MIMO.
b. Run the MML command MOD LOCELL to modify the cell configuration to ensure that
the local cell does not support DC+MIMO.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the DC+MIMO license-related alarms exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => The alarms exist. Go to sub-step d.
N => The alarms do not exist. Go to sub-step e.
e. Run the MML command DSP LOCELL to check whether the local cell supports MIMO.
Y => The local cell supports MIMO. Go to sub-step g.
Y => The local cell does not support MIMO. Go to sub-step f.
f. Rectify the fault that the local cell does not support 2-way transmit diversity by referring
to sub-step 6.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Run the MML command DSP LOCELL to check whether the local cell supports DC.
N=> The local cell supports DC. Contact Huawei Customer Service Center.
Y => The local cell does not support DC. Go to sub-step h.
h. Go to sub-step 12 to rectify the fault that the local cell does not support DC.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N=> The alarm is not cleared. Contact Huawei Customer Service Center.
15. Rectify the fault that the local cell does not support ERACH.
b. Run the MML command MOD LOCELL to modify the cell configuration to ensure that
the local cell does not support ERACH.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
c. Run the MML command DSP LOCELLRES to obtain parameters "Cabinet No. of UL
Process Unit", "Subrack No. of UL Process Unit", and "Slot No. of UL Process Unit".
Then, run the MML command DSP BRDMFRINFO to check whether uplink baseband
resources are established on the WBBPb or WBBPd.
Y => Uplink baseband resources are established on the WBBPb or WBBPd. Baseband
resources in the local cell are sufficient to support ERACH. Go to sub-step e.
N => Uplink baseband resources are not established on the WBBPb or WBBPd.
Baseband resources in the local cell are insufficient to support ERACH. Go to sub-step
d.
d. Add the WBBPb or WBBPd. Then, run the MML command MOD ULGROUP to add the
new WBBPb or WBBPd in the uplink resource group of the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step e.
e. Run the MML command LST LOCELL to check the parameter "DL BB Resource Group
No." of the local cell. Then, run the MML command LST DLGROUP to query the
parameters "Cabinet No. of DL Process Unit", "Subrack No. of DL Process Unit", and
"Slot No. of DL Process Unit" of each board. Run the MML command DSP
BRDMFRINFO to check whether the downlink resource group of the local cell contains
the WBBPb or WBBPd.
Y => The downlink resource group contains the WBBPb or WBBPd.Go to sub-step f.
N => The downlink resource group does not contain the WBBPb or WBBPd. The
baseband resource is insufficient and ERACH cannot be supported. Go to sub-step g.
f. Run the MML command DSP LOCELLRES to query the parameters "Dl BB Resource
Cabinet No.", "Dl BB Resource Subrack No.", and "Dl BB Resource Slot No.". Then, run
the MML command DSP BRDMFRINFO to check whether the downlink resource is
satisfied the local cells.
Y => Go to sub-step h.
N => Go to sub-step g.
g. Add the WBBPb or WBBPd. Then, run the MML command MOD DLGROUP add the
new WBBPb or WBBPd in the downlink resource group of the local cell. Run the MML
command STR REALLOCLOCELL to re-allocate cell resources. Note that this
command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
h. Run the MML command STR REALLOCLOCELL to re-allocate cell resources. Note
that this command interrupts all services of the NodeB.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
16. Remotely rectify the fault that baseband boards do not support Independent Demodulation of
Signals from Multiple RRUs in One Cell.
a. Run the MML command LST LOCELL to query the information about the local cell and
check the parameter "UL BB Resource Group No.". Run the MML command LST
ULGROUP to query the information about the uplink resource group used by the local
cell and check the following parameters of each board, ""Cabinet No. of UL Process
Unit", "Subrack No. of UL Process Unit", and "Slot No. of UL Process Unit". Then, run
the MML command DSP BRDMFRINFO to check whether the WBBPa is contained in
the uplink resource group used by the local cell.
Y =>The WBBPa is contained in the uplink resource group used by the local cell. Go to
sub-step b.
N => The WBBPa is not contained in the uplink resource group used by the local cell.
Contact Huawei Customer Service Center.
b. Run the MML command MOD ULGROUP to remove the WBBPa from the uplink
resource group used by the local cell. The WBBPa does not support Independent
Demodulation of Signals from Multiple RRUs in One Cell. It is recommended that the
WBBPa be replaced by the WBBPb or WBBPd or that the WBBPa is added to another
type of resource group.
Check whether the alarm is cleared.
17. Remotely rectify the fault that the local cell cannot use all available uplink baseband resources in the
uplink resource group.
a. If the NodeB uses over four baseband boards, check whether any of the following
alarms is reported on the board installed in slot 2 or 3:
Board software error alarm
board start failure alarm
board software activation failure alarm
board version mismatch alarm
board type mismatch alarm
board start alarm
If any of the preceding alarms is reported, clear the alarm by referring to related
handling suggestions. After the alarm is cleared, check whether "Specific Problem" is
"All available baseband resources in the uplink resource group cannot be used by the
cell". If the problem persists, Contact Huawei Customer Service Center.
18. Solve the problem remotely that the activation and deactivation capability for the supplementary
carrier of the local cell is not supported.
a. Check whether the local cell is required to support the activation and deactivation
capability for the supplementary carrier.
Y => Go to sub-step b.
N => Go to sub-step d.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether license-related alarms concerning activation and
deactivation for the supplementary carrier exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => Go to sub-step c.
N => Contact Huawei Customer Service Center.
d. Run the MML command SET MACHSPARA to modify the configuration so that the local
cell does not support the activation and deactivation capability for the supplementary
carrier.
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.
19. Solve the problem remotely that the local cell does not support the HSUPA anti-interference
scheduling capability.
a. Check whether the local cell is required to support the HSUPA anti-interference
scheduling capability.
Y => Go to sub-step b.
N => Go to sub-step d.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether license-related alarms concerning HSUPA
anti-interference scheduling exist.
26811 Configured Capacity Limit Exceeding Licensed Limit
Y => Go to sub-step c.
N => Contact Huawei Customer Service Center.
d. Run the MML command SET MACEPARA to modify the configuration so that the local
cell does not support HSUPA anti-interference scheduling.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
20. Rectify the fault that the local cell does not support DC-HSUPA on the M2000
d. Run the MML command RMV ULDUALCELLGRP to modify the configuration so that
the local cell does not support DC-HSUPA.
Check whether the alarm is cleared.
Y =>The alarm is cleared. No further action is required.
N =>The alarm is not cleared. Contact Huawei Customer Service Center.
a. Run the MML command DSP CPRILBR to check whether the line rate of the RRU chain
meets the networking requirement.
Y => The line rate of the RRU chain meets the networking requirement. Go to sub-step
b.
N => The line rate of the RRU chain does not meet the networking requirement. Go to
sub-step c.
b. Query the carrier configuration for UMTS cells and the carrier configurations for cells of
other systems that share CPRI bandwidths with the UMTS cells. Check whether the
carrier configuration exceeds the maximum typical configuration by referring to the
specifications of the MBTS CPRI networking in the 3900 Series Base Station Technical
Description.
Y => The carrier configuration exceeds the maximum typical configuration. Go to
sub-step d.
N => The carrier configuration does not exceed the maximum typical configuration.
Contact Huawei Customer Service Center.
c. Check the maximum configuration at each level in the MML command execution result,
and change the optical modules whose rates do not match.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
d. Adjust the base station configuration based on the specifications of the MBTS CPRI
networking in the 3900 Series Base Station Technical Description.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
When the power sharing among carriers is configured, this alarm is reported if the logical cell does not meet the
power sharing requirements.
Parameters
Parameter
Name Parameter Description
Cause (The source cell is not R99 cell, The target cell is not DPA cell, License capability not support,
Source and target cells use different antennas)
Minor The target cell cannot share the power of the source cell, and the HSDPA services
of the target cell fail to expand.
System Actions
None
Possible Causes
The source cell of the power sharing group is not an R99 cell.
The HSDPA services are not enabled within 10 minutes after the target logical cell in the power
sharing group is established.
Procedure
2. Check that the HSDPA services are disabled in the source cell.
a. On the RNC, run the MML command LST UCELLHSDPA and check whether the query
result contains the information about the source cell.
Y => The query result contains the information about the source cell. Go to sub-step b.
N => The query result does not contain the information about the source cell. Contact
Huawei Customer Service Center.
b. On the RNC, run the MML command LST UCELLHSDPA to check whether the status
of the HSDPA services is ACTIVATED.
Y => The status of the HSDPA services is ACTIVATED. Go to sub-step c.
N => The status of the HSDPA services is not ACTIVATED. Contact Huawei Customer
Service Center.
c. On the RNC, run the MML command DEA UCELLHSDPA to disable the HSDPA
services of the source cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Check that the HSDPA services are enabled in the target cell.
a. On the RNC, run the MML command LST UCELLHSDPA and check whether the query
result contains the information about the target cell.
Y => The query result contains the information about the target cell. Go to sub-step b.
N => The query result does not contain the information about the target cell. Go to
sub-step c.
b. On the RNC, run the MML command LST UCELLHSDPA to check whether the status
of the HSDPA services is DEACTIVATED.
Y => The status of the HSDPA services is DEACTIVATED. Go to sub-step d.
N => The status of the HSDPA services is not DEACTIVATED. Contact Huawei
Customer Service Center.
c. On the RNC, run the MML command ADD UCELLHSDPA to add the HSDPA services
for the target cell.
d. On the RNC, run the MML command ACT UCELLHSDPA to enable the HSDPA
services for the target cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Run the MML command DSP LICENSE on the LMT to check whether the license
supports power sharing.
Y => The license supports power sharing. Contact Huawei Customer Service Center.
N => The license does not support power sharing. Go to sub-step b.
b. Configure a new license for the NodeB on the M2000 side. For details, see the online
help of ALM-26811 Configured Capacity Limit Exceeding Licensed Limit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Run the MML command LST LOCELL on the LMT to query the cell carrier information.
Check whether the source and target cells have the same settings of transmit channels.
Y => Same. Go to sub-step h.
N => Different. Go to sub-step b.
b. On the RNC, run the MML command DEA UCELL to deactivate the cell.
c. Run the MML command RMV PAGRP to remove the power sharing relationship
between the original cell and target cell.
d. Run the MML command RMV LOCELL to remove the original cell and target cell
respectively.
e. Run the MML command ADD LOCELL to add the source cell and target cell
respectively, in which the TX channels for carriers of the source cell and target cellmust
be consistent.
f. Run the MML command ADD PAGRP to add the power sharing relationship between
the source cell and target cell.
g. On the RNC, run the MML command ACT UCELL to activate the cell.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step h.
h. Run the MML command LST LOCELL on the LMT to check whether the source and
target cells have the same settings of transmit diversity.
Y => Same. Contact Huawei Customer Service Center.
N => Different. Go to sub-step i.
i. Run the MML command MOD LOCELL on the LMT to modify the settings of transmit
diversity so that the source and target cells have the same settings of transmit diversity.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when no traffic is detected in the local cell during the specified period of time or when
there is no cell traffic because the KPI values indicating the corresponding logical cell access are abnormal.
Parameters
Parameter
Name Parameter Description
Cause (Cell No Receive Radio link Setup Message, Cell No Receive Radio link Setup Message with
First Rls Flag for Long Time, Baseband Uplink Channel Soft Fault, Downlink Baseband
Resource Fault, High Error Rate of IUB Transmission, Radio link Setup Fail, Others)
Minor Services of the current cell are affected and system self-healing fails.
System Actions
None
Possible Causes
A third-party device, such as the antenna system, TMA, trunk amplifier, or transmission relay, is
faulty.
The parameter settings for the cell are incorrect on the NodeB or RNC.
On occasions such as public holidays or termination of large-scale gatherings, this alarm may be
reported with the alarm cause 0 or 1.
Procedure
a. If the alarm 26200 Board Hardware Fault or 26532 RF Unit Hardware Fault is reported,
go to step 3.
b. If the 26203 Board Software Program Error or 26533 RF Unit Software Program Error
is reported, go to step 4.
3. On the M2000, check the type and status of the board where the correlated hardware alarm is
reported.
a. Run the MML command DSP BRD on the M2000 to display the type of the board
where the alarm is reported. Check whether the displayed board type is an RF board
and the MML command RST BRDPWROFF has not been executed on the RF board
within 2 hours before the alarm was reported.
Y => Run the MML command RST BRDPWROFF on the M2000 to power cycle the RF
b. Replace the faulty board onsite. Check whether the cell becomes functional onsite.
Y => The cell becomes functional. No further action is required.
N => The cell still has no traffic. Contact Huawei Customer Service Center.
a. Check whether the board has been reset within 2 hours before the alarm was initially
reported.
Y => Go to step 6.
N => Reset the board. No further action is required.
a. Check whether the alarm cause is 0 (Radio Link Setup messages not received within a
long period) or 1 (Radio Link Setup messages with the First Rls flag not received within
a long period).
Y => The alarm cause is 0 or 1. Go to step 7.
N => The alarm cause is not 0 or 1. Go to step 6.
a. Check whether the NodeB has been reset within 2 hours before the alarm was initially
reported.
Y => Contact Huawei Customer Service Center..
N => Reset the NodeB. No further action is required.
a. On the M2000, confirm with the network planning engineers whether the alarm is
reported on occasions such as holidays or termination of large-scale gatherings.
Y => No further action is required.
N => Go to substep b.
b. On the M2000, confirm with the network planning engineers whether the parameter
settings of the cell have been adjusted.
Y => Request the network planning engineers to perform further actions.
N => Contact Huawei Customer Service Center.
When a logic cell is established, this alarm is reported if the system detects that the frequency separation
between the frequency of the cell to be established and the frequency of the existing cell carried by the RF unit
is less than the parameter "Frequency Bandwidth" of the RF unit.
Parameters
Minor The services carried by the cell configured with incorrect frequency separation may
be affected. In this case, the KPIs related to network performance may deteriorate.
System Actions
None
Possible Causes
Procedure
a. On the NodeB side, run the MML command LST LOCELL to query the parameters "UL
Frequency Channel Number" and "DL Frequency Channel Number" of the local cell that
is carried by the RF unit with incorrect frequency configuration. Check whether the cell
frequency configuration is consistent with the network planning.
Y => The cell frequency configuration is consistent with the network planning. Go to
step 2.
N => The cell frequency configuration is inconsistent with the network planning. Go to
sub-step b.
b. On the NodeB side, run the MML command DSP LOCELL to query the ID of the logic
cell corresponding to the local cell that is carried by the RF unit with incorrect frequency
configuration.
c. On the RNC side, run the MML command DEA UCELL to deactivate the logic cell.
Then, run the MML command MOD UCELLFREQUENCY to change the cell
frequencies. Ensure that the frequency configuration is consistent with the network
planning.
d. On the NodeB side, run the MML command MOD LOCELL to change the frequencies
of the local cell. Ensure that the frequency configuration is consistent with the network
planning.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command LST FREQBWH to query the parameter "Frequency
Bandwidth" of the RF unit. Check whether the cell frequency separation of the RF unit is
b. Run the MML command DSP LICENSE to check whether "Flexible frequency
separation between G/U" is supported.
Y => "Flexible frequency separation between G/U" is supported. Go to sub-step c.
N => "Flexible frequency separation between G/U" is not supported. Purchase and
activate the license. Then, go to sub-step c.
c. Run the MML command SET FREQBWH to modify the parameter "Frequency
Bandwidth" of the RF unit. Ensure that the cell frequency separation of the RF unit is
greater than or equal to the parameter "Frequency Bandwidth" of the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the uplink or downlink ARFCN fails to be configured or the total maximum transmit
power of all local cells on an RF unit exceeds the maximum transmit power of the RF unit.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Uplink Frequency Configured Failure, Downlink Frequency
Problem Configured Failure, Cell Power Exceeded RF Unit Power Specification)
Major If the uplink or downlink frequency configuration fails, services cannot be connected.
If the total cell power exceeds the RF unit specifications, KPIs deteriorate when the
logical cell is operating under heavy traffic. In serious scenarios, the power amplifier
will be damaged.
System Actions
None.
Possible Causes
The RF unit which carries the services in the local cell does not support the uplink or downlink
ARFCN of the local cell.
The uplink and downlink ARFCNs of the local cell conflict with ARFCNs of a cell in another mode.
The total maximum transmit power of faulty local cells and other local cells exceeds the maximum
Procedure
2. Remotely check whether the RF unit used by the sector supports the ARFCNs configured in the
local cell.
a. Run the MML command LST LOCELL to query the information about the uplink and
downlink ARFCNs configured in the local cell.
b. Run the MML command DSP TXBRANCH and DSP RXBRANCH to query the maximum
and minimum ARFCNs supported by the RF unit in the uplink and downlink.
c. Check whether the uplink and downlink ARFCNs configured in the local cell are within
the allowed ARFCN range of the RF unit.
Y => Both the uplink and downlink ARFCNs are in the allowed ARFCN range of the RF
unit. Contact Huawei Customer Service Center.
N => The uplink or downlink ARFCN is not in the allowed ARFCN range of the RF unit.
Go to step 3.
3. Remotely check whether the uplink or downlink ARFCN is consistent with that in network planning.
a. Check whether the uplink or downlink ARFCN is consistent with that in network planning.
Y => Both the uplink and downlink ARFCNs are consistent with those in network
planning. Go to sub-step b.
N => Either the uplink or downlink ARFCN is inconsistent with that in network planning.
Go to step 4.
4. Remotely modify the uplink or downlink ARFCN configured in the local cell.
a. Run the MML command DEA UCELL on the RNC side to deactivate the logical cell
corresponding to the local cell.
b. Run the MML command MOD LOCELL on the NodeB side to modify the uplink or
downlink ARFCN configured in the local cell to ensure that both the uplink and downlink
ARFCNs are consistent with those in network planning.
c. Run the MML command MOD UCELLFREQUENCY on the RNC side to modify the
uplink or downlink ARFCN to ensure that the uplink and downlink ARFCNs configured in
the logical cell are consistent with those configured in the local cell.
d. Run the MML command ACT UCELL on the RNC side to activate the logical cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Check that the maximum transmit power of the local cell conforms to the network plan on the
M2000.
a. Run the MML command LST LOCELL to query the maximum transmit power of the
faulty local cell.
b. Check whether the maximum transmit power of the local cell conforms to the network
plan.
Note: For a multi-mode RF unit, the maximum transmit power is shared by multiple
modes. If multiple local cells share the transmit channel of one RF unit, the power of the
transmit channel is shared by the local cells. The maximum transmit power of the RF
unit may be restricted to the hardware and the power lock of the RF unit.
Y => The maximum transmit power of the local cell conforms to the network plan. Go to
step 7.
N => The maximum transmit power of the local cell does not conform to the network
plan. Go to step 6.
6. Change the maximum transmit power of the local cell based on the network plan on the M2000.
a. For a cell that has been activated, run the MML command DEA UCELL on the RNC to
deactivate the cell.
b. On the NodeB, run the MML command MOD LOCELL to change the information about
the maximum transmit power of the local cell to ensure that the total maximum transmit
power of all local cells on a transmit channel of an RF unit does not exceed the
maximum transmit power of the RF unit. In addition, the maximum transmit power of the
local cell cannot be smaller than the transmit power specified in the network plan.
c. On the RNC, run the MML command MOD UCELL to change the cell power information
to ensure that the maximum transmit power conforms to the network plan and the
power does not exceed the maximum transmit power of the local cell.
d. On the RNC, run the MML command ACT UCELL activate the cell.
Check whether the alarm is cleared.
Y => The alarm is cleared and is not reported again. No further action is required.
N => The alarm is not cleared or is reported again. Contact Huawei Customer Service
Center.
7. Replace the original RF unit with an RF unit with the larger maximum transmit power onsite.
a. Replace the original RF unit with an RF unit with the larger maximum transmit power to
ensure that the total maximum transmit power of all local cells on a transmit channel of
an RF unit does not exceed the maximum transmit power of the RF unit.
Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
The user can restrict the RNC from using a certain resource or all IMB(Integrated Mobile Broadcast) local cell
resources by blocking local cells. This alarm is reported when IMB local cells are blocked.
Parameters
Minor When a IMB local cell is blocked, the cell cannot carry services.
System Actions
None
Possible Causes
The user runs a command to block the IMB local cell of the NE.
Procedure
a. Run the MML command UBL LOCELL to block the local cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the system detects that a IMB(Integrated Mobile Broadcast) local cell is
unavailable.
Parameters
Parameter
Name Parameter Description
System Actions
None
Possible Causes
Procedure
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the downlink-related alarms of the WBBP exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28301 Board Downlink Service Processing Channel Abnormal
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step c.
c. Run the MML command LST IMBLOCELL to query the IMB local cell information ("DL
BB Resource Group No."), and then run the MML command LST DLGROUP to query
the information about the downlink resource group used by the IMB local cell.
d. Run the MML command DSP BBPTC to query the number of cells supported by the
board in the downlink resource group.
e. Check whether the number of cells configured in the downlink resource group exceeds
the total number of cells allowed by the downlink resource group. The total number of
cells allowed by the downlink resource group is the accumulated value of the number of
cells supported by all boards in the downlink resource group and cannot exceed the
maximum number of cells allowed by the downlink resource group. For details about the
cell specification supported by the board, see the related hardware description.
Y => The number of cells configured for the downlink resource group exceeds the total
number of cells supported by the downlink resource group. Go to sub-step f.
N => The number of cells configured for the downlink resource group does not exceed
the IMB total number of cells supported by the downlink resource group. Contact
Huawei Customer Service Center.
a. Run the MML command LST IMBLOCELL to query the information about the RRU
configured for the IMB local cell, and then run the MML commands LST RRU and LST
RRUCHAIN to query the information about the interface board configured for the RRU.
b. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the interface board-related alarms exist.
26106 Board Clock Input Unavailable
26200 Board Hardware Fault
26201 Board Memory Soft Failure
26204 Board Not In Position
26205 BBU Board Maintenance Link Failure
26210 Board Blocked
26264 System Clock Unlocked
26265 Base Station Frame Number Synchronization Error
28302 Board BFN Abnormal
28303 WBBP-WBBP Interface Abnormal
28381 Board Startup Abnormal Alarm
Y => The alarms exist. Go to sub-step c.
N => The alarms do not exist. Contact Huawei Customer Service Center.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms to determine whether the alarms related to the RRU or RFU exist.
26210 Board Blocked
26235 RF Unit Maintenance Link Failure
26237 RRU Network Breakpoint
26524 RF Unit PA Overcurrent
26525 RF Unit Temperature Unacceptable
26529 RF Unit VSWR Threshold Crossed
26532 RF Unit Hardware Fault
26538 RF Unit Clock Problem
26545 RF Unit TX Channel Switched Off Through Command
26765 RHUB Hardware Fault
26768 RHUB Clock Problem
Y => The alarms exist. Go to sub-step b.
N => The alarms do not exist. Go to sub-step c.
c. Run the MML command LST IMBLOCELL to query the information about the IMB local
cell, such as the RRU or RFU used in the local cell, uplink and downlink UARFCNs, and
maximum output power.
d. Run the MML command DSP RRU to query the specifications of the RRU or RFU.
e. Check whether the u downlink frequencies configured in the local cell are within the
permissible frequency range of the RRU or RFU. (The conversion formula between
UARFCNs and actual frequencies is available in the help information of the MML
command ADD IMBLOCELL.)
Y => Go to sub-step g.
N => Go to sub-step f.
f. Run the MML command MOD IMBLOCELL to change the frequency of the local cell to
a value within the frequency range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step g.
g. Check whether the frequency spacing between the current IMB local cell and any of the
other IMB local cells established on the RRU or RFU exceeds the allowed bandwidth of
the RRU or RFU (Minimum frequency spacing = 3.8 MHz; Maximum downlink frequency
spacing = TxUnitNo 0 Support Band Width - 3.8 MHz).
Y => The frequency spacing between the current IMB local cell and any of the other
IMB local cells established on the RRU or RFU exceeds the allowed bandwidth of the
RRU or RFU. Go to sub-step h.
N => The frequency spacing between the current IMB local cell and any of the other
IMB local cells established on the RRU or RFU does not exceed the allowed bandwidth
of the RRU or RFU. Go to sub-step i.
h. Run the MML command MOD IMBLOCELL to modify the frequency of the IMB local
cell to ensure that its frequency spacing with the other cells is within the range
supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step i.
i. Check whether the number of cells configured on the same RRU or RFU exceeds the
number of carriers supported by the RRU/RFU.
Y => The number of cells configured on the same RRU or RFU exceeds the number of
carriers supported by the RRU or RFU. Go to sub-step j.
N => The number of cells configured on the same RRU or RFU does not exceed the
number of carriers supported by the RRU or RFU. Go to sub-step k.
j. Run the MML command RMV IMBLOCELL to delete the IMB local cell whose
resources are unavailable, and then run the MML command ADD IMBLOCELL to
establish a IMB local cell on another resource group that has sufficient resources.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step k.
k. Check whether the maximum power configured in the IMB local cell is within the power
range supported by the RRU or RFU.
Y => The maximum power configured in the IMB local cell is out of the power range
supported by the RRU or RFU. Go to sub-step l.
N => The maximum power configured in the IMB local cell is within the power range
supported by the RRU or RFU. Go to sub-step m.
l. Run the MML command MOD IMBLOCELL to change the maximum transmit power of
the IMB local cell to a value within the power range supported by the RRU or RFU.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step m.
m. Run the MML command LST RRU to obtain the information about the RRU or RFU
configured on the same chain/ring. Run the MML command LST IMBLOCELL to obtain
the number of cells configured for the same RRU or RFU. Run the MML command DSP
SFP to obtain the transmission rate of the optical module. If the transmission rate is
1.25 Gbit/s, the CPRI interface supports only 8 IMB local cells. If the transmission rate
is 2.5 Gbit/s, the CPRI interface supports only 16 IMB local cells . Check whether the
allowed number of local cells on a chain/ring exceeds the number of IMB local cells
corresponding to the transmission rate on the chain/ring.
Y => The allowed number of local cells on a chain/ring exceeds the number of IMB local
cells corresponding to the transmission rate on the chain/ring. Go to sub-step n.
N => The allowed number of local cells on a chain/ring does not exceed the number of
IMB local cells corresponding to the transmission rate on the chain/ring. Contact Huawei
Customer Service Center.
n. Run the MML command RMV IMBLOCELL to delete the IMB local cell whose
resources are unavailable, and then run the MML command ADD IMBLOCELL to
establish a IMB local cell on another RRU or RFU that has sufficient resources on the
chain/ring.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step o.
o. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 5.
This alarm is reported when the output power of an NE is at least 2 dB lower than the sum of the common
channel power configured by the RNC.
Parameters
Minor The decrease in the NE output power causes a reduction in the cell coverage.
System Actions
None
Possible Causes
Procedure
a. Run the MML command RST BRD to reset the RRU. Then, wait for 15 minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is reported again. Go to step 2.
Parameters
Parameter
Name Parameter Description
Cause (Some RRU(s) in the iDBS cell not usable, Number of occupied BBU CPRI ports connected to
RRUs in the iDBS cell exceeding six, RRU transmit power less than the transmit power required
by the local cell, Two TX channels not supported by the cell, Uplink 16QAM not supported by the
cell, Uplink L2+ not supported by the cell, Downlink 64QAM+MIMO not supported by the cell,
FDE not supported by the cell, IC not supported by the cell, DC not supported by the cell,
BOOST not supported by the cell, DCMIMO not supported by the cell, ERACH not supported by
the cell, MultiRRU Independ DemOver Cell not supported by WBBP Board, Cell can't use all
WBBP Board resources of the uplink resource group, ACT and DEA of Slave Carrier not
supported by the cell, Anti-Interference Scheduling for HSUPA not supported by the cell)
Major The coverage of the faulty local cell decreases, the RTWP reported by some RRUs
is discarded, the features configured on the local cell are not supported, or certain
demodulation capabilities of the uplink resource group used by the local cell are
unavailable.
System Actions
None
Possible Causes
The number of occupied BBU CPRI ports connected to RRUs in the IMB local cell exceeds six, the
maximum number defined in the system.
A logical cell exists, and the maximum TX power of the IMB local cell exceeds the maximum output
power of RRUs.
Procedure
2. Check for redundant RRUs configured in the local cell on the M2000.
a. Run the MML command LST IMBLOCELL to check the RRUs configured in the faulty
IMB local cell. Check whether redundant RRUs exist according to the network planning.
Y => Redundant RRUs exist. Go to sub-step b.
N => Redundant RRUs do not exist. Go to step 3.
b. Run the MML command RMV RRU to delete the redundant RRUs.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
a. Open the alarm browsing window or run the MML command LST ALMAF to check for
active alarms. Check whether the RRUs configured in the faulty local cell are faulty.
Y => The RRUs are faulty. Go to sub-step b.
N => The RRUs are functional. Contact Huawei Customer Service Center.
b. Clear the correlated alarm according to the relevant handling suggestions.
4. Rectify the fault that the number of occupied BBU CPRI ports connected to RRUs in the cell
exceeds six on the M2000.
a. Run the MML command LST IMBLOCELL to query all the RRUs configured in the
current IMB local cell. Check whether the number of occupied BBU CPRI ports
connected to RRUs exceeds six.
Y => The number of occupied BBU CPRI ports connected to RRUs exceeds six. Go to
sub-step b.
N => The number of occupied BBU CPRI ports connected to RRUs does not exceed
six. Contact Huawei Customer Service Center.
b. Reconfigure the position or number of RRUs in the IMB local cell. Ensure that the
number of occupied BBU CPRI ports connected to RRUs is less than or equal to six.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Rectify the fault that the power of the RRU does not support the maximum TX power of the local cell
on the M2000.
a. Run the MML command DSP RRU to query the maximum output power of the RRU,
and run the MML command LST IMBLOCELL to query the maximum TX power of the
IMB local cell.
b. When the logical cell is established, check whether the maximum output power of the
RRU is smaller than the maximum TX power of the IMB local cell.
Y => The maximum output power of the RRU is smaller than the maximum TX power of
the IMB local cell. Go to sub-step c.
N => The maximum output power of the RRU is greater than or equal to the maximum
TX power of the local cell. Contact Huawei Customer Service Center.
c. Run the MML command RMV IMBLOCELL to delete the other local cells on this RRU.
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.
This alarm is reported when the uplink or downlink ARFCN fails to be configured or the total maximum transmit
power of all local cells on an RF unit exceeds the maximum transmit power of the RF unit.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Uplink Frequency Configured Failure, Downlink Frequency
Problem Configured Failure, Cell Power Exceeded RF Unit Power Specification)
System Actions
None.
Possible Causes
The RF unit which carries the services in the IMB(Integrated Mobile Broadcast) local cell does not
support the uplink or downlink ARFCN of the local cell.
The uplink and downlink ARFCNs of the local cell conflict with ARFCNs of a cell in another mode.
The total maximum transmit power of faulty local cells and other local cells exceeds the maximum
transmit power of the RF unit.
Procedure
2. Remotely check whether the RF unit used by the sector supports the ARFCNs configured in the IMB
local cell.
a. Run the MML command LST IMBLOCELL to query the information about the sector to
which the IMB local cell belongs and information about the uplink and downlink ARFCNs
configured in the IMB local cell.
b. Run the MML command LST IMBSEC to query the configuration information of the RF
unit used by the sector.
c. Run the MML command DSP TXBRANCH to query the maximum and minimum
ARFCNs supported by the RF unit in the downlink.
d. Check whether the downlink ARFCNs configured in the IMB local cell are within the
allowed ARFCN range of the RF unit.
Y => Both the downlink ARFCNs are in the allowed ARFCN range of the RF unit.
Contact Huawei Customer Service Center.
N => The downlink ARFCN is not in the allowed ARFCN range of the RF unit. Go to
step 3.
3. Remotely check whether the uplink or downlink ARFCN is consistent with that in network planning.
a. Check whether the downlink ARFCN is consistent with that in network planning.
Y => Both the downlink ARFCNs are consistent with those in network planning. Go to
sub-step b.
N => Either the downlink ARFCN is inconsistent with that in network planning. Go to
step 4.
4. Remotely modify the uplink or downlink ARFCN configured in the local cell.
a. Run the MML command DEA UCELL on the RNC side to deactivate the logical cell
corresponding to the local cell.
b. Run the MML command MOD IMBLOCELL on the NodeB side to modify the downlink
ARFCN configured in the IMB local cell to ensure that both the downlink ARFCNs are
consistent with those in network planning.
c. Run the MML command MOD IMBLOCELL on the RNC side to modify the downlink
ARFCN to ensure that the downlink ARFCNs configured in the logical cell are consistent
with those configured in the IMB local cell.
d. Run the MML command ACT UCELL on the RNC side to activate the logical cell.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Check that the maximum transmit power of the local cell conforms to the network plan on the
M2000.
a. Run the MML command LST LOCELL to query the maximum transmit power of the
faulty local cell.
b. Check whether the maximum transmit power of the local cell conforms to the network
plan.
Note: For a multi-mode RF unit, the maximum transmit power is shared by multiple
modes. If multiple local cells share the transmit channel of one RF unit, the power of the
transmit channel is shared by the local cells. The maximum transmit power of the RF
unit may be restricted to the hardware and the power lock of the RF unit.
Y => The maximum transmit power of the local cell conforms to the network plan. Go to
step 7.
N => The maximum transmit power of the local cell does not conform to the network
plan. Go to step 6.
6. Change the maximum transmit power of the local cell based on the network plan on the M2000.
a. For a cell that has been activated, run the MML command DEA UCELL on the RNC to
deactivate the cell.
b. On the NodeB, run the MML command MOD LOCELL to change the information about
the maximum transmit power of the local cell to ensure that the total maximum transmit
power of all local cells on a transmit channel of an RF unit does not exceed the
maximum transmit power of the RF unit. In addition, the maximum transmit power of the
local cell cannot be smaller than the transmit power specified in the network plan.
c. On the RNC, run the MML command MOD UCELL to change the cell power information
to ensure that the maximum transmit power conforms to the network plan and the
power does not exceed the maximum transmit power of the local cell.
d. On the RNC, run the MML command ACT UCELL activate the cell.
Check whether the alarm is cleared.
Y => The alarm is cleared and is not reported again. No further action is required.
N => The alarm is not cleared or is reported again. Contact Huawei Customer Service
Center.
7. Replace the original RF unit with an RF unit with the larger maximum transmit power onsite.
a. Replace the original RF unit with an RF unit with the larger maximum transmit power to
ensure that the total maximum transmit power of all local cells on a transmit channel of
an RF unit does not exceed the maximum transmit power of the RF unit.
Replace the RF unit.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This alarm is reported when the ratio of the number of times the system cannot provide services to the number
of connection attempts is higher than the preset threshold (10% by default).
Parameters
None.
Minor The hardware capability is insufficient. Some terminals cannot use the services
provided by the network.
System Actions
None
Possible Causes
The NodeB receives calls too frequently and its signaling capability cannot handle.
The NodeB serves too many online users and its hardware cannot provide adequate uplink or
downlink CEs.
Procedure
a. Run the MML command LST TRAFFICOVERLOADTHD to query the service overload
alarm threshold.
Check whether the service overload alarm threshold is set properly.
Y=> The service overload alarm threshold is set properly. Contact Huawei Customer
Service Center to implement capacity expansion.
N=> The service overload alarm threshold is not set properly. Go to step 2.
a. Run the MML command SET TRAFFICOVERLOADTHD. Set the service overload
alarm threshold based on service characteristics.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center to implement
capacity expansion.
The alarm is reported when the system detects that the hardware of the GPS receiver is faulty.
Parameters
Minor The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
Procedure
a. Run the MML command RST SATCARD to reset the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
The alarm is reported when the system detects that the antenna of the GPS receiver is not powered on.
Parameters
Minor The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The power supply loop of the antenna of the GPS receiver is faulty.
Procedure
1. Wait for five minutes, and then check that the system can automatically clear the alarm.
a. Wait for five minutes. Then, check whether the system automatically clears the alarm.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command RST SATCARD to reset the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
The alarm is reported when the antenna system between the NodeB and the GPS receiver is faulty.
Parameters
Minor The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
The antenna system of the GPS receiver is not properly connected or is short-circuited.
Procedure
a. Locate the cause of the alarm based on the alarm location information.
If "Specific Problem" is "Antenna Shorted", go to step 2.
If "Specific Problem" is " Antenna Open", go to step 4.
2. Disconnect the antenna system from the GPS receiver on site, and then wait for five minutes to
check that the alarm is cleared.
a. Disconnect the feeder at the antenna connector of the GPS receiver, and then wait for
five minutes.
Check whether the alarm is cleared.
Y => The alarm is cleared. The antenna system is faulty. Go to step 3.
N => The alarm is not cleared. The GPS receiver itself is faulty. Go to step 6.
a. Check the antenna system. Clear the fault of short circuit if any.
4. Check that the antenna system is properly connected to the GPS receiver on site.
a. Check whether the antenna system is properly connected to the GPS receiver.
Reconnect the antenna system if necessary.
Check 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.
a. Run the MML command RST SATCARD to reset the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 7.
a. Run the MML command RST SATCARD to reset the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. Reconnect the antenna system to the GPS receiver. The
alarm handling is complete.
N => The alarm is not cleared. Go to step 7.
The alarm is reported when the system detects that the software program error occurs in the GPS receiver.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Position Solution Invalid, Clock Steering Disabled, Clock Model
Problem Invalid, Almanac Invalid)
Minor The GPS receiver fails to receive information from the satellite. The NodeB fails to
provide the GPS data for the RNC.
System Actions
None
Possible Causes
Procedure
1. Wait for five minutes, and then check that the system can automatically clear the alarm.
a. Wait for five minutes. Then, check whether the system automatically clears the alarm.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command RST SATCARD to reset the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
This alarm is reported when the GPS receiver is searching for a satellite or cannot automatically search for a
satellite.
Parameters
Minor The GPS receiver cannot lock the satellite. The NodeB fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
Procedure
1. Check that the GPS receiver is automatically searching for a satellite on the M2000.
a. Run the MML command LST GPS to list the preset search duration of the GPS
receiver.
Wait for some time. Then, check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command RST SATCARD to reset the GPS receiver.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 3.
b. Keep waiting for the time one hour longer than the preset search duration, or three
times longer than the typical duration specified for SEARCH_WITH_PRECISION.
The alarm is reported when the communication between the NodeB and the GPS receiver fails.
Parameters
Minor The NodeB cannot receive the valid GPS data and thus fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
The cable connections between the NodeB and the GPS receiver are faulty.
Procedure
1. Check that the GPS receiver is properly connected to the NodeB on site.
a. Check whether the GPS receiver is properly connected to the NodeB. If necessary,
reconnect the cables properly between the NodeB and the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to sub-step b.
b. Replace the cables between the NodeB and the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
The NodeB performs the initialization configuration on the GPS receiver. This alarm is reported when the GPS
receiver fails to respond or responds unexpectedly upon receiving the controlling message from the NodeB.
Parameters
Minor The NodeB cannot receive the valid GPS data and thus fails to provide the GPS data
for the RNC.
System Actions
None
Possible Causes
Procedure
a. Run the MML command RST SATCARD to reset the GPS receiver.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
You can test the connectivity of the NodeB. This alarm is reported if the connectivity test is unsuccessful.
Parameters
Major The transmission link is disconnected, and the ongoing services carried on the link
are disrupted.
System Actions
Possible Causes
Procedure
a. Check for the correlated alarm of the faulty board on the M2000:
25880 Ethernet Link Fault
25895 Ethernet Trunk Group Fault
Y => The correlated alarm exists. Go to sub-step b.
N => The correlated alarm does not exist. Go to step 2.
b. Clear the correlated alarm according to the relevant handling suggestions.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
a. Run the MML command CFMTRACE to perform a loopback test at the ends of the
disconnected link and check whether the loopback test is successful.
Y => The test is successful. Contact the maintenance personnel of the transport
network.
N => The test fails. Go to sub-step b.
b. Contact the maintenance personnel of the transport network to obtain the networking
configuration, and then run the MML command CFMTRACE to perform a loopback test
at the ends of the disconnected link and NodeB and check whether each
MIP(Maintenance Intermediate Point).
Y => All the MIPs are reachable. Contact Huawei Customer Service Center.
N => Certain MIPs are unreachable. Contact the maintenance personnel of the
transport network.
This alarm is reported when the system detects that one transport object cannot be configured to the board and
therefore the configuration data cannot take effect.
Parameters
Parameter
Name Parameter Description
Transmission (Ethernet Port, Device IP Address, IP Path, Local IP, OM Channel, IP Route, E1/T1,
Object Type Resource Group, PPP Link, MLPPP Group, MLPPP Link, IP PM Session, IMA Group, IMA
Link, AAL2 Node, AAL2 Path, VCG, SAAL Link, Ethernet Trunk Group, SCTP Link, UNI Link,
Tree Link PVC, Fractional ATM Link, IP to Resource Group Mapping, Line Rate, HSDPA Flow
Control Para, Ethernet Trunk Link, BFD Session, CFM MA, CFM MEP, CFM Remote MEP,
CFM Binding IP, Timeslot Cross, STM-1, HSUPA Flow Control Para, CFM MD, TUNNEL,
Service IP)
Major The transport object for which this alarm is generated is unavailable and the ongoing
services carried on the transport object are disrupted.
System Actions
Possible Causes
Procedure
2. Check for this alarm in the lower layer objects of the bearer object on the M2000.
a. Determine whether the faulty object belongs to the following types: AAL2 path, device
IP address, Fractional ATM link, IMA link, IP path, PPP link, SAAL link, SCTP link,
structured CES channel, networking PVC, time slot cross, non-structured CES channel,
UNI link, transmission resource group, IP clock switch, IP clock link, AAL2 node, AAL2
adjacent node,and Trunk link.
Y => The faulty object belongs to one of the preceding types. Go to sub-step b.
N => The faulty object does not belong to these types. Go to step 3.
b. Run the MML command LST ALMAF to check whether this alarm is generated on the
lower layer object that carries the faulty object.
Y => The alarm is generated on the lower layer object that carries the faulty object. Go
to sub-step c
Y => The alarm is not generated on the lower layer object that carries the faulty object.
Go to step 3.
3. Check that the type of the board type supports the configuration parameters of the object on the
M2000.
a. Based on the type of the transport object in the alarm information, run the
corresponding MML command to query the status of the transport object. Run the MML
command DSP BRD or DSP BRD to query the type of the board where the object
resides. Check the user manual to determine whether the type of the board supports
the configuration parameters of the object.
Y => The type of the board supports all the configuration parameters of the object.
Contact Huawei Customer Service Center.
N => The type of the board does not support certain configuration parameters of the
object. Go to sub-step b.
Description
This alarm is reported when uplink service processing channel of a board is faulty.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Dedicated Channel Demodulation Unit 1 Faulty, Access Channel
Problem Demodulation Unit Faulty, AI Data Transmission Failure, DSP BFN Abnormal, APP Measurement
Failure, CHIP Register Configuration Abnormal, CPU-DSP Coding Unit Interface Frame Error,
SIR Data Transmission Failure, DSP Timing Interrupt Abnormal, DSP Peripheral Equipment
Abnormal, DSP External Interface Abnormal, CHIP Register Configuration Abnormal, DSP-Chip
Interrupt Timeout, PRBUS Interface Abnormal, Chip BFN Abnormal, DSP Kernel Abnormal, CPU
and DSP Disconnected, Decoding Module Internal Error, Decoding Module External Interface
Abnormal, ARM Disconnected, Dedicated Channel Demodulation Unit 0 Faulty)
Major The faulty uplink resources are unavailable, resulting in decreased system capacity
or service interruption.
System Actions
When this alarm is generated, the system sets the corresponding uplink processing channel as unavailable
according to the fault code reported. If other uplink resources are available in the baseband subrack, the
services carried by the uplink processing channel are migrated to another uplink resource. If other uplink
resources are unavailable or the uplink processing channel becomes unavailable due to service migration failure,
the cells carried by the uplink processing channel become unavailable. In this case, the system automatically
notifies the RNC that the local cells are unavailable.
Possible Causes
The uplink dedicated demodulation channel, access demodulation channel, or encoding channel is faulty.
Procedure
a. Note: Resetting the board disrupts some or even all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the downlink service processing channel of a board is faulty.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(CHIP Register Configuration Abnormal, Power Control Interface
Problem from FPGA to DL ASIC Abnormal, Modulation Interface from DL ASIC to FPGA Abnormal, DSP
Internal Error, Downlink Service Processing Unit Faulty, CHIP Register Configuration Abnormal,
DSP Kernel Abnormal, DSP Internal Abnormal, DSP External Interface Abnormal, Chip External
Interface Abnormal, CPU and DSP Disconnected, PRBUS Interface Abnormal, ARM
Disconnected, RTWP Channel Abnormal, Downlink Resource Coding Abnormal, PGBUS
Interface Abnormal, CPU-DSP Coding Unit Interface Frame Error)
Major The faulty downlink resources are unavailable, resulting in decreased system
capacity or service interruption.
Minor The faulty downlink resources are unavailable. The system still has resources that
are working normally. The system capacity decreases.
System Actions
When this alarm is generated, the system sets the corresponding downlink processing channel as unavailable
according to the fault code reported. If other downlink resources are available in the baseband subrack, the
services carried by the downlink processing channel are migrated to another downlink resource. If other
downlink resources are unavailable or the downlink processing channel becomes unavailable due to service
migration failure, the cells carried by the downlink processing channel become unavailable. In this case, the
system automatically notifies the RNC that the local cells are unavailable.
Possible Causes
Procedure
a. Note: Resetting the board disrupts some or even all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the system detects that the frame number received on the board for synchronization
has errors.
Parameters
Parameter
Name Parameter Description
Specific Specific Problem of the alarm(Downlink DSP's ASIC Power Abnormal, BFN of the Decoding
Problem Unit Abnormal, BFN of the Dedicated Channel Demodulation Unit 0 Abnormal, BFN of the
Access Channel Demodulation Unit Abnormal, BFN of the Encoding Unit Abnormal)
Major Certain or all service resources of the faulty board are unavailable. The system
capacity decreases.
System Actions
When this alarm is generated, the system sets the corresponding service processing unit as unavailable
according to the fault code reported.
Possible Causes
Procedure
a. Note: Resetting the board disrupts some or even all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is generated when the service data channel between the WBBPs is faulty.
Parameters
Major Certain or all service resources of the faulty board are unavailable. The system
capacity decreases.
System Actions
The system sets the service data channel between the WBBPs as unavailable.
Possible Causes
Procedure
a. Note: Resetting the board disrupts some or even all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours.
Run the MML command RST BRD to reset the receive board.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the RRU detects that the voltage of its power supply is higher than or lower than the
rated voltage.
Parameters
System Actions
None
Possible Causes
Procedure
a. Run the MML command RST BRDPWROFF to reset the RRU module on which the
alarm is generated.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
This alarm is reported when the PRRU detects that the reflected power of the antenna connector is too high.
Parameters
Average Forward Power (0.1 dBm) Average Forward Power (0.1 dBm)
Average Backward Power (0.1 dBm) Average Backward Power (0.1 dBm)
Major The uplink or downlink performance of the PRRU is degraded and the services
System Actions
None
Possible Causes
Procedure
When one of the following situations occurs in the system, this alarm is generated.
The system detects that available uplink or downlink baseband processing resources are not added to any uplink
or downlink resource groups.
The system detects that a certain board that cannot be added to multiple UL resource groups is added to
multiple UL resource groups.
Parameters
Parameter
Name Parameter Description
Cause (Uplink Process Unit Inconsistent with Uplink Resource Group Configuration, Downlink Process
Unit Inconsistent with Downlink Resource Group Configuration, This baseband board cannot
belong to multiple uplink resource groups)
Major If "Specific Problem" is "Uplink process unit inconsistent with uplink resource group
configuration" or "Downlink process unit inconsistent with downlink resource group
configuration", the services cannot be carried by the baseband processing resources
that are not added to a resource group. As a result, the baseband processing
capability is insufficient and the UE access is difficult. If "Specific Problem" is
"Baseband board not belonging to multiple UL resource groups", the baseband
processing resource is used by one of the UL group resources.
System Actions
None
Possible Causes
The UE configuration is incomplete. Not all the baseband processing resources are added to the resource group.
A certain board that cannot be added to multiple UL resource groups is added to multiple UL resource groups.
Procedure
a. Identify the cause of the alarm based on the alarm location information.
If "Specific Problem" is "Uplink process unit inconsistent with uplink resource group
configuration", go to step 2.
If "Specific Problem" is "Downlink process unit inconsistent with downlink resource
group configuration", go to step 3.
If "Specific Problem" is "Baseband board not belonging to multiple UL resource groups",
go to step 4.
2. Add all the uplink baseband processing resources to the uplink resource group on the M2000.
a. Run the MML command LST ULGROUP to query the configuration of the uplink
resource group. Run the MML command DSP BRD to query the status of the board and
determine whether there are any available uplink baseband processing resources that
are not added to the uplink resource group.
Y => Some available uplink baseband processing resources are not added to the uplink
resource group. Go to substep b.
N => All available uplink baseband processing resources are added to the uplink
resource group. Contact Huawei Customer Service Center.
b. Run the MML command MOD ULGROUP to add an idle baseband processing board to
the configured uplink baseband resource group (RGOPTYPE=ADDULPUNIT).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
3. Add all the downlink baseband processing resources to the downlink resource group on the M2000.
a. Run the MML command LST DLGROUP to query the configuration of the downlink
resource group. Run the MML command DSP BRD to query the status of the board and
determine whether there are any available downlink baseband processing resources
that are not added to the downlink resource group.
Y => Some available downlink baseband processing resources are not added to the
b. Run the MML command MOD DLGROUP to add an idle baseband processing board to
the configured downlink baseband resource group (RGOPTYPE=ADDULPUNIT).
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
a. Check whether the board needs to be added to multiple UL resource groups in base
station configuration plan.
Y => The board needs to be added to multiple UL resource groups in base station
configuration plan. Go to substep b.
N => The board does not need to be added to multiple UL resource groups in base
station configuration plan. Go to substep c.
b. Run the MML command DSP BBPTC to query the capability of the baseband board.
Based on the command output and the board capability described in the Hardware
Description, determine whether the board can be added to two uplink transmission
resource groups.
Y => The board can be added to two uplink transmission resource groups. Contact
Huawei Customer Service Center.
N => The board cannot be added to two uplink transmission resource groups. Go to
step 5.
c. Run the MML command MOD ULGROUP to delete the board that is not needed in the
resource group.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
5. Replace the baseband board with a board that can be added to two UL resource groups onsite.
This alarm is reported when the system detects that the current board cannot serve as the backup of the
transmission of another board after the board is started.
Parameters
Parameter
Name Parameter Description
Cause (Back-board not support, Board Type Mismatch, Board not support, Sub-board Type
Mismatch)
Specific Specific Problem of the alarm(Back-board not support, Board Type Mismatch, Board not
Problem support, Sub-board Type Mismatch)
Major The active/standby transmission is not supported, thus affecting the reliability of the
system transmission.
System Actions
None
Possible Causes
Procedure
This alarm is reported when the system detects that the configuration file does not exist, the file format is illegal,
or the file data is illegal after the NE is started or the configuration file is re-downloaded.
Parameters
Parameter
Parameter Description
Name
Specific Specific Problem of the alarm(OAM configuration data illegal, Transport configuration data
Problem illegal, Signal configuration data illegal)
Major Some configuration data is illegal, or the NE cannot obtain the configuration data.
The NE has to operate with the default configuration data. In this case, the NE
cannot provide normal services.
System Actions
The NE operates with the default configuration data. If the transmission link is available but the IPoA channel
fails, the NE may start BOOTP.
Possible Causes
The configuration file is illegal. For example, the file format is invalid or syntax errors exist in the file.
Procedure
a. Run the MML command ULD CFGFILE to upload the data configuration file from the
BBU. Enter the IP address of the FTP server according to the configuration of the FTP
server. Then, specify the destination path, user name, and password. Use the default
values for other parameters. Check whether the upload is successful based on the
command response.
Y => The upload is successful. Go to step 2.
N => The upload fails. The configuration file may be missing or the flash may be faulty.
Go to step 3.
a. Check whether the configuration file is correct. Ensure that the NE type and hardware
type in the file are consistent with the running data and that the file is in .xml format.
Y => The configuration file is correct. Go to step 3.
N => The configuration file is not correct. Go to sub-step b.
a. Retrieve the correct configuration file or use the modified configuration file.
b. Run the MML command DLD CFGFILE to download the data configuration file to the
BBU. Enter the IP address of the FTP server according to the configuration of the FTP
server. Then, specify the source path, user name, and password.
a. Note: Replacing the main control board disrupts all the ongoing services of the base
station. Therefore, perform this operation in low-traffic hours. The base station software
upgrade may be required during board replacement, so the correct software version
should be ready for use in advance.
Replace the main control board. Wait until the startup of the main control board is
complete.
b. Run the MML command DLD CFGFILE to download the data configuration file to the
BBU. Enter the IP address of the FTP server according to the configuration of the FTP
server. Then, specify the destination path, user name, and password.
c. Run the MML command SET CFGFILEENB (FLAG=ENABLE,
RSTMODE=IMMEDIATELY) to set the enabling flag of the downloaded data
configuration file.
If "Reset Mode" is "Immediately reset", the NE will be automatically reset. Otherwise,
the NE needs to be reset manually.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Reinstall the original board. Contact Huawei Customer
Service Center.
This alarm is reported when the main control board fails to set parameters on a board during the startup of the
board or the board cannot be started.
Parameters
Parameter
Name Parameter Description
Cause (Key Parameter Configuration Failure, Non-Key Parameter Configuration Failure, Startup
Timeout)
Major When the setting of the key parameters fails, the board becomes unavailable. When
the setting of the unimportant parameters fails, the secondary functions of the board
cannot work properly. When the board cannot be started, the board fails to work
properly and the services carried by the board are interrupted.
System Actions
The system automatically disables the board when the setting of the key parameters fails or the board cannot
be started.
Possible Causes
Procedure
2. Check for the alarms indicating hardware failures and configuration failures of the board on the
M2000.
This alarm is reported when the external analog signal is too strong or too weak or when the external Boolean
indicates the external Boolean device is faulty.
Parameters
Specific Problem Specific problem of the alarm (Only for analog alarm)
System Actions
None.
Possible Causes
In the case of the external analog device, the external analog alarm threshold is incorrect.
In the case of the external Boolean device, the external Boolean alarm enabling or signal level
configuration is incorrect.
The cable connection between the external analog equipment and the monitoring device is faulty.
Procedure
a. Check the external alarm is whether an external analog alarm or an external Boolean
alarm.
If the external analog alarm is defined, go to procedure b
If the external Boolean alarm is defined, go to step d
b. Run the MML command LST ALMPORT to check whether the threshold of the external
analog alarm or the alarm disable configuration and alarm valid level configuration of the
external Boolean alarm is consistent with that in the configuration planning.
d. Run the MML command LST ALMPORT to check whether the alarm disable
configuration and alarm valid level configuration of the external Boolean alarm is
consistent with that in the configuration planning.
Y => The configuration is consistent with that in the planning. Go to procedure 2.
N => The configuration is inconsistent with that in the planning. Go to step e.
e. Run the MML command SET ALMPORT to set the alarm disable configuration and
alarm valid level configuration based on the configuration planning.
Check whether the alarm is cleared.
Y => The alarm is cleared. No further action is required.
N => The alarm is not cleared. Go to step 2.
2. Check the cable connection between the external analog/boolean equipment and the monitoring
device on site.
N => The alarm is not cleared. Contact Huawei Customer Service Center.
This document describes all the events of the BTS3900 WCDMA, BTS3900A WCDMA, BTS3900L WCDMA,
BTS3900C WCDMA, BTS3900AL WCDMA, and DBS3900 WCDMA. The MML commands involved in this
document takes NodeB_2U for example.
Version
The following table lists the product versions involved in this document.
Intended Audience
Field engineers
System engineers
Shift operators
Site maintainers
Network operators
Concepts
Concept Description
Event Name Unique name of an event in one product. Event names clearly and accurately indicate event
meanings. There is a one-to-one mapping between event names and IDs.
Event Level Impact of an event on service quality. There are three event severity levels: major, minor,
and warning.
Major event: affects service quality and requires immediate action during working
hours.
Minor event: generally does not affect service quality, but requires handling or
observation in a reasonable amount of time to avoid more serious faults.
Warning event: indicates a potential error that may affect service quality. It
Concept Description
Change History
The SCTP link consists of the active path and the standby path. This event is reported when the SCTP protocol
stack detects that the current path is unavailable and the SCTP switches to another path.
Parameters
Name Meaning
Switchover SCTP link path switchover direction (Main-to-Standby Switchover, Standby-to-Main Path
Direction Switchover)
Minor During the switchover between the primary link and the secondary link of the SCTP,
the signaling communication fails temporarily. In this case, no terminal can access
the network during the switchover.
Possible Causes
The current link that carries the SCTP is faulty, and the SCTP switches to another link.
The automatic switchover is enabled. When the secondary link is used, the automatic switchover is
triggered if the primary link is restored.
Procedure
This event is reported when the switchover of the maintenance link between the base station and the M2000
occurs.
Parameters
Name Meaning
Minor None
Possible Causes
The current link for remote maintenance is faulty, and another link is used for remote maintenance.
Procedure
This event is reported when a board is reset due to the execution of a command or exception.
Parameters
Name Meaning
Reset Reason of the board reset (Board Power Off, User Command, System Self-Reset, External
Cause Operation Reset, Swap MPT, Exceptional Reset, Communication Abnormal, Unknown Reason)
Possible Causes
The board is reset due to a power failure, for example, removing and then inserting the board or
running a reset command through power-off.
The board is reset due to the execution of a command, for example, running a software activation
command, a board reset command, or a board addition command during an upgrade.
The board is reset due to internal negotiation of the system, for example, changing the environment
variables of the board, or the board is reset due to a transmission subsystem fault.
The board is reset due to an exception, for example, memory software failure.
The board is reset due to the disconnection between the board and the upper-level node.
Procedure
This event is reported when the base station is reset due to the execution of a command, software upgrade, or
exception.
Parameters
Name Meaning
Reset Reason of the NE reset (Board Power-Off, User Command, System Self-Reset, External
Cause Operation, Active/Standby MPT Switchover, Exceptional Reset, Disconnected Link, Unknown)
Minor The ongoing services carried on the base station are interrupted.
Possible Causes
The base station is reset due to internal negotiation of the system , a UTRPc/UMPT board fault and
signaling extension services unavailable, or a transmission subsystem fault.
Procedure
This event is reported when the NE downloads the software to the main control board from the server.
Parameters
Name Meaning
Warning None
Possible Causes
The NE software automatic supplementation function is triggered. This function is triggered when a
new board is installed in the base station but the base station does not have the software for the
board.
Procedure
This event is reported when the NE succeeds in downloading or fails to download software to the main control
board from the server.
Parameters
Name Meaning
Warning None
Possible Causes
Procedure
This event is reported when the NE downloads the software to each board to be activated from the main control
board and updates the software.
Parameters
Name Meaning
Warning None
Possible Causes
Procedure
This event is reported when the NE downloads the software to each board to be activated from the main control
board and succeeds in updating or fails to update the software.
Parameters
Name Meaning
Warning None
Possible Causes
Procedure
In ring topology, the uplink and downlink of the RF unit cooperate in active/standby mode. If the uplink is faulty,
the RF unit automatically switches to the downlink. This event is reported in this case.
Parameters
Name Meaning
Minor In the case of a hot ring, the ongoing services are not affected. In the case of a cold
ring, the ongoing services are disrupted temporarily.
Possible Causes
Procedure
This event is reported when the RF unit automatically switches off the TX channel due to a critical fault on the RF
unit, or when the user sends a command to switch off the TX channel.
Parameters
Name Meaning
Possible Causes
A critical fault occurs on the RF unit, such as PA overcurrent, critical overtemperature, or extremely
high VSWR.
The user sends a command to switch off the TX channel of the RF unit.
When the AC mains failure occurs and the batteries are running out, the system automatically
switches off the TX channel of the RF unit to extend the operating time of the BBU and transmission
devices.
Procedure
This event is reported when the user sends a command to switch on the TX channel of an RF unit, or when a cell
is activated.
Parameters
Name Meaning
Minor None
Possible Causes
A cell is activated.
Procedure
Parameters
Name Meaning
Reset Cause of the RF unit reset (Board Power-Off, User Command, Exceptional Reset,
Reason Disconnected Link, Unknown Reason)
Minor The RF unit starts. The services of the RF unit are set up again.
Possible Causes
The RF unit automatically resets after it is disconnected for a long period of time.
The RF unit automatically resets after the RF software activation or new configuration is complete.
The RF unit automatically resets after it exits the sleep mode.
Procedure
In ring topology, the CPRI uplink and downlink of the RHUB cooperate in active/standby mode. If the CPRI uplink
is faulty, the RHUB automatically switches to the CPRI downlink. This event is reported in this case.
Parameters
Name Meaning
Uplink Port Before Switchover Uplink port before switchover (Port 0(West), Port 1(East))
Uplink Port After Switchover Uplink port after switchover (Port 0(West), Port 1(East))
Minor In the case of a hot ring, the ongoing services are not affected. In the case of a cold
ring, the ongoing services are disrupted temporarily.
Possible Causes
Procedure
Parameters
None.
Warning The dynamic counting items and performance items in the license, such as the
number of channel elements (CEs) in the uplink and number of CEs in the downlink,
are set to their maximum values. Other types of license-controlled items use their
original values.
The system can keep in the emergency state for a maximum of seven days. Later,
the system is rolled back to the license state.
Possible Causes
The emergency status of a license is activated by someone in an emergency such as fire or earthquake.
Procedure
Parameters
None.
Possible Causes
The emergency status of a license remains active for seven days. After the seven-day period
elapses, the emergency status is automatically ceased.
Procedure
This event is reported when the NBAP common signaling processing over the Iub interface fails.
Parameters
Name Meaning
Cause (Common TRCH Setup Failure, Common TRCH RECFG Failure, Common MEA INIT Failure,
Common MEA Failure, Cell Setup Failure, Cell RECFG Failure, SYS MSG Update Failure, Shared
TRCH RECFG Failure, INFO EXCHANGE INIT Failure, INFO EXCHANGE Failure)
Cell ID Cell ID
Specific Specific Problem of the alarm(System Message Abnormal, Common Transport Channel Carried by
Problem SCCPCH Abnormal, Common Transport Channel Carried by PRACH Abnormal, Other Transport
Channel Abnormal, RTWP Measurement Abnormal, Transmitted Carrier Power Measurement
Abnormal, Acknowledged PRACH Preambles Measurement Abnormal, GPS Timing of Cell Frames
Measurement Abnormal, Transmitted Carrier Power Measurement Abnormal Not Used for HSDPA,
HS-DSCH Required Power Measurement Abnormal, HS-DSCH Provided Bit Rate Measurement
Abnormal, ISCP Measurement Abnormal, APAP Measurement Abnormal, DPAP Measurement
Abnormal, SOTD Measurement Abnormal, Shared Transport Channel Reconfiguration Failure, INFO
EXCHANGE INIT Failure, INFO EXCHANGE Failure, Cell Procedure Abnormal)
Possible Causes
Resources in the cell are insufficient or faulty. For example, the hardware of the board carrying the
traffic is faulty.
The processing of the RNC is incorrect. As a result, the contents of the message that is sent to the
NE are incorrect.
Procedure
a. Run the MML command DSP LOCELL to check whether the local cell status of the
failed signaling is normal.
Y => “Local Cell Status” is “Local Cell Available”. The local cell is normal. Go to step 2.
N => “Local Cell Status” is “Local Cell Unavailable”. The local cell is faulty. The cause
may be that the hardware resources of the NE are faulty. Go to sub-step b.
b. Run the MML command LST ALMAF to check whether certain alarms of the NE are not
cleared.
Y => Certain alarms are not cleared. Go to sub-step c.
N => All alarms are cleared. Go to sub-step d.
d. Run the MML command RMV LOCELL to delete the local cell that is faulty.
e. Run the MML command ADD LOCELL to add the deleted cell again.
f. Wait for 1 minute, and then run the MML command DSP LOCELL to check whether the
local cell status of the failed signaling is normal.
Y => “Local Cell Status” is “Local Cell Available”. The local cell is normal. Go to step 2.
N => “Local Cell Status” is “Local Cell Unavailable”. The local cell is faulty. Contact
Huawei Customer Service Center.
a. Run the MML command DSP CELLCFG to check whether the logical cell status of the
failed signaling is normal.
Y => The logical cell is normal. Go to step 3.
N => The logical cell is faulty. The cause may be that the transmission resources of the
NE are faulty. Go to sub-step b.
b. Run the MML command LST ALMAF to check whether active alarms exist on the NE.
Y => There is one or more active alarms on the NE. Go to sub-step c.
N => There is no active alarm on the NE. Go to sub-step d.
c. Clear the correlated alarm according to the relevant handling suggestions.
f. Wait for one minute, and then run the MML command DSP CELLCFG to check whether
the logical cell status is normal.
Y => The logical cell is normal. Go to step 3.
N => The logical cell is faulty. Contact Huawei Customer Service Center.
a. Check whether this alarm is reported again. If this alarm is reported, Contact Huawei
Customer Service Center.
This event is reported when the system attempts to reestablish the local cell for recovery from the fault upon
service interruption caused by a local cell failure, or when the local cell is reestablished for resource optimization.
Parameters
Name Meaning
Major In the case that the event is reported because the local cell is faulty, only the faulty
Possible Causes
The local cell fails to provide services and the system attempts to the local cell reestablish the local
cell for recovery from the fault. This happens when: a) The SET NOACCESSALMPARA command is
executed and the AUTORCVRMTHD parameter is set to CELLRESTART. b) The cell has no output
power.
If the resources of the local cell are not optimum, the system attempts to optimize the resources.
This happens when: a) The STR REALLOCLOCELL command is executed to optimize baseband
resources.
Procedure
This event is reported when the system attempts to reestablish the IMB( Integrated Mobile Broadcast) local cell
for recovery from the fault upon service interruption caused by a IMB local cell failure, or when the IMB local cell
is reestablished for resource optimization.
Parameters
Name Meaning
Major In the case that the event is reported because the IMB local cell is faulty, only the
faulty IMB local cell and faulty logical cell are reestablished.
In the case that the event is reported because the resources of the IMB local cell are
not optimum, all the available local cells and logical cells are reestablished.
Possible Causes
The IMB local cell is faulty and fails to provide services. Thus, the system attempts to recover from
the fault by reestablishing the IMB local cell.
If the resources of the IMB local cell are not optimum, the system attempts to optimize the resources
of the IMB local cell.
Procedure
This event is reported when the auto negotiation is enabled for the local Ethernet electrical port but disabled for
the peer Ethernet electrical port.
Parameters
Name Meaning
Minor If the Ethernet electrical port carries heavy traffic, Ethernet frames may be lost,
causing the services to be interrupted for a short time.
Possible Causes
The auto negotiation is enabled for the local Ethernet electrical port but disabled for the peer port (full-duplex or
half-duplex).
Procedure
1. Perform the corresponding operation on the M2000 to allow the system to renegotiate the working
mode of the Ethernet ports.
a. Set the working mode of the Ethernet port on the peer device connected to the NE to
auto negotiation, and then run the MML command RST ETHPORT to reset the Ethernet
electrical port for which the event is triggered.
This event is reported when the MML command is executed to reset the ETH port, MLPPP group, PPP link, and
ETHTRUNK.
Parameters
Name Meaning
Object Type (Ethernet Port, MLPPP Group, PPP Link, Ethernet Trunk Group)
Major The signaling and services carried on the ETH port, MLPPP group, PPP link,
ETHTRUNK are interrupted for a short time.
Possible Causes
The MML command is executed to reset the objects of the IP transmission network (ETH port, MLPPP group,
PPP link, and ETHTRUNK).
Procedure
This event is reported when the operation of running the command SET CFGFILEENB with Enable Flag set to
Enable is successful.
Parameters
None.
Minor After the system is restarted, the downloaded configuration file takes effect and
overwrites the original configuration file.
Possible Causes
The command SET CFGFILEENB is executed with Enable Flag set to Enable.
Procedure
This event is reported when the operation of running the command SET CFGFILEENB with Enable Flag set to
Disable is successful.
This event is also reported in the scenario where the system automatically disables the flag that has been
enabled after the user redownloads the configuration file, activates the configuration baseline (CB), or rolls back
the CB.
Parameters
None.
Possible Causes
The command SET CFGFILEENB is executed with Enable Flag set to Disable.
The flag is enabled, but the user redownloads the configuration file.
The flag is enabled, but the user rolls back the CB.
Procedure
This event is reported when the user runs the command to reset the NE or the active WMPT/UMPT.
Parameters
None.
Possible Causes
The user runs the command to reset the NE or the active WMPT/UMPT.
Procedure