Owc403700 Bsc6900 Wcdma v900r014 Troubleshooting Issue 1.

BSC6900 WCDMA V900R014 Troubleshooting
Confidential Information of Huawei. No Spreading Without Permission
Local end loopback, which means that data goes through a loop within a NodeB (or
RNC) instead of through E1 cables. It is used to check whether the transmission chips
are normal.
After we execute the SET E1T1LOP as REMOTE mode on A side, we can execute DSP
E1T1 on B side to query E1 state, if the state is normal, that means the physical
transmission from A to B is normal, otherwise, it means the transmission is faulty.
Use STP E1T1ONLTST to stop the E1/T1 online BER test and report the test data to the
LMT.
RNC dont support online BER test.
Run STP E1T1OFFLTST to stop the offline test. When the test is stopped, the final
statistics result is reported.
Configure the E1 remote loopback on the local end, and then start the E1 offline
performance test on the remote end. Or configure the E1 physical loopback on the
local end, and then start the E1 offline test on the local end. The test time is one to
sixty minutes.
Online BER test does not affect services,
Offline BER test affect services, but the result is more accurate than that of the online
test.
To conduct the BER test, perform the following steps:

1) Use the STR E1T1TST command to start the BER test.
2) Use the DSP E1T1TST command to query the test result.
3) Use the STP E1T1TST command to stop the test.
Configure the E1 remote loopback on the local end, and then start the E1 offline
performance test on the remote end. Or configure the E1 physical loopback on the
local end, and then start the E1 offline test on the local end. The test time is one to
sixty minutes.
Once the function is activated, the continuous check on the VCL persists until it is
deactivated. This function operates at the ATM F5 layer through OAM cells. Therefore,
the ongoing service will not be affected.
You can run this command to activate the continuous check on VCL, and then run
DSP VCLCC to query the operation result, and finally run DEA VCLCC to deactivate
the continuous check on VCL.
This command is applicable to the AEUa, AOUa, AOUc, UOIa(ATM) and UOIc boards.
The continuous check function applies only to the VCL that bears the SAAL link, IPoA
PVC, or AAL2 path.
The continuous check can be activated on the SAAL link only when the upper-layer
application bearer such as NCP/CCP/ADJNODE/MTP3LNK is configured.
The continuous check operation succeeds only when the continuous check is also
activated on the peer VCL.The operation on the NodeB side is activated passively.
Otherwise, the system regards the VCL to be faulty, and the VCL CC Activation Failure
alarm is generated.
Either CC or LOOBACK can be activated on each VCL at a time.
The VCL should have been configured before the command was executed. Only the
VCL that bears the SAAL link, IPoA link and AAL2 path can support CC state query.
Even if the CC function of the VCL is not activated the CC state still can be queried,
because the CC function can be activated passively, that is, it can be activated by other
network nodes.
If the CC type is LOOPBACK, the query result will show loopback delay information.
You can run this command to activate the performance monitoring on the VCL, and
then run DSP VCLPM to query the operation result, and finally run DEA VCLPM to
deactivate the performance monitoring on the VCL. This command is applicable to the
AOUc and UOIc boards.
The performance monitoring function applies only to the VCL that bears the SAAL link,
IPoA PVC, or AAL2 path.
The performance monitoring can be activated on the SAAL link only when the upperlayer application bearer such as NCP/CCP/ADJNODE/MTP3LNK is configured.
If the backplane version of subrack where the board is located ( it can be queried by
running DSP BRDVER) is VER.A or VER.B, the MSP 1+1 Unidirectional Protection
Switching mode does not support VCL PM; If the backplane version is VER.C or later
versions, the MSP 1+1 Unidirectional Protection Switching mode supports VCL PM.
Whenever PM is performed, it is advisable to insure that the corresponding CC
mechanism is activated during the overall performance assessment period. This allows
a continuous monitoring of the availability of the connection portion during that
measurement period. CC need to be activated before starting the PM process.
RNC and NodeB support this function.
Use this command to query the result of the performance monitoring (PM) of the
virtual channel link (VCL). The query result includes the activation status of the PM
function, statistics of the cell loss, statistics of the cell misinsertion and application of
the VCL.
You cannot obtain the VCL statistics if the VCL to be queried is in deactivated state.
The VCL whose PM status to be queried must be already configured. Only the PM
status of the VCL that carries the SAAL link, IPoA PVC and AAL2 path can be queried.
The PM function can be activated passively, that is, it can be activated by other
network nodes. Therefore, even if the PM function for the VCL is not activated, the
PM status can still be queried.
The working status measurement result of the AAL terminal corresponding to a

specified VCC can be obtained by AAL VCC performance measurement. The result
information includes: number of bytes correctly received/transmitted, number of
packets correctly received/transmitted, number of cells correctly received/transmitted,
number of error bytes received/transmitted.
NodeB dont support this function.
Use this command to query the performance measurement result of a specified AAL
VCC. This command is applicable to the AEUa,AOUa,AOUc,UOIa(ATM or IP) and UOIc
boards.
Query the AAL performance measurement of the VCL terminal corresponding to a
specified VCC. The working status measurement result of the AAL terminal
corresponding to a specified VCC can be obtained by AAL VCC performance
measurement. The result information includes: number of bytes correctly
received/transmitted, number of packets correctly received/transmitted, number of
cells correctly received/transmitted, number of error bytes received/transmitted.
Use this command to ping a destination IP address from a specified source IP address
of a board to check the connectivity of the IP layer between the local end and the peer
end.
This command is applicable to the PEUa, AEUa, AOUa, AOUc, UOIa(ATM or IP), FG2a,
GOUa, POUa, UOIc, FG2d, FG2c, GOUd, GOUc and POUc boards.
The source IP address must be the local IP address of the PPP link of the
PEUa/POUa/UOIa(IP)/POUc board, the local IP address of the MP group of the
PEUa/POUa/POUc board, the IP address of the Ethernet port of the
FG2a/GOUa/FG2d/FG2c/GOUd/GOUc board, the IP address of the Trunk group of the
FG2a/GOUa/FG2d/FG2c/GOUd/GOUc board, the local IP address of the IPoA PVC of
the AOUa/AOUc/AEUa/UOIa (ATM)/UOIc (ATM) or the device IP address of the board.
After configure the IPoA link used as an OM channel when ATM transmission is
adopted, Ping is used to check the OoS of ATM transmission.
This function is used to monitor the time difference between RNC Frame Number
(RFN) and NodeB Frame Number (BFN) of the specified cell and the time taken for
node synchronization. By performing this task, you can observe the float between the
RFN and BFN and transfer delay in real time. If the difference between RFN and BFN
varies too rapidly, you can infer that there are some problems on the transmission
between the BSC6900 and the NodeB.
This command can obtain the statistic of the parameters, such as Link Availability
Status, Number of received Unicast frame, Rx correct bytes, Tx correct bytes and so
on.
PING principle
PING works in this procedure: The system sends a PING request to the
destination. If the connection to the destination network is good, the host
computer of the destination responses to the source host computer upon
receiving the PING request.
If the network is found faulty through PING, you can use TRACERT to locate
the fault.
The output of PING is the PING response from the destination. If no response
is received within the limit, the output is "Request time out". Otherwise it
outputs the message size in bytes, message number, TTL, and response time.
The final statistics include the number of sent messages, number of received
messages, percentage of the non-response messages, and the minimum,
maximum and average response time.
If the result is Request time out, it means transmission is disconnected.

