GSM Troubleshooting Guide 20140516-A - V1.5 (BSC6000&BSC6900)

Doc Code Product Name BSC6900/BSC6000
Intended Audience GSM Accident Recovery Team Product Version R15
Compiling Department GSM Accident Recovery Team Internal use Internal use
GSM Troubleshooting Guide
Prepared By GSM Accident Recovery Team Date 2013-09-17
Reviewed By Date
Reviewed By Date
Approved By Date
Huawei Technologies Co., Ltd.

BSC6900/BSC6000
GSM Troubleshooting Guide Change History
Change History
Date Issue Description Author
2012-01-11 1.00 Completed the draft. Huo Zhifei and Luo Jiangtao
2012-01-17 1.40 Modified document details. Huo Zhifei, Zhang Chen, Wang Wenfeng,
Wang Ke, and Zhang Jie
2012-02-06 1.41 Added the voice description. Huo Zhifei and Wang Wenfeng
2012-04-06 1.42 Added descriptions about Huo Zhifei, Tang XianGui, and Tang
GBAM and TC faults. Honggang
2012-06-26 1.43 Added methods for handling Huo Zhifei, Zhang Jie, and Liu Ping
link disconnection on the Gb
interface and BTS.
2012-07-04 V1.44 Added specifc cases. Huo Zhifei
2013-09-17 1.46 Added specifc cases. Liang Yesong, Guo Zhikuan, and Zhang
Chen
Issue 1.46 (2013-09-17) Huawei Proprietary and Confidential i

Copyright © Huawei Technologies Co.,
Ltd.
BSC6900/BSC6000
GSM Troubleshooting Guide Contents
Contents
Change History..................................................................................................................................i
1 Overview.........................................................................................................................................1
2 Applicable Range..........................................................................................................................2
3 Fault Scope Identification............................................................................................................3
3.1 Fault Scope Identification of CS Services......................................................................................................................3
3.2 Fault Scope Identification of PS Services......................................................................................................................5
4 Guide to Common Emergency Recovery..................................................................................7

4.1 CS Services.....................................................................................................................................................................7
4.1.1 Faulty CS Services......................................................................................................................................................7
4.1.2 Faulty SS7 Links.......................................................................................................................................................15
4.1.3 Interrupted TC Subracks............................................................................................................................................21
4.1.4 TC DSP Failures........................................................................................................................................................22
4.1.5 Faulty Voice Services................................................................................................................................................23
4.2 PS Services...................................................................................................................................................................26
4.2.1 Faulty PS Services and PDCH Faults........................................................................................................................26
4.2.2 Gb Interface Faults....................................................................................................................................................32
4.2.3 Alarms over the Gb Interface....................................................................................................................................34
4.3 BTS Link Disconnection and Cell Out-Of-Service......................................................................................................36
4.4 Repeated Board Resets.................................................................................................................................................41
4.5 Board Loading Failures................................................................................................................................................42
4.6 GBAM/GOMU Faults..................................................................................................................................................44
4.6.1 GBAM/GOMU Troubleshooting...............................................................................................................................44
4.6.2 GBAM Migration......................................................................................................................................................46
4.6.3 BSC Configuration Data Restoration........................................................................................................................48
4.7 Faults in A over IP Mode..............................................................................................................................................50
5 Appendix.......................................................................................................................................52
5.1 Quick Troubleshooting of the GBAM and GOMU Startup Failures...........................................................................52
5.1.1 Connect the keyboard and display (or KVM) to the GBAM/GOMU. Power on the GBAM/GOMU. Check the
output information during the GBAM/GOMU startup......................................................................................................52
5.1.2 Check and re-configuring the RAID.........................................................................................................................54
5.1.3 Remove and insert the hard disks..............................................................................................................................54
BSC6900/BSC6000
GSM Troubleshooting Guide Contents
5.1.4 Re-install the Linux operating system.......................................................................................................................55

5.2 Precautions for Replacing the GBAM Server with the GOMU Board........................................................................56
5.2.1 Check whether the GOMU spare part meets the requirements.................................................................................56
5.2.2 Check whether the available slots in the subrack meet the GOMU installation requirements.................................56
5.2.3 Convert the BSC configuration data..........................................................................................................................56
5.2.4 Install the OMU software..........................................................................................................................................57
5.2.5 Restore the data.........................................................................................................................................................58
5.2.6 Activate the license....................................................................................................................................................58
5.2.7 Verify the operation results........................................................................................................................................58
BSC6900/BSC6000
GSM Troubleshooting Guide 4 Guide to Common Emergency Recovery
1 Overview
As a supportive document for GSM fault handling, this document summarizes the experience
and cases for troubleshooting of the BSC6000/BSC6900 products. The response speed is
important for troubleshooting. Therefore, the troubleshooting personnel must plan ahead of
time and completely understand the way for troubleshooting. In addition, the personnel must
prepare in advance and be familiar with the methods for collecting fault information and the
measures for handling typical scenarios.
Principles for troubleshooting are as follows:
 Troubleshooting must follow the related emergency recovery flow. The troubleshooting
personnel must carry out their duties to improve efficiency.
 Work division must be made as soon as possible.
 Services must be recovered before root cause analysis. Recovery measures must be
executed in priority.
 If measures described in this guide are invalid, reset the BSC after confirming with the
Research and Development (R&D) department.
2 Applicable Range
This document is intended for the following personnel:

 R&D Accident Recovery Team
 GTAC Accident Recovery Team
 On-site maintenance engineers
3 Fault Scope Identification
Specific recovery measures can be provided quickly based on related MML commands,
counters, and alarms.
For alarms related to congestion and intermittent disconnection, check whether the alarm information of
ALM-20271 Statistical Alarm includes the intermittent disconnection alarm.
1.1 Fault Scope Identification of CS Services

Range Counter Alarm
Faults at a cell Counters on accessibility: ALM-21801 GSM Cell out of

RA303G: CELL.ESTB.IND.SUCC.RATE.IMM.ASS Service
RCA313: CELL.ASS.SUCC.RATE 21002 LAPD Broken LAPD
Link (BSC6000)
RA333: CELL.CALL.ESTB.SUCC.RATE
ALM-21512 LAPD Link Fault
Counters on retainability: (BSC6900)
K3004: CELL.KPI.SD.TRAF.ERL ALM-21820 GSM KPI Exceed
K3014: CELL.KPI.TCH.TRAF.ERL.TRAF Threshold (in the V009R013)
ZTR304:
CELL.RATE.TCH.CALL.DROP.INCLUDE.HO
ZTR104C: CELL.SD.CALL.DROP
CM334: CELL.TRAF.CH.CALL.DROPS.EQUIP.FAIL
Counters on mobility
RH303: CELL.HO.SUCC.RATE
RH303B: CELL.INTRABSC.HO.SUCC.RATE
TH343: CELL.INTERBSC.INCELL.HO.SUCC.RATE
Faults on a Counters on accessibility: ALM-21801 GSM Cell out of
base RA303G: CELL.ESTB.IND.SUCC.RATE.IMM.ASS Service
transceiver 21002 LAPD Broken LAPD
station (BTS) RCA313: CELL.ASS.SUCC.RATE
Link (BSC6000)
RA333: CELL.CALL.ESTB.SUCC.RATE
Range Counter Alarm
Counters on retainability: ALM-21512 LAPD Link Fault

K3004: CELL.KPI.SD.TRAF.ERL (BSC6900)
K3014: CELL.KPI.TCH.TRAF.ERL.TRAF ALM-21807 OML Fault
ZTR304: ALM-12816 BTS Clock
CELL.RATE.TCH.CALL.DROP.INCLUDE.HO Synchronization Abnormal
Alarm
ALM-11332 IP clock abnormal
CM334: CELL.TRAF.CH.CALL.DROPS.EQUIP.FAIL alarm
Faults on an Counters on accessibility: ALM-20243 Board Hardware
interface board RA303G: CELL.ESTB.IND.SUCC.RATE.IMM.ASS Fault
RCA313: CELL.ASS.SUCC.RATE ALM-20241 Board Unavailable
RA333: CELL.CALL.ESTB.SUCC.RATE ALM-20251 Board Temperature
too High
Counters on retainability:
K3004: CELL.KPI.SD.TRAF.ERL
K3014: CELL.KPI.TCH.TRAF.ERL.TRAF
ZTR304:
CELL.RATE.TCH.CALL.DROP.INCLUDE.HO
CM334: CELL.TRAF.CH.CALL.DROPS.EQUIP.FAIL
You must check whether faulty cells are connected to the
same interface board.
Faults in a Counters on accessibility: ALM-20227 Communication
subrack RA303G: CELL.ESTB.IND.SUCC.RATE.IMM.ASS Between Subracks Faulty
RCA313: CELL.ASS.SUCC.RATE ALM-20244 Subrack Reset
RA333: CELL.CALL.ESTB.SUCC.RATE ALM-20260 Internal
Communication Fault
Counters on retainability:
ALM-20256 CPU Overload
K3004: CELL.KPI.SD.TRAF.ERL
ALM-20251 Board Temperature
K3014: CELL.KPI.TCH.TRAF.ERL.TRAF too High
ZTR304: ALM-20228 GE Link Between
CELL.RATE.TCH.CALL.DROP.INCLUDE.HO GE Switching Board and Service
ZTR104C: CELL.SD.CALL.DROP Board Faulty
CM334: CELL.TRAF.CH.CALL.DROPS.EQUIP.FAIL ALM-20222 Communication
Counters on mobility Between GE Switching Boards
Range Counter Alarm
RH303: CELL.HO.SUCC.RATE Faulty

RH303B: CELL.INTRABSC.HO.SUCC.RATE ALM-20246 Ater RSL Faulty
Faults on a Involved Counters are related to BTSs and cells ALM-20244 Subrack Reset
base station connecting to multiple BM subracks: ALM-20261 Ater OML Faulty
controller Counters on accessibility:
(BSC) ALM-20736 Data Inconsistency
ZTR101A: BSCRPT.RATE.RANDOM.ACC.SUCC Between OMU and Host
ZTR102A: BSCRPT.RATE.ASS.SUCC ALM-20260 Internal
Counters on retainability: Communication Fault
ZK3004: BSCRPT.KPI.SD.TRAF.ERL ALM-20246 Ater RSL Faulty
ZK3014: BSCRPT.KPI.TCH.TRAF.ERL.TRAF (service
channel)
ZTR107A: BSCRPT.RATE.TCH.CALL.DROP
ZK3180: BSCRPT.KPI.HO.SUCC.RATE
ZK3174: Internal Handover Success Rate Per BSC
Faults on all Counters on accessibility: ALM-21521 SCCP Subsystem
BSCs ZTR101A: BSCRPT.RATE.RANDOM.ACC.SUCC Prohibited
connecting to a You must check transmission on
mobile ZTR102A: BSCRPT.RATE.ASS.SUCC
the A interface and alarms on the
switching Counters on retainability: UMG and MSC, and try to reset
center (MSC) ZK3004: BSCRPT.KPI.SD.TRAF.ERL the peer device.
ZK3014: BSCRPT.KPI.TCH.TRAF.ERL.TRAF (service You must ping the peer IP
channel) address.
ZTR107A: BSCRPT.RATE.TCH.CALL.DROP
ZK3180: BSCRPT.KPI.HO.SUCC.RATE
ZK3174: Internal Handover Success Rate Per BSC
1.2 Fault Scope Identification of PS Services

Procedure MML Command Counter Alarm
Check whether the GbFr: GbFr: GbFr:

Gb interface is DSP E1T1 L9602: Number of Frames ALM-21201 E1/T1 Loss of
faulty. Received on the BC Signal
DSP BC
DSP NSVC L9601: Number of frames ALM-21385 Gb BC Failure
transmitted on the BC ALM-22003 NSVC
GbIP:
L9704: Total Number of bytes Disconnection
DSP ETHPORT of transmitted NS PDUs on GbIP:
PING IP NSVC
ALM-21345 Ethernet Link
TRC IPADDR L9705: Total Number of bytes Fault
of received NS PDUs on NSVC
Procedure MML Command Counter Alarm
DSP NSVL GbIP: ALM-21346 IP Connectivity

DSP GBIPROUTE L9804: Total Number of bytes Check Failure
Cell services: of transmitted NS PDUs on ALM-22004 NSVL Faulty
NSVL ALM-22009 NSVL Dynamic
DSP SIGBVC
L9805: Total Number of bytes Configuration Procedure
DSP PTPBVC of received NS PDUs on NSVL Failure
Cell services: Cell services:
L9403: Total Bytes of Uplink ALM-22005 NSE Faulty
LLC PDUs Sent ALM-22008 PTP BVC Faulty
L9503: Total Bytes of Downlink
LLC PDUs Received
Check whether the DSP PSCELL AR9303: Average Number of ALM-21816 Cell Logical
channel is faulty. DSP PSRES Available PDCHs Channel Failure Alarm
R9305: Minimum Number of
Available PDCHs
Check whether DSP PSCELL TL9023: Throughput of Uplink ALM-22006 Cell PS Service
calls at a cell are GPRS RLC Data Blocks Faulty
faulty. TL9123: Throughput of
Downlink GPRS RLC Data
Blocks
TL9237: Throughput of Uplink
EGPRS RLC Data Blocks
TL9338: Throughput of
Downlink EGPRS RLC Data
Blocks
L9403: Total Bytes of Uplink
LLC PDUs Sent
L9503: Total Bytes of Downlink
LLC PDUs Received
2 Guide to Common Emergency Recovery
2.1 CS Services
3.1.1 Faulty CS Services
Symptom Fast Handling (Perform Operations in Sequence to Rectify the Fault)
Calls cannot be Low location update success rate

originated, certain If the location update success rate in a core network (CN) is low, the A interface cannot
immediate receive the location update request from the MSC. To rectify this fault, perform the
assignments fail, following operations
and the location
update success rate 1. Run the SET GCELLCCBASIC command with MS MAX Retrans set to
is low. The counter 1_Times(1_Times). Then, check whether services recover. (If services recover, set
RCA313: MS MAX Retrans to the original value.)
Assignment Success 2. Decrease the maximum number of channel request messages sent within a period as
Rate is involved. follows:
a For a BSC6000, run the MOD FCSW command with Channel Request CS
Domain Average Message Number of CPU0 In Period set to 100.
b For a BSC6900, run the SET BSCFCPARA command with Max CS CHAN
REQ Num in Period, Average PS CHAN REQ Num, and Max Location
Update REQ Num in Period all set to 10.
After services recover, set all the preceding parameters to their original values.
3. Block certain or all BTSs, unlock them one by one, and then check whether services
recover.
4. Run the SET GCELLCCBASIC command to set the classes of common access
control subscribers based on the number of subscribers of each class. This setting
prohibits the subscribers with low access control classes from accessing the network.
The access control classes are defined in subscriber registration information stored on
the CN.
Immediate assignment failures
1. Use the immediate assignment measurement data in periods with low immediate
assignment success rate to calculate the times of immediate assignment failures for
circuit services and location updates respectively as follows:
2020-4-12 Huawei Proprietary and Confidential 7

