IP RAN Deployment Guide

Ehu
Document
Code
Intended
Audience
Department
INTERNAL
WCDMA
UMTS
Maintenance Dept
Product
Name
WCDMA RNC&NodeB
Product
Version
V200R0010
Document
Version
IPRAN Deployment Guide V210

Prepared by
Transport Team of
Maintenance Dept
UMTS
Date
2008-08-25
Reviewed by
Transport Team of
Maintenance Dept
UMTS
Date
2008-08-25
Reviewed by
Transport Team of
Maintenance Dept
UMTS
Date
2008-08-25
Approved by
Date
Huawei Technologies Co., Ltd.

All rights reserved
INTERNAL
IPRAN Deployment Guide
Revision Record
Date
Revision
Version
Description
Author
2008-06-16
V1.0
Initial draft
Transport Team of
UMTS Maintenance
Dept
2008-08-01
V1.1
Modified on the basis of test and review

results
Transport Team of
UMTS Maintenance
Dept
2008-08-21
V1.2
Modified on the basis of review results

by Maintenance Dept
Transport Team of
UMTS Maintenance
Dept
INTERNAL
Contents
2008-09-14
Huawei Confidential
Page 2 of 133
INTERNAL
Tables
Table 2.1Hardware requirements ..........................................................................................12
Table 2.2Version requirement ...............................................................................................13
Table 2.3Comparison of RNC IP interface boards .................................................................13
Table 2.4Functions of NodeB IP transmission boards ............................................................15
2008-09-14
Huawei Confidential
Page 3 of 133
INTERNAL
Figures
Figure 1.1PPP frame format ...................................................................................................8
Figure 1.2IPHC compression range ........................................................................................8
Figure 1.3Position of the M3UA in each interface protocol stack ............................................16
Figure 1.4Principle of multi-home ..........................................................................................18
Figure 1.5PDH/SDH-based IPRAN L2 networking .................................................................24
Figure 1.6SDH-based IPRAN L2 networking .........................................................................24
Figure 1.7MSTP-based IPRAN L2 networking .......................................................................25
Figure 1.8Data network-based IPRAN L2 networking ............................................................26
Figure 1.9L3 networking of RNC directly connecting to one router .........................................27
Figure 1.10L3 networking of RNC directly connecting to two routers ......................................28
Figure 1.11L3 networking with the load sharing .....................................................................29
Figure 1.12IPRAN networking in the hybrid transport - Iub......................................................30
Figure 1.13IPRAN networking in the ATM/IP dual-stack transport - Iub...................................31
Figure 1.14 Iub interface protocol stack .................................................................................42
Figure 1.15IP planning of Ethernet-based L3 networking .......................................................47
Figure 1.16IP RAN hybrid transport networking .....................................................................52
Figure 1.17IP planning of Ethernet-based L3 networking .......................................................53
Figure 1.18E1-based IP planning ..........................................................................................53
Figure 1.19Dual stack transport networking............................................................................59
Figure 1.20ATM configuration planning..................................................................................59
Figure 1.21IP address planning for layer 3 networking over Ethernet......................................60
Figure 1.22IP address planning for layer 2 networking over Ethernet......................................60
Figure 1.23IP protocol stack of IU-PS interface......................................................................92
Figure 1.24IP protocol stack of IU-CS interface......................................................................93
Figure 1.25IP protocol stack of IUR interface..........................................................................93
Figure 1.26IUPS data planning .............................................................................................94
Figure 1.27PSP-IPSP transfer networking .............................................................................95
2008-09-14
Huawei Confidential
Page 4 of 133
INTERNAL

Figure 1.28ASP-SGP direct connection networking ...............................................................96
Figure 1.29ASP-SGP transfer networking ..............................................................................96
Figure 1.30IUCS data planning ...........................................................................................100
Figure 1.31IUR data planning .............................................................................................104
Figure 1.32Maintaining NodeB by the M2000 Through the RNC...........................................113
Figure 1.33Maintaining the NodeB directly by the M2000 .....................................................116
Figure 1.34Initial address application in the scenario without using DHCP Relay ..................121
Figure 1.35Server-Client networking with using the Relay ....................................................122
Figure 1.36Initial address application in the scenario using the DHCP Relay ........................122
Figure 1.37General process of NodeB remote software debug .............................................123
2008-09-14
Huawei Confidential
Page 5 of 133
INTERNAL

Keywords: IPRAN, PPP, FE, SCTP, IPPATH
Abstract: This document describes the basic principle, basic networking, deployment
preparation, basic configuration procedure, precautions, principles and configurations of
the DHCP remote debugging of the WCDMA IPRAN.
The information in this document is for the internal use only and cannot be used as the basis for
the reply to a customer or Market Dept.
Acronyms and Abbreviations:
Abbreviations
Full Name
PPP
Point-to-Point Protocol
DHCP
Dynamic Host Configuration

Protocol
OSPF
Open Shortest Path First
RIP
Route Information Protocol
ISIS
Intermediate SystemIntermediate System
WFQ
Weighted Fair Queuing
Chapter 1 Overview
1.1 Introduction to the V210 IPRAN
In V210, the Iub, Iur, and Iu interfaces are carried over the IP transport network. An
operator can use the existing IP networks for the transport expansion. The network
construction cost is saved. In addition, the IP network provides a variety of access
modes and provides the sufficient transport bandwidth for high speed data services
(for example, HSDPA).
2008-09-14
Huawei Confidential
Page 6 of 133
INTERNAL

With the comparison to V18 and V29, the new IPRAN functions in the V210 are as
follows:
1.1.1 FP MUX
1. Principles
The frame protocol multiplexing (FPMUX) multiplexes several small FP PDU
frames (sub-frame) that should be transmitted independently to one UDP/IP frame
header. As a result, a number of UDP/IP headers are saved. Hence, the transport
efficiency increases.
The FP MUX is applicable to only the user plane in the IPRAN Iub interface.
2. Protocol
The FP MUX is the protocol defined by Huawei.
3. Command
//At the RNC side:
ADD IPPATH: FPMUX=YES, SUBFRLEN=127, MAXFRAMELEN=270, FPTIME=2;
By default, the FP MUX is disabled.
After the FP MUX is enabled, the default parameters are as follows:
FPMux maximum sub frame length (SUBFRLEN)=127Bytes
FPMux maximum multiplexing frame length (MAXFRAMELEN)=127Bytes
Multiplexing maximum delay (FPTIME) =2ms
// At the NodeB side:

ADD
IPPATH:
SRN=0,
SN=6,
SBT=BASE_BOARD,
PT=ETH,
JNRSCGRP=DISABLE,
FPMUXSWITCH=ENABLE,
SUBFRAMELEN=127,
FRAMELEN=270, TIMER=1;
By default, the FP MUX is disabled.
After the FP MUX is enabled, the default parameters are as follows:
FPMux maximum sub frame length (SUBFRAMELEN)=127Bytes
FPMux maximum multiplexing frame length (FRAMELEN)=127Bytes
Multiplexing maximum delay (TIMER) = 1ms
2008-09-14
Huawei Confidential
Page 7 of 133
INTERNAL
1.1.2 IPRAN Header Compression

1. Principles
The IPRAN header compression improves the transport efficiency by compressing
partial fields of PPP frames.
Figure 1.1 PPP frame format
The PPP frame header compression algorithm implements the following:
Address and control field compression (ACFC): The address and control field
is the constant value (0XFF03) and is not transported every time. After the
PPP link is configured with the Link Control Protocol (LCP), the subsequent
packet address and control fields can be compressed.
Protocol field compression (PFC): The PFC can compress two-byte protocol
field to one byte. The system judges whether the protocol field is one byte or
two bytes according to the last significant bit (LSB) of the first byte in the
protocol field. If the LSB is 1, it indicates that the protocol field is two bytes in
length. If the LSB is 0, it indicates that the protocol field is only one byte in
length. For example, the first byte of the protocol field is 0x00, it can be
compressed.
IP Header Compression (IPHC): The IPHC compresses the IP/UDP header of

the PPP frame.
Compression
range
PPP
header
IPheader
UDP
header
Application
data
PPPtail
Figure 1.2 IPHC compression range
2008-09-14
Huawei Confidential
Page 8 of 133
INTERNAL

IPHC principles:
1) The header field remaining unchanged is not carried in each packet that is
sent. The header field changed according to the designated mode can be
replaced by fewer bits.
2) If the header context of the packet stream is established at both ends of a
link, only the changed header field and the corresponding context tag are
transferred. The original header can be recovered according to the context
and changed fields.
Terms:
Context: It is the status table of the synchronization maintenance of the same
packet stream by the compresser and decompresser. The compresser uses it
to compress the packet header. The decompresser uses it to recover the
compressed packet header.
2. Protocol
ACFC: RFC 1661
PFC: RFC 1661
IPHC: RFC 2507 and RFC 3544
3. Command
At the RNC side:
ADD PPPLNK: MUX=Disable, IPHC=UDP/IP_HC, PFC=Enable, ACFC=Enable;

By default, three algorithms are enabled.
At the NodeB side:
ADD PPPLNK: IPHC=ENABLE, PFC=ENABLE, ACFC=ENABLE;

By default, three algorithms are enabled.
1.1.3 IPRAN Fault Detection

1. Principles
At present, the RNC supports the ARP detection and BFD detection for detecting
the transport link from the RNC to the peer equipment:
Address resolution protocol (ARP) detection
The system determines the continuity of the link according to the response of the
2008-09-14
Huawei Confidential
Page 9 of 133
INTERNAL

peer equipment by sending ARP requests to the peer equipment. Every the fixed
duration, the RNC constructs an ARP request packet to send to the network. The
destination address of the packet is the peer address to be detected. The RNC
determines the continuity of the link by judging whether the response from the
destination address is received.
The ARP detection is applicable to only the direct connection detection whose both
ends are on the same network segment.
Features of the ARP detection are as follows:
The ARP is the basic protocol, without depending on the peer equipment. The
detection starts at one single end.
The detection state is related to the port state. The port switchover is triggered
if a fault is detected. The system deletes the route whose detection address is
the next hop. The upper layer service selects other available channels.
The ARP detection supports the independent port detection, only active port
detection, and active/standby port simultaneous detection.
When the active and standby ports are detected at the same time, the IP
address of the active and standby ports should not be on the same network
segment.
Bidirectional forwarding detection (BFD)
The method of the BFD detecting the link continuity: The system originates the
handshake packets from both ends and determines the link continuity according to
the handshake result (success or failure).
The V210 RNC implements the single-hop BFD (SBFD) and multi-hop BFD
(MBFD):
SBFD:
The SBFD is applicable to only the direct connection detection whose both ends
are on the same network segment, which is the same as the ARP detection. The
features of the SBFD are as follows:
The both ends must start at the same time. The detection duration at both
ends must be configured to be equivalent. At present, only the asynchronous
mode is supported.
The detection state is related to the port state. The port switchover is triggered
if a fault is detected. The system deletes the route whose detection address is
the next hop. The upper layer service selects other available channels.
The independent port detection is supported. Only the active port is detected.
The active/standby port simultaneous detection is not supported.
2008-09-14
Huawei Confidential
Page 10 of 133
INTERNAL
MBFD:
The MBFD is applicable to the non direct connection end-to-end detection in the
scenario where signals pass more than one network nodes. The features of the
MBFD are as follows:
The both ends must start at the same time. The detection duration at both
ends must be configured to be equivalent. At present, only the asynchronous
mode is supported.
The detection state is not associated. If a fault is detected, only an alarm is

reported.
The MBFD does not depend on a port. The IP (DEVIP or ETHIP) of the active
and standby boards can be used as the local address of the multi-hop BFD. In
addition, the peer IP address and any local IP address should not be on the
same network segment.
2. Protocol
ARP protocol and BFD protocol
3. Commands
By default, ARP detection, SBFD, or MBFD is disabled.
ARP detection (three modes)
1) Active/standby port simultaneous detection

STR
GATEWAYCHK:
SRN=0,
SN=14,
CHKTYPE=ARP,
PN=0,
MODE=REDPORT,
GATEWAY="100.10.10.20",
BAKIP="100.10.20.10",
BAKMASK="255.255.255.0", BAKGATEWAY="100.10.20.20", ARPTIMEOUT=3,
ARPRETRY=3;
2) Active port detection
STR
GATEWAYCHK:
SRN=0,
SN=14,
CHKTYPE=ARP,
PN=0,
MODE=PRIMARYCHKONLY,
GATEWAY="100.10.10.10",
ARPTIMEOUT=3,
ARPRETRY=3;
3) Independent port detection
STR GATEWAYCHK: SRN=0, SN=14, CHKTYPE=ARP, PN=0, MODE=INDPORT,
GATEWAY="100.10.10.10", ARPTIMEOUT=3, ARPRETRY=3;
Default parameters of the ARP detection:
ARPTIMEOUT: 300 ms
2008-09-14
Huawei Confidential
Page 11 of 133
INTERNAL
ARPRETRY: 3 times
SBFD
1) Independent port detection

STR
GATEWAYCHK:
SRN=0,
SN=14,
CHKTYPE=SBFD,
PN=0,
MODE=INDPORT, GATEWAY="100.10.10.20", MINTXINT=30, MINRXINT=30,
BFDDETECTCOUNT=3;
2) Active port detection
STR
GATEWAYCHK:
SRN=0,
SN=14,
CHKTYPE=SBFD,
PN=0,
MODE=PRIMARYCHKONLY,
GATEWAY="100.10.10.20",
MINTXINT=30,
MINRXINT=30, BFDDETECTCOUNT=3;
MBFD
STR
GATEWAYCHK:
SRN=0,
SN=14,
CHKTYPE=MBFD,
MBFDLOCALIP="100.10.10.10",
GATEWAY="100.20.20.20",
MINTXINT=30,
MINRXINT=30, BFDDETECTCOUNT=3
The default parameters of the BFD are as follows:
Min interval of BFD packet send (MINTXINT): 30 ms

Min interval of BFD packet receive (MINTXINT): 30 ms
BFDDETECTCOUNT: 3 times
1.2 Availability
1.2.1 Requirements for NEs
The IP feature requires the coordination of the NodeB, RNC, and CN. Table 1-1
lists the data configuration requirements for these NEs. The symbol '' indicates
that the NE is required.
Table 2.1 Hardware requirements
IP
feature
requirement
NodeB
RNC
CN
Data configuration
Hardware
requirements
WMPT/UTRP
PEUa/POUa/UOIa_IP/FG2a/GOUa
2008-09-14
Huawei Confidential
Page 12 of 133
INTERNAL
1.2.2 Supporting Versions

Table 2.2 Version requirement
Product
Supporting Version
RNC
BSC6810
BSC6810V200R010C01B051 and later
NodeB
DBS3836
V200R010C01B040 and later
BTS3836/ BTS3836A
V200R010C02B040 and later
CME
M2000
1.2.3 Other Support

1. RNC side
If the IP RAN feature is required, the corresponding IP interface boards should be
added at the RNC and NodeB sides. At the RNC side, the interface boards
supporting the IP interface are as follows:
FG2a: RNC packet over electronic 8-port FE or 2-port GE Ethernet Interface

unit REV:a
GOUa: RNC 2-port packet over Optical GE Ethernet Interface Unit REV:a
PEUa: RNC 32-port Packet over E1/T1/J1 Interface Unit REV:a
UOIa_IP: RNC 4-port Packet over Unchannelized Optical STM-1/OC-3c Interface

unit REV:a
POUa: RNC 2-port packet over channelized Optical STM-1/OC-3 Interface Unit
REV:a
The following table describes the features and functions of these boards.
Table 2.3 Comparison of RNC IP interface boards
Board Type
FG2a
Description
Enabling IP over Ethernet
Providing eight FE ports and two GE electrical ports
Providing IP over FE/GE
Supporting interfaces such as Iu-CS, Iu-PS, Iu-BC, Iur, and Iub
2008-09-14
Huawei Confidential
Page 13 of 133
INTERNAL

GOUa
PEUa
Enabling IP over Ethernet
Providing two GE optical ports
Providing IP over GE
Supporting IP over E1/T1/J1
Providing 32 channels of IP over PPP/MLPPP over E1/T1
Providing 128 PPP links or 64 MLPPP groups, each MLPPP group

containing 8 MLPPP links
Providing the fractional IP function
Providing the timeslot cross-connection
Obtaining clock signals from the Iu interface and exporting timing signals to
the GCUa/GCGa board
UOIa_IP
Exporting timing signals to the NodeB
Supporting interfaces such as Iu-CS, Iur, and Iub
Providing 4 unchannelized STM-1/OC-3c optical interfaces
Supporting IP over SDH/SONET
Supporting PPP (LCP/NCP/IPCP)/PPPMUX protocol
Obtaining clock signals from the Iu interface and exporting the clock
signals to the GCUa/GCGa board
POUa
Exporting clock signals to the NodeB
Providing two optical interfaces over channelized optical STM-1/OC-3

transmission based on IP protocols
Supporting IP over E1/T1 over SDH/SONET
Providing Multi-Link PPP. In E1 transmission mode, 42 MLPPP groups are

provided, and in T1 transmission mode, 64 MLPPP groups are provided.
Providing 126 E1s or 168 T1s
Supporting interfaces such as Iu-CS, Iur, and Iub
Obtaining clock signals from the Iu interface and exporting the clock
signals to the GCUa/GCGa board
Exporting timing signals to the NodeB
2. At the NodeB side:

In V210, boards supporting the IP transmission at the NodeB side are as follows:
2008-09-14
Huawei Confidential
Page 14 of 133
INTERNAL
WCDMA Main Processing & Transmission unit board (WMPT): Provides one
4-channel E1 port, one FE electrical port, and one FE optical port. Supports
ATM and IP.
Universal Transmission Processing unit (UTRP): Provides 8 E1s/T1s. The

board supports ATM and IP protocols.
The following table describes the functions of these boards.

Table 2.4 Functions of NodeB IP transmission boards
Board Type
WMPT
Description
Supporting IP over Ethernet and IP over E1/T1/J1
Providing one 4-channel E1 port, one FE electrical port, and one
FE optical port
Providing 8-channel IP over PPP/MLPPP over E1/T1
Providing 8 PPP links or 4 MLPPP groups (each MLPPP group
contains up to eight MLPPP links)
Providing Fractional IP function
Providing the timeslot cross-connection function
Supporting the line clock extraction
Supporting the Iub interface
Supporting IP over E1/T1/J1
Providing 8-channel E1/T1 interfaces
UTRP
Providing 16-channel IP over PPP/MLPPP over E1/T1

Providing 16 PPP links or 4 MLPPP groups (each MLPPP group
contains up to 16 MLPPP links)
Providing Fractional IP function
Providing the timeslot cross-connection function
Supporting the line clock extraction
Supporting the Iub interface
2008-09-14
Huawei Confidential
Page 15 of 133
INTERNAL
Chapter 2 Introduction to Basic

Protocols
2.1 M3UA
Figure 1.3 Position of the M3UA in each interface protocol stack
2.1.1 Principles and Relevant Concepts

MTP3 User Adaption Layer (M3UA): It is the adaption layer protocol of MTP level-3
users. The M3UA provides the conversion between the signaling point code (SPC)
and IP address. The M3UA is applicable to the transmission of the SS7 protocol
between the SoftSwitch and signaling gateway (SG). The M3UA supports the
transmission of MTP level-3 user message in the IP network, including but not
limited to, ISUP, TUP, and SCCP messages. The RANAP is the SCCP user
protocol. Their messages are transparently transmitted in the M3UA protocol layer
as the SCCP payload.
Concepts related to the M3UA:
Application server (AS): It serves the logical entity of specific routing keywords.
The AS processes the call procedure of all SCN trunks identified by SS7 SIO, DPC,
OPC, and CIC. The AS contains a group of unique AS process, among them, one
or two are in the active state.
2008-09-14
Huawei Confidential
Page 16 of 133
INTERNAL

Application server process (ASP): It is the process instance of the AS. One ASP
functions as one active or standby process of the AS. One ASP contains one
SCTP endpoint and may be configured to process signaling services in one or
more ASs.
IP server process (IPSP): It is the process instance based on the IP application.
Essentially, the IPSP is the same as the ASP. The IPSP uses the point to point
M3UA, instead of SG services.
Signaling gateway (SG): It is the signaling proxy for receiving and sending
signaling messages at the edge between the SS7 network and IP network.
Signaling gateway process (SGP): It is an instance of the signaling gateway
process. The SGP is the activation, backup, load-sharing, or broadcast process of
the signaling gateway.
Switched Circuit Network (SCN): It is the network carrying services by using the
channel with the pre-defined bandwidth.
Media gateway (MG): When a media stream flows from the SCN to the PS
network, the MG terminates the SCN media stream and packs media data (if
media data is not based on the data packet form), and transfers the packed service
to the packet-based network. When a media stream flows from the PS network to
the SCN, the system implements the reversal procedure.
Media gateway controller (MGC): The MGC is responsible for processing the
resource registration and management on the MG.
2.1.2 Functions of the M3UA

Functions of the M3UA are as follows:
Supporting the transport of all MTP3 user message (ISUP, TUP, or SCCP)
Supporting the seamless interaction of the same MTP3 user protocol in

different networks (for example, the interaction between the ISUP in the SCN
and the ISUP in the IP network)
Supporting the SCTP connection and service management between the SG

and MGC (or the database in the IP network), and between IPSPs
Supporting the redundancy protection (active/standby connection or load

sharing) between the SG and MGC (or the database in the IP network), and
between IPSPs
Supporting the interworking capability of the MTP3 network management

function and address translation mapping (SS7<->IP)
Supporting the redundancy management, SCTP stream mapping, and
2008-09-14
Huawei Confidential
Page 17 of 133
INTERNAL

congestion control
Supporting the seamless network management interaction and active

connection control
2.1.3 Protocol
RFC 3332
2.1.4 Configuration Sequence at the RNC Side

The configuration sequence at the RNC side is as follows:
(OPC --> N7DPC )--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK
2.2 SCTP
For the SCTP principles, see V18 Deployment Guide. This section describes the
multi-homed SCTP.
2.2.1 Principles of Multi-Homed SCTP

The multi-homed SCTP means that one device has multiple IP addresses.
Figure 1.4 Principle of multi-home
Path: It is the route of data transmission. In the IP network, the transmission path is
related to the destination IP address and the source IP address. Actually, a path is
determined by the destination address and source address. The SCTP supports the
2008-09-14
Huawei Confidential
Page 18 of 133
INTERNAL