If Request time out exist with probabilities, it means packets loss exist.
If the value of time is big, it means transfer delay is high.
If the difference between the value of time is large, it means vibration exist.
Trace Principle
The process for running is as follows: The source computer sends a data
packet with the TTL as 1. The first hop responds with an ICMP error message
indicating that the packet is not sent due to TTL timeout. The data packet is
sent with the TTL as 2, and then likewise the second hop responses TTL
timeout. The process is carried on until the data packet reaches the
destination. The purpose of these procedures is to record every original
address of the ICMP TTL timeout message. These addresses form the route for
sending an IP packet to the destination.
If the network is found faulty through PING, you can use TRACERT to locate
the fault.
If the route address in the response is 0.0.0.0, it means that the test passed
through a route over board.
The output of TRACERT includes the IP addresses of all the gateways that the
data packet has gone through from the source to the destination, and the
response duration for each gateway. If the response time expires, it outputs a
star sign "*".
If network is normal, every next hop is display.

If network is abnormal, destination ip is not reachable, and stop at the faulty segment.
Princilpe
RNC sends ICMP or UDP packets to the destination continuously through the
IPPATH that activate the function of IPPATH ping. If the IPPATH to the
destination network is normal, the destination send responses to the RNC. And
the RNC will receive returning packets.
Result Analysis of IPPATH testing
If the RNC cant receive returning packets, it mean the IPPATH is abnormal,
and will reportPath Faultalarm.
Principle
After the IP loopback test is started, the DSP sends loopback packets to the
NodeB in a specified period and then the NodeB returns the loopback packets
to the DSP
You can determine the connectivity and link quality according to the received
loopback packets
NodeB support IP loopback operation, but dont support IP loopback test.
RNC support IP loopback test only.
Use this command to set remote loop of IP level.

The command can be executed only when the transmission board is in normal
operation.
The loop back mode can be overwritten.
The command only take effect with the IP packets of the UDP protocol.
This command can not be executed with IP tracing at the same time.
Some services may be interrupted.
After starting the remote loop of IP level on NodeB, IP Remote Loopback would be
reported.
Use this command to display the remote loop mode of IP level.
Use this command to start the IP loopback test. The function is to check the
connectivity between DSP and the interface boards or the peer equipments.This
command is applicable to the FG2a, GOUa, FG2c and GOUc boards.
Note
Only one IP loopback test can be started for one DSP.
This command is used to start the IP loopback test on the Iub or Abis interface.
When the parameter LOPT is set as REMOTE_LOOP, you need to enable the IP
remote loopback function by setting IP address and port number on the
NodeB. Otherwise, the function is unavailable.
The quaternary group information (Local IP address, Peer IP address, Src

Port NO., and Dst Port NO.) set in each IP loopback detection cannot be the
same.
Use this command to query the result of the loopback test at the IP layer.
The IP loopback test should be enabled on the DSP to be queried.
Princilpe
The principle of IP PM is similar to that of ATM OAM PM. One end sends an
FM (Forward Monitoring) message periodically, the other end responds to the
PM with the BR (Backward Reporting) message as soon as it receives the FM
message.
With FM and BR, packet loss rate of link and jitter could be calculated
accordingly.
IP PM is Huawei private protocol. RNC and Node B must support this feature
simultaneously. FG2a/FG2c, GOUa/GOUc of BSC6900.
Note
The IP path to be activated with the IPPM detection function must be

configured, and all the IPPMs corresponding to the IP path are activated.
The IP path to be activated with the IPPM must be configured on Iub or Abis
interface.
If several IPPATH have same local IP and peer IP, but have different VLANID,
some IPPM on NodeB or BTS may fail to be activated.
Use this command to query IPPM State. This command is applicable to the FG2a,
GOUa, FG2c and GOUc boards.
Use DEA IPPM to deactivate all the IPPMs corresponding to an IP path on the RNC.
Use RMV IPPMSESSION to remove an IPPM session on the NodeB.
E1/T1 is a shortened form of the two different systems PCM30 and PCM24 in digital
system. The transmission rate of E1 link is 2,048 kbit/s, and that of T1 link is 1,544
kbit/s.
The type of E1 link can be E1_DOUBLE_FRAME or E1_CRC4_MULTI_FRAME
E1_DOUBLE_FRAME represents the link with dual-frame structure.
E1_CRC4_MULTI_FRAME indicates the link with multi-frame structure. The

E1_CRC4_MULTI_FRAME format is usually applied. Links of
E1_CRC4_MULTI_FRAME type can perform error checking, which may greatly
reduce the error rate of synchronous frame extraction.
The type of T1 link can be T1_EXTENDED_SUPER_FRAME or T1_SUPER_FRAME type
T1_SUPER_FRAME represents super frame.
T1_EXTENDED_SUPER_FRAME indicates extended super frame. Usually, the

T1_EXTENDED_SUPER_FRAME format is applied. Links of
T1_EXTENDED_SUPER_FRAME type can also perform error checking.
The coding types of E1 link are HDB3 and AMI
HDB3 is usually applied. HDB3 represents high-density bipolar code. It is not

easy to be interfered, and the transmission distance is about several kilometers.
The coding types of T1 link are B8ZS and AMI.
B8ZS is usually used. It helps prevent clock signals from being lost, but AMI
cannot perform such function.
Configuration Mismatch
Frame Structure, Line Code, and Scramble Switch should be consistent with
the peer equipment respectively.
For a single link or port, its type cannot be changed from E1 to T1 or from T1
to E1. All the links must be set to the T1 or E1 type uniformly.
If a link is used, its type cannot be changed from E1 to T1 or from T1 to E1.
The change from E1 to T1 or from T1 to E1 performed on the RNC AOU/POU

takes effect only after the board is reset.
Impedance Fault
Function of NodeB E1/T1 DIP Switch
the working mode: E1 or T1
Set matched impedance: 75(E1 Coaxial cable), 120(E1 Twisted pair cable),
100( T1 Twisted pair cable)
Set the grounding status: Coaxial cable with the outer layer of its TX and RX
ends grounded (default state).
When the coaxial cable is used, the outer layer of the TX end is usually
grounded. For example,
When device A connects to device B, the outer layer of the TX ends on

both devices must be grounded.
If the outer layer is not enabled on device B, the outer layer of both
RX and TX ends on device A must be grounded.
When the twisted pair cable is used, no need the grounding.
RNC MML: DSP E1T1
Use this command to query one or multiple E1/T1 ports for the working state
and attributes, including port running state, port type, TX frame format,
expected RX frame format, TX line coding mode, RX line coding mode,
loopback type, highway data rate on the BSC6900 side, line impedance,
communication distance, clock mode, code violation count, framing error
count, CRC error count, E-bit error count, Sa6 error count, multiframe periods
in asynchronous state, changes of frame or multiframe alignment, whether to
enable scrambling, connected node information, whether the E1/T1 port is
used and site name.
NodeB MML:DSP E1T1
Use this command to display E1/T1 port status, E1/T1Work Mode, Clock Mode,
Line Code, Frame Format, Loopback Mode, Line Impedance.
Loop back mode:

NOLOOP (loopback mode is cancelled.)
REMOTE (Remote loopback, which means that data goes through a loop of E1 cables
between NodeB and RNC. it is used to check whether the E1 cables are normal.)
Default value: NOLOOP
LOCAL (Local end loopback, which means that data goes through a loop within a
NodeB (or RNC) instead of through E1 cables. It is used to check whether the
transmission chips are normal.)
After we execute the SET E1T1LOP as REMOTE mode on A side, we can execute DSP
E1T1 on B side to query E1 state, if the state is normal, that means the physical
transmission from A to B is normal, otherwise, it means the transmission is faulty.
NodeB MML: STR E1T1ONLTST

Use this command to start the E1/T1 online performance test.
A maximum of three users can start the online performance test simultaneously on each
port.
You cannot start an online performance test at the port where an offline performance
test is already started. Conversely, you cannot start an offline performance test at the
port where an online performance test is already started.
You can start the online performance test on multiple ports on the same board.
If the online performance test encounters a turnover, the number of error bits after the
turnover is reported.
An online performance test is applicable to a transmission link working properly and
having error bits. You are advised to check the E1/T1 link status before starting an online
test. If the link is faulty, you are not advised to start an online performance test. In this
case, you can start an E1/T1 offline performance test and rectify the E1/T1 link fault.
When Period Report Switch is set to ON, the test result within a second is reported every
other second. When Period Report Switch is set to OFF, you can run the STP
E1T1ONLTST command to obtain the test result.
NodeB MML: STP E1T1ONLTST
Use this command to stop an E1/T1 online performance test and report the test data to
the LMT.
You cannot perform any operations on the E1/T1 online performance test started by
another user.
This command takes effect only when the test of the corresponding online performance
data has been started.
NodeB MML: STR E1T1OFFLTST

Use this command to start an E1/T1 offline BER test on the transmission board.
An E1/T1 offline performance test is used to determine the BER of an E1/T1 link. Before
starting the test, set the E1/T1 port at the peer end to remote loopback or set the E1/T1
port at the local end to local loopback or physical loopback. The test is invalid if no
loopback is specified.
When the E1/T1 port at the peer end is set to remote loopback or physical loopback is
implemented at the local end, there is a possibility that the physical layer cannot detect
the existence of the physical loopback due to bit errors on the link. As a result, you may
run the DSP E1T1 command to check whether the associated E1/T1 ports are in physical
loopback state. Note that the E1/T1 offline performance test can be started only when
physical loopback is in effect implemented.
A loopback is specified for the E1/T1 offline performance test. This may disrupt services.
The E1/T1 high BER detection stops when an E1/T1 offline performance test is started.
In this case, the status of the E1/T1 high BER errors is not updated.
When an E1/T1 offline performance test is started, a Pseudo-Random Binary Sequence
(PRBS) is transmitted on the E1/T1 link. The PRBS is a type of test data that does not
have a frame format. Therefore, frame synchronization loss may occur on the E1/T1 link.
If Period Report Switch is set to ON, the test result is reported every other second. If
Period Report Switch is set to OFF, you can obtain the test result after the test duration
expires or after you run the STP E1T1OFFLTST command.
After the test duration expires, the total BER and total number of error bits within the
test duration are reported irrespective of whether Period Report Switch is set to ON.
Each time only one user can start the E1/T1 offline performance test on an E1/T1 port. If
multiple users start such tests on an E1/T1 port, a failure will be reported.
RNC MML: STR E1T1TST

Use this command to start an E1/T1 Bit Error Ratio (BER) test on the AEU, PEU, AOU,
and POU. The BER test may interrupt the service carried on the port.
Before starting the BER test, configure the local loopback at the local end or configure
the remote loopback at the peer end or connect the TX end to the RX end by using
the loopback connector.
The accuracy of testing results is limited because the test tool is not a specialized tool
for the BER test. Thus, the tool is used to test only the BER severity. To obtain accurate
BER data, use a tool specialized for the BER test.
The loopback test and BER test cannot be performed simultaneously.
An E1/T1 port must be set to the loopback state before the BER test is started on the
E1/T1 port or before the timeslot-level test is started on the E1/T1 port.
One BER test can be started for a board at a time.
To conduct the BER test, perform the following steps:
1) Use the STR E1T1TST command to start the BER test.
2) Use the DSP E1T1TST command to query the test result.
3) Use the STP E1T1TST command to stop the test.
After the BER test is stopped, the DSP E1T1TST command can still be used to query
the last test result.
RNC MML: STP E1T1TST
Use this command to stop an E1/T1 Bit Error Rate (BER) test.
Query first, Handling second
To Query the E1/T1 alarm and use DSP E1T1 to query the E1/T1 state first, if
the abnormal state of E1/T1 have been found, handle the fault.
Loop back first, Test second
If the E1/T1 state is abnormal, just need use DSP E1T1 to query the state, no
need test BER of it. If the High BER alarm appeared, use online or offline test
function.
Online test first, Offline test second
Because the Offline interrupt the running of link, so Online test is the first
choice
Far first, Near second
Loop back distance should be long at first, if in the case, the link is abnormal,
decrease the loopback distance and query link state again.
BGN
BGNAK
BGNREJ
END
ENDAK
RS
RSAK
ER
ERAK
SD
POLL
STAT
USTAT
Initial link establishment

Acknowledgment to initial link establishment
Rejection to initial link establishment
Link interruption
Acknowledgment to link interruption
Request of synchronization
Acknowledgment to synchronization
Request of error recovery
Acknowledgment to error recovery
Upper layer data packet
State request
State response
Packet loss report
The SAAL faults are as follows: outgoing unidirectional communication, incoming