Ltd.
Circuit services: Times of immediate assignment failures = CA300J:

CELL_IMM_ASS_REQ – CA303J: CELL_IMM_ASS_SUCC
Location updates: Times of immediate assignment failures (location updates) =
A300F: CELL_CH_REQ_LOC_UPDATE – A3030F:
CELL_ESTB_IND_LOC_UPDATE_SD
If the times of immediate assignment failures caused by location updates account for
90% of the total failures, and the failures occur in certain cells, the fault is caused by
abnormal location updates. In this case, ask the R&D department to communicate
with the customer.
5. Perform the following operations:
c Check whether a large number of alarms, such as ALM-21001 LAPD Link
Congestion, ALM-20087 High BER over the E1/T1 Link, or ALM-20092 E1/T1
Excessive Bit Error Rate Per Hour, are generated on the BSC6000. Check whether
a large number of alarms, such as ALM-21511 LAPD Link Congestion, ALM-
20087 High BER over the E1/T1 Link, or ALM-20092 E1/T1 Excessive Bit Error
Rate Per Hour, are generated on the BSC6900.
If a large number of the preceding alarms exist, time delay and bit errors occur on
the Abis interface.
d Check whether the number of the alarms, such as ALM-1000 LAPD_OML Fault
and ALM-20249 Tributary Alarm Indication Signal (AIS) and the value of the
counter A300F: CELL_CH_REQ_LOC_UPDATE increase significantly on the
BSC6000; check whether the number of alarms such as 21807 OML Fault and
25801 E1/T1 Alarm Indication Signal and the value of the counter A300F:
CELL_CH_REQ_LOC_UPDATE increase significantly on the BSC6900.
If the preceding symptoms occur, intermittent disconnection occurs on the Abis
interface. In the preceding two scenarios, faults on the intermediate transmission
device must be rectified.
6. Check whether the values of the counters K3000: CELL_KPI_SD_REQ, K3004:
CELL_KPI_SD_TRAF_ERL, and K3014: CELL_KPI_TCH_TRAF_ERL_TRAF
increase significantly.
If the values increase significantly, a large number of MSs access the network. In this
case, rectify the fault based on step 5.
7. Check whether ALM-21504 MTP3 Signaling Link2 Congestion occurs and the value
of the counter L6016: MTP3_LNK_MSU_DISCARD is relatively large on the
BSC6000. Check whether ALM-21501 MTP3 Signaling Link Congestion occurs and
the value of the counter T6126: Number of Messages Discarded on MTP3 Link Due
to Link Congestion is relatively large on the BSC6900.
If the preceding symptoms occur, rectify the fault based on step 5.
8. If a large number of MSs access the network and the A interface is congested, rectify
the fault as follows:
a Run the following command to set the maximum retransmission times of the MS
to 1, and check whether services are recovered:
SET GCELLCCBASIC:MSMAXRETRAN=1_Times;
After services are recovered, set the maximum retransmission times of the MS to
the original value.
b Run the following commands to reduce the message arrival rate of channel
requests:

Ltd.
BSC6000: MOD FCSW: CHREQCSAVGMSGNUMINPERIOD=100;
BSC6900: SET BSCFCPARA: CHREQCSMAXMSGNUMINPERIOD=10,

LOCUPMAXMSGINPERIOD=10;
After services are recovered, set the message arrival rate of channel requests to the
original value.
c Block certain or all BTSs, unblock the BTSs one by one, and check whether
services are recovered.
9. Run the LST N7DPC and LST MTP3LKS commands to check whether the
signaling route mask and signaling link mask are configured correctly.
The correct number of 1s in the signaling route mask is n1 ( 2^n1 must be larger
than or equal to the number of routes). The correct number of 1s in the signaling
link mask is n2 (2^n2 must be larger than or equal to the number of links in a link
set). The AND operation between the signaling route mask and the signaling link
mask configured for the link set is equal to 0.
10.After the system upgrade, ZTR110A Success Rate of Call Setup (Immediate
Assignment) per BSC decreases; ZK3001 Failed SDCCH Seizures due to Busy
SDCCH per BSC is not significantly changed with comparison to the same period
before the system upgrade; A3040 Call Setup Indications Timed Out (SDCCH)
greatly increases. The indicator changes show that an MS camps on a cell with poor
signal quality after the system upgrade, which results in a low immediate assignment
success rate. Based on the indicators of the RA303G immediate assignment success
rate, filter top 10 to 20 cells with poor immediate assignment success rate. Enable the
MS to camp on a cell with better signal quality.
DEA GCELL:IDTYPE=BYID,CELLID=(involved cell ID)
ACT GCELL:IDTYPE=BYID,CELLID=(involved cell ID)
The preceding operations must be complete within 15 minutes. Then, check the
statistics of ZTR110A in the next 15-minute period. If the statistics are improved
significantly but are still not recovered to the expected values, filter top 10 to 20
cells with low RA303G immediate assignment success rate and perform the
preceding operations until the statistics of ZTR110A are recovered to the
expected value.
Calls cannot be 1. Check whether configuration operations are performed before the fault occurs.
originated and If configuration operations are performed, roll back the configuration if possible.
certain assignments
2. Check whether all assignment failures are caused by faulty devices based on the
fail. The counter
counter ZTA312L: Failed Assignments per BSC (Equipment Failure).
RCA313:
Assignment Success If all assignment failures are caused by faulty devices, perform the following steps in
Rate is involved. sequence. Check the result of each step before proceeding with the next step. The
procedure ends until the fault is rectified.
a Switch over the active and standby TNUs in all subracks.
b Switch over all the active and standby Abis interface boards.
c Switch over all the active and standby A interface boards.
d Switch over all the active and standby MPUs.
e Switch over all the active and standby Ater interface boards.
f Switch over all the active and standby SCUs.

Ltd.
g Reset the DPUc/DPUf boards one by one.

3. Run the LST SRCONPATH command to check whether paths are configured
between BM subracks. Run the DSP LINKBTNUTNU command to query the
connection status between subracks to check whether the TNU physical connection
between the BM subracks is correct.
If the connection between the BM subracks is incorrect, ALM-20231 Link Between
TDM Switching Boards in Different Subracks Faulty occurs. In the V009R013, the
BSC detects the connection status between subracks automatically. If the connection
is incorrect, ALM-21601 Inter-Subrack Connection Resources Exist Fault Alarm
occurs.
4. If the fault persists, report the debugging logs, configuration data, and traffic
measurement data to the R&D personnel for analysis.
5. In A over IP mode, if the cause value for assignment failures is Requested Speech
Version Unavailable (a large number of A3129S: Failed Assignments (Requested
Speech Version Unavailable) are measured) and the HR/FR AMR is used as the
speech version for assignments, check whether the Active Coding Set (ACS) collection
is set to SET1 on the wireless network and CN.
(SET GCELLCCAMR: IDTYPE=BYID, CELLID=*,ACTCDSETF=4_75KBIT/S-
1&5_15KBIT/S-0&5_90KBIT/S-1&6_70KBIT/S-0&7_40KBIT/S-1&7_95KBIT/S-
0&10_2KBIT/S-0&12_2KBIT/S-1;)
In A over IP mode, if the cause value for assignment failures is Invalid Message (a
large number of A3129J: Failed Assignments (Invalid Message) are measured), check
whether required IP paths are not configured and start a signaling tracing task for the
failed assignments. Find out the IP paths assigned by the MSC based on the tracing
result, and run the ADD IPPATH command to add the missing IP paths.
6. If the fault occurs in only peak hours, do as follows:
a Run the DSP CPUUSAGE command to query the digital signal processing (DSP)
usage of the DPUc/x/f.
If the DSP usage on all boards is close to or equal to 95%, DSP resources are
insufficient and boards must be added.
b Run the DSP ATERTS command to check the Ater resource usage.
If no idle Ater resource exists, Ater resources are insufficient. Ports or boards
must be added, or BTSs must be relocated to other subracks.
c Check whether all failed calls are inter-subrack calls.
If a failed call is an inter-subrack call, the BM subrack mapping to the assigned
CIC number is not the subrack that houses the BTS, or the resource query of a
single user indicates an inter-subrack call.
Check whether the DPUP is absent whereas the BM subrack for PS services
exists.
If such situation occurs, insert a DPUP in the BM subrack and run the SET
PSCELLTODSP command.
d In the remote TC subrack, check whether Ater links are congested (whether ALM-
21511 LAPD Link Congestion is generated) or the number of Ater links meets
product configuration requirements. If Ater links are congested or the number of
Ater links does not meet requirements, run the ADD ATERSL command to add
Ater links.
e If the cause value for all assignment failures is No Abis Resource
Ltd.
Available (a large number of A312F: Number of Assignment

Failures (No Abis Resource Available) are measured), perform the
following operations:
 If a cell is enabled with the Flex Abis feature, run the LST
BTSIDLETS command to check whether idle timeslots are
configured. If idle timeslots are configured, run the SET
BTSIDLETS command to delete them.
 If the site where assignment failures occur uses IP
transmission, query the port bandwidth as follows:
Scenario 1: The Abis interface on the BSC uses IP over FE/GE
transmission. All the BTSs involved in assignment failures are
connected only to one or several ports.
(1) Run the DSP ETHPORT command to obtain the status of
the port connecting to the problem BTSs. Record the value of
Speed in the command output.
(2) Obtain the counters of IP Transport Adjacent Node
Resource Operation Measurement (ANIIPTRM). Among the
counters, check whether a large number of T6511: Number of
Failed Resource Allocations Due to Insufficient Bandwidth on
the IP Transport Adjacent Node are measured on the problem
BTSs.
(3) Add up the values of the counter T6509: IP Path Forward
Bandwidth Allocated to IP Transport Adjacent Node measured
on the BTSs connected to the port. If the ratio of the sum
result to the value of Speed recorded in step (1) exceeds
95%, the assignment failures are caused by unavailability of
Abis resources. To resolve this problem, adopt any of the
three solutions as follows:
- Adopt solution 1 if the port rate is 1000 Mbit/s.
- If the port rate is 100 Mbit/s, check whether the port
supports the rate 1000 Mbit/s.
 If yes, adopt solution 2.
 If no, adopt solution 3.
Solution 1: Migrate certain BTSs connected to this port to
another port while ensuring that the sum of the values of
T6509: IP Path Forward Bandwidth Allocated to IP Transport
Adjacent Node measured on each port is 70% less than the
port rate.
Solution 2: Check whether the peer end (a port on a data
communication device that is connected to a BSC port)
supports the rate 1000 Mbit/s. If the peer end does not
support this rate, replace the peer-end port with one
supporting the rate. In this case, an autonegotiation port is
recommended. Furthermore, if the peer-end port works in
forced full duplex mode, the BSC port must be set to the
forced full duplex mode and support the rate 1000 Mbit/s. If
the peer-end port cannot be replaced, adopt solution 1.
Solution 3: Replace the BSC port with one supporting the rate
Ltd.
1000 Mbit/s, and configure this port with the same

negotiation mode as the peer-end port. Alternatively, perform
these operations after implementing solution 1.
Scenario 2: BTSs supporting the IP over E1 mode and BTSs
connected to different ports are deployed.
(1) Obtain the value of the counter T6509: IP Path Forward
Bandwidth Allocated to IP Transport Adjacent Node. If the
value of this counter reaches the bandwidth configured for
the E1 port, IP path, or logical port, do as follows:
- If the logical port is configured, check the value of TRM
load threshold index. If the value of TRM load
threshold index is 2, change it to 3. If the value of TRM
load threshold index is 3, go to the next step.
The unit of the bandwidth on the logical port is 64 kbit/s. Ensure
that the bandwidth for the logical port equals that for the
physical link.
- If no logical port is configured, add the logical port, and
set TRM load threshold index to 3. If the problem
persists, go to the next step.
(2) For BTSs supporting the IP over E1 mode, calculate the
bandwidth for the IP path and logical port using the following
formula: Bandwidth for the IP path and logical port = 64
kbit/s x Number of timeslots provided by the E1 port
(3) For BTSs supporting the IP over FE mode, you are advised
to configure at least 10 MHz bandwidth for the IP path and
logical port.
f If the POUc is used as the Abis interface board, check the number
of TRXs configured for the POUc. If the POUc boards work in
active/standby mode, verify that the POUc boards are configured
with 512 TRXs at most. If the POUc boards work in independent
mode, verify that the POUc boards are configured with 256 TRXs
at most. In addition, check whether ALM-21604 Insufficient
Transmission Resources is reported and whether the log records
the event of insufficient low voltage differential signal (LVDS)
links. If the event is found in the log, cut over the BTSs connected
to the Abis interface board with insufficient LVDS links to another
interface board of the serving BSC, block non-VIP BTSs, or turn on
the LVDS preemption switch as follows:
 For BSC6900 V900R013, run the following command:
SET SS7PATCHSWITCH: SwitchParameter16=1;
 For BSC6900 V900R014, run the following command:
SET BSCBASIC: ENPREEMPTABISLVDSADMT=ON;
ALM-21604 Insufficient Transmission Resources was introduced in BSC6900 V900R014.
Calls cannot be 1. Check whether configuration operations are performed before the fault occurs.
originated and all If configuration operations are performed, roll back the configuration if possible.
assignments fail.
7. Check whether a large number of assignment failures are caused by faulty devices
Ltd.
The counter based on the counter ZTA312L: Failed Assignments per BSC (Equipment Failure).
RCA313: If the assignment failures are caused by faulty devices, switch over all TNUs. If the
Assignment Success fault persists, reset the DPUc/x/f one by one.
Rate is involved.
8. Trace signaling on the Abis interface and the BSSAP signaling on the A interface at
the faulty cell for three minutes, and reset the subrack.
The number of 1. Run the LST GCELLHO2GBA2 command to check whether the BA2 table is
outgoing handovers manually generated.
decreases or the When frequencies between the local cell and a neighbor cell are different, frequencies
handovers fail. The recorded in the BA2 table of a system message vary from the actual frequencies at the
counters CH310: neighbor cell. As a result, handover cannot be initiated. You must run the SET
Number of Outgoing GCELLHO2GBA2 command to manually generate the BA2 table.
Internal Inter-Cell
9. Run the SET GCELLIDLEBASIC command to check whether NCCPERMIT is set
Handover Requests
to 1.
and TH313: Success
Rate of Outgoing If NCCPERMIT is not set to 1, change the value as required.
Internal Inter-Cell 10.Trace signaling on the Abis interface and the BSSAP signaling on the A interface at
Handovers counters the faulty cell for 10 minutes, and report the trace information to the R&D personnel
are involved. for analysis.
Paging issues (The Based on the following conditions 1 to 5, determine the points where paging messages
paging success rate are discarded. Then, adjust related parameters based on detailed causes. If multiple
of the CN conditions among conditions 1 to 4 are met, the current paging amount has exceeded the
decreases.) processing capability of the BSS. In this situation, decrease the paging amount on the
MSC first by performing the following operations: 1. Disable entire-network paging.
Enable paging by LA. Set the paging interval to a value greater than 5s. 2. Disable
secondary paging if the paging issue is serious, and enable TMSI-based paging. (These
operations are performed on the CN. For detailed commands, see the configurations of
the specific CN vendors.)
1. If the following symptoms occur, the number of paging messages exceeds the paging
message transmission threshold specified over the air interface on the BTS. The BTS
discards certain paging messages. To resolve this issue, you can configure the
extension BCH function or splitting LAC function.
A337: Number of Deletions of the Paging for CS Services on the PCH is much larger
than 0; or A338: Number of Expiries of the Paging for CS Services on the PCH is
much larger than 0.
A339: Number of Deletions of the Paging for PS Services on the PCH is much larger
than 0; or A340: Number of Expiries of the Paging for PS Services on the PCH is
much larger than 0.
2. If A0300 (Number of MSC-initiated CS paging requests) + A0301 (Number of
SGSN-initiated CS paging requests) is much larger than A032 (Number of BSC MSC
PAGING REQ CS), the A interface-level flow control discards the paging messages
of CS services.
 For the BSC6000:
Adjust Max CS Paging Message Num in Period. In this way, the message arrival rate-
based flow control on the BSC is minimized (according to the empirical value on the
existing network, the maximum number of paging messages of CS services can be
adjusted from 160 to 330 in the multi-LAC scenario).
Adjust the number of paging messages of CS services over the A interface. Set Max

Ltd.
CS Paging Message Num in Period in SET BSCFCPARA to the number of LACs x

160. If the extension BCH function is enabled, set Max CS Paging Message Num in
Period to the number of LACs x 160 x 2.
Run the SET BSCFCPARA: PGCLASSIFINGALLOWED=2 command to enable
the secondary paging flow control to restrict the number of secondary paging services.
By preferentially performing the flow control on the secondary paging services, the
BSC load is decreased.
3. The CPU load is unbalanced. As a result, paging messages or paging response
messages are discarded due to the flow control.
Fault-locating methods:
Check whether ALM-21210 CPU Overload is generated or the CPU load statistics
collected in the performance measurement indicate that the CPU is overloaded (check
CPU traffic measurement counter R9703: The max usage of CPU. If the CPU peak
usage of the XPU board reaches 85, you can consider that the flow control is
implemented due to CPU overload).
If the CPU is overloaded, a large number of paging messages may be discarded on the
LAPD link (you can confirm the message discarding with traffic measurement
counter A351: Number of Discarded Re-paging Messages for CS Services or A352C:
PCH AGCH AVG QUEUE LEN).
Handling suggestions:
Ensure that RSL links managed by CPUs on the XPUT are distributed evenly. If the
RSL links are not distributed evenly, deploy a pseudo site and migrate the RSL links
to the pseudo site to achieve even distribution.
Fault-locating methods:
Check whether ALM-20256 CPU Overload is generated. Obtain the total traffic
volume of BTSs managed by the CPUSs on each XPU. If the average CPU usage of
the CPUSs with heavy traffic volume exceeds 75% and the CPU usage difference
between CPUSs is large (the CPU usage difference exceeds 20%), adjust the
unbalanced CPU usage among CPUSs.
Handling suggestions:
a If the CPU usage of the XPU on the BSC is high continuously, decrease the values
for Max CS Paging Message Num in Period and Max PS Paging Message Num
in Period.
b If the CPU usage of certain CPUS is high, run the LST BTSCTRL command to
query the IDs of the CPUSs to which the BTSs belong. Run the SET
BTSCTRLEX command to migrate the BTSs on the CPUSs with heavy traffic
volume to the CPUSs with light traffic volume.
4. If the traffic statistics of A531: CS Pagings Discarded on LAPD Link or A532: PS
Pagings Discarded on LAPD Link are greater than 0 or ALM-21001 LAPD Link
Congestion (BSC6000) or ALM-21511 LAPD Link Congestion (BSC6900) is
generated, paging messages are discarded on the LAPD link.
Enable the cell paging package over the Abis interface to ease the LAPD link
congestion.
Increase the LAPD Congestion Start Threshold and Congestion End Threshold to
95% and 90% respectively.
Ltd.
When the transmission delay over the Abis interface is long, adjust the sliding
window of the RSL from 4 to 8.
It is recommended that you adjust the RSL multiplexing ratio of cells with a large
number of paging messages from 2:1 to 1:1.
5. In the MSC Pool scenario, check whether the TMSI in the A interface paging
messages is identical with that of the corresponding MSC to ensure that the MSC with
paging response to the TMSI sent from the BSC is the same as the MSC in the paging
delivery.
1. Check whether the GOUc is connected to a router of Cisco.
If it is connected to a router of Cisco, check whether the attribute of the router's port
that is connected to the GOUc is DOWN. If the port attribute is DOWN, run the
The A interface is following commands in the interface view of the Cisco router:
interrupted. Router>en //Enter the EXEC mode.
The A interface is password:xxxxxx //Key in the password.
carried by the Router# config terminal //Enter the global configuration mode.
GOUc, on which the
signaling and Router(config)#interface gigabitethernet0/0 //Enter the interface of the router.
services are Router(config-if)#undo shutdown
interrupted and Router(config-if)#exit //Exit the port mode.
ALM-21345
Ethernet Link Fault 2. Run the LST ETHPORT command to query the value of Auto negotiation of the
is reported. interrupted A interface. Then, run the SET ETHPORT command to change the value
of this parameter as follows:
 If the queried value is ENABLE, change the value to DISABLE.
 If the queried value is DISABLE, change the value to ENABLE.
3.1.2 Faulty SS7 Links

Symptom Fast Handling (Perform Operations in Sequence to Rectify the
Fault)
The combination subrack is 1. Select a faulty SS7 link, and trace the MTP2, MTP3, and SCCP messages
configured. The SS7 links are on the A interface for 5 minutes.
congested or intermittent 11.Check whether transmission alarms occur on the A interface of the faulty
disconnection occurs. The SS7 link.
alarm ALM-21501 MTP3 You can run the LST MTP3LNK command to query the following
Signaling Link Congestion information about the A interface that is configured for the MTP3 link:
occurs or the alarm ALM-
20271 Statistical Alarm − Subrack number of port A
indicates that the alarm ALM- − Slot number of port A
21501 MTP3 Signaling Link − Port A number
Congestion occurs.
− Timeslot mask of the A interface
12.If the signal link is congested, run the LST N7DPC and LST MTP3LKS
command to check whether the signaling route mask and signaling link
mask are configured correctly.
The correct number of 1s in the signaling route mask is n1 (2^n1 must
be greater than or equal to the number of routes). The correct number
Ltd.
Fault)
of 1s in the signaling link mask is n2 (2^n2 must be greater than or

equal to the number of links in a link set). The AND operation
between the signaling route mask and the signaling link mask
configured for the link set is equal to 0.
13.If the faulty SS7 links are distributed on multiple A interface boards on
the BSC, assist MSC engineers to rectify the fault.
You can run the LST MTP3LNK command to query the following
information about the A interface board carrying the MTP3 link:
− Subrack number of port A
− Slot number of port A
14.Check whether all SS7 links on the peer interface board are faulty. If all
SS7 links are faulty, reset the peer interface board. Check whether the
peer interface board resets repeatedly. If the peer interface board resets
repeatedly, assist related engineers to rectify the fault.
15.If all SS7 links configured on an A interface board are faulty, reset the A
interface board.
information about the A interface that is configured for the MTP3 link:
− Subrack number of port A
− Slot number of port A
16.Switch over transmission links.

17. If all SS7 links configured on an XPU are faulty, switch over the XPUs.
If the switchover fails, run the RST BRD command to reset the active
XPU. If the RST BRD command execution fails due to timeout or other
causes, run the RST JTGBRD SRN=0, SN=0; command to reset the
XPU (set the Description file parameter by referring to the MML online
help). If the RST JTGBRD command is unavailable (in versions earlier
than R13), remove and then insert the XPU. If the fault persists, run the
INH BRD: INHT=PHYSICAL; and UIN BRD: UINT=PHYSICAL;
commands to inhibit and uninhibit the XPU, respectively.
information about the XPU carrying the MTP3 link:
− Subrack number
− Slot number
18.(Primary operation) Run the DEA BTS command to deactivate BTSs,

and run the ACT BTS command to activate the BTSs in batches after
recovery.
(Backup operation) Run the following commands to reduce the message
arrival rate of channel requests:

Then, check whether services recover.

19.Check whether the values of MTP2.LNK.RATIO.TX and
MTP2.LNK.RATIO.RX are greater than 20% during peak hours.
Ltd.
Fault)
If both values are greater than 20%, add SS7 links to ensure the values
are less than20%.
20.Perform loopback tests to locate the fault.
Check whether the fault occurs on the BSC.
Run the SET E1T1LOP command to perform a local loopback test for
the port corresponding to the A interface board in the TC subrack. If the
rate of the MTP3 link is 64 kbit/s, set Loop type to
SIN_CHN_LOC(single channel local loop).
Run the DSP MTP2LNK command to query the MTP2 link status.
If the link status is IN SERVICE, the fault occurs outside the BSC. In
this case, perform loopback tests on different line segments between the
BSC and MSC to check the MTP2 link status.
If the MTP2 link status is abnormal during a loopback test on a specific
line segment, the fault occurs on the BSC. In this case, switch over the A
interface boards carrying the MTP2 link.
Separate subracks are 1. Select a faulty SS7 link, and trace the MTP2, MTP3, and SCCP messages
configured. The SS7 links are on the A interface for 5 minutes.
congested or intermittent 21.Check whether transmission alarms occur on the A interface and Ater
disconnection occurs. The interface of the faulty SS7 link.
alarm ALM-21501 MTP3 You can run the LST MTP3LNK command to query the following
Signaling Link Congestion information about the A interface that is configured for the MTP3 link:
occurs or the alarm ALM-
20271 Statistical Alarm − Subrack number of port A
indicates that the alarm ALM- − Slot number of port A
21501 MTP3 Signaling Link − Port A number
Congestion occurs.
− Timeslot mask of the A interface
You can run the LST MTP3LNK command to query the index number
of the Ater connection path that is configured for the MTP3 link. Then
you can run the LST ATERCONPATH command to query the Ater
interface that is configured for the BM and TC subracks housing the link
based on the obtained index number.
22.If the signal link is congested, run the LST N7DPC and LST MTP3LKS
mask are configured correctly.
The correct number of 1s in the signaling route mask is n1 ( 2^n1 must
be greater than or equal to the number of routes). The correct number
of 1s in the signaling link mask is n2 (2^n2 must be greater than or
equal to the number of links in a link set). The AND operation
between the signaling route mask and the signaling link mask
configured for the link set is equal to 0.
23.If the transmission on the Ater interface board in a BM subrack is faulty
and multiple Ater interfaces are configured on the live network, move the
SS7 links from the faulty Ater interface board to other Ater interface
boards.
24.If the faulty SS7 links are distributed on multiple Ater interface boards,
assist MSC engineers to rectify the fault.
25.If all SS7 links configured on an Ater interface board in a BM subrack

Ltd.
Fault)
are faulty, switch over the Ater interface boards.
You can run the LST MTP3LNK command to query the index number
of the Ater connection path that is configured for the MTP3 link. Then
you can run the LST ATERCONPATH command to query the Ater
interface that is configured for the BM subrack housing the link based on
the obtained index number.
26.If all SS7 links on the peer interface board are faulty, reset the peer
interface board and check whether the peer interface board switches
repeatedly.
27.Switch over transmission links.
28.If all SS7 links configured on an XPU are faulty, switch over the XPUs.
If the switchover fails, run the RST BRD command to reset the active
XPU. If the RST BRD command execution fails due to timeout or other
causes, run the RST JTGBRD SRN=0, SN=0; command to reset the
XPU (set the Description file parameter by referring to the MML online
help). If the RST JTGBRD command is unavailable (in versions earlier
than R13), remove and then insert the XPU. If the fault persists, run the
INH BRD: INHT=PHYSICAL; and UIN BRD: UINT=PHYSICAL;
information about the XPU carrying the MTP3 link:
−Subrack number
−Slot number
29.(Primary operation) Run the DEA BTS command to deactivate BTSs,
and run the ACT BTS command to activate the BTSs in batches after
recovery.
(Backup operation) Run the following commands to reduce the message
arrival rate of channel requests:

Then, check whether services recover.

30.Check whether the values of MTP2.LNK.RATIO.TX and
MTP2.LNK.RATIO.RX are greater than 20% during peak hours.
If both values are larger than 20%, add SS7 links to ensure that the
values are less than 20%.
31.Run the SET E1T1LOP command on the port corresponding to the Ater
interface board to check whether the MTP2 link runs properly.
If the MTP2 link runs properly, the BSC is normal. You must perform
loopback tests on different line segments between the BSC and the MSC
to check the MTP2 link status. If the MTP2 link status is abnormal
during a loopback test on a specific line segment, the fault occurs on the
segment.
32.Perform loopback tests to locate the fault.
a Check whether the fault occurs on the BSC.
Run the SET E1T1LOP command to perform a local loopback test
Ltd.
Fault)
for the port corresponding to the A interface board in the TC subrack.

