Professional Documents
Culture Documents
Troubleshooting Guide
Issue
01
Date
2014-05-31
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and
the customer. All or part of the products, services and features described in this document may not be
within the purchase scope or the usage scope. Unless otherwise specified in the contract, all statements,
information, and recommendations in this document are provided "AS IS" without warranties, guarantees or
representations of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2014-05-31)
Preface
Preface
Overview
This document describes how to troubleshoot common faults that occur after the RASYS is
operational. Common faults include faults detected during routine maintenance, faults
detected during alarm handling, emergency faults, and faults reported by customers.
Intended Audience
This document is intended for:
System engineers
Field engineers
Change History
Issue
Description
01 (2014-05-31)
Draft A (2013-10-30)
Issue 01 (2014-05-31)
ii
Content
Content
Preface ............................................................................................................................................... ii
1 Safety Precautions ......................................................................................................................... 1
1.1 General Safety Precautions .............................................................................................................................. 1
1.1.1 All Safety Precautions ............................................................................................................................. 1
1.1.2 Symbols .................................................................................................................................................. 1
1.1.3 Local Safety Regulations ........................................................................................................................ 2
1.1.4 General Installation Requirements .......................................................................................................... 2
1.1.5 Grounding Requirements ........................................................................................................................ 2
1.1.6 Human Safety.......................................................................................................................................... 2
1.1.7 Equipment Safety .................................................................................................................................... 2
1.2 Electrical Safety ............................................................................................................................................... 3
1.2.1 High Voltage ........................................................................................................................................... 3
1.2.2 Thunderstorm .......................................................................................................................................... 3
1.2.3 High Electrical Leakage .......................................................................................................................... 3
1.2.4 Power Cable ............................................................................................................................................ 4
1.2.5 Fuse ......................................................................................................................................................... 4
1.2.6 Electrostatic Discharge............................................................................................................................ 4
1.3 Inflammable Environment ................................................................................................................................ 5
1.4 Batteries ........................................................................................................................................................... 5
1.4.1 Storage Batteries ..................................................................................................................................... 5
1.4.2 Lithium Batteries .................................................................................................................................... 7
1.5 Radiation .......................................................................................................................................................... 8
1.5.1 Electromagnetic Field Exposure ............................................................................................................. 8
1.5.2 Laser Hazards.......................................................................................................................................... 8
1.6 Working at Heights ........................................................................................................................................... 9
1.6.1 Hoisting Heavy Objects .......................................................................................................................... 9
1.6.2 Using Ladders ....................................................................................................................................... 10
1.7 Mechanical Safety .......................................................................................................................................... 12
1.7.1 Drilling Holes........................................................................................................................................ 12
1.7.2 Handling Sharp Objects ........................................................................................................................ 12
1.7.3 Handling Fans ....................................................................................................................................... 12
1.7.4 Moving Heavy Objects ......................................................................................................................... 12
Issue 01 (2014-05-31)
iii
Content
Issue 01 (2014-05-31)
iv
Content
Issue 01 (2014-05-31)
Content
Issue 01 (2014-05-31)
vi
Content
Issue 01 (2014-05-31)
vii
Content
Issue 01 (2014-05-31)
viii
1 Safety Precautions
Safety Precautions
1.1.2 Symbols
This symbol indicates that a hazard with a high level of risk, which if not avoided, will result
in death or serious injury.
This symbol indicates a potentially hazardous situation, which if not avoided, could result in
equipment damage, data loss, performance degradation, or unexpected results.
This symbol indicates additional information provided to emphasize or supplement important points of
an operation.
Issue 01 (2014-05-31)
1 Safety Precautions
Only well-trained and qualified personnel are allowed to install and maintain Huawei
equipment.
Only qualified professional personnel are allowed to remove safety facilitates and repair
the equipment.
Operators must immediately report faults or errors that may cause safety problems.
Remove the AC power connector when there is lightning. Do not use fixed or touch
terminals or antenna connectors when there is lightning.
The preceding instructions apply to wireless fixed terminals.
To prevent electric shock, do not connect a safety extra-low voltage (SELV) circuit to a
telecommunication network voltage (TNV) circuit.
To prevent laser radiation from injuring your eyes, never look into the optical fiber outlet
without eye protection.
To prevent electric shock and burns, wear electrostatic discharge (ESD) clothing, gloves,
and wrist strap. Remove conductors such as jewelry and watches before operating
equipment.
In the event of a fire, evacuate the building or equipment site. Raise a fire alarm at the
closest alarm point, or call the emergency number. Do not re-enter a burning building
under any circumstances.
Before operation, securely fix equipment on the floor or to other immovable objects such
as walls and mounting racks.
Issue 01 (2014-05-31)
1 Safety Precautions
After installing the equipment, clear packaging materials from the equipment site.
Only qualified and authorized electricians are allowed to install the AC facility and
perform high voltage and AC operations.
When an operation is performed in a damp environment, make sure that the equipment is
dry. When water is found in a cabinet or the cabinet is damp, power off the cabinet
immediately.
High-voltage power supply provides power for the system in operation. Direct or indirect
contact with high voltage through damp objects can be fatal.
Improper high voltage operations may cause accidents, such as fire and electrical shock.
1.2.2 Thunderstorm
Do not perform any operations, including high voltage and AC operations, on steel towers or
mast during a thunderstorm.
The preceding requirements only apply to BTSs and devices equipped with an antenna or
GPS antenna.
Ground a device before powering it on. Otherwise, personal injury or equipment damage may
be caused by high leakage current.
Issue 01 (2014-05-31)
1 Safety Precautions
Before installing or removing a power cable, turn off the power switch.
Before connecting a power cable, ensure that the labels of the power cables are correct.
Do not install or remove power cables when a device is in power-on state. Transient contact
between the core of the power cable and the conductor may generate electric arcs or sparks,
which may cause fire or harm human eyes.
1.2.5 Fuse
If a fuse is replaced, the new fuse must be of the same type and specifications.
The static electricity generated by human bodies may damage the electrostatic-sensitive
components, such as the large-scale integrated (LIS) circuits on boards.
Body movement, friction between bodies and clothes, friction between shoes and floors,
or handling of plastic articles can cause static electromagnetic fields on human bodies.
These static electromagnetic fields cannot be eliminated until the static is discharged.
Issue 01 (2014-05-31)
1 Safety Precautions
Do not store a device or perform any operation in an environment that has inflammable and
explosives air or gas.
Operating electrical devices in an inflammable environment can be fatal.
1.4 Batteries
1.4.1 Storage Batteries
Before handling storage batteries, carefully read safety precautions for battery handling and
connection.
Issue 01 (2014-05-31)
1 Safety Precautions
Improper handling of storage batteries causes hazards. Avoid short circuits or electrolyte
overflows, or leakages when handling storage batteries.
An electrolyte overflow may damage equipment. It can corrode metal parts and circuit
boards, and ultimately cause short circuits of boards and damage equipment.
Storage batteries store high energy. Improper operations can result in short circuits and
cause severe personal harm.
General Precautions
Before installing and maintaining a storage battery, observe the following precautions:
When handling a storage battery, ensure that its electrodes are upward. Leaning or
reversing the storage battery is prohibited.
Short Circuit
A battery short circuit may cause injuries. Although the voltage of ordinary batteries is low,
the instantaneous high current caused by the short circuit releases a great deal of energy.
Keep metal objects, which may cause a battery short circuit, away from batteries. If metal
objects must be used, disconnect the battery in use before performing operations.
Hazardous Gas
Do not use unsealed lead-acid storage batteries. Lead-acid storage batteries must be stable and
placed horizontally to prevent the batteries from releasing flammable gas, which may cause
fire or erode the device.
When in use, lead-acid storage batteries emit flammable gas. Therefore, ventilation and
fireproofing measures must be taken at the sites where lead-acid storage batteries are used.
Issue 01 (2014-05-31)
1 Safety Precautions
Battery Temperature
Excessive heat can cause the battery casing to soften and warp, potentially resulting in
electrolyte overflow.
When the temperature of a battery is higher than 60C, check the battery for electrolyte
overflow. If the electrolyte overflows, immediately absorb and counteract the electrolyte. You
can use the following substances to absorb and counteract the leaking electrolyte:
Choose a substance to counteract and absorb the leaking electrolyte according to the
instructions provided by the battery manufacturer.
Battery Leakage
When there is electrolyte leakage, immediately absorb and counteract the electrolyte.
When moving or handling a battery that has electrolyte leakage, note that electrolyte in
contact with skin or eyes can cause injury. In the event of electrolyte injuries, rinse the
affected area with water and seek medical attention immediately.
Issue 01 (2014-05-31)
1 Safety Precautions
1.5 Radiation
1.5.1 Electromagnetic Field Exposure
Radio frequency signals with high intensity are harmful to the human body.
Before installing or maintaining an antenna on a steel tower or mast with a large number of
transmitter antennas, coordinate with parties concerned to switch off the transmitter antennas.
The Base Transceiver Station (BTS) emits radio frequency (RF) radiation (radiation hazard).
Before installing or operating BTSs, be aware of RF safety instructions. Follow local
regulations when installing BTSs.
Exclusion Zones
Antennas must be properly located to prevent the public from accessing areas where RF
exposure levels exceed safety limits.
If RF exposure level exceeds safety limits, ensure that transmitter antennas are switched
off when working with or near antennas. Areas with excessive RF exposure levels must
be confined within a distance of 10 m from antennas.
Each exclusion zone must be defined by a physical barrier and by recognizable sign
warning the public and workers.
When handling optical fibers, do not stand close to, or look into the optical fiber outlet
without eye protection.
Laser transceivers or transmitters are used in the optical transmission system and associated
test tools. The laser transmitted through optical fibers has very high power density and is
invisible to human eyes. A beam of light can cause damage to the retina.
Generally, staring into the end of an exposed optical fiber or broken optical fiber without eye
protection from a distance of more than 150 mm [5.91 in.] will not cause eye injury. However,
eyes may be damaged if an optical tool such as a microscope, magnifying glass, or eye loupe
is used to view a bare optical fiber end.
To prevent laser radiation, observe the following precautions:
Only trained and authorized personnel are allowed to perform later-related operations.
Switch off units producing laser signals before disconnecting an optical fiber connector.
Never look into the end of an exposed optical fiber or open connector if you are not sure
whether the optical source is switched off.
Issue 01 (2014-05-31)
1 Safety Precautions
Use an optical power meter to check that the optical source is switched off.
Before opening the front door of an optical transmission system, ensure that you are not
exposed to laser radiation.
Do not use an optical tool such as a microscope, magnifying glass, or eye loupe to view
optical fiber connectors or ends.
Only trained and qualified personnel are allowed to cut and splice optical fibers.
Before cutting or splicing an optical fiber, ensure that the optical fiber is disconnected
from the optical source. After disconnecting the optical fiber, use protecting caps to
protect all optical connectors.
Prevent the devices and tools that you carry from falling down.
Take safety and protection measures, such as wear a helmet and safety belt.
Ensure that adequate protective clothing, essential in cold and wet weather, is available.
Ensure all lifting devices are tested and approved, and ready for use.
Do not walk below the cantilever or lifted object when heavy objects are being hoisted.
Only trained and qualified personnel are allowed to perform hoisting operations.
Ensure the hoisting tools are tested and approved, and ready for use.
Before hoisting heavy objects, ensure that the hoisting tools are fixed to a secure object
or wall with good weight capacity.
Ensure that the angle formed by two lifting straps is not larger than 90 degrees. See
Figure 1-2.
Issue 01 (2014-05-31)
1 Safety Precautions
Before using a ladder, check whether it is damaged. Only use ladders in good condition.
Check the maximum weight capacity of the ladder. Avoid overweighting the ladder.
Placing a Ladder
The recommended gradient of ladders is 75 degrees. You can measure the gradient of the
ladder with a right angle or your arms, as shown in Figure 1-3.
When using a ladder, ensure that it is securely placed. Ensure the wider feet of the ladder are
downward, and take preventive measures to protect the ladder from sliding.
Issue 01 (2014-05-31)
10
1 Safety Precautions
Ensure that your bodys center of gravity does not deviate from the edges of the two long
sides.
To reduce the risk of falling, hold your balance on the ladder before performing an
operation.
Do not climb higher than the fourth rung of the ladder counted from up to down. If you
need to climb a roof, ensure that the ladder top is at least one meter higher than the roof,
as shown in Figure 1-4.
Figure 1-4 Ladder with its top one meter higher than the roof
Issue 01 (2014-05-31)
11
1 Safety Precautions
Do not drill holes in cabinets without permission. Drilling holes without complying with
requirements may affect the electromagnetic shielding performance of the cabinet and
damage cables inside. In addition, if scraps caused by drilling enter the cabinet, the printed
circuit boards (PCBs) may be short circuited.
Wear an eye protection when drilling holes to prevent your eyes from being injured by
splashing metal scraps.
Ensure that the scraps caused by drilling do not enter the cabinet. After drilling, clear the
metal scraps immediately.
Before you hold or carry a device, wear protective gloves to avoid getting injured by sharp
edges of the device.
When replacing a component, place the component, screws, and tools in a safe place. If
these objects fall into operating fans, the fans may be damaged.
Do not insert your fingers or boards into operating fans until the fans are switched off
and stop running.
When a chassis is being moved out of a cabinet, unsecured or heavy objects may tip over
if not properly secured, causing personal injury.
Issue 01 (2014-05-31)
12
1 Safety Precautions
Generally, two persons are required to carry a chassis. When moving a chassis, keep
your back straight and move carefully to prevent a sprain.
When moving or lifting a chassis, hold the handles or bottom of the chassis. Do not hold
the handles of components installed in the chassis, such as power modules, fan boxes,
and boards.
1.8 Others
Installing or Removing a Board
Before installing a board, wear an ESD wrist strap or gloves. Use proper force to prevent the
pins on the backplane from being bent.
When installing or removing a board, observe the following precautions:
Prevent the surface of a board from contacting the surface of another board. This
prevents the boards from being short-circuited or scratched.
To prevent electrostatic-sensitive devices from being damaged by ESD, do not touch the
circuits, components, connectors, or connection slots on boards.
Do not bundle signal cables along with high current cables or high voltage cables.
Cables can be laid or installed only when the temperature is higher than 0C.
Before laying out cables that have been stored at a temperature lower than 0C, move the
cables to an environment of the ambient temperature and store them at the ambient
temperature for at least 24 hours.
Handle cables with care, especially in low temperatures. Do not drop cables directly
from the vehicle.
Issue 01 (2014-05-31)
13
Issue 01 (2014-05-31)
14
Back up data
No
Yes
Determine the scope and
type of the fault
Perform emergency
maintenance
Yes
Is the fault
an emergency
fault?
No
Locate the fault
Is the fault
rectified?
No
Yes
Record the troubleshooting
process
End
Backing Up Data
When a fault occurs, save the data and back up the relevant database, alarm information, and
log files. For more information about backing up contents and backup methods, refer to the
RASYS Routine Maintenance Guide.
Issue 01 (2014-05-31)
15
Alarms and any associated alarms generated when the fault occurs
Consult the personnel who reported the fault to learn about the fault symptoms and when,
where, and how often the fault occurs.
Consult the maintenance engineers about the running status of the equipment, fault
symptoms, operations performed before the fault occurs, and measures taken after the
fault occurs.
Evaluate the scope and impact of the fault by demonstrating the service, testing the
performance, and tracing interfaces or signaling messages.
Do not rush the handling of a fault Collect as much information as possible before you
rectify it.
Maintain effective communication with other maintenance engineers and contact them for
assistance as needed.
Handoff failure
Equipment failure
Issue 01 (2014-05-31)
16
Fault
Handoff failure
Handoff failure
Registration, authentication,
and encryption failures
Equipment failure
Some faults cannot be clearly classified. For example, a voice call failure may result from a
clock failure. When this occurs, refer to the sections related to clock failures.
The severity of a fault is determined based on its symptoms. The symptoms and related
scopes for emergency faults are listed in Table 2-2.
Table 2-2 Symptoms and related scopes for emergency faults
Symptoms
Scope
Locating a Fault
A fault may result from several events. Eliminate possible causes and determine the root
cause of the fault.
Issue 01 (2014-05-31)
17
Rectifying a Fault
After locating a fault, rectify the fault and restore the RAC by taking the necessary measures,
such as fixing circuit problems, replacing boards, modifying configuration data, switching
over boards, and resetting boards.
Application
Scenarios
Usage
Issue 01 (2014-05-31)
User-reported faults
None.
18
Application
Scenario
Usage
For details about how to use the subscriber signaling tracing tool, see
the RAC6690 Operation Guide and RASYS RAC6690 Service
Maintenance System Help.
Interface Tracing
Function
Application
Scenario
Usage
Issue 01 (2014-05-31)
Used for:
Locating link problems, such as link setup, link deletion, and link
modification.
For details about how to use the interface tracing tool, see the CDMA
WLL LMT User Guide and RASYS CDMA Alarm Management
System Help.
19
Alarm Information
Function
Application
Scenario
Used for:
Usage
For details about how to use the Alarm Management System, see the
CDMA WLL LMT User Guide and Airbridge RASYS CDMA Alarm
Management System Help.
Application
Scenario
Usage
Issue 01 (2014-05-31)
For more information about the meaning of the indicator status, refer
to the Indicators on RACBoards section of the RAC6690 Hardware
Description.
20
Application
Scenario
Usage
Checking Data
Function
Signaling messages
Usage
Issue 01 (2014-05-31)
21
Application
Scenario
Usage
None.
Instruments, meters, and software test tools are a common way for
testing specific resources, such as transcoders (TCs), and Service
Delivery Units (SDUs). Measured data is used for determining
whether a device is faulty, or if its performance sharply declines.
Application
Scenario
Usage
Application
Scenario
Usage
Issue 01 (2014-05-31)
22
Application
Scenario
Usage
Application
Scenario
Usage
Issue 01 (2014-05-31)
23
Application
Scenario
Use this method to query, modify, add, and delete files of the
maintained devices, and to upload and download files.
Usage
Tool List
Table 2-3 describes the tools used for troubleshooting RASYS faults.
Table 2-3 Troubleshooting tools
Category
Name
Function
Reference
General
tool
LMT
Special
tools
Alarm
Management
System
U2000 client
Cait
QXDM
Issue 01 (2014-05-31)
24
Category
Meter
Name
Function
Reference
Iperf
DSLA
LMT
The LMT is a PC that has maintenance system software installed, and is connected to the
RAC for maintaining the RASYS.
For details about how to start the LMT, see the RASYS LMT User Manual.
Remote Access
For the principles and methods of remote access, see the RAC6690 BAM Management Guide.
Procedure
RAC version
information
Run the LST BAMVER command on the RAC LMT. Then obtain the RAC version
information from the result of the command.
RAC configuration
script
Running logs of
RAC boards or
subsystems
The existing running logs for RAC boards or subsystems are saved in
D:\SysExpdat\runlog on the BAM. Historical logs for the RAC boards or subsystems
are saved in D:\CDMA2000\Backup\FamRunLog on the BAM. The logs are saved by
date. Obtain the required running logs for boards based on the date. When the size of
data reaches 10 MB, the running log is generated and is named by date.
After the command executes successfully, obtain the exported script file from
D:\cdma2000\backup\mmlscript on the BAM.
The *.dat.bz2 file in the directory is the process file of the running log and cannot be
decompressed.
To view the current running log of boards or subsystems, run the COL FAMLOG
command.
Running logs of
specific RAC boards
Issue 01 (2014-05-31)
The existing running logs for RAC boards or subsystems are saved in
D:\SysExpdat\runlog on the BAM. Historical logs for the RAC boards or subsystems
are saved in D:\CDMA2000\Backup\FamRunLog on the BAM. The logs are saved by
25
Item
Procedure
or subsystems
date. The name of a board log file or a subsystem log file contains the actual board
name or subsystem name. Obtain the running logs for a specific board or subsystem.
Information about
existing alarms
Information about
historical alarms
Raw traffic statistics files are saved by date in D:\cdma2000 on the BAM. Obtain the
raw traffic statistics file based on the date.
Create and start a task for tracing call logs by using the SysExplorer. The tracing file is
saved in D:\SysExpDat\Clt\.
Create and start a task for capturing packets by using the SysExplorer. The packet
capture file is saved in D:\SysExpDat\UserPacketCatch\.
Single-subscriber
traffic tracing file
Start a task for tracing the single-subscriber traffic on the Service Maintenance System.
The tracing file is saved in D:\Airbridge\OutputFile\RMON\USERTP_RESOURCE on
the BAM.
Radio resource
monitoring file
Start a task for monitoring radio resources on the Service Maintenance System. The
monitoring file is saved in D:\Airbridge\OutputFile\RMON\RADIO_RESOURCE on
the BAM.
1. Run the MOD CDRFILTER command on the LMT to enable the CDR filter switch.
2. Add the corresponding CDR carrier, subscriber, and subsystem based on the CDR
trace type.
3. Start the CDR tracing. After a raw CDR file is generated, it is automatically saved in
D:\SysExtDat\CDR on the BAM.
4. After the CDR tracing is started for a specific period, obtain the raw CDR file in this
directory.
Issue 01 (2014-05-31)
The raw license file is saved in D:\cdma2000\loaddata on the BAM. The raw license file
name is raclicense.dat.
26
Item
Procedure
License information
2. Run the DSP LICENSEFILEINFO command on the LMT to query the license
information about the FAM and BAM.
3.Run the following commands:
DSP RACLICENSECFG
DSP SYSESN
DSP RACLICENSECFG
Procedure
Alarm information
Run the following command to query current alarms and historical alarms.
LST NEALMLOG: ALMTP=ALL, SD=2009&&10&11, ED=2009&&10&12,
STAT=NORMAL;
This command enables you to query alarms that are generated within a set time period.
In the above example, the information in red represents the start and end date of that
time period. If the start and end date are not specified, the number of alarms you query
at a time may exceed the maximum of 1,000. If this happens, query results cannot be
exported. Huawei recommends you use this command to specify the start and end date
when querying historical alarms. If the date information is not specified, the date when
the command is executed is considered the start date and end date by default, and all
the alarms that are generated from 00:00:00 to the current time of the day are queried,
including alarms that are not cleared.
Run the LST CURALM command to query existing alarms and run the LST
HISALM command to query historical alarms through the Telnet.
1. Run the RPT CBTSLOG command to enable the BTS to report running logs. After
this command is successfully executed, the BTS takes about 10 minutes to upload the
log file because of its large size.
2. The BTS logs are classified into running logs and operation logs, which are saved as
files in D:\Airbridge\Services\BTSLog. Each file name contains the BTS ID. The .bak
file containing running logs is a historical log file.
BAM log
Configuration script
1. Run the SAV CBTSCFG: BTSID=XXX; command to save the BTS configuration
scripts on the Service Maintenance System.
2. The BTS configuration scripts are saved in D:\cdma2000\BTSLoad\cfg.
1.The logs of the upgrade wizard client are saved in the following path:
C:\Program Files\HuaWei\VerUpgrade\CBTS\Log
The logs are saved in the default path C:\Program Files\ or the installation directory
HuaWei\VerUpgrade\CBTS\Log.
2.The logs of the upgrade wizard server are saved in the following paths on the active
Issue 01 (2014-05-31)
27
Item
Procedure
and standby BAMs:
C:\WINDOWS\BTSVutServer\Log
D:\cdma2000\VerUpgrade\Log\BTSVutServer
If disk F exists, the logs are saved in F:\cdma2000\VerUpgrade\Log\BTSVutServer.
(Received Signal
Strength Indicator)
RSSI tracing
1. Start the RSSI tracing for the BTS on the Service Maintenance System.
2. The file containing statistics on the error codes of BTS links is saved in
D:\Airbridge\services\LinkErrCnt. The file name is BTSXXXXLinkErrorCount.txt,
where XXXX indicates the BTS ID.
Issue 01 (2014-05-31)
28
Possible Cause
The possible causes for the failure are as follows:
Workaround
Issue 01 (2014-05-31)
29
For more information about how to replace an interface board, see "Replacing RAC Boards"
in the RAC6690 Site Maintenance Guide.
Troubleshooting Method
At sites where interface boards are configured independently, back up the interface
boards using the same type of board.
Possible Cause
The possible causes for the failure are as follows:
The pins on the backplane connector are bent, which causes a short circuit or open signal
circuit on the backplane.
Workaround
Replace the faulty backplane.
For more information about how to replace a subrack backplane, see "Maintaining RAC
Subracks" in the RAC6690 Site Maintenance Guide.
Troubleshooting Method
Back up the subrack backplane based on actual configurations of the live network.
Possible Cause
The Y-shaped clock cable is faulty.
Workaround
Replace the damaged Y-shaped clock cable.
Issue 01 (2014-05-31)
30
For more information about how to replace the Y-shaped clock cable, see "Replacing RAC
Cables" in the RAC6690 Site Maintenance Guide.
Troubleshooting Method
Back up the Y-shaped clock cable based on actual configurations of the live network.
Possible Cause
Two power inputs of the PDB are provided by one power distribution box. The failure of the
power distribution box results in the failure of the power distribution system.
Workaround
Rectify the fault on the input power.
For more information about how to maintain the power distribution system, see "Maintaining
the Power Supply System of the RAC" in the RAC6690 Site Maintenance Guide.
Troubleshooting Method
Check that two power inputs are provided by two power distribution cabinets. This
ensures that the power distribution system works properly when one power input fails.
Check the power distribution system thoroughly. If two power inputs are provided by
one power distribution cabinet, change the power distribution system based on
information in the RAC6690 Site Maintenance Guide.
Possible Cause
The fan box is faulty.
Workaround
Replace the faulty fan box.
For more information about how to replace a fan box, see "Maintaining RAC Subracks" in the
RAC6690 Site Maintenance Guide.
Issue 01 (2014-05-31)
31
Troubleshooting Method
Back up the fan box based on actual configurations of the live network.
Possible Cause
The possible causes for the failure are as follows:
The power module is installed improperly. As a result, the power supply between the
power distribution frame (PDF) and the cabinet fails.
The circuit breaker (or fuses) on the BTS is disconnected from the PDF or is
deteriorating. The circuit breaker deterioration may lead to unstable power supply.
The power supply of the BTS deteriorates because the wiring terminals are oxidized.
Consequently, the power module or the RF module is faulty.
Check that the screws are securely connected to the wiring posts on the top of the RAC
cabinet and check that the RAC cabinet is grounded properly. Improper grounding of the
RAC cabinet may cause high BER, resulting in frequent restarting of the BTS
Check that the power cable is securely connected to the PDF. In addition, check that lugs
are correctly installed if there are overlaid lugs
Workaround
Check whether the voltage of power supply at the top of the RAC cabinet is normal
and stable.
Set the multimeter to the DC voltage mode, and connect the positive and negative
poles of the multimeter to the positive and negative power supply terminals at the top
of the RAC cabinet respectively. The positive terminal is a GND terminal, and the
negative terminal is a 48 V terminal. The voltage of the terminals ranges from 40 V
DC to 60 V DC
If the power supply at the top of the RAC cabinet is abnormal or unstable, request
power supply maintenance engineers to rectify the faults. The abnormal or unstable
power supply may be caused by insecure wiring, cable deterioration, or fuse
disconnection (for example, fuse wires or circuit breakers are disconnected).
Troubleshooting Method
Check the power module installation, cable connections, and power supply system by using
tools and referring to the preceding handling suggestions.
Issue 01 (2014-05-31)
32
4 Troubleshooting Emergencies
Troubleshooting Emergencies
Symptom
In the coverage area of a RAC, a RAC module, or several BTSs, call setups for mobile
stations (MSs) fail.
Issue 01 (2014-05-31)
33
4 Troubleshooting Emergencies
Figure 4-1 Flowchart for troubleshooting call setup failures in the RAC coverage area
Start
Check alarms
Is the software
automatically loaded
to the faulty board
successfully?
Yes
Is there a Board
Not in Position
alarm?
No
Yes
No
Yes
Are all boards
unavailable?
No
4
End
Issue 01 (2014-05-31)
34
4 Troubleshooting Emergencies
Troubleshooting Procedure
1. Check alarms.
On the Alarm Management System, choose Browse > Fault Alarm. The Fault
Alarm Browse window is displayed.
On the Service Maintenance System, run the LST ALMLOG command to query information about all
alarms generated before a specified time.
If all the cells configured in the RAC are normal, see section 4.2.1 .
If some cells configured in the RAC are abnormal, see section 4.2.3 .
If all cells configured in the RAC are abnormal, see section 4.2.4 .
---End
Issue 01 (2014-05-31)
35
4 Troubleshooting Emergencies
Symptom
Call setups in a large coverage area fail, and all boards are unavailable. Additionally, the
following symptoms appear.
On the Service Maintenance System, the equipment panel status shows boards in all
subrack are faulty.
On the Service Maintenance System, run the DSP BRDINFO command to query the
status of the specific board. The returned result shows the board status is unavailable.
Issue 01 (2014-05-31)
36
4 Troubleshooting Emergencies
Figure 4-2 Flowchart for troubleshooting call setup failures when boards in all RAC subracks are
unavailable
Start
1
Is the ping
operation
successful?
No
Yes
3
No
Yes
Is the BSC
faulty?
No
Yes
5
End
Troubleshooting Procedure
1. On the BAM, ping the IP address of the SCUOa in the CMPS subrack.
In the Windows operating system, choose Start > Running and then run the cmd
command to open the MS-DOS window
Ping the IP address of the SCUOa in the CMPS to check whether the communication
between the BAM and the SCUOa is normal. For example, run the ping 80.130.16.192
command. The following message is displayed:
Pinging 80.130.16.192 with 32 bytes of data: Reply from 80.130.16.192: bytes=32
time<10ms TTL=255 Reply from 80.130.16.192: bytes=32 time<10ms TTL=255 Reply from
80.130.16.192: bytes=32 time<10ms TTL=255 Reply from 80.130.16.192: bytes=32
time<10ms TTL=255
Issue 01 (2014-05-31)
37
4 Troubleshooting Emergencies
If a reply message similar to the preceding one is received, communication between the
BAM and the SCUOa in the CMPS subrack is normal.
2. Check whether the Ethernet cable is properly connected and that the settings of the IP address
and subnet mask are correct.
Check whether the internal virtual IP address of the BAM is 80.0.0.255 and the subnet
mask is 255.0.0.0.
Check whether the Ethernet adapter group configuration for the BAM is correct.
Check whether all processes in the BAM manager are in the running state.
Symptom
When calls fail to be set up in the coverage area of a RAC, check the status of the cells
configured in each subrack. The symptoms are as follows:
Cells configured in some RAC subracks are abnormal, and calls fail to be set up in these
cells.
Cells configured in other RAC subracks are normal, and calls can be set up in these cells.
Issue 01 (2014-05-31)
38
4 Troubleshooting Emergencies
Figure 4-3 Flowchart for troubleshooting call setup failures when cells configured in some RAC
subracks are abnormal
Start
Are all
cells associated with
the SPUO subsystem
abnormal?
Yes
No
3
Are
all abnormal cells
associated with the
same Abis interface
board?
No
Yes
Are all abnormal cells
associated with the same
port of the Abis interface
board?
Yes
No
4
End
Troubleshooting Procedure
1. Query the SPUO subsystem associated with the abnormal cell.
Issue 01 (2014-05-31)
On the Service Maintenance System, run the DSP RES command to query the status of
all sector carriers. Record all abnormal cells.
39
4 Troubleshooting Emergencies
On the Service Maintenance System, run the LST CELL command to check the cell
information. Record the mapping between the cells and the SPUO subsystems.
Locate the SPUO subsystems associated with the abnormal cells according to the
preceding query results.
2. Switch over or replace the APUOc onto which the SPUO subsystem is loaded.
On the Service Maintenance System, run the STR MANUALSWITCHING command to
switch over the APUOc. If the service is not restored after the switchover, replace the APUOc.
3. Query the Abis interface boards associated with the abnormal cells.
On the Service Maintenance System, run the DSP RES command to query the status of
all RAC sector carriers. The status of a normal carrier meets the following requirements:
Operating Status is Enabled
Administrative Status is Unlocked
Usage Status is Active or Idle
On the Service Maintenance System, run the LST BTSLNK command to check the
mapping between the abnormal cells and the RAC Abis interface boards.
Symptom
Call setups in the coverage area of a RAC fail, and all the RAC cells are in abnormal status.
Issue 01 (2014-05-31)
40
4 Troubleshooting Emergencies
Figure 4-4 Flowchart for troubleshooting call setup failures when cells configured in all RAC
subracks are abnormal
Start
Is the APUOc
faulty?
Yes
No
Is the RAC
faulty?
No
Yes
3
End
Troubleshooting Procedure
1. Switch over or replace the APUOc.
On the Service Maintenance System, run the STR MANUALSWITCHING command to
switch over the APUOc. If the service is not restored after the switchover, replace the APUOc.
2. Collect data before resetting the RAC.
Before resetting the RAC, collect and send the necessary data to Huawei for further analysis.
3. Reset the RAC.
Run the RST FRM command to reset the RAC CSPS, and then reset the CMPS. Check
whether the fault is rectified by making a call in the problem area.
---End
Issue 01 (2014-05-31)
41
4 Troubleshooting Emergencies
The Fade Timer times out. If an MS receives over 12 (N2m) bad frames, the MS disables
its transmitter but continues to receive signals in the reverse link. If the MS receives two
continuous good frames (N3m) in 5 seconds, the MS enables its transmitter again. If the
MS fails to receive two continuous good frames in 5 seconds, the MS is reinitialized.
The reverse call drop control mechanism may differ when different devices are configured.
The BSS call drop mechanism of the Huawei CDMA2000 1X device is described as follows:
A RAC receives 300 continuous idle frames from the reverse link. During a soft handoff,
because of a long transmission delay between legs, the frames on different legs fail to be
aligned when being combined. In this case, the RAC identifies the frames that fail to be
aligned as idle frames, resulting in call drops.
After legs are combined, there are over 270 Erasure frames, or bad frames, among 300
reverse frames. This results in call drops.
The markov frame error rate (FER) is excessively high. The markov FER refers to the
proportion of bad frames to all frames that a RAC receives. If a received frame is
different from the frame generated in the RAC, the received frame is counted as a bad
frame. Additionally, lost frames are also counted as bad frames. When bad frames make
up 95% per of 500 frames, call drops occur.
In addition to monitoring radio link performance, the RAC also monitors the transmission on
the Abis and A interfaces, and running status of equipment. When a fault is detected, call
drops occur.
Table 4-1 lists the different causes of CS call drops.
Table 4-1 List of difference causes of CS call drops
Measurement
Unit
Type
Definition
Unit
CS Call Drop
Cause Categories
Times
Times
Issue 01 (2014-05-31)
42
Measurement
Unit
4 Troubleshooting Emergencies
Type
Definition
Unit
Times
Times
Times
Times
Issue 01 (2014-05-31)
43
4 Troubleshooting Emergencies
Figure 4-5 Flowchart for troubleshooting call drops for a large number of voice subscribers during
conversation
Start
1
Is the transmission
link alarm or BTS
alarm generated?
Yes
Cause value is
Abis interface
No
3
Handle alarms
Check BTSs
Other cause
values
10
Yes
Rectify BTS
resource faults
11
No
6
No
12
Yes
End
Troubleshooting Procedure
1. Check the Alarm Management System.
Log in to the Alarm Management System to check alarms.
2. Handle alarms.
If the transmission link alarm exists, see chapter 15 "Troubleshooting Transmission Failures."
Issue 01 (2014-05-31)
44
4 Troubleshooting Emergencies
If the Abis interface is configured with E1/T1 links, monitor the E1/T1 link status to
check whether faults occur on the physical link.
Run the LOP E1T1 and STR CBTSLNKDATALP commands to start the E1/T1 link
loopback test to locate the fault.
If the Abis interface is configured with Ethernet links, run the ADD ARPPRT command
to start the ARP check. If alarms are generated on the Alarm Management System, the
communication between the two ends is faulty. If no alarms are generated on the Alarm
Management System and the peer end can respond to the ARP check, communication
between the FG1B/FG2B and the peer end is normal.
If the receive power is over 94 dBm while the Ec/Io is less than 15 dBm, radio
interference or pilot pollution may exist or the size of the forward search window is set
smaller than the minimum value.
If the receive power is less than 95 dBm, radio coverage quality is poor. The problem
can be resolved by adjusting the downtilt angle or azimuth angle of the antenna, or by
increasing the antenna height or the transmit power. New BTSs are required in scenarios
where the radio coverage is not sufficient.
If the receive power is normal but the transmit power is excessively high during calls, it
may be caused by reverse interference, system overload, or not sufficient reverse
coverage. If the problem is caused by reverse interference, the RSSI and electromagnetic
interference test helps locate the source of the interference. If the problem is caused by
not sufficient reverse coverage, new BTSs are required.
Issue 01 (2014-05-31)
45
4 Troubleshooting Emergencies
The default size of the search window can satisfy the seamless coverage networking. The
sizes of forward and reverse search windows need to be enlarged only for the wide coverage
networking, or when repeaters are installed in the network.
----End
E
C
E
C
Public network
Original voice
Modulated radio signal
Frame data
PCM data
In the CDMA network, the most basic elements for voice data processing are the
coder/decoder (codec) and the echo canceler (EC). In CDMA voice services, signal flows are
described as follows:
Modulated radio signal: Refers to signals that are processed through channel encoding.
The MS sends signals to the air interface after the original voice and channel are
encoded.
Frame data: Channel decoding, a basic function provided by BTSs, converts original
voice data from PCM data to voice data frames after the original voice data is encoded
by the codec on the MSs.
PCM data: After receiving data frames sent from the BTS, the RAC decodes the data
frames into PCM data by using the codec, and then sends the PCM data to the MSC for
data exchange.
Issue 01 (2014-05-31)
46
4 Troubleshooting Emergencies
The codec functions as a voice data compressor with certain compression loss which
decreases voice quality. The CDMA2000 system supports four encoding/decoding algorithms:
QCELP13K, QCELP8K, EVRC, and EVRC-B.
Issue 01 (2014-05-31)
47
4 Troubleshooting Emergencies
Check the MS
Yes
Replace the MS
Yes
Yes
Is the radio
environment poor?
No
Check the encoding and
transmission of the voice signal
source
Yes
No
7
Is the
FER on the Um
interface
excessively
high?
9
Yes
No
Check and handle data switching
or transmission problems in the
core network
10
Is the
voice coding and
decoding algorithm set
properly?
11
No
Yes
Contact Huawei technical support
End
Issue 01 (2014-05-31)
48
4 Troubleshooting Emergencies
Troubleshooting Procedure
1. Check the MS.
Use different types of MSs for test.
2. Replace the MS.
Use higher-performance MSs.
3. Check the radio environment.
Contact network optimization personnel to check the radio environment.
4. Optimize the network.
Contact network optimization personnel to optimize the network.
5. Check the encoding and transmission of the voice signal source.
Run the STR CBTSLNKTST command to start a BTS link test on the bit error rate (BER) to
check whether the performance of the physical link transmission is normal.
6. Handle the BER problem.
Contact BTS engineers to handle the BER problem.
7. Check the frame error rate (FER) on the air interface.
On the Service Maintenance System, start the Markov Test Call State Monitoring on a
Markov-enabled MS to check whether the FER on the air interface is high.
8. Modify the FER.
Run the MOD FER command on the Service Maintenance System to decrease the FER on
the air interface.
Adjusting the target FER notably affects the voice quality of the entire network and the
system capacity. Relevant parameters are often set to general values that are widely used
in the telecom industry. Huawei recommends that you retain these values, and change
them only when necessary.
Increasing the target FER deteriorates voice quality or increases the FER in data services,
but expands the system capacity.
Decreasing the target FER increases voice quality and decreases the FER, but reduces
the system capacity.
Check the voice coding and decoding algorithm of an MS. The algorithm is configured
before the MS is delivered. Contact the MS manufacturer.
Issue 01 (2014-05-31)
49
4 Troubleshooting Emergencies
The EVRC algorithm provides better voice quality than the Q8K algorithm. Huawei recommends the
EVRC algorithm be set as the called-party assignment algorithm for the RAC and the initial algorithm
for the MS.
Check the voice coding and decoding algorithm of an MS. If the Q8K algorithm is used,
change Q8K to EVRC.
Check the called-party assignment algorithm of the RAC. If the Q8K algorithm is used,
change Q8K to EVRC.
---End
In the CDMA2000 1X network, the data services are unavailable but voice services are
normal.
Symptom
Issue 01 (2014-05-31)
50
4 Troubleshooting Emergencies
No
Is the registration
information
correct?
Yes
Yes
Replace the MS
registration
Modify the
information
3
Yes
No
4
Start user interface tracing
6
Switch over or replace the
APUOc
Yes
7
Is A11-Registration Reply
in the tracing messages?
No
Yes
Is the
communication
proper?
9
10
No
Yes
Resolve the PDSN problem
11
Configure the parameters
between the PCF and PDSN
Yes
Contact Huawei technical
support
End
Issue 01 (2014-05-31)
51
4 Troubleshooting Emergencies
Troubleshooting Procedure
1. Check the subscription information about the Mobile Station (MS) that fails to access the data
services.
In the HDB database, check whether the subscription information is correct and
whether the subscriber has been assigned the appropriate permissions to access the
data service. If the subscription information is incorrect, or the subscriber lacks the
appropriate permissions, the MSC does not send the assign req message to the RAC
after receiving a CM Service Request message from the RAC.
On the AAA server, check the subscription information about the subscriber. If the
subscription information is correct but the call is immediately released after setup
(that is, the MS fails to pass the AAA authentication), the MS is faulty or the identity
code written for the MS is incorrect. Replace the faulty MS with a new MS of the
same type or re-write the identity codes for the MS.
Check the subscription information about the EV-DO subscribers on the AN-AAA
server. If the subscription information is correct but the call is immediately released after
being set up (that is, the MS fails to pass the AN-AAA authentication), the MS is faulty
and needs to be replaced with a new MS of the same type.
Issue 01 (2014-05-31)
52
4 Troubleshooting Emergencies
During a data service call, check whether an A11-Registration Reply message is displayed in
the output window on the Service Maintenance System.
8. Check the communication between the PCF and the PDSN.
Run the ping command to check whether the communication between the PCF and the PDSN
is normal. For example, run the ping 129.11.17.230 command to check the communication of
the PDSN with the IP address of 129.11.17.230.
If the time in the returned message is excessively long or the Request timed out message
is returned, the communication is abnormal.
9. Check the cable connection between the PCF interface board and the PDSN.
Check whether the Ethernet cables are securely connected to corresponding ports.
10. Check whether the value of code is accepted (0).
In the output window of the Service Maintenance System, check whether the value of code of
the A11-Registration Reply message is accepted (0), which indicates that the PDSN receives
the A11-Registration Request message.
11. Reconfigure the parameters related to the interconnection between the PCF and the PDSN.
Check whether the interconnection parameter settings on the PCF and the PDSN are
consistent. If they are not consistent, contact RAC and PDSN data configuration engineers to
modify the parameter settings.
---End
Symptom
Table 4-2 lists the symptoms of call setup failures in the coverage area of a BTS.
Table 4-2 List of symptoms of call setup failures in the coverage area of a BTS
Item
Symptom
Service
Board status
Issue 01 (2014-05-31)
53
Alarm
4 Troubleshooting Emergencies
Analysis
When calls fail to be set up in the coverage area of a BTS, determine whether the failure
occurs on a single BTS or multiple BTSs controlled by one RAC. If the failure occurs on
multiple BTSs controlled by a RAC, contact the RAC engineers.
Table 4-3 lists the possible causes and cause analysis of call setup failures in the coverage
area of a BTS.
Table 4-3 List of possible causes and cause analysis of call setup failures in the coverage area of a
BTS
Possible Cause
Cause Analysis
Recent maloperations
Issue 01 (2014-05-31)
54
Possible Cause
Cause Analysis
4 Troubleshooting Emergencies
Faults in the
transmission system
The RRU3606/ODU3601CE is
faulty
If the OML fails, a red cross is displayed on the navigation tree on the Service
Maintenance System.
Issue 01 (2014-05-31)
55
Possible Cause
4 Troubleshooting Emergencies
Cause Analysis
Call setup faults exist in the
coverage area of all BTSs
controlled by a subrack of a RAC.
Issue 01 (2014-05-31)
56
4 Troubleshooting Emergencies
Figure 4-9 Flowchart for troubleshooting call setup failures in the coverage area of a BTS
Issue 01 (2014-05-31)
57
4 Troubleshooting Emergencies
Troubleshooting Procedure
1. Check the power supply system.
Check whether the call setup failures are caused by the power supply system.
If the BTS has proper input power but alarms related to the power module exist on the Alarm
Management System, the power module is faulty. Alarms related to the power module
include:
DC Over-Voltage Alarm
DC Under-Voltage Alarm
a.
b.
According to the alarm information, check the status of corresponding power module.
Issue 01 (2014-05-31)
58
4 Troubleshooting Emergencies
Check whether the output of the external AC/DC power supply equipment is proper.
Check whether the cable connection between the external AC/DC power supply
equipment and the BTS is secure.
Check whether the internal cable connections in the BTS are secure.
If no fault is included in the preceding checking results but alarms related to the power
module still exist in the BTS, the boards or slots of the BTS are faulty.
2. Check the transmission system.
Check whether the fault is caused by the transmission system.
If alarm related to the E1/T1 link, FE link, and IMA/UNI/FRAC/PPP link status is generated
on the Alarm Management System, the transmission system is faulty.
The BTSID and BTSTP of the BTS which are set by running the SET CBTSINFO
command are not consistent with those set on the RAC. In that case, the RAC fails to
identify the BTS and therefore calls fail to be set up in the coverage area of the BTS.
The modified transmission link data of the BTS, such as IP address, is not consistent
with that in the RAC. The inconsistency results in the connection failure of transmission
link.
Run the LST LOG command to query the commands sent recently to the BTS. For example,
if a fault occurs on March 1, 2007, run the following command to query all the commands
sent from the client before that day. (By default, a maximum of 1000 commands can be
returned.)
LST LOG: ETIME=2007&03&01;
b.
Issue 01 (2014-05-31)
Check whether the boards are faulty at the remote end or the local end.
At the local end, observe the indicators on the panel. The ALM indicator is on or
blinks if a board is faulty.
At the remote end, observe the status of each board on the Service Maintenance
System. A faulty board is displayed in red on the panel of the Service Maintenance
System.
59
4 Troubleshooting Emergencies
If calls fail to be set up in the coverage area of a BTS, restore the services first, and then troubleshoot.
If a board is faulty, replace the board in an attempt to restore the services first. Then, locate the fault.
Use the alarms displayed on the Alarm Management System to locate the faulty board.
After replacing the boards, if the fault persists, replace the slot. If the services are not restored
after the board and the slot are replaced, the fault is not on the board or in the slot.
To replace the parts of BBU3900, see the Airbridge BBU3900 User Guide.
To replace the parts of an ODU3601CE, see the Airbridge ODU3601CE User Guide.
To replace the parts of a BTS3900, see the BTS3900 Site Maintenance Guide.
To replace the parts of a BTS3900A, see the BTS3900A Site Maintenance Guide.
To replace the parts of a BTS3900C, see the BTS3900C Site Maintenance Guide.
To replace the parts of a BTS3600AC, see the BTS3600AC Site Maintenance Guide.
To replace the parts of a BTS3600CE, see the BTS3600CE Site Maintenance Guide.
On the Service Maintenance System, run the LST RACBTSINF and LST
BTSBTPINFO commands to query the BTS basic information and BOOTP information
configured in the RAC. Run the LST BTS and LST BTSBTPINFO commands to query
the BTS basic information and BOOTP information configured in the BTS.
If the BTS basic information configured in the RAC is not consistent with the
information configured in the BTS, run the MOD BTS command to modify the BTS
basic information.
If the BOOTP information configured in the RAC is not consistent with the information
configured in the BTS, run relevant MML commands to modify the BTS basic
information.
Issue 01 (2014-05-31)
For ATM over E1/T1 or IP over E1/T1 transmission, run the MOD BTSBTPINFO
command to modify the BOOTP information.
60
4 Troubleshooting Emergencies
For IP over FE transmission, run the SET CBTSOAMIP command to set the OM IP
address of the BTS.
---End
Symptom
Calls can be set up in the coverage area of the BTS when connected to the ODU3601CE.
However, calls fail to be set up in the coverage area of the ODU3601CE
Analysis
Before handling call setup failures in the coverage area of an ODU3601CE, check whether
the BTS is faulty. If an alarm is generated on the upper-level BTS, rectify the fault first.
Table 4-4 describes of the possible causes and further analysis of call setup failures in the
coverage area of an ODU3601CE
Table 4-4 Possible causes and further analysis of call setup failures in the coverage area of an
ODU3601CE
Possible Cause
Cause Analysis
Faults in the
upper-level BTS
Recent
maloperations
Hardware faults in
ODU3601CE
Issue 01 (2014-05-31)
61
4 Troubleshooting Emergencies
Possible Cause
Cause Analysis
Cable connection
faults
Incorrect
configuration data
Issue 01 (2014-05-31)
62
4 Troubleshooting Emergencies
Figure 4-10 Flowchart for troubleshooting call setup failures in the coverage area of an
ODU3601CE
Issue 01 (2014-05-31)
63
4 Troubleshooting Emergencies
Troubleshooting Procedure
1. Clear faults in the upper-level BTS.
Check whether call setup failures are caused by faults in the upper-level BTS.
If a faulty ODU3601CE is directly connected to the BTS, query the alarms generated on
the BTS. Identify alarms related to the ODU3601CE, and rectify faults according to the
alarm handling suggestions. For details regarding troubleshooting of a fault in the
upper-level BTS, see section 4.6 "Troubleshooting Call Setup Failures in the Coverage
Area of a BTS."
Issue 01 (2014-05-31)
64
4 Troubleshooting Emergencies
Check whether the optical fiber connection between the upper-level BTS and
ODU3601CE is working properly.
Check whether the optical fiber between the HCPM/HECM and OMTR is damaged.
Check whether the optical ports on the HCPM/HECM and OMTR are damaged.
If the output power of the OMTR is normal, but the output power of the OMPA is
abnormal, check the cable connection between the OMTR and OMPA. If the cable
connection is secure, the OMPA is faulty. Replace the OMPA.
Check whether an antenna VSWR alarm is generated. If an alarm exists, check the
antenna system. If there is no alarm, go to 5.
Log in to the Service Maintenance System, and click the Maintenance tab.
Locate the faulty ODU3601CE on the navigation tree, and click Device Panel under the
ODU3601CE.
Select the ODU3601CE, and observe the ODU3601CE devices displayed on the right
panel.
If some ODU3601CE modules are displayed in red, the modules are functioning
improperly.
If all the modules of the ODU3601CE are displayed in gray, the modules are offline
because of faulty optical fiber transmission.
If some ODU3601CE modules are displayed in gray, the modules are not properly
installed.
Check whether a major alarm related to the RF module, power amplifier module, or
power modules is generated. If such an alarm is generated, handle the alarm as
suggested.
For information regarding the replacement of the ODU3601CE RF module, see the
Airbridge ODU3601CE User Guide.
Issue 01 (2014-05-31)
65
4 Troubleshooting Emergencies
Check whether the antenna is damaged, and whether the connectors of the feeders and
antenna are damaged due to a water leakage. The antenna must be intact, and there must
be no water leaks on the connectors or jumpers.
If the antenna is defective, contact Huawei technical support.
If call setup failures persist after the preceding operations are performed, replace the MDFU.
----End
Symptom
Calls can be set up in the coverage areas of the BTS when connected to the RRU. However,
calls fail to be set up in the coverage area of the RRU
Analysis
Before handling call setup failures in the coverage area of an RRU, check whether the BTS is
faulty. If an alarm is generated on the BTS, rectify the fault first.
Figure 4-5 describes the possible causes and further analysis of call setup failures in the
coverage area of an RRU
Table 4-5 Possible causes and further analysis of call setup failures in the coverage area of an
RRU
Possible Cause
Cause Analysis
Faults in the
upper-level BTS
Recent
maloperations
Hardware faults
in RRU3606
Cable connection
faults
Incorrect
configuration data
Issue 01 (2014-05-31)
66
Possible Cause
4 Troubleshooting Emergencies
Cause Analysis
command
Issue 01 (2014-05-31)
67
4 Troubleshooting Emergencies
Figure 4-11 Flowchart for troubleshooting call setup failures in the coverage area of an RRU
Issue 01 (2014-05-31)
68
4 Troubleshooting Emergencies
Troubleshooting Procedure
1. Rectify faults in the upper-level BTS.
Check whether call setup failures are caused by faults in the upper-level BTS.
If a faulty RRU is directly connected to the BTS, query the alarms generated in the BTS.
Identify alarms related to the RRU, and rectify the faults according to the alarm handling
suggestions. For details about the troubleshooting of faults in the upper-level BTS, see
section 4.6 "Troubleshooting Call Setup Failures in the Coverage Area of a BTS."
If a faulty RRU is connected to the BTS through another RRU, rectify the faults in both
the BTS and the upper-level RRU.
Issue 01 (2014-05-31)
69
4 Troubleshooting Emergencies
Check whether the optical fiber connection between the upper-level BTS and RRU is
working properly.
Check whether the fiber between the HCPM/HECM and RRU is damaged.
Check whether the optical ports of HCPM/HECM and the RRU are damaged.
Check whether an antenna VSWR alarm is generated. If an alarm exists, check the
antenna system. If no alarm exists, go to 5.
Log in to the Service Maintenance System, and click the Maintenance tab.
Locate the faulty RRU on the navigation tree, and click Device Panel under the RRU.
Select the RRU, and observe RRU devices displayed in the right panel.
If the RRU modules are displayed in green, the modules are functioning properly.
If all the modules of the RRU are displayed in gray, the existing optical fiber
connection is faulty and the modules of the RRU are offline.
Check whether a major alarm related to the RF module, power amplifier module, or
power modules is generated. If such an alarm is generated, handle the alarm as
suggested.
For the more information regarding the replacement of the RRU3606, see the Airbridge
RRU3606 User Guide.
Issue 01 (2014-05-31)
70
Issue 01 (2014-05-31)
71
The MS sends an Origination Meg with the Layer 2 Ack Request on the RACH to
request services.
b.
Upon receiving the Origination Meg, the BS sends a Base Ack Order to the MS.
c.
If a traffic channel is required for the call, the BS sends a Channel Assignment Message
on the paging channel of the air interface to initiate the setup of the radio traffic channel
and sends Null Traffic Data on the traffic channel to the MS to enable the MS to access
the forward channel.
d.
e.
The MS sends the Traffic Channel Preamble on the reverse traffic channel to enable the
BS to access the reverse traffic channel.
f.
After accessing the reverse traffic channel, the BS sends the Base Ack Order with the
Layer 2 Ack Request on the forward traffic channel to the MS.
g.
Upon receiving the Base Ack Order, the MS sends the MS Ack Order and Null Traffic
Data on the reverse traffic channel.
h.
The BS sends the Service Connect Meg to the MS to specify the service configuration
for the call. The MS begins processing services according to the specified service
configuration.
i.
Upon receiving the Service Connect Meg, the MS sends a Service Connect Complete
message to the BS. After the radio traffic channel and terrestrial circuits are established,
the BS sends an Assignment Complete message to the MSC and determines the MS is in
the conversation state.
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Issue 01 (2014-05-31)
72
Troubleshooting Procedure
1. Log in to the Alarm Management System and check whether a BTS Standing Wave Alarm
(ID: 18400) is generated.
If the BTS Standing Wave Alarm is generated, resolve the standing wave problem. Then,
go to 5.
2. Run the DSP RES command to query the status of the current carrier.
If the queried Administrative Status of the carrier is Locked, run the UBL RES
command to unblock the carrier. Then, go to 3.
If the queried Operational Status of the carrier is Disabled, resolve the problem by
enabling the carrier. For more information, see section 16.2 "Troubleshooting the
Unavailability of BTS Carriers."
3. Perform drive tests and determine whether there are areas that signals cannot reach.
If there are areas that signals cannot reach, contact network planning engineers to
optimize the network and improve coverage. Then, go to 5.
4. Check whether the output power of the BTS is normal by referring to related BTS manuals.
If the output power of the BTS is abnormal, restore the output power of the BTS. For
details about how to identify and troubleshoot BTS power failures, see related BTS
manuals.
5. Perform the dialing test on an idle MS, and check whether the signal receive performance of
the MS is normal.
----End
Cause
The protocol version of the RAC is higher than the protocol versions of the MSs.
Analysis
Check the protocol version of the RAC, and protocol versions of the MSs.
Issue 01 (2014-05-31)
73
Troubleshooting Procedure
1. Run the LST PREV command to query the minimum protocol version of the RAC, and the
protocol versions and models of the affected MS. Check whether the protocol versions of the
MSs are higher than the minimum protocol version of the RAC.
If the protocol versions of the MSs are higher than the minimum protocol version of the
RAC:
MSs of a high protocol version only support system messages of a high protocol version.
If the RAC has a low protocol version, MSs of a high protocol version may fail to access
the network because structures of RAC messages may vary with different protocol
versions. For example:
If BandClass is 0: The RAC is at band 800 MHz. The minimum protocol version of
the RAC is 2.
If BandClass is 1: The RAC is at band 1900 MHz. The minimum protocol version of
the RAC is 1.
If BandClass is 5: The RAC is at band 450 MHz. The minimum protocol version of
the RAC is 5.
Go to 2.
If the protocol versions of the MSs are lower than the minimum protocol version of the
RAC:
MSs of a low protocol version only support system messages of a low version. If the RAC has
a high protocol version, MSs of a low protocol version may fail to access the network because
structures of RAC messages may vary with different protocol versions.
Go to 2.
2. Run the MOD PREV command to change the minimum protocol versions supported by the
RAC. Perform dialing tests between the affected MS and MSs of various protocol versions
such as versions 1, 4, and 6. Check whether the dialing tests are normal.
If dialing tests are normal, MSs of various protocol versions can access the network. In
this case, you can determine that the setting of the protocol version is corrected and the
fault has been rectified. No further action is required.
----End
Issue 01 (2014-05-31)
74
The MS sends an Origination Message to the BSS on the access channel over the air
interface, and requires a response from the BSS.
b.
After receiving the Origination Message, the BSS sends a BS Ack Order to the MS.
Issue 01 (2014-05-31)
75
c.
The BSS constructs a CM Service Request message, encapsulates it, and then sends it to
the MSC over the A interface. For CS calls, the BSS can recommend the required
terrestrial link and request the MSC to assign the circuit through this message.
d.
The MSC sends an Assignment Request message to the BSS to request radio resources.
If the MSC can assign the terrestrial link recommended by the BSS in the CM
Service Request message, the MSC assigns the terrestrial link in the Assignment
Request message.
The BSS then uses the terrestrial link assigned by the MSC.
a.
After assigning TCHs for the MS, the BSS sends a Channel Assignment Message or
Extended Channel Assignment Message on the paging channel to instruct the MS to set
up radio TCHs.
b.
The MS sends a TCH Preamble on the reverse TCH specified by the BSS.
c.
After acquiring the reverse TCH, the BSS sends a BS Ack Order on the forward TCH
and requires a response from the MS.
d.
e.
The BSS sends a Service Connect Message or Service Option Response Order to the MS
to specify the service configuration for the call.
f.
After receiving either the Service Connect Message or the Service Option Response
Order, the MS starts to process services according to the specified service configuration
and responds with a Service Connect Completion Message.
g.
After both the TCH and the terrestrial link are successfully established, the BSS sends an
Assignment Complete Message to the MSC, indicating that the two parties can start
conversation.
h.
If the calling process tone is provided within the TCH frame, the MSC sends the
ringback tone to the MS through the TCH.
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Issue 01 (2014-05-31)
Check the configuration and usage of CEs of the access BTS or subsystem.
76
Troubleshooting Procedure
Check the configuration and usage of CEs.
1. If the system uses a BTS-level license, run the DSP CBTSLICENSE command to query the
number of CEs configured for the access BTS and the number of CEs already in use. In
addition, check whether the number of CEs is sufficient.
2. If the system uses a RAC-level license, run the DSP RACLICENSECFG command to query
the number of CEs configured on the RAC and CEs already in use. Then, check whether the
number of CEs is sufficient.
If the number of CEs is insufficient, apply for a new license that authorizes more CEs.
No further action is required.
3. Check whether an alarm related to the CCPM/HCPM board is generated on the Alarm
Management System.
If such an alarm is generated, rectify the CCPM/HCPM board fault according to the
alarm reference.
If configuration is consistent, go to 5.
5. Check whether an alarm related to the Abis interface link of the access BTS is generated on
the Alarm Management System.
If such an alarm is generated, clear the alarm according to the alarm reference.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Issue 01 (2014-05-31)
77
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Configurations of the RAC and MSC are not consistent on the A interface.
Analysis
To locate the fault, perform the following operations:
Check MS authentication.
Troubleshooting Procedure
Check the A interface link.
1. Perform signaling tracing on subscriber interfaces, and check whether the MSC responds with
a message after the RAC sends the CM Service Request to the MSC.
3. Check whether an alarm related to the A interface link is generated on the Alarm
Management System.
Issue 01 (2014-05-31)
If such an alarm is generated, clear the alarm according to the alarm reference.
78
5. Check whether the SCCP subsystem number on the RAC and that on the MSC are consistent
by running the LST SCCPSSN command on the Service Maintenance System.
6. Check whether the A interface version of the RAC and that of the MSC are consistent by
running the LST RACINF command on the Service Maintenance System.
Check MS authentication.
7. Check whether the cause value carried in the Clear Command message is "Authentication
Failure, 0x1A":
If yes, go to 8.
8. Check whether broadcast authentication is enabled for the RAC by running the LST
SYSMSGPARA: CCMINF=AUTH command on the Service Maintenance System.
If broadcast authentication is disabled, run the MOD AUTH command to enable it.
9. Request the maintenance engineers of the MS, R_UIM card, and HLR/AC to check whether
the authentication parameters are consistent. Check the parameters IMSI, ESN, MEID, and
A_Key.
If parameters are not consistent, request the maintenance engineers to modify parameter
settings.
Initiate an SSD update by canceling the account. Then, open an account on the HLR.
Issue 01 (2014-05-31)
79
If an MS with the R_UIM card always fails to pass authentication, interchange the R_UIM
cards of this MS with an MS that has passed the authentication. Determine whether the
problem is caused by the R_UIM cards or the MS.
12. If the fault persists after completing the preceding steps, contact Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Issue 01 (2014-05-31)
80
Troubleshooting Procedure
Check the status, type, and configuration of the A interface link.
1. Check whether an alarm related to the A interface link is generated.
If such an alarm is generated, clear the alarm according to the alarm reference.
3. Query the destination IP address, port IP address, and gateway IP address of the A interface
board by running the LST ETHLNK and LST IPBRDROUTE commands. Check whether
the IP addresses are consistent with the planning.
If the IP addresses are not consistent with the planning, run the RMV ETHLNK, ADD
ETHLNK, and MOD IPBRDROUTE commands to change the IP addresses.
4. Query the configuration data of the A2 interface link on the RAC by running the LST TKC
command. Contact the CN engineers to check whether the configuration data on the CN side
is consistent with that on the RAC.
If the configuration is not consistent, run the MOD TKC command to modify the RAC
configuration.
In E1 working mode, the initial CIC number of the RAC must be consistent with that of the
MSC. In T1 working mode, the MSC initial CIC number is equal to the RAC initial number
plus 1. This is because the RAC initial CIC number is configured as not installed by default,
and the MSC initial CIC number is configured as available by default.
Check the status of TCs/ECs.
5. Check the number of TCs on voice service processing boards
(DPUTb/ECUOa/TCUOc/ECUOc) and check whether the number of TCs is greater than 0.
If the number is less than 0, expand capacity of the voice service processing boards
(DPUTb/ECUOa/TCUOc/ECUOc).
If the status is abnormal, load the DSP again to restore the DSP.
----End
Issue 01 (2014-05-31)
81
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
82
Issue 01 (2014-05-31)
83
When a paged MS is within the servicing area of the MSC, the MSC sends a Paging
Request message to the BSS to start the call setup of the paged MS.
b.
The BSS sends a General Page Message that carries the identity code of the MS on the
paging channel.
c.
Upon receiving the General Page Message, the MS sends a Page Response Message to
the BSS on the access channel.
d.
The BSS uses the information to form a Paging Response Message. After encapsulating
this message, the BSS sends it to the MSC. In the message, the BSS can recommend a
terrestrial circuit and request the MSC to assign the circuit.
e.
After receiving the Page Response Message, the BSS sends a BS Ack Order message to
the MS.
f.
The MSC sends an Assignment Request message to the BSS to request radio resources.
If the MSC can assign the terrestrial link recommended by the BSS in the CM
Service Request message, the MSC assigns the terrestrial link in the Assignment
Request message.
The BSS then uses the terrestrial link assigned by the MSC.
a.
After assigning TCHs for the MS, the BSS sends a Channel Assignment Message or
Extended Channel Assignment Message over the paging channel to start setting up radio
TCHs.
b.
c.
After acquiring the reverse TCH, the BSS sends a BS Ack Order on the forward TCH
and requires an ACK from the MS.
d.
In response, the MS sends an MS Ack Order on the reverse TCH to the BSS.
e.
The BSS sends a Service Connect Message or Service Option Response Order to the MS
to specify the service configurations to be used for the call.
f.
Upon receiving the message, the MS starts processing services according to the specified
configurations and responds with the Service Connect Completion Message.
g.
After the radio TCH and the terrestrial circuit are both successfully connected, the BSS
sends an Assignment Complete Message to the MSC, regarding that the MS is handling
the call.
h.
The BSS sends an Alert with Info message to the MS to instruct the MS to ring.
i.
After receiving the message, the MS sends an MS Ack Order to the BSS and begins
ringing.
j.
When the call is answered, the MS sends a Connect Order message to the BSS, which
carries the Layer 2 verification request.
k.
After receiving the message, the BSS sends a BS Ack Order to the MS on the forward
TCH.
l.
The BSS sends a Connect message to inform the MSC that the MS has answered the call.
At this point, it is determined the MS is handling a call.
Issue 01 (2014-05-31)
84
Cause
Common causes of the fault are as follows:
Configurations of the signaling points, cells, or LACs on the RAC and core network are not
consistent.
Analysis
To locate the fault, perform the following operations:
Check whether the configurations of the signaling points, cells, or LACs on the RAC and
core network are consistent.
Troubleshooting Procedure
1. Run DSP SUBCSR command to query the data of a specified subscriber.
2. Run LST V5BAPORT command to list the information of V5 basic velocity ports.
3. Run DSP VDBUSER command is used to display the data of a specified subscriber recorded
in the VDB.
4. Check V5 interface.
----End
Information Collection.
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
Issue 01 (2014-05-31)
85
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
86
Soft Handoff
Soft handoff (SHO) refers to the process during which the MS sets up a link to the new cell in
the same frequency before disconnecting the link to the source cell. During a soft handoff, the
MS maintains the communication with the source BTS when it is setting up connection with
the target BTS.
Hard Handoff
Hard handoff (HHO) refers to the process during which the MS disconnects from the carrier
of the source BTS and then starts setting up connection with the carrier of the target BTS.
That is, the MS disconnects from the network and then connects to the network. During a
hard handoff, the communication links are disconnected transiently.
Softer handoff
Access handoff
Issue 01 (2014-05-31)
87
Cause
Common causes of the fault are as follows:
Analysis
When MSs fail to perform HHOs, check the network coverage in the edge area first by
observing whether MSs can detect and report pilot strength of the target BTS and whether the
pilot strength of the target BTS exceeds the HHO threshold. Then, check whether the
parameter configuration of the HHO algorithm is proper.
Issue 01 (2014-05-31)
88
Troubleshooting Procedure
1. Check whether the BTS coverage in the edge area is normal, and check whether the
parameters related to signal receiving and BTS engineering (such as downtilt, azimuth, and
height of the antenna) are set properly.
If the BTS coverage is normal and the relevant parameters are set properly, go to 2.
If the BTS coverage is abnormal and the related parameters are set improperly, adjust the
parameter settings to optimize the coverage so that the MSs can report the pilot strength
of the source BTS and target BTS.
If the switch is disabled, enable the switch of an HHO algorithm that is consistent with
the HHO algorithm set in the RAC.
The switch settings of different HHO algorithms are queried by using different commands.
Table 8-1lists the related commands to querying and modifying switch settings of HHO
algorithms.
Table 8-1 Commands used for querying and modifying HHO algorithm switches
HHO Algorithm
Switch
Definition
Query
Command
Modification
command
Default
Value
Intra-frequency HHO
algorithm switch
1: Turn on the
switch
LST
HOINF
MOD PHOALG
LST
RACHO
MOD PHOALG
LST
RACHO
MOD PHOALG
LST
HOINF
MOD PHOALG
LST
HOINF
MOD PHOALG
1: Turn on the
switch
0: Turn off the
switch
MS-assisted HHO
algorithm switch
1: Turn on the
switch
0: Turn off the
switch
Handdown HHO
algorithm switch
1: Turn on the
switch
0: Turn off the
switch
Direct HHO
algorithm switch
1: Turn on the
switch
0: Turn off the
switch
Issue 01 (2014-05-31)
89
For example, to query the switch setting of the intra-frequency HHO algorithm, run the
following command on the Service Maintenance System: LST HOINF: CN=106, SCTID=0,
CRRID=255, QRYINF=PHOALG;.
3. Check whether the HHO threshold is properly set.
If the threshold is set improperly, run the corresponding MML command to change the
threshold.
You can run the LST HOINF MML command to query the threshold of the intra-frequency
HHO algorithm.
For example, run LST HOINF: CN=106, SCTID=0, CRRID=255, QRYINF=HHOSF
Table 8-2 lists the MML commands used to modify HHO threshold value. (For details of
these commands, see MML Command Online Help.)
Table 8-2 MML commands related to HHO threshold
HHO Threshold
Modification Command
Definition
MOD DRCT
MOD HNDDWN
MOD HHOBPLT
MOD HHOSF
MOD HHOMA
4. Conduct dialing tests in the problem area to check whether MSs perform HHOs normally.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
Issue 01 (2014-05-31)
90
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Analysis
A precondition for performing inter-frequency HHOs is that the MS can search a target carrier
in a frequency band. Another precondition is that the neighboring relationship between the
source carrier and target carrier must be configured on the RAC. The RAC determines
whether the HHO is allowed based on the pilot strength of the target carrier or the values of
other parameters that the MS reports. The threshold of the algorithm affects the
inter-frequency HHO decision by the RAC.
Issue 01 (2014-05-31)
91
Troubleshooting Procedure
1. Check whether the MS supports the target frequency band.
Issue 01 (2014-05-31)
92
If the MS does not support the target frequency band, replace the MS with an MS that
supports the target frequency band.
2. Run the LST RACHO command to check whether the inter-frequency HHO algorithm is
enabled.
If the algorithm is disabled, run the MOD RACHO command to enable it.
3. Run the LST NBRCDMACH command to check whether the sector of the source carrier is
configured with correct inter-frequency cell neighboring relationship.
4. Run the LST DRCTTRG command to check whether a carrier operates on a different
frequency band is configured as the direct HHO target carrier of the source carrier.
If a carrier in a different frequency band is configured as the direct HHO target carrier of
the source carrier, go to 5.
If no carrier in a different frequency band is configured as the direct HHO target carrier
of the source carrier, run the ADD DRCTTRG command to configure a carrier in
different frequency band as the direct HHO target carrier of the source carrier.
5. Check whether the parameters of inter-frequency HHO algorithm are properly set.
6. Conduct dialing tests in the problem area to check whether inter-frequency HHOs can be
performed.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
Issue 01 (2014-05-31)
93
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
The neighboring relationship between the source carrier and the target carrier is absent.
Issue 01 (2014-05-31)
94
Is the samefrequency
neighboring relation
configured?
3
No
Add a same-frequency
neighboring relation
between the target sector
and the source sector
Yes
Check the handoff threshold value
Is the handoff
threshold value
proper?
No
Yes
Check the target carrier
Yes
No
Check the gain values of the source
sector and the target sector
No
Yes
9
11
Yes
No
Make a test call
End
Issue 01 (2014-05-31)
95
Troubleshooting Procedure
1. Check the intra-frequency neighboring relationship between the source sector and target
sector.
On the Service Maintenance System, query all intra-frequency neighboring sectors of the
source sector. For example, run the following command:
LST NBRCDMACH: NBRINF=SFNBR;
If the returned results include the target sector, the target sector and source sector are
intra-frequency neighboring sectors, go to 3
If the returned results do not include the target sector, the target sector and source sector
are intra-frequency neighboring sectors, go to 2.
2. Set the target sector as an intra-frequency neighboring sector of the source sector.
On the Service Maintenance System, configure the target sector as the intra-frequency
neighboring sector of the source sector.
For example, run the following command:
ADD NBRCDMACH: CCDMACH="958-2-0-283"; NBRCDMACHS="119-2310-1-283";
SFFLAG=SINGLE; DFFLAG=SINGLE; NBFLAG=SINGLE;
DFFLAG=SINGLE, NBFLAG=SINGLE;
3. Check the threshold value of the soft handoff.
On the Service Maintenance System, check whether the handoff parameters of the sectors are
set properly.
For example: Run LST DOHO: (for EV-DO network)
Run LST HOINF: (for 1X network)
The threshold value is generally set to the default value, or a value suggested by the network
planning personnel or network optimization personnel. If the threshold value is set to the
value suggested by the network planning personnel or network optimization personnel, check
whether the threshold value is the recommended value. If the two values are consistent, the
setting is proper.
If the threshold value is set to the default value, check whether the handoff parameters of the
target sector are consistent with the parameters of other normal sectors. If the handoff
parameters are consistent, the setting is proper.
Issue 01 (2014-05-31)
96
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
97
Cause
Common causes of the fault are as follows:
The A13 interface is faulty.
Issue 01 (2014-05-31)
98
Issue 01 (2014-05-31)
99
Troubleshooting Procedure
1. Check whether the source and target ANs have a neighboring relationship.
Run the LST NBRAN command for both the source and target ANs to determine whether a
neighboring relationship is configured between them.
If a neighboring relationship is not configured between the source and target ANs, go to
2.
2. Configure the neighboring relationship between the source and target ANs.
Run the ADD NBRAN command to add the neighboring relationship between the source and
target ANs. For example:
ADD NBRAN: NBRANIP="129.9.123.102"", NBRA16PROTYPE=PREV0,
EVDOTRANSMODE=MODE3, ANHOSWITCH=OFF, SNDA13PAGINGSWITCH=OFF,
DEALA13PAGINGSWITCH=ON;
3. Run the LST NBRANLNK command to check whether a neighboring AN link is configured
between the source and target ANs.
If the neighboring AN link is configured between the source and target ANs, go to 5.
If the neighboring AN link is not configured between the source and target ANs, go to 4.
4. Run the ADD NBRANLNK command to configure the link between the source AN and the
neighboring target AN.
5. Run the LST DOCS command on both the source and target ANs to check whether color
code and subnet are the same.
Run the MOD DOCS command to modify color code and subnet on the source AN or
target AN.
Run the MOD DOCS command of the neighboring AN to modify color code and subnet
of the neighboring AN.
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Issue 01 (2014-05-31)
100
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect the information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Issue 01 (2014-05-31)
101
Issue 01 (2014-05-31)
102
Start
Yes
Yes
No
No
No
No
No
No
Yes
Yes
8
Check whether an external
carrier is configured for the
target AN
No
No
Yes
Yes
No
No
No
No
Yes
10
11
Yes
Yes
12
Yes
13
15
No
Yes
14
No
Yes
End
Issue 01 (2014-05-31)
103
Troubleshooting Procedure
1. Browse the alarms to check whether there are license-related alarms.
2. Browse the alarms to check whether there are inter-AN link alarms.
If an inter-AN link alarm exists, clear the alarm by referring to section 15.7
"Troubleshooting A13/A16 Link Failure."
3. Run the LST DOHO command on the LMT to check whether the Inter-AN HHO Division
Switch is enabled for both the source and target ANs.
If the switches are not enabled, run the MOD DOHO: INTERANHHODIVSW=ON;
command to enable the switches.
4. Run the LST NBRAN command on the LMT to check whether color codes of the target and
source ANs are properly configured.
If color codes are not properly configured, modify the color code and ensure the target
and source AN are properly configured.
5. Run the LST NBRAN command on the LMT to check whether the A16 Interface Protocol
Revision of Neighbor AN of the target AN is consistent with that of the source AN.
If the A16 Interface Protocol Revision of Neighbor AN is not consistent, modify one of
the A16 Interface Protocol Revision of Neighbor AN of the source AN and the target
AN to keep them consistent.
If the switch is not enabled, enable the switch for the HHO algorithms by referring to the
CBSS Feature Configuration Guide.
7. Run the LST NBRAN command on the LMT to check whether the A16 Interface Protocol
Revision of Neighbor AN of the target and source ANs are Huawei proprietary protocols.
If the A16 Interface Protocol Revision of Neighbor AN of the source and target ANs
are Huawei proprietary protocols, go to 9.
If the A16 Interface Protocol Revision of Neighbor AN of the source and target ANs
are not Huawei proprietary protocols, go to 8.
8. Check whether an external target carrier is configured for the target AN.
If an external carrier is not configured for the target AN, run the ADD
DOOUTPLTHHOTRG command to configure it.
9. Check whether the target carrier set or neighboring carriers for the HHO are properly
configured on the source AN.
Issue 01 (2014-05-31)
104
If the target carrier set or neighboring carriers for the HHO are properly configured on
the source AN, go to 10.
If the target carrier set or neighboring carriers for the HHO are not properly configured
on the source AN, refer to the CBSS Feature Configuration Guide.
10. Run the LST CDMACH command on the LMT to check whether the external carrier
supports HHO.
If the external carrier does not support HHO, run the MOD OUTCDMACH command
to enable the external carrier to support HHOs.
11. Start tracing the inter-AN handoffs of an AT over the Um, Abis, A9, A11, A13, A16, and
A17 interfaces. Check whether the A16 interface session migration is complete.
If the A16 interface session migration is not complete, contact Huawei technical support.
12. Start tracing messages on the target AN to check whether the AT sends the TCA message and
ConnectionClose messages.
If the TCA and ConnectionClose messages are properly delivered on the source AN, go
to 13.
If the TCA and ConnectionClose messages are not properly delivered on the source AN,
contact Huawei technical support.
13. Start tracing messages on the target AN to check whether the AT sends the TCC message.
14. Start tracing messages on the target AN to check whether the A8/A9 and A10/A11
connections are successfully activated.
If the A8/A9 and A10/A11 connections are successfully activated, no further action is
required.
If the A8/A9 and A10/A11 connections are not successfully activated, contact Huawei
technical support.
15. Perform a drive test in the top areas where HHOs fail. Determine whether the network
coverage is faulty, or if HHO parameters are not properly configured.
If the network coverage is faulty or HHO parameters are not properly configured, no
further action is required.
If the network coverage is not faulty and HHO parameters are properly configured,
contact Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault.
Issue 01 (2014-05-31)
105
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Color code and subnet configured for one carrier are the same as those for the
neighboring carrier.
Issue 01 (2014-05-31)
106
Start
Is neighboring
relationship configured?
Is a link
configured?
End
Issue 01 (2014-05-31)
107
Troubleshooting Procedure
1. Check whether the source and target ANs have a neighboring relationship.
Run the LST NBRAN command of both the source and target ANs to check whether a
neighboring relationship is configured between them.
If the command output contains the IP address of the target AN, it indicates that a
neighboring relationship is configured between the source and target ANs. Go to 3.
If the command output does not contain the IP address of the target AN, it indicates that
a neighboring relationship is not configured between the source and target Ans. Go to 2.
2. Configure the neighboring relationship between the source and target ANs.
Run the ADD NBRAN command on the LMT. For example:
ADD NBRAN: NBRANIP="129.9.123.102", NBRA16PROTYPE=PREV0,
EVDOTRANSMODE=MODE3, ANHOSWITCH=OFF, SNDA13PAGINGSWITCH=OFF,
DEALA13PAGINGSWITCH=ON;
3. Check whether a link is configured between the source and target ANs.
Run the LST NBRANLNK command of both the source and target ANs to check whether the
link between the two neighboring ANs is configured.
If the command output contains the IP address of the target AN, it indicates that the link
is configured between neighboring ANs. Go to 5.
If the command output does not contain the IP address of the target AN, go to 4.
4. Configure the link between the source AN and the neighboring target AN.
Run the ADD NBRANLNK command on the Service Maintenance System.
5. Check whether color code and subnet of the carrier on the source AN are the same as those of
the neighboring carrier on the target AN.
Run the LST DOCS command of both the source and target ANs to check whether color code
and subnet of the carrier on the source AN are the same as those of the neighboring carrier on
the target AN.
If color code and subnet of the carrier on the source AN are the same as those of the
neighboring carrier on the target AN, go to 6.
If the color code and subnet of the carrier on the source AN are different from those of
the neighboring carrier on the target AN, go to 7.
Modify color code and subnet of the neighboring AN after color code and subnet of a
carrier is modified.
Run the MOD DOCS command on the Service Maintenance System of the neighboring AN.
7. Check whether the fault is cleared.
Issue 01 (2014-05-31)
108
Start the Um and the A17 interface tracings on the Service Maintenance System. Move an AT
in active state from the coverage area of the source AN to the coverage area of the target AN.
If no session setup message is detected in the air interface tracing, but an inter-AN
handoff message is detected in the A17 interface tracing, it indicates the fault is resolved.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Subscriber interface tracing (A1, Abis, Um, A9, A11, A3, and A7 interfaces)
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
109
Report the MS location and status so that the MS can be paged when it functions as the
called party.
Enable the MS in timeslot mode and provide timeslot period indexes so that the RAC
can know which timeslot the MS is listening to.
Inform the BSS system of MS type and protocol version so that the BSS can know the
MS's capability to support the channel.
Virtual
MSC
BSS
1. Registration Message
2. Location Updating Request
3. Location Updating Accept
4. Registration Accepted Order
1. The MS sends the Registration Message to the BSS to initiate the registration
process. The Registration Message carries the information about cells searched
by the MS.
Issue 01 (2014-05-31)
111
2. After receiving the Registration Message, the BSS generates the Location
Updating Request message based on the information about cells and
authentication and sends the message to the MSC.
3. The MSC authenticates the MS. After the MS survives the authentication, the
MSC records the cell where the MS resides and send the BSS the Location
Updating Accept message.
4. The BSS sends the Registration Accepted Order message to the MS.
5. The registration is complete.
Cause
Common causes of the fault are as follows:
Issue 01 (2014-05-31)
112
Are
parameters of these
messages
correct?
No
Yes
Are registration
parameters
correct?
5
No
Yes
Check the registration
parameters configured on
an MS
Are
registration
parameters on the
MS correct?
No
Yes
End
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Run the LST SYSMSGPARA command to check the System Parameter Message (SPM).
Review the following fields:
Issue 01 (2014-05-31)
113
Local Registration Flag: If this field is set to Automatic registration is required for
local MSs (non-roaming MSs), all local MSs automatically initiate registration. That is,
all MSs sharing the same home SID/NID as the local network initiate registration.
Power-up Registration Flag: This field specifies whether registration is required upon
MS power-up. It must be set to Registered.
Power-down Registration Flag: This field specifies whether registration is required upon
MS power-down. It must be set to Registered.
System Message Parameter Change Registration Flag: This field specifies whether
registration is required after system parameters are changed. It must be set to
Registered.
Registration Zone: The value of this field is usually identical with the LAC.
If the SPM message is not correct, modify the parameters and perform a dialing test. If
the test result is normal, no further action is required. If the test result is abnormal, go to
2.
Modify the cell parameters so that parameters of other cells are different from those of
the local cell. This will trigger registration of the MS. For this operation, go to 4.
Issue 01 (2014-05-31)
114
If the setting of MS registration parameters is not correct, modify the settings. If test
result shows the initiation of localization registration is normal, no further action is
required.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
115
No
Yes
Is the
MS correctly defined?
No
Yes
End
Troubleshooting Procedure
1. Check the RAC data configuration.
Check whether the homing RAC is configured for the current MS. If the homing RAC is not
configured or is incorrectly configured, the MSC rejects the location updating message
reported by the RAC.
Query the mapping between the IMSI and the RAC on the Service Maintenance System by
running the LST IMSIBSC command.
According to the query results, check whether the configured homing RAC is the actual
homing RAC.
Run the STR CRC command to verify that data between the FAM and BAM is consistent.
2. Modify the RAC data configuration.
Issue 01 (2014-05-31)
116
Modify the RAC data configuration to ensure that the mapping between the IMSI and the
RAC is correct.
For example, to modify the configuration of the RAC whose IP address is 192.168.0.1 and
whose mapping IMSI is prefixed with 4600309, run the following command:
MOD IMSIBSC: IMSIMASK="4600309", BSCIP="192.168.0.1";
3. Check whether the MS is correctly defined in the HDB.
If the MS is not correctly defined in the HDB, the MSC rejects the location updating message
reported by the RAC.
For example, to check whether an MS whose IMSI is 460030912120001 is correctly defined,
run the following command on the Service Maintenance System:
DSP SUBSCR: SUBSCRINFO=IMSI, IMSI="460030912127777",
NEEDSECRETDATA=NO;
Check whether the ESN is correct.
4. Modify the subscriber subscription information.
If the ESN or A-KEY is incorrect, run the MOD IMSIAKEYESN command to correct it.
If the MS has been defined, run the RMV SUBSCR command to delete the subscriber. Then,
run the MOD IMSIAKEYESN command to modify the subscriber subscription information.
If the MS-initiated registration failure is caused by other incorrect information, run the MOD
SUBSCR command.
5. Verify that the MS can be registered when being powered on or powered off.
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Issue 01 (2014-05-31)
117
Troubleshooting Procedure
1. Check whether the area where the hybrid AT is located is covered by the EV-DO network by
performing an EV-DO dialing test.
If the hybrid AT is not covered by the EV-DO network, 1X/EV-DO interoperation is not
available.
2. Check whether network parameters set on the hybrid AT are correct. For specific
configurations, contact the supplier of the hybrid AT.
If parameters are incorrect, request the supplier of the hybrid AT to modify the setting.
Then, perform a test. If the test results are normal, no further action is required. If the test
results are abnormal, contact Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
118
10
Troubleshooting Authentication
Failures
Shared secret data (SSD) update is performed to update the SSD parameter stored in the
MS to ensure the consistency of parameters between the MS and the network.
SSD Update
SSD is a 128-bit data pattern stored on the MS, readily available to the network. The first 64
bits of the SSD are defined as SSD-A that is used to support authentication procedures. The
second 64 bits of the SSD is defined as SSD-B that is used to support voice authentication and
signaling message authentication. The SSD is derived from the A-key and a random challenge
(RANDSSD) through a certain algorithm. The SSD is never broadcast between the MS and
the network across the air interface. The RAC updates the SSD by updating the RANDSSD.
SSD update is initiated in the case of an authentication request failure, or by the AC. Usually,
the entity controlling the authentication in the network initiates the Unique Challenge
procedure after an SSD update procedure is completed.
Figure 10-1 shows a successful case of the SSD update procedure.
Issue 01 (2014-05-31)
119
Note: The MSE in the preceding figure indicates a logical module that implements the MSC
functions in RAC6690. It is also called a virtual MSC.
The SSD update procedure is described as follows:
a.
The MSC sends an SSD Update Request message to the BS to indicate that the SSD on
the MS needs updating. The update information is in the form of a random number
(RANDSSD) that can be used by the MS to calculate the new SSD.
b.
Based on the SSD Update Request message from the MSC, the BS sends the SSD
Update message to the MS, indicating the MS should update its SSD.
c.
Upon receiving the SSD Update message from the BS, the MS uses the RANDSSD as
input to the algorithm to generate the new SSD. The MS then selects a 32-bit random
number (RANDBS) and sends it to the BS in a Base Station Challenge Order message.
d.
The BS forwards the Base Station Challenge message to the MSC to verify whether the
new SSD calculated by the MS is the same as that in the network.
e.
Upon receiving the Base Station Challenge message, the MSC uses the new SSD as
input to the algorithm to generate the authentication response signature (AUTHBS). The
MSC then sends the AUTHBS to the BS in the Base Station Challenge Response
message.
f.
Upon receiving the message, the BS transmits the information in a Base Station
Challenge Confirmation Order message to the MS.
g.
If AUTHBS from the MSC is valid, the MS returns an SSD Update Confirmation Order
message to the BS. If AUTHBS from the MSC is invalid, the MS returns an SSD Update
Rejection Order message to the BS.
h.
The BS forwards the information in the SSD Update Response message to the MSC.
Issue 01 (2014-05-31)
120
Terminal Authentication
Terminal authentication verifies the authenticity of an MS, and denies service to unauthorized
MS. The authentication involves a common network algorithm and a parameter unique to
each MS, known only by the MS and the network, called the A-Key. A second level of
security, SSD, is derived from the A-Key and a random challenge (RANDSSD). The A-Key
and the SSD are never broadcast across the air interface. Instead, a publicly available random
number (RAND) is sent to the MS. The RAND and SSD are used as input to the
authentication algorithm for both the MS and the network. The authentication result, referred
to as AUTHR, is calculated by the MS and returned to the network. It is compared to the
AUTHR calculated by the network. If the results match, authentication is successful.
Two forms of authentication are available for CDMA MSs:
Global Challenge Authentication: The RAND value is broadcast on the paging channel
and is available to all MSs accessing the cell. The MS calculates AUTHR using this
RAND, and provides it in its initial access message, which may be a location registration,
origination, or page response.
b.
c.
The MS calculates the result AUTHU based on the specified RANDU and SSD of the
MS. It then returns an Authentication Challenge Response Message to the BS, with the
enclosed AUTHU.
Issue 01 (2014-05-31)
121
d.
The BS forwards the AUTHU information to the MSC using the Authentication
Response message.
Issue 01 (2014-05-31)
122
Issue 01 (2014-05-31)
123
Issue 01 (2014-05-31)
124
Cause
Common causes of the fault are as follows:
a.
The A-Key value on the MS is not consistent with that on the HLR of the core network.
b.
If the global challenge authentication of all MSs fails, it indicates the authentication
switch on the RAC is disabled.
Analysis
Troubleshooting Procedure
Query the Authentication Parameters Configured on the RAC
1. Query the authentication switch on the RAC. On the Service Maintenance System, run the
following command:
LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=AUTH;
The command output is as follows:
%%LST SYSMSGPARA: CN=20, SCTID=0, CRRID=0, CCMINF=AUTH;%%
RETCODE = 0 Execution succeeded
Authentication Information
-------------------------Cell ID
Sector ID
Carrier ID
Authentication Indicator
value
20
0
0
Authenticate
(Number of results = 1)
--END
Random authentication
100
In the output, Authentication Indicator indicates the status of the authentication switch on
the RAC.
Issue 01 (2014-05-31)
125
2. Enable the authentication switch on the RAC. On the Service Maintenance System, run the
following command:
MOD AUTH: CN=20, SCTID=0, CRRID=0, AUTH=YES, RAND=100;
Set AUTH to YES to enable the authentication switch on the RAC.
If the MS passes the authentication after the data is modified, no further action is
required.
If the A-Key value on the MS is not consistent with that on the HLR, go to 4.
4. Modify the A-Key value on the MS or the HLR. Contact MS or HLR maintenance engineers
to modify the values so that they are consistent.
If the MS passes the authentication after the A-Key values are modified, no further
action is required.
If the authentication fails again after the A-Key values are modified, go to 5.
If the MS passes the authentication after the R_UIM card is replaced, no further action is
required.
If the authentication fails again, collect relevant information according to the following
"Information Collection" and contact Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Issue 01 (2014-05-31)
126
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
127
Is the A-key
stored in the LE
correct?
No
Yes
Is the A-key
stored in the MS
modified?
Yes
No
4
Does the MS
support this
function?
No
Yes
6
End
Troubleshooting Procedure
1. Check the A-KEY on the RAC.
To query the A-KEY on the RAC, run the following command on the Service
Maintenance System:
Issue 01 (2014-05-31)
128
Example 1:List the IMSI-AKEY-ESN relationship of the subscriber with the IMSI of
460030910010001:
LST IMSIAKEYESN: INFO=IMSI, IMSI="460030910010001";
Execution result:
+++
HW-AirBridge
2007-07-19 20:44:36
O&M
#74496
%%LST IMSIAKEYESN: INFO=IMSI, IMSI="460030910010001";%%
RETCODE = 0 Execution succeeded
IMSI
A_KEY Value
460030910010001
0000000000000000
--
ESN/MEID
-
END
To query the MS A-KEY, enter the super user password on the MS.
2. Modify the A-KEY on the RAC by performing the following operations:
a.
Run the DSP SUBSCR command to query the subscription information of the
subscriber.
b.
c.
d.
e.
Issue 01 (2014-05-31)
129
Troubleshooting
Figure 10-8 shows the troubleshooting procedure.
Figure 10-8 Troubleshooting procedure
Start
1
Is the A-key
stored in the RAC
correct?
No
Yes
Is the A-key
stored in the MS
correct?
No
Yes
4
End
Procedure
1. Query the A-KEYs stored in the RAC and MS.
For details, see Unique Challenge Failures of an MS (over the V5 Interface).
2. Modify the A-KEY stored in the RAC.
For details, see Unique Challenge Failures of an MS (over the V5 Interface).
3. Modify the A-KEY stored in the MS.
On the MS, enter the super password of the MS to check and modify the A-KEY. The A-KEY
stored in the MS should be consistent with that stored in the RAC.
4. Make a test call.
Issue 01 (2014-05-31)
130
Initiate an SSD update from the RAC. If the SSD update is successful, you can infer that the
fault is rectified.
If an SSD update fail in the case that the A-KEYs stored in the RAC and the MS are
consistent, you can infer that the MS does not supports the SSD update.
Troubleshooting
In the case of the V5 interface, the MS authentication failure usually results from the incorrect
settings of the authentication flag. Figure 10-9 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
131
Does the MS
subscribes to the
function?
No
2
Subscribes to the
authentication function
Yes
Check the settings of the
authentication flag on the RAC
Is the
authentication flag
enabled?
No
4
Enable the authentication flag
at the RAC
Yes
Is the
authentication flag
enabled?
No
6
Enable the authentication flag
at the MSC
Yes
Is the
authentication flag
enabled?
No
8
Enable the authentication flag
at the HDB
Yes
End
Procedure
1. Check whether the MS subscribes to the authentication function.
On the Service Maintenance System, run DSP SURACR to check whether the MS subscribes
to the authentication function. For example,
Issue 01 (2014-05-31)
132
Issue 01 (2014-05-31)
133
To check whether the previous modifications take effect, you can run STR CRC to check the
data on the RAC and the BAM.
Cause
Common causes of the fault are as follows:
The AT is unauthorized.
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
Check Whether the Configuration Between the AN and the AN-AAA Is Correct
1. Run the LST PCFAAA command to query the binding relationship between the PCF and the
ANAAA.
2. Check whether there is the binding relationship between the PCF and the ANAAA in the
output information.
3. Run the LST ANAAA command to check whether the configuration information of the
AN-AAA server is correct. On the Service Maintenance System, run the following command:
LST ANAAA:;
The command output is as follows:
%%LST ANAAA:;%%
RETCODE = 0 Execution succeeded
Issue 01 (2014-05-31)
134
Domain Name
huawei.com
123456789
In the output, check whether the configuration information of the AN-AAA server, such as IP
address, domain name, and key, is correct.
5. Check whether the ALM-2291 A12 Interface Authentication Path Fault alarm is available on
PCFs that are configured with the connecting relationship with the AN-AAA.
If the alarm is available, rectify the fault by referring to the ALM-2291 A12 Interface
Authentication Path Fault alarm.
If the authentication mode is not CHAP, change the mode to CHAP and perform the test
again. For details, see manuals related to the AT.
Issue 01 (2014-05-31)
135
0xc223
0xc023
If A12 Access Reject message is included, have the ANAAA engineers check whether
the subscriber is properly defined.
8. Check whether the A12 Access Reject message is included in the traced messages.
If A12 Access Reject message is not included, collect relevant information according to
the following "Information Collection" and contact Huawei technical support.
----End
Issue 01 (2014-05-31)
136
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
137
11
Active: An air traffic channel is available between the MS and the BTS. The MS and the
BTS can transmit data. Connections of the air interface, A8 interface, and A10 interface
are retained.
Dormant: No air traffic channel is available between the MS and the BTS. The PPP link
connection, however, exists between the MS and the PDSN. Connections of the air
interface and the A8 interface are released. The A10 connection is retained.
Null: No traffic channel or PPP link exists between the MS and the BTS. Connections of
the air interface, A8 interface, and A10 interface are released.
Description
During the data service process, the MS can switch from one state to another.
Issue 01 (2014-05-31)
139
The MS sends an Origination Message on the access channel of the air interface to the
BSS.
b.
Upon receiving the message, the BSS sends a BS Ack Order to the MS.
c.
d.
The MSC sends an Assignment Request to the BSS, requesting allocation of radio
resources.
e.
The BSS sends an A9-Setup-A8 message to the PCF, requesting the setup of an A8
connection.
f.
The PCF sends an A11-Registration-Request message to the PDSN, requesting the setup
of an A10 connection.
g.
The PDSN accepts the request and sends an A11-Registration-Reply message to the
PCF.
h.
The PCF sends an A9-Connect-A8 message to the BSS. The A8 and A10 connections
are set up.
i.
The BSS sends an Extended Channel Assignment Message (ECAM) on the paging
channel of the air interface.
Issue 01 (2014-05-31)
140
j.
The MS sends the Traffic Channel Preamble (TCH Preamble) on the specified reverse
traffic channel.
k.
After detecting the reverse traffic channel, the BSS sends a BS Ack Order on the forward
traffic channel to the MS.
l.
In response, the MS sends an MS Ack Order on the reverse traffic channel and transmits
null traffic frames on the reverse traffic channel.
m.
The BSS sends a Service Connect Message or a Service Option Response Order to the
MS to specify the service configuration for the call.
n.
After receiving the message, the MS starts to process services according to the specified
service configuration and responds with the Service Connect Completion Message.
o.
After the radio traffic channel and the terrestrial link are set up and interconnected, the
BSS sends an Assignment Complete Message to the MSC.
p.
The MS negotiates with the PDSN to set up a PPP connection. For Mobile IP access
mode, the Mobile IP connection must be set up. The PPP messages and Mobile IP
messages are transmitted on the traffic channel.
q.
After the PPP connection is set up, the data service enters the connection state.
The MS sends a Release Order message on the dedicated control channel of the air
interface to the BSS.
b.
c.
When releasing network resources, the MSC sends a Clear Command message to the
BSS.
d.
Issue 01 (2014-05-31)
141
e.
The BSS sends an A9-Release-A8 message to the PCF, requesting the release of the A8
connection.
f.
g.
The PDSN sends an A11-Registration-Reply message to the PCF. The A10 connection is
released.
h.
The BSS sends an A9-Release-A8 Complete message to the PCF. The A8 connection is
released.
i.
Troubleshooting
Figure 11-3 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
142
Is
the call originated
through an MS?
No
Is
the call originated
through a wireless
modem?
No
Yes
Yes
Yes
Are
the settings correct?
No
No
Correct the
configuration of the
wireless modem
Yes
Is
the configuration
correct?
End
Procedure
1. Check the dial-up settings of the MS.
Use an MS to dial up and check whether the screen on the MS displays the information on the data
service.
If the MS does not display the information of the data service, check the dial-up settings of the MS.
Ensure that the port rate of the MS is consistent with that of the computer, that the port ID is correct, and
that the settings of dial-up parameters are correct.
2. Check the configuration of the wireless modem.
Use a wireless modem to dial up and observe the indicator on the wireless modem. If the indicator blinks
twice per second, you can infer that the wireless modem functions properly. If the indicator blinks fast,
you can infer that the wireless modem is faulty.
In addition, check whether the port and associated parameters are correct.
3. Make a test call.
Make a data service call to check whether the fault is rectified.
Issue 01 (2014-05-31)
143
----End
Cause
Common causes of the fault are as follows:
The physical connection between the A10/A11 interface board and the PDSN is faulty.
The route from the A10/A11 interface board to the PDSN is not configured properly.
Analysis
To locate the fault, perform the following operations:
Check the physical connection between the A10/A11 interface board and the PDSN.
Check the route from the A10/A11 interface board to the PDSN.
Troubleshooting Procedure
1. Run the LST ETHLNK command to check whether the physical connection between the
A10/A11 interface board and the PDSN is normal.
2. Run the LST IPBRDROUTE command to check whether the route from the A10/A11
interface board to the PDSN is configured.
If the route is not configured, run the ADD IPBRDROUTE command to add a route
from the A10/A11 interface board to the PDSN.
If the data configuration is not correct, ask PDSN engineers to correct the errors on the
PDSN.
Issue 01 (2014-05-31)
144
----End
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Check the cause value and code field of the A11-Registration-Reply message to see whether
the failure is caused by not consistent configuration between the PCF and the PDSN.
The cause value 0x00 indicates the A11 access succeeded. Other cause values indicate that the
A11 access failed.
The failure is caused normally by not consistent configuration between the PCF and the
PDSN.
Issue 01 (2014-05-31)
145
2. Track PPP messages on the PDSN server, and check whether PPP negotiation is successful.
As this operation involves coordination with the PDSN, contact PDSN engineers for
assistance.
If the parameter configuration is not correct, check whether user name and password on
the terminal is consistent with that set on the AAA server. If they are not consistent,
obtain the user name and password from AAA server engineers and correct the user
name and password on the terminal. As this step involves operations on the AAA server,
contact AAA server engineers for assistance.
----End
Cause
Common causes of the fault are as follows:
The radio environment is poor.
Analysis
To locate the fault, perform the following operations:
Check the matching relationship between protocol versions of the PCF and the PDSN.
Troubleshooting Procedure
1. Check whether the radio environment is good.
If data calls are successful, the A11 interface link is functional and handoff failure may be
caused by poor radio environment. You can test the quality of the radio environment by
placing voices calls.
If the radio environment is poor, see the method of solving the voice call handoff problem to
locate and resolve the problem.
----End
Issue 01 (2014-05-31)
146
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
On the Service Maintenance System, initiate signaling tracing, traffic tracing of a single user,
and QXDM tracing over the air interface.
1. During QXDM tracing, check whether the frame error rate (FER) over the air interface is high.
The FER of 1X data services should be lower than 5%.
2. Check whether alarms related to error bits are generated during transmission over the Abis
interface.
If the alarms are generated, clear the error bits generated during the transmission over the
Abis interface.
If the alarms are generated, clear the clock-related alarms on the BTS.
4. During QXDM tracing, check whether the Ec/Io value is within normal range. Generally, the
Ec/Io value should be greater than 6.5 dB.
Issue 01 (2014-05-31)
147
If the Ec/Io value is not within normal range, contact network optimization personnel to
optimization the network.
5. Analyze the signaling on the Service Maintenance System of the RAC. Review the cause
value, carried in the Abis-Burst Response message sent by the BTS during SCH application,
to check whether the resource application from the RAC was approved.
If the radio resources on the BTS are sufficient, the resource application from the RAC is
approved. That is, the cause value is 0x0. If the resources on the BTS are not sufficient, the
cause value is 0x4. For example, CE resources are not sufficient. The cause value can be used
to determine why the BTS rejects the SCH application from the RAC.
If resources on the BTS are not sufficient, contact BTS engineers for assistance.
6. After traffic tracing of the single user, check whether the disorder of generic routing
encapsulation (GRE) and packet loss of the GRE are included in the reports pertaining to
FG1X and GOUX on the PCF. If these are included in the reports, it indicates packet loss
occurred during transmission from the PCF to the PDSN.
If the disorder and the packet loss of the GRE are included in the reports, check the
transmission from the PCF to the PDSN. The problem may be caused by an incorrect
port mode of a transmission device such as a switch or router, or incorrect MTU
configuration of the port or equivalent route generated on the transmission network.
If the disorder and the packet loss of the GRE are not included in the reports, contact
Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Issue 01 (2014-05-31)
148
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
149
12
AT
Air
Interface
Source AN
A9
PCF
Core Network
A10
A11
PDSN/FA
IPSec
HA
Radius
A12
A18
ANAAA
AAA
IPSec
A13/A16/A17
Target AN
The radio access network consists of the Access Network (AN) and function modules
including the Packet Control Function (PCF) and Access Network-Authentication,
Accounting, Authorization Server (AN-AAA). The AN is responsible for sending and
receiving messages from the BTS, and controlling the BTS. The PCF is responsible for setting
up the connection between the A8 and A10 interfaces, and choosing the Packet Data Service
Node (PDSN). The AN-AAA is responsible for access authentication to complete the
algorithms and related parameters.
The core network consists of the PDSN and function modules such as AAA. The PDSN is
responsible for the setup, management, and release of the packet data session. The AAA is
responsible for the registration, authentication, and charging related to users.
In the case of mobile IP, the core network also includes the Foreign Agent (FA) and the Home
Agent (HA). As the foreign agent of the mobile IP technology, the FA is responsible for
registering, charging, and forwarding subscriber data. The FA and the PDSN share the same
Issue 01 (2014-05-31)
151
physical module. As the starting point of the IPSec tunnel, the HA is used to assign IP
addresses, select routes, and encrypt data when subscribers are roaming.
The interfaces of the EV-DO system are as follows:
A8/A9: internal interfaces between the AN and the PCF. The A8 interface is used to
carry service data, and the A9 interface is used to carry signaling.
A10/A11: interfaces between the PCF and the PDSN, also called R-P interface. The A10
interface is used to carry data, and the A11 interface is used to carry signaling.
A12: an interface between the AN and the AN-AAA. It is used to carry information
regarding access authentication of subscribers.
A13: an interface used to carry call transfer signaling when high-speed data services
between ANs are in the dormant state.
A16: an interface used to carry call transfer signaling when high-speed data services
between ANs are in the active state and hard handoff is performed.
A17: an interface used to carry soft handoff signaling when high-speed data services
between ANs are in the active state.
A18: an interface used to carry transmission of soft handoff data when high-speed data
services between ANs are in the active state.
Cause
Common causes of the fault are as follows:
Analysis
Trace the message on the subscriber interface of the EV-DO AT whose UATI assignment has
failed, and analyze the tracing code stream to determine the abnormal point of information
exchange between the AT and the AN. Generally, the information exchange failure is caused
by the poor radio environment on the air interface.
If transmission of HardwareID between the AT and the AN has failed, see 1 through 7.
If transmission of UATI between the AT and the AN has failed, see 8 through 13.
Troubleshooting Procedure
On the Service Maintenance System, initiate message tracing on the subscriber interface and
QXDM tracing on the EV-DO AT.
Issue 01 (2014-05-31)
152
1. Check whether the UATI Request message is included in messages traced on the subscriber
interface. For more information regarding tracing, see the section "Tracing Messages over the
BSS Interface" in the CBSS LMT User Guide.
If the message is not included, check whether the AT finds the network and whether the
configuration of the AT is correct.
2. Check whether the HardwareID Request message is included in messages traced on the
subscriber interface.
3. Check whether the HardwareID Response message is included in messages traced on the
subscriber interface.
4. Check whether the HardwareID Request message is included in messages traced by the
QXDM.
5. The AN sends the HardwareID Request message, but the AT fails to receive the message. The
message may be lost during transmission over the air interface. You are advised to perform
the test at a new place where the radio environment on the air interface is good, and check
whether the symptoms are the same as those described in 4.
6. Check whether the HardwareID Response message is included in messages traced by the
QXDM.
If the message is not included, the AT has failed to respond with the HardwareID
Response message after receiving the HardwareID Request message. This indicates that
the configuration or message processing of the AT is faulty. Contact the AT manufacturer
to examine the problem, or replace the faulty AT with a new one to perform the test
again.
7. The AT sends the HardwareID Response message, but the AN fails to receive the message.
The message may be lost during the transmission over the air interface. You are advised to
perform the test at a new place where the radio environment on the air interface is good, and
check whether the symptoms are the same as those described in 6.
If symptoms are different, refer to the related instructions to re-locate the fault.
8. Check whether the UATI Assignment message is included in messages traced on the
subscriber interface.
Issue 01 (2014-05-31)
153
9. Check whether the UATI Complete message is included in messages traced on the subscriber
interface.
If the UATI Complete message is included, the UATI assignment has succeeded. No
further action is required.
10. Check whether the UATI Assignment message is included in messages traced by the QXDM.
11. The AN sends the UATI Assignment message, but the AT fails to receive the message. The
message may be lost during the transmission over the air interface. You are advised to
perform the test at a new place where the radio environment on the air interface is good, and
check whether the symptoms are the same as those described in 10.
If symptoms are different, refer to the related instructions to re-locate the fault.
12. Check whether the UATI Complete message is included in messages traced by the QXDM.
If the message is not included, the AT fails to respond with the UATI Complete message
after receiving the UATI Request message. This indicates that the configuration or
message processing of the AT is faulty. Contact the AT manufacturer to examine the
problem, or replace the faulty AT with a new one.
13. The AT sends the UATI Complete message, but the AN fails to receive the message. The
message may be lost during the transmission over the air interface. You are advised to
perform the test at a new place where the radio environment on the air interface is good, and
check whether the symptoms are the same as those described in 13.
If symptoms are different, refer to the related instructions to re-locate the fault.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Issue 01 (2014-05-31)
154
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Trace the message on the subscriber interface of the EV-DO AT that has failed to access the
network, and analyze the tracing code stream. Common causes of the fault are as follows:
The negotiation of protocol types and configuration parameters between the AT and the
AN has failed.
The configuration negotiation messages are lost due to the poor radio environment on the
air interface.
Analysis
The configuration negotiation message includes request and response messages, which are
presented in pairs. After sending the negotiation request message, the AT or AN must receive
the negotiation response message within two seconds. Otherwise, the configuration
negotiation fails. The configuration negotiation ends with the Configuration Complete
message. To locate the fault, perform the following operations:
Check whether the negotiation request message and the negotiation response message
are presented in pairs. For details, see 1 to 2
Determine why the configuration negotiation messages are not presented in pairs. For
details, see 3 to 4.
Check the reason contained in the Session Close message after configuration negotiation
fails. For details, see 5.
Troubleshooting Procedure
On the Service Maintenance System, initiate message tracing on the subscriber interface and
QXDM tracing on the EV-DO AT.
1. Check whether the negotiation request message and the negotiation response message are
presented in pairs in messages traced on the subscriber interface.
2. Check whether the negotiation request message and the negotiation response message are
included in messages traced by the QXDM, but excluded in messages traced on the subscriber
interface.
Issue 01 (2014-05-31)
155
If the negotiation request message and the negotiation response message are included in
messages traced by the QXDM, but excluded in messages traced on the subscriber
interface, go to 3.
If the negotiation request message and the negotiation response message are excluded in
messages traced by the QXDM, and excluded in messages traced on the subscriber
interface, go to 4.
3. The negotiation request message and the negotiation response message are lost during the
transmission over the air interface. You are advised to perform the test again at a new place
where the radio environment on the air interface is good, and check whether the symptoms are
the same as those described in 2.
If symptoms are different, refer to the related instructions to re-locate the fault.
4. Check whether the negotiation response message is excluded in messages traced by the
QXDM and messages traced on the subscriber interface.
If the negotiation response message is excluded, perform the following operations. First,
if the AT fails to send the negotiation response message after receiving the negotiation
request message, replace the faulty AT with a new one and perform the test again, or
contact the AT manufacturer to examine the problem. If the AN fails to send the
negotiation response message after receiving the negotiation request message, contact
Huawei technical support.
5. View the cause contained in the Session Close message in messages traced on the subscriber
interface, and rectify the fault based on the cause. Then, check whether the fault is rectified.
----End
Table 12-1 lists the cause values contained in the Session Close message as specified by the
protocol.
Table 12-1 Encoding of CloseReason field
Field Value
Meaning
MoreInfoLen
MoreInfo
0x00
Normal Close
N/A
0x01
Close Reply
N/A
0x02
Protocol Error
N/A
0x03
Followed by "Type" in
Subtype
0x04
variable
0 or multiple "Type" in
Subtype, which is
followed by incorrect
attributes
0x05
N/A
Issue 01 (2014-05-31)
156
Field Value
Meaning
MoreInfoLen
MoreInfo
0x06
Session Lost
N/A
0x07
Session Unreachable
N/A
0x08
N/A
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Issue 01 (2014-05-31)
157
Analysis
According to signaling tracing process on the Service Maintenance System, identify call
failure points and analyze causes for the failures.
Troubleshooting Procedure
1. Check whether the radio environment is poor. Contact network optimization personnel to
check that the radio environment meets the following requirements. The Ec/Io value must
be over 10 dB. The RSSI value must be in the range of 116.0 dBm to 93.0 dBm.
If normal, go to 2.
If the system uses a BTS-level license, run the DSP CBTSLICENSE command to query
the number of EV-DO CEs configured for the access BTS and the number of EV-DO
CEs already in use. In addition, check whether the number of EV-DO CEs is sufficient.
If the number of EV-DO CEs is not sufficient, add EV-DO CEs to the BTS.
b.
If the system uses a BSC-level license, run the DSP BSCLICENSECFG command to
query the number of EV-DO CEs configured on the BSC and EV-DO CEs already in use.
Then, check whether the number of EV-DO CEs is sufficient.
If the number of EV-DO CEs is insufficient, apply for a new license that authorizes
more EV-DO CEs. No further action is required.
3. Check whether the BSC and BTS configurations are consistent by running the CHK
CBTSIFCFG command:
If configuration is consistent, go to 4.
4. Check whether an alarm related to the CECM board is generated on the Alarm Management
System.
If such an alarm is generated, clear the alarm according to the alarm reference.
5. Check whether an alarm related to the Abis interface link of the access BTS is generated on
the Alarm Management System.
If such an alarm is generated, clear the alarm according to the alarm reference.
6. Check whether an alarm related to the A10A11 interface link is generated on the Alarm
Management System.
If such an alarm is generated, clear the alarm according to the alarm reference.
----End
Issue 01 (2014-05-31)
158
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information
Cause
Common causes of the fault are as follows:
Analysis
The constant but low forward rate is generally caused by constrained bandwidth in the traffic
channel. Therefore, review the following items in sequence.
Check the upper-layer modules, such as the SDU, PCF, A10 link, and PDSN.
The BSS performs the following operations to provide overall reference for EV-DO rate
analysis:
Trace flows of single EV-DO subscribers.
Records the information about the EC board, Abis interface board, APUDc board, DPUDb
board, and PCF board.
Issue 01 (2014-05-31)
159
Trace QXDM.
Capture packets on SDU boards and network side.
Troubleshooting Procedure
1. Observe the downlink DRC value on the air interface from the report of the EC board,
generated by the traffic tracing of the single user, to check whether the radio environment on
the air interface is poor. The poor radio environment on the air interface affects the rate.
If the radio environment on the air interface is poor, contact network optimization
personnel to optimize the network.
2. To ensure the download rate of EV-DO services, a single EV-DO Rev. A carrier sector should
be configured with two E1 cables, and configured with the bandwidth of 3.6 MHz in FE mode.
You are advised to analyze the bandwidth configuration of the Abis link and related alarms to
check whether the not sufficient bandwidth of the Abis link is caused by configuration or link
fault.
If the not sufficient bandwidth is caused by configuration or link fault, reconfigure the
bandwidth of the Abis link or rectify the fault.
If the not sufficient bandwidth is not caused by the configuration or link fault, go to 3.
3. Generally, the FE networking or the GE networking is used between the PCF and the PDSN
and the link bandwidth is sufficient. In some cases, the E1 transmission network may be used
between the PCF and the PDSN, or the FE networking or the GE networking is used between
the PCF and the PDSN but the bandwidth is constrained. In either case, the transmission
bandwidth between the PCF and the PDSN is not sufficient. In such situations, a computer
can be connected to the mirror port of the switch at the exit of the PCF. The IP address of the
computer should be configured on the same network segment as that of the PCF. Then, the
computer can perform the download test to check whether the download rate cannot reach 10
Mbit/s.
If the download rate cannot reach 10 Mbit/s, expand the bandwidth of transmission links
between the PCF and the PDSN.
4. Check whether TCP MTU (Max Transfer Unit) and TcpWindowSize are set correctly. You
are advised to set TCP MTU (Max Transfer Unit) to 1460 bytes, and TcpWindowSize to
65535 bytes.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
Issue 01 (2014-05-31)
160
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Analysis
The forward rate fluctuation is generally caused by the packet loss in the traffic channel. In
the case of TCP services, both the forward packet loss and the reverse packet loss may lead to
the rate fluctuation. Therefore, review the following items in sequence.
Check upper-layer modules, such as the SDU, PCF, A10 link, and PDSN.
The BSS performs the following operations to provide overall reference for EV-DO rate
analysis:
Records the information about the EC board, Abis interface board, APUDc board,
DPUDb board, and PCF board.
Trace QXDM.
Issue 01 (2014-05-31)
161
Troubleshooting Procedure
1. Observe the downlink DRC value on the air interface from the report of the EC board,
generated by the traffic tracing of the single user, to check whether the radio environment on
the air interface is fluctuated. The fluctuation of the radio environment on the air interface
leads to the rate fluctuation.
If the radio environment on the air interface fluctuates, contact network optimization
personnel to optimize the network.
2. In the report of the EC board generated by traffic tracing of the single user, observe the
sending of downlink forward data to check whether the branches frequently change. The
frequent change in the main branch affects the forward rate.
3. Check whether the uplink or downlink packet loss is present in the RAC interface board
report generated after the single user tracing.
4. In the report of the EC board generated by traffic tracing of the single user, check whether
there are a large number of downlink RLP packet loss and downlink Abis packet error. The
RLP packet loss is caused by the Abis packet loss, or Abis packet disorder. In normal cases,
the RLP packet loss rate is lower than 1%, and the number of Abis packet errors is low or
even none. A large proportion of Abis packet error indicates that Abis link is faulty.
If there are a large number of downlink RLP packet loss and downlink Abis packet errors,
check the Abis transmission link.
If there are not a large number of downlink RLP packet loss and downlink Abis packet
errors, go to 5.
5. In the branch report of the APUDc or DPUDb generated by traffic tracing of the single user,
check whether the forward delay or reverse delay is long. The long delay affects the forward
rate.
6. In the call report of the APUDc or DPUDb generated by traffic tracing of the single user,
check whether any bytes are lost over the A8 interface.
7. Check whether the disorder and the packet loss of the GRE are included in the reports of the
FG1X and the GOUX on the PCF generated by traffic tracing of the single user. If the
disorder and packet loss of the GRE are included in the reports, it indicates packet loss
occurred during the transmission from the PCF to the PDSN.
Issue 01 (2014-05-31)
If the disorder and packet loss of the GRE are included in the reports, check the
transmission from the PCF to the PDSN. Similar problems may be caused by incorrect
port mode of the transmission device (such as switch and router) between the PCF and
162
the PDSN, incorrect MTU parameter configuration of the port, and equivalent route
generated on the transmission network.
If the disorder and packet loss of the GRE are not included in the reports, contact
Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Check the upper-layer modules, such as the SDU, PCF, A10 link, and PDSN.
Issue 01 (2014-05-31)
163
The BSS performs the following operations to provide overall reference for EV-DO rate
analysis:
Records the information about the EC board, Abis interface board, APUDc board,
DPUDb board, and PCF board,
Trace QXDM.
Troubleshooting Procedure
1. In the radio resource check report of the BTS, check whether the value of RSSI is abnormal.
Generally, the value of RSSI should be smaller than 100 dB.
If the value of RSSI is abnormal, contact network optimization personnel to resolve the
RSSI problem.
2. Observe the downlink DRC value on the air interface from the report of the EC board,
generated by traffic tracing of the single user, to check whether the radio environment on the
air interface is poor. Although DRC is a forward value, it can be used as reference for the
reverse rate.
If the radio environment on the air interface is poor, contact network optimization
personnel to optimize the network.
3. Perform the forward rate test for EV-DO services to check whether the forward rate can reach
the normal value.
If the forward rate cannot reach the normal value, check the problem as specified in 12.6
Troubleshooting EV-DO Forward Rate Fluctuation.
4. Check whether the RAC T2P parameter is set correctly. If the default value of the T2P
parameter on the RAC is used, the reverse rate for EV-DO services can reach 600 Kbit/s. To
reach a higher reverse rate, you are advised to modify the value of the T2P parameter.
5. Check whether TCP MTU (Max Transfer Unit) and TcpWindowSize are set correctly on
the computer. You are advised to set TCP MTU (Max Transfer Unit) to 1460 bytes, and
TcpWindowSize to 65535 bytes.
----End
Issue 01 (2014-05-31)
164
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
165
Issue 01 (2014-05-31)
167
13
b.
The license management center generates a license file according to the contract with the
network operator.
c.
The license management center delivers the license file to the network operator.
d.
The network operator powers on the equipment and loads the license file. If the license
file needs to be updated, the network operator can forcibly load the license file to the
related NE by using the FTP protocol.
e.
The PMUO subsystem on the APUOc verifies the validity of the license file.
f.
If the control mode of the license is at the BTS level, the PMUO subsystem sends the
resolved data to each BTS through the SPUO subsystem.
g.
If the control mode of the license is at the RAC level, the PMUO subsystem
automatically allocates CE resources to each SPUO subsystem.
Cause
According to license loading and alarm information, common causes of the fault are as
follows:
Issue 01 (2014-05-31)
169
Analysis
You can locate the fault by performing the following operations:
Check whether the ESN in the license file matches the ESN of the RAC.
Check whether the license file has expired the 60-day trial period.
Troubleshooting Procedure
1. Check whether the license file is available in the loading directory on the BAM.
Check whether the raclicense.dat file is available in the directory ..\cdma2000\LoadDATA
on the BAM.
2. Check whether the transmission between the BAM and the host is faulty.
If the cause displayed on the loading interface shows the file transmission has failed, the
transmission link between the BAM and the host may be faulty. For details about the
transmission fault between the BAM and the host, see Chapter 8 .
3. Check whether the cause for failing to load the license file is a decoding failure. That is, the
license file is abnormal.
Issue 01 (2014-05-31)
170
7. Check whether the equipment ESN matches the ESN specified in the license file.
The equipment ESN is written to the flash memory of the APUOc. The license file is
requested through the ESNs of the active and standby APUOc boards. Therefore, the
requested license file is only available for the or APUOc. If the APUOc is replaced, the
equipment ESN does not match that specified in the license file. As the system runs in trial
mode for 60 days, the license becomes invalid if the faults are not rectified within the trial
period.
If the equipment ESN matches that specified in the license file, contact Huawei technical
support.
If the equipment ESN does not match that specified in the license file, go to 8.
8. Apply for a new license file to replace the original license file. Then, go to 9.
For details about how to apply for a license file, see the Commercial License Application
Process.
9. Run the LOD LICENSE command to forcibly load the license file. Then, check whether the
loading is successful.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
171
Cause
According to the license alarm information, common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Check whether the RAC configuration exceeds the restriction on the license.
Troubleshooting Procedure
1. Query the cause of the System License Invalid alarm.
Start the Alarm Management System from an LMT Query the historical alarms. Select the
System License Invalid alarm, and double-click it to view the cause of the alarm.
2. Check whether the license file fails to be loaded.
If it loads successfully, go to 5.
3. Check whether the license file is available in the loading directory on the BAM.
Check whether the raclicense.dat file is available in the directory ..\cdma2000\Loaddata on
the BAM.
4. Check whether the transmission between the BAM and the host is faulty.
If the cause displayed on the loading interface shows that the file transmission fails, the
transmission link between the host and the BAM may be faulty. For details about transmission
fault between the BAM and the host, see chapter 16 "Troubleshooting OM Failures."
If it is not faulty, go to 5.
Issue 01 (2014-05-31)
172
9. Check whether the equipment ESN matches the ESN specified in the license file.
The equipment ESN is written to the flash memory of the APUOc. The license file is
requested through the ESNs of the active and standby APUOc boards. Therefore, the
requested license file is only available for the APUOc. If the APUOc is replaced, the
equipment ESN does not match that specified in the license file. As the system runs in trial
mode for 60 days, the license becomes invalid if the faults are not rectified within the trial
period
10. Check whether the number of configured carriers exceeds the specifications. That is, check
whether the number of configured carriers exceeds the license restriction.
If it does not exceed the license restriction, contact Huawei technical support.
11. Check whether services are restored after redundant carriers are deleted.
On the LMT, run the RMV CDMACH command to delete carriers. Ensure that the number of
configured carriers is within the restriction on the license file. In addition, run the RMV
CBTSSECTORCARRIER command to remove carriers in sectors of a BTS, ensuring that
the carrier configuration on the BTS is the same as that on the RAC.
12. Apply for a new license file to replace the original license file. Then, go to 13.
For details about how to apply for a license file, see the Commercial License Application
Process
13. Run the LOD LICENSE command to forcibly load the license file and check whether the
loading is successful.
Issue 01 (2014-05-31)
173
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
According to the license alarm information, common causes of the fault are as follows:
The SPUO subsystem works abnormally.
Analysis
To locate the fault, perform the following operations:
Switch over or reset the APUOc.
Troubleshooting Procedure
1. Switch over or reset the APUOc
On the Service Maintenance System, run the STR MANUALSWITCHING command to
switch over the APUOc, or run the RST BRD command to reset it. You may also right-click
on the equipment panel on the Service Maintenance System, and then select Start Manual
Switch Over or Reset Board.
Check whether services are restored after the APUOc is reset.
Issue 01 (2014-05-31)
174
---End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
According to the license alarm information, common causes of the fault are as follows:
The reverse CE resource configuration of the BTS is abnormal.
Analysis
To locate the fault, perform the following operations:
Check whether the reverse CE resource configuration of the BTS is abnormal.
Troubleshooting Procedure
1. Run the following command to query the reverse CE resource configuration of the BTS.
Check whether the value of 1X Reverse CE Number and EV-DO Reverse CE Number is
set to 0, or excessively small.
Issue 01 (2014-05-31)
175
2. Modify the reverse CE resource configuration of the BTS, and check whether the fault is
rectified.
On the Service Maintenance System, run the MOD RACBTSINF command to modify the
reverse CE resource configuration of the BTS.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
176
14
Issue 01 (2014-05-31)
177
Figure 14-1 Structure of the logical structure of the clock synchronization system
In the RAC system, the frame numbers on the air interface must be synchronized with the
satellite synchronization time. Therefore, the RAC is required to ensure both transmission
synchronization and time synchronization.
The differences between transmission synchronization and time synchronization are as
follows:
Line clock signal extracted through the A interface (2.048 MHz line clock signal
extracted from the EIUAa, OIUAa, PEUAa, POUAa, or PO1Aa)
Issue 01 (2014-05-31)
178
The policies for choosing the clock source of the RAC are as follows:
Line clock signals extracted from the A interface are used on a priority basis. If such
signals are not available, the satellite synchronization clock signals are used. BITS clock
signals are not commonly used.
If the line clock signal extracted from the A interface is used and multiple subracks are
configured for the RAC, the clock signal is extracted from the EIUAa, OIUAa, PEUAa,
POUAa, or PO1Aa of the CMPS on a priority basis.
When the FG1Aa or FG2Aa is used as an A interface board, it cannot provide line clock
signals. In this case, the RAC cannot extract line clock signals from the A interface.
Clock Signal Transmission in Transmission Synchronization
After the clock source is selected, the transmission synchronization clock signal is transmitted
as follows:
a.
The RAC sends the clock signal to the GCUOa for phase locking through the reference
clock signal input cable.
b.
The GCUOa generates an 8 kHz system clock signal for the RAC and sends the signal to
the SCUOa in the primary processing subrack by using the backplane, and to the SCUOa
in the secondary processing subrack by using the Y-shaped clock signal cable.
c.
The SCUOa in each subrack performs phase locking for the 8 kHz system clock signal to
convert the signal to a 32 MHz signal. The SCUOa then sends the 32 MHz signal to the
other boards in the subrack as the working clock signal of the subrack.
The GCUOa receives the signal from the GPS or GLONASS antenna.
b.
The GCUOa extracts 1PPS and absolute time information and sends the information to
the SCUOa in the primary processing subrack through the backplane, or to the SCUOa in
the secondary processing subrack through the Y-shaped clock signal cable.
c.
Based on the signal, the SCUOa generates an RFN cell and distributes the RFN cell
through the bus on the backplane to all the boards. In practice, only the APUSc, APUDc,
DPUSb and DPUDb use the RFN cell.
Issue 01 (2014-05-31)
179
Alarm
ALM-6250
ALM-6253
ALM-6254
ALM-6256
ALM-6258
ALM-6259
ALM-6261
ALM-6280
ALM-6288
ALM-6343
ALM-6344
ALM-6025
ALM-6044
ALM-9058
Issue 01 (2014-05-31)
180
a.
b.
indicates feeder, with the other end connected to the surge protector on the RF unit.
If the distance between the satellite antenna and the RF unit is shorter than 50 m (164.04 ft), use an
RG8 feeder.
If the distance ranges between 50 m (164.04 ft) and 100 m (328.08 ft), use a 1/2" feeder.
Board synchronization clock: a synchronization clock output by the satellite card in the
CMPT/USCU
Internal clock: used when no external clock source is available. When the internal clock
is used, the crystal oscillator of the CMPT is in the free-run or holdover state.
Issue 01 (2014-05-31)
181
If multiple synchronization sources are configured for a BTS, the BTS searches for an available
synchronization source in descending order of priority.
The internal synchronization clock source is not configured with a synchronization clock. Therefore,
it is not regarded as an available synchronization source.
ID
Alarm
ALM-19365
ALM-19366
ALM-19367
ALM-19368
ALM-19369
ALM-19370
ALM-19371
ALM-19373
ALM-19374
Issue 01 (2014-05-31)
182
ID
Alarm
ALM-19375
ALM-19406
Cause
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Run the DSP CLKSRC command to query whether the current RAC clock source is correct.
For details about the RAC clock data configuration, see the RAC6690 Initial Configuration
Guide.
If the current system clock source is incorrect, run the RMV CLKSRC or ADD
CLKSRC command to modify the RAC clock source.
2. In the alarm management system, check whether there are any alarms listed in Table 14-1.
If there are any of these alarms in the alarm management system, clear them.
3. In the alarm management system, check whether there are any alarms listed in Table 14-2.
If there are any of these alarms in the alarm management system, clear them.
If there are not these alarms in the alarm management system, contact Huawei for
technical support.
----End
Issue 01 (2014-05-31)
183
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Cause
The time displayed on an MS depends on the GPS time in the system messages sent by the
RASYS and the time zone of the area where the MS resides.
Analysis
Troubleshooting Procedure
1. In the alarm management system, check whether there are any of alarms listed on Table 19-1.
If there are any of these alarms in the alarm management system, clear them.
2. Check whether the local time offset of 1X messages are correctly configured. Run the LST
SYSMSGPARA command to query the configuration of the synchronization channel
messages of the cell where the MS resides. Then, Check whether Local Time Offset in the
messages is the local time zone.
If the Local Time Offset in the messages is the local time zone, go to 3.
If the Local Time Offset in the messages is not the local time zone, set Local Time Offset
to the local time zone.
3. Check whether the local time offset of EV-DO messages are correct. Run the LST DOSPM
command to query the configuration of the synchronization channel messages of the cell
Issue 01 (2014-05-31)
184
where the AT resides. Check whether Local Time Offset in the messages is the local time
zone.
If the Local Time Offset in the messages is the local time zone, go to 4.
If the Local Time Offset in the messages is not the local time zone, set Local Time Offset
to the local time zone.
4. Enable the MS to access the network again, and check whether the displayed time is correct.
The local time offset is included in the 1X synchronization channel message, which is received by an
MS only when the MS searches for a 1X network. Therefore, modification of the local time offset takes
effects on the MS only when the MS accesses the network again.
----End
Information Collection
Collect the following information before contacting Huawei for technical support:
Current alarm
Historical alarm
Issue 01 (2014-05-31)
185
15
Troubleshooting Transmission
Failures
ETH link
UNI link
TRUNK link
IMA link
MLPPP link
PPP link
Logical links are virtual links used to transmit the signaling, service data, and OM messages
between the network interfaces. One logical link can be carried on different physical links.
Table 15-2 lists common logical links.
Issue 01 (2014-05-31)
187
Logical Link
Between RACs
OM link
A13/A16 link
A3 link
A8/A9 link
Signaling link
A17 link
A7 link
A10/A11 link
Traffic link
A18 link
A12 link
b.
c.
d.
Logical Link
Transport layer
TCP/UDP link
Network layer
IP link
Link layer
MAC/MLPPP/PPP/HDLC link
Physical layer
PHY/E1/T1 link
As shown in the preceding table, PHY links, E1/T1 links, MAC links, PPP/MLPPP links, IP
links, and logical links are at different layers. If the transmission interface is faulty, you can
locate the fault by protocol layer in bottom-up mode.
Before locating the fault in the transmission link, you need to check whether the Alarm
Management System reports physical layer alarms, link layer alarms, or logical link alarms.
If the Alarm Management System only reports the logical link alarms, such as the Abis
signaling link fault alarm, troubleshoot the failure by checking the data configuration
directly.
If the Alarm Management System reports the physical layer alarms and link layer alarms,
such as the E1/T1 link alarm and Ethernet link alarm, clear the physical layer alarms by
performing the loopback by segment and checking the DIP switches, and then handle the
data link layer alarms.
Issue 01 (2014-05-31)
188
If the alarm is cleared, the problem does not lie in the link segment.
By performing the loopback by segment, you can accurately locate the physical faults. When
the E1/T1 link alarm or FE link alarm is generated, the loopback by segment is an effective
means of locating the problem.
When you check the grounding status, you need to check the grounding status of all the
transmission devices.
If the alarm of E1/T1 BER Threshold Exceeded is reported and other E1/T1 transmission link
alarms are not reported within one hour, the DIP switches may be set incorrectly.
Use the port IP address to ping the node IP address of the transmission link to check the
transmission at the IP layer. Note that the route must be configured correctly.
Use the logical IP address to ping the logical IP address of the interconnected device to
check whether the logical link is normal. For example, if the A10/A11 interface is faulty,
you can use the logical IP address of the interface board to ping the logical IP address of
the interconnected PDSN device to check whether the logical link fault is caused by the
fault at the IP layer. Note that the route must be configured correctly.
The physical layer alarms and link layer alarms are not generated.
The logical link alarms, such as the Abis signaling link alarm, are generated.
Run the CHK CBTSIFCFG command to check whether the script configuration of the RAC
is the same as that of the BTS.
Issue 01 (2014-05-31)
189
Symptom
Service
1. The OM link between the RAC and the BTS cannot be set up.
2. All the services between the RAC and the BTS are interrupted.
Alarm
Issue 01 (2014-05-31)
190
Item
Symptom
IMA/Fractional IMA Link TX Fault at Far End
IMA/Fractional IMA Link Remote Reception Failure
PPP Link Fault
MLPPP Group Fault Alarm
Ethernet TRUNK Link Down
Ethernet TRUNK Group Down
Ethernet Link Transmission and Reception Defect
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Check whether the settings of the DIP switches of the Abis interface are correct.
If the settings are incorrect, set the DIP switches of the Abis interface correctly.
For details about how to set the DIP switches of the Abis interface on the RAC, see the
RAC6690 Hardware Description. For details about how to set the DIP switches of the Abis
interface board on the BTS, see the BBU3900 User Guide.
2. Check whether the Alarm Management System reports alarms related to the E1/T1, optical
interface, or Ethernet.
If the Alarm Management System reports such alarms, clear the alarms according to the
handling suggestions in the alarm reference.
If the Alarm Management System does not report such alarms, go to 3 when the E1/T1
or STM-1 transmission mode is used. Go to 4 if the FE transmission mode is used.
3. Run the SET TRTEST command to start an E1/T1 crossed pair connection test. Then, run
the DSP TRTEST command to view the test result.
If the E1/T1 crossed pair connection is abnormal, reconnect the E1/T1 crossed pair.
Issue 01 (2014-05-31)
191
4. Check whether the Alarm Management System reports alarms related to the fractional
IMA/IMA link, PPP/MLPPP link, or Ethernet link.
If the Alarm Management System reports such alarms, clear the alarms according to the
handling suggestions in the alarm reference. If these alarms persist, go to 5.
If the Alarm Management System does not report such alarms, no further action is
required.
5. If the fractional IMA link group is configured, check whether the timeslots configured for the
RAC are consistent with the timeslots configured for the BTS. If they are not consistent,
change the configuration of timeslots as required.
If the PPP or MLPPP link group is configured and is carried on the STM-1, run the LST
SDHCFG command to check whether the configuration of the RAC is consistent with the
configuration of the intermediate transmission device. If they are not consistent, change the
configuration as required.
If the ETHLINK or ETHTRK link is configured, check the information about the route from
the RAC to the intermediate transmission device and the information about the route from the
RAC to the BTS. If the route information is not configured, configure it as required.
----End
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. If the Alarm Management System reports alarms related to the E1/T1, optical interface,
PPP/MLPPP link, or Ethernet, troubleshoot the fault by referring to the troubleshooting
procedure for the Abis transmission link failure.
Issue 01 (2014-05-31)
192
2. Run the LST BTSLNK command to check whether the following configurations of the BTS
OM links are correct: board type, MLPPP group number, Ethernet port number, IP address,
and gateway IP address of the interface board.
3. Run the RMV BTSOMLNK and ADD BTSOMLNK commands to change the
configurations of OM links.
If the fault is not rectified and the link type is ETHLNK or ETHTRK, go to 4.
If the fault is not rectified and the link type is PPP or MLPPP, contact Huawei technical
support.
4. Run the LST BTSBOOTP command to check whether the following BTS BOOTP
configurations are correct: the logical IP address, port IP address, and gateway IP address of
the BTS interface board, and BTS electronic serial number (ESN).
If the BTS BOOTP configurations are correct and the Abis interface uses the Layer 2
networking mode, go to 5.
If the BTS BOOTP configurations are correct and the Abis interface uses the Layer 3
networking mode, go to 6.
If the BTS BOOTP configurations are incorrect, run the MOD BTSBOOTP command
or RMV BTSBOOTP and ADD BTSBOOTP commands to change the configurations
as required.
5. Run the LST SRVVLANID or the DSP CBTSVLAN command to check whether the BTS
VLAN configuration, including VLANID, is correct. You must ensure that the VLAN
configuration of the intermediate transmission device is consistent with the BTS VLAN
configuration.
If the configuration is incorrect, run the MOD SRVVLANID command to change the
configuration as required.
6. Check whether the configuration of DHCP Relay of the intermediate transmission device is
correct.
----End
Issue 01 (2014-05-31)
193
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Run the LST BTSLNK command to check whether the following configurations of the BTS
signaling links are correct: interface board, MP group number, Ethernet port number, interface
board IP address, gateway IP address, and SCTP link number.
If the configurations are incorrect, run the RMV BTSSIGLNK and ADD BTSSIGLNK
commands to change the configurations.
2. Run the LST CDMACH command to check whether the RAC is configured with the correct
type of carriers.
If carriers are not configured, configure them. If the RAC is configured with incorrect
type of carriers, go to 3.
If carriers are not configured, configure them. If the BTS is configured with incorrect
type of carriers, go to 4.
4. Troubleshoot the fault according to the handling suggestions of the alarm of Abis Signaling
Link Interrupted on the Alarm Management System.
----End
Issue 01 (2014-05-31)
194
Cause
Common causes of the fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Troubleshoot the fault by referring to the troubleshooting procedure of the Abis transmission
link fault if the Alarm Management System reports alarms related to E1/T1, optical port,
PPP/MLPPP link, or Ethernet.
2. Run the LST BTSLNK command to check whether the following configurations of the BTS
signaling links are correct: interface board, MP group number, Ethernet port number, interface
board IP address, and gateway IP address.
If the configurations are incorrect, run the RMV BTSTRFLNK and ADD
BTSTRFLNK commands to change the configurations.
3. Run the CHK CBTSIFCFG command to check whether the configurations of traffic links on
the RAC are consistent with those on the BTS.
If the configurations are not consistent, change the configurations of traffic links on the
BTS.
---End
Cause
Common causes of the fault are as follows:
Issue 01 (2014-05-31)
195
Analysis
To locate the fault, perform the following operations:
Check whether the A3 links between RACs are configured correctly. For details, see 1.
Check whether any alarm is generated for the logical links that carry A3 links.
Troubleshooting Procedure
1. Run the LST NBRBSCLNK command to check whether the following configurations related
to the A3 interface are incorrect: interface board slot number, link mode of the bearer (such as
IMA, MLPPP, PPP, or FE link), and link number of logical links.
If the configurations are incorrect, change the configurations. If the A3 handoffs recover,
no further action is required.
2. Check whether any alarm is generated for the logical links that carry the A3 links. To check
the link status, run the DSP IMAGRPSTAT, DSP MPLNKSTAT, DSP PPPLNKSTAT, or
DSP ETHLNKSTAT command.
If any alarm is generated, clear the alarm according to the handling suggestions in the
alarm reference. If the A3 handoffs recover, no further action is required.
If the interface board is reset, wait until the board starts again. If the A3 handoffs recover,
no further action is required.
4. Request the device maintenance engineers on the peer end to check whether the PMU
subsystem is reset.
If the PMU subsystem is reset, wait until the PMU restarts. If the A3 handoffs recover,
no further action is required.
----End
Issue 01 (2014-05-31)
196
Cause
Common causes of the fault are as follows:
Configurations of network connections between the PCF and the AAA are incorrect.
Physical connection failures occur between the PCF and the AAA.
Analysis
Review the alarm information.
Troubleshoot the service failure between the PCF and the AAA according to the handling
suggestions of the alarm of AN-AAA Authentication Unreachable (Alarm ID: 2293).
Troubleshoot the configuration problems of the network connections between the PCF
and the AAA according to the handling suggestions of the alarm of A12 Interface
Authentication Path Fault (Alarm ID: 2291).
Troubleshoot the physical connection failures between the PCF and the AAA according
to the handling suggestions of the alarm of Ethernet Link Fault Alarm (Alarm ID: 851).
Troubleshooting Procedure
Troubleshoot the fault according to the handling suggestions in the alarm reference.
Issue 01 (2014-05-31)
197
Cause
Common causes of the fault are as follows:
Configurations of the network connections between the AN and its adjacent ANs are
incorrect.
Network connections between the AN and its adjacent ANs are interrupted.
Analysis
To locate the fault, perform the following operations:
Check whether the A18 links between ANs are configured correctly.
Check whether any alarm is generated for the logical links that carry the A18 links.
Troubleshooting Procedure
1. Run the LST BSCINF and LST NBRAN commands to query information about the serving
AN and the adjacent ANs. Check whether identical IP addresses are allocated to the serving
AN and adjacent ANs and that the IP address allocated to adjacent ANs is not a broadcast IP
address.
If identical IP addresses are allocated, change the related configurations. If the A18
handoffs recover, no further action is required.
2. Run the LST NBRANLNK command to check whether the configurations of the A18 links
on the adjacent ANs are incorrect.
If the configurations are incorrect, change the related configurations. If the A18 handoffs
recover, no further action is required.
3. Check the network structure to determine whether the serving AN and the adjacent ANs are
on the same network segment.
If the serving AN and the adjacent ANs are on the same network segment, go to 4.
If the serving AN and the adjacent ANs are not on the same network segment, run the
ADD IPBRDROUTE command to add the route configuration.
4. Check whether any alarm is generated for the logical links that carry the A18 links. To check
the link status, run the DSP IMAGRPSTAT, DSP MPLNKSTAT, DSP PPPLNKSTAT, or
DSP ETHLNKSTAT command.
If any alarm is generated, clear the alarm according to the handling suggestions in the
alarm reference. If the A18 handoffs recover, no further action is required.
If no alarm is generated, go to 5.
Issue 01 (2014-05-31)
198
5. Wait for five minutes and then check whether the alarm is cleared.
----End
Issue 01 (2014-05-31)
199
Is the E1 link
normal?
No
Yes
Is the
cable correctly
connected?
No
Yes
Check clocks
Are clocks
normal?
Yes
No
Adjust clocks
Yes
Check whether the CRC
configured on the RAC
matches that on the LE
Are they
consistent?
No
End
Troubleshooting Procedure
1.
To query the status of the E1 link used during V5 interface configuration, run the following
command on the Service Maintenance System:
DSP E1T1STAT: FN=2, SN=14, BTP=EIUAa;
2.
Check whether the physical connection of the E1 cable is correct. If the E1 cable is not
correctly connected, connect the cable correctly.
Issue 01 (2014-05-31)
200
3.
On the Alarm Management System, choose Browse > Fault Alarm. The Fault Alarm
Browse window is displayed.
4.
Run the LST BRDPARA command to check whether configurations of clock parameters are
correct.
5.
Check whether the CRC4 verification flag is consistent with that on the switch.
The CRC4 verification flag should be consistent with that on the switch. You can run the LST
V5LNK command to check the configuration for CRC4 verification flag on the RAC.
If the CRC4 verification flag is inconsistent with that on the switch, run the MOD V5LNK
command to modify the configuration.
NOTE
If the E1 cable is correctly connected, and if the CRC4 verification flag is consistent with the switch flag,
you are advised to perform the segmental loopback to locate the problem, such as the E1 cable remote
loopback and transmission loopback.
----End
Issue 01 (2014-05-31)
201
Is the E1 link
normal?
No
Yes
Is the V5 link
normal?
No
Yes
End
Troubleshooting Procedure
1.
On the Service Maintenance System, run DSP E1T1STAT command to check the status of
the E1 link used during the V5 interface configuration.
For example, DSP E1T1STAT: FN=2, SN=14, BTP=EIUAa;
2.
On the Service Maintenance System, run the DSP V5LNK command to query the status of
the V5 link. For example,
DSP V5LNK: FN=3, V5ID=2, LINKS=0, BN=16;
3.
If the V5 link is in the BLOCK state, run the UBL V5LNK command on the RAC to
unblock the V5 link. If the V5 link is still in the BLOCK state, have LE engineers to run
the corresponding command on the LE to unblock the V5 link.
If the V5 link is in the FAULT state, wait for two minutes and check the status of the V5
link. If the V5 link is still in the BLOCK state, have Huawei engineers locate and rectify
the fault.
----End
Issue 01 (2014-05-31)
202
Symptom
The status of the V5 interface is not Normal but the E1 link and V5 link are running properly.
Is the
configuration
correct?
No
Yes
3
Are the V5
interface data
consistent?
No
No
Yes
5
Are the TX
and RX ends correctly
connected?
Yes
End
Issue 01 (2014-05-31)
203
1.
On the Service Maintenance System, run the LST V5CCH command to query the
configuration of the V5 C channel.
2.
The following table lists the V5 configuration that should be consistent between the LE and
the RAC.
Table 15-5 Data to be negotiated between the LE and the RAC
Negotiation
Item
Command
Value
Remarks
V5ID,
ANV5ID
LST V5ITF
0
to
16777215
V5VER
LST V5ITF
V51, V52
VARIANT
LST V5ITF
0 to 127
LINKID
LST V5LNK
0 to 254
TSNo
LST V5CCH
15, 16, 31
PROTTYPE
LST V5CCH
Protect Group
1 Main
Protect Group
1 Standby
Protect Group
2 Main
Protect Group
2 Standby
CHNID
LST V5CCH
0 to 65534
PSTNLCCID
LST V5ITF
0 to 65534
Issue 01 (2014-05-31)
204
Negotiation
Item
Command
Value
Remarks
L3ADDR
LST
V5BAPORT
0 to 32767
TELNO
LST
V5BAPORT
Within
bits
32
V5PARAVAL
3
LST
V5SOFTPARA
Supported or
Not
Supported
4.
If the configuration for the V5 interface is incorrect, run the MOD V5ITF command to
modify the configuration.
If the configuration for the V5 link is incorrect, run the MOD V5LNK command to
modify the configuration.
If the configuration for the C channel is incorrect, run the MOD V5CCH command to
modify the configuration.
5.
Enable the LAP signaling tracing. If no frame signaling is received from the LE, faults
occur on the LE. Have the LE engineers rectify the faults.
If there is some signaling on C path of the C channel, check whether the E1 cable is
incorrectly connected.
----End
Symptom
The status of the V5 interface is not Normal but the E1 link and V5 link are normal.
Impacts of the faults are as follows:
Issue 01 (2014-05-31)
If no A+ interface is configured between the RAC and the LE, subscribers under the
coverage of the RAC cannot initiate calls.
205
Voice and data services that are processed by all subscribers registered on the LE are
handed off to other LEs. This increases the load of other LEs.
No
Yes
No
Yes
Is the A+ interface
configuration on the LE consistent
with that on the RAC?.
No
Yes
End
Troubleshooting Procedure
1.
On the service maintenance system, run the DSP BRDINFO command to query the status of
the interface board. For example,
Issue 01 (2014-05-31)
206
For details about how to replace a board, see the operations in the Site Maintenance Guide.
3.
On the service maintenance system, run the DSP E1T1STAT command to query the
status of E1 links connected to the RAC. For example,
On the service maintenance system, run the DSP V5LNK command to query the link status.
For example,
DSP V5LNK: V5ID=2, LINKS=0, BN=16;
4.
5.
If the A+ links are blocked, run the UBL V5LNK command to unblock the link on
the RAC side. If the links are still blocked after the unblock operation on the RAC,
have the LE technical support engineers unblock the link.
If the links are faulty, wait for 2 minutes. Then, query the status of the link. If the
status is still Fault, contact Huawei technical support engineers.
Check whether the configuration on the LE is consistent with that on the RAC, such as the
interface IDs, interface protocol versions, protection groups. For details about the
configuration, see Table 15-6.
Table 15-6 A+ interface parameters to be negotiated between the LE and the RAC
Negotiation Items
Value
Description
V5 Interface ID
0 to 16777215
V5 Protocol Version
V51 or V52
Variant
0 to 127
Link ID
0 to 254
OFFICENO V5
0 to 65534
Issue 01 (2014-05-31)
207
Timeslot
15, 16, or 31
1: Group 1 (active)
2: Group 1
(standby)
3: Group 2 (active)
4: Group 2
(standby)
Logic C Channel ID
0 to 65534
0 to 65534
L3 Address
0 to 32767
Phone No.
A 4- to 32-digit
decimal string.
Whether to Support
Accelerate Synchronization
Procedure
Supported or Not
Supported
6.
If the A+ interface configuration on the LE is inconsistent with that on the RAC, perform the
following operations:
If the A+ interface configuration is incorrect, run the MOD V5ITF command to correct
the configuration.
If the link configuration is incorrect, run the MOD V5LNK command to correct the
configuration.
If the C-channel configuration is incorrect, run the MOD V5CCH command to correct
the configuration.
----End
Issue 01 (2014-05-31)
208
16
16 Troubleshooting OM Failures
Troubleshooting OM Failures
Remote OM failures
Local OM failures
Cause
For ATs with access authentication failures, trace messages over subscriber interfaces and
analyze the traced code stream and alarms to locate the fault. Common causes of the fault are
as follows:
Analysis
To locate the fault, perform the following operations:
Issue 01 (2014-05-31)
209
16 Troubleshooting OM Failures
Troubleshooting Procedure
1. Run the MML command DSP SIGLNKSTAT to check whether the signaling link is normal.
2. Run the MML command CHK CBTSIFCFG to check whether carrier configurations and IP
addresses on the RAC and BTS are consistent respectively.
If the carrier configurations and IP addresses on the RAC and BTS are consistent
respectively, contact Huawei technical support.
If the carrier configurations or IP addresses on the RAC and BTS are inconsistent
respectively, modify the configuration on the RAC and BTS to ensure consistency.
----End
Cause
According to the analysis of the license-related alarm information, common causes of the
fault are as follows:
Analysis
To locate the fault, perform the following operations:
Troubleshooting Procedure
1. Check the E1 links configured for the BTS.
On the Service Maintenance System, run the LST BTSLNK command.
The command output is as follows:
+++
HW-Airbridge
O&M
#85
%%LST BTSLNK:;%%
Issue 01 (2014-05-31)
2009-12-23 11:33:30
210
16 Troubleshooting OM Failures
Execution succeeded
Link Type
Subrack No.
O&M Link
O&M Link
2
2
10
10
1
2
2266
2267
Index
Interface Board
Slot No.
Link Mode
1
2
1
1
17
14
ETH
PPP
0
1(1)
Index
Bandwidth (Kbps)
Link Flag
O&M IP Address
BTS Interface=>
Board IP Address
1
2
129.10.40.218
129.9.200.219
10.10.10.10
12.23.25.26
Index
Gateway IP Address
1
2
150.150.150.11
-
(Number of results = 2)
BTS Link Information
-------------------Index
BTS ID
BTS Name
Signaling Link
Signaling Link
2
2
1
2
2266
2267
Index
Interface Board=>
Subrack No.
1
2
10
10
1
1
2
2
Index
Interface Board
Slot No.
Link Mode
Bandwidth (Kbps)=>
1
2
18
14
ETH
PPP
0
1(1)
Index
Link Flag
BTS Signaling IP
Address
BTS Interface=>
Board IP Address
1
2
80.126.8.218
80.126.8.219
10.10.10.10
12.23.25.26
Index
Gateway IP Address
Issue 01 (2014-05-31)
BTS2266
BTS2267
Link Type
System Type
Protocol Type=>
211
16 Troubleshooting OM Failures
1
2
150.150.150.11
-
Index
1
2
2
-
CDMA2000 1X
CDMA2000 1X and
EV-DO
SCTP
TCP
(Number of results = 2)
BTS Link Information
-------------------Index
BTS ID
BTS Name
BTS2266
BTS2267
Link Type
Subrack No.=>
Traffic Link
Traffic Link
2
2
1
2
2266
2267
Index
Interface Board
Slot No.
Link Mode=>
1
2
10
10
1
1
18
14
ETH
PPP
Index
System Type
Bandwidth (Kbps)=>
1
2
0
1(1)
1984
Index
Link Flag
1
2
66
-
2
1
80.126.8.218
80.126.8.219
Index
BTS Interface
Board IP Address
Gateway IP Address
FP MUX Switch=>
1
2
10.10.10.10
12.23.25.26
150.150.150.11
-
Off
-
Index
1
2
(Number of results = 2)
---
END
Issue 01 (2014-05-31)
212
16 Troubleshooting OM Failures
+++
HW-Airbridge
2007-05-29 15:11:29
O&M
#89331
%%DSP E1T1STAT: FN=2, SN=14, BTP=PEUBa, E1T1NO=1;%%
RETCODE = 0 Execution succeeded
Query Result
-----------Index
Slot
14
E1/T1No.
E1/
T1OperationalStatus
Aavailable
(Number of Results = 1)
---
END
4. Modify the physical connections according to the data configuration, and then check whether
the BTS can be successfully pinged from the BAM.
If the BTS can be successfully pinged from the BAM, no further action is required.
If the BTS cannot be pinged from the BAM, contact Huawei technical support.
----End
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
213
16 Troubleshooting OM Failures
Cause
The symptoms of BTS remote OM failures are as follows:
The Abis interface link works normally, but the remote Service Maintenance System
fails to ping the BTS.
The remote Service Maintenance System fails to display the working status of the BTS.
Analysis
Table 16-1 describes possible causes of remote OM failures.
Table 16-1 Possible causes of remote OM failures
Possible Cause
Analysis
Issue 01 (2014-05-31)
214
Possible Cause
16 Troubleshooting OM Failures
Analysis
active and standby CMPTs, or replacing the CMPT.
Troubleshooting Procedure
1. Check whether the BAM is working properly.
Issue 01 (2014-05-31)
215
16 Troubleshooting OM Failures
Check whether the BAM starts up normally, and the loading process is normal.
2. Check whether the transmission system is faulty.
Run the LST ALMFE command to query active alarms. The transmission system is faulty if
alarms related to E1/T1 links, FE links, or IMA/UNI/FRAC/PPP links are generated on the
Alarm Management System.
3. Check whether the BTS or the RAC is correctly configured.
Check whether the queried BTS type is consistent with the configuration.
Check whether the value of BTSTP set through the ADD BTS command is consistent
with the value of BTSCLASS set through the SET CBTSINFO command. If the
settings are not consistent, modify the settings to be consistent.
The BTS is managed through the Service Maintenance System on the BAM and data is
loaded from the BAM to the BTS. The BAM, however, fails to telnet to the BTS. In this case,
the route to the BAM may be incorrectly configured because signal streams are sent to the
BTS in form of IP packets during the telnet.
Ping the BTS on the RAC. If the BTS cannot be pinged, the BOOTP information is
incorrectly configured.
Run the LST BTSBTPINFO command to check whether the following BOOTP information
is correct:
BTS ID
Slot No., subslot No., and optical port No. of the CLPC for the active/standby CMUX
that provides the OM link or the subrack No. of the CIPS that connects the RAC and the
BTS
VCI/VPI
If the BOOTP information is incorrect, run the MOD BTSBTPINFO command to modify the
configuration.
4. Check whether advanced FTP properties are correctly configured.
If the BTS fails to upload or download data, the user name, password, or advanced FTP
properties may be incorrect.
On the BAM, check whether the user name omu is valid and whether the password is
correct. Ensure the user name and password are both omu. In the properties of the user,
ensure "Users cannot change the password" and "The password is permanently valid" are
selected.
Check whether the FTP service is enabled on the Internet service manager on the BAM.
Then, check whether the user right is correctly configured. Ensure the virtual path is
correctly configured and enabled. The virtual path must be consistent with the root path
of the loading path. For example, if the loading path is D:\btsload, the virtual path should
be D:.
5. Check whether the version of the software on the BAM is consistent with the version of the
BTS software.
Issue 01 (2014-05-31)
216
16 Troubleshooting OM Failures
If the version of the software on the BAM is not consistent with the version of the BTS
software, the following failures occur and the BTS fails to identify the board No.:
Downloading or activating the FPGA software or the CPU software fails during the
board upgrade.
Each BTS board is marked with a gray cross on the remote Service Maintenance System
after an upgrade.
Ensure the version of the software on the BAM is consistent with the version of the BTS
software before an upgraded.
6. Check whether the voltage is normal.
Check whether the power system of the equipment room functions correctly. If the power
system is faulty, contact power system maintenance engineers from the customer.
Check whether AC/DC power equipment in the different types of BTSs is faulty. For details,
see Table 16-2.
Table 16-2 AC/DC supply devices for different types of BTSs
BTS Type
Checklist
DBS3900
The APM30 supplies power and the DCDU distributes power for the
BBU3900/RRU3606/ODU3601CE.
BTS3900
BTS3900A
BTS3900C
BTS3606CE
BTS3606AC
Issue 01 (2014-05-31)
217
17
Power Equipment
48 V DC
DCDU
Issue 01 (2014-05-31)
218
Power Equipment
48 V DC
DCDU
220 V AC/110 V AC
Symptom
The UPEU functions as the power module of the BBU3900, and works in active/standby
mode.
Table 17-3 describes symptoms of UPEU failures.
Table 17-3 Symptoms
Item
Symptom
Service
Board status
Alarm
Analysis
Table 17-4 describes possible causes of UPEU failures.
Issue 01 (2014-05-31)
219
Analysis
Power Board
Failure
Board Input
Voltage Too Low
Issue 01 (2014-05-31)
220
Troubleshooting Procedure
1. Check whether the UPEU is correctly installed.
If the UPEU is not correctly installed, the Power Board Failure alarm is generated after you
run the LST ALMFE command.
Check whether the connector is securely inserted in the PWR port on the UPEU. If the
connector is loose, secure it.
Check whether the connector at the other end is correctly connected to the DCDU of the
cabinet.
Run the DSP CBTSBBUPWRINFO command to check whether the configured number
and position of the UPEU are correct. The UPEU supports the active/standby working
mode.
If the configured number or position of the UPEU is incorrect, run the RMV
CBTSUPEU command to remove the UPEU. Then, run the ADD CBTSUPEU
command to configure the UPEU again.
Check whether the input voltage of the UPEU is within the range from 38.4 V DC to
57 V DC.
If the input voltage is within the range from 38.4 V DC to 57 V DC, the external
DC supply is normal.
If the input voltage is beyond the range from 38.4 V DC to 57 V DC, the external
DC supply is faulty.
----End
Symptom
The MAPM/MDPM functions as the power module of the ODU3601CE.
Table 17-5 describes the symptoms of MAPM/MDPM failures.
Issue 01 (2014-05-31)
221
Symptom
Service
Board status
Alarm
Analysis
Table 17-6 describes the possible causes of MAPM/MDPM failures.
Table 17-6 Possible causes
Possible Cause
Analysis
36 V DC to 57 V DC (48 V DC supply)
Issue 01 (2014-05-31)
222
Troubleshooting Procedure
1. Check whether the MAPM/MDPM is correctly installed.
Check whether the connector is securely inserted in the AC INPUT/DC INPUT port on
the MAPM/MDPM. If the connector is loose, secure it.
Check whether the connector at the other end is securely connected to the APM30. If the
connector is loose, secure it.
Issue 01 (2014-05-31)
Check whether the input voltage of the MAPM is within the range from 90 V AC to 135
V when 110 V AC power is supplied or is within the range from 176 V AC to 290 V AC
when 220 V AC power is supplied.
223
If the input voltage is within the range, the external AC power supply is normal.
If the input voltage is beyond the range, the AC power supply fails.
Check whether the input voltage of the MDPM is within the range from 36 V DC to
57 V DC.
If the input voltage is within the range, the external DC supply is normal.
If the input voltage of the MDPM is beyond the range, the DC supply is faulty.
----End
Symptom
The ODU3601CE uses the power module MAPM/MDPM.
Table 17-7 describes symptoms of ODU3601CE power module failures.
Table 17-7 Symptoms
Item
Symptom
Service
Board status
Alarm
Analysis
Table 17-8 describes possible causes of ODU3601CE power module failures.
Table 17-8 Possible causes
Possible Cause
Analysis
Issue 01 (2014-05-31)
224
Possible Cause
Analysis
36 V DC to 57 V DC (48 V DC supply)
Troubleshooting Procedure
1. Check whether the MAPM/MDPM is correctly installed.
Issue 01 (2014-05-31)
225
Check whether the connector is securely inserted in the AC INPUT/DC INPUT port. If
the connector is loose, secure it.
Check whether the connector at the other end of the cable is securely connected to the
APM30. If the connector is loose, secure it.
Check whether the input voltage of the MAPM ranges from 90 V AC to 135 V AC when
110 V AC power is supplied or ranges from 176 V AC to 290 V AC when 220 V AC
power is supplied.
If the input voltage of the MAPM is within the range, the external AC supply is
normal.
If the input voltage of the MAPM is beyond the range, the external AC supply is
faulty.
Check whether the input voltage of the MDPM ranges from 36 V DC to 57 V DC.
If the input voltage of the MDPM is within the range, the external DC supply is
normal.
If the input voltage of the MDPM is beyond the range, the DC supply is faulty.
----End
Issue 01 (2014-05-31)
226
18
18.1.1 Terminology
The terminologies of BTS environment monitoring equipment are as follows:
Boolean value
A variable that determines the ON or OFF state
Analog value
A continuous variable such as the temperature and humidity
Dry contact
A port used for reporting equipment status
Active contact
A contact through which output signals carry output voltages
Basic port
Default ports used for monitoring water immersion, infrared rays, door status,
temperatures and humidity, and smoke
Issue 01 (2014-05-31)
227
Manages the power system and controls the charge and discharge of batteries.
Detects and reports information about water immersion, smoke, door status, and standby
Boolean values. Reports the ambient temperature, battery temperature, and standby
analog values.
Detects power distribution conditions and reports related alarms (including dry contact
alarms)
For details about the PMU, see the APM30 User Guide.
The EMUA is an environment monitoring unit. The EMUA monitors the following items:
Environment
Intrusion
Power distribution
For details about the EMUA, see the EMUA User Guide.
Issue 01 (2014-05-31)
228
Function Set
Function
PMU
Power system
management
EMUA
Environment value
analog signal
18.1.4 Specifications
Environmental specifications for the BTS include equipment storage, transportation, and
operating specifications. This section describes the requirements for the ambient temperature
and humidity of equipment operating.
Requirements for the operating temperature are as follows:
Issue 01 (2014-05-31)
BBU:
Indoors: 5% to 95%
Outdoors: 5% to 100%
Huawei Proprietary and Confidential
Copyright Huawei Technologies Co., Ltd
229
RRU: 5% to 100%
ODU: 5% to 100%
Symptom
Table 18-2 describes symptoms of BTS environment monitoring failures.
Table 18-2 Symptoms
Item
Symptom
Board status
Alarm
When the environmental specifications for the BTS are beyond the preset
range, alarms are generated and reported by the environment monitoring
equipment to the RAC. These alarms include:
Analysis
Table 18-3 describes possible causes of BTS environment monitoring failures.
Table 18-3 Possible causes
Possible Cause
Analysis
Environmental
specifications are
beyond the preset
ranges.
Issue 01 (2014-05-31)
230
Possible Cause
Analysis
Cabinet Smoke Alarm
DC Over-Voltage Alarm/DC
Under-Voltage Alarm
Failure of Reading
Temperature Sensor
The environment
monitoring
device is
incorrectly
installed.
Issue 01 (2014-05-31)
231
Troubleshooting Procedure
1. Check whether environmental specifications of the BTS are beyond the preset ranges.
Clear related alarms. For details, see the alarm reference.
2. Check whether the environment monitoring device and related cables are correctly installed.
For details about how to install the EMUA, see the EMUA User Guide.
Issue 01 (2014-05-31)
232
If the RUN indicator on the EMUA blinks at 0.5 Hz and the ALM indicator is off, the
EMUA is powered on. If the RUN indicator is off, the power cable may be reversely
connected. For a description of indicators, see the EMUA User Guide.
Check whether the EMUA is correctly installed, and whether the communication cable is
securely connected to the EMUA and CMPT.
Run the DSP CBTSEMUAINFO command to query EMUA information. If
"PMU-main processing module Communication Link Interrupted" is displayed in the
execution result, the EMUA or communication cable is incorrectly installed.
Check whether the cables are securely connected to the EMUA and the sensors.
For details about the ports on the EMUA and sensors, see the EMUA User Guide.
Check whether the DIP switches on the EMUA are correctly set.
The DIP switch enables or disables sensors. For example, if you want to enable the
water sensor, set the DIP switch for the water sensor to ON. For details about the DIP
switches on the EMUA, see the EMUA User Guide.
You need to set the DIP switch according to the communication protocol supported
by the BTS before the EMUA communicates with the BTS through the serial port.
For example, set the four bits of the SW_ADDR DIP switch to ON (0000) if the
protocol type used by the BTS is CDMA. For the indication of the SW_ADDR DIP
switch, see the EMUA User Guide.
3. Check whether the data of the environment monitoring device is correctly configured.
Run the DSP CBTSEMUA command to check whether the BTS environment
monitoring board is configured.
If the environment monitoring board is not configured, run the ADD CBTSEMUA
command to add an environment monitoring board.
Check whether the environment monitoring device supports analog extended ports or
Boolean extended ports according to the instructions related to the environment
monitoring device.
Follow the instructions related to the environment monitoring device and check
whether the parameters are correctly set.
The temperature and humidity are analog values. Analog values must be set
according to the actual conditions and software configuration rules. For example, the
difference between the upper alarm threshold and the lower alarm threshold must be
greater than 2% of the measurement range of analog values.
For details about how to replace the components in the BBU3900, see the BBU3900
User Guide.
b.
For details on how to replace the RRU3606, see the RRU3606 User Guide.
c.
For details about how to replace the components in the ODU3601CE, see the Airbridge
ODU3601CE User Guide.
----End
Issue 01 (2014-05-31)
233
19
Issue 01 (2014-05-31)
234
Board Initialization
After the BTS is powered on, the boot software on each board loads the BTS software from
the flash memory to the RAM, starts self-check and initialization, and sets up communication
links between boards. If initialization fails, the corresponding boards are reset.
Table 19-1 describes board status during board initialization.
Table 19-1 Board status
Item
Status
BTS board
Service
Maintenance
System
OM Link Setup
Before you remotely configure the BTS on the BAM, an OM link must be set up between the
BTS and the BAM. The physical transmission bearer between the BTS and the RAC can be
E1/T1 or FE cables. The transmission mode over the physical bearer can be ATM or IP. E1/T1
links support ATM or IP transmission, while FE links only support IP transmission. The BBU
currently supports IP over E1/T1 and IP over FE transmission.
If the Huawei RAC6690 is used, the information about the OM link needs to be configured on
the RAC, not on the BTS.
If the Huawei RAC6610 is used, the BTS sends two BOOTP requests to the RAC to obtain
the IP address of the CMPT, route information, and OM IP address of the BTS.
During the startup of the BTS, the CMPT sends the BOOTP request to the CBPE in the
RAC.
From the BOOTP request, the CBPE obtains information such as the IP address of the
CMPT and route information according to the information about the BOOTP
transmission channel.
The CBPE sends the CMPT the BOOTP response frame that contains the IP address of
the CMPT and other information.
The BTS obtains the OM IP address of the BTS, and sends the TCP link setup request to
the BAM.
The BAM receives this request, and the BTS sets up an OM link to the BAM.
If IP over FE transmission is used, BOOTP requests are not sent.
Satellite Tracing
After initialization, the CMPT/USCU traces satellites to obtain reliable clock signals.
Issue 01 (2014-05-31)
235
If a standby CMPT is configured and the links of the standby CMPT are normal, the BTS
switches over the active and standby CMPTs.
Status
BTS board
Service Maintenance
System
Correlated alarm
If the BTS software version is not consistent with that on the BAM, the BTS automatically
downloads the BTS software from the BAM when the automatic download switch is on. If the
OM link to the BAM cannot be set up and the configuration files are available in the flash
memory of the CMPT, the BTS downloads the configuration files from the flash memory.
Cell Setup
After Abis signaling links are set up, the BBU reports information about BTS resource
configuration to the RAC and requests logical configuration from the RAC. The RAC sends
cell configuration data to the BBU. The BTS configures carrier attributes, sets up common
channels, and updates overhead messages. This enables MSs to access the network and
initiate calls.
Issue 01 (2014-05-31)
236
Symptom
Table 19-3 lists symptoms of BTS startup failures.
Table 19-3 Symptoms
Item
Symptom
Service
Board
status
The RUN or ALM indicator on BTS boards blinks fast or the boards are in
offline state.
The CMPT is repeatedly reset.
Alarm
Physical link alarms are generated when signals on E1 links are lost, receive
signals on FE links are lost, frames on E1/T1 links are out of
synchronization, or FE link transmission develops an error.
OM link alarms
OM link alarms are generated when the communication link between the
RAC and the BTS is disconnected, or when the OM links between the CMPT
and other boards are disconnected.
Signaling/traffic link alarms are generated when activated links are not
sufficient in the link group or when the Abis signaling link is disconnected.
GPS clock alarms are generated when the satellites locked by the satellite
card are not sufficient, or when a short- or open-circuit occurs between the
satellite card and the satellite antenna.
Carrier resource alarms are generated when the sector carrier is incorrectly
configured, or when the ARFCN of the sector carrier is incorrect.
Issue 01 (2014-05-31)
237
Analysis
Table 19-4 describes possible causes of BTS startup failures.
Table 19-4 Possible causes
Possible Cause
Analysis
Abis transmission is
faulty.
The bit error rate (BER) is excessively high in the loopback test conducted between
the transmission equipment room to the RAC or the BTS.
The transmission link is unavailable according to the query result, and alarms related
to E1/T1 links are generated.
The cabinet is
incorrectly grounded.
The transmission link is intermittently disconnected, or the BER of E1/T1 Link Too
High alarm is generated. The alarm is cleared after the BTS is powered off and reset.
The alarm, however, is generated again after the BTS runs for a certain period.
Issue 01 (2014-05-31)
238
Possible Cause
Analysis
The connection between the
AC/DC power equipment and
the BTS3900A is faulty.
Issue 01 (2014-05-31)
239
Possible Cause
Analysis
The installation position of the
GPS antenna is improper.
The data
configuration is
incorrect, or is not
consistent with that of
the RAC.
The BAM server is not started, or the load process on the BAM server is improper.
Therefore, the OM link cannot be set up and the BTS startup fails.
The temperature of
the BTS is beyond the
normal range.
The requirements for the ambient temperature of the BTS are as follows:
Ambient temperature for the DBS3900:
Issue 01 (2014-05-31)
240
Issue 01 (2014-05-31)
241
Troubleshooting Procedure
1. Check the BAM server.
Check whether the fault is caused by BAM server problems. Check whether the BAM
server starts, and whether the load process is proper.
2. Check the transmission system.
Check whether the fault is caused by transmission system problems.
Run the LST ALMFE command to query the current alarms. The transmission system is
faulty if alarms related to the E1/T1 link, FE link, and IMA/UNI/FRAC/PPP link are
generated on the Alarm Management System.
For details about how to troubleshoot the transmission system, see chapter 15
"Troubleshooting Transmission Failures."
3. Check the data configuration.
Issue 01 (2014-05-31)
242
Check the configurations of the sector carrier or local cell ID on the RAC and BTS.
On the BAM, run the LST CELL command to check whether the cell information is
configured, and whether the cell information configured on the RAC is consistent
with that configured on the BTS. Run the RMV CBTSCELL, ADD CBTSCELL,
MOD CELL, ADD CELL, or RMV CELL command to modify the cell resource
configuration.
CELLID configured on the MSC must be consistent with that configured on the RAC. LOCALCELLID
configured on the RAC must be consistent with that configured on the BTS.
Check the mask, OM IP address, or signaling link IP address on the RAC and the
BTS.
Run the LST RACBTSINF and LST BTS commands to check whether the OM IP
address configured on the RAC is consistent with that configured on the BTS.
On the BAM, run the DSP SIGLNKSTAT command to check the signaling link
status. If the signaling link is not set up, run the LST BTSLNK and DSP
CBTSTERSIGLNK commands to check whether data configurations such as the
mask or the signaling link IP address, on the BTS and RAC are consistent.
Run the LST CDMACH command to check whether the band configuration is
correct. If the band configuration is incorrect, run the RMV CDMACH, ADD
CDMACH, or MOD CDMACH command to modify it.
Issue 01 (2014-05-31)
Check the resistance between the shield layer and the core wire of the GPS antenna
feeder.
243
Disconnect the clock signal cable from the CMPT and disconnect the GPS antenna.
Use a multimeter to measure the resistance between the shield layer and the core wire
of the GPS antenna feeder. Ensure the resistance is more than one megaohm.
Shortcircuit the shield layer and the core wire at one end of the feeder. Check the
resistance between the shield layer and the core wire at the other end of the feeder.
Ensure the resistance is less than 10 ohms.
If the resistance is less than 10 ohms, the GPS antenna is faulty. Replace the GPS
antenna.
If the resistance ranges from 150 ohms to 200 ohms, test the working current of the GPS
antenna.
6. Check the current of the GPS antenna.
Reconnect the antenna system. Disconnect the cable from the GPS port on the panel of
the CMPT. Connect the outer shell of the cable to the outer layer of the GPS port. Use a
multimeter to measure the current between the cable and the core wire of the GPS port.
If the current ranges from 20 mA to 30 mA, the GPS antenna is operational. If the GPS
antenna is faulty, replace it.
Check whether there are interference sources and obstacles around the GPS antenna.
High buildings or tall trees, and highpower microwave devices or radio broadcast
stations, affect the normal operation of the GPS antenna.
Check whether the power system of the equipment room functions properly.
If the power system is faulty, ask the customer to resolve the power problems.
Based on Table 19-5, check the AC/DC power equipment of BTSs of different types.
Check Whether...
DBS3900
The APM30 and DCDU (the APM30 and DCDU have normal power
output) are securely connected to the BBU3900/RRU3606.
BTS3900
BTS3900A
BTS3900C
BTS3606CE
BTS3606AC
Issue 01 (2014-05-31)
244
---End
Table 19-6 Commands used for different transmission types and query results
Type
E1/T1
FE
Run the DSP CBTSFEPORTINFO command. The query result includes the
link status and the loopback status.
Check whether the GPS clock signal cable is securely connected to the GPS port on
the panel of the CMPT.
Insecure connection between the GPS clock signal cable and the GPS port may cause
unlocking of satellites. Before you determine whether the out-of-lock failure is
caused by a fault in the CMPT or the slot for the CMPT, run the SET CBTSCLK
command to set Reference Clock Source of High Priority to INCLK. If the fault is
rectified, the CMPT or the slot for the CMPT is normal. In this case, locate the
out-of-lock failure in the GPS antenna system.
Disconnect the GPS clock signal cable from the GPS port on the panel of the CMPT.
Connect the positive pole of a multimeter to the internal hole of the GPS port and the
negative pole to the outer shell. Then, test whether the output voltage of the GPS port
is less than 4.5 V DC or is 0 V DC. If the output voltage of the GPS port is abnormal,
the CMPT or the slot for the CMPT is faulty. Replace the CMPT or install the CMPT
in another slot.
----End
Issue 01 (2014-05-31)
245
Information Collection
If it is necessary to contact Huawei technical support, maintenance engineers should collect
the following information related to the fault:
For details about how to collect information, see section 2.4 "Collecting the Fault
Localization Information."
Issue 01 (2014-05-31)
246
CDMA WLL10.0
Troubleshooting Guide
20
DBS3900 RF Subsystem
The RRU3606 is the DBS3900 RF module. It receives and transmits radio signals, and
implements communication between MSs and the radio network system.
BTS3900 RF Subsystem
The CRFU is the BTS3900 RF module. It receives and transmits radio signals, and
implements communication between MSs and the radio network system.
BTS3900A RF Subsystem
The CRFU is the BTS3900A RF module. It receives and transmits radio signals, and
implements communication between MSs and the radio network system.
BTS3900C RF Subsystem
The RRU3606 is the BTS3900C RF module. It receives and transmits radio signals, and
implements communication between MSs and the radio network system.
BTS3606CE RF Subsystem
The STDM and SPAM are the BTS3606CE RF modules. They receive and transmit radio
signals, and implement communication between MSs and the radio network system.
The STDM contains two sub-modules: STRM and SDFU. The STRM supports
modulation and demodulation of baseband signals, up-conversion, and down-conversion.
The SDFU filters signals and performs duplex isolation.
The SPAM consists of three SPABs and one SPMB. The three SPABs amplify downlink
signals of three sectors. The SPMB processes signals reported by the SPABs, and ensures
the normal operation of the SPABs.
Issue 01 (2014-05-31)
247
CDMA WLL10.0
Troubleshooting Guide
BTS3606AC RF Subsystem
The STDM and SPAM are the BTS3606CE RF modules. They receive and transmit radio
signals, and implement communication between MSs and the radio network system.
The STDM contains two sub-modules: STRM and SDFU. The STRM supports
modulation and demodulation of baseband signals, up-conversion, and down-conversion.
The SDFU filters signals and performs duplex isolation.
The SPAM consists of three SPABs and one SPMB. The three SPABs amplify downlink
signals of three sectors. The SPMB processes signals reported by the SPABs, and ensures
the normal operation of the SPABs.
To trace the reverse RSSI in remote mode, select RSSI Monitoring under Resource
Monitoring on the Service Maintenance System, or use Telnet to log in to the BTS.
To trace the reverse RSSI in local mode, connect a crossover cable to the CMPT, and use
Telnet to trace the reverse RSSI.
The commands for RSSI tracing are only applicable to RRUs or RFUs of
fourth-generation BTSs.
RSSI tracing does not stop when you end the Telnet connection. Therefore, you must
stop the tracing and disable serial port redirection when RSSI tracing in Telnet mode is
complete.
If the Telnet connection is ended improperly, enable serial port redirection again and stop
all tracing tasks.
The character string for the item parameter of the str infotrace command is case
sensitive.
The RSSI values obtained in local RSSI tracing are instantaneous values measured every
100 milliseconds. A value is reported every three seconds.
Precautions
Test Procedure
1. Connect cables as shown in Figure 20-1. Set the IP address of the PC to 172.16.16.1.
Issue 01 (2014-05-31)
248
CDMA WLL10.0
Troubleshooting Guide
2. Choose Start > Run. In the Run dialog box, enter Telnet 172.16.16.16 to start the Telnet
program. Enter the user name and the password, and enable the automatic association.
AirBridge BTS3606 CDMA BTS Local Maintenance Console.
Copyright (C) 2000-2006 Huawei Technologies Co., Ltd. All Rights Reserved.
> User name: system
> Password :
HW CBTS>opnday
associational inputting on
HW CBTS>str info
trace: brdtp=trm, brdid=0;
---End
Issue 01 (2014-05-31)
249
CDMA WLL10.0
Troubleshooting Guide
If the average value of main RSSIs ranges from 116 dBm to 93 dBm, the receive main is
functional.
If the average value of diversity RSSIs ranges from 116 dBm to 93 dBm, the receive diversity is
functional.
If the main and diversity of the RRU3606/CRFU are both connected to the antenna system, the
difference between the average value of main RSSIs and the average value of diversity RSSIs must
be within 6 dBm.
Symptom
The current and long-term RSSI information facilitates fault analysis and location. Current
information can be obtained through RSSI tracing on the Service Maintenance System or in
Telnet mode. Long-term RSSI information can be obtained from U2000 traffic statistics.
RSSI problems generally fall into the following three scenarios:
Scenario 1: The difference between the main RSSI and the diversity RSSI is higher than
6 dBm.
Scenario 2: The main RSSI is within the normal range from 116 dBm to 93 dBm, and
the diversity RSSI is lower than 116 dBm.
Scenario 3: Both main and diversity RSSIs are higher than 93 dBm.
Cause
Common causes of the RSSI exception are as follows:
Analysis
Before going to a site, you must analyze relevant data on the U2000, or on the Service
Maintenance System. RSSI exception involves many factors and requires the customer and
network planners to work together to locate the problems. Data analysis involves the
following:
Issue 01 (2014-05-31)
250
CDMA WLL10.0
Troubleshooting Guide
Analyze U2000 traffic statistics to obtain information on how the main and diversity
RSSIs change over time.
Analyze the distribution of sites whose RSSIs are abnormal on the network plan map.
Analyze CDR data. Generally, CDR data is analyzed when MSs are considered to be
faulty.
Troubleshooting Procedure
Scenario 1: The difference between the main RSSI and the diversity RSSI is significant.
a.
When the RX_INB and RX_OUTA ports on one RFU/RRU are not connected to those
on another RFU/RRU, the diversity RSSI is within the normal range from 116 dBm to
93 dBm, and the difference between the main RSSI and the diversity RSSI is higher
than 6 dBm.
Symptom: When the RX_INB and RX_OUTA ports on one RFU/RRU are not connected
to those on another RFU/RRU, the diversity RSSI is within the normal range from 116
dBm to 93 dBm, and the difference between the main RSSI and the diversity RSSI is
higher than 6 dBm. If the diversity RSSI is below 116 dBm over a long period, the
possible cause is that the diversity feeder is not securely connected or the contact inside
the connector is poor.
Trace the main and diversity RSSIs on the Service Maintenance System in real time.
Run the MOD CDMACH command to set the baseband gains of all carriers carried on the
RFU/RRU. Do not change the RF gain. Check whether the difference between the main
RSSI and the diversity RSSI increases when the value of the baseband gain is set to 4000.
If the difference increases, set the value of the baseband gain to 1000 to check whether the
difference decreases and is within the normal range.
If either of the previous scenarios occurs, the main antenna system for this sector is faulty.
If the feeder is faulty, cross-modulation interference increases when the transmit power
increases. Cross-modulation interference decreases when the transmit power decreases.
Issue 01 (2014-05-31)
251
CDMA WLL10.0
Troubleshooting Guide
Add a load to locate which part of the feeder is faulty. A load is added to absorb the
transmit power of the BTS to exclude external factors for the RSSI exception.
Unblock the carriers and connect the load to the ANT_TX/RXA port on the RFU/RRU
whose antenna system is faulty. Then, check whether the difference between the main RSSI
and the diversity RSSI is lower than 6 dBm by tracing main and diversity RSSIs. If the
difference is lower than 6 dBm, the RFU/RRU is normal. If the difference is not lower than
6 dBm, the RFU/RRU is faulty.
Connect the load to the joint where the feeder and the jumper are connected on the
RFU/RRU side. Then, check whether the RFU/RRU and the jumper are normal. If they are
faulty, check the joints or replace the jumper.
Connect the load to the joint where the antenna and the jumper are connected. Then, check
whether the RFU/RRU, jumpers, and feeder are normal. If they are faulty, check the joints,
or replace the jumpers or the feeder. If they are normal, the antenna is faulty or the RSSI
exception is caused by external factors.
Connect the load to the joint where the jumper and the feeder are connected on the antenna
side. Then, check whether the RFU/RRU, jumper, and feeder are normal. If they are faulty,
check the joints, or replace the jumper or the feeder.
b.
When the RX_INB and RX_OUTA ports on one RFU/RRU are connected to those on
another RFU/RRU, the difference between the main RSSI and the diversity RSSI of one
sector is higher than 6 dBm.
Symptom: When the RX_INB and RX_OUTA ports on one RFU/RRU are connected to
those on another RFU/RRU, the difference between the main RSSI and the diversity RSSI
of one sector is higher than 6 dBm. The main RSSIs of all carriers carried on one
RFU/RRU are higher than 93 dBm, and the diversity RSSIs are within the normal range
from 116 dBm to 93 dBm. The main RSSIs of all carriers carried on the other RFU/RRU
are within the normal range from 116 dBm to 93 dBm, and diversity RSSIs are higher
than 93 dBm. For example: RFU0/RRU0 is configured with carriers 10 and 11, and
RFU1/RRU1 is configured with carriers 6 and 7. The main RSSIs of carriers 10 and 11 are
higher than 93 dBm, and the diversity RSSIs of carriers 10 and 11 are within the normal
range from 116 dBm to 93 dBm. The main RSSIs of carriers 6 and 7 are within the
normal range from 116 dBm to 93 dBm, and the diversity RSSIs of carriers 6 and 7 are
higher than 93 dBm.
Issue 01 (2014-05-31)
252
CDMA WLL10.0
Troubleshooting Guide
When the RFUs/RRUs configured for a BTS work in active/standby mode, two feeders for
one sector are connected to the ANT_TX/RXA ports on the RFU/RRUs. In this case, when
the main RSSIs of the carriers are higher than 93 dBm, the antenna system connected to
the RFU/RRU carrying these carriers is faulty.
For example, if the main RSSIs of carriers 10 and 11 are higher than 93 dBm, the antenna
system connected to RFU0/RRU0 is faulty. If the main RSSIs of carriers 6 and 7 are higher
than 93 dBm, the antenna system connected to RFU1/RRU1 is faulty.
To check whether the antenna system is faulty, run the MOD CDMACH command to set
the baseband gain of all carriers carried on the RFU/RRU whose antenna system is faulty.
Do not change the RF gain. Then, check whether the difference between the main RSSI and
the diversity RSSI increases when the value of the baseband gain is set to 4000. If the
difference increases, set the value of the baseband gain to 1000 to check whether the
difference decreases and whether it is lower than 6 dBm.
If either of the previous scenarios occurs, the main feeder for this sector is faulty.
If the feeder is faulty, RSSI increases when the transmit power increases because
cross-modulation interference has increased. RSSI decreases when the transmit power
decreases because cross-modulation interference has decreased.
Add a load to locate which end of the feeder is faulty. A load is added to absorb the
transmit power of the BTS to exclude external factors for the RSSI exception.
Unblock the carriers and connect the load to the ANT_TX/RXA port on the RFU/RRU
whose antenna system is faulty. Then, check whether the difference between the main RSSI
and the diversity RSSI is lower than 6 dBm by tracing main and diversity RSSIs. If the
difference is lower than 6 dBm, the RFU/RRU is normal. Then, perform the next operation.
If the difference is not lower than 6 dBm, the RFU/RRU is faulty. Then, replace the
RFU/RRU.
Connect the load to the joint where the feeder and the jumper are connected on the
RFU/RRU side. Then, check whether the RFU/RRU and the jumper work properly. If they
do not work properly, check the joints or replace the jumper.
Issue 01 (2014-05-31)
253
CDMA WLL10.0
Troubleshooting Guide
Connect the load to the joint where the antenna and the jumper are connected. Then, check
whether the RFU/RRU, jumpers, and feeder work properly. If they do not work properly,
check the joints, or replace the jumpers or the feeder. If they work properly, the antenna is
faulty or the RSSI exception is caused by external factors.
Connect the load to the joint where the jumper and the feeder are connected on the antenna
side. Then, check whether the RFU/RRU, jumper, and feeder work properly. If they do not
work properly, check the joints, or replace the jumper or the feeder.
Scenario 2: The main RSSI is within the normal range from 116 dBm to 93 dBm, and the
diversity RSSI is lower than 116 dBm.
a.
When the RX_INB and RX_OUTA ports on one RFU/RRU are not connected to those
on another RFU/RRU, the main RSSI is within the normal range from 116 dBm to 93
dBm, but the diversity RSSI is lower than 116 dBm over a long period.
Symptom: When the RX_INB and RX_OUTA ports on one RFU/RRU are not connected
to those on another RFU/RRU, the main RSSI is within the normal range from 116 dBm
to 93 dBm, but the diversity RSSI is lower than 116 dBm over a long period.
If the BTS is a distributed base station, check whether a jumper is connected to the
ANT_RXB port on the RRU. If there is no jumper connected to this port, ignore the RSSI
exception.
If the BTS is an outdoor macro base station, check whether the diversity feeder works
properly using the following method: Switch the main and diversity feeders with each
other. Then, check the transmit power and voltage standing wave ratio (VSWR) of the
carrier. If the VSWR is higher than 2, one end of the feeder is disconnected or not securely
connected.
Add a load to locate the problem. A load is added to absorb the transmit power of the BTS
to exclude external factors for the RSSI exception.
Unblock the carriers and connect the load to the ANT_TX/RXA port on the RFU/RRU
whose antenna system is faulty. Then, check whether the difference between the main RSSI
and the diversity RSSI is lower than 6 dBm by tracing main and diversity RSSIs. If the
difference is lower than 6 dBm, the RFU/RRU is normal. Then, perform the next operation.
If the difference is not lower than 6 dBm, the RFU/RRU is faulty. Then, replace the
RFU/RRU.
Issue 01 (2014-05-31)
254
CDMA WLL10.0
Troubleshooting Guide
Connect the load to the joint where the jumper and the feeder are connected on the antenna
side. Then, check whether the RFU/RRU, jumper, and feeder work properly. If they do not
work properly, check the joints, or replace the jumper or the feeder.
Connect the load to the joint where the antenna and the jumper are connected. Then, check
whether the RFU/RRU, jumpers, and feeder work properly. If they do not work properly,
check the joints, or replace the jumpers or the feeder. If they work properly, the antenna is
faulty or the RSSI exception is caused by external factors.
b.
When the RX_INB and RX_OUTA ports on one RFU/RRU are connected to those on
another RFU/RRU, the main RSSI is within the normal range from 116 dBm to 93
dBm, but the diversity RSSI is lower than 116 dBm over a long period.
Symptom: When the RX_INB and RX_OUTA ports on one RFU/RRU are connected to
those on another RFU/RRU, the main RSSI is within the normal range from 116 dBm to
93 dBm, but the diversity RSSI is lower than 116 dBm over a long period.
Check whether the cables between the RFUs/RRUs are securely connected and the
diversity bypass switch is enabled.
If the BTS is an outdoor macro base station, check whether the diversity feeder works
properly using the following method: Switch the main and diversity feeders with each
other. Then, check the transmit power and VSWR of the carrier. If the VSWR is higher
than 2, one end of the feeder is disconnected or not securely connected.
Add a load to locate the problem. A load is added to absorb the transmit power of the BTS
to exclude external factors for the RSSI exception.
Unblock the carriers and connect the load to the ANT_TX/RXA port on the RFU/RRU
whose antenna system is faulty. Then, check whether the difference between the main RSSI
and the diversity RSSI is lower than 6 dBm by tracing main and diversity RSSIs. If the
difference is lower than 6 dBm, the RFU/RRU is normal. Then, perform the next operation.
If the difference is not lower than 6 dBm, the RFU/RRU is faulty. Then, replace the
RFU/RRU.
Issue 01 (2014-05-31)
255
CDMA WLL10.0
Troubleshooting Guide
Connect the load to the joint where the feeder and the jumper are connected on the
RFU/RRU side. Then, check whether the RFU/RRU and the jumper work properly. If they
do not work properly, check the joints or replace the jumper.
Connect the load to the joint where the feeder and the jumper are connected on the antenna
side. Then, check whether the RFU/RRU, jumper, and feeder work properly. If they do not
work properly, check the joints, or replace the jumper or the feeder.
Connect the load to the joint where the antenna and the jumper are connected. Then, check
whether the RFU/RRU, jumpers, and feeder work properly. If they do not work properly,
check the joints, or replace the jumpers or the feeder. If they work properly, the antenna is
faulty or the RSSI exception is caused by external factors.
Scenario 3: Both main and diversity RSSIs are higher than 93 dBm.
a.
Both main and diversity RSSIs of all carriers of a sector are higher than 93 dBm, and
this is not affected by traffic changes.
Symptom: Both main and diversity RSSIs of all carriers of a sector are higher than 93
dBm, and this is not affected by traffic changes.
If the BTS is a distributed base station, the RSSI exception is caused by the distributed
system. Add a load to confirm that the RSSI exception is not caused by the RFU/RRU.
If the BTS is an outdoor base station, check whether the RSSI exception is caused by a
radio repeater, because the radio repeater affects the signals when receiving and amplifying
the signals on a whole band.
Replay the spectrum using the Nastar and analyze the traffic statistics on the U2000 to
check whether the spectrum exceptions are consistent with the abnormal traffic statistics.
Issue 01 (2014-05-31)
256
CDMA WLL10.0
Troubleshooting Guide
Based on the previous operations, the interference source is in the range the sector covers
but the exact place cannot be located. In this case, test the RSSIs of other BTSs around the
current BTS to locate the interference source using the following method: On the Mapinfo,
locate the BTSs whose RSSIs are abnormal around the current BTS. Then, trace and
analyze the spectrum and traffic statistics of those BTSs using the method mentioned
previously. Finally, locate the interference source according to the node of different
directions where RSSI exceptions occur.
Locating method: Start locating the interference source at the BTS where the RSSI is
greatly affected. Then, locate the interference source using the YBT250 along the antenna
direction of the sector where the RSSI exception occurs.
Yagi-Uda antennas are widely used for most radio repeaters and are installed on the
building top or an open area. Therefore, locate the interference source using the YBT250 at
a place with a higher altitude.
The power of a radio repeater is low. Therefore, there is a clear wave on the spectrum
analyzer only when the distance between the spectrum analyzer and the antenna is shorter
than 200 m. After the interference source is located, power off the radio repeater to check
whether the RSSI is normal.
b.
Both main and diversity RSSIs of all carriers of a sector are higher than 93 dBm, and
this is greatly affected by traffic changes. The RSSI is higher than 93 dBm in daytime,
and is within the normal range from 116 dBm to 93 dBm at night.
Symptom: Both main and diversity RSSIs of all carriers of a sector are higher than 93
dBm, and this is greatly affected by traffic changes. The RSSI is higher than 93 dBm in
daytime, and is within the normal range from 116 dBm to 93 dBm at night.
To locate the problem, check the items in the following sequence: network optimization
parameters, neighboring cell, heavy traffic, and interference source.
For network optimization parameters, check the RegZone and Location Area Code
parameters, and access parameters to confirm the values of these parameters for the BTS
with abnormal RSSIs are the same as those for other BTSs.
Issue 01 (2014-05-31)
257
CDMA WLL10.0
Troubleshooting Guide
Both main and diversity RSSIs of all carriers of a sector are higher than 93 dBm because
two sectors are not configured as neighboring sectors. As a result, an MS cannot be handed
off to the target sector with strong pilot signals and the MS transmit power automatically
increases. Then, the base noise of the target sector increases. This affects other MSs in the
target sector. Finally, main and diversity RSSIs increase.
Some MSs try to access the network many times when there is a heavy traffic. As a result,
main and diversity RSSIs increase. This can be determined after the traffic statistics for
carrier traffic and congestion are analyzed.
A radio repeater affects the BTS with abnormal RSSIs 24 hours every day. When MSs are
within the coverage range of the radio repeater, and the traffic of the MSs differs greatly in
daytime and at night, main and diversity RSSIs may increase. Use the following method to
check whether main and diversity RSSIs increase due to an interference source: Trace the
reverse spectrum and analyze it using the Nastar. If the spectrum shape is
and the band is between 825 MHz and 835 MHz, the RSSI exception is caused by the
interference of a radio repeater.
Based on the previous operations, the interference source is in the range the sector covers
but the exact place cannot be located. In this case, test the RSSIs of other BTSs around the
current BTS to locate the interference source using the following method: On the Mapinfo,
locate the BTSs whose RSSIs are abnormal around the current BTS. Then, trace and
analyze the spectrum and traffic statistics of those BTSs using the method mentioned
previously. Finally, locate the interference source according to the node of different
directions where RSSI exceptions occur.
Locating method: Start locating the interference source at the BTS where the RSSI is
greatly affected. Then, locate the interference source using the YBT250 along the antenna
direction of the sector where the RSSI exception occurs.
Yagi-Uda antennas are widely used for most radio repeaters and are installed on the
building top or an open area. Therefore, locate the interference source using the YBT250 at
a place with a higher altitude.
The power of a radio repeater is low. Therefore, there is a clear wave on the spectrum
analyzer only when the distance between the spectrum analyzer and the antenna is shorter
than 200 m. After the interference source is located, power off the radio repeater to check
whether the RSSI is normal.
Issue 01 (2014-05-31)
258
CDMA WLL10.0
Troubleshooting Guide
c.
Both main and diversity RSSIs of some carriers of a sector are higher than 93 dBm.
Symptom: Both main and diversity RSSIs of some carriers of a sector
are higher than 93 dBm.
Symptom
Table 20-1 describes the symptoms of the BTS standing wave.
Issue 01 (2014-05-31)
259
CDMA WLL10.0
Troubleshooting Guide
Symptom
Service
The MS cannot receive signals or can only receive weak signals. This
may lead to call drops. The coverage range of the BTS or the sector
carrier diminishes.
Status of the RF
module
Alarm
Analysis
Table 20-2 describes the possible causes of BTS standing wave failures.
Table 20-2 Possible causes of BTS standing wave failures
Possible Cause
Analysis
The antenna
system is faulty.
Engineering quality
Antenna quality
Delivery mistake
The RF module
is faulty.
Issue 01 (2014-05-31)
260
CDMA WLL10.0
Troubleshooting Guide
Troubleshooting Procedure
1. Check the antenna system.
Check whether the faults are caused by the antenna system. When checking the antenna
system, adhere to the following rules.
Issue 01 (2014-05-31)
If the antenna is damaged, the antenna system is open-circuited. If water enters the
antenna, the antenna system is short-circuited. In either of the preceding situations, the
VSWR is higher than 4.0. In normal situations, the VSWR must be lower than 1.5. The
thresholds for the standing wave alarms are as follows:
If the VSWR is higher than 4.0, the standing wave alarm is generated.
If the VSWR ranges from 2.5 to 4.0 and the RRU/CRFU is used as the RF module,
the standing wave alarm is generated.
If the RF module is STDM and the VSWR ranges from 2.0 to 4.0, the standing wave
alarm is generated.
When the BTS is put into service, test the BTS coverage and record details of the test
location.
261
CDMA WLL10.0
Troubleshooting Guide
After any standing wave alarm is generated, perform the coverage level test for the BTS
and compare results with the information recorded when the BTS is put into service. If
coverage is not affected, the alarms are false. If the coverage is affected and the TX level
of the power amplifier is normal, the fault may be in the antenna system.
To measure the VSWR of the antenna system, connect the RF jumper connector at the
cabinet top to the input port of the SiteMaster.
If the BTS is functional, the VSWR must be smaller than 1.5. If the VSWR is equal to or
greater than 1.5, check the antenna system. Use a SiteMaster to locate the position with
the greatest echo loss. Then examine the construction.
Run the LST CELL command to check whether the frequency band of the cell is
consistent with that supported by the RF module.
If the frequency band of the cell is incorrect, modify the data configuration.
If the RF module does not support the required band, replace the RF module.
Before you remove the RF cable or replace the RF components, power off the RF module.
If the fault persists when the antenna system is normal, replace the RF module and check
whether the fault is rectified.
----End
Follow-up Procedure
If faults persist, contact Huawei technical support.
Issue 01 (2014-05-31)
262
CDMA WLL10.0
Troubleshooting Guide
21
Defining a Subscriber
Before providing the RAC services to a subscriber, you must define the subscriber first.
The prerequisites for defining a subscriber are as follows:
The IMSI of the subscriber is included in the IMSIs allocated to the RAC.
The mapping between the IMSI and the A-KEY or the ESN is configured.
The IMSI and the PN specified for this subscriber are not used by other subscribers.
Deleting a Subscriber
To stop providing the RAC services to a subscriber, you must delete the subscriber. After the
subscriber is deleted, the PN and the IMSI of the subscriber can be used by other subscribers.
You can delete a subscriber by using a forcible or non-forcible method.
When you select a method of deleting a subscriber, note that:
If you use the forcible method, you can delete a subscriber even if the subscriber is in a
call or is engaged in other services. In addition, the call or the ongoing services are
forcibly interrupted.
If you use the non-forcible method, you cannot delete a subscriber who is in a call or is
engaged in other service.
If you delete subscribers in batches, the specified subscribers are forcibly deleted
irrespective of whether the Forcibly deleting a subscriber field is set to YES or NO.
Issue 01 (2014-05-31)
263
CDMA WLL10.0
Troubleshooting Guide
Modifying an IMSI
Modifying an IMSI refers to modifying the IMSI of a subscriber and the A-KEY and the ESN
that correspond to the IMSI without changing the PN of the subscriber.
When you modify the IMSI of a subscriber, note that:
The new IMSI used in the modification belongs to an IMSI resource that is administered
by the HDB. In addition, the A-KEY and the ESN that correspond to the new IMSI are
correctly configured.
If you use the forcible method, you can modify the IMSI of a subscriber who is in a call
or is engaged in other services.
If you do not use the forcible method, you cannot modify the IMSI of a subscriber who is
in a call or is engaged in other services.
When you modify the IMSI of a subscriber, only the ESN and A-KEY of the subscriber
are modified if the new IMSI is the same as the original IMSI. In this case, the forcible
method of modifying the IMSI is unavailable.
If the new IMSI is different from the original IMSI, you can use the forcible or
non-forcible method to modify the IMSI of the subscriber based on the requirements of
the subscriber.
Modifying a PN
When you modify the PN of a subscriber, ensure that the new PN belongs to a configured PN
resource and that the related V5 resource is correctly configured.
Modifying the PN of a subscriber does not affect the in-process call or other ongoing services
of the subscriber.
Troubleshooting
Figure 21-1 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
264
CDMA WLL10.0
Troubleshooting Guide
Is the process
normal?
2
No
Yes
Check whether the IMSI or
the PN is used
Is the
IMSI or the PN
used?
Yes
No
Is the
correspondence
configured?
5
No
Yes
Check the PN-subrack
correspondence
Is the
correspondence
configured?
7
No
Yes
Check the IMSI-AKEY-ESN
correspondence
Is the
correspondence
configured?
9
No
Yes
Check the V5 basic velocity
port table
Is the table
configured?
11
No
10
Yes
Redefine the MS
End
Issue 01 (2014-05-31)
265
CDMA WLL10.0
Troubleshooting Guide
Procedure
1. Check the HDataMan process.
Start the BAM Manager and check whether the status of the HDataMan process is Started.
If the status is not Started, restart the HDataMan process and provide the log under the
directory D:\AirBridge\Services\Log to the Huawei local office.
2. Check whether the IMSI or the PN is used.
1.
On the Service Maintenance System, check whether the IMSI is used. For example,
For example,
DSP SUBSCR: SUBSCRINFO=IMSI, IMSI="460030912120001", NEEDSECRETDATA=NO;
If data on the IMSI are displayed, you can infer that the IMSI is used and you cannot use
this IMSI to define a subscriber.
If no data on the IMSI are displayed, you can use this IMSI after you delete the
corresponding subscriber or modify the PN of the corresponding MS.
2.
If data on the PN are displayed, you can infer that the PN is used and you cannot use this
PN to define a subscriber.
If no data on the PN are displayed, you can use this PN after you delete the
corresponding subscriber or modify the PN of the corresponding MS.
Check whether the IMSI is in the IMSI segments administered by the RAC. If the IMSI is not
in the IMSI segments administered by the RAC, add the mapping between the IMSI and the
RAC or modify the IMSI of the MS.
4. Add the IMSI-RAC mapping.
On the Service Maintenance System, run the following command:
ADD IMSIBSC: IMSIMASK="4600309", BSCIP="129.11.17.1";
Check whether the PN is in the PN segments. If the PN is not in the PN segments, add a new
PN segment.
6. Add the PN-subrack mapping.
On the Service Maintenance System, run the following command:
ADD PNSUBRCK: BPN="6000000", EPN="9000000", FN=3;
Issue 01 (2014-05-31)
266
CDMA WLL10.0
Troubleshooting Guide
The configuration of the V5 resources must be consistent with that on the LE.
Troubleshooting
Figure 21-2 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
267
CDMA WLL10.0
Troubleshooting Guide
Start
1
Is the process
normal?
No
Yes
Check whether the
subscriber is defined
Is the subscriber
defined?
3
No
Yes
Check whether the
subscriber is in a call
Is the subscriber in
a call?
4
No
Yes
Forcibly delete the
subscriber
End
Procedure
1. Check the HDataMan process.
Start the BAM Manager and check whether the status of the HDataMan process is Started.
If the status is not Started, restart the HDataMan process and provide the log under the
directory D:\AirBridge\Services\Log to the Huawei local office.
2. Check whether the subscriber is defined.
Issue 01 (2014-05-31)
268
CDMA WLL10.0
Troubleshooting Guide
If no data are displayed, you can infer that the subscriber is defined and you cannot delete the
subscriber.
3. Check whether the subscriber is in a call.
On the Service Maintenance System, run the following command:
DSP VDBUSER: NTYPE=PN, PN="6005000";
If the status of the subscriber is ACTIVE, you can infer that the subscriber is in a call and
you cannot delete this subscriber.
----End
Troubleshooting
Figure 21-3 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
269
CDMA WLL10.0
Troubleshooting Guide
Start
1
Is the process
normal?
No
Yes
Check whether the
subscriber is defined
Is
the subscriber
defined?
No
Yes
Yes
No
End
Procedure
1. Check whether the HDataMan process is normal.
Start the BAM Manager and check whether the status of the HDataMan process is Started. If
the status is not Started, restart the HDataMan process and provide the log under the
directory D:\AirBridge\Services\Log to the Huawei local office.
2. Check whether the subscriber is defined.
On the Service Maintenance System, run the following command:
Issue 01 (2014-05-31)
270
CDMA WLL10.0
Troubleshooting Guide
If no data are displayed, you can infer that the subscriber is not defined and you cannot
modify the IMSI for the subscriber.
3. Check whether the new IMSI is used.
On the Service Maintenance System, run the following command:
DSP SUBSCR: SUBSCRINFO=IMSI, IMSI="460030912120001", NEEDSECRETDATA=NO;
If data on the new IMSI are displayed, you can infer that the new IMSI is used and you cannot
use this IMSI.
Ensure that that the new IMSI exists in the IMSI-RAC mapping, and that the IMSI-A-KEY-ESN
mapping is configured.
If the new IMSI is identical with the original one, the subscriber data in the FAM are forcibly updated.
----End
Troubleshooting
Figure 21-4 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
271
CDMA WLL10.0
Troubleshooting Guide
Start
1
Is the process
normal?
No
Yes
Check whether the
subscriber is defined
Is
the subscriber
defined?
No
Yes
Is the PN used?
Yes
Use another PN
No
Modify the PN
End
Procedure
1. Check whether the HDataMan process is normal.
Start the BAM Manager and check whether the status of the HDataMan process is Started. If
the status is not Started, restart the HDataMan process and provide the log under the
directory D:\AirBridge\Services\Log to the Huawei local office.
2. Check whether the subscriber is defined.
On the Service Maintenance System, run the following command:
Issue 01 (2014-05-31)
272
CDMA WLL10.0
Troubleshooting Guide
If no data are displayed, you can infer that the subscriber is not defined and you cannot
modify the PN for the subscriber.
3. Check whether the new PN is used.
Ensure that the new PN exists in the PN-subrack mapping, and that the V5 basic velocity port table is
configured.
If data on the new PN are displayed, you can infer that the new PN is used and you cannot use
this PN. Use another new PN that is not used.
4. Modify the PN.
Run MOD SUBSCRPN to modify the PN. For example,
MOD SUBSCRPN: SUBSCRINFO=PN, OLDPN="50081000", NEWPN="50081001";
----End
Issue 01 (2014-05-31)
273
CDMA WLL10.0
Troubleshooting Guide
22
VCN-V
BSS-V
LE
VCN-H
1.Origination Message
2.Base Station
Ack Order
3.Complete L3 Info:
CM Service Request
4.Roam CM Service
Request
5.ESTABLISH
6.ESTABLISH ACK
7.ALLOCATION
11.Channel Assignment
Message
10.Assignment
Request
9.Roam
Assignment Request
8.ALLOCAITON
COMPLETE
12.Tch Preamble
13.BS Ack Order
14.MS Ack Order
15.Service Connect
Message
16.Service Connect
Completion
17.Assignment
Complete
18.Roam Assignment
Complete
19.Send Called
Number(DTMF)
RingBack Tone
Issue 01 (2014-05-31)
275
CDMA WLL10.0
Troubleshooting Guide
Procedure
2 MOC Failures shows the procedure of the roaming MOC voice service.
1.
Upon receipt of the CM_Service_Request message, the MSC-V resolves the cell
information carried in the CM_Service_Request message, computes the roaming billing
area code by using a specific roaming billing algorithm. Then the MSC-V constructs the
roaming billing area code in the Roam CM_Service_Request message and sends the
Roam CM_Service_Request message to the MSC-H.
2.
The MSC-H verifies the Roam CM_Service_Request message and decodes the
information in this message. Then the MSC-H constructs the roaming ID, the home
location information, and the access location information in the original ESTABLISH
message and sends this message to the LE.
Troubleshooting
Figure 22-2 shows the troubleshooting procedure.
Issue 01 (2014-05-31)
276
CDMA WLL10.0
Troubleshooting Guide
Are
these parameters
enabled?
3
No
Yes
Check the correspondence
between the roaming
charging area number and
the roaming charging area
ID
4
Is the
correspondence
configured?
5
No
Yes
Check the correspondence
between the cell and the
roaming charging area ID
Is the
correspondence
configured?
7
No
Yes
Check the roaming charging
area ID in the subscription
profile
8
Is the ID configured?
No
Yes
Is the
correspondence
configured?
Yes
No
Add the correspondence
between the number
segment and the roaming
charging area ID
End
Issue 01 (2014-05-31)
277
CDMA WLL10.0
Troubleshooting Guide
Procedure
1. Check the roaming-related system-level software parameter and V5 software parameter.
1.
=
=
=
=
3
10
PARA1(AN Invoke TEI Cancellation Procedure)
Host does not initiate TEI cancellation procedure
Subrack No.
V5 Interface ID
Parameter Index
Parameter Value
=
=
=
=
3
10
PARA2(Reserved)
0
Subrack No.
V5 Interface ID
Parameter Index
Parameter Value
=
=
=
=
3
10
PARA3(Exchange Parameter)
Accelerated Synchronization Supported
Subrack No.
V5 Interface ID
Parameter Index
Parameter Value
=
=
=
=
3
10
PARA4(Link Fault Monitoring Timer)
5
TO BE CONTINUED
--END
Issue 01 (2014-05-31)
278
CDMA WLL10.0
Troubleshooting Guide
Run LST RCAREA to check whether the mapping between the roaming billing area number
and the roaming billing area ID is configured.
4. Add the mapping between the roaming billing area number and the roaming billing area ID.
Run ADD RCAREA to add the mapping between the roaming billing area number and the
roaming billing area ID.
5. Check the mapping between the cell and the roaming billing area ID.
Run LST CELL to check whether the mapping between the cell and the roaming billing area
ID is configured.
6. Add the mapping between the cell and the roaming billing area ID.
Run MOD CELL to add the mapping between the cell and the roaming billing area ID.
7. Check the roaming billing area ID in the subscription profile.
Run DSP SUBSCR to check whether the roaming billing area ID is configured in the
subscription profile.
If the output displays roaming billing Area ID List = -, -, -, you can infer that this ID is not
configured.
8. Check the mapping between the number segment and the roaming billing area ID.
Run LST RCPN to check whether the mapping between the number segment and the
roaming billing area ID is configured.
9. Add the mapping between the number segment and the roaming billing area ID.
Run ADD RCPN to add the mapping between the number segment and the roaming billing
area ID.
----End
Issue 01 (2014-05-31)
279