09_rn30037en06gln0__dcn

5/20/2018 09_RN30037EN06GLN0__DCN

1/40

1 Nokia Siemens Networks Presentation / Author / Date

For internal use

Module 7: DCN

5/20/2018 09_RN30037EN06GLN0__DCN

2/40


For internal use

Overview and Objective

The DCN network in OSS4 provides the means of creating aconnection between OSS and network elements as well asbetween different OSS sites

Objective of the Module is to To understand the overall DCN network architecture

What information is needed in order to plan DCN network

Different alternatives for implementation OSPF

5/20/2018 09_RN30037EN06GLN0__DCN

3/40


For internal use

Network Planning

All Equipment

IP AddressesNetwork Topology

System Requirements

Network planning

5/20/2018 09_RN30037EN06GLN0__DCN

4/40


For internal use

General View of OSS4 DCN

Regional clusterRegional cluster

Site 2Site 2

Regional clusterRegional cluster

Site 3Site 3

3G 2G 3G 2G

WAN (IP)

VPN

Global clusterGlobal cluster

Site 1Site 1

PaCo PaCo

5/20/2018 09_RN30037EN06GLN0__DCN

5/40


For internal use

3G DCN Architecture

2G MSC MGW

3G Switching Core NetAct

RNC RNC RNC

BTSBTSBTSBTSBTS

BTSBTS

BTSBTSBTSBTS

IP DCN

3G SGSN

3G Packet Core

3G RAN

Iub

IuCS

Iur

IuPS

BTS

RNC DCN

area

5/20/2018 09_RN30037EN06GLN0__DCN

6/40


For internal use

RAN IP addressing

IP addressing is dependent on the network topology -> No default IPaddressing scheme can be provided

OMU in the RNC acts as an IP router

Reserve appropriate subnet for RNC internal LAN (depends on your IPnetwork configuration)

WCDMA BTS consists of AXC and Ultrasite and Flexi BTSs

Allocate a /29 subnet per BTS at minimum

/28 subnet recommended

Unnumbered links between BTSs

Simplifies the IP network planning

Since RAN04 static and OSPF routing is supported -> To make therouting configuration easier, use network segmentation (routesummarization)

Leave space for possible network expansion (for example 2 x /29 subnetsfor each WCDMA BTS)

5/20/2018 09_RN30037EN06GLN0__DCN

7/40


For internal use

IP over ATM connection for DCN in Ultra site BTS

VCI 36

VCI 30

AXU

Private IP addresses192.168.255.32/25

LMP 192.168.255.129/25

IFUA

PDH, IMA or SDH

CIF 1 VCI 44

VPI 1

VPI 0VCI 32

Transmission

ConvergenceAdaptor

VPI 4

VPI 0

WBTS

C-NBAP

O&M

D-NBAP

AAL2 TPs

AAL2 sig

WAM 1-0

192.168.255.1

192.168.255.16O&M Master WAM

VCI 33

VCI 34

VCI 35

VCI 45

VCI 49

VCI 50

IP

router

WAM 1 is TelecomMaster WAM

5/20/2018 09_RN30037EN06GLN0__DCN

8/40


For internal use

AXC

MasterWAM

WAM WAM

LMP

Inter unitcommunication

inside AXC:Subnet: 192.168.254.0/ 24

192.168.255.1 192.168.255.2 192.168.255.3

192.168.255.32

WAM-AXU Subnet: 192.168.255.0 / 25192.168.255.16

192.168.255.129

192.168.255.130

LMP Subnet: 192.168.255.128 / 25

Internal IP Addresses in AXC

Private IP addresses are used only for BTS internal communication.

They are predefined and same in all BTS.

These addresses must not be used for any other purpose!

5/20/2018 09_RN30037EN06GLN0__DCN

9/40


For internal use

Private IP Addresses in AXC

Only public IP addresses are seen from other network elements and NMS.

"Public" addresses may be in the "private" IP address space

"Private" subnets in the sense of AXC are only those defined on the

previous slide.

AXC