If the rate of the MTP3 link is 64 kbit/s, set Loop type to
SIN_CHN_LOC(single channel local loop).
Run the DSP MTP2LNK command to query the MTP2 link status.
If the link status is IN SERVICE, the fault occurs outside the BSC.
In this case, perform loopback tests on different line segments
between the BSC and MSC to check the MTP2 link status.
If the MTP2 link status is abnormal during a loopback test on a
specific line segment, the fault occurs on the BSC. In this case,
perform the next step.
b Check whether the fault occurs in the BM subrack.
Perform a loopback test on the Ater interface in the BM subrack to
query the MTP2 link status. If the MTP2 link status is abnormal,
switch over the Ater interfaces in the BM subrack. If the MTP2 link
status is normal, the fault does not occur in the BM subrack. In this
case, perform the next step.
c Check whether the fault occurs on the transmission side or the TC
subrack.
Perform a loopback test on the Ater interface in the TC subrack to
query the MTP2 link status. If the MTP2 link status is normal, switch
over the Ater interfaces in the TC subrack. If the MTP2 link status is
abnormal, the fault occurs on the transmission side. In this case, you
must perform loopback tests along the line to check the MTP2 link
status in each line segment and locate the fault.
The A interface is unavailable 1. Trace the MTP3 and SCCP signaling to check whether only uplink traffic
and the peer CN is provided by exists at the SCCP layer.
vendor Ericsson or NSN. 33.If the device is connected to a CN provided by vendor Ericsson, check
whether the UMG or MSC connects to other BSCs. If other BSCs are
faulty, reset the peer interface board or the peer device.
A interface disconnection: 1. Verify that the GOUc is connected to a Cisco's router.
Signaling and services are 2. Check the setting of the port on the Cisco router that connects to the
suspended on the GOUc which GOUc board. If the port attribute is set to DOWN, run the undo
bears the A interface, and the shutdown command on the port setting window of the router.
GOUc reports ALM-21345 Router>en //Enter the EXEC mode.
Ethernet Link Fault.
password:xxxxxx //Type the password.
Router# config terminal //Enter the global configuration mode.
Router(config)#interface gigabitethernet0/0 //Enter the port setting window.
Router(config-if)#undo shutdown
Router(config-if)#exit Exit from the port mode.
The SCTP link is interrupted, and 1. Select a faulty SCTP link, and trace the SCTP, M3UA, and SCCP
the alarms ALM-21541 SCTP messages on the A interface for 5 minutes.
Link Fault and ALM-21542 2. If the SCTP link is a new one, check whether the IP address/port
SCTP Link Congestion are numbers for both sides of the SCTP link are consistent with those
generated. configured for the CN.
3. Run the Ping command to check whether the transmission is normal.
Ltd.
Fault)
You can run the LST SCTPLNK command to query the local IP address of
the SCTP link. Then, run the LST ETHIP or LST DEVIP command to
query the subrack number and slot number of the A interface board based on
the obtained local IP address.
4. If the SCTP link is congested, run the LST N7DPC and LST M3LKS
mask are correctly configured. The correct number of 1s in the signaling
route mask is n1 (2^n1 must be greater than or equal to the number of
routes). The correct number of 1s in the signaling link mask is n2 (2^n2
must be greater than or equal to the number of links in a link set). The
AND operation between the signaling route mask and the signaling link
mask configured for the link set is equal to 0.
5. If all SCTP links configured on an interface board are faulty, switch over
the interface boards.
You can run the LST SCTPLNK command to query the local IP address of
the SCTP link. Then, run the LST ETHIP or LST DEVIP command to
query the subrack number and slot number of the A interface board based on
the obtained local IP address.
6. If all SCTP links configured on an XPU are faulty, switch over the
XPUs.
You can run the LST SCTPLNK command to query the following
information about the XPU carrying the SCTP link:
− Subrack number
− Slot number
7. If no operation is performed for the SCTP link and the link interruption
is caused by a network upgrade or reconstruction, check whether the
SCTP link works in client mode on both the BSC and CN sides. If the
SCTP link works in client mode on both sides, modify the work mode of
the SCTP link to allow it to work in server mode on the CN side.
You can run the LST SCTPLNK command to check whether the value
of MODE is CLIENT(CLIENT MOD) for the SCTP link on the BSC
side. Check the work mode of the SCTP link on the CN side. If required
information on the CN side is unavailable, check the work mode of the
SCTP link based on traced signaling messages of the faulty SCTP link.
If the INIT messages can be received from the CN side, the SCTP link
works in client mode on the CN side.
8. Query the traced signaling messages of the SCTP link. If the link
establishment message is sent only on the local end and the SCTP link is
interrupted by the Abort message received from the peer end during
message exchanging, contact the engineers responsible for the peer end
for fault analysis.
9. Check whether the number of IP addresses on the local end is the same
as that on the peer end for an SCTIP link if both of the following
conditions are met:
The local end responds with an Abort message after receiving a
Ltd.
Fault)
COOKIE ACK message from the peer end during a 4-way handshake.
The SCTP link works in server mode, which can be obtained based on
15.
For example, if two local IP addresses and two peer IP addresses are
configured for the local end and only one local IP address and one peer
IP address are configured for the peer end, the number of IP addresses is
inconsistent between both sides. In this case, modify the IP address
configurations to ensure that both sides are configured with the same
number of IP addresses.
2.1.1 Interrupted TC Subracks

Fault)
The remote TC subrack and 1. Check whether the alarm ALM-20261 Ater OML Faulty is cleared.
Ater interface board provide 34.Check the transmission status (check whether transmission alarms occur
optical interfaces. Indicators on on the BSC).
all boards in the TC subrack 35.Remove Ater interface boards that are inserted in odd-number slots in the
turn red. The Ater operation and TC subrack and carry the Ater OMLs.
maintenance links (OMLs) are
You can run the LST ATERCONPATH command to query the slot
interrupted.
number of an Ater interface board.
If operations cannot be immediately performed on the TC subrack,
remove Ater interface boards in odd-number slots in the BM subrack.
36.Power off and power on the TC subrack.
37.Check the intermediate transmission device.
The remote TC subrack and 1. Check whether the alarm ALM-20261 Ater OML Faulty is cleared.
Ater interface board provide 38.Check the transmission status (check whether transmission alarms occur
electric interfaces. Indicators on on the BSC).
all boards in the TC subrack 39.Remove active Ater interface boards that are inserted in the TC subrack
turn red. The Ater OMLs are and carry the Ater OMLs.
interrupted.
If the fault persists, insert the removed boards. After the board runs
properly, remove another board and check whether the fault is rectified.
40.Power off and power on the TC subrack.
41.Check the intermediate transmission device.
3.1.3 TC DSP Failures

Symptom Troubleshooting Procedure
The TC digital signal processors 1. If the DSPs that are reset repeatedly are located on the same DPU, check
(DSPs) are reset repeatedly, the whether the SET TCTYPE command is executed based on the operation
TC DSPs fail, or the alarm logs. If SET TCTYPE is not executed, reset the DPU. If the fault
ALM-20243 Board Hardware persists, replace a DPU.
Fault is generated. 2. If the DSPs that are reset repeatedly are located on different DPUs and
Ltd.
the reset time is different, check whether the TC-related functions are
enabled based on the operation records and configuration information. If
the TC-related functions are enabled, disable these functions and check
whether the DSPs work properly.
3. Run the LST GCELLCCACCESS command to check whether the WB-
AMR (full rate voice version 5) is enabled. If the WB-AMR is enabled,
disable it and check whether the DSPs work properly.
4. In the AoTDM scenario, if no configuration operation is performed,
check whether the voice quality enhancement (VQE) is enabled (check
whether the VQE parameters are set to ON, for example, SET
TCPARA: AecEnFlag=ON, AlcEnFlag=ON, AncEnFlag=ON,
EVADEnFlag=ON, TFOOptSwitch=ON, EPLCSwitch=ON). If the
parameters are set to ON, set these parameters to OFF.
5. In the AoTDM scenario, if the tandem free operation (TFO) is enabled,
run the SET GCELLBASICPARA command with
NBAMRTFOSWITCH set to DISABLE to disable the TFO.
6. Disable the DSP self-healing function. Check whether the DSPs work
properly.
SET TCPARA: SELFHEALINGSWITCH=SELFHEAL0-0
&SELFHEAL1-0&SELFHEAL2-0&SELFHEAL3-0&
SELFHEAL4-0&SELFHEAL5-0&SELFHEAL6-0&SELFHEAL7-0;
2.1.2 Faulty Voice Services

Fault)
Noise, one-way audio, or no BSC6000:

audio occurs. If the fault range cannot be determined based on the one-way audio logs and
loopback tests and the probability of one-way audio faults is high,
preferentially perform the following operations to rectify the fault:
(1) Switch over the TNUs in the BM and TC subracks. Additionally, if IP
or High-Level Data Link Control (HDLC) transmission is used, switch
over both the TNUs and SCUs in the BM and TC subracks.
(2) Switch over the Abis, Ater, and A interface boards.
(3) Reset all DPUs where voice service faults have occurred or reset all
DPUs in sequence. Notify the customers of the board reset in advance
because voice services will be interrupted during DPU reset.
1. Perform the following operations as required:
a In TDM mode, enable the level-2 one-way audio detection function.
You can press Ctrl+Shift+F12 to enter the superuser window, and
configure the following parameters in the Inner Software
Parameters tab page:
− Speech Channel Alarm Threshold
− Speech Channel Resume Alarm Threshold
− Tc Mute Detect Class1 Threshold(%)
You can also configure the following cell parameters:

Ltd.
Fault)
− Tc Mute Detect Flag

− Mute Detect Class2 Switch
− Period of Mute Detect Class1
− Exceptional Frame Threshold (%)
− Period of Detect Frame[0.25s]
− Mute Detect Time
Twenty minutes later, analyze the one-way audio logs to locate the
public resources with one-way audio faults. Then, switch over, reset,
or replace the boards that provide these cross-connect resources.
b In Abis over IP or A over IP scenarios, run the PING IP command to
ping 100 packets for five consecutive times.
The DSCP value used for the Ping test is the value mapping to the
voice service (which is set to 46 by default). You must check whether
packet loss (larger than 0.1%) and excessive time delay (more than
80 ms for terrestrial transmission and 700 ms for satellite
transmission) occur. If packet loss or excessive time delay occurs,
switch over the interface boards. If the fault persists, contact
engineers related to intermediate transmission devices for help.
c Run the BLK ACIC command to block related timeslots if the
average occupied duration of the A interface specified in KPIs
AL0001 to AL0031 is shorter than that of other timeslots or is shorter
than 30s.
2. Analyze alarm logs to check whether transmission alarms occur in the
public resources specified in step 1.
If transmission alarms occur, block related resources and contact
transmission engineers for help.
3. Perform drive tests, and choose BSC Maintenance > Maintenance User
Resource > Query Single User Resource from the menu to query the
call resources of a single user after the fault re-occurs.
If the voice channel is in idle state, the uplink channel between the DPU
and the BTS is faulty. You must perform loopback tests manually to
locate the fault, switch over, reset, or replace the boards that provide the
public resources, or block the resources.
4. If the faults occur on a specific BTS, run the RST BTS command to reset
the BTS.
BSC6900:
If the fault range cannot be determined based on the one-way audio logs and
loopback tests and the probability of one-way audio faults is high,
preferentially perform the following operations to rectify the fault:
(1) Switch over the TNUs in the BM and TC subracks. Additionally, if IP
or HDLC transmission is used, switch over both the TNUs and SCUs in
the BM and TC subracks.
(2) Switch over the Abis, Ater, and A interface boards.
(3) Reset all DPUs where voice service faults have occurred or reset all
DPUs in sequence. Notify the customers of the board reset in advance
Ltd.
Fault)
because voice services will be interrupted during DPU reset.

1. Perform the following operations as required:
a In TDM mode, enable the level-2 one-way audio detection function.
You can run the SET BSCINNSOFT command on the Web LMT to
configure the following parameters:
− Speech Channel Alarm Clearance Threshold
Then, you can also run the SET GCELLSOFT command to
− Exceptional Frame Threshold of Mute Detect Class1
− Period of Mute Detect Class2 TRAU Frame
In A over IP scenarios (in V009R013 or later versions), enable the
one-way audio detection function. You can run the SET
BSCINNSOFT command on the Web LMT to configure the
following parameters:
− Speech Channel Alarm Clearance Threshold
Then, you can also run the SET GCELLSOFT command to
− Exceptional Frame Threshold of Mute Detect Class1
Twenty minutes later, analyze the one-way audio logs to locate the
public resources with one-way audio faults. Then, switch over, reset,
or replace the boards that provide these public resources.
b In Abis over IP or A over IP scenarios, run the PING IP command to
ping 100 packets for five consecutive times.
The DSCP value used for the Ping test is the value mapping to the
voice service (which is set to 46 by default). You must check whether
packet loss (larger than 0.1%) and excessive time delay (more than
80 ms for terrestrial transmission and 700 ms for satellite
transmission) occur. If packet loss or excessive time delay occurs,
switch over the interface boards. If the fault persists, contact
engineers related to intermediate transmission devices for help.
If IP transmission is used, check whether the VLAN configuration
and ID on the BSC are consistent with those on the transmission
network.
c Run the BLK AE1T1 command to block related timeslots if the
average occupied duration of the A interface specified in KPIs
AL0001 to AL0031 is shorter than that of other timeslots or is shorter
Ltd.
Fault)
than 30s.
42.Analyze alarm logs to check whether transmission alarms occur in the
public resources specified in step 1.
If transmission alarms occur, block related resources. If the fault persists,
contact transmission engineers for help.
43.Perform drive tests, and run the DSP CALLRES command on the Web
LMT to query the call resources of a single user after the fault re-occurs.
If the voice channel is in idle state, the uplink channel between the DPU
and the BTS is faulty. You must run the STR CALLRESLOP command
manually to locate the fault, switch over, reset, or replace the boards that
provide the public resources, or block the resources.
44.If the faults occur on a specific BTS, run the following command to reset
the BTS:
RST BTS: TYPE=BTSSOFT, IDTYPE=BYID, BTSID=***, LEVEL=4-LEVEL;
3.2 PS Services
3.2.1 Faulty PS Services and PDCH Faults
Common 1. If UmVer is set to GSM_PHASE_1, change the value to GSM_PHASE_2Plus.

parameter check Related commands:
operations
LST/SET BSCBASIC:
UmVer=GSM_PHASE_2Plus,AbisVer=GSM_PHASE_2Plus,AVer=GSM_PHASE_2
Plus;
11.If NMO is set to NMOIII, change the value to NMOII.
Related commands:
LST/SET GCELLPSBASE: IDTYPE=BYID, CELLID=**, NMO=NMOII;
12.Add paths between the TNU subracks that house the DPUd or DPUg.
Related commands:
LST/ADD SRCONPATH;
13.If PRIACCTHR is not set to 6, change the value to 6.
Related commands:
LST/SET GCELLPSBASE: PRIACCTHR=6
14.If the number of PTP BVCs exceeds the specifications, decrease the number of PTP
BVCs to ensure that it complies with the specifications. The specifications in different
versions are as follows:
All V900R011 and V900R012 patch versions earlier than V900R012C01SPC500:
2048

Ltd.
V900R012C01SPC550 and later V900R012C01 patch versions: 10480

All V900R013 versions: 10384
Related commands:
RMV PTPBVC
A PDCH in a PS 1. If the inter-subrack connection paths between TNUs are not configured, run the
cell in a subrack following command to add these paths:
becomes faulty in LST/ADD SRCONPATH;
Abis over TDM
mode. As a result, 45.Run the following command to check whether the TNU port is normal:
network access DSP LINKBTNUTNU;
fails. 46.Move the PS cell to the digital signal processor (DSP) in a subrack with cells that
provide services properly, and check whether the fault is rectified.
Related commands:
DSP/SET PSCELLTODSP;
A PDCH becomes When IP MUX is enabled, run the STR CALLRESLOP: LOPLOC=NSSAINTF,
faulty in Abis over LOPDIR=MSC; or STR CALLRESLOP: LOPLOC=NSSAINTF, LOPDIR=MSC;
IP mode. command to enable speech loopback. Due to software defects, the low-priority PS data is
discarded during flow control. As a result, the PDCH becomes faulty.
Workarounds:
1. Run the SWP BRD: SRN=XX, SN=YY; command to switch over the interface
boards.
2. Disable both of the IP MUX and speech loopback functions.
Related commands:
RMV IPMUX: IPMUXINDEX=x;
RMV BTSABISMUXFLOW
STP CALLRESLOP
A PDCH becomes When the BTS uses terrestrial transmission and the loopback delay is longer than 280 ms,
faulty in Abis over a PDCH cannot be activated. As a result, the PDCH becomes faulty and the ping delay
IP mode. fluctuates.
Workarounds:
1. Change the transmission mode from terrestrial transmission to satellite transmission
by running the following command:
SET BTSTRANS: IDTYPE=BYID, BTSID=x, TransMode=SAT_TRANS;
2. Adjust the transmission mode to reduce the loopback delay.
A PDCH becomes The negotiation result is inconsistent between the active and standby ports or the
faulty in Abis over bandwidth negotiation mode queried in the LST ETHPORT command output is
IP mode. inconsistent with that queried in the DSP ETHPORT command output. As a result, the
PDCH becomes faulty.
Workarounds:
Run the SWP BRD: SRN=XX, SN=YY; command to switch over the interface boards.