unidirectional communication, selective packet loss, no communication, and irregular
packet loss.
Run the LST SAALLNK command to check whether the configuration at both ends is
correct.
Run the DSP SAALLNK command on the both end to display whether the upper layer
application (MTP3b or NCP/CCP) of the SAAL is configured.
Start the SAAL/MTP3b/SCCP tracing. Analyze the fault phenomenon and possible
causes through the tracing.
The following sections describe the locating of four faults that frequently occur.
Enable the SAAL tracing on the RNC. (Trace -->UMTS Service -->Interface Trace ->SAAL)
In this scenario, the SAAL link on the RNC is not configured with the upper layer
application, however, the peer SAAL link is configured with the upper layer
application.
In this scenario ,the possible causes:
The SAAL link on the NodeB is not configured with the upper layer application
The unilateral communication
The cause may be that there are a large amount of packets lost, therefore, the other
end cannot receive the packets and then triggers the release.
DSP AALVCCPFM
Use this command to query the performance measurement result of a specified AAL
VCC. This command is applicable to the AEUa, AOUa, AOUc, UOIa(ATM or IP) and
UOIc boards.
Query the AAL performance measurement of the VCL terminal corresponding to a
specified VCC. The working status measurement result of the AAL terminal
corresponding to a specified VCC can be obtained by AAL VCC performance
measurement. The result information includes: number of bytes correctly
received/transmitted, number of packets correctly received/transmitted, number of
cells correctly received/transmitted, number of error bytes received/transmitted.
The AAL2PATH unavailable fault is usually result in the establishment failure of the
common channel in the cell, the establishment failure of the RRC connection, and the
establishment failure of the CS service. By nature, these faults are establishment
failures of the QAAL2.
Check the data configuration related to the AAL2PATH
Check whether the VPI/VCI and AAL2PATH ID on both ends are consistent.
You can query the data on the RNC and NodeB by running the LST
AAL2PATH command on the LMT.
Check whether the physical port of the AAL2PATH on the RNC is configured
with the corresponding port controller, and whether the port controller (SPU
sub-system) is working normally.
Check whether the AAL2 Route configuration is correct
If the AAL2PATH of the IUCS is unavailable, run the LST AAL2RT command
on the LMT to check whether the destination ATM address configured on the
RNC is consistent with the ATM address contained in the RAB message sent
from the CN.
If the IUB port is used, check whether the ATM address contained in the
RL_SETUP_RSP message sent from the NodeB is consistent with the ATM
address configured in the ADD UNODEB command.
Note that in the versions later than V2R10, the AAL2 route from the IUB port
to the NodeB is not configured manually on the RNC. The system automatically
configures the route based on the ATM address in the ADD UNODEB
command.
If the IUR port is used, check whether the ATM address contained in the
RNSAP_RL_SETUP_RSP message sent from the DRNC is consistent with the
ATM address configured in the ADD UNRNC command.
Check the AAL2 PATH state and bandwidth configuration
On the RNC, run the DSP AAL2PATH command through the LMT to query
whether the AAL2PATH is available, and whether the AAL2PATH is blocked by
the local end or peer end. If the AAL2PATH is blocked by the local end or peer
end, you must unblock the AAL2PATH.
Check whether the remaining bandwidth and CID of the AAL2PATH are
sufficient. If the remaining bandwidth or CID is insufficient, the AAL2 access
fails.
Check whether the physical link of the AAL2PATH and the PVC are normal
Check whether the physical link of the AAL2PATH generates the relevant
alarm. If the alarm is generated, you must process the alarm firstly.
If the data configuration and physical link are normal, you must check whether
the PVC layer is normal.
If both ends of the connection support the CC check, you can enable the CC
check of the PVC corresponding to the AAL2PATH. On the NodeB, the CC
check is enabled by default.
If the CC check is not supported on the both ends or one end of the
connection, you can set the PVC upper layer carried by the AAL2PATH to the
SAALLNK, and then query the packet receiving and transmitting of the PVC by
running the DSP AALVCCPFM command.
Enable the QAAL2 tracing in the interface tracing on the RNC (Trace -->UMTS Service ->Interface Trace Task -->QAAL2)and enable the IUB port tracing on the NodeB (the
ALCAP message must be selected).
The QAAL2 establishment failure occurs in the following cases:
The local end does not send the QAAL2 establishment request message. In this
case, you must check the parameter settings on both ends.
The peer end does not return the QAAL2 establishment verification message or
the QAAL2_Release_Confirm message. In this case, you must check the specific
cause value. For example, if the bandwidth is insufficient, you must check the
bandwidth configuration on the peer end.
Introduction to Ethernet, Fast Ethernet and Gigabit Ethernet

It is nearly impossible to discuss networking without the mention of Ethernet, Fast Ethernet and
Gigabit Ethernet. But, in order to determine which form is needed for your application, its
important to first understand what each provides and how they work together.
A good starting point is to explain what Ethernet is. Simply, Ethernet is a very common method
of networking computers in a LAN using copper cabling. Capable of providing fast and
constant connections, Ethernet can handle about 10,000,000 bits per second and can be used
with almost any kind of computer.
While that may sound fast to those less familiar with networking, there is a very strong demand
for even higher transmission speeds, which has been realized by the Fast Ethernet and Gigabit
Ethernet specifications (IEEE 802.3u and IEEE 802.3z respectively). These LAN (local area
network) standards have raised the Ethernet speed limit from 10 megabits per second (Mbps)
to 100Mbps for Fast Ethernet and 1000Mbps for Gigabit Ethernet with only minimal changes
made to the existing cable structure.
The building blocks of today's networks call out for a mixture of legacy 10BASE-T Ethernet
networks and the new protocols. Typically, 10Mbps networks utilize Ethernet switches to
improve the overall efficiency of the Ethernet network. Between Ethernet switches, Fast
Ethernet repeaters are used to connect a group of switches together at the higher 100 Mbps
rate.
However, with an increasing number of users running 100Mbps at the desktop, servers and
aggregation points such as switch stacks may require even greater bandwidth. In this case, a
Fast Ethernet backbone switch can be upgraded to a Gigabit Ethernet switch which supports
multiple 100/1000 Mbps switches. High performance servers can be connected directly to the
backbone once it has been upgraded.
The UTRP2 provides two 10M/100M/1000M Ethernet optical ports, performs functions
of the MAC layer, receives and transmits data on Ethernet links, and analyzes the MAC
address.
The UTRP9 provides four 10M/100M/1000M Ethernet electrical ports and performs
the functions of the MAC layer and physical layer.
FE Ports on the WMPT
Label
Connector Type
Description
FE0
RJ45 connector
FE electrical port
FE1
SFP connector
FE optical port
As an interface board, the FG2c board supports IP over Ethernet transmission
Provides twelve channels over FE ports or eight channels over FE ports and four
channels over GE ports
Provides the link aggregation function at the MAC layer
Provides the routing-based backup and load sharing
Supports the Iu, Iur, and Iub interfaces

As an optical interface board, the GOUc board supports IP over Ethernet transmission
Provides four channels over GE ports
Provides the routing-based backup and load sharing
Supports the Iu, Iur, and Iub interfaces
Checking the cable and connector