MasterWAM

WAM WAM

10.100.0.5

10.100.0.9 10.100.0.9

LMP

10.100.0.9

LMT -10.100.0.10

Subnet: 10.100.0.8/29

5/20/2018 09_RN30037EN06GLN0__DCN

10/40


For internal use

Internal IP Addresses in Flexi BTS

Private subnet

Private IPv4 addresses fromthe 192.168.255.0/24 subnetare used in the BTS LAN forBTS-internal communicatione.g.

user plane forwarding

BTS internal O&M functions

Provide local access for the

element manager

FSP FSP FCM

FTM

192.168.255.129

IPV4 router

DCN

LMP

Flexi BTS

internal

LAN

FlexiBTS Control &Multiplexing

192.168.255.130

( For LMT to

connect to LMP)

5/20/2018 09_RN30037EN06GLN0__DCN

11/40


For internal use

Private IP Addresses in Flexi BTS

Public subnet

FTM and FCM have also publicIPv4 addresses

The public IPv4 addresses areconfigurable and used formanagement traffic

For external equipment at the BTSsite (e.g. battery backup, webcam,

antenna tilt etc.) FTM provides aDHCP server

Can statically (client identifier orMAC address) or dynamically(pool) allocate public IPv4addresses to the external

equipment 192.168.255.0/24 subnet must not

be used in the DCN for publicaddresses

FSP FSP FCM

FTM

IPV4 router

DCN

LMP

Flexi BTS

internal

LAN

FlexiBTS Control &Multiplexing

Flexi

Transport

Module

5/20/2018 09_RN30037EN06GLN0__DCN

12/40


For internal use

RNC IP Address Planning

IP addressing can be based onnetwork topology.

Depending on available address

ranges e.g. a /19 range could bereserved per RNC.

/19 subnet has max. 2046 subnetsand max. 8192 hosts.

This results in 448 /28 subnets orBTSs.

A0001

A0002

A0003

A0004

A0005

A0006

A0007

A0008

A0009

A0010

A0011

A0012

A0013

A0014

A0015

A0016

A0017 A0018

A0019

A0020

A0021

A0022

A0023A0024

A0025

A0026

A0027

A0028

A0029

A0030

A0031

A0032

A0033

A0034

A0035

A0036

A0037

A0038

A0039

A0040

A0041

A0042

A0043

RNC001

A0045

AXC

AXC

AXC

IU

IU

IU

IU

AXC

IU

IU

IU

A

IU

IU

IU

A

IU

IU

AXC

IU

AXC

IU

IU

IU

IU

IU

IUAXC

IU

A

A

AXC

AXC

IU

AXC

IU

IU

AXC

IU

AXC

AXC

AXC

AXC

AXC

AXC

AXC

AXC

AXC

AXC

AXC

AXC

IU

AXC

ATM

IU

ATM

AXC

AXC

RNC

IU

AXC

AXC

AXC

AXC

AXC

AXC

AXC

IU

AXC

IU

IU

IU

AXC

IU

AXC

IU

AXC

IU

IU

AXC

AXC

IU

AXC

AXC

AXC

IU

IU

IU

IU

AXC

IU

IU

IU IU

IU

IU

A

IU

IU

IU

IU

IU

AXC

IU

5/20/2018 09_RN30037EN06GLN0__DCN

13/40


For internal use

RAN DCN Topology Alternatives: Tree

IP: More complex IP topology as in Star topology

IP Planning: careful far-sighted IP planningrecommended to help for OSPF routesummarization

IP Routing: can be done automatically usingOSPF in the RNCs OMU (also in BTS startingwith AXC C2.1 sw!)

IP Resources: only few routing entries in AXCand RNC

ATM: Simple preconfigured topology

ATM Planning not needed: default VPI/VCIvalues can be used, no cross-connects neededto be planned for

ATM configuring not needed: preconfiguredVPI/VCI (from the planning guideline) values canbe used, no ATM cross-connects to beconfigured

ATM Resources minimised: no ATM cross-connects in AXC or RNC