Ltd.
APDCH becomes 1. Run LST IPPATH to query the IP path type of PS services and LST TRMMAP to
faulty or the MS query the resource mapping table of adjacent nodes.
does not response If the IP path type is not consistent with the resource mapping table of adjacent nodes,
in Abis over IP the PDCH is faulty. In this case, change the IP path type as required.
mode. As a result,
network access 47.Check whether the value of MPTYPE is configured correctly for the POUc.
fails. The value of MPTYPE in LST MPGRP must be consistent with that of
MPSWITCH in LST BTSMPGRP. You are advised to set MPTYPE to MCPPP.
15.Check whether the long-time speech loopback operation is performed on the Abis
interface boards, such as POUc, GOUc, and FG2c boards, in BSC6900 V900R013.
Workarounds:
Switch over or reset the Abis interface boards.
DPU boards are 1. Query the value of the R9346: Number of Dynamic PDCH Requests Without
insufficient, Application Attempts Because the Number of Activated PDCHs Reaches Board
causing some Specification counter. The query result shows that the number of PDCHs exceeds the
PDCHs to be upper limit allowed by the DPU board.
faulty.
2. According to the DSP PSRES command output, determine that the number of
PDCHs on the DSP where the faulty PDCH is located exceeds the upper limit allowed by
the DSP. For example, the upper limit allowed by the DSP on the DPUd is 48.
Related commands:
DSP PSRES
Workarounds:
Add a DPU board or decrease the value of Maximum Rate Threshold of PDCHs in a
Cell.
Related commands:
SET GCELLPSCHM
Data traffic After the SGSN Pool is enabled, the SGSN in the PDP activation message may be
decreases and a incorrect and causes a decrease in the data traffic and a large number of PDP context
large number of activation failures if the NRI configuration on the BSC is absent, duplicated, or incorrect.
PDP contexts fail In this case, configure an NRI consistent with that of the core network on the BSC based
to be activated on the SGSN Pool configuration principle.
when the SGSN
Pool is enabled. Related commands:
LST/ADD NRISGSNMAP: NRI=xx, OPNAME="xx", CNID=xx;
LST/SET SGSNPOOL: POOLALLOW=ALLOW, NRILEN=xx;
Most MSs cannot If large-sized packets sent from the SGSN are fragmented into three parts, the FG2a board
access the cannot properly process them.
network. Large- Workarounds:
sized packets
always fail to be Set the maximum media transcoding unit (MTU) to a small value (recommended value:
pinged between 1460) on ports on the IP interface boards of the SGSN.
the BSC and
SGSN.
A large number of The PS core network may incorrectly configure MSs in RLC unacknowledged mode or
MSs fail to access LLC acknowledged mode. As a result, data traffic on the BSC decreases.
Ltd.
the network and The reliability-class field in the qos information element (IE)of the ACTIVE PDP
data traffic CONTEXT ACCEPT message indicates the RLC and LLC modes of MSs. The value 0
decreases. indicates the RLC acknowledged mode and the value 1 indicates the LLC
unacknowledged mode.
Workarounds:
Contact engineers of the PS core network to change the configuration modes of MSs.
PS services 1. Query the KPI A531: CS Pagings Discarded on LAPD Link to check that a large
become faulty number of CS pagings are discarded.
during peak hours. 48.If the BTS supports the function of paging packets (for details, refer to the following
The immediate version mapping table), run the following command to set PMNUM to 15:
assignment
success rate of PS SET GCELLSOFT: IDTYPE=BYID, CELLID=1, PMOAFLAG=OPEN, PMI=2,
services is low. PMNUM=15;
49.If the BTS does not support the function of paging packets, run the following
command to configure the problem cell in an independent LA or relocate the problem
cell to an LA with a small number of pagings:
MOD GCELL: LAC=12;
BTS Version That Remarks
Supports Paging
BTS312 None The TRX board capacity determines whether the BTS
supports the function of paging packets. When board
BTS390 All mixed insertion is allowed, the TRX type and BTS
0 version jointly determine whether the BTS supports
paging.
BTS301 BTS3012
2 V300R008C12B419
The success rate of Channel attributes are sent over RSLs in the V009R012 and V009R013 and frequency
PS service hopping information such as the MAIO is not sent to the BTS. As a result, the MAIO
establishment information is inconsistent and affects the success rate of PS service establishment and the
decreases and the call drop rate.
call drop rate Workarounds:
increases by 10%
respectively after 1. Run the following command to disable the Flex MAIO:
the Flex MAIO is MOD GCELL: IDTYPE=BYID, CELLID=xx, FLEXMAIO=OFF;
enabled. 50.Run the following command to send channel attributes from OMLs:
SET OTHSOFTPARA: BSCRESERVEDPARA4=xxx;
Bit 9 in the value of BSCRESERVEDPARA4 must be set to 0.
For example, if the parameter value is set to 65535 (0xFFFF in hexadecimal notation),
the value is changed to 65279 (0xFEFF) after bit 9 is set to 0.
51.Run the following command to redistribute PS services on the network:
SET PSCELLTODSP: IDXTYPE=BYBSC;
The number of Check whether the flow control parameters are set to their default values.
failed TBF If the flow control parameters are configured incorrectly, a large number of PS resource
establishments applications is discarded because of the flow control mechanism. As a result, the number
increases sharply of failed TBF establishments increase sharply.
because of other
reasons. Solution:
Ltd.
Run the following command to set the flow control parameters to their default values:
LST/SET BSCFCPARA: CHREQPSAVGMSGNUMINPERIOD=200,
PSRESREQMSGNUMINPERIOD=500;
PS services 1. Run the RST BRD command to reset the active and standby XPUM boards if the
become faulty inter-subrack cables are configured for the subracks accommodating the DPUd or
after the external DPUg board.
PCU is changed to 52.If services in cells on the BTS312 or BTS3006C are abnormal, change the value of the
a built-in PCU. EGPRS parameter LQCMODE from IR to LA and perform a level-4 BTS reset.
Related commands:
SET GCELLEGPRSPARA: IDTYPE=BYID, CELLID=***, LQCMODE=IR;
RST BTS: TYPE=BTSSOFT, IDTYPE=BYID, BTSID=***, LEVEL=4-LEVEL;
PS counters When the value of the ZTL3188D: Number of PCH Overloads on the Abis Interface per
deteriorate when BSC (PS Service) counter on the BSC increases, the BSC of GBSS13.0 performs flow
traffic on CCCHs control on single-block assignment messages. As a result, first-phase single-block
is congested and assignment messages cannot be delivered during two-phase access and the access
an incorrect flow procedure fails. In addition, the values of the A9201: Number of Uplink EGPRS TBF
control policy is Establishment Attempts, A9001: Number of Uplink GPRS TBF Establishment Attempts,
used in a BSC of and L9506: Total Bytes of LLC PDUs Sent decrease. In the preceding scenario, perform
GBSS13.0. the following operations to resolve this problem:
1. Run the following command to set the Support 11BIT EGPRS Access parameter to
YES(YES):
SET GCELLPSBASE: IDTYPE=BYID, CELLID=x, EGPRS11BITCHANREQ=YES;
2. Run the following command to set the Force MS Two-phase Access parameter to
Close(Close):
SET BSCPSSOFTPARA: Force2Phase=Close;
3. Run the following command to add an EDGE channel to the cell:
SET GTRXCHAN: TRXID=x, CHNO=x, CHTYPE=x, GPRSCHPRI=EGPRSNORCH;
4. If the cell does not support EGPRS, run the following command to set the EDGE
parameter to YES(Yes):
SET GCELLGPRS: IDTYPE=BYID, CELLID=x, GPRS=SupportAsInnPcu, EDGE=
YES;
3.2.2 Gb Interface Faults

The transmission is normal, Certain NSN SGSN versions have the bugs that result in dynamic NSVL
an NSVL fault alarm is negotiation failures.
generated over the Gb Workarounds:
interface, and the dynamic
configuration fails. 1. Reconfigure the NSVL on the SGSN.
2. Reconfigure the NSVL on the BSC.
MML commands:
RMV NSVLLOCAL
Ltd.
ADD NSVLLOCAL
The transmission is normal The Ericsson SGSN is not configured with the NSE and allows to dynamically
but the NSVL or NSE on the negotiate all NSEs on the BSC. There are two identical NSEs. One NSE is
Gb interface is intermittently frequently requested and the other one is frequently faulty.
disconnected and reports Workarounds:
alarms.
1. Change the NSEI configuration in the alarms.
2. Identify repeated NSEI configurations on all BSCs under the SGSN.
The attach fails and the CN The LAC table of the SGSN is incorrect. As a result, cells in an LA cannot
does not send any attach process PS services and the traffic volume at the LLC layer decreases.
acceptance messages. As a Workarounds:
result, the PS services fail to
be processed. 1. Reconfigure the LAC table on the CN.
2. Migrate cells to another LA. Exercise caution when performing this
operation.
The NS layer is normal. A The SGSN resources are insufficient. As a result, the PTPBVC activation fails.
large number of PTPBVC Workarounds:
activations fail and the
SGSN does not send any 1. Delete certain PTPBVCs with low service volumes.
PTP activation response 16. Expand the capacity of the SGSN.
messages.
Services carried by certain The number of PTPBVCs on the Gb interface board of the BSC exceeds 2048.
PTPBVCs on the BSC are When more than 2048 PTPBVCs are configured, the service is abnormal. The
abnormal. The LLC has LLC layer corresponding to the PTPBVC has uplink traffic but no downlink
uplink traffic but no traffic.
downlink traffic. Workarounds:
Delete some PTPBVCs to ensure that the number of PTPBVCs is less than
2048.
MML command: RMV PTPBVC
After the SGSN Pool is In the SGSN Pool scenario, if the network resource identifier (NRI) is not
enabled, the data traffic configured, repeatedly configured, or incorrectly configured, the PDP activation
decreases and a large number messages may be transmitted to inappropriate SGSNs. As a result, the data
of PDP activations fail. traffic decreases and a large number of PDP activations fail.
The NRI configured on the BSC must be consistent with that configured on the
CN. The NRI configuration must comply with the SGSN Pool configuration
principles.
The MML commands are as follows:
ADD NRISGSNMAP: NRI=xx, OPNAME="xx", CNID=xx;
SET SGSNPOOL: POOLALLOW=ALLOW, NRILEN=xx;
The Gb interface is in the 1. Check whether the GOUc board is connected to a Cisco router.
down state. Check whether the attribute of the port on the Cisco router connected to the
The GOUc board over the GOUc board is DOWN. If yes, run the undo shutdown command in the
Gb interface reports ALM- interface view of the router.
21345 Ethernet Link Fault. Router>en//Entering the EXCEL mode
password:xxxxxx//Entering the password
Router# config terminal //Enter the global configuration mode.

Ltd.
Router(config)#interface gigabitethernet0/0//Entering the interface view
Router(config-if)#exit//Exiting the port mode
2. Run the LST ETHPORT command to query the value of Auto negotiation.
Then, run the SET ETHPORT command to change the parameter value.
a. If the parameter value queried in the LST ETHPORT command output is
ENABLE, change it to DISABLE.
a. If the parameter value queried in the LST ETHPORT command output is
DISABLE, change it to ENABLE.
3.2.3 Alarms over the Gb Interface

Fault)
ALM-21385 Gb BC Failure is 1. Run the DSP E1T1 command to check whether the E1/T1 port is normal.
reported. If not, rectify the port fault. If yes, proceed with the next step.
53.Run the DSP BC command to check whether BC services are available.
If BC services are unavailable, run the SWP BRD command to switch
over PEUa boards and XPU boards where the NSE belongs in sequence.
If the switchover fails, reset the active board. If the RST BRD command
execution fails due to timeout or other causes, run the RST JTGBRD:
SRN=0, SN=0; command to reset the board.
Set the last parameter in the RST JTGBRD command by referring to the
command reference.
If the command is unavailable, remove and install the board.
If the fault persists, run the following commands to inhibit and uninhibit
the board:
INH BRD: INHT=PHYSICAL;
UIN BRD: UINT=PHYSICAL;
54.Check whether the BC timeslot configurations are consistent between the
BSC and the CN.
ALM-22003 NSVC 1. Check whether ALM-21385 Gb BC Failure is reported. If yes, clear the
Disconnection is reported. alarm by following steps in the corresponding descriptions. If no,
proceed with the next step.
55.Run DSP NSVC to check whether NSVC services are in Active
Unblock state.
If NSVC services are not in Active Unblock state, trace the SIGBVC and
PTPBVC messages on the BSC side. You can run LST NSE to obtain
the NSE identifier.
56.Switch over the PEUa interface boards, and switch over the XPUs of the
NSE.
ALM-22004 NSVL Faulty is 1. Run a ping command to check whether the service IP address between
reported. the BSC and the SGSN can be pinged. The service IP address is the same
as the remote IP address queried using the LST NSVLREMOTE
Ltd.
Fault)
command. Then, run the TRC IPADDR command to check whether all
link routes for the service IP address between the BSC and the SGSN are
normal.
If yes, proceed with the next step.
If no, resolve the transmission route problem. Then, proceed with the
next step.
57.Run the DSP NSVL command to check whether the value of "
If no, switch over the FG2a/FG2c/GOUc boards and XPU boards where
the NSE belongs in sequence. Query the XPU boards where the NSE
belongs by running the LST NSE command. If the switchover fails, reset
the active board. If the RST BRD command execution fails due to
timeout or other causes, run the RST JTGBRD: SRN=0, SN=0;
command to reset the board.
command reference.
the board:
ALM-22005 NSE Faulty is 1. Check whether BC/NSVC/NSVL services are normal.
reported. If yes, run the DSP SIGBVC command to query the NSE status. If the
NSE is faulty, run the RST SIGBVC command to recover the NSE. If
the fault persists, proceed with the next step.
If no, rectify the fault based on related alarm processing principle.
2. Switch over the PEUa/FG2a/FG2c/GOUc boards and XPU boards where
the NSE belongs in sequence. Query the XPU boards where the NSE
belongs by running the LST NSE command. If the switchover fails, reset
the active board. If the RST BRD command execution fails due to
timeout or other causes, run the RST JTGBRD: SRN=0, SN=0;
command to reset the board.
command reference.
the board:
ALM-22008 PTP BVC Faulty 1. Check whether the following alarms are reported:
is reported. - ALM-21385 Gb BC Failure
- ALM-22003 NSVC Disconnection
- ALM-22004 NSVL Faulty
- ALM-22005 NSE Faulty

