Contents

 Infrastructure aspects

 Protocol Stack

 Iub over IP migration

 Defining network topology and nodes interconnectivity

 Install and configure ET-MFX boards in the nodes
 Migration of Iub to IP
 Clean obsolete objects
 Infrastructure Aspects
 Infrastructure aspects

 Protocol Stack

 Iub over IP migration

 Defining network topology and nodes interconnectivity

 Install and configure ET-MFX boards in the nodes
 Migration of Iub to IP
 Clean obsolete objects
RBS 3810 with IP (P6)

Infrastructure Aspects
 Iub: ET-MFX12 or ETMFX13

– 7 port built in Ethernet switch

– 1 SFP + 6 Electrical Eth. ports
 Variant with 6 SFP and 1 Electrical
ports available (ETMFX13)
– Synch server Iub

RNC 3810
 RBS 3000 with IP

Infrastructure Aspects
 Iub: ETMFX11
 For Iub and O&M
 IP/Ethernet interface with optional Ethernet switch
 1 SFP + 6 Electrical Eth. ports
 Synch client

 RBS with CBU

 In P6.0, only RBS nodes equipped with CBU boards can be
configured for IP transport.

 RBS without CBU

 In P6.1 support for IP transport is also possible with older RBS
nodes (RBS2/3), with upgraded HW (GPB and TUB).

 The RBS has to be equipped with a GPB with at least 512 MB RAM. The RBS 3206
recommended version is ROJ 119 2106/51, revision R2 or later.
 The RBS has to be equipped with a Timing Unit Board 2 (TUB 2)
variant.
Protocol Stack
 Infrastructure aspects

 Protocol Stack

 Iub over IP migration

 Defining network topology and nodes interconnectivity

 Install and configure ET-MFX boards in the nodes
 Migration of Iub to IP
 Clean obsolete objects
Iub Protocols from ATM to IP

Protocol Stack
Radio Network Transport Network Radio Network
Control Plane Control Plane User Plane

Radio DCH, HS-DSCH, E-DCH Node

Network Synch FACH, PCH, RACH FPs
Network NBAP Synch
and Node Sync (over FACH)
Layer
Control Plane User Plane

