Documente Academic
Documente Profesional
Documente Cultură
Critical Alarm
Trouble-
shooting Guide
Document Type: MOP
Manish Singh
& Santosh M Jagtap Hiren Joshi
Umesh Jagtap
****************************INDEX****************************
1. Check the value of the parameter "Possible cause" in the information used
for locating the fault.
a. "Possible cause" is 0. Add the GDPUP to increase the number of
packet DSPs available.
b. "Possible cause" is 1. Need to apply for a license that supports this
feature.
c. "Possible cause" is 2. Go to 2.
d. "Possible cause" is 3. Go to 3.
2. Run the MML command DSP PSCELL to check whether the cell Um
administration state is blocked.
Y => Adjust the BTS to unblock the Um interface. For example, unblock
the blocked cell.
3. Run the MML command DSP PSCELL to check whether the cell Gb
administration state is blocked.
Y => Go to 4.
Y => Go to b.
DESCRIPTION: This alarm is generated when the BSC fails to read the license file.
IMPACT: The functions and resources of the BSC system are restricted. If the alarm
persists for seven days, all the services are prohibited.
b. If the alarm is reported, rectify the fault according to the alarm. Then,
check whether the alarm is cleared.
N => Go to 2.
Y => Go to 3.
N => Go to 5.
3. On the MML client, run the MML command LST LICENSE to check whether
the license file is activated.
N => Go to 4.
4. On the MML client, run the MML command ACT LICENSE to activate the
specified license file.
On the MML client, run the DLD LICENSE to download the specified
license files on the FTP server to the OMU server.
b. On the MML client, run the MML command ACT LICENSE to activate
the specified license file. Then, check whether the alarm is cleared.
IMPACT: The signaling unit cannot be sent by the local signaling point to the DSP. The
service is disrupted.
Y => Clear the parent alarm according to the corresponding handling suggestions.
Check whether the alarm is cleared.
N => Go to 2.
This alarm is reported when the parent alarm occurs on the ports for all the
internal signaling links. The parent alarm leads to the child alarm, and they are
reported simultaneously without fixed sequence.
N => Go to 3.
For details about how to configure the signaling links, refer to the HUAWEI
BSC6000 Base Station Controller Data Config
Y => If the status of the MTP2 link is in service, Please contact to TEC.
N => check whether the MTP2 Link Service Disrupted alarm is reported.Handle
the alarms according to the suggestions. The alarm handling is complete.
DESCRIPTION: Both active SCU and standby SCU are unavailable. Services related to
the subrack are unavailable.
IMPACT: Both active SCU and standby SCU are unavailable. Services related to the
subrack are unavailable.
1. Check the location information of the alarm. If the extension sub rack reports the
alarm, Go to [2].If remote sub rack reports the alarm, Go to [4].
2. Insert the Ethernet cable securely between the main sub rack and extension sub
rack. Check whether the alarm is cleared.
3. Replace the Ethernet cable between the main subrack and extension subrack.
Check whether the alarm is cleared.
5. Replace the E1 cable between the local subrack and remote subrack. Check
whether the alarm is cleared.
6. Request the maintenance personnel to check whether the status of the GSCU
board in the subrack is available.
N => The status of the GSCU is unavailable. Identify the cause for unavailability
and reset the GSCU. The alarm handling is complete.
DESCRIPTION: This alarm is generated on the SCU in the GMPS when the
communication between the board and the SCU in the GMPS is interrupted.
IMPACT: GOMU:
1. On the LMT, check whether a pair of GOMUs is configured for the BSC.
Y => Go to 2.
Y => Go to 3.
N => Insert the standby GOMU. Then, wait until the startup of the GOMU is
complete. Go to 4.
N => Go to 4.
N => Start the OMU software on the standby GOMU. Then, check whether the
alarm is cleared.
1. If the remote TC subrack is configured, check whether the OML on the Ater
interface is disconnected.
a. On the LMT, check whether the remote configuration is adopted and
whether all boards in the TC subrack are unavailable.
Y => Go to b.
N => Go to 2.
b. Log in to the LMT. Choose Alarm Maintenance > Browse Alarm to check
whether the following parent alarm is reported.
Y => Go to c.
N => Go to 2.
c. If the alarm is reported, rectify the fault according to the alarm . Then,
check whether the alarm is cleared.
N => Go to 2.
2. Check whether the Ethernet cable between SCUs of the GMPS and another
subrack is disconnected.
a. On the LMT, check whether all boards in the subrack are unavailable.
Y => Go to b.
N => Go to 3.
b. Check whether the port on panel of the SCU in the GMPS is enabled.
Y => Go to d.
N => Go to d.
d. Check whether the Ethernet cable between the SCUs on the GMPS and the
problematic subrack is normal and whether the Ethernet port LED is
normal.
N => Go to b.
b. Check whether the board is removed. Insert the board and wait until the
loading of the board is complete. Then, check whether the alarm is
cleared.
N =>Go to c.
c. Remove and then reinsert the board when the traffic volume is low. Then,
check whether the alarm is cleared.
N => Go to d.
DESCRIPTION: This alarm is generated when the parsing of the license file fails because
the license file is not available, the license file will expire in 30 days, or the license file
already expires.
IMPACT: 60 days after the license file is invalid, the functions and resources controlled
by the license will be restricted and the control items of products are reduced to the
minimum configuration. This may affect the services.
1. Check the value of the parameter Reason of check failure in the information used
for locating the fault.
a. The value is "0 = Parsing license error". Go to 2.
b. The value is "1 = License expired". Go to 6.
c. The value is "2 = No activated license". Go to 3.
d. The value is "3 = License will expire". Go to 6.
2. Reload the specified license file and reactivate it.
a. Run the MML command DLD LICENSE on the MML client to
download the specified license file on the FTP server to the GOMU server
through FTP.
b. Run the MML command ACT LICENSE on the MML client to activate
the specified license file.
Y => Go to 7.
N => Go to c.
c. Check whether the license file matches the configured signaling point.
N => Go to d.
d. Apply for a new license according to the configured signaling point and
activate it. Then, check whether the alarm is cleared.
Y => Go to 4.
N => Go to 5.
4. Run the MML command LST LICENSE on the MML client to check whether
the license file is activated.
Y => Go to 7.
N => Go to 5.
5. Run the MML command ACT LICENSE on the MML client to activate the
specified license file.
Set the RX C2 byte on the peer board to 0x02, and then check whether the alarm is
cleared.
DESCRIPTION: Higher order path remote defect indication at the receiver side of optical
interface.
1. Check whether any of the following alarms exist on the peer equipment: 20232
Loss of Administration Unit Pointer (AULOP),20231 Administration Unit
Alarm Indication Signal (AUAIS), 20235 High-Order Path Signal Label Byte
Mismatch (HPSLM), or 20234 Trace Flag Mismatch on the High-Order Path
of the Optical Port (HPTIM).
Y => Go to 2.
2. Ask the maintenance personnel at the peer end to clear the alarms there, and then
check whether the alarm on the local equipment is cleared.
DESCRIPTION: Tributary unit alarm indication signal. No signal is detected between the
peer equipment (BTS or BSC) and the transmission equipment, whereas the transmission
equipment is normally connected with the local equipment.
1. Wait until the board is successfully loaded and restarted. Check whether the alarm
is cleared.
2. Replace the board and wait until the board is successfully restarted. Check
whether the alarm is cleared.
DESCRIPTION: This alarm is generated when the CPU usage exceeds 85% and this
situation lasts for more than one minute. When the CPU usage is over high, the flow
control occurs. As a result, the capability of processing services reduces and even the
board is reset.
IMPACT: When the CPU usage is overhigh, the flow control occurs. As a result, the
capability of processing services reduces and even the board is reset.
Y => The alarm is cleared after the traffic reduces. The alarm handling is
complete.
N => Go to b.
b. Remove and then reinsert the board when the traffic volume is low. Then,
check whether the alarm is cleared.
N => Go to c.
ALARM:20422-Abnormal Voltage
Alarm Description
This alarm is reported when one supply voltage of the input power in the power
distribution box or one supply voltage of the environment monitoring device exceeds the
upper or lower voltage limitation
Impact on System
The power distribution box supplies power abnormally. This may has an impact on
normal running of the system. If the voltage exceeds the upper or lower limitation, the
power module on the board might stop supplying power and the service is interrupted.
1. Check the duration of the alarm. If the duration is less than 10 seconds, the alarm
is reported because of the voltage pulsation and is unnecessary to be handled.
2. If the duration is long, Check whether the power supply is normal.
N=> The power supply is over voltage or under voltage. Inform the network
operator to take certain measures, such as power transfer or battery maintenance.
The alarm handling is complete.
NOTE:
3. Reset the power distribution box on the LMT. After the power distribution box is
registered successfully, check whether the alarm is cleared.
ALARM:20421-Abnormal Temperature.
Description
An over temperature alarm is reported when the fan box or independent fan
box detects that the temperature exceeds the upper temperature threshold.
An under temperature alarm is reported when the temperature of the power
distribution box or the environment monitor device exceeds the lower
temperature threshold. In reverse, an over temperature alarm is reported.
Impact on System
The over temperature or the under temperature of the cabinet has an impact
on normal running of the system.
Impact on System
The BSC can not apply the resource for the services.
N = Go to 2.
Alarm Description
Impact on System
Fan block affects system running environment, such as temperature and humidity.
Y => Go to 3.
N => Clean the air filter and then install it. For the method of installing the air
filter, refer to the BSC6000 Parts Replacement Guide. Go to 2.
2. Check whether the fan rev is nomal. The full rev is 4000 RPM.
3. Replace the fan subrack and check whether the alarm is cleared.
ALARM:293-GB BC Faulty
Alarm Description
BC is a binding of E1's some slots for transferring service data and signaling data. This
alarm is reported when the Gb interface is broken, the configuration of Gb interface is
faulty, or the BC is blocked.
Impact on System
1. Check whether the E1 cable between the BSC and the SGSN is correct;
Y => Go to 2;
2. On the local maintenance terminal of BSC and SGSN, separately run the MML
command LST BC. Check whether the configurations include sub rack No., slot
No., port No., BC ID, Times lot Mask of BSC and SGSN are the same;
Y => Same, Go to 3;
N => Different, Go to 4;
3. On the local maintenance terminal of BSC, run the MML command DSP BC.
Check whether the BC is blocked;
The temperature of the test point of the board is over the critical high threshold
Impact on System
2. Check whether there are empty slots which have not installed dummy panels.
Y => There are empty slots which have not installed dummy panels. Go to 3.
3. Check whether the temperature exceeds the normal operation range for the
equipment.
Y => The temperature exceeds the normal operation range for the equipment.
Adjust the temperature to the normal operation range. Go to 4.
N => The temperature does not exceed the normal operation range. Please contact
TEC.
ALARM:331-NSVC Faulty
Alarms Description
The NSVC refers to the virtual connection at the NS layer of the Gb interface. This alarm
is generated when the GEPUG is faulty, the NSVC is blocked, the bearer channel is
inaccessible, or the configuration of the BSC and SGSN is faulty.
Impact on System
• If the backup NSVL is not configured, the data services in the relevant cells
cannot be performed;
• If a backup NSVL is configured, the data services in the relevant cells can be
performed, but the service capacity decreases.
1. Run the MML command DSP NSVC to check whether the NSVC is blocked.
Y => Run the MML command UBL NSVC to unblock the NSVC.
N => Go to 2.
Y => Go to 3
3. On the LMT of the BSC and the SGSN, separately run the MML command LST
NSVC. Check whether the configuration of the NSE and NSVC on the BSC and
that on the SGSN are consistent.
Y => Go to 4.
N => Configure the NSE and Configure the NSVC of the BSC to ensure that they
are consistent with those of the SGSN
Y => Go to 5.
N => Remove and reinsert the GEPUG until the board works normally.
5. Run the MML commands DSP BC and DSP PVC. Check whether the statistical
data of the BC and PVC is normal.
N => TEC
This alarm is triggered when the RLOS (signal loss at receiving end) alarm, or the RLOF
(frame loss at receiving end) alarm, or the HPLOM (multi-frame loss at high-phase
channel) alarm occurs to the TEU.
Impact on System
Services borne by the faulty optical interface are interrupted. If the optical interface
connecting to the lower level devices fails, services supported by the lower level devices
will be interrupted. If the optical interface connecting to the upper level devices fails,
services supported by the devices of the lower level or the local level will be interrupted.
N=> Go to Step 2.
Check to ensure the power supply for other network elements (NE) in the optical
transmission network is normal, and the cable connecting to the local BTS has
been connected properly, and the transmission devices of the upper layer are in
normal operation. Clear the faults of other NEs if any. View whether the alarm is
cleared.
N=> Go to Step 3.
Check whether the tail fiber is neat, and whether the flange is properly connected.
Clean the tail fiber if dirty and reconnect the flange properly. View whether the
alarm is cleared.
N=>Go to Step 4.
Measure the power of optical signals from the peer end to see whether the result is
smaller than -28dBm.
5. Perform self-loop for western optical fiber and eastern optical fiber
Perform self-loop for western optical fiber and eastern optical fiber. View whether
the alarm is cleared.
This alarm is triggered when the optical transmitter in the IASU detects transmit loss of
signal (TLOS) or transmit loss of clock (TLOC) or the optical receiver detects multiplex
section remote defect indication (MSRDI) from the peer site.
Impact on System
Services borne by the faulty optical interface are interrupted. If the optical interface
connecting to the lower level devices fails, services supported by the lower level devices
will be interrupted. If the optical interface connecting to the upper level devices fails,
services supported by the devices of the lower level or the local level will be interrupted.
Check whether the fiber connector is loose or blurred. If yes, clear it with alcohol
and securely connect it to the port.
Check whether the pigtail fiber connected with the local or peer site is severely
bent or broken. If yes, bundle it well or replace it with a normal one.
N=> Go to Step 2.
2. Check the transmit and receive optical power of the optical module
Measure the receive optical power of the local site and the transmit optical power
of the peer one with an optical power meter based on the optical path
corresponding to the "Sub No.".
Check whether the receive optical power is within -35 dBm to -28 dBm and
Check whether the transmit optical power is within -15 dBm to -8 dBm.
Y=> The receive and transmit optical power is normal.Please contact Huawei
Customer Service Center
and whether it is damaged. Verify that the fiber is normal, replace the MCU in the
local site. The alarm handling ends.
N=> The receive optical power is low. Pls contact TEC to check whether the fiber
is in bad contact with the port and whether it is damaged. If yes, securely connect
the fiber or replace it with a normal one. The alarm handling ends.
This alarm is generated if the handshake between the BSC and the MSC at the SCCP
layer fails.
Impact on System
The signaling interaction and the services between the BSC and the MSC are disrupted.
Y => The data configurations of the SS7 signaling points are the same. Go
to c.
N => The data configurations of the SS7 signaling points are different. Go
to b.
b. Ensure that the data configurations of the SS7 signaling points of the BSC
are the same as those of the MSC. Then, check whether the alarm is
cleared.
c. Check whether the data configurations of the SS7 signaling links of the
BSC are the same as those of the MSC.
Y => The data configurations of the SS7 signaling links are the same. Go
to e.
N => The data configurations of the SS7 signaling links are different. Go
to d.
d. Ensure that the data configurations of the SS7 signaling links of the BSC
are the same as those of the MSC. Then, check whether the alarm is
cleared.
e. Check whether the data configurations of the SS7 signaling links are
consistent with the physical connections.
Y => The data configurations of the SS7 signaling links are consistent
with the physical connections. Go to 2.
N => The data configurations of the SS7 signaling links are inconsistent
with the physical connections. Go to f.
f. Ensure that the data configurations of the SS7 signaling links are
consistent with the physical connections. Then, check whether the alarm is
cleared.
2. Check the status of the SCCP DSP and of the MTP3 link.
a. Check whether the SCCP DSP is manually inhibited.
b. Uninhibit the SCCP DSP. Then, check whether the alarm is cleared.
d. Activate the MTP3 link. Then, check whether the alarm is cleared.
3. Check whether the BSC is reset.Inquire the maintenance engineers about whether
the BSC is reset.
4. Log in to the LMT and then choose Alarm Maintenance > Browse Alarm. Check
whether the alarm 21528 Remote SCCP Fault is reported.
Y => The alarm is reported. The SCCP management subsystem of the MSC is
faulty. Contact the maintenance engineers of the MSC. The alarm handling is
complete.
Impact on System
1. In the Brow Alarm window on the LMT, check whether 21525 SCCP DSP
Unreachable is reported.
Y => The SCCP DSP is inaccessible. Handle the alarm according to the
suggestions in 21525 SCCP DSP Unreachable.
N => Go to 2.
2. Check the state of the SCCP subsystem. Check whether the alarm is cleared.