Checking the cable connection and connector. The cable length can not exceed 100m.Replace
the cable and check the alarm.
Checking the parameter of the FE
Use DSP ETHPORT to check the port state, use LST ETHPORT to query the parameter
of two peers, assure the parameter used are same.
Recommended parameter:
Port speed
Duplex Mode
Priority
100M (1000M for GE)
Full
High
100M (1000M for GE)
AUTO
Medium
AUTO
AUTO
Low
Fault Isolation
1. Use PC connect with NodeB, to check the alarm is cleared or not.
2. Use PC connect with Peer, to check the PCs ETH port is On or not.
3. If step1 s alarm is cleared and step2s LED is OFF, then the peer side may be fault.
4. If step1s alarm is not cleared and step2s LED is ON, the NodeB port may be fault. In
this case, use RST ETHPORT and RST BRD to reset the port and broad (Must use MML
to reset), then check the chip alarm, if the chip alarm appear, replace broad.
Note: some PCs ETH ports adaptive capability is not good, we can use several PC to test.
[RNC MML] PING IP
[NodeB MML] PING
The faults in the data link layer include: The VLAN is faulty, The transmission network
is faulty.
Generally, the maximum transmission distance of the Ethernet cable is within 100 m.
Note:
The port rate and auto-negotiation mode are the direct parameters for two
interconnected devices, for example, they are the interworking parameters
used by the NodeB to connect another device directly.
The meaning of consistent negotiation parameters: Take the port rate as an
example, if the port rate on one end is 100 Mbit/s, the port rate on the other
end is also 100 Mbit/s, and the auto-negotiation modes on both ends are
AUTO. The duplex mode is configured in the similar way.
We recommend that: On the both ends, the rate is 100 Mbit/s (for the GE, the
rate is 1000 Mbit/s)
Use this command to query the working status and traffic statistics of an Ethernet port.
Use this command to list the parameters of an Ethernet port.
You can use this command to display the status of an Ethernet port, which includes
Max Transmission Unit, Speed, MAC address, Duplex, Physical layer status, and the
traffic information. If there are multiple ports, only the primary information of the
ports is displayed. If there is only one port, the port information is displayed in detail.
Note: The port adaptation of some PCs is not good. You can test several PCs and
choose the best one, or perform the test by connecting the service port and
maintenance port
Firstly, the RNC or NodeB query the next hop MAC address (the corresponding ARP
entry) based on the IP route. With the ARP entry, the RNC or NodeB sends the packets
to the ICMP, SCTP, or UDP. If the RNC does not obtain the ARP entry, the RNC sends a
ARP request broadcast packet and ask for the next hop MAC address
If the RNC and NodeB adopt layer 2 networking, the ARP request is sent to the NodeB
or RNC. If the network adopts layer 3 networking, the ARP request is sent to the
gateway.
If the transmitting endpoint has the ARP entry, the ARP request packet is not
transmitted.
If the peer ARP entry is available on both ends, you can infer that the fault is not
caused by the ARP entry
If the ARP entry is available on only one end (assume that the ARP entry is available on
the RNC only), after you run the ping command and then run the DSP ARP command
on the NodeB, if the ARP entry is still unavailable, you must check the VLAN
configuration on the RNC
If the ARP entry is unavailable on both ends, the test procedure is as follows:
Run the ping command on the RNC, and then query the ARP entry on the
NodeB, if the ARP entry is available, you can infer that the ARP request sent by
the RNC can be received by the NodeB. Run the DSP ARP command to query
the ARP entry on the RNC. If the ARP entry is available, you can infer that the
fault is not caused by the ARP. If the ARP entry is unavailable, you can infer
that the ARP response on the NodeB is faulty. You must check the VLAN
configuration on the NodeB.
Run the ping command on the NodeB, and then query the ARP entry on the
RNC. The description of the query result is similar to the preceding description.
After you run the ping command on the RNC and NodeB, if the ARP entry is
not available on the peer end, you can infer that the transmission network may
be faulty.
Use this command to ping a destination IP address from a specified source IP address
of a board to check the connectivity of the IP layer between the local end and the peer
end.
The source IP address must be the local IP address of the PPP link of the
PEUa/POUa/UOIa(IP)/POUc board, the local IP address of the MP group of the
PEUa/POUa/POUc board, the IP address of the Ethernet port of the
FG2a/GOUa/FG2c/GOUc board, the IP address of the Trunk group of the
FG2a/GOUa/FG2c/GOUc board, the local IP address of the IPoA PVC of the
AOUa/AOUc/AEUa/UOIa (ATM)/UOIc (ATM) or the device IP address of the board.
You can run this command again only after the execution result has been returned.
This command is unavailable on the standby port.
To stop a consecutive ping operation, press CTRL+Q.
You can use ARP to display the ARP table of the system to check whether an ARP
procedure succeeded.
The output of ARP includes the IP address and the MAC address.
Function
You can use PING to check the network connections and the network quality.
Yon can use Ctrl^Q to Stop PING.
The NodeB stop PING during the BOOTP process.

Note
If the PING packet is bigger than MTU and the peer device does not support
PING packet fragmentation, or the IP transport network shields PING packets,
PING will be failed or expire. The IP addresses of the whole network broadcast,
0.x.x.x, 127.x.x.x, Type D, and Type E are illegal addresses.
The Source IP address of the command PING can be 0.0.0.0, OMCH local
address, or the active interface address (including IP address, PPP, and ML PPP
local address). When the IP address 0.0.0.0 is input, the most matched route
to the destination IP address will be automatically assigned, and the IP address
of the outbound port which corresponds to the route will be used as the
source IP address, from which the PING packets will be send.
The parameter of SRC IP must be configured when the command of PING is

operated over board(IP address 0.0.0.0 will make the PING operation failure).
Run the ADD VLANMAP command to configure the VLAN for the next hop data. The
next hop address can be configured with multiple VLANs.
Run the ADD VLANCLASS to add a VLAN table entry to a VLAN group.
Run the LST VLANCLASS to list all the configured VLAN priority mapping
relationships.
When the ARP entry is normal, the troubleshooting procedure is as the

troubleshooting procedure of FE faults in IP layer.
The FE faults in IP layer are usually caused by the faulty routes.
You must run the ADD VLANID command to configure the VLAN to the address to
be pinged if the VLAN must be configured and the Ping switch of the IPPATH is
disabled.
Use this command to query the real-time information on an IP route carried by the
interface boards.
Use this command to list the configuration of an IP route.

You can use this command to list all the routes from a specified Subrack No. to a
certain destination network address.
You can use this command to query the information about all reachable IP routes.
You can use this command to list the information about all the static IP routes.
Note
The destination IP address cannot be the local PPP IP address of the

PEUa/POUa/UOIa(IP)/POUc board, the local MP group IP address of the
PEUa/POUa board, the Ethernet IP address of the FG2a/GOUa/FG2c/GOUc
board, the Trunk group IP address of the FG2a/GOUa/FG2c/GOUc board or the
equipment IP address of the board.
After you run this command on a board for once, the command can be
executed on the board again only after the result of the previously executed
command is returned.
The TRC IPADDR command is not supported by the standby port.
To stop the running of the TRC IPADDR command, press Ctrl+Q.
Note
Use this command to start route tracing. Route tracing obtains the information
about the gateways on the host-to-destination route by sending test packets
on the route. By running this command, you may check whether the route is
reachable and locate the position where a network connection failure occurs.
The IP addresses of the whole network broadcast, 0.x.x.x, 127.x.x.x, Type D,
and Type E are illegal addresses.
The command of TRACERT isn't supported in the over board instance.
This command cannot be used with the PING , CFMTRACE , or CFMPING
command.
You can press Ctrl+Q to stop running the TRACERT command.
The SCTP faults are classified into the following two kinds:
The SCTP faults caused by no communication or unilateral communication, for

example, the data is sent to the peer end but no response is retuned; the peer
end data cannot be received.
The SCTP faults caused by link interruption, for example, the SCTP intermittent
fault, and SCTPLNK down.
To remove the SCTP faults, you must often use the SCTP message tracing. The SCTP
information chunk falls into many types, such as INIT, INIT ACK, DATA, SACK, ABORT,
SHUTDOWN, ERROR, COOKIEECHO, and HEARTBEAT. Figure shows the normal SCTP
interactive messages.
Check the transmission
Run the ping command to ping the peer address. Check whether the ping
action is successful. If the ping action is not successful, check the route and the
transmission network.
Check the interworking parameter settings
Run the LST SCTPLNK command on the both ends. Check whether the SCTP
interworking parameters are consistent with those on the peer end. The MTU
values on the both ends must be smaller than or equal to the MTU value of the
transmission network.
Check the upper layer application configuration
Run the LST SCTPLNK command on the both ends. Check whether the SCTP
upper layer applications (such as the NCP, CCP, and M3UA) are configured.
Enable the SCTP tracing
If no problem is found in the preceding operations, you can enable the SCTP
tracing on the LMT. Compare the tracing message with the normal interactive
message, and determine whether the packet loss occurs and the position of
the packet loss.
The IPPATH unavailable fault is usually result in the establishment failure of the
common channel in the cell, the establishment failure of the RRC connection, and the
establishment failure of the CS/PS service.
If there is no communication in the transmission path, and the ping check of the
IPPATH is not enabled, the RNC does not report the IPPATH unavailable fault.
Check the data configuration related to the IPPATH
Check the IPPATH parameter settings
On the RNC and NodeB, run the LST IPPATH command through the LMT
to check whether the local IP address and peer IP address are configured
correctly.
Check the IP PATH state and bandwidth configuration
On the RNC, run the DSP IPPATH command through the LMT to check
whether the IPPATH is available and whether the remaining bandwidth is
sufficient. If the IPPATH is unavailable or the remaining bandwidth is
insufficient, the IPPATH access fails.
Check whether the IP route is configured correctly
The route on the intermediate route device and the core network and the
route on the NRNC not provided by Huawei must be checked with the
assistance of the customer.
On the RNC and NodeB, run the LST IPRT and DSP IPRT commands through
the LMT to check whether the routing tables of the interface board and main
control board contain the routes to the IPPATH peer address.
Run DSP FAMDATA(BT=SCU, TNAME=TIPROUTETBL) to check the routing