multi-home, that is, multiple IP addresses can be used for the transport. The
conservative policy is used. In the case of the connection setup, the system selects
one active path (active source address and active destination address) for the
transport. When the active path is unreachable or the retransmission is required,
another path is used.
Multi-homed endpoint: In one endpoint, if multiple transport addresses are used as
the destination address, the endpoint is considered as the multi-homed endpoint.
2.2.2 SCTP Dual-Homed Mechanism Supported by the RNC

The multi-homed SCTP supported by V210 RNC refers to two local addresses and
two peer addresses. As shown in Figure 2-2, the local system has IP A and IP B, and
the peer system has IP 1 and IP 2.
Active destination address:
The Path is maintained by maintaining the state of the destination address. In the case
of multiple destination addresses, one active destination address is maintained. The
active destination address is preferred for sending data.
Maintenance path:
At present, only two maintenance paths are available. When one is unavailable, the
system finds the next available path through sending the heartbeat. In the path that is
not maintained, the system does not send the heartbeat actively.
2.2.3 Protocol
For the relevant protocol, see the RFC2960. For the dual-homed SCTP, see " 6.4
Multi-homed SCTP Endpoints".
2.3 Others
For the principles of the TCP, UDP, PPP, ARP, NAT, VLAN, and TRACERT, see
V18 Deployment Guide.
2008-09-14
Huawei Confidential
Page 19 of 133
INTERNAL
Chapter 3 Introduction to the Networking

3.1 V2 Backup Policy
3.1.1 Backup Mode at the RNC Side
Two backup modes are available in the RNC: board backup and port backup
Board backup
In the board backup mode, one board is active and the other is standby. The service
can be processed by the active board or by active and standby boards. When the active
board is faulty, the RNC automatically originates the switchover of the active/standby
boards.
Port backup
In the port backup mode, one port is active and the other is standby. Services are
transported through the active port only. When the active port is faulty, the RNC
automatically originates the switchover of the active/standby ports.
1. Board backup mode
With the comparison to V29, the board backup and port backup in V210 are
independent. If only the board backup is configured, without configuring the port
backup, the board is switched over only when the board is faulty.
In the board backup mode, one board is active and the other is standby. The service
can be processed by the active board or by active and standby boards (that is, the
board is in the active/standby mode and the port is in the load sharing mode).
When the active board is faulty, the RNC automatically originates the switchover of
active/standby board.
You can set the board backup relation by running ADD BRD. If Backup is set to Yes,
the board backup applies.
2. Port backup mode
FG2a and GOUa boards

2008-09-14
Huawei Confidential
Page 20 of 133
INTERNAL

When the active/standby slots in the RNC subrack are configured with two FG2a/GOUa
boards, two FG2a/GOUa boards can be set to Board backup;port not backup, or
board and port backup.
When FG2a/GOUa boards are set to the board backup, you can configure the FE/GE
port backup by running ADD ETHREDPORT.
If the port backup is not configured and only the board backup is configured, the board
backup and port load-sharing mode applies.
With the comparison to V29, the Board and port backup bonding is reduced in the IP
interface board for the backup mode in V210, and only Board and port backup apart
and the board backup and port load sharing mode are available in V210.
UOIa_IP and POUa boards
When the UOIa is in the board backup mode, the corresponding optical ports (for
example, optical port 0 in the active board and optical port 0 in the standby board) in
active/standby UOIa are also backed up. The backup mode is MSP 1:1 or MSP 1+1
(single end or dual ends).
When the optical interface of the UOIa is in MSP 1:1 backup, one optical port is active,
and the other optical port is standby. The active optical port is responsible for receiving
and transmitting data.
In the case of the MSP 1+1 backup of the optical port in the UOIa board, one optical
interface is active and the other is standby. The data processing of the backup mode:
The active and standby optical ports send data at the same time, and only the active
optical port receives data.
To set the relevant attributes of the MSP backup, run SET MSP. MSP attributes include
Revertive type, WTR Time (required only when Revertive type is set to REVERTIVE),
K2 Mode, SDSF Priority, and Backup mode. The settings of these parameters must
be consistent with those at the peer end through negotiation.
3. Impact on the system by the switchover
When the FG2a/GOUa adopts the board backup without the port backup, the
switchover of the active/standby board has not impact on existing services.
When the FG2a/GOUa adopts the board backup and port backup, the switchover of the
active/standby board has the slight impact on the data transport. The existing service is
not interrupted.
If the data traffic of the optical interface is large, the switchover of the active/standby
UOIa board has the slight impact on the data transport. The existing service is not
interrupted.
2008-09-14
Huawei Confidential
Page 21 of 133
INTERNAL
3.1.2 NodeB Side

1. NodeB supports only the board backup mode, without supporting the port backup mode
In the board backup mode, data is configured and processed only in the active
board, and the standby board is in the monitoring status. When all used physical
links in the active board is in the unavailable state (For example, E1 has the LOS
alarm and the FE port is DOWN) and a physical link is available in the standby
board, the board can be switched over. In the case of the switchover, the active
and standby boards are restarted. When the configurations of the active board are
loaded to the standby board, the standby board is upgraded to the active board. In
the case of the switchover, the service is interrupted.
In the configuration of the board backup mode, only the CME can be used to
generate the configuration file. To query the current board mode, run LST IUBGRP
in the LMT. If the board is not configured to the active/standby mode, you can
perform configurations by running commands. The specific configuration modes
are as follows:
2008-09-14
Huawei Confidential
Page 22 of 133
INTERNAL
3.2 Common Networking Modes

3.2.1 Layer-2 Networking Mode
The RNC is connected to the NodeB (Iub interface) through the LAN. The RNC is
2008-09-14
Huawei Confidential
Page 23 of 133
INTERNAL

connected to the SGSN (Iu interface) through the LAN. The RNC is connected to the
RNC (Iur interface) through the LAN. The interface address of each NE is on the same
network segment.
According to the transport media, the following network modes are available:
1. IP over E1/T1 over PDH/SDH (Iub interface)
Figure 1.5 PDH/SDH-based IPRAN L2 networking
The RNC and NodeB access the transport network through the E1/T1. The
data is transmitted in the IP over MLPPP or PPP over E1/T1 mode.
The NodeB can obtain the line clock over E1/T1.
Backup mode: The PEUa is set to active/standby board by running ADD BRD.
The active/standby PEUa board is connected to the peer equipment through the Yshaped E1/T1 cable.
The RNC and NodeB use the header compression algorithm to improve the
transport efficiency.
2. IP over SDH (Iub interface)
Figure 1.6 SDH-based IPRAN L2 networking
The RNC accesses the transport network through the channelized STM-1 on
the POUa. The NodeB accesses the transport network through the E1/T1. The data is
2008-09-14
Huawei Confidential
Page 24 of 133
INTERNAL

transmitted in IP over MLPPP or PPP over E1/T1 mode.
NodeB can obtain the line clock over E1/T1.
Backup mode: The POUa is set to the active/standby board by running ADD
BRD. The optical interface in the board is set to MSP 1:1 or MSP 1+1 backup mode.
The RNC and NodeB use the header compression algorithm to improve the
transport efficiency.
3. MSTP-based IP networking (Iub interface)
Figure 1.7 MSTP-based IPRAN L2 networking
The RNC accesses the MSTP network through the GE optical port of the
GOUa board or FE/GE electrical port of the FG2a board. The NodeB accesses the
transport network through the FE electrical port or optical port. The data is transmitted in
the IP over Ethernet mode.
The NodeB can extract the clock from the MSTP network over E1/T1, or obtain
the clock source from the GPS/IP Clock Server.
Backup mode: The FG2a/GOUa is set to the active/standby board, port

backup (Board and port backup apart) or board backup while the port in the load-sharing
mode.
Transport efficiency: Multiple NodeBs share the VC Trunk bandwidth to use

the transport network resources to the maximum extent.
QoS: The RNC and NodeB support the mapping of IEEE 802.1p/q, DSCP, and
VLAN Priority. The transport network supports the IEEE 802.1p/q to schedule the QoS of
different services.
2008-09-14
Huawei Confidential
Page 25 of 133
INTERNAL

4. Data network-based IP networking (IUB/IUR/IUCS/IUPS)
The RNC is connected to the NodeB (Iub interface) through the L2 data network. The
RNC is connected to the SGSN (Iu interface) through the L2 data network. The RNC is
connected to the RNC (Iur interface) through the L2 data network. The interface
address of the interconnected NE is on the same network segment.
Figure 1.8 Data network-based IPRAN L2 networking
The RNC accesses the data network through the GE optical port of the GOUa
board or FE/GE electrical port of the FG2a board. The NodeB/NRNC/MGW/SGSN
accesses the L2 data network through the FE electrical port or optical port.
The NodeB can extract the clock from the ATM transport network over E1/T1,
or obtain the clock source from the GPS/IP Clock Server.
Backup mode: The FG2a/GOUa is set to the active/standby board, port

backup (board backup separated from port backup) or board backup while the port in the
load-sharing mode.
QoS: The RNC, NodeB, core network equipment, and L2 support IEEE
802.1p/q, that is, support the VLAN and VLAN priorities for the QoS scheduling of the
data network. The data network must meet the requirements: delay <40ms, jitter < 15ms,
packet loss ratio < 0.05%
3.2.2 Layer-3 Networking Modes

1. RNC directly connecting to one router
The RNC is connected to the NodeB (Iub interface) through the L3 switching network.
2008-09-14
Huawei Confidential
Page 26 of 133
INTERNAL

The RNC is connected to the SGSN (Iu interface) through the L3 switching network.
The RNC is connected to the RNC (Iur interface) through the L3 switching network. The
interface address of each NE is in different network segments.
Figure 1.9 L3 networking of RNC directly connecting to one router
accesses the transport network through the FE electrical port or optical port. The data is
transmitted in the IP over Ethernet mode.
The NodeB can extract the clock over E1/T1, or obtain the clock source from
the GPS/IP Clock Server.
Backup mode: The FG2a/GOUa is in the board backup and port backup.
The active and standby ports are connected to two ports of one router/L3 switch. The
two ports in the router/L3 switch are configured in the same VLAN. One VLAN interface
address is configured as the RNC gateway.
QoS: The RNC, NodeB, and core network equipment support the mapping of
IEEE 802.1p/q, DSCP, and VLAN Priority. The data network supports the MPLS TE,
MPLS Diffserv, IP Diffserv, and VLAN COS to schedule the service QoS. The data
network must meet the requirements: delay <40ms, jitter < 15ms, packet loss ratio <
0.05%
2008-09-14
Huawei Confidential
Page 27 of 133
INTERNAL

2. RNC directly connecting to two routers
Figure 1.10 L3 networking of RNC directly connecting to two routers
Backup mode: The FG2a/GOUa is in the board backup and port backup. The
board backup and port backup are independent of each other.
The active and standby ports of RNC are respectively connected to two ports of the
active and standby PEs. The RNC is connected to the data transport network through
the PE.
The active and standby ports of the RNC share one IP address (IP1-1). Two ports of the
active and standby PE are configured in the same VLAN, with the configuration of the
VRRP. The VRRP virtual IP (IP-0) functions as the RNC gateway.
MPLS Diffserv, IP Diffserv, and VLAN COS to schedule the QoS of different services.
The data network must meet the requirements: delay <40ms, jitter < 15ms, packet loss
ratio < 0.05%
2008-09-14
Huawei Confidential
Page 28 of 133
INTERNAL

3. Load sharing
Figure 1.11 L3 networking with the load sharing
Backup mode: The FG2a/GOUa is in the board backup and the port is in the
load sharing mode. The double bandwidths are obtained with the reliability guarantee of
the board and transport.
Two ports of the active and standby boards in the load sharing are connected to two
routers/L3 switch. Two ports in the FG2a/GOUa are respectively configured with the IP
address, with the corresponding gateway in the interconnected router/L3 switch.
Through the routing configuration, the IP load sharing is implemented between any
active FE/GE ports.
Route with the load sharing: Multiple different NEXTHOP routes exist in the
network segment to the same destination.
Traffic in the route with the load sharing is distributed on average.
The load sharing is in the load sharing mode to ensure the correct time sequence
of user flows.
2008-09-14
Huawei Confidential
Page 29 of 133
INTERNAL

MPLS Diffserv, IP Diffserv, and VLAN COS to schedule the QoS of different services.
The data network must meet the requirements: delay <40ms, jitter < 15ms, packet loss
ratio < 0.05%
3.2.3 Hybrid Transport Networking
TDMnetwork
Datanetwork
Figure 1.12 IPRAN networking in the hybrid transport - Iub
The Iub interface uses the transport network of different QoSs to carry
services of different QoSs: The service with high QoS is transported through the
dedicated line. The service with low QoS is transported through the low cost transport
network (for example, Ethernet).
The control plane and real-time services and OM services are transported
through the TDM with the high QoS.
Non real-time services are transported through the data network with low QoS.
transmitted in IP over Ethernet mode.
RNC and NodeB access the TDM transport network over E1/T1. The data is transmitted
in IP over MLPPP/PPP over E1/T1 mode.
The NodeB can extract the clock through additionally over E1/T1.
Backup mode:
The FG2a/GOUa is in the board backup, with the port backup or port load sharing mode.
PEUa/POS/UOI_IP is the board backup.
2008-09-14
Huawei Confidential
Page 30 of 133
INTERNAL
3.2.4 ATM/IP Dual-Stack Transport Networking
Figure 1.13 IPRAN networking in the ATM/IP dual-stack transport - Iub
When the bandwidth in the original ATM networking is deficient (in the case of
the HSDPA/HSUPA), the IP transport network can be extended. The transport cost is
saved and the bandwidth is improved.
The original ATM networking remains unchanged. The RNC and NodeB
access the TDM transport network through the E1/T1.
The RNC and NodeB access the data transport network through the new IP
interface board. The RNC accesses the data network through the GE optical port of the
GOUa board or FE/GE electrical port of the FG2a board. The
NodeB/NRNC/MGW/SGSN accesses the transport network through the FE electrical
port or optical port. The data is transmitted in IP over Ethernet mode
The NodeB can extract the clock over E1/T1.
Backup mode: see L2 data networking and L3 data networking.
QoS: The control plane and real-time services and OM services are
transported through the ATM. The non real-time service is transported through the IP.
3.3 Backup Constraint

3.3.1 RNC
1) In the separate mode, the route must be configured in even slots.
2) The backup mode should not be configured in odd slots.
3) After the active/standby Ethernet ports are configured, the corresponding
2008-09-14
Huawei Confidential
Page 31 of 133
INTERNAL

ports of the active/standby boards function as the active/standby ports.
4) The backup port should not be used. The gateway continuity check can be
started.
5) When at least either of the active and standby ports is configured with IP
or port control, two ports are not allowed to be configured as the active
and standby ports.
3.3.2 NodeB:
1)
Boards supporting the board backup:
V210: WMPT/UTRP
V110: NUTI/HBBU. NDTI does not support.
2)
The code backup is performed in the NodeB. Hence, the service is

interrupted in the case of the switchover.
3)
In the backup mode, data is configured only in the active board. By default,
the slot with the smaller ID in the backup group is the active board in the
initial configuration.
Chapter 4 V210 IPRAN Key Configurations

4.1 Relevant Settings of the IPRAN
4.1.1 RNC Side
1. Set the Ethernet port attribute.
Command: SET ETHPORT
Set the VLAN tag attribute of the Ethernet port
The VLAN tag attribute of the Ethernet port cannot be set. By default, the setting is
HYBRID.
Set the work mode of the FE/GE port: The work mode at both ends for the
interconnection must be consistent.
//Set the FE port of the FG2 board to Auto negotiation or forced 100M/Full.
2008-09-14
Huawei Confidential
Page 32 of 133
INTERNAL

SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2, PTYPE=FE, PN=0, AUTO=ENABLE;
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2, PTYPE=FE, PN=0, AUTO=DISABLE,
FESPEED=100M, DUPLEX=Full;
//The work mode of the GE port of the FG2 board cannot be configured. By default, the
value is 1000M/FULL.
//Set the GE port of the GOUa board to Auto negotiation.
SET ETHPORT: SRN=0, SN=14, BRDTYPE=GOU, PTYPE=GE, PN=0, AUTO=ENABLE;
//Set the GE port of the GOUa board to non-auto negotiation. The default value is
1000M/FULL, which cannot be modified.
SET
ETHPORT:
AUTO=DISABLE;
SN=14,
BRDTYPE=GOU,
PTYPE=GE,
PN=0,
Set the percentage of the OAM minimum assurance bandwidth to the port bandwidth.
By default, the value is 0%. The value can be changed according to the planning of
the current network.
SET
ETHPORT:
OAMFLOWBW=0;
SRN=0,
SRN=0,
SN=14,
BRDTYPE=FG2/GOU,
PTYPE=FE/GE,
Set the MTU. By default, the value is 1500 bytes.
SET ETHPORT: SRN=0, SN=14, BRDTYPE=FG2/GOU, PTYPE=FE/GE, MTU=1500,

2. Set the mapping between the DSCP and VLAN PRI.
Command: SET DSCPMAP
SET DSCPMAP: DSCP=X, VLANPRI=X;
The default mapping relation is as follows:
2008-09-14
DSCP
VLAN Priority
0-7
8 - 15
16 - 23
24 - 31
32 - 39
40 - 47
48 - 55
56 - 63
Huawei Confidential
Page 33 of 133
INTERNAL

3. Set the mapping between the queue of the IP type port and the DSCP
SET QUEUEMAP: Q0MINDSCP=XX,
Q3MINDSCP= XX, Q4MINDSCP= XX;
Q1MINDSCP=
XX,
Q2MINDSCP=
XX,
The default setting is as follows:
The mapping between the DSCP value range and Q0-Q5 is as follows:
DSCP
QUEUE ID
40 - 63
32 - 39
24 - 31
16 - 23
8 - 15
0-7
Note:
1) The IP port types include Ethernet port, PPP link, MP group, and IP logical port. Each
IP type port has six service data queues. The priorities of each queue are different. Q0
features the highest priority. Q5 features the lowest priority.
2) Q0MINDSCP - Q4MINDSCP must meet the following conditions:
Q0MINDSCP > Q1MINDSCP > Q2MINDSCP > Q3MINDSCP > Q4MINDSCP
4. Set the DSCP value of the OAM flow
SET QUEUEMAP: SRN=0, SN=14, OAMMINBWKEY=ON, OAMFLOWDSCP=X;
By default, the value is OFF.
Note:
1) The OAM flow cannot be transported through Q0-Q5, but transported through private
queues.
2) If the minimum assurance bandwidth switch of the OAM flow is enabled, the DSCP of
2008-09-14
Huawei Confidential
Page 34 of 133
INTERNAL

the designated OAM flow should not be identical with the DSCP value of any IPPATH.
5. Set the corresponding DSCP of the SCTP link and whether to enable the VLAN.
ADD SCTPLNK: DSCP=X, VLANFlAG=ENABLE, VLANID=X;
Default configurations: DSCP=62. The VLAN is not enabled.
6. Set the corresponding DSCP of the IPPATH and whether to enable the VLAN.
ADD IPPATH: PATHT=X, DSCP=X, VLANFlAG=ENABLE, VLANID=X;
The default setting is as follows:
IPPATH Type
DSCP
HQ_RT
46
LQ_RT
34
HQ_NRT
18
LQ_NRT
10
HQ_HSDPART
38
LQ_HSDPART
30
HQ_HSDPANRT
14
LQ_HSDPANRT
HQ_HSUPART
36
LQ_HSUPART
28
HQ_HSUPANRT
12
LQ_HSUPANRT
HQ_QOSPATH
Null
LQ_QOSPATH
The value is
determined
according to the
configuration in the
TRMMAP.
VLANID Flag
Disable
Disable
Disable
Disable
Disable
Disable
Disable
7. Add the mapping between the destination IP and VLANID

ADD VLANID: IPADDR="X.X.X.X", VLANID=X;
If the VLAN is not enabled in Steps 5 and 6, the following two purposes are achieved by
running this command:
1) IP packets sending to the destination IP address are labeled with the designated VLAN
2008-09-14
Huawei Confidential
Page 35 of 133
INTERNAL

ID.
2) ARP request packets of the destination IP address are labeled with the designated
VLAN ID.
8. Set the mapping between the PHB and DSCP
ADD TRMMAP: ITFT=IUB_IUR_IUCS/IUPS, TRANST=IP, EFDSCP=X, AF43 DSCP=X,
AF42 DSCP=X, AF41 DSCP=X, AF33 DSCP=X, AF32 DSCP=X, AF31 DSCP=X, AF23
DSCP=X, AF22 DSCP=X, AF21 DSCP=X, AF13 DSCP=X, AF12 DSCP=X, AF11
DSCP=X, BEDSCP=X;
The default mapping relation is as follows:
PHB
DSCP
EF
AF4
AF3
AF2
AF1
46
AF43
38
AF42
36
AF41
34
AF33
30
AF32
28
AF31
26
AF23
22
AF22
20
AF21
18
AF13
14
AF12
12
AF11
10
BE
4.1.2 NodeB Side

1. Set the Ethernet port attribute
Command: SET ETHPORT
Set the work mode of the FE port: The work mode at both ends for the interconnection
must be consistent.
2008-09-14
Huawei Confidential
Page 36 of 133
INTERNAL

2. Set the priority of the signaling and OM
Command: SET DIFPRI
Related parameters are as follows:
Name
Description
Priority Rule
Value range: IPPRECEDENCE,DSCP
Signal Priority
Value range:
0 - 7: when PRIRULE is IPPRECEDENCE,
0 - 63: when PRIRULE is DSCP.
OM Priority
Value range:
0 - 7: when PRIRULE is IPPRECEDENCE,
0 - 63: when PRIRULE is DSCP.
The relations between the signaling, service, and DSCP values are as follows:
1) Iub interface signaling data
Signaling data over Iub interface is transported with SCTP. The sending of the
DSCP priority in the SCTP protocol package is determined by the DSCP in the
Signaling Priority type by running SET DIFPRI.
2) Common channel
The common channel transports control information, with the higher priority. The
priority is equivalent to the NCP/CCP data. For services in the common channel,
data from the RNC to the NodeB is transmitted through the DSCP on the RT
PATH. The data returned from the NodeB to the RNC is transmitted through the
DSCP of the Signal Priority by running SET DIFPRI.
3) R99 service (user voice and PS network access data)
The NodeB sends the DSCP priority of these UDP packages. When the connection
is established, the RNC notifies the NodeB. The DSCP settings are determined by
the RNC.
4) HSDPA
Data from the RNC to the NodeB is the downloaded data. The DSCP value of the
HSDPA_IPPATH configured by the RNC determines the DSCP for the data
transmitting. The flow control information frame returned from the NodeB to the
RNC is uploaded by using the DSCP value of the Signal Priority configured by
running SET DIFPRI.
5) HSUPA
The data from the NodeB to the RNC and data from the RNC to the NodeB are
transmitted by using the DSCP value sent in the case of the RNC link setup.
2008-09-14
Huawei Confidential
Page 37 of 133
INTERNAL

