IP RAN Engineering Guide (RAN16.0 - Draft A) PDF

WCDMA RAN
IP RAN Engineering Guide Feature

Parameter Description
Issue Draft A
Date 2014-01-20
HUAWEI TECHNOLOGIES CO., LTD.

Copyright Huawei Technologies Co., Ltd. 2014. All rights reserved.
No part of this document may be reproduced or transmitted in any form or by any means without prior written
consent of Huawei Technologies Co., Ltd.
Trademarks and Permissions
and other Huawei trademarks are trademarks of Huawei Technologies Co., Ltd.
All other trademarks and trade names mentioned in this document are the property of their respective holders.
Notice
The purchased products, services and features are stipulated by the contract made between Huawei and the
customer. All or part of the products, services and features described in this document may not be within the
purchase scope or the usage scope. Unless otherwise specified in the contract, all statements, information,
and recommendations in this document are provided "AS IS" without warranties, guarantees or representations
of any kind, either express or implied.
The information in this document is subject to change without notice. Every effort has been made in the
preparation of this document to ensure accuracy of the contents, but all statements, information, and
recommendations in this document do not constitute a warranty of any kind, express or implied.
Huawei Technologies Co., Ltd.

Address: Huawei Industrial Base
Bantian, Longgang
Shenzhen 518129
People's Republic of China
Website: http://www.huawei.com
Email: support@huawei.com
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential i

Copyright Huawei Technologies Co., Ltd.
WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description Contents
Contents
1 About This Document..................................................................................................................1

1.1 Scope..............................................................................................................................................................................1
1.2 Intended Audience..........................................................................................................................................................1
1.3 Change History...............................................................................................................................................................1
2 Engineering Guidelines...............................................................................................................3
2.1 WRFD-050402 IP Transmission Introduction on Iub Interface.....................................................................................3
2.1.1 When to Use................................................................................................................................................................3
2.1.2 Required Information..................................................................................................................................................3
2.1.3 Planning.......................................................................................................................................................................3
2.1.3.1 Network Planning.....................................................................................................................................................3
2.1.3.2 Hardware Planning...................................................................................................................................................4
2.1.4 Deployment.................................................................................................................................................................4
2.1.4.1 Process......................................................................................................................................................................4
2.1.4.2 Requirements............................................................................................................................................................5
2.1.4.3 Data Preparation.......................................................................................................................................................6
2.1.4.4 Activation.................................................................................................................................................................6
2.1.4.5 Activation Observation.............................................................................................................................................7
2.1.4.6 Deactivation..............................................................................................................................................................8
2.1.4.7 Reconfiguration........................................................................................................................................................8
2.1.5 Performance Monitoring..............................................................................................................................................9
2.1.6 Parameter Optimization...............................................................................................................................................9
2.1.7 Troubleshooting...........................................................................................................................................................9
2.2 WRFD-050409 IP Transmission Introduction on Iu Interface.....................................................................................10
2.2.1 When to Use..............................................................................................................................................................10
2.2.2 Required Information................................................................................................................................................10
2.2.3 Planning.....................................................................................................................................................................11
2.2.3.1 Network Planning...................................................................................................................................................11
2.2.3.2 Hardware Planning.................................................................................................................................................11
2.2.4 Deployment...............................................................................................................................................................11
2.2.4.1 Process....................................................................................................................................................................11
2.2.4.2 Requirements..........................................................................................................................................................12
2.2.4.3 Data Preparation.....................................................................................................................................................13
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential ii

WCDMA RAN
2.2.4.4 Activation...............................................................................................................................................................13
2.2.4.5 Activation Observation...........................................................................................................................................14
2.2.4.6 Deactivation............................................................................................................................................................14
2.2.4.7 Reconfiguration......................................................................................................................................................14
2.2.5 Performance Monitoring............................................................................................................................................14
2.2.6 Parameter Optimization.............................................................................................................................................14
2.2.7 Troubleshooting.........................................................................................................................................................14
2.3 WRFD-050410 IP Transmission Introduction on Iur Interface....................................................................................14
2.3.1 When to Use..............................................................................................................................................................14
2.3.2 Required Information................................................................................................................................................15
2.3.3 Planning.....................................................................................................................................................................15
2.3.4 Deployment...............................................................................................................................................................15
2.3.4.1 Process....................................................................................................................................................................15
2.3.4.2 Requirements..........................................................................................................................................................16
2.3.4.4 Activation...............................................................................................................................................................17
2.3.4.6 Deactivation............................................................................................................................................................18
3 Engineering Guidelines for Transmission Reliability........................................................19

3.1 Ethernet Port Backup for the Base Station Controller..................................................................................................19
3.1.1 When to Use Ethernet Port Backup for the Base Station Controller.........................................................................19
3.1.2 Planning.....................................................................................................................................................................19
3.1.3 Deployment...............................................................................................................................................................19
3.1.3.1 Requirements..........................................................................................................................................................19
3.1.3.2 Activation...............................................................................................................................................................20
3.1.3.2.1 Using MML Commands......................................................................................................................................20
3.1.3.2.2 MML Command Examples.................................................................................................................................20
3.1.3.2.3 Using the CME....................................................................................................................................................20
3.1.3.4 Deactivation............................................................................................................................................................21
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential iii

WCDMA RAN
3.2 Ethernet Route Backup for the Base Station Controller...............................................................................................21
3.2.1 When to Use Ethernet Route Backup for the Base Station Controller......................................................................22
3.2.2 Planning.....................................................................................................................................................................22
3.2.3 Deployment...............................................................................................................................................................22
3.2.3.1 Requirements..........................................................................................................................................................22
3.2.3.3 Activation...............................................................................................................................................................23
3.2.3.3.3 Using the CME....................................................................................................................................................24
3.2.3.5 Deactivation............................................................................................................................................................25
3.3 Ethernet Route Backup for the Base Station................................................................................................................26
3.3.1 When to Use Ethernet Route Backup for the Base Station.......................................................................................26
3.3.2 Planning.....................................................................................................................................................................26
3.3.3 Deployment...............................................................................................................................................................26
3.3.3.1 Requirements..........................................................................................................................................................26
3.3.3.3 Activation...............................................................................................................................................................27
3.3.3.3.3 Using the CME....................................................................................................................................................29
3.3.3.5 Deactivation............................................................................................................................................................30
3.4 Link Aggregation in Scenario 1....................................................................................................................................31
3.4.1 When to Use Link Aggregation in Scenario 1...........................................................................................................31
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential iv

WCDMA RAN
3.4.2 Planning.....................................................................................................................................................................31
3.4.3 Deployment...............................................................................................................................................................31
3.4.3.1 Requirements..........................................................................................................................................................31
3.4.3.3 Activation...............................................................................................................................................................32
3.4.3.3.3 Using the CME....................................................................................................................................................33
3.4.3.5 Deactivation............................................................................................................................................................34
3.5.2 Planning.....................................................................................................................................................................35
3.5.3 Deployment...............................................................................................................................................................35
3.5.3.1 Requirements..........................................................................................................................................................35
3.5.3.3 Activation...............................................................................................................................................................36
3.5.3.3.3 Using the CME....................................................................................................................................................37
3.5.3.5 Deactivation............................................................................................................................................................38
3.6.2 Planning.....................................................................................................................................................................39
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential v

WCDMA RAN
3.6.3 Deployment...............................................................................................................................................................39
3.6.3.1 Requirements..........................................................................................................................................................39
3.6.3.3 Activation...............................................................................................................................................................39
3.6.3.3.3 Using the CME....................................................................................................................................................40
3.6.3.5 Deactivation............................................................................................................................................................41
3.7 OM Channel Backup....................................................................................................................................................41
3.7.1 When to Use OM Channel Backup...........................................................................................................................41
3.7.2 Planning.....................................................................................................................................................................42
3.7.3 Deployment...............................................................................................................................................................42
3.7.3.1 Requirements..........................................................................................................................................................42
3.7.3.3 Activation...............................................................................................................................................................43
3.7.3.3.3 Using the CME....................................................................................................................................................45
3.7.3.5 Deactivation............................................................................................................................................................46
4 Engineering Guidelines for Transmission Maintenance and Detection..........................47

4.1 BFD..............................................................................................................................................................................47
4.1.1 When to Use BFD......................................................................................................................................................47
4.1.2 Planning.....................................................................................................................................................................47
4.1.3 Deployment...............................................................................................................................................................47
4.1.3.1 Requirements..........................................................................................................................................................47
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential vi

WCDMA RAN

4.1.3.3 Precautions..............................................................................................................................................................53
4.1.3.4 Activation...............................................................................................................................................................54
4.1.3.4.3 Using the CME....................................................................................................................................................54
4.1.3.6 Deactivation............................................................................................................................................................57
4.2 GTP-U Echo.................................................................................................................................................................59
4.2.1 When to Use GTP-U Echo........................................................................................................................................59
4.2.2 Deployment...............................................................................................................................................................59
4.2.2.1 Requirements..........................................................................................................................................................59
4.2.2.3 Activation...............................................................................................................................................................61
4.2.2.3.3 Using the CME....................................................................................................................................................62
4.2.2.5 Deactivation............................................................................................................................................................63
5 Parameters.....................................................................................................................................65
6 Counters........................................................................................................................................66
7 Glossary.........................................................................................................................................67
8 Reference Documents.................................................................................................................68
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential vii

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 1 About This Document
1 About This Document
1.1 Scope
This document describes the engineering guidelines for interfaces, transmission reliability, and
maintenance and detection in IP transmission mode.
This document covers the following features:
l WRFD-050402 IP Transmission Introduction on Iub Interface

l WRFD-050409 IP Transmission Introduction on Iu Interface
l WRFD-050410 IP Transmission Introduction on Iur Interface
For details about the working principles of the IP Transmission feature, see SingleRAN IP
Transmission Feature Parameter Description.
1.2 Intended Audience

This document is intended for personnel who:
l Need to understand the features described herein

l Work with Huawei products
1.3 Change History

This section provides information about the changes in different document versions. There are
two types of changes, which are defined as follows:
l Feature change
Changes in features of a specific product version
l Editorial change
Changes in wording or addition of information that was not described in the earlier version
Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 1

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 1 About This Document
Draft A (2014-01-20)
This document is created for RAN16.0.
Contents of the document are moved from IP RAN Feature Parameter Description.

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 2 Engineering Guidelines
2 Engineering Guidelines
2.1 WRFD-050402 IP Transmission Introduction on Iub

Interface
This section describes how to activate, deploy, and maintain the IP Transmission Introduction
on Iub Interface feature.
The Iub interface supports the configuration of IP paths or transmission resource pools. This
document provides the engineering guidelines with the configuration of IP paths. For details
about the engineering guidelines with the configuration of transmission resource pools, see
Transmission Resource Pool in RNC Feature Parameter Description. The BSC6910 supports
only the transmission resource pool networking mode.
2.1.1 When to Use

Use this feature when IP transmission is used on the Iub interface.
2.1.2 Required Information

l Physical layer data: physical layer configurations of the peer end, including port and VLAN
configurations
l Transport layer data: device IP address of the peer end, next-hop IP address of the NodeB,
and maximum transmission unit (MTU) and DSCP configurations of the NodeB
l Data link layer data: SCTP configurations of the peer end
2.1.3 Planning
2.1.3.1 Network Planning