table on the XPU/SCU of the RNC.
If you cannot find the outgoing port when setting the IPPATH on the RNC
onsite, you must configure the corresponding IP Route and then add the
IPPATH.
Step 1 Check the configuration and connection
Check the connection.
If the backup mode at both ends is not the same, modify the local or the peer end
backup mode to the 1+1 or 1:1 mode.
If the restoration mode at both ends is the same, modify the local or the peer end
restoration mode to revertive or non-revertive. In the 1:1 backup mode, only the
non-restorable mode is optional.
If the switching mode at both ends is not the same, modify the local or the peer
end switching mode to single-ended switching or dual-ended switching. Huawei
RNC products do not support single-ended switching in the 1:1 backup mode.
If the MSP is deactivated, activate the local or the peer MSP.
If the working channel and the protection channel are inversely connected,
reconnect the optical fiber.
If one end is locked for protection, cancel the protection lock at the local or the
peer end.
Step 2 Check optical interface alarms
Check whether a fault alarm related to the optical interface is generated.
When the SF alarms (such as the LOS, LOF, MS_RDI, and MS_AIS fault alarms
related to the optical interface and the APS fault alarms related to the standby
board) are generated, the RNC automatically triggers switching.
Check whether the MSP switching alarm maps the optical interface switching
alarm.
Step 3 Check whether the MSP switching alarm is generated due to the local or the peer
end fault. If the alarm is generated due to the peer end fault, check the peer end devices.
The RNC OM network is divided into the external network, internal network, MPS
network, MPS-EPS network, and EPS network. Each subnet is responsible for certain
functions.
External Network
The external network refers to the network between the OMU board and the
OM console (LMT or M2000). The external network provides the interface for the
OM console to access the OM subsystem.
Internal Network
The internal network refers to the network between the OMU board and the
SCU board in the MPS subrack. The internal network provides a bridge for the
communication between the OMU and the host.
MPS Network
The MPS network refers to the OM network between the SCU board in the MPS
subrack and the other boards in the same subrack. The backplane in the MPS
subrack is used to connect entities on this network.
MPS-EPS Network
The MPS-EPS network refers to the network between the SCU board in the MPS
subrack and the SCU in each EPS subrack. The connections between the SCU
board in the MPS subrack and the SCU board in each EPS subrack through
Ethernet cables comprise the MPS-EPS network. Through this network, the RNC
can transmit the OM information to the SCU board in each EPS subrack through
the SCU board in the MPS subrack.
EPS Network
The EPS network refers to the OM network between the SCU board in an EPS
subrack and the other boards in the same subrack. The backplane in the EPS
subrack is used to connect entities on this network.
Run the command DSP OMU to check whether the active and standby OMUs are
normal (the blue part in the following information).
Check whether the internal and external networks are normal (the red part in the
following information).
If the internal network is abnormal, check whether the OMU is correctly

installed and whether the SCU is working normally.
If the external network is abnormal, check whether the external network

cables are correctly connected.
Run the command DSP OMU to query the status of the active and standby OMUs.
Check whether data synchronization is normal and whether the FE port connection is
normal.
Check whether the standby OMU starts normally. If the standby OMU does not
start normally, start the standby OMU.
For example, after a sudden switchover is performed between the active and
standby OMUs, if data synchronization fails, you can run the command DSP
OMU to find out the direct cause through the Data-sync state field in the
result.
If the network is normal, check whether the ALM-20701 OMU Failure Switchover
alarm is generated. If the alarm is generated, do as follows:
Use the troubleshooting method of the ALM-20701 OMU Failure Switchover

alarm to clear the alarm.
If the standby OMU is faulty and cannot be switched back, the onsite
personnel must check whether the data is the latest, and whether the data on
the OMU and host is consistent. If the data is consistent, you must clear the
alarm manually, run the command STP DATASYNC to stop data
synchronization, and run the command STR DATASYNC to enable data
synchronization again.
Note
when you perform the soft reset, you must be able to log in to the OMU server
remotely. In this way, you can avoid that the OMU cannot be started after the
OMU server is reset.
when you perform the hard reset, you must be able to perform cold start on
the OMU server locally. In this way, you can avoid that the OMU cannot be
started after the OMU server is reset.
Run the command DSP UCELL to query the cause of the cell setup failure. The
information similar to the following is displayed. Take measures based on the specific
cause.
If the cell setup failure is due to NCP unavailability or CCP unavailability, the link
bearing NCP or CCP may be faulty. Check whether an alarm related to the
corresponding SAAL or SCTP link (SAAL: ATM; SCTP: IP transmission) is generated. If
such an alarm is generated, clear the alarm according to help of the alarms
If the cell setup failure is due to FP synchronization failure or Common channel setup
failure, the user-plane transmission bearer may be faulty. Check whether a path alarm
is generated.
If the cell setup failure is due to Power mismatch, check whether the local cell on the
NodeB side is normal. If the local cell is unavailable, rectify the fault according to the
relevant chapter in the NodeB troubleshooting guide (Chapter 8 "Cell Setup Failure").
If the local cell is available, check whether the maximum downlink power on the
NodeB side and that on the RNC side. If the former is smaller than the latter, modify
the maximum downlink power on the RNC side or on the NodeB side to ensure that
the maximum downlink power on the NodeB side is greater than that on the RNC side.
Run the command LST UCELL on the RNC LMT to query the maximum downlink
power on the RNC side.
Run the command LST LOCELL on the NodeB LMT to query the maximum downlink
power on the NodeB side. The result is as follows:
If the cell setup failure is due to NodeB return cell setup failure and the Cause=NodeB
sends CELL SETUP FAILURE (Frequency acquisition not supported) information
is generated in the ALM-22206 Cell Setup Failed alarm, check whether the frequency
configurations on the RNC and the NodeB are consistent (run the command LST
UCELL on the RNC and the command LST LOCELL on the NodeB to query the
frequency configurations).
If the cell setup failure is due to Local cell not reported and the Cause=Data
configuration error or inconsistent with physical resources information is
generated in the ALM-22206 Cell Setup Failed alarm, check whether the NodeB is
configured with a local cell and whether the parameter configuration of the local cell
is consistent with that of the cell on the RNC side (run the command LST UCELL on
the RNC and the command LST LOCELL on the NodeB to query the parameter
configuration).
If the cell setup failure is due to Common channel setup failed and the setup failure of
the common channel is due to the allocation failure of L2 resources (Reason of the
latest common channel setup failure = L2 resource allocation failed), check whether
the service subrack is inserted with DPUs. If DPUs are inserted, run the command DSP
BRD to query the status of DPUs. If all DPUs are barred, unbar the DPUs; if all DPUs
are abnormal, insert new DPUs or replace the DPUs.
Run the command LST UNODEB or DSP LICUSAGE to check whether the license
control items unavailable for cells configured with ATM/IP dual stack or IPRAN. After
running the command DSP LICUSAGE, if the license control item is displayed with a
value that is not 0, this control item is available, as shown in the figure.
After running the command DSP LICUSAGE, if the license control item is not
displayed, the license is unavailable, and you need to reapply the license. If the license
control item is displayed with a value of 0, run the command SET LICENSE to enable
the license.
If the cell is configured with IPRAN, the license control item IP Transportation in Iub
Interface must be ON; if the cell is configured with ATM/IP dual stack, the license
control items IP Transportation in Iub Interface and IUB ATM/IP Dual Stack
Transportation Function must be ON.
Possible Fault Causes
Emergency faults are as follows:
Receive customers complaints that the call quality and access for many
users in a live network are affected.
KPIs, such as the call drop rate and the access success rate,
deteriorate seriously, affecting the call quality and network accessing
for a large number of users in a live network.
Services in one subsystem, one subrack, or the entire RNC are affected.
All services in one interface board are affected.
In the case of emergency faults, see section BSC6900 V900R014