6) OM maintenance data
The OM maintenance data is transported through the TCP. The sending of the
DSCP priority in the packages is determined by the DSCP in the OM type by
running SET DIFPRI.
Precautions for the configuration:

1) Priority Rule: It has two options: IPPRECEDENCE and DSCP. The
recommended configuration is DSCP. The IPPRECEDENCE is labeled by using
the priority field in the type of service (TOS) field in the IP header. The DSCP is
configured according to the DSCP value of the Diffserv.
One IPPRECEDENCE corresponds to a range of the DSCP value.
DSCP range: [A,B) Specific value:
I PPRECEDENCE DSCP
0 000000~001000
1 001000~010000
2 010000~011000
3 011000~100000
4 100000~101000
5 101000~110000
6 110000~111000
7 111000~111111
2) The SIG precedence is configured to be consistent with the DSCP value of the
SCTP in the RNC.
3. Set the configuration between the DSCP and VLAN
Command: SET VLANCLASS
In the VLAN configurations, the VLANIDs vary with protocol types. The NodeB
distinguishes according to the following rules:
Protocol type = SCTP: Iub interface signaling data includes only the NCP/CCP data.
Correspond to the SIG class by running the command SET VLANCLASS.
SET VLANCLASS: VLANGROUPNO=X,
VLANID=X, VLANPRIO=X;
TRAFFIC=SIG,
INSTAG=ENABLE,
Protocol type = UDP: Voice, PS network access, and H download. It applies to data
of common channels. In addition, the local UDP port number is in the legal range of
the NodeB. It corresponds to USERDATA class by running the command SET
VLANCLASS.
2008-09-14
Huawei Confidential
Page 38 of 133
INTERNAL

SET VLANCLASS: VLANGROUPNO=X, TRAFFIC=USERDATA,
INSTAG=ENABLE, VLANID=X, VLANPRIO=0;
Protocol type = UDP: The local UDP port number is not in the legal range of the
NodeB. It is other applications (for example, TRACERT). It corresponds to OTHER
class by running the command SET VLANCLASS.
SET VLANCLASS: VLANGROUPNO=X,
SRVPRIO=X,
TRAFFIC=OTHER,
INSTAG=ENABLE,
Protocol type = TCP: Data of OM management and maintenance. It corresponds to

the OM class by running the command SET VLANCLASS.
Protocol type = Others: Includes, but not limited to, ICMP, ARP, and DHCP. The value
is treated as other types. It corresponds to the OM class by running the command SET
VLANCLASS.
SET
VLANCLASS:
VLANGROUPNO=X,
TRAFFIC=OM,
INSTAG=ENABLE,
4. Set the VLAN based on the next hop (V210)

Command: ADD VLANMAP
Set the VLANID based on the next hop (V210). The configuration methods are as
follows:
1) All data is labeled with the same VLAN.
When running the command ADD VLANMAP, select the single VLAN for the
VLANMODE. That is, all data with the same next hop address is labeled with the VLAN.
ADD
VLANMAP:
NEXTHOPIP="12.13.14.15",
INSTAG=ENABLE, VLANID=100, VLANPRIO=1;
VLANMODE=SINGLEVLAN,
2) Label different VLANs according to data types

When running the command ADD VLANMAP, select VLANGRP for the VLANMODE.
To set the VLAN in the VLANGRP, run SET VLANCLASS.
ADD
VLANMAP:
VLANGROUPNO=0;
NEXTHOPIP="12.13.14.15",
VLANMODE=VLANGROUP,
According to the correspondence between the service and DSCP, the signaling at the
NodeB side, uplink frame of the common channel, the uplink control frame of the
HSDPA use the DSCP value of the SIG type by running the command SET DIFPRI.
The signaling uses the SCTP. The uplink frame of the common channel and the uplink
control frame of the HSDPA use the UDP. Hence, the VLANs should be set
respectively.
2008-09-14
Huawei Confidential
Page 39 of 133
INTERNAL

5. Example
SET DIFPRI: PRIRULE=DSCP, SIGPRI=48, OMPRI=20;
VLAN configuration of the signaling:
SET
VLANCLASS:
VLANGROUPNO=0,
VLANID=100, VLANPRIO=6;
TRAFFIC=SIG,
INSTAG=ENABLE,
VLAN configuration of the uplink frame of the common channel and the uplink control
frame of the HSDPA
SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA,
SRVPRIO=48,
If the priority rule by running the command SET DIFPRI is IPPRECEDENCE, use one
value in the DSCP range corresponding to the IPPRCEDENCE by running the
command SET VLANCLASS.
Note: V110 does not support the label of the VLAN based on the next hop; therefore,
the command ADD VLANMAP does not apply. Enable the VLANTAG by running the
command SET ETHPORT. Then, run the command SET VLANCLASS. The
configuration method is the same as that by running the command SET VLANCLASS
in V210.
4.2 Constraint and Restrictions of IP Address and Configuration

This section describes current constraints on the IP transport configurations. In the
networking, data is planned according to the constraints.
4.2.1 Constraints of RNC IP Address

The interface IP address, user plane IP address, and control plane IP address should
not be 0.*.*.*, 127.*.*.*, 255.255.255.255, RNC internal subnet segment, RNC debug
subnet segment (by running the command SET SUBNET. The default network
segment is 192), BAM internal/external network segment, and M2000 network
segment.
Constraints of RNC IP address network segment:
1. All Ethernet port address (ETHIP) in the RNC interface board should not be on the
2. The device IP address (DEVIP) of the same interface board in the RNC should not
be on the same network segment.
3. The device IP address (DEVIP) and ETHIP of the same interface board in the RNC
2008-09-14
Huawei Confidential
Page 40 of 133
INTERNAL

should not be on the same network segment.
4. The device IP address should not be the same as the configured IP address
(including local/peer IP address of the PPP link, local/peer IP address of the MLPPP
group, Ethernet port IP address, IPPATH peer address, SCTP link peer address) in the
RNC.
5. The Ethernet port IP address should not be the same as the configured IP address
(including local/peer IP address of the PPP link, local/peer IP address of the MLPPP
group, and the device IP address) in the RNC.
6. The local IP address of the MLPPP group and PPPLNk should not be the same as
the local address in the RNC, or the same as the peer address (for example, PPP port
IP address, ETH port address, ETH gateway, and logical IP address) in the RNC. The
peer address should not be the same as the local address in the RNC.
4.2.2 Constraints of NodeB IP Address

The NodeB interface address, user plane address, control plane address, or
maintenance address should not be 0.*.*.*, 127.*.*.*, 255.255.255.255, and 10.22.1.x
(internal restricted address in the RAN6.0 NodeB).
Constraints of NodeB IP address network segment:
One interface can be configured with up to four IP addresses, which can be on the
The addresses of different interfaces should not be on the same network segment.
The interface address and the maintenance address may be on the same network
segment.
The peer addresses such as the MLPPP group and PPPLNK should not be the same
as the configured address in the NodeB. The local address should not be the same as
the configured interface address in the NodeB.
Chapter 5 Example of Iub Interface Configuration

5.1 Version Description
RNC version: V210060
2008-09-14
Huawei Confidential
Page 41 of 133
INTERNAL
5.2 IUB Interface Protocol Stack

In the case of the Iub over IP, the compliant sequence in adding Iub interface data
should be consistent with the protocol structure, that is, from the lower layer to the
upper layer. Data is configured from the control plane to the user plane.
The following figure shows IP-based protocol stack of the Iub interface.
Figure 1.14 Iub interface protocol stack
5.3 Data Planning

In the case of the IP transport, the interconnected data (unless otherwise specified) of
the Iub interface is obtained through the negotiation between the RNC and the NodeB.
Before configuring IP-based Iub interface data, confirm the following information:
L2 networking or L3 networking
Ethernet-based transport, private line-based transport, or IP hybrid transport
The IP transport solutions vary with transport networks used in the Iub interface.
2008-09-14
Huawei Confidential
Page 42 of 133
INTERNAL
5.3.1 Data Planning in L2 Networking

This section describes the data planning in the case of the use of the FE. For the data
planning of PPP/MLPPP, see section 7.3.3.
1. Data planning of physical layer and data link layer
Data Item
RNC Side
NodeB
Data Source
FG2/GOUa
WMPT
Internal planning
10.10.10.2/24
10.10.10.1/24
Network planning
Whether
to
backup/backup
mode
Yes/Board
backup,
backup
No
Internal planning
Subrack No./Slot
No./Port No.
0/18/0
0/6/0
Port
IP
address/subnet
mask
10.10.10.1/24
10.10.10.2/24
Master
address/slave
address
FE Interface
port type
data
Gateway
address
board
IP
IP
IP
port
Network planning
2. Data planning of control plane

Data Item
NCP
RNC
NodeB
IUB
congestion
control switch
OFF
OFF
NodeB Max Hsdpa

User Number
3840
3840
58080
9000
Local SCTP Port No.
SCTP signaling link Server

mode
Client
SPU Slot No.
SPU Subsystem No.
DSCP
62
62
First local IP address
10.10.10.1/24
10.10.10.2/24
Second
address
local
2008-09-14
IP
Huawei Confidential
Data Source
Negotiation data
Page 43 of 133
INTERNAL

Whether
to
bind Yes/18/20
logical
port/logical
port slot No. and port
No.
Whether
to
VLAN/VLAN ID
10
add 10
Local SCTP Port No.

CCP
58080
9001
SCTP signaling link Server

mode
Client
Port No.
SPU Slot No.
SPU Subsystem No.
DSCP
62
62
First local IP address
10.10.10.1/24
10.10.10.2/24
Second
address
local
IP
Whether
to
bind Yes/18/20
logical
port/logical
port slot No. and port
No.
Whether
to
VLAN/VLAN ID
10
add 10
3. Data planning of user plane

Data Item
RNC
NodeB name
RNC8-BBU1
BBU1
Transport Neighbor Node

ID
IP Protocol Version
IP path 1
NodeB
IPv4
Network
planning
Negotiation
data
Eth
Eth
IP Path flag
PATH Type
RT
RT
Whether to bind logical

port/logical port slot No.
and port No.
Yes/18/20
Local IP address/subnet
mask
10.10.10.1/24
10.10.10.2/24
Huawei Confidential
Negotiation
data
IPv4
Port type
2008-09-14
Data Source
Network
planning
Page 44 of 133
INTERNAL

Data Item
IP path2
IP path 3
RNC
NodeB
Use
VLAN
or
not/Enabled VLAN ID
YES/VLAN10
YES/VLAN10
PATH check flag
ENABLE
Check IP address
10.10.10.2/24
DSCP
46
46
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
NRT
NRT

and port No.
Yes/18/20
mask
10.10.10.1/24
10.10.10.2/24
Use
VLAN
or
not/Enabled VLAN ID
YES/VLAN10
YES/VLAN10
PATH check flag
ENABLE
Check IP address
10.10.10.2/24
DSCP
18
18
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
HSDPANRT
HSDPANRT

and port No.
Yes/18/20
2008-09-14
Huawei Confidential
Data Source
Internal
planning
Negotiation
data
Network
planning
Internal
planning
Negotiation
data
Page 45 of 133
INTERNAL

Data Item
IP path 4
RNC
NodeB
mask
10.10.10.1/24
10.10.10.2/24
Use
VLAN
or
not/Enabled VLAN ID
YES/VLAN10
YES/VLAN10
PATH check flag
ENABLE
Check IP address
10.10.10.2/24
DSCP
10
10
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
HSUPANRT
HSUPANRT

and port No.
Yes/18/20
mask
10.10.10.1/24
10.10.10.2/24
Use
VLAN
or
not/Enabled VLAN ID
YES/VLAN10
YES/VLAN10
PATH check flag
ENABLE
Check IP address
10.10.10.2/24
DSCP
10
10
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
NO
NO
FPMUX Enable
Data Source
Network
planning
Internal
planning
Negotiation
data
Network
planning
Internal
planning
4. Data planning of management plane

Data Item
2008-09-14
RNC
NodeB
Huawei Confidential
Data Source
Page 46 of 133
INTERNAL

OMIP address at
NodeB side
10.10.10.3/24 (If NodeB

OMIP and the interface IP
are on the same network
segment, enable the ARP
proxy function of the
interface)
Interface IP address at NodeB side
10.10.10.2/24
Gateway IP address at NodeB side
10.10.10.1/24
Gateway IP address 10.10.10.2/24

at RNC side
Interface IP address 10.10.10.1/24

at RNC side
BAM
external 10.161.215.242/24
network IP address
IP
address
M2000 Server
of
10.161.215.230/24
Network planning
5.3.2 Data Planning in L3 Networking

1. IP addresses planning
The following figure shows the Ethernet-based IP planning.
If the load-sharing mode is not used and only one IP address is used at the RNC side, the
ETHIP of the FG2 can be used directly. The DEVIP should not be configured and used. In the
example, the DEVIP used in the SCTP and IPPATH local address is optional, and indicates
only the configuration and usage of the DEVIP.
Figure 1.15 IP planning of Ethernet-based L3 networking
2008-09-14
Huawei Confidential
Page 47 of 133
INTERNAL

Data Item
FE
por
t
dat
a
RNC
Side
Interface
type
board
Gateway
address
IP
NodeB
FG2/GOUa
WMPT
Internal planning
10.10.10.1/26
16.16.16.1/26
Network planning
No
Internal planning
Backup/backup
mode
Yes/Board
backup,
backup
Subrack No./Slot
No./Port No.
0/18/0
0/6/0
Port
IP
address/subnet
mask
10.10.10.2/26
16.16.16.2/26
Master
address/slave
address
IP
IP
Data Source
port
Network planning

RNC
Data Item
IUB congestion
switch
NodeB
control
OFF
OFF
NodeB Max Hsdpa User

Number
3840
3840
Port
58080
9000
SCTP signaling link

mode
Server
Client
SPU Slot No.
SPU
No.
62
62
NCP
Local
No.
SCTP
Subsystem
DSCP
First
local
address
IP
10.10.10.100/26
16.16.16.2/26
Second
address
IP
local
2008-09-14
Huawei Confidential
Data Source
Negotiation data
Page 48 of 133
INTERNAL
CCP
Whether to bind
logical port/logical
port slot No. and
port No.
Yes/18/20
Whether to add
VLAN/VLAN ID
Local
No.
port
58080
9001
SCTP signaling link

mode
Server
Client
Port No.
SPU Slot No.
SPU
No.
62
62
SCTP
Subsystem
DSCP
First
local
address
IP
10.10.10.100/26
16.16.16.2/26
Second
address
IP
Whether to bind
port slot No. and
port No.
Yes/18/20
Whether to add
VLAN/VLAN ID
local

RNC
Data Item
IP path 1
NodeB
Data Source
NodeB name
RNC8-BBU1
BBU1
Transport Neighbor Node

ID
IP Protocol Version
IPv4
IPv4
Network
planning
Port type
Eth
Eth
IP Path flag
Negotiation
data
PATH Type
RT
RT

and port No.
Yes/18/20
2008-09-14
Huawei Confidential
Negotiation
data
Page 49 of 133
INTERNAL

Data Item
10.10.10.100/26
16.16.16.2/26
Use VLAN or not/Enabled

VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
46
46
bandwidth
20000
20000
Receive bandwidth (kbps)
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
NRT
NRT

and port No.
Yes/18/20
mask
10.10.10.100/26
16.16.16.2/26

VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
18
18
bandwidth
20000
20000
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
HSDPANRT
HSDPANRT

and port No.
Yes/18/20
Transmit
(kbps)
IP path 3
NodeB
mask
Transmit
(kbps)
IP path2
RNC
2008-09-14
Huawei Confidential
Data Source
Network
planning
Internal planning
Negotiation
data
Network
planning
Internal planning
Negotiation
data
Page 50 of 133
INTERNAL

Data Item
NodeB
mask
10.10.10.100/26
16.16.16.2/26

VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
10
10
bandwidth
20000
20000
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
HSUPANRT
HSUPANRT

and port No.
Yes/18/20
mask
10.10.10.100/26
16.16.16.2/26

VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
10
10
bandwidth
20000
20000
20000
20000
FPMUX Enable
NO
NO
Transmit
(kbps)
IP path 4
RNC
Transmit
(kbps)
Data Source
Network
planning
Internal planning
Negotiation
data
Network
planning
Internal planning

Data Item
2008-09-14
RNC
NodeB
Huawei Confidential
Data Source
Page 51 of 133
INTERNAL

OMIP address at
NodeB side
9.9.9.9/26 (If NodeB

OMIP and the interface
IP are on the same
network
segment,
enable the ARP proxy
function of the interface)
16.16.16.2/26
16.16.16.1/26

at RNC side

at RNC side
BAM
external 10.161.215.242/24
network IP address
IP
address
M2000 Server
of
10.161.215.230/24
Network planning
5.3.3 Data Planning of Hybrid Transport Networking

In the case of the hybrid transport, signaling and real-time services are transmitted through the
PPP, and BE services are transmitted through the FE.
1. IP addresses planning
The RNC and NodeB (3X1) access the SDH optical transport network through the
Add/Drop Multiplexer (ADM) respectively. The RNC is connected to the NodeB
through the SDH or Plesiochronous Digital Hierarchy (PDH) transport network.
Meanwhile, the RNC and NodeB access the Ethernet (L3 networking).
E1/T1
NodeB1
ADM
PDH/SDH
ADM
E1/T1
BSC6800
Ethernet
Figure 1.16 IP RAN hybrid transport networking
2008-09-14
Huawei Confidential
Page 52 of 133
INTERNAL

The following figure shows the Ethernet-based IP planning.
Figure 1.17 IP planning of Ethernet-based L3 networking
The following figure shows the E1-based IP planning.
Figure 1.18 E1-based IP planning

Data Item
FE
port
data
RNC Side
NodeB
Data Source
Interface board type
FG2/GOUa
WMPT
Internal planning
Gateway IP address
10.10.10.1/26
16.16.16.1/26
Network
planning
Backup/backup
mode
Yes/Board
backup
separated from
port backup
No
Subrack
No./Slot
No./Port No.
0/18/0
0/12/0
Port
address/subnet
mask
10.10.10.2/26
16.16.16.2/26
2008-09-14
IP
Huawei Confidential
Internal planning
Network
planning
Page 53 of 133
INTERNAL

Data Item
RNC Side
Master
address/slave
address
IP
IP
NodeB
Data Source
PPP
Interface board type
PEU/UOI_IP/POUa
WMPT
/MLPPP
Gateway IP address
Link
PPP
Subrack
No./Slot
No./E1T1 Port No.
0/14/0
0/12/0
MLPPP group No.
PPP/MLPPP link No.
Local IP address,
subnet mask
13.13.13.1/24
13.13.13.2/24
Network
planning
Bearer timeslot
TS1&TS2&TS3
TS1&TS2&TS3
Negotiation data
&TS4&TS5&TS6
&TS4&TS5&TS6
Link
data
Internal planning
The settings are not

required when the RNC
uses UOI_IP and POUa.
RNC
Data Item
NCP
NodeB
Iub
congestion
control switch
OFF
OFF
NodeB
Hsdpa
Number
Max
User
3840
3840
Port
58080
9000
SCTP signaling link

mode
Server
Client
62
62
Local
No.
SCTP
SPU Slot No.

SPU
No.
Subsystem
DSCP
First
local
address
IP
13.13.13.1/24
13.13.13.2/24
Second
address
IP
local
2008-09-14
Huawei Confidential
Data Source
Negotiation data
Page 54 of 133
INTERNAL
CCP
Whether to bind
port slot No. and
port No.
Whether to add
VLAN/VLAN ID
Local
No.
port
58080
9001
SCTP signaling link

mode
Server
Client
Port number
62
62
SCTP
SPU Slot No.

SPU
No.
Subsystem
DSCP
First
local
address
IP
13.13.13.1/24
13.13.13.2/24
Second
address
IP
Whether to bind
port slot No. and
port No.
Whether to add
VLAN/VLAN ID
local

RNC
Data Item
IP path 1
NodeB
Data Source
NodeB name
RNC8-BBU1
BBU1
Transport neighbor node

flag
IP protocol version
IPv4
IPv4
Network
planning
Port type
PPP
PPP
IP Path flag
Negotiation
data
PATH type
RT
RT

and port No.
2008-09-14
Huawei Confidential
Negotiation
data
Page 55 of 133
INTERNAL

Data Item
IP path2
IP path 3
RNC
NodeB
mask
13.13.13.1/24
13.13.13.2/24
Use
VLAN
or
not/Enabled VLAN ID
PATH check flag
ENABLE
Check IP address
13.13.13.2/24
DSCP
46
46
Transmit
(kbps)
bandwidth
1800
1800
Receive
(kbps)
bandwidth
1800
1800
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
NRT
NRT

and port No.
Yes/18/20
mask
10.10.10.100 /26
16.16.16.2/26
Use
VLAN
or
not/Enabled VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
18
18
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
HSDPANRT
HSDPANRT
2008-09-14
Huawei Confidential
Data Source
Network
planning
Internal
planning
Negotiation
data
Network
planning
Internal planning
Negotiation
data
Page 56 of 133
INTERNAL

Data Item
IP path 4
RNC
NodeB

and port No.
Yes/18/20
mask
10.10.10.100/26
16.16.16.2/26
Use
VLAN
or
not/Enabled VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
10
10
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
FPMUX Enable
NO
NO
Port type
Eth
Eth
IP Path flag
PATH type
HSUPANRT
HSUPANRT