Ltd.
Fault)
 If yes, clear these alarms by following steps in the corresponding

descriptions.
 If no, proceed with the next step.
2. Run the DSP PTPBVC command to query the PTPBVC status. If the
PTPBVC is faulty, run the RST PTPBVC command. If the PTPBVC does
not recover, compare the CGI configuration in a normal cell with that in a
problem cell to check whether the configurations are consistent. If
inconsistent, proceed with the next step.
3. Run the RMV PTPBVC and ADD PTPBVC commands to replace the
BVCI with a new one. If the fault persists, proceed with the next step.
4. Check whether PTPBVCs of the problem cell are distributed to the same
DSP or XPU. If yes, perform cell migration.
3.3 BTS Link Disconnection and Cell Out-Of-Service

Fault)
Services of certain BTSs are  If the OMLs work properly but the BTSs cannot start working or some
adversely affected, for example, cells are out of service, perform the following operations to rectify the
BTS links are disconnected, fault:
cells are out of service, or all 1. Run the following command to perform a level-4 BTS reset:
channel indicators stay red or
white. Alternatively, some RST BTS: TYPE=BTSSOFT, IDTYPE=BYID, BTSID=***, LEVEL=4-
BTSs cannot start working after LEVEL;
data transmission recovers, with Run the following command to perform a level-4 cell reset:
ALM-21801 GSM Cell out of RST GCELL: IDTYPE=BYID, CELLID=0, LEVEL=4-LEVEL;
Service or ALM-21807 OML
Fault reported. Switch over the interface boards and XPU boards for the BTSs or cells.
58.Check whether ALM-21806 BTS Not Support Configured Function is
reported and check the setting of Support for Unified Data
Configuration (for 3900 series base stations) or Support Normalized
3012 Series Base Stations (for 3012 series base stations) by running the
LST BTS command.
- If ALM-21806 is reported and the parameter is set to Support, upgrade
the BTS versions.
- If ALM-21806 is reported and the parameter is set to Not Support, roll
back the BTS versions or upgrade the data configuration.
Then, run the LST BTS command to check whether the BTSs are
activated, and run the DSP BTSVER and LST VER commands to check
whether the BTS versions match the BSC version.
59.If local operation and maintenance can be performed, reset or replace the
boards that failed to start.
60.If the BSC6900 is used, the BTS versions are GBSS8.0 or GBSS8.1, and

Ltd.
Fault)
backup power saving is enabled, run the LST BTSBAKPWR command

with Backup Power Saving Method set to BYPWR.
61.Relocate the BTSs to another subrack.
Remove the BTSs. Then, reconfigure the BTSs in another subrack or
Abis interface board.
 If the OMLs are faulty, perform the following operations to rectify the
fault:
1. Analyze the deployment of disconnected BTSs, and then perform the
following operations:
(1) Run the following command to perform a level-4 BTS reset:
RST BTS: TYPE=BTSSOFT, IDTYPE=BYID, BTSID=***,
LEVEL=4-LEVEL;
(2) Switch over the interface boards and XPU boards for the BTSs or
cells.
If the disconnected BTSs use IP transmission, perform the following
operations to check the transmission:
(1) When the Abis interface uses IP transmission at layer 2 or the BTS
gateway router functions as a DHCP server, disable the DHCP
server.
(2) When the Abis interface uses IP transmission at layer 3, no DHCP
Relay is configured for the gateway on the BTS side, or the DHCP
relay IP address is not the BSC address, configure a DHCP Relay to
the BTS gateway and set its address to the BSC service IP address.
(3) Check whether transmission alarms are reported. If reported, clear
the alarms.
(4) Ping the BTS IP addresses and the BTS gateway, and perform
traceroute on the BTS IP address. In layer 3 networking, if the
preceding operations fail, contact the customer to check whether the
intermediate transmission devices work properly. If the intermediate
transmission devices do not work properly, the routes between the
BSC and BTSs are unreachable.
(5) Check whether the ESN has been modified and whether the
configured ESN is consistent with that on the BSC. (You can run the
LST BTSESN command to query the ESN configured on the BSC,
and run the DSP BTSESN command to query the ESN reported by
the BTS but not configured on the BSC.)
2. If local operation and maintenance can be performed, reset or replace the
boards that failed to start.
For HDLC-based BTSs, check the BTS versions and the data
configuration. If they are inconsistent, roll back the BTS versions or
upgrade the data configuration. (You can run the LST BTS command to
check the setting of Support for Unified Data Configuration for 3900
series base stations or Support Normalized 3012 Series Base Stations
for 3012 series base stations.)
3. Relocate the BTSs to another subrack.
Remove the BTSs. Then, reconfigure the BTSs in another subrack or
Ltd.
Fault)
Abis interface board.

Links of BTSs connecting to an 1. In Abis over IP mode, rectify the transmission fault by referring to the
interface board are handling methods for BTS link disconnections.
disconnected, a large number of 2. If the OIUa board functions as the Abis interface board, perform the
cells are out of service, or following operations:
services are adversely affected.
(1) Switch over the active and standby OIUa boards or reset the OIUa
board.
(2) Remove the OIUa board from the odd-numbered slot.
3. Check whether the BTS versions match the BSC version.
4. If the BTSs are configured on the GOUc board and the GOUc board
reports ALM-21345 Ethernet Link Fault, perform the following
operations:
(1) Check whether the GOUc board is connected to a Cisco router.
Check the setting of the port on the Cisco router that connects to the GOUc
board. If the port attribute is set to DOWN, run the undo shutdown
command on the port setting window. The details are as follows:
Router>en//Enter the EXEC mode.
password:xxxxxx//Type the password.
Router# config terminal//Enter the global configuration mode.
Router(config)#interface gigabitethernet0/0//Enter the port setting
window.
Router(config-if)#exit//Exit the port setting mode.

(2) Run the LST ETHPORT command to check the negotiation mode of
the port. Then, run the SET ETHPORT command to modify the Auto
negotiation parameter setting as follows:
- If the parameter value is ENABLE in the LST ETHPORT command
output, change it to DISABLE.
- If the parameter value is DISABLE in the LST ETHPORT command
output, change it to ENABLE.

Ltd.
Fault)
Links of BTSs distributed on an 1. Switch over or reset the XPU. If the switchover fails, reset the active
XPU are disconnected, a large XPU board. If the RST BRD command execution fails due to timeout or
number of cells are out of other causes, run the RST JTGBRD: SRN=0, SN=0; command to reset
service, or services are the XPU (set the Description file parameter by referring to the MML
adversely affected. online help). If the RST JTGBRD command is unavailable, run the INH
BRD: INHT=PHYSICAL; and UIN BRD: UINT=PHYSICAL;
commands to inhibit and uninhibit the XPUm respectively. If the fault
persists, perform the following operations:
(1) Remove the standby XPU.
(2) Observe the board status.
(3) Insert the standby XPU.
(4) Switch over the XPUs.
(6) Remove the standby XPU.
(8) Insert the standby XPU.
2. Remove and then insert both the active and standby XPUs.
3. If the fault persists, switch over the SCUs, remove and then insert the
SCUs, or remove one SCU.
4. Run the SET BTSCTRL command, which applies only to the BSC6900,
to designate the BTS control plane to the CPUS of a functional XPU.
5. Relocate the BTS to another subrack by running the following
commands:
BSC6000 command examples:
MOV BTS: IDXTYPE=BYIDX, BTSIDX=XX, DESTMODE=TDM,
DESTNODE=BSC, SRN=XX, SN=XX, PN=XX;
BSC6900 command examples:
RMV BTSCONNECT: IDTYPE=BYID, BTSID=xx, INPN=xx;
ADD BTSCONNECT: IDTYPE=BYID, BTSID=xx, DESTNODE=BSC,
SRN=xx, SN=xx, PN=xx;
BTS links are disconnected due 1. Run the following commands to check whether the APS attribute of the
to switchover of optical optical interface board is consistent with that of the transmission device:
interface boards, with an alarm BSC6000: LST OIUAPS;
reported, indicating that active
and standby switchover of BSC6900: LST MSP;
optical interface boards. If the APS attribute of the optical interface board is inconsistent with that
of the transmission device, make them consistent.
2. Reset the peer interface board, and remove the board in the odd-
numbered slot at the local end.
3. Contact transmission device engineers to jointly locate the fault, and
prepare for BTS relocation.
Cells are out of service 1. Check whether the BTS versions match the BSC version.
randomly, with ALM-21801 2. Run the LST BTSAUTODLDACTINFO command to check whether
GSM Cell out of Service the BTS automatic activation function is enabled and whether the
Ltd.
Fault)
reported. activated version is correct.

The BTS is disconnected after a Check whether the following conditions are met:
BSC upgrade.  The BSC is upgraded from a BSC6000 to a BSC6900.
 A BTS3012 series base station (BTS3012/BTS3012AE/BTS3012II/
BTS3006C/BTS3002E) is used.
 The BTS uses one of the following versions:
- BTS3012 V300R008C12B419
- BTS3012 V300R008C12B423
- BTS3012 V300R008C12B425
- BTS3012 V300R008C12B427
- BTS3012 V300R008C12B429
In the preceding BTS versions, the processing of extended attributes is
defective. As a result, the BTSs cannot identify the extended attributes
delivered by the target BSC version, and therefore the extended attributes
cannot be properly processed in codes, leading to a dead loop and BTS reset.
As a result, links are repeated established but fail between the BTSs and
BSC. In this case, roll back the BSC. Then, upgrade the BTSs to new
versions and upgrade the BSC again.
Pico BTSs are disconnected Check whether the IPsec tunnel to the pico BTS exists on the firewall
from the public network (display IPsec sa). If not, reset the local transmission devices connected to
deployed with IPsec after a the pico BTSs. (This operation is mandatory when the pico BTSs work in
BSC upgrade. modem mode.)

Ltd.
3.4 Repeated Board Resets
Fault)
The active and standby boards For both the BSC6000 or BSC6900, perform the following operations:
reset repeatedly. 1. Check for alarms, and remove the boards with major alarms or high-
priority alarms.
2. Replace the boards.
An independent board resets Replace the board on the BSC6000 or BSC6900.
repeatedly.
All boards in a subrack are For both the BSC6000 or BSC6900, perform the following operations:
faulty. 1. Switch over or reset the active SCU.
2. Check for alarms, and remove the SCUs with major alarms or high-
priority alarms.
3. If the fault persists, insert the removed SCU, and remove the other SCU.
The XPUs in all subracks reset For the BSC6000, run the LST ETHSWITCH command to query the
repeatedly. PARC self-healing function. If the function is disabled, run the following
command to enable the PARC self-healing function:
SET ETHSWITCH: FADETECTSW=OPEN, FAPOSTSW=OPEN,
ISOLATESYSSW=OPEN, ISOLATEIOSW=OPEN;
For the BSC6900, the PARC self-healing function is enabled by default.

Ltd.
3.5 Board Loading Failures
Fault)
All or certain BSC board For the BSC6000, perform the following operations:
indicators turn red on the device 1. Check whether the DIP switches on the faulty subrack are correctly set.
panel of the Web LMT. The For details, see the following section in the BSC6000 online help:
LMT loading progress bar does
not display the progress or the BSC Hardware Description > BSC Subracks > DIP Switches on the BSC
progress fails to reach 100%. Subrack
2. Run RST OMUCORE to reset the OMU core.
3. If the fault persists, reset or remove and then insert the active OMU.
4. Reset or remove and then insert the boards whose data loading failed. If
the RST BRD command execution fails due to timeout or other causes,
run the RST JTGBRD: SRN=0, SN=0; command to reset the boards
(set the Description file parameter by referring to the MML online help).
If the RST JTGBRD command is unavailable (in versions earlier than
R13), remove and then insert the boards. If the fault persists, run the INH
5. Reset or remove and then insert the SCUs in the same subrack.
(1) If loading fails on all boards, remove and then insert or reset both
SCUs in the same subrack.
(2) If loading fails only on boards in odd-numbered slots, remove and
then insert or reset the SCU in slot 7. If loading fails only on boards
in even-numbered slots, remove and then insert or reset the SCU in
slot 6.
6. Retain only one SCU and check whether loading is successful.
Retain the SCU in slot 6 in the same subrack to check whether loading is
successful. If the loading still fails, insert an SCU in slot 7. After loading
is completed, remove the SCU in slot 6 three minutes later.
7. Power off the entire subrack.
If loading fails on all boards and the fault cannot be rectified after the
preceding operations, power off the entire subrack.
8. Check the SGSN Pool configuration on the BSC.
If the loading progress reaches 90% and fails repeatedly on the XPUM
whereas loading on other boards is normal, run LST NRISGSNMAP to
check whether the NRI value in the command output is duplicate.
For the BSC6900, perform the following operations:
1. Check whether the faulty subrack is in ineffective mode.
If the subrack is in ineffective mode, run SET CFGDATAEFFECTIVE
to change the subrack to effective mode.
Ltd.
Fault)
2. Check whether the internal network IP address of the OMU is correct.

If the IP address is incorrect, change the IP address by referring to OMU
Administration Guide.
If loading fails on the board in slot 24/25 of subrack 0 or on a board in
the TC subrack connecting to the Ater interface board that is installed in
slot 24/25 of subrack 0, perform the following operations:
(1) Log in to the active OMU by using PuTTY and run the ifconfig
command.
(2) Check whether the VLAN 1 IP address (the inet addr option) is set
to 80.168.3.50/60 and the VLAN 1:0 IP address is set to 80.168.3.40.
(3) Check whether the masks (the Mask option) of both VLAN 1 and
VLAN 1:0 are set to 255.0.0.0.
3. Reset the configure and ftp_server modules of the active OMU. (You
must run RST OMUMODULE twice to reset the modules.)
4. If the fault persists, reset or remove and then insert the active OMU.
5. Reset or remove and then insert the boards whose data loading failed. If
the RST BRD command execution fails due to timeout or other causes,
run the RST JTGBRD: SRN=0, SN=0; command to reset the boards
(set the Description file parameter by referring to the MML online help).
If the RST JTGBRD command is unavailable (in versions earlier than
R13), remove and then insert the boards. If the fault persists, run the INH
6. Reset or remove and then insert the SCUs in the same subrack.
a If loading fails on all boards, reset or remove and then insert both
SCUs in the same subrack.
b If loading fails only on boards in odd-numbered slots, reset or remove
and then insert the SCU in slot 7. If loading fails only on boards in
even-numbered slots, reset or remove and then insert the SCU in slot
6.
7. Retain only one SCU and check whether loading is successful.
Retain the SCU in slot 6 in the same subrack to check whether loading is
successful. If the loading still fails, insert an SCU in slot 7. After loading
is completed, remove the SCU in slot 6 three minutes later.
9. If the XPU cannot start working even after its data loading is successful,
run the DEA BTS command to deactivate the BTS. If the deactivation
fails due to incorrect configuration of some cells (for example, the CA
list is empty), set the entire subrack to ineffective mode to rectify the
fault. Then, set the entire subrack to effective mode again. Finally, reset
the subrack to check whether the fault is rectified.
All the XPU boards become Obtain the GCELLFREQDATA Check tool from the following path:
faulty and turn red on the LMT http://support.huawei.com/support/pages/editionctrl/catalog/ShowSoftDetail.
device panel due to a BSC do?
Ltd.
Fault)
upgrade or XPU reset. The actionFlag=displaySoftInfo&node_id=000001442079&web_doc_id=SW000