l Layer 3 networking with IP over Ethernet is recommended.
l Neither layer 2 networking nor IP over E1/T1 is recommended.

WCDMA RAN
2.1.3.2 Hardware Planning

l The FG2a/FG2c and GOUa/GOUc of the BSC6900 support this feature.
l The BTS3902E and BTS3803E support this feature.
l The following BTS3900 boards support this feature: WMPT, UMPT, UTRP2, UTRP9, and
UTRPc.
2.1.4 Deployment
2.1.4.1 Process
Figure 2-1 shows the procedure for deploying IP Transmission Introduction on Iub Interface on
the RNC side.
Figure 2-1 Deployment of IP Transmission Introduction on Iub Interface (RNC)

WCDMA RAN
Figure 2-2 shows the procedure for deploying IP Transmission Introduction on Iub Interface on
the NodeB side.
Figure 2-2 Deployment of IP Transmission Introduction on Iub Interface (NodeB)
2.1.4.2 Requirements
l Bearer network QoS
Interfac Unidirectional Delay Jitter (ms) Packet Loss Rate (10-x)

e (ms)
Maximum Target Maximum Targe Maximum Targe

Value Value Value t Value t
Value Value
Iub 40 10 15 2 10-3 10-4
Iu-CS 15 10 7 7 10-3 10-4
Iu-PS 15 10 7 7 10-3 10-6
Iur 15 10 7 7 10-3 10-4

WCDMA RAN
NOTE
l The Maximum Value column indicates the basic commercial requirement for deploying radio services.
l The Target Value column lists the requirement for the transport network when customers require high
KPIs on the radio network. For example, the maximum throughput for HSPA+ users is required to be
84 Mbit/s.
l These QoS requirements are not applicable to satellite bearers.
l License
The license for the IP Transmission Introduction on Iub Interface feature has been activated.
For details on how to activate the license, see License Management Feature Parameter
Description.
Feature ID Feature Name License Control NE Sales Unit

Item
WRFD-05040 IP Transmission IP Transportation in RNC Erl+Mbps

2 Introduction on Iub Interface
Iub Interface
2.1.4.3 Data Preparation

For data preparation on the RNC side, see section "Data Preparation for Initial Configuration"
in BSC6900 UMTS Initial Configuration Guide (MML-Based).
For data preparation on the NodeB side, see section "Preparing Transport Data for a NodeB"
in 3900 Series Base Station Initial Configuration Guide.
For data preparation on the BTS3902E&BTS3803E side, see section "Preparing Data" in
BTS3902E&BTS3803E WCDMA Initial Configuration Guide.
2.1.4.4 Activation
l For details about activation using MML commands on the RNC side, follow the path below
from the navigation tree of BSC6900 UMTS Initial Configuration Guide (MML-Based)
> Configuring the Interfaces > Configuring the Iub Interface (over IP). For details
about activation using the CME on the RNC side, follow the path below from the navigation
tree of BSC6900 UMTS Initial Configuration (CME-based) > Configuring BSC6900
Data (General Configuration) > Configuring Interface Data.
l For details about activation on the NodeB side, follow the path below from the navigation
tree of 3900 Series Base Station Initial Configuration Guide: 3900 Series Base Station
Initial Configuration (Based on the CME) > Creating a NodeB > Creating a Single
NodeB > Configuring NodeB Transport Data > Configuring Physical NodeB
Transport Data (Non-Secure Networking).
l For details about activation on the BTS3902E&BTS3803E side, follow the path below from
the navigation tree of BTS3902E&BTS3803E WCDMA Initial Configuration
Guide: Creating a NodeB > Creating a Single NodeB > Configuring NodeB Transport
Data > Configuring Physical NodeB Transport Data (Non-Secure Networking).

WCDMA RAN
MML Command Examples

For details, see section "Typical Configuration Scripts" in BSC6900 UMTS Initial Configuration
Guide (MML-Based) and "Typical Configuration Scriptsn" in 3900 Series Base Station Initial
Configuration (Using MML Commands).
2.1.4.5 Activation Observation

l On the RNC side
Step 1 Run the BSC6900 MML command DSP IPPATH to check whether the IP path is available and
whether the bandwidth for the IP path is in use.
Expected result: The command output shows that the value of the Operation state parameter
is Available and the values of the Used forward bandwidth of path and Used backward
bandwidth of path parameters are not 0.
NOTE
Before running the DSP IPPATH command, run the BSC6900 MML command ADD IPPATH with
PATHCHK set to ENABLED.
Step 2 Optional: Run the BSC6900 command DSP IPCHK to check whether the value of the Check
state parameter is UP.
Expected result: The command output shows that the value of the Check state parameter is
UP.
Step 3 Run the BSC6900 command DSP SCTPLNK to check whether the value of the Operation
state parameter is Available.
Expected result: The command output shows that the value of the Operation state parameter
is Available.
Step 4 Use UE 1 to call UE 2. Use UE 2 to answer and start a conversation with UE 1.
Expected result: The conversation is normal and the voice is clear.
Step 5 Optional: Start a Cell Trace task on the RNC LMT. On the FMR tab, select Transport Data
Periodic Report and enter SCCPCH ID and Report Period of the cell to be traced.
Expected result: On the Results of cell message tracing window, Trace Type is IP Interface
Trace.
Step 6 Optional: Start an Iub Interface Trace task on the RNC LMT. On the Basic tab, select
SCTP. On the SCTP tab, enter SCTP Link ID and select SCTP Message.
Expected result: On the Results of Tracing Messages on the Iub Interface window, Trace
Type is SCTP Message Trace.
----End
The following table lists the counters related to IP transmission over the Iub interface on the
RNC side.

WCDMA RAN
Counter Counter Name Counter Description

ID
67191612 VS.SCTP.RX.PKGNUM Number of IP Packets Received on the

SCTP Link
67191613 VS.SCTP.TX.PKGNUM Number of IP Packets Transmitted on

the SCTP Link
67195399 VS.IPPATH.IPLAYER.RXPACK- Number of Packets Received at the IP

ETS Layer of an IP Path
67195395 VS.IPPATH.IPLAYER.TXPACK- Number of Packets Transmitted at the

ETS IP Layer of an IP Path
l On the NodeB side
Step 1 Run the NodeB MML command DSP ETHPORT to check the Ethernet physical port status.
Step 2 Optional: Start Iub Interface Trace and IP Message Statistics tasks on the NodeB LMT.
Expected result: There are traced messages. Services are carried on the SCTP link and IP path.
----End
The following table lists the counters related to IP transmission over the Iub interface on the
NodeB side.
Counter ID Counter Name Counter Description
1542455874 VS.IPPath.TxPkts Number of Packets Successfully Transmitted on the

IP Path
1542455877 VS.IPPath.RxPkts Number of Packets Successfully Received on the IP

Path
1542455424 VS.Sctp.RxPkts Number of IP Packets Successfully Received on the

SCTP Link
1542455425 VS.Sctp.TxPkts Number of IP Packets Successfully Transmitted on

the SCTP Link
2.1.4.6 Deactivation
This feature does not need to be deactivated.
2.1.4.7 Reconfiguration
For details, see RAN Reconfiguration Guide.

WCDMA RAN
2.1.5 Performance Monitoring

None
2.1.6 Parameter Optimization

None
2.1.7 Troubleshooting
l For details about troubleshooting on the RNC side, see section "Troubleshooting IP
Transmission Faults" in RAN Troubleshooting Guide. For details about alarm handling
procedures on the RNC side, see section "Transport Alarm" in BSC6900 UMTS Alarm
Reference.
l The following table lists the alarms on the NodeB side.
Alarm ID Alarm Name NE Feature ID Feature

Name
ALM-25879 Ethernet Port NodeB WRFD-05040 IP

Broadcast 2 Transmission
Packets Introduction on
Exceeding Iub Interface
Alarm
ALM-25880 Ethernet Link NodeB WRFD-05040 IP

Fault 2 Transmission
Introduction on
Iub Interface
ALM-25885 IP Address NodeB WRFD-05040 IP

Conflict 2 Transmission
Introduction on
Iub Interface
ALM-25886 IP Path Fault NodeB WRFD-05040 IP

2 Transmission
Introduction on
Iub Interface
ALM-25888 SCTP Link NodeB WRFD-05040 IP

Fault 2 Transmission
Introduction on
Iub Interface
ALM-25889 SCTP Link NodeB WRFD-05040 IP

Congestion 2 Transmission
Introduction on
Iub Interface

WCDMA RAN
Alarm ID Alarm Name NE Feature ID Feature

Name
ALM-25897 IP Excessive NodeB WRFD-05040 IP

Frame Error 2 Transmission
Rate Introduction on
Iub Interface
ALM-25898 IP Path NodeB WRFD-05040 IP

Excessive 2 Transmission
Packet Loss Introduction on
Rate Iub Interface
ALM-25901 Remote NodeB WRFD-05040 IP

Maintenance 2 Transmission
Link Failure Introduction on
Iub Interface
ALM-25835 NCP Fault NodeB WRFD-05040 IP

2 Transmission
Introduction on
Iub Interface
ALM-25836 CCP Fault NodeB WRFD-05040 IP

2 Transmission
Introduction on
Iub Interface
2.2 WRFD-050409 IP Transmission Introduction on Iu

Interface
This section describes how to activate, verify, and deactivate the Hybrid Iub IP Transmission
feature.
The BSC6910 does not support the Hybrid Iub IP Transmission feature.
The BTS3902E and BTS3803E do not support this feature.
2.2.1 When to Use

Use this feature when IP transmission is used on the Iu interface.

configurations
and MTU and DSCP configurations of the NodeB

WCDMA RAN
2.2.3 Planning

l The layer 3 network with IP over Ethernet on the RNC and NodeB sides is recommended.

The FG2a/FG2c and GOUa/GOUc of the BSC6900 support this feature.
2.2.4 Deployment
2.2.4.1 Process
Figure 2-3 shows the deployment process of the IP Transmission Introduction on Iu Interface
feature.

WCDMA RAN
Figure 2-3 Deployment of IP Transmission Introduction on Iu Interface
Interface Unidirectional Delay Jitter (ms) Packet Loss Rate (10-

(ms) x)
Maximu Target Maximu Target Maximu Target

m Value Value m Value Value m Value Value
Iub 40 10 15 2 10-3 10-4

WCDMA RAN
Iu-CS 15 10 7 7 10-3 10-4
Iu-PS 15 10 7 7 10-3 10-6
Iur 15 10 7 7 10-3 10-4
NOTE
84 Mbit/s.
l License
The IP Transportation in Iu Interface license has been activated. For details on how to
activate the license, see License Management Feature Parameter Description.
Feature ID Feature License NE Sales Unit

Name Control Item
WRFD-05040 IP IP RNC Erl+Mbps

9 Transmission Transportation
Introduction on in Iu Interface
Iu Interface
l NE
The CN nodes must support IP transmission.

For data preparation on the RNC side, see section "Data Preparation for Initial Configuration"
in BSC6900 UMTS Initial Configuration Guide (MML-Based).
2.2.4.4 Activation
l For details about activation using MML commands, follow the path below from the
navigation tree of BSC6900 UMTS Initial Configuration Guide (MML-Based) >
Configuring the Interfaces > Configuring the Iu Interface (over IP).
l For details about activation using the CME, follow the path below from the navigation tree
of BSC6900 UMTS Initial Configuration (CME-based) > Configuring BSC6900 Data
(General Configuration) > Configuring Interface Data.