and port No.
Yes/18/20
mask
10.10.10.100/26
16.16.16.2/26
Use
VLAN
or
not/Enabled VLAN ID
PATH check flag
ENABLE
Check IP address
16.16.16.2/26
DSCP
10
10
Transmit
(kbps)
bandwidth
20000
20000
Receive
(kbps)
bandwidth
20000
20000
NO
NO
FPMUX Enable
Data Source
Network
planning
Internal planning
Negotiation
data
Network
planning
Internal planning

Data Item
RNC
2008-09-14
NodeB
Huawei Confidential
Data Source
Page 57 of 133
INTERNAL

OMIP address at
NodeB side
9.9.9.9/26 (If NodeB OMIP

and the interface IP are on
the
same
network
segment, enable the ARP
proxy function of the
interface)
16.16.16.2/26
16.16.16.1/26

at RNC side

at RNC side
BAM
external 10.161.215.242/24
network IP address
IP
address
M2000 Server
of
10.161.215.230/24
Network
planning
5.3.4 Data Planning of Dual Stack Transport Networking

With the development of data services, especially with the introduction of HSDPA and HSUPA,
there is an increasing demand for bandwidth on the Iub interface. The transmission based on
ATM over E1, however, is expensive. Data services produce decreasing benefits for telecom
operators. Therefore, the telecom operators are eager for a low-cost Iub transmission solution.
In such a situation, ATM/IP dual stack transport is introduced. In addition to the guarantee of
services, this transport reduces costs of data transmission on the Iub interface.
Based on the Quality of Service (QoS) and bandwidth requirements, ATM/IP dual stack
transport implements data transmission as follows:
Voice, streaming, and signaling services have a relatively low requirement for
the bandwidth and high requirement for the QoS. Such services are
transmitted on ATM networks.
BE services and HSDPA/HSUPA services have a relatively high requirement

for the bandwidth and low requirement for the QoS. Such services are
transmitted on IP networks.
Note: The transmission paths carrying different services are configurable (depending on the
data planning).
ATM/IP dual stack transport protects the investment of the existing ATM networks, reduces the
impact of IP transport on the ongoing services on the ATM networks, and meets the
requirements of telecom operators for highly efficient and low-cost networks and for flexible
networking.
2008-09-14
Huawei Confidential
Page 58 of 133
INTERNAL

1. Networking Description
The ATM/IP dual stack transport enables hybrid transport of services that have different QoS
requirements. The services of high QoS requirements, such as voice, streaming, and signaling,
are transmitted on the ATM network. The services of low QoS requirements, such as HSDPA
and HSUPA, are transmitted on the IP network.
Figure 1.19 Dual stack transport networking
To support this networking mode, an RSS or RBS of the RNC is configured with both ATM and
IP interface boards.
The ATM interface board can be an AEUa, AOUa, or UOIa (UOI_ATM). It is

connected to the ATM network through the E1/T1 port, channelized STM-1
port, or OC-3C port.
The IP interface board can be an FG2a, GOUa, POUa, or UOIa (UOI_IP). It is

connected to the IP network through the Ethernet port, E1/T1 port,
channelized STM-1 port, or OC-3C port.
The NodeB is connected to the ATM and IP networks through its ATM and IP interface boards
respectively.
2. Networking Planning
Note: This configuration is based on the following scenarios: On the RNC side, the AOUa
serves as the ATM interface board and the FG2a serves as the IP interface board. The
signaling, R99 real-time (RT), and OM services are transmitted on the ATM network, and the
R99 non-real-time (NRT), HSDPA, and HSUPA services are transmitted on the IP network.
For dual backup channels of signaling and OM services, the related parameters should be
modified in the configuration.
Figure 1.20 ATM configuration planning
2008-09-14
Huawei Confidential
Page 59 of 133
INTERNAL
Figure 1.21 IP address planning for layer 3 networking over Ethernet
Figure 1.22 IP address planning for layer 2 networking over Ethernet
Data Planning at the Physical Layer and Data Link Layer

Data planning for ATM transport
2008-09-14
Huawei Confidential
Page 60 of 133
INTERNAL
Data planning for layer 3 networking
Data planning for layer 2 networking
2008-09-14
Huawei Confidential
Page 61 of 133
INTERNAL
Data Planning on the Control Plane
Data Planning on the User Plane
2008-09-14
Huawei Confidential
Page 62 of 133
INTERNAL
2008-09-14
Huawei Confidential
Page 63 of 133
INTERNAL
2008-09-14
Huawei Confidential
Page 64 of 133
INTERNAL
Data Planning on the Management Plane
2008-09-14
Huawei Confidential
Page 65 of 133
INTERNAL
5.4 Configuration Procedures at RNC Side

Version in the configuration example: RNC uses V210060
5.4.1 Configuration of Layer-2 Networking

In the case of the L2 networking, the port IP f the RNC interface board and the NodeB IP are on
the same network segment. For the configuration of PPP link, see section 7.4.3.
1. Connect the network cable.
Label of hardware connection: The FG2 board of the RNC is in slot 18/19 in subrack 0. The FE
port is 0. The binding between the board backup and port backup is used.
2. Perform the configuration in the RNC in the MML
Configure the physical layer data.
//Set the Ethernet port attributes. The FE port of the RNC and the FE port interconnected to the
RNC must be set to 100M/FULL.
SET ETHPORT: SRN=0, SN=18, BRDTYPE=FG2, PTYPE=FE,
AUTO=DISABLE,
FESPEED=100M,
DUPLEX=Full,
FC=ON,
FLOWCTRLSWITCH=ON, FCINDEX=1;
PN=0, MTU=1500,
OAMFLOWBW=1,
Parameter Description:
AUTO
Auto
negotiation
or not
FESPEED FE port rate
2008-09-14
This parameter is determined according to the device

interconnected to the RNC. If the interconnected device is in the
auto negotiation mode, the RNC port is also in the auto negotiation
mode. Otherwise, the RNC port is set to non auto negotiation
mode. The GE port must be in the auto negotiation mode.
This parameter is designated according to the rate of the peer
Huawei Confidential
Page 66 of 133
INTERNAL
device. Generally, the value is 100M/1000M.

DUPLEX
Work mode
Half duplex: Data packets cannot be transmitted when the system

is receiving data packets.
Full duplex: The system can receive and transmit data at the same
time.
Generally, the parameter is set to Full duplex.
//Add the IP address of the Ethernet port. The IP address of the RNC interface board is
10.10.10.1/24.
ADD ETHIP: SRN=0,
MASK="255.255.255.0";
SN=18,
PN=0,
IPTYPE=PRIMARY,
IPADDR="10.10.10.1",
Add the configuration of the data link layer.
//Data link layer data should not be configured in the FE/GE port.
//Add the logical port.
ADD
LGCPORT:
SRN=0,
RSCMNGMODE=EXCLUSIVE,
FLOWCTRLSWITCH=ON;
LPNSN=18,
CNOPINDEX=0,
LPN=20,
PNSN=18,
PN=0,
BWADJ=OFF,
CIR=313,
Add the control plane data, including SCTP signaling link, NodeB basic information, NodeB
algorithm parameter, transport neighbor node, and Iub port data (NCP link and CCP link).
//At least two SCTP links are available, one is used for the NCP, and the other is used for the
CCP. The RNC selects the server mode. The local IP is the FE IP of the RNC interface board.
The peer IP is the FE IP of the NodeB interface board. For the port number, see the negotiation
data table.
ADD SCTPLNK: SRN=0, SN=0, SSN=0, SCTPLNKN=1, MODE=SERVER, APP=NBAP,
LOCIPADDR1="10.10.10.1",
PEERIPADDR1="10.10.10.2",
PEERPORTNO=9000,
LOGPORTFLAG=YES,
LOGPORTSN=18,
LOGPORTNO=20,
VLANFlAG=ENABLE,
VLANID=10, SWITCHBACKFLAG=YES;
LOCIPADDR1="10.10.10.1",
PEERPORTNO=9001,
LOGPORTFLAG=YES,
LOGPORTSN=18,
LOGPORTNO=20,
VLANFlAG=ENABLE,
VLANID=10, SWITCHBACKFLAG=YES;
//Add NodeB and algorithm parameters.
ADD NODEB: NodeBName="RNC8-BBU1",
TnlBearerType=IP_TRANS,
SharingSupport=NON_SHARED, CnOpIndex=0;
2008-09-14
NodeBId=1, SRN=0, SN=0, SSN=0,

IPTRANSAPARTIND=NOT_SUPPORT,
Huawei Confidential
Page 67 of 133
INTERNAL

ADD
NODEBALGOPARA:
NodeBLdcAlgoSwitch=IUB_LDR-1&LCG_CREDIT_LDR-1,
NodeBHsdpaMaxUserNum=3840, NodeBHsupaMaxUserNum=3840;
//Add the transport neighbor node.
ADD ADJNODE: ANI=1, NAME="NODEB1", NODET=IUB, NODEBID=1, TRANST=IP;
//Add the link of the NodeB control port.
ADD NCP: NODEBNAME="RNC8-BBU1", CARRYLNKT=SCTP, SCTPLNKN=1;
ADD CCP: NODEBNAME="RNC8-BBU1", PN=0, CARRYLNKT=SCTP, SCTPLNKN=2;
Configure the mapping relation of transport resources and activity factor table.
//Add the mapping relation of transport resources to map services with different QoS to the
corresponding transport channels. In this way, the transport bandwidth is used effectively.
ADD TRMMAP: TMI=1, ITFT=IUB_IUR_IUCS, TRANST=IP, EFDSCP=46, AF43DSCP=38,
AF42DSCP=36,
AF41DSCP=34,
AF33DSCP=30,
AF32DSCP=28,
AF31DSCP=26,
AF23DSCP=22,
AF22DSCP=20,
AF21DSCP=18,
AF13DSCP=14,
AF12DSCP=12,
AF11DSCP=10,
BEDSCP=0,
CCHPRIPATH=HQ_IPRT,
CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT,
SRBSECPATH=NULL,
VOICEPRIPATH=HQ_IPRT,
VOICESECPATH=NULL,
CSCONVPRIPATH=HQ_IPRT,
CSCONVSECPATH=NULL,
CSSTRMPRIPATH=HQ_IPRT, CSSTRMSECPATH=NULL, PSCONVPRIPATH=HQ_IPRT,
PSCONVSECPATH=NULL, PSSTRMPRIPATH=HQ_IPRT, PSSTRMSECPATH=HQ_IPRT,
PSHIGHINTERACTPRIPATH=HQ_IPNRT,
PSHIGHINTERACTSECPATH=HQ_IPRT,
PSMIDINTERACTPRIPATH=HQ_IPNRT,
PSMIDINTERACTSECPATH=HQ_IPRT,
PSLOWINTERACTPRIPATH=HQ_IPNRT,
PSLOWINTERACTSECPATH=HQ_IPRT,
PSBKGPRIPATH=HQ_IPNRT, PSBKGSECPATH=HQ_IPRT, HDSRBPRIPATH=HQ_IPRT,
HDSRBSECPATH=NULL,
HDCONVPRIPATH=HQ_IPRT,
HDCONVSECPATH=NULL,
HDSTRMPRIPATH=HQ_IPRT,
HDSTRMSECPATH=NULL,
HDHIGHINTERACTPRIPATH=HQ_IPHDNRT, HDHIGHINTERACTSECPATH=HQ_IPHUNRT,
HDMIDINTERACTPRIPATH=HQ_IPHDNRT,
HDMIDINTERACTSECPATH=HQ_IPHUNRT,
HDLOWINTERACTSECPATH=HQ_IPHUNRT,
HDBKGPRIPATH=HQ_IPHDNRT,
HDBKGSECPATH=NULL,
HUSRBPRIPATH=HQ_IPRT,
HUSRBSECPATH=NULL,
HUCONVPRIPATH=HQ_IPRT, HUCONVSECPATH=NULL, HUSTRMPRIPATH=HQ_IPRT,
HUSTRMSECPATH=NULL,
HUHIGHINTERACTPRIPATH=HQ_IPHUNRT,
HUHIGHINTERACTSECPATH=HQ_IPHDNRT, HUMIDINTERACTPRIPATH=HQ_IPHUNRT,
HUMIDINTERACTSECPATH=HQ_IPHDNRT,
HULOWINTERACTPRIPATH=HQ_IPHUNRT,
HULOWINTERACTSECPATH=HQ_IPHDNRT,
HUBKGPRIPATH=HQ_IPHUNRT,
HUBKGSECPATH=HQ_IPHDNRT;
//Add the activity factor table. Designate the activity factor for different services to multiplex
transport resources.
ADD FACTORTABLE: FTI=1, REMARK="IUB", GENCCHDL=70, GENCCHUL=70,
MBMSCCHDL=100, SRBDL=15, SRBUL=15, VOICEDL=70, VOICEUL=70, CSCONVDL=100,
2008-09-14
Huawei Confidential
Page 68 of 133
INTERNAL

CSCONVUL=100, CSSTRMDL=100, CSSTRMUL=100, PSCONVDL=70, PSCONVUL=70,
PSSTRMDL=100, PSSTRMUL=100, PSINTERDL=100, PSINTERUL=100, PSBKGDL=100,
PSBKGUL=100, HDSRBDL=50, HDCONVDL=70, HDSTRMDL=100, HDINTERDL=100,
HDBKGDL=100, HUSRBUL=50, HUCONVUL=70, HUSTRMUL=100, HUINTERUL=100,
HUBKGUL=100;
//Configure the mapping of transport resources of neighbor nodes.
ADD ADJMAP: ANI=1, CNMNGMODE=EXCLUSIVE, CNOPINDEX=0, TMIGLD=1, TMISLV=1,
TMIBRZ=1, FTI=1;
Add user plane data, including port controller, IP PATH, IP route, and transport resource
group.
Route should not be added in the case of L2 networking.

//Add the port controller.
FE bearer: add transport resources of port 0 of FG2 board in slot 18 to manage and control the
SPU subsystem.
ADD PORTCTRLER: SRN=0, SN=18, PT=ETHER, CARRYEN=0, CTRLSN=0, CTRLSSN=0;
//Add the IP PATH: the unit is kbps.
ADD
IPPATH:
ANI=1,
PATHID=1,
PATHT=HQ_RT,
IPADDR="10.10.10.1",
PEERIPADDR="10.10.10.2", PEERMASK="255.255.255.255", TXBW=20000, RXBW=20000,

CARRYFLAG=LGCPORT,
LPNSN=18,
LPN=20,
FPMUX=NO,
DSCP=46,
VLANFlAG=ENABLE, VLANID=20, PATHCHK=ENABLED, ECHOIP="10.10.10.2";

ADD
IPPATH:
ANI=1,
PATHID=2,
PATHT=HQ_NRT,
IPADDR="10.10.10.1",

CARRYFLAG=LGCPORT,
LPNSN=18,
LPN=20,
FPMUX=NO,
DSCP=18,

ADD
IPPATH:
ANI=1,
PATHID=3,
PATHT=HQ_HSDPANRT,
IPADDR="10.10.10.1",

CARRYFLAG=LGCPORT,
LPNSN=18,
LPN=20,
FPMUX=NO,
DSCP=10,

ADD
IPPATH:
ANI=1,
PATHID=4,
PATHT=HQ_HSUPANRT,
IPADDR="10.10.10.1",

CARRYFLAG=LGCPORT,
LPNSN=18,
LPN=20,
FPMUX=NO,
DSCP=10,
Add the O&M channel.
2008-09-14
Huawei Confidential
Page 69 of 133
INTERNAL

Add the NodeB IP address for the operation and maintenance.
ADD NODEBIP: NODEBID=1, NBTRANTP=IPTRANS_IP, NBIPOAMIP="10.10.10.3",
NBIPOAMMASK="255.255.255.0", IPSRN=0, IPSN=18, IPGATEWAYIP="10.10.10.2",
IPLOGPORTFLAG=YES, IPLPN=20;
Add the IP attributes of the NE management system: The EMSIP is the access IP of the M2000.
ADD EMSIP: EMSIP="10.161.215.230", MASK="255.255.255.0", BAMIP="10.161.215.232",
BAMMASK="255.255.255.0";

The port IP of the RNC interface board and the NodeB IP belong to different network
segments. Packets are forwarded to the NodeB through a router.
1. Connect E1 cable or Ethernet cables.
Label of hardware connection: The FG2 board is in slot 18/19 in subrack 0. The FE port is 0.
The board backup separated from the port backup is used.
2. Perform the configuration in the RNC in the MML.
Difference from the L2 networking: When physical layer data is configured, you should add the
device IP address of the board. The device IP address should not be the same as the
configured IP address in the RNC (including local/peer IP address of the PPP link, local/peer IP
address of the MLPPP group, Ethernet port IP address, IPPATH peer address, SCTP link peer
address).
ADD
DEVIP:
SRN=0,
SN=18,
IPADDR="10.10.10.100",
MASK="255.255.255.192";
ADD ETHIP: SRN=0, SN=18, PN=0, IPADDR="10.10.10.2", MASK="255.255.255.192";
Add the configuration of the data link layer.
//Data link layer data should not be configured in the FE/GE port.
//Add the logical port.
ADD
LGCPORT:
SRN=0,
FLOWCTRLSWITCH=ON;
LPNSN=18,
CNOPINDEX=0,
LPN=20,
PNSN=18,
PN=0,
BWADJ=OFF,
CIR=313,
algorithm parameter, neighbor node, and Iub port data (NCP link and CCP link).
2008-09-14
Huawei Confidential
Page 70 of 133
INTERNAL

CCP. The RNC selects the server mode. The local IP is the FE IP of the RNC interface board.
The peer IP is the FE IP of the NodeB interface board. For the port number, see the negotiation
data table.
LOCIPADDR1="10.10.10.100",
PEERPORTNO=9000,
LOGPORTFLAG=YES,
LOGPORTSN=18,
LOGPORTNO=20,
VLANFlAG=DISABLE,
SWITCHBACKFLAG=YES;
LOCIPADDR1="10.10.10.100",
PEERPORTNO=9001,
LOGPORTFLAG=YES, LOGPORTSN=18, LOGPORTNO=20, VLANFlAG= DISABLE,
SWITCHBACKFLAG=YES;

ADD
NODEBALGOPARA:
AF42DSCP=36,
AF41DSCP=34,
AF33DSCP=30,
AF32DSCP=28,
AF31DSCP=26,
AF23DSCP=22,
AF22DSCP=20,
AF21DSCP=18,
AF13DSCP=14,
AF12DSCP=12,
AF11DSCP=10,
BEDSCP=0,
CCHPRIPATH=HQ_IPRT,
CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT,
SRBSECPATH=NULL,
VOICESECPATH=NULL,
CSCONVSECPATH=NULL,
2008-09-14
Huawei Confidential
Page 71 of 133
INTERNAL

HDSRBSECPATH=NULL,
HDCONVSECPATH=NULL,
HDSTRMSECPATH=NULL,
HDBKGSECPATH=NULL,
HUSRBSECPATH=NULL,
HUSTRMSECPATH=NULL,
HUBKGUL=100;
TMIBRZ=1, FTI=1;
group.

SPU subsystem.
ADD
IPPATH:
ANI=1,
PATHID=1,
PATHT=HQ_RT,
IPADDR="10.10.10.100",

CARRYFLAG=LGCPORT,
LPNSN=18,
LPN=20,
FPMUX=NO,
DSCP=46,
VLANFlAG=DISABLE, PATHCHK=ENABLED, ECHOIP="16.16.16.2";

2008-09-14
Huawei Confidential
Page 72 of 133
INTERNAL

ADD
IPPATH:
ANI=1,
PATHID=2,
PATHT=HQ_NRT,
IPADDR="10.10.10.100",

CARRYFLAG=LGCPORT, LPNSN=18,
LPN=20,
FPMUX=NO, DSCP=18,
VLANFlAG=
DISABLE, PATHCHK=ENABLED, ECHOIP="16.16.16.2";

ADD
IPPATH:
ANI=1,
PATHID=3,
PATHT=HQ_HSDPANRT,
IPADDR="10.10.10.100",

CARRYFLAG=LGCPORT,
LPNSN=18, LPN=20,
FPMUX=NO, DSCP=10,
VLANFlAG=

ADD
IPPATH:
ANI=1,
PATHID=4,
PATHT=HQ_HSUPANRT,
IPADDR="10.10.10.100",

CARRYFLAG=LGCPORT, LPNSN=18,
LPN=20,
FPMUX=NO, DSCP=10,
VLANFlAG=

//Add the user plane route.
ADD
IPRT:
SRN=0,
SN=18,
DESTIP="16.16.16.2",
MASK="255.255.255.0",
NEXTHOP="10.10.10.1", PRIORITY=HIGH;;

BAMMASK="255.255.255.0";
5.4.3 Configuration of Hybrid Transport Networking

The port IP of the RNC interface board and the NodeB IP belong to different network
segments. Packets are forwarded to the NodeB through a router. In the case of the FE bearer,
use the FG2a board and port backup, with the switchover separation mode. Support the port
independent switchover. The dual reliabilities (board and transport) are provided. The
FG2a/GOUa board backup and port load sharing mode can be used. Through the route
configuration, the IP load sharing can be implemented between any two active FE/GE ports.
2008-09-14
Huawei Confidential
Page 73 of 133
INTERNAL

1. Connect E1 cables or Ethernet cables.
Label of hardware connection: The PEU board of the RNC is in slot 14/15 in subrack 0. The
FG2 is in slot 18/19 of subrack 0. The PPP LINK is carried over No.0 E1 pair (E1 is numbered
from 0), and the FE port is 0.
Signaling and real-time services are transmitted through the PPP, and BE services are
transmitted through the FE.
Configure the physical layer data. The configuration is not required in the case of E1
bearer.
Difference from the L2 networking: When physical layer data is configured, you should add the
device IP address of the board. The device IP address should not be the same as the
configured IP address in the RNC (including local/peer IP address of the PPP link, local/peer IP
address of the MLPPP group, Ethernet port IP address, IPPATH peer address, SCTP link peer
address).
ADD
DEVIP:
SRN=0,
SN=18,
IPADDR="10.10.10.100",
MASK="255.255.255.192";
//Add the PPP links. DS1=0, that is, No.0 E1 is used.
Run DSP E1T1:SRN=0, SN=14, BT=AEU/PEU; to observe the E1 state.
ADD PPPLNK: SRN=0, SN=14, PPPLNKN=0, DS1=0, TSBITMAP=TS1-1&TS2-1&TS3-1&TS41&TS5-1&TS6-1&TS7-1&TS8-1&TS9-1&TS10-1&TS11-1&TS12-1&TS13-1&TS14-1&TS151&TS16-1&TS17-1&TS18-1&TS19-1&TS20-1&TS21-1&TS22-1&TS23-1&TS24-1&TS251&TS26-1&TS27-1&TS28-1&TS29-1&TS30-1&TS31-1,
IPADDR="13.13.13.1",
MASK="255.255.255.0", PEERIPADDR="13.13.13.2", PPPMUX=Disable, AUTHTYPE=NO_V;
Add the logical port.
ADD
LGCPORT:
SRN=0,
FLOWCTRLSWITCH=ON;
LPNSN=18,
CNOPINDEX=0,
LPN=20,
PNSN=18,
PN=0,
BWADJ=OFF,
CIR=313,
algorithm parameter, transport neighbor node, and Iub port data (NCP link and CCP link).
CCP. The RNC selects the server mode. The local IP is the local IP of the RNC PPP link. The
peer IP is the peer IP of the RNC PPP link. For the port number, see the negotiation data table.
2008-09-14
Huawei Confidential
Page 74 of 133
INTERNAL