Quick Troubleshooting Guide or section BSC6900 Heavy Traffic
Precaution and Emergency Measure Guide in the UMTS Maintenance
Guide, and troubleshoot the faults accordingly.
Possible causes for non-emergency faults are as follows:
Cell activation failure
Power congestion
Code resource congestion
Transmission congestion
CE congestion
DSP soft failure
If the fault is not an emergency service problem, you can infer that only some users
cannot make calls or access the network. To rectify the fault, do as follows:
Check whether the cell status is normal, namely, whether cell setup is normal, whether
the cell is available, and whether the cell uplink or downlink traffic is congested. Run
the following commands to query the cell status:
DSP UCELL
DSP UCELLCHK
If the cell is not activated, run the command ACT UCELL to activate the cell. If
the cell activation fails, run the command DSP UCELL to query the failure
cause.
For the specific cause analysis of the cell activation failure, see Chapter 4 .
If the cell is successfully set up, run the command LST UCELLACCESSSTRICT
to check whether the cell or the user AC is barred. If the cell is barred, unbar
the cell.
Run the DSP UCELLCHK to check whether the cell is in congested state, including power
congestion, code resource congestion, transmission congestion, and CE congestion.
Power congestion:
Power congestion is classified into uplink power congestion and downlink power
congestion. Usually, algorithm 1 is used as the downlink connection admission control
(CAC) algorithm, whereas the uplink CAC algorithm is turned off.
If the access failure is due to uplink power congestion, run the command DSP
UCELLCHK to check whether the RTWP is within the valid range (96.5 dB to 105.5
dB). Run the command LST UCELLCAC to check whether the auto-adaptive
background noise update switch is ON. If the auto-adaptive background noise update
switch is ON, deactivate the cell, and then re-activate the cell to check whether the
RTWP is normal.
If the auto-adaptive background noise update switch is OFF, turn off the uplink CAC
switch or reset the background noise. You can use the following command to turn off
the uplink CAC switch:
MOD UCELLALGOSWITCH:NBMUlCacAlgoSelSwitch=ALGORITHM_OFF;
Check the average RTWP value (vs-meanrtwp) in the traffic statistics, and set the
background noise to the minimum vs-meanrtwp.
The command is as follows:
MOD UCELLCAC: BackgroundNoise=61;

The parameter value depends on the site requirements. By default, it is set to
61. Actually configured noise floor = 112 + BackgroundNoise x 0.1
If the access failure is due to downlink power congestion, run the command DSP
UCELLCHK to check whether the latest TCP value is normal (<75%). To query the
admission threshold of a specific service, you can run the command LST UCELLCAC.
If the TCP value exceeds the threshold, the access fails. Check whether the admission
threshold is configured according to the baseline data or radio parameters for network
planning, and modify the obvious errors. For example, the admission threshold is
configured to 30%. If the threshold is configured according to the baseline data or
radio parameters for network planning, the network planners should negotiate with
the customer on whether to adjust the threshold to admit more users or expand the
capacity.
Code congestion:
Run the command DSP UCELLCHK to check whether the cell used rate of
code resources is normal and trace the code tree to check whether the cell
uses too many code words. If the minimum available code words are more
than the reserved code words, the cell capacity is limited and needs expansion.
The fewer the code words, the greater the service rate. For example, the
available minimum code word is SF32 but the configured reserved code word
is only SF16, the admission fails.
Alternatively, you can run the command LST UCELLCAC to check whether the
reserved code word of the cell is configured according to the baseline data or
the radio parameters for network planning. Newly admitted users cannot use
reserved code words. As a result, the more the reserved code words, the fewer
code words available for new users. If the configured value is too small (SF4),
you can modify it according to the baseline data. Otherwise, the network
planners should negotiate with the customer on whether to adjust the
threshold to admit more users or to expand capacity.
If the cell's number of users is too small and available minimum code words
are fewer than reserved code words, no congestion occurs. You can deactivate
the cell and then re-activate the cell to view the test result.
Transmission congestion:
Run the command DSP UCELLCHK to check whether Iub interface of the cell
is in congested state.
If the Iub interface is in congested state, check whether the reserved

bandwidth for the AAL2PATH is too high. By default, the reserved bandwidth
is 0. That is, no bandwidth is reserved.
Run the command LST TRMFACTOR to check whether the values configured
for service activation factors are within the valid ranges. Usually, these
parameters should be configured with recommended values.
For the PS services, you should also check whether the GBR is configured according to
the baseline data. If the GBR value is obviously inappropriate (such as 384 KB), the
network planners should negotiate with the operator on whether to decrease the GBR
to admit more users or adjust the bandwidth.
CE congestion:
Run the command DSP UCELLCHK to check whether the CEs of the cell are
congested.
Check whether the LAC/SAC/RAC data is configured and activated on the CN side
(MSC/SGSN). If this data is not configured, UEs cannot register to or attach themselves
to the network. You can trace the intelligent optimum sample (IOS) of the cell to
check whether a UE can register on or attach to the network normally.
When the SAC data is not configured on the CN side, the RNC fails to send the
initial direct transfer message for setting up signaling connection control part
(SCCP) connection. As a result, the UE cannot access the network.
Check whether the AAL2Path or IPPATH is available and configured correctly.
Run the command LST TRMMAP to check whether the transmission mapping
is set correctly. For example, in the ATM transmission, 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); High Speed Packet
Access (HSPA) services map HSPA NRT paths. High Speed Downlink Packet
Access (HSDPA) services and High Speed Uplink Packet Access (HSUPA) services
map with each other. Run the command LST AAL2PATH or LST IPPATH to
check whether the mapped path in the TRMMAP is actually configured.
According to the preceding result, the AMR service can be set up only after an
RT_VRB type AAL2 path or an EF type IP path is configured.
If the service is not recovered, please ask Huawei engineer for help.
Check whether the licenses for the HSPA functions are valid
Run the command DSP LICUSAGE to check whether the High Speed
Downlink Packet Access (HSDPA) and High Speed Uplink Packet Access
(HSUPA) functions are enabled. If the functions are not enabled, you must
apply for licenses to activate the HSPA functions.
Check data configuration
Run the command LST UNODEB to check whether the NodeB protocol
version is configured correctly. The REL-5 version supports the HSDPA, and the
REL-6 version supports both the HSDPA and the HSUPA.
Check the occupation of the code tree in the cell
Check the occupation of code tree resources in the cell. Usually, the HSDPA
service uses the last five SF16 code tree resources. If the resources are
distributed to R99 users, the HSDPA service cannot be set up.
Step 1
Check whether the UE supports the HSPA services