Transport
Network ALCAP
Layer , Q.2150.2)
(Q.2630 NTP

SAAL-UNI
SCTP SAAL-UNI UDP AAL2 AAL0
ATM IP
Ethernet
Physical Layer (E1, J1, STM-1 etc)
Iub over IP migration
 Infrastructure aspects

 Protocol Stack

 Iub over IP migration

 Defining network topology and nodes interconnectivity

 Install and configure ET-MFX boards in the nodes
 Migration of Iub to IP
 Clean obsolete objects
IP address plan for RNC Iub
Type of IP address Max Redunda Number of IP
number ncy addresses

IP host for Iub UP (ET-MFX) 16 - 16

IP host for Iub CP (module MP) 33 2 66

Subtotal (RNC IP hosts): 82

Default Gateway (external) 1 3 3

Actual subnet address 1 - 1

Broadcast address 1 - 1

Total (RNC with subnet): 87

Closest Subnet size 128 (41 spare)

IP address plan for RBS Iub
Type of IP address Max Redundan Number of IP
number cy addresses

IP host for UP (ET-MFX) 1 - 1

IP host for CP 1 - 1

Subtotal (RBS IP hosts): 2

Default Gateway (external) 1 1-3 1 (typical)

Actual subnet address 1 - 1

Broadcast address 1 - 1

Total (RBS with subnet): 5

Closest Subnet size 8 (3 spare)

IP Addressing/VLAN - Overview
 Basic principles:
 Logical separation of O&M and traffical IP Transport
VLAN ID 100-110 traffic, VLAN ID 900-910 O&M (typical)
 Share physical resources
 One-to-one mapping Subnetwork <-> VLAN
 Traffical and O&M IP networks can use private IP addresses (see RFC 1918)
 The recommendation is to use addresses from the 10-network (10.x.y.z)
 IP Addressing considerations:
 Addressing for Iu/Iur in RNC (common with CN Nodes)
 Iub IP Transport
L3 based (one subnet per node)
 L2 based (large subnets)
 O&M IP Addressing
 Install and configure ET-MFX12 boards in the
RNC

Ethernet/IP Backhaul
(port 6 for electric and
port 7 for optical cable)

Redundancy Jumper from

other ET-MFX (Port 1)

 Insert ET-MFX12 Board(s) and Cabling

Install and configure ET-MFX12 boards in the
RNC

The ET-MFX board is the key product to be installed in

the RNC in order to handle Iub traffic over IP
For Installing the ET-MFX boards in the RNC confirm that
the following prerequisites are fulfilled

 ET-MFX12 boards are available

 RNC is Hardware R4 or higher

 The RNC has available slots for installing the new ET-MFX12
boards, Extension sub-rack preferred

 The RNC is running P6 software

Install and configure ET-MFX12 boards in the
RNC
 The appropriate cable kits and applicable ICF connections
plates are available

 A Thin Client configured to run EMAS

 Java 1.4.2_8 or higher is installed on the Thin Client

 Mo and/or BCT configuration scripts are available and

prepared according to network IP address plan

 OSS R5.3 up and running in case of BCT files are used

Procedure to install ET-MFX Board on RNC
Open RNC Element Manager
Assure that the slot is available

Figure above show slot 4th is available

Verify that Auto Configuration is activated
AutoConfigurationAllowed -> True
Install and configure ET-MFX12 boards in the
RNC

 Before Installing the ET-MFX12 boards. The ET-MFX12 Software Allocation role must
be assigned to the right slots,
 Run Expand RNC Tool Part 1
Run the RNC Hardware Configuration Tool – Part 1
Go to Tool -> RNC Hardware Configuration Tool. Then
assign software allocation to the ET-MFX slot. Then press
Apply.

 Select for slot(s)

appropriate
Software Allocation
Role
Install and configure ET-MFX12 boards in the
RNC

 Go back to the MS (Main subrack) frame and insert the RNC UserId and Password in
the blank field, then press Apply
Install and configure ET-MFX12 boards in the
RNC

 Run Expand RNC Tool Part 2

 Insert the RNC UserId and Password in the blank field, then press Apply
Install and configure ET-MFX12 boards in the
RNC

 ET-MFX12 board are installed

Install and configure ET-MFX12 boards in the
RNC

If Objects are installed. Create a new Configuration Version

Install and configure ET-MFX12 boards in the
RNC

TransportNetwork ManagedElement Equipment Subrack

Sctp IpSystem Slot

IpAccessHostGPB IpAccessHostPool IpAccessHostEt PlugInUnit

ExchangeTerminalIp

Red frame = System created InternalEthernetPort EthernetSwitch SwitchStp

IpInterface EthernetSwitchPort SwitchPortStp

 Check that every System Created Object is installed

Procedure to install ET-MFX Board on RBS
Slot position based on RBS type:
RBS Type ET Slots

RBS 3206F/E 2, 3, 22 and 23

RBS 3206M 2, 3 and 4
RBS 3518 2
RBS 3418 2

The Hardware Configuration and Software allocation

procedure is the same on RBS
Install and configure ET-MFX11 boards in the
RBS

 Verify that Auto Configuration is activated

Install and configure ET-MFX11 boards in the
RBS

Ethernet/IP Backhaul (port 6

for electric and port 7 for
optical cable)

O&M from CBU (port 3)

O&M from ET-MFX port 2

 Install ET-MF11 Board in the RBS

Install and configure ET-MFX11 boards in the
RBS

 Connect the Ethernet transport cable in the System port cable, the O&M cable must
be connected from the CBU board to the ET-MFX11 board.
 Add “jumper” cable for O&M from ET-MFX (System port 2) to CBU.
Install and configure ET-MFX11 boards in the
RBS
TransportNetwork ManagedElement Equipment Subrack

Sctp IpSystem Slot

IpAccessHostGPB IpAccessHostEt PlugInUnit

IpSyncRef ExchangeTerminalIp

InternalEthernetPort EthernetSwitch SwitchStp

Red frame = System created

Yellow frame = Initial configuration
Blue frame = Site Basic (On-site) IpInterface EthernetSwitchPort SwitchPortStp
Green frame = Site Specific (ARW, BCT)

 Check that System created Object is installed

Procedure to configure ET-MFX board on
RNC (Prerequisites)
ATND document from Ericsson Network Design
team
IP address allocation
ET-MFX installed on RNC and RBS
Router configuration prepared
Procedure to configure ET-MFX board on
RNC (Sample Script)
Confirm IpInterface MO already created on RNC

Define and Configure Control Plane

RNC_MS-27_ControlPlane_Sample.mo

Define and Configure User Plane

RNC_MS-27_UserPlane_Sample.mo
Define and Configure IubLink

RNC_MS-27_Iublink_Sample.mo
Manually change this value according to ATND
Equipment=1,Subrack=MS,Slot=27,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitch=1
a. enableVlan
b. pbitQueueMap
c. untaggedIngressVid
d. vlanMembership

Equipment=1,Subrack=MS,Slot=27,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1
a. dscpPbitMap

Equipment=1,Subrack=MS,Slot=27,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitch=1,EthernetSwitchPort=6
a. operatingMode
b. pbitQueueMap
c. systemPort
d. untaggedIngressVid
e. vlanMembership
Procedure to configure ET-MFX board on
RBS (Sample Script)
Confirm IpInterface MO already created on RNC

Define and Configure User Plane

RBS_UserPlane_Template.mo
Define and Configure Control Plane

RBS_ControlPlane_Template.mo
Add NTP Synchronization

RBS_IPSync_Template.mo
Manually change this value according to ATND
Equipment=1,Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitch=1
a. enableVlan
b. pbitQueueMap
c. untaggedIngressVid
d. vlanMembership

Equipment=1,Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminalIp=1,InternalEthernetPort=1
a. dscpPbitMap

Equipment=1,Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitch=1,EthernetSwitchPort=6
a. operatingMode
b. pbitQueueMap
c. systemPort
d. untaggedIngressVid
e. vlanMembership
Keep this locked for RBS. Because RSTP (Rapid
Spanning Tree Protocol) is not used in RBS
Rapid Spanning Tree Protocol (RSTP) is used for
protection switching in the Ethernet network, so that
a failure in a single board does not stop the traffic
from any other board and so that for any one failing
link there is always a combination of other links that
can transfer the traffic (board protection)
Add the following ref to this parameter
userPlaneIpResourceRef

Backup CV
RNC Precheck before ATM-IP migration
Check on the following object are unlocked and
enabled
a. (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=MS,Slot=27,PlugInUnit=1
b. (UNLOCKED) 1 (ENABLED)
Equipment=1,Subrack=MS,Slot=27,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitch=1,EthernetS
witchPort=6
c. (UNLOCKED) 1 (ENABLED) IpSystem=1,IpAccessHostPool=Iub
d. (UNLOCKED) 1 (ENABLED) IpSystem=1,IpAccessHostEt=MS-27

IP ping test from object IpAccessHostEt until all the

configured IP in PE router & RBS can be reached
RBS Precheck before ATM-IP migration
Check on the following object are unlocked and
enabled
a. (UNLOCKED) 1 (ENABLED) Equipment=1,Subrack=1,Slot=2,PlugInUnit=1
b. (UNLOCKED) 1 (ENABLED)
Equipment=1,Subrack=1,Slot=2,PlugInUnit=1,ExchangeTerminalIp=1,EthernetSwitch=1,EthernetSwit
chPort=6
c. (UNLOCKED) 1 (ENABLED) IpSystem=1,IpAccessHostEt=Slot-2

IP ping test from object IpAccessHostEt until all the

configured IP in PE router & RNC can be reached
Check on IPsync are unlocked and enabled
ATM to IP migration
Make a test call, verify that the site is working fine
Lock Utrancell and IubLink in RNC
Change the user/controlplanetransportoption in RNC
> lset IubLink=Iub_BENTMU controlPlaneTransportOption atm=0,ipv4=1
> lset IubLink=Iub_BENTMU userPlaneTransportOption atm=0,ipv4=1

Change the user/controlplanetransportoption in RBS

> lset Iub=BENTMU controlPlaneTransportOption atm=0,ipv4=1
> lset Iub=BENTMU userPlaneTransportOption atm=0,ipv4=1

Unlock Utrancell and IubLink in RNC

Make a test call
Create CV both on RNC and Node B
Thank you