loading progress indicates 0502448&colID=ROOTENWEB|CO0000000174
100%, but boards cannot start Execute the tool to check whether the CA lists for some cells are correct.
working. (You can run the COL LOG: LOGTYPE=MEM_DB_BAK-1; command
to obtain the DB data.)If some CA lists are incorrect, perform the following
operations:
1. Run the SET CFGDATAINEFFECTIVE command to set the subrack
accommodating the fault XPU board to ineffective mode.
2. Run the DEA GCELL command to deactivate problem cells.
3. Run the ADD GCELLFREQ command to correct the CA list. (The tool
automatically generates the corresponding command.)
4. Reactivate the cells.
5. Run the SET CFGDATAEFFECTIVE to set the subrack
accommodating the XPU board to effective mode.
6. Reset the subrack.
The XPU starts working properly.
All the MPU boards become 1. Run the SET CFGDATAINEFFECTIVE command to set the subrack
faulty and turn red on the LMT accommodating the fault MPU board to ineffective mode.
device panel due to a BSC 2. Deactivate all BTSs.
upgrade or MPU reset. The
loading progress indicates 3. Reactivate all the BTSs.
100%, but boards cannot start 4. Run the SET CFGDATAEFFECTIVE to set the subrack
working. accommodating the MPU board to effective mode.
5. Reset the subrack.
The MPU starts working properly.
3.6 GBAM/GOMU Faults

3.6.1 GBAM/GOMU Troubleshooting
The GBAM/GOMU fails and For the BSC6000 or BSC6900:

the operation and maintenance For details about the following operations, see the section 4.1"Quick
connection is interrupted. The Troubleshooting of the GBAM and GOMU Startup Failures."
fault cannot be cleared after the
board is re-inserted or the server 1. Connect a keyboard display or a keyboard, video, and mouse (KVM) to
is powered off and then a GBAM/GOMU. Resolve the problem based on the displayed error
powered on again. information.
2. Check and set the RAID.
3. Remove and then insert the hard disk.
4. Re-install the operating system.

Ltd.
You can check the following indicators on the M2000 on the MSC side to
determine whether the GBAM/GOMU failure causes service damages:
Location update services: Location Management Measurement > Location
Update Success Rate
Voice services: MSC CSSR Measurement > MO Success Rate and MT
Success Rate
Handover services: MSC Handover Measurement > Number of Handover
Success Times/Number of Handover Requests
Precautions for replacing the For the BSC6000 or BSC6900:
GBAM server with the GOMU For details about the operations, see section 4.2"Precautions for Replacing
board the GBAM Server with the GOMU Board."
1. Check whether the operating system of the OMU spare part meets the
requirements (for the BSC6000, the operating system of the OMU spare
part must be SUSE).
2. Check whether the available slots in the subrack meet the requirements.
The OMUa/OMUb occupies two slots.
When the OMUa/OMUb is installed in the front of the subrack, the
OMUa/OMUb occupies slots 0 and 1 or slots 2 and 3. When the
OMUa/OMUb is installed in the rear of the subrack, the OMUa/OMUb
occupies slots 20 and 21 or slots 22 and 23.
In the BSC6000 C15 and BSC6900 versions, when the OMUa/OMUb is
installed in the rear of the subrack, the OMUa/OMUb occupies slots 24
and 25 or slots 26 and 27.
The OMUc occupies only a slot. The slot number for the OMUc is the
same as that for the OMUa and OMUb.
3. Modify the data of the BSC.
For the BSC6000, modify the data on the LMT in offline mode. For the
BSC6900, modify the data in the MML scripts.
4. Install the OMU software.
Note that the OMU patches and front-end board patches are loaded
separately for the BSC6000.
The OMU patches and front-end board patches can be loaded together
for the BSC6900OMU. Pay attention to the patch file directories in the
R11, R12, and R13 versions.
5. Restore the data.
For the BSC6000, import the data using the precfg.sh script.
For the BSC6900, import the data using the MML script or data files in
*.bak format (the data files are saved in the *.dat format by the M2000).
6. Activate the license.
After the data consistency is confirmed, activate the license.
7. Verify the operation results.
Verify that the data on the front end and back end is the same and the
versions are consistent. Check whether alarms and traffic measurement
results are reported properly. Conduct the service dialing tests.
The OMU software fails to start. 1. Check the permission on the /mbsc/mysql directory by performing the
following operations: Log in to the OMU using the PuTTY, and run the
Ltd.
ls -l command under the /mbsc/ directory.
Check whether the permission on the mysql folder is "drwxrwxrwx". If no,

run the chmod 777 mysql command to change the permission.
2. Check the permission on the /usr/local/mysql directory by performing
the following operations: Log in to the OMU using the PuTTY, and run
the ls -l command under the /usr/local/ directory.
Check whether the permission on the mysql folder is "lrwxrwxrwx". If

no, run the chmod 777 mysql command to change the permission.
NOTE
The meaning of "drwxrwxrwx" is as follows:
"d" indicates the directory.
The nine characters (three groups with three characters in each group) following "d"
indicate the permission on the file. The first "rwx" indicates the permission of the file
owner. The second "rwx" indicates the permission of users in the same user group as the
file owner. The third "rwx" indicates the permission of other users. "r", "w", and "x"
indicate the read, write, and execute permissions, respectively.
3.6.2 GBAM Migration

When no GBAM spare part is 1. Back up the data of the normal BSC (perform this operation on the
available, use the GBAM on other normal BSC).
BSC in the same equipment to For the BSC6000: Back up the data in online mode on the LMT.
recover the services on the faulty
BSC. (Note: Do not change the For the BSC6900: Run BKP DB to import the database file. Obtain
physical positions of the GBAMs the database file from the corresponding path on the GBAM (by
default, the database file is saved in the
Ltd.
and do not power off the GBAMs. /BSC6000/data/mbsc/bam/version_a/data/backup directory and the
Connect the normal GBAM with directory is displayed after the command is executed).
the SCU of the fault BSC using 2. Disconnect the GBAM from the SCU (perform this operation on the
network cables.) normal BSC).
Remove the network cables that connect the rear panel of the GBAM
and the SCU panel in slots 6 and 7.
3. Import the data of the faulty BSC to the normal GBAM.
For the BSC6000, import the data of the faulty BSC to the normal
GBAM.
For the BSC6900:
If the database file of the faulty BSC is available, use the database file
to restore the data.
If only the MML script is available, perform the following steps:
1) Run SET CFGDATAINEFFECTIVE to set all the subracks to
the ineffective mode.
2) Run the MML script.
3) Run SET CFGDATAEFFECTIVE to set all the subracks to the
effective mode.
4. Connect the normal GBAM with port 10 on the SCU panel in slots 6
and 7 on the faulty BSC.
5. Verify the data consistency between the front end and the back end.
1) Check whether the imported data is consistent on the front end
and the back end.
For the BSC6000, check the data consistency on the LMT.
For the BSC6900, run ACT CRC to check the data consistency.
2) If the data is inconsistent, reset the boards or subracks of the
BSC on which the data is inconsistent.
For the BSC6000: Reset the subracks or boards on the LMT.
When you reset the subracks, reset the remote subracks first.
For the BSC6900: Reset the subracks or boards using the MML
command. When you reset the subracks, reset the remote
subracks first. To reset the BSC, run RST BSC: BSCID=0.
After the normal GBAM is used to 1. Disconnect the normal GBAM and the faulty SCU (perform this
recover the faulty BSC, the normal operation on the faulty BSC).
GBAM must be re-configured for Remove the network cables that connect the rear panel of the GBAM
the original BSC. and the SCU panel in slots 6 and 7.
2. Restore the GBAM version.
If another software version has been installed, restore the GBAM
version.
3. Import the backup original BSC data to the normal GBAM. For
details about how to import the data, see section 3.6.3"BSC
Configuration Data Restoration."
For the BSC6000, import the original data of the normal BSC to the
normal GBAM.
For the BSC6900, import the original database file of the normal BSC

Ltd.
to the normal GBAM.
4. Connect the normal GBAM with port 10 on the SCU panel in slots 6
and 7 on the normal BSC.
5. Verify the data consistency between the front end and the back end.
1) Check whether the imported data is consistent on the front end
and the back end.
For the BSC6000, check the data consistency on the LMT.
For the BSC6900, run ACT CRC to check the data consistency.
2) If the data is inconsistent, reset the boards or subracks of the
BSC on which the data is inconsistent.
For the BSC6000: Reset the subracks or boards on the LMT.
When you reset the subracks, reset the remote subracks first.
For the BSC6900: Reset the subracks or boards using the MML
command. When you reset the subracks, reset the remote
subracks first. To reset the BSC, run RST BSC: BSCID=0.
3.6.3 BSC Configuration Data Restoration

After the BSC software is For the BSC6000:

installed on the OMU, you can 1. Obtain the BSC configuration data.
obtain and restore the BSC
configuration data. Besides manually backing up the BSC configuration data, you can
obtain the BSC configuration data in the following ways:
 After you log in to the BSC over the PC on which the LMT is installed,
a copy of offline data is saved in the local path X:\HW
LMT\BSC6000\BSC
version\BackupCfgData\***_BSCIP\lmtonlinecfgbackup.dat.
For example:
D:\HW
LMT\BSC6000\BSC6000V900R008C12\BackupCfgData\Local_admi
n_10.141.124.188\lmtonlinecfgbackup.dat
 After the scheduled backup task is enabled on the M2000, the data
backed up in the latest three backup operations is saved on the M2000.
You can obtain the backup files as follows:
On the M2000 client, choose Maintenance > Backup Management >
NE Backup to open the NE backup management page. On the left
navigation tree, select the corresponding NE and select the latest
backup task. Click Download to the OMC client to download the data
to the local PC.
2. Import the BSC configuration data.
You can import the BSC configuration data in the following ways:
 Import the BSC configuration data on the LMT.
Save the BSC configuration file in the X:\HW LMT\BSC6000\BSC
version\BackupCfgData directory, for example, D:\HW
LMT\BSC6000\BSC6000V900R008C12\BackupCfgData.
Ltd.
Log in to the BSC over the LMT. Choose Configuration > Load and
Restore > Restore with local file. In File on local, select the
configuration file to be imported. Then, click Execute. In several
seconds, the OMU process is restarted. The LMT is temporarily
disconnected and then is reconnected.
In this method, signaling points are configured for the configuration data on the
OMU before the BSC configuration data is imported and the activated license file is
consistent with the BSC configuration data to be imported.
 Use the PuTTY to import the BSC configuration data.
Save the BSC configuration data in the \bsc6000\data\datafile
directory.
On the PuTTY, run omuctrl stop to stop the OMU software.
Then, run the following commands:
cd /BSC6000/bscswm/omuroot/upgrade/
./precfg.sh ***.dat
***.dat indicates the file that saves the BSC configuration data in the
\bsc6000\data\datafile directory. You can use the actual file name to
replace ***.dat. Usually, no prompt information is displayed after the
BSC configuration data is successfully imported. If other prompt
information is displayed, run ./precfg.sh ***.dat again.
This method does not have any restrictions on the existing BSC data and license.
After the BSC configuration data is imported, re-activate the license. During the data
import, stop the OMU. In the active and standby OMUs scenario, the external virtual
IP address is released after the OMUs are stopped. If no external physical IP address
is available, you must import the BSC configuration data on the near end.
The ./precfg.sh command is executed only on the active OMU. If the
./precfg.sh command is executed on both the active OMU and the
standby OMU, perform the OMU switchover after the BSC
configuration data is imported.
If alarm 801 indicating data inconsistency is generated after the BSC
configuration data is imported, reset the subrack or the BSC.
For the BSC6900:
1. Obtain the BSC configuration data.
Besides manually backing up the BSC configuration data (database
files or MML configuration scripts), you can obtain the database files
of the BSC in the following ways:
 The BSC periodically backs up the database files every day. The
database files are saved in the following directory:
\mbsc\bam\active workspace\data\backup
The database files can be saved for up to seven days.
 After the scheduled backup task is enabled on the M2000, the data
backed up in the latest three backup operations is saved on the M2000.
You can obtain the backup files as follows:
On the M2000 client, choose Maintenance > Backup Management >
NE Backup to open the NE backup management page. On the left
navigation tree, select the corresponding NE and select the latest
backup task. Click Download to the OMC client to download the data
Ltd.
to the local PC.
2. Import the BSC configuration data.
You can import the BSC configuration data in the following ways:
 Import the BSC configuration data using the MML script.
Run SET CFGDATAINEFFECTIVE to set all the subracks to the
ineffective mode.
Save the MML script in the FTP directory on the active workspace.
Run RUN BATCHFILE with the end type set to
ALL_END_RETURN and result record to REC_ ERR.
After the BSC configuration data is imported, check whether the result
file contains any error records. If no error record exists, run SET
CFGDATAEFFECTIVE to set all the subracks to the effective mode.
 Import the database file.
Run /etc/rc.d/omud stop to stop the OMU. Then, upload the database
file to the OMU.
Use the PuTTY to log in to the OMU. In the
mbsc/bam/common/services directory, run ./omu_backup_linker to
enable the data restoration tool. Enter restore and the database file path
and file in the Linux system on the OMU to start the data restoration.
After the database file is imported, run ACT CRC to check the data consistency
between the front end and the back end. If alarm 20736 indicating data inconsistency
is generated, reset the subrack or the BSC.
3.7 Faults in A over IP Mode

In A over IP  The assignment fails. The cause value in the Assignment Failure message is equipment
mode, services faults.
cannot be On the LMT, run the LST DSP command to check whether the value of The type of TC
performed and resource is Normal voice coding/decoding.
calls fail.
Alternatively, check whether TCTYPE = GTC is contained in the SET TCTYPE MML
script in the exported MML scripts.
If the value of The type of TC resource is Normal voice coding/decoding or TCTYPE
= GTC is contained in the SET TCTYPE MML script, the TC type is incorrectly
configured. In this situation, run the SET TCTYPE command for all DPU boards with
The type of TC resource set to ITC(Packet Conversion).
 The assignment fails. The Assignment Failure message contains the cause value of
information-element-or-field-missing.
On the LMT, run the LST GCNNODE command to check whether the value of Bearer
for A Interface User Plane is TDM.
Alternatively, check whether ATRANSMODE=TDM is contained in the ADD
GCNNODE MML script in the exported MML scripts.

Ltd.
If the value of Bearer for A Interface User Plane is TDM or ATRANSMODE=TDM
is contained in the ADD GCNNODE MML script, the bearer for the A interface user
plane is incorrectly configured. In this situation, run the MOD GCNNODE command
with Bearer for A Interface User Plane set to IP and Report BSS Transmission
Capability set to YES(Yes). The following is an example: MOD GCNNODE:
CNNODEIDX=XX, ATransMode=IP, CodecRptFlg=YES;
 The assignment occasionally fails.