LOCIPADDR1="13.13.13.1",
PEERPORTNO=9000,
LOGPORTFLAG=NO, VLANFlAG=DISABLE, SWITCHBACKFLAG=YES;
LOCIPADDR1="13.13.13.1",
PEERPORTNO=9001,
LOGPORTFLAG=NO, VLANFlAG= DISABLE, SWITCHBACKFLAG=YES;

ADD
NODEBALGOPARA:
AF42DSCP=36,
AF41DSCP=34,
AF33DSCP=30,
AF32DSCP=28,
AF31DSCP=26,
AF23DSCP=22,
AF22DSCP=20,
AF21DSCP=18,
AF13DSCP=14,
AF12DSCP=12,
AF11DSCP=10,
BEDSCP=0,
CCHPRIPATH=HQ_IPRT,
CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT,
SRBSECPATH=NULL,
VOICESECPATH=NULL,
CSCONVSECPATH=NULL,
HDSRBSECPATH=NULL,
HDCONVSECPATH=NULL,
HDSTRMSECPATH=NULL,
HDBKGSECPATH=NULL,
HUSRBSECPATH=NULL,
2008-09-14
Huawei Confidential
Page 75 of 133
INTERNAL

HUSTRMSECPATH=NULL,
HUBKGUL=100;
TMIBRZ=1, FTI=1;
group.
Route should not be added in the case of L2 networking.

SPU subsystem.
E1 bearer: add transport resources of port 0 of the PEU board in slot 14 to manage and control
the SPU subsystem.
ADD
PORTCTRLER:
SRN=0,
SN=14,
PT=PPP,
CARRYPPPN=0,
CTRLSN=2, CTRLSSN=0;
ADD
IPPATH:
ANI=1,
PATHID=1,
PATHT=HQ_RT,
IPADDR="13.13.13.1",

CARRYFLAG=NULL, FPMUX=NO, DSCP=46, VLANFlAG=DISABLE, PATHCHK=ENABLED,
ECHOIP="13.13.13.2";
ADD
IPPATH:
ANI=1,
2008-09-14
PATHID=2,
PATHT=HQ_NRT,
Huawei Confidential
IPADDR="10.10.10.100",
Page 76 of 133
INTERNAL

CARRYFLAG=LGCPORT,
LPNSN=18, LPN=20,
FPMUX=NO, DSCP=18,
VLANFlAG=

ADD
IPPATH:
ANI=1,
PATHID=3,
PATHT=HQ_HSDPANRT,
IPADDR="10.10.10.100",

CARRYFLAG=LGCPORT,
LPNSN=18, LPN=20,
FPMUX=NO, DSCP=10, VLANFlAG=

ADD
IPPATH:
ANI=1,
PATHID=4,
PATHT=HQ_HSUPANRT,
IPADDR="10.10.10.100",

CARRYFLAG=LGCPORT,
LPNSN=18, LPN=20,
FPMUX=NO, DSCP=10,
VLANFlAG=

ADD
IPRT:
SRN=0,
SN=18,
DESTIP="16.16.16.2",
MASK="255.255.255.0",
NEXTHOP="10.10.10.1", PRIORITY=HIGH;

BAMMASK="255.255.255.0";
5.4.4 Configuration of Dual Stack Transport Networking

The signaling, R99 RT, and OM services are transmitted on the ATM network, and the R99
NRT, HSDPA, and HSUPA services are transmitted on the IP network.
1. Connecting E1 Cables and Ethernet Cables
The hardware connections are as follows: The AOU of the RNC is placed in slot 14 of subrack
0, and the FG2 is placed in slot 18 and 19 of subrack 0. The FE port number is 0. The backup
mode is board backup independent of port backup.
2008-09-14
Huawei Confidential
Page 77 of 133
INTERNAL

(1) Configure the parameters related to ATM transport
Configure the physical layer and data link layer
//Set E1/T1 link parameters.

SET E1T1: SRN=0, SN=14, BT=AOU, LS=ALL, WORKMODE=E1,
LNKT=E1_CRC4_MULTI_FRAME, SCRAMBLESW=ON;
You can run the command DSP E1T1: SRN=0, SN=14, BT=AOU;; to view the E1 state.
//Add an IMA group and IMA links.
ADD IMAGRP: SRN=0, SN=14, BT=AOU, IMAGRPN=0, MINLNKNUM=1, IMAID=0,
TXFRAMELEN=D128, IMAVER=V1.1, FLOWCTRLSWITCH=ON, DLYGB=10;
ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=1;
ADD IMALNK: SRN=0, SN=14, IMAGRPN=0, IMALNKN=2;
//Add ATM traffic records.
ADD ATMTRF: TRFX=100, ST=CBR, UT=KBIT/S, PCR=104, CDVT=1024, REMARK="for IUB
NCP";
CCP";
ALCAP";
ADD ATMTRF: TRFX=120, ST=RTVBR, UT=KBIT/S, PCR=3808, SCR=1821, MBS=1000,
CDVT=1024, REMARK="for R99 RT";
ADD ATMTRF: TRFX=130, ST=UBR_PLUS, UT=KBIT/S, MCR=64, CDVT=1024,
REMARK="for IPOA OM";
Add the data on the Iub control plane.
Add SAAL links. The SAAL links are numbered from 0 through 2. They are terminated at SPUa
subsystem 0 of slot 0 in subrack 0.
//Add the SAAL link carrying the NCP.
ADD SAALLNK: SRN=0, SN=0, SSN=0, SAALLNKN=0, CARRYT=IMA, CARRYSRN=0,
CARRYSN=14, CARRYIMAGRPN=0, CARRYVPI=1, CARRYVCI=34, TXTRFX=100,
RXTRFX=100, SAALLNKT=UNI;
//Add the SAAL link carrying the CCP.
//Add the SAAL link carrying the ALCAP.
2008-09-14
Huawei Confidential
Page 78 of 133
INTERNAL

//Add a NodeB and its algorithm parameters.
ADD NODEB: NodeBName="RNC8-BBU1", NodeBId=1, SRN=0, SN=2, SSN=0,
TnlBearerType=ATMANDIP_TRANS, IPTRANSAPARTIND=NOT_SUPPORT,
Nsap="H'45000006582414723F0000000000000000000000", NodeBProtclVer=R6,
SharingSupport=NON_SHARED, CnOpIndex=0, RscMngMode=SHARE;
ADD NODEBALGOPARA: NodeBName="RNC8-BBU1", NodeBLdcAlgoSwitch=IUB_LDR1&NODEB_CREDIT_LDR-0&LCG_CREDIT_LDR-1, NodeBHsdpaMaxUserNum=3840,
NodeBHsupaMaxUserNum=3840;
//Add the data on the Iub interface.
ADD NCP: NODEBNAME="RNC8-BBU1", CARRYLNKT=SAAL, SAALLNKN=0;
ADD CCP: NODEBNAME=" RNC8-BBU1", PN=0, CARRYLNKT=SAAL, SAALLNKN=1;
Add the data on the Iub user plane.
//Add a port controller.

ADD PORTCTRLER: SRN=0, SN=14, PT=IMA, CARRYIMAGRPN=0, CTRLSN=2,
CTRLSSN=0;
//Add an adjacent node (NodeB1) on the Iub interface. The adjacent node ID is 0 and the
interface type is Iub.
ADD ADJNODE: ANI=1, NAME="RNC8-BBU1", NODET=IUB, NODEBID=1, TRANST=ATM_IP,
IsROOTNODE=YES, SRN=0, SN=2, SSN=0, SAALLNKN=2, QAAL2VER=CS2;
//Add AAL2 paths to the NodeB.
ADD AAL2PATH: ANI=1, PATHID=1, PT=RT, CARRYT=IMA, CARRYF=0, CARRYSN=14,
CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=40, TXTRFX=120,
RXTRFX=120;
ADD AAL2PATH: ANI=1, PATHID=2, PT=RT, CARRYT=IMA, CARRYF=0, CARRYSN=14,
CARRYIMAGRPN=0, ADDTORSCGRP=NO, CARRYVPI=1, CARRYVCI=41, TXTRFX=120,
RXTRFX=120;
//Add an AAL2 route to the NodeB.
ADD AAL2RT: NSAP="H'45000006582414723F0000000000000000000000", ANI=1, RTX=1,
OWNERSHIP=YES;
Add the data on the Iub management plane.
//Add the IP address of a device board.

ADD DEVIP: SRN=0, SN=14, IPADDR="7.7.7.1", MASK="255.255.255.0";
//Add an IPoA PVC.
ADD IPOAPVC: IPADDR="7.7.7.1", PEERIPADDR="7.7.7.7", CARRYT=IMA,
CARRYIMAGRPN=0, CARRYVPI=1, CARRYVCI=33, TXTRFX=130, RXTRFX=130,
PEERT=IUB;
2008-09-14
Huawei Confidential
Page 79 of 133
INTERNAL

//Add the OM IP address of the NodeB.
ADD NODEBIP: NODEBID=1, NBTRANTP=ATMTRANS_IP, NBATMOAMIP="7.7.7.7",
NBATMOAMMASK="255.255.255.0", ATMSRN=0, ATMSN=14, ATMGATEWAYIP="7.7.7.7";
//Add the IP address of the element management system (EMS). (EMSIP is the IP address of
the M2000.)
BAMMASK="255.255.255.0";
(2) Configure the parameters related to IP transport
Layer 2 networking
//Add the IP address of an Ethernet port.

//Add a logical port.
ADD LGCPORT: SRN=0, LPNSN=18, LPN=20, PNSN=18, PN=0,
RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, BWADJ=OFF, CIR=313,
FLOWCTRLSWITCH=ON;
//Configure the TRM mapping and activity factor table.
Add the mapping between transmission resources and service types. (Through this task, the
services of different QoS requirements are mapped onto different channels, thus improving the
bandwidth efficiency.)
ADD TRMMAP: TMI=1, ITFT=IUB_IUR_IUCS, TRANST=ATM_IP, EFDSCP=46,
AF43DSCP=38, AF42DSCP=36, AF41DSCP=34, AF33DSCP=30, AF32DSCP=28,
AF12DSCP=12, AF11DSCP=10, BEDSCP=0, CCHPRIPATH=HQ_IPRT, CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT, SRBSECPATH=NULL, VOICEPRIPATH=HQ_IPRT,
VOICESECPATH=NULL, CSCONVPRIPATH=HQ_IPRT, CSCONVSECPATH=NULL,
PSHIGHINTERACTPRIPATH=HQ_IPNRT, PSHIGHINTERACTSECPATH=HQ_IPRT,
PSMIDINTERACTPRIPATH=HQ_IPNRT, PSMIDINTERACTSECPATH=HQ_IPRT,
PSLOWINTERACTPRIPATH=HQ_IPNRT, PSLOWINTERACTSECPATH=HQ_IPRT,
HDSRBSECPATH=NULL, HDCONVPRIPATH=HQ_IPRT, HDCONVSECPATH=NULL,
HDSTRMPRIPATH=HQ_IPRT, HDSTRMSECPATH=NULL,
HDMIDINTERACTPRIPATH=HQ_IPHDNRT, HDMIDINTERACTSECPATH=HQ_IPHUNRT,
HDLOWINTERACTSECPATH=HQ_IPHUNRT, HDBKGPRIPATH=HQ_IPHDNRT,
HDBKGSECPATH=NULL, HUSRBPRIPATH=HQ_IPRT, HUSRBSECPATH=NULL,
HUSTRMSECPATH=NULL, HUHIGHINTERACTPRIPATH=HQ_IPHUNRT,
HUMIDINTERACTSECPATH=HQ_IPHDNRT, HULOWINTERACTPRIPATH=HQ_IPHUNRT,
HULOWINTERACTSECPATH=HQ_IPHDNRT, HUBKGPRIPATH=HQ_IPHUNRT,
//Add an activity factor table to specify activity factors for each traffic class. (Through this task,
2008-09-14
Huawei Confidential
Page 80 of 133
INTERNAL

the transmission resources can be multiplexed.)
HUBKGUL=100;
//Add the TRM mapping on the adjacent node.
TMIBRZ=1, FTI=1;
//Add the data on the user plane (including adding a port controller, IP paths, and an IP route).
The SPU subsystem is added on port 0 of the FG2 in slot 18.
//Add IP paths (traffic unit: kbit/s).
ADD IPPATH: ANI=1, PATHID=1, PATHT=HQ_NRT, IPADDR="10.10.10.1",
CARRYFLAG=LGCPORT, LPNSN=18, LPN=20, FPMUX=NO, DSCP=18, VLANFlAG=
ADD IPPATH: ANI=1, PATHID=2, PATHT=HQ_HSUPANRT, IPADDR="10.10.10.1",
ADD IPPATH: ANI=1, PATHID=3, PATHT=HQ_HSDPANRT, IPADDR="10.10.10.1",
//Add a VLAN.
ADD VLANID: SRN=0, SN=18, IPADDR="10.10.10.2", VLANID=100;
Layer 3 networking
//Configure the data at the physical layer.

Different from layer 2 networking, layer 3 networking requires the device IP address of a board
to be added, and the device IP address cannot be the same as any IP address configured on
the RNC include the local and peer IP addresses of the PPP link, the local and peer IP
addresses of the MLPPP group, the IP address of the Ethernet port, the peer IP address of the
IP path, and the peer IP address of the SCTP link.
//Add a logical port.
2008-09-14
Huawei Confidential
Page 81 of 133
INTERNAL

ADD LGCPORT: SRN=0, LPNSN=18, LPN=20, PNSN=18, PN=0,
RSCMNGMODE=EXCLUSIVE, CNOPINDEX=0, BWADJ=OFF, CIR=313,
FLOWCTRLSWITCH=ON;
//Configure the TRM mapping and activity factor table.
Add the mapping between transmission resources and service types. (Through this task, the
services of different QoS requirements are mapped onto different channels, thus improving the
bandwidth efficiency.)
ADD TRMMAP: TMI=1, ITFT=IUB_IUR_IUCS, TRANST=ATM_IP, EFDSCP=46,
AF12DSCP=12, AF11DSCP=10, BEDSCP=0, CCHPRIPATH=HQ_IPRT, CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT, SRBSECPATH=NULL, VOICEPRIPATH=HQ_IPRT,
PSHIGHINTERACTPRIPATH=HQ_IPNRT, PSHIGHINTERACTSECPATH=HQ_IPRT,
PSMIDINTERACTPRIPATH=HQ_IPNRT, PSMIDINTERACTSECPATH=HQ_IPRT,
PSLOWINTERACTPRIPATH=HQ_IPNRT, PSLOWINTERACTSECPATH=HQ_IPRT,
HDSRBSECPATH=NULL, HDCONVPRIPATH=HQ_IPRT, HDCONVSECPATH=NULL,
HDSTRMPRIPATH=HQ_IPRT, HDSTRMSECPATH=NULL,
HDMIDINTERACTPRIPATH=HQ_IPHDNRT, HDMIDINTERACTSECPATH=HQ_IPHUNRT,
HDLOWINTERACTSECPATH=HQ_IPHUNRT, HDBKGPRIPATH=HQ_IPHDNRT,
HDBKGSECPATH=NULL, HUSRBPRIPATH=HQ_IPRT, HUSRBSECPATH=NULL,
HUSTRMSECPATH=NULL, HUHIGHINTERACTPRIPATH=HQ_IPHUNRT,
HUMIDINTERACTSECPATH=HQ_IPHDNRT, HULOWINTERACTPRIPATH=HQ_IPHUNRT,
HULOWINTERACTSECPATH=HQ_IPHDNRT, HUBKGPRIPATH=HQ_IPHUNRT,
//Add an activity factor table to specify activity factors for each traffic class. (Through this task,
the transmission resources can be multiplexed.)
HUBKGUL=100;
//Add the TRM mapping on the adjacent node.
TMIBRZ=1, FTI=1;
//Add the data on the user plane (including adding a port controller, IP paths, and an IP route).
The SPU subsystem is added on FE port 0 of the FG2 in slot 18.
2008-09-14
Huawei Confidential
Page 82 of 133
INTERNAL

//Add IP paths (traffic unit: kbit/s).
ADD IPPATH: ANI=1, PATHID=1, PATHT=HQ_NRT, IPADDR="10.10.10.100",
ADD IPPATH: ANI=1, PATHID=2, PATHT=HQ_HSUPANRT, IPADDR="10.10.10.100",
ADD IPPATH: ANI=1, PATHID=3, PATHT=HQ_HSDPANRT, IPADDR="10.10.10.100",
CARRYFLAG=LGCPORT, LPNSN=18, LPN=20, FPMUX=NO, DSCP=12
, VLANFlAG= DISABLE, PATHCHK=ENABLED, ECHOIP="16.16.16.2";
//Add an IP route on the user plane.
ADD IPRT: SRN=0, SN=18, DESTIP="16.16.16.2", MASK="255.255.255.192",
NEXTHOP="10.10.10.1", PRIORITY=HIGH;
5.5 Configuration Procedures at NodeB Side

//Set the Ethernet port attributes.

SET ETHPORT: SRN=0, SN=6, SBT=BASE_BOARD, PN=0, MTU=1500, SPEED=100M,
DUPLEX=FULL, ARPPROXY=ENABLE, FERAT=100, FERDT=100;
//Add the IP address of the Ethernet port. The IP address of the NodeB FE port is
10.10.10.2/24.
ADD DEVIP: SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH, PN=0, IP="10.10.10.2",
MASK="255.255.255.0";
Configure the VLAN and service priority.
//Set the priority of the signaling and OM.

//Set the mapping group of the VLAN priorities.
2008-09-14
Huawei Confidential
Page 83 of 133
INTERNAL

//Set the VLAN priority of the signaling plane.
SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=SIG, INSTAG=ENABLE, VLANID=10,
VLANPRIO=7;
//Set the VLAN priority of the maintenance plane.
SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OM, INSTAG=ENABLE, VLANID=10,
VLANPRIO=5;
//Set the VLAN priority of other types of data.
SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=10,
VLANPRIO=5;
//Set the VLAN priority of the data plane.
SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=USERDATA, SRVPRIO=62,
//Add the next hop VLAN mapping.
ADD VLANMAP: NEXTHOPIP="10.10.10.1", VLANMODE=VLANGROUP, VLANGROUPNO=0;
Add the control plane data.
//Add at least two SCTP links, one is used for the NCP, and the other is used for the CCP.
ADD SCTPLNK: SCTPNO=1, SRN=0, SN=6, LOCIP="10.10.10.2", LOCPORT=9000,
PEERIP="10.10.10.1", PEERPORT=58080;
PEERIP="10.10.10.1", PEERPORT=58080;
ADD IUBCP: CPPT=NCP, BEAR=IPV4, LN=1;
ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=IPV4, LN=2;
2008-09-14
Huawei Confidential
Page 84 of 133
INTERNAL
Add the user plane data.
//Add the transport resource group.

ADD RSCGRP: SRN=0, SN=6, BEAR=IPV4, SBT=BASE_BOARD, PT=ETH, PN=0,
RSCGRPID=0, TXBW=20000, RXBW=20000;
//Add the IP PATH (At the RNC side, two IP PATHs with the same DSCP are available,
respectively corresponding to HSDPA and HSUPA. At the NodeB side, one IP PATH of the
HSPA should be added).
ADD IPPATH: PATHID=1, SRN=0, SN=6, SBT=BASE_BOARD, PT=ETH,
JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="10.10.10.2", RNCIP="10.10.10.1", TFT=RT,
DSCP=46, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0,
FPMUXSWITCH=DISABLE;
JNRSCGRP=ENABLE, RSCGRPID=0, NODEBIP="10.10.10.2", RNCIP="10.10.10.1",
TFT=NRT, DSCP=18, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0,
TFT=HSPA_NRT, DSCP=10, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0,

ADD OMCH: IP="10.10.10.3", MASK="255.255.255.0", PEERIP="10.161.215.230",
PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0, SN=6, SBT=BASE_BOARD, BRT=YES,
DSTIP="10.161.215.0", DSTMASK="255.255.255.0", RT=NEXTHOP, NEXTHOP="10.10.10.1";

DUPLEX=FULL, ARPPROXY=ENABLE, FERAT=100, FERDT=100;
16.16.16.2/26.
2008-09-14
Huawei Confidential
Page 85 of 133
INTERNAL

MASK="255.255.255.192";
//Configure the DSCP of the signaling plane and maintenance plane.

PEERIP="10.10.10.100", PEERPORT=58080;
PEERIP="10.10.10.100", PEERPORT=58080;

TFT=RT, DSCP=46, RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0,
2008-09-14
Huawei Confidential
Page 86 of 133
INTERNAL

Route should be added in the case of L3 networking.
ADD IPRT: SRN=0, SN=6, SBT=BASE_BOARD, DSTIP="10.10.10.0",

DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="16.16.16.1";

5.5.3 Configuration of Hybrid Transport Networking
Add the physical layer configuration.
//Set E1/T1 work mode.