Tree topology

Physical

connectionATMconnection= logical IPconnection

RNC

BTS

BTS

BTS

BTSBTS

BTSBTS

BTS

5/20/2018 09_RN30037EN06GLN0__DCN

14/40


For internal use

RAN DCN Topology Alternatives: Star

IP: Simpler IP topology as in Tree topology IP Planning: simple IP address planning

IP Routing: simple in AXC, many routes in RNC, butdone automatically via OSPF

IP Resources: only 1 routing entry in AXC, but 1 perBTS in RNC

ATM: More complex ATM topology as in Tree topology

ATM Planning: individual VPI/VCI per BTS to be

planned for cross-connects needed for all AXC on wayto RNC

ATM configuring: individual VPI/VCI to be configuredBefore adding a new BTS, all the ATM cross-connectsbetween the new node and RNC needs to be updated.

ATM Resources: many ATM cross-connects in BTS,many VPI/VCI ending in RNC

Star topology

Tree or Star? Compare OPEX (Operational expenses) estimations

BTSBTSBTSBTS

BTS

Physical connection

ATM connection= logical IP connection

RNC

BTSBTSBTS

Note: Since RAS05 RNC supports 512 simultaneous IP over ATM connections (AA interfaces)

5/20/2018 09_RN30037EN06GLN0__DCN

15/40


For internal use

DCN Network Topology Alternatives

5/20/2018 09_RN30037EN06GLN0__DCN

16/40


For internal use

DCN Bandwidth Requirements

Nokia recommends an available DCN bandwidth of 64 kbit/s (~151 cps) perBTS.

The network topology has an impact on how this is bandwidth is allocated.

In case all BTS DCN connection is a point to point in a star topology, then