Run the LST IPPATH command to check whether the forward and backward
bandwidths configured for IP paths over the A interface are sufficient.

Ltd.
BSC6900/BSC6000
4 Appendix
4.1 Quick Troubleshooting of the GBAM and GOMU

Startup Failures
This section describes the emergency recovery without any spare parts in case of
GBAM/GOMU startup failures.
Startup failures refer to the start failure of the operating system after the GBAM/GOMU is
powered on.
4.1.1 Connect the keyboard and display (or KVM) to the

GBAM/GOMU. Power on the GBAM/GOMU. Check the output
information during the GBAM/GOMU startup.
The GBAM uses the keyboard with the PS/2 serial port and VGA display; the GOMU uses
the keyboard with the USB port and VGA display.
Perform the operations based on the output information.
1.1 The following information is displayed:
Press <ESC> to view diagnostic messages
Press <F2> to enter SETUP,<F12> Network Boot
Press Esc and observe the output information.
BSC6900/BSC6000

....
Drive 0 on adapter 1 is predicting a future failure... //The detailed error information may be
different from this example output information.
Press any key to continue...//This information is displayed at the end of the output
information.
Press any key and check whether the system can be started.

8131:Processor 02: Disabled
8190:Watchdog timer fail on last boot //The detailed error information may be different from
this example output information.
Press F1 to Resume, Press F2 to Run Setup//This information is displayed at the end of the
output information.
Press F1 to continue the system startup.
Reboot and Select proper Boot device
BSC6900/BSC6000
or Insert Boot Media in selected Boot device and press a key

Re-configure the RAID by referring to section 4.1.2"Check and re-configuring the RAID."
1.5 The following symptom occurs:

If the system skips the hardware self-check and directly starts the operating system, the
operating system may be faulty. Re-install the operating system by referring to section
4.1.4"Re-install the Linux operating system."
If kernel painic:***** is displayed, the kernel of the operating system breaks down.
4.1.2 Check and re-configuring the RAID.

 GBAM
See section 5.1.2.2 "Checking the RAID of the GBAM Server Hard Disk", section
5.1.2.3 "Deleting the RAID of the GBAM Server Hard Disk", and section 5.1.2.4
"Configuring the RAID of the GBAM Server Hard Disk" in the BSC GBAM
Management Guide (V900R008C12_06).
 GOMU
See section 4.3.6 "Configuring RAID 1 of the OMU Hard Disk" in the BSC OMU
Serial cables are used for OMU management. If no serial cable is available on site, use the keyboard and
display.
4.1.3 Remove and insert the hard disks.

 GBAM
Power off the GBAM. Open the GBAM front panel and remove a hard disk. Power on
the GBAM and check its operating status. If the fault persists, power off the GBAM and
insert the plugged out hard disk. Remove another hard disk. Then, power on the GBAM
and check its operating status.
For details about how to remove the GBAM front panel, see IBM x3650T Product Guide
2008.
For details about how to remove and insert hard disks, see IBM x3650T Product Guide
2008.
 GOMU
BSC6900/BSC6000
Remove the OMU board to power it off. Unscrew two screws of a hard disk to remove
the hard disk. Then, insert the hard disk and power the OMU board. Check the operating
status of the OMU board.
If the fault persists, remove the OMU board and insert the removed hard disk. Fasten the
screws of the hard disk. Remove another hard disk. Then, insert the OMU board and
power it on. Check the operating status of the OMU board.
4.1.4 Re-install the Linux operating system.

 GBAM
You can obtain the IBM x3650t GBAM system restoration disk at the support website:
Software Center > Controlled Tool > Wireless Network > GBSS Product
Maintenance Tools > IBM x3650t Server.
You can obtain the HP cc3310 GBAM system restoration disk at the support website:
Software Center > Controlled Tool > Wireless Network > GBSS Product
Maintenance Tools > HP cc3310 Server.
Huawei C5210 can use the restoration disk for HP cc3310.
For the BSC6900, you must bind the network adapter after the GBAM operating system
is re-installed.
You can obtain the network adapter binding tool at the support website: Software
Center > Controlled Tool > Wireless Network > GBSS Product Maintenance Tools >
GSM BSC6000 Network Adapter Binding Tool.
 GOMU
For the BSC6000:
You can install the SUSE system in the following ways:
 Use the fixomu disk to install the SUSE operating system.
You can obtain the fixomu disk at the support website: Software Center > Controlled
Tool > Wireless Network > GBSS Product Maintenance Tools > FIXOMU (for
BSC6000V900R008C12).part1_VER, FIXOMU(for
BSC6000V900R008C12).part2_VER, FIXOMU(for
BSC6000V900R008C12).part3_VER, and FIXOMU(for
BSC6000V900R008C12).part4_VER.
For details, see section 9.12 "Recovering the OMU Server using the Fault Recovery Tool
in BSC OMU Management Guide (V900R008C12_06).
 Use the easyinstall to install the SUSE operating system (use the easyinstall installation
disk, SUSE 9 disk, and SUSE 9 SP3 disk that are delivered with the OMU board).
For details, see chapter 5 "Installing the GOMU Operating System" in the BSC OMU
For the BSC6900:
You can install the operating system (Dopra or SUSE) of the BSC6900 in the following ways:
 Use the Dopra USB disk preparation tool to install the Dopra operating system.
You can obtain the Dopra installation tool at the support website: Software Center >
Version Software > Wireless Network > SingleRAN > SRAN Operation and
Maintenance Tools > Dopra_Linux_USB Disk Preparation Tool.
 Use the fixomu or easyinstall to install the SUSE operating system.
BSC6900/BSC6000
4.2 Precautions for Replacing the GBAM Server with the

GOMU Board
4.2.1 Check whether the GOMU spare part meets the
requirements.
The OMU boards that support only the SUSE 9.3 operating system include the default
delivered OMUb boards and OMUa board with the SUSE 9.3 operating system.
Check method:
Insert an OMU board to any available slot in the subrack. After logging in to the OMU
over the PuTTY, run uname -r. If the following information is displayed, the OMU
operating system is the SUSE operating system: 2.6.5-7.244-smp.
The BSC6900 supports the OMU boards (OMUa, OMUb, and OMUc) with the SUSE,
Dopra, and Windows operating systems.
On the GSM network, the OMU boards with the Linux operating system are used by
default. Theoretically, the OMUa boards with the Windows system and supporting the
3G standard can be used.
The BOM codes of OMU boards are as follows:
OMUa: 02238806
OMUb: 02237111
OMUc: 03053461
4.2.2 Check whether the available slots in the subrack meet the
GOMU installation requirements.
An OMUa or OMUb board occupies two slots and an OMUc board occupies one slot.
The requirements for slots in subrack 0 in different BSC versions are as follows:
R3: The OMU board can be installed in slots 20 and 21 or slots 22 and 23.
R8C01 and R8C12: The OMU board can be installed in slots 0 and 1, slots 2 and 3, slots
20 and 21, or slots 22 and 23.
R8C15: The OMU board can be installed in slots 0 and 1, slots 2 and 3, slots 20 and 21,
slots 22 and 23, slots 24 and 25, or slots 26 and 27.
All versions: The OMU board can be installed in slots 0 and 1, slots 2 and 3, slots 20 and
21, slots 22 and 23, slots 24 and 25, or slots 26 and 27.
(The OMUc can be installed in slots 0 to 3, slots 20 to 23, or slots 24 to 27. Note that the
active and standby OMUc boards must be installed in adjacent slots.)
If no available slot is provided by the subrack, you can move certain boards in the
subrack. To move a board, modify the configuration data and adjust the board and cable
connections in the subrack.
BSC6900/BSC6000
4.2.3 Convert the BSC configuration data.

1. Move the board.
Log in to the LMT in offline mode and select the GBAM mode. Delete the boards
that occupy the OMU slots. Add these boards to other slots and configure the related
data. Then, save the configurations in offline mode.
2. Convert the data.
Log in to the LMT in offline mode and select the GBAM mode. Convert the data
related to board moving to the data in front OMU installation mode or rear OMU
installation mode based on the prompt information.
Move the boards and convert the data.
In the MML configuration script, modify the ADD BRD command and other related
commands used by the boards that occupy the OMU slots. Enable these boards to occupy
other slots. Then, add the ADD BRD MML command used for adding the OMU boards.
4.2.4 Install the OMU software.

Remove the boards that occupy the OMU slots and insert these boards to other slots.
Insert the OMU board and manually install the software. The precautions for the OMU
software installation are as follows:
− For the OMU basic versions, run rpm -Uvh to install the software.
− You can download the OMU patch package on the MML client and use the PuTTY to
run the upgrade script to install the OMU patches. The OMU patches are not installed
using the rpm command.
− After the OMU patches are installed, load and activate the host software and hot
patches of the host.
You can load and activate the host software and hot patches of the host as follows
when the services are properly provided on the front end:
a. Disable the network adapter of the internal network of the OMU (When the
OMU is running, use the PuTTY to run ifdown bond0).
b. On the MML client, load and activate the host software and hot patches of the
host.
c. Disable the OMU. Enable the network adapter of the internal network (use the
PuTTY to run ifup bond0). Then, enable the OMU.
1. The precautions for preparing the version installation package with patches are as
follows:
For the R11 version, save the PAT file in the patch directory of the SPC basic
version.
For the R12 and later versions, save the entire patch version package in the patch
directory of the basic version.
2. In the R11 version, you must run INS PATCH to install the hot patches.
3. Ensure that the subracks are in the ineffective mode when you import the MML
script. Then, reset the subracks in effective mode (the subrack reset must not affect
ongoing services).
BSC6900/BSC6000
4.2.5 Restore the data.

The precautions for data restoration are as follows:
Save the configuration data file (in *.dat format) in the \bsc6000\data\datafile directory.
On the PuTTY, enter the /BSC6000/bscswm/omuroot/upgrade directory and run
./precfg.sh ****.dat to import the configuration data. Data can be imported only to the
active OMU. If the data is imported to the standby OMU, perform the OMU switchover.
The installed OMU has the minimum configuration. Data cannot be imported over the
LMT because the data such as the OPC is not configured.
After the data is imported, check the data consistency. If the data is inconsistent, reset the
subrack.
Import the MML script when the subracks are in ineffective mode. The database file in
*.bak format that does not require board moving can be imported using the
omu_backup_linker in the /mbsc/bam/common/services directory.
The omu_backup_linker is saved in the /BSC6000/data/mbsc/bam/common/services directory in the

SUSE operating system.
After the database file is imported, ensure that the subracks are in effective mode. Run
ACT CRC to check the data consistency. If the data is inconsistent, reset the OMU
board (if the SCU data is inconsistent, reset the subrack).
4.2.6 Activate the license.

After the data is imported and the data consistency is ensured, activate the license.
4.2.7 Verify the operation results.

a. Check whether the front end and back end can be maintained, whether alarms are
reported successfully, and whether the versions of the front end and back end are
consistent.
b. Check whether the M2000 can perform the maintenance tasks properly and whether
the alarms and traffic statistics are reported successfully.
c. Verify the services. Perform dialing tests. Check the channel usage.

GSM Troubleshooting Guide 20140516-A - V1.5 (BSC6000&BSC6900)

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

GSM Troubleshooting Guide 20140516-A - V1.5 (BSC6000&BSC6900)

Uploaded by

Copyright:

Available Formats

Doc Code Product Name BSC6900/BSC6000

Intended Audience GSM Accident Recovery Team Product Version R15

GSM Troubleshooting Guide

Prepared By GSM Accident Recovery Team Date 2013-09-17

Huawei Technologies Co., Ltd.

Date Issue Description Author

Issue 1.46 (2013-09-17) Huawei Proprietary and Confidential i

4 Guide to Common Emergency Recovery..................................................................................7

5.1.4 Re-install the Linux operating system.......................................................................................................................55

This document is intended for the following personnel:

1.1 Fault Scope Identification of CS Services

Faults at a cell Counters on accessibility: ALM-21801 GSM Cell out of

Counters on retainability: ALM-21512 LAPD Link Fault

RH303: CELL.HO.SUCC.RATE Faulty

1.2 Fault Scope Identification of PS Services

Check whether the GbFr: GbFr: GbFr:

DSP NSVL GbIP: ALM-21346 IP Connectivity

Calls cannot be Low location update success rate

2020-4-12 Huawei Proprietary and Confidential 7

Circuit services: Times of immediate assignment failures = CA300J:

2020-4-12 Huawei Proprietary and Confidential 8

BSC6000: MOD FCSW: CHREQCSAVGMSGNUMINPERIOD=100;

BSC6900: SET BSCFCPARA: CHREQCSMAXMSGNUMINPERIOD=10,

ACT GCELL:IDTYPE=BYID,CELLID=(involved cell ID)

2020-4-12 Huawei Proprietary and Confidential 9

g Reset the DPUc/DPUf boards one by one.

Available (a large number of A312F: Number of Assignment

1000 Mbit/s, and configure this port with the same

ALM-21604 Insufficient Transmission Resources was introduced in BSC6900 V900R014.

2020-4-12 Huawei Proprietary and Confidential 13

CS Paging Message Num in Period in SET BSCFCPARA to the number of LACs x

3.1.2 Faulty SS7 Links

of 1s in the signaling link mask is n2 (2^n2 must be greater than or

− Slot number of port A

− Slot number of port A

16.Switch over transmission links.

18.(Primary operation) Run the DEA BTS command to deactivate BTSs,

BSC6900: SET BSCFCPARA: CHREQCSMAXMSGNUMINPERIOD=10,

Then, check whether services recover.

2020-4-12 Huawei Proprietary and Confidential 17

BSC6900: SET BSCFCPARA: CHREQCSMAXMSGNUMINPERIOD=10,

Then, check whether services recover.

for the port corresponding to the A interface board in the TC subrack.

2.1.1 Interrupted TC Subracks

3.1.3 TC DSP Failures

2.1.2 Faulty Voice Services

Noise, one-way audio, or no BSC6000:

2020-4-12 Huawei Proprietary and Confidential 22

− Tc Mute Detect Flag

because voice services will be interrupted during DPU reset.

Common 1. If UmVer is set to GSM_PHASE_1, change the value to GSM_PHASE_2Plus.

2020-4-12 Huawei Proprietary and Confidential 25

V900R012C01SPC550 and later V900R012C01 patch versions: 10480

2020-4-12 Huawei Proprietary and Confidential 26

3.2.2 Gb Interface Faults

2020-4-12 Huawei Proprietary and Confidential 30

3.2.3 Alarms over the Gb Interface

2020-4-12 Huawei Proprietary and Confidential 32

 If yes, clear these alarms by following steps in the corresponding

3.3 BTS Link Disconnection and Cell Out-Of-Service

2020-4-12 Huawei Proprietary and Confidential 33

backup power saving is enabled, run the LST BTSBAKPWR command

Abis interface board.