The setup of the HSPA services requires the support of the UE. Send the RRC
CONNECTION SETUP REQ message to check whether the UE attempting to
access the network supports the HSPA functions. If the UE supports the
HSDPA, the REL-5 version is displayed. If the message contains the
ueCapabilityIndication IE and the value contains edch, the UE supports the
HSUPA function, as shown in the following figure.
RRC_RRC_CONNECT_REQ
Step 2
Check whether the number of HSPA users is limited

The number of HSUPA users and the number of HSDPA users are independent
from each other. Therefore, you need to set admission thresholds at both the
cell level and the NodeB level.
The maximum number of HSPA users supported by a cell is MIN (value
specified in the RNC license, value set in the cell CAC algorithm). The RNC
license controls the maximum number of HSPA users a single cell, which can
be queried through the command DSP LICUSAGE. This number is subject to
the maximum number of HSPA users that are supported. For example, the
64HSDPA Users per Cell switch is ON, indicating that the cell supports up to
64 HSDPA users.
Run the command LST UCELLCAC and set the numbers of HSUPA users and HSDPA
users in the cell CAC algorithm.
Run the command LST UNODEBLGOPARA to query the maximum number of HSPA
users supported by the NodeB. By default, this number is 6144. Access failure rarely
occurs.
Run the command DSP UCELLCHK to query the number of HSPA users supported by
the serving cell. If the result is equal or close to the number of users permitted in the
license or configured in the CAC algorithm, the access fails due to the admission
threshold for HSPA users. You need to re-apply for the relevant license or modify
admission threshold for users.
Step 3
Check the AAL2PATH and IPPATH configurations
Check whether the AAL2PATH (ATM) or IPPATH (IP) are configured on the RNC
and NodeB. You must view the corresponding transmission resource mapping
table. Run the command LST TRMMAP, and the following information is
displayed.
Run the command LST AAL2PATH to check whether the AAL2PATH with the
corresponding properties is configured. For example, according to the
preceding result, the HSDPA service can be set up only when the AAL2PATH
configured with the ATMHD UBR is available. Check the HSUPA service in the
same method.
Step 4 Check whether the AAL2PATH and IPPATH are available
If the AAL2PATH and IPPATH are configured, check whether these paths are
available.
Step 5
Check the MBR assigned by the CN

The RNC determines whether to use the HS-DSCH or E-DCH to bear the service
based on the MBR assigned by the CN and the preset threshold. If the MBR
assigned by the CN exceeds the threshold for setting up the HSPA service, the
service can be set up on the HS-DSCH/E-DCH. Otherwise, the service is borne
on the E-DCH. The thresholds for the BE service and streaming service are set
independently.
As shown in the following figure, the MBR is assigned in the
RANAP_RAB_ASSIGNMENT_REQUSET message.
You can run the command LST UFRCCHLTYPEPARA to query the threshold
for setting up the HSPA service. If the uplink rate assigned by the CN is lower
than the threshold for setting up the HSUPA service, you should negotiate with
the operator on whether to modify the threshold to set up the HSPA service.
Alternatively, you can modify the subscription information on the HLR. Check
the consistency between the IMSI information and the CN-assigned
information before the modification. The subscription information on the HLR
may be correct, but an AT command is used to limit the rate during the dialup. Instead of providing a solution to the problem, the modification of the
threshold for setting up the HSPA service can only ensure the setting-up of the
service on the HS-DSCH. The service rate for users is still under the control of
the MBR. Therefore, it is necessary to modify the subscription information on
the HLR or cancel the AT command for limiting the service rate.
Step 6 Check the health of a cell
Run the command DSP UCELLCHK to check the health of a cell and whether
the cell is in congested state.
Step 7 If you cannot solve the HSPA service setup failure, please ask Huawei
engineer for help.
The PS relocation fails. During Iu interface tracing, the RNC initiates the relocation.
After the CN sends the relocation command, the RNC cancels the relocation.
The cause of relocation cancellation is iu-transport-connection-failed-to-establish.
Abnormality information (such as GRA FAIL) is displayed in the CDT.
The IP routes on the Iur interface are used to forward the PS data during Serving Radio
Network Subsystem (SRNS) relocation. During the SRNS relocation, the PS data is
transferred from the local RNC to the SGSN and then to the neighboring RNC.
Therefore, the prerequisites to configuration of IP routes on the Iur interface are that
the IP paths between the local RNC and the SGSN, between the neighboring RNC and
the SGSN, and between the Service RNC (SRNC) and the Drift RNC (DRNC) are
configured.
Step 1
Check whether the Iu-PS user-plane (UP) used for relocation is set up.
If the cause of the relocation failure is iu-transport-connection-failed-toestablish, and the abnormality information (such as GRA Fail) is displayed,
the Iu-PS UP is faulty.
Most Iu-PS UP faults are related to the configuration of the IP packet round
trip delay (IPRT) or IPPATH.
The IPRT must be configured on the interface board. The mask and next hop
address must be consistent with the Iu-PS UP address configured for other
CNs. The destination address is the GPRS Tunneling Protocol for the user-plane
(GTPU) address of the neighboring RNC. In addition, you must configure the
IPPATH from the local GTPU address to the peer GTPU address. The adjacent
node is the adjacent node of the PS CN. After the IPRT is configured on the
interface board, if you execute the ping command, with the DEVIP of the local
Iu-PS UP as the source address and the GTPU address of the neighboring RNC
as the destination address, the execution is successful.
Step 2 View the CDT information to check whether the GTPU address of the
neighboring RNC is configured correctly.
In the RANAP_Relocation_Command signaling of the Iu interface, the

transportLayerAddress-First information element (IE) indicates the GTPU
address of the neighboring RNC. As shown in the following figure, the GTPU
address is 0C 11 0A 0D or 12.17.10.13 in decimal notation.
Set up the Iu-PS UP for relocation according to Step 1, and check whether the
destination IP address of the IPRT or the IPPATH and the mask contains the
GTPU IP address after the AND operation is performed. If the destination IP
address and the mask do not contain the GTPU IP address, add the IPRT and
IPPATH.
In this section, an example is described to help you understand the configuration of PS

relocation.
Take the actual configuration of a site as an example. This site is deployed in Iu-PS
ATM networking mode (the load of the Iu-PS link is shared by the boards in slot 16
and slot 17). Both IP and ATM networking modes are used for the Iur interfaces to
different neighboring RNCs.
The Iur data should be configured in advance according to the following procedure. In
the case of multiple neighboring RNCs, the Iur data for each neighboring RNC should
be configured in sequence.
Cautioned Words
1
Tracing ( Signaling/
Message/Interface etc)
The privacy-related information may be anonymity for user's

privacy protection
FTP
There is security risk for FTP protocol and Huawei recommends to

use SFTP or FTPS to replace it
IP address

privacy protection
Collect

privacy protection

Owc403700 Bsc6900 Wcdma v900r014 Troubleshooting Issue 1.

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Owc403700 Bsc6900 Wcdma v900r014 Troubleshooting Issue 1.

Uploaded by

Copyright:

Available Formats

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

To conduct the BER test, perform the following steps:

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

The working status measurement result of the AAL terminal corresponding to a

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting

Confidential Information of Huawei. No Spreading Without Permission

BSC6900 WCDMA V900R014 Troubleshooting