Professional Documents
Culture Documents
Issue
01
Date
2011-08-11
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 the warranty of any kind, express or implied.
Website:
http://www.huawei.com
Email:
support@huawei.com
Issue 01 (2011-08-11)
01 (2011-08-11)
This is the first commercial release of RAN12.0.
Issue 01 (2011-08-11)
ii
Contents
Contents
About This Document .................................................................................................................... ii
1 Overview......................................................................................................................................1-1
1.1 Purpose .......................................................................................................................................................... 1-1
1.2 Intended Audience ......................................................................................................................................... 1-1
1.3 Organization .................................................................................................................................................. 1-1
1.4 Reference Documents ................................................................................................................................... 1-1
iii
Contents
Issue 01 (2011-08-11)
iv
Contents
Issue 01 (2011-08-11)
1 Overview
Overview
1.1 Purpose
This document provides information on how to identify and repair common faults on RAN
devices that are working in a live network. Operation and maintenance (OM) personnel
should use this guide in the following scenarios:
z
1.3 Organization
This guide consists of the following chapters:
z
Chapter 1 Overview
Issue 01 (2011-08-11)
1-1
Issue 01 (2011-08-11)
2-1
Issue 01 (2011-08-11)
2-2
Operations performed on the equipment before the fault occurred, and the results of these
operations
Consult the personnel who reported the fault about symptoms, time, location, and
frequency of the fault.
Consult the OM personnel about the equipment running status before the fault occurred,
operations performed on the equipment before the fault occurred, fault symptoms, and
measures taken to deal with the fault and the results.
Observe board LEDs, the OM subsystem, and the alarm management system to obtain
information about the status of system software and hardware.
Estimate the impact of the fault by testing services, measuring performance, and tracing
interface messages or signaling messages.
Do not handle a fault hastily. Collect as much information as possible before attempting
to repair the fault.
Maintain good communication with other departments and OM personnel of other sites.
Ask them for technical support if necessary.
Issue 01 (2011-08-11)
2-3
2.2.4 Troubleshooting
To repair faults and restore the system, troubleshoot different faults using proper measures
and procedures. Troubleshooting consists of checking cables, replacing boards, modifying
data configuration, switching over boards, and resetting boards.
Summarize methods for improvement of the system which could avoid recurrence of the
faults of the same type.
Ensure notes are recorded in a logbook or other method that OM personnel will have future access to.
E-mail: support@huawei.com
Website: http://support.huawei.com
http://support.huawei.com contains contact information for the local office in your region.
Call quality and access for many users in a live network are affected.
KPIs, such as call drop rate and access success rate, deteriorate so much that the call
quality and access for many users in a live network are seriously affected.
The KPI Exceed Threshold alarm (ID: 22302) is generated, and the performance
statistics are such that emergency measures must be taken.
The services in one subsystem, one subrack, or the entire radio network controller (RNC)
are affected.
All the services in one interface board are affected, or one digital signal processor (DSP)
is faulty.
Issue 01 (2011-08-11)
2-4
NOTE
If the services in one NodeB are affected, it is not an emergency fault.
Process Description
When emergency situations occur, follow these three steps:
1. Check associated alarms and operation logs.
Check associated alarms to identify, isolate, and roll back the services rapidly and efficiently.
Issue 01 (2011-08-11)
2-5
If errors (for example incorrect settings) were introduced into the core network (CN),
neighboring RNCs (NRNCs), or transmission devices.
If modification of any RNC, CN, or NRNC parameters has been made. If this has been
done, then restore the preceding parameters, and check if services are restored.
2. Determine the impact and scope of the faults, and try to recover the network.
3. Check if network services are fully restored.
---End
Application Scenarios
Original information provides an important reference for determining the scope and type of
the faults. In the initial phase of troubleshooting, original information provides a reference for
determining the fault scope and determining possible locations of the faults. Senior OM
personnel are able to locate faults using original information.
Instructions
Original information can be applied to troubleshooting both network element faults and other
faults such as E1T1 faults. In the trunk troubleshooting process, you must connect to the
transport system and map the signaling. Therefore, original information such as whether the
transport system works properly, whether the peer end parameters are modified, and the
definitions of some signaling parameters is vital to the troubleshooting and repair of the faults.
Issue 01 (2011-08-11)
2-6
Application Scenarios
Alarms can help in handling equipment faults and service faults.
Instructions
See the local maintenance terminal (LMT) online help for instructions on the alarm system.
See the related online help in the alarm management system for detailed troubleshooting
methods of each alarm.
Application Scenarios
LED status is used to locate the general area of the fault. LEDs can indicate a specific fault or
can be used to locate other faulty equipment. All information gathered from LEDs can be used
to facilitate later operations. After observing the LED status of a board, circuit, link, or node,
check any associated alarms.
Instructions
For details about the board LED status, see the related online help section in the related
hardware description.
Applicable to various scenarios for analyzing the call procedure and for tracing VIP
users
Application Scenarios
User tracing can locate recurring faults in call services.
Instructions
For instructions on user tracing, see the OM online help.
Issue 01 (2011-08-11)
2-7
Traces all messages over the interface for a specific period of time
Application Scenarios
Interface tracing can locate faults in calls, for example, low put-through rate of calls in a
commercial network.
Instructions
For instructions on interface tracing, see the LMT online help.
Application Scenarios
Traffic statistics are applied to KPI analysis and performance analysis.
Instructions
Traffic statistics can be obtained through the M2000 or Nastar.
Issue 01 (2011-08-11)
2-8
Application Scenarios
Comparison and interchange are used when faults occur after NE hardware, software or a new
feature is introduced that may have caused a service outage.
Instructions
Use this method to compare the performances and KPIs before and after hardware or software
is changed, or a new feature is introduced.
Application Scenarios
An upgrade is recommended when the current version has bugs that are fixed in later versions.
A rollback is required when the updated version causes KPIs to deteriorate or services to be
interrupted.
Instructions
For details, see the relevant upgrade guide.
Issue 01 (2011-08-11)
2-9
Issue 01 (2011-08-11)
2-10
Database information
OMU logs
Alarm logs
Host logs
Traffic statistics
Issue 01 (2011-08-11)
3-1
Various error information and running trace of the front administration module (FAM)
host
See section 3.4.5 "Collecting Host Logs" for procedures to collect host logs.
3-2
In the Windows operating system, log in to the active OMU. Start the
omu_backup_linker tool.
b.
In the Linux operating system, log in to the active OMU. Run the cd
/mbsc/bam/common/services command. This command switches the current directory to
the directory in which the tool is located.
Run the /omu_backup_linker command, and then press Enter to start the tool, as shown in
the following figure.
Issue 01 (2011-08-11)
3-3
Type a valid backup file pathname, and press Enter to begin the backup. If the message
"Backup OMU database succeed!" is displayed, then the database has been successfully
backed up on the OMU, as shown in the following figure.
---End
Issue 01 (2011-08-11)
3-4
The LST LOGRSTINFO command will query and display the specific path of the saved
logs.
---End
---End
Issue 01 (2011-08-11)
3-5
Issue 01 (2011-08-11)
3-6
---End
On the Other tab, finish the tracing and recording configuration, as shown in the following
figure.
Issue 01 (2011-08-11)
3-7
For data transmission faults, ensure that faults that occur in the first 100 seconds are traced. If no fault
appears in the first 100 seconds, restart tracing.
---End
Issue 01 (2011-08-11)
3-8
2. Choose a log file and then click Download. The file is saved in the default directory
Root\bam\common\MeasResult or a designated directory.
---End
Issue 01 (2011-08-11)
3-9
Issue 01 (2011-08-11)
3-10
---End
User Tracing
1. Log in to the LMT, double-click User to start user tracing.
2. Set Trace Method. If no drive test UE is available, select Chain Time, and the system will
randomly trace less than four UEs. If drive test UE is available, select IMSI.
a.
Set Chain Time for user tracing, as shown in the following figure.
Note that the Begin Time must be the same or earlier than the current time, and the End
Time should be around 24 hours later.
Issue 01 (2011-08-11)
3-11
b.
Issue 01 (2011-08-11)
3-12
3. On the IUB and UU tabs, select the CDT items to be traced, and enter the parameters, as
shown in the following two figures.
Issue 01 (2011-08-11)
3-13
4. Select Autosave on the Basic tab page, enter a saved path in File Name, and click OK to start
tracing.
The following figure shows the report of the traced CDT messages.
---End
Issue 01 (2011-08-11)
3-14
a.
Collect the NodeB CHR using computer onsite. Use this method only if you can log in to
the NodeB directly through the LMT.
Run the following commands:
SET CHRSW: CHRSW=ON, CHRTYPE=ALL, IP=XX.XXX.XXX.XXX,
DSTF=X:\CHRDATA\, USR=admin, PWD=admin;
SET CHRLEVEL: CHRLEVEL=DETAIL; CHRUSERTYPE=ALL USERTYPE;
Ensure that the IP is the IP address of the computer, and the user name and password are
correct. When using the FTP software provided with the NodeB LMT, the user name and
password are admin. The path X:\ CHRDATA must be set up in advance.
b.
Do as follows to collect the NodeB CHR through the FTP client of the M2000. Use this
method only if you can log in to the NodeB LMT using the M2000 client.
Run the following command:
SET CHRSW: CHRSW=ON, IP=XX.XXX.XXX.XXX, DSTF="/export/home/sysm",
USR="ftpuser", PWD="ftpuser";
c.
Do as follows to collect the NodeB CHR through the RNC BAM FTP server. Use this
method only if you can upload data through the RNC BAM FTP server:
Run the following command:
SET CHRSW: CHRSW=ON, IP=XX.XXX.XXX.XXX, DSTF=/ftp/, USR=FtpUsr,
PWD=XXXXXXXX;
Note that the path of the BAM FTP server must be one of the following two:
D:\WCDMA RNC\BAM\VersionA\FTP
D:\WCDMA RNC\BAM\VersionB\FTP
4. Six minutes after the command is executed, check whether any logs are uploaded to the path
D:\CHRDATA before the test.
5. After the NodeB CHR is completely uploaded, run the following command to turn off the
CHR function:
SET CHRSW: CHRSW=OFF; SET CHRLEVEL: CHRLEVEL=NONE;
Note that the NodeB CHR collected through the second or third method can be retrieved from
the FTP server.
---End
Issue 01 (2011-08-11)
3-15
2. Click Open, and double-click the XXX.pyc file on the desktop, as shown in the following
figure.
Issue 01 (2011-08-11)
3-16
The following figure shows an example of the preceding operations being successful.
3. Right-click the blank area and choose to save the exported results.
Collecting the DSP memory will be used as an example to describe this process.
a.
Issue 01 (2011-08-11)
3-17
b.
Upload the board logs for the baseband processing board after running the script. See
section 3.6.3 "Collecting NodeB Main Board and Board Logs" for more details.
---End
Issue 01 (2011-08-11)
3-18
Issue 01 (2011-08-11)
3-19
Choices are available for the alarm types, event types, and sites.
Issue 01 (2011-08-11)
3-20
3. Enter the name of the file to be uploaded in the displayed dialog box. Click to select
Compress Upload which reduces upload time. Name the file in the site name + date format
to make it different from previously downloaded files.
Issue 01 (2011-08-11)
3-21
Click OK to begin the upload of NodeB WMPT log to the M2000 server.
4. Click NM Server, and choose the corresponding NodeB in the left pane.
Issue 01 (2011-08-11)
3-22
6. Choose Transfer > From NM to Client, specify a path. When the process starts, the selected
file will be uploaded to the local computer.
To upload a NodeB configuration file, click the Data tab, as shown in the following
figure.
Issue 01 (2011-08-11)
3-23
---End
3. Choose the NodeB and configuration file in the displayed window. When the process starts, a
configuration file is downloaded to the M2000 server.
Select the downloaded file in the file list under Data. Choose Transfer > From NM to NE,
and the configuration file is sent to the NodeB through the M2000.
---End
Back up the configuration file for the NodeB to be upgraded before upgrade.
Check whether the versions before and after the upgrade are recommended in the
upgrade guide.
Issue 01 (2011-08-11)
3-24
Check whether the upgrade-related software has been uploaded to the M2000 server.
Click the > icon in the dialog box, as shown in the following figure.
Issue 01 (2011-08-11)
3-25
Click Next to select the software version and operation settings. Click Finish to start the
upgrade.
---End
To reduce bandwidth usage, the first method is usually adopted. However, in some cases, the
RNC BAM may be not compatible with the NodeB, which leads to the failure in uploading
Issue 01 (2011-08-11)
3-26
and downloading files. In this situation, change the FTP server address of a NodeB to the IP
address of the M2000 OMC.
1. Choose Software > File Server Setting to open the File Server Setting window.
2. Select the NodeB in the left pane. If you select RNC, information of all the NodeBs under the
RNC is displayed.
3. Set the file server in the File Server Name column. If the files cannot be uploaded or
downloaded when the file server is configured in the RNC BAM, change the file server
setting to that of the M2000. The M2000 is the OMC, and appears in the File Server Name
column in the following figure.
---End
Issue 01 (2011-08-11)
3-27
Method 1: Log in to the NodeB directly through the M2000 if your computer is running the
corresponding LMT.
Right-click the selected NodeB, and choose Maintenance Client from the drop-down menu.
The M2000 automatically logs in to the NodeB using the LMT, as shown in the following
figure.
Method 2: Log in to the NodeB through the configured M2000 proxy server.
1. Set the NodeB information on the LMT, as shown in the following figure.
2. Select Proxy Server, and ensure that the Proxy Server IP address is set to that of the M2000.
3. Enter the user name and password for the M2000, and then click Login, as shown in the
following figure.
Issue 01 (2011-08-11)
3-28
---End
2. Enter the user name and password for the M2000 and click Login.
Issue 01 (2011-08-11)
3-29
3. Select the NodeB in the displayed dialog box and click OK.
---End
Issue 01 (2011-08-11)
3-30
4 RNC Troubleshooting
RNC Troubleshooting
Configurations, such as maximum downlink power and frequencies, on the RNC and
NodeB are inconsistent.
Issue 01 (2011-08-11)
4-1
4 RNC Troubleshooting
If Reason of the latest cell setup failure is NCP unavailable or CCP unavailable, the
link that carries the NCP or CCP may be faulty. Check whether an alarm related to the
corresponding SAAL (for ATM transmission) or SCTP (for IP transmission) link is
reported. If such an alarm is reported, clear the alarm according to the instructions in the
alarm reference.
If Reason of the latest cell setup failure is Power mismatch, check whether the local
cell on the NodeB side is available. If the local cell is unavailable and the alarm
ALM-4033 Local Cell Unusable is reported, clear the alarm according to the instructions
in the NodeB alarm reference. If the local cell is available, check the maximum downlink
power configured on the NodeB and RNC. If the power configured on the NodeB is
smaller than that on the RNC, change the maximum downlink power on either the
NodeB or RNC so that that the power configured on the NodeB is greater than or equal
to that on the RNC.
Run the LST UCELL command on the RNC LMT to query the maximum downlink
power on the RNC side. The following is shown as an example:
Issue 01 (2011-08-11)
4-2
4 RNC Troubleshooting
Run the LST LOCELL command on the NodeB LMT to query the maximum downlink
power on the NodeB side. The following is shown as an example:
Issue 01 (2011-08-11)
If Reason of the latest cell setup failure is NodeB return cell setup failure and cause
is "NodeB sends CELL SETUP FAILURE (Frequency acquisition not supported)" in the
4-3
4 RNC Troubleshooting
location information about the alarm ALM-22206 Cell Setup Failure, check whether the
frequency configurations on the RNC and NodeB are consistent.
Run the LST UCELL command on the RNC LMT and the LST LOCELL command on
the NodeB LMT to query the frequency configurations.
z
If Reason of the latest cell setup failure is Local cell not reported and cause is "Data
configuration error or inconsistent with physical resources" in the location information
about the alarm ALM-22206 Cell Setup Failure, check whether the NodeB is configured
with a corresponding local cell and whether the local cell ID on the RNC and NodeB is
consistent. Run the LST UCELL command on the RNC and the LST LOCELL command
on the NodeB to query the local cell ID.
If Reason of the latest cell setup failure is Common channel setup failed and reason
of the latest common channel setup failure is "L2 resource allocation failed", log in to the
RNC LMT. View the BSC Device Panel window and check whether DPUs can be
detected. If no DPUs can be detected, insert new DPUs. If DPUs can be detected but are
unavailable, replace them with new ones.
Log in to the RNC LMT. Run the LST LICENSE command and set FN to the file name of
the current license to check the license items. If IP transmission is used over the Iub interface,
IP Transportation in Iub Interface should be ON; if IP/ATM dual-stack transmission is
used over the Iub interface, IUB ATM/IP Dual Stack Transportation Function should be
ON, as shown in the following figure:
+++
WCDMA-RNC
O&M
#138901
2011-08-09 19:53:28
%%LST LICENSE:;%%
RETCODE = 0
Execution succeeded.
LicenseFileName
IsCurrentLicense
Demo_BSC6900_V900R013_UO_20110727.dat
license.dat
(Number of results = 2)
+++
WCDMA-RNC
O&M
#138902
2011-08-09 19:53:52
Execution succeeded.
......
Issue 01 (2011-08-11)
MBMS Function=ON
HSDPA DRD=ON
4-4
4 RNC Troubleshooting
=
Enhanced Iu Flex=ON
Function=ON
If you still cannot locate the cause of the problem after performing the preceding procedure,
collect information using the following table and contact Huawei technical support:
Information to Be
Collected
Method
Result
MML reports
MML reports
Messages traced
over the Iub
interface
Configuration script
RNC alarms
The CN is faulty.
Issue 01 (2011-08-11)
4-5
4 RNC Troubleshooting
Iu-related configurations, set by running the ADD TRMMAP, ADD ADJMAP, and ADD
UCNNODE commands, are incorrect or deleted.
The Service Area Codes (SACs), Routing area codes (RACs), and Location Area Codes
(LACs) of some cells are not configured on the CN side.
Resources of certain cells, such as power, code, transmission, and channel element (CE)
resources, are congested.
If the user plane of the Iu interface is faulty and the following alarm is reported:
z
2. Check other RNCs connected to the same CN. If most of them are faulty, check whether the
CN is faulty or has had configurations modified recently.
3. Check whether all cells served by the RNC are abnormal by checking the counters
VS.RAB.AttEstabCS.Conv and VS.RAB.SuccEstabCS.Conv. If all cells are abnormal,
troubleshoot the problem by following steps 3 through 6. If only some cells are abnormal,
troubleshoot the problem by following steps 7 through 13.
4. If IP transmission mode is used over the Iu interface, start Iu-interface tracing to check
whether services fail mainly on certain IP addresses assigned by the CN. If so, check whether
the IP paths and routes to those IP addresses are configured on the RNC.
5. Check whether paths over the Iu interface are consistent with the configurations set by
running the ADD TRMMAP command. Check whether the configuration of the CN node or
Iu-CS AAL2 routers is omitted or deleted.
6. Check the measurement of AAL2 path traffic over the Iu interface by checking the counters
VS.AAL2PATH.PVCLAYER.RXBYTES and VS.AAL2PATH.PVCLAYER.TXBYTES or
check the measurement of IP path traffic over the Iu interface by checking the counters
VS.IPPATH.IPLAYER.RXBYTES and VS.IPPATH.IPLAYER.TXBYTES. If the traffic of
one path is much smaller than that of any other path or is unidirectional, remove that one path
by running the RMV AAL2PATH or RMV IPPATH command to restore the service. If the
usage of each path approaches 100%, new paths need to be added or the path bandwidth needs
to be expanded.
Issue 01 (2011-08-11)
4-6
4 RNC Troubleshooting
7. Locate and check the SPU subsystem and interface board that serves the faulty cells. If most
of these cells are served by the same board, perform an active/standby switchover on the
board.
8. Run the DSP UCELL command to check the cell status. If the Operation state of the cell is
Unavailable, check the fault reason.
If the cell is not activated, run the ACT UCELL command to activate the cell. If the cell
setup fails, refer to section 4.1 for troubleshooting.
If the Operation state is Available, run the LST UCELLACCESSSTRICT command to
check whether the cell or user Access Class (AC) is barred, as shown in the following figure.
If Access class x barred indicator or Cell barred indicator for SIB3 is BARRED, change
it to NOT_BARRED.
Run the DSP UCELLCHK command to check whether the power, code, transmission, or CE
resources of the cell are congested, as shown in the following figure.
Issue 01 (2011-08-11)
4-7
4 RNC Troubleshooting
Power congestion
Power congestion may be on the uplink or downlink. Run the LST UCELLALGOSWITCH
command to query the call admission control (CAC) algorithm in use.
If the access failure is caused by uplink power congestion, check whether the RTWP is within
the valid range (96.5 dB to 105.5 dB).
Check whether Auto-Adaptive Background Noise Update Switch is ON. If so, deactivate
the cell, and then re-activate the cell to check whether the RTWP becomes normal.
If Auto-Adaptive Background Noise Update Switch is OFF, turn off the uplink CAC
switch or reset the background noise value.
To turn off the uplink CAC switch, run the following command:
MOD UCELLALGOSWITCH: NBMUlCacAlgoSelSwitch=ALGORITHM_OFF
To reset the background noise value, check the average RTWP value (indicated by
VS.MeanRTWP) in the performance statistics, and set the background noise value to the
minimum VS.MeanRTWP. An example command is as follows:
MOD UCELLCAC: BackgroundNoise=61;
The default value of BackgroundNoise is 61. The parameter value depends on the onsite conditions and
is calculated with this formula: Background noise = 112 + BackgroundNoise x 0.1.
Issue 01 (2011-08-11)
4-8
4 RNC Troubleshooting
If the access failure is caused by downlink power congestion, check the latest Transmit
Carrier Power (TCP) value and run the LST UCELLCAC command to query the service
admission threshold. If the TCP value exceeds the threshold, the access fails. Check whether
the admission threshold is configured according to the baseline data or network planning data.
If not, change the admission threshold to the correct value. Otherwise, consult Huawei
network planning engineers about whether to adjust the threshold or expand the capacity.
Code congestion
Check whether the Cell code used rate is normal, and trace the code tree to check whether the
cell uses too many code resources. If the minimum available codes are more than the DL
handover reserved spreading factor (SF), the cell capacity is limited and needs to be expanded.
The smaller the SF, the higher the service rate. For example, if the available minimum SF is
SF32 but the configured reserved SF is only SF16, the admission
fails.
Alternatively, you can run the LST UCELLCAC command to check whether the reserved
code of the cell is configured according to the baseline data or the network planning data. If
Issue 01 (2011-08-11)
4-9
4 RNC Troubleshooting
the reserved SF is too small (for example, SF4), change it according to the baseline data.
Otherwise, consult Huawei network planning engineers about whether to adjust the SF or to
expand capacity.
Newly admitted users cannot use reserved SFs. As a result, the smaller the SF, the fewer code resources
available for newly admitted users.
Transmission congestion
Run the DSP UCELLCHK command to check whether the Iub interface of the cell is
congested.
If the Iub interface is congested, check whether the reserved bandwidth for the AAL2 path is
within the valid range. By default, the reserved bandwidth is 0, indicating that no bandwidth
is reserved.
Issue 01 (2011-08-11)
4-10
4 RNC Troubleshooting
Run the LST TRMFACTOR command to check whether the values configured for service
activation factors are within the valid ranges. For best results, these parameters should be set
to their recommended values.
For PS services, run the LST UUSERGBR command to check whether the guaranteed bit
rate (GBR) is configured according to the baseline data. If the GBR value is too large (such as
384 kbit/s), consult the network planning engineers about whether to decrease the GBR or
adjust the bandwidth. The GBR and bandwidth adjustment is subject to the approval of the
operator.
Issue 01 (2011-08-11)
4-11
4 RNC Troubleshooting
CE congestion
Run the DSP UCELLCHK command to check whether CE resources of the cell are
congested. CE congestion can be eliminated by purchasing more CE licenses or deploying
more sites for traffic sharing.
9. Check whether the LAC/SAC/RAC data is configured on the CN side (MSC/SGSN). If the
data is not configured, UEs cannot register or attach themselves to the network. You can trace
the intelligent optimum sample (IOS) of the cell to check whether a UE can register or attach
to the network.
When the LAC/SAC/RAC data is not configured on the CN side, the initial direct transfer messages sent
by the RNC are not responded or are rejected and the signaling connection control part (SCCP)
connection setup fails. As a result, the UE cannot access the network.
10. Check whether the AAL2Path or IPPATH is available and configured correctly.
Run the LST TRMMAP command to check whether the transmission mapping is set
correctly. For example, CS services map RT paths (primary paths) and NRT paths (secondary
paths); R99 PS services map NRT paths (primary paths) and RT paths (secondary paths);
HSPA services map HSPA NRT paths. High Speed Downlink Packet Access (HSDPA)
services and High Speed Uplink Packet Access (HSUPA) services can share the same
TRMMAP. Run the LST AAL2PATH or LST IPPATH command to check whether the
mapped path in the TRMMAP is configured.
Issue 01 (2011-08-11)
4-12
4 RNC Troubleshooting
According to the preceding results, the CS services can be set up only after an ATMRT path or
HQ_IPRT path is configured.
11. If you still cannot locate the cause of the problem after performing the preceding procedure,
collect information using the following table and contact Huawei technical support:
Information to Be Collected
Method
Result
Configuration data
OPT_LOG and
HISTORY_ALARM log
Binary logs
Issue 01 (2011-08-11)
COL LOG:
LOGTYPE=HISTORY_ALARM1&OPT_LOG-1;
4-13
4 RNC Troubleshooting
Information to Be Collected
Method
Result
Issue 01 (2011-08-11)
4-14
5 NodeB Troubleshooting
NodeB Troubleshooting
Either the main or diversity RTWP is abnormally high while the other is normal.
Either the main or diversity RTWP is abnormally low while the other is normal.
Alternatively, the alarm ALM-26521 RF Unit RX Channel RTWP/RSSI Too Low is reported.
This alarm is reported in either of the following two scenarios:
z
The diversity channels are configured with but not connected to antennas.
As specified by the 3GPP standard, the range of RTWP is 1064 dBm. The RTWP is
abnormal if its value is continuously greater than 102 dB or less than 110 dB or if the
RTWP peak value is continuously greater than 80 dB.
Issue 01 (2011-08-11)
5-1
5 NodeB Troubleshooting
Feeder loss needs to be calculated based on the length and type of feeder; this information can
be found in the feeder product document.
3. Check whether there is passive intermodulation.
Run the SET TXSW command to shut down the transmit channel. If the RTWP value then
returns to normal, the RTWP abnormality may be caused by the passive intermodulation.
Check the main feeder connection.
If the RTWP value does not return to normal after the shutdown, go to step 4.
4. Check the number of HSUPA subscribers.
Log in to the RNC LMT, and choose Monitor > UMTS Monitoring > Cell Performance
Monitoring. Check whether the number of HSUPA users exceeds 10. If so, ignore this
problem because a large number of HSUPA users usually lead to a high RTWP value.
If the number of HSUPA users is less than 10, go to step 5.
Issue 01 (2011-08-11)
5-2
5 NodeB Troubleshooting
6. If you still cannot locate the cause of the problem after performing the preceding procedure,
collect information using the following table and contact Huawei technical support:
Issue 01 (2011-08-11)
5-3
5 NodeB Troubleshooting
Information to Be
Collected
Method
Result
MML reports
MML reports
TMA Gain
MML reports
Tracing logs or
RTWP data
Traffic
RTWP tracing results of the faulty cell. To start a tracing, log in to the NodeB LMT and
choose Maintenance > Realtime Specific Monitoring > Board RTWP. The results
will be generated in 20 minutes.
Issue 01 (2011-08-11)
5-4
5 NodeB Troubleshooting
Issue 01 (2011-08-11)
5-5
5 NodeB Troubleshooting
The number of uplink or downlink CEs exceeds the number allowed by the license.
The number of local cells exceeds the number allowed by the license.
The number of cells with transmit power of xx exceeds the value of PA[XXdBm].
Issue 01 (2011-08-11)
5-6
5 NodeB Troubleshooting
2. Check whether the O&M channels between the M2000 and NodeBs are normal and whether
the status of the NodeBs is normal on the main topology of the M2000.
3. Redeliver the license.
4. If you still cannot locate the cause of the problem after performing the preceding procedure,
collect information using the following table and contact Huawei technical support:
Issue 01 (2011-08-11)
5-7
5 NodeB Troubleshooting
Information to Be
Collected
Method
Result
NodeB WMPT
logs
On the left side of the window, click OMC Server. Select the
corresponding NodeB and click Other on the right side of the
window. Right-click the log to be downloaded to the local PC and
choose Transfer > From NE to OMC Client.
A screen capture for the
license delivery failure
When the license delivery fails, save the screen capture of the
current window in .jpg format.
A screen
capture for the
license delivery
failure
Double-click the NodeB with delivery failure and save the screen
capture of the displayed window in .jpg format.
A screen
capture for the
detailed cause
of the license
delivery failure
License file to be
delivered
License file to
be delivered
Issue 01 (2011-08-11)
5-8
Possible Causes
z
The negotiation mode of the Ethernet ports on the NodeB or RNC is inconsistent with
that of the Ethernet ports on devices interconnected with the NodeB or RNC.
Virtual local area network (VLAN) configurations and Address Resolution Protocol
(ARP) security-related configurations are incorrect.
Issue 01 (2011-08-11)
6-1
The Quality of service (QoS) policy for the transport network is inappropriate.
Troubleshooting Methods
If IP transmission on an FE port is interrupted, analyze reported alarms and events, conduct
ping tests, trace IP packets, query the ARP tables by running the DSP ARP command, or
query the routing tables by running the DSP IPRT command.
The section Troubleshooting Procedure provides guidelines for checking whether faults occur
at the physical, data link, or IP layer.
For details on how to conduct a ping test and how to trace IP packets, see section 6.1.3 "Verification
Methods."
Troubleshooting Procedure
1. Troubleshoot the physical layer.
Check whether the duplex mode for Ethernet ports on the NodeB is consistent with that on the
RNC, whether Maximum Transfer Unit (MTU) configurations are appropriate, and whether
there are errors in the IP packets received by the RNC and NodeB. For details, see section
6.1.3 "Verification Methods."
Check whether optical cables are connected correctly. Remove one optical cable from the
transmit end and check whether a relevant alarm is generated on the receive end. If a relevant
alarm is generated, the cable is properly connected.
2. Troubleshoot the data link layer.
Check whether VLAN configurations are correct. For two interconnected devices, VLAN IDs
between interconnected ports on the two devices must be consistent. Otherwise, the two
devices cannot communicate with each other. Further, note the following:
z
If load sharing and VLAN are applied to ports on the active and standby boards of the
RNC, VLAN IDs between these ports must be the same. You can add a VLAN ID to a
specific port by running the ADD VLANID command.
If a VLAN is applied to the NodeB, a VLAN must be also applied to Stream Control
Transmission Protocol (SCTP) links, IP paths carrying user data, common channels
carrying user data, and O&M channels. If an IP clock is configured, a VLAN must be
applied to IP clock links, and the VLAN IDs of these links must be consistent with the
network plan. If the NodeB is configured with multiple next hops, you must distinguish
them according to the network plan when applying the VLAN to the NodeB. You can run
the LST VLANMAP and LST VLANCLASS commands to query VLAN
configurations for the NodeB.
Check whether there are ARP tables corresponding to the RNC, NodeB, and router.
3. Troubleshoot the IP layer.
Check whether IP route configurations are correct and whether these configurations have
taken effect. Devices whose IP addresses belong to different network segments must be
configured with routers.
Check whether the local end is correctly connected to the peer end, and whether the two ends
are correctly connected to the gateway by conducting IP tests. When conducting an IP test,
you are advised to use IP packets with different packet sizes and different differentiated
services code point (DSCP) values. For details, see section 6.1.3 "Verification Methods."
Issue 01 (2011-08-11)
6-2
Locate faults by tracing IP packets. For details, see section 6.1.3 "Verification Methods."
If you are not sure whether faults occur on universal terrestrial radio access network (UTRAN) devices
or in the transport network even though you have ensured that configurations are correct and appropriate,
connect a PC to the NodeB or RNC to narrow down areas where the faults may occur.
4. If you still cannot locate the cause of the problem after performing the preceding procedure,
collect information using the following table and contact Huawei technical support:
Information to Be
Collected
Method
Result
Detailed networking
Execution results
ARP tables
Execution results
Routing tables
Execution results
Pinged IP packets
Execution results
Traced IP packets
Execution results
Operation results
Issue 01 (2011-08-11)
6-3
Users experience poor speech quality, the call drop rate is high, and the HSPA data rate is low
or greatly fluctuates.
Possible Causes
z
The negotiation mode of Ethernet ports on the NodeB or RNC is inconsistent with that of
Ethernet ports on the interconnected device.
Troubleshooting Methods
If some IP packets are lost, analyze the reported alarms and events, conduct ping tests, or
trace IP packets.
The section Troubleshooting Procedure provides guidelines for checking whether faults occur
at the physical, data link, or IP layer.
For details on how to conduct a ping test and how to trace IP packets, see section 6.1.3 "Verification
Methods."
Troubleshooting Procedure
1. Troubleshoot the physical layer.
Check whether parameter settings for Ethernet ports on the NodeB or RNC are consistent
with those for Ethernet ports on the interconnected device, whether MTU configurations are
appropriate, and whether there are errors in the IP packets received by the RNC and NodeB.
For details, see section 6.1.3 "Verification Methods."
Check whether Ethernet cables are functioning correctly. Replace one Ethernet cable with a
new one and check whether IP packets are received correctly. If no IP packets are lost, the
replaced Ethernet cable was the cause of the problem. If some IP packets are still lost, the
replaced Ethernet cable is not faulty.
Check whether optical cables are correctly connected to receive ports, transmit ports, active
ports, or standby ports on devices. Ensure that cables do not cross. If you still cannot locate
the fault, connect a PC to the NodeB or RNC to narrow down areas where faults may occur.
2. Ping all the involved routers, the RNC, and the NodeB in sequence.
If some packets are lost when you ping the NodeB from the RNC, ping all the involved
routers and the NodeB in sequence to locate the device where these packets are lost. You can
also perform these operations on the NodeB if some packets are lost when you ping the RNC
from the NodeB.
Conduct IP tests to check whether the local end is connected correctly to the peer end and
whether the two ends are connected correctly to the gateway. When conducting an IP test, use
IP packets with different packet sizes and different DSCP values. For details, see section 6.1.3
"Verification Methods."
Issue 01 (2011-08-11)
6-4
3. If you still cannot locate the cause of the problem after performing the preceding procedure,
collect information using the following table and contact Huawei technical support:
Information to Be Collected
Method
Result
Detailed networking
Execution results
Pinged IP packets
Execution results
Traced IP packets
Execution results
Operation results
Issue 01 (2011-08-11)
6-5
Port No. must be set to the port number of the Ethernet port.
Run the DSP ETHPORT command on the NodeB LMT to query the properties of an
Ethernet port, as shown in the following figure:
Port No. must be set to the port number of the Ethernet port.
Clear Statistic specifies whether to clear statistic values from the execution results after the command is
executed.
Issue 01 (2011-08-11)
6-6
Max transmit unit indicates the maximum size of data that can be transmitted over the
Ethernet port. Currently, this parameter is consistently set to 1500 on all UTRAN devices. For
devices in the transport network, this parameter must be set to a value greater than 1500.
Speed and Duplex indicate the working mode of the Ethernet port. If the RNC is
interconnected with another device, the duplex mode of this port must be consistent with that
of the corresponding port on the interconnected device. Otherwise, some packets may be lost,
errors may occur in received IP packets, or services may be interrupted.
Link Availability Status indicates the current link status. If the value is Unavailable, the IP
transmission is interrupted.
Rx correct bytes indicates the size of correct packets received by this port and Tx correct
bytes the size of correct packets transmitted from this port. By comparing the execution
results of the DSP ETHPORT command from each time, you can determine whether this port
is transmitting and receiving packets correctly.
Rx bad bytes indicates the size of incorrect packets received by this port and Tx bad bytes
the size of incorrect packets transmitted from this port. If values of these two parameters are
not 0, this port has received or transmitted incorrect packets.
Issue 01 (2011-08-11)
6-7
Ping
You can ping the NodeB on the RNC or ping the RNC on the NodeB.
1) Theory
When you ping the peer end from the local end, an Internet Control Message Protocol (ICMP)
echo request packet is automatically sent to the peer end. Upon receiving the packet, the peer
end responds with an ICMP packet.
With the Ping function, O&M personnel can check whether a device is connected correctly to
the transport network, whether transmission is stable, whether transmission delay or variation
occurs, and whether packets are correctly transmitted and received. In addition, by pinging all
the involved devices one by one, O&M personnel can locate faults accurately and efficiently.
If you ping another device on the RNC, set the size of ICMP packets, TTL value, DSCP value,
number of ping tests, test frequency, and response expiration threshold. If you ping another
device on the NodeB, set the size of ICMP packets, DSCP value, number of ping tests, and
response expiration threshold.
Set Size of packet to 20, 500, or 1500 and use the DSCP value of 48, 46, 38, 22, 14, or 0 to
perform a ping test. If possible, try all of these values.
2) Example
The following operations are performed on the RNC LMT.
Run the RNC MML command PING IP with Source IP address, Destination IP address,
Subrack No., and Slot No. set to appropriate values. Set Differentiated services code point
to an appropriate value if you want to check whether a specific ICMP packet with a certain
DSCP value is transmitted or received correctly.
The following figure shows the interface where you can set the preceding parameters:
Issue 01 (2011-08-11)
6-8
Parameter
Meaning
Source IP address
Destination IP address
Whether to ping the peer end continuously. If you set this parameter to NO,
you must specify the Packet Number parameter. If you want to check
whether some packets are lost, delay variation occurs, or transmission is
interrupted, set Packet Number to a large value, for example, 1000.
Size of packet
Reply Time-Out
Interval of send
Time to Live
Issue 01 (2011-08-11)
6-9
Meaning
Packet Size(byte)
Timeout(ms)
Packet Number
Priority Rule
DSCP
Appoint Interface
As shown in the preceding figure, the delay is shorter than 80 ms, and no packets are lost
because the number of transmitted packets equals the number of received packets.
The following figure shows the execution results of the command when exceptions occur in
the transport network:
Issue 01 (2011-08-11)
6-10
As shown in the following figure, the message "Request time out" is displayed, which
indicates that some packets are lost:
As shown in the preceding figure, if the value of time is greater than 80 ms, the transmission
delay is long. If the value fluctuates with a large difference (for example, over 30 ms), delay
variation occurs. If the message "Request time out" is displayed multiple times, transmission
is interrupted.
Ping test results not only expose faults in the network but also provide the type and severity of
the problem. For example, if some packets are lost, you can figure out a packet loss rate based
on the number of transmitted ICMP packets and the number of received ICMP packets. This
loss rate tells you the severity of the problem.
4) Notes
If you want to check whether IP transmission is interrupted, set Packet Number to a value
greater than 1000 to ensure accurate test results.
Traceroute
1) Theory
Traceroute enables users to obtain next hops on an IP path between the transmit end and
receive end by using ICMP expired packets, ICMP unreachable packets, and the TTL field in
headers of IP packets. If the transmit end sends a router an IP packet with a TTL value of 0,
the router discards the packet and responds with an ICMP expired packet. The transmit end
can then obtain the IP address of this router. By sending ICMP unreachable packets, the
transmit end determines whether packets have reached the destination router. If the receive
Issue 01 (2011-08-11)
6-11
end cannot receive IP packets, you can specify the maximum TTL value and then trace IP
packets to locate faults accurately and efficiently.
2) Operation
The following operations are performed on the RNC LMT.
Run the RNC MML command TRC IPADDR, as shown in the following figure:
Meaning
Destination IP address
Destination IP address
Source IP address
Source IP address
MAX TTL
Number of
TRACERT Packages
Per TTL
Reply Time-out
Issue 01 (2011-08-11)
6-12
Meaning
TTL First
TTL Max
UDP Port
Timeout
DF Switch
DSCP
Issue 01 (2011-08-11)
6-13
Then, increase the TTL value next time you trace IP packets. If tracing results are displayed as
asterisks when a specific TTL value is used, the corresponding next hop is faulty.
Issue 01 (2011-08-11)
6-14
Possible Causes
E1/T1 cables or optical cables are improperly connected or become faulty.
PVC layer configurations are incorrect.
QoS policy is incorrect.
Exceptions occur on all the devices involved.
Troubleshooting Methods
If ATM transmission is interrupted, conduct a CC test on a PVC or run the RNC MML
command DSP AALVCCPFM or LOP VCL to check whether a disconnected PVC is
causing the ATM transmission interruption. For details, see section 6.2.3 "Verification
Methods."
The section Troubleshooting Procedure provides guidelines for checking whether faults occur
at the physical, data link, or transport layer.
Troubleshooting Procedure
1. Check whether E1/T1 port configurations are correct, including the frame format, coding
scheme, scrambling mode, resistance capability, and grounding. To query these
configurations, run the RNC MML commands LST E1T1 and DSP E1T1 or the NodeB
MML command DSP E1T1WORKMODE.
Note the following when checking E1/T1 port configurations:
z
The configured resistance capability of an E1/T1 cable must be consistent with its actual
capability. In addition, its resistance capability on the local end must be consistent with
that on the peer end. 75-Ohm E1/T1 cables require grounding while 120 Ohm E1/T1
cables do not.
Frame format, scrambling mode, and coding scheme of an E1/T1 port on the local end
must be consistent with those of the corresponding E1/T1 port on the peer end.
Otherwise, the status of upper-layer links may become abnormal, the alarm ALM-21221
IMA Link Loss of Frame may be reported on the RNC, and the alarm ALM-25823 IMA
Link Loss of Frame may be reported on the NodeB.
If the coding scheme HDB3 is used, no scrambling mode needs to be activated. If the
coding scheme AMI is used, a scrambling mode must be activated; otherwise, the
IMAGRP negotiation will fail.
2. Check whether E1/T1 cable connections are correct, whether E1/T1 cables are correctly
connected and these cables do not cross, and whether inverse multiplexing over ATM (IMA)
links belong to the same IMA group on both the local end and the peer end.
1) Incorrect E1/T1 cable connections
Issue 01 (2011-08-11)
6-15
According to the network plan, ports 0 and 1 must be connected to B1 and ports 2 and 3 to B2.
The E1/T1 cables, however, are incorrectly connected, as shown in the following figure. In
this case, E1/T1 cables can operate properly but the carried links fail.
Adding new links, deleting existing links, or resetting carried links cannot solve the problem.
To check whether an E1/T1 cable is properly connected, disconnect the cable on the local end
and check the port on the peer end that reports an E1/T1 loss of signal alarm. If the port is the
one specified by the network plan, the cable is correctly connected. Otherwise, the cable is
incorrectly connected.
2) Crossed pair E1/T1 cable connections
As shown in the following figure, three E1/T1 cables cross each other. In this case, no alarms
are reported but the carried IMA or MP links fail. To check whether E1/T1 cables cross each
other, perform the operations described in the preceding section Incorrect E1/T1 cable
connections.
Issue 01 (2011-08-11)
6-16
3) IMA links that belong to the same IMA group on the local end but belong to different IMA
groups on the peer end
As shown in the following figure, device A is connected to device B using two E1/T1 cables
and to device C using another two E1/T1 cables. These four IMA links belong to the same
IMA group on device A, but belong to two different IMA groups on device B and device C.
Types of services carried on PVCs on the local end must be consistent with those on the
peer end. Bandwidth configurations on the local end must also be consistent with those
on the peer end.
Configured bandwidth of a PVC must not exceed the physical bandwidth of the
corresponding E1/T1 cable or the bandwidth of the corresponding logical port.
Otherwise, some cells may be lost.
Physical bandwidth of an E1/T1 cable or bandwidth of the corresponding logic port must
exceed the sum of the following three rates:
Issue 01 (2011-08-11)
6-17
MCR of the corresponding PVC carrying O&M channels with an ATM service type
of UBR+
PCR of the PVC carrying signaling data with an ATM service type of CBR or
RTVBR
SCR of the PVC carrying speech data with an ATM service type of CBR or RTVBR
Method
Result
Detailed networking
and cable
connection
verification records
Execution results
Execution results
CC test on a PVC
Execution results
Transport network
configurations and
QoS policy
Operation results
Issue 01 (2011-08-11)
6-18
If a large number of ATM cells are lost, the following alarms are reported on the RNC:
z
Users experience poor speech quality or even call drops, and the HSPA data rate is low. IP
over ATM (IPoA) O&M channels transfer MML commands slowly, and the results of the ping
test conducted on these O&M channels show that some packets are lost.
Possible Causes
z
Issue 01 (2011-08-11)
6-19
E1/T1 port configurations are incorrect such as the frame format, coding scheme,
scrambling mode, resistance capability, and slots.
Types of services carried on PVCs on the local end are inconsistent with those of PVCs
on the peer end.
Bandwidth configurations on the local end are inconsistent with those on the peer end.
Troubleshooting Methods
If some ATM cells are lost, conduct a CC test on a PVC, enable the performance monitoring
(PM) function on a PVC, run the RNC MML command DSP AALVCCPFM or LOP VCL,
or ping IPoA O&M channels. For details, see section 6.2.3 "Verification Methods."
The section Troubleshooting Procedure provides guidelines for checking whether faults occur
at the physical, data link, or transport layer.
Troubleshooting Procedure
1. Check whether E1/T1 port configurations are correct, including the frame format, coding
scheme, scrambling mode, resistance capability, and grounding. To query these
configurations, run the RNC MML commands LST E1T1 and DSP E1T1 or the NodeB
MML command DSP E1T1WORKMODE.
Note the following when checking E1/T1 port configurations:
z
The configured resistance capability of an E1/T1 cable must be consistent with its actual
capability. In addition, its resistance capability on the local end must be consistent with
that on the peer end. 75-Ohm E1/T1 cables require grounding while 120 Ohm E1/T1
cables do not.
Frame format, scrambling mode, and coding scheme of an E1/T1 port on the local end
must be consistent with those of the corresponding E1/T1 port on the peer end.
Otherwise, the status of upper-layer links may become abnormal, the alarm ALM-21221
IMA Link Loss of Frame may be reported on the RNC, and the alarm ALM-25823 IMA
Link Loss of Frame may be reported on the NodeB.
If the coding scheme HDB3 is used, no scrambling mode needs to be activated. If the
coding scheme AMI is used, a scrambling mode must be activated; otherwise, the
IMAGRP negotiation will fail.
2. Check whether E1/T1 cable connections are correct, whether E1/T1 cables are correctly
connected and these cables do not cross, and whether inverse multiplexing over ATM (IMA)
links belong to the same IMA group on both the local end and the peer end.
1) Incorrect E1/T1 cable connections
According to the network plan, ports 0 and 1 must be connected to B1 and ports 2 and 3 to B2.
The E1/T1 cables, however, are incorrectly connected, as shown in the following figure. In
this case, E1/T1 cables can operate properly but the carried links fail.
Issue 01 (2011-08-11)
6-20
Adding new links, deleting existing links, or resetting carried links cannot solve the problem.
To check whether an E1/T1 cable is properly connected, disconnect the cable on the local end
and check the port on the peer end that reports an E1/T1 loss of signal alarm. If the port is the
one specified by the network plan, the cable is correctly connected. Otherwise, the cable is
incorrectly connected.
2) Crossed pair E1/T1 cable connections
As shown in the following figure, three E1/T1 cables cross each other. In this case, no alarms
are reported but the carried IMA or MP links fail. To check whether E1/T1 cables cross each
other, perform the operations described in the preceding section Incorrect E1/T1 cable
connections.
3) IMA links that belong to the same IMA group on the local end but belong to different IMA
groups on the peer end
Issue 01 (2011-08-11)
6-21
As shown in the following figure, device A is connected to device B using two E1/T1 cables
and to device C using another two E1/T1 cables. These four IMA links belong to the same
IMA group on device A, but belong to two different IMA groups on device B and device C.
Types of services carried on PVCs on the local end must be consistent with those on the
peer end. Bandwidth configurations on the local end must also be consistent with those
on the peer end.
Configured bandwidth of a PVC must not exceed the physical bandwidth of the
corresponding E1/T1 cable or the bandwidth of the corresponding logical port.
Otherwise, some cells may be lost.
Physical bandwidth of an E1/T1 cable or bandwidth of the corresponding logic port must
exceed the sum of the following three rates:
Issue 01 (2011-08-11)
MCR of the corresponding PVC carrying O&M channels with an ATM service type
of UBR+
6-22
PCR of the PVC carrying signaling data with an ATM service type of CBR or
RTVBR
SCR of the PVC carrying speech data with an ATM service type of CBR or RTVBR
Method
Result
Detailed networking
and cable
connection
verification records
Execution results
Execution results
PVC performance
Execution results
Issue 01 (2011-08-11)
6-23
Information to Be
Collected
Method
Result
Configurations and
QoS policy of the
transport network
Operation results
Meaning
Link type
Type of the test PVC. SAAL links, IPoA PVCs, and AAL2 paths support CC tests.
Type of CC test. CC tests include continuity check tests and loopback tests.
Activation mode
Issue 01 (2011-08-11)
6-24
Parameter
Meaning
Activation direction
If the following alarms are reported when software version RAN11.0 or earlier is used, some
CC cells are lost:
z
The following figure shows that the test PVC is functioning properly:
Issue 01 (2011-08-11)
6-25
5) Notes
Before conducting a CC test on a PVC, ensure that both the local end and peer end support
the test. Otherwise, the test cannot be started.
Issue 01 (2011-08-11)
6-26
Meaning
Link type
Type of the test PVC. SAAL links, IPoA PVCs, and AAL2 paths support the PM
function.
Activation mode
Activation direction
To enable the PM function for a PVC (Adjacent node ID = 150; AAL2 path ID = 1;
Activation direction = BOTH), run the following command:
ACT VCLPM: LNKT=AAL2PATH, ANI=150, PATHID=1, DR=BOTH, BSIZE=D1024,
PMMODE=AUTO;
Run the RNC MML command DEA VCLPM to disable the PM function for a PVC.
To obtain statistic parameter values within a specific period of time, run the RNC MML
command ACT VCLPM five times at an interval of 3 minutes, and save and compare the
execution results.
5) Querying the performance of the test PVC
To query the performance of the test PVC, run the RNC MML command DSP VCLPM, as
shown in the following figure:
Issue 01 (2011-08-11)
6-27
To obtain statistic parameter values within a specific period of time, run the DSP VCLPM
command five times at an interval of 3 minutes, and save and compare the execution results.
Issue 01 (2011-08-11)
6-28
Meaning
Link type
Type of the test PVC. You can query the performance of SAAL
links, IPoA PVCs, and AAL2 paths.
Run the command multiple times at a fixed interval, and save and compare the execution
results. By doing this, you can obtain the number of transmitted, received, and erroneous cells
over the test PVC.
Issue 01 (2011-08-11)
6-29
Run the RNC MML command LST IPOAPVC to locate the PVC that carries the IPoA O&M
channel for the NodeB, as shown in the following figure:
Issue 01 (2011-08-11)
6-30
Run the RNC MML command PING IP with parameters set to appropriate values:
When setting a value for Size of packet, try all the preceding common values to obtain
accurate test results.
3) Analysis of execution results
Issue 01 (2011-08-11)
6-31
As shown in the following figure, the packet loss rate and delay information are displayed in
the execution result:
Meaning
Link type
Type of the test PVC. SAAL links, IPoA PVCs, and AAL2 paths support loopback tests.
Issue 01 (2011-08-11)
6-32
To accurately analyze the PVC quality, run the LOP VCL command multiple times, and save
and compare the execution results.
Issue 01 (2011-08-11)
6-33
AC
Access Class
AMR
Adaptive multirate
ARP
BER
CAC
CC
Connectivity check
CDT
CE
Channel element
CHR
CN
Core network
DSCP
DSP
DSP
FAM
GBR
HSDPA
HSPA
HSUPA
ICMP
IMA
IOS
IPoA
IP Over ATM
KPI
LAC
Layer 2
L2
Issue 01 (2011-08-11)
7-1
LMT
MTU
NRNC
Neighboring RNC
O&M
OMCH
PCHR
PM
Performance monitoring
PVC
QoS
Quality of service
RAC
RNC
RTWP
SAC
SCCP
SCTP
SF
Spreading factor
TCP
TMA
TTL
Time to live
UTRAN
VLAN
Issue 01 (2011-08-11)
7-2