Guide (MML-Based).

WCDMA RAN

For details, see Activation Observation in 2.1.4.5 Activation Observation. In addition, perform
the following:
Optional: Start an Iub Interface Trace task on the RNC LMT. On the Basic tab, select SCTP
and on the displayed SCTP tab, enter SCTP Link ID and select SCTP Message.
Expected result: On the Results of Tracing Messages on the Iub Interface window, Trace

None

None
For details about troubleshooting, see section "Troubleshooting IP Transmission Faults" in RAN
Troubleshooting Guide. For details about alarm handling procedures, see section "Transport
Alarm" in BSC6900 UMTS Alarm Reference.
2.3 WRFD-050410 IP Transmission Introduction on Iur

Interface
This section describes how to activate, verify, and deactivate the IP Transmission Introduction
on Iur Interface feature.
The Iur interface supports the configuration of IP paths or transmission resource pools. This
document provides the engineering guidelines with the configuration of IP paths. For details
about the engineering guidelines with the configuration of transmission resource pools, see
Transmission Resource Pool in RNC Feature Parameter Description. The BSC6910 supports
only the transmission resource pool networking mode.
2.3.1 When to Use

Use this feature when IP transmission is used on the Iur interface.

WCDMA RAN

configurations
and MTU and DSCP configurations of the NodeB
2.3.3 Planning

l The layer 3 network with IP over Ethernet on the RNC and NodeB sides is recommended.

The FG2a/FG2c and GOUa/GOUc of the BSC6900 support this feature.
2.3.4 Deployment
2.3.4.1 Process
Figure 2-4 shows deployment process of IP Transmission Introduction on Iur Interface.

WCDMA RAN
Figure 2-4 Deployment of IP Transmission Introduction on Iur Interface
Interface Unidirectional Delay Jitter (ms) Packet Loss Rate (10-

(ms) x)
Maximu Target Maximu Target Maximu Target

m Value Value m Value Value m Value Value
Iub 40 10 15 2 10-3 10-4
Iu-CS 15 10 7 7 10-3 10-4
Iu-PS 15 10 7 7 10-3 10-6
Iur 15 10 7 7 10-3 10-4

WCDMA RAN
NOTE
84 Mbit/s.
l License
The license for the IP Transmission Introduction on Iur Interface feature has been activated.
For details on how to activate the license, see License Management Feature Parameter
Description.

Name Control Item
WRFD-05041 IP IP RNC Erl+Mbps

0 Transmission Transportation
Introduction on in Iur Interface
Iur Interface
l NE
The adjacent RNC must support the IP Transmission Introduction on Iur Interface feature.

For details, see section "Data Preparation for Initial Configuration" in BSC6900 UMTS Initial
Configuration Guide (MML-Based).
2.3.4.4 Activation
l For details about activation using MML commands, follow the path below from the
navigation tree of BSC6900 UMTS Initial Configuration Guide (MML-Based) >
Configuring the Interfaces > Configuring the Iur Interface (over IP).
l For details about activation using the CME, follow the path below from the navigation tree
of BSC6900 UMTS Initial Configuration (CME-based) > Configuring BSC6900 Data
(General Configuration) > Configuring Interface Data.

Guide (MML-Based).

For details, see Activation Observation in 2.1.4.5 Activation Observation. In addition, perform
the following:
Optional: Start an Iur Interface Trace task on the RNC LMT. On the Basic tab, select SCTP.
On the SCTP tab, enter SCTP Link ID and select SCTP Message.

WCDMA RAN
Expected result: On the Results of Tracing Messages on the Iur Interface window, Trace

None

None
For details about troubleshooting, see section "Troubleshooting IP Transmission Faults" in RAN
Troubleshooting Guide. For details about alarm handling procedures, see section "Transport
Alarm" in BSC6900 UMTS Alarm Reference.

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 3 Engineering Guidelines for Transmission Reliability
3 Engineering Guidelines for Transmission

Reliability
3.1 Ethernet Port Backup for the Base Station Controller
3.1.1 When to Use Ethernet Port Backup for the Base Station
Controller
It is recommended that layer 3 networking be used. The base station controller is networked
with the router that supports VRRP.
3.1.2 Planning

The inter-board active and standby ports on the active and standby boards of the base station
controller are connected to the layer 3 router.

The FG2a/FG2c/FG2d and GOUa/GOUc/GOUd boards of the BSC6900 support Ethernet port
backup.
3.1.3 Deployment
If the base station controller is directly connected to the layer 3 router, the router must support
VRRP over VLANIF.
If the base station controller is not directly connected to the router, the switch for layer 2 must
be configured and the base station controller is connected to the switch.

WCDMA RAN
3.1.3.2 Activation
3.1.3.2.1 Using MML Commands

Step 1 Run the base station controller MML command ADD ETHREDPORT with Subrack No., Slot
No., and Port No. set to the location where the Ethernet ports on the active board are.
Step 2 Run the base station controller MML command ADD ETHIP to set the IP address of the Ethernet
port.
Step 3 Run the base station controller MML command STR IPCHK to enable BFD between the IP
address of the Ethernet port and one of the real IP addresses of the VRRP-enabled router. Set
Check type to SBFD, Carry port type to ETHPORT, Whether affect the port swapping to
YES(YES), and Route associated flag to NO(NO).
Step 4 Run the base station controller MML command STR IPCHK to enable BFD between the IP
address of the Ethernet port and the other one of the real IP addresses of the VRRP-enabled
router. Set Check type to SBFD, Carry port type to ETHPORT, Whether affect the port
swapping to YES(YES), and Route associated flag to NO(NO).
----End
3.1.3.2.2 MML Command Examples

//Activating Ethernet port backup
ADD ETHREDPORT: SRN=2, SN=26, PN=1;
ADD ETHIP: SRN=2, SN=26, PN=1, IPINDEX=0, IPADDR="126.126.126.1",
MASK="255.255.255.0";
STR IPCHK: SRN=2, SN=26, CHKN=0, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=1,
MODE=CHECK_ON_PRIMARY_PORT, PEERIP="126.126.126.2", WHETHERAFFECTSWAP=YES,
ROUTEASSOCIATEDFLAG=NO;
MODE=CHECK_ON_PRIMARY_PORT, PEERIP="126.126.126.3", WHETHERAFFECTSWAP=YES,
ROUTEASSOCIATEDFLAG=NO;
3.1.3.2.3 Using the CME
Table 3-1 Configuring parameters on the CME
SN MO NE Parameter Parameter Configura

Name ID ble in CME
Batch
Modificati
on
1 ETHREDP BSC6900 Subrack No. SRN No

ORT
Slot No. SN
Port No. PN
2 ETHIP BSC6900 Local IP IPADDR No

address
Subnet mask MASK

WCDMA RAN

Step 1 Run the base station controller MML command DSP ETHPORT to check whether the Ethernet
port is functional.
Step 2 Run the base station controller MML command PING IP to check whether the IP address
between the local and peer ends can be pinged.
Step 3 Disconnect the cable from the active port. Run the base station controller MML command PING
IP to check whether the IP address between the local and peer ends can be pinged.
Step 4 Connect the cable to the active port and disconnect the cable from the standby port. Run the base
station controller MML command PING IP to check whether the IP address between the local
and peer ends can be pinged.
Step 5 Connect the cable to the standby port.
----End

Step 1 Run the base station controller MML command STP IPCHK to disable BFD.
Step 2 Run the base station controller MML command RMV ETHIP to remove the IP address of the
Ethernet port.
Step 3 Run the base station controller MML command RMV ETHREDPORT to remove the Ethernet
port.
----End

//Deactivating Ethernet port backup
STP IPCHK: SRN=0, SN=26, CHKN=0;
RMV ETHIP: SRN=2, SN=26, TRKN=2, IPINDEX=0;
RMV ETHREDPORT: SRN=2, SN=26, TRKN=2;

Run the base station controller MML command DSP ETHPORT to check whether the Ethernet
port is functional.
If ALM-21346 IP Connectivity Check Failure and ALM-21345 Ethernet Link Fault are reported,
clear them by referring to the alarm handling suggestions.
3.2 Ethernet Route Backup for the Base Station Controller

WCDMA RAN
3.2.1 When to Use Ethernet Route Backup for the Base Station
Controller
with the router that supports active/standby gateway.
3.2.2 Planning

The inter-board active and standby routes on the active and standby boards of the base station
controller are connected to the router that supports active/standby gateway.

The following boards support Ethernet route backup for the base station controller:
l FG2a/FG2c/ FG2d and GOUa/GOUc/GOUd of the BSC6900

l FG2c/FG2d, GOUc/GOUd, and EXOUa of the BSC6910
3.2.3 Deployment
A standby route is configured from each of the active and standby gateways to the base station
controller. If a route is faulty, the gateway router still can return packets to the base station
controller through the standby route.
When no IP transmission resource pools are configured, the base station controller configures
routes based on the destination IP address. When IP transmission resource pools are configured,
the base station controller configures routes based on the source IP address.
Table 3-2 Data to prepare when the routes are configured based on the destination IP address
Parameter Parameter ID Setting Notes Data Source

Name
Forward route NEXTHOP Set this parameter to the Transport network

address IP address of the active/ plan
standby gateway.
Priority PRIORITY Set this parameter to Transport network

HIGH for the active plan
gateway and LOW for
the standby gateway.

WCDMA RAN
Table 3-3 Data to prepare when the routes are configured based on the source IP address
Parameter Parameter ID Setting Notes Data Source

Name
Forward route NEXTHOP Set this parameter to the Transport network

address IP address of the active plan
gateway.
Standby next hop STANDBYNEXTHO Set this parameter to the Transport network
P IP address of the standby plan
gateway.
3.2.3.3 Activation

When routes are configured based on the destination IP address, perform the following steps:
Step 1 Run the base station controller MML command ADD IPRT with Forward route address set
to the IP address of the active gateway and Priority to HIGH.
Step 2 Run the base station controller MML command ADD IPRT with Forward route address set
to the IP address of the standby gateway and Priority to LOW.
----End
When routes are configured based on the source IP address, perform the following steps:
Step 1 Run the base station controller MML command ADD SRCIPRT with Forward route
address set to the IP address of the active gateway, Standby Next hop switch to YES(YES),
and Standby next hop to the IP address of the standby gateway.
Step 2 Run the base station controller MML command STR IPCHK with Check type set to SBFD,
Carry port type to ETHPORT, Check mode to CHECK_ON_INDEPENDENT_PORT
(Check on Independent Port), and Route associated flag to YES(YES) to start BFD for the
active gateway router.
Step 3 Run the base station controller MML command STR IPCHK with Check type set to SBFD,
Carry port type to ETHPORT, Check mode to CHECK_ON_INDEPENDENT_PORT
(Check on Independent Port), and Route associated flag to YES(YES) to start BFD for the
standby gateway router.
----End