SET E1T1WORKMODE: SRN=0, SN=7, SBT=BASE_BOARD,
FRAME=E1_CRC4_MULTI_FRAME, LNCODE=HDB3, CLKM=SLAVE;
//Add the PPP link.
ADD PPPLNK: SRN=0, SN=6, SBT=BASE_BOARD, PPPLNKN=0, PN=0, AUTH=NONAUTH,
TSN=TS1&TS2&TS3&TS4&TS5&TS6&TS7&TS8&TS9&TS10&TS11&TS12&TS13&TS14&TS1
5&TS16&TS17&TS18&TS19&TS20&TS21&TS22&TS23&TS24&TS25&TS26&TS27&TS28&TS
29&TS30&TS31, LOCALIP="13.13.13.2", IPMASK="255.255.255.0", PEERIP="13.13.13.1";
DUPLEX=FULL, ARPPROXY=DISABLE, FERAT=100, FERDT=100;
16.16.16.2/26.
MASK="255.255.255.192";
//Configure the DSCP of the signaling plane and maintenance plane.

2008-09-14
Huawei Confidential
Page 87 of 133
INTERNAL

PEERIP="13.13.13.1", PEERPORT=58080;
PEERIP="13.13.13.1", PEERPORT=58080;
//Route should be added in the case of L3 networking.

ADD RSCGRP: SRN=0, SN=6, BEAR=IPV4, SBT=BASE_BOARD, PT=PPP, PN=0,
ADD IPPATH: PATHID=1, SRN=0, SN=6, SBT=BASE_BOARD, PT=PPP,
JNRSCGRP=ENABLE, RSCGRPID=1, NODEBIP="13.13.13.2", RNCIP="13.13.13.1", TFT=RT,
DSCP=46, RXBW=1800, TXBW=1800, TXCBS=900000, TXEBS=0;
2008-09-14
Huawei Confidential
Page 88 of 133
INTERNAL
//Add the NodeB IP address for the operation and maintenance.

ADD
OMCH:
IP="9.9.9.9",
MASK="255.255.255.192",
PEERIP="10.161.215.230",
5.5.4 Configuration of Dual Stack Transport Networking

1. Configure the Parameters Related to ATM Transport
Configuration the physical layer data
//Set the working mode of E1/T1 links.

SET E1T1WORKMODE: SRN=0, SN=7, SBT=BASE_BOARD,
FRAME=E1_CRC4_MULTI_FRAME, LNCODE=HDB3, CLKM=SLAVE;
//Add an IMA group and IMA links.
ADD IMAGRP: SRN=0, SN=7, SBT=BASE_BOARD, IMAGRPN=0, VER=V1.1,
FRMLEN=D128, MINLNK=1;
ADD IMALNK: SRN=0, SN=7, SBT=BASE_BOARD, IMALNKN=0,
IMAGRPSBT=BASE_BOARD, IMAGRPN=1;
ADD IMALNK: SRN=0, SN=7, SBT=BASE_BOARD, IMALNKN=0,
IMAGRPSBT=BASE_BOARD, IMAGRPN=2;
Configuration the control plane data
//Add SAAL links.

//Add the SAAL link carrying the NCP.
ADD SAALLNK: SAALNO=0, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA, PN=0,
JNRSCGRP=DISABLE, VPI=1, VCI=34, ST=CBR, PCR=104;
//Add the SAAL link carrying the CCP.
//Add the SAAL link carrying the ALCAP.
2008-09-14
Huawei Confidential
Page 89 of 133
INTERNAL

//Add the data on the Iub interface.
ADD IUBCP: CPPT=NCP, BEAR=ATM, LN=0, FLAG=MASTER;
ADD IUBCP: CPPT=CCP, CPPN=0, BEAR=ATM, LN=1, FLAG=MASTER;
//Add the data on the user plane
ADD AAL2NODE: NT=LOCAL, LN=2,
ADDR="H'45000006582414723F0000000000000000000000";
ADD AAL2PATH: NT=LOCAL, PATHID=1, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA,
PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=40, ST=RTVBR, PCR=3808, SCR=1821,
MBS=1000, CDVT=10240, RCR=3807, PAT=RT;
ADD AAL2PATH: NT=LOCAL, PATHID=2, SRN=0, SN=7, SBT=BASE_BOARD, PT=IMA,
PN=0, JNRSCGRP=DISABLE, VPI=1, VCI=41, ST=RTVBR, PCR=3808, SCR=1821,
MBS=1000, CDVT=10240, RCR=3807, PAT=RT;
Add an OM channel.
//Add the IP address of the NodeB to serve as an OM channel.

PEERMASK="255.255.255.0", BEAR=ATM, SRN=0, SN=7, JNRSCGRP=DISABLE,
SBT=BASE_BOARD, PT=IMA, PN=0, VPI=1, VCI=33, ST=UBR+;
2. Configure the Parameters Related to IP Transport
1To configure the parameters for the layer 2 networking, do as follows:
Add the configuration at the physical layer
//Set the attributes for an Ethernet port.

DUPLEX=FULL, ARPPROXY=DISABLE, FERAT=100, FERDT=100;
//Add the IP address of an Ethernet port.
MASK="255.255.255.192";
Add the data on the user plane

2008-09-14
Huawei Confidential
Page 90 of 133
INTERNAL

JNRSCGRP=DISABLE, NODEBIP="10.10.10.2", RNCIP="10.10.10.1", TFT=NRT, DSCP=18,
RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;
JNRSCGRP=DISABLE, NODEBIP="10.10.10..2", RNCIP="10.10.10.1", TFT=HSPA_NRT,
Configure a VLAN
ADD VLANMAP: NEXTHOPIP="10.10.10.1", VLANMODE=VLANGROUP, VLANGROUPNO=0;

SET VLANCLASS: VLANGROUPNO=0, TRAFFIC=OTHER, INSTAG=ENABLE, VLANID=100,
VLANPRIO=1;
2To configure the parameters for the layer 3 networking, do as follows:
MASK="255.255.255.192";
Add the data on the user plane.
//Add IP paths.
JNRSCGRP=DISABLE, NODEBIP="16.16.16.2", RNCIP="10.10.10.2", TFT=NRT, DSCP=18,
RXBW=20000, TXBW=20000, TXCBS=10000000, TXEBS=0, FPMUXSWITCH=DISABLE;
JNRSCGRP=DISABLE, NODEBIP="16.16.16.2", RNCIP="10.10.10.2", TFT=HSPA_NRT,
//Add an IP route.
2008-09-14
Huawei Confidential
Page 91 of 133
INTERNAL
Chapter 6 Example of IU/IUR Interface

Configuration
6.1 Version Description
The configurations of IUPS and IUR are based on the RNC210 051.
The configuration of the IUCS is based on the RNC210 052.
6.2 IU/IUR Interface Protocol Stack
Figure 1.23 IP protocol stack of IU-PS interface
2008-09-14
Huawei Confidential
Page 92 of 133
INTERNAL
Figure 1.24 IP protocol stack of IU-CS interface
Figure 1.25 IP protocol stack of IUR interface
2008-09-14
Huawei Confidential
Page 93 of 133
INTERNAL
6.3 Procedures of IU PS Configuration (IP)

6.3.1 IP Addresses Planning
Note: This section describes the IP address planning by using the GOU board in Slot 24 in
Subrack 0 as an example. Figure 6-4 shows specific IP addresses.
FE IP: 172.18.62.129/29
G
O
U
Sig IP: 172.16.123.(153,154)
S
G
S
N
Router
Gateway IP : 172.18.62.134/29
G
G
S
N
User IP:
172.16.31.(14,16, 18)
202.65.243.201
Figure 1.26 IUPS data planning
6.3.2 Configuring Physical Layer Data
Set the Ethernet port attribute
//Set the Ethernet port attributes to ensure the consistency of the FE port attribute between the
RNC and the interconnected device.
SET ETHPORT: SRN=0, SN=24, BRDTYPE=GOU, PN=0, MTU=1500, AUTO=ENABLE,
OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0;
//Add the IP address of the Ethernet port.
ADD ETHIP: SRN=0, SN=24,
MASK="255.255.255.248";
PN=0,
IPTYPE=PRIMARY,
IPADDR="172.18.62.129",
//Add the device IP address of the board. The value is optional. The device IP is used as the
local address of the SCTPLNK and IPPATH.
6.3.3 Adding Control Plane Data of Iu-PS Interface

General configuration procedures:
2008-09-14
Huawei Confidential
Page 94 of 133
INTERNAL

//Run ADD SCTPLNK to add one SCTP signaling link. To add more SCTP links, run the
command for multiple times. Set Work mode to Client/SERVER (the SGSN is Server and the
RNC is Client). Set Application Type to M3UA.
ADD SCTPLNK:SRN=0, SN=2, SSN=2, SCTPLNKN=0, MODE=CLIENT, APP=M3UA,
DSCP=62,
LOCPTNO=8525,
LOCIPADDR1="172.18.62.129",
PEERIPADDR1="172.16.123.153",
PEERPORTNO=8625,
LOGPORTFLAG=NO,
RTOMIN=1000,
RTOMAX=3000,
RTOINIT=1000,
RTOALPHA=12,
RTOBETA=25,
HBINTER=1000,
MAXASSOCRETR=4,
MAXPATHRETR=2,
CHKSUMTX=NO,
CHKSUMRX=NO,
CHKSUMTYPE=CRC32,
MTU=1500,
VLANFLAG=DISABLE,
CROSSIPFLAG=UNAVAILABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10;
DSCP=62,
LOCPTNO=8526,
LOCIPADDR1="172.18.62.129",
PEERIPADDR1="172.16.123.154",
PEERPORTNO=8626,
LOGPORTFLAG=NO,
RTOMIN=1000,
RTOMAX=3000,
RTOINIT=1000,
RTOALPHA=12,
RTOBETA=25,
HBINTER=1000,
MAXASSOCRETR=4,
MAXPATHRETR=2,
CHKSUMTX=NO,
CHKSUMRX=NO,
CHKSUMTYPE=CRC32,
MTU=1500,
VLANFLAG=DISABLE,
CROSSIPFLAG=UNAVAILABLE, SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10;
//Run ADD N7DPC to add one DPC.
ADD N7DPC: DPX=3, DPC=H'000515, SLSMASK=B0000, NEIGHBOR=YES, NAME="ROC
HW SGSN", DPCT=IUPS, STP=OFF, PROT=ITUT, BEARTYPE=M3UA;
//Run ADD M3LE to add one M3UA local entity.
ADD
M3LE:
LENO=0,
NAME="ROC_RNC12";
ENTITYT=M3UA_IPSP,
RTCONTEXT=4294967295,
Note:
PSP-IPSP transfer networking
A
I PSP
0xA75
B
I PSP
0xB85
C
I PSP
0xC95
Figure 1.27 PSP-IPSP transfer networking
2008-09-14
Huawei Confidential
Page 95 of 133
INTERNAL

Three M3 (A, B, and C) entities exist. A corresponds to 0xA75. B corresponds to 0xB85. C
corresponds to 0xC95.
A is connected to C through the transfer in B, or through one direct connection line. To
configure three channels, do as follows:
ASP-SGP direct connection networking
A
ASP
B
SGP
0xB85
0xA75
Figure 1.28 ASP-SGP direct connection networking
In this networking mode, B functions as the proxy. If B is the UMG with the connection of
NEs, their DPCs use the UMG as the proxy. Otherwise, the scenario is applied seldom.
ASP-SGP transfer networking
A
ASP
0xA75
B
SGP
SS7
C
SS7
0xB85
0xC95
Figure 1.29 ASP-SGP transfer networking
//Run ADD M3DE to add one M3UA destination entity.

ADD
M3DE:
DENO=3,
LENO=0,
DPX=3,
RTCONTEXT=4294967295, NAME="ROC HW SGSN";
ENTITYT=M3UA_IPSP,
//Run ADD M3LKS to add the M3UA link set. To implement the M3UA link load sharing,
set Signaling Link Mask to B0111.
ADD
M3LKS:
SIGLKSX=3,
TRAMODE=M3UA_LOADSHARE_MOD,
NAME="to ROC HW SGSN";
2008-09-14
DENO=3,
LNKSLSMASK=B1111,
WKMODE=M3UA_IPSP, PDTMRVALUE=5,
Huawei Confidential
Page 96 of 133
INTERNAL

Note: To implement the signaling route load sharing, it is recommended that Signaling
Route Mask should be set to B1000 by running the command ADD N7DPC. Signaling
Link Mask should be set to B0111 by running the command ADD M3LKS.
//Run ADD M3RT to add the M3UA route.
ADD M3RT: DENO=3, SIGLKSX=3, PRIORITY=0, NAME="to ROC HW SGSN";
//Run ADD M3LNK to add the M3UA link. To add more M3UA links, run the command for
multiple times.
ADD M3LNK:SIGLKSX=3, SIGLNKID=0, SRN=0, SN=2, SSN=2, SCTPLNKN=0,
PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="to ROC HW SGSN_0";
PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="to ROC HW SGSN_1";
//Run ADD ADJNODE to add one transport neighbor node. Set Node type to IUPS,
Transport type to IP.
ADD ADJNODE:ANI=3, NAME="ROC HW SGSN", NODET=IUPS, SGSNFLG=YES,
DPX=3, TRANST=IP;
//Run ADD CNDOMAIN to add the CN domain. Set CN domain ID to PS_DOMAIN.
ADD
CNDOMAIN:
DRXCYCLELENCOEF=6;
CNDOMAINID=PS_DOMAIN,
NMO=MODE2,
//Run ADD CNNODE to add the CN node. Set CN domain ID to PS_DOMAIN. Set IU
trans bearer type to IP_TRANS.
ADD CNNODE: CNOPINDEX=0, CNID=1, CNDOMAINID=PS_DOMAIN, DPX=3,
CNPROTCLVER=R6,
CNLOADSTATUS=NORMAL,
AVAILCAP=65535,
TNLBEARERTYPE=IP_TRANS;
6.3.4 Adding the Mapping Relation of Transport Resources of Neighbor

Nodes
//Run ADD TRMMAP to add one mapping relation record between a transport and a
service. To add more mapping records, run the command for multiple times.
ADD TRMMAP:TMI=6, ITFT=IUPS, EFDSCP=46, AF43DSCP=38, AF42DSCP=38,
BEDSCP=0;
//Run ADD FACTORTABLE to add one activity factor record.
Note: The two items are mandatory. The two items are required by running ADD
ADJNODE.
2008-09-14
Huawei Confidential
Page 97 of 133
INTERNAL

ADD FACTORTABLE:FTI=6, REMARK="FOR RNC12 IUPS USER", GENCCHDL=70,
GENCCHUL=70,
MBMSCCHDL=100,
SRBDL=15,
SRBUL=15,
VOICEDL=70,
VOICEUL=70, CSCONVDL=100, CSCONVUL=100, CSSTRMDL=100, CSSTRMUL=100,
PSCONVDL=70, PSCONVUL=70, PSSTRMDL=100, PSSTRMUL=100, PSINTERDL=100,
PSINTERUL=100, PSBKGDL=100, PSBKGUL=100, HDSRBDL=50, HDCONVDL=70,
HDSTRMDL=100, HDINTERDL=100, HDBKGDL=100, HUSRBUL=50, HUCONVUL=70,
HUSTRMUL=100, HUINTERUL=100, HUBKGUL=100;
//Run ADD ADJMAP to add one activity factor record to configure the corresponding
transport resource mapping table for different levels of subscribers, and configure the
activity factor table.
ADD ADJMAP: ANI=3, CNMNGMODE=SHARE, TMIGLD=6, TMISLV=6, TMIBRZ=6,
FTI=6;
6.3.5 Adding User Plane Data of Iu-PS Interface

//Run ADD PORTCTRLER to add transport resources for the designated port to manage
and control the SPUa subsystem.
ADD PORTCTRLER: SRN=0, SN=24, PT=ETHER, CARRYEN=0, CTRLSN=2,
CTRLSSN=2,
FWDHORSVBW=0,
BWDHORSVBW=0,
FWDCONGBW=0,
BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0;
//Run ADD IPPATH to add one IP PATH. To add more IP PATHs, run the command for
multiple times.
ADD IPPATH:ANI=3, PATHID=0, PATHT=HQ_QOSPATH, IPADDR="172.18.62.129",
PEERIPADDR="202.65.243.201", PEERMASK="255.255.255.255", TXBW=1000000,
RXBW=1000000,
CARRYFLAG=NULL,
FPMUX=NO,
FWDHORSVBW=0,
BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0,
BWDCONGCLRBW=0,
VLANFLAG=DISABLE,
PATHCHK=ENABLED,
ECHOIP="202.65.243.201", PERIOD=5, CHECKCOUNT=5, ICMPPKGLEN=64;
ADD IPPATH: ANI=3, PATHID=3, PATHT=HQ_QOSPATH, IPADDR="172.18.62.129",
PEERIPADDR="172.16.31.14",
PEERMASK="255.255.255.255",
TXBW=5088,
RXBW=5088, CARRYFLAG=NULL, FPMUX=NO, FWDHORSVBW=0, BWDHORSVBW=0,
FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0,
VLANFLAG=DISABLE, PATHCHK=ENABLED, ECHOIP="172.16.31.14", PERIOD=5,
CHECKCOUNT=5, ICMPPKGLEN=64;
PEERIPADDR="172.16.31.16",
PEERMASK="255.255.255.255",
TXBW=5088,
2008-09-14
Huawei Confidential
Page 98 of 133
INTERNAL

PEERIPADDR="172.16.31.18",
PEERMASK="255.255.255.255",
TXBW=5088,
//Run ADD IPRT to add the IP route in the user plane (the user plane route is optional and
is configured when L3 networking is used between the RNC and the CS).
NEXTHOP="172.18.62.134", PRIORITY=HIGH, REMARK="For NSN RNC3";
//Add the signaling plane route.
NEXTHOP="172.18.62.134", PRIORITY=HIGH, REMARK="to ROC HW SGSN CP_0";
NEXTHOP="172.18.62.134", PRIORITY=HIGH, REMARK="to ROC HW SGSN CP_1";
6.4 Procedures of IU CS Configuration (IP)

Note: This section describes the IP address planning by using the GOU board in Slot 14 in
Subrack 0 as an example. Figure 6-4 shows specific IP addresses.
2008-09-14
Huawei Confidential
Page 99 of 133
INTERNAL

User IP
FE IP
M
G
W
: 10 .210 .1 .52
G
O
U
DEV IP
: 10 .210 .1 .37
Router
M
S
C
Gateway IP
: 10 .210 .1 .49 /29
: 10 .210 .1 .4 5 /30 (Sig )
10 .210 .1 .4 1 /30 (User )
Sig IP
: 10 .210 .1 .69
Figure 1.30 IUCS data planning
6.4.2 Configuration of Physical Layer Data

For configurations of other boards such as UOI, POU, and PEU, see the initial
configuration guide.
//Run SET ETHPORT to set the Ethernet port attributes.
SET ETHPORT: SRN=0, SN=14, BRDTYPE=GOU, PN=0, MTU=1500, AUTO=DISABLE,
FC=OFF, OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0;
//Run ADD ETHIP to add the IP address of the Ethernet port.
ADD
ETHIP:
SRN=0,
SN=14,
PN=0,
IPADDR="10.210.1.52", MASK="255.255.255.248";
IPTYPE=SECOND,
IPINDEX=1,
// (Optional) Run ADD DEVIP to add the device IP address of the board.
Note: The device IP is used as the local address of the SCTPLNK and IPPATH.
6.4.3 Adding Control Plane Data of Iu-CS Interface

command for multiple times. Set Work mode to Client/SERVER (the RNC is Client). Set
Application Type to M3UA.
2008-09-14
Huawei Confidential
Page 100 of 133
INTERNAL

DSCP=62,
LOCPTNO=5000,
LOCIPADDR1="10.210.1.45",
PEERIPADDR1="10.210.1.69",
PEERPORTNO=5000,
LOGPORTFLAG=NO,
RTOMIN=1000, RTOMAX=3000, RTOINIT=1000, RTOALPHA=12, RTOBETA=25,
HBINTER=1000,
MAXASSOCRETR=4,
MAXPATHRETR=2,
CHKSUMTX=NO,
CHKSUMRX=NO,
CHKSUMTYPE=CRC32,
MTU=1500,
VLANFLAG=ENABLE,
VLANID=102,
CROSSIPFLAG=UNAVAILABLE,
SWITCHBACKFLAG=YES,
SWITCHBACKHBNUM=10;
DSCP=62,
LOCPTNO=5002,
LOCIPADDR1="10.210.1.45",
PEERIPADDR1="10.210.1.69",
PEERPORTNO=5002,
LOGPORTFLAG=NO,
RTOMIN=1000, RTOMAX=3000, RTOINIT=1000, RTOALPHA=12, RTOBETA=25,
HBINTER=1000,
MAXASSOCRETR=4,
MAXPATHRETR=2,
CHKSUMTX=NO,
CHKSUMRX=NO,
CHKSUMTYPE=CRC32,
MTU=1500,
VLANFLAG=ENABLE,
VLANID=102,
SWITCHBACKFLAG=YES,
SWITCHBACKHBNUM=10;
//Run ADD N7DPC to add one DPC. To add more DPCs, run the command for multiple
times.
ADD N7DPC: DPX=0, DPC=H'000972, SLSMASK=B0000, NEIGHBOR=YES,
NAME="MSC1", DPCT=IUCS_RANAP, STP=OFF, PROT=ITUT, BEARTYPE=M3UA;
NAME="MGW4M01", DPCT=IUCS_ALCAP, STP=OFF, PROT=ITUT, BEARTYPE=M3UA;
//Run ADD M3LE to add one M3UA local entity.
ADD
M3LE:
LENO=0,
NAME="RNC4M01";
ENTITYT=M3UA_IPSP,
RTCONTEXT=4294967295,

ADD
M3DE:
DENO=0,
LENO=0,
DPX=0,
RTCONTEXT=4294967295, NAME="IUCS-MSC1";
ENTITYT=M3UA_IPSP,
//Run ADD M3LKS to add the M3UA link set.

ADD
M3LKS:
SIGLKSX=0,
NAME="IUCS-MSC1";
DENO=0,
LNKSLSMASK=B1111,
2008-09-14
Huawei Confidential
Page 101 of 133
INTERNAL

ADD M3RT: DENO=0, SIGLKSX=0, PRIORITY=0, NAME="IUCS-RANP1";
multiple times.
ADD M3LNK:SIGLKSX=0, SIGLNKID=0, SRN=0, SN=2, SSN=0,
PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="CS1-0";
SCTPLNKN=0,
ADD M3LNK:SIGLKSX=0, SIGLNKID=1, SRN=0, SN=2, SSN=1,

PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="CS1-1";
SCTPLNKN=1,
//Run ADD ADJNODE to add one transport neighbor node. Set Node type to IUCS,
ADD ADJNODE: ANI=1700, NAME="MGW4M01", NODET=IUCS, DPX=1, TRANST=IP;
//Run ADD CNDOMAIN to add the CN domain. Set CN Domain Flag to CS_DOMAIN.
ADD
CNDOMAIN:
CNDOMAINID=CS_DOMAIN,
DRXCYCLELENCOEF=6;
T3212=10,
ATT=ALLOWED,
//Run ADD CNNODE to add the CN node. Set CN domain Flag to CS_DOMAIN. Set IU
trans bearer type to IP_TRANS.
ADD CNNODE: CNOPINDEX=0, CNID=1, CNDOMAINID=CS_DOMAIN, DPX=0,
CNPROTCLVER=R5,
SUPPORTCRTYPE=CR529_SUPPORT,
CNLOADSTATUS=NORMAL,
AVAILCAP=1000,
TNLBEARERTYPE=IP_TRANS,
RTCPSWITCH=OFF;

Nodes
//Run ADD TRMMAP to add one mapping relation record between the transport and
ADD TRMMAP:TMI=1, ITFT=IUB_IUR_IUCS, TRANST=IP, EFDSCP=46, AF43DSCP=38,
AF11DSCP=10,
BEDSCP=0,
CCHPRIPATH=HQ_IPRT,
CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT,
SRBSECPATH=NULL,
CSSTRMPRIPATH=HQ_IPRT,
CSSTRMSECPATH=NULL,
PSCONVPRIPATH=HQ_IPRT, PSCONVSECPATH=NULL, PSSTRMPRIPATH=HQ_IPRT,
PSSTRMSECPATH=NULL,
PSHIGHINTERACTSECPATH=NULL,
PSMIDINTERACTSECPATH=NULL,
PSLOWINTERACTSECPATH=NULL,
PSBKGPRIPATH=HQ_IPNRT,
PSBKGSECPATH=NULL, HDSRBPRIPATH=HQ_IPHDRT, HDSRBSECPATH=NULL,
2008-09-14
Huawei Confidential
Page 102 of 133
INTERNAL

HDCONVPRIPATH=HQ_IPHDRT,
HDCONVSECPATH=NULL,
HDSTRMPRIPATH=HQ_IPHDNRT,
HDSTRMSECPATH=NULL,
HDHIGHINTERACTPRIPATH=HQ_IPHDNRT,
HDHIGHINTERACTSECPATH=NULL,
HDMIDINTERACTSECPATH=NULL,
HDLOWINTERACTPRIPATH=HQ_IPHDNRT,
HDLOWINTERACTSECPATH=NULL,
HDBKGSECPATH=NULL,
HUSRBPRIPATH=HQ_IPHURT,
HUSRBSECPATH=NULL,
HUCONVPRIPATH=HQ_IPHURT,
HUCONVSECPATH=NULL,
HUSTRMPRIPATH=HQ_IPHURT,
HUSTRMSECPATH=NULL,
HUHIGHINTERACTSECPATH=NULL,
HUMIDINTERACTPRIPATH=HQ_IPHUNRT,
HUMIDINTERACTSECPATH=NULL,
HULOWINTERACTSECPATH=NULL,
HUBKGPRIPATH=HQ_IPHUNRT, HUBKGSECPATH=NULL;
Note: The two items are mandatory. The two items are required by running the command
ADD ADJMAP.
ADD FACTORTABLE:FTI=1, REMARK="IUCS", GENCCHDL=70, GENCCHUL=70,
MBMSCCHDL=100,
SRBDL=15,
SRBUL=15,
VOICEDL=70,
VOICEUL=70,
CSCONVDL=100,
CSCONVUL=100,
CSSTRMDL=100,
CSSTRMUL=100,
FTI=1;
6.4.5 Adding User Plane Data of Iu-CS Interface

CTRLSSN=0,
FWDHORSVBW=0,
BWDHORSVBW=0,
FWDCONGBW=0,
multiple times.
ADD
IPPATH:
2008-09-14
ANI=1700,
PATHID=0,
PATHT=RT,
Huawei Confidential
IPADDR="10.210.1.41",
Page 103 of 133
INTERNAL

PEERIPADDR="10.210.1.37",
PEERMASK="255.255.255.248",
TXBW=1000000,
RXBW=1000000, DSCP=46, FWDHORSVBW=0, BWDHORSVBW=0, FWDCONGBW=0,
BWDCONGBW=0, FWDCONGCLRBW=0, BWDCONGCLRBW=0, VLANFLAG=ENABLE,
VLANID=101,
PATHCHK=ENABLED,
ECHOIP="10.210.1.37",
PERIOD=5,
//Run ADD IPRT to add the IP route (it is configured when L3 networking is used between
the RNC and the CS).
NEXTHOP="10.210.1.49", PRIORITY=HIGH, REMARK="MGW4M01";
//Add the signaling plane route.
NEXTHOP="10.210.1.73", PRIORITY=HIGH, REMARK="MSC1";
6.5 Procedures of IUR Configuration (IP)

Note: This section describes the IP address planning by taking the GOU board in Slot16
of Subrack 0 as an example.
FE IP: 172.18.30.65/29
FE IP: 172.18.62.65/29
G
O
U
Other
RNC
Router
G
O
U
Gateway IP: 172.18.62.70/29
Figure 1.31 IUR data planning
6.5.2 Configuration of Physical Layer Data

For configurations of other boards such as UOI, POU, and PEU, see the initial
configuration guide.
2008-09-14
Huawei Confidential
Page 104 of 133
INTERNAL

//Run SET ETHPORT to set the Ethernet port attributes.
SET ETHPORT: SRN=0, SN=16, BRDTYPE=GOU, PN=0, MTU=1500, AUTO=ENABLE,
OAMFLOWBW=0, FLOWCTRLSWITCH=ON, FCINDEX=0;
//Run ADD ETHIP to add the IP address of the Ethernet port.
ADD ETHIP: SRN=0, SN=16, PN=0, IPTYPE=PRIMARY, IPADDR="172.18.62.65",
MASK="255.255.255.248";
// (Optional) Run ADD DEVIP to add the device IP address of the board.
Note: The device IP is used as the local address of the SCTPLNK and IPPATH.
6.5.3 Adding Control Plane Data of Iur Interface

(OPC --> N7DPC)--> M3LE --> M3DE --> M3LKS --> M3RT --> M3LNK
command for multiple times. Set Work mode to Client/SERVER (the RNC is Client). Set
Application Type to M3UA.
ADD SCTPLNK:SRN=0, SN=2, SSN=3, SCTPLNKN=0, MODE=SERVER, APP=M3UA,
DSCP=62,
LOCIPADDR1="172.18.62.65",
PEERIPADDR1="172.18.30.65",
PEERPORTNO=9000,
LOGPORTFLAG=NO,
RTOMIN=1000,
RTOMAX=3000,
RTOINIT=1000, RTOALPHA=12, RTOBETA=25, HBINTER=1000, MAXASSOCRETR=4,
MAXPATHRETR=2, CHKSUMTX=NO, CHKSUMRX=NO, CHKSUMTYPE=CRC32,
MTU=1500,
VLANFLAG=DISABLE,
SWITCHBACKFLAG=YES, SWITCHBACKHBNUM=10;
//Run ADD N7DPC to add one DPC. For the type, select the IUR interface.
NAME="HW RNC11", DPCT=IUR, STP=OFF, PROT=ITUT, BEARTYPE=M3UA;
//Run ADD NRNC to add the neighbor RNC information.
ADD NRNC: NRNCID=11, SHOTRIG=CS_SHO_SWTICH-1&HSPA_SHO_SWITCH1&NON_HSPA_SHO_SWTICH-1,
HHOTRIG=OFF,
SERVICEIND=SUPPORT_CS_AND_PS,
IUREXISTIND=TRUE,
DPX=11,
RNCPROTCLVER=R6,
STATEINDTMR=20,
SUPPIURCCH=NO,
HHORELOCPROCSWITCH=DL_DCCH_SWITCH-0&IUR_TRG_SWITCH-0,
TNLBEARERTYPE=IP_TRANS,
DSCRIND=FALSE,
IURHSDPASUPPIND=OFF,
IURHSUPASUPPIND=OFF;
2008-09-14
Huawei Confidential
Page 105 of 133
INTERNAL

ADD
M3DE:
DENO=11,
LENO=0,
RTCONTEXT=4294967295, NAME="RNC11 DE";
DPX=11,
ENTITYT=M3UA_IPSP,
//Run ADD M3LKS to add the M3UA link set. To implement the M3UA link load sharing,
set Signaling Link Mask to B0111.
ADD
M3LKS:
SIGLKSX=11,
NAME="RNC12 To RNC 11";
DENO=11,
LNKSLSMASK=B1111,
ADD M3RT: DENO=11, SIGLKSX=11, PRIORITY=0, NAME="M3RT BETWEEN RNC12
AND RNC 11";
multiple times.
PRIORITY=0, LNKREDFLAG=M3UA_MASTER_MOD, NAME="Route from RNC12 To
RNC11";

Nodes
//Run ADD ADJNODE to add one transport neighbor node. Set Node type to IUCS,
ADD ADJNODE: ANI=11, NAME="to ROC_RNC11", NODET=IUR, DPX=11, TRANST=IP;
Adding the Mapping Relation of Transport Resources of Neighbor Nodes
//Run ADD TRMMAP to add one mapping relation record between a transport and a
ADD TRMMAP:TMI=1, ITFT=IUB_IUR_IUCS, TRANST=IP, EFDSCP=46, AF43DSCP=38,
AF11DSCP=10,
BEDSCP=0,
CCHPRIPATH=HQ_IPRT,
CCHSECPATH=NULL,
SRBPRIPATH=HQ_IPRT,
SRBSECPATH=NULL,
CSSTRMPRIPATH=HQ_IPRT,
CSSTRMSECPATH=NULL,
PSCONVPRIPATH=HQ_IPRT, PSCONVSECPATH=NULL, PSSTRMPRIPATH=HQ_IPRT,
PSSTRMSECPATH=NULL,
2008-09-14
Huawei Confidential
Page 106 of 133
INTERNAL

PSHIGHINTERACTSECPATH=NULL,
PSMIDINTERACTSECPATH=NULL,
PSLOWINTERACTSECPATH=NULL,
PSBKGPRIPATH=HQ_IPNRT,
PSBKGSECPATH=NULL, HDSRBPRIPATH=HQ_IPHDRT, HDSRBSECPATH=NULL,
HDCONVPRIPATH=HQ_IPHDRT,
HDCONVSECPATH=NULL,
HDSTRMPRIPATH=HQ_IPHDNRT,
HDSTRMSECPATH=NULL,
HDHIGHINTERACTPRIPATH=HQ_IPHDNRT,
HDHIGHINTERACTSECPATH=NULL,
HDMIDINTERACTSECPATH=NULL,
HDLOWINTERACTPRIPATH=HQ_IPHDNRT,
HDLOWINTERACTSECPATH=NULL,
HDBKGSECPATH=NULL,
HUSRBPRIPATH=HQ_IPHURT,
HUSRBSECPATH=NULL,
HUCONVPRIPATH=HQ_IPHURT,
HUCONVSECPATH=NULL,
HUSTRMPRIPATH=HQ_IPHURT,
HUSTRMSECPATH=NULL,
HUHIGHINTERACTSECPATH=NULL,
HUMIDINTERACTPRIPATH=HQ_IPHUNRT,
HUMIDINTERACTSECPATH=NULL,
HULOWINTERACTSECPATH=NULL,
HUBKGPRIPATH=HQ_IPHUNRT, HUBKGSECPATH=NULL;
Note: 4 and 5 are mandatory. The two items are required by running the command ADD
ADJMAP.
ADD FACTORTABLE:FTI=1, REMARK="IUCS", GENCCHDL=70, GENCCHUL=70,
MBMSCCHDL=100,
SRBDL=15,
SRBUL=15,
VOICEDL=70,
VOICEUL=70,
CSCONVDL=100,
CSCONVUL=100,
CSSTRMDL=100,
CSSTRMUL=100,
FTI=1;
6.5.5 Adding User Plane Data of Iur Interface

CTRLSSN=0,
FWDHORSVBW=0,
BWDHORSVBW=0,
FWDCONGBW=0,
2008-09-14
Huawei Confidential
Page 107 of 133
INTERNAL

multiple times.
ADD IPPATH:ANI=11, PATHID=0, PATHT=HQ_QOSPATH, IPADDR="172.18.62.65",
PEERIPADDR="172.18.30.65",
PEERMASK="255.255.255.255",
TXBW=1000000,
RXBW=1000000,
CARRYFLAG=NULL,
FPMUX=NO,
FWDHORSVBW=0,
BWDHORSVBW=0, FWDCONGBW=0, BWDCONGBW=0, FWDCONGCLRBW=0,
BWDCONGCLRBW=0,
VLANFLAG=DISABLE,
PATHCHK=ENABLED,
ECHOIP="172.18.30.65", PERIOD=5, CHECKCOUNT=5, ICMPPKGLEN=64;
//Run ADD IPRT to add the IP route (it is optional and configured when L3 networking is
used between the RNC and the CS).
//Route of user plane and signaling plane (Peer signaling and user plane address are
normalized)
NEXTHOP="172.18.62.70", PRIORITY=HIGH, REMARK="IUR IPRT BETWEEN RNC12
AND RNC11";
6.6 IU/IUR Configuration Specifications

6.6.1 Configuration Specifications of Control Plane (IUPS-IP)
1. Difference of the configuration specifications between the M3UA and IuCS: The RNC is the Client of the IPSP. The SGSN is the Server of the
IPSP. Other rules are the same as those of the Iu-CS.
2. The SCCP timer configuration specification is the same as that of the IuCS.
6.6.2 Configuration Specifications of User Plane (IUPS-IP)

1. Each ETH PORT using the Iu-PS interface is configured with one IP
PATH. The type is QoS PATH.
2. If the peer device supports the function, enable the PING detection
function of the IP PATH.
3. Configure the bandwidth for the IP PATH. If the middle transport
bandwidth is smaller than the port bandwidth, the IP PATH bandwidth is
set to the transport bandwidth. If the transport bandwidth is not limited,
the IP PATH bandwidth is configured to the port bandwidth.
4. The port controller should distribute ports used in each subrack to all
2008-09-14
Huawei Confidential
Page 108 of 133
INTERNAL

SPU subsystems on average.
6.6.3 Configuration Specifications of Control Plane (IUCS-IP)

1. It is recommended that the context of the M3UA local entity route should
be set to 4294967295 (all F).
Note: If the peer system requires that the RNC must carry the route
context in ASP ACTIVE message, negotiate with the peer system about
the M3LE route context of the RNC.
2. The context of the destination entity route should be set to 4294967295
(all F).
Note: If the peer system requires the negotiation, set the destination
entity route context according to the route context provided by the peer
system.
3. The service mode of the M3UA linkset requires the negotiation with the
peer system. The load-sharing mode is recommended (the
active/standby flag of initialized bearer service of the M3UA link is the
master mode). If the M3LE/M3DE is configured according to Table 2, the
work mode of the linkset is configured to IPSP. The precedence of all
links in the linkset must be the same.
4. RNC V29 binds the Client/Server of the M3UA with the Client/Server of
the SCTP. If the SCTP link used by the M3UA is the Server, the M3UA is
also the Server. If the SCTP link is Client, the M3UA is also the Client.
Configuration personnel should pay attention to this in the case of the
negotiation of the work mode of the SCTP/M3UA with the peer system
(in the IPSP-IPSP networking, the M3UA link in the Client mode
originates the link establishment of the M3UA link).
5. For the reliability, if the peer system supports the SCTP dual-home, all
SCTP links corresponding to the M3UA should be set to dual home
(each end uses two IPs).
6.6.4 Configuration Specifications of User Plane (IUCS-IP)

1. Each ETH PORT using the Iu-CS interface is configured with one IP
PATH. The type is QoS PATH.
2008-09-14
Huawei Confidential
Page 109 of 133
INTERNAL

6.6.5 Configuration Specifications of Control Plane (IUR-IP)

1. The M3UA configuration specifications are the same as the Iu-PS.
2. The SCCP timer configuration specification is the same as that of the IuCS.
6.6.6 Configuration Specifications of User Plane (IUR-IP)

1. Each ETH PORT using the Iur interface is configured with one IP PATH.
The type is QoS PATH.
Note: For version earlier than V29C01B063, configure the IP PATH for
each NRNC user plane IP. That is, the network segment configuration of
the user plane IP is not supported.
6.7 Relevant Knowledge Points

6.7.1 Two Modes
Work Mode
The concept is used in the M3UA linkset. The work mode must be negotiated
with the peer system, that is, specify who originates the link establishment. At
present, the link establishment is originated in the IPSP client and ASP mode. At
present, the work mode is applicable to only the linkset mode.
Traffic Mode
2008-09-14
Huawei Confidential
Page 110 of 133
INTERNAL

The traffic mode requires the negotiation with the peer system, for example,
AS. The information is carried in the ASP Active message. At the end where the
ASP Active message is received, the system compares Traffic Mode with Traffic
Mode configured at the peer system. If both are inconsistent, the system discards
this message and returns one ERROR (AS traffic mode is not matched). The
highest state of the AS can be only INACTIVE. The traffic mode cannot serve the
SCCP.
6.7.2 Relation between Signaling Link and Mask

The signaling link mask of the M3UA linkset should meet the following two
conditions:
1) The number (n) of 1 in the mask determines the maximum number of links (2^n)
for the load sharing. The number of configured M3UA links must be smaller than or
equal to 2^n.
2) The AND operation between this value and Signaling Route Mask configured in
the N7DPC must be 0.
Number
of
Subracks
Number
of
M3UA Links
Signaling
Mask
B0001
B0011
B0011
B0111
B0111
B0111
Link
Remark
The
SPU
subsystem
terminated in the M3UA
should be distributed in
subracks and SPMs on
average.
The
bearer
should be distributed on all
ports of the Iu-CS on
average.
6.8 Configuration Example of Current Network

For the IUCS example in Paraguay, see the following attachment:
C: \ Document s and
Set t i ngs\ user\ \ I PRAN\ CFGMML- 20080712050252V21052. t xt
For the IUPS/IUR example of Singapore M1, see the following attachment:
2008-09-14
Huawei Confidential
Page 111 of 133
INTERNAL
C: \ Document s and
Set t i ngs\ user\ \ I PRAN\ CFGMML- 20080611134355. t xt
2008-09-14
Huawei Confidential
Page 112 of 133
INTERNAL
Chapter 7 Remote O&M Channel

7.1 Maintaining the NodeB through the O&M Channel of the
RNC
7.1.1 Principles and Basic Configuration Procedures
Figure 7-1 shows the maintenance of the NodeB through the O&M channel of the
RNC.
Figure 1.32 Maintaining NodeB by the M2000 Through the RNC
Principles of maintaining NodeB through RNC

O&M packets are routed to the RNC from the M2000 directly. Data packets are
forwarded through the OMU and interface board in the RNC. After the arrival at the interface
board, packets are forwarded to the NodeB through the PPP/MLPPP/FE/GE.
ADD EMSIP: Configure the EMS IP address.
ADD NODEBIP: Configure the NodeB O&M IP.
If the transport type of the NodeB is IUB-ATM, Next hop IP address must be the peer
IP address of the IPOA PVC. If the transport type of the NodeB is IUB-IP, Next hop IP
2008-09-14
Huawei Confidential
Page 113 of 133
INTERNAL

address must be one of the following configured addresses:
PPP link peer IP address
MLPPP group peer IP address
IP address with the same network segment of the FE/GE port
ADD NODEBESN: If the DHCP function is used between the RNC and the NodeB, add
the NodeB electronic serial number to respond to DHCP requests reported by the
NodeB (Optional).
7.1.2 Configuration Example

1. The OM address of the NodeB and the NodeB interface address are on the same network
segment
Note: The OM address and interface address of the NodeB are on the same
network segment. At the NodeB side, you should run SET ETHPORT to enable the
ARP proxy function of the port.
Name
Address
M2000 address
10.161.215.230
OMU external network address
10.161.215.211
OMU internal network address
80.168.6.40
FG2a internal address
80.168.6.64
FG2a interface address
12.12.8.1
NodeB interface address
12.12.8.2
NodeB OM address
12.12.8.11
ADD EMSIP: Configure the EMS IP address.
Command:
ADD EMSIP: EMSIP="10.161.215.230", MASK="255.255.0.0";
After the running of this command, the network segment route to the M2000 is
added to the FG2a interface board. The value of the network segment route is the
result with the AND operation between the address by running the command ADD
EMSIP and the mask. The results are as follows:
%%DSP IPRT: SRN=0, SN=18;%%
Destination address Address mask
Next hop address
10.161.0.0
80.168.6.40
2008-09-14
255.255.0.0
Huawei Confidential
Page 114 of 133
INTERNAL
ADD NODEBIP: Configure the NodeB O&M IP.
Command:
ADD
NODEBIP:
NODEBID=1,
NBTRANTP=IPTRANS_IP,
NBIPOAMIP="12.12.8.11", NBIPOAMMASK="255.255.0.0", IPSRN=0, IPSN=18,
IPGATEWAYIP="12.12.8.2", IPLOGPORTFLAG=NO;
After the running of this command, the RNC automatically adds the route to the
NodeB in the OMU. One host route is added. The results are as follows:
%%LST BAMIPRT:;%%
Destination network address Destination address mask Forward route address
12.12.8.11
255.255.255.255
80.168.6.64
ADD NODEBESN: Add the electronic serial number of the NodeB to respond to DHCP
requests reported by the NodeB (optional).
2. The OM address of the NodeB and the NodeB interface address are not on the same
network segment.
Assume that the OM address of the NodeB is changed to 10.10.10.10/24
1) The service is available; therefore, the service from the FG2a to NodeB interface
address is normal. The OM address of the NodeB and the interface address are not
on the same network segment; therefore, the route to the NodeB is automatically
added in the FG2a by running the command ADD NODEBIP.
ADD
NODEBIP:
NODEBID=1,
NBTRANTP=IPTRANS_IP,
NBIPOAMIP="10.10.10.10", NBIPOAMMASK="255.255.0.0", IPSRN=0, IPSN=18,
IPGATEWAYIP="12.12.8.2", IPLOGPORTFLAG=NO;
The results (the network segment route added to the NodeB on the FG2a) are as
follows:
%%DSP IPRT: SRN=0, SN=18;%%
Destination address Address mask
10.10.10.0
255.255.255.0
Next hop address
12.12.8.2
2) The M2000 can normally maintain the OMU; therefore, the path from the M2000
to the OMU is normal.
Note: In the EMS system, the route to the NodeB must be added. In the NodeB, the
route to the M2000 must be added.
Through the preceding configuration, the NodeB O&M channel in the RNC is
normal. You need not to configure any route in the RNC manually.
2008-09-14
Huawei Confidential
Page 115 of 133
INTERNAL
7.2 Maintaining the NodeB directly by the M2000