this 64 kbit/s is speared from the control plane and user plane bandwidth(configure all the CBR VCCs in a way that there is 64 kbit/s unallocated onthe Iub;

DCN bandwidth = Total Iub capacity (C-NBAP+D-NBAP+AAL2SIG+AAL2UP)

In case there is DCN UBR VCC level cross connection, or intermediate IProuting for the DCN traffic, the last mile should respect the aboverecommendation, but the intermediate bandwidth, RNC-ATM switch, ATMswitch-ATM switch, etc should be left to an IP dimensioning based on

estimated DCN traffic.

Minor bandwidth savings with intermediate IP routing

Less configuration work with intermediate IP routing

5/20/2018 09_RN30037EN06GLN0__DCN

17/40


For internal use

IP DCN Example

NE-RNC-01IP add :

10.10.0.0/24

OMU10.10.0.1

AA1

EL0 10.10.0.2

NTP server

10.0.1.230

OSS IP net.

IP add : 10.100.0.16/28

AXC

10.100.0.25

MWAM10.100.0.21

LMP

.27LMT =.26

.28 .29 .30

Use for 3rd party equipments

Subnet IP add :10.100.0.24/29

NE-AXC-02

IP add : 10.100.0.0/28

ESA12

OMS

DNS_1 10.0.1.240

DNS_2 10.0.1.245

10.10.0.5

10.0.1.129

NetAct

AXC

10.100.0.9

MWAM10.100.0.5

LMP

.11LMT =.10

.12 .13 .14

Use for 3rd party equipments

Subnet IP add :10.100.0.8/29

NE-AXC-01

5/20/2018 09_RN30037EN06GLN0__DCN

18/40


For internal use

IP DCN Example

10.100.0.2

5

5/20/2018 09_RN30037EN06GLN0__DCN

19/40


For internal use

Example of Different Ultrasite BTS subnets forDCN

If the unnumbered interface addressing is used,

all the AA interface will have the OMU-logical

address defined

Earlier DCN planning documents recommended an

addressing scheme like shown in left table because

AA-if subnet, MWAM subnet and LMP subnet hadto be separated. This is not valid anymore since

some releases ago. Therefore thetable above is

recommended to save IP addresses (network &

broadcast address)

5/20/2018 09_RN30037EN06GLN0__DCN

20/40


For internal use

IFUG Application Example

IFUG can be used to attachexternal equipment on site

In Flexi BTS the LMP can be

attached with external Ethernethub to connect externalequipment on site

IP addresses via DHCP

straight cablecross cablefibre cable

5/20/2018 09_RN30037EN06GLN0__DCN

21/40


For internal use

Example of Flexi BTS subnet for DCN

Flexi IP addresses

TRS IP address, Subnet Mask, DefaultGateway

Addresses via DHCP

The DHCP is used to automaticallyprovide IP configuration parameters toequipment or hosts connected to thelocal management port (LMP) of theBTS

DHCP parameters must be configured

on the transmission sub-module beforeit responds to the DHCP clients

Should be part of the subnet defined bythe TRS IP address and Subnet Mask

BTS IP address The BTS IP address has to be part of

the subnet defined by the TRS IPaddress and Subnet Mask

RNC IP address

10.130.30.21Free

10.130.30.20Free

10.130.30.19Free

10.130.30.18Real Tilt

10.130.30.23Broadcast

10.130.30.16Subnet/29

10.130.30.22BTS

10.130.30.17TRS

Example Flexi BTS subnet

5/20/2018 09_RN30037EN06GLN0__DCN

22/40


For internal use

RAN IP Addressing cont.

In many cases, the operator has existing IP network. Someaddresses ranges (usually 10.n.n.n or 192.n.n.n) have beenalready reserved and this reservation must be taken into

account during planning of 3G network. Clear IP address plan for 3G network elements

Separate switches and RNCs from access part (e.g. BS)

If, for example, the 10.n.n.n addressing is used, the plannerscan use the following recommendation:

10.0.0.0 10.0.255.255 Reserved for the backbone

10.1.0.0 10.9.255.255 Reserved for Core network (CS and PS)

10.10.0.0 10.99.255.255 Reserved for RNCs

10.100.0.0 10.199.255.255 Reserved for BS network

5/20/2018 09_RN30037EN06GLN0__DCN

23/40


For internal use

OSPF in AXC

5/20/2018 09_RN30037EN06GLN0__DCN

24/40


For internal use

OSPF in AXC for Routing

OSPF is a high level routing protocol

OSPF automates the exchange of routing information throughout anetwork no need to add manual routes all devices know how to reach each other in the network all devices configurations can as well affect all other devices

OSPF in BTS is available RAN04 onwards AXC C2.1 or newer required OSPF in RNC for DCN is totally independent from OSPF in RNC for Iu-PS Benefits of OSPF:

Automatic calculation of the routing tables for all network elements in the DCN No need for a manual configuration of routes

RNC receives automatically routing table information from new BTSs

AXC1 AXC2 AXC3

10.100.0.9 10.100.0.25 10.100.0.41

PtP linkPtP link

route

dest: 10.100.0.41

gw: 10.100.0.25

dest: 10.100.0.9

gw: 10.100.0.25

5/20/2018 09_RN30037EN06GLN0__DCN

25/40


For internal use

Purpose and Use

Easier configuration of even large DCN networks

no need to configure additional routes in AXC1 to reach AXCs beyond AXC2 via IP

Protection of DCN links (limited scope)

If link (a) fails link (b) is used to reach AXC5 from AXC2

Optimised use of memory possible when stub areas are configured

All AXCs are holding only one route (towards RNC) to be fully interconnected to alldevices in Area 0

AXC2

AXC6

AXC5

AXC4AXC3

AXC7

AXC1

(a)

(b) (b)

RNC

OSS

GGSN

SGSN Area 0Area 1(Stub)

5/20/2018 09_RN30037EN06GLN0__DCN

26/40


For internal use

Configuration via AXC-Manager 1. Create OSPF area

2. Add DCN

interface

towards

next WBTS

in the chain

3. Add DCN

interface

towardsRNC

5/20/2018 09_RN30037EN06GLN0__DCN

27/40


For internal use

Limitations for OSPF in AXC

AXC in BTS does not support:

Propagation of static routes to OSPF

Configuration of Virtual Links Authentication on its OSPF messages

OSPF to routers on the subnet connected to LMP No OSPF messages are exchanged with routers on the LMP link (for

reasons of security) although the subnet might be advertised.

Other Routing Protocols, therefore it cannot be used as anASBR (autonomous system boundary router)

OSFP is not supported over numbered interfaces on BTSO&M interfaces

5/20/2018 09_RN30037EN06GLN0__DCN

28/40


For internal use

OSPF areas example

In 3G OSPF is best used with treetopology

General OSPF rules:

If a router is partof multiple areas,one of the areas hasto be the backbone

Routers in an area shouldnot be more than 50

ABR router in 3G networksusing OSPF is the RNC

BTS areas should be configured astotally stub areas

Address allocation should be contiguousto make route summarisation possible

Backbone

RNC

subnet

BTS

BTSBTS

BTS

BTS

BTS

BTS

BTS

Area 501

IP 10.150.16.0/20

Area 500

IP 10.150.0.0/20

Area 50

IP 10.10.5.0/24

Area 0

RNC

5/20/2018 09_RN30037EN06GLN0__DCN

29/40


For internal use

Configuring DCN in RNC

5/20/2018 09_RN30037EN06GLN0__DCN

30/40


For internal use

Configuring IP for BTS O&M

1. Configure physical interfaces.

2. Create ATM resources (ATM interfaces, access profiles, VPLtps, VCLtps).

3. Create an IP over ATM interface towards BTS in OMU (QMF).

4. Assign IP addresses to the network interface (QRN).

5. Create static route for O&M connection towards BTS (QRC) or configure OSPF.

IP over ATM

interface

ATM

interface

VPI,

VCI

unnumbered

interface

Index skipped when

logical IP address

IP address,

logicaldestination IP

address

State*no index

neededMTU

size

OMU

indexdestination IP

address

Default:

GW

Gateway addressnetmas

kIP /

MAC

5/20/2018 09_RN30037EN06GLN0__DCN

31/40


For internal use

3. Required parameters for IPOAM in the RNC (1/2)

Parameters for IP over ATM interface:

unit type/Index

OMU and its index (0 or 1). For interface terminated on the logical address, skip index.

Logical/physical

L or P, This parameter defines whether IP over ATM interface is terminated to the logicalor physical address type of the unit. The possible parameter values are L for logicaladdress type and P for physical address type.

DCN connection is terminated on the logical OMU address.

IP interface Its a unique name for the IP over ATM interface. It begins with 'AA' and continues withnumbers, for example AA0, AA1....

ATM interface if / VPI / VCI

Encapsulation method

LLC/SNAP or VCmux. The default value is LLC/SNAP.

Usage

The value can be IPOAUD, IPOART or IPOAM. The default value is IPOAM.

5/20/2018 09_RN30037EN06GLN0__DCN

32/40


For internal use

4. Required parameters for IPOAM in the RNC (2/2)Parameters to assign IP address for the created AA interface

unit type/index OMU and its index (0 or 1). For interface terminated on the logical address, skip index.

Interface name Starts with AA

point to point interface type N (Numbered Interface, unique IP address, default), U (Unnumbered interface, shares IP address)

IP address The address of the OMU is specified in conventional dot notation (#.#.#.#).

IP address type

L (Logical IP address. This address belongs to the specified interface of the specified functional unit.The logical IP address follows the active unit. The logical IP address can be given to 2N and N+1units. In N+1 units you have to identify unit type and unit index. In 2N units you only have to identifythe unit type of the 2N unit; unit index is not needed)

P (Physical IP address). This address is assigned to the specified computer unit permanently.

destination IP address

The IP address of the point-to-point link. The address is specified in conventional dot notation(#.#.#.#). The range for each part of the address is from 0 to 255.

MTU The maximum transmittable size of a single, complete IP data unit. You can give MTU only for some

interfaces, for IP over ATM, the default value is 9180 byte.

5/20/2018 09_RN30037EN06GLN0__DCN

33/40


For internal use

5. Required parameters for IP static routes

The needed parameters for IP static routes are:

unit Type and Index

OMU,0 or OMU,1

destination IP address netmask length

The length of the destination address netmask.

next hop type

GW Gateway. The default value.

IF Computer unit's own interface

Address Type:

IP address or MAC (Link level MAC address).

IP/MAC Address:

This is the address of the gateway.

DCN: Interface Configuration FTM

5/20/2018 09_RN30037EN06GLN0__DCN

34/40


For internal use

DCN: Interface Configuration

1. Click Configuration TRS Configuration DCN Interfaces.

2. Click on New ATM DCN Interface.

4. Click Send to save changes.

Note: Interface, traffic descriptor and public IP address need to have been configured beforehand.

3. Configure all ATM Parameters using Pseudowire as ATM interface.

FTM

FTM

5/20/2018 09_RN30037EN06GLN0__DCN

35/40


For internal use

Pseudowire OAM: BFD Configuration #1

1. Click Configuration

TRS Configuration

ATM Over Ethernet.2. Select ATM Over Ethernet Settings.


3. Set Control Word In Use.

FTM

FTM

5/20/2018 09_RN30037EN06GLN0__DCN

36/40


For internal use

Pseudowire OAM: BFD Configuration #2

5. Click Configuration TRS ConfigurationATM Over Ethernet.

6. Select the required Pseudowire to setup BFD.


7. Take BFD Into Use.

FTM

F t D i ti IP Filt iAXC & FTM

5/20/2018 09_RN30037EN06GLN0__DCN

37/40


For internal use

Feature Description- IP FilteringRAS06

AXC & FTM

Logical Exception Domains = Ruleset

TRS

LMP

subnet

BTS

Application

Manager

NetAct

RNC

RAN/DCNNode-B

TRS Ruleset

BTS Ruleset

Power Supply Monitor

Any 3

LMP Ruleset

Real Tilt

rd party equipment

Application Manager at Far-End is used for the management of the equipmentsconnected locally to the BTS/AXC.


5/20/2018 09_RN30037EN06GLN0__DCN

38/40


For internal use

Feature Description- IP Filtering

IP and Port based filtering is security feature designed to restrict accessof some hosts towards DCN while allowing other hosts at the same time.

The Filtering is done on IP addresses and IP ports (TCP/UDP ports)

level.

By default, traffic between LMP and DCN network is discarded and alltypes of traffic between BTS/FTM and DCN network is allowed.

The filtering rules are classified into three Rulesets:

LMP Ruleset ..controls traffic between LMP subnet and DCN network

TRS Ruleset.. controls traffic between TRS and DCN network

BTS Ruleset.. controls traffic between BTS and DCN network

AXC & FTM


5/20/2018 09_RN30037EN06GLN0__DCN

39/40


For internal use

Feature Description- IP Filtering

The Near Endpoint IP address of each Ruleset is fixed. LMP Ruleset LMP subnet (as a whole). TRS Ruleset Public IP address of AXC/FTM. BTS Ruleset Public IP address of the BTS.

The Far Endpoint IP addresses and Near and FarEndpoint ports are configured by the user.

AXC & FTM

Allowed ports on the

LMP subnet Allowed Far end IP

address/es

Allowed ports on the

Far End host

Limitations of IP FilteringAXC & FTM

5/20/2018 09_RN30037EN06GLN0__DCN

40/40


For internal use

Limitations of IP Filtering

Maximum rules that are allowed under each rule set is 32.

Port sequence configuration is not allowed in case of FTM.AXC allows in total 10 ports in sequence form for both near

and far endpoint ports. When Alias is used Far-end ports are fixed.

LMP rules are implied to whole LMP/TRS subnet

Enabling the Restricted Mode for LMP On deletes all rulesunder LMP rule set.

ICMP tests (with ping or tracert) can be done only whenWildcard rule is configured.

09_rn30037en06gln0__dcn

Documents