//Activating Ethernet route backup for the base station controller
//Running the following commands when routes are configured based on the
destination IP address
ADD IPRT: SRN=2, SN=26, DSTIP="10.10.10.10", DSTMASK="255.255.255.255",
NEXTHOPTYPE=Gateway, NEXTHOP="126.126.126.2", PRIORITY=HIGH;
ADD IPRT: SRN=2, SN=26, DSTIP="10.10.10.10", DSTMASK="255.255.255.255",
NEXTHOPTYPE=Gateway, NEXTHOP="126.126.127.2", PRIORITY=LOW;
//Running the following commands when routes are configured based on the source IP

WCDMA RAN
address
ADD SRCIPRT: SRN=2, SN=26, IPTYPE=DEVIP, SRCIPADDR="20.20.20.1",
NEXTHOP="126.126.126.2", STANDBYNEXTHOPSWITCH=YES,
STANDBYNEXTHOP="126.126.127.2";
//Activating BFD between the base station controller and router
STR IPCHK: SRN=2, SN=26, CHKN=0, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=1, MODE=
CHECK_ON_INDEPENDENT_PORT, PEERIP="126.126.126.2", ROUTEASSOCIATEDFLAG=YES;
MODE=CHECK_ON_INDEPENDENT_PORT, PEERIP="126.126.127.2", ROUTEASSOCIATEDFLAG=YES;
Table 3-4 Configuring parameters on the CME (when routes are configured based on the
destination IP address)

Name ID ble in CME
Batch
Modificati
on
1 IPRT Base station Forward NEXTHOP No

controller route address
Priority PRIORITY
Table 3-5 Configuring parameters on the CME (when routes are configured based on the source
IP address)

Name ID ble in CME
Batch
Modificati
on
1 SRCIPRT Base station Forward NEXTHOP No

controller route address
Standby STANDBY
Next hop NEXTHOP
switch SWITCH
Standby next STANDBY

hop NEXTHOP

When routes are configured based on the destination IP address, perform the following steps:

WCDMA RAN
Step 1 Run the base station controller MML command DSP IPRT to check whether the route is valid.
----End
When routes are configured based on the source IP address, perform the following steps:
Step 1 Run the base station controller MML command DSP SRCIPRT to check whether the route is
valid.
between the two ends can be pinged.
----End

Step 2 When routes are configured based on the destination IP address, run the base station controller
MML command RMV IPRT to remove the standby and active routes. If the removal fails,
perform operations as prompted.
Step 3 When routes are configured based on the source IP address, run the base station controller MML
command RMV SRCIPRT to remove the active and standby gateways. If the removal fails,
perform operations as prompted.
----End

//Deactivating Ethernet route backup for the base station controller
//Running the following commands when routes are configured based on the
destination IP address
RMV IPRT: SRN=2, SN=26, DSTIP="10.10.10.10", DSTMASK="255.255.255.255",
NEXTHOPTYPE=Gateway, NEXTHOP="126.126.127.2";
RMV IPRT: SRN=2, SN=26, DSTIP="10.10.10.10", DSTMASK="255.255.255.255",
NEXTHOPTYPE=Gateway, NEXTHOP="126.126.126.2";
//Running the following command when routes are configured based on the source IP
address
RMV SRCIPRT: SRN=2, SN=26, SRCIPADDR="20.20.20.1";
When routes are configured based on the destination IP address, run the MOD IPRT command
to perform reconfiguration. When routes are configured based on the source IP address, run the
MOD SCRIPRT command to perform reconfiguration.

To check whether the route is valid, run the base station controller MML command DSP
IPRT (when routes are configured based on the destination IP address) or DSP SRCIPRT
(when routes are configured based on the source IP address).

WCDMA RAN
If ALM-21346 IP Connectivity Check Failure is reported, clear the alarm by referring to the
alarm handling suggestions.
3.3 Ethernet Route Backup for the Base Station
3.3.1 When to Use Ethernet Route Backup for the Base Station
It is recommended that layer 3 networking be used. The base station is networked with the router
that supports active/standby gateway.
3.3.2 Planning

A physical port of the base station is connected to the router that supports active/standby gateway
through the layer 2 network.

The following boards support Ethernet route backup for the base station:
l GTMUb
l WMPT/UMPT/LMPT
l UTRPc/UTRP (using the daughter board UEOC/UQEC/UIEC)
3.3.3 Deployment
A standby route is configured from each of the active and standby gateways to the base station.
If a route is faulty, the gateway router still can return packets to the base station through the
standby route.
Requirements for licenses:
Feature ID Feature Name License NE Sales Unit

Control Item
LOFD/ IP Route IP Route eNodeB per eNodeB

TDLOFD-0030 Backup Backup
06

WCDMA RAN
Table 3-6 Data to prepare for Ethernet route backup for the NodeB, eNodeB, eGBTS, and co-
MPT base station
Parameter Name Parameter ID Setting Notes Data Source
Next Hop IP NEXTHOP Set this parameter to Transport

the IP address of the network plan
active/standby
gateway.
Preference PREF The active gateway Transport

takes precedence network plan
over the standby
gateway.
Table 3-7 Data to prepare for Ethernet route backup for the GBTS
Route Priority PRI The active gateway Transport

takes precedence network plan
over the standby
gateway.
Forward Route NEXTHOP Set this parameter to Transport

Address the IP address of the network plan
active/standby
gateway.
3.3.3.3 Activation

Perform the following steps for the NodeB, eNodeB, eGBTS, and co-MPT base station:
Step 1 Run the base station MML command ADD IPRT with Next Hop IP set to the IP address of the
active gateway and Preference to 60.
Step 2 Run the base station MML command ADD IPRT with Next Hop IP set to the IP address of the
standby gateway and Preference to 80.
Step 3 Run the base station MML command ADD BFDSESSION with Hop Type set to
SINGLE_HOP(Single Hop) and Session Catalog to RELIABILITY(Reliability) to start
BFD for the active gateway router.

WCDMA RAN
Step 4 Run the base station MML command ADD BFDSESSION with Hop Type set to
SINGLE_HOP(Single Hop) and Session Catalog to RELIABILITY(Reliability) to start
BFD for the standby gateway router.
Step 5 (Optional) Run the base station MML command SET GTRANSPARA with Switch Back
Time set to 300.
----End
NOTE
Set Protocol Version as the BFD session protocol version supported by the peer device.
Perform the following steps for the GBTS:
Step 1 Run the base station MML command ADD BTSIPRT with Forward Route Address set to the
IP address of the active gateway and Route Priority to 60.
Step 2 Run the base station MML command ADD BTSIPRT with Forward Route Address set to the
IP address of the standby gateway and Route Priority to 80.
Step 3 Run the base station MML command ADD BTSBFD with Hop Type set to SBFD
(SINGLE_HOP) to start BFD for the active gateway router.
Step 4 Run the base station MML command ADD BTSBFD with Hop Type set to SBFD
(SINGLE_HOP) to start BFD for the standby gateway router.
Step 5 (Optional) Run the base station MML command SET BTSGTRANSPARA with Route
switching delay set to 300.
----End

//Activating Ethernet route backup for the NodeB, eNodeB, eGBTS, and co-MPT base
station RTIDX=0, SN=7, SBT=BASE_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="126.126.126.2", PREF=60;
ADD IPRT: RTIDX=1, SN=7, SBT=BASE_BOARD, DSTIP="10.10.10.10",
DSTMASK="255.255.255.255", RTTYPE=NEXTHOP, NEXTHOP="126.126.127.2", PREF=80;
ADD BFDSESSION: SN=7, BFDSN=0, SRCIP="126.126.126.1", DSTIP="126.126.126.2",
HT=SINGLE_HOP, CATLOG=RELIABILITY, VER=STANDARD;
ADD BFDSESSION: SN=7, BFDSN=1, SRCIP="126.126.127.1", DSTIP="126.126.127.2",
HT=SINGLE_HOP, CATLOG=RELIABILITY, VER=STANDARD;
SET GTRANSPARA: SBTIME=300;
//Activating Ethernet route backup for the GBTS
ADD BTSIPRT: IDTYPE=BYID, BTSID=8, RTIDX=0, DSTIP="10.10.10.1",
DSTMASK="255.255.255.255", PRI=60,RTTYPE=NEXTHOP, NEXTHOP="126.126.126.2";
ADD BTSIPRT: IDTYPE=BYID, BTSID=8, RTIDX=1, DSTIP="10.10.10.1",
DSTMASK="255.255.255.255", PRI=80,RTTYPE=NEXTHOP, NEXTHOP="126.126.127.2";
ADD BTSBFD: IDTYPE=BYID, BTSID=8, BFDSN=0, SRCIP="126.126.126.1",
DSTIP="126.126.126.2", HT=SBFD;
ADD BTSBFD: IDTYPE=BYID, BTSID=8, BFDSN=1, SRCIP="126.126.127.1",
DSTIP="126.126.127.2", HT=SBFD;
SET BTSGTRANSPARA: IDTYPE=BYID, BTSID=8, RoutingBackDelayTime=300;

WCDMA RAN
Table 3-8 Parameters for Ethernet route backup (NodeB, eNodeB, eGBTS, and co-MPT base
station)
MO Sheet in Parameter Group Rem