7.2.1 Principles and Basic Configuration Procedures
Figure 1.33 Maintaining the NodeB directly by the M2000
The OM channel from the M2000 to the NodeB does not pass the RNC. The
configurations are as follows:
Add the NodeB IP in the RNC: Add the NodeB IP for the M2000 to
provide the automatic search function (for the automatic search function of the
M2000, see the V8 IPRAN Deployment Guide).
Synchronize the M2000 to the RNC: Read the OMIP to the NodeB
from the BAM database and establish the OM channel with the NodeB.
If the OMIP of the NodeB and FE port are on the same network
segment. In the NodeB LMT, run SET ETHPORT to enable the ARP proxy function
of the port. Otherwise, one route to the NodeB OMIP must be added to Router2.
The next hop is the FE port address.
7.3 Comparison between the Maintenance through the RNC

and Maintenance by the M2000 directly
Maintenance through the RNC
Benefits
2008-09-14
It does not depend on the

transport network.
Huawei Confidential
Maintenance
directly
by
the
M2000
OM packets of the NodeB do

not cause extra burden for
the RNC.
The architecture is clear. A

fault can be located quickly.
Page 116 of 133
INTERNAL

Limitations
The load of the RNC increases.
The RNC cannot be isolated in

the location of a fault related to
the NodeB OM.
In special cases, a router is

required (for example, label
the VLAN).
Recommendation: In the IP networking, the direct maintenance of the NodeB by

the M2000 is recommended. The maintenance through the RNC is not
recommended. Thus, the occupation of the IUB transport resources decreases.
The load traffic between the RNC board decreases.
In special cases, the maintenance of the NodeB through the RNC is used. For
example, the IUB interface has the VLAN and a route device is unavailable for
labeling the VLAN.
7.4 Active/Standby OMCH Configurations at the NodeB Side

7.4.1 Basic Principles
The V210 is applicable to the dual stack. The IP scenario supports the
active/standby OMCH channel. The ATM scenario does not support the
active/standby configuration.
In the IP scenario, two remote maintenance channels can be configured. Two
channels reach the peer ends through different routes. After the NodeB starts, the
active channel is selected fixedly as the activation channel. If the active channel is
not available, the standby channel does not function as the activation channel
automatically. At this time, the results are null by running the command DSP
OMCH. In the initial configuration, one active OMCH channel must be configured.
Note:
1. The remote maintenance channel IP, local maintenance channel IP, and
IP of each interface (except the FE interface) should not be on the same
network segment. The local IP of two remote maintenance channels
should not be on the same network segment.
2. If the peer IP and local IP of the maintenance channel are not on the
same network segment, you should run ADD OMCH to bind the route.
Only the binding route of the activation channel is valid. The binding
route of deactivation channel is not valid. Hence, the binding route is
used for this maintenance channel. Otherwise, the corresponding binding
route is invalid when the maintenance channel is switched over to the
deactivation channel. As a result, channels using the route are
interrupted. To ensure that the binding route of the maintenance channel
2008-09-14
Huawei Confidential
Page 117 of 133
INTERNAL

is used for this maintenance channel only, the destination network
segment of the binding route should be different from any route
destination network segment added by running the command ADD IPRT.
To query the configured route, run LST IPRT.
3. If the local IP of the OMCH and the FE address are on the same network
segment, run SET ETHPORT to enable the ARP proxy.
7.4.2 Configuration Example

1. Hybrid transport scenario
In the case of the hybrid transport, two OMCHs are configured: one is over the
ETH, and the other is over the PPP.
ADD OMCH: FLAG=MASTER, IP="12.12.8.11", MASK="255.255.255.0",
PEERIP="10.161.215.230", PEERMASK="255.255.255.0", BEAR=IPV4, SRN=0,
SN=6,
SBT=BASE_BOARD,
BRT=YES,
DSTIP="10.161.215.0",
DSTMASK="255.255.255.0", RT=NEXTHOP, NEXTHOP="12.12.8.1", PREF=60;
ADD OMCH: FLAG=SLAVE, IP="14.14.14.14", MASK="255.255.255.0",
SN=5,
SBT=E1_COVERBOARD,
BRT=YES,
DSTIP="10.161.215.0",
DSTMASK="255.255.255.0", RT=IF, IFT=PPP, IFNO=0, PREF=60;
2. Dual-stack scenario
In the case of the dual-stack, two OMCHs are configured: one OMCH is over IP
and the configurations are the same as the previous IP scenario; the other OMCH
is over ATM.
SN=6,
SBT=BASE_BOARD,
BRT=YES,
DSTIP="10.161.215.0",
DSTMASK="255.255.255.0", RT=NEXTHOP, NEXTHOP="12.12.8.1", PREF=60;
ADD OMCH: FLAG=SLAVE, IP="14.14.14.14", MASK="255.255.255.0",
PEERIP="10.161.215.230", PEERMASK="255.255.255.0", BEAR=ATM, SRN=0,
SN=6, JNRSCGRP=DISABLE, SBT=BASE_BOARD, PT=IMA, PN=0, VPI=1,
VCI=33, ST=UBR+, MCR=32, PCR=144;
3. ATM scenario
In the ATM scenario, the active/standby configuration is not supported. Only one
remote maintenance channel is configured.
2008-09-14
Huawei Confidential
Page 118 of 133
INTERNAL

PEERIP="10.161.215.230", PEERMASK="255.255.255.0", BEAR=ATM, SRN=0,
SN=6, JNRSCGRP=DISABLE, SBT=BASE_BOARD, PT=IMA, PN=0, VPI=1,
VCI=33, ST=UBR+, MCR=32, PCR=144;
2008-09-14
Huawei Confidential
Page 119 of 133
INTERNAL
Chapter 8 Remote
Debug
of
NodeB
8.1 NodeB Remote Software Debug
Usually, the NodeB software debug is subcontracted to a local cooperation partner.
The software debug is implemented at the local NodeB. The fee of the NodeB
software debug ranges from 1500 RMB to 7000 RMB.
To save this engineering cost, the remote debug for a NodeB is implemented in the
equipment room in the centralized mode. This mode can replace the debug at the
local NodeB. Benefits:
1. After the hardware of NodeB is installed, engineers need not enter
the site again.
2. The cost of the software debug is saved.
3. The construction speed of a NodeB is quicker.
After the transport of the Iub interface in the IPRAN is ready, two modes are
available for activating the NodeB remote maintenance channel:
Correct data configuration files are downloaded to the NodeB to

ensure the successful interconnection between the RNC and the
NodeB OM channel.
The DHCP is used to activate the NodeB remote OM channel when

correct data configuration files cannot be downloaded to the NodeB.
This section describes the remote debug of a NodeB related to Iub interface in the
IPRAN networking. Maintenance personnel use the M2000 or LMT debug a NodeB
in the remote OMC equipment room through the NodeB remote maintenance
channel.
2008-09-14
Huawei Confidential
Page 120 of 133
INTERNAL
8.2 Introduction to the DHCP

8.2.1 Basic Principles
The dynamic host configuration protocol (DHCP) transfers configuration
information (including allocated IP address, subnet mask, and default gateway) for
a host in the network. The DHCP is encapsulated through the UDP. Based on the
BOOTP protocol, the function of dynamically obtaining the IP address is added. In
packets, options are added.
Concepts:
DHCP Client: It is the host in the network using the DHCP obtain configuration
parameters, for example, NodeB.
DHCP Server: It is the host in the network returning configuration parameters to the
DHCP Client, for example, RNC
DHCP Relay: It is the device transferring DHCP packets between the DHCP Server
and the DHCP Client. The DHCP Relay can be a router or specific host.
8.2.2 Scenario without Using the DHCP Relay

When the L2 network exists between the NodeB (DHCP Client) and DHCP Server,
devices between them need not support the DHCP Relay.
The DHCP Server is the address of the RNC interface board. The L2 network
exists between the NodeB and RNC interface board. Figure 8-1 shows the DHCP
procedure.
DISCOVER (Broadcast)
RNC interfaceboard
Server
Activeboard electronic
serial number
NodeB FE IP and mask
NodeB OMIP and mask
NodeB peer OMIP and mask
REQUEST (Broadcast)
Figure 1.34 Initial address application in the scenario without using DHCP Relay
2008-09-14
Huawei Confidential
Page 121 of 133
INTERNAL
8.2.3 Scenario with Using the DHCP Relay

When the L3 network exists between the NodeB (DHCP Client) and DHCP Server,
the gateway router of the NodeB must support the DHCP Relay.
dhcp client 0
network 1
dhcp relay
network 0
network 2
dhcp server
network n
NETWORK n-1
dhcp client n
Figure 1.35 Server-Client networking with using the Relay
The DHCP Server is the address of the RNC interface board. The L3 network
exists between the NodeB and RNC interface board. The gateway router of the
NodeB starts the DHCP Relay. Figure 8-3 shows the DHCP procedure.
Broadcast
Unicast
Unicast
Broadcast
Unicast
Unicast
Figure 1.36 Initial address application in the scenario using the DHCP Relay
2008-09-14
Huawei Confidential
Page 122 of 133
INTERNAL
8.3 General Process of NodeB Remote Software Debug

NodeB RemoteSoftwareDebugFlowchart
Performthe
integrated selftest for
hardware
Is the NodeB
pinged
successfully?
Cut over the

transport and
antennafeeder
Download data
configuration files
Ping the NodeB to
be debugged
remotely
Upgrade
BOOTROM
Upgrade Flash
software
OMSTAR hardwareinstallationandinspection
Check the
power-on
Power on the
NodeB
Install hardware
Hardwareinstallation
Debug the
transport
Is thecutover of
thetransport
over?
Performthe
remote debug
Start the NodeB

remote debugtool
Download scripts
at theRNC side of
NodeB to be
debugged
Personnel inOMC remoteequipment room
Prepare data
Handle
faults of the
NodeB
Informof theactiveboard
electronic serial number
Is theremote
debug
successful?
End
M2000/LMT remote debug
Figure 1.37 General process of NodeB remote software debug
8.4 Configuration Example

The following table lists the configuration of the RNC through an example of NodeB using the
FE interface.
Name
RNC
address
Value
interface
12 .12 .12 .1
M2000 address
11.11.11.1
NodeB
address
10 .10 .10 .10
interface
NodeB
electronic
serial number
222222222222222222222
ADD
NODEBESN:
NODEBID=111,
NBLB1="111222222222222222222222222222",
USENBLB2=Disable,
USEFE=Enable,
USEPPP=Disable,
USEMP=Disable,
PTIP="10.10.10.10", PTIPMASK="255.255.255.0", FEDHCPSVRIP="12.12.12.1";
2008-09-14
Huawei Confidential
Page 123 of 133
INTERNAL

ADD EMSIP: EMSIP="11.11.11.1", MASK="255.255.255.0";
Note:
1. The IP address of the DHCP Server must be one of the following
addresses configured in the FG2, GOU, and PEU: device IP address,
Ethernet port IP address, PPP link local IP address, and MLPP group
local IP address.
2. The electronic serial number of the NodeB can be queried directly from
the main control board of the NodeB.
For the software debug, see the WCDMA Iub IPRAN Networking NodeB Remote Software
Debug Guide.
2008-09-14
Huawei Confidential
Page 124 of 133
IPRAN
Chapter 9 Troubleshooting
9.1 Troubleshooting related to the RNC
9.1.1 Using the Tracert for Analysis in the case of Failure to Ping Packets
1. Application scenario
When packets failed to be pinged or the delay is large, analyze the path of packets
to be pinged by using the Tracert. The displayed information indicates in which
gateway or path packets are delayed, and the delay time. The information is helpful
for locating the fault. For the Trace principles, see the V18 IPRAN Deployment
Guide.
2. Description
1) Run Tracert to query all path information from the PC to the peer device. For
example,
2) On the RNC: TRC IPADDR: SRN=0, SN=18, DESTIP="10.10.10.10";

3. Commands on the RNC
DSP ARP: Query the port ARP table.
DSP IPRT: Query the board route table

2008-09-14
1 , 133
IPRAN
DSP ETHPORT: Query the port state and packet receiving and transmitting
9.1.2 Problems related to the SCTP

1. Principles
RNC
SPU
Debugdevice
PIU
HUB
Bearer network
Peer NE
Capture
packets by the
Ethreal
The data channel of the SCTP: SPU <--> PIU <--> Bearer network <--> Peer NE
When you locate the fault of the connection failure or one-way connection, you
should perform the following:
As shown in the dotted line in the preceding figure, use the Ethereal to catch
packets between the bearer network and RNC, and check whether packets exist in
the network. If packets are unavailable in the network, the source end does not
send packets. Then, check whether the problem results from the RNC side or nonRNC side.
This principle applies to the location of a SCTP problem or other problems.
2. One-way connection due to incorrect configuration in the upper layer
The tracing is performed on site. The following figure shows trace results.
The peer end transmits the INIT. The local end returns INITACK. Both ends start to
2008-09-14
2 , 133
IPRAN
interact with Cookie. Then, the RNC sends an ABORT. The peer end continues to
transmit the INIT. In the initial link establishment, the RNC transmits the ABORT.
The causes are as follows:
The data receiving and transmitting are normal. The processing of protocol
messages is abnormal, because the protocol is processed on the SPU. After the
start of the SPU, the system prints that the upper layer link is not configured.
Location principle
Check the following:
1. Interconnection parameters of the SCTP: Check whether the IP address
and port are consistent with the negotiation.
2. No configuration of the upper layer application of the SCTP: For
example, the NCP, CCP, and M3UA are not configured.
3. Connection failure due to the loss of Cookie packets
In a test, the signaling interaction is as follows (results traced at the RNC side):
NodeB
RNC
I NI T
I NI TACK
I NI T
I NI TACK
I NI T
I NI TACK
ABORT
According to the signaling tracing, the NodeB correctly sends the INIT and the RNC
also correctly returns the INITACK. The NodeB does not send COOKIE.
The causes are as follows: Use the Ethereal to catch packets. Packets exist in the
network. At the NodeB side, the symptom is as follows:
2008-09-14
3 , 133
IPRAN
NodeB
RNC
INIT
INITACK
COOKIE
Timeout
INIT
INITACK
COOKIE
Timeout
INIT
INITACK
According to the tracing on the SPU, the packet does not reach the SPU. The
packet may be lost in the PIU.
The INIT and INITACK packets can be received and transmitted normally. It
indicates that the channel is normal.
The INIT packets can be received. The RNC cannot receive COOKIE packets. The
comparison of two packets (including quintuple, VLAN, and IP header) indicates
that no error is found. The COOKIE packet is longer than the INIT packet. Check
the MTU and find that it is too small. The PIU loses the MTU. Run SET ETHPORT
to set the MTU to a larger value. The problem is solved.
4. Location of faults related to the SCTP
Handlings of a problem that does not comply with the protocol:
1. Analyze the tracing on the SPU. Analyze whether each field of each
protocol message is correct.
2. Start the redirection of the SPU serial port and analyze the printing
information on the SPU.
3. Locate the problem on the SPU according to the information
corresponding to the serial port redirection.
Note: Usually, this type of problem results from incorrect configurations. Hence,
engineers should check configurations.
2008-09-14
4 , 133
IPRAN
9.1.3 Cases of M3UA Common Problems

1. The link establishment fails due to inconsistent configurations at both ends
Symptom:
One end of the link is DOWN and the other end is INACTIVE. The ASP end sends UP
messages to the SGP periodically.
Handling:
1. Analyze codes. When configuration at both ends are inconsistent, the
SGP returns the ACK after the receive of the UP message, with carrying
the error information in the Info field. After receiving of the ACK, the ASP
discards the message, without any processing. After the timeout of the
UP timer, the ASP sends the UP message again.
2. Analyze configuration data. It is found that the configurations of the OPC
and DPC at both ends are not matched. This is the cause.
Comments:
In the case of the data configuration, engineers should ensure the correctness of the data.
The data check mechanism is available in the M3UA, and the mechanism cannot check
the configuration of the peer end. In the case of the data configuration, engineers should
check configuration data at the peer end.
2. A link fails to be established due to the repeated configuration of the ASPID
Symptom:
At the ASP side, one link is configured. ASP ID is 65536. During the link establishment, it
is found that the SGP side returns Error (ASP illegal flag). The link fails to be established.
Handling:
1. Analyze the codes. During the link establishment, the system judges
whether the link with the ID is recorded in the linkset when the UP
message is received. If yes, it indicates that the link is established and
the system returns Error. The link is not established.
2. After the communications with the product line, it is found that the link is
added in the case of the online operations. The product personnel do not
know whether the ID in the previous links exists. Engineers guess that
the possibility is high.
3. After the replacement of the ASP ID, the problem is solved.
Comments:
2008-09-14
5 , 133
IPRAN
When data is dynamically added, engineers should familiar with the previous
configurations to avoid the conflict between the new data and old data.
Chapter 10 Alarms
10.1 Alarms at the RNC Side (V210)
ALM-1711 PATH Fault
ALM-1712 PATH Forward Congestion
ALM-1713 PATH Backward Congestion
ALM-1714 Port Forward Congestion
ALM-1715 Port Backward Congestion
ALM-1721 Logical Port Forward Congestion
ALM-1722 Logical Port Backward Congestion
ALM-1851
ALM-1852 SCTP Link Congested
ALM-1853 Link Destination IP Changeover
ALM-1861 M3UA Link Fault
ALM-1862 M3UA Link Congestion
ALM-1863 M3UA destination entity route invalid
ALM-1864 M3UA route unavailable
ALM-1865 M3UA destination entity inaccessible
ALM-2602 PPP/MLPPP Link Down
ALM-2604 MLPPP Group Down
ALM-2606 IP PATH Down
ALM-2609 FE Port Active/Standby Switchover
ALM-2612 interface board bottom GE link fault alarm
ALM-2613 Ethernet port work mode change alarm
ALM-2622 MLPPP group link bandwidth change alarm
ALM-2623 Ethernet port bandwidth change alarm
ALM-2624 L3 detection failure alarm
ALM-2625 IP address conflict detection alarm
2008-09-14
SAAL Link Unavailable
6 , 133
IPRAN
ALM-420 IP PM detection start failure
ALM-421 IP PM detection failure
ALM-422 logical port bandwidth adjustment exceeding threshold
ALM-851 FE Link Down
ALM-852 FE Link Send Defect Indication
ALM-853 FE Link Receive Defect Indication
ALM-854 FE Link Loop
10.2 Alarms at the NodeB Side
ALM-2750 FE Chip Initialization Failure
ALM-2751 IP Transmission Network FE Interface Abnormal
ALM-2752 IP Transmission Network PPP Interface Abnormal
ALM-2753 IP Transmission Network ML PPP Interface Abnormal
ALM-2754 PPPoE Interface Fault
ALM-2755 IP RAN NCP Abnormal
ALM-2756 IP RAN CCP Abnormal
2008-09-14
7 , 133

IP RAN Deployment Guide

Uploaded by

Document Information

Original Description:

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

IP RAN Deployment Guide

Uploaded by

Copyright:

Available Formats

Ehu

IPRAN Deployment Guide V210

Huawei Technologies Co., Ltd.

IPRAN Deployment Guide

Modified on the basis of test and review

Modified on the basis of review results

IPRAN Deployment Guide

IPRAN Deployment Guide

IPRAN Deployment Guide

IPRAN Deployment Guide

IPRAN Deployment Guide

IPRAN Deployment Guide

Dynamic Host Configuration

Open Shortest Path First

Route Information Protocol

Intermediate SystemIntermediate System

Weighted Fair Queuing

IPRAN Deployment Guide

FPMux maximum sub frame length (SUBFRLEN)=127Bytes

FPMux maximum multiplexing frame length (MAXFRAMELEN)=127Bytes

Multiplexing maximum delay (FPTIME) =2ms

// At the NodeB side:

FPMux maximum sub frame length (SUBFRAMELEN)=127Bytes

FPMux maximum multiplexing frame length (FRAMELEN)=127Bytes

Multiplexing maximum delay (TIMER) = 1ms

IPRAN Deployment Guide

1.1.2 IPRAN Header Compression

Figure 1.1 PPP frame format

The PPP frame header compression algorithm implements the following:

IP Header Compression (IPHC): The IPHC compresses the IP/UDP header of

Figure 1.2 IPHC compression range

IPRAN Deployment Guide

ACFC: RFC 1661

PFC: RFC 1661

IPHC: RFC 2507 and RFC 3544

At the RNC side:

ADD PPPLNK: MUX=Disable, IPHC=UDP/IP_HC, PFC=Enable, ACFC=Enable;

At the NodeB side:

ADD PPPLNK: IPHC=ENABLE, PFC=ENABLE, ACFC=ENABLE;

1.1.3 IPRAN Fault Detection

Address resolution protocol (ARP) detection

IPRAN Deployment Guide

Bidirectional forwarding detection (BFD)

IPRAN Deployment Guide

The detection state is not associated. If a fault is detected, only an alarm is

ARP detection (three modes)

1) Active/standby port simultaneous detection

IPRAN Deployment Guide

1) Independent port detection

Min interval of BFD packet send (MINTXINT): 30 ms

IPRAN Deployment Guide

1.2.2 Supporting Versions

BSC6810V200R010C01B051 and later

V200R010C01B040 and later

V200R010C02B040 and later

1.2.3 Other Support

FG2a: RNC packet over electronic 8-port FE or 2-port GE Ethernet Interface

PEUa: RNC 32-port Packet over E1/T1/J1 Interface Unit REV:a

UOIa_IP: RNC 4-port Packet over Unchannelized Optical STM-1/OC-3c Interface

Enabling IP over Ethernet

Providing eight FE ports and two GE electrical ports

Providing IP over FE/GE

Supporting interfaces such as Iu-CS, Iu-PS, Iu-BC, Iur, and Iub