the arks
Summary
Data File
IPRT IPRoutePat *Route Index/*Cabinet No./*Subrack No./*Slot No./ None

tern Subboard Type/Route Type/*Destination IP/*Mask/
Next Hop IP/Preference/Description Info
Table 3-9 Configuring parameters on the CME (GBTS)

Name ID ble in CME
Batch
Modificati
on
1 BTSIPRT GBTS Route PRI Yes

Priority
Forward NEXTHOP
Route
Address

The following describes activation observation for the NodeB, eNodeB, eGBTS, and co-MPT
base station.
IP route backup can be implemented and verified in a flexible way. For two IP routes with the
same destination but different priorities and next-hop IP addresses, generate a fault in one IP
route. If the other IP route takes over and functions normally, IP route backup is activated. If
the two IP routes are both functional, data is transmitted on the IP route with the higher priority.
Before the verification, check the status of the active and standby IP routes and ensure that both
routes are functional. For this purpose, run the DSP IPRT command to verify that both routes
are in the routing table. The verification procedure is as follows:
Step 1 Check the active route. Run the TRACERT command. In the displayed results, the first hop IP
address is the next hop IP address of the active route.
Step 2 Generate a fault in the active route. Run the DSP IPRT command. The active route is not in the
routing table.

WCDMA RAN
Step 3 Verify the switchover. Run the TRACERT command. The switchover is successful if the first
hop IP address is the next hop IP address of the standby route.
Step 4 Restore the transmission link of the IP route with the higher priority.
----End

Perform the following steps for the NodeB, eNodeB, eGBTS, and co-MPT base station:
Step 1 Run the base station MML command RMV BFDSESSION to disable BFD.
Step 2 Run the base station MML command RMV IPRT to remove the low-priority and high-priority
routes. If the removal fails, perform operations as prompted.
----End
Perform the following steps for the GBTS:
Step 1 Run the base station MML command RMV BTSBFD to disable BFD.
Step 2 Run the base station MML command RMV BTSIPRT to remove the low-priority and high-
priority routes. If the removal fails, perform operations as prompted.
----End

//Deactivating Ethernet route backup for the NodeB, eNodeB, eGBTS, and co-MPT base
station
RMV BFDSESSION: SN=7, BFDSN=0;
RMV BFDSESSION: SN=7, BFDSN=1;
RMV IPRT: RTIDX=0;
RMV IPRT: RTIDX=1;
//Deactivating Ethernet route backup for the GBTS
RMV BTSBFD: IDTYPE=BYID, BTSID=8, BFDSN=0;
RMV BTSBFD: IDTYPE=BYID, BTSID=8, BFDSN=1;
RMV BTSIPRT: IDTYPE=BYID, BTSID=8, RTIDX=0;
RMV BTSIPRT: IDTYPE=BYID, BTSID=8, RTIDX=1;
To perform reconfiguration:
l Run the MOD IPRT command for the NodeB, eNodeB, eGBTS, and co-MPT base station.
l Run the MOD BTSIPRT command for the GBTS.

To perform performance monitoring:
l Run the DSP IPRT command for the NodeB, eNodeB, eGBTS, and co-MPT base station.
l Run the DSP BTSIPRT command for the GBTS.

WCDMA RAN
If ALM-25899 BFD Session Fault is reported, clear the alarm by referring to the alarm handling
suggestions.
3.4 Link Aggregation in Scenario 1
3.4.1 When to Use Link Aggregation in Scenario 1

with the router that supports VRRP.
3.4.2 Planning

Manual active/standby link aggregation is performed on the active and standby boards of the
base station controller. The base station controller is connected to the layer 3 router. The layer
3 router provides the VRRP networking. It is not required that the interconnected devices provide
link aggregation.

The following boards support link aggregation in scenario 1:

3.4.3 Deployment
If the base station controller is directly connected to the layer 3 router, the router must support
VRRP over VLANIF.
If the base station controller is not directly connected to the router, the switch for layer 2 must
be configured and the base station controller is connected to the switch.

Control Item
LOFD/ IP Route IP Route eNodeB per eNodeB

06

WCDMA RAN
Table 3-10 Data to prepare for link aggregation in scenario 1
Trunk group work WORKMODE Set this parameter to Transport

mode ACTIVE_STAND network plan
BY(Active
standby).
Aggregation Mode LACPMODE Set this parameter to Transport

MANUAL_AGGR network plan
EGATION.
Revertive type RT Set this parameter to Transport

NON- network plan
REVERTIVE
(NON-
REVERTIVE).
3.4.3.3 Activation

Step 1 Run the base station controller MML command ADD ETHTRK with Trunk group work
mode set to ACTIVE_STANDBY(Active standby), Aggregation Mode to
MANUAL_AGGREGATION, and Revertive type to NON-REVERTIVE(NON-
REVERTIVE) to add a link aggregation group.
Step 2 Run the base station controller MML command ADD ETHTRKLNK with Trunk group work
mode set to ACTIVE_STANDBY(Active standby) to add a link to the link aggregation group
for the port on the active board.
for the port on the standby board. Note that Port priority of the port on the standby board must
be higher than that of the port on the active board. A larger value indicates a lower priority.
Step 4 Run the base station controller MML command ADD ETHTRKIP to set the IP address of the
link aggregation group.
Step 5 Run the base station controller MML command STR IPCHK to enable BFD between the link
aggregation group and one of the real IP addresses of the VRRP-enabled router. Set Check
type to SBFD, Carry port type to TRUNK, and Whether affect the port swapping to YES
(YES).
Step 6 Run the base station controller MML command STR IPCHK to enable BFD between the link
aggregation group and the other one of the real IP addresses of the VRRP-enabled router. Set
Check type to SBFD, Carry port type to TRUNK, and Whether affect the port swapping
to YES(YES).
----End

WCDMA RAN

//Activating link aggregation in scenario 1
ADD ETHTRK: SRN=2, SN=26, TRKN=2, WORKMODE=ACTIVE_STANDBY, RT=NON-REVERTIVE,
LACPMODE=MANUAL_AGGREGATION;
ADD ETHTRKLNK: SRN=2, SN=26, TRKN=2, TRKLNKSN=26, TRKLNKPN=0,
WORKMODE=ACTIVE_STANDBY, PORTPRI=100;
ADD ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0, IPADDR="126.126.126.1",
MASK="255.255.255.0";
STR IPCHK: SRN=2, SN=26, CHKN=0, CHKTYPE=SBFD, CARRYT=TRUNK,
WORKMODE=ACTIVE_STANDBY, TRUNKN=2, PEERIP="126.126.126.2", WHETHERAFFECTSWAP=YES;
STR IPCHK: SRN=2, SN=26, CHKN=0, CHKTYPE=SBFD, CARRYT=TRUNK,
WORKMODE=ACTIVE_STANDBY, TRUNKN=2, PEERIP="126.126.126.3", WHETHERAFFECTSWAP=YES;

Name ID ble in CME
Batch
Modificati
on
1 ETHTRK Base station Trunk No. TRKN No

controller
Trunk group WORKMO
work mode DE
Aggregation LACPMOD
Mode E
Revertive RT
type
2 ETHTRKL Base station Trunk No. TRKN No

NK controller
Trunk Link TRKLNKSN
Slot No.
Trunk Link TRKLNKP

No. N
Trunk group WORKMO

work mode DE
3 ETHTRKI Base station Trunk No. TRKN No

P controller
IP address IPINDEX
index
Local IP IPADDR
address
Subnet mask MASK

WCDMA RAN

Step 1 Run the base station controller MML command DSP ETHTRK to check whether the link
aggregation group is functional.
Step 2 Run the base station controller MML command DSP ETHTRKLNK to check whether the links
in the link aggregation group are functional.
----End

Step 2 Run the base station controller MML command RMV ETHTRKIP to remove the IP address
of the link aggregation group. If the removal fails, perform operations as prompted.
Step 3 Run the base station controller MML command RMV ETHTRKLNK to remove the ports/links
from the link aggregation group.
Step 4 Run the base station controller MML command RMV ETHTRK to remove the link aggregation
group.
----End

//Deactivating link aggregation in scenario 1
RMV ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0;
RMV ETHTRKLNK: SRN=2, TRKLNKSN=26, TRKLNKPN=1;
RMV ETHTRK: SRN=2, SN=26, TRKN=2;
To perform reconfiguration, run the MOD ETHTRKIP command.

Run the base station controller MML command DSP ETHTRK to check whether the link
Run the base station controller MML command DSP ETHTRKLNK to check whether the links
If ALM-21346 IP Connectivity Check Failure is reported, clear the alarm by referring to the

WCDMA RAN

It is recommended that layer 2 networking be used and the peer layer 2 transmission device
support the link aggregation group.
3.5.2 Planning

Inter-board link aggregation is used on the active and standby boards of the bases station
controller that is connected to the layer 2 transmission device. The port on the active/standby
board is involved in link aggregation in static active/standby mode.

The following boards support link aggregation in scenario 2:

3.5.3 Deployment
The base station controller is directly connected to the layer 2 transmission device. The layer 2
transmission device supports link aggregation.
Trunk group work WORKMODE Set this parameter to Transport network

mode ACTIVE_STANDB plan (negotiation
Y(Active standby). required)
Aggregation Mode LACPMODE Set this parameter to Transport network

STATIC_LACP. plan (negotiation
required)
Revertive type RT Set this parameter to Transport network

NON-REVERTIVE plan (negotiation
(NON- required)
REVERTIVE).

WCDMA RAN
Trunk system SYSPRI Set this parameter to Transport network

priority be lower than the plan (negotiation
priority of the peer required)
device.
Note that a larger value
indicates a lower
priority.
3.5.3.3 Activation

Step 1 Run the base station controller MML command ADD ETHTRK with Trunk group work
mode set to ACTIVE_STANDBY(Active standby), Aggregation Mode to
STATIC_LACP, Revertive type to NON-REVERTIVE(NON-REVERTIVE), and Trunk
system priority to a value larger than the priority of the peer deviceto add a link aggregation
group.
for the port on the active board.
for the port on the standby board. Note that Port priority of the port on the standby board must
be higher than that of the port on the active board. A larger value indicates a lower priority.
Step 4 Run the base station controller MML command ADD ETHTRKIP to set the IP address of the
link aggregation group.
----End

ADD ETHTRK: SRN=2, SN=26, TRKN=2, WORKMODE=ACTIVE_STANDBY, SYSPRI=100, RT=NON-
REVERTIVE, LACPMODE=STATIC_LACP;
ADD ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0, IPADDR="126.126.126.1",
MASK="255.255.255.0";

WCDMA RAN

Name ID ble in CME
Batch
Modificati
on
1 ETHTRK Base station Trunk No. TRKN No

controller
Trunk group WORKMO
work mode DE
Aggregation LACPMOD
Mode E
Revertive RT
type
2 ETHTRKL Base station Trunk No. TRKN No

NK controller
Trunk Link TRKLNKSN
Slot No.
Trunk Link TRKLNKP

No. N
Trunk group WORKMO

work mode DE
Port priority PORTPRI
3 ETHTRKI Base station Trunk No. TRKN No

P controller
IP address IPINDEX
index
Local IP IPADDR
address
Subnet mask MASK

Step 1 Run the base station controller MML command DSP ETHTRK to check whether the link
Step 2 Run the base station controller MML command DSP ETHTRKLNK to check whether the links

WCDMA RAN
----End

Step 1 Run the base station controller MML command RMV ETHTRKIP to remove the IP address
of the link aggregation group. If the removal fails, perform operations as prompted.
Step 2 Run the base station controller MML command RMV ETHTRKLNK to remove the ports/links
from the link aggregation group.
Step 3 Run the base station controller MML command RMV ETHTRK to remove the link aggregation
group.
----End

RMV ETHTRKIP: SRN=2, SN=26, TRKN=2, IPINDEX=0;
RMV ETHTRK: SRN=2, SN=26, TRKN=2;
To perform reconfiguration, run the MOD ETHTRKIP command.

Run the base station controller MML command DSP ETHTRK to check whether the link
Run the base station controller MML command DSP ETHTRKLNK to check whether the links
If ALM-21349 Ethernet Trunk Group Fault and ALM-21350 Ethernet Trunk Link Fault are
reported, clear them by referring to the alarm handling suggestions.

The base station has multiple FE or GE ports, and these ports are either electrical or optical.
Layer 2 or layer 3 networking can be used. The peer layer 2 or layer 3 transmission device
supports link aggregation.

WCDMA RAN
The ports on the base station board involve in link aggregation in static load sharing mode.
3.6.2 Planning

None

The UMPT/WMPT/LMPT and UTRP/UTRPc boards of the 3900 series base stations support
link aggregation in scenario 3.
3.6.3 Deployment
The base station is directly connected to the layer 2 or layer 3 transmission device. The layer 2
or layer 3 transmission device supports link aggregation.

Control Item
LOFD/ Ethernet Link Ethernet Link eNodeB per eNodeB

TDLOFD-0030 Aggregation Aggregation
08
Trunk Type LACP Set this parameter to Transport

ENABLE(Enable network plan
LACP). (negotiation
required)
3.6.3.3 Activation

Step 1 Run the base station MML command ADD ETHTRK to add a link aggregation group.

WCDMA RAN
Step 2 Run the base station MML command ADD ETHTRKLNK with Master Flag set to YES(Yes)
to add a primary port to the link aggregation group.
Step 3 Run the base station MML command ADD ETHTRKLNK with Master Flag set to NO(No)
to add another port to the link aggregation group. Repeat the command until all required ports
are added.
Step 4 Run the base station MML command ADD DEVIP with Port Type set to ETHTRK(Ethernet
Trunk) and Port No. to the value of Trunk No..
----End

ADD ETHTRK: SN=5, SBT=ETH_COVERBOARD, TN=0, LACP=ENABLE;
ADD ETHTRKLNK: SN=5, SBT=ETH_COVERBOARD, TN=0, PN=0, FLAG=YES;
ADD ETHTRKLNK: SN=5, SBT=ETH_COVERBOARD, TN=0, PN=1, FLAG=NO;
ADD DEVIP: SN=5, SBT=ETH_COVERBOARD, PT=ETHTRK, PN=0, IP="126.126.126.1",
MASK="255.255.255.0";
Table 3-15 Parameters for link aggregation in scenario 3
MO Sheet in the Parameter Group Remarks

Summary Data
File
ETHTRK User-defined sheet Cabinet No./Subrack None

Ethernet Trunk No./Slot No./
patten is Subboard Type/
recommended. Trunk No./ Trunk
Type/Max
Transmission Unit
(byte)/ ARP Proxy
ETHTRKLNK User-defined sheet Cabinet No./Subrack None

Ethernet Trunk No./ Slot No./ Trunk
Member patten is No./ Ethernet Port
recommended. No./ Port Priority/
Master Flag

Step 1 Run the DSP ETHTRK command to query the status of one Ethernet trunk. If Ethernet Trunk
Status is Up and Number of Active Trunk Ports is not 0, the Ethernet link aggregation function
is normal and there are active ports in the trunk.
Step 2 Remove the optical fiber or Ethernet cable from one active port, and run the DSP ETHTRK
command again. The number of this port is not displayed in the result and the S1 interface is
functional. Run the DSP ETHTRKLNK command to query the status of this port. Port
Status is Down.

WCDMA RAN
Step 3 Reconnect the optical fiber or Ethernet cable to the port.
Step 4 Run the DSP ETHTRK and DSP ETHTRKLNK commands. The port to which the optical
fiber or Ethernet cable is reconnected becomes active again.
----End

Step 1 Run the base station MML command RMV DEVIP to remove the device IP address.
Step 2 Run the base station MML command RMV ETHTRKLNK to remove the ports from the link
aggregation group. The primary port must be removed last.
Step 3 Run the base station MML command RMV ETHTRK to remove the link aggregation group.
----End

RMV DEVIP: SN=5, SBT=ETH_COVERBOARD, PT=ETHTRK, PN=0, IP="126.126.126.1";
RMV ETHTRKLNK: SN=5, SBT=ETH_COVERBOARD, TN=0, PN=1;
RMV ETHTRKLNK: SN=5, SBT=ETH_COVERBOARD, TN=0, PN=0;
RMV ETHTRK: SN=5, SBT=ETH_COVERBOARD, TN=0;
If a port has different attributes from other ports, you need to remove the port from the link
aggregation group.

Run the base station MML command DSP ETHTRK to check whether the link aggregation
group is functional.
Run the base station MML command DSP ETHTRKLNK to check whether the links in the
link aggregation group are functional.
If ALM-25895 Ethernet Trunk Group Fault and ALM-25887 Ethernet Trunk Link Fault are
reported, clear them by referring to the alarm handling suggestions.
3.7 OM Channel Backup
3.7.1 When to Use OM Channel Backup

Only the eNodeB, eGBTS, and co-MPT base station support OM channel backup.

WCDMA RAN
OM channel backup applies when hybrid transmission is used on the base station for high-QoS
and low-QoS links, secure and non-secure links, and multi-RAT services of a co-MPT
multimode base station.
3.7.2 Planning

Two IP addresses for the two OM channels must be planned on the base station side for different
transmission links.

The UMPT/LMPT and UTRP boards of the 3900 series base stations support OM channel
backup.
3.7.3 Deployment
The U2000 must be configured with the IP addresses of the master and slave OM channels and
the bound routes.

Control Item
LOFD/ OM Channel OM Channel eNodeB per eNodeB

05
Table 3-16 Data to prepare for OM channel backup
Standby Status FLAG Set this parameter to Network plan

MASTER(Master)
for the master OM
channel and to
SLAVE(Slave) for the
slave OM channel.

WCDMA RAN
Local IP IP Set this parameter to Network plan

the IP address of the
master/slave OM
channel.
Local Mask MASK N/A Network plan
Peer IP PEERIP Set this parameter to Network plan

the IP address of the
U2000.
Peer Mask PEERMASK N/A Network plan
Binding Route BRT Set this parameter to Network plan

YES(Yes).
Route Index RTIDX Set this parameter to Network plan

the index of the route
bound to the master
OM channel.
Binding Secondary BINDSECONDARY Set this parameter to Network plan

Route RT YES(Yes) when the
U2000 uses the remote
HA system and the IP
address of the standby
U2000 is not within
the network segment
range of the route
bound to the OM
channel. Otherwise,
set this parameter to
NO(No).
Secondary Route SECONDARYRTID This parameter is valid Network plan

Index X only if Binding
Secondary Route is
set to YES(Yes). Set
this parameter to the
index of the route to
the standby U2000.
3.7.3.3 Activation
Step 1 Run the base station MML command ADD OMCH with Standby Status set to MASTER
(Master), Local IP to the IP address of the master OM channel, Binding Route to YES(Yes),
and Route Index to the index of the route bound to the master OM channel.

WCDMA RAN
You must set Binding Secondary Route when the U2000 uses the remote HA system and the
IP address of the standby U2000 is not within the network segment range of the route bound to
the master OM channel. In this case, set Binding Secondary Route to YES(Yes) and Secondary
Route Index to the index of the route from the master OM channel to the standby U2000.
Step 2 Run the base station MML command ADD OMCH with Standby Status set to SLAVE
(Slave), Local IP to the IP address of the slave OM channel, Binding Route to YES(Yes), and
Route Index to the index of the route bound to the slave OM channel.
You must set Binding Secondary Route when the U2000 uses the remote HA system and the
IP address of the standby U2000 is not within the network segment range of the route bound to
the slave OM channel. In this case, set Binding Secondary Route to YES(Yes) and Secondary
Route Index to the index of the route from the slave OM channel to the standby U2000.
----End

//Activating OM channel backup when the U2000 does not use the remote HA system
DSTMASK="255.255.255.0", RTTYPE=NEXTHOP, NEXTHOP="126.126.126.2";
ADD OMCH: FLAG=MASTER,IP="10.10.10.1", MASK="255.255.255.255",
PEERIP="100.100.100.1", PEERMASK="255.255.255.0", BEAR=IPV4, BRT=YES, RTIDX=0,
BINDSECONDARYRT=NO, CHECKTYPE=NONE;
ADD OMCH: FLAG=SLAVE, IP="10.10.11.1", MASK="255.255.255.255",
BINDSECONDARYRT=NO, CHECKTYPE=NONE;
//Activating OM channel backup when the U2000 uses the remote HA system
ADD OMCH: FLAG=MASTER, IP="10.10.10.1", MASK="255.255.255.255",
BINDSECONDARYRT=YES, SECONDARYRTIDX=2, CHECKTYPE=NONE;
ADD OMCH: FLAG=SLAVE, IP="10.10.11.1", MASK="255.255.255.255",
BINDSECONDARYRT=YES, SECONDARYRTIDX=3, CHECKTYPE=NONE;

WCDMA RAN
Table 3-17 Parameters for OM channel backup

Summary Data
File
OMCH OMCHPattern Mask / Peer IP / Peer None

Mask / Bearer Type/
Cabinet No./Subrack
No./Slot No./
Subboard Type/
Binding Route/
Destination IP/
Destination Mask/
Route Type/Interface
Type/
PreferenceRoute-
Route Index/Binding
Secondary Route/
Secondary Route
Index/Check Type/
UDP Session ID

Descriptions in this section are based on two assumptions:
l The local IP addresses of the master and slave OM channels belong to different network
segments.
l The next-hop IP addresses of the IP routes bound to the master and slave OM channels are
different.
Perform the verification based on the actual networking mode if the actual networking mode is
different from the assumptions. Ensure that the standby OM channel status is normal and a
switchover can be triggered if the active OM channel is faulty.
The activation observation procedure is as follows:
Step 1 Check which channel is the active OM channel.
Run the DSP OMCH command to query the status of the master and slave OM channels. An
OM channel is active if its OM Channel Status is Normal and Used State is In Use.
Step 2 Trigger an OM channel switchover.
Generate a transport link fault for the active OM channel and verify that the standby OM channel
can take over.
l If the active OM channel is the master channel, generate a route fault for the master OM
channel. Wait about 10 minutes and run the DSP OMCH command to check the status of

WCDMA RAN
the slave OM channel. The switchover is successful if OM Channel Status is Normal and
Used State is In Use.
l If the active OM channel is the slave channel, generate a route fault for the slave OM channel.
Wait about 10 minutes and run the DSP OMCH command to check the status of the master
OM channel. The switchover is successful if OM Channel Status is Normal and Used
State is In Use.
Step 3 Restore the faulty OM channel.
----End

Run the base station MML command RMV OMCH with Standby Status set to SLAVE(Slave)
to remove the slave OM channel. If the removal fails, perform operations as prompted.

//Removing the slave OM channel
RMV OMCH: FLAG=SLAVE;
To perform reconfiguration, run the MOD OMCH command.

Run the DSP OMCH command to query the status of the master and slave OM channels.
If ALM-25901 Remote Maintenance Link Failure is reported, clear the alarm by referring to the

WCDMA RAN 4 Engineering Guidelines for Transmission Maintenance and
IP RAN Engineering Guide Feature Parameter Description Detection
4 Engineering Guidelines for Transmission

Maintenance and Detection
4.1 BFD
4.1.1 When to Use BFD

It is recommended that BFD be activated only for quickly locating a fault because BFD affects
CPU performance and occupies transmission bandwidth when IP transmission is used.
4.1.2 Planning

N/A

l The FG2a/FG2c and GOUa/GOUc of the BSC6900 support BFD.
l The FG2c, GOUc, and EXOUa of the BSC6910 support BFD.
l The WMPT, SMPT, LMPT, and UMPT of the BTS3900 support BFD.
4.1.3 Deployment
l NEs
The connected device supports BFD.
l Operating environment
Ethernet ports are available on the LMPT or UMPT on the eNodeB.
l License


Name Control Item
LOFD-003007 Bidirectional Bidirectional eNodeB per eNodeB

Forwarding Forwarding
Detection Detection
TDLOFD-003 Bidirectional Bidirectional eNodeB per eNodeB

007 Forwarding Forwarding
Detection Detection

Table 4-1, Table 4-2, and Table 4-3 list the data to prepare before activating BFD.
Table 4-1 Data to prepare before activating BFD (RNC side)
Bfd Protocol Switch SWITCH N/A Transport network

plan
Check type CHKTYPE N/A Transport network

plan
Carry port type CARRYT N/A Transport network

plan

Check mode MODE When Check type is Transport network

set to SBFD and plan
Carry port type is
set to ETHPORT,
set this parameter to
CHECK_ON_IND
EPENDENT_POR
T or
CHECK_ON_PRI
MARY_PORT.
When Check type is
set to SBFD and
Carry port type is
set to TRUNK, you
do not need to set this
parameter but need to
enter the IP address
to be checked.
When Check type is
set to MBFD, you do
not need to set this
parameter but need to
enter the IP address
to be checked.
Multi hop BFD MBFDLOCALIP N/A Transport network

detect local ip plan
My discriminator of MYDISCRIMINAT N/A Transport network

BFD OR plan
Min interval of BFD MINTXINT N/A Transport network

packet send [ms] plan
Min interval of BFD MINRXINT N/A Transport network

packet receive [ms] plan
Detect multiplier of BFDDETECTCOU N/A Transport network

BFD packet NT plan
Route associated flag ROUTEASSOCIAT This parameter is Transport network

EDFLAG valid only when plan
Check type is set to
SBFD.
Differentiated DSCP N/A Transport network

services code point plan

Table 4-2 Data to prepare before activating BFD (GBTS side)
Hop Type HT l SBFD sessions Transport network

are used for point- plan
to-point
continuity checks
in layer 2
networking
scenarios.
l MBFD sessions
are used for end-
to-end continuity
checks in layer 3
networking
scenarios.
Source IP Address SRCIP N/A Transport network

plan
Destination IP DSTIP N/A Transport network

Address plan
Time for Waiting to BTSWTR 3S Transport network

Restore plan
Minimum TX MINTXINTERVAL 100 ms Transport network

Interval plan
Minimum RX MINRXINTERVAL 100 ms Transport network

Interval plan
Detect Period DETECTMULT 3 Transport network

plan
DSCP DSCP N/A Transport network

plan
Table 4-3 Data to prepare before activating BFD (eGBTS/NodeB/eNodeB side)
Parameter Name Parameter ID Setting Notes Data

Source
Hop Type HT l SBFD sessions are used for Transport

point-to-point continuity network
checks in layer 2 plan
networking scenarios.
l MBFD sessions are used for
end-to-end continuity
checks in layer 3
networking scenarios.


Source
Source IP SRCIP This parameter specifies the Transport

source IP address of the BFD network
session. Set this parameter plan
based on the network plan.
A BFD session cannot be
configured as a single-hop
session if its source IP address
is a logical IP address.
Ensure that the source IP
address has been configured in
the associated DEVIP MO.
This parameter must be a valid
IP address and cannot be set to
0.0.0.0. It must be a device IP
address of a specified board
(for example, the IP address of
an Ethernet port) or a logical IP
address (for example, the IP
address of a loopback
interface), but cannot be the IP
address of an OM channel.
This parameter must be set to a
different value from that of the
BFDSESSION.DSTIP
parameter.


Source
Destination IP DSTIP This parameter specifies the

destination IP address of the
BFD session. Set this
parameter based on the
network plan.
If the hop type is single-hop
and the source IP port is an
Ethernet port in the BFD
session to be added, the source
and destination IP addresses
must be on the same network
segment. If a single-hop
reliability BFD session is
inactive, the route with the
next-hop IP address set to the
same value as the destination IP
address of the BFD session is
disabled. If a BFD session is
active, the route with the next-
hop IP address set to the same
value as the destination IP
address of the BFD session is
enabled.
The destination IP address of
each BFD session must be
unique.
Min TX Interval MINTI 100 ms Transport

network
plan
Min RX Interval MINRI 100 ms Transport

network
plan
Detection Multiplier DM 3 Transport

network
plan


Source
Session Catalog CATLOG Set this parameter based on the Transport

network plan. network
l If this parameter is set to plan
MAINTENANCE
(Maintenance), this BFD
session is used only for
continuity checks.
l If this parameter is set to
RELIABILITY
(Reliability), the BFD
session is used to trigger
route interlock. When a
route is faulty, a standby
route takes over to prevent
link interruption caused by
the route failure.
Protocol Version VER This parameter specifies the Transport

protocol version of the BFD network
session. Set this parameter as plan
the BFD session protocol
version supported by the peer
device.
DSCP DSCP N/A Transport

network
plan
BFD sessions are classified into SBFD sessions and MBFD sessions by hop type. BFD sessions
are also classified into maintainability BFD sessions and reliability BFD sessions by session
type.
4.1.3.3 Precautions
Currently, the RNC only supports SBFD on the active port and in asynchronous mode. It does
not support simultaneous SBFD on the active and standby ports.
If an SBFD session is shut down when it is running, the base station or base station controller
automatically disables the routes whose next-hop IP address is the peer IP address of the failed
SBFD session.
If SBFD is configured to be applicable only to the active port on the base station controller side
and the Whether affect the port swapping (IPCHK.WHETHERAFFECTSWAP) parameter
is set to YES(YES), an SBFD link fault triggers a port switchover. Otherwise, an SBFD link
fault does not trigger a port switchover, but the availability of the related routes is affected.

4.1.3.4 Activation

NOTE
The correct IP path has been configured based on the network plane. For the BSC6910 which does not
support the configuration of IP paths, the BFD cannot be bound with an IP path or IP route.
l Base station controller side
Step 1 Run the MML command SET BFDPROTOSW with Bfd Protocol Switch set to BFD_ON to
activate BFD.
Step 2 Run the MML command STR IPCHK with Check type set to SBFD or MBFD to start the
continuity check.
Step 3 (Optional) Run the MML command ADD IPPATHBIND with IP path ID set to the ID of the
IP path to be checked for binding the BFD with the IP path.
Step 4 (Optional) Run the MML command ADD IPRTBIND with Destination IP address and
Forward route address set to the destination IP address and next hop IP address to be check,
respectively. This is for binding the BFD with the IP route.
----End
l eGBTS/NodeB/eNodeB side
Run the MML command ADD BFDSESSION with Hop Type and Session Catalog set to
SINGLE_HOP and RELIABILITY, respectively.
l GBTS side
Run the BSC MML command ADD BTSBFD and set the related parameters.

//Activating the BFD feature
(Optional) SET BFDPROTOSW: SRN=0, SN=26, SWITCH=BFD_ON;
STR IPCHK: SRN=5, SN=26, CHKTYPE=SBFD, CARRYT=ETHPORT, PN=0,
MODE=CHECK_ON_PRIMARY_PORT, PEERIP="99.9.9.100", WHETHERAFFECTSWAP=NO,
MINTXINT=50, MINRXINT=50, BFDDETECTCOUNT=5;
(Optional) ADD IPPATHBIND: ANI=0, PATHID=0, SRN=0, SN=24, CHKN=1;
(Optional) ADD IPRTBIND: SRN=0, SN=26, DESTIP="10.10.10.1",
MASK="255.255.255.255", NEXTHOP="5.5.5.5", MBFDCHKN=0;
//Adding a BFD session
ADD BFDSESSION: CN=0, SRN=0, SN=6, BFDSN=0, SRCIP="192.168.5.5",
DSTIP="192.168.5.6", HT=SINGLE_HOP, MINTI=100, MINRI=100, DM=3,
CATLOG=RELIABILITY, DSCP=0, VER=DRAFT4;

You need to customize a summary data file based on the default one. Table 10-4 lists the related
parameters.
Batch reconfiguration using the CME is the recommended method to activate a feature on
existing base stations. This method reconfigures all data, except neighbor relationships, for
multiple base stations in a single procedure. The procedure is as follows:

Step 1 After creating a planned data area, choose CME > Advanced > Customize Summary Data
File (U2000 client mode), or choose Advanced > Customize Summary Data File (CME client
mode), to customize a summary data file for batch reconfiguration.
NOTE
For context-sensitive help on a current task in the client, press F1.
The following steps take operations for the eNodeB as an example:
Step 2 Choose CME > LTE Application > Export Data > Export Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Export Data > Export Base Station
Bulk Configuration Data (CME client mode), to export the base station data stored on the CME
into the customized summary data file.
Step 3 In the summary data file, set the parameters in the MOs listed in Table 10-4 and close the file.
Step 4 Choose CME > LTE Application > Import Data > Import Base Station Bulk Configuration
Data (U2000 client mode), or choose LTE Application > Import Data > Import Base Station
Bulk Configuration Data (CME client mode), to import the summary data file into the CME,
and then start the data verification.
Step 5 After data verification is complete, choose CME > Planned Area > Export Incremental
Scripts (U2000 client mode), or choose Area Management > Planned Area > Export
Incremental Scripts (CME client mode), to export and activate the incremental scripts.
----End
On the CME, set the parameters listed in the "Data Preparation" section for a single base station.
The procedure is as follows:
Step 1 In the planned data area, click Base Station in the upper left corner of the configuration window.
Step 2 In area 1 shown in Figure 4-1, select the base station to which the MOs belong.

Figure 4-1 MO search and configuration window
NOTE
To view descriptions of the parameters in the MO, click in area 4 and press F1.
Area 5 displays the details of a selected area-4 entry in vertical format. Click the Details icon to show or
hide this area.
Step 3 On the Search tab page in area 2, enter an MO name, for example, CELL.
Step 4 In area 3, double-click the MO in the Object Name column. All parameters in this MO are
displayed in area 4.
Step 5 Set the parameters in area 4 or 5.
Step 6 Choose CME > Planned Area > Export Incremental Scripts (U2000 client mode), or choose
Area Management > Planned Area > Export Incremental Scripts (CME client mode), to
export and activate the incremental scripts.
----End
l In IPsec-disabled scenarios, the IP over FE Summary template summary data file is

recommended.
l In IPsec-enabled scenarios, the IP over FE Summary template in Security Scenario
summary data file is recommended.
SBFD and MBFD use the same summary data file but different parameter values.

Table 4-4 Parameters for BFD

Summary Data
File
BFDSESSION eNodeB transport Cabinet No./ None

Maintenance patten Subrack No./ Slot
No./Session ID /
VRF Index/ Source
IP / Destination IP /
Hop Type / Session
Catalog / DSCP /
Protocol Version

BFD sessions are classified into maintainability BFD sessions and reliability BFD sessions by
session type. BFD sessions are also classified into SBFD sessions and MBFD sessions by hop
type. The method of verifying SBFD is the same as that of verifying MBFD.
The verification procedure is as follows:
Step 1 Enable BFD-based IP fault detection. If BFD fails, ALM-21346 IP Connectivity Check Failure
is reported.
Step 2 Run the RNC MML command DSP IPCHK to query gateway check parameter and status.
Step 3 Run the NodeB MML command DSP BFDSESSION to query the status of a BFD session.
----End
Run the DSP BFDSESSION command. If Session State is Up, the feature is activated.

Base station controller side:
Step 1 Run the RNC MML command STP IPCHK to stop the continuity check of the gateway on FE/
GE ports.
----End
Base station side:
Step 1 Run the NodeB MML command RMV BFDSESSION to remove a BFD session.
----End

//Stopping a continuity check

//Removing a BFD session

RMV BFDSESSION: CN=0, SRN=0, SN=0, BFDSN=0;

Base station controller side:
Step 1 Run the MML command DSP IPCHK to query gateway check parameter and status.
----End
Base station side:
Step 2 Run the MML command DSP BFDSESSION to query the status of a BFD session.
----End

l Base station controller side
Modify the following parameters by running the STR IPCHK command as required:
MINTXINT, MINRXINT, and BFDDETECTCOUNT.
If the BFD packets are sent too frequently and occupy too large bandwidth, the
performance of the connected equipment will be affected. In this case, you are advised
to increase the value of the MINTXINT parameter after discussion with the customer.
If the frequency of sending BFD packets is too low, the detection accuracy will be low.
In this case, you are advised to decrease the value of the MINTXINT parameter after
discussion with the customer.
If the fault detection on the receiving end is too sensitive, there will be ping-pong effect.
In this case, you are advised to increase the values of the MINRXINT and
BFDDETECTCOUNT parameters after discussion with the customer.
If the fault detection on the receiving end is not sensitive, it will take too much time to
detect the fault. In this case, you are advised to decrease the values of the
MINRXINT and BFDDETECTCOUNT parameters after discussion with the
customer.
l Base station side:
Modify the following parameters by running the MOD BFDSESSION command as
required: MINTI, MINRI, and DM.
If the BFD packets are sent too frequently and occupy too large bandwidth, the
performance of the connected equipment will be affected. In this case, increase the value
of the MINTI parameter.
If the frequency of sending BFD packets is too low, the detection accuracy will be low.
In this case, you are advised to decrease the value of the MINTI parameter after
discussion with the customer.
If the fault detection on the receiving end is too sensitive, there will be ping-pong effect.
In this case, you are advised to increase the values of the MINRI and DM parameters
after discussion with the customer.
If the fault detection on the receiving end is not sensitive, it will take too much time to
detect the fault. In this case, you are advised to decrease the values of the MINRI and
DM parameters after discussion with the customer.

The ALM-21346 IP Connectivity Check Failure is reported if the BFD fails.
Table 4-5 Alarm related to BFD sessions
Alarm ID Alarm Name NE Feature ID Feature Name
ALM-21346 IP Connectivity RNC WRFD-050409 IP Transmission

Check Failure WRFD-050403 Introduction on
Iu Interface
WRFD-050410
IP Transmission
Introduction on
Iub Interface
IP Transmission
Introduction on
Iur Interface
If a BFD session is faulty, check whether an alarm listed in Table 4-6 is generated on the eNodeB.
If an alarm is generated, clear the alarm by referring to the related alarm reference.
Table 4-6 Alarm related to BFD sessions
Alarm ID Alarm Name Severity
25899 BFD Session Fault Minor
4.2 GTP-U Echo

The eNodeB and RNC support GTP-U echo.
4.2.1 When to Use GTP-U Echo

Enable GTP-U echo if the eNodeB/RNC needs to check the timer length and number of timeouts
for detecting a discontinuity or failure in the GTP-U path.
4.2.2 Deployment
GTP-U echo monitoring has no requirement for the operating environment, transport
networking, and licenses.

Data Preparation on the RNC Side

The following table describes the parameters that must be set by running the SET UGTPU
command to configure the timer length and number of timeouts for detecting a discontinuity or
failure in the GTP-U path.
Para Param Data Setting Notes

meter eter ID Source
Name
Path GTPU Networ This parameter specifies the maximum time interval between
Timeo PATH k plan sending of path detection message at the local end and
ut TIME (negoti reception of a response message from the peer end. If no
Thresh OUTT ation response is received after the delay threshold is exceeded, the
old HD not local end regards that the path detection fails or another path
require detection message needs to be transmitted.
d)
Maxi GTPU Networ This parameter specifies the maximum number of times the
mum PATH k plan path detection message is retransmitted when no response to
Path TIME (negoti the path detection message is received. If the number of times
Timeo OUTM ation the path detection message is retransmitted exceeds the
uts AXNU not maximum value, the path detection fails.
M require
d)
Echo EchoS Networ Set this parameter based on the network plan. You are advised
Detect witch k plan to set this parameter to ON to enable GTP-U echo.
ion (negoti
Switch ation
not
require
d)
Data Preparation on the eNodeB Side

The following table describes the parameters that must be set in a GTPU MO to configure the
timer length and number of timeouts for detecting a discontinuity or failure in the GTP-U path.

Para Param Data Setting Notes

meter eter ID Source
Name
ECHO GTPU. Networ Set this parameter based on the network plan. If no echo
Frame TIME k plan response is received during the period specified by this
Timeo OUTT (negoti parameter, echo response times out.
ut H ation
not
require
d)
ECHO GTPU. Networ Set this parameter based on the network plan. This parameter
Frame TIME k plan specifies the maximum number of echo response timeouts. If
Timeo OUTC (negoti the number of times no echo response is received reaches the
ut NT ation value specified by this parameter, the GTP-U path fails.
Count not
require
d)
DSCP GTPU. Networ Set this parameter based on the network plan.
DSCP k plan
(negoti
ation
not
require
d)
Static GTPU. Networ Set this parameter based on the network plan. The value
Check STATI k plan ENABLE(Enable) is recommended.
Switch CCHK (negoti
ation
not
require
d)
4.2.2.3 Activation

RNC side:
Step 1 Run the MML command SET GTPU with Echo Detection Switch set to ON.
----End
eNodeB side:
Step 1 Run the MML command MOD GTPU with Static Check Switch set to ENABLE(Enable).
----End


//Enabling GTP-U echo on the RNC
SET UGTPU: EchoSwitch=ON;
//Enabling GTP-U echo on the eNodeB
MOD GTPU: STATICCHK=ENABLE;

Table 4-7 lists the parameters for GTP-U echo monitoring on the eNodeB side.
Table 4-7 Parameters for GTP-U echo monitoring

Summary Data
File
GTPU eNodeB transport Echo Frame Timeout None

Maintenance patten (ms) / Echo Frame
Timeout Count /
DSCP / Static Check
Switch
Activation Observation on the RNC Side

N/A
Activation Observation on the eNodeB Side

For more information about how to start GTP-U echo monitoring on the U2000, see the U2000
online help.
The activation observation procedure is as follows:
Step 1 Before starting GTP-U echo monitoring, check the following items.
If... Then...
GTP-U static detection is Ensure that the cell is activated.

enabled in the initial data
configuration
GTP-U static detection is Ensure that bearers are set up for UEs in the cell. This can
disabled in the initial data be achieved by using UEs to access the cell and injecting
configuration packets to the uplink or downlink of the UEs.
The eNodeB can send GTP-U echo control messages in one of the preceding scenarios.
Step 2 Log in to the U2000.

To see the U2000 online help, press F1 in the U2000 window.
Step 3 Create a GTP-U echo monitoring task and set associated parameters.
l For details about how to create a GTP-U echo monitoring task, choose Fault
Management > FARS > LTE Trace/Monitoring > Creating LTE Trace/Monitoring
Tasks in the TOC pane.
l For details about how to set parameters for a GTP-U echo monitoring task, choose Fault
Management > FARS > LTE Trace/Monitoring > References for LTE Trace
Interfaces > Parameters for Creating an LTE Trace/Monitoring Task.
Step 4 Run the monitoring task, and check the results. GTP-U echo monitoring is successfully activated
if echo request and response messages can be viewed in real time, as shown in Figure 4-2.
Figure 4-2 GTP-U echo monitoring result example
----End

RNC side:
Step 1 Run the MML command SET UGTPU with Echo Detection Switch set to OFF.
----End
eNodeB side:
Step 1 Run the MML command MOD GTPU with Static Check Switch set to DISABLE(Disable).
----End

//Disabling GTP-U echo on the RNC
SET UGTPU: EchoSwitch=OFF;
//Disabling GTP-U echo on the eNodeB
MOD GTPU: STATICCHK=DISABLE;

N/A


None
None

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 5 Parameters
5 Parameters
There are no specific parameters associated with this feature.

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 6 Counters
6 Counters
There are no specific counters associated with this feature.

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 7 Glossary
7 Glossary
For the acronyms, abbreviations, terms, and definitions, see Glossary.

WCDMA RAN
IP RAN Engineering Guide Feature Parameter Description 8 Reference Documents
8 Reference Documents
1. License Management Feature Parameter Description

2. Transmission Resource Pool in RNC Feature Parameter Description
3. BSC6900 UMTS Initial Configuration Guide (MML-Based)
4. BSC6900 UMTS Initial Configuration (CME-based)
5. 3900 Series Base Station Initial Configuration Guide
6. BTS3902E&BTS3803E WCDMA Initial Configuration Guide
7. RAN Reconfiguration Guide
8. BSC6900 UMTS Alarm Reference


IP RAN Engineering Guide (RAN16.0 - Draft A) PDF

Загружено:

Сведения о документе

Оригинальное название

Авторское право

Доступные форматы

Поделиться этим документом

Поделиться или встроить документ

Параметры публикации

Этот документ был вам полезен?

Это неприемлемый материал?

Авторское право:

Доступные форматы

IP RAN Engineering Guide (RAN16.0 - Draft A) PDF

Загружено:

Авторское право:

Доступные форматы

WCDMA RAN

IP RAN Engineering Guide Feature

HUAWEI TECHNOLOGIES CO., LTD.

Trademarks and Permissions

Huawei Technologies Co., Ltd.

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential i

1 About This Document..................................................................................................................1

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential ii

3 Engineering Guidelines for Transmission Reliability........................................................19

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential iii

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential iv

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential v

4 Engineering Guidelines for Transmission Maintenance and Detection..........................47

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential vi

4.1.3.2 Data Preparation.....................................................................................................................................................48

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential vii

1 About This Document

This document covers the following features:

l WRFD-050402 IP Transmission Introduction on Iub Interface

1.2 Intended Audience

l Need to understand the features described herein

1.3 Change History

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 1

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 2

2.1 WRFD-050402 IP Transmission Introduction on Iub

2.1.1 When to Use

2.1.2 Required Information

2.1.3.1 Network Planning

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 3

2.1.3.2 Hardware Planning

Figure 2-1 Deployment of IP Transmission Introduction on Iub Interface (RNC)

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 4

Figure 2-2 Deployment of IP Transmission Introduction on Iub Interface (NodeB)

Interfac Unidirectional Delay Jitter (ms) Packet Loss Rate (10-x)

Maximum Target Maximum Targe Maximum Targe

Iub 40 10 15 2 10-3 10-4

Iu-CS 15 10 7 7 10-3 10-4

Iu-PS 15 10 7 7 10-3 10-6

Iur 15 10 7 7 10-3 10-4

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 5

Feature ID Feature Name License Control NE Sales Unit

WRFD-05040 IP Transmission IP Transportation in RNC Erl+Mbps

2.1.4.3 Data Preparation

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 6

MML Command Examples

2.1.4.5 Activation Observation

Step 4 Use UE 1 to call UE 2. Use UE 2 to answer and start a conversation with UE 1.

Expected result: The conversation is normal and the voice is clear.

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 7

Counter Counter Name Counter Description

67191612 VS.SCTP.RX.PKGNUM Number of IP Packets Received on the

67191613 VS.SCTP.TX.PKGNUM Number of IP Packets Transmitted on

67195399 VS.IPPATH.IPLAYER.RXPACK- Number of Packets Received at the IP

67195395 VS.IPPATH.IPLAYER.TXPACK- Number of Packets Transmitted at the

l On the NodeB side

Counter ID Counter Name Counter Description

1542455874 VS.IPPath.TxPkts Number of Packets Successfully Transmitted on the

1542455877 VS.IPPath.RxPkts Number of Packets Successfully Received on the IP

1542455424 VS.Sctp.RxPkts Number of IP Packets Successfully Received on the

1542455425 VS.Sctp.TxPkts Number of IP Packets Successfully Transmitted on

Issue Draft A (2014-01-20) Huawei Proprietary and Confidential 8

2.1.5 Performance Monitoring

2.1.6 Parameter Optimization